Cisco 6400 Series Broadband Aggregators

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

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

[dec]

Decimal number

[hex]

Hexadecimal number

[char]

Single character

[chars]

Character string

%AAL5-1-NOMEMORY: msgtxt_nomemory

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

%AAL5-3-INTERNAL_ERROR: [chars]

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

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

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

%ALARM-1-CRITICAL_ALARM: CRITICAL alarm condition 
detected

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

%ALARM-1-CRITICAL_ALARM: CRITICAL alarm condition 
detected

A critical alarm event has occurred and will cause a serious result. This error needs immediate attention and resolution. The system will shut down within two minutes.

Check the source of the critical alarm to take corresponding actions. Do not turn on power unless the situation is corrected.

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

%ALARM-2-MAJOR_ALARM: Major alarm condition 
detected

A major alarm event has occurred and will affect system service. This error needs immediate attention and resolution.

Check the source of the major alarm to take corresponding actions. This situation should be corrected or noted.

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

%ALARM-3-MINOR_ALARM: Minor alarm condition 
detected

A minor alarm event has occurred. It does not affect system service but needs attention.

Check the source of the minor alarm to prevent the situation from becoming a major event.

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

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

This message can occur for these unrelated reasons:

• Address Resolution Protocol (ARP) is allowed only on AAL5SNAP virtual circuits.

• The virtual path identifier-virtual channel identifier (VPI-VCI) pair or the VCD is already in use.

• Only one virtual channel connection (VCC) is allowed on a point-to-point interface.

• AAL3/4-SMDS virtual circuit must be the only virtual circuit on an interface.

• AAL3/4-SMDS multiplex ID exceeds the maximum.

• Switched Multimegabit Data Service (SMDS) is not enabled.

• The driver failed to accept the virtual circuit.

If none of these actions solve the problem, copy the error message exactly as it appears and report it to your technical support representative.

• Change the encapsulation to AAL5SNAP.

• Try a different VPI-VCI number.

• Use a different subinterface.

• Turn off AAL3/4.

• Use a smaller multiplex ID value.

• Enable SMDS.

• Initiate the virtual circuit again.

%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]

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

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

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

The system attempted to allocate some memory but failed.

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

%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.

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

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.

%ATM-4-ILMIKEEPALIVEFAIL: Restarting ATM signaling 
and ILMI. Keepalive failure detected.

Adjacent peer device is not responding to Interim Local Management Interface (ILMI) Keepalive polling.

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 the warning message exactly as it appears, and report it to your technical support representative.

%ATM-4-ILMICONFIGCHANGE:

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

Wait for the interface to restart.

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

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

No action is required.

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

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

No action is required.

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

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

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.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

%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

An internal error occurred.

Contact your technical support representative for assistance.

%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)

An internal error occurred.

Contact your technical support representative for assistance.

%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)

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

%ATMSIG-3-ENQFAIL: enqueue atmsig_cb.pnni_queue 
atm_ys_msg->ret_code = IPC_ASYNC

An internal error occurred.

Contact your technical support representative for assistance.

%ATMSIG-3-ENQFAIL: enqueue atmSig_outputQ 

An internal error occurred.

Contact your technical support representative for assistance.

%ATMSIG-3-FAILASSERT: [chars]

ATM signaling found an internal critical error.

Contact your technical support representative for assistance.

%ATMSIG-3-FAILXCONN: xconn fail

An internal error occurred.

Contact your technical support representative for assistance.

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

An invalid message was received from routing. The number of ports is greater than the maximum.

Contact your technical support representative for assistance.

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

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

Contact your technical support representative for assistance.

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

An invalid message was received from a PNNI routing error. A null message was received.

Contact your technical support representative for assistance.

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

An invalid message was received from routing. The message type is not valid.

Contact your technical support representative for assistance.

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

An invalid message was received from routing. The source process is not valid. It must be a routing module.

Contact your technical support representative for assistance.

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

An invalid message was received from routing. The destination process is not valid. It must be a signaling module.

