|
|
The following are maintenance bus (MBus) system error messages.
Error Message
%MBUS_SYS-3-ENQUEUE: Failed to queue message from slot [dec] stream [dec]Explanation An attempt to queue a message from the interrupt for process-level software has failed. The message will be dropped. The dropped message indicates a potential problem in the maintenance bus (MBus) process-level message handling. This error can occur if there are problems specifically with the MBus process or general Cisco IOS process-related issues. This error may also happen if the MBus process is not scheduled for extended periods of time and there is heavy MBus traffic.
Recommended Action If this is a persistent problem, either the MBus process is dead or there are other Cisco IOS-related problems. Consider rebooting the gigabit route processor (GRP) if possible.
Error Message
%MBUS_SYS-3-MAXSIZE: Message from slot [dec] stream [dec] of length [dec] > max message size [dec]Explanation A message from a slot has exceeded the maximum message size of 254 bytes and therefore will be dropped. This error should not happen during normal operations.
Recommended Action To verify the functionality of maintenance bus (MBus) use the show mbus counters and the show mbus can-error commands. If any particular card shows errors and this condition persists, try reloading the card if possible. The error counts in the show mbus commands can be cleared using the clear mbus-statistics command.
Error Message
%MBUS_SYS-3-MSGINVCHN: MBUS invalid channel selected (dev=[int],type=[int],channel=[dec],len=[int])Explanation The software tried to send a message on a invalid maintenance bus (MBus) channel.
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
%MBUS_SYS-3-MSGTOOBIG: MBUS message length too big (dev=[int],type=[int],len=[int])Explanation The software tried to send a message with a length greater than the maximum message size of 254 bytes.
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
%MBUS_SYS-3-NOBUFFER: Message from slot [dec] in stream [dec] droppedExplanation A message from the slot was dropped because there was no maintenance bus (MBus) buffer available. Either the messages are coming too fast or the process-level message handling is not processing the messages quickly enough.
Recommended Action This condition should correct itself. Check if the gigabit route processor (GRP) is being inundated by messages from the chassis. If the condition persists, consider rebooting the GRP.
Error Message
%MBUS_SYS-3-NOCHANNEL: Failed to allocate MBUS channel for over 10 secsExplanation No maintenance bus (MBus) channel could be allocated for sending messages. Either there is very heavy MBus traffic or there is a hardware problem. If there is temporary heavy traffic, the condition will clear itself. In case of hardware errors either the MBus agent has died or the hardware interface to the mailbox is not processing the messages. Resetting the processor, including the agent, may clear the problem. If the problem persists, the card probably has hardware problems and requires diagnosis.
Recommended Action Power cycle the card. If the problem persists, the card may be defective and should be replaced.
Error Message
%MBUS_SYS-3-REASSEMBLY: Error slot [dec], stream [dec] [chars]Explanation A reassembly error was detected for the given slot and stream combination. Either the slot and stream combination was incorrect (so it gave an invalid reassembly buffer index) or the first and last, or last few, packets were lost. The message will be dropped and may cause errors for the application running over the maintenance bus (MBus).
Recommended Action This condition should correct itself. No action is required.
Error Message
%MBUS_SYS-0-REGISTRY: Failed to create registry [chars][chars]Explanation The specified registry could not be created. The inability to create the registry is a catastrophic error for this feature. This condition requires a developer's intervention for a solution.
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
%MBUS_SYS-3-SEQUENCE: Sequencing error (slot [dec], stream [dec]): expected [dec], received [dec]Explanation An incorrect sequence number was detected in a multi-packet message. This error could occur if the source packetized the message incorrectly (unlikely) or if one or more packets were dropped.
Recommended Action Check if there is excessive maintenance bus (MBus) activity, such as copious printing from a line card. To determine the lost message count, use the show mbus counters command.
Error Message
%MBUS_SYS-3-TIMEOUT: Timeout on mbus request. Dest = [int], type = [int], addr = 0x[hex]Explanation No response was received from a maintenance bus (MBus) request. This request was either for an EEPROM field or a register read.
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
%MBUS_SYS-3-TXERR: Failed to transmit MBUS message for over 10 secsExplanation Message could not be transmitted since all the transmit buffers had been full for over 10 seconds. This may be a temporary problem if there is heavy maintenance bus (MBus) traffic. Otherwise, this error probably indicates a hardware problem. Either the MBus agent is not responding or the hardware interface is not generating interrupts.
Recommended Action If this is a persistent problem power cycle the card. If the problem still continues it is likely to be a hardware problem that requires diagnosis.
Error Message
%MBUS_SYS-3-UNEXPECTED: Unexpected response key = [int], current key = [int]Explanation An unexpected response to a read register or to a read EEPROM was received.
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 memory scan error messages.
Error Message
%MEMSCAN-2-BSSREG: Parity error(0x[hex]) found in imagebss regionExplanation A parity error was found in the BSS region of the memory.
Recommended Action Schedule a reboot of the system to clear the memory as soon as possible. An attempt to remove the parity error during the normal operation of the router will cause it to reload. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.
Error Message
%MEMSCAN-2-DATAREG: Parity error(0x[hex]) found in imagedata regionExplanation A parity error was found in the data region of the memory.
Recommended Action Schedule a reboot of the system to clear the memory as soon as possible. An attempt to remove the parity error during the normal operation of the router will cause it to reload. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.
Error Message
%MEMSCAN-3-DUPERR: Another parity error(0x[hex]) found in bolck(0x[hex]). Not scrubedExplanation Multiple parity errors have been found in a memory block.
Recommended Action Schedule a reboot of the system to clear the memory as soon as possible. An attempt to remove the parity error during the normal operation of the router will cause it to reload. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.
Error Message
%MEMSCAN-3-INHEAD: Parity error(0x[hex]) found in block headerExplanation A parity error has been found in the block header.
Recommended Action Schedule a reboot of the system to clear the memory as soon as possible. An attempt to remove the parity error during the normal operation of the router will cause it to reload. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.
Error Message
%MEMSCAN-3-INPREV: Parity error(0x[hex]) found in block field **previousExplanation A parity error has been found in a critical field of a block header.
Recommended Action Schedule a reboot of the system to clear the memory as soon as possible. An attempt to remove the parity error during the normal operation of the router will cause it to reload. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.
Error Message
%MEMSCAN-3-INUSE: Parity error(0x[hex]) found in busy bolck(0x[hex])Explanation A parity error has been found in a busy block that cannot be scrubbed or removed.
Recommended Action Schedule a reboot of the system to clear the memory as soon as possible. An attempt to remove the parity error during the normal operation of the router will cause it to reload. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.
Error Message
%MEMSCAN-6-LINKED: Error(0x[hex]) block(0x[hex]) linked, size [dec]Explanation A parity error was found in a free block that could not be scrubbed. The free block has been moved to a dead list so that it cannot be accessed again.
Recommended Action Schedule a reboot of the system to clear the memory as soon as possible. An attempt to remove the parity error during the normal operation of the router will cause it to reload. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.
Error Message
%MEMSCAN-6-MSCRUBED: Parity error(0x[hex]) scrubed multiple timesExplanation Multiple parity errors were found at the specified address.
Recommended Action Schedule a reboot of the system to clear the memory as soon as possible. An attempt to remove the parity error during the normal operation of the router will cause it to reload. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.
Error Message
%MEMSCAN-6-SCRUBED: Parity error(0x[hex]) scrubedExplanation One or more parity errors were found and scrubbed.
Recommended Action No action is required.
Error Message
%MEMSCAN-6-SPLIT: Error(0x[hex]) block(0x[hex]) split, bad block(0x[hex]) linked, size 0x[hex]Explanation A parity error was found in a free block that could not be scrubbed. The free block has been fragmented, and the fragment that contains the parity error has been moved to a dead list so that it cannot be used again.
Recommended Action Schedule a reboot of the system to clear the memory as soon as possible. An attempt to remove the parity error during the normal operation of the router will cause it to reload. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.
Error Message
%MEMSCAN-2-TEXTREG: Parity error(0x[hex]) found in imagetext regionExplanation A parity error was found in the text region of memory.
Recommended Action Schedule a reboot of the system to clear the memory as soon as possible. An attempt to remove the parity error during the normal operation of the router will cause it to reload. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.
Error Message
%MEMSCAN-3-UNKNOWN: Parity error(0x[hex]) found in other(unknown) regionExplanation A parity error was found in an unknown region of the memory.
Recommended Action Schedule a reboot of the system to clear the memory as soon as possible. An attempt to remove the parity error during the normal operation of the router will cause it to reload. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.
The following are Modem ISDN channel aggregation (MICA) modem error messages.
Error Message
%MICA-3-BADIMAGE: Cannot download version [chars] on module [dec]Explanation The block information that is necessary for downloading modem firmware is missing for the indicated firmware version.
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
%MICA-3-BADMODEM: Modem [dec] went badExplanation Run-time checks for modem health have determined that the indicated modem is no longer functional. The loss of functionality was caused by a hardware or 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
%MICA-3-BADMODULE: Module in socket [dec] is of unknown type (board-id=[dec])Explanation The modem module in the socket indicated by the message is invalid, possibly because the serial EEPROM on the module was not programmed correctly.
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
%MICA-3-BADPARAM: Modem [dec]: [chars] while handling [chars].Explanation The modem state machine has received a bad parameter, as indicated by the error 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
%MICA-3-BADRXOPCODE: Bad mail message opcode from modem [dec]: opcode = 0x[hex]Explanation A message with an illegal operation code was received from the specified modem.
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
%MICA-3-BADTXOPCODE: Bad tx mail message opcode = 0x[hex]Explanation An attempt has been made to send a message with an illegal operation code to the specified modem.
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
%MICA-3-CONTIGUOUS: Contiguous packet sent for transmitExplanation A software error has occurred. As a result, an unexpected packet was prepared for transmission and dropped.
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
%MICA-3-CRASH: Runtime error on MICA module [dec]Explanation A software error that involves the modem firmware running on the specified modem module 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
%MICA-6-INIT: Modem module [dec] initializedExplanation The indicated modem module was successfully initialized.
Recommended Action No action is required.
Error Message
%MICA-3-INVALID_PARAM: Mica sent invalid stack address or length, MICA module [dec], addr 0x[hex], length [dec]Explanation A run-time error has occurred on the Modem ISDN channel aggregation (MICA), causing it to send an invalid stack address or length.
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
%MICA-3-NAK: NAK from modem [dec] in state [dec] -- payload 0x[hex]Explanation A message sent to the specified modem was rejected.
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
%MICA-3-NOENTRIES: Exhausted [chars] DMA entries for module [dec]Explanation The software structures that are used to drive the direct memory access (DMA) engines were temporarily exhausted while attempting the task specified in the error message. As a result of this error, the task was aborted.
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
%MICA-3-NOIDB: No IDB structure for modem [dec]Explanation A software structure was found in an unexpected state during the run time for the specified modem.
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
%MICA-3-NOMAILELEMENTS: Exhausted free mail elements for modem_num [dec]Explanation The software structures that are used to receive and transmit messages from the Modem ISDN channel aggregation (MICA) modems were temporarily exhausted.
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
%MICA-3-NOPPPCTX: No PPP context structure for modem [dec]Explanation A software structure was found in an unexpected state during the run time for the specified modem.
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
%MICA-3-NORXPAK: Static receive paktype unavailableExplanation A software structure was found in an unexpected state during the run time for the specified modem.
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
%MICA-3-NOTPLX: Bad vendor id from PLX 9060SD -- value was 0x[hex]Explanation A hardware error involving the protocol control information (PCI) interface chip 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
%MICA-3-NOTTY: No TTY structure for modem [dec]Explanation A software structure was found in an unexpected state during the run time for the indicated modem.
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
%MICA-3-PORTWARE: Bad version [chars] portware: [chars]Explanation Verification tests could not confirm the firmware image for the specified version of modem firmware that is bundled into the modem card image.
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
%MICA-3-PWDNLDTO: Portware download timed out for module [dec]Explanation The diagnostic message that is expected back from a Modem ISDN channel aggregation (MICA) modem after a successful download and initialization of the modem firmware, was not received within the allotted 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
%MICA-3-RESTART: Attempting restart of modem module [dec]Explanation The specified modem module had a run-time error and therefore was reset. An attempt is now being made to restart the modem module.
Recommended Action No action is required.
Error Message
%MICA-3-TXDESCLIMIT: Packet descriptor count ([dec]) exceeds transmit ring sizeExplanation The packet to be sent required more descriptors than were available on the transmit ring, and the packet was dropped.
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
%MICA-3-WRONGMODULE: Module in socket [dec] (board-id=[dec]) is [chars] module; card is not [chars] cardExplanation The modem module in the specified socket is inappropriate for the modem card on which it is installed.
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.
The following are PCI MC68840 FDDI port adapter error messages.
Error Message
%MIF68840-1-DISCOVER: Only found [dec] interfaces on bay [dec], shutting down bayExplanation The number of interfaces found was not what was expected. This error may indicate a hardware failure.
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
%MIF68840-3-NOTMIF68840: Bay [dec] device ID seen as [hex], expected [hex]Explanation The FDDI driver has failed to initialize.
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
%MIF68840-5-NOTSUPPORTED: '[chars]' command on [chars]Explanation The requested device or port is not supported as a FDDI interface
Recommended Action No action is required.
Error Message
%MIF68840-3-OWNERR: [chars] packet buffer, pak=0x[hex]Explanation This error indicates an internal software inconsistency.
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.
The following are MCOM integrated modem network module error messages.
Error Message
%MIMIC-3-CONFIGFAIL: The MCOM integrated modem network module in slot [dec] failed to configure. [chars]Explanation The MCOM integrated modem network module hardware may be defective.
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
%MIMIC-3-CONTROLLERFAIL: The MCOM integrated modem network module controller in slot [dec] [chars]Explanation The MCOM integrated modem network module hardware may be defective.
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
%MIMIC-3-DISCOVER: The MCOM integrated modem network module in slot [dec] failed to initialize properlyExplanation The MCOM integrated modem network module hardware may be defective.
Recommended Action Power down, reinsert the network module, and reboot 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.
Error Message
%MIMIC-3-DOWNLOAD_ERR: The [chars] firmware download for the network module in slot [dec] failedExplanation The MCOM integrated modem network module hardware may be defective.
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
%MIMIC-3-INVALID_PCI_ID: The network module hardware reports an invalid [chars] device id of [hex]Explanation The MCOM integrated modem network module hardware may be defective.
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
%MIMIC-3-MODEM_RESET_ERR: The modem in slot [dec] port [dec] failed to reset (status = 0x[hex])Explanation The MCOM integrated modem network module hardware may be defective.
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
%MIMIC-3-NOMEMORY: No memory for [chars] of unit [dec]Explanation The router does not have enough memory to perform the specified function.
Recommended Action Ensure that there is sufficient memory available in the 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
%MIMIC-3-SPECIALCDINUSE: Unable to reset MCOM integrated modem [dec]/[dec]Explanation A critical error has occurred and the device driver has unsuccessfully attempted to reset the modem.
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
%MIMIC-4-UNKNOWNPLATFORM: The MCOM integrated modem subsystem is not compatible with this routerExplanation The network module is not compatible with the current platform into which it is plugged.
Recommended Action Power down, remove the network module, and reboot the system.
The following are MK5025 serial controller error messages.
Error Message
%MK5-1-BADRING: msgtxt_badringsizeExplanation 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
%MK5-1-INITFAIL: msgtxt_initfailExplanation The hardware has failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message
%MK5-1-INITNOPPRIM: Unit [dec], initialization failure - No CSR1_PPRIM_INIT_CONF, csr1 = 0x[hex]Explanation The hardware has failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message
%MK5-1-INITUERR: Unit [dec], initialization CSR1_UERR failure, csr1=0x[hex]Explanation The hardware has failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message
%MK5-5-LINEFLAP: Unit [dec] excessive modem control changesExplanation Too many modem control interrupts have been received. The port was disabled to prevent excessive use of the CPU.
Recommended Action Check the cable on the serial port.
Error Message
%MK5-1-MEMERR: msgtxt_memoryerrorExplanation A network serial interface has detected a hardware problem.
Recommended Action Repair or replace the controller.
Error Message
%MK5-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
%MK5-3-OUTENCAP: Unit [dec], bad output packet encapsulation: 0x[hex]Explanation An internal software error has occurred.
Recommended Action If either of these messages recur, call your Cisco technical support representative for assistance.
Error Message
%MK5-3-PLOSTERR: Unit [dec], provider primitive lost, csr0=0x[hex], csr1=0x[hex]Explanation A network serial interface detected a hardware problem.
Recommended Action Repair or replace the controller.
Error Message
%MK5-3-PPRIMERR: Unit [dec], unexpected provider primitive, csr0=0x[hex], csr1=0x[hex]Explanation A network serial interface has detected a hardware problem.
Recommended Action Repair or replace the controller.
Error Message
%MK5-3-SPURPPRIMERR: Unit [dec], spurious provider primitive interrupt, csr0=0x[hex], csr1=0x[hex]Explanation A network serial interface has detected a hardware problem.
Recommended Action Repair or replace the controller.
Error Message
%MK5-3-UPRIMERR: Unit [dec], user primitive error, csr0=0x[hex], csr1=0x[hex]Explanation A network serial interface has detected a hardware problem.
Recommended Action Repair or replace the controller.
The following are integrated modem network module error messages.
Error Message
%MMODEM-3-HWFAIL: Cannot determine hardware version for integrated modem Network Module in slot [dec]Explanation The integrated modem network module hardware may be defective.
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
%MMODEM-3-IMAGEBAD: Integrated modem image file [chars] cannot be loadedExplanation The integrated modem override file does not contain valid images.
Recommended Action The integrated modem network module will be loaded with the default software images. 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
%MMODEM-3-IMAGEHWINCOMPATMAX: Integrated modem image file [chars] cannot be loaded because it requires a minimum integrated modem Network Module hardware version between [hex] and [hex], inclusiveExplanation The integrated modem override file is not compatible with the existing version of integrated modem hardware. This override file can be used only with specified network module hardware versions. The integrated modem network module will be loaded with the default software images.
Recommended Action No action is required.
Error Message
%MMODEM-3-IMAGEHWINCOMPATNOMAX: Integrated modem image file [chars] cannot be loaded because it requires a minimum integrated modem Network Module hardware version of [hex]Explanation The integrated modem override file is not compatible with the version of integrated modem hardware. This override file can be used only with specified network module hardware versions. The integrated modem network module will be loaded with the default software images.
Recommended Action No action is required.
Error Message
%MMODEM-3-IMAGEIOSINCOMPATMAX: Integrated modem image file [chars] cannot be loaded because it requires an IOS version between [dec].[dec]([dec].[dec]) and [dec].[dec]([dec].[dec]), inclusiveExplanation The integrated modem override file is not compatible with the version of Cisco IOS software running on this router. This override file can be used only with the specified versions of Cisco IOS software. The integrated modem network module will be loaded with the default software images.
Recommended Action No action is required.
Error Message
%MMODEM-3-IMAGEIOSINCOMPATNOMAX: Integrated modem image file [chars] cannot be loaded because it requires an IOS version of [dec].[dec]([dec].[dec]) or laterExplanation The integrated modem override file is not compatible with the version of Cisco IOS software running on this router. The integrated modem network module will be loaded with the default software images.
Recommended Action If you wish to use this modem override image file, you must upgrade to the specified version of Cisco IOS software.
Error Message
%MMODEM-3-IMAGEWRONGTYPE: Integrated modem image file [chars] cannot be loadedExplanation The integrated modem override file does not contain valid firmware images. The integrated modem network module will be loaded with the default software images.
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 router shelf modem management error messages.
Error Message
%MODEM-4-B2BABORT: Modems ([chars]) and ([chars]) back-to-back test: abortedExplanation This tracing message indicates that a back-to-back test has failed between the two specified Modem ISDN channel aggregation (MICA) modems.
Recommended Action Perform more back-to-back tests by pairing the failed modems with other modems to determine which modem is defective. Check the failed modems again after performing a power cycle. 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
%MODEM-5-B2BCONNECT: Modems ([chars]) and ([chars]) connected in back-to-back test: [chars]Explanation A back-to-back test connection has been made between the selected modems. The test is still in progress.
Recommended Action No action is required.
Error Message
%MODEM-5-B2BINIT: Auto Back-to-Back test initiated by [chars]Explanation This tracing message indicates that an automatic back-to-back test has been initiated by the specified Modem ISDN channel aggregation (MICA) modem.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM-5-B2BMODEMS: Modems ([chars]) and ([chars]) completed back-to-back test: success/packets = [dec]/[dec]Explanation The reported modems have passed the back-to-back test without any errors.
Recommended Action No action is required.
Error Message
%MODEM-1-BADEVENT: Invalid modem management [chars] event 0x[hex] for modem([chars])Explanation The modem management facility received an unrecognized event.
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
%MODEM-1-BADMODEM: Modem ([chars]) failed [chars]Explanation A software or hardware problem has been detected on a modem. The specific modem and reason are listed in the 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
%MODEM-4-BADMODEMS: Modems ([chars]) and ([chars]) failed back-to-back test: [chars]Explanation The two modems reported in the message have failed a back-to-back test. At least one of the modems is defective.
Recommended Action Perform more back-to-back tests by pairing the failed modems with other modems to determine which modem is defective. Check the failed modems again after performing a power cycle. 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
%MODEM-5-CONFIG: Configurations fast-answer and country [chars] conflict.Explanation The fast-answer configuration conflicts with the country setting. The country setting has been given priority and the fast-answer setting has been disabled.
Recommended Action No action is required.
Error Message
%MODEM-1-DL_FAIL: Firmware download failed for slot [dec] module_mask [hex]Explanation The modem modules did not send back an "initialized" message after the download.
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
%MODEM-1-DL_FAIL_FILE_XFER: Firmware download failed for slot [dec] module_mask 0x[hex] due to file transfer errorExplanation The download of a portware file to the modem card over Dial Shelf Interconnect Protocol (DSIP) as part of a modem firmware upgrade attempt has timed out and has failed to complete successfully.
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
%MODEM-5-DL_GOOD: Modem ([chars]) completed firmware download: [chars]Explanation The specified modem has succeeded in downloading its internal microcode.
Recommended Action No action is required.
Error Message
%MODEM-1-DL_LOSS_FAIL: Firmware download failure for slot [dec] module [dec]Explanation The portware download for the module was previously deferred. A later portware download attempt has failed because the information required for the download was 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
%MODEM-1-DL_PROC_FAIL: Portware download process creation failedExplanation A portware download process creation 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
%MODEM-5-DL_START: Modem ([chars]) started firmware downloadExplanation The specified modem has begun downloading its internal microcode.
Recommended Action No action is required.
Error Message
%MODEM-5-MODEM_OK: Modem ([chars]) passed the testExplanation Tests on the specified modem were successful.
Recommended Action No action is required.
Error Message
%MODEM-5-MODEM_RECOVERY_DL: Slot [dec], Module [dec]: [chars]Explanation This message provides module download information.
Recommended Action No action is required.
Error Message
%MODEM-5-MODEM_RECOVERY_PROCESS: [chars]Explanation This message provides modem recovery process information.
Recommended Action No action is required.
Error Message
%MODEM-3-MODEMSTART_OUTOFMEM: Error -- Unable to allocate memory to startup modem board in slot [dec]Explanation A memory shortage has prevented a modem board startup process from completing.
Recommended Action Issue the show memory command and copy the command output that reports the amount of processor and I/O memory usage. Provide this information, along with the output from the show version command, to your Cisco technical support representative.
Error Message
%MODEM-4-NO_TIME_FOR_DC: Warning -- Not enough time to process DC sessionExplanation The DC (direct-connect) session did not have enough time to complete.
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
%MODEM-3-PWDNLDPROC: Portware download manager process start-up failedExplanation The attempt to start up the portware download manager process at initialization time has failed. As a result, portware download requests cannot be processed.
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
%MODEM-3-UNEXPECTED_STATUS_EV: Error -- status state machine received unexpected event=[dec] for modem([chars])Explanation The status-polling state machine of the modem management subsystem has received an undefined event for or from the specified modem.
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
%MODEM-3-UNEXPECTED_STATUS_STATE: Error -- status state machine in unknown state=[dec] for modem([chars])Explanation The status-polling state machine of the modem management subsystem for the specified modem has entered an undefined 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 router shelf modem history and tracing error messages.
Error Message
%MODEM_HIST-7-CONTROL: chars]: Control Reply: 0x[hex][hex]Explanation This tracing message indicates that a reply to a control message has been received.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-CSM_IC_CALLING_NUM: [chars]: ISDN incoming caller number: [chars]Explanation This tracing message gives the number of an incoming ISDN caller.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-CSM_OC_CALLED_NUM: [chars]: ISDN outgoing called number: [chars]Explanation This tracing message indicates a dialed ISDN number.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-MICA_DEBUG_EVT: [chars]: [chars]:Explanation This tracing message indicates a host debug event that has been reported by the specified Modem ISDN channel aggregation (MICA) modem.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-MICA_DYNAMIC_EVT: [chars]: [chars]: [chars]Explanation This tracing message indicates a dynamic event that has been reported by the specified Modem ISDN channel aggregation (MICA) modem.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-MICA_END_CONN_EVT: [chars]: [chars]: [chars]Explanation This tracing message indicates an end-connection event from the specified Modem ISDN channel aggregation (MICA) modem.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-MICA_LEAD_EVT: [chars]: [chars]: [chars], [chars], [chars], [chars]Explanation This tracing message indicates a lead event that has been reported by the specified Modem ISDN channel aggregation (MICA) modem.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-MICA_OOS_EVT: [chars]:[chars] Cause: [chars]Explanation This tracing message indicates an out-of-service event from the specified Modem ISDN channel aggregation (MICA) modem.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-MICA_STARTUP_EVT: [chars]: [chars]: [chars]. Modem firmware = [dec].[dec].[dec].[dec]Explanation This tracing message indicates the successful startup of the specified Modem ISDN channel aggregation (MICA) modem.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-MICA_STATE_EVT: [chars]:[chars] State: [chars]Explanation This tracing message indicates a state event that has been reported by the specified Modem ISDN channel aggregation (MICA) modem.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-MICA_STATIC_EVT: [chars]: [chars]: [chars]Explanation This tracing message indicate a static event that has been reported by the specified Modem ISDN channel aggregation (MICA) modem.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-MICA_STATUS_EVT: [chars]: [chars]: [chars]. Modem firmware = [dec].[dec].[dec].[dec]Explanation This tracing message indicates a status event that has been reported by the specified Modem ISDN channel aggregation (MICA) modem.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_ANALOG: [chars]: Modem Analog signal event: TX = [dec], RX = [dec], Signal to noise = [dec]Explanation This tracing message indicates a change in the analog signal status.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_CALLER_ID: [chars]: Caller ID event: [chars]Explanation This tracing message indicates that the caller ID data has been received.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_CONN_1: [chars]: Connection event: TX/RX Speed = [int]/[int], Modulation = [chars]Explanation This tracing message indicates the establishment of a connection.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_CONN_2: Direction = [chars], Protocol = [chars], Compression = [chars]Explanation This is a continuation of the connection state tracing message.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_CONX_UPDATE: [chars]: Connection update event: TX/RX Speed = [int]/[int], Modulation = [chars]Explanation This tracing message indicates that a connection state change has occurred.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_DTR: [chars]: DTR event: [chars]Explanation This tracing message indicates that a change in the DTR signal has occurred.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_END_1: [chars]: End connection event: Retransmits for MNP block (TX/RX) = [dec]/[dec]Explanation This tracing message indicates the end-of-connection status.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_END_2: Duration = [dec]:%-02d:%-02d, Number of TX/RX char = [dec]/[dec]Explanation This is a continuation of the end-of-connection status message.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_END_3: Local Disc Reason = [chars], Remote Disc Reason = [chars]Explanation This is a continuation of the end-of-connection status message.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_ERROR: [chars]: Polling protocol error event: 0x[hex]Explanation This tracing message indicates that a polling protocol error has occurred.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_EVT_LOST: [chars]: Status event lost: 0x[hex]Explanation This tracing message indicates that a polling event was lost.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_INACT: [chars]: Modem Activity event: [chars]Explanation This tracing message indicates that a change in data activity status has occurred.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_MODEM_STATE: [chars]: Modem State event: [chars]Explanation This tracing message indicates that a modem state change has occurred.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_NO_RESP: [chars]: No poll response event: 0x[hex]Explanation This tracing message indicates that no poll response was received.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_PHONE: [chars]: Phone number event: [chars]Explanation This tracing message indicates that a phone number has been dialed.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_PROGRESS: [chars]: Call Progress event: [chars]Explanation This tracing message provides the status of a call in progress.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_RS232: [chars]: RS232 event: [chars][char] [chars][char] [chars][char] [chars][char] [chars][char] [chars][char] [chars][char]Explanation This tracing message indicates the occurrence of RS-232 (EIA/TIA-232) events.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_TX_RX: [chars]: TX/RX event: TXD=[chars], RXD=[chars]Explanation This tracing message indicates the occurrence of transmit and receive events.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-POLL_UNKNOWN: [chars]: Unknown or lost event 0x[hex]Explanation This tracing message indicates that the modem event history contains an unrecognized event. One or more events may be missing from the trace.
Recommended Action This error could be caused by insufficient space for storing the modem history. A possible remedy is to shorten the number of events recorded between history dumps. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%MODEM_HIST-7-STARTUP: [chars]: Startup Response: [chars]. Modem (boot) firmware = [dec].[dec].[dec] ([dec].[dec].[dec])Explanation This tracing message indicates the successful startup of the specified modem.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-TRACE_HDR: Modem [chars] Events Log:Explanation This is the initial message for the trace of the specified modem. The trace messages for the modem will follow.
Recommended Action Debug message only. No action is required.
Error Message
%MODEM_HIST-7-UNKNOWN_FRAME: [chars]: Error in events logExplanation This tracing message indicates a formatting error in the modem event history. One or more events may be missing from the trace.
Recommended Action Debug message only. No action is required.
The following are modem NVRAM error messages.
Error Message
%MODEM_NV-5-FLEXIBLE: [chars]Explanation This message type is created for all messages that have simple ASCII text and do not take any parameter. The message will provide details of the problem that 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 Versatile Interface Processor (VIP) Multi-channel Port Adapter (MPA) error messages.
Error Message
%MPA68360-1-DWNLDCKSM: MPA68360: Download checksum error (sent = 0x[hex], received = 0x[hex]Explanation The download of the internal microcode to the MPA68360 has failed to checksum correctly. This problem usually indicates a hardware failure of the MPA68360.
Recommended Action Perform a power cycle. 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
%MPA68360-1-DWNLDFL: MPA68360 download failed.Explanation The MPA68360 interface has failed. It could not download its operational microcode.
Recommended Action Perform a power cycle. 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
%MPA68360-1-INITFAIL: MPA68360 slot [dec]: Init Failed at [chars]Explanation The MPA68360 has failed to complete 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
%MPA68360-3-MBXREAD: MPA68360: Stale msg in [chars]- mbx0:%lx mbx1:%lx mbx2:%lxExplanation The MPA68360 has not responded to a message within a specified 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
%MPA68360-1-NOTCMPLT: MPA68360 download failed to complete.Explanation The MPA68360 has failed. It could not download its operational microcode.
Recommended Action Perform a power cycle. 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
%MPA68360-3-NOTMPA68360: Device reported [hex]Explanation The MPA68360 hardware has failed. A non-MPA68360 device pointed at the software for the MPA68360.
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
%MPA68360-1-NOTREADY: Not ready for download.Explanation The MPA68360 did not respond when commanded to download its operational microcode.
Recommended Action Perform a power cycle. If the message recurs, contact your Cisco technical support representative.
Error Message
%MPA68360-3-PANIC: MPA68360: Exception [dec], trace [dec]Explanation A software or hardware error involving the MPA68360 interface 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
%MPA68360-1-STARTFAIL: [chars]: Channel enable failedExplanation A software or hardware error has occurred. The MPA68360 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
%MPA68360-1-STOPFAIL: [chars]: Channel disable failedExplanation A software or hardware error has occurred. The MPA68360 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
%MPA68360-3-TOOSMALL: MPA68360: [chars] - packet was less than two bytesExplanation An output packet that was smaller than the minimum allowable datagram size was detected. An error in another driver or an error in the system software probably triggered this error 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.
The following are Label Switch Path (LSP) tunnel error messages.
Error Message
%MPLS_TE-3-CONSISTENCY: [chars]: [chars] [chars] [chars]Explanation An action attempted by the traffic engineering tunnel implementation has encountered an unexpected condition.
Recommended Action Copy the message exactly as it appears and report it to your Cisco technical service representative.
Error Message
%MPLS_TE-3-SIGNALLERINIT: Signaller unable to [chars]register RSVP [chars]Explanation A message handler used by the signaller to receive events or requests from the Resource Reservation Protocol (RSVP) could not be installed or has been removed.
Recommended Action Copy and save the message. If possible, restart the tag-switched path (TSP) tunnel signalling process by entering the no tag-switching tsp-tunnels command, followed by the tag-switching tsp-tunnels command. If the message continues to occur even after restarting the signalling process has been restarted several times, 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
%MPLS_TE-3-TUNNELKILL: Tunnel removal attempt (by [chars]) failed for tunnel [chars]: [chars]Explanation A state that is associated with a tag-switched path (TSP) tunnel could not be completely removed because of an internal failure.
Recommended Action Copy and save this message. If possible, remove all local TSP tunnel states by issuing the no tag-switching tsp-tunnels command, followed by the tag-switching tsp-tunnels command. The TSP tunnels that are removed by the first command should be resignaled shortly after the second command has been issued. If the message recurs, copy and save the message, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Multiprotocol over ATM (MPOA) error messages.
Error Message
%MPOA-3-MPC_ERROR: [chars]Explanation A software error has occurred in the multiprotocol-over-ATM client (MPC) 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
%MPOA-6-MPC_INFORMATION: [chars]Explanation This message provides information about the status of a multiprotocol-over-ATM (MPC) client.
Recommended Action No action is required.
Error Message
%MPOA-4-MPC_WARNING: [chars]Explanation This messages is a non fatal warning from the multiprotocol-over-ATM client (MPC) software, probably the result of an incorrect configuration or operator command. Details about the warning are included in the message.
Recommended Action Determine if a configuration or operator error has caused this warning. 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
%MPOA-3-MPOA_ERROR: [chars]Explanation A software error has occurred in the multiprotocol-over-ATM subsystem.
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
%MPOA-3-MPS_ERROR: [chars]Explanation A software error has occurred in the multiprotocol-over-ATM server (MPS) 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
%MPOA-4-MPS_WARNING: [chars]Explanation This is a non fatal warning from the multiprotocol-over-ATM server (MPS) software, probably the result of an incorrect configuration or operator command. Another possible but less likely cause could be an internal software error.
Recommended Action Determine if a configuration or operator error has caused this warning. 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
%MPOA-5-UPDOWN: [chars]Explanation A multiprotocol-over-ATM (MPS) entity has been brought up or down. This is an informational message only.
Recommended Action No action is required.
The following are multicast route error messages.
Error Message
%MROUTE-4-RADIXDELETE: Error trying to delete multicast route entry [int]/[dec] for [int] (expected [hex], got [hex])Explanation An error involving the multicast routing table has occurred. A route could not be deleted from the routing table.
Recommended Action Enter the clear ip mroute command. Determine whether the router is low on memory. 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
%MROUTE-2-RADIXINIT: Error initializing IP multicast radix for [int]Explanation Insufficient memory is available to initialize the IP multicast 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
%MROUTE-4-RADIXINSERT: Error trying to add multicast route entry [int]/[dec] for [int] (expected [hex], got [hex])Explanation An error in the multicast routing table has occurred. A route could not be inserted into the routing table.
Recommended Action Enter the clear ip mroute command. Determine whether the router is low on memory. If the message recurs, contact your Cisco technical support representative.
Error Message
%MROUTE-4-RPF_LOOKUP_LOOP: RPF route lookup loop for [int], route [int]/[dec]Explanation A possible routing loop has been caused by routers that are sending Reverse Path Forwarding (RPF) datagrams to different tables.
Recommended Action Inspect the routing tables used for RPF and resolve any routing loops.
The following are multicast route error messages.
Error Message
%MSDP-5-PEER_UPDOWN: Session to peer [int] going [chars]Explanation The session to the peer is going up or down.
Recommended Action Determine whether the router is low on memory.
The following are Mx serial application-specific integrated circuit (ASIC) error messages.
Error Message
%MUESLIX-4-DEF_SUBRATE: [chars] [chars]Explanation A user has attempted unsuccessfully to change the data service unit (DSU) bandwidth by using DS3 remote management commands. This operation would not change the user-configured DSU bandwidth.
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
%MUESLIX-3-DISCOVER: Mx serial (bay [dec]): Interface found: [dec]Explanation The Mx serial hardware has failed. Some interfaces on the board did not come up.
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
%MUESLIX-1-DWNLDFL: Mx serial (bay [dec]): PA down load failedExplanation The Mx serial hardware has failed and 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
%MUESLIX-1-FAILURE_CAUSE: [chars]: [chars][chars]: 0x[hex], 0x[hex]Explanation A failure involving the port adapter 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 what condition caused the "STOPFAIL/STARTFAIL" error message text, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%MUESLIX-1-HALT: Mx serial: [chars] TPU halted: cause 0x[hex] status 0x[hex] shadow 0x[hex]Explanation The Mx serial firmware 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
%MUESLIX-1-INITFAIL: Mx serial (bay [dec]), Init Failed at [chars]Explanation The Mx serial port adapter has failed to complete 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
%MUESLIX-3-NOTMUESLIX: Mx serial (bay [dec]): Device reported [hex]Explanation The Mx serial hardware has failed. A non-Mx serial device pointed at the Mx serial software.
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
%MUESLIX-3-OWNERR: [dec] packet buffer, pak=0x[hex]Explanation A software or hardware error has occurred. The Mx serial driver has detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%MUESLIX-1-STARTFAIL: Mx serial, [chars] Start Failed at [chars]Explanation A software or hardware error has occurred. The Mx serial interface is not responding to commands that had been 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
%MUESLIX-1-STOPFAIL: Mx serial, [chars] Stop Failed at [chars]Explanation The Mx serial 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.
The following are 8PRI/4T board error messages.
Error Message
%MXT_FREEDM-1-DWNLDFL: 8PRI/4T board slot [dec]: Firmware download failed.Explanation An attempt to download the firmware into the 8PRI/4T board has failed.
Recommended Action Power-cycle the router.
Error Message
%MXT_FREEDM-1-HALT: 8PRI/4T board slot [dec]: Firmware sent a HALT interrupt.Explanation A double bus fault has occurred in the 8PRI/4T board 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
%MXT_FREEDM-1-INVALID_SHMEM: Invalid Shared Memory size detectedExplanation The current shared memory in the 8PRI/4T board is not supported.
Recommended Action Replace the shared memory with the supported configuration.
Error Message
%MXT_FREEDM-1-PCI_DBUS_BR_FAIL: PCI-DBUS Bridge in slot [dec] Failure: [chars]Explanation An internal error has occurred in the 8PRI/4T board.
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 network clock synchronization error messages.
Error Message
%NETWORK_CLOCK_SYNCHRONIZATION-4-NETCLK_CHANGE: Network clock source transitioned from Priority [dec] [chars] [chars] to Priority [dec] [chars] [chars]Explanation A change in the clock source 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
%NETWORK_CLOCK_SYNCHRONIZATION-4-NETCLK_INIT: Network clock source initialised to local oscillatorExplanation This message indicates that the network clock used will be internal.
Recommended Action No action is required.
Error Message
%NETWORK_CLOCK_SYNCHRONIZATION-4-NETCLK_PLL_LOST_LOCK: Network clock [chars] PLL lost lock - clock source failedExplanation The clock source has failed.
Recommended Action If an alternate clock source is available, it will be used.
The following are Next Hop Resolution Protocol (NHRP) error messages.
Error Message
%NHRP-3-PAKERROR: Receive [chars] for our [chars], code: [chars]([dec]), offset: [dec], data: [chars]Explanation An error indication packet has arrived to report that the system had sent a bad packet.
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
%NHRP-3-PAKREPLY: Receive [chars] packet with error - [chars]([dec])Explanation An Next Hop Server (NHS) has rejected a request packet.
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 network interface module (NIM) error messages.
Error Message
%NIM-2-BADNIMREV: Unsupported version of [chars] NIM in slot [dec] Version 0x[hex]Explanation The indicated network interface module (NIM) is not supported because it is not of the correct revision level. Certain platforms (Cisco 4500 or Cisco 4700, for example) require some NIMs to be of a minimum revision level.
Recommended Action Upgrade the NIM to the proper level.
Error Message
%NIM-2-BADSLOT: Illegal reference to non-existent slot [dec]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%NIM-2-BADSUBUNIT: Illegal reference to non-existent subunit [dec] in slot [dec]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%NIM-2-DEADICHAINQ: Attempted to manipulate uninitialized ichainQ in [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
%NIM-2-LOSTICHAINQ: Couldn't find idb 0x[hex] in ichainQ in [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
%NIM-2-NOHWADDRESS: All hardware addresses have been allocated - maximum of [dec]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%NIM-2-UNSUPNIM: Unsupported [chars] NIM in slot [dec]Explanation The specified network interface module (NIM) is not supported on this platform.
Recommended Action Remove the NIM.
The following are Network Routing Processor (NRP) error messages.
Error Message
%NRP-3-IPC: [chars] [chars]Explanation An interprocess communication (IPC) error has occurred. The details of what was attempted and what went wrong will be printed.
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 Network Switch Processor (NSP) error messages.
Error Message
%NSP-3-BADSLOT: Invalid slots[]: [hex]Explanation An internal error, indicating an invalid slot typr pointer, 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
%NSP-2-NOMEMORY: msgtxt_nomemoryExplanation An operation could not be accomplished because of a low memory condition. The current system configuration, the network environment, or possibly a software error might have exhausted or fragmented the system memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a configuration that has more memory.
Error Message
%NSP-4-SONET_ALARM: [chars]: [chars] [chars]Explanation A SONET line warning condition has been detected.
Recommended Action No action is required.
The following are Cisco 6400 node switch processor (NSP) error messages.
Error Message
%NSP_APS-4-SWITCH: Interface [chars] switched from [chars] to [chars] channelExplanation The automatic protection switching (APS) logic has determined that a switchover from one port to another has been requested.
Recommended Action No action is required.
The following are Cisco 6400 online insertion and removal (OIR) error messages.
Error Message
%NSP_OIR-3-ALOC_OIR_EVENT: OIR event structure allocation failureExplanation An internal online insertion and removal (OIR) element allocation failure has occurred. This error usually indicates a memory leak.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%NSP_OIR-3-BADCARD: Unrecognized Card, Driver for Card not available in system software, ignoring card type 0x[hex]Explanation The card that had been inserted into the system was not recognized by the software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%NSP_OIR-3-BADINS: Insufficient system resources to complete card insertion/redundancy request, Reverting ConfigurationExplanation The internal data structures for the specified interface could not be allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%NSP_OIR-3-BAD_FULL_INS: Cannot enable half height card, redundancy conflictExplanation A redundancy or card conflict with the cards in an adjacent slot 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
%NSP_OIR-3-BAD_HALF_INS: Cannot enable half height card, redundancy conflictExplanation A redundancy or card conflict with the cards in an adjacent slot 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
%NSP_OIR-6-FULL_CINS: Card [chars] inserted into slot: [dec]Explanation A full card has been inserted into the slot.
Recommended Action No action is required.
Error Message
%NSP_OIR-6-FULL_CREM: Card [chars] removed from slot: [dec]Explanation A full card has been removed from the slot.
Recommended Action No action is required.
Error Message
%NSP_OIR-6-FULL_ONLINE: Card [chars], slot: [dec], being brought onlineExplanation A full card is being brought online.
Recommended Action No action is required.
Error Message
%NSP_OIR-6-HALF_CINS: Card [chars] inserted into subslot: [dec]/[dec]Explanation A half-height card has been inserted into a subslot.
Recommended Action No action is required.
Error Message
%NSP_OIR-6-HALF_CREM: Card [chars] removed from subslot: [dec]/[dec]Explanation A half-height card has been removed from a subslot.
Recommended Action No action is required.
Error Message
%NSP_OIR-6-HALF_ONLINE: Card [chars], subslot: [dec]/[dec], being brought onlineExplanation A half-height card is being brought online.
Recommended Action No action is required.
Error Message
%NSP_OIR-3-INVCARD: Inserted card incompatible with previously removed cardExplanation The card inserted is not same type as the card that was removed and is therefore invalid.
Recommended Action Insert a card similar to the one that was removed, or clear out the alarm source.
Error Message
%NSP_OIR-3-INV_HWCFG1: Invalid card/configuration in slot([dec]) Ignoring CardExplanation The cards that are present in the chassis in the current mode are incompatible.
Recommended Action Remove the cards and clear out the alarm sources. Ensure that the cards are compatible.
Error Message
%NSP_OIR-3-INV_HWCFG2: Cannot enable card slot([dec]) subslot redundancy is active on subcard in slot([dec])Explanation The cards that are present in the chassis in the current mode are incompatible.
Recommended Action Remove the cards and clear out the alarm sources. Ensure that the cards are compatible.
Error Message
%NSP_OIR-4-INV_REDCFG: Redundancy submode not present!Explanation The system configuration does not have the redundancy submode.
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
%NSP_OIR-3-LONGSTALLExplanation The newly inserted card may not be seated properly.
Recommended Action Remove the card and reseat it.
Error Message
%NSP_OIR-4-UNEXPECTED_OFFLINE: 6400 Card [dec]/[dec] found off line - will 'virtually' remove and reinsert to bring onlineExplanation The specified card has gone offline. This problem may have been caused by a power loss.
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.
Posted: Fri Jun 16 11:50:14 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.