Полезная информация

cc/td/doc/product/software/ios120/12supdoc
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

FPGA Error Messages
FR Error Messages
FR_ELMI Error Messages
FR_LMI Error Message
FTC_TRUNK Error Message
FTPSERVER Error Messages
FW Error Messages
GRIP Error Messages
GRP Error Messages
GRPPOS Error Messages
GSR_ENV Error Messages
GSRIPC Error Messages
GT64010 Error Messages
HAWKEYE Error Messages
HD Error Messages
HMM_ASYNC Error Messages
HOOD Error Messages
HP100VG Error Messages
HUB Error Messages
IBM2692 Error Messages
IDMGR Error Messages
IDTATM25 Error Messages
IFS Error Messages
IGRP Error Message
ILACC Error Messages
INTERFACE_API Error Messages
IP Error Messages
IPACCESS Error Messages
IPC Error Messages
IPCGRP Error Messages
IPCLC Error Messages
IPC_RSP_CBUS Error Messages

FPGA Error Messages

LS1010 chip-specific error messages


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

Explanation   The ABR FPGA chip failed to respond to a reset command during hardware shutdown.

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   
%FPGA-2-DONE_PIN: Done pin or Status pin isn't pull low, FPGA# [dec]

Explanation   The specified FPGA chip showed an incorrect status after downloading its control microcode. This is probably caused by a hardware failure. It is a fatal condition for the system and will be followed by a core dump.

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   
%FPGA-2-DOWNLOAD: Download Fail, FPGA# [dec]

Explanation   The specified FPGA chip failed to respond after downloading its control microcode. This is probably caused by a hardware failure. It is a fatal condition for the system and will be followed by a core dump.

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   
%FPGA-3-MCAST: Multicast FPGA didn't reset properly, Control Register=[hex]

Explanation   The Multicast FPGA chip failed to respond to a reset command during hardware shutdown.

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   
%FPGA-3-NOFORK: Can't create Per VC Counter daemon

Explanation   The software could not spawn a per-VC counter process. This is not a normal condition, and will prevent collection of statistics on the VC. It was probably caused by a low-memory condition.

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


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

Explanation   The specified FPGA chip showed an incorrect status after downloading its control microcode. This is probably caused by a hardware failure. It is a fatal condition for the system and will be followed by a core dump.

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   
%FPGA-3-TRAFF: Traffic FPGA didn't reset properly, Control Register=[hex]

Explanation   The Traffic FPGA chip failed to respond to a reset command during hardware shutdown.

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   
%FPGA-3-TYPE: ***WARNING*** Invalid feature card type -
Use higher version of software: [hex]

Explanation   The Cisco IOS software found an unrecognized feature card during Cisco LS1010 initialization. This probably means that the software must be upgraded in order to support hardware that did not exist at the time the software was written.

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   
%FPGA-3-VERSION: Feature Card version invalid/old. Feature Card Version:[dec].[dec], ASP Version:[dec].[dec]

Explanation   There is a version mismatch between a feature card and the ASP.

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.

FR Error Messages

Frame Relay error messages


Error Message   
%FR-5-DLCICHANGE: Interface [chars] - DLCI [dec] state changed to [chars]

Explanation   The state of the Frame Relay PVC specified by the data-link connection identifier (DLCI) changed.

Recommended Action   This is a notification message only. No action is required.


Error Message   
%FR-4-DLCIDELETE: Interface [chars] - DLCI [dec] - PVC use count [dec]

Explanation   An attempt was made to remove a PVC DLCI while it was still being used.

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


Error Message   
%FR-3-INCORRECT_INT: Incorrect output (sub)interface, broadcast packet dropped!

Explanation   The output subinterface specified in the packet is incorrect. The broadcast packet was dropped.

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


Error Message   
%FR-4-NNISUBINTF: Subinterface not supported on Frame Relay NNI

Explanation   An attempt was made to change the state of a subinterface on the Frame Relay Network-to-Network Interface (NNI).

Recommended Action   Reconfigure the Frame Relay link type or remove the subinterface.


Error Message   
%FR-3-NOMEMORY: No memory for [chars]

Explanation   The requested operation could not be accomplished because of a low memory condition.

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


Error Message   
%FR-3-NULL_INT: Null output interface. Broadcast packet dropped!

Explanation   Output interface is NULL; broadcast packet is dropped.

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

FR_ELMI Error Messages

Frame Relay enhanced Local Management Interface error messages


Error Message   
%FR_ELMI-3-INCORRECT_ID: Incorrect ID

Explanation   The ID in the QOS parameter message is incorrect.

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


Error Message   
%FR_ELMI-3-INCORRECT_IE: Incorrect IE

Explanation   Enhanced LMI is not configured on the interface. The frame was dropped.

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

FR_LMI Error Message

Frame Relay Local Management Interface error message


Error Message   
%FR_LMI-3-INCORRECT_IE: Enhanced LMI not configured, incorrect IE

Explanation   An unexpected LMI information element has been received.

Recommended Action   Verify the configuration for enhanced LMI on the switch matches the configuration on the router.

FTC_TRUNK Error Message

Cisco 3801 platform error message


Error Message   
%FTC_TRUNK-3-CID_IN_USE: [chars] connection-id [dec] is busy, try other cid

Explanation   An attempt was made to use a connection ID that is already assigned and in use; the selected connection ID cannot be used for this session-trunk.

Recommended Action   Try again with a connection ID that is not already in use.


Error Message   
%FTC_TRUNK-1-NOMEMORY: msgtxt_nomemory

Explanation   The MC68360/QUICC CPU was unable to access the memory it needs to carry out its functions. Here are some possible causes. The network is large, requiring a great deal of memory for routing tables, and so on. The router configuration has many features enabled, each of which require a certain amount of memory. A software error (memory leak) exists.

Recommended Action   Reduce system activity to ease the memory demand, or upgrade to a larger memory configuration.


Error Message   
%FTC_TRUNK-1-RELOAD: Must reload to config Interface [chars] as ftc-trunk again

Explanation   If an interface configured as encapsulation ftc-trunk is reconfigured to another encapsulation (such as HDLC), this error message is displayed when the attempt is made to reconfigure it again as encapsulation ftc-trunk. The reload command must be entered before attempting to configure the interface to encapsulation ftc-trunk again.

Recommended Action   Issue the reload command.


Error Message   
%FTC_TRUNK-3-TOOMANY: Cannot config more than [dec] ftc-trunks

Explanation   If there are already four interfaces configured for encapsulation ftc-trunk and the encapsulation ftc-trunk configuration command is issued, this message is displayed to indicate that no more can be configured.

Recommended Action   Free one of the other interfaces first or if conditions warrant, upgrade to a larger configuration with more interfaces.


Error Message   
%FTC_TRUNK-3-TOOMANY_SESSION: Cannot config more than [dec] session-trunks

Explanation   If there are already four interfaces configured for encapsulation ftc-trunk and the encapsulation ftc-trunk configuration command is issued, this message is displayed to indicate that no more can be configured.

Recommended Action   Free one of the existing interfaces before trying again or if conditions warrant, upgrade to a larger configuration.

FTPSERVER Error Messages

FTP server processes error messages


Error Message   
%FTPSERVER-6-CONNCLOSED: Connection closed after [dec] seconds. '[chars]'

Explanation   The FTP connection to a client was closed after 5 minutes of inactivity.

Recommended Action   Client inactivity will cause the server to shutdown the connection.


Error Message   
%FTPSERVER-6-CWDFAILED: setcwd failed ([chars])

Explanation   A FTP client request failed to change to the requested directory.

Recommended Action   Verify the correct path for the desired directory.


