IBM ERserver. System Message Guide. Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter

Transcription

1 IBM ERserver Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter System Message Guide Cisco IOS Release 12.1(14)AY

2 Note: Before using this information and the product it supports, read the general information in Appendix B. Getting help and technical assistance and Appendix C. Notices.12 1First Edition (June 2004) 2 Copyright International Business Machines Corporation All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents Preface Audience Purpose Conventions Related Publications Chapter 1. System Message Overview How to Read System Messages Error Message Traceback Reports Chapter 2. Message and Recovery Procedures CIGESM Messages CMP Messages DOT1X Messages DTP Messages EC Messages ETHCNTR Messages HWMATM_MOD Messages PLATFORM_CAT2950 Messages PLATFORM_CATALYST2950 Messages PM Messages PORT SECURITY Messages SPAN Messages SPANTREE Messages SPANTREE_FAST Messages SPANTREE_VLAN_SWITCH Messages STORM_CONTROL Messages SW_VLAN Messages UDLD Messages UFAST_MCAST_SW Messages Appendix A. Security and QoS Configuration Messages Appendix B. Getting help and technical assistance Before you call Using the documentation Getting help and information from the World Wide Web Software service and support Hardware service and support Appendix C. Notices Edition notice Trademarks Index Copyright IBM Corp

4 2 BookTitle change in special and import

5 Preface Audience This guide is for the networking professional managing the Cisco Systems Intelligent Gigabit Ethernet Switch Module, hereafter referred to as the switch. Before using this guide, you should have experience working with the switch and its software features. Purpose This guide describes only the switch-specific system messages that you might encounter. This guide does not describe how to install your switch or how to configure software features on your switch. It also does not provide detailed information about commands that have been created or changed for use by the switch. For hardware installation information, refer to the hardware installation guide that shipped with your switch. For software information, refer to the software configuration guide and the command reference for this release. Conventions Related Publications This publication uses these conventions to convey instructions and information: Command descriptions use these conventions: Commands and keywords are in boldface text. Arguments for which you supply values are in italic. Square brackets ([ ]) mean optional elements. 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 screen font. Nonprinting characters, such as passwords or tabs, are in angle brackets (< >). Notes use this convention: Note: Means reader take note. Notes contain helpful suggestions or references to materials not in this manual. In addition to this document, the following related documentation comes with the Gigabit Ethernet switch module: Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM eserver BladeCenter System Release Notes Note: Switch requirements and procedures for initial configurations and software upgrades tend to change and therefore appear only in the release notes. Before Copyright IBM Corp

6 installing, configuring, or upgrading the switch, refer to the release notes for the latest information. Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM eserver BladeCenter System Command Reference (order number TBD) This document is in PDF form on the IBM BladeCenter Documentation CD. It includes: Command line interface (CLI) modes Command line interface commands and examples Syntax description Defaults Command history Usage guidelines Related commands Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM eserver BladeCenter Software Configuration Guide This Cisco document is in PDF on the IBM BladeCenter Documentation CD. It contains software configuration information for the Gigabit Ethernet switch module. It provides: Configuration instructions for your Gigabit Ethernet switch module Information about features Information about getting help Guidance for planning, implementing, and administering LAN operating system software Usage examples Troubleshooting information for your Gigabit Ethernet switch module Cisco Intelligent Gigabit Ethernet Switch Module for the IBM eserver BladeCenter Installation Guide This document contains installation and configuration instructions for the Gigabit Ethernet switch module. This document also provides general information about your Gigabit Ethernet switch module, including warranty information, and how to get help. This document is also on the IBM BladeCenter Documentation CD. eserver BladeCenter Type 8677 Installation and User s Guide This document is in PDF on the IBM BladeCenter Documentation CD. It contains general information about your BladeCenter unit, including: Information about features How to set up, cable, and start the BladeCenter unit How to install options in the BladeCenter unit How to configure the BladeCenter unit How to perform basic troubleshooting of the BladeCenter unit How to get help BladeCenter Management Module User s Guide This document is in PDF on the IBM BladeCenter Documentation CD. It provides general information about the management module, including: Information about features How to start the management module 4 Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter System Message Guide

7 How to install the management module How to configure and use the management module BladeCenter HS20 Installation and User s Guide (for each blade server type) These documents are in PDF on the IBM BladeCenter Documentation CD. Each provides general information about a blade server, including: Information about features How to set up and start your blade server How to install options in your blade server How to configure your blade server How to install an operating system on your blade server How to perform basic troubleshooting of your blade server How to get help Cisco IOS Release 12.1 documentation at Cisco IOS Release 12.2 documentation at Preface 5

8 6 Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter System Message Guide

