Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages, Release 3.4
Routing Messages
Downloads: This chapterpdf (PDF - 476.0KB) The complete bookPDF (PDF - 1.84MB) | Feedback

Routing Messages

Table Of Contents

Routing Messages

RETRY Messages

RIB_LIB Messages

RIB_QUERY_ORA Messages

RIB Messages

RIP Messages

ROUTE_MAP Messages

RPL_COORD Messages

RRR_PCALC Messages

RSVP Messages

RUMP Messages

SAP_LISTEN Messages


Routing Messages


This section contains all routing related System Error Messages, such as RETRY, RIB, RIP, and so forth. The following facility codes are represented in this module:

RETRY Messages

RIB_LIB Messages

RIB_QUERY_ORA Messages

RIB Messages

RIP Messages

ROUTE_MAP Messages

RPL_COORD Messages

RRR_PCALC Messages

RSVP Messages

RUMP Messages

SAP_LISTEN Messages

RETRY Messages

Error Message     
 
    
    
   

%ROUTING-RETRY-4-DEBUG_INIT [chars] [dec] [chars] [chars]

Explanation    Internal error. Retry debug library initilization failed

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

RIB_LIB Messages

Error Message     
 
    
    
   

%ROUTING-RIB_LIB-3-ERR_LOCK_FATAL [chars] Pthread [chars], unexpected fatal error [[chars]]

Explanation    An unexpected fatal error occured when trying operate on a pthread lock.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB_LIB-3-FETCH_UPDATE Error fetching RIB update - [chars]

Explanation    Unexpected error fetching a RIB update notification. See error message for more information.

Recommended Action    Restarting the client process from which the errow was emitted, or the RIB server, may fix the problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIB_LIB-4-ERR_POSSIBLE_CONNECTION_LEAK RIB client binding with a non-NULL connection handle. Potential client memory leak.

Explanation    A client passed a pointer to rib_bind which points to a non-NULL connection. This implies a connection leak in the client code.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB_LIB-4-UNBIND Failed to [chars] during client unbind - [chars]

Explanation    Unexpected error during client unbind operation. This may result in a resource leak.

Recommended Action    If there is a evidence of a memory leak in the process which reported this error, restart that process. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

RIB_QUERY_ORA Messages

Error Message     
 
    
    
   

%ROUTING-RIB_QUERY_ORA-3-CERRNO_REG Failure registering cerrno DLL with subsys num [unsigned int] and DLL name [chars]. Error: [chars] ([hex])

Explanation    A failure occurred during the registration of the DLL for decoding error codes from the component. This may render certain codes unprintable, but otherwise has no negative impact.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIB_QUERY_ORA-3-INSTBUILD Failed to build policy operation '[chars]' for attribute '[chars]'.[chars]%s ([hex])

Explanation    There was an internal error in the routing policy library and as a result routing policy may not be applied correctly.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIB_QUERY_ORA-3-ORABUILD Failed to build ORA: [chars]; [chars] ([hex])

Explanation    There was an internal error in the routing policy library and as a result routing policy may not be applied correctly.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIB_QUERY_ORA-3-RUN Could not apply policy operation '[chars]' to attribute '[chars]': [chars] ([hex])

Explanation    There was an internal error in the routing policy library and as a result routing policy may not be applied correctly.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

RIB Messages

Error Message     
 
    
    
   

%ROUTING-RIB-2-PARENT_UNREGISTER Parent [chars] ([chars]) ([dec]) unregistering from Vrf: [chars] Tbl: [chars] Safi: [chars], table id [hex], it still has [dec] dependants, context [chars]

Explanation    A RIB download client (typically bcdl_agent), unregistered from a table while it still has children referring to this table. The number of routes may no longer be insync in all FIBs. If corresponding bcdl_agent restarted just before this message was seen, this error message can be ignored.

Recommended Action    Restart the corresponding bcdl_agent process. *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-CONVERGE_VERSION_MISMATCH Client [chars] has last signalled version [dec] which is less than the RIB version [dec] for Vrf: [chars] Tbl: [chars] Safi: [chars]

Explanation    A client updated the RIB for convergence but not with the latest version as known by RIB. This will have delayed or prevented the convergence of the routing table, and hence the purging of any stale routes from the forwarding table.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-ERR_CHILD_REDIST_REQUESTS [chars] [dec], line [dec], client [chars] ([dec]) table [hex] Vrf: [chars] Tbl: [chars] Safi: [chars]