Contact your technical support representative for assistance.

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

An invalid message was received from routing. There is a null current party.

Contact your technical support representative for assistance.

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

An invalid message was received from routing. There is no signaling control block.

Contact your technical support representative for assistance.

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

An invalid message was received from routing. The message code is not responding.

Contact your technical support representative for assistance.

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

An invalid message was received from routing. The message version is bad.

Contact your technical support representative for assistance.

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

An invalid message was received from routing. The message is null.

Contact your technical support representative for assistance.

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

ATM signaling failed. There is a half-leg removal error.

Contact your technical support representative for assistance.

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

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

Contact your technical support representative for assistance.

%ATMSIG-3-NOMEM: [chars]

ATM signaling could not allocate memory.

Contact your technical support representative for assistance.

%ATMSIG-3-NOSVC: no SVC, atmSig_findPartyBlockByRef

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

Contact your technical support representative for assistance.

%ATMSIG-3-NOSVC: no SVC, atmSig_input

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

Contact your technical support representative for assistance.

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

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

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

The chassis fan does not exist.

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

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

The processor card is overheated. The temperature has exceeded the critical limit. An automatic shutdown results if the condition prevails for more than two minutes.

Possible causes for this error are a malfunctioning fan or a shorted circuit on the processor card.

Check the temperature of the processor card and determine whether the fan is malfunctioning.

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

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

The environment is overheated. The temperature has exceeded the critical limit. An automatic shutdown results if the condition prevails for more than two minutes.

Possible causes for this error are a malfunctioning fan.

Check the temperature next to the chassis intake and determine whether the fan is malfunctioning.

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

%CI-1-NOFAN: Fan tray empty

The chassis fan does not exist.

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

%CI-1-TOTALFANFAIL: Complete fan failure

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

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

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

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

Install the required amount of RAM and try again.

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

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

Before you continue, copy the error message exactly as it appears and report it to your technical support representative.

%CI-3-BLOWER: Fan failure

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

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

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

The processor card is overheated. The temperature has exceeded the major limit.

Possible causes for this error are a malfunctioning fan or a shorted circuit on the processor card.

Check the temperature of the processor card and determine whether the fan is malfunctioning.

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

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

The processor card is overheated. The temperature has exceeded the minor limit. Possible causes for this error are a malfunctioning fan or a shorted circuit on the processor card.

Check the temperature of the processor card and determine whether the fan is malfunctioning.

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

%CI-3-FCTYPE: Cannot recognize Feature Card

The feature card is not recognized by the software. There is a software/hardware incompatibility.

Copy the error message exactly as it appears. Issue the show tech-support command to determine the nature of the error.

If you cannot determine the nature of the error from the message text or from the show tech-support output, call your technical support representative and provide the representative with the message text and the command output.

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

The environment is overheated. The temperature has exceeded the major limit.

A possible cause for this error is a malfunctioning fan.

Check the temperature next to the chassis intake and verify that the fan is not malfunctioning.

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

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

The environment is overheated. The temperature has exceeded the minor limit.

A possible cause for this error is a malfunctioning fan.

Check the temperature next to the chassis intake and verify that the fan is not malfunctioning.

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

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

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

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

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

Copy the error message exactly as it appears. Issue the show tech-support command to determine the nature of the error.

If you cannot determine the nature of the error from the message text or from the show tech-support output, call your technical support representative and provide the representative with the message text and the command output.

%CI-3-PARTFANFAIL: Single fan failure

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

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

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

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

Copy the error message exactly as it appears. Issue the show tech-support command to determine the nature of the error.

If you cannot determine the nature of the error from the message text or from the show tech-support output, call your technical support representative and provide the representative with the message text and the command output.

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

The chassis power supply's fan has failed.

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

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

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

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

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

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

Copy the error message exactly as it appears. Issue the show tech-support command to determine the nature of the error.

If you cannot determine the nature of the error from the message text or from the show tech-support output, call your technical support representative and provide the representative with the message text and the command output.

%CI-6-BLOWEROK: Fan OK

