SWEPA Messages

This section contains software encryption port adapter (SWEPA) and key management messages.

SWEPA-6

Error Message    %SWEPA-6-EPA_EXP_RUNNING: Exp Running .... 

Explanation    The EXP process is running.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SWEPA-6-EPA_EXP_TIMER_EXPIRED: Exp Timer Expired! 

Explanation    The EXP timer has expired.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SWEPA-6-FAILED_TO_ALLOCATE_ENCRYPT_QUE: Failed to allocate the 
encrypt queue. 

Explanation    The encryption queue could not be allocated.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SWEPA-6-FAILED_TO_START_DES_PROCESS: Failed to start DES process 

Explanation    The DES process has failed to start.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SWEPA-6-FAILED_TO_START_EXP_PROCESS: Failed to start EXP process 

Explanation    The EXP process has failed to start.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SWEPA-6-INIT_SW_EPA_IDB: Init swepa idb start ... 

Explanation    The software encryption port adapter information descriptor block (IDB) is being initialized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SWEPA-6-START_DES_PROCESS: DES process start ... 

Explanation    The DES process has started.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SWEPA-6-START_EXP_PROCESS: EXP process start ... 

Explanation    The EXP process has started.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SWITCH Messages

This section contains switch interface messages.

SWITCH-3

Error Message    %SWITCH-1-RF_REGISTRTN_FAILED: unable to register switch driver client 
to RF 

Explanation    The switch driver client could not be registered to the redundancy facility (RF).

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SWITCHOVER Messages

This section contains line card switchover-related messages.

SWITCHOVER-6

Error Message    %SWITCHOVER-6-LC_HA_UNAWARE: Line card (type [hex]) in slot [dec] is 
not confgured HA mode aware 

Explanation    The line card in the specified slot does not support the configured RP redundancy mode. The line card will be reset and reinitialized during RP failover.

Recommended Action    No action is required.

SWITCH_QOS_TB Messages

This section contains trusted boundary messages.

SWITCH_QOS_TB-5

Error Message    %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: [chars] detected on port 
[chars], port trust enabled. 

Explanation    The trusted boundary facility has detected a device that matches the trusted device setting for the port, and the port trust state has been modified.

Recommended Action    No action is required.

Error Message    %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: [chars] no longer detected on port 
[chars], port set to untrusted. 

Explanation    The trusted boundary facility has lost contact with a trusted device, and has set the port trust state to untrusted.

Recommended Action    No action is required.

SWITCH_SPAN_ISSU Messages

This section contains span switch in-service software upgrade (ISSU) messages.

SWITCH_SPAN_ISSU-3

Error Message    %SWITCH_SPAN_ISSU-3-BUFFER: span switch ISSU client failed to get 
buffer for message, error %d 

Explanation    The SPAN switch ISSU client was unable to get a buffer for building a negotiation message. As a result, it cannot send the negotiation message to the standby unit and the standby unit cannot be brought up.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.

Error Message    %SWITCH_SPAN_ISSU-3-CAPABILITY: span switch ISSU client %s 

Explanation    The SPAN switch ISSU client detected an error during capability negotiation. As a result, there is a mismatch in the client capability between the active and standby unit.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message    %SWITCH_SPAN_ISSU-3-INIT: span switch ISSU client initialization 
failed at %s, error %s 

Explanation    The SPAN switch ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SWITCH_SPAN_ISSU-3-MSG_NOT_OK: span switch ISSU client message %d is 
not compatible 

Explanation    The SPAN switch ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message    %SWITCH_SPAN_ISSU-3-MSG_SIZE: span switch ISSU client failed to get 
the message size for message %d 

Explanation    The SPAN switch ISSU client was unable to calculate the message size for the message specified. The client will be unable to send the message to the standby unit.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message    %SWITCH_SPAN_ISSU-3-POLICY: span switch ISSU client message type %d is 
%s 

Explanation    The SPAN switch ISSU client received a message type that it does not support. A policy is applied to make the session compatible.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu session commands and your pertinent troubleshooting logs.

Error Message    %SWITCH_SPAN_ISSU-3-SEND_FAILED: span switch ISSU client failed to 
send a negotiation message, error %d 

Explanation    The SPAN switch ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.

Error Message    %SWITCH_SPAN_ISSU-3-SESSION: span switch ISSU client %s 

Explanation    The SPAN switch ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message    %SWITCH_SPAN_ISSU-3-TRANSFORM: span switch ISSU client %s transform 
failed, error %s 

Explanation    The SPAN switch ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the SPAN switch state will not be identical with the active unit.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

SW_MGR Messages

This section contains segment switch manager messages.

SW_MGR-3

Error Message    %SW_MGR-3-CM_ERROR: Connection Manager Error - [chars]. 

Explanation    An error has occurred in the segment switch connection manager.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SW_MGR-3-CM_ERROR_CLASS: Connection Manager Error: Class [chars]: - 
[chars]. 

Explanation    An error has occurred in the connection manager.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SW_MGR-3-CM_ERROR_FEATURE: Connection Manager Feature Error: (%s) - 
%s. 

Explanation    A segment switch connection manager feature class error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SW_MGR-3-CM_ERROR_FEATURE_CLASS: Connection Manager Feature Error: 
Class %s: (%s) - %s. 

Explanation    A segment switch connection manager feature error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SW_MGR-3-FHM_ERROR: SSM Feature Handler Manager Error - %s. 

Explanation    A feature handler manager error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SW_MGR-3-INVALID_HANDLE: Segment Manager Error - Invalid [chars] 
handle - [dec]. 

Explanation    The connection manager encountered an invalid handle.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SW_MGR-3-INVALID_SEGMENT: Segment Switch Manager Error - Invalid 
segment - [chars]. 

Explanation    The segment switch manager encountered an invalid segment.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SW_MGR-3-SM_ERROR: Segment Manager Error - [chars]. 

Explanation    An error has occurred in the segment manager.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SW_MGR-3-SSM_SEG_ISSU: SSM Segment ISSU: [chars] not supported. 

Explanation    ISSU of this SSM Segment is not supported.

Recommended Action    Not Available.

SW_VLAN Messages

This section contains Virtual LAN (VLAN) manager messages.

SW_VLAN-4

Error Message    %SW_VLAN-4-VLAN_ADD_FAIL: Failed to add VLAN [dec] to vlan database: 
[chars] 

Explanation    The specified VLAN could not be added to the VLAN database. The platform may not allow the addition or there may be insufficient memory to expand the VLAN database.

Recommended Action    Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SW_VLAN-4-VLAN_CREATE_FAIL: Failed to create VLANs [chars]: [chars] 

Explanation    The specified VLANs could not be created. The VLAN manager called a VLAN database routine to create one or more VLANs, but the port manager failed the VLAN creation requests. A possible cause of this error is that the VLANs already exist in the port manager as internal VLANs.

Recommended Action    Check the internal VLAN usage by entering the show vlan internal usage command. Unconfigure the feature that occupies the internal VLAN and retry the VLAN creation operation. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SW_VLAN-4-VLANMGR_INVALID_DATABASE_DATA: VLAN MANAGER received bad 
data of type %s: value %d from function %s 

Explanation    The VLAN manager received invalid data from a VLAN configuration database process.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SW_VLAN-4-VTP_DB_INVALID_VLANID: Invalid VLAN ID [dec] found in VTP 
database download 

Explanation    An invalid VLAN ID was detected in the VTP database during the download of the VTP configuration file. This condition indicates that the VTP configuration file in NVRAM is corrupted.

Recommended Action    Save a copy of the vlan.dat file that includes the invalid VLAN ID to help investigate the condition. Copy the message exactly as it appears on the console or in the system log. Enter the show vtp status and the show vlan commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SW_VLAN-4-VTP_DB_SIZE_CHECK_FAILED: The %s VTP database of length %d 
cannot be supported by the system 

Explanation    The VLAN trunking protocol (VTP) database size is larger than the system can support.

Recommended Action    Reduce the database size by decreasing the configuration parameters. For example, reduce the size of vlan-names.

Error Message    %SW_VLAN-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to [chars]. 

Explanation    The VTP domain name was changed through configuration to the name
specified in the message. A management domain is the naming scope of a VLAN name. Each VLAN has a name that is unique within the management domain.

Recommended Action    This is an informational message only. No action is required.

Error Message    %SW_VLAN-4-VTP_PRIMARY_SERVER_CHG: %e has become the primary server 
for the %s VTP feature 

Explanation    The primary server status has changed and the indicated device has become the primary server for the indicated VTP feature.

Recommended Action    No action is required.

Error Message    %SW_VLAN-4-VTP_SEM_BUSY: VTP semaphore is unavailable for function 
[chars]. Semaphore locked by [chars] 

Explanation    The VTP database is currently locked by another task and is not available.

Recommended Action    Retry the operation later. If this condition recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SW_VLAN-6

Error Message    %SW_VLAN-6-OLD_CONFIG_FILE_READ: Old version [dec] VLAN configuration 
file detected and read OK. Version [dec] files will be written in the future. 

Explanation    This message indicates that the VLAN software detected an old version of the VLAN configuration file format. The software was able to interpret the file with no problems but will create files using the new format in the future. The first [dec] is the old version number, and the second [dec] is the new version number.

Recommended Action    No action is required.

Error Message    %SW_VLAN-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to [chars]. 

Explanation    The VTP domain name was changed through configuration to the name specified in the message. A management domain is the naming scope of a VLAN name. Each VLAN has a name that is unique within the management domain.

Recommended Action    No action is required.

Error Message    %SW_VLAN-6-VTP_MODE_CHANGE: VLAN manager changing device mode from 
[chars] to [chars]. 

Explanation    Some switch devices must automatically change VTP device modes upon receipt of a VLAN configuration database containing more than a set number of VLANs, depending on the device. This message indicates that such a spontaneous conversion has occurred, what the previous mode was, and what the current mode is. [chars] is the VTP device mode. In VTP server mode, the VLAN manager must record each change of VTP configuration and each change of device configuration relating to VTP (such as mode changes, device domain name changes, and password changes) to non-volatile storage using IFS system calls. If a system call fails, the device must spontaneously convert to the VTP client mode. Call failures are usually the result of a hardware failure of the non-volatile storage system, which may require replacement. Other possible causes include software bugs or, in the case of TFTP storage, a transient network or TFTP server failure.

Recommended Action    No action is required.

Error Message    %SW_VLAN-6-VTP_PRUNING_CHANGE: VTP Operational Pruning [chars]. 

Explanation    VTP operational pruning has been enabled or disabled as shown in [chars], due to either an administrative pruning change, a VTP mode change, or VTP configuration propagation. To view the reason for the change, enter the show vtp status command.

Recommended Action    No action is required.

SW_SP-VLAN

Error Message    %SW_VLAN-SP-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to %s.

Explanation    The VTP domain name was changed through configuration to the name specified in the message. A management domain is the naming scope of a VLAN name. Each VLAN has a name that is unique within the management domain.

Recommended Action    No action is required.

SW_VLAN_ISSU Messages

This section contains switch VLAN in-service software upgrade (ISSU) messages.

SW_VLAN_ISSU-2

Error Message    %SW_VLAN_ISSU-2-GET_BUFFER: Switch Vlan ISSU client failed to get 
buffer for message. Error: %d (%s) 

Explanation    The switch VLAN ISSU client was unable to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.

Error Message    %SW_VLAN_ISSU-2-INIT: Switch Vlan ISSU client initialization failed to 
%s. Error: %d (%s) 

Explanation    The switch VLAN ISSU client could not be initialized. This initialization failure must be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SW_VLAN_ISSU-2-SEND_NEGO_FAILED: Switch Vlan ISSU client failed to 
send negotiation message. Error: %d (%s) 

Explanation    The switch VLAN ISSU client was unable to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.

Error Message    %SW_VLAN_ISSU-2-SESSION_NEGO: Switch Vlan ISSU client encountered 
unexpected client nego_done. Error: %d (%s) 

Explanation    An ISSU-compliant client transitions through a series of internal states. The switch VLAN ISSU client encountered a client negotiation done state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message    %SW_VLAN_ISSU-2-SESSION_REGISTRY: Switch Vlan ISSU client failed to 
register session information. Error: %d (%s) 

Explanation    The switch VLAN ISSU client was unable to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

SW_VLAN_ISSU-3

Error Message    %SW_VLAN_ISSU-3-CAP_INVALID_SIZE: Switch Vlan ISSU client capability 
list is empty. 

Explanation    The switch VLAN ISSU client capability exchange list is empty, which is an invalid condition.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu capability entires commands and your pertinent troubleshooting logs.

Error Message    %SW_VLAN_ISSU-3-CAP_NOT_COMPATIBLE: Switch Vlan ISSU client capability 
exchange result incompatible. 

Explanation    Based on the results of the capability exchange, the switch VLAN ISSU client is not compatible with the peer.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message    %SW_VLAN_ISSU-3-INVALID_SESSION: Switch Vlan ISSU client does not have 
a valid registered session. 

Explanation    The switch VLAN ISSU client does not have a valid registered session.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message    %SW_VLAN_ISSU-3-MSG_NOT_COMPATIBLE_WITH_PEER: 'Message Type %d' is not 
supported by Switch Vlan ISSU client at peer 

Explanation    The switch VLAN ISSU client at the peer supervisor is not compatible for this message type. The switch VLAN client will be marked as incompatible with the peer.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message    %SW_VLAN_ISSU-3-MSG_NOT_OK: Switch Vlan ISSU client 'Message Type %d' 
is not compatible 

Explanation    The switch VLAN ISSU client received an incompatible message from the peer device. The message cannot be processed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message    %SW_VLAN_ISSU-3-MSG_SIZE: Switch Vlan ISSU client failed to get the 
MTU for Message Type %d. Error: %d (%s) 

Explanation    The switch VLAN ISSU client was unable to calculate the MTU for the specified message. As a result, the client is unable to send the message to the standby device.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message    %SW_VLAN_ISSU-3-SESSION_UNREGISTRY: Switch Vlan ISSU client failed to 
unregister session information. Error: %d (%s) 

Explanation    The switch VLAN ISSU client was unable to unregister session information.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message    %SW_VLAN_ISSU-3-TRANSFORM_FAIL: Switch Vlan ISSU client %s transform 
failed for 'Message Type %d'. Error: %d (%s) 

Explanation    The switch VLAN ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the switch VLAN state between the active device and the standby device is not identical.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

SW_VLAN_RF Messages

This section contains switch VLAN redundancy facility (RF) messages.

SW_VLAN_RF-3

Error Message    %SW_VLAN_RF-3-CREATE_PROCESS: Switch Vlan RF client failed to create 
%s process 

Explanation    The switch VLAN redundancy facility (RF) client could not create a process. As a result, bulk synchronization will fail.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SYS Messages

This section contains operating system messages.

SYS-2

Error Message    %SYS-2-BAD_BM_ARG: Invalid BM index boolean used as argument ([dec]) 

Explanation    An illegal boolean manager index argument was referenced.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYS-2-CHUNKPARTIAL: Attempted to destroy partially full chunk, chunk 
[hex]. 

Explanation    A software error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYS-2-FAILEDUPDATE: Failed to update Process id: %d in %s 

Explanation    An internal software error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYS-2-IMMORTAL: Attempt to shut down management process [dec] 
([chars]). 

Explanation    An attempt was made to shut down the specified management process.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, the stack trace, and your pertinent troubleshooting logs.

Error Message    %SYS-2-INPUT_GETBUF: Bad getbuffer, bytes= [dec], for interface= 
[chars] 

Explanation    The software requested a buffer that is larger than the largest configured buffer size, or it requested a negative-sized buffer.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYS-2-NOPID: Process MIB is not aware of Process id: %d 

Explanation    An internal software error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYS-2-NV_BAD_PTR: Bad NVRAM pointer. NV Header values are, nv: %p 
.textbase: %p .textsize: %d .magic: 0x%X .checksum: 0x%X .system_version: %d 
.textptr: %p v1_ptr: %p .priv: %p 

Explanation    A pointer corruption in NVRAM caused a failure in accessing the NVRAM.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYS-2-SYSMEMINFO: System Memory: [int]K total, [int]K used, [int]K 
free 

Explanation    This is an auxiliary message to several memory-related messages. It provides only additional system memory information usage.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SYS-3

Error Message    %SYS-3-BADRESID: Clock hardware returned bad residual [dec]. 

Explanation    A software error occurred.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %SYS-3-CHUNK_NO_EXMEM: No handler to [chars] external memory. 

Explanation    An attempt was made to allocate or free a chunk of external memory, but no handler for managing external memory was registered.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYS-3-MEMSEMFAIL: Mempool semaphore creation failed for [chars] 

Explanation    Semaphore creation for the specified memory pool has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYS-3-PREEMPTSUSP: Suspending a preemptive process [chars] 

Explanation    A preemptive process attempted a suspend, which is not allowed because they are expected to finish their work as quickly as possible and go back to idle queue.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYS-3-PROCSEMFAIL: Process semaphore creation for preemptive 
processes failed. 

Explanation    Creation of a process function semaphore to protect the critical section of the process create routine has failed. The semaphore creation can fail if there is not enough chunk memory to create the event structure.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SYS-4

Error Message    %SYS-4-CPURESRISING: %s%s is seeing %s cpu util %u%% at %s level more 
than the configured %s limit %u %% 

Explanation    The system is experiencing high CPU usage, possibly from a process that is monopolizing the CPU. This condition demands immediate attention because packets or calls may be dropped. This message should be matched with a corresponding CPURESFALLING or CPURESUNAPPLY notification.

Recommended Action    No action is required.

SYS-5

Error Message    %SYS-5-CONFIG: Configured from [chars] 

Explanation    The router's configuration was changed.

Recommended Action    This is a notification message only. No action is required.

Error Message    %SYS-5-FIFOBUS_ERR: Flow-control threshold on module [dec] has 
exceeded the default value. Threshold will be set to lower value 

Explanation    The FIFO threshold values are monitored for flow-control. When the threshold value exceeds the default, the value is set to a new (lower) value

Recommended Action    This is an informational message only. No action is required.

Error Message    %SYS-5-PRIV_I: Privilege level set to %d by%s%s 

Explanation    The privileged mode is enabled or the privilege level is changed. As a result, the associated privilege level, user ID, and line information will be logged.

Recommended Action    No action is required. To disable logging of these events, enter the no logging userinfo command from the global configuration mode.

SYS-6

Error Message    %SYS-6-CLOCKUPDATE: System clock has been updated from [chars] to 
[chars], configured from [chars] by [chars]. 

Explanation    The system clock has been modified.

Recommended Action    This is an informational message only. No action is required.

Error Message    %SYS-6-CPURESFALLING: %s%s is no longer seeing %s high cpu at %s level 
for the configured %s limit %u%%, current value %u%% 

Explanation    The CPU usage has returned to normal after exceeding a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled.

Recommended Action    No action is required.

Error Message    %SYS-6-CPURESUNAPPLY: %s%s is no longer monitoring %s cpu at %s level 
for the configured %s limit. 

Explanation    CPU usage is no longer being monitored for the configured threshold level indicated in the message. The corresponding policy is revoked.

Recommended Action    No action is required.

Error Message    %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host %s%s%s%s 

Explanation    System logging to the indicated server or host (VRF) has started or stopped.

Recommended Action    No action is required.

Error Message    %SYS-6-NOBRIDGE: Bridging software not present 

Explanation    Your system is not configured to be a bridge.

Recommended Action    Configure the bridging software.

Error Message    %SYS-6-READ_BOOTFILE_SKIP: boot system [chars] command is skipped

Explanation    A configured boot system command is skipped. Either the system experienced a crash while loading this image in the last attempt or the filename is not properly specified. Subsequent boot system commands will be tried

Recommended Action    Replace the failed boot system image with a good one. There could be various reasons that this specified image failed, for example the image might be with a bad checksum.

SYS-SP

Error Message    %SYS-SP-3-LOGGER_FLUSHING: System pausing to ensure console debugging 
output.

Explanation    Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen, the rest of the system is paused until the console output catches up. This can break time-critical behavior, such as maintaining an ISDN link.

Recommended Action    Consider using conditional debugging, turning off console logging, or using the o logging console guaranteed command, or turning off link-state messages for some interfaces.

Error Message    %SYS-SP-3-LOGGER_FLUSHED: System was paused for %TE to ensure console 
debugging output.

Explanation    Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen, the rest of the system was paused until the console output catches up. This can break time-critical behavior, such as maintaining an ISDN link.

Recommended Action    Consider using conditional debugging, turning off console logging, or using the o logging console guaranteed command, or turning off link-state messages for some interfaces.

SYSLOGD Messages

This section contains system logging (SYSLOG) messages.

SYSLOGD-3

Error Message    %SYSLOGD-3-DROPPED_MESSAGES: A total of [int] messages have been 
dropped by the syslog daemon, due to [chars]

Explanation    The syslogd process has dropped received messages. The syslogd process may be receiving too many messages to process before the buffer fills, or it may have received a message for which there was insufficient memory available. In either case, there may be a bug in the sending process.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SYSMGR Messages

This section contains system manager messages.

SYSMGR-3

Error Message    %SYSMGR-3-ABNORMTERM: [chars]:[dec] (jid [dec]) abnormally terminated, 
[chars] 

Explanation    A process was abnormally terminated.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYSMGR-3-ERROR: [chars]:[dec] (jid [dec]) [chars] ([chars]) 

Explanation    The system manager server has encountered an error condition.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SYSMGR-6

Error Message    %SYSMGR-6-ERROR_EOK: [chars]:[dec] (jid [dec]) [chars] 

Explanation    The system manager server has encountered an error condition.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYSMGR-6-RESTART: Restarting process [chars] by [chars] 

Explanation    A process was restarted through the CLI.

Recommended Action    This is an informational message only. No action is required.

SYSMGR_PLATFORM Messages

This section contains Cisco Catalyst 6000 system manager process messages.

SYSMGR_PLATFORM-5

Error Message    %SYSMGR_PLATFORM-5-WAIT_RP: Waiting RP to complete crashinfo and core 
file collection 

Explanation    Sysmgr.proc process is waiting for the RP to signal the end of crashinfo or core file collection.

Recommended Action    This is an informational message only. No action is required.

SYSTEM_BUS_ASIC Messages

This section contains System Bus Translator ASIC messages.

SYSTEM_BUS_ASIC-3

Error Message    %SYSTEM_BUS_ASIC-3-INTR_FATAL: SYSTEM BUS ASIC [dec]: recoverable 
interrupt [chars] 

Explanation    The System Bus Translator ASIC detected an unexpected interrupt condition. This message indicates a hardware failure or malfunction. The system will reload to fix the problem.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYSTEM_BUS_ASIC-3-INTR_RECOVERY: SYSTEM BUS ASIC [dec]: recoverable 
interrupt [chars] 

Explanation    The System Bus Translator ASIC detected an unexpected interrupt condition.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYSTEM_BUS_ASIC-3-INTR_RESET: SYSTEM BUS ASIC [dec]: was reset 

Explanation    The System Bus Translator ASIC was reset as part of the system recovery sequence.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYSTEM_BUS_ASIC-3-INTR_STATS_RECOVERY: SYSTEM BUS ASIC [dec]: 
Recoverable Interrupt warning [chars] 

Explanation    The System Bus Translator ASIC detected an unexpected condition in the statistics collection module.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYSTEM_BUS_ASIC-3-INTR_WARN: SYSTEM BUS ASIC [dec]: Non-fatal 
Interrupt warning [chars] 

Explanation    The System Bus Translator ASIC detected an unexpected nonfatal condition.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYSTEM_BUS_ASIC-3-INTR_WARN_TYPE2: SYSTEM BUS ASIC [dec]: Non-fatal 
interrupt Warning [chars] error code [dec] 

Explanation    The System Bus Translator ASIC detected an unexpected nonfatal condition.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYSTEM_BUS_ASIC-3-KUMA_INTR_THROTTLED: SYSTEM BUS ASIC %d: Kuma 
interrupts throttled 

Explanation    The system bus translator ASIC detected too many interrupts. To avoid performance degradation, the system has temporarily masked interrupts.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYSTEM_BUS_ASIC-3-KUMA_INTR_UNTHROTTLED: SYSTEM BUS ASIC %d: Kuma 
interrupts unthrottled 

Explanation    The system has unmasked the interrupts that were masked temporarily.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

SYSTEM_CONTROLLER Messages

This section contains system controller messages.

SYSTEM_CONTROLLER-3

Error Message    %SYSTEM_CONTROLLER-3-COR_MEM_ERR: Correctable DRAM memory error. Count 
[dec], log [hex]

Explanation    A transient DRAM memory error was detected and corrected.

Recommended Action    If the error message appears infrequently, no action is required. If the message recurs, reseat the SDRAM SIMM on the supervisor engine. If errors persist, replace the SIMM. If the errors continue after the SIMM is replaced, the supervisor engine may need to be replaced.

Error Message    %SYSTEM_CONTROLLER-3-ERROR: Error condition detected: [chars]

Explanation    The most common errors from the Mistral ASIC on the MSFC are TM_DATA_PARITY_ERROR, SYSDRAM_PARITY_ERROR, SYSAD_PARITY_ERROR, and TM_NPP_PARITY_ERROR. Possible causes of these parity errors are random static discharge or other external factors.

Recommended Action    If the error message appears only once (or rarely), monitor the system log to determine whether the error message was an isolated incident. If the message recurs, check the environmental conditions for problems such as power brownouts, static discharges, or strong EMI fields. If these environmental conditions are within normal ranges and the error continues to appear, the supervisor engine may need to be replaced.

Error Message    %SYSTEM_CONTROLLER-3-EXCESSIVE_RESET: System Controller is getting 
reset so frequently 

Explanation    The MISTRAL ASIC is being reset frequently. The usual cause is an improperly seated module or another hardware condition.

