Cisco Catalyst Blade Switch 3120 for HP System Message Guide Cisco IOS Release 12.2(40)EX November 2007 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 vii vii Conventions vii Related Publications viii Obtaining Documentation, Obtaining Support, and Security Guidelines CHAPTER 1 System Message Overview 1-1 How to Read System Messages 1-1 Error Message Traceback Reports Output Interpreter 1-6 Bug Toolkit 1-6 Contacting TAC 1-6 CHAPTER 2 1-5 Message and Recovery Procedures ACLMGR Messages BADTRANSCEIVER Messages BSPATCH Messages 2-8 CFGMGR Messages 2-9 DOT1X Messages 2-16 2-19 DOT1X_SWI
Contents GBIC_SECURITY Messages 2-33 GBIC_SECURITY_CRYPT Messages 2-35 GBIC_SECURITY_UNIQUE Messages HARDWARE Messages HLFM Messages 2-36 2-41 HPSECURE Messages 2-42 IGMP_QUERIER Messages IMAGEMGR Messages 2-42 2-43 IP_DEVICE_TRACKING Messages MAC_MOVE Messages PHY Messages 2-44 2-45 2-45 PIMSN Messages 2-47 PLATFORM Messages 2-47 PLATFORM_ENV Messages 2-48 PLATFORM_FBM Messages 2-49 PLATFORM_HCEF Message 2-50 PLATFORM_HPLM Messages PLATFORM _IPC Messages 2-50 2-51 PLATFORM_IPv6
Contents SPANTREE_VLAN_SW Messages STACKMGR Messages 2-85 STORM_CONTROL Messages SUPERVISOR Messages SUPQ Messages 2-87 2-88 2-88 SW_DAI Messages 2-90 SW_MACAUTH Messages SW_MATM 2-85 2-92 2-93 SWITCH_QOS_TB Messages SW_VLAN Messages 2-94 TCAMMGR Messages 2-100 UDLD Messages 2-93 2-102 UFAST_MCAST_SW Messages VQPCLIENT Messages 2-104 2-104 INDEX Cisco Catalyst Blade Switch 3120 for HP System Message Guide OL-12249-01 v
Contents Cisco Catalyst Blade Switch 3120 for HP System Message Guide vi OL-12249-01
Preface Audience This guide is for the networking professional managing the Cisco Catalyst Blade Switch 3120 for HP or blade switch stack, known 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 Cisco Catalyst Blade Switch 3120 for HP-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 contained in this manual.
Preface Obtaining Documentation, Obtaining Support, and Security Guidelines • Cisco Catalyst Blade Switch 3000 Series for HP Getting Started Guide (not orderable but available on Cisco.com) • Regulatory Compliance and Safety Information for the Cisco Catalyst Blade Switch 3000 Series for HP (not orderable but available on Cisco.
Preface Obtaining Documentation, Obtaining Support, and Security Guidelines Cisco Catalyst Blade Switch 3120 for HP System Message Guide x OL-12249-01
C H A P T E R 1 System Message Overview This guide describes the switch 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. This guide also includes error messages that appear when the system fails.
Chapter 1 System Message Overview How to Read System Messages Table 1-1 Facility Codes Facility Code Description Location ACLMGR ACL manager “ACLMGR Messages” section on page 2-3 BACKUP_INTERFACE Flex Links “BACKUP_INTERFACE Messages” section on page 2-7 BADTRANSCEIVER Defective transceiver messages “BADTRANSCEIVER Messages” section on page 2-7 BSPATCH Boot loader patch “BSPATCH Messages” section on page 2-8 CFGMGR Configuration manager “CFGMGR Messages” section on page 2-9 CGESM CGE
Chapter 1 System Message Overview How to Read System Messages Table 1-1 Facility Codes (continued) Facility Code Description Location PLATFORM Low-level platform-specific “PLATFORM Messages” section on page 2-47 PLATFORM_ENV Platform environment “PLATFORM_ENV Messages” section on page 2-48 PLATFORM_FBM Platform fallback bridging manager “PLATFORM_FBM Messages” section on page 2-49 PLATFORM_HPLM Platform pseudo label manager “PLATFORM_HPLM Messages” section on page 2-50 PLATFORM_IPC Platf
Chapter 1 System Message Overview How to Read System Messages Table 1-1 Facility Codes (continued) Facility Code Description Location SW_DAI Dynamic ARP inspection “SW_DAI Messages” section on page 2-90 SW_MACAUTH MAC address authentication “SW_MACAUTH Messages” section on page 2-92 SW_QOS_TB QoS trusted boundary “SWITCH_QOS_TB Messages” section on page 2-93 SW_VLAN VLAN manager “SW_VLAN Messages” section on page 2-94 TCAMMGR Ternary content addressable memory manager “TCAMMGR Messages
Chapter 1 System Message Overview Error Message Traceback Reports Table 1-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 1 System Message Overview Error Message Traceback Reports Output Interpreter The Output Interpreter provides additional information and suggested fixes based on the output of many CLI commands, such as the the show tech-support privileged EXEC command. You can access the Output Interpreter at this URL: https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.
C H A P T E R 2 Message and Recovery Procedures This chapter describes the Cisco Catalyst Blade Switch 3120 for HP 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 2 • IGMP_QUERIER Messages, page 2-42 • IMAGEMGR Messages, page 2-43 • IP_DEVICE_TRACKING Messages, page 2-44 • MAC_MOVE Messages, page 2-45 • PHY Messages, page 2-45 • PIMSN Messages, page 2-47 • PLATFORM Messages, page 2-47 • PLATFORM_ENV Messages, page 2-48 • PLATFORM_FBM Messages, page 2-49 • PLATFORM_HCEF Message, page 2-50 • PLATFORM_HPLM Messages, page 2-50 • PLATFORM _IPC Messages, page 2-51 • PLATFORM_IPv6_UCAST Message, page 2-52 • PLATFORM_PBR Messages, page 2-5
Chapter 2 Message and Recovery Procedures ACLMGR Messages • TCAMMGR Messages, page 2-100 • UDLD Messages, page 2-102 • UFAST_MCAST_SW Messages, page 2-104 • VQPCLIENT Messages, page 2-104 ACLMGR Messages This section contains the access control list (ACL) manager messages. Most messages in this section are the result of a switch memory shortage, which includes hardware memory and label space but not CPU memory. Both kinds of memory shortages are described.
Chapter 2 Message and Recovery Procedures ACLMGR Messages Error Message ACLMGR-3-AUGMENTFAIL: Augmenting of access-map [chars] on [chars] label [dec] failed. Explanation The system ran out of CPU DRAM when trying 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.
Chapter 2 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 2 Message and Recovery Procedures ACLMGR Messages Error Message ACLMGR-3-PACLTTABLE: Not in truth table: IPSrcGrd [dec] PACL [dec]. Explanation A 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. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 2 Message and Recovery Procedures BACKUP_INTERFACE 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 2 Message and Recovery Procedures BSPATCH Messages BSPATCH Messages This section contains boot loader patch messages. Error Message BSPATCH-1-RELOAD: System will reboot to activate newly patched Boot Loader. Explanation The switch will automatically reboot after the boot loader is patched. Recommended Action If this message recurs, copy it 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 2 Message and Recovery Procedures CFGMGR Messages CFGMGR Messages This section contains the configuration manager messages. Error Message CFGMGR-1-UNABLE_TO_SEND_RUN_CFG: unable to send running-cfg, bits: [hex], retrying... Explanation The system is unsuccessfully attempting to distribute the running configuration to the stack member switches. [hex] is the bit representation of the switch number.
Chapter 2 Message and Recovery Procedures CFGMGR Messages Error Message CFGMGR-5-UNABLE_TO_USE_PROVISIONED_CFG: Switch [dec] will receive the default configuration. 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.
Chapter 2 Message and Recovery Procedures CGESM Messages CGESM Messages This section contains the Cisco Gigabit Ethernet Switch Module (CGESM) specific messages. Error Message CGESM-5-FC_MODULE_INSERT: Fiber Channel Module Insertion Detected. Explanation This message means that the fiber channel module has been inserted. Recommended Action No action is required. Error Message CGESM-5-FC_MODULE_REMOVAL: Fiber Channel Module Removal Detected.
Chapter 2 Message and Recovery Procedures CLS_ACC Messages Error Message CLS_ACC-2-MODE_ENTERED: Entering consoleless access mode [chars] Explanation The switch enters consoleless access mode. [chars] is the name of the mode. Recommended Action No action is required. Error Message CLS_ACC-2-MODE_EXITED: Complete consoleless access from mode [chars] Explanation The switch exits from consoleless access mode. [chars] is the mode. Recommended Action No action is required.
Chapter 2 Message and Recovery Procedures CLS_ACC Messages Error Message CLS_ACC-3-NO_ACC_INTF: Failed to find a free interface as consoleless access interface or failed to retrieve the access interface information Explanation The switch cannot find an interface to be the management interface for consoleless access. 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 2 Message and Recovery Procedures CLS_ACC Messages Error Message CLS_ACC-3-VLAN_CREATE_FAIL: Failed to allocate a free vlan as consoleless access vlan,use default mamagement vlan Explanation The switch cannot find a VLAN with an ID from 2 to1000 to be the management VLAN for consoleless access. 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 2 Message and Recovery Procedures CLS_ACC Messages Error Message CLS_ACC-5-RSTIMG: User reset switch image to factory default image under recovery mode Explanation In recovery mode, the switch image resets to the default image. Recommended Action No action is required. Error Message CLS_ACC-7-ACC_INTF: Selected management interface: [chars] interface number: [dec] Explanation An interface has been selected for Express Setup.
Chapter 2 Message and Recovery Procedures DHCP_SNOOPING Messages DHCP_SNOOPING Messages This section contains the DHCP snooping messages. Error Message DHCP_SNOOPING-3-DHCP_SNOOPING_INTERNAL_ERROR: DHCP Snooping internal error, [chars]. Explanation A software sanity check failed in the DHCP snooping process. [chars] is 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 2 Message and Recovery Procedures DHCP_SNOOPING Messages Error Message DHCP_SNOOPING-4-IP_SOURCE_BINDING_NON_EXISTING_VLAN_WARNING: IP source binding is configured on non existing vlan [dec]. 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.
Chapter 2 Message and Recovery Procedures DHCP_SNOOPING Messages Error Message DHCP_SNOOPING-6-BINDING_COLLISION: Binding collision. [dec] bindings ignored. 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.
Chapter 2 Message and Recovery Procedures DOT1X Messages DOT1X Messages This section contains the IEEE 802.1x messages. Error Message DOT1X-4-MEM_UNAVAIL: Memory was not available to perform the 802.1X action. Explanation The system memory is not sufficient to perform IEEE 802.1x authentication. Recommended Action Reduce other system activity to reduce memory demands. If the switch does not have enough memory, upgrade to a larger memory configuration.
Chapter 2 Message and Recovery Procedures DOT1X Messages Error Message DOT1X-5-ERR_MULTI_ACCESS: Dot1x can not be enabled on voice vlan configured ports. Explanation IEEE 802.1x authentication could not be enabled on the voice VLAN- configured port. This occurred because the switch tried to set IEEE 802.1x port control to auto or force-unauthorized mode on a voice VLAN- configured port, which is not allowed. Recommended Action Disable the voice VLAN on the interface, and then try IEEE 802.
Chapter 2 Message and Recovery Procedures DOT1X_SWITCH Messages Error Message DOT1X-5-ERR_TRUNK: Dot1x can not be enabled on Trunk port. Explanation IEEE 802.1x authentication could not be enabled on the trunk port. This occurred because the switch tried to set IEEE 802.1x port control to auto or force-unauthorized mode on a trunk port, which is not allowed. Recommended Action Disable trunking on the interface, and try to re-enable IEEE 802.1x authentication on the port.
Chapter 2 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 2 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 2 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 2 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 cannot 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 2 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 2 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 get the memory it needed to initialize the required data structures. [chars] is the data structure name.
Chapter 2 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 EtherChannel or the other ports in the EtherChannel. For the interface to join the bundle (EtherChannel), change the interface attributes to match the EtherChannel attributes.
Chapter 2 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 2 Message and Recovery Procedures EC Messages Error Message EC-5-NOPAGP: Invalid EC mode, PAgP not enabled. Explanation PAgP is not included in the Cisco IOS image and 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.
Chapter 2 Message and Recovery Procedures ETHCNTR Messages Error Message EC-5-UNSUITABLE: [chars] will not join any port-channel, [chars]. 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.
Chapter 2 Message and Recovery Procedures EXPRESS_SETUP Messages Error Message ETHCNTR-3-SNAP_FORWARDING_UNSUPPORTED: IPv4/IPv6 SNAP forwarding will be disabled because switch [dec] does not support this feature. Explanation A switch that is being added to the stack does not support the forwarding of IP Version 4 (IPv4) and IP Version 6 (IPv6) frames with Subnetwork Access Protocol (SNAP) encapsulation. If this occurs, forwarding of IPv4 and IPv6 frames is disabled in the switch stack.
Chapter 2 Message and Recovery Procedures FRNTEND_CTRLR Messages Error Message EXPRESS_SETUP-6-MODE_EXITED. Explanation The Express Setup mode is no longer active. Recommended Action No action is required. FRNTEND_CTRLR Messages This section contains the front-end controller messages. Error Message FRNTEND_CTRLR-1-MGR_TXQ_FULL: The front end controller Tx queue reached watermark level Explanation There are too many messages in the queue between the front-end controller and the switch software.
Chapter 2 Message and Recovery Procedures GBIC_SECURITY Messages Error Message GBIC_SECURITY-4-EEPROM_CRC_ERR: EEPROM checksum error for GBIC in [chars]. Explanation The GBIC in the specified port has invalid EEPROM data. [chars] is the port in which the GBIC is inserted. Recommended Action Remove the GBIC from the port. Error Message GBIC_SECURITY-4-EEPROM_READ_ERR: Error in reading GBIC serial ID in [chars]. Explanation An error occurred while the switch was reading the GBIC type from the EEPROM.
Chapter 2 Message and Recovery Procedures GBIC_SECURITY_CRYPT Messages Error Message GBIC_SECURITY-6-SFP_REMOVED: Transceiver SFP [chars] module removed from [chars] Explanation The online insertion and removal (OIR) facility detected the removal of a transceiver module from 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 2 Message and Recovery Procedures GBIC_SECURITY_UNIQUE Messages GBIC_SECURITY_UNIQUE Messages This section contains the Cisco GBIC, SFP, and 10-Gigabit Ethernet module security messages that identify whether the module is unique. Note The switches support SFP and 10-Gigabit Ethernet modules and do not support GBIC modules.
Chapter 2 Message and Recovery Procedures HARDWARE Messages Error Message HARDWARE-2-FAN_ERROR: Fan Failure. Explanation This message means that the fan is not working. Recommended Action This is a hardware failure. The fan might recover automatically. If the fan failure persists, 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 2 Message and Recovery Procedures HARDWARE Messages Error Message HARDWARE-2-FAN_ERROR: Fan [chars] Failure Explanation The switch fan is not working. [chars] is the fan name. Recommended Action This is a hardware failure. The fan might recover automatically. If the fan failure persists, 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 2 Message and Recovery Procedures HARDWARE Messages Error Message HARDWARE-2-FAN_ERROR: Fan Failure. Explanation This message means that the fan is not working. Recommended Action This is a hardware failure. The fan might recover automatically. If the fan failure persists, 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 2 Message and Recovery Procedures HARDWARE Messages Error Message HARDWARE-3-PORTNUM_ERROR: port number [dec] is invalid. Explanation The port number used is invalid (out of range). Each interface in a given port ASIC is identified by an index value. [dec] is the port 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.
Chapter 2 Message and Recovery Procedures HLFM Messages Error Message HARDWARE-5-THERMAL_NORMAL: Temperature is within the acceptable limit. Explanation This message means that temperature sensor valve inside the switch is within the normal limit. Recommended Action No action is required. HLFM Messages This section contains messages from the local forwarding manager. Error Message HLFM-3-MACFREE_ERROR: MAC address [enet], vlan [dec] is still referenced; cannot free.
Chapter 2 Message and Recovery Procedures HPSECURE Messages Error Message HLFM-3-SEND_FAIL: Failed to send RPC message, req [dec], [chars]. Explanation There is a local resource error or that too many outgoing messages are queued for the message class. [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 2 Message and Recovery Procedures IMAGEMGR 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. Explanation IGMP snooping is disabled on this VLAN. Do not enable the IGMP querier when IGMP snooping is disabled. [dec] is the VLAN IDs. Recommended Action Confirm that IGMP snooping is enabled both globally and on the VLAN.
Chapter 2 Message and Recovery Procedures IP_DEVICE_TRACKING Messages Error Message IMAGEMGR-6-AUTO_COPY_SW_INITIATED: Auto-copy-software process initiated for systems [bits: [hex]]. Explanation Systems with incompatible software have been detected in the switch stack. The stack now finds out whether or not software is available to be copied to the incompatible systems and whether or not it is appropriate to automatically copy the software. [bits [hex]] is the bit representation of the switch number.
Chapter 2 Message and Recovery Procedures MAC_MOVE Messages MAC_MOVE Messages This section contains the MAC_MOVE messages. Error Message MAC_MOVE-4-NOTIF: Host [enet] in vlan [dec] is flapping between port [chars] and port [chars]. Explanation The host is moving between the specified ports. [enet] is the Ethernet address of the host, [dec] is the VLAN ID, the first [chars] is the first port, and the second [chars] is the second port. Recommended Action Check your network for loops.
Chapter 2 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 2 Message and Recovery Procedures PIMSN Messages PIMSN Messages This section contains the PIMSN messages for the Protocol Independent Multicast (PIM) snooping feature. Error Message PIMSN-6-IGMPSN_GLOBAL: PIM Snooping global runtime mode [chars] due to IGMP Snooping [chars]. Explanation IGMP snooping must be enabled for PIM snooping to run. When IGMP snooping is disabled, PIM snooping is disabled. When IGMP snooping is re-enabled, PIM snooping is re-enabled.
Chapter 2 Message and Recovery Procedures PLATFORM_ENV Messages Error Message PLATFORM-3-PW_REC_HRPC_BAD_LENGTH: Received incompatible length (=[dec]) in set-password-recovery HRPC message from box [dec]. Explanation The system received an incompatible length parameter in the set-password-recovery HRPC message. This can be caused by a stack operating with incompatible software versions on different stack members. The first [dec] is the length and the second [dec] is the switch.
Chapter 2 Message and Recovery Procedures PLATFORM_FBM Messages Error Message PLATFORM_ENV-1-FAN_NOT_PRESENT: Fan is not present. Explanation The fan is not in the switch. Recommended Action If the fan is removable, remove and replace it into the switch. If the problem persists after insertion, replace the fan. Error Message PLATFORM_ENV-1-FRU_PS_ACCESS: [chars]. Explanation The switch failed to access the power supply due to a communication problem. [chars] is the error message.
Chapter 2 Message and Recovery Procedures PLATFORM_HCEF Message PLATFORM_HCEF Message This section has the Cisco Express Forwarding message. Error Message PLATFORM_HCEF-3-ADJ: [chars] Explanation This message appears when an unsupported feature is configured on a switch running Cisco IOS Release 12.2(25)SE. [chars] is the error message. Recommended Action Determine if a generic routing encapsulation (GRE) tunnel or the ip cef accounting global configuration command are configured.
Chapter 2 Message and Recovery Procedures PLATFORM _IPC Messages Error Message PLATFORM_HPLM-6-LABEL_START: VRF Label compaction started. Explanation The VRF label compaction process has started. Recommended Action No action is required. 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].
Chapter 2 Message and Recovery Procedures PLATFORM_IPv6_UCAST Message Error Message PLATFORM_IPC-3-MEMBER: [chars]. 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. Use the Bug Toolkit to look for similar reported problems.
Chapter 2 Message and Recovery Procedures PLATFORM_PBR Messages Error Message PLATFORM_PBR-3-INSTALL_FAIL: Policy route-map [chars] not installed in hardware. Explanation The PBR manager was unable to install the complete route-map in hardware, so the packets are forwarded to the CPU for processing. [chars] is the route-map. Recommended Action Simplify route-map configurations. For example, use the same route-map on multiple interfaces.
Chapter 2 Message and Recovery Procedures PLATFORM_PM Messages Error Message PLATFORM_PBR-4-SDM_MISMATCH: [chars] requires sdm template routing. Explanation The routing template is not enabled. [chars] is the text string PBR. Recommended Action Modify the SDM template to enable the routing template. Use the sdm prefer routing configuration command, and then reload the switch by using the reload privileged EXEC command. PLATFORM_PM Messages This section contains platform port manager (PM) messages.
Chapter 2 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]. Explanation The system is unable to allocate memory for RPC. [chars] describes the error message.
Chapter 2 Message and Recovery Procedures PLATFORM_RPC Messages Error Message PLATFORM_RPC-3-PERSISTENT_UNABLE_TO_SEND: System is consistently unable to send RPC message: [chars], paks_outstanding: [int]. Explanation The system is experiencing a persistent low-level transport failure in sending RPC messages.
Chapter 2 Message and Recovery Procedures PLATFORM_SPAN Messages Error Message PLATFORM_RPC-3-UNABLE_TO_SEND: System is unable to send RPC message: [chars], paks_outstanding: [int]. Explanation The system had a low-level transport failure when trying to send an RPC message.
Chapter 2 Message and Recovery Procedures PLATFORM_UCAST Messages Error Message PLATFORM_UCAST-3-ARP: [chars]. Explanation The ARP 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. Use the Bug Toolkit to look for similar reported problems.
Chapter 2 Message and Recovery Procedures PLATFORM_UCAST Messages Error Message PLATFORM_UCAST-3-HSRP: [chars]. 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. Use the Bug Toolkit to look for similar reported problems.
Chapter 2 Message and Recovery Procedures PLATFORM_VLAN Messages PLATFORM_VLAN Messages This section contains platform VLAN messages. Error Message PLATFORM_VLAN-3-LOCK_FAIL: Failed to lock vlan-id [dec], associated mapped vlan id value [dec]. Explanation The VLAN lock operation failed. This can occur if the VLAN is already active in the system or if the VLAN ID is not active. The first [dec] is the VLAN ID, and the second [dec] is the mapped-vlan-id (MVID).
Chapter 2 Message and Recovery Procedures PLATFORM_WCCP Messages PLATFORM_WCCP Messages This section contains platform Web Cache Communication Protocol (WCCP) messages. Error Message PLATFORM-WCCP-3-NO_LABEL: Cannot allocate WCCP Label Explanation The WCCP label could not be allocated. This means that the hardware cannot be programmed to implement WCCP redirection. Recommended Action Reduce the number of interfaces configured for WCCP redirection or policy based routing.
Chapter 2 Message and Recovery Procedures PM Messages Error Message PM-2-VLAN_ADD: Failed to add VLAN [dec] - [chars]. 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 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 2 Message and Recovery Procedures PM Messages Error Message PM-4-BAD_CARD_COOKIE: an invalid card 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 2 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 2 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). [chars] is the port where the threshold was exceeded.
Chapter 2 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 2 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 2 Message and Recovery Procedures PM Messages Error Message PM-4-PORT_BOUNCED: Port [chars] was bounced by [chars]. 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. Active ports in the link-down state are returned to the link-up state when the port is restarted (the re-activation event).
Chapter 2 Message and Recovery Procedures PORT_SECURITY Messages Error Message PM-4-VMPS_CFG: Dynamic access VLAN [dec] same as voice vlan on [chars]. 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 VLAN ID that is different from the voice VLAN ID.
Chapter 2 Message and Recovery Procedures Protocol Tunneling Messages Error Message PORT_SECURITY-6-VLAN_FULL: Vlan [dec] on port [chars] has reached its limit. Address [enet] has been removed. Explanation The voice VLAN is the same as the access VLAN, and the maximum number of MAC addresses reached the maximum limit 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.
Chapter 2 Message and Recovery Procedures QOSMGR Messages technical support and provide the representative with the gathered information. For more information about the online tools and about contacting HP, see the “Error Message Traceback Reports” section on page 1-5. Error Message QOSMGR-3-FILTERTYPE_INVALID: Internal Error Invalid Policy filtertype [dec]. Explanation An internal software error has occurred. [dec] is the invalid filter type identification.
Chapter 2 Message and Recovery Procedures QOSMGR Messages technical support and provide the representative with the gathered information. For more information about the online tools and about contacting HP, see the “Error Message Traceback Reports” section on page 1-5. Error Message QOSMGR-3-NULL_POLICER: Internal Error Invalid Policer. Explanation An internal software error has occurred. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 2 Message and Recovery Procedures QOSMGR Messages technical support and provide the representative with the gathered information. For more information about the online tools and about contacting HP, see the “Error Message Traceback Reports” section on page 1-5. Error Message QOSMGR-3-RESERVE_COUNT_ERROR: Reserved Count Exceeding total [dec]. Explanation An internal software error has occurred in the allocated reserved buffers. [dec] is the reserved count computed by the software.
Chapter 2 Message and Recovery Procedures QOSMGR Messages Error Message QOSMGR-4-CLASS_NOT_SUPPORTED: Classification is not supported in classmap [chars]. Explanation An unsupported match class-map configuration command was configured in a policy map and attached to an egress interface, or more than one match class-map command was configured. This is a hardware limitation. [chars] is the class-map name. Recommended Action Reconfigure the class map or the policy map.
Chapter 2 Message and Recovery Procedures RMON Messages Error Message QOSMGR-4-NOT_SUPPORTED: Action ’[chars]’ is not supported for a policymap attached to output side. 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 effect. This is a hardware limitation. [chars] is either the set or trust action.
Chapter 2 Message and Recovery Procedures SDM Messages Error Message RMON-5-RISINGTRAP: Rising trap is generated because the value of [chars] exceeded the rising-threshold value [dec]. Explanation A rising trap has been generated. The value of the specified MIB object has exceeded the rising threshold value. [chars] is the MIB object, and [dec] is the threshold value. Recommended Action Take appropriate action on the specified object.
Chapter 2 Message and Recovery Procedures SPANTREE Messages Error Message SPAN-3-SESS_HW_UNAVAIL: SPAN hardware resource not available [chars] Explanation The system could not allocate a SPAN hardware resource for the feature specified in the error message. A possible cause is that all SPAN source sessions are already in use. The system can be configured with a maximum of two SPAN source sessions or one RSPAN source session. [chars] is the unavailable resource.
Chapter 2 Message and Recovery Procedures SPANTREE Messages Error Message SPANTREE-2-BLOCK_BPDUGUARD_VP: Received BPDU on port [chars], vlan [dec] with BPDU Guard enabled. Disabling vlan. Explanation A bridge protocol data unit (BPDU) was received on the interface and VLAN specified in the error message. The spanning tree BPDU guard feature was enabled and configured to shut down the VLAN. As a result, the VLAN was placed in the error-disabled state. [chars] is the interface, and [dec] is the vlan.
Chapter 2 Message and Recovery Procedures SPANTREE Messages Error Message SPANTREE-2-LOOPGUARD_BLOCK: Loop guard blocking port [chars] on [chars]. Explanation The spanning-tree message age timer has expired because no 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 loopguard-inconsistent to prevent possible loops from being created.
Chapter 2 Message and Recovery Procedures SPANTREE Messages appropriate priority for the VLAN spanning tree, consistent with the CIST role on the port of the MST switch. The first [chars] is the MST switch, the second [chars] is the port, and the third [chars] is the PVST+ switch. The first [dec] is the VLAN ID, the second [dec] is the MST switch, and [enet] is the MST-switch MAC address.
Chapter 2 Message and Recovery Procedures SPANTREE Messages Error Message SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id [dec] on [chars] [chars]. 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.
Chapter 2 Message and Recovery Procedures SPANTREE Messages Error Message SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking [chars] on [chars]. Port consistency restored. Explanation The port VLAN ID or port type inconsistencies have been resolved, and spanning tree will unblock the listed interface of the listed spanning-tree instance as appropriate. The first [chars] is the interface, and the second [chars] is the spanning-tree instance. Recommended Action No action is required.
Chapter 2 Message and Recovery Procedures SPANTREE Messages 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. 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.
Chapter 2 Message and Recovery Procedures SPANTREE Messages Error Message SPANTREE-6-PORTADD_ALL_VLANS: [chars] added to all Vlans Explanation The interface has been added to all VLANs. [chars] is the added interface. Recommended Action No action is required. Error Message 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.
Chapter 2 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 2 Message and Recovery Procedures STACKMGR Messages Error Message STACKMGR-3-MSG_FAIL: Failed to retrieve stack message from port-asic [dec] in direction [dec]. Explanation The stack manager module failed to retrieve stack messages. The first [dec] is the ASIC ID, and the second [dec] is the direction. Recommended Action No action is required. Error Message STACKMGR-3-NORECORD: Switch removed event for switch [dec] with no switch record.
Chapter 2 Message and Recovery Procedures STORM_CONTROL Messages Error Message STACKMGR-4-SWITCH_ADDED_VM: Switch [dec] has been ADDED to the stack (VERSION_MISMATCH). Explanation A switch that has been added to the stack has a different software version. [dec] is the switch number. Recommended Action No action is required. Error Message STACKMGR-4-SWITCH_REMOVED: Switch [dec] has been REMOVED from the stack. Explanation The specified switch has been removed from the stack. [dec] is the switch number.
Chapter 2 Message and Recovery Procedures SUPERVISOR Messages Error Message STORM_CONTROL-3-SHUTDOWN: A packet storm was detected on [chars]. The interface has been disabled. Explanation The amount of traffic detected on the interface has exceeded the configured threshold values. Because the interface is configured to shut down if a packet storm event is detected, it has been placed in an error-disabled state. [chars] is the affected interface.
Chapter 2 Message and Recovery Procedures SUPQ Messages Error Message SUPQ-4-CPUHB_RECV_STARVE: [chars]. 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. Use the Bug Toolkit to look for similar reported problems.
Chapter 2 Message and Recovery Procedures SW_DAI Messages Error Message SUPQ-4-RECV_QUEUE_STUCK: Receive queue Stuck for asic [dec] queue [dec]. Explanation The system has detected that the receiving queue is not being cleared in a reasonable time. The first [dec] is the ASIC, and the second [dec] is the queue 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.
Chapter 2 Message and Recovery Procedures SW_DAI Messages Error Message SW_DAI-6-DHCP_SNOOPING_PERMIT: [dec] ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]). Explanation The switch has received ARP packets that have been permitted because the sender’s IP and MAC address match the DHCP snooping database for the received VLAN. The first [dec] is the number of valid ARP packets.
Chapter 2 Message and Recovery Procedures SW_MACAUTH Messages Error Message SW_DAI-4-SPECIAL_LOG_ENTRY: [dec] Invalid ARP packets [[time-of-day]]. Explanation The switch has received ARP packets considered invalid by ARP inspection. The packets are erroneous, and their presence might show attempted man-in-the-middle attacks in the network.
Chapter 2 Message and Recovery Procedures SW_MATM Error Message SW_MACAUTH-5-CLEAR_TABLE: MAC Authentication Table Cleared Explanation The MAC authentication table was cleared. Recommended Action No action is required. 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.
Chapter 2 Message and Recovery Procedures SW_VLAN Messages Error Message SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: [chars] no longer detected on port [chars], operational port trust state is now untrusted. Explanation A trusted boundary lost contact with a trusted device and has set the port trust state to untrusted. The first [chars] is the trusted device, and the second [chars] is the port Recommended Action No action is required. SW_VLAN Messages This section contains the VLAN manager messages.
Chapter 2 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 2 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 2 Message and Recovery Procedures SW_VLAN Messages Error Message SW_VLAN-4-IFS_FAILURE: VLAN manager encountered file operation error call = [chars] / file = [chars] / code = [dec] ([chars]) / bytes transferred = [dec]. 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 function call name, and the second [chars] is the file name.
Chapter 2 Message and Recovery Procedures SW_VLAN Messages contact HP technical support and provide the representative with the gathered information. For more information about the online tools and about contacting HP, see the “Error Message Traceback Reports” section on page 1-5. Error Message SW_VLAN-4-VTP_INTERNAL_ERROR: VLAN manager received an internal error [dec] from vtp function [chars] [chars]. Explanation The VLAN manager received an unexpected error code from the VTP configuration software.
Chapter 2 Message and Recovery Procedures SW_VLAN Messages Error Message SW_VLAN-4-VTP_SEM_BUSY: VTP semaphore is unavailable for function [chars]. Semaphore locked by [chars]. Explanation The VTP database is not available. You should access the VTP database later. The first [chars] is the function name that you want to configure, and the second [chars] is the function name that is using the VTP database. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 2 Message and Recovery Procedures TCAMMGR Messages STANDBY received a checkpoint message with a sequence number that does not match the expected sequence number. The first [dec] is the expected checkpoint message sequence number, and the second [dec] is the received checkpoint message sequence 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 using the Output Interpreter.
Chapter 2 Message and Recovery Procedures TCAMMGR Messages Error Message TCAMMGR-3-HANDLE_ERROR: cam handle [hex] is invalid. 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. Use the Bug Toolkit to look for similar reported problems.
Chapter 2 Message and Recovery Procedures UDLD Messages Error Message TCAMMGR-3-REGMASK_ERROR: invalid cam region [dec] mask [dec] pair. Explanation A caller attempted to install an entry with an invalid mask for the region. Only a predetermined set of masks is allowed in a region. The first [dec] is the region, and the second [dec] is the mask. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 2 Message and Recovery Procedures UDLD Messages Error Message UDLD-3-UDLD_INTERNAL_ERROR: UDLD internal error [chars]. Explanation A software check failed during UDLD processing. [chars] is a description of the internal 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 2 Message and Recovery Procedures UFAST_MCAST_SW Messages Error Message UDLD-6-UDLD_PORT_RESET: UDLD reset interface [chars]. 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.
Chapter 2 Message and Recovery Procedures VQPCLIENT Messages technical support and provide the representative with the gathered information. For more information about the online tools and about contacting HP, see the “Error Message Traceback Reports” section on page 1-5. Error Message VQPCLIENT-2-DENY: Host [enet] denied on interface [chars]. Explanation The VLAN Membership Policy Server (VMPS) has denied access for the given host MAC address to an interface.
Chapter 2 Message and Recovery Procedures VQPCLIENT Messages Error Message VQPCLIENT-2-SHUTDOWN: Interface [chars] shutdown by VMPS. Explanation The VMPS has directed that an interface be shut down. [chars] is the interface name. Recommended Action No action is normally required. If you think that the port should not have been shut down, verify the configuration on the VMPS. Error Message VQPCLIENT-2-TOOMANY: Interface [chars] shutdown by active host limit.
Chapter 2 Message and Recovery Procedures VQPCLIENT Messages Error Message VQPCLIENT-7-PROBE: Probing primary server [IP_address]. Explanation The system is trying to reestablish connectivity with the primary VMPS at the given IP address. Recommended Action This is a debug message only. No action is required. Error Message VQPCLIENT-7-RECONF: Reconfirming VMPS responses. Explanation The switch is reconfirming all responses with the VMPS. Recommended Action This is only a debug message.
Chapter 2 Message and Recovery Procedures VQPCLIENT Messages Cisco Catalyst Blade Switch 3120 for HP System Message Guide 2-108 OL-12249-01
I N D EX Numerics C 10-Gigabit Ethernet module messages CFGMGR messages See GBIC_SECURITY_CRYPT messages Cisco Network Assistant See Network Assistant requirements See GBIC_SECURITY_UNIQUE messages 10-Gigabit Ethernet module security messages 2-9 CLS_ACC 2-11 See GBIC_SECURITY_CRYPT messages codes See GBIC_SECURITY_UNIQUE messages configuration, initial 1-1 See getting started guide and hardware installation guide See GBIC_SECURITY messages configuration manager messages A See CFGMGR mes
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 2-35 2-36 2-33 Gigabit Interface Converter security messages See DTP messages See GBIC_SECURITY_CRYPT messages See GBIC_SECURITY_UNIQUE messages E See GBIC_SECURITY messages EC messages guide 2-27 ETHCNTR messages audience 2-31 vii purpose of EtherChannel con
Index messages (continued) L MAC_MOVE LACP messages PHY See EC messages 2-45 PIMSN Link Aggregation Control Protocol messages See EC messages 2-45 2-47 PLATFORM 2-47 PLATFORM_FBM local forwarding manager messages 2-49 PLATFORM_HPLM See HLFM messages PLATFORM_IPC 2-51 PLATFORM_PBR 2-52 PLATFORM_PM M 2-54 PLATFORM_RPC MAC_MOVE messages See SW_MACAUTH messages 1-2 message mnemonic code 2-60 PLATFORM_WCCP 2-61 2-61 QOSMGR 2-3 BACKUP_INTERFACE BSPATCH RMON 2-7 SDM 2-8 2-75
Index messages, transceiver platform pseudo label manager messages 2-7 message severity levels description table See PLATFORM_HPLM messages PM messages 1-4 2-61 policy-based routing messages 1-4 message text definition mmemonic code See PLATFORM_PBR messages 1-4 PORT_SECURITY messages 1-4 2-69 Port Aggregation Protocol messages See EC messages N port manager messages Network Assistant requirements See PM messages viii port manager messages, platform notes date/time stamp designation d
Index SFP security messages T See GBIC_SECURITY_CRYPT messages See GBIC_SECURITY_UNIQUE messages tables message severity levels See GBIC_SECURITY messages variable fields small form-factor pluggable module messages 1-4 1-5 See GBIC_SECURITY_CRYPT messages TAC, contacting See GBIC_SECURITY_UNIQUE messages TCAMMGR messages See GBIC_SECURITY messages ternary content addressable memory manager messages SPAN messages 1-6 2-100 See TCAMMGR messages 2-76 spanning-tree fast-convergence messages
Index VQPCLIENT messages 2-104 VTP messages See SW_VLAN messages W WCCP messages 2-61 Cisco Catalyst Blade Switch 3120 for HP System Message Guide IN-6 OL-12249-01
