System Error Messages

This facility controls a feature in the RISC-processor-based Cisco products that identifies software in need of memory use optimization.

Explanation A software component within the router has been identified as needing memory optimization.

Recommended Action Report this message to your technical support representative.

Explanation The router has identified a fatal error in a software component and could not correct it.

Recommended Action Record the entire message and immediately contact your technical support representative for assistance.

Explanation The router has identified more software components in need of memory optimization than it can record.

Recommended Action Call your technical support representative for assistance.

Explanation The router cannot start the memory performance monitoring system because there is not enough system memory to do so.

Recommended Action Call your technical support representative for assistance.

Explanation An error has been identified (and temporarily corrected) within a software component in the router.

Recommended Action Report the entire message and any problem you are experiencing to your technical support representative.

Explanation An error has been identified (and temporarily corrected) within a software component in the router.

Recommended Action Report the entire message and any problem you are experiencing to your technical support representative.

ARAP Error Messages

Explanation This message will only appear when "arap logging" has been configured The message notes that an ARAP user has logged out.

Explanation This message will only appear when "arap logging" has been configured. The message notes that an ARAP user has logged in.

Explanation A user has been disconnected from ARAP at an unexpected time. This may be due to modems dropping, server error, client problems, or anynumber of other difficulties.

Explanation The ARAP client was denied access, probably due to a configuration problem on the server. Error message should indicate the problem. Denials due to bad passwords don't show up here.

Recommended Action Examine buffer usage statistics. Possibly more memory is required.

Explanation The startup negotiation between a client and the ARAP server has fallen out of order. If this is sporadic, it is indicative of line noise.

Recommended Action If this message recurs, reinstall the ARA client software.

Explanation TACACS authentication has failed because extended TACACS has not been configured.

Explanation ARAP has failed to run because it couldn't allocate enough memory for its internal data structures.

Recommended Action Examine "show mem" details of memory usage. Possibly install more memory.

AT Error Messages

Explanation The port is determining the correct configuration. This message is generated when discovery mode is enabled and no other router has been detected.

Explanation The initial hint address was in use. A search will be made for a valid address.

Explanation The hint address specified for the port was not valid for its current configuration.

Recommended Action No action required; the hint is ignored and a random valid hint is automatically computed.

Explanation No hint address or a bad hint address was specified. This message indicates which AppleTalk address will be used.

Explanation The software detected an inconsistency. Although this error is serious, the router attempts to continue. AppleTalk processing may be impaired.

Recommended Action Record the entire message and note any AppleTalk problems you experience. Give this information to your technical support representative in a problem report.

Explanation A neighboring router's AppleTalk configuration does not agree with this router's AppleTalk configuration. This condition can result from a mismatch between the neighbor's network range and this router's network range.

Recommended Action Modify either this router's or the neighboring router's configuration so that the network ranges agree.

Explanation The system has not heard about a route within the required time-out period. Therefore, the route has been marked as bad. This may mean that a network has become unreachable for some reason—perhaps a broken connection. This message does not necessarily reflect an error condition.

Explanation The software detected an unexpected condition. The router takes corrective action and continues.

Recommended Action Record the entire message and note any AppleTalk problems you are experiencing. Give this information to your technical support representative in a problem report.

Explanation The user has attempted to remove a route from the routing table with the command clear appletalk route. The command failed because the route was directly connected (that is, it was created by a configuration command).

Recommended Action Remove the route by reconfiguring the directly connected interface with which it is associated.

Explanation A neighboring router only supports extended AppleTalk networks with a cable range of 1 and with one assigned zone, for example, 25-25.

Recommended Action Upgrade routers that can support only the original AppleTalk specification, and observe the compatibility rules in the interim.

Explanation Although this router has neighbors that require your internetwork to observe compatibility rules, a route has been learned that has multiple zone names defined. This condition can cause inconsistencies for nodes in your internet.

Recommended Action Upgrade routers that can support only the original AppleTalk specification, and observe the compatibility rules in the interim.

Explanation Although this router has neighbors that require your internetwork to observe compatibility rules, a route has been learned that has a wide (greater than 1) cable range. This condition can cause inconsistencies for nodes in your internetwork.

Recommended Action Upgrade routers that can support only the original AppleTalk specification, and observe the compatibility rules in the interim.

Recommended Action Call your technical support representative for assistance.

Explanation The AppleTalk configuration was verified by consulting the indicated router.

Explanation This message is generated by a debug command to provide additional information about a condition in AppleTalk.

Recommended Action If you are experiencing problems in AppleTalk, show these messages to your technical support representative.

Explanation This message is generated during the verification startup process when there is a disagreement between the default zone (the first zone defined after the appletalk cable-range command) and the router that confirmed the configuration. When an AppleTalk end node is first connected to a network, it joins this default zone until it is overridden.

Recommended Action Correct the configuration so that all routers are advertising the same default zone. Note that several router implementations are known to mismanage the default zone.

Recommended Action Call your technical support representative for assistance.

Explanation Another AppleTalk node on a common network interface has claimed the same AppleTalk address that this router was using. This error indicates a serious, unexpected problem. If this is a recurring problem, there may be a physical network problem in which the nodes are unable to hear each other.

Recommended Action This router will restart AppleTalk processing on the common network interface to resolve the address conflict. No action required.

Explanation Another router on an FDDI ring running AppleTalk is running a release of the router software previous to 9.0(2). Routers running software releases earlier than 9.0(2) use an encapsulation for AppleTalk on FDDI rings that is not compatible with the Apple FDDITalk preliminary proposal.

Explanation An attempt was made to configure an interface to have the same or a conflicting AppleTalk address or cable range as another interface on the same router.

Recommended Action Verify that you are not specifying an AppleTalk address or cable range used previously on this router, and reconfigure the interface.

Explanation This message is generated by performing the EXEC command clear interface on an interface currently routing AppleTalk.

Explanation An AppleTalk hardware interface has been disabled because of a bad serial line, a configuration command, or a bad interface.

Recommended Action If the port has not been intentionally disabled, this message may reflect a hardware problem. If so, repair or replace the controller.

Explanation This message is generated when a configuration change necessitates resetting the hardware interface. AppleTalk has reinitialized the port.

Explanation An AppleTalk port that was previously shut down has been restarted.

Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server cannot begin or recover operations because of an invalid IP address configuration. This condition only occurs when the configured MacIP server's IP address is not valid on the same cable of any operable IP interface. An AppleTalk zone of the MacIP server replaces ZONE-NAME. The MacIP server's configured IP address replaces X.X.X.X.

When this error occurs, the MacIP configuration is considered invalid and is deleted.

Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server is no longer operational for any reason. MacIP servers shut down in response to MacIP configuration changes or errors, or a change in the condition or configuration of an AppleTalk or IP interface for which the MacIP server is providing service. An AppleTalk zone of the MacIP server replaces ZONE-NAME. The MacIP server's configured IP address replaces X.X.X.X.

Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server can no longer operate due to a change in the condition of the IP interface it serves. This condition can occur if IP routing is shut down on the interface, or the IP address of the interface is changed so that the MacIP server's IP address is no longer valid on the same cable. An AppleTalk zone of the MacIP server replaces ZONE-NAME. The MacIP server's configured IP address replaces X.X.X.X.

Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server has fully initialized and is ready to accept client requests. An AppleTalk zone served by the MacIP server replaces ZONE-NAME. The MacIP server's configured IP address replaces X.X.X.X.

Explanation A computed multicast address disagrees with that provided by another AppleTalk router. The other AppleTalk router may be misconfigured or faulty.

Explanation This message is displayed upon successful completion of the EXEC command clear appletalk neighbor.

Explanation A neighboring router to which this router previously lost connectivity has reappeared on the network.

Explanation The port was disabled because the configured AppleTalk address or cable range on the interface conflicts with another router on the attached network.

Explanation The configuration specified for the interface conflicts with the active AppleTalk internetwork. For example, a cable range is configured so that it overlaps an existing route but does not match the entry exactly.

Recommended Action Reconfigure the port so that it is consistent with the existing internetwork or take any other actions necessary to resolve the conflict. AppleTalk will periodically attempt to restart the port.

Explanation A new AppleTalk route has been learned. The message includes the source of the route and its distance in hops.

Recommended Action If fewer than 250 nodes reside on your AppleTalk network, call your technical support representative. Otherwise, you must split your AppleTalk network into smaller networks.

Recommended Action Call your technical support representative for assistance.

