RSCMSM through SBC_HA
RSCMSM
%RSCMSM-3-NO_SUCH_INTERFACE : [chars]: The interface doesn't exist | |
---|---|
Explanation | The interface for resource measurement doesn't exist at the time of the operation. |
Recommended Action | Check the configuration to see if that interface is there |
%RSCMSM-5-TEST_ALREADY_RUNNING : One test is already running. | |
---|---|
Explanation | there is already one test running at the same time. |
Recommended Action | Please wait for the completeness of the running test before starting another test. |
%RSCMSM-3-NO_LIST_CREATED : [chars]: Cannot create interface-based rsc list. | |
---|---|
Explanation | This failure is due to the list create operation. |
Recommended Action | Please check the memory at the moment. |
RSRB
%RSRB-4-OPTNULL : Remopened and t NULL | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If any of these messages recur, call your technical support representative for assistance. |
%RSRB-4-PEERSTAT : Peer [chars], wrong state [dec] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If any of these messages recur, call your technical support representative for assistance. |
%RSRB-4-CONNSTAT : Peer [chars], IFin, bad connection state [dec] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If any of these messages recur, call your technical support representative for assistance. |
%RSRB-4-BADLEN : Peer [chars], [chars], bad length [dec], trn [dec] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If either message recurs, call your technical support representative for assistance. |
%RSRB-3-BADVERSIONIF : IFin: [chars]: version mismatch, mine [dec], theirs [dec] | |
---|---|
Explanation | The remote end of a direct serial peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date. |
Recommended Action | Call your technical support representative for an update. |
%RSRB-3-BADVERSIONFST : FSTin: [chars]: version mismatch, mine [dec], theirs [dec] | |
---|---|
Explanation | The remote end of a direct serial peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date. |
Recommended Action | Call your technical support representative for an update. |
%RSRB-3-BADVERSIONTCP : [chars]: [dec]/[IP_address]: version mismatch, mine [dec], theirs [dec] | |
---|---|
Explanation | The remote end of a TCP remote peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date. |
Recommended Action | Call your technical support representative for an update. |
%RSRB-3-IFERR : [chars]: [chars]: [chars], op [hex], len [dec], trn [dec] | |
---|---|
Explanation | The remote end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration. |
Recommended Action | Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn. |
%RSRB-3-SENDPUNTIF : [chars]: sent [chars] to [chars] | |
---|---|
Explanation | The local end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration. |
Recommended Action | Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. |
%RSRB-3-FSTERR : [chars]: [chars]: [IP_address], op [hex], len [dec], trn [dec] | |
---|---|
Explanation | The remote end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration. |
Recommended Action | Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn. |
%RSRB-3-SENDPUNTFST : [chars]: sent [chars] to [chars] | |
---|---|
Explanation | The local end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration. |
Recommended Action | Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. |
%RSRB-4-BADLENIP : Peer [dec]/[IP_address], [chars], bad length [dec], trn [dec] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If either message recurs, call your technical support representative for assistance. |
%RSRB-4-ILLPEER : Peer [chars] [%-08x], illegal state [dec] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If either of these messages recur, call your technical support representative for assistance. |
%RSRB-4-CONNILLSTATE : Peer [chars], CONN, illegal state [dec] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If any of these messages recur, call your technical support representative for assistance. |
%RSRB-4-CONIPST : Peer [dec]/[IP_address], CONN, illegal state [dec] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If any of these messages recur, call your technical support representative for assistance. |
%RSRB-3-HDRNOVRP : Peer [IP_address], HDR, no vrp | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If any of these messages recur, call your technical support representative for assistance. |
%RSRB-3-HDRVRP : Peer [dec]/[IP_address], HDR, vrp state wrong, [dec] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If any of these messages recur, call your technical support representative for assistance. |
%RSRB-4-HDRRECV : Peer [dec]/[IP_address], HDR, recv state invalid, not empty [dec] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If any of these messages recur, call your technical support representative for assistance. |
%RSRB-3-NOMEMORY : Unit [dec], no memory for [chars] | |
---|---|
Explanation | The requested operation could not be accomplished because of a low memory condition. |
Recommended Action | Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. |
%RSRB-4-LOCAL : Unit [dec], local/vring set simultaneously, vrn [dec] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If either of these messages recur, call your technical support representative for assistance. |
%RSRB-3-NOTREM : Null idb and not remote | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If any of these messages recur, call your technical support representative for assistance. |
%RSRB-4-BADVRE : Bad vre type | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If any of these messages recur, call your technical support representative for assistance. |
%RSRB-4-RNGXFAIL : Ring exchange failure, resetting peer: [chars] | |
---|---|
Explanation | The RSRB peer initiation logic failed due to a memory shortage or congestion condition. |
Recommended Action | The problem should clear and the peers should re-open without operator intervention. |
RSVP
%RSVP-5-CLEAR_COUNTERS : Clear RSVP message counters by [chars] | |
---|---|
Explanation | The RSVP message counters have been cleared |
Recommended Action | No action is required. |
%RSVP-5-NO_MATCH_IF_ID_HOP : Received PATH ([IP_address]_[int]->[IP_address]_[int]) - Failed to find interface from IF_ID HOP from neighbor [IP_address] | |
---|---|
Explanation | The interface id in the HOP object does not match any of this node's interfaces. |
Recommended Action | Verify the configuration. |
%RSVP-3-BAD_RMSG_TIMER : Inconsistent RSVP reliable message timer | |
---|---|
Explanation | The summary refresh timer may be blocked. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative. |
%RSVP-3-BAD_RSVP_MSG_RCVD_LEN : RSVP Message had a bad length; ip data len: [dec] rsvp len: [dec] | |
---|---|
Explanation | The router received an RSVP message with the length field set to an unexpected value. Be aware that a bad length error may also be a side-effect of packet corruption. |
Recommended Action | LOG_BAD_RSVP_MSG_ACTION Copy the error message(s) exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data that may help identify the nature of the error and send this information to your Cisco technical support representative. |
%RSVP-3-BAD_RSVP_MSG_RCVD_MALFORMED : RSVP Message was malformed; traversed objects len: [dec] rsvp msg len: [dec] | |
---|---|
Explanation | An error was encountered during validation of the objects in an RSVP message received by the router. |
Recommended Action | LOG_BAD_RSVP_MSG_ACTION Copy the error message(s) exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data that may help identify the nature of the error and send this information to your Cisco technical support representative. |
%RSVP-3-BAD_RSVP_MSG_RCVD_VER : RSVP Message had a bad version: [dec] | |
---|---|
Explanation | The router received an RSVP message with the version field set to an unexpected value. |
Recommended Action | LOG_BAD_RSVP_MSG_ACTION Copy the error message(s) exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data that may help identify the nature of the error and send this information to your Cisco technical support representative. |
%RSVP-3-BAD_RSVP_MSG_RCVD_CHECKSUM : RSVP Message had a bad checksum: [dec] foo: [dec] | |
---|---|
Explanation | The router received an RSVP message with the checksum field incorrectly set. Bad checksums would most likely be caused by packet corruption outside RSVP. Be aware that corruption reported by RSVP might also be affecting other protocols on the router and might explain other unexpected non-RSVP protocol behavior. Please attempt to track down the source of the corruption. |
Recommended Action | LOG_BAD_RSVP_MSG_ACTION Copy the error message(s) exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data that may help identify the nature of the error and send this information to your Cisco technical support representative. |
%RSVP-3-BAD_RSVP_MSG_RCVD_TYPE : RSVP Message had a bad type: [dec] | |
---|---|
Explanation | The router received an incorrect RSVP message. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative. |
%RSVP-3-IP_HDR : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] | |
---|---|
Explanation | This is an auxiliary message to several packet-related messages. It displays the contents of 8 32-bit words immediately following the start of the IPv4/v6 header, in hex format. To decode the information in the IPv4 and IPv6 headers, please refer to RFCs 791 and 2460. |
Recommended Action | Decode the information in the IPv4 and IPv6 headers to determine the source of the RSVP message. |
%RSVP-3-MSG_1 : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] | |
---|---|
Explanation | This is an auxiliary message to several packet-related messages. It displays the contents of the first 8 32-bit words immediately following the start of the RSVP header, in hex format. To decode the information in the RSVP header, please refer to RFC 2205. |
Recommended Action | If you need additional information about the packet, then turn on debug ip rsvp dump-messages <msg type> [hex] and try to capture the bad message. If you use the hex version of this command, you can convert it to pcap format with the offline tool text2pcap and then view the contents with another offline tool such as ethereal. |
%RSVP-3-MSG_2 : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] | |
---|---|
Explanation | This is an auxiliary message to several packet-related messages. It displays the contents of the next 8 32-bit words following those that are printed by the MSG_1 message above, in hex format. To decode the information in these 32-bit words, please refer to RFC 2205. |
Recommended Action | If you need additional information about the packet, then turn on debug ip rsvp dump-messages <msg type> [hex] and try to capture the bad message. If you use the hex version of this command, you can convert it to pcap format with the offline tool text2pcap and then view the contents with another offline tool such as ethereal. |
%RSVP-3-BAD_RSVP_MSG_RCVD_OBJ_LEN : Received a bad RSVP message, num objs: [dec] obj len: [dec] msg_len: [dec] | |
---|---|
Explanation | An error was encountered during validation of the objects in an RSVP message received by the router. The number of objects in the RSVP message was found to be greater than the maximum expected number or the size of an object was found to be smaller than the minimum expected size. |
Recommended Action | LOG_BAD_RSVP_MSG_ACTION Copy the error message(s) exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data that may help identify the nature of the error and send this information to your Cisco technical support representative. |
%RSVP-3-CONSISTENCY : [chars]: [chars] [chars] [chars] | |
---|---|
Explanation | An action attempted by the rsvp implementation encountered an unexpected condition |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative. |
%RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_NO_SA : [chars] message from [IP_address] discarded: no security association for [IP_address] - no RSVP security key configured or no memory left. | |
---|---|
Explanation | The router received an RSVP message that contained a secure hash but dropped the message because the router was not able to create a security association for the sending system. |
Recommended Action | Check the configuration on the router to make sure that RSVP has access to a security key for the sending system. If such a key is configured, then check to see if the router has run out of memory. |
%RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_DIGEST : [chars] message from [IP_address] discarded - incorrect message digest | |
---|---|
Explanation | The router received an RSVP message that contained a different secure hash from the one computed by the router. RSVP discarded the message because the message may have come from an untrusted source. |
Recommended Action | Check the configuration on the router and the sending system to make sure they are using the correct security key and secure hash algorithm. |
%RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_WIN : [chars] message from [IP_address] discarded - seq #[int] outside authentication window | |
---|---|
Explanation | The router received an RSVP message whose authentication sequence number is less than the lower limit of the out-of-order window. RSVP discarded the message because an untrusted source may be (unsuccessfully) attempting an RSVP message replay attack. |
Recommended Action | It is possible that a trusted source is sending a burst of reordered RSVP messages that is too large for the authentication window size. If you can verify that the source is trusted and its messages are being sent in large reordered bursts, use the ip rsvp authentication window-size command to increase the window size on the receiving router. It is also possible that a trusted source has rebooted and its clock has gone backward in time; in this case, the source should be configured to synchronize its clock with an NTP server. Otherwise, the sender could be an untrusted source (unsuccessfully) attempting an RSVP message replay attack; try to find and disable the untrusted source. |
%RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_DUP : [chars] message from [IP_address] discarded - authentication seq #[int] is a duplicate | |
---|---|
Explanation | The router received an RSVP message with an authentication sequence number that has already been seen. RSVP discarded the message because an untrusted source may be (unsuccessfully) attempting an RSVP message replay attack. |
Recommended Action | If you can verify that the source is trusted, it is possible that the source has rebooted and its clock has gone backward in time; in this case, the source should be configured to synchronize its clock with an NTP server. Otherwise, the sender could be an untrusted source (unsuccessfully) attempting an RSVP message replay attack; try to find and disable the untrusted source. |
%RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_COOKIE : [chars] message from [IP_address] discarded - challenge failed for key ID %*s | |
---|---|
Explanation | The router sent an RSVP message to challenge the untrusted source to compute a secure hash on a random piece of data and return the hash with the same data, but the source did not return the expected data. RSVP discarded the response because the untrusted source may be (unsuccessfully) attempting an RSVP challenge response replay attack. |
Recommended Action | If you can verify that the source is trusted, it is possible that the source has malfunctioned; in this case, copy the error message exactly as it appears on the console or in the system log, issue the show tech-support rsvp command to gather data which may help identify the nature of the error, and send this information to your Cisco technical support representative. Otherwise, try to find and disable the untrusted source. |
%RSVP-3-RSVP_MSG_AUTH_CHALLENGE_TIMEOUT : No response to challenge issued to [IP_address] for key ID %*s | |
---|---|
Explanation | The router sent an RSVP message to challenge the untrusted source to compute a secure hash on a random piece of data and return the hash with the same data, but the source did not reply. The source may have crashed or lost its network connection. However, it is also possible that the source was (unsuccessfully) attempting to replay an RSVP message before the challenge and gave up when it saw the challenge from the router |
Recommended Action | If you can verify that the source is trusted, try to determine if it has crashed or lost its network connection and then restore network connectivity to it. If the source repeatedly crashes when challenged, a temporary workaround might be to disable challenges on the router by issuing a no ip rsvp authentication challenge command until the problem on the source is resolved. Otherwise, assume the source is untrusted; try to find and disable it. |
%RSVP-3-RSVP_MSG_AUTH_TYPE_MISMATCH : [chars] message from [IP_address] discarded - authentication algorithm mismatch | |
---|---|
Explanation | The router received an RSVP message from a source that required authentication but the received message was using the wrong authentication algorithm. |
Recommended Action | Issue a show ip rsvp authentication detail <source> command on the router to display the expected algorithm type. Then find the source and change its configuration to match. |
%RSVP-5-RSVP_AUTH_ONE_KEY_EXPIRED : Key (ID) [int] in chain [chars] has expired | |
---|---|
Explanation | The router has detected that one key in a RSVP key chain has expired and that RSVP has switched to the next unexpired key in that chain. |
Recommended Action | Update the key chain by changing the text and expiration time(s) for the expired key. |
%RSVP-2-RSVP_AUTH_KEY_CHAIN_EXPIRED : All the keys in chain [chars] have expired - please update the key chain now | |
---|---|
Explanation | The router attempted to use a key in an RSVP key chain but discovered that all the keys in the chain have expired. The router will attempt to to find another suitable key. If no other suitable per-neighbor key can be found, the router will attempt to use key (chain) configured for the interface over which the authenticated RSVP message is being sent or received. |
Recommended Action | Update the key chain by updating the text and expiration time(s) for the expired key(s). |
%RSVP-1-RSVP_AUTH_NO_KEYS_LEFT : No valid keys left for [IP_address] | |
---|---|
Explanation | The router attempted to use a key in an RSVP key chain but discovered that all the keys in the chain have expired and no other per-neighbor or per-interface keys are available for the specified neighbor. The router will continue to use the last key in the chain rather than revert to an unauthentication condition. However, the specified neighbor router may start discarding RSVP messages at that point and reservations with that neighbor may eventually time out. |
Recommended Action | Update the key chain by updating the text and expiration time(s) for the expired key(s). |
%RSVP-4-RSVP_AUTH_DUPLICATE_KEY_ID : Key chains [chars] and [chars] contain duplicate key ID [int] | |
---|---|
Explanation | An attempt is being made to add a new key identifier to a key chain in the router configuration but RSVP detected that this identifier is found in another key chain already assigned to RSVP. Since key identifiers must be unique across all the key chains used by RSVP, RSVP will not use the keys with this identifier in all such key chains. This could cause RSVP authentication to fail in some cases. |
Recommended Action | Update the listed key chain(s) so they use different key identifiers. |
%RSVP-5-RSVP_AUTH_KEY_ACL_CHANGE : Key chain [chars] [chars] for [IP_address] because ACL [chars] [chars] | |
---|---|
Explanation | The ACL specified in the message text associates the key chain specified in the message text with a set of RSVP neighbors. RSVP uses the specified key chain to authenticate each RSVP message exchanged with that set of RSVP neighbors after the association is configured. Subsequently, the specified ACL has been reconfigured such that the key chain association is no longer valid for one or more RSVP neighbors in the set. This causes RSVP to search the configuration for another suitable key chain to use with those neighbors. If no such key chain is found, RSVP will no longer be able to provide authentication for messages exchanged with those RSVP neighbors. This causes RSVP to discard RSVP messages from that set of neighbors. Because this may ultimately lead to loss of RSVP functionality with those neighbors, RSVP generates this system message. This system message may also be generated if the ACL is subsequently changed so that it re-associates RSVP neighbors with the specified key chain. If RSVP is not using another key chain for the set of RSVP neighbors specified by the ACL, RSVP will begin using the specified key chain to exchange authenticated RSVP messages with that set of RSVP neighbors, potentially restoring RSVP functionality with those neighbors. |
Recommended Action | If the ACL change unexpectedly caused authentication to be disabled or enabled for one or more RSVP neighbors, undo the ACL change so that RSVP authentication is not impacted. |
%RSVP-3-RSVP_MFI_RECOVERY : RSVP calculated Recovery Time is longer than TE Rewrite Hold-Time registered with LSD. Some LSPs may not be be recovered. | |
---|---|
Explanation | TE registered a maximum cutover time with the LSD that is less than the time it may actually take to recover all LSPs. As a result, more than usual traffic loss may occur on some LSPs during recovery |
Recommended Action | Make note of the number of Checkpointed LSPs in the RSVP HA database by issuing the command show ip rsvp high-availability database internal . This number likely exceeds the hard defined limit of the number of recoverable LSPs. Provide this information to Cisco technical support representative. |
RSVP_SYNC_ISSU
%RSVP_SYNC_ISSU-2-INIT : RSVP_SYNC ISSU client initialization failed to [chars]. Error: [dec] ([chars]) | |
---|---|
Explanation | The RSVP_SYNC ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade. |
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. |
%RSVP_SYNC_ISSU-3-TRANSFORM_FAIL : RSVP_SYNC ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars]) | |
---|---|
Explanation | The RSVP_SYNC ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the RSVP_SYNC state between the active device and the standby device is not identical. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated version <session_id>) |
%RSVP_SYNC_ISSU-3-MSG_NOT_OK : RSVP_SYNC ISSU client 'Message Type [dec]' is not compatible | |
---|---|
Explanation | The RSVP_SYNC ISSU client received an incompatible message from the peer device. The message cannot be processed. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu message group <client_id> and show issu session <client_id> and show issu negotiated version <session_id>) |
%RSVP_SYNC_ISSU-3-MSG_SIZE : RSVP_SYNC ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars]) | |
---|---|
Explanation | The RSVP_SYNC ISSU client failed to calculate the MTU for the specified message. The RSVP_SYNC ISSU client is not able to send the message to the standby device. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu message group <client_id> and show issu session <client_id> and show issu negotiated version <session_id>) |
%RSVP_SYNC_ISSU-3-INVALID_SESSION : RSVP_SYNC ISSU client does not have a valid registered session. | |
---|---|
Explanation | The RSVP_SYNC ISSU client does not have a valid registered session. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id>) |
%RSVP_SYNC_ISSU-2-SESSION_REGISTRY : RSVP_SYNC ISSU client failed to register session information. Error: [dec] ([chars]) | |
---|---|
Explanation | The RSVP_SYNC ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id>) |
%RSVP_SYNC_ISSU-3-SESSION_UNREGISTRY : RSVP_SYNC ISSU client failed to unregister session information. Error: [dec] ([chars]) | |
---|---|
Explanation | The RSVP_SYNC ISSU client failed to unregister session information. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated capability <session_id>) |
%RSVP_SYNC_ISSU-2-SESSION_NEGO : RSVP_SYNC ISSU client encountered unexpected client nego_done. Error: [dec] ([chars]) | |
---|---|
Explanation | An ISSU-compliant client transitions through a series of internal states. The RSVP_SYNC ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated capability <session_id>) |
%RSVP_SYNC_ISSU-2-SEND_NEGO_FAILED : RSVP_SYNC ISSU client failed to send negotiation message. Error: [dec] ([chars]) | |
---|---|
Explanation | The RSVP_SYNC ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client) |
%RSVP_SYNC_ISSU-2-GET_BUFFER : RSVP_SYNC ISSU client failed to get buffer for message. Error: [dec] ([chars]) | |
---|---|
Explanation | The RSVP_SYNC ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client) |
%RSVP_SYNC_ISSU-3-MSG_NOT_COMPATIBLE_WITH_PEER : 'Message Type [dec]' is not supported by RSVP_SYNC ISSU client at peer | |
---|---|
Explanation | The RSVP_SYNC ISSU client at the peer supervisor is not compatible for this message type. The RSVP_SYNC client will be marked as incompatible with the peer. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu message group <client_id> and show issu session <client_id> and show issu negotiated version <session_id>) |
%RSVP_SYNC_ISSU-3-CAP_NOT_COMPATIBLE : RSVP_SYNC ISSU client capability exchange result incompatible. | |
---|---|
Explanation | The RSVP_SYNC ISSU client capability exchange have negotiated as incompatible with the peer. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu negotiated capability <Session_ID>) |
%RSVP_SYNC_ISSU-3-CAP_INVALID_SIZE : RSVP_SYNC ISSU client capability list is empty. | |
---|---|
Explanation | The RSVP_SYNC ISSU client capability exchange list size is invalid. |
Recommended Action | LOG_STD_SH_CMD_ACTION( show issu capability entires <Client_ID>) |
RTMGR
%RTMGR-3-GENERAL : [chars] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If this message recurs, copy the error message exactly as it appears on the console or in the system log. 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. |
%RTMGR-3-UNLOCK_ERR : Attempt to unlock active topology '[chars]' (in VRF [chars] [chars]) | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If this message recurs, copy the error message exactly as it appears on the console or in the system log. 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. |
%RTMGR-3-VRF_ERR : Topology VRF [chars] creation error | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If this message recurs, copy the error message exactly as it appears on the console or in the system log. 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. |
%RTMGR-3-TOPO_VRF_ERR : Topology [chars] address-family [chars] has no VRF entry | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If this message recurs, copy the error message exactly as it appears on the console or in the system log. 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. |
%RTMGR-3-TOPO_IPMCAST_BASE_ERR : Failed to create the base mcast topology in vrf [chars] with error [chars] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If this message recurs, copy the error message exactly as it appears on the console or in the system log. 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. |
%RTMGR-3-TOPO_INTF_CTX : Interface [chars] address-family [chars] topology context is NULL or the function [chars] is not set | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If this message recurs, copy the error message exactly as it appears on the console or in the system log. 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. |
%RTMGR-3-TOPO_SYNC_ERR : Failed to duplicate active topology on standby (rc=[dec]), id [hex] [chars] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If this message recurs, copy the error message exactly as it appears on the console or in the system log. 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. |
%RTMGR-3-TOPO_UNSUPPORTED_AFI : Attempt to enable unsupported AFI ([hex]) | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If this message recurs, copy the error message exactly as it appears on the console or in the system log. 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. |
%RTMGR-3-TOPO_AF_ENABLE_ERR : Failed to enable AF base topology [chars] (error [chars]) | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If this message recurs, copy the error message exactly as it appears on the console or in the system log. 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. |
%RTMGR-3-TOPO_AFI_CTX : Topology address-family [chars] context block is NULL. | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If this message recurs, copy the error message exactly as it appears on the console or in the system log. 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. |
%RTMGR-3-TOPO_INTF_INV_VRFID : Interface [chars] with invalid vrfid [hex] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If this message recurs, copy the error message exactly as it appears on the console or in the system log. 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. |
%RTMGR-3-TOPO_CACHE_INIT_ERROR : ([chars]) | |
---|---|
Explanation | cached topo initialization failure |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%RTMGR-3-TOPO_CACHE_ADD_ERROR : ([chars]) | |
---|---|
Explanation | cached topo entry creation failure |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%RTMGR-3-TOPO_CACHE_ERROR : ([chars]) | |
---|---|
Explanation | cached topo failure |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%RTMGR-3-TOPO_LCKMGR_INIT_ERROR : ([chars]) manager init failure | |
---|---|
Explanation | Topology lock manager initialization failure |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%RTMGR-3-TOPO_LCKMGR_GET_LOCK_COUNT_ERROR : Failed to get lock count for topology([chars]) | |
---|---|
Explanation | Topology lock manager get lock count failure |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%RTMGR-3-TOPO_HA_LOCK_IVRF_TOPO : Acquired a HA lock on an iVRF topology([chars]) | |
---|---|
Explanation | Topology HA lock shouldn't be applied in an iVRF topology |
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. |
%RTMGR-3-TOPO_UNSUPPORTED_API : Topology API [chars] is unsupported due to [chars] | |
---|---|
Explanation | Topology API is unavailable |
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. |
%RTMGR-3-TOPO_PROCESS_INIT_ERROR : Topology process init failed due to [chars] | |
---|---|
Explanation | Topology process initialization failed |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%RTMGR-3-TOPO_SUBMODE_ERROR : Unexpected transition from parser submode '[chars]' | |
---|---|
Explanation | An error occured while parsing the topology command |
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. |
RTT
%RTT-4-DuplicateEvent : IP SLAs [dec]: Duplicate event received. Event number [dec] | |
---|---|
Explanation | IP SLAs process has received a duplicate event |
Recommended Action | This is only a warning message. If this recurs, enter the command <CmdBold>show ip sla configuration<NoCmdBld> and copy the output of the command. Copy the message 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 along with information about the application that is configuring and polling the Service Assurance Agent probes. |
%RTT-3-IPSLANOPROCESS : IP SLAs: Cannot create a new process | |
---|---|
Explanation | IP SLAs is unable to start a new process, and may not be running. |
Recommended Action | Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. |
%RTT-3-IPSLANEGATIVEVALUE : IP SLAs([dec]): Negative Value for [chars] | |
---|---|
Explanation | IP SLAs statistics has generated an error message. |
Recommended Action | Contact your Cisco technical support representative |
%RTT-3-IPSLAPROBENOTFOUND : IP SLAs: Error deleting the probe | |
---|---|
Explanation | Trying to delete a probe which does not exist |
Recommended Action | Contact your Cisco technical support representative |
%RTT-3-IPSLATHRESHOLD : IP SLAs([dec]): Threshold [chars] for [chars] | |
---|---|
Explanation | This informational message logs threshold violations in the Service Assurance Agent probes. This messages appears when the ip sla logging trap command is entered |
Recommended Action | If this message is not necessary, enter the no ip sla logging trap command to disable logging. Otherwise, no action is required |
%RTT-3-IPSLAINITIALIZEFAIL : IP SLAs: Failed to initialize, IP SLAs functionality will not work | |
---|---|
Explanation | IP SLAs failed to initialize. This condition is caused by either a timer wheel timer functionality init that failed or a process that could not be created. A likely cause of this condition is that sufficient memory is not available to complete the task. |
Recommended Action | Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. LOG_STD_REDUCE_ACTION |
%RTT-3-IPSLATWINITFAIL : IP SLAs: Generic Timer wheel timer functionality failed to initialize | |
---|---|
Explanation | IP SLAs could not initialize the timer wheel. |
Recommended Action | Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. LOG_STD_REDUCE_ACTION |
%RTT-4-IPSLACLOCKNOTSET : IP SLAs Probe(s) could not be scheduled because clock is not set. | |
---|---|
Explanation | One or more IP SLAs probes could not be scheduled because system clock is not set. |
Recommended Action | Ensure that the system clock is functional by using Network Time Protocol or another mechanism. |
%RTT-4-IPSLASCHEDCONFIGFAIL : IP SLAs Probe [dec]: [chars] | |
---|---|
Explanation | The IP SLAs probe could not be scheduled. Either the configured starting time has already ocurred, or the starting time is invalid. |
Recommended Action | Reschedule the failed probe with a valid start time. |
%RTT-3-IPSLARESPTWINITFAIL : IP SLAs responder initialzation failed | |
---|---|
Explanation | |
Recommended Action |
%RTT-4-IPSLAENDPOINTDEREGISTER : IP SLAs end point de-registered by hub [IP_address]. | |
---|---|
Explanation | |
Recommended Action |
%RTT-4-IPSLAAUTODISCOAUTHFAIL : IP SLAs end point discovery authentication failure for spoke [IP_address]. | |
---|---|
Explanation | The IP SLAs responder initialization failed to initialize timerwheel. Because of this failure the IP SLAs probes on other routers for which this router acts as responder will not work. |
Recommended Action | Contact your Cisco technical support representative. |
%RTT-3-IPSLARESPEVQINITFAIL : IP SLAs responder initialzation failed | |
---|---|
Explanation | The IP SLAs responder initialization failed to initialize event queue. Because of this failure the IP SLAs probes on other routers for which this router acts as responder will not work. |
Recommended Action | Contact your Cisco technical support representative. |
%RTT-3-IPSLARTPAPPINITFAILED : IP SLAs rtp operation application process initialzation failed | |
---|---|
Explanation | The IP SLAs rtp operation application process failed to initialize. Because of this failure the IP SLAs rtp operations will not work. |
Recommended Action | Contact your Cisco technical support representative. |
%RTT-4-SAASCHEDCONFIGFAIL : IP SLA Monitor Probe [dec]: [chars] | |
---|---|
Explanation | The IP SLA Monitor probe could not be scheduled. Either the configured starting time has already ocurred, or the starting time is invalid. |
Recommended Action | Reschedule the failed probe with a valid start time. |
%RTT-4-SAAGRPSCHEDCONFIGFAIL : Group Schedule Entry [dec]: [chars] | |
---|---|
Explanation | The probes could not be group scheduled. Either the configured starting time has already ocurred, or the starting time is invalid. |
Recommended Action | Reschedule the group scheduling entry with a valid start time. |
%RTT-3-SAAMPLS : IP SLA Monitor([dec]): MPLS [chars] Probe [chars] [chars] for destination-address [IP_address] lsp-selector [IP_address] | |
---|---|
Explanation | This informational message logs violations in the Service Assurance Agent probes. This messages appears when the ip sla logging trap command is entered |
Recommended Action | If this message is not necessary, enter the no ip sla logging trap command to disable logging. Otherwise, no action is required |
%RTT-3-IPSLA_AQM : [chars]: [chars] | |
---|---|
Explanation | This message indicates software error in IPSLA auto qos monitor feature. |
Recommended Action | Contact your Cisco technical support representative. |
%RTT-4-OPER_TIMEOUT : condition [chars], entry number = [dec] | |
---|---|
Explanation | This message logs timeout condition in the IPSLAs operations. This message is enabled when the ip sla monitor logging trap command is entered |
Recommended Action | Ensure that the destination for the IPSLAs operation is reachable. If you do not want to log these messages for IPSLAs operations, enter the no ip sla monitor logging trap command to disable the logging |
%RTT-4-OPER_CLOSS : condition [chars], entry number = [dec] | |
---|---|
Explanation | This message logs connection loss condition in the IPSLAs operations. This message is enabled when the ip sla monitor logging trap command is entered |
Recommended Action | Ensure the the destination for the IPSLAs operation is reachable. Also ensure that the IPSLAs responder operation is configured on the destination. If you do not want to log these messages for IPSLA operations, enter the no ip sla monitor logging trap command to disable logging. |
%RTT-4-AUTOAPI : IPSLAs Auto CFG ERR: [chars]([chars]) [chars] | |
---|---|
Explanation | An error occured while configuring IPSLAs Auto parameters. Some, or all of your configurations may not have been (un)set |
Recommended Action | Please check the configuration and try again |
%RTT-4-AUTOAPIOPER : IPSLAs Auto CFG ERR: [chars]([chars])[[dec]] [chars] | |
---|---|
Explanation | An error occured while configuring IPSLAs Auto parameters. Some, or all of your configurations may not have been (un)set |
Recommended Action | Please check the configuration and try again |
%RTT-3-AUTO : Error: [chars] | |
---|---|
Explanation | An error occured while generating IPSLAs Auto operation. |
Recommended Action | Please check the configuration and try again |
%RTT-4-AUTOMEM : IPSLAs Auto MEM ERR: [chars]([chars]) [chars] | |
---|---|
Explanation | IPSLAs Auto feature failed during memory allocation |
Recommended Action | These maybe transient errors, please try again |
%RTT-4-INVALIDSRCIPADDR : Possible invalid src IP address ([IP_address]) configured. | |
---|---|
Explanation | This message appears when no source IP address is found on the host matching the one specified by the user |
Recommended Action | Unconfigure the probe and reconfigure with valid source IP address |
%RTT-3-REACTNOTIFYFAILED : entry number = [dec], reason = [chars] | |
---|---|
Explanation | IPSLAs Reaction condition was met for specified operation and one or more IPSLAs Event Publisher clients have registered interest for this condition but the notification for this occurence failed. |
Recommended Action | These maybe transient system errors and the notification may work next time. Use show ip sla event-publisher command to see which clients are registered and take action recommended by them. |
%RTT-4-REACTPARTIALEVENT : entry number = [dec], missing data = [chars] | |
---|---|
Explanation | IPSLAs Reaction Event is missing some interesting data |
Recommended Action | This could be because of IPSLAs software error. Please collect show ip sla config output and report issue to TAC |
%RTT-3-EPNOTIFYFAILED : event type = [chars], client = [chars], reason = [chars] | |
---|---|
Explanation | Notification for specified type to specified IPSLAs Event Publisher client failed |
Recommended Action | This maybe transient system error and the notification may work next time. Take the action as suggested by the identified client for loss of notification. |
%RTT-3-EPSTARTERROR : Failed to start IPSLAs Event Publisher | |
---|---|
Explanation | IPSLAs is unable to start a new process for Event Publisher. Reaction Alert notifications will not work. |
Recommended Action | Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. |
%RTT-3-EPURFTYPE : IPSLAs EventPublisher: Unknown reaction filter type for client [chars] | |
---|---|
Explanation | IPSLAs Event Publisher encountered unknown filter type while sending the reaction alert to specified client Reaction Alert notifications may continue to work for same and other clients. |
Recommended Action | Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. |
%RTT-4-EPINIT : IPSLAs Event Publisher Init Failed. Reason = [chars] | |
---|---|
Explanation | IPSLAs Event Publisher Initialization failed. The system will try to recover by doing the initialization tasks when first client subscribes to IPSLAs events. |
Recommended Action | Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. |
%RTT-4-EPAPI : IPSLAs EP API: [chars] api failed, client = [chars], reason = [chars] | |
---|---|
Explanation | IPSLAs Event Publisher API failed for reason identified |
Recommended Action | The error code is reported to API client. Take the action recommended by the client identified. |
%RTT-4-OPER_PROTOERR : Entry number = [dec], Protocol Specific Error [chars], specific code = [dec] | |
---|---|
Explanation | This message logs protocol specific error condition in the IPSLAs operations. This message is enabled when the ip sla logging traps command is entered |
Recommended Action | Ensure that the destination for the IPSLAs operation is reachable. Also ensure that the IPSLA responder operation is configured on the destination. If you do not want to log these messages for IPSLAs operations, enter the no ip sla logging traps command to disable the logging |
SADB
%SADB-4-TREE_CORRUPTED : SADB : AVL Tree got corrupted | |
---|---|
Explanation | SADB's one of the AVL Trees got corrupted |
Recommended Action | No action is required. |
SBC
%SBC-3-FEAT_DOWN : Invalid request [chars] while feature down, call id [int] | |
---|---|
Explanation | While the feature was not active, an invalid request was received from another layer of the SBC software stack for the specified call ID. Some requests do not have an associated call ID. For them the displayed call ID is zero. |
Recommended Action | This is a software issue. The consequences could be limited to only one or a few calls. LOG_STD_RECUR_ACTION |
%SBC-3-FEAT_UP : Invalid request [chars] while feature up | |
---|---|
Explanation | While the feature was active, an invalid request was received from another layer of the SBC software stack. |
Recommended Action | This is a software issue. There are no consequences as this can only have been an Init request while the feature was already active. LOG_STD_RECUR_ACTION |
%SBC-3-NO_RES : [chars] resource not available for the [chars] request, call id [int] | |
---|---|
Explanation | The specified software resource was not available or could not be located for the specified request from upper SBC software stack layers for the specified call ID. |
Recommended Action | This is a software issue. The consequences are that the specified request could not be performed. LOG_STD_RECUR_ACTION |
%SBC-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int] | |
---|---|
Explanation | For a request from upper SBC software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck call that cannot be established etc. In rare cases this could also affect other operations such as feature activation, deactivation, modification, High-Availability switchover operations. |
Recommended Action | This is normally a software issue. LOG_STD_RECUR_ACTION |
%SBC-3-IPC_NORES : No space for the IPC reply, size [int] | |
---|---|
Explanation | For a request from upper SBC software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck call that cannot be established etc. In rare cases this could also affect other operations such as feature activation, deactivation, modification, High-Availability switchover operations. |
Recommended Action | This is normally a software issue. LOG_STD_RECUR_ACTION |
%SBC-2-IPC_INIT : IPC message handler registration failure, rc [int] | |
---|---|
Explanation | Registering an IPC message handler for the SBC feature failed. This will cause the feature not to function. The function |
Recommended Action | This is normally a software issue. The consequences are that the SBC feature will not function. LOG_STD_ACTION |
%SBC-3-MEM_INIT_FAILED : Allocation of [chars] memory failed for SBC | |
---|---|
Explanation | SBC Initialization of channel pool failed. |
Recommended Action | LOG_STD_ACTION |
%SBC-3-PKT_REPLICA_INIT_FAILED : Register to Generic Packet Replication failed for SBC | |
---|---|
Explanation | SBC Initialization of packet replication registration failed. |
Recommended Action | LOG_STD_ACTION |
SBC_CFG
%SBC_CFG-3-DBE_CONFIG_FAILURE : An SBC DBE configuration failure has occurred. | |
---|---|
Explanation | SBC has been unable to apply its DBE configuration. |
Recommended Action | Attempt to manually reconfigure the SBC DBE. LOG_STD_ACTION |
%SBC_CFG-6-SERVICE_CHANGE_COLD_BOOT : Delay [chars]. | |
---|---|
Explanation | SBC has been configured to delay sending a ServiceChange message at boot. Upon the delay timer expiring, the ServiceChange message will be sent. |
Recommended Action | This message is for informational purposes only. A ServiceChange message will be sent out once the delay timer expires. |
%SBC_CFG-4-SERVICE_CHANGE_COLD_BOOT_DELAY_FAILED : Failed to delay ServiceChange. | |
---|---|
Explanation | SBC has failed to start a timer for delaying a ServiceChange message at boot. The ServiceChange message will be sent out without a delay. |
Recommended Action | Ensure that SBC has been fully Activated and that all requested pinholes have been established. LOG_STD_ACTION |
%SBC_CFG-3-SERVICE_CHANGE_COLD_BOOT_FAILED : Delayed ServiceChange failed. | |
---|---|
Explanation | SBC has failed to send the delayed ServiceChange message at boot. |
Recommended Action | Ensure that the SBC configuration is valid, and perform a manual SBC Activation. |
%SBC_CFG-3-MED_NOT_DEL_V4 : IPv4 address(es) deleted ([IP_address] [IP_address], VRF '[chars]'), media addresses/pools not removed. | |
---|---|
Explanation | One or more IPv4 addresses of an SBC interface were removed while the SBC was still active. Please remove the media addresses/pools later manually. If the media addresses/pools were associated with a VRF then it will be necessary to remove the media addresses/pools by unconfiguring the SBC. |
Recommended Action |
%SBC_CFG-3-MED_NOT_DEL_V6 : IPv6 address(es) deleted ([IPV6 address]/[int] VRF '[chars]'), media addresses/pools not removed. | |
---|---|
Explanation | One or more IPv6 addresses of an SBC interface were removed while the SBC was still active. Please remove the media addresses/pools later manually. If the media addresses/pools were associated with a VRF then it will be necessary to remove the media addresses/pools by unconfiguring the SBC. |
Recommended Action |
%SBC_CFG-3-SBC_NOT_CONFIG : SBC is not configured. VOIP LI configuration request failed | |
---|---|
Explanation | Since SBC is not configured, the VOIP LI request is rejected. First configure SBC and then VOIP LI requests will be processed. |
Recommended Action |
%SBC_CFG-4-BLACKLIST_CLEARED : Source [chars]: cleared blacklist event or alert, reason: [chars] | |
---|---|
Explanation | A blacklist event or alert is cleared. |
Recommended Action |
%SBC_CFG-4-BLACKLIST_MINOR : Source [chars]: minor blacklist alert, reason: [chars] | |
---|---|
Explanation | A minor blacklist alert has been generated. |
Recommended Action |
%SBC_CFG-4-BLACKLIST_MAJOR : Source [chars]: major blacklist alert, reason: [chars] | |
---|---|
Explanation | A major blacklist alert has been generated. |
Recommended Action |
%SBC_CFG-4-BLACKLIST_CRITICAL : Source [chars]: critical blacklist alert, reason: [chars] | |
---|---|
Explanation | A critical blacklist alert has been generated. |
Recommended Action |
%SBC_CFG-4-BLACKLIST_BLOCKED : Source [chars]: blacklisted, blocked, reason: [chars] | |
---|---|
Explanation | The source is blacklisted. |
Recommended Action |
SBC_HA
%SBC_HA-3-INTERNAL : An internal SBC HA error has been encountered[chars]. | |
---|---|
Explanation | An internal error has been encountered. |
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. |
%SBC_HA-3-LARGE_IPS_MSG : SBC failed to receive large sync message of size [dec]. | |
---|---|
Explanation | The SBC module was unable to successfully receive a large sync message on the Standby. The Standby will be will not have an identical dynamic state as the Active. |
Recommended Action | No action is required. |
%SBC_HA-3-LARGE_IPS_MSG_FAIL : SBC failed to send large sync message of size [dec]. | |
---|---|
Explanation | The SBC module was unable to successfully send a large sync message to the Standby because this version of the Standby does not support large messages. The Standby will be will not have an identical dynamic state as the Active. |
Recommended Action | No action is required. |
%SBC_HA-3-CONFIG_SYNC : SBC failed to cache SBC config of size [dec]. | |
---|---|
Explanation | The SBC module was unable to successfully cache the SBC config on the Standby. The Standby will be unable to write SBC config to NVRAM. |
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. |
%SBC_HA-3-RF_REGISTRATION : SBC RF failed to register | |
---|---|
Explanation | The SBC module was unable to successfully register with the RF infrastructure. SBC will not be able to operate in a stateful mode. |
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. |
%SBC_HA-3-WATCH_PROGRESSION : SBC RF failed to create progression watch points. | |
---|---|
Explanation | The SBC module was unable to successfully create the RF progression watch points. RF progression will not be suspended at bulk synchronisation time, so some SBC calls may be lost if a switchover occurs immediately after the system reaches the Standby Hot redundancy state. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SBC_HA-3-NO_SYNC_PROCESS : SBC RF failed to start the config sync process. | |
---|---|
Explanation | The SBC module was unable to successfully start the configuration sync process. The Standby will be unable to fully initialise. |
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. |
%SBC_HA-3-RF_TIMER_EXTENSION_EXPIRY : SBC RF progression extension timer expired. | |
---|---|
Explanation | The SBC module's RF progression extension timer expired. RF progression will resume, but if a switchover occurs immediately after the system reaches the Standby Hot redundancy state then some SBC calls may be lost. |
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. |
%SBC_HA-3-HOLD_PROGRESSION : SBC RF failed to start the progression holding process. | |
---|---|
Explanation | The SBC module was unable to successfully start the RF progression holding process. RF progression will resume immediately, but if a switchover occurs immediately after the system reaches the Standby Hot redundancy state then some SBC calls may be lost. |
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. |
%SBC_HA-3-RF_PROGRESSION : SBC RF failed to resume RF progression at state [chars]. | |
---|---|
Explanation | The SBC module was unable to successfully resume RF progression at the noted state. The Standby will be unable to fully initialise. |
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. |
%SBC_HA-3-RF_CONFIG_SYNC : SBC RF will not be able to synchronise SBC configuration to the Standby. Failure cause: [chars]. | |
---|---|
Explanation | The SBC module will not be able to synchronise the SBC config to the Standby. The Standby will be unable to write SBC config to NVRAM. |
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. |
%SBC_HA-3-IPC_RMI_INIT : SBC IPC failed to register with RMI ([chars]). | |
---|---|
Explanation | The SBC IPC module was unable to successfully register with the Resource Manager. SBC may not be able to operate in a stateful mode. |
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. |
%SBC_HA-3-IPC_INIT : SBC IPC failed to initialise ([chars]). | |
---|---|
Explanation | The SBC IPC module was unable to successfully initialise. SBC may not be able to operate in a stateful mode. |
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. |
%SBC_HA-3-IPC_SEND : SBC IPC message send failed (error [chars]). | |
---|---|
Explanation | The SBC module was unable to successfully send a message to its peer. SBC will not be able to operate in a stateful mode. |
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. |
%SBC_HA-3-ISSU_REGISTRATION : SBC ISSU failed to register. | |
---|---|
Explanation | The SBC module was unable to successfully register with the ISSU infrastructure. SBC will not be able to operate in a stateful mode. |
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. |
%SBC_HA-3-ISSU_CLIENT_REGISTRATION : SBC Client ([dec]) Registration failed ([chars]). | |
---|---|
Explanation | The SBC module was unable to successfully register with the ISSU infrastructure. SBC will not be able to operate in a stateful mode. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show issu clients 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. |
%SBC_HA-3-ISSU_ENTITY_REGISTRATION : SBC Entity ([dec]) Registration failed ([chars]). | |
---|---|
Explanation | The SBC ISSU entity could not be registered. SBC will not be able to operate in a stateful mode. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show issu entities 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. |
%SBC_HA-3-ISSU_MSGTYPE_REGISTRATION : SBC Msg Type for Entity ([dec]) Registration failed ([chars]). | |
---|---|
Explanation | The message type for SBC ISSU could not be registered. SBC will not be able to operate in a stateful mode. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show issu message types 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. |
%SBC_HA-3-ISSU_MSGGROUP_REGISTRATION : SBC Msg Group ([dec]) for Entity ([dec]) Registration failed ([chars]). | |
---|---|
Explanation | The message group for SBC ISSU could not be registered. SBC will not be able to operate in a stateful mode. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show issu message groups 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. |
%SBC_HA-3-ISSU_CAPTYPE_REGISTRATION : SBC Cap Type for Entity ([dec]) Registration failed ([chars]). | |
---|---|
Explanation | A capability type could not be registered for SBC ISSU. SBC will not be able to operate in a stateful mode. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show issu capability types 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. |
%SBC_HA-3-ISSU_CAPENTRY_REGISTRATION : SBC Cap Entry ([dec]) for Entity ([dec]) Registration failed ([chars]). | |
---|---|
Explanation | A capability entry could not be registered for SBC ISSU. SBC will not be able to operate in a stateful mode. |
Recommended Action | LOG_STD_SH_CMD_ACTION(show issu capability entries) |
%SBC_HA-3-ISSU_CAPGROUP_REGISTRATION : SBC Cap Group ([dec]) for Entity ([dec]) Registration failed ([chars]). | |
---|---|
Explanation | A capability group could not be registered for SBC ISSU. SBC will not be able to operate in a stateful mode. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show capability groups 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. |
%SBC_HA-3-ISSU_SESSION_REGISTRATION : SBC session for Entity ([dec]) Registration failed ([chars]). | |
---|---|
Explanation | The SBC ISSU session could not be registered. SBC will not be able to operate in a stateful mode. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show issu sessions 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. |
%SBC_HA-3-ISSU_START_NEGOTIATION : SBC ISSU negotiation failed to start ([chars]). | |
---|---|
Explanation | The SBC module was unable to successfully start negotiatiation with its peer. SBC will not be able to operate in a stateful mode. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show issu fsm 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. |
%SBC_HA-4-ISSU_GET_BUFFER : SBC ISSU session failed to get buffer. | |
---|---|
Explanation | The SBC ISSU client failed to get a buffer. Some High-Availability SBC information may be missing from the peer. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show processes memory 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. |
%SBC_HA-3-ISSU_NEGOTIATION : SBC ISSU negotiation failed. | |
---|---|
Explanation | The SBC module was unable to successfully negotiate with its peer. SBC will not be able to operate in a stateful mode. |
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. |
%SBC_HA-3-ISSU_MSG_MTU : SBC Client ([dec]) get msg mtu failed. Error = [dec]. | |
---|---|
Explanation | The SBC ISSU client could not obtain a message of the required size. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show issu fsm 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. |
%SBC_HA-3-ISSU_TRANSFORM : SBC ISSU [chars] transformation failed ([chars]). | |
---|---|
Explanation | The transformation operation for an SBC ISSU message has failed. |
Recommended Action | LOG_STD_SH_CMD_ACTION(show issu fsm and show issu sessions) |
%SBC_HA-3-LARGE_IPS_UNSUPP : The current version of the SBC Standby does not support the syncing of large SBC contexts | |
---|---|
Explanation | The current version of the SBC Standby does not support the syncing of large SBC contexts. A context that contains 24 or more media and signaling flows is a large context. It is rare to have such a large context and thus, ISSU compatibility has been permitted even though this difference in support exists. Normal SBC High Availability synchronization will continue to operate successfully as long as no contexts contain more than 24 signaling or media flows. Context information beyond 24 flows will not be replicated and thus on RP switchover the Active RP will not have information about all the contexts |
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. |
%SBC_HA-3-ILT_STUB : SBC ILT Stub process creation failed. | |
---|---|
Explanation | The SBC module was unable to successfully create the ILT Stub process. SBC will not be able to operate in a stateful mode. |
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. |
%SBC_HA-3-ILT_REGISTRATION : SBC ILT registration failed. | |
---|---|
Explanation | The SBC module was unable to successfully register for communication with the peer unit. SBC will not be able to operate in a stateful mode. |
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. |
%SBC_HA-3-ILT_PROC_CREATE : SBC ILT process creation failed. | |
---|---|
Explanation | The SBC module was unable to successfully create an SBC process. SBC will not be able to operate in a stateful mode. |
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. |
%SBC_HA-3-SBC_IPV6_CFG : SBC has detected configuration/dynamic state ([chars]) which is not supported on the peer. | |
---|---|
Explanation | Peer SBC does not support IPv6. |
Recommended Action | Manually remove IPv6 configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_DYNAMIC_CODEC_CFG : SBC has detected Dynamic Codec configuration which is not supported on the peer. SBC cannot proceed as HA client. Remove all codec configuration to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support Dynamic Codec configuration. |
Recommended Action | Manually remove Dynamic Codec configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_XML_BILLING_CFG : SBC has detected Xml Billing configuration which is not supported on the peer. SBC cannot proceed as HA client. Remove all xml billing configuration to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support Xml Billing configuration. |
Recommended Action | Manually remove Xml Billing configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_RG_NO_TRANSPORT : SBC was unable to register a transport with the RG infrastructure for inter-chassis HA. | |
---|---|
Explanation | SBC will not be able to support inter-chassis HA. |
Recommended Action | No action is required. |
%SBC_HA-3-SBC_RG_NO_CLIENT : SBC was unable to register the RG Client with the RG infrastructure for inter-chassis HA. | |
---|---|
Explanation | SBC will not be able to support inter-chassis HA. |
Recommended Action | No action is required. |
%SBC_HA-3-SBC_RG_NO_PROCESS : SBC was unable to start a process used by the RG client | |
---|---|
Explanation | SBC will not be able to support inter-chassis HA. |
Recommended Action | No action is required. |
%SBC_HA-3-SBC_RG_NO_SOCKET : SBC was unable to open a socket for the RG client | |
---|---|
Explanation | SBC will not be able to support inter-chassis HA. |
Recommended Action | No action is required. |
%SBC_HA-3-SBC_RG_SOCK_FAIL : SBC lost connection with RG peer, socket failure [chars], len=[dec] | |
---|---|
Explanation | SBC HA may be disabled until peer connection is established. |
Recommended Action | No action is required. |
%SBC_HA-3-SBC_CODEC_INTERWORK_CFG : SBC has detected codec configuration which is not supported on the peer. SBC cannot proceed as HA client. Remove all newly entered codec configuration to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support codec preference, variant or interwork configuration. |
Recommended Action | Manually remove newly added codec configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_MSMB_CFG : SBC has detected Multi SBC Media Bypass configuration which is not supported on the peer. SBC cannot proceed as HA client. Remove all Multi SBC Media Bypass configuration to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support Multi SBC Media Bypass configuration. |
Recommended Action | Manually remove Multi SBC Media Bypass configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_DBL_NA_ALERT_CFG : SBC has detected blacklist entries configured which have reason na-policy-failure OR minor, major, critical alerts which is not supported on the peer. SBC cannot proceed as HA client. Remove all blacklist entries with this reason or any alerts configuration to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support blacklist reason na-policy-failure or blacklist alerts configuration. |
Recommended Action | Manually remove blacklist reason na-policy-failure and minor, major or critical alerts configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_B2B_RESTART : SBC restart has taken longer than expected. The SBC will be restarted, but may require a shut/no shut of the redundancy group in order to return to stateful HA with the active router. | |
---|---|
Explanation | SBC process restart timedout, may require manual intervention. |
Recommended Action | Shut/No shut the standby redundancy group associated with the SBC. LOG_STD_ACTION |
%SBC_HA-3-SBC_HA_CALL_ONA_CFG : SBC has detected first-outbound-na-table configured within a call-policy-set. This command is not supported on the peer. SBC cannot proceed as HA client. Remove all first-outbound-na-table configuration to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support first-outbound-na-table configuration within a call-policy-set. |
Recommended Action | Manually remove the first-outbound-na-table configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_HA_ADMIN_DOMAIN_CFG : SBC has detected an admin-domain configuration. This feature is not supported on the peer. SBC cannot proceed as HA client. Remove all admin-domain submodes from the configuration to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support admin-domain configuration. |
Recommended Action | Manually remove the admin-domain submodes from configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_HA_CAC_AVG_PER2_CFG : SBC has detected averaging-period 2 cac configuration. Averaging-period 2 is not supported on the peer. SBC cannot proceed as HA client. Remove the cac-policy-set averaging-period 2 configuration to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support averaging-period 2 cac configuration. |
Recommended Action | Manually remove the cac-policy-set averaging-period 2 configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_HA_CAC_AVG_PER2_RATE_CFG : SBC has detected cac-policy-set rate limit configuration for averaging-period 2. Averaging-period 2 is not supported on the peer. SBC cannot proceed as HA client. Remove the cac-policy-set rate limit configuration for averaging-period 2 to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support cac rate limit configuration for averaging-period 2. |
Recommended Action | Manually remove the rate limit commands for averaging-period 2 found within the cac-policy-set entry and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_HA_PORT_TAG_CFG : SBC has detected an port tag configuration. This feature is not supported on the peer. SBC cannot proceed as HA client. Remove all port tag from the configuration to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support port tag configuration. |
Recommended Action | Manually remove the port tag from configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_FLEX_MED_RTG_CFG : SBC has detected flexible media routing configuration. This feature is not supported on the peer. SBC cannot proceed as HA client. Remove all flexible media routing config from the configuration to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support flexible media routing configuration. |
Recommended Action | Manually remove flexible media routing from configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_HA_CAC_PRIVACY_SERV_CFG : SBC has detected cac-policy-set privacy-service configuration for a cac entry. This enhancement is not supported on the peer. SBC cannot proceed as HA client. Remove the cac-policy-set privacy-service related configuration to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support cac-policy-set privacy-service configuration for a cac entry. |
Recommended Action | Manually remove the privacy-service related commands configured within the cac-policy-set entry and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_IMP_NA_REGEX_CFG : SBC has detected number analysis entries that match on text addresses, which are not supported on the peer. Remove all regex number analysis entries to proceed with ISSU/D | |
---|---|
Explanation | Peer SBC does not support regex number analysis entries. |
Recommended Action | Manually remove regex number analysis entries and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_IMP_NA_EDITSRC_CFG : SBC has detected number analysis entries that have edit-src actions, which are not supported on the peer. Remove all edit-src actions from all number analysis entries to proceed with ISSU/D | |
---|---|
Explanation | Peer SBC does not support edit-src actions in number analysis entries. |
Recommended Action | Manually remove edit-src actions from all number analysis entries and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_IMP_NA_SRCANON_CFG : SBC has detected na-src-name-anonymous number analysis tables, which are not supported on the peer. Remove all na-src-name-anonymous number analysis tables to proceed with ISSU/D | |
---|---|
Explanation | Peer SBC does not support na-src-name-anonymous number analysis tables. |
Recommended Action | Manually remove all na-src-name-anonymous number analysis tables and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_MESSAGE_EDITING_CFG : SBC has detected message editing configured which may have sip editor_type editor OR parameter-editor OR header-editor OR method-editor OR body-editor OR option-editor which is not supported on the peer. SBC cannot proceed as HA client. Remove all message editing config to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support message editing configuration. |
Recommended Action | Manually remove message editing configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_RG_NO_VRF : SBC VRF mismatch between active and standby, please add [chars] | |
---|---|
Explanation | SBC may fail to fully support SSO |
Recommended Action | No action is required. |
%SBC_HA-3-SBC_RG_VRF_INUSE : VRF is used by SBC, add back or remove from active, please add [chars] | |
---|---|
Explanation | SBC may fail to fully support SSO |
Recommended Action | No action is required. |
%SBC_HA-3-SBC_SIPS_H323_INTWK_CFG : SBC has detected SIPS-H323 Interworking configured which may have trusted H323 Adjacencies or secure calls configured which is not supported on the peer. SBC cannot proceed as HA client. Remove all SIPS-H323 Interworking config to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support SIPS-H323 Interworking configuration. |
Recommended Action | Manually remove SIPS-H323 Interworking configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_LRU_CFG : SBC has detected LRU configured SBC cannot proceed now. Remove all LRU CONFIG to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support LRU configuration. |
Recommended Action | Manually remove LRU configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_SDP_EDITING_CFG : SBC has detected sdp editing configured which may have script-set OR active-script-set OR test script-set on any adjacency configured which is not supported on the peer. SBC cannot proceed as HA client. Remove all sdp editing config to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support sdp editing configuration. |
Recommended Action | Manually remove sdp editing configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_CAC_ENHANCEMENT_CFG : SBC has detected cac enhancement feature configured which may have branch cli OR cac-scope (adjacency ,account)cli SBC cannot proceed as HA client. Remove all cac enhancement feature config to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support cac enhancement feature configuration. |
Recommended Action | Manually remove cac enhancement feature configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_QOS_DEMARCATION_CFG : SBC has detected qos demarcation configured which may have statistics threshold OR g107a factor OR cal_moscqe OR g107 bpl OR g107 ie OR qos trap configured ,which is not supported on the peer. SBC cannot proceed as HA client. Remove all qos demarcation config to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support qos demarcation configuration. |
Recommended Action | Manually remove qos demarcation configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_VIA_PASSTHROUGH_CFG : SBC has detected Via Passthrough configured SBC cannot proceed now. Remove all Via Passthrough CONFIG to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support Via Passthrough configuration. |
Recommended Action | Manually remove Via Passthrough configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_MEDIA_BYPASS_NATTAGGEN_CFG : SBC has detected media bypass auto-nat-tag-gen configured SBC cannot proceed now. Remove all media bypass auto-nat-tag-gen config to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support media bypass auto-nat-tag-gen configuration. |
Recommended Action | Manually remove media bypass auto-nat-tag-gen configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_MEDIA_ADDRESS_PRESERVE_INIT_NEGO_CFG : SBC has detected media address preserve init-negotiation configured SBC cannot proceed now. Remove all media address preserve init-negotiation config to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support media address preserve init-negotiation configuration. |
Recommended Action | Manually remove media address preserve init-negotiation configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_SUBSCRIBER_TCP_CFG : SBC has detected subscriber tcp configured which may have subscriber tcp incoming-only configured which is not supported on the peer. SBC cannot proceed as HA client. Remove all subscriber tcp config to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support susbscriber tcp configuration. |
Recommended Action | Manually remove subscriber tcp configuration and reinitiate ISSU. LOG_STD_ACTION |
%SBC_HA-3-SBC_IMS_RF_CFG : SBC has detected ims rf configured. SBC cannot proceed now. Remove all ims rf config to proceed with ISSU/ISSD. | |
---|---|
Explanation | Peer SBC does not support ims rf configuration. |
Recommended Action | Manually remove ims rf configuration and reinitiate ISSU. LOG_STD_ACTION |