Cisco III System Message Guide - Page 257

Chapter 2 Messages and Recovery Procedures SIP600 Messages OL-11469-02 Error Message %SIP600-3-NOMEM: [chars] Explanation The OSM could not obtain statistics because of insufficient memory. 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://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-3-NO_STATID: PXF([dec]): no stat_id is available for statistics collection Explanation The OSM has used up all statistics-collection resources. No resources are available for further statistics collection. Recommended Action Reduce the number of features configured on the specified PXF. If conditions warrant, copy the error message exactly as it appears on the console or in the system log, and contact your Cisco technical support representative. Error Message %SIP600-3-NO_STAT_PROCESS: Failed to create stat process Explanation The SIP 600 failed to create a statistics process. All statistics counters will be zero. Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.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-3-PE_BUS_ERR_INT: Packet Engine Bus Error Interrupt: [chars] Explanation A packet engine bus error interrupt 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://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 Catalyst Supervisor Engine 32 PISA Cisco IOS System Message Guide, Release 12.2ZY 2-227