|
|
LS1010 chip-specific error messages
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.
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.
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.
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.
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.
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.
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.
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.
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.
Frame Relay error messages
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.
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.
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.
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.
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.
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.
Frame Relay enhanced Local Management Interface error messages
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.
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.
Frame Relay Local Management Interface error message
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.
Cisco 3801 platform error message
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.
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.
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.
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.
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.
FTP server processes error messages
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.
Explanation A FTP client request failed to change to the requested directory.
Recommended Action Verify the correct path for the desired directory.
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.
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.
Explanation A new FTP server connection has opened.
Recommended Action FTP server connections can be disabled by using the command no ftp-server enable.
Explanation An FTP login has occurred.
Recommended Action This is an informational message only. Informational messages can be disabled by changing logging level.
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.
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.
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.
Inspection subsystem error messages
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Xerox Network Systems (XNS) Routing Protocol error messages
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.
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.
Gigabit route processor (RP) error messages
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
POS route processor (RP) driver error messages
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.
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.
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.
Gigabit Switch Router environment monitor error messages
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.
Explanation One or more fans are broken or missing. This may cause the chassis to overheat.
Recommended Action Replace the bad fan tray.
Explanation The slot has been powered down for safety reasons.
Recommended Action Rectify the specified condition before using the card again.
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.
Explanation The power supply input voltage failed.
Recommended Action Ensure that the power supply is plugged in and turned on.
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.
Gigabit Switch Router IPC service routines error messages
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.
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.
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 DMA controller driver error messages
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.
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.
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.
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.
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.
Token Ring PCI port adapter error messages
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.
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.
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.
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.
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.
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.
HD64570 serial controller error messages
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.
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.
Explanation An internal software error occurred.
Recommended Action If message recurs, call your technical support representative for assistance.
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.
Hex modem network module asynchronous driver error messages
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.
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.
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.
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.
Explanation There are no modems installed on the network module.
Recommended Action Make sure the network module contains properly installed MICA-6DM SIMMs.
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.
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.
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.
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.
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.
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.
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.
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.
LAN controller 100VG-AnyLAN interface error messages
Explanation An internal software error occurred.
Recommended Action If the message recurs, call your technical support representative for assistance.
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.
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.
Explanation An Ethernet transceiver is unplugged or faulty.
Recommended Action Repair or replace the controller.
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.
100VF-AnyLAN PA driver error messages
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.
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.
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.
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.
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.
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.
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.
Explanation Could not find Hardware CAM on the PA module.
Recommended Action Repair or replace the 100VG PA interface module.
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.
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.
Explanation Unable to login to the hub.
Recommended Action Take action based on the error messages that follow.
Cisco Ethernet hub error messages
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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 messages which refer to an IBM Token Ring chip set
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.
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.
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.
Explanation The Token Ring PCI port adapter driver depends on capabilities of the Revision 2 processor.
Recommended Action Upgrade the processor to Revision 2.
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.
ID Manager error messages
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.
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.
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.
IDT ATM25 network module error messages
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.
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.
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.
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.
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.
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.
Cisco IOS File System error messages
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.
Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
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.
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.
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.
Interior Gateway Routing Protocol error message
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 driver error messages
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.
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
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.
Explanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
Explanation An Ethernet transceiver is malfunctioning, the Ethernet is overloaded, or the Ethernet cable is too long.
Recommended Action Repair or replace the controller.
Explanation An Ethernet transceiver is unplugged or faulty.
Recommended Action Repair or replace the controller.
Explanation An Ethernet interface detected a hardware problem.
Recommended Action Repair or replace the controller.
Explanation An Ethernet interface is malfunctioning, or an internal software error occurred.
Recommended Action Repair or replace the controller.
Explanation An Ethernet interface generated a spurious Initialization Done interrupt.
Recommended Action Repair or replace the controller.
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
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.
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.
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.
Internet Protocol error messages
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.
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.
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.
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.
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.
Explanation Another system is using your IP address.
Recommended Action Change the IP address of one of the two systems.
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.
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.
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.
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.
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.
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.
IP security error messages
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.
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.
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.
Interprocess Communication error messages
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
RP Interprocess Communication error messages
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Gigabit Switch Router line card interprocess communication error messages
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.
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.
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.
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.
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.
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.
Interprocess communication error messages
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.
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.
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.
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.
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.
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.
|
|