-
12.3 T System Message Guide
-
System Message Overview
-
AAA through BSTUN messages
-
C10K through CALL_CONTROL messages
-
CALLRECORD through CPOS messages
-
CRYPTO through DMA messages
-
DNET through ENVM messages
-
ENVMON through FDM_HA messages
-
FECPM through GT96K_TDM messages
-
GTP through HEALTH_MONITOR messages
-
HHM through IPSECV6 messages
-
IPV6 through MICA messages
-
MIPC through NP_VPD messages
-
NRP through PIF messages
-
PIM through PVDM2 messages
-
PXF through RPM_BULK messages
-
RPM_CONN_MGMT through SEC_LOGIN messages
-
SENSOR through SWITCH_IF messages
-
SWITCHOVER through Y88E8K messages
-
Glossary of Acronyms
-
Table Of Contents
PIM Messages
The following are Protocol Independent Multicast (PIM) messages.
Error Message%PIM-5-DRCHG : DR change from neighbor [IP_address] to [IP_address] on interface [chars] (vrf [chars])
Explanation A PIM neighbor is the new designated router on an interface.
Recommended Action No action is required.
Error Message%PIM-5-NBRCHG : neighbor [IP_address] [chars] on interface [chars] (vrf [chars]) [chars]
Explanation A PIM neighbor has become active or inactive (gone up or down) on an interface.
Recommended Action No action is required.
PIM_PROT Messages
The following are Protocol Independent Multicast (PIM) messages.
Error Message%PIM_PROT-6-IDB_ENABLE : Interface [chars] does not support multicast, not enabled
Explanation PIM cannot be enabled on an interface that does not support multicasting.
Recommended Action No action is required.
Error Message%PIM_PROT-3-IDB_INIT : [chars] in [chars] : [chars]
Explanation An internal error has occurred during IDB initialization.
Recommended Action 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PIM_PROT-3-IM_ERR : Interface Manager error - [chars] in [chars] : [chars]
Explanation An internal error has occurred within the Interface Manager.
Recommended Action 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PIM_PROT-7-INTERNAL_ERR : [chars]
Explanation An internal error has occurred.
Recommended Action 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PIM_PROT-3-LIST_ERR : List error in [chars] : [chars]
Explanation An internal list error has occurred.
Recommended Action 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PIM_PROT-3-MSG_SEND_ERR : [chars]
Explanation An internal error occurred during a attempt to send a message. Events scheduled to occur upon receipt of the message (for example, deletion of the PIM tunnel IDB) may not take place.
Recommended Action 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PIM_PROT-3-PAK_ERR : An internal error occured while processing a packet queue
Explanation An internal error has occurred; a managed queue event has been received without a packet.
Recommended Action 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PIM_PROT-3-PROTOCOL_ERR : [chars] - [chars] : [chars]
Explanation An internal error has occurred.
Recommended Action 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PIM_PROT-3-RP_INIT : [chars] in [chars] : [chars]
Explanation An internal error has occurred.
Recommended Action 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PIM_PROT-3-SHUTDOWN_ERR : Error in [chars] : [chars]
Explanation An internal error has occurred.
Recommended Action 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PIM_PROT-3-SRC_UPDATE_ERR : Error in [chars] : [chars]
Explanation An internal error has occurred.
Recommended Action 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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.
PIM_REG_TUN Messages
The following are PIM register tunnel messages.
Error Message%PIM_REG_TUN-3-UNNUM_ERR : Failed to set un-numbered interface for [chars] ([chars])
Explanation The PIM tunnel is not usable without a source address. This condition could occur because a numbered interface could not be found or because some internal error has occurred.
Recommended Action Manually unconfigure the PIM-SM RP and re-configure it.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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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.
PINNACLE Messages
The following are Pinnacle ASIC-specific messages.
Error Message%PINNACLE-4-MACADDRERR : Failed to get Mac Base Address from platform
Explanation A MAC address could not be obtained.
Recommended Action No action is required.
Error Message%PINNACLE-4-OUTOFSYNC : GMAC is not in SYNC: port [dec]
Explanation The GMAC is not in sync.
Recommended Action No action is required.
PKI Messages
The following are PKI feature messages.
Error Message%PKI-6-AUTOENROLL_KEY_LOCKED : Auto-enroll failed - RSA keypair is locked
Explanation Auto-enroll attempted to generate a new RSA keypair. However the existing RSA keypair is locked so auto-enroll cannot proceed.
Recommended Action Auto-enroll will retry the enrollment request. Ensure that the existing RSA keypair is unlocked before the next retry.
Error Message%PKI-6-AUTOSAVE : Running configuration saved to NVRAM
Explanation The auto-enroll feature has obtained a new router key pair and certificate, and has performed an automatic write operation to memory to save them.
Recommended Action No action is required.
Error Message%PKI-6-CERTFAIL : Certificate enrollment failed.
Explanation A fatal error was encountered during a certificate enrollment operation.
Recommended Action Contact the CA administrator.
Error Message%PKI-6-CERT_FATAL_ERR : [chars]
Explanation A fatal error was encountered during a certificate enrollment operation. The operation has been terminated.
Recommended Action Contact the CA administrator.
Error Message%PKI-6-CERTIFSRECV : Could not receive router's Certificate from file system.
Explanation The certificate for the router could not be received from file system.
Recommended Action Verify that the enrollment URL is correct and that the router is able to read from the file system.
Error Message%PKI-6-CERTIFSSEND : Could not send Certificate enrollment request to file system.
Explanation The certificate enrollment request could not be sent to the file system.
Recommended Action Verify that the enrollment URL is correct and that the router is able to write to the file system.
Error Message%PKI-6-CERTPENDING : Enter manual authentication ...
Explanation The CA server is attempting to manually authenticate the router.
Recommended Action Follow the manual authentication procedure.
Error Message%PKI-6-CERTREJECT : Certificate enrollment request was rejected by Certificate Authority
Explanation A certificate enrollment request was received by the Certificate Authority, and the Certificate Authority has rejected the enrollment request.
Recommended Action Contact the Certificate Authority administrator.
Error Message%PKI-6-CERTRET : Certificate received from Certificate Authority
Explanation A certificate enrollment request was received by the Certificate Authority. It has issued the certificate and has sent back a copy.
Recommended Action Informational message only. No action required.
Error Message%PKI-3-CERTRETFAIL : Certificate enrollment failed.
Explanation A certificate enrollment transaction has failed due to an internal error.
Recommended Action Contact the CE or open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PKI-6-CS_DELETE : Certificate Server is deleted.
Explanation The Certificate Server is deleted.
Recommended Action No action is required.
Error Message%PKI-6-CS_DELETE_TP_KEY : Trustpoint and key deleted.
Explanation The trustpoint and key used by the Certificate Server have been deleted.
Recommended Action No action is required.
Error Message%PKI-6-CS_GRANT_AUTO : All enrollment requests will be automatically granted.
Explanation All enrollment requests will be granted automatically.
Recommended Action No action is required.
Error Message%PKI-6-CS_GRANT_AUTO_RA : Enrollment requests coming from known RAs will be automatically granted.
Explanation Enrollment requests coming from known RAs will be automatically granted.
Recommended Action No action is required.
Error Message%PKI-6-CS_REJECT_AUTO : All enrollment requests will be automatically rejected.
Explanation All enrollment requests will be automatically rejected.
Recommended Action No action is required.
Error Message%PKI-3-GETCARACERT : Failed to receive RA/CA certificates.
Explanation A failure was encountered while CA or RA certificates were being parsed or processed.
Recommended Action Check the status of the certificate, or contact the CA administrator.
Error Message%PKI-3-INVALIDCACERT : Failed to process CA certificate.
Explanation The CA certificate that was received from the CA server could not be processed.
Recommended Action Enter the parser command.
Error Message%PKI-3-INVALID_INPUT : The input to the parser command is not correct
Explanation The arguments supplied with the parser command are not correct.
Recommended Action Reenter the command.
Error Message%PKI-4-NOAUTOSAVE : Configuration was modified. Issue "write memory" to save new certificate
Explanation The auto-enroll feature has obtained a new router key pair and certificate. However, the running configuration was previously modified.
Recommended Action Enter the write memory command to save the new certificates and keys.
Error Message%PKI-4-NOSHADOWAUTOSAVE : Configuration was modified. Issue "write memory" to save new IOS CA certificate
Explanation Cisco IOS CA Rollover has generated a shadow CA keypair and certificate. However, the running configuration was previously modified.
Recommended Action Enter the write memory command to save the new certificate(s) and key(s).
Error Message%PKI-6-PKCS12EXPORT_FAIL : PKCS #12 Export Failed.
Explanation An attempt to generate and export information conforming to the PKCS #12 format has failed.
Recommended Action No action is required.
Error Message%PKI-6-PKCS12EXPORT_SUCCESS : PKCS #12 Successfully Exported.
Explanation Information conforming to the PKCS #12 format has been generated and successfully exported.
Recommended Action No action is required.
Error Message%PKI-6-PKCS12IMPORT_FAIL : PKCS #12 Import Failed.
Explanation An attempt to import information conforming to the PKCS #12 format has failed.
Recommended Action No action is required.
Error Message%PKI-6-PKCS12IMPORT_SUCCESS : PKCS #12 Successfully Imported.
Explanation Information conforming to the PKCS #12 format has been successfully imported.
Recommended Action No action is required.
Error Message%PKI-3-POLLCACERT : Polling CA certificate .....
Explanation The CA certificate is being polled.
Recommended Action Check to see if the CA server or the LDAP server is online.
Error Message%PKI-3-POLLRACERT : Polling RA certificate .....
Explanation The RA certificate is being polled.
Recommended Action Check to see if the CA server or the LDAP server is online.
Error Message%PKI-3-POLLROUTERCERT : Polling Router certificate .....
Explanation The router certificate is being polled.
Recommended Action Check to see if the CA server or the LDAP server is online.
Error Message%PKI-3-QUERYCACERT : Failed to query CA certificate.
Explanation A CA certificate from the CA server could not be queried.
Recommended Action Enter the parser command.
Error Message%PKI-6-SHADOWAUTOSAVE : Running configuration saved to NVRAM
Explanation IOS CA Rollover has generated a shadow CA keypair and certificate, and has done an automatic "write memory" to save them.
Recommended Action No action is required.
Error Message%PKI-3-QUERY_KEY : Querying key pair failed.
Explanation A public key or private key query attempt using the subject name has failed.
Recommended Action Resubmit the enrollment request. Check the subject name.
Error Message%PKI-3-SOCKETSELECT : Failed to select the socket.
Explanation The socket could not be selected.
Recommended Action Check for a TCP of socket debugging message to attempt to investigate the problem.
Error Message%PKI-3-SOCKETSEND : Failed to send out message to CA server.
Explanation A message could not be sent to the CA server. This failure is caused by a problem with the HTTP transaction.
Recommended Action Check the HTTP connection to the CA server.
PLATFORM Messages
The following are platform-specific messages.
Error Message%PLATFORM-4-COOKIE : Corrupt or missing MAC address cookie\n using random base [enet]
Explanation The contents of the MAC address EEPROM is invalid. The system is providing a random MAC address.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PLATFORM-4-DEVICE : Missing device information for [chars] (Slot [dec], Device Instance [dec])
Explanation The system software was unable to retrieve a pointer to a device information structure for the specified device.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PLATFORM-3-FATALCINNAMON : The FPGA controller has received a fatal interrupt, reg=[hex], mask=[hex], config=[hex] - [chars]
Explanation The FPGA controller has received a fatal interrupt. This condition might be caused by either a hardware or a software problem.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PLATFORM-3-FATALPXF : Fatal PXF interrupt, reg=[hex], mask=[hex], config=[hex] - [chars]
Explanation The PXF has issued a fatal interrupt. This condition may be caused by a hardware or a software problem.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PLATFORM-3-FPGAUPDBRDNOACCESS : Cannot access Slot [dec], FPGA version check and update skipped.
Explanation The line card or NSE cannot be accessed to perform a FPGA version check and update.
Recommended Action Do not remove any line card or NSE during the FPGA version check and update process. If the line card or NSE was not removed during the process, 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PLATFORM-3-FPGAUPDFAIL : Slot [dec] [chars] update from version [dec].[dec] to version [dec].[dec] failed. System may not function properly.
Explanation An attempt to update the FPGA has failed.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PLATFORM-3-FPGAUPDLCNOACTIVE : Slot [dec] linecard activation failed after FPGA update, error code = [dec]
Explanation The line card could not be activated after the FPGA had been updated.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PLATFORM-3-FPGAUPDLCNODEACTIVE : Slot [dec] linecard deactivation failed after FPGA update, error code = [dec]
Explanation The line card could not be deactivated after the FPGA had been updated.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PLATFORM-3-FPGAUPDLCNORESET : Slot [dec] linecard reset failed after FPGA update
Explanation The line card could not be reset after the FPGA had been updated.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PLATFORM-3-FPGAUPDNOACCESS : Cannot access Slot [dec] [chars], FPGA version check and update skipped.
Explanation The FPGA flash memory could not be accessed.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PLATFORM-4-FPGAUPDNOBNDLIMG : System cannot retrieve a compatible bundled FPGA image for slot [dec] [chars] (hardware version [dec].[dec]), FPGA version check and update skipped
Explanation The Cisco IOS software does not contain a compatible FPGA bundled image.
Recommended Action Check the field alerts and other related documents to ensure that the line card or NSE is supported. If required, upgrade the hardware or Cisco IOS software.
Error Message%PLATFORM-3-FPGAUPDNORELOAD : After FPGA update, Primary NSE reload was aborted. Need to reload in order for the new FPGA image(s) to take effect
Explanation The FPGA of the primary NSE was updated. However, the system did not reload.
Recommended Action Reload the primary NSE. If the NSE cannot be reloaded, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PLATFORM-6-FPGAUPDSKIP : Slot [dec] [chars] update skipped.
Explanation The FPGA update operation has been skipped, even though the current FPGA version is potentially incompatible.
Recommended Action Check the field alerts and other related documents, and update the FPGA if required.
Error Message%PLATFORM-6-FPGAUPDSUCCESS : Slot [dec] [chars] successfully updated from version [dec].[dec] to [dec].[dec].
Explanation The FPGA update has successfully completed.
Recommended Action No action is required.
Error Message%PLATFORM-3-FPGAUPDUITIMEOUT : System FPGA update skipped for slot [dec] and up due to no user response.
Explanation The FPGA update operation was skipped because no response was received from the user.
Recommended Action Enter the upgrade fpga all command in privileged EXEC mode to start the update process, which checks the FPGA versions and ensures that all the FPGAs in the system are compatible.
Error Message%PLATFORM-4-HWTIMERALLOCFAIL : Failed to allocate hardware timer for [chars]
Explanation The system software was unable to allocate a hardware timer from the system hardware timer pool. Because of this condition, the feature indicated in the message text will not be functional.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PLATFORM-3-LCCONFIG : Exceeds [dec] [chars]
Explanation The aggregate throughput of line cards has exceeded the rated capacity of this system.
Recommended Action Refer to the configuration guidelines for the maximum allowed aggregate throughput of line cards for the system.
Error Message%PLATFORM-3-MINIMALBOOT : System in minimal boot mode.
Explanation The system has initialized in "minimal boot" mode. This condition may be caused by incompatible FPGA or hardware versions or an FPGA that was not properly loaded.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PLATFORM-4-NOCPUVER : Invalid CPU ID, assuming revision 1
Explanation The CPU ID could not be read from EEPROM. This condition is most likely due to a hardware failure.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PLATFORM-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation A MAC address could not be allocated because of an incorrect slot and port combination. This combination exceeds the maximum number of available hardware ports and slots.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PLATFORM-3-SPEED_DUPLEX_MISMATCH : [chars] does not support mixed auto and non-auto speed and duplex settings. Default both speed and duplex to auto.
Explanation The hardware does not support speed and duplex settings that are a mixture of autonegotiated and nonautonegotiated. Both the speed and duplex settings will default to autonegotiated.
Recommended Action Ensure that the speed and the duplex settings of the port are both set to autonegotiated, or both set to nonautonegotiated. Any mismatch results in both settings default to autonegotiated.
PM3387 Messages
The following are One-port Gigabit Ethernet HWIC-1GE-SFP messages.
Error Message%PM3387-3-BAD_CLOCK : Clock is missing at DLL0_RUN
Explanation MAC can not obtain a clock on the system bus. This condition indicates a hardware problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PM3387-3-MISSING_RES : Missing resistors on TDI and TMS
Explanation A problem occurred while MAC hardware was being assembled. This condition indicates a hardware problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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.
PM_DB_HA Messages
The following are port management database high availability client messages.
Error Message%PM_DB_HA-3-CHKPT_INTERNAL : Internal PM DB checkpointing error [[chars]]
Explanation An internal error has occurred within the PM DB checkpointing code.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PM_DB_HA-3-OBJ_MISSING : Missing entry for [chars] [[dec]] for slot [dec] to populate [chars]
Explanation The system cannot populate the object with the checkpoint data.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PM_DB_HA-3-SPE_SM_FAIL : Fail to simulate the [chars] event during the switchover
Explanation The system cannot replay the event on the newly active RSC during a switchover.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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.
POLICY_API Messages
The following are policy API messages.
Error Message%POLICY_API-4-POLICYDYNCLR : Dynamic policy on intf:[chars] cleared. Static policy in use.
Explanation A dynamic policy was attempting to override the static policy. The dynamic policy has been cleared, the static policy is now in effect.
Recommended Action No action is required.
Error Message%POLICY_API-4-POLICYOVERIDE : Dynamic policy overriding static on intf:[chars]
Explanation Both a static policy and a dynamic policy are configured on the interface. The dynamic policy will override the static policy.
Recommended Action If preferred, remove the static policy configuration.
Error Message%POLICY_API-4-POLICYSTATICCLR : Static policy on intf:[chars] cleared. Dynamic policy in use.
Explanation A dynamic policy has overridden the static policy. The static policy has been cleared.
Recommended Action No action is required.
POLICY_MANAGER Messages
The following are Policy Manager messages.
Error Message%POLICY_MANAGER-2-INIT_FAILURE : Init failure: [chars]
Explanation A problem occurred during the initialization of the Policy Manager during system initialization.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POLICY_MANAGER-3-INVALID_ACTION : Invalid action
Explanation An invalid action was performed by the Policy Manager.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POLICY_MANAGER-3-INVALID_PARAMETERS : A call to Policy Manager is made with invalid parameters
Explanation A call to the Policy Manager was made with one or more invalid parameters.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POLICY_MANAGER-3-INVALID_SEVERITY : Invalid event severity [hex]
Explanation The event that was received by the Policy Manager contained an invalid severity and was, therefore, not processed.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POLICY_MANAGER-2-NO_FREE_EVENT_BUFFERS : Event pool depleted: [chars]
Explanation The event pool has been depleted. There are no free buffers to process the event.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POLICY_MANAGER-3-NO_FREE_POLICY_IDS : No more Policy IDs available
Explanation There are no more Policy IDs that can be allocated. Policy Manager policies can no longer be created.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POLICY_MANAGER-3-NULL_ACTION_ROUTINE : NULL action routine invoked
Explanation The Policy Manager attempted to invoke an action that was of a null value.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POLICY_MANAGER-3-PRE_INIT_CALL : Policy Manager routine called prior to initialization
Explanation The Policy Manager component was called prior to its initialization.This action could result in vital information being lost.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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.
POS Messages
The following are Packet over SONET subsystem messages.
Error Message%POS-1-DISCOVER : [chars]([dec]) Only found [dec] interfaces, deactivating line card
Explanation The PoS hardware has failed. An incorrect number of interfaces has been discovered.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POS-1-HWFAIL : [chars]([dec]) Hardware failure. [chars]
Explanation The PoS line card has encountered a hardware failure. The line card will be deactivated.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POS-1-INITFAIL : [chars] initialization failed
Explanation The PoS line card failed to complete its hardware initialization.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POS-3-INTERNAL : POS internal error, [chars] [dec] [dec]
Explanation An internal PoS error 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POS-3-INTERNALCMD : POS LC command internal error, [chars] [dec] [dec]
Explanation A command error has occurred on an internal PoS line 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POS-3-INTERNALEVT : POS LC Event internal error, [chars] [dec] [dec]
Explanation A command error has occurred on an internal PoS line 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POS-3-MIBINITFAIL : POS MIB initialization failed, [chars] [dec]
Explanation The MIB for PoS could not be initialized.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POS-3-REDFATALLCEVT : Fatal error event on i/f ([chars]) reason: [chars]
Explanation A fatal event has occurred on an internal redundant line 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POS-4-REDINLCEVT : Redundant inactive i/f ([chars]) event: [chars], reason: [chars]
Explanation An event has occurred on an internal redundant line 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POS-1-TRESFAIL : [chars]([dec]/[dec]) Failed to obtain PXF resources, error=[dec], shutting down interface
Explanation The PoS line card failed to get the PXF resources. The interface will be shut down if it was operational, or will be deactivated if this card was activated by an OIR operation.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POS-3-UNSUPPORTED : [chars]([dec]) [chars]\n
Explanation The PoS hardware is not supported on this platform.
Recommended Action Upgrade your system.
POSDW Messages
The following are Packet over SONET double-wide PCI port adapter driver messages.
Error Message%POSDW-1-DISCOVER : Only found [dec] interfaces on bay [dec], shutting down bay
Explanation The PA-POS-OC3 port adapter hardware could not be initialized. An incorrect number of interfaces were discovered during initialization.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POSDW-1-INITFAIL : [chars] init timed out
Explanation The PA-POS-OC3 port adapter driver could not complete its hardware initialization.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POSDW-3-NOTPOSDW : Device reported [hex]
Explanation The PA-POS-OC3 port adapter hardware could not be initialized. An incorrect device identifier was found.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POSDW-3-OWNERR : [chars] packet buffer, pak=[hex]
Explanation A software or hardware error has occurred. The PA-POS-OC3 port adapter driver detected that the transmit ring is in an inconsistent and unrecoverable state.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POSDW-3-UNSUPPORTED : [chars]
Explanation The PA-POS-OC3 port adapter is not supported on this platform. The message text specifies the part of the system that requires an upgrade.
Recommended Action Upgrade your system to a platform that supports the PA-POS-OC3 port adapter. Refer to the system log to determine the part of your system that requires an upgrade.
POS_GIGE Messages
The following are Packet over SONET (PoS) Gigabit Ethernet messages.
Error Message%POS_GIGE-3-INTERNAL : POS_GIGE internal error, [chars] [dec]
Explanation An internal POS_GIGE error 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POS_GIGE-3-MAJOR_FAULT : POS_GIGE unrecoverable error, [chars], error_code=[hex]
Explanation An internal POS_GIGE operation error 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POS_GIGE-3-POS_GIGE_MISMATCH : [chars], expected [hex], actual [hex]
Explanation PCI initialization has failed.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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.
POT1E1 Messages
The following are Versatile Interface Processor (VIP) multichannel port adapter messages.
Error Message%POT1E1-3-FREEDMFATAL : Bay [dec]: freedm reset, command-status register [hex]
Explanation The POT1E1 port adapter has experienced a fatal problem related to FREEDM.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%POT1E1-2-NOACCPTR : VC=[dec] [chars]
Explanation The POT1E1 port adapter could not increment the pointer count.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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, show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides, and your pertinent troubleshooting logs.
Error Message%POT1E1-2-NOINC : [chars]
Explanation The POT1E1 port adapter encountered a null access pointer while it was incrementing the pointer count.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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, show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides, and your pertinent troubleshooting logs.
Error Message%POT1E1-2-QTAIL : Qhead=[hex] particle_count=[dec] size=[dec]
Explanation The POT1E1 port adapter encountered a null queue heading.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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, show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides, and your pertinent troubleshooting logs.
Error Message%POT1E1-2-TXBADVC : [chars], vc [dec]\n
Explanation The POT1E1 contained an invalid Tx VC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number of the affected line card, to gather data that may help identify the nature of the error. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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, show tech-support and show controllers vip slot-number tech-support commands and your pertinent troubleshooting logs.
PPP Messages
The following are Point-to-Point Protocol (PPP) messages.
Error Message%PPP-4-NOGROUP : Multilink Group Interface was not created. [chars]
Explanation A multilink group interface could not be created. Most likely the requested interface exceeded the platform MLP group interface limit.
Recommended Action No action is required. Note that the platform does not support additional MLP interfaces.
PQUICC Messages
The following are MPC860 quad integrated communications controller messages.
Error Message%PQUICC-1-QMC_GLOBAL_ERROR : PQUICC([dec]/[dec]), Global error [hex] in QMC
Explanation One or more of the channels served by the QMC instance has encountered one of these conditions:
–
Transmitter underflow
–
–
Normally this problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%PQUICC-3-SPURIOUS_INTERRUPT : Interface card in slot [dec] generated a spurious interrupt
Explanation The interface card on the router, which is not supported by the installed image of Cisco IOS software, generated a spurious interrupt that cannot be processed.
Recommended Action No action is required. To avoid seeing this message in the future, remove the unsupported card or use a Cisco IOS software image that supports it.
PQUICC_ETHERNET Messages
The following are Ethernet MPC860 quad integrated communications controller messages.
Error Message%PQUICC_ETHERNET-4-BABBLE : PQUICC/[chars], Babble error
Explanation The transmitter has been on the channel longer than the time it takes to transmit the largest frame.
Recommended Action The system should recover. No action is required.
Error Message%PQUICC_ETHERNET-5-COLL : PQUICC/[chars], Excessive collisions, TDR=[dec], TRC=[dec].
Explanation Ethernet or Fast Ethernet has detected multiple collisions. This condition may occur under heavy loads.
Recommended Action The system should recover. No action is required.
Error Message%PQUICC_ETHERNET-5-EXCESSCOLL : PQUICC/[chars], Excessive collision
Explanation Ethernet or Fast Ethernet has detected multiple collisions. This condition may occur under heavy loads.
Recommended Action The system should recover. No action is required.
Error Message%PQUICC_ETHERNET-1-INITFAIL : PQUICC/[chars], Init failed, CSR[dec]=[hex]
Explanation The software failed to initialize or restart an Ethernet or Fast Ethernet interface.
Recommended Action Clear the interface. If the message recurs, call your
technical support representative for assistance.Error Message%PQUICC_ETHERNET-1-INITFAILP : PQUICC/[chars], Init failed, CSR[dec]=[hex]
Explanation The PQUICC Ethernet could not allocate an I/O buffer pool.
Recommended Action Clear the interface. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PQUICC_ETHERNET-5-LATECOLL : PQUICC/[chars], Late collision
Explanation Late collisions have occurred on the Ethernet or Fast Ethernet interface.
Recommended Action If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. For regular Ethernet, the system should recover. No action is required.
Error Message%PQUICC_ETHERNET-5-LOSTCARR : PQUICC/[chars], Lost carrier. Transceiver problem?
Explanation The cable or transceiver is not connected.
Recommended Action Connect the cable or transceiver.
Error Message%PQUICC_ETHERNET-1-MEMERR : PQUICC/[chars], Memory error, CSR[dec]=[hex]
Explanation The interface could not access system resources for a long period of time. This condition may occur under very heavy loads.
Recommended Action The system should recover. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PQUICC_ETHERNET-2-NOISL : Interface [chars] does not support ISL
Explanation The interface cannot be configured as an ISL trunk.
Recommended Action Check the interface or system configuration.
Error Message%PQUICC_ETHERNET-3-OVERFLO : PQUICC/[chars], Receive overflow
Explanation While a frame was being received, the local buffer of the controller chip transmitted insufficient data because data could not be transferred to DRAM quickly enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%PQUICC_ETHERNET-3-OWNERR : PQUICC/[chars], Buffer ownership error, pak=[hex]
Explanation The software detected an error in while attempting to determine the ownership of the descriptor.
Recommended Action Attempt to load a later version of Cisco IOS software on the system. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PQUICC_ETHERNET-1-SHOWFAIL : PQUICC/[chars], Memory error, CSR[dec]=[hex]
Explanation The PQUICC Ethernet could not allocate sufficient memory to display the controller.
Recommended Action Clear the interface. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PQUICC_ETHERNET-3-UNDERFLO : PQUICC/[chars], Transmit underflow
Explanation While a frame was being transmitted, the local buffer of the controller chip received insufficient data because data could not be transferred to the chip quickly enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
PQUICC_FE Messages
The following are Fast Ethernet MPC860 quad integrated communications controller messages.
Error Message%PQUICC_FE-4-BABBLE : PQUICC/FE([dec]/[dec]), Babble error, CSR[dec]=[hex]
Explanation The transmitter has been on the channel longer than the time it takes to transmit the largest frame.
Recommended Action The system should recover. No action is required.
Error Message%PQUICC_FE-5-COLL : PQUICC/FE([dec]/[dec]), Excessive collisions, TDR=[dec], TRC=[dec].
Explanation Ethernet or Fast Ethernet has detected multiple collisions. This condition may occur while the system is experiencing heavy loads.
Recommended Action The system should recover. No action is required.
Error Message%PQUICC_FE-5-EXCESSCOLL : PQUICC/FE([dec]/[dec]), Excessive collision
Explanation Ethernet or Fast Ethernet has detected multiple collisions. This condition may occur while the system is experiencing heavy loads.
Recommended Action The system should recover. No action is required.
Error Message%PQUICC_FE-1-INITFAIL : PQUICC/FE([dec]/[dec]), Init failed, CSR[dec]=[hex]
Explanation The software failed to initialize or restart an Ethernet or Fast Ethernet interface.
Recommended Action Clear the interface. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PQUICC_FE-1-INITFAILP : PQUICC/FE([dec]/[dec]), Init failed at [chars]
Explanation The FEC could not allocate an I/O buffer pool.
Recommended Action Clear the interface. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PQUICC_FE-5-LATECOLL : PQUICC/FE([dec]/[dec]), Late collision
Explanation Late collisions have occurred on the Ethernet or Fast Ethernet interface.
Recommended Action If the interface is a Fast Ethernet interface, verify that both peers are in the same duplex mode. For regular Ethernet, the system should recover. No action is required.
Error Message%PQUICC_FE-5-LOSTCARR : PQUICC/FE([dec]/[dec]), Lost carrier. Transceiver problem?
Explanation The cable or transceiver is not connected.
Recommended Action Connect the cable or transceiver.
Error Message%PQUICC_FE-1-MEMERR : PQUICC/FE([dec]/[dec]), Memory error, CSR[dec]=[hex]
Explanation The interface could not access system resources for a long period of time. This problem may occur under very heavy system loads.
Recommended Action The system should recover. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PQUICC_FE-2-NOISL : Interface [chars] does not support ISL
Explanation The interface cannot be configured as an ISL trunk.
Recommended Action Check the configuration of the interface.
Error Message%PQUICC_FE-3-OVERFLO : PQUICC/FE([dec]/[dec]), Receive overflow
Explanation While receiving a frame, the local buffer of the controller chip transmitted insufficient data because data could not be transferred to DRAM quickly enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%PQUICC_FE-3-OWNERR : PQUICC/FE([dec]/[dec]), Buffer ownership error, pak=[hex]
Explanation The software detected an error regarding the ownership of a descriptor.
Recommended Action Attempt to use a later version of the Cisco IOS software. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PQUICC_FE-1-SHOWFAIL : PQUICC/FE([dec]/[dec]), Memory error at [chars]
Explanation The FEC could not allocate sufficient memory to display a controller.
Recommended Action Clear the interface. 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PQUICC_FE-3-UNDERFLO : PQUICC/FE([dec]/[dec]), Transmit underflow
Explanation While a frame was being transmitted, the local buffer of the controller chip received insufficient data because data could not be transferred to the chip quickly enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
PS Messages
The following are power supply messages.
Error Message%PS-3-DCOUTPUTVOLTFAIL : System detected Power System [dec] DC FAIL condition.
Explanation The power system has experienced a DC failure. One of the DC outputs has failed on the power supply.
Recommended Action Identify the DC output that has failed and replace the failed power supply.
Error Message%PS-3-DCOUTPUTVOLTOK : Power System DC condition is now normal
Explanation The power system DC is operating normally.
Recommended Action This is an informational message only. No action is required.
Error Message%PS-1-INITSYS : [chars]
Explanation An environmental monitor process could not be created. The most likely reason for this condition is a lack of system memory.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PS-3-INPUTVOLTFAIL : System detected Power System [dec] AC FAIL condition.
Explanation The power system has experienced an AC failure. One of the AC inputs has failed on the power supply.
Recommended Action Identify the AC input that has failed. Ensure that the AC circuit in your building is operational, verify that the power cord is plugged into the power supply, and ensure that the AC power switch on the power supply is turned on.
Error Message%PS-3-INPUTVOLTOK : Power System AC condition is now normal
Explanation The power system AC is operating normally.
Recommended Action This is an informational message only. No action is required.
Error Message%PS-3-MULTFAIL : There is more than one failure with the Power System [dec]; please resolve problems immediately
Explanation The power system has experienced multiple failures. This message indicates a critical condition.
Recommended Action Examine the LEDs on the front of the power supply to identify the failures.
Error Message%PS-3-NOMEM : OUT of Memory: [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%PS-3-OVERTEMP_OK : System temperature is now normal.
Explanation The system is operating at a normal temperature. The system previously detected an over temperature condition which has now cleared. This was most likely caused by high ambient temperature where the router is located.
Recommended Action No action is required.
Error Message%PS-3-PSOK : Power System is now normal
Explanation The power system is operating normally.
Recommended Action This is an informational message only. No action is required.
Error Message%PS-3-THERMAL : System detected Power System [dec] THERMAL FAIL condition.
Explanation The power system has experienced an over-temperature condition.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PS-3-THERMOK : Power System THERMAL condition is now normal.
Explanation The power system thermal condition is now normal. The power supply previously detected an over-temperature condition that has now cleared. This condition was most likely due to high ambient temperature where the power supply is located. A power system thermal failure can also be caused by a fan failure in the power supply.
Recommended Action No action is required.
PT Messages
The following are protocol translation messages.
Error Message%PT-3-BADRULEDELETE : Error deleting ruleset[chars], [chars].
Explanation An internal software error has occurred.
Recommended Action 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PT-3-BADRULEUNLOCK : Invalid unlock on ruleset[chars], [chars].
Explanation An internal software error has occurred.
Recommended Action 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PT-3-BADSCOPERATION : Invalid [chars] of subcommand [dec] on ruleset[chars].
Explanation An internal software error has occurred.
Recommended Action 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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PT-6-INVOPERATION : An invalid [chars] operation defined for [chars] parameter [chars].
Explanation An internal data consistency error has been detected. This is an internal verification message and does not affect system operation, but it does indicate a problem with the system that requires further investigation.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PT-3-NOOPERATION : No [chars] operation defined for [chars] parameter [chars].
Explanation An internal data consistency error has been detected.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PT-4-PARAMCHANGED : PT ruleset[chars]: [chars] parameter [chars] changed; [chars].
Explanation A protocol parameter value that was generated by a rule set was modified so that it would be valid for a protocol translation operation.
Recommended Action Review the rule set processing for the identified parameter to determine if it requires modification to generate a value that is within the range of values supported for protocol translation.
Error Message%PT-3-PARAMEVALERR : PT ruleset[chars] parameter error in [chars] line [dec]; [chars] [dec].
Explanation A parameter evaluation error was detected for the specified rule set, operation and line.
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PT-3-PARAMRESULTERR : PT ruleset[chars] protocol [chars] parameter [chars] parse error: [chars].
Explanation The final value of a protocol or parameter string for a rule set could not be decoded.
Recommended Action Review the rule set elements that set the parameter value to determine if the elements require modification to generate a valid result.
Error Message%PT-3-PARAMRESULTINVALID : PT ruleset[chars] protocol [chars] parameter [chars] invalid: [chars].
Explanation The value of a protocol or parameter for a rule set is not valid.
Recommended Action Review the rule set elements that set the parameter value to determine if the elements require modification to generate a valid result.
Error Message%PT-6-RULESETACCESS : Ruleset [chars] refused an incoming connection due to the access-class.
Explanation An incoming connection attempt that was matched by a protocol translation rule set has been refused because the source address failed the configured access class test for the rule set.
Recommended Action The network administrator may need to verify that the rule set access class configuration is appropriate.
Error Message%PT-6-RULESETLIMIT : Ruleset [chars] refused an incoming connection due to the max-user limit.
Explanation An incoming connection attempt that would normally be processed by a protocol translation rule set has been refused because the configured maximum-user limit has been exceeded.
Recommended Action Increase the configured maximum-user limit, if required.
Error Message%PT-4-RULESETWRITER : PT ruleset[chars] evaluation skipped; ruleset is being modified.
Explanation An incoming connection attempt was not evaluated by the identified protocol translation rule set because that rule set is in the process of being modified.
Recommended Action Allow the editing operation for the rule set to be completed before the incoming connection attempt is processed.
PVDM2 Messages
The following are PVDM2 SIMM messages.
Error Message%PVDM2-1-SIMM_FAILED : PVDM2 in slot [dec]: PVDM2 in subslot/pvdm slot [dec] initialization failed.
Explanation The PVDM that is plugged into the module failed during its initialization.
Recommended Action Check the part number on the PVDM to see if it is supported in the version of Cisco IOS software that is operational on the router. Ensure that the PVDM2 SIMM is not damaged. If you require further assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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%PVDM2-1-SIMM_UNKNOWN : PVDM2 in slot [dec]: PVDM SIMM in subslot/pvdm slot [dec]
has an unkown id of [hex].Explanation The software did not recognize the type of PVDM SIMM that was plugged in.
Recommended Action Check the part number on the PVDM to see if it is supported in the version of Cisco IOS software that is operational on the router. If you require further assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, 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.