Error Message   
%FTPSERVER-6-NETRDFAILED: FTP control connection / tcp_read failed

Explanation   An error occurred while reading the command line from the FTP client.

Recommended Action   Verify the network connection from client to server and verify the FTP client operation.


Error Message   
%FTPSERVER-6-NETWRTFAILED: FTP Server:connection / tcp_write failed

Explanation   A TCP write failed while sending an FTP command reply to the client.

Recommended Action   Verify the network connection from client to server and verify the FTP client operation.


Error Message   
%FTPSERVER-6-NEWCONN: FTP Server - new connection made

Explanation   A new FTP server connection has opened.

Recommended Action   FTP server connections can be disabled by using the command no ftp-server enable.


Error Message   
%FTPSERVER-6-REPLYLOGN: (REPLY) [dec]

Explanation   An FTP login has occurred.

Recommended Action   This is an informational message only. Informational messages can be disabled by changing logging level.


Error Message   
%FTPSERVER-6-REPLYLOGTEXT: [dec][chars]

Explanation   This text was sent to the FTP client.

Recommended Action   This is an informational message only. Informational messages can be disabled by changing logging level.


Error Message   
%FTPSERVER-6-TOPDIRTEST: Input path failed Top-dir([chars]) test

Explanation   An operation attempted to use a path not within the tree under the ftp-server topdir configuration parameter.

Recommended Action   Reconfigure the server topdir parameter, or select another path.


Error Message   
%FTPSERVER-4-XFER_WARNING: File may not have transferred correctly

Explanation   Extra linefeeds were received in ASCII mode

Recommended Action   The file may be OK. If the file did not transfer correctly, try using a different FTP client.

FW Error Messages

Inspection subsystem error messages


Error Message   
%FW-4-ALERT_OFF: [chars], count ([dec]/[dec]) current 1-min rate: [dec]

Explanation   Either the number of half-open connections or the new connection initiation rate has gone below the max-incomplete low threshold. This message indicates that the rate of incoming new connections has slowed down and is issued only when the max-incomplete low threshold is crossed.

Recommended Action   This message is for informational purposes only, but may indicate that an attack has stopped.


Error Message   
%FW-4-ALERT_ON: [chars], count ([dec]/[dec]) current 1-min rate: [dec]

Explanation   Either the max-incomplete high threshold of half-open connections or the new connection initiation rate has been exceeded. This error message indicates that an unusually high rate of new connections is coming through the firewall, and a DOS attack may be in progress. This message is issued only when the max-incomplete high threshold is crossed.

Recommended Action   This message is for informational purposes only, but may indicate a security problem.


Error Message   
%FW-2-BLOCK_HOST: Blocking new TCP connections to host [int] for [dec] minute[chars] (half-open count [dec] exceeded)

Explanation   This message indicates that any subsequent new TCP connection attempts to the specified host will be denied because the max-incomplete host threshold of half-open TCP connections is exceeded, and the blocking option is configured to block the subsequent new connections. The blocking will be removed when the configured block-time expires.

Recommended Action   This message is for informational purposes only, but may indicate that a SYN flood attack was attempted.


Error Message   
%FW-3-FTP_NON_MATCHING_IP_ADDR: Non-matching address [int] used in [chars] -- FTP client [int] FTP server [int]

Explanation   An FTP client attempted to use a PORT command or the FTP server attempted to use the response to a PASV command to trick the firewall into opening access to a third-party host that is different from the two hosts engaged in the FTP connection. This message indicates that a suspicious violation was detected while attempting to modify the security policy in the firewall. The command is rejected and the connection is reset by the firewall.

Recommended Action   This message is for informational purposes only, but may indicate that an attempt was made to grant or open access to unauthorized hosts.


Error Message   
%FW-3-FTP_PRIV_PORT: Privileged port [dec] used in [chars] -- FTP client [int] FTP server [int]

Explanation   An FTP client attempted to use a PORT command or the FTP server attempted to use the response to a PASV command to trick the firewall into opening access to a privileged port. This message indicates that a suspicious violation was detected from the FTP client/server attempting to modify the security policy in the firewall. The command is rejected and the connection is reset by the firewall.

Recommended Action   This message is for informational purposes only, but may indicate that an attempt was made to gain access to privileged ports.


Error Message   
%FW-3-FTP_SESSION_NOT_AUTHENTICATED: Command issued before the session is authenticated -- FTP client [int] FTP server [int]

Explanation   An FTP client attempted to use the PORT command or an FTP server attempted to use the response to a PASV command to open a data channel in the firewall prior to the client's successful authentication with the server. This is a suspicious attempt by the client/server to trick the firewall into opening a hole so that outside attackers can take advantage of the firewall opening. This message indicates that a suspicious violation was detected, and the PORT or PASV command/response is rejected by the firewall. The data channel in the firewall will not be opened until the authentication is done successfully.

Recommended Action   This message is for informational purposes only, but may indicate that an illegal attempt was made to modify the firewall security policy.


Error Message   
%FW-4-HOST_TCP_ALERT_ON: Max tcp half-open connections ([dec]) exceeded for host [int].

Explanation   The max-incomplete host limit of half-open TCP connections has been exceeded. This message indicates that a high number of half-open connections is coming to the protected server, and may indicate that a SYN flood attack is in progress and is targeted to the specified server host.

Recommended Action   This message is for informational purposes only, but may indicate that a SYN flood attack was attempted. If this alert is issued frequently and identified to be mostly false alarms, then the max-incomplete host threshold value is probably set too low, and there is a good deal of legitimate traffic coming in to that server. In this case, the max-incomplete host parameter should be set to a higher number to avoid false alarms.


Error Message   
%FW-3-HTTP_JAVA_BLOCK: JAVA applet is blocked from ([int]:[dec]) to ([int]:[dec])

Explanation   A Java applet was seen in the HTTP channel, and the firewall configuration indicates that the applet from this Web site should be prohibited. The message indicates that the applet is being downloaded from one of the prohibited sites and its entrance to the protected network is not allowed. The connection is reset and the transmission of the detected applet is aborted immediately.

Recommended Action   This message is for informational purposes only, but may indicate a security problem.


Error Message   
%FW-3-NOTFOUND: Session context for ([int]:[dec]) => ([int]:[dec]) not found.

Explanation   The CBAC code was searching its database for information for a particular inspection session, but this information was not found.

Recommended Action   If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.


Error Message   
%FW-6-SESS_AUDIT_TRAIL: [chars] session initiator ([int]:[dec]) sent [int] bytes -- responder ([int]:[dec]) sent [int] bytes

Explanation   This message documents the per-session transaction log of network activities. The message is issued at the end of each inspected session and it records the source/destination addresses and ports, as well as the number of bytes transmitted by the client and server.

Recommended Action   This message is for informational purposes only, and can be used to collect the basic accounting for the inspected sessions.


Error Message   
%FW-3-SMTP_INVALID_COMMAND: Invalid SMTP command from initiator ([int]:[dec])

Explanation   The CBAC code detected an invalid SMTP command in the inspected SMTP connection. This message indicates that a suspicious violation was detected that may be an attack to the mail server system. The command is rejected and the connection is reset by the firewall immediately.

Recommended Action   This message is for informational purposes only, but may indicate a security problem.


Error Message   
%FW-4-UNBLOCK_HOST: New TCP connections to host [int] no longer blocked

Explanation   New TCP connection attempts to the specified host are no longer blocked. This message indicates that the blocking of new TCP attempts to the specified host has been lifted.

Recommended Action   This message is for informational purposes only, but may indicate a SYN flood attack was attempted to the host.

GRIP Error Messages

