Resolving Error Messages

The list of system error messages provides a description of error messages organized according to the system facility that produces the messages, in alphabetical order. Within each system facility section, messages are listed alphabetically by mnemonic. Each error message is followed by an explanation and a recommended action. System error messages appear only when the system remains operational.

Error message severity levels correspond to the keywords assigned by the logging global configuration commands that define where and at what level these messages appear. The default is to log messages to the console at the debugging level (7).

C.2 How to Read System Error Messages

System error messages begin with a percent sign and have the following syntax structure:

%FACILITY-SEVERITY-MNEMONIC: Message-text

FACILITY is a code consisting of two or more uppercase letters that indicate the facility associated with the message. A facility can be a hardware device, a protocol, or a module of the system software. Table C-1 lists the system facility codes.

Table C-1: Facility Codes

Code Facility

AAL5

ATM adaptation layer 5

ALARM

Alarm specific errors

ATM

ATM specific errors

ATMSIG

ATM signaling

CI

Environment monitor

CLOCKSW

Network clocking errors

EHSA

EHSA availability errors

FILESYS

File system errors

FPGA

Field programmable gate array

IPC

IPC card errors

LANE

LAN emulation

LINECARD

Errors related to the NRPs or line cards

Miscellaneous

Miscellaneous error messages

NRP

NRP related errors

NSPINT

NSP errors

OC3SUNI

Optical carrier 3 driver

OIR

Online insertion and removal

PAMMBOX

Port adapter module mailbox

PNNI/IISP

PNNI or IISP routing

RSP

Redundant system processor errors

SONICT

Ethernet driver

Code	Facility
AAL5	ATM adaptation layer 5
ALARM	Alarm specific errors
ATM	ATM specific errors
ATMSIG	ATM signaling
CI	Environment monitor
CLOCKSW	Network clocking errors
EHSA	EHSA availability errors
FILESYS	File system errors
FPGA	Field programmable gate array
IPC	IPC card errors
LANE	LAN emulation
LINECARD	Errors related to the NRPs or line cards
Miscellaneous	Miscellaneous error messages
NRP	NRP related errors
NSPINT	NSP errors
OC3SUNI	Optical carrier 3 driver
OIR	Online insertion and removal
PAMMBOX	Port adapter module mailbox
PNNI/IISP	PNNI or IISP routing
RSP	Redundant system processor errors
SONICT	Ethernet driver

SEVERITY is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. Table C-2 lists the severity levels.

Level	Description
0 - emergency	System unusable
1 - alert	Immediate action needed
2 - critical	Critical condition
3 - error	Error condition
4 - warning	Warning condition
5 - notification	Normal but significant condition
6 - informational	Informational message only
7 - debugging	Appears during debugging only

Table C-2: Error Message Severity Levels

Level Description

0 - emergency

System unusable

1 - alert

Immediate action needed

2 - critical

Critical condition

3 - error

Error condition

4 - warning

Warning condition

5 - notification

Normal but significant condition

6 - informational

Informational message only

7 - debugging

Appears during debugging only

MNEMONIC is a code that uniquely identifies the error message.

Message-text is a text string that describes the condition. This portion of the message may contain detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets ([ ]). A decimal number, for example, is represented as [dec].
Table C-3 lists the representations of variable fields and the type of information in the fields.

The following is a sample system error message:

%SONICT-3-XMIT_ERR: TX Error [hex]

Representation	Type of Information
[dec]	Decimal number
[hex]	Hexadecimal number
[char]	Single character
[chars]	Character string

Table C-3: Representation of Variable Fields in Error Messages

Representation Type of Information

[dec]

Decimal number

[hex]

Hexadecimal number

[char]

Single character

[chars]

Character string

C.3 Error Message Traceback Reports

A number of messages describe internal errors and contain traceback information. This information is very important and should be included when you report a problem to your technical support representative.

The following sample message includes traceback information:

-Process= "Exec", level= 0, pid= 17 -Traceback= 1A82 1AB4 6378 A072 1054 1860

C.4 List of Error Messages

Cisco 6400 software error messages are separated according to the facility codes shown in Table C-1.

C.4.1 AAL5 Error Messages

Error Message %AAL5-1-NOMEMORY: msgtxt_nomemory

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %AAL5-3-INTERNAL_ERROR: [chars]

Error Message %AAL5-3-RXERR [hex], orig [hex], port=[chars]

C.4.2 Alarm Error Messages

Error Message %ALARM-1-CRITICAL_ALARM: CRITICAL alarm condition detected

Explanation A critical alarm event has happened, it will cause a serious result, and needs immediate attention and to be fixed. System will shut down within two minutes.

Recommended Action Check the source of the critical alarms to take corresponding actions. Don't turn on power unless the situation is corrected. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %ALARM-2-MAJOR_ALARM: Major alarm condition detected

Explanation A major alarm event has happened, it will affect the system service, and needs attention or fix.

Recommended Action Check the source of the major alarms to take corresponding actions. This situation should be corrected or be duly noted. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %ALARM-3-MINOR_ALARM: Minor alarm condition detected

Explanation A minor alarm event has happened, it does not affect the system service, but needs attention.

Recommended Action Check the source of the minor alarms to avoid the situation getting worse. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

C.4.3 ATM Error Messages

Error Message %ATM-3-FAILCREATEVC: ATM failed to create VPI=[dec], VCI=[dec]) on Interface [chars], (Cause of the failure: [chars])

Explanation This message can occur for the following unrelated reasons. Each reason is accompanied by a recommended action.

Address Resolution Protocol (ARP) is allowed only on AAL5-SNAP virtual circuits.
- Change the encapsulation to AAL5SNAP.
The virtual path identifier-virtual channel identifier (VPI-VCI) pair, or the VCD is already in use.
- Try using a different VPI-VCI number.
Only one virtual channel connection (VCC) is allowed on a point-to-point interface.
- Try using a different subinterface.
AAL3/4-SMDS virtual circuit must be the only virtual circuit on an interface.
- Turn off AAL3/4.
AAL3/4-SMDS multiplex ID exceeds the maximum.
- Try a smaller multiplex ID value.
Switched Multimegabit Data Service (SMDS) is not enabled.
- Enable SMDS.
The driver failed to accept the virtual circuit.
- Try initiating the virtual circuit again.

Recommended Action If none of the previous actions fix the problem, copy the error message exactly as it appears and report it to your technical support representative.

Error Message %ATM-4-MTUCALLMISMATCH: Incoming call from [ATM NSAP] has a mismatched maximum transmission unit - incoming forward PDU size is [dec], backward PDU size is [dec], interface [chars] MTU size is [dec][chars]

Explanation The calling or called party has a maximum transmission unit (MTU) size configured that is different from the MTU size on the current interface.

Recommended Action Either change the configured MTU size on the current interface to that of the caller's or called party's interface, or change the caller's or called party's interface to match the current interface.

Error Message %ATM-4-NOMEM: Failed to allocate memory--[chars], ONEMIN

Explanation The system attempted to allocate some memory but failed.

Recommended Action Reduce the RAM usage or add more RAM to your switch.