Explanation    An unexpected error occured when trying to add a path to the next-hop database.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-ERR_LOCK_FATAL Pthread lock [chars], unexpected fatal error [[chars]]

Explanation    An unexpected fatal error occured when trying operate on a pthread lock.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-ERR_LOOKUP Table [hex], prefix [chars]/[dec], intf [hex], unexpected lookup results in [chars]

Explanation    An unexpected lookup error occured when trying to lookup a prefix.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-ERR_MEM_ALLOC Failed to allocate memory for RIB operations

Explanation    Failed to allocate memory for RIB operations probably out of memory because of huge configuration or a memory leak.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-ERR_MEM_NHPATH [chars]

Explanation    An unexpected error occured when trying to clear redist information for a client.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-ERR_MUTEX_FATAL Mutex [chars], context '[chars]', unexpected fatal error [[chars]]

Explanation    An unexpected fatal error occured when trying to lock or unlock a RIB mutex.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-ERR_NH_PACK [chars], table [hex]

Explanation    An unexpected nh notification packing error occured.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-ERR_NH_PATH Could not add [chars] to nh db for Vrf: [chars] Tbl: [chars] Safi: [chars]

Explanation    An unexpected error occured when trying to add a path to the next-hop database.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-ERR_REDIST_INFO_CLEAR [chars], table [hex], client [chars] [chars] ([dec])

Explanation    An unexpected error occured when trying to clear redist information for a client.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-ERR_RIBIO Client [chars] [chars] warning [[chars]]

Explanation    An unexpected but non-fatal error occurred when a client performed an input/output operation. See error message for more information.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-ERR_RSI [chars], [chars] [chars] id [hex], [chars]

Explanation    An unexpected RSI error occured during a table creation/deletion/modification operation.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-ERR_TABLE_OPERATION [chars], table [hex] [chars]

Explanation    Some type of table related error occurred.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-ERR_THREAD_POOL Thread pool [chars] unexpected fatal error [[chars]]

Explanation    An unexpected fatal error during a RIB thread pool operation. See error message for more details.

Recommended Action    If the error is due to lack of resources, attempt to free some up and then restart RIB. Otherwise Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIB-3-EVENT_BOOLEAN_SET Failed to set [chars] event boolean to [chars]: [chars]

Explanation    Unexpected error during event boolean set. This may result in unreleased memory resources in RIB server.

Recommended Action    If there is evidence of a memory leak in the RIB server, restarting it should help alleviate the problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIB-3-GO_ACTIVE Failed to transition from active to standby - [chars]

Explanation    Fatal error handling node state transition to active.

Recommended Action    The RIB process should have restarted automatically and then gone into active state successfully. If not, try manually restarting it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIB-3-GO_STANDBY Node state changed from active to standby - don't know what to do

Explanation    Node role state regressed from active state to standby state. This is not currently supported by RIB.

Recommended Action    If the node's role change from active to standby was not deliberate, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIB-3-INTERFACE_DB Interface database: failed to [chars] the entry for [chars] with table id [unsigned int]

Explanation    The rib unexpectedly failed to update the interface - IP address database.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-INVALID_BATCH_OPERATION Received invalid batch operation from client: [unsigned int]

Explanation    A client sent a batch to RIB containing an invalid op code.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-INVALID_BCDL_REGISTRATION BCDL client [chars] ([dec]) registering with parent [chars] ([dec]) which also has a parent

Explanation    Invalid BCDL registration detected.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-INVALID_TABLE_ACCESS A client attempted to access invalid table: [hex]

Explanation    A client attempted to access a RIB table that does not exist.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-LTRACE_INIT RIB ltrace init failed. Error initialising [[chars]] trace buffer. Process terminated : [chars]

Explanation    The ltrace buffer could not be initialised

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-LWM_REPLY Failed to send reply to client - [chars]

Explanation    Unexpected error sending reply to a RIB client.

Recommended Action    Check for errors in the state of the routing table. If any problems are identified, restarting the client and/or RIB may help to fix the problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIB-3-MAIN_INIT Main thread initialization failed [[chars]:[chars]]. Process terminated

Explanation    An error occurred during main thread initialization, causing the process to terminate. Check the details of the error message for more information.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-MGMNT_INIT Management thread initialization failed [[chars]:[chars]]. Process terminated

Explanation    An error occurred during management thread initialization, causing the process to terminate. Check the details of the error message for more information.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-NEXTHOPS_TRAVERSE Failed to unregister next-hops for client [chars] - [chars]

Explanation    Unexpected error unregistering client next-hops. This may lead to a slow memory leak.