Xerox Network Systems (XNS) Routing Protocol error messages


Error Message   
%GRIP-3-BADPATHS: Invalid number of paths ([dec]) for [dec]

Explanation   An internal inconsistency was detected in the XNS routing table structure.

Recommended Action   Note the parameters associated with this message and call your technical support representative for assistance.


Error Message   
%GRIP-2-BADROUTE: Error [chars] route - null table

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.

GRP Error Messages

Gigabit route processor (RP) error messages


Error Message   
%GRP-3-ADDRERROR: Bad access to fabric-buffers: invalid address

Explanation   This message indicates that an illegal access was made to fabric buffers. This usually indicates a software error.

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


Error Message   
%GRP-4-BADLENGTH: Internal fabric register mismatch.
Expected length = [int]. Received length = [int]

Explanation   This message indicates that a packet was received from the fabric but the length received and the length indicated in the buffer header do not match.

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   
%GRP-4-BAD_PKT: CSAR: Received slot [int] Chan [int]

Explanation   A bad packet was received at CSAR.

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   
%GRP-3-BAD_RESET:

Explanation   Software attempted to reset itself over the MBUS.

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   
%GRP-3-BAD_STATE: Slot:[int] State:[chars]

Explanation   A message send was attempted to a card that was in an incorrect state. The card and state are shown in the error message.

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


Error Message   
%GRP-3-BADSTATE: Reassembly state is bad for slot [int]. State = [int]

Explanation   This message indicates that software is in an incorrect state for receiving the current packet over the fabric. The message indicates the slot the packet was received on and the state the reassembly was in.

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   
%GRP-3-BMAUCODE_ALLOC: Failed buffer allocation for [chars]

Explanation   Could not allocate a data structure to contain contents of the given BMA microcode file. There may be insufficient DRAM.

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   
%GRP-3-BMAUCODE_BAD: Slot [dec]: bad slot state ([dec]) or card type ([hex] - [chars])

Explanation   Unable to select or download the given BMA microcode on the given slot. The line card is either not present, there is a card that is not a line card in the given slot, or the line card is not enabled.

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   
%GRP-3-BMAUCODE_ENABL: No line cards enabled: selector [chars], feature [chars]

Explanation   Selection or download of the BMA microcode failed for all slots, selector and feature. There are no enabled line cards.

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   
%GRP-3-BMAUCODE_FAIL: Slot [dec], selector [chars], feature [chars]

Explanation   Selection or download of the BMA microcode failed for the given slot, selector and feature. The line card could be disabled or there was an error on the line card when attempting to select or download the BMA microcode.

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


Error Message   
%GRP-3-BMAUCODE_FILE: Error reading [chars]

Explanation   Could not read the given binary BMA microcode, possibly because it is not found.

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


Error Message   
%GRP-3-BMAUCODE_SELECTOR: Command selector [chars] != file header selector [chars]

Explanation   For the BMA microcode download command, the selector specified on the command line does not match that in the binary BMA microcode file.

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   
%GRP-4-CAMFULL: Too many entries in the Ethernet CAM

Explanation   This message indicates that too many MAC addresses were put into the Ethernet's CAM. This usually indicates a software error.

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


Error Message   
%GRP-3-CARVE_ADD: Failed to add buffer size [unsigned long] with delta [int]

Explanation   Could not add the given buffer size to the SDRAM buffer carve specification because of internal parameter errors: exceeded available number of elements, excessive delta size, or null parameters.

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   
%GRP-3-CARVE_FAIL: [chars] BMA, slot [int]

Explanation   SDRAM buffer carve on the given line card failed, the RP failed to send the line card the carve information via IPCs, or the carve result from the line card failed to return to the RP. The line card could be disabled at this point.

Recommended Action   Try rebooting the line card. If this fails to fix the problem, consider power cycling the router. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%GRP-3-CARVE_FREEQS: Free queues ([int]) > allowed ([int])

Explanation   The number of free queues allowed for SDRAM buffer carving has been exceeded.

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   
%GRP-4-CARVE_MTU: Only [int] MTUs considered (max = [dec])

Explanation   The list of different MTUs that can be considered in SDRAM buffer carving is limited by the given maximum number.

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   
%GRP-3-CARVE_PCT: Sum percentage SDRAM buffers ([int]) > 100

Explanation   The specified sum of percentages for SDRAM buffer sizes has exceeded 100.

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   
%GRP-3-CARVE_SIZE: SDRAM buffer size [unsigned long] < its delta [unsigned long]

Explanation   Rounded-up SDRAM buffer size should be larger than a given delta size.

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   
%GRP-3-CARVE_SPEC: Empty SDRAM buffer carve specification

Explanation   There is no SDRAM buffer carve specification to send to a line card.

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


Error Message   
%GRP-3-CARVE_ZERO: [chars] BMA, slot [int], entry index [int]: zero SDRAM buffer size

Explanation   The given SDRAM buffer size should not be zero.

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   
%GRP-4-CELLNEG: Detected an internal signal error on the fabric interface

Explanation   This message indicates an internal signal between the CSAR and the FIA was deasserted too early.

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   
%GRP-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 because of a hardware problem or manufacturing problem.

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   
%GRP-4-CORRUPT: Corrupted packet received. start_offset = [int]
length = [int] card = [int]

Explanation   This message indicates that a buffer was received from the fabric with a corrupted buffer header.

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   
%GRP-4-CRC32: CRC32 error detected from slot [int]

Explanation   This message indicates that a CRC32 error was detected.

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


Error Message   
%GRP-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 on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%GRP-4-ETHERPAL: Ethernet PAL on the GRP is missing

Explanation   The system software detected that the Ethernet PAL on the GRP is either missing or is improperly installed.

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   
%GRP-3-EXEC_ALLOC: No memory for command

Explanation   No memory was available to allocate for the remote command string.

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   
%GRP-3-EXEC_ENABL: No line cards enabled

Explanation   There are no enabled line cards.

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   
%GRP-3-EXEC_SLOT: Slot [dec] not enabled

Explanation   There is no card in the given slot or it exists but is not enabled.

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   
%GRP-3-FABCOPY: [chars] address = 0x[hex].

Explanation   This message indicates that the fabric driver software passed an incorrectly aligned pointer.

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   
%GRP-3-FABRIC: [chars] ([int])

Explanation   The master gigabit route processor is unable to communicate over the fabric to the line card that is displayed in the error message.

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


Error Message   
%GRP-3-FABRIC_MULTI: [chars] ([hex])

Explanation   A problem has been detected between the master RP and a line card over the fabric.

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   
%GRP-3-FABRIC_UNEXP: [chars] ([int])

Explanation   An expected message was received from the line card indicated in the error message.

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


Error Message   
%GRP-3-FABRIC_UNI: [chars] ([int])

Explanation   A problem has been detected between the master RP and a line card over the fabric.

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   
%GRP-4-FIRSTLAST: First/Last cell error detected from slot [int]

Explanation   This message indicates that a cell was received with an invalid first or last bit set.

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   
%GRP-4-FROMFABPAR: Parity error detected in from fabric buffer memory. Slot [int]

Explanation   This message indicates that a parity error was detected from the fabric buffers.

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   
%GRP-3-IFCON: Too many Queued messages, No buffers available

Explanation   This message indicates that there are too many messages coming from the GSR line card. There are no more buffers on the RP to handle these messages. Try shutting down debugs on the line card or reloading it.

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


Error Message   
%GRP-3-LC_POST_ALLOC: Failed buffer allocation for [chars]

Explanation   Could not allocate a data structure to contain contents of the given line card POST file. There may be insufficient DRAM.

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   
%GRP-3-LC_POST_FAIL: Slot [dec] fail download

