Cisco IOS XR System Error Message Reference Guide, Release 3.5
Services Messages
Downloads: This chapterpdf (PDF - 434.0KB) The complete bookPDF (PDF - 18.83MB) | Feedback

Services Messages

Table Of Contents

Services Messages

RSPP_MA Messages

rspp_rio_ea Messages

RSPP_REPO Messages

RSPP_REX Messages

RSPP_ROXI Messages

SD_COMMON Messages

SD Messages

SRD_AGENT Messages

SRD_LIB Messages

SRD Messages

SVII_EA_GSR Messages

TTY Messages


Services Messages


This section contains all Services related System Error Messages. The following facility codes are represented in this module:

RSPP_MA Messages

rspp_rio_ea Messages

RSPP_REPO Messages

RSPP_REX Messages

RSPP_ROXI Messages

SD_COMMON Messages

SD Messages

SRD_AGENT Messages

SRD_LIB Messages

SRD Messages

SVII_EA_GSR Messages

TTY Messages

RSPP_MA Messages

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-2-IMP_FAILED An error was detected while performing [chars] for [chars] (Error: [chars]). Traffic Diversion may now be inconsistent.

Explanation    Some aspect of diversion implementation has failed. This means that traffic may be inconsistently diverted for the specified interface (ie traffic may be diverted to the service card in the ingress direction, but not on egress). Note that, where the error message indicates a single interface that is affected, there may also be other attachments impacted by the error.

Recommended Action    Restarting the rspp_ma process on the node which produced the error may solve the issue. If not, contact support.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-3-EVENT Error receiving event: [chars]

Explanation    An error occured receiving an event from the OS. The process will restart.

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     
 
    
    
   

%SERVICES-RSPP_MA-3-IMP_ERROR A persistent error has occured during the implementation of one or more attachments. Diversion may be in an inconsistent state

Explanation    While attempting to implement one or more attachments, the service diversion infrastructure has hit one or more problems that were not solved by a retry, and as such one or more diversions may be in an inconsistent state. Retries will continue to be made, and a further message will be printed if this situation clears.

Recommended Action    Running 'show firewall attachments' will provide information on which attachments are suffering from errors, and in which way they will not be operating correctly. These problems may be cleared by removing and re-attaching the service to the specified interface. If this does not resolve the problem, then support should be contacted.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-3-INIT Failure during intialization of RSPP MA [chars]. Error: [chars]

Explanation    A failure occurred during the initialization of the RSPP MA, the process responsible for managing the diversion of packets to services such as firewalls. The initialization will be aborted and retried.

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     
 
    
    
   

%SERVICES-RSPP_MA-3-INIT_NON_FATAL Non-fatal error during intialization of RSPP MA [chars]: [chars] Continuing with initialization.

Explanation    A non-fatal failure occurred during the initialization of the specified module of RSPP MA, the process responsible for managing the diversion of packets to services such as firewalls. This will typically mean that some level of debugging support will not be provided for the process (e.g. error codes will not be decoded), but the functioning of the process is not otherwise affected. Restarting the process should restore full debugging support.

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     
 
    
    
   

%SERVICES-RSPP_MA-3-LCFG_DELETE Failed to process local configuration delete for interface [chars]. Error: [chars]

Explanation    An error has occurred while removing the diversion implemented for the given interface. The error string will give more detail on the type of error that has occurred.

Recommended Action    For non-resource errors, adding and removing a service attachment for the interface indicated in the message may remove the error. 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. If the error is a resource error this will be indicated in the error description given. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If any inconsistency in packet forwarding to the indicated interfaces is seen, a restart of RSPP MA may solve the problem.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-3-LCFG_UPDATE Failed to process local configuration update for attachment of service [chars] of type [chars] to interface [chars] with attachment ID [chars]. Error: [chars]

Explanation    An error has occurred while implementing the diversion required for the given service attachment. The error string will give more detail on the type of error that has occurred.

Recommended Action    For non-resource errors, removing and adding back the configuration that prompted the message may remove the error. 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. If the error is a resource error this will be indicated in the error description given. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If any inconsistency in packet forwarding to the indicated interfaces is seen, a restart of RSPP MA may solve the problem.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-3-NO_VFW RSPP MA was started when the firewalls package was not installed. Exiting