Error Message %ATM-3-UNSUPPORTED_QOS_PARMAS:ATM failed to create VC on Interface [ATM int],(Cause of the failure Invalid traffic shaping parameters or out of rate queues.

Explanation The system attempted to create a virtual circuit (VC) with traffic shaping parameters not supported by the hardware.

Recommended Action Either change the requested traffic shaping parameter to one that the hardware supports, or use existing parameters to avoid the need for a new rate queue.

Error Message %ATM-4-ILMIKEEPALIVEFAIL: Restarting ATM signalling and ILMI. Keepalive failure detected.

Explanation Adjacent peer device is not responding to ILMI Keepalive polling.

Recommended Action Check the connection of the ATM interface and the status of the adjacent peer device. Correct them if necessary. Wait and check if ILMI Keepalive comes up again. If the problem persists, copy this warning message exactly as it appears, and report it to your technical support representative.

Error Message %ATM-4-ILMICONFIGCHANGE:

Explanation Restarting ATM signaling and ILMI. Peer Configuration change detected. Configuration of adjacent peer device has been changed.

Recommended Action Wait for the interface to restart itself.

Error Message %ATM-6-ILMIAUTOCFGALREADY: Auto-configuration already enabled.

Explanation ATM autoconfiguration has been enabled already.The atm auto-configuration command just entered is ignored.

Recommended Action No action required.

Error Message %ATM-6-ILMINOAUTOCFG: Auto configuration already disabled.

Explanation ATM autoconfiguration has been enabled already. The no atm auto-configuration command just entered is ignored.

Recommended Action No action required.

Error Message %ATM-4-UNMATCHUNIVERSIONSSCOP: sig_db->namestring, rcv N(SQ)=0 in BeginPdu at UNI 3.1

Explanation This message appears on the console when the two ATMUNI versions on either side do not match. For example, the Cisco 6400 is configured in UNI 3.1 version mode and the device attached to it is configured for UNI version 3.0.

Recommended Action Change the UNI version on either side to match the other. On the Cisco 6400 switch side, use the atm uni version command on the interface specified in the error message.

C.4.4 ATM Signaling Error Messages

Error Message %ATMSIG-3-ATMSIG_PRTY_DELETE_FAILED: svc->svc_namestring, svc->vpci, svc->vci, (svc->callRef & ATMSIG_CALLREF_VALUEMASK), (party ? party->endpointRef

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-ATMSIG_PRTY_INSERT_FAILED ,partnerSvc->svc_namestring, partnerSvc->vpci, partnerSvc->vci, (partnerSvc->callRef & ATMSIG_CALLREF_VALUEMASK), (partnerParty ? partnerParty->endpointRef

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-ATMSIG_PRTY_INSERT_FAILED: svc->svc_namestring, svc->vpci, svc->vci, (svc->callRef & ATMSIG_CALLREF_VALUEMASK), (svc->curr_party ? svc->curr_party->endpointRef

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-ATMSIG_SVC_INSERT_FAILED: destSvc->svc_namestring, destSvc->vpci, destSvc->vci, (destSvc->callRef & ATMSIG_CALLREF_VALUEMASK), (destSvc->rootParty ? destSvc->rootParty->endpointRef : 0), destSvc)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-ATMSIG_SVC_INSERT_FAILED: svc->svc_namestring, svc->vpci, svc->vci, (svc->callRef & ATMSIG_CALLREF_VALUEMASK), (svc->curr_party ? svc->curr_party->endpointRef : 0), svc); errmsg(&msgsym(UNEXPECTEDEVENT,SCHED)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-ENQFAIL: enqueue atmsig_cb.mgmtapi_inqueue errmsg(&msgsym(UNEXPECTEDEVENT, SCHED)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-ENQFAIL: enqueue acctGlob.mymsg_inqueue free(msg) errmsg(&msgsym(UNEXPECTEDEVENT,SCHED)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-ENQFAIL: enqueue atmsig_cb.mgmtapi_inqueue msg->err_code = ATMSIG_MGMT_API_INTERNAL_ERROR

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-ENQFAIL: enqueue atmsig_cb.mgmtapi_inqueue free(msg)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-ENQFAIL: enqueue atmsig_cb.pnni_queue atm_ ys_msg->ret_code = IPC_ASYNC

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-ENQFAIL: enqueue atmSig_outputQ

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-FAILASSERT: [chars]

Explanation ATM signaling found an internal critical error.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-FAILXCONN: xconn fail

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-INVPNNIMSG: Invalid msg from routing/pnni: number of ports > MAX

Explanation An invalid message received from routing. Number of ports greater than maximum.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-INVPNNIMSG: Invalid msg from routing/pnni: NULL port list

Explanation An invalid message received from routing. No ports can be found to route this call.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-INVPNNIMSG: Invalid msg from routing/pnni: NULL message

Explanation An invalid message received from PNNI routing error. Null message received.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-INVPNNIMSG: Invalid msg from routing/pnni: msg type not valid

Explanation An invalid message received from routing. Message type not valid.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-INVPNNIMSG: Invalid msg from routing/pnni: source proc not valid

Explanation An invalid message received from routing. Source process not valid. It must be a routing module.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-INVPNNIMSG: Invalid msg from routing/pnni: dest proc not valid

Explanation An invalid message received from routing. Destination process not valid. It must be a signaling module.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-INVPNNIMSG: Invalid msg from routing/pnni: NULL curr party

Explanation An invalid message received from routing. Null current party.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-INVPNNIMSG: Invalid msg from routing/pnni: NULL SVC

Explanation An invalid message received from routing. No signaling control block.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-INVPNNIMSG: Invalid msg from routing/pnni: msg code not resp

Explanation An invalid message received from routing. Message code not responding.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-INVPNNIMSG: Invalid msg from routing/pnni: msg vers bad

Explanation An invalid message received from routing. Message version bad.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-INVPNNIMSG: Invalid msg from routing/pnni: NULL port_rsp message

Explanation An invalid message received from routing. Null message.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-FAILHALFLEGREM: halfLeg removal failed, removeHalfLeg

Explanation ATM signaling failed half-leg removal error.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-FAILHALFLEGREM: 2nd halfleg failed, Get 2nd half leg failure. no ifcb

Explanation ATM signaling failed to remove the second half-leg of a connection.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-NOMEM: [chars]

Explanation ATM signaling could not allocate memory.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-NOSVC: no SVC, atmSig_findPartyBlockByRef

Explanation ATM signal control block was not found for a party message.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %ATMSIG-3-NOSVC: no SVC, atmSig_input

Explanation ATM signal control block was not found for an input message.

Recommended Action If this message occurs, contact your technical support representative for assistance.

C.4.5 CI Error Messages

Error Message %CI-0-SHUTFANFAIL: Shutting down due to complete fan failure

Error Message %CI-0-SHUTFANGONE: Shutting down due to missing fan tray

Explanation The chassis fan does not exist.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CI-1-CORETEMPCRITICAL: Core CRITICAL Temperature limit exceeded

Explanation An overheating of the Processor Card is detected. The temperature has exceeded critical limit. An automatic shutdown results if the condition prevails for more than two minutes. Possible causes for this error are malfunctioning fan or a shorted circuit on the processor card.

Recommended Action Check temperature of Processor Card and determine whether the fan is malfunctioning. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CI-1-INLETTEMPCRITICAL: Inlet CRITICAL Temperature limit exceeded

Explanation An overheating of environment is detected. The temperature has exceeded major limit. An automatic shutdown results if the condition prevails for more than two minutes. Possible causes for this error are malfunctioning fan.

Recommended Action Check temperature next to chassis intake and determine whether the fan is malfunctioning. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CI-1-NOFAN: Fan tray empty

Explanation The chassis fan does not exist.

Error Message %CI-1-TOTALFANFAIL: Complete fan failure

Explanation The chassis fan has failed. This may be due to an internal hardware problem. If this condition persists more for more than two minutes, system will be shut down automatically.

Error Message %CI-3-ASPMEM: Santa equipped with [chars] requires at least [dec] MB of RAM Only [dec] MB of RAM installed

Explanation The particular feature card installed needs more RAM than the installed amount.

Recommended Action Install the required amount of RAM and try again.

Error Message %CI-3-ASPREV: ***WARNING*** Hot swapping the ASP will cause hardware damage.

Explanation The ASP is not hot-swappable. If hot-swapped, hardware damage might result.

Recommended Action Please take advice from Cisco technical support engineers before continuing.

Error Message %CI-3-BLOWER: Fan failure

Explanation The chassis fan has failed. This may be due to an internal hardware problem.

Error Message %CI-3-CORETEMPMAJOR: Core Major Temperature limit exceeded

Explanation An overheating of the Processor Card is detected. The temperature has exceeded major limit. Possible causes for this error are malfunctioning fan or a shorted circuit on processor card.

Error Message %CI-3-CORETEMPMINOR: Core Minor Temperature limit exceeded

Explanation An overheating of the Processor Card is detected. The temperature has exceeded minor limit. Possible causes for this error are malfunctioning fan or a shorted circuit on processor card.

Error Message %CI-3-FCTYPE: Cannot recognize Feature Card

Explanation The feature card is not recognized by the software.

Recommended Action Software/hardware incompatibility Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CI-3-INLETTEMPMAJOR: Inlet Major Temperature limit exceeded

Explanation An overheating of environment is detected. The temperature has exceeded major limit. Possible cause for this error is a malfunctioning fan.

Recommended Action Check temperature next to chassis intake and verify that the fan is not malfunctioning. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CI-3-INLETTEMPMINOR: Inlet Minor Temperature limit exceeded

Explanation An overheating of environment is detected. The temperature has exceeded minor limit. A possible cause for this error is a malfunctioning fan.

Error Message %CI-3-NOACK: Access to [chars] failed

Error Message %CI-3-NOFORK: Couldn't start environment polling daemon

Explanation The environment monitoring daemon process is not started at chassis initialization. Environment polling is not possible. This is due to an internal process creation failure.

Recommended Action There is an internal error. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CI-3-PARTFANFAIL: Single fan failure

Explanation The chassis fan is not fully functioning. This may be due to an internal hardware problem.

Error Message %CI-3-PSFAIL: Power supply [int] failure

Explanation The chassis power supply has failed. This may be due to an internal hardware problem in the power supply in question.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CI-3-PSFANFAIL: Power supply fan [int] failure

Explanation The chassis power supply's fan has failed.

Error Message %CI-3-PSTYPE: ***WARNING*** Incompatible power supply types - One is AC, other is DC.

Explanation The chassis power supply types are incompatible. Power supplies need to be of the same type for normal functioning.

Error Message %CI-3-SHUTDOWN: Shutting down due to overheat

Explanation The temperature of the chassis is over the limit and has prevailed for more than two minutes. Auto shutdown initiated.

Error Message %CI-6-BLOWEROK: Fan OK

Explanation Chassis fan is working fine.

Recommended Action No action is required.

Error Message %CI-6-CORETEMPOK: Core Temperature OK

Explanation The temperature next to the core of the processor card is normal.

Recommended Action No action is required.

Error Message %CI-6-INLETTEMPOK: Inlet Temperature OK

Explanation The temperature next to the chassis intake is normal.

Recommended Action No action is required.

Error Message %CI-6-PSCHANGE: Power supply [int] changed from [chars] to [chars]

Explanation The chassis power supply has changed from one type to another.

Recommended Action No action is required.

Error Message %CI-6-PSFANOK: Power supply fan [int] OK

Explanation Chassis power supply fan is normal.

Recommended Action No action is required.

Error Message %CI-6-PSOK: Power supply [int] OK

Explanation Chassis power supply is normal.

Recommended Action No action is required.

C.4.6 Clock Error Messages

Error Message %CLOCKSW-3-BOGUS_PLIMTYPE: [chars]: bogus plimtype 0x[hex]

Explanation This indicates an internal error in the IDB. This interface cannot be selected as a network clocking source.

Recommended Action Select another interface as the network clocking source.

Error Message %CLOCKSW-3-CLOCK_ALL_FAIL: All selected network clock sources have failed

Explanation All of the configured network clocking sources have failed.

Recommended Action Restore proper operation to one or more of the selected interfaces.

Error Message %CLOCKSW-3-CLOCK_FAIL: Network clock source [chars], priority [dec], failure

Explanation Specified network clocking source has failed.

Recommended Action Restore proper operation of the selected interface.

Error Message %CLOCKSW-6-CLOCK_OK: Network clock source [chars], priority [dec], ok

Explanation Specified network clocking source is operational.

Recommended Action No action is required.

Error Message %CLOCKSW-6-PFQ_PLL_BYPASS: Bypassing FC-PFQ PLL

Explanation The FC-PFQ clock is non-operational, bypassing.

Recommended Action No action is required.

Error Message %CLOCKSW-6-SWITCH_SOURCES: Switching from [chars] to [chars] at priority level [dec]

Explanation The network clock source has changed from one source to another.

Recommended Action No action is required.

C.4.7 EHSA Error Messages

Error Message %EHSA-3-EHSA_ALARMS: [chars]

Explanation An EHSA Alarm assertions error occurred. The details about what was attempted and what went wrong will be printed.

Recommended Action Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.

Error Message %EHSA-3-FSM: [chars]

Explanation An EHSA Finite State Machine (FSM) error occurred. The details about what was attempted and what went wrong will be printed.

Error Message %EHSA-3-GENERAL: [chars]

Explanation An EHSA error occurred. The details about what was attempted and what went wrong will be printed.

Error Message %EHSA-3-IPC: [chars] [chars]

Explanation An Interprocess Communication (IPC) error occurred. The details about what was attempted and what went wrong will be printed.

Error Message %EHSA-3-PEER_MONITOR: [chars]

Explanation An EHSA Peer Monitor error occurred. The details about what was attempted and what went wrong will be printed.

C.4.8 File System Error Messages

Error Message %FILESYS-3-FLASH: [chars] [chars] error [dec]

Explanation A file system error has occurred.

Error Message %FILESYS-5-DEV: PCMCIA flash card [chars] [chars]

Explanation A file system's status has changed. Follow any instructions provided with the message.

Recommended Action No action is required.

C.4.9 FPGA Error Messages

Error Message %FPGA-3-ABR: ABR FPGA don't reset properly, Control Register=[hex]

Explanation Status of the FPGA is abnormal when ABR is being handled. Might be due to an internal code error.

Error Message %FPGA-3-DONE_PIN: Done pin or Status pin isn't pull low, FPGA# [dec]

Explanation The hardware Done pin or Status pin are not properly set in the FPGA.

Error Message %FPGA-3-DOWNLOAD: Download Fail, FPGA# [dec]

Explanation Download failed for the given FPGA version. May be due to a code error.

Error Message %FPGA-3-MCAST: Multicast FPGA don't reset properly, Control Register=[hex]

Explanation Status of the FPGA is abnormal when multicast is being done. Might be due to an internal code error.

Error Message %FPGA-3-NOFORK: Can't create Per VC Counter daemon

Explanation The new port adapter module (PAM) is not inserted into the slot properly.

Recommended Action Remove the new PAM and re-insert it into the slot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %FPGA-3-STATUS_PIN: Error in status pin, FPGA# [dec]

Explanation Status pin not functioning properly in FPGA.

Error Message %FPGA-3-TRAFF: Traffic FPGA don't reset properly, Control Register=[hex]

Explanation Status of the FPGA is abnormal when traffic is being handled. Might be due to an internal code error.

Error Message %FPGA-3-TYPE: ***WARNING*** Invalid feature card type - Use higher version of software: [hex]

Explanation The feature card might be new or the software installed doesn't support the feature card due to new features/incompatibilities.

Recommended Action Update your software to a higher version. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %FPGA-3-VERSION: Feature Card version invalid/old. Feature Card Version:[dec].[dec], NSP Version:[dec].[dec]

Explanation Invalid or obsolete version of the feature card is used. This is not compatible with the current NSP version.

Recommended Action Feature card version needs to be updated. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

C.4.10 IPC Error Messages

Error Message %IPC_RSP_CBUS-3-CARDERR: [chars]

Explanation An IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %IPC_RSP_CBUS-3-INVNUM: [chars] ([dec])

Explanation The IPC application tried to send a message that was larger than IPC could handle. The message was not transmitted.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %IPC_RSP_CBUS-3-MSGERR: [chars] ([dec])

Explanation The slave IPC cannot register with master. It cannot exchange messages with the master.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %IPC_RSP_CBUS-3-NOBUF: [chars]

Explanation The IPC ran out of memory device (MEMD) buffers.

Recommended Action Reduce the number of applications currently running on the IPC. Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %IPC_RSP_CBUS-3-NOHWQ: Hardware queue for card at slot [dec] not found

Explanation IPC messages cannot be transmitted due to a missing hardware queue. The messages were discarded, and subsequent messages will not be transmitted to that card.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %IPC_RSP_CBUS-3-SEATERR: [chars] ([dec])

Explanation The ID associated with an IPC card is either missing, duplicated, or cannot be created.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

C.4.11 LAN Emulation Error Messages

Error Message %LANE-3-BADILMI: Unexpected ILMI event [dec]

Explanation An internal error occurred.

Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the switch configuration.

Error Message %LANE-3-BADNAME: ELAN name must be 1-32 characters long

Explanation An emulated LAN (ELAN) name was entered in a command that is longer than
32 characters. The LAN Emulation (LANE) standard v1.0 requires a name that is 32 characters or less in length.

Recommended Action Re-enter a shorter name.

Error Message %LANE-3-BADTYPE: LAN Emulation supports only Ethernet type

Explanation The user specified a Token Ring-emulated LAN, which is not currently supported.

Recommended Action Specify an Ethernet-emulated LAN. Future software releases will support Token Ring ELANs.

Error Message %LANE-3-LANE_LESBUS_UP: LES/BUS coming up from previous command

Explanation The lane server-bus command was reissued to start the LANE service components while the switch was trying to execute a previously issued lane server-bus command.

Recommended Action Wait for the initial lane server-bus command to either succeed or fail. The status of the server bus can be checked via the show lane server-bus interface subinterface name command. The previous command can also be canceled with the no lane server-bus command. If these steps fail to clear the problem, issue the shutdown command followed by a no shutdown command cycle on the subinterface, or on the whole interface. As a last resort, issue the no interface subinterface name command followed by the shutdown, no shutdown command cycle.

Error Message %LANE-3-LANE_SIG_CHAIN: not in [chars] chain ([hex] [hex])

Explanation An internal error occurred while system routines were handling ATM signaling messages for LANE.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-3-LANE_SIG_ERR: [chars]

Explanation An internal error occurred while system routines were handling ATM signaling messages for LANE.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-3-LANE_SIG_INV_MSG: invalid msg received ([hex] [hex] [hex])

Explanation An internal error occurred while system routines were handling ATM signaling messages for LANE.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-3-LANE_SIG_INV_STATE: invalid [chars] req in state [dec] ([hex])

Explanation An internal error occurred while system routines were handling ATM signaling messages for LANE.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-6-LEC: [chars]

Explanation A hardware or software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-3-LEC_BADAD: [chars] LEC unable to compute ATM address

Explanation The client cannot obtain an ATM address from the given configuration, or auto-assignment failed to get an ATM prefix from the switch.

Recommended Action If you expect the switch to assign the prefix to the switch, check that the Interim Local Management Interface (ILMI) is functional and the switch has a prefix configured. Otherwise, confirm that the client has an address in the nonvolatile RAM (NVRAM) configuration.

Error Message %LANE-3-LEC_CFG: [chars] CFG_REQ failed, [chars] (LECS returned [dec])

Explanation A software or hardware error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-3-LEC_CONTROL_MSG: Received bad control message on interface > [chars], 10*ONESEC

Explanation The client received a control message over one of its control virtual channel connections (VCCs) that failed the header check.

Recommended Action This message indicates a noninteroperable LANE configuration server, LANE server, or LANE client implementation on the emulated LAN.

Error Message %LANE-6-LEC_INFO: [chars]

Explanation A software or hardware error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-3-LEC_JOIN: [chars] JOIN failed, [chars] (LES returned [dec])

Explanation A software or hardware error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-3-LEC_LISTEN: [chars] listen failed on [chars]

Explanation The client failed an attempt to listen on a particular ATM address.

Recommended Action Reconfigure the client ATM address. It is conflicting with another component on the ATM Interface Processor (AIP) for the same ATM address.

Error Message %LANE-3-LEC_SIGNAL: Unexpected SigAPI event [dec], 10*ONESEC

Explanation ATM signaling sent the client an unexpected message type.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-4-LEC_STATE_ERROR: State: [dec], Event [dec]

Explanation A hardware or software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-6-LEC_TIMER: Timer [chars] expired

Explanation A hardware or software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-3-LECS_ERR: [chars]

Explanation An internal consistency error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-4-LECS_WARN: [chars]

Explanation The LANE configuration server address could not be registered with or deregistered from the switch using ILMI.

: Possible causes:

The switch prefix is not available.
The address is not acceptable to the switch (the prefix does not conform).
The interface over which this operation should take place is down.
The ILMI subsystem on the switch is not completely initialized.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-3-LSV_ADDR: [chars] elan [chars] unable to register LES/BUS ATM addr

Explanation A hardware or software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-3-LSV_BADAD: <interface> elan <ELAN name> unable to compute [chars] ATM address

Explanation Software was unable to compute an ATM address based on the ATM address template given. The characters in chars (see above display) will be either "BUS" (broadcast-and-unknown), "server," or "config server" in the actual error message.

Recommended Action Enter a correct ATM address template for the LANE component ("BUS," "server," or "config server") named in the error message.

Error Message %LANE-3-LSV_CRASH: <interface> elan <ELAN name> unrecoverable error [chars]

Explanation An internal error occurred.

Error Message %LANE-3-LSV_DUPATM: <interface> elan <ELAN name> client [dec] duplicate ATM address registration <ATM address>

Explanation An attempt was made by the specified LANE client to register a Media Access Control (MAC) address and ATM address pair that duplicated an ATM address already registered to another LANE client.

Recommended Action Use the show lane server command to list the registered addresses in the LANE server reporting the error. Correct one of the two LANE clients that is trying in error to use the same ATM address.

Error Message %LANE-3-LSV_DUPID: <interface> elan <ELAN name> duplicate LECID [dec]

Explanation An attempt was made to define two different server-direct PVCs both on the same subinterface (same LANE server) and both for the same client (LECID).

Recommended Action Delete one of the lane pvc commands that has this duplicated LECID.

Error Message %LANE-3-LSV_DUPMAC: <interface> elan <ELAN name> client [dec] duplicate MAC address registration [enet]

Explanation An attempt was made by the specified LANE client to register a MAC address and ATM address pair that duplicated a MAC address already registered to another LANE client.

Error Message %LANE-4-LSV_LECID: <interface> elan <ELAN name> LECIDs exhausted, 10*ONESEC

Explanation The LANE server specified has 65,279 clients. No more can be added.

Recommended Action Change the configurations to avoid trying to have more than 65,279 LANE clients on this server.

Error Message %LANE-3-LSV_MCAST: <interface> elan <ELAN name> unable to create [chars] MC group

Explanation An internal error occurred.

Error Message %LANE-3-LSV_NOREG: <interface> elan <ELAN name> client [dec] unable to register MAC address [enet]

Explanation An internal error occurred.

Error Message %LANE-6-MAKE17: Created vcd [dec] (PVC [dec]/[dec]) for config server access

Explanation The LANE software created a PVC (normally 0/17) for accessing the LANE configuration server.

Recommended Action Informational message only. No action required.

Error Message %LANE-3-NAMECHG: Attempt to change ELAN name

Explanation Both the LANE client and the LANE server/BUS may have an emulated LAN name specified in the configuration via the lane server-bus and lane client commands. If both specify the emulated LAN name, then the name cannot be changed by re-entering just one of the commands.

Recommended Action Use the no lane server-bus command to delete the server/BUS or use the no lane client command to delete the client. Re-enter the other of the two commands with another emulated LAN name. Finally, re-enter the deleted command with the new emulated LAN name.

Error Message %LANE-3-NEWPREF: <interface> elan <ELAN name> ATM address prefix [chars]

Explanation Entering a new ATM address template for some LANE component caused the specified LANE server or bus to drop all clients and restart.

Recommended Action Informational message only. No action required.

Error Message %LANE-3-NOILMI: ILMI service registration failed

Explanation The ILMI feature is not included in the software build running on the switch.

Recommended Action Reload the switch with software that includes the ILMI feature.

Error Message %LANE-3-NOINT: <interface> still destroying old sub-interface

Explanation An attempt was made to create a new subinterface while a previous version of the subinterface was still being destroyed.

Recommended Action Wait a minute and try again. If failure still occurs, try shutting down the main interface. Rebooting may be required to recover in extreme cases.

Error Message %LANE-3-NOREGATM: <interface> cannot register <ATM address> with ILMI

Explanation An attempt was made to register the given ATM address with the failed switch. This failure can occur because the ATM switch is down or misconfigured. The registration will be retried.

Recommended Action If the situation persists after a number of attempts and the switch is up, examine the configuration of the switch. The most likely cause is that the ATM address being registered is not compatible with the parameters --- for example, the ATM address prefix --- configured in the switch. Correct the configuration.

Error Message %LANE-3-NOREGILMI: [chars] [chars] cannot register [chars] with ILMI

Explanation An attempt to register the given ATM address with the ATM switch failed. This failure can occur because the ATM switch is down or misconfigured. The registration will be retried.

Recommended Action If the situation persists after a number of attempts, and the switch is up, the configuration of the switch and router should be examined. A likely cause is that the ATM address being registered is not compatible with the parameters configured in the switch. Correct the configuration.

Error Message %LANE-3-NOREGILMI: lec_info->swidb->namestring,LEC, lec_info->nsap.addr

Explanation An attempt to register the given ATM address with the ATM switch failed. This failure can occur because the ATM switch is down or misconfigured. The registration will be retried.

Error Message %LANE-3-NOVCD: VCDs exhausted

Explanation When trying to create PVC 0/17, the switch ran out of PVC resources.

Recommended Action The number of PVCs can be increased with the atm maxvc command.

Error Message %LANE-3-PVCBAD: <interface> elan <ELAN name> PVC vcd [dec] has no [chars] assigned

Explanation The characters in chars (see above display) will be either "ATM address" or "LECID." This message is reported when a PVC is created without all the necessary information included in the lane pvc command.

Recommended Action Include a lane pvc command with the information appropriate for the PVC.

Error Message %LANE-3-PVCLECS: Unable to create PVC [dec]/[dec]

Explanation An attempt to create the named PVC failed. The most likely reason is that a PVC was defined on the same or another subinterface with the same virtual path identifier-virtual channel identifier (VPI-VCI) pair, but with a different encapsulation or usage type.

Recommended Action Correct the configuration.

Error Message %LANE-3-REGSTATE: ILMI event in state [dec]

Explanation An internal error occurred.

Error Message %LANE-3-TYPECHG: Attempt to change ELAN type

Explanation Both the LANE client and the LANE server/bus may have an ELAN type specified in the configuration via the lane server-bus and lane client commands as either Ethernet or Token Ring. If both, specify the type; the type cannot be changed by re-entering just one of the commands.

Recommended Action Use the no lane server-bus command to delete the server bus or the no lane client command to delete the client. Re-enter the other of the two commands with a new type. Finally, re-enter the deleted command with the new type.

Error Message %LANE-5-UPDOWN: [chars] [chars] [chars]: [chars] changed state to [chars]

Explanation A software or hardware error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-3-LEC_REGISTER: REGISTER failed, [chars]. LES returned [dec]

Explanation A software or hardware error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %LANE-3-LEC_LISTEN: lec_info->swidb->namestring, addr

Explanation The client failed an attempt to listen on a particular ATM address.

Recommended Action Reconfigure the client ATM address. It is conflicting with another component on the ATM Interface Processor (AIP) for the same ATM address.

C.4.12 Line Card Error Messages

Error Message %LINECARD-3-NRP_BADSTATUS: NRP slot [dec] subslot [dec] invalid Mailbox status area contents or unreachable.

Error Message %LINECARD-3-NRP_CONFIG: NRP slot [dec] subslot [dec] invalid Mailbox config area contents or unreachable.

Error Message %LINECARD-3-NRP_CRASHING: NRP slot [dec] subslot [dec] crashing.

Error Message %LINECARD-3-NRP_CRASHREBOOT: NRP slot [dec] subslot [dec] crashed and rebooted.

Error Message %LINECARD-3-NRP_NONOP: NRP slot [dec] subslot [dec] non-operational.

Error Message %LINECARD-3-NRP_SECONDARYDEAD: NRP slot [dec] subslot [dec] reports EHSA secondary down.

Error Message %LINECARD-3-NRP_SECONDARYUP: NRP slot [dec] subslot [dec] reports EHSA secondary up.

Error Message %LINECARD-3-NRP_SECONDARY_TO_PRIMARY: NRP slot [dec] subslot [dec] EHSA secondary to primary cutover.

C.4.13 Node Route Processor Error Messages

Error Message %NRP-1-NOMEMORY: msgtxt_nomemory

Error Message %NRP-3-BADUNIT: msgtxt_badunit

Error Message %NRP-3-SPURIDON: msgtxt_spuriousidon

Error Message %NRP-3-TXOUTERR: Unable to write a message to NRP Mailbox, slot [dec]

Error Message %NRP-4-INVALIDSLOT: NRP not found in slot [dec], subslot [dec]

C.4.14 Node Switch Processor Error Messages

Error Message %NSP-1-NOMEMORY: msgtxt_nomemory

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's memory.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a configuration that has more memory.

Error Message %NSP-3-BADSLOT: Invalid slots[]: [hex]

Explanation Invalid slottype pointer.

Error Message %NSP-4-SONET_ALARM: [chars]: [chars] [chars]

Explanation SONET line warning.

Error Message %NSPINT-3-INTERNAL_ERROR: no handler for index [dec]

Error Message %NSPINT-5-SPURIOUS: Spurious level [dec] interrupt ([dec])

Error Message %NSP_OIR-3-ALOC_OIR_EVENT: OIR event structure allocation failure

Explanation Internal OIR element allocation failure. Usually this will indicate some memory leak.

Recommended Action Restart/reboot box at a convenient time. This problem will not affect normal operation but you will be unable to remove old hardware, or insert new hardware and bring it online

Error Message %NSP_OIR-3-BADCARD: Unrecognized Card, Driver for Card not available in system software, ignoring card type 0x[hex]

Explanation Card inserted into system is not recognized by software -- ignoring.

Recommended Action Replace card or upgrade software on NSP.

Error Message %NSP_OIR-3-BADINS: Insufficient system resources complete card insertion/redundancy request, Reverting Configuration

Explanation Operations associated with inserting card have failed. The system will revert to its previous state.

Error Message %NSP_OIR-3-BAD_FULL_INS: Cannot enable half height card, redundancy conflict

Explanation Redundancy/card conflict with cards in adjacent slot.

Error Message %NSP_OIR-3-BAD_HALF_INS: Cannot enable half height card, redundancy conflict

Explanation Redundancy/card conflict with cards in adjacent slot.

Error Message %NSP_OIR-3-INVCARD: Inserted card incompatible with previously removed card

Explanation Card inserted is not same type as one previously removed and thus invalid.

Recommended Action Please insert card similar to one which was previously removed or clear out alarm source.

Error Message %NSP_OIR-3-INV_HWCFG1: Invalid card/configuration in slot([dec]) Ignoring Card

Explanation Cards present in chassis in current mode are incompatible.

Recommended Action Caused by any number of events -- clear hw-module sub x/y cardtype to clear out alarms, or remove card.

Error Message %NSP_OIR-3-INV_HWCFG2: Cannot enable card slot([dec]) subslot redundancy is active on subcard in slot([dec])

Explanation Cards present in chassis in current mode are incompatible.

Recommended Action Caused by any number of events -- clear hw-module sub x/y cardtype to clear out alarms, or remove card.

Error Message %NSP_OIR-3-LONGSTALL: Long bus stall ([int] s), the new PAM may not seated properly. Please remove it and try again.

Explanation The card is bad or not properly seated.

Recommended Action Remove card and reinsert into chassis. If problem persists, the card is probably bad.

Error Message %NSP_OIR-4-INV_REDCFG: Redundancy submode not present!

Explanation System config does not have Redundancy submode.

Recommended Action Configure redundancy submode for this platform.

Error Message %NSP_OIR-6-FULL_CINS: Card [chars] inserted into slot: [dec]

Explanation Full card inserted into slot.

Error Message %NSP_OIR-6-FULL_CREM: Card [chars] removed from slot: [dec]

Explanation Full card removed from slot.

Error Message %NSP_OIR-6-FULL_ONLINE: Card [chars], slot: [dec], being brought online

Explanation Full card being brought online.

Error Message %NSP_OIR-6-HALF_CINS: Card [chars] inserted into subslot: [dec]/[dec]

Explanation Half-height card inserted into subslot.

Error Message %NSP_OIR-6-HALF_CREM: Card [chars] removed from subslot: [dec]/[dec]

Explanation Half-height card removed from subslot.

Error Message %NSP_OIR-6-HALF_ONLINE: Card [chars], subslot: [dec]/[dec], being brought online

Explanation Half-height card being brought online.

C.4.15 OC3SUNI Error Messages

Error Message %OC3SUNI-1-INITFAIL: msgtxt_initfail

Error Message %OC3SUNI-1-NOMEMORY: msgtxt_nomemory

Error Message %OC3SUNI-3-BADUNIT: msgtxt_badunit

Error Message %OC3SUNI-3-SPURIDON: msgtxt_spuriousidon

C.4.16 OIR Error Messages

Error Message %OIR-3-SHUTDOWN: Shutting down due to overheat

Explanation System shutdown due to overheat error.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %OIR-6-INSCARD: Card inserted in slot [dec], subcard [dec], interfaces administratively shutdown

Explanation Card inserted in the slot for sub card, port, and interfaces was administratively shut down.

Recommended Action This message is provided for information only.

Error Message %OIR-6-REMCARD: Card removed from slot [dec], subcard [dec], interfaces disabled

Explanation Card inserted in the slot for sub card, port, and interfaces was disabled.

Recommended Action This message is provided for information only.

Error Message %OIR-3-LONGSTALL: Long bus stall ([dec] [chars]), the new PAM may not seated properly. Please remove it and try again.

Explanation While hot swapping a PAM, the system detected the card is not seated properly.

Recommended Action Remove the card and reinsert it.

C.4.17 Port Adapter Module Mailbox Errors

Error Message %PAMMBOX-3-BADCONFIG: Bad mailbox config data 0x[hex], 0x[hex]

Explanation An error was found in the mailbox config data.

Error Message %PAMMBOX-3-BADRXFRMHDR: [dec] [dec] [dec] [dec] 0x[hex] 0x[hex] 0x[hex]

Explanation A received PAM mailbox message frame has a bad header.

Error Message %PAMMBOX-3-BADSTATUS: Bad mailbox status data 0x[hex], 0x[hex]

Explanation An error was found in the mailbox status data.

Error Message %PAMMBOX-3-INITERROR: Initialization Error: [chars]

Explanation An error occurred during the subsystem initialization.

Error Message %PAMMBOX-3-PLATADDSLOT: Platform add slot error [dec], [dec]

Explanation The platform-dependent add slot routine failed.

Error Message %PAMMBOX-3-PLATDELETESLOT: Platform delete slot error [dec], [dec]

Explanation The platform-dependent delete slot routine failed.

Error Message %PAMMBOX-3-RXBADSTATE: RX mailbox in illegal state [dec] [dec]

Explanation The RX mailbox has interrupted as owned but state is not owned.

Error Message %PAMMBOX-3-RXNOIDB: RX a message but no NRP IDB for slot [dec] subslot[dec]

Explanation A message has been received but no IDB exists for the given slot/subslot.

Error Message %PAMMBOX-3-RXQWAKEUPREASON: Unknown wakeup reasons: [dec] [dec]

Explanation The RX packet Q process woke up for unknown reason.

Error Message %PAMMBOX-3-TXBADSTATE: TX mailbox in illegal state [dec] [dec] [dec]

Explanation The TX mailbox is owned and empty, but output queue is not empty.

Error Message %PAMMBOX-3-TXOUTERR: Transmit Message Output Error: [dec] [dec] [dec] [dec]

Explanation Sanity checks on a transmit message failed.

Error Message %PAMMBOX-3-TXPAKERR: Transmit Message No Packet

Explanation TX message cannot get a packet.

Error Message %PAMMBOX-3-TXRXBADINITSTATE: TX/RX mailbox owned in illegal initial state [dec] [dec]

Explanation The TX/RX mailbox is in an illegal initial ownership state.

Error Message %PAMMBOX-3-UNEXPECTEDINT: Unexpected PAM Mailbox Interrupt: [chars]

Explanation Sanity checks on a transmit message failed.

C.4.18 PNNI/IISP Error Messages

Error Message %PNNI-2-NO_INTERNAL_NUMBER:

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: failed to get the argument to pnni_hello process, pid = , pdb->pid

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Can't find node included in ACK header: , *pnni_nodeid_string(node_id)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Cannot relocate PTSE component

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR : Can't find node included in ACK header: pnni_nodeid_string(node_id)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Hello state machine error in state error_msg, pnni_idb->port_id

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: IF table full, cannot add new interface port

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Unknown timer type, expired_timer

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Attempt to add a PTSE but Node doesn't exist pnni_nodeid_string(node_id), ptse_id

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Cannot add NNI interface port

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: retbuffer(pak)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: PNNI relocation of addr failed, could not find pfx

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Can't find our own node in PTSE database

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Cannot add NNI interface, uninitialized pointers ios_idb

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Cannot locate neighbor to be deleted

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Duplicate node, pnni_nodeid_string(node_id)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Duplicate PTSE of, pnni_nodeid_string(node_id), ptse_id)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Getting Node Id For An Invalid Node

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: IISP failed to get, the argument to iisp_router process, pid = , pdb->pid)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Internal Nbr Number Stack Overflow

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Null element to deq_ptse

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: NULL node in ptsedb ID, , ptsedb->ptse_data->ptse_id)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Out Of Parse Buffers

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: PNNI: Service orig timer, but PTSE is NULL!!!, , ptsedb)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Rcv DS in an invalid nbr state

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Received API message to create an interface for an existing port,, port)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Remove neighbor with interface list not empty

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: removing our own PTSE ID 1, \nplse collect \show atm pnni trace buf, ptse)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: rxmt timer with no element.

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-3-INTERNAL_ERROR: Unrecognized req msg from signaling, msg->op_code

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-INTERNAL_ERROR: IISP failed to get the argument to iisp_router process

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-BADPACKET: Hello, len_err_str, ((pnni_ptse_hdr_t *)hello)->ptse_type, TLV_LEN(hello)

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-BADPACKET: Nodal REQ, Contains Unknown Mandatory IG, req_hdr, req_hdr->type

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-BADPACKET: PTSE ACK, Has No Nodal PTSE Acks, ack_pkt->type, TLV_LEN((pnni_tlv_t *)ack_pkt))

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-BADPACKET: PTSE ACK, Has No Nodal PTSE Acks, pnni->type, TLV_LEN((pnni_tlv_t *)pnni))

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-BADPACKET: PTSE ACK, len_err_str, ((pnni_ptse_hdr_t *)ptse_ack)->ptse_type, TLV_LEN(ack))

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-BADPACKET: PTSE len_err_str, ((pnni_ptse_hdr_t *)ptse)->ptse_type, TLV_LEN((pnni_tlv_t *)ptse))

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-BADPACKET: PTSP, Has Unknown Mandatory IG At Top Level, ptsp, ptsp->type

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-BADPACKET: REQ Contains Unknown Mandatory IG At Top Level req_pkt, req_pkt->type

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-BADPACKET: REQ error_msg, 0, 0); } req_hdr = pnni_get_next_tlv((pnni_tlv_t)pnni, (pnni_tlv_t)req_hdr

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-BADPACKET: REQ, len_err_str, ((pnnihdr_t *)req)->type, TLV_LEN(req))

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-BADROUTEREQ: msg->op_code )

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-CONFIG_ERROR: Port looped-back, cannot form adjacency

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-CONFIG_ERROR: Missing PNNI VC on NNI interface.

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-CONFIG_ERROR: Neighbor in different PeerGroup

