Catalyst 3750 Switch System Message Guide, Rel. 12.1(19)EA1, February 2004
System Message Overview
Downloads: This chapterpdf (PDF - 198.0 KB) The complete bookPDF (PDF - 1.15 MB) | Feedback

System Message Overview

Table Of Contents

System Message Overview

How to Read System Messages

Error Message Traceback Reports

Output Interpreter

Bug Toolkit

Contacting TAC

System Message Overview

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

Note For information about system messages that are not Catalyst 3750 platform-specific, refer to the Cisco IOS Software System Messages for Cisco IOS Release 12.1.

This chapter contains these sections:

How to Read System Messages

Error Message Traceback Reports

How to Read System Messages

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

seq no:timestamp: %facility-severity-MNEMONIC:description (hostname-n)

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

Each system message begins with a percent sign (%) and is structured as follows:


FACILITY is a code consisting of two or more uppercase letters that show the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software. Table 1-1 lists Catalyst 3750-specific facility codes. These messages are described in "Message and Recovery Procedures," in alphabetical order by facility code with the most severe (lowest number) errors described first.

Table 1-1 Facility Codes 

Facility Code


ACL Manager

"ACLMGR Messages" section


Configuration Manager

"CFGMGR Messages" section


Cluster Membership Protocol

"CMP Messages" section


IEEE 802.1X messages

"DOT1X (802.1X) Messages" section


Dynamic Trunking Protocol

"DTP Messages" section



"EC Messages" section


Ethernet Controller

"ETHCNTR Messages" section


Express Setup

"EXPRESS_SETUP Messages" section


GBIC/SFP module security

Note These errors refer to small-form factor pluggable (SFP) modules.

"GBIC/SFP Security Messages" section



"HARDWARE Messages" section


HULC Local Forwarding Manager

"HLFM Messages" section


Interface Description Block Manager

"IDBMAN Messages" section


Power over Ethernet (PoE)

"ILPOWER (Power over Ethernet) Messages" section


Image Manager

"IMAGEMGR Messages" section



"PHY Messages" section


Low-level Platform-specific

"PLATFORM Messages" section


Platform Fallback Bridging Manager

"PLATFORM_FBM Messages" section


Platform Inter-Process Communication protocol

"PLATFORM _IPC Messages" section


Platform Policy-Based Routing

"PLATFORM_PBR Messages" section


Platform Port Manager

"PLATFORM_PM Messages" section


Platform Remote Procedure Call

"PLATFORM_RPC Messages" section


Platform Switched Port Analyzer

"PLATFORM_SPAN Messages" section


Platform Unicast Routing

"PLATFORM_UCAST Messages" section


Platform VLAN

"PLATFORM_VLAN Messages" section


Port Manager

"PM Messages" section


QoS Manager

"QOSMGR Messages" section


Switch Database Manager

"SDM Message" section


Switched Port Analyzer

"SPAN Messages" section


Spanning Tree

"SPANTREE Messages" section


Spanning-tree Fast Convergence

"SPANTREE_FAST Messages" section


Spanning-tree VLAN Switch

"SPANTREE_VLAN_SW Messages" section


Stack Manager

"STACKMGR Messages" section


Supervisor ASIC

"SUPERVISOR Messages" section


Supervisor Queue

"SUPQ Messages" section


VLAN Manager

"SW_VLAN Messages" section


Ternary Content Addressable Memory Manager

"TCAMMGR Messages" section


UniDirectional Link Detection

"UDLD Messages" section


Uplink Fast Packet Transmission

"UFAST_MCAST_SW Messages" section


VLAN Query Protocol Client

"VQPCLIENT Messages" section

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 lists the message severity levels.

Table 1-2 Message Severity Levels 

Severity Level

0 - emergency

System is unusable.

1 - alert

Immediate action required.

2 - critical

Critical condition.

3 - error

Error condition.

4 - warning

Warning condition.

5 - notification

Normal but significant condition.

6 - informational

Informational message only.

7 - debugging

Message that appears during debugging only.

MNEMONIC is a code that uniquely identifies the message.

Message-text is a text string describing the condition. This portion of the message sometimes contains detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets ([ ]). A decimal number, for example, is represented as [dec]. Table 1-3 lists the variable fields in messages.

Table 1-3 Representation of Variable Fields in Messages 

Type of Information


Decimal integer


Single character


Character string


Ethernet address (for example, 0000.FEED.00C0)


Hexadecimal integer


Internet address

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

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

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

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

Error Message Traceback Reports

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

This message example includes traceback information:

-Process= "Exec", level= 0, pid= 17
-Traceback= 1A82 1AB4 6378 A072 1054 1860 

Some system messages ask you to copy the error messages and take further action. These online tools also provide more information about system error messages.

Output Interpreter

The Output Interpreter provides additional information and suggested fixes based on the output of many CLI commands, such as the the show tech-support privileged EXEC command. You can access the Output Interpreter at this URL:

Bug Toolkit

The Bug Toolkit provides information on open and closed caveats, and allows you to search for all known bugs in a specific Cisco IOS Release. You can access the Bug Toolkit at this URL:

Contacting TAC

If you cannot determine the nature of the error, see the "Obtaining Technical Assistance" section for further information.