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

Services Messages

Table Of Contents

Services Messages

IPSEC_SVI_EA Messages

IPSEC_SVI_NETIO Messages

IPSEC_SVIA Messages

OT Messages

RSPP_REPO Messages

rspp_rio_ea Messages

RSPP_ROXI Messages

SBC_RSRCMON Messages

SBC Messages

SBCSVI_BILLING Messages

SBCSVI_EA Messages

SBCSVI_NETIO Messages

SVII_EA_STATS Messages

SVII_EA Messages

SVII_LRD_SPA Messages

SVII_MGR Messages

VASI_EA Messages

VASI_MA Messages

VASI_NETIO Messages


Services Messages


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

IPSEC_SVI_EA Messages

IPSEC_SVI_NETIO Messages

IPSEC_SVIA Messages

OT Messages

RSPP_REPO Messages

rspp_rio_ea Messages

RSPP_ROXI Messages

SBC_RSRCMON Messages

SBC Messages

SBCSVI_BILLING Messages

SBCSVI_EA Messages

SBCSVI_NETIO Messages

SVII_EA_STATS Messages

SVII_EA Messages

SVII_LRD_SPA Messages

SVII_MGR Messages

VASI_EA Messages

VASI_MA Messages

VASI_NETIO Messages

IPSEC_SVI_EA Messages

Error Message     
 
    
    
   

%SERVICES-IPSEC_SVI_EA-3-INITFAIL Failure during initialization. Error: [chars]

Explanation    A failure occurred during the initialization of the IPSec SVI EA process on a particular node. The process will be restarted. Until the process starts successfully, any IPSec SVI interfaces located on that node will not come up. (If there is a standby node the interfaces should come up on the standby).

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-IPSEC_SVI_EA-3-INTERNAL [chars]

Explanation    An unexpected internal error has occurred in the IPSec SVI EA process. 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-IPSEC_SVI_EA-3-INTERNAL_ERR [chars] : [chars]

Explanation    An unexpected internal error has occurred in the IPSec SVI EA process. 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-IPSEC_SVI_EA-3-LINK_FAIL Error while [chars]ing [unsigned int] interfaces: [chars]

Explanation    An error occurred while attempting to program HW for IPSec SVI on specified node. The interfaces will not come up. If there is a standby node configured for the interfaces, they may come up on the standby.

Recommended Action    It may help to shut down, then bring up, the IPSEc SVI interfaces in question.

Error Message     
 
    
    
   

%SERVICES-IPSEC_SVI_EA-3-NOT_FOUND Received request for an interface (0x[pointer]) that is not in our database

Explanation    The IPSec SVI EA process received a request to process an interface that does not exist in its database. This indicates some sort of internal inconsistency.

Recommended Action    It may help to restart the IPSec SVI EA process. If there are any obvious resource problems (e.g. memory exhaustion), these must be fixed first. 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-IPSEC_SVI_EA-3-SSC_SEND Error while sending messages to Service Director: [chars]

Explanation    A problem was encountered while trying to send a batch of messages to the Service Director. The Service Director may not be up to date with the state of services on this node, so IPSec SVI interfaces located on this node may fail to forward packets.

Recommended Action    It may help to restart the IPSec SVI EA process. If there are any obvious resource problems (e.g. memory exhaustion), these must be fixed first. 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-IPSEC_SVI_EA-3-SSC_SEND_SRV Error while sending message about [chars] to Service Director: [chars]

Explanation    A problem was encountered while trying to send a single message to the Service Director. The Service Director may not be up to date with the state of this services on this node, so the associated IPSec SVI interfaces located on this node may fail to forward packets.

Recommended Action    It may help to restart the IPSec SVI EA process. If there are any obvious resource problems (e.g. memory exhaustion), these must be fixed first. 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-IPSEC_SVI_EA-3-STATE_CHANGE An error occurred while checking the state for '[chars]': [chars]

Explanation    While the IPSec SVI EA process was checking the state for the specified interface, an error was encountered. The interface in question may be left in an inconsistent state.