Explanation   Download of the GLC POST failed for the given slot. The line card could be disabled or there was an error on the line card when attempting to download the GLC POST.

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   
%GRP-3-LDFAIL: Unable to download ucode from [chars] in slot [hex] (bitmask), trying [chars] ucode

Explanation   For some reason, the line card image specified by the configuration is not suitable for downloading, or another error occurred. The line card image that is bundled within the GRP's system image will be loaded.

Recommended Action   Attempt to reload the microcode. 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   
%GRP-3-MEMSIZE: Non oct-byte access to fabric buffers

Explanation   This message indicates that an illegal access was made to fabric buffers. This usually indicates a software error.

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


Error Message   
%GRP-3-MODULE: Missing [chars] for [chars]

Explanation   A hardware or software error occurred.

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


Error Message   
%GRP-3-MSGTOOBIG: Datagram size too large ([int])

Explanation   This message indicates that a packet was attempted to be sent over the fabric but was too large to be sent. This usually indicates a software error.

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


Error Message   
%GRP-3-NOFILE: Ucode file [chars] not found, system ucode loaded in slot [hex] (bitmask).

Explanation   The file specified by the configuration was not found in Flash. The slot number represents a bit mask of the cards affected. The line card image that is bundled within the GRP's system image will be loaded.

Recommended Action   Use the show flash command to determine if the file is located in Flash. If the file is there, attempt to reload the microcode. 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   
%GRP-4-NO_INTF: CSAR: No interface available Slot [int] Chan [int]

Explanation   CSAR received a packet with no valid interface.

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


Error Message   
%GRP-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   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   
%GRP-4-OLDVERSION: Running old version of GRP

Explanation   The system software detected an old version of the GRP.

Recommended Action   The GRP must be upgraded in order to run with this software.


Error Message   
%GRP-3-PARITYERR: Parity error detected in the fabric buffers. Data ([hex])

Explanation   A parity error was detected by the fabric interface hardware on the RP. The hex number indicates the error interrupt vector. This usually indicates a hardware problem on the RP.

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   
%GRP-3-POST_CODE_FILE: Error reading [chars], post.ucode is required in slot0 for upgrade

Explanation   Could not read the given binary LC POST code, possibly because it is not found post.ucode in PCMCIA card.

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


Error Message   
%GRP-4-Q_CORRUPT: CSAR: HoldQ Count is corrupted

Explanation   CSAR: Queue indicates a packet even though no packet is available.

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   
%GRP-3-QFULLPAR: Parity error detected

Explanation   This message indicates that a parity error was detected between the CSAR and the FIA on the queue full signals. This usually indicates a hardware error.

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


Error Message   
%GRP-4-REASSEMBLY: Reassembly error detected. Slot = [int].
State = [int], Status = [int]

Explanation   This message indicates that there has been an error in reassembling a buffer over the fabric. The message indicates the slot that the errored packet was received on and the state that the reassembly was in. The status of the packet can be decoded as follows: (00 - middle buffer), (01 - last buffer), (10 - first buffer), (11 - only buffer).

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   
%GRP-3-RESET_CARD: Card [int] has reset too many times

Explanation   The line card specified in the error message automatically reset itself too many times in attempts to overcome an error condition. It will attempt a reload again after 10 minutes. This probably indicates that the card is either incorrectly installed, misconfigured or experiencing a hardware failure.

Recommended Action   Check the configuration and cabling for errors. The line card can be reloaded manually using the microcode reload command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%GRP-3-RESTART: NULL

Explanation   The SDRAM buffer memory was reset and reallocated. If this was a result of an operator-issued command (changing the MTU on an interface, for example) then this is not cause for concern.

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


Error Message   
%GRP-4-RXFAB: From fabric buffers are out of order with software.
Index = [int], Expected = [int], Received = [int]

Explanation   This message indicates that the fabric driver software is out of sync with the fabric hardware.

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


Error Message   
%GRP-4-SEQUENCE: Sequence error detected from slot [int]. Expected [int]

Explanation   This message indicates that a cell was received with an incorrect sequence number.

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   
%GRP-3-TYPE: Unknown link type [int] int [int]/[int]

Explanation   A packet was received on an interface that had an unknown link type. This most likely indicates a software problem.

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   
%GRP-3-UCODEFAIL: [chars] [int]

Explanation   The image that was downloaded to the line card was rejected by the line card.

Recommended Action   Attempt to reload the microcode. 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   
%GRP-3-UCODETIMEOUT: [chars] ([int])

Explanation   The line card did not acknowledge the download of the image.

Recommended Action   Attempt to reload the line card image. 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   
%GRP-3-UNDEF_HDR: Slot [int]:[hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]

Explanation   This message indicates that a packet was received from the fabric but there was a problem in the header. The data that appear are the first bytes from the buffer header and payload.

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   
%GRP-4-UNEXPBUFFER: Unexpected buffer finished sending to fabric ([int]).

Explanation   This message indicates that a to-fabric buffer completed sending. However software was not expecting this buffer to be completed.

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   
%GRP-3-UNEXPINT: [chars] [hex]

Explanation   An unexpected interrupt occurred from a device on the GRP. The device that caused the interrupt is given in the error message output.

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.

GRPPOS Error Messages

POS route processor (RP) driver error messages


Error Message   
%GRPPOS-4-MSGVERSION: Incompatible message version with slot [dec]

Explanation   The message version being sent by the line card is incompatible with the message version used by the GRP. This type of incompatibility could happen if the GRP and line card are using different Cisco IOS releases because of a GRP OIR event

Recommended Action   If the only problem is that pos statistics are not reported to the GRP, a microcode reload will solve the problem.


Error Message   
%GRPPOS-3-OP: Interface ([chars]): [chars]

Explanation   The POS RP driver received an unexpected event.

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


Error Message   
%GRPPOS-3-TIMEOUT: Interface ([chars]): [chars]

Explanation   The POS RP driver queried the line card for SONET information, but the line card did not reply.

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

GSR_ENV Error Messages

Gigabit Switch Router environment monitor error messages


Error Message   
%GSR_ENV-1-CRITICAL: Slot [dec] [chars] [dec] [chars] [chars] [dec] [chars]

Explanation   The slot environmental parameters are in the critical range. The card in the slot may be powered down for safety reasons.

Recommended Action   Rectify the condition immediately.


Error Message   
%GSR_ENV-1-CRITICAL_FAN: Slot [dec] [chars] [int] [chars]

Explanation   One or more fans are broken or missing. This may cause the chassis to overheat.

Recommended Action   Replace the bad fan tray.


Error Message   
%GSR_ENV-0-POWERDOWN: [chars] in slot [dec]

Explanation   The slot has been powered down for safety reasons.

Recommended Action   Rectify the specified condition before using the card again.


Error Message   
%GSR_ENV-0-SHUTDOWN: Slot [dec] [chars] [dec] [chars] [chars] [dec] [chars]

Explanation   The slot may be powered down for safety reasons. The card will be powered down after three warnings.

Recommended Action   Rectify the specified condition before using the card again.


Error Message   
%GSR_ENV-0-SHUTDOWN_PS: Slot [dec] [chars] [int] [chars]

Explanation   The power supply input voltage failed.

Recommended Action   Ensure that the power supply is plugged in and turned on.


Error Message   
%GSR_ENV-2-WARNING: Slot [dec] [chars] [dec] [chars] [chars] [dec] [chars]

Explanation   The specified slot environmental parameters are outside the normal range of operation.

