-
Cisco IOS System Error Messages, Volume 2 of 2
-
About Cisco IOS Software
-
System Error Messages Overview
-
NPS_APS through POSDW
-
POSLC through PQUICC_ETHER
-
PQUICC_ETHERNET through RESOURCE_MON
-
RESYNCH through SDLC
-
SDLLC through SNAPSHOT
-
SNASW
-
SNMP through SW_VLAN
-
SYS through TCP
-
TDM through TXCONN
-
UBR7200 through VPD
-
VPDN through XTAGATM
-
CMCC System Error Messages
-
CMCC-ADAPTER
-
CMCC-BSQ through CMCC-DEBUGGER
-
CMCC-DIAG through CMCC-NEVADA
-
CMCC-OFFL through CMCC-XCPA
-
System Failure Messages
-
Glossary of Acronyms
-
Index
-
Table Of Contents
SNMP Messages
The following are Simple Network Management Protocol (SNMP) error messages.
Error Message%SNMP-3-AUTHFAIL : Authentication failure for SNMP req from host [dec].[dec].[dec].[dec]
Explanation An SNMP request was sent by the host at the address [dec].[dec].[dec].[dec], but the request PDU was not properly authenticated.
Recommended Action Make sure that the community and user name that are used in the SNMP request from the remote host have been configured on the router.
Error Message%SNMP-3-BADOID : Attempt to generate an invalid object identifier
Explanation An attempt has been made to generate an object identifier that has fewer than two subidentifiers. A valid object identifier must contain at least two subidentifiers.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SNMP-3-BADVALUE : Maximum number of index supported is 20
Explanation An attempt has been made to generate an SNMP trap containing an MIB object whose instance identifier size has exceeded the maximum size. An SNMP trap contains some number of MIB objects, and the size of the instance identifier for these objects is restricted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SNMP-3-CPUHOG : Processing [chars] of [chars]
Explanation SNMP has taken too much time to process a request.
Recommended Action If conditions warrant, use the debug snmp packet command to determine the contents of the SNMP request that is causing the message. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP-4-NOENGINEID : Remote snmpEngineID for [IP_address] not found when creating user: [chars]
Explanation An attempt to create a user has failed. This condition likely has occurred because the engine ID of the remote agent or SNMP Manager was not configured.
Recommended Action Configure the remote snmpEngineID and reconfigure the user. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP-4-NOFLASH : Reading snmpEngineBoots from flash failed
Explanation An attempt to read the snmpEngineBoots file from the Flash memory has failed. This condition most likely has occurred because the Flash memory card does not exist on the router. This message should appear only when the router is reloaded.
Recommended Action If a Flash memory card does not exist on the router, install a Flash memory card. If a Flash memory card exists already, its memory may be full. Erase the Flash memory and reload the router. If, after performing these steps, the problem persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP-3-TRAPBLOCK : Attempt to generate SNMP trap from a process with blocking disabled
Explanation During processing, a process with blocking disabled attempted to generate an SNMP trap that would block. A process that is configured this way is not allowed to use this function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP-4-TRAPDROP : [chars]
Explanation An attempt was made to generate an SNMP trap, but the trap could not be sent. This condition most likely has occurred because the SNMP traps process is not running. More information will be given in the error message.
Recommended Action Use the show process command to determine whether the SNMP traps process is running. If the SNMP traps process is not running, reload the system. If, after reloading, the SNMP traps process is still not running, there may not be enough memory for it to run. If the steps described previously do not resolve the problem, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP-3-TRAPINTR : Attempt to generate SNMP trap from interrupt level
Explanation The code attempted to generate an SNMP trap during the processing of an interrupt. This function is not allowed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP-5-WARMSTART : SNMP agent on host [chars] is undergoing a warm start
Explanation The SNMP server was restarted.
Recommended Action This is a notification message only. No action is required.
SNMP_MGR Messages
The following are Simple Network Management Protocol (SNMP) proxy error messages.
Error Message%SNMP_MGR-3-BADAGETIMER : Unexpected age timer found on session [hex]
Explanation The system has found an internal timer that should not be running.
Recommended Action Disable the SNMP Manager by entering the no snmp-server manager command. Then reenable the SNMP Manager by entering the snmp-server manager command. Entering these commands should effectively reset all of the internal structures. If entering this command sequence does not adequately resolve the problem, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP_MGR-4-BADAUTHTYPE : Unsupported SNMP authorization type: [int]
Explanation The system has found an unknown SNMP authorization type. This condition may prevent the SNMP Manager from correctly sending and receiving SNMP messages to or from a particular SNMP agent.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP_MGR-3-BADINFORMTRANSPORT : Unknown inform transport type: [chars]
Explanation The destination of the specified SNMP inform has used an unknown transport type. The inform notification cannot be sent to the specified destination.
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. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SNMP_MGR-3-BADOP : Unknown operation code [int]
Explanation An SNMP PDU that has been delivered to the SNMP Manager contains an unknown operation code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP_MGR-3-BADPDUTYPE : Received unknown PDU type: [int]
Explanation A PDU of an unknown type has been delivered to the SNMP Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP_MGR-4-BADRESPONSESTATUS : Unknown response status code: [int]
Explanation The SNMP Manager process has received an internal response with an unknown status code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP_MGR-3-BADTRANSPORT : Unknown transport type: [int]
Explanation A PDU from an unknown transport type has been delivered to the SNMP Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP_MGR-3-BADUSECOUNT : Corrupted use counter found on session [hex]
Explanation A cached SNMP session structure might have been corrupted.
Recommended Action Disable the SNMP Manager by entering the no snmp-server manager command. Then reenable the SNMP Manager by entering the snmp-server manager command. Entering these commands should effectively reset all of the internal structures. If entering this command sequence does not adequately resolve the problem, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP_MGR-4-EMPTYQUEUE : Input queue is empty
Explanation The SNMP Manager process has received a notification to process its input queue, but the SNMP Manager process found the queue to be empty.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP_MGR-3-MISSINGHOST : Cannot locate information on SNMP informs host: [IP_address]
Explanation The system cannot locate configuration information about an SNMP informs host. The "informs destination" table entry for the specified SNMP cannot be found, and inform notifications will not be sent to this destination.
Recommended Action Enter the show snmp host and show snmp commands. Delete and readd the informs destination by entering the snmp-server host global configuration command to attempt to clear the condition. If entering this command fails to clear the condition, and you cannot determine the nature of the error from the error message text or from the show snmp host and show snmp command output, contact your Cisco technical support representative and provide the representative with the gathered information. Reloading the system may be necessary.
Error Message%SNMP_MGR-4-NOCANCEL : Unable to cancel a previously sent inform request.
Explanation The number of unacknowledged inform requests issued has reached the configured maximum limit. To make resources available for sending out a new inform request, one of the older inform requests must be cancelled. The algorithm that is used to choose which inform request is the most appropriate one to cancel has failed to choose any. The new inform request will not be sent, and it will be dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP_MGR-3-NOPROC : Failed to create SNMP Manager process
Explanation The system was unable to initialize the SNMP Manager process. This condition is most likely due to a lack of memory.
Recommended Action Use the show memory command to examine the amount of available memory. If free memory is low, you may need to reconfigure or reload the system. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SNMP_MGR-4-NOTENABLED : SNMP Manager not enabled (requested by [chars])
Explanation A Cisco IOS application is attempting to use the SNMP Manager services, but the SNMP Manager functionality has not been enabled.
Recommended Action Enter the snmp-server manager command in global configuration mode to enable SNMP Manager services. The Cisco IOS application that is requesting these services is specified in the message. Alternatively, if it is not necessary for the Cisco IOS application that is requesting these services to use SNMP Manager services, disable or reconfigure the specified application so that it no longer makes SNMP Manager requests.
Error Message%SNMP_MGR-3-RESPDROP : Insufficient memory to handle response to request id [int]
Explanation An SNMP response PDU has been received from a Cisco IOS application. There is not enough memory available to cache the response and return it to the original requesting Cisco IOS application. If this was a transient problem, the original SNMP request will likely be resent, and another SNMP response will be returned and delivered to the original Cisco IOS application that made the request.
Recommended Action If this message recurs, you will be required to free up some memory for the SNMP Manager to function. Enter the show memory command to determine if the available memory is low. You may be required to reconfigure or reload the system to make more memory available. Alternatively, you can disable the SNMP Manager by entering the no snmp-server manager command.
Error Message%SNMP_MGR-3-SESSIONINUSE : Attempt to destroy session [hex] that is still in use
Explanation An attempt has been made to remove a cached SNMP session structure, but the session is still in use and should not be removed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
SOI Messages
The following are Simple Network Management Protocol (SNMP) over interprocess communication (IPC) error messages.
Error Message%SOI-2-BADPXMCOMMUNITY : PXM's community string (length [dec]) was invalid. Limits are [dec] to [dec].
Explanation The system has received an invalid PXM community string.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SOI-2-BADPXMIPADDR : PXM's IP address (length [dec]) was invalid. Must be [dec].
Explanation The system has received an invalid PXM IP address.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SOI-2-BADPXMMESSAGE : Message from PXM had a type [dec] which is unknown.
Explanation The system has received an unknown message from the PXM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SOI-2-PORTCREERR : Unable to create the SNMP Over IPC comm port [chars] to the PXM.
Explanation An attempt to create a communication port to the PXM has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SOI-2-PORTLOCERR : Unable to locate the SNMP Over IPC comm port [chars] to the PXM.
Explanation An attempt to locate an already open port to the PXM has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SOI-2-PORTOPENERR : Unable to open the SNMP Over IPC comm port [chars] to the PXM.
Explanation An attempt to open a communication port to the PXM has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SOI-2-PORTREGFAIL : SNMP Over IPC : IPC Port registry for port [chars] failed.
Explanation An SNMP over IPC request to register an IPC port has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SOI-2-QUEUCREATFAIL : Unable to create the SNMP over IPC watched queue.
Explanation An SNMP over IPC watched queue could not be created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
SONET Messages
The following are Synchronous Optical Network (SONET) error messages.
Error Message%SONET-4-ALARM : [chars]: [chars] [chars]
Explanation The specified SONET alarm has been declared or released.
Recommended Action Repair the source of the alarm.
Error Message%SONET-3-APSCOMM : [chars]: [chars]
Explanation An APS error related to connectivity between the working and the protect routers has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SONET-3-APSCOMMEST : [chars]: Link to [chars] channel established - protocol version [dec]
Explanation APS has established connectivity between the working and protect routers.
Recommended Action This is an informational message only. No action is required.
Error Message%SONET-3-APSCOMMLOST : [chars]: Link to [chars] channel lost
Explanation Connectivity between the working and protect routers has been lost. APS operation is able to continue in degraded mode.
Recommended Action Restore connectivity between the working and protect routers.
Error Message%SONET-4-APSMM : APS mode mismatch - [chars]
Explanation A unidirectional/bidirectional mismatch has been detected by the APS system.
Recommended Action Match the router configuration with the provisioned circuit.
Error Message%SONET-3-APSNCHN : APS Local request [dec] has no corresponding channel number
Explanation The APS software has malfunctioned.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SONET-3-APSNOINTFC : APS No interfaces available for IP connection
Explanation APS requires an out-of-band path for interrouter communication.
Recommended Action Configure an out-of-band path for interrouter APS communication.
Error Message%SONET-3-BADAUTH : APS Bad authentication from [IP_address],
Explanation The APS software has detected an unauthorized message. This message could result from improper configuration, unauthorized access, or packet corruption.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SONET-3-BADVER : APS version mismatch; this system ver [dec]; other ver [dec] - msg rejected:
Explanation The APS software has detected an invalid version number in the hello message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SONET-3-MISVER : [chars]: APS version mismatch.
WARNING: Loss of Working-Protect link can deselect both
protect and working interfaces. [chars] router requires
software upgrade for full protection.Explanation The APS software has detected that either the working or the protect router requires a software upgrade. APS operation can continue prior to the upgrade.
Recommended Action Upgrade the specified router.
Error Message%SONET-3-NOBUFFER : No buffer available for sending APS message
Explanation No data buffer was available to send an APS message.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SONET-3-NOSOCKET : Unable to open socket
Explanation The APS system was unable to open a socket for communication purposes.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
SONETMIB Messages
The following are Synchronous Optical Network (SONET) Management Information Base (MIB) error messages.
Error Message%SONETMIB-1-DELETE : could not delete interface, if_index=[dec]
Explanation The specified interface was not removed from the queue successfully.
Recommended Action No action is required.
Error Message%SONETMIB-1-MALLOCNEW : Malloc failed for new interface=[dec]
Explanation The system was unable to allocate enough memory to create a SONET MIB structure for the new interface.
Recommended Action No action is required.
Error Message%SONETMIB-3-NULLCFGPTR : NULL SONET MIB config pointer, if_index=[dec]
Explanation The system has attempted to initialize the SONET MIB using a NULL pointer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
SONICT Messages
The following are SONIC Ethernet interface-related error messages.
Error Message%SONICT-1-INITFAIL : Unit [dec], initialization timeout failure, csr[dec]=[hex]
Explanation A failure has occurred in the initialization sequence of the sonicT chip.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show cont e0/0/x command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show cont e0/0/x output, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SONICT-2-NOMEMORY : Unit [dec], no memory for [chars]
Explanation An operation could not be accomplished because of a low memory condition. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the system memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
SPAN Messages
The following are Spanning Tree Protocol error messages.
Error Message%SPAN-4-DST_ALREADY_DST : Interface(s) [chars] already configured as monitor destinations in other monitor sesssions
Explanation The specified interface or interfaces are already configured as a monitor destination in another monitor session and will be ignored. All other monitor destinations that are being configured are applied.
Recommended Action Choose a SPAN destination interface that is not a SPAN destination in any other SPAN session, or remove the SPAN destination configuration from another session before configuring it as a SPAN source interface.
Error Message%SPAN-4-DST_ALREADY_SRC : Interface(s) [chars] already configured as monitor sources
Explanation The specified interface or interfaces are already configured as a monitor source in this or another monitor session and will be ignored. All other monitor destinations that are being configured are applied.
Recommended Action Choose a SPAN destination interface that is not a SPAN source in any SPAN session, or remove the SPAN source configuration before configuring it as a SPAN destination interface.
Error Message%SPAN-4-FTR_ALREADY_SRC : Configuring filter VLANs [chars], but there are already source VLANs configured.
Explanation Filter VLANs are being configured, but source VLANs are already configured in the same monitoring session. Filter VLANs and source VLANs are not allowed to be configured at the same time.
Recommended Action Choose a SPAN filter VLAN that is not already a SPAN source VLAN, or remove the SPAN source VLAN configuration before configuring a SPAN filter VLAN.
Error Message%SPAN-3-MEM_UNAVAIL : Memory was not available to perform the SPAN operation
Explanation The system was unable to perform a SPAN operation because of a lack of memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%SPAN-4-RXOVFL : This platform allows a maximum of [dec] RX monitor interface(s)
Explanation The number of interfaces that are being monitored in the RX direction exceeds the maximum number allowed on this platform. All interfaces beyond the number allowed are ignored.
Recommended Action Be aware that not all interfaces requested to be configured were actually configured. Enter the show monitor command in EXEC mode to see which interfaces were actually configured.
Error Message%SPAN-4-SRC_ALREADY_DST : Interface(s) [chars] already configured as monitor destinations
Explanation At least one interface that is being configured as a monitor source is ignored because it is already configured as a monitor destination in this or another monitor session. All other monitor destinations that are being configured are applied.
Recommended Action Choose a SPAN source interface that is not a SPAN destination in any SPAN session, or remove the SPAN destination configuration from the interface before configuring it as a SPAN source interface.
Error Message%SPAN-4-SRC_ALREADY_FTR : Configuring source VLANs [chars], but there are already filter VLANs configured.
Explanation Source VLANs are being configured, but filter VLANs are already configured in the same monitoring session. Filter VLANs and source VLANs are not allowed to be configured at the same time.
Recommended Action Choose a SPAN source VLAN that is not already a SPAN filter VLAN, or remove the SPAN filter VLAN configuration before configuring a SPAN source VLAN.
Error Message%SPAN-4-TXOVFL : This platform allows a maximum of [dec] TX monitor interface(s)
Explanation The number of interfaces being monitored in the TX direction exceeds the maximum number allowed on this platform. All interfaces beyond the number allowed are ignored.
Recommended Action Be aware that not all interfaces requested to be configured were actually configured. Enter the show monitor command in EXEC mode to see which interfaces were actually configured.
Error Message%SPAN-3-UNKN_ERR : An internal error occurred during a SPAN operation.
Explanation SPAN has detected an error in its internal operation.
Recommended Action The error might be transient, and retrying the SPAN operation might be successful. If retrying the SPAN operation fails, the switch might need to be reloaded to complete the desired operation.
Error Message%SPAN-3-UNKN_ERR_PORT : An internal error occurred when configuring SPAN on port [chars]
Explanation SPAN has detected an error in its internal operation.
Recommended Action The error might be transient, and retrying the SPAN operation might be successful. If retrying the SPAN operation fails, the switch might need to be reloaded to complete the desired operation.
SPANTREE Messages
The following are Spanning Tree error messages.
Error Message%SPANTREE-7-BLOCK_PORT_TYPE : Blocking [chars] on [chars]. Inconsistent port type.
Explanation The specified interface has an inconsistent port type and is being held in a spanning-tree blocking state until the port type inconsistency is resolved.
Recommended Action Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected have the same mode (access or trunk). If the mode is trunk, verify that both interfaces use the same encapsulation (ISL or 802.1Q). When these parameters are consistent, spanning tree will automatically unblock the interfaces as appropriate.
Error Message%SPANTREE-2-BLOCK_PVID_LOCAL : Blocking [chars] on [chars]. Inconsistent local vlan.
Explanation The spanning-tree port with the specified spanning-tree instance and interface has a port VLAN ID inconsistency and will be held in spanning-tree blocking state until the port VLAN ID inconsistency is resolved. The specified spanning-tree instance is that of the native VLAN ID of the specified interface.
Recommended Action Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. Once the configuration is corrected, spanning tree will automatically unblock the interfaces as appropriate.
Error Message%SPANTREE-2-BLOCK_PVID_PEER : Blocking [chars] on [chars]. Inconsistent peer vlan.
Explanation The spanning-tree port with the specified spanning-tree instance and interface has a port VLAN ID inconsistency and will be held in spanning-tree blocking state until the port VLAN ID inconsistency is resolved. The specified spanning-tree instance is that of the native VLAN ID of the interface on the peer switch to which the specified interface is connected.
Recommended Action Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. Once the configuration is corrected, spanning tree will automatically unblock the interfaces as appropriate.
Error Message%SPANTREE-3-PORT_SELF_LOOPED : [chars] disabled.- received BPDU src mac ([enet]) same as that of interface
Explanation The source MAC address contained in a BPDU that was received on the specified interface matches the MAC address assigned to that interface This indicates that a port may be looped back to itself. This condition might be caused by a diagnostic cable that is being plugged in. The interface will be administratively shutdown.
Recommended Action Check the interface configuration and any cable plugged into the interface. Once the problem is resolved, reenable the interface by entering the no shutdown command in interface configuration mode.
Error Message%SPANTREE-2-RECV_1Q_NON_1QTRUNK : Received 802.1Q BPDU on non 802.1Q trunk [chars] [chars].
Explanation The specified interface on which an SSTP BPDU was received was in trunk mode, but the specified interface was not using 802.1Q encapsulation.
Recommended Action Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected have the same mode (access or trunk). If the mode is trunk, verify that both interfaces use the same encapsulation (ISL or 802.1Q).Once these parameters are consistent, spanning tree will automatically unblock the interfaces as appropriate.
Error Message%SPANTREE-7-RECV_1Q_NON_TRUNK : Received 802.1Q BPDU on non trunk [chars] [chars].
Explanation An SSTP BPDU that was not operationally a trunk has been received on the specified interface.
Recommended Action Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected have the same mode (access or trunk). If the mode is trunk, verify the same encapsulation (none, ISL or 802.1Q). Once these parameters are consistent, spanning tree will automatically unblock the interfaces as appropriate.
Error Message%SPANTREE-2-RECV_BAD_TLV : Received SSTP BPDU with bad TLV on [chars] [chars].
Explanation The specified interface has received a SSTP BPDU that was missing the VLAN ID tag. The BPDU is discarded.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SPANTREE-2-RECV_PVID_ERR : Received BPDU with inconsistent peer vlan id [dec] on [chars] [chars].
Explanation The specified interface has received an SSTP BPDU that is tagged with a VLAN ID that does not match the VLAN ID on which the BPDU was received. This condition occurs when the native VLAN is not consistently configured on both ends of a 802.1Q trunk.
Recommended Action Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. Once this inconsistency is corrected, spanning tree will automatically unblock the interfaces as appropriate.
Error Message%SPANTREE-2-RX_PORTFAST : Received BPDU on PortFast enabled port. Disabling [chars].
Explanation A BPDU that has spanning-tree portfast enabled was received on the specified interface. Since the Spanning Tree BPDU Guard is also enabled, the interface is administratively shutdown.
Recommended Action Verify the configuration of portfast on the interface. If portfast behavior is desired, verify that the interface is connected to a host or router only and not to a bridge or a switch. After resolving the conflict, reenable the interface by entering the no shutdown command in interface configuration mode.
Error Message%SPANTREE-2-UNBLOCK_CONSIST_PORT : Unblocking [chars] on [chars]. Port consistency restored.
Explanation The Port VLAN ID and/or Port Type inconsistencies have been resolved. Spanning tree will now unblock the specified interface of the specified spanning-tree instance as appropriate.
Recommended Action No action is required.
SPANTREE_FAST Messages
The following are Spanning Tree Fast Convergence error messages.
Error Message%SPANTREE_FAST-7-PORT_FWD_UPLINK : [chars] [chars] moved to Forwarding (UplinkFast).
Explanation The specified interface has been selected as the new root port for the listed spanning-tree instance.
Recommended Action No action is required.
SPARC Messages
The following are Cisco 3800 SPARC coprocessor subsystem error messages.
Error Message%SPARC-3-DOWN : SPARC process is not responding, [chars]
Explanation The SPARC coprocessor subsystem is not responding to configuration commands. The SPARC coprocessor will be restarted automatically when this condition occurs. This is not a normal condition. Recurrence of the problem could indicate a hardware failure.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
SPE Messages
The following are Service Processing Element (SPE) error messages.
Error Message%SPE-3-MSMGR_REGISTRATION_ERR : Failed to register [chars] with Modem Service Manager
Explanation Port Management has failed to register with the Modem Service Manager.
Recommended Action No action is required.
Error Message%SPE-6-NULL_OBJ : SPE object [chars] is unavailable.
Explanation Information about the specified SPE could not be retrieved. The SPE may not exist.
Recommended Action No action is required.
Error Message%SPE-3-PM_DB_NO_MEM : Failed to allocate [chars] for slot [dec]
Explanation Port Management has failed to allocate memory to create a slot object.
Recommended Action No action is required.
Error Message%SPE-3-PM_DIRECT_MODEM_QUERY_ERR : Failed to find the response buffer for modem [chars] command
Explanation Modem direct query responses could not find a buffer to send data to the router shelf.
Recommended Action No action is required.
Error Message%SPE-3-PM_SLOT_NO_MODULES : Database reported 0 modules for slot [dec]
Explanation The card in this slot should contain multiple modules. However, the database indicates that the card in this slot contains no modules.
Recommended Action No action is required.
Error Message%SPE-3-RECOVERY_DNLD_MAINT_NO_MEM : Recovery Download Maintenance ran out of chunk memory; [chars]
Explanation The Recovery Download Maintenance messages cannot be sent.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SPE-6-SM_BUSIEDOUT : SPE [chars] busiedout(maintenance will be allowed)
Explanation The SPE is temporarily taken out of service. Maintenance activities can still be performed.
Recommended Action No action is required.
Error Message%SPE-6-SM_CLEARED : SPE [chars] Cleared
Explanation The SPE will be redownloaded with the configured firmware.
Recommended Action No action is required.
Error Message%SPE-3-SM_CRASHED : SPE [chars] crashed
Explanation The firmware running on the SPE has been aborted.
Recommended Action No action is required.
Error Message%SPE-6-SM_DEFER_DOWNLOAD : SPE [chars] : Firmware download deferred
Explanation The firmware download for the SPE is postponed due to active calls.
Recommended Action No action is required.
Error Message%SPE-3-SM_DOWNLOAD_FAILED : SPE [chars] is BAD - [chars].
Explanation The SPE has failed to download, and it will be marked as bad.
Recommended Action No action is required.
Error Message%SPE-3-SM_EVENT_NO_MEM : SPE SM out of event buffers; [chars] [chars]
Explanation The PM SPE state machine has run out of event memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SPE-3-SM_POST_FAILED : SPE [chars] is BAD.
Explanation The SPE has failed the POST, and it will be marked as bad.
Recommended Action No action is required.
Error Message%SPE-3-SM_RESPONSE_NO_MEM : SPE SM out of response buffers
Explanation The PM SPE state machine has run out of response event memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SPE-6-SM_SHUTDOWN : SPE [chars] shutdown
Explanation The SPE has been taken out of service. Maintenance activities cannot be performed.
Recommended Action No action is required.
Error Message%SPE-6-SM_START_DOWNLOAD : SPE [chars] : Firmware download initiated
Explanation Firmware download for the SPE has been initiated.
Recommended Action No action is required.
Error Message%SPE-4-SPE_ACT_SESS_WARN : Active session count = [dec]. Country code not set
Explanation The country code cannot be set on a system with active sessions.
Recommended Action No action is required.
Error Message%SPE-4-SPE_CONFIG_WARN : Country Code Trunk card mismatch for.
Explanation A country code that was configured may not work with the trunk card.
Recommended Action No action is required.
Error Message%SPE-6-SPE_DNLD_MAINT : [chars] [chars]
Explanation This message provides information about the download maintenance that is running.
Recommended Action This is an informational message only. No action is required.
Error Message%SPE-6-SPE_DNLD_MAINT_PROCESS : [chars]
Explanation This message provides information about the download maintenance process.
Recommended Action This is an informational message only. No action is required.
Error Message%SPE-3-ST_API_ERR : PM failed to create [chars].
Explanation Port Management has failed to initialize the CSM event processing component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SPE-3-ST_EVENT_NO_MEM : PM ST failed to create [chars].
Explanation Port Management has failed to allocate dynamic chunk memory for event logging.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
SRCP_APP Messages
The following are Simple Resource Coordination Protocol (SRCP) application error messages.
Error Message%SRCP_APP-6-DNS_QUEUE_FAILED : Failed to create DNS message watched queue\n
Explanation The system has failed to create a DNS message watched queue.
Recommended Action Check free memory size to ensure that there is enough memory to perform the requested operation. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%SRCP_APP-6-PROCESS_CREATION_FAILED : Cannot create SRCP application process\n
Explanation The system has failed to create the SRCP application process.
Recommended Action Check free memory size to ensure that there is enough memory to perform the requested operation. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%SRCP_APP-6-SOCKET_OPEN_FAILED : Failed to open UDP port for SRCP\n
Explanation The system has failed to open a UDP port for the SRCP process.
Recommended Action Check if any other applications use the same UDP port number (2427).
Error Message%SRCP_APP-6-SYS_QUEUE_FAILED : Failed to create SRCP system message watched queue\n
Explanation The system has failed to create an SRCP system message watched queue.
Recommended Action Check free memory size to ensure that there is enough memory to perform the requested operation. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
SRP Messages
The following are Spatial Reuse Protocol (SRP) error messages.
Error Message%SRP-4-ALARM : [chars] Side [char] Keepalive [chars]
Explanation The specified network has a physical line error condition.
Recommended Action Diagnose and repair the physical error.
Error Message%SRP-3-DUP_MAC_ADDR : [chars] : Duplicate mac addresses in topology
Explanation The topology contains one or more duplicate MAC addresses.
Recommended Action Identify the duplicate address and correct the configuration.
Error Message%SRP-3-RING_ID_ERROR : [chars] : Rx side [chars], Tx side of fiber originates on side [chars]
Explanation The fiber on the specified side is remotely connected to the wrong side.
Recommended Action Verify that each side A is connected to side B and that each side B is connected to side A.
Error Message%SRP-3-SINGLE_NODE_TOPO : [chars] : Single node in topology
Explanation The topology discovery has resulted in a single node being found.
Recommended Action This condition can be caused by duplicate MAC addresses. Identify the MAC address of the interface and ensure it is not duplicated on other nodes. If the node is in loopback, disregard this message.
SSE Messages
The following are silicon switching engine (SSE) error messages.
Error Message%SSE-3-BADMEMORY : SSE memory failure detected, orig [hex] [hex], tested [hex] [hex]
Explanation A memory error 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. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SSE-2-BOGUSEQ : SSE bogus equal branch [hex], [hex], [dec] [hex]
Explanation The data structures that are used by the SSE have an internal inconsistency.
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. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SSE-3-COMPERR : SSE compilation failure -- [chars]
Explanation A software failure 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. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SSE-2-HUNG : SSE hung -- [chars]
Explanation The SSE has locked up.
Recommended Action Reboot the SSE.
Error Message%SSE-2-HWFAILURE : SSE hardware failure -- [chars] code [hex]
Explanation A hardware error has occurred. This condition indicates an unexpected condition on the Silicon Switch Processor (SSP) board.
Recommended Action It might be necessary to replace the SSP. 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. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SSE-2-MEMERROR : SSE memory failure, address [hex],
expected [hex], got [hex]Explanation A hardware error has occurred. This condition indicates a memory failure on the Silicon Switch Processor (SSP) board.
Recommended Action It might be necessary to replace the SSP. 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. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SSE-2-NESTADDR : SSE nested addresses detected, protocol [dec] [IP_address]
Explanation The data structures used by the SSE have an internal inconsistency.
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. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SSE-2-NOMATCH : SSE delete didn't end at a match node, type [char],value [dec], address [IP_address], bytecount [dec], high [dec], state [dec]
Explanation The data structures used by the SSE have an internal inconsistency.
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. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SSE-2-NOMEMORY : No memory available for [chars]
Explanation An 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.
Error Message%SSE-2-NOTZERO : program memory does not start at zero
Explanation A hardware error has occurred. This error indicates an unexpected condition on the Silicon Switch Processor (SSP) board.
Recommended Action It might be necessary to replace the SSP. 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. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SSE-2-SWFAILURE : SSE software failure -- [chars] [hex]
Explanation A software failure 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. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
SSH Messages
The following are Secure Shell (SSH) Protocol error messages.
Error Message%SSH-5-DISABLED : SSH [dec].[dec] has been disabled
Explanation The SSH protocol has been disabled for connections.
Recommended Action This is an informational message only. No action is necessary.
Error Message%SSH-5-ENABLED : SSH [dec].[dec] has been enabled
Explanation The SSH protocol has been enabled for connections.
Recommended Action This is an informational message only. No action is necessary.
Error Message%SSH-3-KEYPAIR : Attempt to generate server keys failed - error code: [chars]
Explanation A server RSA keypair could not be generated.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SSH-3-PRIVATEKEY : Unable to retrieve RSA private key for [chars]
Explanation An RSA private key does not exist or is corrupted.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
SSRP Messages
The following are error messages for the SONET/SDH based SRP Double Wide PCI port adapter driver.
Error Message%SSRP-3-UNSUPPORTED : [chars]\n
Explanation The SSRP hardware is not supported on this platform.
Recommended Action Upgrade the system to support the SSRP hardware.
STANDBY Messages
The following are Hot Standby Router Protocol (HSRP) error messages.
Error Message%STANDBY-3-BADAUTH : Bad authentication from [IP_address], remote state [chars]
Explanation Two routers that are participating in HSRP disagree about the valid authentication string.
Recommended Action Enter the standby authentication interface command to repair the HSRP authentication discrepancy between the local system and the router whose IP address is reported.
Error Message%STANDBY-3-DIFFVIP1 : [chars] Group [dec] active routers virtual
IP address [IP_address] is different to the locally configured
address [IP_address]Explanation The HSRP virtual IP address contained in the Hello message from the active router is different from the HSRP virtual IP address that is configured on the local router.
Recommended Action Check the configuration on all HSRP routers.
Error Message%STANDBY-3-DUPADDR : Duplicate address [IP_address] on [chars], sourced by [enet]
Explanation The router has received an HSRP message on the interface. The IP address in the HSRP message is the same as the IP address of the router. This condition may be caused by a network loop, a misconfiguration, or a malfunctioning switch.
Recommended Action Ensure that there are no network loops. Check the configuration on all the HSRP routers. Ensure that any switches are configured correctly and functioning properly.
Error Message%STANDBY-3-DUPVIP1 : [chars] Group [dec] address [IP_address] is
already assigned to [chars] group [dec]Explanation The system cannot learn the HSRP virtual IP address contained in the hello message as the HSRP virtual IP address is already assigned to a different HSRP group.
Recommended Action Check the configuration on all HSRP routers.
Error Message%STANDBY-3-DUPVIP2 : [chars] Group [dec] address [IP_address] is
already assigned on this interfaceExplanation The system cannot learn the HSRP virtual IP address contained in the hello message as the HSRP virtual IP address is already assigned to this interface.
Recommended Action Check the configuration on all HSRP routers.
Error Message%STANDBY-3-DUPVIP3 : [chars] Group [dec] address [IP_address] is
already assigned to, or overlaps with, an address on
another interface or applicationExplanation The system cannot learn the HSRP virtual IP address contained in the hello message as it is already assigned to, or overlaps with, an address on another interface or application.
Recommended Action Check the configuration on all HSRP routers.
Error Message%STANDBY-3-MISCONFIG : Attempt to change [chars] MAC address to [enet] when DECNET already running
Explanation A software or hardware error 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. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%STANDBY-3-NOSOCKET : Unable to open socket
Explanation The system was unable to initialize an IP connection for HSRP.
Recommended Action Ensure that there is at least one interface configured to run IP.
Error Message%STANDBY-6-STATECHANGE : Standby: [dec]: [chars] state [chars] -> [chars]
Explanation The router has changed its state.
Recommended Action No action is required.
STUC Messages
The following are SDSL Transmission Unit - central office error messages.
Error Message%STUC-3-MARGIN_LOW : [chars] [chars] [chars] [chars] [chars]
Explanation The SNR margin on the physical line connecting the port to the CPE has dropped below the configured SNR margin threshold for that port. This message is cleared when the specified condition is corrected.
Recommended Action Perform one or more of the following actions: Check the length and quality of the physical connection from the CPE to the DSL service provider. A longer distance between the CPE and DSLAM or a noisy line with high attenuation would impact the line training process. Check the port dsl-profile SNR threshold value configured on the DSLAM and the output (status) of the show dsl interface atm command. Collect the output logs for the show tech-support and show logging buffer commands on your DSLAM, the details of your CPE model and manufacturer, and the system configuration. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%STUC-3-PORT_FAIL : [chars] [chars] [chars] [chars] [chars]
Explanation The port has been configured as administratively up, but the port or interface is operationally down. There is no physical layer connectivity with the CPE.
Recommended Action Perform one or more of the following actions: Check that the CPE is connected to the line card. Check the length and quality of the physical connection from the CPE to the DSL service provider. A longer distance between the CPE and DSLAM or a noisy line with high attenuation would impact the line training process. Check the port interface and the dsl-profile configuration details and the output (status) of the show dsl interface atm command on the DSLAM. Collect the output logs for the show tech-support and show logging buffer commands on your DSLAM, the details of your CPE model and manufacturer, and the system configuration. Contact your Cisco technical support representative, and provide the representative with the gathered information.
STUN Messages
The following are serial tunnel (STUN) error messages.
Error Message%STUN-3-BADCONN : CONN: bad connection ([dec]), peer: [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%STUN-3-BADLENOP : [chars]: bad len or unknown op, op [dec], len [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%STUN-3-BADMAGIC : [chars]: wrong magic, mine [hex], theirs [hex] ([dec])
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%STUN-3-BADMAGICTCP : [chars]: peer [chars], wrong magic, mine [hex], theirs [hex]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%STUN-3-BADPASSIVEOPEN : passive open from [IP_address]([dec]) -> [dec] failed
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%STUN-3-CONNILLSTATE : CONN: Peer [chars], illegal state [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%STUN-6-CONNOPENFAIL : CONN: peer [chars] open failed, [chars] [[int]]
Explanation An attempt to connect to a remote TCP STUN peer has failed.
Recommended Action Verify that the remote peer is accessible from this router, that it is running software capable of supporting STUN, and that it is configured correctly.
Error Message%STUN-4-ERR : [chars]: [chars]: [chars], op [hex], len [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%STUN-2-NOBUF : Interface [chars], no buffer available to [chars]