Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
Fax: 408 527-0883
Text Part Number: OL-11469-02
IOS System Message Guide
800 553-NETS (6387)
Page 2
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
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)
This preface describes the audience, organization, and conventions of this publication, and provides
information on how to obtain related documentation.
Audience
This publication is for experienced network administrators who are responsible for configuring and
maintaining Catalyst 6500 series switches that are configured with the Supervisor Engine 32 and the
Programmable Intelligent Services Adapter (PISA).
Organization
The major sections of this publication are as follows:
ChapterTitleDescription
1System Message
2Messages and
Overview
Recovery
Procedures
Describes how to read a system or error
message.
Contains the message descriptions and
recovery procedures.
Related Documentation
The following publications are available for the Catalyst 6500 series switches:
• Catalyst 6500 Series Switch Module Installation Guide
• Catalyst 6500 Series Switch Cisco IOS Command Reference
NoteMeans reader take note. Notes contain helpful suggestions or references to material not covered in
the publication.
Cautions use the following conventions:
Caution Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation, at:
Subscribe to the What’s New in Cisco Product Documentation as an RSS feed and set content to be
delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently
supports RSS Version 2.0.
This publication lists and describes the Cisco IOS system messages for Catalyst 6500 series switches.
The system software sends these error messages to the console (and, optionally, to a logging server on
another system) during operation. Not all system error messages indicate problems with your system.
Some messages are purely informational, while others may help diagnose problems with
communications lines, internal hardware, or the system software.
This publication also includes error messages that appear when the system fails.
This chapter contains the following sections:
• System Message Structure, page 1-1
• System Message Example, page 1-8
• Using the Error Message Decoder to Search for System Messages, page 1-8
• Searching for System Messages in Online Documentation, page 1-8
• Terminology, page 1-9
• Error Message Traceback Reports, page 1-9
System Message Structure
System error messages are structured as follows:
%FACILITY-SEVERITY-MNEMONIC: Message-text
• FACILITY code
The facility code consists of two or more uppercase letters that indicate the facility to which the
message refers. A facility can be a hardware device, a protocol, or a module of the system software.
The severity level 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. Tab l e 1- 2 lists the message severity levels.
System Message Structure
Table 1-2 Message Severity Levels
Severity LevelDescription
0 – emergencySystem is unusable
1 – alertImmediate action required
2 – criticalCritical condition
3 – errorError condition
4 – warningWarning condition
5 – notificationNormal but significant condition
6 – informationalInformational message only
7 – debuggingMessage that appears during debugging only
• MNEMONIC code
The MNEMONIC code uniquely identifies the error message.
• Message-text
Message-text is a text string that describes the condition. The text string sometimes contains detailed
information about the event, including terminal port numbers, network addresses, or addresses that
correspond to locations in the system memory address space. Because variable fields change from
message to message, they are represented here by short strings enclosed in square brackets ([ ]). A
decimal number, for example, is represented as [dec]. Table 1-3 lists the variable fields in messages.
Table 1-3Representation of Variable Fields in Messages
RepresentationType of Information
[chars] or [char]Character string
[dec]Decimal
[hex]Hexadecimal integer
[int]Integer
[num]Number
System Message Example
The following is an example of a system error message:
%LINK-2-BADVCALL: Interface [chars], undefined entry point
• LINK is the facility code.
Chapter 1 System Message Overview
• 2 is the severity level.
• BADVCALL is the mnemonic code.
• “Interface [chars], undefined entry point” is the message text.
Some messages also indicate where the system condition occurred. These messages are structured as
follows:
%FACILITY-SOURCE-SEVERITY-MNEMONIC: Message-text
SOURCE indicates the location of the condition. Examples of SOURCE are SP, which indicates that the
condition occurred in the switch processor, or DFC5, which indicates that the condition occurred in the
Distributed Forwarding Card on the module in slot 5.
Using the Error Message Decoder to Search for System
Messages
The Error Message Decoder (EMD) is a tool that will help you to research and resolve error messages
for Cisco software. EMD helps you to understand the meaning of the error messages that display on the
console of Cisco routers, switches, and firewalls.
To use the EMD, copy the message that appears on the console or in the system log, paste it into the
window, and press the Submit button. You will automatically receive an Explanation, Recommended
Action, and, if available, any related documentation for that message.
Searching for System Messages in Online Documentation
To search for messages in online documentation, use the search function of your browser by copying and
pasting the message that appears on the console or in the system log.
Some messages that appear on the console or in the system log indicate where the system condition
occurred. These messages are structured as follows:
%FACILITY-SOURCE-SEVERITY-MNEMONIC: Message-text
SOURCE indicates the location of the condition. Examples of SOURCE are SP, which indicates that the
condition occurred in the switch processor, or DFC5, which indicates that the condition occurred in the
Distributed Forwarding Card on the module in slot 5.
If you search for the explanation and recommended action of a message that contains a SOURCE,
remove the SOURCE from the text first, and then search for the message in the documentation.
For example, instead of searching the documentation for the message C6KPWR-SP-4-DISABLED,
remove the SOURCE identifier and search for the message C6KPWR-4-DISABLED.
Terminology
In this publication, the terms “module” and “line card” both refer to a switch module.
Terminology
Error Message Traceback Reports
Some messages describe internal errors and contain traceback information. This information is very
important and should be included when you report a problem to your technical support representative.
The following sample message includes traceback information:
This chapter lists the switch system messages by facility. Within each facility, the messages are listed by
severity levels 0 to 7. The highest severity level is 0, and the lowest severity level is 7. Each message is
followed by an explanation and a recommended action.
NoteThe messages listed in this chapter do not include the date/time stamp designation; the date/time stamp
designation is displayed only if the software is configured for system log messaging.
For Cisco IOS system messages not contained in this publication, refer to this document:
This section contains Allegro Crypto Engine (ACE) messages.
Error Message %ACE-3-NOENGINESLOT: Interface [chars] has no crypto engine slot
Explanation
crypto engine slot was assigned to that interface. [chars] is the name of the interface that is missing
the crypto engine slot command.
Recommended Action Configure the interface in question with the crypto engine [sub]slot command.
Error Message %ACE-3-OUTOFID_RL: Too may [chars] IDs in the system. Cannot allocate
a new one
Explanation
Recommended Action Reduce the traffic load, the number of IPsec tunnels, or the frequency of
changing the value of a cryptographic key. If this message appeared under light traffic conditions,
copy the message exactly as it appears on the console or in the system log. Research and attempt to
resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some
This message appears when an IKE SA was requested for a given interface, but no
messages, these tools and utilities will supply clarifying information. Search for resolved software
issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require
assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the information you have gathered. Attach the
following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %ACE-6-SWITCHOVER: VPN-SM switchover: [dec]/[dec] has been [chars]
[dec]/[dec]
Explanation
Recommended Action No action is required.
Error Message %ACE-6-UNEXP_INBOUND_IPSEC: [chars]: received unexpected IPsec packet:
Recommended Action If this message appears when booting the router and enabling the hardware
A module-to-module switchover has occurred. System performance is not affected.
An IPsec packet was unexpectedly forwarded to the RP.
crypto accelerator, then this message is normal and can be safely ignored. Otherwise, copy the error
message exactly as it appears on the console or in the system log, and report it to your Cisco
technical support representative.
Recommended Action If this message appears when booting the router and enabling the hardware
An IPsec packet was unexpectedly forwarded to the RP.
crypto accelerator, then this message is normal and can be safely ignored. Otherwise, copy the error
message exactly as it appears on the console or in the system log, and report it to your Cisco
technical support representative.
The specified policy was not applied for the given host IP due to the reason specified as
Error.
Recommended Action When the “POLICY” character string is “HOST ACL,” verify that an input
access control list (ACL) is defined and configured on the interface. A “URL REDIRECT ACL”
policy needs a URL-redirect vendor-specific attribute (VSA) to have an associated access control
list URL-redirect-ACL VSA that can be used to determine HTTP redirect criteria. HTTP packets
that match the ACL are subject to redirection. When a URL-redirect-ACL access control list is not
specified or is not configured, the host will not be set up for HTTP redirection.
Error Message %AP-4-AUTH_PROXY_NOMEM: Sufficient memory was not available to [chars]
Explanation
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
There was not enough memory to perform the specified operation.
upgrade to a larger memory configuration.
Error Message %AP-4-POSTURE_EXCEED_MAX_INIT: Exceeded maximum limit ([dec]) on
entires in authentication proxy posture cache in initializing state
Explanation
The number of entries that are in the Authentication Proxy posture cache and in an
initializing state has exceeded the maximum limit.
Recommended Action This condition might indicate a denial of service (DoS) attack. Copy the
message exactly as it appears on the console or in the system log. Research and attempt to resolve
the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages,
these tools and utilities will supply clarifying information. Search for resolved software issues using
the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open
a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the information you have gathered. Attach the
following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
to initialize successfully. Information about the failed device is specified in the message text on the
console or in the system log.
Recommended Action Power down and reseat the indicated SPA card. If the condition persists, copy
the message exactly as it appears on the console or in the system log. Research and attempt to
resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some
messages, these tools and utilities will supply clarifying information. Search for resolved software
issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require
assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the information you have gathered. Attach the
following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
the console or in the system log provides more information about the specific nature 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 issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the show logging and show tech-support commands and your
pertinent troubleshooting logs.
The SPA failed to complete hardware initialization. One of the devices in the SPA failed
A data path protocol violation or sequence error has been detected. The message text on
Error Message %ATMSPA-3-FATAL_ERROR: occurred on [chars]. Resetting SPA
ATMSPA Messages
Explanation
The SPA has been reset because of a critical error in one of its devices. The error could
be either a single occurrence of an event or multiple occurrences within a period of time. The
message text on the console or in the system log provides more information about the specific nature
of the error.
Recommended Action If the SPA is reset more than once, copy the message exactly as it appears on
the console or in the system log. Research and attempt to resolve the issue using the tools and
utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will
supply clarifying information. Search for resolved software issues using the Bug Toolkit at
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the show logging and show tech-support commands and your
pertinent troubleshooting logs.
Error Message %ATMSPA-3-FPD_VER_DEPENDENCY_NOTE: Cannot perform the requested FPD
update operation because [chars] in subslot [int]/[int] has incompatible HW
version [int].[int] with FPD image version [dec].[dec] for FPD ID [dec]. Only image
version greater than [int].[int] can be used in the update operation of [chars]
with HW version greater than [int].[int].
Explanation
The version of the field-programmable device (FPD) image from the FPD image bundle
or package is not compatible with the hardware version of the target card.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the show logging and show tech-support commands and your
pertinent troubleshooting logs.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
The error that is specified in the message has been detected.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the show logging and show tech-support commands and your
pertinent troubleshooting logs.
A hardware error has been detected. The message text on the console or in the system
log provides more information about the specific nature 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 issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the show logging and show tech-support commands and your
pertinent troubleshooting logs.
Traffic-shaping parameters could not be configured because the number of unique
shaping parameters that are configured on the PVCs or PVPs in this specified ATM SPA is over the
maximum limit. The maximum number of unique shaping parameters that can be configured on the
PVCs or PVPs is 4096.
Recommended Action Ensure that the total number of unique shaping parameters that are configured
on both PVCs and PVPs does not exceed the maximum limit of 4096.
A software error has been detected. The message text on the console or in the system
log provides more information about the specific nature 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 issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the show logging and show tech-support commands and your
pertinent troubleshooting logs.
Error Message %ATMSPA-3-VCQ_ERROR: [chars]: VC queue configuration failed due to
un-initialized queue table(global identifier [dec])
Explanation
Recommended Action Attempt to perform a soft OIR operation by entering the command that is
The software configuration of a VC queue failed because of an uninitialized queue table.
described in the software configuration guide for the shared port adapter. If the condition persists,
copy the message exactly as it appears on the console or in the system log. Research and attempt to
resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some
messages, these tools and utilities will supply clarifying information. Search for resolved software
issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require
assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the information you have gathered. Attach the
following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ATMSPA-4
Error Message %ATMSPA-4-VCSETUP: [chars]: VC setup command received on the LC for an
existing VC (VCD [dec])
BGP Messages
Explanation
configured by a previous setup VC command from the route processor (RP). A duplicate setup
command may indicate that the RP did not receive a response from the line card for the previous
setup command.
Recommended Action No action is required.
Error Message %ATMSPA-4-VCTEARDOWN: [chars]: VC tear down command received on the LC
for a non-existing VC (VCD [dec])
Explanation
teardown command from the RP. A duplicate teardown command may indicate that the RP did not
receive a response from the line card for the previous teardown command.
Recommended Action No action is required.
BGP Messages
This section contains Border Gateway Protocol (BGP) messages.
BGP-3
A command to set up a VC has been received for a VC that has already been set up and
The VC does not exist on the line card. The VC may have been torn down by a previous
Error Message %BGP-3-ADDPATH: Number of paths for [chars] exceeded allowed maximum
of [dec]
Explanation
Recommended Action Restrict the number of neighbors advertising the same prefix by implementing
inbound filters.
OL-11469-02
BGP is receiving the same prefix from too many neighbors.
type. The Tag Forwarding Information Base (TFIB) asks for a label for a prefix in the VRF routing
table. The per-VRF aggregate label will be assigned to the connected or BGP aggregate prefix when
BGP runs a best-path calculation.
Recommended Action No action is required. If this message recurs, contact your Cisco technical
support representative.
Error Message %BGP-4-MAXPFX: No. of prefix received from [chars][chars][chars] (afi
[dec]) reaches [dec], max [dec]
Explanation
The number of prefixes received from a neighbor has exceeded a configured limit.
This message might appear when a prefix changes to a connected or BGP aggregate
The number of prefixes received from a neighbor has reached a warning limit.
Recommended Action Check the number of prefixes received from the neighbor and determine
whether the limit should be increased.
C6K_MPLS_COMMON Messages
This section contains Catalyst 6500 series switch and Cisco 7600 series router LAN and WAN
Multiprotocol Label Switching (C6K_MPLS_COMMON) messages.
C6K_MPLS_COMMON-3
Error Message %C6K_MPLS_COMMON-3-L2_CONFIG_NOT_RECOMMENDED: xconnect is configured
on interface vlans and WAN interfaces are facing the MPLS Core. Do not configure
LAN interfaces facing the MPLS Core.
Explanation
network configuration has cross-connection services configured on interface VLANs and has WAN
interfaces facing the MPLS core.
Recommended Action Do not configure MPLS on LAN interfaces facing the MPLS core if the
network has cross-connect services configured on an interface VLAN and WAN interfaces that face
the MPLS core.
An attempt was made to configure a LAN interface to face the MPLS core. The current
Error Message %C6K_MPLS_COMMON-3-L3_CONFIG_NOT_RECOMMENDED: LAN interfaces are
facing the MPLS Core. Do not configure xconnect on interface vlans.
C6K_MPLS_LC Messages
Explanation
An attempt was made to configure a cross-connection service on an interface VLAN.
The current network configuration has MPLS configured on a LAN interface that is facing the MPLS
core.
Recommended Action Do not configure cross-connection services on an interface VLAN if the
network has MPLS configured on a LAN interface.
Error Message %C6K_MPLS_COMMON-3-OSM_BB1_CONFIG_UNSUPPORTED: The maximum label
range configured for this system exceeds the [int] limit supported by the module
in slot [int]. For proper MPLS functionality on any of the interfaces on this
module the maximum label range should be set to [int].
Explanation
Recommended Action Change the maximum MPLS label range by using the mpls label range
The OSM cannot support the MPLS label range configured for this system.
command.
Error Message %C6K_MPLS_COMMON-3-VPLS_CONFIG_EXCEEDED: The number of EoMPLS/VPLS VCs
exceeded the maximum supported on [IP_address]/[int].
Explanation
The number of destination routers or the global number of virtual circuits exceeded the
maximum limit supported by the device.
Recommended Action Refer to network configuration guidelines for the maximum limits.
C6K_MPLS_LC Messages
This section contains Catalyst 6500 series switch and Cisco 7600 series router Multiprotocol Label
Switching (MPLS) switch processor or module (C6K_MPLS_LC) messages.
C6K_MPLS_LC-3
Error Message %C6K_MPLS_LC-3-MALLOCFAIL: failed to create [chars]
Explanation
MPLS packets might be forwarded by the software.
Recommended Action Reduce other system activity to ease memory demands. If necessary, increase
system memory. When more memory is available, wait for a few minutes and enter the clear ip
route command. If sufficient memory has not been made available, this message will be displayed
again. If this problem persists, contact your Cisco technical support representative.
The system failed to allocate memory for an MPLS entry for the incoming label. Some
Error Message %C6K_MPLS_LC-3-REWRITEFAIL: null adj for incoming label [dec]
Explanation
entry might not be programmed because the incoming label has the NULL adjacency entry. This
condition is an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log. Contact your Cisco technical support representative with the output of the show mpls
forwarding-table labels command.
Error Message %C6K_MPLS_LC-3-TCAMFAIL: failed to insert label [dec] to TCAM
Explanation
The TCAM might be full. Some MPLS packets might be forwarded by the software.
Recommended Action Reduce the number of routes in the system to free up TCAM space. When
enough free TCAM space is available, the software starts the TCAM recovery mechanism
automatically. The TCAM recovery mechanism reinstalls the MPLS label entries that previously
failed.
The specified incoming label has a NULL adjacency entry. The hardware adjacency
The system failed to allocate TCAM entry for an MPLS entry for the specified label.
C6K_MPLS_RP Messages
This section contains Catalyst 6500 series switch and Cisco 7600 series router LAN Multiprotocol Label
Switching (C6K_MPLS_RP) messages.
C6K_MPLS_RP-2
Error Message %C6K_MPLS_RP-2-NO_IP_ACL_RSVD_VLAN: IP ACL features will not be
applied to MPLS->IP packets due to a lack of internal VLAN resources
Explanation
shared by VLANs used for SVI, VLANS used for subinterfaces, hidden VLANs used for routed
ports, and internal VLANs used for some VRFs. An internal VLAN is needed when an IP ACL
feature is applied to a VRF interface. If the total number of VLANs in use exceeds 4096, no more
internal VLANs can be allocated, so IP ACL features will not be applied to MPLS-to-IP packets.
Recommended Action Reduce the total number of VLANs in use by removing SVI interfaces,
subinterfaces, and/or VRF interfaces.
The total number of VLANs in use might have exceeded 4096. The VLAN resources are
Error Message %C6K_MPLS_RP-2-NO_IP_QOS_RSVD_VLAN: IP QoS features will not be
applied to MPLS->IP packets due to a lack of internal VLAN resources
C6K_MPLS_RP Messages
C6K_MPLS_RP-3
Error Message %C6K_MPLS_RP-3-L2_CONFIG_NOT_RECOMMENDED: xconnect is configured on
interface vlans and WAN interfaces are facing the MPLS Core. Do not configure LAN
interfaces facing the MPLS Core.
Explanation
The total number of VLANs in use might have exceeded 4096. The VLAN resources are
shared by VLANs used for SVI, VLANS used for subinterfaces, hidden VLANs used for routed
ports, and internal VLANs used for some VRFs. An internal VLAN is needed when an IP QoS
feature is applied to a VRF interface. If the total number of VLANs in use exceeds 4096, no more
internal VLANs can be allocated, so IP QoS features will not be applied to MPLS-to-IP packets.
Recommended Action Reduce the total number of VLANs in use by removing SVI interfaces,
subinterfaces, and/or VRF interfaces.
Explanation
An attempt was made to configure a LAN interface to face the MPLS core. The current
network configuration has cross-connection services configured on interface VLANs and has WAN
interfaces facing the MPLS core.
Recommended Action Do not configure MPLS on LAN interfaces facing the MPLS core if the
network has cross-connection services configured on an interface VLAN and WAN interfaces that
face the MPLS core.
Error Message %C6K_MPLS_RP-3-L3_CONFIG_NOT_RECOMMENDED: LAN interfaces are facing
the MPLS Core. Do not configure xconnect on interface vlans.
Explanation
An attempt was made to configure a cross-connection service on an interface VLAN.
The current network configuration has MPLS configured on a LAN interface that is facing the MPLS
core.
Recommended Action Do not configure cross-connection services on an interface VLAN if the
This section contains general Catalyst 6500 series switch and Cisco 7600 series router platform
(C6K_PLATFORM) messages.
C6K_PLATFORM-0
Error Message %C6K_PLATFORM-0-UNKNOWN_CHASSIS: The chassis type is not known.([hex])
Chapter 2 Messages and Recovery Procedures
Explanation
specified in the error message.
Recommended Action Ensure that your Cisco IOS software release train supports the chassis type.
Upgrade your system to the latest Cisco IOS software release in your release train.
C6K_PLATFORM-2
Error Message %C6K_PLATFORM-2-PEER_RESET: [chars] is being reset by the [chars]
Explanation
exceptions.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the show logging and show tech-support commands and your
pertinent troubleshooting logs.
The Cisco IOS software installed on the system does not recognize the chassis type
The local CPU is being reset by the peer CPU when the peer CPU reloads because of
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the
This message provides information regarding the internal state of the SiByte processor.
OL-11469-02
Page 45
Chapter 2 Messages and Recovery Procedures
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the show logging and show tech-support commands and your
pertinent troubleshooting logs.
C6K_PLATFORM-4
Error Message %C6K_PLATFORM-4-CONFREG_BREAK_ENABLED : The default factory setting
for config register is 0x2102.It is advisable to retain 1 in 0x2102 as it prevents
returning to ROMMON when break is issued.
C6K_PLATFORM Messages
Explanation
The SP configuration register has been changed from the default factory setting of
0x2102 to another hexadecimal value.
Recommended Action No action is required.
Error Message %C6K_PLATFORM-4-ENVMON: System shutdown due to temperature alarms is
[chars].
Explanation
The system has a configuration to shut down a module if its operating temperature
exceeds a temperature threshold. This configuration has been bypassed, and a module will still
operate in an over-temperature condition. Operating at an over-temperature condition can damage
the hardware.
Recommended Action Do not override the sensor alarms that act on an over-temperature condition.
Enter the environment-monitor shutdown temperature command to bring the system back to
standard temperature detection.
Error Message %C6K_PLATFORM-4-RTC_OSCILLATOR: The oscillator in the Real Time Clock
is [chars]. Calendar [chars] be maintained during the powered down state of the
switch.
Explanation
A command has been entered that will cause the system calendar not to be maintained
during a power down of the switch. The system date and time will require manual setting when the
system is powered up during the next boot time. This command is useful to conserve the battery
power of the CMOS, which is used to keep the real-time clock active while the switch is powered
down. This condition is useful only if the switch is powered down for a long period of time.
Recommended Action If the switch need not be powered down for a long period of time, remove the
configuration by entering the no hw-module rtc-oscillator shutdown command.
Error Message %C6K_PLATFORM-5-LESS_SPACE : May not have enough space to save the
crash info. on flash of [chars] on module: [dec]
Chapter 2 Messages and Recovery Procedures
Explanation
It is possible that crash information could not be saved on the flash memory device.
Recommended Action Remove files from the flash memory device that may not be needed, and enter
the squeeze command for the flash memory device.
Error Message %C6K_PLATFORM-5-MISMATCH : '[chars]' device programming algorithm
mismatch detected on [chars] (module: [dec]), formatting is recommended.
Explanation
the flash memory was formatted is different from what the current running software has detected.
Recommended Action Reformat the flash memory device. Otherwise, no action is required.
The flash memory device does not have enough memory to save the crash information.
The flash memory device programming algorithm that was written to the device when
C6K_POWER Messages
This section contains Catalyst 6500 series switch and Cisco 7600 series router power (C6K_POWER)
messages. For more power messages, see the “C6KPWR Messages” section of this chapter.
C6K_POWER-3
2-16
Error Message %C6K_POWER-3-NOTIFY_FAIL: Failed to notify RP of change in operator
status for [chars] number [dec] from ’[chars]’ to ’[chars]’
Explanation
in 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 issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the show logging and show tech-support commands and your
pertinent troubleshooting logs.
The SP is unable to acquire the resources needed to notify the RP of the event specified
OL-11469-02
Page 47
Chapter 2 Messages and Recovery Procedures
C6K_POWER-4
Error Message %C6K_POWER-4-PD_NOLINKUP: The device connected to [dec]/[dec] is
powered up but its link is not up in [dec] seconds. Therefore, power is withdrawn
from the port.
C6K_PROCMIB Messages
Explanation
link was not operational in the specified number of seconds.
Recommended Action Try to connect the device to a different port or connect a different device to the
port specified in the message.
The system withdrew the power that was allocated to the specified port because the port
C6K_POWER-6
Error Message %C6K_POWER-6-NOLPP: Because of lack of system power, devices that
require the system to power them on may not come up within one second.
Explanation
the device until it has received authorization for power allocation from the software running on the
supervisor engine.
Recommended Action No action is required.
The local power pools have been deallocated. The module firmware cannot power up
C6K_PROCMIB Messages
This section contains Catalyst 6500 series switch and Cisco 7600 series router Process MIB SP CPU
(C6K_PROCMIB) messages.
C6K_PROCMIB-3
Error Message %C6K_PROCMIB-3-IPC_PORTOPEN_FAIL: Failed to open port while connecting
to process statistics: error code = [chars]
OL-11469-02
Explanation
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the show logging and show tech-support commands and your
pertinent troubleshooting logs.
An error occurred during an attempt to open a port for an IPC message.
Error Message %C6K_PROCMIB-3-IPC_TRANSMIT_FAIL: Failed to send process statistics
update : error code = [chars]
Chapter 2 Messages and Recovery Procedures
Explanation
Recommended Action Copy the message exactly as it appears on the console or in the system log.
An error occurred during an attempt to send an IPC message.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the show logging and show tech-support commands and your
pertinent troubleshooting logs.
Error Message %C6K_PROCMIB-3-MALLOC_FAILURE_IPC: Failed to allocate IPC message to
contact process
Explanation
Recommended Action Copy the message exactly as it appears on the console or in the system log.
A memory allocation failure occurred during the processing of an IPC message.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the show logging and show tech-support commands and your
pertinent troubleshooting logs.
C6K_WAN_C2W Messages
This section contains Catalyst 6500 series switch and Cisco 7600 series router WAN C2Wire
(C6K_WAN_C2W) messages.
C6K_WAN_C2W-4
Error Message %C6K_WAN_C2W-4-READERROR: C2Wire read failed reg [hex] on device
[chars]
Explanation
Recommended Action No action is required if this warning message appears occasionally. If the
message appears often in a short period of time, copy the message exactly as it appears on the
console or in the system log. Research and attempt to resolve the issue using the tools and utilities
provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply
clarifying information. Search for resolved software issues using the Bug Toolkit at
The SMbus driver failed to read from the specified C2W device.
OL-11469-02
Page 49
Chapter 2 Messages and Recovery Procedures
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the show logging and show tech-support commands and your
pertinent troubleshooting logs.
Recommended Action No action is required if this warning message appears occasionally. If the
message appears often in a short period of time, copy the message exactly as it appears on the
console or in the system log. Research and attempt to resolve the issue using the tools and utilities
provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply
clarifying information. Search for resolved software issues using the Bug Toolkit at
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the show logging and show tech-support commands and your
pertinent troubleshooting logs.
C6KENV Messages
This section contains Catalyst 6500 series switch and Cisco 7600 series router environmental
(C6KENV) messages.
C6KENV-2
The SMbus driver failed to write to the specified C2W device.
Error Message %C6KENV-2-BADFLOWCTRL: Module [dec] not at an appropriate hardware
revision level to support DFC. Power denied
Explanation
revision level and cannot support a DFC. If a DFC is present, the module will not be activated and
remains powered down.
Recommended Action Remove the DFC to enable the module to operate at its current hardware
revision level. To enable DFC operation, ensure that the module is at an appropriate hardware
revision level.
OL-11469-02
The fabric-capable module in the specified slot is not at an appropriate hardware
Error Message %C6KENV-2-BADFLOWCTRL_WARN: WARNING: Module [dec] not at an
appropriate hardware revision level to support DFC3
Explanation
The fabric-capable module in the specified slot is not at an appropriate hardware
revision level to support a DFC3 or higher.
Recommended Action When you upgrade the DFC daughter card, also upgrade the module to an
appropriate hardware revision level.
Error Message %C6KENV-2-BADPINN1: Module [dec] not at an appropriate hardware
revision level to coexist with PFC3 system. Power denied
Explanation
The module specified in the error message has a revision of 2.x or below. Modules with
this revision will experience problems when they are used with a supervisor engine with a PFC3
installed and they should not be used.
Recommended Action Upgrade the module to an appropriate hardware revision level.
Error Message %C6KENV-2-BADTRANSCEIVER: Module [dec] will be power disabled because
an inappropriate transceiver is inserted at [chars].
Explanation
An incompatible transceiver is inserted at the interface specified in the error message.
This transceiver should not be used in this system.
Recommended Action Remove the specified transceiver and restore power to the module. If this
transceiver was purchased from Cisco, contact your Cisco technical support representative to get the
transceiver replaced.
Error Message %C6KENV-2-C2PLUSWITHNODB: The constellation 2 plus module in slot
[dec] has no forwarding daughter board. Power denied
Explanation
The module in the slot specified has no forwarding daughter card and is expected to
have either a distributed, accelerated, or centralized forwarding card. This module will not be
activated and will remain powered down.
Recommended Action Enter the show module command to view error message details.
Error Message %C6KENV-2-DFCMISMATCH: Module [dec] DFC incompatible with Supervisor
DFC. Power denied
Explanation
The DFC in the specified module is different from the DFC in the supervisor engine.
The module will not be activated and remains powered down.
Recommended Action Enter the show module command to view the difference between the DFC in
the module and the DFC in the supervisor engine.
Error Message %C6KENV-2-DFCMISMATCHMINOR: Module [dec] DFC installed is incompatible
with system operating mode. Power denied. To enable Module [dec] DFC, the system
must be reset.
WARNING: Any system reset will change the system operating mode which can result
in degradation of system performance. To eliminate this from occurring, remove
Module [dec] DFC or replace with a system compatible DFC.
C6KENV Messages
Explanation
The DFC in the specified slot does not have the same software operating mode as the
rest of the system. The DFC will remain powered down and cannot be activated.
Recommended Action Enter the show module and show platform earl-mode commands to view the
difference between the DFC in the specified slot and the operating mode of the rest of the system.
Error Message %C6KENV-2-FANUPGREQ: Module [dec] not supported without fan upgrade
Explanation
The supervisor engine and the DFC in the specified slot require a fan tray upgrade. A
system shutdown is scheduled.
Recommended Action Upgrade the system fan tray.
Error Message %C6KENV-2-SHUTDOWN_NOT_SCHEDULED: Major sensor alarm for [chars] is
ignored, [chars] will not be shutdown.
Explanation
The system detected that the specified module should be shut down because it exceeded
major sensor thresholds. However, the command that shuts down the module in the event of a major
sensor alarm has been overridden, so the specified module will not be shut down. The command used
to override the shutdown is no environment-monitor shutdown.
Recommended Action Remove the configuration that bypasses the module shutdown due to sensor
thresholds being exceeded. Shut down the module after removing the configuration.
Error Message %C6KENV-4-FANCOUNTFAILED: Required number of fan trays is not present
Explanation
The specified alarm condition has been cleared. The shutdown has been cancelled.
The system is missing the number of required fan trays to operate properly. Although
this is a minor alarm, system components could overheat and be shut down.
Recommended Action Insert the required fan tray as soon as possible.
Error Message %C6KENV-4-FANCOUNTOK: Required number of fan trays is present
Explanation
Recommended Action No action is required.
The number of required fan trays has been restored.
Error Message %C6KENV-4-FANHIOUTPUT: Version [dec] high-output fan-tray is in effect
Explanation
The system has detected that the fan tray is a high-output (version 2) fan tray. The
system has updated the cooling capacity for the fan tray.
Recommended Action No action is required.
Error Message %C6KENV-4-FANLOOUTPUT: Version [dec] low-output fan-tray is in effect
Explanation
The system has detected that the fan tray is a low-output (version 1) fan tray. The system
has updated the cooling capacity for the fan tray.
Recommended Action No action is required.
Error Message %C6KENV-4-FANPSINCOMPAT: Fan tray and power supply [dec] are
incompatible
Explanation
An upgrade of the power supply is required to sufficiently operate this fan tray.
Although this is a minor alarm, overcurrent protection on the power supply could start without
further warning.
Recommended Action Upgrade the power supply.
Error Message %C6KENV-4-FANVERCHK: Power-supply [dec] inserted is only compatible
with Version [dec] fan-tray. Please make sure fan is low-output fan-tray
Explanation
The system has detected that the fan tray is a low-output (version 1) fan tray. If the fan
tray is a low-output tray, no action is required. If the fan tray is actually a high-output (version 2)
fan tray, the specified power supply is not able to support the high-output fan tray.
Recommended Action If the fan tray is a high-output (version 2) fan tray, enter the hw-module
fan-tray version 2 command to update the system with the upgrade information. Replace the 1000
W or 1300 W power supply, as these two power supplies are not compatible in this chassis with the
version 2 fan tray.
Error Message %C6KENV-4-INSUFFCOOL: Module [dec] cannot be adequately cooled
Explanation
The fan tray cannot adequately cool the specified module. Although this is a minor
alarm, system components could overheat and be shut down.
Recommended Action Upgrade the system fan tray.
Error Message %C6KENV-4-MINORTEMPOKALARM: [chars] all temperature sensor have
failed. If the module temperature sensor does not recover by itself, please power
cycle the module when it is feasible
Explanation
Recommended Action If the module temperature sensors do not recover, power cycle the module
This section contains Catalyst 6500 series switch and Cisco 7600 series router power (C6KPWR)
messages.
C6KPWR-2
Error Message %C6KPWR-2-INSUFFICIENTPOWER: Powering down all linecards as there is
not enough power to operateall critical cards
Chapter 2 Messages and Recovery Procedures
Explanation
The switch was operating with two power supplies in combined mode. One of the power
supplies has failed. Available power is insufficient to support all critical service modules. Critical
service modules include modules that support VPNs or IP security. If these critical modules fail,
security issues could arise; therefore, all modules have been powered down.
Recommended Action Replace the failed power supply.
Error Message %C6KPWR-2-MAJORPOWERALARM: In the absence of power supply 1, system
power usage exceeds allowed range of [chars]W. Power total will be reduced in [dec]
seconds
Explanation
The power supply in slot 2 has exceeded its allowed range, causing a major power alarm.
The range is specified in the error message.
Recommended Action Enter the show power command to determine the actual power usage. Insert a
power supply in power supply slot 1, or power down some modules to reduce system power usage.
If downtime can be scheduled, move the power supply from slot 2 to slot 1. If this condition persists,
the environmental monitor will shut down some modules to prevent a complete power failure.
Error Message %C6KPWR-2-MAJORPOWERALARMRECOVER: System power usage has returned to
allowed operating range
Explanation
System power usage has returned to the permitted operating range. The scheduled
shutdown is cancelled, and the system will continue operating.
Recommended Action No action is required.
Error Message %C6KPWR-2-MINORPOWERALARM: In the absence of power supply 1, system
power usage exceeds the recommended range of [chars]W
Explanation
The power supply in slot 2 has exceeded its allowed range, causing a minor power
alarm. The range is specified in the error message. Selected modules will be shut down to prevent a
complete power failure.
Recommended Action Enter the show power command to determine the actual power usage. Insert a
power supply in power supply slot 1, or power down some modules to reduce system power usage.
If downtime can be scheduled, move the power supply from slot 2 to slot 1.
Error Message %C6KPWR-3-PSUNKNOWN: Unknown power supply in slot [dec] (idprom read
failed).
C6KPWR Messages
C6KPWR-4
Explanation
Recommended Action Remove and reinsert the power supply. Fasten the screw, and attempt to operate
The IDPROM of the power supply in the specified slot cannot be read.
the power supply again. 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 issue using the tools and utilities provided
at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the
Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or
contact your Cisco technical support representative and provide the representative with the
information you have gathered. Attach the following information to your case in nonzipped,
plain-text (.txt) format: the output of the show logging and show tech-support commands and your
pertinent troubleshooting logs.
Error Message %C6KPWR-4-INPUTCHANGE: Power supply [dec] input has changed. Power
capacity adjusted to [chars]W
Explanation
The power supply in the specified slot has detected a change in its input supply. The
power capacity for the power supply has been adjusted accordingly.
Recommended Action Enter the show power command to see the current power status. Otherwise, no
action is required.
Error Message %C6KPWR-4-MAJORPOWERALARMRECOVER: System power usage has returned to
allowed operating range
Explanation
shutdown was cancelled. The system will continue operating.
Recommended Action No action is required.
Error Message %C6KPWR-4-MINORPOWERALARM: In the absence of power supply 1, system
power usage exceeds the recommended range of [chars]W
Explanation
alarm. The range is specified in the error message. Selected modules will be shut down to prevent a
complete power failure.
Recommended Action Enter the show power command to determine the actual power usage. Insert a
power supply in power supply slot 1, or power down some modules to reduce system power usage.
If downtime can be scheduled, move the power supply from slot 2 to slot 1.
OL-11469-02
System power usage has returned to the allowed operating range, so the scheduled
The power supply in slot 2 has exceeded its allowed range, causing a minor power
Error Message %C6KPWR-4-MINORPOWERALARMRECOVER: System power usage has returned to
normal operating range
Explanation
Recommended Action No action is required.
Error Message %C6KPWR-4-PS1FAILALERT: Do not remove power supply 1 without inserting
another supply. In the absence of power supply 1, system power capacity will be
reduced to [chars]W after a [dec] second grace period.
Explanation
System power usage has returned to the normal operating range.
The system is experiencing heavy traffic. In this condition, the single power supply
should be used in slot 1 rather than in slot 2.
Recommended Action Insert a power supply in slot 1, or move the power supply from slot 2 to slot 1.
Error Message %C6KPWR-4-PS2ONLY: Single power supply system should utilize power
supply slot 1
Explanation
The system is experiencing heavy traffic. In this condition, the single power supply
should be used in slot 1 rather than in slot 2.
Recommended Action Move the power supply from slot 2 to slot 1.
Error Message %C6KPWR-4-PSINPUTDROP: Power supply [dec] input has dropped
Explanation
The power supply in the specified slot has detected a drop in its input supply. The power
capacity for the power supply has been adjusted accordingly.
Recommended Action Enter the show power command to see the current power status. Otherwise, no
action is required.
Error Message %C6KPWR-4-PSMISMATCH: power supplies rated outputs do not match.
Explanation
Recommended Action For more efficient load sharing, use power supplies with the same output
The two power supplies in the system have different output ratings.
rating.
Error Message %C6KPWR-4-PSNOREDUNDANCY: Power supplies are not in full redundancy,
power usage exceeds lower capacity supply
Explanation
The two power supplies in the system have different output ratings. Current power usage
exceeds the capacity of the lower-rated power supply. If the higher-rated power supply fails, the
lower-rated power supply will not be able to support all modules that are currently powered up.
Recommended Action To ensure that the system power supplies are optimally redundant, use power
supplies with identical output ratings or reduce system power consumption.