|
|
The following are microcode error messages.
Error Message
%UCODE-3-BADCHKSUM: Bad checksum in [chars], found 0x[hex] expected 0x[hex]Explanation The microcode file has become corrupted; the checksum computed after reading the file from Flash memory does not match the version in the file. The file will not be downloaded, and the onboard ROM microcode will be used instead.
Recommended Action Reload the microcode. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UCODE-3-BADHWVER: Ucode file [chars] requires [chars] version [dec].x hardwareExplanation A mismatch was detected during an attempt to load a microcode file into an interface processor. The hardware requires a different microcode version from the one specified.
Recommended Action Use the required microcode version.
Error Message
%UCODE-3-HDRCORRUPT: Ucode header corrupted in [chars], found 0x[hex] expected 0x[hex]Explanation The microcode file has become corrupted; the checksum computed after reading the file from Flash memory does not match the version in the file. The file will not be downloaded, and the onboard ROM microcode will be used instead.
Recommended Action Reload the microcode. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UCODE-3-IPCBUFFAIL: Unable to obtain IPC resourcesExplanation The interprocess communication (IPC) service used to download the microcode to the interface processors has failed to obtain a buffer. The interface processors will not load properly.
Recommended Action Reload the microcode. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UCODE-3-IPCINITFAIL: Unable to initialize IPC [chars] servicesExplanation The interprocess communication (IPC) service used to download the microcode to the interface processors has failed to initialize. The interface processors will not load properly.
Recommended Action The router must be reloaded to resolve the problem.
Error Message
%UCODE-3-IPCINVALID: Invalid IPC request ([dec]) received from ([hex])Explanation The interprocess communication (IPC) service used to download microcode to the interface processors has received an invalid message.
Recommended Action Ensure that the proper revisions of microcode are selected.
Error Message
%UCODE-3-LDFAIL: Unable to download ucode from [chars] in slot [dec], trying [chars] ucodeExplanation The microcode file specified by the configuration is not suitable for downloading, or another error has occurred. The onboard ROM microcode will be loaded so the interface can remain operational.
Recommended Action Reload the microcode. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UCODE-3-NOBUF: Unable to allocate memory for ucode bufferExplanation A buffer is required for decompression of the microcode before it is loaded into an interface processor. This buffer could not be allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UCODE-3-NOFILE: Ucode file [chars] not found, system ucode loaded in slot [dec]Explanation The microcode file specified by the configuration was not found in Flash memory. The onboard ROM microcode will be loaded so that the interface can remain operational.
Recommended Action Enter the show flash command to determine if the file is located in Flash memory. If the file is located in Flash memory, reload the microcode. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UCODE-3-NOROM: Invalid attempt to load ROM ucode in slot [dec]Explanation Some interface processors cannot load the microcode from ROM. This error is caused by an invalid configuration statement.
Recommended Action Remove the invalid configuration statement.
Error Message
%UCODE-5-OBSOLETE: FDDI unit [dec] has obsolete microcode: please upgrade itExplanation A FDDI interface processor has been found running obsolete microcode that does not support microcode CMT, which is required for all Cisco IOS software releases from 10.2 on.
Recommended Action Upgrade the microcode on the interface processor.
Error Message
%UCODE-3-RDFAIL: Unable to read ucode file [chars] from flashExplanation For some reason, the microcode file could not be read from Flash memory. The Flash memory might be locked by another process or otherwise unavailable.
Recommended Action Use the show flash command to determine whether the Flash memory is in use and issue another microcode reload command when the Flash memory is free. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UCODE-3-SRCTYPE: Invalid Ucode source type ([dec])Explanation The specified microcode source type is not supported on this platform.
Recommended Action Ensure that the proper revisions of microcode are selected.
Error Message
%UCODE-3-TOOBIG: File [chars] at length [dec] is too long for buffer (size [dec])Explanation The file is too large for the buffer. The onboard ROM microcode will be loaded.
Recommended Action If the error message recurs after the onboard ROM microcode is loaded, call your Cisco technical support representative for assistance.
Error Message
%UCODE-3-VERSIONCK: Inappropriate version [int].[int] for [chars]Explanation An attempt was made to load an inappropriate version of microcode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UCODE-3-WRONGHARD: [chars] is [chars] ucode not [chars], microcode/hardware mismatchExplanation The specified microcode file is not the correct revision for the interface processor specified in the configuration. The onboard ROM microcode will be loaded. This message indicates a configuration error.
Recommended Action Confirm the interface type and reload the microcode.
The following are UNIX error messages.
Error Message
%UNIX-1-SYSABORT: System abortedExplanation The system has aborted.
Recommended Action Record the output from the following commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
The following are utility error messages.
Error Message
%UTIL-3-RANGEINCON: internal inconsistency [dec] [hex]Explanation A fatal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UTIL-3-RANGENULLINPUT: null pointer input to range functionExplanation An attempt was made to access a range function with a null pointer. The range list creation has failed.
Recommended Action Review the error log for a corresponding memory allocation failure message. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UTIL-3-TREE: Data structure error--[chars]Explanation A software error has occurred, resulting in a data structure inconsistency.
Recommended Action Copy the error message exactly as it appears, and report it to your Cisco technical support representative. Ask for their assistance in obtaining a version of code with the error fixed.
The following are Voice over IP (VoIP) error messages.
Error Message
%VFC-3-ERROR_ANALYZE: [chars], Error analyzing the device in slot [dec].Explanation The feature card in the specified slot could not be recognized.
Recommended Action Power down, reinsert the voice feature card (VFC), 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.
Error Message
%VFC-3-ERROR_INIT_BLDR: [chars] Unable to download the Boot loader firmware, ret = 0x[hex]Explanation An error involving the initialization of the digital signal processor (DSP) with the bootloader firmware has occurred.
Recommended Action Power down, reinsert the port module, 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.
Error Message
%VFC-3-ERROR_INIT_OVERLAY: [chars] Unable to download the Application overlay firmware. Status returned 0x[hex]Explanation An error involving the initialization of the digital signal processor (DSP) with the application or overlay firmware has occurred.
Recommended Action Power down, reinsert the port module, 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.
Error Message
%VFC-1-ERROR_INTR: [chars] , Error interrupt occured type = 0x[hex].Explanation The direct memory access (DMA) engine cannot reach the protocol control information (PCI) bus to read the descriptors.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VFC-1-INCORRECT_DSP_ID: VFC in slot [dec]: Incorrect [dec] DSP-ID passed by SPI.Explanation The digital signal processor (DSP) ID provided by the SPI for download is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VFC-3-INCORRECT_ID: VFC in slot [dec]: PCI device not supported.Explanation An interface controller device did not report a correct device ID.
Recommended Action Power down, reinsert the port module, 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.
Error Message
%VFC-1-INVALID_CONFIGURATION: vfc([dec]), vfc cards has an invalid configuration.Explanation The Cisco IOS software does not recognize the configuration of the voice interface card (VIC).
Recommended Action Check the part number of the VIC to see if it is supported in the version of Cisco IOS software operational on the router, or contact your Cisco technical support representative.
Error Message
%VFC-1-NODPMEMORY: VFC ([dec]/[dec]), vfc dual-ported memory unavailable.Explanation The router or access server could not allocate dual-ported memory for the descriptors.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VFC-1-NO_DSPM: vfc([dec]), No dsp module has been found.Explanation The Cisco IOS software could not detect any digital signal processor (DSP) modules plugged into the voice interface card.
Recommended Action Check the part number on the DSP module (DSPM) card to see if it is supported in the version of Cisco IOS software that is operational on the router, or contact your Cisco technical support representative.
Error Message
%VFC-1-NO_RING_DESCRIPTORS: No more ring descriptors available on [dec] slot.Explanation The VoIP feature card (VFC) driver cannot queue messages onto the direct memory access (DMA) engine for transmit.
Recommended Action Reset the digital signal processors (DSPs) on this port module. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VFC-1-TOOBIG: [hex] packet(size [dec]) too big.Explanation An oversize packet (greater than the 256 bytes) has been received on this interface.
Recommended Action The system should recover. No action is required. If the problem recurs, it indicates an error that might be related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VFC-1-UNKNOWN_DSPM: vfc([dec]), vfc dspm daughter card has an unknown id of [hex]Explanation The software did not recognize the type of digital signal processor (DSP) module that is plugged into the voice card.
Recommended Action Check the part number on the DSP module (DSPM) card to see if it is supported in the version of Cisco IOS software operational on the router or contact your Cisco technical support representative for assistance.
The following are Banyan VINES error messages.
Error Message
%VINES-2-BADPARAM: [chars] called with [chars] parameter set to [chars]Explanation One of the Banyan VINES lookup functions was requested with an invalid argument.
Recommended Action Copy the message exactly as it appears, run a memory dump up to 128 bytes, and confirm the location specified in the error message. Contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%VINES-2-BADTIMER: RTP timer for [chars] was found disabled, and was resetExplanation An internal interface timer is not running. This condition usually occurs after an interface has been reset.
Recommended Action No action is required. The system automatically restarts the timer.
Error Message
%VINES-2-CACHEFAILED: Cannot build cache entry ([dec] bytes) for %#z on [chars]Explanation Banyan VINES fast switching has detected that a packet destined for a given address did not have proper encapsulation information or its encapsulation size was too large to fit into the cache.
Recommended Action Ensure that the VINES encapsulation and interface-specific mappings for the specified interface are configured correctly. If the configurations seem valid, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VINES-2-CACHEUNSUPP: Caching of [chars] not supported on [chars]Explanation The cache population routing for Banyan VINES fast switching was requested for an interface that does not support VINES fast switching.
Recommended Action If other encapsulation types are available on the interface, try using them. If this problem is not limited to one or two destinations (but rather occurs with all traffic using the interface), disable VINES fast switching for the interface until you have identified the real cause of the problem. If you need assistance, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VINES-2-CONSISTENCY: Error [chars]Explanation An error involving the Banyan VINES code has occurred. This error message will give additional information to identify one of two possible causes:
This problem may cause temporary slow performance to the stations that have experienced this inconsistency until complete cache entries are added. However, connectivity should not be lost, because all data traffic can still be routed through process-level switching.
Recommended Action Copy the message exactly as it appears, and report it your Cisco technical support representative. If the warning message is about IPC port number depletion, use the show vines ipc command to check how many IPC ports are currently in use by which services and determine whether the IPC connections are all legitimate. To release IPC ports, issue the clear vines ipc command. If the warning message is about VINES cache entries, provide the contents of the VINES route cache, neighbor, and routing tables immediately after the error messages appeared. If the problem persists, issue the clear vines cache command, and monitor the router if the situation improves.
Error Message
%VINES-2-CORRUPTENTRY: Detected a corrupted entry in the [chars] tableExplanation The Banyan VINES code has detected a corrupted internal table entry.
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. If possible, clear the VINES routing table or neighbor table in which the corrupted entry was observed. Clearing the routing or neighbor table will result in a temporary loss of connectivity until the table is rebuilt.
Error Message
%VINES-2-DUPADDR: Duplicate address detected on interface [chars]Explanation The router has detected that its Banyan VINES address is being used by another router.
Recommended Action To identify the other router that is using this address, manually inspect the configuration of each router. When you have identified the router that has the duplicate address, issue the vines routing [address | recompute] command on both routers or issue the enable vines routing command, specifying a unique address. If one of the routers does not support the recompute keyword, disable VINES on that router, issue the write terminal command to save the configuration to memory, reboot the router, and then enter the vines routing command with a unique VINES address on the affected routers until each router has a unique address.
Error Message
%VINES-2-ENCAPFAILED: Encapsulation failed for %#z via %#z on [chars]Explanation Banyan VINES fast switching has encountered an encapsulation failure when building a cache entry for a neighbor.
Recommended Action Examine your configuration for causes of the encapsulation failure. Look for missing map statements, interfaces that have gone down, and so on. If this error results in lost connectivity, disable VINES fast switching by issuing the no vines route-cache command. Because disabling fast switching will slow network perform, you should issue the vines route-cache command to reenable fast switching as soon as you have identified the cause of the problem. If you cannot identify the cause, contact your Cisco technical support representative. Provide the output of the show vines cache, show vines neighbor, and show vines route commands for the destination address and neighboring routers you are using. Also provide the output of the show interface and show vines interface commands for the incoming and outgoing interfaces.
Error Message
%VINES-6-FNNOTFOUND: [chars] service [chars] routine missing [chars] vectorExplanation There is an inconsistency in the static Banyan VINES data structures for handling application-layer packets.
Recommended Action Turn on VINES service level debugging for the service reported in the error message, and copy the debug traces and the error message exactly as they appear on the console or in the system log. Report them to your Cisco technical support representative.
Error Message
%VINES-2-INVALIDPATH: Bad [chars] in path for neighbor entry %zExplanation While searching the neighbor table, the code determined that a pointer that should point to a Banyan VINES path structure actually points to some other structure.
Recommended Action Copy the message exactly as it appears, and report it your Cisco technical support representative. If possible, clear the VINES neighbor table. Clearing the VINES table will result in a temporary loss of connectivity until all neighbors and routes are relearned.
Error Message
%VINES-2-INVALIDROUTE: Bad [chars] in route for server entry %ZExplanation While searching the routing table, the code determined that a pointer that should point to a Banyan VINES route structure actually points to some other structure.
Recommended Action Copy the message exactly as it appears, and report it your Cisco technical support representative. If possible, clear the VINES neighbor table. Clearing the VINES table will result in a temporary loss of connectivity until all neighbors and routes are relearned.
Error Message
%VINES-6-IPCNOROUTINE: IPC port [dec] registered without an upcall ([chars])Explanation There is an inconsistency in the active Banyan VINES data structure for handling interprocess communication (IPC) data messages. A message was received for a port that should have a listener, but the listener routine cannot be found.
Recommended Action Examine the IPC ports currently supported on the router by issuing the show vines ipc command, and verify that the reported IPC port is indeed not active. Copy the message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative along with the output of the debug vines ipc command.
Error Message
%VINES-2-NOBUFFERS: No buffers available for [chars]Explanation There were no buffers available to send a Banyan VINES service query or reply.
Recommended Action Examine the system memory and buffer capacity and compare it with current usage. If you notice a substantial discrepancy, monitor the system for possible memory leaks or buffer drainage and report the problem to your Cisco technical support representative. Provide the representative with the output gathered from the following commands:
Error Message
%VINES-2-NOVENCAP: Encapsulation failed on [chars] for address %#zExplanation The Banyan VINES code tried to send a packet on an interface that does not have a new encapsulation routine for outbound packets.
Recommended Action Toggle the interface by issuing the interface shut and no shut commands, and then issue the no vines metric and vines metric commands. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information. If possible, turn on and provide interface-specific debug traces, particularly for VINES activities.
Error Message
%VINES-6-RPCNOSERVICE: IPC port [dec] registered without a serviceExplanation There is an inconsistency in the active Banyan VINES data structure for handling Net remote-procedure call (RPC) messages. A message was received for a port that should have a service description, but that service description cannot be found.
Recommended Action Enter the show vines ipc command and determine if the reported IPC port has a registered service. Copy the message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative. If possible, provide the output of the debug vines netrpc command.
Error Message
%VINES-6-RTNNOTFOUND: [chars] service [chars] routine not found while [chars]Explanation There is an inconsistency in the active Banyan VINES service description data structures. A service handler routine cannot find the description of its own service.
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. In addition, provide the output of the show vines service and debug vines service traces commands for the service reported in the error message.
The following are Versatile Interface Processor (VIP) error messages.
Error Message
%VIP-3-AFOVERFLOW: VIP address filter table fullExplanation The Versatile Interface Processor (VIP) Ethernet interface uses an internal MAC address table to filter incoming packets. Once the table is full, additional address entries are rejected. The MAC address table is consumed by entries for various protocols, such as Protocol Independent Multicast (PIM) or Hot Standby Router Protocol (HSRP). This message indicates that an incoming packet had a destination address different from the MAC addresses that were included in a full table. Therefore, the packet will be ignored.
Recommended Action Distribute some of the HSRP entries to other Ethernet interfaces.
Error Message
%VIP-3-BADMALUCMD: Unsupported MALU command [dec], arg=[hex], pascb=[hex]Explanation The Route Processor (RP) or the Route Switch Processor (RSP) has forwarded an unsupported command that the Cisco IOS 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.
Error Message
%VIP-3-CMDNOPASCB: PASCB Null for command [dec], arg=[hex]Explanation The Route Processor (RP) or the Route Switch Processor (RSP) has forwarded an unsupported command that the Cisco IOS 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.
Error Message
%VIP-3-NODISPATCH: Dispatch vector Null, cmd=[dec], dintf=[dec]Explanation No command dispatch vector was found for the specified interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VIP-2-NOICBS: No MEMD icbs left for PA [dec] Interface [dec]Explanation No Switch Processor (SP) interrupt control block structure was associated with the port adapter or the interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VIP-3-UNDEFIDBTYPE: Undefined idb type [dec]Explanation The Versatile Interface Processor (VIP) kernel has identified a media type other than Ethernet, Token-Ring, or serial. These are the media types supported by Cisco IOS Release 11.2 on the VIP. This error might be caused by having an older version of the software running on a device with a new VIP port adapter.
Recommended Action Check whether your version of Cisco IOS software supports the VIP port adapter. If an old software version does not appear to be the problem, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Multilink PPP error messages.
Error Message
%VIPMLP-2-NOVC: [chars]: packet received for non-existent VC [dec]Explanation A virtual channel encapsulation has been corrupted.
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.
The following are MC3810 voice FSM subsystem error messages.
Error Message
%VOICE_FSM-3-ERROR: NULLExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VOICE_FSM-5-MC3810_NOTICE: NULLExplanation This message is informational only.
Recommended Action No action is required.
The following are MC310 voice resource subsystem error messages.
Error Message
%VOICE_RC-3-ERROR: NULLExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VOICE_RC-5-MC3810_NOTICE: NULLExplanation This message is informational only.
Recommended Action No action is required.
The following are Voice over IP (VoIP) call history output messages.
Error Message
%VOIPAAA-5-VOIP_CALL_HISTORY: allLegType [dec], onnectionId [hex] [hex] [hex] [hex], etupTime [chars], eerAddress %*s, eerSubAddress %*s, isconnectCause %*s, isconnectText %*s, onnectTime [chars], isconnectTime [chars], allOrigin %ld, hargedUnits %ld, nfoType %ld, ransmitPackets %ld, ransmitBytes %ld, eceivePackets %ld, eceiveBytes %ldExplanation This error message provides call history detail output that is used in simple accounting. The ASCII comma-delimited output can be stored using the syslogd command and passed on to other billing or processing software on a server.
The following are voice port adapter error messages.
Error Message
%VPA-3-INITFAIL: VPA (bay [dec]), Init Failed at [chars] - line [dec] arg [hex]Explanation The voice port adapter has 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.
Error Message
%VPA-6-NOTDMBP: No TDM backplane is supported on slot [dec].Explanation No time-division multiplexing (TDM) backplane is supported on the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VPA-6-NOTSUPPORT: Voice PA is not supported in this platform.Explanation The voice port adapter is not supported in this platform.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VPA-6-RXDFILLFAIL: VPA (bay [dec]), Data rx ring refill failed: rxd_fill_fail=[dec]Explanation The voice port adapter has not refilled the data rx ring.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VPA-6-RXVFILLFAIL: VPA (bay [dec]), Voice rx ring refill failed: rxv_fill_fail=[dec]Explanation The voice port adapter has not refilled the voice rx ring.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VPA-3-TDMFAIL: VPA-TDM, access failed at [chars] - line [dec], arg1=[dec],arg2=[dec]Explanation The voice port adapter could not access the time-division multiplexing (TDM) switch.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VPA-3-TSBUSY: VPA (bay [dec]), TDM timeslot is busy: ST=[dec]/TS=[dec]Explanation The voice port adapter has refused a cross-connect setup request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VPA-3-TSNONBUSY: VPA (bay [dec]), TDM timeslot is non busy: ST=[dec]/TS=[dec]Explanation The voice port adapter has refused a cross connect tear-down request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VPA-5-TXVFULL: VPA (bay [dec]), Voice tx ring is full: dma_done=[dec], last_dma_done=[dec]Explanation The voice tx ring of the voice port adapter is full.
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.
%VPA-3-UNEXPEVENT: VPA (bay [dec]), received an unexpected event=[hex]Explanation The voice port adapter has received an unexpected event from the firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are virtual private dial-up networking (VPDN) error messages.
Error Message
%VPDN-6-AUTHENERR: [chars] [chars] [chars] cannot authenticate for [chars] [chars] [chars][chars][chars]Explanation The NAS/LAC or HGW/LNS is unable to locate a AAA server for the purposes of authenticating the user or tunnel. This error indicates that the router was unable to establish a network connection with the designated server. This error message might contain a reason string that identifies the point of failure.
Recommended Action Check the AAA configuration on the NAS/LAC or HGW/LNS and the network connectivity to the AAA server.
Error Message
%VPDN-6-AUTHENFAIL: [chars] [chars] [chars], [chars]authentication failure [chars]for [chars] [chars] [chars][chars][chars]Explanation The NAS/LAC or HGW/LNS has failed to authenticate a user or a tunnel, or the HGW/LNS has failed authentication with the client that initiated the session. For errors that involve user or tunnel authentication failures, this error message will contain a reason string that identifies the point of failure.
Recommended Action If the HGW/LNS is failing authentication check the username configuration on the NAS/LAC or HGW/LNS and possibly even on the client. Removing the negotiation of outbound authentication (for example, by authenticating the user only in the inbound direction) is one possible solution. If AAA is applicable, check the AAA configuration on the NAS/LAC or HGW/LNS and network connectivity to the AAA server.
Error Message
%VPDN-6-AUTHORERR: [chars] [chars] [chars] cannot authorize for [chars] [chars] [chars][chars][chars]Explanation The NAS/LAC or HGW/LNS is unable to locate a AAA server for the purposes of authorizing the user or tunnel. The router was unable to establish a network connection with the designated (configured) server. This error message might contain a reason string that identifies the point of failure.
Recommended Action Check the AAA configuration on the NAS/LAC or HGW/LNS and the network connectivity to the AAA server.
Error Message
%VPDN-6-AUTHORFAIL: [chars] [chars] [chars], [chars]authorization failure for [chars] [chars] [chars][chars][chars]Explanation The NAS/LAC or HGW/LNS has failed to authorize a user or a tunnel. This error message might contain a reason string that identifies the point of failure.
Recommended Action Check authorization configuration on the NAS/LAC or HGW/LNS. If AAA is applicable, check network connectivity to the AAA servers.
Error Message
%VPDN-6-CLOSED: [chars] [chars] [chars] closed [chars] [chars] [chars][chars][chars]Explanation The remote server, typically the HGW/LNS, has closed this session. The reason for the closure is encoded in a hexadecimal format and corresponds to the particular protocol descriptions; for example, for L2F the values are documented in section 4.4.5 of the Internet Draft. A description string that describes the closure reason might also be present.
Recommended Action Check configuration on the NAS/LAC or HGW/LNS
Error Message
%VPDN-6-MAX_SESS_EXCD: [chars] [chars] [chars] has exceeded configured local session-limit and rejected [chars] [chars] [chars][chars][chars]Explanation The NAS/LAC or HGW/LNS has refused this session because the configured maximum Virtual Private Dialup Networking (VPDN) session limit has been reached.
Error Message
%VPDN-4-MIDERROR: [chars] [chars] [chars] unable to terminate user [chars][chars][chars]Explanation The HGW/LNS could not forward the Virtual Private Dialup Networking (VPDN) user because of an internal error. This error may be either resource-/ or configuration-related. The error message may contain a reason string that reports the point of failure.
Recommended Action Check the configuration on the HGW/LNS.
Error Message
%VPDN-5-NOIDB: [chars] [chars] [chars] unable to terminate user [chars]Explanation The HGW/LNS has reached the maximum number of interfaces allowed on the router and cannot create sessions for users forwarded by Virtual Private Dialup Networking (VPDN).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VPDN-4-REFUSED: Session for [chars] Refused status = [hex]Explanation The remote server has refused this session.
Recommended Action Check the configuration on the HGW/LNS.
Error Message
%VPDN-6-RESIZE: Updated [chars] MID table size to [int]Explanation The NAS/LAC or HGW/LNS has altered the size of the MID table through command line configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VPDN-6-SOFTSHUT: [chars] [chars] [chars] has turned on softshut and rejected [chars] [chars] [chars][chars][chars]Explanation The NAS/LAC or HGW/LNS can no longer accept new connections when the vpdn softshut command has been entered. This feature prevents new sessions from being established on a VPN tunnel. The existing session will continue until termination.
Recommended Action To disable the VPDN feature and return the VPN tunnel to active service, enter the no vpdn softshut command.
Error Message
%VPDN-6-TIMEOUT: [chars] [chars] [chars] disconnected [chars] [chars] [chars][chars][chars]Explanation The NAS/LAC or HGW/LNS has disconnected the user because the timer has expired. This error may be related to a PPP negotiation error or might be an absolute timeout for the session.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VPDN-5-UNREACH: [chars] [chars] [chars] is unreachableExplanation The NAS/LAC or HGW/LNS has timed out while attempting to establish a tunnel connection to a HGW/LNS or NAS/LAC. This error might be caused by network, authentication, or authorization issues.
Recommended Action Take the following steps to check for problems:
The following are Virtual Switch Interface (VSI) master error messages.
Error Message
%VSI_M-3-INCOMPATVER: None of the VSI versions ([int]-[int]) for session [dec] on [chars] can be usedExplanation The Virtual Switch Interface (VSI) master on the Tag Switch Controller (TSC) and the VSI slaves on the controlled switch must use the same version of the VSI protocol. This error reports that the slave for the indicated session on the indicated control interface does not support a VSI version that is also supported by the VSI master and all the other slaves. The session cannot be established until the VSI master and all the other slaves use the same version of the VSI protocol. This error indicates that the Cisco IOS software version running on the TSC is not compatible with the Cisco IOS software running on the controlled switch.
Recommended Action Determine which versions of Cisco IOS software are running on the TSC and the controlled switch, and upgrade the Cisco IOS software or firmware that is out of date.
Error Message
%VSI_M-2-XCONNFAIL: Cross-connect [chars]/[int]/[int] [chars] [chars]/[int]/[int] failed unexpectedlyExplanation One or more cross-connects that were previously established by the Tag Switch Controller through the Virtual Switch Interface (VSI) have failed. The Tag Virtual Circuit of which this cross-connect was a part will no longer carry traffic end-to-end. The failure may be caused by an unexpected condition on the switch that the Tag Switch Controller (TSC) controls, or it may be caused by a switch configuration error that happened while the switch was not in communication with the TSC, but before the TSC detected this lack of communication.
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 command output, call your Cisco technical support representative and provide the representative with the gathered information.
The following are Voice Telephony security parameter index (SPI) error messages.
Error Message
%VTSP-3-CAPABILITYMISMATCH: voice port [chars]: call connection id [0x[hex] 0x[hex] 0x[hex] 0x[hex]]Explanation There was a capabilities mismatch between the two call legs. Capabilities are negotiated among the call legs for CODEC, VAD, and FAX rate.
Recommended Action Ensure that the dial peer configuration is appropriate for the interface in question. Also ensure that the configuration on the interface is correct.
Error Message
%VTSP-3-DOCALLHISFAIL:Explanation The attempt to allocate or insert an active VTSP call record into the call history list has failed.
Recommended Action No action is required.
Error Message
%VTSP-3-DSPALARM: DSP ID 0x[hex]: status=0x[hex] message=0x[hex] text=[chars]Explanation The digital signal processor (DSP) has reported a fatal error. All calls on the DSP were dropped and a DSP reload was attempted.
Recommended Action Verify that the DSP has reloaded properly by attempting to place a call on the affected voice port. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VTSP-3-DSP_TIMEOUT: DSP timeout on event [dec]: DSP ID=0x[hex]: [chars]Explanation A timeout on the digital signal processor (DSP) response has occurred.
Recommended Action The DSP has been reset automatically. If the problem persists, contact your Cisco technical support representative.
Error Message
%VTSP-4-FSM_BAD_EVENT: Invalid FSM Input on channel [chars]: state=[chars] event=[dec]Explanation An internal finite-state machine error that may be associated with dropped or hung calls has occurred.
Recommended Action Contact your field service representative if this message is accompanied by dropped or hung calls.
Error Message
%VTSP-3-FSM_ERROR: [chars]Explanation An internal finite-state machine error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VTSP-3-MSGSNDFAIL: channel:[chars] DSP ID:0x[hex] Message ID:0x[hex]Explanation A message could not be sent to the digital signal processor (DSP). The call continued but may have experienced problems.
Recommended Action Verify that the DSP is still functioning properly by attempting to place a call on the affected voice port. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%VTSP-3-NOEVENT: no free event structure available from [chars] for DSP messageExplanation There were no event structures remaining in the system pools to alert the router of a voice or signalling event.
Recommended Action Check that the voice port for which the event was reported is still operational. If the voice port was not operation, clear it.
Error Message
%VTSP-3-VTSP_BLOCK: vtsp_call_block allocate failedExplanation A memory shortage has caused a call block allocation to fail.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%VTSP-3-VTSP_HAIRPINN: haipinn peer cdb not exist, cdb 0x[hex], dst_call_id [dec]Explanation A memory shortage has caused the RBTreeCreate process to fail.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
The following are Web Cache Communication Protocol (WCCP) error messages.
Error Message
%WCCP-5-CACHEFOUND: Web Cache [int] acquiredExplanation The router has acquired the specified web cache service.
Recommended Action No action is required.
Error Message
%WCCP-1-CACHELOST: Web Cache [int] lostExplanation The router has lost contact with the specified web cache service.
Recommended Action Verify the operation of the specified web cache service.
The following are X.25 error messages.
Error Message
%X25-3-ADDRESSBAD: Interface [chars], x25 address [chars] subaddress [char] is too longExplanation This message occurs when a subaddress is configured. When this subaddress is combined with the X.121 address of the interface, the total address exceeds the limit of 15 characters.
Recommended Action Reconfigure the subaddress so that this does not happen.
Error Message
%X25-3-BADCONFIG: Interface [chars], X.25 [chars], current config. retainedExplanation The X.25 configuration of the interface is not valid. The existing configuration was not changed.
Recommended Action Ensure that the switched virtual circuit ranges of the interface do not overlap; for nonzero values, lic <= hic < ltc <= htc < loc <= hoc. (For more information, refer to "Configuring X.25 and LAPB" in the Wide-Area Networking Configuration Guide.) If an incoming-only range is defined, ensure that it is numerically less than the two-way range. If an outgoing-only range is defined, check that it is numerically greater than the two-way range. No virtual circuit high/low parameter is zero unless its partner low/high parameter is also zero. The default window sizes are less than the interface modulo.
Error Message
%X25-3-BADCONFIGATTEMPT: Attempt to [chars].Explanation The user has attempted an invalid configuration.
Recommended Action The error will indicate what invalid action was attempted. Check your configuration and if necessary contact a Cisco technical support representative for assistance.
Error Message
%X25-4-BADMBIT: Interface [chars], VC [dec], partial data packet has M-bit setExplanation A virtual circuit has been set up using the default maximum packet sizes, but the data terminal equipment (DTE) and data communications equipment (DCE) are not configured with the same default values. A packet was received that had the M-bit set, signifying that more data follows, but the packet did not carry the maximum number of bytes allowed. Such partial data packets must have the M-bit cleared. The resulting loss of a message boundary might cause problems for the data recipient.
Recommended Action Verify the default flow control parameters of the DTE and the DCE. If this message recurs, call your Cisco technical support representative for assistance.
Error Message
%X25-4-BADUPCALL: Interface [chars], Unexpected call ([chars]) from LLC2 DTE=[hex][hex].[hex][hex].[hex][hex].Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-3-COMPERR: Interface [chars] LCI [dec] low-level stac compression errorExplanation A stacker compression algorithm internal error or a shortage of buffer space was encountered during a compression operation. This error should never happen.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-4-DEBUG_LCI: LCI deleted at interrupt timeExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-3-ERR_SUBST_XOT_DNS_DEST: Error substituting regular expression for XOT DNS destination patternExplanation The regular expression substitute utility has failed to produce the X.25 hostname pattern to be sent to the Domain Name System (DNS) for address resolution.
Recommended Action Correct the DNS substitution pattern that was specified in the x.25 route command.
Error Message
%X25-2-ILLP4: Interface [chars], Illegal state [chars] when P4Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-3-INTIMEQ: Interface [chars], LCN [dec] already in timer queue, new time %#TaExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-3-INVCFGID: [dec] is not a valid X.25 configuration IDExplanation An invalid configuration ID has been used.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-4-LARGEPKSIZE: Interface [chars], [chars] packet sizes [dec]/[dec] too large; lower values will be negotiatedExplanation The default packet sizes or outgoing packet size facility values of the interface are too large to be carried by Link Access Procedure, Balanced (LAPB). The router will negotiate lower packet size values automatically.
Recommended Action Increase the LAPB N1 value. For example, for an X.25 maximum packet size of 1024 bytes, the modulo 8 X.25 operation will add 3 bytes of overhead, and the modulo 8 LAPB operation will add 4 bytes of overhead (the two bytes of cyclic redundancy check (CRC) are defined to be included). Therefore the LABP N1 value must be at least 8248 bytes (1031 bytes * 8 = 8248).
Error Message
%X25-3-LCIBOGUS: in x25_timer NULL lci_idb [hex]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-5-NOBUF: Interface [chars] LCI [dec] [chars]Explanation A decompression buffer was not available for an incoming compressed packet. This message is a warning only (the compressed packet was not lost). However, an X.25 packet layer RNR (wait) was generated, and packet-level transmission on the logical channel number (LCN) will not resume (RR issued) until a decompression buffer becomes available.
Recommended Action If this message occurs frequently, you may be required to modify the buffer pool. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-3-NOLCI: Interface [chars], Delete: lci [dec] not found in [chars] tableExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-3-NOTFINDBH: Can't find bfe host address [int] to deleteExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-4-PARTIALMAP: Interface [chars], [chars] encapsulation call from [chars] partially mapped to [chars]Explanation An incoming X.25 call specified a protocol that was assigned to a multiprotocol map; the virtual circuit (VC) will not be able to carry the full set of protocols specified by the map.
Recommended Action Modify the configuration of the router or the far host to match the encapsulation method used.
Error Message
%X25-5-PBPDBIT: Interface [chars] LCI [dec] PBP Compression does not support X25 D bitExplanation Compression is not enabled because D-bit support is configured for the local channel identifier (LCI).
Recommended Action Reconfigure the interface without D-bit support, or do not attempt to run with compression.
Error Message
%X25-5-PBPHOLDQ: Interface [chars] LCI [dec] X25 Hold queue needs to be at least default sizeExplanation An attempt was made to configure the X.25 hold queue to less than the minimum value of 10 packets.
Recommended Action Configure the X.25 hold queue to be 10 packets or more.
Error Message
%X25-5-PBPNOEND: Interface [chars] LCI [dec] End system not configured for X25 PBPExplanation A compression or decompression operation was attempted by a router other than an end router. Only end routers can perform compression and decompression.
Recommended Action Reconfigure the routers so that only the end routers in the network perform compression and decompression.
Error Message
%X25-3-PROFILENO: profile [chars] does not existExplanation An X.25 interface has been configured to use an X.25 profile that does not exist.
Recommended Action Create and configure the X.25 profile by entering the x25 profile {name} global command before referencing the profile.
Error Message
%X25-3-PVCBAD: Interface [chars], PVC [dec], [chars]Explanation A switched permanent virtual circuit (PVC) cannot be connected. The final [chars] text string in the message represents the state of the PVC. These text strings can also appear within the output of the show x25-vc command. For more information, refer to the show x25-vc command documentation in the Wide-Area Networking Command Reference.
Recommended Action Validate the configuration of the PVCs at both ends of the connection and reconfigure them if necessary.
Error Message
%X25-4-RANGEUNUSED: Interface [chars], [chars] VC range unused; set limits to zeroExplanation An outdated method was used to specify a virtual circuit range. (An outgoing-only or incoming-only virtual circuit range exactly overlaps the two-way virtual circuit range.)
Recommended Action To specify a virtual circuit range, use the current method and set the range limits to zero. To write the configuration to memory, enter the copy running-config startup-config command in privileged configuration mode. Using the copy running-config startup-config command will store the modified (zero) range limits.
Error Message
%X25-3-SIZEBAD: Interface [chars] LCI [dec] Decompression size errorExplanation An internal software error has occurred. The PBP header has an uncompressed packet size field. Each uncompressed packet size is checked against this field.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-3-SPURD1: Interface [chars], Spurious D1 timer wakeup on LCI [dec]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-3-SYNCBAD: Interface [chars] LCI [dec] Decompression sync error. expected [dec] got [dec]Explanation An internal software error involving the PBP header has occurred. The PBP header has an 8-bit synchronization field that is checked on each received 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.
Error Message
%X25-3-TRUNCATE_ALT_XOT_DNS_DEST: Truncating excess XOT addresses ([dec]) returned by DNSExplanation An X.25 route Domain Name System (DNS) lookup has returned more than the maximum number of permissible XOT destination addresses.
Recommended Action Review the DNS database entries used for XOT destination lookup and change the configuration so that no more than 6 XOT destination addresses exist.
Error Message
%X25-3-UNKNOWNPROT: [chars] : Unable to identify lower layer protocolExplanation The interface descriptor block (IDB) is not using X.25 and therefore cannot support the lower-level Connection-Mode Network Service (CMNS) protocol.
Recommended Action Check your hardware configuration or contact your Cisco technical support representative for assistance.
Error Message
%X25-4-VCLOSTSYNC: Interface [chars], VC [dec] TCP connection [chars]Explanation An X.25 circuit that is being tunneled over a TCP connection between routers was not cleared completely. The last [chars] text string in the message can take one of two forms. If the text string is "closed unexpectedly," the router at the remote end of the connection was rebooted, or the connection failed. If the text string is "connection corrupted," it is likely that the connection was made to a router running an older Cisco IOS software release.
Recommended Action If the text string is "closed unexpectedly," reestablish the connection after the remote router or intervening network becomes operational. If the text string is "connection corrupted," upgrade to a more recent version of the Cisco IOS software for the router at the other end of the connection .
Error Message
%X25-3-VERSIONBAD: Interface [chars] LCI [dec] Compression Version mismatch expected [hex] received [hex]Explanation An internal software error has occurred involving the PBP header. The PBP header has a mismatched version field. The version is checked on each received 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.
Error Message
%X25-3-X25DEENCINV: [chars]Explanation An X.25 service configuration is being removed.
Recommended Action If this was not a desired action, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-3-X25ENCINV: [chars]Explanation An X.25 service is being configured.
Recommended Action If this was not a desired action, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-3-X25INT: Interface [chars], X.25 internal error [chars]Explanation This is a general message covering numerous internal X.25 error conditions. The message text contains additional details that can be used to identify the problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-3-X25NOCFG: Profile is not configuredExplanation An X.25 interface has been configured to use an X.25 profile that is not configured.
Recommended Action Configure the X.25 profile by entering the x25 profile {name} global command before referencing the profile.
Error Message
%X25-3-X25NOTAVAIL: [chars] : Lower layer protocol is not availableExplanation The required lower-layer protocol is unavailable.
Recommended Action Check your configuration or contact your Cisco technical support representative for assistance.
Error Message
%X25-4-XOTHOSTWRONG: Wrong host ([int]) for XOT connection to [chars] PVC [dec]; expecting [int]Explanation This message occurs when an incoming X.25-over-TCP (XOT) connection identifies a permanent virtual circuit (PVC) that is configured for a different host IP address, and whose configuration does not permit connection to a different host.
Recommended Action If the host that is attempting the connection should be allowed, either the remote host should be configured to use a single host address (by adding the xot-source typenumber option and choosing ifc for the typenumber argument) or the local PVC should be configured to accept connections from any host (by using the xot-promiscuous option). If the host that is attempting the connection is an unauthorized one, the network administrator should take the appropriate security measures to investigate the unauthorized host.
Error Message
%X25-3-XOTINT: XOT internal error [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-3-XOTPROTOCOL: XOT protocol error from [int]: [chars]Explanation A protocol error involving an X.25-over-TCP (XOT) connection has been detected. The connected virtual circuit (VC) has been closed. A flaw may exist in the XOT implementation of the remote host.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%X25-4-XOTPVCDUPLICATE: Duplicated remote PVC data for {[chars], pvc [dec]} and {[chars], pvc [dec]}Explanation This message identifies two local X.25-over-TCP (XOT) permanent virtual circuits (PVCs) that are defined using duplicate specifications for the connecting remote XOT PVC. This message probably indicates a configuration error.
Recommended Action The network administrator should examine the specified PVCs to determine what XOT PVC configuration is required.
The following are External Call Control Telephony Service Provider error messages.
Error Message
%XCCTSP_VOICE-3-ADDINTRFFAIL: The Voice Telephony Service Provider has rejected our request to add this voice interface ([dec]:[dec])Explanation The voice software was unable to report a new signalling interface to the Voice Telephony Service Provider.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCCTSP_VOICE-3-MALLOC: No memory is available to build any internal data structure for the voice software.Explanation The voice software was unable allocate memory to build any internal data structures. The system may be out of 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCCTSP_VOICE-3-NOMEM: No memory is available to build the voice interface ([dec]:[dec])Explanation The voice software was unable allocate memory to build a voice interface data structure. The system may be out of 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCCTSP_VOICE-3-NOSDB: No signaling data block is available to build the voice interface([dec]:[dec])Explanation The voice software was unable to obtain a signalling data block from the Voice Telephony Service Provider. The system may be out of 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCCTSP_VOICE-3-NOTDMCHNL: XCCTSP failed to get a free dsp tdm channel from the DSP Resource Manager (DSPRM) to handle an incoming callExplanation The voice software was unable to obtain the time-division multiplexing (TDM) channel for a free digital signal processor (DSP) from the DSP Resource Manager. All the DSPs have been used to process calls or have been taken out of service.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCCTSP_VOICE-3-NOVOICEVDEV: Cannot find the voice data block which matches an asynchronous response for a call.Explanation An internal software error has occurred.
Recommended Action Contact your field service representative if this message is coincident with dropped calls. If this message is not coincident with dropped calls, 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCCTSP_VOICE-3-UNDEFDSX0: Undefined dsx0 interface for controller([dec])Explanation The voice software is using a dsx0 interface for the specified controller that has not been defined. An internal software error has occurred.
Recommended Action Contact your field service representative if this message is coincident with dropped calls. If this message is not coincident with dropped calls, 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCCTSP_VOICE-3-UNDEFVOICEINTRF: Invalid voice interface controller:group([dec]:[dec])Explanation The voice interface defined by the controller:group keyword is not yet defined within the voice software, but attempts have been made to use this interface. An internal software error has occurred.
Recommended Action Contact your field service representative if this message is coincident with dropped calls. If this message is not coincident with dropped calls, 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Mainframe Channel Port Adapter error messages.
Error Message
%XCPA-3-BADHWVER: bay [[dec]] pre-production hardware version detected (hw:[int].[int], [int].[int]).Explanation The Mainframe Channel Port Adapter (XCPA) hardware major version is 0, which indicates that the hardware is preproduction. Port adapters having this hardware version were provided to early field test (EFT) and beta customers. These port adapters should be upgraded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCPA-3-BOOTCFG: bay [[dec]] unable to download boot configuration information.Explanation After microcode was downloaded to the Mainframe Channel Port Adapter (XCPA), an attempt was made to copy boot information into its memory. This operation has failed. The port adapter will be deactivated.
Recommended Action To reset the port adapter, you must enter the microcode reload command. If the error recurs, record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-BOOTFAIL: bay [[dec]] [chars][chars]Explanation The Mainframe Channel Port Adapter (XCPA) did not become operational after microcode was downloaded and the CPU has been taken out of reset. The message contains the reason for this error that was reported by the port adapter. The port adapter will be deactivated.
Recommended Action To reset the channel port adapter, you must enter the microcode reload command. If the error recurs, record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-BOOTVER: bay [[dec]] incompatible microcode (boot version [int].[int] not within [int].[int] - [int].[int]).Explanation An incompatibility exists between the version of the system image and the version of the microcode.
Recommended Action To display the default and configured versions of microcode for this port adapter hardware type, enter the show microcode command. Ensure that the correct version of microcode exists in Flash memory. To load the microcode, enter the microcode reload command. If the error recurs, record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-DEACTIVATED: bay [[dec]] deactivatedExplanation The Mainframe Channel Port Adapter (XCPA) is being deactivated because it has failed to successfully complete initialization. Other messages in the log will specify the exact cause of the failure.
Recommended Action If possible, correct any errors indicated by the other messages reported in the log at the time of this message. To reset the port adapter, you must enter the microcode reload command. If the error persists, ensure that the port adapter is properly seated in the bay. If the error still recurs, record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-DMAERROR: bay [[dec]] dma error: [chars]Explanation A direct memory access (DMA) failure has occurred.
Recommended Action Reload the microcode by entering the microcode reload command. If the error persists, ensure that the Mainframe Channel Port Adapter (XCPA) is properly seated in the bay. If the error still recurs, record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-DWNLDCKSM: bay [[dec]] checksum calculated [hex], expected [hex]Explanation The calculated checksum of a section in the downloadable microcode file did not match the expected value.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCPA-3-DWNLDFAIL: bay [[dec]] download failed [chars] [chars]Explanation The microcode download has failed for the reason specified in the message. The Mainframe Channel Port Adapter (XCPA) will be deactivated.
Recommended Action To reset the port adapter, you must enter the microcode reload command. If the error recurs, record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-HWVER: bay [[dec]] incompatible microcode (hw:[int].[int], [int].[int]).Explanation An incompatibility exists between the Mainframe Channel Port Adapter (XCPA) hardware and the version of microcode that the system image attempted to load.
Recommended Action Use the show microcode command to display the default and configured versions of microcode for this port adapter hardware type. Ensure that the correct version of microcode exists in Flash. To load the microcode, use the microcode reload command.
If the error still occurs, record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-INITFAIL: bay [[dec]] initialization failed: [chars]Explanation The Mainframe Channel Port Adapter (XCPA) driver has failed to successfully initialize the hardware on the port adapter. The port adapter will be deactivated.
Recommended Action To reset the port adapter, you must enter the microcode reload command. If the error persists, verify that the port adapter is properly seated in the bay. If the error still recurs, record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-IPC: bay [[dec]] - [chars] (code=[dec])Explanation A Mainframe Channel Port Adapter (XCPA) Interprocess Communication (IPC) error has occurred. The port adapter in the specified bay is unusable.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCPA-3-NEVER: bay [[dec]] mailbox response timed out after ([int] + [int]) usecs, mbx=[hex]Explanation A mailbox command sent from the driver to the Mainframe Channel Port Adapter (XCPA) did not complete within the expected time limit. As a result of this error, the channel port adapter driver will reset the channel port adapter and reload the microcode to it.
Recommended Action If the port adapter driver does not reset the port adapter and successfully reload the microcode to it, enter the microcode reload command to reload the microcode.
If the error recurs, record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-NOTANALYZED: bay [[dec]] analyze failedExplanation The Mainframe Channel Port Adapter (XCPA) driver has failed to successfully complete the tasks necessary for the initial bringup of the port adapter. This error is usually caused by a shortage of memory. Previous messages in the log will report the exact reason for the failure. The port adapter will be deactivated.
Recommended Action To reset the port adapter, you must enter the microcode reload command. If the error persists, ensure that the port adapter is properly seated in the bay. If the error still recurs, record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-NOTLOADED: bay [[dec]] port adapter download and reset failedExplanation The microcode driver has failed to successfully complete the necessary tasks for downloading microcode to the Mainframe Channel Port Adapter (XCPA) and bringing its CPU out of reset. Previous messages in the log will indicate the exact reason for the failure. The port adapter will be deactivated.
Recommended Action To reset the port adapter, you must enter the microcode reload command. If the error persists, ensure that the port adapter is properly seated in the bay. If the error still recurs, record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-NOTOPER: bay [[dec]] not operational after [dec] usecs; status=[hex]Explanation After a microcode download, the Mainframe Channel Port Adapter (XCPA) did not send a message indicating that it was operational within the expected time limit. The port adapter will be deactivated.
Recommended Action To reactivate the port adapter and reload the microcode, you must enter the microcode reload command. If the error recurs, record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-OUTHUNG: [chars] - output stuck - [chars]Explanation A transmit queue of the Mainframe Channel Port Adapter (XCPA) contained packets that had been queued for an excessive period of time. A command requesting dump information will be sent to the port adapter and then the port adapter will be reset.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCPA-3-PORTCONN: bay [[int]] failed to establish [chars] connection ([hex])Explanation An attempt to establish the console or debugger connection with the Mainframe Channel Port Adapter (XCPA) has failed.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCPA-3-PORTIOKILL: Port IO [chars] process terminating.Explanation The unexpected termination of a port I/O process has 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCPA-3-POWEREDOFF: bay [[dec]] powered offExplanation The Mainframe Channel Port Adapter (XCPA) has been powered off. Other messages in the log will report the cause of this event.
Recommended Action If possible, correct any errors indicated by the other messages reported in the log at the time of this message. To reset the port adapter, enter the microcode reload command.
If the error persists, ensure that the port adapter is properly seated in the bay.
If the error still recurs, record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-RXQ: [chars] - consistency error - [chars] ([hex],[dec])Explanation A consistency check did not receive the specified packets that were sent by the Mainframe Channel Port Adapter (XCPA). The packets are being dropped.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCPA-3-STATUS: bay [[dec]] [chars] (code=[dec])Explanation The Mainframe Channel Port Adapter (XCPA) is reporting a condition that has effected the operational status of the card. This message contains the reason for the condition that was reported by the port adapter. The port adapter will automatically be restarted.
Recommended Action If the port adapter does not automatically restart after detecting the operation status error, enter the microcode reload command. Whether or not the port adapter can be restarted, report this status along with the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-SWITCH: Driver init failed - [chars] (bay=[dec])Explanation The channel port driver packet switch driver initialization has failed. The channel port adapter will not be usable.
Recommended Action Obtain the following information:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-UCODEHDR: bay [[dec]] skip=[hex] hdr_ver=[hex] fw_rev=[hex] req_hw_ver=[hex] hw_type=[hex]Explanation The header information in the downloadable microcode file contains incorrect information. Other messages in the log specify what information is incorrect.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCPA-3-UCODEREAD: bay [[dec]] - error reading microcode file, read=[dec], requested=[dec]Explanation An error occurred while the Mainframe Channel Port Adapter (XCPA) was reading the microcode file. The port adapter will be deactivated.
Recommended Action To reactivate the port adapter and reload the microcode, enter the microcode reload command.
If the error recurs, record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-UCODESEC: bay [[dec]] wcs=[hex] addr=[hex] len=[hex] ep=[hex] compr=[hex] sec_type=[hex] ver=[hex]Explanation The header information in a section of the downloadable microcode file contains incorrect information. Other messages in the log will identify the information that is incorrect.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCPA-3-UKNMBXCMD: bay [[dec]] unknown mailbox command: [hex] [hex] [hex] [hex]Explanation The Mainframe Channel Port Adapter (XCPA) sent a mailbox command that the driver did not expect. This error may occur if there is a version mismatch between the system image and the microcode.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCPA-3-UNEXPECTEDINT: cause=[hex], mask=[hex], addr_dec_err=[hex], bus_err=[hex], ch0_ctrl=[hex]Explanation An unexpected interrupt has 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCPA-3-VPLDVER: bay [[dec]] incompatible microcode (vpld version [int].[int] not within [int].[int] - [int].[int]).Explanation An incompatibility exists between the version of the system image and the version of the microcode.
Recommended Action Use the show microcode command to display the default and configured versions of microcode for this port adapter hardware type. Ensure that the correct version of microcode exists in Flash. Use the microcode reload command to load the microcode. If the error recurs, record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%XCPA-3-XCPADRIVERKILL: Unexpected request to terminate: XCPA driver process ([chars])Explanation An unexpected termination of the Mainframe Channel Port Adapter (XCPA) driver process has 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are extended tag ATM (XTagATM) error messages.
Error Message
%XTAGATM-3-CONSISTENCY: [chars]Explanation An action attempted by the extended tag ATM (XTagATM) interface implementation has encountered an unexpected condition
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XTAGATM-3-CONTROLVC: [chars]; could not create the control VC; reason [chars]Explanation The extended tag ATM (XTagATM) driver was unable to create the tag switching control virtual circuit (VC). This error may be the result of a configuration problem or of an unexpected condition within the XTagATM driver. A Tag Distribution Protocol (TDP) session cannot be established on this interface without the tag switching control VC.
Recommended Action To check for a configuration problem, ensure that the virtual path identifier (VPI) and virtual circuit identifier (VCI) values for the tag control VC lie within the range supported on the controlled switch interface that is associated with the XTagATM interface (by using the extended-port command in interface configuration mode). If the configuration is correct, the problem may be caused by an unexpected condition within the XTagATM driver. In this case, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XTAGATM-3-CTLVCVPI: [chars]; VPI for control VC must be 0 or within configured range on switchExplanation An incorrect virtual path identifier (VPI) value for the tag control virtual circuit (VC) has been entered. The VPI value for the tag control VC, set by entering the tag-switching atm vpi command in interface configuration mode, either must be 0 or must lie within the range of VPI values that is configured for tag switching on the controlled ATM switch. If the VPI value for the tag switching control VC is outside the appropriate range of values, the tag control VC will not be created, and the Tag Distribution Protocol (TDP) session will not be established on the extended tag ATM (XTagATM) interface.
Recommended Action Either reconfigure the VPI value for the tag switching control virtual circuit (VC) using the tag-switching atm vpi command in interface configurational mode for the Tag Switch Controller or else reconfigure the range of VPI values available for tag switching on the controlled ATM switch. Make sure that the VPI value specified for the tag control VC is either 0 or a value that is within the configured range of VPI values available for tag switching on the controlled ATM switch.
Error Message
%XTAGATM-3-DUPEXTPORT: [chars]; mapped to the same switch interface as [chars]Explanation Two extended tag ATM (XTagATM) interfaces have been associated with a single interface, creating a duplicate binding on the controlled ATM switch. The duplicate binding will cause one of the XTagATM interfaces to remain down indefinitely. If this 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.
Recommended Action To remove the duplicate binding, enter the extended-port interface configuration command on one of the XTagATM interfaces.
Error Message
%XTAGATM-4-NEWVCINRANGE: VC created on [chars] in range reserved for TSC (VPIs [int]-[int], VCIs [int]-[int])Explanation A virtual circuit (VC) whose virtual path identifier (VPI) or virtual circuit identifier (VCI) is in the range configured for use by the Tag Switch Controller (TSC) on the TSC-controlled ATM switch was just created. The TSC will be unable to create a VC with that VPI or VCI, and no data will be transmitted or received on the associated extended Tag ATM (XTagATM) tag switched controlled virtual circuit (TVC). The new VC may be on either the primary interface or a subinterface.
Recommended Action Reconfigure the new VC so that it does not fall into the range reserved for the TSC, or reconfigure the VPI/VCI range on the TSC-controlled ATM switch so that it excludes the VPI/VCI of the new VC.
Error Message
%XTAGATM-4-OLDVCINRANGE: VC exists on [chars] in range reserved for TSC (VPIs [int]-[int], VCIs [int]-[int])Explanation An existing virtual circuit (VC) has a virtual path identifier (VPI) or virtual circuit identifier (VCI) that is in the range configured for use by the Tag Switch Controller (TSC) on the TSC-controlled ATM switch. The TSC will be unable to create a VC with that VPI/VCI, and no data will be transmitted or received on the associated extended tag ATM (XTagATM) tag switched controlled virtual circuit (TVC). The existing VC may be on either the primary interface or a subinterface. This message is issued only once, even if there are multiple existing VCs in the reserved range.
Recommended Action Reconfigure the existing VCs so that they do not fall into the range reserved for the TSC, or reconfigure the VPI/VCI range on the controlled switch so that it excludes the VPI/VCIs of existing VCs.
Error Message
%XTAGATM-3-SWITCHVPI: [chars]; switch VPI range ([dec]-[dec]) outside usable range ([dec]-[dec])Explanation The virtual path identifier (VPI) range that has been configured for tag switching on the Tag Switch Controller (TSC)-controlled ATM switch does not overlap the range of VPI values that the TSC can support. This error will prevent a Tag Distribution Protocol (TDP) session from being established on this interface.
Recommended Action Reconfigure the VPI range on the controlled switch so that it overlaps the range of VPI values that the TSC can support.
Posted: Fri Jun 16 11:55:17 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.