Recommended Action   Rectify the warning condition specified. For example, for temperature warnings, verify that adequate cooling is available and that the empty slots have blank covers. For voltage warnings check the appropriate power supply. These conditions must be rectified immediately.

GSRIPC Error Messages

Gigabit Switch Router IPC service routines error messages


Error Message   
%GSRIPC-3-PORT: port ([chars]) already exists

Explanation   The port to be created exists already.

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


Error Message   
%GSRIPC-3-REXEC: [chars]

Explanation   This message indicates a remote execution open port failure.

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


Error Message   
%GSRIPC-3-SYSCALL: For port ([chars]): [chars] fails (cause: [chars])

Explanation   This message indicates an IPC kernel system call failure.

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

GT64010 Error Messages

GT64010 DMA controller driver error messages


Error Message   
%GT64010-3-DMA: Interrupt error, c=[hex], m=[hex], rc=[hex]

Explanation   An unexpected interrupt was registered from a DMA engine that was not initialized by software.

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


Error Message   
%GT64010-1-DMASTALL: DMA interrupt stalled, restarted engine [dec]

Explanation   The driver timed out while waiting for completion of a DMA task. The DMA engine has been restarted.

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   
%GT64010-3-NOCHANNEL: Referencing unused DMA channel [dec]

Explanation   Access to an uninitialized DMA engine was attempted.

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   
%GT64010-3-TIMER: Interrupt error, c=[hex], m=[hex], rc=[hex]

Explanation   An unexpected timer interrupt was received from a timer element that was not initialized by software.

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


Error Message   
%GT64010-3-TIMERINSTALL: Attempt to install already installed timer [dec]

Explanation   An attempt was made to initialize a timer element that is already in use.

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.

HAWKEYE Error Messages

Token Ring PCI port adapter error messages


Error Message   
%HAWKEYE-3-ADPCHK: Interface [chars], adapter check error

Explanation   The Token Ring interface encountered an unrecoverable error condition while it was operating and connected to the ring. The interface will automatically shut itself down.

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


Error Message   
%HAWKEYE-1-DISCOVER: Only found [dec] interfaces on bay [dec], shutting down bay

Explanation   This message may occur during Cisco IOS software initialization or after a Token Ring port adapter was inserted online. The message indicates that the Token Ring device driver was unable to communicate with all of the interfaces that are expected to be on the port adapter module. This could mean that one or more interfaces is not functioning.

Recommended Action   Reseat the port adapter in the slot. If necessary, install it in another available 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   
%HAWKEYE-3-INITFAIL: [chars] failed to initialize - [chars]

Explanation   The Token Ring interface encountered an error while attempting to open a connection to the ring. The specific error that occurred is indicated by the last half of the error message, described as one of the following:

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


Error Message   
%HAWKEYE-3-MAC_CMD_Q_OVERFLOW: HAWKEYE ([dec]/[dec]), MAC command queue overflow

Explanation   The interface's command queue was full when the device driver attempted to send a command to the interface hardware. This error message may occur if the device driver software sends commands faster than the interface hardware can process them. This condition is usually not a critical error and the interface should continue to function normally. However, if the error message recurs frequently, it may indicate a more serious problem.

Recommended Action   If the message recurs, contact your Cisco technical support representative. Otherwise, no action is required.


Error Message   
%HAWKEYE-1-NOPCIMEMORY: HAWKEYE ([dec]/[dec]), No PCI memory available

Explanation   The interface's device driver was unable to allocate the necessary amount of shared memory between the driver and the interface hardware. This condition can occur if the system contains less than the recommended minimum amount of SRAM for the current interface combination. Since shared memory blocks are required for the interface to function, this interface will be inoperable until the memory shortage is corrected.

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   
%HAWKEYE-1-OLDREV: HAWKEYE(bay [dec]), Port adapter requires Rev 2 CPU, shutting down bay

Explanation   This message is specific to Cisco 7200 series routers. It indicates that the device driver detected an NPE150 CPU version earlier than revision 2. The Token Ring device driver needs an NPE150 revision 2 or later CPU.

Recommended Action   Upgrade the Cisco 7200 router processor to an NPE150 revision 2 or later.

HD Error Messages

HD64570 serial controller error messages


Error Message   
%HD-1-BADLOOPCABLE: Loopback not supported for a 4T DTE/X.21, port [dec] in slot [dec]

Explanation   Loopback mode is not allowed when using an X.21 DTE cable on a Quad serial NIM port.

Recommended Action   Do not enable loopback, or use a different cable type.