9 Chapter 1. System Message Overview This guide describes the switch-specific system messages. During operation, the system software sends these messages to the console (and, optionally, to a logging server on another system). Not all system messages indicate problems with your system. Some messages are purely informational, whereas others can help diagnose problems with communications lines, internal hardware, or the system software. This guide also includes error messages that appear when the system fails. Note: The Catalyst 2950 switch messages listed in this guide also apply to the Cisco Systems Intelligent Gigabit Ethernet Switch Module. This chapter contains these sections: How to Read System Messages, on page 7 Error Message Traceback Reports, on page 9 How to Read System Messages Table 1. Facility Codes. System messages begin with a percent sign (%) and are structured as follows: %FACILITY-SEVERITY-MNEMONIC: Message-text FACILITY is a code consisting of two or more uppercase letters that show the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software. Table 1 lists the system facility codes. Facility Code Description Location CIGESM Cisco Systems Intelligent Gigabit Ethernet Switch Module CIGESM Messages section on page 12 (CIGESM) CMP Cluster Membership Protocol CMP Messages section on page 15 DOT1X 802.1X DOT1X Messages section on page 16 DTP Dynamic Trunking Protocol DTP Messages section on page 17 EC EtherChannel EC Messages section on page 18 ETHCNTR Ethernet controller ETHCNTR Messages section on page 21 HWMATM_MOD PLATFORM_CAT2950 Hardware MAC address table manager Application-specific Integrated Circuit (ASIC) for the switch HWMATM_MOD Messages section on page 22 PLATFORM_CAT2950 Messages section on page 22 PLATFORM_CATALYST2950 Low-level platform messages PLATFORM_CAT2950 Messages section on page 22 PM Port manager PM Messages section on page 26 PORT_SECURITY Port security PORT SECURITY Messages section on page 31 SPAN Switch Port Analyzer (SPAN) SPAN Messages section on page 31 Copyright IBM Corp

10 Table 1. Facility Codes (Continued). Facility Code Description Location SPANTREE Spanning tree SPANTREE Messages section on page 32 SPANTREE_FAST Spanning-tree fast convergence SPANTREE_FAST Messages section on page 38 SPANTREE_VLAN_SWITCH Spanning-tree VLAN switch SPANTREE_VLAN_SWITCH Messages section on page 38 STORM_CONTROL Storm control STORM_CONTROL Messages section on page 38 SW_VLAN VLAN manager SW_VLAN Messages section on page 39 UDLD UniDirectional Link Detection (UDLD) UDLD Messages section on page 43 UFAST_MCAST_SW UplinkFast multicast software UFAST_MCAST_SW Messages section on page 44 SEVERITY is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. Table 2 lists the message severity levels. MNEMONIC is a code that uniquely identifies the message. Table 2. Message Severity Levels. Severity Level Description 0 emergency System is unusable. 1 alert Immediate action required. 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. Message-text is a text string describing the condition. This portion of the message sometimes contains detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets ([ ]). A decimal number, for example, is represented as [dec]. Table 3 lists the variable fields in messages. Table 3. Representation of Variable Fields in Messages. Representation [dec] [char] [chars] [enet] [hex] [inet] Type of Information Decimal integer Single character Character string Ethernet address (for example, 0000.FEED.00C0) Hexadecimal integer Internet address 8 Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter System Message Guide

11 This is a sample system message: %EC-5-UNBUNDLE:Interface Gi0/2 left the port-channel Po2 The messages in Chapter 2 Message and Recovery Procedures, are described in alphabetical order by facility code with the most severe (lowest number) errors described first. Error Message Traceback Reports Some messages describe internal errors and contain traceback information. This information is very important and should be included when you report a problem to your technical support representative. This message example includes traceback information: -Process= "Exec", level= 0, pid= 17 -Traceback= 1A82 1AB A Some messages ask you to copy the messages and take further action. These online tools can provide more information about messages: 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: Bug Toolkit The Bug Toolkit provides information on open and closed caveats, and allows you to search for all known bugs in a specific Cisco IOS Release. You can access the Bug Toolkit at this URL: If you still cannot determine the nature of the error, provide the information you have gathered to your technical support representative. Chapter 1. System Message Overview 9

12 10 Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter System Message Guide

13 Chapter 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. Notes: 1. The messages listed in this chapter do not include the date/time stamp designation that displays only if the software is configured for system log messaging. 2. The Catalyst 2950 switch messages listed in this chapter also apply to the Cisco Systems Intelligent Gigabit Ethernet Switch Module. This chapter contains these message categories: CIGESM Messages, on page 12 CMP Messages, on page 15 DOT1X Messages, on page 16 DTP Messages, on page 17 EC Messages, on page 18 ETHCNTR Messages, on page 21 HWMATM_MOD Messages, on page 22 PLATFORM_CAT2950 Messages, on page 22 PLATFORM_CATALYST2950 Messages, on page 26 PM Messages, on page 26 PORT SECURITY Messages, on page 31 SPAN Messages, on page 31 SPANTREE Messages, on page 32 SPANTREE_FAST Messages, on page 38 SPANTREE_VLAN_SWITCH Messages, on page 38 STORM_CONTROL Messages, on page 38 SW_VLAN Messages, on page 39 UDLD Messages, on page 43 UFAST_MCAST_SW Messages, on page 44 Copyright IBM Corp