The chassis fan is working correctly.

No action is required.

%CI-6-CORETEMPOK: Core Temperature OK

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

No action is required.

%CI-6-INLETTEMPOK: Inlet Temperature OK

The temperature next to the chassis intake is normal.

No action is required.

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

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

No action is required.

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

The chassis power supply fan is normal.

No action is required.

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

The chassis power supply is normal.

No action is required.

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

An internal error in the IDB has occurred. The interface cannot be selected as a network clocking source.

Select another interface as the network clocking source.

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

All the configured network clocking sources have failed.

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

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

The specified network clocking source has failed.

Restore proper operation of the selected interface.

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

The specified network clocking source is operational.

No action is required.

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

The FC-PFQ clock is not operational, bypassing.

No action is required.

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

The FC-PFQ clock is not operational, bypassing.

No action is required.

%EHSA-3-EHSA_ALARMS: [chars]

An enhanced high system availability (EHSA) alarm assertions error occurred. Details about the error event will be printed.

Copy the error message exactly as it appears, the system configuration, and all other relevant information and report it to your technical support representative.

%EHSA-3-FSM: [chars]

An EHSA Finite State Machine (FSM) error occurred. Details about the error event will be printed.

Copy the error message exactly as it appears, the system configuration, and all other relevant information and report it to your technical support representative.

%EHSA-3-GENERAL: [chars]

An EHSA error occurred. Details about the error event will be printed.

Copy the error message exactly as it appears, the system configuration, and all other relevant information and report it to your technical support representative.

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

An Interprocess Communication (IPC) error occurred. Details about the error event will be printed.

Copy the error message exactly as it appears, the system configuration, and all other relevant information and report it to your technical support representative.

%EHSA-3-PEER_MONITOR: [chars]

An EHSA Peer Monitor error occurred. Details about the error event will be printed.

Copy the error message exactly as it appears, the system configuration, and all other relevant information and report it to your technical support representative.

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

A file system error has occurred.

Copy the error message exactly as it appears. Issue the show tech-support command to determine the nature of the error.

If you cannot determine the nature of the error from the message text or from the show tech-support output, contact your technical support representative for assistance.

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

The status of a file system has changed.

Follow the instructions provided with the message. No further action is required.

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

The status of the field programmable gate-array (FPGA) is abnormal when available bit rate (ABR) is being handled. This might be due to an internal code error.

Copy the error message exactly as it appears. Issue the show tech-support command to determine the nature of the error.

If you cannot determine the nature of the error from the message text or from the show tech-support output, contact your technical support representative and provide the representative with the message text and the command output.

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

Either the hardware Done pin or Status pin is not properly set in the FPGA.

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

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

The download failed for the given FPGA version. This might be due to a code error.

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

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

The status of the FPGA is abnormal during multicast. This might be due to an internal code error.

Copy the error message exactly as it appears. Issue the show tech-support command to determine the nature of the error.

If you cannot determine the nature of the error from the message text or from the show tech-support output, contact your technical support representative and provide the representative with the message text and the command output.

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

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

Remove the new PAM from the slot and re-insert it.

If the error message recurs, copy it exactly as it appears, and report it to your technical support representative.

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

The status pin is not functioning properly in FPGA.

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

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

The status of the FPGA is abnormal when traffic is being handled. This might be due to an internal code 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 message text or from the show tech-support output, contact your technical support representative and provide the representative with the message text and the command output.

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

The feature card might be new or the software installed does not support the feature card due to new features/incompatibilities.

Update your software to a later version.

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

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

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

Update the version of the feature card.

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

%IPC_RSP_CBUS-3-CARDERR: [chars]

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

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

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

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

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

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

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

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

%IPC_RSP_CBUS-3-NOBUF: [chars]

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

Reduce the number of applications that currently run on the IPC.

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

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

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.

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

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

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

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

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

An internal error occurred.

Download the system error log, and then call your technical support representative and provide the log, the error message, and the switch configuration.

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

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.

Enter a name that is 32 characters or less.

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