Explanation    RSPP MA, the service diversion management agent, could not complete initialization as the firewall service package could not be found in the current installed image. Restart will not be attempted.

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     
 
    
    
   

%SERVICES-RSPP_MA-3-PUBLISH_DELETE Failed to publish local configuration delete for interface [chars]. Error: [chars]

Explanation    An error has occurred while indicating the deletion of the given service attachment removal to nodes other than that local to the interface indicated. Packet diversion may now be inconsistent. The error string will give more detail on the type of error that has occurred.

Recommended Action    For non-resource errors, adding and removing a service attachment for the interface indicated in the message may remove the error. 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. If the error is a resource error this will be indicated in the error description given. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If any inconsistency in packet forwarding to the indicated interfaces is seen, a restart of RSPP MA may solve the problem.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-3-PUBLISH_UPDATE Failed to publish local configuration update for attachment of service [chars] of type [chars] to interface [chars] with attachment ID [chars] to remote nodes. Error: [chars]

Explanation    An error has occurred while indicating the occurence of the given update to nodes other than that local to the interface indicated. Packet diversion may now be inconsistent. The error string will give more detail on the type of error that has occurred.

Recommended Action    For non-resource errors, removing and adding back the configuration that prompted the message may remove the error. 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. If the error is a resource error this will be indicated in the error description given. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If any inconsistency in packet forwarding to the indicated interfaces is seen, a restart of RSPP MA may solve the problem.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-3-RCFG Failed to process remote config notification of [chars] of attachment of service [chars] of type [chars] to interface [chars] with attachment ID [chars]. Error: [chars]

Explanation    An error has occurred while processing the attachment of a service to an interface remote to this node. Packet diversion may now be inconsistent on this node. The error string will give more detail on the type of error that has occurred.

Recommended Action    For non-resource errors, removing and adding back the configuration that prompted the message may remove the error. 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. If the error is a resource error this will be indicated in the error description given. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If any inconsistency in packet forwarding to the indicated interfaces is seen, a restart of RSPP MA may solve the problem.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-3-RCFG_REFRESH Error deleting any stale attachment publications to remote nodes. Error: [chars]

Explanation    If a virtual firewall or other service is attached to an interface, then all cards in the system need to know. Similarly, if a service attachment is deconfigured, then all cards needs to be notified. This will not happen if the interface's line card is down (eg a preconfigured attachment is removed while the card is absent from the chassis and then re-inserted). A backup mechanism exists for this case, that ensures that any attachments that were deconfigured in such a situation really are removed globally. This error indicates that a problem occurred with this backup mechanism. So if a service attachment was deconfigured while the card was down, the rest of the system might not have caught up, and could still be diverting or dropping traffic for that interface.

Recommended Action    If an interface seems 'stuck', then configuring an attachment again, committing the configuration, and then de-configuring that attachment and comitting should un-stick it.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-4-DUP_CREATE Attachment of service [chars] of type [chars] to interface [chars] with attachment ID [chars] invalid due to duplicate attachment to interface [chars]. Both attachments will be invalidated.

Explanation    The same service attachment has been configured on two or more interfaces, resulting in both attachments being viewed as failed and moved in to failure state.

Recommended Action    Removing the given configuration until zero or one instances of the attachment exist will resolve this misconfiguration.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-4-DUP_CREATE_ERR Error withdrawing attachment of service [chars] of type [chars] to interface [chars] with attachment ID [chars] (invalid due to duplicate attachment to interface [chars]): [chars]

Explanation    An error has occurred processing an invalid configuration whereby the same service attachment has been configured on two or more interfaces (which should result in both attachments being viewed as failed and moved in to failure state). Packet diversion may now be inconsistent. The error string will give more detail on the type of error that has occurred.

Recommended Action    For non-resoucre errors, removing the initial misconfiguration may remove this error. If the error is a resource error this will be indicated in the error description given. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If any inconsistency in packet forwarding to the indicated interfaces is seen, a restart of RSPP MA may solve the problem.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-4-DUP_REMOVE Attachment of service [chars] of type [chars] to interface [chars] with attachment ID [chars] now valid due to removal of duplicate attachment to interface [chars]. Attachment will be reimplemented.

