Cisco III System Message Guide - Page 262

SIP600_PARSING_ENGINE Messages Chapter 2 Messages and Recovery Procedures Error Message %SIP600_PARSING_ENGINE-3-MASTER_ABORT: Parsing Engine CPU Master Abort Error Explanation The SIP-600 parsing engine has detected a CPU master abort interrupt. A read-only to write-only register or a write-only to read-only register could cause this interrupt. The parsing engine continues to process data from the interfaces, if possible. Recommended Action If traffic resumes, no action is required. 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://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 %SIP600_PARSING_ENGINE-3-PARITY_ERROR: Parsing Engine CPU Parity Error Explanation The SIP-600 parsing engine has detected a CPU parity error. Suspect a hardware fault on the second occurrence of this message. Otherwise, the parsing engine continues to process data from the interface, if possible. Recommended Action If traffic resumes, no action is required. 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://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 %SIP600_PARSING_ENGINE-3-RP_INT_WATCHDOG_TIMEOUT: Parsing Engine RP Interface Watchdog Timeout Explanation The SIP-600 parsing engine has detected an RP interface watchdog timeout. The RP interface process has not relinquished the processor for the watchdog timeout period. The parsing engine continues to process data from the interfaces if possible. Recommended Action If traffic resumes, no action is required. 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://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-232 Catalyst Supervisor Engine 32 PISA Cisco IOS System Message Guide, Release 12.2ZY OL-11469-02