Recommended Action    If RIB is leaking memory, try restarting it. *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-NH_CLIENT Failed to insert client [chars]/[chars] for nexthop [chars]/[dec]

Explanation    An unexpected error occured when trying to clear redist information for a client.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-NH_DB_ADD Could not add nexthop to nh db, error [chars]

Explanation    An unexpected error occured when trying to clear redist information for a client.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-NH_INSERT_HEAP Cannot insert nh_entry into the heap, [chars]

Explanation    An unexpected error occured when trying to clear redist information for a client.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-NSF_WARN Failed to allocate resources required for NSF [chars]

Explanation    Unexpected resource error during NSF initialization. This may result in NSF failures.

Recommended Action    Free some resources and restart RIB *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-PREFIXES_FULL The route prefix table ([hex]) is full with [unsigned int] prefixes.

Explanation    The route prefix table has become full--either because the table reached the configured maximum fill level, or a maximum of 2,000,000 prefixes are stored.

Recommended Action    If the maxmimum configured number of allowed route prefixes is configured lower than the allowed maximum of 2,000,000, update the configuration to allow a larger number of route prefixes. This threshold is set using the 'maximum prefix {max_prefixes} {low_threshold_percentage}' command. This command can be set per virtual router (vrf) or for the main routing table.

Error Message     
 
    
    
   

%ROUTING-RIB-3-PURGE_TIMER_ALLOC Not enough memory to allocate purge timer for Protocol [chars] (Instance [chars])

Explanation    Couldn't allocate a purge timer. Old routes for this protocol may not automatically get purge from the FIB table.

Recommended Action    Free up some resources and restart the RIB. *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-QSM_ADD_SERVICE RIB failed function qsm_add_service to add local service: [chars]

Explanation    RIB failed to advertise it local channel during failed over.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-RUMP_NOTIFY Failed to notify RUMP of new protocol: [chars]

Explanation    Failed to notify RUMP about a newly registered protocol. See error message for more details. The result is that routes from the new protocol will not be redistributed into the multicast table.

Recommended Action    Restart the RUMP process. *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-SHUTDOWN Process is shutting down: [chars]

Explanation    The RIB process has performed a graceful shutdown and will be restarted.

Recommended Action    Check to make sure the process has restarted. If not, restart manually Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIB-3-TIME_ERR Failed to get timestamp from kernel

Explanation    A call to clock_gettime failed.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-3-UPDATE_TIMEOUT Client [chars] updated the RIB without signaling update completion for Vrf: [chars] Tbl: [chars] Safi: [chars]

Explanation    A client updated the RIB without signaling update completion. This will have delayed the convergence of the routing table, and hence the purging of any stale routes from the forwarding table.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-4-PREFIXES_BELOW_THRESHOLD The previously full route prefix table ([hex]) is no longer full and can accept more routes.

Explanation    The route prefix table is no longer considered full. This warning is generated after a full route prefix table frees off some route prefixes.

Recommended Action    *NONE*

Error Message     
 
    
    
   

%ROUTING-RIB-4-PREFIXES_REACHED_LOW_THRESHOLD The fill level for the route prefix table ([hex]) reached the low warning fill level of [unsigned int] prefixes.

Explanation    This warning indicates the number of prefixes in the specified prefix table reached the configured fill threshold. This is an informational message that may be used to alert changing trends in the number of active prefixes. This threshold is set using the 'maximum prefix {max_prefixes} {low_threshold_percentage}' command. This command can be set per virtual router (vrf) or for the main routing table.

Recommended Action    If this threshold is regularly reached, it may no longer convey the original meaning. Either increase the fill percentage for the prefix table, or increase the number of prefixes that can be stored in the table. Both of these options are updated in the using the 'maximum prefix' command.

Error Message     
 
    
    
   

%ROUTING-RIB-4-RECURSION_DEPTH_CHANGED Maximum recursion depth changed. Please restart process to take effect.

Explanation    The maximum recursion depth has changed. In order for the new value to take effect, the process has to be restarted. This warning is generated to remind the the customer to restart the RIB processes.

Recommended Action    restart the RIB

Error Message     
 
    
    
   

%ROUTING-RIB-4-SELECT_IGNORED Client [chars] on [chars] - File select input ignored

Explanation    Internal notification error.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-4-SYSMGR_NODE_STATE Failed to retrieve node state from sysmgr: [chars]

Explanation    Sysmgr returned a failover from a node state query.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-4-UNSUPPORTED_OOM_STATE Bad memory state received from wdsysmon ([dec])