14 CIGESM Messages This section contains the Cisco Systems Intelligent Gigabit Ethernet Switch Module (CIGESM) messages. PLATFORM_CIGESM-2-OVER_THERMAL_THRESH2: The Switch Module has exceeded its second thermal threshold. Explanation This message means that the switch temperature has exceeded the second thermal threshold 185 F (85 C), and that the switch is operating in an environment that can cause damage to the hardware. The BladeCenter chassis will shut down the switch shortly after this condition is detected. Verify that environmental conditions of the BladeCenter chassis are adequate. Do not restart the switch until the overtemperature condition has been resolved. PLATFORM_CIGESM-3-IMAGEUPGRADEFAIL: PIC microcontroller image upgrade failed. Explanation This message means that the PIC microcontroller image upgrade failed, because the new PIC microcontroller image failed the sanity check or failed the readback verification. Perform the PIC microcontroller image upgrade again. PLATFORM_CIGESM-4-OVER_THERMAL_THRESH1: The Switch Module has exceeded its first thermal threshold. Explanation This message means that the switch temperature has exceeded the first thermal threshold, and the switch is still operating normally. The first thermal threshold is 167 F (75 C). Temperature inside the BladeCenter chassis should be monitored. IPLATFORM_CIGESM-4-SWITCHRESETPIC: Keepalive ECHO failed, PIC microcontroller has been reset. Explanation This message means that the PIC microcontroller has not responded to three consecutive keepalive messages. The switch re-set the PIC microcontroller to reestablish communication. PLATFORM_CIGESM-4-UNDR_THERMAL_THRESH2: The Switch Module has recovered from second thermal threshold. Explanation This message means that the switch temperature no longer exceeds the second thermal threshold of 185 F (85 C). The switch might still be operating over the first thermal threshold of 167 F (75 C). Temperature inside the chassis should be monitored. 12 Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter System Message Guide

15 PLATFORM_CIGESM-5-DISABLE_EXTERN: Request from Management Module: disable all external ethernet ports gi0/ Explanation This message means that the switch received a request from the management module to shut down ports 17 to 20. PLATFORM_CIGESM-5-DISABLE_EXTERNMGMT: Request from Management Module: Switch can be managed from mgmt module ports only gi0/ Explanation This message means that the switch can only be managed through ports 15 and 16 through the management module. HTTP, SNMP, and Telnet data paths must go through the management module. PLATFORM_CIGESM-5-ENABLE_EXTERN: Request from Management Module: enable external ethernet ports gi0/ Explanation This message means that the switch performed a no shutdown interface configuration command on ports 17 to 20, because of a request from the management module to enable these ports. PLATFORM_CIGESM-5-ENABLE_EXTERNMGMT: Request from Management Module: Switch can be managed from all ports. Explanation This message means that the switch can be managed through ports as well as through the management module ports 15 and 16. PLATFORM_CIGESM-5-MM_NEITHER: The Switch Module cannot detect either Managment Module as active. Explanation This message means that the switch cannot determine which management module is the active primary. This does not affect the operation of the switch. PLATFORM_CIGESM-5-MM_SWITCHOVER: The active Managment Module is now in slot [dec]. Explanation This message means that the switch recognizes that the management module in the specified slot is the active primary. [dec] is the chassis slot number. Chapter 2. Message and Recovery Procedures 13

16 PLATFORM_CIGESM-5-UNDR_THERMAL_THRESH1: The Switch Module has recovered from first thermal threshold. Explanation This message means that the switch temperature no longer exceeds the first thermal threshold of 167 F (75 C). Temperature inside the chassis should be monitored. PLATFORM_CIGESM-6-ACQUIRE_IP: Request from Management Module: acquire IP Address from EEPROM. Explanation This message means that the switch should use the IP address, netmask, and default IP gateway from EEPROM memory. This information can be configured through the CLI or through the BladeCenter Management Module WEB page. PLATFORM_CIGESM-6-PICREADFAIL: Read request to PIC microcontroller failed. Explanation This message means that the PIC microcontroller failed to respond to a Read request. The PIC microcontroller might be too busy to respond and thus the Read request timed out, or a checksum error in the communication exists. PLATFORM_CIGESM-6-PICWRITEFAIL: Write request to PIC microcontroller failed. Explanation This message means that the PIC microcontroller failed to respond to a Write request. The PIC microcontroller might be too busy to respond and thus the Write request timed out, or a checksum error in the communication exists. PLATFORM_CIGESM-6-RESETMGMT1: Request from Management Module received: reset ethernet port Gi0/15. Explanation This message means that the switch had reset port 15, because of a request from the management module to reset the port. PLATFORM_CIGESM-6-RESETMGMT2: Request from Management Module received: reset ethernet port Gi0/16. Explanation This message means that the switch had reset port 16, because of a request from the management module to reset the port. 14 Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter System Message Guide