Recommended Action    Power down and reseat the module. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYSTEM_CONTROLLER-3-INVALID_EARL_HANDLER: EARL interrupt handler is 
not valid 

Explanation    The EARL interrupt handler is not valid.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %SYSTEM_CONTROLLER-3-MISTRAL_RESET: System Controller is reset:Normal 
Operation continues 

Explanation    The system controller is being reset. Operation will continue, but the message rate will be limited.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TAC Messages

This section contains TACACS system messages.

Error Message    %TAC-3-SERVCONF: Server config failure: [chars] 

Explanation    The server configuration failed.

Recommended Action    Please configure the server properly.

Error Message    %TAC-3-SERVINT: [chars] 

Explanation    This is an internal software error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %TAC-3-SERVNO: Server [chars] is not configured 

Explanation    The server is not configured.

Recommended Action    Please configure a server before un-configuring it.

Error Message    %TAC-4-SERVREFNAME: Warning: Server [chars] is still referenced by 
server group. 

Explanation    The server being removed is still referenced by a server group.

Recommended Action    Please dereference the server from the server group as soon as possible.

Recommended Action   

Error Message    %TAC-6-SERVDEP: tacacs-server host CLI will be deprecated soon. Please 
move to tacacs server CLI 

Explanation    Migration from tacacs-server host CLI to tacacs server CLI.

Recommended Action    Please try to use the new CLI.

TAR_FS Messages

This section contains tar file system messages.

TAR_FS-3

Error Message    %TAR_FS-3-IMAGE_FILE_INVALID: [chars] file not found in archive 

Explanation    The tar file system could not locate the relevant tar element inside the archive.

Recommended Action    Check whether the archive is complete and not corrupted, or if it is the wrong format. If the problem can be recreated with debug ifs file turned on, you can more quickly identify the problem. Save the output of the archive tar /table archive-name command if it is a pure tar archive, or the show image contents file archive-name command if the archive is a system image. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TCAM_MGR Messages

This section contains TCAM manager messages.

TCAM_MGR-3

Error Message    %TCAM_MGR-3-BAD_FIRST_DYN_REGION: [dec] 

Explanation    A TCAM error was detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCAM_MGR-3-BAD_LAST_DYN_REGION: [dec] 

Explanation    A TCAM error was detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCAM_MGR-3-INTERNAL_ERROR: [chars], [chars], [dec] 

Explanation    A TCAM error was detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCAM_MGR-3-INVALID_OPERATION: [chars], [dec] 

Explanation    A TCAM error was detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCAM_MGR-3-INVALID_REG_TYPE: [chars], [dec] 

Explanation    A TCAM error was detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCAM_MGR-3-MALLOC_FAIL: [chars], [chars] 

Explanation    A TCAM error was detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCAM_MGR-3-OP_FAIL: [chars] failed for application [chars], 
application entry [hex] with [chars] error 

Explanation    A TCAM error was detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCAM_MGR-3-UNUSUAL_BUG_WARNING: [chars] mbu [hex] free_array_index 
[dec] region_id [dec] 

Explanation    A TCAM error was detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TCAMMGR Messages

This section contains TCAM manager messages.

TCAMMGR-3

Error Message    %TCAMMGR-3-GROW_ERROR: cam region [dec] can not grow 

Explanation    This CAM region is configured as a static region with a fixed number of entries, and a call was requested to add more CAM entries to the specified region.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCAMMGR-3-HANDLE_ERROR: cam handle [hex] is invalid 

Explanation    The CAM handle that was used by the caller is invalid.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCAMMGR-3-INDEX_ERROR: cam value/mask index [dec] is invalid 

Explanation    The CAM index that was used by the caller is invalid.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCAMMGR-3-MOVE_ERROR: cam entry move from index [int] to index [int] 
failed 

Explanation    A move operation for a CAM entry from one index to another has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCAMMGR-3-REGION_ERROR: cam region [dec] is invalid 

Explanation    The CAM region is invalid.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCAMMGR-3-REGMASK_ERROR: invalid cam region [dec] mask [dec] pair 

Explanation    Only a predetermined set of masks are allowed in a region. The caller requested to install an entry in the specified region that contained an invalid mask for that region.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TCATM Messages

This section contains ATM tag distribution and control messages.

TCATM-3

Error Message    %TCATM-3-INTERNAL: [chars] 

Explanation    An operation that is required for proper operation of the TCATM has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TCP Messages

This section contains Transmission Control Protocol (TCP) messages.

TCP-2

Error Message    %TCP-2-INVALIDTCB: Invalid TCB pointer: [hex] 

Explanation    An invalid TCB is used.

Recommended Action    If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.

TCP-3

Error Message    %TCP-3-BADMSS: Incorrect mss [dec] observed 

Explanation    The maximum segment size is incorrect. TCP cannot guarantee further reliable operation for this connection.

Recommended Action    Check the MTU for the interface and increase it as required. If, after adjusting the MTU, this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCP-3-CHKPT_INIT: TCP failed to initialize checkpoint storage: %s 

Explanation    The TCP process failed to initialize checkpoint storage for ports.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCP-3-ERR_DUMP_DEB: netdump_print_context failed, %d 

Explanation    Netdump print failed while dumping a process debug context.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCP-3-ERR_MD5_INVALID: MD5 validation failed, incoming packet src: 
%s:%d, dst: %s:%d 

Explanation    MD5 validation failed on an incoming packet.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCP-3-ERR_MD5_WRITE: MD5 option write failed, dst: %s:%d 

Explanation    The TCP process failed to write an MD5 option.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCP-3-ERR_NETWORK_INIT: TCP failed to connect with network layer: %s, 
error %s 

Explanation    TCP initialization with the network layer failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCP-3-ERR_OUT_BUFF: ran out of buffer with %ld bytes %s to send 

Explanation    TCP ran out of buffer space while copying segment data.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCP-3-ERR_PAK_FSV: %s 

Explanation    An FSV operation failed on the packet.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCP-3-ERR_PAK_DISCARD: %s: %s,  <%s:%d> -> <%s:%d> 

Explanation    Packet information from a discarded packet is displayed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCP-3-ERR_PCB_VECTOR: ip_pcb_get_family_vector failed, %d 

Explanation    The TCP process failed to get a pointer to the PCB family vector.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCP-3-ERR_SET_APP_LEN: %s: set_Application_length failed: %s 

Explanation    The TCP process failed to set an application buffer for the segment.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCP-3-FORKFAIL: Failed to start a process to negotiate options. 

Explanation    The system failed to create a process to handle requests from a client. This condition could be caused by insufficient memory.

Recommended Action    Reduce other system activity to ease memory demands.

Error Message    %TCP-3-SOCKET_RESMGR_ATTACH: Failed to setup the transport as a 
resource manager: %s 

Explanation    The TCP process failed to advertise itself to the system as a resource manager.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCP-3-TRACE_ERR: %s error (%d). Premature trace termination for 
control block 0x%p 

Explanation    A trace terminated prematurely.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TCP-4

Error Message    %TCP-4-ERR_PAK_CLIENT: %s, res %d 

Explanation    A packet client operation failed in TCP.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCP-4-WARNING_DEBUG: %s 

Explanation    TCP failed to open the console device for debug.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TCP-6

Error Message    %TCP-6-INFO_RCV_SIG: recieved signal %d 

Explanation    The TCP process received a signal.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TCP-6-MD5NOSPACE: Insufficient space for MD5 option 

Explanation    There was insufficient space for the MD5 option. This condition should not occur, because the MD5 option, when requested, is required and is given preference over other TCP options.

Recommended Action    Unconfigure other TCP options, if any, in an attempt to create space for the MD5 option. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TCP-7

Error Message    %TCP-7-ERR_TCP_INIT: TCP failed to initialize: %s, error %s

Explanation    TCP initialization failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TENGIGE_LC Messages

This section contains 10-Gigabit Ethernet line card messages.

TENGIGE_LC-3

Error Message    %TENGIGE_LC-3-LASER_TEMP_ERR: Laser Temperature Alarm : [dec]/[dec] 

Explanation    A laser temperature alarm condition has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TENGIGE_LC-3-MIB_TENGIGE_LASER_FAILURE: Laser failure detected 
during soft-start procedures : [chars] 

Explanation    A laser failure has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TENGIGE_LC-3-MIB_TENGIGE_LOSYNC_ALM: Loss of Sync ; [chars] 

Explanation    The Gigabit Ethernet function lost its synchronization.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TENGIGE_LC-3-TENGIGE_LOSYNC_ALM: [chars] side Loss of Sync lock: 
[chars] 

Explanation    The Gigabit Ethernet function lost its synchronization.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TENGIGE_LC-3-TENGIGE_LOSYNC_ALM_CLR: CLEARED : [chars] Loss of Sync 
lock: [chars] 

Explanation    The Gigabit Ethernet function lost its synchronization.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TENGIGE_LC-6

Error Message    %TENGIGE_LC-6-LASER_DISABLED: Laser disabled as per user configuration 
[[dec]/[dec]] 

Explanation    The laser has been disabled as specified by the user configuration.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TENGIGE_LC-6-LASER_DISABLED_BY_HW: Laser disabled as per laser safety 
configuration [[dec]/[dec]] 

Explanation    The laser has been disabled as specified by the safety configuration.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TENGIGE_LC-6-MIB_TENGIGE_TRUNK_LOSYNC_PALM: Trunk side Loss of Sync 
Prealarm; [chars] 

Explanation    The trunk lost its synchronization while it was receiving data.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TENGIGE_LC-6-TENGIGE_TRUNK_RX_LOSYNC_PALM: Trunk side Loss of Sync 
lock Prealarm: [chars] 

Explanation    The trunk lost its synchronization while it was receiving data.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TID_HA Messages

This section contains table ID high availability (HA) messages.

TID_HA-3

Error Message    %TID_HA-3-ISSUERR: [chars] [chars] 

Explanation    An error occurred during an in-service software upgrade (ISSU) versioning operation.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TID_HA-3-ISSUERRCF: [chars] checkpoint code [dec] 

Explanation    An error occurred during an ISSU versioning operation due to an error in the checkpoint facility.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TID_HA-3-RXFAIL1: [chars] 

Explanation    An error occurred while receiving a table ID synchronization message.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TID_HA-3-RXFAIL2: [chars], type [dec], version [dec], flags [hex] 

Explanation    An error occurred while receiving a table ID synchronization message.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message    %TID_HA-3-RXFAIL3: [chars] type [dec], version [dec],flags [hex], 
application [dec], action [dec], tableid [dec], name [chars] 

Explanation    An error occurred while receiving a table ID synchronization message.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TID_HA-3-SYNCFAIL: [chars] 

Explanation    Internal table ID information may have not been synchronized to the standby unit correctly.

Recommended Action    Reload the standby unit. If the error condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TID_HA-3-SYNCFAILCF: [chars] checkpoint code [dec] 

Explanation    Internal table ID information may have not been synchronized to the standby unit correctly due to an error in the checkpoint facility.

Recommended Action    Reload the standby unit. If the error condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TID_HA-3-TXFAIL: [chars], name [chars] tableid [dec] action [dec] 

Explanation    An error occurred while sending the internal table ID information.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TID_HA-3-TXFAILCF: [chars], name [chars], tableid [dec], action 
[dec], checkpoint code [dec] 

Explanation    Failed to send internal table ID information due to an error in the checkpoint facility.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TIDP Messages

This section contains Threat Information Distribution Protocol (TIDP) messages.

TIDP-3

Error Message    %TIDP-3-RESTART: Restarting TIDP due to unexpected error 

Explanation    An unexpected error has occurred in the Threat Information Distribution Protocol (TIDP) process. TIDP has been restarted in an attempt to restore operation.

Recommended Action    Enter the debug tidp errors and debug tidp events commands to gather data that may help identify the nature of the error. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TIDP-4

Error Message    %TIDP-4-AUTHFAIL: Message from %s, %i failed authentication 

Explanation    The signature of a received message failed authentication. The message has been dropped.

Recommended Action    Check the local and peer configurations to make sure that compatible authentication key sets are used.

Error Message    %TIDP-4-REPLAYMSG: Unexpected message from %s, %i received 

Explanation    A message with a sequence number outside of the acceptable range was received and has been dropped. The message might be a replay message and might indicate an intrusion attack.

Recommended Action    Verify that the peer's hardware and configuration has not been altered. Verify connectivity to the peer.

Error Message    %TIDP-4-SRCCHANGED: Address changed was being used by TIDP 

Explanation    An interface IP address was changed, but the former address was being used as the Threat Information Distribution Protocol (TIDP) source address. TIDP cannot operate properly if the address is not local.

Recommended Action    Restore the original IP address to the original interface or to a new interface, or change the TIDP source address.

TIDP-5

Error Message    %TIDP-5-BADMSG: Message from %s, %i failed validation 

Explanation    A message has failed basic header and range check validation. The message has been dropped.

Recommended Action    Check the local and peer configurations to make sure that compatible versions of TIDP and encryption keys are used.

Error Message    %TIDP-5-OVERSIZE: Oversized message received from %s, %i 

Explanation    A larger than expected message was received and has been dropped.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TIDP-5-PEERSRCCHANGED: TIDP source address of the connection to peer 
%i is changed 

Explanation    The Threat Information Distribution Protocol (TIDP) source address changed. The change might be caused by DHCP renewal or by the user manually changing the IP address at the interface.

Recommended Action    No action is required.

Error Message    %TIDP-5-REGFAIL: Failed to register to peer %s, %i, group %u 

Explanation    Attempts to register with the specified peer have failed. Another attempt will be made after the configured maximum retry interval.

Recommended Action    Verify connectivity to the peer and make sure that the configuration between peers is compatible.

TIDP-6

Error Message    %TIDP-6-DUPLICATE: Duplicate message from %s, %i received 

Explanation    A message was received that had the same sequence number as a previously received message. The message has been dropped.

Recommended Action    No action is required.

TINY_FRAG_POLICER Messages

This section contains tiny fragment policer messages.

TINY_FRAG_POLICER-6

Error Message    %TINY_FRAG_POLICER-6-AGGREGATE_THRESHOLD_EXCEEDED: [dec] bps: it is 
recommended to reduce the hi threshold value 

Explanation    The fragment offset == 1 (fo1) packets aggregate threshold has exceeded the acceptable value.

Recommended Action    Reduce the interface high-threshold values.

Error Message    %TINY_FRAG_POLICER-6-HI_THRESHOLD_EXCEEDED: [dec] bps: installing 
rate limiter for vlan [int] on interface [chars] 

Explanation    The fragment offset == 1 (fo1) packets high threshold has exceeded the acceptable value.

Recommended Action    This is an informational message only. No action is required.

Error Message    %TINY_FRAG_POLICER-6-RATELIMITER_FAILED: could not [chars]install 
rate limiter for vlan [int] interface [chars] 

Explanation    The fragment offset == 1 (fo1) rate installer failed due to resource issues.

Recommended Action    This is an informational message only. No action is required.

Error Message    %TINY_FRAG_POLICER-6-RATELIMITER_REMOVED: removing rate limiter for 
vlan [int] from interface [chars] 

Explanation    The fragment offset == 1 (fo1) packets dropped below the low threshold.

Recommended Action    This is an informational message only. No action is required.

TMS Messages

This section contains Threat Management Service (TMS) messages.

TMS-2

Error Message    %TMS-2-PROCESS_ERR: Router could not create a TMS controller process 

Explanation    The router was unable to create a TIDP-based Mitigation Services (TMS) controller process.

Recommended Action    Reload the device.

TMS-4

Error Message    %TMS-4-BAD_PKT: %s| Group=%u|%s Type=%d| Flags=%d 

Explanation    The controller has received an invalid or unexpected packet from the consumer.

Recommended Action    Check the specified consumer for the TIDP-based Mitigation Services (TMS) protocol operation.

Error Message    %TMS-4-MSG_ERR: Unknown message event reveived 

Explanation    The TIDP-based Mitigation Services (TMS) process received an unknown message event.

Recommended Action    If this message recurs, reload the device.

Error Message    %TMS-4-PROCESS_STOP: PROCESS=%s| ACTION=%s. 

Explanation    The specified process is stopped.

Recommended Action    Reload the device.

Error Message    %TMS-4-UNKN_EVENT_ERR: UNKNOWN Event for Event=%d. 

Explanation    The TMS controller process received an unknown event.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TMS-4-UNKN_PROCESS_ERR: An unknown operational error occurred. 

Explanation    The TMS process cannot operate due to an internal system error.

Recommended Action    Reload the device.

Error Message    %TMS-4-UNKN_TIMER_ERR: An unknown Timer operational error occurred 

Explanation    The TMS process cannot operate due to an internal system error.

Recommended Action    Reload the device.

TMS-6

Error Message    %TMS-6-CONSUMER_CLEAR: %s 

Explanation    The consumer has cleared all statistics.

Recommended Action    No action is required.

Error Message    %TMS-6-CONSUMER_STATE: %s 

Explanation    This message indicates whether the TIDP-based Mitigation Services (TMS) consumer is configured or unconfigured.

Recommended Action    No action is required.

Error Message    %TMS-6-DEVICE: %s| Group=%u|%s Status=%s 

Explanation    This message indicates whether a consumer is registered or unregistered on the specified group.

Recommended Action    No action is required.

Error Message    %TMS-6-GROUP: %s| Group=%u|%s Status=%s 

Explanation    This message indicates whether a group is configured or unconfigured on the specified host.

Recommended Action    No action is required.

Error Message    %TMS-6-RESET: %s| Group=%u| %s Action=%s| Start TID=%d| End TID=%d 

Explanation    The controller sent a reset request for an action to a specific consumer or a group.

Recommended Action    No action is required.

Error Message    %TMS-6-STATUS: %s| Group=%u|%s Start TID=%d| End TID=%d 

Explanation    The controller sent a status request to a specific consumer or a group.

Recommended Action    No action is required.

Error Message    %TMS-6-THREAT: %s| Group=%u|%s TID=%d 

Explanation    The controller sent a threat message to a specific consumer or a group.

Recommended Action    No action is required.

Error Message    %TMS-6-THREATSTATUS: %s| Group=%u|%s Threat=%d| Version=%d| Action=%s 

Explanation    This message displays the status of a threat on a consumer in the specified group.

Recommended Action    No action is required.

Error Message    

TN Messages

This section contains Telnet messages.

TN-2

Error Message    %TN-2-BADCONN: Bad conn pointer [hex] closing all connections on 
terminal line [dec] 

Explanation    An internal software error has occurred.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TOPN_COUNTERS Messages

This section contains switch TopN report counters messages.

TOPN_COUNTERS-3

Error Message    %TOPN_COUNTERS-3-MGMT: %s transmit receive byte count is excessive, 
1st poll %llu, 2nd poll %llu 

Explanation    The traffic counter value on the interface is higher than expected. The module might be reporting an erroneous number.

Recommended Action    Verify the traffic flow on the interface. If the flow does not match the TOPN report, contact your Cisco technical support representative.

TOPN_COUNTERS-4

Error Message    %TOPN_COUNTERS-4-MEM_UNAVAIL: Memory was not available for handling 
the TopN request 

Explanation    The system cannot handle the TopN request because of lack of memory.

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

TOPN_COUNTERS-5

Error Message    %TOPN_COUNTERS-5-AVAILABLE: TopN report [dec] is available 

Explanation    The specified report is ready and can be viewed by the users.

Recommended Action    This is an informational message only. No action is required.

Error Message    %TOPN_COUNTERS-5-DELETED: TopN report [dec] deleted by [chars] 

Explanation    The specified report has been deleted by the specified user.

Recommended Action    This is an informational message only. No action is required.

Error Message    %TOPN_COUNTERS-5-KILLED: TopN report [dec] task killed by [chars] 
[chars] 

Explanation    The system was in the process of generating the specified report, but the specified user terminated the report before its completion.

Recommended Action    This is an informational message only. No action is required.

Error Message    %TOPN_COUNTERS-5-NOPORTS: No interfaces in the system match the 
interface type for the generation of the topN report [dec] 

Explanation    There were no interfaces in the system that matched the interface type selected in the specified report.

Recommended Action    This is an informational message only. No action is required.

Error Message    %TOPN_COUNTERS-5-STARTED: TopN collection for report [dec] started by 
[chars] 

Explanation    The TopN report that was requested by the specified user starts with the specified report number.

Recommended Action    This is an informational message only. No action is required.

TPLUS Messages

This section contains Terminal Access Controller Access Control System (TACACS) protocol messages.

TPLUS-3

Error Message    %TPLUS-3-FORKFAIL: Failed to fork process for [chars]. 

Explanation    A process fork failed, probably due to insufficient memory.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TRACKING Messages

This section contains object tracking (TRACKING) messages.

TRACKING-5

Error Message    %TRACKING-5-STATE: %d %s %s %s %s-%s 

Explanation    A tracked object has changed its state.

Recommended Action    No action is required.

TRAFFIC_UTIL Messages

This section contains traffic utilization (TRAFFIC_UTIL) messages.

TRAFFIC_UTIL-4

Error Message    %TRAFFIC_UTIL-4-MONITOR_BACKPLANE_BELOW_THR: Backplane traffic 
utilization is %d%%, below threshold(%d%%) within %d second interval 

Explanation    The backplane traffic utilization is below the utilization threshold.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRAFFIC_UTIL-4-MONITOR_BACKPLANE_REACH_THR: Backplane traffic 
utilization is %d%%, reached threshold(%d%%) within %d second interval 

Explanation    The backplane traffic utilization has reached a utilization threshold.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRAFFIC_UTIL-4-MONITOR_FABRIC_EG_BELOW_THR: Module %d, Channel %d 
egress traffic utilization is %d%%, below or equal threshold(%d%%) within %d 
second interval 

Explanation    The fabric channel egress traffic utilization is below a utilization threshold.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRAFFIC_UTIL-4-MONITOR_FABRIC_EG_REACH_THR: Module %d, Channel %d 
egress traffic utilization is %d%%, reached threshold(%d%%) within %d second 
interval 

Explanation    The fabric channel egress traffic utilization has reached a utilization threshold.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRAFFIC_UTIL-4-MONITOR_FABRIC_IG_BELOW_THR: Module %d, Channel %d 
ingress traffic utilization is %d%%, below or equal threshold(%d%%) within %d 
second interval 

Explanation    The fabric channel ingress traffic utilization is below a utilization threshold.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRAFFIC_UTIL-4-MONITOR_FABRIC_IG_REACH_THR: Module %d, Channel %d 
ingress traffic utilization is %d%%, reached threshold(%d%%) within %d second 
interval 

Explanation    The fabric channel ingress traffic utilization has reached a utilization threshold.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TRANGE Messages

This section contains time-range (TRANGE) error messages.

TRANGE-2

Error Message    %TRANGE-2-NOMEMORY: Alloc fail for time-range config buffer. Disabling 
distributed mode on lc 

Explanation    The system was unable to allocate a buffer to send time-range configuration information to the line cards.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show chunks commands and your pertinent troubleshooting logs. show chunks

Error Message    %TRANGE-2-WRONGREQUEST: Invalid request to allocate chunk of size %d 

Explanation    A request was made to allocate a time-range chunk greater than the maximum allowed size (TRANGE_LARGE_CHUNK_SZ).

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRANGE-2-WRONGSIZE: Incorrect length trange ipc xdr of len=%d 
received 

Explanation    The RP sent a time-range configuration message of the wrong size.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TRANSCEIVER Messages

This section contains transceiver module messages.

TRANSCEIVER-3

Error Message    %TRANSCEIVER-3-ATTACH_FAILURE: Detected for transceiver module in 
[chars], module disabled 

Explanation    A software device driver attach has failed. This condition could be caused by a software, firmware, or hardware problem, but a software or firmware problem is more likely. As a result of the error, the module is disabled.

Recommended Action    Power down and reseat the module. Hardware replacement should not occur on the first occurrence. Before requesting hardware replacement, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRANSCEIVER-3-CHECKSUM_ERROR: Detected in the transceiver module in 
[chars], module disabled 

Explanation    A checksum error was detected when reading the ID PROM of a transceiver module for the specified interface. As a result of the error, the module is disabled.

Recommended Action    Power down and reseat the module. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRANSCEIVER-3-INIT_FAILURE: Detected for transceiver module in 
[chars], module disabled 

Explanation    An initialization failure occurred for the transceiver module for the specified interface. This condition could be caused by a software, firmware, or hardware problem. As a result of the error, the module is disabled.

Recommended Action    Power down and reseat the module. Hardware replacement should not occur on the first occurrence. Before requesting hardware replacement, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRANSCEIVER-3-INTERNAL_ERROR: [chars] 

Explanation    The transceiver subsystem encountered an internal software error. The message contains text that can be used to help identify the nature of the problem.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRANSCEIVER-3-NOT_COMPATIBLE: Detected for transceiver module in 
[chars], module disabled 

Explanation    The transceiver module for the specified interface is not compatible with the interface. As a result of the error, the module is disabled.

Recommended Action    Replace the module with a compatible transceiver. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRANSCEIVER-3-NOT_IDENTIFIED: Detected for transceiver module in 
[chars], module disabled 

Explanation    The transceiver module for the specified interface could not be identified and may not be compatible with the interface. As a result of the error, the module is disabled.

Recommended Action    Replace the module with a compatible transceiver. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRANSCEIVER-3-NOT_SUPPORTED: Detected for transceiver module in 
[chars], module disabled 

Explanation    The transceiver module for the specified interface is not a Cisco supported module. As a result of the error, the module is disabled.

Recommended Action    Replace the module with a Cisco supported transceiver. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRANSCEIVER-3-OPER_ENABLE_FAILURE: Detected for transceiver module in 
[chars], module disabled 