Explanation    A memory state transition notification was received from wdsysmon with an invalid state.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-4-WARN_UNEXPECTED_EXT_COMM [chars], [chars]/[dec] in table [hex]

Explanation    A route has extended communities attached to it unexpectedly.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%ROUTING-RIB-5-TABLE_NH_DAMPED Nexthops in Vrf: [chars] Tbl: [chars] ([hex]) Safi: [chars] are getting damped

Explanation    This notification indicates that there is atleast one nexthop in this RIB table that is getting damped.

Recommended Action    *DEBUG*

Error Message     
 
    
    
   

%ROUTING-RIB-6-INFO_LOCKING_CONTEXT_DISPLAY Rib locking context[[dec]] [chars], operation: [chars], thread id: [dec]

Explanation    Display a single entry of locking context information. The cause of this informational message should be evident from the context in the log.

Recommended Action    *DEBUG*

Error Message     
 
    
    
   

%ROUTING-RIB-7-INFO_LOCKING_OPERATION_DISPLAY [chars] in function [chars]

Explanation    Display the operation being performed on lock, and the function the operation is taking place in. This will only be displayed in verbose locking debugging.

Recommended Action    *DEBUG*

Error Message     
 
    
    
   

%ROUTING-RIB-7-SERVER_ROUTING_DEPTH Recursion loop looking up prefix [chars] in Vrf: [chars] Tbl: [chars] Safi: [chars]

Explanation    Recursive route lookup for resolving the prefix has exceeded the maximum recursion depth allowed(possibly because of a routing loop).

Recommended Action    To further debug/troubleshoot this state use commands like 'show route' and 'show route resolving-next-hop' recursively to resolve the prefix manually, notice if there are any loops indeed.

RIP Messages

Error Message     
 
    
    
   

%ROUTING-RIP-2-CRIT_OOM RIP out-of-memory event [chars]: new/current state=[chars]: old state=[chars]

Explanation    This is an event associated with out-of-memory conditions on the router. If the new state is MINOR, no new VRF contexts or interfaces will be activated. If the new state is SEVERE, some VRF contexts and interfaces may be forcible deactivated in order to free up memory. If the new state is CRITICAL, the RIP process will be shutdown. If the new state is NORMAL, RIP will behave normally. If a VRF context or interface is forcibly deactivated, it will not be activated again when memory state returns to NORMAL unless the user explicitly clears the out-of-memory condition in the VRF context or the interface using the 'clear rip' command.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%ROUTING-RIP-2-ERR_MEM_ALLOC Could not allocate memory for [chars]: instance [chars]

Explanation    There is not enough memory available to RIP process.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_AUTH Failure in RIP authentication module in context [chars]: instance [chars]: error=[chars]

Explanation    Internal error encountered in RIP authentication module.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_CFG Error during configuration in context [chars]: error=[chars]

Explanation    Internal error encountered in RIP configuration functions.

Recommended Action    Please retry the configuration command that caused this error and check running configuration to make sure it is correct. If the error persists open a case with TAC.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_CLEAR Error in clear server in context [chars]: error=[chars]

Explanation    Internal error encountered in RIP clear server.

Recommended Action    Please retry the command. If the error persists open a case with TAC.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_EVENT Event handling error in context [chars]: type [dec]: error=[chars]

Explanation    Internal error encountered in RIP event handling mechanisms.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_IF Error in interface module in context [chars]: instance [chars]: error=[chars]

Explanation    Internal error encountered in RIP interface module.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_INIT Initialization error in context [chars]: instance [chars]: error=[chars]

Explanation    There was an error during initialization of one of RIP's components.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_ITAL ITAL error in context [chars]: VRF [chars]: Interface [chars]: IPAddress [chars]: error=[chars]

Explanation    Internal error encountered in RIP ITAL module.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_OOM Error in handling out-of-memory condition in context [chars]: state=[chars]: error=[chars]

Explanation    An internal error encountered in RIP's OOM module. This may affect RIP's behavior only under low memory conditions; otherwise RIP will operate normally.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_PAK_AUTH Authentication failure for RIP [chars] packet in context [chars]: instance [chars]: error=[chars]

Explanation    Authentication failure during RIP send/receive packets.

Recommended Action    Please check to make sure RIP interface authentication configuration is correct. If key chains are used, please make sure atleast one active key is available for send operation. Please make sure both send and receive interfaces are configured with the same authentication mode. For text authentication mode, please make sure the active password used on the send interface key chain is also active on the receive interface key chain. For MD5 authentication mode, please make sure the active key ID and password used on the send interface key chain is also active on the receive interface key chain.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_PAK_RECV Packet receive error in context [chars]: instance [chars]: error=[chars]