Explanation    The given attachment configuration, which was previously invalid due to duplicate attachments being configured on different interfaces, is now valid as the duplicate attachment configuration has been removed.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-4-DUP_REMOVE_ERR Error reinstalling attachment of service [chars] of type [chars] to interface [chars] with attachment ID [chars] (now valid due to removal of duplicate attachment to interface [chars]): [chars]

Explanation    The given attachment configuration, which was previously invalid due to duplicate attachments being configured on different interfaces, is now valid as the duplicate attachment configuration has been removed, but an error has occurred reimplementing the attachment. The error string given should give more details on the error that has occurred.

Recommended Action    For non-resource errors, removing and adding back the configuration that prompted the message may remove the error. 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. If the error is a resource error this will be indicated in the error description given. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If any inconsistency in packet forwarding to the indicated interfaces is seen, a restart of RSPP MA may solve the problem.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-4-FA_BATCH_ERR Errors occurred processing batch of failure action notifications. Total Errors: [unsigned int], First Error [chars]

Explanation    One or more errors occurred in RSPP MA, the service diversion management agent, during the processing of a set of configuration detailing the failure policies to be applied in the event of service failure. The configured failure policies may now not be implemented on the node indicated. The error string will give more detail on the type of error that has occurred.

Recommended Action    For non-resource errors, removing and adding back the configuration that prompted the message may remove the error. 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. If the error is a resource error this will be indicated in the error description given. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If any inconsistency in packet forwarding to the indicated interfaces is seen, a restart of RSPP MA may solve the problem.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-4-RCFG_BATCH Failed to signal [chars] of batch of remote config publications. Error: [chars]

Explanation    An error has occurred sending information on service attachments to interfaces local to the node to remote nodes.

Recommended Action    For non-resource errors, removing and adding back the configuration that prompted the message may remove the error. 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. If the error is a resource error this will be indicated in the error description given. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If any inconsistency in packet forwarding to the indicated interfaces is seen, a restart of RSPP MA may solve the problem.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-4-RED_STATE_ERR Error handling change in redundancy state. Error [chars]

Explanation    An error has occurred during the handling of a notification from Sysmgr indicating a change in the redundancy state of the card indicated (e.g. from standby to online).

Recommended Action    Restarting RSPP MA may solve the problem. 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     
 
    
    
   

%SERVICES-RSPP_MA-4-RED_STATE_UNK Unable to handle redundancy state notification. New redundancy state [unsigned int], previous state [unsigned int]

Explanation    A notification has been received from Sysmgr indicating that the redundancy state (e.g. active, standby, etc) of the card has changed to a state unknown to RSPP MA. RSPP MA will continue to use the old state.

Recommended Action    A restart of RSPP MA may solve the problem. 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     
 
    
    
   

%SERVICES-RSPP_MA-4-RESYNC_FAILED Failed to resync diversions correctly. Error: [chars]

Explanation    An error has occurred following a restart of RSPP MA in the reconciliation of persistent data structures with the current configuration. Packet diversion may now be inconsistent.

Recommended Action    Restarting RSPP MA may clear the error. 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     
 
    
    
   

%SERVICES-RSPP_MA-4-SD_BATCH_ERR Errors occurred processing batch of Service Director notifications. Total Errors: [unsigned int], First Error [chars]

Explanation    One or more errors occurred in RSPP MA, the service diversion management agent, during the processing of a set of notifications from Service Director, containing service locations and diversion information. Diversions for service attachments may now be inconsistent on the given node. The error string will give more detail on the type of error that has occurred.

Recommended Action    If the error is a resource error this will be indicated in the error description given. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If any inconsistency in packet forwarding to the indicated interfaces is seen, a restart of RSPP MA may solve the problem. If the error string given does not indicate that this is a resource error, 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     
 
    
    
   

%SERVICES-RSPP_MA-4-SD_ERR Error requesting service information from the Service Director on services referenced by the last batch of attachment or failure action configuration. Error [chars]

Explanation    When a service attachment (e.g. a firewall attachment) is configured on an interface, the local RSPP MA process (the service diversion management agent) must request information on the attached service from Service Director to be able to implement the required diversion. This error indicates that a problem has arisen in this request. The error string given should give more details on the error that has occurred.

