Cisco III System Message Guide - Page 228

PISA Messages Chapter 2 Messages and Recovery Procedures PISA Messages This section contains Programmable Intelligent Services Accelerator (PISA) messages. PISA-3 Error Message %PISA-3-GENERIC_ME_ERROR: microengine [dec] thread [dec] param1 [hex] param2 [hex] param3 [hex] param4 [hex] param5 [hex] param6 [hex] param7 [hex] Explanation This message is for testing the debug mechanism of the PISA generic microengine error definition. Recommended Action No action is required. Error Message %PISA-3-MQC_ATTACH_POLICY: Failed to attach policy-map [chars] to interface [chars] on [chars] direction. [chars] Explanation PISA MQC policy-map attachment failed because of one of the following policies: convert ixp-policy, add ixp-policy to vlan, write ixp-policy, or attach acls in ixp-policy. Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.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. Error Message %%PISA-3-MQC_MODIFY_POLICY: Failed to modify policy-map [chars] from interface [chars] on [chars] direction. [chars] Explanation Failed to modify the PISA MQC policy map because the ixp-policy was not found, or the parameters are invalid, or the user failed to remove or attach the policy. Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.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. 2-198 Catalyst Supervisor Engine 32 PISA Cisco IOS System Message Guide, Release 12.2ZY OL-11469-02