17 CMP Messages This section contains the Cluster Membership Protocol (CMP) messages. CMP-5-ADD: The Device is added to the cluster (Cluster Name:[chars], CMDR IP Address [inet]). Explanation This message means that the device is added to the cluster. [chars] is the cluster name, and [inet] is the Internet address of the command switch. CMP-5-MEMBER_CONFIG_UPDATE: Received member configuration from member [dec]. Explanation This message means that the active or standby command switch received a member configuration. [dec] is the member number of the sender. CMP-5-MGMT_VLAN_CHNG: The management vlan has been changed to [dec]. Explanation This message means that the management VLAN has changed. [dec] is the new management VLAN number. CMP-5-NBR_UPD_SIZE_TOO_BIG: Number of neighbors in neighbor update is [int], maximum number of neighbors allowed in neighbor update is [int]. Explanation This message means that the number of cluster neighbors in the clustering neighbor update packet exceeds the number of neighbors supported by the clustering module design. [int] is the number of cluster neighbors. CMP-5-REMOVE: The Device is removed from the cluster (Cluster Name:[chars]). Explanation name. This message means that the device is removed from the cluster. [chars] is the cluster Chapter 2. Message and Recovery Procedures 15

18 DOT1X Messages This section contains the 802.1X authorization messages. DOT1X_MOD-3-NULLPTR: Unexpected null pointer in [chars] at [dec]. Explanation This message means that an internal software error occurred. [chars] is the software filename, and [dec] is the line number in the file. Find out more about the error by using the show tech-support privileged EXEC command and DOT1X-3-ROUTEDPORT: Received vlan id ([dec]) from RADIUS for routed port [chars]. Explanation This message means that during 802.1X authorization, the RADIUS server provided a VLAN ID for a routed port. Remove the VLAN ID in the RADIUS configuration, or configure the port as an access port. DOT1X-3-VLANINVALID: Received invalid vlan ([dec]) from RADIUS for [chars]. Explanation This message means that during 802.1X authorization, the RADIUS server provided a VLAN ID that is not configured on the switch. Change the VLAN ID in the RADIUS configuration, or configure the VLAN on the switch. DOT1X-3-VLANMALFORMED: Received malformed vlan from RADIUS for [chars]. Explanation This message means that during 802.1X authorization, the RADIUS server provided an invalid VLAN ID. Correct the VLAN ID in the RADIUS configuration. DOT1X-3-VOICEVLAN: Received voice vlan ([dec]) from RADIUS for [chars]. Explanation This message means that during 802.1X authorization, the RADIUS server provided a VLAN ID that conflicts with the voice VLAN ID on the port. port. Change the VLAN ID in the RADIUS configuration, or change the voice VLAN on the switch 16 Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter System Message Guide

19 DTP Messages This section contains the Dynamic Trunking Protocol (DTP) messages. DTP-4-MEM_UNAVAIL: Memory was not available to perform the trunk negotiation action. Explanation memory. This message means that the system is unable to negotiate trunks because of a lack of Reduce other system activity to ease the memory demands. DTP-4-TMRERR: An internal timer error occurred when trunking on interface [chars]. Explanation This message means that a timer used by the trunking protocol unexpectedly expired. [chars] is the trunked interface. This error is internally corrected, and no long-term ramifications exist. However, if more problems with trunking occur, reload the switch by using the reload privileged EXEC command. DTP-4-UNKN_ERR: An unknown operational error occurred. Explanation This message means that the system is unable to negotiate trunks because an internal operation generated an unexpected error. Reload the switch by using the reload privileged EXEC command. DTP-5-ILGLCFG: Illegal config (on, isl--on, dot1q) on [chars]. Explanation This message means that one end of the trunk is configured as on, ISL, and the other end is configured as on, 802.1Q. [chars] is the interface. This configuration is illegal and will not establish a trunk between two switches. You must change the encapsulation type so that both ends of the trunk match. DTP-5-NONTRUNKPORTON: Port [chars] has become non-trunk. Explanation This message means that the interface changed from trunk to access. [chars] is the interface that changed. This message is provided for information only. DTP-5-TRUNKPORTCHG: Port [chars] has changed from [chars] trunk to [chars] trunk. Explanation This message means that the encapsulation type of the trunk has changed. The first [chars] is the interface, the second [chars] is the original encapsulation type, and the third [chars] is the new encapsulation type. This message is provided for information only. Chapter 2. Message and Recovery Procedures 17