Explanation    Error encountered during RIP packet receive operation.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_POLICY Policy error in context [chars]: name [chars]: error=[chars]

Explanation    Internal error with route policies used by RIP.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_RDB RDB error in context [chars]: VRF [chars]: TableID [unsigned int]: error=[chars]

Explanation    Error encountered in RIP's routing database.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_REDIST Redistribution error in context [chars]: protocol [chars]: instance [chars]: error=[chars]

Explanation    Internal error encountered during redistribution of other protocols into RIP.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_RIB RIB error in context [chars]: VRF [chars]: IPAddress/PrefixLen [chars]/[unsigned int]: error=[chars]

Explanation    Error encountered by RIP during interaction with RIB.

Recommended Action    These messages are expected during RIB process restart. In all other cases, please contact TAC.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_THREAD_MUTEX_LOCK Error [chars] locking [chars] in context [chars]: error=[chars]

Explanation    Internal error during locking of a RIP resource.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_THREAD_MUTEX_UNLOCK Error unlocking [chars] in context [chars]: error=[chars]

Explanation    Internal error during unlocking of a RIP resource.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RIP-3-ERR_TOPO Route operation error in context [chars]: VRF [chars]: IPAddress/PrefixLen [chars]/[unsigned int]: error=[chars]

Explanation    Internal error encountered in RIP's topology module.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

ROUTE_MAP Messages

Error Message     
 
    
    
   

%ROUTING-ROUTE_MAP-1-FAILED_MEMORY_LIBRARY [chars]: out of memory

Explanation    The route map library was unable to allocate memory.

Recommended Action    This indicates a low-memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message     
 
    
    
   

%ROUTING-ROUTE_MAP-1-FAILED_MEMORY_NOTIFICATION Internal Error: memory allocation failed during route-map notification on item '[chars]%s'

Explanation    The route map library was unable to allocate memory while creating or updating an active route map.

Recommended Action    This indicates a low memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message     
 
    
    
   

%ROUTING-ROUTE_MAP-1-MEMORY_ALLOC_ERROR [chars]: out of memory

Explanation    show route map client failed to allocate memory

Recommended Action    This indicates a low-memory condition. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. *REDUCE*

Error Message     
 
    
    
   

%ROUTING-ROUTE_MAP-3-FAILED_BIND_SYSDB [chars] during show route-map

Explanation    Failed to connect sysdb server to get information.

Recommended Action    Check existence of the sysdb server.

Error Message     
 
    
    
   

%ROUTING-ROUTE_MAP-3-FAILED_CORRUPT_ROUTEMAP Route map structure is corrupt

Explanation    The route map structure passed to the library was corrupt

Recommended Action    Restart the process experiencing the error.

Error Message     
 
    
    
   

%ROUTING-ROUTE_MAP-3-FAILED_INTERNAL_DAEMON Internal Error: call to function '[chars]' by route-map daemon failed

Explanation    An internal error has occurred which prevents the route map daemon from continuing.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-ROUTE_MAP-3-FAILED_INTERNAL_NOTIFICATION Internal Error: call to function '[chars]' failed during route-map notification on item '[chars]%s'

Explanation    An internal error has occurred while creating or updating an active route map.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-ROUTE_MAP-3-FAILED_LIST_NEXT_SYSDB [chars] during show route-map

Explanation    Failed to connect sysdb server to get information.

Recommended Action    Check existence of the sysdb server.

Error Message     
 
    
    
   

%ROUTING-ROUTE_MAP-3-FAILED_LIST_SYSDB [chars] during show route-map

Explanation    Failed to connect sysdb server to get information.

Recommended Action    Check existence of the sysdb server.

Error Message     
 
    
    
   

%ROUTING-ROUTE_MAP-7-FAILED_BACKEND_LIBRARY Call to '[chars]' from function '[chars]' returned error:'[chars]'

Explanation    An error occured while using the Backend library.

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%ROUTING-ROUTE_MAP-7-FAILED_INVALID_PARAMETER [chars]: NULL event parameter is illegal

Explanation    An error occured while using the Route Map library

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%ROUTING-ROUTE_MAP-7-FAILED_SYSDB_DAEMON Call to '[chars]' from function '[chars]' returned error:'[chars]'

Explanation    An error occurred while using SysDB.

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%ROUTING-ROUTE_MAP-7-FAILED_SYSDB_LIBRARY Call to '[chars]' from function '[chars]' returned error:'[chars]'

