SYSHW through ZONE

SYSHW through TENSRFSM

SYSHW

%SYSHW-3-SYSHW_READ : A read operation has failed for device: [chars] error: [chars]
Explanation A syshw read operation failed for the mentioned device
Recommended Action The error message indicates a read failure for the device. No action is needed from the user. However, if these errors come continuously or frequently, it may indicate permanent fault with the specific device/component.


%SYSHW-3-SYSHW_WRITE : A write operation has failed for device: [chars] error: [chars]
Explanation A syshw write operation failed for the mentioned device
Recommended Action The error message indicates a write failure for the device. No action is needed from the user. However, if these errors come continuously or frequently, it may indicate a permanent fault with the specific device/component.


%SYSHW-3-SYSHW_REG_READ : A register read operation has failed for device: [chars] register: [chars] error: [chars]
Explanation A syshw register read operation failed for the mentioned device
Recommended Action The error message indicates a read failure for the device. No action is needed from the user. However, if these errors come continuously or frequently, it may indicate permanent fault with the specific device/component.


%SYSHW-3-SYSHW_REG_WRITE : A register write operation has failed for device: [chars] register: [chars] error: [chars]
Explanation A syshw register read operation failed for the mentioned device
Recommended Action The error message indicates a read failure for the device. No action is needed from the user. However, if these errors come continuously or frequently, it may indicate permanent fault with the specific device/component.


SYSPLAT

%SYSPLAT-5-PLIM_BLOCK_EVENT : Block [chars]/[dec] of PLIM device had I/O event [hex]
Explanation A PLIM device I/O event has occurred. This event is not serious but is logged for diagnostic purposes.
Recommended Action No user action is required.


%SYSPLAT-3-PLIM_BRIDGE_CRITICAL_ERROR : Reloading [chars] due critical event [hex] in block [chars]/[dec] of PLIM device
Explanation A critical PLIM device I/O event has occurred.
Recommended Action The system automatically reloads the hardware component experiencing the error. If the problem persists, copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative.


%SYSPLAT-5-PLIM_EVENT_RATE : The [chars] event rate of [int] has exceeded the threshold of [int] on interconnect [dec]
Explanation A Serial Bridge has experienced a high event rate. This condition is not considered serious, but is logged for diagnostic purposes. This could be due to a hardware or software driver defect.
Recommended Action No user action is required. If this message persists, a PLIM device critical message that needs to be addressed will appear.


%SYSPLAT-3-PLIM_CRITICAL_ERROR_RATE : Reloading [chars] due to critically high PLIM device error rate.
Explanation A Serial Bridge has experienced a persistently high error rate. The condition is serious and the card must be reloaded. This could be due to a hardware or software driver defect.
Recommended Action Copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative.


TAC

%TAC-6-SENDTMO : Send type [dec] to [IP_address] timed out
Explanation 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.
Recommended Action Check the TACACS server and the network attached to it.


%TAC-4-UNEXREP : Reply for non-existent request, [dec] on queue
Explanation 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.
Recommended Action If this message recurs, call your technical support representative for assistance.


%TAC-3-XTACACL : [chars]: accesslist [hex] out of range for [chars]
Explanation The TACACS facility created a message that contains an accesslist which is not a valid accesslist (out of bounds).
Recommended Action If this message recurs, call your technical support representative for assistance.


%TAC-4-NOTIMEOUT : Warning: This command has been deprecated in favor of the line-command timeout login response
Explanation This command is deprecated, and should no longer be used. Instead, the line-command timeout login response now provides this functionality
Recommended Action Use the line-command timeout user-response


%TAC-3-PICKCTX : No pick-context
Explanation The context to pick the next server has disappeared.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TAC-4-SERVREF : Warning: Server [chars]:[dec] is still referenced by server group.
Explanation The server being removed is still referenced by a server group
Recommended Action Please dereference the server from the server group as soon as possible.


%TAC-4-SERVREFNAME : Warning: Server [chars] is still referenced by server group.
Explanation The server being removed is still referenced by a server group
Recommended Action Please dereference the server from the server group as soon as possible.


%TAC-3-SERVNO : Server [chars] is not configured
Explanation The server is not configured
Recommended Action Please configure a server before un-configuring it


%TAC-6-SERVDEP : tacacs-server host CLI will be deprecated soon. Please move to tacacs server <name> CLI
Explanation Migration from tacacs-server host CLI to tacacs server <name> CLI
Recommended Action Please try to use new CLI


%TAC-3-SERVCONF : Server config failure: [chars]
Explanation The server configuration failed
Recommended Action Please configure the server properly


%TAC-3-SERVINT : [chars]
Explanation This is an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TAC-3-SECRETDEFINEFAILED : Key definition ignored.
Explanation 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.
Recommended Action Configure a proper secret.


TAGMGR_DB_SYSLOG

%TAGMGR_DB_SYSLOG-3-TAGMGR_RF_TAG_CREATE_ERROR : Failure during RF tag [chars] creation, could not add to rf profile tag list
Explanation Failed to add RF tag to RF profile tag list
Recommended Action Please delete the RF tag and configure again


TAR_FS

%TAR_FS-3-IMAGE_FILE_INVALID : [chars] file not found in archive
Explanation The Tar File System could not locate the relevant tar element inside the archive
Recommended Action Check whether the Archive is complete and not corrupted or of the wrong format. If the problem could be recreated with debug ifs file turned on, it could help in quick identification of the problem. Collect the output of archive tar /table archive-name if it is a pure tar archive or show image contents file archive-name if the archive is a system image


TCP

%TCP-3-TCP_REG_FAILED : QFP TCP registers failed
Explanation Cisco internal software error. QFP TCP feature initialization detected that registration failed. QFP TCP will not be functional while this condition exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


TCP_PROXY

%TCP_PROXY-2-PROXY_IPC_INIT_FAILED : QFP TCP Proxy IPC initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP TCP Proxy initialization detected that the IPC interface initialization failed. QFP TCP proxy will not be functional while this condition exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TCP_PROXY-3-PROXY_BAD_MSG : CPP TCP Proxy received bad length message type [dec]
Explanation Cisco internal software error. CPP TCP Proxy received a corrupted message from control plane. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TCP_PROXY-3-PROXY_INV_MSG : CPP TCP Proxy received invalid message type [dec]
Explanation Cisco internal software error. CPP TCP Proxy received an invalid message type from control plane. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TCP_PROXY-3-PROXY_IPC_CHUNK_FAILED : CPP TCP Proxy chunk memory failure [dec]
Explanation Cisco internal software error. QFP TCP Proxy chunk memory allocation detected failure. QFP TCP proxy will not be functional while this condition exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TCP_PROXY-3-PROXY_IPC_ALLOC_FAILED : CPP TCP Proxy [chars] message lost due to message buffer allocation failure.
Explanation Cisco internal software error. CPP TCP Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TCP_PROXY-3-PROXY_IPC_SEND_FAILED : CPP TCP Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. CPP TCP Proxy message processing detected a message sent failure. The message is lost as the result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TCP_PROXY-3-PROXY_DEBUG_REG_FAILED :
Explanation TCP Conditional Debugging registration failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


TDLDB

%TDLDB-3-SESSION_LOCK_TIMEOUT : Owner: user-proc: [chars], DB: [chars]. Lock expired [chars] ago.
Explanation An application running in a process wishes to have an exclusive write access to DB. It acquires a session lock with for a specific period and is expected to release or renew the session lock. The appication has failed to do so and hence the unexpected timeout has occured
Recommended Action This is unexpected. Report this to Cisco TAC.


TELNETD

%TELNETD-3-ISSUE_FILE_OPEN : Error opening login banner: [chars]
Explanation An error has occurred opening the login banner. It could not be displayed to a user connecting via telnet.
Recommended Action 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) . If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


TENSRFSM

%TENSRFSM-3-NULLMACH : Invalid machine pointer [hex]
Explanation state machine invalid pointer
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TENSRFSM-3-INVSTATE : Invalid current state [hex]
Explanation state machine invalid state
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TENSRFSM-3-INVEVENT : Invalid event_id [hex]
Explanation state machine invalid event
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TENSRFSM-3-INVTRANS : obj: [[hex]] event_id: [[hex]] er_p: [[hex]] arg: [[hex]] session state [chars] -> [chars]
Explanation state machine invalid transition
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TENSRFSM-3-NOEVENT : Unable to apply event [hex]
Explanation state machine transition failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TENSRFSM-3-NOPROCID : Unable to launch TE NSR FSM Process.
Explanation state machine transition process launch failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


THREAT_DEFENSE through TRACK

THREAT_DEFENSE

%THREAT_DEFENSE-3-VTCP_INIT_FAILED :
Explanation Initialization of VTCP failed.
Recommended Action LOG_STD_ACTION


%THREAT_DEFENSE-3-DESTROY_CHUNK_FAILED :
Explanation Destroy chunk failed.
Recommended Action LOG_STD_ACTION


%THREAT_DEFENSE-4-TD_ERM_AVERAGE_THREAT : Event Rate Monitoring: Average threat identified. Zone [[chars]], event type [[chars]], average [[dec]] configured threshold [[dec]]
Explanation Event Rate Monitoring: Average threat identified
Recommended Action LOG_STD_ACTION


%THREAT_DEFENSE-4-TD_ERM_BURST_THREAT : Event Rate Monitoring: Burst threat identified. Zone [[chars]], event type [[chars]], configured threshold [[dec]]
Explanation Event Rate Monitoring: Burst threat identified
Recommended Action LOG_STD_ACTION


THREAT_DEFENSE_PROXY

%THREAT_DEFENSE_PROXY-3-PROXY_MEM_EXTEND_FAILED :
Explanation Extending memory failed.
Recommended Action LOG_STD_ACTION


%THREAT_DEFENSE_PROXY-4-PROXY_IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid IPC message length.
Recommended Action LOG_STD_ACTION


%THREAT_DEFENSE_PROXY-4-PROXY_IPC_INVALID_MSG : [dec]
Explanation Invalid IPC message
Recommended Action LOG_STD_ACTION


%THREAT_DEFENSE_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action LOG_STD_ACTION


TIME

%TIME-3-HB_SEQ_FAIL : expected seq_num [hex], rcvd seq_num [hex], MSGDEF_LIMIT_MEDIUM
Explanation The timer services had exceeded the maximum number of timer heartbeat sequence number errors.
Recommended Action LOG_STD_ACTION


%TIME-2-TIMESTAMP_BAD_CLOCK : [int]
Explanation Unsupported PPE core clock frequency.
Recommended Action LOG_STD_ACTION


%TIME-2-HB_START_FAILED : timer services failed to start
Explanation The timer services could not be started, because GPM allocation failed
Recommended Action LOG_STD_ACTION


TLSCLIENT

%TLSCLIENT-5-UPDOWN : Session [[IPV6 address]] to TLSGW: [[chars]] is [chars]
Explanation TLS Tunnel service state changed.
Recommended Action No action is required.


%TLSCLIENT-5-REKEY_CONN_FAILURE : Rekey failed for Session [[IPV6 address]] to TLSGW [[chars]]
Explanation This message indicates that the Rekey for the tunnel to the tlsgw failed.
Recommended Action Either the server is down or the connectivity to the server is broken


TMQ

%TMQ-3-NOTFOUND : TMQ, Attempt to delete entry not in queue
Explanation An attempt was made to delete an entry not in the queue.
Recommended Action Advisory message only. No action required.


TN

%TN-3-READLINE : Unknown return code [dec] from telnet_readline()
Explanation An internal software error occurred.
Recommended Action If any message recurs, call your technical support representative for assistance.


%TN-3-BADSTATE : Illegal state [dec]
Explanation An internal software error occurred.
Recommended Action If any message recurs, call your technical support representative for assistance.


%TN-2-BADLOGIN : Bad login string pointer [hex]
Explanation An internal software error occurred.
Recommended Action If any message recurs, call your technical support representative for assistance.


%TN-2-BADCONN : Bad conn pointer [hex] closing all connections on terminal line [dec]
Explanation An internal software error occurred.
Recommended Action If any message recurs, call your technical support representative for assistance.


TN3270

%TN3270-2-INP_OVF1 : Input Buffer overflow
Explanation 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.
Recommended Action Copy this error message exactly as it appears, and contact your technical support representative for assistance.


TPLUS

%TPLUS-3-FORKFAIL : Failed to fork process for [chars].
Explanation Quite likely, we ran out of memory. Other explanations are possible.
Recommended Action If this message recurs, call your technical support representative for assistance.


%TPLUS-3-UNKNOWNTYPE : TPLUS: [hex] Unknown Request type [int].
Explanation Unknown request type in client request
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


TR

%TR-2-PANICTYPE : Unit [dec], [chars] error
Explanation 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.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-2-PANIC : Unit [dec], panic %-08x %-08x %-08x
Explanation The Token Ring monitor firmware detected a fatal error that indicates an impending interface failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-2-PANICINF : Unit [dec], PI %-08x %-08x %-08x %-08x %-08x %-08x
Explanation 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.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-3-BADMUL : [chars]: Can't set address to a multicast ([enet])
Explanation An attempt was made to set the Token Ring interface MAC address to a reserved multicast address.
Recommended Action 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-BADSTART : Unit [dec], Start completion and wrong idb state - state= [dec]
Explanation An internal software error occurred.
Recommended Action 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) . If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-3-RESETFAIL : Unit [dec], reset failed, error code %-08x.
Explanation An internal software error occurred.
Recommended Action 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) . If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-6-STATE : [chars]: Ring Status: [chars]
Explanation 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.
Recommended Action No action is required.


%TR-6-STATRING : TR[dec]: Ring Status: [chars] [chars]
Explanation 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
Recommended Action Check the Token Ring for the indicated condition.


%TR-3-INTFAIL : Unit [dec] interface failure: [hex] [hex] [hex], idb state [dec]
Explanation The Token Ring Monitor firmware detected a fatal error due either to an internal software problem or to a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-3-BADRNGNUM : Unit [dec], ring number ([dec]) doesn't match established number ([dec]).
Explanation The number you have configured for the local ring does not match the value currently in use on the ring.
Recommended Action 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-WIREFAULT : Unit [dec], wire fault: check the lobe cable MAU connection.
Explanation The Token Ring hardware is reporting a wire fault condition.
Recommended Action Check the cable connecting the router to the Token Ring media attachment unit (MAU).


%TR-3-OPENFAIL : Unit [dec], open failed: [chars], [chars]
Explanation 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.
Recommended Action 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-OPENFAIL2 : Unit [dec], open failed: check the lobe cable DB-9 connection.
Explanation The Token Ring interface was unable to insert itself into the ring, and the error code returned indicates a wiring problem.
Recommended Action 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. LOG_STD_RECUR_ACTION


%TR-3-SETGRPFAIL : Unit [dec], set group address failed (code [hex]).
Explanation An internal software error occurred.
Recommended Action 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) . If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-3-SETFUNFAIL : Unit [dec], set functional address failed (code [hex]).
Explanation An internal software error occurred.
Recommended Action 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) . If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-3-SETBRIDGEFAIL : Unit [dec], set bridge failed (code [hex]).
Explanation A hardware error occurred. The source routing accelerator (SRA) chip on the Token Ring card could not be initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-3-BADUNIT : Bad unit number [dec]
Explanation 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.
Recommended Action If this message recurs, call your technical support representative for assistance. It will be necessary to determine the hardware unit configuration.


%TR-3-BADBUFFSIZE : Unit [dec], bad buffersize = [dec]
Explanation An internal software error occurred.
Recommended Action 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) . If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-3-BADFUNC : Unit [dec], bad functional address=[hex], ring mode=[hex]
Explanation An internal software error occurred.
Recommended Action 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) . If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-3-BADBRDGPARMS : Unit [dec], bad bridge parameters: bridge_num=[dec], max_rd=[dec]thisring=[dec], targetring=[dec]
Explanation An internal software error occurred.
Recommended Action 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) . If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-3-INITFAIL : Unit [dec], init failed. result code=[hex], error code=[hex]
Explanation The Token Ring hardware failed to initialize properly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-3-MODEFAIL : Unit [dec], change mode failed. result code=[hex], error code=[hex]
Explanation An internal hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-3-NOFIRM : Unit [dec], no TMS380 firmware present. eagle=[hex], magic=[hex]
Explanation An internal hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-3-BADFIRMTYPE : Unit [dec], bad firmware type code during [chars]. type=[hex], fw=[hex]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-3-BADFIRM : Unit [dec], Tokenring firmware download failed got [hex], expected [hex], at address [hex].[hex]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TR-2-NOMEMORY : Unit [dec], no memory for [chars]
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%TR-3-DIAGFAIL : Interface [chars] failed init diags ([hex]), [chars]
Explanation The microcode attempted to run its diagnostics on the chip and failed.
Recommended Action Issue a clear interface command. LOG_STD_RECUR_ACTION


%TR-3-ADPCHK : Interface [chars], adapter check error (non-fatal)([hex] [hex] [hex] [hex])
Explanation The Token Ring monitor firmware detected a non-fatal error on the interface card.
Recommended Action Issue a clear interface command. If this message recurs, call your technical support representative for assistance.


%TR-3-ADPCHKFATAL : Interface [chars], adapter check error (fatal) ([hex] [hex] [hex] [hex])
Explanation The Token Ring monitor firmware detected a fatal error on the interface card.
Recommended Action Issue a clear interface command. If this message recurs, call your technical support representative for assistance. You may need to replace the interface card


TRACK