Error Message   
%HD-1-BADPORTADAPTER: 4T Port Adapter fault on port [dec] in slot [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   
%HD-1-BADRING: msgtxt_badringsize

Explanation   An internal software error occurred.

Recommended Action   If message recurs, call your technical support representative for assistance.


Error Message   
%HD-5-LINEFLAP: Unit [dec] excessive modem control changes

Explanation   Too many modem control interrupts have been received. The port was disabled to prevent excessive use of the CPU.

Recommended Action   Check the cable on the serial port.

HMM_ASYNC Error Messages

Hex modem network module asynchronous driver error messages


Error Message   
%HMM_ASYNC-3-CARD_FAILED_DOWNLOAD: Unable to download firmware image to digital modem card in slot [dec]

Explanation   A processor failed to come up on the digital modem card.

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


Error Message   
%HMM_ASYNC-3-MODEM_FAILED_DIAGS: Digital modem [dec]/[dec] on Simm [dec] failed power on diagnostics.

Explanation   The digital modem did not pass the power diagnostics. It will not be used.

Recommended Action   If the remaining SIMMs pass diagnostics, remove or replace the problem SIMM before continuing. 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   
%HMM_ASYNC-3-MODEM_STOPPED_PROCESSING_MAIL: HMM Modem [dec]/[dec] failed to accept a new command.

Explanation   The modem did not accept a new command. This problem may be a transient failure or the modem may remain unusable until the system is reset.

Recommended Action   You may try to reset the modem by issuing the clear modem slot/port command. 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   
%HMM_ASYNC-3-NOMEMORY: No memory for [chars] of unit [dec]

Explanation   The router does not have enough memory to perform the function

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


Error Message   
%HMM_ASYNC-4-NO_MODEMS_PRESENT: HMM Digital Modem Card [dec] contains no active modems.

Explanation   There are no modems installed on the network module.

Recommended Action   Make sure the network module contains properly installed MICA-6DM SIMMs.


Error Message   
%HMM_ASYNC-3-NORAWRXPOOL: Unable to create pool for [dec] raw Rx mode buffers

Explanation   The router does not have enough I/O memory for buffers

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


Error Message   
%HMM_ASYNC-3-NORAWTXPOOL: Unable to create pool [dec] raw Tx mode buffers

Explanation   The router does not have enough I/O memory for buffers

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


Error Message   
%HMM_ASYNC-3-NOTTYCREATE: Unable to create TTY structure for line [dec]

Explanation   Unable to create TTY line control block for the specified line. This may be caused by not having enough memory in the router.

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


Error Message   
%HMM_ASYNC-3-SIMM_FAILED_DOWNLOAD: Unable to download modem firmware image to Simm [dec] in slot [dec].

Explanation   Modem firmware failed to load onto the SIMM.

Recommended Action   If firmware successfully loaded onto remaining SIMMs, remove or replace the problem SIMM before continuing. 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   
%HMM_ASYNC-3-SIMM_RUNTIME_ERROR: Simm [dec] in slot [dec] has halted due to a Runtime Error.

Explanation   The portware running on the SIMM was halted because of a runtime error. The six modems contained on the SIMM have been marked "bad" and are not usable until the system is reloaded.

Recommended Action   Copy the error message exactly as it appears, along with the output from the show modem and show modem log commands, and report it to your technical support representative.


Error Message   
%HMM_ASYNC-3-TDM_SYNTHESIS_ERROR: HMM Digital Modem Card [dec] experienced a TDM Synthesis Error

Explanation   The digital modem card failed to send or receive PCM data in time to avoid data loss. This may cause the modems to speed shift, retrain, or hangup.

Recommended Action   Verify that the DS1 interfaces share a common clock source. 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   
%HMM_ASYNC-3-UNKNOWN_MESSAGE: Received unknown message 0x[hex] at mail offset [dec] from modem [dec]/[dec].

Explanation   An unidentified message was received from the modem. This is symptomatic of running an incompatible version of modem firmware.

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


Error Message   
%HMM_ASYNC-3-UNKNOWNPLATFORM: Unknown Platform type to support HMM Network Module

Explanation   The network module is not compatible with the current platform that it is plugged in to.

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.

HOOD Error Messages

LAN controller 100VG-AnyLAN interface error messages


Error Message   
%HOOD-3-BADUNIT: msgtxt_badunit

Explanation   An internal software error occurred.

Recommended Action   If the message recurs, call your technical support representative for assistance.


Error Message   
%HOOD-5-CABLEERR: Unit [dec], HP100VG, cable error. Training failed

Explanation   A 100VG cable or hub is faulty.

Recommended Action   If the message recurs, and either the cable or hub appears to be good, repair or replace the router module.


Error Message   
%HOOD-5-COLL: Unit [dec], excessive collisions

Explanation   An Ethernet cable is broken or unterminated, or the transceiver is unplugged.

Recommended Action   If the transceiver appears to be properly terminated, repair or replace the router.


Error Message   
%HOOD-5-LOSTCARR: Unit [dec], lost carrier. Transceiver problem?

Explanation   An Ethernet transceiver is unplugged or faulty.

Recommended Action   Repair or replace the controller.


Error Message   
%HOOD-5-NOCABLE: Unit [dec], HP100VG, no tone detected. Check cable, hub

Explanation   A 100VG cable is faulty.

Recommended Action   If the message recurs, and either the cable or hub appears to be good, repair or replace the router module.

HP100VG Error Messages

100VF-AnyLAN PA driver error messages


Error Message   
%HP100VG-1-ACCESS: [chars] access to network denied

Explanation   Access to the network is denied because of incompatible configuration.

Recommended Action   Check the configuration of the hub for Frame Format, Promiscuous, and Repeater bit to indicate proper configuration.


Error Message   
%HP100VG-5-CABLEERR: [chars] training failed

Explanation   An 100VG cable or hub is faulty.

Recommended Action   Repair or replace the cable or hub. If the cable or hub appears to be good, repair or replace the VG PA interface module.


Error Message   
%HP100VG-1-DISCOVER: Only found [dec] interfaces on bay [dec], shutting down bay

Explanation   No VG interface detected.

Recommended Action   Ensure that 100VG PA is properly seated in the slot. Otherwise, repair or replace the 100VG PA interface module.


Error Message   
%HP100VG-1-DUPMAC: On [chars] LAN segment

Explanation   Two VG devices on the same LAN segment have the same MAC address.

Recommended Action   Check router configuration to ensure that no duplicate MAC address is configured.


Error Message   
%HP100VG-1-LANCNF: [chars] configuration not compatible with the network

Explanation   Configuration of the router module is not compatible with the network.

Recommended Action   Check the configuration of the hub for Frame Format, Promiscuous, and Repeater bit to indicate proper configuration.


Error Message   
%HP100VG-5-LOSTCARR: [chars] cable/hub problem?

Explanation   The VG controller detects a link to the hub is down because of a cable, hub or VG controller problem.

Recommended Action   Repair or replace the cable or hub. If either the cable or hub appears to be good, repair or replace the VG PA interface module.


Error Message   
%HP100VG-5-NOCABLE: [chars] cable fault; tone not detected

Explanation   An 100VG cable is faulty.

Recommended Action   Repair or replace the cable. If either the cable appears to be good, repair or replace the VG PA interface module.


Error Message   
%HP100VG-3-NOCAM: [chars] hardware CAM device not found

Explanation   Could not find Hardware CAM on the PA module.

Recommended Action   Repair or replace the 100VG PA interface module.


Error Message   
%HP100VG-3-NOTHP100VG: Bay [dec] device ID seen as [hex], expected [hex]

Explanation   Could not find 100VG PCI device.

Recommended Action   Ensure that the 100VG PA is properly seated in the slot. Otherwise, repair or replace the 100VG PA interface module.


Error Message   
%HP100VG-3-OWNERR: [chars] packet buffer, pak=0x[hex]

Explanation   A software or hardware error occurred. The HP100VG driver detected that the buffer ring is in an inconsistent and unrecoverable state.

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


Error Message   
%HP100VG-1-TRAINFAIL: [chars] unable to login to the hub

Explanation   Unable to login to the hub.

Recommended Action   Take action based on the error messages that follow.

HUB Error Messages

Cisco Ethernet hub error messages


Error Message   
%HUB-1-BADHUB: Invalid hub type [dec] and number [dec]

Explanation   An internal software error occurred.

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


Error Message   
%HUB-1-BADUNIT: Bad port number [dec]

Explanation   An internal software error occurred.

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


Error Message   
%HUB-1-NOMEMORY: msgtxt_nomemory

Explanation   The system detected that there is not enough memory for the hub initialization.

Recommended Action   If conditions warrant, upgrade to a larger memory configuration.


Error Message   
%HUB-1-READERR: Read op [dec] not allowed

Explanation   An internal software error occurred.

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


Error Message   
%HUB-1-WRITEERR: Write op [dec] not allowed

Explanation   An internal software error occurred.

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

IBM2692 Error Messages

Error messages which refer to an IBM Token Ring chip set


Error Message   
%IBM2692-1-DISCOVER: Only found [dec] interfaces on bay [dec], shutting down bay

Explanation   One of the interface controller devices on the module did not initialize properly.

Recommended Action   Power down, reinsert the network module, and reboot. If the message recurs, call your technical support representative for assistance.


Error Message   
%IBM2692-1-LL_QUEUE_OVERFLOW: IBM2692 ([dec]/[dec]), LL queue overflow.

Explanation   A packet buffer queue overflowed. This message indicates that a packet was lost, probably because of traffic congestion.

Recommended Action   A small number of queue overflows might not be a cause for concern. Reducing the load on the router or installing a higher-performance router should alleviate this problem.


Error Message   
%IBM2692-1-NOPCIMEMORY: [chars] [chars] creation failed

Explanation   The router or access server could not allocate memory for the descriptors.

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


Error Message   
%IBM2692-1-OLDREV: Bay [dec] port adapter requires Rev 2 CPU

Explanation   The Token Ring PCI port adapter driver depends on capabilities of the Revision 2 processor.

Recommended Action   Upgrade the processor to Revision 2.


Error Message   
%IBM2692-1-SRBQ_OVERFLOW: Queue size on [chars] exceeded [dec]

Explanation   The maximum number of commands that can be queued to the Token Ring port has been exceeded. Normally, such a problem is temporary, depending on transient peak loads within the system.

Recommended Action   The system should recover. No action is required.

IDMGR Error Messages

ID Manager error messages


Error Message   
%IDMGR-3-INTERRUPT: [chars]

Explanation   A id_get was attempted at the interrupt level.

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


Error Message   
%IDMGR-3-INVALID_ID: bad id in [chars]

Explanation   An ID Manager error occurred.

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


Error Message   
%IDMGR-3-MALLOC_FAILURE: [chars]

Explanation   A malloc failure occurred in ID Manager.

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.

IDTATM25 Error Messages

IDT ATM25 network module error messages


Error Message   
%IDTATM25-1-DISCOVER: Only found [dec] interfaces on bay [dec], shutting down bay

Explanation   The ATM25 network module hardware may be bad

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


Error Message   
%IDTATM25-3-FAILSETUPVC: Interface [chars], Failed to setup vc [dec] (Cause: [chars])

Explanation   The ATM25 network module hardware may be bad.

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


Error Message   
%IDTATM25-3-FAILTEARDOWNVC: Interface [chars], Failed to down vc [dec] (Cause: [chars])

Explanation   The ATM25 network module hardware may be bad.

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


Error Message   
%IDTATM25-1-INITFAIL: IDTATM25([dec]/[dec]), Init failed, CSR[dec]=0x[hex]

Explanation   The ATM25 network module hardware may be bad.

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


Error Message   
%IDTATM25-3-NOTIDTATM25: Device reported [hex]

Explanation   The ATM25 network module hardware may be bad.

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


Error Message   
%IDTATM25-3-UNSUPPORTED: Interface [chars], [chars] not supported

Explanation   The ATM25 network module hardware may be bad.

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

IFS Error Messages

Cisco IOS File System error messages


Error Message   
%IFS-4-FILEMAX: Failed to open [chars], maximum open files [dec])