Explanation An AppleTalk node has sent a GetNet Info request to this router specifying an invalid network number for the source of the GetNet Info request. This situation occurs when an AppleTalk end node is moved between networks and is therefore misconfigured for the current network.

Recommended Action Call your technical support representative for assistance.

Explanation A previously configured Name Binding Protocol (NBP) proxy has been deleted. The router can no longer convert NBP requests to a format understood by routers that support only the original specification of AppleTalk.

Explanation The router could not deliver a packet to a destination because it did not know where to send it.

Recommended Action If the destination is valid, you must determine why the router does not know the route (that is, the neighboring router may be withholding information).

Explanation An attempt to generate an AppleTalk packet from the router has failed because no valid AppleTalk source address is available to identify this router in the packet.

Recommended Action Configure a port to have an address or cable range and verify that the port is operational.

Explanation The user tried to execute the EXEC commands show appletalk neighbor or clear appletalk neighbor with a nonexistent neighbor address.

Recommended Action Specify a valid neighbor address, that is, one that appears in the output of the show appletalk neighbor command with no arguments.

Explanation The user tried to execute the EXEC commands show appletalk route or clear appletalk route with a nonexistent route.

Recommended Action Specify a valid route, that is, one that appears in the output of the show appletalk route command with no arguments.

Explanation You tried to show or change the AppleTalk configuration when AppleTalk routing was not turned on.

Recommended Action Issue the appletalk routing configuration command prior to issuing any other AppleTalk configuration or display command.

Explanation The specified interface has an encapsulation method that does not support AppleTalk.

Explanation The firmware on the MCI controller card does not support AppleTalk fast switching.

Recommended Action No corrective action is required. Normal AppleTalk operation is permitted, but the fast switching cache is disabled for the associated port. If unexpected, verify that the MCI controller firmware for the interface specified in the error message is at level 1.7 or higher.

Explanation No other AppleTalk routers were found on the network attached to the port.

Recommended Action Call your technical support representative for assistance.

Explanation A new AppleTalk path has been learned. The message includes the source of the path, its distance in hops, its metric, and the type of path.

Explanation The path to a network has changed either because the old path went down or the new path was better.

Explanation A router has gone down somewhere on the AppleTalk network. The specified peer notified this router of the change.

Recommended Action Call your technical support representative for assistance.

Explanation A connected route is being advertised as down (also known as notify neighbor) because the configured port is no longer operational.

Recommended Action Informational message only. No action required. If unexpected, correct the situation that caused the port to be disabled.

Explanation A router has gone down somewhere on the AppleTalk network. The specified peer notified this router of the change.

Explanation A routing update has been received for a previously suspect route.

Explanation An internal error has occurred that violates a programming assertion in the AppleTalk networking module.

Recommended Action Save the text of the message, the output of the show version command, and a copy of the router configuration file. Call your technical support representative for assistance.

Explanation The configurations of one or more other routers are inconsistent with the configuration of this router.

Explanation This message reports the zone name and network number that are being advertised to support the appletalk nbp-proxy command.

Recommended Action Informational message only. No action required. One message is generated for each configuration command when proxy service is initiated.

BGP Error Messages

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 Initialization of Radix tree 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.

BRI Error Messages

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

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.

Recommended Action Call your technical support representative for assistance.

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

CBus Error Messages

Recommended Action Call your technical support representative for assistance.

Explanation The Token Ring monitor firmware has detected a fatal error on the interface card.

Recommended Action Issue a clear interface command. If this message recurs, call your technical support representative for assistance.

Explanation A command from the system to the Token Ring interface failed to complete.

Recommended Action Call your technical support representative for assistance.

Recommended Action Issue a clear interface command. If this message recurs, call your technical support representative for assistance.

Recommended Action Call your technical support representative for assistance.

Recommended Action Issue a clear interface command. If this message recurs, call your technical support representative for assistance.

Explanation The Token Ring interface failed to complete a command that is part of the reset sequence.

Recommended Action Issue a clear interface command. If this message recurs, call your technical support representative for assistance.

Explanation A hardware component failed an internal diagnostic test. Test output and descriptions of ranges follow.

Indicates the Multibus jumper setting for the ciscoBus controller, or in the Cisco 7000, a slot number.

Indicates the ciscoBus relative slot number (0 to 3, or in the Cisco 7000, 0 to 4) of the daughter card that failed the test.

If the failed test was memd read, the processor was able to write to shared ciscoBus buffer memory from the ciscoBus registers, but was unable to read back that memory through special commands to the daughter card.

If the failed test was memd write, writes to MEMD through the daughter card were not verified successfully with reads through the ciscoBus controller.

The daughter card under test responds successfully to some commands (otherwise the software would have received a DAUGHTER_NO_RSP message), but its MEMD tests failed. The daughter card must be able to write to some MEMD addresses; otherwise, it cannot respond to any commands.

Recommended Action First check that the daughter controller card is properly seated in its Multibus and ciscoBus connectors. Next, swap daughter cards and check whether the error follows the daughter card or the slot. If the message recurs, call your technical support representative for assistance.

Explanation A hardware component failed an internal diagnostic test. Test output and descriptions of ranges follow.

Unit [dec] (ranges 0-14):
Indicates the Multibus jumper setting for the ciscoBus controller.

daughter controller [dec] (ranges 0-3):
Indicates the ciscoBus relative slot number (0 to 3, or in the Cisco 7000, 0 to 4) of the daughter card that failed the test.

The daughter card's hardware was recognized across the ciscoBus backplane, but the daughter card did not respond to the first command issued to it.

This condition is a result of one of the following: the daughter card did not reset, or the microcode on the card is in a hung state, or the card cannot fully communicate across the ciscoBus backplane (cannot read or write shared MEMD or does not get the MALU_ATTENTION signal across the ciscoBus).

Recommended Action First, make sure that the daughter card is properly seated in its Multibus and ciscoBus connectors. If this action does not solve the problem, call your technical support representative.

Recommended Action Make sure the device is functioning and is configured correctly.

Explanation A Fast Serial Interface Processor (FSIP) has not responded to a reset request from the route processor.

Recommended Action Check FSIP electrical connections, cable, and ciscoBus connections. An FSIP microcode reload will be required. If the check of electrical connections reveals no problems and the message recurs, call your technical support representative for assistance.

Recommended Action Call your technical support representative for assistance.

Recommended Action Make sure the device is functioning and is configured correctly.

Recommended Action Correct any problems with the Ethernet cable, then manually re-enable the port.

Explanation This ERROR results from CPU starvation, typically caused by heavy fast switching activity. The counts displayed for the MultiChannel Interface Processor (MIP) card are incorrect.

Recommended Action Call your technical support representative for assistance.

Explanation The controller type was derived from a hardware probe. The controller number indicates the ciscoBus relative slot number. The most likely problem is a missing or invalid MAC address cookie ROM. A less likely explanation is corrupted MEMD after the memd self-tests.

Recommended Action Call your technical support representative for assistance. It will be necessary to replace the cookie ROM.

Explanation The requested operation could not be accomplished because of a low memory condition or an unseated card in the Cisco 7000.

Recommended Action Reduce other system activity to ease memory demands. Check that all cards are properly seated. If conditions warrant, upgrade to a larger memory configuration.

Explanation A ciscoBus controller took too long to respond to a command and was restarted by software.

Recommended Action If this message recurs, call your technical support representative for assistance. You might need to repair or replace the controller.

Explanation An interface reset was attempted on an interface that was removed from the router. This message appears if you use the shutdown command to bring down a removed interface.

Recommended Action Check switch settings on the interface cards. Check for proper unit numbers. Reset the cards. Replace the malfunctioning device.

Recommended Action Make sure the device is functioning and is configured correctly.

CIP Error Messages

The system can report error conditions in several facility codes related to the Channel Interface Processor. As shown in the following example, the format of the error messages for the CIP differs slightly from the format of other system error messages:

All CIP-related error messages begin with a percent sign (%), the facility code CIP, and a number that indicates the slot where the CIP is installed. The next meaningful information is the facility subcode, severity level, and mnemonic. This part of the error message is preceded by another percent sign, such as %ADAPTER-6-DIAGBEGIN in the above example.

For simplicity, CIP error messages are organized into sections alphabetically by facility subcode. Within each CIP section, messages appear alphabetically by mnemonic. CIP and slot number are not shown in the error message listing.

CIP-ADAPTER Error Messages