Recommended Action    For non-resource errors, removing and adding back the configuration that prompted the message may remove the error. 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. If the error is a resource error this will be indicated in the error description given. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If any inconsistency in packet forwarding to the indicated interfaces is seen, a restart of RSPP MA may solve the problem.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-4-SD_REFRESH SD Messages lost. Restarting to handle

Explanation    Service Director has indicated that a problem has occurred that may have caused internal messages to be dropped. RSPP MA is restarting to handle.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-6-IMP_ERROR_CLEARED All pre-existing persistent errors have been cleared. All diversion should now be operating correctly.

Explanation    This message should only be seen after a corresponding IMP_ERROR message has been seen. It indicates that any problems with diversions should now have been resolved.

Recommended Action    No further action should be necessary.

Error Message     
 
    
    
   

%SERVICES-RSPP_MA-6-PROBLEM_EXITING Problem ensuring an orderly exit: [chars]

Explanation    The process implementing service diversions (eg for virtual firewalls) has just exited, since the last service attachments have just been deconfigured. As part of this orderly shutdown, the process tried to inform System Manager that this was happening, but hit a problem in signalling this fact. The system should have recovered from this problem fully; however, very rarely it is possible that some other service attachment configuration in the same commit could be rejected.

Recommended Action    If any service attachments in the same configuration commit were rejected, simply re-commit them.

rspp_rio_ea Messages

Error Message     
 
    
    
   

%SERVICES-rspp_rio_ea-3-DEBUG Failed to initialize service ingress diversion debug facility: [chars]

Explanation    An error occurred during initialization of the service ingress diversion debug facility. The 'debug services diversion rio ea' command will not function correctly. Otherwise service ingress diversion will work correctly. Executing the command 'proc restart rspp_rio_ea' for the node where the error message originated might resolve this condition.

Recommended Action    This is not a fatal error.

Error Message     
 
    
    
   

%SERVICES-rspp_rio_ea-3-DM_REMOVE Failed to remove service ingress diversion (ifh=[hex]). Could not remove [chars]: [chars]

Explanation    An error occurred during service ingress diversion removal from the specified interface.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%SERVICES-rspp_rio_ea-3-EDM Failed to initialize service ingress diversion External Data Manager: [chars]

Explanation    During initialization of the EDM an error occurred. The EDM was not successfully registered, so show commands and other manageability applications may not function correctly. Otherwise service ingress diversion will work correctly. Executing the command 'proc restart rspp_rio_ea' for the node where the error message originated might resolve this condition.

Recommended Action    This is not a fatal error.

Error Message     
 
    
    
   

%SERVICES-rspp_rio_ea-3-EVENT_BLOCK An error was received during event_block: [chars]

Explanation    The service ingress diversion process received an error while waiting for events from other processes in the system. The process will be restarted.

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%SERVICES-rspp_rio_ea-3-EVM_CREATE_FAILED RSPP RIO event manager create failed: [chars].

Explanation    An error occurred during initialization of service ingress diversion process. The process could not create an event queue used to communicate with other processes in the system. The initialization will be aborted and retried.

Recommended Action    This condition might indicate a low memory condition. Reduce other system activity to ease memory demand. 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     
 
    
    
   

%SERVICES-rspp_rio_ea-3-FM_INIT_REPLAY Could not re-synchronize with feature manager process: [chars]

Explanation    During the initialization of ingress diversion process, feature manager process requested a replay of all current diversions but the replay operation failed.

Recommended Action    If this message is reported more than once, execute the command 'proc restart feat_mgr' for the node where the error message originated.

Error Message     
 
    
    
   

%SERVICES-rspp_rio_ea-3-IMP_INIT_ERR IMP initialization failed during [chars]: [chars]

Explanation    The service ingress diversion process failed while trying to connect to Interface Manager Proxy process. The process will be restarted. If error still exists, execute the command 'proc restart imp' for the node where the error message originated.

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%SERVICES-rspp_rio_ea-3-INIT_FAILED Ingress Diversion process initialization failed following [unsigned int] function call(s): [chars].