%TRACK-3-ERROR : Internal error, [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TRACK-4-WARN : Internal warning, [chars]
Explanation An internal software warning occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TRACK-6-STATE : [chars]
Explanation The Tracked object has changed state.
Recommended Action No action is required.


%TRACK-6-INFO : Internal info, [chars]
Explanation An internal software information message occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


TRCCFG through UDLD

TRCCFG

%TRCCFG-3-INVALID_BOOT_TRACE_CFG : Boottime trace configuration string [chars] invalid
Explanation The value is not accepted by flash library due to an error. The result is that the boottime trace configuration settings are not successfully saved for use across re-boots.
Recommended Action Check that the boot trace configuration is valid. If valid, try saving configuration again.


%TRCCFG-3-ROMMON_OUT_OF_SPACE_TRACE_CFG : No space in rommon for boot trace configuration
Explanation Rommon is full and does not have room to save boot trace configuration.
Recommended Action Remove any unnecessary rommon variables to free up space and retry.


TSP

%TSP-3-NOEVENT : no free event structure available from [chars] for DSP message
Explanation There were no event structures remaining in the system pools to alert the router of a voice or signaling event.
Recommended Action Check that the voice port for which the event was reported is still operational. If not, clear the voice port.


%TSP-3-CAPABILITYMISMATCH : voice port [chars]: call connection id [[hex] [hex] [hex] [hex]]
Explanation There was a capabilities mismatch between the two call legs. capabilities are negotiated between call legs for CODEC, VAD and FAX rate.
Recommended Action 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-DSPALARM : voice port [chars]: status=[hex] message=[hex]
Explanation The DSP reported a fatal error. All calls on the DSP were dropped and a DSP reload was attempted.
Recommended Action 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-PRI : [chars] at slot [dec], unit [dec], channel [dec]
Explanation A PRI signalling channel is added/deleted to TSP's inventory of signalling channels.
Recommended Action This is a notification message only. No action is required.


%TSP-3-FSM_ERROR : [chars]
Explanation Internal Finite State Machine Error.
Recommended Action Contact your technical support representative, include the full text of the error message.


TTY

%TTY-3-AUTOCONFIG : TTY%t: Modem auto-configuration failed
Explanation 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.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TTY-3-NOPROCESS : Cannot create [chars] process
Explanation Failed creating the process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


TTYMON

%TTYMON-3-INIT : The software which monitors ownership of the console port cannot be initialized correctly
Explanation The Host Manager process on the Route Processor, and only the Route Processor, is responsible for determining which process has control of the console port, either IOSd or an IOSXE process. A user can initiate a switch in ownership by by entering the 'send break' command at a telnet prompt to switch from IOSd to a shell instance. Control is returned to IOSd by exiting the shell instance. The component within the Host Manager responsible for this has encountered an initialization error and console monitoring is no longer available.
Recommended Action Check the status of the Host Manager process. Check the Host Manager log files for further indications as to why the initialization failed and if necessary restart the machine.


%TTYMON-3-CHASFS : The software which monitors ownership of the console port cannot [chars] a filesystem configuration value.
Explanation The Host Manager process on the Route Processor, and only the Route Processor, is responsible for determining which process has control of the console port, either IOSd or an IOSXE process. A user can initiate a switch in ownership by by entering the 'send break' command at a telnet prompt to switch from IOSd to a shell instance. Control is returned to IOSd by exiting the shell instance. The component within the Host Manager responsible for monitoring a change of console ownership uses the filesystem to store various settings. This error indicates that the daemon encountered a problem either reading or writing a value from/to the filesystem.
Recommended Action Check the log files for the Host Manager and search for entries related to 'ttymon' and 'chasfs' and this should give an indication as to why the operation failed. Check available resources and see if other daemons are also experiencing problems with the chassis filesystem since this may indicate a more pervasive problem. If so the reboot the box.


%TTYMON-3-AGETTY : Cannot initiate a switch in console ownership. A required program could not be launched successfully.
Explanation The Host Manager process on the Route Processor, and only the Route Processor, is responsible for determining which process has control of the console port, either IOSd or an IOSXE process. A user can initiate a switch in ownership by by entering the 'send break' command at a telnet prompt to switch from IOSd to a shell instance. Control is returned to IOSd by exiting the shell instance. Switching ownership of the console port is initiated by the user entering a 'send break' command at a telnet prompt. The Host Manager launches one or more programs to authenticate users and to provide a shell instance. One or more of these programs has not been configured correctly.
Recommended Action Some required programs are either not available or not configured correctly or are failing for some reason. If this occurs after a recent upgrade it is possible that the upgrade has corrupted the current installation.


TUN

%TUN-3-API_ARGS : unexpected arguments: [chars], [chars]
Explanation A public tunnel component api was driven with arguments outside the expected boundaries.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-TUN_DB_IF : Operation on tunnel interface table failed for [chars] - [chars]
Explanation Manipulation of the tunnel interface table failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-RECURDOWN : [chars] temporarily disabled due to recursive routing
Explanation When routing the same payload protocol over a carrier protocol (tunneling IP over IP, for example), it is possible to misconfigure your network so that you will try to route to the tunnel destination address via the tunnel. This is usually caused by a misconfiguration of the tunnel or a temporary instability due to route flapping elsewhere in your network. It is important to take steps to ensure that routing information between the carrier networks and the payload networks is not allowed to mix. If the router discovers a recursive routing problem, it will temporarily shut down the tunnel interface for a few minutes so that the situation that is causing this problem can resolve itself as routing protocols converge. If the problem is caused by misconfiguration, the link may oscillate indefinitely.
Recommended Action No action is required.


%TUN-5-RECURDOWN_SRC : [chars] linestate down, recursive source interface, next output [chars]
Explanation Whilst evaluating tunnel linestate we revisted a source interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-ENDPOINT_STORE : Operation [chars] failed for [chars]
Explanation Manipulation of the tunnel endpoint store failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-MULTI_KEYS_INFO : [chars] [chars]
Explanation Manipulation of the tunnel keys database failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-MULTI_KEYS_INFO_ERROR : [chars] [dec]
Explanation Manipulation of the tunnel keys database failed because of incorrect idb_index.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-4-UDLR_IDB_ERROR : UDLR [chars] - [chars]
Explanation An error was encountered on a udlr interface
Recommended Action No action is required.


%TUN-3-ENDPOINT_ERROR : [chars] [chars]
Explanation An internal software error occurred when manipulating the tunnel endpoint database
Recommended Action No action is required.


%TUN-5-IGNOREICMPMTU : [chars] ignoring received ICMP Type 3 Code 4, due to pmtud min-mtu setting
Explanation An ICMP Type 3 Code 4 (fragmentation needed and DF set) packet has been received. This packet has specified a Next-Hop MTU smaller than the tunnel current minimum path mtu discovery mtu value. The ICMP packet has been ignored and the MTU of the tunnel has not been changed.
Recommended Action If you want the ICMP packet to be accepted and to be used to decrease the tunnel MTU then use the tunnel path-mtu-discovery min-mtu command to decrease the minimum mtu allowed. The min-mtu specified is the minimum tunnel payload mtu allowed. Use the show interface tunnel command to view the current path mtu discovery settings.


%TUN-5-IGNOREICMP6MTU : [chars] ignoring received ICMP6 Type 2 Code 0 , due to pmtud min-mtu setting
Explanation An ICMP6 Type 2 Code 0 (ICMP6 Packet Too Big message) packet has been received. This packet has specified a Next-Hop MTU smaller than the tunnel current minimum path mtu discovery mtu value. The ICMP6 packet has been ignored and the MTU of the tunnel has not been changed.
Recommended Action If you want the ICMP6 packet to be accepted and to be used to decrease the tunnel MTU then use the tunnel path-mtu-discovery min-mtu command to decrease the minimum mtu allowed. The min-mtu specified is the minimum tunnel payload mtu allowed. Use the show interface tunnel command to view the current path mtu discovery settings.


%TUN-3-MTUCONFIGEXCEEDSL2MTU_IPV4 : [chars] IPv4 MTU configured [int] exceeds tunnel maximum MTU [int]
Explanation 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.
Recommended Action 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]
Explanation 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.
Recommended Action 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-MTUCONFIGLESSTHAN_MINIPV4MTU : [chars] IPv4 MTU [int] is lesser than the minimum IP MTU [int], fragmentation may occur
Explanation 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.
Recommended Action 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-MTUCONFIGEXCEEDSTRMTU_IPV4 : [chars] IPv4 MTU configured [int] exceeds tunnel transport MTU [int]
Explanation 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.
Recommended Action 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]
Explanation 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.
Recommended Action 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-MTUDEFAULTEXCEEDSL2MTU_IPV4 : [chars] transport MTU [int] exceeds [chars] configured IPv4 MTU [int], fragmentation may occur
Explanation A default MTU value has been configured on the tunnel and this value exceeds the underlying physical interface MTU. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface.
Recommended Action If possible, increase the size of the IPv4 MTU on the underlying physical interface using ip mtu.