Explanation The user has used the test cbus command to request a particular adapter diagnostic to be run. This message is to inform the user that the diagnostic routine has started.

Explanation A diagnostic routine has detected a failure in the ECA hardware. These codes are used to locate the specific component that failed.

Recommended Action Report this message to your technical support representative.

Explanation A diagnostic routine has detected a failure in the ECA hardware. These codes are used to locate the specific component that failed.

Recommended Action Report this message to your technical support representative.

Explanation A diagnostic routine has failed. The specified port will not be used.

Recommended Action Report this message to your technical support representative.

Explanation A diagnostic requested by the test cbus command has completed successfully.

Explanation The diagnostic number requested by the test cbus command is not a valid diagnostic number.

Explanation The test cbus command was used to run a diagnostic on an active interface.

Recommended Action Use the shutdown command to stop the interface and then reissue the diagnostic request.

Explanation A diagnostic routine did not complete execution. The specified port will not be used.

Recommended Action Report this message to your technical support representative.

Explanation A diagnostic requested via the test cbus command did not terminate.

Recommended Action Report this message to your technical support representative.

Explanation Each adapter has an onboard microprocessor. This message indicates that the operation to load the code for that microprocessor failed.

Recommended Action Report this message to your technical support representative.

Explanation This indicates that an error has occurred on the adapter. The information displayed will assist development in determining the nature of the error.

Recommended Action Report this message to your technical support representative.

Explanation This message is displayed at the start of the logout data. It is then followed by the previous message.

Recommended Action Report this message to your technical support representative.

Explanation This message is used when displaying logout information. Its purpose is to avoid printing duplicate data.

Recommended Action Report this message to your technical support representative.

Explanation The data in this message is scan data for the adapter in the specified port. This scan is usually produced as a result of a hardware error.

Recommended Action Report the entire error message and scan data to your technical support representative.

Explanation The data in this message is related to a hardware failure of an adapter.

Recommended Action Report the entire error message and scan data to your technical support representative.

Explanation Prior to the adapter receiving a start command from the route processor, a set of diagnostics is run. If one of them fails, then the adapter will not be started when the start command is issued.

Recommended Action Report this message to your technical support representative.

Explanation A wrap plug is installed in the specified port. Wrap diagnostics will run until the plug is removed if this is the only adapter or if both adapters have wrap plugs installed.

Recommended Action Remove the wrap plug and connect the interface to a channel.

Explanation The wrap plug has been removed, causing the wrap diagnostics to terminate.

Explanation The wrap diagnostics have been terminated because the other adapter is active.

Recommended Action Remove the wrap plug and connect the interface to a channel if you wish to use this adapter. Otherwise, no action is required.

CIP-BSQ Error Messages

Explanation The sequence of buffer status queue entries received for read commands does not match the sequence of the storage control blocks used for the reads. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

Explanation Either an attempt was made to transfer more data in a single channel command word than the CIP can handle, or an internal error has occurred. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

CIP-CBUS_ATTN Error Message

CIP error messages relating to the CBUS_ATTN routine, the facility that receives configuration requests and gathers statistics

Explanation The RP has requested the CIP to store a configuration command at an invalid memory address. The CIP has recovered by ignoring the request.

Recommended Action Report this error to your technical support representative.

CIP-CBUS_WRITE Error Messages

CIP error messages for the CBUS_WRITE facility, which is used by the Enhanced Online Insertions Removal (EOIR) support on the CIP to track writes to MEMD and reissue them if a CBUS problem occurs

Explanation The type parameter in the write tracking table is invalid. This is an internal CIP logic error. The CIP has recovered by ignoring the entry.

Recommended Action Report this error to your technical support representative.

Explanation A write error interrupt has occurred, but the hardware that keeps track of the address of the error does not have a valid address.

Recommended Action Report this error to your technical support representative.

Explanation A write error was detected, but there was no corresponding entry in the table that keeps track of these entries. This is an internal CIP logic error. The CIP has recovered by ignoring the write error.

Recommended Action Report this error to your technical support representative.

Explanation This is a debugging print of the CBUS write stack. It is associated with the CBUS_WRITE-3-MISSING error message.

Recommended Action Report this error to your technical support representative.

Explanation A write operation to an address other than MEMD has timed out. This is probably a hardware problem. The CIP has failed and attempted to restart.

Recommended Action Record the address indicated in the error message. The address will enable a support representative to determine which component to replace. Report this error to your technical support representative.

CIP-CCA Error Messages

Explanation The adapter notified the CIP that an accept command response was issued. The CIP does not request notification of accept command response messages. Therefore, this message means the adapter has generated an unexpected message.

Recommended Action Normal processing will resume, but it would be useful for development to know that this message has occurred. Report this message to your technical support representative.

Explanation The adapter presented the CIP with a message using an undefined code point. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

Explanation The adapter notified the CIP that the buffer status queue was full. The CIP never provides enough buffers to the adapter to cause the buffer status queue to become full. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

Explanation The user has attempted to start the PCA with the select bypass switch in the bypass position. The PCA cannot go on-line with the switch in the bypass position.

Recommended Action Move the select bypass switch on the PCA-Y cable from the bypass position to the select position.

Explanation The adapter notified the CIP that a halt subchannel command was issued by the host, but provided the CIP with an undefined type of cancel.

Recommended Action The CIP will recover but development should be informed. Report this message to your technical support representative.

Explanation The adapter notified the CIP that a halt subchannel command was issued by the host for an undefined path. This is an internal logic error.

Recommended Action The CIP software has recovered but development needs to know the problem. Report this message to your technical support representative.

Explanation The adapter notified the CIP that a start subchannel command was issued by the host for an undefined path. This is an internal logic error.

Recommended Action The CIP software has recovered but development needs to know the problem. Report this message to your technical support representative.

Explanation The adapter notified the CIP that a connection was established for a device other than the one that the CIP had just requested. This is an internal logic error.

Recommended Action The CIP software has recovered but development needs to know the problem. Report this message to your technical support representative.

Explanation When a device error occurs, the adapter specifies the type of error so that the correct recovery action can be performed. The type specified is not defined. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

Explanation A device error was generated, and either it occurred while status was being presented but no device was active, or it occurred for an undefined device. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

Explanation A device error occurred, but the path specified in the device error message is not defined. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

Explanation The adapter reported an ending status interrupt for a channel command word that should not have caused the CIP to be notified. This is an internal logic error.

Recommended Action The CIP has performed recovery, but development should be notified of the problem. Report this message to your technical support representative.

Explanation The adapter sent a request to the CIP to perform a logout, but the command modifier in the message was not a valid value. This is an internal logic error.

Recommended Action The CIP has performed recovery, but development should be notified of the problem. Report this message to your technical support representative.

Explanation The adapter requested the CIP to present status for an undefined path. This is an internal logic error.

Recommended Action The CIP has performed recovery, but development should be notified of the problem. Report this message to your technical support representative.

Explanation The adapter has requested the CIP to perform reset processing for an undefined path. This is an internal logic error.

Recommended Action The CIP has performed recovery, but development should be notified of the problem. Report this message to your technical support representative.

Explanation The adapter has requested the CIP to reset a logical path, but the flags on the reset request were not valid. This is an internal logic error.

Recommended Action The CIP has performed recovery, but development should be notified of the problem. Report this message to your technical support representative.

Explanation The adapter has requested the CIP to reset an undefined logical path. This is an internal logic error.

Recommended Action The CIP has performed recovery, but development should be notified of the problem. Report this message to your technical support representative.

Explanation The CIP was notified that an I/O operation was attempted with a storage control block that was marked as not ready. The specified I/O operation should never have a not ready storage control block. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

Explanation The adapter requested that the CIP perform a selective reset, but the request code in the message was not a valid value. This is an internal logic error.

Recommended Action The CIP has performed recovery, but development should be notified of the problem. Report this message to your technical support representative.

Explanation The adapter has requested the CIP to perform a selective reset on an undefined logical path. This is an internal logic error.

Recommended Action The CIP has performed recovery, but development should be notified of the problem. Report this message to your technical support representative.

Explanation The adapter has presented the CIP with notification that status was accepted by the channel, but the request code in the status message was not a valid code. This is an internal logic error.

Recommended Action The CIP has performed recovery, but development should be notified of the problem. Report this message to your technical support representative.

Explanation The adapter requested the CIP to perform a system reset, but the request code in the message was not a valid value. This is an internal logic error.

