Cisco IAD2423-16FXS-RF - IAD 2423 Router, ME-2400-24TS-D, ME 3400E, ME 3400, ME 2400 System Message Manual

Cisco ME 3400E, ME 3400, and ME 2400
Ethernet Access Switches
System Message Guide

Cisco IOS Release 12.2(44)EY (ME 3400E)
Cisco IOS Release 12.2(46)SE (ME 3400 and ME 2400)

February 2009

Americas Headquarters

Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: [phone]

800 553-NETS (6387)

Fax: [phone]

Text Part Number: OL-9641-04

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 HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome
to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco
Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco
Cisco

Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step,
Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort
MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, 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
Cisco

Systems, Inc. and/or its affiliates in the United States and certain 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. (0812R)

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 ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

© 2006-2009 Cisco Systems, Inc. All rights reserved.

Store are service marks; and Access Registrar, Aironet, AsyncOS,

IMPLIED, INCLUDING, WITHOUT

Certified Internetwork Expert logo, Cisco IOS,

logo, LightStream, Linksys, MediaTone,

logo are registered trademarks of

CONTENTS

Preface v

Audience v

Purpose v

Conventions v

Related Publications vi

Obtaining Documentation and Submitting a Service Request i-vii

CHAPTER

CHAPTER

1 System Message Overview 1-1

How to Read System Messages 1-1

Error Message Traceback Reports 1-3

Output Interpreter 1-3
Bug Toolkit 1-3
Contacting TAC 1-3

2 Messages and Recovery Procedures 2-1

ACLMGR Messages 2-3

BACKUP_INTERFACE Messages 2-7

BADTRANSCEIVER Messages 2-7

BSPATCH Messages 2-8

DHCP_SNOOPING Messages 2-9

DOT1X Messages 2-12

DOT1X_SWITCH Messages 2-17

EC Messages 2-20

ETHCNTR Messages 2-24

FRNTEND_CTRLR Messages 2-25

GBIC_SECURITY Messages 2-25

GBIC_SECURITY_CRYPT Messages 2-27

GBIC_SECURITY_UNIQUE Messages 2-28

HARDWARE Messages 2-28

HCPU_PROT_MGR Messages 2-30

HLFM Messages 2-30

IDBMAN Messages 2-31

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

iii

Contents

IGMP_QUERIER Messages 2-34

MAC_LIMIT Messages 2-35

MAC_MOVE Messages 2-36

PAGP_DUAL_ACTIVE Messages 2-36

PHY Messages 2-37

PIMSN Messages 2-39

PLATFORM Messages 2-39

PLATFORM_ENV Messages 2-40

PLATFORM_PBR Messages 2-42

PLATFORM_PM Messages 2-43

PLATFORM_SPAN Messages 2-44

PLATFORM_UCAST Messages 2-45

PLATFORM_VLAN Messages 2-47

PM Messages 2-48

PORT_SECURITY Messages 2-56

QOSMGR Messages 2-57

REP Messages 2-66

RMON Messages 2-66

SPAN Messages 2-67

SPANTREE Messages 2-67

SPANTREE_FAST Messages 2-74

SPANTREE_VLAN_SW Messages 2-75

STORM_CONTROL Messages 2-75

SUPERVISOR Messages 2-76

SUPQ Messages 2-76

SW_DAI Messages 2-78

SW_VLAN Messages 2-80

TCAMMGR Messages 2-85

UDLD Messages 2-87

VQPCLIENT Messages 2-89

I

NDEX

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

iv

OL-9641-04

Audience

Preface

This guide is for the networking professional managing the Cisco Metro Ethernet (ME) 3400E,
ME

3400, and ME 2400 Ethernet Access switches, hereafter referred to as the switch. Before using this
guide, you should have experience working with the Cisco IOS software and the switch software
features.

Purpose

This guide describes only the Cisco ME 3400E, ME 3400, and ME 2400 switch-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.

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 and the
getting started guide that shipped with your switch. For software information, see the software
configuration guide and the command reference for this release. For the latest documentation updates,
see the release notes for this release.

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

element.

Interactive examples use these conventions:

• Terminal sessions and system displays are in screen font.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

v

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

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

Related Publications

Documents on this Cisco.com site provide complete information about the switches:

• Cisco ME 3400E switch:

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

• Cisco ME 3400 switch:

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

• Cisco ME 2400 switch:

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

Preface

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

• For initial configuration information, see the “Configuring the Switch with the CLI-Based Setup

Program” appendix in the hardware installation guide.

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

These are combined documents for the switches:

• Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switches System Message Guide

• Cisco ME 3400 and ME 2400 Ethernet Access Switches Getting Started Guide

• Regulatory Compliance and Safety Information for the Cisco ME 3400 and ME 2400 Ethernet

Access Switches

These documents are available for the Cisco ME 3400E switch:

• Release Notes for the Cisco ME 3400E Ethernet Access Switch

• Cisco ME 3400E Ethernet Access Switch Software Configuration Guide

• Cisco ME 3400E Ethernet Access Switch Command Reference

• Cisco ME 3400E Ethernet Access Switch Hardware Installation Guide

• Cisco ME 3400E Ethernet Access Switch Getting Started Guide

• Regulatory Compliance and Safety Information for the Cisco ME 3400E Ethernet Access Switch

These documents are available for the Cisco ME 3400 switch:

• Release Notes for the Cisco ME 3400 Ethernet Access Switch

• Cisco ME 3400 Ethernet Access Switch Software Configuration Guide

• Cisco ME 3400 Ethernet Access Switch Command Reference

• Cisco ME 3400 Ethernet Access Switch Hardware Installation Guide

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

vi

OL-9641-04

Preface

Obtaining Documentation and Submitting a Service Request

These documents are available for the Cisco ME 2400 switch:

• Release Notes for the Cisco ME 2400 Ethernet Access Switch

• Cisco ME 2400 Ethernet Access Switch Software Configuration Guide

• Cisco ME 2400 Ethernet Access Switch Command Reference

• Cisco ME 2400 Ethernet Access Switch Hardware Installation Guide

You can also refer to these documents are available for additional information:

• Cisco Small Form-Factor Pluggable Modules Installation Notes

• Cisco CWDM GBIC and CWDM SFP Installation Note

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

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

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

Ve r si o n 2.0.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

vii

Obtaining Documentation and Submitting a Service Request

Preface

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

viii

OL-9641-04

CHAP T E R

1

System Message Overview

This guide describes the Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access switches system
messages. During operation, the system software sends these messages to the console (and, optionally,
to a logging server on another system). Not all system messages indicate problems with your system.
Some messages are purely informational, whereas others can help diagnose problems with
communications lines, internal hardware, or the system software. This guide also includes error
messages that appear when the system fails.

Note For information about system messages that are not Cisco ME switch platform-specific, see the Cisco

IOS Software System Messages for Cisco IOS Release 12.2S.

This chapter contains these sections:

• How to Read System Messages, page 1-1

• Error Message Traceback Reports, page 1-3

How to Read System Messages

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:

seq no:timestamp: %facility-severity-MNEMONIC:description

By default, a switch sends the output from system messages to a logging process.

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.
Examples of facilities are: ACLMGR, DOT1X, and HARDWARE.

The messages are described in Chapter 2, “Messages and Recovery Procedures,” in alphabetical
order by facility code with the most severe (lowest number) errors described first.

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

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

OL-9641-04

Table 1-1 lists the message severity levels.

1-1

How to Read System Messages

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

• Message-text is a text string describing the condition. This portion of the message sometimes

Chapter 1 System Message Overview

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-2 lists the variable fields in messages.

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

This example shows a partial switch system message:

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)

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

1-2

OL-9641-04

Chapter 1 System Message Overview

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

Error Message Traceback Reports

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 vii for further information.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

1-3

Error Message Traceback Reports

Chapter 1 System Message Overview

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

1-4

OL-9641-04

CHAP T E R

2

Messages and Recovery Procedures

This chapter describes the Cisco ME 3400E, ME 3400, and ME 2400 switches system messages in
alphabetical order by facility. Note that some messages apply only to specific switches and are never
seen on the other switches.

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.

Note 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

• DHCP_SNOOPING Messages, page 2-9

OL-9641-04

• DOT1X Messages, page 2-12

• DOT1X_SWITCH Messages, page 2-17

• EC Messages, page 2-20

• ETHCNTR Messages, page 2-24

• FRNTEND_CTRLR Messages, page 2-25

• GBIC_SECURITY Messages, page 2-25

• GBIC_SECURITY_CRYPT Messages, page 2-27

• GBIC_SECURITY_UNIQUE Messages, page 2-28

• HARDWARE Messages, page 2-28

• HCPU_PROT_MGR Messages, page 2-30

• HLFM Messages, page 2-30

• IDBMAN Messages, page 2-31 (Cisco ME 3400E and ME 3400 switches only)

• IGMP_QUERIER Messages, page 2-34

• MAC_LIMIT Messages, page 2-35

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-1

Chapter 2 Messages and Recovery Procedures

• MAC_MOVE Messages, page 2-36

• PAGP_DUAL_ACTIVE Messages, page 2-36

• PHY Messages, page 2-37

• PIMSN Messages, page 2-39

• PLATFORM Messages, page 2-39

• PLATFORM_ENV Messages, page 2-40 (Cisco ME 3400E and ME 3400 switches only)

• PLATFORM_PBR Messages, page 2-42 (Cisco ME 3400E and ME 3400 switches only)

• PLATFORM_PM Messages, page 2-43

• PLATFORM_SPAN Messages, page 2-44

• PLATFORM_UCAST Messages, page 2-45 (Cisco ME 3400E and ME 3400 switches only)

• PLATFORM_VLAN Messages, page 2-47

• PM Messages, page 2-48

• PORT_SECURITY Messages, page 2-56

• QOSMGR Messages, page 2-57

• REP Messages, page 2-66 (Cisco ME 3400E and ME 3400 switches only)

• RMON Messages, page 2-66

• SPAN Messages, page 2-67

• SPANTREE Messages, page 2-67

• SPANTREE_FAST Messages, page 2-74

• SPANTREE_VLAN_SW Messages, page 2-75

• STORM_CONTROL Messages, page 2-75

• SUPERVISOR Messages, page 2-76

• SUPQ Messages, page 2-76

• SW_DAI Messages, page 2-78 (Cisco ME 3400E and ME 3400 switches only)

• SW_VLAN Messages, page 2-80

• TCAMMGR Messages, page 2-85

• UDLD Messages, page 2-87

• VQPCLIENT Messages, page 2-89

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-2

OL-9641-04

Chapter 2 Messages and Recovery Procedures

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 This message means that the ACL manager was unable to 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.

Recommended Action Reduce other system activity to ease memory demands.

Error Message ACLMGR-2-NOVLB: Cannot create memory block for VLAN [dec].

Explanation This message means that the ACL manager was unable to save per-VLAN information

needed for its correct operation. Some per-interface features, such as access groups or VLAN maps,
will not be configured correctly. [dec] is the VLAN number.

ACLMGR Messages

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 This message means that 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 This message means that there are too many ACLs configured for the platform-specific

ACL TCAM table to support. [dec] is the label number, and [chars] represents the layer. The first
[chars] is for Layer 3; the second is for Layer 2. If only one layer of TCAM is full, only one string
is displayed, and the other string is NULL.

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

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-3

ACLMGR Messages

Chapter 2 Messages and Recovery Procedures

Error Message ACLMGR-3-AUGMENTFAIL: Augmenting of access-map [chars] on [chars]

label [dec] failed.

