Feedback
Table Of Contents
Message and Recovery Procedures
NETWORK_PORT_SATELLITE Messages
Message and Recovery Procedures
This chapter describes the switch system messages in alphabetical order by facility. Within each facility, the messages are listed by severity levels 0 to 7: 0 is the highest severity level, and 7 is the lowest severity level. Each message is followed by an explanation and a recommended action.
Note
The messages listed in this chapter do not include the date/time stamp designation that displays only if the software is configured for system log messaging.
CMP Messages
This section contains the Cluster Membership Protocol (CMP) messages.
Error Message CMP-5-ADD: The Device is added to the cluster (Cluster Name:[chars], CMDR IP Address [inet]).Explanation This message means the device is added to the cluster. [chars] is the cluster name; [inet] is the Internet address of the command switch.
Recommended Action No action is required.
Error Message CMP-5-MEMBER_CONFIG_UPDATE: Received member configuration from member [dec].Explanation This message means that the active or standby command switch received a member configuration; [dec] is the number of the sender.
Recommended Action No action is required.
Error Message CMP-5-MGMT_VLAN_CHNG: The management vlan has been changed to [dec].Explanation This message means that the management VLAN has changed. [dec] is the new management VLAN number.
Recommended Action No action is required.
Error Message CMP-5-REMOVE: The Device is removed from the cluster (Cluster Name:[chars]).Explanation This message means that the device is removed from the cluster; [chars] is the cluster name.
Recommended Action No action is required.
CPU_NET Messages
This section contains the CPU network interface messages.
Error Message CPU_NET-0-QUEUE_STUCK: The interface between the CPU and the switch has become stuck. The switch must now reset to clear this condition. Retrieval queue [dec].Explanation This message means that the CPU can no longer communicate with the network. The CPU has multiple packet receive queues; [dec] is the receive queue number.
Recommended Action Reload the system by using the reload privileged EXEC command.
DTP Messages
This section contains the Dynamic Trunking Protocol (DTP) messages.
Error Message DTP-4-MEM_UNAVAIL: Memory not available to perform the trunk negotiation action.Explanation This message means that the system is unable to negotiate trunks because of a lack of memory.
Recommended Action Reduce other system activity to ease the memory demands.
Error Message DTP-4-TMRERR: An internal timer error occurred when trunking on interface [chars].Explanation This message means that a timer used by the trunking protocol unexpectedly expired. [chars] is the trunked interface.
Recommended Action This error is internally corrected, and no long-term ramifications exist. However, if more problems with trunking occur, reload the switch by using the reload privileged EXEC command.
Error Message DTP-4-UNKN_ERR: An unknown operational error occurred.Explanation This message means that the system is unable to negotiate trunks because an internal operation generated an unexpected error.
Recommended Action Reload the switch by using the reload privileged EXEC command.
Error Message DTP-5-ILGLCFG: Illegal config (on, isl--on, dot1q) on [chars].Explanation This message means that one end of the trunk is configured as ON, ISL, and the other end is configured as ON, 802.1Q. [chars] is the interface.
Recommended Action This configuration is illegal and will not establish a trunk between two switches. You must change the encapsulation type so that both ends of the trunk match.
Error Message DTP-5-NONTRUNKPORTON: Port [chars] has become non-trunk.Explanation This message means that the interface changed from trunk to access. [chars] is the interface that changed.
Recommended Action This message is provided for information only.
Error Message DTP-5-TRUNKPORTCHG: Port [chars] has changed from [chars] trunk to [chars] trunk.Explanation This message means that the encapsulation type of the trunk has changed. The first [chars] is the interface, the second [chars] is the original encapsulation type, and the third [chars] is the new encapsulation type.
Recommended Action This message is provided for information only.
Error Message DTP-5-TRUNKPORTON: Port [chars] has become [chars] trunk.Explanation This message means that the interface changed from an access to a trunk. The first [chars] is the interface, and the second [chars] is the encapsulation.
Recommended Action This message is provided for information only.
EC Messages
This section contains the EtherChannel and Port Aggregation Protocol (PAgP) messages.
Error Message EC-4-NOMEM: Not enough memory available for [chars].Explanation This message means that the PAgP Shim/EtherChannel could not obtain the memory it needed to initialize the required data structures. [chars] is the EtherChannel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message EC-5-BUNDLE: Interface [chars] joined port-channel [dec].Explanation This message means that the listed interface joined the specified EtherChannel. [chars] is the physical interface, which can be a switch port a routed port. [dec] is the EtherChannel number.
Recommended Action No action is required.
Error Message EC-5-CANNOT_BUNDLE1: Port-channel [chars] is admin-down, port [chars] will remain stand-alone.Explanation This message means that the EtherChannel is administratively shut down. The first [chars] is the EtherChannel number, and the second [chars] is the physical interface, which can be a switch port or a routed port.
Recommended Action Enable the EtherChannel by using the no shutdown interface configuration command.
Error Message EC-5-CANNOT_BUNDLE2: [chars] is not compatible with [chars] and will be suspended.Explanation This message means that the interface has different interface attributes than other ports in the EtherChannel. For the interface to join the bundle (EtherChannel), change the interface attributes to match the EtherChannel attributes. The first [chars] is the EtherChannel, and the second [chars] is the physical interface, which is a switch port or a routed port.
Recommended Action Change the interface attributes to match the EtherChannel attributes.
Error Message EC-5-L3DONTBNDL1: [chars] suspended: PAgP not enabled on the remote port.Explanation This message means that PAgP is enabled on the Layer 3 interface, but the partner port is not enabled for PAgP. In this mode, the port is placed in a suspended state. [chars] is the Layer 3 interface.
Recommended Action Enable PAgP on the remote side by using the channel-group interface configuration command.
Error Message EC-5-L3DONTBNDL2: [chars] suspended: incompatible partner port with [chars].Explanation This message means that an interface cannot join an EtherChannel group because the local group capability and the partner group capability must be the same as that of the interfaces in the group. In this case, the ports in the partner's bundle (EtherChannel) do not all have the same group capability. [chars] is the physical interface, which can be a switch port a routed port.
Recommended Action Ensure that the partner group capability is the same for all the ports in the group.
Error Message EC-5-L3PORTDOWN: Shutting down [chars] as its port-channel is admin-down.Explanation This message means that the Layer 3 port administrative state is ruled by the administrative state of its EtherChannel. If the EtherChannel administrative state is down, the port administrative state is also forced to be down. [chars] is the Layer 3 interface.
Recommended Action Enable the aggregate port administrative-state by entering the no shutdown interface configuration command on the aggregation interface.
Error Message EC-5-L3STAYDOWN: [chars] will remain down as its port-channel [chars] is admin-down.Explanation This message means that on Layer 3 interfaces and aggregation interfaces, the administrative state of the aggregation interface overrides the administrative status of the Layer 3 interface. If the aggregation interface is administratively down, all interfaces in the aggregation interface are forced to be down. [chars] is the Layer 3 interface.
Recommended Action Enter the no shutdown interface configuration command on the aggregation interface.
Error Message EC-5-NOPAGP: Invalid EC mode, PAgP not enabled.Explanation This message means that PAgP is not included in the IOS image and that the EtherChannel mode cannot be set to desirable or auto.
Recommended Action Obtain an image with PAgP included, or set the mode to on by using the channel-group channel-group-number mode on interface configuration command.
Error Message EC-5-UNBUNDLE: Interface [chars] left the port-channel [dec].Explanation This message means that the listed interface left the specified EtherChannel. [chars] is the physical interface, which can be a switch port a routed port. [dec] is the EtherChannel.
Recommended Action No action is required.
Error Message EC-5-UNSUITABLE: [chars] will not join any port-channel; unsuitable attributes configured.Explanation This message means that one of the interfaces cannot join the EtherChannel because it is configured for PortFast, VLAN Membership Policy Server (VMPS), or as a Switch Port Analyzer (SPAN) destination port. All of these are unsuitable configurations for EtherChannels. [chars] is the interface name.
Recommended Action Reconfigure the port; remove the unsuitable configuration.
ETHCNTR Messages
This section contains the Ethernet controller messages. These messages are a result of a failure of the switch software when trying to program the hardware. Most of these errors lead to incorrect switch behavior, and you should call your Cisco technical support representative.
Error Message ETHCNTR-3-HALF_DUX_COLISION_EXCEED_THRESHOLD: Collision at [chars] exceed threshold. Consider as loop-back.Explanation This message means that the collision at a half-duplex port exceeded the threshold, and the port is considered to be in the loop-back state. [chars] is the port.
Recommended Action No action is required.
Error Message ETHCNTR-3-INTERNAL_ERROR: Internal Error [chars].Explanation This message means that an internal error occurred when the software was trying to program the hardware. As a result, the switch is in an inconsistent state and might not provide the expected functions. [chars] describes the internal operation that failed.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message ETHCNTR-3-INVALIDMAP: Invalid map [dec] for address [enet].Explanation This message means that an attempt to bridge a packet in software obtained an invalid result. [dec] is the map number, and [enet] is the Ethernet address.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message ETHCNTR-3-LOOP_BACK_DETECTED:, Loop-back detected on [chars]. The port is forced to linkdown.Explanation This message means that the loop-back condition might be caused by a balun cable being accidentally plugged into the port. [chars] is the port.
Recommended Action Check the cables. If a balun cable is connected and the loopback condition is desired, no action is required. Otherwise, connect the correct cable, and bring the port up by entering the no shutdown interface configuration command.
Error Message ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access [chars] request ([hex]) from satellite [dec].Explanation This message means that a request to read or write the satellite RAM produced an unexpected reply. [chars] is the request type (read or write), [hex] is the address, and [dec] is the satellite number.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message ETHCNTR-3-UNEXPECTED_EVENT: Request [hex] encountered event [dec] in state [dec].Explanation This message means that an unexpected event occurred during a RAM-access request.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message ETHCNTR-4-INVALID_REPLY: Ethernet Controller: [dec] invalid [chars] response received [chars].Explanation This message means that an invalid response was received while accessing the Ethernet controller RAM.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message ETHCNTR-7-RAM_ACCESS_CMD_GROWING: Ethernet Controller: Growing RAM Access [chars] Command.Explanation This message means that the command buffer for the RAM access is growing dynamically because the original buffer was not big enough.
Recommended Action No action is required.
FM Messages
This section contains the feature manager messages. The feature manager software module manages access control lists (ACLs). Most messages in this section are the result of a switch memory shortage, which includes hardware memory such as the ternary content addressable memory (TCAM) and label space versus CPU memory. Both kinds of memory shortages are described.
Error Message FM-1-INIT: Feature Manager subsystem initialization failure.Explanation This message means that the feature manager subsystem failed to initialize. The most likely cause is insufficient memory at initialization. Either the hardware has failed, or the wrong IOS image is installed.
Recommended Action Replace the failing hardware, or obtain the correct IOS image for this platform.
Error Message FM-2-NOMAP: Cannot create Feature Manager data structures for VLAN Map [chars].Explanation This message means that the feature manager could not allocate the data structures needed to describe a VLAN map in a form that can be loaded into hardware. This error is probably caused by a lack of free memory. [chars] is the VLAN map name.
Recommended Action Reduce other system activity to ease the CPU demands.
Error Message FM-2-NOSB: Cannot create subblock for interface [chars].Explanation This message means that the feature manager was unable to save per-interface information needed for its correct operation. Some per-interface features, such as access groups or VLAN maps, will not be correctly configured. [chars] is the interface name.
Recommended Action Use a less complicated configuration that requires less CPU memory.
Error Message FM-2-NOVLB: Cannot create memory block for VLAN [dec].Explanation This message means that the feature manager was unable to save per-VLAN information needed for its correct operation. Some per-interface features, such as access groups or VLAN maps, will not be correctly configured. [dec] is the VLAN number.
Recommended Action Use a less complicated configuration that requires less CPU memory.
Error Message FM-2-NOVMR: Cannot create VMR data structures for access list [chars].Explanation This message means that the feature manager could not allocate the data structures needed to describe an ACL in a form that can be loaded into hardware. This error is probably caused by a lack of available CPU DRAM. [chars] is the access-list name.
Recommended Action Use a less complicated configuration that requires less memory.
Error Message FM-3-AUGMENTFAIL: Augmenting of access-map [chars] on [chars] label [dec] failed.Explanation This message means that the system ran out of CPU memory when attempting to merge internally required elements with the configured access maps. The first [chars] is the access-map name, and the second [chars] is the direction in which the map was applied (input or output). [dec] is the label number.
Recommended Action Reduce other system activity to ease the memory demands.
Error Message FM-3-GOTLABEL: Got label for [chars].Explanation This message means that the feature manager is able to allocate a hardware label for the interface. The interface needed a label before, but no label was available. [chars] is the label.
Recommended Action No action is required. (This message pairs with the FM-3-NOLABEL message and means that the previous error condition has rectified itself.)
Error Message FM-3-GOTVLABEL: Got label for VLAN [dec].Explanation This message means that the feature manager is able to allocate a hardware label for the VLAN. The VLAN needed a label before, but no label was available. [dec] is the VLAN number.
Recommended Action No action is required. (This message pairs with the FM-3-NOLABELVL message and means that the previous error condition has rectified itself.)
Error Message FM-3-INITLABEL: Special initialization of label [dec] failed.Explanation This message means that the initialization of the access list hardware failed. Prioritization of routing protocol packets above other kinds of packets might not occur on some VLANs or routed ports.
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 FM-3-INSERTFAIL: Insert of access-map [chars] [dec] into [chars] label [dec] failed.Explanation This message means that the system ran out of CPU DRAM when trying to merge sections of an access map. The first [chars] is the map name, and the second [chars] is the direction in which the map was applied. The first [dec] is the entry number, and the second [dec] is the label number.
Recommended Action Reduce other system activity to ease the memory demands. For example, remove any ACLs that have been defined but are not now used. Use simpler ACLs with fewer access control entries (ACEs). Use fewer VLANs, and remove any unneeded VLANs from the VLAN database.
Error Message FM-3-MERGEFAIL: [chars] ACL merge error [dec] on label [dec].Explanation This message means that the feature manager was unable to complete the merge of the configured features into a form suitable for loading into the hardware. Packets potentially affected by this feature are sent to the CPU for processing. The CPU processing needed to uphold the overflowed ACL severely degrades performance. [chars] is the ACL-type error (IP or MAC). The first [dec] is the error code, and the second [dec] is the label number.
Recommended Action Reorganize the ACLs so that all entries fit into hardware. Use less complicated and fewer ACLs.
Error Message FM-3-NOLABEL: Cannot allocate [chars] label for interface [chars].Explanation This message means that the feature manager was unable to allocate a label for the features on this interface. This means that the hardware cannot be programmed to implement the features, and packets for this interface will be filtered in software. There is a limit of 256 labels per direction. The first [chars] is the direction (input or output); the second [chars] is the interface name.
Recommended Action Reorganize the ACLs so that all entries fit into hardware. Use less complicated and fewer ACLs.
Error Message FM-3-NOLABELVL: Cannot allocate [chars] label for VLAN [dec].Explanation This message means that the feature manager was unable to allocate a label for the features on this VLAN. This means that the hardware cannot be programmed to implement the features, and packets on this VLAN will be filtered in software. There is a limit of 256 labels per direction. [chars] is the direction (input or output); [dec] is the VLAN number.
Recommended Action Allocate more space to the relevant section of the TCAM by using the sdm prefer global configuration command and reboot the switch, or use a simpler configuration. Use the same VLAN map on multiple VLANs, if possible.
Error Message FM-3-NULLCPU: Sending traffic on empty [chars] label [dec] to CPU.Explanation This message means that an internal software error occurred. [chars] is the direction (input or output), and [dec] is the label number.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message FM-3-RELOADED: Reloading [chars] label [dec] feature.Explanation This message means that the feature manager was able to fit more of the configured features on this label into the hardware. One or more features were previously unloaded because of a lack of space. [chars] is the direction (input or output), and [dec] is the label number.
Recommended Action No action is required.
Error Message FM-3-TOSCOST: Minimize monetary cost TOS bit unsupported in hardware, ignored.Explanation This hardware platform does not support filtering based on the type of service (TOS) and precedence; it supports filtering based on Differentiated Services Code Points (DSCPs). The DSCP field does not include the minimize monetary cost bit from the TOS field; hardware ignores this bit when checking for a match to an access control entry (ACE), which can lead to unintended filtering actions.
Recommended Action Design filters that do not test for the minimum monetary cost TOS.
Error Message FM-3-UNLOADING: Unloading [chars] label [dec] feature.Explanation This message means that the feature manager was unable to fit the complete configuration into the hardware, so some features will be applied in software. This error prevents some or all the packets in a VLAN from being forwarded in hardware and requires them to be forwarded by the CPU. Multicast packets might be dropped instead of being forwarded. [chars] is the direction (input or output), and [dec] is the label number.
Recommended Action Allocate more space to the relevant section of the TCAM by using the sdm prefer global configuration command and reboot the switch, or use a simpler configuration. Use the same access control lists on multiple interfaces, if possible.
Error Message FM-7-TRANSDEF: No augmentation function found for VMR.Explanation This message means that an internal error occurred. An access control list was not correctly interpreted. The value-mask result (VMR) is incorrect.
Recommended Action Copy the error exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
GBIC_1000BASET Messages
This section contains the 1000BASE-T GBIC module messages.
Error Message GBIC_1000BASET-6-GBIC_1000BASET_DEFAULT_CONFIG: 1000BASE-T GBIC module is detected in [chars]. Speed and duplex will be autonegotiated.Explanation This message means that a 1000BASE-T GBIC module is detected in the slot, and its speed and duplex are automatically autonegotiated. [chars] is the slot in which the GBIC is installed.
Recommended Action No action is required.
Error Message GBIC_1000BASET-6-GBIC_1000BASET_NO_CONFIG_NEGOTIATE: Configuration ignored. 1000BASE-T GBIC modules only support autonegotiation.Explanation This message means that the disabling of autonegotiation is ignored. The 1000BASE-T GBIC modules support autonegotiation.
Recommended Action No action is required.
GIGASTACK Messages
This section contains the GigaStack Gigabit Interface Converter (GBIC) module messages.
Error Message GIGASTACK-1-NO_LOOP_DETECT: The link neighbor of link [dec] of GigaStack GBIC in [chars] did not respond to the loop detection request. If loop topology is deployed, make sure all switches in the stack are running the latest software.Explanation This message means that no acknowledgement for the loop-detection request is received from one of the links on a GigaStack GBIC. Either the neighboring switch does not support the GigaStack GBIC loop-breaking algorithm, or the link between the two GigaStack GBICs is broken. Under this condition, a GigaStack loop topology is not automatically detected, and the connectivity between switches in the stack can be lost. [dec] is the link number; [chars] is the slot number.
Recommended Action If a loop topology is used with the GigaStack GBIC, ensure that the latest software is running on all switches in the stack. Check the GigaStack GBICs involved to ensure that they are functioning.
Error Message GIGASTACK-3-INIT_FAILURE: GigaStack GBIC in [chars] initialization failed.Explanation This message means that the GigaStack GBIC failed POST. [chars] is the slot number.
Recommended Action Remove the GigaStack GBIC, and re-insert it into the GBIC slot.
Error Message GIGASTACK-6-LOOP_BROKEN: Link loss is detected in the GigaStack loop. Link 2 of the GigaStack GBIC in [chars] is re-enabled.Explanation This message means that the loop formed by GigaStack GBICs is broken because of a link loss. Link 2 of the master loop breaker is re-enabled to replace the broken link. [chars] is the slot number.
Recommended Action No action is required.
Error Message GIGASTACK-6-LOOP_DETECTED: GigaStack GBIC in [chars] is selected as Master Loop Breaker. Link 2 of the GigaStack GBIC is disabled to break the loop.Explanation This message means that a loop is detected in the stack, and this GigaStack GBIC is selected as the master loop breaker. Link 2 of this GigaStack GBIC is disabled to break the loop. [chars] is the slot number.
Recommended Action No action is required.
L2TM Messages
This section contains the Layer 2 forwarding manager messages. This software module controls the part of the hardware that performs MAC address-based forwarding and learning. The forwarding table is implemented with a ternary content addressable memory (TCAM) device.
Error Message L2TM-3-ACCESS_ERR: TCAM access failed while [chars].Explanation This message means that a failure occurred while reading from or writing to the TCAM. [chars] describes the part of the TCAM and the operation that failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message L2TM-7-INTERNAL_ERR: Internal error:[chars].Explanation This message means that an internal error occurred. [chars] describes the internal operation that failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
NETWORK_PORT_SATELLITE Messages
The section contains the network port satellite messages. A network port satellite is a Cisco ASIC within the switch that provides Layer 2 and Layer 3 functionality and the interface between a Gigabit link or multiple 10/100 Ethernet links and the switch.
Error Message NETWORK_PORT_SATELLITE-6-MAC_LOCKUP: Transmit lock up is detected in [chars]. This port is administratively down.Explanation When the PHY is powered on and off, the MAC cycles from Gigabit to 100, and the port might lock up and stop sending packets. The PHY refers to the physical layer device on the switch, which sends and receives optical signals and provides framing and line integrity.
Recommended Action Shut down the port by using the shutdown interface configuration command, and bring it back up by using the no shutdown interface configuration command.
PLATFORM_CAT3550 Messages
This section contains the Catalyst 3550 low-level platform messages.
Error Message PLATFORM_CAT3550-1-CRASHED: [chars].Explanation This message means that the system is attempting to display the failure message from the previous failure. [chars] is the crash message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
PM Messages
This section contains the port manager messages. The port manager is a state machine that controls all the logical and physical interfaces. All features, such as VLANs, UDLD, and so forth, work with the port manager to provide switch functions.
Error Message PM-2-NOMEM: Not enough memory available for [chars].Explanation This message means that the port manager subsystem could not obtain the memory it needed to initialize the specified operation. [chars] is the port manager operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message PM-2-VLAN_ADD: Failed to add VLAN [dec] - [chars].Explanation This message means that the software failed to add the VLAN to the VLAN Trunk Protocol (VTP) database. [dec] is the VLAN ID; [chars] specifies the reason for the failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message PM-4-BAD_APP_ID: An invalid application id [dec] was detected.Explanation This message means that the port manager detected an invalid request. [dec] is the application ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message PM-4-BAD_APP_REQ: An invalid [chars] request by the '[chars]' application was detected.Explanation This message means that the port manager detected an invalid request. The first [chars] is the invalid request; the second [chars] is the application making the request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message PM-4-BAD_CARD_COOKIE: An invalid card cookie was detected.Explanation This message means that the port manager detected an invalid request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message PM-4-BAD_CARD_SLOT: An invalid card slot [dec] was detected.Explanation This message means that the port manager detected an invalid request. [dec] is the slot number.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message PM-4-BAD_COOKIE: [chars] was detected.Explanation This message means that the port manager detected an invalid request. [chars] is the invalid request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message PM-4-BAD_PORT_COOKIE: An invalid port cookie was detected.Explanation This message means that the port manager detected an invalid request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message PM-4-BAD_PORT_NUMBER: An invalid port number [dec] was detected.Explanation This message means that the port manager detected an invalid request. [dec] is the port number.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message PM-4-BAD_VLAN_COOKIE: An invalid vlan cookie was detected.Explanation This message means that the port manager detected an invalid request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message PM-4-BAD_VLAN_ID: An invalid vlan id [dec] was detected.Explanation This message means that the port manager detected an invalid request. [dec] is the VLAN ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message PM-4-ERR_DISABLE: [chars] error detected on [chars], putting [chars] in err-disable state.Explanation This message means that the port manager detected a misconfiguration or misbehavior and placed the interface in an error-disabled state. A recovery is attempted after the configured retry time (the default is 5 minutes). The first [chars] is the error, and the second and third [chars] are the affected interfaces.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message PM-4-ERR_RECOVER: Attempting to recover from [chars] err-disable state on [chars].Explanation This message means that the port manager is attempting to bring the interface up after taking it down to the error-disabled state. The first [chars] is the error, and the second [chars] is the affected interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message PM-4-TOO_MANY_APP: Application '[chars]' exceeded registration limit.Explanation This message means that the port manager detected an invalid request. [chars] is the application.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
QATM Messages
This section contains the quality of service (QoS) and access control list (ACL) TCAM manager messages. This software module configures the hardware to match the QoS classification and security ACL that you configure on the switch.
Error Message QATM-2-ASDATA_READ: Cannot read TCAM associated data.Explanation This message means associated data could not be read from the TCAM. This error might mean a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message QATM-2-ASDATA_WRITE: Cannot write TCAM associated data.Explanation This message means associated data could not be written to the TCAM. This error might mean a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message QATM-2-TCAM_READ: Cannot read TCAM.Explanation This message means that the TCAM could not be read from. This error might mean a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message QATM-2-TCAM_WRITE: Cannot write the TCAM.Explanation This message means that the TCAM could not be written to. This error might mean a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
QM Messages
This section contains the QoS manager messages.
Error Message QM-4-ACTION_NOT_SUPPORTED: Action is not supported in policy map [chars].Explanation This message means that an action other than the set, trust, and police policy-map class configuration commands was configured in a policy map. This is a hardware limitation. [chars] is the name of the policy map.
Recommended Action Configure only the supported actions of set, trust, and police when in policy-map class configuration mode.
Error Message QM-4-CLASS_NOT_SUPPORTED: Classification is not supported in class map [chars].Explanation This message means that an unsupported match class-map configuration command was configured in a policy map and attached to an egress interface or that more than one match command was configured. This is a hardware limitation. [chars] is the class map name.
Recommended Action Reconfigure the class map or the policy map. Use only the match ip dscp dscp-list class-map configuration command in a policy map that is attached to an egress interface. Only one match per class map is supported.
Error Message QM-4-HARDWARE_NOT_SUPPORTED: Hardware limitation has been reached for policy map [chars].Explanation The policy map configuration has exceeded the limitation of the hardware. You either configured more QoS ACL entries than the number specified in the Switch Database Management (sdm) template, or you configured more policers in a policy map (by using the police or police aggregate policy-map class configuration command) than supported. [chars] is the policy map name.
Recommended Action Reconfigure the class map or the policy map, and reduce the number of QoS ACLs or policers.
Error Message QM-4-MATCH_NOT_SUPPORTED: Match type is not supported in class map [chars].Explanation This message means that only the access-group acl-index-or-name, ip dscp dscp-list, and ip precedence ip-precedence-list match types are supported with the match class-map configuration command. [chars] is the name of the class map.
Recommended Action Reconfigure the class map; use only the match access-group, match ip dscp, and match ip precedence class-map configuration commands within the class map.
Error Message QM-4-NOT_SUPPORTED: Action [chars] is not supported for a policy map attached to output side.Explanation This message means that a set or trust policy-map class configuration command was configured in a policy map and attached to an egress interface. A warning message is logged, and the actions do not take affect. This is a hardware limitation. [chars] is either the set or trust action.
Recommended Action Do not configure a set or trust policy-map class configuration command in a policy map and attach it to an egress interface. These policy-map actions are supported only on ingress interfaces.
SPAN Messages
This section contains the Switch Port Analyzer (SPAN) messages.
Error Message SPAN-3-MEM_UNAVAIL: Memory was not available to perform the SPAN operation.Explanation This message means that the system was unable to perform a SPAN operation because of a lack of memory.
Recommended Action Reduce other system activity to ease the memory demands.
Error Message SPAN-3-UNKN_ERR: An internal error occurred during a SPAN operation.Explanation This message means that SPAN detected an error in its internal operation.
Recommended Action The error might be transient. Try the SPAN operation again. If a second attempt also fails, reload the switch by using the reload privileged EXEC command to complete the operation.
Error Message SPAN-3-UNKN_ERR_PORT: An internal error occurred when configuring SPAN on port [chars].Explanation This message means that SPAN detected an error in its internal operation; [chars] is the interface.
Recommended Action The error might be transient. Try the SPAN operation again. If a second attempt also fails, try reloading the switch by using the reload privileged EXEC command to complete the operation.
Error Message SPAN-4-DSD_ALREADY_DST: Interfaces [chars] already configured as monitor destinations in other monitor sessions.Explanation This message means that at least one interface being configured as a monitor destination is ignored because it is already configured as a monitor destination in another monitor session. All the other monitor destinations being configured are applied. [chars] is the interface.
Recommended Action Choose a SPAN destination interface that is not a SPAN destination in any other SPAN session, or remove the prior SPAN destination configuration from another session before configuring it as a SPAN destination interface for the current session.
Error Message SPAN-4-DSD_ALREADY_SRC: Interfaces [chars] already configured as monitor sources.Explanation This message means that at least one interface being configured as a monitor destination is ignored because it is already configured as a monitor source in this or in another monitor session. All the other monitor destinations being configured are applied. [chars] is the interface.
Recommended Action Choose a SPAN destination interface that is not a SPAN source in any other SPAN session, or remove the prior SPAN source configuration before configuring it as a SPAN destination interface.
Error Message SPAN-4-FTR_ALREADY_SRC: Configuring filter VLANs [chars], but there are already source VLANs configured.Explanation This message means that filter VLANs are being configured, but source VLANs have already been configured in the same monitoring session. Filter VLANs and source VLANs cannot be configured during the same monitoring session. [chars] is the VLAN ID.
Recommended Action Configure only one type of VLAN during a monitoring session. (Choose a SPAN filter VLAN that is not already a SPAN source VLAN, or remove the SPAN source VLAN configuration before configuring a SPAN filter VLAN.)
Error Message SPAN-4-RXOVFL: This platform allows a maximum of [dec] RX monitor interface(s).Explanation This message means that the number of interfaces being monitored in the receive direction exceeds the maximum number allowed on this switch. All interfaces beyond the number allowed are ignored and will not be configured. [dec] is the maximum interfaces allowed for monitoring in the receive direction.
Recommended Action Enter the show monitor privileged EXEC command to determine which interfaces were actually configured. Make the necessary configuration changes so that the configured interfaces do not exceed the allowed maximum. Be aware that the interfaces that were actually configured are a subset of the interfaces that were requested to be configured.
Error Message SPAN-4-SRC_ALREADY_DST: Interface(s) [chars] already configured as monitor destinations.Explanation This message means that at least one interface being configured as a monitor source is ignored because it is already configured as a monitor destination in this or another monitor session. All the other monitor sources being configured are applied. [chars] is the interface.
Recommended Action Choose a SPAN source interface that is not a SPAN destination in any other SPAN session, or remove the SPAN destination configuration from the interface before configuring it as a SPAN source interface.
Error Message SPAN-4-SRC_ALREADY_FTR: Configuring source VLANs [chars], but there are already filter VLANs configured.Explanation This message means that source VLANs are being configured, but filter VLANs have already been configured in the same monitoring session. Filter VLANs and source VLANs cannot be configured during the same monitoring session. [chars] is the VLAN ID.
Recommended Action Configure only one type of VLAN during a monitoring session. (Choose a SPAN source VLAN that is not already a SPAN filter VLAN, or remove the SPAN filter VLAN configuration before configuring a SPAN source VLAN.)
Error Message SPAN-4-TXOVFL: This platform allows a maximum of [dec] TX monitor interface(s).Explanation This message means that the number of interfaces being monitored in the transmit direction exceeds the maximum number allowed on this switch. All interfaces beyond the number allowed are ignored. [dec] is the maximum interfaces allowed for monitoring in the transmit direction.
Recommended Action Enter the show monitor privileged EXEC command to determine which interfaces were actually configured. Make the necessary configuration changes so that the configured interfaces do not exceed the allowed maximum. Be aware that the interfaces that were actually configured are a subset of the interfaces that were requested to be configured.
SPANTREE Messages
This section contains the spanning-tree messages:
Error Message SPANTREE-2-BLOCK-PVD-PEER: Blocking on [chars] [chars]. Inconsistent peer vlan.Explanation This message means that the spanning-tree port associated with the listed spanning-tree instance and interface will be held in the spanning-tree blocking state until the port VLAN ID (PVID) inconsistency is resolved. The listed spanning-tree instance is that of the native VLAN ID of the interface on the peer switch to which the listed interface is connected. The first [chars] is the spanning-tree instance; the second [chars] is the interface.
Recommended Action Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree automatically unblocks the interfaces as appropriate.
Error Message SPANTREE-2-BLOCK-PVID-LOCAL: Blocking [chars] on [chars] Inconsistent local vlan.Explanation This message means that the spanning-tree port associated with the listed spanning-tree instance and interface will be held in the spanning-tree blocking state until the port VLAN ID (PVID) inconsistency is resolved. The listed spanning-tree instance is that of the native VLAN ID of the listed interface. The first [chars] is the spanning-tree instance; the second [chars] is the interface.
Recommended Action Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree automatically unblocks the interfaces as appropriate.
Error Message SPANTREE-2-RECV-1Q-NON-1QTRUNK: Received 802.1Q BPDU on non 802.1Q trunk [chars] [chars].Explanation This message means that the listed interface on which a Shared Spanning Tree Protocol (SSTP) bridge protocol data unit (BPDU) was received was in trunk mode but was not using 802.1Q encapsulation. [chars] are the connected interfaces.
Recommended Action Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected are in the same mode (access or trunk). If the mode is trunk, verify that both interfaces have the same encapsulation (ISL or 802.1Q). When these parameters are consistent, spanning tree automatically unblocks the interface.
Error Message SPANTREE-2-RECV-BAD-TLV: Received SSTP BPDU with bad TLV on [chars] [chars].Explanation This message means that the listed interface received an SSTP BPDU that was missing the VLAN ID tag. The BPDU is discarded. [chars] is the interface that received the SSTP BPDU.
Recommended Action If the message recurs, copy the message exactly as 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 SPANTREE-2-RECV-PVID-ERR: Received BPDU with inconsistent peer vlan id [dec] on [chars] [chars].Explanation This message means that the listed interface received an SSTP BPDU that is tagged with a VLAN ID that does not match the VLAN ID on which the BPDU was received. This occurs when the native VLAN is not consistently configured on both ends of an 802.1Q trunk. [dec] is the VLAN ID; [chars] are the connected interfaces.
Recommended Action Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree automatically unblocks the interfaces.
Error Message SPANTREE-2-ROOTGUARD_BLOCK: Root guard blocking port [chars] on [chars].Explanation A BPDU was received on the listed interface that advertises a superior spanning-tree root bridge to that currently in use. The interface is put into blocking state and marked as root-guard inconsistent to prevent a suboptimal spanning-tree topology from forming.
Recommended Action Enter the show spanning-tree inconsistentports privileged EXEC command to review the list of interfaces with root-guard inconsistencies. Determine why devices connected to the listed ports are sending BPDUs with a superior root bridge, and take action to prevent more occurrences. Once the inaccurate BPDUs have been stopped, the interfaces automatically recover and resume normal operation. Make sure that it is appropriate to have root guard enabled on the interface.
Error Message SPANTREE-2-ROOTGUARD_CONFIG_CHANGE: Root guard [chars] on port [chars] on [chars].Explanation The spanning-tree root guard configuration for the listed interface has changed. If enabled, any BPDU received on this interface that advertises a superior spanning-tree root bridge to that already in use will cause the interface to be put into blocking state and marked as root-guard inconsistent.
Recommended Action Verify that this is the desired configuration for the listed interface. Correct it if it is not the desired configuration; otherwise, no action is required.
Error Message SPANTREE-2-ROOTGUARD_UNBLOCK: Root guard unblocking port [chars] on [chars].Explanation The listed interface is no longer receiving BPDUs advertising a superior root bridge. The root-guard inconsistency is cleared for the interface, and the blocking state is removed from the interface.
Recommended Action No action is required.
Error Message SPANTREE-2-RX-PORTFAST: Received BPDU on PortFast enabled port. Disabling [chars].Explanation This message means that a BPDU was received on the listed interface, which has the spanning-tree PortFast feature enabled. Because spanning-tree BPDU guard is also enabled, the interface is administratively shut down. [chars] is the interface that received the BPDU.
Recommended Action Verify the PortFast configuration on the interface. If the PortFast behavior is desired, verify that the interface is connected to only a host or router and not to a bridge or a switch. After resolving the conflict, re-enable the interface by entering the no shutdown interface configuration command.
Error Message SPANTREE-2-UNBLOCK-CONSIST-PORT: Unblocking [chars] on [chars]. Port consistency restored.Explanation This message means that the port VLAN ID or port type inconsistencies have been resolved and spanning tree will unblock the listed interface of the listed spanning-tree instance as appropriate. The first [chars] is the spanning-tree instance; the second [chars] is the interface.
Recommended Action No action is required.
Error Message SPANTREE-3-BAD_PORTNUM_SIZE: Rejected an attempt to set the port number field size to [dec] bits (valid range is [dec] to [dec] bits).Explanation This message means an error occurred in the platform-specific code, which caused it to request more or less bits than are possible. The spanning-tree port identifier is a 16-bit field, which is divided evenly between the port priority and port number, with each subfield being 8 bits. This allows the port number field to represent port numbers between 1 and 255. However, on systems with more than 255 ports, the size of port number portion of the port ID must be increased to support the number of ports. This is performed by the STP subsystem at system initialization because the maximum number of ports on a particular platform will not change. This error occurs because of an error in the platform-specific code, which causes it to request more or less bits than are possible.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show version privileged EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message text or from the show version command, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message SPANTREE-3-PORT_SELF_LOOPED: [chars] disabled.- received BPDU src mac [enet] same as that of interface.Explanation This message means that a BPDU was received on the listed interface with a source MAC address that matches the one assigned to the listed interface. This means that a port might be looped back to itself, possibly because of an installed diagnostic cable. The interface will be administratively shut down. [chars] is the interface that received the BPDU; [enet] is the source MAC address.
Recommended Action Check the interface configuration and any cable plugged into the interface. When the problem is resolved, re-enable the interface by entering the no shutdown interface configuration command.
Error Message SPANTREE-7-BLOCK-PORT-TYPE: Blocking [chars] on [chars]. Inconsistent port type.Explanation This message means that the listed interface is being held in the spanning-tree blocking state until the port type inconsistency is resolved. The first [chars] is the spanning-tree instance; the second [chars] is the interface.
Recommended Action Verify that the configuration and operational states of the listed interface and those of the interface to which it is connected are in the same mode (access or trunk). If the mode is trunk, verify that both interfaces have the same encapsulation (ISL or 802.1Q). When these parameters are consistent, spanning tree automatically unblocks the interface.
Error Message SPANTREE-7-RECV-1Q-NON-TRUNK: Received 802.1Q BPDU on non trunk [chars] [chars].Explanation This message means that an SSTP BPDU was received on the listed interface, which is not an operational trunking interface. [chars] are the connected interfaces.
Recommended Action Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected are in the same mode (access or trunk). If the mode is trunk, verify that both interfaces have the same encapsulation (none, ISL, or 802.1Q). When these parameters are consistent, spanning tree automatically unblocks the interface.
SPANTREE_FAST Messages
This section contains the spanning-tree fast convergence messages:
Error Message SPANTREE_FAST-7-PORT_FWD_UPLINK: [chars] [chars] moved to Forwarding (UplinkFast).Explanation This message means that the listed interface has been selected as the new path to the root switch for the listed spanning-tree instance. The first [chars] is the interface; the second [chars] is the spanning-tree instance.
Recommended Action No action is required.
SPANTREE_VLAN_SWITCH Messages
The section contains the per-VLAN spanning-tree specific-messages for the Catalyst 3550 switches.
Error Message SPANTREE_VLAN_SW-2-MAX_INSTANCE: Platform limit of [dec] STP instances exceeded. No instance created for [chars] (port [chars]).Explanation This message means that the number of currently active VLAN spanning-tree instances has reached a platform-specific limit. No additional VLAN instances will be created until the number of existing instances drops below the platform limit. [dec] is the spanning-tree instance limit. The first [chars] is the smallest VLAN number of those VLANs that are unable to have STP instances created.
Recommended Action Reduce the number of currently active spanning-tree instances by either disabling some of the currently active spanning-tree instances or deleting the VLANs associated with them. You must manually enable the spanning trees that were unable to be created because of limited instances.
SW_VLAN Messages
This section contains the VLAN manager messages. The VLAN manager receives information from the VLAN Trunk Protocol (VTP) and enables the proper VLAN membership on all interfaces through the port manager.
Error Message SW_VLAN-3-VLAN_PM_NOTIFICATION_FAILURE: VLAN Manager synchronization failure with Port Manager over [chars].Explanation This message means that the VLAN manager dropped a notification from the port manager because of a lack of ready pool space. [chars] is the type of port manager notification.
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 SW_VLAN-3-VTP_PROTOCOL_ERROR: VTP protocol code internal error:[chars].Explanation This message means that the VTP code encountered an unexpected error while processing a configuration request, a packet, or a timer expiration. [chars] is the internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message SW_VLAN-4-BAD_PM_VLAN_COOKIE_RETURNED: VLAN manager unexpectedly received a bad PM VLAN cookie from the Port Manager, VLAN indicated:[dec].Explanation This message means that the VLAN manager received an upcall and a VLAN cookie from the port manager, which translated to a bad VLAN number. [dec] is the VLAN ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message SW_VLAN-4-BAD_VLAN_CONFIGURATION_FILE: VLAN configuration file contained incorrect verification word:[hex].Explanation This message means that the VLAN configuration file read by the VLAN manager did not begin with correct value. The VLAN configuration file is invalid, and it has been rejected. [hex] is the incorrect verification value.
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 SW_VLAN-4-BAD_VLAN_CONFIGURATION_FILE_VERSION: VLAN configuration file contained unknown file version:[dec].Explanation This message means that the VLAN configuration file read by the VLAN manager contained an unrecognized file version number, which might mean an attempt to regress to an older version of the VLAN manager software. [dec] is the file version number.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message SW_VLAN-4-BAD_VLAN_TIMER_ACTIVE_VALUE: Encountered incorrect VLAN timer active value:[chars].Explanation This message means that, because of a software error, a VLAN timer was detected as active when it should have been inactive or is inactive when it should have been active. [chars] is the VLAN timer active value.
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 SW_VLAN-4-IFS_FAILURE: VLAN manager encountered file operation error: call = [chars] / code = [dec] ([chars]) / bytes transferred = [dec].Explanation This message means that the VLAN manager received an unexpected error return from an IOS file system (IFS) call while reading the VLAN database. The first [chars] is the IFS operation that failed. The first [dec] is the error code, the second [chars] is the textual interpretation of the error code, and the second [dec] is the number of bytes transferred.
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 SW_VLAN-4-NO_PM_COOKIE_RETURNED: VLAN manager unexpectedly received a null [chars] type cookie from the Port Manager, data reference:[chars].Explanation This message means that the VLAN manager queried the port manager for a reference cookie but received a NULL pointer instead. The first [chars] is the type of port manager cookie, and the second [chars] is the interface or VLAN that is the source of the problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message SW_VLAN-4-VTP_INTERNAL_ERROR: VLAN manager received an internal error [dec] from vtp function [chars]:[chars].Explanation This message means that the VLAN manager received an unexpected error code from the VTP configuration software. [dec] is the error code; the first [chars] is the VTP function, and the second [chars] is the error code description.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message SW_VLAN-4-VTP_INVALID_DATABASE_DATA: VLAN manager received bad data of type [chars]:value [dec] from vtp database function [chars].Explanation This message means that the VLAN manager received invalid data from a VTP configuration database routine. The first [chars] is the data type; [dec] is the inappropriate value that was received, and the second [chars] is the VTP database function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message SW_VLAN-4-VTP_INVALID_EVENT_DATA: VLAN manager received bad data of type [chars]:value [dec] while being called to handle a [chars] event.Explanation This message means that the VLAN manager received invalid data from the VTP configuration software. The first [chars] is the data type; [dec] is the value of that data, and the second [chars] is the VTP event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message SW_VLAN-4-VTP_USER_NOTIFICATION: VTP protocol user notification: [chars].Explanation This message means that the VTP code encountered an unusual diagnostic situation.
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 SW_VLAN-6-OLD_CONFIG_FILE_READ: Old version [dec] VLAN configuration file detected and read OK. Version [dec] files will be written in the future.Explanation This message means that the VLAN software detected an old version of the VLAN configuration file format. It interpreted the file without a problem, but it will create files using the new format in the future. The first [dec] is the old version number, and the second [dec] is the new version number.
Recommended Action No action is required.
Error Message SW_VLAN-6-VTP_MODE_CHANGE: VLAN manager changing device mode from [chars] to [chars].Explanation This message means that an automatic VTP mode device change occurred upon receipt of a VLAN configuration database message containing more than a set number of VLANs. The first [chars] is the previous mode, and the second [chars] is the current mode.
Recommended Action No action is required.
UDLD Messages
This section contains UniDirectional Link Detection (UDLD) messages.
Error Message UDLD-3-UDLD_IDB_ERROR: UDLD error handling [chars] interface:[chars].Explanation This message means that a software error occurred in UDLD processing associated with a specific interface. The first [chars] is the event, and the second [chars] is the interface number.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message UDLD-3-UDLD_INTERNAL_ERROR: UDLD internal error:[chars].Explanation This message means that a software check failed during UDLD processing. [chars] is a description of the internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message UDLD-3-UDLD_INTERNAL_IF_ERROR: UDLD internal error, interface [chars]:[chars].Explanation This message means that a software check failed during UDLD processing. [chars] are the affected interfaces.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface [chars], [chars] detected.Explanation This message means that the UDLD Protocol disabled an interface because it detected connections between neighbors that were functioning only in one direction, which might potentially cause spanning-tree loops or interfere with connectivity. The cause is likely to be hardware related, either due to a bad port, a bad cable, or a misconfigured cable. The first [chars] is the interface number, and the second [chars] is the error detected.
Recommended Action Try to correct the configuration or locate the bad cable. If you are not successful, copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message UDLD-6-UDLD_PORT_RESET: UDLD reset interface [chars].Explanation This message means that the UDLD Protocol detected a unidirectional connection between neighbors. You reset the port that was disabled by UDLD by using the udld reset privileged EXEC command or through a hardware action such as a link-state change. [chars] in the interface number.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.