A Token Ring-emulated LAN was specified, which is not currently supported.

Specify an Ethernet-emulated LAN.

Note: Future software releases will support Token Ring ELANs.

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

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

Wait for the initial lane server-bus command to either succeed or fail. You can check the status of the server bus by issuing the show lane server-bus interface <subinterface name> command.

Note: You cancel this command 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 entire interface.

Lastly, issue the no interface <subinterface name> command followed by the shutdown, no shutdown command cycle.

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

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

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

%LANE-3-LANE_SIG_ERR: [chars]

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

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

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

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

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

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

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

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

%LANE-6-LEC: [chars]

A hardware or software error occurred.

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

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

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

If you expect the switch to assign the prefix to the switch, make sure that the ILMI is functional and that the switch has a prefix configured. Otherwise, confirm that the client has an address in the nonvolatile RAM (NVRAM) configuration.

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

A software or hardware error occurred.

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

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

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

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

%LANE-6-LEC_INFO: [chars]

A software or hardware error occurred.

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

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

A software or hardware error occurred.

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

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

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

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

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

ATM signaling sent the client an unexpected message type.

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

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

A hardware or software error occurred.

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

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

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

%LANE-3-LECS_ERR: [chars]

An internal consistency error occurred.

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

%LANE-4-LECS_WARN: [chars]

The LANE configuration server address could not be registered with or unregistered 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.

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

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

A hardware or software error occurred.

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

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

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

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

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

An internal error occurred.

Download the system error log, and then call your technical support representative and provide the log, the error message, and the switch configuration.

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

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.

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.

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

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

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

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

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.

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 MAC address.

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

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

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

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

An internal error occurred.

Download the system error log, then call your technical support representative and provide the log, the error message, and the switch configuration.

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

An internal error occurred.

Download the system error log, then call your technical support representative and provide the log, the error message, and the switch configuration.

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

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

This is an informational message.

No action required.

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

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.

Issue the no lane server-bus command to delete the server/BUS or issue 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.

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

Entering a new ATM address template for a LANE component caused the specified LANE server or bus to drop all clients and restart. This is an informational message.

No action required.

%LANE-3-NOILMI: ILMI service registration failed

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

Reload the switch with software that includes the ILMI feature.

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

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

Wait a minute and try again. If it fails again, shut down the main interface. Rebooting may be required to recover in extreme cases.

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

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.

If the situation persists after several attempts and the switch is up, examine the switch configuration. The most likely cause is that the ATM address being registered is not compatible with the parameters configured in the switch (for example, the ATM address prefix).

Correct the configuration.

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

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. Another attempt to register will be made.

If the situation persists after several attempts and the switch is up, examine the configurations of the switch and router. A likely cause is that the ATM address being registered is not compatible with the parameters configured in the switch.

Correct the configuration.

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

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. Another attempt to register will be made.

If the situation persists after several attempts and the switch is up, examine the configurations of the switch and router. A likely cause is that the ATM address being registered is not compatible with the parameters configured in the switch. Correct the configuration.

%LANE-3-NOVCD: VCDs exhausted

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

Increase the number of PVCs by issuing the atm maxvc command.

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

The characters in [chars] 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.

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

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

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.

Correct the configuration.

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

An internal error occurred.

Download the system error log, then call your technical support representative and provide the log, the error message, and the switch configuration.

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

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.

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.

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

A software or hardware error occurred.

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

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

A software or hardware error occurred.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

%NRP-1-NOMEMORY: msgtxt_nomemory

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

%NRP-3-BADUNIT: msgtxt_badunit

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

%NRP-3-SPURIDON: msgtxt_spuriousidon

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

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

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

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

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

%NSP-1-NOMEMORY: msgtxt_nomemory

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.

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

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

There is an invalid slot-type pointer.

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

SONET line warning.

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

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

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

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

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

There is an internal online insertion and removal (OIR) element allocation failure. This usually indicates a memory leak.

This problem will not affect normal operation, but you will be unable to add/remove hardware and bring it online.

