Cisco III System Message Guide - Page 342

VPNSMIOS Messages Chapter 2 Messages and Recovery Procedures 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://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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 about 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-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. 2-312 Catalyst Supervisor Engine 32 PISA Cisco IOS System Message Guide, Release 12.2ZY OL-11469-02