Cisco III System Message Guide - Page 225

Chapter 2 Messages and Recovery Procedures PFREDUN Messages PFREDUN-4 Error Message %PFREDUN-4-AUTOBOOT: [chars] Explanation The RP experienced a hardware failure or another type of failure. When the redundant system initializes, the redundant supervisor engine will wait for the RP to initialize. Because the RP cannot initialize due to the failure, the redundant supervisor engine might never initialize. The default wait time for the RP to initialize (three minutes) has now expired, and the autoboot feature for the supervisor engine has been 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://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 %PFREDUN-4-BOOTSTRING_INVALID: The bootfile [chars] is not present in standby Explanation The bootfile that is configured is not present on the redundant supervisor engine. If the redundant supervisor engine resets, it will not come up because it will not find the image specified in the bootstring. Recommended Action No action is required. Error Message %PFREDUN-4-PFC_MISMATCH: My PFC [chars] and Other's PCF [chars] mismatch Explanation The active supervisor engine and the redundant supervisor engine have different versions of the PFC daughter card. Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.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. OL-11469-02 Catalyst Supervisor Engine 32 PISA Cisco IOS System Message Guide, Release 12.2ZY 2-195