Gbic security crypt 4 vn data crc error - Исправление ошибок и поиск оптимальных решений проблем

GBIC_SECURITY_CRYPT through IPA

GBIC_SECURITY_CRYPT through HAL_GENMEM

GBIC_SECURITY_CRYPT
GBIC_SECURITY_UNIQUE
GDOI
GENERIC_SUBBLOCK
GEN_DB
GEN_PROXY
GLBP
GRIP
HA
HAL_GENMEM

GBIC_SECURITY_CRYPT

%GBIC_SECURITY_CRYPT-4-UNRECOGNIZED_VENDOR : GBIC in port [dec] manufactured by an unrecognized vendor
Explanation	The GBIC was identified as a Cisco GBIC, but the system was unable to match its manufacturer with one on the known list of Cisco GBIC vendors
Recommended Action	Check to see if the Cisco IOS software running on the system supports the GBIC. If the GBIC is newer, a system software upgrade might be required.

%GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR : GBIC in port [dec] has bad crc
Explanation	The GBIC was identified as a Cisco GBIC, but it does not have valid CRC in the EEPROM data.
Recommended Action	Check to see if the Cisco IOS software running on the system supports the GBIC. If the GBIC is newer, a system software upgrade might be required. Even if the GBIC is unrecognized by the system, the GBIC may still operate properly, but might have limited functionality.

%GBIC_SECURITY_CRYPT-4-ID_MISMATCH : Identification check failed for GBIC in port [dec]
Explanation	The GBIC was identified as a Cisco GBIC, but the system was unable to verify its identity
Recommended Action	Check to see if the Cisco IOS software running on the system supports the GBIC. If the GBIC is newer, a system software upgrade might be required. Otherwise, verify that the GBIC was obatined from Cisco or from a supported vendor.

GBIC_SECURITY_UNIQUE

%GBIC_SECURITY_UNIQUE-4-DUPLICATE_SN : GBIC interface [dec]/[dec] has the same serial number as another GBIC interface
Explanation	The GBIC was identified as a Cisco GBIC, but its serial number matches that of another interface on the system.
Recommended Action	Cisco GBICs are assigned unique serial numbers. Verify that the GBIC was obtained from Cisco or a supported vendor

%GBIC_SECURITY_UNIQUE-3-DUPLICATE_GBIC : GBIC interface [dec]/[dec] is a duplicate of GBIC interface [dec]/[dec]
Explanation	The GBIC was identified as a Cisco GBIC, but its vendor ID and serial number match that of another interface on the system.
Recommended Action	Cisco GBICs are assigned unique serial numbers. Verify that the GBIC was obtained from Cisco or a supported vendor

GDOI

%GDOI-1-GDOI_ACL_NUM : The ACL has too many entries. GDOI will honor only the first 100 ACL entries specified.
Explanation	The ACL has too many entries. GDOI will honor only the first 100 ACL entries specified.
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.

%GDOI-1-GDOI_ACL_NUM : The ACL has too many entries. GDOI will honor only the first 100 ACL entries specified.

Explanation

The ACL has too many entries. GDOI will honor only the first 100 ACL entries specified.

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.

%GDOI-3-GDOI_ACL_RANGE : The ACL [chars] contains port range which is NOT supported. WARNING: No TEK policy will be created.
Explanation	GDOI does not support port range in the ACL policy.
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.

%GDOI-3-GDOI_ACL_RANGE : The ACL [chars] contains port range which is NOT supported. WARNING: No TEK policy will be created.

Explanation

GDOI does not support port range in the ACL policy.

Recommended Action

%GDOI-1-GDOI_ACE_DENY : A Group Member ACL policy containing deny was attempted. This is not supported.
Explanation	A Group Member ACL policy containing deny was attempted. This is not supported.
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.

%GDOI-1-GDOI_ACE_DENY : A Group Member ACL policy containing deny was attempted. This is not supported.

Explanation

A Group Member ACL policy containing deny was attempted. This is not supported.

Recommended Action

%GDOI-1-UNREGISTERED_INTERFACE : Group [chars] received registration from unregistered interface.
Explanation	Receiving registration from unregistered interface. Stop processing it.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.

%GDOI-1-UNREGISTERED_INTERFACE : Group [chars] received registration from unregistered interface.

Explanation

Receiving registration from unregistered interface. Stop processing it.

Recommended Action

%GDOI-1-UNAUTHORIZED_IDENTITY : Group [chars] received registration from unauthorized identity: [chars]
Explanation	The registration request was dropped because the requesting device was not authorized to join the group.
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.

%GDOI-1-UNAUTHORIZED_IDENTITY : Group [chars] received registration from unauthorized identity: [chars]

Explanation

The registration request was dropped because the requesting device was not authorized to join the group.

Recommended Action

%GDOI-1-UNAUTHORIZED_IPADDR : Group [chars] received registration from unauthorized ip address: [chars]
Explanation	The registration request was dropped because the requesting device was not authorized to join the group.
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.

%GDOI-1-UNAUTHORIZED_IPADDR : Group [chars] received registration from unauthorized ip address: [chars]

Explanation

The registration request was dropped because the requesting device was not authorized to join the group.

Recommended Action

%GDOI-4-GM_RE_REGISTER : The IPSec SA created for group [chars] may have expired/been cleared, or didn’t go through. Re-register to KS.
Explanation	The IPSec SA created for one group may have expired/been cleared, or didn’t go through, need to re-register to KS.
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.

%GDOI-4-GM_RE_REGISTER : The IPSec SA created for group [chars] may have expired/been cleared, or didn’t go through. Re-register
to KS.

Explanation

The IPSec SA created for one group may have expired/been cleared, or didn’t go through, need to re-register to KS.

Recommended Action

%GDOI-5-GM_REGS_COMPL : Registration to KS [chars] complete for group [chars] using address [chars] fvrf [chars] ivrf [chars]
Explanation	Complete registration
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.

%GDOI-5-GM_REGS_COMPL : Registration to KS [chars] complete for group [chars] using address [chars] fvrf [chars] ivrf [chars]

Explanation

Complete registration

Recommended Action

%GDOI-5-GM_FAILED_TO_INSTALL_POLICIES : FAILED: Installation of Reg/Rekey policies from KS [chars] for group [chars] & gm identity [chars]
Explanation	Failed Policy installation
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.

%GDOI-5-GM_FAILED_TO_INSTALL_POLICIES : FAILED: Installation of Reg/Rekey policies from KS [chars] for group [chars] & gm
identity [chars]

Explanation

Failed Policy installation

Recommended Action

%GDOI-5-GM_INSTALL_POLICIES_SUCCESS : SUCCESS: Installation of Reg/Rekey policies from KS [chars] for group [chars] & gm identity [chars] fvrf [chars] ivrf [chars]
Explanation	Policy Installation Success
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.

%GDOI-5-GM_INSTALL_POLICIES_SUCCESS : SUCCESS: Installation of Reg/Rekey policies from KS [chars] for group [chars] & gm
identity [chars] fvrf [chars] ivrf [chars]

Explanation

Policy Installation Success

Recommended Action

%GDOI-5-GM_RECV_REKEY : Received Rekey for group [chars] from [chars] to [chars] with seq # [dec], spi [hex][hex]
Explanation	Received Rekey
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.

%GDOI-5-GM_RECV_REKEY : Received Rekey for group [chars] from [chars] to [chars] with seq # [dec], spi [hex][hex]

Explanation

Received Rekey

Recommended Action

%GDOI-5-KS_SEND_MCAST_REKEY : Sending Multicast Rekey [chars]for group [chars] from address [chars] to [chars] with seq # [dec] spi: [hex][hex]
Explanation	Sending Multicast Rekey
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.

%GDOI-5-KS_SEND_MCAST_REKEY : Sending Multicast Rekey [chars]for group [chars] from address [chars] to [chars] with seq #
[dec] spi: [hex][hex]

Explanation

Sending Multicast Rekey

Recommended Action

%GDOI-5-KS_SEND_UNICAST_REKEY : Sending Unicast Rekey [chars]for group [chars] from address [chars] with seq # [dec] spi: [hex][hex]
Explanation	Sending Unicast Rekey
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.

%GDOI-5-KS_SEND_UNICAST_REKEY : Sending Unicast Rekey [chars]for group [chars] from address [chars] with seq # [dec] spi:
[hex][hex]

Explanation

Sending Unicast Rekey

Recommended Action

%GDOI-3-KS_BAD_ID : Registration: [chars] config mismatch between KS and the GM [IP_address], in the group [chars].
Explanation	During GDOI registration protocol, a configuration mismatch between local key server and group member.
Recommended Action	Contact the Group member’s administrator.

%GDOI-3-GDOI_REKEY_FAILURE : Processing of REKEY payloads failed on GM [chars] in the group [chars], with peer at [chars]
Explanation	During GDOI rekey the payload parsing failed on this GM from the Key Server.
Recommended Action	Contact the Group member’s administrator.

%GDOI-3-GDOI_REKEY_SEQ_FAILURE : Failed to process rekey seq # [int] in seq payload for group [chars], last seq # [int]
Explanation	During GDOI rekey the seq payload parsing failed on this GM from the Key Server.
Recommended Action	Contact the Group member’s administrator.

%GDOI-4-KS_GM_REJECTS_SA_PAYLOAD : Registration: GM [IP_address] rejected a policy in the SA proposal sent by KS, in the group [chars].
Explanation	During GDOI registration protocol, a proposal sent by the key server was refused by the group member.
Recommended Action	Contact the Group member’s administrator.

%GDOI-4-GM_REJECTING_SA_PAYLOAD : Registration: Policy in SA payload sent by KS [IP_address] rejected by GM in the group [chars] reason [chars].
Explanation	During GDOI registration protocol, a proposal sent by the key server was refused by the local group member.
Recommended Action	Contact the Key server’s administrator.

%GDOI-4-KS_HASH_FAIL : Registration: Bad(No) Hash in Message sent by the GM [IP_address] to KS in the group [chars].
Explanation	During GDOI registration protocol, a message sent by the Group member has bad or no hash .
Recommended Action	Contact the Group member’s administrator.

%GDOI-4-GM_HASH_FAIL : Registration: Bad(No) hash in message sent by the KS [IP_address] to GM in the group [chars].
Explanation	During GDOI registration protocol, a message sent by the Key server has bad or no hash .
Recommended Action	Contact the Key Server’s administrator.

%GDOI-3-KS_UNAUTHORIZED : Registration: Unauthorized [IP_address] tried to join the group [chars].
Explanation	During GDOI registration protocol, an unauthorized member tried to join a group Some might consider this a hostile event.
Recommended Action	Contact the Key Server’s administrator.

%GDOI-3-KS_GM_REVOKED : Re-Key: GM [IP_address] revoked by KS in the group [chars].
Explanation	During Re-key protocol, an unauthorized member tried to join a group. Some might consider this a hostile event.
Recommended Action	Contact the Key Server’s administrator.

%GDOI-5-KS_GROUP_ADD : Config: KS [IP_address] added to the Group [chars].
Explanation	A Config command has been executed to add a Key Server in a group
Recommended Action	Informational message.

%GDOI-5-KS_GROUP_DELETE : Config: KS [IP_address] removed from the Group [chars].
Explanation	A Config command has been executed to remove a Key Server from a group
Recommended Action	Informational message.

%GDOI-6-KS_FIRST_GM : Re-key: First GM [IP_address] seen by KS in the group [chars].
Explanation	Local key server has received the first group member joining the group
Recommended Action	Informational message.

%GDOI-6-KS_LAST_GM : Re-key: Last GM [IP_address] left the group [chars].
Explanation	Last group member has left the group on the local key server
Recommended Action	Informational message.

%GDOI-5-GM_CM_ATTACH : Crypto map attached for GM in group [chars].
Explanation	A crypto map has been attached for the local group member.
Recommended Action	Informational message.

%GDOI-5-GM_CM_DETACH : Crypto map detached for GM in group [chars].
Explanation	A crypto map has been detached for the local group member.
Recommended Action	Informational message.

%GDOI-5-GM_UNREGISTER : GM left the group [chars].
Explanation	A Group member has left the group.
Recommended Action	Informational message.

%GDOI-4-GM_RECV_POLICY_REPLACE_NOW : GM received policy replace now rekey from KS in group [chars].
Explanation	A messages sent by the KS to immediately replace SAs policies on the GM has been received.
Recommended Action	Informational message.

%GDOI-4-GM_RECV_DELETE_IMMEDIATE : GM receive REMOVAL-NOW in group [chars] to cleanup downloaded policy now. Re-registration will start in a randomly chosen period of [dec] sec
Explanation	A messages sent by the KS to delete the GM has been received.
Recommended Action	Informational message.

%GDOI-4-GM_RECV_RE_AUTH : GM received Re-auth-msg from KS in group [chars]. re-registration will start before SA expiry
Explanation	A message sent by the KS to have a GM re-auth has been received.
Recommended Action	Informational message.

%GDOI-4-GM_RECV_DELETE : GM received delete-msg from KS in group [chars]. TEKs lifetime are reduced and re-registration will start before SA expiry
Explanation	A messages sent by the KS to delete the GM has been received.
Recommended Action	Informational message.

%GDOI-5-GM_CLEAR_REGISTER : Config: GM cleared gdoi configuration for the group [chars].
Explanation	clear crypto gdoi command has been executed by the local GM
Recommended Action	Informational message.

%GDOI-5-KS_CLEAR_REGISTER : Config: KS cleared gdoi configuration for the group [chars].
Explanation	clear crypto gdoi command has been executed by the local KS
Recommended Action	Informational message.

%GDOI-3-COOP_KS_UNREACH : Cooperative KS [chars] Unreachable in group [chars]. IKE SA Status = [chars]
Explanation	The reachability between the configugred cooperative key servers is lost. Some might consider this a hostile event.
Recommended Action	Contach the Administrator(s) of the configured key servers.

%GDOI-5-COOP_KS_REACH : Reachability restored with Cooperative KS [chars] in group [chars].
Explanation	The reachability between the configugred cooperative key servers is restored.
Recommended Action	Informational message

%GDOI-5-COOP_KS_ADD : [chars] added as COOP Key Server in group [chars].
Explanation	A key server has been added to the list of cooperative key servers in a group
Recommended Action	Informational message

%GDOI-5-COOP_KS_REMOVE : [chars] removed as COOP Key Server in group [chars].
Explanation	A key server has been removed from the list of cooperative key servers in a group
Recommended Action	Informational message

%GDOI-4-COOP_KS_UNAUTH : Contact from unauthorized KS [chars] in group [chars] at local address [chars] (Possible MISCONFIG of peer/local address)
Explanation	An unauthorized remote server tried to contact the local KS may be at different key server address in a group. Some might consider this a hostile event.
Recommended Action	Informational message

%GDOI-5-COOP_KS_ELECTION : KS entering election mode in group [chars] (Previous Primary = [chars])
Explanation	The local Key server has entered the election process in a group
Recommended Action	Informational message

%GDOI-5-COOP_KS_TRANS_TO_PRI : KS [chars] in group [chars] transitioned to Primary (Previous Primary = [chars])
Explanation	The local Key server transitioned to a primary role from being a secondary server in a group
Recommended Action	Informational message

%GDOI-5-COOP_KS_ADMN_USRP_PRI : Primary role Usurped by KS [chars] in group [chars].
Explanation	A network adminstrator has made the local KS as primary, by means of a CLI command. Currently Unimplemented.
Recommended Action	Informational message

%GDOI-5-GM_REKEY_TRANS_2_MULTI : Group [chars] transitioned to multicast rekey.
Explanation	GM has transitioned from using unicast rekey mechanism to multicast mechanism
Recommended Action	Informational message

%GDOI-5-KS_REKEY_TRANS_2_MULTI : Group [chars] transitioned to multicast rekey.
Explanation	Group has transitioned from using unicast rekey mechanism to multicast mechanism
Recommended Action	Informational message

%GDOI-5-GM_REKEY_TRANS_2_UNI : Group [chars] transitioned to Unicast Rekey.
Explanation	GM has transitioned from using multicast rekey mechanism to unicast mechanism
Recommended Action	Informational message

%GDOI-5-KS_REKEY_TRANS_2_UNI : Group [chars] transitioned to Unicast Rekey.
Explanation	Group has transitioned from using multicast rekey mechanism to unicast mechanism
Recommended Action	Informational message

%GDOI-4-GM_REKEY_NOT_RECD : GM did not receive rekey from KS [IP_address] in group [chars].
Explanation	GM has not received a rekey message from a key server in a group Currently Unimplemented.
Recommended Action	Informational message

%GDOI-5-KS_NACK_GM_EJECT : KS ejected GM [IP_address] in group [chars].
Explanation	Key server has reached a condition of not receiving an ACK from GM and has been ejected
Recommended Action	Informational message

%GDOI-3-KS_BLACKHOLE_ACK : KS blackholing GM [IP_address] in group [chars].
Explanation	Key server has reached a condition of blackholing messages from GM Some might consider this a hostile event.
Recommended Action

%GDOI-4-KS_UNSOL_ACK : KS received unsolicited ACK from GM [IP_address] in group [chars].
Explanation	Key server has received an unsolicited ACK from a past GM or is under a DOS attack. Some might consider this a hostile event.
Recommended Action

%GDOI-5-KS_REGS_COMPL : KS completed successful registration in group [chars] with GM [IP_address].
Explanation	Key server has successfully completed a registration in a group
Recommended Action

%GDOI-5-GM_ENABLE_GDOI_CM : GM has enabled ACL on GDOI crypto map in group [chars].
Explanation	Group member has enabled ACL on a GDOI Crypto map in a group with a key server
Recommended Action

%GDOI-5-GM_ACL_MERGE : ACL betweem KS and GM in group [chars] merged.
Explanation	The ACL differences between GM and KS are resolved and a merge took place
Recommended Action

%GDOI-5-GM_SA_INGRESS : Receive only ACL received from KS [IP_address] in group [chars].
Explanation	Received only acl has been received by GM from a KS in a group
Recommended Action

%GDOI-5-KS_CONV_SAS_DUPLEX : IPSec SAs converted to Duplex in group [chars].
Explanation	IPSec SAs have been converted to bidirectional mode in a group
Recommended Action

%GDOI-5-KS_CONV_SAS_INGRESS : IPSec SAs converted to Ingress in group [chars].
Explanation	IPSec SAs have been converted to receive only mode in a group
Recommended Action

%GDOI-5-GM_CONV_SA_DUPLEX : IPSec SAs converted to Duplex in group [chars] on the GM.
Explanation	IPSec SAs have been converted to bidirectional mode in a group on a GM
Recommended Action

%GDOI-5-GM_CONV_SA_DUPLEX_LOCAL : IPSec SAs converted to Duplex in group [chars] on a GM by a local event.
Explanation	IPSec SAs have been converted to bidirectional mode in a group on a GM by a CLI command
Recommended Action

%GDOI-5-LKH_ENABLE : LKH enabled in group [chars].
Explanation	LKH has been enabled in a group
Recommended Action

%GDOI-5-LKH_DISABLE : LKH disabled in group [chars].
Explanation	LKH has been disabled in a group
Recommended Action

%GDOI-4-LKH_GM_DELETE : GM [IP_address] deleted from LKH in group [chars].
Explanation	A Group member has been deleted in a group from LKH
Recommended Action

%GDOI-4-TIMEBASED_REPLAY_FAILED : An anti replay check has failed in group [chars]: my_pseudotime = [chars], peer_pseudotime = [chars], replay_window = [dec] (sec), src_ip = [IP_address], dst_ip = [IP_address]
Explanation	A Group member or Key server has failed an anti replay check.
Recommended Action

%GDOI-3-PIP_PSEUDO_TIME_ERROR : An Anti-Replay check has failed for PIP in group [chars]: my_pseudotime = [chars], peer_pseudotime = [chars], replay_window = %lld (sec), src_addr = [chars], dst_addr = [chars]
Explanation	A Group member has failed PIP anti replay check.
Recommended Action

%GDOI-3-P2P_KGS_INFRA_ERROR : PIP session with [chars] failed because of KGS Infra failure. Reason = [chars]

Explanation

A Group Member has encountered a KGS Infra failure.

Recommended Action

%GDOI-4-TIMEBASED_REPLAY_FAILED_IPV6 : An anti replay check has failed in group [chars]: my_pseudotime = [chars], peer_pseudotime = [chars], replay_window = [dec] (sec), src_ip = [IPV6 address], dst_ip = [IPV6 address]
Explanation	A Group member or Key server has failed an anti replay check.
Recommended Action

%GDOI-3-GM_FAILED_TO_INITIALISE : GDOI GM Process has failed to initialise
Explanation	GDOI Group Member process has failed to initialise on this Network Element
Recommended Action

%GDOI-3-PSEUDO_TIME_LARGE : Pseudotime difference between KS ([dec] sec) and GM ([dec] sec) is larger than expected in group [chars]. Adjust to new PST
Explanation	A Group member has received pseudotime which has large difference as compared to own pseudotime
Recommended Action

%GDOI-3-PSEUDO_TIME_TOO_OLD : Rekey received in group [chars] is too old and fail PST check: my_pst is [dec] sec, peer_pst is [dec] sec, allowable_skew is [dec] sec
Explanation	A Group member has received pseudotime which has large difference as compared to own pseudotime
Recommended Action

%GDOI-3-GM_INCOMPLETE_CFG : Registration: incomplete config for group [chars]
Explanation	Registration can not be completed since the GDOI group configuration may be missing the group id, server id, or both
Recommended Action	Contact the Group member’s administrator.

%GDOI-1-KS_NO_RSA_KEYS : RSA Key — [chars] : Not found, Required for group [chars]
Explanation	Rsa Keys were not found in Key Server and they are required for signing and verifying rekey messages
Recommended Action	Contact the Key Server’s administrator and ask him to do create the RSA Key pair

%GDOI-4-RSA_KEYS_MODIFIED : WARNING: GMs for group [chars] will re-register due to signature verification failure
Explanation	Rekeys will be dropped by GM as signature verification would fail due to modification of RSA Keys
Recommended Action	Informational message

%GDOI-3-KS_REKEY_AUTH_KEY_LENGTH_INSUFFICIENT : Rejected [chars] change: using sig-hash algorithm [chars] requires an authentication key length of at least [int] bits ([int] blocks in bytes) — [chars] [chars] key [chars] is only [int] blocks in bytes
Explanation	Using a sig-hash algorithm for rekeys requires that the RSA key modulus length for the rekey authentication be at least the length of the hash generated by the sig-hash algorithm plus some padding bytes. If the RSA key modulus length is not large enough, the Key Server administrator needs to generate a new RSA key pair wit a sufficient length.
Recommended Action	Contact the Key Server’s administrator to re-generate the RSA key pair with at least the modulus length given in the syslog.

%GDOI-3-COOP_CONFIG_MISMATCH : WARNING: Group [chars], [chars] configuration between Primary KS and Secondary KS are mismatched
Explanation	The configuration between Primary KS and Secondary KS are mismatched
Recommended Action	Contact the Key Sever’s administrator

%GDOI-3-GM_ACL_PERMIT : GM doesn’t support permit configured under local access-list. Traffic from [chars] to [chars] will be dropped.
Explanation	GM can only support ACL for deny. Any traffic matching the permit entry will be dropped.
Recommended Action	Remove the permit entry from the ACL used by GDOI crypto map

%GDOI-3-GM_NO_IPSEC_FLOWS : IPSec FLOW limit possibly reached
Explanation	Hardware Limitation for IPSec Flow limit Reached. Cannot create any more IPSec SAs
Recommended Action	Contact the Group member’s administrator.

%GDOI-3-GM_NO_CRYPTO_ENGINE : No crypto engine is found due to lack of resource or unsupported feature requested
Explanation	Failed to select a suitable crypto engine because requested packet path not available, or requested feature not supported
Recommended Action	Check policy configured on KS

%GDOI-3-COOP_PACKET_DROPPED : Announcement message dropped due to packet size [dec] bytes.
Explanation	Hard limit set on the driver buffer size prevents sending packets of this size or bigger
Recommended Action	Informational message

%GDOI-3-UNEXPECTED_SIGKEY : Unexpected Signature Key detected: freeing it
Explanation	Unexpected Signature Key found: freeing the signature key
Recommended Action	Informational message

%GDOI-3-UNSUPPORTED_TEK_PROTO : Unexpected TEK Protocol : [dec]
Explanation	Unexpected TEK PROTOCOL
Recommended Action	Informational message

%GDOI-4-GM_DELETE : GM [chars] deleted from group [chars].
Explanation	A group member has been deleted in a group from Key Server
Recommended Action	Informational message

%GDOI-5-KS_USING_DEFAULT_TRANSFORM : GETVPN is using default transforms for profile [chars]

Explanation

Using default transformset

Recommended Action

%GDOI-5-GM_REKEY_CIPHER_HASH_CHECK_FAIL : Rekey cipher/hash ([chars]) used in Group [chars] is unacceptable by this client.
Explanation	The key-server has chosen KEK rekey cipher/hash algorithms which are not acceptable by this group-member
Recommended Action	Contact the Key server’s administrator.

%GDOI-5-GM_REKEY_TRANSFORMSET_CHECK_FAIL : The transformset ([chars]) for data-protection in Group [chars] is unacceptable by this client.
Explanation	The key-server has chosen a TEK transformset which is not acceptable by this group-member
Recommended Action	Contact the Key server’s administrator.

%GDOI-3-COOP_ANN_SEQ_FAILURE : COOP Ann msg seq check failed for group [chars], ann seq# [int], sess seq# [int]
Explanation	COOP Ann msg seq check failed
Recommended Action	Contact Administrator

%GDOI-4-GDOI_ANN_TIMESTAMP_TOO_OLD : COOP_KS ANN from KS [chars] in group [chars] is too old and fail PST check: my_pst is [int] sec, peer_pst is [int] sec, allowable_skew is [dec] sec
Explanation	The KS has received an ANN msg from a primary KS in which the timestamp is too old
Recommended Action

%GDOI-4-GDOI_ANN_TIMESTAMP_LARGE : COOP_KS ANN received from KS [chars] in group [chars] has PST bigger than myself. Adjust to new PST: my_old_pst is [int] sec, peer_pst is [int] sec
Explanation	The KS receive an ANN from a KS in which the timestamp is bigger than expected; also update my PST to peer’s
Recommended Action

%GDOI-4-GDOI_ANN_TIMESTAMP_LARGE_NO_UPDATE : COOP_KS ANN received from KS [chars] in group [chars] has PST bigger than myself: my_pst is [int] sec, peer_pst is [int] sec
Explanation	The KS receive an ANN from a KS in which the timestamp is bigger than expected; No update of my PST
Recommended Action

%GDOI-4-GDOI_ANN_INCONSISTENT_TBAR : COOP_KS ANN received from [chars] in group [chars] has inconsistent TBAR setting inconsistent than mine
Explanation	The KS has received an ANN msg from a secondary KS in which the timestamp is too old
Recommended Action

%GDOI-5-COOP_KS_VALID_ANN_TIMER_EXPIRED : This sec-KS has NOT received an ANN with valid PST for an extended period in group [chars]. It will block new GMs registration temporarily until a valid ANN is received
Explanation	No valid ANN message has been received in this secondary KS for a prolong period. Temporarily blocking new GM registrations until a valid ANN is received
Recommended Action	Informational message

%GDOI-5-COOP_KS_BLOCK_NEW_GM_REGISTER_ANN : This KS temporarily blocks GM with ip-addr [chars] from registering in group
[chars] as it has not received an ANN with valid PST for prolonged period

Explanation

No valid ANN message has been received in this secondary KS for a prolong period. Temporarily blocking new GM registrations
until a valid ANN is received

Recommended Action

%GDOI-5-COOP_KS_BLOCK_NEW_GM_REGISTER_ELECTION : This KS temporarily blocks GM with ip-addr [chars] from registering in group
[chars] as the KS election is underway

Explanation

The KS is in the process of electing a primary. Temporarily blocking new GM registrations until the election is complete

Recommended Action

%GDOI-5-COOP_KS_BLOCK_NEW_GM_REGISTER_KSSID : This KS is blocking GM with ip-addr [chars] from registering in group [chars] as it has overlapping KS Sender Identifier(s) (KSSID) with another COOP-KS peer (MISCONFIG)
Explanation	Another COOP-KS peer in the group has been configured with a KSSID value that is the same as one configured on this KS. GM registration is blocked as a result until the overlap is fixed.
Recommended Action	Check the configured KSSID(s) for all COOP-KS peers by issuing ‘show crypto gdoi ks coop ident detail’ on the primary KS

%GDOI-5-COOP_KS_RESUME_NEW_GM_REGISTER : This KS will now resume new GM registration functionality in group [chars]

Explanation

This KS will now resume new GM registration functionality

Recommended Action

%GDOI-5-SA_KEK_UPDATED : SA KEK was updated [hex][hex][hex][hex]
Explanation	KEK was updated in the Registration/Rekey and a new KEK SA was created
Recommended Action	Informational message.

%GDOI-5-SA_PIP_UPDATED : SA PIP was updated 0x[chars]
Explanation	PIP was updated in Registration/Rekey and a new PIP SA was created
Recommended Action	Informational message.

%GDOI-3-SA_KEK_INSATALL_FAILED : Failed to install KEK SA
Explanation	KEK SA instalation has failed
Recommended Action	Informational message.

%GDOI-3-P2P_PEER_MIGRATE_FAILED : Failed to install P2P rekey SA with peer [chars] in group [chars]
Explanation	Installation of P2P Rekey SA with an existing peer has failed
Recommended Action	Check the status of all peers using the command ‘show crypto gdoi gm p2p peers’ and wait for PIP initiation between the failed peers. Traffic distruption may occur.

%GDOI-5-SA_TEK_UPDATED : SA TEK was updated
Explanation	TEK was updated in the Registration/Rekey and a new TEK IPSEC SA was created
Recommended Action	Informational message.

%GDOI-4-GM_MINOR_VERSION_MISMATCH : GM [IP_address] Minor Version mismatch. Use ‘show crypto gdoi ks members’ to see GM versions
Explanation	GM has different minor version.
Recommended Action	show crypto gdoi ks members

%GDOI-3-GM_MAJOR_VERSION_MISMATCH : GM [IP_address] registration rejected due to major version mismatch. GM must be using major version [dec] in order to be compatible with this KS
Explanation	GM has a non-compatible major version.
Recommended Action	Check GDOI version compatibility on KS and GMs

%GDOI-4-KS_MINOR_VERSION_MISMATCH : COOP-KS Minor Version mistmatch in group [chars]. My version is [dec].[dec].[dec], peer [chars] has version [dec].[dec].[dec]
Explanation	Coop KS has different minor version.
Recommended Action	show crypto gdoi ks coop

%GDOI-3-KS_MAJOR_VERSION_MISMATCH : COOP-KS Major Version mismatch in group [chars]. My version is [dec].[dec].[dec], peer [chars] has version [dec].[dec].[dec]
Explanation	COOP-KS has a non-compatible major version.
Recommended Action	Check GDOI version compatibility on KS

%GDOI-2-COOP_MINOR_VERSION_MISMATCH : COOP-KS Minor version mistmatch in group [chars]. My COOP version is [dec].[dec].[dec], peer [chars] has version [dec].[dec].[dec]. Upgrade [chars] [chars] to COOP version [dec].[dec].[dec] to prevent COOP outage.
Explanation	Coop KS has different minor version.
Recommended Action	show crypto gdoi ks coop

%GDOI-3-COOP_MAJOR_VERSION_MISMATCH : COOP-KS Major Version mismatch in group [chars]. My version is [dec].[dec].[dec], peer [chars] has version [dec].[dec].[dec]
Explanation	COOP-KS has a non-compatible major version.
Recommended Action	Check COOP version compatibility on KS

%GDOI-3-COOP_LIMIT_REACHED : Peer [chars] has reached COOP limit of maximum number of gms. COOP GM database sync fails. Upgrade to COOP version [dec].[dec].[dec] and above
Explanation	COOP-KS has a non-compatible peer.
Recommended Action	Check COOP version compatibility on peer KS

%GDOI-5-POLICY_CHANGE : GDOI group [chars] policy has changed. Use ‘crypto gdoi ks rekey’ to send a rekey, or the changes
will be send in the next scheduled rekey

Explanation

Reminder message that GDOI configuration has changed.

Recommended Action

%GDOI-5-ESON_POLICY_CHANGE_RESTART1 : ESON group [chars] policy has changed. Must use ‘clear crypto gdoi ks members now’
to restart the group

Explanation

Reminder message that ESON configuration has changed.

Recommended Action

%GDOI-5-ESON_POLICY_CHANGE_RESTART2 : ESON group [chars] policy has changed. Must use ‘crypto gdoi ks replace now’ to restart
the group

Explanation

Reminder message that ESON configuration has changed.

Recommended Action

%GDOI-5-GM_DELETE_EXPIRED_KEK : KEK expired for group [chars] and was deleted

Explanation

Deleting Expired KEK

Recommended Action

%GDOI-5-GM_DELETE_EXPIRED_PIP : PIP with SPI 0x[chars] expired for group [chars] and was deleted

Explanation

Deleting Expired PIP

Recommended Action

%GDOI-5-GM_DELETE_EXPIRED_P2P : P2P SA with epoch hash 0x[chars] expired for group [chars] and was deleted

Explanation

Deleting Expired P2P

Recommended Action

%GDOI-5-POLICY_CHANGE_TO_SUITEB : Group [chars] changed to Suite-B policy. Use ‘crypto gdoi ks rekey’ to generate the new
Suite-B policy and cause all GMs to re-register to download SIDs, or this will happen in the next scheduled rekey

Explanation

Migrating from non-Suite-B to Suite-B policy requires that the user issues ‘crypto gdoi ks rekey’ like any other POLICY_CHANGE,
but this will cause a re-initialization rather than just a rekey.

Recommended Action

%GDOI-5-KS_REINIT_GROUP : [chars] for group [chars] and will re-initialize the group.

Explanation

KS has reached one of the following conditions (indicated by the first part of the message) requiring re-initialization of
the group: — Group Size configuration changed — Previously used KSSID removed from configured KSSID set — KS runs out of KSSIDs
& GMSIDs — COOP SID client gets a re-initialization indication from COOP-KS — KSSID overlap detected by COOP is resolved —
TEK policy is changed from non-CTR to CTR (SIDs required).

Recommended Action

%GDOI-5-KS_REINIT_FINISH : Re-initialization of group [chars] completed.

Explanation

A previously triggered re-initialization, as signified by a %GDOI-5-KS_REINIT_GROUP syslog, has completed after the expiry
of the old TEK.

Recommended Action

%GDOI-3-KS_NO_SID_AVAILABLE : GMs for group [chars] need SIDs but this KS has no KS SIDs configured or no more SIDs available.
Explanation	This KS has a counter-mode transform configured requiring SIDs and either has no KSSIDs configured or has run out of SIDs. Registering GMs will not be able to register successfully until more KSSIDs are configured on this KS.
Recommended Action	Check the configured KSSID(s) for this KS by issuing ‘show crypto gdoi ks ident detail’ and consider configuring more KSSIDs using the ‘identifier’ sub-mode under ‘server local’.

%GDOI-3-COOP_KSSID_OVERLAP : Overlapping KS Sender Identifier(s) (KSSID) {[chars]} with COOP-KS peer [chars] in group [chars] blocking GM registration (MISCONFIG)
Explanation	Another COOP-KS peer in the group has been configured with a KSSID value that is the same as one configured on this KS. GM registration is blocked as a result until the overlap is fixed.
Recommended Action	Check the configured KSSID(s) for all COOP-KS peers by issuing ‘show crypto gdoi ks coop ident detail’ on the primary KS

%GDOI-5-COOP_KSSID_OVERLAP_RESOLVED : Resolved overlapping KS Sender Identifier(s) (KSSID) with COOP-KS peer allowing GM
registrations once again

Explanation

Another COOP-KS peer in the group had been configured with a KSSID value that was the same as one configured on this KS, but
has been resolved so that GM registration is allowed again.

Recommended Action

%GDOI-5-GM_IV_EXHAUSTED : GM for group [chars] exhausted its IV space for interface [chars] and will re-register.

Explanation

One of the interfaces where a CTR transform (e.g. GCM-AES / GMAC-AES) has been installed as TEK policy with SIDs has exhausted
its IV space & must re-register to receive new SIDs.

Recommended Action

%GDOI-5-GM_REKEY_IPV4_POLICY_CHECK_FAIL : Non-IPv4 policies is received in IPv4 Group [chars]; rekey is rejected
Explanation	This GM is registering to an IPv4 group but erroneously receiving IPv6 policies in rekey
Recommended Action	Contact the Key server’s administrator.

%GDOI-5-GM_REKEY_IPV6_POLICY_CHECK_FAIL : Non-IPv6 policies is received in IPv6 Group [chars]; rekey is rejected
Explanation	This GM is registering to an IPv6 group but erroneously receiving IPv4 policies in rekey
Recommended Action	Contact the Key server’s administrator.

%GDOI-4-UNKNOWN_GM_VERSION_REGISTER : WARNING: GM [IP_address] with unknown GDOI ver registered to group [chars] (e.g old-IOS or non-Cisco GM please check ‘show crypto gdoi ks members’ and ‘show crypto gdoi feature’ to ensure all your GMs can support the GETVPN features enabled.
Explanation	A GM is registered with unknown GDOI SW version; cannot determine its feature capability.
Recommended Action	Check GMs can support all GETVPN features enabled in KS. Also check output of ‘show crypto gdoi feature’ and ‘debug crypto gdoi ks infra detail’ (note: high volume of debugs). msgdef_ddts_component(ipsec-getvpn)

%GDOI-4-NEWER_GM_VERSION_REGISTER : WARNING: GM [IP_address] registers to group [chars] with newer GDOI version than KS. Please check’show crypto gdoi ks members’ and ‘show crypto gdoi feature’ to ensure all GMs can support the GETVPN features enabled.
Explanation	A GM is registered with newer GDOI SW version; cannot determine its feature capability.
Recommended Action	Check GMs can support all GETVPN features enabled in KS. Also check output of ‘show crypto gdoi feature’ and ‘debug crypto gdoi ks infra detail’ (note: high volume of debugs). msgdef_ddts_component(ipsec-getvpn)

%GDOI-4-REJECT_GM_VERSION_REGISTER : Reject registration of GM [IP_address] (ver [hex]) in group [chars] as it cannot support these GETVPN features enabled: [chars]
Explanation	Reject GM registration because it cannot support the GETVPN features enabled in the group.
Recommended Action	Check GMs can support all GETVPN features enabled in KS. Also check output of ‘show crypto gdoi feature’ and ‘debug crypto gdoi ks infra detail’ (note: high volume of debugs). msgdef_ddts_component(ipsec-getvpn)

%GDOI-4-GM_RECOVERY_REGISTRATION : GM recovery re-registration for group [chars] will start in a randomly chosen period of [dec] sec
Explanation	GM recovery feature detects dataplane error and will re-register to KS to refresh keys and policy
Recommended Action	Informational message.

%GDOI-4-GM_RECOVERY_REGISTRATION_POSTPONED : Detects data error in group [chars] but the previous recovery/rekey has occured within the last recovery-check interval. Postpone recovery registration to start in [dec] sec
Explanation	GM recovery feature detects dataplane error and will re-register to KS to refresh keys and policy
Recommended Action	Informational message.

%GDOI-4-GM_SA_TRACK_SET_EOT_ERROR : Group [chars] encountered error in setting EOT object ID [dec] to state [chars].
Explanation	GM SA TRACK state change occur but fail to update EOT object ID accordingly
Recommended Action	Informational message. Check to make sure the EOT object ID is configured properly

%GDOI-5-POLICY_CHANGE_ERROR_MULTIPLE_PORTS : Multiple ports detected for ACL [chars] which is not supported. WARNING: No
TEK policy will be created.

Explanation

Informs user that there is an error in the ACL with regards to the number of ports.

Recommended Action

%GDOI-6-COOP_KS_VER_TRANSIT : Coop KS [chars] protocol version transits from version 1.0.1 to 2.0.0

Explanation

The KS is transitioning to a new version.

Recommended Action

%GDOI-4-COOP_KS_RBLY_FAILED : Coop KS [chars] in group [chars] session Reassembly failed in TransID [int]

Explanation

The KS COOP had an error reassmbling a packet from a peer KS

Recommended Action

%GDOI-4-COOP_KS_CHECKPT_MISMATCH : Coop KS [chars] in group [chars] received Checkpoint Mismatch message.

Explanation

The KS COOP had received a checkpoint mismatch from a KS COOP peer

Recommended Action

%GDOI-3-COOP_KS_CANNOT_FIND_PROFILE : Coop KS in group [chars] has a configured IKEv2 profile ‘[chars]’ that doesn’t exist.
The COOP will not come up until this error is fixed.

Explanation

The KS COOP coniguration redunadancy ikve2-profile specifies a profile that doesn’t exist. The COOP will not come up.

Recommended Action

%GDOI-5-IPSEC_INITIATE_GM_REGISTER : IPSEC initiate GDOI group [chars] to register

Explanation

IPSEC initiate a GM registration for the group

Recommended Action

%GDOI-3-IPSEC_INITIATE_GM_REGISTER_POSTPONE : IPSEC triggering registration for group [chars] too frequently. Postpone the registration to occur in [dec] msec.
Explanation	GM detects IPSEC triggering registration for the group too frequently. GDOI will rate-limit and postpone the registration.
Recommended Action	Contact the Group member’s administrator.

%GDOI-3-IPSEC_INITIATE_GM_REGISTER_IGNORE : IPSEC triggering registration for group [chars] too frequently. Ignore the request as registartion has already been scheduled to occur in [dec] msec.
Explanation	GM detects IPSEC triggering registration for the group too frequently. GDOI will ignore the request as registration has already been scheduled.
Recommended Action	Contact the Group member’s administrator.

%GDOI-3-COOP_KS_TOO_MANY_GROUPS_SHARE_IKE_SA : The COOP KS has too many groups sharing the same IKE SA for the peer addresses
local [chars] remote [chars]. Connectivity could be compromised. Please reduce to [dec].

Explanation

There is a limit to the number of COOP KS groups that can share the. same IKE SA. This can lead to intermittent connectivity
for the COOP KS in congested networks

Recommended Action

%GDOI-3-COOP_KS_SEND_WINDOW_LIMIT_REACHED : The COOP KS has reached its window limit for the peer addresses local [chars]
remote [chars]. This is due to connectivity issues between the key servers in question.

Explanation

The COOP KS running over IKEv2 has a limit to the number of pending messages that can be sent. This limit has been reached
which is an indication that there is a connectivity issue between the key servers

Recommended Action

%GDOI-4-REJECT_GM_CKM_REGISTER : Reject registration of GM [IP_address] in group [chars] as it has CKM enabled but this secondaryKS
has not sync up all KGS params yet

Explanation

Reject GM registration because this is a secondaryKS and it has not received KGS seed and rekey-epoch from primaryKS yet

Recommended Action

%GDOI-4-COOP_KS_CKM_INCOMPATIBLE : Found incompatible COOP-KS that cannot support CKM in group [chars]. Please check ‘show
crypto gdoi feature ckm’and upgrade the incompatible KS immediately.

Explanation

Found incompatible COOP-KS that cannot support CKM in the group. Network administrator should check ‘show crypto gdoi feature
ckm’and upgrade the incompatible KS immediately

Recommended Action

%GDOI-5-GM_REGISTER_UPDATE_TBAR : Platform HA forwarding-plane comes online, group [chars] gm-identity [chars] fvrf [chars]
ivrf [chars] re-register to refresh TBAR info.

Explanation

HA forwarding-plane comes online, group %s gm-identity %s fvrf %s ivrf %s is re-registering to refresh TBAR info.

Recommended Action

%GDOI-3-GM_IPD3P_NO_IPV6_SUPPORT : GETVPN group-member does not support IP-D3P for IPv6.
Explanation	GETVPN group-member does not support IP-D3P for IPv6.
Recommended Action	Contact the Administrator(s) to correct the key server policy.

%GDOI-3-GM_IPD3P_NO_TRANSPORT_SUPPORT : GETVPN group-member does not support IPD3P transport mode
Explanation	GETVPN group-member does not support IPD3P transport mode
Recommended Action	Contact the Administrator(s) to correct the key server policy.

%GDOI-3-GM_IPD3P_AND_CMD_CANT_COEXIST : GETVPN group-member does not support coexistance of IPD3P and Cisco-metadata features
Explanation	GETVPN group-member does not support the enabling of IPD3P and Cisco-metadata features (e.g TBAR-PST, SGT) at the time
Recommended Action	Contact the Administrator(s) to correct the key server policy.

GENERIC_SUBBLOCK

%GENERIC_SUBBLOCK-2-LATE_REGISTER : Late registration of GSB type [chars], with id [dec]

Explanation

An attempt to register a new generic subblock type was received after subblocks have already been allocated from the control
structure with previously registered types

Recommended Action

%GENERIC_SUBBLOCK-2-BUILDXDR : Failed to build message for GSB: [chars]

Explanation

An attempt to build a message for distribution of generic subblock failed

Recommended Action

%GENERIC_SUBBLOCK-2-UNPACKXDR : Unpacked [dec] bytes and attempted to consume [dec] bytes for GSB: [chars]

Explanation

A discrepancy was detected between length of message expected versus length of message received

Recommended Action

%GENERIC_SUBBLOCK-2-GSBNOTISSUAWARE : GSB [chars] is not ISSU aware. Cannot distribute it to ISSU-aware slots

Explanation

This GSB is expected to be ISSU aware but it is not. It cannot be distributed safely to ISSU-aware slots as it may not be
correctly interpreted

Recommended Action

GEN_DB

%GEN_DB-3-NULL_TREE_NODE : Node is NULL [chars]
Explanation	This message indicates that the tree node being examined is NULL
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%GEN_DB-3-INVALID_RECORD_KEY : [chars]: invalid record key *
Explanation	This message indicates that the record key is invalid
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%GEN_DB-3-NO_KEY_FUNC : [chars]: [chars][chars]
Explanation	This message indicates that key functions are missing from the database handle, or key function is a NULL Pointer
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%GEN_DB-3-KEY_FUNC_DOESNT_EXIST : [chars]: Key function does not exist
Explanation	This message indicates that key function being considered does not exist in the database definition
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%GEN_DB-3-INVALID_CLIENT_TYPE : [chars]: Invalid client type, got [dec] (must be between 0 and [dec])
Explanation	This message indicates that client type is outside the expected range
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%GEN_DB-3-NULL_DB_HNDL : NULL Database Handle [chars]
Explanation	This message indicates the database handle was NULL
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%GEN_DB-3-NULL_DB_HNDL_ELEMENT : [chars]: NULL Database Element [chars]
Explanation	This message indicates the database handle element was NULL
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%GEN_DB-3-LIST_FAIL : [chars]:[chars]
Explanation	This message indicates that a list operations such as enqueue, dequeu failed
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%GEN_DB-3-LIST_FAIL_FOR_RECORD : [chars]:[dec]:[chars]
Explanation	This message indicates that a list operations such as enqueue, dequeu failed
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%GEN_DB-3-WAVL_FAIL : [chars]: [chars]
Explanation	This message indicates that a wavl tree operation failed
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%GEN_DB-3-RECORD_DELETE_FAIL : [chars]:[chars]
Explanation	This message indicates that a record could not be deleted
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%GEN_DB-3-PARSER_INIT_FAIL : [chars]:[dec]: Parser Could not be initialized
Explanation	This message indicates that the IOS Parser command could not be initialized
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%GEN_DB-3-UNKNOWN_PARSER_CMD : [chars]:[dec]: Unknown Parser Command
Explanation	This message indicates that the IOS Parser command was not recognized
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

GEN_PROXY

%GEN_PROXY-3-IPC_UNHANDLED : failure
Explanation	An unknown message type: %d was received by the Generic Client Proxy.
Recommended Action	LOG_STD_ACTION

%GEN_PROXY-3-REPLY_MSG : wrong version [dec]
Explanation	An incorrect SBS message was received by the Generic Client Proxy.
Recommended Action	LOG_STD_ACTION

%GEN_PROXY-3-STACK_ALLOC_FAILED : Stack allocation for reply failed reply_size [hex]
Explanation	Stack space could not be allocated for reply.
Recommended Action	LOG_STD_ACTION

%GEN_PROXY-3-GPM_ALLOC_FAILED : GPM allocation for reply failed pak_size [hex] reply_size [hex]
Explanation	GPM could not be allocated for reply.
Recommended Action	LOG_STD_ACTION

%GEN_PROXY-3-IPC_SEND_FAILED : IPC send reply failed [chars]
Explanation	GEN proxy failed to send of reply to IPC msg.
Recommended Action	LOG_STD_ACTION

GLBP

%GLBP-4-BADAUTH : Bad authentication received from [chars], group [dec]
Explanation	Two routers participating in a Gateway Load Balancing Protocol group disagree on the valid authentication string.
Recommended Action	Use the glbp authentication interface command to repair the GLBP authentication discrepancy between the local system and the one whose IP address is reported.

%GLBP-3-MISCONFIG : Cannot add MAC address [enet] to interface [chars] — not supported

Explanation

A software or hardware error 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.

%GLBP-6-STATECHANGE : [chars] Grp [int] state [chars] -> [chars]
Explanation	The GLBP gateway has changed state
Recommended Action	No action is required.

%GLBP-6-FWDSTATECHANGE : [chars] Grp [int] Fwd [int] state [chars] -> [chars]
Explanation	The GLBP forwarder has changed state
Recommended Action	No action is required.

%GLBP-4-DUPADDR : Duplicate address [chars] on [chars], sourced by [enet]
Explanation	The IP address in a GLBP message received on the interface is the same as the router’s own IP address. This may be because of misconfiugration, or because of a malfunctioning switch
Recommended Action	Check the configurations on all the GLBP routers, and make sure that any switches you have are functioning properly.

%GLBP-4-DUPVIP1 : [chars] Grp [dec] address [chars] is already assigned to [chars] group [dec]
Explanation	The GLBP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to a different GLBP group.
Recommended Action	Check the configuration on all GLBP routers.

%GLBP-4-DUPVIP2 : [chars] Grp [dec] address [chars] is already assigned on this interface
Explanation	The GLBP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to this interface.
Recommended Action	Check the configuration on all GLBP routers.

%GLBP-4-DUPVIP3 : [chars] Grp [dec] address [chars] is already assigned to, or overlaps with, an address on another interface or application
Explanation	The GLBP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to, or overlaps with, an address on another interface or application.
Recommended Action	Check the configuration on all GLBP routers.

%GLBP-4-BADVIP : [chars] Grp [dec] address [chars] is in the wrong subnet for this interface
Explanation	The GLBP virtual IP address contained in the Hello message cannot be learnt as it is not within a subnet configured on the interface.
Recommended Action	Check the configuration on all GLBP routers and ensure that the virtual IP address is within a configured subnet.

%GLBP-4-DIFFVIP1 : [chars] Grp [dec] active routers virtual IP address [chars] is different to the locally configured address [chars]
Explanation	The GLBP virtual IP address contained in the Hello message from the Active router is different to that configured locally.
Recommended Action	Check the configuration on all GLBP routers.

GRIP

%GRIP-3-BADPATHS : Invalid number of paths ([dec]) for %q
Explanation	An internal inconsistency was detected in the XNS routing table structure.
Recommended Action	Note the parameters associated with this message and call your technical support representative for assistance.

%GRIP-2-BADROUTE : Error [chars] route — null table
Explanation	A hardware or software error occurred.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

HA

%HA-6-TOOBIG : Running config too big, config sync failed
Explanation	The running config was too big to be synced
Recommended Action	No action is required.

%HA-6-SWITCHOVER : Route Processor switched from standby to being active
Explanation	This RP switched to become the active RP
Recommended Action	No action is required.

HAL_GENMEM

%HAL_GENMEM-3-HAL_MISMATCHED_GENMEM : VADDR:[int] LINE: [dec]
Explanation	Mismatched genmem.
Recommended Action	LOG_STD_ACTION

HAL_PACKET through HTSP

HAL_PACKET
HA_EM
HA_PROXY
HDLC
HFSLIB
HMAN
HMAN_CPU
HPI
HSRP
HTSP

HAL_PACKET

%HAL_PACKET-3-HAL_GATHER_ASYNC_WAIT_TIMEOUT : seqnum=[int] pak-type=[int]
Explanation	Packet Hardware Transmit Error
Recommended Action	LOG_STD_ACTION

HA_EM

%HA_EM-7-FMCMN_PTHREAD_MUTEX_LOCK : [chars]: Error locking mutex [chars]; [chars]
Explanation	The pthread_mutex_lock function reported an error while attempting to lock the specified mutex.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMCMN_PTHREAD_MUTEX_UNLOCK : [chars]: Error unlocking mutex [chars]; [chars]
Explanation	The pthread_mutex_unlock function reported an error while attempting to unlock the specified mutex.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFDCMN_DM_CREATE : [chars]: could not create dispatch manager: [chars]
Explanation	The event detector has failed to create an dispatch manager.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFDCMN_EA_ATTACH : [chars]: could not register for asynchronous message events: [chars]
Explanation	The event detector has failed to attach an event handler for asynchronous messages.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFDCMN_INV_TM : [chars]: invalid timer: type=[dec], timer=[IPV6 address]
Explanation	Internal error. The timer value is invalid or not as expected.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFDCMN_INV_TM_TYPE : [chars]: invalid timer type: [dec]
Explanation	Internal error. The timer type is invalid or not supported.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFDCMN_MSGSEND_EVT : [chars]: error returned from event_send_pulse; [chars]
Explanation	The event detector has failed to send a pulse to itself to notify of a pending message send event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFDCMN_PUB_RBLD : [chars]: [chars]
Explanation	Internal error. The event detector has failed to rebuild the publish list from the checkpointed records.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFDCMN_XDM_DISPATCH_FAIL : [chars]: XOS Dispatch Manager dispatch error: [dec]
Explanation	XOS Dispatch Manager reports an error when dispatching an event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFDCMN_XDM_WAIT_FAIL : [chars]: XOS Dispatch Manager wait error: [dec]
Explanation	XOS Dispatch Manager reports an error when waiting for an event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_ADD_PARSER : [chars]: Unable to add [chars] event detector command;
Explanation	The Event detector failed to add command.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_CHKPT_INIT : [chars]: [chars]
Explanation	Internal error. The event detector has failed to initialize with the checkpointing server.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_CHKPT_TBL_ADD : [chars]: [chars]
Explanation	Internal error. The event detector has failed to add a record to the checkpointing table.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_CHKPT_TBL_INIT : [chars]: [chars]
Explanation	Internal error. The event detector has failed to initialize a table with the checkpointing server.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_CHKPT_TBL_ITERATE : [chars]: [chars]
Explanation	Internal error. The event detector has failed to iterate the checkpointing table.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_CHKPT_TBL_REMOVE : [chars]: [chars]
Explanation	Internal error. The event detector has failed to remove a record from the checkpointing table.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_COND_WAIT : [chars]: conditional wait error: [chars]
Explanation	Internal error. The event detector has failed to do pthread conditional wait.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_CONNECTION_FAIL : Could not connect to [chars] : [chars]
Explanation	Could not connect to event detector on the remote node. Node may be invalid or not available or the process may not be available to accept the connection.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_DE_FETCH : [chars]: [chars][[dec]]
Explanation	Internal error. The event detector has failed to fetch a data elementfrom the statistics data engine.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_DE_INIT : [chars]: [chars]
Explanation	Internal error. The event detector has failed to initialize the statistics data engine.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_DM_CREATE : [chars]: could not create dispatch manager: [chars]
Explanation	The event detector has failed to create an dispatch manager.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_EA_ATTACH : [chars]: could not register for asynchronous message events: [chars]
Explanation	The event detector has failed to attach an event handler for asynchronous messages.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMFD_EMPTY_QUEUE : [chars]: The [chars] event detector I/O queue empty.
Explanation	The I/O queue is empty at this point, and should not be.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_ENQUEUE_FAIL : [chars]: Unable to enqueue [chars];
Explanation	The enqueue function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_EV_BLOCK : [chars]: [chars]
Explanation	The event_block function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_EVM_CREATE : Could not create event manager: [chars]
Explanation	The event detector has failed to create an Event Manager.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_HIST_QERR : [chars]
Explanation	Internal error. The event detector has failed to get a free history listentry.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_HIST_RBLD : [chars]: [chars]
Explanation	Internal error. The event detector has failed to rebuild the history list from the checkpointed records.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_INV_COMPARE_OP : [chars]: invalid comparison operator: [dec]
Explanation	Internal error. The value comparison operator is invalid or notsupported.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_INV_STATS_TYPE : [chars]: invalid statistics value type: [dec]
Explanation	Internal error. The statistics data type is invalid or not supported.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_INV_TM : [chars]: invalid timer: type=[dec], timer=[IPV6 address]
Explanation	Internal error. The timer value is invalid or not as expected.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_INV_TM_TYPE : [chars]: invalid timer type: [dec]
Explanation	Internal error. The timer type is invalid or not supported.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_LOCAL_NODEID : Could not get local nodeid: [chars]
Explanation	Could not get local node identifier.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_MALLOC : [chars]: Unable to allocate [chars]; [chars]
Explanation	The malloc function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_MET_ENQUEUE : [chars]: could not enqueue metric data: [chars]
Explanation	Internal error. The system manager event detector has failed to add a metric data entry to the list.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_MET_RBLD : [chars]: [chars]
Explanation	Internal error. The event detector has failed to rebuild the metriclist from the checkpointed records.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_MISC_ERR : [chars]: [chars]
Explanation	An unexpected error occurred.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_MSGSEND_EVT : [chars]: error returned from event_send_pulse; [chars]
Explanation	The event detector has failed to send a pulse to itself to notify of a pending message send event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_MSGSEND_RETRY_ERR : [chars]: [dec]
Explanation	The event detector has exceeded its maximum number of retries to send apulse to the embedded event manager to notify of an event publish.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_NO_CLOCK : [chars]: unable to read clock using clock_gettime: [chars]
Explanation	The clock_gettime function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_NO_MEM : [chars]: not enough memory: [chars]
Explanation	Allocating memory failed due to a low-memory condition.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_OE_CREATE : [chars]: could not create an occurrence entry
Explanation	Internal error. The event detector has failed to create an entry for thematched occurrence list.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_OE_REMOVE : [chars]: could not remove an occurrence entry
Explanation	Internal error. The event detector has failed to remove an entry for thematched occurrence list.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMFD_OID_UNAVAIL : [chars]: The following oid has become unavailable: [chars]
Explanation	The registered oid is no longer available in the system.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_OPEN_CONF : [chars]: could not open event detector config file: [chars]
Explanation	The event detector has failed to open the config file for event detector type information.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_PTHRD_CREATE : [chars]: could not create a Posix thread
Explanation	The pthread_create function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_PUB_RBLD : [chars]: [chars]
Explanation	Internal error. The event detector has failed to rebuild the publish list from the checkpointed records.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_PUB_TM_ALLOC : [chars]: Unable to allocate memory for event publish timer block
Explanation	Internal error. The event detector has failed to allocate memoryfor the event publish timer block.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMFD_QUEUE_INIT : [chars]: Unable to initialize queue;
Explanation	The queue initialization function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_RESOURCE_MONITOR_REGISTER_FAIL : [chars]: resource_monitor_register failed; return code = [dec]
Explanation	The resource_monitor_register function reported an error trying toregister for RMI notifications.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_RM_ATTACH : [chars]: could not attach resource manager funtions to event manager: [chars]
Explanation	The event detector has failed to attach a Resource Manager to an Event Manager.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SM_PROC_EXIT : [chars]: [chars]
Explanation	The system manager failed to execute the default action of the terminated process.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_ADDR_ILLEGAL : [chars]: Illegal SNMP address type
Explanation	The SNMP address is illegal.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_ADDR_IPV6 : [chars]: SNMP IPV6 address is not supported
Explanation	The IPV6 address is not supported.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_BUILD_PDU_FAILED : [chars]: SNMP build pdu failed
Explanation	The SNMP pdu build has failed.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_COMM_FAIL : [chars]: Unable to create SNMP octet community string; string = [chars]
Explanation	The community string was not able to build into a SNMP octet string
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_COMMUNICATE_FAIL : [chars]: [chars] [chars]
Explanation	Unable to communicate with SNMPD process
Recommended Action	Check whether SNMP is configured on this Router.

%HA_EM-7-FMFD_SNMP_ERRCODE : [chars]: [chars]
Explanation	The SNMP error code.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_MAKE_PDU_FAILED : [chars]: SNMP make pdu failed
Explanation	The SNMP pdu make has failed.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMFD_SNMP_MIB_OBJ_REP_FAIL : [chars]: SNMP MIB object info replace failed [dec]
Explanation	The SNMP MIB object info replace function has failed.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_MSG_FAIL : [chars]: Unable to create a SNMP message; community = [chars]
Explanation	The SNMP message failed to be created
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-4-FMFD_SNMP_NO_OBJECT_VALUE : [chars]: SNMP MIB object value not provided
Explanation	The SNMP MIB object value is not provided for substitution.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMFD_SNMP_OBJECT_UNKNOWN_RESPONSE_CODE : [chars]: Unknown SNMP object response code [dec]
Explanation	The SNMP MIB object response code is unknown.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_OID_INVALID : [chars]: Invalid SNMP oid length [dec]
Explanation	The SNMP oid has invalid length
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_OID_MAKE_FAIL : [chars]: Unable to build an oid string into a SNMP oid; oid = [chars]
Explanation	The oid string was not able to build into a SNMP oid
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_REQ_FAILED : [chars]: SNMP request failed
Explanation	The SNMP request has failed.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_RESP_CANCEL : [chars]: SNMP response cancelled
Explanation	The SNMP response has been cancelled.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_RESP_ERROR : [chars]: SNMP response error; error_status = [dec]
Explanation	The SNMP response has error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_RESP_Q_EMPTY : [chars]: SNMP proxy exec got event, but queue is empty
Explanation	The SNMP proxy got event but the queue is empty.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_RESP_TIMEOUT : [chars]: SNMP response has timed out
Explanation	The SNMP response has timed out.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_UNKNOWN_TYPE : [chars]: Unknown SNMP operation or response type [dec]
Explanation	The operation or response type is unknown.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SNMP_VARBIND_FAIL : [chars]: Unable to create a SNMP varbind
Explanation	The oid failed to make into a SNMP varbind
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_STATS_VAL_GET_ERR : [chars]: [chars]
Explanation	Internal error. The event detector has failed retrieving a valid statistics value.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SYSDB_BIND : [chars]: [chars]
Explanation	Failed to bind to SysDB.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SYSDB_GET : [chars]: [chars]
Explanation	Failed to retrieve an item from SysDB.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_SYSDB_REG_NOTIFY : [chars]: [chars]
Explanation	Failed to register for notification of a set of items in SysDB.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_TM_CRTICK_INIT : [chars]: [chars]
Explanation	Internal error. The initialization of the cron-tick function has failed.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_TM_LEAF_NEW : [chars]: could not create a leaf timer
Explanation	Internal error. The event detector has failed to create a managedleaf timer.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMFD_TTY_NUM : [chars]: Error occurred while fetching TTY number.
Explanation	The Embedded Event Manager failed to fetch a TTY number.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_XDM_DISPATCH_FAIL : [chars]: XOS Dispatch Manager dispatch error: [dec]
Explanation	XOS Dispatch Manager reports an error when dispatching an event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMFD_XDM_WAIT_FAIL : [chars]: XOS Dispatch Manager wait error: [dec]
Explanation	XOS Dispatch Manager reports an error when waiting for an event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMC_APPL_CBH_PULSE : [chars]: Unable to locate application publish callback entry for pulse code [dec]
Explanation	The application publish callback handler was unable to validate the pulse code received.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMC_APPL_CBH_SEND : [chars]: Unable to send response for FH_MSG_CALLBACK_DONE [chars]
Explanation	The registration callback handler was unable to send the FH_MSG_CALLBACK_DONE message to the Embedded Event Manager Server.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMC_CB_CLOSE : [chars]: fh_close failed [chars]
Explanation	The fh_close function reported an error trying to initialize the internal callback connection.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMC_CB_EV_CREATE : [chars]: event_manager_create failed [chars]
Explanation	The event_manager_create function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMC_CBH_PROCESS_CREATE : [chars]: callback handler process create failed for eid: [dec]
Explanation	The process_create function reported an error trying to create thecallback handler process.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMC_CB_INIT : [chars]:[dec] (thread:[dec]) fh_init failed [chars]
Explanation	The fh_init function reported an error trying to initialize the internal callback connection.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMC_CBS_PT_CREATE : [chars]: pthread_create failed [chars]
Explanation	The pthread_create function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMC_ENQUEUE_FAIL : [chars]: Unable to enqueue [chars];
Explanation	The enqueue function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMC_FH_INIT : [chars]: fh_init failed : [dec]
Explanation	The fh_init function reported an error trying to initialize EEM fora callback process.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMC_INV_REPLY : [chars]: Application client library unable to handle message receive.
Explanation	The API received a msg reply when it was not in a state to acceptsuch messages.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMC_MALLOC : [chars]: Unable to allocate [chars];
Explanation	The malloc function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMC_REG_CBH_PULSE : [chars]: Unable to locate reg callback entry for pulse code [dec]
Explanation	The registration callback handler was unable to validate the pulse codereceived.
Recommended Action	The pthread_create function reported an error.

%HA_EM-7-FMC_REG_CBH_SEND : [chars]: Unable to send response for FH_MSG_CALLBACK_DONE [chars] [dec]
Explanation	The registration callback handler was unable to send theFH_MSG_CALLBACK_DONE message to the Embedded Event Manager Server.
Recommended Action	The pthread_create function reported an error.

%HA_EM-7-FMC_XDM_DISPATCH_FAIL : [chars]: XOS Dispatch Manager dispatch error: [dec]
Explanation	XOS Dispatch Manager reports an error when dispatching an event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMC_XDM_WAIT_FAIL : [chars]: XOS Dispatch Manager wait error: [dec]
Explanation	XOS Dispatch Manager reports an error when waiting for an event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_ACTION : [chars]: Error occurred while performing action: [chars].
Explanation	The Embedded Event Manager Policy Director failed to perform anaction for the registered event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_ACTION_INFO : [chars]: Error occurred while fetching action information: [dec].
Explanation	The Embedded Event Manager Policy Director failed to gather actioninformation registered for the event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_ACTION_NOTRACK : [chars]: unable to set state for tracking object number [int]; object does not exist or is not a stub-object.
Explanation	The Embedded Event Manager applet attempted to set the state ofa tracking object that does not exist.
Recommended Action	Only set the state of tracking objects that have already been configured in the system. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_CHECKSUM_MISMATCH : [chars]: file checksum mismatch
Explanation	The checksum value of an installed policy does not match the valueprovided by the installation manager.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_CHKPT_INIT : [chars]: could not register the application with the checkpointing server: [chars]
Explanation	Failed to register an application with the checkpointing server.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_CHKPT_ITERATE_END : [chars]: call to chkpt_iterate_end returned unexpected failure.
Explanation	Failed to register an application with the checkpointing server.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_CHKPT_NULL_PTR : [chars]: Got a null [chars] but non-null value was expected
Explanation	Failed to do further processing because we got a null data when a non-null value was expected.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_CHKPT_TBL_ADD : [chars]: could not save a record into a checkpointing table: [chars]
Explanation	Failed to save a record into the given checkpointing table.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_CHKPT_TBL_INFO_READ : [chars]: could not read the existing table information: [chars]
Explanation	Failed to read the existing table information using checkpointing API.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_CHKPT_TBL_INIT : [chars]: failed to initialize [chars]: [chars]
Explanation	Could not initialize a table with the checkpointing server.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_CHKPT_TBL_RECOVER : [chars]: could not recover the checkpointed [chars]: [chars]
Explanation	Failed to recover a checkpointed table.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_CHKPT_TBL_REMOVE : [chars]: could not delete a record from a checkpointing table: [chars]
Explanation	Failed to delete a record from the given checkpointing table.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_CHKPT_TBL_RESET : [chars]: could not reset a record in a checkpointing table: [chars]
Explanation	Failed to reset a record in the given checkpointing table.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_CLI_CONNECT : Unable to establish CLI session: [chars]
Explanation	Unable to establish CLI session.
Recommended Action

%HA_EM-3-FMPD_CLI_DISCONNECT : Error disconnecting from CLI session: [chars]
Explanation	An error occurred while disconnecting from the CLI session.
Recommended Action

%HA_EM-3-FMPD_CLI_NOTTY : Error attempting to access an unopened CLI session: [chars]
Explanation	An error occurred attempting to access an unopened CLI session: %s
Recommended Action

%HA_EM-3-FMPD_CLI_READ : Unable to read CLI response: [chars]
Explanation	Unable to read CLI response.
Recommended Action

%HA_EM-3-FMPD_CLI_WRITE : Unable to send CLI command: [chars]
Explanation	Unable to send CLI command.
Recommended Action

%HA_EM-6-FMPD_CONTEXT_RETRIEVE : Failed to retrieve context for key [chars]: [chars]
Explanation	Failed to context retrieve variable information for event.
Recommended Action	Ensure context information with the given key is saved. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-6-FMPD_CONTEXT_SAVE : Failed to save variable context for key [chars]: [chars]
Explanation	Failed to context save variable information for event.
Recommended Action	Ensure context information with the same key is not already saved. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-4-FMPD_DIRECTORY_NOT_EXIST : User policy directory [chars] could not be found on [chars]
Explanation	A policy directory could not be found. Cold start on this location may result in startup configuration failure.
Recommended Action	Create the directory on this location.

%HA_EM-6-FMPD_DIVIDE_ZERO : Invalid operand in arithmetic division, cannot divide by zero
Explanation	Arithmetic division does not allow divide by zero.
Recommended Action	Ensure denominator provided to division action is non-zero.

%HA_EM-4-FMPD_DSIG_TYPE_CHANGE : Cisco Signature not found or invalid. [chars] has been registered as a user policy.
Explanation	Cisco Signature not found or invalid.
Recommended Action	Sign with Cisco signature.

%HA_EM-6-FMPD_EEM_CONFIG : [chars]: [chars]
Explanation	The Embedded Event Manager reports an error on Event Managerconfiguration
Recommended Action	Check the EEM applet or policy configuration

%HA_EM-6-FMPD_EEM_LOG_MSG : [chars]
Explanation	The Embedded Event Manager reports errors when registering a TCL policy.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_ERROR : Error executing applet [chars] statement [chars]
Explanation	The Embedded Event Manager policy director found an error whenprocessing an applet.
Recommended Action	Check syntax of applet statement. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-4-FMPD_EVENT_CREATE : [chars]: failed to create an event: [chars]
Explanation	Failed to create an Embedded Event Manager event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-4-FMPD_EVENT_REG : [chars]: failed to register an event: [chars]
Explanation	Failed to register an Embedded Event Manager event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_EVENT_TYPE : [chars]: unknown event type [dec]
Explanation	An unknown Embedded Event Manager even type was detected.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_EVM_CREATE : [chars]: could not create event manager: [chars]
Explanation	An internal error was detected when creating Event Manager.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_EVM_EVENT_BLOCK : [chars]: failed to block waiting for Event Manager events: [chars]
Explanation	An internal error was detected when block waiting for Event Manager events.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_EXECUTE_CALLBACK : [chars]: failed to execute callback
Explanation	Failed to execute callback routine.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_FH_INIT : [chars]: could not initialize Embedded Event Manager service: [chars]
Explanation	An internal error was detected when initializing Embedded Event Managerservice.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_FILE_CLOSE : [chars]: failed to close fd [chars] : [chars]
Explanation	Failed to close the given file descriptor due to some internal error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_FILE_DELETE : [chars]: failed to delete file: [chars] : [chars]
Explanation	Failed to delete the given file.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_FILE_OPEN : [chars]: failed to open file [chars] : [chars]
Explanation	Failed to open the given file due to some internal error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_FILE_READ : [chars]: failed to read from fd [chars] : [chars]
Explanation	Failed to read from the given file descriptor due to some internal error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_FILE_WRITE : [chars]: failed to write to fd [chars] : [chars]
Explanation	Failed to write to the given file descriptor due to some internal error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_FORMAT_TIME : [chars]: error attemting to format time string
Explanation	Format time failure.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_GET_PRIO : [chars]: failed to get process priority: [chars]
Explanation	Internal error. A call to get process scheduling priority failed.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-4-FMPD_IPC_GET_PAK : [chars]: failed to allocate an IPC buffer
Explanation	Embedded Event Manager failed to allocate a buffer from IPC.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_IPC_PORT_CREATE : [chars]: failed to create an IPC port: [chars]
Explanation	Embedded Event Manager failed to create an IPC port.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_IPC_PORT_OPEN : [chars]: failed to open an IPC port: [chars]
Explanation	Embedded Event Manager failed to open an IPC port.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_IPC_PORT_REGISTER : [chars]: failed to register an IPC port: [chars]
Explanation	Embedded Event Manager failed to register an IPC port.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-4-FMPD_IPC_SEND_MSG : [chars]: failed to send an IPC message: [chars]
Explanation	Embedded Event Manager failed to send a message through IPC.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_LAST_POLICY : [chars]: invalid last policy name replied [chars]
Explanation	Internal error. The last policy name the script director repliedto show fm policy registered command is an invalid policy name.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_MEM_ALLOC : Not enough memory ([dec] bytes)
Explanation	Allocating memory failed due to a low-memory condition.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-4-FMPD_NO_ACTION : No action configured for applet [chars]
Explanation	No action has been configured for this applet.
Recommended Action	Configure at least one action for this applet.

%HA_EM-7-FMPD_NO_CLOCK : [chars]: unable to read clock using clock_gettime: [chars]
Explanation	The clock_gettime function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_NOEID : [chars]: No such event id found.
Explanation	An internal software error occurred.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_NOESID : [chars]: No such event spec id found.
Explanation	The Embedded Event Manager Policy Director could not find the eventfor the event spec. ID.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-4-FMPD_NO_EVENT : No event configured for applet [chars]
Explanation	No event has been configured for this applet.
Recommended Action	Configure an event for this applet.

%HA_EM-7-FMPD_NO_MEM : [chars]: not enough memory: [chars]
Explanation	Allocating memory failed due to a low-memory condition.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_NO_PROC : [chars]: Failed to create process
Explanation	The process create function reports an error
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-4-FMPD_NOTAGNAME : [chars]: No tag [chars] found corresponding to this event publish.
Explanation	The Embedded Event Manager policy director could not associate the tagname with a published event.
Recommended Action	Only use tagnames in the action info type event reqinfo command which correspond to the published event.

%HA_EM-6-FMPD_OPERAND_INVALID : Invalid operand in action, expected value within range %ld to %ld, received: [chars]
Explanation	Arithmetic actions only accept valid long integer values.
Recommended Action	Ensure value provided to action is long integer.

%HA_EM-3-FMPD_OVL_NOTIF_REG : [chars]: could not register for Version Manager notification: [chars]
Explanation	An internal error was detected when registering for Version Manager notification.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_OVL_SETUP_ENV : [chars]: [chars]
Explanation	Updating environment variables of the process according to system variables stored in sysdb failed.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-4-FMPD_POLICY_APPLY : Could not apply policy ‘[chars]’: [chars]
Explanation	A policy could not be applied. This message signaled an unsuccessful apply of the policy.
Recommended Action	Remove the configuration for the policy (and commit), and then attempt to configure the registration of the same policy.

%HA_EM-6-FMPD_POLICY_CHANGED : [chars]: registered policy [chars] changed by the last installation update
Explanation	A registered policy was changed by the last installation update. If the update used the start option, the old policy was automatically unregistered and the new policy registered. Otherwise, the old policy would remain registered and functional until the user unregisters it manually.
Recommended Action	None.

%HA_EM-4-FMPD_POLICY_CONFIG_INCONSISTENT : Policy ‘[chars]’: [chars]
Explanation	Some policy configuration is potentially inconsistent, and the user should follow the guidelines in the message to amend this.
Recommended Action	Examine the guidelines in the message, and the event manager configuration,to determine the potential problem. Note that this is just a warning message, not an error message, as the configuration is legal — it may be the case that the user has intentionally set this configuration.

%HA_EM-6-FMPD_POLICY_DELETED : [chars]: registered policy [chars] deleted by the last installation update
Explanation	A registered policy was deleted by the last installation update. If the update used the start option, the policy was automatically unregistered. Otherwise, the policy would remain registered and functional until the user unregisters it manually.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_POLICY_HASH : [chars]: The hash computation routine reported an error; [chars]
Explanation	The policy dir checksum function reported the specified error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-4-FMPD_POLICY_NOT_EXIST : Policy file [chars] could not be found on [chars]
Explanation	A policy file could not be found. Cold start on this location may result in startup
Recommended Action	Copy the policy file to this location.

%HA_EM-6-FMPD_POLICY_REG_SUCC : [chars]: Policy ‘[chars]’ registered successfully, by user [chars], with persist time [dec] and type [dec]
Explanation	A new policy has been registered with Embedded Event Manager. This message signaled a successful registration.
Recommended Action	None.

%HA_EM-7-FMPD_POLICY_TBL_REMOVE : [chars]: could not delete a record from a checkpointing table: [chars]
Explanation	Failed to delete a record from the given checkpointing table.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-4-FMPD_POLICY_TUPLE_UNPACK : Failed to unpack_tuple to get username (Err: [dec]) for [chars]
Explanation	Failed to unpack sysdb tuple to get the username for the scripts.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_POLICY_UNREG_ERR : [chars]: could not unregister policy [chars]: [chars]
Explanation	A registered policy changed or deleted by the last installation update was detected. Since the update used the start option, the old policy was automatically unregistered. This message signaled an unsuccessful unregistration.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_POLICY_UNREGREG_ERR : [chars]: could not replace policy [chars]: [chars]
Explanation	A registered policy changed by the last installation update was detected. Since the update used the start option, the old policy was automatically replaced by the new policy. This message signaled an unsuccessful replacement of the policy.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-6-FMPD_POLICY_UNREGREG_SUCC : [chars]: policy [chars] replaced successfully
Explanation	A registered policy changed by the last installation update was detected. Since the update used the start option, the old policy was automatically replaced by the new policy. This message signaled a successful replacement of the policy.
Recommended Action	None.

%HA_EM-6-FMPD_POLICY_UNREG_SUCC : [chars]: policy [chars] unregistered successfully
Explanation	A registered policy changed or deleted by the last installation update was detected. Since the update used the start option, the old policy was automatically unregistered. This message signaled a successful unregistration.
Recommended Action	None.

%HA_EM-3-FMPD_PROCESS_XML : [chars]: error processing xml buffer
Explanation	An error occurred processing the event publish information xml buffer.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_QUEUE_INIT : [chars]: could not initialize queue
Explanation	An internal error was detected when initializing Embedded Event Managerqueue.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_REFRESHTIMER_INIT : Failed to initialize a refresh timer ([chars]): [chars]
Explanation	Failed to initialize a Embedded Event Manager refresh timer.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-6-FMPD_REGCOMP : Error compiling regular expression: [chars]
Explanation	An error was encountered when compiling the given regular expression.
Recommended Action	Check syntax of regular expression pattern. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_REQINFO : [chars]: Error attempting to fetch event information: [chars].
Explanation	The Embedded Event Manager Policy Director failed to receive event infofor a callback.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_SET_INFO : [chars]: Error occurred while fetching variable information: [dec].
Explanation	The Embedded Event Manager Policy Director was unable to set thevariable with the requested information.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_SHM_OPEN : [chars]: ERROR opening shared mem IDB
Explanation	An internal error was detected when attempting to open the IDB shared memory area
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_SMTP : Error occurred when sending mail to SMTP server: [chars] : [chars]
Explanation	An unexpected error occurred when sending mail to SMTP server.
Recommended Action

%HA_EM-3-FMPD_SMTP_SEND : Unable to send notification using all SMTP servers
Explanation	An unexpected error occurred when sending mail to all SMTP servers.
Recommended Action

%HA_EM-6-FMPD_SNMP_DUP_OID : [chars]: duplicate oid
Explanation	The oid is a duplicate
Recommended Action	Check the EEM applet or policy configuration

%HA_EM-6-FMPD_SNMP_NO_VAR : [chars]: No variable [chars]
Explanation	The variable is not defined.
Recommended Action	Check the EEM applet or policy configuration

%HA_EM-6-FMPD_SNMP_TRAPVAR_ADD : [chars]: Error adding trapvar to queue [chars]
Explanation	The trap variable was not added to the queue.
Recommended Action	Check the EEM applet or policy configuration

%HA_EM-6-FMPD_SNMP_VARS_EXCEEDED : [chars]: number of values exceeded [dec]
Explanation	The number of values per variable exceeded the maximum
Recommended Action	Check the EEM applet or policy configuration

%HA_EM-7-FMPD_SWITCH_FAIL : [chars]: The system is unable to switch to standby processor. Switchover cancelled.
Explanation	Switchovers must occur when STANDBY is available and ready.
Recommended Action	None Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-6-FMPD_SWITCH_HARDWARE : [chars]: Policy has requested a hardware switchover
Explanation	An Embedded Event Manager policy requested that a hardware switchoveroccur.
Recommended Action	None

%HA_EM-7-FMPD_SYSDB_VERIFY_REG : Could not register for SysDB verification: [chars]
Explanation	An internal error was detected when trying to register verify function and/or apply function for SysDB tuple operations upon the given item within the given namespace.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_THREAD_POOL : [chars]: [chars]
Explanation	An internal error was detected while initialization of threadpool.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_UNKNOWN_ENV : [chars]: could not find environment variable: [chars]
Explanation	The Embedded Event Manager policy director could not find the environmentvariable specified in the action message.
Recommended Action	Only use well known Embedded Event Manager environment variables. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMPD_UNKNOWNTYPE : [chars]: Unknown event type found in applet.
Explanation	The Embedded Event Manager applet had an unknown event type.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-6-FMPD_UPDATE_POLICY_COPY : Policy update has copied [dec] bytes from [chars] to [chars]
Explanation	An EEM policy has been copied as a result of an event manager update command
Recommended Action

%HA_EM-6-FMPD_UPDATE_POLICY_REGISTER : Policy update has successfully re-registered policy [chars]
Explanation	An EEM policy has been successfully re-registered as a result of an event manager update command
Recommended Action

%HA_EM-6-FMPD_UPDATE_POLICY_REGISTER_FAIL : Policy update has failed to register policy [chars] [chars]
Explanation	An EEM policy has failed to be registered as a result of an event manager update command
Recommended Action

%HA_EM-6-FMPD_UPDATE_POLICY_UNREGISTER_FAIL : Policy update has failed to unregister policy [chars] [chars]
Explanation	An EEM policy has failed to be unregistered as a result of an event manager update command
Recommended Action

%HA_EM-3-FMPD_WRONGTYPE : [chars]: Published event type does not match event spec.
Explanation	The Embedded Event Manager Policy Director detected a mis-match in eventtype between the published event and the event spec.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_XDM_DISPATCH_FAIL : [chars]: XOS Dispatch Manager dispatch error: [dec]
Explanation	XOS Dispatch Manager reports an error when dispatching an event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMPD_XDM_WAIT_FAIL : [chars]: XOS Dispatch Manager wait error: [dec]
Explanation	XOS Dispatch Manager reports an error when waiting for an event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-ACTION_ADD_PARSER : [chars]: Unable to add action [chars] command;
Explanation	Failed to add action command.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-ACTION_CNS_AGENT_UNAVAIL : [chars]: CNS Event Agent not available: [dec]
Explanation	The CNS Event Agent is currently not available.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-ACTION_CNS_CLEAR_RESTART : [chars]: Unable to clear restart callback;
Explanation	The CNS Action process failed to clear restart callback.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-ACTION_CNS_OPEN_FAIL : [chars]: Unable to open connection to CNS Event Agent: [dec]
Explanation	The CNS Action process failed to open CNS handle to Event Agent.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-ACTION_CNS_SET_RESTART : [chars]: Unable to set restart callback;
Explanation	The CNS Action process failed to set the restart callback.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-ACTION_ENQUEUE_FAIL : [chars]: Unable to enqueue [chars];
Explanation	The enqueue function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-ACTION_WB_CREATE : [chars]: create_watched_boolean failed: [chars]
Explanation	The create_watched_boolean function reported an error trying to createthe watched boolean.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-ACTION_WB_DELETE : [chars]: delete_watched_boolean failed: [chars]
Explanation	The delete_watched_boolean function reported an error trying to delete the watched boolean.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_ASYNC_ATTACH_CHKPT : [chars]: Failed to attach to handle chkpt asynchronous events; [chars]
Explanation	The event_pulse_attach_event function reported an error trying to attach the chkpt pulse handler.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_ASYNC_ATTACH_DEFAULT : [chars]: Failed to attach to handle default asychronous events; [chars]
Explanation	The event_pulse_attach_event function reported an error trying to attach the default pulse handler.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_CHKPT_INIT : [chars]: could not register the application with the checkpointing server: [chars]
Explanation	Failed to register an application with the checkpointing server.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_CHKPT_ITERATE_END : [chars]: call to chkpt_iterate_end returned unexpected failure.
Explanation	Unexpected error when iterating over a checkpointing table.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_CHKPT_NULL_PTR : [chars]: Got a null [chars] when non-null value was expected
Explanation	Failed to do further processing because we got a null data when a non-null value was expected.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_CHKPT_TBL_ADD : [chars]: could not add to the checkpointed [chars]: [chars]
Explanation	Failed to add a record to the checkpointed table.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_CHKPT_TBL_INFO_READ : [chars]: could not read the existing table information: [chars]
Explanation	Failed to read the existing table information using checkpointing API.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_CHKPT_TBL_INIT : [chars]: failed to initialize [chars]: [chars]
Explanation	Could not initialize a table with the checkpointing server.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_CHKPT_TBL_RECOVER : [chars]: could not recover for the checkpointed [chars]: [chars]
Explanation	Failed to recover a record from the checkpointed table.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_CHKPT_TBL_REMOVE : [chars]: could not remove from the checkpointed [chars]: [chars]
Explanation	Failed to remove a record from a checkpointed table.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_CHKPT_TBL_SAVE : [chars]: could not save to the checkpointed [chars]: [chars]
Explanation	Failed to save a record to a checkpointed table.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_CHKPT_TBL_UNREG : [chars]: could not unregister the checkpointed table [chars]: [chars]
Explanation	Failed to unregister a checkpointed table.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMS_CNS_FAIL : [chars]: Failed to perform CNS action: [chars]
Explanation	The Embedded Event Manager failed attempting to send a CNS message.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_CREATE_THREAD_POOL : [chars]: Error reported by create_thread_pool function; [chars]
Explanation	The create_thread_pool function reported an error while attempting to create the thread pool.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMS_EMPTY_QUEUE : [chars]: The I/O queue empty.
Explanation	The I/O queue is empty at this point, and should not be.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMS_ENQUEUE_FAIL : [chars]: The Unable to enqueue packet onto queue.
Explanation	The queue is not in a state to handle enqueues.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_EVM_CREATE : [chars]: event_manager_create failed; [chars]
Explanation	The event_manager_create function reported an error trying to initialize the event manager.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_EVM_EVENT_BLOCK : An error occurred while waiting for an event: [chars]
Explanation	The event infrastructure will ignore this error and continue to wait for the next event. If this error is seen repeatedly, the process may not be able to function and will need to be restarted.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_FDC_ALLOCATE : [chars]: Failed to allocate Event Detector context control block; [chars]
Explanation	The get_fd function reported an error trying to allocate a Event Detectorcontext control block.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_FDC_OPEN : [chars]: Failed to open Event Detector context control block
Explanation	The open_fd function reported an error trying to open a Event Detectorcontext control block.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_GET_NODE_NAME : [chars]: platform_get_node_name failed; [chars]
Explanation	The platform_get_node_name function reported an error trying to obtain the node name.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_GET_NODE_STATE : Failed to get the current nodes state: [chars]
Explanation	The call to get the nodes current state failed.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_GET_PRIO : [chars]: Failed to get process priority; [chars]
Explanation	The getprio function reported an error trying to obtain the default process priority.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_GUARD_WORD_VER : [chars]: [chars] guard word corrupted; [IPV6 address]
Explanation	The guard word for the specified control block does not contain what isexpected.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_INV_ARG_STRING : [chars]: Invalid argument string: [chars]
Explanation	An invalid argument string was passed to the specified function.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_INV_ENV_STRING : [chars]: Invalid environment string: [chars]
Explanation	An invalid environment string was passed to the specified function.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_KILL : [chars]: Unable to kill process [chars]; [chars]
Explanation	The kill function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_KILL_RUN : [chars]: Unable to kill run process [dec] for [chars]; [chars]
Explanation	The kill function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-6-FMS_LAST_POLICY : [chars]: Cannot change a class [chars] [chars] to priority LAST. LAST is for default policies only
Explanation	Embedded Event Manager Scheduler Command can only change a default policy to priority LAST.
Recommended Action	The command is applicable to default policies only.

%HA_EM-7-FMS_MALLOC : [chars]: Unable to allocate [chars]; [chars]
Explanation	The malloc function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_MISC_ERR : [chars] ([chars])
Explanation	An unexpected error occurred.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-6-FMS_MODIFY_LAST_POLICY : [chars]: Cannot modify a LAST policy to class [chars]. LAST policies are for class default only.
Explanation	Embedded Event Manager LAST policy is for default class only.
Recommended Action	The command is applicable to default policies only.

%HA_EM-6-FMS_MODIFY_POLICY : [chars]: unable to modify the policy to class [chars]: scheduling rule unavailable.
Explanation	There is no scheduler rule configured to service this event class.
Recommended Action	Please configure a scheduler rule before modifying the event.

%HA_EM-7-FMS_NO_CLOCK : [chars]: unable to read clock using clock_gettime: [chars]
Explanation	The clock_gettime function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-4-FMS_NO_SCHED_THREAD : No threads are configured to service event class [chars]
Explanation	The Embedded Event Manager has no scheduler threads to service this event class.
Recommended Action	Track ED is not available in this image Configure threads for the event class using the ‘event manager scheduler’ command.

%HA_EM-3-FMS_NO_TRACK : keyword in the correlate statement is not supported in this image.
Explanation	The Embedded Event Manager Track ED is not supported in this image.
Recommended Action	Track ED is not available in this image

%HA_EM-7-FMS_NULL_SCRIPT_NAME : [chars]: The script name is NULL
Explanation	An invalid script name was passed as an argument into the specifiedfunction.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMS_OPEN : [chars]: Unable to open [chars]; [chars]
Explanation	The open function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_OVL_NOTIFY_REG : [chars]: ovl_notification_register failed when registering to handle OVL notifications; [chars]
Explanation	The ovl_register_notification function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_OVL_SETUP_ENV : [chars]: [chars]
Explanation	Updating environment variables of the process according to system variables stored in sysdb failed.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMS_POLICY_CHECKSUM : [chars]: Checksum error for policy [chars] — this policy will not be run
Explanation	The checksum computed for the specified policy does not match the original checksum computed when the policy was registered.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_POLICY_EXEC : [chars]: Policy execution [chars]
Explanation	The Embedded Event Manager policy excution state has been changed to thestate named in the message.
Recommended Action

%HA_EM-3-FMS_POLICY_HASH : [chars]: The hash computation routine reported an error; [chars]
Explanation	The fh_hash_md5_fd() function reported the specified error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-3-FMS_POLICY_LOOKUP_FAIL : [chars]: Failed to look up in the table the registration specification for policy [chars].
Explanation	A table lookup for the registration specification for the policy failed.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_POLICY_MAX_ENTRIES : [chars]: Class [chars]: Maximum number of [dec] [chars] publish entries exceeded; some events have been discarded
Explanation	An attempt to publish an event failed because there is no more room in the publish queue
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative

%HA_EM-6-FMS_POLICY_TIMEOUT : Policy ‘[chars]’ has hit its maximum execution time of [dec].%9.9ld seconds, and so has been halted
Explanation	The policy has exceeded its maximum execution time, and so has been halted part way through execution.If this policy is expected to take a long time to run, it may need to have ‘maxrun_sec’ added to the policy registration line (or its value increased if it is already specified).
Recommended Action	NONE

%HA_EM-3-FMS_QUEUE_INIT : [chars]: The Unable to initialize queue.
Explanation	The queue cannot be initialized.An attempt to publish an event failed because there is no more roomin the publish queue.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_REALLOC_FAIL : [chars]: Unable to reallocate [chars]; [chars]
Explanation	The realloc function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_REG_NODE_STATE_CHANGE : Failed to register for node state changes: [chars]
Explanation	The call to register for node state changes failed.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-6-FMS_RELOAD_SYSTEM : [chars]: Policy has requested a system reload;
Explanation	An Embedded Event Manager policy requested that the system be reloaded.
Recommended Action

%HA_EM-6-FMS_RUNNING_POLICY : [chars]: cannot [chars] a running policy with jobid [dec].
Explanation	Embedded Event Manager Scheduler Command cannot change a running policy.
Recommended Action	The command is not applicable to a running policy.

%HA_EM-7-FMS_SPAWN : [chars]: Unable to spawn [chars]; [chars]
Explanation	The spawn function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_STRDUP : [chars]: Failed to duplicate string [chars]; [chars]
Explanation	The strdup function reported an error.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_SWITCH_FAIL : [chars]: The system is unable to switch to standby processor. Switchover cancelled.
Explanation	Switchovers must occur when STANDBY is available and ready.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-6-FMS_SWITCH_HARDWARE : [chars]: Policy has requested a hardware switchover
Explanation	An Embedded Event Manager policy requested that a hardware switchoveroccur.
Recommended Action

%HA_EM-3-FMS_SWITCH_NOT_RF_ACTIVE : [chars]: This processor is not in ACTIVE state (state = [dec]). Switchover must be performed on ACTIVE processor.
Explanation	Switchovers must occur on ACTIVE unit, not STANDBY unit.
Recommended Action

%HA_EM-7-FMS_SYSLOG_SCAN_RESIGN : [chars]: Failed to unload Syslog FD DLL [chars]; return code=[dec]
Explanation	The syslog_scan_resign function reported an error trying to unload the specified Syslog Event Detector DLL library.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_SYSLOG_SCAN_SIGNUP : [chars]: Failed to load Syslog FD DLL [chars]; return code=[dec]
Explanation	The syslog_scan_signup function reported an error trying to load the specified Syslog Event Detector DLL library.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_SYSMGR_RELOAD_FM : [chars]: Failed to load Sysmgr FD DLL [chars]; return code=[dec]
Explanation	The sysmgr_reload_fh_detector function reported an error trying to load the specified Sysmgr Event Detector DLL library.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_THREADPOOL_MAX : Maximum number ([dec]) of callback events exceeded for [chars]; There is no available thread in the threadpool to service the event.
Explanation	An attempt to schedule an event requiring a callback failed because there is no available thread in the threadpool.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_THREAD_POOL_START : [chars]: Error reported by thread_pool_start function; [chars]
Explanation	The thread_pool_start function reported an error while attempting to start the thread pool.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_WB_CREATE : [chars]: create_watched_boolean failed; [chars]
Explanation	The create_watched_boolean function reported an error trying to createthe watched boolean.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_WDSYSMON_RELOAD_FM : [chars]: Failed to load WDSysMon FD DLL [chars]; return code=[dec]
Explanation	The wd_reload_fh_detector function reported an error trying to load the specified WDSysMon Event Detector DLL library.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_WQ_CREATE : [chars]: create_watched_queue failed; [chars]
Explanation	The create_watched_queue function reported an error trying to createthe watched queue.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_XDM_DISPATCH_FAIL : [chars]: XOS Dispatch Manager dispatch error: [dec]
Explanation	XOS Dispatch Manager reports an error when dispatching an event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_XDM_WAIT_FAIL : [chars]: XOS Dispatch Manager wait error: [dec]
Explanation	XOS Dispatch Manager reports an error when waiting for an event.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

%HA_EM-7-FMS_XOS_DM_EXECUTE : [chars]: Failed to attach a handler to process child process exit; [chars]
Explanation	The xos_dm_execute function reported an error trying to attach the handler to process child process exit.
Recommended Action	Copy the message exactly as it appears, and report it your technical support representative.

HA_PROXY

%HA_PROXY-3-PROXY_IPC_PAK_ALLOC_FAILED :
Explanation	Allocation of IPC packet failed.
Recommended Action	LOG_STD_ACTION

%HA_PROXY-2-HA_SESSION_ALLOC_FAILED : [chars]: unable to allocate entry for [chars] binding
Explanation	HA could not allocate a control block to manage the service
Recommended Action	LOG_STD_ACTION

%HA_PROXY-2-HA_FIND_SERVICE_FAILED : [chars]: unable to find [chars] service
Explanation	HA could not find the specified service
Recommended Action	LOG_STD_ACTION

%HA_PROXY-3-HA_DUP_SERVICE_NAME : [chars]: Duplicate service name: [chars] on bind
Explanation	Duplicate service name on ha service bind
Recommended Action	LOG_STD_ACTION

%HA_PROXY-3-HA_DUP_SERVICE_INDEX : [chars]: Duplicate service index: [dec] on bind
Explanation	Duplicate service index on ha service bind
Recommended Action	LOG_STD_ACTION

%HA_PROXY-3-HA_INVALID_REQUEST : [chars]: Unknown request: [dec]
Explanation	HA control services received unknown request
Recommended Action	LOG_STD_ACTION

%HA_PROXY-3-HA_MALFORMED_PKT : Malformed packet bad [chars] [hex], MSGDEF_LIMIT_MEDIUM
Explanation	HA Sync packet was malformed, may not have been fully processed
Recommended Action	LOG_STD_ACTION

%HA_PROXY-4-HA_UNKNOWN_SERVICE : Sync msg for unknown service [hex] rg [hex], MSGDEF_LIMIT_MEDIUM
Explanation	HA Sync received a message for an unknown service
Recommended Action	LOG_STD_ACTION

%HA_PROXY-4-HA_PKT_ERROR : Error processing HA sync pkt, rg [hex], MSGDEF_LIMIT_MEDIUM
Explanation	HA Sync packet was dropped while processing
Recommended Action	LOG_STD_ACTION

HDLC

%HDLC-1-ISSU_NOMEMORY : msgtxt_nomemory
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.

%HDLC-4-ISSU_SENDFAILED : HDLC ISSU: send message failed, rc = [dec]

Explanation

The sending of a message has failed.

Recommended Action

%HDLC-4-ISSU_INCOMPATIBLE : hdlc-issu-compat: returned FALSE

Explanation

The compatibility checking has failed

Recommended Action

%HDLC-4-ISSU_XFORM : [chars]: failed, rc=[chars]

Explanation

The transform has failed.

Recommended Action

HFSLIB

%HFSLIB-3-HFSOPEN : Problem accessing the udev generated file: [chars]
Explanation	No explanation.
Recommended Action	No action is required.

%HFSLIB-3-HFSINOFAILED : Inotify failed to initialize : [chars]
Explanation	This error occurs when the inotify sub-system is misbehaving
Recommended Action	No action is required.

%HFSLIB-3-HFSINOWATCH : Inotify failed to add a watch: [chars]
Explanation	This error occurs when the inotify sub-system is misbehaving
Recommended Action	No action is required.

HMAN

%HMAN-3-CONSOLE_SETUP_FAILED : Failed to setup console service. It should be enabled on [chars]
Explanation	Setup of a console service failed.
Recommended Action	Check the host manager launch parameters and correct as required.

%HMAN-3-HOSTNAME_SET_FAILED : Failed to set hostname: [chars]

Explanation

The host manager received notification that the system hostname has been set. The host manager failed to pass this value to
the ASR kernel.

Recommended Action

Repeat the process to configure the hostname. If the problem persists, copy the message exactly as it appears on the console
or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using
the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case,
or contact your Cisco technical support representative and provide the representative with the gathered information.

%HMAN-2-INITIALIZATION_FAILED : Host Manager initialization failed.

Explanation

Initialization of the host manager failed.

Recommended Action

Review Host Manager logs taking note of the timestamp information to select specific information to review. Copy the message
and other related information exactly as it appears on the console or in the system log. Research and attempt to resolve the
issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using
the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case,
or contact your Cisco technical support representative and provide the representative with the gathered information.

HMAN_CPU

%HMAN_CPU-3-PAGE_FAULT_HIGH : CPU Usage due to Memory Pressure exceeds threshold on [chars]. Below are the top 5 memory consuming processes: [chars] (PID=[dec] RSS=[dec] MB),
Explanation	When CPU usage due to Major Page Fault exceeds a pre-defined threshold for a CPU core, this error message is emitted.
Recommended Action	No action is needed if system continues to perform as expected. If sytem performance deteriorate (and eventually, system reloads due to unspecified reason) around the time when this message is observed, open a case with the Technical Assistance Center via the following Internet link, or contact your Cisco technical support representative: https://mycase.cloudapps.cisco.com/case

HPI

%HPI-3-FAILED_START : channel:[chars] DSP ID:[hex], failed mode [dec] for service [dec]

Explanation

Failed to start DSP services

Recommended Action

%HPI-3-INVALID_PAYLOAD : wrong payload size, channel:[chars] DSP ID:[hex], failed mode [dec] for service [dec]

Explanation

Failed to start DSP services

Recommended Action

%HPI-3-CODEC_NOT_LOADED : channel:[chars] DSP ID:[hex], command failed as codec not loaded [dec]

Explanation

Sending messages to DSP without a loaded codec can result with the DSP failing

Recommended Action

%HPI-4-INVALID_CODEC_LOAD : channel:[chars] DSP ID:[hex], invalid hpi mode [dec] for loading codec [dec]

Explanation

Attempt to load codec when the DSP is in an invalid mode which can result with DSP failure

Recommended Action

%HPI-4-NO_CLOSE : channel:[chars] DSP ID:[hex]

Explanation

Attempt to release DSP without sending close message

Recommended Action

%HPI-4-INVALID_ECAN_TYPE : [chars] ECAN is not available in voice-card [dec], [chars] ECAN will be used
Explanation	All voice cards participated in DSPFarm must have the same echo canceller type
Recommended Action	Make sure all voice cards participated in DSPFarm have the same echo canceller type configured

%HPI-3-GSMAMRNB_LICENSE_NOT_ACTIVATED : ********************************************************* GSM AMR-NB License is not
yet activated. Please configure ‘license feature gsmamrnb-codec-pack’ and accept the EULA to activate the license. *********************************************************

Explanation

Failed to start DSP services for GSM AMR-NB codec

Recommended Action

%HPI-6-SRTP_EVAL_LIMIT : The SRTP bandwidth and tunnels usage exceed the license limits
Explanation	The SRTP bandwidth and tunnels exceed the license limits
Recommended Action	No action is required.

%HPI-3-SRTP_EVAL_FREE_ERROR : Error encountered on release SRTP bandwidth and tunnels reservation
Explanation	Error encountered on release SRTP bandwidth and tunnels
Recommended Action	No action is required.

%HPI-3-NACK_HIGH : DSP to IOS Nack message with severity [chars] [chars] [chars]
Explanation	DSP to IOS Nack message with high severity
Recommended Action	Check the NACKed message’s parameters for configuration errors. These messages tend to affect call flow, thus they are labeled with high severity.

%HPI-4-NACK_MED : DSP to IOS Nack message with severity [chars] [chars] [chars]
Explanation	DSP to IOS Nack message with medium severity
Recommended Action	Check the NACKed message’s parameters for minor configuration errors.

%HPI-6-NACK_LOW : DSP to IOS Nack message with severity [chars] [chars] [chars]
Explanation	DSP to IOS Nack message with low severity
Recommended Action	Information only, displaying NACKed messages that are for debugging purposes.

%HPI-6-NACK : DSP to IOS Nack message [chars] [chars]
Explanation	DSP to IOS Nack message with no severity in order to work with dspware without Nack severity implementation
Recommended Action	Information only, displaying NACKed messages.

HSRP

%HSRP-3-NOSOCKET : Unable to open socket
Explanation	The system was unable to initialize an IP connection for the Hot Standby protocol.
Recommended Action	Make sure that there is at least one interface configured to run IP.

%HSRP-4-BADAUTH : Bad authentication from [chars], group [dec], remote state [chars]
Explanation	Two routers participating in HSRP disagree on the valid authentication string.
Recommended Action	Use the standby authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported.

%HSRP-4-BADAUTH2 : Bad authentication from [chars]
Explanation	Two routers participating in HSRP disagree on the valid authentication string.
Recommended Action	Use the standby authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported.

%HSRP-3-MISCONFIG : Attempt to change [chars] MAC address to [enet] when DECNET already running
Explanation	An HSRP group attempted to become active on an interface that can only support a single MAC address and which is running DECnet. If standby use-bia is not configured then HSRP would normally set the interface MAC address to the HSRP virtual MAC address, but this is not allowed if DECnet is running.
Recommended Action	Enable standby use-bia on the interface.

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

%HSRP-4-DUPADDR : Duplicate address [chars] on [chars], sourced by [enet]

Explanation

The IP address in an HSRP message received on the specified interface is the same as the IP address of the router. Another
router might be configured with the same IP address. The most likely cause is a network loop or a misconfigured switch that
is causing the router to see its own HSRP Hello messages.

Recommended Action

Check the configurations on all the HSRP routers to ensure that the interface IP addresses are unique. Check that no network
loops exist. If port channels are configured check that the switch is correctly configured for port-channels. Enable standby
use-bia so that the error message displays the interface MAC address of the sending router. This can be used to determine
if the error message is caused by a misconfigured router or a network loop.

%HSRP-4-DUPVIP1 : [chars] Grp [dec] address [chars] is already assigned to [chars] group [dec]
Explanation	The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to a different HSRP group.
Recommended Action	Check the configuration on all HSRP routers and ensure that the virtual IP address of each HSRP group is unique.

%HSRP-4-DUPVIP2 : [chars] Grp [dec] address [chars] is already assigned on this interface
Explanation	The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to this interface.
Recommended Action	Check the configuration on all HSRP routers and ensure that the virtual IP address of each HSRP group is unique.

%HSRP-4-DUPVIP3 : [chars] Grp [dec] address [chars] is already assigned to, or overlaps with, an address on another interface or application
Explanation	The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to, or overlaps with, an address on another interface or application.
Recommended Action	Check the configuration on all HSRP routers and ensure that the virtual IP address of each HSRP group is unique.

%HSRP-4-BADVIP : [chars] Grp [dec] address [chars] is in the wrong subnet for this interface
Explanation	The HSRP virtual IP address contained in the Hello message cannot be learnt as it is not within a subnet configured on the interface.
Recommended Action	Check the configuration on all HSRP routers and ensure that the virtual IP address is within a configured subnet.

%HSRP-4-DIFFVIP1 : [chars] Grp [dec] active routers virtual IP address [chars] is different to the locally configured address [chars]
Explanation	The HSRP virtual IP address contained in the Hello message from the Active router is different from the virtual IP address configured locally.
Recommended Action	Check the configuration on all HSRP routers in the group and ensure they are all configured with the same virtual IP address.

HTSP

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

%HTSP-3-CAPABILITYMISMATCH : voice port [chars]: call connection id [[hex] [hex] [hex] [hex]]
Explanation	There was a capabilities mismatch between the two call legs. capabilities are negotiated between call legs for CODEC, VAD and FAX rate.
Recommended Action	Check that the dial peer configuration is appropriate for the interface in question. Also check that and configuration on the interface is correct.

%HTSP-3-DSPALARM : voice port [chars]: status=[hex] message=[hex] text=[chars]
Explanation	The DSP reported a fatal error. All calls on the DSP were dropped and a DSP reload was attempted.
Recommended Action	Verify that the DSP reloaded properly by attempting to place a call on the affected voice port. Contact your technical support representative, include the full text of the error message.

%HTSP-3-TRUNKNOTSUPPORTED : voice port [chars]: Ground Start trunking not supported
Explanation	This voice port does not support the ‘connection trunk’ command when ground start signaling is configured. Trunking mode on this voice is supported when using loop start signaling.
Recommended Action	Shut down the voice port, remove the ‘connection trunk’ and/or ‘signal groundStart’ command from the voice port configuration, and unshut the voice port.

%HTSP-5-UPDOWN : Trunk port(channel) [[chars]] is [chars]
Explanation	Trunk port:channel changed state.
Recommended Action	No action is required.

%HTSP-3-CADENCENOTSUPPORTED : voice port [chars]: ring cadence not suitable for caller id. on_time_first=[dec] off_time_first=[dec] on_time_second=[dec] off_time_second=[dec]
Explanation	Ring off period is not sufficient for caller id transmission. If caller id transmission during ring is configured make sure that the ring off duration is long enough.
Recommended Action	If caller id transmission during ring is configured make sure that the ring off duration is long enough. Make sure that the cptone setting and caller-id alerting settings are correct.

%HTSP-5-VPM_BUSYOUT : voice port [chars]: [chars] busyout
Explanation	voice port busyout status changed
Recommended Action	use SHOW VOICE BUSYOUT to find out the reason why voice port busyout monitoring is triggered

%HTSP-5-VPM_PCM_CAPTURE : User trigger PCM capture is [chars] on voice port [chars]
Explanation	User trigger PCM capture is enabled or disable on this voice port
Recommended Action	This is just for information only

%HTSP-5-VPM_CABLE_STAT : voice port [chars]: cable [chars]
Explanation	Cable for analog voice port is reconnected or removed
Recommended Action	Check the cable connection for this analog voice port

HTTP through IDB_IDENTITY

HTTP
HTTPC
HUNTGRP
HW_API
HW_FLOWDB
HW_IDPROM_ENVMON
HW_PFU
ICC
IDBMAN
IDB_IDENTITY

HTTP

%HTTP-3-PROC_NOCREAT : Unable to create HTTP process.
Explanation	An error occurred during initialization of the HTTP process. The HTTP process that processes all HTTP requests and responses could not be created.
Recommended Action	Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

%HTTP-4-SERVER_CONN_RATE_EXCEED : Number of connections per minute has exceeded the maximum limit([dec]) as specified by the platform.
Explanation	The message indicates that the current number of connections requested per minute has exceeded the limit specified by the platform. HTTP server will resume accepting the connections 15 seconds from the time the message is issued. This restriction is done as per the HTTP throttling functionality.
Recommended Action	Reduce connection rate to the server.

%HTTP-3-OUTOF_MEM : HTTP out of memory.
Explanation	An error occurred during initialization of the HTTP process. The HTTP process could not create crucial internal data structures that are required for operation of the HTTP subsystem. The most likely reason for this condition is an exhaustion of system memory.
Recommended Action	Reduce other system activity to ease memory demands. if conditions warrant, upgrade to a larger memory configuration.

%HTTP-3-INIT_FAIL : HTTP Process Init failed.
Explanation	Initialization of the HTTP Subsystem has failed
Recommended Action	Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

%HTTP-6-SERVER_SETUP_FAILED : Server setup failed
Explanation	Setup of the HTTP(S) server to listen on the specified port number has failed.
Recommended Action	Disable the server, verify that port number is correct and enable the server. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

HTTPC

%HTTPC-3-PROC_NOCREAT : Unable to create HTTP Client process.
Explanation
Recommended Action

%HTTPC-3-OUTOF_MEM : HTTP Client out of memory.
Explanation
Recommended Action

%HTTPC-3-CACHE_MEM : HTTP Client Cache Init out of memory.
Explanation
Recommended Action

%HTTPC-3-INIT_FAIL : HTTP Client Process Init failed.
Explanation
Recommended Action

%HTTPC-3-OUTOF_SYNC : HTTP Client header tables out of sync.
Explanation
Recommended Action

%HTTPC-6-CONNECT_FAILED : The connection to server [IP_address] failed
Explanation
Recommended Action

%HTTPC-3-RECEIVE_SOCK_READ_EVENT_WHILE_DISABLED : Received socket read event while read interest is disabled callID([dec]) fd([dec]) — closing socket.
Explanation	The HTTP Client is receiving the socket READ event while the READ interest is being disabled. Something has gone wrong between the http client and the socket interfaced.
Recommended Action	Record the error and report it to the system administrator.

%HTTPC-3-CONNECT_NULL : NULL connection structure for fd([dec]) — closing socket.
Explanation	The HTTP Client is receiving the socket READ event but it fails to locate the connection structure for this file descriptor(fd). If this is seen continuously in a loop, it is an indication that something has gone wrong in the socket code. Since the socket is immediately closed after this event, the HTTP client should stop seeing READ event.
Recommended Action	Record the error and traceback and report it to the system administrator.

%HTTPC-6-REQUEST_FAILED : request URI [chars] failed
Explanation
Recommended Action

%HTTPC-6-CLOSE_SRV_CONNECT : The connection to server [IP_address] appears to be hung and will be closed.
Explanation	Messages are being backed up in the HTTP Client’s write queue in the connection with the specified server. The connection is assumed to have gone bad and the HTTP Client is closing the connection.
Recommended Action	Check with the specified server for possible connection error.

%HTTPC-3-COOKIE_MEM : HTTP Client runs out of allowable memory to store cookies.
Explanation	The total memory allocated for storing cookies has run out. All cookies received from the HTTP server will be dropped. Users may no longer be able to interact with a session-based origin server until memory is freed up.
Recommended Action	Users may want to try their requests at a later time or contact the system administrator to increase the maximum RAM allowed for saving HTTP cookies.

HUNTGRP

%HUNTGRP-3-INVALID_URL : Could not open the file provided in URL: <[chars]>
Explanation	URL path provided can’t be accessed. This usually indicates that path provided is invalid but may also be because the the path doesn’t allow anonymous access to create files or open it in write mode
Recommended Action	Check that the url path provided is valid

%HUNTGRP-3-WRITE_FAIL : Could not write data to the URL: <[chars]>t %%bytes written=[dec] out of [dec]
Explanation	Write attempt to the url path provided was unsuccessful. This usually indicates that the file was successfully opened with write and append permissions but writing all the content from buffer or may be some of it to the file failed.
Recommended Action

HW_API

%HW_API-3-RESILIENCE_NO_HANDLER : No handlers in place for [chars] sw object creation failure.

Explanation

COMMON_HW_API_INTERNAL_ERROR

Recommended Action

%HW_API-3-INVALID_OBJ : Invalid object [hex]

Explanation

HW_API_INTERNAL_ERROR

Recommended Action

%HW_API-3-INVALID_TYPE : Invalid type [dec]

Explanation

HW_API_INTERNAL_ERROR

Recommended Action

%HW_API-3-INVALID_WALK_SPEC : Invalid walk spec [hex]

Explanation

HW_API_INTERNAL_ERROR

Recommended Action

%HW_API-3-WALK_MODE_UNSUPPORTED : Walk mode ‘[chars]’ unsupported

Explanation

HW_API_INTERNAL_ERROR

Recommended Action

%HW_API-3-INVALID_CONTEXT : Invalid context [hex]

Explanation

HW_API_INTERNAL_ERROR

Recommended Action

%HW_API-3-BACKWALK_REQUEST : Backwalk request failed, [chars]

Explanation

A request to walk internal data structures has failed. Depending on criticality of the data, accuracy of forwarding may impacted.

Recommended Action

%HW_API-3-BACKWALK_REQUEST_VALUE : Backwalk request failed, [chars] ([hex])

Explanation

A request to walk internal data structures has failed. Depending on criticality of the data, accuracy of forwarding may impacted.

Recommended Action

%HW_API-3-VECTOR : Failed to set [chars] vector for [chars], [chars]

Explanation

HW_API_INTERNAL_ERROR

Recommended Action

%HW_API-3-NO_OBJ_TYPE_LIST_ENTRY : Invalid sw_obj_type ([dec]) used with obj_type_list

Explanation

HW_API_INTERNAL_ERROR

Recommended Action

%HW_API-3-NO_OBJ_TYPE_LIST_ENTRY2 : Invalid sw_obj_link_type ([dec]) used with obj_type_list

Explanation

HW_API_INTERNAL_ERROR

Recommended Action

%HW_API-3-INIT_FAIL : HW-API init [chars] failed[chars]

Explanation

HW_API_INTERNAL_ERROR

Recommended Action

HW_FLOWDB

%HW_FLOWDB-3-HW_FLOWDB_OOM : FlowDB memory usage exceeded 95[int]sage. OOM condition can occur.
Explanation	FlowDB running low on memory. Out-of-memory condition can occur
Recommended Action	Check sw-distrib for actual utilization of FlowDB memory

HW_IDPROM_ENVMON

%HW_IDPROM_ENVMON-3-HW_IDPROM_FIELD_INVALID : The idprom contains an invalid environmental monitoring field.

Explanation

If this error occurs then parsing of the environmental monitoring data is aborted. Environmental monitoring will be either
incomplete or absent entirely.

Recommended Action

If this message recurs, 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.

%HW_IDPROM_ENVMON-3-HW_IDPROM_CHECKSUM_INVALID : The idprom contains an invalid checksum in a sensor entry. Expected: [hex],
calculated: [hex]

Explanation

If this error occurs then parsing of the environmental monitoring data is aborted. Environmental monitoring will be either
incomplete or absent entirely.

Recommended Action

%HW_IDPROM_ENVMON-2-ACT2_UDI_DATA_INVALID : The act2 udi secure area format mismatch with unsecure area

Explanation

This Router may not have been manufactured by Cisco or with Cisco’s authorization. This product may contain software that
was copied in violation of Cisco’s license terms. If your use of this product is the cause of a support issue, Cisco may deny
operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet. Please
contact Cisco’s Technical Assistance Center for more information.

Recommended Action

%HW_IDPROM_ENVMON-3-PS_IDPROM_INVALID_PID : [chars] in slot PFU[dec] has INVALID PID [chars] and it needs to be replaced immediately

Explanation

The PID read from the PEM IDPROM is not supported in this hardware configuration. It will be allowed to continue but immediate
replacement is required

Recommended Action

HW_PFU

%HW_PFU-3-PFU_IDPROM_READ_ERR : Could not read the PEM/FM idprom in slot P[dec].The system will run without environmental
monitoring for this component

Explanation

The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom
could not be read, therefore no monitoring will take place.

Recommended Action

%HW_PFU-3-PFU_IDPROM_CORRUPT : The PEM/FM idprom could be read, but is corrupt in slot P[dec] The system will run without
environmental monitoring for this component

Explanation

The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom
could not be read, therefore no monitoring will take place.

Recommended Action

%HW_PFU-3-PFU_IDPROM_INVALID_PID : The PEM/FM idprom has invalid PID in slot PFU[dec] The system will run without environmental
monitoring for this component

Explanation

The idprom contains PID information required in order to properly operate the environmental monitoring subsystems. The idprom
PID is invalid , therefore no monitoring will take place.

Recommended Action

ICC

%ICC-2-NOMEM : No memory available for [chars]

Explanation

The ICC subsystem could not obtain the memory it needed.

Recommended Action

%ICC-4-CONSISTENCY : Internal consistency check: [chars]

Explanation

An internal inconsistency was found in some ICC data structures.

Recommended Action

%ICC-4-COMM : Communication failure occurred while [chars]
Explanation
Recommended Action

%ICC-4-BAD_ACCOUNTING : ICC received a bad class [dec]

Explanation

A communication failure has occurred between this card and another card in the system.

Recommended Action

%ICC-4-HEARTBEAT : Card [dec] failed to respond to heartbeat

Explanation

A communication failure has occurred between the primary and the specified line card.

Recommended Action

%ICC-5-WATERMARK : [dec] [chars] [chars] pkts for class [chars] are waiting to be processed

Explanation

Processor got packets for the class and are waiting to be procssed

Recommended Action

%ICC-2-OPEN : ICC Create Session Failed for card <[hex]> Queue <[chars]>
Explanation	ICC was not able to create a session for the destination seat
Recommended Action	collect output from ‘show oir debug swover_global_mask’ from SP

%ICC-2-JOIN : ICC mcast joining failed member <[hex]> to group <[hex]> with ipc error <[chars]>
Explanation	ICC was not able to join a member for the mcast group
Recommended Action	collect output ‘show icc mcast status’ from RP

%ICC-5-HUGE_BUFFER : Class [[chars]] with Request id [dec] requested a huge buffer of Size [dec].
Explanation	Huge packet requests would deplete the memory at the linecards
Recommended Action	ICC client is trying to request huge packet buffer Please use the command Show icc internal to get get the traceback and file a DDTS against the component

%ICC-3-MAST_BAD_FREE : ICC multicast memory already freed

Explanation

One of the ICC multicast request’s memory was found to be free when response arrived

Recommended Action

IDBMAN

%IDBMAN-3-VLANINUSE : [chars]: Vlan [dec] is in use by [chars]
Explanation	Each L3 interface has a Vlan associated with it. This message indicates that the Vlan associated with the interface is being used by some other L3 Interface, which is not anticipated to happen
Recommended Action	No action is required.

%IDBMAN-3-INVALIDVLAN : [chars]: trying to use invalid Vlan [dec]

Explanation

There is an internal error that caused an invalid Vlan to be used by the software.

Recommended Action

%IDBMAN-3-VLANNOTSET : [chars]: Vlan [dec] not set since it already has Vlan [dec]

Explanation

There is an internal error that caused an interface to not have its Vlan set to the requested value

Recommended Action

%IDBMAN-6-VLANMAPPED : Vlan [dec] is mapped to [chars]
Explanation	Informational message indicating that the given Vlan is mapped to the given interface
Recommended Action	No action is required.

%IDBMAN-3-AGGPORTMISMATCH : [chars]([dec] / [dec]) does match internal slot/port state [chars]([dec] / [dec])

Explanation

There is an internal error that caused an invalid aggregate port to be used by the software.

Recommended Action

%IDBMAN-3-INVALIDAGGPORTBANDWIDTH : [chars]([dec] / [dec]) has an invalid bandwidth value of [dec]

Explanation

There is an internal error that caused an invalid bandwidth to be used for an aggregate port.

Recommended Action

%IDBMAN-3-DELETEDAGGPORT : [chars]([dec] / [dec]) Group [dec] has been deleted, but is being reused.

Explanation

There is an internal error that caused an interface that has been deleted to be reused for a new aggregate port.

Recommended Action

%IDBMAN-3-NOTANAGGPORT : [chars]( [dec] / [dec] ) is not an aggregate port

Explanation

There is an internal error that caused an interface that is not an aggregate port to be used for aggregate port operations

Recommended Action

%IDBMAN-3-INVALIDPORT : [chars]: trying to use invalid port number [dec] ( Max [dec] )

Explanation

There is an internal error that caused an invalid port numer to be used by the software.

Recommended Action

%IDBMAN-4-ACTIVEPORTSINAGGPORT : [chars]( [dec] / [dec] ) has [dec] active ports, but is being removed

Explanation

There is an internal error that caused an aggregate port with active ports to be removed

Recommended Action

%IDBMAN-3-PORTNOTINAGGPORT : [chars]([dec] / [dec]) is not present in Aggport [chars]([dec] / [dec])

Explanation

There is an internal error that caused an invalid port to be referred to be part of an aggregate port.

Recommended Action

%IDBMAN-4-REMOVED_NONDEFAULT_CONFIG : Removed non default configuration for interfaces in slot [dec]
Explanation	In SSO mode, the non-default configuration for any removed linecard is not synced to the standby during the bulk sync, and it is removed from the configuration to avoid a config mismatch between active and standby supervisors.
Recommended Action	No action is required.

%IDBMAN-3-IIF_ID_REGISTRATION_FAILED : IIF_ID registration failed for Port [chars] due to memory allocation failure. Port has been shutdown
Explanation	The system is low on memory due to which IIF-ID registration failed. This results in failure to apply polices such as QoS and Security acls on this port.
Recommended Action	LOG_STD_REDUCE_ACTION Once memory is available, run ‘no shutdown’ on the port.

IDB_IDENTITY

%IDB_IDENTITY-3-MALLOC : Memory allocation failure for HWIDB type [dec]

Explanation

A memory allocation failure occured when trying to allocate the identity for this HWIDB. This HWIDB will not be allocated
an IF Index which will prevent it from being used for forwarding data.

Recommended Action

IDB_SGI through ILPOWER

IDB_SGI
IDMGR
IEDGE
IF
IFDAMP
IFMAP
IFMGR
IFS
IKEV2
ILPOWER

IDB_SGI

%IDB_SGI-2-XDRREG : [chars]

Explanation

An internal software error occurred.

Recommended Action

%IDB_SGI-2-MEMREQ : [chars]

Explanation

An internal software error occurred.

Recommended Action

%IDB_SGI-3-BADPTR : [chars] of interface with ifindex [int] is invalid

Explanation

An internal software error occurred.

Recommended Action

%IDB_SGI-3-MEMFAIL : [chars]

Explanation

An internal software error occurred.

Recommended Action

%IDB_SGI-4-MEMBERREQ : member request failure for interface with ifindex [int] returned err — [chars]

Explanation

An internal software error occurred.

Recommended Action

%IDB_SGI-3-XDRREQ : [chars]

Explanation

An internal software error occurred.

Recommended Action

%IDB_SGI-4-INTERR : [chars] for interface with ifindex [int]

Explanation

An internal software error occurred.

Recommended Action

%IDB_SGI-4-UNEXPINP : [chars]

Explanation

An internal software error occurred.

Recommended Action

IDMGR

%IDMGR-3-MALLOC_FAILURE : [chars]

Explanation

A malloc failure occured in ID Manager.

Recommended Action

%IDMGR-3-INTERRUPT : [chars]

Explanation

An id_get attempted at interrupt level.

Recommended Action

%IDMGR-3-INVALID_ID : bad id in [chars] (id: [hex])

Explanation

An ID Manager error occurred.

Recommended Action

%IDMGR-3-INVALID_ID_TABLE_SIZE : bad new ID table size

Explanation

A bad new table request to ID Manager occurred.

Recommended Action

%IDMGR-3-ID_MANAGER_INTERNAL_ERROR : [chars]

Explanation

Internal Error occured with ID Manager.

Recommended Action

IEDGE

%IEDGE-4-PBHK_DEPLETED_INDICES : No more portbundles can be allocated
Explanation	The source interfaces configured for Portbundle Hostkey feature are not sufficient and the number of portbundles available are all used up. Add more source interfaces in the configuration.
Recommended Action	Check configuration on the ISG

%IEDGE-4-TC_UNDEFINED_ACL : Traffic class ACL [chars] is not defined, creating permit all ACL
Explanation	The ACL specified for classification of traffic is not configured on the ISG. Creating a permit all ACL. ACL should be configured on the ISG.
Recommended Action	Configure the ACL on the ISG

%IEDGE-4-CLOCK_CHANGE_TIMER_INV : A Local clock change has caused a running timer to be invalid
Explanation	A change in local clock has made a currently running timer to be invalid
Recommended Action	Check the clock configuration

%IEDGE-3-CH_INTERNAL_ERROR : Internal error in command processing — session handle=[hex]
Explanation	There has been an internal error relating to CoA command processing.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IEDGE-3-CH_REGISTER_ERROR : CoA registration error in command processing — type ‘[chars]’
Explanation	There has been an internal error relating to CoA command processing.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

IF

%IF-3-IDB_LIST_BAD_REF_COUNT : A bad reference count was encountered in an idb list element.
Explanation	A software error occurred.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IF-2-IDB_TABLE_INIT : Malloc failed while initializing idb table
Explanation
Recommended Action

%IF-3-BAD_MTU : Internal error. MTU on [chars] too large or negative. Truncating from %ld to [int].
Explanation	An internal software error occurred. The system attempted to set the MTU on an interface to an invalid value.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IF-3-BADLOCK : Invalid lock use for [chars]: [chars][chars]

Explanation

Application layer code attempted to access an unlocked interface.

Recommended Action

%IF-3-BADHWUNLOCK : ([chars]) attempted to unlock [chars] ([dec]). Locked by [chars] ([dec]).

Explanation

Attempt to release semaphore held by another process.

Recommended Action

%IF-3-SEMAHOG : ([chars]) could not get [chars] semaphore. Held by ([chars]).

Explanation

Unable to obtain interface semaphore.

Recommended Action

%IF-4-BACKWARD_COUNTERS : Corrected for backward [chars] counters ([int] -> [int]) on [chars]

Explanation

The interface specified in the message has a packet counter that has decreased in number. This condition can occur if a packet
is counted and then dropped. This event was detected and corrected.

Recommended Action

If this condition persists, 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.

%IF-3-BADMACADDRTYPE : illegal mac address type, [dec]

Explanation

This is an interal error that was recovered gracefully.

Recommended Action

%IF-4-NOBGPROCESS : Network background process not running. [chars]
Explanation	A process which manages network interface background processing is not yet running, but another system process has tried to send the process a message.
Recommended Action	An interface on the router may have missed a request to bring itself up. If that happens, it may be necessary to reset the interface using a `shutdown` operation and then a `no shutdown`.

IFDAMP

%IFDAMP-5-UPDOWN : interface [chars] update [chars] state to [chars], interface is [chars]suppressed
Explanation	dampening interface changed state.
Recommended Action	No action is required.

%IFDAMP-5-ZERODELAY : dampening reuse timer is updated with 0 delay time
Explanation	Inconsistency of dampening reuse timer wheel
Recommended Action	No action is required.

IFMAP

%IFMAP-3-CAUSE_CFG : hash table not initialized

Explanation

PAL interface handle to uidb hash table not initialized

Recommended Action

IFMGR

%IFMGR-3-IFINDEX_PERSIST_ENTRY_CORRUPT : [chars] seems to be corrupted. Trying to read [dec] size
Explanation	The ifIndex-table seems to be corrupted.
Recommended Action	Delete the ifindex-table.

%IFMGR-3-INVALID_PERSISTENT_DATA : Invalid persistent data
Explanation	Trying to write invalid persistent data
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IFMGR-3-NOVECTOR : Interface manager failed to allocate IF vector. size [dec]
Explanation	The interface vector was not able to be allocated with the number of elements required—initially or resize (see size in the error message).
Recommended Action	TBD

%IFMGR-3-VECTOREXD : IF manager attempted to use interface [dec] outside vector range.
Explanation	This message indicates that an interface with too large of an ifIndex value was attempted to be added to the IF-MGR DB.
Recommended Action	Additional IF-MGR warning and/or error messages should accompany indication of this error. These additional messages should provide more details on the effected interface.

%IFMGR-3-VECTORPOSUSED : IF manager attempted to add interface [dec] which was already added.
Explanation	This message comes from the IF-MGR DB when it is trying to add an ifIndex value for this interface which already exists in the ifIndex DB.
Recommended Action	TBD

%IFMGR-4-VECTORIFSUSPECT : IF manager added interface [dec] which is unexpectedly large.
Explanation	The ifIndex allocation scheme gives out sequential ifIndex values. This message comes from the IF-MGR DB when it is trying to add an ifIndex value much larger than the former greatest ifIndex value in the DB.
Recommended Action	TBD

%IFMGR-3-IFDB : IF manager interface database [chars] failure- [dec]
Explanation
Recommended Action	TBD

%IFMGR-3-IFTDB : IF manager interface table database [chars] failure- [dec]
Explanation
Recommended Action	TBD

%IFMGR-3-NOTYPEVECTOR : Interface manager failed to allocate IF type vector. size [dec]
Explanation	The interface type vector was not able to be allocated with the number of elements required—initially or resize.
Recommended Action	TBD

%IFMGR-3-NOIMACP : IF manager control process failed to start
Explanation
Recommended Action	TBD

%IFMGR-4-NOIFINDEX : All SNMP if indices are exhausted
Explanation	All SNMP MIB indices have been exhausted. Interfaces will not be able to obtain an interface index that they can use to register with the interface MIB.
Recommended Action	Attempt a system reload. If the problem persists after the system reload, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.

%IFMGR-3-BADIFINDEXTABLE : The file nvram:ifIndex-table is corrupt.
Explanation	The file is not in the expected format.
Recommended Action	If possible, please delete the file.

%IFMGR-4-NOSYNC : ifIndex not being synced between active and standby
Explanation	When the standby comes up, then the tuple of ifIndex and ifDescr is synced so that when interfaces comes up they get the same ifIndex. This error happens when the interface doesn’t get the ifIndex for the given ifDescr
Recommended Action	Inform the technical support to raise the ddts

%IFMGR-5-RESTART : [chars]
Explanation	The IF MGR process has restarted
Recommended Action	This is an informational message. The system should recover on its own.

%IFMGR-4-STACK_RELATIONSHIP_ADD_ERROR : [chars]: Request for creating invalid stack relationship [dec], [dec]
Explanation	The IF MGR received the call to add invalid stack relationship. The higher and lower ifIndex are shown in the message. The module of the IF MGR from where this message is generated is also shown in the message
Recommended Action	Inform the technical support to raise the ddts

%IFMGR-3-DUP_IFINDEX : Duplicate ifIndex ([dec]) found for ifDescr [chars]; exists in ifTable for ifDescr [chars].
Explanation	Interfaces have same ifIndex in IF-MGR assigned list. The 2nd interface registered with IF-MGR will be assigned with new index
Recommended Action	1. No Action, if ifIndex persist is not required. 2. Reload the standby RP, if ERR msg only seen in standby RP 3. Reload the router with the proper ifindex-table and image

%IFMGR-7-NO_IFINDEX_FILE : Unable to open [chars] [chars]
Explanation	This is a informational message. This means system found no saved ifIndex information, and ifIndex is not persisted across reboots. The ifIndices will be reassigned.
Recommended Action	1. No Action, if ‘snmp-server ifIndex persist’ is not configured. 2. If ‘snmp-server ifindex persist’ is configured then copy the error message exactly as it appears, and report it to your technical support representative.

IFS

%IFS-4-FILEMAX : Failed to open [chars], maximum open files [dec])
Explanation	The router has reached the maximum number of files that may be open at one time.
Recommended Action	Close some files and try again. If this messages recurs, contact your technical support representative.

%IFS-3-FSMAX : Failed to add [chars], maximum filesystems [dec]
Explanation	The router has reached the maximum number of file systems that can be supported at one time.
Recommended Action	Contact your technical support representative.

%IFS-3-FSDUP : Failed to add [chars], filesystem prefix exists
Explanation	A file system cound not be added because another file system exists with the same name.
Recommended Action	Contact your technical support representative.

%IFS-3-FS_CREATE_FAIL : Failed to create [chars] file system, [chars]
Explanation	An internal software error occurred.
Recommended Action	Call your technical support representative for assistance.

%IFS-3-FS_CREATE_FAIL2 : Failed to create [chars] simple file system, [chars]
Explanation	An internal software error occurred.
Recommended Action	Call your technical support representative for assistance.

%IFS-3-FS_MISSING_FUNCTIONS : ‘[chars]’ file system missing required functions, not created
Explanation	Some file systems require a certain set of function to be present in order to be usable. This file sustem does not support all the mandatory functionality.
Recommended Action	Call your technical support representative for assistance.

%IFS-3-FS_STRUCT_ERROR : Data does not match expected internal representation
Explanation	A mismatch exists between the representation of data extracted from the filesystem and the expectation of its formatting. This may occur when running in a dual-RP environment, with different IOS versions running on the two RPs.
Recommended Action	Ensure both RPs are running the IOS same version, if running in a dual-RP environment. If not, call your technical support representative for assistance.

IKEV2

%IKEV2-5-OSAL_INITIATE_TUNNEL : NULL
Explanation
Recommended Action

%IKEV2-5-RECV_CONNECTION_REQUEST : NULL
Explanation
Recommended Action

%IKEV2-3-NEG_ABORT : NULL
Explanation
Recommended Action

%IKEV2-1-SEND_COOKIE_CHALLENGE : NULL
Explanation
Recommended Action

%IKEV2-5-IPSEC_COLLISION : NULL
Explanation
Recommended Action

%IKEV2-5-SA_UP : NULL
Explanation
Recommended Action

%IKEV2-5-SA_DOWN : NULL
Explanation
Recommended Action

%IKEV2-5-SA_REJECTED_RESOURCE_LOW : NULL
Explanation
Recommended Action

%IKEV2-5-SA_REJECTED_LIMIT_REACHED : [chars]
Explanation
Recommended Action

%IKEV2-5-INCREASE_PEER_WINDOW_SIZE : NULL
Explanation
Recommended Action

ILPOWER

%ILPOWER-3-ILPOWER_INTERNAL_IF_ERROR : Inline Power internal error, interface [chars]: [chars]

Explanation

A software check failed during Power over Ethernet (PoE) processing.

Recommended Action

%ILPOWER-5-ILPOWER_POWER_DENY : Interface [chars]: inline power denied. Reason: [chars]
Explanation	There is not enough power remaining in the switch to supply to the Power over Ethernet (PoE) port.
Recommended Action	No action is required.

%ILPOWER-5-ILPOWER_POWER_CDP_SHUT : Interface [chars]: inline power shut
Explanation	Inline power is shut because cdp consumption power on this Power over Ethernet (PoE) port is greater than 1. allocation power or 2. hardware interface limit or 3. user configured max power or 4. available power on this switch.
Recommended Action	No action is required.

%ILPOWER-3-CONTROLLER_ERR : Controller error, Controller number [dec]: [chars]

Explanation

An error reported or caused by the Power over Ethernet (PoE) controller is detected.

Recommended Action

%ILPOWER-3-CONTROLLER_POST_ERR : Inline Power Feature is disabled on this switch because Power On Self Test (POST) failed
on this switch. Please consult TECH support for further assistance

Explanation

An error reported or caused by the Power over Ethernet (PoE) controller is detected during POST.

Recommended Action

%ILPOWER-3-CONTROLLER_IF_ERR : Controller interface error, [chars]: [chars]

Explanation

An interface error is detected between the Power over Ethernet (PoE) controller and system.

Recommended Action

%ILPOWER-3-CONTROLLER_PORT_ERR : Controller port error, Interface [chars]: [chars]

Explanation

A port error reported by the Power over Ethernet (PoE) controller is detected.

Recommended Action

%ILPOWER-5-POWER_GRANTED : Interface [chars]: Power granted
Explanation	There is enough power available in the switch, and the switch is providing power on the interface.
Recommended Action	No action is required.

%ILPOWER-5-LINKDOWN_DISCONNECT : Interface [chars]: Link down disconnect
Explanation	The powered device is no longer connected to the switch, or the connected powered device is being powered by an external AC power source. The switch is no longer providing power on the interface.
Recommended Action	No action is required.

%ILPOWER-5-IEEE_DISCONNECT : Interface [chars]: PD removed
Explanation	The powered device is no longer connected to the switch, or the connected powered device is being powered by an external AC power source. The switch is no longer providing power on the interface.
Recommended Action	No action is required.

%ILPOWER-7-DETECT : Interface [chars]: Power Device detected: [chars]
Explanation	The switch has detected the attached power device.
Recommended Action	No action is required.

%ILPOWER-5-INVALID_IEEE_CLASS : Interface [chars]: has detected invalid IEEE class: [dec] device. Power denied
Explanation	The power device has invalid IEEE class. switch won’t powerup the device
Recommended Action	No action is required.

%ILPOWER-3-SHUT_OVERDRAWN : Interface [chars] is shutdown as it is consuming more than the maximum configured power ([dec]) milliwatts.
Explanation	Interface is shutdown because it is consuming more than the maximum configured power
Recommended Action	Make sure correct power is budgeted for this interface based on the power device electrical specifications or ratings. It is recommended to change the police cutoff power to a higher value to keep the device powered on

%ILPOWER-4-LOG_OVERDRAWN : Interface [chars] is overdrawing power. it is consuming [dec] milliwatts where as maximum configured power is ([dec]) milliwatts.
Explanation
Recommended Action	Make sure correct power is budgeted for this interface based on the power device electrical specifications or ratings. Otherwise you might risk overloading the switch. It is recommended to change the police cutoffpower appropriately if needed

%ILPOWER-5-CLR_OVERDRAWN : Interface [chars] is NOT overdrawing power. it is consuming [dec] milliwatts where as maximum configured value is ([dec]) milliwatts.
Explanation
Recommended Action	No action is required.

%ILPOWER-5-POLICE_POWER_INVALID : Interface [chars]: invalid power police [dec] milliwatts current [dec] mA voltage [dec]
mV

Explanation

power policing current or voltage value is invalid.

Recommended Action

%ILPOWER-5-SENSE_POWER_INVALID : Interface [chars]: invalid power sense [dec] milliwatts current [dec] mA voltage [dec] mV

Explanation

power sensing current or voltage value is invalid.

Recommended Action

%ILPOWER-4-ILPOWER_POWER_SUPPLY : PoE Power Supply [chars]: [chars]
Explanation	The power supply for PoE is OIR
Recommended Action	Make sure power supply to PoE input is inserted after removal

%ILPOWER-4-ILPOWER_PS_ABSENCE : PoE module Power Supply not present Inline Power Feature is disabled on [chars] because Power On Self Test (POST) failed : [chars]
Explanation	The power supply for PoE expansion module is not present or not inserted properly or faulty
Recommended Action	Make sure power supply to expansion module is inserted properly and reload the switch with PoE power supply present

%ILPOWER-5-PWRGOOD_SPARE_PAIR : Interface [chars]: spare pair power good
Explanation	Spare pair power request was successful and power is available on spare pair
Recommended Action	No action is required.

%ILPOWER-5-TSTART_SPARE_PAIR : Interface [chars]: spare pair power error: TSTART
Explanation	spare pair tstart error has occurred, power on spare pair will not be supplied
Recommended Action	No action is required.

%ILPOWER-5-PGOOD_TIMEOUT_SPARE_PAIR : Interface [chars]: spare pair power good timeout error
Explanation	spare pair power good timeout error has occurred, power on spare pair will not be supplied
Recommended Action	No action is required.

%ILPOWER-5-DET_SHORT_SPARE_PAIR : Interface [chars]: spare pair short detected
Explanation	spare pair short detect error has occurred, power on spare pair will not be supplied
Recommended Action	No action is required.

%ILPOWER-5-DET_TIMEOUT_SPARE_PAIR : Interface [chars]: spare pair detect timeout
Explanation	spare pair timeout detect error has occurred, power on spare pair will not be supplied
Recommended Action	No action is required.

%ILPOWER-6-SET_ILPOWER : Set power allocated to POE to [dec] for slot [dec]
Explanation	The power allocated to POE has changed
Recommended Action	No action is required.

%ILPOWER-5-SINGLE_PAIRSET_FAULT : Interface [chars]: shutting down [chars] pairset due to fault
Explanation	The dual signature PD on this port has hit a critcal fault on one pairset and hence that pairset will be shutdown
Recommended Action	No action is required.

%ILPOWER-5-LLDP_SHUTDOWN : Interface [chars]: PD requested shutdown for [dec] sec via LLDP MDI TLV
Explanation	Inline power is removed because PD requested shutdown via LLDP MDI TLV
Recommended Action	No action is required.

IM through IOSD_INFRA

IM
IMGR
INDXOBJ
INFRA
INSTALL
INTERCHASSIS_REDUNDANCY
INTERFACE_API
IOMD_INFRA
IOSD
IOSD_INFRA

IM

%IM-0-UIPEER_CREATE : Failed to create user interface peer.
Explanation	The system failed to create a user interface peer.
Recommended Action	In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot \| subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

%IM-2-INSTALL_FAILURE : Virtualization Service[chars]
Explanation	The installation of the virtualization service failed.
Recommended Action	Enable the IOx-manager trace logs and repeat the installation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.

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

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

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

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

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

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

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

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

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

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

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

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

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

%IM-2-HA_SYNC_ERR : [chars] ‘[chars]’ [chars]
Explanation	The ha-sync persistent storage disk for the virtualization service cannot be watched for sync to standby RP.
Recommended Action	Collect the IOx-manager logs and scan them for the cause.

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

%IM-2-RESET_FORCE : Virtualization Services non-recoverable reset command processed

Explanation

A ‘virtualization service reset force’ command has been entered and processed. This action initiates a cleanup of last resort.
Occasionally a VM will get into an unrecoverable state that prevents it from activating but also from uninstalling. This is
a rare event but when it happens the only resort may be to remove the .conf control file and reboot, which forces a cleanup
of all previously installed VM files and artifacts. Note that once this command is used, current VMs are considered to be
in an unstable or unpredictable state, and all future install, uninstall, upgrade, and activation commands will be blocked.

Recommended Action

Once the command is entered and accepted, there is no recourse but to restart the system.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

%IM-6-IOX_RECONCILE_INFO : App-hosting application reconcile process [chars]
Explanation	Indicates stage of reconcile (application recovery) process.
Recommended Action	No action is required

%IM-6-IOX_START_INFO : [chars] cannot be started because it is not installed
Explanation	Indicates starting an app before installation.
Recommended Action	No action is required

%IM-6-IOX_START_SUCCESS : [chars] is in RUNNING state
Explanation	Indicates starting an app after installation.
Recommended Action	No action is required

%IM-6-IOX_START_FAIL : [chars] failed to start
Explanation	Indicates starting an app after installation.
Recommended Action	No action is required

%IM-6-START_MSG : app-hosting: [chars]
Explanation	Message for starting an app.
Recommended Action	In the failed case, check Ioxman’s trace log for the cause of the failure. In the successful case, this notification can be ignored.

%IM-6-INSTALL_MSG : app-hosting: [chars]
Explanation	Message for installing an app.
Recommended Action	In the failed case, check Ioxman’s trace log for the cause of the failure. In the successful case, this notification can be ignored.

%IM-6-ACTIVATE_MSG : app-hosting: [chars]
Explanation	Message for activating an app.
Recommended Action	In the failed case, check Ioxman’s trace log for the cause of the failure. In the successful case, this notification can be ignored.

%IM-6-DEACTIVATE_MSG : app-hosting: [chars]
Explanation	Message for deactivating an app.
Recommended Action	In the failed case, check Ioxman’s trace log for the cause of the failure. In the successful case, this notification can be ignored.

%IM-2-IOX_ENABLEMENT : IOX is ready.
Explanation	Message for IOX enablement.
Recommended Action	No action is required

%IM-6-UPGRADE_MSG : app-hosting: [chars]
Explanation	Message for upgrading an app.
Recommended Action	In the failed case, check Ioxman’s trace log for the cause of the failure. In the successful case, this notification can be ignored.

%IM-6-VERIFICATION_MSG : app-hosting: [chars]
Explanation	Message for signature verification
Recommended Action	In the failed case, check Ioxman’s trace log for the cause of the failure. In the successful case, this notification can be ignored.

IMGR

%IMGR-0-FIPS_FMFP_BYPASS_TEST : NIST bypass test failed for [chars].
Explanation	Forwarding Manager IPsec component detected a discrepancy when adding or deleting a security sensitive object. This could be due to a hardware or software resouce limitation or a software defect.
Recommended Action	Check the logs for information on the relevant object download states. Remove the object or a parent object in question. If the problem persists reboot the forwarding processor (ESP).

%IMGR-6-FIPS_FMFP_CRNG_TEST : continuous [chars]approved RNG test failed.
Explanation	Forwarding Manager IPsec component detected two identical random number sequences. This could be due to a hardware mulfunction or a software defect.
Recommended Action	If the problem persists reboot the forwarding processor (ESP).

%IMGR-6-FIPS_FMFP_OLAP_TEST : FIPS-approved RNG key seed and state overlap.
Explanation	Forwarding Manager IPsec component detected an overlap in FIPS-approved RNG key seed and state. This could be due to a hardware mulfunction or a software defect.
Recommended Action	If the problem persists reboot the forwarding processor (ESP).

%IMGR-6-FIPS_FMFP_KAT_TEST : power up cryptographic self-test didnot run to completion: [chars].
Explanation	Forwarding Manager power up known answer self-test (KAT) failed. This could be due to a hardware malfunction or a software defect.
Recommended Action	If using ipsec, reboot the forwarding processor (ESP).

%IMGR-0-FIPS_CPP_CLIENT_BYPASS_TEST : CPP Client FIPS bypass test failed for [chars].
Explanation	Forwarding Manager CPP client IPSEC bypass test failed. This could be due to a hardware malfunction or a software defect.
Recommended Action	If the problem persists reboot the forwarding processor (ESP).

%IMGR-6-FIPS_FMFP_N2_ERR_FAIL : Cryptographic coprocessor non-critical failure: [chars].
Explanation	Cryptographic coprocessor non-critical operation failed. If the problem persists reboot the forwarding processor(ESP)
Recommended Action	If the problem persists reboot the forwarding processor (ESP).

%IMGR-0-FIPS_FMFP_N2_SEVERE_ERR_FAIL : Cryptographic coprocessor severe failure: [chars].
Explanation	Cryptographic coprocessor critical operation failed. Further data processing on ESP is halted
Recommended Action	forwarding processor (ESP) is rebooted automatically. no action needed

%IMGR-6-FMFP_KAT_TEST_RESULT : crypto self-test for algorithm: ([chars] … passed).
Explanation	Forwarding Manager power up known answer self-test (KAT) success. This is not an error message
Recommended Action	No action needed.

%IMGR-6-FMFP_IPSEC_MIN_MTU_INFO : MTU smaller than minimum IPSec MTU, [chars].
Explanation	Minimum MTU supported by crypto processor is 256B, MTU lower than 256B is set to 256B
Recommended Action	No action needed

%IMGR-6-FMFP_IPSEC_UNSUPPORTED_CIPHER : Cipher [chars] is not supported on this ESP.
Explanation	This ESP does not support this IPSec cipher
Recommended Action	No action needed

%IMGR-6-FMFP_IPSEC_CRYPTO_CTRL_THROTTLED : IPsec Control Plane Overload Crypto Device: [chars].
Explanation	This ESP crypto device is overloaded.
Recommended Action	May need to config platform ipsec control-plane medium\|heavy

%IMGR-6-FMFP_CRYPTO_DEVICE_BUSY : All Crypto Device cores are busy with data packets.
Explanation	All ESP crypto device are busy.
Recommended Action	May need to lower crypto traffic rate.

INDXOBJ

%INDXOBJ-3-INTERRUPT : index object routine [chars] called from interrupt context

Explanation

inappropriate index object routine called from interrupt routine.

Recommended Action

%INDXOBJ-3-ADD_ERROR : index add for [chars] failed: [chars]

Explanation

index object routine error

Recommended Action

INFRA

%INFRA-3-INVALID_GPM_ACCESS : Invalid GPM [chars] at [hex] HAL start [hex] HAL end [hex] INFRA start [hex] INFRA [hex] NET [hex], MSGDEF_LIMIT_MEDIUM
Explanation	Processing packet went beyond valid packet data, packet was possibly invalid, ppe info and encrypted pkt dump follow
Recommended Action	LOG_STD_ACTION

%INFRA-3-INVALID_GPM_ACCESS_INFO : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation	Registers associated with previous exception error
Recommended Action	LOG_STD_ACTION

%INFRA-3-INVALID_GPM_ACCESS_DATA :
Explanation	Packet associated with previous exception error The packet data has been encrypted
Recommended Action	LOG_STD_ACTION

INSTALL

%INSTALL-5-OPERATION_START_INFO : Started [chars] package [chars]
Explanation	This message is used to indicate the beginning of operations.
Recommended Action	No action required. This is not an error, it is an indication that the system is starting the operation.

%INSTALL-5-OPERATION_COMPLETED_INFO : Completed [chars] package [chars]
Explanation	This message is used to indicate the completion of operations.
Recommended Action	No action required. This is not an error, it is an indication that the system completed the operation.

%INSTALL-3-OPERATION_ERROR_MESSAGE : Failed to [chars] package [chars], Error: [chars]
Explanation	This message is used to inform the failure reason.
Recommended Action	Please refer to the error message to analyze the cause of failure.

%INSTALL-5-INSTALL_START_INFO : Started [chars] [chars] [chars]
Explanation	This message is used to indicate the beginning of install operations.
Recommended Action	No action required. This is not an error, it is an indication that the system is starting this operation.

%INSTALL-5-INSTALL_COMPLETED_INFO : Completed [chars] [chars] [chars]
Explanation	This message is used to indicate the completion of install operations.
Recommended Action	No action required. This is not an error, it is an indication that the system completed this operation.

%INSTALL-3-INSTANT_ERROR_MESSAGE : Error Message: [chars]
Explanation	This message is used to send a instant erorr message.
Recommended Action	No action required.

%INSTALL-5-INSTALL_AUTO_ABORT : Install auto abort timer expired: initiating abort
Explanation	An install operation has been aborted because the auto abort 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.

%INSTALL-5-INSTALL_AUTO_ABORT_TIMER_PROGRESS : Install auto abort timer will expire in [dec] seconds
Explanation	An install operation will be aborted after specified seconds of time.
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.

INTERCHASSIS_REDUNDANCY

%INTERCHASSIS_REDUNDANCY-4-STDBY_PRESENT : Removal of standby RP in location [chars] is recommended for inter-chassis redundancy
configuration

Explanation

Removal of standby RP from the chassis is recommended for inter-chassis redundancy

Recommended Action

INTERFACE_API

%INTERFACE_API-4-BADSWIDB : [chars] may not be referencing the correct swidb

Explanation

An internal software error occurred.

Recommended Action

%INTERFACE_API-4-BADPAKINPUT : pak->if_input is not initialized

Explanation

An internal software error occurred.

Recommended Action

%INTERFACE_API-1-NAMESTRTOOLONG : Interface name [chars].[int] exceeded maximum allowed length [dec]

Explanation

An internal software error occurred.

Recommended Action

%INTERFACE_API-3-NOADDSUBBLOCK : The [chars] subblock named [chars] was not added to [chars]

Explanation

A software error has occured, this message is displayed when IDB subblocks cannot be added.

Recommended Action

%INTERFACE_API-3-INVALIDSUBBLOCKPARAMETERS : Invalid subblock parameters for [chars] were supplied.

Explanation

An internal software error occurred.

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show idb and show tech-support
commands to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit BUG_TOOLKIT
. If you still require assistance, open a case with the Technical Assistance Center via the Internet TAC_CASE_OPEN , or contact
your Cisco technical support representative and provide the representative with the gathered information.

%INTERFACE_API-3-SUBNUMDBERR : subnum [hex] error in [chars]

Explanation

A software error has occured, this message is displayed when a problem has occured with a sub_number db.

Recommended Action

%INTERFACE_API-1-NOMORESWIDB : No more SWIDB can be allocated, maximum allowed [dec]

Explanation

No more Interfaces can be created because the maximum number of SWIDB allowed for this platform has been reached

Recommended Action

%INTERFACE_API-1-NOMORE_HASWIDBS : No more IDBS can be created. The maximum allowed numbers, [int], has been reached on Standby Please force redundancy mode to RPR if full Active Capacity, [int], is needed
Explanation	No more Software IDB numbers can be Created. The maximum allowed numbers has been reached for this High Available System.
Recommended Action

%INTERFACE_API-1-NOMOREHWIDBNUMBERS : No more hardware IDB numbers can be issued. The maximum allowed numbers, [dec], has been reached for this platform.
Explanation	No more hardware IDB numbers can be issued. The maximum allowed numbers has been reached for this platform.
Recommended Action	In addition to the following, copy the information from `show idb`. LOG_STD_ACTION

%INTERFACE_API-1-NOMORESWIDBNUMBERS : No more software IDB numbers can be issued. The maximum allowed numbers, [dec], has been reached for this platform.
Explanation	No more software IDB numbers can be issued. The maximum allowed numbers has been reached for this platform.
Recommended Action	In addition to the following, copy the information from `show idb`. LOG_STD_ACTION

%INTERFACE_API-4-BADPAKOUTPUT : pak->if_output is not initialized on interface [chars]

Explanation

An internal software error occurred.

Recommended Action

%INTERFACE_API-4-BADPOINTER : Function [chars] detected an invalid [chars] pointer of %08lX, ignoring

Explanation

A software error has occurred, this message is displayed when an invalid pointer is detected.

Recommended Action

%INTERFACE_API-3-NODESTROYSUBBLOCK : The [chars] subblock named [chars] was not removed

Explanation

A software error has occured, this message is displayed when IDB subblocks cannot be removed.

Recommended Action

%INTERFACE_API-3-CANNOTGETMTU : Error [dec] received while getting MTU: [chars]. Using default [int]

Explanation

A software error has occurred while attempting to retrieve the MTU value from the interface.

Recommended Action

%INTERFACE_API-3-NOSUBBLOCK : [chars] subblock does not exist on interface [chars]

Explanation

An internal software error occurred.

Recommended Action

%INTERFACE_API-4-TBLERROR : A error occurred while using the Index Table utility for [chars].

Explanation

A software error has occurred; this message is displayed when an Index table feature could not be used successfully.

Recommended Action

%INTERFACE_API-3-BADIDBSTATUSCHANGECALL : Invalid function call at interrupt level.

Explanation

An internal function was illegally called at interrupt level. This error might be caused by incorrectly coded creation or
deletion of an interface, or during an OIR operation.

Recommended Action

Perform a search of the Bug Toolkit, BUG_TOOLKIT . If you still require assistance, copy the error message exactly as it appears
on the console or in the system log. Issue the show tech command and copy the output. If you performed any actions before the error message appeared, make a note of this. Open a
case with the Technical Assistance Center via the Internet TAC_CASE_OPEN , or contact your Cisco technical support representative
and provide the representative with the gathered information.

%INTERFACE_API-3-IFNUMTOIDBERROR : Error occurred while using the ifnum to idb table for interface [chars], if number [dec],
during [chars]

Explanation

A software error has occurred. This message is displayed when an operation on the if_number to idb mapping table could not
be performed successfully.

Recommended Action

%INTERFACE_API-3-HWIDBQREENTRANT : [chars] in progress of being inserted/removed, ignoring new request to [chars]

Explanation

A software error has occurred while attempting to insert or remove the interface into the system as there’s already another
attempt in progress to insert or remove this interface. The first attempt must complete before a new attempt can be started.
The user should retry this operation at a later time.

Recommended Action

IOMD_INFRA

%IOMD_INFRA-4-BADPOINTER : Function [chars] detected an invalid [chars] pointer of %08lX, ignoring

Explanation

A software error has occurred, this message is displayed when an invalid pointer is detected.

Recommended Action

Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system
log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using
the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case,
or contact your Cisco technical support representative and provide the representative with the gathered information.

%IOMD_INFRA-3-IPCSENDFAIL : IOMD failed to send a message [chars] reason: [chars]

Explanation

IOMD failed to send message to the RP

Recommended Action

%IOMD_INFRA-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]

Explanation

The IM failed to allocate a buffer for communication with RSP

Recommended Action

%IOMD_INFRA-6-TDLMSG_INCOMPATIBLE : Failed to copy message [chars] to buffer, not allowed for current domain.

Explanation

Failure to marshal a message indicates an incompatibility with the intended recipient.

Recommended Action

%IOMD_INFRA-3-INVALID_SLOT_NUM : An invalid slot number is specified in one of the internal APIs. slot=[dec] max_slot=[dec]

Explanation

Invalid slot number to find the TDL domain

Recommended Action

%IOMD_INFRA-3-INVALID_BAY_NUM : An invalid bay number is specified in one of the internal APIs. bay=[dec] max_bay=[dec]

Explanation

Invalid bay number to find the TDL domain

Recommended Action

%IOMD_INFRA-4-INTR_OVER_LIMIT : IOMd main thread disabled interrupt for [int] msec.

Explanation

IOMd main thread process disabled interrupt too long

Recommended Action

%IOMD_INFRA-3-INTR_EVENT : IOMd fast thread event ([dec]).

Explanation

IOMd fast thread event

Recommended Action

%IOMD_INFRA-3-I2C_WRITE : An I2C write has failed because [chars]
Explanation	An I2C write has failed. This could be due to a hardware or software defect.
Recommended Action	Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.

%IOMD_INFRA-3-I2C_READ : An I2C read has failed because [chars]
Explanation	An I2C read has failed. This could be due to a hardware or software defect.
Recommended Action	Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.

%IOMD_INFRA-3-LINECARDDIAGSFAILED : Module [chars] in Slot [dec] failed online diagnostics. Please use ‘show post’ for more details
Explanation	Online Diag has failed. This could be due to a hardware or software defect.
Recommended Action	Note the time of the error message and examine the logs for errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.

IOSD

%IOSD-3-BIPC_REJECT : Could not accept ipc connection: [chars]
Explanation	This error occurs if shell-manager has denied an ipc connection request from IOS.
Recommended Action	Check the connection request parameters.

%IOSD-3-TDL_PROPERTIES : Could not set message properties for connection: [chars]
Explanation	This error occurs if shell-manager is unable to set message properties for the IOS-sman connection
Recommended Action	Check the connection request parameters.

IOSD_INFRA

%IOSD_INFRA-6-IFS_DEVICE_OIR : Device [chars] [chars]
Explanation	USB inserted/removed
Recommended Action	No action is required.

%IOSD_INFRA-3-IFS_DEVICE_DETECT_FAIL : Device [chars] [chars]
Explanation	USB detection failed
Recommended Action	USB Insertion could not be handled completely. Device needs to be removed and re-inserted

IOSXE_APS through IOSXE_FMANRP_CCE

IOSXE_APS
IOSXE_CSLIFS
IOSXE_CXSC
IOSXE_DNS
IOSXE_EPA
IOSXE_ETHERCHAN
IOSXE_EZMENU
IOSXE_FMANRP
IOSXE_FMANRP_ADJ
IOSXE_FMANRP_CCE

IOSXE_APS

%IOSXE_APS-3-GROUP_CONFIG_FAIL : Group change for interface [chars] Group [dec] failed

Explanation

Group change for interface has failed

Recommended Action

%IOSXE_APS-3-CONFIG_FAIL : config change for interface [chars] Group [dec] failed

Explanation

config for an interface to forwarding plane has failed

Recommended Action

%IOSXE_APS-3-FLOWIDDELETIONFAILED : Deletion of APS flow ID with manager failed for interface [chars] group [dec]

Explanation

An unexpected condition has occurred that deletion of APS flow ID.

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show interface 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.

%IOSXE_APS-3-FLOWIDALLOCFAILED : Allocation of APS flow ID with manager failed for interface [chars] group [dec]

Explanation

An unexpected condition has occurred that allocation of APS flow ID. failed

Recommended Action

%IOSXE_APS-3-PAIR_CONFIG_FAIL : Pair config for interface [chars] Group [dec] failed

Explanation

Pair config for interface has failed

Recommended Action

%IOSXE_APS-3-CCCONFIGFAILED : Pair config for interface [chars] Group [dec] failed

Explanation

Pair config for interface has failed

Recommended Action

%IOSXE_APS-3-FLOWCONFIGTOCCFAILED : Flow id to cc for interface [chars] Group [dec] failed

Explanation

Flow id to cc for an interface has failed

Recommended Action

%IOSXE_APS-3-DOWNLOADFAIL : Unable to download [chars] message to [chars]

Explanation

An unexpected condition has occurred which resulted in a configuration not being sent to the reported process.

Recommended Action

IOSXE_CSLIFS

%IOSXE_CSLIFS-3-ERROR_SETTING : Error setting default file system ([dec])
Explanation	There is an error happened after calling function ifs_set_default_directory
Recommended Action	Check the csl filesystem

IOSXE_CXSC

%IOSXE_CXSC-3-ALLOC : Failed to allocate message for proposition

Explanation

When attempting to program the dataplane with a CXSC proposition object, there was no enough memory to allocate the message.

Recommended Action

%IOSXE_CXSC-3-MESSAGE : Failed to send message for proposition

Explanation

When the proposition was being prepared for sending to the data plane, there was an error.

Recommended Action

%IOSXE_CXSC-3-ACTION : Unknown proposition action ([dec])

Explanation

When the proposition was being sent to the data plane, the action was unknown error.

Recommended Action

%IOSXE_CXSC-3-BAD_PROPOSITION : Proposition obj corrupt

Explanation

When the proposition was being sent to the data plane, the object itself is corrupt.

Recommended Action

%IOSXE_CXSC-3-BAD_SUMMARY : Summary obj corrupt

Explanation

When the proposition summary was being sent to the data plane, the object itself is corrupt.

Recommended Action

%IOSXE_CXSC-4-DUAL_RP_UNSUPPORTED : Dual RPs are not supported in conjunction with CXSC

Explanation

CXSC is not supported in a dual RP environment. To resolve this warning, either unconfigure CXSC or remove the redundant Route
Processor.

Recommended Action

%IOSXE_CXSC-3-RF_INIT : Failed to initialize CXSC Redundancy Facility client

Explanation

An unexpected condition occurred where the CXSC Redundancy Facility failed to initialize.

Recommended Action

%IOSXE_CXSC-3-STILE_ACTIVATE : Failed to activate NBAR classification: ([dec])

Explanation

An unexpected condition occurred where the CXSC NBAR protocol classification failed to activate.

Recommended Action

%IOSXE_CXSC-3-STATISTICS_ALLOCATION : Unable to allocate space for statistics

Explanation

During initialization, there was failure in the allocation of the memory to gather the statistics. It is non fatal, but after
seeing this message, the CXSC subsystem will not be able to gather statistics.

Recommended Action

%IOSXE_CXSC-3-BAD_PROTOCOLPACK : Invalid Protocol Pack object

Explanation

When the Protocol Pack was being sent to the data plane, the object’s contents were invalid.

Recommended Action

%IOSXE_CXSC-3-FILESYSTEM_ERR : FileSystem Error ([chars]): Unable to Copy File from [chars] to [chars]

Explanation

Unable to copy the NBAR Protocol Pack File to the file system for subsequent loading. The system will revert to the previously
loaded Protocol Pack.

Recommended Action

%IOSXE_CXSC-3-INSUFFICIENT_ALLOC_IOSXE_VER : Insufficent memory allocated for IOSXE version String

Explanation

The input IOSXE Version String has insufficient memory to hold the IOSXE Version.

Recommended Action

%IOSXE_CXSC-3-INSUFFICIENT_ALLOC_NBAR_VER : Insufficent memory allocated for NBAR Engine Version String

Explanation

The input NBAR Engine Version string has insufficient memory to hold the NBAR Engine Version.

Recommended Action

%IOSXE_CXSC-3-PLATFORM_TYPE : Unrecognised platform type. CPU ID [dec]

Explanation

The platform that the cxsc service is being installed on is not recognised. The most likely cause is that this platform is
not supported.

Recommended Action

IOSXE_DNS

%IOSXE_DNS-3-UPDATE_FAILED : Update resolv.conf, vrf [chars], rc [dec]

Explanation

An unexpected condition has occurred while updating the DNS file

Recommended Action

%IOSXE_DNS-3-VRF_FAILED : Operation ([chars]) on /etc/netns/[chars], rc [dec]

Explanation

An unexpected condition has occurred while updating the DNS directory

Recommended Action

IOSXE_EPA

%IOSXE_EPA-3-CREATION_FAILURE : slot=[dec] subslot=[dec], spa_type=[hex], lc_type=[hex].

Explanation

Failed to create a SPA object.

Recommended Action

%IOSXE_EPA-3-ACT2_AUTHENTICATION_FAILURE : slot=[dec] subslot=[dec], spa_type=[hex], lc_type=[hex].

Explanation

ACT2 dev authentication Failed.

Recommended Action

%IOSXE_EPA-3-NULL_EPASENSOR_PTR :

Explanation

Pointer to a DEVSENSOR object is NULL.

Recommended Action

%IOSXE_EPA-3-NULL_PORT_PTR :

Explanation

Pointer to a PORT object is NULL.

Recommended Action

%IOSXE_EPA-3-NULL_DEVPSEQ_PTR :

Explanation

Pointer to a DEVPSEQ object is NULL.

Recommended Action

%IOSXE_EPA-3-NULL_DEVOBJ_PTR :

Explanation

Pointer to a DEVOBJ object is NULL.

Recommended Action

%IOSXE_EPA-3-NULL_FPGA_PTR :

Explanation

Pointer to a FPGA object is NULL.

Recommended Action

%IOSXE_EPA-3-NULL_EPA_PTR :

Explanation

Pointer to an EPA object is NULL.

Recommended Action

%IOSXE_EPA-3-NULL_VSC_PHY_INFO_PTR :

Explanation

Pointer to a VSC PHY INFO object is NULL.

Recommended Action

%IOSXE_EPA-3-NULL_VFT :

Explanation

Pointer to a DEVSENSOR object is NULL.

Recommended Action

%IOSXE_EPA-3-UNSUPPORTED_XCVR : Transceiver type [chars] is not allowed on spa [chars], port [dec],
Explanation	This transceiver is not allowed on the SPA
Recommended Action	Consult the documentation and ensure supported transceivers are plugged into the SPA

%IOSXE_EPA-3-AUTONEG_CFG_ERR : interface [chars] autoneg state ‘[chars]’ is incompatible with transciever. Remove ‘[chars]’ to allow the transceiver.
Explanation	Autoneg Config is not compatible. Remove autoneg config on the interface to allow the transceiver
Recommended Action	Remove the negotiation auto config or reinsert the previously enabled transceiver.

%IOSXE_EPA-3-XCVR_EC_BWMISMATCH : Trasnsceiver bandwidth is incompatible with Port-channel[dec] allowed bandwidth. Remove ‘channel-group [dec]’ config for interface [chars] to allow the transceiver
Explanation	The interface port into which the transceiver is inserted is part of a Port-channel. The Port-channel has member links whose bandwidth doesn’t match with the inserted transceier’s bandwidth. Since, port-channel cannot allow heterogenous bandwidth links, this transceiver is not allowed in to the port.
Recommended Action	Remove the channel-group config for the port where transceiver is inserted or insert a transceiver whose bandwidth is compatible with the port-channel bandwidth

%IOSXE_EPA-3-XCVR_PROHIBIT : Transceiver is prohibited to come online for interface [chars]

Explanation

XCVR is prohibited on the interface

Recommended Action

IOSXE_ETHERCHAN

%IOSXE_ETHERCHAN-6-LINK_MTU : Interface [chars] MTU set to port-channel [chars] MTU [dec]
Explanation	The MTU for the interface mentioned in the message is changed to match the MTU configured on the port channel interface
Recommended Action	No action is required.

%IOSXE_ETHERCHAN-3-LINK_MTU_FAIL : Failure in changing MTU of interface [chars] to port-channel [chars] MTU
Explanation	The MTU for the interface mentioned in the message cannot be changed to match the MTU configured on the port channel interface
Recommended Action	Remove the link mentioned in the message from the port-channel group

IOSXE_FMANRP

%IOSXE_FMANRP-4-MSGDISPATCHNULL : TDL messages NULL from IOS.

Explanation

An unexpected condition has occurred while IOS trying to dispatch the TDL message handler functions for received TDL messages
from Forwarding Manager.

Recommended Action

%IOSXE_FMANRP-4-MSGDISPATCH : Unable to dispatch received TDL message ‘[chars]’ from Forwarding Manager. LUID: [chars]

Explanation

An unexpected condition has occurred while IOS trying to dispatch the TDL message handler functions for received TDL messages
from Forwarding Manager.

Recommended Action

%IOSXE_FMANRP-4-MSGIPCERR : Unable to process received IPC messages from Forwarding Manager, error: [chars].

Explanation

An unexpected condition has occurred while IOS trying to process received IPC message from Forwarding Manager.

Recommended Action

%IOSXE_FMANRP-3-EPOCHTDLMSGMARSHAL : Failed to copy epoch TDL message to IPC buffer, epoch number [dec]

Explanation

This operation to build a TDL messages for epoch message has failed.

Recommended Action

%IOSXE_FMANRP-3-MSGMARSHALERR : Unable to copy IPC messages into transport buffer. Message: [chars]

Explanation

An unexpected condition has occurred while IOS trying to copy IPC message to transport buffer in order to send the message
from IOSd to Forwarding Manager.

Recommended Action

%IOSXE_FMANRP-3-MSGENQERR : Unable to enqueue IPC messages to IOS IPC queue. Message: [chars].

Explanation

An unexpected condition has occurred while IOS trying to enqueue IPC message to IOS IPC queue in order to send the message
to Forwarding Manager.

Recommended Action

%IOSXE_FMANRP-4-MSGNONTDLSTATSERR : Unable to process received non-TDL stats message from Forwarding Manager, error: [chars]
([dec]).

Explanation

An unexpected condition has occurred while IOS trying to process received non-TDL stats message from Forwarding Manager.

Recommended Action

IOSXE_FMANRP_ADJ

%IOSXE_FMANRP_ADJ-3-NOADJ : Adjacency entry is null

Explanation

An unexpected condition has occurred which is due to the absence of an adjacency entry structure.

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show adjacency 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.

%IOSXE_FMANRP_ADJ-3-NOFIBHWIDB : FIB Interface [chars] is null
Explanation	An unexpected condition has occurred which is due to the absence of a FIB interface structure.
Recommended Action	LOG_STD_SH_CMD_ACTION(show adj)

%IOSXE_FMANRP_ADJ-3-ENQUEFAIL : Unable to send [chars] [chars] message to Forwarding Manager Process

Explanation

An unexpected condition has occurred which resulted in a configuration not being sent to the Forwarding Manager Processs.

Recommended Action

%IOSXE_FMANRP_ADJ-3-ENCSIZE : Invalid encap length [dec] which is larger than max allowed [dec] bytes

Explanation

An unexpected condition has occurred which is due to invalid adjacency encapsulation size being larger than the maximum value
allowed.

Recommended Action

IOSXE_FMANRP_CCE

%IOSXE_FMANRP_CCE-4-CCE_STACK_LIMIT : Failed to create class [dec] filter list
Explanation	An operation to send a filter list to the forwarding processor for a particular class has failed due to a resource issue. This may imply that the notification was dropped.
Recommended Action	LOG_STD_SH_CMD_ACTION(show class-map [type <class type> <name>])

%IOSXE_FMANRP_CCE-3-CCE_INVALID_FILTER_RELN : Invalid filter relation [int]
Explanation	An internal error occured when trying to build class-map information for one of the classes in a policy-map.
Recommended Action	LOG_STD_SH_CMD_ACTION(show policy-map [type <policy type> <name>])

%IOSXE_FMANRP_CCE-3-CCE_FILTER_OVERFLOW : Filter list overflow at type [chars]
Explanation	An internal error occured when trying to build class-map information for one of the classes in a policy-map.
Recommended Action	LOG_STD_SH_CMD_ACTION(show class-map [type <class type> <name>])

%IOSXE_FMANRP_CCE-3-CCE_CLASS_CREATE : Unable to create class [int].[int]
Explanation	An error occured when trying to create a class-map.
Recommended Action	LOG_STD_SH_CMD_ACTION(show policy-map [type <policy type> <name>])

%IOSXE_FMANRP_CCE-4-CCE_NESTED_CLASS_LIMIT : Nested class [dec] layers cannot exceed 4
Explanation	When configure nested classes as match statements, the total levels of nested classes cannot exceed 4 layers
Recommended Action	LOG_STD_SH_CMD_ACTION(show class-map [type <class type> <name>])

IOSXE_FMANRP_CEF through IOSXE_MEMPOOL_MIB

IOSXE_FMANRP_CEF
IOSXE_FMANRP_FPM
IOSXE_FMANRP_OBJID
IOSXE_FMANRP_OBJID2
IOSXE_FMANRP_RTMAP
IOSXE_FMANRP_URPF
IOSXE_FMANRP_ZONES
IOSXE_INFRA
IOSXE_LICENSE_POLICY_MANAGER
IOSXE_MEMPOOL_MIB

IOSXE_FMANRP_CEF

%IOSXE_FMANRP_CEF-3-NOFIB : FIB entry is null

Explanation

An unexpected condition has occurred which is due to the absence of a FIB entry structure.

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show ip cef 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.

%IOSXE_FMANRP_CEF-3-NOFIBSB : FIB SB entry is null

Explanation

An unexpected condition has occurred which is due to the absence of a FIB SB entry structure.

Recommended Action

%IOSXE_FMANRP_CEF-3-NOFIBTABLE : FIB table is null

Explanation

An unexpected condition has occurred which is due to the absence of a FIB table structure.

Recommended Action

%IOSXE_FMANRP_CEF-3-NOFIBIDB : FIB interface is null

Explanation

An unexpected condition has occurred which is due to the absence of a FIB interface structure.

Recommended Action

%IOSXE_FMANRP_CEF-3-ENQUEFAIL : Unable to send [chars] [chars] message to Forwarding Manager Process

Explanation

An unexpected condition has occurred which resulted in a configuration not being sent to the Forwarding Manager Processs.

Recommended Action

%IOSXE_FMANRP_CEF-4-UPDFRAGSTATSERR : Update IP Fragmentation statistics error

Explanation

An unexpected condition has occurred when updating fragmentation statistics

Recommended Action

%IOSXE_FMANRP_CEF-4-UPDREASSSTATSERR : Update IP Reassembly statistics error

Explanation

An unexpected condition has occurred when updating reassembly statistics

Recommended Action

%IOSXE_FMANRP_CEF-4-UPDSTATSERR : Update CEF statistics error

Explanation

An unexpected condition has occurred when updating cef statistics

Recommended Action

%IOSXE_FMANRP_CEF-3-ROUTEMSGMARSHAL : Failed to copy route essage to IPC buffer for prefix [chars]/[dec] — [chars]

Explanation

This operation to build a TDL messages for route download has failed.

Recommended Action

%IOSXE_FMANRP_CEF-3-NOFIBPUSHCNT : FIB push counter is null

Explanation

An unexpected condition has occurred which is due to the absence of a FIB push counter structure.

Recommended Action

%IOSXE_FMANRP_CEF-3-NOFIBSIGNAL : FIB signal is null

Explanation

An unexpected condition has occurred which is due to the absence of a FIB signal structure.

Recommended Action

%IOSXE_FMANRP_CEF-3-NONATADDR : NAT address is null

Explanation

An unexpected condition has occurred which is due to the absence of an NAT address.

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show ip alias 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.

IOSXE_FMANRP_FPM

%IOSXE_FMANRP_FPM-4-INVALIDLENTYPE : Field length type in PHDF file is invalid

Explanation

An unexpected condition has occurred which is due to the invalid field length type in PHDF file.

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the 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.

%IOSXE_FMANRP_FPM-4-INVALIDMATCHTYPE : FPM match type is invalid [dec]

Explanation

An unexpected condition has occurred which is due to the invalid FPM match type in one of FPM class-map filter match entry

Recommended Action

%IOSXE_FMANRP_FPM-4-INVALIDACTION : FPM feature action is invalid [dec]

Explanation

An unexpected condition has occurred which is due to the invalid action type when trying to bind FPM action with target class
group.

Recommended Action

%IOSXE_FMANRP_FPM-3-NOSTATUPDATE : Failed to update class-map statistics during periodic update

Explanation

A statistics update for a class-map has failed.

Recommended Action

IOSXE_FMANRP_OBJID

%IOSXE_FMANRP_OBJID-5-DUPCREATE : Duplicate forwarding object creation obj_handle [hex], type [int], existing obj_id [hex],
type [int]

Explanation

An unexpected condition has occurred which results in duplicate forwarding object creation.

Recommended Action

IOSXE_FMANRP_OBJID2

%IOSXE_FMANRP_OBJID2-3-DUPCREATE : Duplicate forwarding object creation obj_handle [hex], type [int], existing obj_id [hex],
type [int]

Explanation

An unexpected condition has occurred which results in duplicate forwarding object creation with different object types.

Recommended Action

IOSXE_FMANRP_RTMAP

%IOSXE_FMANRP_RTMAP-3-RTMAPNULL : The route-map structure for [chars] is null
Explanation	An unexpected condition has occurred which is due to the absence of a route-map data structure.
Recommended Action	show route-map

%IOSXE_FMANRP_RTMAP-4-UNKOWNCLIANT : Unknown client type [dec] received

Explanation

An unexpected known client type is received for route-map download.

Recommended Action

%IOSXE_FMANRP_RTMAP-3-INVALID_LIST : NULL

Explanation

An internal list structure has been detected as invalid.

Recommended Action

%IOSXE_FMANRP_RTMAP-3-RTMAP_UNSUPPORTED : Routemap ([chars]) contain unsupported match/set clause, ignored

Explanation

A map contains unsupported match or set clause

Recommended Action

IOSXE_FMANRP_URPF

%IOSXE_FMANRP_URPF-4-NOV4SWIDB : v4 sub-interface is null

Explanation

An unexpected condition has occurred which is due to the absence of a v4 swidb structure.

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show ip interface 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.

%IOSXE_FMANRP_URPF-4-NOV6SWIDB : v6 sub-interface is null

Explanation

An unexpected condition has occurred which is due to the absence of a v6 swidb structure.

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show ipv6 interface 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.

%IOSXE_FMANRP_URPF-3-INVALIDIFHDL : Invalid interface handle [int] for interface (number= [int], swidb= [hex], name= [chars])

Explanation

An unexpected condition has occurred which is due to an invalid interface handle

Recommended Action

%IOSXE_FMANRP_URPF-4-UPDV4STATSERR : Update v4 URPF statistics error

Explanation

An unexpected condition has occurred when updating v4 URPF statistics

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show ip interface <name> 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.

%IOSXE_FMANRP_URPF-4-UPDV6STATSERR : Update v6 URPF statistics error

Explanation

An unexpected condition has occurred when updating v6 URPF statistics

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show ipv6 interface <name> 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.

IOSXE_FMANRP_ZONES

%IOSXE_FMANRP_ZONES-3-NOSTATUPDATE : Failed to update zone-pair statistics during periodic update (zone [chars], class [int])

Explanation

A statistics update for a zone-pair has failed.

Recommended Action

IOSXE_INFRA

%IOSXE_INFRA-3-INVALID_ERRMSG : Error message type [dec] not defined

Explanation

Error message type used is not defined in IOSXE infrastruction

Recommended Action

%IOSXE_INFRA-3-SHIM_INIT_WQ_FAIL : IOSXE shim layer initialization failed: Can not create receiving queues

Explanation

IOSXE IOS shim layer initialization of watched queue failed

Recommended Action

%IOSXE_INFRA-3-SHIM_INIT_WQ_CHASFS_FAIL : IOSXE shim layer initialization failed: Can not create receiving chasfs watched
queue

Explanation

IOSXE IOS shim layer initialization of watched queue failed

Recommended Action

%IOSXE_INFRA-3-SHIM_INIT_PROC_FAIL : IOSXE shim layer initialization failed: Dispatch process creation failed

Explanation

IOSXE IOS shim layer initialization creating dispatch process failed

Recommended Action

%IOSXE_INFRA-3-SHIM_INIT_MEM_FAIL : IOSXE shim layer initialization failed: Memory initialization failed.

Explanation

IOSXE IOS shim layer initialization of memory failed

Recommended Action

%IOSXE_INFRA-3-SHIM_NO_IPC_DISPATCH_HDL : IOSXE shim layer [chars] process message without IPC dispatch handler.

Explanation

IOSXE IOS shim layer has no ipc dispatch handler set

Recommended Action

%IOSXE_INFRA-3-SHIM_RXMSG_NO_IPC_HDL : IOSXE shim layer without IPC handler for fd [dec], seqnum [dec].

Explanation

IOSXE IOS shim layer cannot find ipc handler

Recommended Action

%IOSXE_INFRA-3-SHIM_INIT_TDL_FAIL : IOSXE shim layer initialization TDL Lib [chars] failed.

Explanation

IOSXE IOS shim layer initialization of TDL library

Recommended Action

%IOSXE_INFRA-3-SHIM_INIT_DISPATCH_INIT_FAIL : IOSXE shim layer initialization, dispatch path init failed.

Explanation

IOSXE IOS shim layer initialization of TDL disatch path

Recommended Action

%IOSXE_INFRA-3-INVALID_RUNTIME_IDX : Thread runtime index [dec] is not valid

Explanation

Export the thread’s running time failed.

Recommended Action

%IOSXE_INFRA-6-THEAD_SELECT_ERR : Inbound message or packet select error, [chars].

Explanation

Socket select operation error in threads

Recommended Action

%IOSXE_INFRA-3-INJECT_HDR_LENGTH_ERR : Inject hdr size [int] exceeds limit

Explanation

Inject header length exceeds pak header space

Recommended Action

%IOSXE_INFRA-3-INJECT_EMBEDDED_HDR_LENGTH_ERR : Can’t allot space needed for embedded inject hdr size [int] exceeds limit

Explanation

Can’t allot space needed for embedded inject header, exceeds pak header space

Recommended Action

%IOSXE_INFRA-3-INJECT_NO_IF_OUTPUT_ERR : Output intf is NULL, [chars]

Explanation

Output intf is requred to proceed, else skip the feautre

Recommended Action

%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_INV_PARAM : Invalid parameter: [chars]

Explanation

Invalid parameter was passed when generating punt err log

Recommended Action

%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_GET_FILE_NAME : Failed to get file name: [chars]

Explanation

Could not form a file name when generating punt err logPunt keepalive log error seen

Recommended Action

%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_INV_FILE_ID : Invalid file descriptor: [dec]

Explanation

Invalid file descriptor was found when generating punt err log

Recommended Action

%IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_OPEN_FILE : Failed to open file: [chars]

Explanation

Failed to open file when generating punt err log

Recommended Action

%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_CLOSE_FILE : Failed to close file with descriptor: [dec]

Explanation

Closing of file failed when generating punt err log

Recommended Action

%IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_WRITE_TO_FILE : Write to file Id [dec] failed [dec] bytes, expected [dec] bytes

Explanation

Write to file failed when generating punt err log

Recommended Action

%IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_ALLOC_TTY : Failed to allocate a tty

Explanation

Can’t allocate a TTY when generating punt err log

Recommended Action

%IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_ALLOC_CSB : Failed to allocate a csb

Explanation

Can’t allocate a csb when generating punt err log

Recommended Action

%IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_PARSE_CMD : Failed to parse command: [chars]

Explanation

Failed to parse a command when generating punt err log

Recommended Action

%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_GET_PROCID : Failed to get process id

Explanation

Can’t get identifier of the process generating punt err log

Recommended Action

%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_INV_PROCID : Invalid proc id [dec], expected [dec]

Explanation

Invalid process trying to generate punt err log

Recommended Action

%IOSXE_INFRA-4-NO_PUNT_KEEPALIVE : Keepalive not received for [int] seconds

Explanation

Punt Inject keepalive message was not received

Recommended Action

%IOSXE_INFRA-2-FATAL_NO_PUNT_KEEPALIVE : Keepalive not received for [int] seconds resetting

Explanation

Punt Inject keepalive message was not received

Recommended Action

%IOSXE_INFRA-2-FATAL_PUNT_LINK_DOWN : Punt Inject link went down resetting

Explanation

Punt Inject link went down

Recommended Action

%IOSXE_INFRA-3-INJECT_GSB_CTL_INIT_FAIL : Inject adjacency subblock init failed

Explanation

Adj subblock control or register failed

Recommended Action

%IOSXE_INFRA-3-PUNT_ADDR_RES_ENCAP_ERR : Punted address resolution packet with unknown encap [chars]

Explanation

Punted packet for ARP/ND with encap not supported

Recommended Action

%IOSXE_INFRA-3-PUNT_SVC_PROC_ERR : Punt service [chars] create failed

Explanation

Punt service process can not be created

Recommended Action

%IOSXE_INFRA-3-VM_PAGE_TABLE_ERR : VM guarded page operation failed, address [hex], [chars]

Explanation

VM guarded page avl tree operation error

Recommended Action

%IOSXE_INFRA-3-PUNT_SVC_TYPE_UNKNOWN : Punted packet with unknown service type [int]

Explanation

Punted pak with an unsupported service type

Recommended Action

%IOSXE_INFRA-5-PUNT_SVC_CANT_ENQUEUE : Punted pak can’t be enqueued for service

Explanation

Punted pak enqueue failed

Recommended Action

%IOSXE_INFRA-5-PUNT_SVC_INVALID_OPT_PKT : Invalid IPv4 options packet punted to RP

Explanation

Invalid IPv4 options packet dropped in RP

Recommended Action

%IOSXE_INFRA-4-INJECT_TUN_NONIP_WARN : pak with linktype [chars] gets into non-ip tunnel

Explanation

IP/IPv6/MPLS packet should to go through GRE tunnel for non-IP payload

Recommended Action

%IOSXE_INFRA-3-INJECT_FEATURE_ESS_ERR : ESS segment not found, type [dec] hdl [hex]

Explanation

Packets to be injected to an unsupported ESS segment

Recommended Action

%IOSXE_INFRA-6-PROCPATH_CLIENT_HOG : IOS shim client ‘[chars]’ has taken %ld msec (runtime: %ld msec) to process a ‘[chars]’
message

Explanation

The specified IOSXE IOS shim client has taken too long to process a received IPC or chasfs message

Recommended Action

%IOSXE_INFRA-6-AUXTHD_REQUEST : Too many outstanding requests for file system access

Explanation

Resource temporarily unavailable

Recommended Action

%IOSXE_INFRA-3-APP_SESS_OPEN_FAILED : An attempt to open [chars] with handle number [dec] has failed ([dec])

Explanation

Application session between processes failed to estabish.

Recommended Action

%IOSXE_INFRA-3-CONSOLE_DBUG_DROP : System dropped [dec] bytes of console debug messages.
Explanation	Debugging messages are being generated faster than they can be displayed on the console. The messages can not be guaranteed to be seen so this message replaces the lost messages.
Recommended Action	Consider using conditional debugging or turning off console logging.

%IOSXE_INFRA-3-PUNT_INCOMP_WRONG_ADJID : Punted address resolution packet linktype [chars], adj-id [dec] is with linktype
[chars]

Explanation

CPP needs to punt incomplete adjacency for resolution by specifying the adjacency-id, but the included adjacency-id does not
match the incomplete adjacency this packet triggered.

Recommended Action

%IOSXE_INFRA-3-IFS_EXTLINK_ADD_FAIL : Could not add filesystem [chars] to IFS links

Explanation

Attempt to add filesystem root to allow for links failed

Recommended Action

%IOSXE_INFRA-3-IFS_UDEV_REMOVE_FAIL : Could not remove udev device [chars]

Explanation

Attempt to remove udev device failed

Recommended Action

%IOSXE_INFRA-3-IFS_DFLT_FS_REG_FAIL : Unable to set [chars] as a default file system.

Explanation

IOSXE’s platform dependent code failed to register the default file system.

Recommended Action

%IOSXE_INFRA-3-IFS_INIT_HIDDEN_FAIL : IOSXE shim layer initialization failed: Can not create receiving queues

Explanation

IOSXE IOS shim layer initialization of hidden path watch failed

Recommended Action

%IOSXE_INFRA-3-BSO_MSG_HDR_LENGTH_ERR : BSO message header length [int] is incorrect

Explanation

BSO message header length is incorrect

Recommended Action

%IOSXE_INFRA-3-BSO_MSG_HDR_MSGTYPE_ERR : BSO message header msgtype [int] is incorrect

Explanation

BSO message header msgtype is incorrect

Recommended Action

%IOSXE_INFRA-3-BSO_MSG_UNMARSHAL_ERR : BSO message unmarshalling has failed

Explanation

BSO message unmarshalling has failed

Recommended Action

%IOSXE_INFRA-3-BSO_MSG_CACHE_ERR : BSO message query cache update error — [chars]

Explanation

BSO message query cache update error

Recommended Action

%IOSXE_INFRA-4-BSO_MSG_RIB_WATCH_WARN : BSO message RIB watch start error

Explanation

BSO message RIB watch start error

Recommended Action

%IOSXE_INFRA-3-RELOAD_INFO_SAVE_FAIL : Unable to save reload information: [dec]: [chars].

Explanation

IOSXE’s platform dependent code failed to save the reload information.

Recommended Action

%IOSXE_INFRA-3-SN_IPFRR_PROC_ERR : Static Nexthop IPFRR [chars] create failed

Explanation

SN IPFRR process can not be created

Recommended Action

%IOSXE_INFRA-6-CONSOLE_ACTIVE : [chars]
Explanation	Indicates that the current instance of IOS is assuming active control of the console. This is informational.
Recommended Action	No action is required.

%IOSXE_INFRA-6-PLATFORM_RELOAD : [chars]
Explanation	Indicates that the current instance of IOS is being reset by the platform code. This is part of a normal reset sequence and the message is informational.
Recommended Action	No action is required.

%IOSXE_INFRA-6-CHASFS_CLOCK_SET_FAIL : Failed to set Chasfs property on system time change

Explanation

Unable to set chasfs property on system time change

Recommended Action

%IOSXE_INFRA-3-CYAN_API_ERROR : Failed to retrieve platform dependent value of [chars] (err=[dec])

Explanation

CYAN API function failed

Recommended Action

%IOSXE_INFRA-6-SHIM_RXMSG_IPC_INFO : IOS shim layer process IPC msg for fd [dec], seq_num [dec], ipc_status [dec]

Explanation

Recommended Action

%IOSXE_INFRA-3-SHIM_IPC_NOT_PROCESSED : msg handler returned FALSE for IPC msg for fd [dec], seq_num [dec], service [chars]

Explanation

Recommended Action

%IOSXE_INFRA-3-SWIFT_ORCH_PROC_FAIL : IOSXE SWIFT Orchestrator process creation failed

Explanation

The SWIFT Orchestrator process could not be created

Recommended Action

%IOSXE_INFRA-3-BAD_GLIBC_BUF_FREE : An IOS buffer is freed into GLIBC buffer pool, buffer blockmagic [hex], flags [hex]

Explanation

An IOS buffer is freed into GLIBC buffer pool.

Recommended Action

%IOSXE_INFRA-3-BIPC_MGS_ALLOC_FAIL : Allocating [dec] byte for IPC [chars] msg failed: out of memory

Explanation

system is out of memory

Recommended Action

%IOSXE_INFRA-3-SOCKET_PEEK_ERR : Interrupt processing of Punt received packets over socket failed as peek of packet returned
error: [chars]

Explanation

Peek at incoming message hit error

Recommended Action

%IOSXE_INFRA-3-GET_BUFFER_ERR : Interrupt processing of Punt received packets over socket failed to get a packet buffer for
len [dec]

Explanation

Failed to get a packet buffer from the specified pool.

Recommended Action

%IOSXE_INFRA-3-SOCKET_RECV_ERR : Interrupt processing of Punt received packets over socket failed as receive packet hit error:
[chars]

Explanation

Hit error when receives packet from a socket.

Recommended Action

%IOSXE_INFRA-3-SOCKET_SEND_ERR : Transmit packet to the socket hit error: [chars]

Explanation

Transmit a packet to another socket hit error.

Recommended Action

%IOSXE_INFRA-3-INJECT_HEADER_ERR : Transmit packet to the socket failed as packet header length is greater than datagram
size. It’s an incorrect packet and cannot proceed sending. header length is [dec], datagram size is [dec].

Explanation

Packet header length is wrong.

Recommended Action

%IOSXE_INFRA-3-IDB_CREATE_ERR : Failed to create IDB(Interface Descriptor Block) for Punt/Inject socket interface

Explanation

Creating an idb corresponding to an interface failed.

Recommended Action

%IOSXE_INFRA-3-MALLOC_FAST_ERR : Failed to allocate memory for Punt/Inject socket instance

Explanation

malloc_fast failed to allocate memory.

Recommended Action

%IOSXE_INFRA-3-IDB_INIT_ERR : Failed to initialize IDB(Interface Descriptor Block) for Punt/Inject socket interface

Explanation

Hit error when we initialize idb.

Recommended Action

%IOSXE_INFRA-3-PI_SOCKET_RAW_PRE_INIT_ERR : Punt/Inject socket pre-initialization(IDB creation) failed

Explanation

PI Socket Raw pre-initialization failed.

Recommended Action

%IOSXE_INFRA-3-PI_SOCKET_RAW_INIT_ERR : Punt/Inject socket initialization failed

Explanation

PI Socket Raw initialization failed.

Recommended Action

%IOSXE_INFRA-3-MCPRP_INIT_PUNTPATH_FD_ERR : Initializing the ipc control for the puntpath fd failed

Explanation

Initializing the ipc control for the puntpath fd failed

Recommended Action

%IOSXE_INFRA-3-LIIN_TUN_MSG_ERR : LIIN error — [chars] [chars] [dec]

Explanation

LIIN in Tunnel mode experiencing error

Recommended Action

IOSXE_LICENSE_POLICY_MANAGER

%IOSXE_LICENSE_POLICY_MANAGER-2-CONFIG_NULL : [chars]: Configuration is unavailable

Explanation

License Configuration is undefined for this platform.

Recommended Action

%IOSXE_LICENSE_POLICY_MANAGER-2-FEATURE_CONFIG_NULL : [chars]: Feature Configuration is unavailable

Explanation

Feature Configuration is undefined for this platform.

Recommended Action

%IOSXE_LICENSE_POLICY_MANAGER-2-FEATURE_MALLOC_FAILED : [chars]: Policy Mgr Feature Registration struct malloc failed

Explanation

Memory allocation for Feature Registration Struct failed

Recommended Action

%IOSXE_LICENSE_POLICY_MANAGER-2-FEATURE_NAME_NULL : [chars]: Feature name is NULL

Explanation

License feature name string is NULL

Recommended Action

%IOSXE_LICENSE_POLICY_MANAGER-2-LIC_REG_FAILED : [chars]: Failed to register [chars] license feature, result = [hex]

Explanation

License Registration failed

Recommended Action

%IOSXE_LICENSE_POLICY_MANAGER-2-LIC_REQ_FAILED : [chars]: [dec]/[dec]: Lic request failed (idx:[dec]), feature=[chars], lic_cnt=[dec],
err=[dec]

Explanation

License Request failed

Recommended Action

%IOSXE_LICENSE_POLICY_MANAGER-2-LIC_REL_FAILED : [chars]: [dec]/[dec]: Lic release failed (idx:[dec]), feature=[chars], lic_cnt=[dec],
err=[dec]

Explanation

License Release failed

Recommended Action

%IOSXE_LICENSE_POLICY_MANAGER-2-LIC_REQ_GEN_FAIL : [chars]: [dec]/[dec]: Lic request failed

Explanation

License Request failed

Recommended Action

%IOSXE_LICENSE_POLICY_MANAGER-2-LIC_REL_GEN_FAIL : [chars]: [dec]/[dec]: Lic request failed

Explanation

License Release failed

Recommended Action

%IOSXE_LICENSE_POLICY_MANAGER-2-BAY_MALLOC_FAILED : [chars]: Policy Mgr Bay DB malloc failed for [dec]/[dec]

Explanation

Memory allocation for SPA/EPA failed

Recommended Action

%IOSXE_LICENSE_POLICY_MANAGER-2-IF_MALLOC_FAILED : [chars]: Policy Mgr IF DB malloc failed for [dec]/[dec]

Explanation

Memory allocation for SPA/EPA interfaces failed

Recommended Action

%IOSXE_LICENSE_POLICY_MANAGER-6-LIC_REQ_SUC : [int]/[int]/[int]: License request is successful for [chars] feature
Explanation	License release is successful, port allowed to go down
Recommended Action	Nothing the system is working properly

%IOSXE_LICENSE_POLICY_MANAGER-6-LIC_REL_SUC : [int]/[int]/[int]: License release is successful for [chars] feature
Explanation	License release is successful, port allowed to go down
Recommended Action	Nothing the system is working properly

%IOSXE_LICENSE_POLICY_MANAGER-4-INSUF_LIC : [int]/[int]/[int]: Insufficient [chars] license, skipping license request assuming customer has honor license
Explanation	Permanent/Evaluation licenses have exhausted, skipping license request asuming customer has purchased license
Recommended Action	Nothing the system is working properly

%IOSXE_LICENSE_POLICY_MANAGER-4-DISABLE_MACSEC : [chars]: Disabling MACsec configuration due to insufficient license
Explanation	Disabling MACsec configuration from port due to insufficient MACsec license
Recommended Action	Purchase/Install MACsec license

IOSXE_MEMPOOL_MIB

%IOSXE_MEMPOOL_MIB-3-BUFFPOOL_REG_ERROR : Bufferpool register data exceeds allocated memory; Retrieved only [dec] entries.

Explanation

Memory allocated is not enough

Recommended Action

IOSXE_MGMTVRF through IOSXE_RP_IF_FLOW_IDS

IOSXE_MGMTVRF
IOSXE_MLP
IOSXE_OIR
IOSXE_PEM
IOSXE_PLATFORM
IOSXE_QFP
IOSXE_RP_ALARM
IOSXE_RP_CFG_NOT
IOSXE_RP_DPIDB
IOSXE_RP_IF_FLOW_IDS

IOSXE_MGMTVRF

%IOSXE_MGMTVRF-3-PROCESS_CREATE_FAIL : Management VRF process creation failed, [chars]

Explanation

Can not create IOS process for mgmt port init

Recommended Action

%IOSXE_MGMTVRF-3-VRF_CREATE_FAIL : Management VRF creation failed [chars]

Explanation

Can not create mgmt vrf during system init

Recommended Action

%IOSXE_MGMTVRF-3-AFI_ATTACH_FAIL : Management VRF AFI [chars] attach failed

Explanation

Can not create afi subblock for mgmt vrf

Recommended Action

%IOSXE_MGMTVRF-3-INTF_ATTACH_FAIL : Management VRF attach to mgmt [chars] failed

Explanation

Can not associate mgmt port to mgmt vrf

Recommended Action

%IOSXE_MGMTVRF-3-SET_TABLEID_FAIL : Installing [chars] Management interface tableid [hex] failed

Explanation

Fail to set mgmt port tableid into Linux kernel

Recommended Action

%IOSXE_MGMTVRF-6-CREATE_SUCCESS_INFO : Management vrf [chars] created with ID [dec], ipv4 table-id [hex], ipv6 table-id [hex]
Explanation	mgmt vrf and ipv4, ipv6 tables created for mgmt port
Recommended Action

IOSXE_MLP

%IOSXE_MLP-3-ENQUEFAIL : Unable to send [chars] [chars] message to Forwarding Manager Process

Explanation

An unexpected condition has occurred which resulted in a configuration not being sent to the Forwarding Manager Processs.

Recommended Action

%IOSXE_MLP-4-UPDSTATSERR : Update MLP statistics error

Explanation

An unexpected condition has occurred when updating mlp statistics

Recommended Action

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

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

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

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

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

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

IOSXE_OIR

%IOSXE_OIR-6-INSCARD : Card ([chars]) inserted in [chars]slot [chars]
Explanation	The OIR facility detected the insertion of a card in the slot number specified in the message.
Recommended Action	No action is required.

%IOSXE_OIR-6-REMCARD : Card ([chars]) removed from [chars]slot [chars]
Explanation	The OIR facility detected the removal of a card from the slot number specified in the message.
Recommended Action	No action is required.

%IOSXE_OIR-6-ONLINECARD : Card ([chars]) online in [chars]slot [chars]
Explanation	The OIR facility detected the state change to online for the card in the slot number specified in the message.
Recommended Action	No action is required.

%IOSXE_OIR-6-OFFLINECARD : Card ([chars]) offline in [chars]slot [chars]
Explanation	The OIR facility detected the state change to offline for the card in the slot number specified in the message.
Recommended Action	No action is required.

%IOSXE_OIR-3-CARDERR : Could not read state property for [chars] slot [dec]
Explanation	The OIR facility detected a failure for exceeding the number of retries to find state chasfs property.
Recommended Action	No action is required.

%IOSXE_OIR-6-SOFT_STARTSPA : SPA([chars]) restarted in [chars]
Explanation	The SPA in the specified subslot is restarted by the command `hw-module subslot` `slot#/subslot#` `start`
Recommended Action	No action is required.

%IOSXE_OIR-3-SPA_INTF_ID_ALLOC_FAILED : Failed to allocate interface identifiers for SPA([chars]) in slot/bay: [int]/[int]
Explanation	Failed to get CC buffer and flow control identifiers for the SPA in the specified subslot Traffic cannot flow through the SPA under this failure condition. This can happen if the system runs out of available identifiers.
Recommended Action	Try to reduce the number of interfaces configured in the system either by physically removing the SPAs or by changing the system configuration

%IOSXE_OIR-6-SOFT_STOPSPA : SPA([chars]) stopped in [chars], interfaces disabled
Explanation	The SPA in the specified subslot is stopped by the command `hw-module subslot` `slot#/subslot#` `stop` The interfaces on that processor will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces.
Recommended Action	No action is required.

%IOSXE_OIR-6-SOFT_RELOADSPA : SPA([chars]) reloaded on [chars]
Explanation	The SPA in the specified subslot is reloaded by the command `hw-module subslot` `slot#/subslot#` `reload`
Recommended Action	No action is required.

%IOSXE_OIR-6-SYNCSPA : SPA ([chars]) reloading to come up in [chars] mode
Explanation	The SPA in the specified subslot is reloaded by the command `hw-module subslot` `slot#/subslot#` `reload`
Recommended Action	No action is required.

%IOSXE_OIR-6-INSSPA : SPA inserted in [chars]/[int]
Explanation	The OIR facility detected the insertion of a SPA in the subslot number specified in the message.
Recommended Action	No action is required.

%IOSXE_OIR-6-REMSPA : SPA removed from [chars]/[int], interfaces disabled
Explanation	The OIR facility detected the removal of a SPA from the subslot number specified in the message. The interfaces on that processor will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces.
Recommended Action	No action is required.

%IOSXE_OIR-6-INSSSFP : Smart SFP inserted in port [chars]
Explanation	The OIR facility detected the insertion of TSoP/VCoP SSFP in the port number specified in the message.
Recommended Action	No action is required.

%IOSXE_OIR-6-REMSSFP : Smart SFP removed from port [chars]
Explanation	The OIR facility detected the removal of TSoP/VCoP SSFP in the port number specified in the message.
Recommended Action	No action is required.

%IOSXE_OIR-6-SPARELOAD : SPA reloaded on subslot [int]/[int]
Explanation	The SPA in the specified subslot is reloaded.
Recommended Action	No action is required.

%IOSXE_OIR-6-CARDRECONCILE : SPA type changed on subslot [int]/[int] from [int] to [int]
Explanation	The SPA in the specified subslot has been initialized, and it has been detected that it is of a different type to the SPA that was previously in this subslot.
Recommended Action	No action is required.

%IOSXE_OIR-3-OIRTWICE : Subslot [int]/[int] OIR insertion/removal not paired up: [chars]

Explanation

An internal OIR-related error occured for the specified SPA.

Recommended Action

%IOSXE_OIR-3-QUIESCE_FAIL : Quiesce failed for subslot [int]/[int] (error = [dec])
Explanation	The RP failed to contact the SPA during failover. The SPA will be reset.
Recommended Action	No action is required.

%IOSXE_OIR-3-UNQUIESCE_FAIL : Unquiesce failed for subslot [int]/[int] (error = [dec])
Explanation	The RP failed to unquiesce the SPA in the specified subslot. The SPA will be reset.
Recommended Action	No action is required.

%IOSXE_OIR-3-POWER_CYCLE_IMMINENT : The SPA in subslot [int]/[int] will be power cycled in [dec] seconds.
Explanation	The SPA in the specified subslot will be power cycled in the amount of time specified in the error message.
Recommended Action	No action is required.

%IOSXE_OIR-3-PROCMSG : Process msg send failed for process[dec]

Explanation

Process message send failed.

Recommended Action

%IOSXE_OIR-3-MODULE : Missing [chars] for [chars]

Explanation

A hardware or software error occurred.

Recommended Action

%IOSXE_OIR-3-SPA_MDR_FAIL : Minimal Disruptive Restart process failed for SPA in subslot [int]/[int], reason [chars].
Explanation	The SPA in the subslot failed Minimal Disruptive Restart. Minimal Disruptive Restart process is aborted and an attempt will be made to recover the SPA by resetting the SPA hardware.
Recommended Action	No action is required.

IOSXE_PEM

%IOSXE_PEM-6-INSPEM_FM : PEM/FM [chars] inserted
Explanation	The platform detected the insertion of a power/fan module in the slot number specified in the message.
Recommended Action	No action is required.

%IOSXE_PEM-6-REMPEM_FM : PEM/FM [chars] removed
Explanation	The platform detected the removal of a power/fan module in the slot number specified in the message.
Recommended Action	No action is required.

%IOSXE_PEM-6-PEMOK : The PEM in [chars] is functioning properly

Explanation

The PEM hardware may have been either switched off, or reporting a failure condition. This message indicates that the PEM
is no longer either switched off, or reporting a failure

Recommended Action

%IOSXE_PEM-3-PEMFAIL : The PEM in [chars] is switched off or encountering a failure condition.

Explanation

The PEM hardware has been either switched off, or is reporting a failure condition.

Recommended Action

%IOSXE_PEM-6-FANOK : The fan in [chars]/[dec] is functioning properly

Explanation

The fan was reporting a failure condition. This message indicates that the fan is no longer reporting a failure

Recommended Action

%IOSXE_PEM-3-FANFAIL : The fan in [chars]/[dec] is encountering a failure condition

Explanation

The fan’s hardware is reporting that the fan is failing. This is most likely because the hardware detects the fan as spinning
below the minimum speed.

Recommended Action

%IOSXE_PEM-3-PEMCHASFSERR : The PEM in [chars] has encountered a system software error.

Explanation

The PEM’s underlying software for storing PEM state is not working properly.

Recommended Action

%IOSXE_PEM-3-TEMPERATURE_RAISE : Sensor [chars] has reached maximum temeprature value, Leads to shutdown the system

Explanation

The Temperature sensor reaching maximum threshold value working properly.

Recommended Action

%IOSXE_PEM-3-FAN_FAIL_SHUTDOWN : More thatn one [chars] has failed, Leads to shutdown the system

Explanation

The Temperature sensor reaching maximum threshold value working properly.

Recommended Action

%IOSXE_PEM-3-SSFP_TEMPERATURE_RAISE : [chars] transceiver temeprature reached threshold value, Leads to shutdown the system

Explanation

The Temperature sensor reaching maximum threshold value working properly.

Recommended Action

%IOSXE_PEM-3-PEMREDLOWSTANDBY : Cannot activate [chars] configuration. Total power budget of standby power supplies is [dec]W.
Standby power must be greater than or equal to the largest power supply capacity ([dec]W).

Explanation

Operating in unprotected mode Should insert at least one ps in standby slots with a capacity greater than or equal to the
largest capacity power supply in the system. The configuration will be applied automatically once requirements are met.

Recommended Action

%IOSXE_PEM-3-PEMREDNOPWR : Cannot enable power redundancy mode [chars] because config would create mode with insufficient [chars] power
Explanation	Configuration set by user is not valid as power supplies in the active slots do not contain enough power to meet the power requirements
Recommended Action	Insert additional power supplies and configure them to be active or configure current standby power supplies to active such that power requirements are met

IOSXE_PLATFORM

%IOSXE_PLATFORM-3-WDC_INVALID_LENGTH : WDC length can not be determined: [dec]
Explanation	WDC length was not retrieved properly
Recommended Action	Check if WDC is programmed on this device

%IOSXE_PLATFORM-3-WDC_NOT_FOUND : WDC returned length: [dec]
Explanation	WDC length was set to 0, which specifies probably WDC does not exist
Recommended Action	Check if WDC is programmed on this device

%IOSXE_PLATFORM-3-WDC_TLV_NOT_FOUND : WDC TLV could not be read from the Quack device
Explanation	WDC TLV couldn’t be read from the Quack device
Recommended Action	Check if WDC is programmed on this device

IOSXE_QFP

%IOSXE_QFP-2-LOAD_EXCEED : Slot: [int], QFP:[int], Load [int]%[hex]ceeds the setting threshold.
Explanation	QFP Load exceeds setting threshold.
Recommended Action	Monitor the traffic load.

%IOSXE_QFP-2-LOAD_RECOVER : Slot: [int], QFP:[int], Load [int]%% recovered.
Explanation	QFP Load recovered.
Recommended Action	No action required (normal operation).

IOSXE_RP_ALARM

%IOSXE_RP_ALARM-6-INFO : [chars] [chars] [chars]: [chars] [chars]
Explanation
Recommended Action

%IOSXE_RP_ALARM-6-INFO : [chars] [chars] [chars] [chars] [chars]
Explanation	Alarm assertion or deassertion information.
Recommended Action	No action is required.

%IOSXE_RP_ALARM-2-PEM : [chars] [chars] [chars]: [chars] [chars]
Explanation
Recommended Action

%IOSXE_RP_ALARM-2-PEM : [chars] [chars] [chars] [chars] [chars]
Explanation	Power Entity Module missing information
Recommended Action	No action is required.

%IOSXE_RP_ALARM-2-ESP : [chars] [chars] [chars]: [chars] [chars]
Explanation
Recommended Action

%IOSXE_RP_ALARM-2-ESP : [chars] [chars] [chars] [chars] [chars]
Explanation	No ESP running alarm information
Recommended Action	No action is required.

IOSXE_RP_CFG_NOT

%IOSXE_RP_CFG_NOT-3-MSGNOCAND : Can not construct a candidate entry for configuration export

Explanation

This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the the
TDL error may indicate a version conflict with respect to configuration.

Recommended Action

%IOSXE_RP_CFG_NOT-3-MSGNOPWARR : Can not construct an array for configuration export

Explanation

This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the the
TDL error may indicate a version conflict with respect to configuration.

Recommended Action

%IOSXE_RP_CFG_NOT-3-MSGNOUPDATEMSG : Can not construct an update message for configuration export

Explanation

This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the the
TDL error may indicate a version conflict with respect to configuration.

Recommended Action

%IOSXE_RP_CFG_NOT-3-MSGNOREPLMSG : Can not construct a replace message for configuration export

Explanation

This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the the
TDL error may indicate a version conflict with respect to configuration.

Recommended Action

%IOSXE_RP_CFG_NOT-2-MSGNOEXP : Can not construct a ‘[chars]’ message for configuration export: [chars]

Explanation

This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the the
TDL error may indicate a version conflict with respect to configuration.

Recommended Action

%IOSXE_RP_CFG_NOT-2-MSGTDLINITERROR : Configuration Notification messaging module initialization failed: Unable to initialize
messaging: [chars]

Explanation

The Configuration Notification subsystem has failed to initialize the infrastructure for messaging with the Pluggable Services
Daemon. Notification of configuration to critical modules cannot proceed.

Recommended Action

%IOSXE_RP_CFG_NOT-2-MSGTDLERROR : Error processing TDL message. [dec]

Explanation

An unexpected condition in which IOS has received a TDL message which it can not process.

Recommended Action

%IOSXE_RP_CFG_NOT-2-MSGIPCINITERROR : Error initializing IPC queue

Explanation

An unexpected condition in which IOS could not initialize a message queue to the PSD.

Recommended Action

%IOSXE_RP_CFG_NOT-3-MSGIPCTXERROR : IPC transmit error. [dec]

Explanation

An unexpected condition in which IOS encountered an error trying to send a message to another process. %d

Recommended Action

%IOSXE_RP_CFG_NOT-3-MSGOBJNULL : An unexpected condition in which IOS has received a null pointer that it expects to be non-null.

Explanation

An unexpected condition has occurred while IOS is trying to process a username command.

Recommended Action

%IOSXE_RP_CFG_NOT-3-MSGENCRYPTINVALID : The mcprp_cfg_notify subsystem has seen an encryption type it does not recognize.
[dec]

Explanation

An unexpected condition has occurred while IOS is trying to process a username command.

Recommended Action

%IOSXE_RP_CFG_NOT-3-NVWRITE_EXPORT : Failed to export [chars] notification: [dec]

Explanation

When a ‘write memory’ or ‘write erase’ operation occurs, the Configuration Notification subsystem exports this event into
the chassis file system. This message indicates that the export failed.

Recommended Action

%IOSXE_RP_CFG_NOT-3-MCP_DBPERSIST_STAT : Failed to read [chars] property: [dec]

Explanation

When a ‘reload’ operation occurs, this chasfs property is read to determine the status of the DB persist/restore/delete operation.
This message indicates that the read failed.

Recommended Action

%IOSXE_RP_CFG_NOT-3-MCP_DBPERSIST_ERROR : System configuration update could not complete

Explanation

When a ‘reload’ operation occurs, this chasfs property is read to determine the status of the DB persist/restore/delete operation.
This message indicates that the operation failed.

Recommended Action

%IOSXE_RP_CFG_NOT-3-MCP_FRU_LOCATION : Failed to get local FRU location: [dec]

Explanation

Unable to get local FRU location

Recommended Action

%IOSXE_RP_CFG_NOT-3-MCP_FRU_INVALID : Unknow FRU location: [chars]

Explanation

Unknown FRU location

Recommended Action

%IOSXE_RP_CFG_NOT-3-BOOT_VAR_NOT_SET : Boot variable either does not exist or buffer is too small. Keeping it blank.

Explanation

Boot variable either does not exist or buffer is too small. Not able to set boot variable. Ignoring it.Aborting reload.

Recommended Action

%IOSXE_RP_CFG_NOT-3-BOOT_IMAGE_NOT_FOUND : Primary image is not found, the system is going to reload as per user request.

Explanation

Primary image which is set in boot statement either does not exist or not found. Primary image is not found, it should prompt
the user to see if they wish to proceed. Aborting reload.

Recommended Action

%IOSXE_RP_CFG_NOT-6-IOX_SERVICE_NOTSUPPORTED : IOx service not supported.
Explanation	IOx service is not supported in this platform currently. This may be either due to the feature unavailability or due the current inadequate license level of the system.
Recommended Action

IOSXE_RP_DPIDB

%IOSXE_RP_DPIDB-3-IDXBADRANGE : Datapath IDB index [dec] is not in a valid range

Explanation

An unexpected condition has occurred as the index of a datapath IDB is not valid.

Recommended Action

%IOSXE_RP_DPIDB-3-IDXALLOCFAILED : Datapath IDB index allocation failed: [chars]

Explanation

An unexpected condition has occurred as all the available of datapath IDB indices are used.

Recommended Action

%IOSXE_RP_DPIDB-3-IDXINSERTFAILED : Insertion of datapath IDB index [dec] into database failed

Explanation

An unexpected condition has occurred that insertion of datapath IDB indices failed.

Recommended Action

%IOSXE_RP_DPIDB-3-IDXLOOKUPFAILED : Lookup of datapath IDB index from the database failed ([chars])

Explanation

An unexpected condition has occurred that lookup of datapath IDB indices failed.

Recommended Action

%IOSXE_RP_DPIDB-3-IDXDELETIONFAILED : Deletion of datapath IDB index from the database failed ([chars] — [hex]) rc [dec]

Explanation

An unexpected condition has occurred that deletion of datapath IDB indices failed.

Recommended Action

%IOSXE_RP_DPIDB-3-NOHWSUBBLOCK : HWIDB [chars] does not have a hardware subblock

Explanation

An unexpected condition has occurred that no hardware subblock was previously allocated for a HWIDB.

Recommended Action

%IOSXE_RP_DPIDB-3-NOSWSUBBLOCK : SWIDB [chars] does not have a software subblock

Explanation

An unexpected condition has occurred that no software subblock was previously allocated for a SWIDB.

Recommended Action

%IOSXE_RP_DPIDB-3-IDBBADTYPE : Datapath IDB type [dec] is not valid

Explanation

An unexpected condition has occurred as the type of a datapath IDB is not valid.

Recommended Action

%IOSXE_RP_DPIDB-3-IDBEXIST : Datapath IDB already exists in this mapping entry: [chars]-[dec]

Explanation

An unexpected condition has occurred that an attempt is made to save datapath IDB in a mapping entry filled by another.

Recommended Action

%IOSXE_RP_DPIDB-3-IDBNONEXIST : Datapath IDB does not exist in this mapping entry: [chars]-[dec]

Explanation

Datapath IDB lookup points to empty mapping entry.

Recommended Action

%IOSXE_RP_DPIDB-3-RF : Datapath IDB RF operation failed — [chars]

Explanation

Failure in some datapath ID RF activity.

Recommended Action

%IOSXE_RP_DPIDB-3-CF : Datapath IDB CF operation failed — [chars]

Explanation

Failure in some datapath ID CF activity.

Recommended Action

%IOSXE_RP_DPIDB-3-RPC : Datapath IDB RPC operation failed — [chars]

Explanation

Failure in some datapath ID RPC activity.

Recommended Action

%IOSXE_RP_DPIDB-3-REGISTRATION : ISSU [chars] failed for [chars]; [chars]

Explanation

An ISSU registration for the set of initial capabilities and sessions failed due to the reason specified. This will have the
effect of the DPIDX ISSU support being unavailable between peers.

Recommended Action

%IOSXE_RP_DPIDB-3-ISSU : [chars] [chars] failed; [chars]

Explanation

An operation pertaining to the ISSU support for DPIDX failed to complete using either the CF or IPC transport context with
the reason specified

Recommended Action

%IOSXE_RP_DPIDB-3-TRANSFORM : [chars] of [chars] via [chars] failed for dpidx [int]

Explanation

An attempt to either encode or decode a versioned synchronization message has failed due to an internal error encountered
by the ISSU component.

Recommended Action

%IOSXE_RP_DPIDB-3-RECEIVE : Message via [chars] is [chars]

Explanation

An attempt to receive and process a versioned negotiation or synchronization message has failed due to an internal error being
detected by the information received from the IPC or CF components.

Recommended Action

%IOSXE_RP_DPIDB-3-TRANSMIT : Unable to send via [chars] [chars] [chars] [chars]; [chars]

Explanation

An attempt to send a versioned negotiation or synchronization message has failed due to an internal error encountered by the
IPC or CF components.

Recommended Action

%IOSXE_RP_DPIDB-3-NEGOTIATION : Failed to start ISSU [chars] session negotiation; [chars]

Explanation

The ISSU negotiation with the peer failed to start for either the CF or IPC transport with the reason specified.

Recommended Action

%IOSXE_RP_DPIDB-6-READY : [chars] peer not ready, discarding [chars]
Explanation	The synchronization attempt for the message has determined that the transport has lost communication with its peer. This is a normal situation which indicates that the standby route-processor is currently out of service implying a simplex redundancy mode.
Recommended Action

%IOSXE_RP_DPIDB-6-RELOAD : [chars], reloading [chars]

Explanation

A synchronization attempt between the active and standby RP peers has failed with the reason indicated. The standby peer is
reloaded in an attempt to resynchronize when operating in a stateful redundant mode.

Recommended Action

%IOSXE_RP_DPIDB-3-DECODE : Decode via [chars] of [chars] failed

Explanation

A message of the transport and type described failed in its attempt to be decoded on the standby. The resultant action taken
by the standby route processor is an attempt to resynchronize.

Recommended Action

%IOSXE_RP_DPIDB-3-PROGRESSION : Unable to inform RF of bulk sync completion; [chars]

Explanation

The active route processor has sent a notification to the standby to inform of the completion of the bulk synchronization
of the DPIDX configuration. The standby has failed to respond to the active informing that it received the notification noting
the reason for the failure. The resultant action taken by the standby route processor is an attempt to resynchronize.

Recommended Action

%IOSXE_RP_DPIDB-3-BULK_SYNC : Failed to send [chars] information to peer

Explanation

The bulk synchronization of the DPIDX configuration to the standby RP has failed to complete successfully; DPIDX has therefore
taken the action which will result in a reload of the peer in order to once more attempt to successfully synchronize the configuration
state which may have failed initially to a transient condition.

Recommended Action

%IOSXE_RP_DPIDB-3-DYN_SYNC : Failed to process [chars] dynamic state

Explanation

The incremental synchronization of the DPIDX configuration to the standby RP has failed to complete successfully. This implies
that the configuration state between the active and standby RP is inconsistent.

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show interfaces 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.

%IOSXE_RP_DPIDB-6-TIMEOUT : Bulk sync is flow controlled by [chars]

Explanation

The bulk synchronization of the DPIDX configuration to the standby RP has encountered a flow control condition which has effected
a timeout awaiting the condition to clear. This will result in a reload of the standby RP to allow the bulk synchronization
to restart.

Recommended Action

%IOSXE_RP_DPIDB-3-IDBNOTVAI : Invalid API call for [chars]

Explanation

Failure in an internal API

Recommended Action

%IOSXE_RP_DPIDB-3-NULLTIMER : NULL timer

Explanation

A timer is NULL

Recommended Action

%IOSXE_RP_DPIDB-3-LIST : List [chars] failed for [chars]

Explanation

List enqueue or removal failed

Recommended Action

%IOSXE_RP_DPIDB-3-FASTNOTIFY : Fast notify failed for [chars]

Explanation

A fast notify message failed

Recommended Action

%IOSXE_RP_DPIDB-3-DOWNLOADFAIL : Unable to download [chars] message to [chars]

Explanation

An unexpected condition has occurred which resulted in a configuration not being sent to the reported process.

Recommended Action

%IOSXE_RP_DPIDB-3-FRRLDFLOWIDDELETIONFAILED : Deletion of fast-reroute flow ID with manager failed

Explanation

An unexpected condition has occurred that deletion of fast-reroute flow ID.

Recommended Action

%IOSXE_RP_DPIDB-3-EFPSTATSFAILED : EFP stats message data get error: ([dec]) for EFP [int] on [chars]

Explanation

An unexpected error occurred extracting fields from an EFP stats message.

Recommended Action

%IOSXE_RP_DPIDB-3-MTU_ALLOC_FAIL : No hardware resources for [int] byte MTU on [chars]
Explanation	We reached to the threshold of maximum supported unique MTU on this platform.
Recommended Action	No action is required.

%IOSXE_RP_DPIDB-3-IP_MTU_ALLOC_FAIL : No hardware resources for [int] byte IP MTU on [chars]
Explanation	We reached to the threshold of maximum supported unique IP MTU on this platform.
Recommended Action	No action is required.

IOSXE_RP_IF_FLOW_IDS

%IOSXE_RP_IF_FLOW_IDS-3-NO_BUFF_FOR_SYNC : The Checkpoint Faclity reported the error [chars] during a request for a buffer
length of [dec]. This [chars] CF client has failed to synchronize a transaction to the Standby RP.

Explanation

This error indicates that the buffer management within the Checkpoint Facility has either run out of buffers, or has some
other problem. If this occurs during Bulk Sync then Bulk Sync will terminate without completing. Otherwise the incremental
Sync will fail.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-BUFF_OFFSET_NULL : Unable to utilize the memory buffer provided by the Checkpoint Facility. This
[chars] CF client has failed to Bulk Sync.

Explanation

This error indicates the Checkpoint Facility is having problems recognizing its own buffer layout. If this occurs during Bulk
Sync then Bulk Sync will terminate without completing. Otherwise the incremental Sync will fail.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-CF_SEND_BULK_NONBLOCKED : The Checkpoint Facility reported the error [chars] while attempting to
send a message. Bulk Sync of this [chars] CF client is terminating.

Explanation

This error indicates the Checkpoint Facility has internal problems related to IPC, and cannot perform a non-blocked send operation.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-DEFERRED_DURING_BULK_SYNC : Encountered error [chars] while trying to place an [chars] transaction
on the Deferred list during Bulk Sync for the [chars] CF client.

Explanation

Unable to cache a deferred transaction while Bulk Sync is underway. This can adversely impact SSO state on the Standby RP.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-CF_SEND_INCR_NONBLOCKED : The Checkpoint Facility reported the error [chars] while attempting to
send a non-blocked message. The Incremental Sync transaction for this [chars] CF client cannot be sent to the Standby RP.

Explanation

This error indicates the Checkpoint Facility has internal problems related to IPC.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-6-CFPEER_CANNOT_RECV : The Checkpoint Peer is not ready to receive messages. The Incremental Sync transaction
for this [chars] CF client will not occur.

Explanation

This error indicates the Checkpoint Facility has signalled the peer has gone away.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-SEND_FAIL_RELOAD : Checkpoint Facility Failed to send a [chars] transaction for this [chars] CF client.
Reloading the Standby RP.

Explanation

This indicates the underlying Checkpoint Facility could not deliver a message sent from the active RP to the standby RP. The
process will automatically reload the standby RP.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-4-DEF_LIST_REMOVE : Failed to remove one entry from the Deferred Sync list, for the [chars] CF client.

Explanation

An unexpected condition occured during list maintenance.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-CF_CANNOT_REGISTER : The call to add this [chars] CF client to the Checkpoint Facility failed with
the error [chars]. This client is unable to proceed and will not be registered.

Explanation

For some reason the Checkpoint Facility will not register this client. As a result the Standby will never receive synchronized
state from this CF client on the Active RP, The system is not capable of SSO and HA switchover.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-RF_PEER_EVENT_BUFFER : This [chars] RF client is unable to acquire an event buffer to send an RF
peer message, the error [chars] was returned.

Explanation

This indicates the RF facility is unable to provide a message buffer needed to communicate with the RF peer. As a consequence
the RF progression may be compromised.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-RF_SEND_PEER : This [chars] RF client encountered error [chars], when attempting to send a peer message.

Explanation

This indicates the RF facility could not send a message to the RF peer. As a consequence the RF progression may be compromised.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-RF_PROCESS_FAILED : This [chars] RF client Failed to create the Bulk Sync Process.

Explanation

The background process which performs the RF Bulk Sync failed to be created. As a consequence the Standby will never obtain
the relevent SSO state to enable HA switchover.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-RF_POOL_REGEN_PROCESS_FAILED : The [chars] RF client Failed to create the Id Pool Regeneration process.

Explanation

The background process which performs Flow Control Id Pool regeneration failed to start. As a consequence the Standby will
never obtain the relevent SSO state to enable HA switchover.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-RF_POOL_REGEN_ERROR : Id Pool Regeneration encountered error code [dec], cannot switchover.

Explanation

The background process which performs Flow Control Id Pool regeneration encountered an error. As a consequence the Standby
does not have valid Flow Id pools and cannot progress to Active state.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-RF_SPA_ID_REGEN_ERROR : Error code [dec] encountered trying to regenerate spa [chars] identifier
in slot/subslot ([int]/[int])

Explanation

The background process which performs Flow Control Id Pool regeneration encountered an error. As a consequence the Standby
does not have valid Id pools and cannot progress to Active state.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-RF_IF_ID_REGEN_ERROR : Error code [dec] encountered trying to regenerate interface flow-control identifer.
If id [int] resides in slot/subslot/port ([int]/[int]/[int]).

Explanation

The background process which performs Flow Control Id Pool regeneration encountered an error. As a consequence the Standby
does not have valid Id pools and cannot progress to Active state.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-RF_ADD_CLIENT_FAILED : The RF facility failed to add this [chars] client, reason given is [chars].

Explanation

This indicates the RF facility could not add the client.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-REGISTRATION : ISSU [chars] failed for [chars]; [chars]

Explanation

An ISSU registration for the set of initial capabilities and sessions failed due to the reason specified. This will have the
effect of the SPA MARMOT ID ISSU support being unavailable between peers.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-ISSU_OP : [chars] [chars] failed; [chars]

Explanation

An operation pertaining to the ISSU support for SPA MARMOT IDs failed to complete using the CF transport context with the
reason specified

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-TRANSFORM : [chars] of [chars] via CF failed

Explanation

An attempt to either encode or decode a versioned synchronization message has failed due to an internal error encountered
by the ISSU component.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-TRANSMIT : Unable to send via [chars] [chars] [chars] [chars]; [chars]

Explanation

An attempt to send a versioned negotiation or synchronization message has failed due to an internal error encountered by the
CF component.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-NEGOTIATION : Failed to start ISSU [chars] session negotiation; [chars]

Explanation

The ISSU negotiation with the peer failed to start for either the CF or IPC transport with the reason specified.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-6-READY : [chars] peer not ready, discarding [chars]
Explanation	The synchronization attempt for the message has determined that the transport has lost communication with its peer. This is a normal situation which indicates that the standby route-processor is currently out of service implying a simplex redundancy mode.
Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-DECODE : Decode via CF of [chars] failed

Explanation

A message sent via the CF transport failed in its attempt to be decoded on the standby. The resultant action taken by the
standby route processor is an attempt to resynchronize.

Recommended Action

%IOSXE_RP_IF_FLOW_IDS-3-RECEIVE : Client reports message CF is [chars]

Explanation

An attempt to receive and process a versioned negotiation or synchronization message has failed due to an internal error being
detected by the information received from the CF component.

Recommended Action

IOSXE_RP_MGMTE through IOSXE_TIMESTAMP_ENGINE

IOSXE_RP_MGMTE
IOSXE_RP_NV
IOSXE_RP_SPA
IOSXE_RP_VTYMGT
IOSXE_SERVICE_ENGINE
IOSXE_SIP_SPA
IOSXE_SPA
IOSXE_SYS_INFRA
IOSXE_THROUGHPUT
IOSXE_TIMESTAMP_ENGINE

IOSXE_RP_MGMTE

%IOSXE_RP_MGMTE-3-MSGCREATENULL : Cannot allocate [chars] TDL message

Explanation

An unexpected condition in which IOS cannot allocate TDL message for Management ethernet.

Recommended Action

%IOSXE_RP_MGMTE-3-MSGTDLINITERROR : Management ethernet interface messaging module initialization failed: Unable to initialize
messaging: [chars]

Explanation

The Management ethernet interface subsystem has failed to initialize the infrastructure for messaging with the Pluggable Services
Daemon. Configuration of management ethernet modules cannot proceed.

Recommended Action

%IOSXE_RP_MGMTE-3-PROCESS_CREATE_FAIL : Management ethernet statistics process creation failed

Explanation

Can not create IOS process for RP management ethernet port statistics collection

Recommended Action

%IOSXE_RP_MGMTE-3-MGMT_MAC_MODIFY_FAIL : Management ethernet interface mac address modification failed

Explanation

Can not override mac-address for management ethernet interface

Recommended Action

IOSXE_RP_NV

%IOSXE_RP_NV-3-NV_ACCESS_FAIL : Initial read of NVRAM contents failed
Explanation	This error happens when the contents of the NVRAM cannot be read during system initialization. The failure may be due to data corruption of the NVRAM contents. The initial configuration dialog will be entered and the configuration must be restored.
Recommended Action	LOG_STD_ACTION

%IOSXE_RP_NV-3-BACKUP_NV_ACCESS_FAIL : Initial read of backup NVRAM contents failed
Explanation	This error happens when the contents of the backup NVRAM cannot be read during system initialization. The failure may be due to data corruption of the backup NVRAM contents. The primary nvram contents will be backed up here again.
Recommended Action	LOG_STD_ACTION

IOSXE_RP_SPA

%IOSXE_RP_SPA-3-SEND_NGIO_MSG_FAIL : NGIO Module message send failed for slot [dec] subslot [dec]

Explanation

Failed to send ngio msg to iomd.

Recommended Action

%IOSXE_RP_SPA-3-MAC_FILTER_ADD_FAIL : All the available [dec] mac filters for [chars] have been consumed. Failed to add [enet] for interface [chars]
Explanation	The hardware cannot support any more filters.
Recommended Action	The interface configuration should be reworked to not cross the limit set by the hardware. If the error is still seen please LOG_STD_SH_TECH_ACTION

%IOSXE_RP_SPA-3-SEND_L2_HDR_MSG_FAIL : slot [dec] subslot [dec]

Explanation

Failed to send ngio L2 header to iomd.

Recommended Action

%IOSXE_RP_SPA-3-NO_HOST_INFO : slot [dec] subSlot [dec], spaType [hex]

Explanation

Failed to get information about the host linecard.

Recommended Action

%IOSXE_RP_SPA-3-MAX_SPA : Power to IPSEC-SPA-2G in [chars] is denied because it has exceeded the number allowed([dec])
Explanation	The number of IPSEC-SPA-2G in a chassis is limited. This message is displayed when the number of IPSEC-SPA-2G in the chassis has exceeded this limit.
Recommended Action	Use only the number of supported IPSEC-SPA-2G

%IOSXE_RP_SPA-3-SPA_NO_HOST_INFO : slot [dec] subSlot [dec], PID [chars]

Explanation

Failed to get information about the host linecard.

Recommended Action

%IOSXE_RP_SPA-3-HWIDB_FAILURE : Creation: slot [dec] subSlot [dec] port [dec] vc [dec]

Explanation

Failed to create an interface hwidb.

Recommended Action

%IOSXE_RP_SPA-3-INVALID_PORT_NUM : slot=[dec] port=[dec], hwidbType=[hex], max_port_num=[dec], LCtype=[hex]

Explanation

The port number is out of range.

Recommended Action

%IOSXE_RP_SPA-4-SPA_RESP_CMD_MISMATCH : [chars]: Expecting response to interface configuration command [int] but received response to command [int].
Explanation	An internal synchronization error occurred while configuring the interface. The configuration may not have succeeded.
Recommended Action	Check that the running configuration for the interface is correct. If this message occurred on the standby, try reloading the standby to ensure that its configuration is in sync. If this message is repeatable, please LOG_STD_SH_TECH_ACTION

%IOSXE_RP_SPA-6-CARDRELOAD : Module [int] reload due to SPA insert in [int]/[int].
Explanation	When inserting a SPA on this carrier card, the card is reset.
Recommended Action	No action is required.

%IOSXE_RP_SPA-6-CTRLRSWITCH : switching controller type from [chars]([dec]) to [chars]([dec]) for subslot [int]/[int].
Explanation	When IOSXE-SIP40 is inserted in the slot previously occupied by IOSXE-SIP10 or vice-versa the controller type of the card is overwritten to reflect the current SIP.
Recommended Action	No action is required.

%IOSXE_RP_SPA-4-SPA_CMD_NO_RESP : [chars]: No response for interface configuration command [int]
Explanation	A timeout occurred while RP was waiting for a response from line card. This may happen due to line card CPU being too busy to respond to the command.
Recommended Action	No action is required.

%IOSXE_RP_SPA-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]

Explanation

The RP failed to allocate a buffer for communication with a SPA

Recommended Action

%IOSXE_RP_SPA-3-DPIDX_LKUP_FAIL : Failed to retrieve datapath identifier for interface [chars]
Explanation	The SPA driver is not able to retrieve the datapath identifier for the interface specified in the message. This indicates a software error.
Recommended Action	No action is required.

%IOSXE_RP_SPA-3-FLOWID_ALLOC_FAIL : Failed to allocate a flow control identifier for interface [chars]
Explanation	The SPA driver is not able to allocate the datapath flow control identifier for the interface specified in the message. This indicates a software error.
Recommended Action	No action is required.

%IOSXE_RP_SPA-3-FLOWID_RELEASE_FAIL : Failed to release a flow control identifier for interface [chars] (status = [dec])
Explanation	The SPA driver is not able to release the datapath flow control identifier for the interface specified in the message. This indicates a software error.
Recommended Action	No action is required.

%IOSXE_RP_SPA-3-VC_PROV_FAIL : Failed to provision interface [chars]
Explanation	The SPA driver is not able to provision the interface specified in the message. Verify that the SPA hardware is not provisioned above the supported limit. Otherwise, this indicates a hardware error.
Recommended Action	No action is required.

%IOSXE_RP_SPA-3-CI_UPDATE_FAIL : Failed to update connection identifier for interface [chars]
Explanation	The SPA driver is not able to update the datapath connection identifier for the interface specified in the message. This indicates a software error.
Recommended Action	No action is required.

%IOSXE_RP_SPA-3-NULL_DATA_STRUCTURE : common_str_empty_str
Explanation	A SPA driver is not able to retrieve the data structure mentioned in the message. This indicates a software error.
Recommended Action	No action is required.

%IOSXE_RP_SPA-3-HWIDB_INIT_FAIL : Failed to initialize data structure for SPA port [dec]/[dec]/[dec]
Explanation	A SPA driver was not able to properly initialize a data structure mentioned in the message. This indicates a software error.
Recommended Action	No action is required.

%IOSXE_RP_SPA-3-ERROR : common_str_empty_str

Explanation

This message can take many forms. It provides information about a software error.

Recommended Action

%IOSXE_RP_SPA-4-LCLOG_TOOLONG : Message too long from slot [int]/[int]: [int] bytes

Explanation

The SPA module passed down a logger message that is too long for the RP to handle.

Recommended Action

%IOSXE_RP_SPA-4-LCLOG_PARSE_ERR : Error parsing logger message: [chars] from subslot [int]/[int]

Explanation

The SPA module passed down a logger message that could not be parsed.

Recommended Action

%IOSXE_RP_SPA-3-BAD_IFCOMTYPE : Bad ifcom message type=[int]

Explanation

A SPA module passed down a message that the RP software was not prepared to handle.

Recommended Action

%IOSXE_RP_SPA-4-IPCFAILED : IPC failed to send RPC message to SPA module
Explanation	The RP failed to send an RPC message via IPC to a SPA module.
Recommended Action	No action is required.

%IOSXE_RP_SPA-3-FOREVER : cmd [int] to [chars] (slot [int]/[int]) took [int]secs, done [hex]

Explanation

A CCB command from the RP to a SPA module took longer than expected.

Recommended Action

%IOSXE_RP_SPA-4-SEMAHOG : Process [dec] ([chars]) hogging [chars]! calling proc [dec] ([chars])
Explanation	The RP waited too long for a reply to a command sent to a SPA module.
Recommended Action	No action is required.

%IOSXE_RP_SPA-3-IPCPORTFAIL : Failed to open IPC port ‘[chars]’ with error [chars]

Explanation

The RP failed to open a port for communication with a SPA module.

Recommended Action

%IOSXE_RP_SPA-4-CCB_PLAYBACK_ERROR : CCB playback failed for slot [dec].
Explanation	The High Availability component for SPA modules failed to synchronize some new state information for the specified slot.
Recommended Action	Reload the standby supervisor module to force a fresh bulk synchronization. If this error recurs, LOG_STD_ACTION

%IOSXE_RP_SPA-4-CCB_RECORD_ERROR : CCB record failed for slot [dec].

Explanation

The High Availability component for SPA modules failed to record some new state information for the specified slot.

Recommended Action

%IOSXE_RP_SPA-3-IPCSENDFAIL : Failed to send IPC message [chars]

Explanation

The RP failed to send a message to a SPA module.

Recommended Action

%IOSXE_RP_SPA-3-IFCFG_NO_UNIQUE_KEY : No unique-key generator registered for interface configuration command [int].

Explanation

The High Availability component for SPA modules is unable to properly synchronize state information for the current configuration.

Recommended Action

%IOSXE_RP_SPA-3-IFCFG_FOREVER : to [chars] (slot [int]/[int]) took [int]secs, ret_val [int]

Explanation

A interface config command from the RP to a SPA module took longer than expected.

Recommended Action

%IOSXE_RP_SPA-4-IFCFG_CMD_TIMEOUT : Interface configuration command ([hex]) to slot [int]/[int] timed out

Explanation

The RP sent an configuration command to the slot specified in the error message and received no confirmation for the command.

Recommended Action

%IOSXE_RP_SPA-3-IFCFG_CMD_NOT_OWNER : Process ‘[chars]’ waiting for interface configuration command ([hex]) to slot [int]/[int]
without acquiring lock owned by process ‘[chars]’

Explanation

A process on the RP sent an configuration command to the slot specified in the error message and a different process waited
for the result. This could cause incorrect line card configuration states.

Recommended Action

%IOSXE_RP_SPA-4-IFCFG_DFLT_LIST_ERROR : For Interface Configuration command [int], default retval list search resulted [hex] for slot [int]/[int]
Explanation	The High Availability component for SPA modules failed to synchronize some new state information for the specified slot.
Recommended Action	LOG_STD_SH_CMD_ACTION(show platform redundancy if-config default-retvals)

%IOSXE_RP_SPA-4-IFCFG_PLAYBACK_ERROR : Interface Configuration command [int] playback failed for slot [int]/[int].

Explanation

The High Availability component for SPA modules failed to synchronize some new state information for the specified slot.

Recommended Action

%IOSXE_RP_SPA-4-IFCFG_RECORD_ERROR : Interface Configuration command [int] record failed for slot [int]/[int].

Explanation

The High Availability component for SPA modules failed to record some new state information for the specified slot.

Recommended Action

%IOSXE_RP_SPA-4-INCR_CFG_SYNC_FAIL : [chars] incremental running-config sync for [[dec]/[dec]] failed — [chars]([dec]) , Reload Standby
Explanation	The specified IOSXE incremental running-config sync failed
Recommended Action	Power cycle the redundant supervisor

%IOSXE_RP_SPA-3-IPCPORT : Failed to [chars] IPC port ‘[chars]’, error [chars]
Explanation	The Linecard failed to create a port for communication with the Route Processor (IOSXE-RP).
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IOSXE_RP_SPA-3-PROGRESSION : Unable to inform RF of bulk sync completion; [chars]

Explanation

The standby has failed to notify the active that its bulks synchronization of the SPA TSM has completed. The resultant action
taken by the standby route processor is an attempt to resynchronize.

Recommended Action

%IOSXE_RP_SPA-3-VC_FLOWID_ALLOC_FAIL : Failed to allocate a flow control identifier for VC [dec] under interface [chars]
Explanation	The SPA driver is not able to allocate the datapath flow control identifier for the VC/interface specified in the message. This indicates a software error.
Recommended Action	No action is required.

%IOSXE_RP_SPA-3-VC_INGID_ALLOC_FAIL : Failed to allocate a ingress identifier for VC [dec] interface [chars]
Explanation	The SPA driver is not able to allocate the datapath ingress identifier for the VC/interface specified in the message. This indicates a software error.
Recommended Action	No action is required.

%IOSXE_RP_SPA-4-SPA_RESP_CMD_ERR : [chars]: Received response to interface configuration command [chars] with wrong return value [int].
Explanation	An internal error occurred while configuring the interface. The configuration may not have succeeded.
Recommended Action	Check that the running configuration for the interface is correct. If this message is repeatable, please LOG_STD_SH_TECH_ACTION

%IOSXE_RP_SPA-3-FRR_CFG_REC_FAIL : Failed to record fast reroute conifguration on [chars]: [chars]

Explanation

This message is displayed when a fast reroute configuration is not properly recorded.

Recommended Action

%IOSXE_RP_SPA-3-MISSING_SPA_PKG_ERR : sipspa[chars] package is not installed for slot = [dec] and subslot = [dec], SPA bootup failed.
Explanation	This message is displayed when attempting to bootup a SPA without installing a subpackage required for the same.
Recommended Action	Download the sub-package required for the affected SPA from the Cisco CCO software download site and install the same. This SPA can be booted in sub-package mode only. Please refer to the Cisco ASR platform documentation for obtaining and installing sub-packages.

%IOSXE_RP_SPA-3-UNSUPPORTED_SRVCS_SPA : Service SPA ([hex]) in [dec]/[dec] is not supported. SPA bootup failed.
Explanation	This message is displayed when attempting to bootup any service SPA in router running non K9 image, i.e., non-crypto image.
Recommended Action	Download the K9 IOS XE sub-packages and the required sub-package for the given service SPA from the Cisco CCO software download site and install the same. This SPA can be booted in sub-package mode only. Please refer to the Cisco ASR platform documentation for obtaining and installing sub-packages.

%IOSXE_RP_SPA-3-MISSING_SPA_PKG_WARN : sipspa[chars] package is not installed in standby for slot = [dec] and subslot = [dec].

Explanation

This message is displayed in standby console when attempting to bootup or restart or reload a WMA SPA without installing a
subpackage in the standby RP, although the SPA is or will be operational due to prior wma spa package installation in active
RP. If switchover takes place the WMA SPA will still be operational. But any subsequent soft or hard oir of the SPA will fail
due to missing sub package required to boot up the SPA. Hence it is recommended to complete the wma spa package installation
in standby also before switchover or immidiately after switchover.

Recommended Action

Download the sub-package required for the affected SPA from the Cisco CCO software download site and install the same for
the standby RP as is done on active RP. Please refer to the Cisco ASR platform documentation for obtaining and installing
sub-packages.

%IOSXE_RP_SPA-3-SPA_WRONGTYPE : Mismatched SPA type ([dec]) in slot [dec]/[dec]. Expected type [dec]. Use ‘no card [dec]/[dec]’ command to override preprovisioning and update card type.
Explanation	The SPA inserted does not match the currently provisioned SPA type.
Recommended Action	Replace wrong SPA with currently provisioned SPA type, or type ‘no card’ to allow new card type to be discovered.

%IOSXE_RP_SPA-6-MEDIA_AUTOFAILOVER : Media Fail over from ([chars]) to ([chars])
Explanation	Gige Media Failover.
Recommended Action	This is inforamtional message, Not an error message. Use ‘show interface gig’ to see the current active media type.

%IOSXE_RP_SPA-3-SONET_ALARM_PROC_ERR : [chars] Error has occurred while processing in the sonet alarm-proc
Explanation	Either free/create of the memory failed in SONET alarm proc
Recommended Action

%IOSXE_RP_SPA-3-LIC_REQ_FAILED : [int]/[int]/[int]: Interface enable not allowed — license request failed , err=[hex]

Explanation

A 10 Gig License is required to enable this port. License request has been denied by license manager

Recommended Action

%IOSXE_RP_SPA-3-LIC_REL_FAILED : [int]/[int]/[int]: Failed to release license feature [chars], handle=[hex], err=[hex]

Explanation

License release has been denied by license manager

Recommended Action

%IOSXE_RP_SPA-3-LIC_REG_FAILED : [int]/[int]/[int]: Failed to register license feature [chars], err=[hex]

Explanation

License registration has been denied by license manager

Recommended Action

IOSXE_RP_VTYMGT

%IOSXE_RP_VTYMGT-3-MSGDISPATCHNULL : Received NULL TDL message

Explanation

An unexpected condition in which IOS has received a NULL TDL message for Vty Management.

Recommended Action

%IOSXE_RP_VTYMGT-3-MSGDISPATCH : Unable to dispatch received TDL messages for Vty Management

Explanation

An unexpected condition has occurred while IOS is trying to dispatch to the TDL message handler functions for received TDL
messages for Vty Management.

Recommended Action

%IOSXE_RP_VTYMGT-3-MSGMISSINGFIELD : Missing field ‘[chars]’ in TDL Vty Management message ‘[chars]’ received

Explanation

A message missing a required field was received for Vty Management

Recommended Action

%IOSXE_RP_VTYMGT-3-MSGINVALIDFIELDINT : Invalid field ‘[chars]’ in TDL message ‘[chars]’ received: value ‘[int]’ for Vty
Management

Explanation

A message with an invalid field value was received for Vty Management

Recommended Action

%IOSXE_RP_VTYMGT-3-MSGINVALIDFIELDSTR : Invalid field ‘[chars]’ value ‘[chars]’ in TDL message ‘[chars]’ received for Vty
Management

Explanation

A message with an invalid field value was received for Vty Management

Recommended Action

%IOSXE_RP_VTYMGT-3-MSGERROR : Error ‘[dec]’ handling a received TDL message ‘[chars]’ for Vty Management: [chars]

Explanation

An unexpected condition has occurred while IOS is processing a received Vty Management TDL message

Recommended Action

%IOSXE_RP_VTYMGT-3-MSGBUILDERROR : Error ‘[dec]’ building TDL Vty Management message ‘[chars]’: [chars]

Explanation

An unexpected condition has occurred while IOS is building a TDL response message for Vty Management

Recommended Action

%IOSXE_RP_VTYMGT-3-MSGMARSHALERROR : Error ‘[dec]’ marshaling TDL Vty Management message ‘[chars]’: [chars]

Explanation

An unexpected condition has occurred while IOS is marshaling TDL response message for Vty Management

Recommended Action

%IOSXE_RP_VTYMGT-3-MSGENQUEUEERROR : Error queueing TDL Vty Management message ‘[chars]’

Explanation

An unexpected condition has occurred when IOS attempted to queue a TDL response message for Vty Management

Recommended Action

%IOSXE_RP_VTYMGT-3-MSGBIPCERR : Unable to process received BIPC messages for Vty Management, error: [chars]

Explanation

An unexpected condition has occurred while IOS was trying to process a received BIPC message for Vty Management.

Recommended Action

%IOSXE_RP_VTYMGT-3-MSGBIPCBUFFER : Unable to acquire a BIPC buffer of length [dec] for sending messages.

Explanation

A message was to be sent by IOS, but no BIPC buffer was available. The message to be sent has been discarded and the associated
operation failed.

Recommended Action

%IOSXE_RP_VTYMGT-3-MSGEXTAPPUPDATE : Unable to update external application data for line ‘[dec]’

Explanation

An attempt to update the external application for a line failed unexpectedly. The line update failed and if the line number
specified is valid, the line was released.

Recommended Action

%IOSXE_RP_VTYMGT-3-MSGVTYSVCINIT : Unable to initialize the Vty Management service listen port

Explanation

The platform IPC services failed to register the Vty Management service’s need for a listen port. The Vty Management service
will be unable to process requests. IOS services will be unavailable to external access methods.

Recommended Action

%IOSXE_RP_VTYMGT-3-MSGVTYCOUNT : Invalid vty count [dec] detected on initialization

Explanation

Upon initialization, the Vty Management subsystem checks that the number of available vtys for the platform is valid.

Recommended Action

%IOSXE_RP_VTYMGT-3-SET_ACCESS_FAIL : Installing LIIN interface access control failed
Explanation	This error happens when the Vty Management subsystem failed to set the access control function for the LIIN, possibly due to IOS out of memory or corruption. Persistent access features into IOS will not work.
Recommended Action	LOG_STD_ACTION

IOSXE_SERVICE_ENGINE

%IOSXE_SERVICE_ENGINE-3-MSGOPENFAIL : Cannot open interface [chars] ([dec])

Explanation

During the creation of a Service-Engine interface, it is necessary to program the system parameters in the driver. The driver
cannot be opened.

Recommended Action

%IOSXE_SERVICE_ENGINE-3-MSGSETFAIL : Set id on interface [chars] ([dec])

Explanation

During the creation of a Service-Engine interface, it is necessary to program the system parameters in the driver. The failed
to accept the programming.

Recommended Action

%IOSXE_SERVICE_ENGINE-3-MSGINITFAIL : Initialization of interface [chars] failed

Explanation

The initialization of the interface mentioned in the error message has failed.

Recommended Action

IOSXE_SIP_SPA

%IOSXE_SIP_SPA-3-HWIDB_FAILURE : Creation: port [dec] vc [dec]

Explanation

Failed to create a hwidb.

Recommended Action

%IOSXE_SIP_SPA-3-DEVICE_ERROR : subSlot [dec], spatype [hex]. Device error: [chars]

Explanation

An error related to a device on the SPA is detected.

Recommended Action

%IOSXE_SIP_SPA-3-ISR_RC_ERROR : ISR return code out of range. rc=[dec]

Explanation

The ISR error return code is out of range.

Recommended Action

%IOSXE_SIP_SPA-3-SPA_INTF_ID_CC_ALLOC_FAILED : Failed to allocate interface identifiers for SPA ([chars]) in slot/bay: [int]/[int]
Explanation	Failed to get CC buffer and flow control identifiers for the SPA in the specified subslot Traffic cannot flow through the SPA under this failure condition. This can happen if the system runs out of available identifiers.
Recommended Action	Try to reduce the number of interfaces configured in the system either by physically removing the SPAs or by changing the system configuration

%IOSXE_SIP_SPA-4-SPABUS : Subslot [dec], [chars] SPA BUS access failed. timeout=[int] err=[int] par=[int] err_c=[hex] addr=[hex]
data =[hex]

Explanation

SPABUS has reported an error.

Recommended Action

%IOSXE_SIP_SPA-4-SPABUS2 : Subslot [dec] SPA BUS access failed. No SPA present error

Explanation

SPABUS has reported an error.

Recommended Action

%IOSXE_SIP_SPA-6-OIR : Bay [dec] [chars] changed to [chars]
Explanation	SPA OIR Sequence
Recommended Action	No action is required.

%IOSXE_SIP_SPA-4-MAX_BANDWIDTH : Total SPA bandwidth exceeds line card capacity of [int] Mbps
Explanation	The total bandwidth of SPAs exceeds the rated capacity of this line card.
Recommended Action	Refer to the line card guidelines for the maximum allowed aggregated SPA bandwidth for the line card

%IOSXE_SIP_SPA-4-MAX_BANDWIDTH_NS : Total SPA bandwidth exceeds line card capacity, full utilization of installed SPA interfaces is not supported
Explanation	The total bandwidth of SPAs exceeds the rated capacity of this line card.
Recommended Action	Refer to the line card guidelines for the maximum allowed aggregated SPA bandwidth for the line card

%IOSXE_SIP_SPA-3-POWER : Bay [dec] 12V power is [chars]

Explanation

SPA 12V power fault indicator

Recommended Action

%IOSXE_SIP_SPA-3-SPI4_INIT_FAILURE : Bay [dec] initialization failure
Explanation	Failed to create SPI4 subblock
Recommended Action	Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, LOG_STD_ACTION

%IOSXE_SIP_SPA-3-MESSAGE_ERROR : Bay [dec]: [chars]
Explanation	An unexpected error has occurred.
Recommended Action	Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, LOG_STD_ACTION

%IOSXE_SIP_SPA-3-SPI4_CONFIG_FAILURE : Bay [dec], spi4 configuration failure, error [dec]
Explanation	Failed to configure SPI4 interface
Recommended Action	Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, LOG_STD_ACTION

%IOSXE_SIP_SPA-3-SPI4_NOTSYNC : [chars]: Can not synchronize SPI4 bus (host: src [chars]in sync, sink [chars]in sync, spa: src [chars]in sync, sink [chars]in sync).
Explanation	SPI4 bus between modular services card and SPA is not synchronized. It indicates either a not properly seated SPA, a hardware failure or an outdated ROMMON/FPGA image.
Recommended Action	Ensure that the SPA is properly seated in its subslot and reseat it if required.

%IOSXE_SIP_SPA-3-SPA_CTRL_INIT_FAILURE : Subslot [dec], spa controller initialisation failure, error [dec]
Explanation	Failed to initialise SPA controller
Recommended Action	Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, LOG_STD_ACTION

%IOSXE_SIP_SPA-3-SPA_CTRL_EFC_CONFIG_FAILURE : Subslot, spa controller EFC configuration failure, error [dec]
Explanation	Failed to configure SPA controller EFC
Recommended Action	Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, LOG_STD_ACTION

%IOSXE_SIP_SPA-3-FCI_NOT_SET : Bay [dec] — FCI type not set

Explanation

An FCI type of zero was detected

Recommended Action

%IOSXE_SIP_SPA-3-EFC_CHAN_ERR : EFC error — interface [chars], vc [dec], anyphy [dec], err_code [dec] : [chars]
Explanation	Failed to configure efc channel/parameters
Recommended Action	Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, LOG_STD_ACTION

%IOSXE_SIP_SPA-3-INVALID_ANYPHY : Bay [dec] — Invalid anyphy number [int] for vc [dec]

Explanation

Interface has invalid anyphy mumber

Recommended Action

Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://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).

%IOSXE_SIP_SPA-3-LINKREC_ERROR : Link record error — Bay [dec] vc [dec], error code [dec]

Explanation

Error processing link record structure

Recommended Action

%IOSXE_SIP_SPA-3-SONET_CLOCK_FAILED : SPA Sonet clock has failed (status = [hex])
Explanation	The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper operation, such as POS and ATM will be affected.
Recommended Action	If the SPA Sonet clock does not recover, perform an OIR. LOG_STD_RECUR_ACTION

%IOSXE_SIP_SPA-3-SONET_CLOCK_RECOVERED : SPA Sonet clock has recovered (status = [hex])
Explanation	SPA Sonet clock has recovered
Recommended Action	No action is required.

%IOSXE_SIP_SPA-3-INVALID_IF : Attempted to access HWIDB for port [int] on slot [dec] subSlot [dec]
Explanation	The ASR1000 attempted to access the HWIDB associated with a non-existent port.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IOSXE_SIP_SPA-3-ASR1000IPCALLOCFAIL : Failed to allocate Common IPC buffer [chars]
Explanation	The Carrier Card failed to allocate a buffer for communication with the Route Processor.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IOSXE_SIP_SPA-3-CMDNOINT : HWIDB Null for command [dec], port [hex]
Explanation	The Route Processor passed down a port number that is unknown on the carrier card.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IOSXE_SIP_SPA-3-EFC_FC_MAP_FAIL : Failed to update EFC flow control identifier for interface [chars] (status = [dec])
Explanation	The SPA driver is not able to update the datapath EFC flow control identifier for the interface specified in the message. This indicates a hardware error.
Recommended Action	No action is required.

%IOSXE_SIP_SPA-3-EFC_PROV_FAIL : Failed to provision EFC for interface [chars] (status = [dec])
Explanation	The SPA driver is not able to provision EFC for the interface specified in the message. This indicates a hardware error.
Recommended Action	No action is required.

%IOSXE_SIP_SPA-3-EFC_UNPROV_FAIL : Failed to unprovision EFC for VC [chars] (status = [dec])
Explanation	The SPA driver is not able to unprovision EFC for the interface specified in the message. This indicates a hardware error.
Recommended Action	No action is required.

%IOSXE_SIP_SPA-3-C2W_MAIN_INIT_FAIL : Failed to initialize SPA main c2w bus for subslot [dec] (status = [dec])
Explanation	The SPA driver is not able to initialize SPA main c2w. This indicates a hardware error.
Recommended Action	No action is required.

%IOSXE_SIP_SPA-3-NETCLK_FAIL : Failed to [chars] SPA reference clock on [chars]
Explanation	The SPA driver is not able to correctly configure the SPA reference clock on the specified interface. This indicates a hardware error.
Recommended Action	No action is required.

%IOSXE_SIP_SPA-3-LVLTRTOOBIG : Loveletter length exceeds max, [int] bytes
Explanation	The ASR1000-SIP line card attempted to send a large message to the Route Processor (ASR1000-RP).
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IOSXE_SIP_SPA-3-NODISPATCH : Dispatch vector Null, cmd=[dec], dintf=[dec]
Explanation	No command dispatch vector was found for the specified interface.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IOSXE_SIP_SPA-3-BADMALUCMD2 : Unsupported MALU cmd/arg0=[hex][hex], arg1arg2=[hex][hex] , hwidb=[chars]
Explanation	The Route Processor (ASR1000-RP) passed down a command that the software was not prepared to handle.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IOSXE_SIP_SPA-3-BADMALUCMD : Unsupported MALU command [dec], arg=[hex], pascb=[hex]
Explanation	The Route Processor (ASR1000-RP) passed down a command that the software was not prepared to handle.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IOSXE_SIP_SPA-3-BAD_IFCOMTYPE : Bad ifcom message type=[int]
Explanation	The Route Processor (ASR1000-RP) passed down a message that the software was not prepared to handle.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IOSXE_SIP_SPA-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation	The Linecard failed to send a message to the Route Processor (ASR1000-RP).
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IOSXE_SIP_SPA-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation	The SPA failed to allocate a buffer for communication with the Route Processor (ASR1000-RP).
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IOSXE_SIP_SPA-3-IPCPORTFAIL : Failed to open IPC port ‘[chars]’ [chars] with error [chars]

Explanation

The RP failed to open a port for communication with a SPA module.

Recommended Action

%IOSXE_SIP_SPA-3-IPCPORT : Failed to [chars] IPC port ‘[chars]’, error [chars]
Explanation	The Linecard failed to create a port for communication with the Route Processor (ASR1000-RP).
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IOSXE_SIP_SPA-3-FAST_NOTIFY_ERROR : Failed to send fast notification to [chars] for [chars] [chars].

Explanation

The SPA driver failed to deliver a fast notification.

Recommended Action

%IOSXE_SIP_SPA-6-LOGGERMSGTOOBIG : Logger message length ([int] bytes) exceeds the maximum allowed size

Explanation

The carrier card attempted to send a large message to the Route Processor

Recommended Action

%IOSXE_SIP_SPA-3-FRR_CFG_FAIL : Failed to configure fast reroute on [chars]: [chars].

Explanation

The SPA driver failed to configure fast rerouting on an interface.

Recommended Action

%IOSXE_SIP_SPA-3-APS_CFG_FAIL : Failed to configure APS on [chars]: [chars].

Explanation

The SPA driver failed to configure APS on an interface.

Recommended Action

%IOSXE_SIP_SPA-3-APS_PGP_FAIL : APS PGP Message send failed toslot/tobay [dec]: [dec].

Explanation

APS PGP between working and protect has failed

Recommended Action

%IOSXE_SIP_SPA-3-MDR_BACKUP_FAIL : Minimal Disruptive Restart backup failed for slot [int], bay [int]; reason ([chars])
Explanation	The SPA driver could not backup data required for Minimal Disruptive Restart process. The Minimal Disruptive Restart process for the SPA may be terminated as a consequence.
Recommended Action	The Minimal Disruptive Restart backup is stored in RP harddisk or Bootflash. If sufficient space is available on these devices, copy the error message exactly as it appears, and report it to your technical support representative.

%IOSXE_SIP_SPA-3-MDR_BACKUP_OPEN_FAIL : Failed to open Minimal Disruptive Restart backup for slot [int], bay [int], type [dec]; reason ([chars])
Explanation	The SPA driver could not open Minimal Disruptive Restart backup file. The Minimal Disruptive Restart process may be terminated as a consequence.
Recommended Action	The Minimal Disruptive Restart backup is stored in RP harddisk or Bootflash. If sufficient space is available on these devices, copy the error message exactly as it appears, and report it to your technical support representative.

%IOSXE_SIP_SPA-3-MDR_BACKUP_WRITE_FAIL : Failed to write [dec] bytes to Minimal Disruptive Restart backup[chars] for slot [int], bay [int], type [dec]; reason ([chars])
Explanation	The SPA driver could not write to Minimal Disruptive Restart backup file. The Minimal Disruptive Restart process may be terminated as a consequence.
Recommended Action	The Minimal Disruptive Restart backup is stored in RP harddisk or Bootflash. If sufficient space is available on these devices, copy the error message exactly as it appears, and report it to your technical support representative.

%IOSXE_SIP_SPA-3-MDR_BACKUP_READ_FAIL : Failed to read [dec] from Minimal Disruptive Restart backup for slot [int], bay [int],
type [dec]; reason ([chars])

Explanation

The SPA driver could not read from Minimal Disruptive Restart backup file. The Minimal Disruptive Restart process may be terminated
as a consequence.

Recommended Action

%IOSXE_SIP_SPA-3-MDR_CONFIG_REPLAY : Configuration replay failed during Minimal Disruptive Restart for slot [int], bay [int];
reason ([chars])

Explanation

The SPA driver failed to process config replay during Minimal Disruptive Restart. The Minimal Disruptive Restart process may
be terminated as a consequence.

Recommended Action

%IOSXE_SIP_SPA-3-SPA_ETHER_SUSPEND_ERROR : SPA ETHER process suspended too long; totally for [dec] milliseconds

Explanation

The SPA ETHER process is not able to write to ezman as ezman is blocked for writes. Copy the error message exactly as it appears
and report it to your technical support representative.

Recommended Action

IOSXE_SPA

%IOSXE_SPA-3-CREATION_FAILURE : slot=[dec] subslot=[dec], spa_type=[hex], lc_type=[hex].

Explanation

Failed to create a SPA object.

Recommended Action

%IOSXE_SPA-3-SPA_CREATION_FAILURE : slot=[dec] subslot=[dec], PID=[chars] lc_type=[hex].

Explanation

Failed to create a SPA object.

Recommended Action

%IOSXE_SPA-3-NULL_VFT : [chars] virtual function table is not initialized. spaType=[hex]

Explanation

A required function table is not initialized

Recommended Action

%IOSXE_SPA-3-NULL_VFUNC : [chars] vector is not initialized. spaType=[hex]

Explanation

A required function vector is not initialized

Recommended Action

%IOSXE_SPA-3-MEM_ALLOC_ERROR : [chars]

Explanation

Memory allocation error.

Recommended Action

%IOSXE_SPA-3-NULL_SPA_PTR :

Explanation

Pointer to a SPA object is NULL.

Recommended Action

%IOSXE_SPA-3-NULL_BAY_PTR :

Explanation

Pointer to SPA bay is NULL.

Recommended Action

%IOSXE_SPA-3-INVALID_SLOT_NUM : slot= [dec], max slot = [dec]

Explanation

An invalid slot number is specified in one of the internal APIs.

Recommended Action

%IOSXE_SPA-3-INVALID_SUBSLOT_NUM : subslot= [dec], max subslot = [dec]

Explanation

An invalid subslot number is specified in one of the internal APIs.

Recommended Action

%IOSXE_SPA-3-INVALID_DB_NUM : db = [dec], max db = [dec], db intf = [dec], max db intf = [dec]

Explanation

An invalid daughter board number is specified in one of the internal APIs.

Recommended Action

%IOSXE_SPA-3-INVALID_RP_SLOT_NUM : slot= [dec], max slot = [dec]

Explanation

An invalid RP slot number is specified in one of the internal APIs.

Recommended Action

%IOSXE_SPA-3-INVALID_CPU_NUM : cpu= [dec], max cpu = [dec]

Explanation

An invalid CPU number is specified in one of the internal APIs.

Recommended Action

%IOSXE_SPA-3-INVALID_SLOTUNIT_NUM : cardwide-port = [dec], max cardwide-port = [dec]

Explanation

An invalid cardwide-port number is specified in one of the internal APIs.

Recommended Action

%IOSXE_SPA-3-INVALID_INDX_RANGE : index1= [dec], index2= [dec], maxIndex= [dec]

Explanation

An invalid index range is specified in one of the internal APIs.

Recommended Action

%IOSXE_SPA-3-INVALID_IF_INDEX : index= [dec], spaType=[hex], slot [dec] subSlot [dec] slotunit [dec] vc [dec]

Explanation

Index for the interface is not valid.

Recommended Action

%IOSXE_SPA-3-INVALID_DATA_INSTANCE : interface type [chars], slot [dec] port [dec] vc [dec] : [chars]

Explanation

Data required to support the interface is not available.

Recommended Action

%IOSXE_SPA-3-POWER_CYCLE : [chars] occurred on Shared Port Adapter [int]/[int]

Explanation

An error has occurred which will cause the Shared Port Adapter to be power cycled

Recommended Action

%IOSXE_SPA-3-DIAG_CONFIG : [chars] did not complete [dec]/[dec]

Explanation

An error has occured during diagnostic test.

Recommended Action

%IOSXE_SPA-3-UNSUPPORTED_DATA : Data conversion error ([chars], [hex])

Explanation

An internal software error has occured when converting the data specified in the message from one representation to another.

Recommended Action

%IOSXE_SPA-3-IPC_FAILURE : IPC failure while [chars]

Explanation

An error has occurred while prepareing or sending an IPC message.

Recommended Action

%IOSXE_SPA-3-SENDCFGFAIL : Failed to send configuration for [chars] to carrier-card for subslot=[dec]/[dec]

Explanation

Sending configuration failed.

Recommended Action

%IOSXE_SPA-3-CREATE_TDLH_FAILURE : Failed to create SPA [dec]/[dec] handle

Explanation

Failed to create message handle for SPA communication.

Recommended Action

%IOSXE_SPA-3-DOMAIN_TDLH_FAILURE : [chars], rc = [dec]

Explanation

Failed to bind message handle for SPA communication.

Recommended Action

%IOSXE_SPA-3-SETUP_TDLH_FAILURE : Failed to set the alloc/free handler for SPA [dec]/[dec] handle

Explanation

Failed to set the alloc/free handler for SPA communication.

Recommended Action

%IOSXE_SPA-3-DISPATCH_INIT_TDLH_FAILURE : Failed to initialize dispatch path for SPA [dec]/[dec] handle

Explanation

Failed to initialize dispatch path handle for SPA communication.

Recommended Action

%IOSXE_SPA-3-INVALID_SPA_TDL_CCAPI_USAGE :

Explanation

Incorrect usage of an internal API that should only be used on CC.

Recommended Action

%IOSXE_SPA-6-TDLMSG_INCOMPATIBLE : Failed to copy message [chars] to buffer, not allowed for current domain.

Explanation

Failure to marshal a message indicates an incompatibility with the intended recipient.

Recommended Action

%IOSXE_SPA-3-CREATE_TDLMSG_FAILURE : Failed to create [chars] message for [chars].

Explanation

Failed to create/allocate necessary TDL message for SPA communication.

Recommended Action

%IOSXE_SPA-3-INVALID_HANDLE : Failed to get a valid IPC handle for type [int], slot [dec], subslot [dec].

Explanation

The client handle was found to be NULL for the given type/slot/subslot.

Recommended Action

%IOSXE_SPA-6-UPDOWN : Interface [chars], link down due to [chars]
Explanation	Ethernet link is down due to remote/local fault.
Recommended Action	Replace the faulty cable.

%IOSXE_SPA-6-DUAL_RATE_CHANGE : [chars]: [chars]
Explanation	Change in rate of the link.
Recommended Action	No action is required.

%IOSXE_SPA-3-SPA_SETUP_FAILURE : Failed to properly setup for SPA communication on slot [dec], subslot [dec].

Explanation

Discovery of the linux interface used to communicate with a SPA failed

Recommended Action

%IOSXE_SPA-3-ABANDON_SPA_CONFIGURATION : Abandon configuration for subslot [dec]/[dec], the SPA type([dec]) is NOT match with SUP card.
Explanation	Abandon SPA configuration.
Recommended Action	Please check the startup configuration, use no card command to override wrong card configuration and update card type.

IOSXE_SYS_INFRA

%IOSXE_SYS_INFRA-6-BIPC_READ_ERR : connection read error from [chars], rc [dec], bring down IPC id [dec] for fd [dec] seq
[dec]

Explanation

BIPC error during IPC read

Recommended Action

%IOSXE_SYS_INFRA-6-BIPC_READBUF_ERR : process receive buffer error from [chars], rc [dec], bring down IPC

Explanation

BIPC error during IPC read from buffer

Recommended Action

%IOSXE_SYS_INFRA-6-BIPC_DISCONNECT : disconnect by application for [chars], bring down IPC

Explanation

BIPC disconnect requested by an application

Recommended Action

%IOSXE_SYS_INFRA-6-BIPC_WRITE_ERR : write bipc error for [chars], rc [dec], bring down IPC

Explanation

BIPC error during IPC read

Recommended Action

%IOSXE_SYS_INFRA-6-BIPC_CREATE : bipc connect succeeded for [chars], ipc_ctl_id [dec], ipc_fd [dec], seq [dec]

Explanation

BIPC connect succeeded

Recommended Action

%IOSXE_SYS_INFRA-3-BIPC_CREATE_FAIL : Failed to open IPC port ‘[chars]’ for service ‘[chars]’ with error [chars].

Explanation

BIPC connect failed

Recommended Action

%IOSXE_SYS_INFRA-3-BIPC_DISCONNECT_FAIL : Failed to disconnect IPC port ‘[chars]’ for service ‘[chars]’ with error [chars].

Explanation

BIPC disconnect failed

Recommended Action

%IOSXE_SYS_INFRA-4-BIPC_TX_Q_THRESHOLD : BIPC transmit queue threshold reached for the channel ‘[chars]’: ipc_ctl_id [dec]
(ipc_fd [dec], seq_num [dec]), Tx Q size [dec]

Explanation

Large number of unsent IPC messages are queued in a BIPC send buffer

Recommended Action

%IOSXE_SYS_INFRA-4-BIPC_RX_IN_APPL_THRESHOLD : Number of IPC messages held in the application reached the maximum channel
threshold. IPC channel ‘[chars]’: ipc_ctl_id [dec] (ipc_fd [dec], seq_num [dec]), curr IPC msg hel in appl [dec]

Explanation

Application is holding large number of received IPC messages

Recommended Action

%IOSXE_SYS_INFRA-3-EVLIB_EPOLL_ARGS : evGetEpollArgs returned fd [dec]

Explanation

Evlib retuned a huge FD value that IOS can not handle.

Recommended Action

%IOSXE_SYS_INFRA-6-EOBC_ADDR_CACHE : EOBC ip-table cache: [chars]

Explanation

Unable to setup internal address for eobc communication

Recommended Action

%IOSXE_SYS_INFRA-3-EOBC_SOCK : Socket event for [chars]
Explanation	An internal socket level event has returned an error which is indicated. This may have been the result of a bind, peek, receive or send operation with respect to the EOBC interface listed.
Recommended Action	LOG_STD_SH_CMD_ACTION(show eobc, show platform software infrastructure bipc)

%IOSXE_SYS_INFRA-3-EWRITE_EVENT_FD : Write to [chars] wakeup fd failed, errno [dec], current signal/wakeup cnt: [int]/[int]

Explanation

Trigering a thread by writing to its wakeup fd failed

Recommended Action

%IOSXE_SYS_INFRA-3-EREAD_EVENT_FD : [chars] read from wakeup fd failed, errno [dec]

Explanation

A thread reading from its wakeup fd failed

Recommended Action

%IOSXE_SYS_INFRA-3-EIOS_POLL : IOS thread poll on event lib and wakeup fds failed, errno [dec]

Explanation

IOS thread poll on event lib and wakeup fds failed

Recommended Action

%IOSXE_SYS_INFRA-3-EIOS_EVDISPATCH : IOS scheduler event dispatch failed, ev_ret [dec], errno [dec]

Explanation

IOS scheduler event dispatch failed

Recommended Action

%IOSXE_SYS_INFRA-3-EIOS_EVGETNEXT : IOS scheduler get next event failed, ev_ret [dec], errno [dec]

Explanation

IOS scheduler get next event failed

Recommended Action

%IOSXE_SYS_INFRA-3-EFP_EVDISPATCH : Fastpath thread event dispatch failed, ev_ret [dec], errno [dec]

Explanation

fastpath thread event dispatch failed

Recommended Action

%IOSXE_SYS_INFRA-3-EFP_EVGETNEXT : Fastpath thread get next event failed, ev_ret [dec], errno [dec]

Explanation

Fastpath thread get next event failed

Recommended Action

%IOSXE_SYS_INFRA-3-EFP_EPOLL_WAIT : Fastpath thread epoll wait failed, errno [dec]

Explanation

Fastpath epoll wait failed

Recommended Action

%IOSXE_SYS_INFRA-3-EFP_TOP_EPOLL_CTL_FAILED : Fastpath thread top level efd epoll [chars] failed, fd [dec], errno [dec]

Explanation

Fastpath top level efd epoll_ctl operation failed

Recommended Action

%IOSXE_SYS_INFRA-3-EFP_IPC_EPOLL_CTL_FAILED : Fastpath thread [chars] [chars] for IPC channel [chars] (ipc id [dec], ipc
fd [dec], seqnum [dec]) failed, efd [dec], errno [dec]

Explanation

Fastpath epoll_ctl operation for an IPC channel failed

Recommended Action

%IOSXE_SYS_INFRA-3-EFP_IPC_EPOLL_NO_IPC_ENTRY : IPC entry not found for ipc fd [dec], seq [dec], events [hex] while processing
[chars] from epoll fd [dec]

Explanation

Fastpath failed to find IPC entry after epoll_wait

Recommended Action

%IOSXE_SYS_INFRA-6-FP_IPC_DISCONNECT : IPC channel disconnect for [chars], ipc_ctl_id [dec], fd [dec], seq_num [dec], loc
[chars], err [dec] ([chars])

Explanation

An IPC channel in fastpath is terminated

Recommended Action

%IOSXE_SYS_INFRA-6-IOS_IPC_CTL_DESTROY : IPC control blk destroy: name [chars], ipc_ctl_id [dec], refcout [dec], need_free
[dec]

Explanation

An IPC control block is requested to be destroyed

Recommended Action

%IOSXE_SYS_INFRA-6-IOS_FREE_IPC_CTL : IPC control blk free: name [chars], ipc_ctl_id [dec], refcount [dec]

Explanation

An IPC control block is freed

Recommended Action

%IOSXE_SYS_INFRA-4-BIPC_CLEAR_CONN : IPC channel (fd [dec], seq_num [dec]) for service ‘[chars]’ cleared by user

Explanation

BIPC disconnect requested by an user with clear command

Recommended Action

IOSXE_THROUGHPUT

%IOSXE_THROUGHPUT-3-INVALID_CONFIG : No valid license found for the configured throughput level: [chars] kbps
Explanation	Users has the boot up throughput set to non-default level without having the valid license.
Recommended Action	Install valid throughput license

%IOSXE_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

%IOSXE_THROUGHPUT-3-CONF_FAILED : Configuration failed. Installed license does not support the throughput level. Please install the valid license
Explanation	An error occurred when the throughput configuration was attempted.
Recommended Action

%IOSXE_THROUGHPUT-3-INVALID_LEVEL : An invalid throughput level: [chars] kbps was selected.
Explanation	The configured throughput level is unknown
Recommended Action

%IOSXE_THROUGHPUT-6-LEVEL : Throughput level has been set to [dec]00000 kbps
Explanation	Throughput level has been set to a number
Recommended Action

%IOSXE_THROUGHPUT-3-SETUP_FAILED : Throughput level setup failed. Boot up will be at the default throughput
Explanation	An error occurred when licensing tried to setup the througput
Recommended Action

IOSXE_TIMESTAMP_ENGINE

%IOSXE_TIMESTAMP_ENGINE-4-ERROR : NULL

Explanation

An unexpected condition has occurred.

Recommended Action

%IOSXE_TIMESTAMP_ENGINE-3-TSU_ERR : An unexpected condition has occurred at module ([chars])

Explanation

An unexpected condition has occurred at the Interface Module TSU.

Recommended Action

IOSXE_UPGRADE_ROMMON through IPA

IOSXE_UPGRADE_ROMMON
IOSXE_USB
IOSXE_UTD
IOSXE_VMAN
IOSXE_WCCP
IOSXE_WD
IOS_LICENSE_IMAGE_APPLICATION
IOXN_APP
IP
IPA

IOSXE_UPGRADE_ROMMON

%IOSXE_UPGRADE_ROMMON-0-ROMMON_UPGRADE_FAIL : ROMMON upgrade failed: partition [chars]

Explanation

An attempt to upgrade the ROMmon failed.

Recommended Action

Check the system messages to see if any messages appeared that might indicate the source of the ROMmon problem. If you do
not find any additional information indicating a correctable problem, collect all output on the screen, in particular the
console port output after the upgrade rom-monitor command was entered and the output of show rom-monitor, and provide the
collected information to a Cisco technical support representative.

%IOSXE_UPGRADE_ROMMON-0-ROMMON_LOADTEST_FAIL : ROMMON FIPS_140-3 Load test *FAILED*: file [chars]

Explanation

FIPS 140-3 Related Load test failed for the ROMmon.

Recommended Action

Check the system messages to see if any messages appeared that might indicate the source of the ROMmon Load test problem.
If you do not find any additional information indicating a correctable problem, collect all output on the screen, in particular
the console port output after the upgrade rom-monitor command was entered and the output of show rom-monitor, and provide
the collected information to a Cisco technical support representative.

IOSXE_USB

%IOSXE_USB-3-ESHOW_USB : Internal Error locating database for USB Devices.

Explanation

The mcp_usb_devices is incorrect and needs to be changed

Recommended Action

IOSXE_UTD

%IOSXE_UTD-3-ALLOC : Failed to allocate message

Explanation

When attempting to program the dataplane there was not enough memory to allocate the message.

Recommended Action

%IOSXE_UTD-3-MESSAGE : Failed to send message

Explanation

When the message was being prepared for sending to the data plane, there was an error.

Recommended Action

%IOSXE_UTD-4-VERSION_INCOMPATIBILITY : UTD package version [chars] does not match recommended UTD package version [chars]

Explanation

The UTD package version does not match the recommended UTD package version embedded in this IOS-XE version.

Recommended Action

%IOSXE_UTD-2-VERSION_UNSUPPORTED : UTD package version [chars] is not supported, recommended version is [chars]

Explanation

The UTD package version does not match the required UTD version embedded in this IOS-XE version. This is an unsupported configuration
and may behave unexpectedly.

Recommended Action

%IOSXE_UTD-4-SIG_UPDATE_CFG : UTD signature updates have been configured — A brief service interruption at the time of update
is expected

Explanation

The UTD service will be restarted if a new signature package is found. During this time, if fail-close has been configured
(recommended), traffic that would be inspected by UTD will be dropped. Otherwise (default), traffic that would be inspected
by UTD will be allowed to pass uninspected. To minimize this service interruption, it is recommended to schedule this operation
outside of normal business hours.

Recommended Action

%IOSXE_UTD-4-SIG_UPDATE_EXEC : UTD signature update has been executed — A brief service interruption is expected

Explanation

The UTD service will be restarted if a new signature package is found. During this time, if fail-close has been configured
(recommended), traffic that would be inspected by UTD will be dropped. Otherwise (default), traffic that would be inspected
by UTD will be allowed to pass uninspected. To minimize this service interruption, it is recommended to execute this operation
outside of normal business hours.

Recommended Action

%IOSXE_UTD-4-MT_CONFIG_DOWNLOAD : UTD MT configuration download has [chars]

Explanation

In UTD multitenancy mode, the configuration download to the container can take a while. Please be patient.

Recommended Action

%IOSXE_UTD-4-MT_CONTAINER_MESSAGE_TIMEOUT : UTD message sent to the container has timed out

Explanation

The UTD message sent to the container has timed out.

Recommended Action

%IOSXE_UTD-4-MT_CONTAINER_MESSAGE_NAK : Container responded to UTD message with an error: [dec]

Explanation

The container rejected the UTD message

Recommended Action

%IOSXE_UTD-4-MT_CONTAINER_SESSION_TIMEOUT : UTD container download has timed out

Explanation

The container did not respond with an up/down status before the session timed out.

Recommended Action

%IOSXE_UTD-4-MT_CONTAINER_STATUS_DOWN : UTD poll: container status is DOWN

Explanation

The container sent a down status to the poll message

Recommended Action

IOSXE_VMAN

%IOSXE_VMAN-3-MSGINITFAIL : Failed to initialize required Virt-manager resource: [chars]

Explanation

During the initialization of the resources required by Virt-manager, a failure occurred. This has prevented virtual services
from being activated.

Recommended Action

%IOSXE_VMAN-3-MSGDISPATCH : Unable to dispatch received TDL message from Virt-manager

Explanation

An unexpected condition has occurred while IOS was trying to dispatch a TDL message received from Virt-manager.

Recommended Action

%IOSXE_VMAN-3-RSPMSGHDLR : Failed to deliver response message: [chars]

Explanation

An unexpected condition has occurred while IOS was trying to deliver a response message to a virtual service received from
Virt-manager.

Recommended Action

IOSXE_WCCP

%IOSXE_WCCP-4-NOINPUT : NULL input, [chars]

Explanation

An unexpected condition has occurred which is due to the NULL value of the input parameter.

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show ip wccp 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.

%IOSXE_WCCP-4-NOSVCGRP : [chars] Service Group ([dec], [dec], [int]) NOT exist

Explanation

An unexpected condition has occurred which is due to the absence of the service group structure.

Recommended Action

%IOSXE_WCCP-4-NOACL : Access list is null

Explanation

An unexpected condition has occurred which is due to the absence of an access list structure.

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show ip access-lists 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.

%IOSXE_WCCP-4-ACELIMIT : Too many ACEs in MASK ACL, please switch to Hash mode

Explanation

Mask merged ACL generate too many ACEs.

Recommended Action

%IOSXE_WCCP-4-BADACE : Access list contains invalid ace

Explanation

An unexpected condition has occurred which is due to an invalid statement in the access list structure.

Recommended Action

%IOSXE_WCCP-4-NOINTF : No [chars] interface info for Service Group ([dec], [dec], [int])

Explanation

An unexpected condition has occurred which is due to the absence of MCP WCCP interface info for the specific service group.

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show platform software wccp 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.

%IOSXE_WCCP-4-UNKNOWNDIR : Unknown [chars] interface direction [hex] for Service Group ([dec], [dec], [int])

Explanation

An unexpected condition has occurred which is due to the unknown direction has been applied to the interface for the service
group.

Recommended Action

%IOSXE_WCCP-4-NOSTATS : WCCP [chars] message error

Explanation

An unexpected condition has occurred which is due to the error in receiving WCCP stats update message.

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show platform software wccp <id> counters 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.

%IOSXE_WCCP-4-NOSTATSSVC : Service Group ([dec], [dec], [int]) not exist for the stats message

Explanation

An unexpected condition has occurred which can’t find the service group for the service group stats message.

Recommended Action

%IOSXE_WCCP-4-NOSTATSINTF : Interface handle [int] not exsit for the stats message

Explanation

An unexpected condition has occurred which can’t find the interface handle for the interface stats message.

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show platform software wccp <id> int counters 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.

IOSXE_WD

%IOSXE_WD-2-HEARTBEAT_FAIL : Heartbeat is not emitted. Heartbeat count:[dec]
Explanation	Failure in IOS to generate a heartbeat is an abnormal condition
Recommended Action	This message may be related to an abnormal configuration and system load, or transient high processing demand. When reporting this message, copy the message text exactly as it appears, include the stack trace and report to your technical support representative

%IOSXE_WD-2-HOG_DETECT_FAIL : CPUHOG detection failed to start.
Explanation	Failure in setting up CPUHOG detection mechanism is an abnormal condition
Recommended Action	This message may be related to an abnormal configuration and system load, or transient high processing demand. When reporting this message, copy the message text exactly as it appears, include the stack trace and report to your technical support representative

IOS_LICENSE_IMAGE_APPLICATION

%IOS_LICENSE_IMAGE_APPLICATION-3-FAILED : [chars]
Explanation	The ios licensing subsystem failed to create a process/watched boolean etc to watch request from the remote show subsys license commands
Recommended Action	please capture the error msg and forward it to the appropriate licensing component

%IOS_LICENSE_IMAGE_APPLICATION-3-UNKNOWN_EVENT : [chars]
Explanation	The ios image licensing subsystem received an event which it does not understand or recognizes
Recommended Action	please capture the error msg and forward it to the appropriate licensing component

%IOS_LICENSE_IMAGE_APPLICATION-3-UNKNOWN_VERSION : [chars]
Explanation
Recommended Action

%IOS_LICENSE_IMAGE_APPLICATION-6-NO_LICENSE : No valid license available: [chars] = [chars]; [chars] = [dec]; [chars] = [chars]:[chars]
Explanation	The ios image licensing subsystem received an event for an unknown version of a feature There is no valid license available on the box and we are running on a default feature
Recommended Action	please capture the error msg and forward it to the appropriate licensing component please purchase a license to activate required features

%IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL : Module name = [chars] Next reboot level = [chars] and License = [chars]
Explanation	This is an informational message to display the change in the next reboot license level
Recommended Action	This is an informational message, no action is required

%IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL_CONFIG : Please issue ‘license boot’ config command to make extension license ([chars]) available for use.
Explanation	This is an informational message to info user that to make extension license available to support image level, licensing image level needs to be configured
Recommended Action	This is an informational message, no action is required

%IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_CONFIG : EULA must be accepted for license level = [chars]
Explanation	This is an informational message to inform user that the user needs to reissue the command from an interactive terminal
Recommended Action	This is an informational message, no action is required

IOXN_APP

%IOXN_APP-3-INITFAIL : Failed to create chasfs property ioxman (rc =[chars]) or caf (rc = [chars]) is not up

Explanation

An unexpected condition resulted into failure to start an application.

Recommended Action

%IOXN_APP-3-CLEANUPFAIL : Failed to create chasfs property to indicate cleanup of previous app installation (rc = [chars])

Explanation

An unexpected condition resulted in failure to setup the start of an application.

Recommended Action

%IOXN_APP-3-GSFAIL : [chars] [int]

Explanation

An unexpected condition resulted into failure to start an application.

Recommended Action

%IOXN_APP-3-CFGFAIL : [chars] [chars]

Explanation

An unexpected condition resulted into failure to apply auto config

Recommended Action

%IOXN_APP-3-PREVOPFAIL : Overriding previous operation ([chars] iox) that is taking longer than [int] secs to complete

Explanation

An unexpected condition resulted in failure to apply iox config

Recommended Action

%IOXN_APP-3-MSGFAIL : Message dispatch failure ([chars]).

Explanation

Message could not be dispatched to an application.

Recommended Action

%IOXN_APP-6-STARTUP_CONFIG_INFO : [chars]

Explanation

Informational logs for startup config injection.

Recommended Action

%IOXN_APP-6-STARTUP_CONFIG_CHASSIS_INFO : [chars] [dec]/[chars]/[dec]/[dec]
Explanation	Chassis information at startup config injection.
Recommended Action	No action is required.

%IOXN_APP-3-STARTUP_CONFIG_FAIL : [chars] [chars]

Explanation

Error while creating startup config

Recommended Action

%IOXN_APP-3-IPCINITFAIL : [chars]

Explanation

A critical IPC initialization error occured

Recommended Action

%IOXN_APP-6-SLOT_NOTIFICATION : [chars] [dec]
Explanation	Slot addition or removal information
Recommended Action	No action is required.

IP

%IP-4-CLASS : Bad IP address and mask [IP_address]%m in class_resolve()

Explanation

An internal software error occurred.

Recommended Action

%IP-4-DUPADDR : Duplicate address [IP_address] on [chars], sourced by [enet]
Explanation	Another system is using your IP address.
Recommended Action	Change the IP address of one of the two systems.

%IP-4-ZERO_ADDR : Zero MAC address for [IP_address] in ARP cache
Explanation	An entry in the ARP cache have a NULL MAC address
Recommended Action	If this message recurs, call your technical support representative for assistance.

%IP-3-DESTHOST : src=[IP_address], dst=[IP_address], NULL desthost

Explanation

An internal software error occurred.

Recommended Action

%IP-3-BADIPALIGN : Invalid alignment in packet for IP. [chars]=[hex]
Explanation	The packet data structure is misaligned. This condition may result in a small amount of overhead in processing IP traffic.
Recommended Action	Enter a show hardware command and report the output, along with this error message, to your technical support representative.

%IP-3-BADSROUTE : Improper source route. Length [dec] Ptr [dec]

Explanation

A hardware or software error occurred.

Recommended Action

%IP-6-PHYBCASTDROP : Physical broadcast packet detected and dropped, src=[IP_address], dst=[IP_address]
Explanation	Physical broadcast packet was dropped.
Recommended Action	No action is required.

%IP-6-L2MCASTDROP : Layer 2 Multicast packet detected and dropped, src=[IP_address], dst=[IP_address]
Explanation	Layer 2 Multicast packet with Layer3 Unicast Destination was dropped.
Recommended Action	No action is required.

%IP-3-LOOPPAK : Looping packet detected and dropped — src=[IP_address], dst=[IP_address], hl=[int], tl=[int], prot=[int],
sport=[int], dport=[int] in=[chars], nexthop=[IP_address], out=[chars]options=[chars]

Explanation

A software error occurred.

Recommended Action

%IP-5-WEBINST_START : Attempting web install from host [IP_address]
Explanation	A hardware or software error occurred.
Recommended Action	Copy the error message exactly as it appears, and report it to your technical support representative.

%IP-5-WEBINST_KILL : Terminating DNS process

Explanation

A hardware or software error occurred.

Recommended Action

%IP-5-WEBINST_COMP : Selected IP address [IP_address]

Explanation

A hardware or software error occurred.

Recommended Action

%IP-5-WEBINST_RESP : Sending DNS response to [IP_address] (request was for [IP_address])

Explanation

A hardware or software error occurred.

Recommended Action

%IP-3-CNTRFULL : IP counter block is full (setting protocol [dec])

Explanation

An internal software error occured.

Recommended Action

%IP-5-TURBOACL : [chars]

Explanation

Error occured in intialisation of TURBOACL.

Recommended Action

Copy the error message exactly as it appears on the console or in the system log. Issue the show process 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.

%IP-5-ACL : [chars]

Explanation

Error occured in IP access checks.

Recommended Action

%IP-4-UNICASTRPF : IP unicast reverse-path check disabled on [chars]

Explanation

The IP verify unicast reverse-path feature was disabled because CEF was disabled (either through configuration or due to an
internal error.

Recommended Action

%IP-3-LOOPOUTIF : Output interface for packet has been changed for [dec] times and dropped — src=[IP_address], dst=[IP_address],
hl=[int], tl=[int], prot=[int], in=[chars], nexthop=[IP_address], out=[chars]

Explanation

A software error occurred.

Recommended Action

%IP-3-MAXIRDP : Attempt to send IRDP to proxies exceeding configurable limit: [dec], interface: [chars], secondary = [dec], proxy = [dec]
Explanation	The sum of configured secondary addresses and configured proxy addresses exceeds the number of total addresses that the IRDP can support in its implementation.
Recommended Action	Reduce the number of either the secondary IP addresses or proxy addresses configured for the interface.

%IP-4-IPPOOLS : Detected a local pool and a DHCP pool with the same name: [chars]
Explanation	A local pool and a DHCP pool have been configured with the same name. This may cause conflict during address allocations.
Recommended Action	Change the name of one of the two pools

%IP-3-ICMPRATELIMIT : [int]nreachables rate-limited within [int] milliseconds on [chars]. [int] log messages suppressed since last log message displayed on [chars]
Explanation	An excessive number of packets are triggering log messages on this interface
Recommended Action	change the log threshold with the icmp rate-limit command or find the source of the packets and block the packets from this router

%IP-3-ICMPRATELIMITDF : [int] DF unreachables rate-limited within [int] milliseconds on [chars]. [int] DF log messages suppressed since last log message displayed on [chars]
Explanation	An excessive number of packets are triggering log messages on this interface
Recommended Action	change the log threshold with the icmp rate-limit command or find the source of the packets and block the packets from this router

%IP-3-NOOUTINTF : Output interface not available. source address: [IP_address], destination address: [IP_address], routing
type: [int]

Explanation

The output interface for this packet is not set

Recommended Action

%IP-3-NONALIAS : non-alias address [IP_address] in table [chars] found in IP alias list

Explanation

The IP alias list holds IP aliases only but non-alias entries are found.

Recommended Action

%IP-3-IPTOPOID : Topology ID [hex] is invalid, can’t get the base topology ID.

Explanation

An internal software error occurred

Recommended Action

%IP-3-SBINIT : Error initializing [chars] subblock data structure. [chars]

Explanation

Initialization of the specified subblock data structure could not be accomplished.

Recommended Action

IPA

%IPA-3-PORTCONN : bay [[int]] failed to establish [chars] connection ([hex])

Explanation

An attempt to establish the console or debugger connection with the channel port adapter failed.

Recommended Action

%IPA-3-PORTIOKILL : Port IO [chars] process terminating.

Explanation

Unexpected termination of a port io process.

Recommended Action

%IPA-3-NEVER : bay [[chars]] mailbox response timed out after ([int] + [int]) usecs, mbx=[hex]
Explanation	A mailbox command sent from driver to the channel port adapter never completed within the expected time limit. As a result of this error, the channel port adapter driver will reset the port adapter and reload microcode to it.
Recommended Action	The reset and reload rectified the problem. If that did not occur, then try the `microcode reload` operation again. <Body><par>If the error still occurs, record the output from the following commands: <Bullet><par>`show tech` <Bullet><par>`dir slot0:` <Bullet><par>`dir slot1:` <Bullet><par>`show log` <Body><par>Provide this information to your technical support representative.

%IPA-3-UKNMBXCMD : [chars]: unknown mailbox command: [hex] [hex] [hex] [hex]

Explanation

The channel port adapter sent a mailbox command that the driver did not expect. This may occur if there is a version mismatch
between the system image and the microcode.

Recommended Action

%IPA-3-INVMBXCMD : [chars]: invalid mailbox command: [hex]

Explanation

A subsytem attempted to register a mailbox command that is out of range.

Recommended Action

Источник

Stumped: gbic-invalid error, bad crc — anyone see this before?

so I’ve been successfully able to make a fiber etherchannel between my 3750G’s upon themselves, but I’m trying to connect the 3750G (Master) in a uplink to my HP Procurve 2910al and I’m getting a bad crc error:

00:10:02: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port 65564 has bad crc
00:10:02: %PM-4-ERR_DISABLE: gbic-invalid error detected on Gi1/0/28, putting Gi1/0/28 in err-disable state
00:10:04: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/28, changed state to down

.
here is the config on the 3750G — it’s a factory reset, basic config only. anyone see something I’m missing? — at the bottom will be the HP Procurve. Only thing I can think of is maybe the 3750G needs a firmware update. I’ve tried a Netgear, Dell, and HP Gbic stick and they all give the same crc. Even brand-new Netgeat carrot sticks; i’m perplexed.
Switch#
Switch#show ver
Cisco IOS Software, C3750 Software (C3750-IPBASEK9-M), Version 12.2(25)SEB1, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2005 by Cisco Systems, Inc.
Compiled Sat 30-Apr-05 02:33 by yenanh

ROM: Bootstrap program is C3750 boot loader
BOOTLDR: C3750 Boot Loader (C3750-HBOOT-M) Version 12.1(14r)EA1a, RELEASE SOFTWARE (fc1)

Switch uptime is 8 hours, 12 minutes
System returned to ROM by power-on
System image file is «flash:c3750-ipbasek9-mz.122-25.SEB1/c3750-ipbasek9-mz.122-25.SEB1.bin»

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

Switch#
Switch#
Switch#
Switch#

Switch>
Switch>
Switch>
Switch>
Switch>
Switch>enable
Switch#
Switch#
Switch#
Switch#
Switch#
Switch#
Switch#
Switch#show config
Using 1891 out of 524288 bytes
!
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Switch
!
!
no aaa new-model
switch 1 provision ws-c3750g-24ts
ip subnet-zero
ip routing
!
!
!
!
!
!
no file verify auto
spanning-tree mode pvst
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
interface Port-channel1
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface GigabitEthernet1/0/1
!
interface GigabitEthernet1/0/2
!
interface GigabitEthernet1/0/3
!
interface GigabitEthernet1/0/4
!
interface GigabitEthernet1/0/5
!
interface GigabitEthernet1/0/6
!
interface GigabitEthernet1/0/7
!
interface GigabitEthernet1/0/8
!
interface GigabitEthernet1/0/9
!
interface GigabitEthernet1/0/10
!
interface GigabitEthernet1/0/11
!
interface GigabitEthernet1/0/12
!
interface GigabitEthernet1/0/13
!
interface GigabitEthernet1/0/14
!
interface GigabitEthernet1/0/15
!
interface GigabitEthernet1/0/16
!
interface GigabitEthernet1/0/17
!
interface GigabitEthernet1/0/18
!
interface GigabitEthernet1/0/19
!
interface GigabitEthernet1/0/20
switchport mode access
!
interface GigabitEthernet1/0/21
switchport mode access
!
interface GigabitEthernet1/0/22
switchport mode access
!
interface GigabitEthernet1/0/23
switchport mode access
!
interface GigabitEthernet1/0/24
switchport mode access
!
interface GigabitEthernet1/0/25
!
interface GigabitEthernet1/0/26
!
interface GigabitEthernet1/0/27
!
interface GigabitEthernet1/0/28
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 1 mode active
!
interface Vlan1
description ‘Primary Vlan’
no ip address
!
interface Vlan100
ip address 192.168.225.31 255.255.255.192
ip helper-address 192.168.225.1
!
ip classless
ip http server
ip http secure-server
!
!
control-plane
!
!
line con 0
line vty 0 4
no login
line vty 5 15
no login
!
!
end

Switch#show inter giga1/0/28
GigabitEthernet1/0/28 is down, line protocol is down (err-disabled)
Hardware is Gigabit Ethernet, address is 0013.c444.809c (bia 0013.c444.809c)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Auto-duplex, Auto-speed, link type is auto, media type is unknown
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of «show interface» counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
—More—

Switch#
Switch#config t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#inter giga1/0/28
Switch(config-if)#no shut
Switch(config-if)#exit
Switch(config)#exit
Switch#show inter giga1/0/28
08:18:43: %SYS-5-CONFIG_I: Configured from console by console
GigabitEthernet1/0/28 is down, line protocol is down (err-disabled)
Hardware is Gigabit Ethernet, address is 0013.c444.809c (bia 0013.c444.809c)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Auto-duplex, Auto-speed, link type is auto, media type is unknown
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of «show interface» counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
—More—

@ @
File «flash:c3750-ipbasek9-mz.122-25.SEB1/c3750-ipbasek9-mz.122-25.SEB1.bin» unc ompressed and installed, entry point: 0x3000
executing.

Restricted Rights Legend

Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software — Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

Cisco IOS Software, C3750 Software (C3750-IPBASEK9-M), Version 12.2(25)SEB1, REL EASE SOFTWARE (fc1)
Copyright (c) 1986-2005 by Cisco Systems, Inc.
Compiled Sat 30-Apr-05 02:33 by yenanh
Image text-base: 0x00003000, data-base: 0x00DB5330

flashfs[1]: 358 files, 5 directories
flashfs[1]: 0 orphaned files, 0 orphaned directories
flashfs[1]: Total bytes: 15998976
flashfs[1]: Bytes used: 7683072
flashfs[1]: Bytes available: 8315904
flashfs[1]: flashfs fsck took 4 seconds.
flashfs[1]: Initialization complete. done Initializing flashfs.

POST: CPU MIC register Tests : Begin
POST: CPU MIC register Tests : End, Status Passed

POST: PortASIC Memory Tests : Begin
POST: PortASIC Memory Tests : End, Status Passed

POST: CPU MIC PortASIC interface Loopback Tests : Begin
POST: CPU MIC PortASIC interface Loopback Tests : End, Status Passed

POST: PortASIC RingLoopback Tests : Begin
POST: PortASIC RingLoopback Tests : End, Status Passed

Waiting for Stack Master Election (around 30 seconds).
POST: PortASIC CAM Subsystem Tests : Begin
POST: PortASIC CAM Subsystem Tests : End, Status Passed

POST: No Cable found on stack port 1
POST: No Cable found on stack port 2

POST: PortASIC Stack Port Loopback Tests : Begin
POST: PortASIC Stack Port Loopback Tests : End, Status Passed

POST: PortASIC Port Loopback Tests : Begin
POST: PortASIC Port Loopback Tests : End, Status Passed

Election Complete
Switch 1 booting as Master
Waiting for Port download. Complete

A summary of U.S. laws governing Cisco cryptographic products may be found at:
Export Compliance Product Report Application

If you require further assistance please contact us by sending email to
[email protected] .

cisco WS-C3750G-24TS (PowerPC405) processor (revision H0) with 118784K/12280K by tes of memory.
Processor board ID CAT0916Y04G
Last reset from power-on
1 Virtual Ethernet interface
28 Gigabit Ethernet interfaces
The password-recovery mechanism is enabled.

512K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address : 00:13:C4:44:80:80
Motherboard assembly number : 73-7058-12
Power supply part number : 341-0045-01
Motherboard serial number : CAT091605VP
Power supply serial number : LIT091003WE
Model revision number : H0
Motherboard revision number : A0
Model number : WS-C3750G-24TS-S
System serial number : CAT0916Y04G
Hardware Board Revision Number : 0x09

Switch Ports Model SW Version SW Image * 1 28 WS-C3750G-24TS 12.2(25)SEB1 C3750-IPBASEK9-M

Failed to generate persistent self-signed certificate.
Secure server will use temporary self-signed certificate.

Press RETURN to get started!

00:01:25: %STACKMGR-6-SWITCH_ADDED: Switch 1 has been ADDED to the stack
00:01:26: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state t o down
00:01:28: %SPANTREE-5-EXTENDED_SYSID: Extended SysId enabled for type vlan
00:01:30: %SYS-5-CONFIG_I: Configured from memory by console
00:01:30: %STACKMGR-6-SWITCH_READY: Switch 1 is READY
00:01:30: %STACKMGR-6-STACK_LINK_CHANGE: Stack Port 1 Switch 1 has changed to st ate DOWN
00:01:30: %STACKMGR-6-STACK_LINK_CHANGE: Stack Port 2 Switch 1 has changed to st ate DOWN
00:01:30: %STACKMGR-6-MASTER_READY: Master Switch 1 is READY
00:01:30: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port 65564 has bad c rc
00:01:30: %PM-4-ERR_DISABLE: gbic-invalid error detected on Gi1/0/28, putting Gi 1/0/28 in err-disable state
00:01:30: %SYS-5-RESTART: System restarted —
Cisco IOS Software, C3750 Software (C3750-IPBASEK9-M), Version 12.2(25)SEB1, REL EASE SOFTWARE (fc1)
Copyright (c) 1986-2005 by Cisco Systems, Inc.
Compiled Sat 30-Apr-05 02:33 by yenanh
Switch>
Switch>enable
Switch#config t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#inter giga1/0/28
Switch(config-if)#keep
Switch(config-if)#keepalive 10
Switch(config-if)#exit
Switch(config)#exit
Switch#wr
00:09:17: %SYS-5-CONFIG_I: Configured from console by consoleme
Translating «wrme». domain server (255.255.255.255)
% Unknown command or computer name, or unable to find computer address
Switch#
Switch#
Switch#copy
Switch#copy ru
Switch#copy running-config st
Switch#copy running-config startup-config
Destination filename [startup-config]?
Building configuration.
[OK]
Switch#
Switch#
Switch#
Switch#config t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#inter giga1/0/28
Switch(config-if)#shut
Switch(config-if)#no
00:09:58: %LINK-5-CHANGED: Interface GigabitEthernet1/0/28, changed state to administratively downshut
Switch(config-if)#
00:10:02: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port 65564 has bad crc
00:10:02: %PM-4-ERR_DISABLE: gbic-invalid error detected on Gi1/0/28, putting Gi1/0/28 in err-disable state
00:10:04: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/28, changed state to down

Switch>$col on Interface Vlan1, changed state t o down
00:01:26: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state t^ o down

% Invalid input detected at ‘^’ marker.

Switch>$SPANTREE-5-EXTENDED_SYSID: Extended SysId enabled for type vlan
00:01:28: %SPANTREE-5-EXTENDED_SYSID: Extended SysId enabled for type vlan
^
% Invalid input detected at ‘^’ marker.

Switch>00:01:30: %SYS-5-CONFIG_I: Configured from memory by console
^
% Invalid input detected at ‘^’ marker.

Switch>00:01:30: %STACKMGR-6-SWITCH_READY: Switch 1 is READY
^
% Invalid input detected at ‘^’ marker.

Switch>$Stack Port 1 Switch 1 has changed to st ate DOWN
00:01:30: %STACKMGR-6-STACK_LINK_CHANGE: Stack Port 1 Switch 1 has changed to st^ ate DOWN

% Invalid input detected at ‘^’ marker.

Switch>$Stack Port 2 Switch 1 has changed to st ate DOWN
00:01:30: %STACKMGR-6-STACK_LINK_CHANGE: Stack Port 2 Switch 1 has changed to st^ ate DOWN

% Invalid input detected at ‘^’ marker.

Switch>00:01:30: %STACKMGR-6-MASTER_READY: Master Switch 1 is READY
^
% Invalid input detected at ‘^’ marker.

Switch>$CRC_ERROR: GBIC in port 65564 has bad c rc
00:01:30: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port 65564 has bad c^ rc

% Invalid input detected at ‘^’ marker.

Switch>$i1/0/28, putting Gi 1/0/28 in err-disable state
00:01:30: %PM-4-ERR_DISABLE: gbic-invalid error detected on Gi1/0/28, putting Gi^ 1/0/28 in err-disable state

% Invalid input detected at ‘^’ marker.

Switch>00:01:30: %SYS-5-RESTART: System restarted —
^
% Invalid input detected at ‘^’ marker.

Switch>$n 12.2(25)SEB1, REL EASE SOFTWARE (fc1)
Cisco IOS Software, C3750 Software (C3750-IPBASEK9-M), Version 12.2(25)SEB1, REL ^ EASE SOFTWARE (fc1)

% Invalid input detected at ‘^’ marker.

Switch>Copyright (c) 1986-2005 by Cisco Systems, Inc.
^
% Invalid input detected at ‘^’ marker.

Switch>Compiled Sat 30-Apr-05 02:33 by yenanh
^
% Invalid input detected at ‘^’ marker.

Switch>$abitEthernet1/0/23, changed state to up
00:01:33: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/23,^ changed state to up

% Invalid input detected at ‘^’ marker.

Switch>$LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to up
00:01:34: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/23, changed state to up
^
% Invalid input detected at ‘^’ marker.

Switch>$col on Interface Vlan1, changed state t o up
00:02:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state t^ o up

% Invalid input detected at ‘^’ marker.

Switch>
Switch>
Switch>
Switch>
Switch>
Switch>
Switch>
Switch>
Switch>
Switch>
Switch>
Switch>
Switch>
Switch>enable
Switch#config t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#inter giga1/0/28
Switch(config-if)#keep
Switch(config-if)#keepalive 10
Switch(config-if)#exit
Switch(config)#exit
Switch#wr
00:09:17: %SYS-5-CONFIG_I: Configured from console by consoleme
Translating «wrme». domain server (255.255.255.255)
% Unknown command or computer name, or unable to find computer address
Switch#
Switch#
Switch#copy
Switch#copy ru
Switch#copy running-config st
Switch#copy running-config startup-config
Destination filename [startup-config]?
Building configuration.
[OK]
Switch#
Switch#
Switch#
Switch#config t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#inter giga1/0/28
Switch(config-if)#shut
Switch(config-if)#no
00:09:58: %LINK-5-CHANGED: Interface GigabitEthernet1/0/28, changed state to administratively downshut
Switch(config-if)#
00:10:02: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port 65564 has bad crc
00:10:02: %PM-4-ERR_DISABLE: gbic-invalid error detected on Gi1/0/28, putting Gi1/0/28 in err-disable state
00:10:04: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/28, changed state to down
00:13:57: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port 65564 has bad crc
Switch(config-if)#
Switch(config-if)#
Switch(config-if)#
Switch(config-if)#
00:15:17: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port 65562 has bad crc
00:15:17: %PM-4-ERR_DISABLE: gbic-invalid error detected on Gi1/0/26, putting Gi1/0/26 in err-disable state
00:15:37: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port 65561 has bad crc
00:15:37: %PM-4-ERR_DISABLE: gbic-invalid error detected on Gi1/0/25, putting Gi1/0/25 in err-disable state

Switch con0 is now available

Press RETURN to get started.

00:24:20: %SYS-5-CONFIG_I: Configured from console by console
Switch>
Switch>
Switch>
Switch>
Switch>
Switch>enable
Switch#show ip inter br
Interface IP-Address OK? Method Status Protocol
Vlan1 unassigned YES NVRAM up up
Vlan100 192.168.225.31 YES NVRAM up down
GigabitEthernet1/0/1 unassigned YES unset down down
GigabitEthernet1/0/2 unassigned YES unset down down
GigabitEthernet1/0/3 unassigned YES unset down down
GigabitEthernet1/0/4 unassigned YES unset down down
GigabitEthernet1/0/5 unassigned YES unset down down
GigabitEthernet1/0/6 unassigned YES unset down down
GigabitEthernet1/0/7 unassigned YES unset down down
GigabitEthernet1/0/8 unassigned YES unset down down
GigabitEthernet1/0/9 unassigned YES unset down down
GigabitEthernet1/0/10 unassigned YES unset down down
GigabitEthernet1/0/11 unassigned YES unset down down
GigabitEthernet1/0/12 unassigned YES unset down down
GigabitEthernet1/0/13 unassigned YES unset down down
GigabitEthernet1/0/14 unassigned YES unset down down
GigabitEthernet1/0/15 unassigned YES unset down down
GigabitEthernet1/0/16 unassigned YES unset down down
GigabitEthernet1/0/17 unassigned YES unset down down
GigabitEthernet1/0/18 unassigned YES unset down down
GigabitEthernet1/0/19 unassigned YES unset down down
GigabitEthernet1/0/20 unassigned YES unset down down
GigabitEthernet1/0/21 unassigned YES unset down down
GigabitEthernet1/0/22 unassigned YES unset down down
GigabitEthernet1/0/23 unassigned YES unset up up
GigabitEthernet1/0/24 unassigned YES unset down down
GigabitEthernet1/0/25 unassigned YES unset down down
GigabitEthernet1/0/26 unassigned YES unset down down
GigabitEthernet1/0/27 unassigned YES unset down down
GigabitEthernet1/0/28 unassigned YES unset down down
Port-channel1 unassigned YES unset down down
Switch#
Switch#
Switch#
Switch#
Switch#
Switch#
Switch#

ProCurve J9148A 2910al-48G-PoE Switch
Software revision W.14.49

RESTRICTED RIGHTS LEGEND

Use, duplication, or disclosure by the Government is subject to restrictions
as set forth in subdivision (b) (3) (ii) of the Rights in Technical Data and
Computer Software clause at 52.227-7013.

HEWLETT-PACKARD COMPANY, 3000 Hanover St., Palo Alto, CA 94303

We’d like to keep you up to date about:
* Software feature updates
* New product announcements
* Special events

Please register your products now at: www.ProCurve.com

Smith-MDF# show config

; J9148A Configuration Editor; Created on release #W.14.49

hostname «Smith-MDF»
module 1 type J9148A
interface 25
disable
exit
interface 46
disable
exit
interface 48
disable
exit
trunk 47 Trk2 LACP
ip default-gateway 192.168.225.1
ip routing
vlan 1
name «DATA-vlan»
untagged 25-26,44,48
no untagged 1-24,27-43,45-46,Trk2
no ip address
exit
vlan 2
name «smith-camera’s»
untagged 35-36,39-40
ip address 192.200.102.1 255.255.255.224
exit
vlan 4
name «disabled-ports»
untagged 46
no ip address
exit
vlan 15
name «Wireless»
untagged 30-34
ip helper-address 172.16.35.8
ip address 172.16.35.2 255.255.255.224
exit
vlan 5
name «dell switch»
untagged 37-38,45
ip helper-address 192.168.2.6
ip address 192.168.2.5 255.255.255.0
exit
vlan 100
name «Primary-Vlan»
untagged 1-24,27-29,41-43,Trk2
ip helper-address 192.168.225.1
ip address 192.168.225.15 255.255.255.192
exit
ip route 0.0.0.0 0.0.0.0 192.168.225.1
ip route 172.16.7.0 255.255.255.0 192.225.225.6
ip route 172.16.8.0 255.255.255.0 192.225.225.6
ip route 172.16.35.0 255.255.255.224 172.16.35.3
ip route 192.168.102.0 255.255.255.0 192.225.225.6
ip route 192.168.104.0 255.255.255.0 192.225.225.6
ip route 192.168.106.0 255.255.255.0 192.225.225.6
ip route 192.168.108.0 255.255.255.0 192.225.225.6
ip route 192.168.120.0 255.255.255.0 192.225.225.6
ip route 192.168.130.0 255.255.255.0 192.225.225.6
snmp-server community «public» unrestricted
spanning-tree
spanning-tree Trk2 priority 4
primary-vlan 100
management-vlan 100
no autorun
password manager

Smith-MDF#
Smith-MDF#
Smith-MDF#

Источник

Hi We are having an issue with a 3750X. 7 Ports are down showing the same error:

*Mar 1 02:20:36.791: %PHY-4-CHECK_SUM_FAILED: SFP EEPROM data check sum failed for SFP interface Gi1/0/14

*Mar 1 02:20:36.800: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi1/0/14 has bad crc

We have done shutdown and no shutdown but to no avail. Also we have tested ports with known working SFP’s and still get the same errors.

Any help would be appreciated, Thanks: Here are the error logs:

This is after inserting each GBIC

=================================

SILSSWC-WTTSL2#

*Mar 1 02:20:36.791: %PHY-4-CHECK_SUM_FAILED: SFP EEPROM data check sum failed for SFP interface Gi1/0/14

*Mar 1 02:20:36.800: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi1/0/14 has bad crc

SILSSWC-WTTSL2#

*Mar 1 02:20:41.892: %PHY-4-CHECK_SUM_FAILED: SFP EEPROM data check sum failed for SFP interface Gi1/0/15

*Mar 1 02:20:41.900: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi1/0/15 has bad crc

SILSSWC-WTTSL2#

*Mar 1 02:20:45.490: %PHY-4-CHECK_SUM_FAILED: SFP EEPROM data check sum failed for SFP interface Gi1/0/16

*Mar 1 02:20:45.499: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi1/0/16 has bad crc

SILSSWC-WTTSL2#

*Mar 1 02:20:49.064: %PHY-4-CHECK_SUM_FAILED: SFP EEPROM data check sum failed for SFP interface Gi1/0/17

*Mar 1 02:20:49.072: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi1/0/17 has bad crc

SILSSWC-WTTSL2#

*Mar 1 02:20:52.394: %PHY-4-CHECK_SUM_FAILED: SFP EEPROM data check sum failed for SFP interface Gi1/0/18

*Mar 1 02:20:52.403: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi1/0/18 has bad crc

SILSSWC-WTTSL2#

*Mar 1 02:20:55.221: %PHY-4-CHECK_SUM_FAILED: SFP EEPROM data check sum failed for SFP interface Gi1/0/19

*Mar 1 02:20:55.230: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi1/0/19 has bad crc

SILSSWC-WTTSL2#

*Mar 1 02:20:58.308: %PHY-4-CHECK_SUM_FAILED: SFP EEPROM data check sum failed for SFP interface Gi1/0/20

*Mar 1 02:20:58.317: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi1/0/20 has bad crc

SILSSWC-WTTSL2#

*Mar 1 02:21:36.602: %SFF8472-5-THRESHOLD_VIOLATION: Gi1/0/3: Tx power low alarm; Operating value: -40.0 dBm, Threshold value: -13.5 dBm.

*Mar 1 02:21:37.550: %SFF8472-5-THRESHOLD_VIOLATION: Gi1/0/6: Tx power low alarm; Operating value: -40.0 dBm, Threshold value: -13.5 dBm.

SILSSWC-WTTSL2#

*Mar 1 02:21:38.683: %SFF8472-5-THRESHOLD_VIOLATION: Gi1/0/8: Tx power low alarm; Operating value: -40.0 dBm, Threshold value: -13.5 dBm.

*Mar 1 02:21:39.152: %SFF8472-5-THRESHOLD_VIOLATION: Gi1/0/9: Tx power low alarm; Operating value: -40.0 dBm, Threshold value: -13.5 dBm.

*Mar 1 02:21:39.614: %SFF8472-5-THRESHOLD_VIOLATION: Gi1/0/10: Tx power low alarm; Operating value: -40.0 dBm, Threshold value: -13.5 dBm.

SILSSWC-WTTSL2#

*Mar 1 02:21:40.151: %SFF8472-5-THRESHOLD_VIOLATION: Gi1/0/11: Tx power low alarm; Operating value: -40.0 dBm, Threshold value: -13.5 dBm.

*Mar 1 02:21:40.520: %SFF8472-5-THRESHOLD_VIOLATION: Gi1/0/12: Tx power low alarm; Operating value: -40.0 dBm, Threshold value: -13.5 dBm.

SILSSWC-WTTSL2#

Output of ‘show log’ after inserting GBICs in ports 14 through 20.

===================================================================

*Mar 1 02:18:42.379: %SYS-5-CONFIG_I: Configured from console by vty0 (100.0.0.199)

*Mar 1 02:19:11.303: %LINK-5-CHANGED: Interface GigabitEthernet1/0/20, changed state to administratively down

*Mar 1 02:19:18.350: %PHY-4-CHECK_SUM_FAILED: SFP EEPROM data check sum failed for SFP interface Gi1/0/20

*Mar 1 02:19:18.358: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi1/0/20 has bad crc

*Mar 1 02:19:18.358: %PM-4-ERR_DISABLE: gbic-invalid error detected on Gi1/0/20, putting Gi1/0/20 in err-disable state

*Mar 1 02:19:19.734: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/20, changed state to down

*Mar 1 02:19:30.161: %SYS-5-CONFIG_I: Configured from console by vty0 (100.0.0.199)