Explanation    Failed to enable the transceiver module for the specified interface. This condition could be caused by a software, firmware, or hardware problem. As a result of the error, the module is disabled.

Recommended Action    Power down and reseat the module. Hardware replacement should not occur on the first occurrence. Before requesting hardware replacement, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRANSCEIVER-3-RPC_FAILED: Application error rc = [dec]: 

Explanation    The system failed to retrieve the information required to execute the command.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show version command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRANSCEIVER-3-RPC_LC_PROC_INIT_FAIL: Transceiver RPC init failure: 
[chars] 

Explanation    The system failed to create the resources required to process user interface commands for transceivers. The error is not fatal but some show commands could fail.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show version command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRANSCEIVER-3-RPC_PROCESSING_ERROR: Transceiver RPC error: [chars] 

Explanation    A nonfatal error occurred during the processing of an RPC message.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show version command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TRANSCEIVER-3-SM_CREATION_FAILURE: Transceiver OIR State Machine 
creation failed for [chars], module disabled. 

Explanation    A state machine could not be created for the transceiver OIR operation. If a memory allocation message was also received with this message, this condition indicates insufficient system memory. Other possible causes include an invalid subblock pointer.

Recommended Action    If it is insufficient system memory, reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TRANSCEIVER-6

Error Message    %TRANSCEIVER-6-INSERTED: transceiver module inserted in [chars] 

Explanation    The online insertion and removal (OIR) facility detected a newly inserted transceiver module for the interface specified in the error message.

Recommended Action    This is an informational message only. No action is required.

Error Message    %TRANSCEIVER-6-REMOVED: Transceiver module removed from [chars]

Explanation    The online insertion and removal (OIR) facility detected the removal of a transceiver module from the specified interface.

Recommended Action    This is an informational message only. No action is required.

TRIFECTA Messages

This section contains Trifecta service module messages.

Error Message    %TRIFECTA-6-X86_FPGAVER_MISMATCH: Module [dec]: [chars] 

Explanation    Trifecta X86 FPGA version mismatch.

Recommended Action    No action is required.

Error Message    %TRIFECTA-6-X86ONLINE: Trifecta X86 in slot [dec] is online. 

Explanation    Trifecta X86 has finished booting up and is online.

Recommended Action    No action is required.

Error Message    %TRIFECTA-6-X86_RESTART_REASON: Module [dec]: [chars] 

Explanation    Trifecta X86 restart reason.

Recommended Action    No action is required.

TTFIB_NP_CLIENT Messages

This section contains Toaster Tag FIB (TTFIB) NP client messages.

TTFIB_NP_CLIENT-3

Error Message    %TTFIB_NP_CLIENT-3-ERROR: [chars] [chars] [chars] 

Explanation    Failed to set or clear port mode flags because the NP returned a failure condition.

Recommended Action    Reload the Cisco IOS image on the affected card or platform. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TTFIB_NP_CLIENT-3-INFO: [chars] 

Explanation    TTFIB NP client failed to initialize properly, which results in improper operation of the any transport over MPLS (AToM) feature.

Recommended Action    Reload the Cisco IOS image on the affected card or platform. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TTFIB_NP_CLIENT-3-NOMEM: [chars] 

Explanation    TTFIB NP client failed to initialize properly, which results in improper operation of the any transport over MPLS (AToM) feature.

Recommended Action    This message may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled via the configuration. Reload the Cisco IOS image on the affected card or platform. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TTFIB_NP_CLIENT-4

Error Message    %TTFIB_NP_CLIENT-4-HDLC: [chars] 

Explanation    Improper usage of SIP-400 for the HDLC over MPLS (HDLCoMPLS) feature.

Recommended Action    This is an informational message only. No action is required.

Error Message    %TTFIB_NP_CLIENT-4-PPP: [chars] 

Explanation    Improper usage of SIP-400 for the PPP over MPLS (PPPoMPLS) feature.

Recommended Action    This is an informational message only. No action is required.

Error Message    %TTFIB_NP_CLIENT-4-VPLS: [chars] 

Explanation    Improper usage of SIP-400 for the Virtual Private LAN Service (VPLS) feature.

Recommended Action    This is an informational message only. No action is required.

Error Message    %TTFIB_NP_CLIENT-4-WARN: [chars] [dec] [chars] 

Explanation    A TTFIB entry could not be added because the entry passed is invalid.

Recommended Action    Reload the Cisco IOS image on the affected card or platform. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TUN Messages

This section contains tunnel messages.

TUN-3

Error Message    %TUN-3-API_ARGS: unexpected arguments: [chars], [chars] 

Explanation    A public tunnel component API was called with arguments outside the expected boundaries.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-3-ENDPOINT_ERROR: [chars] [chars] 

Explanation    An internal software error occurred during manipulating the tunnel endpoint database.

Recommended Action    No action is required.

Error Message    %TUN-3-ENDPOINT_STORE: Operation [chars] failed for [chars] 

Explanation    Manipulation of the tunnel endpoint store has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-3-ILLEGAL_ARGS: Illegal arguments - [chars] 

Explanation    An internal software error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-3-MTUCONFIGEXCEEDSL2MTU_IPV4: [chars] IPv4 MTU configured [int] 
exceeds tunnel maximum MTU [int] 

Explanation    An IPv4 MTU value is configured on the tunnel interface and this value exceeds the tunnel's maximum MTU. This message is typically observed when the tunnel header size changes or when the MTU of the underlying exit interface changes. As a result of either, the tunnel maximum MTU can change. This message can also be observed when using an IPv6 tunnel to carry IPv4 since IPv4 MTU config in this case allows for a value to be configured that is greater than the tunnel's maximum MTU. As a result of any of these conditions, packets may be dropped.

Recommended Action    If a specific IPv4 MTU value is not required, it is recommended that you leave the value at the default by typing no ip mtu on the tunnel interface. If a specific value is required, it is recommended that you check the interface MTU value from the show interface tunnel command and adjust ip mtu on the tunnel interface to be lower than or equal to this.

Error Message    %TUN-3-MTUCONFIGEXCEEDSL2MTU_IPV6: [chars] IPv6 MTU configured [int] 
exceeds tunnel maximum MTU [int] 

Explanation    An IPv6 MTU value is configured on the tunnel interface and this value exceeds the tunnel's maximum MTU. This message is typically observed when the tunnel header size changes or when the MTU of the underlying exit interface changes. As a result of either, the tunnel maximum MTU can change. This message can also be observed when using an IPv6 tunnel to carry IPv6 since IPv6 MTU config in this case allows for a value to be configured that is greater than the tunnel's maximum MTU. As a result of any of these conditions, packets may be dropped.

Recommended Action    If a specific IPv6 MTU value is not required, it is recommended that you leave the value at the default by typing no ipv6 mtu on the tunnel interface. If a specific value is required, it is recommended that you check the interface MTU value from the show interface tunnel command and adjust ipv6 mtu on the tunnel interface to be lower than or equal to this.

TUN-4

Error Message    %TUN-4-MTUCONFIGEXCEEDSTRMTU_IPV4: [chars] IPv4 MTU configured [int] 
exceeds tunnel transport MTU [int] 

Explanation    An IPv4 MTU value has been configured on the tunnel interface and this value exceeds the tunnel's transport (default) MTU. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface.

Recommended Action    If a specific IPv4 MTU value is not required, it is recommended that you leave the value at the default by typing no ip mtu on the tunnel interface. If a specific value is required, it is recommended that you check the tunnel transport MTU value from the show interface tunnel command and adjust ip mtu on the tunnel interface to be lower than or equal to this.

Error Message    %TUN-4-MTUCONFIGEXCEEDSTRMTU_IPV6: [chars] IPv6 MTU configured [int] 
exceeds tunnel transport MTU [int] 

Explanation    An IPv6 MTU value has been configured on the tunnel interface and this value exceeds the tunnel's transport (default) MTU. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface.

Recommended Action    If a specific IPv6 MTU value is not required, it is recommended that you leave the value at the default by typing no ipv6 mtu on the tunnel interface. If a specific value is required, it is recommended that you check the tunnel transport MTU value from the show interface tunnel command and adjust ipv6 mtu on the tunnel interface to be lower than or equal to this.

Error Message    %TUN-4-MTUCONFIGLESSTHAN_MINIPV4MTU: [chars] IPv4 MTU [int] is lesser 
than the minimum IP MTU [int], fragmentation may occur 

Explanation    The IPv4 MTU value calculated on the tunnel interface is less than the minimum IP MTU. The MTU of the underlying exit interface of the tunnel is too small. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface.

Recommended Action    If a specific MTU value is not required for the exit interface, it is recommended that you leave the value at the default by typing no mtu on the exit interface. If a specific value is required, it is recommended that you check the MTU value from the show interface command for the exit interface and adjust mtu on the tunnel exit to be higher than this.

Error Message    %TUN-4-UDLR_IDB_ERROR: UDLR [chars] - [chars] 

Explanation    An error was encountered on a unidirectional link routing (UDLR) interface.

Recommended Action    No action is required.

TUN-5

Error Message    %TUN-5-HW_IF_INDEX_ILLEGAL: Attempt to create tunnel interface for 
[chars] with illegal index: [dec] 

Explanation    The creation of a tunnel interface failed due to an invalid index.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-5-INIT_ERROR: A critical error [chars]occurred during 
initialization 

Explanation    The creation of a tunnel subsystem failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-5-RECURDOWN_SRC: [chars] linestate down, recursive source 
interface, next output [chars] 

Explanation    While the tunnel line state was being evaluated, a source interface was revisited.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-5-TUN_DB_IF: Operation on tunnel interface table failed for 
[chars] - [chars] 

Explanation    A manipulation of the tunnel interface table failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-5-TUN_HWIDB_DELETE: Failed to delete hwidb for Tunnel [dec] index 
[dec] 

Explanation    The deletion of a tunnel interface failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-5-TUN_HWIDB_LIST_DELETE: Failed to delete [chars] from tunnel 
hwidb list 

Explanation    The deletion of a tunnel from the hardware IDB list failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-5-TUN_HWIDB_LIST_INSERT: Failed to add [chars] to tunnel hwidb 
list 

Explanation    The insertion of a tunnel into the hardware IDB list failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-5-TUN_HWIDB_RECYCLE: Failed to recycle hwidb for Tunnel [dec] 
index [dec] 

Explanation    The recycling of a tunnel interface failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-5-TUN_LIST_CREATE: Failed to create tunnel list [chars] 

Explanation    The creation of a tunnel list failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-5-TUN_SWIDB_DELETE: Failed to delete swidb for Tunnel [dec] index 
[dec] 

Explanation    The deletion of a tunnel interface failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-5-TUN_SWIDB_RECYCLE: Failed to recycle swidb for Tunnel [dec] 
index [dec] 

Explanation    The recycling of a tunnel interface failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-5-TUN_TABLE: Operation [chars] on tunnel table failed for [chars] 
- [chars] 

Explanation    The manipulation of the tunnel table failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-5-TUN_UNIT_LIST_DELETE: Failed to delete entry unit [dec] to 
tunnel unit list 

Explanation    A deletion from the tunnel unit failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %TUN-5-TUN_UNIT_LIST_INSERT: Failed to add entry unit [dec] to tunnel 
unit list 

Explanation    The insertion of the tunnel unit failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

TUNSS Messages

This section contains tunnel security messages.

Error Message    %TUNSS-6-PROTECTION_BAD_TUN_MODE: Tunnel mode [chars] not supported by 
tunnel protection. Protection removed. 

Explanation    The chosen tunnel mode is not supported by tunnel protection interfaces. Protection has been turned off and removed.

Recommended Action    Unless protection is desired on this interface, no action is required. If protection is desired, a crypto-map must be used instead.

Error Message    %TUNSS-3-PROTECTION_PROCESS_FAIL

: Failed to create tunnel security process

Explanation    The system failed to start a processes necessary to do tunnel protection.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

UAM Messages

This section contains Upgrade Analysis Module (UAM) messages.

UAM-3

Error Message    %UAM-3-IMPACT_FAMILY: UAM is unable to get the impact of the upgrade 
on '%s' linecards family (SR is '%s') 

Explanation    The Upgrade Analysis Module (UAM) is unable to determine the impact of the current upgrade for the line cards belonging to the specified family. An upgrade operation will probably result in the resetting of all line cards in that family.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %UAM-3-INVALID_CONTEXT: Trying to stop the upgrade, but there is no 
upgrade currently 

Explanation    An application is trying to stop an upgrade cycle, but there is no upgrade in progress.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %UAM-3-INVALID_WB: Trying to set an invalid watched boolean 

Explanation    During runtime, the UAM is trying to release a process using an invalid internal data structure. The command line interface will probably be blocked or the standby supervisor will be unable to boot.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

UBL Messages

This section contains Universal Boot Loader (UBL) messages.

UBL-2

Error Message    %UBL-2-SLAVE_FAIL: Could not download image due to - [chars]. 

Explanation    The standby supervisor engine could not carry out its task of downloading an image from the active supervisor engine due to the reason mentioned in the error message. This could be due to an internal error or due to an old image running on the active supervisor engine that does not support UBL. Prior error messages might provide more information about the actual problem.

Recommended Action    Ensure the conditions mentioned in the message are met. If preceding error messages in the log indicate that this is an internal error, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

UDLD Messages

This section contains UniDirectional Link Detection (UDLD) protocolmessages.

UDLD-3

Error Message    %UDLD-3-UDLD_NOKADIS: UDLD unable to create the kadis timer, status 
[dec] 

Explanation    A failure occurred during creation of the kadis timer from UDLD pseudo preemptive process.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %UDLD-3-UDLD_NOPREEMP: UDLD unable to create pseudo preemptive process 

Explanation    A failure occurred during creation of the UDLD pseudo preemptive process.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

UDLD-4

Error Message    %UDLD-4-UDLD_PORT_FAILURE: UDLD failure reported per user request, 
interface [chars], [chars] detected, 

Explanation    An interface failure was reported because UDLD protocol detected the cause indicated on the interface. Cause is likely due to bad interface hardware or cable misconfiguration. Interface not err-disabled as user choose to see error-report. User should investigate and take action.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

UDLD-6

Error Message    %UDLD-6-UDLD_PORT_LINKDOWN: Fast UDLD cache times out for intf 
[chars], moves port to linkdown state 

Explanation    Fast UDLD cache entry for the reported interface times out. This could be due to either remote side port shut, LC OIR, or real link failure. UDLD moved the port to linkdown state for all cases. If this is not caused by a link failure, UDLD should receive a PM linkdown notification within the next 4 seconds. If UDLD does not receive any notification, then it will consider this a link failure and will err-disable the port.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

UNICAST_FLOOD Messages

This section contains unicast flooding (UNICAST_FLOOD) messages.

UNICAST_FLOOD-4

Error Message    %UNICAST_FLOOD-4-DETECTED: Host [enet] on vlan [dec] is flooding to an 
unknown unicast destination at a rate greater than/equal to [dec] Kfps 

Explanation    A host was found going up and down between ports.

Recommended Action    Verify the reason why the host is sending traffic to an unknown unicast destination.

Error Message    %UNICAST_FLOOD-4-FILTER_TABLE_FULL: The filter table is full 

Explanation    The system has detected too many unicast floods to unknown destinations.

Recommended Action    Investigate the reason why so many hosts in the network are sending traffic to unknown unicast destinations.

UNICAST_FLOOD-5

Error Message    %UNICAST_FLOOD-5-FILTER_INSTALLED: Filter for host [enet] has been 
installed. It will be removed in [dec] minute(s) 

Explanation    A host was flooding unicast packets to an unknown destination. A filter has been installed.

Recommended Action    No action is required.

UTIL Messages

This section contains utility messages.

UTIL-3

Error Message    %UTIL-3-DLL: Data structure error -- %s 

Explanation    A software error occurred, resulting in data structure inconsistency.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %UTIL-3-IDTREE_NOTRACE: [chars] 

Explanation    A software error occurred, resulting in a data structure inconsistency.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %UTIL-3-IDTREE_TRACE: [chars] 

Explanation    A software error occurred, resulting in a data structure inconsistency.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VACL Messages

This section contains VLAN ACL messages.

VACL-4

Error Message    %VACL-4-VLANACCESSMAP_ACTION_CHANGED: No redirect interfaces, map 
<[chars]> - sequence [dec] action set to DROP 

Explanation    One or more redirect interfaces were removed, leaving the redirect interface list emptyand changing the sequence action to DROP.

Recommended Action    Update the sequence, adding one or more valid redirect interfaces to the affected VLAN access maps.

Error Message    %VACL-4-VLANACCESSMAP_CWAN_DELETE: VLAN ACCESS-MAP [chars] applied on 
[chars] will be removed. 

Explanation    Logical interface(MFR,MLP) with a VACL Access-map is being removed so the associated vlan filter will be removed to avoid config errors and inconsistencies

Recommended Action    User has to re-configure the vlan filter if the removed logical interface is being removed

Error Message    %VACL-4-VLANACCESSMAP_RDT_DELETE: [chars] [chars] is removed from 
redirect list of map: [chars] - sequence [dec] 

Explanation    One of the redirect interfaces in a VLAN access map needed to be removed from a redirect sequence. This situation can occur if the interface was deleted or became an active member of an Ethernet channel that is not supported.

Recommended Action    Revert the state of the interface and add this redirect interface again to the redirect sequence for the affected VLAN access maps.

VALENCIA Messages

This section contains Services SPA Carrier Card (SSC-600) Valencia ASIC messages.

VALENCIA-3

Error Message    %VALENCIA-3-GIO: Bay [dec]: [chars]. 

Explanation    A data corruption due to a parity error was detected on the GIO bus.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VALENCIA-3-NP: Bay [dec], [chars][dec]: [chars]. 

Explanation    Data corruption was detected in one of the network processors.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VALENCIA-3-PL3: Bay [dec]: [chars]. 

Explanation    A data corruption due to a parity error was detected on the PL3 interface.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VALENCIA-3-PLL_LOCK: Bay [dec]: [chars] PLL Lock Failure 

Explanation    The specified phase-locked loop (PLL) failed to lock.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VALENCIA-3-PPE: Bay [dec], [chars]: [chars]. 

Explanation    Data corruption was detected in the VLAN RAM.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VALENCIA-3-SPI_FIFO: Bay [dec], [chars]: [chars] [chars]. 

Explanation    Data corruption was detected in one of the SPI FIFOs.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VALENCIA-3-SPI_SNK: Bay [dec]: [chars]. 

Explanation    There was an error receiving data from the SPA, possibly due to data corruption.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VALENCIA-3-SPI_SNK_CHAN: Bay [dec]: [chars] error on channel [dec]. 

Explanation    There was an error receiving data from the SPA.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VALENCIA-3-SPI_SRC: Bay [dec]: [chars]. 

Explanation    There was an error sending data to the SPA.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VDD Messages

This section contains virtual device driver (VDD) messages.

VDD-3

Error Message    %VDD-3-NULL_CB: Supplied %s control block is NULL. %s 

Explanation    An NULL control block was passed internally as part of an operation to read or write to the required register or memory address. As a result, the operation could not be processed and the address contents are now incorrect.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VDD-3-NULL_SPACE_CB: Supplied %s space control block is NULL. %s 

Explanation    An NULL space control block was passed internally as part of an operation to read or write to the required address. As a result, the operation could not be processed and the address contents are now incorrect.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VDD-3-SIZE_TOO_LARGE: An attempt was made to create a %s of size %d 
bits. 

Explanation    The virtual device driver received a request to create a data entity that is larger than allowed. Because the entry cannot be created, its data will be lost.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VFI Messages

This section contains virtual forwarding instance (VFI) messages.

VFI-3

Error Message    %VFI-3-ILLEGAL: %s 

Explanation    An illegal event was processed by the XCONNECT subsystem.

Recommended Action    No action is required.

VFI-4

Error Message    %VFI-4-CONFIG: %s 

Explanation    The specified configuration data for a virtual forwarding instance (VFI) is invalid.

Recommended Action    No action is required.

VINES Messages

This section contains Banyan Virtual Integrated Network Service (VINES) messages.

Error Message    %VINES-2-INVALIDROUTE: Bad [chars] in route for server entry [v-name] 

Explanation    While searching the routing table, the code determined that a pointer that should point to a VINES route structure actually points to some other structure.

Recommended Action    Copy the message exactly as it appears, and report it your technical support representative. If possible, clear the VINES routing table. This will result in a temporary loss of connectivity until all routes are relearned.

VIP Messages

This section contains Versatile Interface Processor (VIP) messages.

VIP-3

Error Message    %VIP-3-SVIP_CRASHINFO_ERROR: Crashinfo initiation failed on the VIP. 

Explanation    The crash information (crashinfo) file for the VIP could not be collected because the process to collect the crashinfo file could not be properly initiated.

Recommended Action    If the error message recurs, copy the message exactly as it appears on the console or in the system log and enter the show controllers vip slot# tech-support and show controllers vip slot# logging commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VIPMLP Messages

This section contains multilink PPP messages.

Error Message    %VIPMLP-2-NOINTERLEAVE: [chars] Interleave not configured due to 
Insufficient memory 

Explanation    Interleave was not configured due to insufficient memory.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VLAN_MAPPING_ISSU Messages

This section contains VLAN mapping in-service software upgrade (ISSU) messages.

VLAN_MAPPING_ISSU-3

Error Message    %VLAN_MAPPING_ISSU-3-BUFFER: vlan_mapping VLAN Mapping ISSU client 
failed to get buffer for message, error %d 

Explanation    The VLAN mapping ISSU client was unable to get a buffer for building a negotiation message. As a result, the client cannot send the negotiation message to the standby unit and the standby unit cannot be brought up.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.

Error Message    %VLAN_MAPPING_ISSU-3-CAPABILITY: vlan_mapping VLAN Mapping ISSU client 
%s 

Explanation    The VLAN mapping ISSU client detected an error during capability negotiation. As a result, there is a mismatch in the client capability between the active and standby unit.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message    %VLAN_MAPPING_ISSU-3-INIT: vlan_mapping VLAN Mapping ISSU client 
initialization failed at %s, error %s 

Explanation    The VLAN mapping ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VLAN_MAPPING_ISSU-3-MSG_NOT_OK: vlan_mapping VLAN Mapping ISSU client 
message %d is not compatible 

Explanation    The VLAN mapping ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message    %VLAN_MAPPING_ISSU-3-MSG_SIZE: vlan_mapping VLAN Mapping ISSU client 
failed to get the message size for message %d 

Explanation    The VLAN mapping ISSU client was unable to calculate the message size for the message specified. The client will be unable to send the message to the standby unit.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message    %VLAN_MAPPING_ISSU-3-POLICY: vlan_mapping VLAN Mapping ISSU client 
message type %d is %s 

Explanation    The VLAN mapping ISSU client received a message type that it does not support. A policy is applied to make the session compatible.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu session commands and your pertinent troubleshooting logs.

Error Message    %VLAN_MAPPING_ISSU-3-SEND_FAILED: vlan_mapping VLAN Mapping ISSU 
client failed to send a negotiation message, error %d 

Explanation    The VLAN mapping ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.

Error Message    %VLAN_MAPPING_ISSU-3-SESSION: vlan_mapping VLAN Mapping ISSU client %s 

Explanation    The VLAN mapping ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message    %VLAN_MAPPING_ISSU-3-TRANSFORM: vlan_mapping VLAN Mapping ISSU client 
%s transform failed, error %s 

Explanation    The VLAN mapping ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the vlan_mapping VLAN Mapping state will not be identical with the active unit.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

VOA Messages

This section contains Hamptons variable optical attenuator (VOA) subcards messages.

VOA-3

Error Message    %VOA-3-HIGH_ALM_THR: High Alarm Threshold for optical power on port 
[chars] [chars] 

Explanation    The high alarm threshold for the optical power level has been exceeded.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VOA-3-HIGH_WARN_THR: High Warning Threshold for optical power on port 
[chars] [chars] 

Explanation    The high warning threshold for the optical power level has been exceeded.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VOA-3-LOW_ALM_THR: Low Alarm Threshold for optical power on port 
[chars] [chars] 

Explanation    The low alarm threshold for the optical power level has been exceeded.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VOA-3-LOW_WARN_THR: Low Warning Threshold for optical power on port 
[chars] [chars] 

Explanation    The low warning threshold for the optical power level has been exceeded.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPD Messages

Error Message    %VPD-4-CESCLK_INIT: ATM CES (Voice Processor Deck) clock source 
initialized to local oscillator. 

Explanation    Warning indicates that ATM CES (Voice Processor Deck ) clock used will be internal.

Recommended Action    No action is required.

VPDN Messages

This section contains Virtual Private Dialup Networking (VPDN) messages.

VPDN-3

Error Message    %VPDN-3-DROP_ADDR_MISMATCH: [chars] 

Explanation    The remote server changed its address.

Recommended Action    Change initiate-to configuration at the LAC to point to the exact IP address LNS will use.

Error Message    %VPDN-3-IP_SWITCH_ERR: l2x ip switching vector not installed 

Explanation    The platform-dependent Layer 2X IP Cisco Express Forwarding (CEF) switching module is missing.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPDN-3-NORESOURCE: [chars] [chars] [chars] no resources for user 
[chars][chars][chars] 

Explanation    The platform (for example, the Cisco Network Authentication Server and L2TP access concentrator (NAS/LAC) or the home gateway and L2TP network server (HGW/LNS)) has exhausted its resources for forwarding a VPDN user.

Recommended Action    Check the available memory of the platform.

VPDN-4

Error Message    %VPDN-4-MIDERROR: [chars] [chars] [chars] unable to terminate user 
[chars][chars][chars] 

Explanation    The HGW/LNS was unable to complete the forwarding of the VPDN user because of an internal error. This condition may be resource-related or configuration-related. A reason string may be present in the message text to indicate the point of failure.

