Catalyst 3750, 3560, 3550, 2975, 2970, and 2960 Switch System Message Guide Cisco IOS Release 12.2(46)SE and Release 12.2(46)EX November 2008 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
C O N T E N T S Preface vii Audience Purpose i-vii i-vii Conventions i-vii Related Publications i-viii Obtaining Documentation, Obtaining Support, and Security Guidelines CHAPTER 2 System Message Overview 2-1 How to Read System Messages 2-1 Error Message Traceback Reports Output Interpreter 2-7 Bug Toolkit 2-7 Contacting TAC 2-7 CHAPTER 3 2-7 Message and Recovery Procedures ACLMGR Messages 3-1 3-3 AUTOQOS Messages 3-8 BACKUP_INTERFACE Messages 3-8 BADTRANSCEIVER Messages BSPATCH Me
Contents EXPRESS_SETUP Messages FM Messages 3-34 3-35 FRNTEND_CTRLR Messages GBIC Messages 3-44 3-45 GBIC_SECURITY Messages 3-48 GBIC_SECURITY_CRYPT Messages 3-51 GBIC_SECURITY_UNIQUE Messages GIGASTACK Messages 3-53 HARDWARE Messages 3-54 HLFM Messages 3-52 3-56 HPSECURE Messages IDBMAN Messages 3-57 3-58 IGMP_QUERIER Messages ILPOWER Messages 3-61 3-62 IMAGEMGR Messages 3-69 IP_DEVICE_TRACKING_HA Messages L2TM Messages 3-71 L3TCAM Messages 3-71 MAC_LIMIT Messages 3-72 MAC_MO
Contents PLATFORM_UCAST Messages 3-92 PLATFORM_VLAN Messages 3-95 PLATFORM_WCCP Messages 3-96 PM Messages 3-97 PORT_SECURITY Messages QATM Messages QM Messages 3-107 3-108 QOSMGR Messages RMON Messages SDM Messages 3-105 3-111 3-117 3-118 SPAN Messages 3-118 SPANTREE Messages 3-119 SPANTREE_FAST Messages 3-127 SPANTREE_VLAN_SW Messages STACKMGR Messages 3-127 STORM_CONTROL Messages SUPERVISOR Messages SUPQ Messages 3-130 3-131 3-131 SW_DAI Messages 3-134 SW_MACAUTH Messages SW_M
Contents Catalyst 3750, 3560, 3550, 2975, 2970, and 2960 Switch System Message Guide vi OL-8551-04
Preface Audience This guide is for the networking professional managing the Catalyst 3750, 3560, 3550, 2975, 2970, and 2960 switch or switch stack, hereafter referred to as the switch. Before using this guide, you should have experience working with the Cisco IOS software and the switch software features. Purpose This guide describes only the Catalyst 3750, 3560, 3550, 2975, 2970, and 2960 switch-specific system messages that you might encounter.
Preface Related Publications Interactive examples use these conventions: • Terminal sessions and system displays are in screen font. • Information you enter is in boldface • Nonprinting characters, such as passwords or tabs, are in angle brackets (< >). screen font. Notes use this convention and symbol: Note Means reader take note. Notes contain helpful suggestions or references to materials not in this manual.
Preface Related Publications See these documents for other information about the switch: • Release Notes for the Catalyst 3750, 3560, 3550, 2970, and 2960 Switches • Catalyst 3750, 3560, 3550, 2970, and 2960 Switch System Message Guide • Catalyst 3750 Switch Software Configuration Guide • Catalyst 3750 Switch Command Reference • Catalyst 3750 Switch Hardware Installation Guide • Catalyst 3750 Switch Getting Started Guide • Regulatory Compliance and Safety Information for the Catalyst 3750 Swit
Preface Obtaining Documentation, Obtaining Support, and Security Guidelines • Cisco CWDM GBIC and CWDM SFP Installation Note • Cisco RPS 300 Redundant Power System Hardware Installation Guide • Cisco RPS 675 Redundant Power System Hardware Installation Guide • For information about the Network Admission Control (NAC) features, see the Network Admission Control Software Configuration Guide (Not orderable but available on Cisco.
CH A P T E R 2 System Message Overview This guide describes the Catalyst 3750, 3560, 3550, 2975, 2970, and 2960-specific system messages. During operation, the system software sends these messages to the console (and, optionally, to a logging server on another system). Not all system messages indicate problems with your system. Some messages are purely informational, whereas others can help diagnose problems with communications lines, internal hardware, or the system software.
Chapter 2 System Message Overview How to Read System Messages Table 2-1 Facility Codes Facility Code Description Location ACLMGR ACL manager “ACLMGR Messages” section on page 3-3 AUTOQOS Automatic quality of service (auto-QoS) (only Catalyst 3550 switches) “AUTOQOS Messages” section on page 3-8 BACKUP_INTERFACE Flex Links “BACKUP_INTERFACE Messages” section on page 3-8 BADTRANSCEIVER Defective transceiver messages (only 3750 and 2975 switches) “BADTRANSCEIVER Messages” section on page 3-9
Chapter 2 System Message Overview How to Read System Messages Table 2-1 Facility Codes (continued) Facility Code Description Location GBIC_SECURITY_UNIQUE GBIC and SFP module security “GBIC_SECURITY_UNIQUE Messages” section on page 3-52 GIGASTACK GigaStack GBIC module (Catalyst 3550 switch only) “GIGASTACK Messages” section on page 3-53 HARDWARE Hardware “HARDWARE Messages” section on page 3-54 HLFM Local forwarding manager “HLFM Messages” section on page 3-56 HPSECURE Port security “HP
Chapter 2 System Message Overview How to Read System Messages Table 2-1 Facility Codes (continued) Facility Code Description Location PLATFORM_PM Platform port manager “PLATFORM_PM Messages” section on page 3-88 PLATFORM_RPC Platform remote procedure call (only Catalyst 3750 and 2975 switches) “PLATFORM_RPC Messages” section on page 3-89 PLATFORM_SPAN Platform Switched Port Analyzer “PLATFORM_SPAN Messages” section on page 3-91 PLATFORM_UCAST Platform unicast routing “PLATFORM_UCAST Messa
Chapter 2 System Message Overview How to Read System Messages Table 2-1 Facility Codes (continued) Facility Code Description Location SW_MATM Mac address table manager (only Catalyst 3550 switches) “SW_MATM Messages” section on page 137 SWITCH_QOS_TB QoS trusted boundary “SWITCH_QOS_TB Messages” section on page 3-145 TCAMMGR Ternary content addressable memory manager “TCAMMGR Messages” section on page 3-145 UDLD UniDirectional Link Detection “UDLD Messages” section on page 3-147 UFAST_MCA
Chapter 2 System Message Overview How to Read System Messages Table 2-3 Representation of Variable Fields in Messages Representation Type of Information [dec] Decimal integer [char] Single character [chars] Character string [enet] Ethernet address (for example, 0000.FEED.
Chapter 2 System Message Overview Error Message Traceback Reports Error Message Traceback Reports Some messages describe internal errors and contain traceback information. This information is very important and should be included when you report a problem to your technical support representative. This message example includes traceback information: -Process= "Exec", level= 0, pid= 17 -Traceback= 1A82 1AB4 6378 A072 1054 1860 Some system messages ask you to copy the error messages and take further action.
Chapter 2 System Message Overview Error Message Traceback Reports Catalyst 3750, 3560, 3550, 2975, 2970, and 2960 Switch System Message Guide 2-8 OL-8551-04
CH A P T E R 3 Message and Recovery Procedures This chapter describes the Catalyst 3750, 3560, 3550, 2975, 2970, and 2960 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.
Chapter 3 Message and Recovery Procedures • GBIC_SECURITY_CRYPT Messages, page 3-51 • GBIC_SECURITY_UNIQUE Messages, page 3-52 • GIGASTACK Messages, page 3-53 (only Catalyst 3550 switches) • HARDWARE Messages, page 3-54 • HLFM Messages, page 3-56 • HPSECURE Messages, page 3-57 (only Catalyst 3750 and 2975 switches) • IDBMAN Messages, page 3-58 • IGMP_QUERIER Messages, page 3-61 • ILPOWER Messages, page 3-62 • IMAGEMGR Messages, page 3-69 (only Catalyst 3750 and 2975 switches) • IP_DEV
Chapter 3 Message and Recovery Procedures ACLMGR Messages • SDM Messages, page 3-118 (only Catalyst 3750 and 2975 switches) • SPAN Messages, page 3-118 • SPANTREE Messages, page 3-119 • SPANTREE_FAST Messages, page 3-127 • SPANTREE_VLAN_SW Messages, page 3-127 • STACKMGR Messages, page 3-127 (only Catalyst 3750 and 2975 switches) • STORM_CONTROL Messages, page 3-130 • SUPERVISOR Messages, page 3-131 • SUPQ Messages, page 3-131 • SW_DAI Messages, page 3-133 (only Catalyst 3750 and 3560 s
Chapter 3 Message and Recovery Procedures ACLMGR Messages Error Message ACLMGR-2-NOVMR: Cannot generate hardware representation of access list [chars] Explanation There are insufficient resources available to create a hardware representation of the ACL. A lack of available logical operation units or specialized hardware resources can cause this problem. Logical operation units are needed for a TCP flag match or a test other than eq (ne, gt, lt, or range) on TCP, UDP, or SCTP port numbers.
Chapter 3 Message and Recovery Procedures ACLMGR Messages Error Message ACLMGR-3-IECPORTLABELERROR: ACL labels are out-of-sync on interface [chars], label [dec] is not available on asic [dec]. Explanation An internal software error has occurred. [chars] is the interface name. The first [dec] is the label associated with the ACL, and the second [dec] is the ASIC number. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 3 Message and Recovery Procedures ACLMGR Messages Error Message ACLMGR-3-MAXRECURSION: Too many ([dec]) levels of recursion while merging ACLs (code [dec]). 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. The second [dec] is an internal code number of the merge stage that encountered the problem.
Chapter 3 Message and Recovery Procedures ACLMGR Messages Error Message ACLMGR-3-PACLTTABLE: Not in truth table: IPSrcGrd [dec] PACL [dec]. Note This message applies to the Catalyst 3750 and 3560 switches. Explanation An unrecoverable software error occurred while trying to merge the configured port ACL features. The first [dec] is the action specified by IP source guard, and the second [dec] is the action specified by the port ACL.
Chapter 3 Message and Recovery Procedures AUTOQOS Messages Error Message ACLMGR-3-UNLOADING: Unloading [chars] label [dec] feature. Explanation The ACL manager was unable to fit the complete configuration into the hardware, so some features will be applied in software. This prevents some or all of the packets in a VLAN from being forwarded in hardware and requires them to be forwarded by the CPU. Multicast packets might be dropped entirely instead of being forwarded.
Chapter 3 Message and Recovery Procedures BADTRANSCEIVER Messages BADTRANSCEIVER Messages This section contains the BADTRANSCEIVER message. Error Message BADTRANSCEIVER, PHY, LOG_WARNING: An innapropriate transceiver has been inserted in interface [chars]. Note This message applies only to Catalyst 3750 and 2975 switches. Explanation A defective module is installed in the specified interface. [chars] is the interface. Recommended Action Remove the transceiver.
Chapter 3 Message and Recovery Procedures CFGMGR Messages Error Message BSPATCH-3-FAILED: Failed to install Boot Loader patch ([chars]). Note This message apply only to Catalyst 3750, 3560, and 2970 switches. Explanation The switch failed to apply a boot loader patch. [chars] is the SDRAM refresh timer register setting. 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.
Chapter 3 Message and Recovery Procedures CFGMGR Messages Error Message CFGMGR-1-UNABLE_TO_SEND_STARTUP_CFG: unable to send startup-cfg, bits: [hex], retrying... Note This message applies only to Catalyst 3750 and 2975 switches. Explanation The system is unsuccessfully attempting to distribute the startup configuration file to the stack member switches. [hex] is the bit representation of the switch number.
Chapter 3 Message and Recovery Procedures CFGMGR Messages Explanation The switch type of the specified switch does not match the provisioned configuration for its switch number; therefore, the default configuration is applied to this switch. [dec] is the stack member number. Recommended Action No action is required. Error Message CFGMGR-6-APPLYING_RUNNING_CFG: as new master. Note This message applies only to Catalyst 3750 and 2975 switches.
Chapter 3 Message and Recovery Procedures CMP Messages Error Message CFGMGR-6-UNABLE_TO_NVGEN_RUNNING_CFG: config file too large... Note This message applies only to Catalyst 3750 and 2975 switches. Explanation The stack master is unable to generate the stack running configuration because the configuration file is too large. Recommended Action Remove some configuration commands. CMP Messages This section contains the Cluster Membership Protocol (CMP) messages.
Chapter 3 Message and Recovery Procedures DHCP_SNOOPING Messages Error Message CMP-5-MGMT_VLAN_CHNG: The management vlan has been changed to [dec]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation The management VLAN has changed. [dec] is the new management VLAN ID. Recommended Action No action is required.
Chapter 3 Message and Recovery Procedures DHCP_SNOOPING Messages Error Message DHCP_SNOOPING-4-AGENT_OPERATION_FAILED_N: DHCP snooping binding transfer failed ([dec]). [chars]. 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.
Chapter 3 Message and Recovery Procedures DHCP_SNOOPING Messages Error Message DHCP_SNOOPING-4-NTP_NOT_RUNNING: NTP is not running; reloaded binding lease expiration times are incorrect. 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.
Chapter 3 Message and Recovery Procedures DHCP_SNOOPING_CAT3550 Messages Error Message DHCP_SNOOPING-6-INTERFACE_NOT_VALID: Interface not valid. [dec] bindings ignored. 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.
Chapter 3 Message and Recovery Procedures DOT1Q_TUNNELLING Messages Error Message DHCP_SNOOPING_CAT3550-3-UNEXPECTED_EVENT: Process received unknown event (major [hex], minor [hex]). Note This message applies to only Catalyst 3550 switches. Explanation A process received an event it was unable to handle.
Chapter 3 Message and Recovery Procedures DOT1X_SWITCH Messages Error Message DOT1X-4-PROC_START_ERR: Dot1x unable to start. Explanation The system failed to start the IEEE 802.1x process. 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. Explanation The IEEE 802.
Chapter 3 Message and Recovery Procedures DOT1X_SWITCH Messages Error Message DOT1X_SWITCH-5-ERR_INVALID_PRIMARY_VLAN: Attempt to assign primary VLAN [dec] to 802.1x port [chars] Explanation An attempt was made to assign a primary VLAN to an IEEE 802.1x port, which is not allowed. [dec] is the VLAN, and [chars] is the port. Recommended Action Update the configuration to use a different VLAN.
Chapter 3 Message and Recovery Procedures DOT1X_SWITCH Messages Error Message DOT1X_SWITCH-5-ERR_VLAN_EQ_MDA_INACTIVE: Multi-Domain Authentication cannot activate because Data and Voice VLANs are the same on port [chars] Explanation Multi-Domain Authentication host mode cannot start if the configured data VLAN on a port is the same as the voice VLAN. [chars] is the port. Recommended Action Change either the voice VLAN or the access VLAN on the interface so that they are not equal.
Chapter 3 Message and Recovery Procedures DOT1X_SWITCH Messages Error Message DOT1X_SWITCH-5-ERR_VLAN_ON_ROUTED_PORT: Dot1x cannot assign a VLAN [dec] to a routed port [chars] Explanation An attempt was made to assign a VLAN to a supplicant on a routed port, which is not allowed. [dec] is the VLAN ID and [chars] is the port. Recommended Action Either disable the VLAN assignment, or change the port type to a nonrouted port.
Chapter 3 Message and Recovery Procedures DTP Messages 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. Explanation The system is unable to negotiate trunks because of a lack of memory. Recommended Action Reduce other system activity to ease memory demands. Error Message DTP-4-TMRERR: An internal timer error occurred when trunking on interface [chars].
Chapter 3 Message and Recovery Procedures DWL Messages Error Message DTP-5-NONTRUNKPORTON: Port [chars] has become non-trunk. Explanation The interface changed from a trunk port to an access port. [chars] is the interface that changed. Recommended Action This message is provided for information only. Error Message DTP-5-TRUNKPORTCHG: Port [chars] has changed from [chars] trunk to [chars] trunk. Explanation The encapsulation type of the trunk port has changed.
Chapter 3 Message and Recovery Procedures EC Messages 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]. Explanation Either the LACP or the PAgP EtherChannel could not obtain the memory it needed to initialize the required data structures. [chars] is the data structure name.
Chapter 3 Message and Recovery Procedures EC Messages Error Message EC-5-CANNOT_BUNDLE2: [chars] is not compatible with [chars] and will be suspended ([chars]). Explanation The interface has different interface attributes than the other ports in the EtherChannel. For the interface to join the bundle (EtherChannel), change the interface attributes to match the EtherChannel attributes.
Chapter 3 Message and Recovery Procedures EC Messages Error Message EC-5-ERRPROT2: Command rejected: the interface [chars] is already part of a channel with a different type of protocol enabled. Explanation The interface cannot be selected for the specified protocol because it is already part of a channel with a different type of protocol enabled. [chars] is the interface. Recommended Action Remove the interface from the channel group.
Chapter 3 Message and Recovery Procedures EC Messages Error Message EC-5-L3STAYDOWN: [chars] will remain down as its port-channel [chars] is admin-down. Note This message applies only to Catalyst 3550 switches. Explanation On Layer 3 interfaces and aggregation interfaces, the administrative state of the aggregation interface overrides the administrative status of the Layer 3 interface.
Chapter 3 Message and Recovery Procedures ENVIRONMENT Messages Error Message EC-5-STAYDOWN: no-shut not allowed on [chars]. Module [dec] not online. Explanation An interface with an EtherChannel configuration cannot be enabled by using the no shutdown interface configuration command because 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.
Chapter 3 Message and Recovery Procedures ETHCNTR Messages 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 If a multiple-fan failure is causing the switch to overheat, replace the switch.
Chapter 3 Message and Recovery Procedures ETHCNTR Messages Error Message ETHCNTR-3-HALF_DUX_COLLISION_EXCEED_THRESHOLD: Collision at [chars] exceed threshold. Consider as loop-back. Explanation The collisions at a half-duplex port exceeded the threshold, and the port is treated as a loopback.
Chapter 3 Message and Recovery Procedures ETHCNTR Messages Error Message ETHCNTR-3-LOOP_BACK_DETECTED:, Loop-back detected on [chars]. The port is forced to linkdown. Explanation This message occurs when a keepalive packet is looped back to the port that sent the keepalive. The loopback condition might be caused by a balun cable being accidentally connected to the port, or there might be a loop in the network. [chars] is the port. Recommended Action Examine the cables.
Chapter 3 Message and Recovery Procedures ETHCNTR Messages Explanation There are too many VLANs and routed ports (if the switch supports routed ports) configured. [chars] is the short interface name, such as Gi1/0/1 on a Catalyst 3750 switch, or the VLAN name, such as VLAN0002. Recommended Action Reduce the total number of VLANs and routed ports to less than 1023. To preserve configuration and connections across reboots, save the configuration.
Chapter 3 Message and Recovery Procedures EXPRESS_SETUP Messages Error Message ETHCNTR-3-UNEXPECTED_EVENT: Request [hex] encountered event [dec] in state [dec]. Note This message applies only to Catalyst 3550 switches. 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.
Chapter 3 Message and Recovery Procedures FM Messages Error Message EXPRESS_SETUP-6-MODE_EXITED. Explanation The 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).
Chapter 3 Message and Recovery Procedures FM Messages Error Message FM-2-NOVLB: Cannot create memory block for VLAN [dec]. Note This message applies only to Catalyst 3550 switches. 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.
Chapter 3 Message and Recovery Procedures FM Messages 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 This message applies only to Catalyst 3550 switches.
Chapter 3 Message and Recovery Procedures FM Messages Error Message FM-3-INITLABEL: Special initialization of label [dec] failed. Note This message applies only to Catalyst 3550 switches. 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.
Chapter 3 Message and Recovery Procedures FM Messages Error Message FM-3-LABELERROR: Incorrect label to [chars] vlan label attribute copy callback srclabel [dec], dstlabel [dec]. Note This message applies only to Catalyst 3550 switches. 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.
Chapter 3 Message and Recovery Procedures FM Messages Error Message FM-3-NOLABEL: Cannot allocate [chars] label for interface [chars]. Note This message applies only to Catalyst 3550 switches. 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.
Chapter 3 Message and Recovery Procedures FM Messages Error Message FM-3-NOTOBJECT: Invalid object (VLAN [dec], IDB [hex]) used in Feature Manager operation. Note This message applies only to Catalyst 3550 switches. 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.
Chapter 3 Message and Recovery Procedures FM Messages Error Message FM-3-QOSTTABLE: Not in truth table: ACL [dec] in map, action [dec]. Note This message applies only to Catalyst 3550 switches. Explanation A software error occurred while trying to merge a quality of service (QoS) policy map.
Chapter 3 Message and Recovery Procedures FM Messages Error Message FM-3-UNKNOWNACTION: Unknown VMR access group action [hex]. Note This message applies only to Catalyst 3550 switches. 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.
Chapter 3 Message and Recovery Procedures FRNTEND_CTRLR Messages Error Message FM-4-EXCESSSECONDARY: More than [dec] secondary IP addresses configured on interface [chars]. Note This message applies only to Catalyst 3550 switches.
Chapter 3 Message and Recovery Procedures GBIC Messages Error Message FRNTEND_CTRLR-2-SUB_INACTIVE: The front end controller [dec] is inactive. Note This message applies only to Catalyst 3750 and 2975 switches. Explanation The front-end controller that controls the LEDs, the PoE features, and the fan-control features is now inactive on the port controlled by the front-end controller. This does not affect the traffic on the port. [dec] is the controller number. Recommended Action Reset the switch.
Chapter 3 Message and Recovery Procedures GBIC Messages Error Message GBIC_1000BASET-6-GBIC_1000BASET_NO_CONFIG_NEGOTIATE: Configuration ignored. 1000BASE-T GBIC modules only support autonegotiation. Note This message applies only to Catalyst 3550 switches. 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.
Chapter 3 Message and Recovery Procedures GBIC Messages Error Message GBIC-4-NOREAD_VSDATA: Unable to read vendor-specific data for GBIC interface [chars]. Note This message applies only to Catalyst 3550 switches. 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.
Chapter 3 Message and Recovery Procedures GBIC_SECURITY Messages Error Message GBIC-6-SERDES_MODULE_UNKNOWN: Unrecognizable GBIC found in [chars] (module mask [hex]). Note This message applies only to Catalyst 3550 switches. 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.
Chapter 3 Message and Recovery Procedures GBIC_SECURITY Messages Error Message GBIC_SECURITY-4-DUPLICATE_SN: GBIC interface [dec] has the same serial number as another GBIC interface. Note This message applies only to Catalyst 3550 switches. 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.
Chapter 3 Message and Recovery Procedures GBIC_SECURITY Messages Error Message GBIC_SECURITY-4-GBIC_INTERR: Internal error occurred in setup for GBIC interface [chars]. Explanation The system could not allocate resources or had some other problem during the setup for the specified SFP module interface. [chars] is the interface in which the SFP module is installed. Recommended Action Reload the switch by using the reload privileged EXEC command.
Chapter 3 Message and Recovery Procedures GBIC_SECURITY_CRYPT Messages Error Message GBIC_SECURITY-6-SFP_INSERTED: Transceiver SFP [chars] module inserted in [chars] Explanation The online insertion and removal (OIR) facility detected a newly inserted transceiver module for the interface specified in the message. The first [chars] is the module and the second [chars] is the interface. Recommended Action No action is required.
Chapter 3 Message and Recovery Procedures GBIC_SECURITY_UNIQUE Messages Error Message GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC interface [chars] has bad crc. Explanation The small form-factor pluggable (SFP) module was identified as a Cisco SFP module, but it does not have a valid cyclic redundancy check (CRC) in the EEPROM data. [chars] is the port. Recommended Action Ensure that the Cisco IOS software running on the switch supports the SFP module. You might need to upgrade your software.
Chapter 3 Message and Recovery Procedures GIGASTACK Messages 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 This message applies only to Catalyst 3550 switches.
Chapter 3 Message and Recovery Procedures HARDWARE Messages 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 This message applies only to Catalyst 3550 switches. 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.
Chapter 3 Message and Recovery Procedures HARDWARE Messages 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.
Chapter 3 Message and Recovery Procedures HLFM Messages Error Message HARDWARE-3-STATS_ERROR: Statistics ID [dec] is invalid. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation The statistics ID used is out of range. The statistics supported by the port ASIC are identified by an ID. [dec] is the statistics ID. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 3 Message and Recovery Procedures HPSECURE Messages Error Message HLFM-3-MOD_SD: Failed to modify Station Descriptor with index [dec], vlan [dec], di [dec], error [dec], mad [dec], ref-count [dec]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation The forwarding manager attempted to modify a station descriptor that is no longer in use or is invalid.
Chapter 3 Message and Recovery Procedures IDBMAN Messages IDBMAN Messages This section contains the interface description block manager (IDBMAN) messages. Error Message IDBMAN-3-AGGPORTMISMATCH: [chars]: [chars]([dec] / [dec]) does not match internal slot/port state [chars]([dec] / [dec]). Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation There is an internal error that caused an invalid aggregate port to be used by the software.
Chapter 3 Message and Recovery Procedures IDBMAN Messages Explanation There is an internal error that caused an invalid bandwidth to be used for an aggregate port. [chars] is the port-channel name. The ([dec] / [dec]) are the slot and port numbers (slot/port). The last [dec] is the bandwidth. 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.
Chapter 3 Message and Recovery Procedures IDBMAN Messages Explanation There is an internal error that caused an interface that is not an aggregate port to be used for aggregate port operations. [chars] is the interface name, and ([dec] / [dec]) are the slot and port number (slot/port). 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.
Chapter 3 Message and Recovery Procedures IGMP_QUERIER Messages Error Message IDBMAN-4-ACTIVEPORTSINAGGPORT: [chars]( [dec] / [dec] ) has [dec] active ports, but is being removed. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation An internal error removed an aggregate port that has active ports. [chars] is the port-channel name, and the ([dec] / [dec]) are the slot and port number (slot/port). The last [dec] is the number of currently active ports.
Chapter 3 Message and Recovery Procedures ILPOWER Messages Error Message IGMP_QUERIER-4-SNOOPING_DISABLED: The IGMP querier is operationally disabled in VLAN [dec] because IGMP snooping has been disabled in this VLAN. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation IGMP snooping is disabled on this VLAN. Do not enable the IGMP querier when IGMP snooping is disabled. [dec] is the VLAN IDs.
Chapter 3 Message and Recovery Procedures ILPOWER Messages Explanation An error reported or caused by the PoE controller is detected. [dec] is the controller instance, which is 0 to 5 on a 24-port PoE switch and 0 to 11 on a 48-port PoE switch. [chars] describes the error. 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.
Chapter 3 Message and Recovery Procedures ILPOWER Messages Error Message ILPOWER-3-CONTROLLER_IF_ERR: Controller interface error, [chars]: [chars]. Note This message applies only to Catalyst 3750, 3560, and 3550 switches. Explanation An interface error is detected between the PoE controller and the system. The first [chars] is the interface. The second [chars] describes the error. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 3 Message and Recovery Procedures ILPOWER Messages Error Message ILPOWER-3-CONTROLLER_POST_ERR: Inline Power Feature is disabled on this switch because Power On Self Test (POST) failed on this switch. Please consult TECH support for further assistance Note This message applies only to Catalyst 3750, 3560, and 3550 switches. Explanation An error reported or caused by the Power over Ethernet (PoE) controller is detected during power-on self-test (POST).
Chapter 3 Message and Recovery Procedures ILPOWER Messages Error Message ILPOWER-4-LOG_OVERDRAWN: Interface [chars] is overdrawing power. it is consuming [dec] milliwatts where as maximum configured power is ([dec]) milliwatts. Note This message applies only to Catalyst 3750, 3560, and 3550 switches. Explanation The powered device is drawing more power than the maximum powered configured on the interface. [chars] is the interface, and [dec] is the maximum configured power.
Chapter 3 Message and Recovery Procedures ILPOWER Messages Error Message ILPOWER-5-IEEE-DISCONNECT: Interface [chars]: PD removed. Note This message applies only to Catalyst 3750 and 3560 switches. Explanation The powered device is no longer connected to the switch or that the connected powered device is being powered by an external AC power source. The switch is no longer providing power to the port. [chars] is the interface. Recommended Action No action is required.
Chapter 3 Message and Recovery Procedures ILPOWER Messages Error Message ILPOWER-5-INVALID_IEEE_CLASS: Interface [chars]: has detected invalid IEEE class: [dec] device. Power denied Note This message applies only to Catalyst 3750 and 3560 switches. Explanation The power device has an invalid IEEE class so that the switch is not supplying power to the device. [chars] is the interface name. [dec] is the class number of the device. Recommended Action No action is required.
Chapter 3 Message and Recovery Procedures IMAGEMGR Messages IMAGEMGR Messages This section contains image manager messages, which are related to image compatibility within the stack. Error Message IMAGEMGR-6-AUTO_ADVISE_SW_INITIATED: Auto-advise-software process initiated for systems [bits: [hex]]. Note This message applies only to Catalyst 3750 and 2975 switches. Explanation Systems with incompatible software have been detected in the switch stack.
Chapter 3 Message and Recovery Procedures IP_DEVICE_TRACKING_HA Messages Explanation A line of output from the auto-copy-software process is being displayed. [chars] is a text message reporting status of the upgrade process. Recommended Action No action is required. Error Message IMAGEMGR-6-AUTO_DOWNLOAD_SW_INITIATED: Auto-download-software process initiated for systems [bits: [hex]]. Note This message applies only to Catalyst 3750 and 2975 switches.
Chapter 3 Message and Recovery Procedures L2TM Messages L2TM Messages This section contains the Layer 2 forwarding manager messages. This software module controls the part of the hardware that performs MAC address-based forwarding and learning. A ternary content addressable memory (TCAM) device implements the forwarding table. Error Message L2TM-3-ACCESS_ERR: TCAM access failed while [chars]. Note This message applies only to Catalyst 3550 switches.
Chapter 3 Message and Recovery Procedures MAC_LIMIT Messages 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.
Chapter 3 Message and Recovery Procedures MAC_MOVE Messages Error Message MAC_LIMIT-4-ENFORCE: Enforcing limit on Vlan [dec] with Configured limit = [dec]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation The number of MAC address entries for the VLAN exceeds the maximum number allowed, and the configured action is to limit the number of entries to the maximum allowed.
Chapter 3 Message and Recovery Procedures PAGP_DUAL_ACTIVE Messages Error Message NETWORK_PORT_SATELLITE-3-PHY_LOCKUP: Repeated phy lockup seen on [chars]. Interface will be shut down. Note This message applies only to Catalyst 3550 switches. Explanation PHY lockup was detected too many times in a row. The interface is shut down to avoid continuous link flapping.
Chapter 3 Message and Recovery Procedures PBR Messages Error Message %PAGP_DUAL_ACTIVE-3-REGISTRY_ADD_ERR: Failure in adding to [chars] registry Explanation The switch could not add a function to the registry. [chars] is the registry name. Recommended Action No action is required. PBR Messages This section contains the policy-based routing (PBR) messages. Error Message PBR-2-NO_RMAP: Cannot create PBR data structures for route-map [chars] Note This message applies only to Catalyst 3550 switches.
Chapter 3 Message and Recovery Procedures PBR Messages Error Message PBR-3-UNSUPPORTED_RMAP: Route-map [chars] not supported for Policy-Based Routing Note This message applies only to Catalyst 3550 switches. 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.
Chapter 3 Message and Recovery Procedures PHY Messages PHY Messages This section contains the PHY messages. Error Message PHY-4-BADTRANSCEIVER: An inappropriate transceiver has been inserted in interface [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation A transceiver that should not be used is in the specified interface. Recommended Action Remove the transceiver.
Chapter 3 Message and Recovery Procedures PHY Messages Error Message PHY-4-MODULE_DUP: SFPs in [chars] and in [chars] have duplicate vendor-id and serial numbers. Explanation The SFP module was identified as a Cisco SFP module, but its vendor ID and serial number match that of another SFP module in the system. The first [chars] is the interface in which the SFP module is installed, the second [chars] is the interface where the duplicate SFP module is installed.
Chapter 3 Message and Recovery Procedures PIMSN Messages Error Message PHY-4-UNSUPPORTED_TRANSCEIVER:Unsupported transceiver found in [chars] Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation The SFP module was identified as a unsupported, non-Cisco SFP module. [chars] is the unsupported module. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 3 Message and Recovery Procedures PLATFORM Messages PLATFORM Messages This section contains low-level platform-specific messages. Error Message PLATFORM-1-CRASHED: [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation The system is attempting to display the failure message from the previous failure. [chars] is the description of the error message. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 3 Message and Recovery Procedures PLATFORM_FBM Messages Error Message PLATFORM-3-PW_REC_HRPC_NOT_ON_MASTER: Set-password-recovery HRPC msg from box [dec] received on master. Note This message applies only to Catalyst 3750 and 2975 switches. Explanation The stack master has received a set-password-recovery HRPC message. These messages should be received on stack member switches only. [dec] is the switch.
Chapter 3 Message and Recovery Procedures PLATFORM_HCEF Messages Error Message PLATFORM_FBM-4-RESOURCE_CRUNCH: Fallback bridging on bridge-group [dec] is experiencing a resource crunch. One or more bridge-groups may not be functional. It will recover automatically when system recovers from resource crunch. Delete the bridge-group to immediately recover. Note This message applies only to Catalyst 3750 and 3560 switches. Explanation Fallback bridging could not be configured properly.
Chapter 3 Message and Recovery Procedures PLATFORM_HPLM Messages PLATFORM_HPLM Messages This section has the platform pseudo label manager messages. Error Message PLATFORM_HPLM-3-ERROR: Failed Alloc for action record label move from [dec] to [dec]. Note This message applies only to Catalyst 3750 and 3560 switches. Explanation An internal resource allocation error occurred during the label compaction process. The first [dec] is the previous label, and the second [dec] is the new label.
Chapter 3 Message and Recovery Procedures PLATFORM _IPC Messages PLATFORM _IPC Messages This section contains the Inter-Process Communication (IPC) protocol messages. The IPC protocol handles communication between the stack master switch and stack member switches. Error Message PLATFORM_IPC-3-COMMON: [chars]. Note This message applies only to Catalyst 3750 and 2975 switches. Explanation There has been an IPC failure. [chars] describes the error message.
Chapter 3 Message and Recovery Procedures PLATFORM_IPv6 Message Error Message PLATFORM_IPC-3-MEMBER: [chars]. Note This message applies only to Catalyst 3750 and 2975 switches. Explanation There has been an IPC failure on a stack member switch. [chars] describes 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.
Chapter 3 Message and Recovery Procedures PLATFORM_PBR Messages PLATFORM_PBR Messages This section contains policy based routing (PBR) messages. Error Message PLATFORM_PBR-2-NO_RMAP: Cannot create PBR data structures for route-map [chars]. Note This message applies only to Catalyst 3750 and 3560 switches. Explanation The PBR manager could not allocate the internal data structures for this route-map. A likely cause is lack of available memory. [chars] is the route-map.
Chapter 3 Message and Recovery Procedures PLATFORM_PBR Messages Error Message PLATFORM_PBR-3-UNSUPPORTED_RMAP: Route-map [chars] not supported for Policy-Based Routing. Note This message applies only to Catalyst 3750 and 3560 switches. 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 the route-map.
Chapter 3 Message and Recovery Procedures PLATFORM_PM Messages PLATFORM_PM Messages This section contains platform port manager (PM) messages. Error Message PLATFORM_PM-3-IFCOUNTERROR: Unit number [dec] of interface [chars] is more than max allowed value of [dec]. Explanation There are too many interfaces configured for the interface type. [dec] is the interface count, [chars] is the interface, and [dec] is the maximum number of interfaces.
Chapter 3 Message and Recovery Procedures PLATFORM_RPC Messages PLATFORM_RPC Messages This section contains platform-specific remote procedure call (RPC) messages. The RPC function in the switch stack allows instances of code running on the various systems in a stack to intercommunicate by using a virtual function-call mechanism. Error Message PLATFORM_RPC-0-RESOURCE_CRASH: [chars]. Note This message applies only to Catalyst 3750 and 2975 switches.
Chapter 3 Message and Recovery Procedures PLATFORM_RPC Messages 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 on page 2-7. Error Message PLATFORM_RPC-3-PERSISTENT_UNABLE_TO_SEND: System is consistently unable to send RPC message: [chars], paks_outstanding: [int].
Chapter 3 Message and Recovery Procedures PLATFORM_SPAN Messages Explanation There is a local resource error or that too many outgoing messages are queued for the message class. The first [dec] is RPC request class, the second [dec] is the RPC request number, and [chars] is an optional comment. 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.
Chapter 3 Message and Recovery Procedures PLATFORM_UCAST Messages PLATFORM_UCAST Messages This section contains platform unicast routing messages. Error Message PLATFORM_UCAST-3-ADJ: [chars]. Note This message applies only to Catalyst 3750 and 3560 switches. Explanation The adjacency module for unicast routing encountered an error. [chars] describes the error. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 3 Message and Recovery Procedures PLATFORM_UCAST Messages Error Message PLATFORM_UCAST-3-CEF: [chars]. Note This message applies only to Catalyst 3750 and 3560 switches. Explanation The Cisco Express Forwarding (CEF) module for unicast routing encountered an error. [chars] describes the error. 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.
Chapter 3 Message and Recovery Procedures PLATFORM_UCAST Messages Error Message PLATFORM_UCAST-3-HSRP: [chars]. Note This message applies only to Catalyst 3750 and 3560 switches. Explanation The Hot Standby Router Protocol (HSRP) module for unicast routing encountered an error. [chars] describes the error. 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.
Chapter 3 Message and Recovery Procedures PLATFORM_VLAN Messages Error Message PLATFORM_UCAST-6-PREFIX: One or more, more specific prefixes could not be programmed into TCAM and are being covered by a less specific prefix Note This message applies only to Catalyst 3750 and 3560 switches. Explanation A more specific prefix could not be programmed into Ternary Content Addressable Memory (TCAM) and is covered by a less specific prefix. This could be a temporary condition.
Chapter 3 Message and Recovery Procedures PLATFORM_WCCP Messages Error Message PLATFORM_VLAN-3-UNLOCK_FAIL: Failed to unlock vlan-id [dec], associated mapped vlan id value [dec]. Explanation The switch failed to unlock a VLAN ID. The most likely cause is that the VLAN is already unlocked. The first [dec] is the VLAN ID, and the second [dec] is the MVID. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 3 Message and Recovery Procedures PM Messages 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-LOW_SP_MEM: Switch process available memory is less than [dec] bytes. Note This message applies to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.
Chapter 3 Message and Recovery Procedures PM Messages Error Message PM-3-INTERNALERROR: Port Manager Internal Software Error ([chars]: [chars]: [dec]: [chars]). Explanation An internal software error occurred in the port manager. The parameters identify the problem for technical support. The first [chars] is the error message, and the second [chars] is the filename. [dec] is the line number, and the last [chars] is the function name.
Chapter 3 Message and Recovery Procedures PM Messages Error Message PM-4-BAD_CARD_SLOT: an invalid card slot ([dec]) was detected. Explanation The port manager detected an invalid request. [dec] is the slot number. 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 tech-support user EXEC command to gather data that might help identify the nature of the error.
Chapter 3 Message and Recovery Procedures PM Messages Error Message PM-4-BAD_PORT_COOKIE: an invalid port cookie was detected. Explanation The port manager detected an invalid request. 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 tech-support user EXEC command to gather data that might help identify the nature of the error.
Chapter 3 Message and Recovery Procedures PM Messages Error Message PM-4-ERR_DISABLE: [chars] error detected on [chars], putting [chars] in err-disable state. 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).
Chapter 3 Message and Recovery Procedures PM Messages Error Message PM-4-ERR_RECOVER_VP: Attempting to recover from [chars] err-disable state on [chars], vlan [dec]. Explanation The port manager is attempting to bring up the virtual port after taking it down to the error-disabled state. The first [chars] is the error, the second [chars] is the virtual port, and [dec] is the VLAN ID. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 3 Message and Recovery Procedures PM Messages Error Message PM-4-INT_VLAN_NOTAVAIL: Failed to allocate internal VLAN in Port Manager. 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.
Chapter 3 Message and Recovery Procedures PM Messages Error Message PM-4-PORT_BOUNCED: Port [chars] was bounced by [chars]. Note This message applies to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation During a switchover when the port was in the link-down state, the port manager restarted the port. A port can be restarted only when the port data structures are not consistent in the active and standby supervisors.
Chapter 3 Message and Recovery Procedures PORT_SECURITY Messages 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 on page 2-7. Error Message PM-4-VMPS_CFG: Dynamic access VLAN [dec] same as voice vlan on [chars]. Note This message applies to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.
Chapter 3 Message and Recovery Procedures PORT_SECURITY Messages Error Message PORT_SECURITY-6-ADDR_REMOVED: Address [dec]:[enet] exists on port [chars]. It has been removed from port [chars]. Explanation A routed port is reconfigured as a switch port. The address in the previous switch configuration conflicts with 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.
Chapter 3 Message and Recovery Procedures QATM Messages QATM Messages This section contains the QoS and ACL TCAM manager messages. This software module configures the hardware to match the QoS classification and security ACL that you configure on the switch. Error Message QATM-2-ASDATA_READ: Cannot read TCAM associated data. Note This message applies only to Catalyst 3550 switches. Explanation Associated data could not be read from the TCAM. This error might mean a hardware failure.
Chapter 3 Message and Recovery Procedures QM Messages Error Message QATM-2-TCAM_WRITE: Cannot write the TCAM. This message applies only to Catalyst 3550 switches. 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.
Chapter 3 Message and Recovery Procedures QM Messages Error Message QM-4-CLASS_NOT_SUPPORTED: Classification is not supported in class map [chars]. Note This message applies only to Catalyst 3550 switches. 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.
Chapter 3 Message and Recovery Procedures QM Messages 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.
Chapter 3 Message and Recovery Procedures QOSMGR Messages QOSMGR Messages This section contains the quality of service (QoS) manager messages. An incorrect QoS setting causes these messages. Error Message QOSMGR-3-FEATURE_NOT_FOUND: Cannot find feature for [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation An internal software error has occurred. [chars] is the description of the feature that the software cannot find.
Chapter 3 Message and Recovery Procedures QOSMGR Messages 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 on page 2-7. Error Message QOSMGR-3-NO_POLICER_QOSLABEL: Creating port Class Label Failed. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.
Chapter 3 Message and Recovery Procedures QOSMGR Messages Error Message QOSMGR-3-POLICER_RES_COUNT: Internal Error Invalid Policer count. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation An internal software error has occurred. 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.
Chapter 3 Message and Recovery Procedures QOSMGR Messages Error Message QOSMGR-3-RESERVE_COUNT_ERROR: Reserved Count Exceeding total [dec]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation An internal software error has occurred in the allocated reserved buffers. [dec] is the reserved count computed by the software. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 3 Message and Recovery Procedures QOSMGR Messages Error Message QOSMGR-4-ACTION_NOT_SUPPORTED: Action is not supported in policymap [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. 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 policy-map name.
Chapter 3 Message and Recovery Procedures QOSMGR Messages Error Message QOSMGR-4-HARDWARE_NOT_SUPPORTED: Hardware limitation has reached for policymap [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation The policy-map configuration has exceeded the limitation of the hardware. You configured more QoS ACL entries than the number specified in the Switch Database Management (SDM) template. [chars] is the policy-map name.
Chapter 3 Message and Recovery Procedures RMON Messages Explanation The policy-map configuration has exceeded the limitation of the hardware. You configured more policers together in all policy maps (by using the police or police aggregate policy-map class configuration command) than supported by hardware. [chars] is the policy-map name. Recommended Action Reconfigure the class maps or the policy maps, or delete the policy map from some interfaces.
Chapter 3 Message and Recovery Procedures SDM Messages SDM Messages This section contains the Switch Database Management (SDM) message. Error Message SDM-6-MISMATCH_ADVISE: [chars]. Note This message applies only to Catalyst 3750 and 2975 switches. Explanation A stack member cannot support the SDM template that the stack master is using. Switches in the SDM mismatch state are not functional stack members. This error follows the STACKMGR-6-SWITCH_ADDED_SDM error message if it reports SDM_MISMATCH.
Chapter 3 Message and Recovery Procedures SPANTREE Messages 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. Explanation A bridge protocol data unit (BPDU) was received on an interface that has the spanning tree BPDU guard feature enabled. As a result, the interface was administratively shut down. [chars] is the interface name.
Chapter 3 Message and Recovery Procedures SPANTREE Messages Error Message SPANTREE-2-BLOCK_PVID_PEER: Blocking [chars] on [chars]. Inconsistent peer vlan. 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.
Chapter 3 Message and Recovery Procedures SPANTREE Messages Error Message SPANTREE-2-LOOPGUARD_CONFIG_CHANGE: Loop guard [chars] on port [chars] on [chars]. Explanation The spanning-tree loopguard configuration for the listed interface has been changed. If enabled, the interface is placed into the blocking state. It is marked as loopguard-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.
Chapter 3 Message and Recovery Procedures SPANTREE Messages Error Message SPANTREE-2-PVSTSIM_OK: PVST Simulation inconsistency cleared on port [chars]. Explanation The specified interface is no longer receiving PVST BPDUs advertising information that is inconsistent with the CIST port information. The PVST simulation inconsistency is cleared, and the interface returns to normal operation. [chars] is the port. Recommended Action No action is required.
Chapter 3 Message and Recovery Procedures SPANTREE Messages Error Message SPANTREE-2-ROOTGUARD_BLOCK: Root guard blocking port [chars] on [chars]. 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.
Chapter 3 Message and Recovery Procedures SPANTREE Messages Error Message SPANTREE-3-BAD_PORTNUM_SIZE: Rejected an attempt to set the port number field size to [dec] bits (valid range is [dec] to [dec] bits). Explanation An error occurred in the platform-specific code that caused it to request more or less bits than are possible. The spanning-tree port identifier is a 16-bit field, which is divided evenly between the port priority and port number, with each subfield being 8 bits.
Chapter 3 Message and Recovery Procedures SPANTREE Messages Error Message SPANTREE-4-PORT_NOT_FORWARDING: [chars] [chars] [chars] [chars]. Explanation This message appears when a port-not-forwarding alarm is set or cleared. The first [chars] is the mode (for example, assert or clear), and the second [chars] is the severity (for example, minor). The third [chars] is the interface name, and the fourth [chars] is the alarm string (for example, port not forwarding).
Chapter 3 Message and Recovery Procedures SPANTREE Messages Error Message No action is required.SPANTREE-6-PORTDEL_ALL_VLANS: [chars] deleted from all Vlans Explanation The interface has been deleted from all VLANs. [chars] is the deleted interface. Recommended Action No action is required. Error Message SPANTREE-6-PORT_STATE: Port [chars] instance [dec] moving from [chars] to [chars]. Explanation The port state changed. The first [chars] is the interface name. [dec] is the spanning-tree instance ID.
Chapter 3 Message and Recovery Procedures SPANTREE_FAST Messages 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). 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.
Chapter 3 Message and Recovery Procedures STACKMGR Messages Explanation This switch could not get the device record for some or all other switches in the stack. 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.
Chapter 3 Message and Recovery Procedures STACKMGR Messages Explanation The specified stack port status has changed state to up or down. The first [chars] is the stack port (1 or 2), [dec] is the switch number, and the second [chars] is the new state (up or down). Recommended Action No action is required. Error Message STACKMGR-4-SWITCH_ADDED: Switch [dec] has been ADDED to the stack. Note This message applies only to Catalyst 3750 and 2975 switches.
Chapter 3 Message and Recovery Procedures STORM_CONTROL Messages Error Message STACKMGR-5-MASTER_READY: Master Switch [dec] is READY. Note This message applies only to Catalyst 3750 and 2975 switches. Explanation The stack master is ready for use. [dec] is the stack master switch number. Recommended Action No action is required. Error Message STACKMGR-5-SWITCH_READY: Switch [dec] is READY. Note This message applies only to Catalyst 3750 and 2975 switches. Explanation The switch is ready.
Chapter 3 Message and Recovery Procedures SUPERVISOR Messages SUPERVISOR Messages This section contains the supervisor ASIC message. This ASIC controls the CPU and the switch sending and receiving ports. Error Message SUPERVISOR-3-FATAL: [chars]. Note This message applies to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation An internal error occurred in the supervisor ASIC. [chars] is the detailed error message.
Chapter 3 Message and Recovery Procedures SUPQ Messages Error Message SUPQ-4-CPUHB_RECV_STARVE: [chars]. Note This message applies to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation The system has detected that messages directed to the CPU are delayed. [chars] is the detailed 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.
Chapter 3 Message and Recovery Procedures SW_DAI Messages Error Message SUPQ-4-PORT_QUEUE_STUCK: Port queue Stuck for asic [dec] port [dec] queue [dec]. Note This message applies to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation The system has detected that an interface queue is not being cleared in a reasonable time. The first [dec] is the ASIC, the second [dec] is the interface, and the third [dec] is the queue number.
Chapter 3 Message and Recovery Procedures SW_DAI Messages The second [dec] is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and the time of day. Recommended Action No action is required. Error Message SW_DAI-4-DHCP_SNOOPING_DENY: [dec] Invalid ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]).
Chapter 3 Message and Recovery Procedures SW_DAI Messages interface. The second [dec] is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and the time of day. Recommended Action No action is required. Error Message SW_DAI-4-PACKET_BURST_RATE_EXCEEDED: [dec] packets received in [dec] seconds on [chars].
Chapter 3 Message and Recovery Procedures SW_MACAUTH Messages Error Message SW_DAI-6-ACL_PERMIT: [dec] ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]). Note This message applies only to Catalyst 3750 and 3560 switches. Explanation The switch has received ARP packets that are permitted as a result of an ACL match. The first [dec] is the number of valid ARP packets.
Chapter 3 Message and Recovery Procedures SW_MATM Messages Error Message SW_MACAUTH-5-MACAUTH_ENADSA: MAC Authentication [chars] Explanation MAC authentication is enabled or disabled. [chars] is the MAC authentication status, either enabled or disabled. Recommended Action No action is required. Error Message SW_MACAUTH-5-MAC_AUTHENTICATED: MAC [enet] was authenticated Explanation The switch has received a command to authenticate a MAC address. [enet] is the MAC address.
Chapter 3 Message and Recovery Procedures SW_VLAN Messages Error Message SW_VLAN-3-VLAN_DAT_CACHE_SEQUENCE: Out of sequence vlan.dat sync message. Expected: [dec]; received: [dec]. Explanation The vlan.dat file is synchronized to the STANDBY through one or more checkpoint messages from ACTIVE. The sequence number for each set of checkpoint messages starts with 1. These messages are cached at the STANDBY until the end-of-set indicator is received.
Chapter 3 Message and Recovery Procedures SW_VLAN Messages Error Message SW_VLAN-4-BAD_PM_VLAN_COOKIE_RETURNED: VLAN manager unexpectedly received a bad PM VLAN cookie from the Port Manager, VLAN indicated [dec]. Explanation 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.
Chapter 3 Message and Recovery Procedures SW_VLAN Messages Error Message SW_VLAN-4-BAD_VLAN_TIMER_ACTIVE_VALUE: Encountered incorrect VLAN timer active value [chars]. Explanation Because of a software error, a VLAN timer was detected as active when it should have been inactive or as inactive when it should have been active. [chars] is the VLAN timer active value. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 3 Message and Recovery Procedures SW_VLAN Messages Error Message SW_VLAN-4-EXT_VLAN_INVALID_DATABASE_DATA: Extended VLAN manager received bad data of type [chars] value [dec] from function [chars]. 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.
Chapter 3 Message and Recovery Procedures SW_VLAN Messages Error Message SW_VLAN-4-STARTUP_EXT_VLAN_CONFIG_FILE_FAILED: Failed to configure extended range VLAN from startup-config. Error [chars]. 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.
Chapter 3 Message and Recovery Procedures SW_VLAN Messages Error Message SW_VLAN-4-VTP_INVALID_DATABASE_DATA: VLAN manager received bad data of type [chars] value [dec] from vtp database function [chars]. Explanation 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.
Chapter 3 Message and Recovery Procedures SW_VLAN Messages Error Message SW_VLAN-4-VTP_USER_NOTIFICATION: VTP protocol user notification: [chars]. 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.
Chapter 3 Message and Recovery Procedures SWITCH_QOS_TB Messages SWITCH_QOS_TB Messages This section contains the QoS trusted boundary (TB) messages. Error Message SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: [chars] detected on port [chars], port's configured trust state is now operational. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.
Chapter 3 Message and Recovery Procedures TCAMMGR Messages Error Message TCAMMGR-3-HANDLE_ERROR: cam handle [hex] is invalid. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation The CAM handle used by the caller is not valid. [hex] is the handle 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.
Chapter 3 Message and Recovery Procedures UDLD Messages Explanation The CAM region is not valid. [dec] is the region. 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.
Chapter 3 Message and Recovery Procedures UDLD Messages Error Message UDLD-3-UDLD_IDB_ERROR: UDLD error handling [chars] interface [chars]. 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 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.
Chapter 3 Message and Recovery Procedures UFAST_MCAST_SW Messages 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 on page 2-7. Error Message UDLD-6-UDLD_PORT_RESET: UDLD reset interface [chars].
Chapter 3 Message and Recovery Procedures VQPCLIENT Messages VQPCLIENT Messages This section contains VLAN Query Protocol (VQP) client messages. Error Message VQPCLIENT-2-CHUNKFAIL: Could not allocate memory for VQP. Explanation An error occurred when the system tried to allocate memory for the VQP client. 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.
Chapter 3 Message and Recovery Procedures WCCP Messages Error Message VQPCLIENT-3-VLANNAME: Invalid VLAN [chars] in response. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches. Explanation The VLAN membership policy server (VMPS) has specified a VLAN name that is unknown to the switch. [chars] is the VLAN name. Recommended Action Ensure that the VLAN exists on the switch. Verify the VMPS configuration by entering the show vmps privileged EXEC command.
Chapter 3 Message and Recovery Procedures WRLSCNTR Messages Explanation Part of initialization required for the normal operation of the wireless LAN controller failed. 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.
I N D EX Cluster Membership Protocol messages A See CMP messages abbreviations cluster requirements char, variable field 2-6 chars, variable field CMP messages 2-6 dec, variable field codes 2-6 enet, variable field 2-6 hex, variable field 2-6 inet, variable field 2-6 configuration manager messages See CFGMGR messages conventions command access control list messages publication 3-3 text i-vii auto-QoS messages 3-8 i-vii i-vii D BACKUP_INTERFACE messages BADTRANSCEIVER messages
Index dynamic ARP inspection G See SW_DAI messages Dynamic Host Configuration Protocol messages GBIC_SECURITY_CRYPT messages GBIC_SECURITY_UNIQUE messages See DHCP messages Dynamic Trunking Protocol messages GBIC_SECURITY messages 3-51 3-52 3-48 GBIC messages, Catalyst 3550 See DTP messages GigaStack GBIC module 3-53 identification and validation E 3-45 Gigabit Interface Converter messages, Catalyst 3550 EC messages See GBIC messages, Catalyst 3550 3-25 ENVIRONMENT messages ETHCNTR messa
Index initial configuration See getting started guide and hardware installation guide interface description block manager messages See IDBMAN messages BSPATCH 3-9 CFGMGR 3-10 CMP 3-13 DHCP DHCP_SNOOPING inter-process communication protocol messages See PLATFORM_IPC messages IP_DEVICE_TRACKING_HA messages DOT1Q_TUNNELLING 3-70 DOT1X (802.
Index MAC_MOVE MATM SW_VLAN 3-73 3-138 SWITCH_QOS_TB 3-138 NETWORK_PORT_SATELLITE network port satellite TCAMMGR 3-73 UDLD 3-73 PAGP_DUAL_ACTIVE 3-146 3-148 UFAST_MCAST_SW 3-74 PBR 3-75 VQPCLIENT PHY 3-77 WCCP PIMSN PLATFORM_FBM 3-152 PLATFORM_IPC description 3-82, 3-83 table 3-84 PLATFORM_PBR 2-5 2-5 message text definition 3-85, 3-86 mmemonic code 3-88 PLATFORM_RPC 3-9 message severity levels 3-81 PLATFORM_HPLM PLATFORM_PM 3-150 messages, transceiver 3-80 3-1
Index PLATFORM_IPC messages PLATFORM_PBR messages PLATFORM_PM messages quality of service manager messages 3-84 quality of service messages 3-88 PLATFORM_RPC messages See auto-QoS messages 3-89 PLATFORM_SPAN messages See QATM messages 3-91 PLATFORM_UCAST messages See QM messages 3-92 PLATFORM_VLAN messages 3-95 PLATFORM_WCCP messages 3-96 PLATFORM messages See QOSMGR messages 3-85, 3-86 R 3-80 platform pseudo label manager messages remote network monitoring messages See PLATFORM_HP
Index spanning tree per-VLAN messages transceiver messages See SPANTREE_VLAN_SW messages SPANTREE_FAST messages SPANTREE messages See SWITCH_QOS_TB messages 3-127 3-119 U stack manager messages See STACKMGR messages STACKMGR messages UDLD messages 3-127 3-130 See PLATFORM_UCAST messages UniDirectional Link Detection messages See SUPQ messages See UDLD messages 3-131 SW_DAI messages upgrading information 3-134 SW_MACAUTH messages SW_VLAN messages 3-150 unicast routing messages 3-131 supe