Explanation   The router reached the maximum number of files that may be open at one time.

Recommended Action   Close some files and try again. If this messages recurs, contact your technical support representative.


Error Message   
%IFS-3-FS_CREATE_FAIL: Failed to create [chars] file system, [chars]

Explanation   An internal software error occurred.

Recommended Action   Call your technical support representative for assistance.


Error Message   
%IFS-3-FS_CREATE_FAIL2: Failed to create [chars] simple file system, [chars]

Explanation   An internal software error occurred.

Recommended Action   Call your technical support representative for assistance.


Error Message   
%IFS-3-FSDUP: Failed to add [chars], filesystem prefix exists

Explanation   A file system could not be added because another file system exists with the same name.

Recommended Action   If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%IFS-3-FSMAX: Failed to add [chars], maximum filesystems [dec]

Explanation   An internal software error occurred.

Recommended Action   If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%IFS-3-FS_MISSING_FUNCTIONS: '[chars]' file system missing required functions, not created

Explanation   Some file systems require a certain set of functions to be present in order to be usable. This file system does not support all the mandatory functionality.

Recommended Action   Call your technical support representative for assistance.

IGRP Error Message

Interior Gateway Routing Protocol error message


Error Message   
%IGRP-3-NOSOCKET: Unable to open socket for AS [dec]

Explanation   The requested operation could not be accomplished because of a low memory condition.

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

ILACC Error Messages

ILACC driver error messages


Error Message   
%ILACC-4-BABBLE: Unit [dec], babble error, csr0 = 0x[hex]

Explanation   An Ethernet interface is malfunctioning.

Recommended Action   Determine whether the malfunction stems from a software or hardware error by turning off all fast switching. Error messages showing that the packet is too large for the link indicate a software error at a high level. Copy the error message exactly as it appears, and report it to your technical support representative. Receiving no error messages indicates a hardware error. Repair or replace the controller.


Error Message   
%ILACC-3-BADUNIT: msgtxt_badunit

Explanation   An internal software error occurred.

Recommended Action   If this message recurs, contact your technical support representative.


Error Message   
%ILACC-5-COLL: Unit [dec], excessive collisions. TDR=[dec]

Explanation   An Ethernet cable is broken or unterminated, or the transceiver is unplugged. The time delay reflectometer (TDR) counter is an internal ILACC counter that counts the time (in ticks of 100 ns each) from the start of a transmission to the occurrence of a collision. Because a transmission travels about 35 feet per tick, this value is useful to determine the approximate distance to a cable fault.

Recommended Action   If the transceiver appears to be properly terminated, repair or replace the Ethernet interface card.


Error Message   
%ILACC-1-INITFAIL: msgtxt_initfail

Explanation   The hardware failed to initialize correctly.

Recommended Action   Repair or replace the controller.


Error Message   
%ILACC-5-LATECOLL: Unit [dec], late collision error

Explanation   An Ethernet transceiver is malfunctioning, the Ethernet is overloaded, or the Ethernet cable is too long.

Recommended Action   Repair or replace the controller.


Error Message   
%ILACC-5-LOSTCARR: Unit [dec], lost carrier. Transceiver problem?

Explanation   An Ethernet transceiver is unplugged or faulty.

Recommended Action   Repair or replace the controller.


Error Message   
%ILACC-1-MEMERR: msgtxt_memoryerror

Explanation   An Ethernet interface detected a hardware problem.

Recommended Action   Repair or replace the controller.


Error Message   
%ILACC-3-OWNERR: msgtxt_ownerror

Explanation   An Ethernet interface is malfunctioning, or an internal software error occurred.

Recommended Action   Repair or replace the controller.


Error Message   
%ILACC-3-SPURIDON: Unit [dec], spurious IDON interrupt, csr[dec]=0x[hex]

Explanation   An Ethernet interface generated a spurious Initialization Done interrupt.

Recommended Action   Repair or replace the controller.


Error Message   
%ILACC-3-UNDERFLO: Unit [dec], underflow error

Explanation   The Ethernet hardware is requesting data faster than the system can supply it. This condition might indicate that the system is at the limit of its performance.

Recommended Action   A small number of underflows might not be a cause for concern. You can monitor underflows with the show interface command. Reducing the load on the router or installing a higher-performance router should alleviate this problem.

INTERFACE_API Error Messages

Interface API error messages


Error Message   
%INTERFACE_API-4-BADPAKINPUT: pak-if_input is not initialized

Explanation   An internal software error occurred.

Recommended Action   If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%INTERFACE_API-4-BADPAKOUTPUT: pak-if_output is not initialized

Explanation   An internal software error occurred.

Recommended Action   If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%INTERFACE_API-4-BADSWIDB: [chars] may not be referencing the correct swidb

Explanation   An internal software error occurred.

Recommended Action   If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.

IP Error Messages

Internet Protocol error messages


Error Message   
%IP-3-BADIPALIGN: Invalid alignment in packet for IP. [chars]=[hex]

Explanation   The packet data structure is misaligned. This condition may result in a small amount of overhead in processing IP traffic.

Recommended Action   Enter a show hardware command and report the output, along with this error message, to your technical support representative.


Error Message   
%IP-3-BADSROUTE: Improper source route. Length [dec] Ptr [dec]

Explanation   A hardware or software error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%IP-4-CLASS: Bad IP address and mask [inet] in class_resolve()

Explanation   An internal software error occurred.

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   
%IP-3-CNTRFULL: IP counter block is full (setting protocol [dec])

Explanation   An internal software error occurred.

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


Error Message   
%IP-3-DESTHOST: src=[int], dst=[int], NULL desthost

Explanation   An internal software error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%IP-4-DUPADDR: Duplicate address [int] on [chars], sourced by [sci_notation]

Explanation   Another system is using your IP address.

Recommended Action   Change the IP address of one of the two systems.


Error Message   
%IP-3-LOOPPAK: Looping packet detected and dropped - src=[int], dst=[int], hl=[int], tl=[int], prot=[int], sport=[int], dport=[int] in=[chars], nexthop=[int], out=[chars]options=[chars]

Explanation   A software error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%IP-5-WEBINST_COMP: Selected IP address [int]

Explanation   A hardware or software error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%IP-5-WEBINST_KILL: Terminating DNS process

