Cisco Catalyst Blade Switch 3040 for FSC System Message Guide Cisco IOS Release 12.2(25)SEF2 September 2006 Corporate 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 ix Cisco.
Contents DOT1X_SWITCH Messages DTP Messages 2-15 DWL Messages EC Messages 2-13 2-17 2-17 ETHCNTR Messages 2-21 GBIC_SECURITY Messages 2-21 GBIC_SECURITY_CRYPT Messages 2-23 GBIC_SECURITY_UNIQUE Messages HARDWARE Messages HLFM Messages 2-24 2-24 2-26 IDBMAN Messages 2-27 IGMP_QUERIER Messages 2-29 IP_DEVICE_TRACKING_HA Messages MAC_LIMIT Messages 2-31 MAC_MOVE Messages 2-31 PHY Messages 2-32 PLATFORM Messages 2-33 PLATFORM_PM Messages 2-34 PLATFORM_VLAN Messages PM Messages 2-3
Contents UFAST_MCAST_SW Messages VQPCLIENT Messages 2-71 2-71 INDEX Cisco Catalyst Blade Switch 3040 for FSC System Message Guide OL-10697-01 v
Contents Cisco Catalyst Blade Switch 3040 for FSC System Message Guide vi OL-10697-01
Preface Audience This guide is for the networking professional managing the Cisco Catalyst Blade Switch 3040 for FSC, 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.
Preface Related Publications • Braces ({ }) group required choices, and vertical bars ( | ) separate the alternative elements. • Braces and vertical bars within square brackets ([{ | }]) mean a required choice within an optional element. 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.
Preface Obtaining Documentation Obtaining Documentation Cisco documentation and additional literature are available on Cisco.com. This section explains the product documentation resources that Cisco offers. Cisco.com You can access the most current Cisco documentation at this URL: http://www.cisco.com/techsupport You can access the Cisco website at this URL: http://www.cisco.com You can access international Cisco websites at this URL: http://www.cisco.com/public/countries_languages.
Preface Cisco Product Security Overview Cisco Product Security Overview Cisco provides a free online Security Vulnerability Policy portal at this URL: http://www.cisco.com/en/US/products/products_security_vulnerability_policy.
Preface Product Alerts and Field Notices Product Alerts and Field Notices Modifications to or updates about Cisco products are announced in Cisco Product Alerts and Cisco Field Notices. You can receive Cisco Product Alerts and Cisco Field Notices by using the Product Alert Tool on Cisco.com. This tool enables you to create a profile and choose those products for which you want to receive information. To access the Product Alert Tool, you must be a registered Cisco.com user. (To register as a Cisco.
Preface Obtaining Technical Assistance and then click the Technical Support & Documentation.radio button. To provide feedback about the Cisco.com website or a particular technical document, click Contacts & Feedback at the top of any Cisco.com web page. Submitting a Service Request Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.
Preface Obtaining Additional Publications and Information Obtaining Additional Publications and Information Information about Cisco products, technologies, and network solutions is available from various online and printed sources. • The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners.
Preface Obtaining Additional Publications and Information Cisco Catalyst Blade Switch 3040 for FSC System Message Guide xiv OL-10697-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 Error Message Traceback Reports Table 1-1 Message Severity Levels (continued) Severity Level Description 2 – critical Critical condition. 3 – error Error condition. 4 – warning Warning condition. 5 – notification Normal but significant condition. 6 – informational Informational message only. 7 – debugging Message that appears during debugging only. • MNEMONIC is a code that uniquely identifies the message.
Chapter 1 System Message Overview Error Message Traceback Reports 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. These online tools also provide more information about system error messages.
Chapter 1 System Message Overview Error Message Traceback Reports Cisco Catalyst Blade Switch 3040 for FSC System Message Guide 1-4 OL-10697-01
C H A P T E R 2 Message and Recovery Procedures This chapter describes the switch system messages in alphabetical order by facility. Within each facility, the messages are listed by severity levels 0 to 7: 0 is the highest severity level, and 7 is the lowest severity level. Each message is followed by an explanation and a recommended action.
Chapter 2 Message and Recovery Procedures ACLMGR Messages • PLATFORM_PM Messages, page 2-34 • PLATFORM_VLAN Messages, page 2-35 • PM Messages, page 2-36 • PORT_SECURITY Messages, page 2-43 • QOSMGR Messages, page 2-44 • RMON Messages, page 2-49 • SPAN Messages, page 2-49 • SPANTREE Messages, page 2-50 • SPANTREE_FAST Messages, page 2-57 • SPANTREE_VLAN_SW Messages, page 2-58 • STORM_CONTROL Messages, page 2-58 • SUPERVISOR Messages, page 2-59 • SUPQ Messages, page 2-59 • SW_MAC
Chapter 2 Message and Recovery Procedures ACLMGR Messages Error Message ACLMGR-2-NOVLB: Cannot create memory block for VLAN [dec]. Explanation The ACL manager could not save per-VLAN information needed for its correct operation. Some per-interface features, such as access groups or VLAN maps, will not be configured correctly. [dec] is the VLAN ID. Recommended Action Use a less complicated configuration that requires less memory.
Chapter 2 Message and Recovery Procedures ACLMGR Messages Error Message ACLMGR-3-INSERTFAIL: Insert of access-map [chars] #[dec] into [chars] label [dec] failed. Explanation The system ran out of CPU memory when trying to merge sections of an access map. The first [chars] is the map name, and the second [chars] is the direction in which the map was applied. The first [dec] is the entry number, and the second [dec] is the label number.
Chapter 2 Message and Recovery Procedures ACLMGR Messages Error Message ACLMGR-3-NOLABEL: Cannot allocate [chars] label for interface [chars]. Explanation The ACL 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 2 Message and Recovery Procedures BACKUP_INTERFACE 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 1-2. Error Message ACLMGR-3-UNLOADING: Unloading [chars] label [dec] feature.
Chapter 2 Message and Recovery Procedures CMP Messages Error Message BSPATCH-1-PATCHED: Boot Loader patch ([chars]) installed. Explanation A boot loader patch is installed successfully. [chars] is the SDRAM refresh timer register setting. 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. Use the Bug Toolkit to look for similar reported problems.
Chapter 2 Message and Recovery Procedures DHCP_SNOOPING Messages Error Message CMP-5-MEMBER_CONFIG_UPDATE: Received member configuration from member [dec]. Explanation The active or standby command switch received a member configuration. [dec] is the member number of the sender. Recommended Action No action is required. Error Message CMP-5-MGMT_VLAN_CHNG: The management vlan has been changed to [dec]. Explanation The management VLAN has changed. [dec] is the new management VLAN ID.
Chapter 2 Message and Recovery Procedures DHCP_SNOOPING Messages Error Message DHCP_SNOOPING-4-AGENT_OPERATION_FAILED: DHCP snooping binding transfer failed. [chars]. Explanation The DHCP snooping binding transfer process failed because of the specified reason for failure. [chars] is the reason for failure. Recommended Action No action is required. Error Message DHCP_SNOOPING-4-AGENT_OPERATION_FAILED_N: DHCP snooping binding transfer failed ([dec]). [chars].
Chapter 2 Message and Recovery Procedures DHCP_SNOOPING Messages Error Message DHCP_SNOOPING-4-IP_SOURCE_BINDING_PVLAN_WARNING: IP source filter may not take effect on secondary vlan [dec] where IP source binding is configured. [chars]. Explanation If private VLANs are configured, the IP-source-guard filter on the primary VLAN automatically propagates to all secondary VLANs. [dec] is the secondary VLAN, and [chars] is the warning. Recommended Action No action is required.
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 the IEEE 802.1x authentication. Recommended Action Reduce other system activity to reduce memory demands. Error Message DOT1X-4-PROC_START_ERR: Dot1x unable to start. Explanation The system failed to start the IEEE 802.1x process.
Chapter 2 Message and Recovery Procedures DOT1X_SWITCH Messages Error Message DOT1X-5-SECURITY_VIOLATION: Security violation on interface [chars], New MAC address [enet] Explanation The port on the specified interface has been disabled because of a security violation. When an interface is configured in single-host mode, any new host that is detected on the interface is treated as a security violation. [chars] is the interface number, and [enet] is the MAC address of the new host.
Chapter 2 Message and Recovery Procedures DOT1X_SWITCH Messages Error Message DOT1X_SWITCH-5-ERR_SPAN_DST_PORT: Assigning a dot1x VLAN [dec] to a SPAN destination port [chars] is not allowed Explanation You cannot assign an IEEE 802.1x VLAN to a port that is configured as a SPAN destination port. Recommended Action Update the configuration to use a different VLAN, or disable the RSPAN VLAN. Error Message DOT1X_SWITCH-5-ERR_VLAN_EQ_VVLAN: Data VLAN [dec] on port [chars] cannot equal to Voice VLAN.
Chapter 2 Message and Recovery Procedures DTP Messages Error Message DOT1X_SWITCH-5-ERR_VLAN_PROMISC_PORT: Assigning a dot1x VLAN [dec] to a promiscuous port [chars] is not allowed Explanation An attempt was made to assign a VLAN to a supplicant on a promiscuous port, which is not allowed. [dec] is the VLAN ID and [chars] is the port. Recommended Action Change the port mode to a nonpromiscuous port.
Chapter 2 Message and Recovery Procedures DTP Messages Error Message DTP-4-UNKN_ERR: An unknown operational error occurred. Explanation The system is unable to negotiate trunks because an internal operation generated an unexpected error. Recommended Action Reload the switch by using the reload privileged EXEC command. Error Message DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on port [chars] because of VTP domain mismatch.
Chapter 2 Message and Recovery Procedures DWL Messages DWL Messages This section contains the down-when-looped (DWL) message. This feature disables an interface when a loopback is detected. Error Message DWL-3-LOOP_BACK_DETECTED: Loop-back detected on [chars]. Explanation There is a loopback on the specified port. The cause might be a Token-Ring Type-1 cable connected to the port or a misconfiguration in the network. Recommended Action Correct the problem that is causing the loopback condition.
Chapter 2 Message and Recovery Procedures EC Messages Error Message EC-5-CANNOT_BUNDLE1: Port-channel [chars] is down, port [chars] will remain stand-alone. Explanation The state of the port channel (EtherChannel) is down, for example, the port channel might be administratively disabled or disconnected. The physical interface cannot join the bundle (EtherChannel) until the state of the port channel is up. The first [chars] is the EtherChannel. The second [chars] is the port number.
Chapter 2 Message and Recovery Procedures EC Messages Error Message EC-5-ERRPROT: Channel protocol mismatch for interface [chars] in group [dec]: the interface can not be added to the channel group. Explanation The interface cannot be added to the channel group with the specified mode. [chars] is the interface, and [dec] is the channel group. Recommended Action Change the channel group or the mode for the interface.
Chapter 2 Message and Recovery Procedures EC Messages Error Message EC-5-STAYDOWN: [chars] will remain down as its port-channel [chars] is admin-down. Explanation The administrative state of the aggregation port overrides that of the affected port. If the aggregation port is administratively down, all ports in the aggregation port are forced to be administratively down. The first [chars] is the physical interface, and the second [chars] is the EtherChannel.
Chapter 2 Message and Recovery Procedures ETHCNTR Messages ETHCNTR Messages This section contains the Ethernet controller messages. These messages are a result of a failure of the switch software when trying to program the hardware and lead to incorrect switch behavior. 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 considered as a loopback.
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 GBIC_SECURITY_CRYPT Messages This section contains the Cisco GBIC module and SFP module security messages. The switch recognizes the module as a Cisco module but identifies another problem with it. Note The switch supports SFP modules and does not support GBIC modules. Although the error message text refers to GBIC interfaces and modules, the messages from the switch actually refer to the SFP module interfaces and modules.
Chapter 2 Message and Recovery Procedures GBIC_SECURITY_UNIQUE Messages GBIC_SECURITY_UNIQUE Messages This section contains the Cisco GBIC module and SFP module security messages that identify whether the module is unique. Note The switch supports SFP modules and does not support GBIC modules. Although the error message text refers to GBIC interfaces and modules, the messages from the switch actually refer to the SFP module interfaces and modules.
Chapter 2 Message and Recovery Procedures HARDWARE Messages Error Message HARDWARE-3-INDEX_ERROR: Index value [dec] is invalid. Explanation The index into the hardware table is out-of-range. [dec] is the index 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 HLFM Messages 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. Explanation An attempt was made to free a MAC address before releasing all references to it. [enet] is the MAC address, 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 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]). Explanation There is an internal error that caused an invalid aggregate port to be used by the software. The first [chars] is the name of the function where the error occurred.
Chapter 2 Message and Recovery Procedures IDBMAN Messages Error Message IDBMAN-3-INVALIDPORT: [chars]: trying to use invalid port number [dec] ( Max [dec] ). Explanation There is an internal error that caused an invalid port number to be used by the software. [chars] is the interface name. The first [dec] is the port number that is invalid, and the second [dec] is the maximum allowed value for a port number. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 2 Message and Recovery Procedures IGMP_QUERIER 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 1-2. Error Message IDBMAN-3-VLANNOTSET: [chars]: Vlan [dec] not set since it already has Vlan [dec]. Explanation An interface VLAN was not set to the requested value because of an internal error.
Chapter 2 Message and Recovery Procedures IP_DEVICE_TRACKING_HA 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 MAC_LIMIT Messages MAC_LIMIT Messages This section contains the MAC_LIMIT messages, which describe the entries in the MAC address table. Error Message MAC_LIMIT-4-DROP: Vlan [dec] with Configured limit = [dec] has currently [dec] Entries. Explanation The number of MAC address table entries for a VLAN is less than or equal to the maximum number allowed.
Chapter 2 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]. Explanation A transceiver that should not be used is in the specified interface. Recommended Action Remove the transceiver. If the transceiver is a Cisco device, contact your Cisco technical support representative.
Chapter 2 Message and Recovery Procedures PLATFORM Messages Error Message PHY-4-SFP_NOT_SUPPORTED: The SFP in [chars] is not supported Explanation This small form-factor pluggable (SFP) module type is not supported on this switch. [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. Use the Bug Toolkit to look for similar reported problems.
Chapter 2 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 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 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. Explanation The available memory for the switch processor is low.
Chapter 2 Message and Recovery Procedures PM 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 1-2. Error Message PM-4-BAD_APP_ID: an invalid application id ([dec]) was detected. Explanation The port manager detected an invalid request. [dec] is the application ID.
Chapter 2 Message and Recovery Procedures PM 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 1-2. Error Message PM-4-BAD_COOKIE: [chars] was detected. Explanation The port manager detected an invalid request. [chars] is the invalid request.
Chapter 2 Message and Recovery Procedures PM 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 1-2. Error Message PM-4-BAD_VLAN_COOKIE: an invalid vlan cookie was detected. Explanation The port manager detected an invalid request.
Chapter 2 Message and Recovery Procedures PM Messages Error Message PM-4-ERR_RECOVER: Attempting to recover from [chars] err-disable state on [chars]. Explanation The port manager is attempting to bring the interface up after taking it down to the error-disabled state. The first [chars] is the error, and the second [chars] is the affected interface. Recommended Action 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 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 QOSMGR Messages Error Message PORT_SECURITY-6-VLAN_REMOVED: VLAN [dec] is no longer allowed on port [chars]. Its port security configuration has been removed. Explanation The VLAN is not allowed on the trunk port and is removed from the trunk port configuration. [dec] is the VLAN ID, and [chars] is the switch port assigned to the VLAN. Recommended Action No action is required. QOSMGR Messages This section contains the quality of service (QoS) manager messages.
Chapter 2 Message and Recovery Procedures QOSMGR Messages Error Message QOSMGR-3-NO_POLICER_QOSLABEL: Creating port Class Label Failed. 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. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error.
Chapter 2 Message and Recovery Procedures QOSMGR Messages Error Message QOSMGR-3-POLICYMAP_NOT_FOUND: Cannot find policymap for [chars]. Explanation An internal software error has occurred. [chars] is the policy-map name. Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error.
Chapter 2 Message and Recovery Procedures QOSMGR Messages Error Message QOSMGR-3-VMRSEQ_INVALID: Internal Error Invalid VMR sequence. 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. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error.
Chapter 2 Message and Recovery Procedures QOSMGR Messages Error Message QOSMGR-4-HARDWARE_NOT_SUPPORTED: Hardware limitation has reached for policymap [chars]. 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. Recommended Action Reconfigure the class map or the policy map, and reduce the number of QoS ACLs.
Chapter 2 Message and Recovery Procedures RMON Messages Error Message QOSMGR-4-POLICER_POLICY_NOT_SUPPORTED: Number of policers has exceeded per policy hardware limitation for policymap [chars]. Explanation The policy-map configuration has exceeded the limitation of the hardware. You configured more policers in a policy map (by using the police or police aggregate policy-map class configuration command) than supported. [chars] is the policy-map name.
Chapter 2 Message and Recovery Procedures SPANTREE Messages Error Message SPAN-3-UNKN_ERR_PORT: An internal error occurred when configuring SPAN on port [chars]. Explanation SPAN detected an error in its internal operation. [chars] is the interface. Recommended Action The error might be transient. Try the SPAN operation again. If the second attempt also fails, reload the switch by using the reload privileged EXEC command to complete the operation.
Chapter 2 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 2 Message and Recovery Procedures SPANTREE Messages feature is mainly used to detect unidirectional links. The first [chars] is the loopguard state (enable or disable), the second [chars] is the interface name, and the third [chars] is the spanning-tree instance. Recommended Action Verify that this is the desired configuration for the listed interface. Correct it if this is not the desired configuration; otherwise, no further action is required.
Chapter 2 Message and Recovery Procedures SPANTREE Messages Error Message SPANTREE-2-RECV_1Q_NON_1QTRUNK: Received 802.1Q BPDU on non 802.1Q trunk [chars] [chars]. Explanation The listed interface on which a Shared Spanning Tree Protocol (SSTP) BPDU was received was in trunk mode but was not using IEEE 802.1Q encapsulation. The first [chars] is the port, and the second [chars] is the VLAN.
Chapter 2 Message and Recovery Procedures SPANTREE Messages occurrences. When the inaccurate BPDUs have been stopped, the interfaces automatically recover and resume normal operation. Make sure that it is appropriate to have root guard enabled on the interface. Error Message SPANTREE-2-ROOTGUARD_CONFIG_CHANGE: Root guard [chars] on port [chars] on [chars]. Explanation The spanning-tree root guard configuration for the listed interface has changed.
Chapter 2 Message and Recovery Procedures SPANTREE Messages error in the platform-specific code, which causes it to request more or less bits than are possible. The first [dec] is the number of bits for the port number, and the second and third [dec] describe the valid range. Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter.
Chapter 2 Message and Recovery Procedures SPANTREE 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 1-2. Error Message SPANTREE-5-EXTENDED_SYSID: Extended SysId [chars] for type [chars]. Explanation The extended system ID feature is either enabled or disabled for the given type of spanning tree.
Chapter 2 Message and Recovery Procedures SPANTREE_FAST Messages Error Message SPANTREE-7-BLOCK_PORT_TYPE: Blocking [chars] on [chars]. Inconsistent port type. Explanation The listed interface is being held in the spanning-tree blocking state until the port-type inconsistency is resolved. The first [chars] is the interface, and the second [chars] is the spanning-tree instance.
Chapter 2 Message and Recovery Procedures SPANTREE_VLAN_SW Messages SPANTREE_VLAN_SW Messages The section contains the per-VLAN spanning-tree-specific message. Error Message SPANTREE_VLAN_SW-2-MAX_INSTANCE: Platform limit of [dec] STP instances exceeded. No instance created for [chars] (port [chars]). Explanation The number of currently active VLAN spanning-tree instances has reached a platform-specific limit.
Chapter 2 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]. Explanation An internal error occurred in the supervisor ASIC. [chars] is the detailed error message. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 2 Message and Recovery Procedures SUPQ Messages Error Message SUPQ-4-CPUHB_SLOW_TRANSMIT: [chars]. Explanation The system is warning you about a slowdown of the transmit interface. [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_MACAUTH Messages SW_MACAUTH Messages This section contains the MAC address authentication messages. Error Message SW_MACAUTH-4-UNAUTH_MAC: Unauthenticated MAC [enet] on port [chars] Explanation The switch has received an unauthenticated MAC address on the specified port. [enet] is the unauthenticated MAC address, and [chars] is the port. Recommended Action No action is required.
Chapter 2 Message and Recovery Procedures SW_VLAN 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 1-2. Error Message SW_VLAN-3-VTP_PROTOCOL_ERROR: VTP protocol code internal error [chars].
Chapter 2 Message and Recovery Procedures SW_VLAN Messages Error Message SW_VLAN-4-BAD_VLAN_CONFIGURATION_FILE_VERSION: VLAN configuration file contained unknown file version [dec]. Explanation The VLAN configuration file read by the VLAN manager contained an unrecognized file version number, which might mean an attempt to regress to an older version of the VLAN manager software. [dec] is the file version number.
Chapter 2 Message and Recovery Procedures SW_VLAN 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 1-2. Error Message SW_VLAN-4-IFS_FAILURE: VLAN manager encountered file operation error call = [chars] / file = [chars] / code = [dec] ([chars]) / bytes transferred = [dec].
Chapter 2 Message and Recovery Procedures SW_VLAN Messages Error Message SW_VLAN-4-VLAN_CREATE_FAIL: Failed to create VLANs [chars]: [chars]. Explanation The specified VLANs could not be created. The port manager might not have completed the VLAN creation requests because the VLANs already exist as internal VLANs. The first [chars] is the VLAN ID, and the second [chars] describes the error.
Chapter 2 Message and Recovery Procedures SW_VLAN Messages Error Message SW_VLAN-4-VTP_INVALID_EVENT_DATA: VLAN manager received bad data of type [chars] value [dec] while being called to handle a [chars] event. Explanation The VLAN manager received invalid data from the VTP configuration software. The first [chars] is the data type, [dec] is the value of that data, and the second [chars] is the VTP event. Recommended Action Copy the message exactly as it appears on the console or in the system log.
Chapter 2 Message and Recovery Procedures SWITCH_QOS_TB Messages Error Message SW_VLAN-6-VTP_MODE_CHANGE: VLAN manager changing device mode from [chars] to [chars]. Explanation An automatic VTP mode device change occurred upon receipt of a VLAN configuration database message containing more than a set number of VLANs. The first [chars] is the previous mode, and the second [chars] is the current mode. Recommended Action No action is required.
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 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 1-2. Error Message VQPCLIENT-2-DENY: Host [enet] denied on interface [chars].
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 a debug message only.
I N D EX publication A text vii vii abbreviations char, variable field chars, variable field dec, variable field 1-2 D 1-2 1-2 date/time stamp designations 2-1 enet, variable field 1-2 device manager requirements viii hex, variable field 1-2 DHCP_SNOOPING messages inet, variable field 1-2 DHCP messages access control list manager messages See ACLMGR messages ACLMGR messages audience 2-2 2-8 2-8 documentation, related viii document conventions vii DOT1X (IEEE 802.
Index interface description block manager messages F See IDBMAN messages facility codes IP_DEVICE_TRACKING_HA messages in system messages 2-30 1-1 Flex Link messages L See BACKUP_INTERFACE messages See backup interface messages format of system messages LACP messages 1-1 See EC messages Link Aggregation Control Protocol messages See EC messages G local forwarding manager messages GBIC_SECURITY_CRYPT messages GBIC_SECURITY_UNIQUE messages GBIC_SECURITY messages 2-23 See HLFM messages 2-24
Index HLFM 2-26 IDBMAN N 2-27 IEEE 802.
Index Switched Port Analyzer messages R See SPAN messages remote network monitoring messages system message format 1-1 See RMON messages requirements device manager viii RMON messages 2-49 T tables message severity levels S severity levels description table variable fields 1-2 TAC, contacting 1-3 TCAMMGR messages 1-1 1-1 2-67 ternary content addressable memory manager messages 1-1 See TCAMMGR messages SFP security messages time stamp information 1-1 See GBIC_SECURITY_CRYPT messages
Index VQPCLIENT messages 2-71 VTP messages See SW_VLAN messages Cisco Catalyst Blade Switch 3040 for FSC System Message Guide OL-10697-01 IN-5
Index Cisco Catalyst Blade Switch 3040 for FSC System Message Guide IN-6 OL-10697-01
Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions. This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed. Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions.