Explanation    An error occurred while using SysDB.

Recommended Action    Debug message only. No action is required.

RPL_COORD Messages

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-3-ERR_EVM_CREATE Unable to obtain required communication handler: [chars]

Explanation    The rpl multi-version coordinator was unable to obtain the event handler. This handle is required for all base level communitions with the rest of the system, so the coordinator was shutdown so sysmanger could attempt to restart.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-3-ERR_EVM_EVENT_BLOCK Error seen in primary wait loop: [chars]

Explanation    The rpl multi-version coordinator saw an error in the primary event loop.

Recommended Action    This should be reported to technical support. If only a single message was seen, however, the coordinator may still be functioning. Route policy may not be operational until this is resolved.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-3-ERR_EVM_PROC_AVAILABLE Unable to issue process available: [chars]

Explanation    The system manager did not accept the proccess available that the rpl multi-version coordinator tried to post. The coordinator will exit so the system manager can restart it. Route policy may not be operational until this is resolved.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-3-ERR_EVM_PROC_READY Unable to issue process ready: [chars]

Explanation    The system manager did not accept the proccess ready that the rpl multi-version coordinator tried to post. The coordinator will exit so the system manager can restart it. Route policy may not be operational until this is resolved.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-3-ERR_GROUP_CREATE Unable to create the required '[chars]' group services group: [chars]

Explanation    The rpl multi-version coordinator was unable to create the group services group that is required to coordinate with other route policy entities. The coordinator will exit to allow the system manager to restart it. Route policy may not be operational until this is resolved.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-3-ERR_LWM_CHANNEL Unable to publish global channel: [chars]

Explanation    The rpl multi-version coordinator was unable to publish its channel in the global space. The coordinator will exit so the system manager can restart it. Route policy may not be operational until this is resolved.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-3-SW_CHANGE Unable to register for software change notification because [chars]

Explanation    The attempt to register with the install manager for change of software notification failed. The process will restart in an attempt to clear the problem. Route policy may not be operational until this is resolved.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-4-DEFAULT_ACTION The call to install_default_action failed because [chars]

Explanation    During the processing of a software change notice, the command to take the default restart action failed. The routine will now fall back on a straight exit.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-4-DLL_MANAGER Unable to setup remote dll manager: [chars]

Explanation    The attempt to setup the rpl remote dll coordinator failed. This will prevent the rpl coordinator from running and may prevent route policy from executing.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-4-ERR_DLL_CHECK The query to install_check_dll_changes failed because [chars]

Explanation    During the processing of a software change notice, the command to check the list of open dlls vs changed dlls failed. The routine will now attempt to fall back on default disposition.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-4-ERR_DLL_LIST The query for docked dlls failed because [chars]

Explanation    During the processing of a software change notice, the command to get a list of dlls that this process had open failed. The routine will now attempt to fall back on default disposition.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-4-ERR_GROUP_COMPONENT Group message from outside route access component ([dec] vs [dec]). ignored.

Explanation    The rpl multi-version coordinator received a group services message from a component other than itself. The message was ignored and thus the operations of the coordinator are unaffected. However, this can be a sign that something else is going wrong in the system.

Recommended Action    Observe system for other failures.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-4-ERR_GROUP_MSG_BAD Unknown message type: [dec]. Message ignored.

Explanation    The rpl multi-version coordinator received a message with a type it did not recognize. The message was ignored.

Recommended Action    Observe system for other failures.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-4-ERR_GROUP_MSG_LONG A 'who has this' message longer ([dec]) than required [dec] octets. Ignored.

Explanation    A 'who has this' dll message was longer than its content implied. This indicates either a corruptions of the message itself or a failure of the client to build the message correctly.

Recommended Action    Observe system for other failures.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-4-ERR_GROUP_MSG_SHORT A 'who has this' message shorter ([dec]) than required [dec] octets. Ignored.

Explanation    A 'who has this' dll message was shorted than its content implied. This indicates either a corruptions of the message itself or a failure of the client to build the message correctly.

Recommended Action    Observe system for other failures.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-4-ERR_MEM_ALLOC rpl multi-version Coordinator could not get memory to respond to 'who has this' request.

Explanation    The rpl multi-version coorindator was unable to respond to a 'who has this' request and was forced to ignore the message. This will likely cause a timeout on the client side. If this was the only node with the version of the dll being requested active on it, the client will be unable to access this version. If other nodes have it, the multi-version dll operation will continue. The status of this node remains in uncertain in any case.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-4-FIND_FILE Dll '[chars]' find failed ([chars]). No response sent