Explanation   A hardware or software error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%IP-5-WEBINST_RESP: Sending DNS response to [int] (request was for [int])

Explanation   A hardware or software error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%IP-5-WEBINST_START: Attempting web install from host [int]

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   
%IP-4-ZERO_ADDR: Zero MAC address for [int] in ARP cache

Explanation   An entry in the ARP cache has a NULL MAC address.

Recommended Action   If this message recurs, call your technical support representative for assistance.

IPACCESS Error Messages

IP security error messages


Error Message   
%IPACCESS-2-NOMEMORY: Alloc fail for acl-config buffer. Disabling distributed mode on lc

Explanation   Unable to allocate memory for a buffer in order to send the access list configuration to the line cards.

Recommended Action   Enter a show chunks command and report the output, along with this error message, to your technical support representative.


Error Message   
%IPACCESS-2-WRONGREQUEST: Invalid request to allocate chunk of size [dec]

Explanation   The maximum size for access list chunks is IPACCESS_LARGE_CHUNK_SZ.

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


Error Message   
%IPACCESS-2-WRONGSIZE: Incorrect length acl ipc xdr of type=[chars] len=[dec] received

Explanation   The RP sent an access list configuration message of the wrong size for that type.

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

IPC Error Messages

Interprocess Communication error messages


Error Message   
%IPC-2-CANT_SEND: Cannot send IPC message: [chars]

Explanation   An error occurred in the IPC slave-discovery mechanism. It might result in a malfunction in the operation of the IPC.

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   
%IPC-4-CONSISTENCY: Message failed consistency check: [chars]

Explanation   An internal inconsistency was found in some IPC data structures.

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   
%IPC-3-DELETED: Attempt to delete an IPC message (0x[hex]) a second time

Explanation   An internal inconsistency was found in some IPC data structures.

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


Error Message   
%IPC-4-GET_PAK_MSG: Failed for message size=[dec]

Explanation   The system is out of pak type buffers of the required size.

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   
%IPC-3-GIANT: Request for giant IPC packet denied. Request size = [dec]

Explanation   Someone requested a message that was too large for the IPC system.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc status 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 ipc status output, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%IPC-5-INVALID: [chars] [chars]=0x[hex]

Explanation   An IPC message has an invalid seat, port, or callback.

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   
%IPC-2-INVALSIZE: IPC message received with invalid size(size/type - [dec]/[dec])

Explanation   An IPC message was received with an invalid size.

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   
%IPC-2-LOCK: Lock done a deleted element

Explanation   An internal inconsistency was found in some IPC data structures.

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   
%IPC-3-NOBUFF: The [chars] IPC message header cache has emptied

Explanation   The given IPC message header cache has emptied.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc status 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 ipc status output, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%IPC-5-NODELFUNC: Delayed init function not available

Explanation   The IPC application cannot be initialized because its initialization function does not appear in the IPC initialization function list.

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   
%IPC-2-NODISPATCH: Message for [dec].[dec] has no receive queue or dispatch routine

Explanation   The IPC user failed to provide any means of handling the received message.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc ports 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 ipc ports output, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%IPC-2-NOMEM: No memory available for [chars]

Explanation   The IPC protocol subsystem could not obtain the memory it needed.

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   
%IPC-5-NULL: [chars] [chars]=0x[hex]

Explanation   An IPC message has a null seat, port, or callback.

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   
%IPC-5-NULLDELFUNC: Passed Null Delayed function to register

Explanation   IPC cannot register an application's NULL function in the IPC initialization function list.

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   
%IPC-2-ONINT: Called from interrupt level: [chars]

Explanation   The IPC user attempted a prohibited call into IPC while IPC was running on the interrupt stack.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc status 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 ipc status output, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%IPC-5-OUTPUT_FAIL: Num [dec] Func=0x[hex] Seat: ID=[hex] %10s Sent %6d Heard %6d

Explanation   IPC output failed in the function for a given seat, with given sequence numbers for sending and receiving.

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   
%IPC-5-QFULL: Q=0x[hex] [chars] [dec]

Explanation   The IPC queue is full.

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   
%IPC-5-SEQ_ERR: [chars] Num [dec] From [hex],[hex]

Explanation   Errors occurred in IPC message sequence numbers.

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   
%IPC-5-SLAVELOG: VIP-[chars]

Explanation   The Cisco IOS software, running on a Versatile Interface Processor (VIP) card, generated this message. The error message has been passed up to the Route Processor (RP) or Route Switch Processor (RSP) for display. This message appears only if the user has configured the service slavelog command.

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   
%IPC-2-UNLOCK: Unlock done on already unlocked element

Explanation   An internal inconsistency was found in some IPC data structures.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.

IPCGRP Error Messages

RP Interprocess Communication error messages


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

Explanation   An IPC card 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 on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%IPCGRP-3-CMDOP: IPC command [int] (slot[int]/[int]): [chars]

Explanation   IPC command processing operational errors occurred.

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


Error Message   
%IPCGRP-3-CREATE_FAIL: [chars] [chars]

Explanation   An IPC port was not created on the RP.

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   
%IPCGRP-3-EVENTOP: Event (slot[int]): [chars]

Explanation   IPC event processing operational errors occurred.

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


Error Message   
%IPCGRP-3-EXECCMDMSG: Incorrect msg size (size=[int])

Explanation   The message size is incorrect for a REXEC-On IPC command.

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


Error Message   
%IPCGRP-3-INVNUM: [chars] ([int])

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 on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%IPCGRP-3-MSGERR: [chars] ([int])

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

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   
%IPCGRP-3-NBLKCMD: [chars]

Explanation   A nonblocking IPC command queue initialization failure occurred.

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


Error Message   
%IPCGRP-3-NOHWIDB: Cannot find hwidb for interface([int]/[int])

Explanation   An interface identifier does not exist for the interface addressed by the corresponding IPC message.

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


Error Message   
%IPCGRP-3-NULLMSG: Null [chars] ipc message

Explanation   An unexpected empty IPC message was received.

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


Error Message   
%IPCGRP-3-NULLREXECCMD: Received empty ipc rexec cmd message

Explanation   An REXEC-On IPC command failure occurred.

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


Error Message   
%IPCGRP-3-REXEC: [chars]

Explanation   An REXEC-On IPC command failure occurred.

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


Error Message   
%IPCGRP-3-SEATERR: [chars] ([int])

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 on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%IPCGRP-3-SYSCALL: System call for command [int] (slot[int]/[int]) : [chars] (Cause: [chars])

Explanation   An IPC kernel system call error occurred.

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

IPCLC Error Messages

Gigabit Switch Router line card interprocess communication error messages


Error Message   
%IPCLC-3-EVENT: Event ([int]) [chars] error

Explanation   Command or event processing operational errors occurred.

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


Error Message   
%IPCLC-3-EVENTSYS: Event ([int]) system call [chars] error (cause: [chars])

Explanation   IPC kernel system call errors occurred.

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


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

Explanation   The line card IPC cannot register with the route processor. It cannot exchange messages route processor.

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


Error Message   
%IPCLC-3-OP: [chars]

Explanation   Command or event processing operational errors occurred.

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


Error Message   
%IPCLC-3-REPLY: Reply (to cmd [int]) [chars] error

Explanation   Command or event processing operational errors occurred.

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


Error Message   
%IPCLC-3-REPLYSYS: Reply (to cmd [int]) system call [chars] error (cause: [chars])

Explanation   Reply-to-RP-command operation errors occurred.

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

IPC_RSP_CBUS Error Messages

Interprocess communication 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 because of 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.


hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1998 © Cisco Systems Inc.