Recommended Action The CIP has performed recovery, but development should be notified of the problem. Report this message to your technical support representative.

Explanation The wrap plug is installed on the PCA in the specified port. The PCA can not be used unless connected to a channel.

Explanation The adapter requested the CIP to perform a request. When the CIP tried to present the response to the request, it was not able to write the common communication area. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

CIP-CLAW Error Messages

CIP error messages related to the Common Link Access to Workstation (CLAW) facility

Explanation An attempt was made to establish a connection, but the host application name specified on the host does not match the host application name specified in the router configuration.

Explanation During the system validate processing, the host name configured in the router did not match the host name configured on the host.

Explanation The host is configured to receive frames that are smaller than the CIP is designed to send. The CIP has notified the host of the problem.

Recommended Action Reconfigure the frame size on the host to be 4096 or larger.

Explanation The host has generated a bad return code in the response to the system validate request sent by the CIP.

Recommended Action Check the return code and correct the configuration as appropriate.

Explanation The version specified in a message from the host is not the same as the version specified in the CIP.

Recommended Action Report this error to your technical support representative.

Explanation An attempt was made to establish a connection, but the work station application name specified on the host does not match the work station application name specified in the router configuration.

Explanation During the system validate processing, the work station name configured in the router did not match the work station name configured on the host.

Explanation The host is configured to write more data in a single frame to the CIP than the CIP is designed to receive. The CIP has notified the host of the problem.

Recommended Action Reconfigure the frame size on the host to be 4096 or smaller.

Explanation The host sent a CLAW command with an invalid CLAW command code. The CIP has ignored the request.

Recommended Action Report this error to your technical support representative.

Explanation A packet was received from the host but the logical link specified with the data does not represent a valid connection. The packet was dropped.

Recommended Action Report this error to your technical support representative.

Explanation An attempt was made to allocate a link ID to assign to a connection request, but all link IDs were in use. The CIP has recovered by generating a bad return code to the requestor.

Recommended Action Report this error to your technical support representative.

Explanation The host software attempted to disconnect a link that was not established. The CIP has ignored the request.

Recommended Action Report this error to your technical support representative.

Explanation No available transmit buffers exist, but the CLAW connection has not reached its transmit buffer limit. The packet has been dropped.

Recommended Action Report this error to your technical support representative.

Explanation The link ID in a disconnect is not in the valid range for all CLAW links. The CIP has recovered by ignoring this request.

Recommended Action Report this error to your technical support representative.

Explanation The request type in a transfer element is not a valid value. This is an internal logic error. The CIP has recovered by ignoring the transfer element.

Recommended Action Report this error to your technical support representative.

Explanation The request type in a transfer element is valid but is not expected to occur at this time. This is an internal logic error. The CIP has recovered by ignoring the transfer element.

Recommended Action Report this error to your technical support representative.

CIP-CONFIG Error Messages

Explanation The port type function returned an invalid port type. This is an internal logic error.

Recommended Action Report this message to your technical support representative.

Explanation The router encountered an unrecognized configuration type when it attempted to update the maximum number of transmit buffers to be used by a device. This is an internal logic error.

Recommended Action Report this message to your technical support representative.

Explanation The device type specified by the route processor in a configuration request is not a valid device type. This is an internal logic error. The configuration request was ignored.

Recommended Action Report this message to your technical support representative.

Explanation The router has attempted to configure a PCA adapter with an invalid channel speed.

Recommended Action The CIP has recovered by ignoring the request. Report this error to your technical support representative.

Explanation The virtual circuit number specified by the route processor on a configuration request is too large. This is an internal logic error. The configuration request was ignored.

Recommended Action Report this message to your technical support representative.

Explanation A packet has been queued for the CIP with an invalid virtual circuit number.

Recommended Action The CIP has recovered by dropping the packet. Report this error to your technical support representative.

Explanation The route processor attempted to configure an odd address for a CLAW device. CLAW configuration requests must specify an even address. This is an internal logic error. The configuration request was ignored.

Recommended Action Report this message to your technical support representative.

Explanation The route processor attempted to reconfigure an existing device without first removing the device. This is an internal logic error. The original configuration remains.

Recommended Action Report this message to your technical support representative.

Explanation The route processor attempted to configure an existing device. This is an internal logic error. The configuration request was ignored.

Recommended Action Report this message to your technical support representative.

Explanation The route processor attempted to configure a device using a virtual circuit number that was already in use by another device. This is an internal logic error. The configuration request was ignored.

Recommended Action Report this message to your technical support representative.

Explanation The CIP does not have sufficient storage to allocate an application block. The configuration request was ignored.

Recommended Action Purchase the next larger storage size for the CIP or configure fewer devices.

Explanation The route processor attempted to unconfigure a device, but the control unit image for the device could not be located. This is an internal logic error. The unconfigure request was ignored.

Recommended Action Report this message to your technical support representative.

Explanation The route processor attempted to unconfigure a device, but the device was not defined. This is an internal logic error. The unconfigure request was ignored.

Recommended Action Report this message to your technical support representative.

Explanation No storage was available for the device block. The configuration request is ignored.

Recommended Action Purchase the next larger storage size for the CIP or configure fewer devices.

Explanation An attempt was made to configure more than 64 different paths. Only 64 paths are supported. The configuration request was ignored.

Explanation No storage was available for the logical path table. The configuration request was ignored.

Recommended Action Purchase the next larger storage size for the CIP or configure fewer devices.

Explanation The route processor attempted to unconfigure a device, but the virtual circuit number for the device is not defined. This is an internal logic error. The unconfigure request was ignored.

Recommended Action Report this message to your technical support representative.

Explanation An attempt was made to define more than 256 devices. Only 256 devices are supported on an adapter. The configuration request was ignored.

Explanation Work was pending when the router finished processing an unconfigure request. This is an internal logic error.

Recommended Action Report this message to your technical support representative.

Explanation A packet has been queued for the CIP with a valid virtual circuit number, but the virtual circuit number is associated with the other port adapter.

Recommended Action The CIP has recovered by dropping the packet. Report this error to your technical support representative.

CIP-DIAG Error Message

Explanation A request was made to run an ECA diagnostic, but the number of the diagnostic to run was not valid. This is an internal logic error. The request to run the diagnostic is ignored.

Recommended Action Report this message to your technical support representative.

CIP-DMA Error Messages

Error messages for the function on the CIP that is responsible for transfering data between the DRAM on the CIP and MEMD

Explanation The CBUS controller started a read or write operation and did not receive a response from the CBUS indicating the completion status. The packet has been dropped.

Recommended Action Report this error to your technical support representative.

Explanation A parity error was detected on the CBUS during a data transfer. The packet has been dropped.

Recommended Action Report this error to your technical support representative.

Explanation A parity error was detected during data transfer. The packet has been dropped.

Recommended Action Report this error to your technical support representative.

Explanation The CIP was notified that the current DMA transfer had completed, but the DMA status register indicated the transfer was still in progress. The CIP has restarted.

Recommended Action Report this error to your technical support representative.

Explanation The CBUS did not respond to the DMA controller within 10 microseconds (10µs). The packet has been dropped.

Recommended Action Report this error to your technical support representative.

Explanation A DMA interrupt occurred, but no transfer was pending. This is either an internal logic error or a hardware failure. The CIP has restarted.

Recommended Action Report this error to your technical support representative.

CIP-GET_DATA Error Message

CIP error messages related to the internal routine for allocating transfer elements

Explanation An attempt was made to allocate a transfer element and no storage was available. This is a fatal error. The CIP has restarted.

Recommended Action Report this error to your technical support representative.

CIP-INT Error Messages

Explanation A request was made to add an interrupt handler to the fast I/O path with an invalid interrupt type. This is a fatal internal logic error.

Explanation A request was made to add an interrupt handler with an invalid interrupt number. This is a fatal internal logic error.

Explanation A request was made to add an I/O interrupt handler with an invalid interrupt code. This is a fatal internal logic error.

Explanation A request was made to add a system call handler with an invalid system call number. This is a fatal internal logic error.

Explanation A request was made to remove an interrupt handler from the fast I/O path with an invalid interrupt type. This is a fatal internal logic error.

Explanation A request was made to remove an interrupt handler with an invalid interrupt number. This is a fatal internal logic error.

Explanation A request was made to remove an I/O interrupt handler with an invalid interrupt code. This is a fatal internal logic error.