Explanation This message means that the system ran out of CPU DRAM when attempting 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 This message means that 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, 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-3.

“Error

Error Message ACLMGR-3-INSERTFAIL: Insert of access-map [chars] #[dec] into [chars]
label [dec] failed.

Explanation This message means that the system ran out of CPU memory when trying to merge

sections of an access map. The first [chars] is the map name, and the second [chars] is the direction
in which the map was applied. The first [dec] is the entry number, and the second [dec] is the label
number.

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 This message means that 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, 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-3.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-4

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message ACLMGR-3-MAXRECURSION: Too many ([dec]) levels of recursion while

merging ACLs (code [dec]).

Explanation This message means that 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 This message means that 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 This message means that the ACL manager was unable to allocate a label for the

features on this interface. This means that the hardware cannot be programmed to implement the
features, and packets for this interface will be filtered in software. There is a limit of 256 labels per
direction. 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 This message means that an unrecoverable software error occurred while trying to

merge the configured output 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, 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-3.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-5

ACLMGR Messages

Chapter 2 Messages and Recovery Procedures

Error Message ACLMGR-3-PACLTTABLE: Not in truth table: IPSrcGrd [dec] PACL [dec].

Explanation This message means that an unrecoverable software error occurred while trying to

merge the configured port ACL features. The first [dec] is the action specified by IP source guard,
and the second [dec] is the action specified by the port ACL.

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, 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 ACLMGR-3-QOSTTABLE: Not in truth table: ACL [dec] in map, action [dec].

Explanation This message means that 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.

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

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

Message Traceback Reports” section on page 1-3.

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

Explanation This message means that 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 This message means that 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, 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-3.

“Error

“Error

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-6

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message ACLMGR-3-UNLOADING: Unloading [chars] label [dec] feature.

Explanation This message means that 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 message.

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.

BACKUP_INTERFACE Messages

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

Explanation This message means that 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.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-7

BSPATCH Messages

BSPATCH Messages

This section contains boot loader patch messages.

Error Message BSPATCH-1-RELOAD: System will reboot to activate newly patched Boot
Loader.

Explanation This message means that 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, 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-3.

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

Chapter 2 Messages and Recovery Procedures

Explanation This message means that 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, 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-3.

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

Explanation This message means that 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, 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-3.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-8

OL-9641-04

Chapter 2 Messages and Recovery Procedures

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 This message means that 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, 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-3.

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

DHCP_SNOOPING Messages

Explanation This message means that the DHCP snooping binding transfer process failed because of

the specified reason for failure. [chars] is the reason for failure.

Recommended Action No action is required.

Error Message DHCP_SNOOPING-4-AGENT_OPERATION_FAILED_N: DHCP snooping binding

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

Explanation This message means that 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.

Error Message DHCP_SNOOPING-4-DHCP_SNOOPING_ERRDISABLE_WARNING: DHCP Snooping

received [dec] DHCP packets on interface [chars].

Explanation This message means that 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.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-9

DHCP_SNOOPING Messages

Error Message DHCP_SNOOPING-4-DHCP_SNOOPING_PVLAN_WARNING: DHCP Snooping

configuration may not take effect on secondary vlan [dec]. [chars]

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

Note This message applies only to the Cisco ME 3400E and ME 3400 switches.

Chapter 2 Messages and Recovery Procedures

Explanation This message means that if private VLANs are configured, the DHCP Snooping

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

Recommended Action No action is required.

Explanation This message means that 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.

Error Message DHCP_SNOOPING-4-IP_SOURCE_BINDING_NON_EXISTING_VLAN_WARNING: IP

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

Note This message applies only to the Cisco ME 3400E and ME 3400 switches.

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-NTP_NOT_RUNNING: NTP is not running; reloaded binding

lease expiration times are incorrect.

Explanation This message means that 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.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-10

OL-9641-04

Chapter 2 Messages and Recovery Procedures

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 This message means that the CPU is receiving DHCP packets a higher rate than the

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

Recommended Action No action is required.

Error Message DHCP_SNOOPING-4-STANDBY_AGENT_OPERATION_FAILED: DHCP snooping binding

transfer failed on the Standby Supervisor. [chars].

Explanation This message means that 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.

DHCP_SNOOPING Messages

Explanation This message means that 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 This message means that the specified number of bindings were ignored when the

switch read the database file. The bindings from the database file have MAC address and VLAN
information that a configured DHCP snooping binding already uses.

Recommended Action No action is required.

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

bindings ignored.

Explanation This message means that 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 This message means that 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.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-11

DOT1X Messages

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

Explanation This message means that 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 This message means that the specified number of bindings were ignored when the

switch read the database file because 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

Chapter 2 Messages and Recovery Procedures

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 This message means that the system memory is not sufficient to perform the 802.1x

authentication.

Recommended Action Reduce other system activity to reduce memory demands.

Error Message DOT1X-4-MSG_ERR: Unknown message event received.

Explanation This message means that the 802.1x process received an unknown message event.

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

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

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

Explanation This message means that the system failed to create the 802.1x process.

Recommended Action Restart the 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 This message means that the 802.1x process cannot operate because of an internal

system error.

Recommended Action No action is required.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-12

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message DOT1X-5-ERR_CHANNELLING: Dot1x can not be enabled on Channelling

ports.

Explanation This message means that 802.1x could not be enabled on the channeling port. Trying to

set 802.1x port-control to auto or force-unauthorized (force_unauth) mode on a channeling port,
which is not allowed, caused this condition.

Recommended Action Disable channeling on the interface, and then enable 802.1x.

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

Explanation This message means that 802.1x could not be enabled on the dynamic mode port. Trying

to set 802.1x port-control to auto or force-unauthorized (force_unauth) mode on a dynamic mode
port, which is not allowed, caused this condition.

Recommended Action Disable dynamic mode on the interface, and then enable 802.1x.

Error Message DOT1X-5-ERR_DYNAMIC_VLAN: Dot1x can not be enabled on dynamic VLAN

ports.

DOT1X Messages

Explanation This message means that 802.1x could not be enabled on the dynamic VLAN port.

Trying to set 802.1x port-control to auto or force-unauthorized (force_unauth) mode on a dynamic
VLAN port, which is not allowed, caused this condition.

Recommended Action Disable dynamic VLAN configuration on the interface, and then enable

802.1x.

Error Message DOT1X-5-ERR_INVALID_TUNNEL_MEDIUM_TYPE: Got an invalid value [chars]
for TUNNEL_MEDIUM_TYPE [chars].

Explanation This message means that the provided tunnel medium is either unsupported or invalid.

[chars] is the text received from the RADIUS server.

Recommended Action Change the value to a valid tunnel medium.

Error Message DOT1X-5-ERR_INVALID_TUNNEL_TYPE: Got an invalid value of [chars] for

TUNNEL_TYPE [chars].

Explanation This message means that the provided tunnel type is either unsupported or invalid.

[chars] is the text received from the RADIUS server.

Recommended Action Change the value to a valid tunnel type.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-13

DOT1X Messages

Chapter 2 Messages and Recovery Procedures

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

tunnelling enabled ports.

Explanation This message means that 802.1x could not be enabled on the protocol-tunneling-enabled

port. Trying to set 802.1x port-control to auto or force-unauthorized (force_unauth) mode on a
protocol-tunneling-enabled port, which is not allowed, caused this condition.

Recommended Action Change the access VLAN on the interface, and then enable 802.1x.

Error Message DOT1X-5-ERR_PVLAN_TRUNK:Dot1x can not be enabled on private VLAN trunk

ports

Explanation This message means that 802.1x could not be enabled on private VLAN ports on which

trunking is enabled.

Recommended Action No action is required.

Error Message DOT1X-5-ERR_RSPAN_VLAN: Dot1x can not be enabled on ports configured

in Remote SPAN vlan.

Explanation This message means that 802.1x could not be enabled on the remote SPAN VLAN port.

Trying to set 802.1x port-control to auto or force-unauthorized (force_unauth) mode on a port that
is in a remote SPAN VLAN, which is not allowed, caused this condition.

Recommended Action Disable remote SPAN on the VLAN, and then enable 802.1x.

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

configured as a SPAN Dest port.

Explanation This message means that 802.1x cannot be enabled on a port that is a SPAN destination

port because these features are mutually exclusive. [chars] is the port.

Recommended Action Remove the SPAN destination port from the SPAN session before

reconfiguring 802.1x on the port.

Error Message DOT1X-5-ERR_TRUNK: Dot1x can not be enabled on Trunk port.

Explanation This message means that 802.1x could not be enabled on the trunk port. Trying to set

802.1x port control to auto or force-unauthorized (force_unauth) mode on a trunk port, which is not
allowed, caused this condition.

Recommended Action Disable trunking on the interface, and then enable 802.1x.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-14

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message DOT1X-5-ERR_TUNNEL: Dot1x can not be enabled on 802.1q tunnelling

enabled ports.

Explanation This message means that 802.1x could not be enabled on the 802.1Q

tunneling-enabled-port. Trying to set 802.1x port-control to auto or force-unauthorized
(force_unauth) mode on a 802.1Q-tunnel-enabled port, which is not allowed, caused this condition.

Recommended Action Disable 802.1Q tunneling on the interface, and then enable 802.1x.

Error Message DOT1X-5-ERR_VLAN_INTERNAL: The VLAN [dec] is being used internally and

cannot be assigned for use on the Dot1x port [chars] Vlan.

Explanation This message means that the VLAN is used internally and cannot be assigned again for

use on this port. [dec] is the VLAN ID. [chars] is the port number.

Recommended Action Update the configuration to not use this VLAN.

Error Message DOT1X-5-ERR_VLAN_INVALID: The VLAN [dec] is invalid and cannot be

assigned for use on the 802.1X port [chars] Vlan.

DOT1X Messages

Explanation This message means that the specified VLAN is out of range and cannot be assigned for

use on this port. [dec] is the VLAN ID. [chars] is the port number.

Recommended Action Update the configuration to use a valid VLAN.

Error Message DOT1X-5-ERR_VLAN_NOT_ASSIGNABLE: RADIUS tried to assign a VLAN to

dot1x port [chars] whose VLAN cannot be assigned.

Explanation This message means that the RADIUS server tried to assign a VLAN to a supplicant on

a port whose VLAN cannot be changed, such as a routed port. [chars] is the port number.

Recommended Action Change the specified port to a Layer 2 port by using the switchport interface

configuration command.

Error Message DOT1X-5-ERR_VLAN_NOT_FOUND: Attempt to assign non-existent [chars]
VLAN [chars] to dot1x port [chars].

Explanation This message means that an attempt to assign a VLAN to a supplicant on a port fails

because the VLAN was not found in the VTP database. [chars] is the port number.

Recommended Action Make sure that the VLAN exists, or use another VLAN.

Error Message DOT1X-5-ERR_VLAN_RESERVED: The VLAN [dec] is a reserved vlan and cannot

be assigned for use on the Dot1x port [chars] Vlan.

Explanation This message means that the VLAN specified is a reserved VLAN and cannot be

assigned for use on this port. [dec] is the VLAN ID. [chars] is the port number.

Recommended Action Update the configuration to not use this VLAN.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-15

DOT1X Messages

Chapter 2 Messages and Recovery Procedures

Error Message DOT1X-5-ERR_VLAN_RSPAN_CONFIGURED: VLAN [dec] is configured as a

Remote SPAN VLAN, which has Dot1x enabled interface(s) configured. Please disable
Dot1x on all ports in this VLAN or do not enable RSPAN on this VLAN.

Explanation This message means that remote SPAN should not be enabled on a VLAN in which ports