%TUN-5-TUN_TABLE : Operation [chars] on tunnel table failed for [chars] - [chars]
Explanation Manipulation of the tunnel table failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-DECAP_OCE : [chars] [chars]
Explanation An internal software error occurred in the tunnel subsystem which is responsible for building forwarding for the purposes of decapsulation
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-DECAP_TINFO : [chars] [chars]
Explanation An internal software error occurred in the tunnel subsystem which is responsible for driving forwarding based on the tinfo configuration
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-ILLEGAL_ARGS : Illegal arguments - [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-TUN_HWIDB_RECYCLE : Failed to recycle hwidb for Tunnel [dec] index [dec]
Explanation Recycling of tunnnel interface failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-TUN_SWIDB_RECYCLE : Failed to recycle swidb for Tunnel [dec] index [dec]
Explanation Recycling of tunnnel interface failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-TUN_HWIDB_DELETE : Failed to delete hwidb for Tunnel [dec] index [dec]
Explanation Deletion of tunnnel interface failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-TUN_SWIDB_DELETE : Failed to delete swidb for Tunnel [dec] index [dec]
Explanation Deletion of tunnnel interface failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-TUN_INTF_STATE_RESET : Failed to reset tunnel interface state for [chars]
Explanation Reset of tunnnel interface failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-TUN_UNIT_LIST_INSERT : Failed to add entry unit [dec] to tunnel unit list
Explanation Insertion of tunnnel unit failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-TUN_HWIDB_LIST_INSERT : Failed to add [chars] to tunnel hwidb list
Explanation Insertion of tunnnel to hwidb list failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-TUN_UNIT_LIST_DELETE : Failed to delete entry unit [dec] to tunnel unit list
Explanation Deletion from tunnnel unit failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-TUN_HWIDB_LIST_DELETE : Failed to delete [chars] from tunnel hwidb list
Explanation Deletion of tunnnel from hwidb list failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-TUN_LIST_CREATE : Failed to create tunnel list [chars]
Explanation Creation of tunnel list failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-HW_IF_INDEX_ILLEGAL : Attempt to create tunnel interface for [chars] with illegal index: [dec]
Explanation Creation of tunnel interface failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-INIT_ERROR : A critical error [chars]occurred during initialization
Explanation Creation of tunnel subsystem failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-TUN_SIDB2TUNS : [chars]: [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-TUN_SB : TUN_SB: [chars][chars][chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-TUN_DBG : TUN_DBG: [chars] [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-TUN_HA : Tunnel HA: [chars]
Explanation Tunnel HA encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-GROUPS : Tunnel Groups: [chars]: [chars]
Explanation The tunnel group component encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-WCCP_GROUP : Tunnel WCCP Groups: [chars]: [chars]
Explanation The tunnel group component encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-OTV_GROUP : Tunnel OTV Groups: [chars]: [chars]
Explanation The tunnel group component encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-L3VPN_GROUP : Tunnel L3VPN Groups: [chars]: [chars]
Explanation The tunnel group component encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-L3VPN_ENCAP_IP_PROFILE : L3VPN Encap IP : [chars]: [chars]
Explanation The L3VPN Encap IP component encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-4-L3VPN_ENCAP_IP_SRC_DEL : L3VPN Encap IP : [chars]: [chars]
Explanation The user configuration change results in a warning. This message is typically printed when the user tries to delete a loopback interface, and the loopback interface is configured as the source interface of the L3VPN encap IP profile
Recommended Action It is recommended that the user removes the loopback interface as the source interface of the L3vpn encap ip profile, before deleting the loopback interface.


%TUN-3-SIA_GROUP : Tunnel SIA Groups: [chars]: [chars]
Explanation The tunnel group component encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-6RD : [chars]: [chars]
Explanation The tunnel 6RD feature encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-6RD_INFO : [chars]: [chars]
Explanation 6RD configuration has been removed as it is not compatible with the new sub-mode
Recommended Action No action is required.


%TUN-3-CM1 : [chars]
Explanation The tunnel classification module encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-CM2 : [chars] [dec]
Explanation The tunnel classification module encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-3-TUNTO : Operation: [chars], Action: [chars], Reason: [chars]
Explanation The tunnel-to module encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TUN-5-L3VPN_IP_PROFILE_DELETE : l3vpn encap ip profile [chars] deleted
Explanation l3vpn encap ip profile is deleted
Recommended Action No action is required.


TVI_PROXY

%TVI_PROXY-2-TVI_MSG_PROXYINIT_FAILURE : ET-Analytics - Failed to register IPC message handler, result code [int]
Explanation QFP ET-Analytics feature failed to register an IPC message handler for communication with control plane. This will cause the featue not to function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TVI_PROXY-3-TVI_MSG_PROXY_UNKNOWN_IPCMSG : ET-Analytics - Received an unknown type (code [int]), IPC message
Explanation QFP ET-Analytics feature received an unknown message from another layer of ET-Analytics feature's software stack.
Recommended Action 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) . If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%TVI_PROXY-3-TVI_MSG_PROXY_INVALID_MSGLEN : ET-Analytics - Received an invalid length IPC message
Explanation QFP ET-Analytics feature received an incorrect length of IPC message from anoter layer of ET-Analytics feature's software stack, m_enum %d, m_subtype %d, m_len %d, m_flags 0x%x, m_source %d.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TVI_PROXY-3-TVI_MSG_PROXY_ALLOC_FAILURE : ET-Analytics - Failed to get [int] bytes space for IPC reply message
Explanation QFP ET-Anallytics feature detected buffer allocation failure while sending reply to a message from another layer of ET-Analytics feature's software stack.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TVI_PROXY-3-TVI_MSG_PROXY_OPENREPLY_FAIL : ET-Analytics - Failed to open reply message part of IPC packet
Explanation QFP ET-Analytics feature failed to open message part of IPC packet while sending a reply to another layer of ET-Analytics feature's software stack.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TVI_PROXY-3-TVI_MSG_PROXY_IPCSEND_FAIL : ET-Analytics - Failed to send IPC message, result code [dec]
Explanation QFP ET-Analytics feature failed to send IPC message to another layer of ET-Analytics feature's software stack.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TVI_PROXY-3-TVI_MSG_PROXY_DEBUG_REG_FAILED :
Explanation ET-Analytics Conditional Debugging Registration failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%TVI_PROXY-4-PROXY_IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid ET-Analytics IPC message length.
Recommended Action LOG_STD_ACTION


%TVI_PROXY-3-PROXY_HSL_CREATE_FAILED :
Explanation HSL creation failed.
Recommended Action LOG_STD_ACTION


%TVI_PROXY-3-PROXY_HSL_ADD_DEST_FAILED :
Explanation HSL add destination failed.
Recommended Action LOG_STD_ACTION


%TVI_PROXY-4-PROXY_HSL_ALREADY_INIT :
Explanation HSL logger already initialized
Recommended Action LOG_STD_ACTION


%TVI_PROXY-3-PROXY_HSL_MODIFY_DEST_FAILED :
Explanation HSL modify destination failed.
Recommended Action LOG_STD_ACTION


%TVI_PROXY-3-PROXY_HSL_BIND_FAILED :
Explanation HSL bind failed.
Recommended Action LOG_STD_ACTION


%TVI_PROXY-3-PROXY_HSL_ENABLE_FAILED :
Explanation HSL enable failed.
Recommended Action LOG_STD_ACTION


%TVI_PROXY-4-PROXY_HSL_NOT_INIT : [int]
Explanation HSL logger not initialized
Recommended Action LOG_STD_ACTION


%TVI_PROXY-3-PROXY_HSL_MODIFY_FAILED :
Explanation HSL modification failed.
Recommended Action LOG_STD_ACTION


%TVI_PROXY-3-PROXY_HSL_BIND_TEMPLATE_FAILED : [dec]
Explanation HSL bind tempalte failed at given index.
Recommended Action LOG_STD_ACTION


UBD

%UBD-2-INITIALIZATION_FAILED :
Explanation Initialization of ursa bootstrap process failed.
Recommended Action Review UBOOTD logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log.


%UBD-0-MQIPC_INITIALIZATION : MQIPC initialization failed because [chars]
Explanation MQIPC initialization failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%UBD-0-MQIPC_ADVANCE : Failed to advance MQIPC queue because [chars]
Explanation The MQIPC initialization failed.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%UBD-0-EVENT_LIBRARY : An event facility initialization or maintenance function failed because [chars]
Explanation An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered inforation to a Cisco technical support representative.


UCODE

%UCODE-3-BADCHKSUM : Bad checksum in [chars], found [hex] expected [hex]
Explanation 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.
Recommended Action Reload the microcode. If the message recurs, call your technical support representative for assistance.


%UCODE-3-HDRCORRUPT : Ucode header corrupted in [chars], found [hex] expected [hex]
Explanation 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.
Recommended Action Reload the microcode. If the message recurs, call your technical support representative for assistance.


%UCODE-3-LDFAIL : Unable to download ucode from [chars] in slot [dec], trying [chars] ucode
Explanation 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.
Recommended Action Attempt to reload the microcode. If the message recurs, call your technical support representative for assistance.


%UCODE-3-NOFILE : Ucode file [chars] not found, system ucode loaded in slot [dec]
Explanation The file specified by the configuration was not found in Flash. The onboard ROM microcode will be loaded so the interface can remain operational.
Recommended Action 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-BADHWVER : Ucode file [chars] requires [chars] version [dec].x hardware
Explanation 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.
Recommended Action Use the required microcode version.


%UCODE-3-RDFAIL : Unable to read ucode file [chars] from flash
Explanation For some reason, the microcode file was not read from Flash. Flash might be locked by another process or otherwise unavailable.
Recommended Action 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-3-TOOBIG : File [chars] at length [dec] is too long for buffer (size [dec])
Explanation The file is too large for the buffer. The onboard ROM microcode will be loaded.
Recommended Action If the error message recurs after the onboard ROM microcode is loaded, call your technical support representative for assistance.


%UCODE-3-WRONGHARD : [chars] is [chars] ucode not [chars], microcode/hardware mismatch
Explanation 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.
Recommended Action Reenter your microcode configuration command after confirming the interface type and reload the microcode.


%UCODE-5-OBSOLETE : FDDI unit [dec] has obsolete microcode: please upgrade it
Explanation 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.
Recommended Action Upgrade the microcode on the interface processor.


%UCODE-3-VERSIONCK : Inappropriate version [int].[int] for [chars]
Explanation An attempt was made to load an inappropriate version of microcode.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.


%UCODE-3-NOBUF : Unable to allocate memory for ucode buffer
Explanation A buffer is required to decompress microcode before loading it into an interface processor. This buffer could not be allocated for some reason.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.


%UCODE-3-NOMEMORY : Unable to allocate memory during microcode reload
Explanation An attempt at memory allocation failed while downloading microcode to Interface processor.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.


%UCODE-3-NOROM : Invalid attempt to load ROM ucode in slot [dec]
Explanation Some interface processors cannot load microcode from ROM.
Recommended Action Remove the erroneous configuration statement.


%UCODE-3-IPCINITFAIL : Unable to initialize IPC [chars] services
Explanation The InterProcess Communication (IPC) service used to download microcode to certain interface processors has failed to initialize.
Recommended Action Certain Interface Processors will not load properly. The router must be reloaded to clear the problem.


%UCODE-3-IPCBUFFAIL : Unable to obtain IPC resources
Explanation The InterProcess Communication (IPC) service used to download microcode to certain interface processors has failed to obtain a buffer.
Recommended Action 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-IPCINVALID : Invalid IPC request ([dec]) received from ([hex])
Explanation The InterProcess Communication (IPC) service used to download microcode to certain interface processors has received an invalid message.
Recommended Action Verify that the proper revisions of code are selected.


%UCODE-3-SRCTYPE : Invalid Ucode source type ([dec])
Explanation Microcode source type as specified is not supported on the given platform
Recommended Action Verify that the proper revisions of code are selected.


UDEV

%UDEV-3-UDEVPERMS : An invalid permissions value, [chars], was found in a udev file
Explanation The udev files for a particular filesystem contain a description the file system. If the permissions attribute is not recognized then this file system may run with incorrect permissions.
Recommended Action No action is required.


UDLD

%UDLD-3-UDLD_INTERNAL_ERROR : UDLD internal error: [chars]
Explanation A softare sanity check failed in the course of UDLD processing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%UDLD-3-UDLD_INTERNAL_IF_ERROR : UDLD internal error, interface [chars]: [chars]
Explanation A softare sanity check failed in the course of UDLD processing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%UDLD-3-UDLD_IDB_ERROR : UDLD error handling [chars] interface: [chars]
Explanation A softare error occurred in UDLD processing associated with a specific interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%UDLD-4-UDLD_PORT_DISABLED : UDLD disabled interface [chars], [chars] detected
Explanation 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.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%UDLD-6-UDLD_PORT_RESET : UDLD reset interface [chars]
Explanation A port which had been disabled for UDLD has been reset.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%UDLD-4-UDLD_PORT_FAILURE : UDLD failure reported per user request, interface [chars], [chars] detected.
Explanation 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.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


UFAST_MCAST_SW through UTD

UFAST_MCAST_SW

%UFAST_MCAST_SW-4-MEM_NOT_AVAILABLE : No memory is available for transmitting UplinkFast packets on Vlan [dec].
Explanation UplinkFast packets will not be transmitted on Vlan %d due to a lack of memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%UFAST_MCAST_SW-3-PROC_START_ERROR : No process available for transmitting UplinkFast packets.
Explanation UplinkFast packets will not be transmitted as the process could not be created.
Recommended Action 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.


UI

%UI-6-NOHANDLER : module type [int] subtype [int]
Explanation A UI message was received containing an unrecognized module type or module subtype
Recommended Action LOG_STD_ACTION


%UI-3-REPLY : module type [int] subtype [int]
Explanation A UI reply message failed in the IPC send. Sender will not get reply
Recommended Action LOG_STD_ACTION


%UI-3-IPC_ALLOC : module type [int] subtype [int]
Explanation IPC packet allocation failed for UI reply. Sender will not get reply
Recommended Action LOG_STD_ACTION


UICFGEXP

%UICFGEXP-3-MESSAGE_ERROR : Unable to process message for '[chars]': [chars]
Explanation A message was received by the configuration export module which could not be processed. The message has been discarded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%UICFGEXP-3-WRITE_FAILED : Unable to write configuration for '[chars]': [chars]
Explanation The configuration export module failed to write the server configuration files. The server configuration change has not occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%UICFGEXP-6-SERVER_NOTIFIED_START : Server [chars] has been notified to start
Explanation The server has been notified to start.
Recommended Action No action is required.


%UICFGEXP-6-SERVER_NOTIFIED_STOP : Server [chars] has been notified to stop
Explanation The server has been notified to stop.
Recommended Action No action is required.


%UICFGEXP-3-LIBRARY_ERROR : Error loading library '[chars]': [chars]
Explanation A configuration message was received which required a library to be loaded. The library failed to load.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%UICFGEXP-3-SYMBOL_ERROR : Error loading library symbol '[chars]' from '[chars]': [chars]
Explanation A configuration message was received which required a library to be loaded. The library failed to load all required symbols.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


UIPEER

%UIPEER-3-INVALID_EPOCH_MESSAGE : The peer process was unable to process an incoming epoch update message from the shell-manager
Explanation For each new type definition language (TDL) epoch, the Shell Manager broadcasts a change notification message to its peers. If the Shell Manager's message is incorrect or corrupt, the peers are unable to identify the new epoch. In this case, the peers reject the proposed epoch.
Recommended Action Check the trace files for the Shell Manager failed process. Check or undo any recently installed packages, then restart the system.


%UIPEER-3-INVALID_DEBUG_MESSAGE : The peer process was unable to process an incoming message for 'debug all' from the shell-manager
Explanation When the 'debug all' command is issued, the Shell Manager broadcasts a notification of the command request to its peers. If the notification message has been corrupted or incorrectly created, the peers cannot complete the requested operation.
Recommended Action Check the trace files for the Shell Manager failed process. Restart the system.


%UIPEER-3-INVALID_HOSTINFO_MESSAGE : The peer process was unable to process an incoming message for host info from the shell-manager
Explanation When host information, such as the hostname, changes, the Shell Manager broadcasts a notification of the change to its peers. If the notification message has been corrupted or incorrectly created, the peers cannot complete the requested operation.
Recommended Action Check the trace files for the Shell Manager failed process. Restart the system.


%UIPEER-2-TDL_MESSAGE : Cannot construct an IPC message for library. The message name is [chars] and the reason is: [chars]
Explanation A problem occurred while constructing a type definition language (TDL) message or setting a field in a TDL message. If the problem occurred during construction of a TDL message, then the system is out of memory. If the problem occurred while setting a field in the TDL message, there is a library mismatch issue.
Recommended Action Check [uipeer] ERR entries in the log files for message reporting problems.


%UIPEER-3-NO_PEER : A process was unable to retrieve a shell-manager peer handle.
Explanation A process was attempting to communicate with the Shell Manager daemon using the integrated [uipeer] component. The error occurred because the peer instance could not be found.
Recommended Action Check [uipeer] ERR entries in the log files for message reporting problems.


%UIPEER-5-TIMER_ACCURACY_TEST : Timer Accuracy Test [chars].
Explanation Test result of Timer Accuracy Test
Recommended Action No action is required. This is informational message


UMBRELLA

%UMBRELLA-6-UMBRELLA_DIRECT_CLOUD_ACCESS : Direct cloud access is enabled
Explanation Umbrella Direct cloud access Enabled
Recommended Action This message is for informational purposed only


%UMBRELLA-3-DNSCRYPT_CERT_MAGIC_MISMATCH : Invalid certificate received: Certificate magic mismatch
Explanation Umbrella DNSCrypt certificate magic mismatch
Recommended Action This message is for informational purposed only


%UMBRELLA-3-DNSCRYPT_UMBRELLA_OUT_FAILURE : DNSCrypt Channel connect failed: Interface with umbrella out config not found
Explanation Umbrella out is required on an interface for DNSCrypt channel connect
Recommended Action This message is for informational purposed only


%UMBRELLA-3-DNSCRYPT_CERT_MAJOR_VER_MISMATCH : Invalid certificate received: Certificate major version mismatch
Explanation Umbrella DNSCrypt certificate major version mismatch
Recommended Action This message is for informational purposed only


%UMBRELLA-3-DNSCRYPT_CERT_MINOR_VER_MISMATCH : Invalid certificate received: Certificate minor version mismatch
Explanation Umbrella DNSCrypt certificate minor version mismatch
Recommended Action This message is for informational purposed only


%UMBRELLA-3-DNSCRYPT_CERT_SIGNATURE_MISMATCH : Invalid certificate received: Certificate signature mismatch
Explanation Umbrella DNSCrypt certificate signature mismatch
Recommended Action This message is for informational purposed only


%UMBRELLA-3-DNSCRYPT_CERT_INVALID_START_TIME : Invalid certificate received: Certificate not active yet: start time [chars]
Explanation Umbrella DNSCrypt certificate not active yet
Recommended Action This message is for informational purposed only


%UMBRELLA-3-DNSCRYPT_CERT_INVALID_END_TIME : Invalid certificate received: Certificate expired on [chars]
Explanation Umbrella DNSCrypt certificate expired
Recommended Action This message is for informational purposed only


%UMBRELLA-3-DNSCRYPT_CERT_SUCCESS : Umbrella DNSCrypt certificate successfully received
Explanation Umbrella DNSCrypt certificate successfully received
Recommended Action This message is for informational purposed only


%UMBRELLA-3-DNSCRYPT_CERT_FAILURE : Failed to fetch Umbrella DNSCrypt certificate
Explanation Failed to fetch Umbrella DNSCrypt certificate
Recommended Action This message is for informational purposed only


%UMBRELLA-3-DNS_RES_FAILURE : Failed to resolve name [chars] Retry attempts:[dec]
Explanation Umbrella dns resolution for device registration server is failed.
Recommended Action This message is for informational purposed only


%UMBRELLA-3-SSL_HANDSHAKE_FAILURE : SSL handshake failed
Explanation Umbrella device registration failed,as SSL handshake did not succed
Recommended Action This message is for informational purposed only


%UMBRELLA-3-CONNECT_FAILURE : socket connection to the server [chars] failed ,Retry attempts:[dec]
Explanation Umbrella device registration failed, as socket connect failed
Recommended Action This message is for informational purposed only


%UMBRELLA-3-NO_UMBRELLA_OUT_FAILURE : umbrella out is not configured on wan interface
Explanation Umbrella out is required on wan for device registration
Recommended Action This message is for informational purposed only


%UMBRELLA-6-DEV_REG_SUCCESS : Device id for [chars]/tag [chars]/[chars] is [chars]
Explanation Device registration for the interface/profile is successfull
Recommended Action This message is for informational purposed only


%UMBRELLA-3-DEV_REG_UNAUTHORIZED : Invalid token/api-key/secret/orgid
Explanation Token/api-key/secret/orgid used for device registration is invalid
Recommended Action This message is for informational purposed only


%UMBRELLA-3-DEV_REG_INTERNAL_SERVER_ERROR : Internal Server Error
Explanation Server is not down/not responding
Recommended Action This message is for informational purposed only


%UMBRELLA-6-DEV_REG_CONFLICT : Device id is already assigned
Explanation Device id for this Token/API key is already assigned
Recommended Action This message is for informational purposed only


%UMBRELLA-6-DEV_REG_BAD_REQUEST : Request for device registration does not contain required parameters
Explanation Request for device registration does not contain required parameters
Recommended Action This message is for informational purposed only


%UMBRELLA-6-DEV_REG_TOO_MANY_REQUEST : Too many device registration requests
Explanation Too many device registration requests
Recommended Action This message is for informational purposed only


%UMBRELLA-6-DEV_REG_FORBIDDEN : Request for device registration does not contain correct uri
Explanation Request for device registration does not contain correct uri
Recommended Action This message is for informational purposed only


%UMBRELLA-3-UMBRELLA_SPLITDNS_MAX_PAT_EXCEEDED : UMBRELLA local domain bypass (maximum 64 rules allowed): [chars]
Explanation Max number of local domain patterns cannot exceed 64 as allowed by DSA.
Recommended Action This message is for informational purposed only


%UMBRELLA-3-UMBRELLA_SPLITDNS_MAX_PAT_LEN_EXCEEDED : UMBRELLA splitdns ignoring pattern as length exceeds maximum limit.[chars]
Explanation Local domain pattern length cannot exceed 100 for DSA.
Recommended Action This message is for informational purposed only


%UMBRELLA-3-UMBRELLA_HA_INIT_FAILURE : Failed to register with RF, rc = [dec]
Explanation Failed to register with RF during system initialization
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%UMBRELLA-3-UMBRELLA_HA_SYNC_FAILED : UMBRELLA HA syncing [chars] failed.
Explanation syncing of info to the peer node failed.
Recommended Action This message is for informational purposed only


%UMBRELLA-6-UMBRELLA_HA_MSG_RECV : UMBRELLA HA message [chars] received.
Explanation Message HA message received from peer node.
Recommended Action This message is for informational purposed only


%UMBRELLA-3-DEV_REG_TOKEN_INVALID : Token expired
Explanation Token used for device registration expired
Recommended Action Reactivtae Umbrella license


%UMBRELLA-3-DEV_REG_ORG_NOT_EXISTS : Org does not exists
Explanation Organization does not exists
Recommended Action Reactivtae Umbrella license


UPGRADE

%UPGRADE-3-STAGGERED_UPGRADE_MOVE_REPORT_ERROR : Staggered AP Upgrade reboot process startedStaggered AP Upgrade completed succesfullyStaggered AP Upgrade errorAborted AP Upgrade successfullyStaggered AP Upgrade not in progress, fail to abort AP upgradeTrigger abort CLI from source WLC, fail to abort AP upgradeInvalid ap upgrade report name
Explanation Rebooting given APs in staggered wayAll APs in current upgrade process rebooted with the new versionError occured in upgrade reset process. Operation aborted.Aborted AP upgrade process.Error occured in AP upgrade abort process. Operation aborted.AP upgrade abort CLI should be triggered from source WLC.Upgrade report name entered is invalid
Recommended Action Please enter a valid ap upgrade report name.


%UPGRADE-3-STAGGERED_UPGRADE_IN_PROGRESS : AP upgrade is in progress. New ap upgrade process is not allowed
Explanation If an ap upgrade process is already running, either in source or destination mode, new ap upgrade process is not allowed
Recommended Action Please wait for the current ap upgrade to finish before triggering this command.


%UPGRADE-3-MOBILITY_TUNNEL_DOWN : AP upgrade process aborted. Mobility tunnel is down for more than the permissible amount of time
Explanation If the mobility tunnel with the peer is down for more than the permissible amount of time, the current upgrade process is aborted
Recommended Action Please restore the mobility status between source and destination controllers before initiation of AP move/upgrade to destination


%UPGRADE-3-DESTINATION_NOT_READY : Destination controller not ready. Aborting upgrade process
Explanation Destination controller may be going through another AP upgrade or move
Recommended Action Please wait for the current ap upgrade to finish before triggering this command.


%UPGRADE-3-DESTINATION_NOT_RESPONDING : AP upgrade process aborted. Destination controller is not responding
Explanation Destination controller is not responding to the upgrade request message
Recommended Action Destination Controller may be down or unreachable. Please restore the mobility status between source and destination controllers before initiation of AP move/upgrade to destination


%UPGRADE-3-AP_SW_UPDATE_ERR_LOG_MSG : AP Upgrade record deleted successfullyAP Upgrade clear report error, failed to find upgrade report name : <[chars]> from upgrade report tableStaggered AP Upgrade in progress, failed to delete upgrade record with report name : <[chars]> from upgrade report tableAP SW update [chars]
Explanation Deleted AP upgrade record.Error occured in deleting record from upgrade report table. Operation aborted.Error occured in deleting record from upgrade report table. Operation aborted.AP Software Update logging
Recommended Action AP software update failed. ISSU image upgrade or SMU patching could be aborted. The user needs to initiate ISSU upgrade/SMU patch again. If the error occured during manual operation, operation can be initiated again


%UPGRADE-5-AP_SW_UPDATE_LOG_MSG : AP SW update [chars]
Explanation AP Software Update logging
Recommended Action No action required


%UPGRADE-3-AP_UPGRADE_FALLBACK_VERSION_VALIDATION_FAILURE : AP Upgrade fallback process startedAP Upgrade fallback process completed succesfullyStaggered AP Upgrade with fallback type as either reset or reset with fallback completed succesfullyAP Upgrade fallback errorSource controller is not responding or has responded with invalid software version
Explanation Starting AP upgrade fallback processAP Upgrade fallback process completedAll APs in current upgrade process rebooted with the new versionError occured in upgrade fallback process. Operation aborted.Source controller is not responding to the upgrade fallback version request message or it has responded with an invalid software version
Recommended Action Please reload source controller with valid image


%UPGRADE-3-AP_UPGRADE_FALLBACK_INIT_TIMEOUT : Timeout occurred either source controller is not responding or has responded with invalid software version. Aborting fallback process
Explanation Timeout occurred. Source controller is not responding to the upgrade fallback version request message or it has responded with an invalid software version. Aborting fallback process
Recommended Action Please reload source controller with valid image and initiate upgrade process from destination controller by using CLI: 'ap image move destination <Destination Name> <Destination IPv4/IPv6 address> <Report name>'


%UPGRADE-3-AP_UPGRADE_FALLBACK_TYPE_MSG_ERROR : AP upgrade process aborted. Failed to send fallback type message to peer
Explanation Error occured while sending fallback type message to peer. Operation aborted.
Recommended Action Please restore the mobility status between source and destination controller


URLF

%URLF-6-SITE_ALLOWED : [chars]Client [IP_address]:[dec] accessed server [IP_address]:[dec]
Explanation This message indicates that all URLs belongs to the server are allowed to be passed with out URL filter servers authentication
Recommended Action This message is just for informational purpose, it can be used to keep track of number of GET request that are sent from client to server


%URLF-4-SITE_BLOCKED : [chars]Access denied for the site '[chars]', client [IP_address]:[dec] server [IP_address]:[dec]
Explanation This message indicates that all underlying URLs of the specified domain are blocked
Recommended Action This indicates that an user has made an attempt to browse a forbidden site


%URLF-6-URL_ALLOWED : [chars]Access allowed for URL '[chars]', client [IP_address]:[dec] server [IP_address]:[dec]
Explanation This message indicates that the http GET request sent from client is allowed to be transmitted to http server
Recommended Action This is just an informational message


%URLF-4-URL_BLOCKED : [chars]Access denied URL '[chars]', client [IP_address]:[dec] server [IP_address]:[dec]
Explanation This message indicates that access to the requested URL is denied and the corresponding TCP connection is closed
Recommended Action This indicates that an user has made an attempt to browse a forbidden site


%URLF-3-SERVER_DOWN : [chars]Connection to the URL filter server [IP_address] is down
Explanation This messages indicates that a connection between the router and a url filter server is down. If more than one servers are configured the router will make use of other servers for URL authentication, otherwise it will check whether allow mode is 'on' or 'off'. If allow mode is 'on' the router will pass all the packets, otherwise it will drop all the packet and close the TCP connection.
Recommended Action The network administrator can possibly check whether the URL filter server (WebSense/N2H2) is down and restart it if required. If it still does not work then the admin may have to install a URL filter server on another system and configure the same on the router.


%URLF-3-ALLOW_MODE : [chars]Connection to all the URL filter servers are down and the allow mode is '[chars]'
Explanation This messages indicates that connection to all the URL filter servers are down. If allow mode is 'on' the router will pass all the http traffic, otherwise it will drop the http traffic and close the TCP connection
Recommended Action The network administrator can possibly check whether the URL filter server (WebSense/N2H2) is down and restart it if required. If it still does not work then the admin may have to install a URL filter server on another system and configure the same on the router.


%URLF-5-SERVER_UP : [chars]Connection to an URL filter server([IP_address]) is made, the router is returning from ALLOW MODE
Explanation This message indicates that at least one connection is up between router and a URL filter server. System is leaving out of allow mode
Recommended Action This is just an informational message


%URLF-3-URL_TOO_LONG : [chars]URL sent from [IP_address] is too long (more than [dec] bytes), possibly a fake packet?
Explanation The URL parsed from http GET request is too long, it could possibly be a fake packet, so the packet will be dropped
Recommended Action This could be a fake packet sent by the attackers


%URLF-3-MAX_REQ : [chars]The number of pending request exceeds the maximum limit [dec]
Explanation This message indicates that the number of requests pending in the router for URL authentication from URL filter server exceeds the maximum limit. In this case the http request will be dropped
Recommended Action This message is just for informational purpose


%URLF-3-RESOURCE_ALLOC_FAILED : The resource allocation failed for URL filter subsystem
Explanation This message indicates that the URLF feature is not able to allocate memory for various data structures
Recommended Action The router is running out of memory, disable the features that are not used, or check if something goes wrong


USB_TOKEN

%USB_TOKEN-3-USB_TOKEN_NOMEM : No available memory for [chars]
Explanation Memory allocation failure.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%USB_TOKEN-3-USB_TOKEN_MSG_FAILURE : Failure in handling USB Security Token insertion/removal event
Explanation Retrieving Token insertion/removal message failed in Token Daemon
Recommended Action Remove the token and insert it back. If the problem still persists, report the problem to your technical support representative along with the output of show usb device, show usb controller and show file systems commands.


%USB_TOKEN-3-USB_TOKEN_SEMCREATE_FAILURE : Failure in creating USB Security Token semaphore
Explanation Watched semaphore creation failed
Recommended Action Report the problem to your technical support representative along with the output of show usb device and show usb controller commands.


%USB_TOKEN-3-USB_TOKEN_MAX_TOKENS_INSERTED : Unavailable USB Security Token slot
Explanation Maximum number of tokens that can be supported are already inserted
Recommended Action Remove the other tokens that are not in use. And, remove and insert this token again.


USB_TOKEN_FILESYS

%USB_TOKEN_FILESYS-6-USB_TOKEN_INSERTED : USB Token device inserted: [chars].
Explanation A USB Token device has been detected.
Recommended Action Informational message only. No action required.


%USB_TOKEN_FILESYS-6-USB_TOKEN_REMOVED : USB Token device removed: [chars].
Explanation A USB Token device has been removed.
Recommended Action Informational message only. No action required.


%USB_TOKEN_FILESYS-6-REGISTERING_WITH_IFS : Registering USB Token File System [chars]: might take a while...
Explanation Registering USB Token File System is being registered.
Recommended Action Informational message only. No action required.


%USB_TOKEN_FILESYS-3-FAIL_TO_BUILD_MFD : USB Token File System failed to build MFD...
Explanation USB Token File System failed to build the Master File Directory (MFD) database.
Recommended Action Remove this token and insert it again. If the problem still persists, report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.


%USB_TOKEN_FILESYS-3-MFD_FORWARD_INCOMPATIBLE : Unable to understand MFD database of version [dec].[dec].
Explanation The version of the Master File Directory (MFD) database stored in token device is higher than what the running USB Token File System can support or understand.
Recommended Action Upgrade the USB Token File System by reloading the router with a higher version of IOS software.


%USB_TOKEN_FILESYS-6-REGISTERED_WITH_IFS : USB Token File System [chars] is registered...
Explanation USB Token File System registered successfully.
Recommended Action Informational message only. No action required.


%USB_TOKEN_FILESYS-3-FAIL_TO_REGISTER_WITH_IFS : Failed to register USB Token File System with IFS.
Explanation The process of registering USB Token File System with IOS File System (IFS) did not succeed. IFS provides a common user interface to all users of file system functionality regardless of the differences among file systems.
Recommended Action Remove this token and insert it again. If the problem still persists, report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.


%USB_TOKEN_FILESYS-3-MAX_TOKENS_INSERTED : The number of tokens exceeded the maximum that can be supported by USB Token File System.
Explanation Maximum number of tokens that can be supported by USB Token File System are already inserted.
Recommended Action Remove the other tokens that are not in use. And, remove and insert this token again. If the problem still persists, report the problem to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.


%USB_TOKEN_FILESYS-3-FAIL_TO_CREATE_TALKER : Token File System callback: failed to create token talker, token name [chars], status [dec].
Explanation USB Token File System failed to establish connection with USB Token Device Driver.
Recommended Action Remove and insert this token again. If the problem still persists, report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.


%USB_TOKEN_FILESYS-3-FAIL_TO_DESTROY_TALKER : Token File System callback: failed to destroy token talker, token name [chars], status [dec].
Explanation USB Token File System failed to destroy the connection with USB Token Device Driver.
Recommended Action Insert and remove this token again. If the problem still persists, report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.


%USB_TOKEN_FILESYS-3-UNKNOWN_TOKEN_EVENT : Token File System callback: unknown event [dec].
Explanation USB Token File System callback function received an unknown event from USB Token Device Driver.
Recommended Action Check USB ports to see if the token device is inserted or removed correctly. If the problem still persists, report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.


%USB_TOKEN_FILESYS-3-FAIL_TO_CREATE_WATCHED_BOOLEAN : Could not create a watched boolean!
Explanation USB Token File System could not create a watched boolean. This condition indicates that memory resources are being exhausted.
Recommended Action Reduce other system activities to ease memory demands or remove any token device that is not in use to free up some memory.


%USB_TOKEN_FILESYS-3-ASYNC_IO_UNEXPECTED_EVENT : Token Asynchronous I/O: Unexpected Event [dec].
Explanation Token Asynchronous I/O process received an unexpected event.
Recommended Action Report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.


%USB_TOKEN_FILESYS-3-ASYNC_IO_FAIL_TO_REQUEUE_REQUEST : Token Asynchronous I/O: failing to requeue an I/O request.
Explanation Token Asynchronous I/O process failed to requeue an I/O request.
Recommended Action Report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.


%USB_TOKEN_FILESYS-3-ASYNC_IO_FAIL_TO_GET_ARGUMENT : Token Asynchronous I/O: Could not get argument.
Explanation Token Asynchronous I/O process failed to retrieve argument.
Recommended Action Report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.


%USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_WRITING_FILE : Error writing file: file [chars], ret code [hex], [chars].
Explanation Token Asynchronous I/O process encountered I/O write failure.
Recommended Action Report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.


%USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_CREATING_FILE : Error creating file: file [chars], ret code [hex], [chars].
Explanation Token Asynchronous I/O process failed to create a file in USB token device.
Recommended Action Report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.


%USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_CREATING_DIRECTORY : Error creating directory: dir [chars], ret code [hex], [chars].
Explanation Token Asynchronous I/O process failed to create a directory in USB token device.
Recommended Action Report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.


%USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_DECODE_OP_CODE : Unrecognized I/O Op-code: [dec].
Explanation Token Asynchronous I/O process could not decode the Op-code in an I/O request.
Recommended Action Report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.


UTD

%UTD-3-UTD_COND_DEBUG_REG_FAILED : Failed to initialize Conditional Debugging for UTD
Explanation A non-fatal error occurred when attempting to Register/Initialize conditional debugging.
Recommended Action LOG_STD_ACTION


%UTD-5-UTD_POLICY_NAT_DROP_PKT : NAT packet drop, MSGDEF_LIMIT_SLOW
Explanation Packet dropped by NAT during UTD policy phase
Recommended Action Inspect NAT diagnostics to determine reason for packet drop LOG_STD_ACTION


%UTD-5-UTD_POLICY_DROP_PKT : Policy: Dropped packet from vrf [chars] [chars] %CA:[int] => %CA:[int] proto [chars] due to ([int]) [chars] ident [int] [chars], MSGDEF_LIMIT_FAST
Explanation Packet dropped during packet policy phase for the given reason
Recommended Action This message is for informational purposed only, but may indicate a security problem. LOG_STD_NO_ACTION


%UTD-4-UTD_INSPECT_DROP_PKT : Inspection: Dropped packet from vrf [chars] [chars] %CA:[int] => %CA:[int] proto [chars] due to ([int]) [chars] ident [int] [chars], MSGDEF_LIMIT_FAST
Explanation Packet dropped during packet inspection for the given reason
Recommended Action This message is for informational purposed only, but may indicate a security problem. LOG_STD_NO_ACTION


%UTD-4-UTD_DIVERT_DROP_PKT : Diversion: VPATH decapsulation dropped packet from vrf [chars] [chars] %CA:[int] => %CA:[int] proto [chars] due to ([int]) [chars] ident [int] [chars], MSGDEF_LIMIT_FAST
Explanation Packet dropped during packet reinjection
Recommended Action This message is for informational purposed only, but may indicate a security problem. LOG_STD_NO_ACTION


%UTD-4-UTD_ENCAPS_DROP_PKT : Diversion: VPATH encapsulation dropped packet from vrf [chars] [chars] %CA:[int] => %CA:[int] proto [chars] due to ([int]) [chars] ident [int] [chars], MSGDEF_LIMIT_FAST
Explanation Packet dropped while attempting to add VPATH data
Recommended Action This message is for informational purposed only, but may indicate a security problem. LOG_STD_NO_ACTION


%UTD-1-UTD_HEALTH_CHANGE : Service node changed state [chars] => [chars] ([int])
Explanation Service node and changed health status
Recommended Action Service node has changed status Green - Service node is health. No action required. Yellow - Service node not accepting new connections. Too many connections for enhanced inspection. Red - Service node is down Check IPS/IDS service node Not detected - Unknown state. Service node not detected Check IPS/IDS service node LOG_STD_ACTION


%UTD-6-UTD_DF_WHITELIST_MATCH : UTD WebFilter Domain Whitelist [**] [Domain: [chars]] [Matched Pattern: [chars]] {[chars]} %CA:[int] -> %CA:[int], MSGDEF_LIMIT_FAST/100
Explanation DNS domain matched to one of the configured whitelist patterns
Recommended Action This message is for informational purposed only, but may indicate a security problem. LOG_STD_NO_ACTION


%UTD-6-UTD_DF_BLACKLIST_MATCH : UTD WebFilter Domain Blacklist [**] [Domain: [chars]] [Matched Pattern: [chars]] {[chars]} %CA:[int] -> %CA:[int], MSGDEF_LIMIT_FAST/100
Explanation DNS domain matched to one of the configured blacklist patterns
Recommended Action This message is for informational purposed only, but may indicate a security problem. LOG_STD_NO_ACTION


%UTD-3-IPC_INVALID_MSG : UTD-Invalid request [int]
Explanation We received an invalid message from another layer of the UTD software stack.
Recommended Action 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) . If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%UTD-3-FEAT_DOWN : UTD-Invalid request [chars] ([int]) while feature is down
Explanation While the feature was not active, an invalid request was received from another layer of the UTD software stack.
Recommended Action 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) . If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%UTD-3-FEAT_CTX_DOWN : UTD-Invalid request [chars] ([int]) while context is down
Explanation While the feature context was not active, an invalid request was received from another layer of the UTD software stack.
Recommended Action 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) . If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%UTD-3-IPC_OPEN_REPLY : UTD-IPC Open Reply failed, request [int]
Explanation For a request from upper UTD software stack layers it was not possible to open the reply buffer.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%UTD-3-IPC_NORES : UTD-No space for the IPC reply, size [int], request [int]
Explanation For a request from upper UTD software stack layers it was not possible to allocate space for a reply for the specified size.
Recommended Action 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) . If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%UTD-3-IPC_INVALID_MSG_LEN : UTD-Invalid IPC length, [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid IPC message length
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%UTD-3-IPC_SEND_FAILED : UTD-IPC [chars] [int] send failed [int]
Explanation IPC message send failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%UTD-2-IPC_INIT_FAILED : UTD-IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the UTD feature failed. This will cause the feature to not function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%UTD-2-IPC_FAILURE : UTD-IPC message [chars] handler failed, rc [int]
Explanation An IPC message handler for the UTD feature failed. This will cause the feature to not function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


UTIL through VOICE_HA

UTIL

%UTIL-3-RANGEINCON : internal inconsistency [dec] [hex]
Explanation A fatal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%UTIL-3-RANGENULLINPUT : null pointer input to range function
Explanation An attempt was made to access a range function with a NULL pointer. The range list creation failed.
Recommended Action 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-0-ITEMLIST_RESIZE : An attempt was made to resize an itemlist but not enough memory is available
Explanation An attempt was made to resize itemlist memory to be larger than the memory available. Itemlists are often used when showing interface statistics. This event is unexpected and may be an indication of memory corruption.
Recommended Action Note any recent commands that may have triggered this error. Copy the error message and traceback exactly as it appears, and report it to your technical support representative.


%UTIL-3-RADIXTREE : Data structure error--[chars]
Explanation A software error occurred, resulting in a data structure inconsistency.
Recommended Action 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-TREE : Data structure error--[chars]
Explanation A software error occurred, resulting in a data structure inconsistency.
Recommended Action 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-6-RANDOM : A pseudo-random number was generated twice in succession
Explanation A pseudo-random number generator produced the same number twice in succession.
Recommended Action 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.


%UTIL-3-IDTREE_TRACE : [chars]
Explanation A software error occurred, resulting in a data structure inconsistency.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%UTIL-3-IDTREE_NOTRACE : [chars]
Explanation A software error occurred, resulting in a data structure inconsistency.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%UTIL-3-DLL : Data structure error -- [chars]
Explanation A software error occurred, resulting in data structure inconsistency.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


VASI

%VASI-2-DB_ENTRY_ALLOC_FAIL : VASI pair db entry allocation for interface [chars] failed
Explanation VASI pair database error. Memory chunk allocation for VASI pair database entry has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute 'show proc memory' command.


%VASI-2-DB_INSERT_FAIL : VASI pair db entry add for interface [chars] failed
Explanation VASI pair database error. Insertion of a new entry into VASI pair database has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks, look for memory corruption causes, verify correct database management. Execute 'show proc memory' command.


%VASI-2-DB_DELETE_FAIL : VASI pair db entry delete for interface [chars] failed
Explanation VASI pair database error. Removal of entry from VASI database has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks, look for mamory corruption causes and check for correct database management. Execute 'show proc memory' command.


%VASI-2-DB_ENTRY_FREE_FAIL : VASI pair entry free failed
Explanation VASI pair database error. Memory chunk free of VASI pair database entry has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute 'show proc memory' command.


%VASI-2-DB_ALLOC_FAIL : VASI pair db allocation failed
Explanation VASI pair database error. Memory chunk creation for VASI pair database has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute 'show proc memory' command.


%VASI-2-DB_DESTROY_FAIL : VASI pair database destroy failed
Explanation VASI pair database error. Memory chunk destroy has failed for VASI pair database.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute show proc memory command.


VDSL_DAEMON

%VDSL_DAEMON-3-NOPROC : VDSL Daemon [chars] SM create event process failed
Explanation The router does not have enough memory run this VDSL/ADSL feature
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VDSL_DAEMON-3-NOMEM : VDSL Daemon [chars] malloc failed : out of memory
Explanation The router does not have enough memory installed to run this VDSL/ADSL feature
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VDSL_DAEMON-3-MALLOCFAIL : There is not enough main memory for the new VDSL [chars] firmware images on flash
Explanation The router failed to malloc a buffer for the firmware imageson the flash. More DRAM is required for the feature which allows specificVDSL firmware images on the flash to replace the VDSL firmware imagesembedded in IOS.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VDSL_DAEMON-3-INITFAIL : VDSL Daemon [chars] init failed.
Explanation The VDSL module hardware may be bad
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VDSL_DAEMON-3-INVALID_DS : Daemon [chars] invalid vdsl instance.
Explanation Encounter an invalid vdsl instance
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VDSL_DAEMON-4-QUEUE_EMPTY : Daemon [chars] configuration queue is empty.
Explanation program is unable to send a message to the queue process.
Recommended Action nothing


%VDSL_DAEMON-4-INVALID_CDB : Invalid daemon [chars] controller [chars].
Explanation Encounter an invalid daemon cdb instance.
Recommended Action nothing


%VDSL_DAEMON-3-FPGA_FAIL : VDSL FPGA Download failed.
Explanation The VDSL module hardware may be bad
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VDSL_DAEMON-3-MODEMRESET : VDSL Modem reset. [chars]
Explanation The VDSL module is under reset.
Recommended Action 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) . If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%VDSL_DAEMON-4-TRAINMODE_NOT_SUPPORTED : [chars] transport mode is not supported on [chars].
Explanation Only ATM is supported on ADSL and PTM/Ethernet is supported on VDSL2).
Recommended Action Change DSLAM profile to select the correct mode for CPE


