ISDN through KEYSTORE
ISDN
%ISDN-6-CONNECT : Interface [chars] is now connected to [chars] [chars] | |
---|---|
Explanation | This is an informational message sent when a call is connected. The message displays the remote name and number, which it receives from the Point-to-Point Protocol (PPP) authentication or from where the dialer placed the call to. |
Recommended Action | No action is required. |
%ISDN-6-DISCONNECT : Interface [chars] disconnected from [chars] [chars], call lasted [int] seconds | |
---|---|
Explanation | This is an informational message sent when a call is disconnected. The message displays the remote name and number, which it receives from the Point-to-Point Protocol (PPP) authentication or from where the dialer placed the call to. It also shows how long the call lasted. |
Recommended Action | No action is required. |
%ISDN-1-NOMEMORY : 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. |
%ISDN-4-INVALID_SPID : Interface [chars], Spid[dec] was rejected | |
---|---|
Explanation | The SPID configured in the router has been rejected by the switch. |
Recommended Action | Determine the correct SPID, reenter the SPID and clear the BRI interface. |
%ISDN-4-INVALID_CALLEDNUMBER : Interface [chars], Ignoring call, LDN and Called Party Number mismatch | |
---|---|
Explanation | The incoming ISDN call is ignored because the Called Party Number does not match the LDN numbers configured in the router. |
Recommended Action | Correct the LDN in the router to match the Called Party Number delivered in the incoming setup message. |
%ISDN-4-INVALID_EID : Interface [chars], Ignoring call, EndPoint Identifier (EID) mismatch | |
---|---|
Explanation | The incoming ISDN call is ignored because the EID delivered in the incoming setup message cannot be matched. |
Recommended Action | If EID is delivered in the setup message, use the isdn debugs and show isdn status commands to determine the current EID values. You may need to contact the service provider. |
%ISDN-6-LAYER2UP : Layer 2 for Interface [chars], TEI [int] changed to up | |
---|---|
Explanation | This is an informational message. It is sent when an ISDN Layer2 logical link is up. It also shows the TEI associated with this logical link. |
Recommended Action | No action is required. |
%ISDN-3-LAYER2_UP : Layer 2 for Interface [chars], TEI [int] changed to up | |
---|---|
Explanation | This is an informational message but being logged as an ERR at request from some customers. It is sent when an ISDN Layer2 logical link is up. It also shows the TEI associated with this logical link. |
Recommended Action | No action is required. |
%ISDN-6-LAYER2DOWN : Layer 2 for Interface [chars], TEI [int] changed to down | |
---|---|
Explanation | This is an informational message. It is sent when an ISDN Layer2 logical link is down. It also shows the TEI associated with this logical link. |
Recommended Action | No action is required. |
%ISDN-3-LAYER2_DOWN : Layer 2 for Interface [chars], TEI [int] changed to down | |
---|---|
Explanation | This is an informational message but being logged as ERR at request from some customers. It is sent when an ISDN Layer2 logical link is down. It also shows the TEI associated with this logical link. |
Recommended Action | No action is required. |
%ISDN-6-CHAN_UNAVAILABLE : Interface [chars] Requested Channel [dec] is not available | |
---|---|
Explanation | This is an informational message. It is sent when the requested channel is not available. |
Recommended Action | No action is required. |
%ISDN-6-CALL_COLLISION : Interface [chars] Call Cid [hex] Cref [hex] collision on Channel [dec] in_use_cid [hex] cref [hex], Channel awarded to the received call | |
---|---|
Explanation | This is an informational message. It is sent when a Call is received that collides with an existing call on the same channel. |
Recommended Action | No action is required. |
%ISDN-6-NO_TIMER : No Free Timer Entry, caller [hex], timers used [dec] | |
---|---|
Explanation | This could be an indication of low memory. It is sent when the ISDN protocol cannot start new timers for it's operation. |
Recommended Action | capture the show isdn mem, show isdn status output for possible debugging information. Reduce other system activity to ease the memory demands in the system. |
%ISDN-6-INVALID_TIMER : [chars]: Invalid Timer Handle, caller [hex] handle %3d | |
---|---|
Explanation | This could be an indication of low memory. It is sent when an invalid ISDN timer handle is passed on for timer operations |
Recommended Action | capture the show isdn mem, show isdn status output for possible debugging information. Reduce other system activity to ease the memory demands in the system. |
%ISDN-4-INVALID_EVENT : [chars]: Bad Event Received For Current State | |
---|---|
Explanation | The State Transition for the ISDN L2 Socket Process failed. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (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. |
%ISDN-4-SPURIOUS_CONNECT : [chars]: Spurious Connection Accepted and Closed on port [int] | |
---|---|
Explanation | An unknown TCP connection was accepted and refused. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (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. |
%ISDN-4-GET_STATUS_STATE_FAIL : [chars]: isdn_get_status_state: Unknown DSL [int] | |
---|---|
Explanation | An attempt to retrieve the status of a DSL that is not currently configured. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (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. |
%ISDN-4-ISDN_L2_INTERFACE_NOT_REGISTERED : [chars]: isdn_to_L2: Unknown DSL [int] for command [chars] | |
---|---|
Explanation | The ISDN Stack has not registered its L2 Message Handler |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (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. |
%ISDN-4-BAD_DSL_FOR_CREATE_DELETE_L2 : [chars]: isdn_create_delete_signalling_channel: Unknown DSL [int] for [chars] | |
---|---|
Explanation | The Creation/Deletion service for the L2 Signalling handlerfor the given DSL is missing |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (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. |
%ISDN-4-OPEN_TEMP_SOCKET_FAIL : [chars]: Failed to Open Required Temporary Socket[chars] | |
---|---|
Explanation | The (Re)Open attempt for a required temporary socket failed,without this socket the L2 socket process will fail |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (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. |
%ISDN-4-ISDN_UNEXPECTED_EVENT : [chars]: Occurred at [chars]:[dec] | |
---|---|
Explanation | An unexpected event of significance has occurred |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (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. |
%ISDN-4-RLM_STATUS_CHANGE : ISDN SC [chars]: Status Changed to: [chars]. | |
---|---|
Explanation | ISDN has been notified by the RLM component of a status change in the RLM link |
Recommended Action | No action is required. |
%ISDN-2-ISDN_GENERAL_TRACEBACK : [chars]:[dec] | |
---|---|
Explanation | A debug - traceback condition has occurred |
Recommended Action | No action is required. |
%ISDN-3-ISDN_RESOURCE_UNAVAILABLE : [chars]: Resource not available, at [chars]:[dec] | |
---|---|
Explanation | Hardware resource could not be allocated |
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. |
%ISDN-2-ISDN_FATAL : ISDN FATAL ERROR: file [chars], function [chars], message: [chars] | |
---|---|
Explanation | ISDN has detected a fatal system 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. |
%ISDN-3-ISDN_CCB_FREE : [chars]: CCB with call id [hex] on b channel [dec] was leaked, but has been freed by ISDN Housekeeping. Reason: [chars] | |
---|---|
Explanation | A data structure internal to ISDN has leaked. |
Recommended Action | No action is required. |
%ISDN-3-ISDN_CCB_FREE_FAILS : [chars]: CCB with call id [hex] on b channel [dec] was leaked (reason: [chars]), and can't be free'd by ISDN Housekeeping. | |
---|---|
Explanation | A data structure internal to ISDN has leaked and we can't fix it for some reason. |
Recommended Action | No action is required. |
%ISDN-4-ISDN_CCB_LEAK : [chars]: CCB with callid [hex] on b channel [dec] has been leaked. Reason: [chars] | |
---|---|
Explanation | A data structure internal to ISDN has been leaked |
Recommended Action | No action is required. |
%ISDN-4-SERVICE : Interface [chars] [chars] [chars] message for chan [dec] state [chars] | |
---|---|
Explanation | This is an informational message but will be logged as a warning message if so configured. |
Recommended Action | No action is required. |
%ISDN-4-RESTART : Interface [chars] [chars] [chars] message with restart class of [chars] chan [dec] | |
---|---|
Explanation | This is an informational message but will logged as a warning message if so configured. |
Recommended Action | No action is required. |
%ISDN-4-STATUS : Interface [chars] [chars] [chars] st [hex] ev [hex] cid [hex] cref [hex] | |
---|---|
Explanation | This is an informational message but being logged as a warning message if so configured. |
Recommended Action | No action is required. |
%ISDN-4-SERV_AUDIT_C1 : Interface [chars] service audit trigger condition [dec] on channel [dec] | |
---|---|
Explanation | This is an informational message but will be logged as a warning message if so configured. |
Recommended Action | No action is required. |
%ISDN-5-SERV_AUDIT_C2 : Interface [chars] service audit trigger condition [dec] on channel [dec] | |
---|---|
Explanation | This is an informational message but will be logged as a warning message if so configured. |
Recommended Action | No action is required. |
%ISDN-6-SERV_AUDIT_C3 : Interface [chars] service audit trigger condition [dec] on channel [dec] | |
---|---|
Explanation | This is an informational message but will be logged as a warning message if so configured. |
Recommended Action | No action is required. |
%ISDN-4-ISDN_NLCB_LEAK : [chars]: NLCB leak detected. nlcb [hex] call id [hex] reason: [chars] | |
---|---|
Explanation | A data structure internal to ISDN has not been freed |
Recommended Action | No action is required. |
%ISDN-3-ISDN_NLCB_FREE : [chars]: NLCB with call id [hex] was leaked, but has been freed by ISDN Housekeeping. Reason: [chars] | |
---|---|
Explanation | A data structure internal to ISDN has leaked. |
Recommended Action | No action is required. |
%ISDN-6-REPEATED_SETUP : Interface [chars] Call Cid [hex] Cref [hex] received a retransmitted setup on channel [dec] in_use_cid [hex] cref [hex]. | |
---|---|
Explanation | This is an informational message sent when a duplicate SETUP message is received on a B-channel. This indicates that the rate of calls being received is momentarily greater than the rate calls can be processed. No action is required. |
Recommended Action | No action is required. |
%ISDN-6-NFAS_STATUS_CHANGE : [chars] [chars] [chars] [chars] | |
---|---|
Explanation | The NFAS D-channel status has changed. |
Recommended Action | No action is required. |
%ISDN-2-ISDN_EXIT : [chars] | |
---|---|
Explanation | The ISDN task has terminated execution for the specified reason, and may cause CISCO IOS to terminate. |
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. |
ISR4000_RP_NGIO_ATM
%ISR4000_RP_NGIO_ATM-4-SETUPVC : Interface [chars], VC ([dec]) setup failed, reason = [dec] | |
---|---|
Explanation | A command to setup a VC has failed on RP. |
Recommended Action | The SPA ATM driver has detected a problem creating the internal OAM VC. Reload the indicated SPA card to reconfigure the internal OAM VC. If the error messages persists, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt). |
%ISR4000_RP_NGIO_ATM-4-TEARDOWNVC : Interface [chars], VC ([dec]) teardown failed, (vc state = [dec]/[dec]) | |
---|---|
Explanation | A command to remove a VC config has failed on RP. |
Recommended Action | The SPA ATM driver has detected a problem tearing down the internal OAM VC. Reload the indicated SPA card to do a clean tear down of the internal OAM VC. If the error messages persists, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt). |
%ISR4000_RP_NGIO_ATM-5-MPVCVPSETUP : Interface [chars] has a VC/VP ([dec]) configured already, VC/VP ([dec]) cannot be configured. | |
---|---|
Explanation | The SPA ATM driver supports configuring only one VC/VP under a point to multi point sub-interface. The sub-interface specified in the message already has VP/VC configured. |
Recommended Action | No action is required. |
%ISR4000_RP_NGIO_ATM-3-ATM_FLOWID_GET_FAIL : Failed to get a flow control identifier for interface [chars] for index [dec] | |
---|---|
Explanation | The SPA driver is not able to obtain the datapath flow control identifier for the data path identifier under the interface specified in the message. This indicates a software error. |
Recommended Action | No action is required. |
%ISR4000_RP_NGIO_ATM-3-ATM_DPIDB_ALLOC_FAIL : Failed to allocate a data plane identifier for interface [chars] for VCD [dec] | |
---|---|
Explanation | The SPA driver is not able to allocate the datapath identifier for the VCD under the interface specified in the message. This indicates a software error. |
Recommended Action | No action is required. |
%ISR4000_RP_NGIO_ATM-3-ATM_VC_INGRESS_ID_ALLOC_FAIL : Failed to allocate VC ingress identifier on interface [chars] for VCD [dec] ebfc_id [dec] when [chars] | |
---|---|
Explanation | The ATM SHIM is not able to allocate the ingress identifier for the VCD under the interface specified in the message. This indicates a software error. |
Recommended Action | No action is required. |
%ISR4000_RP_NGIO_ATM-3-ATM_DPIDB_GET_FAIL : Failed to get a data plane identifier for interface [chars] for VCD [dec] | |
---|---|
Explanation | The SPA driver is not able to obtain the datapath identifier for the VCD under the interface specified in the message. This indicates a software error. |
Recommended Action | No action is required. |
%ISR4000_RP_NGIO_ATM-3-ATM_TXCHANL_GET_FAIL : Failed to get a valid tx_chan id for interface [chars] for VCD [dec] | |
---|---|
Explanation | The SPA driver is not able to obtain the datapath tx channel identifier for the VCD under the interface specified in the message. This indicates a SPA occur error. |
Recommended Action | No action is required. |
%ISR4000_RP_NGIO_ATM-3-ATM_VC_SPA_SETUP_FAIL : SPA Error response on interface [chars] when [chars] for VCD [dec] ebfc_id [dec] ret_val [dec] | |
---|---|
Explanation | The SPA give a error response for ATM setup or response timeout in atm vc setup message. This indicates a SPA occur error. |
Recommended Action | No action is required. |
%ISR4000_RP_NGIO_ATM-3-ATM_VC_CFG_SEND_FAIL : Error in sending message to SPA on interface [chars] when [chars] for VCD [dec] ebfc_id [dec] | |
---|---|
Explanation | The SPA give a error response for ATM setup or response timeout in atm vc setup message. This indicates a SPA occur error. |
Recommended Action | No action is required. |
%ISR4000_RP_NGIO_ATM-3-ATM_VC_CORE_GET_FAIL : Failed to get a ATM VC core info for interface [chars] VCD [dec] | |
---|---|
Explanation | Could not get VC core information when get SPA VCOPEN or VCMODIRY response. This indicates a ATM information error. |
Recommended Action | No action is required. |
%ISR4000_RP_NGIO_ATM-3-ATM_VC_ENCAP_GET_FAIL : Failed to get ATM encapsulation for interface [chars] ([dec]/[dec]) VCD [dec] | |
---|---|
Explanation | Could not get VC encapsulation information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error. |
Recommended Action | No action is required. |
%ISR4000_RP_NGIO_ATM-3-ATM_VC_ERROR_ENCAP_TYPE : Get ATM ERROR encapsulation for interface [chars] ([dec]/[dec]) VCD [dec] | |
---|---|
Explanation | Get a ERROR VC encapsulation information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error. |
Recommended Action | No action is required. |
%ISR4000_RP_NGIO_ATM-3-ATM_VC_CON_SET_FAIL : Failed set ATM con for interface [chars] ([dec]/[dec]) VCD [dec] | |
---|---|
Explanation | Could not get VC encapsulation information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error. |
Recommended Action | No action is required. |
%ISR4000_RP_NGIO_ATM-3-ATM_VC_EGRESSID_UPDATE_FAIL : Failed to update ATM egress id for interface [chars] VCD [dec] egress_id [dec] | |
---|---|
Explanation | Could not update VC egress id when get SPA VCOPEN or VCMODFY response This indicates ATM occur error. |
Recommended Action | No action is required. |
%ISR4000_RP_NGIO_ATM-3-ATM_VC_DPIDX_GET_FAIL : Failed to get ATM dpidx for interface [chars] VCD [dec] | |
---|---|
Explanation | Could not get VC dpidx information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error. |
Recommended Action | No action is required. |
%ISR4000_RP_NGIO_ATM-3-PROCESS_FAIL : process creation failed for [chars] | |
---|---|
Explanation | The Periodic one second process creation failed. This indicates a 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. |
%ISR4000_RP_NGIO_ATM-3-ATM_SPA_AUTOVC_FAIL : [chars]: atm autovc discovery configuration failed, reason: [chars] | |
---|---|
Explanation | A command to configure the atm autovc discovery on an atm interface 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. |
%ISR4000_RP_NGIO_ATM-3-ATM_SPA_VC_MAX_LIMIT_REACHED : total active atm vc reached system limitation of [dec] | |
---|---|
Explanation | total number of active atm vc has reached max limit allowed on the system |
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. |
%ISR4000_RP_NGIO_ATM-4-ATM_SPA_VC_ABOVE_WM_WARNING : total active atm vc approaching [int] percent of system limitation of [dec] | |
---|---|
Explanation | total number of active atm vc is approaching the high water mark of sysyem limitation |
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. |
%ISR4000_RP_NGIO_ATM-5-ATM_SPA_VC_BELOW_WM_NOTICE : total active atm vc below [int] percent of system limitation of [dec] | |
---|---|
Explanation | total number of active atm vc below the high water mark of sysyem limitation |
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. |
%ISR4000_RP_NGIO_ATM-3-ATM_PER_SPA_MAX_VC_LIMIT_REACHED : total active atm vc per ATM SPA reached limitation of [dec] | |
---|---|
Explanation | total number of active atm vc per ATM SPA has reached max limit |
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. |
%ISR4000_RP_NGIO_ATM-3-ATM_FLOWID_OUT_OF_RANGE : Flow control identifiers for interface [chars] (chan lo [hex] chan hi [hex]) are out of range, Index [hex] | |
---|---|
Explanation | The flow control identifier received for the interface is out of range. This indicates SPA driver is responding with out of range flow control identifier |
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. |
ISR_THROUGHPUT
%ISR_THROUGHPUT-3-SETUP_FAILED : Throughput upgrade license set up failed | |
---|---|
Explanation | An error occurred when setting up the throughput upgrade licenses. |
Recommended Action |
%ISR_THROUGHPUT-6-LEVEL : Throughput level has been set to [dec]00 kbps | |
---|---|
Explanation | Throughput level has been set to a number |
Recommended Action |
%ISR_THROUGHPUT-6-CRYPTO : Crypto level has been set to [dec]00 kbps | |
---|---|
Explanation | Crypto level has been set to a number |
Recommended Action |
%ISR_THROUGHPUT-6-UNTHROTTLED : Crypto level is unthrottled | |
---|---|
Explanation | Crypto level has been unthrottled |
Recommended Action |
%ISR_THROUGHPUT-3-CONF_FAILED : Configuration failed | |
---|---|
Explanation | An error occurred when the throughput configuration was attempted. |
Recommended Action |
%ISR_THROUGHPUT-3-EULA_NOT_ACCEPTED : The EULA has to be accepted prior to throughput configuration. | |
---|---|
Explanation | Users need to accept EULA to activate the license |
Recommended Action | Accept EULA for throughput license |
%ISR_THROUGHPUT-3-INVALID_CONFIG : An invalid throughput config: [chars] kbps was selected. | |
---|---|
Explanation | The configured throughput is unknown |
Recommended Action |
ISSU
%ISSU-3-BOOT_SYNC : Problem with sync of ISSU boot state - [chars] | |
---|---|
Explanation | The ISSU state between two FRUs is not properly synchronized as a result of a boot error. |
Recommended Action | This message will automatically appear during certain events, such as during a FRU removal or if the FRU loses connectivity. In most cases, the router will resynchronize the ISSU state between the FRUs without any user intervention. If the ISSU state is not resynchronized after multiple attempts, the problem is likely a result of another problem. Monitor the other system messages to see if a more serious issue has occurred on your router. If you are unable to resolve this other issue and this message persists, gather the output of show tech-support and provide it to a Cisco technical support representative. |
%ISSU-0-BOOT_SYNC_FAIL : Problem with sync of ISSU boot state - [chars] | |
---|---|
Explanation | The ISSU state between two FRUs is not properly synchronized as a result of a boot error. |
Recommended Action | This message will automatically appear during certain events, such as during a FRU removal or if the FRU loses connectivity. In most cases, the router will resynchronize the ISSU state between the FRUs without any user intervention. If the ISSU state is not resynchronized after multiple attempts, the problem is likely a result of another problem. Monitor the other system messages to see if a more serious issue has occurred on your router. If you are unable to resolve this other issue and this message persists, gather the output of show tech-support and provide it to a Cisco technical support representative. |
%ISSU-0-PKG_INCONSIST : Reason: [chars] | |
---|---|
Explanation | A software consolidated package or sub-package has an error that indicates the sub-package should not be installed or used. |
Recommended Action | If this message is received, the desired consolidated package or sub-package should not be used. Upgrade using a different consolidated package or sub-package, and report the problem consolidated package or sub-package to Cisco technical support. |
%ISSU-3-INCOMPAT : The packages in [chars] are not consistent | |
---|---|
Explanation | The sub-packages specified for running on the chassis are not compatible with one other. |
Recommended Action | Install a compatible set of packages to allow normal operation. This will require booting a known-good package set. |
%ISSU-3-BOOT_UNCLEAN : Found reload log file, moved to [chars] | |
---|---|
Explanation | A log file was found at bootup indicating that all shutdown tasks were not performed on a previous reload. |
Recommended Action | No user action is necessary. The system will automatically resolve most issues related to the shutdown task as part of the bootup procedure. If a problem related to the tasks that did not shutdown occurs, another error message will occur providing information about that problem. |
%ISSU-5-ISSU_STATE_INVALID : ISSU stored state found invalid and cleaned up: [chars] | |
---|---|
Explanation | The RP has corrected a failed ISSU install state that was detected at bootup. |
Recommended Action | No user action is necessary. This is an informative message indicating that the failed ISSU state has been corrected. |
%ISSU-0-PKG_MNT_SCRIPT_FAIL : Package: [chars] | |
---|---|
Explanation | A consolidated package or sub-package has encountered an error indicating it is not usable. |
Recommended Action | Upgrade your software using a different consolidated package or sub-package. |
%ISSU-5-ISSU_AUTO_ROLLBACK : ISSU rollback timer expired: initiating rollback | |
---|---|
Explanation | An ISSU upgrade has been rolled back because the rollback timer has expired. |
Recommended Action | No user action is needed. If you want to commit the ISSU upgrade, redo the upgrade. Otherwise, this is an informational message only. |
%ISSU-0-SOFTWARE_INVALID : Package for location [chars]: [chars] | |
---|---|
Explanation | The sub-packages have encountered an error related to the structure of the loaded software. |
Recommended Action | This error is likely caused by a failure of the boot or installation process or a corrupted provisioning file. If the system displays error messages related to the boot that can be addressed, address those messages. Downloading new software, if possible, may also help with the problem. If the problem persists, gather the output of show tech-support and provide it to a Cisco technical support representative. |
%ISSU-0-RESET_FRU_FAIL : Problem with ISSU reset of remote FRU - [chars] | |
---|---|
Explanation | After a sub-package installation, one or more FRUs that were upgraded failed to initialize within the timeout period. |
Recommended Action | This problem is more likely to occur in routers with larger configurations, so if your router has a large configuration, you may want to wait a few more minutes to see if your hardware initializes. If the hardware continues to not initialize, reset the FRUs which failed to initialize. If resetting the FRUs fails to resolve the issue, gather the output of show tech-support and contact a Cisco technical support representative. |
%ISSU-3-UCODE_INCOMPAT : Found mismatch for ucode feature - [chars] | |
---|---|
Explanation | During boottime microcode feature version check, a version mismatch was found for this feature. |
Recommended Action | Please ensure that versions of features in microcode are compatible by provisioning a different set of microcode files. |
%ISSU-3-SYNC_ERR : Problem with sync of state - [chars] | |
---|---|
Explanation | The software state between two FRUs or switches is not properly synchronized as a result of a boot error. |
Recommended Action | This message may appear during certain events, such as during a FRU or switch removal or if the FRU or switch loses connectivity. In most cases, the router will resynchronize the software state between the FRUs or switches without any user intervention. If the software state is not resynchronized after multiple attempts, the problem is likely a result of another problem. Monitor the other system messages to see if a more serious issue has occurred on your router. If you are unable to resolve this other issue and this message persists, gather the output of show tech-support and provide it to a Cisco technical support representative. |
IVR
%IVR-3-BAD_IVR_VERSION : Script requires version [dec].[dec], image supports [dec].[dec] | |
---|---|
Explanation | IVR Script requires a higher IVR infrastructure version |
Recommended Action | Upgrade IOS, or use a different script |
%IVR-3-NOSCRIPT : Could not load IVR script [chars] errno=[dec]=[chars] | |
---|---|
Explanation | Could not read in the IVR script |
Recommended Action | Check that script exists on the server, and is readable. |
%IVR-3-BADSCRIPT : Could not parse malformed IVR script: [chars] | |
---|---|
Explanation | Could not parse malformed IVR script |
Recommended Action | Check the script and fix the syntax error. |
%IVR-3-ABNORMAL_EXIT : TCL IVR Process for this call with CallID [dec] exits , bad event: [chars] received | |
---|---|
Explanation | The TCL IVR call process exited for the specified call. The call process did not clear a prior call properly, so other events could not be handled. Only the specified call is affected |
Recommended Action | If problem persists for subsequent calls,copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. |
%IVR-3-LOW_MEMORY : IVR: Sytem running on low memory. Free memory: %l bytes. Call is rejected. | |
---|---|
Explanation | System does not have enough memory to accept calls |
Recommended Action | Check to see what is causing low system memory. |
%IVR-3-LOW_MEMORY_RESOURCE : IVR: System running low on memory ([dec]/100 in use). Call (callID=[dec]) is rejected. | |
---|---|
Explanation | System does not have enough free memory to accept a new call |
Recommended Action | Ensure that the gateway has the recommended amount of memory for this IOS feature set and version. |
%IVR-3-LOW_CPU_RESOURCE : IVR: System experiencing high cpu utilization ([dec]/100). Call (callID=[dec]) is rejected. | |
---|---|
Explanation | System does not have enough CPU resources available to accept a new call |
Recommended Action | Ensure that the call setup rate is within the supported capacity of this gateway. |
%IVR-2-APP_CRIT_R : [chars] | |
---|---|
Explanation | A critical message was reported by an IVR Tcl application. |
Recommended Action | The remedy of the problem is application specific. |
%IVR-3-APP_ERR_R : [chars] | |
---|---|
Explanation | An error message was reported by an IVR Tcl application. |
Recommended Action | The remedy of the problem is application specific. |
%IVR-4-APP_WARN_R : [chars] | |
---|---|
Explanation | A warning message was reported by an IVR Tcl application. |
Recommended Action | The remedy of the problem is application specific. |
%IVR-6-APP_INFO_R : [chars] | |
---|---|
Explanation | An informational message was reported by an IVR Tcl application. |
Recommended Action | The remedy of the problem is application specific. |
%IVR-6-APP_PARALLEL : Cannot use dial-peer [dec] (parallel hunt-group) for a rotary or in a hunt-group call. | |
---|---|
Explanation | The dial-peer for parallel hunt-groups must have a unique pilot number. |
Recommended Action | Create a unique dial-peer destination-number for the parallel hunt-group. |
%IVR-6-APP_SEQ_HUNT : Pilot hunt-group '[chars]' found in hunt-group list. Nested hunt-groups are allowed only as the hunt-group's final number. | |
---|---|
Explanation | Nested sequential hunt-group detected in dial-peer rotary. Nested hunt-groups is unsupported. |
Recommended Action | Do not create hunt-group lists that contain hunt-group pilot numbers. |
%IVR-1-APP_PARALLEL_INVALID_LIST : Call terminated. Huntgroup '[dec]' does not contain enough valid SIP end-points to proceed with a parallel call. | |
---|---|
Explanation | The call to a parallel hunt-group was denied because less than two valid SIP end-points were found in the huntgroup list. |
Recommended Action | Check the hunt-group list's numbers. Remove any incorrect numbers or numbers that have a non-SIP dial-peer. If the numbers are from SIP phones, then verify whether the phones have registered to the system yet. |
%IVR-2-INVALID_DSAPP_DIALPEER : Service dsapp contains an invalid dial peer tag: [chars] | |
---|---|
Explanation | An invalid dial peer tag has been configured for the dsapp service. The tag either is not in the range from 1 to 2147483647, or it belongs to a non-existent dial-peer. |
Recommended Action | Enter the show running-config or the show dial-peer voice command to find a valid dial peer tag. Reconfigure the dial peer with a valid tag or remove the dial peer tag completely to allow the system to match from the system dial peers. |
%IVR-4-INVALID_DSAPP_BLINDTIME : Blind-xfer-wait-time [dec] is invalid. Resetting to [dec] seconds. | |
---|---|
Explanation | The configured value for blind-xfer-wait-time was outside of the acceptable range (0-10) and has been reset to the indicated value. |
Recommended Action | If the new value for blind-xfer-wait-time is unacceptable, you can change it from the command line interface. |
%IVR-4-INVALID_DSAPP_TOGGLE_TIME : Disc-toggle-time [dec] is invalid. Resetting to [dec] seconds. | |
---|---|
Explanation | The configured value for disc-toggle-time was outside of the acceptable range (10-30) and has been reset to the indicated value. |
Recommended Action | If the new value for disc-toggle-time is unacceptable, you can change it from the command line interface. |
%IVR-5-APP_CALL_PREEMPTION : CallID [dec] is being preempted | |
---|---|
Explanation | A notification message was reported by an IVR application on detecting callID %d being preempted. |
Recommended Action | This is not a problem but notifying syslog about preempted call. |
%IVR-2-APP_CRIT : [chars] | |
---|---|
Explanation | A critical message was reported by an IVR Tcl application. |
Recommended Action | The remedy of the problem is application specific. |
%IVR-3-APP_ERR : [chars] | |
---|---|
Explanation | An error message was reported by an IVR Tcl application. |
Recommended Action | The remedy of the problem is application specific. |
%IVR-4-APP_WARN : [chars] | |
---|---|
Explanation | A warning message was reported by an IVR Tcl application. |
Recommended Action | The remedy of the problem is application specific. |
%IVR-6-APP_INFO : [chars] | |
---|---|
Explanation | An informational message was reported by an IVR Tcl application. |
Recommended Action | The remedy of the problem is application specific. |
%IVR-5-APP_MED_INACT_DETECTED : [chars] | |
---|---|
Explanation | A notification message was reported by an IVR application on detecting media inactivity. |
Recommended Action | This is not a problem but notifying syslog about media inactivity. |
%IVR-5-APP_MED_REACT_DETECTED : [chars] | |
---|---|
Explanation | A notification message was reported by an IVR application on detecting media activity. |
Recommended Action | This is not a problem but notifying syslog about media activity. |
%IVR-5-APP_LOG_DUR_CALL_DETECTED : [chars] | |
---|---|
Explanation | A notification message was reported by an IVR application on detecting long duration call. |
Recommended Action | This is not a problem but notifying syslog about long duration call. |
IVR_MSB
%IVR_MSB-3-NOPROMPT : Could not create IVR prompt [chars] errno=[dec]=[chars] | |
---|---|
Explanation | Could not read in the IVR prompt |
Recommended Action | Check that prompt exists on the server, and is readable. |
%IVR_MSB-3-NO_IO_MEMORY : [chars]: Failed to create pool_group [hex] buffer_pool [hex] platform_mc_buf_pool_count [dec] | |
---|---|
Explanation | No IO memory to create IVR private pak pool |
Recommended Action | Check to see if there is enough IO memory. |
%IVR_MSB-3-INVALID_MAX_PROMPTS : [chars]: This version of IOS does not support prompt playout for IVR applications. | |
---|---|
Explanation | This error will be displayed if an IVR application is used on a gateway that does not support IVR prompt playout. |
Recommended Action | Ensure that this platform and IOS version support the IVR feature set. |
%IVR_MSB-3-INVALID_PROMPT_SIZE : [chars]: Bad size for the prompt file [chars]. Read size [dec]. Expected size [dec]. | |
---|---|
Explanation | Prompt file size error. File may be corrupted. |
Recommended Action | Replace the bad prompt file. |
IVR_NOSIGNALING
%IVR_NOSIGNALING-3-LOW_MEMORY_RESOURCE : IVR: System running low on memory ([dec]/100 in use). Application cannot be instantiated. | |
---|---|
Explanation | System does not have enough free memory to spawn a new instance of IVR application |
Recommended Action | Ensure that the gateway has the recommended amount of memory for this IOS feature set and version. |
%IVR_NOSIGNALING-3-LOW_CPU_RESOURCE : IVR: System experiencing high cpu utilization ([dec]/100). Application cannot be instantiated. | |
---|---|
Explanation | System does not have enough CPU capacity to spawn a new instance of IVR application |
Recommended Action | Ensure that the call setup rate is within the supported capacity of this gateway. |
KERBEROS
%KERBEROS-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. |
KEYMAN
%KEYMAN-4-KEYSTR_CRYPTO_TYPE : Type [dec] encryption unknown. Interpreting keystring as literal | |
---|---|
Explanation | The format type was not recognized by the system. A keystring format type value of 0 (unencrypted keystring) or 7 (hidden keystring), followed by a space, can precede the actual keystring to indicate its format. An unknown type value will be accepted, but the system will consider the keystring as being unencrypted. |
Recommended Action | Use the correct format for the value type or remove the space following the value type |
%KEYMAN-4-KEYSTR_BAD_CRYPTO : Bad encrypted keystring for key id [dec]. | |
---|---|
Explanation | The system could not successfully decrypt an encrypted keystring. The keystring may have been corrupted during system configuration. |
Recommended Action | Re-enter the key-string command, and reconfigure the key string. |
KEYSTORE
%KEYSTORE-3-IFS_OPEN_W : Failed to open file [chars] for writing software keystore. ([chars]) | |
---|---|
Explanation | An error occurred while opening a file for persistent storage. CTS keys could not be saved to persistent storage. |
Recommended Action |
%KEYSTORE-3-IFS_WRITE : An error occurred while writing to the software keystore file. | |
---|---|
Explanation | CTS keys could not be saved to persistent storage. |
Recommended Action |
%KEYSTORE-3-IFS_OPEN_R : Failed to open file [chars] for reading software keystore. ([chars]) | |
---|---|
Explanation | An error occurred while opening the keystore file for reading. CTS keys could not be retrieved. |
Recommended Action |
%KEYSTORE-3-IFS_READ : An error ([chars]) occurred while reading from the software keystore file. | |
---|---|
Explanation | CTS keys could not be retrieved from persistent storage. |
Recommended Action |
%KEYSTORE-3-BAD_MAGIC : Bad magic number [hex] in software keystore file [chars]. | |
---|---|
Explanation | Keystore data file appears to have been corrupted. Keys can not be retrieved from persistent memory. |
Recommended Action |
%KEYSTORE-3-UNEXPECTED_EOF : Unexpected end of file while reading software keystore [chars]. | |
---|---|
Explanation | Keystore data file appears to have been truncated. One or more keys can not be retrieved from persistent memory. |
Recommended Action |
%KEYSTORE-3-IPCPORT : Failed to create IPC port ([chars]) for keystore redundancy. [chars]. | |
---|---|
Explanation | An error was encountered when trying to create an IPC port. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
Recommended Action |
%KEYSTORE-3-IPCOPEN : Failed to open IPC port to peer for keystore redundancy: [chars] | |
---|---|
Explanation | An error was encountered when trying to open an IPC port for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
Recommended Action |
%KEYSTORE-3-IPCNOCONN : No IPC communication path to peer available for keystore [chars]. | |
---|---|
Explanation | No IPC connection to the peer was available for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
Recommended Action |
%KEYSTORE-3-IPCSEND : IPC send error ([chars]) while sending [chars]. | |
---|---|
Explanation | An error occurred while sending an IPC message to the peer during a keystore redundancy operation. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
Recommended Action |
%KEYSTORE-3-ISSU_INCOMPAT : Standby incompatible for SSO. | |
---|---|
Explanation | The image on the standby failed ISSU message version negotiation. As a result, we will not be able to sync keystore updates to it and so it is disallowed from reaching hot standby status in SSO mode. |
Recommended Action |
%KEYSTORE-3-IPC_NO_PROC : Could not create a process to receive keystore redundancy messages. | |
---|---|
Explanation | An error was encountered when trying to create a process to handle incoming keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore. |
Recommended Action |
%KEYSTORE-3-NO_KEYSTORE : CTS hardware keystore is not responsive and software emulation is not enabled. | |
---|---|
Explanation | The CTS hardware keystore on the switch has failed and needs to be inspected. Since CTS credentials are stored in the keystore, this means that CTS authentication and authorization operations will fail. The following action is recommended: If the defect is shown on the Active Supervisor, try to switchover to Standby Supervisor. If the defect is shown on Standby Supervisor, try to reset the Standby. If the defect persists, there may be damage to the hardware keystore chip, please take appropriate action. In the meantime, you can configure the switch to use software keystore emulation. After you have enabled software keystore emulation, please re-configure CTS credentials to populate the software keystore. |
Recommended Action |