20 DTP-5-TRUNKPORTON: Port [chars] has become [chars] trunk. Explanation This message means that the interface changed from an access to a trunk. The first [chars] is the interface, and the second [chars] is the encapsulation. This message is provided for information only. EC Messages This section contains the EtherChannel, Link Aggregation Control Protocol (LACP), and Port Aggregation Protocol (PAgP) messages. EC-4-NOMEM: Not enough memory available for [chars]. Explanation This message means that either the LACP or the PAgP EtherChannel could not obtain the memory it needed to initialize the required data structures. [chars] is the name of the data structure. Find out more about the error by using the show tech-support privileged EXEC command and EC-5-BUNDLE: Interface [chars] joined port-channel [chars]. Explanation This message means that the listed interface joined the specified EtherChannel. The first [chars] is the physical interface, and the second [chars] is the EtherChannel interface. EC-5-CANNOT_ALLOCATE_AGGREGATOR: Aggregator limit reached, cannot allocate aggregator for group [dec]. Explanation This message means that the aggregator cannot be allocated in the group. aggregator. Change the port attributes of the ports in the group so that they match and join the same EC-5-CANNOT_BUNDLE_LACP: [chars] is not compatible with aggregators in channel [dec] and cannot attach to them ([chars]). Explanation This message means that the port has port attributes that are different from the port channel or ports within the port channel. Change the port attributes so that they match the other ports in the EtherChannel. 18 Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter System Message Guide

21 EC-5-CANNOT_BUNDLE_QOS: Removed [chars] from port channel because a QoS policy cannot be supported across multiple DFC cards. Explanation This message means the specified port cannot join the port channel because the QoS policy attached to the port channel cannot support the multiple Distributed Forwarding Cards (DFCs). [chars] identifies the port that cannot join the port channel. Place the port in another port channel or remove the QoS policy from the port channel. EC-5-CANNOT_BUNDLE1: Port-channel [chars] is admin-down, port [chars] will remain stand-alone. Explanation This message means that the EtherChannel is administratively shut down. The first [chars] is the EtherChannel interface, and the second [chars] is the physical interface. Enable the EtherChannel by using the no shutdown interface configuration command. EC-5-CANNOT_BUNDLE2: [chars] is not compatible with [chars] and will be suspended ([chars]). Explanation This message means that the interface has different interface attributes than other ports in the EtherChannel. For the interface to join the bundle (EtherChannel), change the interface attributes to match the EtherChannel attributes. The first [chars] is the interface to be bundled, the second [chars] is the physical interface that is already in the bundle, and the third [chars] is the reason for the incompatibility. Change the interface attributes to match the EtherChannel attributes. EC-5-ERRPROT: Channel protocol mismatch for interface [chars] in group [dec]: the interface cannot be added to the channel group. Explanation This message means that the interface cannot be added to the channel group by using the specified mode. Change the channel group or the mode for the interface. EC-5-ERRPROT2: Command rejected: the interface [chars] is already part of a channel with a different type of protocol enabled. Explanation This message means that the interface cannot be selected for the specified protocol because it is already part of an EtherChannel group with a different protocol enabled. Remove the interface from the EtherChannel group. EC-5-ERRPROT3: Command rejected: the interface [chars] is already part of a channel. Explanation This message means that the interface cannot be unselected for the specified protocol because it is already part of an EtherChannel group. Remove the interface from the EtherChannel group. Chapter 2. Message and Recovery Procedures 19

22 EC-5-L3DONTBNDL1: [chars] suspended: PAgP not enabled on the remote port. Explanation This message means that Port Aggregation Protocol (PAgP) is enabled on a Layer 3 interface, but the remote port does not have PAgP enabled. In this mode, the port is put in a suspended state. Enable PAgP on the remote port. EC-5-L3DONTBNDL2: [chars] suspended: incompatible partner port with [chars]. Explanation This message means that the group capabilities of the remote port are different than one or more of the other ports in the bundle. For a port to join a bundle, the local port and the remote port must have the same group capabilities as the other ports in the bundle. Configure the remote port with the same group capabilities as the other ports in the bundle. EC-5-L3DONTBNDL3: [chars] suspended: LACP not enabled on the remote port. Explanation This message means that Link Aggregation Control Protocol (LACP) is enabled on a Layer 3 interface, but the remote port does not have LACP enabled. In this mode, the local port is put in a suspended state. Enable LACP on the remote port. EC-5-L3PORTDOWN: Shutting down [chars] as its port-channel is admin-down Explanation This message means that a Layer 3 port is being forced to shut down because its aggregation port is in a down state. [chars] is the interface name. Bring up the aggregation port by using the no shutdown interface configuration command. EC-5-L3STAYDOWN: [chars] will remain down as its port-channel [chars] is admin-down Explanation This message means that a Layer 3 port is being forced to shut down because its aggregation port is in a down state. [chars] is the interface name. Bring up the aggregation port by using the no shutdown interface configuration command. EC-5-NOLACP: Invalid EC mode. LACP not enabled. Explanation This message means that LACP is not included in the image on your switch. An EtherChannel cannot be set into any LACP mode. Upgrade your switch with an image that supports LACP. 20 Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter System Message Guide