Explanation An internal error occurred.

Recommended Action If this message occurs, contact your technical support representative for assistance.

Error Message %PNNI-4-INTERNAL_ERROR: Unrecognized req msg from signaling [hex]

Explanation Unrecognized request message from signaling error process.

Recommended Action If this message occurs, contact your technical support representative for assistance.

C.4.19 RSP Error Messages

Error Message %RSP-2-BADCACHE: Possible cache overrun detected. End of MEMD buffer : 0x[hex] End of datagram : 0x[hex] bufhdr [hex]: [hex] [hex] [hex] [hex] Flushing Cache

Explanation A packet greater than the maximum possible MTU was processed. Or, an illegal buffer header data area was found.

Recommended Action Call your technical support representative for support.

Error Message %RSP-2-NOMEMORY: No memory available for [chars]

Explanation An attempt at memory allocation failed.

Recommended Action Try these actions to remedy the problem: Add memory. 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 %RSP-2-QADIAG: QA Diagnostic [chars] error at [hex]

Explanation An error occurred while accessing RSP internal hardware.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %RSP-2-QAERROR: [chars] error, [chars] at addr [hex] ([chars]) log [hex], data [hex] [hex]

Explanation A software error was detected during packet switching.

Recommended Action Call your technical support representative for support.

Error Message %RSP-2-STALL: partially inserted or removed IPs on cyBus[int]