Recommended Action    Check the configuration of the HGW/LNS.

Error Message    %VPDN-4-REFUSED: Session for %s Refused status = %x 

Explanation    The remote server refused this session.

Recommended Action    Check the configuration of the home gateway (HGW) or L2TP Network Server (LNS).

Error Message    %VPDN-4-SESSIONERROR: [chars] [chars][chars] unable to terminate user 
[chars][chars][chars] 

Explanation    The HGW/LNS was unable to complete the forwarding of the VPDN user due to an internal error. This error may be resource related or configuration related. A reason string may be present to indicate the point of failure.

Recommended Action    Check the configuration on the HGW/LNS

VPDN-5

Error Message    %VPDN-5-NOIDB: [chars] [chars] [chars] unable to terminate user 
[chars] 

Explanation    The HGW/LNS has exhausted its resources for creating sessions for VPDN forwarded users. It has reached the maximum number of interfaces allowed on the router.

Recommended Action    Limit the number of interfaces to the maximum allowable interfaces.

Error Message    %VPDN-5-UNREACH: [chars] [chars] [chars] is unreachable 

Explanation    The platform (for example, the Cisco NAS/LAC or the HGW/LNS) has timed out while it was attempting to establish a tunnel connection to a HGW/LNS or NAS/LAC. The timeout may be due to network, authentication, or authorization issues.

Recommended Action    Check the configuration on the platform and check the network connectivity between the NAS/LAC and HGW/LNS. Check to see if the tunnel setup requires a different source IP address from that of the NAS/LAC.

VPDN-6

Error Message    %VPDN-6-AUTHENERR: [chars] [chars] [chars] cannot locate a AAA server 
for [chars] [chars] [chars][chars][chars] 

Explanation    Either the NAS/LAC or the HGW/LNS is unable to locate an AAA server for the purposes of authenticating the user or tunnel. This condition indicates that the router was unable to establish a network connection with the designated or configured server. A reason string may be present in the message text to provide further information.

Recommended Action    Check the AAA configuration on the platform (for example, the Cisco NAS/LAC or the HGW/LNS) and check the network connectivity to the AAA servers.

Error Message    %VPDN-6-AUTHENFAIL: [chars] [chars] [chars], 
[atalk_address]uthentication failure [chars]for [chars] [chars] 
[chars][chars][chars] 

Explanation    The platform (for example, the Cisco NAS/LAC or the HGW/LNS) has failed to authenticate a user or a tunnel, or the HGW/LNS has failed authentication with the client that initiated the session. For authentication failures of the user or tunnel, a reason string should be present in the message text to indicate the point of failure. When a client fails to authenticate the HGW, a reason string may be present, depending upon the point of failure.

Recommended Action    Check the username configuration on the platform and, possibly, the client. If the HGW/LNS is failing authentication, removing the negotiation of outbound authentication (that is, authenticating the user only in the inbound direction) is one possible solution. If AAA is applicable to the condition, check the AAA configuration on the NAS/LAC or HGW/LNS and check the network connectivity to the AAA servers.

Error Message    %VPDN-6-AUTHORERR: [chars] [chars] [chars] cannot locate a AAA server 
for [chars] [chars] [chars][chars][chars] 

Explanation    The platform (for example, the Cisco NAS/LAC or the HGW/LNS) is unable to locate a AAA server for the purposes of authorizing the user or tunnel. The router was unable to establish a network connection with the designated or configured server. A reason string may be present in the message text to provide further information.

Recommended Action    Check the AAA configuration on the platform and check the network connectivity to the AAA servers.

Error Message    %VPDN-6-AUTHORFAIL: [chars] [chars] [chars], 
[atalk_address]uthorization failure for [chars] [chars] [chars][chars][chars] 

Explanation    The platform (for example, the Cisco NAS/LAC or the HGW/LNS) has failed to authorize a user or a tunnel. A reason string may be present in the message text to indicate the point of failure.

Recommended Action    Check the authorization configuration on the platform. If AAA is applicable to the condition, check the network connectivity to the AAA servers.

Error Message    %VPDN-6-CLOSED: [chars] [chars] [chars] closed [chars] [chars] 
[chars][chars][chars] 

Explanation    The remote server, typically the HGW/LNS, closed this session. The reason for the closing is encoded in a hexadecimal format and corresponds to the particular protocol descriptions. For the L2F protocol, the values are documented in section 4.4.5 of the Internet Draft. A description string may also be present that describes the reason for the closing.

Recommended Action    Check the configuration on the platform (for example, the configuration of the Cisco NAS/LAC or the HGW/LNS).

Error Message    %VPDN-6-DOWN: %s %s %s changed state to down %s %s %s%s%s 

Explanation    The remote server, typically the home gateway (HGW) and L2TP Network Server (LNS), closed this tunnel. The reason for the closure is encoded in a decimal format defined in the particular protocol specification. For example, the closure values for Layer 2 Forwarding (L2F) are documented in section 4.4.5 of the L2F Internet Draft. The closure reason may also be displayed in a description string.

Recommended Action    Check the configuration on the network access server (NAS) and L2TP access concentrator (LAC) , or on the home gateway (HGW) and L2TP Network Server (LNS).

Error Message    %VPDN-6-MAX_SESS_EXCD: %s %s %s has exceeded configured local 
session-limit and rejected %s %s %s%s%s 

Explanation    The NAS/LAC or HGW/LNS has refused this session since the configured maximum VPDN session limit has been reached.

Recommended Action    No action is required.

Error Message    %VPDN-6-RESIZE: Updated [chars] session table size to [int] 

Explanation    The platform (for example, the Cisco NAS/LAC or the HGW/LNS) has altered the size of the session table using the CLI.

Recommended Action    No action is required.

Error Message    %VPDN-6-SOFTSHUT: %s %s %s has turned on softshut and rejected %s %s 
%s%s%s 

Explanation    The NAS/LAC or HGW/LNS can no longer accept new connections when the vpdn softshut command has been entered. Existing sessions will continue until termination.

Recommended Action    To allow new connections, enter the no vpdn softshut command. Otherwise, no action is required.

Error Message    %VPDN-6-TIMEOUT: [chars] [chars] [chars] disconnected [chars] [chars] 
[chars][chars][chars] 

Explanation    The platform (for example, the Cisco NAS/LAC or the HGW/LNS) has disconnected the user because of the expiration of a timer. This condition may be PPP negotiation-related or might be an absolute timeout for the session.

Recommended Action    If the session has timed out automatically, no action is required.

Error Message    %VPDN-6-VPDN_DEADCACHE_EVENT: LSG dead cache entry [IP_address] 
[chars] 

Explanation    A dead cache entry status is changed in the VPDN Load Sharing Group (LSG) table. The event could be 'Added', where a LSG entry goes Down, 'Deleted', where an entry moves out of the Down status, or 'Cleared', where an entry is cleared by a user.

VPLS_NP_CLIENT Messages

This section contains VPLS NP client messages.

VPLS_NP_CLIENT-3

Error Message    %VPLS_NP_CLIENT-3-INFO: [chars] 

Explanation    The VPLS NP client failed to initialize properly. This condition will result in improper operation of the any transport over MPLS (AToM) feature.

Recommended Action    Reload the Cisco IOS image on the affected card or platform. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPLS_NP_CLIENT-3-NOMEM: [chars] 

Explanation    The VPLS NP client failed to initialize properly. This condition will result in improper operation of the AToM feature. This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled by the configuration.

Recommended Action    Reload the Cisco IOS image on the affected card or platform. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPLS_NP_CLIENT-4

Error Message    %VPLS_NP_CLIENT-4-WARN: [chars] [dec] [chars] 

Explanation    The entry could not be added because it is invalid.

Recommended Action    Reload the Cisco IOS image on the affected card or platform. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPN_HW Messages

This section contains VPN hardware accelerator for IPSec (VPN_HW) messages.

VPN_HW-0

Error Message    %VPN_HW-0-SELF_TEST_FAILURE: Hardware Crypto self-test failed 
([chars]) 

Explanation    One of the hardware crypto self-tests has failed. The crypto engine is not operable in this state.

Recommended Action    If the failure persists, contact Cisco to replace the hardware.

VPN_HW-1

Error Message    %VPN_HW-1-ALIGN: Slot: [dec] - Alignment failure on packet buffer: 
[hex] 

Explanation    A software error has occurred. The VPN hardware accelerator driver has detected that the buffer is not aligned correctly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPN_HW-1-ERROR: slot: [dec] - [chars] 

Explanation    An error occurred in the application that was using the VPN hardware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPN_HW-1-HEARTBEAT: VPN Module in slot: [dec]: Keepalive lost. 

Explanation    Keepalive messages have been lost, which indicates that the VPN hardware accelerator is no longer operating.

Recommended Action    Reboot your router. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPN_HW-1-INITFAIL: Slot [dec]: [chars] 

Explanation    The VPN hardware accelerator driver could not initialize the accelerator at the slot specified in the error message at the specified point.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPN_HW-1-NOMEMORY: [chars] creation failed for slot [dec] 

Explanation    During its initialization phase, the VPN hardware driver could not allocate memory for the data structure that is specified in the error message.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPN_HW-1-OWNER: slot: [dec]: [chars] packet buffer, pak=[hex] 

Explanation    A software or hardware error has occurred. The VPN hardware accelerator driver has detected that the buffer ring is in an inconsistent and unrecoverable state.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPN_HW-1-PACKET_ERROR: slot: [dec] Packet Encryption/Decryption 
error, [chars] 

Explanation    An unexpected error occurred during the encryption or decryption of a packet.

Recommended Action    This message can occur occasionally during normal operation of the system. It may occur during the transition to a new session key for a security association. In such cases, no action is required. However, if it happens frequently, or is associated with traffic disruption, then note the status value and contact your Cisco technical support representative. The VPN hardware accelerator will most likely need to be replaced.

Error Message    %VPN_HW-1-TOOBIG: Slot: [dec] - [chars] received a packet with size 
[dec]. 

Explanation    A packet was received that was too large. The hardware supports only the MTU size specified in the message.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPN_HW-1-UNSUPP: VPN Module in slot: [dec]: [chars] ([hex]). 

Explanation    This revision or version of the VPN hardware accelerator in the slot specified in the error message is not supported.

Recommended Action    Verify that the VPN hardware adapter is the proper hardware level and software revision for the running version of the Cisco IOS software. If it is, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPN_HW-3

Error Message    %VPN_HW-3-MULTDEV: Cannot support more than one Encryption AIM 

Explanation    A second Encryption AIM was discovered present in the system. The Encryption AIM software only supports a single Encryption AIM. All other Encryption AIMs installed will be ignored.

Recommended Action    Remove one of the Encryption AIMs that are installed in your system.

VPN_HW-4

Error Message    %VPN_HW-4-PACKET_ERROR: slot: [dec] Packet Encryption/Decryption 
error, [chars] 

Explanation    An unexpected error occurred during the encryption or decryption of a packet.

Recommended Action    This message can occur occasionally during normal operation of the system.
It may occur during the transition to a new session key for a security association. In such cases, no action is required. However, if it happens frequently, or is associated with traffic disruption, then note the status value and contact your Cisco technical support representative. The VPN hardware accelerator will most likely need to be replaced.

VPN_HW-6

Error Message    %VPN_HW-6-FIPSFAIL: FIPS test_id [dec]([chars]) Test Failure will be 
induced 

Explanation    The FIPS test was forced to fail from ROMMON.

Recommended Action    If this condition is undesirable, do not set FIPS_FAIL using ROMMON.

Error Message    %VPN_HW-6-INFO: slot: [dec] [chars] 

Explanation    This is an informational message from the VPN hardware accelerator driver.

Recommended Action    No action is required.

Error Message    %VPN_HW-6-INFO_LOC: Crypto engine: [chars] [chars] 

Explanation    This is an informational message from the VPN hardware accelerator driver.

Recommended Action    No action is required.

Error Message    %VPN_HW-6-SHUTDOWN: [chars] shutting down 

Explanation    The specified VPN hardware is shutting down. It may have been physically removed.

Recommended Action    This is an informational message only. No action is required.

VPNMAP Messages

This section contains Virtual Private Network mapper (VPNMAP) messages.

VPNMAP-2

Error Message    %VPNMAP-2-REALLOC_ERROR: Exceeded number of resources to support 
hardware switching of VRF %s. Please unconfigure some of the existing VRFs as some 
entries will be software switched in the next reload. 

Explanation    Because no further hardware resources are available to support hardware switching of VRFs, some VRFs must be software switched. Unconfigure the mls ipv6 vrf command or some of the existing features that use those resources. Examples of features using hardware switching resources are VRF, EoMPLS, and MDT.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, remote command module, show platform software vpn mapping, show platform software vpn status, and show running-config commands and your pertinent troubleshooting logs.

Error Message    %VPNMAP-2-SPACE_EXCEEDED: Exceeded number of resources to support 
hardware switching of VRFs. Please unconfigure some of the existing VRFs as some 
entries will be software switched. 

Explanation    Because no further hardware resources are available to support hardware switching of VRFs, some VRFs must be software switched. Unconfigure the mls ipv6 vrf command or some of the existing features that use those resources. Examples of features using hardware switching resources are VRF, EoMPLS, and MDT.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, remote command module, show platform software vpn mapping, show platform software vpn status, and show running-config commands and your pertinent troubleshooting logs.

VPNSM Messages

This section contains Virtual Private Network Services Module (VPNSM) messages.

VPNSM-2

Error Message    %VPNSM-2-ACE_PKA_KAT_FAILURE: PKA: Known Answer Test failure: [chars] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-2-ACESCPERROR: Null MAC address pointer in SCP module 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPNSM-3

