|
|
Apple Remote Access Protocol error messages
Explanation An unexpected message was received during the Microcom Networking Protocol version 4 (MNP4) link setup.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation This message appears only when ARA Protocol logging is configured. The message notes that an ARA Protocol user has logged out.
Recommended Action No action is required.
Explanation This message appears only when ARA Protocol logging is configured. The message notes that an ARA Protocol user has logged in.
Recommended Action No action is required.
Explanation A configuration command was not recognized.
Recommended Action Check the configuration file on the server for any invalid configuration commands.
Explanation A user was disconnected from ARA Protocol at an unexpected time. The disconnection may be caused by modems dropping, server error, client problems, or any number of other difficulties.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Explanation Internal data structures are corrupted.
Recommended Action Check for abnormally high CPU usage.
Explanation The ARA Protocol client was denied access, probably because of a configuration problem on the server. The error message should indicate the problem. This message does not indicate access denials caused by bad passwords.
Recommended Action Investigate the problem reported in the error message.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The startup negotiation between a client and the ARA Protocol server fell out of order. If this message is received sporadically, it indicates line noise.
Recommended Action If this message recurs, reinstall the ARA client software.
Explanation The router received an invalid packet during ARA connection setup phase.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Explanation The router resent MNP4 packets the maximum number of times without receiving an acknowledgment.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Explanation This indicates that the router received a disconnect request from the remote Macintosh client.
Recommended Action No action is required.
Explanation This message indicates that the router received MNP4 connection request. MNP4 acknowledgment timer value is also indicated.
Recommended Action No action is required.
Explanation Terminal Access Controller Access Control System (TACACS) authentication failed because extended TACACS is not configured.
Recommended Action Configure extended TACACS.
Explanation Memory not available for internal MNP4 logging.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error occurred.
Recommended Action Report this error to your technical support representative.
Explanation A corrupted packet reached the ARA Protocol code.
Recommended Action Check for excessive CPU usage or excessive line noise.
Explanation The router received an oversized MNP4 frame.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Explanation No buffer exists for an incoming packet.
Recommended Action Examine buffer usage statistics. Possibly more memory is required.
Explanation ARAP connection was terminated without a known cause.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation The router repeated resending of MNP4 packets as the Macintosh client failed to acknowledge previously resent packets.
Recommended Action If this error message persists for several ARAP connections, report it to your technical support representative.
Explanation The software timed out during the MNP4 link setup.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation The router is dropping the connection after doing maximum resends.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The router received an invalid packet during ARAP MNP4 connection setup phase.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Explanation The router disconnected as the remote Macintosh client stopped sending ARAP tickle or data packets.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Asynchronous Security Protocol error message
Explanation This message occurs only when ASP is configured. It indicates the serial interface using ASP is configured incorrectly or does not support asynchronous mode.
Recommended Action Verify the correct hardware interface type is being used.
AppleTalk error messages
Explanation The interface is determining the correct configuration. This message is displayed when discovery mode is enabled and no other router is detected.
Recommended Action No action is required.
Explanation The initial hint address was in use. A search will be made for a valid address.
Recommended Action No action is required.
Explanation The hint address specified for the interface was not valid for the current configuration.
Recommended Action The hint address is ignored and a random valid hint address is automatically computed. No action is required.
Explanation No hint address or a bad hint address was specified. This message indicates which AppleTalk address will be used for the interface.
Recommended Action No action is required.
Explanation The software detected an inconsistency. Although this error is serious, the router attempts to continue. AppleTalk processing might be impaired.
Recommended Action Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your technical support representative.
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 did not detect a route within the required timeout period. Therefore, the route is marked as bad. A network might have become unreachable for some reason, perhaps because of a broken connection. This message does not necessarily indicate an error condition.
Recommended Action No action is required.
Explanation The software detected an unexpected condition. The router takes corrective action and continues.
Recommended Action Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your technical support representative.
Explanation You attempted to remove a route from the routing table by issuing the clear appletalk route command. The command failed because the route was on a directly connected interface (it was created when you configured the router).
Recommended Action Remove the route by reconfiguring the directly connected interface with which it is associated.
Explanation A neighboring router supports only extended AppleTalk networks with a cable range of 1 and with one assigned zone (for example, 25-25).
Recommended Action Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers.
Explanation Although this router has neighbors that require your internetwork to observe compatibility rules, AppleTalk has learned of a route with multiple zone names defined. This condition can cause node inconsistencies on your AppleTalk network.
Recommended Action Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers.
Explanation Although this router has neighbors that require your internetwork to observe compatibility rules, AppleTalk has learned of a route that has a cable range greater than 1. This condition can cause node inconsistencies on your AppleTalk network.
Recommended Action Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers.
Explanation Two routers on the network have the same router ID.
Recommended Action Reconfigure the router to have a unique router ID. If the problem recurs, copy the error message exactly as it appears and report it to your technical support representative.
Explanation The AppleTalk configuration was verified by consulting the indicated router.
Recommended Action No action is required.
Explanation This message is generated by a debug command and provides additional information about an AppleTalk condition.
Recommended Action Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your technical support representative.
Explanation During the verification startup process, a disagreement occurred 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 the default zone until it is overridden.
Recommended Action Use the appletalk zone command to 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.
Explanation A route on the AppleTalk network aged out.
Recommended Action No action is required.
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation The domain router detected a routing loop. Routing loops are not allowed. The domain router runs a background loop detection process. The domain router starts this process when it receives a new zone list from a domain that is identical to the list in the main routing table and whose network range length matches that in this list. The loop detection process sends several AppleTalk Name Binding Protocol (NBP) loopback packets. When one of these packets is received on an interface that does not belong to the original domain, the domain router first shuts off all the domains involved in the loop, and then shuts off all the interfaces in these domains. The loop detection does not catch all types of loops. It is your responsibility to make sure that no loop exists.
Recommended Action Disable the cause of the routing loop. Then use the clear appletalk command to restart the interfaces involved.
Explanation The remap range overflowed. If a network (range) cannot fit inside the remapping range, the network or cable range being advertised by a neighboring router is not accepted. When an overflow occurs, all interfaces in the domain are disabled.
Recommended Action Use the appletalk domain remap-range command to increase the remapping range. Then restart the interfaces.
Explanation Another AppleTalk node on a common network interface claimed the same AppleTalk address used by this router. This error indicates a serious, unexpected problem. If it recurs, a physical network problem might exist in which the nodes cannot communicate with each other.
Recommended Action The interface on this router restarts AppleTalk processing on the common network interface to resolve the address conflict. No action is required.
Explanation An AppleTalk hardware interface was disabled.
Recommended Action No action is required.
Explanation An AppleTalk Enhanced IGRP interface that was previously shut down was restarted.
Recommended Action No action is required.
Explanation A new AppleTalk Enhanced IGRP path has been learned. The message indicates the source of the path, its distance in hops, its metric, and the type of path.
Recommended Action No action is required.
Explanation AppleTalk Enhanced IGRP did not have enough time to process packets.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation A peer router is unreachable.
Recommended Action No action is required.
Explanation A new neighbor appeared on the network.
Recommended Action No action is required.
Explanation Another AppleTalk router on the FDDI ring is running a release of the router software earlier than 9.0(2). Routers running these early software releases use an encapsulation for AppleTalk on FDDI rings that is not compatible with the Apple FDDITalk implementation.
Recommended Action Upgrade the routers running the software releases that use the pre-FDDITalk encapsulation for AppleTalk on FDDI rings.
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 A clear interface command was issued on an interface that is currently routing AppleTalk.
Recommended Action No action is required.
Explanation An AppleTalk hardware interface was disabled because of a bad serial line, a configuration command, or a bad interface.
Recommended Action If the interface was not intentionally disabled, this message indicates a hardware problem. In this case, repair or replace the applicable hardware.
Explanation The hardware interface was reset because of a configuration change. After the reset, AppleTalk automatically reinitialized the interface.
Recommended Action No action is required.
Explanation An AppleTalk interface that was previously shut down was restarted.
Recommended Action No action is required.
Explanation An unrecognized command was specified in the Name Binding Protocol (NBP) test facility.
Recommended Action Enter a valid command.
Explanation A peer router is unreachable.
Recommended Action No action is required.
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. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command. When this error occurs, the MacIP configuration is considered invalid and is deleted.
Recommended Action No action is required.
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. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.
Recommended Action No action is required.
Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server can no longer operate because of 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. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.
Recommended Action No action is required.
Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server is fully initialized and is ready to accept client requests. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.
Recommended Action No action is required.
Explanation A computed multicast address disagrees with that provided by another AppleTalk router. The other AppleTalk router might be misconfigured or faulty.
Recommended Action Correct the problem at the other router.
Explanation The clear appletalk neighbor command displays this command when it completes successfully.
Recommended Action No action is required.
Explanation A neighboring router to which this router previously lost connectivity reappeared on the network.
Recommended Action No action is required.
Explanation The interface was disabled because the configured AppleTalk address or cable range for the interface conflicts with that of another router on the attached network.
Recommended Action Reconfigure the affected routers so that there are no conflicting addresses or cable ranges on the attached network.
Explanation The configuration specified for the interface conflicts with the active AppleTalk internetwork. For example, a cable range might be configured that overlaps an existing route but does not match the entry exactly.
Recommended Action Use the appletalk cable-range command to reconfigure the interface so that there are no conflicts with the existing AppleTalk network, or take any other actions necessary to resolve the conflict. AppleTalk will periodically attempt to restart the interface.
Explanation The router discovered a new AppleTalk router on the network.
Recommended Action No action is required.
Explanation A new AppleTalk route was learned. The message indicates the source of the route and its distance in hops.
Recommended Action No action is required.
Explanation A new AppleTalk zone was created.
Recommended Action No action is required.
Explanation No free node could be found on the interface.
Recommended Action If your AppleTalk network has less than 250 nodes, issue the debug appletalk errors command and then call your technical support representative. If your AppleTalk network has more than 250 nodes, split it into smaller networks by creating new segments and moving some nodes into the new segments.
Explanation A path to the specified network could not be found.
Recommended Action Use the show appletalk route command to verify that a path to the specified network exists. If it does, copy the error message exactly as it appears, and report it along with the output of the show appletalk route command to your technical support representative.
Explanation An AppleTalk node 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 to another network and is, therefore, misconfigured for the current network.
Recommended Action No action is required.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A previously configured Name Binding Protocol (NBP) proxy was deleted. The router can no longer convert NBP requests to a format understood by routers that support only the original AppleTalk specification.
Recommended Action No action is required.
Explanation The router could not deliver a packet to a destination because it did not know where to send it.
Recommended Action Use the show appletalk route command to verify that a path to the destination exists. If it does, copy the error message exactly as it appears, and report it with the output of the show appletalk route command to your technical support representative.
Explanation The router could not generate an AppleTalk packet because no valid AppleTalk source address was available to identify this router in the packet.
Recommended Action Configure an interface to have an address or cable range. Use the show appletalk command to verify that the interface is operational.
Explanation You specified a nonexistent neighbor address in a show appletalk neighbor or clear appletalk neighbor command.
Recommended Action Specify a valid neighbor address (one that appears in the output of the show appletalk neighbor command).
Explanation You specified a nonexistent route in a show appletalk route or clear appletalk route command.
Recommended Action Specify a valid route (one that appears in the output of the show appletalk route command).
Explanation You tried to show or change the AppleTalk configuration when AppleTalk routing was not turned on.
Recommended Action Issue the appletalk routing command before issuing any other AppleTalk configuration or display command.
Explanation An encapsulation method on the specified interface does not support AppleTalk.
Recommended Action No action is required.
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The firmware on the MCI controller card does not support AppleTalk fast switching.
Recommended Action No corrective action is required. Normal AppleTalk operation continues, but the fast-switching cache is disabled for the interface associated with the MCI card. If this message is unexpected, verify that the MCI 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 interface.
Recommended Action No action is required.
Explanation AppleTalk Update-Based Routing Protocol (AURP) detected packets that were out of sequence. This might be caused by a lost connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A new AppleTalk path has been learned. The message indicates the source of the path, its distance in hops, its metric, and the type of path.
Recommended Action No action is required.
Explanation The path to a network changed because either the old path went down or the new path was better.
Recommended Action No action is required.
Explanation A path on the AppleTalk network aged out.
Recommended Action No action is required.
Explanation A router went down somewhere on the AppleTalk network. The indicated peer notified this router of the change.
Recommended Action No action is required.
Explanation The router detected a conflicting cable range. A router is configured with a cable range that overlaps with an existing range, but does not match the entry exactly.
Recommended Action Use the show appletalk command to identify the overlapped cable range, and then reconfigure the misconfigured router.
Explanation A name registration call is being performed.
Recommended Action No action is required.
Explanation A connected route is being advertised as down (also known as "notify neighbor") because the configured interface is no longer operational.
Recommended Action No action is required.
Explanation A router went down somewhere on the AppleTalk network. The indicated peer notified this router of the change.
Recommended Action No action is required.
Explanation A routing update was received for a previously suspect route.
Recommended Action No action is required.
Explanation The state of a path changed.
Recommended Action No action is required.
Explanation An internal error occurred. Specifically, a programming assertion in the AppleTalk networking code was violated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation The zone list of the configured interface is inconsistent with the zone list of other routers.
Recommended Action Reconfigure the zone list on the router so that it does not conflict with that the zone lists on other routers.
Explanation The router removed an unused zone from the zone table.
Recommended Action No action is required.
Explanation This message reports the zone name and network number that are being advertised to support the appletalk nbp-proxy command.
Recommended Action When proxy service is initiated, this message is generated each time the appletalk nbp-proxy command is issued. No action is required.
Asynchronous Transfer Mode error messages
Explanation The command just entered causes ATM Soft Restart.
Recommended Action Stand by and let ATM Signaling and ILMI to restart.
Explanation System memory exhaustion caused an internal software error in the ATM subsystem.
Recommended Action If the system exhibits any unexpected behavior as a result of this memory exhaustion, it may need to be reset to clear the error. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Explanation This message can occur for the following unrelated reasons. Each reason is accompanied by a recommended action.
Recommended Action If none of the previous actions fix the problem, copy the error message exactly as it appears and report it to your Cisco technical support representative.
Explanation The command just entered sets up a new ILMI access filter for address registration. It only affects new addresses to be registered. The addresses already registered will not be affected.
Recommended Action Issue the shutdown and no shutdown commands on this interface to restart address registration if you need to remove addresses already registered but not permitted by the new access filter.
Explanation The command just entered enables ATM address registration.
Recommended Action Issue the shutdown and no shutdown commands on this interface if you need to start address registration right away. Otherwise, wait for the next interface restart.
Explanation ATM auto-configuration has been enabled already. The atm auto-configuration command just entered is ignored.
Recommended Action No action is required.
Explanation Configuration of adjacent peer device has been changed.
Recommended Action Wait for the interface to restart itself.
Explanation The command just entered sets up new global default access filter for address registration. It only affects new addresses to be registered on interfaces using the global default. The addresses already registered will not be affected.
Recommended Action Issue the shutdown and no shutdown commands on desired interfaces to restart address registration if you need to remove addresses already registered but not permitted by the new global default access filter.
Explanation Adjacent peer device is not responding to Interim Local Management Interface (ILMI) Keepalive polling.
Recommended Action Check the connection of the ATM interface and the status of the adjacent peer device. Correct them if necessary. Wait and check if ILMI Keepalive comes up again. If the problem persists, copy this warning message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The command just entered causes auto-configuration to be disabled. The most recently entered interface parameters will be used at the next interface restart.
Recommended Action Note which parameters have been configured.
Explanation ATM auto-configuration has been disabled already. The no atm auto-configuration command just entered is ignored.
Recommended Action No action is required.
Explanation The calling or called party has a maximum transmission unit (MTU) size configured that is different from the MTU size on the current interface.
Recommended Action Either change the configured MTU size on the current interface to that of the caller's or called party's interface, or change the caller's or called party's interface to match the current interface.
Explanation The specified ATM interface hardware has run out of interface memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The ATM subsystem ran out of the internal resources necessary to create a new virtual circuit. This may indicate a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation The ATM peer equipment appears to be running an old version of ATM UNI. Communication with it is not possible.
Recommended Action The peer equipment must be upgraded in order to communicate with this system.
Explanation Either the configuration contains invalid traffic shaping parameters or the software ran out of rate queues.
Recommended Action Check the configuration for errors.
Explanation MinSvccVci is greater than MaxVci, after negotiation with the peer through ILMI.
Recommended Action Disable auto-configuration on both sides and change the port configuration appropriately so that SVCCs can be setup.
ATM access concentrator PCI port adapter driver error messages
Explanation The port adapter failed its initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The port adapter failed its initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The port adapter failed its initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation Bridge configuration failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The port adapter ID was not correct.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The port adapter failed its initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The PCI device ID was not correct.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
ATM core error messages
Explanation The ATM core subsystem encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The ATM core subsystem encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The ATM core subsystem encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The ATM core subsystem encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
ATM port adapter error messages
Explanation The PA host driver detected a duplicate rx host buffer returned.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The port adapter received a packet on a non-existent VC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The TI1570 chip reserves three RX DMA channels for OAM cells. As a result, the last three VCIs of the last VPI block cannot be used for regular traffic.
Recommended Action Try different VCI/VPI combinations.
Explanation The port adapter failed to process a command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A memory test failed within the PCI control memory. This probably indicates a memory chip has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR CW4010 Registers dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR CW4010 Registers dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR CW4010 Registers dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR CW4010 Registers dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR CW4010 Registers dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR CW4010 Registers dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR CW4010 Registers dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR CW4010 Registers dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The software could not identify the interface card.
Recommended Action Power down the system, reseat the interface card, and reboot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The port adapter received a giant packet.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The port adapter failed to complete hardware initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The bandwidth requirements of the installed port adapters exceed the processor's rated capability.
Recommended Action Either remove one of the port adapters or upgrade the VIP.
Explanation The ATM Deluxe PCI driver found an incorrect PCI device ID during initialization. A hardware failure could have the caused the wrong ID to be read, or the software in use does not support hardware that did not exist at the time the software was written.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR miscellaneous dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR miscellaneous dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR miscellaneous dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR miscellaneous dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The driver found a device type other than what it expected in the specified PCI slot. If the device is a TI1570 then a hardware failure may have occurred.
Recommended Action Power down the system, re-seat the interface card, and reboot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation This message is probably caused by memory exhaustion. Memory could not be allocated by the driver for a packet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Explanation The port adapter needs more PCI memory. The installed amount is less than required by the drivers for packet buffers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A parity error occurred on the PCI bus. This probably indicates an existing or developing hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR APU Registers dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR APU Registers dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR APU Registers dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation SAR APU Registers dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information
Explanation The port adapter failed to write a register.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The port adapter failed to send a report from the VIP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A receive DMA channel failed to deactivate during shutdown of a virtual circuit. This failure could originate in hardware or software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation This message indicates that excessive traffic congestion on the ATM interface may have resulted in cell loss. The PCI-ATM interface's cell buffers were full when a cell arrived on the interface, resulting in a receive freeze condition.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The SAR chip crashed, and the interface is being reset.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A transmit DMA channel failed to flush its buffers during shutdown of an ATM interface. This failure could originate in hardware or software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The PCI-ATM interface had to stop the transmitter while waiting for data.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An attempt was made to configure a rate queue on an ATM Lite port adapter that does not support rate queues.
Recommended Action Check the configuration and try again, avoiding unsupported features.
ATM signaling subsystem error messages
Explanation A software error occurred during removal of a member from a closed user group. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A software error occurred during addition of a member to a closed user group. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A software error occurred during removal of a party from a point-to-multipoint call. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A software error occurred during addition of a party to a point-to-multipoint call. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A software error occurred during closure of an SVC. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A software error occurred during creation of an SVC. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A configuration error occurred in the ATM Signaling subsystem. The message will display more specific information about the problem location.
Recommended Action Correct the configuration.
Explanation An internal software error occurred while handling a user request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error occurred. This message should only be displayed when verbose debugging is enabled for an SVC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error occurred during installation of an SVC cross-connect.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation This message indicates an error in the PNNI routing subsystem. It could be caused by an internal software error or by bad control information received from peer equipment. The message will contain additional information that can help locate the cause. Any message with "NULL" probably indicates a problem with this system; other messages probably point at the peer equipment.
Recommended Action Check this system and the peer equipment for any obvious errors. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error occurred, probably including memory exhaustion.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Service Specific Connection Oriented Protocol (SSCOP) error messages
Explanation A software error occurred in the ATM SSCOP subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation This message indicates a routine step of the ATM SSCOP initialization sequence.
Recommended Action No action is required.
Explanation The ATM peer equipment appears to be running an old version of ATM UNI. Communication with it is not possible.
Recommended Action The ATM peer equipment may need attention. Verify its UNI version is at least 3.1, and upgrade if necessary.
PIMv2 AUTORP error messages
Explanation There are an abnormally large number of items in the RP queue. This could indicate that the system CPU is overloaded.
Recommended Action Reduce other system activity to ease processor demands. If conditions warrant, consider changes to the network architecture to handle more volume, including upgrading to a larger router.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
PPP Bandwidth Allocation Protocol error messages
Explanation An internal software error occurred.
Recommended Action Call your technical support representative and report the error message, the system version, and the router configuration. (Use the show version command to obtain the software version.)
Explanation BAP will not be operational and will not be negotiated.
Recommended Action Call your technical support representative and report the error message, the system version, and the router configuration. (Use the show version command to obtain the software version.)
Border Gateway Protocol error messages
Explanation An addition to the radix trie could not be completed because of an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation A BGP neighbor has either come up or gone down. The message describes the change for it. This message appears only if the log-neighbor-changes command is configured for the BGP process.
Recommended Action This informational message normally appears as routers and BGP neighbors go up or down. However, unexpected neighbor loss might indicate high error rates or high packet loss in the network and should be investigated.
Explanation The remote BGP peer sent in an update with an invalid AS path.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation A BGP path could not be deleted because of an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation A deletion from the radix trie could not be completed because of an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation 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 The number of parallel paths exceeds the configured limit.
Recommended Action Increase the number of parallel paths allowed.
Explanation The number of prefixes received from a neighbor reached the warning limit.
Recommended Action Check the number of prefixes received from the neighbor and determine if the limit should be increased.
Explanation The number of prefixes received from a neighbor exceeds the configured limit.
Recommended Action Check the number of prefixes received from the neighbor and determine if the limit should be increased.
Explanation The counter value for accepted prefixes is incorrect and less than zero.
Recommended Action This is a rare situation and is a result of an internal problem. Reset the session to correct it.
Explanation The remote BGP peer sent in a route with an illegal next hop. The given route was ignored.
Recommended Action No action is required.
Explanation The allocation of a neighbor index for this neighbor 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 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 the radix trie 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.
ISDN Basic Rate Interface error messages
Explanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
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 ISDN leased line requires an ISDN switch type configure.
Recommended Action Choose and configure a BRI switch type; if unsure, choose any switch.
AS5200 BRIMUX board error messages
Explanation A BRIMUX firmware problem may be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A BRIMUX firmware problem may be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A BRIMUX board hardware problem may be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A BRIMUX firmware problem may be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A BRIMUX firmware problem may be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A BRIMUX firmware problem may be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A BRIMUX firmware problem may be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A B-channel on the BRIMUX board changed state.
Recommended Action No action is required.
Explanation A BRIMUX board hardware or firmware problem may be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation A port on the BRIMUX board changed state.
Recommended Action No action is required.
Explanation A BRIMUX board changed state.
Recommended Action No action is required.
Binary Synchronous Communications (Bisync) protocol error messages
Explanation An unexpected receive occurred during a transmission.
Recommended Action Verify that the line has been consistently defined with regard to the carrier. If the message is continuously reported, issue the shut and no shut commands to restart the bisynchronous interface in question.
Explanation This message occurs only when BSC local acknowledgment is configured. It indicates the serial interfaces that are using the BSTUN tunnel are configured incorrectly (both have been configured as a secondary).
Recommended Action Reconfigure the serial interfaces correctly to be a primary and secondary pair.
Explanation This message indicates that memory in the router was exhausted.
Recommended Action Perform diagnostics on the router to locate the subsystem or interface responsible for consuming memory. The only method that will clear this situation is to reload the router.
Block serial tunneling error messages
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation An attempt to connect to a remote TCP BSTUN peer failed.
Recommended Action Verify that the remote peer is accessible from this router, that it is running software capable of supporting BSTUN, and that it is configured correctly.
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation BSTUN was unable to start the interface for handling the specified protocol traffic.
Recommended Action If this message appears while you are configuring BSTUN, check for other system errors (such as no available memory in the router, or the interface shutting down). If no obvious problem can be detected, record all the displayed values and any other BSTUN error messages, and contact your technical support representative.
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 BSTUN group. If memory shortages persist, call your technical support representative for assistance.
Explanation An action was taken that requires the previous definition of a BSTUN group number.
Recommended Action Make sure encapsulation bstun and the bstun group have been defined for the interface.
Explanation A BSTUN route has not been configured for the frame with a destination address.
Recommended Action If this message appears while you are debugging BSTUN, it indicates that no specific BSTUN route has been configured for the frames being received with the device address listed in the packet debug trace. You may choose to configure a BSTUN route, or ignore this message.
Explanation A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.
Recommended Action No action is required.
Explanation A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.
Recommended Action No action is required.
Explanation A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.
Recommended Action No action is required.
Explanation A connection to a remote peer is being shut down. This is typically the result of user intervention in BSTUN reconfiguration or disabling. This is good, expected behavior.
Recommended Action No action is required.
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation The BSTUN background process is terminating.
Recommended Action If this message appears while you are unconfiguring BSTUN, no action is required. Otherwise, record all the displayed values and any other BSTUN error messages, and contact your technical support representative.
Explanation A remote peer reestablished a connection to this router.
Recommended Action No action is required.
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Explanation A remote peer closed a BSTUN connection with this router.
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).
Explanation This route closed a BSTUN connection with a remote peer.
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).
Explanation An event passed to the BSTUN layer for processing could not be decoded.
Recommended Action Perform a hard restart on the indicated interface.
Cisco 1600 platform error messages
Explanation Your router is functional. However, there is an interface that the software does not recognize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The operation might have failed because of a transient network problem.
Recommended Action Retry the operation. If the problem persists, call your technical support representative for assistance.
|
|