are configured with 802.1x enabled. [dec] is the VLAN ID.

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

on all the ports in this VLAN.

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 (zero, broadcast or multicast
mac address [chars] is trying to authenticate).

Explanation This message means that authentication was attempted for a zero, broadcast, or

multicast MAC address using 802.1x. 802.1x authentication is allowed only for a valid nonzero,
nonbroadcast, or nonmulticast source MAC address.

Recommended Action Connect a 802.1x-supported host to the 802.1x-enabled port.

Error Message DDOT1X-5-NOT_DOT1X_CAPABLE: Dot1x disabled on interface [chars]

because it is not an Ethernet interface.

Explanation This message means that you can enable 802.1x authentication only on Ethernet

interfaces. [chars] is the interface.

Recommended Action Enable 802.1x authentication only on Ethernet interfaces.

Error Message DOT1X-5-SECURITY_VIOLATION: Security violation on the interface

[chars], new MAC address [enet] is seen.

Explanation A host on the specified interface is trying to access the network or to authenticate in a

host mode that does not support the number of hosts attached to the interface. This is a security
violation, and the port is put in the error-disabled state.

Recommended Action Ensure that the interface is configured to support the number of attached hosts.

Enter the shutdown interface configuration command and then the no shutdown interface
configuration command to restart the port.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-16

OL-9641-04

Chapter 2 Messages and Recovery Procedures

DOT1X_SWITCH Messages

This section contains the DOT1X_SWITCH Messages.

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]

DOT1X_SWITCH Messages

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]

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.

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]

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.

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

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.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-17

DOT1X_SWITCH Messages

Error Message DOT1X_SWITCH-5-ERR_SEC_VLAN_INVALID: Attempt to assign secondary VLAN

[dec] to non-PVLAN host 802.1x port [chars]

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

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]

Chapter 2 Messages and Recovery Procedures

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.

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.

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.

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.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-18

OL-9641-04

Chapter 2 Messages and Recovery Procedures

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_PROMISC_PORT: Attempt to assign VLAN [dec] to

promiscuous 802.1x port [chars]

DOT1X_SWITCH Messages

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.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-19

EC Messages

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

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

Chapter 2 Messages and Recovery Procedures

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

802.1x on all the ports in this VLAN.

Explanation This message means that either the LACP or the PAgP EtherChannel could not obtain

the memory it needed to initialize the required data structures. [chars] is the 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, 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 EC-5-BUNDLE: Interface [chars] joined port-channel [chars].

Explanation This message means that the listed interface joined the specified EtherChannel. The first

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

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

Recommended Action No action is required.

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

allocate aggregator for group [dec].

Explanation This message means that 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.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-20

OL-9641-04

Chapter 2 Messages and Recovery Procedures

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

Explanation This message means that the interface has different interface attributes than other ports

in the EtherChannel. For the interface to join the bundle (EtherChannel), change the interface
attributes to match the EtherChannel attributes. The first [chars] is the interface to be bundled, the
second [chars] is the physical interface (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.

EC Messages

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
Catalyst 3750 switch, [dec] is the channel group number, and the last [chars] is the reason.

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

port.

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

Explanation This message means that 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.

Recommended Action No action is required.

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.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-21

EC Messages

Chapter 2 Messages and Recovery Procedures

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 This message means that 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 This message means that 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 This message means that 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 This message means that 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.

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

Note This message applies only to the Cisco ME 3400E and ME 3400 switches.

Explanation This message means that 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.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-22

OL-9641-04

Chapter 2 Messages and Recovery Procedures

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

Explanation This message means that the EtherChannel mode cannot be set because LACP is not

included in the software image.

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 This message means that PAgP is not included in the Cisco IOS image and that 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 This message means that 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.

EC Messages

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

to activate the aggregation port.

Error Message EC-5-STAYDOWN: [chars] will remain down as its port-channel [chars] is
admin-down.

Explanation This message means that 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 This message means that 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.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-23

ETHCNTR Messages

Chapter 2 Messages and Recovery Procedures

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

Explanation This message means that the listed interface left the specified EtherChannel. The first

[chars] is the physical interface, 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 This message means that one of the interfaces cannot join the EtherChannel because it

is configured for PortFast, as a VLAN Membership Policy Server (VMPS), for 802.1x, 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.

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. Incorrect switch behavior results.

Error Message ETHCNTR-3-HALF_DUX_COLLISION_EXCEED_THRESHOLD: Collision at [chars]
exceed threshold. Consider as loop-back.

Explanation This message means that 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.

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

CSCea46385 for more

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-24

OL-9641-04

Chapter 2 Messages and Recovery Procedures

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

Shutting down [chars].

Explanation This message means that there are too many VLANs and routed ports configured.

[chars] is the short interface name, such as Gi0/1, 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.

FRNTEND_CTRLR Messages

This section contains the front-end controller messages.

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

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

switch software.

FRNTEND_CTRLR Messages

Recommended Action Try reloading the switch. If this does not resolve the issue, this might be a

hardware problem. Contact the Cisco technical support representative.

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

Explanation This message means that 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 by resetting the switch, contact

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

GBIC_SECURITY Messages

This section contains the Cisco Gigabit Interface Converter (GBIC) and small form-factor pluggable
(SFP) module security messages. The GBIC and SFP modules have a serial EEPROM that contains the
serial number, security code, and cyclic redundancy check (CRC). When the module is inserted into the
switch, the software reads the EEPROM to recompute the security code and CRC. The software
generates an error message if the CRC is invalid or if the recomputed security code does not match the
one stored in the EEPROM.

Note The switch supports SFP modules and does not support GBIC modules. Although the error message text

refers to GBIC interfaces and modules, the messages from the switch actually refer to the SFP module
interfaces and modules.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-25

GBIC_SECURITY Messages

Error Message GBIC_SECURITY-4-EEPROM_CRC_ERR: EEPROM checksum error for GBIC in

[chars].

Error Message GBIC_SECURITY-4-EEPROM_READ_ERR: Error in reading GBIC serial ID in
[chars].

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

Chapter 2 Messages and Recovery Procedures

Explanation This message means that 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.

Explanation This message means that 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.

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

the GBIC is inserted.

Recommended Action Remove the GBIC from the port.

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

interface [chars].

Explanation This message means that 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 Cisco, see the

“Error Message

Traceback Reports” section on page 1-3.

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

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

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

Recommended Action No action is required.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-26

OL-9641-04

Chapter 2 Messages and Recovery Procedures

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

from [chars]

Explanation The online insertion and removal (OIR) facility detected the removal of a transceiver

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

Recommended Action No action is required.

GBIC_SECURITY_CRYPT Messages

This section contains the Cisco GBIC module and SFP module security messages. The switch recognizes
the module as a Cisco module but identifies another problem with it.

Note The switch supports SFP modules and does not support GBIC modules. Although the error message text

refers to GBIC interfaces and modules, the messages from the switch actually refer to the SFP module
interfaces and modules.

GBIC_SECURITY_CRYPT Messages

Error Message GBIC_SECURITY_CRYPT-4-ID_MISMATCH: Identification check failed for

GBIC in port [chars]

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.

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

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

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

but it does not have valid 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.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-27

GBIC_SECURITY_UNIQUE Messages

GBIC_SECURITY_UNIQUE Messages

This section contains the Cisco GBIC module and SFP module security messages that identify whether
the module is unique.

Note The switch supports SFP modules and does not support GBIC modules. Although the error message text

refers to GBIC interfaces and modules, the messages from the switch actually refer to the SFP module
interfaces and modules.

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

Explanation This message means that the SFP module was identified as a Cisco 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 SPF module, and the second [dec]/[dec] is the interface of the existing
module.

Chapter 2 Messages and Recovery Procedures

Recommended Action Cisco 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.

Explanation This message means that 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.

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, contact Cisco technical support and provide
the representative with the gathered information. For more information about the online tools and
about contacting Cisco, see the

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

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-28

OL-9641-04

Chapter 2 Messages and Recovery Procedures

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

Explanation This message means that 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, 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-3.

Error Message HARDWARE-3-INDEX_ERROR: Index value [dec] is invalid.

Explanation This message means that 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, 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-3.

HARDWARE Messages

“Error

“Error

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

Explanation This message means that 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, 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-3.

Error Message HARDWARE-3-PORTNUM_ERROR: port number [dec] is invalid.

Explanation This message means that 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, 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-3.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-29

HCPU_PROT_MGR Messages

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

Explanation This message means that the statistics ID used is out of range. The statistics supported

by the port ASIC are identified by an ID. [dec] is the statistics ID.

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

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

Message Traceback Reports” section on page 1-3.

HCPU_PROT_MGR Messages

This section contains the CPU protection manager messages.

Error Message HCPU_PROT_MGR-4-PROGRAM_POLICER_FAIL: Could not program policer for
port.

Chapter 2 Messages and Recovery Procedures

“Error

Explanation This message means that a hardware error could have 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, 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

HLFM Messages

This section contains messages from the local forwarding manager.

Error Message HLFM-3-MACFREE_ERROR: MAC address [enet], vlan [dec] is still
referenced; cannot free.

Explanation This message means that 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, 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-3.

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

“Error

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-30

OL-9641-04

Chapter 2 Messages and Recovery Procedures

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

mac-address [enet], vlan [dec].

Explanation This message means that the IP address and MAC address tables are out of sync.

[IP_address] is the IP address, [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, 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-3.

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 This message means that 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.

IDBMAN Messages

“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, 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-3.

IDBMAN Messages

This section contains the interface description block manager (IDBMAN) messages.

Note These messages apply only to the Cisco ME 3400E and ME 3400 switches.

Error Message IDBMAN-3-AGGPORTMISMATCH: [chars]: [chars]([dec] / [dec]) does not

match internal slot/port state [chars]([dec] / [dec]).

Explanation This message means that there is an internal error that caused the software to use an

invalid aggregate port. The first [chars] is the name of the function where the error occurred. The
second and third [chars] are the port-channel names, and the ([dec] / [dec]) are the slot and port
numbers (slot/port).

“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, 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-3.

OL-9641-04

“Error

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-31

IDBMAN Messages

Chapter 2 Messages and Recovery Procedures

Error Message IDBMAN-3-DELETEDAGGPORT: [chars]([dec] / [dec]) Group [dec] has been

deleted, but is being reused.

Explanation This message means that there is an internal error that caused a deleted interface to be

reused for a new aggregate port. [chars] is the port-channel name, and the ([dec] / [dec]) are the slot
and port numbers (slot/port). The last [dec] is the channel-group 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, 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-3.

Error Message IDBMAN-3-INVALIDAGGPORTBANDWIDTH: [chars]([dec] / [dec]) has an
invalid bandwidth value of [dec].

Explanation This message means that there is an internal error that caused an invalid bandwidth to

be used for an aggregate port. [chars] is the port-channel name. The ([dec] / [dec]) are the slot and
port numbers (slot/port). The last [dec] is the bandwidth.

“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, 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-3.

Error Message IDBMAN-3-INVALIDPORT: [chars]: trying to use invalid port number [dec]
( Max [dec] ).

Explanation This message means that there is an internal error that caused the software to use an

invalid port number. [chars] is the interface name. The first [dec] is the port number that is invalid,
and the second [dec] is the maximum allowed value for a port number.

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

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

Error Message IDBMAN-3-INVALIDVLAN: [chars]: trying to use invalid Vlan [dec].

Explanation This message means that there is an internal error that caused the software to use an

invalid VLAN. [chars] is the interface name, and [dec] is the VLAN number that is invalid.

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

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-32

OL-9641-04

Chapter 2 Messages and Recovery Procedures

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

Error Message IDBMAN-3-NOTANAGGPORT: [chars]( [dec] / [dec] ) is not an aggregate
port.

Explanation This message means that there is an internal error that caused an interface that is not an

aggregate port to be used for aggregate port operations. [chars] is the interface name, and ([dec] /
[dec]) are the slot and port number (slot/port).

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

Research and attempt to resolve the error by using the Output Interpreter. 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-3.

IDBMAN Messages

“Error

“Error

Error Message IDBMAN-3-PORTNOTINAGGPORT: [chars]([dec] / [dec]) is not present in
Aggport [chars [([dec] / [dec]).

Explanation This message means that an internal error has been detected. A port that was supposed

to be in an aggregate port was not. The first [chars] is the interface name, and the second [chars] is
the port-channel name. The ([dec] / [dec]) are the slot and port numbers (slot/port).

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

Research and attempt to resolve the error by using the Output Interpreter. 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-3.

Error Message IDBMAN-3-VLANNOTSET: [chars]: Vlan [dec] not set since it already has
Vlan [dec].

Explanation This message means that there is an internal error that caused an interface to not have

its VLAN set to the requested value. [chars] is the interface name. The first [dec] is the new VLAN
number, and the second [dec] is the currently assigned VLAN 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, 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-3.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-33

IGMP_QUERIER Messages

Error Message IDBMAN-4-ACTIVEPORTSINAGGPORT: [chars]( [dec] / [dec] ) has [dec]

active ports, but is being removed.

Explanation This message means that there is an internal error that caused an aggregate port with

active ports to be removed. [chars] is the port-channel name, and the ([dec] / [dec]) are the slot and
port number (slot/port). The last [dec] is the number of currently active ports.

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

Message Traceback Reports” section on page 1-3.

IGMP_QUERIER Messages

This section contains the IGMP querier messages.

Chapter 2 Messages and Recovery Procedures

“Error

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 This message means that you must specify an IP address for the IGMP querier at either

the global or per-VLAN level. [dec] is the VLAN number.

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 This message means that PIM was detected on the SVI. Do not enable the IGMP querier

when PIM is enabled on the SVI. [dec] is the VLAN number.

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 This message means that IGMP snooping was detected in a disabled state on this

VLAN. The IGMP querier function should not be operationally enabled when IGMP snooping is
disabled. [dec] is the VLAN numbers.

Recommended Action Confirm that IGMP snooping is enabled both globally and on the VLAN.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-34

OL-9641-04

Chapter 2 Messages and Recovery Procedures

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 This message means that Protocol-Independent Multicast (PIM) is disabled on the

switch virtual interface (SVI), and the IGMP querier function is now enabled. [dec] is the VLAN
number.

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 This message means that IGMP snooping was enabled. As a result, the IGMP querier

function is now enabled. [dec] is the VLAN number.

Recommended Action No action is required.

MAC_LIMIT Messages

MAC_LIMIT Messages

This section contains the MAC_LIMIT messages, which describe the entries in the MAC address table.

Error Message MAC_LIMIT-4-DROP: Vlan [dec] with Configured limit = [dec] has
currently [dec] Entries.

Explanation This message means that the number of MAC address table entries for a VLAN is less

than or equal to the maximum number allowed. The first [dec] is the VLAN ID, the second [dec] is
the maximum number of MAC address entries, and the third [dec] is the number of entries in the
MAC address table.

Recommended Action Your system administrator configures an action.

Error Message MAC_LIMIT-4-ENFORCE: Enforcing limit on Vlan [dec] with Configured

limit = [dec].

Explanation This message means that the number of MAC address entries for the VLAN exceeds the

maximum number allowed and that the configured action is to limit the number of entries to the
maximum allowed. The first [dec] is the VLAN ID, and the second [dec] is the maximum number
of MAC address entries.

Recommended Action Your system administrator configures an action.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-35

MAC_MOVE Messages

Error Message MAC_LIMIT-4-EXCEED: Vlan [dec] with Configured limit = [dec] has

currently [dec] Entries.

Explanation This message means that the number of MAC address entries for a VLAN exceeds the

maximum number allowed. The first [dec] is the VLAN ID, the second [dec] is the maximum
number of MAC address entries, and the third [dec] is the number of entries in the MAC address
table.

Recommended Action Your system administrator configures an action.

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 This message means that 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.

Chapter 2 Messages and Recovery Procedures

Recommended Action Check your network for loops.

PAGP_DUAL_ACTIVE Messages

This section contains Port Aggregation Protocol (PAgP) dual-active detection messages.

Error Message %PAGP_DUAL_ACTIVE-3-OBJECT_CREATE_FAILED: Unable to create [chars]

Explanation The switch cannot create the specified managed object. [chars] is the object name.

Recommended Action No action is required.

Error Message %PAGP_DUAL_ACTIVE-3-RECOVERY_TRIGGER: PAgP running on [chars]

informing virtual switches of dual-active: new active id [enet], old id [enet]

Explanation PAgP received a new active ID on the specified interface, which means that all virtual

switches are in a dual-active scenario. The interface is informing virtual switches of this, which
causes one switch to go into recovery mode. [chars] is the interface. The first [enet] is the new
active ID. The second [enet] is the ID that it replaces.

Recommended Action No action is required.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-36

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message %PAGP_DUAL_ACTIVE-3-REGISTRY_ADD_ERR: Failure in adding to [chars]

registry

Explanation The switch could not add a function to the registry. [chars] is the registry name.

Recommended Action No action is required.

PHY Messages

This section contains the PHY messages.

Error Message PHY-4-BADTRANSCEIVER: An inappropriate transceiver has been inserted
in interface [chars].

Explanation This message means that a transceiver that should not be used is in the specified

interface.

Recommended Action Remove the transceiver. If the transceiver is a Cisco device, contact your Cisco

technical support representative.

PHY Messages

Error Message PHY-4-CHECK_SUM_FAILED: SFP EEPROM data check sum failed for SFP

interface [chars].

Explanation This message means that 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 This message means that the system detected excessive frame check sequence (FCS),

data word, or idle word errors on the specified interface. [chars] is the interface.

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.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-37

PHY Messages

Chapter 2 Messages 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, 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-3.

Error Message PHY-4-SFP_NOT_SUPPORTED: The SFP in [chars] is not supported

Explanation This message means that this small form-factor pluggable (SFP) module type is not

supported on this switch. [chars] is the interface.

“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, 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-3.

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, 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-3.

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

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, 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-5.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-38

OL-9641-04

Chapter 2 Messages 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 This message means that 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 This message means that 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 This message means that 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, 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-3.

“Error

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

Note This message applies only to the Cisco ME 3400E and ME 3400 switches.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-39

PLATFORM_ENV Messages

Explanation This message means that there are too many VLANs and routed ports. [chars] is the

short interface name, such as Gi0/1, or the VLAN name, such as VLAN0002.

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

preserve configurations and connections across reboots, save the configuration.

PLATFORM_ENV Messages

This section contains platform-specific environmental messages.

Error Message PLATFORM_ENV-1-DUAL_PWR: Faulty internal power supply [chars]
detected.

Note This message applies only to the Cisco ME 3400E and ME 3400 switches.

Explanation A faulty internal power supply was detected in one of the two power supplies on the

switch. [chars] is the power supply name.

Chapter 2 Messages and Recovery Procedures

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

Error Message PLATFORM_ENV-1-EXTERNAL_ALARM_CONTACT_ASSERT: Alarm asserted: %s.

Note This message applies only to the Cisco ME 3400E switch.

Explanation An error condition was detected on an external alarm contact.

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

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-40

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message PLATFORM_ENV-1-EXTERNAL_ALARM_CONTACT_CLEAR: Alarm cleared: %s.

Note This message applies only to the Cisco ME 3400E switch.

Explanation An error condition was cleared on external alarm contact.

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

Message Traceback Reports” section on page 1-3.

Error Message PLATFORM_ENV-1-FRU_PS_FAN_FAILED: Faulty PS%s fan detected.

Note This message applies only to the Cisco ME 3400E switch.

PLATFORM_ENV Messages

“Error

Explanation A power-supply fan failure was detected.

Recommended Action Replace the faulty fan.

Error Message PLATFORM_ENV-1-FRU_PS_FAN_OK: PS%s fan ok.

Note This message applies only to the Cisco ME 3400E switch.

Explanation The power-supply fan module is working correctly.

Recommended Action No action is required.

Error Message PLATFORM_ENV-1-FRU_PS_OIR: FRU Power Supply %s.

Note This message applies only to the Cisco ME 3400E switch.

Explanation A power-supply moduel was inserted or removed.

Recommended Action No action is required.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-41

PLATFORM_PBR Messages

PLATFORM_PBR Messages

This section contains policy based routing (PBR) messages.

Note These messages apply only to the Cisco ME 3400E and ME 3400 switches.

Error Message PLATFORM_PBR-2-NO_RMAP: Cannot create PBR data structures for

route-map [chars].

Explanation This message means that 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.

Chapter 2 Messages and Recovery Procedures

Explanation This message means that 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].

Explanation This message means that 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.

Error Message PLATFORM_PBR-3-UNSUPPORTED_RMAP: Route-map [chars] not supported for
Policy-Based Routing.

Explanation This message means that 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.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-42

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message PLATFORM_PBR-4-CPU_SUPPORTED_ACTION: Set action in sequence [dec] of

route-map [chars] supported by forwarding to CPU.

Explanation This message means that 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 This message means that 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.

PLATFORM_PM Messages

Error Message PLATFORM_PBR-4-SDM_MISMATCH: [chars] requires sdm template routing.

Explanation This message means that the routing template is not enabled. [chars] is the text string

PBR.

Recommended Action Modify the SDM template to enable the routing template. Use the sdm prefer

routing configuration command, and then reload the switch by using the reload privileged EXEC
command.

PLATFORM_PM Messages

This section contains platform port manager (PM) messages.

Error Message PLATFORM_PM-3-IFCOUNTERROR: Unit number [dec] of interface [chars] is
more than max allowed value of [dec].

Explanation This message means that 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, 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-3.

“Error

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-43

PLATFORM_SPAN Messages

Error Message PLATFORM_PM-3-INTVLANINUSE: internal vlan-id [dec] allocated for

interface [chars] is still in use.

Error Message PLATFORM_PM-3-NOINTVLAN: internal vlan of interface [chars] is not
active for vlan-id [dec].

Chapter 2 Messages and Recovery Procedures

Explanation This message means that 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, 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-3.

Explanation This message means that internal vlan_data is not active for the given VLAN ID. [chars]

is the interface, 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, 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-3.

“Error

“Error

PLATFORM_SPAN Messages

This section contains the Switched Port Analyzer (SPAN) messages.

Error Message PLATFORM_SPAN-3-PACKET_DROP: Decreases egress SPAN rate.

Explanation This message means that 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 Cisco, see the

Traceback Reports” section on page 1-3.

“Error Message

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-44

OL-9641-04

Chapter 2 Messages and Recovery Procedures

PLATFORM_UCAST Messages

This section contains platform unicast routing messages.

Note These messages apply only to the Cisco ME 3400E and ME 3400 switches.

Error Message PLATFORM_UCAST-3-ADJ: [chars].

Explanation This message means that the adjacency module for unicast routing encountered an error.

[chars] describes the error.

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

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

Message Traceback Reports” section on page 1-3.

PLATFORM_UCAST Messages

“Error

Error Message PLATFORM_UCAST-3-ARP: [chars].

Explanation This message means that 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, 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-3.

Error Message PLATFORM_UCAST-3-CEF: [chars].

Explanation This message means that 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, 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-3.

“Error

“Error

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-45

PLATFORM_UCAST Messages

Error Message PLATFORM_UCAST-3-DYNAMIC: [chars].

Error Message PLATFORM_UCAST-3-ERROR: [chars].

Chapter 2 Messages and Recovery Procedures

Explanation This message means that 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, 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-3.

Explanation This message means that 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.

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

Message Traceback Reports” section on page 1-3.

“Error

“Error

Error Message PLATFORM_UCAST-3-HSRP: [chars].

Explanation This message means that 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, 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-3.

Error Message PLATFORM_UCAST-3-INTERFACE: [chars].

Explanation This message means that 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, 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-3.

“Error

“Error

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-46

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message PLATFORM_UCAST-3-RPC: [chars].

Explanation This message means that 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, 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-3.

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 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 ip unicast failed route privileged EXEC command lists the failed
prefixes.

PLATFORM_VLAN Messages

“Error

Recommended Action No action is required.

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 This message means that 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, 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-3.

Error Message PLATFORM_VLAN-3-MVID_ERROR: Mapped Vlan ID value [dec] associated with
vlan-id [dec] is invalid.

“Error

Explanation This message means that 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, open a case with the TAC, or

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-47

PM Messages

Chapter 2 Messages and Recovery Procedures

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

Error Message PLATFORM_VLAN-3-UNLOCK_FAIL: Failed to unlock vlan-id [dec],
associated mapped vlan id value [dec].

Explanation This message means that the switch failed to unlock a VLAN ID. The most likely cause

is that the VLAN is already unlocked. The first [dec] is the VLAN ID, and the second [dec] is the
MVID.

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

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

Message Traceback Reports” section on page 1-3.

“Error

“Error

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.

Error Message PM-2-NOMEM: Not enough memory available for [chars].

Explanation This message means that 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.

Explanation This message means that the port manager subsystem could not obtain the memory it

needed to initialize the specified operation. [chars] is the port manager operation.

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

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-48

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message PM-3-INTERNALERROR: Port Manager Internal Software Error ([chars]:

[chars]: [dec]: [chars]).

Explanation This message means that an internal software error occurred in the port manager. The

parameters identify the problem for Cisco 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, 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-3.

Error Message PM-4-BAD_APP_ID: an invalid application id ([dec]) was detected.

Explanation This message means that the port manager detected an invalid request. [dec] is the

application ID.

PM Messages

“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. 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 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 PM-4-BAD_APP_REQ: an invalid [chars] request by the ’[chars]’
application was detected.

Explanation This message means that the port manager detected an invalid request. The first [chars]

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

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, 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 PM-4-BAD_CARD_COOKIE: an invalid card cookie was detected.

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

Explanation This message means that 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, open a case

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-49

PM Messages

Chapter 2 Messages and Recovery Procedures

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 PM-4-BAD_CARD_SLOT: an invalid card slot ([dec]) was detected.

Explanation This message means that 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, 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 PM-4-BAD_COOKIE: [chars] was detected.

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

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

Explanation This message means that 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, 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 PM-4-BAD_HA_ENTRY_EVENT: Invalid Host access entry event ([dec]) is
received.

Explanation This message means that an invalid host access entry event was received; the host access

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

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, 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-3.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-50

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message PM-4-BAD_PORT_COOKIE: an invalid port cookie was detected.

Explanation This message means that 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, 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 PM-4-BAD_PORT_NUMBER: an invalid port number ([dec]) was detected.

Explanation This message means that 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, 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

PM Messages

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

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

Error Message PM-4-BAD_VLAN_COOKIE: an invalid vlan cookie was detected.

Explanation This message means that 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, 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 PM-4-BAD_VLAN_ID: an invalid vlan id ([dec]) was detected.

Explanation This message means that the port manager detected an invalid request. [dec] is the

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

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

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-51

PM Messages

Chapter 2 Messages and Recovery Procedures

Error Message PM-4-ERR_DISABLE: [chars] error detected on [chars], putting [chars]

in err-disable state.

Explanation This message means that the port manager detected a misconfiguration or misbehavior

and placed the interface in an error-disabled state. A recovery is attempted after the configured retry
time (the default is 5 minutes). [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.

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

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

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

Error Message PM-4-ERR_RECOVER: Attempting to recover from [chars] err-disable state
on [chars].

Explanation This message means that the port manager is attempting to bring the interface up after

taking it down to the error-disabled state. The first [chars] is the error, and the second [chars] is the
affected interface.

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

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-52

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message PM-4-ERR_RECOVER_VP: Attempting to recover from [chars] err-disable

state on [chars], vlan [dec].

Explanation The port manager is attempting to bring up the virtual port after taking it down to the

error-disabled state. The first [chars] is the error, the second [chars] is the virtual port, and [dec] is
the VLAN ID.

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

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

Message Traceback Reports” section on page 1-3.

Error Message PM-4-EXT_VLAN_INUSE: VLAN [dec] currently in use by [chars].

Explanation This message means that the port manager failed to allocate the VLAN for external use

because the VLAN is being used by another feature. [dec] is the VLAN that is being used, and
[chars] is the feature that is using it.

PM Messages

“Error

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 This message means that the port manager failed to allocate the requested VLAN. The

VLAN is probably being used as an internal VLAN by other features. [dec] is the requested VLAN.

Recommended Action Try to configure a different VLAN on the device.

Error Message PM-4-INACTIVE: putting [chars] in inactive state because [chars].

Explanation This message means that 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, 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-3.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-53

PM Messages

Chapter 2 Messages and Recovery Procedures

Error Message PM-4-INT_FAILUP: [chars] failed to come up. No internal VLAN available.

Explanation This message means that 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 PM-4-INT_VLAN_NOTAVAIL: Failed to allocate internal VLAN in Port
Manager.

Explanation This message means that 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 This message means that 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, 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 PM-4-LIMITS: The number of vlan-port instances on [chars] exceeded the
recommended limit of [dec].

Explanation This message means that the total number of individual VLAN ports, counted over the

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

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.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-54

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message PM-4-NO_SUBBLOCK: No PM subblock found for [chars].

Explanation This message means that 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, 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 PM-4-PORT_BOUNCED: Port [chars] was bounced by [chars].

Explanation This message means that 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.

PM Messages

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

Recommended Action No action is required.

Error Message PM-4-PVLAN_TYPE_CFG_ERR: Failed to set VLAN [dec] to a [chars] VLAN.

Explanation This message means that 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 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 PM-4-TOO_MANY_APP: application ’[chars]’ exceeded registration limit.

Explanation This message means that the port manager detected an invalid request. [chars] is the

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

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, 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-3.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-55

PORT_SECURITY Messages

Error Message PM-4-UNKNOWN_HOST_ACCESS: Invalid Host access value ([dec]) is

received.

Explanation This message means that 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, 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-3.

PORT_SECURITY Messages

This section contains the port security messages.

Chapter 2 Messages and Recovery Procedures

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.

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.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-56

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message PORT_SECURITY-6-ADDRESSES_REMOVED: Maximum system secure address count

reached. Some secure addresses configured on port [chars] removed.

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_REMOVED: VLAN [int] is no longer allowed on port

[chars]. Its port security configuration has been removed.

Explanation A configured VLAN has been excluded 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.

Recommended Action No action is required.

QOSMGR Messages

QOSMGR Messages

This section contains the quality of service (QoS) manager messages. An incorrect QoS setting causes
these messages.

Error Message QOSMGR-3-CANNOT_ERR_DISABLE_DUE_TO_INTERNAL_ERR: Can not put port in
err-disable due to an internal error [chars].

Explanation This message means that 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, 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 QOSMGR-3-HW_PROGRAM_PORT_SHAPE_FAIL: Error in programming hardware for
port shape for interface [chars].

Explanation This message means that an internal software error has occurred. [chars] is the

description of the feature that the software cannot find.

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

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, open a case

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-57

QOSMGR Messages

Chapter 2 Messages and Recovery Procedures

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 QOSMGR-3-HW_PROGRAM_SHAPE_CLASS_FAIL: Error in programming hardware
for port shape for interface [chars].

Explanation This message means that 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, 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-3.

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

Error Message QOSMGR-3-HW_PROGRAM_POL_RATE_FAIL: Error in programming the configured
police rate in policy class [chars].

Explanation This message means that 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, 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 QOSMGR-3-FAIL_TO_MATCH_QOS_LABEL: Failed to match to QoS labels.

Explanation This message means that an internal software error has occurred.

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

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, 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-3.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-58

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message QOSMGR-3-FAIL_TO_UPDATE_TX_QOS_LABEL: Failed to update transmit QoS

label to queue mapping.

Explanation This message means that 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, 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 QOSMGR-3-HW_PROGRAM_Q_SHAPE_FAIL: Error in programming hardware for
queue shape in policy class.

Explanation This message means that 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, 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

QOSMGR Messages

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

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

Error Message QOSMGR-3-POLICER_PER_PORT_EXCEEDED: Policers per port limit exceeded
in hardware.

Explanation This message means that 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, 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 QOSMGR-3-HW_PROGRAM_WRITE_PORT_POLICER_FAIL: Failed to program port
policer.

Explanation This message means that an internal software error has occurred.

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

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, 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-3.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-59

QOSMGR Messages

Chapter 2 Messages and Recovery Procedures

Error Message QOSMGR-3-CANNOT_ALLOC_POL_FOR_PLCMAP: Failed to allocate policer for

policy-maps.

Explanation This message means that 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, 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 QOSMGR-3-FAIL_GET_AGG_POLICER: Failed to get aggregate policers.

Explanation This message means that 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, 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-3.

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

Error Message QOSMGR-3-FAIL_UPDATE_HARDWARE_FOR_TBLMAP: Failed to update hardware
for table-map.

Explanation This message means that 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, 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 QOSMGR-3-UPDATE_QUEUE_THSHLD_FAIL: Failed to update queue threshold.

Explanation This message means that an internal software error has occurred.

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

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, 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-3.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-60

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message QOSMGR-3-NULL_POLICER: Internal Error Invalid Policer.

Explanation This message means that 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, 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 QOSMGR-3-POLICER_RES_COUNT: Internal Error Invalid Policer count.

Explanation This message means that 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, 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

QOSMGR Messages

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

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

Error Message QOSMGR-3-MERGE_RES_COUNT: Internal Error Invalid count.

Explanation This message means that 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, 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 QOSMGR-3-POLICYMAP_NOT_FOUND: Cannot find policymap for [chars].

Explanation This message means that an internal software error has occurred. [chars] is the

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

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, 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-3.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-61

QOSMGR Messages

Chapter 2 Messages and Recovery Procedures

Error Message QOSMGR-3-QUEUE_PTR_ERROR: queue pointers out of order [hex] [hex]

[hex] [hex].

Explanation This message means that an internal software error has occurred. [hex] [hex] [hex] [hex]

are the software-computed queue pointer values. The parameters provide error details for Cisco
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, 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 QOSMGR-3-FEATURE_NOT_FOUND: Cannot find feature for [chars].

Explanation This message means that an internal software error has occurred. [chars] is the

description of the feature that the software cannot find.

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

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, 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 QOSMGR-3-NO_VMR_QOSLABEL: qm_generate_vmrs have no qos label.

Explanation This message means that an internal software error has occurred.

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

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, 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 QOSMGR-3-NO_POLICER_QOSLABEL: Creating port Class Label Failed.

Explanation This message means that an internal software error has occurred.

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

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, 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

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

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

2-62

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message QOSMGR-3-RESERVE_COUNT_ERROR: Reserved Count Exceeding total [dec].

Explanation This message means that 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, 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 QOSMGR-3-RESOURCE_INTERNAL: Internal Error in resource allocation.

Explanation This message means that 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, 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

QOSMGR Messages

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

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

Error Message QOSMGR-3-VMRSEQ_INVALID: Internal Error Invalid VMR sequence.

Explanation This message means that 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, 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 QOSMGR-3-FILTERTYPE_INVALID: Internal Error Invalid Policy filtertype
[dec].

Explanation This message means that an internal software error has occurred. [dec] is the invalid

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

filter type identification.

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 Cisco, see the

“Error Message Traceback Reports” section on

page 1-3.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-63

QOSMGR Messages

Chapter 2 Messages and Recovery Procedures

Error Message QOSMGR-3-INITIALIZING_INTERNAL_LINK_FAIL: Failed to initialize

internal link [dec].

Explanation This message means that an internal software error has occurred. [dec] is the interface.

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 Cisco, see the

page 1-3.

Error Message QOSMGR-4-COMMAND_FAILURE: Execution of [chars] command failed.

Explanation This message means that 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 Cisco, see the

page 1-3.

“Error Message Traceback Reports” section on

“Error Message Traceback Reports” section on

Error Message QOSMGR-4-HARDWARE_PROGRAMMING_ERROR: Hardware programming error
encountered for policymap [chars].

Explanation This message means that 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, 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 QOSMGR-4-POLICER_PLATFORM_NOT_SUPPORTED: Policer configuration has
exceeded hardware limitation for policymap [chars].

Explanation This message means that the policy-map configuration has exceeded the limitation of

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

the hardware. You configured together more policers 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.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-64

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message QOSMGR-4-POLICER_POLICY_NOT_SUPPORTED: Number of policers has exceeded

per policy hardware limitation for policymap [chars].

Explanation This message means that 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.

Error Message QOSMGR-4-QOSLABEL_EXCEED_MAX: Hardware limitation was reached for
policymaps.

Explanation This message means that the policy map configuration has exceeded the limitations of

the hardware, specifically the number of QoS labels. The QoS label entries needed by this particular
policy map configuration, along with the ones already allocated for any other policy maps attached
to interfaces, cause the total number of required entries to exceed the limit supported by the
hardware for the switch.

Recommended Action Reconfigure the class map, reduce number of classes in the policy map, or

reduce or reconfigure the actions associated with classes to reduce the number of QoS labels.

QOSMGR Messages

Error Message

resources.

Explanation The number of QoS TCAM entries required for all attached QoS policies exceeds the

QOSMGR-4-QOS_TCAM_RESOURCE_EXCEED_MAX: Exceede

d a maximum of QoS TCAM

maximum number of QoS TCAM entries.

Recommended Action Reconfigure the class map or reduce the number of classes in the policy map

to reduce the number of TCAM entries.

Error Message QOSMGR-4-VLAN_LABEL_EXCEED_MAX: Exceeded a maximum of active vlan
classifications.

Note This message applies only to the Cisco ME 3400E and ME 3400 switches.

Explanation The number of VLAN classifications required for all attached per-port, per-VLAN QoS

policies exceeds the maximum number of VLAN classifications that are supported by this hardware.

Recommended Action Reconfigure the attached per-port, per-vlan QoS policies to reduce the number

of VLANs used for classification.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-65

REP Messages

REP Messages

This section contains the Resilient Ethernet Protocol (REP) messages.

Note These messages apply only to the Cisco ME 3400E and ME 3400 switches.

Error Message REP-4-LINKSTATUS: [chars] (segment [dec]) is [chars]

Explanation The Resilient Ethernet Protocol (REP) link status has changed. The first [chars] is the

interface name that has a link-status change. The [dec] is the REP segment number of the interface.
The second [chars] is the new link status.

Recommended Action No action is required.

Error Message REP-5-PREEMPTIONFAIL: can not perform preemption on segment [dec] due

to [char]

Chapter 2 Messages and Recovery Procedures

Explanation The Resilient Ethernet Protocol (REP) preempt operation failed. This could be due to

an invalid port ID or a neighbor_offset number specified with the rep block port interface
configuration command. This could also be caused by entering the rep block port preferred
interface configuration command if there is no REP port configured with the preferred keyword.
[dec] is the segment number, and [char] is the reason for the failure.

Recommended Action Correct the configuration, and run REP manual pre-emption on the primary

edge port by entering the rep preempt segment command.

RMON Messages

This section contains the Rmote 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 This message means that 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 This message means that 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.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-66

OL-9641-04

Chapter 2 Messages 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 This message means that 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-UNKN_ERR: An internal error occurred during a SPAN operation.

Explanation This message means that 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.

SPAN Messages

Error Message SPAN-3-UNKN_ERR_PORT: An internal error occurred when configuring SPAN

on port [chars].

Explanation This message means that 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_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.

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.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-67

SPANTREE Messages

Chapter 2 Messages and Recovery Procedures

Error Message SPANTREE-2-BLOCK_PVID_LOCAL: Blocking [chars] on [chars]. Inconsistent

local vlan.

Explanation This message means that 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 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 This message means that 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 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 This message means that 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 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.

Error Message SPANTREE-2-LOOPGUARD_BLOCK: Loop guard blocking port [chars] on
[chars].

Explanation This message means that 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

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-68

OL-9641-04

Chapter 2 Messages and Recovery Procedures

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 This message means that 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 This message means that 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.

Error Message SPANTREE-2-PVSTSIM_FAIL: Superior PVST BPDU received on VLAN [dec]

port [chars], claiming root [dec]:[enet]. Invoking root guard to block the port.

Explanation This message means that root guard blocked a port that might cause a spanning-tree

loop. When a PVST+ switch is connected to an MST switch, the IST root (MSTOO) becomes the
root for all PVST+ spanning trees. A loop can occur if any of the PVST+ spanning trees have a better
root than IST. To prevent the loop, root guard blocks the port on the MST switch that receives the
superior message from the PVST+ side. The first [dec] is the VLAN ID, [chars] is the short interface
name, such as Gi0/1, the second [dec] is the root bridge priority, and [enet] is the root bridge MAC
address.

Recommended Action When spanning tree converges after a new switch or switch port is added to the

topology, root guard might temporarily block the port and then automatically restore it. If the port
remains blocked, identify the root bridge from this error message, and configure a less favorable
priority for the VLAN spanning tree. There could be other superior PVST roots, and the port cannot
recover until all such roots are cleared. Alternatively, try disabling and then enabling the VLAN
port.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-69

SPANTREE Messages

Chapter 2 Messages and Recovery Procedures

Error Message SPANTREE-2-RECV_1Q_NON_1QTRUNK: Received 802.1Q BPDU on non 802.1Q

trunk [chars] [chars].

Explanation This message means that the listed interface on which a Shared Spanning Tree Protocol

(SSTP) BPDU was received was in trunk mode but was not using 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 (none or 802.1Q). When the
encapsulation is consistent, spanning tree automatically unblocks the interface.

Error Message SPANTREE-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV on [chars]
[chars].

Explanation This message means that 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, 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-3.

Error Message SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id
[dec] on [chars] [chars].

Explanation This message means that 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 802.1Q trunk. [dec] is the VLAN
ID, the first [chars] is the port, and the second [chars] is the VLAN.

Recommended Action Verify that the configurations of the native VLAN ID is consistent on the

interfaces on each end of the 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 This message means that 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

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-70

OL-9641-04

Chapter 2 Messages and Recovery Procedures

occurrences. When the inaccurate BPDUs have been stopped, the interfaces automatically recover
and resume normal operation. Make sure that it is appropriate to have root guard enabled on the
interface.

Error Message SPANTREE-2-ROOTGUARD_CONFIG_CHANGE: Root guard [chars] on port [chars]
on [chars].

Explanation This message means that 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].

SPANTREE Messages

Explanation This message means that 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 This message means that 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.

Error Message SPANTREE-3-BAD_PORTNUM_SIZE: Rejected an attempt to set the port

number field size to [dec] bits (valid range is [dec] to [dec] bits).

Explanation This message means that an error occurred in the platform-specific code that caused it

to request more or less bits than are possible. The spanning-tree port identifier is a 16-bit field,
which is divided evenly between the port priority and port number, with each subfield being 8 bits.
This allows the port number field to represent port numbers between 1 and 255. However, on
systems with more than 255 ports, the size of port number portion of the port ID must be increased
to support the number of ports. This is performed by the spanning-tree subsystem at system
initialization because the maximum number of ports on a particular platform will not change. This

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-71

SPANTREE Messages

Chapter 2 Messages and Recovery Procedures

error occurs because of an error in the platform-specific code, which causes it to request more or
less bits than are possible. The first [dec] is the number of bits for the port number, and the second
and third [dec] describe the valid range.

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

Research and attempt to resolve the error by using the Output Interpreter. Enter the show version
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 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-3.

Error Message SPANTREE-3-PORT_SELF_LOOPED: [chars] disabled.- received BPDU src mac
([enet]) same as that of interface.

Explanation This message means that a BPDU was received on the listed interface with a source

MAC address that matches the one assigned to the listed interface. This means that a port might be
looped back to itself, possibly because of an installed diagnostic cable. The interface will be
administratively shut down. [chars] is the interface that received the BPDU, and [enet] is the source
MAC address.

Recommended Action Check the interface configuration and any cable connected to the interface.

When the problem is resolved, re-enable the interface by entering the no shutdown interface
configuration command.

Error Message SPANTREE-4-PORT_NOT_FORWARDING: [chars] [chars] [chars] [chars].

Explanation This message appears when a port-not-forwarding alarm is set or cleared. The first

[chars] is the mode (for example, assert or clear), and the second [chars] is the severity (for example,
minor). The third [chars] is the interface name, and the fourth [chars] is the alarm string (for
example, port not forwarding).

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

Error Message SPANTREE-5-EXTENDED_SYSID: Extended SysId [chars] for type [chars].

Explanation This message means that the extended system ID feature is either enabled or disabled

for the given type of spanning tree. If enabled, the spanning-tree instance identifier is stored in the
lower portion of the bridge ID priority field and limits the allowed values for the bridge priority from
0 to 61440, in increments of 4096. If disabled, the bridge ID priority field consists only of the
configured priority, but some spanning-tree features might not be available on a given platform (for
example, support for 4096 VLANs). On some platforms, this feature might be mandatory. The first
[chars] is the extended system ID state (enable or disable), and the second [chars] is the
spanning-tree instance.

Recommended Action No action is required.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-72

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message SPANTREE-5-ROOTCHANGE: Root Changed for [chars] [dec]: New Root Port

is [chars]. New Root Mac Address is [enet].

Explanation This message means that the root switch changed for a spanning-tree instance. The first

[chars] and [dec] is the interface ID for the previous root port, the second [chars] is the interface ID
for the new root port, and [enet] is the Ethernet address of the new root port.

Recommended Action No action is required.

Error Message SPANTREE-5-TOPOTRAP: Topology Change Trap for [chars] [dec].

Explanation This message means that a trap was generated because of a topology change in the

network.

Recommended Action No action is required.

Error Message SPANTREE-6-PORTADD_ALL_VLANS: [chars] added to all Vlans

Explanation The interface has been added to all VLANs. [chars] is the added interface.

SPANTREE Messages

Recommended Action No action is required.

Error Message SPANTREE-6-PORTDEL_ALL_VLANS: [chars] deleted from all Vlans

Explanation The interface has been deleted from all VLANs. [chars] is the deleted interface.

Recommended Action No action is required.

Error Message SPANTREE-6-PORT_STATE: Port [chars] instance [dec] moving from [chars]

to [chars].

Explanation This message means that the port state changed. The first [chars] is the interface name.

[dec] is the spanning-tree instance ID. The second [chars] is the old state (such as listening, learning,
or forwarding, and so forth), and the third [chars] is the new state.

Recommended Action No action is required.

Error Message SPANTREE-7-BLOCK_PORT_TYPE: Blocking [chars] on [chars]. Inconsistent

port type.

Explanation This message means that the listed interface is being held in the spanning-tree blocking

state until the port-type inconsistency is resolved. The first [chars] is the interface, and the second
[chars] is the spanning-tree instance.

Recommended Action Verify that the configuration and operational states of the listed interface and

those 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 (none or 802.1Q). When these
parameters are consistent, spanning tree automatically unblocks the interface.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-73

SPANTREE_FAST Messages

Error Message SPANTREE-7-PORTDEL_SUCCESS: [chars] deleted from Vlan [dec].

Error Message SPANTREE-7-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk

[chars] [chars].

Chapter 2 Messages and Recovery Procedures

Explanation This message means that the interface has been deleted from VLAN. [chars] is the

interface, and [dec] is the VLAN ID.

Recommended Action No action is required.

Explanation This message means that an SSTP BPDU was received on the listed interface, which is

not an operational trunking interface. The first [chars] is the port name, and the second [chars] is the
VLAN name.

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 (none or 802.1Q). When these
parameters are consistent, spanning tree automatically unblocks the interface.

SPANTREE_FAST Messages

This section contains the spanning-tree fast-convergence message.

Error Message SPANTREE_FAST-7-PORT_FWD_UPLINK: [chars] [chars] moved to Forwarding
(UplinkFast).

Explanation This message means that the listed interface has been selected as the new path to the

root switch for the listed spanning-tree instance. The first [chars] is the spanning-tree instance, and
the second [chars] is the interface.

Recommended Action No action is required.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-74

OL-9641-04

Chapter 2 Messages and Recovery Procedures

SPANTREE_VLAN_SW Messages

The section contains the per-VLAN spanning-tree-specific message.

Error Message SPANTREE_VLAN_SW-2-MAX_INSTANCE: Platform limit of [dec] STP instances
exceeded. No instance created for [chars] (port [chars]).

Explanation This message means that the number of currently active VLAN spanning-tree instances

has reached a platform-specific limit. No additional VLAN instances will be created until the
number of existing instances drops below the platform limit. [dec] is the spanning-tree instance
limit, and the first [chars] is the smallest VLAN number of those VLANs that are unable to have
spanning-tree instances created.

Recommended Action Reduce the number of currently active spanning-tree instances by either

disabling some of the currently active spanning-tree instances or deleting the VLANs associated
with them. You must manually enable the spanning trees that could not be created because of limited
instances.

SPANTREE_VLAN_SW Messages

STORM_CONTROL Messages

This section contains the storm control messages.

Error Message STORM_CONTROL-3-FILTERED: A [chars] storm detected on [chars]. A
packet filter action has been applied on the interface.

Explanation This message means that the amount of traffic detected on the interface has exceeded

the configured threshold values. The system is filtering the excess traffic. The first [chars] is the
traffic type, and the second [chars] is the interface.

Recommended Action Determine and fix the root cause of the excessive traffic on the interface.

Error Message STORM_CONTROL-3-SHUTDOWN: A packet storm was detected on [chars]. The

interface has been disabled.

Explanation This message means that the amount of traffic detected on the interface has exceeded

the configured threshold values. Since the interface is configured to shutdown if a packet storm
event is detected, it has been placed in an error-disabled state. [chars] is the affected interface.

Recommended Action You can enable error-disabled recovery by using the errdisable recovery

global configuration command to automatically re-enable the interface. You should determine and
fix the root cause of the excessive traffic on the interface.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-75

SUPERVISOR Messages

SUPERVISOR Messages

This section contains the supervisor ASIC message. This ASIC controls the CPU and the switch send
and receive ports.

Error Message SUPERVISOR-3-FATAL: [chars].

Explanation This message means that an internal error occurred in the supervisor ASIC. [chars] is

the detailed error message.

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

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

Message Traceback Reports” section on page 1-3.

Chapter 2 Messages and Recovery Procedures

“Error

SUPQ Messages

This section contains the supervisor queue messages. These messages are related to CPU send and
receive queues.

Error Message SUPQ-3-THROTTLE_CPU_QUEUE: Invalid application ID [dec] used for
throttling.

Explanation This message means that an application has passed an invalid application ID for throttle

check. [dec] is the internal application identifier.

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

Message Traceback Reports” section on page 1-3.

Error Message SUPQ-4-CPUHB_RECV_STARVE: [chars].

Explanation This message means that the system has detected that messages directed to the CPU are

delayed. [chars] is the detailed error message.

“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, 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-3.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-76

“Error

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message SUPQ-4-CPUHB_SLOW_TRANSMIT: [chars].

Explanation This message means that the system is warning you about a slowdown of the transmit

interface. [chars] is the detailed error message.

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

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. 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-3.

Error Message SUPQ-4-CPUHB_TX_FAIL: [chars].

Explanation This message means that the system is warning you about the transmit interface

discarding the heartbeat message. [chars] is the detailed error message.

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

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. 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-3.

SUPQ Messages

“Error

“Error

Error Message SUPQ-4-PORT_QUEUE_STUCK: Port queue Stuck for asic [dec] port [dec]
queue [dec].

Explanation This message means that the system has detected that an interface queue is not being

cleared in a reasonable time. The first [dec] is the ASIC, the second [dec] is the interface, and the
third [dec] is the queue number.

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

Error Message SUPQ-4-RECV_QUEUE_STUCK: Receive queue Stuck for asic [dec] queue
[dec].

Explanation This message means that the system has detected that the receive queue is not being

cleared in a reasonable time. The first [dec] is the ASIC, and the second [dec] is the queue number.

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

Research and attempt to resolve the error by using the Output Interpreter. 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-3.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-77

SW_DAI Messages

SW_DAI Messages

This section contains the dynamic ARP inspection (DAI) messages.

Note These messages apply only to the Cisco ME 3400E and ME 3400 switches.

Error Message SW_DAI-4-ACL_DENY: [dec] Invalid ARPs ([chars]) on [chars], vlan

[dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]).

Explanation This message means that the switch has received ARP packets considered invalid by

ARP inspection. The packets are erroneous, and their presence shows that administratively denied
packets were seen in the network. This log message appears when ACLs either explicitly or
implicitly deny packets (with static ACL configuration). These packets show attempted
man-in-the-middle attacks in the network. The first [dec] is the number of invalid ARP packets. The
first [chars] is either Req (request) or Res (response), and the second [chars] is the short name of the
ingress interface. The second [dec] is the ingress VLAN ID.
[enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the
sender, the MAC address of the target, the IP address of the target, and the time of day.

Chapter 2 Messages and Recovery Procedures

Recommended Action No action is required.

Error Message SW_DAI-4-DHCP_SNOOPING_DENY: [dec] Invalid ARPs ([chars]) on [chars],

vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]).

Explanation This message means that the switch has received ARP packets considered invalid by

ARP inspection. The packets are erroneous, and their presence might show attempted
man-in-the-middle attacks in the network. This log message appears when the sender’s IP and MAC
address binding for the received VLAN is not in the DHCP snooping database. The first [dec] is the
number of invalid ARP packets. The first [chars] is either Req (request) or Res (response), and the
second [chars] is the short name of the ingress interface. The second [dec] is the ingress VLAN ID.
[enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the
sender, the MAC address of the target, the IP address of the target, and the time of day.

Recommended Action No action is required.

Error Message SW_DAI-6-DHCP_SNOOPING_PERMIT: [dec] ARPs ([chars]) on [chars], vlan

[dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]).

Explanation This message means that the switch has received ARP packets that have been permitted

because the sender’s IP and MAC address match the DHCP snooping database for the received
VLAN. The first [dec] is the number of valid ARP packets. The first [chars] is either Req (request)
or Res (response), and the second [chars] is the short name of the ingress interface. The second [dec]
is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the
sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and
the time of day.

Recommended Action No action is required.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-78

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message SW_DAI-4-INVALID_ARP: [dec] Invalid ARPs ([chars]) on [chars], vlan

[dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]).

Explanation This message means that the switch has received ARP packets considered invalid by

ARP inspection. The packets do not pass one or more validation checks of the source or destination
MAC address or the IP address. The first [dec] is the number of invalid ARP packets. The first
[chars] is either Req (request), Res (response), or Invalid Opcode. The second [chars] is the short
name of the ingress interface. The second [dec] is the ingress VLAN ID.
[enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the
sender, the MAC address of the target, the IP address of the target, and the time of day.

Recommended Action No action is required.

Error Message SW_DAI-4-PACKET_BURST_RATE_EXCEEDED: [dec] packets received in [dec]

seconds on [chars].

Explanation This message means that the switch has received the given number of ARP packets in

the specified burst interval. The interface is in the error-disabled state when the switch receives
packets at a higher rate than the configured packet rate every second over the configured burst
interval. The message is logged just before the interface is error disabled and if the configured burst
interval is more than a second. The first [dec] is the number of packets, the second [dec] is the
number of seconds, and [chars] is the affected interface.

SW_DAI Messages

Recommended Action No action is required.

Error Message SW_DAI-4-PACKET_RATE_EXCEEDED: [dec] packets received in [dec]

milliseconds on [chars].

Explanation This message means that the switch has received the given number of ARP packets for

the specified duration on the interface. This message is logged just before the port is put into the
error-disabled state because of the exceeded packet rate and when the burst interval is set to
1

second. The first [dec] is the number of packets, the second [dec] is the number of milliseconds,

and [chars] is the affected interface.

Recommended Action No action is required.

Error Message SW_DAI-4-SPECIAL_LOG_ENTRY: [dec] Invalid ARP packets [[time-of-day]].

Explanation This message means that the switch has received ARP packets considered invalid by

ARP inspection. The packets are erroneous, and their presence might show attempted
man-in-the-middle attacks in the network. This message differs from other SW_DAI messages in
that this message captures all messages when the rate of incoming packets exceeds the dynamic ARP
inspection logging rate. [dec] is the number of invalid ARP packets, and [time-of-day] is the time
of day.

Recommended Action No action is required.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-79

SW_VLAN Messages

Chapter 2 Messages and Recovery Procedures

Error Message SW_DAI-6-ACL_PERMIT: [dec] ARPs ([chars]) on [chars], vlan

[dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]).

Explanation This message means that the switch has received ARP packets that are permitted as a

result of an ACL match. The first [dec] is the number of valid ARP packets. The first [chars] is either
Req (request) or Res (response), and the second [chars] is the short name of the ingress interface.
The second [dec] is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC
address of the sender, the IP address of the sender, the MAC address of the target, the IP address of
the target, and the time of day.

Recommended Action No action is required.

Error Message SW_DAI-6-DHCP_SNOOPING_PERMIT: [dec] ARPs ([chars]) on [chars], vlan

[dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]).

Explanation This message means that the switch has received ARP packets that have been permitted

because the sender’s IP and MAC address match the DHCP snooping database for the received
VLAN. The first [dec] is the number of valid ARP packets. The first [chars] is either Req (request)
or Res (response), and the second [chars] is the short name of the ingress interface. The second [dec]
is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the
sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and
the time of day.

Recommended Action No action is required.

SW_VLAN Messages

This section contains the VLAN manager messages. The VLAN manager receives information from the
VTP and enables the proper VLAN membership on all interfaces through the port manager.

Error Message SW_VLAN-3-MALLOC_FAIL: Failed to allocate [dec] bytes

Explanation Memory allocation failed. [dec] is the number of bytes.

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

Message Traceback Reports” section on page 1-3.

Error Message SW_VLAN-3-VLAN_DAT_CACHE_SEQUENCE: Out of sequence vlan.dat sync
message. Expected: [dec]; received: [dec].

Explanation The vlan.dat file is synchronized to the STANDBY through one or more checkpoint

messages from ACTIVE. The sequence number for each set of checkpoint messages starts with 1.
These messages are cached at the STANDBY until the end-of-set indicator is received. The

“Error

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-80

OL-9641-04

Chapter 2 Messages and Recovery Procedures

STANDBY received a checkpoint message with a sequence number that does not match the expected
sequence number. The first [dec] is the expected checkpoint message sequence number, and the
second [dec] is the received checkpoint message sequence number.

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

Research and attempt to resolve the error using the Output Interpreter. 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

Message Traceback Reports” section on page 1-3.

Error Message SW_VLAN-3-VLAN_PM_NOTIFICATION_FAILURE: VLAN Manager synchronization
failure with Port Manager over [chars].

Explanation This message means that the VLAN manager dropped a notification from the port

manager because of a lack of ready pool space. [chars] is the type of port manager notification.

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

Message Traceback Reports” section on page 1-3.

SW_VLAN Messages

“Error

“Error

Error Message SW_VLAN-3-VTP_PROTOCOL_ERROR: VTP protocol code internal error
[chars].

Explanation This message means that the VTP code encountered an unexpected error while

processing a configuration request, a packet, or a timer expiration. [chars] is the internal error.

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

Research and attempt to resolve the error by using the Output Interpreter. 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 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 SW_VLAN-4-BAD_PM_VLAN_COOKIE_RETURNED: VLAN manager unexpectedly
received a bad PM VLAN cookie from the Port Manager, VLAN indicated [dec].

Explanation This message means that the VLAN manager received an upcall and a VLAN cookie

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

from the port manager, which translated to a bad VLAN number. [dec] is the VLAN ID.

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 Cisco, see the

“Error Message

Traceback Reports” section on page 1-3.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-81

SW_VLAN Messages

Chapter 2 Messages and Recovery Procedures

Error Message SW_VLAN-4-BAD_STARTUP_VLAN_CONFIG_FILE: Failed to configure VLAN from

startup-config. Fallback to use VLAN configuration file from non-volatile memory.

Explanation This message means that the VLAN software did not use the VLAN configuration from

the startup-configuration file. It will use the binary VLAN configuration file in NVRAM memory.

Recommended Action No action is required.

Error Message SW_VLAN-4-BAD_VLAN_CONFIGURATION_FILE: VLAN configuration file

contained incorrect verification word [hex].

Explanation This message means that the VLAN configuration file read by the VLAN manager did

not begin with the correct value. The VLAN configuration file is invalid, and it has been rejected.
[hex] is the incorrect verification value.

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 Cisco, see the

Traceback Reports” section on page 1-3.

“Error Message

Error Message SW_VLAN-4-BAD_VLAN_CONFIGURATION_FILE_VERSION: VLAN configuration
file contained unknown file version [dec].

Explanation This message means that the VLAN configuration file read by the VLAN manager

contained an unrecognized file version number, which might mean an attempt to regress to an older
version of the VLAN manager software. [dec] is the file version number.

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 Cisco, see the

“Error Message

Traceback Reports” section on page 1-3.

Error Message SW_VLAN-4-BAD_VLAN_TIMER_ACTIVE_VALUE: Encountered incorrect VLAN
timer active value [chars].

Explanation This message means that, because of a software error, a VLAN timer was detected as

active when it should have been inactive or as inactive when it should have been active. [chars] is
the VLAN timer active value.

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

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

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-82

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message SW_VLAN-4-EXT_VLAN_INTERNAL_ERROR: Extended VLAN manager received an

internal error [dec] from [chars] [chars].

Explanation This message means that an unexpected error code was received by the VLAN manager

from the extended-range VLAN configuration software. [dec] is the error code. The first [chars] is
the function, and the second [chars] describes the error 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. 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 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 SW_VLAN-4-EXT_VLAN_INVALID_DATABASE_DATA: Extended VLAN manager
received bad data of type [chars] value [dec] from function [chars].

Explanation This message means that invalid data was received by the extended-range VLAN

manager from an extended-range VLAN configuration database routine. The first [chars] is the data
type, [dec] is the number received, and the second [chars] is the function name.

SW_VLAN Messages

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

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 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 SW_VLAN-4-IFS_FAILURE: VLAN manager encountered file operation error
call = [chars] / file = [chars] / code = [dec] ([chars]) / bytes transferred =
[dec].

Explanation This message means that the VLAN manager received an unexpected error return from

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

a Cisco IOS file system (IFS) call while reading the VLAN database. The first [chars] is the function
call name, and the second [chars] is the file name. [dec] is the error code, the third [chars] is the
textual interpretation of the error code, and the second [dec] is the number of bytes transferred.

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

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-83

SW_VLAN Messages

Chapter 2 Messages and Recovery Procedures

Error Message SW_VLAN-4-NO_PM_COOKIE_RETURNED: VLAN manager unexpectedly received a

null [chars] type cookie from the Port Manager, data reference [chars].

Explanation This message means that the VLAN manager queried the port manager for a reference

cookie but received a NULL pointer instead. The first [chars] is the type of port manager cookie,
and the second [chars] is the interface or VLAN that is the source of the problem.

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 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 SW_VLAN-4-STARTUP_EXT_VLAN_CONFIG_FILE_FAILED: Failed to configure
extended range VLAN from startup-config. Error [chars].

Explanation This message means that the VLAN software failed to use an extended-range VLAN

configuration from the startup configuration file. All extended-range VLAN configurations are lost
after the system boots up. [chars] is a description of the error code.

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

Recommended Action No action is required.

Error Message SW_VLAN-4-VLAN_CREATE_FAIL: Failed to create VLANs [chars]: [chars].

Explanation This message means that the specified VLANs could not be created. The port manager

might not have completed the VLAN creation requests because the VLANs already exist as internal
VLANs. The first [chars] is the VLAN ID, and the second [chars] describes the error.

Recommended Action Check the internal VLAN usage by using show vlan internal usage privileged

EXEC command, reconfigure the feature that is using the internal VLANs, and try to create the
VLANs again. If this message appears again, 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 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 SW_VLAN-6-OLD_CONFIG_FILE_READ: Old version [dec] VLAN configuration
file detected and read OK. Version [dec] files will be written in the future.

Explanation This message means that the VLAN software detected an old version of the VLAN

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

configuration file format. It interpreted the file without a problem, but it will create files using the
new format in the future. The first [dec] is the old version number, and the second [dec] is the new
version number.

Recommended Action No action is required.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-84

OL-9641-04

Chapter 2 Messages and Recovery Procedures

Error Message SW_VLAN-6-VLAN_DAT_CACHE_EXISTS: Unexpected vlan.dat cache exists.

Removing the cache and continuing the sync with new set.

Explanation This message rarely appears and does not affect switch functionality.

Recommended Action No action is required.

Error Message SW_VLAN-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to [chars].

Explanation The VLAN Trunking Protocol (VTP) domain name was changed through the

configuration to the name specified in the message. [chars] is the changed domain name.

Recommended Action No action is required.

TCAMMGR Messages

This section contains the ternary content-addressable memory manager (TCAMMGR) messages.

TCAMMGR Messages

Error Message TCAMMGR-3-GROW_ERROR: cam region [dec] can not grow.

Explanation This message means that the specified CAM region is configured as a static region with

a fixed number of entries, and a caller requested to add more CAM entries. [dec] is the CAM region.

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

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. 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-3.

Error Message TCAMMGR-3-HANDLE_ERROR: cam handle [hex] is invalid.

Explanation This message means that the CAM handle used by the caller is not valid. [hex] is the

handle value.

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

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. 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-3.

“Error

“Error

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-85

TCAMMGR Messages

Chapter 2 Messages and Recovery Procedures

Error Message TCAMMGR-3-INDEX_ERROR: cam value/mask index [dec] is invalid.

Explanation This message means that the CAM index used by the caller is not valid. [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, 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-3.

Error Message TCAMMGR-3-MOVE_ERROR: cam entry move from index [int] to index [int]
failed.

Explanation This message means that moving a CAM entry from one index to another failed. [int] 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, 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-3.

“Error

“Error

Error Message TCAMMGR-3-REGION_ERROR: cam region [dec] is invalid.

Explanation This message means that the CAM region is not valid. [dec] is the region.

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

Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. 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-3.

Error Message TCAMMGR-3-REGMASK_ERROR: invalid cam region [dec] mask [dec] pair.

Explanation This message means that a caller attempted to install an entry with an invalid mask for

the region. Only a predetermined set of masks is allowed in a region. The first [dec] is the region,
and the second [dec] is the mask.

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

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

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-86

OL-9641-04

Chapter 2 Messages and Recovery Procedures

UDLD Messages

This section contains UniDirectional Link Detection (UDLD) messages.

Error Message UDLD-0-STOPPED:UDLD process stopped:[chars].

Explanation This message means that the UDLD process stopped because it cannot read the unique

system identifier that is being used by UDLD. The system identifier is used to identify the device
that is sending the UDLD packets. [chars] is the UDLD process name.

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

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

UDLD Messages

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

Error Message UDLD-3-UDLD_IDB_ERROR: UDLD error handling [chars] interface [chars].

Explanation This message means that a software error occurred in UDLD processing associated with

a specific interface. The first [chars] is the event, and the second [chars] is the interface.

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

Research and attempt to resolve the error by using the Output Interpreter. 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 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 UDLD-3-UDLD_INTERNAL_ERROR: UDLD internal error [chars].

Explanation This message means that a software check failed during UDLD processing. [chars] is a

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

description of the internal error.

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

Research and attempt to resolve the error by using the Output Interpreter. 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 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-3.

OL-9641-04

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-87

UDLD Messages

Chapter 2 Messages and Recovery Procedures

Error Message UDLD-3-UDLD_INTERNAL_IF_ERROR: UDLD internal error, interface [chars]

[chars].

Explanation This message means that a software check failed during UDLD processing. The first

[chars] is the interface, and the second [chars] is a description of 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. 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 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 UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface [chars], [chars]
detected.

Explanation This message means that the UDLD Protocol disabled an interface because it detected

connections between neighbors that were functioning only in one direction, which might potentially
cause spanning-tree loops or interfere with connectivity. The cause is likely to be hardware related,
either due to a bad port, a bad cable, or a misconfigured cable. The first [chars] is the interface, and
the second [chars] is the error detected.

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

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 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 UDLD-6-UDLD_PORT_RESET: UDLD reset interface [chars].

Explanation This message means that the UDLD Protocol detected a unidirectional connection

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

between neighbors. Reset the port that was disabled by UDLD by using the udld reset privileged
EXEC command or through a hardware action such as a link-state change. [chars] is the interface.

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 Cisco, see the

“Error Message

Traceback Reports” section on page 1-3.

Cisco ME 3400E, ME 3400, and ME 2400 Ethernet Access Switch System Message Guide

2-88

OL-9641-04