-
Cisco IOS System Messages, Volume 2 of 2
-
System Messages Overview
-
MBUF through MODEM
-
MODEM_HIST through NSP
-
NSP_APS through POSDW
-
POSLC through PQUICC_ETHER
-
PQUICC_ETHERNET through RESOURCE_MON
-
RESYNCH through SDLC
-
SDLLC through SNAPSHOT
-
SNASW
-
SNMP through SWITCH_IF
-
SYS through TCPIP
-
TDM through TXCONN
-
UBR7200 through VPD
-
VPDN through XTAGATM
-
Volume 2 Glossary
-
Table Of Contents
NETWORK_CLOCK_SYNCHRONIZATION Messages
MODEM_HIST Messages
The following are router shelf modem history and tracing messages.
Error Message%MODEM_HIST-7-CONTROL : /n [chars]: Control Reply: [hex][hex]
Explanation A reply to a control message was received. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-CSM_IC_CALLED_NUM : /n[chars]: ISDN incoming called number: [chars]
Explanation The number of the ISDN line that is receiving a call has been displayed. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-CSM_IC_CALLING_NUM : /n[chars]: ISDN incoming caller number: [chars]
Explanation The number of an incoming ISDN caller has been displayed. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-3-CSM_MODEMDEAD : \n[chars]:[chars]\n Cause: [chars]
Explanation This message is a trace log event. A timeout occurred while a modem was being disconnected and then reconnected. The modem is marked as out of service so that it can be recovered.
Recommended Action No action is required.
Error Message%MODEM_HIST-7-CSM_OC_CALLED_NUM : \n[chars]: ISDN outgoing called number: [chars]
Explanation A dialed ISDN number has been displayed. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-3-DC_EVT_POLL : \n[chars]: DC session response: [chars]
Explanation A DC session response event has occurred. This is a trace log event only.
Recommended Action No action is required.
Error Message%MODEM_HIST-3-DC_SESSION : \n[chars]: DC Session received reply
Explanation The DC session has received a reply. This is a trace log event only.
Recommended Action No action is required.
Error Message%MODEM_HIST-3-END_CALL : [chars] Modem [dec]/[dec] [chars]
Explanation The end of the modem call has occurred. This is an informational message only.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MODEM_HIST-7-MICA_DEBUG_EVT : \n[chars]: [chars]:
Explanation A host debug event has been reported by the specified MICA modem. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_DYNAMIC_EVT : \n[chars]: [chars]: [chars]
Explanation A dynamic event has been reported by the specified MICA modem. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_END_CONN_EVT : \n[chars]: [chars]: [chars]
Explanation An end-connection event from the specified MICA modem has occurred. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_LEAD_EVT : \n[chars]: [chars]:[chars], [chars], [chars], [chars]
Explanation A lead event has been reported by the specified MICA modem. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_OOS_EVT : \n[chars]: [chars]\n[chars] Cause: [chars]
Explanation An out-of-service event from the specified MICA modem has occurred. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_STARTUP_EVT : \n[chars]: [chars] [chars]. \n[chars] Modem firmware = [dec].[dec].[dec].[dec]
Explanation A successful startup of the specified MICA modem has occurred. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_STATE_EVT : \n[chars]: [chars]\n[chars] State: [chars]
Explanation A state event has been reported by the specified MICA modem. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_STATIC_EVT : \n[chars]: [chars]: [chars]
Explanation A static event has been reported by the specified MICA modem. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_STATUS_EVT : \n[chars]: [chars]: [chars]. \n[chars] Modem firmware = [dec].[dec].[dec].[dec]
Explanation A status event has been reported by the specified MICA modem. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_ANALOG : \n[chars]: Modem Analog signal event: TX = [dec], RX = [dec], Signal to noise = [dec]
Explanation A change in the status of an analog signal has occurred. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_CALLER_ID : \n[chars]: Caller ID event: [chars]
Explanation Caller ID data has been received. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_CONN_1 : \n[chars]: Connection event: TX/RX Speed = [int]/[int], Modulation = [chars]
Explanation The establishment of a connection has occurred. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_CONN_2 : \n Direction = [chars], Protocol = [chars], Compression = [chars]
Explanation This message is a continuation of the connection state tracing message.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_CONX_UPDATE : \n[chars]: Connection update event: TX/RX Speed = [int]/[int], Modulation = [chars]
Explanation A connection state change has occurred. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-3-POLL_DSP_NEEDED : \n[chars]: DSP Image Needed Event
Explanation A DSP image must be downloaded to the modem to achieve 56K operation.
Recommended Action Download the DSP image to the modem.
Error Message%MODEM_HIST-7-POLL_DTR : \n[chars]: DTR event: [chars]
Explanation A change in the DTR signal has occurred. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_END_1 : \n[chars]: End connection event: Retransmits for MNP block (TX/RX) = [dec]/[dec]
Explanation An end-of-connection status has occurred. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_END_2 : \n Duration = [dec]:[dec]:[dec], Number of TX/RX char = [dec]/[dec]
Explanation This message is a continuation of the end-of-transmission status message.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_END_3 : \n Local Disc Reason = [chars], Remote Disc Reason = [chars]
Explanation This message is a continuation of the end-of-transmission status message.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_ERROR : \n[chars]: Polling protocol error event: [hex]
Explanation A polling protocol error has occurred. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_EVT_LOST : \n[chars]: Status event lost: [hex]
Explanation A polling event has been lost. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_INACT : \n[chars]: Modem Activity event: [chars]
Explanation A change in the data activity status has occurred. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_MODEM_STATE : \n[chars]: Modem State event: [chars]
Explanation A modem state change has occurred. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_NO_RESP : \n[chars]: No poll response event: [hex]
Explanation No response has been received to a poll. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_PHONE : \n[chars]: Phone number event: [chars]
Explanation A phone number is being dialed. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_PROGRESS : \n[chars]: Call Progress event: [chars]
Explanation The status of a call in progress has been provided. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_RS232 : \n[chars]: RS232 event: [chars][char] [chars][char] [chars][char] [chars][char] [chars][char] [chars][char] [chars][char]
Explanation RS-232 (EIA/TIA-232) events have occurred. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_TX_RX : \n[chars]: TX/RX event: TXD=[chars], RXD=[chars]
Explanation Transmit-and-receive events have occurred. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-POLL_UNKNOWN : \n[chars]: Unknown or lost event [hex]
Explanation The modem event history contains an unrecognized event. One or more events might be missing from the trace.
Recommended Action This condition could be caused by insufficient space for storing the modem history. If these events are desirable, 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 : \n[chars]: Startup Response: [chars].
Modem (boot) firmware = [dec].[dec].[dec] ([dec].[dec].[dec])Explanation The successful startup of the specified modem has occurred. This is a tracing message only.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-TRACE_HDR : \n\n[chars] Modem [chars] Events Log:
Explanation This is the initial message for the trace of the specified modem. The stored trace messages for the modem will follow.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-UNKNOWN_FRAME : \n[chars]: Error in events log
Explanation A formatting error has occurred in the modem event history. One or more events might be missing from the trace.
Recommended Action This is a debug message only. No action is required.
MODEM_NV Messages
The following are modem NVRAM 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
MODEMCALLRECORD Messages
The following are Modem Call Record messages.
Error Message%MODEMCALLRECORD-3-PM_CALL_RECORD_ERROR : [chars]
Explanation The modem call record log is too large and exceeds the capacity of the system log.
Recommended Action No action is required.
Error Message%MODEMCALLRECORD-3-PM_NO_CALL_RECORD_BUF : [chars]
Explanation A failure to allocate a buffer for building the modem call record has occurred.
Recommended Action No action is required.
Error Message%MODEMCALLRECORD-6-PM_TERSE_CALL_FAILED_RECORD : [chars]
Explanation A terse modem call record could not be created.
Recommended Action No action is required.
Error Message%MODEMCALLRECORD-6-PM_TERSE_CALL_RECORD : [chars]
Explanation A terse modem call record was created.
Recommended Action No action is required.
MONITOR Messages
The following are Cisco IOS software ROM monitor messages.
Error Message%MONITOR-3-VARRESTFAIL : ROM monitor variable restoration of "[chars]", failed.
Explanation The new ROM monitor variable could not be written to memory, and the ROM monitor variable could not be restored to its original value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support and show bootvar commands to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support and show bootvar command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MONITOR-3-VARSETFAIL : ROM monitor variable set of "[chars]" failed.
Explanation The system could not set a ROM monitor variable. This condition typically occurs when no ROM monitor memory is available to save the variable. The ROM monitor memory is most likely already filled with configuration boot commands.
Recommended Action Enter the show bootvar command and check the output to determine if there is anything unusual with the system. Try to reduce the number of configuration boot commands.
MPA68360 Messages
The following are VIP Multi-channel Port Adapter messages.
Error Message%MPA68360-1-DWNLDCKSM : Failed for bay [dec], sent = [hex], received = [hex]
Explanation The download of the internal firmware 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 problem persists, there might be a problem with the MPA68360 hardware.
Error Message%MPA68360-1-DWNLDFAIL : Microcode to port adaptor in bay [dec]
Explanation A microcode download to the port adapter in the specified bay has failed.
Recommended Action Try reseating the PA correctly. If the problem persists, verify the hardware by inserting the PA in another router. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPA68360-1-INITFAIL : Slot [dec]: [chars]
Explanation The PRI port adapter has failed to complete its hardware initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MPA68360-3-MBXREAD : [chars] has stale msg - mbx0:[hex], mbx1:[hex], mbx2:[hex]
Explanation The MPA68360 has not responded to a message within a specified time.
Recommended Action Try reseating the PA correctly. If the problem persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPA68360-1-NOTCMPLT : Microcode download to bay [dec] failed
Explanation The MPA68360 hardware has failed. It could not download its operational microcode.
Recommended Action Try reseating the PA correctly. If the problem persists, copy the error message exactly as it appears, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MPA68360-3-NOTMPA68360 : Bay [dec] device ID seen as [hex], expected [hex]
Explanation The MPA68360 hardware has failed. A device other than the MPA68360 pointed at the software for the MPA68360 serial.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MPA68360-1-NOTREADY : Bay [dec] for microcode download
Explanation An error has occurred on the communication path between the driver and the MPA68360.
Recommended Action Try reseating the PA correctly. If the problem persists, verify the hardware by inserting the PA in another router. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPA68360-3-PANIC : Exception [dec], trace [dec]
Explanation The MPA68360 firmware has detected an illegal or unexpected CPU exception or condition. This condition may be caused by a software error or by a hardware failure.
Recommended Action Try reseating the PA correctly. If the problem persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPA68360-1-STARTFAIL : [chars] channel not enabled
Explanation A software or hardware error has occurred. The MPA68360 serial interface is not responding to the commands that are used to initialize it.
Recommended Action Enter the debug serial interface EXEC command on the Cisco 7200 VIP. When this message is seen again, collect the output, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Note
Entering the debug serial interface command can cause a flood of debug messages if many serial interfaces are configured. Turn off debugging as soon as the information is collected.
Error Message%MPA68360-1-STOPFAIL : [chars] channel not disabled
Explanation The PRI port adapter has failed to respond to a request to disable an interface.
Recommended Action Enter the debug serial interface EXEC command on the Cisco 7200 VIP. When this message is seen again, collect the output, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Note
MPC Messages
The following are CMCC messages for the Multipath Channel (MPC) protocol.
Error Message%MPC-3-BAD_CONFIG_CODE : [chars]: Unrecognized config action code [dec]
Explanation A TG configuration command has been received containing an unrecognized action code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-BAD_CONFIG_DIR : PA[dec] MPC [hex]-[hex] bad direction code [hex]
Explanation The configuration message for a CMPC statement contains an invalid direction code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-6-BAD_DIRECTION : PA[dec] MPC [hex]-[hex] configured for [chars]
Explanation An XID2 message from the host has specified a subchannel read or write transfer direction that is different from the direction configured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-BAD_DLC_CMD : Received MPC DLC command [hex] unrecognized
Explanation An MPC DLC frame has been received with an unrecognized DLC command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-BAD_FLAGS : Received MPC frame with invalid flags [hex]
Explanation An MPC block has been received with an unrecognized header configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-BAD_HDR : Unrecognized MPC header received: [hex] [hex]
Explanation An MPC block has been received with an unrecognized header configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-BAD_INB_BFR : Inbound bfr to CMPC has no room for header
Explanation The CMPC is attempting to build a DLC header, but there is insufficient space in the inbound buffer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-BLOCK_SEQ_ERROR : Block rcvd with seq num [hex], expected [hex]
Explanation An MPC block has been received with a sequence number error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CFG_TYPE_ERR : [chars]: CMPC TG partner type code invalid
Explanation The CMPC TG configuration block contains an invalid partner type code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CMPCP_ACT_ERR : Activate, but CvInfo block already active with handle [dec]
Explanation An attempt has been made to activate an MPC+ control block that is already active.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CMPCP_BLK_FMT_ERR : [chars]: [chars]
Explanation An MPC+ channel block that contains a format error has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-6-CMPCP_CONN_ACT : [chars]: [chars] Connection Activated
Explanation An IP type connection has been activated.
Recommended Action No action is required.
Error Message%MPC-6-CMPCP_CONN_INACT : [chars]: [chars] Connection Deactivated
Explanation An IP type connection has been deactivated.
Recommended Action No action is required.
Error Message%MPC-3-CMPCP_CV_ERR1 : Unrecognized/Unexpected CV: [hex]
Explanation An unrecognized or unexpected MPC+ subvector has been received from the host.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CMPCP_CV_ERR2 : Possible Config error:\n Rcvd [chars] [chars], [chars] [chars]
Explanation CMPC+ has detected a mismatch between a value received from the host and a configured or generated value. A configuration error may have occurred.
Recommended Action If this is not the case, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CMPCP_CV_ERR3 : Corrupt CV Frame: [chars]
Explanation A received CV frame is corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CMPCP_CV_LEN_ERR : Received subvector [hex] too long
Explanation An MPC+ subvector that is longer than the area reserved on the basis of protocol analysis has been received from the host.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-6-CMPCP_CV_LOG : [chars]: Event/State [chars]/[chars]
Explanation This informational message is given before CMPCP_CV_ERR type messages to provide a more complete description of the problem.
Recommended Action See the CMPCP_CV_ERR message that follows.
Error Message%MPC-3-CMPCP_DUPL_TOKEN : Duplicate group token, '[chars]' PA[dec] MPC [hex]-[hex]
Explanation An XID2 message from the host specifies a group token that has already been specified for another TG. A configuration error in which multiple read or write subchannels are specified in a TRLE may have occurred.
Recommended Action If this is not the case, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CMPCP_FRAME_ERR1 : [chars]: Frame rcvd on [chars] token [chars]
Explanation A problem has been detected with an MPC+ frame token.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CMPCP_FRAME_ERR2 : [chars]: Frame rcvd on [chars] token, [chars]: [hex]
Explanation A specific field in an MPC+ subvector received from the host is not recognized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CMPCP_HANDLE_ERR : All CMPC+ handles in use
Explanation An MPC+ handle cannot be allocated because the handle pool is empty.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CMPCP_INACT_ERR : Inact, but CvInfo block already inactive
Explanation An attempt is made to deactivate an MPC+ control block that is already inactive.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CMPCP_PROT_ERR : [chars]: Unrecognized Protocol Type: [hex]
Explanation The host has attempted to set the protocol type for a connection to a value not recognized by CMPC+.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-6-CMPCP_STALE_TOKEN : Rcvd MPC+ local token is stale
Explanation A local token was received that is no longer in use.
Recommended Action This action probably occurred during a TG shutdown sequence, with no associated operational problems. If an operation problem occurred, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CMPCP_TOKEN_ERR : Error in rcvd MPC+ local token: [chars]
Explanation An invalid condition has been detected in a received local token.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CMPCP_TOKEN_LEN_ERR : Token detectd with invalid size: [dec]
Explanation A token with an invalid length has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CONFIG_ERR : TG configured IP but channel protocol not MpcPlus
Explanation The host has attempted a channel connection to a TG but did not use the correct channel protocol (MPC+). A configuration error may have occurred.
Recommended Action If this is not the case, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CV_CMGR_FSM_ERR : [chars]: Event [chars], State [chars]
Explanation An internal state machine has attempted to execute an event that is inconsistent with the state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-CV_PROT_FSM_ERR : [chars]: Event [chars], State [chars]
Explanation An internal state machine has attempted to execute an event that is inconsistent with the state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-6-INIT : PA[dec] MPC [hex]-[hex] Device initialized
Explanation An MPC device has been initialized. The device string is in the form PAx MPC yyyy-zz, where x is the port adapter number, yyyy is the path, and zz is the device number.
Recommended Action No action is required.
Error Message%MPC-3-LENGTH_ERR : Inconsistent length in received MPC frame for TG [chars]
Explanation An MPC frame has been received with a length value that is inconsistent with the channel block length.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-6-LENGTH_ERR_DATA : Additional LENGTH_ERR message data: [hex][hex][hex][hex][hex][hex][hex][hex]
Explanation This informational message immediately follows a LENGTH_ERR_INFO message if frame data exists.
Recommended Action Copy this message, along with the contents of the LENGTH_ERR and LENGTH_ERR_INFO messages. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-6-LENGTH_ERR_INFO : Additional LENGTH_ERR message info: currBfr [hex], msg_length [hex]
Explanation This informational message immediately follows and amplifies a LENGTH_ERR message.
Recommended Action Copy this message, along with the contents of the LENGTH_ERR message, Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-6-LINK_CONFIGURED : Link [chars] already configured
Explanation An attempt has been made to configure an MPC link that has already been configured.
Recommended Action No action is required.
Error Message%MPC-6-NODE_NOT_ACTIVE : Host attempted activation of [chars] but TG not configured
Explanation A message has been received for an MPC link for which the transmission group has not been configured.
Recommended Action Configure the required TG. This process may require the host node or profile to be cycled down and up.
Error Message%MPC-0-NOMEM : [chars] Attempt to acquire memory failed, pc: [hex], at [int]
Explanation A call to create a pool or get a buffer has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-PARTNER_CFG_ERR : [chars]: [chars]
Explanation A configuration command has failed because the MPC partner linkage is not established.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-PARTNER_FSM_ERR : TG Name: [chars], Event [chars], State [chars]
Explanation An internal state machine has attempted to execute an event inconsistent with the state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-6-SEQ_NUM_WRAP : Sequence number from host wrapped. TG name [chars]
Explanation The sequence number in a block from the host has wrapped.
Recommended Action No action is required.
Error Message%MPC-6-SHUTDOWN : PA[dec] MPC [hex]-[hex] Device shutdown
Explanation An MPC device has been shut down. The device string is in the form PAx MPC yyyy-zz, where x is the port adapter number, yyyy is the path, and zz is the device number.
Recommended Action No action is required.
Error Message%MPC-3-SUBCH_FSM_ERR : PA[dec] MPC [hex]-[hex] Event [chars], State [chars]
Explanation An internal state machine has attempted to execute an event inconsistent with the state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-SWEEP_FSM_ERR : TG Name: [chars], Event [chars], State [chars]
Explanation An internal state machine has attempted to execute an event inconsistent with the state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-SWEEP_SEQ_ERROR : Sweep rcvd with seq num [hex], expected [hex]
Explanation An MPC sweep command has been received with a sequence number error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-0-SYSMGT_ERROR1 : MPC Subch detected error in sysmgt call: invalid CMPC DEVICE length
Explanation An invalid parameter has been received in a system management call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-0-SYSMGT_ERROR2 : MPC Subch detected error in sysmgt call: invalid operation [dec]
Explanation An invalid parameter has been received in a system management call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-0-SYSMGT_ERROR3 : MPC Llcc-Tg detected error in sysmgt call: invalid operation [dec]
Explanation An invalid parameter has been received in a system management call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-0-SYSMGT_ERROR4 : MPC Llcc-Tg detected error in sysmgt call: invalid CMPC DEVICE length
Explanation An invalid parameter has been received in a system management call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-6-TOO_MANY_TGS : Cannot configure more than [dec] MPC TGs
Explanation This informative message has been given when an attempt is made to configure more than the maximum number of MPC TGs.
Recommended Action No action is required.
Error Message%MPC-3-XID2_BAD_DATA : Invalid Xid2 Message: bad length or format
Explanation An MPC subchannel is in the XID2 exchange state, and the message received has a length that is not valid for an XID2 message segment.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-XID2_BAD_HDR : Unrecognized Xid2 header received
Explanation An Xid2 frame has been received and with a header configuration that is not recognized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPC-3-XID2_FSM_ERR : PA[dec] MPC [hex]-[hex] Event [chars], State [chars]
Explanation An internal state machine has attempted to execute an even that is inconsistent with the state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
MPLS_ATM_TRANS Messages
The following are ATM Transport over MPLS messages.
Error Message%MPLS_ATM_TRANS-3-CONSISTENCY : [chars]
Explanation An action attempted by the ATM over MPLS implementation has encountered an unexpected condition.
Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
MPLS_TE Messages
The following are Label Switch Path (LSP) Tunnel 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 on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPLS_TE-5-LSP : [chars]
Explanation An informational traffic engineering tunnel trap was generated for an LSP event.
Recommended Action Copy and save the message exactly as it appears on the console or in the system log for debugging analysis if the user is interested in understanding tunnel operation.
Error Message%MPLS_TE-3-SIGNALLERINIT : Signaller unable to [chars]register RSVP [chars]
Explanation A message handler used by the signaler to receive events or requests from RSVP could not be installed or removed.
Recommended Action Copy and save the message exactly as it appears on the console or in the system log. If possible, restart the TSP tunnel signaling process by issuing 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 signaling process several times, contact your Cisco technical support representative for assistance.
Error Message%MPLS_TE-5-TUN : [chars]
Explanation An informational traffic engineering tunnel trap was generated for a tunnel event.
Recommended Action Copy and save the message exactly as it appears on the console or in the system log for debugging analysis if the user is interested in understanding tunnel operation.
Error Message%MPLS_TE-3-TUNNELKILL : Tunnel removal attempt (by [chars]) failed for tunnel [chars]: [chars]
Explanation The state that is associated with a 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 state by issuing the no tag-switching tsp-tunnels command, followed by the tag-switching tsp-tunnels command. (The TSP tunnels that were removed by the first command should be resignaled shortly after the second command has been issued.) If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
MPLS_TE_PCALC Messages
The following are MPLS TE path calculation facility messages.
Error Message%MPLS_TE_LM-5-CLEAR_COUNTERS : Clear MPLS TE Link Management counters by [chars]
Explanation The MPLS TE link management counters have been cleared.
Recommended Action No action is required.
Error Message%MPLS_TE_PCALC-2-DUP_IP_ADDRESS : [chars] [IP_address] [chars]
Explanation Two nodes have the same stable IP address.
Recommended Action Find the system that has the duplicate IP address and configure a different IP address for that system.
Error Message%MPLS_TE_PCALC-2-DUP_RRR_ID : [chars] [IP_address] [chars]
Explanation Two nodes have the same stable router ID.
Recommended Action Find the system that has the duplicate router ID and configure a different ID for that router.
Error Message%MPLS_TE_PCALC-3-INIT : pcalc_system_id_size == 0
Explanation An internal inconsistency has been detected when an attempt was made to initialize the MPLS TE path calculation system ID before the system ID size is known.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPLS_TE_PCALC-2-INVLD_RTR_FRAGMENT : Router id ([IP_address]) received from [chars] in fragment [int], previously received in fragment [int]
Explanation A router ID has been received in fragments.
Recommended Action Locate the problem router and contact your Cisco technical support representative for assistance.
Error Message%MPLS_TE_PCALC-2-INVLD_RTR_ID : Invalid router id ([IP_address]) received from [chars] in fragment [int]
Explanation An invalid router LSA has been received. An LSA should not contain a router ID of zero. The cause of this problem might be misconfiguration, memory corruption, or unexpected behavior on a router.
Recommended Action Locate the problem router and check the configuration. To determine what is causing this problem, contact your Cisco technical support representative for assistance.
Error Message%MPLS_TE_PCALC-3-LSA : [chars] [chars]
Explanation An internal inconsistency has been detected when an attempt was made to receive an LSA for the MPLS TE topology database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPLS_TE_PCALC-2-MEM : [chars] [dec]
Explanation An attempt to allocate memory has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPLS_TE_PCALC-3-PATH : [chars]
Explanation An internal inconsistency has been detected when an attempt was made to establish an MPLS TE tunnel using the MPLS TE path calculation subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
MPOA Messages
The following are Multiprotocol over ATM (MPOA) 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. Enter the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MPOA-6-MPC_INFORMATION : [chars]
Explanation This message provides information about the status of an MPC client.
Recommended Action No action is required.
Error Message%MPOA-4-MPC_WARNING : [chars]
Explanation This message is a nonfatal warning from the 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 this error message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%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. Enter the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MPOA-3-MPS_ERROR : [chars]
Explanation A software error has occurred in the MPS software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MPOA-6-MPS_INFORMATION : [chars]
Explanation This message provides information about the status of an MPS.
Recommended Action No action is required.
Error Message%MPOA-4-MPS_WARNING : [chars]
Explanation This is a nonfatal warning from the 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 this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MPOA-5-UPDOWN : [chars]
Explanation A multiprotocol-over-ATM entity has been brought up or down.
Recommended Action This is a status message only. No action is required.
MROUTE Messages
The following are multicast route messages.
Error Message%MROUTE-6-LARGE_TWHEEL_DELAY : Exceeded maximum delay ([dec] ms) requested: [dec]
Explanation A timer with large delay has been requested. There is a maximum delay defined for the timer wheel. A function with a higher delay than the maximum delay has been scheduled. If a function with a higher delay is scheduled, it will be scheduled using the maximum possible delay minus a small delay offset.
Recommended Action Verify if a large IGMP query interval is set. Some timers can refresh periodically to allow for the large delay. Otherwise, no action is required.
Error Message%MROUTE-3-MIDB_QUEUE_ERR : Interface [chars] not in ([IP_address], [IP_address])
Explanation An error in maintaining the multicast route table has occurred. The MIDB has the highest expiration timer; however, it is not in the MDB that points to the MIDB.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MROUTE-4-RADIXDELETE : Error trying to delete multicast route entry [IP_address]/[dec] for [IP_address] (expected [hex], got [hex])
Explanation An error in 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 this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MROUTE-2-RADIXINIT : Error initializing IP multicast radix for [IP_address]
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. Enter the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MROUTE-4-RADIXINSERT : Error trying to add multicast route entry [IP_address]/[dec] for [IP_address] (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 this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MROUTE-3-ROUTECOUNT_ERR : Running multicast route count [int]
Explanation This system message was created as a troubleshooting aid to capture an unlikely internal software error. The condition that caused this message should not be seen in current Cisco IOS software releases and should not impact system performance.
Recommended Action If this message was seen after you entered the show ip mroute command, use the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl to search for the message and upgrade the Cisco IOS software based on the release in which the fix was integrated. If, after the upgrade, this message recurs and there is still a performance problem, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.
Error Message%MROUTE-3-ROUTECOUNT_ZERO : Multicast route count reached zero
Explanation The running count of multicast routes has reached zero when it should be nonzero.
Recommended Action An error in maintaining the multicast route count has occurred. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MROUTE-4-ROUTELIMIT : [int] routes exceeded multicast route-limit of [dec] - VRF [chars]
Explanation The number of multicast routes exceeds the configured maximum number. New routes cannot be added unless the configuration is changed.
Recommended Action If multicast traffic is of any priority among the traffic carried by this router, use the ip multicast route-limit command to increase the number of multicast routes. Otherwise, no action is required.
Error Message%MROUTE-4-ROUTELIMITWARNING : multicast route-limit warning (curr [int] threshold [int]) - VRF [chars]
Explanation The number of multicast routes has reached the configured percentage of the multicast route limit.
Recommended Action Consider increasing the multicast route limit.
Error Message%MROUTE-4-RPF_LOOKUP_LOOP : RPF route lookup loop for [IP_address], route [IP_address]/[dec]
Explanation A possible routing loop has been caused by routers that are sending RPF datagrams to different tables.
Recommended Action Check the routing tables used for RPF and resolve any routing loops.
Error Message%MROUTE-3-TWHEEL_ERR : Timer wheel internal error
Explanation An internal error in maintaining the timer wheel has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MROUTE-3-TWHEEL_INIT_ERR : Trying to re-initialize an already initialized timer wheel
Explanation An internal software error occurred while a timer wheel was being initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MROUTE-3-TWHEEL_INSERT_ERR : An error occured after inserting or executing a timer wheel event
Explanation An internal software error occurred after a timer wheel event was inserted or executed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MROUTE-3-TWHEEL_INT_ERR : Timer wheel error at interrupt level [dec]
Explanation An internal error involving the timer wheel occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MROUTE-3-TWHEEL_SLOT_ERR : Timer wheel event:[hex] slot:[dec] func:[hex] unequal to exec slot: [dec]
Explanation The timer wheel event has an inconsistent slot number.
Recommended Action Enter the clear ip mroute * command. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MROUTE-3-WAVLINIT : Could not initialize WAVL tree for ([IP_address],[IP_address])
Explanation An error has occurred in initializing the outgoing interface list for a multicast route. When this situation occurs, the system cannot search for the outgoing interfaces for a multicast route; hence, there is no reason for the MDB to be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
MSDP Messages
The following are Multicast Source Discovery Protocol (MSDP) route messages.
Error Message%MSDP-5-PEER_IS_SELF : Peering with self ([IP_address])
Explanation The MSDP is peering with itself.
Recommended Action Check the address of the MSDP peer.
Error Message%MSDP-5-PEER_UPDOWN : SessiSon to peer [IP_address] going [chars]
Explanation The session to the peer is going up or down.
Recommended Action Determine whether the router is low on memory.
Error Message%MSDP-4-PKT_TOO_BIG : Message size violation on [int]-byte packet from [IP_address], discarded
Explanation A message larger than the maximum MSDP message size has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSDP-4-SA_LIMIT : SA from peer [IP_address], RP [IP_address] for ([IP_address], [IP_address]) exceeded sa-limit of [dec]
Explanation The number of MSDP SAs exceeds the configured maximum number. SA cache entries cannot be added unless the configuration is changed.
Recommended Action If MSDP SAs come from legitimate sources or route processors, use the ip msdp sa-limit command to increase the number of SA entries allowed from the subject peer. Otherwise, no action is required.
MSG802 Messages
The following are CMCC Channel Interface Processor (CIP) 802 messages that are related to the IEEE 802.2cx Logical Link Control (LLC) protocol stack.
Error Message%MSG802-3-ADAPTER_LIMIT_EXCEEDED : Configuration for adapter [dec] [enet] rejected ([chars])
Explanation An attempt was made to configure more than 18 CSNA adapters. A maximum of 18 CSNA adapters is allowed per CIP.
Recommended Action To comply with the 18 CSNA adapter limit, reduce the number of CSNA adapters configured.
Error Message%MSG802-6-ADAPTER_OPEN : Adapter [chars]/[int] now open
Explanation Operability for the specified adapters that were brought up has been confirmed.
Recommended Action No action is required.
Error Message%MSG802-6-ADAPTER_REM : Adapter [chars]/[int] now removed
Explanation The removal of each of the specified adapters has been confirmed.
Recommended Action No action is required.
Error Message%MSG802-6-ADAPTER_UPD : Adapter [chars]/[int] LLC parm now altered
Explanation The changed LLC parameters for each of the specified adapters has been confirmed.
Recommended Action No action is required.
Error Message%MSG802-6-BADNS_WARN : INVALID NS detected [dec] times; tuning of LLC parameter may be needed !!!
Explanation The LLC protocol stack has received a bad frame that contains an "Invalid NS" message from its peer. Incorrectly configured LLC parameters may have occurred.
Recommended Action Reconfigure the LLC parameters of the CIP adapter and the peer.
Error Message%MSG802-6-CTASET_FAIL : set cta max_conn [dec] failed ([dec] bytes free) - max conn remain at [dec]
Explanation In its current configuration, the CTA mapper for CSNA cannot accept the maximum number of connections because of insufficient memory. Any attempt to decrease the maximum number of connections will be rejected.
Recommended Action CSNA should be run on a CIP card with at least 32 MB of memory. Refer to the CIP CSNA configuration guide to determine the memory requirements for the maximum number of connections configured. Check the router configuration in the virtual interface of the CIP (x/2) MAX_LLC_CONNECTIONS parameter. Determine whether the device has been over configured. If over configuring the device is not the problem, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-6-DMA_ABORT : DMA message consists of [dec] fragments with length of [dec]
Explanation The specified DLU send request has been aborted because it contained too many fragments or the fragments were too long.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-6-FLOW_OFF_COUNT : On [int], Off<30 [int], Off>30 [int], total [int], max off time [int] ms
Explanation This message provides statistics about flowed-off connections and may be preceded by a CTA-0-INACTIVE message.
Recommended Action No action is required.
Error Message%MSG802-6-FLOW_OFF_INFO : Ran [hex], Ucep [hex], Pcep [hex], [int] ms, ccb [hex]
Explanation This message provides statistics about flowed-off connections and may be preceded by a CTA-0-INACTIVE message.
Recommended Action No action is required.
Error Message%MSG802-6-FLOW_OFF_TERM : Terminating connection, RMAC=[hex].[hex].[hex] LMAC=[hex].[hex].[hex] RSAP=[hex] LSAP=[hex]
Explanation A connection has been terminated.
Recommended Action No action is required.
Error Message%MSG802-6-FRAMESZ_EXCEEDED : frame exceeded max size ([dec] bytes)
Explanation The MEMD buffer currently supports a maximum frame size of 4472 bytes. CSNA has detected that the specified frame exceeded the maximum size. The frame has been discarded.
Recommended Action Check the maximum frame length configured for the MEMD buffer.
Error Message%MSG802-3-HARD_ERROR : [chars]
Explanation The protocol stack has encountered error conditions that prevent it from continuing its normal operations. An error checking condition may have occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-3-INVALID_CFGCMD : invalid config cmd detected cmd=[dec]
Explanation The LLC task has detected an invalid configuration command. The command is rejected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-6-INVALID_ID : [chars]: invalid id type = [hex]
Explanation The LLC has received an invalid ID type that is not supported. The request is discarded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-3-INVALID_MSICMD : invalid msi cmd detected cmd=[dec]
Explanation The LLC task has detected an invalid MSI command. The request is discarded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-6-INVALID_PRIMITIVE : [chars]: invalid primitive code = [hex]
Explanation The LLC has received an invalid service primitive code. The error message will provide the service primitive code and identify the module and routine that had received it. This is not a fatal error, and the CSNA will continue to operate.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-3-INVALID_VCN1 : LAN not configured for vcn=[dec], adapter=[dec], lan=[dec], ran=[dec] - cfg cmd rejected ([chars])
Explanation An attempt to process the specified configuration command has failed because an invalid VCN was detected. The configuration command is rejected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-3-INVALID_VCN2 : LAN has configured for vcn=[dec], adapter=[dec], lan=[dec], ran=[dec] - cfg cmd rejected ([chars])
Explanation An attempt to process the specified configuration command has failed because an invalid VCN was detected. The configuration command is rejected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-6-LLC_DUP_CCB : LLC Station : RMAC=[hex].[hex].[hex] LMAC=[hex].[hex].[hex] LSAP=[hex] RSAP=[hex]
Explanation A request to open station has been received for a station address that already is open.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-6-LLC_DUP_SAP : LLC Duplicate SAP on interface [int] : SAP=[hex], new user([hex],[hex]) old user([hex],[hex])
Explanation The specified remote SAP has been opened by more than one XCA major node. The pair of values that follow old and new user in the message text are the USAP that identified the XCA major node that attempted to activate the MTU that was already in use.
Recommended Action Check the XCA node definitions.
Error Message%MSG802-6-LLC_SHUT : LLC shutdown completed
Explanation The LLC has been shut down. The LLC DMA READ/WRITE task and the TIMER task have been shut down.
Recommended Action No action is required.
Error Message%MSG802-6-LLC_START : Starting LLC-2 with a session capacity of [int]
Explanation The LLC subsystem has been brought up.
Recommended Action No action is required.
Error Message%MSG802-6-MAX_FAILED : change max conn [dec] failed ([dec] bytes free) - max conn remain at [dec]
Explanation In its current configuration, the CTA mapper for CSNA cannot accept the maximum number of connections because of insufficient memory. Any attempt to decrease the maximum number of connections will be rejected.
Recommended Action CSNA should be run on a CIP card with at least 32 MB of memory. Refer to the CIP CSNA configuration guide to determine the memory requirements for the maximum number of connections configured. Check the router configuration in the virtual interface of the CIP (x/2) MAX_LLC_CONNECTIONS parameter. Determine whether the device has been overconfigured. If the device has not been overconfigured, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-6-MAX_FAILED2 : cipmsg pool empty - max conn remain at [dec]
Explanation The CIP was not able to provide the maximum number of connections there were configured because it is unable to allocate a message buffer from the Multipath message pool.
Recommended Action Retry the max_llc command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-6-MAX_LLC_EXCEEDED : MAX_LLC_SESSIONS([int]) exceeded - [int] sessions rejected.
Explanation The maximum number of concurrent LLC connections has been exceeded.
Recommended Action Increase the MAX_LLC_SESSIONS parameter on the CIP virtual interface.
Error Message%MSG802-6-NOMEM : Insufficient memory to initialize LLC - [chars]
Explanation The channel adapter does not have sufficient memory to initialize the LLC stack. The LLC stack will not be started.
Recommended Action Verify the amount of memory installed on the channel adapter and upgrade if necessary.
Error Message%MSG802-3-QUEUE_OPEN : [chars] ([chars])
Explanation The LLC task has detected a queue-open failure. The resource may not be available for this request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-3-RESOURCE_DEPLETED : [chars] ([chars])
Explanation The protocol stack has encountered error conditions that prevent it from continuing its normal operations. Possible errors include resource depletion.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-6-SHRINK_CONN : reducing max_conn doesn't take effect until the virtual interface is restarted - max conn remain at [dec]
Explanation An attempt has been made to reduce the maximum connection limit. This release of Cisco IOS software does not allow you to reduce the maximum connection limit.
Recommended Action No action is required.
Error Message%MSG802-6-SHUT_IN_PROG : shutdown in progress ... [chars] command rejected
Explanation The LLC has entered a shutdown cleanup state. All configuration commands will be rejected.
Recommended Action Retry the command when the LLC has returned to an operational state.
Error Message%MSG802-6-START802_FAILED : unable to start 802 for [dec] connections - Memory Avail = [dec] bytes ([chars])
Explanation The CIP cannot bring up the CTA 802 task because of insufficient memory.
Recommended Action Check the maximum number of connections configured to see if CIP is overconfigured. If the Multipath is not overconfigured, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-6-THRESHOLD : Connection threshold is set to accept maximum [dec] connections
Explanation The CSNA is currently configured to accept the maximum number of connections per user command.
Recommended Action No action is required.
Error Message%MSG802-3-UNKNOWN_EVENT : detect unknown event; event=[dec]
Explanation The LLC task has detected an unknown event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSG802-3-UNSUPPORTED : [chars] ([chars])
Explanation The LLC task has detected a request for an unsupported function. The request will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
MSPI Messages
The following are Mail Service Provider messages.
Error Message%MSPI-1-MSPI_BAD_CONFIG : MSPI-bad configuration, [chars]
Explanation A configuration error has been detected.
Recommended Action Add or fix the dial peer configuration.
Error Message%MSPI-2-MSPI_BAD_CONTEXT : MSPI-bad context pointer, [chars]
Explanation A bad context pointer was passed.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSPI-4-MSPI_BAD_MESSAGE : MSPI- Bad message received
Explanation An unexpected message has been received.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSPI-2-MSPI_INTERNAL_ERROR : MSPI-Internal software error, cid=[dec], [chars]
Explanation An internal software error occurred. This condition might occur when the Cisco IOS software encountered any null pointer, invalid state or event, or other failed operation.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MSPI-4-MSPI_NO_SMTP : MSPI- Can't connect to the SMTP server, cid=[dec], [chars]
Explanation No connection was created to the specified SMTP server.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show call active voice, show call active fax, show call history voice, show call history fax, debug mspi send, debug mspi receive and debug fax mspi all commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MSPI-4-MSPI_NO_SMTP_SEND : MSPI- Could not \n send data to the SMTP server, cid=[dec], [chars]
Explanation A connection was made to the SMTP server, but no data could be sent to the SMTP server.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show call active voice, show call active fax, show call history voice, show call history fax, debug mta send all, debug mta receive all and debug fax mta all commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MSPI-1-NOMEMORY : Unit [dec], 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%MSPI-4-SMTP_NOT_CONNECTED : SMTP- failed [chars], [dec]
Explanation An attempt to connect to a remote mail server was not successful. This is unexpected behavior.
Recommended Action No action is required.
Error Message%MSPI-6-SMTP_OPEN : SMTP- opening [chars], [dec]
Explanation A connection is being attempted.
Recommended Action No action is required.
MUESLIX Messages
The following are Mx serial application-specific integrated circuit (ASIC) messages.
Error Message%MUESLIX-1-CLOCKRATE : [chars]:Link is brought [chars] due to clock rate change, threshold configured = [int], received clock rate = [int]
Explanation The received clock rate has been changed from below the configured threshold to above, or the received clock rate has been changed from above the configured threshold to below.
Recommended Action If the clock rate falls below the configured threshold, check the received clock rate from the provider end.
Error Message%MUESLIX-4-DEF_SUBRATE : [chars] [chars]
Explanation A user has changed the DSU bandwidth by using DS3 remote management commands. This action did 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, contact 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 system was not able to recognize all the Mueslix devices that are present on the system.
Recommended Action Attempt to reseat the PA properly in the system slots. If this error recurs, verify for the hardware failure including the Cisco 7200 chassis if the failure occurred with the 7200, the VIP if the failure occurred with the RSP, and the PA. This error will occur only if there is a hardware failure.
Error Message%MUESLIX-1-DWNLDFL : Mx serial (bay [dec]): PA down load failed
Explanation The Mx serial hardware has failed and could not download its operational microcode.
Recommended Action Attempt to reseat the PA properly in the system slots. If this error recurs, verify for the hardware failure including the Cisco 7200 chassis if the failure occurred with the 7200, the VIP if the failure occurred with the RSP, and the PA. This error will occur only if there is a hardware failure.
Error Message%MUESLIX-1-FAILURE_CAUSE : [chars]: [chars][chars]: [hex], [hex]
Explanation This message provides further information on what caused the problem with restarting (STARTFAIL) or stopping (STOPFAIL) the serial interface.
Recommended Action Extract the information from the port adapter to determine which error caused the problem with restarting or stopping the serial interface. Enter the debug serial mueslix command. Enter the show tech-support and show tech-support and show log commands. Contact your Cisco technical support representative and provide the representative with the gathered information. Disable the debug serial mueslix command after the information has been gathered.
Error Message%MUESLIX-1-HALT : Mx serial: [chars] TPU halted: cause [hex] status [hex] shadow [hex]
Explanation The Mx serial firmware is not in synchronization with the driver.
Recommended Action This condition will clear by itself. Enter the debug serial mueslix command. Enter the show tech-support and show log commands. Contact your Cisco technical support representative and provide the representative with the gathered information. Disable the debug serial mueslix command after the information has been gathered.
Error Message%MUESLIX-1-INITFAIL : Mx serial (bay [dec]), Init Failed at [chars]
Explanation The Mx serial port adapter has failed to complete its hardware initialization.
Recommended Action Attempt to reseat the PA properly in the system slots. If this error recurs, verify for the hardware failure including the 7200 chassis if the failure occurred with the 7200, the VIP if the failure occurred with the RSP, and the PA, as this error will occur only if there is a hardware failure.
Error Message%MUESLIX-3-NOTMUESLIX : Mx serial (bay [dec]): Device reported [hex]
Explanation The system hardware has failed. A non-Mx serial device pointed at the Mx serial software.
Recommended Action Check the system configuration for the failure in the bay number that is reported in the error message. If the device is not a Mueslix-based PA, contact the appropriate component to which that PA belongs. If the device is a Mueslix-based PA, then attempt to reseat the PA. If this message recurs, enter the show tech-support and show log commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MUESLIX-3-OWNERR : [dec] packet buffer, pak=[hex]
Explanation A software or hardware error occurred. The Mx serial driver detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Enter the debug serial mueslix command. Enter the show tech-support and show log commands. Contact your Cisco technical support representative and provide the representative with the gathered information. Disable the debug serial mueslix command after the information has been gathered.
Error Message%MUESLIX-1-STARTFAIL : Mx serial, [chars] Start Failed at [chars]
Explanation A software or hardware error occurred. The Mx microcode is not responding to the enable command that was used to restart the serial interface.
Recommended Action Enter the debug serial mueslix command. Enter the show tech-support and show log commands. Contact your Cisco technical support representative and provide the representative with the gathered information. Disable the debug serial mueslix command after the information has been gathered.
Error Message%MUESLIX-1-STOPFAIL : Mx serial, [chars] Stop Failed at [chars]
Explanation A software or hardware error has occurred. The Mx microcode is not responding to the disable command that was used to stop the serial port.
Recommended Action Enter the debug serial mueslix command. Enter the show tech-support and show log commands. Contact your Cisco technical support representative and provide the representative with the gathered information. Disable the debug serial mueslix command after the information has been gathered.
MXT_FREEDM Messages
The following are 8PRI/4T board messages.
Error Message%MXT_FREEDM-1-DWNLDFL : 8PRI/4T board slot [dec]: Firmware download failed.
Explanation An attempt to download firmware into an 8PRI/4T board has failed.
Recommended Action Power-cycle the router. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MXT_FREEDM-1-INVALID_SHMEM : Invalid Shared Memory size detected
Explanation The current shared memory present in the box is not supported.
Recommended Action Replace the shared memory with the supported configuration. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%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, contact your Cisco technical support representative, and provide the representative with the gathered information.
NATMIB_HELPER Messages
The following are NAT MIB helper messages.
Error Message%NATMIB_HELPER-3-NOCREAT : NATMIB Helper Process not created - NAT MIB will not work properly
Explanation An attempt to start the NAT MIB helper process failed when the NAT MIB subsystem was initialized. The NAT MIB helper process was not created. A possible reason for this condition is a lack of memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Reload the router after reconfiguring.
NBAR Messages
The following are network-based application recognition (NBAR) messages.
Error Message%NBAR-2-HEURISTIC_XDR_FAILED : Failure in the heuristic subsystem of NBAR: [chars]
Explanation The system failed to distribute NBAR heuristic data structures from the route processor to the line cards.
Recommended Action Disable heuristic protocols on the distributed platforms.
Error Message%NBAR-1-LINKNEXTCORRUPTED : link->next not NULL when allocated. link->next = [chars]\n
Explanation An attempt was made to get a link from the free bucket, which is pointing to another resource. Links within the free bucket should be NULL; therefore, this condition indicates that the link is corrupted and should not be used.
Recommended Action Configure the router by entering the ip nbar resources command to allocate a larger initial pool of resources.
Error Message%NBAR-1-LINKPREVCORRUPTED : link->prev not NULL when allocated. link->prev = [chars]\n
Explanation An attempt was made to get a link from the free bucket which is pointing to another resource. Links within the free bucket should be NULL; therefore, this condition indicates that the link is corrupted and should not be used.
Recommended Action Configure the router by entering the ip nbar resources command to allocate a larger initial pool of resources.
Error Message%NBAR-1-MAXMEMORYUSED : Reached maximum ammount of memory allocated for stile\n
Explanation This platform allows NBAR to use a limited amount of memory for classification. The memory allocated for NBAR has been exhausted because of high traffic conditions.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%NBAR-2-NOMEMORY : No memory available for [chars]
Explanation An attempt at memory allocation has failed.
Recommended Action Perform the following actions to remedy the problem: Disable some features. Apply filtering to decrease the size of system data structures, the routing table, for example. In general, reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%NBAR-2-NOSTATEMEM : Memory for maintaining state used up
Explanation NBAR uses memory to maintain state information about stateful flows. There is a maximum limit on how much memory NBAR can use for this purpose and the maximum limit has been reached.
Recommended Action Increase the memory on the platform.
Error Message%NBAR-2-RMINVALIDCONFIG : NBAR resource manager : too many buckets ([dec])
Explanation NBAR was configured so that the internal data structures needed to maintain stateful protocol information were too large.
Recommended Action Configure the router by entering the ip nbar resources command with a smaller maximum idle (max-idle) time.
Error Message%NBAR-2-RMNORESOURCE : NBAR resources exhausted
Explanation To save stateful information on protocols, NBAR must use dynamic resources. These resources have been exhausted.
Recommended Action Configure the router by entering the ip nbar resources command to allocate a larger initial pool of resources. The default number of initial resources is 10000. Also, try configuring a shorter maximum idle (max-idle) time.
NET_SERV Messages
The following are Network Services messages.
Error Message%NET_SERV-4-UNEXPECTED : Unexpected error: [chars]
Explanation An unexpected error has occurred while a services timer operation was performed.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NET_SERV-4-WARNING : Unexpected condition: [chars]
Explanation An unexpected condition has been detected while a services timer operation was performed.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
NETWORK_CLOCK_SYNCHRONIZATION Messages
The following are network clock synchronization messages.
Error Message%NETWORK_CLOCK_SYNCHRONIZATION-4-NETCLK_CHANGE : \nNetwork clock source transitioned from \nPriority [dec] [chars] [chars] to Priority [dec] [chars] [chars]\n
Explanation A change in the clock source has occurred.
Recommended Action No action is required.
Error Message%NETWORK_CLOCK_SYNCHRONIZATION-4-NETCLK_INIT : \nNetwork clock source initialised to local oscillator.\n
Explanation The network clock used will be internal.
Recommended Action No action is required.
Error Message%NETWORK_CLOCK_SYNCHRONIZATION-4-NETCLK_PLL_LOST_LOCK : \nNetwork clock [chars] PLL lost lock - clock source failed.\n
Explanation The clock source has failed.
Recommended Action If an alternate clock source is available, it will be used.
NEVADA Messages
The following CMCC messages are related to the Channel Interface Processor (CIP) interrupt controller.
Error Message%NEVADA-0-BADADD : Add: Invalid nevada interrupt code [dec]
Explanation An attempt was made to specify an interrupt handler for an invalid interrupt type on an interrupt control chip. A fatal internal logic error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NEVADA-0-BADDISABLE : Disable: Invalid nevada interrupt code [dec]
Explanation An attempt was made to disable an invalid interrupt type on an interrupt control chip. A fatal internal logic error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NEVADA-0-BADENABLE : Enable: Invalid nevada interrupt code [dec]
Explanation An attempt was made to enable an invalid interrupt type on an interrupt control chip. A fatal internal logic error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NEVADA-0-BADENABLE2 : Enable: No interrupt routine for code [dec]
Explanation An attempt was made to enable an interrupt routine on an interrupt control chip, but no interrupt routine was specified. A fatal internal logic error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NEVADA-0-BADINT : Interrupt received with no interrupt routine defined
Explanation An interrupt was received for a code with no interrupt handler defined. A fatal internal logic error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NEVADA-0-BADREMOVE : Remove: Invalid nevada interrupt code [dec]
Explanation An attempt was made to remove an interrupt handler for an invalid interrupt type on the an interrupt control chip. A fatal internal logic error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
NHRP Messages
The following are Next Hop Resolution Protocol (NHRP) messages.
Error Message%NHRP-3-PAKERROR : Receive [chars] for our [chars], code: [chars]([dec]), offset: [dec], data: [chars]
Explanation The system has received an error indication packet indicating that the system sent a bad packet prior to this message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NHRP-3-PAKREPLY : Receive [chars] packet with error - [chars]([dec])
Explanation An NHS has rejected or failed to serve the NHRP client request packet.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
NI2 Messages
The following are NI2 messages.
Error Message%NI2-3-BITS_FAILED : [chars] [chars] [chars] [chars] [chars]
Explanation The timing source that is used for timing bits has failed.
Recommended Action Determine the cause of the failure and correct the problem, is possible.
Error Message%NI2-3-CHASSIS : Motherboard EEPROM: Chassis model not found.
Explanation The data stored in the motherboard EEPROM is invalid or is incomplete.
Recommended Action Contact your Cisco technical support representative to update your system.
Error Message%NI2-3-CONFIG : Recommended port adapter configuration exceeded
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%NI2-4-COOKIE : Corrupt or missing MAC address cookie
using random base [enet]Explanation An invalid MAC address in the backplane EEPROM has been detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%NI2-1-DISCOVER_ENET : Failed to init Ethernet device [dec]
Explanation The software could not initialize.
Recommended Action Power down the system, reseat the interface card, and reboot the system. If the message recurs, If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%NI2-1-DISCOVER_SAR : Failed to init SAR device [dec]
Explanation The software could not initialize.
Recommended Action Power down the system, reseat the interface card, and reboot the system. If the message recurs, If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%NI2-2-FPGALOAD : FPGA download failure: [chars]
Explanation A broken motherboard or NVRAM contents has been detected.
Recommended Action Run diagnostics to attempt to diagnose the problem.
Error Message%NI2-3-IONOT0 : IO card discover in non-zero slot [dec]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%NI2-3-IPC : [chars]: IPC Failure
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%NI2-3-IPCOPENFAILED : Couldn't open IPC portfor port id [hex] slot [dec]: [chars]
Explanation Information could not be obtained from a line card.
Recommended Action Reseat the line card in the specified slot.
Error Message%NI2-1-LC_ALERT : [chars]
Explanation A line card log message has been received.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%NI2-2-LC_CRIT : [chars]
Explanation A line card log message has been received.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%NI2-7-LC_DEBUG : [chars]
Explanation A line card log message has been received.
Recommended Action No action is required.
Error Message%NI2-0-LC_EMERG : [chars]
Explanation A line card log message has been received.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%NI2-3-LC_ERR : [chars]
Explanation A line card log message has been received.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%NI2-6-LC_INFO : [chars]
Explanation A line card log message has been received.
Recommended Action No action is required.
Error Message%NI2-5-LC_NOTICE : [chars]
Explanation A line card log message has been received.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%NI2-3-LC_UNKNOWN : [chars]
Explanation A line card log message has been received.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%NI2-4-LC_WARN : [chars]
Explanation A line card log message has been received.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%NI2-3-LOSS_OF_SYNC : [chars] [chars] [chars] [chars] [chars]
Explanation The highest-configured priority clock has lost its synchronization or has failed.
Recommended Action Determine the cause of the failure and correct the problem.
Error Message%NI2-4-MACBLKSIZE : Unknown MAC address block size.
Explanation Data stored in the midplane is invalid or is incomplete.
Recommended Action Contact your Cisco technical support representative to update your system.
Error Message%NI2-3-NO_ATM_PHY : Unable to determine trunk PHY type.
Explanation Data stored in the motherboard EEPROM is invalid or is incomplete.
Recommended Action Contact your Cisco technical support representative to update your system.
Error Message%NI2-4-NOCPUVER : Invalid CPU ID, assuming revision 1
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%NI2-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation The MAC allocation limit has been exceeded.
Recommended Action Remove unnecessary interfaces.
Error Message%NI2-3-NOMEM : OUT of Memory: [chars]
Explanation A memory allocation failure has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%NI2-3-NOPORTINFO : Port info invalid for port [dec] slot [dec]: [chars]
Explanation Port details of the line card could not be accessed.
Recommended Action Reseat the line card. Reboot the chassis if this message recurs.
Error Message%NI2-3-NOPORTINFO_ID : Port info invalid for port id [hex] slot [dec]: [chars]
Explanation Memory could not be allocated for IPC data.
Recommended Action Reseat the line card. Reboot the chassis if this message recurs.
Error Message%NI2-3-NO_SERIAL : Backplane EEPROM: no chassis serial number.
Explanation Data stored in the backplane EEPROM is invalid or is incomplete.
Recommended Action Contact your Cisco technical support representative to update your system.
Error Message%NI2-1-NTC_IPC_DOWN : LOST IPC with DSL uplink:[chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%NI2-5-NTC_IPC_UP : Established IPC with DSL uplink:[chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%NI2-4-NTC_SLOT : DSL Alternate uplink [chars] Not Supported
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%NI2-4-PCIVALID : PCI activation failed, bay [dec], [hex]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%NI2-3-PROCESS_FAILED : [chars] [chars] [chars] [chars] [chars]
Explanation The redundancy process has failed. The system currently has no backup.
Recommended Action Reboot the unit on which the process failed.
Error Message%NI2-3-UNK_CHASSIS : Motherboard EEPROM: unknown chassis model [hex].
Explanation Data stored in the backplane EEPROM is invalid or is incomplete.
Recommended Action Contact your Cisco technical support representative to update your system.
NIM Messages
The following are network interface module (NIM) messages.
Error Message%NIM-2-BADNIMREV : Unsupported version of [chars] NIM in slot [dec] Version [hex]\n
Explanation The indicated NIM is not supported because it is not the correct revision. 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]\n
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NIM-2-BADSUBUNIT : Illegal reference to non-existent subunit [dec] in slot [dec]\n
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NIM-2-DEADICHAINQ : Attempted to manipulate uninitialized ichainQ in [chars]\n
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NIM-2-LOSTICHAINQ : Couldn't find idb [hex] in ichainQ in [chars]\n
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NIM-2-NOHWADDRESS : All hardware addresses have been allocated - maximum of [dec]\n
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NIM-2-UNSUPNIM : Unsupported [chars] NIM in slot [dec]\n
Explanation The indicated NIM is not supported on this platform.
Recommended Action Remove the NIM.
NP Messages
The following are NextPort (NP) messages.
Error Message%NP-3-CTRL_POOL_CREATION_FAIL : Control buffer pool could not be created
Explanation The NextPort driver could not create the control buffer pool required for Tx and Rx of NextPort control messages
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP-3-MODNOTEXIST : Slot [dec], DFC [dec], Module [dec] not exist.
Explanation No virtual console can be opened for this module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP-3-NAKRSP : NAK Response Received - command [hex], result code [hex], msg id [hex], session id [hex], msg tag [hex], slot/port [dec]/[dec]
Explanation A NAK response was sent by the NextPort module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP-3-NOTMSGID : Message Id [hex] not supported.
Explanation The NextPort module does not support this control message ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP-3-NULL_PTR : [chars] is NULL in [chars] for port [dec]
Explanation An unexpected null pointer is in the location specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP-3-QUEUEFULL : [chars] queue is full for Slot [dec], DFC [dec], Module [dec].
Explanation The Tx queue is full for this module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP-3-RESET_DFC : DFC Reset-Cleared Failed - DFC [dec]
Explanation The DFC could not be reset and cleared.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
NP_BS Messages
The following are NextPort (NP) BootStrap and Crash Monitor messages.
Error Message%NP_BS-3-CRC_FAIL : NextPort Module [dec]/[dec]/[dec] failed firmware image validation
Explanation The NextPort BootStrap and Crash Monitor has detected a failed NextPort firmware CRC validation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_BS-6-FW_DNLD_IN_PROGRESS : Module FW Download [dec]/[dec]/[dec] spe [dec] is in [chars] state
Explanation The NextPort module firmware download is in a Progress state.
Recommended Action No action is required.
Error Message%NP_BS-2-HYBRID_CARD_INVALID_DFC_CONFIG : Feature board in slot [dec] does not have valid DFCs!
Explanation The feature board does not have valid DFCs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_BS-3-INITSYS : [chars]
Explanation The NextPort BootStrap and Crash Monitor has failed to initialize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_BS-3-INVALID_FW : Invalid NextPort Firmware for [dec]/[dec]/[dec]
Explanation The NextPort BootStrap and Crash Monitor has detected invalid NextPort firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_BS-3-INVALID_IDT : NextPort Module [dec]/[dec]/[dec] detected an invalid IDT
Explanation NextPort BootStrap and Crash Monitor has detected an invalid IDT.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_BS-3-INVALID_MC_POST : NextPort Module [dec]/[dec]/[dec] detected a module POST failure [hex]
Explanation The NextPort BootStrap and Crash Monitor has detected a module POST failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_BS-3-MEM_TEST_FAIL : NextPort Module [dec]/[dec]/[dec] memory test failed
Explanation The NextPort BootStrap and Crash Monitor has detected a failed NextPort module memory test.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_BS-3-MODULE_ACCESS_ERR : Failed to access NextPort module [dec]/[dec]/[dec] crash info
Explanation The NextPort BootStrap and Crash Monitor has failed to access crash information.
Recommended Action No action is required.
Error Message%NP_BS-6-MODULE_FW_DNLD : Module FW Download [chars] to NextPort module [dec]/[dec]/[dec]
Explanation The NextPort module firmware is being downloaded from Flash memory.
Recommended Action No action is required.
Error Message%NP_BS-6-MODULE_STARTED : NextPort module [dec]/[dec]/[dec] Started - [dec].[dec].[dec].[dec]
Explanation The NextPort BootStrap and Crash Monitor has successfully started a module.
Recommended Action No action is required.
Error Message%NP_BS-6-MODULE_STOPPED : NextPort module [dec]/[dec]/[dec] Stopped
Explanation The NextPort BootStrap and Crash Monitor has stopped a module.
Recommended Action No action is required.
Error Message%NP_BS-3-NO_KEEPALIVE : NextPort module [dec]/[dec]/[dec] failed to respond to keepalive message
Explanation The NextPort BootStrap and Crash Monitor has detected a module that has failed to respond to a keepalive message.
Recommended Action No action is required.
Error Message%NP_BS-3-NOMEM : [chars]
Explanation The NextPort BootStrap and Crash Monitor could not allocate memory for the internal module database.
Recommended Action No action is required.
Error Message%NP_BS-3-NO_SUCH_MODULE : [chars] nonexisting NP module [dec]/[dec]/[dec]
Explanation The NextPort BootStrap and Crash Monitor has detected an internal database error.
Recommended Action No action is required.
Error Message%NP_BS-3-NULL_FW_PTR : NULL NextPort Firmware pointer for [dec]/[dec]/[dec]
Explanation The NextPort BootStrap and Crash Monitor has detected a null NextPort firmware pointer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_BS-3-Q_FAILURE : NextPort Module [dec]/[dec]/[dec] control queue creation failure
Explanation The NextPort BootStrap and Crash Monitor has detected a control queue creation failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_BS-2-THREE_NP108_NOT_PRESENT : Feature Board in slot [dec] does not have three NP108s!
Explanation The feature board does not have three NP108s. A correct configuration has three NP108s.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
NP_DDSM Messages
The following are NextPort Digital Data Services Manager messages.
Error Message%NP_DDSM-3-DIAL_STRING_TOO_LONG : [dec]/[dec]:DIGITAL_DIALSTRING_NTF string too long, len=[dec]
Explanation The NextPort Digital Data Services Manager received a dial string that was too long.
Recommended Action No action is required.
Error Message%NP_DDSM-3-INVALID_CALL_TYPE : Invalid call type from DIGITAL_GET_LLC_CMD : [hex]
Explanation The specified outgoing call type is unsupported.
Recommended Action No action is required.
Error Message%NP_DDSM-3-UNSUPPORTED_CALL_TYPE : Call type is either not set or not supported
Explanation The digital data call type is either not set or not supported
Recommended Action Copy the error message exactly as it appears on the console or in the system log and give it to your Cisco technical support representative.
Error Message%NP_DDSM-3-UNSUPPORTED_REVERSE_TELNET_CALL : HDLC digital call dial-out through reverse telnet is not supported
Explanation The NextPort Digital Data Service Manager does not support outgoing HDLC digital calls through reverse Telnet.
Recommended Action No action is required.
NP_DSPLIB Messages
The following are NextPort DSPLIB messages.
Error Message%NP_DSPLIB-3-INVALID_STATE : Invalid NP DSPLIB state ([dec]) at [chars] for port ([dec]/[dec])
Explanation The NextPort DSPLIB is in an invalid state at this time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
NP_EST Messages
The following are NextPort messages.
Error Message%NP_EST-6-CTRL_NAK_RSP : [chars]
Explanation An EST Control NAK Notification has been sent to the Cisco IOS software to convey additional debug data regarding a NAK that occurred on the Control Queue.
Recommended Action No action is required.
Error Message%NP_EST-6-DIAG_POST_NTF : [chars]
Explanation EST Diagnostic and POST Notification has been sent to the Cisco IOS software to convey additional information about the power-on self-test or a diagnostic test result.
Recommended Action No action is required.
Error Message%NP_EST-3-MSG_ERR : [chars]
Explanation EST has detected an internal error.
Recommended Action No action is required.
Error Message%NP_EST-6-RUNTIME_ERR_NTF : [chars]
Explanation An EST runtime error notification has been sent to the Cisco IOS software to convey additional debug data that may help identify the cause of the error.
Recommended Action No action is required.
NP_MD Messages
The following are NextPort modem driver messages.
Error Message%NP_MD-3-BADENCAP : Unknown encapsulation [dec] on interface [chars]
Explanation A software error, which resulted in an unknown encapsulation type on the specified interface, has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-CONTIGUOUS : Contiguous packet sent for transmit
Explanation A software error, which resulted in an unexpected packet being set up for transmission, has occurred, and the packet was dropped by the NextPort Modem Driver.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-DATA_CHAN_RX_OVERFLOW : Too many buffers ([dec]) rxd for port [dec]
Explanation The NextPort module has sent more buffers than is allowed for this channel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-DATA_QUEUE_SEND_FAIL : Could not send to data queue for port [dec], inflight tx buffers [dec]
Explanation The NextPort Modem Driver could not send a buffer to interface driver.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-MODEM_SLOT_CREATION_FAIL : Modem slot structure for slot [dec] could not be created
Explanation The NextPort modem driver could not create the modem slot structure that is required for the modem services of this card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-6-MODULE_DOWN : NextPort module [dec]/[dec]/[dec] down
Explanation The NextPort Modem Driver has detected that a module is going down.
Recommended Action No action is required.
Error Message%NP_MD-6-MODULE_UP : NextPort module [dec]/[dec]/[dec] up
Explanation The NextPort Modem Driver has detected that a module is coming up.
Recommended Action No action is required.
Error Message%NP_MD-0-NOHWIDBS : Cannot allocate interface Async[dec]/[dec]
Explanation The allocation of interface structure has failed. Either there is not enough memory or the maximum number of interfaces has been exceeded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-0-NOMEMORY : Cannot allocate [dec] bytes of memory for [chars]
Explanation The system has failed to allocate an important data structure because of a lack of memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show mem command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show mem command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NP_MD-0-NO_MODULE_ELEMENTS : Cannot bring up the module [dec]/[dec]/[dec] due to lack of module elements
Explanation The NextPort modem driver cannot allocate an important data structure, called a module element, which is necessary to bring up the module. This condition should not normally happen and possibly indicates an error condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-0-NOPAKS : TTY [chars]: Cannot allocate [chars]
Explanation An important buffer cannot be allocated because of the packet memory shortage.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-NO_SEED_BUFFER : No buffer to seed data queue for module [dec]/[dec]/[dec]
Explanation The NextPort Modem Driver could not obtain a buffer to seed the module data queue because of a packet memory shortage.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-0-NO_SUCH_LINE : Attempt to [chars] a data channel on the unexisting line [dec]/[dec]
Explanation An internal software error has occurred that may have corrupted the modem database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-0-NO_SUCH_MODEM : Attempt to [chars] a data channel on the unexisting modem [dec]/[dec]
Explanation An internal software error has occurred that may have corrupted the modem database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-0-NO_SUCH_SLOT : Slot [dec] is not present in the system
Explanation An internal software error has occurred that may have corrupted the slot database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-0-NOTTYS : Cannot allocate TTY[dec] ([dec]/[dec])
Explanation The allocation of the tty structure has failed. Either there is not enough memory or the tty number is too big.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-NOTXPAK : Static transmit paktype unavailable
Explanation A software structure was found in an unexpected state during runtime for the specified modem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-NP_PROC_CHUNK : [chars]
Explanation The system failed to create the queue chunk for the NextPort module-up process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-NPMODULEPROC : [chars]
Explanation The system failed to create the NextPort module-up process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-NPMODULEQ : [chars]
Explanation The system failed to create the watched queue for the NextPort module-up process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-NPMODULESTRUCT : [chars]
Explanation The system failed to allocate chunk memory for the NextPort module, or the system failed to allocate memory for the watched queue entry for the process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-NULL_PTR : [chars] is NULL in [chars] for port [dec]
Explanation There is an unexpected null pointer at the specified location.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-RETURN_DATA_BUFF_FAIL : Failed to return data buffer for port [dec]
Explanation A call to the NextPort interface driver to replenish the data buffer for the specified channel has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-RTSLOW : TTY [chars]: RTS is incorrectly deasserted; reasserting now
Explanation A software error has occurred that resulted in an invalid state for the RTS modem signal.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-SEED_BUFFER_FAIL : Could not seed data queue for module [dec]/[dec]/[dec]
Explanation The NextPort modem driver could not seed the data queue with buffers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-0-SLOT_ALREADY_PRESENT : Slot [dec] is already present in the system
Explanation An internal software error has occurred that may have resulted in a corrupted slot database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-6-SLOT_INSERTED : Slot [dec] ([dec] ports max) inserted
Explanation The NextPort modem driver has detected a slot that is inserted in the system. All slots that are present in the system are treated as being inserted during startup.
Recommended Action No action is required.
Error Message%NP_MD-6-SLOT_REMOVED : Slot [dec] removed
Explanation A slot has been removed from the system.
Recommended Action No action is required.
Error Message%NP_MD-3-TX_INBAND_MSG_FAILURE : Failed to send inband message for port [chars] ([chars])
Explanation A call to a send inband message on the data queue has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-TXQUEUE_EMPTY : TTY [chars]: No buffers available to set up the transmit queue
Explanation A software error has occurred that resulted in an unexpected exhaustion of the pool of data buffers that are used by the modem drivers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-1-UNKNOWN_ESCAPE_CHAR : TTY [chars]: Attempt to set an unknown special character (type [dec]) to [hex]
Explanation The NextPort modem driver has received a request for hardware detection of an unknown type of special character because of an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MD-3-UNKNOWN_INBAND : TTY [chars]: Unknown NextPort in-band message (msg_id [hex]) received
Explanation The NextPort modem driver has received an unknown message from a NextPort module. This can happen if new firmware is used with an obsolete version of Cisco IOS software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
NP_MM Messages
The following are NextPort module manager messages.
Error Message%NP_MM-3-COUNTRY_CODE_FAILURE : Module country code failure [dec]/[dec]/[dec]
Explanation The NextPort module manager has failed to set the country code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MM-3-DATA_Q_FAILED : Failed to create Data Q [dec] for NP module [dec]/[dec]/[dec]
Explanation The NextPort module manager has failed to create a data queue.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MM-3-INVALID_ACK_RSP : Unsupported module ACK response [dec]/[dec]/[dec]: msg len = [dec], session ID = [dec], msg tag = [dec], msg ID = [dec], cmd msg ID = [dec], result code = [dec]
Explanation The NextPort module manager has received an unsupported message response.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MM-3-INVALID_NPADDRESS : Invalid NP_ADDRESS [dec]/[dec]/[dec]/[dec] - [chars]
Explanation The NextPort module manager has detected an invalid NextPort address (NP_ADDRESS).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MM-3-INVALID_RSP : Unsupported module response [dec]/[dec]/[dec]: msg len = [dec], session ID = [dec] msg tag = [dec], msg ID = [dec]
Explanation The NextPort module manager has received an unsupported message response.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MM-3-INVALID_STATE : Invalid NP module state([chars]) [dec]/[dec]/[dec] - [chars]
Explanation The NextPort module manager has detected an invalid NP module state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MM-3-MEM_ERR : Failed to allocate control message buffer for NP module [dec]/[dec]/[dec] - [chars]
Explanation The NextPort module manager has failed to allocate a control message buffer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MM-3-MODULE_CRASH : Module Crash detected [dec]/[dec]/[dec]: state = [dec], cause code = [dec]
Explanation The NextPort module manager has detected a crashed module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MM-3-RESTART_EXCEEDED : Module exceeded restart threshold [dec]/[dec]/[dec]
Explanation The NextPort module manager has detected a module that has exceeded the restart threshold.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MM-3-RUNTIME_ERR : Module Run Time Error [dec]/[dec]/[dec] : recovery = [hex], error = [hex]
Explanation The NextPort module manager has received a module run-time error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_MM-3-SEND_FAILED : Failed to send [chars] message to NP module [dec]/[dec]/[dec]
Explanation The NextPort module manager has failed to send a control message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
NP_SIGLIB Messages
The following are NextPort Signaling Library messages.
Error Message%NP_SIGLIB-3-CPTONE_FORMAT_FAIL : Format of cp tone failed for tone-id [dec], port [dec]/[dec]
Explanation Formatting the call processing tone message to the NextPort module has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
NP_SPE_DS Messages
The following are NextPort Dial Shelf Service Processing Element (SPE) Manager messages.
Error Message%NP_SPE_DS-3-NOMEMORY : Cannot allocate [dec] bytes of memory for [chars]
Explanation The system has failed to allocate an important data structure because of a lack of memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show mem command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show mem command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NP_SPE_DS-3-SPE_DNLD_FAIL : SPE [dec]/[dec]/[dec]/[dec]: [chars]
Explanation The SPE download code has failed, and the download has been aborted.
Recommended Action No action is required.
Error Message%NP_SPE_DS-3-SPE_DNLD_INIT_FAIL : [chars]
Explanation The SPE download code has failed to initialize, and the SPE download will fail.
Recommended Action No action is required.
NP_SSM Messages
The following are NextPort Session and Service Manager messages.
Error Message%NP_SSM-3-INVALID_HANDLE : SSM([dec]/[dec]): Invalid Session/Service Instance Handle
Explanation Session and Service Manager Received has failed to obtain its instance handle for the slot and port.
Recommended Action No action is required.
Error Message%NP_SSM-3-INVALID_MSG : SSM: Invalid Session/Service Message, ID = [hex]
Explanation The Session and Service Manager has received an invalid message from the NextPort Message Dispatcher.
Recommended Action No action is required.
Error Message%NP_SSM-0-NOMEMORY : Cannot allocate [dec] bytes of memory for [chars]
Explanation The system failed to allocate an important data structure because of a lack of memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show mem command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show mem command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NP_SSM-6-NULL_SSM_INFO : NULL SSM Info Handle for slot [dec], port [dec]
Explanation The NextPort Session and Service Manager has failed to obtain a control information handle for the specified slot and port numbers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_SSM-6-NULL_VDEV_COMMON : NULL Vdev Common Handle for slot [dec], port [dec]
Explanation The NextPort Session and Service Manager has failed to obtain a voice device information handle for the specified slot and port numbers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_SSM-3-RUNTIME_ERROR : SSM([dec]/[dec]): Session Runtime Error Code = [dec], Recovery Action = [dec]
Explanation The NextPort Session and Service Manager has received a run-time error for the slot and port.
Recommended Action No action is required.
NP_VPD Messages
The following are NextPort Voice Packet Driver messages.
Error Message%NP_VPD-3-BADENCAP : Unknown encapsulation [dec] on interface [chars]
Explanation A software error resulted in an unknown encapsulation type on the interface specified by the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-6-BUFFER_SHORTAGE : Buffer shortages for [dec] voice ports during Nextport module bring-up
Explanation The NextPort Voice Packet driver has detected a buffer shortage when the module was brought up.
Recommended Action No action is required.
Error Message%NP_VPD-3-CONTIGUOUS : Contiguous packet sent for transmit
Explanation A software error resulted in an unexpected packet being set up for transmission. The packet was dropped by the NextPort Voice Packet driver.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-3-DATA_CHAN_RX_OVERFLOW : Too many buffers ([dec]) rxd for port [dec]
Explanation The NextPort Module has sent more buffers than is allowed for this channel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-3-DATA_QUEUE_SEND_FAIL : Could not send to data queue for port [dec], inflight tx buffers [dec]
Explanation The NextPort Voice Packet driver could not send a buffer to the interface driver.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-3-FAIL_ALLOC_VC_TBL : Failed to allocate vchan instance \n table for slot [dec]
Explanation The RSC has failed to allocate a VCHAN instance table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-3-FIRST_DEV_RANGE : First device [dec] is out of range
Explanation The first device is out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-6-MODULE_DOWN : NextPort module [dec]/[dec]/[dec] down
Explanation The NextPort Voice Packet driver has detected a module that failed.
Recommended Action No action is required.
Error Message%NP_VPD-6-MODULE_UP : NextPort module [dec]/[dec]/[dec] up
Explanation The NextPort Voice Packet driver has detected a module that has become available.
Recommended Action No action is required.
Error Message%NP_VPD-0-NOHWIDBS : Cannont create hwidb for slot [dec]
Explanation The allocation of an interface structure has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-0-NOMEMORY : Cannot allocate [dec] bytes of memory for [chars]
Explanation The system has failed to allocate an important data structure because of a lack of memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show mem command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show mem command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NP_VPD-0-NO_MODULE_ELEMENTS : Cannot bring up the module [dec]/[dec]/[dec] due to lack of module elements
Explanation The NextPort Voice Packet driver cannot allocate an important data structure, which is called the module element. The module element is necessary to bring up the module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-3-NORXPAK : Static receive paktype unavailable
Explanation NextPort was unable to allocate a packet type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-3-NO_SEED_BUFFER : No buffer to seed data queue for module [dec]/[dec]/[dec]
Explanation Because of a shortage of packet memory, the NextPort Voice Packet driver could not obtain a buffer while it tried to seed the module data queue.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-0-NO_SUCH_LINE : Attempt to [chars] a data channel on the unexisting line [dec]/[dec]
Explanation An internal software error has occurred that probably resulted in a corrupted voice database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-0-NO_SUCH_SLOT : Slot [dec] is not present in the system
Explanation An internal software error has occurred that possibly resulted in a corrupted slot database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-0-NO_SUCH_VOICE_PORT : Attempt to [chars] a data channel on the unexisting voice port [dec]/[dec]
Explanation An internal software error has occurred that probably resulted in a corrupted voice database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-3-NOTXPAK : Static transmit paktype unavailable
Explanation A software structure was found in an unexpected state during run time for the indicated modem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-3-RETURN_DATA_BUFF_FAIL : Failed to return data buffer for port [dec]
Explanation A call to the NextPort Interface driver to replenish the data buffer for this channel has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-3-SEED_BUFFER_FAIL : Could not seed data queue for module [dec]/[dec]/[dec]
Explanation The NextPort Voice Packet driver could not seed the data queue with buffers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-0-SLOT_ALREADY_PRESENT : Slot [dec] is already present in the system
Explanation An internal software error has occurred that possibly resulted in a corrupted slot database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-6-SLOT_INSERTED : Slot [dec] ([dec] ports max) inserted
Explanation The NextPort Voice Packet driver has detected a slot that is being inserted in the system. All slots that are present are treated as if they are being inserted in the system during the startup procedure.
Recommended Action No action is required.
Error Message%NP_VPD-6-SLOT_REMOVED : Slot [dec] removed
Explanation A slot has been removed from the system.
Recommended Action No action is required.
Error Message%NP_VPD-3-TXQUEUE_EMPTY : TTY [chars]: No buffers available to set up the transmit queue
Explanation A software error has occurred that resulted in an unexpected exhaustion of the pool of data buffers used by the NextPort Voice Packet drivers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VPD-3-VPD_POOL_CREATE_FAIL : Failed to create particle pool
Explanation NextPort failed to create a particle pool.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
NP_VSM Messages
The following are NextPort Voice Service Manager (VSM) messages.
Error Message%NP_VSM-4-INVALID_COMBINATION : Invalid combination - [chars]
Explanation The system has encountered an invalid combination of parameters.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VSM-3-INVALID_STATE_NTF : NP-VSM([dec]/[dec]): Invalid State Notification Received service [hex]
Explanation The NextPort VSM received an SSM state notification, which it is not supposed to receive, on the specified slot and port.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VSM-3-MALLOC_FAILURE : No memory is available to build session information for slot [dec]
Explanation The NextPort VSM does not have sufficient memory available to build some internal data structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VSM-3-OUT_OF_RANGE_VALUE : [chars] value:[dec] is out of range
Explanation The NextPort VSM has received an invalid or out-of-range value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NP_VSM-3-PROT_VIOLATION : [chars] Protocol Violation received on slot [dec] port [dec]
Explanation The NextPort VSM has received a protocol violation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
NRP Messages
The following are Network Routing Processor (NRP) messages.
Error Message%NRP-3-IPC : [chars] [chars]
Explanation An 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. Copy down the configuration of the router along with any other relevant information and contact your Cisco technical support representative for assistance.
NRP2 Messages
The following are Network Route Processor, type 2 messages.
Error Message%NRP2-1-INITFAILED : I82543([dec]/[dec]), initialization failed
Explanation NRP2 GE interface initialization has failed. The reason for this failure is unknown.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2-2-INTBEFOREINIT : Attempt to enable/disable [chars] interface interrupts before initialization complete
Explanation The interrupt code has detected an error in the initialization of the interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NRP2-2-RESET_FAILED : PCI device reset failed to complete - reloading
Explanation The PCI device reset transition has failed to complete in the expected time. This condition indicates a fatal hardware error condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NRP2-2-RESET_STUCK : PCI device reset done bit stuck - reloading
Explanation The PCI device "reset done" bit was asserted before a reset was started. This condition indicates a fatal hardware error condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NRP2-4-SLAVE_DOWN : NRP2-REDUNDANCY Secondary NRP2 in slot [dec], went down.
Explanation The primary NRP2 lost communication with the redundant NRP2.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NRP2-5-SLAVE_UP : NRP2-REDUNDANCY Secondary NRP2 in slot [dec], came up
Explanation The redundant NRP2 came up and established communication with the primary NRP2.
Recommended Action No action is required.
NRP2_NVMANAGE Messages
The following are Network Route Processor, type 2 NVRAM management messages.
Error Message%NRP2_NVMANAGE-4-FILE_OPEN_RD_ERROR : NRP2 slot [dec]/[dec] unable to open file [chars] for reading
Explanation The NRP-2 specified in the error message is unable to locate an NVRAM image. Most likely, the specified image is not present or this is the first time an NRP-2 has been installed in this slot. The NRP-2 NVRAM will revert to its default values.
Recommended Action Verify that there is a functioning disk in the NSP.
Error Message%NRP2_NVMANAGE-4-FILE_OPEN_WR_ERROR : NRP2 slot [dec]/[dec], unable to open file [chars] for writing
Explanation The identified NRP-2 is unable to write an NVRAM image. Most likely, the NSP disk is either not present or too full to allow writing this file. Changes to the NRP-2 NVRAM parameters will not be saved.
Recommended Action Verify that there is a functioning disk in the NSP and remove any unneeded files.
Error Message%NRP2_NVMANAGE-4-FILE_READ_ERROR : NRP2 slot [dec]/[dec], error while reading file [chars]
Explanation The identified NRP-2 is unable to read its NVRAM image. NRP-2 NVRAM will revert to its default values.
Recommended Action Verify that there is a functioning disk in the NSP.
Error Message%NRP2_NVMANAGE-4-FILE_WRITE_ERROR : NRP2 slot [dec]/[dec], error while writing file [chars]
Explanation NRP-2 NVRAM data is stored on local NSP disk space. The NRP2 specified in the error message did not have its NVRAM saved to disk because of a file error. Changes to the NRP-2 NVRAM parameters will not be saved.
Recommended Action Verify that there is a functioning disk in the NSP and remove any unneeded files.
Error Message%NRP2_NVMANAGE-4-NO_RD_MEMORY : NRP2 slot [dec]/[dec], unable to allocate memory while reading file [chars]
Explanation The specified NRP-2 did not have its NVRAM initialized because the system ran out of memory during the read operation. NRP-2 NVRAM will revert to its default values.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_NVMANAGE-4-NO_WR_MEMORY : NRP2 slot [dec]/[dec], unable to allocate enough memory while writing file [chars]
Explanation NRP-2 NVRAM data is stored on local NSP disk space. The NRP-2 specified in the error message did not have its NVRAM saved to disk because the system ran out of memory during the write operation. Changes to the NRP-2 NVRAM parameters will not be saved.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
NRP2_SE64 Messages
The following are upper- and lower-layer device driver messages for the NRP-2 ATM SAR.
Error Message%NRP2_SE64-3-LLD_BAD_BCS : The BCS [dec] out of rang ([dec], [dec])
Explanation The VBR BCS is out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_BAD_MPH_COUNT : Inconsistent mp holder count: [dec] [dec]
Explanation The MP holder count is too large.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_BAD_MPH_DESTROY : mp holder destroy count incorrect: [dec] [dec] [dec]
Explanation The MP holder destroy count is incorrect.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_BAD_PCR : The PCR [dec] larger than [dec]
Explanation The VBR PCR is out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_BAD_RX_POOL_SIZE : Rx pool size [int], too big
Explanation The requested Rx pool size is greater than 32K.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_BAD_RX_RANGE : Particle out of boundary
Explanation An SAR particle is out of boundary.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_BAD_SCR : The SCR [dec] out of rang ([dec], [dec])
Explanation A VBR SRC is out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_BAD_VC_DESC : Illegal vcd on get rx cell count: [dec], value is invalid
Explanation An illegal VC descriptor was given as an argument.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_BAD_VPI_VCI_BITS : Invalid vpi_bits ([dec]) or vci_bits ([dec])
Explanation VPI bits or VCI bits are out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_CLOSE_VC_TIMEOUT : vc closing timeout
Explanation A VBR VC closing timeout error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-4-LLD_DEVNOTFOUND1 : Can't find SE64: ID: [hex], Control: [hex], Done: [hex]
Explanation The system could not find the SE64 device on the PCI bus.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_DEVNOTFOUND2 : Failed to find SE64: ID: [hex], Control: [hex], Done: [hex]
Explanation The system has tried and failed to find the SE64 device on the PCI bus. This message marks the system's final attempt to find the SE64 device on the PCI bus.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_INVALID_VC : Invalid VC descriptor [dec]
Explanation An error involving an invalid VC descriptor in closing the VC has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_MP_HOLDER_ERR : [chars]
Explanation An error in LLD packet or particle queue integrity has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_MPHOLDER_DQADR : vc dequeued mp holder addr mismatch, vcd [dec], holder ba, [hex], ba [hex]
Explanation The dequeued MP buffer holder address does not match the buffer holder address.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_MPHOLDER_DQNULL : mp holder tail is null on vc dequeue, vcd; [dec]
Explanation The MP holder tail should not be null during the checked dequeue.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_MPHOLDER_NQNULL : mp holder tail is null on vc enqeue, vcd; [dec], head: 0x08x
Explanation An attempt to enqueue an MP holder has found an empty tail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_MPHOLDERNONZERO : Free mp holder holder not zero, current count: [dec]
Explanation The MP free holder pool was expected to be empty; however, the pool has a nonzero count.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_NOFREEMPHOLDER : No free holder was available, current count: [dec]
Explanation An MP free holder pool was empty.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_NO_MEM : No memory for [chars]
Explanation The system has run out of memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_NVCI_INVALID_VPI : Undefined VPI bits: VPI: [dec]
Explanation The number of VPI bits are not supported by the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_PARALIGN : Particle not aligned to 2k boundary [hex]
Explanation SE64 requires that Rx particles be aligned to 2k.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_PAROCCUPIED : Particle slot occupied upon return: [dec]
Explanation A particle slot was unexpectedly occupied during its return.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_PARRANGE : Particle out of range: [dec] [dec]
Explanation An Rx particle index is outside the expected range of values.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_RX_DESC_ERR : [chars]
Explanation A SAR Rx descriptor error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_RX_OFFSET_NOT_MATCH : Unusable RX buffer offset [dec]
Explanation The Rx VC has not closed while it was trying to set up a VC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_RXPCLR : RXP bit already clr at index: [dec]
Explanation The SE64 Rx pool own bit was unexpectedly cleared upon buffer return.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_RXPKT_BADDSCDEX1 : Bad Rx descriptor index: [dec]
Explanation SE64 has returned a bad index for an RX VC descriptor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_RXPKT_NULLPH : NULL RX particle header [hex]
Explanation A null particle header has been found at the index specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_RXPKT_POOLID : Bad Rx Pool ID: which [dec], poolid [dec]
Explanation SE64 has returned an invalid pool ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_RXPKT_RPTCODE : Bad Rx report type code: code [dec]
Explanation SE64 has returned an invalid Rx report type code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_RXPKT_SMCODE : Bad Rx State Machine return code: which [dec]
Explanation SE64 Rx state machine has returned an invalid code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_RX_VC_NOT_CLOSE : VC not closed. Rx desc ind [dec]
Explanation A VC could not be set up because the Rx VC was not closed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_RXVCSM_BADIN : Invalid input to RX VC State Machine: Current State [chars] Input [dec]
Explanation There was an unexpected input to the Rx VC SM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_SAR_HW_ERR : SAR hardware error
Explanation The SAR system control register has returned all ones. Initialization has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_SHAPER_ERR : [chars]
Explanation A SAR shaper error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_SHAPER_NOT_SET : Shaper [dec] is not setup
Explanation The shaper specified in the error message is not set up.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_SNDBUF_ALIGN2K : Buffer is not aligned to 2k
Explanation The Tx buffer is not aligned on 2k.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_SNDPAK_ALIGN : send packet mis-aligned: vcd [dec], buffer_base [hex]
Explanation The Tx packet length is misaligned.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_SNDPAK_LEN0 : send packet length is zero: vcd [dec], data_block [hex]
Explanation The packet length is expected to be nonzero but was detected as being zero.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_SNDPAK_NOMPHOLDER : No mp holder available: vcd [dec]
Explanation A free MP holder was not available for a Tx packet.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_SNDPAK_SARNOTREADY : SAR not ready during packet TX: vcd [dec]
Explanation SAR was not ready and could not accept a Tx buffer during a packet transfer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_SNDPAK_VCDMT : send packet vc desc null: vcd [dec]
Explanation The Tx packet VC descriptor was empty when it should have contained a non-null value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_SNDPAR_ALIGN : send particle mis-aligned: vcd [dec], buffer_base [hex]
Explanation A Tx particle length is misaligned.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_SNDPAR_LEN0 : send particle length is zero: vcd [dec], data_block [hex]
Explanation A Tx particle length is expected to be nonzero but was detected as being zero.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_SNDPAR_NOMPHOLDER : No mp holder available: vcd [dec]
Explanation A free MP holder was not available for a Tx particle.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_SNDPAR_SARNOTREADY : SAR not ready during particle TX: vcd [dec]
Explanation SAR was not ready and could not accept a new buffer during an attempted particle transfer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_SNDPAR_VCDMT : send particle vc desc null: vcd [dec]
Explanation The Tx particle VC descriptor was empty when it should have contained a non-null value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_TX_DESC_ERR : [chars]
Explanation A SAR Tx descriptor error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_TXRPT_DSCDEX : Bad Tx report descr index: index [dec]
Explanation SE64 returned an invalid Tx descriptor index.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_TXRPT_NOBUF : Tx report buffer mp holder not found: buf_addr [hex]
Explanation The system could not find an MP holder for the returned buffer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_VCD_NOT_MATCH : vcd does not match record:[dec], pass [dec]
Explanation The VCD did not match while the system was closing the VC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-LLD_VC_NOT_SETUP : VC not setup [dec]
Explanation The Rx VC was not closed when the system was trying to set up a VC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_BAD_BUF_TO_VCD : Failed buffer to VCD translation [dec]
Explanation The translation table contains an invalid entry.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_BAD_RX_POOL : [dec] [dec]
Explanation An unexpected Rx particle pool count has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_BADVC : [chars] bad vcd [dec] packet - \n [hex] [hex] [hex] [hex] [hex] [hex]
Explanation A packet has been received on a nonexistent VC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_CHANGE_VC_ENCAP_FAILED : VC([dec]) Encap not changed
Explanation The VC encapsulation has not been changed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_DUP_RXP : [hex]
Explanation A duplicate RXP entry was encountered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_ILLEGAL_EXEC : Illegal exec [dec]
Explanation Unexpected code was executed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_ILLEGAL_TX_PAK : Illegal TX packet type: [chars]
Explanation An illegal packet type was passed on to the LLD.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_INVALID_VCI : VC([dec]/[dec]) VCI too large
Explanation The VCI is too large.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_INVALID_VPI : VC([dec]/[dec]) VPI too large
Explanation The VPI is too large.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_MALLOCFAIL : Malloc Failure: [chars]
Explanation Memory allocation of a data structure has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_NEG_TX_AVAIL : Negative internal tx buffer available resources [dec]
Explanation The internal Tx buffer available resources were found to have a negative value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_NO_TXPAK_RES : Too many VCs: no TX resources remaining for VBR traffic on vcd [dec], max VCs is [dec]
Explanation The number of configured VCs has consumed all Tx resources.
Recommended Action Enter the shutdown and no shutdown commands to restart the interface and configure fewer VCs.
Error Message%NRP2_SE64-3-ULD_OUTPUT_VC_THROTTLE : Output VC Throttled: VCD = [dec]
Explanation An output VC was throttled.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_POOLFAIL : Pool Create Failure: [chars]
Explanation The creation of a buffer or particle pool has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_SAR_REV : Unsupported SAR [hex]
Explanation The SAR revision is not supported in this image.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_UNDERFLOW1 : [dec] [dec] [dec] [dec] [dec] [dec]
Explanation A global statistics counter has underflowed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_UNDERFLOW2 :
Explanation A per-VC statistics counter has underflowed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_VC_DELETED : [chars] vcd [dec] is deleted\n
Explanation The system is transmitting a packet on a nonexistent VC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_VC_SETUP_QOS : Illegal QOS for vcd [dec] setup
Explanation An illegal QoS has been encountered during the setup for a VC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_VC_TEARDOWN_QOS : Illegal QOS for vcd [dec] teardown
Explanation An illegal QoS has been encountered during the removal of a VC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NRP2_SE64-3-ULD_VCUP : VCD = [dec]
Explanation A VC setup has been requested for a VC that is already up.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
NRP2EHSA Messages
The following are NRP2 EHSA-related messages.
Error Message%NRP2EHSA-3-CONFIG_SYNC : [chars]
Explanation An EHSA configuration synchronization error has occurred. The details about what was attempted and what went wrong are shown in the error message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy down the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NRP2EHSA-3-EHSA_ALARMS : [chars] (slot [dec]/[dec])\n
Explanation An EHSA alarm assertions error has occurred. The details about what was attempted and what went wrong are shown in the error message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy down the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NRP2EHSA-3-FSM : [chars]
Explanation An EHSA Finite State Machine error has occurred. The details about what was attempted and what went wrong are shown in the error message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy down the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NRP2EHSA-3-GENERAL : [chars]
Explanation An EHSA error has occurred. The details about what was attempted and what went wrong are shown in the error message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy down the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NRP2EHSA-3-PEER_MONITOR : [chars] (slot [dec])\n
Explanation An EHSA peer monitor error has occurred. The details about what was attempted and what went wrong are shown in the error message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy down the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NRP2EHSA-5-PEER_MONITOR_EVENT : [chars] ([chars][chars]([dec]))\n \n
Explanation An EHSA peer monitor event has occurred and been reported.
Recommended Action Analyze the report to find out the reason for a switch-over.
NSE Messages
The following are network services engine messages.
Error Message%NSE-3-BAD_TUNNEL_MAGIC : Incorrect tunnel structure signature in fuction [chars]: tp=[hex] magic=[hex].
Explanation A pointer in Cisco IOS software has become corrupted and is not pointing to the correct part of Cisco IOS software. This pointer mismatch may be caused by high VPN session loads. This condition can cause a router trap and can cause the router to be reloaded.
Recommended Action Manually reload the router as soon as possible. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NSE-3-BAD_TUNNEL_POINTER : Pointer mismatch in fuction [chars]: tp=[hex] tunnel=[hex] toaster_tunn[[dec]]=[hex].
Explanation A pointer in Cisco IOS software has become corrupted and is not pointing to the correct part of Cisco IOS software. This pointer mismatch may be caused by high VPN session loads. This condition can cause a router trap and can cause the router to be reloaded.
Recommended Action Manually reload the router as soon as possible. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NSE-6-NOVLAN_STATS : No VLAN statistics are avaliable for PXF switched interface [chars].
Explanation No 802.1Q statistics are available for packets that are PXF switched.
Recommended Action No action is required.
Error Message%NSE-3-QUEUEHUNG : QoS queue hung on interface [chars].
Explanation The system was unable to close down the QoS support in PXF for the interface cleanly. Problems may arise if the QoS support in PXF for the interface is restarted without first reloading the PXF microcode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NSE-3-TUNNEL_ALREADY_IN_USE : New tunnel (local::remote) [dec]::[dec] already in use by tunnel [dec]::[dec].
Explanation A new tunnel has the same local tunnel ID as an existing tunnel. The new tunnel creation will be aborted.
Recommended Action No action is required.
Error Message%NSE-3-UNKNOWN_QOS_ACTION : Unknown QoS action type: [hex].
Explanation A QoS feature, unrecognized by PXF, has been configured with the Modular QoS CLI. The feature will work, but excessive punting may occur if the feature is on an output interface.
Recommended Action If performance is poor, try disabling PXF.
NSP Messages
The following are Network Switch Processor (NSP) messages.
Error Message%NSP-3-BADSLOT : Invalid slots[]: [hex]
Explanation An internal error, indicating an invalid slot type pointer, has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%NSP-3-BOGUS_PARAMETER : Bogus parameter passed: [chars] [dec]
Explanation An internal error, indicating an invalid parameter passed to a routine, has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%NSP-2-NOMEMORY : Unit [dec], no memory for [chars]
Explanation An operation could not be accomplished because of a low memory condition. The current system configuration, 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 larger memory configuration.
Error Message%NSP-4-SONET_ALARM : [chars]: [chars] [chars]
Explanation A SONET line warning condition has been detected.
Recommended Action No action is required.
