Table Of Contents
Service Messages
SBCSVI_EA Messages
SBCSVI_NETIO Messages
SD_COMMON Messages
SD Messages
SVII_EA Messages
SVII_MGR Messages
Service Messages
This section contains all service related System Error Messages. The following facility codes are represented in this module:
•
SBCSVI_EA Messages
•
SBCSVI_NETIO Messages
•
SD_COMMON Messages
•
SD Messages
•
SVII_EA Messages
•
SVII_MGR Messages
SBCSVI_EA Messages
Error Message
%SERVICE-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
%SERVICE-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
%SERVICE-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
%SERVICE-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
%SERVICE-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
%SERVICE-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
%SERVICE-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
%SERVICE-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
%SERVICE-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
%SERVICE-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.
SD_COMMON Messages
Error Message
%SERVICE-SD_COMMON-3-SEND_FAILED
Failed to send a '[chars]' message: '[chars]'
Explanation A required control message could not sent. The reason for the failure is detailed in the
message.
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
%SERVICE-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
%SERVICE-SD-3-BATCH_DECODE_ERROR
Message decode error, message type: [chars],
message number: [dec], error: [chars]
Explanation The Service Director received a batch containing a malformed message. The contents
of the message are lost, and hence the subsequent control changes will not occur.
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. In the short-term, restart the 'service_director' process to force a resync of all
control data.
Error Message
%SERVICE-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
%SERVICE-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
%SERVICE-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.
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
%SERVICE-SD-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.
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.
Error Message
%SERVICE-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.
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
%SERVICE-SD-3-UPDATE_FAILED
Service State update to state [unsigned int] for
service ([unsigned int], [chars]) failed: [chars]
Explanation An attempted service state transition failed. This transition will not be retried.
Recommended Action If the service in question is no longer in an appropriate state, restart the
'service_director' process. Service state can be gleaned from the output of 'show services
redundancy'. 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
%SERVICE-SD-4-INVALID_FIND_SERVICE
An invalid find_service 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
%SERVICE-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.
SVII_EA Messages
Error Message
%SERVICE-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
%SERVICE-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
%SERVICE-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_MGR Messages
Error Message
%SERVICE-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
%SERVICE-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
%SERVICE-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
%SERVICE-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
%SERVICE-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
%SERVICE-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.