|
|
Operating system error messages
Explanation A block of memory at the indicated location is corrupt.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation A block of memory at the indicated location is corrupt.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An invalid status code has been passed to a buffer-deletion routine. The buffer will be correctly returned to the free pool, but will not be correctly counted in the per-protocol statistics.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A block of memory at the indicated location is corrupt.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation A pointer in the block header at the indicated location is corrupt.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The free memory pool is corrupt.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation This is an auxiliary message to several memory-related messages. It provides a formatted display of some of the information in the header of a corrupted data block.
Recommended Action This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of the previously printed error message.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation At least one informational or error message was printed by the boot loader.
Recommended Action If the system image was loaded, no action is recommended. If the system image did not load as configured, send a log file and configuration information to your technical support representative.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation No memory was available to create a process.
Recommended Action If you suspect a memory leak, copy this message exactly as it appears, and report it to your technical support representative. If a memory leak does not appear to be the problem, ensure that more memory is available to support the additional features.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The router's configuration was changed.
Recommended Action This is a notification message only. No action is required.
Explanation The router has been configured to generate nonvolatile memory using the commands of an older software release. The current configuration of the router contains a command that cannot be saved using only the older command set.
Recommended Action Allow the router to save the configuration using the command set of the current software release, or remove the commands that cannot be saved using the older command set.
Explanation The router's configuration was changed.
Recommended Action This is a notification message only. No action is required.
Explanation The software detected that the configuration saved in memory was written by a newer software release. There might be commands saved in memory that are not implemented by the older software release.
Recommended Action Examine all the messages printed while the router was booting. For each message about an unknown command, determine whether that feature is required. If so, upgrade to a newer software release that supports that feature.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The configuration was written successfully.
Recommended Action This is a notification message only. No action is required.
Explanation The write of the nonvolatile configuration failed because an internal variable was not set properly.
Recommended Action If this messages occurs, copy it exactly as it appears and report it to your technical support representative.
Explanation The write of the nonvolatile configuration failed.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation The indicated process ran too long without relinquishing the processor.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation The software requested a buffer that is larger than the largest configured buffer size, or it requested a negative-sized buffer.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An operation could not be accomplished because of a low-memory condition. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the router's memory.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation The software image being run is for a different hardware architecture. This problem can occur on a Cisco 1003, Cisco 1004, or Cisco 1005. The Cisco 1003 and Cisco 1004 use a different image from the Cisco 1005.
Recommended Action Install the correct software image.
Explanation This message indicates that a memory allocation or deallocation was attempted from an interrupt handler.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation The router is configured to crash when total available memory drops below a specified threshold. That threshold has been reached.
Recommended Action It might be necessary to free some memory by exiting a program. If this message recurs, call your technical support representative for assistance.
Explanation The requested memory allocation is not available from the specified memory pool. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the router's memory.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation This is an auxiliary message to several memory-related messages. It provides a raw display of the information in the header of a corrupted data block.
Recommended Action This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of the previously printed error message.
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Explanation This is an auxiliary message to several memory-related messages. It provides the address of the memory block and the calling program counter for the last eight blocks allocated and for the last eight blocks freed.
Recommended Action This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of a previously printed error message.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation Your system is not configured to be a bridge.
Recommended Action Configure the bridging software.
Explanation The router is configured to crash when the largest available contiguous memory block drops below a specified threshold. That threshold has been reached.
Recommended Action It might be necessary to free some memory by exiting a program. If this message recurs, call your technical support representative for assistance.
Explanation An operation could not be accomplished because of a low-memory condition. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the router's memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a configuration that has more memory.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation A block of memory in the free pool is actually in use. The message indicates the number of processes using the memory block.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation A configuration was accepted over the network, so the setup session will be aborted.
Recommended Action This is a notification message only. No action is required.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation The environmental monitor detected a high-temperature condition.
Recommended Action Ensure that the room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. Call your technical support representative for assistance, if necessary.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred.
Recommended Action Copy this messages exactly as it appears, and report it, along with the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages, to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation A reload or restart was requested.
Recommended Action This is a notification message only. No action is required.
Explanation SNMP cannot be used to reload the router unless this functionality has been previously configured. This message reports that an attempt to reload the router failed because SNMP reloads are not currently configured on the router.
Recommended Action This is a notification message only. No action is required.
Explanation A reload or restart was requested.
Recommended Action This is a notification message only. No action is required.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the message exactly as it appears and report it your technical support representative.
Explanation SNMP is reading the host configuration from a network host.
Recommended Action This is a notification message only. No action is required.
Explanation SNMP is reading the network configuration from a network host.
Recommended Action This is a notification message only. No action is required.
Explanation SNMP is writing the current configuration to a network host.
Recommended Action This is a notification message only. No action is required.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation An internal table entry became corrupt.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Explanation This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred.
Recommended Action Copy this message exactly as it appears, and report it, along with the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages, to your technical support representative.
Explanation The indicated callback routine ran for too long without relinquishing the processor.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Explanation The indicated process ran for too long without relinquishing the processor. The system killed it as a runaway process.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation A freed buffer was placed on the wrong list of free buffers.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Explanation A software error occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
System controller subsystem error messages
Explanation A SDP hello packet was received from the shelf, which is not trusted.
Recommended Action Specify either the correct SDP password and/or destination on the shelf from which this message was received.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The system controller found a shelf with an invalid IP address.
Recommended Action Check the IP address set on the shelf.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation Two shelves with same the shelf-id are configured in the system.
Recommended Action Change the shelf-id for one of the shelves.
Explanation This message contains health monitor setup commands polling information. If you see this message every ten minutes, the health monitor is not able to set that corresponding entry on that shelf.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The health monitor failed to setup the monitoring command on a particular shelf.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The SDP packet received by the system controller contained an invalid version number.
Recommended Action Check that the shelf is running a compatible version of SDP. If this message recurs, call your technical support representative for assistance.
Explanation No SDP hello packets were received from the particular shelf, which could indicate that the particular router shelf is down or is misconfigured.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The SDP protocol on the system controller has detected a particular shelf.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The SDP protocol on the system controller has detected that a particular shelf configuration has changed.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation A likely cause of this error message is that the performance collector process has terminated.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The SDP protocol on the system controller has detected that a particular shelf has reloaded.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The SDP protocol on the system controller did not receive hello packets from a particular shelf.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The SDP protocol on the system controller has detected a particular shelf.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The indicated shelf is not responding to SNMP requests.
Recommended Action Check the SNMP configuration for the above shelf and also check that the correct community string is specified in the system-controller community command on the system controller.
Syslog-server file system routines error messages
Explanation A syslog file was not created.
Recommended Action There is probably no PCMCIA disk on slot0 on the system controller. Check to see if it is a PCMCIA Flash.
Explanation You may have issued a directory name that already exists on the PCMCIA disk.
Recommended Action Check to see if the directory name you supplied already exists on the PCMCIA disk and re-enter a different name.
Explanation The syslog records are not timestamped, possibly because the service timestamps command was not issued.
Recommended Action Issue the service timestamps log datetime command on your router. This will cause the system to timestamp debugging or logging messages. At a minimum, use the datetime keyword.
Explanation Illegal file system.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The maximum allowed syslog files was exceeded.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation There was no configuration change to the syslog-server.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation There is no memory left.
Recommended Action The system controller is running very low on memory. If this message recurs, call your technical support representative for assistance.
Explanation There is no syslog file.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation A syslog file was not opened. One or more of the subfiles may have been deleted or there is no PCMCIA disk.
Recommended Action You may not have a PCMCIA disk in slot 0 on the system controller. Check to see if it is a PCMCIA Flash. If one or more of the subfiles is missing, they will be automatically restored when the current file reaches its capacity and gets archived.
Explanation The router is not configured to timestamp all the log messages.
Recommended Action Configure your router with appropriate commands to timestamp the log messages (for example, use the service timestamps command).
Explanation A file was not read.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The command or device name is unknown, or the router was unable to find the device address.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation A syslog file was not written.
Recommended Action If this message recurs, call your technical support representative for assistance.
System Management error messages
Explanation System Management Remote Procedure Call operation failure. Request for information from the CIP card will not be processed.
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 System Management Remote Procedure Call Network management event error detected.
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 System Management Remote Procedure Call operation failure. Request for information from the CIP card will not be processed.
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.
Terminal Access Controller Access Control System (TACACS) protocol error messages
Explanation This command is deprecated and should no longer be used. Instead, the timeout login response command now provides this functionality.
Recommended Action Use the line-command timeout user-response.
Explanation A background TACACS notification (enabled with the tacacs notify command) was not acknowledged by the TACACS server processor within the timeout period (5 minutes). The information contained in that notification was lost. This loss of information may interfere with accounting or auditing on the server. This condition arises when the TACACS server is misconfigured, crashed, or became unreachable via the network.
Recommended Action Check the TACACS server and the network attached to it.
Explanation The TACACS facility received a message it was not expecting. This may occur when a TACACS server sends duplicate responses or when it responds to a request that has already timed out. It also may be caused by an internal software problem.
Recommended Action If this message recurs, call your technical support representative for assistance.
Explanation The TACACS facility created a message that contains an access list that is not a valid access list (out of bounds).
Recommended Action If this message recurs, call your technical support representative for assistance.
Tag distribution and control error messages
Explanation When a new IP address for a TDP peer is learned, it may be necessary to update the Tag Forwarding Information Base (TFIB) for any routes for which the new address is a next hop. Deciding whether it is necessary to update the TFIB is the responsibility of an address process. This message is generated when an attempt to create the address process fails.
Recommended Action This is an informational message. As long as it needs the process, the system will regularly attempt to create it. If this message recurs, copy it exactly as it appears and report it to your technical service representative.
Explanation When a new IP address for a TDP peer is learned, it may be necessary to update the Tag Forwarding Information Base (TFIB) for any routes for which the new address is a next hop. Deciding whether it is necessary to update the TFIB is the responsibility of an address process. This message is generated when an attempt to queue work for the address process fails.
Recommended Action This is an informational message. The system remembers that it needs to do this work and will regularly attempt to queue the necessary work item. If this message recurs, copy it exactly as it appears and report it to your technical service representative.
Explanation An attempt to allocate a tag-switching data structure failed because of a low memory condition.
Recommended Action Reduce other system activity if possible. If this message persists, call your technical service representative for assistance.
Explanation An unexpected failure occurred while building a TDP protocol information element (PIE) for transmission to a TDP peer. It occurred when attempting to add a tag binding or an address to the PIE.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation An action attempted by the Tag Control process encountered an unexpected condition.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation A problem was encountered in clean up following termination of a Tag Distribution Protocol (TDP) session.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation A TDP protocol information element (PIE) received from a TDP peer contained an unexpected binding list type. The PIE will be ignored.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag-switching ip), waiting 15 to 20 seconds, and then reenabling it (tag-switching ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Explanation An operation on the TDP Directed Adjacency data structure failed.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation Internally when a process, such as the TDP process, must request the tag distribution and control process to take some action, it queues a work item for the tag distribution and control process. This message is generated when an attempt to queue work for the tag distribution and control process fails. The failure can occur if the system is unable to allocate memory to hold the work request, or if the process has stopped processing requests on its work queue.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation The tag distribution and control process failed to initialize itself. The probable cause is insufficient memory.
Recommended Action Reduce other system activity if possible. If this message persists, call your technical service representative for assistance.
Explanation The system was unable to initialize the data structure used to support allocation of tags for tag switching for the specified tag pool.
Recommended Action The system proceeds by ignoring the event. However, since the system will not be able to allocate tags from the tag pool, it will not advertise them to peers. Therefore, it will not be able to forward tagged packets it receives (because it does not advertise tags, it should not receive tagged packets). Copy the message exactly as it appears and report it along with the startup and running configuration to your technical service representative.
Explanation The revision number used to manage advertisement of interface addresses to TDP peers overflowed. This will result in faulty advertisement of interface addresses to TDP peers and faulty tag switching on those peers.
Recommended Action To restore proper interface address advertisement, reboot the platform. Report this condition to your technical service representative.
Explanation A tag distribution protocol (TDP) peer requested an action that is not currently implemented by the tag distribution and control subsystem.
Recommended Action The request will be ignored. If the message recurs, copy the message exactly as it appears and report it to your technical service representative.
Explanation An operation involving the state machine for a TDP peer failed.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation An attempt to create the tag distribution and control process failed. The probable cause is insufficient memory.
Recommended Action Reduce other system activity if possible. If this message persists, call your technical service representative for assistance.
Explanation Some Tag Information Base (TIB) maintenance operations involve a complete scan (walk) of the TIB radix tree data structure. This message is generated when a TIB walk encounters an unexpected failure.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation An attempt to queue a TDP protocol information element (PIE) for transmission to a TDP peer failed.
Recommended Action This is an informational message. Failure to queue a PIE for a peer should occur only when the TDP session with the peer no longer exists. The software should recover from this situation by discarding the TDP session and trying to establish a new one. If this message recurs, copy it exactly as it appears and report it to your technical service representative.
Explanation An operation on the state machine for the tag distribution and control process failed.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation The tag distribution and control process maintains a data structure used to convert between the TDP identifier for a TDP peer and the IP addresses of that peer. This message is generated when an internal inconsistency is discovered in that data structure.
Recommended Action Disable dynamic tag switching at the chassis level (no tag-switching ip), wait 15 to 20 seconds, and then reenable it (tag-switching ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Explanation The tag distribution and control process maintains a data structure that is used to convert between the TDP identifier for a TDP peer and the IP addresses of that peer. This message is generated when an internal inconsistency is discovered in that data structure.
Recommended Action Disable dynamic tag switching at the chassis level (no tag-switching ip), wait 15 to 20 seconds, and then reenable it (tag-switching ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Transparent bridging error messages
Explanation The transparent bridging driver received a packet with unrecognizable encapsulation. The packet had to be discarded.
Recommended Action This could indicate that a network media error occurred or that a protocol is being used that is newer than this Cisco IOS software release. If it is believed that the dropped packets are of a real protocol, upgrade to a new release of the software that handles the protocol.
Explanation There is a configuration problem. The specified extended access list either does not exist or contains an error.
Recommended Action Correct the configuration problem.
Explanation A packet was received that exceeds the expected maximum transmission unit (MTU) length for the receiving interface. The first 4 bytes of the packet following the source address are also provided to assist diagnosis.
Recommended Action Use the address and packet information provided to trace the source of these packets and reduce its MTU to conform to the standard for the given media.
Explanation Transparent bridging was configured on an interface that does not support it.
Recommended Action Remove transparent bridging from the configuration on the specified interface.
Explanation A transparently bridged packet destined for an ATM interface cannot be fully addressed.
Recommended Action Clear the bridge table to force relearning of all addresses.
Explanation An ATM interface was configured for transparent bridging without also specifying the associated virtual circuits.
Recommended Action Configure the required virtual circuits on the specified interface.
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
ATM TAG control error messages
Explanation An internal inconsistency was detected when an attempt was made to insert an item in a list.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation ATM TAG Control uses a table driven state machine to keep track and transition a TVC through various states. A state transition occurs when a TVC receives one of many possible events. When this error occurs, it means that a TVC received an event that it did not expect while in this state.
Recommended Action The system can continue but may lose the TVC that generated this error. Copy the message exactly as it appears and report it to your technical service representative.
Explanation This message appears when a loop is discovered in the network.
Recommended Action Check the configuration and network path for the relevant prefix.
Explanation ATM TAG Control received a malformed PIE from TDP.
Recommended Action This does not affect system operation. However if this message recurs, report it to your technical service representative.
Explanation Tag switching is not enabled on the specified interface. Tag VCI requests and advertising will be rejected. As a side effect, the VCI requests at the upstream device can remain in the BindWait state until tag switching is re-enabled on this interface.
Recommended Action Enable tag switching.
Explanation An attempt to request or to create a binding failed while the ATM tag-control system was not initialized. Probable causes are misconfiguration or low memory.
Recommended Action Reduce other system activity if possible, and call your technical service representative for assistance.
Explanation An internal inconsistency was detected when an attempt was made to remove an item from a list not on the list.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation An internal inconsistency was detected when an attempt was made to add an item to a list already on the list.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation An attempt to create the ATM tag control process failed. The probable cause is insufficient memory.
Recommended Action Reduce other system activity if possible, and call your technical service representative for assistance.
Explanation The system ran out of VC resources for the specified interface. Tagged virtual circuits (TVCs) for some destination prefixes will not be established, possibly resulting in degraded network performance.
Recommended Action Ensure that the negotiated VPI range is sufficient to permit usage of the maximum number of TVCs available on the hardware. If the negotiated VPI range is sufficient, then reconfigure the network so that fewer TVCs are required on this interface.
Explanation This message appears when a loop is discovered in the network.
Recommended Action Check the configuration and network path for the relevant prefix.
Explanation An unexpected bind is received for a prefix. This message appears only when a memory resource allocation failure prevents this peer from informing the neighbor to release the bind. The system will continue but the downstream neighbor could be holding a binding for which there is no matching VCI at this end.
Recommended Action Reduce other system activity if possible, and call your technical service representative for assistance.
Explanation The system ran out of resources to setup a switch cross-connect for the specified interfaces. Tagged virtual circuits (TVCs) for some destination prefixes will not be established, possibly resulting in degraded network performance.
Recommended Action Ensure that the negotiated VPI range is sufficient to permit usage of the maximum number of TVCs available on the hardware. If the negotiated VPI range is sufficient, reconfigure the network so that fewer TVCs are required on this interface.
Transmission Control Protocol error messages
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Explanation The system received a TCP packet with an invalid MD5 authentication digest on a connection endpoint. The message ends with the string (RST) if the incoming packet was a TCP reset packet.
Recommended Action Determine why the source of the packet is not generating correct digests on the connection. This could be because of either misconfiguration or security weaknesses.
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Explanation An internal software error occurred
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Explanation TCP received a packet from a user application after the connection was already half-closed.
Recommended Action Determine which TCP application is still sending after the connection was half-closed.
Explanation The TCP Intercept code has changed state.
Recommended Action This message is for informational purposes, but it may indicate a security problem.
Explanation An invalid TCB is used.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Explanation An invalid TCP ENCAPS was used.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Explanation The TCP Intercept code was searching its database for information for a particular connection, but this information was not found.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the message exactly as it appears and contact your technical support.
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Time-division multiplexing error messages
Explanation The TDM cross-connect that was requested was not possible. This is probably because one of the devices either does not exist or is not properly configured for TDM.
Recommended Action Check the command for errors and the ports for correct configuration before trying again. Note that the type argument of the tdm-group command only applies if the mode cas command is enabled. If configuring a cross-connect pass-through from UIO serial port 0 or 1 to a controller, the encapsulation clear-channel command must be configured on the serial port.
Explanation The specified board returned an ID that was not recognized by the operating system. This could be caused by a hardware failure reporting an incorrect ID or because this software predates the hardware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The specified TDM port failed to be initialized. This error is possibly caused by a 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 The specified TDM port on the system motherboard failed to be initialized. This is possibly caused by a 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.
Tag Distribution Protocol (TDP) error messages
Explanation The tag-switching advertise-tags configuration command has no effect for tag-controlled ATM interfaces. The rationale for this behavior is:
Recommended Action No action is required.
Explanation The tag-switching advertise-tags configuration command has no effect for tag-controlled ATM interfaces. The rationale for this behavior is:
Recommended Action No action is required.
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an address with a bad length was received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the remainder of the PIE beyond the bad item. The partially processed PIE may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing a metric with a bad length was received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the remainder of the PIE beyond the bad item. The partially processed PIE may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an unknown metric list type or one that is unexpected for the situation was received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Explanation An unknown Tag Distribution Protocol (TDP) protocol information element (PIE) type has been received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing a destination prefix with a bad length has been received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the remainder of the PIE beyond the bad item. The partially processed PIE may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Explanation An action attempted by the Tag Distribution Protocol (TDP) encountered an unexpected condition.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation An action attempted by the Tag Distribution Protocol (TDP) implementation failed.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation The Tag Distribution Protocol (TDP) requires that each chassis have a TDP identifier. An attempt to set the TDP identifier for the chassis failed.
Recommended Action This is an informational message. As long as it needs to set its chassis TDP identifier the system will periodically attempt to do so until it succeeds. If this message recurs, copy it exactly as it appears and report it to your technical service representative.
Explanation This is an informational message generated by the Tag Distribution Protocol (TDP) implementation.
Recommended Action No action is required.
Explanation An attempt to allocate a buffer for Tag Distribution Protocol (TDP) Keep Alive protocol information element (PIE) has failed.
Recommended Action The system will continue by omitting transmission of the TDP Keep Alive PIE. This may result in termination of one or more TDP sessions as the peers time out the sessions. If this message persists, reduce other system activity if possible, and call your technical service representative for assistance.
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) that is malformed was received from a TDP peer.
Recommended Action This is an informational message. The system will recover from this situation by terminating the TDP session and attempting to establish a new session with the peer. If this message recurs, copy it exactly as it appears and report it to your technical service representative.
Explanation A violation of the TDP protocol by a TDP peer was detected.
Recommended Action This is an informational message. The system will recover from this situation by terminating the TDP session and attempting to establish a new session with the peer. If this message recurs, copy it exactly as it appears and report it to your technical service representative.
Explanation An error occurred while attempting to read a TDP PDU received from a peer.
Recommended Action This is an informational message. The system will recover from this situation by terminating the TDP session and attempting to establish a new session with the peer. If this message recurs, copy it exactly as it appears and report it to your technical service representative.
Explanation An operation on the state machine for a TDP peer failed.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation The VPI range exchanged between the Tag Distribution Protocol (TDP) peers is non-overlapping.
Recommended Action The system will not be able to create a TDP session between the affected TDP peers. Reissue the tag-switching vpi command on the appropriate interface with the correct VPI range.
Explanation An attempt to allocate a buffer for Tag Distribution Protocol (TDP) TAGATM VPI/VCI ranges failed.
Recommended Action The system will not be able to create a TDP session between the affected TDP peers. If this message persists, reduce other system activity if possible, and call your technical service representative for assistance.
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an address list type that is unexpected for the situation has been received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing a binding list type that is unexpected for the situation has been received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) that is unexpected for the situation was received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an unknown address list type was received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an unknown binding list type has been received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Traffic engineering loop prevention error messages
Explanation An unexpected failure occurred while building a TDP protocol information element (PIE) for transmission to a TDP peer. It occurred during an attempt to add a metric to the PIE.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation An action attempted by the traffic engineering loop prevention implementation encountered an unexpected condition
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Explanation The loop prevention database failed to initialize itself. The probable cause is insufficient memory.
Recommended Action Reduce other system activity if possible. If this message persists, call your technical support representative for assistance.
Explanation The loop prevention control process failed to initialize itself. The probable cause is insufficient memory.
Recommended Action Reduce other system activity if possible. If this message persists, call your technical support representative for assistance.
Explanation An operation on the traffic engineering metric database failed.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Tag Forwarding Information Base error messages
Explanation An unexpected operation on a Tag Forwarding Information Base (TFIB) entry for a recursive route occurred, or an adjacency has an invalid mac rewrite string.
Recommended Action The system proceeds by creating an untagged entry in the TFIB. This will cause tagged packets for this destination being dropped or stripped of their tag. Copy the message exactly as it appears and report it to your technical service representative.
Explanation A temporary difference occurred between the CEF database and the Tag Forwarding Information Base (TFIB). This difference will be resolved later.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation An invalid tag was seen while performing an operation on the Tag Forwarding Information Base (TFIB)
Recommended Action This is an informational message. The system proceeds by omitting the tag operation. This may result in impaired or faulty behavior for tagged packets for this destination. Copy the message exactly as it appears and report it to your technical service representative.
Explanation An operation on the Tag Forwarding Information Base (TFIB) that requires memory failed because of insufficient free memory.
Recommended Action Reduce other system activity if possible. If this message persists, call your technical service representative for assistance.
Explanation An unexpected operation on the Tag Forwarding Information Base (TFIB) occurred.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation An unexpected operation on the Tag Forwarding Information Base (TFIB) occurred.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation An unexpected operation on the Tag Forwarding Information Base (TFIB) occurred.
Recommended Action This is an informational message. The system proceeds by omitting the tag operation. This may result in impaired or faulty behavior for tagged packets for this destination. Copy the message exactly as it appears and report it to your technical service representative.
Explanation An unexpected operation on the Tag Forwarding Information Base (TFIB) occurred.
Recommended Action This is an informational message. The system proceeds by omitting the tag operation. This may result in impaired or faulty behavior for tagged packets for this destination. Copy the message exactly as it appears and report it to your technical service representative.
Explanation An unexpected operation on the Tag Forwarding Information Base (TFIB) occurred.
Recommended Action This is an informational message. The system proceeds by omitting the tag operation. This may result in impaired or faulty behavior for tagged packets for this destination. Copy the message exactly as it appears and report it to your technical service representative.
Explanation A temporary difference occurred between the CEF database and the Tag Forwarding Information Base (TFIB). This difference will be resolved later.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Explanation An unexpected operation on the Tag Forwarding Information Base (TFIB) occurred.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
PCI/TI1570-based ATM port adapter error messages
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 An internal hardware or software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The ATM port adapter failed to complete hardware initialization.
Recommended Action Reset the adapter. This should not be a recurring condition. 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 ATM-PCI port adapter software driver found fewer devices than it was configured to expect. This could mean that the missing device(s) failed to start and may have failed.
Recommended Action Try shutting off the power, reseating the card, and rebooting. 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 error message probably indicates a hardware failure in the ATM-PCI port adapter.
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 ATM virtual circuit could not be shut down for the reason shown in the error message. This probably indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The ATM-PCI port adapter driver received and handled a framer interrupt.
Recommended Action This is an informational message only. No action is required.
Explanation The ATM port adapter failed to complete hardware initialization.
Recommended Action Reset the adapter. This should not be a recurring condition. 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 ATM port adapter failed to complete hardware initialization. Details of the failure are shown in the error message.
Recommended Action Reset the adapter. This should not be a recurring condition. 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 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 An internal hardware or software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation The system experienced memory exhaustion in the PCI/packet memory. This was probably caused by heavy traffic congestion but could also be a software error.
Recommended Action Review the configuration for performance bottlenecks. 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 Memory exhaustion has occurred in the ATM-PCI port adapter driver.
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 ATM-PCI port adapter driver could not recognize the interface chips.
Recommended Action Power down, 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 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 is 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 The ATM-PCI port adapter driver found incorrect device IDs on the specified card. This could indicate either a hardware failure or that the software must be upgraded to recognize newer hardware.
Recommended Action Power down, reseat the interface card, and reboot. Or investigate if newer software is needed for your hardware. 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 ATM-PCI port adapter driver experienced an internal error, probably caused by software but possibly a hardware failure.
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 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. A small number of freezes might not be a cause for concern.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Explanation This error message probably indicates a hardware failure on the ATM-PCI port adapter.
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 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 This message indicates the PCI-ATM interface had to stop the transmitter while waiting for data. A small number of freezes might not be a cause for concern.
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.
|
|