23 EC-5-NOPAGP: Invalid EC mode. PAgP not enabled. Explanation This message means that PAgP is not included in the IOS image and that the EtherChannel mode cannot be set to desirable or auto. 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. EC-5-STAYDOWN: no-shut not allowed on [chars]. Module [dec] not online. Explanation This message means that an interface with an EtherChannel configuration cannot be enabled by using the no shutdown interface configuration command. It is a member of an EtherChannel group, and that EtherChannel group has been administratively shut down. The interface has an EtherChannel configuration, but no information is available yet about its port channel. Wait until the module is online to determine the port-channel setting of the EtherChannel. EC-5-UNBUNDLE: Interface [chars] left the port-channel [chars]. Explanation This message means that the listed interface left the specified EtherChannel. The first [chars] is the physical interface, and the second [chars] is the EtherChannel. EC-5-UNSUITABLE: [chars] will not join any port-channel, [chars]. Explanation This message means that one of the interfaces cannot join the EtherChannel because it is configured for PortFast, as a VLAN Membership Policy Server (VMPS), for 802.1X, as a voice VLAN, or as a Switched Port Analyzer (SPAN) destination port. All of these are unsuitable configurations for EtherChannels. The first [chars] is the interface name, and the second [chars] describes the details of the unsuitable configuration. Reconfigure the port; remove the unsuitable configuration. ETHCNTR Messages This section contains the Ethernet controller messages. These messages are a result of a failure of the switch software when trying to program the hardware. Most of these errors lead to incorrect switch behavior, and you should call your technical support representative. ETHCNTR-3-HALF_DUX_COLISION_EXCEED_THRESHOLD: Collision at [chars] exceed threshold. Consider as loop-back. Explanation This message means that the collision at a half-duplex port exceeded the threshold and that the port is considered to be in the loop-back state. [chars] is the port. Chapter 2. Message and Recovery Procedures 21

24 ETHCNTR-3-LOOP_BACK_DETECTED:, Loop-back detected on [chars]. The port is forced to linkdown. Explanation This message means that the loop-back condition might be caused by a balun cable being accidentally connected to the port. [chars] is the port. Check the cables. If a balun cable is connected and the loopback condition is desired, no action is required. Otherwise, connect the correct cable, and bring the port up by entering the no shutdown interface configuration command. HWMATM_MOD Messages This section contains the hardware MAC address table manager (HW MATM) message. HWMATM_MOD-3-NULLPTR: Unexpected null pointer in [chars] at [dec]. Explanation This message means that an internal software error occurred. [chars] is the software filename, and [dec] is the line number in the file. Find out more about the error by using the show tech-support privileged EXEC command and PLATFORM_CAT2950 Messages This section contains the application-specific integrated circuit (ASIC) driverrelated messages. PLATFORM_CAT ASIC_BIST_FAILURE: C2950 BIST failed for memory [chars] count [dec]. Explanation This message means that, during power-on self-test (POST), the built-in memory test on the ASIC failed, which might occur because the ASIC has a defect. [chars] is the name of the ASIC memory table, and [dec] is the number of address failures in the built-in memory test. Find out more about the error by using the show tech-support privileged EXEC command and PLATFORM_CAT ASIC_INIT_FAILURE: ASIC driver initialization has failed. Explanation This message means that one of the steps in the ASIC initialization sequence failed. This might occur because of a failure in the peripheral component interconnect (PCI) configuration setup, the Inter-IC (I2C) initialization, the built-in self-test on the ASIC, or another initialization sequence. This failure might also occur because of an ASIC defect. Find out more about the error by using the show tech-support privileged EXEC command and 22 Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter System Message Guide