Restart/reboot.

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

A card inserted in the system is not recognized by software.

Replace the card or upgrade the software on the NSP.

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

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

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

There is a redundancy/card conflict with cards in an adjacent slot.

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

There is a redundancy/card conflict with cards in an adjacent slot.

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

The card inserted is not the same type as the one previously removed and so is invalid.

Insert a card similar to the one that was previously removed or clear the alarm source.

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

Cards present in the chassis in the current mode are incompatible.

Issue the clear hw-module sub x/y cardtype command to clear the alarms, or remove the card.

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

Cards present in the chassis in the current mode are incompatible.

Issue the clear hw-module sub x/y cardtype command to clear alarms, or remove the card.

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

The card is bad or not properly seated.

Remove the card and insert it again into the chassis. If the problem persists, the card is probably bad.

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

System configuration does not have a redundancy submode.

Configure redundancy submode for this platform.

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

A full card is inserted into the slot.

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

A full card is removed from the slot.

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

A full card is being brought online.

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

A half-height card is inserted into a subslot.

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

A half-height card is removed from a subslot.

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

A half-height card is being brought online.

%OC3SUNI-1-INITFAIL: msgtxt_initfail

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

%OC3SUNI-1-NOMEMORY: msgtxt_nomemory

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

%OC3SUNI-3-BADUNIT: msgtxt_badunit

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

%OC3SUNI-3-SPURIDON: msgtxt_spuriousidon

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

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

The system shut down due to an overheating error.

Contact your technical support representative for assistance.

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

A card was inserted in the slot. Subcard, port, and interfaces were administratively shut down.

This message is provided for information only.

No action is required.

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

A card was inserted in the slot. Subcard, port, and interfaces were disabled.

This message is provided for information only.

No action is required.

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

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

Remove the card and insert it again.

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

An error was found in the mailbox configuration data.

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

There is a bad header in a received PAM mailbox message frame.

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

An error was found in the mailbox status data.

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

An error occurred during the subsystem initialization.

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

The platform-dependent add slot routine failed.

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

The platform-dependent delete slot routine failed.

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

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

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

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

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

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

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

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

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

Checks on a transmit message failed.

%PAMMBOX-3-TXPAKERR: Transmit Message No Packet

The TX message cannot get a packet.

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

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

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

Verification checks on a transmit message failed.

%PNNI-2-NO_INTERNAL_NUMBER:

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

%PNNI-3-INTERNAL_ERROR: Cannot relocate PTSE 
component

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

%PNNI-3-INTERNAL_ERROR: Attempt to add a PTSE but 
Node does not exist pnni_nodeid_string(node_id), 
ptse_id

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

%PNNI-3-INTERNAL_ERROR: retbuffer(pak)

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

%PNNI-3-INTERNAL_ERROR: Null element to deq_ptse

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

%PNNI-3-INTERNAL_ERROR: Out Of Parse Buffers

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

%PNNI-3-INTERNAL_ERROR: rxmt timer with no element

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

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

An internal error occurred.

Contact your technical support representative for assistance.

%PNNI-4-CONFIG_ERROR: Missing PNNI VC on NNI 
interface

An internal error occurred.

Contact your technical support representative for assistance.

%PNNI-4-CONFIG_ERROR: Neighbor in different 
PeerGroup

An internal error occurred.

Contact your technical support representative for assistance.

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

There is an unrecognized request message from the signaling error process.

Contact your technical support representative for assistance.

%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

A packet greater in size than the maximum transmission unit (MTU) was processed, or an illegal buffer header data area was found.

Call your technical support representative for assistance.

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

An attempt at memory allocation failed.

Perform one of these:

• Add memory.

• Disable some features.

• Apply filtering to decrease the size of system data structures; for example, the routing table.

• In general, reduce other system activities to ease memory demands.

If conditions warrant, upgrade to a larger memory configuration.

%RSP-2-QADIAG: QA Diagnostic [chars] error at [hex]

An error occurred while accessing RSP internal hardware.

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

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