Explanation    When the rpl multi-version coordinator tried to locate the dll, an error was encountered. Because of this, no response will be returned.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-4-INSTALL_READY The call to indicate install ready failed because [chars]

Explanation    The attempt to notify install manager of install complete failed. If this is the initial startup, there should be no side affects. If this is the result of a software upgrade/downgrade, it is likely the process will be restarted by sysmgr after a timeout period.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-4-REBOOT install_will_this_node_reboot failed because [chars]

Explanation    During the processing of a software change notice, the command to get reboot information for this notice failed. The routine will now attempt to fall back on default disposition.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-7-DBGINIT Unable to setup debug handlers: [chars]

Explanation    The rpl multi-version coordinator was unable to setup the debug handlers. This will not affect its operational, but will prevent debug commands for the coordinator from functioning.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-7-ERR_GROUP_RESPONSE Response to message [chars] received, but coordinator only supports requests

Explanation    The rpl multi-version coordinator received a message response instead of a request. This has been ignored and it is likely no other problems will result from this.

Recommended Action    Observe system for other failures.

Error Message     
 
    
    
   

%ROUTING-RPL_COORD-7-NO_TERM The message string '[chars]' was missing it null terminator from [chars]:[chars]

Explanation    The given message string should have arrived with a null terminator in it. The library has repaired this, but it should not have occured in the first place. No operational impact should be visible.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

RRR_PCALC Messages

Error Message     
 
    
    
   

%ROUTING-RRR_PCALC-3-ERR_MEM_ALLOC [chars] [dec]

Explanation    A failure at an attempt to allocate memory was detected.

Recommended Action    Add more memory.

RSVP Messages

Error Message     
 
    
    
   

%ROUTING-RSVP-3-RSVP_LSP_RESOURCE_EXHAUSTED Failed to get a new LSP resource

Explanation    Resources to setup new LSP's are exhausted.

Recommended Action    This condition will persist until some LSP's are brought down.

Error Message     
 
    
    
   

%ROUTING-RSVP-3-RSVP_TRACE_INIT_FAILED RSVP event tracing subsytem initialization failed

Explanation    RSVP could not initialize the event tracing module

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RSVP-4-SHUTDOWN Process is shutting down ([chars]): [chars]

Explanation    RSVP process has encountered a problem which means it is no longer able to continue and is shutting down. The message includes a brief description of the problem. The message also describes whether or not RSVP process has been automatically restarted.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Follow the instructions associated with this message. If message states that an automatic restart has been scheduled, then RSVP process will recover automatically. If a manual restart is required, then 'process restart rsvp' is required to recover.

Error Message     
 
    
    
   

%ROUTING-RSVP-5-BAD_RSVP_MSG_RCVD_AUTH_DIGEST Incoming [chars] from [chars] to [chars] discarded - bad digest using key chain '[chars]' key [unsigned int], [chars]

Explanation    The router received an RSVP message with a bad integrity digest. RSVP discarded the message because the digest verification failed. The 'key-strings' used may not be configured the same on both sender/receiver.

Recommended Action    Check the configuration on the router and sending system to make sure that the authentication configuration is compatible. Especially ensure that the key-strings for the specified key ID's match. Also ensure that the peer is using a supported HMAC cryptographic-algorithm.

Error Message     
 
    
    
   

%ROUTING-RSVP-5-BAD_RSVP_MSG_RCVD_AUTH_DUP Incoming [chars] from [chars] to [chars] discarded - authentication seq #[unsigned long long int] is a duplicate, [chars]

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.

Error Message     
 
    
    
   

%ROUTING-RSVP-5-BAD_RSVP_MSG_RCVD_AUTH_KEY Incoming [chars] from [chars] to [chars] discarded - key [unsigned int] is not eligble using key chain '[chars]', [chars]

Explanation    The router received an RSVP message with a bad integrity digest. RSVP discarded the message because the digest verification failed. The received key ID specified is not currently active/configured.

Recommended Action    Check the configuration on the router and sending system to make sure that the authentication configuration is compatible. Especially ensure that the configured key ID's match and are active/enabled.

Error Message     
 
    
    
   

%ROUTING-RSVP-5-BAD_RSVP_MSG_RCVD_AUTH_SEQ Incoming [chars] from [chars] to [chars] discarded - authentication seq #[unsigned long long int] is outside authentication window ([unsigned long long int]), [chars]