Explanation A request was made to add a system call handler with an invalid system call number. This is a fatal internal logic error.

CIP-LOVE Error Message

CIP error messages related to the mechanism that sends statistics from the CIP to the router.

Explanation An attempt was made to transfer statistics to the RP. The DMA routines returned the wrong transfer request. The CIP has recovered.

Recommended Action Report this error to your technical support representative.

CIP-MEMD Error Message

Explanation A packet was queued to the CIP and the virtual circuit associated with the packet is not valid. The CIP dropped the packet.

Recommended Action Report this error to your technical support representative.

CIP-NEVADA Error Messages

Explanation An attempt was made to specify an interrupt handler for an invalid interrupt type on the nevada interrupt control chip. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Explanation An attempt was made to disable an invalid interrupt type on the nevada interrupt control chip. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Explanation An attempt was made to enable an invalid interrupt type on the nevada interrupt control chip. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Explanation An attempt was made to enable an interrupt routine on the nevada interrupt control chip, but there was not interrupt routine specified. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Explanation An interrupt was received for a code with no interrupt handler defined. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Explanation An attempt was made to remove an interrupt handler for an invalid interrupt type on the nevada interrupt control chip. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

CIP-SCB Error Message

Explanation An attempt was made to free SCB 0. This is an internal logic error. The request was ignored.

Recommended Action Report this message to your technical support representative.

CIP-SCHED Error Messages

Error messages related to the scheduler, the facility responsible for determining which process to run at a given time on the CIP

Explanation A request was made to create a process, but the priority for the process was not valid. The process was not created.

Recommended Action Report this error to your technical support representative.

Explanation An attempt was made to request a lock, but the lock word contained invalid data. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Explanation An attempt was made to unlock a lock, but the data in the lock word was not valid. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Explanation An attempt was made to unlock a lock that was not held. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Explanation An attempt was made to create more tasks than the CIP is designed to allow. The process was not created.

Recommended Action Report this error to your technical support representative.

Explanation An attempt was made to create a process and there was not sufficient storage available to contain the stack for the process. The process was not created.

Recommended Action Report this error to your technical support representative.

Explanation An attempt was made to create a process and there was not sufficient storage available to contain the control block for the process. The process was not created.

Recommended Action Report this error to your technical support representative.

Explanation An attempt was made to unlock a lock that was set by another task. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Explanation This message contains data that relates to the SCHED-0-NOTMYLOCK message.

Recommended Action Report this error to your technical support representative.

CIP-SLC Error Messages

Explanation An attempt to scan the first set of internal latches on the ESCON processor failed.

Recommended Action Report this message to your technical support representative.

Explanation An attempt to scan the second set of internal latches on the ESCON processor failed.

Recommended Action Report this message to your technical support representative.

Explanation An attempt to scan the internal latches of the serial link controller failed.

Recommended Action Report this message to your technical support representative.

Explanation An attempt was made to stop the clock on the interface between the Enterprise Systems Connection (ESCON) processor and the serial link controller. The serial link controller did not indicate that the clock was stopped.

Recommended Action Report this message to your technical support representative.

Explanation An attempt was made to stop the clock on the ESCON processor. The serial link controller did not indicate that the clock was stopped. The CIP attempted to stop the BIDI clock.

Recommended Action Report this message to your technical support representative.

CLNS Error Messages

Explanation Intermediate System-to-Intermediate system (IS-IS) allows only three area addresses per area. Multiple routers with at least one area address in common merge all of their configured area addresses into a single set. If the resulting set has more than three area addresses, this message appears and indicates that there will be a loss of connectivity to the specified area.

Recommended Action Reconfigure the network so that the area has fewer area addresses, or split the area into multiple areas.

Explanation Either message can occur when an interface is down and a static neighbor entry exists in the system's CLNS routing table. If this is not the case, the message indicates an internal software error.

Recommended Action Check the interface. If the interface is not down and no static neighbor entry exists for that interface, call your technical support representative for assistance.

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

COMP Error Messages

Recommended Action Call your technical support representative for assistance.

Explanation Interface serial0 compression getbuffer failed, causing Link Access Procedures, Balanced (LAPB) retransmissions.

Explanation One interface is configured for predictor compression, the other is not.

CONTROLLER Error Messages

Explanation A controller has stopped responding to commands over the cBus, so it has been put into shutdown mode.

Recommended Action Re-enable the controllers by issuing the no shut configuration command on all controllers on the card, or hotswap out the bad card and install the new one. You must still manually "no shut" the controllers.

CSC2-4 Error Message

Explanation The Universal Asynchronous Receiver/Transmitter (UART) in the console serial interface is malfunctioning.

DBUS Error Messages

Explanation The ID EEPROM on the indicated card is not programmed correctly.

Recommended Action Call your technical support representative for a replacement.

Explanation A processor has reported a bus error. The processor will be reset and not used until the next online insertion and removal (OIR) event or microcode download, when it will be retested.

Recommended Action Reinstall the processor or download the microcode. If this message recurs, call your technical support representative for assistance.

Explanation A processor has reported an error. This message is sent out in conjunction with other error messages to provide additional information.

Recommended Action Call your technical support representative and report information about all error messages displayed.

Explanation A processor has reported an internal error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.

Recommended Action Reinstall the processor or download the microcode. If this message recurs, call your technical support representative for assistance. Currently no boards report this error.

Explanation You have either a prototype or an RP1 EEPROM that does not have the necessary block of MAC addresses.

Recommended Action Replace the RP1 EEPROM. Call your technical support representative for assistance.

Explanation The structure containing the system MAC address needed by the OIR facility cannot be found in the RP EEPROM. The RP must be returned for reprogramming.

Recommended Action Return the RP for reprogramming and call your technical support representative for assistance.

Explanation A processor reported a mismatch between the contents of the slot register and its complement. This condition indicates a hardware failure in the diagnostic bus controller on that processor or on the diagnostic bus. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.

Recommended Action Call your technical support representative for assistance.

Explanation A processor reported a controller type that is unknown to the system. The processor will not be used and needs to be repaired.

Recommended Action Call your technical support representative for assistance.

Explanation Writable Control Store (WCS) is the set of devices on each interface processor that contains the running microcode. It can be loaded either from the ROM on the interface processor or from the system by using the downloadable microcode facility. In this message, a processor has reported a WCS controller instruction error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.

Recommended Action Call your technical support representative for assistance.

Explanation The processor in slot [n] reported a WCS controller error. The processor will be reset and new microcode loaded. This error message is encountered only while downloading microcode.

Recommended Action If this message recurs after the processor is reset and new microcode is loaded, call your technical support representative for assistance.

Explanation A processor has indicated an error condition while downloading microcode. The status, cmd/data, and pos numbers reflect the error condition, the last byte of microcode loaded, and the position in the file, respectively. If this error is encountered, the microcode download is aborted and the ROM microcode is loaded.

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

Explanation A processor has reported a WCS parity error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.

Recommended Action Replace the processor or download microcode. If this message recurs, call your technical support representative for assistance.

DLSW Error Messages

Recommended Action Call your technical support representative for assistance.

DNET Error Messages

Explanation The system is receiving its own DECnet packets. Either a serial line is looped back or another host with the same DECnet address is already present on the LAN.

Recommended Action Check the serial lines (if present) and the DECnet configuration.

Explanation Your DECnet configuration is incorrect. A host that is specified as nonlocal is present on your local network.

Recommended Action Correct the configuration. Call your technical support representative if you need assistance.

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.

DSPU Error Messages

Explanation Remote PU has rejected the router's request for an SSCP-PU session.

Recommended Action Verify PU configuration parameters at the router and at the remote PU. Determine whether the problem exists at the remote PU, and correct it. If the problem persists, call your technical support representative for assistance.

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

Recommended Action Verify configuration parameters at the router and at the remote station. Determine whether the router is configured to accept connectIn from this remote station.

Explanation Connection with the remote station could not be established because of insufficient memory in the router.

Recommended Action Correct low memory problem in the router. If the problem persists, call your technical support representative for assistance.

Recommended Action Verify host configuration parameters at the router and at the host. Determine whether the router is configured to accept connectIn from this host.

Recommended Action Verify PU configuration parameters at the router and at the remote PU. Determine whether the router is configured to accept connectIn from this remote PU.

Recommended Action Verify host configuration parameters at the router and at the host. Determine whether the host is active and responding to connection requests.