A software error was detected during packet switching.

Call your technical support representative for assistance.

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

A board is not fully seated in the chassis or there is a hardware problem with the RSP or backplane.

Reseat the boards.

If this message persists, call your technical support representative for assistance.

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

An incorrect value has been written on an accumulator.

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

As a workaround, do a micro reload to correct the error condition.

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

A software or hardware error occurred.

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

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

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

Upgrade the board.

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

An error was discovered in an IPC message.

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

%RSP-3-ERROR: NULL

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

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

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

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

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

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

The ID EEPROM on the RSP is missing or bad. This message indicates a manufacturing error.

Contact your technical support representative.

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

A software or hardware error occurred.

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

%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]

A software or hardware error occurred.

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

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

A software or hardware error occurred.

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

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

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

Copy the error message exactly as it appears, the router configuration, and all other relevant information and report it to your technical support representative.

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

Firmware for the interface processor experienced a critical condition.

Copy the error message exactly as it appears. Issue the show tech-support command. Report the error message and the output of the show tech-support command to your technical support representative.

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

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

Contact your technical support representative.

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

This message indicates miscommunication between the RSP and an IP.

Contact your technical support representative.

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

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

Copy the error message exactly as it appears, the router configuration, and all other relevant information and report it to your technical support representative.

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

The characters shown can be 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 can result from a previous Interprocess Communication (IPC) error occurring while the HSA environment is reconfigured.

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 slave RSP will match the default slave RSP specified in (or inferred from) the system configuration file.

For details of various HSA configuration modes, refer to the Cisco IOS Configuration Fundamentals Configuration Guide. See the "Loading System Images and Configuration Files" chapter (Cisco 7500 series only).

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

The master and slave are running incompatible software versions for the master/slave exchange process.

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, perform and record the output of the show version, more system:running-config, and show controller commands. Report this information and the error message to your technical support representative.

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

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

Copy the error message exactly as it appears. Issue the show tech-support command. Report the error message and the command output to your technical support representative.

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

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

Report this error to your technical support representative.

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

A software or hardware error occurred.

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

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

No microcode is defined or available for the specified card.

Reconfigure the card to specify an existing microcode file.

%RSP-3-RESTART: NULL

The cBus buffer memory was reset and re-allocated.

If memory is not reset manually (for example, by changing the MTU on an interface), report the error to your technical support representative.

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

The slave RSP has undergone a hardware state change. Both the old and new states are shown. Possible states are nonparticipant, slave, master, and unplugged. Possible state changes indicated by the message:

• any to unplugged

• unplugged to nonparticipant or slave

• nonparticipant to slave

• slave to nonparticipant

Any other combination is unexpected.

Perform one of these steps, which depends on the cause of the alarm:

• 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 console using the if-console slot command. You will 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, the router configuration, and all other relevant information to your technical support representative. Log out from the slave RSP 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 configuration and all other relevant information to your technical support representative so that the problem can be investigated.

%RSP-3-SLAVEMASTER: Slave stole mastership

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 have control. This behavior indicates a software or hardware error.

Copy the error message exactly as it appears, the router configuration, and all other relevant information and report it to your technical support representative.

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

Another process is temporarily locking the slave configuration.

Retry the command that caused the error message. If the error message recurs, check for other execs by issuing 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.

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

Miscommunication occurred between the RSP and an IP.

Report this error to your technical support representative.

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

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

Report this error to your technical support representative.

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

Memory size mismatch between master and slave RSP.

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

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

HSA requires a minimum of 24 MB of memory.

Upgrade your system to meet minimum memory requirements for HSA.

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

The quantity of RSP DRAM is below the recommended amount.

Add DRAM.

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

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.

No action required.

%SONICT-1-INITFAIL: msgtxt_initfail

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

%SONICT-1-NOMEMORY: msgtxt_nomemory

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

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

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

%SONICT-3-OWNERR: msgtxt_ownerror

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

%SONICT-3-SPURIDON: msgtxt_spuriousidon

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

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

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