Catalyst 3750x PDF
Catalyst 3750x PDF
February 2011
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
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 IMPLIED, INCLUDING, WITHOUT
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.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at
www.cisco.com/go/trademarks. Third party trademarks mentioned 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. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display
output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in
illustrative content is unintentional and coincidental.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
© 2007–2010 Cisco Systems, Inc. All rights reserved.
Preface vii
Purpose vii
Conventions vii
EC Messages 2-29
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 iii
PM Messages 2-82
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
iv OL-9772-05
PT Messages 2-92
INDEX
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 v
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
vi OL-9772-05
Purpose
This guide describes the Catalyst 3750-X, 3750-E, 3560-X, or 3560-E switch or the Catalyst 3750-X or
3750-E switch stack-specific system messages that you might encounter. For a complete list of
Cisco IOS system error messages, see the Cisco IOS Software System Error Messages, Cisco IOS
Release 12.2 available from the Cisco.com home page by choosing Technical Support &
Documentation > Documentation > Cisco IOS Software.
This guide does not describe how to install your switch or how to configure software features on your
switch. It also does not provide detailed information about commands that have been created or changed
for use by the switch. For hardware installation information, see the hardware installation guide that
shipped with your switch. For software information, see the software configuration guide and the
command reference for this release.
For documentation updates, see the release notes for this release.
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.
• Information you enter is in boldface screen font.
• Nonprinting characters, such as passwords or tabs, are in angle brackets (< >).
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 vii
Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in
this manual.
Related Publications
• Catalyst 3750-X switch:
http://www.cisco.com/en/US/products/ps10745/tsd_products_support_series_home.html
• Catalyst 3750-E switch:
http://www.cisco.com/en/US/products/ps7077/tsd_products_support_series_home.html
• Catalyst 3560-X switch:
http://www.cisco.com/en/US/products/ps10744/tsd_products_support_series_home.html
• Catalyst 3560-E switch:
http://www.cisco.com/en/US/products/ps7078/tsd_products_support_series_home.html
Note • For initial configuration information, see the “Using Express Setup” chapter in the getting started
guide or the “Configuring the Switch with the CLI-Based Setup Program” appendix in the hardware
installation guide.
• For device manager requirements, see the “System Requirements” section in the release notes.
• For Network Assistant requirements, see the Getting Started with Cisco Network Assistant.
• For cluster requirements, see the Release Notes for Cisco Network Assistant.
• For upgrade information, see the “Downloading Software” section in the release notes.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
viii OL-9772-05
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 ix
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
x OL-9772-05
This guide describes the Catalyst 3750-X, 3750-E, 3560-X, or 3560-E-specific system messages. The
system software sends these messages to the console (and, optionally, to a logging server on another
system). Not all system messages mean problems with your system. Some messages are informational,
and others can help diagnose problems with communications lines, internal hardware, or the system
software.
Note For information about system messages that are not Catalyst 3750-X, 3750-E, 3560-X, or 3560-E
platform-specific, see the Cisco IOS Software System Messages for Cisco IOS Release 12.2S.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 1-1
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
1-2 OL-9772-05
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 1-3
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
1-4 OL-9772-05
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 1-5
• SEVERITY is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower
the number, the more serious the situation.
Table 1-2 Message Severity Levels
All syslog messages generated by a Catalyst 3750-X or 3750-E switch other than the master switch
appear with (Switch-x) where Switch-x is the number of the stack member generating the message.
Syslog messages generated by the master switch appear with no hostname string.
This example shows a partial switch system message on a switch other than a Catalyst 3750-E:
00:00:46: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up
00:00:47: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
00:00:47: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
00:00:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
00:00:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed
state to down 2 *Mar 1 18:46:11: %SYS-5-CONFIG_I: Configured from console by vty2
(10.34.195.36)
18:47:02: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36)
*Mar 1 18:48:50.483 UTC: %SYS-5-CONFIG_I: Configured from console by vty2 (10.34.195.36)
This example shows a partial switch system message for a stack master and a stack member switch
(hostname Switch-2) in a Catalyst 3750-E switch stack:
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
1-6 OL-9772-05
Some system messages ask you to copy the error messages and take further action.
Output Interpreter
The Output Interpreter provides additional information and suggested resolutions based on the output of
many CLI commands, such as the show tech-support privileged EXEC command.
https://www.cisco.com/pcgi-bin/Support/OutputInterpreter/home.pl
Bug Toolkit
The Bug Toolkit provides information on open and closed caveats. You can search for all known bugs in
a specific Cisco IOS Release.
http://tools.cisco.com/Support/BugToolKit/
Contacting TAC
If you cannot determine the nature of the error, see the “Obtaining Documentation and Submitting a
Service Request” section on page ix for further information.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 1-7
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
1-8 OL-9772-05
This chapter describes the Catalyst 3750-X, 3750-E, 3560-X, and 3560-E system messages in
alphabetical order by facility. Within each facility, the messages are listed by severity levels 0 to 7: 0 is
the highest severity level, and 7 is the lowest severity level. Each message is followed by an explanation
and a recommended action.
Note The messages listed in this chapter do not include the hostname or the date/time-stamp designation that
appears only if the software is configured for system log messaging.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-1
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-2 OL-9772-05
ACLMGR Messages
Error Message ACLMGR-2-NOMAP: Cannot create ACL Manager data structures for VLAN Map
[chars].
Explanation The ACL manager could not allocate the data structures needed to describe a VLAN
map into 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.
Error Message ACLMGR-2-NOVLB: Cannot create memory block for VLAN [dec].
Explanation The ACL manager could not save per-VLAN information needed for its correct
operation. Some per-interface features, such as access groups or VLAN maps, will not be configured
correctly. [dec] is the VLAN ID.
Recommended Action Use a less complicated configuration that requires less memory.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-3
Explanation Available resources are not sufficient to create a hardware representation of the ACL. A
lack of available logical operation units or specialized hardware resources can cause this problem.
Logical operation units are needed for a TCP flag match or a test other than eq (ne, gt, lt, or range)
on TCP, UDP, or SCTP port numbers.
Recommended Action Modify the ACL configuration to use fewer resources, or rename the ACL with
a name or number that alphanumerically precedes the other ACL names or numbers.
Error Message ACLMGR-3-ACLTCAMFULL: Acl Tcam Full. Drop packets on Output Acl label
[dec] on [chars] [chars].
Explanation The platform-specific TCAM cannot support the number of configured ACLs. [dec] is
the label number, and [chars] is the layer. The first [chars] is for Layer 3, and the second [chars] is
for Layer 2. If only the Layer 2 or Later 3 hardware table is full, only one string appears, and the
other string is NULL.
Recommended Action Reduce the number of IP or MAC access lists to be applied to interfaces.
Explanation The system ran out of CPU DRAM when trying to merge internally required elements
with the configured access maps. The first [chars] is the access-map name, the second [chars] is the
direction in which the map was applied (input or output), and [dec] is the label number.
Explanation An internal software error has occurred. [chars] is the interface name. The first [dec] is
the label associated with the ACL, and the second [dec] is the ASIC number.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-4 OL-9772-05
Explanation The system ran out of CPU memory when trying to merge sections of an access map.
The first [chars] is the map name, and the second [chars] is the direction (incoming or outgoing) in
which the map was applied. The first [dec] is the entry number, and the second [dec] is the label
number.
Recommended Action Reduce other system activity to ease memory demands. For example, remove
any ACLs that have been defined but not used. Use simpler ACLs with fewer access control entries
(ACEs). Use fewer VLANs, and remove any unneeded VLANs from the VLAN database.
Error Message ACLMGR-3-INTTABLE: Not in truth table: VLMAP [dec] RACL [dec] Mcb [dec]
Feat [dec].
Explanation An unrecoverable software error occurred while trying to merge the configured input
features. [dec] are internal action codes.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Explanation The configuration is too complicated for the platform-specific ACL merge code to
support. The most likely cause is too many separate access lists in a single VLAN map or policy
map. The first [dec] is the number of levels of recursion. The second [dec] is an internal code number
of the merge stage that encountered the problem.
Recommended Action Reduce the number of IP or MAC access lists (considered separately) in any
one VLAN or policy map to fewer than the number of levels reported by this log message.
Error Message ACLMGR-3-MERGEFAIL: [chars] ACL merge error [dec] ([chars]) on [chars]
label [dec].
Explanation The ACL manager could not 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. 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.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-5
Error Message ACLMGR-3-NOLABEL: Cannot allocate [chars] label for interface [chars].
Explanation The ACL manager could not allocate a label for the features on this interface. This
means that the hardware cannot be programmed to implement the features, and packets for this
interface will be filtered in software. There is a limit of 256 labels per direction. The first [chars] is
the direction (input or output), and the second [chars] is the interface name.
Recommended Action Use a simpler configuration. Use the same ACLs on multiple interfaces, if
possible.
Error Message ACLMGR-3-OUTTTABLE: Not in truth table: RACL [dec] VLMAP [dec].
Explanation A software error occurred while trying to merge the configured output features. The first
and second [dec] are the internal action codes.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Error Message ACLMGR-3-PACLTTABLE: Not in truth table: IPSrcGrd [dec] PACL [dec].
Explanation A software error occurred while trying to merge the configured port ACL features. The
first [dec] is the action specified by IP source guard, and the second [dec] is the action specified by
the port ACL.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Error Message ACLMGR-3-QOSTTABLE: Not in truth table: ACL [dec] in map, action [dec].
Explanation A software error occurred while trying to merge a quality of service (QoS) policy map.
The first [dec] is the ACL number, and the second [dec] is the action corresponding to the specified
ACL number.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-6 OL-9772-05
Explanation The ACL manager can now 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.
Explanation An internal software error has occurred. [hex] is an internal action code.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Explanation The ACL manager could not load the complete configuration into the hardware, so some
features will be applied in the software. Some or all of the packets in a VLAN are 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.
Explanation The ACL manager cannot store the flow-based Switched Port Analyzer (FSPAN)
configuration, and this feature has been temporarily disabled for the specified session. The first
[chars] is the type of FSPAN session: either vlan-based FSPAN for a VLAN FSPAN session or
port-based FSPAN for a port FSPAN session. [dec] is the session number, and the second [chars] is
the type of traffic being filtered: MAC, IPv4, or IPv6.
Recommended Action Specify an Switch Database Management (SDM) template that allocates more
system resources for ACLs, simplify the ACL, or use the same ACLs on multiple interfaces.
Explanation The ACL manager can store the flow-based SPAN configuration for the specified
session. One or more ACLs had previously been unloaded because of lack of hardware memory. The
first [chars] is the type of FSPAN session: either vlan-based FSPAN for a VLAN FSPAN session or
port-based FSPAN for a port FSPAN session. [dec] is the session number, and the second [chars] is
the type of traffic being filtered: MAC, IPv4, or IPv6.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-7
AUTHMGR Messages
Error Message AUTHMGR-5-SECURITY_VIOLATION: Security violation on the interface
[chars], new MAC address ([enet) is seen. AuditSessionID [chars]
Explanation A host on the interface attempted to gain access to the network or attempted to
authenticate. The interface mode does not support the number of hosts that are attached to the
interface. This is a security violation, and the interface has been error disabled. The first [chars] is
the interface, [enet] is the Ethernet address of the host, and the second [chars] is the session ID.
Recommended Action Make sure that the interface is configured to support the number of attached
hosts. Enter the shutdown interface configuration command followed by no shutdown interface
configuration command to restart the interface.
Explanation A VLAN was assigned. [dec] is the VLAN ID, the first [chars] is the interface, and the
second [chars] is the session ID.
Error Message AUTHMGR-7-FAILOVER: Failing over from [chars] for client ([chars]) on
Interface [chars] AuditSessionID [chars]
Explanation The authorization manager is failing over from the current authentication method to
another method. The first [chars] is the current authentication method, the second [chars] is the
client ID, the third [chars] is the interface, and the fourth [chars] is the session ID.
Explanation All available authentication methods have been tried for the client, but authentication has
failed. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the
session ID.
Recommended Action No action is required. If local authorization has been configured, the port is
authorized based on the local authorization method. Otherwise, authentication restarts according to
the configured reauthentication period.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-8 OL-9772-05
Explanation The results of the authentication. The first [chars] is the status of the authentication, the
second [chars] is the authentication method, the third [chars] is the client ID, the fourth [chars] is the
interface, and the fifth [chars] is the session ID.
BACKUP_INTERFACE Messages
Error Message BACKUP_INTERFACE-5-PREEMPT: Preempting interface [chars] in backup
pair ([chars], [chars]), preemption mode is [chars]
Explanation The switch is preempting the current forwarding interface in the backup interface pair.
The first [chars] is the number of the current forwarding interface. The second and third [chars] are
the names of the interfaces in the backup pair, and the fourth [chars] is the pre-preemption mode.
Explanation Flex Link VLAN load-balancing (VLB) detects a nontrunk port. [chars] is the interface
name.
BADTRANSCEIVER Messages
Error Message BADTRANSCEIVER, PHY, LOG_WARNING: An innapropriate transceiver has
been inserted in interface [chars].
Explanation A defective module is installed in the specified interface. [chars] is the interface.
Recommended Action Remove the transceiver. If it was purchased from Cisco, contact your Cisco
representative to have the transceiver replaced.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-9
BSPATCH Messages
Error Message BSPATCH-1-RELOAD: System will reboot to activate newly patched Boot
Loader.
Explanation The switch automatically reboots 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-7.
Explanation A boot loader patch 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-7.
Explanation The switch did not 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-10 OL-9772-05
CFGMGR Messages
Note These messages apply only to the Catalyst 3750-X and 3750-E switches.
Explanation The system is unsuccessfully trying to distribute the running configuration to the stack
member switches. [hex] is the bit representation of the switch 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-7.
Explanation The system is unsuccessfully trying to distribute the startup configuration file to the
stack member switches. [hex] is the bit representation of the switch 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-7.
Explanation An error occurred when the system was automatically applying the startup
configuration to the running configuration.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-11
Explanation A stack member switch attempted to write to the startup configuration file. Only the
stack master can write to the startup configuration file.
Explanation The switch type of the specified switch does not match the provisioned configuration
for its switch number. The default configuration is applied to this switch. [dec] is the stack member
number.
Explanation The configuration manager received a notification about adding a stack member switch
that already exists in the stack. [int] is the switch number.
Recommended Action If this message recurs, copy it exactly as it appears on the console or in the
system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug
Toolkit to look for similar reported problems. If you still require assistance, 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-7.
Explanation The stack master is temporarily unable to generate the stack running configuration
because another process is generating the configuration file.
Explanation The stack master cannot generate the stack running configuration because the
configuration file is too large.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-12 OL-9772-05
CLS_ACC Messages
Error Message CLS_ACC-2-CONFIG_NV_DATA: Express setup parameter committed. Default
port role will be applied
Explanation After the Express Setup settings are configured, the switch becomes a configured
switch. The default port roles are automatically applied to all ports. You can now manually modify
the port role configurations.
Explanation The switch enters consoleless access mode. [chars] is the name of the mode.
Explanation The switch exits from consoleless access mode. [chars] is the mode.
Explanation The system did not create the process to execute consoleless access.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error 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-7.
Explanation Pressing the Mode button for more than 5 seconds causes an unconfigured switch to go
into Express Setup mode. Pressing the Mode button for more than 5 seconds does not affect an
already configured switch. The switch does not go into Express Setup mode. [chars] is the mode.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-13
Explanation The switch is not correctly configured for consoleless access mode and cannot go into
that mode. [chars] is the mode.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Explanation The switch cannot find an interface to be the management interface for consoleless
access.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Explanation A request to configure the switch with consoleless access commands failed its memory
allocation. [chars] describes whether processor memory allocation or I/O memory allocation failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Error Message CLS_ACC-3-NOSOCKET: Fail to create DNS socket for consoleless access
Explanation The socket creation process failed. The switch cannot go into consoleless access mode
and stops.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-14 OL-9772-05
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-7.
Explanation The switch cannot find a VLAN with an ID from 2 to1000 to be the management VLAN
for consoleless access.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Error Message CLS_ACC-4-NO_HTTP_PAGE: Failed to locate HTTP page for the consoleless
access mode
Explanation The switch cannot find the HTTP page that appears in Express Setup mode because the
page is not on the flash memory.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Error Message CLS_ACC-4-UNEXPECTEDEVENT: Switch does not support or not ready for
consoleless access mode
Explanation The switch does not support or is not ready to go into the consoleless access mode.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-15
Error Message CLS_ACC-5-RSTIMG: User reset switch image to factory default image
under recovery mode
Explanation In recovery mode, the switch image resets to the default image.
Explanation An interface has been selected for Express Setup. [chars] is the name of the interface,
and [dec] is the number of the interface.
Explanation The switch assigned a VLAN to the management interface for consoleless access. [dec]
is the VLAN ID.
Error Message CLS_ACC-7-CONFIG: Save access intf config: if: [chars], port num:
[dec], vlan [dec], admin-down?:[dec]
Explanation The switch has saved the interface configuration. After the switch exits Express Setup
mode and the management interface is configured, the saved configuration takes effect. [chars] is
the name of the mode. The first [dec] is the port number, the second [dec] is the VLAN ID, and the
third [dec] is the port status.
Explanation The management interface has been configured, or its original configuration has been
restored. [chars] is the name of the configuration file.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-16 OL-9772-05
CMP Messages
Error Message CMP-4-MEM_CMPIP_ADDR_CONFLICT: Conflict with CMP IP address
[IP_address], Reissuing a new CMP IP address to member [dec]
Explanation The cluster commander found a conflict with the assigned CMP IP address of the
member. A new unique CMP IP address is assigned to the member. [dec] is the member number.
Recommended Action This is only a warning message. The commander has already assigned the
cluster member a new unique address. Clear any open TCP connections on the member by using
clear tcp privileged EXEC command.
Error Message CMP-5-ADD: The Device is added to the cluster (Cluster Name: [chars],
CMDR IP Address [IP_address]).
Explanation The device is added to the cluster. [chars] is the cluster name, and [IP_address] is the
Internet address of the command switch.
Explanation The active or standby command switch received a member configuration. [dec] is the
member number of the sender.
Error Message CMP-5-MGMT_VLAN_CHNG: The management vlan has been changed to [dec].
Explanation The management VLAN has changed. [dec] is the new management VLAN ID.
Explanation The number of cluster neighbors in the clustering neighbor update packet exceeds the
number of neighbors supported by the clustering module. The first [int] is the new number of
neighbors, and the second [int] the maximum number of neighbors.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-17
Error Message CMP-5-REMOVE: The Device is removed from the cluster (Cluster Name:
[chars]).
Explanation The device is removed from the cluster. [chars] is the cluster name.
DHCP_SNOOPING Messages
Error Message DHCP_SNOOPING-3-DHCP_SNOOPING_INTERNAL_ERROR: DHCP Snooping internal
error, [chars].
Explanation A software sanity check failed in the DHCP snooping process. [chars] is the error.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Explanation The DHCP snooping binding transfer process failed because of the specified reason for
failure. [chars] is the reason for the failure.
Explanation The DHCP snooping binding transfer process failed because of the specified reason for
failure. [dec] is the number of failures, and [chars] is the reason for the failure. This message is
rate-limited.
Explanation The switch detected a DHCP packet rate-limit violation on the specified interface and
put the interface in the error-disabled state. [dec] is the number of DCHP packets, and [chars] is the
interface.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-18 OL-9772-05
Explanation If the private VLAN feature is configured, the DHCP snooping configuration on the
primary VLAN automatically propagates to all the secondary VLANs. [dec] is the VLAN ID of the
secondary VLAN, and [chars] is the warning.
Explanation An IP source binding was configured on a VLAN that has not been configured yet. [dec]
is the VLAN.
Explanation If private VLANs are configured, the IP-source-guard filter on the primary VLAN
automatically propagates to all secondary VLANs. [dec] is the secondary VLAN, and [chars] is the
warning.
Explanation If the DHCP snooping database agent loads the DHCP snooping bindings and Network
Time Protocol (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.
Explanation The CPU is receiving DHCP at a higher rate than the DHCP snooping can process.
These DHCP packets are dropped to prevent a denial of service attack. [chars] is the warning.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-19
Explanation The DHCP snooping binding transfer process failed on a standby supervisor engine.
[chars] is the standby supervisor engine.
Explanation The DHCP binding transfer process succeeded. [chars] is the DCHP snooping database.
Explanation The specified number of bindings were ignored when the switch read the database file.
The bindings from the database file have MAC address and VLAN information that a configured
DHCP snooping binding already uses.
Explanation The specified number of bindings were ignored when the switch read the database file
because the interface in binding database is not available, the interface is a routed port, or the
interface is a DHCP snooping-trusted Layer 2 interface. [dec] is the number of bindings that the
switch ignores.
Explanation The specified number of bindings were ignored when the switch read the database file
because the DHCP lease expired. [dec] is the number of bindings.
Explanation The specified number of bindings were ignored when the switch read the database file
because the database read operation failed. [dec] is the number of bindings.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-20 OL-9772-05
Explanation The specified number of bindings were ignored when the switch read the database file
because the VLAN is no longer configured on the switch. [dec] is the number of bindings that the
switch ignores.
DOT1X Messages
Error Message DOT1X-4-MEM_UNAVAIL: Memory was not available to perform the 802.1X
action. AuditSessionID [chars]
Explanation The system memory is not sufficient to perform the 802.1x authentication. [chars] is the
session ID.
Recommended Action Restart the 802.1x process by entering the dot1x system-auth-control global
configuration command. If this message recurs, reload the device.
Explanation The 802.1x process cannot operate because of an internal system error.
Explanation 802.1x authentication could not be enabled on the EtherChannel port. An attempt to set
802.1x port control to auto or to force-unauthorized mode on the channel port, which is not
allowed, caused this condition.
Recommended Action Disable the EtherChannel on the interface, and then re-enable 802.1x
authentication.
Explanation 802.1x authentication could not be enabled on the dynamic-mode port. An attempt to
set 802.1x port-control to auto or force-unauthorized mode on a dynamic mode port, which is not
allowed, caused this condition.
Recommended Action Disable dynamic mode on the interface, and then try 802.1x authentication.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-21
Explanation 802.1x authentication could not be enabled on the voice VLAN-configured port. An
attempt to set 802.1x port control to auto or force-unauthorized mode on a voice VLAN-configured
port, which is not allowed, caused this condition.
Recommended Action Disable the voice VLAN on the interface, and then try 802.1x authentication.
Explanation 802.1x authentication could not be enabled on the protocol tunneling enabled port. This
condition was caused by trying to set 802.1x port-control to auto or force-unauthorized mode on a
protocol tunneling enabled port, which is not allowed.
Recommended Action Disable protocol tunnelling on the interface, and retry the 802.1x operation.
Explanation 802.1x authentication could not be enabled on a port with the same VLAN for the access
VLAN and the voice VLAN. An attempt to set 802.1x port control to auto or force-unauthorized
mode on the port, which is not allowed, caused this condition.
Recommended Action Change the voice VLAN or access VLAN on the interface, and retry the 802.1x
operation.
Explanation 802.1x authorization could not be enabled on the remote SPAN (RSPAN) VLAN port.
An attempt to set 802.1x port-control to auto or force-unauthorized mode on a port assigned to an
RSPAN VLAN, which is not allowed, caused this condition.
Recommended Action Disable RSPAN on the VLAN, and retry the 802.1x operation.
Explanation 802.1x and SPAN destination ports are mutually exclusive. [chars] is the port.
Recommended Action Disable the SPAN destination port configuration, and then reconfigure 802.1x
authentication on the port.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-22 OL-9772-05
Explanation 802.1x authentication could not be enabled on the trunk port. An attempt to set 802.1x
port control to auto or force-unauthorized mode on a trunk port, which is not allowed, caused this
condition.
Recommended Action Disable trunking on the interface, and re-enable 802.1x authentication on the
port.
Explanation The specified VLAN is out of range and cannot be assiged as an 802.1x port. [dec] is
the VLAN, and [chars] is the 802.1x port.
Explanation The authentication was unsuccessful. The first [chars] is the client ID, the second
[chars] is the interface, and the third [chars] is the session ID.
Explanation The 802.1x interface parameter is out of the specified range or is invalid. [chars] is the
interface.
Recommended Action See the command-line help string for the valid 802.1x parameters.
Explanation Authentication using 802.1x is not allowed for zero, broadcast, and multicast source
MAC addresses. [enet] is the invalid MAC address.
Recommended Action Connect an 802.1x supported host to the 802.1x enabled port.
Explanation The authentication result was overridden. The first [chars] is the client ID, the second
[chars] is the interface, and the third [chars] is the session ID.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-23
Explanation Authentication was successful. The first [chars] is the client ID, the second [chars] is
the interface, and the third [chars] is the session ID.
DOT1X_SWITCH Messages
Error Message DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on
[chars] AuditSessionID [chars]
Explanation The client MAC address could not be added to the MAC address table because the
hardware memory is full or because the address is a secure address on another port. [enet] is the
client MAC address, the first [chars] is the interface, and the second [chars] is the session ID.
Recommended Action If the hardware memory is full, remove some of the dynamic MAC addresses.
If the client address is on another port, remove it from that port.
Explanation An attempt was made to assign a primary VLAN to an 802.1x port, which is not allowed.
[dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Explanation An attempt was made to assign a nonsecondary VLAN to a private VLAN host 802.1x
port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Change the port mode so that it is no longer a private VLAN host port, or use
a valid secondary VLAN.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-24 OL-9772-05
Explanation An attempt was made to assign a private VLAN whose primary VLAN does not exist or
is shut down. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Make sure that the primary VLAN exists and is not shut down. Verify that the
private VLAN is associated with a primary VLAN.
Recommended Action Make sure a VLAN with the specified name/ID exists on the switch.
Explanation An attempt was made to assign a secondary VLAN to a port that is not a private VLAN
host port, which is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars]
is the session ID.
Recommended Action Change the port mode 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 802.1x port that is configured as a
Switched Port Analyzer (SPAN) destination port. [dec] is the VLAN, the first [chars] is the port, and
the second [chars] is the session ID.
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 (MDA) host mode cannot start when the configured data
VLAN on a port is the same as the voice VLAN. [chars] is the port session ID.
Recommended Action Change either the voice VLAN or the access VLAN on the port so that they are
not the same.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-25
Explanation An attempt was made to assign a data VLAN to an 802.1x port that is the same as the
voice VLAN. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Change either the voice VLAN or the 802.1x-assigned VLAN on the port so
that they are not the same.
Explanation An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified
is used internally and cannot be assigned to this port. [dec] is the VLAN, the first [chars] is the port,
and the second [chars] is the session ID.
Explanation An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified
is out of range. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session
ID.
Explanation An attempt was made to assign a VLAN to an 802.1x port, but the VLAN was not found
in the VLAN Trunking Protocol (VTP) database. [dec] is the VLAN, the first [chars] is the port, and
the second [chars] is the session ID.
Recommended Action Make sure that the VLAN exists and is not shut down, or use another VLAN.
Explanation An attempt was made to assign a VLAN to a routed 802.1x port, which is not allowed.
[dec] is the VLAN, and [chars] is the port.
Recommended Action Change the port mode so that it is no longer a routed port, or change the
configuration so that no VLAN is assigned.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-26 OL-9772-05
Explanation An attempt was made to assign a VLAN to a supplicant on a routed port, which is not
allowed. [dec] is the VLAN ID, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Either disable the VLAN assignment, or change the port type to a nonrouted
port.
Explanation An attempt was made to assign a VLAN to a promiscuous 802.1x port, which is not
allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Change the port mode so that it is not promiscuous, or reconfigure the port so
that no VLAN is assigned to it.
Explanation An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified
is a reserved VLAN and cannot be assigned to this port. [dec] is the VLAN, the first [chars] is the
port, and the second [chars] is the session ID.
Explanation Remote SPAN should not be enabled on a VLAN with 802.1x authentication. [dec] is the
VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Either disable remote SPAN on the VLAN, or disable 802.1x on all the ports
in this VLAN.
DTP Messages
Error Message DTP-4-MEM_UNAVAIL: Memory was not available to perform the trunk
negotiation action.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-27
Explanation A timer used by the trunking protocol unexpectedly expired. [chars] is the trunked
interface.
Recommended Action This problem is corrected internally and has no long-term ramifications.
However, if more problems with trunking occur, reload the switch by using the reload privileged
EXEC command.
Explanation The system cannot negotiate trunks because an internal operation generated an
unexpected error.
Recommended Action Reload the switch by using the reload privileged EXEC command.
Explanation The two ports in the trunk negotiation belong to different VTP domains. Trunking can
be configured only when the ports belong to the same VTP domain. [chars] is the port number.
Recommended Action Ensure that the ports in the trunk negotiation belong to the same VTP domain.
Explanation One end of the trunk link is configured as on with ISL encapsulation and that the other
end is configured as on with 802.1Q encapsulation. [chars] is the interface.
Recommended Action This configuration is illegal and will not establish a trunk between two
switches. You must change the encapsulation type so that both ends of the trunk match.
Explanation The interface changed from a trunk port to an access port. [chars] is the interface that
changed.
Error Message DTP-5-TRUNKPORTCHG: Port [chars] has changed from [chars] trunk to
[chars] trunk.
Explanation The encapsulation type of the trunk port has changed. The first [chars] is the interface,
the second [chars] is the original encapsulation type, and the third [chars] is the new encapsulation
type.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-28 OL-9772-05
Explanation The interface has changed from an access port to a trunk port. The first [chars] is the
interface, and the second [chars] is the encapsulation type.
DWL Messages
Error Message DWL-3-LOOP_BACK_DETECTED: Loop-back detected on [chars].
Explanation There is a loopback on the specified port that might be caused by a Token-Ring Type-1
cable connected to the port or a misconfiguration in the network. [chars] is the port.
Recommended Action Correct the problem that is causing the loopback condition. Then enter the
shutdown and the no shutdown interface configuration commands.
EC Messages
Error Message EC-4-NOMEM: Not enough memory available for [chars].
Explanation Either the LACP or the PAgP EtherChannel could not get the memory it needed to
initialize the required data structures. [chars] is the data structure name.
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-7.
Explanation The listed interface joined the specified EtherChannel. The first [chars] is the physical
interface, and the second [chars] is the EtherChannel interface.
Explanation A new aggregator cannot be allocated in the group. [dec] is the affected group.
Recommended Action Change the port attributes of the ports in the group so that they match and join
the same aggregator.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-29
Explanation The aggregation port is down. The port remains standalone until the aggregation port is
up. The first [chars] is the EtherChannel, and 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 The interface has different interface attributes than the EtherChannel or the other ports
in the EtherChannel. For the interface to join the bundle (EtherChannel), change the interface
attributes to match the EtherChannel attributes. The first [chars] is the interface to be bundled, the
second [chars] is the physical interface (a switch port or a routed port) that is already in the bundle,
and the third [chars] is the reason for the incompatibility.
Recommended Action Change the interface attributes to match the EtherChannel attributes.
Explanation The port has different port attributes than the port channel or ports within the port
channel. [chars] is the incompatible port, [dec] is the channel group number, and the last [chars] is
the reason.
Recommended Action For the port to join the EtherChannel bundle, change the port attributes so that
they match the port.
Explanation A port was not operational because its attributes were different from those of the port
channel or ports within the port channel. The system has detected that the attributes of the port now
match the port-channel attributes. [chars] is the affected port.
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.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-30 OL-9772-05
Error Message EC-5-ERRPROT: Channel protocol mismatch for interface [chars] in group
[dec]: the interface can not be added to the channel group.
Explanation The interface cannot be added to the channel group with the specified mode. [chars] is
the interface, and [dec] is the channel group.
Recommended Action Change the channel group or the mode for the interface.
Error Message EC-5-ERRPROT2: Command rejected: the interface [chars] is already part
of a channel with a different type of protocol enabled.
Explanation The interface cannot be selected for the specified protocol because it is already part of
a channel with a different protocol. [chars] is the interface.
Error Message EC-5-ERRPROT3: Command rejected: the interface [chars] is already part
of a channel.
Explanation The interface cannot be unselected for the specified protocol because it is already part
of a channel group. [chars] is the interface.
Error Message EC-5-L3DONTBNDL1: [chars] suspended: PAgP not enabled on the remote
port.
Explanation PAgP is enabled on the Layer 3 interface but the partner port is not enabled for PAgP.
In this mode, the port is placed in a suspended state. [chars] is the Layer 3 interface.
Recommended Action Enable PAgP on the remote side by using the channel-group interface
configuration command.
Error Message EC-5-L3DONTBNDL2: [chars] suspended: LACP currently not enabled on the
remote port.
Explanation LACP is enabled on a Layer 3 interface but is not enabled on the partner port. In this
mode, the port is put in a suspended state. [chars] is the interface name.
Error Message EC-5-L3DONTBNDL3: [chars] suspended: LACP not enabled on the remote
port.
Explanation LACP is enabled on a Layer 3 interface but the remote port does not have LACP
enabled. In this mode, the local port is put in a suspended state. [chars] is the interface name.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-31
Explanation 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.
Explanation PAgP is not included in the Cisco IOS image and the EtherChannel mode cannot be set
to desirable or auto.
Recommended Action Obtain an image with PAgP included, or set the mode to on by using the
channel-group channel-group-number mode on interface configuration command.
Explanation The administrative state of the port is controlled by the administrative state of its
aggregate port. If the administrative state of the aggregate port is down, the administrative state of
the port is also forced to be down. [chars] is the physical interface.
Recommended Action Enter the no shutdown interface configuration command on the aggregate port
to activate the aggregation port.
Error Message EC-5-STAYDOWN: [chars] will remain down as its port-channel [chars] is
admin-down.
Explanation The administrative state of the aggregation port overrides that of the affected port. If the
aggregation port is administratively down, all ports in the aggregation port are forced to be
administratively down. The first [chars] is the physical interface, and the second [chars] is the
EtherChannel.
Recommended Action Enter the no shutdown interface configuration command on the aggregation
port to activate (unshut) the aggregation port.
Error Message EC-5-STAYDOWN: no-shut not allowed on [chars]. Module [dec] not online.
Recommended Action No action is required. Wait until the module is online to find out the
port-channel setting of the EtherChannel.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-32 OL-9772-05
Explanation The listed interface left the specified EtherChannel. The first [chars] is the physical
interface, which can be a switch port or a routed port, and the second [chars] is the EtherChannel.
Error Message EC-5-UNSUITABLE: [chars] will not join any port-channel, [chars].
Explanation One of the interfaces cannot join the EtherChannel because it is configured for PortFast,
as a VLAN Membership Policy Server (VMPS), for 802.1x, as a voice VLAN, or as a SPAN
destination port. All of these are illegal configurations for EtherChannels. The first [chars] is the
interface name, and the second [chars] describes the details of the illegal configuration.
Recommended Action Remove the illegal configuration and reconfigure the port.
EPM Messages
Error Message EPM-6-AUTH_ACL: POLICY [chars]| EVENT [chars]
Explanation The switch has sent or received a download request for a downloadable ACL (dACL).
The first [chars] is the dACL policy. The second [chars] is the event.
ETHCNTR Messages
Error Message ETHCNTR-3-HALF_DUX_COLLISION_EXCEED_THRESHOLD: Collision at [chars]
exceed threshold. Consider as loop-back.
Explanation The collisions at a half-duplex port exceeded the threshold, and the port is treated as a
loopback. On switches that support Power over Ethernet (PoE), this message might be displayed
when a device that can be powered by either a PoE switch port or by AC power is not being powered
by an external AC power source and is connected to a port that has been configured with the power
inline never interface configuration command. [chars] is the port where the threshold was exceeded.
Recommended Action On switches that support PoE, remove the device or configure the port by
entering the power inline auto, shutdown, and no shutdown interface configuration commands.
No action is required on non-PoE switches. The port is error disabled until the problem is resolved.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-33
Explanation 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 CSCea46385 for more
information.
Explanation There are too many VLANs and routed ports (if the switch supports routed ports)
configured. [chars] is the short interface name, such as Gi1/0/1 on a Catalyst 3750-E switch, or the
VLAN name, such as VLAN0002.
Recommended Action Reduce the total number of VLANs and routed ports to less than 1023. To
preserve configuration and connections across reboots, save the configuration.
Explanation A switch that is being added to the stack does not support the forwarding of IP Version 4
(IPv4) and IP Version 6 (IPv6) frames with Subnetwork Access Protocol (SNAP) encapsulation. If
this occurs, forwarding of IPv4 and IPv6 frames is disabled in the switch stack. [dec] is the stack
member number.
Recommended Action Replace the stack member with a switch that supports forwarding of IPv4 and
IPv6 frames with SNAP encapsulation.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-34 OL-9772-05
EXPRESS_SETUP Messages
Note For Express Setup with the Ethernet management port, see the CLS_ACC Messages section.
Explanation The system cannot reset the configuration. [chars] is a text string that explains why the
reset failed. For example, error renaming config file, error removing config file, or error
removing private config file.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Explanation The configuration is reset. [chars] is a text message that clarifies the reset event, such
as The configuration is reset and the system will now reboot.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-35
FRNTEND_CTRLR Messages
Note These messages apply only to the Catalyst 3750-X and 3750-E switches.
Explanation There are too many messages in the queue between the front-end controller and the
switch software.
Recommended Action Reset the switch. If the problem is not resolved, contact your Cisco technical
support representative because there might be a problem with the switch.
Explanation The front-end controller that controls the LEDs, the PoE features, and the fan-control
features is now inactive on the port controlled by the front-end controller. This does not affect the
traffic on the port. [dec] is the controller number.
Recommended Action Reset the switch. If the problem is not resolved, contact your Cisco technical
support representative because there might be a problem with the switch.
GBIC_SECURITY Messages
Note The Catalyst 3750-X, 3750-E, 3560-X, and 3560-E switches support SFP modules and do not support
GBIC modules. Although the error message text refers to GBIC interfaces and modules, the messages
from the switches actually refer to the SFP and 10-Gigabit Ethernet module interfaces and modules.
Explanation The GBIC in the specified port has invalid EEPROM data. [chars] is the port in which
the GBIC is inserted.
Explanation An error occurred while the switch was reading the GBIC type from the EEPROM.
[chars] is the port in which the GBIC is inserted.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-36 OL-9772-05
Explanation The GBIC in the specified port has invalid EEPROM data. [chars] is the port in which
the GBIC is inserted.
Explanation The system could not allocate resources or had some other problem during the setup for
the specified SFP module interface. [chars] is the interface in which the SFP module is installed.
Recommended Action Reload the switch by using the reload privileged EXEC command. If the
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. 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-7.
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.
Explanation The 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.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-37
GBIC_SECURITY_CRYPT Messages
Note The Catalyst 3750-X, 3750-E, 3560-X, and 3560-E switches support SFP and 10-Gigabit Ethernet
modules but do not support GBIC modules. Although the error message text refers to GBIC interfaces
and modules, the messages from the switches actually refer to the SFP and 10-Gigabit Ethernet module
interfaces and modules.
Explanation The 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.
Explanation The 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.
Explanation The SFP module was identified as a Cisco SFP module, but it does not have a valid
cyclic redundancy check (CRC) in the EEPROM data. [chars] is the port.
Recommended Action Ensure that the Cisco IOS software running on the switch supports the SFP
module. You might need to upgrade your software. Even if the SFP module is unrecognized by the
switch, the SFP module might still operate properly but have limited functionality.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-38 OL-9772-05
GBIC_SECURITY_UNIQUE Messages
Note The Catalyst 3750-X, 3750-E, 3560-X, and 3560-E switches support SFP and 10-Gigabit Ethernet
modules and do not support GBIC modules. Although the error message text refers to GBIC interfaces
and modules, the messages from the switches actually refer to the SFP and 10-Gigabit Ethernet module
interfaces and modules.
Explanation The SFP module was identified as a Cisco GBIC or SFP module, but its vendor ID and
serial number match that of another interface on the system. The first [dec]/[dec] is the interface of
the duplicate GBIC or SPF module, and the second [dec]/[dec] is the interface of the existing
module.
Recommended Action Cisco GBIC or SFP modules are assigned unique serial numbers. Verify that
the module was obtained from Cisco or from a supported vendor.
Explanation The SFP module was identified as a Cisco SFP module, but its serial number matches
that of another interface on the system. [dec]/[dec] is the interface in which the duplicate module is
installed.
Recommended Action Cisco SFP modules are assigned unique serial numbers. Verify that the module
was obtained from Cisco or from a supported vendor.
HARDWARE Messages
Error Message HARDWARE-2-FAN_ERROR: Fan [chars] Failure
Explanation The switch fan is not working. [chars] is the fan name.
Recommended Action This is a hardware failure. The fan might recover automatically. If the fan
failure persists, Copy the message exactly as it appears on the console or in the system log. Research
and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for
similar reported problems. If you still require assistance, open a case with the TAC, or contact your
Cisco technical support representative, and provide the representative with the gathered information.
For more information about these online tools and about contacting Cisco, see the “Error Message
Traceback Reports” section on page 1-7
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-39
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-7.
Explanation The temperature sensor valve inside the switch reached the warning threshold. The
switch can function normally until the temperature reaches the critical threshold.
Recommended Action The external temperature is high. Reduce the temperature in the room.
Explanation The port ASIC number is invalid. [dec] is the port 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.
Explanation The index into the hardware table is out-of-range. [dec] is the index value.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Explanation The interrupt ID used in a port ASIC is invalid. [dec] is the interrupt number.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-40 OL-9772-05
Explanation The port number is out of range. [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.
Explanation The temperature sensor is not functioning, and the switch temperature behavior cannot
be determined.
Recommended Action Ensure that the ambient temperature is not too high. If the message appears
again, replace the component.
Explanation The statistics ID used is out of range. The statistics supported by the port ASIC are
identified by an ID. [dec] is the statistics ID.
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-7.
Recommended Action Make sure the fan is completely inserted. If the fan is removable, remove and
replace it into the switch. If the message appears again after insertion, replace the fan.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-41
HLFM Messages
Error Message HLFM-3-MACFREE_ERROR: MAC address [enet], vlan [dec] is still
referenced; cannot free.
Explanation An attempt was made to free a MAC address before releasing all references to it. [enet]
is the MAC address, and [dec] is the VLAN ID.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Explanation 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 “Error
Message Traceback Reports” section on page 1-7.
Error Message HLFM-3-MOD_SD: Failed to modify Station Descriptor with index [dec],
vlan [dec], di [dec], error [dec], mad [dec], ref-count [dec].
Explanation The forwarding manager tried to modify a station descriptor that is no longer in use or
is invalid. The first [dec] is the station index, the second [dec] is the VLAN ID, the third [dec] is the
destination index, the fourth [dec] is the error code, the fifth [dec] is the MAC address descriptor,
and the sixth [dec] is the ref-count for this MAC address descriptor.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Error Message HLFM-3-SEND_FAIL: Failed to send RPC message, req [dec], [chars].
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-42 OL-9772-05
Explanation There is a local resource error or that too many outgoing messages are queued for the
message class. [dec] is the RPC request number, and [chars] is an optional comment.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
HPSECURE Messages
Error Message HPSECURE-6-ADDR_REMOVED: Address [enet]:[dec] on port [chars] cannot
be added on switch [dec] and has been removed.
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Explanation At least one switch in the stack could not add the MAC address due to a resource failure,
and the MAC address has been deleted from all the switches in the stack. [enet] is the MAC address,
the first [dec] is the VLAN to which the MAC address is assigned, [chars] is the interface, and the
second [dec] is the stack member number.
HULC_LICENSE Messages
Error Message HULC_LICENSE-1-LICENSE_REGISTER_FAILED: [chars] - rc = [dec]
Explanation The licensing initialization failed. [chars] explains what part of the license registration
failed, and [dec] is the type of license initialization 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.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-43
IFMGR Messages
Error Message IFMGR-3-IFINDEX_PERSIST_ENTRY_CORRUPT: [chars] seems to be corrupted.
Trying to read [dec] size
Explanation The ifIndex table is corrupted. [chars] is the path to the IfIndex file, and [dec] is the
number of bytes that was being read from the ifIndex table when the corruption was detected.
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.
IGMP_QUERIER Messages
Error Message IGMP_QUERIER-4-NO_IP_ADDR_CFG: The IGMP querier cannot send out
General Query messages in VLAN [dec] because there is no IP address configured on
the system.
Explanation An IP address for the IGMP querier was not configured at either the global or per-VLAN
level. [dec] is the VLAN ID.
Explanation Protocol-Independent Multicast (PIM) was detected on the switch virtual interface
(SVI). Do not enable the IGMP querier when PIM is enabled on the SVI. [dec] is the VLAN ID.
Explanation IGMP snooping is disabled on this VLAN. Do not enable the IGMP querier when IGMP
snooping is disabled. [dec] is the VLAN IDs.
Recommended Action Confirm that IGMP snooping is enabled both globally and on the VLAN.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-44 OL-9772-05
Explanation PIM is disabled on the SVI, and the IGMP querier function is now enabled. [dec] is the
VLAN ID.
Explanation IGMP snooping was enabled. As a result, the IGMP querier function is now enabled.
[dec] is the VLAN ID.
ILET Messages
Error Message ILET-1-AUTHENTICATION_FAIL: This Switch may not have been manufactured
by Cisco or with Cisco’s authorization. This product may contain software that
was copied in violation of Cisco’s license terms. If your use of this product is
the cause of a support issue, Cisco may deny operation of the product, support
under your warranty or under a Cisco technical support program such as Smartnet.
Please contact Cisco’s Technical Assistance Center for more information.
Explanation A license authentication failure occurred for a component that was installed in the
switch. [chars] is the component.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-45
ILPOWER Messages
Error Message ILPOWER-3-CONTROLLER_ERR: Controller error, Controller number [dec]:
[chars].
Explanation An error reported or caused by the PoE controller is detected. [dec] is the controller
instance, which is 0 to 5 on a 24-port PoE switch and 0 to 11 on a 48-port PoE switch. [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 “Error
Message Traceback Reports” section on page 1-7.
Explanation An interface error is detected between the PoE controller and the system. The first
[chars] is the interface. The second [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 “Error
Message Traceback Reports” section on page 1-7.
Recommended Action Enter the shutdown and no shutdown interface configuration commands on
the affected interfaces. Upgrade to Cisco IOS Release12.1(14)EA1 or later, which provides an
electrostatic discharge (ESD) recovery mechanism.
Explanation An error reported or caused by the Power over Ethernet (PoE) controller is detected
during power-on self-test (POST).
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
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-46 OL-9772-05
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-7.
Explanation A software check failed during PoE processing. The first [chars] is the interface. The
second [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
“Error Message Traceback Reports” section on page 1-7.
Explanation The interface is shut down because it is consuming more than the maximum power
allocation. [chars] is the port, and [dec] is the maximum configured power.
Recommended Action Ensure that the cutoff-power value is configured for the device and is based on
the powered-device specifications or ratings. We recommend configuring the cutoff power to a value
higher than the required power for the device.
Explanation The powered device is drawing more power than the maximum power configured on the
interface. The power budgeting calculations determined by the switch are no longer valid, and you
might risk overloading the switch. [chars] is the interface, and [dec] is the maximum configured
power.
Recommended Action Ensure that the correct power is budgeted for this interface based on the
powered-device electrical specifications or ratings. We recommend that you change the cutoff power
value.
Explanation The device connected to the PoE interface is consuming less power than the maximum
power allocation. [chars] is the interface. The first [dec] is the power being consumed, and the
second [dec] is the maximum allocated power value.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-47
Explanation The powered device is not connected to the switch, or the connected powered device is
being powered by an external AC power source. The switch is no longer providing power to the port.
[chars] is the interface.
Explanation Inline power is shut down because CDP consumption power on this PoE port is greater
than the allocation power, the hardware interface limit, the user-configured maximum power, or the
available power on this switch. [chars] is the interface.
Explanation There is not enough power remaining in the switch to supply to the PoE port. [chars] is
the interface.
Explanation The powered device has an invalid IEEE class so that the switch is not providing power
to the device. [chars] is the interface. [dec] is the IEEE class number.
Explanation The powered device is no longer connected to the switch, or the connected powered
device is being powered by an external AC power source. The switch is no longer providing power
on the interface. [chars] is the interface.
Explanation The power policing current or voltage value is invalid. [chars] is the interface. The first
[dec] is the power policing limit (cutoff value in mW), the second [dec] is the power usage in mA,
and the third [dec] is the power usage in mV.
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
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-48 OL-9772-05
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-7.
Explanation The switch can provide power to the interface. [chars] is the interface.
Explanation The power-monitoring voltage or current value is invalid. [chars] is the interface. The
first [dec] is the power-monitoring cutoff value, the second [dec] is the real-time power consumption
in mA, and the third [dec] is the real-time power consumption in mV.
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-7.
Explanation The switch has detected a connected powered device. The first [chars] is the interface.
The second [chars] is the Cisco pre-standard powered device or the IEEE-compliant powered device.
IMAGEMGR Messages
Note These messages apply only to the Catalyst 3750-X and 3750-E switches.
Explanation Systems with incompatible software have been detected in the switch stack.
Auto-advise software informs you when not all switches in the stack are running the same software
version. The stack master then attempts to upgrade all switches running different versions to the
version that the master is running. The stack finds out whether or not software is available to be
copied to the incompatible systems and if so, advises you how to copy it. Otherwise, the system
informs you that the software on the switch stack needs to be updated. [bits [hex]] is the bit
representation of the switch number.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-49
Explanation A line of output from the auto-advise-software process is being displayed. [chars] is a
text message reporting status of the upgrade process.
Explanation Systems with incompatible software have been detected in the switch stack. The stack
now finds out whether or not software is available to be copied to the incompatible systems and
whether or not it is appropriate to automatically copy the software. [bits [hex]] is the bit
representation of the switch number.
Explanation A line of output from the auto-copy-software process appears. [chars] is a text message
reporting status of the upgrade process.
Explanation Systems with incompatible software have been detected in the switch stack. The stack
now attempts to download software from a previously configured location and to install it to make
the systems compatible. [bits [hex]] is the bit representation of the switch number.
Explanation A line of output from the auto-download-software process appears [chars] is a text
message reporting the status of the upgrade process.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-50 OL-9772-05
IP_DEVICE_TRACKING Messages
Error Message IP_DEVICE_TRACKING-4-TABLE_LOCK_FAILED: Table already locked by
process-id [dec]([chars])
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Explanation The IP device tracking table could not be updated due to a lock held by another process.
[dec] is the process number, and [chars] is the process.
MAC_MOVE Messages
Error Message MAC_MOVE-4-NOTIF: Host [enet] in vlan [dec] is flapping between port
[chars] and port [chars].
Explanation The host is moving between the specified ports. [enet] is the Ethernet address of the
host, [dec] is the VLAN ID, the first [chars] is the first port, and the second [chars] is the second port.
PAGP 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.
Explanation PAgP received a new active ID on the specified interface and all virtual switches moved
into a dual-active scenario. As a result, the interface informed the virtual switches of this, which
caused one switch to go into recovery mode. [chars] is the interface, the first [enet] is the new active
ID, and the second [enet] is the ID that it replaces.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-51
Explanation The switch could not add a function to the registry. [chars] is the registry name.
PHY Messages
Error Message PHY-4-BADTRANSCEIVER: An inappropriate transceiver has been inserted
in interface [chars].
Recommended Action Remove the transceiver. If the transceiver is a Cisco device, contact your Cisco
technical support representative.
Error Message PHY-4-CHECK_SUM_FAILED: SFP EEPROM data check sum failed for SFP
interface [chars].
Explanation The SFP module was identified as a Cisco SFP module, but the system cannot read the
vendor data information to verify whether it is correct. [chars] is the interface in which the SFP
module is installed.
Recommended Action Remove and then reinsert the SFP module. If it fails again with the same error
message, the SFP module might be defective.
Error Message PHY-4-EXCESSIVE_ERRORS: Excessive FCS, data, or idle word errors found
on interface [chars].
Explanation The system detected excessive frame check sequence (FCS), data word, or idle word
errors on the specified interface. [chars] is the interface.
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.
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
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-52 OL-9772-05
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-7.
Explanation The SFP module type is not supported on this switch. [chars] is the interface.
Recommended Action Remove the unsupported SFP module, and get a supported SFP module.
Explanation The 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 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-7.
Explanation The SFP module was identified as an 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.
PIMSN Messages
Error Message PIMSN-6-IGMPSN_GLOBAL: PIM Snooping global runtime mode [chars] due to
IGMP Snooping [chars].
Explanation 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.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-53
Error Message PIMSN-6-IGMPSN_VLAN: PIM Snooping runtime mode on vlan [dec] [chars]
due to IGMP Snooping [chars].
Explanation 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.
PLATFORM Messages
Error Message PLATFORM-1-CRASHED: [chars].
Explanation The system is trying 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 “Error
Message Traceback Reports” section on page 1-7.
Explanation There are too many VLANs and routed ports. [chars] is the short interface name, such
as Gi1/0/1, or the VLAN name, such as VLAN0002.
Recommended Action Reduce the total number of VLANs and routed ports to be less than 1023. To
preserve configurations and connections across reboots, save the configuration.
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Recommended Action Make sure that all stack members are running compatible software images. If the
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. 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-54 OL-9772-05
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Explanation The stack master has received a set-password-recovery HRPC message. These messages
should be received only on stack member switches. [dec] is the switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Explanation A stack member switch has received a get-password-recovery HRPC message. These
messages should only be received by the stack master. [dec] is the switch.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Explanation The switch detected an unsupported field replaceable unit (FRU). The first [chars] is the
unsupported FRU. The second [chars] is the slot.
Note This message applies only to the Catalyst 3750-X and 3560-X switches.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-55
PLATFORM_ENV Messages
Error Message PLATFORM_ENV-1-FAN: Faulty fan detected.
Recommended Action If the message appears again, immediately replace the switch fan.
Recommended Action If the fan is removable, remove and replace it into the switch. If the message
appears again after insertion, replace the fan.
Explanation The switch did not access the power supply due to a communication problem. [chars] is
the error message.
Recommended Action This problem could be transient. If the message appears again, replace the
power supply.
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-7.
Explanation The specified signal of the power supply is faulty. [chars] is the signal value (12V or
PoE).
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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-56 OL-9772-05
Explanation The specified signal of the power supply has been restored. [chars] is the signal value
(12V or PoE).
Explanation The internal power supply does not provide enough power for the Power over Ethernet
(PoE) ports.
Recommended Action Substitute a power supply that can provide enough power for the PoE ports.
Explanation An RPS 2300 communication error is detected. [chars] is 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 “Error
Message Traceback Reports” section on page 1-7.
Explanation An RPS 2300 fan failure is detected. [chars] is the error message.
Recommended Action Disconnect any switches connected to the RPS 2300, and immediately replace
the fan.
Explanation An RPS 2300 over current condition is detected. [chars] is the error message.
Recommended Action Disconnect the switches from the RPS 2300 that is not providing power to
them.
Explanation An RPS 2300 power supply fan failure is detected. [chars] is the power supply ID (A or
B).
Recommended Action Disconnect any switches connected to the RPS 2300, and immediately replace
the power supply.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-57
Explanation The power supplies in the RPS 2300 are incompatible. [chars] is the error message.
Recommended Action Remove one of the power supplies, or use compatible power supplies.
Explanation The specified RPS 2300 has a faulty signal. The first [chars] is the signal value (12V or
PoE), and the second [chars] is the power supply ID (A or B).
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-7.
Explanation The power supply in the RPS 2300 has reached the critical threshold. It cannot function
normally.
Recommended Action The external temperature is too high. Immediately reduce the room
temperature.
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-7.
Explanation The RPS 2300 system power state changed to bad. The RPS 2300 might not be able to
provide power to the switch. [chars] is the error message.
Recommended Action Check the power supplies in the RPS 2300. If the message appears again,
replace the power supplies.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-58 OL-9772-05
Explanation The RPS 2300 system power state changed to good. [chars] is the error message.
Explanation The temperature sensor value in the RPS 2300 has reached the critical threshold. It
cannot function normally.
Recommended Action The external temperature is too high. Immediately reduce the room
temperature in the room.
Recommended Action Ensure that ambient temperature is not too high. If the message appears again,
check the switch temperature by entering the show env all privileged EXEC command.
Explanation The temperature sensor value in the RPS 2300 has reached the warning threshold. The
RPS can function normally until the temperature reaches the critical threshold.
Recommended Action The external temperature is high. Reduce the room temperature.
Explanation The RPS 2300 is continuing to back up the switch even though the command on the
switch instructs it to no longer provide power to the switch. [chars] is the error message.
Explanation The RPS 2300 state changed to standby. It can no longer provide power to the switch.
[chars] is the error message.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-59
Explanation The RPS 2300 is continuing to back up the switch even though the command on the
switch instructs the RPS 2300 to no longer supply power to the switch. [chars] is the error message.
Recommended Action This problem could be transient. If the message appears again, disconnect and
then reconnect the switch.
Explanation An RPS 2300 power-on self-test (POST) failure is detected. [chars] is the error message.
Explanation The temperature sensor value in the RPS 2300 is within the normal limit.
Explanation A power supply is inserted or removed. [chars] is the power supply status that can be
either inserted or removed.
Explanation The RPS 2300 state is changed. [chars] is the state (added or removed).
Explanation This message has information about the RPS 2300. [chars] is the information (inserted,
is in active mode, or removed).
Explanation A power supply is inserted in the RPS 2300. [chars] is the system message.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-60 OL-9772-05
Explanation A power supply is removed from the RPS 2300. [chars] is the system message.
Explanation A power supply wa inserted or removed. [dec] is the power supply. [chars] is the power
supply status that can be either inserted, removed, powered on, or powered off.
PLATFORM_FBM Messages
Error Message PLATFORM_FBM-4-RECOVERED: Fallback bridging recovered from resource
crunch.
Explanation Fallback bridging could not be properly configured. The most likely cause is a
hardware-full condition on at least one stack member. [dec] is the bridge group.
Recommended Action The switch automatically recovers, but this could take some time. For an
immediate recovery, use the shutdown interface configuration command to disable the port and to
stop the traffic flow to the switch. Use the clear mac-address-table dynamic privileged EXEC
command to remove all MAC addresses from the hardware. Use the no shutdown interface
configuration command to re-enable the port.
PLATFORM_HCEF Messages
Error Message PLATFORM_HCEF-3-ADJ: [chars]
Explanation An unsupported feature has been configured on a switch running Cisco IOS Release
12.2(25)SE. [chars] is the error message.
Recommended Action Determine if a generic routing encapsulation (GRE) tunnel or the ip cef
accounting global configuration command are configured. Only Distance Vector Multicast Routing
Protocol (DVMRP) tunnels are supported. If the GRE tunnel is configured, remove the tunnel, or
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-61
upgrade the switch software to a Cisco IOS release when the GRE feature is needed. If the ip cef
accounting command is configured, remove it by using the no ip cef accounting global
configuration command.
Note Cisco IOS Release12.2(25)SEB2 does not support the ip cef accounting command.
PLATFORM_HPLM Messages
Error Message PLATFORM_HPLM-3-ERROR: Failed Alloc for xaction record label move from
[dec] to [dec].
Explanation An internal resource allocation error occurred during the label compaction process. The
first [dec] is the previous label, and the second [dec] is the new label.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative, and provide the representative with the
gathered information.
PLATFORM_IPC Messages
Error Message PLATFORM_IPC-3-COMMON: [chars].
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-62 OL-9772-05
Explanation There has been an IPC failure. [chars] describes the error message.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Explanation There has been an IPC failure on the stack master. [chars] describes the error message.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Explanation An internal IPC application error occurred when an IPC message was sent that exceeded
the maximum length. [chars] describes the error message.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Explanation There has been an IPC failure on a stack member switch. [chars] describes the error
message.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, open a case with the TAC, or
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-63
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-7.
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Explanation There has been an IPC failure in the stack. [chars] describes the error message.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
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-7.
PLATFORM_IPv6_UCAST Messages
Error Message PLATFORM_IPv6_UCAST-6-PREFIX: One or more, more specific prefixes
could not be programmed into TCAM and are being covered by a less specific prefix
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Explanation A more specific prefix could not be programmed into Ternary Content Addressable
Memory (TCAM) and is covered by a less specific prefix. This could be a temporary condition. The
output of the show platform ipv6 unicast retry route privileged EXEC command lists the failed
prefixes.
PLATFORM_PBR Messages
Error Message PLATFORM_PBR-2-NO_RMAP: Cannot create PBR data structures for
route-map [chars].
Explanation The PBR manager could not allocate the internal data structures for this route-map. A
likely cause is lack of available memory. [chars] is the route-map.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-64 OL-9772-05
Explanation The PBR manager could not 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.
Explanation The PBR manager could not allocate a label for this route-map. As a result, the hardware
cannot be programmed to implement policy routing. There is a limit of 247 labels for policy routing.
[chars] is the route-map.
Recommended Action Simplify the configuration with label sharing. Use the same route-maps on
multiple interfaces, if possible.
Explanation The route-map attached to an interface for policy routing contains an action that is not
supported. This is a hardware limitation. [chars] is the route-map.
Recommended Action Use the route-map map-tag permit global configuration command and the set
ip next-hop ip-address route-map configuration command to reconfigure the route map to use only
these supported actions.
Explanation The route-map attached to an interface for policy-based routing contains an action that
is not supported in hardware, so the packets are forwarded to the CPU for processing. The route-map
actions that invoke this forwarding are set interface, set ip default next-hop, set default interface,
or set ip df. [dec] is the action number, and [chars] is the route-map.
Recommended Action Use the set ip next-hop ip-address route-map configuration command to
reconfigure the route map action to route the packet to the specified next hop.
Explanation The PBR manager was able to fit the complete configuration into the hardware. One or
more route-maps previously did not load because of lack of resources. [chars] is the route-map.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-65
Explanation The routing template is not enabled. [chars] is the text string PBR.
Recommended Action Modify the SDM template to enable the routing template. Use the sdm prefer
routing configuration command, and then reload the switch by using the reload privileged EXEC
command.
PLATFORM_PM Messages
Error Message PLATFORM_PM-3-IFCOUNTERROR: Unit number [dec] of interface [chars] is
more than max allowed value of [dec].
Explanation There are too many interfaces configured for the interface type. [dec] is the interface
count, [chars] is the interface, and [dec] is the maximum number of interfaces.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Explanation An internal VLAN ID allocated for an interface is still in use. [dec] is the VLAN ID,
and [chars] is the interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Explanation The 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 “Error
Message Traceback Reports” section on page 1-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-66 OL-9772-05
PLATFORM_RPC Messages
Error Message PLATFORM_RPC-0-RESOURCE_CRASH: [chars].
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Explanation The system cannot allocate memory for RPC. [chars] describes the error message.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Note This message applies only to Catalyst 3750-X and 3750-E switches.
Explanation There is a missing entry in the class table for a message class. [int] is the number of the
missing message class.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-67
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Explanation There are too many outgoing messages queued for a message class. An RSP message
was dropped. The first [int] is the message type, the second [int] is the message class, the third [int]
is the maximum number of messages that can be queued before throttling occurs, and the last [int]
is the total number of messages that have been throttled.
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-7.
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Explanation The system is experiencing a persistent low-level transport failure in sending RPC
messages. [chars] is a description of the error returned by the low-level packet-sending driver that
triggered the error (usually one of these: fifo full, fifo empty, out of buf, out of mem, null pointer,
misc failure), and [int] is the number of packets outstanding (packets from the RPC code to the driver
that have not yet been sent).
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Explanation The platform received an unexpected response. The first [dec] is RPC request class, the
second [dec] is the RPC request number, the third [dec] is the destination switch number, the fourth
[dec] is the returned error number, and [chars] is an optional comment.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-68 OL-9772-05
Note This message applies only to Catalyst 3750-X and 3750-E switches.
Explanation There is a local resource error or that too many outgoing messages are queued for the
message class. The first [dec] is RPC request class, the second [dec] is the RPC request number, and
[chars] is an optional comment.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Explanation The system had a low-level transport failure when trying to send an RPC message.
[chars] is a description of the error returned by the low-level packet sending driver that triggered the
error (usually one of these: fifo full, fifo empty, out of buf, out of mem, null pointer, misc failure),
and [int] is the number of packets outstanding (packets from the RPC code to the driver that have
not yet been sent).
Recommended Action 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-7.
PLATFORM_SPAN Messages
Error Message PLATFORM_SPAN-3-FEATUREMISMATCH:[chars] cannot be supported with the
image running on switch [dec].
Explanation A switch stack member software image does not support a specific flow-based SPAN
(FSPAN) access control list (ACL) filter. [chars] is the FSPAN ACL filter that is not supported, and
[dec] is the stack member number.
Recommended Action Upgrade to an image that supports the FSPAN ACL filter.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-69
Explanation Egress SPAN rates are falling because SPAN is enabled with multicast routing or
fallback bridging.
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-7.
PLATFORM_STACKPOWER Messages
Note These messages apply only to the Catalyst 3750-X switch.
Explanation One of the power cables connected to the switch stack has been inserted or removed.
[dec] is the stack member number. The first [chars] is the power cable number: 1 is for the main
power cable or 2 is for the redundant power cable. The second [chars] is the power cable status; 1 if
the cable is inserted or 2 if the cable is removed.
Explanation One of the power cables can now provide power to the switch stack. [dec] is the stack
member number. [chars] is the power cable number: 1 for the main power cable; 2 for the redundant
power cable.
Explanation There are too many errors on the port providing power to the switch stack. [dec] is the
stack member number. [chars] is the port (1 or 2).
Recommended Action Verify the stack cable connections. If the stack port is shut down, enable it. If
the 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. 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-70 OL-9772-05
Explanation A version mismatch exists between the switch and the other stack members. [dec] is the
stack member number.
Recommended Action Ensure that all switches in the power stack are running the same Cisco IOS
software release.
Explanation The power stack topology is invalid. The switch is forced into standalone mode.
[dec] is the stack member number. [chars] is a number that explains the reason for the invalid power
stack topology.
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-7.
Explanation The power budget of the switch is more than 1000 W above the rated power output for
the switch stack’s power supplies. Add another power supply to the switch stack. [dec] is the stack
member 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-7.
Explanation Power cable 1 of the switch stack has an inward current that is over 40 A. Add another
power supply to the switch stack. [dec] is the stack member 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-71
Explanation Power cable 2 of the switch stack has an inward current that is over 40 A. Add another
power supply to the switch stack. [dec] is the stack member 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-7.
Explanation Power cable 1 of the switch stack has an outward current that is over 40 A. Remove a
power supply from the switch stack. [dec] is the stack member 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-7.
Explanation Power cable 2 of the switch stack has an outward current that is over 40 A. Remove a
power supply from the switch stack. [dec] is the stack member 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-7.
Explanation The power budget of the switch is less than the minimum required switch budget.
[dec] is the stack member 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-72 OL-9772-05
Explanation The switch stack has a switch with multiple power supplies, but another switch in the
same switch stack has no power supplies. The first [dec] is the switch with multiple power supplies.
The second [dec] is the switch without power supplies.
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-7.
Explanation The switch stack does not have enough power to start all the switches in the stack.
[dec] .... [dec] are the switches that could not be started.
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-7.
Explanation The power priorities of one stack switch conflict with the power priorities of another
stack switch. The first [dec] and the second [dec] are the switches that have conflicting power
priorities.
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-7.
Explanation The switch had a low-voltage condition during the last time that it started or shut down.
[dec] is the stack member 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
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-73
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-7.
Explanation The switch shut down because of a sustained overload condition (SOC). [dec] is the
stack member number. A SOC occurs if the power supplies carry a load of twice (or more) the rated
output for 20 ms or longer.
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-7.
Explanation The switch shut down because of a power supply failed (PS_FAIL) condition. [dec] is
the stack member 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-7.
Explanation The switch shut down because of a system ring load shed (SRLS) event. [dec] is the
stack member number. One example of an SRLS event is a situation in which a switch is physically
removed from the power stack by a cable removal and that switch is a sourcing system in a ring
topology.
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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-74 OL-9772-05
Explanation The switch shut down because of a system star load shed (SSLS) event. [dec] is the stack
member number. One example of an SSLS event is a situation in which a switch is physically
removed from the power stack by a cable removal and that switch is a sourcing system in a star
topology.
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-7.
Explanation The switch shut down because of a low-voltage condition. [dec] is the stack member
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-7.
Recommended Action The switch stack with this switch has lost redundancy and is operating in power
sharing mode. [dec] ... [dec] are the stack member numbers that operate in power sharing mode.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Explanation A built-in self protection (BSIP) event occurred. [dec] is the stack member 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-75
Explanation A built-in self protection (BSIP) event occurred on a switch neighbor. The first [dec]
and second [dec] are the stack member numbers on each side of the neighbor.
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-7.
Explanation A neighbor switch shut down because of a sustained overload condition (SOC). The first
[dec] and second [dec] are the stack member numbers on each side of the neighbor. A SOC occurs
if the power supplies carry a load of twice (or more) the rated output for 20 ms or longer.
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-7.
Explanation A neighbor switch shut down because of a power supply failed (PS_FAIL) condition.
The first [dec] and second [dec] are the stack member numbers on each side of the neighbor.
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-7.
Explanation A neighbor switch shut down because of a system ring load shed (SRLS) event. The first
[dec] and second [dec] are the stack member numbers on each side of the neighbor. One example of
an SRLS event is a situation in which a switch is physically removed from the power stack by a cable
removal and that switch is a sourcing system in a ring topology.
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
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-76 OL-9772-05
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-7.
Explanation A neighbor switch shut down because of a system star load shed (SSLS) event. The first
[dec] and second [dec] are the stack member numbers on each side of the neighbor. One example of
an SSLS event is a situation in which a switch is physically removed from the power stack by a cable
removal and that switch is a sourcing system in a star topology.
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-7.
Explanation A neighbor switch shut down because of a low-voltage condition. The first [dec] and
second [dec] are the stack member numbers on each side of the neighbor.
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-7.
Explanation Ports stopped providing Power over Ethernet (PoE) because of a built-in self protection
(BISP) event that was caused by an overcurrent condition. [dec] is the stack member 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-77
Explanation A built-in self protection (BISP) event that affected Power over Ethernet (PoE)
occurred. [dec] is the stack member number.
Explanation A short-circuit built-in self protection (BISP) event occurred on port 1 of the switch.
[dec] is the stack member number.
Recommended Action Disable and then enable port 1 of the switch. If the 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. 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-7.
Explanation A short-circuit built-in self protection (BISP) event occurred on port 2 of the switch.
[dec] is the stack member number.
Recommended Action Disable and then enable port 2 of the switch. If the 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. 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-7.
Explanation A major built-in self protection (BISP) event shut down the neighbor of the switch. The
first [dec] and second [dec] are the stack member numbers on each side of the neighbor.
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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-78 OL-9772-05
PLATFORM_UCAST Messages
Error Message PLATFORM_UCAST-3-ADJ: [chars].
Explanation An error occurred in the adjacency module for unicast routing. [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 “Error
Message Traceback Reports” section on page 1-7.
Explanation An error occurred in the ARP module for unicast routing. [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 “Error
Message Traceback Reports” section on page 1-7.
Explanation An error occurred in the Cisco Express Forwarding (CEF) module for unicast routing.
[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 “Error
Message Traceback Reports” section on page 1-7.
Explanation An error occurred in the dynamic address tracking mechanism for unicast routing.
[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 “Error
Message Traceback Reports” section on page 1-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-79
Explanation An internal unicast routing error occurred. [chars] describes the error.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
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-7.
Explanation An error occurred in the Hot Standby Router Protocol (HSRP) module for unicast
routing. [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 “Error
Message Traceback Reports” section on page 1-7.
Explanation A unicast routing interface error occurred. [chars] describes the error.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Explanation An error occurred in the RPC module for unicast routing. [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 “Error
Message Traceback Reports” section on page 1-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-80 OL-9772-05
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 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 Message PLATFORM_VLAN-3-LOCK_FAIL: Failed to lock vlan-id [dec], associated
mapped vlan id value [dec].
Explanation The VLAN lock operation failed. This can occur if the VLAN is already active in the
system or if the VLAN ID is not active. The first [dec] is the VLAN ID, and the second [dec] is the
mapped-vlan-id (MVID).
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Explanation An active VLAN is not correctly associated with a 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
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-7.
Explanation The switch did not 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 “Error
Message Traceback Reports” section on page 1-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-81
PLATFORM_WCCP Messages
Error Message PLATFORM-WCCP-3-NO_LABEL: Cannot allocate WCCP Label
Explanation The WCCP label could not be allocated. This means that the hardware cannot be
programmed to implement WCCP redirection.
Recommended Action Reduce the number of interfaces configured for WCCP redirection or policy
based routing.
Explanation The SDM routing template must be enabled to support this feature.
Recommended Action Modify the SDM template to enable the routing template. Use the sdm prefer
routing global configuration command, and then reload the switch by using the reload privileged
EXEC command.
PM Messages
Error Message PM-2-LOW_SP_MEM: Switch process available memory is less than [dec]
bytes.
Explanation The available memory for the switch processor is low. This can occur when too many
Layer 2 VLANs are configured. [dec] is the available memory.
Recommended Action Remove VLANs from the system to reduce memory usage.
Explanation The port manager subsystem could not obtain the memory it needed to initialize the
specified operation. [chars] is the port manager operation.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-82 OL-9772-05
Explanation The software did not add the VLAN to the VLAN Trunking Protocol (VTP) database.
[dec] is the VLAN ID, and [chars] specifies the reason for the failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Explanation An internal software error occurred in the port manager. The parameters identify the
problem for technical support. The first [chars] is the error message, and the second [chars] is the
filename. [dec] is the line number, and the last [chars] is the function name.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, 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-7.
Explanation The port manager detected an invalid request. [dec] is the application ID.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
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-7.
Explanation The port manager detected an invalid request. The first [chars] is the invalid request, and
the second [chars] is the application making the request.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-83
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-7.
Explanation The port manager detected an invalid request. [dec] is the slot number.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Explanation The port manager detected an invalid request. [chars] is the invalid request.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Explanation An invalid host access entry event was received. The host access table entry event
should be an add, delete, or update event. [dec] is the event that is received.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-84 OL-9772-05
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-7.
Explanation The port manager detected an invalid request. [dec] is the port number.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
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-7.
Explanation The port manager detected an invalid request. [dec] is the VLAN ID.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Explanation The port manager detected a misconfiguration or misbehavior and error-disabled the
interface. A recovery is attempted after the configured retry time (the default is 5 minutes). On PoE
switches, this message might appear when a device that can be powered by either a PoE switch port
or by AC power is not being powered by an external AC power source and is connected to a port that
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-85
has been configured with the power inline never interface configuration command. [chars] is the
port where the threshold was exceeded. The first [chars] is the error, and both the second and third
[chars] are the affected interface.
Recommended Action On non-PoE switches, 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. On PoE switches, remove the device or configure
the port by entering the power inline auto, shutdown, and no shutdown interface configuration
commands. 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-7.
Explanation The virtual port (that is, the port-VLAN pair) is error-disabled state when it detects a
misconfiguration or misbehavior. If configured, a recovery will be attempted after the configured
retry time (default time is 5 minutes). The first [chars] is the error, and the second [chars] is the port.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error 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-7.
Explanation The port manager is trying to restart an error-disabled interface. The first [chars] is the
error, 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. 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-7.
Explanation The port manager is trying to restart an error-disabled virtual port. 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 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
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-86 OL-9772-05
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-7.
Explanation The port manager did not allocate the VLAN for external use because the VLAN is
being used by another feature. [dec] is the VLAN that is being used, and [chars] is the feature that
is using it.
Recommended Action Reconfigure the feature (for example, the routed port) to use another internal
VLAN or to request another available VLAN.
Explanation The port manager did not allocate the requested VLAN. The VLAN is probably being
used as an internal VLAN by other features. [dec] is the requested VLAN.
Explanation The port is inactive because the port manager could not create a virtual port for the
switch port and VLAN. 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. 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-7.
Error Message PM-4-INT_FAILUP: [chars] failed to come up. No internal VLAN available.
Explanation The port manager did not allocate an internal VLAN. 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.
Explanation The port manager did not 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.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-87
Explanation An invalid host access entry type was received. The host access entry should be a
configured or a dynamic type. [dec] is the entry type that is received.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Error Message PM-4-LIMITS: The number of vlan-port instances on [chars] exceeded the
recommended limit of [dec].
Explanation The total number of individual VLAN ports on the module or the switch has exceeded
the recommended limit. VLANs can be counted more than once. If VLAN 1 is carried on ten
interfaces, it counts 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 counts 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.
Explanation The port manager did not 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. 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-7.
Explanation During a change-over 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 return to the link-up state when
the port is restarted. The first [chars] is the port number, and the second [chars] is the re-activation
event.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-88 OL-9772-05
Explanation The platform did not 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. 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-7.
Explanation The port manager detected an invalid request. [chars] is the application.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Explanation The host access table is being accessed with an invalid host access value. [dec] is the
value that is received.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Error Message PM-4-VMPS_CFG: Dynamic access VLAN [dec] same as voice vlan on [chars].
Explanation The access VLAN ID on the VMPS server is the same as the voice VLAN ID on the
interface. [dec] is the access VLAN ID, and [chars] is the physical interface.
Recommended Action Assign the access VLAN on the VMPS server to a VLAN ID that is different
from the voice VLAN ID.
Explanation The switch did not add a VLAN in VTP client mode.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, open a case with the TAC, or
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-89
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 Error
Message Traceback Reports, page 1-7.
PORT_SECURITY Messages
Error Message PORT_SECURITY-2-PSECURE_VIOLATION:Security violation occurred caused
by MAC [enet] on port [chars].
Explanation An unauthorized device attempted to connect on a secure port. [enet] is the MAC
address of the unauthorized device, and [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.
Explanation An unauthorized device attempted to connect on a secure trunk port. [chars] is the
secure port, [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.
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, and [chars] is the reconfigured port.
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.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-90 OL-9772-05
Error Message PORT_SECURITY-6-VLAN_FULL: Vlan [dec] on port [chars] has reached its
limit. Address [enet] has been removed.
Explanation The voice VLAN is the same as the access VLAN. Because the maximum number of
MAC addresses allowed on the access VLAN has been reached, the specified Ethernet address has
been deleted. [dec] is the VLAN ID, [chars] is the port assigned to the voice VLAN and the access
VLAN, and [enet] is the Ethernet address.
Explanation A configured VLAN is not allowed either due to a port mode change or an allowed
VLAN list change and is removed from the configuration. [int] is the VLAN ID, and [chars] is the
switch port assigned to the VLAN.
POWERNET_ISSU Messages
Error Message POWERNET_ISSU-4-SM_EW_DOMAIN_MISMATCH: Energywise domain of
EtherSwitch is [chars], recommended to have [chars].
Explanation The EnergyWise domain of the service module does not match that of the switch. The
first [chars] is the EnergyWise domain of the service module. The second [chars] is the EnergyWise
domain of the router.
Recommended Action Configure the EnergyWise domain of the service module to match that of the
switch. If the 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.
Note This message applies only to the Catalyst 3750-X and 3560-X switches.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-91
PT Messages
Error Message PT-3-PT_HW_UNAVAIL: Protocol Tunneling hardware resource not
available. [chars]
Explanation Protocol tunneling could not be enabled because no redirect registers are available.
Protocol tunneling requires redirect registers. [chars] is the hardware resource that is not available.
Recommended Action Disable any applications that use redirect registers, and try configuring the
protocol tunneling again.
QOSMGR Messages
Error Message QOSMGR-3-FEATURE_NOT_FOUND: Cannot find feature for [chars].
Explanation An internal software error has occurred. [chars] is the description of the feature that the
software cannot find.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Explanation An internal software error has occurred. [dec] is the invalid filter type identification.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-92 OL-9772-05
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-7.
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-7.
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-7.
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-7.
Explanation An internal software error has occurred. [chars] is the policy-map name.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, open a case with the TAC, or
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-93
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-7.
Explanation An internal software error has occurred. [hex] [hex] [hex] [hex] are the
software-computed queue pointer values. The parameters provide error details for technical support.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Explanation An internal software error has occurred in the allocated reserved buffers. [dec] is the
reserved count computed by the software.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
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-7.
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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-94 OL-9772-05
Explanation An action other than the set, trust, and police policy-map class configuration
commands was configured in a policy map. This is a hardware limitation. [chars] is the policy-map
name.
Recommended Action Configure only the supported actions of set, trust, and police when in
policy-map class configuration mode.
Recommended Action Reconfigure the class map or the policy map. Use only the match ip dscp
dscp-list class-map configuration command in a policy map that is attached to an egress interface.
Only one match per class map is supported.
Explanation The command to configure a QoS setting failed. This is possibly due to lack of hardware
resources. [chars] is the description of the command.
Recommended Action Look for any other messages that indicate resource failure. If other messages
indicate that the hardware resources are exceeded, retry the command with a smaller configuration.
If the 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. 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-7.
Explanation The policy-map configuration has exceeded the limitation of the hardware. You
configured more QoS ACL entries than the number specified in the SDM template. [chars] is the
policy-map name.
Recommended Action Reconfigure the class map or the policy map, and reduce the number of QoS
ACLs.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-95
Explanation An unsupported match type was entered. Only the access-group acl-index-or-name, ip
dscp dscp-list, and ip precedence ip-precedence-list match types are supported with the match
class-map configuration command. [chars] is the class-map name.
Recommended Action Reconfigure the class map using only the match access-group, match ip dscp,
and match ip precedence class-map configuration commands within the class map.
Explanation A set or trust policy-map class configuration command was configured in a policy map
and attached to an egress interface. A warning message is logged, and the actions do not take effect.
This is a hardware limitation. [chars] is either the set or trust action.
Recommended Action Do not configure a set or trust policy-map class configuration command in a
policy map and attach it to an egress interface. These policy-map actions are supported only on
ingress interfaces.
Explanation The policy-map configuration has exceeded the hardware limitation. An attempt to
configure more policers in all policy maps (by using the police or police aggregate policy-map class
configuration command) than supported by the hardware, which is not allowed, caused this
condition. [chars] is the policy-map name.
Recommended Action Reconfigure the class maps or the policy maps, or delete the policy map from
some interfaces.
Explanation The policy-map configuration has exceeded the hardware limitation. An attempt to
configure more policers in a policy map (by using the police or police aggregate policy-map class
configuration command) than supported by the hardware, which is not allowed, caused this
condition. [chars] is the policy-map name.
Recommended Action Reconfigure the class map or the policy map, and reduce the number of
policers.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-96 OL-9772-05
RMON Messages
Error Message RMON-5-FALLINGTRAP: Falling trap is generated because the value of
[chars] has fallen below the falling-threshold value [dec].
Explanation A falling trap has been generated. The value of the specified MIB object is below the
falling threshold value. [chars] is the MIB object, and [dec] is the threshold value.
Explanation A rising trap has been generated. The value of the specified MIB object is above the
rising threshold value. [chars] is the MIB object, and [dec] is the threshold value.
SCHED Messages
Error Message SCHED-3-UNEXPECTEDEVENT: [traceback] [process information] Process
received unknown event (maj [hex], min [hex])
Explanation A process did not handle an event. The first [hex] is the major event number, and the
second [hex] is the minor event 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.
SDM Messages
Error Message SDM-6-MISMATCH_ADVISE: [chars].
Note This message applies only to the Catalyst 3750-X and 3750-E switches.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-97
Explanation A stack member cannot support the SDM template that the stack master is using.
Switches in the SDM mismatch state are not functional stack members. This error follows the
STACKMGR-6-SWITCH_ADDED_SDM error message if it reports SDM_MISMATCH. [chars]
displays mismatch information and recommended corrective actions.
Recommended Action Downgrade the SDM template of the stack master to make it compatible with
the stack member switches. For example, if the stack master uses the aggregator routing template,
the message recommends downgrading the stack master to the desktop routing template by using the
sdm prefer vlan desktop global configuration command.
SPAN Messages
Error Message SPAN-3-MEM_UNAVAIL: Memory was not available to perform the SPAN
operation.
Explanation The system could not perform a SPAN operation because of a lack of memory.
Recommended Action Reduce other system activity to ease the memory demands.
Explanation The system could not allocate a SPAN hardware resource for the feature specified in the
error message. It is possible that a distributed EtherChannel has been configured in the system that
is using a SPAN hardware resource.
Recommended Action Remove one or all of the distributed EtherChannels from the system and retry
the operation.
Explanation The system could not allocate a SPAN hardware resource for the feature specified in the
error message. A possible cause is that all SPAN source sessions are already in use. The system can
be configured with a maximum of two SPAN source sessions or one RSPAN source session. [chars]
is the unavailable resource.
Recommended Action Remove one of the existing SPAN or RSPAN source sessions, and retry the
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.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-98 OL-9772-05
Explanation SPAN detected an error in its internal operation. [chars] is the interface.
Recommended Action The error might be transient. Try the SPAN operation again. If the second
attempt also fails, reload the switch by using the reload privileged EXEC command to complete the
operation.
SPANTREE Messages
Error Message SPANTREE-2-BLOCK_BPDUGUARD: Received BPDU on port [chars] with BPDU
Guard enabled. Disabling port.
Explanation A BPDU was received on an interface that has the spanning tree BPDU guard feature
enabled. As a result, the interface was administratively shut down. [chars] is the interface name.
Recommended Action Either remove the device sending BPDUs, or disable the BPDU guard feature.
The BPDU guard feature can be locally configured on the interface or globally configured on all
ports that have PortFast enabled. To disable BPDU guard on an interface, use the no spanning-tree
bpduguard enable interface configuration command. To disable BPDU guard globally, use the no
spanning-tree portfast bpduguard default global configuration command. After you have
removed the device or disabled BPDU guard, re-enable the interface by entering the no shutdown
interface configuration command.
Explanation A BPDU was received on the interface and the VLAN. The spanning tree BPDU guard
feature was enabled and configured to shut down the VLAN. The VLAN was error disabled. [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 configured locally on the interface or globally on all ports that have
Port Fast enabled. To re-enable the interface and the VLAN, use the clear errdisable privileged
EXEC command.
Explanation The spanning-tree port associated with the listed spanning-tree instance and interface
will be held in the spanning-tree blocking state until the port VLAN ID (PVID) inconsistency is
resolved. The listed spanning-tree instance is that of the native VLAN ID of the listed interface. The
first [chars] is the interface, and the second [chars] is the spanning-tree instance.
Recommended Action Verify that the configuration of the native VLAN ID is consistent on the
interfaces on each end of the 802.1Q trunk connection. When corrected, spanning tree automatically
unblocks the interfaces, as appropriate.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-99
Explanation The spanning-tree port associated with the listed spanning-tree instance and interface
will be held in the spanning-tree blocking state until the port VLAN ID (PVID) inconsistency is
resolved. The listed spanning-tree instance is that of the native VLAN ID of the interface on the peer
switch to which the listed interface is connected. The first [chars] is the interface, and the second
[chars] is the spanning-tree instance.
Recommended Action Verify that the configuration of the native VLAN ID is consistent on the
interfaces on each end of the 802.1Q trunk connection. When interface inconsistencies are
corrected, spanning tree automatically unblocks the interfaces.
Explanation A misconfiguration of a channel group has been detected. For example, the ports on one
side of the EtherChannel either are not configured to be in the channel or did not bundle into the
channel, and the other side has successfully bundled the ports into the EtherChannel. The first
[chars] is the port, and the second [chars] is the VLAN.
Recommended Action Identify the local ports by using the show interfaces status err-disabled
privileged EXEC command, and then check the EtherChannel configuration on the remote device
by using the show etherchannel summary privileged EXEC command on the remote device. After
the configuration is correct, enter the shutdown and then no shutdown interface configuration
commands on the associated port-channel interfaces.
Explanation The spanning-tree message age timer has expired because no BPDUs were received
from the designated bridge. Because this condition could be caused by a unidirectional-link failure,
the interface is put into the blocking state and marked as loopguard-inconsistent to prevent possible
loops from being created. The first [chars] is the port name, and the second [chars] is the
spanning-tree mode displayed in the show spanning-tree privileged EXEC command.
Recommended Action Enter the show spanning-tree inconsistentports privileged EXEC command
to review the list of interfaces with loopguard inconsistencies. Find out why devices connected to
the listed ports are not sending BPDUs. One reason might be that they are not running the STP. If
so, you should disable loop guard on the inconsistent interfaces by using the spanning-tree guard
none interface configuration command or by starting the STP on the remote side of the links.
Explanation The spanning-tree loopguard configuration for the listed interface has been changed. If
enabled, the interface is placed into the blocking state. It is marked as loopguard-inconsistent when
the message-age timer expires because no BPDUs were received from the designated bridge. This
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-100 OL-9772-05
feature is mainly used to detect unidirectional links. The first [chars] is the loopguard state (enable
or disable), the second [chars] is the interface name, and the third [chars] is the spanning-tree
instance.
Recommended Action Verify that this is the desired configuration for the listed interface. Correct it if
this is not the desired configuration.
Explanation The listed interface has received a BPDU. 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.
Explanation Root guard blocked a port on the multiple spanning-tree (MST) switch. When a
designated port on an MST switch is connected to a PVST+ switch, the CIST (MST00) information
on the port of the MST switch must be consistently superior (lower bridge ID, lower path cost, and
so forth) to the information in all the PVST+ messages. If the port is the root, the CIST (MST00)
information on the MST switch must be consistently inferior to all the PVST+ messages. If this
constraint is violated, the port on the MST switch is blocked to prevent a potential bridging loop.
The first [chars] is the MST switch, the second [chars] is the port, and the third [chars] is the PVST+
switch. The first [dec] is the VLAN ID, the second [dec] is the MST switch, and [enet] is the
MST-switch MAC address.
Recommended Action When STP 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 the appropriate priority for
the VLAN spanning tree, consistent with the CIST role on the port of the MST switch.
There could be additional inconsistencies not shown in the message, and the port does not recover
until all these are cleared. To determine which other VLANs have inconsistencies, disable and
re-enable the port. This message appears again and specifies another VLAN with inconsistencies to
be fixed. Repeat this process until all inconsistencies on all VLANs are cleared.
Explanation The specified interface no longer receives PVST BPDUs advertising information that is
inconsistent with the CIST port information. The PVST simulation inconsistency is cleared, and the
interface returns to normal operation. [chars] is the port.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-101
Explanation The interface that received a Shared Spanning Tree Protocol (SSTP) BPDU was in trunk
mode but was not using 802.1Q encapsulation. The first [chars] is the interface, and the second
[chars] is the VLAN.
Recommended Action Verify that the configuration and operational state of the listed interface and
that of the interface to which it is connected are in the same mode (access or trunk). If the mode is
trunk, verify that both interfaces have the same encapsulation (ISL or 802.1Q). If the encapsulation
types are different, use the switchport trunk encapsulation interface configuration command to
make them consistent. When the encapsulation is consistent, spanning tree automatically unblocks
the interface.
Error Message SPANTREE-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV on [chars]
[chars].
Explanation The listed interface received an SSTP BPDU without the VLAN ID tag. The BPDU is
discarded. The first [chars] is the interface, 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-7.
Explanation The listed interface received an SSTP BPDU that is tagged with a VLAN ID that does
not match the VLAN ID that received the BPDU. 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.
Explanation The listed interface received a BPDU 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
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-102 OL-9772-05
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.
Explanation The spanning-tree root guard configuration for the listed interface has changed. If
enabled, any BPDU received on this interface that advertises a superior spanning-tree root bridge
(lower bridge ID, lower path cost, and so forth) to that already in use causes the interface to be put
into the blocking state and marked as root-guard inconsistent. The first [chars] is the root-guard state
(enable or disable), the second [chars] is the interface, and the third [chars] is the spanning-tree
instance.
Recommended Action Verify that this is the desired configuration for the listed interface. Correct it if
it is not the desired configuration.
Explanation The listed interface is no longer receiving BPDUs advertising a superior root bridge
(lower bridge ID, lower path cost, and so forth). The root-guard inconsistency is cleared for the
interface, and the blocking state is removed from the interface. The first [chars] is the port name,
and the second [chars] is the spanning-tree mode displayed in show spanning-tree privileged EXEC
command.
Explanation The port VLAN ID or port type inconsistencies have been resolved, and spanning tree
will unblock the listed interface of the listed spanning-tree instance. The first [chars] is the interface,
and the second [chars] is the spanning-tree instance.
Explanation 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 error occurs because of an
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-103
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. 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-7.
Explanation 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 Verify the interface configuration, and test any cable connected to the interface.
When the problem is resolved, re-enable the interface by entering the no shutdown interface
configuration command.
Explanation The switch has received a prestandard MST BPDU on an interface that is not configured
to send prestandard MST BPDUs. The switch automatically adjusts its configuration on the interface
and starts sending prestandard BPDUs. However, the switch does not automatically detect all
prestandard neighbors, and we recommend that you configure the interface to send prestandard MST
BPDUs by using the spanning-tree mst pre-standard interface configuration command. This
warning message only appears once. [chars] is the interface.
Recommended Action Use the spanning-tree mst pre-standard interface configuration command on
all the interfaces to which other switches running Cisco's prestandard MST version are connected.
We recommend that you migrate all the switches in the network to the IEEE MST standard version.
Explanation A port-not-forwarding alarm is set or cleared. The first [chars] is the mode, and the
second [chars] is the severity. The third [chars] is the interface name, and the fourth [chars] is the
alarm string.
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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-104 OL-9772-05
Explanation 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.
Error Message SPANTREE-5-ROOTCHANGE: Root Changed for [chars] [dec]: New Root Port
is [chars]. New Root Mac Address is [enet].
Explanation 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.
Explanation The interface has been added to all VLANs. [chars] is the added interface.
Explanation The interface has been deleted from all VLANs. [chars] is the deleted interface.
Error Message SPANTREE-6-PORT_STATE: Port [chars] instance [dec] moving from [chars]
to [chars].
Explanation 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.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-105
Explanation The listed interface is 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 (ISL or 802.1Q). When these
parameters are consistent, spanning tree automatically unblocks the interface.
Explanation The interface has been deleted from VLAN. [chars] is the interface, and [dec] is the
VLAN ID.
Explanation An STP 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, ISL, or 802.1Q). When these
parameters are consistent, spanning tree automatically unblocks the interface.
SPANTREE_FAST Messages
Error Message SPANTREE_FAST-7-PORT_FWD_UPLINK: [chars] [chars] moved to Forwarding
(UplinkFast).
Explanation The listed interface has been selected as the new path to the root switch for the listed
spanning-tree instance. The first [chars] is the spanning-tree instance, and the second [chars] is the
interface.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-106 OL-9772-05
SPANTREE_VLAN_SW Messages
Error Message SPANTREE_VLAN_SW-2-MAX_INSTANCE: Platform limit of [dec] STP instances
exceeded. No instance created for [chars] (port [chars]).
Explanation The number of currently active VLAN spanning-tree instances has reached a
platform-specific limit. No additional VLAN instances are created until the existing number of
instances drops below the platform limit. [dec] is the spanning-tree instance limit, the first [chars]
is the smallest VLAN ID of those VLANs that cannot have spanning-tree instances created, and the
second [chars] is the port number.
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.
STACKMGR Messages
Note These messages apply only to Catalyst 3750-X and 3750-E switches.
Explanation This switch could not get the device record for some or all other switches in the stack.
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-7.
Explanation The stack manager module did not retrieve stack messages. The first [dec] is the ASIC
ID, and the second [dec] is the direction.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-107
Error Message STACKMGR-3-NORECORD: Switch removed event for switch [dec] with no
switch record.
Explanation The stack manager received a switch-removed event for which there is no switch record.
[dec] is the switch number.
Explanation The specified switch has been elected stack master. [dec] is the switch number of the
elected stack master.
Explanation The specified stack port status has changed state to up or down. The first [chars] is the
stack port (1 or 2), [dec] is the switch number, and the second [chars] is the new state (up or down).
Error Message STACKMGR-4-SWITCH_ADDED: Switch [dec] has been ADDED to the stack.
Explanation The specified stack member switch has been added to the stack. [dec] is the switch
number.
Error Message STACKMGR-4-SWITCH_ADDED_SDM: Switch [dec] has been ADDED to the stack
(SDM_MISMATCH).
Explanation The specified switch has been added to the stack. [dec] is the switch number.
SDM_MISMATCH means that the added switch cannot support the SDM template that the stack
master is using. Subsequent SDM-6-MISMATCH_ADVISE messages explain the mismatch and
recommend corrective actions.
Error Message STACKMGR-4-SWITCH_ADDED_VM: Switch [dec] has been ADDED to the stack
(VERSION_MISMATCH).
Explanation A switch that has been added to the stack has a different software version. [dec] is the
switch number.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-108 OL-9772-05
Error Message STACKMGR-4-SWITCH_REMOVED: Switch [dec] has been REMOVED from the
stack.
Explanation The specified switch has been removed from the stack. [dec] is the switch number.
Explanation The stack master is ready for use. [dec] is the stack master switch number.
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 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.
Explanation The amount of traffic detected on the interface has exceeded the configured threshold
values. Because the interface is configured to shut down if a packet storm event is detected, it has
been placed in an error-disabled state. [chars] is the affected interface.
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.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-109
SUPERVISOR Messages
Error Message SUPERVISOR-3-FATAL: [chars].
Explanation An internal error occurred in the supervisor ASIC. [chars] is the detailed error message.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
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-7.
SUPQ Messages
Error Message SUPQ-3-THROTTLE_CPU_QUEUE: Invalid application ID [dec] used for
throttling.
Explanation 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 “Error
Message Traceback Reports” section on page 1-7.
Explanation The system has detected that messages directed to the CPU are delayed. [chars] is the
detailed error message.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-110 OL-9772-05
Explanation The system is warning you about a slowdown of the sending 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 “Error
Message Traceback Reports” section on page 1-7.
Explanation The system is warning you about the sending 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 “Error
Message Traceback Reports” section on page 1-7.
Error Message SUPQ-4-PORT_QUEUE_STUCK: Port queue Stuck for asic [dec] port [dec]
queue [dec].
Explanation 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-7.
Error Message SUPQ-4-RECV_QUEUE_STUCK: Receive queue Stuck for asic [dec] queue
[dec].
Explanation The system has detected that the receiving queue is not being cleared in a reasonable
time. The first [dec] is the ASIC, and the second [dec] is the queue number.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-111
SW_DAI Messages
Error Message SW_DAI-4-ACL_DENY: [dec] Invalid ARPs ([chars]) on [chars], vlan
[dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]).
Explanation 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 packets have been denied by ACLs either explicitly or
implicitly (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.
Explanation The switch has received ARP packets considered invalid by ARP inspection. The
packets are erroneous, and their presence might show attempted man-in-the-middle attacks in the
network. This log message appears when the IP and MAC address binding of the sender for the
received VLAN is not present 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.
Explanation The switch has received ARP packets that have been permitted because the IP and MAC
address of the sender 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.
Explanation 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
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-112 OL-9772-05
Explanation 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 put into the error-disabled state 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.
Explanation 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.
Explanation The switch has received ARP packets considered invalid by ARP inspection. The
packets are erroneous, and their presence might show attempted man-in-the-middle attacks in the
network. 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.
Explanation 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.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-113
Explanation The switch has received ARP packets that have been permitted because the IP and MAC
address of the sender 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.
SW_MACAUTH Messages
Error Message SW_MACAUTH-4-UNAUTH_MAC: Unauthenticated MAC [enet] on port [chars]
Explanation The switch has received an unauthenticated MAC address on the specified port. [enet]
is the unauthenticated MAC address, and [chars] is the port.
Explanation MAC authentication is enabled or disabled. [chars] is the MAC authentication status,
either enabled or disabled.
Explanation The switch has received a command to authenticate a MAC address. [enet] is the MAC
address.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-114 OL-9772-05
SW_MATM Messages
Error Message SW_MATM-4-MACFLAP_NOTIF: Host [enet] in [chars] [dec] is flapping
between port [chars] and port [chars]
Explanation The switch found the traffic from the specified host flapping between the specified
ports. [enet] is the host MAC address, [chars] [dec] is the switch ID, and the first and second [chars]
are the ports between which the host traffic is flapping.
Recommended Action Check the network switches for misconfigurations that might cause a
data-forwarding loop.
SW_VLAN Messages
Error Message SW_VLAN-3-MALLOC_FAIL: Failed to allocate [dec] 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 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-7.
Explanation 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 “Error
Message Traceback Reports” section on page 1-7.
Explanation 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. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, open a case with the TAC, or
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-115
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-7.
Explanation The VLAN manager received an upcall and a VLAN cookie from the port manager that
translated to a bad VLAN ID. [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 “Error
Message Traceback Reports” section on page 1-7.
Explanation The VLAN software did not use the VLAN configuration from the startup-configuration
file. It will use the binary VLAN configuration file in NVRAM.
Explanation 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 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-7.
Explanation The VLAN configuration file read by the VLAN manager contained an unrecognized
file version number, which might mean an attempt to regress to an older version of the VLAN
manager software. [dec] is the file version number.
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
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-116 OL-9772-05
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-7.
Explanation A software error has occurred, and 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-7.
Explanation 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. 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-7.
Explanation Envalid 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.
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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-117
Explanation The VLAN manager received an unexpected error return from a Cisco IOS file system
(IFS) call while reading the VLAN database. The first [chars] is the function call name, the second
[chars] is the file name, the first [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-7.
Explanation 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. 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-7.
Explanation The VLAN software did not 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.
Explanation The specified VLANs could not be created. The port manager might not have completed
the VLAN creation requests because the VLANs already exist as internal VLANs. The first [chars]
is the VLAN ID, and the second [chars] describes the error.
Recommended Action Verify the internal VLAN usage by using show vlan internal usage privileged
EXEC command, reconfigure the feature that is using the internal VLANs, and 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. Use the Bug
Toolkit to look for similar reported problems. If you still require assistance, open a case with the
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-118 OL-9772-05
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-7.
Explanation The VLAN manager received an unexpected error code from the VTP configuration
software. [dec] is the error code, the first [chars] is the VTP function, and the second [chars] is the
error-code description.
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-7.
Explanation The VLAN manager received invalid data from a VTP configuration database routine.
The first [chars] is the data type, [dec] is the inappropriate value that was received, and the second
[chars] is the VTP database function.
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-7.
Explanation The VLAN manager received invalid data from the VTP configuration software. The
first [chars] is the data type, [dec] is the value of that data, and the second [chars] is the VTP event.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-119
Explanation The VTP database is not available. You should access the VTP database later. The first
[chars] is the function name that you want to configure, and the second [chars] is the function name
that is using the VTP database.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
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-7.
Explanation The VLAN software detected an old version of the VLAN configuration file format. It
interpreted the file, but it will use the new format in the future. The first [dec] is the old version
number, and the second [dec] is the new version number.
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
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 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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-120 OL-9772-05
Explanation The VTP domain name was changed through the configuration to the name specified in
the message. [chars] is the changed domain name.
SWITCH_QOS_TB Messages
Error Message SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: [chars] detected on port
[chars], port's configured trust state is now operational.
Explanation A trusted boundary detected a device matching the trusted device setting for the port and
has modified the port trust state. The first [chars] is the trusted device, and the second [chars] is the
port.
Explanation A trusted boundary lost contact with a trusted device and has set the port trust state to
untrusted. The first [chars] is the trusted device, and the second [chars] is the port
TCAMMGR Messages
Error Message TCAMMGR-3-GROW_ERROR: cam region [dec] can not grow.
Explanation 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
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-121
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-7.
Explanation The CAM handle used by the caller is not valid. [hex] is the handle value.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. 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-7.
Explanation 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
“Error Message Traceback Reports” section on page 1-7.
Error Message TCAMMGR-3-MOVE_ERROR: cam entry move from index [int] to index [int]
failed.
Explanation A CAM entry being moved 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 “Error
Message Traceback Reports” section on page 1-7.
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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-122 OL-9772-05
Error Message TCAMMGR-3-REGMASK_ERROR: invalid cam region [dec] mask [dec] pair.
Explanation A caller attempted to install an entry with an invalid mask for the region. Only a
predetermined set of masks is allowed in a region. The first [dec] is the region, and the second [dec]
is the mask.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
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-7.
UDLD Messages
Error Message UDLD-0-STOPPED:UDLD process stopped:[chars].
Explanation 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
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. 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-7.
Explanation 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. 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-7.
Explanation A software check failed during UDLD processing. [chars] is a description of the internal
error.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to
look for similar reported problems. If you still require assistance, open a case with the TAC, or
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-123
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-7.
Explanation 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. 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-7.
Explanation 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.
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-7.
Explanation The UDLD Protocol detected a unidirectional connection between neighbors. Reset the
port that was disabled by UDLD by using the udld reset privileged EXEC command or through a
hardware action such as a link-state change. [chars] is the interface.
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-7.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-124 OL-9772-05
UFAST_MCAST_SW Messages
Error Message UFAST_MCAST_SW-3-PROC_START_ERROR: No process available for
transmitting UplinkFast packets.
Explanation UplinkFast packets will not be sent because the process could not be created.
Recommended Action UplinkFast does not work unless you reload the switch software. If the message
appears again after reload, 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-7.
Explanation UplinkFast packets will not be sent on a VLAN due to memory limitations. [dec] is the
VLAN ID.
VQPCLIENT Messages
Error Message VQPCLIENT-2-CHUNKFAIL: Could not allocate memory for VQP.
Explanation An error occurred when the system tried to allocate memory for the VQP client.
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-7.
Explanation The VMPS has denied access for the given host MAC address to an interface. [enet] is
the host MAC address, and [chars] is the interface name.
Recommended Action No action is normally required. If you think that the host should have been
allowed access, verify the configuration on the VMPS.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 2-125
Explanation The system has shut down the specified interface because too many hosts have requested
access to that interface. [chars] is the interface name.
Recommended Action To enable the interface, remove the excess hosts, and enter the no shutdown
interface configuration command.
Explanation The VMPS has sent an unsolicited response with an unknown interface name. [chars] is
the name of the unknown interface.
Explanation The VMPS has specified an unknown VLAN name. [chars] is the VLAN name.
Recommended Action Ensure that the VLAN exists on the switch. Verify the VMPS configuration by
entering the show vmps privileged EXEC command.
WCCP Messages
Error Message WCCP-5-CACHEFOUND: Web Cache [IP_address] acquired.
Explanation The switch has acquired the specified web cache. [IP_address] is the web cache IP
address.
Explanation The switch has lost contact with the specified web cache. [IP_address] is the web cache
IP address.
Recommended Action Verify the operation of the web cache by entering the show ip wccp web-cache
privileged EXEC command.
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
2-126 OL-9772-05
Numerics C
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 IN-1
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
IN-2 OL-9772-05
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 IN-3
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
IN-4 OL-9772-05
tables
facility codes 1-2
message severity levels 1-6
variable fields 1-6
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
OL-9772-05 IN-5
Catalyst 3750-X, 3750-E, 3560-X, and 3560-E Switch System Message Guide
IN-6 OL-9772-05