Recommended Action Verify PU configuration parameters at the router and at the remote PU. Determine whether the remote PU is active and responding to connection requests.

Explanation An invalid MaxIFrame value in XID was received from the remote station; connection with remote station could not be established.

Recommended Action Correct link station configuration at the remote station.

Explanation An invalid WindowSize value in XID was received from the remote station; connection with remote station could not be established.

Recommended Action Correct link station configuration at the remote station.

Explanation The remote station has not requested PU 2.0 activation; connection with remote station terminated.

Recommended Action Correct link station configuration parameters at the remote station to request a system services control point (SSCP)-PU session with the router.

Explanation XID3 with error indication was received from the remote station; connection with remote station could not be established.

Recommended Action Determine which field in XID3 (from bad byte/bit info) is rejected by the remote station and why (from sense data), and correct link station configuration parameters at either the router or the remote station.

Explanation Remote host has rejected the router's request to activate/deactivate an SSCP-LU session.

Recommended Action Verify host configuration parameters at the router and at the remote host. Determine whether the problem exists at the remote host and correct it. If the problem persists, call your technical support representative for assistance.

Recommended Action Correct the problem at the remote PU. If the problem persists, call your technical support representative for assistance.

Explanation Unsupported XID received from the remote station; connection with remote station could not be established.

Recommended Action Configure the remote station to send supported XID (if possible). Supported XID formats are
XID Format 0
XID Format 3

DUAL Error Messages

Recommended Action Call your technical support representative for assistance.

Explanation An interface is going down or is being removed from routing through IGRP, but not all links (neighbors) have been removed from the topology table.

Recommended Action Call your technical support representative for assistance.

EGP Error Messages

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

Explanation An EGP update message was too large to fit into a single buffer.

Recommended Action Call your technical support representative for assistance.

ENV Error Messages

Recommended Action Attempt to resolve the air flow problem. If the problem is not resolved, call your technical support representative for assistance.

Explanation One of the environmental measurements has reached SHUTDOWN status. The system is about to shut down the processor to prevent damage to the hardware.

Recommended Action Attempt to resolve the temperature problem. If the problem is not resolved, call your technical support representative for assistance.

Explanation The ENV card indicates the temperature it measured and the temperature at which it shuts down.

Recommended Action Attempt to resolve the temperature problem. If the problem is not resolved, call your technical support representative for assistance.

Explanation The ENV card indicates which voltage it is measuring (for example, +5, +12, -5, -12), the amount of voltage that it measured, and the voltage at which the processor will shut down the system.

Recommended Action Attempt to resolve the voltage problem. If the problem is not resolved, call your technical support representative for assistance.

ENVM Error Messages

Explanation There might be a hardware problem with the fan array. If the error condition continues for two minutes, the router automatically shuts down to prevent damage to router components.

Recommended Action If the system shuts down, replace the fan tray. Call your technical support representative for assistance.

Explanation The system has reached a SHUTDOWN temperature level, and the router is being shut down to avoid any damage.

Recommended Action Attempt to resolve the temperature problem. If the problem is not resolved, call your technical support representative for assistance.

Recommended Action Check that the power supply is turned on; if it is turned on and still does not operate, call your technical support representative for assistance.

Explanation The temperature parameter shown has reached a warning or critical level and is approaching or has approached a condition that is outside the acceptable range.

Recommended Action Attempt to resolve the temperature problem. If the problem is not resolved, call your technical support representative for assistance.

Explanation The voltage parameter shown has reached a critical level and is now out of specification.

Recommended Action Verify the failure and call your technical support representative for repair or replacement.

FDDI Error Messages

Recommended Action Call your technical support representative for assistance.

Explanation The main processor detects an invalid slot location for one of the network interface cards. This should never happen.

Recommended Action Call your technical support representative about obtaining a replacement card.

Recommended Action Save the output of the error message and call your technical support representative for assistance.

Explanation The FDDI interface has failed. This is the second line of the preceding FDDIFAIL message. This line contains debug information.

Recommended Action Save the output of the error message and call your technical support representative for assistance.

Recommended Action Call your technical support representative for assistance.

FDDISTAT Error Message

Recommended Action Call your technical support representative for assistance.

FR Error Message

Explanation The state of the Frame Relay PVC specified by the DLCI has changed.

GRIP Error Messages

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

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

Recommended Action Call your technical support representative for assistance.

HD Error Messages

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

Recommended Action Call your technical support representative for assistance.

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

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.

Recommended Action If either of these messages recur, call your technical support representative for assistance.

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

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

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

Recommended Action Call your technical support representative for assistance.

Recommended Action If either of these messages recur, call your technical support representative for assistance.

IPRT Error Messages

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

Explanation The requested operation failed 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 Too many network subcommands have been entered for this routing protocol.

IPX Error Messages

Recommended Action Call your technical support representative for assistance.

Explanation An internal inconsistency has been detected in the IPX routing table structure.

Recommended Action Note the parameters associated with this message. If possible, clear the IPX routing table by issuing the clear ipx route command. (This will result in lost connectivity until the routing table is rebuilt.) If the message recurs, note the parameters and call your technical support representative for assistance.

Explanation The system has failed to allocate memory for an event. The event variable will be one of the following procedures which attempts to allocate memory:

Recommended Action Call your technical support representative for assistance.

LANCE Error Messages

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

Explanation An Ethernet cable is broken or unterminated, or the transceiver is unplugged. The time delay reflectometer (TDR) counter is an internal LANCE 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 An Ethernet transceiver is malfunctioning, the Ethernet is overloaded, or the Ethernet cable is too long.

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 An Ethernet interface is malfunctioning, or an internal software error has occurred.

Explanation An Ethernet interface generated a spurious Initialization Done interrupt.

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

Recommended Action A small number of underflows may 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.

LANMGR Error Messages

Explanation The router has detected a conflict in assigned ring numbers for the specified Token Ring. The Ring Parameter Server (RPS) function has been shut down to prevent potentially incorrect information from being sourced onto the ring.

Recommended Action Check all bridges connected to this Token Ring and ensure that they are using the same assigned ring number.

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

Explanation The software on this interface cannot support the functions required for LAN Network Manager.

Recommended Action Call your technical support representative about a firmware upgrade for this interface card.

LAPB Error Messages

Recommended Action Check the serial line and the devices attached to the line.

Explanation A FRMR frame was received, indicating that a protocol violation has been detected. The Reason field will be interpreted by generating INFOBAD, CTRLBAD, N1TOOBIG, or INVNR messages immediately after this message; refer to the explanations for these messages for more information.

Recommended Action The protocol will recover by resetting the service. This will disrupt any network service on top of LAPB (for example, X.25 virtual circuits will be cleared). Follow the recommended action for any error message following the FRMR reports; if service becomes unacceptable, check the serial line and its attached devices.

Explanation A received FRMR frame reported that an information field was present in a frame where no information field is allowed.

Recommended Action Check the serial line and the device attached to the line.

Recommended Action Verify that the equipment attached to the serial line is configured with the same K value (maximum number of outstanding I frames).

Explanation A received FRMR reported an information frame that was too long.

Recommended Action Verify that the equipment attached to the serial line is configured with the same N1 value. N1 is in bits and includes the entire frame plus 16 bits of CRC. However, some equipment may require configuration in octets, the omission of the two CRC octets, or the omission of the three octets of LAPB control information.

Explanation There was insufficient memory for the LAPB protocol engine to send a message.

Recommended Action This message is acceptable if it occurs infrequently, because the LAPB protocol is designed to handle loss of frames. Frequent occurrences can cause disruption of service. The system can be configured to ease memory demands or, if conditions warrant, the system can be upgraded to a larger memory configuration.

Recommended Action If either of these messages recur, call your technical support representative for assistance.

LAT Error Messages

Recommended Action If either of these messages recur, call your technical support representative for assistance.

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

Recommended Action If any of these messages recur, call your technical support representative for assistance.

LINEPROTO Error Message

LINK Error Messages

Explanation The lower level software was unable to write a MAC header for a datagram. A probable cause is configuration error.

Recommended Action Call your technical support representative for assistance.

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

Explanation An attempt to map a network level address to a MAC level address has failed.

Recommended Action Call your technical support representative for assistance.

Explanation An internal software error has occurred. The high-level system code tried to use an unimplemented entry point with the virtual IDB driver.

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

Explanation An interface's IP address was successfully learned dynamically through BootP. The first address is the learned IP address. The second IP address is the IP address of the BootP server that provided the information.

Explanation An FCIT running in nonencapsulating transparent mode has detected an FDDI bridge running in encapsulation mode on the same fiber. This is an unstable situation and should be corrected. The incoming interface is displayed, along with the FDDI MAC address in canonical form.

Recommended Action Upgrade the errant interface to full transparent mode. Call your technical support representative for assistance.

Recommended Action Dependent on the specific error condition. Call your technical support representative for assistance.

Recommended Action Record the complete error message and call your technical support representative for assistance.

Recommended Action Call your technical support representative for assistance.

Recommended Action If any of these messages recur, call your technical support representative for assistance.

Explanation The Reverse Address Resolution Protocol (RARP) has resolved an IP address.

Explanation The Serial Line Address Resolution Protocol (SLARP) has resolved an IP address.

Recommended Action If the state change was unexpected, check the configuration settings for the interface.

MAILBOX Error Messages

Recommended Action If any of these messages recur, call your technical support representative for assistance.

MCI Error Messages

Explanation The input error rate was so high that the interface was temporarily disabled. The interface will be automatically reenabled in 30 seconds.

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

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 A hardware device did not respond appropriately to a request. This generally indicates a hardware problem.

Recommended Action Call your technical support representative for assistance.

Explanation The MCI did not answer a Multibus request. This generally indicates a hardware problem.

Recommended Action Call your technical support representative for assistance.

Explanation A hardware device did not respond appropriately to a request. This generally indicates a hardware problem.

Recommended Action Call your technical support representative for assistance.

Recommended Action Call your technical support representative for assistance. You need to replace the malfunctioning component.

MK5025 Error Messages

Recommended Action If either of these messages recur, call your technical support representative for assistance.

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

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.

Recommended Action If either of these messages recur, call your technical support representative for assistance.

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

NIM Error Messages

Recommended Action Call your technical support representative for assistance.

OIR Error Messages

Explanation The OIR facility has detected a newly inserted processor in slot [n]. The inserted interface will be shut down until it is configured by the user or, if an interface of that type was previously configured, it will be restored to its previous state.

Explanation An attempt was made to remove or insert a card in a system containing at least one card that does not support enhanced online inseration and removal (EOIR).

Recommended Action Upgrade to a card that supports EOIR features. If this does not solve the problem, contact your technical support representative for assistance.

Explanation The OIR facility has detected the removal of a processor from slot [n]. The interfaces on that processor will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces.

OSPF Error Messages

Explanation The system has received an OSPF packet with a length field of less than normal header size or inconsistent with the size of the IP packet in which it arrived. This indicates an error in the sender of the packet.

Recommended Action Call your technical support representative for assistance.

Explanation The router has received an LSA with invalid LSA Type. The cause is either memory corruption or unexpected behavior on a router.

Recommended Action From neighbor address, locate the problem router and reboot it. To determine what is causing this problem, call your technical support representative for assistance.

Recommended Action Call your technical support representative for assistance.

Explanation An invalid OSPF packet has been received. Details are included in the error message. The cause might be a misconfigured OSPF or an internal error in the sender.

Recommended Action Check the OSPF configuration of the receiver and the sender for inconsistency.

Recommended Action Call your technical support representative for assistance.

Explanation The router has been flagged as an Area Border Router (ABR) without backbone area in the router.

Explanation While calculating OSPF routes, the router could not find the Link State Advertisement that represents the connected route in the router.

Recommended Action Clear the ip routes in the routing table by entering the command clear ip ro.

Explanation The router is not able to find its own Router Link State Advertisement. This can occur occasionally and self-correct. However, if this message recurs, restart the OSPF process.

Recommended Action Call your technical support representative for assistance.

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 OSPF hello, database description, or database request packet was received, but the router could not identify the sender.

Recommended Action This situation should correct itself. If the message recurs, call your technical support representative for assistance.

Explanation OSPF failed while attempting to allocate a router ID from the IP address of one of its interfaces.

Recommended Action Make sure that there is at lease one interface that is up and has a valid IP address. If there are multiple OSPF processes running on the router, each process needs its own unique router ID. You must have enough "up" interfaces so that each of them can obtain a router ID.

Explanation OSPF has attempted to redistribute a route but could not fine a valid source protocol.

Explanation The software has detected an unexpected condition. The router will take corrective action and continue.

Recommended Action Record the entire error message and note any OSPF problem you experience. Report the error message to your technical support representative.

Recommended Action Call your technical support representative for assistance.

PAD Error Messages

Recommended Action If any of these messages recur, call your technical support representative for assistance.

PARSER Error Messages

Recommended Action Call your technical support representative for assistance.

Explanation A memory allocation failed, possibly because the router is out of memory, or because the parser is using more memory than it should.

Recommended Action If the router is running out of memory, reduce other system activity to ease memory demands. If the router has sufficient memory but the parser is low on memory, call your technical support representative for assistance.

PPP Error Messages

Explanation The remote and local PPP cannot agree on a set of options that both can perform.

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

Explanation The two ends of a serial link have different IPX network numbers.

Explanation The communications line appears to be echoing the characters that are sent to it.

Recommended Action Check your data communications equipment to make sure it is configured correctly.

Explanation PPP was configured to use TACACS, but "extended TACACS" has not been configured or has been disabled.

Recommended Action Either issue the no ppp use-tacacs command to stop PPP from using TACACS, or issue the tacacs-server extended command to enable extended TACACS.

QLLC Error Messages

Explanation Either remote source-route bridging or local acknowledgment is configured incorrectly.

Recommended Action Verify that remote source-route bridging and local acknowledgment are configured correctly.

Recommended Action Verify that the partner QLLC device is configured correctly.

Explanation Either remote source-route bridging is incorrectly configured, or the other RSRB device is down.

Recommended Action Verify that remote source-route bridging is configured correctly with the right version of the IOS software.

Recommended Action Verify that the Token Ring ports and any participating LAN devices are configured correctly.

Explanation The LLC primitive specified has placed the router in an invalid state.

Recommended Action Verify that the Token Ring ports and any participating LAN devices are configured correctly.

Explanation The partner for this QLLC virtual MAC address does not match the MAC address that was defined with the qllc partner command.

Recommended Action Verify that the qllc partner statement in the configuration file is correct.

Explanation The text string provided with this error message describes the specific QLLC problem.

Recommended Action Follow the instructions that appear with the error message. Call your technical support representative for assistance.

Recommended Action Verify that the LAN is not beaconing and that it is not in a congested state. Call your technical support representative for assistance.

Recommended Action Add a valid qllc srb statement for this serial interface.

Explanation An LLC2 session could not be established with the destination MAC address.

Recommended Action Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN.

Recommended Action Define the virtual MAC address, using either the x25 map qllc or the x25 pvc qllc command.

Explanation There is not enough memory in the system to complete this request.

Recommended Action Add more memory to the router. Otherwise, reduce the configuration or the load on the router.

Recommended Action Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN.

Recommended Action Verify that the LAN partner is configured correctly, and that the partner is on the desired LAN.

Recommended Action Verify that the qllc partner and the qllc xid commands are correct.

RCMD Error Messages

Recommended Action Add an entry to the rhost database or determine which client ip address is valid by examining the rhost database.

Explanation Creation of the rsh daemon failed. This is usually caused by a lack of resources such as memory or vty.

Explanation The IP address for an incoming rcmd request is not registered with DNS.

Explanation An attempt was made to connect to a router through rcp, but the router was not configured as an rcp server.

Explanation An attempt was made to connect to a router through rsh, but the router was not configured as an rsh server.

Explanation An attempt was made to connect to a router through the rshell port (514), but the router was not configured as an rsh or rcp server.

REGEXP Error Message

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

REMIF Error Messages

Recommended Action Call your technical support representative for assistance.

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

RSP Error Messages

Explanation High System Availability (HSA) supports two RSP2s on the router. One RSP2 operates as the master, and the other operates as the slave, which takes over if the master RSP2 fails.

Recommended Action For the HSA feature to function properly, both RSP2s require the same boot-ROM version, the same Cisco IOS release (Cisco IOS Release 11.1(4) or later), and the same DRAM configuration. The minimum DRAM required is 24 MB. Call your technical support representative to order software and memory components.

Explanation The router contains a MIP interface. An internal software error occurred on either the RSP or the MIP.

Recommended Action Call your technical support representative for assistance.

RSRB Error Messages

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

