Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages, Release 3.4 - Packet Infrastructure Messages [Cisco IOS XR Software (End-of-Sale)]

Table Of Contents

Packet Infrastructure Messages

SVII_ADJ_LIB Messages

SVII_ADJ_MGR Messages

Packet Infrastructure Messages

This section contains all Packet Infrastructure related System Error Messages, including ifmgr, tunnels, bundlemgr, pakman, and so forth. The following facility codes are represented in this module:

•SVII_ADJ_LIB Messages

•SVII_ADJ_MGR Messages

SVII_ADJ_LIB Messages
Error Message     
%PKT_INFRA-SVII_ADJ_LIB-3-ADJ_DATA_CORRUPT The SVI Adjacency Manager was provided with corrupt adjacency data for [chars] SSC belonging to service [chars] on location [chars]
Explanation Either the active or standby Service State Controller for the location given in the message provided the Adjacency Manager with corrupt data. This most likely indicates a bug in the Service State Controller logic. No adjacencies will be installed for the named service, so no traffic will be forwarded to or from it.
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     
%PKT_INFRA-SVII_ADJ_LIB-3-FOLLOW_STANDBY_MISMATCH The SVI Adjacency Manager was provided with conflicting settings for installing adjacencies for interface [hex]
Explanation Conflicting 'follow standby' instructions were supplied to the Adjacency Manager for an interface. 'Follow standby' is specified for an interface by a Service State Controller if it believes that traffic should be directed towards the standby, rather than active, service instance. This message indicates that the active and standby Service State Controllers gave conflicting information about where traffic to be directed to. This indicates an inconsistency between the system state as viewed by the Service State Controllers that are responsible for the service to which the interface belongs. Restarting those processes may help, after allowing any other problems that could lead to inconsistencies being resolved. No adjacencies will be installed for the interface, and all traffic to it will be dropped.
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     
%PKT_INFRA-SVII_ADJ_LIB-3-INIT_FAILED Initialization failed, module: [chars], operation: [chars], error: [chars]
Explanation The SVI Adjacency Manager Library's initialization has failed. The process will exit and automatically 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     
%PKT_INFRA-SVII_ADJ_LIB-3-SERVICE_FAILED An error occurred while setting up adjacencies for service '[chars]': [chars]
Explanation The SVII Adjacency Manager encountered an error while preparing to set up adjacencies for the specified service. It is likely that packets will not be forwarded to interfaces for that service. This may be caused by a lack of resources or other system problems. Restarting the 'svi_adj_mgr' process on the affected node (after any other problems have been cleared up) will restore adjacencies for the affected service.
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     
%PKT_INFRA-SVII_ADJ_LIB-4-INTF_DB_INCONSISTENT An inconsistency has been found in the interface database (interface handle [hex])
Explanation An inconsistency has been found in the adjacency manager interface database. The adjacency manager will automatically recover from this; nevertheless it may indicate a software 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     
%PKT_INFRA-SVII_ADJ_LIB-4-REFRESH_FAILED An error occurred while requesting adjacency refresh for service '[chars]': [chars]
Explanation The SVII Adjacency Manager encountered an error while resynchronising its adjacencies. The adjacencies for the specified service may not be correctly set up on the specified card, meaning that traffic for that service arriving at that card may not be forwarded correctly.
Recommended Action Restarting the 'svi_adj_mgr' process on the affected node (after any other problems - such as lack of memory - have been cleared up) will restore adjacencies for the affected service. 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     
%PKT_INFRA-SVII_ADJ_LIB-4-RESTART_FAILED An error occurred while trying to restart cleanly: [chars]
Explanation The SVII Adjacency Manager encountered an error while preparing to restart itself. It will restart itself anyway, but there may be other errors.
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     
%PKT_INFRA-SVII_ADJ_LIB-4-SDIR_INVALID The Service Director library passed invalid parameters to the SVII Adjacency Manager process.
Explanation The Service Director process/library sent an invalid message to the SVII Adjacency Manager. This indicates a problem with the Service Director. It is likely that packets will not be correctly forwarded to some Service Virtual Interfaces.
Recommended Action It may help to restart the SVII Adjacency Manager and/or the Service Director processes. 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     
%PKT_INFRA-SVII_ADJ_LIB-4-SRV_CLEANUP_FAILED The SVI Adjacency Manager 'publish' library encountered an error when trying to clean up after a service unregistered. Error [chars]
Explanation A Service owner tried to revoke a request for adjacencies to be managed by the SVI Adjacency Manager. It is likely that the originally published request has not been cleaned up correctly. This should not have any adverse effects, other than the use of some additional resouces, but probably indicates some kind of programming error.
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_ADJ_MGR Messages
Error Message     
%PKT_INFRA-SVII_ADJ_MGR-3-ADJ_FAILED An error occurred while trying to program an adjacency: [chars] (interface handle=[hex])
Explanation The SVII Adjacency Manager encountered an error while programming an adjacency. Packets may not be forwarded to the affected service interface. The name of the interface can be retrieved with 'show im chains ifhandle 0xabc', where '0xabc' is the interface handle shown in the message.
Recommended Action This error should only arise due to resource constraints (eg memory). Determine which resources are short, and make more available; then restart the 'svi_adj_mgr' process on the affected node.
Error Message     
%PKT_INFRA-SVII_ADJ_MGR-3-ECM_ERROR_FAILED An error occurred while trying to recover from a previous failure: [chars]
Explanation The SVII Adjacency Manager encountered an error while calling AIB. Normally, it would recover from this error. However, a secondary failure has occurred while invoking the recovery mechanism. After this error, packets may not be forwarded correctly for some service virtual interfaces.
Recommended Action The system can be recovered by restarting the 'svi_adj_mgr' 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.
Error Message     
%PKT_INFRA-SVII_ADJ_MGR-3-INIT_FAILED Initialization failed, module: [chars], operation: [chars], error: [chars]
Explanation The SVI Adjacency Manager's initialization has failed. The process will exit and automatically 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     
%PKT_INFRA-SVII_ADJ_MGR-3-LOOP_FAILED Event Loop failed, error: [chars]
Explanation The SVII Adjacency Manager encountered an error while waiting for an event. This should not ordinarily happen, but may indicate a temporary glitch that will automatically recover. If it occurs very frequently it may be necessary to restart the SVII Adjacency Manager 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     
%PKT_INFRA-SVII_ADJ_MGR-3-RECEIVE_MESSAGE An error occurred whilst processing a '[chars]' message from a client, during operation [chars]: [chars]
Explanation The process encountered an error while trying to handle a message from a Service on a line card. If this happens frequently, then restarting the process that caused the error may fix the problem. It may indicate that the card is low on memory.
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     
%PKT_INFRA-SVII_ADJ_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.
Error Message     
%PKT_INFRA-SVII_ADJ_MGR-4-RESTART A failure occured while re-syncing state with AIB after a restart: [chars]
Explanation After a restart, the adjacency manager attempts to re-sync its state with AIB. A failure occurred during this process. This could result in adjacencies being erroneously deleted in AIB, and hence forwarding could be interrupted.
Recommended Action Wait five minutes, then restart the adjacency manager again by entering the command: 'process restart svii_adj_mgr location '. 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     
%PKT_INFRA-SVII_ADJ_MGR-6-CERRNO_FAILED Error registration failed ([chars]) - some messages may not be displayed correctly
Explanation The SVI Adjacency Manager encountered an error while registering its error messages. Some error messages may be displayed numerically rather than with full messages. No other problems will be caused by this failure.
Recommended Action No action need be taken.

	Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages, Release 3.4
	Packet Infrastructure Messages
Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages, Release 3.4 Preface Overview Diagnostic Messages Fabric Messages High Availability (HA) Messages Installation Messages Internet Protocol (IP) Messages Layer 1 Messages Layer 2 Messages Media Messages Manageability (MGBL) Messages Operating System (OS) Messages Packet Infrastructure Messages Platform Messages Replicator Messages Routing Messages Security Messages Simple Network Management Protocol (SNMP) Messages System Database Messages Index	Download this chapter Packet Infrastructure Messages Download the complete book Book-level PDF: Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages (PDF - 2 MB) Feedback Table Of Contents Packet Infrastructure Messages SVII_ADJ_LIB Messages SVII_ADJ_MGR Messages Packet Infrastructure Messages This section contains all Packet Infrastructure related System Error Messages, including ifmgr, tunnels, bundlemgr, pakman, and so forth. The following facility codes are represented in this module: •SVII_ADJ_LIB Messages •SVII_ADJ_MGR Messages SVII_ADJ_LIB Messages Error Message %PKT_INFRA-SVII_ADJ_LIB-3-ADJ_DATA_CORRUPT The SVI Adjacency Manager was provided with corrupt adjacency data for [chars] SSC belonging to service [chars] on location [chars] Explanation Either the active or standby Service State Controller for the location given in the message provided the Adjacency Manager with corrupt data. This most likely indicates a bug in the Service State Controller logic. No adjacencies will be installed for the named service, so no traffic will be forwarded to or from it. 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 %PKT_INFRA-SVII_ADJ_LIB-3-FOLLOW_STANDBY_MISMATCH The SVI Adjacency Manager was provided with conflicting settings for installing adjacencies for interface [hex] Explanation Conflicting 'follow standby' instructions were supplied to the Adjacency Manager for an interface. 'Follow standby' is specified for an interface by a Service State Controller if it believes that traffic should be directed towards the standby, rather than active, service instance. This message indicates that the active and standby Service State Controllers gave conflicting information about where traffic to be directed to. This indicates an inconsistency between the system state as viewed by the Service State Controllers that are responsible for the service to which the interface belongs. Restarting those processes may help, after allowing any other problems that could lead to inconsistencies being resolved. No adjacencies will be installed for the interface, and all traffic to it will be dropped. 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 %PKT_INFRA-SVII_ADJ_LIB-3-INIT_FAILED Initialization failed, module: [chars], operation: [chars], error: [chars] Explanation The SVI Adjacency Manager Library's initialization has failed. The process will exit and automatically 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 %PKT_INFRA-SVII_ADJ_LIB-3-SERVICE_FAILED An error occurred while setting up adjacencies for service '[chars]': [chars] Explanation The SVII Adjacency Manager encountered an error while preparing to set up adjacencies for the specified service. It is likely that packets will not be forwarded to interfaces for that service. This may be caused by a lack of resources or other system problems. Restarting the 'svi_adj_mgr' process on the affected node (after any other problems have been cleared up) will restore adjacencies for the affected service. 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 %PKT_INFRA-SVII_ADJ_LIB-4-INTF_DB_INCONSISTENT An inconsistency has been found in the interface database (interface handle [hex]) Explanation An inconsistency has been found in the adjacency manager interface database. The adjacency manager will automatically recover from this; nevertheless it may indicate a software 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 %PKT_INFRA-SVII_ADJ_LIB-4-REFRESH_FAILED An error occurred while requesting adjacency refresh for service '[chars]': [chars] Explanation The SVII Adjacency Manager encountered an error while resynchronising its adjacencies. The adjacencies for the specified service may not be correctly set up on the specified card, meaning that traffic for that service arriving at that card may not be forwarded correctly. Recommended Action Restarting the 'svi_adj_mgr' process on the affected node (after any other problems - such as lack of memory - have been cleared up) will restore adjacencies for the affected service. 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 %PKT_INFRA-SVII_ADJ_LIB-4-RESTART_FAILED An error occurred while trying to restart cleanly: [chars] Explanation The SVII Adjacency Manager encountered an error while preparing to restart itself. It will restart itself anyway, but there may be other errors. 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 %PKT_INFRA-SVII_ADJ_LIB-4-SDIR_INVALID The Service Director library passed invalid parameters to the SVII Adjacency Manager process. Explanation The Service Director process/library sent an invalid message to the SVII Adjacency Manager. This indicates a problem with the Service Director. It is likely that packets will not be correctly forwarded to some Service Virtual Interfaces. Recommended Action It may help to restart the SVII Adjacency Manager and/or the Service Director processes. 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 %PKT_INFRA-SVII_ADJ_LIB-4-SRV_CLEANUP_FAILED The SVI Adjacency Manager 'publish' library encountered an error when trying to clean up after a service unregistered. Error [chars] Explanation A Service owner tried to revoke a request for adjacencies to be managed by the SVI Adjacency Manager. It is likely that the originally published request has not been cleaned up correctly. This should not have any adverse effects, other than the use of some additional resouces, but probably indicates some kind of programming error. 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_ADJ_MGR Messages Error Message %PKT_INFRA-SVII_ADJ_MGR-3-ADJ_FAILED An error occurred while trying to program an adjacency: [chars] (interface handle=[hex]) Explanation The SVII Adjacency Manager encountered an error while programming an adjacency. Packets may not be forwarded to the affected service interface. The name of the interface can be retrieved with 'show im chains ifhandle 0xabc', where '0xabc' is the interface handle shown in the message. Recommended Action This error should only arise due to resource constraints (eg memory). Determine which resources are short, and make more available; then restart the 'svi_adj_mgr' process on the affected node. Error Message %PKT_INFRA-SVII_ADJ_MGR-3-ECM_ERROR_FAILED An error occurred while trying to recover from a previous failure: [chars] Explanation The SVII Adjacency Manager encountered an error while calling AIB. Normally, it would recover from this error. However, a secondary failure has occurred while invoking the recovery mechanism. After this error, packets may not be forwarded correctly for some service virtual interfaces. Recommended Action The system can be recovered by restarting the 'svi_adj_mgr' 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. Error Message %PKT_INFRA-SVII_ADJ_MGR-3-INIT_FAILED Initialization failed, module: [chars], operation: [chars], error: [chars] Explanation The SVI Adjacency Manager's initialization has failed. The process will exit and automatically 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 %PKT_INFRA-SVII_ADJ_MGR-3-LOOP_FAILED Event Loop failed, error: [chars] Explanation The SVII Adjacency Manager encountered an error while waiting for an event. This should not ordinarily happen, but may indicate a temporary glitch that will automatically recover. If it occurs very frequently it may be necessary to restart the SVII Adjacency Manager 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 %PKT_INFRA-SVII_ADJ_MGR-3-RECEIVE_MESSAGE An error occurred whilst processing a '[chars]' message from a client, during operation [chars]: [chars] Explanation The process encountered an error while trying to handle a message from a Service on a line card. If this happens frequently, then restarting the process that caused the error may fix the problem. It may indicate that the card is low on memory. 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 %PKT_INFRA-SVII_ADJ_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. Error Message %PKT_INFRA-SVII_ADJ_MGR-4-RESTART A failure occured while re-syncing state with AIB after a restart: [chars] Explanation After a restart, the adjacency manager attempts to re-sync its state with AIB. A failure occurred during this process. This could result in adjacencies being erroneously deleted in AIB, and hence forwarding could be interrupted. Recommended Action Wait five minutes, then restart the adjacency manager again by entering the command: 'process restart svii_adj_mgr location '. 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 %PKT_INFRA-SVII_ADJ_MGR-6-CERRNO_FAILED Error registration failed ([chars]) - some messages may not be displayed correctly Explanation The SVI Adjacency Manager encountered an error while registering its error messages. Some error messages may be displayed numerically rather than with full messages. No other problems will be caused by this failure. Recommended Action No action need be taken.
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks