Cisco 3110, 3112 Message Manual

Cisco Catalyst Switch Module 3110 and

3012 for IBM BladeCenter System

Message Guide

Cisco IOS Release 12.2(40)EX2 April 2008

Americas Headquarters

Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000

800 553-NETS (6387)

Fax: 408 527-0883

Text Part Number: OL-12191-01

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.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0804R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity,

logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers,

logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain

IMPLIED, INCLUDING, WITHOUT

Preface

This guide is for the networking professional using the Cisco IOS command-line interface (CLI) to manage the standalone Cisco Catalyst Switch Module 3110 for IBM BladeCenter, Cisco Catalyst Switch Module 3012 for IBM BladeCenter, or the Catalyst Switch Module Before using this guide, you should have experience working with the Cisco IOS commands and the switch software features. Before using this guide, you should have experience working with the concepts and terminology of Ethernet and local area networking.

The Catalyst Switch Module 3110 is also referred to as a stacking-capable switch, and the Catalyst Switch Module 3012 is referred to as a nonstacking-capable switch.

3110 stack, referred to as the switch.

Purpose

You install the switch in the IBM BladeCenter server chassis, referred to as the enclosure. For information about the supported IBM BladeCenter server chassis, see your chassis documentation.

This guide describes only the Catalyst Switch Module 3110 and Catalyst Switch Module 3012-specific system messages that you might encounter. For a complete list of Cisco IOS system error messages, see the Cisco IOS Software System Error Messages, Cisco IOS Release 12.2 available from the Cisco.com home page by selecting Technical Support & Documentation > Documentation > Cisco IOS Software.

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, see the hardware installation guide that shipped with your switch. For software information, see the software configuration guide and the command reference for this release.

For documentation updates, see the release notes for this release.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

vii

Conventions

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

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 and symbol:

Preface

element.

Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in

this manual.

Related Publications

These documents provide complete information about the switch and are available from this Cisco.com site:

http://www.cisco.com/en/US/products/ps8741/tsd_products_support_series_home.html

Note Before installing, configuring, or upgrading the switch, see these documents:

• For initial configuration information, see the “Using Express Setup” chapter in the getting started

guide or the “Configuring the Switch with the CLI-Based Setup Program” appendix in the hardware installation guide.

• For device manager requirements, see the “System Requirements” section in the release notes.

• For Network Assistant requirements, see the Getting Started with Cisco Network Assistant.

• For upgrade information, see the “Downloading Software” section in the release notes.

• Release Notes for the Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter

• Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide

• Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Command Reference

viii

• Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

• Cisco Software Activation Document for IBM

• Device manager online help (available on the switch)

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Preface

• Cisco Catalyst Switch Module 3110G, 3110X, and 3012 for IBM BladeCenter Hardware Installation

Guide

• Cisco Catalyst Switch Module 3110G, 3110X, and 3012 for IBM BladeCenter Getting Started Guide

• Regulatory Compliance and Safety Information for the Cisco Catalyst Switch Module 3110G,

3110X, and 3012 for IBM BladeCenter

• Cisco Small Form-Factor Pluggable Modules Installation Notes

• These compatibility matrix documents are available from this Cisco.com site:

http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list. html

–

Cisco Gigabit Ethernet Transceiver Modules Compatibility Matrix

–

Cisco 100-Megabit Ethernet SFP Modules Compatibility Matrix

–

Cisco Small Form-Factor Pluggable Modules Compatibility Matrix

–

Compatibility Matrix for 1000BASE-T Small Form-Factor Pluggable Modules

• For information about the Network Admission Control (NAC) features, see the Network Admission

Control Software Configuration Guide

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s revised Cisco

technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

New in Cisco Product Documentation, which also lists all new and

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

ix

Preface

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

x

OL-12191-01

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.

For information about Cisco IOS system messages that are not specific to this switch, see the Cisco IOS Software System Messages for Cisco IOS Release 12.2 on www.cisco.com.

This chapter contains these sections:

• How to Read System Messages, page 1-1

• Error Message Traceback Reports, page 1-6

How to Read System Messages

CHA P T ER

1

System log messages can contain up to 80 characters and a percent sign (%), which follows the optional sequence number or time stamp information, if configured. Messages are displayed in this format:

By default, a switch sends the output from system messages to a logging process. In a switch stack, stack members append their hostnames to the output from system messages and redirect the output to the logging process on the stack master.

Each system message begins with a percent sign (%) and is 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-1 lists switch-specific facility codes. These messages are described in Chapter 2, “Message and Recovery Procedures,” in alphabetical order by facility code, with the most severe (lowest

number) errors described first.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

1-1

Chapter 1 System Message Overview

How to Read System Messages

Ta b l e 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

(only the Catalyst Switch Module

3110)

BSPATCH Boot loader patch “BSPATCH Messages” section on page 2-8

CFGMGR Configuration manager (only the

Catalyst Switch Module 3110)

DHCP_SNOOPING DHCP snooping “DHCP_SNOOPING Messages” section on

DOT1X IEEE 802.1x “DOT1X Messages” section on page 2-18

DOT1X_SWITCH IEEE 802.1x for switches “DOT1X_SWITCH Messages” section on

DTP Dynamic Trunking Protocol “DTP Messages” section on page 2-24

DWL Down-when-looped “DWL Messages” section on page 2-26

EC EtherChannel “EC Messages” section on page 2-26

ETHCNTR Ethernet Controller “ETHCNTR Messages” section on page 2-31

EXPRESS_SETUP Express Setup “EXPRESS_SETUP Messages” section on

FRNTEND_CTRLR Front-end controller (only the Catalyst

Switch Module 3110)

GBIC_SECURITY Gigabit Interface Converter (GBIC)

module and small form-factor pluggable (SFP) module security

GBIC_SECURITY_CRYPT GBIC and SFP module security “GBIC_SECURITY_CRYPT Messages” section

GBIC_SECURITY_UNIQUE GBIC and SFP module security “GBIC_SECURITY_UNIQUE Messages” section

HARDWARE Hardware “HARDWARE Messages” section on page 2-38

HLFM Local forwarding manager “HLFM Messages” section on page 2-40

HPSECURE Port security (only the Catalyst Switch

Module 3110)

IGMP_QUERIER Internet Group Management Protocol

(IGMP) querier

IMAGEMGR Image manager (only the Catalyst

Switch Module 3110)

IP_DEVICE_TRACKING IP device tracking “IP_DEVICE_TRACKING Messages” section on

MAC_MOVE Host activity “MAC_MOVE Messages” section on page 2-45

“BADTRANSCEIVER Messages” section on page 2-7

“CFGMGR Messages” section on page 2-9

page 2-15

page 2-21

page 2-32

“FRNTEND_CTRLR Messages” section on page 2-33

“GBIC_SECURITY Messages” section on page 2-34

on page 2-36

on page 2-37

“HPSECURE Messages” section on page 2-41

“IGMP_QUERIER Messages” section on page 2-42

“IMAGEMGR Messages” section on page 2-43

page 2-44

1-2

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 1 System Message Overview

How to Read System Messages

Table 1-1 Facility Codes (continued)

Facility Code Description Location

PHY PHY “PHY Messages” section on page 2-45

PIMSN Protocol Independent Multicast (PIM)

snooping

PLATFORM Low-level platform-specific “PLATFORM Messages” section on page 2-47

PLATFORM_ENV Platform environment “PLATFORM_ENV Messages” section on

PLATFORM_FBM Platform fallback bridging manager “PLATFORM_FBM Messages” section on

PLATFORM_HPLM Platform pseudo label manager “PLATFORM_HPLM Messages” section on

PLATFORM_IPC Platform inter-process communication

protocol (only the Catalyst Switch Module 3110)

PLATFORM_PBR Platform policy-based routing “PLATFORM_PBR Messages” section on

PLATFORM_PM Platform port manager “PLATFORM_PM Messages” section on

PLATFORM_RPC Platform remote procedure call (only

the Catalyst Switch Module 3110)

PLATFORM_SPAN Platform Switched Port Analyzer “PLATFORM_SPAN Messages” section on

PLATFORM_UCAST Platform unicast routing “PLATFORM_UCAST Messages” section on

PLATFORM_VLAN Platform VLAN “PLATFORM_VLAN Messages” section on

PLATFORM_WCCP Platform WCCP “PLATFORM_WCCP Messages” section on

PM Port manager “PM Messages” section on page 2-62

PORT_SECURITY Port security “PORT_SECURITY Messages” section on

QOSMGR QoS manager “QOSMGR Messages” section on page 2-72

RMON Remote Network Monitoring (RMON) “RMON Messages” section on page 2-77

SDM Switch Database Manager (only the

Catalyst Switch Module 3110)

SPAN Switched Port Analyzer “SPAN Messages” section on page 2-78

SPANTREE Spanning Tree “SPANTREE Messages” section on page 2-79

SPANTREE_FAST Spanning-tree fast convergence “SPANTREE_FAST Messages” section on

SPANTREE_VLAN_SW Spanning-tree VLAN switch “SPANTREE_VLAN_SW Messages” section on

“PIMSN Messages” section on page 2-47

page 2-49

page 2-50

“PLATFORM _IPC Messages” section on page 2-51

page 2-53

page 2-55

“PLATFORM_RPC Messages” section on page 2-56

page 2-58

page 2-61

page 2-62

page 2-70

“SDM Messages” section on page 2-78

page 2-88

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

1-3

Chapter 1 System Message Overview

How to Read System Messages

Table 1-1 Facility Codes (continued)

Facility Code Description Location

STACKMGR Stack manager (only the Catalyst

Switch Module 3110)

STORM_CONTROL Storm control “STORM_CONTROL Messages” section on

SUPERVISOR Supervisor ASIC “SUPERVISOR Messages” section on page 2-92

SUPQ Supervisor queue “SUPQ Messages” section on page 2-93

SW_DAI Dynamic ARP inspection “SW_DAI Messages” section on page 2-94

SW_MACAUTH MAC address authentication “SW_MACAUTH Messages” section on

SW_QOS_TB QoS trusted boundary “SWITCH_QOS_TB Messages” section on

SW_VLAN VLAN manager “SW_VLAN Messages” section on page 2-98

TCAMMGR Ternary content addressable memory

manager

UDLD UniDirectional Link Detection “UDLD Messages” section on page 2-107

UFAST_MCAST_SW UplinkFast packet transmission “UFAST_MCAST_SW Messages” section on

VQPCLIENT VLAN Query Protocol client “VQPCLIENT Messages” section on page 2-109

WCCP Web Cache Communication Protocol

(WCCP)

“STACKMGR Messages” section on page 2-89

page 2-92

page 2-97

page 2-98

“TCAMMGR Messages” section on page 2-105

page 2-109

“WCCP Messages” section on page 2-112

• 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.

Ta b l e 1-2 Message Severity Levels

Table 1-2 lists the 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.

• MNEMONIC is a code that uniquely identifies the message.

1-4

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 1 System Message Overview

• 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 1-3 lists the variable fields in messages.

Ta b l e 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.00C0)

[hex] Hexadecimal integer

[inet] Internet address

How to Read System Messages

All syslog messages generated by a Catalyst Switch Module 3110 other than the master switch are displayed ending with (Switch-x) where Switch-x is the number of the stack member generating the message. Syslog messages generated by the master switch are displayed with no hostname string.

This example shows a partial switch system message on a Catalyst Switch Module 3012:

00:00:46: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up 00:00:47: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up 00:00:47: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up 00:00:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down 00:00:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down 2 *Mar 1 18:46:11: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36) 18:47:02: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36) *Mar 1 18:48:50.483 UTC: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36)

This example shows a partial switch system message for a stack master and a stack member switch (hostname Switch-2) in a switch stack:

00:00:46: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up 00:00:47: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up 00:00:47: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/2, changed state to up 00:00:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down 00:00:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to down 2 *Mar 1 18:46:11: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36) 18:47:02: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36) *Mar 1 18:48:50.483 UTC: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36)

00:00:46: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up (Switch-2) 00:00:47: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up (Switch-2) 00:00:47: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/2, changed state to up (Switch-2) 00:00:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down (Switch-2) 00:00:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to down 2 (Switch-2)

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

1-5

Error Message Traceback Reports

Some messages describe internal errors and contain traceback information. This information is very important and should be included when you report a problem to your technical support representative.

This message example includes traceback information:

-Process= "Exec", level= 0, pid= 17

-Traceback= 1A82 1AB4 6378 A072 1054 1860

Some system messages ask you to copy the error messages and take further action. These online tools also provide more information about system error 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:

https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl

Chapter 1 System Message Overview

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:

http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl

Contacting TAC

If you cannot determine the nature of the error, see the “Obtaining Documentation and Submitting a

Service Request” section on page ix for further information.

1-6

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

CHA P T ER

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.

The messages listed in this chapter do not include the hostname or the date/time stamp designation that displays only if the software is configured for system log messaging.

The chapter includes these message facilities:

• ACLMGR Messages, page 2-3

• BACKUP_INTERFACE Messages, page 2-7

• BADTRANSCEIVER Messages, page 2-7

• BSPATCH Messages, page 2-8

• CFGMGR Messages, page 2-9 (only the Catalyst Switch Module 3110)

• CLS_ACC Messages, page 2-11

• DHCP_SNOOPING Messages, page 2-15

• DOT1X Messages, page 2-18

• DOT1X_SWITCH Messages, page 2-21

• DTP Messages, page 2-24

• DWL Messages, page 2-26

• EC Messages, page 2-26

• ETHCNTR Messages, page 2-31

• EXPRESS_SETUP Messages, page 2-32

• FRNTEND_CTRLR Messages, page 2-33 (only the Catalyst Switch Module 3110)

• GBIC_SECURITY Messages, page 2-34 (only the Catalyst Switch Module 3110X)

• GBIC_SECURITY_CRYPT Messages, page 2-36 (only the Catalyst Switch Module 3110X)

• GBIC_SECURITY_UNIQUE Messages, page 2-37 (only the Catalyst Switch Module 3110X)

• HARDWARE Messages, page 2-38

• HLFM Messages, page 2-40

• HPSECURE Messages, page 2-41 (only the Catalyst Switch Module 3110)

• IGMP_QUERIER Messages, page 2-42

• IMAGEMGR Messages, page 2-43 (only the Catalyst Switch Module 3110)

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-1

Chapter 2 Message and Recovery Procedures

• IP_DEVICE_TRACKING Messages, page 2-44 (only the Catalyst Switch Module 3110)

• 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-49

• PLATFORM_FBM Messages, page 2-49

• PLATFORM_HCEF Message, page 2-50

• PLATFORM_HPLM Messages, page 2-50

• PLATFORM _IPC Messages, page 2-51 (only the Catalyst Switch Module 3110)

• PLATFORM_IPv6_UCAST Message, page 2-53 (only stacking-capable switches)

• PLATFORM_PBR Messages, page 2-53

• PLATFORM_PM Messages, page 2-55

• PLATFORM_RPC Messages, page 2-56 (only the Catalyst Switch Module 3110)

• PLATFORM_SPAN Messages, page 2-58

• PLATFORM_UCAST Messages, page 2-58

• PLATFORM_VLAN Messages, page 2-61

• PLATFORM_WCCP Messages, page 2-62

• PM Messages, page 2-62

• PORT_SECURITY Messages, page 2-70

• Protocol Tunneling Messages, page 2-72

• QOSMGR Messages, page 2-72

• RMON Messages, page 2-77

• SDM Messages, page 2-78 (only the Catalyst Switch Module 3110)

• SPAN Messages, page 2-78

• SPANTREE Messages, page 2-79

• SPANTREE_FAST Messages, page 2-88

• SPANTREE_VLAN_SW Messages, page 2-88

• STACKMGR Messages, page 2-89 (only the Catalyst Switch Module 3110)

• STORM_CONTROL Messages, page 2-92

• SUPERVISOR Messages, page 2-92

• SUPQ Messages, page 2-93

• SW_DAI Messages, page 2-94

2-2

• SW_MACAUTH Messages, page 2-97

• SWITCH_QOS_TB Messages, page 2-98

• SW_VLAN Messages, page 2-98

• TCAMMGR Messages, page 2-105

• UDLD Messages, page 2-107

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

• UFAST_MCAST_SW Messages, page 2-109

• VQPCLIENT Messages, page 2-109

• WCCP Messages, page 2-112

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.

Error Message ACLMGR-2-NOMAP: Cannot create ACL Manager data structures for VLAN Map [chars].

Explanation The ACL manager could not allocate the data structures needed to describe a VLAN

map in a form that can be loaded into hardware. This error is most likely caused by lack of free memory. [chars] is the VLAN map name.

ACLMGR Messages

Recommended Action Reduce other system activity to ease memory demands.

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.

Error Message ACLMGR-2-NOVMR: Cannot create VMR data structures for access list

[chars].

Explanation The ACL manager was unable to allocate the value-mask result (VMR) data structures

needed to describe an ACL in a form that can be loaded into hardware. This error is most likely caused by lack of available memory. [chars] is the access-list name.

Recommended Action Use a less complicated configuration that requires less memory.

Error Message ACLMGR-3-ACLTCAMFULL: Acl Tcam Full. Drop packets on Output Acl label

[dec] on [chars] [chars].

Explanation There are too many ACLs configured for the platform-specific ACL hardware table to

support. [dec] is the label number, and [chars] is the layer. The first [chars] is for Layer 3; the second is for Layer 2. If only the Layer 2 or Later 3 hardware table is full, only one string appears, and the other string is

NULL.

OL-12191-01

Recommended Action Reduce the number of IP or MAC access lists to be applied to interfaces.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-3

ACLMGR Messages

Chapter 2 Message and Recovery Procedures

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.

Recommended Action Reduce other system activity to ease memory demands.

Error Message ACLMGR-3-IECPORTLABELERROR: ACL labels are out-of-sync on interface

[chars], label [dec] is not available on asic [dec].

Explanation An internal software error has occurred. [chars] is the interface name. The first [dec] is

the label associated with the ACL, and the second [dec] is the ASIC number.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

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 (incoming or outgoing) in which the map was applied. The first [dec] is the entry number, and the second [dec] is the label number.

Recommended Action Reduce other system activity to ease memory demands. For example, remove

any ACLs that have been defined but are not now used. Use simpler ACLs with fewer access control entries (ACEs). Use fewer VLANs, and remove any unneeded VLANs from the VLAN database.

Error Message ACLMGR-3-INTTABLE: Not in truth table: VLMAP [dec] RACL [dec] Mcb [dec] Feat [dec].

Explanation An unrecoverable software error occurred while trying to merge the configured input

features. [dec] are internal action codes.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

2-4

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

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.

Recommended Action Reduce the number of IP or MAC access lists (considered separately) in any

one VLAN or policy map to fewer than the number of levels reported by this log message.

Error Message ACLMGR-3-MERGEFAIL: [chars] ACL merge error [dec] ([chars]) on [chars] label [dec].

Explanation The ACL manager was unable to complete the merge of the configured features into a

form suitable for loading into the hardware. Packets potentially affected by this feature will be sent to the CPU for processing instead. The most likely cause is specifying an ACL that is too large or too complex for the system. The first [chars] is the ACL-type error (ip or mac), the first [dec] is the error code, the second [chars] is the message string for the preceding error code, the second [dec] is the label number, and the third [chars] is either input or output.

ACLMGR Messages

Recommended Action Specify a smaller and less complicated configuration.

Error Message ACLMGR-3-NOLABEL: Cannot allocate [chars] label for interface [chars].

Explanation The ACL manager could not allocate a label for the features on this interface. This

means that the hardware cannot be programmed to implement the features, and packets for this interface will be filtered in software. There is a limit of 256 labels per direction. The first [chars] is the direction (input or output); the second [chars] is the interface name.

Recommended Action Use a simpler configuration. Use the same ACLs on multiple interfaces, if

possible.

Error Message ACLMGR-3-OUTTTABLE: Not in truth table: RACL [dec] VLMAP [dec].

Explanation A software error occurred while trying to merge the configured output features. The first

and second [dec] are the internal action codes.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-5

ACLMGR Messages

Chapter 2 Message and Recovery Procedures

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.

Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

Error Message ACLMGR-3-QOSTTABLE: Not in truth table: ACL [dec] in map, action [dec].

Explanation A software error occurred while trying to merge a QoS policy map. The first [dec] is the

ACL number, and the second [dec] is the action corresponding to the specified ACL 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. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

“Error Message Traceback

Error Message ACLMGR-3-RELOADED: Reloading [chars] label [dec] feature.

Explanation The ACL manager is now able to load more of the configured features on this label into

the hardware. One or more features had previously been unloaded because of lack of space. [chars] is the direction (input or output), and [dec] is the label number.

Recommended Action No action is required.

Error Message ACLMGR-3-UNKNOWNACTION: Unknown VMR access group action [hex].

Explanation An internal software error has occurred. [hex] is an internal action code.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

2-6

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

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. [chars] is the direction (input or output), and [dec] is the label number.

Recommended Action Use a simpler configuration. Use the same ACLs on multiple interfaces, if

possible.

BACKUP_INTERFACE Messages

This section contains the Flex Link messages.

Error Message BACKUP_INTERFACE-5-PREEMPT: Preempting interface [chars] in backup pair ([chars], [chars]), preemption mode is [chars]

BACKUP_INTERFACE Messages

Explanation The switch is preempting the current forwarding interface in the backup interface pair.

The first [chars] is the number of the current forwarding interface. The second and third [chars] are the names of the interfaces in the backup pair, and the fourth [chars] is the pre-preemption mode.

Recommended Action No action is required.

Error Message BACKUP_INTERFACE-5-VLB_NON_TRUNK: Warning: Flexlink VLB is not

allowed on non-trunk ports. Please configure [chars] to be a trunk port.

Explanation Flex Link VLB detects a nontrunk port. [chars] is the interface name.

Recommended Action Configure the interface to operate in trunking mode.

BADTRANSCEIVER Messages

This section contains the BADTRANSCEIVER message.

Error Message BADTRANSCEIVER, PHY, LOG_WARNING: An innapropriate transceiver has been inserted in interface [chars].

Note This message applies only to the Catalyst Switch Module 3110.

OL-12191-01

Explanation A defective module is installed in the specified interface. [chars] is the interface.

Recommended Action Remove the transceiver. If it was purchased from Cisco, contact your Cisco

representative to have the transceiver replaced.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-7

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. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

page 1-6.

Error Message BSPATCH-1-PATCHED: Boot Loader patch ([chars]) installed.

Chapter 2 Message and Recovery Procedures

“Error Message Traceback Reports” section on

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. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on

page 1-6.

Error Message BSPATCH-3-FAILED: Failed to install Boot Loader patch ([chars]).

Explanation The switch failed to apply a boot loader patch. [chars] is the SDRAM refresh timer

register setting.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

2-8

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

CFGMGR Messages

This section contains the configuration manager messages on stacking-capable switches.

Error Message CFGMGR-1-UNABLE_TO_SEND_RUN_CFG: unable to send running-cfg, bits: [hex], retrying...

Note This message applies only to the Catalyst Switch Module 3110.

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.

Recommended Action Find out more about the error by using the show tech-support privileged

EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting IBM, see the

Message Traceback Reports” section on page 1-6.

CFGMGR Messages

“Error

Error Message CFGMGR-1-UNABLE_TO_SEND_STARTUP_CFG: unable to send startup-cfg, bits: [hex], retrying...

Note This message applies only to the Catalyst Switch Module 3110.

Explanation The system is unsuccessfully attempting to distribute the startup configuration file to the

stack member switches. [hex] is the bit representation of the switch number.

Recommended Action Find out more about the error by using the show tech-support privileged EXEC

command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

Error Message CFGMGR-3-ERROR_APPLYING_STARTUP_CFG: Error Applying Startup Config to Running Config.

Note This message applies only to the Catalyst Switch Module 3110.

Explanation The system encountered an error when it was automatically applying the startup

configuration to the running configuration.

OL-12191-01

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

“Error Message Traceback Reports” section on page 1-6.

2-9

CFGMGR Messages

Chapter 2 Message and Recovery Procedures

Error Message CFGMGR-4-MEMBER_WRITING_STARTUP_CFG: only master can do that.

Note This message applies only to the Catalyst Switch Module 3110.

Explanation A stack member switch attempted to write to the startup configuration file; only the

stack master can write to the startup configuration file.

Recommended Action No action is required.

Error Message CFGMGR-5-UNABLE_TO_USE_PROVISIONED_CFG: Switch [dec] will receive the

default configuration.

Note This message applies only to the Catalyst Switch Module 3110.

Explanation The switch type of the specified switch does not match the provisioned configuration

for its switch number; therefore, the default configuration is applied to this switch. [dec] is the stack member number.

Recommended Action No action is required.

Error Message CFGMGR-6-APPLYING_RUNNING_CFG: as new master.

Note This message applies only to the Catalyst Switch Module 3110.

Explanation A new stack master is applying the backed-up running configuration.

Recommended Action No action is required.

Error Message CFGMGR-6-SPURIOUS_MEMBER_ADD: CFG MGR Recvd Spurious New Member

Notification: [int].

Note This message applies only to the Catalyst Switch Module 3110.

Explanation The configuration manager received a notification about adding a stack member switch

that already exists in the stack. [int] is the switch number.

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. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on

page 1-6.

2-10

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message CFGMGR-6-UNABLE_TO_NVGEN_BUSY_RUNNING_CFG: config file busy,

retrying...

Note This message applies only to the Catalyst Switch Module 3110.

Explanation The stack master is temporarily unable to generate the stack running configuration

because another process is generating the configuration file.

Recommended Action No action is required. The action will be tried again.

Error Message CFGMGR-6-UNABLE_TO_NVGEN_RUNNING_CFG: config file too large...

Note This message applies only to the Catalyst Switch Module 3110.

Explanation The stack master is unable to generate the stack running configuration because the

configuration file is too large.

CLS_ACC Messages

Recommended Action Remove some configuration commands.

CLS_ACC Messages

This section contains the Express Setup messages that appear when you use the Ethernet management port to connect to the PC. In these messages, Express Setup is referred to as consoleless access.

Error Message CLS_ACC-2-CONFIG_NV_DATA: Express setup parameter committed. Default port role will be applied

Explanation After the Express Setup settings are configured, the switch becomes a configured

switch. The default port roles are automatically applied to all ports. You can now manually modify the port role configurations.

Recommended Action No action is required.

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.

OL-12191-01

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.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-11

CLS_ACC Messages

Chapter 2 Message and Recovery Procedures

Error Message CLS_ACC-2-NO_PROCESS: Process creation failure

Explanation Failed to create process to execute 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 using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the

Message Traceback Reports” section on page 1-6.

Error Message CLS_ACC-2-SETUP_BTN_PRS: [chars]

Explanation Pressing the Mode button for more than 5 seconds causes an unconfigured switch to go

into Express Setup mode. Pressing the Mode button for more than 5 seconds does not affect an already configured switch; the switch does not go into Express Setup mode. [chars] is the mode.

Recommended Action No action is required.

“Error

Error Message CLS_ACC-3-CONFIG_ERROR: [chars]

Explanation The switch is not correctly configured for consoleless access mode and cannot go into

that mode. [chars] is the mode.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

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. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

2-12

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message CLS_ACC-3-NOMEMORY: [chars]

Explanation A request to configure the switch with consoleless access commands failed its memory

allocation. [chars] describes whether processor memory allocation or I/O memory allocation failed.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

Error Message CLS_ACC-3-NOSOCKET: Fail to create DNS socket for consoleless access

Explanation The socket creation process failed. The switch cannot go into consoleless access mode

and stops.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

CLS_ACC Messages

“Error Message Traceback

Error Message CLS_ACC-3-UNABLE_TO_RESET_CONFIG: [chars]

Explanation The switch cannot reset the configuration.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

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. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-13

CLS_ACC Messages

Chapter 2 Message and Recovery Procedures

Error Message CLS_ACC-4-NO_HTTP_PAGE: Failed to locate HTTP page for the consoleless

access mode

Explanation The switch cannot find the HTTP page that appears in Express Setup mode because the

page is not on the flash memory.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

Error Message CLS_ACC-4-UNEXPECTEDEVENT: Switch does not support or not ready for consoleless access mode

Explanation The switch does not support or is not ready to go into the consoleless access mode.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

“Error Message Traceback

Error Message CLS_ACC-5-CLRCFG: User cleared switch configurations under recovery mode

Explanation In recovery mode, the switch resets to the default configuration.

Recommended Action No action is required.

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. [chars] is the name of the interface,

and [dec] is the number of the interface.

Recommended Action No action is required.

2-14

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message CLS_ACC-7-ACC_VLAN: Selected vlan [dec] for consoleless access

Explanation The switch assigned a VLAN to the management interface for consoleless access. [dec]

is the VLAN ID.

Recommended Action No action is required.

Error Message CLS_ACC-7-CONFIG: Save access intf config: if: [chars], port num:

[dec], vlan [dec], admin-down?:[dec]

Explanation The switch has saved the interface configuration. After the switch exits Express Setup

mode and the management interface is configured, the saved configuration takes effect. [chars] is the name of the mode. The first [dec] is the port number, the second [dec] is the VLAN ID, and the third [dec] is the port status.

Recommended Action No action is required.

Error Message CLS_ACC-7-CONFIG_SUCCESS: [chars]

DHCP_SNOOPING Messages

Explanation The management interface has been configured, or its original configuration has been

restored. [chars] is the name of the configuration file.

Recommended Action No action is required.

DHCP_SNOOPING Messages

This section contains the DHCP snooping messages.

Error Message DHCP_SNOOPING-3-DHCP_SNOOPING_INTERNAL_ERROR: DHCP Snooping internal error, [chars].

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. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message DHCP_SNOOPING-4-AGENT_OPERATION_FAILED: DHCP snooping binding transfer failed. [chars].

“Error Message Traceback Reports” section on page 1-6.

OL-12191-01

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.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-15

DHCP_SNOOPING Messages

Error Message DHCP_SNOOPING-4-AGENT_OPERATION_FAILED_N: DHCP snooping binding

transfer failed ([dec]). [chars].

Error Message DHCP_SNOOPING-4-DHCP_SNOOPING_ERRDISABLE_WARNING: DHCP Snooping received [dec] DHCP packets on interface [chars].

Error Message DHCP_SNOOPING-4-DHCP_SNOOPING_PVLAN_WARNING: DHCP Snooping configuration may not take effect on secondary vlan [dec]. [chars]

Chapter 2 Message and Recovery Procedures

Explanation The DHCP snooping binding transfer process failed because of the specified reason for

failure [dec] is the number of failures, and [chars] is the reason for the failure. This message is rate-limited.

Recommended Action No action is required.

Explanation The switch detected a DHCP packet rate-limit violation on the specified interface and

put the interface in the error-disabled state. [dec] is the number of DCHP packets, and [chars] is the interface.

Recommended Action No action is required.

Explanation If the private VLAN feature is configured, the DHCP snooping configuration on the

primary VLAN automatically propagates to all the secondary VLANs. [dec] is the VLAN ID of the secondary VLAN, and [chars] is the warning.

Recommended Action No action is required.

Error Message DHCP_SNOOPING-4-IP_SOURCE_BINDING_NON_EXISTING_VLAN_WARNING: IP

source binding is configured on non existing vlan [dec].

Explanation The message means that an IP source binding was configured on a VLAN that has not

been configured yet. [dec] is the VLAN.

Recommended Action No action is required.

Error Message DHCP_SNOOPING-4-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.

2-16

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message DHCP_SNOOPING-4-NTP_NOT_RUNNING: NTP is not running; reloaded binding

lease expiration times are incorrect.

Explanation If the DHCP snooping database agent loads the DHCP snooping bindings and NTP is

not running, the calculated lease duration for the bindings is incorrect.

Recommended Action Configure NTP on the switch to provide an accurate time and date for the

system clock. Then disable and re-enable DHCP snooping to clear the DHCP snooping binding database.

Error Message DHCP_SNOOPING-4-QUEUE_FULL: Fail to enqueue DHCP packet into processing queue: [chars], the queue is most likely full and the packet will be dropped.

Explanation The CPU is receiving DHCP at a higher rate than the DHCP snooping can process.

These DHCP packets are dropped to prevent a denial of service attack. [chars] is the warning.

Recommended Action No action is required.

DHCP_SNOOPING Messages

Error Message DHCP_SNOOPING-4-STANDBY_AGENT_OPERATION_FAILED: DHCP snooping binding

transfer failed on the Standby Supervisor. [chars].

Explanation The DHCP snooping binding transfer process failed on a standby supervisor engine.

[chars] is the standby supervisor engine.

Recommended Action No action is required.

Error Message DHCP_SNOOPING-6-AGENT_OPERATION_SUCCEEDED: DHCP snooping database

[chars] succeeded.

Explanation The DHCP binding transfer process succeeded. [chars] is the DCHP snooping database.

Recommended Action No action is required.

Error Message DHCP_SNOOPING-6-BINDING_COLLISION: Binding collision. [dec] bindings

ignored.

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.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-17

DOT1X Messages

Chapter 2 Message and Recovery Procedures

Error Message DHCP_SNOOPING-6-INTERFACE_NOT_VALID: Interface not valid. [dec]

bindings ignored.

Explanation The specified number of bindings were ignored when the switch read the database file

because the interface in binding database is not available, the interface is a routed port, or the interface is a DHCP snooping-trusted Layer 2 interface. [dec] is the number of bindings that the switch ignores.

Recommended Action No action is required.

Error Message DHCP_SNOOPING-6-LEASE_EXPIRED: Lease Expired. [dec] bindings ignored.

Explanation The specified number of bindings were ignored when the switch read the database file

because the DHCP lease expired. [dec] is the number of bindings.

Recommended Action No action is required.

Error Message DHCP_SNOOPING-6-PARSE_FAILURE: Parsing failed for [dec] bindings.

Explanation The specified number of bindings were ignored when the switch read the database file

because the database read operation failed. [dec] is the number of bindings.

Recommended Action No action is required.

Error Message DHCP_SNOOPING-6-VLAN_NOT_SUPPORTED: Vlan not supported. [dec] bindings

ignored.

Explanation The specified number of bindings were ignored when the switch read the database file

because the VLAN is no longer configured on the switch. [dec] is the number of bindings that the switch ignores.

Recommended Action No action required.

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.

2-18

Recommended Action Reduce other system activity to reduce memory demands. If the switch does

not have enough memory, upgrade to a larger memory configuration.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message DOT1X-4-PROC_START_ERR: Dot1x unable to start.

Explanation The system failed to start the IEEE 802.1x process.

Recommended Action Restart the IEEE 802.1x process by entering the dot1x system-auth-control

global configuration command. If this message recurs, reload the device.

Error Message DOT1X-4-UNKN_ERR: An unknown operational error occurred.

Explanation The IEEE 802.1x process cannot operate because of an internal system error.

Recommended Action Reload the device.

Error Message DOT1X-5-ERR_CHANNELLING: Dot1x cannot be enabled on Channelling ports.

Explanation IEEE 802.1x authentication could not be enabled on the EtherChannel port. This

occurred because the switch tried to set IEEE 802.1x port control to auto or to force-unauthorized mode on the channel port, which is not allowed.

DOT1X Messages

Recommended Action Disable the EtherChannel on the interface and then try to re-enable

IEEE

802.1x authentication.

Error Message DOT1X-5-ERR_DYNAMIC: Dot1x cannot be enabled on Dynamic ports.

Explanation IEEE 802.1x authentication could not be enabled on the dynamic-mode port. This

occurred because the switch tried to set IEEE 802.1x port-control to auto or force-unauthorized mode on a dynamic mode port, which is not allowed.

Recommended Action Disable dynamic mode on the interface, and then try IEEE 802.1x

authentication.

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.1x

authentication.

OL-12191-01

Error Message DOT1X-5-ERR_PROTO_TUNNELLING: Dot1x can not be enabled on protocol

tunnelling enabled ports.

Explanation IEEE 802.1x authentication could not be enabled on the protocol tunneling enabled

port. This condition was caused by trying to set IEEE 802.1x port-control to auto or force-unauthorized mode on a protocol tunneling enabled port, which is not allowed.

Recommended Action Disable protocol tunnelling on the interface, and retry the IEEE 802.1x

operation.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-19

DOT1X Messages

Chapter 2 Message and Recovery Procedures

Error Message DOT1X-5-ERR_PVLAN_EQ_VVLAN: Dot1x can not be enabled on a port with

Access VLAN equal to Voice VLAN.

Explanation IEEE 802.1x authentication could not be enabled on a port with the same VLAN for the

access VLAN and the voice VLAN. This occurred because the switch tried to set IEEE 802.1x port control to auto or force-unauthorized mode on the port, which is not allowed.

Recommended Action Change the voice VLAN or access VLAN on the interface, and retry the IEEE

802.1x operation.

Error Message DOT1X-5-ERR_RSPAN_VLAN: Dot1x can not be enabled on ports configured in Remote SPAN vlan.

Explanation IEEE 802.1x authorization could not be enabled on the remote SPAN (RSPAN) VLAN

port. This occurred because the switch tried to set IEEE 802.1x port-control to auto or force-unauthorized mode on a port assigned to an RSPAN VLAN, which is not allowed.

Recommended Action Disable RSPAN on the VLAN, and retry the IEEE 802.1x operation.

Error Message DOT1X-5-ERR_SPANDST: Dot1x can not be enabled on [chars]. It is

configured as a SPAN Dest port.

Explanation IEEE 802.1x and SPAN destination ports are mutually exclusive. [chars] is the port.

Recommended Action Disable the SPAN destination port configuration, and then reconfigure IEEE

802.1x authentication on the port.

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.

Error Message DOT1X-5-ERR_VLAN_INVALID: The VLAN [dec] is invalid and cannot be assiged for use on the Dot1x port [chars] Vlan

Explanation The specified VLAN is out of range and cannot be assiged as an IEEE 802.1x port. [dec]

is the VLAN, and [chars] is the IEEE 802.1x port.

Recommended Action Reconfigure the configuration to use a valid VLAN.

2-20

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message DOT1X-5-INVALID_INPUT: Dot1x Interface parameter is Invalid on

interface [chars].

Explanation The IEEE 802.1x interface parameter is out of the specified range or is invalid. [chars]

is the interface.

Recommended Action Refer to the CLI help documentation to determine the valid IEEE 802.1x

parameters.

Error Message DOT1X-5-INVALID_MAC: Invalid MAC address(drop, zero, broadcast or multicast mac address) [enet] is trying to authenticate.

Explanation Authentication using IEEE 802.1x is not allowed for zero, broadcast, and multicast

source MAC addresses. [enet] is the invalid MAC address.

Recommended Action Connect an IEEE 802.1x supported host to the IEEE 802.1x enabled port.

DOT1X_SWITCH Messages

This section contains the IEEE 802.1x messages for switches.

Error Message DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on [chars]

Explanation The client MAC address could not be added to the MAC address table because the

hardware memory is full, or the address is a secure address on another port. [enet] is the supplicant MAC address, and [chars] is the interface. This message might appear if the IEEE 802.1x feature is enabled.

Recommended Action If the hardware memory is full, remove some of the dynamic MAC addresses.

If the client address is on another port, manually remove it from that port.

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.

Error Message DOT1X_SWITCH-5-ERR_INVALID_SEC_VLAN: Attempt to assign invalid

secondary VLAN [dec] to PVLAN host 802.1x port [chars]

OL-12191-01

Explanation An attempt was made to assign a nonsecondary VLAN to a private VLAN host IEEE

802.1x port. [dec] is the VLAN, and [chars] is the port.

Recommended Action Change the mode of the port so that it is no longer a private VLAN host port,

or use a valid secondary VLAN.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-21

DOT1X_SWITCH Messages

Error Message DOT1X_SWITCH-5-ERR_PRIMARY_VLAN_NOT_FOUND: Attempt to assign VLAN

[dec], whose primary VLAN does not exist or is shutdown, to 802.1x port [chars]

Error Message DOT1X_SWITCH-5-ERR_RADIUS_VLAN_NOT_FOUND: Attempt to assign non-existent VLAN [chars] to dot1x port [chars]

Error Message DOT1X_SWITCH-5-ERR_SEC_VLAN_INVALID: Attempt to assign secondary VLAN [dec] to non-PVLAN host 802.1x port [chars]

Chapter 2 Message and Recovery Procedures

Explanation An attempt was made to assign a private VLAN whose primary VLAN does not exist or

is shut down. [dec] is the VLAN, and [chars] is the port.

Recommended Action Make sure the primary VLAN exists and is not shut down. Verify that the

private VLAN is associated with a primary VLAN.

Explanation RADIUS attempted to assign a VLAN with a particular name or id to a supplicant on a

port, but the name or id could not be found on the switch. [dec] is the VLAN, and [chars] is the port.

Recommended Action Make sure a VLAN with the specified name/id exists on the switch.

Explanation An attempt was made to assign a secondary VLAN to a port that is not a private VLAN

host port, which is not allowed. [dec] is the VLAN, and [chars] is the port.

Recommended Action Change the mode of the port so that it is configured as a private VLAN host

port, or use a different VLAN that is not configured as a secondary VLAN.

Error Message DOT1X_SWITCH-5-ERR_SPAN_DST_PORT: Attempt to assign VLAN [dec] to

802.1x port [chars], which is configured as a SPAN destination

Explanation An attempt was made to assign a VLAN to an IEEE 802.1x port that is configured as a

SPAN destination port. [dec] is the VLAN, and [chars] is the port.

Recommended Action Change the SPAN configuration so that the port is no longer a SPAN

destination port, or change the configuration so that no VLAN is assigned.

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. This causes Multi-Domain authentication to start.

2-22

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message DOT1X_SWITCH-5-ERR_VLAN_EQ_VVLAN: Data VLAN [dec] on port [chars]

cannot be equivalent to the Voice VLAN

Explanation An attempt was made to assign a data VLAN to an IEEE 802.1x port that is the same as

the voice VLAN. [dec] is the VLAN, and [chars] is the port.

Recommended Action Change either the voice VLAN or the access/IEEE 802.1x-assigned VLAN on

the interface so that they are not equal. This causes the authentication to proceed normally on the next retry.

Error Message DOT1X_SWITCH-5-ERR_VLAN_INTERNAL: Attempt to assign internal VLAN [dec] to 802.1x port [chars]

Explanation An attempt was made to assign an invalid VLAN to an IEEE 802.1x port. The VLAN

specified is used internally and cannot be assigned to this port. [dec] is the VLAN, and [chars] is the port.

Recommended Action Update the configuration to not use this VLAN.

DOT1X_SWITCH Messages

Error Message DOT1X_SWITCH-5-ERR_VLAN_INVALID: Attempt to assign invalid VLAN [dec]

to 802.1x port [chars]

Explanation An attempt was made to assign an invalid VLAN to an IEEE 802.1x port. The VLAN

specified is out of range and cannot be assigned to this port.[dec] is the VLAN, and [chars] is the port.

Recommended Action Update the configuration to use a valid VLAN.

Error Message DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND: Attempt to assign non-existent or

shutdown VLAN [dec] to 802.1x port [chars]

Explanation An attempt was made to assign a VLAN to an IEEE 802.1x port, but the VLAN was not

found in the VTP database. [dec] is the VLAN, and [chars] is the port.

Recommended Action Make sure that the VLAN exists and is not shut down, or use another VLAN.

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.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-23

DTP Messages

Chapter 2 Message and Recovery Procedures

Error Message DOT1X_SWITCH-5-ERR_VLAN_PROMISC_PORT: Attempt to assign VLAN [dec] to

promiscuous 802.1x port [chars]

Explanation An attempt was made to assign a VLAN to a promiscuous IEEE 802.1x port, which is

not allowed. [dec] is the VLAN, and [chars] is the port.

Recommended Action Change the mode of the port so that it is no longer a promiscuous port, or

change the configuration so that no VLAN is assigned.

Error Message DOT1X_SWITCH-5-ERR_VLAN_RESERVED: Attempt to assign reserved VLAN [dec] to 802.1x port [chars]

Explanation An attempt was made to assign an invalid VLAN to an IEEE 802.1x port. The VLAN

specified is a reserved VLAN and cannot be assigned to this port. [dec] is the VLAN, and [chars] is the port.

Recommended Action Update the configuration to not use this VLAN.

Error Message DOT1X_SWITCH-5-ERR_VLAN_ROUTED_PORT: Attempt to assign VLAN [dec] to

routed 802.1x port [chars]

Explanation An attempt was made to assign a VLAN to a routed IEEE 802.1x port, which is not

allowed. [dec] is the VLAN, and [chars] is the port.

Recommended Action Change the mode of the port so that it is no longer a routed port, or change the

configuration so that no VLAN is assigned.

Error Message DOT1X_SWITCH-5-ERR_VLAN_RSPAN: Attempt to assign RSPAN VLAN [dec] to

802.1x port [chars]. 802.1x is incompatible with RSPAN

Explanation An attempt was made to assign a remote SPAN VLAN to an IEEE 802.1x port. Remote

SPAN should not be enabled on a VLAN in which ports are configured with IEEE 802.1x enabled. [dec] is the VLAN, and [chars] is the port.

Recommended Action Either disable remote SPAN configuration on the VLAN, or disable

IEEE

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.

802.1x on all the ports in this VLAN.

2-24

Explanation The system cannot negotiate trunks because of a lack of memory.

Recommended Action Reduce other system activity to ease memory demands.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message DTP-4-TMRERR: An internal timer error occurred when trunking on

interface [chars].

Explanation A timer used by the trunking protocol unexpectedly expired. [chars] is the trunked

interface.

Recommended Action This problem is corrected internally and has no long-term ramifications.

However, if more problems with trunking occur, reload the switch by using the reload privileged EXEC command.

Error Message DTP-4-UNKN_ERR: An unknown operational error occurred.

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.

DTP Messages

Explanation The two ports in the trunk negotiation belong to different VTP domains. Trunking can

be configured only when the ports belong to the same VTP domain. [chars] is the port number.

Recommended Action Ensure that the ports in the trunk negotiation belong to the same VTP domain.

Error Message DTP-5-ILGLCFG: Illegal config (on, isl--on,dot1q) on [chars].

Explanation One end of the trunk link is configured as on with ISL encapsulation and the other end

is configured as on with IEEE 802.1Q encapsulation. [chars] is the interface.

Recommended Action This configuration is illegal and will not establish a trunk between two

switches. You must change the encapsulation type so that both ends of the trunk match.

Error Message DTP-5-NONTRUNKPORTON: Port [chars] has become non-trunk.

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.

OL-12191-01

Explanation The encapsulation type of the trunk port has changed. The first [chars] is the interface,

the second is the original encapsulation type, and the third [chars] is the new encapsulation type.

Recommended Action This message is provided for information only.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-25

DWL Messages

Error Message DTP-5-TRUNKPORTON: Port [chars] has become [chars] trunk.

Explanation The interface has changed from an access port to a trunk port. The first [chars] is the

interface, and the second [chars] is the encapsulation type.

Recommended Action This message is provided for information only.

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 that might be caused by a Token-Ring Type-1

cable connected to the port or a misconfiguration in the network. [chars] is the port.

Recommended Action Correct the problem that is causing the loopback condition. Then enter the

shutdown and the no shutdown interface configuration commands.

Chapter 2 Message and Recovery Procedures

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].