Explanation The remote end of a direct serial peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date.

Recommended Action Call your technical support representative for an update.

Explanation The remote end of a TCP remote peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date.

Recommended Action Call your technical support representative for an update.

Recommended Action If any of these messages recur, call your technical support representative for assistance.

Explanation The remote end of a direct serial RSRB connection has detected a configuration problem or traffic that is not recognized by the configuration.

Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn.

Recommended Action If any of these messages recur, call your technical support representative for assistance.

Explanation The remote end of a direct serial RSRB connection has detected a configuration problem or traffic that is not recognized by the configuration.

Recommended Action If either of these messages recur, call your technical support representative for assistance.

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.

Recommended Action If any of these messages recur, call your technical support representative for assistance.

Explanation The local end of a direct serial RSRB connection has detected a configuration problem or traffic that is not recognized by the configuration.

Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration.

SDLC Error Messages

Recommended Action If this message recurs, check the SDLC serial line and the devices attached to it.

Explanation An SDLC frame had to be dropped from the output hold queue, usually because of excessive congestion on the output link.

Recommended Action If this message occurs frequently, determine why your SDLC link is being overloaded with data and resolve the cause (typically by either increasing bandwidth to your SDLC line or reducing the load on your link).

Explanation A FRMR frame was received. This can be due to a noisy serial line, an overloaded SDLC device, or corrupted data.

Recommended Action If this message recurs, service the serial line and the devices attached to it.

Recommended Action Record the entire error message and call your technical support representative for assistance.

Recommended Action If any of these messages recur, check the SDLC serial line and the devices attached to it.

Explanation An information frame was received from the other end of the SDLC link that was larger than allowed with the N1 parameter on this link.

Recommended Action Either increase the value of the N1 parameter for this interface on the router or reduce the size of the maximum information frame sent by the other end of the link.

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

Explanation The router needed to generate an FRMR frame but could not allocate the necessary memory for the frame.

Recommended Action The fact that memory is so low that it cannot allocate the frame is far more serious than the reason for generating the FRMR. Fix the cause of low memory, and if the problem still occurs, determine why the FRMR must be sent.

Explanation This is a software error. A frame was given to the SDLC handler to process, but the interface on which the frame arrived is not known.

Recommended Action Call your technical support representative for assistance.

Recommended Action No action is required. The SDLLC session will restart without operator intervention.

Explanation An internal software error occurred in the router's SDLC processing system.

Recommended Action Call your technical support representative for assistance.

Explanation A protocol error was detected on a secondary station, but FRMR could not be sent because the station did not own the poll bit. This message indicates either poor line conditions or a faulty SDLC implementation.

Recommended Action If the message recurs, perform traces on the SDLC line. Call your technical support representative for assistance.

Explanation SDLC frames were received from an unknown (unconfigured) SDLC address.

Recommended Action Either configure the station for SDLLC or STUN, or shut down the serial interface to disable the line. Call your technical support representative for assistance.

Explanation This condition typically occurs on multidropped lines when the T1 timer interval is too short or the sdlc line-speed command has not been configured. In rare cases the RTS/CTS handshake can delay the transmission of a frame so long that a response is returned after the next station has been polled.

Recommended Action Adjust the value of the sdlc line-speed statement in the configuration file. (Either take line traces to observe appropriate T1 timer intervals, or adjust empirically.)

SDLLC Error Messages

Synchronous Data Link Control/ Logical Link Control Type 2 translation error messages

Explanation An SDLLC media conversion session has been deactivated. If deactivation is a result of an error condition, this message will include a reason.

Recommended Action If the message does not include a description of an error, the deactivation was normal and the message is for information only. If the message does include a description of an error, begin problem analysis. Determine whether session loss is related to llc2 timers by issuing the debug llc2-err command. If the problem is related to llc2 timers, consider using SDLLC with the local acknowledgment feature. Call your technical support representative for assistance.

SEC Error Messages

Recommended Action If any of these messages recur, call your technical support representative for assistance.

SLIP Error Messages

Recommended Action If either of these messages recurs, call your technical support representative for assistance.

SNMP Error Messages

Explanation The user has entered an snmp-server trap-source command. The interface requested for use as the source address has no address associated with it. The SNMP trap is being sent anyway, but without the source address that the user intended.

Recommended Action There are two possible solutions. Either enter a no snmp-server trap-source command to disable the request for a specific source IP address, or add an IP address to the interface referenced in the snmp-server trap-source configuration command.

Explanation The SNMP server was unable to open a port for receiving SNMP requests. This usually happens when the SNMP server is started using the snmp-server community configuration command on a router or communication server with an interface that has no IP address configured. Another possible cause is low memory.

Recommended Action Configure at least one interface with an IP address or specify the no snmp-server command to remove the SNMP server process. Call your technical support representative if problems persist or if it becomes necessary to add memory.

SSE Error Messages

Recommended Action Call your technical support representative for assistance.

Explanation A hardware error has occurred, indicating an unexpected condition on the SSP board.

Recommended Action It might be necessary to replace the SSP. Call your technical support representative for assistance.

Explanation A hardware error has occurred, indicating memory failure on the SSP board.

Recommended Action It might be necessary to replace the SSP. Call your technical support representative for assistance.

Explanation An 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 A hardware error has occurred, indicating an unexpected condition on the SSP board.

Recommended Action It might be necessary to replace the SSP. Call your technical support representative for assistance.

Recommended Action Call your technical support representative for assistance.

STANDBY Error Messages

Explanation Two routers participating in the Hot Standby protocol disagree on the valid authentication string.

Recommended Action Use the standby authentication interface command to repair the Hot Standby protocol authentication discrepancy between the local system and the one whose IP address is reported.

Explanation The Hot Standby protocol software was unable to allocate a packet buffer. The system may be out of memory.

Recommended Action Record the output from the following commands: show proc mem (repeated twice), show mem, show buffers, show version, write terminal. Provide this information to your technical support representative.

Explanation The system was unable to initialize the Hot Standby protocol on an interface. The system may be out of memory.

Recommended Action Record the output from the following commands: show proc mem (repeated twice), show mem, show version, write terminal. Provide this information to your technical support representative.

Explanation The system was unable to initialize an IP connection for the Hot Standby protocol.

Recommended Action Make sure that there is at least one interface configured to run IP.

STUN Error Messages

Recommended Action If any of these messages recur, call your technical support representative for assistance.

Recommended Action Verify that the remote peer is accessible from this router, that it is running software capable of supporting STUN, and that it is configured correctly.

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

Explanation A memory shortage existed at the time that the configuration command was issued. This condition is rare and, under normal conditions, temporary.

Recommended Action Reconfigure the STUN group. If memory shortages persist, call your technical support representative for assistance.

Explanation The system does not have sufficient memory to define a new STUN schema.

Recommended Action This error message should only print when the router is critically short of memory. Call your technical support representative for assistance.

Recommended Action Call your technical support representative for assistance.

Recommended Action Remove and reconfigure the STUN protocol group. Record the configuration and call your technical support representative for assistance.

Explanation A connection attempt to a remote peer has completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.

Explanation A connection to a remote peer is being shut down. This is typically the result of user intervention in STUN reconfiguration or disabling. This is good, expected behavior.

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

Recommended Action If either of these messages recurs, call your technical support representative for assistance.

Recommended Action Examine the other router to see why it closed this connection with this peer. (This can be caused by normal events, such as reconfiguration.)

Recommended Action Examine this router to see why it closed this connection with this peer. (This can be caused by normal events, such as reconfiguration.)

SUBSYS Error Messages

Recommended Action Call your technical support representative for assistance.

SYS Error Messages

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

Explanation A pointer in the block header at the indicated location is corrupt.

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

Recommended Action Call your technical support representative for assistance.

Recommended Action If any of these messages recur, call your technical support representative for assistance.

Recommended Action Call your technical support representative for assistance.

Explanation The boot image parses the configuration saved in NVRAM and encounters a configuration file written by a newer IOS software version. Router operation is unaffected and will function properly.

Explanation The configuration was written successfully through the Maintenance Operation Protocol (MOP).

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

Recommended Action Call your technical support representative for assistance.

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

Recommended Action If any of these messages recur, call your technical support representative for assistance.

Explanation This message indicates that a memory allocation or deallocation was attempted from an interrupt handler.

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

Recommended Action It may be necessary to free some memory by exiting a program. If this message recurs, call your technical support representative for assistance.