Feedback
Table Of Contents
Message and Recovery Procedures
DHCP_SNOOPING_CAT3550 Messages
NETWORK_PORT_SATELLITE Messages
PLATFORM_CATALYST2940 Messages
PLATFORM_CATALYST2955 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.
This chapter contains these message facilities:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
ANGNP Messages
This section contains the Autonegotiation Next Page (ANGNP) message. This feature disables an interface when a loopback is detected.
Error Message ANGNP-3-LOOP_BACK_DETECTED: Loop-back detected on [chars].Explanation There is a loopback on the specified port. The cause might be a Token-Ring Type-1 cable connected to the port, or a misconfiguration in the network. [chars] is the port name.
Recommended Action Correct the problem that is causing the loopback condition. Then enter the shutdown interface configuration command, followed by the no shutdown interface configuration command to restart the port.
AUTOQOS Messages
This section contains the automatic quality of service (auto-QoS) messages.
Error Message AUTOQOS-3-FEATURE_UNINITIALIZED: Feature not initialized in the platform, [chars].
Note
Explanation The feature did not initialize and is not enabled on any interface. [chars] is the feature name, which is auto-QoS.
Recommended Action If this feature does not operate, reboot the system by using the reload privileged EXEC command. Verify that this feature is supported on your switch by checking the software configuration guide for this software release.
BOOT_HOST_DHCP Messages
This section contains the boot host for DHCP messages.
Error Message BOOT_HOST_DHCP-3-ABORTING: [chars]
Note
Explanation An error occurred during DHCP configuration; the operation stopped due to an unexpected condition. [chars] is the specific condition. This error is usually caused by connectivity problems between the device and the DHCP or TFTP server and might involve the relay agent.
Recommended Action Enter the debug dhcp privileged EXEC command to show detailed DHCP packet content. If you still cannot resolve this error, enter the show running configuration and show tech-support privileged EXEC commands and collect the data from the debug and show commands. Open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message BOOT_HOST_DHCP-4-WARNING: [chars]
Note
Explanation The switch could not configure a device using DHCP, and an unexpected condition occurred that did not cause a failure, but resulted in nonstandard performance. [chars] describes the condition.
Recommended Action No action is required.
Error Message BOOT_HOST_DHCP-6-INFO: [chars]
Note
Explanation This is an informational message generated during device configuration using DHCP. [chars] is the message text.
Recommended Action No action is required.
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]).
Note
Explanation The device is added to the cluster. [chars] is the cluster name, and [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].
Note
Explanation The active or standby command switch received a member configuration. [dec] is the member 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].
Note
Explanation The management VLAN has changed. [dec] is the new management VLAN ID.
Recommended Action No action is required.
Error Message CMP-5-NBR_UPD_SIZE_TOO_BIG: Number of neighbors in neighbor update is [int], maximum number of neighbors allowed in neighbor update is [int].
Note
Explanation The number of cluster neighbors in the clustering neighbor update packet exceeds the number of neighbors supported by the clustering module design. [int] is the number of cluster neighbors.
Recommended Action No action is required.
Error Message CMP-5-REMOVE: The Device is removed from the cluster (Cluster Name:[chars]).
Note
Explanation The device is removed from the cluster. [chars] is the cluster name.
Recommended Action No action is required.
DHCP_SNOOPING Messages
This section contains the DHCP snooping messages.
Error Message DHCP_SNOOPING-3-DHCP_SNOOPING_INTERNAL_ERROR: DHCP Snooping internal error, [chars].
Note
Explanation A software check failed in the DHCP snooping process. [chars] is the error message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message DHCP_SNOOPING-4-AGENT_OPERATION_FAILED: DHCP snooping binding transfer failed. [chars].
Note
Explanation The DHCP snooping binding transfer process failed because of the specified reason for failure. [chars] is the reason for failure.
Recommended Action No action is required.
Error Message DHCP_SNOOPING-4-AGENT_OPERATION_FAILED_N: DHCP snooping binding transfer failed ([dec]). [chars].
Note
Explanation The DHCP snooping binding transfer process failed because of the specified reason for failure [dec] is the number of failures, and [chars] is the reason for the failure. This message is rate-limited.
Recommended Action No action is required.
Error Message DHCP_SNOOPING-4-DHCP_SNOOPING_ERRDISABLE_WARNING: DHCP Snooping received [dec] DHCP packets on interface [chars].
Note
Explanation The switch detected a DHCP packet rate-limit violation on the specified interface and put the interface in the error-disabled state. [dec] is the number of DCHP packets, and [chars] is the interface.
Recommended Action No action is required.
Error Message DHCP_SNOOPING-4-DHCP_SNOOPING_PVLAN_WARNING: DHCP Snooping configuration may not take effect on secondary vlan [dec]. [chars].
Note
Explanation If private VLANs are configured, the DHCP snooping configuration on the primary VLAN automatically propagates to all the secondary VLANs. [dec] is the VLAN IDs of the secondary VLANs, and [chars] is the warning.
Recommended Action No action is required.
Error Message DHCP_SNOOPING-4-IP_SOURCE_BINDING_PVLAN_WARNING: IP source filter may not take effect on secondary vlan [dec] where IP source binding is configured. [chars].
Note
Explanation If private VLANs are configured, the IP-source-guard filter on the primary VLAN automatically propagates to all secondary VLANs. [dec] is the secondary VLAN, and [chars] is the warning.
Recommended Action No action is required.
Error Message DHCP_SNOOPING-4-IP_SOURCE_BINDING_NON_EXISTING_VLAN_WARNING: IP source binding is configured on non existing vlan [dec].
Note
Explanation The message means that an IP source binding was configured on a VLAN that has not been configured yet. [dec] is the VLAN.
Recommended Action No action is required.
Error Message DHCP_SNOOPING-4-NTP_NOT_RUNNING: NTP is not running; reloaded binding lease expiration times are incorrect.
Note
Explanation If the DHCP snooping database agent loads the DHCP snooping bindings and NTP is not running, the calculated lease duration for the bindings is incorrect.
Recommended Action Configure NTP on the switch to provide an accurate time and date for the system clock. Then disable and re-enable DHCP snooping to clear the DHCP snooping binding database.
Error Message DHCP_SNOOPING-4-QUEUE_FULL: Fail to enqueue DHCP packet into processing queue: [chars], the queue is most likely full and the packet will be dropped.
Note
Explanation The CPU is receiving DHCP packets a higher rate than the DHCP snooping process can handle. These DHCP packets are dropped to prevent a denial of service attack. [chars] is the warning.
Recommended Action No action is required.
Error Message DHCP_SNOOPING-4-STANDBY_AGENT_OPERATION_FAILED: DHCP snooping binding transfer failed on the Standby Supervisor. [chars].
Note
Explanation The DHCP snooping binding transfer process failed on a standby supervisor engine. [chars] is the standby supervisor engine.
Recommended Action No action is required.
Error Message DHCP_SNOOPING-6-AGENT_OPERATION_SUCCEEDED: DHCP snooping database [chars] succeeded.
Note
Explanation The DHCP binding transfer process succeeded. [chars] is the DCHP snooping database.
Recommended Action No action is required.
Error Message DHCP_SNOOPING-6-BINDING_COLLISION: Binding collision. [dec] bindings ignored.
Note
Explanation The specified number of bindings were ignored when the switch read the database file. The bindings from the database file have MAC address and VLAN information that a configured DHCP snooping binding already uses.
Recommended Action No action is required.
Error Message DHCP_SNOOPING-6-INTERFACE_NOT_VALID: Interface not valid. [dec] bindings ignored.
Note
Explanation The specified number of bindings were ignored when the switch read the database file because the interface in binding database is not available, the interface is a routed port, or the interface is a DHCP snooping-trusted Layer 2 interface. [dec] is the number of bindings that the switch ignores.
Recommended Action No action is required.
Error Message DHCP_SNOOPING-6-LEASE_EXPIRED: Lease Expired. [dec] bindings ignored.
Note
Explanation The specified number of bindings were ignored when the switch read the database file because the DHCP lease expired. [dec] is the number of bindings.
Recommended Action No action is required.
Error Message DHCP_SNOOPING-6-PARSE_FAILURE: Parsing failed for [dec] bindings.
Note
Explanation The specified number of bindings were ignored when the switch read the database file because the database read operation failed. [dec] is the number of bindings.
Recommended Action No action is required.
Error Message DHCP_SNOOPING-6-VLAN_NOT_SUPPORTED: Vlan not supported. [dec] bindings ignored.
Note
Explanation The specified number of bindings were ignored when the switch read the database file because VLAN is no longer configured on the switch. [dec] is the number of bindings that the switch ignores.
Recommended Action No action required.
DHCP_SNOOPING_CAT3550 Messages
This section contains the DHCP snooping messages on Catalyst 3550 switches.
Error Message DHCP_SNOOPING_CAT3550-3-MVR_INSTALL: Cannot install [chars] ACLs for DHCP Snooping, probably no TCAM space.
Note
Explanation When DHCP snooping is enabled, access control lists (ACLs) need to be installed in the ternary content addressable memory (TCAM). DHCP snooping fails if there is insufficient space in the TCAM.
Recommended Action Reduce the number of input or output port ACLs (PACLs) and VLAN maps to make space in the TCAM.
Error Message DHCP_SNOOPING_CAT3550-3-UNEXPECTED_EVENT: Process received unknown event (major [hex], minor [hex]).
Note
Explanation A process received an event it was unable to handle.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
DOT1Q_TUNNELLING Messages
This section contains the IEEE 802.1Q tunneling message on Catalyst 3550 switches. An incorrect maximum transmission unit (MTU) setting causes these messages.
Error Message DOT1Q_TUNNELLING-4-MTU_WARNING: System MTU of [dec] might be insufficient for 802.1Q tunnelling. 802.1Q tunnelling requires system MTU size of [dec] to handle maximum size ethernet frames.
Note
Explanation The switch MTU setting might not be sufficient for IEEE 802.1Q tunneling. The MTU needs to include the 4-byte overhead associated with the additional IEEE 802.1Q tag. The first [dec] is the current system MTU setting in bytes, and the second [dec] is the required MTU size in bytes.
Recommended Action Adjust the system MTU for the additional IEEE 802.1Q tag by using the system mtu global configuration command, and reload the switch by using the reload privileged EXEC command.
DOT1X Messages
This section contains the IEEE 802.1x authorization messages.
Error Message DOT1X_MOD-3-NULLPTR: Unexpected null pointer in [chars] at [dec].
Note
Explanation An internal software error occurred. [chars] is the software filename, and [dec] is the line number in the file.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message DOT1X-3-ROUTEDPORT: Received vlan id ([dec]) from RADIUS for routed port [chars].
Note
Explanation During IEEE 802.1x authorization, the RADIUS server provided a VLAN ID for a routed port.
Recommended Action Remove the VLAN ID in the RADIUS configuration, or configure the port as an access port.
Error Message DOT1X-3-VLANINVALID: Received invalid vlan ([dec]) from RADIUS for [chars].
Note
Explanation During IEEE 802.1x authorization, the RADIUS server provided a VLAN ID that is not configured on the switch.
Recommended Action Change the VLAN ID in the RADIUS configuration, or configure the VLAN on the switch.
Error Message DOT1X-3-VLANMALFORMED: Received malformed vlan from RADIUS for [chars].
Note
Explanation During IEEE 802.1x authorization, the RADIUS server provided an invalid VLAN ID.
Recommended Action Correct the VLAN ID in the RADIUS configuration.
Error Message DOT1X-3-VLANUNKNOWN: Received unknown vlan ([chars]) from RADIUS for [chars].
Note
Explanation During IEEE 802.1x authorization, the RADIUS server provided a VLAN ID that is not recognized by the switch.
Recommended Action Correct the VLAN ID in the RADIUS configuration.
Error Message DOT1X-3-VOICEVLAN: Received voice vlan ([dec]) from RADIUS for [chars].
Note
Explanation During IEEE 802.1x authorization, the RADIUS server provided a VLAN ID that conflicts with the voice VLAN ID on the port.
Recommended Action Change the VLAN ID in the RADIUS configuration, or change the voice VLAN on the switch port.
Error Message DOT1X-4-MEM_UNAVAIL: Memory was not available to perform the 802.1X action.
Note
Explanation The system memory is not sufficient to perform the IEEE 802.1x authentication.
Recommended Action Reduce other system activity to reduce memory demands.
Error Message DOT1X-4-MSG_ERR: Unknown message event received.
Note
Explanation The IEEE 802.1x process received an unknown message event.
Recommended Action Restart the IEEE 802.1x process by entering the dot1x system-auth-control global configuration command. If this message recurs, reload the device.
Error Message DOT1X-4-UNKN_ERR: An unknown operational error occurred.
Note
Explanation The IEEE 802.1x process cannot operate because of an internal system error.
Recommended Action No action is required.
Error Message DOT1X-5-ERR_CHANNELLING: Dot1x can not be enabled on Channelling ports.
Note
Explanation IEEE 802.1x could not be enabled on the channeling port. Attempting to set IEEE 802.1x port-control to auto or force-unauthorized (force_unauth) mode on a channeling port, which is not allowed, causes this condition.
Recommended Action Disable channeling on the interface, and then enable IEEE 802.1x.
Error Message DOT1X-5-ERR_DYNAMIC: Dot1x can not be enabled on Dynamic ports.
Note
Explanation IEEE 802.1x could not be enabled on the dynamic mode port. Attempting to set IEEE 802.1x port-control to auto or force-unauthorized (force_unauth) mode on a dynamic mode port, which is not allowed, causes this condition.
Recommended Action Disable dynamic mode on the interface, and then enable IEEE 802.1x.
Error Message DOT1X-5-ERR_DYNAMIC_VLAN: Dot1x can not be enabled on Dynamic VLAN ports.
Note
Explanation IEEE 802.1x could not be enabled on the dynamic VLAN port. Attempting to set IEEE 802.1x port-control to auto or force-unauthorized (force_unauth) mode on a dynamic VLAN port, which is not allowed, causes this condition.
Recommended Action Disable dynamic VLAN configuration on the interface, and enable IEEE 802.1x.
Error Message DOT1X-5-ERR_INVALID_AAA_ATTR: Got invalid AAA attribute settings [chars]
Note
Explanation The authorization settings are either unsupported or invalid.
Recommended Action Change the settings to valid values.
Error Message DOT1X-5-ERR_INVALID_TUNNEL_MEDIUM_TYPE: Got an invalid value [chars] for TUNNEL_MEDIUM_TYPE [chars]
Note
Explanation The provided tunnel medium is either unsupported or invalid.
Recommended Action Change the value to a valid tunnel medium.
Error Message DOT1X-5-ERR_INVALID_TUNNEL_TYPE: Got an invalid value of [chars] for TUNNEL_TYPE [chars]
Note
Explanation The provided tunnel type is either unsupported or invalid.
Recommended Action Change the value to a valid tunnel type.
Error Message DOT1X-5-ERR_MULTI_ACCESS: Dot1x can not be enabled on voice vlan configured ports.
Note
Explanation IEEE 802.1x could not be enabled on a voice VLAN-configured port. Attempting to set IEEE 802.1x port-control to auto or force-unauthorized (force_unauth) mode on a voice VLAN-configured port, which is not allowed, causes this condition.
Recommended Action Disable the voice VLAN on the interface, and enable IEEE 802.1x.
Error Message DOT1X-5-ERR_PER_USR_IP_ACL: Applied per-user IP ACL was unsuccessful on interface [chars]
Note
Explanation The switch was unable to apply a per-user IP ACL, possibly because of an invalid hub from the RADIUS server.
Recommended Action Examine the RADIUS hub, and configure a valid one.
Error Message DOT1X-5-ERR_PER_USR_MAC_ACL: Applied per-user MAC ACL was unsuccessful on interface [chars]
Note
Explanation The switch was unable to apply a per-user MAC ACL, possibly because of an invalid setting from the RADIUS server.
Recommended Action Examine the RADIUS hub, and configure a valid setting.
Error Message DOT1X-5-ERR_PRIMARY_VLAN: Dot1x can not be enabled on the port [chars] configured in Primary Vlan.
Note
Explanation IEEE 802.1x could not be enabled on the primary VLAN port. [chars] is the port name. Trying to set IEEE 802.1x port-control to auto or force-unauthorized mode on a primary VLAN port, which is not allowed, can cause this condition. This condition might also occur when a port tries authentication in a primary VLAN.
Recommended Action Reconfigure the VLAN type so it is not the primary VLAN, and then enable IEEE 802.1x.
Error Message DOT1X-5-ERR_PROTO_TUNNELLING: Dot1x can not be enabled on protocol tunnelling enabled ports.
Note
Explanation The protocol-tunneling-enabled port could not enable IEEE 802.1x. Attempting to set IEEE 802.1x port-control to auto or force-unauthorized (force_unauth) mode on a protocol-tunneling-enabled port, which is not allowed, causes this condition.
Recommended Action Do not configure IEEE 802.1x on a tunneled interface.
Error Message DOT1X-5-ERR_RADIUSVLAN_EQ_VVLAN: RADIUS attempted to assign a VLAN to Dot1x port [chars] whose Voice VLAN is same as AccessVlan
Note
Explanation The RADIUS server attempted to assign a VLAN to a client on a port with a voice VLAN that is equal to the access VLAN.
Recommended Action Either update the RADIUS configuration to not assign the VLAN equal to the voice VLAN, or change the voice VLAN on this port.
Error Message DOT1X-5-ERR_RSPAN_VLAN: Dot1x can not be enabled on ports configured in Remote SPAN vlan.
Note
Explanation IEEE 802.1x could not be enabled on the remote SPAN VLAN port. Attempting to set IEEE 802.1x port-control to auto or force-unauthorized (force_unauth) mode on a port that is in a remote SPAN VLAN, which is not allowed, causes this condition.
Recommended Action Disable the remote SPAN on the VLAN, and enable IEEE 802.1x.
Error Message DOT1X-5-ERR_SECONDARY_VLAN: Dot1x can not be enabled on Secondary Vlan on the port [chars].
Note
Explanation IEEE 802.1x could not be enabled on an access port in a secondary VLAN because the access port is not authorized in the secondary VLAN. [chars] is the port name.
Recommended Action Change the VLAN type, and enable IEEE 802.1x.
Error Message DOT1X-5-ERR_SPANDST: Dot1x can not be enabled on [chars]. It is configured as a SPAN Dest port.
Note
Explanation IEEE 802.1x and SPAN destination ports are mutually exclusive features. [chars] is the port.
Recommended Action Disable the SPAN destination port configuration before reconfiguring IEEE 802.1x on the port.
Error Message DOT1X-5-ERR_TRUNK: Dot1x can not be enabled on Trunk port.
Note
Explanation IEEE 802.1x could not be enabled on the trunk port. Attempting to set IEEE 802.1x port-control to auto or force-unauthorized (force_unauth) mode on a trunk port, which is not allowed, causes this condition.
Recommended Action Disable trunking on the interface, and then enable IEEE 802.1x.
Error Message DOT1X-5-ERR_TUNNEL: Dot1x can not be enabled on 802.1q tunnelling enabled ports.
Note
Explanation IEEE 802.1x could not be enabled on the IEEE 802.1Q tunneling-enabled port. Attempting to set IEEE 802.1x port-control to auto or force-unauthorized (force_unauth) mode on a IEEE 802.1Q tunnel-enabled port, which is not allowed, causes this condition.
Recommended Action Disable IEEE 802.1Q tunneling on the interface, and enable IEEE 802.1x.
Error Message DOT1X-5-ERR_VLAN_INTERNAL: The VLAN [dec] is being used internally and cannot be assigned for use on the Dot1x port [chars] Vlan
Note
Explanation The VLAN is used internally and cannot be assigned again for use on this port.
Recommended Action Update the configuration to not use this VLAN.
Error Message DOT1X-5-ERR_VLAN_INVALID: The VLAN [dec] is invalid and cannot be assigned for use on the 802.1X port [chars] Vlan
Note
Explanation The specified VLAN is out of range and cannot be assigned again for use on this port.
Recommended Action Update the configuration to use a valid VLAN.
Error Message DOT1X-5-ERR_VLAN_NOT_ASSIGNABLE: RADIUS tried to assign a VLAN to dot1x port [chars] whose VLAN cannot be assigned
Note
Explanation The RADIUS server tried to assign a VLAN to a client on a port whose VLAN cannot be changed, such as a routed port.
Recommended Action There is no recommended action.
Error Message DOT1X-5-ERR_VLAN_NOT_FOUND: Attempt to assign non-existent [chars] VLAN [chars] to dot1x port [chars]
Note
Explanation An attempt to assign a VLAN to a client on a port fails because the VLAN was not found in the VTP database.
Recommended Action Verify that the VLAN exists, or use another VLAN.
Error Message DOT1X-5-ERR_VLAN_RESERVED: The VLAN [dec] is a reserved vlan and cannot be assigned for use on the Dot1x port [chars] Vlan
Note
Explanation The specified VLAN is reserved and cannot be assigned for use on this port.
Recommended Action Update the configuration to not use this VLAN.
Error Message DOT1X-5-ERR_VLAN_RSPAN_CONFIGURED: VLAN [dec] is configured as a Remote SPAN VLAN, which has Dot1x enabled interface(s) configured. Please disable Dot1x on all ports in this VLAN or do not enable RSPAN on this VLAN.
Note
Explanation You should not enable RSPAN on a VLAN whose ports are configured with IEEE 802.1x enabled.
Recommended Action Either disable the RSPAN configuration on the VLAN, or disable IEEE 802.1x on all of the ports in this VLAN.
Error Message DOT1X-5-ERR_VLAN_SHUTDOWN: Attempt to assign shutdown [chars] VLAN [dec] to dot1x port [chars]
Note
Explanation There is an attempt to assign a VLAN that has been shut down to a supplicant on a port. The first [chars] is (what?) [dec] is the VLAN ID, and the second [chars] is the port name.
Recommended Action Re-enable the VLAN or configure a different VLAN.
Error Message DOT1X-5-INVALID_INPUT: Dot1x Interface parameter is Invalid on interface [chars].
Note
Explanation The IEEE 802.1x interface parameter is out of the specified range or is invalid.
Recommended Action See the CLI help by entering a ? after the command to see the valid range.
Error Message DOT1X-5-INVALID_MAC: Invalid MAC address (drop, zero, broadcast or multicast mac address) [enet] is trying to authenticate.
Note
Explanation A MAC address that was either a zero, broadcast, or multicast address attempted authentication by using IEEE 802.1x. However, IEEE 802.1x authentication is allowed only for valid nonzero, nonbroadcast, or nonmulticast source MAC addresses.
Recommended Action Connect a host that has a valid IEEE 802.1x address to the IEEE 802.1x-enabled port.
Error Message DOT1X-5-NO_UNIDIR_EDGE: Unidirectional port-control is configured on interface [chars], but will not be activated. Port is not configured for portfast.
Note
Explanation The unidirectional port-control feature is configured but not activated because the specified interface is not configured as a PortFast port.
Recommended Action To activate the unidirectional port-control feature, enter the spanning-tree portfast interface configuration command.
Error Message DOT1X-5-NOT_DOT1X_CAPABLE: Dot1x disabled on interface [chars] because it is not an Ethernet interface.
Note
Explanation You can enable IEEE 802.1x authentication only on Ethernet interfaces.
Recommended Action Enable IEEE 802.1x authentication only on Ethernet interfaces.
Error Message DOT1X-5-SECURITY_VIOLATION: Security violation on interface [chars], New MAC address [enet] is seen on the interface in [chars] mode.
Note
Explanation The port on the specified interface is configured in single-host mode. Any new host that is detected on the interface is perceived as a security violation. The port has been disabled.
Recommended Action Verify that the port is configured to use only one host. Enter the shutdown command followed by the no shutdown interface configuration command to restart the port.
DTP Messages
This section contains the Dynamic Trunking Protocol (DTP) messages.
Error Message DTP-4-MEM_UNAVAIL: Memory was not available to perform the trunk negotiation action.
Note
Explanation 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].
Note
Explanation 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.
Note
Explanation 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-DOMAINMISMATCH: Unable to perform trunk negotiation on port [chars] because of VTP domain mismatch.
Note
Explanation The two ports involved in trunk negotiation belong to different VTP domains. Trunking is possible only when the ports involved belong to the same VTP domain. [chars] is the name of the interface.
Recommended Action Ensure that the two ports that are involved in trunk negotiation belong to the same VTP domain.
Error Message DTP-5-ILGLCFG: Illegal config (on, isl--on, dot1q) on [chars].
Note
Explanation 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.
Note
Explanation 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.
Note
Explanation 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.
Note
Explanation 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, Link Aggregation Control Protocol (LACP), and Port Aggregation Protocol (PAgP) messages.
Error Message EC-4-NOMEM: Not enough memory available for [chars].
Note
Explanation Either the LACP or the PAgP EtherChannel could not obtain the memory it needed to initialize the required data structures. [chars] is the name of the data structure.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message EC-5-BUNDLE: Interface [chars] joined port-channel [chars].
Note
Explanation The listed interface joined the specified EtherChannel. The first [chars] is the physical interface, which can be a switch port or a routed port, and the second [chars] is the EtherChannel interface.
Recommended Action No action is required.
Error Message EC-5-CANNOT_ALLOCATE_AGGREGATOR: Aggregator limit reached, cannot allocate aggregator for group [dec].
Note
Explanation The aggregator cannot be allocated in the group.
Recommended Action Change the port attributes of the ports in the group so that they match and
join the same aggregator.Error Message EC-5-CANNOT_BUNDLE_LACP: [chars] is not compatible with aggregators in channel [dec] and cannot attach to them ([chars]).
Note
Explanation The port has port attributes that are different from the port channel or ports within the port channel.
Recommended Action Change the port attributes so that they match the other ports in the EtherChannel.
Error Message EC-5-CANNOT_BUNDLE1: Port-channel [chars] is admin-down, port [chars] will remain stand-alone.
Note
Explanation The EtherChannel is administratively shut down. The first [chars] is the EtherChannel interface, 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 ([chars]).
Note
Explanation The interface has different interface attributes than other ports in the port channel. For the interface to join the bundle (EtherChannel), change the interface attributes to match the EtherChannel attributes. The first [chars] is the interface to be bundled, the second [chars] is the physical interface (a switch port or a routed port) that is already in the bundle, and the third [chars] is the reason for the incompatibility.
Recommended Action Change the interface attributes to match the EtherChannel attributes.
Error Message EC-5-COMPATIBLE: [chars] is compatible with port-channel members.
Note
Explanation A port was not operational because its attributes were different from those of the port channel or ports within the port channel. The system has detected that the attributes of the port now match the port-channel attributes. [chars] is the affected port.
Recommended Action No action is required.
Error Message EC-5-DONTBNDL: [chars] suspended: incompatible partner port with [chars]
Note
Explanation The configuration of the partner port differs from the configuration of other ports in the bundle. A port can only join the bundle when its global configuration and the configuration of the partner port are the same as other ports in the bundle.The first [chars] is the local interface that is being suspended, and the second [chars] is the local interface that is already bundled.
Recommended Action Verify that the configuration of the partner ports is the same for all ports in the bundle.
Error Message EC-5-ERRPROT: Channel protocol mismatch for interface [chars] in group [dec]: the interface cannot be added to the channel group.
Note
Explanation The interface cannot be added to the channel group by using the specified mode. [chars] is the interface, and [dec] is the channel group.
Recommended Action Change the channel group or the mode for the interface.
Error Message EC-5-ERRPROT2: Command rejected: the interface [chars] is already part of a channel with a different type of protocol enabled.
Note
Explanation The interface cannot be selected for the specified protocol because it is already part of an EtherChannel group with a different protocol enabled. [chars] is the interface.
Recommended Action Remove the interface from the EtherChannel group.
Error Message EC-5-ERRPROT3: Command rejected: the interface [chars] is already part of a channel.
Note
Explanation The interface cannot be unselected for the specified protocol because it is already part of an EtherChannel group. [chars] is the interface.
Recommended Action Remove the interface from the EtherChannel group.
Error Message EC-5-L3DONTBNDL1: [chars] suspended: PAgP not enabled on the remote port.
Note
Explanation PAgP is enabled on the Layer 3 interface, but the partner port is not enabled for PAgP. In the port aggregation protocol 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].
Note
Explanation The group capabilities of the remote port are different than one or more of the other ports in the bundle. For a port to join a bundle, the local port and the remote port must have the same group capabilities as the other ports in the bundle. [chars] is the physical interface, which can be a switch port or a routed port.
Recommended Action Configure the remote port with the same group capabilities as the other ports in the bundle.
Error Message EC-5-L3DONTBNDL3: [chars] suspended: LACP not enabled on the remote port.
Note
Explanation LACP is enabled on a Layer 3 interface, but the remote port does not have LACP enabled. In this mode, the local port is put in a suspended state.
Recommended Action Enable LACP on the remote port.
Error Message EC-5-L3STAYDOWN: [chars] will remain down as its port-channel [chars] is admin-down.
Note
Explanation 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-NOLACP: Invalid EC mode. LACP not enabled.
Note
Explanation LACP is not included in the image on your switch. An EtherChannel cannot be set into any LACP mode.
Recommended Action Upgrade your switch with an image that supports LACP.
Error Message EC-5-NOPAGP: Invalid EC mode. PAgP not enabled.
Note
Explanation PAgP is not included in the Cisco 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-PORTDOWN: Shutting down [chars] as its port-channel is admin-down.
Note
Explanation The administrative state of the port is down because its EtherChannel interface, which controls the state of the port, is down.
Recommended Action Enter the no shutdown interface configuration command on the aggregate port.
Error Message EC-5-STAYDOWN: no-shut not allowed on [chars]. Module [dec] not online.
Note
Explanation An interface with an EtherChannel configuration cannot be enabled by using the no shutdown interface configuration command. It is a member of an EtherChannel group, and that EtherChannel group has been administratively shut down. The interface has an EtherChannel configuration, but no information is available yet about its port channel.
Recommended Action No action is required. Wait until the interface is online to determine the port-channel setting of the EtherChannel.
Error Message EC-5-STAYDOWN: [chars] will remain down as its port-channel [chars] is admin-down.
Note
Explanation The administrative state of the aggregation port overrides that of the affected port. If the aggregation port is administratively down, all ports in the aggregation port are forced to be administratively down.
Recommended Action Enter the no shutdown interface configuration command on the EtherChannel interface to bring up the aggregation port.
Error Message EC-5-UNBUNDLE: Interface [chars] left the port-channel [chars].
Note
Explanation The listed interface left the specified EtherChannel. The first [chars] is the physical interface, which can be a switch port or a routed port, and the second [chars] is the EtherChannel.
Recommended Action No action is required.
Error Message EC-5-UNSUITABLE: [chars] will not join any port-channel, [chars].
Note
Explanation One of the interfaces cannot join the EtherChannel because it is configured for PortFast, as a VLAN Membership Policy Server (VMPS), for IEEE 802.1x, as a voice VLAN, or as a Switched Port Analyzer (SPAN) destination port. All of these are unsuitable configurations for EtherChannels. The first [chars] is the interface name, and the second [chars] describes the details of the unsuitable configuration.
Recommended Action Reconfigure the port; remove the unsuitable configuration.
ENVIRONMENT Messages
This section contains the Environment messages.
Error Message ENVIRONMENT-2-FAN_FAULT: FAN FAULT is detected.
Note
Explanation An internal fan fault is detected.
Recommended Action Look at the switch to see if the fan is running, or use the show env privileged EXEC command to determine if a fan on the switch has failed. The switch can operate normally with one failed fan. Replace the switch at your convenience.
Error Message ENVIRONMENT-2-OVER_TEMP:System Fault:OVER TEMPERATURE condition is detected.
Note
Explanation An overtemperature condition is detected.
Recommended Action Use the show env privileged EXEC command to check if an overtemperature condition exists. If an overtemperature condition does exist, place the switch in an environment that is within 32 to 113°F (0 to 45°C), and make sure that the fan intake and exhaust areas are clear.
Note
Error Message ENVIRONMENT-3-OVERTEMP:ASSERT MAJOR Switch Temp above max primary threshold.
Note
Explanation The temperature inside the switch exceeds the maximum primary threshold. A major alarm is raised.
Recommended Action Use the show env privileged EXEC command to verify if an over-temperature condition exists. If an over-temperature condition does exist, place the switch in an environment that is within the switch operating temperature. For information about correct operating temperatures, refer to the Catalyst 2955 Switch Hardware Installation Guide.
Error Message ENVIRONMENT-3-OVERTEMP: CLEAR MAJOR Switch Temp above max primary threshold.
Note
Explanation The temperature inside the switch is below the maximum primary threshold. A major alarm is cleared.
Recommended Action No action is required.
Error Message ENVIRONMENT-3-RPS_FAILED:ASSERT [chars] Switch Redundant Pwr missing or failed.
Note
Explanation The redundant power supply for a system in dual-power mode is either missing or has failed. An associated [chars] alarm is raised. [chars] is the user-configured alarm for this failure.
Recommended Action No action is required.
Error Message ENVIRONMENT-3-RPS_FAILED:CLEAR [chars] Switch Redundant Pwr missing or failed.
Note
Explanation The redundant power supply for a system in dual-power mode is detected or operational after a failure. An associated [chars] alarm is cleared. [chars] is the user-configured alarm for this failure.
Recommended Action Look at the redundant power supply and make sure that it is operating properly.
Error Message ENVIRONMENT-3-UNDERTEMP:ASSERT MAJOR Switch Temp below min primary threshold.
Note
Explanation The temperature inside the switch is below the minimum primary threshold. A major alarm is raised.
Recommended Action Use the show env privileged EXEC command to verify if an undertemperature condition exists. If an undertemperature condition does exist, place the switch in an environment that is within the switch operating temperature. For information about the correct operating temperature, refer to the Catalyst 2955 Switch Hardware Installation Guide.
Error Message ENVIRONMENT-3-UNDERTEMP:CLEAR MAJOR Switch Temp above min primary threshold.
Note
Explanation The temperature inside the switch is above the minimum primary threshold. A major alarm is cleared.
Recommended Action No action is required.
Error Message ENVIRONMENT-4-CONFIG_OVERTEMP: ASSERT [chars] Switch Temp above secondary threshold.
Note
Explanation The temperature inside the switch exceeds the configured threshold. An associated alarm is raised. [chars] is the user-configured alarm for this failure.
Recommended Action Use the show env privileged EXEC command to monitor the switch temperature. If an overtemperature condition occurs, place the switch in an environment that is within the switch operating temperature. For information about the correct operating temperature, refer to the Catalyst 2955 Switch Hardware Installation Guide.
Error Message ENVIRONMENT-4-CONFIG_OVERTEMP: CLEAR [chars] Switch Temp above secondary threshold.
Note
Explanation The temperature inside the switch is below the configured threshold. An associated alarm is cleared. [chars] is the user-configured alarm for this failure.
Recommended Action No action is required.
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.
Error Message ETHCNTR-2-MOLSENDTIMEOUT: Molecule send timeout, queue [dec], molecule [hex] [hex].
Note
Explanation An attempt to read or write one or more of the hardware settings failed.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message ETHCNTR-3-FLOWCONTROL_DUPLEX_ERROR: Flowcontrol will not take effect until duplex is set to auto.
Note
Explanation Flow control cannot be set on the switch in this configuration.
Recommended Action Configure the duplex mode to auto.
Error Message ETHCNTR-3-HALF_DUX_COLISION_EXCEED_THRESHOLD: Collision at [chars] exceed threshold. Consider as loop-back.
Note
Explanation The collision at a half-duplex port exceeded the threshold, and the port is considered to be in the loop-back state. On switches that support Power over Ethernet (PoE), this message might appear when a device that can be powered by either a PoE switch port or by AC power is not being powered by an external AC power source and is connected to a port that has been configured with the power inline never interface configuration command. [chars] is the port where the threshold was exceeded.
Recommended Action On switches that support PoE, remove the device or configure the port by entering the power inline auto, the shutdown, and the no shutdown interface configuration commands. No action is required on non-PoE switches. The port goes into error-disabled mode until the problem is resolved.
Error Message ETHCNTR-3-INTERNAL_ERROR: Internal Error [chars].
Note
Explanation 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 Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message ETHCNTR-3-INVALIDMAP: Invalid map [dec] for address [enet].
Note
Explanation 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 Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message ETHCNTR-3-LOOP_BACK_DETECTED:, Loop-back detected on [chars]. The port is forced to linkdown.
Note
Explanation A loopback condition might be the result of a balun cable incorrectly connected into a port. On PoE switches, this message might appear when a device that can be powered by either a PoE switch port or by AC power is not being powered by an external AC power source and is connected to a port that has been configured with the power inline never interface configuration command. [chars] is the port.
Recommended Action On non-PoE switches, 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 then enable the port up by entering the no shutdown interface configuration command. On PoE switches, remove the device or configure the port by entering the power inline auto, the shutdown, and the no shutdown interface configuration commands.
Error Message ETHCNTR-3-MOLSENDINT: Molecule send from interrupt handler
Note
Explanation An interrupt handler is accessing the hardware in an inpermissible manner.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message ETHCNTR-3-RA_ALLOC_ERROR:RAM Access [chars] [chars] memory allocation failure.
Note
Explanation A request to read from or write to the RAM access failed its memory allocation. The first [chars] is the RAM access command that failed, and the second [chars] describes whether processor memory allocation or I/O memory allocation failed.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message ETHCNTR-3-RA_REPLY_ERROR: Invalid reply to RAM Access [chars] request ([hex]) from satellite [dec].
Note
Explanation A request to read from or write to 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 Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message ETHCNTR-3-UNEXPECTED_EVENT: Request [hex] encountered event [dec] in state [dec].
Note
Explanation An unexpected event occurred during a RAM-access request. [hex] is a request identifier. The first [dec] is an event number, and the second [dec] is a state number.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
EXPRESS_SETUP Messages
This section contains messages for the Express Setup feature.
Error Message EXPRESS_SETUP-3-UNABLE_TO_RESET_CONFIG<EMB_ErrMsgBody>: [chars]
Note
Explanation The system is unable to reset the configuration. [chars] is a text string that explains why the reset failed. For example,
error renaming config file,error removing config file, orerror removing private config file.Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message EXPRESS_SETUP-6-CONFIG_IS_RESET: [chars]
Note
Explanation The configuration is reset. [chars] is a text message that clarifies the reset event, such as
The configuration is reset and the system will now reboot.Recommended Action No action is required.
Error Message EXPRESS_SETUP-6-MODE_ENTERED:
Note
Explanation Express Setup mode is active.
Recommended Action No action is required.
Error Message EXPRESS_SETUP-6-MODE_EXITED
Note
Explanation Express Setup mode is no longer active.
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.
Note
Explanation The feature manager subsystem failed to initialize. The most likely cause is insufficient memory at initialization. Either the hardware has failed, or the wrong Cisco IOS image is installed.
Recommended Action Replace the failing hardware, or obtain the correct Cisco IOS image for this platform.
Error Message FM-2-NOMAP: Cannot create Feature Manager data structures for VLAN Map [chars].
Note
Explanation 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 memory demands.
Error Message FM-2-NOSB: Cannot create subblock for interface [chars].
Note
Explanation 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 memory.
Error Message FM-2-NOVLB: Cannot create memory block for VLAN [dec].
Note
Explanation 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 ID.
Recommended Action Use a less complicated configuration that requires less memory.
Error Message FM-2-NOVMR: Cannot create VMR data structures for access list [chars].
Note
Explanation 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.
Note
Explanation 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, the second [chars] is the direction in which the map was applied (input or output), and [dec] is the label number.
Recommended Action Reduce other system activity to ease the memory demands.
Error Message FM-3-CONFLICT: [chars] [chars] conflicts with [chars].
Note
Explanation Port access lists (PACLs) cannot be applied when input router access lists, VLAN maps, or IP multicast boundaries have been applied, and the reverse. [chars] are the names of the conflicting features.
Recommended Action Remove the conflicting feature or features, and apply the configuration again.
Error Message FM-3-GOTLABEL: Got label for [chars].
Note
Explanation 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].
Note
Explanation 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 ID.
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-ILLEGALCOPY: Illegal copy of [chars] access group [chars] from [chars] label [dec] to [dec].
Note
Explanation An internal software error occurred. The first [chars] is either ip or mac, the second [chars] is an access list name, the third [chars] is either port or vlan, and the two [dec] values are label numbers.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message FM-3-INITLABEL: Special initialization of label [dec] failed.
Note
Explanation 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. [dec] is the label number.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message FM-3-INSERTFAIL: Insert of access-map [chars] [dec] into [chars] label [dec] failed.
Note
Explanation The system ran out of CPU memory 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-INTTABLE: Not in truth table: VLMAP [dec] RACL [dec] Rtprot [dec] Redir [dec] Mcb [dec] Feat [dec].
Note
Explanation An unrecoverable software error occurred while the software was trying to merge the configured input features. The first five [dec] values are internal code numbers for the results of the VLAN map, router ACL, routing protocol selector, IP redirect settings, and the multicast boundary configured on a Layer 3 interface. The sixth [dec] value is the feature that was being examined when the problem was detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message FM-3-LABELERROR: Incorrect label to [chars] vlan label attribute copy callback srclabel [dec], dstlabel [dec].
Note
Explanation The feature manager attribute copy callback was called with an incorrect source or destination label. [chars] is the direction (input or output), the first [dec] is the source label value, and the second [dec] is the destination label value.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message FM-3-MAXRECURSION: Too many ([dec]) levels of recursion while merging [chars] (code [dec]).
Note
Explanation The configuration is too complicated for the platform-specific ACL merge code to support. The most likely cause is too many separate access lists in a single VLAN map or policy map. The first [dec] is the number of levels of recursion. [chars] describes which stage of the merge encountered the problem; the stage can be one of these: VLAN map, Global Input, Global Output, or QoS Map. The second [dec] is an internal code number of the merge stage that encountered the problem.
Recommended Action Reduce the number IP or MAC access lists (counted separately) in any one VLAN or policy map to fewer than the number of levels reported by this log message.
Error Message FM-3-MERGEFAIL: [chars] ACL merge error [dec] ([chars]) on [chars] label [dec].
Note
Explanation The feature manager was unable to merge 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. The first [chars] is the ACL-type error (ip or mac), the first [dec] is the error code, the second [chars] is the message string for the preceding error code, the second [dec] is the label number, and the third [chars] is either input or output.
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].
Note
Explanation 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), and the second [chars] is the interface name.
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 ACLs on multiple interfaces, if possible.
Error Message FM-3-NOLABELVL: Cannot allocate [chars] label for VLAN [dec].
Note
Explanation 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), and [dec] is the VLAN ID.
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-NOTEMPTY: Illegal copy of attribute to non empty [chars] vlan label [dec].
Note
Explanation The feature manager attribute copy callback was called with a destination label already being used by a VLAN or routed port. [chars] is the direction (input or output), and [dec] is the label value.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message FM-3-NOTOBJECT: Invalid object (VLAN [dec], IDB [hex]) used in Feature Manager operation.
Note
Explanation An internal software error has occurred. An invalid combination of VLAN and interface descriptor block (IDB) values was passed to a software routine. [dec] is the VLAN ID, and [hex] is the IDB value.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message FM-3-NULLCPU: Sending traffic on empty [chars] label [dec] to CPU.
Note
Explanation An internal software error occurred. [chars] is the direction (input or output), and [dec] is the label number.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message FM-3-OUTTTABLE: Not in truth table: RACL [dec] VLMAP [dec].
Note
Explanation An unrecoverable software error occurred while trying to merge the configured output features. The two [dec] values are internal code numbers for the results of the router ACL and VLAN map configured on a particular Layer 3 interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message FM-3-QOSTTABLE: Not in truth table: ACL [dec] in map, action [dec].
Note
Explanation A software error occurred while trying to merge a quality of service (QoS) policy map. The first [dec] is the number in the policy map (counting from zero) of the particular ACL where the problem was discovered, and the second [dec] is an internal code number for the result of matching that ACL in the policy map.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message FM-3-RELOADED: Reloading [chars] label [dec] feature in [chars].
Note
Explanation The feature manager is now able to fit more of the configured features on this label into the hardware. One or more features had been previously unloaded because of a lack of space. The first [chars] is the direction (input or output), [dec] is the label number, and the second [chars] is the TCAM ID.
Recommended Action No action is required.
Error Message FM-3-TOSCOST: Minimize monetary cost TOS bit unsupported in hardware, ignored.
Note
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; the hardware ignores this bit when checking for a match to an 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-UNKNOWNACTION: Unknown VMR access group action [hex].
Note
Explanation An internal software error has occurred.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message FM-3-UNLOADING: Unloading [chars] label [dec] feature from [chars].
Note
Explanation 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 from being forwarded in hardware and requires them to be forwarded by the CPU. Multicast packets might be dropped instead of being forwarded. The first [chars] is the direction (input or output), [dec] is the label number, and the second [chars] is the TCAM ID.
Recommended Action Allocate more space to the relevant section of the TCAM by using the sdm prefer global configuration command and then reboot the switch, or use a simpler configuration. Use the same ACLs on multiple interfaces, if possible.
Error Message FM-3-WRONGLABEL: Inconsistent records of label for [chars]: FM has [dec], LM has [dec].
Note
Explanation An internal software error has occurred. [chars] is an interface name. The rest of the message
FM has [dec], LM has [dec]means that the feature manager has a record that the interface belongs to the first [dec] and that the label manager has a record that the interface belongs to the second [dec]. Therefore, the software is in an inconsistent state.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message FM-4-EXCESSSECONDARY: More than [dec] secondary IP addresses configured on interface [chars].
Note
Explanation When secondary IP addresses are configured on an interface and you enable Internet Control Message Protocol (ICMP) redirects for packets received on that interface, the ICMP redirect function on the CPU is not usually notified of packets sent between two different subnets on the same interface. If too many secondary IP addresses are configured on the interface this message is logged, and in addition to being notified about packets that cause the generation of an ICMP redirect, the CPU is also notified about every packet routed between two different subnets that are both on the interface. No ICMP redirects will be sent in error, but the CPU usage might increase because of the additional notifications. [dec] is the limit of secondary IP addresses, and [chars] is the specified interface.
Recommended Action You can use the no ip redirects interface configuration command on the interface named in the message to reduce the CPU load on the system.
Error Message FM-7-TRANSDEF: No augmentation function found for VMR.
Note
Explanation An internal error occurred. An ACL was not correctly interpreted. The value-mask result (VMR) is incorrect.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
GBIC Messages
This section contains Gigabit Interface Converter (GBIC) module identification and validation messages. When a GBIC module is inserted into the switch, the software reads information from the module that identifies its type, and for some types of GBIC modules, obtains additional information to validate the compatibility of the module.
Note
Error Message GBIC_1000BASET-6-GBIC_1000BASET_DEFAULT_CONFIG: 1000BASE-T GBIC module is detected in [chars]. Speed and duplex will be autonegotiated.
Note
Explanation A 1000BASE-T GBIC module is detected in the slot, and its speed and duplex are automatically negotiated. [chars] is the slot in which the module is installed.
Recommended Action No action is required.
Error Message GBIC_1000BASET-6-GBIC_1000BASET_NO_CONFIG_DUPLEX: Configuration ignored. 1000-BaseT GBIC modules only support autonegotiation on duplex.
Note
Explanation Autonegotiation was not used. The 1000BASE-T GBIC modules only support autonegotiation on duplex.
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.
Note
Explanation The disabling of autonegotiation was not used. The 1000BASE-T GBIC modules support autonegotiation.
Recommended Action No action is required.
Error Message GBIC_1000BASET-6-GBIC_1000BASET_NO_CONFIG_SPEED: Configuration ignored. 1000-BaseT GBIC modules only support autonegotiation on speed.
Note
Explanation Autonegotiation was ignored. The 1000BASE-T GBIC modules only support autonegotiated speed.
Recommended Action No action is required.
Error Message GBIC-4-CHECK_SUM_FAILED: GBIC EEPROM data check sum failed for GBIC interface [chars].
Note
Explanation The GBIC module was identified as a Cisco GBIC module, but the system was unable to read vendor-data information to verify its accuracy. [chars] is the interface in which the module is installed.
Recommended Action Remove and re-insert the GBIC module. If it continues to fail after re-insertion, it might be defective.
Error Message GBIC-4-NOREAD_VNAME: Unable to read vendor name for GBIC interface [chars].
Note
Explanation The GBIC module was identified as a Cisco GBIC module, but the system was unable to read the GBIC vendor name. [chars] is the interface in which the module is installed.
Recommended Action Remove and re-insert the GBIC module. If it continues to fail after re-insertion, it might be defective.
Error Message GBIC-4-NOREAD_VSDATA: Unable to read vendor-specific data for GBIC interface [chars].
Note
Explanation The GBIC module was identified as a Cisco GBIC module, but the system was unable to read the identifying vendor-specific information to verify its authenticity. [chars] is the interface in which the module is installed.
Recommended Action Remove and re-insert the GBIC module. If it continues to fail after re-insertion, it might be defective.
Error Message GBIC-4-NOREAD_VSERNUM: Unable to read serial number for GBIC interface [chars].
Note
Explanation The GBIC module was identified as a Cisco GBIC module, but the system was unable to read the serial number of the GBIC module. [chars] is the interface in which the module is installed.
Recommended Action Remove and re-insert the GBIC module. If it continues to fail after re-insertion, it might be defective.
Error Message GBIC-4-UNRECOGNIZED_EXTTYPE: GBIC interface [chars] has unrecognized extended type.
Note
Explanation The GBIC module was identified as a Cisco GBIC module, but the system does not recognize its reported extended type code. [chars] is the interface in which the module is installed.
Recommended Action Check the list of supported GBIC modules for this version of the system software. An upgrade might be required for newer GBIC modules. Even if the module is unrecognized, it might still operate properly, but perhaps with limited functionality.
Error Message GBIC-4-XCVR_INTERR: Internal error occurred in setup for GBIC interface [chars].
Note
Explanation The system could not allocate resources or had some other problem during the setup for the specified GBIC interface. [chars] is the interface in which the GBIC module is installed.
Recommended Action Reload the switch by using the reload privileged EXEC command. If the problem persists, call your Cisco technical support representative.
Error Message GBIC-6-SERDES_MODULE_UNKNOWN: Unrecognizable GBIC found in [chars] (module mask [hex]).
Note
Explanation The GBIC module presented data to the system that did not correctly identify the type of the GBIC module. The switch will treat it as a generic GBIC module. [chars] is the name of the interface in which the unknown module is installed, and [hex] is the module type value returned by the module.
Recommended Action If the GBIC module fails to become operational, carefully remove and re-insert it in the slot. If it continues to fail after re-insertion, it might be defective or incompatible with the switch.
Error Message GBIC-6-SERDES_SERIAL_INV_DATA: Unrecognizable GBIC found in [chars] (serial data [hex]).
Note
Explanation The GBIC module presented data to the system that did not correctly identify the type of the GBIC module. The switch will treat it as a generic GBIC module. [chars] is the name of the interface where the unrecognizable module is found, and [hex] is the data value returned by the module.
Recommended Action If the GBIC module fails to become operational, carefully remove and re-insert it in the slot. If it continues to fail after re-insertion, it might be defective or incompatible with the switch.
GBIC_SECURITY Messages
This section contains the Cisco GBIC module security messages. The GBIC modules have a serial EEPROM that contains the serial number, security code, and cyclic redundancy check (CRC). When the GBIC module is inserted into the switch, the software reads the EEPROM to recompute the security code and CRC. The software generates an error message if the CRC is invalid or if the recomputed security code does not match the one stored in the EEPROM.
Note
Error Message GBIC_SECURITY-4-DUPLICATE_SN: GBIC interface [dec] has the same serial number as another GBIC interface.
Note
Explanation The GBIC module was identified as a Cisco GBIC module, but its serial number matches that of another interface on the system. [chars] is the interface in which the module is installed.
Recommended Action Cisco GBIC modules are assigned unique serial numbers. Verify that the module was obtained from Cisco or a supported vendor.
Error Message GBIC_SECURITY-4-GBIC_INTERR: Internal error occurred in setup for GBIC interface [chars].
Note
Explanation The system could not allocate resources or had some other problem during the setup for the specified GBIC interface. [chars] is the interface in which the GBIC module is installed.
Recommended Action Reload the switch by using the reload privileged EXEC command. If the problem persists, call your Cisco technical support representative.
Error Message GBIC_SECURITY-4-ID_MISMATCH: Identification check failed for GBIC interface [chars].
Note
Explanation The GBIC module was identified as a Cisco GBIC module, but the system was unable to verify its identity. [chars] is the interface in which the module is installed.
Recommended Action Check the list of supported GBIC modules for this version of the system software. An upgrade might be required for newer modules. Otherwise, verify that the module was obtained from Cisco or a supported vendor.
Error Message GBIC_SECURITY-4-UNRECOGNIZED_VENDOR: GBIC interface [chars] manufactured by an unrecognized vendor.
Note
Explanation The GBIC module was identified as a Cisco GBIC module, but the system was unable to match its manufacturer with one of the known list of Cisco GBIC vendors. [chars] is the interface in which the module is installed.
Recommended Action Check the list of supported GBIC modules for this version of the system software. An upgrade might be required for newer modules.
Error Message GBIC_SECURITY-4-VN_DATA_CRC_ERROR: GBIC interface [chars] has bad crc.
Note
Explanation The GBIC module was identified as a Cisco GBIC module, but it does not have a valid CRC in the EEPROM data. [chars] is the interface in which the module is installed.
Recommended Action Check the list of supported GBIC modules for this version of the system software. An upgrade might be required for newer modules. Even if unrecognized, the module might still operate properly, perhaps with limited functionality.
GBIC_SECURITY_CRYPT Messages
This section contains the Cisco GBIC module security messages. The switch recognizes the GBIC module as a Cisco GBIC module but identifies another problem with it.
Note
Error Message GBIC_SECURITY_CRYPT-4-ID_MISMATCH: Identification check failed for GBIC in port [dec].
Note
Explanation The GBIC module was identified as a Cisco GBIC module, but the system was unable to verify its identity. [dec] is the interface in which the module is installed.
Recommended Action Verify that the software release that is running on the system supports the GBIC module. If the GBIC module is newer, a system software upgrade might be required. Otherwise, verify that the GBIC module was obtained from Cisco or from a supported vendor.
Error Message GBIC_SECURITY_CRYPT-4-UNRECOGNIZED_VENDOR: GBIC in port [dec] manufactured by an unrecognized vendor.
Note
Explanation The GBIC module was identified as a Cisco GBIC module, but the system was unable to match its manufacturer with one on the known list of Cisco GBIC module vendors. [dec] is the interface in which the module is installed.
Recommended Action Verify that the Cisco IOS software running on the system supports the GBIC module. If the GBIC module is newer, a system software upgrade might be required.
Error Message GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port [dec] has bad crc.
Note
Explanation The GBIC module was identified as a Cisco GBIC module, but it does not have a valid CRC in the EEPROM data. [dec] is the interface in which the module is installed.
Recommended Action Verify that the software release that is running on the system supports the GBIC module. If the GBIC module is newer, a system software upgrade might be required. Even if the GBIC module is unrecognized by the system, the GBIC module might still operate properly, but it will have limited functionality.
GBIC_SECURITY_UNIQUE Messages
This section contains the Cisco GBIC module security messages that identify whether the GBIC module is unique.
Note
Error Message GBIC_SECURITY_UNIQUE-3-DUPLICATE_GBIC: GBIC interface [dec]/[dec] is a duplicate of GBIC interface [dec]/[dec].
Note
Explanation The GBIC module was identified as a Cisco GBIC module, but its vendor ID and serial number match that of another interface in the system. The first [dec]/[dec] is the module number and the interface number of the GBIC module that caused the error message to occur. The second [dec]/[dec] is the module number and the interface number of the other GBIC module that is already installed in the system.
Recommended Action Cisco GBIC modules are assigned unique serial numbers. Verify that the GBIC module was obtained from Cisco or from a supported vendor.
Error Message GBIC_SECURITY_UNIQUE-4-DUPLICATE_SN: GBIC interface [dec]/[dec] has the same serial number as another GBIC interface.
Note
Explanation The GBIC module was identified as a Cisco GBIC module, but its serial number matches that of another interface in the system. The first [dec]/[dec] is the module number and the interface number in which the module is installed. The second [dec]/[dec] is the duplicate module number and the interface number reported in the message.
Recommended Action Cisco GBIC modules are assigned unique serial numbers. Verify that the GBIC module was obtained from Cisco or from a supported vendor.
GIGASTACK Messages
This section contains the GigaStack 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.
Note
Explanation No acknowledgement for the loop-detection request is received from one of the links on a GigaStack GBIC module. Either the neighboring switch does not support the GigaStack GBIC loop-breaking algorithm, or the link between the two GigaStack GBIC modules 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, and [chars] is the slot number.
Recommended Action If a loop topology is used with the GigaStack GBIC module, ensure that the latest software is running on all switches in the stack. Check the GigaStack GBIC modules involved to ensure that they are functioning.
Error Message GIGASTACK-3-INIT_FAILURE: GigaStack GBIC in [chars] initialization failed.
Note
Explanation The GigaStack GBIC module failed power-on self-test (POST). [chars] is the interface name.
Recommended Action Remove the GigaStack GBIC module, and re-insert it into the GBIC module 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.
Note
Explanation The loop formed by GigaStack GBIC modules 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 interface name.
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.
Note
Explanation A loop is detected in the stack, and this GigaStack GBIC module is selected as the master loop breaker. Link 2 of this GigaStack GBIC module is disabled to break the loop. [chars] is the interface name.
Recommended Action No action is required.
HWMATM_MOD Messages
This section contains the hardware MAC address table manager (HW MATM) messages.
Error Message HWMATM_MOD-3-NULLPTR: Unexpected null pointer in [chars] at [dec].
Note
Explanation An internal software error occurred. [chars] is the software filename, and [dec] is the line number in the file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support 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 or from the show tech-support command display, see the "Error Message Traceback Reports" section for more information.
IDBMAN Messages
This section contains the interface database (IDB) manager process messages on Catalyst 3550 switches.
Error Message IDBMAN-3-AGGPORTMISMATCH: [chars]: [chars]([dec] / [dec]) does match internal slot/port state [chars]([dec] / [dec]).
Note
Explanation The software is using an invalid EtherChannel interface.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message IDBMAN-3-DELETEDAGGPORT: [chars]([dec] / [dec]) Group [dec] has been deleted, but is being reused.
Note
Explanation A new EtherChannel interface is using a deleted interface.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message IDBMAN-3-INVALIDAGGPORTBANDWIDTH: [chars]([dec] / [dec]) has an invalid bandwidth value of [dec].
Note
Explanation An EtherChannel interface is using an invalid bandwidth.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message IDBMAN-3-INVALIDPORT: [chars]: trying to use invalid port number [dec] ( Max [dec] ).
Note
Explanation The software is using an invalid port number.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message IDBMAN-3-INVALIDVLAN: [chars]: trying to use invalid Vlan [dec].
Note
Explanation The software is using an invalid VLAN.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message IDBMAN-3-NOTANAGGPORT: [chars]( [dec] / [dec] ) is not an aggregate port.
Note
Explanation The EtherChannel interface operations are using a nonaggregate port interface.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message IDBMAN-3-PORTNOTINAGGPORT: [chars]([dec] / [dec]) is not present in Aggport [chars]([dec] / [dec]).
Note
Explanation An invalid port is being referred as being part of an EtherChannel interface.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message IDBMAN-3-VLANNOTSET: [chars]: Vlan [dec] not set since it already has Vlan [dec].
Note
Explanation An interface VLAN is not set to the requested value.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message IDBMAN-4-ACTIVEPORTSINAGGPORT: [chars]( [dec] / [dec] ) has [dec] active ports, but is being removed.
Note
Explanation An EtherChannel interface with active ports is being removed.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
ILPOWER Messages
This section contains the Power over Ethernet (PoE) messages for the Catalyst 3550-24PWR switch.
Error Message ILPOWER-3-CONTROLLER_ERR: Controller error, Controller number [dec]: [chars.]
Note
Explanation An error related to the PoE controller has occurred.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message ILPOWER-3-CONTROLLER_ERR:Controller error, Controller number [chars]: accessing failed
Note
Explanation An error reported or caused by the PoE controller was detected. [chars] is the controller number.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message ILPOWER-3-CONTROLLER_ERR:Controller error, Controller number [chars]:Reset failed
Note
Explanation An error reported or caused by the PoE controller was detected. [chars] is the controller number.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message ILPOWER-3-CONTROLLER_IF_ERR:Controller interface error, S2W bus:Initialization failed.
Note
Explanation An interface error was detected between the PoE controller and the system.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message ILPOWER-3-CONTROLLER_PORT_ERR:Controller port error, Interface Fa0/7:Power given, but link is not up.
Note
Explanation A port error reported by the PoE controller was detected.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message ILPOWER-3-CONTROLLER_IF_ERR: Controller interface error, [chars]: [chars]
Note
Explanation An interface error has occurred between the PoE controller and the switch CPU.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface [chars]: [chars].
Note
Explanation The PoE controller has detected a port error.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message ILPOWER-3-ILPOWER_INTERNAL_IF_ERROR:Inline Power internal error. Interface cannot obtain asic-cnfg information.
Note
Explanation The PoE feature code failed for unknown reasons. A software error has probably occurred.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message ILPOWER-5-DC_DISCONNECT: Interface [chars]: DC disconnect.
Note
Explanation The DC power has been disconnected.
Recommended Action No action is required.
Error Message ILPOWER-5-ILPOWER_POWER_DENY:Interface [chars]:inline power denied
Note
Explanation The PoE request was denied because the switch does not have enough power left to support the request. [chars] is the interface number.
Recommended Action No action is required.
L2TM Messages
This section contains the Layer 2 forwarding manager messages on Catalyst 3550 switches. This software module controls the part of the hardware that performs MAC address-based forwarding and learning. A ternary content addressable memory (TCAM) device implements the forwarding table.
Error Message L2TM-3-ACCESS_ERR: TCAM access failed while [chars].
Note
Explanation 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 Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message L2TM-7-INTERNAL_ERR: Internal error:[chars].
Note
Explanation An internal error occurred. [chars] describes the internal operation that failed.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
L3TCAM Messages
This section contains the Layer 3 unicast routing manager messages on Catalyst 3550 switches. This software module controls the part of the hardware that performs unicast routing. A ternary content addressable memory (TCAM) device implements the routing table.
Error Message L3TCAM-3-SIZE_CONFLICT: [chars] requires enabling extended routing.
Note
Explanation The size of the Layer 3 unicast TCAM entry is not sufficient to implement a feature. [chars] is the feature name (either Web Cache Communication Protocol [WCCP] or multiple VPN routing/forwarding [multi-VRF]) that requires the 144-bit TCAM size.
Recommended Action Modify the Switch Database Management (SDM) template to enable the switch to support the 144-bit Layer 3 TCAM. Use the sdm prefer extended-match, sdm prefer access extended-match, or sdm prefer routing extended-match global configuration command, and then reload the switch by using the reload privileged EXEC command.
Error Message L3TCAM-3-TOO_MANY_VRF: Exceed the maximum number of VRF allowed.
Note
Explanation The number of virtual private networks (VPNs) exceeds the number allowed by the VPN routing/forwarding table on this hardware platform.
Recommended Action Reconfigure your switch to limit the number of VRFs. Do not define (name) more than seven VRFs with the ip vrf vrf-name global configuration command.
Error Message L3TCAM-4-WCCP_ENABLE: Both VRF and WCCP are enabled, please remove either WCCP or VRF configuration.
Note
Explanation The switch does not support enabling of both VRF and WCCP.
Recommended Action Reconfigure your switch to use either VRF or WCCP.
LINK Messages
This section contains the Fast Ethernet link-specific messages.
Error Message LINK-3_FCS_ERROR:ASSERT [chars] [chars] FCS Error.
Note
Explanation The frame check sequence (FCS) error rate exceeds the configured FCS error rate threshold. An associated alarm is raised. The first [chars] is the user configured alarm for this fault condition. The second [chars] is the interface.
Recommended Action Verify that there is not a loose connection between the cabling and the switch. If the problem persists, call your Cisco technical support representative.
Error Message LINK-3_FCS_ERROR:CLEAR [chars] [chars] FCS Error.
Note
Explanation The frame check sequence (FCS) error rate is below the configured FCS error rate threshold. An associated alarm is cleared. The first [chars] is the user-configured alarm for this fault condition. The second [chars] is the interface.
Recommended Action No action is required.
Error Message LINK-3_LINK_FAULT:ASSERT [chars] [chars] Link Fault.
Note
Explanation There is a physical link problem. An associated alarm is raised. The first [chars] is the user-configured alarm for this fault condition. The second [chars] is the interface.
Recommended Action Verify that there is not a loose connection between the cabling and the switch. If the problem persists, call your Cisco technical support representative.
Error Message LINK-3_LINK_FAULT:CLEAR [chars] [chars] Link Fault.
Note
Explanation The previous physical link problem has been corrected. The associated alarm is cleared. The first [chars] is the user-configured alarm for this fault condition. The second [chars] is the interface.
Recommended Action No action is required.
LRE_CPE Messages
This section contains the Long-Reach Ethernet (LRE) customer premises equipment (CPE) initialization messages on Catalyst 2950 LRE switches.
Error Message LRE_CPE-3-INVALIDMODE: CPE on interface [chars] is in invalid mode [chars].
Note
Explanation The CPE is in a mode that is inconsistent with its other characteristics, such as the model number. The model number might imply a MAC mode while the CPE is in PHY mode. The first [chars] is the interface to which the CPE is connected, and the second [chars] is CPE mode.
Recommended Action Use the show controllers lre cpe mfg privileged EXEC command to verify that the Model Number field is correct. Use the hw-module slot module-slot # upgrade lre remote privileged EXEC command to ensure that the CPE has the latest supported firmware. If the CPE model number and firmware version are correct, use the shutdown interface configuration command followed by the no shutdown command to force the switch to reread CPE information. If the problem persists, contact your technical support representative.
Error Message LRE_CPE-3-INVALIDPATCH: CPE on interface [chars] has invalid LRE firmware.
Note
Explanation The LRE firmware header does not have a valid signature, or that this firmware header information is inconsistent with the firmware contents. [chars] is the interface to which the CPE is connected.
Recommended Action Upgrade the firmware on the CPE to the latest supported version by using the hw-module slot module-slot # upgrade lre remote privileged EXEC command.
Error Message LRE_CPE-3-INVALIDPHY: CPE on interface [chars] has an unsupported Ethernet PHY.
Note
Explanation The Ethernet PHY device on the CPE is not supported. This error occurs when the switch cannot recognize the PHY identifier of the PHY devices on the CPE. This error might be caused by these conditions: The software version on the switch is not compatible with this CPE, the CPE is not a Cisco-supported device, or the switch did not correctly read the PHY identifier from the CPE. [chars] is the interface to which the CPE is connected.
Recommended Action Verify that the CPE is a Cisco-supported device. Use the show controllers lre cpe mfg privileged EXEC command to verify that the Model Number field is correctly set. If the software version and CPE model number appear correct, enter the shutdown interface configuration command followed by the no shutdown command to force the switch to reread the PHY identifier. As a last resort, power cycle the CPE. If the error persists, contact your technical support representative.
Error Message LRE_CPE-3-NOVERCKSUM: Could not fetch CPE firmware version and checksum on interface [chars].
Note
Explanation The system could not obtain the CPE firmware version and checksum. If the CPE has the latest firmware and the CPE model number is correct, this error might be caused because the LRE link between the switch and the CPE is of poor quality. [chars] is the interface to which the CPE is connected.
Recommended Action Use the show controllers lre cpe mfg privileged EXEC command to verify that the Model Number field is correctly set for this CPE. Use the hw-module slot module-slot # lre upgrade remote privileged EXEC command to ensure that the CPE has the latest firmware. Use the shutdown interface configuration command followed by the no shutdown command to force the switch to get the CPE firmware version and checksum value. As a last resort, power cycle the CPE. If the problem persists, contact your technical support representative.
Error Message LRE_CPE-3-UNKNOWNMODEL: CPE has unrecognizable model number [chars] on interface [chars]
Note
Explanation The Model Number field in the CPE EEPROM output does not match a known CPE model number. The first [chars] is the CPE model number, and the second [chars] is the interface to which the CPE is connected.
Recommended Action Use the show controllers lre cpe mfg privileged EXEC command to check the CPE model number. Verify that the model number is a Cisco-supported one. Use the shutdown interface configuration command followed by no shutdown command to force the switch to get the CPE model number. If the error message persists, copy the output of the show controllers lre cpe mfg command, and contact your technical support representative.
Error Message LRE_CPE-3-WRONGAPPVER: CPE on interface [chars] reported unsupported version of application firmware [chars]. Minimum application firmware version needed [chars]
Note
Explanation Each CPE requires a supported application firmware version to function correctly. This CPE has a application firmware version that predates the earliest supported version. The first [chars] is the interface to which the CPE is connected, the second [chars] is the application firmware version, and the third [chars] is the minimum firmware version required by the CPE.
Recommended Action Application firmware is not currently used on the CPE. This error message is for future use.
Error Message LRE_CPE-3-WRONGBOOTVER: CPE on interface [chars] reported unsupported version of bootloader firmware [chars]. Minimum bootloader firmware version needed [chars]
Note
Explanation Each CPE requires a supported bootloader firmware version to function correctly. This CPE has a version that predates the earliest supported version. The first [chars] is the interface to which the CPE is connected, the second [chars] is the version of the unsupported bootloader firmware, and the third [chars] is the minimum firmware version.
Recommended Action Upgrade the bootloader firmware on the CPE to a version that supports the current requirements by using the hw-module slot module-slot # lre upgrade remote privileged EXEC command. If upgrading the CPE firmware does not solve the problem, force the switch to get the bootloader firmware version by entering the shutdown interface configuration command followed by no shutdown command. As a last resort, power cycle the CPE. If the problem persists, contact your technical support representative.
Error Message LRE_CPE-3-WRONGPATCH: CPE on interface [chars] has wrong patch version [hex]. Patch version [hex] or higher is needed for this CPE.
Note
Explanation Each CPE requires a supported patch version to function. This CPE has a patch version that predates the earliest supported version. This might occur because the switch was upgraded with the latest Cisco IOS software image, but the CPE firmware has not been upgraded. [chars] is the interface to which the CPE is connected, the first [hex] is the incorrect patch version, and the second [hex] is the minimum patch version.
Recommended Action Upgrade the CPE patch to the latest supported version by using the hw-module slot module-slot # upgrade lre remote privileged EXEC command.
Error Message LRE_CPE-5-SSNCHANGED: CPE unit on interface [chars] changed.
Note
Explanation The CPE system serial number change. This occurs when the CPE unit on the interface was replaced. [chars] is the interface to which the CPE is connected.
Recommended Action No action is required.
LRE_LINK Messages
This section contains the Long-Reach Ethernet (LRE) link messages on Catalyst 2950 LRE switches.
Error Message LRE_LINK-3-PROFILE_FAILURE: Interface [chars], profile [chars] failure
Note
Explanation When the switch reloads or when the LRE link is lost, the LRE port first tries to briefly establish a link with the CPE in a common, reduced rate mode. The switch and CPE exchange configuration information to achieve the link rate of the profile configured for the port. When the reduced rate is achieved, the link is dropped briefly, and the LRE and CPE ports attempt to establish the profile link rate. If no LRE link is established after 30 seconds, this message appears, and the port LED is amber. The port continues to try to establish a link, starting with the reduced rate. If the switch or CPE is not operating properly, this message also appears.The first [chars] is the interface to which the CPE is connected, and the second [chars] is the profile name.
Recommended Action Change the profile on the port to one that has a lower rate or has a longer reach. Too many impairments might be on the connection between the switch and the CPE for the ports to sustain the profile rate. If the switch or CPE is not operating properly, contact Cisco Systems.
Error Message LRE_LINK-3-UPDOWN: Interface [chars], changed state to [chars]
Note
Explanation The link between the LRE port and the CPE device has been lost and that no Ethernet traffic is being transferred. This could occur because the port was reconfigured, the profile that the ports uses was reconfigured, the LRE switch connector was disconnected or reconnected, the CPE LRE cable was disconnected, or the switch was power-cycled. It might also be caused by a substantial interruption of the signal or cabling between the LRE port and the CPE. The first [chars] is the interface to which the CPE is connected, and the second [chars] is the port status.
Recommended Action If the port or the profile in use is reconfigured, ignore this message. However, if the LRE link still down after a minute, the cable between the switch and the CPE might be disconnected, or the CPE might have lost power.
Error Message LRE_LINK-4-HEALTH_MON: Interface [chars], had crossed certain monitored thresholds
Note
Explanation The link status monitor for the interface has detected conditions that have crossed the configured thresholds. [chars] is the interface to which the CPE is connected.
Recommended Action Enter the show controllers lre link monitor privileged EXEC command to obtain more information on this error. If the change in operating conditions was unexpected, confirm the configuration settings for the interface.
LRE_UPGRADE Messages
This section contains the Long-Reach Ethernet (LRE) upgrade messages on Catalyst 2950 LRE switches.
Error Message LRE_UPGRADE-3-INIT_SYSTEM: Upgrade module failed to initialize
Note
Explanation The LRE upgrade module failed to initialize.
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 LRE_UPGRADE-3-LOCAL_FAILURE: Upgrade of local controller [chars] failed
Note
Explanation LRE upgrade is unable to download firmware to a local controller. [chars] is the local controller.
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 LRE_UPGRADE-4-INIT_RESOURCE: [chars]
Note
Explanation The LRE upgrade module cannot locate a required resource. [chars] is the missing resource. If the resource message is
cannot locate lre firmware files, the LRE upgrade module might not have found a directory in flash memory named flash:/lre-bin. This directory stores the LRE-related firmware files for the LRE switch and LRE CPE devices. The upgrade module cannot initialize unless this directory already exists in flash memory.Recommended Action Verify that the flash:/lre-bin directory exists. If the directory is missing, create an empty directory named flash:/lre-bin. Otherwise, report this message to your Cisco technical support representative.
Error Message LRE_UPGRADE-4-TERMINATE: Upgrade on [chars] terminated
Note
Explanation The CPE was disconnected or changed in the middle of an upgrade. [chars] is the CPE.
Recommended Action No action is required.
NETWORK_PORT_SATELLITE Messages
The section contains the network port satellite messages on Catalyst 3550 switches. 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-3-PHY_LOCKUP: Repeated phy lockup seen on [chars]. Interface will be shut down.
Note
Explanation PHY lockup was detected too many times in a row. The interface is shut down to avoid continuous link flapping.
Recommended Action To re-enable the interface, use the shutdown interface configuration command, followed by the no shutdown interface configuration command.
Error Message NETWORK_PORT_SATELLITE-6-MAC_LOCKUP: Transmit lock up is detected in [chars]. This port is administratively down.
Note
Explanation When the PHY is powered on and off, the MAC cycles from 1000 to 100 Mbps, 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. [chars] is the interface name.
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.
PBR Messages
This section contains the policy-based routing (PBR) messages on Catalyst 3550 switches.
Error Message PBR-2-NO_RMAP: Cannot create PBR data structures for route-map [chars]
Note
Explanation The PBR manager could not allocate the data structures needed to describe a route map being used for policy routing. This was probably caused by lack of available memory. [chars] is a value that is applied by using the route-map interface configuration command.
Recommended Action Use a less-complicated configuration that requires less memory.
Error Message PBR-3-NO_LABEL: Cannot allocate label for route-map [chars]
Note
Explanation The PBR manager could not allocate a label for this route map. This means that the hardware cannot be programmed to implement policy routing. There is a limit of 247 labels for policy routing. [chars] is a value that is applied by using applied the route-map interface configuration command.
Recommended Action Use a less complicated configuration that allows label sharing. If possible, use the same route maps on multiple interfaces.
Error Message PBR-3-MERGE_FAIL: [chars] ACL merge error [dec] on route-map [chars]
Note
Explanation The PBR manager could not complete the merge of the configured route map into a form suitable for loading into the hardware. The most likely cause is specifying an access control list (ACL) that is too large or too complex for the system to handle. The first [chars] is the module or feature name, and the second [chars] is a value that is applied by using the route-map interface configuration command. [dec] is an internal error code.
Recommended Action Specify a smaller and less-complicated configuration.
Error Message PBR-3-UNSUPPORTED_RMAP: Route-map [chars] not supported for Policy-Based Routing
Note
Explanation The route map attached to an interface for policy routing contains an action that is not supported on this platform. This is a hardware limitation. [chars] is a value that is applied by using the route-map interface configuration command.
Recommended Action Reconfigure the route map. Use only permit entries and set ip next-hop action in the route map.
Error Message PBR-4-CPU_SUPPORTED_ACTION: Set action in sequence [dec] of route-map [chars] supported by forwarding to CPU.
Note
Explanation The route map attached to an interface for policy routing contains an action that is not supported in hardware because it contains set interface, set ip default next-hop, set default interface or set ip df actions. The packets must be forwarded by the CPU. [dec] and [chars] are values that are applied by using the route-map interface configuration command.
Recommended Action Reconfigure the route map. If possible, use only set ip next-hop in the route map.
Error Message PBR-3-INSTALL_FAIL: Policy route-map [chars] not installed in hardware
Note
Explanation The PBR manager was unable to install the complete route map in the hardware, so this will have to be applied in software. The packets must be forwarded by the CPU. [chars] is a value that is applied by using the route-map interface configuration command.
Recommended Action Reconfigure the route map to use a simpler configuration. If possible, use the same route map on multiple interfaces.
Error Message PBR-4-RETRY_INSTALL: Route-map [chars] installed in hardware upon retry
Note
Explanation The PBR manager was able to fit the complete configuration into the hardware. One or more route maps had previously not been loaded because of lack of space. [chars] is a value that is applied by using the route-map interface configuration command.
Recommended Action No action is required.
PHY Messages
This section contains the PHY message.
Error Message PHY-4-MODULE_DUP: SFPs in [chars] and in [chars] have duplicate vendor-id and serial numbers.Explanation The small form-factor pluggable (SFP) module was identified as a Cisco SFP, but its vendor ID and serial number match that of another SFP in the system. The first [chars] is the interface in which the SFP is installed, and the second [chars] is the interface where the duplicate SFP is installed.
Recommended Action Cisco SFP modules are assigned unique serial numbers. Verify that the module was obtained from Cisco or a supported vendor. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
PLATFORM Messages
This section contains the low-level platform message. This message appears when the switch attempts to display the failure message from the previous failure.
Error Message PLATFORM-1-CRASHED: [chars]
Note
Explanation The system is attempting to display the failure message from the previous failure. [chars] is the failure message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
PLATFORM_CAT3550 Messages
This section contains the Catalyst 3550 low-level platform message. This message appears when the switch attempts to display the failure message from the previous failure.
Error Message PLATFORM_CAT3550-1-CRASHED: [chars].
Note
Explanation The system is attempting to display the failure message from the previous failure. [chars] is the failure message.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
PLATFORM_CATALYST2940 Messages
This section contains the Catalyst 2940 platform messages.
Error Message PLATFORM_CATALYST2940-3-C2940_UPLINK_SELECT: [chars] is selected as uplink port.
Note
Explanation [chars] is the enabled uplink port. A single uplink is selected at startup. The other uplink port is shut down. [chars] is the name of the enabled port.
Recommended Action No action is required.
PLATFORM_CATALYST2955 Messages
This section contains the application-specific integrated circuit (ASIC) driver-related messages on Catalyst 2955 switches.
Error Message PLATFORM_CATALYST2955-3-PORT_NOT_OPERATING: ASSERT [chars] [chars]
Note
Explanation The port is not operating and the power-on self-test (POST) has failed. An associated alarm is raised. The first [chars] is the user-configured alarm for this failure. The second [chars] is 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 PLATFORM_CATALYST2955-3-PORT_NOT_OPERATING: CLEAR [chars] [chars]
Note
Explanation The failed port is shut down. An associated alarm is cleared. The first [chars] is the user-configured alarm for this failure. The second [chars] is 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.
PLATFORM_HW Messages
This section contains the ASIC-driver-related messages.
Error Message PLATFORM_HW-3-ASIC_BIST_FAILURE: C2950 BIST failed for memory [chars] count [dec].
Note
Explanation During power-on self-test (POST), the built-in memory test on the ASIC failed, which might occur because the ASIC has a defect. [chars] is the name of the ASIC memory table, and [dec] is the number of address failures in the built-in memory test.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-ASIC_INIT_FAILURE: ASIC driver initialization has failed.
Note
Explanation One of the steps in the ASIC initialization sequence failed. This might occur because of a failure in the peripheral component interconnect (PCI) configuration setup, the Inter-IC (I2C) initialization, the built-in self-test on the ASIC, or another initialization sequence. This failure might also occur because of an ASIC defect.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-GBP_FAILURE: Unable to initialize the external packet memory.
Note
Explanation During the switch driver initialization, there was an error in the external packet memory initialization, which might occur because of a defect in the ASIC or in the external SDRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-GBP_INIT_FAILURE: GBP currently FULL or UNAVAILABLE.
Note
Explanation During the switch driver initialization, an error was detected in the external packet memory, which could be caused by a defect in the ASIC or in the external SDRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-MEM_COPY_FAILURE: Invalid copy [dec] for table [chars].
Note
Explanation There was an attempt to read or write an invalid copy of the switch internal memory. [dec] is the invalid copy number for the table, and [chars] is the name of the ASIC memory table. This is a recoverable error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-MEM_INDEX_FAILURE: Invalid index [dec] for table [chars].
Note
Explanation There was an attempt to access an invalid index of the switch internal memory. [dec] is the index number, and [chars] is the name of the ASIC memory table. This is a recoverable error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-MEM_INIT_FAILURE: The switch memory resources could not be allocated for [chars], initialization failed.
Note
Explanation During the switch driver initialization, driver-related memory resources could not be allocated, which might occur because of a hardware defect. [chars] can be asic instance, switch ports, fast-ethernet queues, or gigabit queues.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-MEM_READ_FAILURE: Read memory failed for memory [chars] at index [dec].
Note
Explanation An attempt to read a valid location in the internal chip memory failed, which might occur because of an ASIC defect. [chars] is the name of the ASIC memory table, and [dec] is the table index.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-MEM_WRITE_FAILURE: Write memory failed for memory [chars] at index [dec].
Note
Explanation An attempt to write to a location in the internal chip memory failed, which might occur because of an invalid memory location or an ASIC defect. [chars] is the name of the ASIC memory table, and [dec] is the table index.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-MIIM_OP_FAILURE: Unable to read PHY register at addr [hex] for phy id [hex].
Note
Explanation There was a failure to read from or write to a PHY register on the switch, which might occur because of a defect in the media independent interface (MII)/Gigabit media independent interface (GMII) switch interface. The first [hex] is the register address, and the second [hex] is the PHY ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-PCI_FIND_FAILURE: The number of asics expected were [dec], PCI bus scan found [dec].
Note
Explanation During the switch driver initialization, the switch found an incorrect number of ASICs on the PCI bus or did not find any ASICs with a correct PCI value. This might occur because of a system PCI bus defect or an incompatible software version running on the switch. The first [dec] is the number of ASICs that the switch should find, and the second [dec] is the actual number of ASICs that the switch found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-PCI_INIT_FAILURE: The PCI address space initialization failed.
Note
Explanation During the switch driver initialization, the PCI address space for the ASIC could not be initialized, which might occur because of a system PCI-bus problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-PCI_TEST_FAILURE: PCI address space test failed, Wrote [hex], read [hex], re-read [hex].
Note
Explanation During POST, the PCI address space for the ASIC was not mapped correctly. This might occur because of a system PCI-bus problem. The first [hex], the second [hex], and the third [hex] are test data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-REG_READ_FAILURE: Register read failed for [chars] in [chars]
Note
Explanation An attempt to read a valid location in the internal chip register failed. This could be due to a hardware defect. The first [chars] is the register identification, and the second [chars] is (what?)
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-REG_WRITE_FAILURE: Register write failed for register [chars] in [chars]
Note
Explanation An attempt to write to a location in the internal chip register failed. This might be caused by writing to an invalid register location or by a defect in the hardware. The first [chars] is the register identification, and the second [chars] is (what?)
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-SCHAN_OP_FAILURE: S-channel operation timeout for opcode [chars].
Note
Explanation There was a failure to read or write to an ASIC register or a memory location because of an ASIC internal bus failure. [chars] is the operation code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-SCHAN_READ_REG_FAILURE: S-channel operation read register failure at addr [hex].
Note
Explanation There was a failure to read the ASIC registers, which might occur because of an invalid register address or internal bus failure. [hex] is the register address.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PLATFORM_HW-3-SYSTEM_INFO_FAILURE: The board information could not be read correctly, initialization failed.
Note
Explanation During switch driver initialization, there was a failure to read the system board information, which might occur because of an ASIC problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log and enter it in the Output Interpreter tool. Enter the show tech-support privileged EXEC command to gather data that might help identify the cause of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
PLATFORM_MONITOR Messages
This section contains Catalyst 2940 low-level messages.
Note
Error Message PLATFORM_MONITOR-3-C2950MONITOR_UNKNOWN_PARAM: Unknown trap type:[dec] received in emt_call function.
Note
Explanation The trap type is unknown. [dec] is the number of a requested service.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more 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].
Note
Explanation The port manager subsystem could not obtain the memory it needed to initialize the specified operation. [chars] is the port manager operation.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-2-VLAN_ADD: Failed to add VLAN [dec] - [chars].
Note
Explanation The software failed to add the VLAN to the VLAN Trunking Protocol (VTP) database. [dec] is the VLAN ID, and [chars] specifies the reason for the failure.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-3-INTERNALERROR: Port Manager Internal Software Error ([chars]: [chars]: [dec]: [chars])
Note
Explanation There was an internal software error encountered in the Cisco IOS Port Manager. The first [chars] is the failure that occurred. The second [chars] is the source file where the failure occurred. [dec] is the line number in the file. The fourth [chars] is the name of the function in which the failure occurred.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-BAD_APP_ID: An invalid application id [dec] was detected.
Note
Explanation The port manager detected an invalid request. [dec] is the application ID.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-BAD_APP_REQ: An invalid [chars] request by the '[chars]' application was detected.
Note
Explanation his message means that the port manager detected an invalid request. The first [chars] is the invalid request, and the second [chars] is the application making the request.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-BAD_CARD_COOKIE: An invalid card cookie was detected.
Note
Explanation The port manager detected an invalid request.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-BAD_CARD_SLOT: An invalid card slot ([dec]) was detected.
Note
Explanation The port manager detected an invalid request. [dec] is the slot number.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-BAD_COOKIE: [chars] was detected.
Note
Explanation The port manager detected an invalid request. [chars] is the invalid request.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-BAD_HA_ENTRY_EVENT: Invalid Host access entry event ([dec]) is received.
Note
Explanation An invalid host access entry event was received; the host access table entry event should be an add, delete, or update event. [dec] is the event that is received.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-BAD_PORT_COOKIE: An invalid port cookie was detected.
Note
Explanation The port manager detected an invalid request.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-BAD_PORT_NUMBER: An invalid port number ([dec]) was detected.
Note
Explanation The port manager detected an invalid request. [dec] is the port number.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-BAD_VLAN_COOKIE: An invalid vlan cookie was detected.
Note
Explanation The port manager detected an invalid request.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-BAD_VLAN_ID: An invalid vlan id ([dec]) was detected.
Note
Explanation The port manager detected an invalid request. [dec] is the VLAN ID.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-ERR_DISABLE: [chars] error detected on [chars], putting [chars] in err-disable state.
Note
Explanation 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). On PoE switches, this message might appear when a device that can be powered by either a PoE switch port or by AC power is not being powered by an external AC power source and is connected to a port that has been configured with the power inline never interface configuration command. [chars] is the port where the threshold was exceeded. The first [chars] is the error, and the second and third [chars] are the affected interfaces.
Recommended Action On non-PoE switches, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error. Use the Bug Toolkit to look for similar reported problems. On PoE switches, remove the device or configure the port by entering the power inline auto, the shutdown, and the no shutdown interface configuration commands. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message PM-4-ERR_RECOVER: Attempting to recover from [chars] err-disable state on [chars].
Note
Explanation 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 Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-EXT_VLAN_INUSE: VLAN [dec] currently in use by [chars].
Note
Explanation The port manager failed to allocate the VLAN for external use because the VLAN is being used by another feature. [dec] is the VLAN that is being used, and [chars] is the feature that is using it.
Recommended Action Reconfigure the feature (for example, the routed port) to use another internal VLAN or to request another available VLAN.
Error Message PM-4-EXT_VLAN_NOTAVAIL: VLAN [dec] not available in Port Manager.
Note
Explanation The port manager failed to allocate the requested VLAN. The VLAN is probably being used as an internal VLAN by other features. [dec] is the requested VLAN.
Recommended Action Try to configure a different VLAN on the device.
Error Message PM-4-INACTIVE: putting [chars] in inactive state because [chars].
Note
Explanation The port manager has been blocked from creating a virtual port for the switch port and VLAN, causing the port to be in an inactive state. The first [chars] is the interface name. The second [chars] specifies the reason for the error message.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-INT_FAILUP: [chars] failed to come up. No internal VLAN available.
Note
Explanation The port manager failed to allocate an internal VLAN, and the interface cannot come up. [chars] is the interface name.
Recommended Action Remove the extended-range VLAN by using the no vlan vlan-id global configuration command to make resources available.
Error Message PM-4-INT_VLAN_NOTAVAIL: Failed to allocate internal VLAN in Port Manager.
Note
Explanation The port manager failed to find any available internal VLAN.
Recommended Action Delete some extended-range VLANs created by users, or remove some features (such as routed ports) that require internal VLAN allocation. To delete extended-range VLANs, use the no vlan vlan-id global configuration command. To delete a routed port, use the no switchport interface configuration command.
Error Message PM-4-INVALID_HOST_ACCESS_ENTRY: Invalid Host access entry type ([dec]) is received.
Note
Explanation An invalid host access entry type was received; the host access entry should be a configured or dynamic type. [dec] is the entry type that is received.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-LIMITS: The number of vlan-port instances on [chars] exceeded the recommended limit of [dec].
Note
Explanation The total number of individual VLAN ports, counted in the specified module or switch, has exceeded the module or switch limit specified in the error message. VLANs can be counted more than once; if VLAN 1 is carried on ten interfaces, it will count as ten VLAN ports. For some platforms, such as the Catalyst 6000, bundling is also ignored for purposes of this count; if eight interfaces on the same module are in one bundle, and the port channel is carrying VLAN 1, it will count as eight VLAN ports. [chars] is the module name (for example, switch or the module number), and [dec] is the recommended limit.
Recommended Action Reduce the number of trunks and VLANs configured in the specified module or switch. Keep the VLAN port count below the recommended limit specified in the software configuration guide. Use the show interface trunk privileged EXEC command to see the total number of trunks and VLANs.
Error Message PM-4-NO_SUBBLOCK: No PM subblock found for [chars].
Note
Explanation The port manager failed to find the subblock for this interface. [chars] is the interface name.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-TOO_MANY_APP: Application '[chars]' exceeded registration limit.
Note
Explanation The port manager detected an invalid request. [chars] is the application.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-UNKNOWN_HOST_ACCESS: Invalid Host access value ([dec]) is received.
Note
Explanation The host access table is being accessed with an invalid host access value. [dec] is the value that is received.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message PM-4-VMPS_CFG: Dynamic access VLAN [dec] same as voice vlan on [chars].
Note
Explanation The access VLAN ID on the VMPS server is the same as the voice VLAN ID on the interface. [dec] is the access VLAN ID, and [chars] is the physical interface.
Recommended Action Assign the access VLAN on the VMPS server to a different VLAN ID from the voice VLAN ID.
PORT_SECURITY Messages
This section contains the port security messages.
Error Message PORT_SECURITY-2-PSECURE_VIOLATION:Security violation occurred caused by MAC [enet] on port [chars].
Note
Explanation An unauthorized device attempted to connect on a secure port. MAC [enet] is the MAC address of the unauthorized device, and port [chars] is the secure port.
Recommended Action Identify the device that attempted to connect on the secure port. Notify your network system administrator of this condition.
Error Message PORT_SECURITY-6-ADDR_REMOVED: Address [dec]:[enet] exists on port [chars]. It has been removed from port [chars].
Note
Explanation A routed port is reconfigured as a switch port. The address in the previous switch configuration conflicts with the information in the running configuration and has been deleted. [dec]:[enet] is the MAC address of the port. [chars] is the reconfigured port.
Recommended Action No action is required.
Error Message PORT_SECURITY-6-VLAN_FULL: Vlan [dec] on port [chars] has reached its limit. Address [enet] has been removed.
Note
Explanation The voice VLAN is the same as the access VLAN and that the number of MAC addresses reached the maximum allowed on the access VLAN. The address is deleted. [dec] is the VLAN ID, [chars] is the port assigned to the voice VLAN and the access VLAN, and [enet] is the MAC address that is deleted.
Recommended Action No action is required.
Error Message PORT_SECURITY-6-VLAN_REMOVED: VLAN [dec] is no longer allowed on port [chars]. Its port security configuration has been removed.
Note
Explanation The VLAN is not allowed on the trunk port and is removed from the trunk port configuration. [dec] is the VLAN ID, and [chars] is the switch port assigned to the VLAN.
Recommended Action No action is required.
QATM Messages
This section contains the QoS and ACL TCAM manager messages on Catalyst 3550 switches. 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.
Note
Explanation Associated data could not be read from the TCAM. This error might mean a hardware failure.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message QATM-2-ASDATA_WRITE: Cannot write TCAM associated data.
Note
Explanation Associated data could not be written to the TCAM. This error might mean a hardware failure.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message QATM-2-TCAM_READ: Cannot read TCAM.
Note
Explanation The TCAM could not be read from. This error might mean a hardware failure.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message QATM-2-TCAM_WRITE: Cannot write the TCAM.
Note
Explanation The TCAM could not be written to. This error might mean a hardware failure.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message QATM-4-TCAM_LOW: TCAM resource running low for table [chars], resource type [chars], on TCAM number [dec].
Note
Explanation The TCAM resource is running low and might cause system instability. The first [chars] is the TCAM table, the second [chars] is the resource type, and [dec] is the TCAM number.
Recommended Action Avoid further configurations that might deplete the indicated TCAM resource type that is running low. Use the show tcam user EXEC command to display information about the input security access control list (ACL), the output security ACL, the QoS, or other regions of the TCAM, as shown in the message TCAM table. If possible, change to a different TCAM allocation by using the sdm prefer global configuration command to configure the template used in the Switch Database Management (SDM) resource allocation.
QM Messages
This section contains the QoS manager messages on Catalyst 3550 switches. An incorrect QoS setting causes these messages.
Error Message QM-4-ACTION_NOT_SUPPORTED: Action is not supported in policy map [chars].
Note
Explanation 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].
Note
Explanation 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].
Note
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.
Error Message QM-4-MATCH_NOT_SUPPORTED: Match type is not supported in class map [chars].
Note
Explanation 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.
Note
Explanation 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.
Error Message QM-4-POLICER_NOT_SUPPORTED: Number of policers has exceeded hardware limitation for policy map [chars].
Note
Explanation The policy-map configuration has exceeded the limitation of the hardware. 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 policers.
Error Message QM-4-POLICING_RATE_NOT_SUPPORTED: Policer configuration has exceeded hardware limitation for policy map [chars].
Note
Explanation The policy-map configuration has exceeded the limitation of the hardware. You configured a larger policing rate or burst size 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 policing rate or burst size.
Error Message QM-4-UNEXPECTED_INTERNAL_QOS_CONDITION: Unexpected internal QoS condition.
Note
Explanation An unexpected internal quality of service (QoS) condition has occurred. QoS debug can be enabled to obtain more information in case the condition recurs.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
SPAN Messages
This section contains the Switched Port Analyzer (SPAN) messages.
Error Message SPAN-3-MEM_UNAVAIL: Memory was not available to perform the SPAN operation.
Note
Explanation 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.
Note
Explanation 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].
Note
Explanation 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 the second attempt also fails, reload the switch by using the reload privileged EXEC command to complete the operation.
SPANTREE Messages
This section contains the spanning-tree messages.
Error Message SPANTREE-2-BLOCK_BPDUGUARD: Received BPDU on port [chars] with BPDU Guard enabled. Disabling port.
Note
Explanation A bridge protocol data unit (BPDU) was received on the interface specified in the error message that has the spanning-tree BPDU guard feature enabled. As a result, the interface was administratively shut down. [chars] is the interface.
Recommended Action Either remove the device sending BPDUs, or disable the BPDU guard feature. The BPDU guard feature can be locally configured on the interface or globally configured on all ports that have Port Fast enabled. After the conflict has been resolved, re-enable the interface by entering the no shutdown interface configuration command.
Error Message SPANTREE-2-BLOCK-PVID-LOCAL: Blocking [chars] on [chars] Inconsistent local vlan.
Note
Explanation The spanning-tree port associated with the listed spanning-tree instance and interface will be held in the spanning-tree blocking state until the per-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 interface, and the second [chars] is the spanning-tree instance.
Recommended Action Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the IEEE 802.1Q trunk connection. When corrected, spanning tree automatically unblocks the interfaces, as appropriate.
Error Message SPANTREE-2-BLOCK-PVID-PEER: Blocking on [chars] [chars]. Inconsistent peer vlan.
Note
Explanation 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 interface, and the second [chars] is the spanning-tree instance.
Recommended Action Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the IEEE 802.1Q trunk connection. When it is corrected, spanning tree automatically unblocks the interfaces, as appropriate.
Error Message SPANTREE-2-CHNL_MISCFG: Detected loop due to etherchannel misconfiguration of [chars] [chars]
Note
Explanation A loop that caused the misconfiguration of a channel group has been detected. An example of such a misconfiguration would be when the ports on one side of the EtherChannel either are not configured to be in the channel or failed to bundle for some reason. The other side has successfully bundled the ports into the EtherChannel.
Recommended Action Determine which local ports are involved by using the show interfaces status err-disabled privileged EXEC command, and then verify EtherChannel configuration on the remote device by using the show etherchannel summary user EXEC command on the remote device. When the configuration is corrected, enter shutdown and no shutdown interface configuration commands on the associated port-channel interface.
Error Message SPANTREE-2-LOOPGUARD_BLOCK: Loop guard blocking port [chars] on [chars].
Note
Explanation The spanning-tree message age timer has expired because no bridge protocol data units (BPDUs) were received from the designated bridge. Because this condition could be caused by a unidirectional-link failure, the interface is put into the blocking state and marked as loop-guard-inconsistent to prevent possible loops from being created. The first [chars] is the name of this port, and the second [chars] is the spanning-tree mode displayed in the show spanning-tree privileged EXEC command.
Recommended Action Enter the show spanning-tree inconsistentports privileged EXEC command to review the list of interfaces with loop-guard inconsistencies. Determine why devices connected to the listed ports are not sending BPDUs. One reason might be that they are not running the Spanning Tree Protocol (STP). If so, you should disable loop guard on the inconsistent interfaces by using the spanning-tree guard none interface configuration command or by starting STP on the remote side of the links.
Error Message SPANTREE-2-LOOPGUARD_CONFIG_CHANGE: Loop guard [chars] on port [chars] on [chars].
Note
Explanation The spanning-tree loop-guard configuration for the listed interface has been changed. If enabled, the interface is placed into the blocking state. It is marked as loop-guard-inconsistent when the message-age timer expires because no BPDUs were received from the designated bridge. This feature is mainly used to detect unidirectional links. The first [chars] is the loop-guard state (enable or disable), the second [chars] is the interface name, and the third [chars] is the spanning-tree instance.
Recommended Action Verify that this is the desired configuration for the listed interface. Correct it if this is not the desired configuration; otherwise, no further action is required.
Error Message SPANTREE-2-LOOPGUARD_UNBLOCK: Loop guard unblocking port [chars] on [chars].
Note
Explanation The listed interface has received a BPDU, and, therefore, if the inconsistency was caused by a unidirectional link failure, the problem no longer exists. The loop-guard-inconsistency is cleared for the interface, which is taken out of the blocking state, if appropriate. The first [chars] is the name of this port, and the second [chars] is the spanning-tree mode displayed in the show spanning-tree privileged EXEC command.
Recommended Action No action is required.
Error Message SPANTREE-2-PVSTSIM_FAIL: Superior PVST BPDU received on VLAN [dec] port [chars], claiming root [dec]:[enet]. Invoking root guard to block the port.
Note
Explanation When a per-VLAN spanning-tree plus (PVST+) switch is connected to a Multiple Spanning Tree Protocol (MSTP) switch, the internal spanning-tree (IST) root (MST00) becomes the root for all PVST+ spanning trees. A loop might be created if any of the PVST+ spanning trees have a better root than the IST. To prevent the loop, the port on the MSTP switch that receives the superior message from the PVST+ side is blocked by root guard. The first [dec] is the VLAN ID, [chars] is the port name, and [dec]:[enet] is the priority and MAC address.
Recommended Action When STP is converging after a new switch or switch port is added to the topology, this condition might happen transiently, and the port automatically unblocks in these cases. If the port remains blocked, identify the root bridge as reported in the message, and configure a priority for the VLAN spanning tree so that it is not selected as the root. There could be other superior PVST+ roots (lower bridge ID, lower path cost, and so forth) than the message shows, and the port does not recover until all such roots are cleared. If you are unsure, disable and re-enable the port.
Error Message SPANTREE-2-RECV-1Q-NON-1QTRUNK: Received 802.1Q BPDU on non 802.1Q trunk [chars] [chars].
Note
Explanation The listed interface on which a Shared Spanning Tree Protocol (SSTP) BPDU was received was in trunk mode but was not using IEEE 802.1Q encapsulation. The first [chars] is the port, and the second [chars] is the VLAN.
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). If the encapsulation types are different, use the switchport trunk encapsulation interface configuration command to make them consistent. When the encapsulation is consistent, spanning tree automatically unblocks the interface.
Error Message SPANTREE-2-RECV-BAD-TLV: Received SSTP BPDU with bad TLV on [chars] [chars].
Note
Explanation The listed interface received a Shared Spanning Tree Protocol (SSTP) bridge protocol data unit (BPDU) without the VLAN ID tag. The BPDU is discarded. The first [chars] is the port, and the second [chars] is the VLAN that received the SSTP BPDU.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message SPANTREE-2-RECV-PVID-ERR: Received BPDU with inconsistent peer vlan id [dec] on [chars] [chars].
Note
Explanation 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 IEEE 802.1Q trunk. [dec] is the VLAN ID, the first [chars] is the port, and the second [chars] is the VLAN.
Recommended Action Verify that the configurations of the native VLAN ID are consistent on the interfaces on each end of the IEEE 802.1Q trunk connection. When the configurations are consistent, spanning tree automatically unblocks the interfaces.
Error Message SPANTREE-2-ROOTGUARD_BLOCK: Root guard blocking port [chars] on [chars].
Note
Explanation On the listed interface a BPDU was received that advertises a superior spanning-tree root bridge (lower bridge ID, lower path cost, and so forth) than that in use. The interface is put into blocking state and marked as root-guard inconsistent to prevent a suboptimal spanning-tree topology from forming. The first [chars] is the name of this port, and the second [chars] is the spanning-tree instance on which this port was blocked.
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. When 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].
Note
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 (lower bridge ID, lower path cost, and so forth) to that already in use causes the interface to be put into the blocking state and marked as root-guard inconsistent. The first [chars] is the root-guard state (enable or disable), the second [chars] is the interface, and the third [chars] is the spanning-tree instance.
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].
Note
Explanation The listed interface is no longer receiving BPDUs advertising a superior root bridge (lower bridge ID, lower path cost, and so forth). The root-guard inconsistency is cleared for the interface, and the blocking state is removed from the interface. The first [chars] is the name of this port, and the second [chars] is the spanning-tree instance on which this port was blocked.
Recommended Action No action is required.
Error Message SPANTREE-2-UNBLOCK-CONSIST-PORT: Unblocking [chars] on [chars]. Port consistency restored.
Note
Explanation The port VLAN ID or port type inconsistencies have been resolved and that spanning tree will unblock the listed interface of the listed spanning-tree instance as appropriate. The first [chars] is the interface, and the second [chars] is the spanning-tree instance.
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).
Note
Explanation An error caused the platform-specific code to request more or fewer bits than are allowed. The spanning-tree port identifier is a 16-bit field. That 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 the 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 does not change. The first [dec] is the number of bits for the port number, and the second and third [dec] describe the valid range.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message SPANTREE-3-PORT_SELF_LOOPED: [chars] disabled.- received BPDU src mac [enet] same as that of interface.
Note
Explanation 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, and [enet] is the source MAC address.
Recommended Action Check the interface configuration and any cable connected to the interface. When the problem is resolved, re-enable the interface by entering the no shutdown interface configuration command.
Error Message SPANTREE-3-PRESTD_NEIGH: pre-standard MST interaction not configured ([chars]).
Note
Explanation The message means that the switch has received a prestandard multiple spanning-tree (MST) BPDU on an interface that is not configured to send prestandard MST BPDUs. The switch automatically adjusts its configuration on the interface and start sending prestandard BPDUs. However, the switch does not automatically detect all prestandard neighbors, and we recommended that you configure the interface to send prestandard MST BPDUs by using the spanning-tree mst pre-standard interface configuration command. This warning message only appears once. [chars] is the interface. [chars} is the interface.
Recommended Action Use the spanning-tree mst pre-standard interface configuration command on all the interfaces to which other switches running Cisco's prestandard MST version are connected. We recommended that you migrate all the switches in the network to the IEEE MST standard version.
Error Message SPANTREE-4-PORT_NOT_FORWARDING: [chars] [chars] [chars] [chars]
Note
Explanation The port is not forwarding packets; that is, it is not in a forwarding state. The first [chars] is the error severity. The second [chars] is the port. The third [chars] is the interface. The fourth [chars] is the status of the interface.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message SPANTREE-4-PORT_NOT_FORWARDING: [chars] [chars] [chars]
Note
Explanation The port is not forwarding packets or is not in a forwarding state. The first [chars] is the alarm ASSERT or CLEAR action. The second [chars] is the user-configured alarm for this fault condition. The third [chars] is 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 SPANTREE-4-PORT_NOT_FORWARDING: ASSERT MINOR [char] Port Not Forwarding.
Note
Explanation The port is not forwarding packets; that is, it is not in a forwarding state. [char] is the port.
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 SPANTREE-5-EXTENDED_SYSID: Extended SysId [chars] for type [chars].
Note
Explanation The extended system ID feature is either enabled or disabled for the given type of spanning tree. If enabled, the spanning-tree instance identifier is stored in the lower portion of the bridge ID priority field and limits the allowed values for the bridge priority from 0 to 61440, in increments of 4096. If disabled, the bridge ID priority field consists only of the configured priority, but some spanning-tree features might not be available on a given platform (for example, support for 4096 VLANs). On some platforms, the extended system ID feature might be mandatory. The first [chars] is the extended system ID state (enable or disable), and the second [chars] is the spanning-tree instance.
Recommended Action No action is required.
Error Message SPANTREE-6-PORT_STATE: Port [chars] instance [dec] moving from [chars] to [chars].
Note
Explanation The state of the port changed.
Recommended Action No action is required.
Error Message SPANTREE-7-BLOCK-PORT-TYPE: Blocking [chars] on [chars]. Inconsistent port type.
Note
Explanation The listed interface is being held in the spanning-tree blocking state until the port-type inconsistency is resolved. The first [chars] is the interface, and the second [chars] is the spanning-tree instance.
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].
Note
Explanation An SSTP bridge protocol data units (BPDU) was received on the listed interface, which is not an operational trunking interface. The first [chars] is the port name, and the second [chars] is the VLAN name.
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 message.
Error Message SPANTREE_FAST-7-PORT_FWD_UPLINK: [chars] [chars] moved to Forwarding (UplinkFast).
Note
Explanation 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 spanning-tree instance, and the second [chars] is the interface.
Recommended Action No action is required.
SPANTREE_VLAN_SWITCH Messages
The section contains the per-VLAN spanning-tree-specific message.
Error Message SPANTREE_VLAN_SW-2-MAX_INSTANCE: Platform limit of [dec] STP instances exceeded. No instance created for [chars] (port [chars]).
Note
Explanation 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, and the first [chars] is the lowest VLAN ID 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 generate this message.
STORM_CONTROL Messages
This section contains the storm control messages.
Error Message STORM_CONTROL-2-SHUTDOWN: Storm control shut down [chars].
Note
Explanation Excessive traffic has been detected on a port that has been configured to be shut down if a storm event is detected. [chars] is the physical interface.
Recommended Action When the source of the packet storm has been fixed, re-enable the port by using the no shutdown interface configuration command.
SW_VLAN Messages
This section contains the VLAN manager messages. The VLAN manager receives information from the 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].
Note
Explanation 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 Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message SW_VLAN-3-VTP_PROTOCOL_ERROR: VTP protocol code internal error:[chars].
Note
Explanation 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 Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more 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].
Note
Explanation The VLAN manager received an upcall and a VLAN cookie from the port manager, which translated to a bad VLAN ID. [dec] is the VLAN ID.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message SW_VLAN-4-BAD_STARTUP_VLAN_CONFIG_FILE: Failed to configure VLAN from startup-config. Fallback to use VLAN configuration file from non-volatile memory.
Note
Explanation The VLAN software did not use the VLAN configuration from the startup-configuration file. It will use the binary VLAN configuration file in NVRAM.
Recommended Action No action is required.
Error Message SW_VLAN-4-BAD_VLAN_CONFIGURATION_FILE: VLAN configuration file contained incorrect verification word:[hex].
Note
Explanation The VLAN configuration file read by the VLAN manager did not begin with the correct value. The VLAN configuration file is invalid, and it has been rejected. [hex] is the incorrect verification value.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message SW_VLAN-4-BAD_VLAN_CONFIGURATION_FILE_VERSION: VLAN configuration file contained unknown file version:[dec].
Note
Explanation 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 Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message SW_VLAN-4-BAD_VLAN_TIMER_ACTIVE_VALUE: Encountered incorrect VLAN timer active value:[chars].
Note
Explanation 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 Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message SW_VLAN-4-EXT_VLAN_CREATE_FAIL: Failed to create VLANs [chars]: [chars].
Note
Explanation The software failed to create VLANs. The first [chars] is the Layer 2 VLAN list, and the second [chars] describes the reason for the failure.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message SW_VLAN-4-EXT_VLAN_INTERNAL_ERROR: Extended VLAN manager received an internal error [dec] from [chars]: [chars].
Note
Explanation An unexpected error code was received by the VLAN manager from the extended-range VLAN configuration software. [dec] is the error code. The first [chars] is the function, and the second [chars] describes the error code.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message SW_VLAN-4-EXT_VLAN_INVALID_DATABASE_DATA: Extended VLAN manager received bad data of type [chars]: value [dec] from function [chars].
Note
Explanation Invalid data was received by the extended-range VLAN manager from an extended-range VLAN configuration database routine. The first [chars] is the data type, [dec] is the number received, and the second [chars] is the function name.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message SW_VLAN-4-IFS_FAILURE: VLAN manager encountered file operation error: call = [chars] / file = [chars] / code = [dec] ([chars]) / bytes transferred = [dec].
Note
Explanation The VLAN manager received an unexpected error return from a Cisco IOS file system (IFS) call while reading the VLAN database. The first [chars] is the name of the function call, and the second [chars] is the file name. [dec] is the error code, the third [chars] is the textual interpretation of the error code, and the second [dec] is the number of bytes transferred.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more 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].
Note
Explanation 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 Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message SW_VLAN-4-STARTUP_EXT_VLAN_CONFIG_FILE_FAILED: Failed to configure extended range VLAN from startup-config. Error [chars].
Note
Explanation The VLAN software failed to use an extended-range VLAN configuration from the startup configuration file. All extended-range VLAN configurations are lost after the system boots up. [chars] is a description of the error code.
Recommended Action No action is required.
Error Message SW_VLAN-4-VTP_INTERNAL_ERROR: VLAN manager received an internal error [dec] from vtp function [chars]:[chars].
Note
Explanation 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 Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more 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].
Note
Explanation 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 Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more 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.
Note
Explanation 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 Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message SW_VLAN-4-VTP_SEM_BUSY: VTP semaphore is unavailable for function [chars]. Semaphore locked by [chars].
Note
Explanation The VTP database is currently locked by another task and is not available. Retry the operation later. [chars] is the name of the function that has locked the VTP database.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message SW_VLAN-4-VTP_USER_NOTIFICATION: VTP protocol user notification: [chars].
Note
Explanation The VTP code encountered an unusual diagnostic situation. [chars] is a description of the situation.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more 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.
Note
Explanation 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].
Note
Explanation 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-0-STOPPED: UDLD process stopped: [chars]
Note
Explanation The UDLD process stopped because it cannot read the unique system identifier that UDLD uses. The system identifier identifies the device that is sending the UDLD packets. [chars] is the system identifier.
Recommended Action Reload the switch by using the reload privileged EXEC command. If the problem persists, enter the show tech-support privileged EXEC command to gather data that might provide information about the error and call your Cisco technical support representative.
Error Message UDLD-3-UDLD_IDB_ERROR: UDLD error handling [chars] interface:[chars].
Note
Explanation 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.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message UDLD-3-UDLD_INTERNAL_ERROR: UDLD internal error:[chars].
Note
Explanation A software check failed during UDLD processing. [chars] describes the internal error.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message UDLD-3-UDLD_INTERNAL_IF_ERROR: UDLD internal error, interface [chars]:[chars].
Note
Explanation A software check failed during UDLD processing. The first [chars] is the interface, and the second [chars] is a description of the error.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface [chars], [chars] detected.
Note
Explanation 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, and the second [chars] is the error detected.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message UDLD-6-UDLD_PORT_RESET: UDLD reset interface [chars].
Note
Explanation The UDLD Protocol detected a unidirectional connection between neighbors. 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] is the interface.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
UFAST_MCAST_SW Messages
This section contains the UplinkFast multicast software (UFAST_MCAST_SW) messages. The switch sends these messages when UplinkFast is enabled, a new root port takes over, and fast relearn multicast packets are not sent.
Error Message UFAST_MCAST_SW-3-PROC_START_ERROR: No process available for transmitting UplinkFast packets.
Note
Explanation No process is available for sending UplinkFast packets.
Recommended Action Reload the switch by using the reload privileged EXEC command. If this problem continues after you reload the switch, enter the show tech-support 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 or from the show tech-support command display, see the "Error Message Traceback Reports" section for more information.
Error Message UFAST_MCAST_SW-4-MEM_NOT_AVAILABLE: No memory is available for transmitting UplinkFast packets on Vlan [dec].
Note
Explanation No memory is available for sending UplinkFast packets on VLAN [dec]. [dec] is the VLAN ID.
Recommended Action Reduce other system activity to reduce memory demands.
VQPCLIENT Messages
This section contains VLAN Query Protocol (VQP) client messages on Catalyst 3550 switches.
Error Message VQPCLIENT-2-CHUNKFAIL: Could not allocate memory for VQP
Note
Explanation An error occurred when the system tried to allocate memory for the VQP client.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message VQPCLIENT-2-INITFAIL: Platform-specific VQP initialization failed. Quitting
Note
Explanation An error occurred during initialization of the VQPC platform-specific code.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message VQPCLIENT-2-IPSOCK: Could not obtain IP socket
Note
Explanation An error occurred when the system attempted to open an IP socket to the VLAN membership policy server (VMPS).
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
Error Message VQPCLIENT-2-PROCFAIL: Could not create process for VQP. Quitting
Note
Explanation An error occurred while a VQP client process was being created.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