Explanation Most likely, a board is not fully seated in the chassis. A less likely possibility is a hardware problem with the RSP or backplane.

Recommended Action Try reseating the boards. Call your technical support representative for assistance if this message persists.

Error Message %RSP-3-ACCERROR: [chars] acc [hex] had bad value [dec]

Explanation An incorrect value has been written on an accumulator.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. A micro reload can correct the error condition as a workaround.

Error Message %RSP-3-BADBUFHDR: [chars], address [hex]

Explanation A software or hardware error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %RSP-3-BADHWREV: [chars] (slot [int]) has wrong hardware revision [int].[int]

Explanation The hardware in the indicated slot needs to be upgraded for operation with the RSP.

Recommended Action Upgrade the board.

Error Message %RSP-3-BADTURBOIPCMSG: Bad Turbo IPC msg ([chars]): msg=[hex] lastmsg=[hex] hdrsize=[hex] size=[hex]

Explanation An error was discovered in an IPC message.

Error Message %RSP-3-ERROR: NULL

Explanation This message can take many forms. It provides information about a software error.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %RSP-3-FOREVER: cmd [int] to [chars] (slot [int]) took [int] usecs, done [hex]

Explanation A command from the RSP to an IP took longer than expected.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %RSP-3-IDPROM: Bad or missing ID EEPROM, controller type [int]