Explanation    The router received an RSVP message with a bad authentication sequence number. It may be possible in some cases that bursts of RSVP messages become re-ordered between RSVP neighbors. It may also be possible that an attack was attempted.

Recommended Action    If this occurs on a regular basis, and you can verify that the node sending the burst of messages is trusted, use the window-size option to allow for the burst size such that RSVP will not discard such reordered bursts.

Error Message     
 
    
    
   

%ROUTING-RSVP-5-BAD_RSVP_MSG_RCVD_AUTH_TYPE_MISMATCH Incoming [chars] from [chars] to [chars] discarded - sender is using [chars] as the digest for key chain '[chars]' key [unsigned int], [chars]

Explanation    The router received an RSVP message with an authentication digest type that does not match the type configured on the router. RSVP discarded the message because the digest cannot be verified.

Recommended Action    Check the configuration on the router and sending system to make sure that the authentication configuration is compatible. Especially ensure that the cryptographic-algorithm for the specified key ID's match.

Error Message     
 
    
    
   

%ROUTING-RSVP-5-RSVP_AUTH_NO_KEYS Outgoing [chars] from [chars] to [chars] discarded - no active keys from key-source [chars] -- [chars], [chars]

Explanation    The router is unable to authenticate outgoing RSVP messages due to a lack of availaible keys.

Recommended Action    Check the router configuration of the specified key source.

Error Message     
 
    
    
   

%ROUTING-RSVP-6-RSVP_HELLO_STATE_DOWN Graceful restart hello session to [chars] has changed to the down state

Explanation    The RSVP Graceful Restart Hello session with a neighbor has gone down. This may be due to either a problem in the communication link with the neighbor or the neighbor's RSVP control plane may be restarting.

Recommended Action    If RSVP hello communication is not re-established within the neighbor's Restart Time, RSVP states will be deleted. You may wish to determine if there is a communication problem with the neighbour, or if the neighbour's RSVP control plane has restarted.

Error Message     
 
    
    
   

%ROUTING-RSVP-6-RSVP_HELLO_STATE_UP A graceful restart hello session to [chars] has been established

Explanation    A new hello session with a neighbour has been established

Recommended Action    No action is required.

RUMP Messages

Error Message     
 
    
    
   

%ROUTING-RUMP-2-ERR_MEM_ALLOC No memory for [chars]

Explanation    The requested operation could not be accomplished because of a low memory condition.

Recommended Action    This indicates a low memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%ROUTING-RUMP-3-ERR_INIT Initialization failed for [chars] ([chars])

Explanation    An error occurred during initialization.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RUMP-3-ERR_SYSDB SysDB Error: [chars] ([chars])

Explanation    An error occurred when accessing the system database.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RUMP-3-INTERNALERR Internal error: [chars]

Explanation    An internal software error occurred.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-RUMP-3-RIB_FAIL RIB failure for [chars] ([chars])

Explanation    RIB initialization failed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

SAP_LISTEN Messages

Error Message     
 
    
    
   

%ROUTING-SAP_LISTEN-3-BAG_RELATED_ERROR Bag related error: [chars] : [chars]

Explanation    The SAP had trouble wth Bags.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-SAP_LISTEN-3-DEBUG_INIT_FAILED Debug Initialization failed

Explanation    Debug Error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-SAP_LISTEN-3-EVENT_CONN_MGR_ERROR Event connection manager error:[chars]

Explanation    Failed to open connection to Connection Manager.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-SAP_LISTEN-3-EVENT_MGR_CREATE_FAILED A call to event_manager_create() failed

Explanation    A problem occurred while calling the event_manager_create() API.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-SAP_LISTEN-3-GEN_ERR [chars] : [chars]

Explanation    General error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-SAP_LISTEN-3-MALLOC_FAILED malloc() failed : failed to allocate memory to receive messages

Explanation    A call to malloc() failed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-SAP_LISTEN-3-SOCKET_ERROR Socket Error : [chars]

Explanation    Socket Error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-SAP_LISTEN-3-SYSDB_ACCESS_ERROR Sysdb related error: [chars]

Explanation    The SAP listener had trouble accessing SysDB.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-SAP_LISTEN-3-SYSDB_REGISTRATION_FAILED Sysdb registration error: [chars]

Explanation    The SAP had trouble registering as a notifier with SysDB.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-SAP_LISTEN-3-TIMER_ERROR Timer Error : [chars]

Explanation    Timer Error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%ROUTING-SAP_LISTEN-3-TUPLE_ERROR Tuple operation error : [chars]

Explanation    Tuple operation failed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information