Explanation    An error occurred during the initialization of service ingress diversion process. The initialization will be aborted and retried. Current and future service to an interface will fail until successful process initialization.

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%SERVICES-rspp_rio_ea-3-MEM During ingress diversion installation or update, failed to get memory for [chars]

Explanation    During processing of a new or existing service ingress diversion, insufficient memory was available. The diversion information was not applied, and future updates may also not be applied correctly.

Recommended Action    This indicates a low memory condition. *REDUCE* Once the memory condition is resolved, execute the command 'proc restart rspp_rio_ea' for the node where the error message originated to ensure all diversion information is correctly set up. 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     
 
    
    
   

%SERVICES-rspp_rio_ea-3-TRACE Failed to initialize service ingress diversion trace facility: [chars]

Explanation    An error occurred during initialization of the trace facility. There will be no trace messages for service ingress diversion. The 'show services diversion rio ea trace' command on this node will not function correctly. Otherwise service ingress diversion will work correctly. Executing the command 'proc restart rspp_rio_ea' for the node where the error message originated might resolve this condition.

Recommended Action    This is not a fatal error.

Error Message     
 
    
    
   

%SERVICES-rspp_rio_ea-6-CORE The service ingress diversion process has reached an unexpected situation ([chars] dumping core - this is NOT a crash.

Explanation    An unexpected situation was reached; the service ingress diversion process has voluntarily produced a core dump for debugging purposes. Unless other symptoms are seen than it can be assumed that the system has recovered.

Recommended Action    *SUPPORT*

RSPP_REPO Messages

Error Message     
 
    
    
   

%SERVICES-RSPP_REPO-3-DUAL_ERR Error encountered by REPO while processing a dual adjacency update request for the adjacency for interface handle [hex]: [chars]

Explanation    An error has occurred in the FIB library responsible for implementing diversions (e.g. for virtual firewall attachments) on a service card, following a call by FIB to retrieve the post-egress diversion forwarding information. If the interface given has a service attached then forwarding following egress diversion to this service may now be incorrect as a result of this error.

Recommended Action    Restarting the fib_mgr process on the node which produced the error may solve the issue. If not, contact support.

Error Message     
 
    
    
   

%SERVICES-RSPP_REPO-3-INIT Error initializing REPO: [chars]

Explanation    An error has occurred during the initialization of the FIB library responsible for implementing diversions (e.g. for virtual firewall attachments). Service attachments may now fail to be implemented properly as a result of this error.

Recommended Action    Restarting the fib_mgr process on the node which produced the error may solve the issue. If not, contact support.

Error Message     
 
    
    
   

%SERVICES-RSPP_REPO-3-INIT_MSG Error encountered by REPO while processing the initialization message from RSPP MA: [chars]

Explanation    An error has occurred in the IPC between the Management Agent for service diversions (e.g. for virtual firewall attachments) and the FIB Library responsible for implementing them, in the initialization stage. The initialization will be aborted, and no changes to service attachment configuration will be made in the forwarding plane

Recommended Action    Restarting the fib_mgr process on the node which produced the error may solve the issue. If not, contact support.

Error Message     
 
    
    
   

%SERVICES-RSPP_REPO-3-TWEAK_ERR Error encountered by REPO while processing an adjacency update request for the adjacency for interface handle [hex]: [chars]

Explanation    An error has occurred in the FIB library responsible for implementing diversions (e.g. for virtual firewall attachments) following a request from FIB to check whether a diversion should be in place for the given adjacency. The adjacency given may now be incorrect as a result of this error.

Recommended Action    Restarting the fib_mgr process on the node which produced the error may solve the issue. If not, contact support.

Error Message     
 
    
    
   

%SERVICES-RSPP_REPO-3-UPDATE_MSG Error encountered by REPO while processing the diversion update message ([hex]) from RSPP MA: [chars]

Explanation    An error has occurred in the IPC between the Management Agent for service diversions (e.g. for virtual firewall attachments) and the FIB Library responsible for implementing them, during a diversion update. The update will not be implemented.

Recommended Action    Restarting the fib_mgr process on the node which produced the error may solve the issue. If not, contact support.

RSPP_REX Messages

Error Message     
 
    
    
   

%SERVICES-RSPP_REX-3-EDM Failed to initialize diversion manager external data manager, error: [chars]. Diagnostic show commands may not function correctly, other functionality is unaffected.

Explanation    During intialization of the EDM an error occurred. The EDM was not successfully registered, so show commands and other manageability applications may not function correctly. Otherwise the diversion manager will work correctly.

Recommended Action    This is not a fatal error. If the show commands are required, restarting the REX process should clear up the problem.

Error Message     
 
    
    
   

%SERVICES-RSPP_REX-3-IMP_CONNECT Failed to connect to IM Proxy. Error: [chars]

Explanation    The diversion manager was unable to connect to IM Proxy to register as an interface capsulation. Diversion information may not be correctly applied or inconsistent.

Recommended Action    The connection will be retried automatically. 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     
 
    
    
   

%SERVICES-RSPP_REX-3-INIT Failure [chars] during intialization of diversion exectution agent. Error: [chars]

Explanation    A failure occurred during the initialization of the RSPP REX library. This is used to divert packets, e.g. to a virtual firewall.

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     
 
    
    
   

%SERVICES-RSPP_REX-3-MEM Diversion manager failed to get memory [chars]. Diversions (e.g to a virtual firewall) may not have been correctly applied.

Explanation    During processing of a new or updated diversion, insufficient memory was available. The diversion information was not applied, and future updates may also not be applied correctly.

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. Once the memory condition is resolved, execute the command 'proc restart rspp_rex' for the node where the error message originated to ensure all diversion information is correctly set up.

Error Message     
 
    
    
   

%SERVICES-RSPP_REX-3-MSG_REPLY Unable to send a reply to diversion manager's client. Error: [chars]

Explanation    The diversion manager process was unable to send a reply to a message sent to one of its clients. Diversion information may be inconsistent.

Recommended Action    Restarting the rspp_rex and fwc processes should clear the problem. 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     
 
    
    
   

%SERVICES-RSPP_REX-3-SYSDB Diversion manager failed to communicate with SysDB. Error: [chars]

Explanation    The diversion manager was unable to communicate with SysDB. Notifications may be missed, and manageability functionality may not be available.

Recommended Action    Check the status of SysDB, and restart the SysDB and firewall controller processes.

Error Message     
 
    
    
   

%SERVICES-RSPP_REX-6-CORE The diversion manager has reached an unexpected situation ([chars] dumping core - this is NOT a crash.

Explanation    An unexpected situation was reached; the diversion manager has voluntarily produced a core dump for debugging purposes. This does not affect the operation of the diversion 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.

RSPP_ROXI Messages

Error Message     
 
    
    
   

%SERVICES-RSPP_ROXI-3-IMP_CONNECT Failed to connect to IM Proxy. Error: [chars]

Explanation    The replicated interface owner was unable to connect to IM Proxy to register as an interface owner. Diversion information may not be correctly applied or inconsistent.

Recommended Action    The connection will be retried automatically. 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     
 
    
    
   

%SERVICES-RSPP_ROXI-3-INIT Failure [chars] during intialization of replicated interface owner. Error: [chars]

Explanation    A failure occurred during the initialization of the replicated interface owner process. This means that attaching services (e.g a firewall) on the card producing this error to interfaces may not work.

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     
 
    
    
   

%SERVICES-RSPP_ROXI-3-MEM Replicated interface owner failed to get memory [chars] during diversion update processing. Diversions (e.g to a virtual firewall) may not have been correctly applied, and future diversion may also not be correctly applied.

Explanation    During processing of a new or updated diversion, insufficient memory was available. The diversion information was not applied, and future updates may also not be applied correctly.

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. Once the memory condition is resolved, execute the command 'proc restart rspp_roxi' for the node where the error message originated to ensure all diversion information is correctly set up.

Error Message     
 
    
    
   

%SERVICES-RSPP_ROXI-3-REPLICATE Bulked operation to [chars] [unsigned int] replicated interface(s) (including [hex]) failed with error: [chars]. Packet diversion may now be incorrectly set up.

Explanation    During the processing of interface create or delete notifications an error occurred that means the interfaces may not have been replicated or unreplicated correctly. This might result in the packets that are diverted to the node being dropped. A user with cisco-support privileges may find the interface name corresponding to the given interface handle using 'show im chains ifhandle'

Recommended Action    Restart the rspp_roxi process on the affected node; 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.

SD_COMMON Messages

Error Message     
 
    
    
   

%SERVICES-SD_COMMON-3-SEND_FAILED Failed to send a '[chars]' message: '[chars]'

Explanation    A required control message could not be sent. The reason for the failure is detailed in the message. The failure is unexpected, and likely caused by a failure in the underlying transport. Services controlled by this process are likely to be out of sync as a result.

Recommended Action    Restart the 'service_director' process to force a resync of all data, which will recover the lost message. 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.

SD Messages

Error Message     
 
    
    
   

%SERVICES-SD-3-ASSERT ASSERT failure: [chars]

Explanation    The process is in an inconsistent state. The process will exit and restart. All data will be resynchronised after the restart.

Recommended Action    No action is required to recover the system, this will happen automatically. Report this issue to your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SERVICES-SD-3-INIT_FAILED Initialisation failed, module: [chars], operation: [chars], error: [chars]

Explanation    The Service Director has failed to start up. The operation being attempted is detailed in the error message. The Service Director will be restarted automatically.

Recommended Action    If the error indicates an Out Of Memory error, then attempt to increase the available resources. Otherwise, if the error persists, contact your technical support representative copying the error message exactly as it appears.

Error Message     
 
    
    
   

%SERVICES-SD-3-LOOP_FAILED Unexpected error in event loop: [chars]

Explanation    An unexpected error has been encountered in the main Service Director event loop. The Service Director will be automatically restarted, and should recover by itself.

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     
 
    
    
   

%SERVICES-SD-3-NOMEM Insufficient resources: [chars]

Explanation    There are insufficient resources to perform some action. The error message contains more details about what action failed. In any case, services may not be operating correctly, and states may be out of sync.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Once the memory conditions have been improved, restart the Service Director process to allow it to resynchronise with its clients.

Error Message     
 
    
    
   

%SERVICES-SD-3-SYSMGR_FAIL SysMgr didn't respond when told we're exiting: [chars]

Explanation    The Service Director attempted to notify SysMgr that it was exiting and SysMgr returned an error. If this coincides with an attempt to configure the locations of a service, then further error may be observed from SysDB.

Recommended Action    Restart the Service Director process. 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     
 
    
    
   

%SERVICES-SD-4-INVALID_FIND_SERVICE An invalid Service Find request was received (type [hex])

Explanation    The Service Director received a batch with an invalid service type field. This can be due to message corruption, or due to a timing issue but is most likely due to an error in a service process. Except in the latter case (when it will most probably be repeated) this error is not fatal.

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     
 
    
    
   

%SERVICES-SD-4-WRONG_SSC Invalid SSC is sending updates on node [hex]. Beginning recovery

Explanation    A Service Controller process not currently registered is sending updates from a node. The Service Director will now attempt to recover from this by resynchronising with its clients.

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     
 
    
    
   

%SERVICES-SD-6-RESTART_SELF The Service Director process requires a restart in order to synchronize data. This message is informational and requires no further action. The reason for restart is: [chars]

Explanation    The Service Director encountered an error when trying to send a control message, which could leave the system in an inconsistent state. The error results from an unexpected failure in the transport infrastructure. The process is now restarting and will then be able to resynchronize its state, restoring system consitency. This message is for informational purposes only, and no further action is required as a result. On completion of the resyncronization, the system will have self-healed, unless any further errors are encountered.

Recommended Action    No action is required unless further errors are observed. If further errors are encountered, wait until possible root problems (such as node reload, or low memory conditions) have been resolved, and restart the Service Director. 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.

SRD_AGENT Messages

Error Message     
 
    
    
   

%SERVICES-SRD_AGENT-6-NODE_REBOOTING A change in role requires Node [chars] to go down for reboot.

Explanation    The Service Role Agent has determined a role change requires a reboot of the specified node. This is not an error.

Recommended Action    None. This is expected behaviour when changing the role of a card.

SRD_LIB Messages

Error Message     
 
    
    
   

%SERVICES-SRD_LIB-4-NOTIFICATION_FAILED SRD Library notification failure: [chars]

Explanation    The Service Role Daemon client library received a notification, but was unable to perform the necessary operations to execute the client's callback function. The client process is unaware of a role change event that has occured, and as such services running on the affected node are likely to be out of sync.

Recommended Action    In order to force a resync of the current role status, restart the process that emitted this error. If the error string indicates a low resource condition, first free up some resources. 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.

SRD Messages

Error Message     
 
    
    
   

%SERVICES-SRD-3-ASSERT ASSERT failure: [chars]

Explanation    The process is in an inconsistent state. The process will exit and restart. All data will be resynchronised after the restart.

Recommended Action    No action is required to recover the system, this will happen automatically. Report this issue to your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SERVICES-SRD-3-INIT_FAILED Initialisation failed, module: [chars], operation: [chars], error: [chars]

Explanation    The Service Role Daemon has failed to start up. The operation being attempted is detailed in the error message. The Service Role Daemon will be restarted automatically.

Recommended Action    If the error indicates an Out Of Memory error, then attempt to increase the available resources. Otherwise, if the error persists, contact your technical support representative copying the error message exactly as it appears.

Error Message     
 
    
    
   

%SERVICES-SRD-3-LOOP_FAILED Unexpected error in event loop: [chars]

Explanation    An unexpected error has been encountered in the main Service Role Daemon event loop. The Service Role Daemon will be automatically restarted, and should recover by itself.

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     
 
    
    
   

%SERVICES-SRD-3-NOMEM Insufficient resources: [chars]

Explanation    There are insufficient resources to perform some action. The error message contains more details about what action failed.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Once the memory conditions have been improved, restart the Service Role Daemon process to allow it to resynchronise with its clients.

Error Message     
 
    
    
   

%SERVICES-SRD-4-CARD_NOT_PRESENT The role you are attempting to assign is not supported by the node you have selected.

Explanation    A node has been set to a role which is not supported. This could be because the wrong card is at this location, or no card is there.

Recommended Action    Insert a card of an appropriate type into the specified location. If you believe that the card in the slot is of an appropriate type, ensure it is correctly booted (in IOX-RUN state according to 'show platform'). If everything looks right, and the role is still not enacted, then contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%SERVICES-SRD-4-ERROR_PROCESSING_LRD_EVENT SRD Unable to process OIR notification: [chars]

Explanation    The Service Role Daemon received an LRd event which it was unable to process. This could potentially mean that a card does not have it's specified role enacted, or removed if it was taken down.

Recommended Action    Restart the service_role_daemon process to resync all roles and replay the lost notification. 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     
 
    
    
   

%SERVICES-SRD-4-ERROR_STARTING_AGENT Unable to update role on card with Node ID [chars]: [chars]

Explanation    The Service Role Change Agent returned an error while running on this node. The role has not been correctly applied on the specified card.

Recommended Action    Restart the service_role_agent process on the given card manually to enact the role. Assuming no error is returned, restart the service_role_daemon process as well to resync the state and notify all interested clients. 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     
 
    
    
   

%SERVICES-SRD-4-MISSING_TIMER_CONTEXT An error occured while setting role. Role not applied.

Explanation    Required data was not available when a timer expired. A role that should be applied now is unable to be applied.

Recommended Action    Restart the service_role_daemon process to attempt to re-enable the role. 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.

SVII_EA_GSR Messages

Error Message     
 
    
    
   

%SERVICES-SVII_EA_GSR-3-INTF_EXIST Interface '[chars]' of type [unsigned int] already exists as type [unsigned int]

Explanation    An attempt was made to create an interface that already existed, but with a different type. It is likely that the given interface will no longer be operating as expected.

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     
 
    
    
   

%SERVICES-SVII_EA_GSR-3-NOMEM Insufficient memory: [chars]

Explanation    SVII EA ran out of memory. The exact operation being attempted is detailed in the error message.

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

TTY Messages

Error Message     
 
    
    
   

%SESSION-TTY-6-SESSION_STARTUP Skip detailed routine and proceed([chars]) [dec]([chars])

Explanation    The TTY Session startup found some error. Error is ignored and console will be activated.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%SESSION-TTY-7-SESSION_STARTUP_OK [chars]

Explanation    Debug message

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.