%VDSL_DAEMON-3-VDSL_CMD_ADD_FAIL : VDSL [chars] add failed.
Explanation adding a command exceeds the maximum number of commands allowed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VDSL_DAEMON-3-FIRMWARE_WARN : Need to reload IOS for VDSL PHY firmware file change to take effect
Explanation The old phy firmware is used until IOS is reload
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VDSL_DAEMON-4-MODE_SWITCH : Please save the configuration and reload the Router due to the ATM-PTM mode change on vdsl 0 controller
Explanation Operating mode switch between ATM and PTM mode require reload
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VDSL_DAEMON-3-VDSL_LINE_UPDOWN : Controller [chars], line [dec], changed state to [chars]
Explanation VDSL Line changed state
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


VFI

%VFI-4-CONFIG : [chars]
Explanation Invalid VFI configuration data passed.
Recommended Action No action is required.


%VFI-3-ILLEGAL : [chars]
Explanation An illegal event has been processed by the xconnect subsystem.
Recommended Action No action is required.


%VFI-6-VFI_STATUS_CHANGED : Status of VFI [chars] changed from [chars] to [chars]
Explanation VFI status has changed
Recommended Action No action is required.


VIDB

%VIDB-3-FORKFAIL : Failed to fork process for [chars].
Explanation Quite likely, we ran out of memory. Other explanations are possible.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIDB-3-FREETIMENOTSET : Value not specified for vidb forcible free time by platform.
Explanation Platform has requested for delayed vidb recycling support, but hasn't specified any value for forcible free time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


VINES

%VINES-2-CORRUPTENTRY : Detected a corrupted entry in the [chars] table
Explanation The VINES code detected that an internal table entry was corrupted.
Recommended Action 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-INVALIDPATH : Bad [chars] in path for neighbor entry %z
Explanation 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.
Recommended Action 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-INVALIDROUTE : Bad [chars] in route for server entry %Z
Explanation 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.
Recommended Action 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-CONSISTENCY : Error [chars]
Explanation 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.
Recommended Action 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-NOBUFFERS : No buffers available for [chars]
Explanation There were no buffers available to send a VINES service query or reply.
Recommended Action 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-ENCAPFAILED : Encapsulation failed for %#z via %#z on [chars]
Explanation VINES fast switching encountered an encapsulation failure when building a cache entry for a neighbor.
Recommended Action 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-CACHEFAILED : Cannot build cache entry ([dec] bytes) for %#z on [chars]
Explanation 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.
Recommended Action 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-CACHEUNSUPP : Caching of [chars] not supported on [chars]
Explanation The cache population routing for VINES fast switching was called for an interface that does not support VINES fast switching.
Recommended Action 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-DUPADDR : Duplicate address detected on interface [chars]
Explanation The router detected that its VINES address is being used by another router.
Recommended Action 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-BADPARAM : [chars] called with [chars] parameter set to [chars]
Explanation One of the VINES lookup functions was called with an illegal argument.
Recommended Action 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-BADTIMER : RTP timer for [chars] was found disabled, and was reset
Explanation An internal interface timer is not running. This condition usually occurs after an interface is reset.
Recommended Action No action is required. The system automatically restarts the timer.


%VINES-6-IPCNOROUTINE : IPC port [dec] registered without an upcall ([chars])
Explanation 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.
Recommended Action 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.


%VINES-6-RPCNOSERVICE : IPC port [dec] registered without a service
Explanation 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.
Recommended Action 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-RTNNOTFOUND : [chars] service [chars] routine not found while [chars]
Explanation There is an inconsistency in the active VINES service description data structures. A service handler routine cannot find the description of its own service.
Recommended Action 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-FNNOTFOUND : [chars] service [chars] routine missing [chars] vector
Explanation There is an inconsistency in the static VINES data structures for handling application-layer packets.
Recommended Action 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-2-NOVENCAP : Encapsulation failed on [chars] for address %#z
Explanation The VINES code tried to send a packet on an interface that does not have a new encapsulation routine for outbound packets.
Recommended Action 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.


VIRT_SERVICE

%VIRT_SERVICE-3-INIT_FAIL : Failed to initialize required virtual service object: [chars]
Explanation During the initialization of the resources required for the virtual service feature, a memory allocation failure occurred. This has prevented the virtual service feature from being enabled.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-ROMMON_UNSUPPORTED : ROM monitor configuration does not support virtualization
Explanation Virtualization is not supported by the current ROM monitor configuration. Verify both the ROM monitor version and ROM monitor variable ENABLE_VTX are correct to enable virtualization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-STBY_ROMMON_UNSUPPORTED : Standby ROM monitor configuration does not support virtualization
Explanation Virtualization is not supported by the current ROM monitor configuration on the standby. Verify both the ROM monitor version and ROM monitor variable ENABLE_VTX are correct to enable virtualization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-ACTIVATE_FAIL : Failed to send virtual service [chars] activate message
Explanation During the creation and transmission of the virtual service activate TDL message a failure occurred. The message was not successfully sent and therefore the virtual service was not activated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-DEACTIVATE_FAIL : Failed to send virtual service [chars] deactivate message
Explanation During the creation and transmission of the virtual service deactivate TDL message a failure occurred. The message was not successfully sent and therefore the virtual service was not deactivated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-UNPROVISION_FAIL : [chars]: [chars]
Explanation During the unprovision of the named virtual service, an unexpected failure occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-STBY_PKG_PATH : Failed to [chars] required by virtual service [chars] on standby
Explanation Specified package definition file was not found on standby. Configuration was accepted. Copy package definition file to standby at earliest convenience.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-4-SWITCHOVER_ACTIVATE : Virtual service [chars] will not be activated following a switchover
Explanation Following a switchover, this virtual service will not be activated as there is an issue with its package definition file. Copy package definition file to standby at earliest convenience.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-PKG_PATH : Failed to [chars] required by virtual service [chars]
Explanation Specified package definition file was not found following a switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-PKG_PATH_ACTIVATE : Failed to [chars]. Virtual service [chars] will not be activated
Explanation Specified package definition file was not found following a switchover. Unable to activate virtual service without specified package definition file present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-INVALID_APPLIANCE_TIMEOUT : A response timeout occurred for an invalid virtual service
Explanation An unexpected condition occurred where the virtual service context pointer in the expired timer was set to NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-UNKNOWN_APPLIANCE_TIMEOUT : A response timeout occurred for unknown virtual service [chars]
Explanation A response timeout occurred for a virtual service that is no longer in the virtual service database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-RESPONSE_TIMEOUT : Virtual service [chars] timed out waiting for a response from Virt-manager
Explanation Failed to receive a response message from Virt-manager for last activation operation performed on the named virtual service. The virtual service activation state was marked as deactivated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-UPGRADE_TIMEOUT : Virtual service [chars] timed out waiting for a package upgrade response from Virt-manager
Explanation Failed to receive a response message from Virt-manager for last upgrade operation performed on the named virtual service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-SEND_RF_MSG : Failed to send RF message to peer - [chars]
Explanation An unexpected condition occurred where an attempt to send an RF message to peer failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-INVALID_RF_MSG : Received an invalid RF message type from peer
Explanation An unexpected condition occurred where an invalid message type was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-UNKNOWN_RF_MSG : Received an unknown RF message type ([dec]) from peer
Explanation An unexpected condition occurred where an unknown timer event was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-UNKNOWN_TIMEOUT_TYPE : A response timeout occurred for an unknown timeout type ([dec])
Explanation An unexpected condition occurred where an unknown timeout type was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-UNKNOWN_TIMER_EVENT : A timer event occurred for an unknown timer event ([dec])
Explanation An unexpected condition occurred where an unknown timer event was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-5-ACTIVATION_STATE : [chars] [chars]
Explanation The activation state of the named virtual service has changed as notified by Virt-manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-3-RESET : Virtual service [chars] reset
Explanation An unexpected condition has occurred where Virt-manager has reported that it detected the named virtual service reset. This virtual service is not configured to be activated and as such, no attempt to reactivate it will be made.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-5-RESET_REACTIVATE : Virtual service [chars] reset and will be reactivated
Explanation Virt-manager has reported that it detected the named virtual service reset. An attempt will be name to reactivate this virtual service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VIRT_SERVICE-5-INSTALL_STATE : [chars] [chars]
Explanation The installation state of the named virtual service has changed as notified by Virt-manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