Explanation The ID EEPROM on the RSP is missing or bad.

Recommended Action This message indicates a manufacturing error. Report this error to your technical support representative.

Error Message %RSP-3-INVQPTR: queue=[hex], bufhdr [hex]: [hex] [hex] [hex] [hex]

Explanation A software or hardware error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %RSP-3-INVRTN: Invalid return queue, next=[hex], hwidb=[hex], type=[hex] queue_ptr=[hex], bufhdr_offset=[hex], id=[dec], bcast_id=[dec] bufhdr [hex]: [hex] [hex] [hex] [hex]

Explanation A software or hardware error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %RSP-3-INVRTNBCASTID: Invalid return queue bcast_id=[dec] bufhdr [hex]: [hex] [hex] [hex] [hex]

Explanation A software or hardware error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %RSP-3-IPC: [chars] [chars]

Explanation An Interprocess Communication (IPC) error occurred. The details about what was attempted and what went wrong will be printed.

Recommended Action Copy the error message exactly as it appears. Copy down the router's configuration along with any other relevant information. Contact your technical support representative for assistance.

Error Message %RSP-3-IP_PANIC: Panic: [chars] [hex] [hex] [hex] [hex]

Explanation Firmware for the interface processor experienced a critical condition.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative, along with the output of "show tech-support."