25 PLATFORM_CAT MEM_COPY_FAILURE: Invalid copy [dec] for table [chars]. Explanation This message means that there was an attempt to read or write an invalid copy of the switch internal memory. [dec] is the invalid copy number for the table, and [chars] is the name of the ASIC memory table. If the message recurs, find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these PLATFORM_CAT MEM_INDEX_FAILURE: Invalid index [dec] for table [chars]. Explanation This message means that there was an attempt to access an invalid index of the switch internal memory. [dec] is the index number, and [chars] is the name of the ASIC memory table. If the message recurs, find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these PLATFORM_CAT MEM_INIT_FAILURE: The switch memory resources could not be allocated for [chars], initialization failed. Explanation This message means that, during the switch driver initialization, driver-related memory resources could not be allocated, which might occur because of an ASIC defect. [chars] can be asic instance, switch ports, fast-ethernet queues, or gigabit queues. Find out more about the error by using the show tech-support privileged EXEC command and PLATFORM_CAT MEM_READ_FAILURE: Read memory failed for memory [chars] at index [dec]. Explanation This message means that an attempt to read a valid location in the internal chip memory failed, which might occur because of an ASIC defect. [chars] is the name of the ASIC memory table, and [dec] is the table index. If the message recurs, find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these Chapter 2. Message and Recovery Procedures 23

26 PLATFORM_CAT MEM_WRITE_FAILURE: Write memory failed for memory [chars] at index [dec]. Explanation This message means that an attempt to write to a location in the internal chip memory failed, which might occur because of an invalid memory location or an ASIC defect. [chars] is the name of the ASIC memory table, and [dec] is the table index. If the message recurs, find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these PLATFORM_CAT MIIM_OP_FAILURE: Unable to read PHY register at addr [hex] for phy id [hex]. Explanation This message means that there was a failure to read from or write to a PHY register on the switch, which might occur because of a defect in the media independent interface (MII)/Gigabit media independent interface (GMII) switch interface. The first [hex] is the register address, and the second [hex] is the PHY ID. If the message recurs, find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these PLATFORM_CAT PCI_FIND_FAILURE: The number of asics expected were [dec], PCI bus scan found [dec]. Explanation This message means that, during the switch driver initialization, the switch found an incorrect number of ASICs on the PCI bus or did not find any ASICs with a correct PCI value. This might occur because of a system PCI bus defect or an incompatible software version running on the switch. The first [dec] is the number of ASICs that the switch should find, and the second [dec] is the actual number of ASICs that the switch found. Find out more about the error by using the show tech-support privileged EXEC command and PLATFORM_CAT PCI_INIT_FAILURE: The PCI address space initialization failed. Explanation This message means that, during the switch driver initialization, the PCI address space for the ASIC could not be initialized, which might occur because of a system PCI-bus problem. Find out more about the error by using the show tech-support privileged EXEC command and 24 Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter System Message Guide

27 PLATFORM_CAT REG_READ_FAILURE: Register read failed for [chars] in [chars] Explanation This message means that the register read failed for register [chars] in [chars]. An attempt to read a valid location in the internal chip register failed. This could be due to a hardware defect. Find out more about the error by using the show tech-support privileged EXEC command and PLATFORM_CAT REG_WRITE_FAILURE: Register write failed for register [chars] in [chars] Explanation This message means that an attempt to write to a location in the internal chip register failed. This might be caused by writing to an invalid register location or by a defect in the hardware. Find out more about the error by using the show tech-support privileged EXEC command and PLATFORM_CAT PCI_TEST_FAILURE: PCI address space test failed, Wrote [hex], read [hex], re-read [hex]. Explanation This message means that, during POST, the PCI address space for the ASIC was not mapped correctly. This might occur because of a system PCI-bus problem. The first [hex], the second [hex], and the third [hex] are test data. Find out more about the error by using the show tech-support privileged EXEC command and PLATFORM_CAT SCHAN_OP_FAILURE: S-channel operation timeout for opcode [chars]. Explanation This message means that there was a failure to read or write to an ASIC register or a memory location because of an ASIC internal bus failure. [chars] is the operation code. If the message recurs, find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these PLATFORM_CAT SCHAN_READ_REG_FAILURE: S-channel operation read register failure at addr [hex]. Explanation This message means that there was a failure to read the ASIC registers, which might occur because of an invalid register address or internal bus failure. [hex] is the register address. If the message recurs, find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these Chapter 2. Message and Recovery Procedures 25