VLAN

%VLAN-5-PRIMARY_LINK_NOT_IN_EC : Warning: VLAN [int]'s main interface is not the channel group of primary=[chars]Per-VLAN manual load-balancing will not take effect until channel-group is configured under the primary interface.
Explanation The interface configured as primary is not a memberlink in the port channel.
Recommended Action Verify the configuration.


%VLAN-5-SECONDARY_LINK_NOT_IN_EC : Warning: VLAN [int]'s main interface is not the channel group of secondary=[chars]Per-VLAN manual load-balancing will not take effect until channel-group is configured under the secondary interface.
Explanation The interface configured as secondary is not a memberlink in the port channel.
Recommended Action Verify the configuration.


%VLAN-3-INTERFACE_NOT_PRESENT : The [chars] link [chars] does not exist. Sub-interface: [chars] VLAN-Id: [int]
Explanation This message appears when the below command is issued (under port-channel sub-interface) with the unknown primary and/or secondary links. encap dot1q <vlan-id> primary <interface> secondary <interface> The interface specified in the command is not available at present. The card might have been physically removed or may not have been inserted properly.
Recommended Action Verify if the interface shows up, using the command - show ip int brief. Please insert the card in case it is removed and run the command again once the card comes up.


VMAN

%VMAN-2-INVALID_PACKAGE : Virtual Service[chars]
Explanation The package definition file for the named virtual service has failed to be validated and the virtual service will not run
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. The most likely cause would be that the package file has been corrupted during file transfer. The suggested action would be to redo the file transfer.


%VMAN-2-INVALID_ACT_MSG : Virtual Service[chars]
Explanation The virtual service activate message was received, however, the data it contained could not be interpreted
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-INVALID_DEACT_MSG : Failed to process virtual service deactivate message
Explanation The virtual service deactivate message was received, however, the data it contained could not be interpreted
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-CREATE_VIRT_INST_ENTRY : Virtual Service[chars]
Explanation The request to create a DB entry for the named virtual service failed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-PROC_INT_LIST : Virtual Service[chars]
Explanation The interface list embedded in the activate request for the named virtual service could not be processed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-ALLOC_VIRT_INST_RCS : Virtual Service[chars]
Explanation A memory allocation request failed to allocate a data structure required to activate the virtual service.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-START_FAILED : Virtual Service[chars]
Explanation The named virtual service failed to start.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-PROCESS_PKG_DEF : Virtual Service[chars]
Explanation The virtual service package for the named virtual service has failed to be validated and the virtual service will not run.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-DEFER_VIRT_INST_PROC : Virtual Service[chars]
Explanation The final activation processing failed to successfully defer.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-COMMIT_VIRT_INST_RCS : Virtual Service[chars]
Explanation The request to commit the resources required by the named virtual service failed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-INSERT_VIRT_INST_ENTRY : Virtual Service[chars]
Explanation Inserting the named virtual service into the virtual service DB tracked by Virt-manager failed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-VIRT_INST_INTERFACE : Virtual Service[chars]
Explanation The number of configured virtual port group interfaces must match the number of Ethernet Network Interfaces defined in the machine definition file
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-VIRT_INST_MEMORY : Virtual Service[chars]
Explanation The virtual service requires physical memory in excess of the free memory available to virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-VIRT_INST_DISK : Virtual Service[chars]
Explanation The virtual service requires Disk Storage in excess of the Free Disk Storage available to virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-INCONSISTENT_MEM_CONFIG : Virtual Service[chars]
Explanation The virtual service machine definition file is inconsistent in the specification of required memory via the <memory> and <currentMemory> nodes.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-MEMORY_LIMIT_WARN : Virtual service ([chars])[chars] defines [int] MB of Memory exceeding the maximum [int] MB.
Explanation The virtual service machine definition file is requesting more memory for the specified profile, than the system has available for virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-MEMORY_LIMIT : Virtual Service[chars]
Explanation The virtual service machine definition file is requesting more memory than the system has available for virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-VCPU_LIMIT : Virtual Service[chars]
Explanation The virtual service machine definition file is requesting more VCPUs than the system has reserved for virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-DISK_IMAGE_PATH : Virtual Service[chars]
Explanation The virtual service machine definition file contains an invalid disk image path for one of the disk devices. This may be a Harddisk, CDROM or USB storage device.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-5-VIRT_INST : LOG FROM VIRTUAL SERVICE [chars]: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required


%VMAN-2-VIRT_INST_CRIT : VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required


%VMAN-3-VIRT_INST_ERR : VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required


%VMAN-4-VIRT_INST_WARN : VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required


%VMAN-5-VIRT_INST_NOTICE : VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required


%VMAN-6-VIRT_INST_INFO : VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required


%VMAN-7-VIRT_INST_DEBUG : VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required


%VMAN-2-VIRT_INST_LOG_UNTHROTTLE : Failed to unthrottle the log for virtual service [chars]
Explanation The named virtual service had sent overwhelming sys log messages and its log had been throttled as a result, but system has failed to unthrottle it for some reason.
Recommended Action For debugging collect the virt-manager logs and scan them for the cause.


%VMAN-2-VIRT_INST_STATE : Virtual Service[chars]
Explanation The named virtual service has failed. It is no longer running either because the guest OS has failed, the guest OS has shut down the machine or the emulator has failed.
Recommended Action An attempt at restarting the virtual service can be made from the IOS configuration by doing a no activate/activate. For debugging collect the Virt-manager logs and scan them for the cause.


%VMAN-2-FIND_VIRT_INST_ENTRY : Failed to find virtual service with id [int] in the Virt-manager DB
Explanation The virtual service with the ID named could not be located in the Virt-manager DB.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-REMOVE_VIRT_INST_ENTRY : Virtual Service[chars]
Explanation Removing the named virtual service from the virtual service DB tracked by Virt-manager failed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-SET_VTX_ROMVAR_STRING : Failed to set ROM monitor variable ENABLE_VTX: Invalid string format: [chars]
Explanation Failed to set ENABLE_VTX rom monitor variable due to invalid string format.
Recommended Action Verify format of string from error message.


%VMAN-2-SET_VTX_ROMVAR_SPACE : Failed to set ROM monitor variable ENABLE_VTX: No space in table
Explanation Failed to set ENABLE_VTX ROM monitor variable due to no space in Monitor Variable Table.
Recommended Action Verify number of entries in Monitor Variable Table.


%VMAN-5-AUX : Virtual Service[chars]
Explanation The AUX login to a virtual service may allow the user access to system functions that may not have been tested or may interact with the system in unintended ways. Use with caution.
Recommended Action No action is required


%VMAN-2-INVALID_UNPROV_MSG : Failed to process virtual service unprovision message
Explanation The virtual service unprovision message was received, however, the data it contained could not be interpreted
Recommended Action Enable the Virt-manager trace logs and repeat the activation followed by deactivation and then unprovision of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-VCPU_INVALID : Virtual Service[chars]
Explanation The virtual service machine definition file is requesting invalid VCPU value.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-CPUSHARES_LIMIT : Virtual Service[chars]
Explanation The virtual service machine definition file is requesting more CPU shares than the system has available for virtual services.
Recommended Action Deactivate any other virtual services to free up CPU share resources and activate this virtual service. If that does not address the problem, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-MORETHANONE_CPUTUNES_CONFIG : Virtual Service[chars]
Explanation The virtual service machine definition file is requesting more than one CPU tunes parameter.
Recommended Action Use a different valid machine definition file for the virtual service. If the problem persists, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-INCONSISTENT_CPUTUNES_CONFIG : Virtual Service[chars]
Explanation The virtual service machine definition file is requesting invalid CPU tunes parameter.
Recommended Action Use a different valid machine definition file for the virtual service. If the problem persists, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-CPUTUNES_SHARES_LIMIT : Virtual Service[chars]
Explanation The virtual service machine definition file is requesting more CPU shares than the system has available for virtual services.
Recommended Action Deactivate any other virtual services to free up CPU share resources and activate this virtual service. If that does not address the problem, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-CPUTUNES_INTERNAL_ERROR : Virtual Service[chars]
Explanation Virt-manager and its associated infrastructure experienced an internal error.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-MACHINE_TYPE_NOT_SUPPORTED : Virtual Service[chars]
Explanation The virtual service cannot be activated as the machine type specified is not supported
Recommended 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.


%VMAN-2-INSTALL_FAILURE : Virtual Service[chars]
Explanation The installation of the virtual service failed.
Recommended Action Enable the Virt-manager trace logs and repeat the installation of the virtual service. Collect the Virt-manager logs and scan them for the cause.


%VMAN-2-INSTALL_MEDIA_RETRY : VMAN, VM install media still unavailable.[chars]
Explanation The install media was not detected. Waiting for udev to complete install media(harddisk) detection.
Recommended Action After VMAN exceeds the maximum retry limit, verify if install media (harddisk) is accessible and retry the installation again.


%VMAN-2-VIRT_INST_MGMT_INTERFACE : Virtual service [chars] has no management interface defined but it is configured in CLI.
Explanation A management interface is configured but none is defined.
Recommended Action Deactivate the virtual service, remove the management interface configuration CLI, and reactivate the virtual-service.