Error Message %RSP-3-LOVEGIANT: Card [chars] wants [dec] byte love letters, but only got [dec] bytes

Explanation An inconsistency between the microcode and the system code was detected.

Recommended Action Report this error to your technical support representative.

Error Message %RSP-3-LOVENOTE: [hex] corrupt: [hex] [hex] [hex] [hex]

Explanation This message indicates miscommunication between the RSP and an IP.

Recommended Action Report this error to your technical support representative.

Error Message %RSP-3-MSDOG: Master/slave watchdog timed out

Explanation The system software failed to reset the master/slave watchdog timer, causing it to time out. This behavior could indicate a software problem or a hardware problem.

Error Message %RSP-3-MSFIX: Fixing [chars] by setting to default [chars]

Explanation The characters shown can be either on the slave RSP setting or on the master RSP setting. The ROM monitor default slave RSP setting is not synchronized with the system configuration file specifications. During bootup, the system image detects the mismatch and modifies the ROM monitor setting to conform with these specifications. This mismatch most likely occurred because a new RSP was being installed and booted in a high system availability (HSA) environment (dual RSPs) for the first time. Alternatively, in established HSA configurations, this message may result from a previous Interprocess Communication (IPC) error occurring while the HSA environment is reconfigured.

Recommended Action Using the show version or show boot command, determine which slot contains the current slave RSP. Using the show config command, determine which slot has been specified as the default slave RSP. If there is no slave default-slot n command in the configuration file, the value defaults to the highest numbered CPU slot (slot 3 on a Cisco 7507, and slot 7 on a Cisco 7513). If the slot number obtained in Step 1 is the same as the number obtained in Step 2, then no further action is required. You have configured HSA in simple hardware backup mode, and both RSPs are identical. However, if the two slot numbers differ, you have configured HSA in software error protection mode, and will have different images running, depending on which RSP is currently the slave RSP. If the slot numbers discovered in Steps 1 and 2 differ, reload your router to ensure that the desired system image is running. After the reload, the actual slave RSP will match the default slave RSP specified in (or inferred from) the system configuration file. For details of various HSA configuration modes consult the Cisco IOS Configuration Fundamentals Configuration Guide. See the "Loading System Images and Configuration Files" chapter (Cisco 7500 series only).