28 PLATFORM_CAT SYSTEM_INFO_FAILURE: The board information could not be read correctly, initialization failed. Explanation This message means that, during switch driver initialization, there was a failure to read the system board information, which might occur because of an ASIC problem. Find out more about the error by using the show tech-support privileged EXEC command and PLATFORM_CATALYST2950 Messages This section contains the Catalyst 2950 low-level platform message. PLATFORM_CATALYST CRASHED: [chars] Explanation This message means that the system is attempting to display the failure message from the previous failure. [chars] is the failure message. Find out more about the error by using the show tech-support privileged EXEC command and 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. PM-2-NOMEM: Not enough memory available for [chars]. Explanation This message means that the port manager subsystem could not obtain the memory it needed to initialize the specified operation. [chars] is the port manager operation. Find out more about the error by using the show tech-support privileged EXEC command and PM-2-VLAN_ADD: Failed to add VLAN [dec] - [chars]. Explanation This message means that the software failed to add the VLAN to the VLAN Trunking Protocol (VTP) database. [dec] is the VLAN ID, and [chars] specifies the reason for the failure. Find out more about the error by using the show tech-support privileged EXEC command and 26 Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter System Message Guide

29 PM-3-INTERNALERROR: Port Manager Internal Software Error [chars]: [chars]: [dec]: [chars] Explanation This message means an internal software error occurred in the IOS Port Manager. The arguments provide details about the failure that technical support can analyze. Find out more about the error by using the show tech-support privileged EXEC command and PM-4-BAD_APP_ID: An invalid application id [dec] was detected. Explanation This message means that the port manager detected an invalid request. [dec] is the application ID. Find out more about the error by using the show tech-support privileged EXEC command and PM-4-BAD_APP_REQ: An invalid [chars] request by the '[chars]' application was detected. Explanation This message means that the port manager detected an invalid request. The first [chars] is the invalid request, and the second [chars] is the application making the request. Find out more about the error by using the show tech-support privileged EXEC command and PM-4-BAD_CARD_COOKIE: An invalid card cookie was detected. Explanation This message means that the port manager detected an invalid request. Find out more about the error by using the show tech-support privileged EXEC command and PM-4-BAD_CARD_SLOT: An invalid card slot ([dec]) was detected. Explanation number. This message means that the port manager detected an invalid request. [dec] is the slot Find out more about the error by using the show tech-support privileged EXEC command and Chapter 2. Message and Recovery Procedures 27

30 PM-4-BAD_COOKIE: [chars] was detected. Explanation This message means that the port manager detected an invalid request. [chars] is the invalid request. Find out more about the error by using the show tech-support privileged EXEC command and PM-4-BAD_HA_ENTRY_EVENT: Invalid Host access entry event ([dec]) is received. Explanation This message means that an invalid host access entry event was received; the host access table entry event should be an add, delete, or update event. [dec] is the event that is received. Find out more about the error by using the show tech-support privileged EXEC command and PM-4-BAD_PORT_COOKIE: An invalid port cookie was detected. Explanation This message means that the port manager detected an invalid request. Find out more about the error by using the show tech-support privileged EXEC command and PM-4-BAD_PORT_NUMBER: An invalid port number ([dec]) was detected. Explanation number. This message means that the port manager detected an invalid request. [dec] is the port Find out more about the error by using the show tech-support privileged EXEC command and PM-4-BAD_VLAN_COOKIE: An invalid vlan cookie was detected. Explanation This message means that the port manager detected an invalid request. Find out more about the error by using the show tech-support privileged EXEC command and 28 Cisco Systems Intelligent Gigabit Ethernet Switch Module for the IBM Eserver BladeCenter System Message Guide

31 PM-4-BAD_VLAN_ID: An invalid vlan id ([dec]) was detected. Explanation ID. This message means that the port manager detected an invalid request. [dec] is the VLAN Find out more about the error by using the show tech-support privileged EXEC command and PM-4-ERR_DISABLE: [chars] error detected on [chars], putting [chars] in err-disable state. Explanation This message means that the port manager detected a misconfiguration or misbehavior and placed the interface in an error-disabled state. A recovery is attempted after the configured retry time (the default is 5 minutes). The first [chars] is the error, and the second and third [chars] are the affected interfaces. Find out more about the error by using the show tech-support privileged EXEC command and PM-4-ERR_RECOVER: Attempting to recover from [chars] err-disable state on [chars]. Explanation This message means that the port manager is attempting to bring the interface up after taking it down to the error-disabled state. The first [chars] is the error, and the second [chars] is the affected interface. Find out more about the error by using the show tech-support privileged EXEC command and PM-4-EXT_VLAN_INUSE: VLAN [dec] currently in use by [chars]. Explanation This message means that the port manager failed to allocate the VLAN for external use because the VLAN is being used by another feature. [dec] is the VLAN that is being used, and [chars] is the feature that is using it. Reconfigure the feature (for example, the routed port) to use another internal VLAN or to request another available VLAN. PM-4-EXT_VLAN_NOTAVAIL: VLAN [dec] not available in Port Manager. Explanation This message means that the port manager failed to allocate the requested VLAN. The VLAN is probably being used as an internal VLAN by other features. [dec] is the requested VLAN. Try to configure a different VLAN on the device. Chapter 2. Message and Recovery Procedures 29