%VMAN-2-GENERAL_FAILURE : Virtual Service[chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required


%VMAN-4-UPDATE_WARNING : Virtual Service[chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required


%VMAN-2-MACH_PARSE_FAILURE : Virtual Service[chars]
Explanation The named virtual service has an invalid parameter specified in the .xml file inside the .ova package
Recommended Action Fix the .xml file inside the .ova package to have valid values. Then retry installing and activating it


%VMAN-3-SDWRAP_ERR : Description: [chars], errcode: [dec]
Explanation Debug infrastructure error
Recommended Action Collect the Virt-manager logs and scan them for the cause.


%VMAN-3-PSS_ERR : Purpose: [chars], URI: [chars], errcode: [dec]
Explanation Persistent Storage Service handling error
Recommended Action Collect the Virt-manager logs and scan them for the cause.


%VMAN-3-PSS_SNAPSHOT_ERR : Source URI: [chars], Destination URI: [chars], errcode: [dec]
Explanation Persistent Storage Service snapshot error
Recommended Action Collect the Virt-manager logs and scan them for the cause.


%VMAN-4-PACKAGE_SIGNING_LEVEL_CHANGED : Package signing level changed from allow '[chars]' to allow '[chars]'
Explanation The package certificate signing level global setting has been changed via configuration under the virtual-service global sub-mode.
Recommended Action Ensure that this setting has been changed as expected by an authorized user.


%VMAN-5-PACKAGE_SIGNING_LEVEL_ON_INSTALL : Package '[chars]' for service container '[chars]' is '[chars]', [chars] '[chars]'
Explanation A service container software package with the certificate signing level described is being installed.
Recommended Action Take note of the service container and software package. Verify the software package is expected to be (un)signed as described and has the appropriate contents. Uninstall the package if unsure of the package origins.


%VMAN-2-NETWORK_CONFIG_ERROR : Virtual Service[chars]
Explanation A network configuration error has been detected for the named virtual service.
Recommended Action No action is required


%VMAN-2-INSTALL_LOG : [chars] [chars] [chars] [chars]
Explanation The installation log of the named virtual service, is to provide more information about long running operation, that could affect the control of CLI
Recommended Action No action is required


%VMAN-2-UPGRADE_LOG : [chars] [chars] [chars] [chars]
Explanation The upgrade log of the named virtual service, is to provide more information about long running operation, that could affect the control of CLI
Recommended Action No action is required


%VMAN-2-INSTALL_STATE : [chars] '[chars]'[chars] [chars]
Explanation The installation state of the named virtual service has changed as notified by Virt-manager.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. In the successful case, this notification can be ignored.


%VMAN-2-UNINSTALL_ALL_VMS : All Virtual Services are being uninstalled [chars][chars] [chars]
Explanation All virtual services are being uninstalled by Virt-manager.
Recommended Action Examine the reason given as to why all virtual services are being uninstalled for more information. If the reason indicated is due to some error condition, check Virt-manager's logs for the cause of the failure.


%VMAN-2-ACTIVATION_STATE : [chars] '[chars]' [chars] [chars]
Explanation The activation state of the named virtual service has changed as notified by Virt-manager.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. In the successful case, this notification can be ignored.


%VMAN-4-WATCHDOG_TIMER : [chars] '[chars]' [chars] [chars]
Explanation The watchdog timer configured for the named virtual service has expired.
Recommended Action Check any logs produced by the virtual service to determine the cause.


%VMAN-2-HA_SYNC_ERR : [chars] '[chars]' [chars]
Explanation The ha-sync persistent storage disk for the virtual service cannot be watched for sync to standby RP.
Recommended Action Collect the Virt-manager logs and scan them for the cause.


%VMAN-4-VIRT_SERV_LIBVIRTD_WARN : VMAN not able to connect to the libvirt daemon after '[dec]' attempts
Explanation VMAN has been unable to connect to the libvirt daemon. Virtualization services will not be available until this connection is made.
Recommended Action Collect the logs produced by 'show virt tech'


%VMAN-2-DEACT_FOR_ISSU : [chars] Max ([int]s)
Explanation An ISSU event is pending. Any active VMs will be automatically deactivated to allow ISSU preprocessing to validate the environment. Any ISSU-deactivated VMs will be automatically restarted if the ISSU is cancelled.
Recommended Action None. Allow the ISSU to continue and the VMs will restart when the ISSU completes or cancel the ISSU and vman will automatically


%VMAN-2-RESET_FORCE : Virtual Services non-recoverable reset command processed
Explanation A 'virtual service reset force' command has been entered and processed. This action initiates a cleanup of last resort. Occasionally a VM will get into an unrecoverable state that prevents it from activating but also from uninstalling. This is a rare event but when it happens the only resort may be to remove the .conf control file and reboot, which forces a cleanup of all previously installed VM files and artifacts. Note that once this command is used, current VMs are considered to be in an unstable or unpredictable state, and all future install, uninstall, upgrade, and activation commands will be blocked.
Recommended Action Once the command is entered and accepted, there is no recourse but to restart the system.


%VMAN-2-MOVE_STATE : [chars] '[chars]' [chars] [chars]
Explanation The move of the core or log file of the named virtual service has as been successful or failed as notified by Virt-manager.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. In the successful case, this notification can be ignored.


%VMAN-2-RSYNC_STATE : [chars] [chars] [chars] [chars]
Explanation VMAN tries to remote sync the virtual-instance configuration file and the OVA repository to all online nodes. If rsync fails even after consecutive retries, this notification would be raised.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. Check for the rsync error code and root cause the same.


%VMAN-2-HA_SYNC_THREAD_STATE : HA remote sychronize thread has failed and exited.
Explanation VMAN tries to remote sync the OVA repository to all online nodes using a separate thread. If that thread fails, this notification would be raised.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. Check for the pthread error msg and root cause the same.


%VMAN-2-HA_STATE : [chars] [chars] [chars] [chars]
Explanation VMAN tries to detect the role/slot of various nodes on HA events from the platform. If any of those event callbacks fail, this notification would be raised.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same.


%VMAN-2-HA_SWITCHOVER_STATE : [chars] [chars] [chars] [chars]
Explanation VMAN HA switchover state related messages for a virtual-service whilst it is being recovered on newly active RP after a HA switchover.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same.


%VMAN-4-HA_SYNC_NEEDED : If using the guest shell, please use 'guestshell sync' if you want to preserve state on standby in case of supervisor switchover
Explanation Message notifying user that he needs to manually synchronize the Virtual service contents to standby supervisor in order to preserve these contents in case of a supervisor switchover. Currently only applicable to the guest shell
Recommended Action User can type the 'guestshell sync' command on active supervisor to synchronize it's contents to the standby supervisor if desired.


%VMAN-2-RESIZE_OPER_STATE : Virtual service '[chars]' [chars][chars] to '[int]' [chars]
Explanation VMAN attempts to resize various VM parameters like rootfs size, CPU share, memory if requested by user. Success/failure status messages for these resize operations are communicated by this syslog.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same.


%VMAN-2-GUESTSHELL_ENABLED : The guest shell has been enabled. The command '[chars]' may be used to access it, '[chars] destroy' to remove it.
Explanation Informs the user that the guest shell virtual service has been enabled (which is done by default).
Recommended Action The user may use or remove the guest shell with the commands specified.


%VMAN-5-PERMISSION_DENIED : Virtual Service '[chars]' is not owned by client IOSd
Explanation An attempt was made to modify a virtual-service that is not owned by by the client. The request was rejected.
Recommended Action No action is required.


VOICE_HA

%VOICE_HA-7-STATUS : [chars].
Explanation VOICE HA INFRA info/status messages.
Recommended Action None


%VOICE_HA-1-SELF_STATE_PROTECTED : [chars] RG[[dec]] [chars].
Explanation VOICE HA functionality has been disabled in this router due to call checkpointing failure.
Recommended Action Router need immediate reload.


%VOICE_HA-1-INTERFACE_DOWN : [chars] RG[[dec]] [chars].
Explanation Interface went down
Recommended Action


%VOICE_HA-5-PEER_STATE_READY : [chars] RG[[dec]] VOICE HA Peer exiting from PROTECTED state.
Explanation VOICE HA functionality is enabled on peer.
Recommended Action


%VOICE_HA-5-PEER_STATE_PROTECTED : [chars] RG[[dec]]. HA functionality disabled for Voice.
Explanation VOICE HA functionality is disabled on the peer. due to call checkpointing failure.
Recommended Action Peer Router need immediate reload.


%VOICE_HA-2-BULK_SYNC_ERR : [chars].
Explanation VOICE HA INFRA encountered a bulk-sync error.
Recommended Action Collect requested data/traceback and forward to the voice-ha component.


%VOICE_HA-2-SYM_DATA_COLLECT_ERR : UC-INFRA HA module [chars] reported DATA COLLECT failure (CID:[dec]) with error code [dec].
Explanation Specified HA module reported error during call leg data collection.
Recommended Action Collect requested data/traceback and forward to the appropriate DDTS-component/module owner of the specified HA module for investigation.


%VOICE_HA-3-DATA_COLLECT_ERR : ([chars]): HA Module [chars] reported DATA COLLECT failure (mainst ID:[dec], CID:[dec]).
Explanation Specified HA module reported error during call leg data collection.
Recommended Action Collect requested data and forward to the appropriate DDTS-component/module owner of the specified HA module for investigation.


%VOICE_HA-2-SYM_DATA_RECREATE_ERR : UC-INFRA HA module [chars] reported RECREATE failure (CID:[dec]) with error code [dec].
Explanation Specified HA module reported error during call leg re-create.
Recommended Action Collect requested data/traceback and forward to the appropriate DDTS-component/module owner of the specified HA module for investigation.


%VOICE_HA-3-DATA_RECREATE_ERR : ([chars]): HA Module [chars] reported [chars] RECREATE failure (mainst ID:[dec], CID:[dec]).
Explanation Specified HA module reported error during call leg re-create.
Recommended Action Collect requested data and forward to the appropriate DDTS-component/module owner of the specified HA module for investigation.


%VOICE_HA-1-DATA_RECREATE_ERR_THRESHOLD : ([chars]): RECREATE_ERR have exceeded threshold counts; performance degradation may occur. Most recent error: Module [chars] reported [chars] RECREATE failure (mainst ID:[dec], CID:[dec]) on STANDBY.
Explanation Specified HA module reported error during call leg re-create.
Recommended Action Collect requested data and forward to the appropriate DDTS-component/module owner of the specified HA module for investigation.


%VOICE_HA-2-SWITCHOVER_IND : [chars].
Explanation VOICE HA detected a failover transition on the STANDBY to become the new ACTIVE.
Recommended Action Verify calls on the new ACTIVE. Peer needs to be in STANDBY mode before the next failover.


VOICE_IEC through WANPHY

VOICE_IEC

%VOICE_IEC-3-GW : [chars]: Internal Error ([chars]): IEC=[dec].[dec].[dec].[dec].[dec].[dec] on callID [dec] [chars]
Explanation An internally-detected error has caused a voice call to be released or terminated. An Internal Error Code (IEC) has been generated to report the error. This IEC will be logged in the accounting record for this call. In addition it is being reported through syslog because of the voice iec syslog configuration.
Recommended Action Refer to the IEC Error Message Decoder at http://www.cisco.com/univercd/cc/td/doc/product/voice/vtgemd.htm and enter the IEC, or enter the show voice iec description IECvalue command, with IECvalue being the value of the IEC that was received, for more information on the details of this error. It is possible some debugging actions might also indicate the cause of the error.


%VOICE_IEC-3-GK : [chars]: Internal Error ([chars]): IEC=[dec].[dec].[dec].[dec].[dec].[dec] on GUID [chars] confid [chars]
Explanation An internally-detected error has caused a voice call to be released or terminated. An Internal Error Code (IEC) has been generated to report the error. This IEC will be logged in the accounting record for this call. In addition it is being reported through syslog because of the voice iec syslog configuration.
Recommended Action Refer to the IEC Error Message Decoder at http://www.cisco.com/univercd/cc/td/doc/product/voice/vtgemd.htm and enter the IEC, or enter the show voice iec description IECvalue command, with IECvalue being the value of the IEC that was received, for more information on the details of this error. It is possible some debugging actions might also indicate the cause of the error.


%VOICE_IEC-3-EXT : Externally-generated Internal Error Code received: [dec].[dec].[dec].[dec].[dec].[dec]
Explanation Some external entity has initiated the termination of a voice call. It has signalled its Internal Error Code to this gateway, to be reported in the accounting record for this call. In addition, it is being reported through syslog because of the voice iec syslog configuration.
Recommended Action Refer to the IEC Error Message Decoder at http://www.cisco.com/univercd/cc/td/doc/product/voice/vtgemd.htm and enter the IEC, or enter the show voice iec description IECvalue command, with IECvalue being the value of the IEC that was received, for more information on the details of this error. It is possible some debugging actions might also indicate the cause of the error.


VOICE_REG_CRED

%VOICE_REG_CRED-6-ADDED : VOICE-REG-POOL-[dec] Credentials of new user ([chars]) added to voice register pool
Explanation Credentials on Phone Pool Added
Recommended Action No action is required.


%VOICE_REG_CRED-6-UPDATED : VOICE-REG-POOL-[dec] Credentials of user ([chars]) updated in voice register pool
Explanation Credentials on Phone Pool Updated
Recommended Action No action is required.


%VOICE_REG_CRED-6-REMOVED : VOICE-REG-POOL-[dec] Credentials of user ([chars]) removed from voice register pool
Explanation Credentials on Phone Pool Removed
Recommended Action No action is required.


%VOICE_REG_CRED-6-AUTOREG_PWD_ADDED : Password added to auto register
Explanation AutoRegister Password Added
Recommended Action No action is required.


%VOICE_REG_CRED-6-AUTOREG_PWD_UPDATED : Password updated in auto register
Explanation AutoRegister Password Updated
Recommended Action No action is required.


%VOICE_REG_CRED-6-AUTOREG_PWD_REMOVED : Password removed from auto register
Explanation AutoRegister Password Removed
Recommended Action No action is required.


%VOICE_REG_CRED-6-ATA_IVR_PWD_ADDED : VOICE-REG-POOL-[dec] ATA IVR Pin added to voice register pool
Explanation ATA IVR Pin Added
Recommended Action No action is required.


%VOICE_REG_CRED-6-ATA_IVR_PWD_UPDATED : VOICE-REG-POOL-[dec] ATA IVR Pin updated in voice register pool
Explanation ATA IVR Pin Updated
Recommended Action No action is required.


%VOICE_REG_CRED-6-ATA_IVR_PWD_REMOVED : VOICE-REG-POOL-[dec] ATA IVR Pin removed from voice register pool
Explanation ATA IVR Pin Removed
Recommended Action No action is required.


%VOICE_REG_CRED-6-PIN_ADDED : VOICE-REG-POOL-[dec] Pin added to voice register pool
Explanation Pin Added
Recommended Action No action is required.


%VOICE_REG_CRED-6-PIN_UPDATED : VOICE-REG-POOL-[dec] Pin updated in voice register pool
Explanation Pin Updated
Recommended Action No action is required.


%VOICE_REG_CRED-6-PIN_REMOVED : VOICE-REG-POOL-[dec] Pin removed from voice register pool
Explanation Pin Removed
Recommended Action No action is required.


VPDN

%VPDN-6-CLOSED : [chars] [chars][chars] closed [chars] [chars] [chars][chars][chars]
Explanation The remote server, typically the HGW/LNS closed this session. The reason for the closure is encoded in a hexadecimal format and corresponds to the particular protocol descriptions i.e. for L2F the values are documented in section 4.4.5 of the Internet Draft. A description string may also be present which describes the closure reason.
Recommended Action Check configuration on the NAS/LAC or HGW/LNS


%VPDN-6-DOWN : [chars] [chars][chars] changed state to down [chars] [chars] [chars][chars][chars]
Explanation The remote server, typically the HGW/LNS closed this tunnel. The reason for the closure is encoded in a decimal format, which corresponds to the particular protocol descriptions i.e. for L2F the values are documented in section 4.4.5 of the Internet Draft. A description string may also be present which describes the closure reason.
Recommended Action Check configuration on the NAS/LAC or HGW/LNS


%VPDN-6-AUTHENERR : [chars] [chars][chars] cannot authenticate for [chars] [chars] [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS is unable to locate a AAA server for the purposes of authenticating the user or tunnel. An error of this type indicates that the router was unable to establish a network connection with the designated/configured server. A reason string may also be present to provide further information.
Recommended Action Check AAA configuration on the NAS/LAC or HGW/LNS and network connectivity to the AAA server(s).


%VPDN-6-AUTHENFAIL : [chars] [chars][chars], [chars]authentication failure [chars]for [chars] [chars] [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS has failed to authenticate a user or a tunnel, or the HGW/LNS has failed authentication with the client which initiated the session. For authentication failures of the user or tunnel a reason string should be present which will 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.
Recommended Action Check username configuration on the NAS/LAC or HGW/LNS and possibly even the client if the HGW/LNS is failing authentication, removing the negotiation of outbound authentication is one possible solution i.e. only authenticate the user in the inbound direction. If AAA is applicable, check AAA configuration on the NAS/LAC or HGW/LNS and network connectivity to the AAA server(s).


%VPDN-6-AUTHORERR : [chars] [chars][chars] cannot authorize for [chars] [chars] [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS is unable to locate a AAA server for the purposes of authorizing the user or tunnel. An error of this type indicates that the router was unable to establish a network connection with the designated/configured server. A reason string may also be present to provide further information.
Recommended Action Check AAA configuration on the NAS/LAC or HGW/LNS and network connectivity to the AAA server(s).


%VPDN-6-AUTHORFAIL : [chars] [chars][chars], [chars]authorization failure for [chars] [chars] [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS has failed to authorize a user or a tunnel. A reason string may be present to indicate the point of failure.
Recommended Action Check authorization configuration on the NAS/LAC or HGW/LNS. If AAA is applicable, check network connectivity to the AAA server(s).


%VPDN-5-UNREACH : [chars] [chars][chars] is unreachable
Explanation The NAS/LAC or HGW/LNS has timed out attempting to establish a tunnel connection to a HGW/LNS or NAS/LAC. This may be due to network or authentication/authorization issues.
Recommended Action Check configuration on the NAS/LAC or HGW/LNS, check network connectivity between the NAS/LAC and HGW/LNS. Check if the tunnel setup needs to have a different source IP address from that of the NAS/LAC.


%VPDN-5-NOIDB : [chars] [chars][chars] unable to terminate user [chars]
Explanation The HGW/LNS is out of resources to create sessions for VPDN forwarded users, in particular it has reached the maximum number of interfaces allowed on the router.
Recommended Action


%VPDN-4-SESSIONERROR : [chars] [chars][chars] unable to terminate user [chars][chars][chars]
Explanation 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.
Recommended Action Check the configuration on the HGW/LNS


%VPDN-3-NORESOURCE : [chars] [chars][chars] no resources for user [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS is out of resources for the forwarding of a VPDN user.
Recommended Action


%VPDN-6-TIMEOUT : [chars] [chars][chars] disconnected [chars] [chars] [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS has disconnected the user due to the expiration of a timer, this may be e.g. PPP negotiation related or an absolute timeout for the session.
Recommended Action


%VPDN-6-SOFTSHUT : [chars] [chars][chars] has turned on softshut and rejected [chars] [chars] [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS can no longer accept new connection when softshut has been turned on. Existing session will continue until termination.
Recommended Action


%VPDN-4-REFUSED : Session for [chars] Refused status = [hex]
Explanation The remote server refused this session.
Recommended Action Check configuration on the HG or LNS


%VPDN-6-RESIZE : Updated [chars] MID table size to [int]
Explanation The NAS/LAC or HGW/LNS has altered the size of the session table through command line configuration.
Recommended Action


%VPDN-6-MAX_SESS_EXCD : [chars] [chars][chars] has exceeded configured local session-limit and rejected [chars] [chars] [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS has refused this session since the configured maximum VPDN session limit has been reached.
Recommended Action


%VPDN-3-IP_SWITCH_ERR : l2x ip switching vector not installed
Explanation Platform dependent l2x ip cef switching module is missing.
Recommended Action


%VPDN-3-DROP_ADDR_MISMATCH : [chars]
Explanation The remote server changed its address.
Recommended Action Change initiate-to configuration at the LAC to point to the exact IP address LNS will use


%VPDN-6-VPDN_DEADCACHE_EVENT : LSG dead cache entry [IP_address] [chars]
Explanation 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.
Recommended Action


%VPDN-6-TUNNEL_IN_RESYNC : [chars] [chars] [chars] tunnel is in HA resync, reject [chars] [chars] [chars]
Explanation The tunnel towards the peer is still in High Availability (HA) resync, hence it cannot bring up any new sessions until the resync is complete.
Recommended Action It is normal for this to occur during tunnel High Availability (HA) resync phase. New sessions cannot be brought up on a tunnel that is in HA resync. Once resync is complete, new sessions can be brought up on this tunnel.


%VPDN-6-QUEUED_PACKET_INFO : UnsetQ reached msg alert threshold. local_cc_id=[int], unsentQ=[int], resendQ=[int], max_unsentQ=[int], max_resendQ=[int]
Explanation UsentQ size has reached the message alert threshold. Message alert threshold can be configured through CLI 'vpdn queuesize-alert <num>'.
Recommended Action


VRFS

%VRFS-3-SBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified subblock data structure could not be accomplished.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VRFS-3-SBNOFN : Missing [chars] subblock [chars] function for [chars]
Explanation Functions for distributing this subblock are missing from the image.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


VRRP

%VRRP-6-STATECHANGE : [chars] Grp [dec] state [chars] -> [chars]
Explanation The VRRP router has changed state
Recommended Action No action is required.


%VRRP-4-BADAUTHTYPE : Bad authentication from [IP_address], group [dec], type [dec], expected [dec]
Explanation Two routers participating in VRRP disagree on the valid authentication type.
Recommended Action Use the vrrp authentication command to repair the VRRP authentication discrepancy between the local system and the one whose IP address is reported.


%VRRP-4-BADAUTH : Bad authentication from [IP_address], group [dec], type [dec]
Explanation Two routers participating in VRRP disagree on authentication
Recommended Action Use the vrrp authentication command to repair the VRRP authentication discrepancy between the local system and the one whose IP address is reported.


%VRRP-3-ERROR : Internal error, [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VRRP-4-WARN : Internal warning, [chars]
Explanation An internal software warning occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VRRP-4-CFG_WARN : [chars]
Explanation There is a mismatch in the number of additional addresses advertised by the peer; or the addresses are mis-ordered in the peer advertisement.
Recommended Action No action is required.


%VRRP-6-STATE : [chars]
Explanation The VRRP router has changed state.
Recommended Action No action is required.


%VRRP-6-INFO : Internal info, [chars]
Explanation An internal software information message occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


VRRS

%VRRS-3-ACCTFORKFAIL : Failed to start accounting process. Accounting-off records may not be sent.
Explanation Failed to create the accounting process.
Recommended Action Free up some memory.


%VRRS-3-ERROR : Internal error, [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VRRS-4-WARN : Internal warning, [chars]
Explanation An internal software warning occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VRRS-6-STATE : [chars]
Explanation The VRRS router has changed state.
Recommended Action No action is required.


%VRRS-6-INFO : Internal info, [chars]
Explanation An internal software information message occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


VSTATS

%VSTATS-6-VCSR : SEQ=[int]:[chars]
Explanation The text data are pushed out as voice call statistics records(VCSR).
Recommended Action The statistics text data should be reordered with the given SEQ number if one large message is chopped into multiple segments. The text data can be parsed/uploaded to be processed in more elegant form.


%VSTATS-6-IEC : SEQ=[int]:[chars]
Explanation The text data are pushed out as internal error code(IEC).
Recommended Action The statistics text data should be reordered with the given SEQ number if one large message is chopped into multiple segments. The text data can be parsed/uploaded to be processed in more elegant form.


VTCP

%VTCP-3-VTCP_CREATE_CB_MALLOC_FAILED :
Explanation Malloc failed during VTCP create callback.
Recommended Action LOG_STD_ACTION


VTSP

%VTSP-3-NOEVENT : no free event structure available from [chars] for DSP message
Explanation There were no event structures remaining in the system pools to alert the router of a voice or signaling event.
Recommended Action Check that the voice port for which the event was reported is still operational. If not, clear the voice port.


%VTSP-3-CAPABILITYMISMATCH : voice port [chars]: call connection id [[hex] [hex] [hex] [hex]]
Explanation There was a capabilities mismatch between the two call legs. capabilities are negotiated between call legs for CODEC, VAD and FAX rate.
Recommended Action 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-DSPALARM : channel [chars], DSP ID [hex]: status=[hex] message=[hex] text=[chars]
Explanation The DSP reported a fatal error. All calls on the DSP were dropped and a DSP reload was attempted.
Recommended Action 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-FSM_ERROR : [chars]
Explanation Internal Finite State Machine Error.
Recommended Action Contact your technical support representative, include the full text of the error message.


%VTSP-3-DSP_TIMEOUT : DSP timeout on channel [chars], event [hex]: DSP ID=[hex]: [chars] (call mode=[dec])
Explanation Timeout on DSP response.
Recommended Action The DSP has been automatically reset. If problem persists, contact your technical support representative


%VTSP-4-FSM_BAD_EVENT : Invalid FSM Input on channel [chars]: state=[chars] event=[dec]
Explanation Internal state machine illegal input. This message represents an internal software fault and may manifest itself as dropped or hung calls.
Recommended Action Contact your field service representative if indication is coincident with dropped or hung calls.


%VTSP-3-DOCALLHISFAIL : vtsp_do_call_history: [chars]
Explanation Allocate or insert an active VTSP call record into call history list failed.
Recommended Action No action is required.


%VTSP-3-MSGSNDFAIL : channel:[chars] DSP ID:[hex] Message ID:[hex]
Explanation A message could not be sent to the DSP. The call continued but may have experienced problems.
Recommended Action 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-VTSP_BLOCK : vtsp_call_block allocate failed
Explanation VTSP call block allocation failed.
Recommended Action Add more memory


%VTSP-3-VTSP_CALL_INFO_CHUNK : VTSP callInfo chunk creation failed.
Explanation Creation of VTSP callInfo chunk failed due to lack of memory.
Recommended Action Add more memory.


%VTSP-3-VTSP_DB_ERR : vtsp_call_block database error
Explanation Internal VTSP call block database error. This message represents an internal software fault and may manifest itself as dropped or hung calls.
Recommended Action Contact your technical support representative, include the full text of the error message.


%VTSP-3-VTSP_HAIRPINN : hairpin peer cdb does not exist, cdb [hex], dst_call_id [dec]
Explanation A hairpin call setup failed because the other call leg does not exist.
Recommended Action Contact your technical support representative. Report the configuration, and the full text of the error message.


%VTSP-3-VTSP_HAIRPIN_NOTPOSSIBLE : Call can't be hairpinned. cdb [hex], dst_cdb [hex], dst_call_id [dec]
Explanation A DSP-less call could not be hairpinned.
Recommended Action Check the dial-peer configuration.


%VTSP-3-VTSP_HAIRPIN_FAILED : Call hairpinning failed. cdb [hex], dst_cdb [hex], dst_call_id [dec]
Explanation A DSP-less call could not be hairpinned.
Recommended Action Under heavy traffic, this failure may happen because no TDM resources wereavailable. Contact your technical support representative, include the full text of the error message.


%VTSP-3-VTSP_CALL_DISC_FAILED : VTSP call disconnect failed. channel id [chars], ret [dec]
Explanation VTSP call disconnect could not be successfully passed and it may result hung calls.
Recommended Action Contact your technical support representative. Report the configuration and full text of the error message.


%VTSP-4-VTSP_PLAR_TIE_FAILED : VTSP connection plar tie set up failed. channel id [chars], cause [dec]
Explanation Connection plar tie set up failed for non-normal reason
Recommended Action Contact your technical support representative. Report the configuration and full text of the error message.


%VTSP-6-UNKNOWN_EXT_AGENT_RESET_ATTEMPT : Request to reset an uknown external agent (ID [dec]) attempted. Attempt ignored.
Explanation A request to reset an external agent (eg H323 Gatekeeper or MGCP CA etc) was attempted but IOS doesn't know how to process the request. This is not usually a problem for the router. It does however mean that the external agent for whom the reset was intended never got it.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VTSP-6-LONG_DUR_CALL_DETECTED : Long Duration Call is detected [chars]
Explanation The call is active for configured duration of long call
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%VTSP-2-H320_MATCH_CALL_QUEUE_ERROR : Memory corruption is found on H.320 Primary Call Match Data Queue. Queue Size=[dec]
Explanation Failed to match an H.320 primary call for an incoming call due to memory curruption.
Recommended Action Contact your technical support representative. Report the configuration and full text of the error message.


WANPHY

%WANPHY-4-WANALARM : [chars]: [chars] [chars]
Explanation The specified WANPHY Alarm has been declared or cleared.
Recommended Action Recommended action is to repair the source of the alarm.


WCCP through XDR

WCCP

%WCCP-1-SERVICELOST : Service [chars][chars][chars] lost on WCCP client [chars]
Explanation WCCP has lost the service associated the specified WCCP client
Recommended Action Verify the operation of the specified WCCP client


%WCCP-5-SERVICEFOUND : Service [chars][chars][chars] acquired on WCCP client [chars]
Explanation WCCP has acquired a service on the specified WCCP client
Recommended Action No action is required.


%WCCP-5-SERVICEMISMATCH : Service [chars][chars][chars] mismatched on WCCP client [chars]
Explanation WCCP has rejected a mismatched service on the specified WCCP client
Recommended Action Amend the WCCP service definition


%WCCP-3-MASKACLMERGE : Mask/ACL merge failed for the service [chars], VRF [chars], service Id [dec]
Explanation An internal error indicating that the Mask/ACL merge has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%WCCP-1-SERVICELIST : Failed to derive service [chars][chars][chars] from service-list [chars]
Explanation 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
Recommended Action Update the service-list ACL to correctly define the desired service


%WCCP-3-SBCREATEFAIL : Unable to allocate [chars] WCCP subblock on interface [chars]
Explanation An internal error indicating that the WCCP process was unable to allocate memory to hold interface specific service information
Recommended Action Ensure that there is enough memory available for all processes


%WCCP-3-SBADDFAIL : Unable to add [chars] WCCP subblock on interface [chars]
Explanation An internal error indicating that the WCCP process was unable to attach interface specific service information
Recommended Action Ensure that there is enough memory available for all processes


%WCCP-3-BADACE : Service [chars][chars][chars], invalid access-list entry (seq:[dec] reason:[chars])
Explanation 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 netflow switching
Recommended Action Update the Access Control List to remove or change the incompatible entry


%WCCP-3-SBINIT : Error initializing [chars] WCCP subblock data structure. [chars]
Explanation Initialization of the specified subblock data structure could not be accomplished.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%WCCP-3-CAP_API_INI : Failed to initialize WCCP platform parameter [int]
Explanation Initialization of a WCCP platform parameter failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%WCCP-3-CAP_API_DEF : Failed to set WCCP platform parameter defaults [hex] ([chars])
Explanation The platform failed to set the WCCP platform parameter defaults.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%WCCP-3-CAP_API_GET : Failed to get WCCP platform parameter [int] ([chars])
Explanation The platform failed to read a WCCP platform parameter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%WCCP-3-CAP_API_SET : Failed to set WCCP platform parameter [int] to [int] ([chars])
Explanation The platform failed to modify a WCCP platform parameter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%WCCP-3-SIFIGNORED : source-interface [chars] ignored ([chars])
Explanation The configured source interface has been ignored whilst determining the WCCP router ID.
Recommended Action Use the indicated reason message to determine why WCCP refused to use the configured interface as its router ID.


WEBSERVER

%WEBSERVER-5-LOGIN_PASSED :
Explanation Login successful
Recommended Action No action is required


%WEBSERVER-5-LOGIN_FAILED :
Explanation Login unsuccessful when user/password is invalid
Recommended Action No action is required


%WEBSERVER-5-SESS_LOGOUT :
Explanation Logout successful
Recommended Action No action is required


%WEBSERVER-5-SESS_TIMEOUT :
Explanation Session Timeout
Recommended Action No action is required


%WEBSERVER-5-CONNECTION_FAILED :
Explanation Failure reason for SSL connection
Recommended Action No action is required


%WEBSERVER-5-MAX_CONNECTION_REACHED :
Explanation Maximum HTTP connection reached.
Recommended Action No action is required


WLCLIENT_IPSG_PROXY

%WLCLIENT_IPSG_PROXY-3-WLS_IPSG_MEM_REQ_FAILED : WLCLIENT IPSG IPC subtype: [dec]
Explanation Requesting more memory failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%WLCLIENT_IPSG_PROXY-3-WLS_IPSG_MEM_EXTEND_FAILED : WLCLIENT IPSG IPC subtype: [dec]
Explanation Extending memory failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%WLCLIENT_IPSG_PROXY-4-PROXY_INVALID_MSG_LEN : QFP WLCLIENT IPSG Proxy IPC invalid length, [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Cisco internal software error. QFP WLCLIENT IPSG Proxy received invalid IPC message length from control plane. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%WLCLIENT_IPSG_PROXY-4-PROXY_INVALID_MSG : QFP WLCLIENT IPSG Proxy received invalid message type [dec]
Explanation Cisco internal software error. QFP WLCLIENT IPSG Proxy received an invalid message from control plane. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%WLCLIENT_IPSG_PROXY-2-PROXY_IPC_INIT_FAILED : QFP WLCLIENT IPSG Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP WLCLIENT IPSG Proxy initialization detected that the IPC interface initialization failed. QFP WLCLIENT IPSG proxy will not be functional while this condition exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%WLCLIENT_IPSG_PROXY-3-PROXY_BAD_MSG : QFP WLCLIENT IPSG Proxy received bad length message type [dec]
Explanation Cisco internal software error. QFP WLCLIENT IPSG Proxy received a corrupted message from control plane. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%WLCLIENT_IPSG_PROXY-3-PROXY_IPC_ALLOC_FAILED : QFP WLCLIENT IPSG Proxy [chars] message lost due to message buffer allocation failure.
Explanation Cisco internal software error. QFP WLCLIENT IPSG Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%WLCLIENT_IPSG_PROXY-3-PROXY_IPC_SEND_FAILED : QFP WLCLIENT IPSG Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. QFP WLCLIENT IPSG Proxy message processing detected a message sent failure. The message is lost as the result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


WLS_FQDN_PROXY

%WLS_FQDN_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%WLS_FQDN_PROXY-4-PROXY_IPC_INVALID_MSG : [hex]
Explanation Received an invalid IPC messages subtype.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


WSMAN

%WSMAN-3-INVALID_TRUSTPOINT : Trustpoint associated with HTTP is either invalid or does not exist
Explanation This message indicates that Trustpoint attached to the HTTP is not valid or it does not exist. Ideally there is a need to create Trustpoint first and then attach to the HTTP process. Incase, Trustpoint is created later then there is a need to restart HTTPS server
Recommended Action Configure a valid trustpoint and attach it to HTTP


WUILOGIN

%WUILOGIN-2-INITIALIZATION_FAILED : WebUI standalone login initialization failed.
Explanation The attempt to access the web user interface using the wuilogin access module failed. The wuilogin access module is used to authenticate web user interface access only when the IOS integrated webserver, which is enabled using the ip http server command, or the IOS process is down or disabled.
Recommended Action Note the time of the error and check the web user interface log (wuilogin-*.log) for additional information on why the attempt to access the web user interface failed.


%WUILOGIN-2-AUTHENTICATION_SYSTEM_FAILED : WebUI standalone authentication process failed. Reason: [chars]
Explanation During the id and password validation phase of the wuilogin access module authentication attempt, an exception occurred. This message usually occurs as a result of a failure of the underlying PAM authentication module.
Recommended Action Note the time of the error and check the web user interface log (wuilogin-*.log) for additional information on why the attempt to access the web user interface failed.


X25

%X25-2-ILLP4 : Interface [chars], Illegal state [chars] when P4
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.


%X25-3-NOLCI : Interface [chars], Delete: lci [dec] not found in [chars] table
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.


%X25-3-UNKNOWNPROT : [chars] : Unable to identify lower layer protocol
Explanation IDB is not using X25 and IDB is not capable of supporting CMNS.
Recommended Action Check your hardware configuration or contact your technical support representative for assistance.


%X25-3-X25NOTAVAIL : [chars] : Lower layer protocol is not available
Explanation The required lower layer service is unavailable.
Recommended Action Check your configuration or contact your technical support representative for assistance.


%X25-3-BADCONFIGATTEMPT : Attempt to [chars].
Explanation The user attempted an illegal configuration.
Recommended Action 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-NOTFINDBH : Can't find bfe host address [IP_address] to delete
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.


%X25-3-INTIMEQ : Interface [chars], LCN [dec] already in timer queue, new time %#Ta
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.


%X25-3-BADCONFIG : Interface [chars], X.25 [chars], current config. retained
Explanation The interface's X.25 configuration is not valid; the existing configuration was not changed.
Recommended Action Verify the following: The interface's switched virtual circuit ranges do not overlap; for nonzero values, lic <= hic < ltc <= htc < loc <= hoc. (For more information, refer to Configuring Virtual Circuit Ranges in the Router Products Configuration Guide.) If an incoming-only range is defined, check that it is numerically less than the two-way range. If an outgoing-only range is defined, check that it is numerically greater than the two-way range. No virtual circuit high/low parameter is zero unless its partner low/high parameter is also zero. The default window sizes are less than the interface modulo.


%X25-3-PVCBAD : Interface [chars], PVC [dec], [chars]
Explanation 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.
Recommended Action Validate the configuration of the PVCs at both ends of the connection, and reconfigure them if necessary.


%X25-3-XOTPROTOCOL : XOT protocol error from [IP_address]: [chars]
Explanation A protocol error was detected over an X.25-over-TCP (XOT) connection, causing the connected VC to close. A flaw may exist in the remote host's XOT implementation.
Recommended Action If this message recurs, call your technical support representative for assistance.


%X25-4-VCLOSTSYNC : Interface [chars], VC [dec] TCP connection [chars]
Explanation An X.25 circuit that is being tunneled over a TCP connection between routers was cleared ungracefully. The last [chars] text string in the message can take one of two forms. If the text string is closed unexpectedly, the router at the remote end of the connection was rebooted, or the connection failed. If the text string is connection corrupted, it is likely that the connection was made to a router running an older software release.
Recommended Action If the text string is closed unexpectedly, reestablish the connection after the remote router or intervening network is operational. If the text string is connection corrupted, upgrade the router at the other end of the connection to a more recent software release.


%X25-4-BADUPCALL : Interface [chars], Unexpected call ([chars]) from LLC2 DTE=[hex][hex].[hex][hex].[hex][hex].
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.


%X25-4-DEBUG_LCI : LCI deleted at interrupt time
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.


%X25-4-RANGEUNUSED : Interface [chars], [chars] VC range unused; set limits to zero
Explanation An outgoing-only or incoming-only virtual circuit range exactly overlaps the two-way virtual circuit range. This was the former method for specifying that a virtual circuit range was not used. The current method is to set the range limits to zero.
Recommended Action Use the privileged copy running-config startup-config command to write the configuration to memory. This will store the modified (zero) range limits.


%X25-4-LARGEPKSIZE : Interface [chars], [chars] packet sizes [dec]/[dec] too large; lower values will be negotiated
Explanation The interface's default packet sizes or outgoing packet size facility values are too large to be carried by Link Access Procedure, Balanced (LAPB).
Recommended Action The router will negotiate lower packet size values automatically. The LAPB N1 value should be increased. For example, for an X.25 maximum packet size of 1024, modulo 8 X.25 operation will add 3 bytes of overhead and modulo 8 LAPB operation will add 4 bytes of overhead (the two bytes of CRC are defined to be included). This means that N1 must be at least 1031 bytes * 8 = 8248.


%X25-4-PARTIALMAP : Interface [chars], [chars] encapsulation call from [chars] partially mapped to [chars]
Explanation An incoming X.25 call specified a protocol that was assigned to a multiprotocol map; the VC will not be able to carry the full set of protocols specified by the map.
Recommended Action Modify the configuration of the router or the far host to match the encapsulation method used.


%X25-5-NOBUF : Interface [chars] LCI [dec] [chars]
Explanation This is a warning only (the compressed packet was not lost). However, an X.25 packet layer RNR (wait) was generated and packet-level transmission on the LCN will not resume (RR issued) until a decompression buffer becomes available.
Recommended Action If this message occurs frequently, you may need to modify the buffer pool. Copy the message exactly as it appears, and report it your technical support representative.


%X25-5-PBPHOLDQ : Interface [chars] LCI [dec] X25 Hold queue needs to be at least default size
Explanation An attempt was made to configure the X.25 hold queue to less than the minimum value.
Recommended Action Configure the X.25 hold queue to be ten or more.


%X25-5-PBPDBIT : Interface [chars] LCI [dec] PBP Compression does not support X25 D bit
Explanation Compression is not enabled because D-bit support is configured for the LCI.
Recommended Action Reconfigure without D-bit support, or do not attempt to run with compression.


%X25-3-SYNCBAD : Interface [chars] LCI [dec] Decompression sync error. expected [dec] got [dec]
Explanation An internal software error occurred. The PBP header has a sync field. The sync field (8 bits) is checked on each received packet.
Recommended Action Contact your technical support representative for assistance.


%X25-3-VERSIONBAD : Interface [chars] LCI [dec] Compression Version mismatch expected [hex] received [hex]
Explanation An internal software error occurred. The PBP header has a mismatched version field. The version is checked on each received packet.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.


%X25-3-SIZEBAD : Interface [chars] LCI [dec] Decompression size error
Explanation An internal software error occurred. The PBP header has an uncompressed packet size field. Each uncompressed packet size is checked against this field.
Recommended Action Contact your technical support representative for assistance.


%X25-5-PBPNOEND : Interface [chars] LCI [dec] End system not configured for X25 PBP
Explanation A compression or decompression operation was attempted by a router other than an end router. Only end routers can perform compression and decompression.
Recommended Action Reconfigure the routers so that only the end routers in the network perform compression and decompression.


%X25-3-COMPERR : Interface [chars] LCI [dec] low-level stac compression error
Explanation A Stacker compression algorithm internal error or shortage of buffer space was encountered during a compression operation. This should never happen.
Recommended Action Report the error to your technical support representative.


%X25-4-BADMBIT : Interface [chars], VC [dec], partial data packet has M-bit set
Explanation This message occurs when a virtual circuit is set up using the default maximum packet sizes, but the DTE and DCE are not configured with the same default values. A packet was received that had the M-bit set, signifying that more data follows, but the packet did not carry the maximum number of bytes allowed. Such partial data packets must have the M-bit cleared. The resulting loss of a message boundary might cause problems for the data recipient.
Recommended Action Verify the default flow control parameters of the DTE and the DCE. If this message recurs, call your technical support representative for assistance.


%X25-3-ADDRESSBAD : Interface [chars], x25 address [chars] subaddress %c is too long
Explanation This message occurs when a subaddress is configured. When this subaddress is combined with the interface's X.121 address, the total address exceeds the limit of 15 characters.
Recommended Action Reconfigure the subaddress so that this does not happen.


%X25-3-ERR_SUBST_XOT_DNS_DEST : Error substituting regular expression for XOT DNS destination pattern
Explanation 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
Recommended Action Correct the X.25 route command's DNS substitution pattern


%X25-3-TRUNCATE_ALT_XOT_DNS_DEST : Truncating excess XOT addresses ([dec]) returned by DNS
Explanation This message occurs when an X.25 route DNS lookup returns more than the 6 permissible XOT destination addresses
Recommended Action Review the DNS database entries used for XOT destination lookup for possible modification


%X25-4-XOTHOSTWRONG : Wrong host ([IP_address]) for XOT connection to [chars] PVC [dec]; expecting [IP_address]
Explanation This message occurs when an incoming XOT connection identifies a PVC that is configured for a different host IP address, and whose configuration does not permit connection to a different host.
Recommended Action If the host attempting the connection should be allowed, either the remote host should be configured to use a single host address (by adding the xot-source-ifc option), or the local PVC should be configured to accept connections from any host (by using the xot-promiscuous option). If the host attempting the connection should not be allowed, the network administrator should take action appropriate for an attempt to create an unauthorized connection.


%X25-4-XOTPVCDUPLICATE : Duplicated remote PVC data for {[chars], pvc [dec]} and {[chars], pvc [dec]}
Explanation This message identifies two local XOT PVCs that are defined using duplicate specifications for the connecting remote XOT PVC.
Recommended Action This message probably reflects a configuration error; the network administrator should examine the identified PVCs to determine what XOT PVC configuration is required.


%X25-4-BFEIP : Warning: IP address is missing or incompatible with BFE mode
Explanation An interface configured for X.25 BFE mode does not have an IP address configured, or the IP address does not conform to BFE requirements, so cannot be mapped to an X.121 address.
Recommended Action Please configure a valid Class A IP address for the interface or remove the 'bfe' option from the 'encapsulation x25' command for the interface.


%X25-3-X25INT : Interface [chars], X.25 internal error [chars]
Explanation This is a general message covering numerous internal X25 error conditions. The message text contains additional details that can be used to identify the problem.
Recommended Action LOG_STD_RECUR_ACTION


%X25-3-XOTINT : XOT internal error [chars]
Explanation This is a general message covering numerous internal error conditions related to XOT. The message text contains additional details that can be used to identify the problem.
Recommended Action Contact your Cisco technical support representative and provide the representative with the error message text exactly as it appears on the console or in the system log and the output of show version, show running-config , show x25 and debug x25 commands


%X25-3-PROFILENO : profile [chars] does not exist
Explanation This message occurs when an X.25 interface is configured to use an X.25 profile that does not exist
Recommended Action Create and configure the x25 profile using x25 profile <name> global subcommand before referencing the profile.


%X25-3-X25NOCFG : Profile is not configured
Explanation This message occurs when an X.25 interface is configued to use an X.25 profile that isn't configured
Recommended Action Configure the x25 profile using x25 profile <name> global subcommand before referencing the profile.


%X25-3-X25ENCINV : [chars]
Explanation This message occurs when configuring an X.25 service.
Recommended Action LOG_STD_ACTION


%X25-3-X25DEENCINV : [chars]
Explanation This message occurs when deconfiguring X.25 service.
Recommended Action LOG_STD__ACTION


%X25-3-INVCFGID : [dec] is not a valid X.25 configuration ID
Explanation This message occurs when an invalid configuration id is used
Recommended Action LOG_STD_ACTION


%X25-5-UPDOWN : Interface [chars] - DLCI [dec] X.25 packet layer state changed to [chars]
Explanation The state of the X.25 context associated with the DLCI changed
Recommended Action Notification message only. No action required


%X25-7-DIAGEVENT : Interface [chars], X.25 diagnostic event, [chars], lci [dec][chars]
Explanation A standard X.25 diagnostic event has been detected. Per Recommendation X.25 a DCE detecting this will send a Diagnostic packet whereas a DTE cannot. The Recommendation defines diagnostic events for packets occurring on an unassigned channel, receipt of some classes of malformed packets, non-standard usage of channel 0 for Call setup or Data traffic, and some protocol timeout events. An unexpected, but benign, diagnostic event may occur when an attached station doesn't respond to a protocol event soon enough; e.g. a timeout waiting for a response to a Call, Clear or Reset sent. The most common malign cause of a diagnostic event is a mismatched configuration of the logical channel ranges between the DTE and DCE stations.
Recommended Action If an attached station is delaying responses to protocol events, check if the appropriate timeout value is sufficient for expected network behavior, and if the connected station is unduly delaying its response. For unassigned logical channel events, enter the show x25 interface <CmdItalics>id<NoCmdItalics> for the reporting station to verify the logical channel assignments configured are correct and operational. These ranges must match those defined on the connected station; refer to the Setting the Virtual Circuit Ranges section of the Cisco IOS Wide-Area Networking Configuration Guide for more information. For the rare case where logical channel 0 is designated for non-standard Call setup or Data traffic, both stations must be configured to reflect that usage. LOG_STD_RECUR_ACTION


%X25-7-DIAGRX : Interface [chars], X.25 Diagnostic received, [chars][chars]
Explanation An X.25 diagnostic packet has been received at the DTE from the DCE. Per Recommendation X.25, a DCE station must send a Diagnostic packet when it detects a standard diagnostic event, which the DTE must discard with no protocol action taken; a DTE cannot send a Diagnostic packet. Recommendation X.25 defines diagnostic events for packets occurring on an unassigned channel, receipt of some classes of malformed packets, non-standard usage of channel 0 for Call setup or Data traffic, and some protocol timeout events. An unexpected, but benign, Diagnostic packet may be received when the DTE station doesn't respond to a protocol event soon enough; e.g. the DCE timed out waiting for a response to a Call, Clear or Reset. The most common malign cause of a diagnostic event is a mismatched configuration of the logical channel ranges between the two stations.
Recommended Action If an attached station is delaying responses to protocol events, check if the appropriate timeout value is sufficient for expected network behavior, and if the connected station is unduly delaying its response. For unassigned logical channel events, enter the show x25 interface <CmdItalics>id<NoCmdItalics> for the reporting station to verify the logical channel assignments configured are correct and operational. These ranges must match those defined on the connected station; refer to the Setting the Virtual Circuit Ranges section of the Cisco IOS Wide-Area Networking Configuration Guide for more information. For the rare case where logical channel 0 is designated for non-standard Call setup or Data traffic, both stations must be configured to reflect that usage. LOG_STD_RECUR_ACTION


%X25-5-CALL_RECORD : [chars]
Explanation This message contains X.25 call record information.
Recommended Action No action is required.


XCCTSP_VOICE

%XCCTSP_VOICE-3-UNDEFVOICEINTRF : Invalid voice interface slot/controller:group([dec]/[dec]:[dec])
Explanation The voice interface defined by controller:group is not yet defined within the voice software but attempts were made to use this interface.
Recommended Action Internal software fault. Contact your field service representative if this message is coincident with dropped calls.


%XCCTSP_VOICE-3-UNDEFDSX0 : Undefined dsx0 interface for controller([dec])
Explanation The dsx0 interface for the specified controller is not defined but the voice software use it.
Recommended Action Internal software fault. Contact your field service representative if this message is coincident with dropped calls.


%XCCTSP_VOICE-3-NOSDB : No signaling data block is available to build the voice interface([dec]/[dec]:[dec]) or DSP may not be present
Explanation The voice software was unable to obtain a signaling data block from the Voice Telephony Service Provider. The system may be out of memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%XCCTSP_VOICE-3-ADDINTRFFAIL : The Voice Telephony Service Provider has rejected our request to add this voice interface ([dec]/[dec]:[dec])
Explanation The voice software was unable to report a new signaling interface to the Voice Telephony Service Provider
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%XCCTSP_VOICE-3-NOMEM : No memory is available to build the voice interface ([dec]:[dec])
Explanation The voice software was unable allocate memory to build a voice interface data structure. The system may be out of memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%XCCTSP_VOICE-3-MALLOC : No memory is available to build any internal data structure for the voice software.
Explanation The voice software was unable allocate memory to build any internal data structures. The system may be out of memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%XCCTSP_VOICE-3-NOTDMCHNL : XCCTSP failed to get a free dsp tdm channel from the DSP Resource Manager (DSPRM) to handle an incoming call
Explanation 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.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%XCCTSP_VOICE-3-NOVOICEVDEV : Cannot find the voice data block which matches an asynchronous response for a call.
Explanation Internal software fault. Contact your field service representative if this message is coincident with dropped calls.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%XCCTSP_VOICE-3-OUTOFRANGE_CTRL : Going out of range for controller number for the slot subslot [dec], ctrl_num [dec]
Explanation Internal software fault. Contact your field service representative
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


XCONNECT

%XCONNECT-3-ILLEGAL : [chars]
Explanation An illegal event has been processed by the xconnect subsystem.
Recommended Action No action is required.


%XCONNECT-3-CONFIG : [chars]
Explanation An invalid xconnect configuration or an error in processing xconnect configuration has occurred.
Recommended Action No action is required.


%XCONNECT-5-REDUNDANCY : [chars]
Explanation An event has occurred that has caused the xconnect redundancy facility to generate a switchover event to the specified backup member
Recommended Action No action is required.


%XCONNECT-5-PW_STATUS : [chars]
Explanation An event has occurred that has caused the pseudowire to change status
Recommended Action No action is required.


%XCONNECT-5-PW_STATUS_LOST : [chars]
Explanation The system is dropping PW_STATUS messages because the status queue is full
Recommended Action No action is required.


XDR

%XDR-3-XDRIPC : XDR IPC error on multicast-group [hex] due to [chars].
Explanation A general IPC related error occurred which may prevent transfer of data to other peers using the IPC mechanism
Recommended Action Get the output of show xdr multicast immediately after this error. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-6-XDRIPCPEER : XDR IPC error occurred for peer in slot [chars] due to [chars][chars].
Explanation A general IPC related error occurred which may prevent transfer of data to other peers using the IPC mechanism
Recommended Action Get the output of show xdr multicast and show xdr linecard immediately after this error. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-2-XDRDISABLEREQUEST : Peer in slot [chars] requested to be disabled due to: [chars]. Disabling linecard
Explanation Due to some error condition the linecard has requested to be disabled
Recommended Action Execute clear xdr linecard from the RP followed by clear xdr channel on the linecard in question to clear the error condition. If the problem persists get the output of show monitor event-trace xdr all from the RP and the linecard in question and report it to your technical support representative.


%XDR-2-XDRLCDISABLEREQUEST : Client [chars] requested to be disabled. [chars]
Explanation Due to some error condition the linecard has requested to be disabled
Recommended Action Execute clear xdr linecard from the RP followed by clear xdr channel on the linecard in question to clear the error condition. If the problem persists get the output of show monitor event-trace xdr all from the RP and the linecard in question and report it to your technical support representative.


%XDR-3-XDRNOMEM : XDR failed to allocate memory during [chars] creation.
Explanation Allocation of memory by the XDR subsystem failed. This may result in an unpredictable behavior of XDR
Recommended Action 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.


%XDR-3-PULLSENDFAIL : Sending data for pull client [chars] to [chars] failed due to slot(s) [chars] not being in group [hex] of slot(s) [chars]
Explanation Data sending for an XDR pull client failed for the reason specified. The data was not sent.
Recommended Action LOG_STD_SH_CMD_ACTION(show xdr multicast-group)


%XDR-3-NONINCRSEQ : Non-increasing maximum sequence ([dec], was [dec]) received from slot [chars]
Explanation Internal software error. May result in unpredictable behaviour.
Recommended Action LOG_STD_SH_CMD_ACTION(show xdr linecard)


%XDR-3-BADSEQVAL : Incorrect maximum sequence calculated ([dec], was [dec]) for slot [chars] with [dec] out of [dec] buffers available
Explanation Internal software error. May result in unpredictable behaviour.
Recommended Action LOG_STD_SH_CMD_ACTION(show xdr linecard)


%XDR-6-ISSUBADRCVTFM : Failed to rcv_transform message - slot [chars], reason: [chars]
Explanation Unable to perform ISSU transform on incoming XDR header. Message will be ignored
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-6-ISSUBADTXTFM : Failed to xmit_transform message - slot [chars], reason [chars]
Explanation Unable to perform ISSU transform on outgoing XDR header. Message will be ignored
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-ISSUBADREGPARAMS : XDR client [chars] trying to register with incomplete ISSU support.
Explanation This client does not properly support ISSU and will be registered as not supporting ISSU.
Recommended Action We cannot allow a client to register with partial ISSU support so it will be registered without it. Please report this message to your technical support representative.


%XDR-3-ISSUCAPNEGOFAIL : XDR client [chars] failed to [chars] capability/ies due to [chars]
Explanation Internal software error - capability negotiation failed unexpectedly.
Recommended Action Copy the message exactly as it appears and report it to your technical support representative


%XDR-3-ISSUINITFAIL : Unable to register XDR ISSU [chars], reason: [chars]
Explanation 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 behaviour.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-6-ISSUCLIENTABSENT : XDR client [chars] absent on slot [chars]. Client functionality may be affected.
Explanation The remote slot doesn't 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 apprporiate. This is expected behaviour in ISSU-capable systems.
Recommended Action No action required. This message just indicates that certain functionality may be reduced due to running different images together.


%XDR-3-ISSU_ENUM_ERROR : Enum for [chars] ([chars] component) is not ISSU-compliant: [chars]
Explanation The given enumeration is not ISSU-compliant for the reason given. Unpredictable behaviour will result when interoperating with different IOS versions.
Recommended Action This requires a code fix before the image can be shipped or ISSU will be broken.


%XDR-3-CLIENTISSUBADGROUP : New m/cast group (slots [chars]) has multiple members before nego complete.
Explanation A new multicast group has been created with multiple slots before ISSU negotiation for each client has completed. This will lead to unpredictable results.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-CLIENTISSUBADNEGOMSG : Unexpected nego msg - slot [chars], XDR client [chars], ctxt [dec]
Explanation XDR has received a negotiation message unexpectedly as this client is either not ISSU aware or has already completed negotiation for this slot. This is likely a precursor to unpredictable behaviour for this client.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-CLIENTISSUSENDFAILED : Can't send XDR client ISSU nego msg: reason [chars], slot [chars], XDR client [chars]
Explanation 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 likley to lead to unpredictable behaviour.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Also copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-CLIENTISSUSTARTNEGOFAIL : Can't start nego: reason [chars], slot [chars], XDR client [chars], sid [dec]
Explanation 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 likley to lead to unpredictable behaviour.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Also copy the message exactly as it appears, and report it to your technical support representative.


%XDR-6-CLIENTISSUBADRCVTFM : Failed to rcv_transform message - from slot [chars], XDR client [chars], context [dec]
Explanation Cannot perform ISSU receive transform. This is likely due to a failure in negotiation earlier, or when one side of an ISSU-enabled XDR connection is out of sync with the other.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-6-CLIENTISSUBADTXTFM : Failed to xmit_transform message - to slot [chars], XDR client [chars], context [dec]
Explanation Cannot perform ISSU transmit transform. This is likely due to a failure in negotiation earlier, or when one side of an ISSU-enabled XDR connection is out of sync with the other.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-CLIENTISSUNEGATIVEPADDING : Negative padding for [chars], slots [chars], msg [dec] (padded: [dec], unpadded: [dec])
Explanation Internal error. Mismatch of internal data structures.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-CLIENTISSUNEGONOTDONE : Attempting to push send XDR message ([dec]) to slots [chars] for [chars] before nego complete.
Explanation Internal error. May result in unpredictable behaviour.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-6-CLIENTISSUUNREG : Failed to unregister session - XDR client [chars], slot [chars], reason [chars]
Explanation Unable to unregister this session. This will likely cause problems when reregistering and should be reported.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-CLIENTISSU_REGERROR : ISSU client [chars] ([dec]), entity [dec], failed ISSU registration: [chars]
Explanation ISSU negotiation failed for this XDR client.
Recommended Action This error indicates a coding problem. It is an error that will occur every time this image is run, and requires a code change to fix it.


%XDR-3-ISSU_NEGOFAIL : ISSU negotiation failed for XDR, slot [chars], reason: [chars]
Explanation ISSU negotiation failed. XDR on this and the remote slot cannot interoperate. Syncing of information to/from this slot for all XDR clients will not be allowed.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-PRIOCLIENTISSU_NEGOFAIL : ISSU negotiation failed for XDR client [chars], slot [chars], reason: [chars]
Explanation ISSU negotiation failed for a core XDR client. XDR on this and the remote slot cannot interoperate in SSO mode. Syncing of information to/from this slot will not happen for any XDR client.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-CLIENTISSU_NEGOFAIL : ISSU negotiation failed for XDR client [chars], slot [chars], reason: [chars]
Explanation ISSU negotiation failed. This XDR client on this and the remote slot cannot interoperate in SSO mode. Syncing of information to/from this slot will not happen for this and dependent clients. See output of show xdr multicast for full details.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-CLIENTISSU_FOF_REGERROR : ISSU client [chars] ([dec]), entity [dec], message [dec] ([chars]), failed ISSU FOF registration: [chars], reason: [chars],
Explanation This ISSU client has a message containing a foreign field owned by another client and failed to register this dependency.
Recommended Action This error indicates a potential coding problem. It is an error that may occur every time this image is run, and may require a code change to fix it.


%XDR-3-CLIENTISSU_FOF_NEGOFAIL : ISSU negotiation failed for FOF client [int], for peer [chars] (ISSU peer [dec]), blocking ISSU client [chars] ([dec]) reason - [chars]
Explanation ISSU negotiation failed for a client which has registered ISSU FOF client dependencies. The dependent clients on this and the remote slot cannot interoperate in SSO mode. Syncing of information to/from this slot will not happen for this and the dependent clients. See output of show xdr multicast for full details.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-BYPASSFOFNEGO : Bypassing FOF ISSU client [chars] ([int]) nego for XDR client [chars], slot [chars] as FOF ISSU client is not present in [chars] image.
Explanation This XDR client has a dependency on another ISSU client due to having foreign-owned-fields. As the ISSU client that owns the foreign-owned fields is not in the image the XDR client will not wait for that client to finish ISSU negotiation. Appearance of this error message indicates that work is required to add the missing client to the image.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-CLIENTISSU_NEGOREGERROR : XDR client [chars], failed ISSU negotiation result notification registration for ISSU client [chars] ([dec]), reason: [chars],
Explanation This client has dependency on the succesful ISSU negotiation of another client and failed to register this dependency
Recommended Action This error indicates a potential coding problem. It is an error that may occur every time this image is run, and may require a code change to fix it.


%XDR-3-CLIENTISSU_NEGOUNREGERROR : Failed to unregister ISSU negotiation result notification registration for ISSU client [chars] ([dec]), reason: [chars],
Explanation This client has dependency on the succesful ISSU negotiation of another client and failed to unregister this dependency when not required.
Recommended Action This error indicates a potential coding problem. It is an error that may occur every time this image is run, and may require a code change to fix it.


%XDR-6-CLIENTNOTREGONRP : Client [chars] has registered on slot [chars] before RP.
Explanation XDR client has registered on non-RP card before RP card. If this has occurred while toggling the client's registration status rapidly then it may be a transient problem and will resolve itself. If not, then the client's status may be unpredictable, and ISSU negotiation (if platform is ISSU-aware) may not take place correctly.
Recommended Action 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 'show xdr client all' 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, and report it to your technical support representative.


%XDR-3-XDROOS : Received an out of sequence IPC message. Expected [dec] but got [dec] from slot [chars].
Explanation An out of sequence IPC message was received
Recommended Action We weren't meant to get the IPC message we did. From this point onwards IPC can't be relied on. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-CLIENTISSUNOMSGGRP : Cannot determine ISSU message group for slot [dec]. Unknown [chars]
Explanation Not able to determine the set of ISSU messages to be used between local and remote slot, due to not being able to determine linecard type for one or other slot. This might be due to a new linecard type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%XDR-6-XDRREGISTRATION : XDR failed to register [chars] client due to [chars]
Explanation Failure to register the said XDR client.
Recommended Action A failure occured which prohibits the XDR client from registering with the core. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-6-XDRINVALIDHDR : XDR for client ([chars]) dropped (slots:[chars] from slot:[chars] context:[int] length:[int]) due to: [chars]
Explanation The XDR message was dropped for the reason given.
Recommended Action If the failure was due to an invalid context for the CEF push client and occurred during an ISSU upgrade then it may be safely ignored. Otherwise: LOG_STD_ACTION


%XDR-6-XDRINVALIDHDRISSU : XDR ISSU negotiation message for client ([chars]) dropped (slots:[chars] from slot:[chars] context:[int] length:[int]) due to: [chars]
Explanation The XDR ISSU negotiation message was dropped for the reason given.
Recommended Action If the message occurred during an ISSU upgrade then it may be safely ignored. Otherwise: LOG_STD_ACTION


%XDR-6-XDRMCASTINIT : XDR mcast subsystem initilisation error: [chars]
Explanation XDR non functional.
Recommended Action A failure occured which prohibits the XDR client from registering with the core. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-CLIENTISSU_PUSHFAIL : Attempting to push send XDR message ([chars]) to slots [chars] via XDR client [chars] failed due to [chars][chars]
Explanation Internal error. May result in unpredictable behaviour.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-XDRMCASTJOIN : Attempt to join [chars] to [chars] failed because client [chars] returned an error
Explanation Internal error. May result in unpredictable behaviour.
Recommended Action Get the output of show xdr multicast, show xdr client all and show monitor event-trace xdr all. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-XDRMCASTJOINREQ : Client [chars] returned an invalid response to a join request for groups [chars] and [chars]
Explanation Internal error. May result in unpredictable behaviour.
Recommended Action Get the output of show xdr multicast, show xdr client all and show monitor event-trace xdr all. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-MSGSIZEFAIL : The IPC message size is out of bounds The ipc_msg_size is : [dec] while the maximum size we can handle is the XDR_IPC_BUFFER_SIZE : [dec] .
Explanation The size of the IPC message that was received is out of bounds
Recommended Action We were not meant to get the IPC message we did. The size of the IPC message is larger than the maximum size that can be handled. This is probably due to communication incompatibility issues between the active and the standby RPs. Please report it to your technical support representative.


%XDR-3-XDRMCAST_PEER_BINDING : XDR peer [chars] bind to group [chars] (was bound to [chars]): [chars]
Explanation Internal error. May result in unpredictable behaviour.
Recommended Action Get the output of show xdr multicast, and show monitor event-trace xdr all. Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-XDRMCASTGRPINVALID : Invalid XDR multicast group for slot(s) [chars]: [chars]
Explanation Internal error. May result in unpredictable behaviour.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-ILLEGAL_CAP_TYPE : Illegal ISSU capability type ([dec]) for XDR client [chars]
Explanation Capability type requested is invalid. The named XDR client may not function as expected.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-ILLEGAL_CAP_VALUE_CHANGE : ISSU capabilities for peers running same IOS version must be supported.
Explanation Basic assumption is that all peers running the same IOS version as the active RP will support the same ISSU capabilities as the active RP. This is an attempt to mark one such peer as not supporting all capabilities. This will break assumptions in XDR ISSU code and cannot be allowed. The traceback will indicate the offending XDR client.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-MISMATCHED_ISSU_CAPABILITY_INFO : [chars]: [chars]
Explanation ISSU-aware XDR clients may have capabilities to negotiate. They can ask XDR to manage the state of these, but must provide all relevant supporting functions to do so. In this case, the given client has not done so.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-ONINT : Invalid operation [chars] at interrupt level by XDR client [chars]
Explanation Invalid operation at interrupt level
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.


%XDR-3-FRAG_CLIENT_NOT_ALLOWED : Received an XDR fragment from client [chars], slot [chars], which is not allowed to send fragments
Explanation Certain clients are restricted by XDR from fragmenting their data, yet such a fragment was received received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%XDR-3-DATA_TOO_LARGE : Data length [dec] exceeds limit of [dec] bytes
Explanation An attempt was made by a client to send XDR data that was over the given length limit, which caused the send to fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%XDR-4-FAILATTEMPTOPENIPCPORT : Attempt to open the IPC ports failed. [chars]
Explanation XDR failed an attempt to open the IPC port to communicate to the specified peer
Recommended Action No action is required.


ZONE through ZONE

ZONE

%ZONE-4-API : Zone [chars] [chars][chars] [chars] failed to notify the data plane
Explanation The notification of a zone operation has failed to update the data plane and as such the application of the zone information within the object will not be applied to the data plane. It is also possible that the common classification may fail to locate and bind to the zone rendering the configuration inconsistent in terms of application.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show memory command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ZONE-6-CONFIG : Zone security [chars] is removed due to VRF config change on interface [chars]
Explanation The notification of a zone is removed from an interface due to a vrf is removed from the interface
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show running command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ZONE-4-LICENSE : License smart enable and zone-license enable should be enabled first
Explanation The notification indicates that zone smart license should be enabled
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show running command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ZONE-4-BINDING : Zone VPN Bind [chars] [chars] [dec] [chars] failed to notify the data plane
Explanation The notification of a zone vpn operation has failed to update the data plane and as such the application of the zone vpn information within the object will not be applied to the data plane.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show zone security command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.