Recommended Action    It may help to restart the IPSec SVI EA process. If there are any obvious resource problems (e.g. memory exhaustion), these must be fixed first. 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.

IPSEC_SVI_NETIO Messages

Error Message     
 
    
    
   

%SERVICES-IPSEC_SVI_NETIO-3-INIT_DEBUG Failure of debug intialization during [chars]. Error: [chars]

Explanation    A failure occurred during the initialization of debug for the NetIO caps. If this occured during an upgrade operation then it will cause the NetIO process to reload. Otherwise this will cause the capsulation to be unloaded, and an error returned to the user.

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-IPSEC_SVI_NETIO-3-INIT_TRACE Failure initializing tracing ([chars] buffer). Error: [chars]

Explanation    A failure occurred during the initialization of tracing for the NetIO caps. This will cause the capsulation to be unloaded, and an error returned to the user.

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.

IPSEC_SVIA Messages

Error Message     
 
    
    
   

%SERVICES-IPSEC_SVIA-4-TUNNEL_SOURCE_CONFLICT Interface [chars] tunnel source IP address conflicts with other system local IP address

Explanation    The interface's tunnel source IP address is configured as a system local IP address.

Recommended Action    Either configure a different tunnel source IP address or change this local system IP address to any other.

OT Messages

Error Message     
 
    
    
   

%SERVICES-OT-3-ERROR [chars]

Explanation    Internal 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     
 
    
    
   

%SERVICES-OT-4-WARNING [chars]

Explanation    Internal Warning.

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-OT-6-TRACK_INFO [chars]

Explanation    Internal information. for example: track state changes.

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_REPO Messages

Error Message     
 
    
    
   