Error Message %RSP-3-MSVERS: Master has m/s version [dec], slave has m/s version [dec]

Explanation The master and slave are running incompatible software versions with regards to the master/slave exchange process.

Recommended Action If the slave image global configuration is used to override the default slave image from the bundle, then the slave image is incompatible. Update either the master or slave image to ensure the two are compatible. If the slave is running the image from the bundle, execute and record the output of show version, more system:running-config, and show controller cbus commands. Report this information and the error message to your technical support representative.

Error Message %RSP-3-NOIDB: bad vc [int] on [chars]

Explanation A channelized interface driver received a packet on an unconfigured channel.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative, along with the output of "show tech-support."

Error Message %RSP-3-NOMAC: Can't allocate MAC address for interface [int]/[int]

Explanation No MAC address was available for allocation to the specified interface.

Recommended Action Report this error to your technical support representative.

Error Message %RSP-3-NORESTART: [chars]: unable to schedule restart for output queue

Explanation A software or hardware error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %RSP-3-NOSTART: No microcode for [chars] card, slot [int]

Explanation No microcode is defined or available for the specified card.

Recommended Action Reconfigure the card to specify an existing microcode file.

Error Message %RSP-3-RESTART: NULL

Explanation The cBus buffer memory was reset and reallocated.

Recommended Action Report this error to your technical support representative, if memory is not reset manually (by changing the MTU on an interface, for example).

