-
Cisco IOS System Messages, Volume 2 of 2
-
System Messages Overview
-
MBUF through MODEM
-
MODEM_HIST through NSP
-
NSP_APS through POSDW
-
POSLC through PQUICC_ETHER
-
PQUICC_ETHERNET through RESOURCE_MON
-
RESYNCH through SDLC
-
SDLLC through SNAPSHOT
-
SNASW
-
SNMP through SWITCH_IF
-
SYS through TCPIP
-
TDM through TXCONN
-
UBR7200 through VPD
-
VPDN through XTAGATM
-
Volume 2 Glossary
-
Table Of Contents
NSP_APS Messages
The following are Cisco 6400 node switch processor (NSP) automatic protection switching (APS) messages.
Error Message%NSP_APS-4-SWITCH : Interface [chars] switched from [chars] to [chars] channel
Explanation The APS logic has determined that a switchover from one port to another was necessary and has switched the specified interface to another port.
Recommended Action No action is required.
NSP_DISK Messages
The following are NSP disk messages.
Error Message%NSP_DISK-1-BAD_MKDIR : Unable to create directory [chars]
Explanation The specified directory could not be created.
Recommended Action Verify that the disk is usable.
Error Message%NSP_DISK-1-BAD_ROOT : PCMCIA ATA disk directory hierarchy could not be created
Explanation The disk root specification is invalid. The directory hierarchy could not be created
Recommended Action Change the disk root specification.
Error Message%NSP_DISK-4-DISK_LOW : PCMCIA ATA disk is running low on space
Explanation The PCMCIA ATA disk has less than 4 Mb or 10% of the disk space left. There are too many files on the PCMCIA disk.
Recommended Action To make more space available, delete unused files on the PCMCIA disk.
Error Message%NSP_DISK-1-MISSING : PCMCIA ATA disk has failed or is missing from system
Explanation The PCMCIA ATA disk that is used to store NRP2 configurations is missing from the system.
Recommended Action If the PCMCIA ATA disk is not present in the NSP chassis, reinsert the PCMCIA disk into the NSP chassis.
Error Message%NSP_DISK-5-PRESENT_OK : PCMCIA ATA disk present/operational
Explanation The PCMCIA ATA disk that is used to store NRP2 configurations is present and operational.
Recommended Action No action is required.
Error Message%NSP_DISK-1-PROCESS : PROCESS Creation Failure
Explanation The processes that monitor the NSP disk could not be created.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%NSP_DISK-5-SPACE_OK : PCMCIA ATA disk has enough space for normal
Explanation The PCMCIA ATA disk has enough free space for normal operation.
Recommended Action No action is required.
Error Message%NSP_DISK-1-WRONG_TYPE : Wrong type of PCMCIA card is inserted to the system
Explanation Insertion of a PCMCIA ATA disk was expected, but the card that was inserted is not a PCMCIA ATA disk.
Recommended Action If the PCMCIA ADA disk is not present in the NSP chassis, reinsert it into the proper PCMCIA SLOT. Otherwise, replace the PCMCIA disk with a known good disk. If this problem persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NSP_DISK-1-ZERO_SPACE : PCMCIA ATA disk has no or little space
Explanation The PCMCIA ATA disk is running critically low on storage space. There are too many files on the PCMCIA disk.
Recommended Action To make more space available, delete unused files.
NSP_OIR Messages
The following are Cisco 6400 online insertion and removal (OIR) messages.
Error Message%NSP_OIR-3-ALOC_OIR_EVENT : OIR event structure allocation failure
Explanation An internal OIR element allocation failure has occurred. This error usually indicates a memory leak.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Restart and reboot the device at a convenient time. This problem will not affect normal operation; however, you will be unable to remove old hardware or insert new hardware and bring it online.
Error Message%NSP_OIR-3-BADCARD : Unrecognized Card, Driver for Card not available in system\n software, ignoring card type [hex]
Explanation The card that was inserted into the system was not recognized by the software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NSP_OIR-3-BAD_FULL_INS : Cannot enable half height card, redundancy conflict
Explanation A redundancy or card conflict with cards in an adjacent slot has occurred.
Recommended Action No action is required.
Error Message%NSP_OIR-3-BAD_HALF_INS : Cannot enable half height card, redundancy conflict
Explanation A redundancy or card conflict with cards in an adjacent slot has occurred.
Recommended Action No action is required.
Error Message%NSP_OIR-3-BADINS : Insufficient system resources to complete card insertion/redundancy request, Reverting Configuration
Explanation The internal data structures for the specified interface could not be allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NSP_OIR-6-FULL_CINS : Card [chars] inserted into slot: [dec]
Explanation A full card has been inserted into the slot.
Recommended Action No action is required.
Error Message%NSP_OIR-6-FULL_CREM : Card [chars] removed from slot: [dec]
Explanation A full card has been removed from the slot.
Recommended Action No action is required.
Error Message%NSP_OIR-6-FULL_ONLINE : Card [chars], slot: [dec], being brought online
Explanation A full card is being brought online.
Recommended Action No action is required.
Error Message%NSP_OIR-6-HALF_CINS : Card [chars] inserted into subslot: [dec]/[dec]
Explanation A half-height card has been inserted into the subslot.
Recommended Action No action is required.
Error Message%NSP_OIR-6-HALF_CREM : Card [chars] removed from subslot: [dec]/[dec]
Explanation A half-height card has been removed from the subslot.
Recommended Action No action is required.
Error Message%NSP_OIR-6-HALF_ONLINE : Card [chars], subslot: [dec]/[dec], being brought online
Explanation A half-height card is being brought online.
Recommended Action No action is required.
Error Message%NSP_OIR-3-INVCARD : Inserted card incompatible with previously removed card
Explanation The card that was inserted is not the same type as the card that was removed and is therefore invalid.
Recommended Action Insert a card similar to the one that was removed, or clear out the alarm source.
Error Message%NSP_OIR-3-INV_HWCFG1 : Invalid card/configuration in slot([dec]) Ignoring Card
Explanation The cards that are present in the chassis in the current mode are incompatible.
Recommended Action Remove the card that is causing the problem and clear out the alarm sources. Ensure that the cards are compatible; otherwise, they cannot run redundantly.
Error Message%NSP_OIR-3-INV_HWCFG2 : Cannot enable card slot([dec]) subslot
Explanation The cards that are present in the chassis in the current mode are incompatible.
Recommended Action Remove the card and clear out the alarms. The card could also be incompatible with existing cards and cannot run redundantly.
Error Message%NSP_OIR-4-INV_REDCFG : Redundancy submode not present!
Explanation The system configuration does not have the redundancy submode.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NSP_OIR-3-LONGSTALL : Long bus stall ([int] s) \nThe newly inserted card may not seated properly.\nPlease remove it and try again.
Explanation The newly inserted card has failed or is not properly seated.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NSP_OIR-6-UCARD_CREM : Card removed from subslot: [dec]/[dec] while processing Insertion
Explanation A card was removed during insertion processing.
Recommended Action No action is required.
Error Message%NSP_OIR-4-UNEXPECTED_OFFLINE : 6400 Card [dec]/[dec] found off line - will 'virtually' \n remove and reinsert to bring online
Explanation The specified card has gone offline. This problem may have been caused by a power loss.
Recommended Action The software will bring the card back online. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
NSPINT Messages
The following are network switch processor (NSP) interrupt infrastructure messages.
Error Message%NSPINT-3-INTERNAL_ERROR : no handler for index [dec]
Explanation An internal error has occurred. An interrupt has been detected for which no handler has been registered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NSPINT-5-SPURIOUS : Spurious level [dec] interrupt ([dec])
Explanation An interrupt has been detected for which no cause could be found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
OFFL Messages
The following Channel Interface Processor (CIP) messages are related to the offload protocol.
Error Message%OFFL-6-ALIASNOTFOUND : Attempt to delete non-existing alias.
Explanation The specified alias does not exist on the offload device.
Recommended Action Make sure that the offload device has the alias you are trying to delete. If it does, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-4-BADDESC : Socket descriptor [dec] in request is bad: state [chars] compare [dec]
Explanation The host sent a socket request with a socket descriptor that is invalid. The CMCC has sent an error response to this socket request. This could be a host error or a CMCC internal logic error.
Recommended Action This message is followed by a hex dump of the request. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-0-BADSCB : Unknown SCB type [dec]
Explanation An internal logic error has occurred. An attempt was made to free a buffer with an unknown type.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the messages and issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-BADSEQ : Socket request [chars] should be last in sequence
Explanation The host sent a socket request that should be the last in a sequence but is not. This error is caused either by an internal logic error or by an incompatibility between the offload code on the mainframe and the offload code on the CMCC. This message is followed by a hex dump of the request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OFFL-6-COMMAND : Unrecognized offload command code [dec]
Explanation The host sent an offload command with an invalid offload command code. The CMCC ignored the request.
Recommended Action Check to see if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OFFL-6-DUPALIAS : Alias already exists on the offload device.
Explanation The offload device already has the specified alias.
Recommended Action Enter the write terminal command to verify that the alias exists. If it does not, copy the error me exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OFFL-7-HEX16B : [hex]: [hex][hex][hex][hex] [hex][hex][hex][hex] [hex][hex][hex][hex] [hex][hex][hex][hex] [chars]
Explanation This message contains a hex dump of data associated with the immediately preceding error message.
Recommended Action Refer to the description of the immediately preceding CMCC error message for the recommended action.
Error Message%OFFL-7-HEX4W : [hex]: [hex] [hex] [hex] [hex] [chars]
Explanation This message contains a hex dump of data associated with the immediately preceding error message.
Recommended Action Refer to the description of the immediately preceding CMCC error message for the recommended action.
Error Message%OFFL-3-ILLALD : Illegal data alignment: [hex] + [dec] bytes >= [hex]. xfer_element = [hex]
Explanation An internal logic error has occurred. The data following an offload message header crossed a buffer boundary. The CMCC ignored the message. This error message is usually an indication that the CMCC has received bad data. Examples of such bad data are CLAW frames that are duplicated or arrive out of order. The offload messages contained in these corrupted CLAW frames are ignored, and this action can lead to hanging sessions or session loss.
Recommended Action Check to see if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-ILLALH : Illegal hdr alignment detected. Address [hex] + [dec] bytes > [hex]. xfer_element = [hex]
Explanation An internal logic error has occurred. An offload message header crossed a buffer boundary. The CMCC ignored the message. This error message is usually an indication that the CMCC has received bad data. Examples of such bad data are CLAW frames that are duplicated or arrive out of order. The offload messages contained in these corrupted CLAW frames are ignored, and this action can lead to hanging sessions or session loss.
Recommended Action Check to see if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-ILLEN : Illegal byte count in offload data. [dec] specified, [dec] available. xfer_element = [hex]
Explanation The buffer length field in the offload message header does not equal the size of the data buffer. This condition typically means that the mainframe has sent bad data to the offload device. Examples of such bad data are CLAW frames that are duplicated or arrive out of order. The offload messages contained in these corrupted CLAW frames are ignored, and this action can lead to hanging sessions or session loss.
Recommended Action Check to see if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-0-ILLFREE1 : SCB chain does not end with a read hdr
Explanation An internal logic error has occurred. An attempt was made to free an incomplete sequence of buffers.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the messages and issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-0-ILLFREE2 : SCB ends with a read hdr with the MTC bit set
Explanation An internal logic error occurred. An attempt was made to free an incomplete sequence of buffers.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the messages and issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-ILLNUM : Illegal number of socket requests. Rejected at [dec]
Explanation The CMCC has received a CLAW frame with too many offload messages. This condition typically means that the mainframe has sent bad data to the offload device. Examples of such bad data are CLAW frames that are duplicated or arrive out of order. The offload messages contained in these corrupted CLAW frames are ignored, and this action can lead to hanging sessions or session loss.
Recommended Action Check to see if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-ILLRST : Received restart with [dec] intf, [dec] is max. xfer_element = [hex]
Explanation The host has sent an offload restart request with too many defined interfaces.
Recommended Action The CMCC has ignored the request. Check your host configuration for this offload device. If you cannot find the problem, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OFFL-6-LONGREC : Attempt to transmit too large a record
Explanation The amount of data being read by the channel exceeded the size of the read channel command word. The CMCC freed the buffers associated with this read operation and continued.
Recommended Action This error message typically means that the host code and the CMCC code were out of synchrony on the read subchannel. Sometimes the condition corrects itself, but most of the time the subchannel has to be restarted, either by varying the device offline on the host or by unconfiguring and reconfiguring the affected offload device.
Error Message%OFFL-3-MISRST : Received restart [chars] with unknown IP [dec].[dec].[dec].[dec]
Explanation The host has sent an offload restart request with an unknown IP address for the API link. The CMCC has ignored the mismatch.
Recommended Action Look for the DEVICE statement for the correct offload device in your TCPIP profile. Check the IP address on the LINK statement for the API link and compare that address with the IP address configured on the offload configuration command of your CMCC. Correct your configuration so the two IP addresses match.
Error Message%OFFL-0-NOMBUF : Out of mbuf's for handling socket operations
Explanation An internal logic error has occurred. Not enough memory buffers were allocated to handle the current offload socket operation.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the messages and issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-NOMEM : Not enough memory to start offload tasks
Explanation Not enough free memory is available to start the TCP/IP offload tasks. The configuration request was ignored.
Recommended Action Install more memory for the CMCC, or configure fewer devices.
Error Message%OFFL-3-NOMEMSOCK : Not enough memory to process socket requests, [dec] open, [dec] in holddown
Explanation Not enough free memory is available to process a socket request. The socket request failed.
Recommended Action Install more memory for the CMCC, configure fewer devices, or limit the number of sessions through this offload device.
Error Message%OFFL-3-NOMEMT : Insufficient memory ([chars]) for offload packet trace.
Explanation Not enough free memory is available for TCP/IP offload PKTTRACE. Tracing of a packet is skipped.
Recommended Action Refine (limit) the PKTTRACE option on the mainframe to reduce the number of packets being traced.
Error Message%OFFL-0-NOPEND : Trying to free buffer when no send is pending. Operation: [dec]
Explanation An internal logic error has occurred. A request to free a send buffer was made even though there is no send pending.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the messages and issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-6-OFFLNOTFOUND : No offload device found.
Explanation No offload device was found for the IP address for which an alias is being configured.
Recommended Action Make sure the offload address specified in the offload alias command matches an offload configuration command. If an offload device exists for the specified IP address, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-PENDREQ : Pending request [hex] deleted due to new request [hex]
Explanation The offload application had to save a socket request for later execution while another request of the same type was pending. The first request was dropped. This situation typically means that the mainframe has sent duplicate CLAW frames. Depending on what kind of offload message was duplicated, a variety of effects may follow, from nothing to session loss or even data corruption.
Recommended Action This error message is typically followed by a hex dump. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-REGERR : Register of offload PKTTRACE failed. Packet tracing skipped.
Explanation An internal error has occurred. The callback registry refused to add the offload tracing function to its list. The tracing of packets is skipped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OFFL-3-REQFORM : Socket request [dec] uses invalid parameters. Offset [dec]: [hex]
Explanation The host sent a socket request with an invalid parameter. The CMCC responded with an error code.
Recommended Action Check to see if there were any special events that coincided with this error message, such an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-REQLEN : Socket request [dec] has wrong length [dec]
Explanation The host has sent a socket request with an incorrect length. The CMCC responded with an error code.
Recommended Action Check to see if there were any special events that coincided with this error message, such an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-REQTYPE : Unknown [chars] socket request code [dec]
Explanation The host sent a socket request with an unknown type. An example could be an IOCTL request with a type code that is not implemented in the current release of CMCC microcode. The CMCC responded with an error code.
Recommended Action Check to see if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-4-SENDERR : Bad serial number [hex] in send request - expected [hex]
Explanation The host sent a Send socket request that had an unexpected serial number in the header. This is most likely a bug on the host.
Recommended Action The CMCC sent an error response to the Send socket request. The host TCP/IP stack will probably print the error message, "Unexpected result from Offload device..." Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OFFL-4-SOCLEFT : [dec] Sockets found after shutdown
Explanation When the offload application quit, it detected sockets that were still waiting for cleanup. This is an internal logic error.
Recommended Action This message should be preceded by other messages that provide further information. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-6-SOCREQ : Unrecognized socket request code [dec]
Explanation The host sent an offload socket request with an invalid request code. The CMCC responded with an error code. This error message can occur if a particular feature of the offload protocol is not supported by the current version of CMCC microcode. This error message can also occur if the CMCC has received bad data.
Recommended Action Check to see if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-6-TOOMANYALIASES : Attempt to configure too many aliases.
Explanation An attempt to configure too many aliases has been rejected. The offload application allows eight aliases per offload device.
Recommended Action If the number of existing aliases is less than the allowed maximum, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-6-TRDISA : Offload PKTTRACE disabled.
Explanation The mainframe TCP/IP has disabled PKTTRACE tracing. This can occur because the GTF was terminated or because a NOTRACE command was issued.
Recommended Action No action is required.
Error Message%OFFL-6-TRENAB : Offload PKTTRACE enabled.
Explanation The mainframe TCP/IP has enabled tracing using PKTTRACE.
Recommended Action No action is required.
Error Message%OFFL-4-TRRESU : Pending trace packets now [dec], tracing resumed ([dec]).
Explanation The number of outstanding trace packets pending to go to the mainframe has reached an acceptable level. Tracing of packets is resumed now, but some packets received or sent by this offload device were not traced during the suspension. The number in parentheses is the count of how many times a suspend occurred. The number serves as a correlator to the suspend message.
Recommended Action No action is required.
Error Message%OFFL-4-TRSUSP : Pending trace packet limit [dec] reached, tracing suspended ([dec]).
Explanation The limit of outstanding trace packets pending to go to the mainframe has been reached. Tracing of packets is suspended temporarily rather than continuing to flood the channel with trace data. Note: This means that some of the packets received or sent by this offload device will not be traced. The number in parentheses is the count of how many times suspend occurred. The number serves as a correlator to the resume message.
Recommended Action A message indicating the resumption of tracing will be seen when the congestion abates. No action is required; however, reducing the amount of tracing being done might minimize such suspensions.
Error Message%OFFL-6-UNEXP : Unexpected offload command code [dec]
Explanation The host sent an offload command with an offload command code that cannot be handled by the CMCC. The CMCC ignored the request.
Recommended Action Check to see if there were any special events that coincided with this error message, such an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-6-VIRTOFFL : Offload device may not be created on a virtual port adapter
Explanation An attempt was made to configure an offload device on the virtual port adapter. Offload devices are permitted on physical port adapters only.
Recommended Action The configuration request was ignored. No action required.
Error Message%OFFL-6-WRCHAIN : Received too long message, xfer_element [hex] chains to [hex]
Explanation The offload application received a message on the CLAW control link or the IP link that consisted of more than 16 CLAW buffers. This is not supported.
Recommended Action If this error is reproducible, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-6-WRITEREAD : Host Wrote data on read subchannel.
Explanation The mainframe has written data to the read subchannel. This is most likely the result of a misconfiguration under a VM guest in which the write device is attached to the read subchannel.
Recommended Action Check the device definitions on the host. If the system is running under VM, verify that the write device is attached to the write subchannel and the read device is attached to the read subchannel.
Error Message%OFFL-0-WRONGFREE : Trying to free mbuf out of sequence
Explanation An internal logic error has occurred. An unexpected address was specified in a request to free a buffer.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the messages and issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
OIR Messages
The following are online insertion and removal (OIR) messages.
Error Message%OIR-3-CARD_BADIDPROM : Card in slot [dec]/[dec] has an invalid card type in IDPROM
Explanation The line card IDPROM is unprogrammed or has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OIR-5-CARD_DETECTED : Card type [chars] ([hex]) in slot [dec]/[dec]
Explanation A card has been detected in the slot specified in the error message.
Recommended Action No action is required.
Error Message%OIR-3-CARD_UNSUPPORTED : Unsupported card type ([hex]) in slot [dec]/[dec].
Explanation The line card is not supported by this version of Cisco IOS software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OIR-6-CONSOLE : Changing console ownership to [chars] processor\n\n\n
Explanation The OIR facility has switched the console to the specified processor.
Recommended Action No action is required.
Error Message%OIR-6-CONSOLE : Card inserted in slot [dec], subcard [dec], interfaces administratively shutdown
Explanation The specified hot-swappable card was inserted in the system. The interfaces on the card will remain administratively disabled until specifically enabled, because they may need to be configured.
Recommended Action This is only an informational message. Configure the interfaces and enable them.
Error Message%OIR-3-LONGSTALL : Long bus stall ([int] ms), check for improperly seated cards
Explanation A problem with the system is preventing the CxBus or CyBus from operating. The likely reason is an improperly seated interface processor.
Recommended Action Ensure that all interface processor cards are firmly seated. If the problem reoccurs, it may indicate a hardware failure.
Error Message%OIR-3-LONGSTALL : Long bus stall ([int] s), the new PAM may not seated properly. Please remove it and try again.
Explanation A hot-swappable card that was inserted into the system has failed to respond. The card may not be properly seated.
Recommended Action Remove and re-insert the specified card. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OIR-3-MGMT_BC_INIT_FAIL : Unable to initialize management back card.
Explanation An attempt to create a valid management back card driver plug-in has failed. This condition was most likely caused by a memory allocation failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OIR-4-NOEOIR : [chars] [chars] version [int].[int] not capable of EOIR
Explanation The specified card is capable of OIR hot-swapping but is not capable of EOIR. Although no damage to the hardware will occur, insertion or removal of the card will cause a CBUS complex restart, which would be disruptive to traffic on other cards in the system.
Recommended Action Restrict insertion or removal of this card to times when a CBUS complex restart will be least disruptive. Alternatively, upgrade the card to the latest revision that supports EOIR.
Error Message%OIR-3-PLUGIN_ATTACH_FAIL : Unable to attach driver plugin in slot [dec]/[dec].
Explanation An attempt for an attach operation for a valid line card driver has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OIR-3-PLUGIN_INIT_FAIL : Unable to create driver plugin in slot [dec]/[dec].
Explanation An attempt to create a valid line card driver plug-in failed. This condition was most likely caused by a memory allocation failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OIR-3-PWRCYCLE : Card in slot [dec], is not responding; it is being power-cycled
Explanation The OIR facility has detected that the line card is unresponsive and has attempted to power-cycle the card.
Recommended Action No action is required.
Error Message%OIR-3-REMCARD : Card removed from slot [dec], subcard [dec], interfaces disabled
Explanation This message indicates that the specified hot-swappable card was removed from the system.
Recommended Action This is an informational message only. No action is required.
Error Message%OIR-3-SEATED : Insert/removal failed for slot [dec], check card seating
Explanation The OIR facility has detected an incorrectly seated card, which has caused the insertion or removal of this card to fail.
Recommended Action Reseat the card in the specified slot.
Error Message%OIR-3-STATE_MACHINE_BUG2 : card_oir_insert_card: already have [hex], removing.
Explanation The line card entered into the slot has a different configuration from the existing slot configuration. The existing slot configuration will be removed.
Recommended Action No action is required.
Error Message%OIR-3-UNKNOWN : Unknown card in slot [dec], card is being disabled
Explanation The OIR facility has detected a line card, but could not determine the type.
Recommended Action Reseat the card in the specified slot.
ON_DIAG Messages
The following are online diagnostics subsystem messages.
Error Message%ON_DIAG-3-ADMIN_DOWN : Test [chars] Failed, [chars] backcard is not present
Explanation The correct back card is not present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-ALARM_UPDATE : [chars], Testname ([chars]), Type ([chars])
Explanation The alarm for the test is being updated.
Recommended Action No action is required.
Error Message%ON_DIAG-3-BARIUM : Barium Device not accessible
Explanation An attempt to access the barium device failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-BARIUM_REG : [chars], expected [hex], actual [hex]
Explanation A barium register read operation has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-CACHE_CRITICAL_DOWN : [chars]: [chars]
Explanation A critical failure of cache hardware diagnostics has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-CACHE_SHUT_DOWN : [chars]: [chars]
Explanation A failure involving the shutdown of cache hardware diagnostics has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-CAM_REG : [chars], expected [hex], actual [hex]
Explanation An attempt to read the CAM Register has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-CBC_REG : [chars], expected [hex], actual [hex]
Explanation An attempt to read the CBC ASIC Register has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-EEPROM_SHUT_DOWN : [chars]
Explanation EEPROM hardware diagnostics have failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-EXCESS_RUN_TIME : Disabling the test ([chars])- run time, [dec] milliseconds, greater than the max. permissible run time [dec] milliseconds
Explanation The test is being disabled because it took excess run time.
Recommended Action No action is required.
Error Message%ON_DIAG-3-FIB_REG : [chars], expected [hex], [hex], [hex] and actual [hex], [hex], [hex]
Explanation An FIB register read operation has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-FLASH_CRITICAL_DOWN : [chars]: [chars]
Explanation A critical failure involving Flash memory hardware diagnostics has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-FLASH_SHUT_DOWN : [chars]: [chars]
Explanation A failure involving a shutdown of the Flash memory hardware diagnostics has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-GIGMAC_REG : [chars], expected [hex], actual [hex]
Explanation A GIGMAC register read operation has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-IOFPGA_SHUT_DOWN : [chars]: [chars]
Explanation IO FPGA hardware diagnostics have failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-MEMORY_CRITICAL_DOWN : [chars]: [chars]
Explanation A critical failure involving memory hardware diagnostics has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-MEMORY_SHUT_DOWN : [chars]: [chars]
Explanation A shutdown failure involving memory hardware diagnostics has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-MEMPOOL_BADCPU_TYPE : Bad cpucard type [dec] for [chars]
Explanation An administrative failure involving the memory pool software diagnostics has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-MEMPOOL_SHUT_DOWN : [chars]: [chars]
Explanation An administrative failure involving the memory pool software diagnostics has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-NVRAM_CRITICAL_DOWN : [chars]: [chars]
Explanation A critical failure involving NVRAM hardware diagnostics has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-NVRAM_SHUT_DOWN : [chars]: [chars]
Explanation A shutdown failure involving NVRAM hardware diagnostics has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-PCI_BRIDGE_SHUT_DOWN : DIAG Error: DEC21150/2115X or TI_21150 Vendor ID error [hex]
Explanation A shutdown failure involving the PCI bridge HW diagnostics has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-PCI_ID_SHUT_DOWN : [chars] [hex]
Explanation A shutdown failure involving the PCI ID hardware diagnostics has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-PKTTYPE_SHUT_DOWN : [chars]: [chars]
Explanation A shutdown failure involving packet type software diagnostics has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-POSIO_REG : [chars], expected [hex], actual [hex]
Explanation A POSIO register read operation has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-SAR_SHUT_DOWN : [chars]: [chars]
Explanation A SAR hardware diagnostics operation has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-SKY_REG : [chars], expected [hex], actual [hex]
Explanation A SKY register read operation has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-SPROCESS_SHUT_DOWN : [chars]: [chars]
Explanation A shutdown failure involving an S process software diagnostics operation has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ON_DIAG-3-TIB_REG : [chars], expected [hex], [hex], [hex] and actual [hex], [hex], [hex]
Explanation A TIB register read operation has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
OOBP Messages
The following are out-of-band port (OOBP) messages.
Error Message%OOBP-4-ASYNC_NO_RSP : Warning -- reset async oobp no response
Explanation The asynchronous driver does not respond to the async reset command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OOBP-4-OOBP_CANT_BE_USED : Warning -- oobp can't be used
Explanation The asynchronous driver cannot send out the OOBP message because there is no resource.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OOBP-4-TIMEOUT_AT_WRONG_STATE : Warning -- OOBP driver timeout at wrong state
Explanation An OOBP response timeout occurred at the wrong OOBP state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
OSPF Messages
The following are Open Shortest Path First (OSPF) messages.
Error Message%OSPF-5-ADJCHG : Process [dec], Nbr [IP_address] on [chars] from [chars] to [chars], [chars]
Explanation An OSPF neighbor has changed state. The message describes the change and the reason for it. This message appears only if the log-adjacency-changes command is configured for the OSPF process.
Recommended Action No action is required.
Error Message%OSPF-6-AREACHG : [IP_address][IP_netmask] changed from area [chars] to area [chars]
Explanation An OSPF configuration change has caused a network range to change areas.
Recommended Action No action is required.
Error Message%OSPF-6-BADCHKSUM : Checksum Failure in database in area [chars]
Link State Id [IP_address] Old Checksum [hex] New Checksum [hex]\nExplanation OSPF has detected a checksum error in the database that was caused by memory corruption.
Recommended Action Restart the OSPF process.
Error Message%OSPF-4-BADLENGTH : Invalid length [dec] in OSPF packet type [dec] from [IP_address] (ID [IP_address]), [chars]
Explanation The system has received an OSPF packet with a length field that is less than normal header size or that is inconsistent with the size of the IP packet in which it arrived. This problem indicates an error involving the sender of the packet.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPF-4-BADLSAMASK : Bad LSA mask: Type [dec], LSID [IP_address] Mask [IP_address] from [IP_address] \nNOTE: This route will not be installed in the routing table.
Explanation The router received an LSA with an invalid LSA mask. The cause is likely due to an invalid or incorrect configuration from the LSA originator.
Recommended Action Find the originating router of this LSA with the invalid mask and correct any misconfiguration of the LSA network. For further debugging help, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OSPF-4-BADLSATYPE : Invalid lsa: [chars] Type [dec], LSID [IP_address] from [IP_address], [IP_address], [chars]
Explanation The router has received an LSA with an invalid LSA type. The cause for this condition is either a memory corruption or unexpected behavior on a router.
Recommended Action Perform the following steps:
a.
From a neighboring address, locate the problem router.
b.
c.
d.
e.
f.
If you cannot determine the nature of the error from the collected information, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPF-4-CONFLICTING_LSAID : Found LSA with the same host bit set but using different mask\n Existing: LSA ID [IP_address][IP_netmask]\n New: Destination [IP_address][IP_netmask]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPF-3-DBEXIST : area [chars] lsid [IP_address] mask [IP_address] adv [IP_address] type [dec]
Explanation OSPF in having a problem locating the LSA. This condition could lead to a memory leak.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPF-4-DUP_RTRID_AREA : Detected router with duplicate router ID [IP_address] in area [chars]
Explanation OSPF has detected a router in the area that has the same router ID as this routing process. Duplicate router IDs may result in network instability, causing some destinations to be unreachable.
Recommended Action The OSPF router ID should be unique. Ensure that all routers in the area have a unique router ID.
Error Message%OSPF-4-DUP_RTRID_AS : Detected router with duplicate router ID [IP_address] in Type-4 LSA advertised by [IP_address]
Explanation The OSPF has received a hello packet from a neighbor that has the same router ID as this routing process. A full adjacency cannot be established.
Recommended Action The OSPF router ID must be unique. Change the router ID of the neighbor.
Error Message%OSPF-4-DUP_RTRID_NBR : OSPF detected duplicate router-id [IP_address] from [IP_address] on interface [chars]
Explanation OSPF has received a hello packet from a neighbor that has the same router ID as this routing process. A full adjacency cannot be established.
The OSPF router ID should be unique. Change the router ID of the neighbor.
Error Message%OSPF-4-ERRRCV : Received invalid packet: [chars] from [IP_address], [chars]
Explanation An invalid OSPF packet was received. Details are included in the error message. The cause might be a misconfigured OSPF or an internal error involving the sender.
Recommended Action Check the OSPF configuration of the receiver and the sender for inconsistency.
Error Message%OSPF-3-INTERNALERR : Internal error: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OSPF-3-INVALID_ENCR_PASSWORD : Invalid encrypted password [chars].
Explanation The user-specified encrypted password is invalid. If the specified encrypted password is invalid, an error message will be printed during configuration.
Recommended Action Perform one of the following actions:
–
–
Error Message%OSPF-3-NOBACKBONE : Flagged as being an ABR without a backbone area
Explanation The router was flagged as an ABR, but there is no backbone area in the router.
Recommended Action Restart the OSPF process.
Error Message%OSPF-3-NOCONNDB : No database entry for connected address [IP_address]
Explanation While calculating OSPF routes, the router could not find the link-state advertisement that represents the connected route in the router.
Recommended Action Clear the IP routes in the routing table by entering the clear ip route command.
Error Message%OSPF-3-NOLSA : Failed to find this routers LSA in [chars]
Explanation The router is not able to find the router link state advertisement. This problem can occasionally occur and self-correct. If this message recurs, restart the OSPF process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OSPF-4-NONEIGHBOR : Received [chars] from unknown neighbor [IP_address]
Explanation An OSPF hello, database description, or database request packet was received, but the router could not identify the sender.
Recommended Action This situation should correct itself. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OSPF-4-NORTRID : OSPF process [dec] cannot start. There must be at least one "up" IP interface, for OSPF to use as router ID
Explanation OSPF failed while attempting to allocate a router ID from the IP address of one of its interfaces.
Recommended Action Ensure that there is at least one interface that is up and has a valid IP address. If there are multiple OSPF processes running on the router, each one requires a unique router ID. You must have enough interfaces that are up so that each of them can obtain a router ID.
Error Message%OSPF-3-NOSELF : if [chars] if_state [dec]
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPF-6-NOSRCPDB : ex_route_callback(): Can't find the src protocol to redistribute net [IP_address][IP_netmask]
Explanation OSPF has attempted to redistribute a route but could not find a valid source protocol.
Recommended Action No action is required.
Error Message%OSPF-4-NOTREDIST5 : db_free: external LSA [IP_address][IP_netmask]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPF-3-RDB_NO_LSA : lsid [IP_address] adv [IP_address] type [dec] gateway [IP_address] metric [dec] network [IP_address] mask [IP_address] protocol [hex] attr [hex] net-metric [dec]
Explanation OSPF has found an inconsistency between its database and the IP routing table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPF-3-RECONF_VL : OSPF process [dec] is changing router-id. Reconfigure virtual link neighbors with our new router-id
Explanation The OSPF process is being reset, and it will select a new router ID. This process will bring down all virtual links. Virtual-link configuration must be changed on all virtual-link neighbors for the links to work again.
Recommended Action Change virtual-link configuration on all the virtual-link neighbors to reflect the new route ID.
Error Message%OSPF-3-UNKNOWNSTATE : Reached unknown state in neighbor state machine
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPF-4-VIRTUAL_IN_NON_BACKBONE : Virtual link information found in non-backbone area: [chars]
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPF-4-WRONG_DEFAULT : Found generating default LSA with non-zero mask\n LSA type : [dec] Mask : [IP_address] metric : [int] area : [chars]
Explanation An internal software error has caused the router to try to generate a default LSA that has the wrong mask and possibly the wrong metric.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPF-6-ZERO_BANDWIDTH : interface [chars] has zero bandwidth
Explanation The interface has reported its bandwidth as zero.
Recommended Action No action is required.
OSPFv3 Messages
The following are Open Shortest Path First (OSPF) messages.
Error Message%OSPFv3-5-ADJCHG : Process [dec], Nbr [IP_address] on [chars] from [chars] to [chars], [chars]
Explanation An OSPF neighbor has changed state. The message text describes the change and the reason it occurred. This message appears only when the log-adjacency-changes command is configured for the OSPF process.
Recommended Action No action is required.
Error Message%OSPFv3-6-AREACHG : [IP_address][IP_netmask] changed from area [chars] to area [chars]
Explanation An OSPF configuration change has caused a network range to change areas.
Recommended Action No action is required.
Error Message%OSPFv3-6-BADCHKSUM : Checksum Failure in database in area [chars]
Link State Id [IP_address] Old Checksum [hex] New Checksum [hex]\nExplanation OSPF has detected a checksum error in the database due to memory corruption.
Recommended Action Restart the OSPF process.
Error Message%OSPFv3-4-BADLENGTH : Invalid length [dec] in OSPF packet fromUnrecognized format ` %P' (ID [IP_address]), [chars]
Explanation The system has received an OSPF packet that has a field length of less than normal header size or a field length that is inconsistent with the size of the IP packet in which the OSPF packet arrived. This problem indicates an error involving the sender of the packet.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPFv3-4-BADLSATYPE : Invalid lsa: [chars]: Type [hex], LSID [int] from [IP_address],Unrecognized format ` %P', [chars]
Explanation The router has received an LSA with an invalid LSA Type. The cause is either memory corruption or unexpected behavior on a router.
Recommended Action From a neighboring address, locate the problem router and perform the following actions:
a.
b.
c.
d.
e.
If you cannot determine the nature of the error from the collected information, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OSPFv3-3-DBEXIST : area [chars] lsid [IP_address] mask [IP_address] adv [IP_address] type [hex]
Explanation OSPF is having a problem locating the LSA. This condition could lead to a memory leak.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPFv3-4-DUP_RTRID_AREA : Detected router with duplicate router ID [IP_address] in area [chars]
Explanation OSPF has detected a router in the area that has the same router ID as this routing process. Duplicate router IDs may result in network instability, causing some destinations to be unreachable.
Recommended Action The OSPF router ID should be unique. Ensure that all routers in the area have a unique router ID.
Error Message%OSPFv3-4-DUP_RTRID_AS : Detected router with duplicate router ID [IP_address] in Type-4 LSA advertised by [IP_address]
Explanation OSPF has received a hello packet from a neighbor that has the same router ID as this routing process. A full adjacency cannot be established.
Recommended Action The OSPF router ID should be unique. Change the router ID of the neighbor.
Error Message%OSPFv3-4-DUP_RTRID_NBR : OSPF detected duplicate router-id [IP_address] fromUnrecognized format ` %P' on interface [chars]
Explanation OSPF has received a hello packet from a neighbor that has the same router ID as this routing process. A full adjacency cannot be established.
Recommended Action The OSPF router ID should be unique. Change the router ID of the neighbor.
Error Message%OSPFv3-4-ERRRCV : Received invalid packet: [chars] fromUnrecognized format ` %P', [chars]
Explanation An invalid OSPF packet was received. Details are included in the error message. The cause might be a misconfigured OSPF or an internal error in the sender.
Recommended Action Check the OSPF configuration of the receiver and check the sender for inconsistency.
Error Message%OSPFv3-3-INIT_IDB : OSPF is enabled on [chars] during idb initialization
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPFv3-3-INTERNALERR : Internal error: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OSPFv3-3-NOBACKBONE : Flagged as being an ABR without a backbone area
Explanation The router was flagged as an Area Border Router without a backbone area in the router.
Recommended Action Restart the OSPF process.
Error Message%OSPFv3-4-NONEIGHBOR : Received [chars] from unknown neighbor [IP_address]
Explanation An OSPF hello, database description, or database request packet was received, but the router could not identify the sender.
Recommended Action No action is required. This situation should correct itself. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OSPFv3-4-NORTRID : OSPFv3 process [dec] could not pick a router-id,
please configure manuallyExplanation OSPF failed while attempting to allocate a router ID from the IP address of one of its interfaces.
Recommended Action Ensure that there is at least one interface that is up and has a valid IP address. If there are multiple OSPF processes running on the router, each one requires a unique router ID. You must have enough interfaces that are up so that each of them can obtain a router ID.
Error Message%OSPFv3-3-NOSELF : if [chars] if_state [dec]
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPFv3-3-RDB_NO_LSA : lsid [IP_address] adv [IP_address] type [hex] gateway [IP_address] metric [dec] network [IP_address] mask [IP_address] protocol [hex] attr [hex] net-metric [dec]
Explanation OSPF has found an inconsistency between its database and the IP routing table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPFv3-3-RECONF_VL : OSPF process [dec] is changing router-id. Reconfigure virtual link neighbors with our new router-id
Explanation The OSPF process is being reset, and it will select a new router ID. This process will bring down all virtual links. Virtual-link configuration must be changed on all virtual-link neighbors for the links to work again.
Recommended Action Change virtual-link configuration on all the virtual-link neighbors to reflect the new route ID.
Error Message%OSPFv3-3-UNKNOWNSTATE : Reached unknown state in neighbor state machine
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPFv3-4-VIRTUAL_IN_NON_BACKBONE : Virtual link information found in non-backbone area: [chars]
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPFv3-4-WRONG_DEFAULT : Found generating default LSA with non-zero mask
LSA type : [hex] Mask : [IP_address] metric : [int] area : [chars]Explanation The router attempted to generate a default LSA with an incorrect mask and, possibly, incorrect metric because of an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OSPFv3-6-ZERO_BANDWIDTH : interface [chars] has zero bandwidth
Explanation The interface reports its bandwidth as zero.
Recommended Action No action is required.
P2IPC Messages
The following are Fast IPC event messages.
Error Message%P2IPC-3-BUFSZERR : [chars](): Failed to get padding size for chunk data size [dec] errno [dec], [chars], line [dec]
Explanation An internal error has occurred. The padding size could not be determined for the specified chunk data size.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-COMEPALLOCFAIL : [chars]() Failed to allocate a P2IPC Comm. endpoint [hex]
Explanation A FIPC communications endpoint failed to be allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-COMEPDELETED : [chars]() Non-existing CommEp [hex] has invalid tag [dec]; Expected tag is [dec]
Explanation A communications endpoint does not exist.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPDETACHERR : Failed to detach Endpoint from Endpoint chain, [chars], line [dec]
Explanation An endpoint could not be detached from the endpoint chain.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-COMEPFREEFAIL : [chars]() Failed to free an P2IPC Comm Endpoint [hex]
Explanation An FIPC communications endpoint could not be allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPIDINVALID : [chars]() An invalid P2IPC_COM_EPID of [hex] was passed as an argument.
Explanation An invalid FIPC communications endpoint ID has been passed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPMALLOCERR : [chars]() Failed to alloc mem for CommEp array (lstSize [dec], arraySize [dec]), errno [dec]
Explanation Memory for a communications endpoint array could not be allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPMEMAREAERR : [chars]() Insufficient memory for Comm Ep array: Want [dec], [dec] ; Got [dec], [dec]
Explanation Insufficient memory was available for a communications endpoint array.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPMGRSEMGIVE : [chars], [dec]
Explanation An error occurred while the communications endpoint manager semaphore was being released.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPMGRSEMTAKE : [chars], [dec]
Explanation An error occurred while the communications endpoint manager semaphore was being acquired.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPNAMEINVAL : Communication Endpoint's [hex] global name [chars] too long, [chars], line [dec]
Explanation The global name for the communication endpoint is too long.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-COMEPNAMESCOINV : [chars]() Name Scope [dec] is invalid
Explanation The name scope of the communication endpoint is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-COMEPOWNERINVAL : [chars]() Communication Endpoint [hex]: access by non-owner task
Explanation The communication endpoint is being accessed by a non-owner task.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPRPLYEPDINV : [chars]() Couldn't get task's Sync Rply Epid, errno [dec]
Explanation The task synchronization reply endpoint ID could be not obtained.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPSEMCREATE : Error [hex] creating EPID semaphore for task [dec]
Explanation An error occurred while the endpoint ID semaphore was being created for the task specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPSEMDEL : Error [hex] deleting P2IPC semaphore [hex] for task [dec]
Explanation An error occurred while the MGX-8850 semaphore was being deleted for the task specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPSEMGIVE : Error [hex] giving EPID semaphore [hex] for task [dec]
Explanation An error occurred while the endpoint ID semaphore was being given for the task specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPSEMINVALID : Invalid EndPoint semaphore in function [chars]
Explanation An invalid semaphore was detected in a communications endpoint.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-COMEPSEMTAKE : [chars] Error [hex] taking EPID semaphore [hex] for task [dec]
Explanation An error occurred while an endpoint ID semaphore was being acquired.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-COMEPTYPEINVAL : [chars]() Communication Endpoint [hex]: invalid type [hex]
Explanation The specified communication endpoint is not an IPC plain asynchronous endpoint.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CONNADD_FAIL : ssi ipc connRef: [chars]() line no [dec] connRef=[dec], connType=[dec]
Explanation An "spiConnAdd" action has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CONNDEL_FAIL : ssi ipc connRef: [chars]() line no [dec] connRef=[dec]
Explanation An "spiConnDel" action has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CONNREF_INVALID : ssi ipc connRef: [chars]() line no [dec] connRef=[dec]
Explanation An invalid connection reference has been received by the SSI IPC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTCEVTREGFAIL : [chars] - CTC Event Registration failed, event [hex], rc [hex], errno [dec]
Explanation CTC event registration failed for the event specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTCSTATETRAFAIL : [chars] - CTC state transition failed, event [hex], rc [hex], errno [dec]
Explanation CTC state transition failed for the event specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLALLOCMSGFAIL : [chars]() Error [hex] allocating message
Explanation An error occurred while a message was being allocated.
Recommended Action No action is required.
Error Message%P2IPC-3-CTLBINDSTATESETERROR : Epid [hex]
Explanation A Bind request is in an invalid state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLBINDSTFAIL1 : [chars](): Epid [hex]: Bind state failed, error [hex] sending to Name Svr
Explanation A Bind request failed because an error occurred while the request was being sent to the name server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLBINDSTFAIL2 : [chars](): Epid [hex]: Bind state failed, error [hex] - out of mblks
Explanation The state of a Bind request has failed because of an outage of memory blocks.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLBINDSTFAIL3 : [chars](): Epid [hex]: error [hex] binding global name
Explanation A Bind request failed because the request was invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLBINDSTUNKN1 : [chars](): Epid [hex]: Bind st. unknown, error [hex] sending duped BIND Rqst
Explanation An unknown error was encountered while a duplicate Bind request was being sent.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLBINDSTUNKN2 : [chars](): Epid [hex]: Bind state unknown, error [hex] receiving BIND Ack
Explanation The system was in an unknown Bind state while a Bind acknowledgment message was being received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLBINDSTUNKN3 : [chars](): Epid [hex]: Bind state unknown, error [hex] putting BIND Rqst on RetxQ
Explanation The system was in an unknown Bind state while a Bind request was being placed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLBINDSTUNKN4 : [chars](): Epid [hex]: Bind st unknown, unknown sts [hex] in BIND Ack, errno [dec]
Explanation A Bind acknowledgment message is in an unknown Bind state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLBINDSTUNKN5 : [chars](): Epid [hex]: Bind state unknown, error [hex] retransmitting BIND Rqst
Explanation The system was in an unknown Bind state while a Bind request was being retransmitted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLCOMEPERR : [chars]() Error [hex] instantiating P2IPC Control Port
Explanation An error occurred while the FIPC control port was being instantiated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLDUPMSGFAIL : [chars]() Error [hex] duplicating message
Explanation An error occurred while a message was being duplicated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLEPWAITERR : [chars](): Error [hex] exiting from EP Wait handler
Explanation An error occurred while the FIPC was exiting from the EP wait handler.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLHDLRATTCHERR : [chars]():Error [hex] attaching EP Wait handler to IPC Ctl queue
Explanation An error occurred while the FIPC was attaching an EP wait handler to an IPC control queue.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLINVIPCVER : [chars](): Ipc Version of Remote Card [dec] is different
Explanation A message could not be sent to a remote card because the IPC version of the remote card is different from the IPC version for this card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLINVMSGTYPE : [chars](): Invalid P2IPC Ctl msg type [hex], arg [hex]
Explanation The message is an invalid FIPC control message type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLINVMSGVER : [chars](): Invalid P2IPC Control msg version [hex], arg [hex]
Explanation The message contains an invalid FIPC control message version.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLINVRMTCTLMSGVER : [chars](): Remote Card IPC CtlMsg Version Invalid
Explanation A message could not be sent to a remote card because the IPC control version of the remote card is different fromthe IPC control version for this card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLMAXBUFRPLYERR : [chars](): Error in Replying to Query for MaxBufSize, error [dec]
Explanation An attempt to reply to a remote card query for the buffer size has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLOUTOFMBLKS : [chars](): P2IPC Control could not allocate mblk
Explanation The FIPC control could not allocate a memory block.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLRCVEPIDERR : [chars]() Error getting caller task's Receive Sync Epid
Explanation An error occurred while the system was attempting to obtain the synchronization endpoint ID for the caller task.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLRCVMSGERR : [chars](): Error [hex] receiving P2IPC Ctl message
Explanation An error occurred while an FIPC control message was being received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLRETXQERR : [chars](): Error [hex] initializing P2IPC Retransmission Queue
Explanation An error occurred while the FIPC retransmission queue was being initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLSYNCTMRERR : [chars](): Error [hex] initializing P2IPC Sync Timer
Explanation An error occurred while an FIPC synchronization timer was being initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLTSKCREATEERR : [chars](): Error [hex] creating P2IPC Control Task
Explanation An error occurred while an FIPC control task was being created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-CTLUNBINDSTFAIL1 : [chars](): Epid [hex]: UnBind state failed, error [hex] sending to Name Svr
Explanation A send request to the name server has failed . This condition caused an Unbind request to fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-CTLUNBINDSTUNKN1 : [chars](): Epid [hex]: UnBind st. unknown, error [hex] sending duped UNBIND Rqst
Explanation A duplicate Unbind request was sent while the system was in an unknown unbind state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-DBUFSIZEINVALID : Requested data buffer size [dec] exceeds system max buffer size, [chars](), line [dec]
Explanation The requested data buffer size exceeds the maximum buffer size of the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-EPHNDLRATTACHED : [chars]() Com Ep [hex] already has EP Handler attached
Explanation The communication endpoint already has an EP handler attached.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-EPHNDLRFAIL : [chars]() P2IPC EPHandler [hex] on Ep [hex] returning sts [hex], errno [dec]
Explanation An error was returned by the FIPC endpoint handler.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-EPWAITEXTINVPRM : Status parameter [hex] to ssiIpcComEpWaitExit is invalid, [chars](), line [dec]
Explanation The "ssiIpcComEpWaitExit" function has received an invalid status parameter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-FILECLOSEFAIL : [chars], errno is [dec], filedescriptor is [dec], [chars], line [dec]
Explanation An error occurred while the FIPC was attempting to close a file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-FILEINVALID : [chars], errno is [dec], filedescriptor is [dec], [chars], line [dec]
Explanation The specified file is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-FILEOPENFAIL : [chars], errno is [dec], fileName is [chars], [chars], line [dec]
Explanation The specified file could not be opened.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-FILEREADFAIL : [chars], errno is [dec], filedescriptor is [dec], [chars], line [dec]
Explanation The specified file could not be read.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-FILESEEKFAIL : [chars], errno is [dec], filedescriptor is [dec], [chars], line [dec]
Explanation An error occurred while the FIPC was attempting to find the specified file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-FILEWRITEFAIL : [chars], errno is [dec], filedescriptor is [dec], [chars], line [dec]
Explanation A write operation failed for the file specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-HIGHMSGQDEAD : P2IPC message High queue, queue [hex] is dead, [chars], line [dec]
Explanation The FIPC message High queue is not responding.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-INVHWIDB : Invalid HWIDB Value: [hex] , [chars], line [dec]
Explanation An invalid hardware IDB was found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-INVNUM : [chars], line [dec]
Explanation An invalid number was found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-ISRNOTCALLABLE : Attempt to take P2IPC semaphore [hex] from interrupt routine
Explanation An attempt was made to remove an FIPC semaphore from an interrupt routine.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-LCNALREADYBOUND : Bind failed: LCN [dec] already bound by [hex], [chars], line [dec]
Explanation A Bind attempt failed because the LCN is already bound by the task ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-LCNBIND_FAIL : ssi ipc connRef: [chars]() line no [dec] connRef=[dec], lcn=[dec], epid=[hex], hanle=[hex], offset=[hex], option=[hex]
Explanation A "ssiIpclcnBind" attempt has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LCNEPIDINVALID : Bind failed: LCN [dec], epid [hex] invalid, [chars], line [dec]
Explanation A Bind attempt has failed because the LCN endpoint ID is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LCNMSGSENDERROR : Failed to send msg on LCN [dec] to epid [hex], errno [dec]
Explanation A message could not be sent on the LCN to the endpoint ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LCNNOTBOUND : LCN [dec] is not bound
Explanation The LCN is not bound.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LCNOUTOFRANGE : LCN [dec] out of range <[dec]-[dec]>, [chars], line [dec]
Explanation The LCN is outside of the normal range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LCNOWNERINVALID : LCN [dec] owned by [hex]: access by non-owner task [hex]
Explanation The LCN is being accessed by a non-owner task.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LCNSARREGFAILED : Bind Failed: LCN [dec] failed SAR registration, errno [dec], [chars], line [dec]
Explanation The LCN failed while SAR registration was occurring. This condition caused a Bind operation to fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LCNSARUNREGFAIL : Unbind Failed: LCN [dec] failed SAR unregistration, errno [dec], [chars], line [dec]
Explanation An Unbind attempt has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-LCNUNBIND_FAIL : ssi ipc connRef: [chars]() line no [dec] connRef=[dec], lcn=[dec]
Explanation An "ssiIpclcnUnbind" attempt has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LINKINERROR : [chars]() Link rcv error [hex], link [hex]; Got [hex], Expected [hex]
Explanation An FIPC link receive error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-LINKMEMALLOCERR : Failed to allocate memory for link cfg table (num links [dec]), [chars](), line [dec]
Explanation Memory could not be allocated for the link configuration table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LINKOUTERROR : [chars](), line [dec], FIPC Link snd error: Expected [hex], Got [hex]
Explanation An FIPC link send error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LINKPLFMSLOT2RX : Platform cannot translate RxLcn for slot [dec], [chars], line [dec]
Explanation The platform cannot translate the Rx LCN.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-LINKSARREGERROR : Error [hex] registering link [dec] SAR (slot [dec]), [chars], line [dec]
Explanation An error occurred while a link was being registered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-LOWMSGQDEAD : P2IPC message Low queue, queue [hex] is dead, [chars], line [dec]
Explanation The FIPC message Low queue is not responding.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKALLOCFTLERR : [chars]() Fatal error [dec] allocating floating mblk, mblk control corrupted ,
Explanation A fatal error occurred while a floating memory block was being allocated. This condition indicates that the memory block control was corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKASSIGNFAIL : Message assignment failed: [chars]() [hex], [chars], line [dec]
Explanation A message assignment has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKBPOOLCRTERR : Failed to create P2IPC buffer pool(buf size [dec], num bufs [dec]), [chars](), line [dec]
Explanation An FIPC buffer pool could not be created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKBUFDESCERR : [chars]() Failed to alloc P2IPC buffer descriptor memory (num buf desc [dec]),
Explanation An FIPC buffer could not be created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKBUFFREEFAIL : [chars]() Failed to free data buffer [hex], errno [dec]
Explanation The FIPC could not free a data buffer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-MBLKENQUEUED : [chars]() Epid [dec]; mbPtr [hex] already freed, mbPtr->next is [hex], mbPtr->datap is [hex], ownerTask is [dec]
Explanation The specified memory block is already enqueued and in use.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKFREEFAIL : [chars]() Failed to free mblk [hex], errno [dec]
Explanation A memory block could not be freed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKINVALID : [chars]() Invalid message descriptor
Explanation FIPC has detected an invalid message descriptor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKMPOOLCRTERR : [chars]() Failed to create P2IPC mblk pool (tot. mblks [dec], fltg. mblks [dec])
Explanation An FIPC memory block pool could not be created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MBLKNOHDRSPACE : [chars] No space for header, errno [dec], Wanted [dec], Got [dec]
Explanation There is no space for a header.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-MBLKUNAVAILABLE : [chars] No mblk available for a buffer - mblk pool corrupted
Explanation No memory block is available for a buffer because the memory block pool is corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MSGQCREATEFAIL : [chars]() Failed to create P2IPC message queue, error [dec]
Explanation An FIPC message queue could not be created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MSGQDEAD : [chars]() P2IPC message queue, line [dec]
Explanation The FIPC message High queue is not responding.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MSGQDELETEFAIL : [chars] Failed to delete P2IPC message queue, queue [hex], errno [dec]
Explanation The FIPC message queue could not be deleted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MSGQEVENT : P2IPC MsgQ Event: [chars], queue [hex], parameters [hex], [hex], [hex], [hex], [chars], line [dec]
Explanation A message queue event has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-MSGQFULL : [chars], line [dec], [chars], line [dec]
Explanation The message queue is full.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMEARRAYFULL : P2IPC Name Server name array is full, [chars], line [dec]
Explanation The FIPC name server name array is full.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMECOMEPCREATE : Failed to instantiate name Server Comm endpoint, errno [dec], [chars], line [dec]
Explanation The name server communications endpoint could not be instantiated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-NAMEENTRYBNDINV : Returned name entry [hex] out of name array bounds [hex]-[hex], [chars], line [dec]
Explanation The FIPC has returned a name entry out of a name array boundary.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMEENTRYINIT : Failed to initialize Name Server name entry, [chars], line [dec]
Explanation A Name Server name entry could not be initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-NAMEENTRYOVRRID : Name entry [chars] epid [hex] overriden with epid [hex], [chars], line [dec]
Explanation The name entry of an endpoint ID has been overridden by another endpoint ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-NAMEINVMSGTYPE : Invalid message type [hex], arg [hex], [chars], line [dec]
Explanation An invalid IPC control message type has been encountered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMEINVMSGVER : Invalid message version [hex], arg [hex], [chars], line [dec]
Explanation An invalid IPC message version has been encountered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMEMEMALLOC : Failed allocate memory forUnrecognized format ` %,' maxNumNames [dec], [chars], line [dec]
Explanation FIPC failed to allocate memory for a global name array.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMEMSGALLCFAIL : Failed to allocate BIND/RESOLVE ACK message, [chars], line [dec]
Explanation A Bind or Resolve acknowledgment message could not be allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-NAMENOENTRYOUT : No outstanding name entry [hex] in name array, [chars], line [dec]
Explanation No outstanding name entry exists in the name array.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMESRCSLOTINV : Name Server BIND Rqst from slot [dec]: Epid's srcPhySlotId [dec], [chars], line [dec]
Explanation A Bind request is invalid because of a slot mismatch.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NAMETASKCREATE : Failed to create Name Server task, errno [dec], [chars], line [dec]
Explanation A name server task could not be created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-NUMCOMEPINVALID : [chars]() Desired number of Comm Eps [dec] exceeds the system limit [dec], errno [dec]
Explanation The number of available endpoint IDs in the system has been exceeded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-P2IPCBASEINITFAIL : Failed to initialize P2IPC Buffers \n, [chars], line [dec]
Explanation FIPC buffers could not be initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-P2IPCINITFAIL : Failed to initialize P2IPC \n, [chars], line [dec]
Explanation FIPC could not be initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-P2IPCLINKINITFAIL : Failed to initialize Link Parameters
, [chars], line [dec]Explanation Link parameters cannot be initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-PAKINVALID : Invalid PakType, [chars](), line [dec]
Explanation The specified packet is of an invalid type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-PARMINVALID : [chars], at address [hex], [chars], line [dec]
Explanation An invalid parameter has been encountered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-PARMOUTOFRANGE : Invalid parameter [chars], value is [dec], [chars], line [dec]
Explanation The value of the specified parameter is out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-REBINDERROR : [chars](): Event Type is [dec]\n
Explanation The specified event type is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-RETXQMQCHAINERR : [chars]() [chars] [chars]: Retxq [hex] Got [hex], Expected [hex]
Explanation The message is not the first message in the chain.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-RETXQSGUNLKFAIL : Failed to unlock timer signal, errno [dec], [chars], line [dec]
Explanation The timer signal could not be unlocked.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-RETXQSIGLCKFAIL : Failed to lock timer signal, errno [dec], [chars], line [dec]
Explanation The timer signal could not be locked.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-RETXQTIMERSET : [chars]() [chars]: RetxQ [hex]: timer set error [hex]
Explanation An error occurred while the time was being set for the queue during message retransmission.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-RETXQTIMRCANCEL : [chars]() [chars]: RetxQ [hex]: timer cancel error [hex]
Explanation An error occurred because the queue timer was being canceled while a message was being retransmitted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-RSLVACKERR : [chars](): Received msg [hex] instead of RESOLVE ACK, arg [hex]
Explanation A Resolve acknowledgment should have been received; instead, the message itself was received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-RSLVNAMELENERR : [chars](): Requested P2IPC Global Name "[chars]" too long (max name len [dec] )
Explanation The name that is to be resolved is too long.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-SENDERROR : P2IPC Message Send error to Epid [hex], Message pointer is [hex], [chars](), line [dec]
Explanation An FIPC error occurred while a message was being sent.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-SMSLOTERROR : Error [hex] and SM slot no passed is [dec], [chars], line [dec]
Explanation An error occurred in the specified SM slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-SYNCCTXTCLNERR : [chars]() Failed to cleanup sync context for epid [dec], errno [dec]
Explanation The synchronization context for the endpoint ID could not be cleaned up.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-SYNCCTXTINUSE : [chars]() Sync context in use in Comm Epid [dec]
Explanation The synchronization context for the specified endpoint ID is already in use.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-SYNCINVALIDRPLY : [chars]() Invalid sync reply on epid [chars], Epid [hex] ([hex]), SeqNum [dec] ([dec])
Explanation An invalid synchronization reply was received on an endpoint.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-SYNCNOTSYNCRPLY : [chars]() Received msg not Sync Reply on epid [chars]
Explanation A synchronization message was expected to be received on the endpoint, but another message was received instead.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TASKENTRYGETFAIL : Error getting task entry for task [dec], [chars], line [dec]
Explanation An error occurred while a task entry was being obtained.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TASKINITFAIL : Error initializing task entry for task [dec], [chars], line [dec]
Explanation An error occurred while a task entry was being initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TASKSEMCREATE : Error [hex] creating Task semaphore for task [dec], [chars], line [dec]
Explanation An error occurred while a task semaphore was being created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TASKSEMDEL : Error [hex] deleting P2IPC semaphore [hex] for task [dec], [chars], line [dec]
Explanation An error occurred while a task semaphore was being deleted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TASKSEMGIVE : Error [hex] giving Task semaphore [hex] for task [dec], [chars], line [dec]
Explanation An error occurred while a task semaphore was being received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TASKSEMINVL : Invalid Task semaphore [dec], [chars], line [dec]
Explanation An invalid task semaphore has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TASKSEMTAKE : Error [hex] taking Task semaphore [hex] for task [dec], [chars], line [dec]
Explanation An error occurred while a task semaphore was being acquired.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-TIMERERROR : Error processing Timer, [chars], line [dec]
Explanation An error has occurred in processing the timer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-4-TIMEREVENT : Timer Event, [chars], line [dec], task [dec], timeout [dec]
Explanation The process timed out while it was waiting for a message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%P2IPC-3-UNEXPECTEDEVENT : [chars], [dec], [chars], line [dec]
Explanation A major software process event has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
P2IPC_TRACE Messages
The following are Fast IPC Trace messages.
Error Message%P2IPC_TRACE-0-0 : Fast IPC Trace Messages
Explanation This messages provides trace messages for FIPC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
PA Messages
The following are port adapter (PA) messages.
Error Message%PA-2-BADDAT : PA interface data incorrect, [hex]
Explanation Incorrect port adapter interface data has been found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-2-BADIDB : PA interface idb incorrect, [hex]
Explanation The control block data structure of the port adapter system indicates a zero interface descriptor block.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-2-BADINTERFACE : Out of range PCI Port Adaptor interface, [dec] on bay [dec]
Explanation The software has specified an out-of-range port adapter interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-2-BADPA : PA interface pa incorrect, [hex]
Explanation An incorrect port adapter interface has been specified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-2-BADPA2 : PA null adapter, [hex]
Explanation A null port adapter interface has been specified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-2-BADPABAY : Out of range PCI Port Adaptor bay [dec]
Explanation The software has specified an out-of-range port adapter bay.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-2-BADPASCB : PA interface pascb incorrect, [hex]
Explanation The port adapter system control block data structure was incorrectly set in the command data structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-2-BADPINST : PA interface port_inst incorrect, [hex]
Explanation An attempt to access internal data pertaining to the port instance has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-2-BADVCONT : PA interface vcont incorrect, [hex]
Explanation An incorrect VC interface has been specified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-3-BRINGUPFAIL : port adapter in bay [[dec]] failed to reset.
Explanation An attempt to reset and initialize the port adapter has timed out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-3-CONFIG : Recommended port adapter configuration exceeded
Explanation The total bandwidth of high- and medium-bandwidth port adapters has exceeded the rated capacity of this system.
Recommended Action Refer to the configuration guidelines for the maximum allowed high- and medium-bandwidth port adapters for the system.
Error Message%PA-3-DEACTIVATED : port adapter in bay [[dec]] powered off.
Explanation The port adapter is being powered off.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PA-2-ILLEGALPA : Illegal Port Adaptor type [dec] in bay [dec] of [chars].
Explanation The port adapter is not supported by the controller into which it is plugged.
Recommended Action Remove the port adapter and return the controller to its original configuration.
Error Message%PA-3-IMPROPER_INSERT : Improper insertion for slot [dec]. Remove and then re-insert the PA
Explanation The PCI activation of the PA has failed; therefore, the PA has been deactivated.
Recommended Action Remove and then reinsert the PA firmly into the slot.
Error Message%PA-2-INCORRECTBRIDGEREG : Bad default register([hex]) setting([hex]) in PA bridge
Explanation The software is unable to configure certain settings for the port adapter PCI bridge in the specified bay.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-3-NOTSUPPORTED : PA in slot[dec] ([chars]) is not supported on this [chars]
Explanation The port adapter in the specified slot is not supported on this chassis or CPU card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-2-PABRIDGE : Failed to config bridge for PA [dec]
Explanation The system side PCI bridge for this port adapter has failed initialization. The port adapter will therefore not be operational.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-3-PACREATE : Unable to create driver for Port Adaptor type [dec] in bay [dec]
Explanation A possible memory shortage or port adapter hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-2-PARECUR : Recursive loop while getting the daughtercard info for PA type [dec]
Explanation While retrieving the daughter card information for the chassis MIB, the platform SNMP code has gone into an infinite loop.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-4-PCIVALID : PCI activation failed, bay [dec], [hex]
Explanation The system has received an invalid PCI signal from the port adapter. This is probably due to a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-2-QOVERFLOW : PA queue overflow, cmd [hex]
Explanation The port adapter queue has overflowed and the programming has been lost.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-3-REVNOTSUPPORTED : PA in slot[dec] ([chars]) requires base h/w revision of ([dec].[dec]) for this [chars]
Explanation A newer hardware revision of the port adapter is required for functional operation on this chassis.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-0-RUPTCONFLICT : Conflict detected when trying to install [chars] interrupt handler, bay [dec].
Explanation An attempt was made to register an interrupt handler either for a nonexistent port adapter or for the wrong interrupt priority level.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-3-SLOTNOTSUPPORTED : This PA type ([chars]) is not supported in slot[dec] of this [chars]
Explanation This port adapter is not supported on the chassis or CPU card in the slot specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-2-UNDEFIO : Unsupported I/O Controller (type [dec]) in I/O Bay. The I/O Controller network interfaces will be unavailable.
Explanation The software does not have a driver for the specified port adapter type located in the I/O bay.
Recommended Action Ensure that the image you are running supports this card. The newer I/O controllers work only with the "kboot" image. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-2-UNDEFPA : Undefined Port Adaptor type [hex] in bay [dec]
Explanation The software does not have a driver for the port adapter type that is in the specified bay.
Recommended Action Ensure that the image you are running supports this card. Check that the card is properly seated. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-2-UNDEFPABRIDGE : Unsupported Port Adaptor Bridge [hex] in bay [dec]
Explanation The software does not have a driver for the port adapter protocol control information bridge that is in the specified bay.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PA-2-UNDEFWIC : Undefined WIC Adaptor type [dec] in bay [dec]
Explanation The software does not have a driver for the type of WIC adapter that is in the specified bay.
Recommended Action Ensure that the image you are running supports this card. Check that the card is properly seated. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
PACK Messages
The following Channel Interface Processor (CIP) messages are related to the packed extension to the Common Link Access to Workstation (CLAW) facility.
Error Message%PACK-3-BADLEN : Invalid length in CLAW packed control message - act [dec], exp [dec]
Explanation A control message was received under the packed CLAW link, and the length did not match that of a known packed control message.
Recommended Action Get a GTF and a channel trace to verify that the host is sending the bad packed message.
Error Message%PACK-3-BADSCBQ : Found data queued with channel queue partially empty.
Explanation After a packet was received, the packed driver detected that packed data was waiting to be queued even though the channel queue was partially emptied.
Recommended Action This is an internal logic error. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-0-BADSIZE : Invalid size in connnection request- [dec] R, [dec] W; defined - [dec] R [dec] W
Explanation In a packed connection request, either a read size requested was smaller than the packed type defined or a write size requested was larger than the packed type defined.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-0-BADSIZE2 : Packed type names:"[chars]" - "[chars]"
Explanation The specified packed type names have experienced a BADSIZE-PACK error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-3-BADSTATE : Claw packed sublink [dec] is in an unknown state [dec]. Path=[hex][hex][hex] device=[hex] link=[hex]
Explanation A packet was received from the host on a packed sublink for which the state was unknown. This is a logic error.
Recommended Action The packet was dropped. Report this error to your Cisco technical support representative.
Error Message%PACK-0-BADTYPE : Host Packed names "[chars]" - "[chars]" do not match any configured names.
Explanation An attempt was made to establish a packed connection, but the packed type names specified on the host do not match any of the packed names specified in the CMCC.
Recommended Action Correct the host configuration or upgrade the CMCC microcode to a version that supports the packed type specified by the host.
Error Message%PACK-0-BADTYPE2 : Supported packed type names: "[chars]" - "[chars]"
Explanation An attempt was made to establish a packed connection, but the packed type names specified on the host do not match any of the packed names specified in the CMCC.
Recommended Action Correct the host or router configuration.
Error Message%PACK-0-BADVERSION : Host CLAW Packing version [dec] does not equal CMCC version [dec].
Explanation The version specified in a packed CLAW message from the host is not the same as the version specified in the CMCC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-6-COMMAND : Unrecognized CLAW packing control command code [dec].
Explanation The host has sent a CLAW packing control command with an invalid command code.
Recommended Action The CMCC has ignored the request. Get a GTF and a channel trace to verify that the host is sending the bad packed message.
Error Message%PACK-6-CTLERROR : Packed control error message received with return code of [dec].
Explanation The host rejected a previously received CLAW packed control message sent by the CMCC.
Recommended Action Check the return code and correct IT as appropriate.
Error Message%PACK-3-ILLEN : Not enough data left in buffer for packed message - remaining [dec], length [dec]
Explanation The host has written a block of packed messages, and the length of the block was inconsistent with the size of the packed messages.
Recommended Action Get a GTF and a channel trace to verify that the host is sending the bad packed messages.
Error Message%PACK-3-ILLEN2 : Received zero length packed message.
Explanation The host has written a block of packed messages, and the length of a packed message was zero. This is an invalid size.
Recommended Action Get a GTF and a channel trace to verify that the host is sending the bad packed message.
Error Message%PACK-6-NOCONN : Channel wrote data on sublink [dec] without a valid connection. Path=[hex][hex][hex] device=[hex] link=[hex]
Explanation A packet has been received from the host, but the packed sublink specified with the data does not represent a valid connection.
Recommended Action The packet was dropped. Report this error to your Cisco technical support representative.
Error Message%PACK-0-NOLINKID : Unable to allocate sublink id for CLAW packing sublink.
Explanation An attempt was made to allocate a sublink ID to assign to a connection request, but all sublink IDs were in use. This error should not occur.
Recommended Action The CMCC has recovered by generating a bad return code to the requestor. Report this error to your Cisco technical support representative.
Error Message%PACK-3-NOMBUF : Couldn't allocate a new MBUF from the CLAW Packing pool.
Explanation An attempt to allocate a new memory buffer from the CLAW packing pool has failed. This is a design error. There should always be enough memory buffers for packed CLAW data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-3-NOMORE : Packed sublink [dec] doesn't support the more bit
Explanation The host sent a packet message with the "More" bit on, and the sublink to which the message was sent does not support the "More" bit.
Recommended Action Get a GTF and a channel trace to verify that the host is sending the bad packed message.
Error Message%PACK-6-NOTPRESENT : CLAW Packing sublink [dec] being freed was not present.
Explanation The host software has attempted to disconnect a CLAW packing sublink that was not established.
Recommended Action The CMCC has ignored the request. Report this error to your Cisco technical support representative.
Error Message%PACK-6-RANGE : CLAW packing sublink [dec] being freed is out of range.
Explanation An attempt to disconnect a CLAW packing sublink has failed because the CLAW packing sublink ID is not in the valid range for all CLAW packed sublinks.
Recommended Action The CMCC has recovered by ignoring this request. Report this error to your Cisco technical support representative.
Error Message%PACK-6-RANGE2 : Out of range sublink ([dec]) received in packed claw message.
Explanation The CLAW packing sublink ID in a packed message is not in the valid range for all CLAW packed sublinks.
Recommended Action The CMCC has recovered by ignoring this request. Report this error to your Cisco technical support representative.
Error Message%PACK-0-SYSMGT_ERROR1 : CLAW detected error in sysmgt call: invalid CLAWPACK CONTROL length
Explanation An invalid parameter was received in a system management call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-0-SYSMGT_ERROR2 : CLAW detected error in sysmgt call: invalid CLAWPACK SUBLINK length
Explanation An invalid parameter was received in a system management call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-3-TOOBIG : Received packet [dec], packed header [dec], negotiated frame [dec], dropped the packet
Explanation The received packet together with the packed header is larger than negotiated CLAW read frame size, and the packet has been dropped.
Recommended Action Set the IP MTU to the negotiated CLAW frame size that is specified in the error message text, less 4 (for the CLAW packed header).
Error Message%PACK-3-TOOLARGE : Received [dec] byte message on packed sublink [dec] - max is [dec].
Explanation The host has sent a packed message on a sublink that was larger than the write size negotiated during the Packed Connection Request sequence.
Recommended Action Get a GTF and a channel trace to verify that the host is sending the bad packed message.
PAD Messages
The following are X.25 packet assembler/disassembler (PAD) messages.
Error Message%PAD-3-GETLINE : Tty[t-line], bad return code [dec] from x3_getline()
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PAD-2-INTR : [chars] called at interrupt level [hex]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PAD-2-PUTSETUP : Tty[t-line], buffer already setup
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
PAMMBOX Messages
The following are platform-independent PAM mailbox serial interface messages.
Error Message%PAMMBOX-3-BADCONFIG : Bad mailbox config data [hex], [hex]
Explanation An error has been found in the mailbox configuration data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PAMMBOX-3-BADRXFRMHDR : [dec] [dec] [dec] [dec] [hex] [hex] [hex]
Explanation A received PAM mailbox message frame contains an invalid header.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PAMMBOX-3-BADSTATUS : Bad mailbox status data [hex], [hex]
Explanation An error has been found in the PAM mailbox status data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PAMMBOX-3-INITERROR : Initialization Error: [chars]
Explanation An error has occurred during the subsystem initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PAMMBOX-3-PLATADDSLOT : Platform add slot error [dec], [dec]
Explanation The platform-dependent add-slot routine has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PAMMBOX-3-PLATDELETESLOT : Platform delete slot error [dec], [dec]
Explanation The platform-dependent delete-slot routine has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PAMMBOX-3-RXBADSTATE : RX mailbox in illegal state [dec] [dec]
Explanation The Rx mailbox is in a not-owned state, but it has interrupted as if it were in an owned state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PAMMBOX-3-RXNOIDB : RX a message but no NRP IDB for slot [dec] subslot[dec]
Explanation A message has been received, but no IDB exists for the specified slot and subslot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PAMMBOX-3-RXQWAKEUPREASON : Unknown wakeup reasons: [dec] [dec]
Explanation The Rx packet queue process has woken up for an unknown reason.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PAMMBOX-3-TXBADSTATE : TX mailbox in illegal state [dec] [dec] [dec]
Explanation The Tx mailbox is owned and empty, but the output queue is not empty.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PAMMBOX-3-TXOUTERR : Transmit Message Output Error: [dec] [dec] [dec] [dec]
Explanation Sanity checks have failed on a transmit message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PAMMBOX-3-TXPAKERR : Transmit Message No Packet
Explanation The Tx message cannot obtain a packet.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PAMMBOX-3-TXRXBADINITSTATE : TX/RX mailbox owned in illegal initial state [dec] [dec]
Explanation The Tx mailbox, the Rx mailbox, or both are in an illegal initial ownership state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PAMMBOX-3-UNEXPECTEDINT : Unexpected PAM Mailbox Interrupt: [chars]
Explanation Sanity checks have failed on a transmit message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
PAR Messages
The following are parity messages.
Error Message%PAR-1-FATAL : [chars]
Explanation A parity error has occurred. This problem might be caused either by a motherboard that has failed or motherboard jumper settings that are incorrectly set.
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.
PARSE_RC Messages
The following are PARSE_RC-related messages.
Error Message%PARSE_RC-3-PRC_LEV_RANGE : Parser Return Code level range error [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy down the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PARSE_RC-3-PRC_NO_CSB : Parser Return Code csb error [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy down the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PARSE_RC-3-PRC_SUBRCODE_RANGE : Parser Return Code state range error [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy down the system's configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the gathered information.
PARSER Messages
The following are parser messages.
Error Message%PARSER-4-BADCFG : Unexpected end of configuration file.\n
Explanation A configuration has been read from the TFTP server or NVRAM, and the end of the file has been encountered before the end statement. The configuration may be corrupted or incomplete. What was read is in effect.
Recommended Action Ensure that the configuration is correct. After the configuration is verified, enter either the copy running-config startup-config command to write the good configuration to NVRAM, or the copy running-config tftp command to write to a network TFTP server.
Error Message%PARSER-4-BADRANGE : Bad range <[dec]-[dec]> for command '[chars]'
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information
Error Message%PARSER-3-BADSUBCMD : Unrecognized subcommand [dec] in [chars] command '[chars]'
Explanation The parser has failed an internal software check.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PARSER-3-CREATEINT : Can't create any more subinterfaces
Explanation The parser has failed an internal software check.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PARSER-2-INTDISABLE : Interrupts disabled in mode [chars] by command '[chars]'
Explanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PARSER-4-INVLDLINE : Invalid line in NV generation: [t-line]\n
Explanation The parser has failed an internal software check.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PARSER-4-INVLDNVGEN : Invalid function called in NVGEN of '[chars]'
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show version command to gather and copy the displayed information. Contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PARSER-4-INVLDSYNTX : Syntax clean up called while not syntax checking. FuncPtr / Context [chars]
Explanation Functions were mistakenly called. There might be more than are one function listed, when only one is allowed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show version command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show version command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PARSER-4-LINKPOINT : Parser reached link_point
Explanation The parser has failed an internal software check.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PARSER-4-MULFUNCS : unknown test in test_multiple_funcs '[char]'
Explanation The parser has failed an internal software check.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PARSER-4-MULTIPLEIFS : interface_action: multiple ifs present when unit_only set
Explanation The parser has failed an internal software check.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PARSER-3-NOLINK : no link_point([dec]) in the [chars] [chars] command chain
Explanation The parser has failed an internal software check.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PARSER-4-NUMHELP : general_number_short_help: Invalid [chars] number flag
Explanation The parser has failed an internal software check.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PARSER-4-NVGEN : nvgen_token called but csb->nvgen not set
Explanation The parser has failed an internal software check.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PARSER-4-PROTOADDR : protoaddr_action: Unknown link_type [dec]
Explanation The parser has failed an internal software check.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PARSER-3-URLOPENFAIL : cannot open file for redirection '[chars]'
Explanation The destination URL for the redirection cannot be opened for writing.
Recommended Action Check for proper URL syntax and for write permission. Ensure that there is free space available for writing, and retry the operation.
PCMCIAFS Messages
The following are PCMCIA disk messages.
Error Message%PCMCIAFS-5-DIBERR : PCMCIA disk [dec] [chars]
Explanation The system cannot boot a image from the PCMCIA Flash disk because the Device Information Block does not match. The Flash disk can be read by the router, but it will require formatting by the router before an image can be booted from it.
Recommended Action Follow any instructions provided in the error message. Before storing a image in the Flash disk and trying to boot from this device, enter the format command to format the Flash disk from the router. Copy the desired image to the Flash disk, and then boot from this device.
PCPA Messages
The CIP, CIP2, ECPA, ECPA4, and PCPA messages all use the same message format. For details on how to locate and interpret these messages, refer to CIP and CIP2 Messages in Volume 1 of the IOS System Messages.
PERUSER Messages
The following are PPP per-user configuration messages.
Error Message%PERUSER-3-ISDNINTF : [chars] [chars]: Can not apply configuration to ISDN channel:
"[chars]"Explanation The configuration cannot be applied to individual ISDN channels.
Recommended Action Virtual profiles and virtual-access interfaces are required in order to apply the configuration to ISDN. Refer to the Cisco IOS Dial Technologies Configuration Guide for more information on virtual profiles.
PF Messages
The following are protocol filtering messages.
Error Message%PF-4-MEM_UNAVAIL : Memory was not available to perform the protocol filtering action
Explanation Protocol filtering is unable to operate because of a lack of memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PF-4-PROC_START_ERR : Protocol filtering unable to start
Explanation Creation of the protocol filtering process could not take place. The reason for this failure is unknown.
Recommended Action Restart protocol filtering in case the condition was transient. If the protocol filtering process still fails, reload the device.
Error Message%PF-5-TRUNKPFOFF : Protocol filtering disabled on interface [chars] because it is a trunk
Explanation Protocol filtering does not operate on trunks. The protocol filtering configuration stays with the trunk port, but it has no effect and does not appear when you show all nondefault protocol filters.
Recommended Action No action is required.
Error Message%PF-4-UNKN_ERR : An unknown operational error occurred
Explanation An internal operational error has occurred. Protocol filtering is unable to operate.
Recommended Action Reload the device.
PFINIT-SP Messages
The following are Platform Initialization SP messages.
Error Message%PFINIT-SP-5-CONFIG_SYNC : Sync'ing the [chars] configuration to the standby Router.
Explanation The configuration has been successfully synchronized to the standby router.
Recommended Action Informational message only. No action is required.
PGM Messages
The following are Pragmatic General Multicast (PGM) messages.
Error Message%PGM-6-ADDR_ERR : Invalid [chars] address [IP_address] in [chars]
Explanation A packet with an invalid address has been received.
Recommended Action No action is required.
Error Message%PGM-3-EXP_TSI_SQN_ERR : Expiring TSI [chars] has retransmit state
Explanation An expiring PGM TSI has an unexpired retransmit state. This condition can occur only because of an internal error or because of memory that cannot be freed.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PGM-3-PAK_ALLOC_ERR : Failed to allocate buffer for [chars]
Explanation Not enough memory is available to allocate packet buffers.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PGM-6-PAK_IIF_FIXUP : Pak for [IP_address] received on [IP_address], fixed input interface
Explanation A PGM packet was received on an interface other than the one to which it was addressed.
Recommended Action No action is required.
Error Message%PGM-6-PAK_MALFORMED_ERR : Malformed packet: [chars]
Explanation A PGM packet did not pass the internal sanity check.
Recommended Action No action is required.
Error Message%PGM-6-QUEUE_FULL : Serviced full queue of PGM packets.
Explanation The PGM process is busy, either because of an excessive retransmit state or because of excessive traffic.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PGM-3-RTX_STATE_ALLOC_ERR : Failed to allocate [chars] state
Explanation Insufficient memory is available to allocate the specified retransmit state.
Recommended Action Manually clear all retransmit states by entering the clear ip pgm router EXEC command or deconfigure and reconfigure the PGM. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PGM-3-RTX_STATE_FREE_ERR : Failed to free [chars] state
Explanation Insufficient memory is available to free the specified retransmit state.
Recommended Action Manually clear all retransmit states by entering the clear ip pgm router EXEC command or deconfigure and reconfigure the PGM. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PGM-6-TSI_GROUP_CHANGE : TSI group changed from [IP_address] to [IP_address]
Explanation A PGM SPM has advertised a new group for the TSI.
Recommended Action No action is required.
Error Message%PGM-6-TSI_SOURCE_CHANGE : TSI source changed from [IP_address] to [IP_address]
Explanation A PGM SPM has advertised a new source for the TSI.
Recommended Action No action is required.
PGMHOST Messages
The following are Pragmatic General Multicast (PGM) host module messages.
Error Message%PGMHOST-6-INPUT_PACKET_ERR : Matched TSI but failed to match dport; expected [dec] actual [dec]
Explanation An incorrectly structured packet has been received from the network.
Recommended Action Investigate the problem and fix the other implementation of PGM.
PIF Messages
The following are RSC PIF messages.
Error Message%PIF-3-DOWNLOAD_ERROR : [chars], [chars]
Explanation The image for the port interface could not be downloaded because the image is either corrupt, is invalid, or is not available. The interface could not be initialized.
Recommended Action Check the port interface status by entering the show pif command and repeat the operation with the port interface debug logs enabled. Enter the debug pif download command to enable the debug log. 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%PIF-3-DOWNLOAD_SUBSYS_ERROR : [chars]
Explanation The download subsystem could not be created. The download procedure could not be started. It is possible that the download attempt might not succeed.
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%PIF-3-DYN_DOWNLOAD_ERROR : [chars], [chars]
Explanation The image for the port interface could not be downloaded because the image is either corrupt, is invalid, or is not available. The interface could not be initialized.
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%PIF-3-EPIF_MIPC_ERROR : [chars]
Explanation An error occurred while port interface-related operations were being performed on the board. An operation that was performed has failed. This condition may occur if the port interface was not properly initialized.
Recommended Action Enter the show pif command to ensure that the port interface process is operational on the port interface board. 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%PIF-3-GIGE_AUTO_NEG_INIT_ERROR : [chars]
Explanation The gigabit Ethernet auto-negotiation operation has failed while the gigabit Ethernet interface was being configured.
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%PIF-3-GIGE_DISABLE_GMAC_ERROR : [chars]
Explanation While the gigabit Ethernet interface was being disabled, the gigabit MAC could not be disabled.
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%PIF-3-GIGE_ENABLE_GGI_ERROR : [chars]
Explanation During the initialization of the gigabit Ethernet interface, the generic gigabit Ethernet interface could not be enabled.
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%PIF-3-GIGE_INIT_GMAC_ERROR : [chars]
Explanation While the gigabit Ethernet interface was being configured, the gigabit MAC could not be initialized.
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%PIF-3-GIGE_LINKUP_INIT_ERROR : [chars]
Explanation The gigabit Ethernet linkup initialization operation has failed while gigabit Ethernet was being configured
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%PIF-3-IDB_CONFIG_PUNT_ERROR : Error configuring [char]PIF on RSC [dec] for packet punting
Explanation The system could not configure the specified hardware to redirect packets to the specified RSC. The most likely cause of this condition is the absence or failure of the peer RSC.
Recommended Action Replace or insert the peer RSC. 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%PIF-3-PIF_INTERNAL : Internal PIF error [[chars]]
Explanation An internal error occurred within the PIF driver software.
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%PIF-3-PIF_MAC_ERROR : [chars], [chars]
Explanation An internal software error has occurred. An internal module failed to allocate a MAC address to a port. This condition may lead to a communication failure between the RSC and the feature board.
Recommended Action Reload the gateway to attempt to fix the problem. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show pif and show tech-support commands. 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%PIF-3-PIF_RESET_INT : Function [chars] called from interrupt context
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%PIF-3-READ_IMEM_ERROR : [chars], [chars]
Explanation An error occurred while port interface-related operations were being performed on the board. An operation that was performed has failed. This condition may occur if the port interface was not properly initialized.
Recommended Action Enter the show pif command to ensure that the port interface process is operational on the port interface board. 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%PIF-3-READ_PHY_ERROR : [chars], [chars]
Explanation An error occurred while port interface-related operations were being performed on the board. An operation that was performed has failed. This condition may occur if the port interface was not properly initialized.
Recommended Action Enter the show pif command to ensure that the port interface process is operational on the port interface board. 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%PIF-3-SLICER_ENABLE_ERROR : Enabling Tx/Rx on SMDR for [chars] port[dec] failed
Explanation An error relating to the port interface has occurred. The enabling of the transceiver on the station message detail recording port has encountered an error.
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%PIF-3-UNKNOWN_EGRESS_CARD_TYPE_ERROR : Unknown Egress Card type [hex] for RSC [dec].
Explanation The system could not configure the specified hardware. The most likely cause is that the egress card is either unsupported or has experienced a hardware failure.
Recommended Action Replace the RSC or the egress card of the RSC. 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%PIF-3-WRITE_IMEM_ERROR : [chars], [chars]
Explanation An error occurred while port interface-related operations were being performed on the board. An operation that was performed has failed. This condition may occur if the port interface was not properly initialized.
Recommended Action Enter the show pif command to ensure that the port interface process is operational on the port interface board. 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%PIF-3-WRITE_PHY_ERROR : [chars], [chars]
Explanation An error occurred while port interface-related operations were being performed on the board. An operation that was performed has failed. This condition may occur if the port interface was not properly initialized.
Recommended Action Enter the show pif command to ensure that the port interface process is operational on the port interface board. 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%PIF-3-XPIF_MIPC_ERROR : [chars]
Explanation An error occurred while port interface-related operations were being performed on the board. An operation that was performed has failed. This condition may occur if the port interface was not properly initialized.
Recommended Action Enter the show pif command to ensure that the port interface process is operational on the port interface board. 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 Messages
The following are Protocol Independent Multicast (PIM) messages.
Error Message%PIM-4-DEPRECATED_HELLO_TLV : Deprecated PIM Hello Option TLV [dec] ([chars]) from [IP_address] ([chars])
Explanation A PIM neighbor is running old Cisco IOS software that uses obsolete Hello Option TLVs. Unless the router is upgraded, multicast DR priority and bidirectional groups might not function properly.
Recommended Action Upgrade all the routers to the latest Cisco IOS software version in your release train.
Error Message%PIM-6-INVALID_RP_JOIN : Received (*, [IP_address]) Join from [IP_address] for invalid RP [IP_address]
Explanation A downstream PIM router has sent a join message for the shared tree, which this router does not want to accept. This behavior indicates that this router will let only downstream routers join to a specific rendezvous point.
Recommended Action Configure all downstream leaf routers (first-hop routers to multicast sources) to join to the RP that is allowed by upstream routers toward the validated rendezvous point.
Error Message%PIM-1-INVALID_RP_REG : Received Register from [IP_address] for [IP_address], not willing to be RP
Explanation A PIM router has received a register message from another PIM router that is configured as the rendezvous point. If the router is not configured for another rendezvous point, it will not accept the register message.
Recommended Action Configure all leaf routers (first-hop routers to multicast sources) with the IP address of the valid rendezvous point.
Error Message%PIM-4-INVALID_SRC_REG : Received Register from [IP_address] for ([IP_address], [IP_address]), not willing to be RP
Explanation A PIM router configured as a rendezvous point has received a register message from another PIM router, but the source of the multicast data is disallowed in this RP.
Recommended Action No action is required.
Error Message%PIM-6-REG_ENCAP_INVALID : Bad register from [IP_address] for ([IP_address], [IP_address]); additional info = [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation A PIM router that is configured as a rendezvous point or configured with NAT has received a PIM register packet from another PIM router. The data that is encapsulated in this packet is invalid.
Recommended Action No action is required.
Error Message%PIM-6-SA_ENCAP_INVALID : Bad SA from RP [IP_address] for ([IP_address], [IP_address]); additional info = [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation A PIM router that is configured as an MSDP peer has received an SA with encapsulated data. The data that is encapsulated in this packet is invalid.
Recommended Action No action is required.
Error Message%PIM-1-SR_INTERVAL_SETTING_ERR : Incompatible SR interval from [IP_address] on [chars] ([dec] != [dec])
Explanation A state-refresh-capable PIM neighbor on this interface has a different, incompatible setting for the state-refresh origination interval from other routers that are connected to the LAN.
Recommended Action Configure all PIM routers connected to this LAN to use the same state-refresh origination interval for their interfaces on the LAN.
PKTS Messages
The following are channel adapter messages that are related to the packet switching API.
Error Message%PKTS-3-BUFLEN : Zero length buffer detected in [chars] for [chars]([hex])
Explanation An application buffer error has been detected in the channel adapter packet-switching API.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PKTS-3-CONSISTENCY : [chars] : [chars] [hex] [dec]
Explanation A consistency error has been detected in the channel adapter packet-switching API.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PKTS-3-INIT : [chars] ([dec])
Explanation The CMCC packet switching initialization has failed because of a lack of memory on the card. Packets will not be switched between the CMCC card and the Route Processor.
Recommended Action Verify that the amount of memory installed an the CMCC card is capable of supporting the configured CMCC microcode.
Error Message%PKTS-3-NOSUPP : [chars] ([hex],[hex])
Explanation An attempt was made to call a function in a packet-switching API control block that was not implemented or supported.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PKTS-3-NOTREADY : packet switching API not initialized - [chars]
Explanation An attempt was made to call a function in a packet-switching API before the initialization of the API was complete.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PKTS-3-SEGMENT : [chars] : [chars] [hex] [dec]
Explanation A data buffer containing too many segments or particles to transmit to the platform Route Processor was detected. The packet is being dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 either a hardware or a software problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PLATFORM-4-IOMEM_MISMATCH : I/O memory size mismatch. Configured size is [dec], allocated size is [dec]
Explanation The allocated I/O memory size does not agree with the configured size.
Recommended Action Reboot the router to reallocate I/O memory.
Error Message%PLATFORM-4-NOCPUVER : Invalid CPU ID, assuming revision 1
Explanation The CPU ID could not be read from the EEPROM. This condition is probably due to a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PLATFORM-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation MAC address allocation failed because of an incorrect slot and port combination, which is out of range for the available hardware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PLATFORM-3-PACONFIG : Exceeds [dec] [chars]
Explanation The total bandwidth of fast and medium bandwidth port adapters exceeds the rated capacity of this system.
Recommended Action Refer to the configuration guidelines for the maximum allowed high- and medium-bandwidth port adapters for the system.
Error Message%PLATFORM-4-RECALLED_NPE : Old version NPE-175/225 with Rev = [hex] system controller. Contact \n upgrades-info@cisco.com for replacement
Explanation The NPE board has been recalled because of an error in the system controller chip.
Recommended Action Replace the NPE-175/225 board.
Error Message%PLATFORM-4-WARN_EXT_INT : Potential loss of external error interrupt, intreg = [hex]: [chars]\n
Explanation The hardware interface for FPGA initialization has masked external error interrupts.
Recommended Action Verify that the OIR still functions.
PM Messages
The following are Port Manager messages.
Error Message%PM-4-BAD_APP_ID : an invalid application id ([dec]) was detected
Explanation An invalid request has been detected by the Port Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-4-BAD_APP_REQ : an invalid [chars] request by the '[chars]' application was detected
Explanation An invalid request has been detected by the Port Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-4-BAD_CARD_COOKIE : an invalid card cookie was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-4-BAD_CARD_SLOT : an invalid card slot ([dec]) was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-4-BAD_COOKIE : [chars] was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-4-BAD_PORT_COOKIE : an invalid port cookie was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-4-BAD_PORT_NUMBER : an invalid port number ([dec]) was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-4-BAD_VLAN_COOKIE : an invalid vlan cookie was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-4-BAD_VLAN_ID : an invalid vlan id ([dec]) was detected
Explanation An invalid request was detected by the Port Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-4-BIT_OUTOFRANGE : bit [dec] is not in the expected range of [dec] to [dec]
Explanation An invalid request has been detected by the Port Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-4-ERR_DISABLE : [chars] error detected on [chars], putting [chars] in err-disable state
Explanation The interface has detected a misconfiguration or misbehavior. The interface will be put in the err-disable state. This action is a defensive measure. A recovery will be attempted after the configured retry time. The default retry time is 5 minutes.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-4-ERR_RECOVER : Attempting to recover from [chars] err-disable state on [chars]
Explanation The system is attempting to bring the interface up after taking it down to the err-disable state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-2-NOMEM : Not enough memory available for [chars]
Explanation The Port Manager subsystem could not obtain the memory it required.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PM-3-NON_SWITCHABLE_PORT : Non-switchable port: [chars].
Explanation The command cannot be performed on the specified port. A switch port configuration command is valid only on ports that support hardware packet switching.
Recommended Action Do not attempt to use switch port commands on standard routed ports. Check the name of the interface you are configuring against the actual hardware.
Error Message%PM-3-PORT_NOT_SHUTDOWN : [chars].
Explanation The command cannot be performed on the specified port. A switch port configuration command is valid only on ports that are shut down.
Recommended Action Do not attempt to use switch port commands until the port has been shut down.
Error Message%PM-4-TOO_MANY_APP : application '[chars]' exceeded registration limit
Explanation An invalid request has been detected by the Port Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
PM_MODEM_HIST Messages
The following are modem history and tracing messages.
Error Message%PM_MODEM_HIST-7-CSM_IC_CALLED_NUM : \n[chars]: ISDN incoming called number: [chars]
Explanation This tracing message indicates the number of the ISDN line that is receiving a call.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-CSM_IC_CALLING_NUM : \n[chars]: ISDN incoming caller number: [chars]
Explanation This tracing message indicates the number of an incoming ISDN caller.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-CSM_OC_CALLED_NUM : \n[chars]: ISDN outgoing called number: [chars]
Explanation This tracing message indicates a dialed ISDN number.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-MODEM_DYNAMIC_EVT : \n[chars]: [chars] \n[chars]
Explanation This tracing message indicates a dynamic event reported by the specified modem.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-MODEM_END_CONN_EVT : \n[chars]: [chars] \n[chars]
Explanation This tracing message indicates an end-of-connection event from the specified modem.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-MODEM_ROS_EVT : \n[chars]: [chars] \n[chars]
Explanation This tracing message indicates a link rate event reported by the specified modem.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-MODEM_STATE_EVT : \n[chars]: [chars]\n[chars] State: [chars]
Explanation This tracing message indicates a state event reported by the specified modem.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-MODEM_STATIC_EVT : \n[chars]: [chars] \n[chars]
Explanation This tracing message indicates a static event reported by the specified modem.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-PORT_STATE_REACHED_NTF_EVT : \n[chars]: [chars] [chars]
Explanation This tracing message indicates a link rate event reported by the specified modem.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-TRACE_HDR : \n\nModem [chars] Events Log:
Explanation This is the initial message for the trace of the specified modem. The stored trace messages of the modem will follow.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-UNKNOWN_EVENT : \n[chars]: Error in events log
Explanation This tracing message indicates a formatting error in the modem event history. One or more events may be missing from the trace.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_HIST-7-UNKNOWN_FRAME : \n[chars]: Error in events log
Explanation This tracing message indicates a formatting error in the modem event history. One or more events may be missing from the trace.
Recommended Action This is a debug message only. No action is required.
PM_MODEM_MAINT Messages
The following are modem maintenance messages.
Error Message%PM_MODEM_MAINT-4-B2BABORT : Modems ([chars]) and ([chars]) back-to-back test: aborted
Explanation This tracing message indicates that a back-to-back test has failed for the two specified MICA modems.
Recommended Action Perform more back-to-back tests by pairing the failed modems with other modems to determine which modem has failed. Check the failed modems again after performing a power cycle. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PM_MODEM_MAINT-5-B2BCONNECT : Modems ([chars]) and ([chars]) connected in back-to-back test: [chars]
Explanation A back-to-back test connection has been made between the selected modems. The test is in progress.
Recommended Action No action is required.
Error Message%PM_MODEM_MAINT-5-B2BINIT : Auto Back-to-Back test initiated by [chars]
Explanation An automatic back-to-back test has been initiated by the specified MICA modem.
Recommended Action This is a debug message only. No action is required.
Error Message%PM_MODEM_MAINT-5-B2BMODEMS : Modems ([chars]) and ([chars]) completed back-to-back test: success/packets = [dec]/[dec]
Explanation The reported modems have passed the back-to-back test with no errors.
Recommended Action No action is required.
Error Message%PM_MODEM_MAINT-1-BADEVENT : Invalid modem management [chars] event [hex] for modem([chars])
Explanation The modem management facility has received an unrecognized event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PM_MODEM_MAINT-1-BADMODEM : Modem ([chars]) failed [chars]
Explanation A software or hardware problem has been detected on a modem. The specific modem and reason are provided in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PM_MODEM_MAINT-4-BADMODEMS : Modems ([chars]) and ([chars]) failed back-to-back test: [chars]
Explanation The two modems that are specified in the message have failed a back-to-back test. At least one of the modems has failed.
Recommended Action Perform more back-to-back tests by pairing the failed modems with other modems to determine which modem has failed. Check the failed modems again after performing a power cycle. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PM_MODEM_MAINT-1-INITFAIL : Initialization failed.
Explanation The modem maintenance facility initialization has failed.
Recommended Action Disable autotest and power-on test and avoid performing a manual back-to-back test. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PM_MODEM_MAINT-5-MODEM_OK : Modem ([chars]) passed the test
Explanation The tests on the specified modem were successful.
Recommended Action No action is required.
PMSM Messages
The following are Port Manager state machine messages.
Error Message%PMSM-4-BADEVENT : Event '[chars]' is invalid for the current state '[chars]': [chars] [chars]
Explanation The Port Manager subsystem attempted to post an event to a state machine that is invalid for the current state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PMSM-4-INIT : Internal error while initializing state machine '[chars]', state '[chars]': [chars]
Explanation An invalid request was detected by the Port Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PMSM-4-NOTIDLE : Attempted to stop state machine [chars] [chars] but it is not idle
Explanation The Port Manager subsystem attempted to stop a state machine that has pending events.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PMSM-4-STOPPED : Event '[chars]' ignored because the state machine is stopped: [chars] [chars]
Explanation The Port Manager subsystem attempted to post an event to a state machine that has already been stopped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PMSM-4-TOOMANY : Event '[chars]' ignored because there are too many pending events: [chars] [chars]
Explanation The Port Manager subsystem attempted to post an event to a state machine that already has the maximum number of events pending.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PMSM-4-UNKNOWN : Event ([dec]) is unknown for the state machine: [chars] [chars]
Explanation The Port Manager subsystem attempted to post an unknown event to a state machine.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
PM-SP Messages
The following are Port Manage SP messages.
Error Message%PM-SP-4-ERR_DISABLE : [chars] error detected on [chars] putting [chars] in err-disable state,
Explanation The port manager detected a misconfiguration or misbehavior and placed the interface in an error-disabled state. A recovery is attempted after the configured retry time (the default is 5 minites). On PoE switches, this message might appear when a devcie that can be powered by either a PoE switch or by AC power is not being powered by an external AC power source and is connected to a port that has been configured with the power inline never interface configuration command. [chars] is the port where the threshold was exceeded. The first [chars] is the error and the second and third [chars] are the affected interfaces.
Recommended Action On non-PoE switches, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEX command to gather data that might 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%PM-SP-4-ERR_RECOVER : Attempting to recover from [chars] err-disable state on [chars].
Explanation The port manager is attempting to bring the interface up after taking it down to the error-disabled state. The first [chars] is the error and the second [chars] is the affected interface.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.PNNI Messages
The following are Private Network-Network Interface (PNNI) messages.
Error Message%PNNI-4-ADDRESS_EXIST : Address derived from the switch's prefix by soft PVC manager [chars] clashes with existing address in prefix table
Explanation A PVC port address assignment has collided with an existing address. An address that would have been assigned by this switch has already been assigned by another.
Recommended Action If it is possible, assign a new MAC address to the peer system that caused the assignment collision.
Error Message%PNNI-4-ATM_SYS_ERROR : Error: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PNNI-4-BADPACKET : Invalid [chars] pkt: [chars] [dec] [dec]
Explanation An invalid packet has been received from a network peer.
Recommended Action Check the originating device for a cause of the corrupted packets.
Error Message%PNNI-4-BADROUTEREQ : Bad Request from Signaling [hex]
Explanation A source routing request by another network host has been corrupted.
Recommended Action Check the originating system for a cause of the problem.
Error Message%PNNI-4-CONFIG_ERROR : Configuration Error: [chars]
Explanation A configuration error has occurred in the PNNI subsystem. The message will display more specific information about the cause of problem.
Recommended Action Change the configuration to correct the error.
Error Message%PNNI-7-DEBUG : [chars]
Explanation This is an informational message only. It is used by Cisco for testing.
Recommended Action No action is required. Informational messages can be disabled by changing the logging level.
Error Message%PNNI-4-DUPLICATE_NODE_ID : [chars] [chars] for node [dec] [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PNNI-6-INFO : [chars]
Explanation This is an informational message only.
Recommended Action No action is required. Informational messages can be disabled by changing the logging level.
Error Message%PNNI-3-INTERNAL_ERROR : [chars][chars] [hex]
Explanation An internal software error has occurred. The message contains more information that can be used to identify the problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PNNI-3-INVALID_MEM : Bad address of [chars] [hex], please collect "show atm pnni trace error"
Explanation An internal software error has occurred.
Recommended Action Enter the show atm pnni trace error command to collect additional information that might help solve the problem. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PNNI-2-NO_INTERNAL_NUMBER : Empty Internal Number Stack: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PNNI-2-SPF_ERROR : Tent List Overflow in [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
PORT Messages
The following are Port Management messages.
Error Message%PORT-6-NULL_OBJ : Port object [chars] is unavailable.
Explanation Information about the specified port could not be retrieved. The port may not exist.
Recommended Action No action is required.
Error Message%PORT-6-PORT_RECOVERY : [chars] [chars]
Explanation Recovery has been triggered, and configured action will take place on the port.
Recommended Action No action is required.
Error Message%PORT-6-SESSION_RECOVERY : [chars] [chars] [dec]
Explanation The session recovery has an invalid cause code.
Recommended Action No action is required.
Error Message%PORT-6-SM_PORT_CLEARED : [chars]
Explanation The ports have been be reset, and any active calls on these ports will be terminated.
Recommended Action No action is required.
POS Messages
The following are Packet over SONET (PoS) subsystem messages.
Error Message%POS-3-HW_FAULT : POS HW error, [chars], error_code=[hex]
Explanation A PoS operation error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%POS-3-INTERNAL : POS internal error, [chars]
Explanation An internal PoS error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%POS-3-MAJOR_FAULT : POS unrecoverable error, [chars], error_code=[hex]
Explanation A PoS operation error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%POS-3-MIBINITFAIL : POS MIB initialization failed, [chars]
Explanation The MIB for PoS failed to initialize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%POS-5-PERIODIC_STATS : POS periodic stats collection not run for [dec] seconds
Explanation The collection of PoS statistics has been delayed. This delay is most likely caused by the RP being busy with high-priority tasks. This condition can cause line alarms to be triggered for a short period of time. The time-based statistics for this interface may also be skewed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%POS-3-POSMISMATCH : [chars], expected [hex], actual [hex]
Explanation The PCI for PoS failed to initialize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 Packet over SONET double-wide PCI port adapter driver hardware has failed. An incorrect number of interfaces has been discovered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%POSDW-1-INITFAIL : [chars] init timed out
Explanation The port adapter of the Packet over SONET double-wide PCI port adapter driver has failed to complete its hardware initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%POSDW-3-NOTPOSDW : Device reported [hex]
Explanation The Packet over SONET double-wide PCI port adapter driver hardware has failed. A non-Packet over SONET double-wide PCI port adapter driver device pointed at the software for the Packet over SONET double-wide PCI port adapter driver.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%POSDW-3-OWNERR : [chars] packet buffer, pak=[hex]
Explanation A software or hardware error has occurred. The driver of the Packet over SONET double-wide PCI port adapter driver has detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%POSDW-3-UNSUPPORTED : [chars]\n
Explanation The Packet over SONET double-wide PCI port adapter driver hardware is not supported on this platform.
Recommended Action Upgrade your system.