%SERVICES-RSPP_REPO-3-DUAL_ERR Error encountered by REPO whilst 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 whilst 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 whilst 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 whilst 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_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 equals [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_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 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.

SBC_RSRCMON Messages

Error Message     
 
    
    
   

%SERVICES-SBC_RSRCMON-1-ALERT SBC resource monitor: [chars] alarm raised. System is now congested. All new calls will be rejected. cpu usage equals [dec], mem state equals [dec]

Explanation    The system is in congested state. Red alarm has been raised. No new calls will be accepted

Recommended Action    reduce the call rate

Error Message     
 
    
    
   

%SERVICES-SBC_RSRCMON-2-WARNING SBC resource monitor: [chars]

Explanation    The system is not able to carry on congestion handling.

Recommended Action    Restart the sbc proces

Error Message     
 
    
    
   

%SERVICES-SBC_RSRCMON-6-INFO SBC resource monitor: Alarm cleared. System is now in normal state. cpu usage equals [dec], mem state equals [dec]

Explanation    The system is in normal state. Alarms have been cleared.

Recommended Action    none

Error Message     
 
    
    
   

%SERVICES-SBC_RSRCMON-7-DEBUG SBC resource monitor: [chars] [dec]

Explanation    Debug messages

Recommended Action    none

SBC Messages

Error Message     
 
    
    
   

%SERVICES-SBC-1-L1 [chars]: [chars]

Explanation    Log level in sbc app is set to higher than nbb_console_unconditional_log_level. Use errmsg facilty to print error message

Recommended Action    collect ips and pd trace

Error Message     
 
    
    
   

%SERVICES-SBC-2-L2 [chars]: [chars]

Explanation    Log level in sbc app is set to higher than nbb_console_unconditional_log_level. Use errmsg facilty to print error message

Recommended Action    collect ips and pd trace

Error Message     
 
    
    
   

%SERVICES-SBC-3-L3 [chars]: [chars]

Explanation    Log level in sbc app is set to higher than nbb_console_unconditional_log_level. Use errmsg facilty to print error message

Recommended Action    collect ips and pd trace

SBCSVI_BILLING Messages

Error Message     
 
    
    
   

%SERVICES-SBCSVI_BILLING-3-CONFERR [chars]
SBC billing paths will not be available

Explanation    Couldn't not establish the SBC instance name from SysDB. SBC instance name is required for the billing cach paths SBC billing application will not be able to save billing records.

Recommended Action    Delete the SBC instance and create it again to mount the SBC billing drives.

Error Message     
 
    
    
   

%SERVICES-SBCSVI_BILLING-3-PATHERR Error: SBC billing cache location [chars] [chars]: [chars]. Make sure that SBC billing drive is installed and formatted.
SBC billing paths will not be available

Explanation    A failure occurred during the creation of an sbc billing cache path. SBC billing application will not be able to save billing records

Recommended Action    Make sure that the the drive needed for the type of SBC billing you need (local or remote) is mounted and formatted. Delete the SBC instance and create again to mount the SBC billing drives.

Error Message     
 
    
    
   

%SERVICES-SBCSVI_BILLING-4-PATHWARN SBC billing path [chars] [chars] [chars]

Explanation    The SBC billing cache path might require some user action to save the billing records in an SBC-instance-specific directory. SBC billing will still work properly but the billing records could either be saved in an SBC-shared directory if the SBC instance name is too long or not saved at all if there is no space left in the drive.

Recommended Action    Make sure that the condition reported doesn't affect the billing records otherwise, correct the condition by changing the SBC instance name or by manually removing the billing files depending on the condition reported.

Error Message     
 
    
    
   

%SERVICES-SBCSVI_BILLING-5-PATHSTATUS SBC billing path [chars] [chars] [chars]

Explanation    The SBC billing cache path mount point status has changed and is being reported to the user for an easier access to the SBC billing records.

Recommended Action    Take note of the paths used by SBC billing to access the SBC billing records

SBCSVI_EA Messages

Error Message     
 
    
    
   

%SERVICES-SBCSVI_EA-3-INITFAIL Failure during initialization. Error: [chars]

Explanation    A failure occurred during the initialization of the SBCSVI EA process on a particular node. The process will be restarted. Until the process starts successfully, any SBCSVI interface located on that node will not come up. (If there is a standby node the interfaces should come up on the standby).

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-SBCSVI_EA-3-INTERNAL [chars]

Explanation    An unexpected internal error has occurred in the SBCSVI EA process. 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-SBCSVI_EA-3-INTERNAL_ERR [chars] : [chars]

Explanation    An unexpected internal error has occurred in the SBCSVI EA process. 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-SBCSVI_EA-3-LINK_FAIL Error while [chars]ing [unsigned int] interfaces: [chars]

Explanation    An error occurred while attempting to join together the two halves of some SBCSVI pairs on the specified node. The pairs will not come up. If there is a standby node configured for the pairs, they may come up on the standby.

Recommended Action    It may help to shut down, then bring up, the SBCSVI interface pairs in question.

Error Message     
 
    
    
   

%SERVICES-SBCSVI_EA-3-NOT_FOUND Received request for an interface (0x[pointer]) that is not in our database

Explanation    The SBCSVI EA process received a request to process an interface that does not exist in its database. This indicates some sort of internal inconsistency.

Recommended Action    It may help to restart the SBCSVI EA process. If there are any obvious resource problems (e.g. memory exhaustion), these must be fixed first. 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-SBCSVI_EA-3-SSC_SEND Error while sending messages to Service Director: [chars]

Explanation    A problem was encountered while trying to send a batch of messages to the Service Director. The Service Director may not be up to date with the state of services on this node, so SBCSVI interfaces located on this node may fail to forward packets.

Recommended Action    It may help to restart the SBCSVI EA process. If there are any obvious resource problems (e.g. memory exhaustion), these must be fixed first. 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-SBCSVI_EA-3-SSC_SEND_SRV Error while sending message about [chars] to Service Director: [chars]

Explanation    A problem was encountered while trying to send a single message to the Service Director. The Service Director may not be up to date with the state of this services on this node, so the associated SBCSVI interfaces located on this node may fail to forward packets.

Recommended Action    It may help to restart the SBCSVI EA process. If there are any obvious resource problems (e.g. memory exhaustion), these must be fixed first. 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-SBCSVI_EA-3-STATE_CHANGE An error occurred while checking the state for '[chars]': [chars]

Explanation    While the SBCSVI EA process was checking the state for the specified interface pair, an error was encountered. The interface pair in question may be left in an inconsistent state.

Recommended Action    It may help to restart the SBCSVI EA process. If there are any obvious resource problems (e.g. memory exhaustion), these must be fixed first. 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.

SBCSVI_NETIO Messages

Error Message     
 
    
    
   

%SERVICES-SBCSVI_NETIO-3-INIT_DEBUG Failure of debug intialization during [chars]. Error: [chars]

Explanation    A failure occurred during the initialization of debug for the NetIO caps. If this occured during an upgrade operation then it will cause the NetIO process to reload. Otherwise this will cause the capsulation to be unloaded, and an error returned to the user.

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-SBCSVI_NETIO-3-INIT_TRACE Failure initializing tracing ([chars] buffer). Error: [chars]

Explanation    A failure occurred during the initialization of tracing for the NetIO caps. This will cause the capsulation to be unloaded, and an error returned to the user.

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.

SVII_EA_STATS Messages

Error Message     
 
    
    
   

%SERVICES-SVII_EA_STATS-3-CHKPT_GET_FAILURE Failed in checkpoint interaction, resulting in zero stats returned for [chars] (expected length [unsigned int], found [unsigned int]): [chars]

Explanation    An error occured during periodic statistics collection for the interface specified. This means that the statistics (as reported by eg. 'show interface') will be inaccurate for as long as this error is seen.

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.

SVII_EA Messages

Error Message     
 
    
    
   

%SERVICES-SVII_EA-3-EVENT Unrecoverable error in event loop. Error: [chars]

Explanation    An error (other than EINTR) occured in the event loop. The process must exit.

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-SVII_EA-3-FORWARDER_CONNECTION Failed to handle forwarder connection being lost - error: [chars]

Explanation    The forwarder driver has restarted, but this process was unable to handle this as the error was unexpected. It is possible, though not necessarily true, that slow path packet processing for some interfaces owned by this process may be broken.

Recommended Action    Restarting the relevant SVI Manager process will prompt a resync, which should get the SVI Manager process and forwarder driver back into step. 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-SVII_EA-3-INIT Failure during intialization of [chars]. Error: [chars]

Explanation    A failure occurred during the initialization of the Service Virtual Interface infrastructure. This resulted in the restart of the process.

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-SVII_EA-3-SEND_FAILED Failed during [chars] stage of sending a '[chars]' message - Error: [chars]

Explanation    A control message could not be sent from the EA to the MA. See error message for a possible reason. An interface may now be in the wrong up/down state.

Recommended Action    Restarting the relevant SVI Manager process will prompt a resync, which should re-send 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.

Error Message     
 
    
    
   

%SERVICES-SVII_EA-3-SYSMGR Failure communicating readiness to System Manager. Error: [chars]

Explanation    The process was initialized successfully but was unable to inform System Manager of the success.

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.

SVII_LRD_SPA Messages

Error Message     
 
    
    
   

%SERVICES-SVII_LRD_SPA-3-STATE_UPDATE Failed to report SPA [chars] change to SVIA; reason: [chars]; error [chars]

Explanation    A failure occured while processing a SPA state or type change notification. Service interfaces configured on the given SPA may not be appropriately (un)replicated.

Recommended Action    Restarting the process in question should rectify the situation. 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_MGR Messages

Error Message     
 
    
    
   

%SERVICES-SVII_MGR-3-ACTIVATE Failure during activation of [chars]. Error: [chars]

Explanation    A failure occurred during the activation of the Service Virtual Interface infrastructure. Activation occurs when the card transitions to ACTIVE state. This error resulted in the restart of the process.

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%SERVICES-SVII_MGR-3-EVENT Unrecoverable error in event loop. Error: [chars]

Explanation    An error (other than EINTR) occured in the event loop. The process must exit.

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-SVII_MGR-3-EXITING Failure communicating exit to System Manager. Error: [chars]

Explanation    The process was unable to inform System Manager of its graceful shutdown.

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-SVII_MGR-3-IM_STATE_SYNC_ERROR The Service Infrastructure encountered an error when trying to synchronize interface states with the Interface Manager process, while [chars]. Error [chars]

Explanation    The Service Application was unable to report the state of an interface that it owns to the Interface Manager process. The interface state may be inconsistent, and may stop forwarding traffic, or forward traffic when it appears shut down.

Recommended Action    Restarting the process that displayed the message may help, & 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-SVII_MGR-3-INIT Failure during intialization of [chars]. Error: [chars]

Explanation    A failure occurred during the initialization of the Service Virtual Interface infrastructure. This resulted in the restart of the process.

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-SVII_MGR-3-INIT_ENS Failure to initialise ENS - retry scheduled. Error: [chars]

Explanation    A failure occurred during the initialization of ENS library in the process. This probably indicates an underlying more severe problem, and retry will 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-SVII_MGR-3-SEND_FAILED Failed to send a '[chars]' message - Error: [chars]

Explanation    A control message could not be sent from the MA to the EA. See error message for a possible reason. An interface may now be in the wrong up/down state.

Recommended Action    Restarting the relevant SVI Manager process will prompt a resync, which should re-send 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.

Error Message     
 
    
    
   

%SERVICES-SVII_MGR-3-SVIA_INTF_STATE_ERROR The Service Application for [chars] attempted to set an invalid interface state. The interface will be taken down. Invalid state: [chars].

Explanation    The Service Application that manages the interface attempted to put the interface in a state that is not valid. This indicates an internal error in the application. The interface will be put in DOWN state and will cease to forward traffic.

Recommended Action    recommend that restarting the process that displayed the message may help, & 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-SVII_MGR-3-SYSMGR Failure communicating readiness to System Manager. Error: [chars]

Explanation    The process was initialized successfully but was unable to inform System Manager of the success.

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.

VASI_EA Messages

Error Message     
 
    
    
   

%SERVICES-VASI_EA-3-ADJACENCY Error setting up adjacencies for an interface: [chars]

Explanation    An error was encoutered while trying to set up adjacencny information for a VASI interface. The exact error is detailed in the error message. Packets will not be forwarded to the affected interface.

Recommended Action    It may help to restart the affected VASI EA process. If there are any obvious resource problems (e.g. memory exhaustion), these must be addressed first. 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-VASI_EA-3-INITFAIL Failure during initialization. Error: [chars]

Explanation    A failure occurred during the initialization of the VASI EA process on a particular node. The process will be restarted. Until the process starts successfully, any VASI interface pairs located on that node will not come up. (If there is a standby node the interfaces should come up on the standby).

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-VASI_EA-3-INTERNAL [chars]

Explanation    An unexpected internal error has occurred in the VASI EA process. 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-VASI_EA-3-INTERNAL_ERR [chars] : [chars]

Explanation    An unexpected internal error has occurred in the VASI EA process. 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-VASI_EA-3-LINK_FAIL Error while [chars]ing [unsigned int] interfaces: [chars]

Explanation    An error occurred while attempting to join together the two halves of some VASI pairs on the specified node. The pairs will not come up. If there is a standby node configured for the pairs, they may come up on the standby.

Recommended Action    It may help to shut down, then bring up, the VASI interface pairs in question.

Error Message     
 
    
    
   

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

Explanation    Insufficient memory was available to perform an operation. The exact operation is detailed in the error message.

Recommended Action    A low memory condition has occured: Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. You will also have to restart the affected VASI EA process once that is done.

Error Message     
 
    
    
   

%SERVICES-VASI_EA-3-NOT_FOUND Received request for an interface (0x[pointer]) that is not in our database

Explanation    The VASI EA process received a request to process an interface that does not exist in its database. This indicates some sort of internal inconsistency.

Recommended Action    It may help to restart the VASI EA process. If there are any obvious resource problems (e.g. memory exhaustion), these must be fixed first. 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-VASI_EA-3-SSC_SEND Error while sending messages to Service Director: [chars]

Explanation    A problem was encountered while trying to send a batch of messages to the Service Director. The Service Director may not be up to date with the state of services on this node, so VASI interfaces located on this node may fail to forward packets.

Recommended Action    It may help to restart the VASI EA process. If there are any obvious resource problems (e.g. memory exhaustion), these must be fixed first. 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-VASI_EA-3-SSC_SEND_SRV Error while sending message about [chars] to Service Director: [chars]

Explanation    A problem was encountered while trying to send a single message to the Service Director. The Service Director may not be up to date with the state of this services on this node, so the associated VASI interfaces located on this node may fail to forward packets.

Recommended Action    It may help to restart the VASI EA process. If there are any obvious resource problems (e.g. memory exhaustion), these must be fixed first. 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-VASI_EA-3-STATE_CHANGE An error occurred while checking the state for '[chars]': [chars]

Explanation    While the VASI EA process was checking the state for the specified interface pair, an error was encountered. The interface pair in question may be left in an inconsistent state.

Recommended Action    It may help to restart the VASI EA process. If there are any obvious resource problems (e.g. memory exhaustion), these must be fixed first. 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-VASI_EA-3-SVI_HW_UPD_FAIL Error updating service infrastructure with new hardware state: [chars]

Explanation    An error was encountered whilst updating the hardware state of one or more VASI interfaces. The exact error is detailed in the error message. The interfaces affected may no longer be able to forward traffic.

Recommended Action    It may help to restart the affected VASI EA process. If there are any obvious resource problems (e.g. memory exhaustion), these must be addressed first. 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.

VASI_MA Messages

Error Message     
 
    
    
   

%SERVICES-VASI_MA-3-INIT Failed to initialise VASI interface owner process. Stage: [chars], error: [chars]

Explanation    The VASI Manager failed to startup correctly. Though it will get automatically restarted, the error is unlikely to be recoverable.

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%SERVICES-VASI_MA-3-INTF_CREATE_FAIL Failed to cleanup after interface creation failed. Error: [chars]

Explanation    The VASI Manager failed to completely clean up interface state after an interface creation failed. This will have left the system in an inconsistent state. The most likely reason for this error is memory exhaustion.

Recommended Action    Look for ways to free up memory and restart the vasimgr process.

VASI_NETIO Messages

Error Message     
 
    
    
   

%SERVICES-VASI_NETIO-3-DROPPED_PACKETS Packets have been dropped in the VASI base capsulation, but no error counts could be updated ([chars]).

Explanation    An error has occured during packet handling in the VASI base capsulation, and no error counters can be updated. If errors are seen for an extended period then it can be assumed that no packets can be forwarded through VASI interfaces. This is likely to be a symptom of a problem in the Packet Forwarding Infrastructure - earlier error messages might indicate the root cause of the problem.

Recommended Action    If the errors stop after a couple of minutes while traffic is still flowing through the VASI interfaces then it can be assumed that the problem has resolved itself. If the problem continues, then unconfiguring and reconfiguring the VASI interfaces could fix the issue.

Error Message     
 
    
    
   

%SERVICES-VASI_NETIO-3-INIT_DEBUG Failure of debug intialization during [chars]. Error: [chars]

Explanation    A failure occurred during the initialization of debug for the NetIO caps. If this occured during an upgrade operation then it will cause the NetIO process to reload. Otherwise this will cause the capsulation to be unloaded, and an error returned to the user.

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-VASI_NETIO-3-INIT_TRACE Failure initializing tracing ([chars] buffer). Error: [chars]

Explanation    A failure occurred during the initialization of tracing for the NetIO caps. This will cause the capsulation to be unloaded, and an error returned to the user.

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.