|
|
The following are online insertion and removal (OIR) error messages.
Error Message
%OIR-6-INSCARD: Card inserted in slot [dec], subcard [dec], interfaces administratively shutdownExplanation The specified hot-swappable card was inserted into the system. The interfaces on the card will remain administratively disabled until specifically enabled, because they may need to be configured.
Recommended Action Configure the interfaces and enable them.
Error Message
%OIR-3-LONGSTALL: Long bus stall ([int] s) , the new PAM may not be seated properly. Please remove it and try againExplanation A hot-swappable card that was inserted into the system has failed to respond. The card may not be seated properly.
Recommended Action Remove and reinsert the specified card. If the message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%OIR-6-REMCARD: Card removed from slot [dec], subcard [dec], interfaces disabledExplanation The specified hot-swappable card was removed from the system.
Recommended Action This message is informational only. No action is required.
The following are out of band port (OOBP) error messages.
Error Message
%OOBP-4-ASYNC_NO_RSP: Warning -- reset async oobp no responseExplanation The asynchronous driver does not response to the async reset command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 usedExplanation The asynchronous driver cannot send out the out of band port (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, call 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 stateExplanation An out of band port (OOBP) response time-out has occurred at the wrong OOBP state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Open Shortest Path First (OSPF) error messages.
Error Message
%OSPF-5-ADJCHG: Process [dec], Nbr [int] on [chars] from [chars] to [chars], [chars]Explanation An Open Shortest Path First (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: [int][inet] changed from area [chars] to area [chars]Explanation An Open Shortest Path First (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 [int] Old Checksum [hex] New Checksum [hex]Explanation Open Shortest Path First (OSPF) has detected a checksum error caused by memory corruption in the database.
Recommended Action Restart the OSPF process.
Error Message
%OSPF-4-BADLENGTH: Invalid length [dec] in OSPF packet from [int] (ID [int]), [chars]Explanation The system has received an Open Shortest Path First (OSPF) packet with 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 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
%OSPF-4-BADLSATYPE: Invalid lsa: [chars] Type [dec], LSID [int] from [int], [int], [chars]Explanation The router has received a link-state advertisement (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 reboot it. To determine what is causing this problem, call your Cisco technical support representative for assistance.
Error Message
%OSPF-4-CONFLICTING_LSAID: Found LSA with the same host bit set but using different maskExplanation 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 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
%OSPF-3-DBEXIST: area [chars] lsid [int] mask [int] adv [int] type [dec]Explanation Open Shortest Path First (OSPF) has a problem locating the link-state advertisement (LSA). This condition could lead to a memory leak.
Recommended Action Check for possible routing problems and monitor the log of the router for recurrence of this message. If routing problems are discovered, or if the message recurs, upgrade your Cisco IOS software version. If the upgrade fails to correct the problem, contact Cisco technical support.
Error Message
%OSPF-3-DUP_RTRID: OSPF detected duplicate router-id [int] from [int] on interface [chars]Explanation Open Shortest Path First (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
%OSPF-4-ERRRCV: Received invalid packet: [chars] from [int], [chars]Explanation An invalid Open Shortest Path First (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-INIT_IDB: OSPF is enabled on [chars] during idb initializationExplanation 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 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
%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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%OSPF-3-NOBACKBONE: Flagged as being an ABR without a backbone areaExplanation The router was flagged as an Area Border Router (ABR) without backbone area in the router.
Recommended Action Restart the Open Shortest Path First (OSPF) process.
Error Message
%OSPF-3-NOCONNDB: No database entry for connected address [int]Explanation While calculating Open Shortest Path First (OSPF) routes, the router could not find the link-state advertisement that represents the connected route in the router.
Recommended Action To clear the IP routes in the routing table, use the clear ip route {address} command.
Error Message
%OSPF-3-NOLSA: Failed to find this routers LSA in [chars]Explanation The router is not able to find its own router link-state advertisement. This error can occur occasionally and will self-correct. However, if this message recurs, restart the Open Shortest Path First (OSPF) process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%OSPF-2-NOMEMORY: No memory for [chars]Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%OSPF-4-NONEIGHBOR: Received [chars] from unknown neighbor [int]Explanation An Open Shortest Path First (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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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 IDExplanation Open Shortest Path First (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 up interfaces 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 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
%OSPF-6-NOSRCPDB: ex_route_callback(): Can't find the src protocol to redistribute net [int][inet]Explanation Open Shortest Path First (OSPF) attempted to redistribute a route but could not find a valid source protocol.
Recommended Action No action is required.
Error Message
%OSPF-6-NOTREDIST1: ex_route_callback(): do not redistribute net [int][inet], [chars]Explanation This message is informational only.
Recommended Action No action is required.
Error Message
%OSPF-6-NOTREDIST3: build_ex_route(): don't redistribute net [int][inet], [int] advertises it alreadyExplanation This message is informational only.
Recommended Action No action is required.
Error Message
%OSPF-4-NOTREDIST4: Database scanner: external LSA [int][inet] is lost, reinstallsExplanation The software has detected an unexpected condition. The router will take corrective action and continue.
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
%OSPF-4-NOTREDIST5: db_free: external LSA [int][inet]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 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
%OSPF-3-RDB_NO_LSA: lsid [int] adv [int] type [dec] gateway [int] metric [dec] network [int] mask [int] protocol [hex] attr [hex] net-metric [dec]Explanation Open Shortest Path First (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 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
%OSPF-3-RECONF_VL: OSPF process [dec] is changing router-id. Reconfigure virtual link neighbors with our new router-idExplanation The Open Shortest Path First (OSPF) process is being reset, and it will to select a new router ID. This process will bring down all virtual links. For them to work again, the virtual link configuration must be changed on all virtual link neighbors.
Recommended Action Change virtual link configuration on all the virtual link neighbors to reflect the router ID.
Error Message
%OSPF-3-UNKNOWNSTATE: Reached unknown state in neighbor state machineExplanation 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 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
%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 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
%OSPF-6-ZERO_BANDWIDTH: interface [chars] has zero bandwidthExplanation The interface has reported its bandwidth as zero.
Recommended Action No action is required.
The following are port adapter (PA) error messages.
Error Message
%PA-2-BADDAT: PA interface data incorrect, [hex]Explanation Incorrect port adapter (PA) interface data has been found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 port adapter system control block (PASCB) data structure indicates a zero interface descriptor block (IDB).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 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, call 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 (PA) interface has been specified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 (PA) interface has been specified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 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, call 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 (PASCB) 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, call 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 port instance internal data has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 virtual circuit (VC) interface has been specified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 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
%PA-3-CONFIG: Recommended port adapter configuration exceededExplanation The total bandwidth of fast and medium bandwidth port adapters has exceeded the rated capacity of this system.
Recommended Action Refer to the configuration guidelines for the maximum allowed fast and medium bandwidth port adapters for the system.
Error Message
%PA-3-DEACTIVATED: port adapter in bay [[dec]] powered offExplanation 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 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
%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-2-INCORRECTBRIDGEREG: Bad default register([hex]) setting([hex]) in PA bridgeExplanation The software is unable to configure certain settings for the port adapter protocol control information (PCI) bridge in the specified bay.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 This port adapter 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, call 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 protocol control information (PCI) bridge for this port adapter (PA) has failed initialization. The PA therefore will not be operational.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 This message indicates a possible memory shortage or port adapter hardware error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 chassismib, the platform Simple Network Management Protocol (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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PA-4-PCIVALID: PCI activation failed, bay [dec], 0x[hex]Explanation The system has received an invalid protocol control information (PCI) signal from the specified port adapter. This error was probably caused by a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 (PA) 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, call 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, call 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PA-2-UNDEFPA: Undefined Port Adaptor type [dec] in bay [dec]Explanation The software does not have a driver for the specified port adapter type located in the specified bay.
Recommended Action Ensure that the image you are running supports this card. Check that the card is properly seated. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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 that port adapter protocol control information (PCI) bridge located in the specified bay.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are X.25 packet assembler/disassembler error 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 and report it to your Cisco technical support representative.
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 and report it to your Cisco technical support representative.
Error Message
%PAD-2-PUTSETUP: Tty[t-line], buffer already setupExplanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your Cisco technical support representative.
The following are parser error messages.
Error Message
%PARSER-4-BADCFG: Unexpected end of configuration fileExplanation This message occurs when a configuration is read from the Trivial File Transfer Protocol (TFTP) server or NVRAM and the end of the file is encountered before the end statement. The configuration may be corrupted or incomplete. What was read is in effect.
Recommended Action Make sure the configuration is correct. Then, to write the correct configuration to NVRAM, execute either a copy running-config command or a startup-config command. To write to a network TFTP server, execute a copy running-config tftp command.
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, call 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PARSER-3-CREATEINT: Can't create any more subinterfacesExplanation 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, call 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, call 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]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, call 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 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 version command to gather data that may provide information to determine the nature of the error. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%PARSER-4-LINKPOINT: Parser reached link_pointExplanation 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, call 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, call 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 setExplanation 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, call 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 chainExplanation 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, call 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 flagExplanation 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, call 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 setExplanation 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, call 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, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are PPP per-user configuration error messages.
Error Message
%PERUSER-3-ISDNINTF: [chars] [chars]: Can not apply configuration to ISDN channel:Explanation The configuration cannot be applied to individual ISDN channels.
Recommended Action You must have virtual profiles and virtual access interfaces in order to apply the configuration to ISDN. Refer to the Cisco IOS Dial Services Configuration Guide for more information on virtual profiles.
The following are Pragmatic General Multicast (PGM) error messages.
Error Message
%PGM-6-DLR_ADDR_ERR: Invalid DLR address [int]Explanation A OPT_RDIR with invalid Designated Local Retransmitter (DLR) address has been received.
Recommended Action No action is required.
Error Message
%PGM-3-EXP_TSI_SQN_ERR: Expiring TSI [chars] has retransmit stateExplanation An expiring Pragmatic General Multicast (PGM) transmitting subscriber information (TSI) frame has remained in an unexpired retransmit state. This condition can occur only because of an internal error or because of unfreeable memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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 [int] received on [int], fixed input interfaceExplanation A Pragmatic General Multicast (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 Pragmatic General Multicast (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 Pragmatic General Multicast (PGM) process is busy, either because of excessive retransmit states 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] stateExplanation Not enough memory is available to allocate a retransmit state.
Recommended Action To manually clear all retransmit states, use the clear ip pgm router command or deconfigure and reconfigure the Pragmatic General Multicast (PGM) router. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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] stateExplanation Not enough memory is available to free the specified retransmit state.
Recommended Action To manually clear all retransmit states, use the clear ip pgm router command or deconfigure and reconfigure the Pragmatic General Multicast (PGM) router. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PGM-6-TSI_GROUP_CHANGE: TSI group changed from [int] to [int]Explanation A Pragmatic General Multicast (PGM) Source Path Message (SPM) that is advertising a new group for the transmitting subscriber information (TSI) has been processed.
Recommended Action No action is required.
Error Message
%PGM-6-TSI_SOURCE_CHANGE: TSI source changed from [int] to [int]Explanation A Pragmatic General Multicast (PGM) Source Path Message (SPM) that is advertising a new source for the transmitting subscriber information (TSI) has been processed.
Recommended Action No action is required.
The following are Protocol Independent Multicast (PIM) error messages.
Error Message
%PIM-6-INVALID_RP_JOIN: Received (*, [int]) Join from [int] for invalid RP [int]Explanation A downstream Protocol Independent Multicast (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 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 [int] for [int], not willing to be RPExplanation A Protocol Independent Multicast (PIM) router received a register message from another PIM router that thinks it is 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-1-INVALID_SRC_REG: Received Register from [int] for ([int], [int]), not willing to be RPExplanation A Protocol Independent Multicast (PIM) router configured as a rendezvous point has received a register message from another PIM router but the source of the multicast data is not allowed in this Route Processor (RP).
Recommended Action No action is required.
Error Message
%PIM-5-REG_ENCAP_INVALID: Bad register from [int] for ([int], [int]). Trace = [hex] [hex] [hex]Explanation A Protocol Independent Multicast (PIM) router configured as a rendezvous point or with Network Address Translation (NAT) has received a PIM Register packet from another PIM router. The data encapsulated in this packet is invalid.
Recommended Action No action is required.
The following are platform-specific error messages.
Error Message
%PLATFORM-4-COOKIE: Corrupt or missing MAC address cookieExplanation 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PLATFORM-4-NOCPUVER: Invalid CPU ID, assuming revision 1Explanation The CPU ID could not be read from the EEPROM. This error is probably caused by a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 The MAC address allocation has failed because of an incorrect slot and port combination that exceeds the maximum available hardware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 fast and medium bandwidth port adapters for the system.
Error Message
%PLATFORM-4-RECALLED_NPE: Old version NPE-175/225 with Rev = 0x[hex] system controller. Contact upgrades-info@cisco.com for replacementExplanation The NPE board has been recalled because of an error in the system controller chip.
Recommended Action Contact Cisco to replace the NPE-175/225 board.
The following are Multilayer Switch Feature Card (MSFC) error messages.
Error Message
%PLATFORM_IMAGE_PREFIX-4-BADFLASH: Unsupported flash type in the bootflash - [chars]Explanation The flash chips in the Flash SIMM are not supported by the platform.
Recommended Action Contact Cisco technical support to update your system.
Error Message
%PLATFORM_IMAGE_PREFIX-3-CHASSIS: Unknown chassis model.Explanation The data stored in the CPU IDPROM is defective or incomplete.
Recommended Action Contact technical support to update your system.
Error Message
%PLATFORM_IMAGE_PREFIX-4-MACBLKSIZE: Unknown MAC address block sizeExplanation Data stored in CPU IDPROM is defective or incomplete.
Recommended Action Contact Cisco technical support to update your system.
The following are Private Network-Network Interface (PNNI) error 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 tableExplanation An permanent virtual circuit (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 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, call 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 the cause of the problem.
Error Message
%PNNI-4-CONFIG_ERROR: Configuration Error: [chars]Explanation There is a configuration error 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.
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, call 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.
Error Message
%PNNI-3-INTERNAL_ERROR: [chars][chars] [hex]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, call 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 errorExplanation An internal software error has occurred.
Recommended Action To collect more information, use show atm pnni trace error command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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 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 %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, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Packet over SONET double wide PCI port adapter driver error messages.
Error Message
%POSDW-1-DISCOVER: Only found [dec] interfaces on bay [dec], shutting down bayExplanation 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POSDW-1-INITFAIL: [chars] init timed outExplanation The Packet over SONET double wide PCI port adapter driver port adapter has failed to complete the hardware initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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-POSDW device pointed at the software for the POSDW.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POSDW-3-OWNERR: [chars] packet buffer, pak=0x[hex]Explanation A software or hardware error has occurred. The Packet over SONET double wide PCI port adapter driver driver has detected that the transmit ring is an inconsistent and unrecoverable state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POSDW-3-UNSUPPORTED: [chars]Explanation The Packet over SONET double wide PCI port adapter driver hardware is not supported on this platform.
Recommended Action Upgrade your system.
The following are Versatile Interface Processor (VIP) multichannel port adapter error messages.
Error Message
%POT1E1-3-BADMSG: Received unexpected mailbox message (id = [dec])Explanation The Versatile Interface Processor (VIP) multichannel port adapter mailbox has received an unexpected message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-1-CONFIGURE: Fail to configure [dec] interfaces on bay [dec], shutting down bayExplanation An attempt to configure the specified interfaces has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-1-DISCOVER: only found [dec] interfaces on bay [dec], shutting down bayExplanation A bay has been shut down, either because of incompatible interfaces or because of a hardware failure involving the Versatile Interface Processor (VIP) multichannel port adapter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-1-DWNLDCKSM: Failed for bay [dec], sent = 0x[hex], received = 0x[hex]Explanation The download of the internal firmware to the Versatile Interface Processor (VIP) multichannel port adapter has failed to checksum correctly. This error usually indicates a hardware failure.
Recommended Action Perform a power cycle. If the problem persists, the VIP multichannel port adapter hardware may be defective.
Error Message
%POT1E1-1-DWNLDFAIL: Download failedExplanation The microcode download to the Versatile Interface Processor (VIP) multichannel port adapter has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-3-ERROR: [chars]Explanation An error involving the Versatile Interface Processor (VIP) multichannel port adapter has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-1-INITFAIL: Slot [dec]: [chars]Explanation The Primary Rate Interface (PRI) port adapter has failed to complete a hardware initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-3-LOVEFAIL: [chars]: failed to send [chars] love letterExplanation The Versatile Interface Processor (VIP) multichannel port adapter has failed to send for a love letter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-3-MBOXRECV: Bay [dec]: fail receiving mbox reply [dec]Explanation The Versatile Interface Processor (VIP) multichannel port adapter mailbox has not received an anticipated reply.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-3-MBOXSEND: Bay [dec]: fail sending mbox msg [dec]Explanation The Versatile Interface Processor (VIP) multichannel port adapter mailbox could not send a message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-3-MBOXSENDP: Bay [dec]: fail sending mbox msg [dec] for port [dec]Explanation The Versatile Interface Processor (VIP) multichannel port adapter mailbox has not sent a message for the specified port.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-3-MBXREAD: [chars] has stale msg - mbx0:%lx, mbx1:%lx, mbx2:%lxExplanation The Versatile Interface Processor (VIP) multichannel port adapter mailbox has not responded to a message within the specified period of time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-1-NOTCMPLT: Microcode download failed to completeExplanation The Versatile Interface Processor (VIP) multichannel port adapter hardware has failed. It could not download its operational microcode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-3-NOTPLX: Device is not PLX 9060 - Device reported [hex]Explanation An invalid device has been reported on the Versatile Interface Processor (VIP) multichannel port adapter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-3-NOTPOT1E1: Device is not FREEDM - Device reported [hex]Explanation The Versatile Interface Processor (VIP) multichannel port adapter hardware has failed. A non-VIP multichannel port adapter device had pointed at the software for the VIP multichannel port adapter serial.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-1-NOTREADY: Not ready for download.Explanation An error on the communication path between driver and Versatile Interface Processor (VIP) multichannel port adapter has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-3-OWNERR: serial ([dec]), Buffer ownership error, pak=0x[hex]Explanation An internal buffer ownership error involving the Versatile Interface Processor (VIP) multichannel port adapter has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-3-PANIC: Exception [dec], trace [dec]Explanation The Versatile Interface Processor (VIP) multichannel port adapter firmware has detected an illegal or unexpected CPU exception or condition. This may be caused by a software error or by a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-2-POT1E1FWCRASHED: F/W crashed: [hex] - VIP resetExplanation The Versatile Interface Processor (VIP) multichannel port adapter firmware has reloaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-2-POT1E1FWCRASHEDINFO: [hex] [hex] [hex] [hex]Explanation This message provides information regarding the reload of the Versatile Interface Processor (VIP) multichannel port adapter firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-2-POTBADCMD: bad POT1E1 command [dec]Explanation The Versatile Interface Processor (VIP) multichannel port adapter has received an unsupported command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-1-STARTFAIL: [chars] channel not enabledExplanation A software or hardware error has occurred. The Versatile Interface Processor (VIP) multichannel port adapter serial interface is not responding to the commands that were used to initialize it.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-1-STOPFAIL: [chars] channel not disabledExplanation The Primary Rate Interface (PRI) port adapter has failed to respond to a request to disable an interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%POT1E1-3-TOOSMALL: [chars] - packet was less than two bytesExplanation A packet that is too small (less than two bytes) was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are plain old telephone service (POTS) error messages.
Error Message
%POTS-4-FSM_ERROR: POTS finite state machine error [chars]Explanation The POTS finite state machine utility has encountered a problem.
Recommended Action If voice calls are unavailable, reload the router. If the problem persists, contact your service provider.
Error Message
%POTS-4-INVALID_EVENT: Port [int], Event [int] finite state machine errorExplanation The POTS finite state machine event should not be received in the current state.
Recommended Action If voice calls are unavailable, reload the router. If the problem persists, contact your service provider.
Error Message
%POTS-4-INVALID_PORT: port [int], Ignoring activation, port number is invalidExplanation The POTS driver request is ignored because the port does not exist.
Recommended Action If voice calls cannot be made, reload the router. If the problem persists, contact your service provider.
Error Message
%POTS-1-NOMEMORY: msgtxt_nomemoryExplanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%POTS-1-NULL_COMMON_PTR: null CSM/POTS Driver common pointerExplanation The requested operation could not be accomplished because of a null pointer.
Recommended Action If voice calls are unavailable, reload the router. If the problem persists, contact your service provider.
Error Message
%POTS-4-PROCESS_EVENT_ERROR: POTS subsystem unexpected event [int]Explanation The POTS subsystem process has received an invalid event.
Recommended Action If voice calls are unavailable, reload the router. If the problem persists, contact your service provider.
Error Message
%POTS-4-QUEUE_EMPTY: POTS empty process message [chars]Explanation A POTS interrupt is unable to send a message to the POTS process.
Recommended Action If voice calls are unavailable, reload the router. If the problem persists, contact your service provider.
Error Message
%POTS-4-VDEV_INIT_ERROR: Port [int] device initialization failureExplanation The POTS subsystem initialization has failed.
Recommended Action If voice calls are unavailable, reload the router. If the problem persists, contact your service provider.
The following are PPP error messages.
Error Message
%PPP-4-IPXNET: mismatched IPX network numbers. Ours = [hex], theirs = [hex]Explanation The two ends of a serial link have different Internetwork Packet Exchange (IPX) network numbers.
Recommended Action Confirm the configuration of both devices.
Error Message
%PPP-4-NOAPPOINT: MLP Bundle [chars] not appointedExplanation The Multilink PPP bundle was not appointed. This error probably occurred because of a lack of memory resources.
Recommended Action Record the output of the show memory summary command, and then analyze the output to find a possible memory leak.
Error Message
%PPP-4-NOCLEAR: MLP Bundle [chars] not clearedExplanation A Multilink PPP bundle was not cleared. This error message was most likely to be caused by a lack of memory resources.
Recommended Action Record the output of the show memory summary command, and then analyze the output to find a possible memory leak.
Error Message
%PPP-4-NOEXTTACACS: ppp TACACS is configured but extended TACACS is not.Explanation PPP was configured to use TACACS, but extended TACACS has not been configured or has been disabled.
Recommended Action Either issue the no ppp use-tacacs command to stop PPP from using TACACS or issue the tacacs-server extended command to enable extended TACACS.
Error Message
%PPP-4-NOMAC: Lex ncp: no free Lex interface found with MAC address [sci_notation]Explanation A LAN Extender interface could not be found with the specified MAC address when a LAN Extender link was being brought up. This is a configuration error.
Recommended Action Refer to the documentation on configuring a LAN Extender Interface.
Error Message
%PPP-4-NOREGISTER: NCP not registered, protocol = [dec]Explanation A PPP Network Control Protocol (NCP) request has encountered an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PPP-4-NOSUCHREQ: Illegal PPP request type = [dec]Explanation An illegal PPP request has been received. This error should never happen during normal operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are MPC860 quad integrated communications controller error messages.
Error Message
%PQUICC-1-BADHDXFSM: PQUICC([dec]/[dec]), Unexpected HDX state [dec], event [dec]Explanation A bad event was detected in the state machine for half-duplex transmission and reception.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PQUICC-5-COLL: Unit [dec], excessive collisions. Retry limit [dec] exceededExplanation An Ethernet cable is broken or is not terminated.
Recommended Action Check cables for proper connections and termination.
Error Message
%PQUICC-1-CTSLOST: PQUICC([dec]/[dec]), Clear to Send LostExplanation The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while transmitting a frame. This problem is the result of a communication line failure or cable disconnection.
Recommended Action Check the serial interface cable and the communication equipment, such as the channel service unit/data service unit (CSU/DSU).
Error Message
%PQUICC-5-HBEAT: Unit [dec], heartbeat check failureExplanation The Ethernet transceiver is malfunctioning.
Recommended Action Replace the Ethernet transceiver.
Error Message
%PQUICC-1-INITFAIL: msgtxt_initfailExplanation 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PQUICC-5-LATECOLL: Unit [dec], late collision errorExplanation The Ethernet cable might be too long, or there could be too many repeaters with the result that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users.
Recommended Action Ensure that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these conditions are not the problem, try removing hosts from the Ethernet segment to reduce the load.
Error Message
%PQUICC-1-LINEFLAP: PQUICC([dec]/[dec]), Excessive modem control changesExplanation The system has received too many modem control signal interrupts. Modem control signals are hardware handshake signals between data terminal equipment (DTE) and data communications equipment (DCE). The signals include either a data carrier detect (DCD) or a data set ready (DSR), or both a DCD and a DSR.
Recommended Action Check the serial interface cable. This error can occur if the cable is disconnected or has come loose and is picking up noise. If the cable appears to be connected correctly, check the equipment connected to the cable.
Error Message
%PQUICC-1-LOSTCARR: Unit [dec], lost carrier. Transceiver problem?Explanation The Ethernet 10BASE-T cable is unplugged.
Recommended Action Reconnect the 10BASE-T Ethernet cable.
Error Message
%PQUICC-1-NOMEMORY: msgtxt_nomemoryExplanation The MPC860/PowerQUICC CPU was unable to access the memory it requires to carry out its functions. Here are some possible causes:
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%PQUICC-3-OWNERR: msgtxt_ownerrorExplanation An internal software error has occurred.
Recommended Action Call your Cisco technical support representative to obtain a software upgrade.
Error Message
%PQUICC-1-TOOBIG: PQUICC([dec]/[dec]), packet too bigExplanation A packet greater than the assigned maximum transmission unit (MTU) of this serial interface was queued for transmission.
Recommended Action The system should recover. No action is required. If the message recurs, it may indicate an error related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PQUICC-1-TOOSMALL: PQUICC([dec]/[dec]), packet was less than 2 bytesExplanation A small packet (less than 2 bytes) was queued for transmission. The interface cannot handle such small packets for transmission.
Recommended Action The system should recover. No action is required. If the message recurs, it may indicate a hardware error related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PQUICC-1-TXERR: [chars]: Fatal transmit error. Restarting...Explanation A fatal transmission error has occurred on the interface, causing the line to be restarted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PQUICC-3-UNDERFLO: Unit [dec], underflow errorExplanation While receiving a frame, the local buffer of the controller chip transmitted insufficient data because the data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required. If the problem recurs, it indicates a hardware error that might be related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PQUICC-1-UNEXPECTED_INTERRUPT: PQUICC([dec]), Unexpected modem-signal interruptExplanation The software has received a modem control signal change that was not expected on this type of WAN interface card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PQUICC-1-UNKNOWN_WIC: PQUICC([dec]), WIC card has an unknown ID of 0x[hex]Explanation The software does not recognize the type of WAN interface card that is plugged into the port module.
Recommended Action Check the part number on the WAN interface card to verify that it is supported in the Cisco IOS software release that is operational on the router, or contact your Cisco technical support representative.
Error Message
%PQUICC-1-UNSUPPORTED_CONFIG: Slot [dec] has an unsupported combination of ISDN WAN interface cardsExplanation It is not possible to support the type of Basic Rate Interface (BRI) card in slot 1 along with another type of BRI card in slot 0.
Recommended Action Remove either one of the BRI cards from its slot.
The following are asynchronous MPC860 quad integrated communications controller error messages.
Error Message
%PQUICC_ASYNC-3-CTSLOST: Unit [dec], Clear to Send LostExplanation The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while sending a frame. This problem is a result of a communication line failure or a cable disconnection.
Recommended Action Check the serial interface cable and the communication equipment, such as the channel service unit/data service unit (CSU/DSU).
The following are Ethernet MPC860 quad integrated communications controller error messages.
Error Message
%PQUICC_ETHER-5-COLL: Unit [dec], excessive collisions. Retry limit [dec] exceededExplanation An Ethernet cable is broken or is not terminated.
Recommended Action Check the cables for proper connections and termination.
Error Message
%PQUICC_ETHER-5-HBEAT: Unit [dec], heartbeat check failureExplanation The Ethernet transceiver is malfunctioning.
Recommended Action Replace the Ethernet transceiver.
Error Message
%PQUICC_ETHER-1-INITFAIL: msgtxt_initfailExplanation 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PQUICC_ETHER-5-LATECOLL: Unit [dec], late collision errorExplanation The Ethernet cable might be too long, or there could be too many repeaters such that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users.
Recommended Action Ensure that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these conditions are not the problem, try removing hosts from the Ethernet segment to reduce the load.
Error Message
%PQUICC_ETHER-1-LOSTCARR: Unit [dec], lost carrier. Transceiver problem?Explanation The Ethernet 10BASE-T cable is unplugged.
Recommended Action Reconnect the 10BASE-T Ethernet cable.
Error Message
%PQUICC_ETHER-1-TXERR: [chars]: Fatal transmit error. Restarting...Explanation A fatal transmission error has occurred on the interface, causing the line to be restarted.
Recommended Action If this message occurs, contact your Cisco technical support representative for assistance.
Error Message
%PQUICC_ETHER-3-UNDERFLO: Unit [dec], underflow errorExplanation While receiving a frame, the local buffer of the controller chip transmitted insufficient data because the data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required. If the problem recurs, it indicates a hardware error that might be related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Fast Ethernet MPC860 quad integrated communications controller error messages.
Error Message
%PQUICC_FE-4-BABBLE: PQUICC/FE([dec]/[dec]), Babble errorExplanation The transmitter has been on the channel longer than the time taken to transmit the largest frame.
Recommended Action The system should recover. No action is required.
Error Message
%PQUICC_FE-5-COLL: PQUICC/FE([dec]/[dec]), Excessive collisions, TDR=[dec], TRC=[dec].Explanation Ethernet or Fast Ethernet interface is seeing multiple collisions. This condition may occur under heavy traffic loads.
Recommended Action The system should recover. No action is required.
Error Message
%PQUICC_FE-1-INITFAIL: PQUICC/FE([dec]/[dec]), Init failed, CSR[dec]=0x[hex]Explanation The software has failed to initialize or restart an Ethernet or Fast Ethernet interface.
Recommended Action Clear the interface. If the message recurs, call your Cisco technical support representative for assistance.
Error Message
%PQUICC_FE-1-INITFAILP: PQUICC/FE([dec]/[dec]), Init failed, CSR[dec]=0x[hex]Explanation The Fast Ethernet Channel (FEC) could not allocate an I/O buffer pool.
Recommended Action Clear the interface. If the message recurs, call your Cisco technical support representative for assistance.
Error Message
%PQUICC_FE-5-LATECOLL: PQUICC/FE([dec]/[dec]), Late collisionExplanation Late collisions have occurred on the Ethernet/Fast Ethernet interface.
Recommended Action If the interface is Fast Ethernet, ensure that both peers are in the same duplex mode. If the interface is Ethernet, the system should recover. No action is required.
Error Message
%PQUICC_FE-5-LOSTCARR: PQUICC/FE([dec]/[dec]), Lost carrier. Transceiver problem?Explanation The cable and the transceiver are not connected.
Recommended Action Reconnect the cable and the transceiver.
Error Message
%PQUICC_FE-1-MEMERR: PQUICC/FE([dec]/[dec]), Memory error, CSR[dec]=0x[hex]Explanation The interface could not access the system resources for a long time. This problem may occur under very heavy traffic conditions.
Recommended Action The system should recover. No action is required. If the message recurs, call your Cisco technical support representative for assistance.
Error Message
%PQUICC_FE-2-NOISL: Interface [chars] does not support ISLExplanation An attempt is being made to configure an interface as an Inter-Switch Link (ISL) trunk, and the interface does not support ISL.
Recommended Action Check the configuration.
Error Message
%PQUICC_FE-3-OVERFLO: PQUICC/FE([dec]/[dec]), Receive overflowExplanation While receiving a frame, the local buffer of the controller chip had transmitted insufficient data because the data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message
%PQUICC_FE-3-OWNERR: PQUICC/FE([dec]/[dec]), Buffer ownership error, pak=0x[hex]Explanation The software has detected an error involving descriptor ownership.
Recommended Action If possible, try using a later version of Cisco IOS software. If the message recurs, call your Cisco technical support representative for assistance.
Error Message
%PQUICC_FE-1-SHOWFAIL: PQUICC/FE([dec]/[dec]), Memory error, CSR[dec]=0x[hex]Explanation The Fast Ethernet Channel (FEC) could not allocate sufficient memory to display the controller.
Recommended Action Clear the interface. If the message recurs, call your Cisco technical support representative for assistance.
Error Message
%PQUICC_FE-3-UNDERFLO: PQUICC/FE([dec]/[dec]), Transmit underflowExplanation While receiving a frame, the local buffer of the controller chip transmitted insufficient data because the data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
The following are serial MPC860 quad integrated communications controller error messages.
Error Message
%PQUICC_SERIAL-3-CTSLOST: Unit [dec], Clear to Send LostExplanation The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface had became inactive while sending a frame. This problem is caused by either a communication line failure or a cable disconnection.
Recommended Action Check the serial interface cable and the communication equipment, such as the channel service unit/data service unit (CSU/DSU).
Error Message
%PQUICC_SERIAL-1-INITFAIL: msgtxt_initfailExplanation The serial interface controller of the MPC860 quad integrated communications controller chip could not be initialized or started for operation. This error usually indicates a hardware problem.
Recommended Action Power-cycle the system. If the error recurs, replace the serial interface controller.
Error Message
%PQUICC_SERIAL-5-LINEFLAP: Unit [dec], excessive modem control changesExplanation The system has received too many modem control signal interrupts. Modem control signals are hardware handshake signals between data terminal equipment (DTE) and data communications equipment (DCE). The signals include either a data carrier detect (DCD) or a data set ready (DSR), or both a DCD and a DSR.
Recommended Action Check the serial interface cable. This error can occur if the cable is disconnected or has come loose and is picking up noise. If the cable appears to be connected correctly, check the equipment that is connected to the cable.
Error Message
%PQUICC_SERIAL-3-UNDERFLO: Unit [dec], underflow errorExplanation While receiving a frame, the local buffer of the controller chip transmitted insufficient data because the data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required. If the problem recurs, it indicates a hardware error that might be related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are power supply error messages.
Error Message
%PS-3-DCOUTPUTVOLTFAIL: System detected Power System [dec] DC FAIL conditionExplanation The power system has experienced a DC failure. One of the DC outputs has failed on the power supply.
Recommended Action identify which DC output has failed. When there is a DC failure, you must replace the power supply.
Error Message
%PS-3-DCOUTPUTVOLTOK: Power System DC condition is now normalExplanation The power system DC is normal.
Recommended Action No action is required.
Error Message
%PS-1-INITSYS: [chars]Explanation An attempt to create the environmental monitor process has failed. The amount of memory available in the router may not be sufficient.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PS-3-INPUTVOLTFAIL: System detected Power System [dec] AC FAIL condition.Explanation The power system experienced an AC failure. One of the DC outputs has failed on the power supply.
Recommended Action Identify which AC input has failed. Ensure that the AC circuit in your building is operational, verify that the power cord is plugged into the power supply, and ensure that the AC power switch to the power supply is on.
Error Message
%PS-3-INPUTVOLTOK: Power System AC condition is now normalExplanation The power system AC is normal.
Recommended Action This is an informational message only. No action is required.
Error Message
%PS-3-MULTFAIL: There is more than one failure with the Power System [dec]; please resolve problems immediatelyExplanation The power system has experienced multiple failures that must be resolved immediately.
Recommended Action Examine the LEDs on the front panel of the power supply to identify and resolve the failures.
Error Message
%PS-3-OVERTEMP_OK: System temperature is now normal.Explanation The system is operating at a normal temperature. The system previously detected a too-high temperature condition that has now cleared. This condition was most likely caused by a high ambient temperature in the area in which the router is located.
Recommended Action No action is required.
Error Message
%PS-3-PSOK: Power System is now normalExplanation The power system is operating normally.
Recommended Action This is an informational message only. No action is required.
Error Message
%PS-3-THERMAL: System detected Power System [dec] THERMAL FAIL condition.Explanation The system has detected a too-high temperature condition that is probably caused by a high ambient temperature in the area in which the router is located.
Recommended Action Ensure that the temperature in the area where the router is normal and resolve any conditions that are causing a temperature increase.
Error Message
%PS-3-THERMOK: Power System THERMAL condition is now normal.Explanation The power system thermal condition is now normal. The power supply previously detected a too-high temperature condition that has now cleared. This condition was most likely caused by a high ambient temperature in the area in which the power supply is located. A power system thermal condition can also be caused by a fan failure in the power supply.
Recommended Action No action is required.
The following are queue and accumulator (QA) error messages.
Error Message
%QA-3-ALLOC: [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 version and show cont cbus commands 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 version and show cont cbus command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%QA-3-DIAG: NULLExplanation This is a diagnostic message.
Recommended Action This message appears after a queue and accumulator (QA) error and contains diagnostic information regarding that error. Copy the original QA error message and all the following QA diagnostic error messages exactly as they appear. Issue the show version and show cont cbus commands to gather additional data that may provide information to determine the nature of the error. Call your Cisco technical support representative and provide the representative with the gathered information.
The following are QEM driver error messages.
Error Message
%QEM-3-DISCOVER: Found [chars] switch processorsExplanation The QEM driver either found no switch processors or found more than one. Exactly one is the only supported configuration.
Recommended Action Ensure that there is only one switch processor.
The following are Qualified Logical Link Control (QLLC) error messages.
Error Message
%QLLC-3-BADOPCODE: Opcode [chars] is invalidExplanation Either remote source-route bridging (RSRB) or local acknowledgment is configured incorrectly.
Recommended Action Verify that RSRB and local acknowledgment are configured correctly.
Error Message
%QLLC-3-BADQLLCSTATE: Bad qllc state - [chars]Explanation An invalid Qualified Logical Link Control (QLLC) primitive was detected.
Recommended Action Ensure that the partner QLLC device is configured correctly.
Error Message
%QLLC-3-BADRSRBOPCODE: Bad opcode [hex] from [sci_notation] to [sci_notation]Explanation Either remote source-route bridging (RSRB) is configured incorrectly or the other RSRB device is down.
Recommended Action Ensure that remote source-route bridging is configured correctly with the correct version of Cisco IOS software.
Error Message
%QLLC-3-BADSTATE: Bad qllc state - [chars] - [sci_notation]Explanation An invalid Qualified Logical Link Control (QLLC) primitive was detected.
Recommended Action Ensure that the Token Ring ports and any participating LAN devices are configured correctly.
Error Message
%QLLC-3-BADSTATEEVENT: Bad qllc state - [chars] event - [chars] macaddr - [sci_notation]Explanation The specified Qualified Logical Link Control (QLLC) primitive has placed the router in an invalid state.
Recommended Action Ensure that the Token Ring ports and any participating LAN devices are configured correctly.
Error Message
%QLLC-3-BAD_XID: Sna configuration error for [sci_notation]: Lan device is PU2.1, X.25 device is PU2.0 (XID Format 1)Explanation The IBM Gateway (3172) or front-end processor on the LAN is sending XID Format 3, which is used to communicate with PU2.1 devices. The X.25 device is a PU2.0 (3174) that is configured to send XID Format 1 messages. This is a very rare situation. A likely cause is that the revision levels on the IBM equipment are incompatible.
Recommended Action Check the revision levels on the external equipment, and upgrade them if necessary.
Error Message
%QLLC-3-DIFFPRTR: [sci_notation] - Different partner - originally [sci_notation] - now [sci_notation]Explanation The partner for this Qualified Logical Link Control (QLLC) virtual MAC address does not match the MAC address that was defined with the qllc partner command.
Recommended Action Ensure that the QLLC partner statement in the configuration file is correct.
Error Message
%QLLC-3-GENERRMSG: [chars]Explanation The text string provided with this error message describes the specific Qualified Logical Link Control (QLLC) problem.
Recommended Action Follow the instructions given with the error message. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%QLLC-3-IFRAME: [chars]Explanation An I-Frame was discarded because of network congestion.
Recommended Action Ensure that the LAN is not beaconing and that it is not in a congested state. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%QLLC-3-INCALL_CFG: Incoming call: No QLLC Service Access Point Configured for x.25 subaddress [chars]Explanation A remote X.25 device that is calling the router for Qualified Logical Link Control (QLLC) service is using a subaddress that was not configured by the X.25 routing facility. The subaddress was not configured for QLLC service.
Recommended Action Correct the QLLC configuration. Configure only the subaddress on the QLLC service, not the complete X.121 address that the remote X.25 device uses.
Error Message
%QLLC-3-INCALL_NO_PARTNER: Incoming call: No partner Mac Address configured - X.25 subaddress [chars]Explanation There is an incoming call, but a connection cannot be initiated to a partner since no partner is configured in a qllc dlsw command (used for Qualified Logical Link Control (QLLC) and DLSw+ only).
Recommended Action To configure a partner for the incoming call, enter the qllc dlsw partner command.
Error Message
%QLLC-3-LNXNOTFOUND: lnx_remove_macaddr_hash did not find target lnxExplanation The qllc srb command is not defined for this interface.
Recommended Action Add a valid qllc srb statement for this serial interface.
Error Message
%QLLC-3-NOLLC2: Unable to open an llc2 sessionExplanation An LLC2 session could not be established with the destination MAC address.
Recommended Action Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN.
Error Message
%QLLC-3-NOMACADDR: No lnx entry for macaddr [sci_notation]Explanation No virtual MAC address was defined for this interface.
Recommended Action Define the virtual MAC address, using either the x25 map qllc or the x25 pvc qllc command.
Error Message
%QLLC-3-NOMEM: Not enough memory availableExplanation There is not enough memory in the system to complete the specified request.
Recommended Action Add more memory to the router. Otherwise, reduce the configuration or the load on the router.
Error Message
%QLLC-3-NONULLXID: Couldn't make null xid - [sci_notation] -[sci_notation]Explanation An attempt to create an IEEE XID has failed.
Recommended Action Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN.
Error Message
%QLLC-3-NOPAKENQ: Pak enqueue failedExplanation A packet was not sent to the LAN.
Recommended Action Ensure that the LAN partner is configured correctly and that the partner is on the desired LAN.
Error Message
%QLLC-4-NOQLLC: Unable to open qllc session, current state is [chars]Explanation A Qualified Logical Link Control (QLLC) session could not be established.
Recommended Action Verify that the qllc partner and the qllc xid commands are correctly entered.
Error Message
%QLLC-3-NOXID2: Couldn't make xid - [sci_notation] -[sci_notation]Explanation The Qualified Logical Link Control (QLLC) XID could not be forwarded to the LAN.
Recommended Action Verify that the qllc partner and the qllc xid commands are correctly entered.
Error Message
%QLLC-3-NO_QLLCBUFFER: M bit Reassembly failed - couldn't allocate a packetExplanation The router has run out of memory and cannot allocate buffers.
Recommended Action Ensure that the router configuration is adequate for the service expected of it. You might want to tune the buffer pools, or upgrade to a larger router. At the very least, you will require more memory.
Error Message
%QLLC-3-NO_QSR: No QLLC Service Access Points definedExplanation No Qualified Logical Link Control (QLLC) services have been configured, even though the router will accept incoming calls for QLLC.
Recommended Action Configure the QLLC service that is required.
Error Message
%QLLC-3-NO_RESOURCE: Incoming Call: Insufficient resources availableExplanation The router cannot accept incoming calls because of insufficient system memory.
Recommended Action Upgrade the system memory.
Error Message
%QLLC-3-NULLPTR: [chars] ptr is nullExplanation The specified structure has not been configured.
Recommended Action Confirm the configuration commands for the structure.
Error Message
%QLLC-3-PARTNER_MISMATCH: Outgoing call: Partner Mac Address [sci_notation] doesn't match configured partner [sci_notation]Explanation A device tried to connect to a Qualified Logical Link Control (QLLC) Virtual MAC (VMAC) from Token Ring, but the MAC address of that device does not match the partner that was specified in the qllc dlsw command.
Recommended Action Correct the QLLC configuration to match the appropriate partner.
Error Message
%QLLC-3-QLLCMAP_ERR: Incoming call: QLLC map entry not foundExplanation A software error in the router code has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are MC68360 quad integrated communications controller error messages.
Error Message
%QUICC-1-NOMEMORY: msgtxt_nomemoryExplanation The MC68360 quad integrated communications controller CPU was unable to access the memory it requires to carry out its functions. Here are some possible causes:
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%QUICC-3-OWNERR: msgtxt_ownerrorExplanation An internal software error has occurred.
Recommended Action Call your Cisco technical support representative to obtain a Cisco IOS software upgrade.
Error Message
%QUICC-3-UCODE_REV_UNKN: Unknown microcode revision number: [dec]Explanation The MC68360 quad integrated communications controller CPU was running an unexpected version of microcode. This situation could occur if a new version of the MC68360 quad integrated communications controller chip were released or if a very old version were used in the manufacturing process of that chip. This situation could also occur if a new version of microcode were released to fix any bugs.
Recommended Action A decrease in performance might occur if there any asynchronous interfaces running PPP. Call your Cisco technical support representative if this is an issue.
The following are asynchronous MC68360 quad integrated communications controller error messages.
Error Message
%QUICC_ASYNC-3-CTSLOST: Unit [dec], Clear to Send LostExplanation The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while sending a frame. This problem is caused by either a communication line failure or a cable disconnection.
Recommended Action Check the serial interface cable and the communication equipment such as the channel service unit/data service unit (CSU/DSU).
The following are Ethernet MC68360 quad integrated communications controller error messages.
Error Message
%QUICC_ETHER-5-COLL: Unit [dec], excessive collisions. Retry limit [dec] exceededExplanation An Ethernet cable is broken or is not terminated.
Recommended Action Check the cables for proper connections and termination.
Error Message
%QUICC_ETHER-5-HBEAT: Unit [dec], heartbeat check failureExplanation The Ethernet cable might be too long, or there could be too many repeaters with the result that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users.
Recommended Action Verify that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these conditions are not the problem, try removing hosts from the Ethernet segment to reduce the load.
Error Message
%QUICC_ETHER-5-LATECOLL: Unit [dec], late collision errorExplanation The Ethernet cable might be too long, or there could be too many repeaters with the result that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users.
Recommended Action Verify that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these conditions are not the problem, try removing hosts from the Ethernet segment to reduce the load.
Error Message
%QUICC_ETHER-1-INITFAIL: msgtxt_initfailExplanation 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%QUICC_ETHER-1-LOSTCARR: Unit [dec], lost carrier. Transceiver problem?Explanation The Ethernet 10BASE-T cable is unplugged.
Recommended Action Reconnect the 10BASE-T Ethernet cable.
Error Message
%QUICC_ETHER-3-UNDERFLO: Unit [dec], underflow errorExplanation While receiving a frame, the local buffer of the controller chip transmitted insufficient data because the data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required. If the problem recurs, it indicates a hardware error that might be related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are serial MC68360 quad integrated communications controller error messages.
Error Message
%QUICC_SERIAL-3-CTSLOST: Unit [dec], Clear to Send LostExplanation The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while transmitting a frame. This problem is a result of a communication line failure or cable disconnection.
Recommended Action Check the serial interface cable and communications equipment such as the channel service unit/data service unit (CSU/DSU).
Error Message
%QUICC_SERIAL-1-INITFAIL: msgtxt_initfailExplanation The serial interface controller of the QUICC chip could not be initialized or started for operation. This error probably indicates a hardware problem.
Recommended Action Power-cycle the system. If the error recurs, replace the unit.
Error Message
%QUICC_SERIAL-5-LINEFLAP: Unit [dec], excessive modem control changesExplanation The system has received too many modem control signal interrupts. Modem control signals are hardware handshake signals between data terminal equipment (DTE) and data communications equipment (DCE). The signals include either a data carrier detect (DCD) or a data set ready (DSR), or both a DCD and a DSR.
Recommended Action Check the serial interface cable. This error can occur if the cable is disconnected or has come loose and is picking up noise. If the cable appears to be connected correctly, check the equipment that is connected to the cable.
Error Message
%QUICC_SERIAL-5-LOSTCARR: Unit [dec], carrier detect signal lost during message receptionExplanation The RS-232C Carrier Detect (DCD) signal was deasserted during message reception. The DCE equipment is responsible for asserting this signal. This error can occur if the serial interface cable is disconnected.
Recommended Action Ensure that the serial interface cable is connected.
Error Message
%QUICC_SERIAL-3-UNDERFLO: Unit [dec], underflow errorExplanation While receiving a frame, the local buffer of the controller chip transmitted insufficient data because the data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required. If the problem recurs, it indicates a hardware error that might be related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are RADIUS error messages.
Error Message
%RADIUS-3-ALLDEADSERVER: No active radius servers found. Id [dec]Explanation All RADIUS servers were found to be unresponsive.
Recommended Action Check the network connectivity to the RADIUS servers, and ensure that the servers are running.
Error Message
%RADIUS-3-FORKFAIL: Failed to fork process for [chars]Explanation The system probably ran out of memory. Other explanations are possible.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RADIUS-6-GETPOOLS: Retrieving IP-Pools via user [chars]Explanation Initial IP-Pool definitions are being retrieved from RADIUS using the profile of the specified user.
Recommended Action No action is required.
Error Message
%RADIUS-6-GETROUTES: Retrieving static routes in user [chars]Explanation Initial static routes are being retrieved from RADIUS using the profile of the specified user.
Recommended Action No action is required.
Error Message
%RADIUS-3-IDENTFAIL: Save of unique accounting ident aborted. Configuration has been modifiedExplanation Since the configuration has been modified, the user cannot save the unique accounting ident to NVRAM.
Recommended Action Save the configuration and try again. If the error persists, call your Cisco technical support representative for assistance.
Error Message
%RADIUS-6-IDENTSAVE: Saving config with new acct ident in nvramExplanation An accounting ident is being saved in NVRAM.
Recommended Action No action is required.
Error Message
%RADIUS-3-NOHOSTNAME: Failed to retrieve my hostnameExplanation An attempt to find the host name of the router has failed. A host name must be defined, because it determines the RADIUS profile to be retrieved.
Recommended Action Define a host name in the configuration of the router.
Error Message
%RADIUS-4-NOSERV: Warning: Server [int]:[dec],[dec] is not definedExplanation The specified server is not on the master list. It should be defined, or unexpected events may happen.
Recommended Action Define the server on the appropriate master list as soon as possible.
Error Message
%RADIUS-3-NOSERVERS: No Radius hosts configuredExplanation Radius is attempting to send a request to a host, but there are no hosts configured.
Recommended Action To configure a host, use the RADIUS-server command.
Error Message
%RADIUS-3-OVERRUN: Insufficient buffer space [dec] for string valueExplanation An internal software error has occurred.
Recommended Action Contact your Cisco technical support representative for assistance.
Error Message
%RADIUS-3-PICKERR: Internal pick-server error: [chars]Explanation Radius has encountered an internal consistency error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RADIUS-3-SECRETLENMAX: Secret exceeded max lengthExplanation The user is attempting to store a per-server secret that exceeds the maximum length of 65 characters.
Recommended Action Configure a shorter secret.
Error Message
%RADIUS-6-SERVERALIVE: Radius server [int]:[dec],[dec] is responding again (previously dead)Explanation A RADIUS server that was previously inactive has started responding again.
Recommended Action No action is required.
Error Message
%RADIUS-4-SERVREF: Warning: Server [int]:[dec],[dec] is still referenced by server groupExplanation The server that is being removed is still referenced by a server group.
Recommended Action Dereference the server from the server group as soon as possible.
The following are radix error messages.
Error Message
%RADIX-3-ADDMASK: Error adding mask entry, [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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RADIX-3-BADTREE: Invalid pointer to head of tree, 0x[hex]Explanation A software programming error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RADIX-3-DELETE: Error deleting trie entry, [chars]Explanation A software programming error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RADIX-2-INIT: No memory for radix initialization: [chars]Explanation The system ran out of memory during initialization. This error should only occur if an image is too large for the existing dynamic memory.
Recommended Action Use a smaller subset image or upgrade hardware.
Error Message
%RADIX-3-NOMEMORY: No memory available [chars]Explanation The system is out of memory.
Recommended Action To correct the problem, reduce the number of routes accepted by this router, upgrade the hardware, or use a smaller subset image on the run-from-RAM platforms.
Error Message
%RADIX-4-ORPHAN: Orphaned mask [hex], refcount=[dec] at [hex], next=[hex]Explanation A software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are remote command error messages.
Error Message
%RCMD-4-RCMDDNSFAIL: DNS hostname/ip address mismatch. [int] unknown to DNSExplanation The IP address for an incoming remote command request is not registered with Domain Name System (DNS).
Recommended Action Add the IP address to DNS.
Error Message
%RCMD-4-RCPATTEMPTED: Remote copy from [chars] at [chars] deniedExplanation An attempt was made to connect to a router through remote copy protocol (RCP), but the router was not configured as an RCP server.
Recommended Action Configure an RCP server.
Error Message
%RCMD-4-RSHATTEMPTED: Remote shell from [chars] at [chars] deniedExplanation An attempt was made to connect to a router through remote shell (rsh) protocol, but the router was not configured as an rsh server.
Recommended Action Configure an rsh server.
Error Message
%RCMD-4-RSHPORTATTEMPT: Attempted to connect to RSHELL from [int]Explanation An attempt was made to connect to a router through the rshell port (514), but the router was not configured as a remote shell protocol (rsh) or remote copy (RCP) protocol server.
Recommended Action Configure an rsh or RCP server.
The following are Cisco optical regenerator error messages.
Error Message
%Regen-3-BADADDR: regen_little_endian_addr: Attempted conversion of invalid address (0x[hex])Explanation A software error has occurred while attempting to determine protocol control information (PCI) device addressing. This condition is most likely to occur because of a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%Regen-3-BADADDR2: regen_big_endian_addr: Attempted conversion of invalid address (0x[hex])Explanation A software error has occurred while attempting to determine protocol control information (PCI) device addressing. This condition is most likely to occur because of a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%Regen-3-BADBAYDEV: get_pci_dev_num: Invalid bay ([dec]) or device number offset (%D)Explanation A software error has occurred while attempting to determine protocol control information (PCI) device addressing. This condition is most likely to occur because of a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%Regen-3-BADDEVNO: pas_get_device_subunit: Invalid PCI device number: [dec]Explanation A software error has occurred while attempting to determine protocol control information (PCI) device addressing. This condition is most likely to occur because of a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%Regen-3-BADNV: Detected invalid NVRAM size: [dec] bytesExplanation The system has detected that the NVRAM is not one of the supported sizes. The NVRAM might be bad.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%Regen-3-BADPA: Invalid Port Adaptor type ([dec]) reported for mainboardExplanation The virtual port adapter type that is derived from the main board is not one of the supported types. The main board might be a new main board type, and the software release you are running does not support the new main board type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%Regen-3-BADPCIRD: PCI Configuration Read Cycle Failed for bus [dec], Device [dec], function [dec], register [dec]Explanation A protocol control information (PCI) bus configuration read cycle has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%Regen-3-BADPCIWR: PCI Configuration Write Cycle Failed for bus [dec], Device [dec], function [dec], register [dec]Explanation A protocol control information (PCI) bus configuration write cycle failed.
Recommended Action The main board must be replaced. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%Regen-3-NOMAC: Can't allocate MAC address for interface [int]/[int]Explanation All the available Media Access Control (MAC) addresses for the system have been allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%Regen-3-NVERASEFAIL: Failed to erase config due to internal errorExplanation The password protection feature has failed to erase the configuration because of an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%Regen-1-OVERTEMP: System detected OVERTEMPERATURE condition. Putting the system in Power save mode and going to common. Please resolve cooling problem and restart system!Explanation The environmental monitor has detected a high-temperature condition.
Recommended Action Ensure that the room temperature is not too high and that the air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following Cisco optical regenerator error messages relate to the Asynchronous MPC860 quad integrated communications controller.
Error Message
%Regen_MAINBOARD_ASYNC_PQUICC-3-NOMEMORY: No memory for [chars] of unit [dec]Explanation The router does not have enough memory to perform the function.
Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are resource monitor subsystem error messages.
Error Message
%RESOURCE_MON-1-INITSYS: [chars]Explanation This error indicates an initialization failure. The specific message text is supplied by the Resource Monitor software. When this error occurs, the Resource Monitor subsystem is not operational.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RESOURCE_MON-1-RSCMON_BAD_DATA: [chars]Explanation This error indicates that internal data was corrupted because of a software error. The specific message text is supplied by the Resource Monitor software.
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
%RESOURCE_MON-1-RSCMON_CLIENT_Q: [chars]Explanation This error indicates a memory exhaustion condition. The specific message text is supplied by the Resource Monitor software.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Posted: Fri Jun 16 11:51:53 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.