Error Message    %VPNSM-3-ACEI0BADPARAM: PcpManCreateTunn: cannot create tunnel with 
expiring Sa

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI0TCAMFAILED: SpdSpInstall: cannot install Sp [dec]: 
TmInsertSp failed 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI1BADPARAM: SpdSpInstall: cannot install generic SP [dec] 
with non-zero priority 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI1OUTOFSA: PcpQOpCreSaBegin: cannot create new Sa using 
SpdMan 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI10OUTOFCME: PcpManCreateAcl: cannot allocate new Acl for 
aclId=[int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI11NESTOVERFLOW: SpdSaAddTmInsCb: cannot have more than 
[dec] pending nested callbacks from TcamMan 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI11OUTOFSEL: PcpAclGetSpSelSet: cannot clone SelSet for 
ACL [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI2BADPARAM: PcpManUpdateFlow: cannot update flow [dec] 
with invalid ID 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI12IDNOTINUSE: PcpManRemoveAcl: cannot remove 
non-existing access list [int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI12OUTOFSAPAR: SpdSaSetKeys: cannot allocate new SaPar for 
Sa [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI13IDINUSE: PcpManRemoveAcl: cannot remove access list 
[int] while in use 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI3OUTOFSEL: PcpQOpActSaBegin: cannot allocate selector set 
for outer Sa in flowId [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI14BADCMEID: PcpSpdCreateCme: cannot create Cme with 
ID=[dec]: too large 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI14NOLOGA: SpdSaSetParams: cannot allocate SPI with 
TcamMan for Sa [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI15IDNOTINUSE: PcpManRemoveCme: cannot remove 
non-existing Cme [int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI16BADPARAM: PcpManActivateFlowAsync: cannot activate 
flow [dec]: Sa is in the wrong state 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI16TCAMFAILED: SpdSaTmInstallIn: cannot install inbound Sa 
[dec] with TcamMan 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI17BADPARAM: PcpManActivateFlowAsync: cannot activate 
non-existing flow [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI17TCAMFAILED: SpdSaTmInstallOut: cannot install outbound 
Sa [dec] with TcamMan 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI18BADPARAM: PcpManCreateSMap: cannot create outbound SPD 
Map [int] with ingress access list [int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI19BADCMEID: PcpManActivateFlowAsync: cannot activate 
flow [dec] with non-existing Cme [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI2BADPARAM: PcpManUpdateFlow: cannot update flow [dec] 
with invalid ID 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI2NESTOVERFLOW: SpdSaInitTmSaOut: outer outbound Sa [dec] 
of Sa [dec] is above nesting limit of [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI20OUTOFSEL: PcpUtilSelSetFromPar: cannot allocate new 
selector set 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI21BADPARAM: PcpAclAppend: got too many denys for 
aclId=[dec], max is [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI22BADPARAM: PcpAclAppend: got out-of-sequence line number 
[dec] for aclId=[dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI23IDINUSE: PcpSpdCreateCme: cannot create Cme with 
ID=[int]: already used 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI24BADPARAM: PcpAclAppend: got invalid ranges for selector 
set at lineNo=[dec], aclId=[dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI25IDINUSE: PcpAclAppend: got duplicate line number [dec] 
for aclId=[dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI26OUTOFSP: PcpCmeInstallNext: cannot create a new Sp 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI27BADPARAM: PcpManSetFlowKeys: cannot set keys for flow 
[dec]: SA is in the wrong state 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI28IDINUSE: PcpQOpCreSaBegin: cannot create second Sa for 
flow [dec]: conditions for transport adj. are not met 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI29SPDFAILED: PcpCmeInstallNext: cannot install Sp [dec] 
with SpdMan 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI3NESTOVERFLOW: SpdSaGetXformSeq: outer inbound Sa [dec] 
of Sa [dec] is above nesting limit of [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI3OUTOFSEL: PcpQOpActSaBegin: cannot allocate selector set 
for outer Sa in flowId [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI30BADPARAM: PcpSpdUpdateCme: cannot update already queued 
Cme [int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI31BADALENUM: PcpQOpActSaBegin: cannot find access list 
entry number [dec] for cmeId=[dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI32BADPARAM: PcpQOpActSaBegin: cannot delete old 
[chars]bound flow [dec] while activating [chars]bound flow [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI33BADPARAM: PcpCmeActivateSa: got invalid lifetime values 
softSecs=[int], hardSecs=[int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI34BADPARAM: PcpCmeActivateSa: got invalid lifetime values 
softKBytes=[int], hardKBytes=[int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI35BADPARAM: PcpCmeIntersectSaWithSp: cannot activate 
flow [dec] with selector ranges not intersecting parent Sp 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI36BADSELADDR: PcpQOpActSaBegin: cannot activate per-host 
flow [dec] with addresses [dec].[dec].[dec].[dec] and [dec].[dec].[dec].[dec] not 
included in Sp [dec] selector sets 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI37OUTOFSEL: PcpQOpActSaBegin: cannot clone selector set 
to activate per-host flow [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI38BADSELADDR: PcpQOpActSaBegin: cannot activate 
transport mode flow [dec] with addresses [dec].[dec].[dec].[dec] and 
[dec].[dec].[dec].[dec] not included in Sp's selector sets 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI39BADPARAM: PcpTrInProcess: got invalid opcode [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI4BADPARAM: PcpQOpCreSaBegin: got invalid addresses 
[int].[int].[int].[int] and [int].[int].[int].[int] for other Sa of flow [dec]: 
expected [int].[int].[int].[int] and [int].[int].[int].[int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI40BADACLID: PcpManCreateCme: cannot create Cme with 
non-existing access list [int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI41SPDFAILED: PcpQOpSaActivated: cannot finish activating 
Sa [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI42QUEUEFULL: PcpCmeActivateSa: cannot activate Sa [dec]: 
queue is full 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI43BADPARAM: PcpAclAppend: got invalid line number [dec] 
for ACL [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI44QUEUEFULL: PcpSpdCreateCme: cannot create Cme [int] 
(aclId=[int]): queue is full 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI45IDNOTINUSE: PcpManDestroyFlowAsync: cannot delete 
already deleted flow [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI46BADPARAM: PcpQOpActSaBegin: cannot activate 
non-fully-specified Sa for Cme [dec] without Acl 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI47BADPARAM: PcpQOpActSaBegin: cannot activate Sa for 
manual Sp (cmeId=[dec],entry=[dec]), Sa already exists 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI48CMEINUSE: PcpManSetInitMode: cannot set fast init-mode 
in TcamMan: [dec] pending Ops, [dec] Flows and [int] Cmes already exist or TcamMan 
is busy 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI49BADPARAM: PcpManQueryFlow: cannot query flow [dec]: Sa 
is not active 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI5BADPARAM: SpdSaActivate: cannot activate Sa [dec], old 
Sa [dec] already has successor Sa [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI5OUTOFSA: PcpQOpCreSaBegin: cannot create new Sa for flow 
[dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI50CMEINUSE: PcpQOpRemCmeBegin: cannot remove Cme [dec]: 
TcamMan is in Init mode 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI51BADPARAM: PcpSpdCreateCme: got invalid flags 
(manual,dynamic,discover,drop,clear) = ([dec],[dec],[dec],[dec],[dec]), 
cmeId=[dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI52IDINUSE: PcpManCreateAcl: cannot process opcode [int] 
for Acl [int] in state [int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI53BADPARAM: PcpManCreateAcl: cannot create Acl with id 
[int] out of range [0,[int]] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI54CMENOTREADY: PcpSpdCreateCme: cannot create Cme [int] 
with Acl [int] when Acl state is [int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI55SPDFAILED: PcpQOpActSaBegin: cannot begin activating Sa 
[dec] for flowId [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI56IDNOTINUSE: PcpManDestroyFlowAsync: cannot delete flow 
[dec] already being deleted 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI57CMEINUSE: PcpManSetInitMode: cannot set normal 
init-mode in TcamMan: there are pending Flows or Cmes 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI58IDNOTINUSE: PcpManDestroyFlowAsync: flow [dec] already 
queued for deletion 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI59BADPARAM: PcpCmeActivateSa: cannot activate flow [dec] 
as per-host with subset of Sp as a selector set 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI6BADPARAM: PcpTrInProcess: got invalid size [dec] for 
opcode [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI6OUTOFSEL: SpdSpInstall: cannot compute SP's 
permit-SelSets from mixed SelSet list 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI60SPDFAILED: PcpManSaUpdateError: cannot update Flow 
[dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI61BADPARAM: PcpQOpActSaBegin: cannot activate Sa for 
cmeId=[dec], entry=[dec] with bad spdId=[dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI62IDINUSE: PcpQOpCreSaBegin: cannot setup Flow [dec] in 
trans.adj. with outer SA in tunnel mode 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI63CMEINUSE: PcpManActivateFlowAsync: cannot activate 
flow [dec] while using fast policy mode 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI64BADPARAM: PcpQOpActSaBegin: got invalid ranges for 
selector set of fully-specified flow [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI65BADPARAM: PcpManSetInitMode: got invalid flags [hex] 
for setting fast policy mode 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI66NOTREADY: PcpManUpdateFlow: cannot update flow [dec] 
when SA is not active 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI67BADPARAM: PcpSpdCreateSMap: cannot create SMap [int] 
with Acl [int] when Acl state is [int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI68BADPARAM: PcpAclAppend: got invalid flags [hex] at 
lineNo=[dec], aclId=[dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI69BADPARAM: PcpManCreateCme: cannot create Cme [int] with 
spdId [int] out of range [0,[int]] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI7BADPARAM: PcpManSetFlowKeys: cannot set keys for flow 
[dec]: invalid ID 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI7OUTOFSEL: SpdSaTmInstallOut: cannot compute outbound 
SA's permit-SelSets from mixed SelSet list 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI70IDNOTINUSE: PcpManUpdateCme: cannot update 
non-existing Cme [int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI71QUEUEFULL: PcpSpdUpdateCme: cannot update Cme [int]: 
queue is full 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI72QUEUEFULL: PcpSpdCreateSMap: cannot create SPD map with 
mapId [int]: queue is full 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI73BADPARAM: PcpSpdCreateSMap: cannot create SPD map with 
mapId [int] out of range [0,[int]] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI74IDINUSE: PcpSpdCreateSMap: cannot create SPD map with 
mapId [int] already in use 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI75TMFAILED: PcpSMapInstall: cannot insert SMap [int] with 
TcamMan 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI76BADPARAM: PcpSpdCreateSMap: cannot create SPD map [int] 
with invalid flags [hex] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI77BADPARAM: PcpManCreateSMap: cannot create SPD Map [int] 
using non-existent access list [int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI78OUTOFSMAP: PcpSpdCreateSMap: cannot create SPD map 
[int]: out of memory 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI79BADPARAM: PcpQOpActSaBegin: cannot activate Sa for 
cmeId=[dec], entry=[dec] when Cme is not ready 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI80QUEUEFULL: PcpManDestroyFlowAsync: cannot delete 
flowId [dec]: operation queue is full 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI81IDNOTINUSE: PcpQOpDelSaBegin: cannot delete already 
deleted flow [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI82QUEUEFULL: PcpManRemoveCme: cannot remove Cme with 
cmeId [int]: queue is full 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI83TMFAILED: PcpSpdInitialize: cannot insert SPD [int] 
with TcamMan 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI84BADPARAM: PcpManCreateSMap: cannot create SPD map [int] 
with spdId [int] out of range [0,[int]] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI85OUTOFSMAP: PcpManCreateSpd: cannot create SPD [int]: 
out of memory 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI86IDINUSE: PcpManActivateFlowAsync: cannot activate 
already active flow [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI87BADPARAM: PcpManCreateFlow: cannot create Flow with 
id=[dec], max is [dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI88IDNOTINUSE: PcpManRemoveSMap: cannot remove 
non-existing SMap [int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI89OUTOFCME: PcpSpdCreateCme: cannot allocate new Cme for 
aclId=[int] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ACEI92QUEUEFULL: PcpManCreateFlow: cannot create flowId 
[dec]: operation queue is full 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-ICPUBADGRESA: Invalid GRE SA - can't find match. saptr:[hex] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-3-SPI_NOT_AVAIL: SPI [hex] is not available 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPNSM-4

Error Message    %VPNSM-4-ACETCAMFULLINSMANSP: Full SA insertion for a manual SP. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ACETCAMPKTNOSA: Packet event for a non-existing SA. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ACETCAMPKTNOSP: Packet event for a non-existing SP. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ACEXCPUALLOC: IPC: Unable to allocate and send STATFLUSH. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ACEXCPUALLOC2: IPC: Unable to allocate IPC to set debug flag. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ACEXCPUALLOC3: IPC: Unable to allocate IPC to start 5840 test. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ACEXCPUCMMTU2: CFGMON: Failed to set MTU. Invalid data [dec], 
ifvlan [hex].

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ACEXCPUCMRESP: XcpuCfgMonReqCallback:Can't respond to host. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ACEXCPUCMRESP3: XcpuCfgMonReqCallback:Global stats...Can't 
respond to host. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ACEXCPUCMRESP4: XcpuCfgMonReqCallback: PerFlow 
Stats....Can't respond to host. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ACEXCPUCMRESP5: XcpuCfgMonReqCallback: PerFlow 
Stats....Can't respond to host. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-DUMPMEM: [hex]: [hex] [hex] [hex] [hex] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-EDSDEBUG: SingleBufErr:([hex]) 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-FIPSCHECK2: FIPS RCVD Multi-buffer Packet. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-FIPSCHECK3: FIPS Failed Packet Comparison. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-FIPSCHECK4: FIPS Test Completed Successfully. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ICPUFRAG1: PktReasmSetAction failed. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ICPUPP2: SaCheckSelectors: Illegal pkt, no valid SA 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ICPUPP3: Illegal pkt dst:[dec].[dec].[dec].[dec] proto:[dec] 
spi:[hex], no match on SA SPI [hex]. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ICPUPP4: Illegal pkt dst:[dec].[dec].[dec].[dec] proto:[dec] 
spi:[hex], no match on SA dst[dec].[dec].[dec].[dec] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ICPUPP8: Illegal clear pkt src:[dec].[dec].[dec].[dec] 
dst:[dec].[dec].[dec].[dec] proto:[dec]. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ICPUPP9: Packet src:[dec].[dec].[dec].[dec] 
dst:[dec].[dec].[dec].[dec] seq num:[hex] failed replay check last seq num:[hex] 
for SA:[hex]. 

Explanation    IPsec packets have failed the anti-replay check. A common cause is the use of QoS in your network. With QoS, lower priority packets can arrive late, missing the anti-replay check window. When this condition occurs, higher level protocols can request retransmission so that functionality is not lost. Time-sensitive protocols, such as voice traffic, might be degraded due to dropped or late packets.

Recommended Action    If anti-replay checking is not needed, disable it by removing the HMAC function from the transform set.

Error Message    %VPNSM-4-ICPUPP10: Packet src:[dec].[dec].[dec].[dec] 
dst:[dec].[dec].[dec].[dec] proto ESP, but not SA proto! 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ICPUPP11: Packet src:[dec].[dec].[dec].[dec] 
dst:[dec].[dec].[dec].[dec] proto AH, but not SA proto! 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ICPUPP12: IPPE says IPSec, not pkt 
src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec]! 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ICPUPP13: Policy check failed for pkt 
src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec] SA 
index:[hex] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ICPUPP14: Pkt src:[dec].[dec].[dec].[dec] 
dst:[dec].[dec].[dec].[dec] proto:[dec] match deny; SA index [hex] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ICPUPP15: SecInfo [hex] doesn't match with SA [hex] SA 
index:[hex] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ICPUPP16: Inner proto [dec] must be IPSec but is not 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ICPUSYSIPADDRADD: PktProcAddSysIpAddr: Unable to add local IP 
Addr [hex] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ICPUSYSIPADDRDEL: PktProcAddSysIpAddr: Unable to delete local 
IP Addr [hex] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-ISAUNCA7: PktProcAtnModSas: Mismatch valid flag unca:invalid 
index:[hex] 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-RECOVERYDONE: CP Lockup Recovery - Done 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-RECOVERYFRAG: Ipfrag: Unable to transmit. CP Lockup Occured. 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-RECOVERYSTART: CP Lockup Recovery - Start(OCPU) 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-4-XCPURECOVERY: Error Disabling CP 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPNSM-6

Error Message    %VPNSM-6-ACEPKAHWCRNGT: PKA: HW RNG has duplicate data, discarding 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-6-ACEPKARNGDUP: PKA: A pseudo-random number was generated twice 
in succession. [hex][hex]; 0Unrecognized format `x%p' 0Unrecognized format `x%p' 
idx:[hex] 

Explanation    An error has been reported by the firmware

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSM-6-ACEPKARNGKAT: PKA: RNG failed KAT 

Explanation    An error has been reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPNSMIOS Messages

This section contains VPNSM crypto connection (VPNSMIOS) messages.

VPNSMIOS-3

Error Message    %VPNSMIOS-3-ILLEGALINTERFACE: Traffic matching crypto maps on [chars] 
will go through unencrypted. Please reconfigure crypto maps as required by VPN 
service module. 

Explanation    An attempt was made to apply an encryption (crypto) map set to an interface that is not a VLAN interface. When this IPsec VPN accelerator is being used, crypto map sets can only be applied to a VLAN interface that has a proper encryption (crypto) connection to a physical port. The interface has been disabled. For more information on crypto guidelines, consult the system configuration manuals.

Recommended Action    Remove the crypto map set from the virtual interface. For more details, consult the configuration guidelines.

Error Message    %VPNSMIOS-3-MACEDONCTVLALLOCFAIL: Failed to allocate Control vlan on 
stby 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONCTVLTIMERON: Control vlan timer is on on stby 

Explanation    An internal error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONNOCCONB2BERR: [chars]no crypto connect is 
disallowed 

Explanation    The system cannot remove the cryptographic connection when a module-to-module partner is still active.

Recommended Action    Remove the module-to-module configuration before removing the cryptographic connection.

Error Message    %VPNSMIOS-3-MACEDONTUNNELADDCBERR: [chars]: tunnel addcb failed: 
reason[[chars]] tvlan[[dec]] slot[[chars]] 

Explanation    An error response was received when attempting to seize the tunnel. In a virtual switch system (VSS), slot [[chars]] indicates switch/slot/subslot; otherwise it indicates slot/subslot.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONTUNNELADDERR: [chars]: tunnel add failed: 
reason[[chars]] ifvlan[[dec]] tvlan[[dec]] slot[[chars]] src[[IP_address]] 
dst[[IP_address]] 

Explanation    An attempt to seize the tunnel has failed. In a virtual switch system (VSS), slot [[chars]] indicates switch/slot/subslot; otherwise it indicates slot/subslot.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONTUNNELCREATEPOLOQERR: Failed to create 
PoloReplicateCfg Q 

Explanation    An internal error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONTUNNELCREATEPROCERR: Failed to create Ace Tunnel 
Task 

Explanation    An internal error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONTUNNELCREATEQERR: Failed to create watched Q 

Explanation    An internal error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONTUNNELCREATETIDERR: Failed to create Ace Tunnel-id 
bitvector 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONTUNNELDELETEIFVLANNOTFOUNDERR: [chars]: no tm 
found while attempting to delete from ifvlan[[dec]] 

Explanation    An internal error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONTUNNELDELETETMNOTFOUNDERR: [chars]: no tm found 
while attempting to delete 

Explanation    An internal error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONTUNNELNOEVENTMSGHANDLERERR: msgtype[[chars]]: No 
event msg handler found. 

Explanation    An internal error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONTUNNELNOIDBERR: No tunnel idb 

Explanation    An internal error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONTUNNELNOTMMSGHANDLERERR: msgtype[[chars]]: No tm 
msg handler found. 

Explanation    An internal error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONTUNNELREMOVECBERR: [chars]: tunnel removecb 
failed: reason[[chars]] tvlan[[dec]] slot[[chars]] 

Explanation    An error response was received when attempting to release the tunnel. In a virtual switch system (VSS), slot [[chars]] indicates switch/slot/subslot; otherwise it indicates slot/subslot.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONTUNNELREMOVEERR: [chars]: tunnel remove failed: 
reason[[chars]] ifvlan[[dec]] tvlan[[dec]] slot[[chars]] src[[IP_address]] 
dst[[IP_address]] id[[dec]] 

Explanation    An attempt to release the tunnel has failed. In a virtual switch system (VSS), slot [[chars]] indicates switch/slot/subslot; otherwise it indicates slot/subslot.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONTUNNELVACLERR: vlan[[dec]]: failed to set vacl: 
action[[dec]] reason[[dec]] 

Explanation    An internal error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONTUNNELVLANERR: [chars]: allocated idb has invalid 
vlan id 

Explanation    An internal error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-MACEDONTUNNELVLANIDBERR: [chars]: unable to allocate idb 

Explanation    An internal error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSMIOS-3-SLOTMISMATCH: [chars] has mismatch crypto engine binding. 
Egress interface is binded to crypto engine [int]/[int] but tunnel protection is 
binded to [int]/[int]. This tunnel is now shutdown. 

Explanation    To use VPN-SM for tunnel protection, the user must enter the crypto engine slot slot command on both the egress interface VLAN and the tunnel interface. The slot on both interfaces must match. When this requirement is not met, this message is displayed. The tunnel is now shut down.

Recommended Action    Modify either one or both crypto engine slot values so that they match.

Error Message    %VPNSMIOS-3-VLANALLOCFAIL: Failed to allocate vlan for %s 

Explanation    The system was unable to allocate a VLAN for internal use.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show platform hardware capacity vlan, and show vlan internal usage commands and your pertinent troubleshooting logs.

VPNSMIOS-4

Error Message    %VPNSMIOS-4-DIFFCRYPTOENGINE: [chars]. Another interface [chars] has 
same local-address [chars] but is on a different crypto engine [chars] 

Explanation    Two crypto interfaces with the same local address must be on the same crypto engine. In a virtual switch system (VSS), crypto engine [chars] indicates switch/slot/subslot; otherwise it indicates slot/subslot.

Recommended Action    Reconfigure the crypto engine command on the interface.

Error Message    %VPNSMIOS-4-LIMITFVRF: System has reached the limit of supported 
front-door VRF. ([dec]) 

Explanation    The number of front-door VRFs supported by VPNSM has reached its limit.

Recommended Action    Unconfigure any unused VRFs.

Error Message    %VPNSMIOS-4-PROMISCOUSMODE: Outside port failed to be in [chars] mode 

Explanation    This message is relevant only if the outside port is an FEPA port.

Recommended Action    Reconfigure the crypto connect command.

Error Message    %VPNSMIOS-4-VPNSMILLEGALQOS0: VPNSM Slot: [dec] can only support [dec] 
cos maps in high priority queue, CoS configuration ignored, reset cos map by 
issuing no priority queue cos-map 1 command 

Explanation    An illegal configuration has been detected.

Recommended Action    Reset the CoS map by entering the no priority-queue cos-map 1 command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPNSMIOSSP Messages

This section contains VPN service module (VPNSM) crypto connection SP messages.

Error Message    %VPNSMIOSSP-6-MACEDONPOWEROFF: Non crypto image detected, disallowing 
power to VPN-SM module in slot [chars]. 

Explanation    The chassis was booted up with an image that does not have the necessary crypto subsystems for the VPN-SM to run correctly. In a virtual switch system (VSS), slot [[chars]] indicates switch/slot/subslot; otherwise it indicates slot/subslot.

Recommended Action    Contact your Cisco technical support representative to obtain the correct image. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPNSPA Messages

This section contains Virtual Private Network shared port adapter (VPNSPA) messages.

VPNSPA-0

Error Message    %VPNSPA-0-ACELOGTEST7: Log test: SEV_EMERG 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPNSPA-1

Error Message    %VPNSPA-1-ACELOGTEST6: Log test: SEV_ALERT 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPNSPA-2

Error Message    %VPNSPA-2-ACEIKEADRVPKRM: Decode of RSA Private Key %d failed 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-2-ACEIKEANVRWRT: RSA Private Key %d NOT written to NVRAM 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-2-ACEIKEANVWRT: RSA Private Key %d NOT zeroized in NVRAM 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-2-ACEIKEANVWRT2: RSA Private Key %d NOT written to NVRAM 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-2-ACEIKEAPRVCREDRV: Driver refused RSA Private Key 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-2-ACEIKEAPRVCRESES: Driver refused RSA Private Key %d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-2-ACEIKEAPRVDRV: Driver refused RSA Private Key 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-2-ACEIKEAPRVNVRD: RSA Private Key %d NOT read from NVRAM 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-2-ACEIKEAPRVREJ: RSA Private Key %d NOT written to NVRAM 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-2-ACEIKEAPRVRMDRV: Decode of RSA Private Key %d failed 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-2-ACEIKEAPRVRMSESDRV: Decode of RSA Private Key %d failed 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-2-ACELOGTEST5: Log test: SEV_CRIT 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-2-ACENVRAMCSUM: NVRAM Checksum failed 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-2-ACENVRAMWR: Write to nvram failed 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-2-ACE_PKA_KAT_FAILURE: PKA: Known Answer Test failure: %s 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPNSPA-3

Error Message    %VPNSPA-3-ACEI0BADPARAM: PcpManCreateTunn: cannot create tunnel with 
expiring Sa 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI0TCAMFAILED: SpdSpInstall: cannot install Sp %ld: 
TmInsertSp failed 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI10OUTOFCME: PcpManCreateAcl: cannot allocate new Acl for 
aclId=%u 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI11NESTOVERFLOW: SpdSaAddTmInsCb: cannot have more than 
%ld pending nested callbacks from TcamMan 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI11OUTOFSEL: PcpAclGetSpSelSet: cannot clone SelSet for 
ACL %d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI12IDNOTINUSE: PcpManRemoveAcl: cannot remove 
non-existing access list %u 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI12OUTOFSAPAR: SpdSaSetKeys: cannot allocate new SaPar 
for Sa %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI13IDINUSE: PcpManRemoveAcl: cannot remove access list %u 
while in use 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI14BADCMEID: PcpSpdCreateCme: cannot create Cme with 
ID=%ld: too large 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI14NOLOGA: SpdSaSetParams: cannot allocate SPI with 
TcamMan for Sa %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI15IDNOTINUSE: PcpManRemoveCme: cannot remove 
non-existing Cme %u 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI16BADPARAM: PcpManActivateFlowAsync: cannot activate 
flow %ld: Sa is in the wrong state 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI16TCAMFAILED: SpdSaTmInstallIn: cannot install inbound 
Sa %ld with TcamMan 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI17BADPARAM: PcpManActivateFlowAsync: cannot activate 
non-existing flow %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI17TCAMFAILED: SpdSaTmInstallOut: cannot install 
outbound Sa %ld with TcamMan 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI18BADPARAM: PcpManCreateSMap: cannot create outbound SPD 
Map %u with ingress access list %u 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI19BADCMEID: PcpManActivateFlowAsync: cannot activate 
flow %ld with non-existing Cme %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI1BADPARAM: SpdSpInstall: cannot install generic SP %d 
with non-zero priority 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI1OUTOFSA: PcpQOpCreSaBegin: cannot create new Sa using 
SpdMan 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI20OUTOFSEL: PcpUtilSelSetFromPar: cannot allocate new 
selector set 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI21BADPARAM: PcpAclAppend: got too many denys for 
aclId=%d, max is %d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI22BADPARAM: PcpAclAppend: got out-of-sequence line 
number %d for aclId=%d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI23IDINUSE: PcpSpdCreateCme: cannot create Cme with 
ID=%u: already used 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI24BADPARAM: PcpAclAppend: got invalid ranges for 
selector set at lineNo=%d, aclId=%d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI25IDINUSE: PcpAclAppend: got duplicate line number %d 
for aclId=%d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI26OUTOFSP: PcpCmeInstallNext: cannot create a new Sp 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI27BADPARAM: PcpManSetFlowKeys: cannot set keys for flow 
%ld: SA is in the wrong state 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI28IDINUSE: PcpQOpCreSaBegin: cannot create second Sa for 
flow %ld: conditions for transport adj. are not met 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI29SPDFAILED: PcpCmeInstallNext: cannot install Sp %d 
with SpdMan 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI2BADPARAM: PcpManUpdateFlow: cannot update flow %ld with 
invalid ID 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI2NESTOVERFLOW: SpdSaInitTmSaOut: outer outbound Sa %ld 
of Sa %ld is above nesting limit of %d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI30BADPARAM: PcpSpdUpdateCme: cannot update already 
queued Cme %u 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI31BADALENUM: PcpQOpActSaBegin: cannot find access list 
entry number %d for cmeId=%d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI32BADPARAM: PcpQOpActSaBegin: cannot delete old %sbound 
flow %ld while activating %sbound flow %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI33BADPARAM: PcpCmeActivateSa: got invalid lifetime 
values softSecs=%lu, hardSecs=%lu 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI34BADPARAM: PcpCmeActivateSa: got invalid lifetime 
values softKBytes=%lu, hardKBytes=%lu 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI35BADPARAM: PcpCmeIntersectSaWithSp: cannot activate 
flow %ld with selector ranges not intersecting parent Sp 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI36BADSELADDR: PcpQOpActSaBegin: cannot activate 
per-host flow %ld with addresses %d.%d.%d.%d and %d.%d.%d.%d not included in Sp 
%d selector sets 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI37OUTOFSEL: PcpQOpActSaBegin: cannot clone selector set 
to activate per-host flow %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI38BADSELADDR: PcpQOpActSaBegin: cannot activate 
transport mode flow %ld with addresses %d.%d.%d.%d and %d.%d.%d.%d not included 
in Sp's selector sets 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI39BADPARAM: PcpTrInProcess: got invalid opcode %d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI3NESTOVERFLOW: SpdSaGetXformSeq: outer inbound Sa %ld of 
Sa %ld is above nesting limit of %d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI3OUTOFSEL: PcpQOpActSaBegin: cannot allocate selector 
set for outer Sa in flowId %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI40BADACLID: PcpManCreateCme: cannot create Cme with 
non-existing access list %u 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI41SPDFAILED: PcpQOpSaActivated: cannot finish 
activating Sa %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI42QUEUEFULL: PcpCmeActivateSa: cannot activate Sa %ld: 
queue is full 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI43BADPARAM: PcpAclAppend: got invalid line number %d for 
ACL %d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI44QUEUEFULL: PcpSpdCreateCme: cannot create Cme %u 
(aclId=%u): queue is full 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI45IDNOTINUSE: PcpManDestroyFlowAsync: cannot delete 
already deleted flow %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI46BADPARAM: PcpQOpActSaBegin: cannot activate 
non-fully-specified Sa for Cme %d without Acl 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI47BADPARAM: PcpQOpActSaBegin: cannot activate Sa for 
manual Sp (cmeId=%d,entry=%d), Sa already exists 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI48CMEINUSE: PcpManSetInitMode: cannot set fast init-mode 
in TcamMan: %ld pending Ops, %ld Flows and %u Cmes already exist or TcamMan is busy 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI49BADPARAM: PcpManQueryFlow: cannot query flow %ld: Sa 
is not active 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI4BADPARAM: PcpQOpCreSaBegin: got invalid addresses 
%u.%u.%u.%u and %u.%u.%u.%u for other Sa of flow %ld: expected %u.%u.%u.%u and 
%u.%u.%u.%u 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI50CMEINUSE: PcpQOpRemCmeBegin: cannot remove Cme %ld: 
TcamMan is in Init mode 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI51BADPARAM: PcpSpdCreateCme: got invalid flags 
(manual,dynamic,discover,drop,clear) = (%d,%d,%d,%d,%d), cmeId=%d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI52IDINUSE: PcpManCreateAcl: cannot process opcode %u for 
Acl %u in state %u 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI53BADPARAM: PcpManCreateAcl: cannot create Acl with id 
%u out of range [0,%u] 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI54CMENOTREADY: PcpSpdCreateCme: cannot create Cme %u 
with Acl %u when Acl state is %u 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI55SPDFAILED: PcpQOpActSaBegin: cannot begin activating 
Sa %ld for flowId %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI56IDNOTINUSE: PcpManDestroyFlowAsync: cannot delete 
flow %ld already being deleted 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI57CMEINUSE: PcpManSetInitMode: cannot set normal 
init-mode in TcamMan: there are pending Flows or Cmes 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI58BADPARAM: PcpManQueryFlow: cannot query flow %ld: 
parent SP is not active 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI59BADPARAM: PcpCmeActivateSa: cannot activate flow %ld 
as per-host with subset of Sp as a selector set 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI5BADPARAM: SpdSaActivate: cannot activate Sa %ld, old Sa 
%ld already has successor Sa %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI5OUTOFSA: PcpQOpCreSaBegin: cannot create new Sa for 
flow %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI60SPDFAILED: PcpManSaUpdateError: cannot update Flow %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI61BADPARAM: PcpQOpActSaBegin: cannot activate Sa for 
cmeId=%d, entry=%d with bad spdId=%ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI62IDINUSE: PcpQOpCreSaBegin: cannot setup Flow %ld in 
trans.adj. with outer SA in tunnel mode 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI63CMEINUSE: PcpManActivateFlowAsync: cannot activate 
flow %ld while using fast policy mode 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI64BADPARAM: PcpQOpActSaBegin: got invalid ranges for 
selector set of fully-specified flow %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI65BADPARAM: PcpManSetInitMode: got invalid flags 0x%x 
for setting fast policy mode 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI66NOTREADY: PcpManUpdateFlow: cannot update flow %ld 
when SA is not active 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI67BADPARAM: PcpSpdCreateSMap: cannot create SMap %u with 
Acl %u when Acl state is %u 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI68BADPARAM: PcpAclAppend: got invalid flags 0x%x at 
lineNo=%d, aclId=%d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI69BADPARAM: PcpManCreateCme: cannot create Cme %u with 
spdId %u out of range [0,%u] 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI6BADPARAM: PcpTrInProcess: got invalid size %d for 
opcode %d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI6OUTOFSEL: SpdSpInstall: cannot compute SP's 
permit-SelSets from mixed SelSet list 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI70IDNOTINUSE: PcpManUpdateCme: cannot update 
non-existing Cme %u 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI71QUEUEFULL: PcpSpdUpdateCme: cannot update Cme %u: 
queue is full 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI72QUEUEFULL: PcpSpdCreateSMap: cannot create SPD map 
with mapId %u: queue is full 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI73BADPARAM: PcpSpdCreateSMap: cannot create SPD map with 
mapId %u out of range [0,%u] 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI74IDINUSE: PcpSpdCreateSMap: cannot create SPD map with 
mapId %u already in use 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI75TMFAILED: PcpSMapInstall: cannot insert SMap %u with 
TcamMan 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI76BADPARAM: PcpSpdCreateSMap: cannot create SPD map %u 
with invalid flags 0x%x 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI77BADPARAM: PcpManCreateSMap: cannot create SPD Map %u 
using non-existent access list %u 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI78OUTOFSMAP: PcpSpdCreateSMap: cannot create SPD map %u: 
out of memory 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI79BADPARAM: PcpQOpActSaBegin: cannot activate Sa for 
cmeId=%d, entry=%d when Cme is not ready 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI7BADPARAM: PcpManSetFlowKeys: cannot set keys for flow 
%ld: invalid ID 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI7OUTOFSEL: SpdSaTmInstallOut: cannot compute outbound 
SA's permit-SelSets from mixed SelSet list 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI80QUEUEFULL: PcpManDestroyFlowAsync: cannot delete 
flowId %ld: operation queue is full 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI81IDNOTINUSE: PcpQOpDelSaBegin: cannot delete already 
deleted flow %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI82QUEUEFULL: PcpManRemoveCme: cannot remove Cme with 
cmeId %u: queue is full 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI83TMFAILED: PcpSpdInitialize: cannot insert SPD %lu with 
TcamMan 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI84BADPARAM: PcpManCreateSMap: cannot create SPD map %u 
with spdId %u out of range [0,%u] 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI85OUTOFSMAP: PcpManCreateSpd: cannot create SPD %u: out 
of memory 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI86IDINUSE: PcpManActivateFlowAsync: cannot activate 
already active flow %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI87BADPARAM: PcpManCreateFlow: cannot create Flow with 
id=%ld, max is %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI88IDNOTINUSE: PcpManRemoveSMap: cannot remove 
non-existing SMap %u 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI89OUTOFCME: PcpSpdCreateCme: cannot allocate new Cme for 
aclId=%u 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI8SPDFAILED: PcpManSetFlowKeys: cannot set keys for flow 
%ld using SpdMan 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI90CMEINUSE: PcpQOpRemCmeBegin: cannot remove Cme %ld 
while in state %d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI91OUTOFSEL: PcpAclGetSpSelSet: cannot clone 
deny-SelSets for ACL %d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI92QUEUEFULL: PcpManCreateFlow: cannot create flowId %ld: 
operation queue is full 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI93OUTOFSEL: PcpCmeIntersectSaWithSp: cannot clone deny 
selectors for flow %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI9BADPARAM: PcpManQueryFlow: cannot query flow %ld: 
invalid ID 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEI9OUTOFSEL: SpdSaActivateOuterSa: cannot create selector 
set 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACELOGTEST4: Log test: SEV_ERR 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEPKARSAPRVXCR: PKA: PkaRsaPrivXcrypt() invalid input 
buffer length %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEPKARSAPUBXCRBUFLEN: PKA: PkaRsaPubXcrypt() invalid input 
buffer length %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEPKASK0LENCROP2: PKA: 0 length crypto operation 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEPKASK0LENCRYOP3: PKA: 0 length crypto operation 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEPKASK0LENOP: PKA: 0 length crypto operation 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEPKASK1STFRAGSHRT: PKA: 1st frag too short for crypto 
operation 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEPKASKDESNOTMUL82: PKA: DES/3DES data length not multiple 
of 8 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEPKASKDESNOTMULT8: PKA: DES/3DES data length not multiple 
of 8 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ACEPKASKNOCRNOAUTH: PKA: Can't have PKA_CRYPTO_NONE and 
PKA_HMAC_NONE 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ICPUBADGRESA: Invalid GRE SA - can't find match. saptr:0x%x 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-ICPUPP22: ICMP received, let it go clear newId %d oldid %d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-3-SPI_NOT_AVAIL: SPI 0x%x is not available 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPNSPA-4

Error Message    %VPNSPA-4-ACEIPCMPINGPRE: IPC ping (%s): premature ping...awaiting 
response to previous ping 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACEIPCMPINGSEQ: IPC ping (%cCPU): seq.# does not match: 
Expected %d, got %d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACEIPCMPINGSKIP: IPC ping (%cCPU): Skipped %d times before 
receiving reply 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACEIPCXNOBUF2: ICPU unable to allocate msg buf for Ping 
Reply: %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACEIPCXNOBUF3: OCPU unable to allocate msg buf for Ping 
Reply: %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACEIPCXPINGNOBUF: %d srcCPU unable to allocate msg buf for 
Ping Reply in CB: %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACELOGTEST3: Log test: SEV_WARN 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACEPKADHRMKGIDBUSY: PkaDhRemoveKeyGroup(): DH group ID %d is 
busy 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACETCAMFULLINSMANSP: Full SA insertion for a manual SP. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACETCAMPKTNOSA: IPC payload : %x 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACETCAMPKTNOSP: Packet event for a non-existing SP. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACETCAMPKTNOSP1: EarlyPkt Exit1. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACETCAMPKTNOSP2: EarlyPkt Exit2. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACETCAMPKTNOSP3: EarlyPkt Exit3. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACEXCPUALLOC: IPC: Unable to allocate and send STATFLUSH. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACEXCPUALLOC2: IPC: Unable to allocate IPC to set debug flag. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACEXCPUALLOC3: IPC: Unable to allocate IPC to start 5840 
test. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACEXCPUCMRESP3: XcpuCfgMonReqCallback:Global stats...Can't 
respond to host. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACEXCPUCMRESP4: XcpuCfgMonReqCallback: DataPath 
Stats....Can't respond to host. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACEXCPUCMRESP5: XcpuCfgMonReqCallback: PerFlow 
Stats....Can't respond to host. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ANTIREPLAYWINDOWDEFAULT: Using default replay window for SA 
SPI 0x%x 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-BULKIP: Wrong type %d size:5d. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-DUMPMEM: 0x%08x: 0x%08x 0x%08x 0x%08x 0x%08x 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-EDSDEBUG: Already in map: map[0x%x] newid0x%x flags:0x%x 
mtu:0x%x spdid:0x%x 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-FIPSCHECK2: FIPS RCVD Multi-buffer Packet. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-FIPSCHECK3: FIPS Failed Packet Comparison. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-FIPSCHECK4: FIPS Test Completed Successfully. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ICPUFRAG1: PktReasmSetAction failed. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ICPUPP10: Packet src:%d.%d.%d.%d dst:%d.%d.%d.%d proto ESP, 
but not SA proto! 

Explanation    The received packet's protocol does not match the security association (SA) protocol. The SA expects Authentication Header (AH), but the packet uses Encapsulating Security Payload (ESP).

Recommended Action    Check whether the negotiated protocol matches the configured transform sets of both peers.

Error Message    %VPNSPA-4-ICPUPP11: Packet src:%d.%d.%d.%d dst:%d.%d.%d.%d proto AH, 
but not SA proto! 

Explanation    The received packet's protocol does not match the SA protocol. The SA expects ESP, but the packet uses AH.

Recommended Action    Check whether the negotiated protocol matches the configured transform sets of both peers.

Error Message    %VPNSPA-4-ICPUPP12: IPPE says IPSec, not pkt src:%d.%d.%d.%d 
dst:%d.%d.%d.%d proto:%d! 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ICPUPP13: Policy check failed for pkt src:%d.%d.%d.%d 
dst:%d.%d.%d.%d proto:%d SA index:0x%x 

Explanation    The decrypted packet does not match the security policy.

Recommended Action    Check whether the security policy on both peers is symmetric.

Error Message    %VPNSPA-4-ICPUPP14: Pkt src:%d.%d.%d.%d dst:%d.%d.%d.%d proto:%d match 
deny; SA index 0x%x 

Explanation    Encrypted packets were received that should have been unencrypted.

Recommended Action    Check whether the security policy on both peers is symmetric.

Error Message    %VPNSPA-4-ICPUPP15: SecInfo 0x%x doesn't match with SA 0x%x SA 
index:0x%x 

Explanation    An unexpected and unsupported nesting of SA was detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ICPUPP16: Inner proto %d must be IPSec but is not 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ICPUPP2: SaCheckSelectors: Illegal pkt, no valid SA 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ICPUPP3: Illegal pkt dst:%d.%d.%d.%d proto:%d spi:0x%x, no 
match on SA SPI 0x%x. 

Explanation    No matching SA was found for the received encrypted packet. This message is most likely to occur during rekeying when the inbound SA is not yet established.

Recommended Action    If the message persists and packets are being lost, check whether the CPU is overloaded or the crypto engine is oversubscribed.

Error Message    %VPNSPA-4-ICPUPP4: Illegal pkt dst:%d.%d.%d.%d proto:%d spi:0x%x, no 
match on SA dst%d.%d.%d.%d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ICPUPP8: Illegal clear pkt src:%d.%d.%d.%d dst:%d.%d.%d.%d 
proto:%d. 

Explanation    Clear packets were received that should have been encrypted.

Recommended Action    Check whether the remote peer has a correct security policy and SA to encrypt the packets.

Error Message    %VPNSPA-4-ICPUPP9: Packet src:%d.%d.%d.%d dst:%d.%d.%d.%d seq num:0x%x 
failed replay check last seq num:0x%x for SA:0x%x. 

Explanation    IPsec packets have failed the anti-replay check. A common cause is the use of QoS in your network. With QoS, lower priority packets can arrive late, missing the anti-replay check window. When this condition occurs, higher level protocols can request retransmission so that functionality is not lost. Time-sensitive protocols, such as voice traffic, might be degraded due to dropped or late packets.

Recommended Action    Increase the anti-replay window size. If anti-replay checking is not needed, disable it by removing the HMAC function from the transform set.

Error Message    %VPNSPA-4-ICPUSYSIPADDRADD: PktProcAddSysIpAddr: Unable to delete sys 
IP Addr %d.%d.%d.%d 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ISAUNCA7: PktProcAtnModSas: Mismatch valid flag unca:invalid 
index:0x%x 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-RECOVERYFRAG: Ipfrag: Unable to transmit. CP Lockup Occured. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-SINGLEIP: Wrong type %d size:%d. 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-SPDID: XcpuSetVlanSpdId: IpcAllocFailed 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-XCPURECOVERY: Error Disabling EDDE EITD DMA 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPNSPA-5

Error Message    %VPNSPA-5-ACELOGTEST2: Log test: SEV_NOTICE 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-4-ACEPKADHGRPNTALC: PkaDhRemoveKeyGroup(): DH group ID %d not 
allocated 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKADHGSBADID: PkaDhGenerateSession(): DH group ID %d not 
defined 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKADHGSHIDNOALL: PkaDhGenerateShared:DH session ID %d not 
allocated 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKADHGSIDINUSE: PKA: PkaDhGenerateSessionInt: DH session 
id %ld already in use 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKADHGSINVID: PKA: PkaDhGenerateSessionInt: invalid DH 
session id %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKAINITCMPL: BCM5820: Initialization complete 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKANOBDESC: PKA: no data buffer descriptors available 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKANOMOREDHGRPS: PKA: no more DH groups available 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKAPOSTRSTDELAY: PKA: BCM5820 post reset delay 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKARESUB: BCM5820: Resubmitting crypto request 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKARESUBPK: BCM5820: Resubmitting PK request 0x%x 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKARSACKBITSNMULT: PKA: RSA key create request of %d bits 
not a multiple of 64 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKARSACKMAXBITS: PKA: RSA key create request of %d bits 
exceeds max of %d bits 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKARSACKTOOMANY: PKA: Too many RSA key create requests 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKARSARMPSBUSYID: PKA: can't remove busy RSA private 
session %ld 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKARST: PKA: BCM5820 in reset 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-5-ACEPKARSTCOMPL: BCM5820: Reset complete 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPNSPA-6

Error Message    %VPNSPA-6-ACEIPCSENDMSGLOCAL: %s send msg buf (local) 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-6-ACEIPCSENDMSGTOOBIG: %s unable to send msg buf (msg too big) 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-6-ACEIPCSENDMSGTOOMANYCLIENTS: %s unable to send msg buf 
(client id too big) 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-6-ACELOGTEST1: Log test: SEV_INFO 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-6-ACEPKAHWCRNGT: PKA: HW RNG has duplicate data, discarding 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-6-ACEPKAPKNOMCR2: PKA: no Public Key MCRs available 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-6-ACEPKARNG: PKA: seed key is same as the seed, discarding 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-6-ACEPKARNGDUP: PKA: A pseudo-random number was generated 
twice in succession. 0x%.8lx%.8lx; 0x%p 0x%p idx:0x%x 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-6-ACEPKARNGKAT: PKA: RNG failed KAT 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-6-ACEPKASKNOCRYCTXT: PKA: no Crypto CTXs available 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-6-ACEPKASKNOMCRS: PKA: no Crypto MCRs available 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VPNSPA-7

Error Message    %VPNSPA-7-ACELOGTEST0: Log test: SEV_DEBUG 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-7-ACELOGTESTA: Log test: SEV_DEBUG A 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-7-ACELOGTESTB: Log test: SEV_DEBUG B %d %s 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-7-ACESHI: git along %d %s 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VPNSPA-7-ACESLO: nuf said 

Explanation    An error was reported by the firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VRRP Messages

This section contains Virtual Router Redundancy Protocol (VRRP) messages.

VRRP-4

Error Message    %VRRP-4-BADAUTH: Bad authentication from %i, group %d, type %d 

Explanation    Two routers participating in Virtual Router Redundancy Protocol (VRRP) disagree on authentication.

Recommended Action    Enter the vrrp authentication command to repair the VRRP authentication discrepancy between the local system and the system whose IP address is reported.

Error Message    %VRRP-4-BADAUTHTYPE: Bad authentication from %i, group %d, type %d, 
expected %d 

Explanation    Two routers participating in VRRP disagree on the valid authentication type.

Recommended Action    Enter the vrrp authentication command to repair the VRRP authentication discrepancy between the local system and the system whose IP address is reported.

VSDA Messages

This section contains virtual switch dual-active (VSDA) messages.

VSDA-3

Error Message    %VSDA-3-ADD_LTL_INDEX_AND_FPOE: Unable to add LTL index 0x%04x and 
program fpoe for %u/%u 

Explanation    An internal error occurred.

Recommended Action    No action is required.

Error Message    %VSDA-3-GET_IDB_FAILED: Failed to get idb for port cookie (linkchange) 

Explanation    An internal error occurred.

Recommended Action    No action is required.

Error Message    %VSDA-3-ICC_ERR: %s 

Explanation    A failure occurred during the intercard communications (ICC) operation.

Recommended Action    No action is required.

Error Message    %VSDA-3-INVALID_PROC_EVENT: Got event %d:%d 

Explanation    The process was awakened with an invalid event.

Recommended Action    No action is required.

Error Message    %VSDA-3-INVALID_TIMER: Invalid timer %d for interface %s 

Explanation    A timer event occurred, but the timer type was invalid.

Recommended Action    No action is required.

Error Message    %VSDA-3-INVALID_TIMER_TYPE: Invalid timer %d processed in %s 

Explanation    A timer event occurred, but the timer type was invalid.

Recommended Action    No action is required.

Error Message    %VSDA-3-LINK_DOWN: Interface %s is no longer dual-active detection 
capable 

Explanation    The specified link is no longer capable of detecting dual-active situations.

Recommended Action    No action is required.

Error Message    %VSDA-3-PKT_CREATE: Can't create packet: %s 

Explanation    A dual-active packet cannot be created due to the reason described.

Recommended Action    No action is required.

Error Message    %VSDA-3-PKT_RX: Can't process the received packet: %s 

Explanation    A dual-active packet cannot be processed due to the reason described.

Recommended Action    No action is required.

Error Message    %VSDA-3-PKT_TX: Can't send packet: %s 

Explanation    A dual-active packet cannot be sent due to the reason described.

Recommended Action    No action is required.

Error Message    %VSDA-3-PROC_CREATE_FAILED: Unable to create process 

Explanation    The specified process could not be created.

Recommended Action    No action is required.

Error Message    %VSDA-3-QUEUE_CREATE_FAILED: Unable to create watched queue 

Explanation    The specified watched queue could not be created.

Recommended Action    No action is required.

Error Message    %VSDA-3-SET_PORT_LTL_INDEX: Unable to set LTL index for port %s to 0x%x 

Explanation    An internal error occurred

Recommended Action    No action is required.

Error Message    %VSDA-3-TIMER_NULL_INTFC: NULL context for timer %d in %s 

Explanation    A timer event occurred, but it specified a NULL interface.

Recommended Action    No action is required.

Error Message    %VSDA-3-TIMER_STARTED: Timer %u on interface %s started 

Explanation    The specified link is now capable of detecting dual-active situations.

Recommended Action    No action is required.

Error Message    %VSDA-3-TX_THREAD_FAILURE: Thread %u: %s 

Explanation    This is a general thread error message.

Recommended Action    No action is required.

Error Message    %VSDA-3-VSDA_SCP_BAD_STATUS: SCP operation ([chars]) return status 
[dec] 

Explanation    A non-blocking SCP operation of the specified type failed for dual-active fast-hello on a line card

Recommended Action    No action is required.

Error Message    %VSDA-3-VSDA_SCP_PAK_FAIL: Unable to get SCP packet for opcode [dec], 
operation [dec] 

Explanation    Packet allocation failed for sending an SCP message to do the specified operation

Recommended Action    No action is required.

Error Message    %VSDA-3-VSDA_SCP_SEND_FAIL: Unable to send SCP message for opcode 
[dec], operation subop [dec] 

Explanation    Packet send failed for the SCP message to perform the specified operation

Recommended Action    No action is required.

VSDA-5

Error Message    %VSDA-5-LINK_UP: Interface %s is now dual-active detection capable 

Explanation    The specified link is now capable of detecting dual-active situations.

Recommended Action    No action is required.

VSEC Messages

This section contains VLAN security violation messages.

VSEC-4

Error Message    %VSEC-4-VLANACCESSLOGRF: FAILED to set VACL-LOG rate limiter. Is 
strongly suggested to rate limit when using this feature 

Explanation    The configuration for the VACL logging rate limiter has failed.

Recommended Action    Determine the rate limiter usage, free some resources if possible, and then try to set the rate limiter again.

VS_GENERIC Messages

This section contains virtual switch (VS) messages.

VS_GENERIC-1

Error Message    %VS_GENERIC-1-VS_HA_PS_NOT_SUPPORTED: Chassis Standby is not supported 
in the current release. Forcing the chassis standby in switch [dec] slot [dec] to 
drop to rommon 

Explanation    The chassis standby function is not supported in this release.

Recommended Action    No action is required.

Error Message    %VS_GENERIC-1-VS_HA_PS_RUNNING_LEGACY_IMAGE: Chassis Standby in 
switch [dec] slot [dec] is running non Virtual Switch image. Please remove the 
chassis standby. 

Explanation    The standby chassis is running an image that does not support virtual switch.

Recommended Action    Remove the standby chassis.

VS_GENERIC-3

Error Message    %VS_GENERIC-3-VS_ADD_VSL_ENTRY_FAILED: Add VSL configured port for 
vslot [int] port [int] failed. Exceed port member count limit. 

Explanation    An attempt to add an entry for (vslot, port) to the VSL configured port list failed because the port member count limit was exceeded.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VS_GENERIC-3-VS_BOOLEAN_CREATE_FAILED: Unable to create watched 
boolean "[chars]" 

Explanation    The creation of the specified watched boolean failed.

Recommended Action    No action is required.

Error Message    %VS_GENERIC-3-VS_ENQUEUE_FAILED: Unable to enqueue to [chars] queue 

Explanation    An internal error occurred that prevented a message from being enqueued to the specified process. The packet was dropped.

Recommended Action    No action is required.

Error Message    %VS_GENERIC-3-VS_ICC_PAK_FAIL: Unable to get ICC packet for opcode 
[dec], operation [dec] 

Explanation    A packet allocation failed for sending an ICC message to do the specified operation.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VS_GENERIC-3-VS_ICC_RESP_PAK_NULL: Failed to obtain response packet 

Explanation    The response packet pointer is NULL. This could be due to an insufficient memory condition on the response packet sending side or to a failure to get an IPC message on the receiving side.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VS_GENERIC-3-VS_NO_PAGP_CHANNEL_HWIDB: No PAgP channel hwidb for PAgP 
group [dec] 

Explanation    An internal error occurred. Port Aggregation Protocol (PAgP) could not find the hardware interface descriptor block (IDB) for this channel group.

Recommended Action    No action is required.

Error Message    %VS_GENERIC-3-VS_PROC_CREATE_FAILED: Unable to create process 
"[chars]" 

Explanation    The creation of the specified process failed.

Recommended Action    No action is required.

Error Message    %VS_GENERIC-3-VS_QUEUE_CREATE_FAILED: Unable to create queue "[chars]" 

Explanation    The creation of the specified queue failed.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_PROC_ARGS_FAILED: Unable to process arguments "[chars]" 

Explanation    The processing of the specified arguments failed.

Recommended Action    No action is required.

VS_GENERIC-5

Error Message    %VS_GENERIC-5-VS_CONFIG_DIRTY: Configuration has changed. [chars] 

Explanation    An attempt to reload was ignored due to a configuration change.

Recommended Action    No action is required.

VSL Messages

This section contains virtual switch link (VSL) messages.

VSL-2

Error Message    %VSL-2-VSL_STATUS: -======== VSL is [chars] ========- 

Explanation    The VSL status has changed to active (up) or inactive (down).

Recommended Action    No action is required.

VSL-3

Error Message    %VSL-3-PRE_PEER_COMM_TIMEOUT: A timeout occurred while waiting for 
vsl_pre_peer_comm_op_done 

Explanation    All applications failed to respond within the specified time. Operation is continuing.

Recommended Action    No action is required.

Error Message    %VSL-3-TROUBLESHOOT: Structure type [int]: [chars] 

Explanation    The specified structure could not be created to save VSL troubleshooting information when VSL goes down.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_ICC_PAK_FAIL: Unable to get ICC packet for opcode [dec], 
operation [dec] 

Explanation    Packet allocation failed for sending an ICC message to do the specified operation.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_ICC_SEND_FAIL: Unable to send ICC message for opcode [dec], 
operation subop [dec] 

Explanation    Packet send failed for the ICC message to perform the specified operation.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_INST_CREATE_FAIL: Failed to create VSLP instance for VSL 

Explanation    Unable to create a VSLP instance for VSL.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_INTERNAL_ERROR: [chars], port [dec]/[dec] 

Explanation    An internal error occurred.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_INVALID_PROC_EVENT: Got event [dec]:[dec] 

Explanation    An invalid event activated the process.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_INVALID_TIMER_CTXT: NULL or invalid timer context 

Explanation    A timer expiration event was received with NULL or invalid context information.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_INV_PORT_STATUS_CHANGE: Link status change ([chars]) on 
non-VSL port [dec]/[dec] 

Explanation    A link status change was detected on a port that is not a VSL member.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_MAX_PORTS: Cannot configure more than [dec] ports 

Explanation    A port could not be added to the VSL because the maximum number of ports in the VSL has been reached.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_MODE_BAD_STATUS: VSL-mode programming ([dec]) returned 
status [dec] 

Explanation    A VSL-mode operation of the specified type failed on a VSL line card.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_PORT_CFG_MOD_OFFLINE: Module [dec] offline when port [dec] 
added to VSL 

Explanation    A port was added to the VSL when the corresponding line card was offline.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_PROC_CREATE_FAILED: Unable to create process "[chars]" 

Explanation    The specified process could not be created for an unknown reason.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_REGISTRY_ADD_FAIL: [chars] registry addition failed 

Explanation    An addition to the given registry failed during initialization.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_RESERVED_LTL_FAIL: Unable to allocate reserved LTL indices 

Explanation    Platform-VSLP for VSL uses a number of reserved Local Target Logic (LTL) indices allocated by the LTL Manager. Because this allocation failed, the system can no longer function.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_ROLE_RES_BOOL_FAIL: Unable to create watched boolean for 
role resolution 

Explanation    A watched boolean for role resolution could not be created.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_SCP_BAD_STATUS: SCP operation ([chars]) return status [dec] 

Explanation    A nonblocking SCP operation of the specified type. failed on a VSL line card

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_SCP_BLK_SEND_FAIL: [chars] for SCP opcode [dec], subopcode 
[dec] 

Explanation    Failed to do the specified operation when sending the specified SCP message through a blocking call.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_SCP_FAIL: SCP operation failed 

Explanation    A nonblocking SCP operation failed on a VSL line card.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_SCP_PAK_FAIL: Unable to get SCP packet for opcode [dec], 
operation [dec] 

Explanation    Packet allocation failed for sending an SCP message to do the specified operation.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_SCP_SEND_FAIL: Unable to send SCP message for opcode [dec], 
operation subop [dec] 

Explanation    Packet send failed for the SCP message to perform the specified operation.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_UNCFG_BAD_PORT: Unconfigure on non-VSL port [dec]/[dec] 

Explanation    An attempt was made to unconfigure a port from the VSL, but the port is not part of the VSL.

Recommended Action    No action is required.

Error Message    %VSL-3-VSL_UNCFG_FAILED: Unconfigure on VSL port [dec]/[dec] failed: 
[chars] 

Explanation    While unconfiguring a VSL port, the specified operation failed.

Recommended Action    No action is required.

VSL-5

Error Message    %VSL-5-VSL_CNTRL_LINK: New VSL Control Link [chars] 

Explanation    A new VSL control link was detected on a VSL line card.

Recommended Action    No action is required.

VSL_BRINGUP Messages

This section contains virtual switch link (VSL) bringup messages.

VSL_BRINGUP-3

Error Message    %VSL_BRINGUP-3-MODULE_DOWN: Failed to bring up VSL module in slot [dec] 
switch [dec]. [chars] 

Explanation    The bringup of the specified module failed due to the reason indicated.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VSL_BRINGUP-3-NO_MODULE_UP: Failed to bring up any VSL modules on 
switch [dec] 

Explanation    An attempt to bring up any VSL line cards or supervisor engines failed due to an internal error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VSL_BRINGUP-3-PROC_CREATE_FAILED: Unable to create process "[chars]" 

Explanation    The creation of the specified process failed.

Recommended Action    No action is required.

Error Message    %VSL_BRINGUP-3-VS_OVERSUB_MODECHANGE_FAIL: Switching mode failed on 
Switch %d module %d port-group %d 

Explanation    The VSL bringup process was unable to change the switching mode of the indicated module.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VSL_BRINGUP-6

Error Message    %VSL_BRINGUP-6-MODULE_UP: VSL module in slot [dec] switch [dec] 
brought up 

Explanation    The specified VSL module was brought up successfully.

Recommended Action    No action is required.

Error Message    %VSL_BRINGUP-6-NOT_VS_CAPABLE_EARL: Supervisor card does not have 
Virtual Switch capable EARL daughter board 

Explanation    The supervisor engine card does not have an EARL daughterboard capable of running in virtual switch mode. An EARL 7.5 or above is required.

Recommended Action    Use a supported supervisor engine card for a virtual switch system.

Error Message    %VSL_BRINGUP-6-PREEMPT_DISABLED: Preemption suppressed due to first 
time VS conversion 

Explanation    A higher priority standby switch will not preempt a lower priority active switch when a virtual switch (VS) system is converted for the first time from a standalone configuration.

Recommended Action    Use the switch accept mode virtual command to merge the standby VSL configuration first. Then, if desired, use the redundancy force-switchover command to make the other switch active.

Error Message    %VSL_BRINGUP-6-SUP720_VS_NOT_SUPPORT: No support for Virtual Switch on 
SUP720. Booting up in Standalone mode 

Explanation    The Supervisor Engine 720 is virtual switch capable. However, Cisco does not officially support virtual switch mode on the Supervisor Engine 720.

Recommended Action    No action is required.

VSLP Messages

This section contains Virtual Switch Link Protocol (VSLP) messages.

VSLP-2

Error Message    %VSLP-2-VSL_DOWN: [chars] 

Explanation    VSL status changed to DOWN. More detail is provided in the message.

Recommended Action    No action is required.

VSLP-3

Error Message    %VSLP-3-ICC_ERR: [chars] 

Explanation    A failure occurred during the inter-card communications (ICC) operation.

Recommended Action    No action is required.

Error Message    %VSLP-3-ISSU_ERROR: %s 

Explanation    The virtual switch link protocol (VSLP) was unable to perform an ISSU operation.

Recommended Action    No action is required.

Error Message    %VSLP-3-PKT: VSLP packet error: [chars] 

Explanation    A VSLP packet error occurred for the reason described.

Recommended Action    No action is required.

Error Message    %VSLP-3-PKT_CREATE: Can't create packet: [chars] 

Explanation    A VSLP packet cannot be created due to the reason described.

Recommended Action    No action is required.

Error Message    %VSLP-3-PKT_RX: Can't process the received packet: [chars] 

Explanation    A VSLP packet cannot be processed due to the reason described.

Recommended Action    No action is required.

Error Message    %VSLP-3-PKT_TX: Can't send packet: [chars] 

Explanation    A VSLP packet cannot be sent due to the reason described.

Recommended Action    No action is required.

Error Message    %VSLP-3-REGISTRY_ADD_ERR: Failure in adding to [chars] registry 

Explanation    A function could not be added to the registry.

Recommended Action    No action is required.

Error Message    %VSLP-3-RRP_ERR_MSG: [chars] 

Explanation    The VSLP role resolution protocol detected an error.

Recommended Action    No action is required.

Error Message    %VSLP-3-RRP_INSTANCE_OUT_OF_BOUNDS: Instance value [dec] is outside 
the expected range 

Explanation    The instance value received is out of bounds.

Recommended Action    No action is required.

Error Message    %VSLP-3-RRP_INVALID_INSTANCE: Instance value [dec] is invalid 

Explanation    The instance value received corresponds to an invalid instance.

Recommended Action    No action is required.

Error Message    %VSLP-3-RRP_MEMORY_ALLOC_ERR: (Instance:[dec], Peer:[dec]): No memory 
available for [chars] 

Explanation    The VSLP could not obtain the requested memory.

Recommended Action    No action is required.

Error Message    %VSLP-3-RRP_PEER_INFO_ERR: (Instance:[dec], Peer:[dec]): Peer [chars] 

Explanation    The role resolution protocol has encountered an error associated with this peer.

Recommended Action    No action is required.

Error Message    %VSLP-3-RRP_PEER_INSTANCE_ERROR: (Instance:[dec], Peer:[dec], 
Up:[dec], Valid:[dec], Switch:[dec], Role:[chars], PeerRole:[chars]): [chars] 

Explanation    An error occurred pertaining to the instance and peer group specified.

Recommended Action    No action is required.

Error Message    %VSLP-3-RRP_PEER_SUP_PSLOT_ERR: 
save_rrp_tlv_data->peer_sup_pslot:[int], my_sup_pslot:[int] 

Explanation    The role resolution protocol detected a difference in the peer supervisor engine pslot.

Recommended Action    No action is required.

Error Message    %VSLP-3-RRP_RESERVED_PEER_ERR: (Instance:[dec], Peer:[dec]): Reserved 
peer [dec] [chars] 

Explanation    The role resolution protocol has detected an error related to the reserved peer.

Recommended Action    No action is required.

Error Message    %VSLP-3-RRP_SESSION_ID_ERR: (Instance:[dec], Peer:[dec]): Session id 
mismatch. Expected [dec], got [dec] 

Explanation    The VSLP role resolution protocol has detected a session ID mismatch.

Recommended Action    No action is required.

Error Message    %VSLP-3-RRP_SLOT_PORT_ERR: (Slot:[dec], Port:[dec]): [chars] 

Explanation    The role resolution protocol has detected an error related to the specified slot and port.

Recommended Action    No action is required.

Error Message    %VSLP-3-RRP_TIMER_CREATE_FAIL: (Instance:[dec], Peer:[dec]): Unable 
to create RRP timer 

Explanation    The role resolution protocol was unable to create a timer for the specified instance and peer.

Recommended Action    No action is required.

Error Message    %VSLP-3-RRP_UNEXPECTED_ROLE: Unexpected roles. Local role = [chars], 
Peer role = [chars] 

Explanation    The role resolution protocol has encountered inconsistent role information.

Recommended Action    No action is required.

Error Message    %VSLP-3-RRP_VALUE_ERR: [chars]: [dec] 

Explanation    The role resolution protocol has encountered an unknown value.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_BOOLEAN_CREATE_FAILED: Unable to create watched boolean 
"[chars]" 

Explanation    The specified watched boolean could not be created.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_INST_INVALID_CAP: Invalid capability [dec] for VSLP 
instance [dec] 

Explanation    A VSLP capability was requested that is beyond the current list of supported capabilities.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_INST_OUT_OF_RANGE_CREATE: Cannot create VSLP instance 
[dec] 

Explanation    A VSLP instance could not be created for the switch ID because it is not within the acceptable range.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_INST_OUT_OF_RANGE_DESTROY: Cannot destroy VSLP instance 
[dec] 

Explanation    The given VSLP instance could not be destroyed because it is not within the acceptable range.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_DOMAIN_MISMATCH: Domain ID in probe packet from peer 
%d is not the same as local Domain ID %d. The packet was dropped. 

Explanation    The virtual switch domain ID in a probe packet from the peer is not the same as the local domain ID. The packet was dropped.

Recommended Action    Investigate and correct this misconfiguration.

Error Message    %VSLP-3-VSLP_LMP_FAIL_REASON: [chars]: [chars] 

Explanation    This message displays the reason for a link to leave the LMP operational state.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_FLAG_SET: Incorrect flag value (0x%x) on port %d/%d 

Explanation    The system detected an unexpected value for the flag field of a VSL link. This condition is caused by an internal software error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show vslp lmp summary, and show vslp lmp fsm commands and your pertinent troubleshooting logs.

Error Message    %VSLP-3-VSLP_LMP_FSM_INVALID_TIMER: Invalid timer [dec] for port 
[dec]/[dec] in [chars] operation 

Explanation    A timer event occurred, but the timer type was invalid.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_FSM_NULL_CTXT: NULL context for FSM action [chars] 

Explanation    An FSM action routine was invoked, but with a NULL context argument.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_FSM_TIMER_BAD_CTXT: Invalid or NULL context for timer 
[dec] in [chars] operation 

Explanation    A timer event occurred, but the FSM infrastructure passed to the handler a context pointer that is currently not in use or is NULL.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_INVALID_PROC_EVENT: Got event [dec]:[dec] 

Explanation    An invalid event woke up the process.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_MAX_PGS: Cannot create more thatn [dec] LMP peer 
groups 

Explanation    The number of LMP peer groups has reached the maximum per-LMP instance.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_MAX_PORTS: Cannot configure more than [dec] ports 

Explanation    LMP could not be configured on a port because the maximum number of ports per-LMP instance has been reached.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_PG_CREATE_FAIL: Unable to create PG ([enet]:[dec]) 
for port [dec]/[dec] 

Explanation    The peer group could not be created for the given port. This port is the first port connected to this peer to move into the operational state.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_PG_GET_FAIL: Unable to get PG (%e) for port %d/%d 

Explanation    The system was unable to get the peer group for the given port.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_PG_INCONSISTENT: PG [enet]:[dec] should have [dec] 
links, but none found 

Explanation    A link has left a peer group that seems to have more links, but no other links were found.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_PG_NO_CTRL_LINK: No control link for preferred PG 
[dec] 

Explanation    A peer group with no control link has been set as the preferred peer group.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_PG_OUT_OF_RANGE: Peer group [dec] is out of range 

Explanation    A peer group has been passed to an API that is out of range.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_RX_BAD_FIRST_TLV: Bad first TLV ([dec]) in received 
packet on port [dec]/[dec] 

Explanation    The received LMP packet was dropped because its first type-length value (TLV) was not a Probe TLV or a Hello TLV.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_RX_BAD_INTERFACE: Incorrect port [dec]/[dec] for 
received packet 

Explanation    A received LMP packet was dropped because it had incorrect received packet information. The LMP packet may have been received from an interface on which VSLP is not enabled.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_RX_BAD_TLV_COUNT: Bad TLV count in received packet 
([dec]) 

Explanation    A received LMP packet was dropped because it had an incorrect number of type-length values (TLVs). This includes the case where no TLVs are received.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_RX_PLATFORM_REJECT: Platform TLV rejected for 
receieved [chars] packet 

Explanation    A received LMP packet was dropped because one or more platform type-length values (TLVs) were rejected.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_RX_QUEUE_FAIL: Unable to enqueue received packet for 
processing 

Explanation    An internal error occurred that prevented a packet from being enqueued to the packet processing queue. The packet was dropped.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_RX_XFORM: Failed to transform received %s packet 

Explanation    An ISSU transformation failed on the received packet. The packet was dropped

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_LMP_SAME_SWITCH_ID: Switch id in probe packet is the same 
as the local switch id %d. The packet was dropped. 

Explanation    The switch ID in a probe packet from the peer is the same as the local switch ID. The packet was dropped.

Recommended Action    Investigate and correct this misconfiguration

Error Message    %VSLP-3-VSLP_NULL_ENTRY: Null [chars] entry in [chars] operation 

Explanation    A NULL entry was passed in the specified operation.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_PROC_CREATE_FAILED: Unable to create process "[chars]" 

Explanation    The specified process could not be created due to unknown reasons.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_QUEUE_CREATE_FAILED: Unable to create watched queue 
"[chars]" 

Explanation    The specified watched queue could not be created due to unknown reasons.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_REGISTRY_ADD_FAIL: [chars] registry addition failed 

Explanation    The given registry addition failed during initialization.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_THREAD_CREATE_FAILURE: tid %u/intvl %u: %s 

Explanation    VSLP transmit thread creation failed for the specified reason.

Recommended Action    No action is required.

Error Message    %VSLP-3-VSLP_THREAD_FAILURE: tid %u: %s 

Explanation    A general VSLP transmit thread failure occurred for the specified reason.

Recommended Action    No action is required.

VSLP-4

Error Message    %VSLP-4-ASIC_DUMP: [chars] 

Explanation    The VSL physical link is up and the role was not resolved in RRP.

Recommended Action    No action is required.

Error Message    %VSLP-4-VSL_PREEMPT_TIMER: Preempt timer configured to [dec] minutes. 
Standby will takeover as active in [dec] minute(s) 

Explanation    The preempt timer is configured on the standby unit. The standby unit will become active after the timer expires.

Recommended Action    No action is required.

VSLP-5

Error Message    %VSLP-5-RRP_ACTIVE_PEER_DOWN: Communication to active peer went down. 
Triggering switchover... 

Explanation    The role resolution protocol has received an indication that communication with the active peer has gone down. This condition will trigger a switchover.

Recommended Action    No action is required.

Error Message    %VSLP-5-RRP_RT_CFG_CHG: Configured [chars] value is different from 
operational value. Change will take effect after config is saved and switch [dec] 
is reloaded. 

Explanation    Role resolution protocol configuration changes by user

Recommended Action    No action is required.

Error Message    %VSLP-5-RRP_MSG: [chars] 

Explanation    A role resolution protocol event was received.

Recommended Action    No action is required.

Error Message    %VSLP-5-RRP_NO_PEER: No VSLP peer found. Resolving role as Active 

Explanation    Because VSLP could not communicate with any peer, it will boot up as active.

Recommended Action    No action is required.

Error Message    %VSLP-5-RRP_PEER_TIMEOUT: VSLP peer timer expired without detecting 
peer. Resolving role as Active 

Explanation    Because the role resolution protocol could not communicate with any peer before the peer timer expiry, it will boot up as active.

Recommended Action    No action is required.

Error Message    %VSLP-5-RRP_PREEMPT: [chars]
Switch [int]: Priority [int]: Preempt [chars]
Switch [int]: Priority [int]: Preempt [chars]

Explanation    Displays preemption configuration.

Recommended Action    No action is required.

Error Message    %VSLP-5-RRP_PREEMPT_IGNORE: %s 

Explanation    The preemption configuration is ignored due to unsaved configurations.

Recommended Action    No action is required.

Error Message    %VSLP-5-RRP_ROLE_RESOLVED: Role resolved as [chars] by VSLP 

Explanation    The role resolution protocol has communicated with a peer and has resolved its role.

Recommended Action    No action is required.

Error Message    %VSLP-5-RRP_RT_CFG_CHANGE: [chars] 

Explanation    The role resolution protocol configuration has been changed by a user.

Recommended Action    No action is required.

Error Message    %VSLP-5-RRP_UNSAVED_CONFIG: Ignoring system reload since there are 
unsaved configurations.
Please save the relevant configurations

Explanation    The role resolution protocol received an indication that the system must be reloaded due to a role change from active to standby. No reload will occur because unsaved configurations exist and would be lost.

Recommended Action    No action is required.

Error Message    %VSLP-5-RRP_WR_MEM_PROGRESS: Ignoring system reload since config save 
operation is in progress. Please wait till the configs are saved 

Explanation    The role resolution protocol (RRP) received an indication that a system reload is required due to a role change from active to standby. Since a configuration save operation is in progress, the system will not be reloaded.

Recommended Action    No action is required.

Error Message    %VSLP-5-VSL_UP: [chars] 

Explanation    VSL status has changed to UP, with more details provided in message.

Recommended Action    No action is required.

VSLP-6

Error Message    %VSLP-6-ACTIVE: [chars] 

Explanation    Displays the state of the virtual switch active supervisor engine.

Recommended Action    No action is required.

Error Message    %VSLP-6-STANDBY: [chars] 

Explanation    Displays the state of the virtual switch standby supervisor engine.

Recommended Action    No action is required.

VSLP_ISSU Messages

This section contains Virtual Switch Link Protocol (VSLP) in-service software upgrade (ISSU) messages.

VSLP_ISSU-3

Error Message    %VSLP_ISSU-3-CAP_RESULT_INCOMPAT: VSLP ISSU client capability exchange 
result incompatible. 

Explanation    Based on the results of the capability exchange, the VSLP ISSU client is not compatible with the peer.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message    %VSLP_ISSU-3-INIT: VSLP ISSU client initialization failed at %s, error 
%s 

Explanation    The VSLP ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VSLP_ISSU-3-INTERNAL: An internal error occurred: %s 

Explanation    A software error occurred during the specified operation.

Recommended Action    No action is required.

Error Message    %VSLP_ISSU-3-INVALID_PROC_EVENT: Got event %d:%d 

Explanation    The process was awakened with an invalid event.

Recommended Action    No action is required.

Error Message    %VSLP_ISSU-3-ISSU_ERROR: %s failed with error code %d for peer %e 

Explanation    An ISSU application program interface (API) was unable to perform an operation for the VSLP layer. The message includes the error code from the ISSU library.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu fsm commands and your pertinent troubleshooting logs.

Error Message    %VSLP_ISSU-3-MSG_NOT_OK: VSLP ISSU client message %s is not compatible 

Explanation    The VSLP ISSU client received an incompatible message from the peer unit. Since the message is not compatible, it cannot be processed by this unit.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message    %VSLP_ISSU-3-NEGO_FAILED: VSLP ISSU start nego session with peer %e 
with error code %s 

Explanation    The VSLP ISSU could not start its negotiation process.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu fsm commands and your pertinent troubleshooting logs.

Error Message    %VSLP_ISSU-3-NULL_ENTRY: Null %s entry in %s 

Explanation    A NULL entry was passed in the specified operation.

Recommended Action    No action is required.

Error Message    %VSLP_ISSU-3-PROC_CREATE_FAILED: Unable to create process 

Explanation    The specified process could not be created.

Recommended Action    No action is required.

Error Message    %VSLP_ISSU-3-QUEUE_CREATE_FAILED: Unable to create watched queue 

Explanation    The specified watched queue could not be created.

Recommended Action    No action is required.

Error Message    %VSLP_ISSU-3-RX_BAD_INTERFACE: Incorrect port %d/%d for received 
packet 

Explanation    A VSLP ISSU packet was received that contains incorrect received packet info. This VSLP ISSU packet may have been received from an interface on which VSLP is not enabled. The packet was dropped.

Recommended Action    No action is required.

Error Message    %VSLP_ISSU-3-RX_QUEUE_FAIL: Unable to enqueue received packet for 
processing 

Explanation    An internal error occurred that prevented a packet from being enqueued to the packet processing queue for processing. The packet was dropped.

Recommended Action    No action is required.

Error Message    %VSLP_ISSU-3-SEND_FAILED: VSLP ISSU client failed to send a 
negotiation message 

Explanation    The VSLP ISSU client could not send a session negotiation message to the peer. When a problem occurs in the negotiation, the peer switch unit cannot be brought up as standby, resulting in two active switches in the system.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message    %VSLP_ISSU-3-SESSION: VSLP ISSU client %s 

Explanation    The VSLP ISSU client detected an error during a session negotiation with the peer unit. As a result, the peer switch cannot be brought up as standby and two switches will be active in the system.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message    %VSLP_ISSU-3-TRANSFORM: VSLP ISSU client %s transform failed for %s 
message, error %s 

Explanation    The VSLP ISSU client could not transform the message. If the transmit transformation failed, the VSLP message cannot be sent to the standby unit. If the receive transformation failed, the VSLP message cannot be processed on the standby unit. In either case, the VSLP ISSU client state will not be identical with the active unit.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

VS_MERGE Messages

VS_MERGE-3

Error Message    %VS_MERGE-3-SAME_ACT_STDBY_PO: Invalid configuration - standby VSL 
port channnel number [int] is same as active VSL port channel. Auto-merge process 
is aborted. 

Explanation    This is an invalid configuration. Active and standby must use different VSL port channel numbers. Auto-merge process is aborted. If this situation happens, standby switch will come up in RPR mode.

Recommended Action    Use different port channel numbers for active and standby VSL port channels and its members. This change can be done by bringing down all VSL links so that standby switch comes up as active switch. Then enter configuration mode and make changes to use different VSL port channel number for local VSL port members. Once completed, reload this switch to start auto-merge procedure again.

VS_MERGE-4

Error Message    %VS_MERGE-4-STDBY_VSL_PO_EXIST: Overwriting existing port channel 
[int] with standby VSL port channel 

Explanation    There exists a port channel that uses the same channel number as standby VSL port channel. Overwrite the existing port channel configuration with standby VSL port channel configuration.

Recommended Action    If the existing port channel configuration is required, then reconfigure the port channel and its related configuration with a different port channel number

VS_MERGE-6

Error Message    %VS_MERGE-6-SAVE_MERGED_CFG: Saving merged configuration... 

Explanation    The merged configuration is being copied to startup-config.

Recommended Action    No action is required.

VS_MOD_PROV Messages

This section contains virtual switch module provisioning messages.

VS_MOD_PROV-3

Error Message    %VS_MOD_PROV-3-AUTO_ADD_SLOT_FAILED: Auto module provision add failed 
for chassis [dec] slot [dec] 

Explanation    A call to add module provisioning information to a red-black tree (RBTree) has failed.

Recommended Action    No action is required.

Error Message    %VS_MOD_PROV-3-AUTO_REM_SLOT_FAILED: Auto module provision remove 
failed for chassis [dec] slot [dec] 

Explanation    Remove module provisioning slot information failed.

Recommended Action    Reproduce the issue after execute 'debug switch virtual ridprom all'CLI on both active RP and SP before bringing up standby chassis. Collect the debug trace information from console.

Error Message    %VS_MOD_PROV-3-ICC_PAK_NULL: Pak pointer for icc msg is NULL 

Explanation    An ICC packet buffer pointer could not be obtained.

Recommended Action    No action is required.

Error Message    %VS_MOD_PROV-3-MSGBUF_PTR_NULL: Data buffer pointer is NULL 

Explanation    A message or data buffer pointer could not be obtained.

Recommended Action    No action is required.

Error Message    %VS_MOD_PROV-3-MTU_ZERO: MTU size is zero due to ISSU session 
negotiation failure. 

Explanation    ISSU return negotiated message size equal to zero for this session. Most likely, there is an issue with IPC transport mechanism that causes ISSU negotiated message to time out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %VS_MOD_PROV-3-NO_AUTO_PROV_PROC: Unable to create VS Auto Module Prov 
process. 

Explanation    The virtual switch automatic module provisioning process could not be created.

Recommended Action    No action is required.

Error Message    %VS_MOD_PROV-3-NO_AUTO_PROV_WB: Unable to create watched boolean(s). 
vs_auto_prov_add_wb = , vs_auto_prov_ha_wb = 

Explanation    The specified watched booleans could not be created.

Recommended Action    No action is required.

Error Message    %VS_MOD_PROV-3-SEND_PROV_DATA_FAILED: Sending of module provision info 
to ACTIVE failed. 

Explanation    The ICC sending of module provisioning information from the standby module to the active module failed.

Recommended Action    No action is required.

VSPA Messages

This section contains VPN Services Port Adapter (VSPA) messages.

VSPA-3

Error Message    %VSPA-3-FIPSERROR: FIPS POST Failed. 

Explanation    The power-on self test (POST) failed. The crypto engine is disabled.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VSPA-3-HARDWARE_ERR: WS-IPSEC-3 Error: %s 

Explanation    A hardware error occurred on the WS-IPSEC-3, causing an interrupt. The module will automatically reload in the case of an unrecoverable error.

Recommended Action    Copy the error message (and any recent error messages) as it appears on the console. In case of a WS-IPSEC-3 crash, collect the crashinfo file from the sup-bootdisk. Contact your Cisco technical support representative and provide the gathered information.

VSPA-4

Error Message    %VSPA-4-FIPS_CRNG_NOTIFY: Same Random Number was generated twice in 
succession! 

Explanation    The same random number was generated twice in succession.

Recommended Action    No action is required.

VSPA-5

Error Message    %VSPA-5-FIPSNOTIFY: FIPS POST Successful. 

Explanation    The power-on self test (POST) succeeded.

Recommended Action    No action is required.

Error Message    %VSPA-5-ILLEGALCLEAR: Illegal Clear Packet: Src =%u.%u.%u.%u, Dst 
=%u.%u.%u.%u, Proto =%u 

Explanation    An unexpected clear (unencrypted) packet was received from the WAN.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VSPA-5-REPLAYERR: Replay Error: Current Seq. No. =%u, Highest Seq No. 
=%u 

Explanation    A replay error was detected on IPsec inbound processing.

Recommended Action    Make sure the IPSec packets are not being reordered in the network, such as by a QoS process.

Error Message    %VSPA-5-SELCHECKERR: Selector Check Error: Src =%u.%u.%u.%u:%u, Dst 
=%u.%u.%u.%u:%u, Proto =%u, saidx =%u 

Explanation    A packet was received that did not fall within the appropriate selector range.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %VSPA-5-SEQOVERFLOW: Sequence number overflow: Src =%u.%u.%u.%u, Dst 
=%u.%u.%u.%u, Proto =%u, saidx =%u 

Explanation    The sequence number in the security association has overflowed.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

VS_PARSE Messages

This section contains virtual switch (VS) messages.

VS_PARSE-3

Error Message    %VS_PARSE-3-ALLOC_ICC_PAK_FAIL: Unable to allocate memory for ICC 
packet 

Explanation    A packet allocation failed for sending an ICC message to do the specified operation.

Recommended Action    No action is required.

Error Message    %VS_PARSE-3-CONFIG_MISMATCH: [chars] 

Explanation    The VSL configuration in the standby module's configuration differs from either the active module's startup configuration or the active module's running configuration.

Recommended Action    Use the show switch virtual redundancy config-mismatch command to display the mismatch configuration. If the standby configuration differed from the active's startup configuration or the active's running configuration, you must fix the discrepancy in VSL configuration between the active and standby switch. Then, enter a write mem command to update the standby's startup configuration and reload the standby.

Error Message    %VS_PARSE-3-MISMATCH: %s 

Explanation    Configuration mismatches were detected between the active and standby units in either the running configuration, the startup configuration, or the EARL operating mode.

Recommended Action    Enter the show switch virtual redundancy mismatch command to display the mismatch. Correct any discrepancy in the VSL configuration between the standby switch's configuration and the active switch's startup configuration or running configuration. Correct any discrepancy in the EARL operating mode between the standby switch's configuration and the active switch's configuration. Enter the write mem command and reload the standby switch.

Error Message    %VS_PARSE-3-VS_HWSB_CREATE_FAIL: Unable to create VS HW SB for vslot 
[int], port [int] 

Explanation    An attempt to create a virtual switch hardware standby has failed due to unknown reasons. During virtual switch mode conversion, the standby VSL port would flap when attempting to reconfigure the port on the active. It is recommended to have at least two physical links for a virtual switch mode conversion attempt in order to avoid a dual active scenario due to this error.

Recommended Action    No action is required.

VS_PARSE-4

Error Message    %VS_PARSE-4-CONFIG_WARNING: %s: %d 

Explanation    Errors were detected while parsing the virtual switch (VS) configuration. The switch will be in standalone mode with a switch number setting.

Recommended Action    If the VS conversion process is successful in bringing up virtual switch mode, no action is required. If the process fails, check the VS configuration.

Error Message    %VS_PARSE-4-NO_VSL_CONFIG: No VSL interface is configured 

Explanation    There are no VSL interfaces configured. This switch cannot communicate with the other switch to form the virtual switch.

Recommended Action    No action is required.

Error Message    %VS_PARSE-4-SWITCH_NUM: %s: %d 

Explanation    A valid ROMMON variable SWITCH_NUMBER must be configured before the switch can be brought up as a virtual switch.

Recommended Action    Configure a valid SWITCH_NUMBER in ROMMON.

VS_QOS_ACL Messages

This section contains virtual switch QoS ACL messages.

VS_QOS_ACL-3

Error Message    %VS_PORT_QOS_ACL-3-PIDX_BASE_MSG_FAILED: Setting of PIDX_BASE to value 
[hex] failed 

Explanation    A message from the TCAM application to set the Tycho's PDIX_BASE has failed.

Recommended Action    No action is required.

VTSP Messages

This section contains Voice Telephony Service Provider (VTSP) messages.

Error Message    %VTSP-3-MSGSNDFAIL: channel:[chars] DSP ID:[hex] Message ID:[hex] 

Explanation    A message could not be sent to the DSP. The call continued but may have experienced problems.

Recommended Action    Verify that the DSP is still functioning properly by attempting to place a call on the affected voice port. Contact your technical support representative, include the full text of the error message.

WARMUPGRADE Messages

This section contains warm upgrade messages.

WARMUPGRADE-3

Error Message    %WARMUPGRADE-3-char: Image file open/read failure. 

Explanation    The warm upgrade process could not open or read from the image file specified.

Recommended Action    Check whether the specified image is present at the desired location and has the required read permissions. If the location is remote, check whether connectivity exists.

Error Message    %WARMUPGRADE-3-CHECKSUM: [chars] image checksum mismatch. 

Explanation    The checksum of the image in memory differs from the expected checksum.

Recommended Action    Check whether the image file is complete and uncorrupted.

Error Message    %WARMUPGRADE-3-DECOMPRESS: Image file decompression failure. 

Explanation    The warm upgrade process could not decompress the image file.

Recommended Action    Check whether the image file is complete and uncorrupted.

Error Message    %WARMUPGRADE-3-FORMAT: Unknown image file format. 

Explanation    The warm upgrade process could not recognize the format of the image file.

Recommended Action    Check whether the specified image is a valid Cisco IOS executable in a supported format. Check the release notes for supported formats.

Error Message    %WARMUPGRADE-3-SIZE: [chars] image size mismatch. 

Explanation    The size of the image in memory differs from the expected size.

Recommended Action    Check whether the image file is complete and uncorrupted.

WCCP Messages

This section contains Web Cache Communication Protocol (WCCP) messages.

WCCP-3

Error Message    %WCCP-3-SBADDFAIL: Unable to add WCCP subblock on interface [chars] 

Explanation    This internal error message indicates that the WCCP process was unable to attach interface-specific service information.

Recommended Action    Ensure that there is enough memory available for all processes.

Error Message    %WCCP-3-SBCREATEFAIL: Unable to allocate WCCP subblock on interface 
[chars] 

Explanation    This internal error message indicates that the WCCP process was unable to allocate memory to hold interface specific service information.

Recommended Action    Ensure that there is enough memory available for all processes.

WiSM Messages

This section contains WiFi services module messages.

WiSM-3

Error Message    WiSM-3-PORTCHANNEL: Portchannel allocation failed for module [dec].

Explanation    The system is unable to allocate enough port channel groups for WiSM card. [dec] is the module number.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

WiSM-5

Error Message    %WiSM-5-DUP_SRVC_IP: Service IP [IP_address] of Controller [dec]/[dec] 
is same as Controller [dec]/[dec] 

Explanation    The Cisco Wireless Services Module software detected that a controller is assigned with an IP address on its service port that is being used by another controller.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %WiSM-5-RESET: Controller [dec]/[dec] not responding, WiSM in slot 
[dec] is being reset 

Explanation    The Cisco Wireless Services Module in the specified slot is being reset because one of the controllers failed to respond to 12 consecutive keepalive requests.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %WiSM-5-STATE: Controller [dec] in slot [dec] is [chars] 

Explanation    A change has been detected in the Cisco Wireless Services Module controller. If the controller status is Oper-Up, WCP communication between the controller and the supervisor engine is up or else it is down.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

WS_ALARM Messages

This section contains Windstar alarm messages.

WS_ALARM-6

Error Message    %WS_ALARM-6-INFO: [chars] [chars] [chars] [chars] [chars] 

Explanation    Displays alarm assertion or deassertion information.

Recommended Action    No action is required.

WS_IPSEC_3 Messages

Error Message    %WS_IPSEC_3-3-FIPSERROR: FIPS POST Failed. 

Explanation    Power On Self Test failed. Crypto engine disabled.

Recommended Action    Contact TAC.

Error Message    %WS_IPSEC_3-3-HARDWARE_ERR: WS_IPSEC_3 Error: [chars] 

Explanation    A hardware error occured on the WS_IPSEC_3 causing an interrupt

Recommended Action    Copy the error message (and any recent error messages) as it appears on the console. In case of a WS_IPSEC_3 crash, collect the crashinfo file from the sup-bootdisk. Contact your Cisco technical support representative and provide the gathered information. The SPA will automatically reload itself in case of a crash

Error Message    %WS_IPSEC_3-4-FIPS_CRNG_NOTIFY: Same Random Number was generated twice 
in succession! 

Explanation    Same random number was generated twice in succession.

Recommended Action    No Action Required.

Error Message    %WS_IPSEC_3-5-FIPSNOTIFY: FIPS POST Successful. 

Explanation    Power On Self Test succeeded.

Recommended Action    No Action Required.

Error Message    %WS_IPSEC_3-5-ILLEGALCLEAR: Illegal Clear Packet: Src 
=[int].[int].[int].[int], Dst =[int].[int].[int].[int], Proto =[int] 

Explanation    An unexpected clear packet was received from the WAN.

Recommended Action    If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support

Error Message    %WS_IPSEC_3-5-REPLAYERR: Replay Error: Current Seq. No. =[int], 
Highest Seq No. =[int] 

Explanation    Failed anti-replay check on IPsec inbound processing.

Recommended Action    Make sure the IPSec packets are not reordered in the networks. Follow up with TAC.

Error Message    %WS_IPSEC_3-5-SELCHECKERR: Selector Check Error: Src 
=[int].[int].[int].[int]:[int], Dst =[int].[int].[int].[int]:[int], Proto =[int], 
saidx =[int] 

Explanation    A packet was received that did not fall within the appropriate Selector range.

Recommended Action    If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %WS_IPSEC_3-5-SEQOVERFLOW: Sequence number overflow: Src 
=[int].[int].[int].[int], Dst =[int].[int].[int].[int], Proto =[int], saidx 
=[int] 

Explanation    The sequence number in the Security Association has overflowed.

Recommended Action    If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

X40G Messages

This section contains X40G client error messages.

X40G-2

Error Message    %X40G-2-TCAM_MGR_CRIT_ERR: GTM ERROR: [chars] ([dec]) 

Explanation    An X40G TCAM critical error was detected.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

X40G-3

Error Message    %X40G-3-TCAM_MGR_ERR: GTM ERROR: [chars] ([dec]) 

Explanation    An X40G TCAM MGR interaction error was detected.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %X40G-3-TCAM_MGR_HW_ERR: GTM HW ERROR: [chars] ([dec]) [[dec]:[hex]] 

Explanation    An X40G TCAM hardware error was detected.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %X40G-3-TCAM_MGR_HW_PERR: GTM HW ERROR: [chars] ([dec]) 

Explanation    An X40G TCAM interface parity error was detected.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

X40G-4

Error Message    %X40G-4-TCAM_MGR_ALLOC_ERR: [chars] NP ([dec]), Region Id ([dec]) 

Explanation    An NP TCAM entry allocation failure was detected.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the remote command module sh platform software xtcammgr instance info command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the gathered information.

X40G-5

Error Message    %X40G-5-TCAM_MGR_INFO: [chars] 

Explanation    An X40G TCAM driver error was detected.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

X40G_PC_QOS-3

Error Message    %X40G_PC_QOS-3-X40G_EXCEED_NUM_QUEUES: %Exceed number of supported 
queues for this interface

Explanation    Not available.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %X40G_PC_QOS-3-X40G_WRED_QLIMIT: %Queue limit and WRED cannot be 
configured together

Explanation    Not available.

Recommended Action    This error indicates a qos policymap configuration error occured. Qos processing on the interface might not work as expected. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

X40G_PC_QOS-4

Error Message    %X40G_PC_QOS-4-X40G_PC_PMAP_INCOMPATIBLE: Warning - Policymap 
attached to port-channel EVC is incompatible with X40G member link. 

Explanation    Policymap attached to port-channel EVC is with an X40G member link.

Recommended Action    Remove policymap attached to port-channel EVC before adding a X40G member link to port-channel.

X40G_QOS-3

Error Message    %X40G_QOS-3-ACTN: [chars] 

Explanation    The x40g qos client detected a qos feature processing error event, specified in the message

Recommended Action    This error indicates a qos policymap configuration error occured. Qos processing on the interface might not work as expected. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %X40G_QOS-3-CFN: [chars] 

Explanation    The x40g qos client detected a classification configuration error event, specified in the message.

Recommended Action    This error indicates a qos policymap configuration error occured. Qos processing on the interface might not work as expected. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %X40G_QOS-3-NOMEM: Memory Allocation Failure - [chars]) 

Explanation    Memory required by the qos client to service one or more Network Processors could not be allocated.

Recommended Action    This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled via the configuration. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %X40G_QOS-3-NP: [chars] 

Explanation    The x40g qos client detected an npu programming error event, specified in the message.

Recommended Action    This error indicates a qos policymap configuration error occured. Qos processing on the interface might not work as expected. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %X40G_QOS-3-PMAP_CONFIG:[chars] 

Explanation    QoS processing on the interface specified in the msg is not functional

Recommended Action    This configuration error is not considered fatal to the operation of the Network Processors. The software is designed to detect and report the error condition. Please refer to the cisco.com documentation for configuration to correct the problem.

Error Message    %X40G_QOS-3-PRFL:[chars] 

Explanation    The x40g qos client detected a hardware profile run out. Hardware profile type is mentioned in the message

Recommended Action    Identify the QoS hardware profile that got exhausted on the ES+ linecard. Modify the QoS configuration on the interface such that it can get a QoS profile shared with any other policymap on linecard or else remove policymap from the interface. Else Qos processing on the interface might not work as expected. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %X40G_QOS-3-SVI_PMAP: [chars] 

Explanation    Only one policymap is allowed to be attached to either direction of interface vlan at a time.

Recommended Action    Please remove previous attached policymap and reattach the policymap. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

X40G_QOS-4

Error Message    %X40G_QOS-4-CFG: [chars] 

Explanation    When applying policymap, configuration may be changed by the NP because of hardware support

Recommended Action    This error indicates a qos policymap configuration error occured. Qos processing on the interface might not work as expected. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

XCONNECT Messages

This section contains xconnect-related event and error messages.

XCONNECT-3

Error Message    %XCONNECT-3-CONFIG: %s 

Explanation    An invalid XCONNECT configuration or an error in processing the XCONNECT configuration has occurred.

Recommended Action    No action is required.

Error Message    %XCONNECT-3-ILLEGAL: %s 

Explanation    An illegal event has been processed by the XCONNECT subsystem.

Recommended Action    No action is required.

XCONNECT-5

Error Message    %XCONNECT-5-PW_STATUS: %s 

Explanation    An event caused the pseudowire to change status.

Recommended Action    No action is required.

Error Message    %XCONNECT-5-REDUNDANCY: %s 

Explanation    An event caused the XCONNECT redundancy facility to generate a switchover to the specified backup member.

Recommended Action    No action is required.

XCPA Messages

Error Message    %XCPA-3-HWVER: bay [[dec]] incompatible microcode (hw:[int].[int], 
[int].[int]). 

Explanation    An incompatability exists between the port adapter hardware and the version of microcode that the system image attempted to load.

Recommended Action    Use the show microcode command to display the default and configured versions of microcode for this port adapter hardware type. Assure that the correct version of microcode exists in flash. Use the microcode reload command to load the microcode. If the error still occurs, record the output from the following commands: show tech, show microcode, dir slot0:, dir slot1:, show log. Provide this information to your technical support representative.

XCVR Messages

This section contains transponder messages.

XCVR-3

Error Message    %XCVR-3-UNKNOWN_SFP_INSERTED: Unknown SFP inserted [chars] 

Explanation    An unknown Small Form Factor Pluggable (SFP) transceiver has been inserted.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

XDR Messages

This section contains eXternal Data Representation (XDR) messages.

XDR-3

Error Message    %XDR-3-BYPASSFOFNEGO: Bypassing FOF ISSU client %s (%u) nego for XDR 
client %s, slot %s as FOF ISSU client is not present in %s image. 

Explanation    This XDR client has a dependency on another ISSU client due to having foreign-owned fields (FOFs). Because the ISSU client that owns the FOFs is not in the image, the XDR client will not wait for that client to finish ISSU negotiation. The missing client must be added to the image.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-CLIENTISSUBADENTITY: Unable to register ISSU entity for 
[chars], reason: [chars] 

Explanation    Unable to register this XDR client's ISSU entity due to problems with registering the item given as a reason in the error message. ISSU will stop working for this client and may lead to unpredictable behavior.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-CLIENTISSUBADGROUP: New m/cast group (slots [chars]) has 
multiple members before nego complete. 

Explanation    A new multicast group has been created with multiple slots before ISSU negotiation for each client has completed. This condition will lead to unpredictable results.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-CLIENTISSUBADNEGOMSG: Unexpected nego msg - slot [chars], 
client [chars], ctxt [dec] 

Explanation    XDR has received a negotiation message unexpectedly as this client is either not ISSU aware or has already completed negotiation for this slot. This condition is likely a precursor to unpredictable behavior for this client.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-CLIENTISSU_FOF_NEGOFAIL: ISSU negotiation failed for FOF client 
%u, for peer %s (ISSU peer %d), blocking ISSU client %s (%d) reason - %s 

Explanation    The ISSU negotiation failed for a client that has registered ISSU foreign-owned field (FOF) client dependencies. The dependent clients on this slot and the remote slot cannot interoperate in SSO mode. Synchronizing of information to and from this slot cannot proceed for this client and the dependent clients. Enter the show xdr multicast command for full details.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show xdr multicast commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-CLIENTISSU_FOF_REGERROR: ISSU client %s (%d), entity %d, 
message %d (%s), failed ISSU FOF registration: %s, reason: %s, 

Explanation    This ISSU client has a message containing a foreign-owned field (FOF) owned by another client, but the client failed to register this dependency. This is an internal software error.

Recommended Action    Update to a later software release.

Error Message    %XDR-3-CLIENTISSUNEGATIVEPADDING: Negative padding for [chars], slots 
[chars], msg [dec] (padded: [dec], unpadded: [dec]) 

Explanation    An internal error occurred involving a mismatch of internal data structures.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-CLIENTISSU_NEGOFAIL: ISSU negotiation failed for [chars], slot 
[chars] [chars] 

Explanation    ISSU negotiation failed. The XDR client on this slot and the remote slot cannot interoperate in SSO mode. Synchronizing of information to and from this slot will not happen for this client and dependent clients. Seethe output of the show xdr multicast command for full details.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-CLIENTISSUNEGONOTDONE: Attempting to push send XDR message 
([dec]) to slots [chars] for [chars] before nego complete. 

Explanation    An internal error occurred that may result in unpredictable behavior.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-CLIENTISSU_NEGOREGERROR: XDR client %s, failed ISSU negotiation 
result notification registration for ISSU client %s (%d), reason: %s, 

Explanation    This client has a dependency on the successful ISSU negotiation of another client and has failed to register this dependency. This is an internal software error.

Recommended Action    Update to a later software release.

Error Message    %XDR-3-CLIENTISSU_NEGOUNREGERROR: Failed to unregister ISSU 
negotiation result notification registration for ISSU client %s (%d), reason: %s, 

Explanation    This client has a dependency on the successful ISSU negotiation of another client and has failed to unregister this dependency when not required. This is an internal software error.

Recommended Action    Update to a later software release.

Error Message    %XDR-3-CLIENTISSUNOMSGGRP: Cannot determine ISSU message group for 
slot %d. Unknown %s 

Explanation    Because the line card type for the specified slot is not recognized, the ISSU client cannot determine the set of ISSU messages to be used between the local and remote slot. This condition might be due to a new line card type.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-CLIENTISSU_PUSHFAIL: Attempting to push send XDR message 
([chars]) to slots [chars] via client [chars] failed due to [chars] 

Explanation    An internal error occurred that may result in unpredictable behavior.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-CLIENTISSU_REGERROR: ISSU client [dec] ([chars]), entity [dec], 
failed ISSU registration: [chars] 

Explanation    The ISSU negotiation failed for this XDR client. This is a software error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-CLIENTISSUSENDFAILED: Can't send XDR client ISSU nego msg: 
reason [chars], slot [chars], client [chars] 

Explanation    XDR has failed to send an ISSU negotiation message for the given client. The slot will be marked as ISSU-unaware, and communication with this slot will proceed on that basis. However, this is likely to lead to unpredictable behavior.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-CLIENTISSUSTARTNEGOFAIL: Can't start nego: reason [chars], slot 
[chars], client [chars], sid [dec] 

Explanation    XDR has failed to start ISSU negotiation with the remote slot for the reason given. The slot will be marked as ISSU-unaware, and communication with this slot will proceed on that basis. However, this is likely to lead to unpredictable behavior.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-ISSUBADREGPARAMS: Client [chars] trying to register with 
incomplete ISSU support. 

Explanation    This client does not properly support ISSU and will be registered as not supporting ISSU.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-ISSUCAPNEGOFAIL: Client [chars] failed to [chars] 
capability/ies due to [chars] 

Explanation    An internal software error occurred. The capability negotiation failed unexpectedly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-ISSU_ENUM_ERROR: Enum for [chars] ([chars] component) is not 
ISSU-compliant: [chars] 

Explanation    The given enumeration is not ISSU-compliant for the reason given. Unpredictable behavior will result when interoperating with different Cisco IOS versions.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-ISSUINITFAIL: Unable to register XDR ISSU [chars], reason: 
[chars] 

Explanation    Unable to register the given XDR ISSU parameter due to the reason given. This will stop ISSU working for this client and may lead to unpredictable behavior.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-ISSU_NEGOFAIL: ISSU negotiation failed for XDR, slot [chars] 
[chars] 

Explanation    ISSU negotiation failed. XDR on this slot and the remote slot cannot interoperate. Synchronizing of information to and from this slot for all XDR clients will not be allowed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-MSGSIZEFAIL: The IPC message size is out of boundsThe 
ipc_msg_size is : [dec] while the maximum size we can handle is 
theXDR_IPC_BUFFER_SIZE : [dec] . 

Explanation    The size of the IPC message that was received is larger than the maximum size that can be handled.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-PRIOCLIENTISSU_NEGOFAIL: ISSU negotiation failed for [chars], 
slot [chars] [chars] 

Explanation    ISSU negotiation failed for a core XDR client. XDR on this slot and the remote slot cannot interoperate in SSO mode. Synchronizing of information to and from this slot will not happen for any XDR client.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-XDRBADSLOT: An invalid slot %d was obtained during - %s 

Explanation    An invalid slot was obtained.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show xdr linecard, and show xdr multicast commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-XDRDEQUEUE: Failed to dequeue from [chars] with [dec] elements 
still queued 

Explanation    A queueing failure has occurred. A nonempty queue could not be dequeued.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-XDRIPC: XDR IPC error on multicast-group [hex] due to [chars]. 

Explanation    A general IPC-related error occurred, which may prevent transfer of data to other peers using the IPC mechanism .

Recommended Action    Enter the show xdr multicast command immediately after this error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-XDRMCASTJOIN: Attempt to join [chars] to [chars] failed because 
client [chars] returned an error 

Explanation    An internal error occurred that may result in unpredictable XDR behavior.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-XDRMCASTJOINREQ: Client [chars] returned an invalid response to 
a join request for groups [chars] and [chars] 

Explanation    An internal error occurred that may result in unpredictable XDR behavior.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-XDRMCAST_PEER_BINDING: XDR peer [chars] bind to group [chars] 
(was bound to [chars]): [chars] 

Explanation    An internal error occurred that may result in unpredictable XDR behavior.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-XDRNOMEM: XDR failed to allocate memory during [chars] 
creation. 

Explanation    Allocation of memory by the XDR subsystem has failed. This failure may result in unpredictable XDR behavior.

Recommended Action    Make sure that there is enough memory for the operations being performed by your system. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-XDROOS: Received an out of sequence IPC message. Expected [dec] 
but got [dec] 

Explanation    An out-of-sequence or unknown IPC message was received. This condition indicates that an IPC is not working properly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-XDRPEER: An XDR peer error for slot [chars]. Due to [chars]. 

Explanation    An error relating to an XDR peer has occurred.

Recommended Action    Enter the show xdr linecard command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-XDRQUEUE: XDR queue error: [chars]. 

Explanation    The XDR subsystem queueing operation failed. This may result in unpredictable behavior of XDR.

Recommended Action    Make sure that there is enough memory for the operations being performed by your machine. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-3-XDRSLOTFROMMASK: Cannot determine slot from mask [chars] 
(client [chars]) 

Explanation    Mapping from slot mask to slot has failed. During ISSU negotiation, the message destination cannot be determined, and the message will be dropped.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

XDR-6

Error Message    %XDR-6-CLIENTISSUBADRCVTFM: Failed to rcv_transform message - from 
slot [chars], client [chars], context [dec] 

Explanation    The system cannot perform an ISSU receive transform. This condition is likely due to an earlier failure in negotiation, or when one side of an ISSU-enabled XDR connection is out of synchronization with the other.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-6-CLIENTISSUBADTXTFM: Failed to xmit_transform message - to slot 
[chars], client [chars], context [dec] 

Explanation    The system cannot perform an ISSU transmit transform. This condition is likely due to an earlier failure in negotiation, or when one side of an ISSU-enabled XDR connection is out of synchronization with the other.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-6-CLIENTISSU_BLOCKED: Client [chars] cannot sync info to/from 
slot [chars] due to ISSU negotiation failure of client [chars] 

Explanation    This client depends on another XDR client for which ISSU negotiation has failed. As a result, this client is prevented from communicating with the remote slot. This is due to ISSU incompatibilities between the two images. Functionality for this client will revert to RPR mode.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-6-CLIENTISSU_UNBLOCKED: Client [chars] can now sync info to/from 
slot [chars] due to ISSU negotiation success of client [chars] 

Explanation    This client depends on another XDR client for which ISSU negotiation had previously failed but has now succeeded. As a result, this client can resume communication with the remote slot. Functionality for this client will revert to SSO mode.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-6-CLIENTISSUUNREG: Failed to unregister session - client [chars], 
slot [chars], reason [chars] 

Explanation    The system was unable to unregister this session. This condition will likely cause problems when reregistering.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-6-CLIENTNOTREGONRP: Client [chars] has registered on slot [chars] 
before RP. 

Explanation    The XDR client has registered on a non-RP card before an RP card. If this has occurred while toggling the client's registration status rapidly, it may be a transient problem that will resolve itself. If not, the client's status may be unpredictable, and ISSU negotiation (if platform is ISSU-aware) may not take place correctly.

Recommended Action    Verify whether the client's registration status is the same on both the RP and the card on which the problem is reported by comparing the output of the show xdr client all command to see if the client is present or absent in both. If so, and no other error messages have been seen, then this is a transient issue and no further action is required. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-6-ISSUBADRCVTFM_DUMP: CSCsh95828 detected. Please collect 'show 
xdr linecard', 'show monitor event-trace xdr all', and the full system log, on 
both the RP and the related LC, and report this occurrence. Slot %s, data 0x%08x 
%08x %08x %08x %08x %08x %08x %08x 

Explanation    This message contains a decoded packet dump and trace log information for investigating CSCsh95828.

Recommended Action    Copy the message exactly as it appears and contact your Cisco technical support representative.

Error Message    %XDR-6-ISSUBADTXTFM: Failed to xmit_transform message - slot [chars], 
reason [chars] 

Explanation    The system was unable to perform an ISSU transform on an outgoing XDR header. The message will be ignored.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-6-ISSUCLIENTABSENT: ISSU client [chars] absent on slot [chars]. 
Client functionality may be affected. 

Explanation    The remote slot does not support this ISSU client. The software will handle this by reducing client functionality locally to continue in SSO mode, or by forcing the remote peer into RPR mode as appropriate. This is expected behavior in ISSU-capable systems.

Recommended Action    No action is required.

Error Message    %XDR-6-ISSUBADRCVTFM: Failed to rcv_transform message - slot [chars], 
reason: [chars] 

Explanation    The system was unable to perform an ISSU transform on an incoming XDR header. The message will be ignored.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-6-XDRDISABLEREQUEST: Peer in slot [chars] requested to be 
disabled due to: [chars]. Disabling linecard 

Explanation    The line card has requested to be disabled due to an error condition.

Recommended Action    Enter the show monitor event-trace xdr command from the RP and the line card in question. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     XDR-6-XDRINVALIDHDR: XDR for client ([chars]) dropped (slots:[chars] 
from slot:[dec] context:[dec] length:[dec]) due to: [chars] 

Explanation    The XDR client specified in the message text could not be registered. A failure has occurred that prohibits the XDR client from registering with the core.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-6-XDRINVALIDHDRISSU: XDR ISSU negotiation message for client 
([chars]) dropped (slots:[chars] from slot:[chars] context:[int] length:[int]) 
due to: [chars] 

Explanation    The XDR ISSU negotiation message was dropped for the reason given.

Recommended Action    If the message occurred during an ISSU upgrade then it may be safely ignored. Otherwise: Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %XDR-6-XDRIPCNOTIFY: Message not sent to slot [chars] because of IPC 
error [chars]. Disabling linecard. (Expected during linecard OIR) 

Explanation    A general IPC-related error has occurred that may prevent transfer of data to other peers using the IPC mechanism.

Recommended Action    Enter the show xdr multicast and show xdr linecard internal commands immediately after this error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-6-XDRIPCPEER: XDR IPC error occurred for peer in slot [chars] due 
to [chars][chars]. 

Explanation    A general IPC-related error has occurred that may prevent transfer of data to other peers using the IPC mechanism.

Recommended Action    Enter the show xdr multicast and show xdr linecard commands immediately after this error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-6-XDRLCDISABLEREQUEST: Client [chars] requested to be disabled. 
[chars] 

Explanation    The line card has requested to be disabled due to an error condition.

Recommended Action    Enter the show monitor event-trace xdr from the RP and the line card in question. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-6-XDRMCASTINIT: XDR mcast subsystem initilisation error: [chars] 

Explanation    A failure occurred that prohibits the XDR client from registering with the core.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %XDR-6-XDRREGISTRATION: XDR failed to register [chars] client due to 
[chars] 

Explanation    The XDR client specified in the message text could not be registered. A failure has occurred that prohibits the XDR client from registering with the core.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.