Error Message EC-5-BUNDLE: Interface [chars] joined port-channel [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.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

Explanation The listed interface joined the specified EtherChannel. The first [chars] is the physical

interface, and the second [chars] is the EtherChannel interface.

“Error Message Traceback

2-26

Recommended Action No action is required.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message EC-5-CANNOT_ALLOCATE_AGGREGATOR: Aggregator limit reached, cannot

allocate aggregator for group [dec]

Explanation A new aggregator cannot be allocated in the group. [dec] is the affected group.

Recommended Action Change the port attributes of the ports in the group so that they match and join

the same aggregator.

Error Message EC-5-CANNOT_BUNDLE1: Port-channel [chars] is down, port [chars] will remain stand-alone

Explanation The aggregation port is down. The port remains standalone until the aggregation port is

up. The first [chars] is the EtherChannel. The second [chars] is the port number.

Recommended Action Ensure that the other ports in the bundle have the same configuration.

Error Message EC-5-CANNOT_BUNDLE2: [chars] is not compatible with [chars] and will

be suspended ([chars])

EC Messages

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. The first [chars] is the interface to be bundled, the second [chars] is the physical interface (a switch port or a routed port) that is already in the bundle, and the third [chars] is the reason for the incompatibility.

Recommended Action Change the interface attributes to match the EtherChannel attributes.

Error Message EC-5-CANNOT_BUNDLE_LACP: [chars] is not compatible with aggregators in

channel [dec] and cannot attach to them ([chars]).

Explanation The port has different port attributes than the port channel or ports within the port

channel. [chars] is the incompatible port. [chars] is the short interface name, such as Gi1/0/1 on a stacking-capable switch, [dec] is the channel group number, and the last [chars] is the reason.

Recommended Action For the port to join the EtherChannel bundle, change the port attributes so that

they match the port.

Error Message EC-5-COMPATIBLE: [chars] is compatible with port-channel members.

Explanation A port was not operational because its attributes were different from those of the port

channel or ports within the port channel. The system has detected that the attributes of the port now match the port-channel attributes. [chars] is the affected port.

OL-12191-01

Recommended Action No action is required.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-27

EC Messages

Chapter 2 Message and Recovery Procedures

Error Message EC-5-DONTBNDL: [chars] suspended: incompatible remote port with

[chars]

Explanation The configuration of the remote port is different from the configuration of other remote

ports in the bundle. A port can only join the bundle when the configuration of the local port and the configuration of the remote port are the same as other ports already in the bundle. The first [chars] is the name of the local interface that is being suspended, and the second [chars] is the name of the local interface that is already bundled.

Recommended Action Make sure that the configuration of the remote ports is the same for all ports in

the bundle.

Error Message EC-5-ERRPROT: Channel protocol mismatch for interface [chars] in group [dec]: the interface 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.

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.

Error Message EC-5-ERRPROT3: Command rejected: the interface [chars] is already part

of a channel.

Explanation The interface cannot be unselected for the specified protocol because it is already part

of a channel group. [chars] is the interface.

Recommended Action Remove the interface from the channel group.

Error Message EC-5-L3DONTBNDL1: [chars] suspended: PAgP not enabled on the remote

port.

Explanation PAgP is enabled on the Layer 3 interface, but the partner port is not enabled for PAgP.

In this mode, the port is placed in a suspended state. [chars] is the Layer 3 interface.

Recommended Action Enable PAgP on the remote side by using the channel-group interface

configuration command.

2-28

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message EC-5-L3DONTBNDL2: [chars] suspended: LACP currently not enabled on the

remote port.

Explanation LACP is enabled on a Layer 3 interface but is not enabled on the partner port. In this

mode, the port is put in a suspended state. [chars] is the interface name.

Recommended Action Enable LACP on the remote side.

Error Message EC-5-L3DONTBNDL3: [chars] suspended: LACP not enabled on the remote

port.

Explanation LACP is enabled on a Layer 3 interface, but the remote port does not have LACP

enabled. In this mode, the local port is put in a suspended state.

Recommended Action Enable LACP on the remote port.

Error Message EC-5-NOLACP: Invalid EC mode, LACP not enabled.

Explanation The EtherChannel mode cannot be set because LACP is not included in the software

image.

EC Messages

Recommended Action Install a software image that includes LACP, and set the EC mode to on.

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.

Explanation The administrative state of the port is controlled by the administrative state of its

aggregate port. If the administrative state of the aggregate port is down, the administrative state of the port is also forced to be down. [chars] is the physical interface.

Recommended Action Enter the no shutdown interface configuration command on the aggregate port

to activate the aggregation port.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-29

EC Messages

Chapter 2 Message and Recovery Procedures

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.

Recommended Action Enter the no shutdown interface configuration command on the aggregation

port to activate (unshut) the aggregation port.

Error Message EC-5-STAYDOWN: no-shut not allowed on [chars]. Module [dec] not online.

Explanation An interface with an EtherChannel configuration cannot be enabled by using the no

shutdown interface configuration command because it is a member of an EtherChannel group and that EtherChannel group has been administratively shut down. The interface has an EtherChannel configuration, but no information is available yet about its port channel. [chars] is the interface, and [dec] is the module.

Recommended Action No action is required. Wait until the module is online to find out the

port-channel setting of the EtherChannel.

Error Message EC-5-UNBUNDLE: Interface [chars] left the port-channel [chars].

Explanation The listed interface left the specified EtherChannel. The first [chars] is the physical

interface, which can be a switch port or a routed port, and the second [chars] is the EtherChannel.

Recommended Action No action is required.

Error Message EC-5-UNSUITABLE: [chars] will not join any port-channel, [chars].

Explanation One of the interfaces cannot join the EtherChannel because it is configured for PortFast,

as a VLAN Membership Policy Server (VMPS), for IEEE 802.1x, as a voice VLAN, or as a Switched Port Analyzer (SPAN) destination port. All of these are unsuitable configurations for EtherChannels. The first [chars] is the interface name, and the second [chars] describes the details of the unsuitable configuration.

Recommended Action Reconfigure the port; remove the unsuitable configuration.

2-30

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

ETHCNTR Messages

This section contains the Ethernet controller messages. These messages result from 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 treated as a

loopback. [chars] is the port where the threshold was exceeded.

Recommended Action No action is required. The port goes into error-disabled mode until the problem

is resolved.

Error Message ETHCNTR-3-LOOP_BACK_DETECTED:, Loop-back detected on [chars]. The port is forced to linkdown.

Explanation This message occurs when a keepalive packet is looped back to the port that sent the

keepalive. The loopback condition might be caused by a balun cable being accidentally connected to the port, or there might be a loop in the network. [chars] is the port.

ETHCNTR Messages

Recommended Action Examine 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. We do not recommend using the no keepalive interface command to disable keepalives. The cause of this network loop must be found and corrected. Although disabling keepalives prevents the port from being error disabled, it does not resolve the cause of the problem and can affect network stability. See

CSCea46385 for more

information.

Error Message ETHCNTR-3-NO_HARDWARE_RESOURCES: Not enough hardware resources. Shutting down [chars].

Explanation There are too many VLANs and routed ports (if the switch supports routed ports)

configured. [chars] is the short interface name, such as Gi1/0/1 on a stacking-capable switch, or the VLAN name, such as VLAN0002.

Recommended Action Reduce the total number of VLANs and routed ports to less than 1023. To

preserve configuration and connections across reboots, save the configuration.

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. [dec] is the stack member number.

OL-12191-01

Recommended Action Replace the stack member with a switch that supports forwarding of IPv4 and

IPv6 frames with SNAP encapsulation.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-31

EXPRESS_SETUP Messages

This section contains the Express Setup messages that appear when you use a 10/100/1000 or the Ethernet management port to connect to the PC. For Express Setup with the Ethernet management port, see the

Error Message EXPRESS_SETUP-3-UNABLE_TO_RESET_CONFIG: [chars].

CLS_ACC Messages section.

Explanation The system is unable to reset the configuration. [chars] is a text string that explains why

the reset failed. For example,

error removing private config file.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Chapter 2 Message and Recovery Procedures

error renaming config file, error removing config file, or

“Error Message Traceback Reports” section on page 1-6.

Error Message EXPRESS_SETUP-6-CONFIG_IS_RESET: [chars].

Explanation The configuration is reset. [chars] is a text message that clarifies the reset event, such

as

The configuration is reset and the system will now reboot.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message EXPRESS_SETUP-6-MODE_ENTERED.

Explanation The Express Setup mode is active.

Recommended Action No action is required.

Error Message EXPRESS_SETUP-6-MODE_EXITED.

Explanation The Express Setup mode is no longer active.

Recommended Action No action is required.

“Error Message Traceback Reports” section on page 1-6.

2-32

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

FRNTEND_CTRLR Messages

This section contains the front-end controller messages on stacking-capable switches.

Error Message FRNTEND_CTRLR-1-MGR_TXQ_FULL: The front end controller Tx queue reached watermark level

Note This message applies only to the Catalyst Switch Module 3110.

Explanation There are too many messages in the queue between the front-end controller and the

switch software.

Recommended Action Reset the switch. If the problem is not resolved, contact your Cisco technical

support representative because there might be a problem with the switch.

Error Message FRNTEND_CTRLR-2-SUB_INACTIVE: The front end controller [dec] is inactive.

FRNTEND_CTRLR Messages

Note This message applies only to the Catalyst Switch Module 3110.

Explanation The front-end controller that controls the LEDs and the fan-control features is now

inactive on the port controlled by the front-end controller. This does not affect the traffic on the port. [dec] is the controller number.

Recommended Action Reset the switch. If the problem is not resolved, contact your Cisco technical

support representative because there might be a problem with the switch.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-33

GBIC_SECURITY Messages

This section contains the 10-Gigabit Ethernet module security messages.

Note The Catalyst Switch Module 3110X supports 10-Gigabit Ethernet modules and does not support Cisco

Gigabit Interface Converter (GBIC) modules. Although the error message text refers to GBIC interfaces and modules, the messages from the switch actually refer to the 10-Gigabit Ethernet module interfaces and modules.

Error Message GBIC_SECURITY-4-EEPROM_CRC_ERR: EEPROM checksum error for GBIC in [chars].

Note This message applies only to the Catalyst Switch Module 3110X.

Explanation The GBIC in the specified port has invalid EEPROM data. [chars] is the port in which

the GBIC is inserted.

Chapter 2 Message and Recovery Procedures

Recommended Action Remove the GBIC from the port.

Error Message GBIC_SECURITY-4-EEPROM_READ_ERR: Error in reading GBIC serial ID in

[chars].

Note This message applies only to the Catalyst Switch Module 3110X.

Explanation An error occurred while the switch was reading the GBIC type from the EEPROM.

[chars] is the port in which the GBIC is inserted.

Recommended Action Remove the GBIC from the port.

Error Message GBIC_SECURITY-4-EEPROM_SECURITY_ERR: GBIC in [chars] failed security

check.

Note This message applies only to the Catalyst Switch Module 3110X.

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.

2-34

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message GBIC_SECURITY-4-GBIC_INTERR: Internal error occurred in setup for GBIC

interface [chars].

Note This message applies only to the Catalyst Switch Module 3110X.

Explanation The system could not allocate resources or had some other problem during the setup for

the specified SFP module interface. [chars] is the interface in which the SFP module is installed.

Recommended Action Reload the switch by using the reload privileged EXEC command. If the

problem persists, find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting IBM, see the

Reports” section on page 1-6.

Error Message GBIC_SECURITY-6-SFP_INSERTED: Transceiver SFP [chars] module inserted in [chars]

GBIC_SECURITY Messages

“Error Message Traceback

Note This message applies only to the Catalyst Switch Module 3110X.

Explanation The online insertion and removal (OIR) facility detected a newly inserted transceiver

module for the interface specified in the message. The first [chars] is the module and the second [chars] is the interface.

Recommended Action No action is required.

Error Message GBIC_SECURITY-6-SFP_REMOVED: Transceiver SFP [chars] module removed

from [chars]

Note This message applies only to the Catalyst Switch Module 3110X.

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.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-35

GBIC_SECURITY_CRYPT Messages

This section contains the 10-Gigabit Ethernet module security messages. The switch recognizes the module as a Cisco module but identifies another problem with it.

Note The Catalyst Switch Module 3110X supports 10-Gigabit Ethernet modules but do not support GBIC

modules. Although the error message text refers to GBIC interfaces and modules, the messages from the switch actually refer to the 10-Gigabit Ethernet module interfaces and modules.

Error Message GBIC_SECURITY_CRYPT-4-ID_MISMATCH: Identification check failed for GBIC in port [chars]

Note This message applies only to the Catalyst Switch Module 3110X.

Explanation The small form-factor pluggable (SFP) module was identified as a Cisco SFP module,

but the system could not verify its identity. [chars] is the port.

Chapter 2 Message and Recovery Procedures

Recommended Action Ensure that the Cisco IOS software running on the switch supports the SFP

module. You might need to upgrade your software. Otherwise, verify that the SFP module was obtained from Cisco or from a supported vendor.

Error Message GBIC_SECURITY_CRYPT-4-UNRECOGNIZED_VENDOR: GBIC in port [chars] manufactured by an unrecognized vendor

Note This message applies only to the Catalyst Switch Module 3110X.

Explanation The small form-factor pluggable (SFP) module was identified as a Cisco SFP module,

but the switch could not match its manufacturer with one on the known list of Cisco SFP module vendors. [chars] is the port.

Recommended Action Ensure that the Cisco IOS software running on the switch supports the SFP

module. You might need to upgrade your software.

Error Message GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port [chars] has bad crc

Note This message applies only to the Catalyst Switch Module 3110X.

2-36

Explanation The small form-factor pluggable (SFP) module was identified as a Cisco SFP module,

but it does not have a valid cyclic redundancy check (CRC) in the EEPROM data. [chars] is the port.

Recommended Action Ensure that the Cisco IOS software running on the switch supports the SFP

module. You might need to upgrade your software. Even if the SFP module is unrecognized by the switch, the SFP module might still operate properly but have limited functionality.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

GBIC_SECURITY_UNIQUE Messages

This section contains the 10-Gigabit Ethernet module security messages that identify whether the module is unique.

Note The Catalyst Switch Module 3110X supports only 10-Gigabit Ethernet modules and do not support

GBIC modules. Although the error message text refers to GBIC interfaces and modules, the messages from the switch actually refer to the 10-Gigabit Ethernet module interfaces and modules.

Error Message GBIC_SECURITY_UNIQUE-3-DUPLICATE_GBIC: GBIC interface [dec]/[dec] is a duplicate of GBIC interface [dec]/[dec].

Note This message applies only to the Catalyst Switch Module 3110X.

Explanation The SFP module was identified as a Cisco GBIC or SFP module, but its vendor ID and

serial number match that of another interface on the system. The first [dec]/[dec] is the interface of the duplicate GBIC or SPF module, and the second [dec]/[dec] is the interface of the existing module.

GBIC_SECURITY_UNIQUE Messages

Recommended Action Cisco GBIC or SFP modules are assigned unique serial numbers. Verify that

the module was obtained from Cisco or from a supported vendor.

Error Message GBIC_SECURITY_UNIQUE-4-DUPLICATE_SN: GBIC interface [dec]/[dec] has the same serial number as another GBIC interface.

Note This message applies only to the Catalyst Switch Module 3110X.

Explanation The SFP module was identified as a Cisco SFP module, but its serial number matches

that of another interface on the system. [dec]/[dec] is the interface in which the duplicate module is installed.

Recommended Action Cisco SFP modules are assigned unique serial numbers. Verify that the module

was obtained from Cisco or from a supported vendor.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-37

HARDWARE Messages

This section contains 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. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the

Traceback Reports” section on page 1-6.

Error Message HARDWARE-2-FAN_ERROR: Fan Failure.

Chapter 2 Message and Recovery Procedures

“Error Message

Explanation The fan is not working.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the

“Error

Message Traceback Reports” section on page 1-6.

Error Message HARDWARE-2-THERMAL_WARNING: Temperature has reached warning threshold.

Explanation The temperature sensor valve inside the switch reached the warning threshold. The

switch can function normally until the temperature reaches the critical threshold.

Recommended Action The external temperature is high. Reduce the temperature in the room.

Error Message HARDWARE-3-ASICNUM_ERROR: Port-ASIC number [dec] is invalid.

Explanation The port ASIC number used is invalid. Each port ASIC is identified by an ID. [dec] is

the ASIC 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. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

2-38

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

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. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message HARDWARE-3-INTRNUM_ERROR: Port-ASIC Interrupt number [dec] is invalid.

Explanation The interrupt ID used in a port ASIC is invalid. [dec] is the interrupt 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. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

HARDWARE Messages

“Error Message Traceback Reports” section on page 1-6.

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. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message HARDWARE-3-THERMAL_NOT_FUNCTIONING: Temperature Sensor is not functioning.

Explanation The temperature sensor is not functioning, and the switch temperature behavior cannot

“Error Message Traceback Reports” section on page 1-6.

be determined.

Recommended Action Ensure that the ambient temperature is not too high. If the problem persists,

replace the component.

Error Message HARDWARE-3-STATS_ERROR: Statistics ID [dec] is invalid.

Explanation The statistics ID used is out of range. The statistics supported by the port ASIC are

identified by an ID. [dec] is the statistics ID.

OL-12191-01

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

“Error Message Traceback Reports” section on page 1-6.

2-39

HLFM Messages

Error Message HARDWARE-5-FAN_NOT_PRESENT: Fan is not present.

Explanation The fan is not in the switch.

Recommended Action Make sure the fan is completely inserted. If the fan is removable, remove and

replace it into the switch. If the problem persists after insertion, replace the fan.

Error Message HARDWARE-5-FAN_OK: Fan works fine.

Explanation The fan is now working properly.

Recommended Action No action is required.

HLFM Messages

This section contains messages from the local forwarding manager.

Chapter 2 Message and Recovery Procedures

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.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message HLFM-3-MAP_ERROR: IP address [IP_address] not in mac tables, mac-address [enet], vlan [dec].

Explanation The IP address and MAC address tables are out of sync. [IP_address] is the IP address,

“Error Message Traceback Reports” section on page 1-6.

[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.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

2-40

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message HLFM-3-MOD_SD: Failed to modify Station Descriptor with index [dec],

vlan [dec], di [dec], error [dec], mad [dec], ref-count [dec].

Explanation The forwarding manager attempted to modify a station descriptor that is no longer in

use or is invalid. The first [dec] is the station index, the second [dec] is the VLAN ID, the third [dec] is the destination index, the fourth [dec] is the error code, the fifth [dec] is the MAC address descriptor, and the sixth [dec] is the ref-count for this MAC address descriptor.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message HLFM-3-SEND_FAIL: Failed to send RPC message, req [dec], [chars].

Note This message applies only to the Catalyst Switch Module 3110.

HPSECURE Messages

“Error Message Traceback Reports” section on page 1-6.

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. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

HPSECURE Messages

This section contains port-security messages.

Error Message HPSECURE-6-ADDR_REMOVED: Address [enet]:[dec] on port [chars] cannot be added on switch [dec] and has been removed.

Note This message applies only to the Catalyst Switch Module 3110.

Explanation At least one switch in the stack could not add the MAC address due to a resource failure,

and the MAC address has been deleted from all the switches in the stack. [enet] is the MAC address, the first [dec] is the VLAN to which the MAC address is assigned, [chars] is the interface, and the second [dec] is the stack member number.

“Error Message Traceback Reports” section on page 1-6.

OL-12191-01

Recommended Action No action is required.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-41

IGMP_QUERIER Messages

This section contains the IGMP querier messages.

Error Message IGMP_QUERIER-4-NO_IP_ADDR_CFG: The IGMP querier cannot send out General Query messages in VLAN [dec] because there is no IP address configured on the system.

Explanation You must specify an IP address for the IGMP querier at either the global or per-VLAN

level. [dec] is the VLAN ID.

Recommended Action Configure a source IP address for the IGMP querier.

Error Message IGMP_QUERIER-4-PIM_ENABLED: The IGMP querier is operationally disabled

in VLAN [dec] because PIM has been enabled on the SVI.

Explanation PIM was detected on the SVI. Do not enable the IGMP querier when PIM is enabled on

the SVI. [dec] is the VLAN ID.

Chapter 2 Message and Recovery Procedures

Recommended Action Ensure that PIM is disabled on the SVI.

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.

Error Message IGMP_QUERIER-6-PIM_DISABLED: The IGMP querier is now operationally

enabled in VLAN [dec] because PIM is no longer enabled on the SVI.

Explanation Protocol-Independent Multicast (PIM) is disabled on the switch virtual interface (SVI),

and the IGMP querier function is now enabled. [dec] is the VLAN ID.

Recommended Action No action is required.

Error Message IGMP_QUERIER-6-SNOOPING_ENABLED: The IGMP querier is now operationally

enabled in VLAN [dec] because IGMP snooping is no longer disabled.

Explanation IGMP snooping was enabled. As a result, the IGMP querier function is now enabled.

[dec] is the VLAN ID.

2-42

Recommended Action No action is required.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

IMAGEMGR Messages

This section contains image manager messages, which are related to image compatibility within the stack.

Error Message IMAGEMGR-6-AUTO_ADVISE_SW_INITIATED: Auto-advise-software process initiated for systems [bits: [hex]].

Note This message applies only to the Catalyst Switch Module 3110.

Explanation Systems with incompatible software have been detected in the switch stack.

Auto-advise software informs you when not all switches in the stack are running the same software version. The stack master then attempts to upgrade all switches running different versions to the version that the master is running. The stack finds out whether or not software is available to be copied to the incompatible systems and if so, advises you how to copy it. Otherwise, the system informs you that the software on the switch stack needs to be updated. [bits [hex]] is the bit representation of the switch number.

IMAGEMGR Messages

Recommended Action No action is required.

Error Message IMAGEMGR-6-AUTO_ADVISE_SW: [chars].

Note This message applies only to the Catalyst Switch Module 3110.

Explanation A line of output from the auto-advise-software process is being displayed. [chars] is a

text message reporting status of the upgrade process.

Recommended Action No action is required.

Error Message IMAGEMGR-6-AUTO_COPY_SW_INITIATED: Auto-copy-software process

initiated for systems [bits: [hex]].

Note This message applies only to the Catalyst Switch Module 3110.

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.

OL-12191-01

Recommended Action No action is required.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-43

IP_DEVICE_TRACKING Messages

Error Message IMAGEMGR-6-AUTO_COPY_SW: [chars].

Note This message applies only to the Catalyst Switch Module 3110.

Explanation A line of output from the auto-copy-software process appears. [chars] is a text message

reporting status of the upgrade process.

Recommended Action No action is required.

Error Message IMAGEMGR-6-AUTO_DOWNLOAD_SW_INITIATED: Auto-download-software process

initiated for systems [bits: [hex]].

Note This message applies only to the Catalyst Switch Module 3110.

Explanation Systems with incompatible software have been detected in the switch stack. The stack

now attempts to download software from a previously configured location and to install it to make the systems compatible. [bits [hex]] is the bit representation of the switch number.

Chapter 2 Message and Recovery Procedures

Recommended Action No action is required.

Error Message IMAGEMGR-6-AUTO_DOWNLOAD_SW: [chars].

Note This message applies only to the Catalyst Switch Module 3110.

Explanation A line of output from the auto-download-software process appears [chars] is a text

message reporting the status of the upgrade process.

Recommended Action No action is required.

IP_DEVICE_TRACKING Messages

This section contains the IP Device Tracking message.

Error Message IP_DEVICE_TRACKING-4-TABLE_LOCK_FAILED: Table already locked by process-id [dec]([chars])

Note This message applies only to the Catalyst Switch Module 3110.

2-44

Explanation The IP device tracking table could not be updated due to a lock held by another process.

[dec] is the process number, and [chars] is the process.

Recommended Action No action is required.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

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.

PHY Messages

This section contains the PHY messages.

MAC_MOVE 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 IBM

technical support representative.

Error Message PHY-4-CHECK_SUM_FAILED: SFP EEPROM data check sum failed for SFP interface [chars].

Explanation The SFP module was identified as a Cisco SFP module, but the system cannot read the

vendor data information to verify whether it is correct. [chars] is the interface in which the SFP module is installed.

Recommended Action Remove and then reinsert the SFP module. If it fails again with the same error

message, the SFP module might be defective.

Error Message PHY-4-EXCESSIVE_ERRORS: Excessive FCS, data, or idle word errors found on interface [chars].

Explanation The system detected excessive frame check sequence (FCS), data word, or idle word

errors on the specified interface. [chars] is the interface.

OL-12191-01

Recommended Action Enter the show interface privileged EXEC command on the specified

interface, and check for cyclic redundancy check (CRC) and other input errors. If errors are excessive, enter the shutdown interface configuration command and then the no shutdown interface configuration command to reset the interface.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-45

PHY Messages

Chapter 2 Message and Recovery Procedures

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.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems.If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

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 Remove the unsupported SFP module, and get a supported SFP module.

“Error Message Traceback Reports” section on page 1-6.

Error Message PHY-4-UNSUPPORTED_SFP_CARRIER: Unsupported SFP carrier module found in [chars]

Explanation The small form-factor pluggable (SFP) carrier module was identified as an unsupported

non-Cisco SFP carrier module. [chars] is the unsupported module.

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. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message PHY-4-UNSUPPORTED_TRANSCEIVER:Unsupported transceiver found in [chars]

Explanation The SFP module was identified as a unsupported, non-Cisco SFP module. [chars] is the

“Error Message Traceback Reports” section on page 1-6.

unsupported module.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

2-46

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

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. The first [chars] is the PIM snooping mode, and the second [chars] is the IGMP snooping mode.

Recommended Action No action is required.

Error Message PIMSN-6-IGMPSN_VLAN: PIM Snooping runtime mode on vlan [dec] [chars]

due to IGMP Snooping [chars].

PIMSN Messages

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. [dec] is the VLAN ID, the first [chars] is the PIM snooping mode, and the second [chars] is the IGMP snooping mode.

Recommended Action No action is required.

PLATFORM Messages

This section contains low-level platform-specific messages.

Error Message PLATFORM-1-CRASHED: [chars].

Explanation The system is attempting to display the failure message from the previous failure.

[chars] is the description of the error message.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

OL-12191-01

Error Message PLATFORM-3-NO_HARDWARE_RESOURCES: Not enough hardware resources.

Shutting down [chars].

Explanation There are too many VLANs and routed ports. [chars] is the short interface name, such

as Gi1/0/1, or the VLAN name, such as VLAN0002.

Recommended Action Reduce the total number of VLANs and routed ports to be less than 1023. To

preserve configurations and connections across reboots, save the configuration.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-47

PLATFORM Messages

Chapter 2 Message and Recovery Procedures

Error Message PLATFORM-3-PW_REC_HRPC_BAD_LENGTH: Received incompatible length

(=[dec]) in set-password-recovery HRPC message from box [dec].

Note This message applies only to the Catalyst Switch Module 3110.

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.

Recommended Action Make sure that all stack members are running compatible software images. If the

problem persists, find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting IBM, see the

Reports” section on page 1-6.

Error Message PLATFORM-3-PW_REC_HRPC_NOT_ON_MASTER: Set-password-recovery HRPC msg from box [dec] received on master.

“Error Message Traceback

Note This message applies only to the Catalyst Switch Module 3110.

Explanation The stack master has received a set-password-recovery HRPC message. These messages

should be received on stack member switches only. [dec] is the switch.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message PLATFORM-3-PW_REC_HRPC_ONLY_ON_MASTER: Get-password-recovery HRPC msg from box [dec] received on member.

Note This message applies only to the Catalyst Switch Module 3110.

Explanation A stack member switch has received a get-password-recovery HRPC message. These

“Error Message Traceback Reports” section on page 1-6.

messages should only be received by the stack master. [dec] is the switch.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

2-48

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

PLATFORM_ENV Messages

This section contains platform-specific environment messages.

Error Message PLATFORM_ENV-1-FAN: Faulty fan detected.

Explanation A faulty fan is detected.

Recommended Action If the message appears again, immediately replace the switch fan.

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.

PLATFORM_ENV Messages

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.

Recommended Action This problem could be transient. If the problem persists, replace the power

supply.

Error Message PLATFORM_ENV-1-TEMP: Abnormal temperature detected.

Explanation An abnormal temperature is detected.

Recommended Action Ensure that ambient temperature is not too high. If the problem persists, check

the switch temperature by entering the show env all privileged EXEC command.

PLATFORM_FBM Messages

This section contains the platform fallback bridging manager (FBM) messages.

Error Message PLATFORM_FBM-4-RECOVERED: Fallback bridging recovered from resource crunch.

OL-12191-01

Explanation Fallback bridging has recovered from an earlier lack of resource.

Recommended Action No action is required.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-49

PLATFORM_HCEF Message

Error Message PLATFORM_FBM-4-RESOURCE_CRUNCH: Fallback bridging on bridge-group

[dec] is experiencing a resource crunch. One or more bridge-groups may not be functional. It will recover automatically when system recovers from resource crunch. Delete the bridge-group to immediately recover.

Explanation Fallback bridging could not be properly configured. The most likely cause is a

hardware-full condition on at least one stack member.

Recommended Action The switch automatically recovers, but this could take some time. For an

immediate recovery, use the shutdown interface configuration command to disable the port and to stop the traffic flow to the switch. Use the clear mac-address-table dynamic privileged EXEC command to remove all MAC addresses from the hardware. Use the no shutdown interface configuration command to re-enable the port.

PLATFORM_HCEF Message

This section has the Cisco Express Forwarding message.

Chapter 2 Message and Recovery Procedures

Error Message PLATFORM_HCEF-3-ADJ: [chars]

Note This message applies only to the Catalyst Switch Module 3110.

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. Only Distance Vector Multicast Routing

Protocol (DVMRP) tunnels are supported. If the GRE tunnel is configured, remove the tunnel, or upgrade the switch software to a Cisco IOS release when the GRE feature is needed. If the ip cef accounting command is configured, remove it by using the no ip cef accounting global configuration command.

PLATFORM_HPLM Messages

This section has the platform pseudo label manager messages.

Error Message PLATFORM_HPLM-3-ERROR: Failed Alloc for xaction record label move from [dec] to [dec].

2-50

Explanation An internal resource allocation error occurred during the label compaction process. The

first [dec] is the previous label, and the second [dec] is the new label.

Recommended Action Copy the error message exactly as it appears on the console or in the system

log, call your IBM technical support representative, and provide the representative with the gathered information.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message PLATFORM_HPLM-6-LABEL_COMPLETE: VRF Label compaction complete.

Explanation The VRF label compaction process has successfully completed.

Recommended Action No action is required.

Error Message PLATFORM_HPLM-6-LABEL_FAILED: VRF Label compaction failed.

Explanation The VRF label compaction process has failed.

Recommended Action No action is required.

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].

Note This message applies only to the Catalyst Switch Module 3110.

Explanation There has been an IPC failure. [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. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message PLATFORM_IPC-3-MASTER: [chars].

Note This message applies only to the Catalyst Switch Module 3110.

“Error Message Traceback Reports” section on page 1-6.

OL-12191-01

Explanation There has been an IPC failure on the stack master. [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. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

“Error Message Traceback Reports” section on page 1-6.

2-51

PLATFORM _IPC Messages

Error Message PLATFORM_IPC-3-MAX_LENGTH_EXCEEDED: [chars].

Note This message applies only to the Catalyst Switch Module 3110.

Error Message PLATFORM_IPC-3-MEMBER: [chars].

Note This message applies only to the Catalyst Switch Module 3110.

Chapter 2 Message and Recovery Procedures

Explanation An internal IPC application error occurred when an IPC message was sent that exceeded

the maximum length. [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. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

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. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message PLATFORM_IPC-3-STACK_EVENT: [chars].

Note This message applies only to the Catalyst Switch Module 3110.

Explanation There has been an IPC failure in the stack. [chars] describes the error message.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

“Error Message Traceback Reports” section on page 1-6.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

2-52

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

PLATFORM_IPv6_UCAST Message

This section contains the IP Version 6 Unicast message.

Error Message PLATFORM_IPv6_UCAST-6-PREFIX: One or more, more specific prefixes could not be programmed into TCAM and are being covered by a less specific prefix

Note This message applies only to the Catalyst Switch Module 3110.

Explanation A more specific prefix could not be programmed into Ternary Content Addressable

Memory (TCAM) and is covered by a less specific prefix. This could be a temporary condition. The output of the show platform ipv6 unicast retry route privileged EXEC command lists the failed prefixes.

Recommended Action No action is required.

PLATFORM_IPv6_UCAST Message

PLATFORM_PBR Messages

This section contains policy based routing (PBR) messages.

Error Message PLATFORM_PBR-2-NO_RMAP: Cannot create PBR data structures for route-map [chars].

Explanation The PBR manager could not allocate the internal data structures for this route-map. A

likely cause is lack of available memory. [chars] is the route-map.

Recommended Action Simplify the configuration so that it requires less memory.

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.

Error Message PLATFORM_PBR-3-NO_LABEL: Cannot allocate label for route-map [chars].

OL-12191-01

Explanation The PBR manager could not allocate a label for this route-map. As a result, the hardware

cannot be programmed to implement policy routing. There is a limit of 247 labels for policy routing. [chars] is the route-map.

Recommended Action Simplify the configuration with label sharing. Use the same route-maps on

multiple interfaces, if possible.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-53

PLATFORM_PBR Messages

Error Message PLATFORM_PBR-3-UNSUPPORTED_RMAP: Route-map [chars] not supported for

Policy-Based Routing.

Error Message PLATFORM_PBR-4-CPU_SUPPORTED_ACTION: Set action in sequence [dec] of route-map [chars] supported by forwarding to CPU.

Chapter 2 Message and Recovery Procedures

Explanation The route-map attached to an interface for policy routing contains an action that is not

supported on this platform. This is a hardware limitation. [chars] is the route-map.

Recommended Action Use the route-map map-tag permit global configuration command and the set

ip next-hop ip-address route-map configuration command to reconfigure the route map to use only

these supported actions.

Explanation The route-map attached to an interface for policy-based routing contains an action that

is not supported in hardware, so the packets are forwarded to the CPU for processing. The route-map actions that invoke this forwarding are set interface, set ip default next-hop, set default interface, or set ip df. [dec] is the action number, and [chars] is the route-map.

Recommended Action Use the set ip next-hop ip-address route-map configuration command to

reconfigure the route map action to route the packet to the specified next hop.

Error Message PLATFORM_PBR-4-RETRY_INSTALL: Route-map [chars] installed in hardware upon retry.

Explanation The PBR manager was able to fit the complete configuration into the hardware. One or

more route-maps previously failed to load because of lack of resources. [chars] is the route-map.

Recommended Action No action is required.

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.

2-54

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

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.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message PLATFORM_PM-3-INTVLANINUSE: internal vlan-id [dec] allocated for interface [chars] is still in use.

PLATFORM_PM Messages

“Error Message Traceback Reports” section on page 1-6.

Explanation An internal VLAN ID allocated for an interface is still in use. [dec] is the VLAN ID,

and [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. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message PLATFORM_PM-3-NOINTVLAN: internal vlan of interface [chars] is not active for vlan-id [dec].

Explanation Internal vlan_data is not active for the given VLAN ID. [chars] is the interface, and

“Error Message Traceback Reports” section on page 1-6.

[dec] is the VLAN ID.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-55

PLATFORM_RPC Messages

This section contains platform-specific remote procedure call (RPC) messages. The RPC function in the switch stack allows instances of code running on the various systems in a stack to intercommunicate by using a virtual function-call mechanism.

Error Message PLATFORM_RPC-0-RESOURCE_CRASH: [chars].

Note This message applies only to the Catalyst Switch Module 3110.

Explanation The system is unable to allocate memory for RPC. [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. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Chapter 2 Message and Recovery Procedures

“Error Message Traceback Reports” section on page 1-6.

Error Message PLATFORM_RPC-3-BAD_CLASS: Bad Class in RPC message: [int].

Note This message applies only to the Catalyst Switch Module 3110.

Explanation There is a missing entry in the class table for a message class. [int] is the number of the

missing message class.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type [int], class [int], max_msg [int], total throttled [int].

Note This message applies only to the Catalyst Switch Module 3110.

Explanation There are too many outgoing messages queued for a message class. An RSP message

“Error Message Traceback Reports” section on page 1-6.

was dropped. The first [int] is the message type, the second [int] is the message class, the third [int] is the maximum number of messages that can be queued before throttling occurs, and the last [int] is the total number of messages that have been throttled.

2-56

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

“Error Message Traceback Reports” section on page 1-6.

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message PLATFORM_RPC-3-PERSISTENT_UNABLE_TO_SEND: System is consistently

unable to send RPC message: [chars], paks_outstanding: [int].

Note This message applies only to the Catalyst Switch Module 3110.

Explanation The system is experiencing a persistent low-level transport failure in sending RPC

messages. [chars] is a description of the error returned by the low-level packet-sending driver that triggered the error (usually one of these: fifo full, fifo empty, out of buf, out of mem, null pointer, misc failure), and [int] is the number of packets outstanding (packets from the RPC code to the driver that have not yet been sent).

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message PLATFORM_RPC-3-RESP_FAIL: Unexpected response or failure, class [dec], req [dec], switch [dec], error [dec], [chars].

PLATFORM_RPC Messages

“Error Message Traceback Reports” section on page 1-6.

Note This message applies only to the Catalyst Switch Module 3110.

Explanation The platform received an unexpected response. The first [dec] is RPC request class, the

second [dec] is the RPC request number, the third [dec] is the destination switch number, the fourth [dec] is the returned error 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. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message PLATFORM_RPC-3-SEND_FAIL: Failed to send RPC message in class [dec], req [dec], [chars].

Note This message applies only to the Catalyst Switch Module 3110.

Explanation There is a local resource error or that too many outgoing messages are queued for the

“Error Message Traceback Reports” section on page 1-6.

message class. The first [dec] is RPC request class, the second [dec] is the RPC request number, and [chars] is an optional comment.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-57

PLATFORM_SPAN Messages

Error Message PLATFORM_RPC-3-UNABLE_TO_SEND: System is unable to send RPC message:

[chars], paks_outstanding: [int].

Note This message applies only to the Catalyst Switch Module 3110.

Chapter 2 Message and Recovery Procedures

Explanation The system had a low-level transport failure when trying to send an RPC message.

[chars] is a description of the error returned by the low-level packet sending driver that triggered the error (usually one of these: fifo full, fifo empty, out of buf, out of mem, null pointer, misc failure), and [int] is the number of packets outstanding (packets from the RPC code to the driver that have not yet been sent).

Recommended Action Find out more about the error by using the show tech-support privileged EXEC

command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting IBM, see the

Reports” section on page 1-6.

“Error Message Traceback

PLATFORM_SPAN Messages

This section contains the Switched Port Analyzer (SPAN) messages.

Error Message PLATFORM_SPAN-3-PACKET_DROP: Decreases egress SPAN rate.

Explanation Egress SPAN rates are falling because SPAN is enabled with multicast routing or

fallback bridging.

Recommended Action Find out more about the error by using the show tech-support privileged EXEC

command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting IBM, see the

Reports” section on page 1-6.

PLATFORM_UCAST Messages

This section contains platform unicast routing messages.

Error Message PLATFORM_UCAST-3-ADJ: [chars].

Explanation The adjacency module for unicast routing encountered an error. [chars] describes the

error.

“Error Message Traceback

2-58

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

“Error Message Traceback Reports” section on page 1-6.

OL-12191-01

Chapter 2 Message and Recovery Procedures

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. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message PLATFORM_UCAST-3-CEF: [chars].

Explanation The Cisco Express Forwarding (CEF) module for unicast routing encountered an error.

[chars] describes the error.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

PLATFORM_UCAST Messages

“Error Message Traceback Reports” section on page 1-6.

Error Message PLATFORM_UCAST-3-DYNAMIC: [chars].

Explanation The dynamic address tracking mechanism 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. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message PLATFORM_UCAST-3-ERROR: [chars].

Explanation An internal unicast routing error occurred. [chars] describes the error.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

“Error Message Traceback Reports” section on page 1-6.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-59

PLATFORM_UCAST Messages

Error Message PLATFORM_UCAST-3-HSRP: [chars].

Error Message PLATFORM_UCAST-3-INTERFACE: [chars].

Chapter 2 Message and Recovery Procedures

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. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Explanation A unicast routing interface error occurred. [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. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

Error Message PLATFORM_UCAST-3-RPC: [chars].

Explanation The RPC 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. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message PLATFORM_UCAST-6-PREFIX: One or more, more specific prefixes could not be programmed into TCAM and are being covered by a less specific prefix

Explanation The more specific prefix could not be programmed into Ternary Content Addressable

“Error Message Traceback Reports” section on page 1-6.

Memory (TCAM) and is covered by a less specific prefix. This could be a temporary condition. The output of the show platform ip unicast failed route privileged EXEC command lists the failed prefixes.

Recommended Action No action required.

2-60

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

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).

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message PLATFORM_VLAN-3-MVID_ERROR: Mapped Vlan ID value [dec] associated with vlan-id [dec] is invalid.

PLATFORM_VLAN Messages

“Error Message Traceback Reports” section on page 1-6.

Explanation An active VLAN is not correctly associated with a mapped-vlan-id (MVID). The first

[dec] is the VLAN ID, and the second [dec] is the MVID.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Error Message PLATFORM_VLAN-3-UNLOCK_FAIL: Failed to unlock vlan-id [dec], associated mapped vlan id value [dec].

Explanation The switch failed to unlock a VLAN ID. The most likely cause is that the VLAN is

“Error Message Traceback Reports” section on page 1-6.

already unlocked. The first [dec] is the VLAN ID, and the second [dec] is the MVID.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-61

PLATFORM_WCCP Messages

This section contains platform Web Cache Communication Protocol (WCCP) messages.

Error Message PLATFORM-WCCP-3-NO_LABEL: Cannot allocate WCCP Label

Note This message applies only to the Catalyst Switch Module 3110.

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.

Error Message PLATFORM-WCCP-4-SDM_MISMATCH: WCCP requires sdm template routing

Chapter 2 Message and Recovery Procedures

Note This message applies only to the Catalyst Switch Module 3110.

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 To support this feature, you need to enable the Switch Database Management (SDM)

routing template.

Recommended Action Modify the SDM template to enable the routing template. Use the sdm prefer

routing global configuration command, and then reload the switch by using the reload privileged

EXEC command.

Explanation The available memory for the switch processor is low. This can occur when too many

Layer 2 VLANs are configured. [dec] is the available memory.

Recommended Action Remove features from the system to reduce memory usage.

2-62

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message PM-2-NOMEM: Not enough memory available for [chars].

Explanation The port manager subsystem could not obtain the memory it needed to initialize the

specified operation. [chars] is the port manager operation.

Recommended Action 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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

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. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

PM Messages

“Error Message Traceback

Error Message PM-3-INTERNALERROR: Port Manager Internal Software Error ([chars]: [chars]: [dec]: [chars]).

Explanation An internal software error occurred in the port manager. The parameters identify the

problem for technical support. The first [chars] is the error message, and the second [chars] is the filename. [dec] is the line number, and the last [chars] is the function name.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

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.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

“Error Message Traceback Reports” section on page 1-6.

Research and attempt to resolve the error by using the Output Interpreter. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-63

PM Messages

Chapter 2 Message and Recovery Procedures

Error Message PM-4-BAD_APP_REQ: an invalid [chars] request by the ’[chars]’

application was detected.

Explanation The port manager detected an invalid request. The first [chars] is the invalid request, and

the second [chars] is the application making the request.

Recommended Action 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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

“Error Message Traceback

Error Message PM-4-BAD_CARD_SLOT: an invalid card slot ([dec]) was detected.

Explanation The port manager detected an invalid request. [dec] is the slot number.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

Error Message PM-4-BAD_COOKIE: [chars] was detected.

Explanation The port manager detected an invalid request. [chars] is the 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.

Use the Bug Toolkit to look for similar reported problems.If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

2-64

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message PM-4-BAD_HA_ENTRY_EVENT: Invalid Host access entry event ([dec]) is

received.

Explanation An invalid host access entry event was received; the host access table entry event should

be an add, delete, or update event. [dec] is the event that is received.

Recommended Action 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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

PM Messages

“Error Message Traceback

Error Message PM-4-BAD_PORT_NUMBER: an invalid port number ([dec]) was detected.

Explanation The port manager detected an invalid request. [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. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

Error Message PM-4-BAD_VLAN_COOKIE: an invalid vlan 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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-65

PM Messages

Chapter 2 Message and Recovery Procedures

Error Message PM-4-BAD_VLAN_ID: an invalid vlan id ([dec]) was detected.

Explanation The port manager detected an invalid request. [dec] is the VLAN ID.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

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. The first [chars] is the error, and the second and third [chars] are the affected interfaces.

“Error Message Traceback

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

Error Message PM-4-ERR_DISABLE_VP: [chars] error detected on [chars], vlan [dec]. Putting in err-disable state.

Explanation This is a defensive measure that puts the virtual port (that is, the port-VLAN pair) in an

error-disabled state when it detects a misconfiguration or misbehavior. If configured, a recovery will be attempted after the configured retry time (default time is 5 minutes). The first [chars] is the error, and the second [chars] is the port.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TA C, 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-6.

2-66

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

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.

Research and attempt to resolve the error by using the Output Interpreter. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

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.

PM Messages

“Error Message Traceback

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. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TA C, 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-6.

Error Message PM-4-EXT_VLAN_INUSE: VLAN [dec] currently in use by [chars].

Explanation The port manager failed to allocate the VLAN for external use because the VLAN is

being used by another feature. [dec] is the VLAN that is being used, and [chars] is the feature that is using it.

Recommended Action Reconfigure the feature (for example, the routed port) to use another internal

VLAN or to request another available VLAN.

Error Message PM-4-EXT_VLAN_NOTAVAIL: VLAN [dec] not available in Port Manager.

Explanation The port manager failed to allocate the requested VLAN. The VLAN is probably being

used as an internal VLAN by other features. [dec] is the requested VLAN.

Recommended Action Try to configure a different VLAN on the device.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-67

PM Messages

Chapter 2 Message and Recovery Procedures

Error Message PM-4-INACTIVE: putting [chars] in inactive state because [chars].

Explanation The port manager has been blocked from creating a virtual port for the switch port and

VLAN, causing the port to be in an inactive state. The reason for this condition is specified in the error message. The first [chars] is the interface name, and the second [chars] is the reason.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

Error Message PM-4-INT_FAILUP: [chars] failed to come up. No internal VLAN available.

Explanation The port manager failed to allocate an internal VLAN, and therefore the interface

cannot be enabled. [chars] is the interface name.

Recommended Action Remove the extended-range VLAN by using the no vlan vlan-id global

configuration command to free up resources.

“Error Message Traceback

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. To delete a routed port, use the no switchport interface configuration command.

Error Message PM-4-INVALID_HOST_ACCESS_ENTRY: Invalid Host access entry type ([dec]) is received.

Explanation An invalid host access entry type was received; the host access entry should be a

configured or a dynamic type. [dec] is the entry type that is received.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

2-68

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message PM-4-LIMITS: The number of vlan-port instances on [chars] exceeded the

recommended limit of [dec].

Explanation The total number of individual VLAN ports, counted over the module or switch, has

exceeded the recommended limit. VLANs can be counted more than once; if VLAN 1 is carried on ten interfaces, it will count as ten VLAN ports. On some platforms bundling is also ignored for purposes of this count; if eight interfaces on the same module are in one bundle, and the port channel is carrying VLAN 1, it will count as eight VLAN ports. [chars] is the module name (for example, switch or the module number), and [dec] is the recommended limit.

Recommended Action Reduce the number of trunks and VLANs configured in the module or switch

as recommended in [dec]. Enter the show interfaces trunk privileged EXEC command to see the total number of trunks and VLANs.

Error Message PM-4-NO_SUBBLOCK: No PM subblock found for [chars].

Explanation The port manager failed to find the subblock for this interface. [chars] is the interface

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 tech-support user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

PM Messages

“Error Message Traceback

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). The first [chars] is the port number, and the second [chars] is the re-activation event.

Recommended Action No action is required.

Error Message PM-4-PVLAN_TYPE_CFG_ERR: Failed to set VLAN [dec] to a [chars] VLAN.

Explanation The platform failed to set a private VLAN type. [dec] is the VLAN ID.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your IBM 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-6.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-69

PORT_SECURITY Messages

Error Message PM-4-TOO_MANY_APP: application ’[chars]’ exceeded registration limit.

Error Message PM-4-UNKNOWN_HOST_ACCESS: Invalid Host access value ([dec]) is

received.

Chapter 2 Message and Recovery Procedures

Explanation The port manager detected an invalid request. [chars] is the application.

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. If

you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback Reports” section on page 1-6.

Explanation The host access table is being accessed with an invalid host access value. [dec] is the

value that is received.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

“Error Message Traceback

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.

PORT_SECURITY Messages

This section contains the port security messages.

Error Message PORT_SECURITY-2-PSECURE_VIOLATION:Security violation occurred caused by MAC [enet] on port [chars].

Explanation An unauthorized device attempted to connect on a secure port. MAC [enet] is the MAC

address of the unauthorized device, and port [chars] is the secure port.

Recommended Action Identify the device that attempted to connect on the secure port. Notify your

network system administrator of this condition.

2-70

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message PORT_SECURITY-2-PSECURE_VIOLATION_VLAN: Security violation on port

[chars] due to MAC address [enet] on VLAN [dec]

Explanation An unauthorized device attempted to connect on a secure trunk port. [chars] is the

secure port, MAC [enet] is the MAC address of the unauthorized device, and [dec] is the VLAN ID.

Recommended Action Identify the device that attempted to connect through the secure trunk port.

Notify your network system administrator of this condition.

Error Message PORT_SECURITY-6-ADDR_REMOVED: Address [dec]:[enet] exists on port [chars]. It has been removed from port [chars].

Explanation A routed port is reconfigured as a switch port. The address in the previous switch

configuration conflicts with the running configuration and has been deleted. [dec]:[enet] is the MAC address of the port. [chars] is the reconfigured port.

Recommended Action No action is required.

Error Message PORT_SECURITY-6-ADDRESSES_REMOVED: Maximum system secure address count

reached. Some secure addresses configured on port [chars] removed.

PORT_SECURITY Messages

Explanation Some configured and sticky MAC addresses on the specified port were removed from

the configuration. The number of secure addresses that the system supports was exceeded. This condition occurs only during hot swapping or port-mode changes (for example, when the port is converted from a Layer 3 to a Layer 2 port). [chars] is the port.

Recommended Action No action is required.

Error Message PORT_SECURITY-6-VLAN_FULL: Vlan [dec] on port [chars] has reached its

limit. Address [enet] has been removed.

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.

Recommended Action No action is required.

Error Message PORT_SECURITY-6-VLAN_REMOVED: VLAN [int] is no longer allowed on port

[chars]. Its port security configuration has been removed.

Explanation A configured VLAN is not allowed either due to a port mode change or an allowed

VLAN list change and is removed from the configuration. [int] is the VLAN ID, and [chars] is the switch port assigned to the VLAN.

OL-12191-01

Recommended Action No action is required.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-71

Protocol Tunneling Messages

This section contains the protocol tunneling message.

Error Message PT-3-PT_HW_UNAVAIL: Protocol Tunneling hardware resource not available. [chars]

Note This message applies only to the Catalyst Switch Module 3110.

Explanation Protocol tunneling could not be enabled because no redirect registers are available.

Protocol tunneling requires redirect registers. [chars] is the hardware resource that is not available.

Recommended Action Disable any applications that use redirect registers, and try configuring the

protocol tunneling again.

QOSMGR Messages

Chapter 2 Message and Recovery Procedures

This section contains the quality of service (QoS) manager messages. An incorrect QoS setting causes these messages.

Error Message QOSMGR-3-FEATURE_NOT_FOUND: Cannot find feature for [chars].

Explanation An internal software error has occurred. [chars] is the description of the feature that the

software cannot find.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

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.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

“Error Message Traceback

2-72

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message QOSMGR-3-MERGE_RES_COUNT: Internal Error Invalid count.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

QOSMGR Messages

“Error Message Traceback

Error Message QOSMGR-3-NO_VMR_QOSLABEL: qm_generate_vmrs have no qos label.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

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.

Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-73

QOSMGR Messages

Chapter 2 Message and Recovery Procedures

Error Message QOSMGR-3-POLICER_RES_COUNT: Internal Error Invalid Policer count.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

“Error Message Traceback

Error Message QOSMGR-3-QUEUE_PTR_ERROR: queue pointers out of order [hex] [hex] [hex] [hex].

Explanation An internal software error has occurred. [hex] [hex] [hex] [hex] are the

software-computed queue pointer values. The parameters provide error details for technical support.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

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.

Recommended Action Copy the message exactly as it appears on the console or in the system log.

Research and attempt to resolve the error by using the Output Interpreter. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

“Error Message Traceback

Reports” section on page 1-6.

2-74

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message QOSMGR-3-RESOURCE_INTERNAL: Internal Error in resource allocation.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

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.

Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

QOSMGR Messages

“Error Message Traceback

Error Message QOSMGR-4-ACTION_NOT_SUPPORTED: Action is not supported in policymap [chars].

Explanation An action other than the set, trust, and police policy-map class configuration

commands was configured in a policy map. This is a hardware limitation. [chars] is the policy-map name.

Recommended Action Configure only the supported actions of set, trust, and police when in

policy-map class configuration mode.

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. Use only the match ip dscp

dscp-list class-map configuration command in a policy map that is attached to an egress interface. Only one match per class map is supported.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-75

QOSMGR Messages

Chapter 2 Message and Recovery Procedures

Error Message QOSMGR-4-COMMAND_FAILURE: Execution of [chars] command failed.

Explanation The command to configure a QoS setting failed. This is possibly due to lack of hardware

resources. [chars] is the description of the command.

Recommended Action Check if any other messages indicate resource failure. If other messages

indicate that the hardware resources are exceeded, retry the command with a smaller configuration. Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting IBM, see the

page 1-6.

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.

“Error Message Traceback Reports” section on

Recommended Action Reconfigure the class map or the policy map, and reduce the number of QoS

ACLs.

Error Message QOSMGR-4-MATCH_NOT_SUPPORTED: Match type is not supported in classmap [chars].

Explanation An unsupported match type was entered. Only the access-group acl-index-or-name, ip

dscp dscp-list, and ip precedence ip-precedence-list match types are supported with the match

class-map configuration command. [chars] is the class-map name.

Recommended Action Reconfigure the class map; use only the match access-group, match ip dscp,

and match ip precedence class-map configuration commands within the class map.

Error Message 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.

Recommended Action Do not configure a set or trust policy-map class configuration command in a

policy map and attach it to an egress interface. These policy-map actions are supported only on ingress interfaces.

2-76

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message QOSMGR-4-POLICER_PLATFORM_NOT_SUPPORTED: Policer configuration has

exceeded hardware limitation for policymap [chars].

Explanation The policy-map configuration has exceeded the limitation of the hardware. You

configured more policers together in all policy maps (by using the police or police aggregate policy-map class configuration command) than supported by hardware. [chars] is the policy-map name.

Recommended Action Reconfigure the class maps or the policy maps, or delete the policy map from

some interfaces.

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.

Recommended Action Reconfigure the class map or the policy map, and reduce the number of

policers.

RMON Messages

This section contains the remote network monitoring (RMON) messages.

Error Message RMON-5-FALLINGTRAP: Falling trap is generated because the value of [chars] has fallen below the falling-threshold value [dec].

Explanation A falling trap has been generated. The value of the specified MIB object has fallen

below the falling threshold value. [chars] is the MIB object, and [dec] is the threshold value.

Recommended Action Take appropriate action on the specified MIB object.

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.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-77

SDM Messages

This section contains the Switch Database Management (SDM) message on the stacking-capable switch.

Error Message SDM-6-MISMATCH_ADVISE: [chars].

Note This message applies only to the Catalyst Switch Module 3110.

Explanation A stack member cannot support the SDM template that the stack master is using.

Switches in the SDM mismatch state are not functional stack members. This error follows the STACKMGR-6-SWITCH_ADDED_SDM error message if it reports SDM_MISMATCH. [chars] displays mismatch information and recommended corrective actions.

Recommended Action Downgrade the SDM template of the stack master to make it compatible with

the stack member switches. For example, if the stack master uses the aggregator routing template, the message recommends downgrading the stack master to the desktop routing template by using the sdm prefer vlan desktop global configuration command.

Chapter 2 Message and Recovery Procedures

SPAN Messages

This section contains the Switched Port Analyzer (SPAN) messages.

Error Message SPAN-3-MEM_UNAVAIL: Memory was not available to perform the SPAN operation.

Explanation The system was unable to perform a SPAN operation because of a lack of memory.

Recommended Action Reduce other system activity to ease the memory demands.

Error Message SPAN-3-SESS_DEC_CFG: SPAN hardware resource is in use. [chars]

Explanation The system could not allocate a SPAN hardware resource for the feature specified in the

error message. It is possible that a distributed EtherChannel has been configured in the system that is using a SPAN hardware resource.

Recommended Action Remove one or all of the distributed EtherChannels from the system and retry

the operation.

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.

2-78

Recommended Action Remove one of the existing SPAN or RSPAN source sessions, and retry the

operation.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message SPAN-3-UNKN_ERR: An internal error occurred during a SPAN operation.

Explanation SPAN detected an error in its internal operation.

Recommended Action The error might be transient. Try the SPAN operation again. If a second attempt

also fails, reload the switch by using the reload privileged EXEC command to complete the operation.

Error Message SPAN-3-UNKN_ERR_PORT: An internal error occurred when configuring SPAN on port [chars].

Explanation SPAN detected an error in its internal operation. [chars] is the interface.

Recommended Action The error might be transient. Try the SPAN operation again. If the second

attempt also fails, reload the switch by using the reload privileged EXEC command to complete the operation.

SPANTREE Messages

This section contains the spanning-tree messages.

Error Message SPANTREE-2-BLOCK_BPDUGUARD: Received BPDU on port [chars] with BPDU Guard enabled. Disabling port.

Explanation A bridge protocol data unit (BPDU) was received on an interface that has the spanning

tree BPDU guard feature enabled. As a result, the interface was administratively shut down. [chars] is the interface name.

Recommended Action Either remove the device sending BPDUs, or disable the BPDU guard feature.

The BPDU guard feature can be locally configured on the interface or globally configured on all ports that have PortFast enabled. To disable BPDU guard on an interface, use the no spanning-tree

bpduguard enable interface configuration command. To disable BPDU guard globally, use the no spanning-tree portfast bpduguard default global configuration command. After you have

removed the device or disabled BPDU guard, re-enable the interface by entering the no shutdown interface configuration command.

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.

OL-12191-01

Recommended Action Either remove the device sending BPDUs, or disable the BPDU guard feature.

The BPDU guard feature can be locally configured on the interface or globally configured on all ports that have Port Fast enabled. Re-enable the interface and vlan by entering the clear errdisable privileged EXEC command.

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-79

SPANTREE Messages

Chapter 2 Message and Recovery Procedures

Error Message SPANTREE-2-BLOCK_PVID_LOCAL: Blocking [chars] on [chars]. Inconsistent

local 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 listed interface. The first [chars] is the interface, and the second [chars] is the spanning-tree instance.

Recommended Action Verify that the configuration of the native VLAN ID is consistent on the

interfaces on each end of the IEEE 802.1Q trunk connection. When corrected, spanning tree automatically unblocks the interfaces, as appropriate.

Error Message SPANTREE-2-BLOCK_PVID_PEER: Blocking [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. The first [chars] is the interface, and the second [chars] is the spanning-tree instance.

Recommended Action Verify that the configuration of the native VLAN ID is consistent on the

interfaces on each end of the IEEE 802.1Q trunk connection. When interface inconsistencies are corrected, spanning tree automatically unblocks the interfaces.

Error Message SPANTREE-2-CHNL_MISCFG: Detected loop due to etherchannel misconfiguration of [chars] [chars].

Explanation A misconfiguration of a channel group has been detected. For example, the ports on one

side of the EtherChannel either are not configured to be in the channel or failed to bundle into the channel, and the other side has successfully bundled the ports into the EtherChannel. The first [chars] is the port, and the second [chars] is the VLAN.

Recommended Action Identify the local ports by using the show interfaces status err-disabled

privileged EXEC command, and then check the EtherChannel configuration on the remote device by using the show etherchannel summary privileged EXEC command on the remote device. After the configuration is correct, enter the shutdown and then no shutdown interface configuration commands on the associated port-channel interfaces.

2-80

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

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. The first [chars] is the port name, and the second [chars] is the spanning-tree mode displayed in the show spanning-tree privileged EXEC command.

Recommended Action Enter the show spanning-tree inconsistentports privileged EXEC command

to review the list of interfaces with loopguard inconsistencies. Find out why devices connected to the listed ports are not sending BPDUs. One reason might be that they are not running the STP. If so, you should disable loop guard on the inconsistent interfaces by using the spanning-tree guard none interface configuration command or by starting the STP on the remote side of the links.

Error Message SPANTREE-2-LOOPGUARD_CONFIG_CHANGE: Loop guard [chars] on port [chars] on [chars].

Explanation The spanning-tree loopguard configuration for the listed interface has been changed. If

enabled, the interface is placed into the blocking state. It is marked as loopguard-inconsistent when the message-age timer expires because no BPDUs were received from the designated bridge. This feature is mainly used to detect unidirectional links. 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.

SPANTREE Messages

Recommended Action Verify that this is the desired configuration for the listed interface. Correct it if

this is not the desired configuration; otherwise, no further action is required.

Error Message SPANTREE-2-LOOPGUARD_UNBLOCK: Loop guard unblocking port [chars] on [chars].

Explanation The listed interface has received a BPDU, and therefore, if the inconsistency was caused

by a unidirectional link failure, the problem no longer exists. The loopguard-inconsistency is cleared for the interface, which is taken out of the blocking state, if appropriate. The first [chars] is the port name, and the second [chars] is the spanning-tree mode displayed in the show spanning-tree privileged EXEC command.

Recommended Action No action is required.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-81

SPANTREE Messages

Chapter 2 Message and Recovery Procedures

Error Message SPANTREE-2-PVSTSIM_FAIL: Blocking [chars] port [chars]: Inconsistent

[chars] PVST BPDU received on VLAN [dec], claiming root [dec]:[enet]

Explanation The specified port on the MST switch is blocked. When a designated port on an MST

switch is connected to a PVST+ switch, the CIST (MST00) information on the port of the MST switch must be consistently superior (lower bridge ID, lower path cost, and so forth) to the information in all the PVST+ messages. If the port is the root, the CIST (MST00) information on the MST switch must be consistently inferior to all the PVST+ messages. If this constraint is violated, the port on the MST switch is blocked to prevent a potential bridging loop.

Recommended Action When STP is converging after a new switch or switch port is added to the

topology, this condition might happen briefly. In such cases, the port unblocks automatically. If the port remains blocked, identify the root bridge as reported in the message, and configure the 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.

There could be additional inconsistencies not shown in the message, and the port does not recover until all these are cleared. To determine which other VL4ANs have inconsistencies, disable and re-enable the port. This message appears again and specifies another VLAN with inconsistencies to be fixed. Repeat this process until all inconsistencies on all VLANs are cleared.

Error Message SPANTREE-2-PVSTSIM_OK: PVST Simulation inconsistency cleared on port [chars].

Explanation The specified interface is no longer receiving PVST BPDUs advertising information

that is inconsistent with the CIST port information. The PVST simulation inconsistency is cleared, and the interface returns to normal operation. [chars] is the port.

Recommended Action No action is required.

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.

Recommended Action Verify that the configuration and operational state of the listed interface and

that of the interface to which it is connected are in the same mode (access or trunk). If the mode is trunk, verify that both interfaces have the same encapsulation (ISL or IEEE 802.1Q). If the encapsulation types are different, use the switchport trunk encapsulation interface configuration command to make them consistent. When the encapsulation is consistent, spanning tree automatically unblocks the interface.

2-82

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Chapter 2 Message and Recovery Procedures

Error Message SPANTREE-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV on [chars]

[chars].

Explanation The listed interface received an SSTP BPDU without the VLAN ID tag. The BPDU is

discarded. The first [chars] is the port, and the second [chars] is the VLAN that received the SSTP BPDU.

Recommended Action If this message recurs, copy the message exactly as it appears on the console

or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, contact IBM technical support and provide the representative with the gathered information. For more information about the online tools and about contacting IBM, see the

Reports” section on page 1-6.

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. [dec] is the VLAN ID, the first [chars] is the port, and the second [chars] is the VLAN.

SPANTREE Messages

“Error Message Traceback

Recommended Action Verify that the configurations of the native VLAN ID is consistent on the

interfaces on each end of the IEEE 802.1Q trunk connection. When the configurations are consistent, spanning tree automatically unblocks the interfaces.

Error Message SPANTREE-2-ROOTGUARD_BLOCK: Root guard blocking port [chars] on [chars].

Explanation On the listed interface, a BPDU was received that advertises a superior spanning-tree

root bridge (lower bridge ID, lower path cost, and so forth) than that in use. The interface is put into blocking state and marked as root-guard inconsistent to prevent a suboptimal spanning-tree topology from forming. The first [chars] is the port name, and the second [chars] is the spanning-tree mode displayed in the output of the show spanning-tree privileged EXEC command.

Recommended Action Enter the show spanning-tree inconsistentports privileged EXEC command

to review the list of interfaces with root-guard inconsistencies. Find out why devices connected to the listed ports are sending BPDUs with a superior root bridge, and take action to prevent more occurrences. When the inaccurate BPDUs have been stopped, the interfaces automatically recover and resume normal operation. Make sure that it is appropriate to have root guard enabled on the interface.

OL-12191-01

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

2-83

SPANTREE Messages

Chapter 2 Message and Recovery Procedures

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. If

enabled, any BPDU received on this interface that advertises a superior spanning-tree root bridge (lower bridge ID, lower path cost, and so forth) to that already in use causes the interface to be put into the blocking state and marked as root-guard inconsistent. The first [chars] is the root-guard state (enable or disable), the second [chars] is the interface, and the third [chars] is the spanning-tree instance.

Recommended Action Verify that this is the desired configuration for the listed interface. Correct it if

it is not the desired configuration; otherwise, no action is required.

Error Message SPANTREE-2-ROOTGUARD_UNBLOCK: Root guard unblocking port [chars] on [chars].

Explanation The listed interface is no longer receiving BPDUs advertising a superior root bridge

(lower bridge ID, lower path cost, and so forth). The root-guard inconsistency is cleared for the interface, and the blocking state is removed from the interface. The first [chars] is the port name, and the second [chars] is the spanning-tree mode displayed in show spanning-tree privileged EXEC command.

Recommended Action No action is required.

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.

2-84

Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter System Message Guide

OL-12191-01

Cisco 3110, 3112 Message Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

CONTENTS

Preface

System Message Overview

How to Read System Messages

Error Message Traceback Reports

Output Interpreter

Bug Toolkit

Contacting TAC

Message and Recovery Procedures

ACLMGR Messages

BACKUP_INTERFACE Messages

BADTRANSCEIVER Messages

BSPATCH Messages

CFGMGR Messages

CLS_ACC Messages

DHCP_SNOOPING Messages

DOT1X Messages

DOT1X_SWITCH Messages

DTP Messages

DWL Messages

EC Messages

ETHCNTR Messages

EXPRESS_SETUP Messages

FRNTEND_CTRLR Messages

GBIC_SECURITY Messages

GBIC_SECURITY_CRYPT Messages

GBIC_SECURITY_UNIQUE Messages

HARDWARE Messages

HLFM Messages

HPSECURE Messages

IGMP_QUERIER Messages

IMAGEMGR Messages

IP_DEVICE_TRACKING Messages

MAC_MOVE Messages

PHY Messages

PIMSN Messages

PLATFORM Messages

PLATFORM_ENV Messages

PLATFORM_FBM Messages

PLATFORM_HCEF Message

PLATFORM_HPLM Messages

PLATFORM _IPC Messages

PLATFORM_IPv6_UCAST Message

PLATFORM_PBR Messages

PLATFORM_PM Messages

PLATFORM_RPC Messages

PLATFORM_SPAN Messages

PLATFORM_UCAST Messages

PLATFORM_VLAN Messages

PLATFORM_WCCP Messages

PM Messages

PORT_SECURITY Messages

Protocol Tunneling Messages

QOSMGR Messages

RMON Messages

SDM Messages

SPAN Messages

SPANTREE Messages