Error Message %RSP-3-SLAVECHANGE: Slave changed state from [chars] to [chars]

Explanation The slave RSP has undergone a hardware state change. Both the old state and new state are shown. Possible states are nonparticipant, slave, master, and unplugged. Possible state changes indicated by the above message are any to unplugged, unplugged to nonparticipant or slave, nonparticipant to slave, slave to nonparticipant. Any other combination is unexpected.

Recommended Action Depending on the cause of the alarm, perform one of the following tasks:

The slave RSP has been removed. Consider reinstalling it if continued high system availability (HSA) operation is required. If the slave RSP is present, ensure that it is properly seated in the card cage.
A slave RSP has been installed. Configure the router for HSA. See the Configuration Fundamentals Configuration Guide in the "Loading System Images and Configuration Files" chapter for more details. In particular, use the slave sync config command to ensure that the new slave RSP is configured consistently with the current master RSP. CAUTION: Failure to ensure a consistent configuration on a freshly installed slave RSP might result in undefined behavior if the router reloads.
A previously crashed slave RSP has been reset, or a newly installed slave RSP is in transition from unplugged to nonparticipant, and finally to slave state. No action is required.
The slave RSP image has crashed. Log in to the slave RSP's console using the if-console slot command. You will now be connected to the ROM monitor prompt on the slave RSP. Diagnose the slave RSP failure. For example, capture the output from the stack and context ROM monitor commands. Provide that information to your technical support representative, along with the router's configuration and any other relevant information, so that the problem can be investigated. Log out from the slave RSP's console port using Ctrl-c or Ctrl-z, and enter the slave reload global configuration command on the master RSP to bring the slave RSP back online. All other state changes indicate a software or hardware error. Provide the router's configuration and any other relevant information to customer support so that the problem can be investigated.

Error Message %RSP-3-SLAVEMASTER: Slave stole mastership

Explanation The master RSP detected that the slave RSP had taken mastership of the router. The old master RSP will reload and become the slave RSP, letting the new master RSP take over. This behavior indicates a software or hardware error.

Error Message %RSP-3-SLAVE_NVRAM_BUSY: Slave NVRAM is temporarily busy

Explanation Another process is temporarily locking the slave config.

Recommended Action Retry the command that caused the error message. If the error message recurs, check for other execs via the show users command. If you know that there are no other users locking the slave NVRAM, then contact your technical support representative for assistance.

Error Message %RSP-3-XBUFHDR: corrupt bufhdr [hex]: [hex] [hex] [hex] [hex]

Explanation Miscommunication occurred between the RSP and an IP.

Recommended Action Report this error to your technical support representative.

Error Message %RSP-4-COOKIE: Corrupt or missing MAC address cookie using random base [sci_notation]

Explanation This message indicates the part containing the MAC addresses allocated to this chassis could not be accessed or was found to be corrupt, either due to a hardware problem or manufacturing problem.

Recommended Action Report this error to your technical support representative.

Error Message %RSP-4-HSA_MEM: size mismatch, master [int]MB, slave [int]MB

Explanation Memory size mismatch between master and slave RSP.

Recommended Action Configure both master and slave RSPs to have an equal amount of memory.

Error Message %RSP-4-HSA_MINMEM: [int]MB required for HSA

Explanation HSA requires a minimum of 24 MB of memory.

Recommended Action Upgrade your system to meet minimum memory requirements for HSA.

Error Message %RSP-4-RSPDRAM: Insufficient DRAM to adequately run this IOS version. [dec]M is recommended.

Explanation The quantity of RSP DRAM is below the recommended amount.

Recommended Action Add DRAM.

Error Message %RSP-5-SLAVEUP: Slave changed to state Running

Explanation This is an informational message to indicate that the slave RSP has started running the slave RSP image. This message appears after the router boots or after the slave reload global configuration command is issued on the master RSP.

Recommended Action No action required.

C.4.20 SONICT Driver Error Messages

Error Message %SONICT-1-INITFAIL: msgtxt_initfail

Error Message %SONICT-1-NOMEMORY: msgtxt_nomemory

Error Message %SONICT-3-INTERNAL_ERROR: [chars] [chars]

Error Message %SONICT-3-OWNERR: msgtxt_ownerror

Error Message %SONICT-3-SPURIDON: msgtxt_spuriousidon

Error Message %SONICT-3-XMIT_ERR: [chars]: TX Error: status = 0x[hex]

Table of Contents

Resolving Error Messages