IPV4_REASS_PROXY through IP_TUNNEL
IPV4_REASS_PROXY
%IPV4_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_INIT_FAILED : | |
---|---|
Explanation | Initialization of fragment information pool failed. |
Recommended Action | LOG_STD_ACTION |
%IPV4_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_EXTEND_FAILED : | |
---|---|
Explanation | Increasing of fragment information pool failed. |
Recommended Action | LOG_STD_ACTION |
%IPV4_REASS_PROXY-3-PROXY_IPC_INIT_FAILED : [dec] | |
---|---|
Explanation | IPC handler initialization failed. |
Recommended Action | LOG_STD_ACTION |
%IPV4_REASS_PROXY-4-PROXY_IPC_INVALID_MSG : [hex] | |
---|---|
Explanation | Received an invalid IPC messages subtype. |
Recommended Action | LOG_STD_ACTION |
IPV6_ACL
%IPV6_ACL-6-ACCESSLOGNP : list [chars]/[dec] [chars] [dec] [IPV6 address] [chars]-> [IPV6 address], [dec] packet[chars] | |
---|---|
Explanation | A packet matching the log criteria for the given access list was detected. |
Recommended Action | No action is required. |
%IPV6_ACL-6-ACCESSLOGDP : list [chars]/[dec] [chars] [chars] [IPV6 address] [chars]-> [IPV6 address] ([dec]/[dec]), [dec] packet[chars] | |
---|---|
Explanation | A packet matching the log criteria for the given access list was detected. |
Recommended Action | No action is required. |
%IPV6_ACL-6-ACCESSLOGSP : list [chars]/[dec] [chars] [chars] [IPV6 address] [chars]-> [IPV6 address], [dec] packet[chars] | |
---|---|
Explanation | A packet matching the log criteria for the given access list was detected. |
Recommended Action | No action is required. |
%IPV6_ACL-6-ACCESSLOGP : list [chars]/[dec] [chars] [chars] [IPV6 address]([dec]) [chars]-> [IPV6 address]([dec]), [dec] packet[chars] | |
---|---|
Explanation | A packet matching the log criteria for the given access list was detected. |
Recommended Action | No action is required. |
IPV6_ADDRESS
%IPV6_ADDRESS-3-INTERNAL : Internal error, [chars] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%IPV6_ADDRESS-3-NO_UNIQUE_IDENTIFIER : Cannot determine an unique IPv6 identifier for the system. IPv6 will not be started. | |
---|---|
Explanation | An unique IPv6 Identifier could not be determined for the system. Therefore the IPv6 process will not be started. This machine will not be able to process any IPv6 packets. |
Recommended Action | Verify that there is at least one interface in this machine that supports IEEE-style addresses. |
%IPV6_ADDRESS-3-NO_PROCESS : Cannot start an IPv6 process; router will not process IPv6 packets. | |
---|---|
Explanation | An IPv6 process could not be started. This machine will not be able to process any IPv6 packets. |
Recommended Action | Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. |
%IPV6_ADDRESS-3-ADDRESS_CFG : [IPV6 address]/[dec] can not be configured on [chars], [chars] | |
---|---|
Explanation | An error was encountered while configuring an IPv6 address |
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. |
%IPV6_ADDRESS-3-NULLIDB : Uninitialized interface pointer - [chars] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%IPV6_ADDRESS-3-OPINPROGRESS : Operation in progress - [chars] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%IPV6_ADDRESS-3-RESERVED_INTFID : Removing [IPV6 address] from [chars] - contains reserved interface identifier. [chars] | |
---|---|
Explanation | Removing IPv6 global address contains the reserved interface 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. |
IPV6_ADDRMGR
%IPV6_ADDRMGR-3-INTERNAL : Internal error, [chars] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
IPV6_FORWARDING
%IPV6_FORWARDING-2-CAUSE_THROTTLE_ERR : Allocation of ipv6 throttle [chars] memory failed | |
---|---|
Explanation | Allocation of memory resource use by ipv6 throttle fail |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%IPV6_FORWARDING-3-CAUSE_LINKTYPE_ERR : Unsupported link type [chars], dropping packet | |
---|---|
Explanation | Link type is unsupported at the current time. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%IPV6_FORWARDING-4-CHECKSUM_ERR : Checksum buffer walk failed | |
---|---|
Explanation | Internal problem occured during calculating segmented packet checksum. |
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. |
%IPV6_FORWARDING-3-TABLE_ID_SZ_ERR : Table ID size configured incorrectly: [dec] | |
---|---|
Explanation | Table ID size must be less than or equal to 16 or 32 bits. |
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. |
IPV6_POLICY_API
%IPV6_POLICY_API-4-IPV6_POLICYOVERIDE : Dynamic policy overriding static on intf:[chars] | |
---|---|
Explanation | Static policy and dynamic policy are configured on the interface. The dynamic policy will override the static policy. |
Recommended Action | Remove the static policy config if desired. |
%IPV6_POLICY_API-4-IPV6_LOCALPOLICYOVERIDE : Local dynamic policy overriding static local policy | |
---|---|
Explanation | Static policy and dynamic local policy are configured. The dynamic local policy will override the static local policy. |
Recommended Action | Remove the static local policy config if desired. |
IPV6_REASS_PROXY
%IPV6_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_INIT_FAILED : | |
---|---|
Explanation | Initialization of fragment information pool failed. |
Recommended Action | LOG_STD_ACTION |
%IPV6_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_EXTEND_FAILED : | |
---|---|
Explanation | Increasing of fragment information pool failed. |
Recommended Action | LOG_STD_ACTION |
%IPV6_REASS_PROXY-3-PROXY_IPC_INIT_FAILED : [dec] | |
---|---|
Explanation | IPC handler initialization failed. |
Recommended Action | LOG_STD_ACTION |
%IPV6_REASS_PROXY-4-PROXY_IPC_INVALID_MSG : [hex] | |
---|---|
Explanation | Received an invalid IPC messages subtype. |
Recommended Action | LOG_STD_ACTION |
IPV6_RIP
%IPV6_RIP-3-NULLIDB : Uninitialized interface pointer - RIPv6 | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%IPV6_RIP-3-NULLPAK : Uninitialized packet pointer - RIPv6 | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%IPV6_RIP-3-NULLPDB : Uninitialized PDB pointer - RIPv6 | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%IPV6_RIP-3-NULLIPDB : Uninitialized iPDB pointer - RIPv6 | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%IPV6_RIP-3-NULLPROTO : Uninitialized protocol pointer - RIPv6 | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%IPV6_RIP-3-NULLSOC : Uninitialized socket pointer - RIPv6 | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%IPV6_RIP-3-ALLOC_PDB : Can't alloc PDB structure - RIPv6 | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%IPV6_RIP-3-ALLOC_IPDB : Can't alloc iPDB structure - RIPv6 | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%IPV6_RIP-3-PROCESS_CREATE : Can't create process - RIPv6 | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%IPV6_RIP-3-ALLOC_ERR : Memory allocation problem - RIPv6 | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%IPV6_RIP-3-PROCESS_MSG_SEND : Can't send message to process - RIPv6 | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
IP_SNMP
%IP_SNMP-3-SOCKET : can't open UDP socket | |
---|---|
Explanation | The SNMP server was unable to open a port for receiving or transmitting SNMP requests. This usually happens when the SNMP server is started using the snmp-server community configuration command on a router or communication server with an interface that has no IP address configured. Another possible cause is low memory. |
Recommended Action | Configure at least one interface with an IP address or specify the no snmp-server command to remove the SNMP server process. Call your technical support representative if problems persist or if it becomes necessary to add memory. |
%IP_SNMP-4-NOTRAPIP : SNMP trap source [chars] has no ip address | |
---|---|
Explanation | The user entered an snmp-server trap-source command. The interface requested for use as the source address has no ipv4 address associated with it. The SNMP trap is being sent anyway, but without the source address that the user intended. |
Recommended Action | There are two possible solutions. Either enter a no snmp-server trap-source command to disable the request for a specific source IP address, or add an IP address to the interface referenced in the snmp-server trap-source configuration command. |
%IP_SNMP-4-NOTRAPIPV6 : SNMP trap source [chars] has no ipv6 address | |
---|---|
Explanation | The user entered an snmp-server trap-source command. The interface requested for use as the source address has no ipv6 address associated with it. The SNMP trap is being sent anyway, but without the source address that the user intended. |
Recommended Action | There are two possible solutions. Either enter a no snmp-server trap-source command to disable the request for a specific source IP address, or add an IPV6 address to the interface referenced in the snmp-server trap-source configuration command. |
%IP_SNMP-4-TOOBIG : Oversize message from [IP_address], datagram size [int], udp length [int] | |
---|---|
Explanation | An incoming SNMP packet had a length field so large that the system had to assume it was in error. This system made a correct reaction to bad external data. Since SNMP packets should originate from systems under the same administration, this may indicate that the network host used to originate the SNMP request had a problem in its networking layer. Alternatively, if the SNMP packet originated from outside the local administrative domain, it could indicate an failed attempt at security penetration and that site should be watched more closely. |
Recommended Action | If the origin is local, no action is required. If the origin is determined to be malicious, either contact the administrator of the originating site or install filters to prevent access by that site, as circumstances warrant. |
IP_TUNNEL
%IP_TUNNEL-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int] | |
---|---|
Explanation | For a request from upper TUNNEL software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
Recommended Action | This is normally a software issue. LOG_STD_RECUR_ACTION |
%IP_TUNNEL-3-IPC_NORES : No space for the IPC reply, size [int] | |
---|---|
Explanation | For a request from upper TUNNEL software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation. |
Recommended Action | This is normally a software issue. LOG_STD_RECUR_ACTION |
%IP_TUNNEL-2-IPC_INIT : IPC message handler registration failure, rc [int] | |
---|---|
Explanation | Registering an IPC message handler for the Tunnel feature failed. This may cause the feature to not function. |
Recommended Action | This is normally a software issue. The consequences are that the tunnel feature may not function. LOG_STD_ACTION |