Network OS Message Reference, 3.0.1 - Brocade

53-1002807-0117 December 2012®Network OSMessage ReferenceSupporting Network OS v3.0.1

TitlePublicationnumberSummary of changesDateNetwork OS Message Reference 53-1002489-01 Updated for Network OS v2.1.1:• Added new chapters: AUTH, C2, ELD,RCS, and TS.• Added new messages: L2SS, PORT,SEC, and SSMD.• Modified messages: L2SS, SEC, andZONE.Network OS Message Reference 53-1002559-01 Updated for Network OS v3.0.0:• Added new chapters: BL, BLL, C3,CHS, ERCP, ESS, FABS, FCMC, FCPH,FLOD, FSPF, FSS, HASM, HAWK, HLO,KTRC, L2AG, LSDB, MCAST_SS,MPTH, MS, NBFS, NS, OSPF, PDM,RTM, SCN, SLCD, SWCH, UCST,UPTH, VRRP, and WLV.• Added new messages: AUTH, C2,DCM, EM, FABR, FVCS, FW, HIL,IPAD, L2SS, MSTP, NSM, and ONMD.• Modified messages: DOT1, EANV,ELD, FCOE, HSL, IGMP, LOG, MSTP,NSM, ONMD, PHP, PLAT, PORT, RAS,RCS, RTWR, SEC, SFLO, SNMP, SS,SSMD, SULB, TOAM, TRCE, TS, VC,VCS, and ZONE.• Deleted chapters: HAM and L3SS.Network OS Message Reference 53-1002807-01 Updated for Network OS v3.0.1:• Added new chapter: LACP.• Added new messages: EM, PORT,RAS, SEC, TS, and VC.• Modified messages: BL, HASM,SNMP.• Deleted messages: RTM.December 2011September 2012December 2012

Viewing and clearing the RASLog messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Displaying the RASLog messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Displaying the messages on an interface module. . . . . . . . . . . . . . . . . . . .12Clearing the RASLog messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Viewing and clearing the SYSTEM messages. . . . . . . . . . . . . . . . . . . . . . . .12Viewing and clearing the DCE messages . . . . . . . . . . . . . . . . . . . . . . . . . . .13Displaying the VCS messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Displaying the FFDC messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Viewing, clearing, and configuring Audit log messages . . . . . . . . . . . . . . . . . . . 14Displaying the Audit messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Clearing the Audit messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Configuring event auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Understanding the RASLog messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16RASLog messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Audit event messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Responding to a RASLog message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Looking up a message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Gathering information about the problem . . . . . . . . . . . . . . . . . . . . . . . . . .18Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19System module descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Chapter 2Chapter 3Chapter 4Chapter 5Chapter 6Chapter 7Log MessagesDCE MessagesFFDC MessagesAudit MessagesVCS MessagesNetwork OS MessagesAUTH Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65BL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79BLL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93C2 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94C3 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97CHS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100DCM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102viNetwork OS Message Reference53-1002807-01

DOT1 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115EANV Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120ELD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122EM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123ERCP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138ESS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139FABR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140FABS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146FCMC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151FCOE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152FCPH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157FLOD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158FSPF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160FSS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163FVCS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167FW Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173HASM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200HAWK Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211HIL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212HLO Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217HSL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219IGMP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221IPAD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223KTRC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225L2AG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227L2SS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230LACP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234LOG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235LSDB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238MCAST_SS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240MPTH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247MS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248MSTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249NBFS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253NS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255NSM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256ONMD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278Network OS Message Reference53-1002807-01vii

About This DocumentIn this chapter•How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix•Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x•What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x•Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi•Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii•Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii•Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii•Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiHow this document is organizedThis document supports Brocade Network OS v3.0.1 and documents RASLog messages that canhelp you diagnose and fix problems with a switch or network. The guide is organized alphabeticallyby module name. A module is a subsystem in the Network OS. Each module generates a set ofnumbered messages. For each message, this guide provides message text, message type, severitylevel, probable cause, and recommended action. There may be more than one cause and morethan one recommended action for any given message. This guide discusses the most probablecause and typical action recommended.This document is organized to help you find the information that you want as quickly and easily aspossible. The document contains the following components:• Chapter 1, “Introduction to RASLog Messages” provides basic information on RASLogmessages.• Chapter 2, “Log Messages” includes a lookup list for LOG messages.• Chapter 3, “DCE Messages” includes a lookup list for DCE messages.• Chapter 4, “FFDC Messages” includes a lookup list for FFDC messages.• Chapter 5, “Audit Messages” includes a lookup list for Audit messages.• Chapter 6, “VCS Messages” includes a lookup list for VCS messages.• Chapter 7, “Network OS Messages” provides message text, probable cause, recommendedaction, and severity for each of the messages.Network OS Message Reference53-1002807-01ix

Supported hardware and softwareIn those instances in which procedures or parts of procedures documented here apply to someswitches but not to others, this guide identifies exactly which switches are supported and which arenot.Although many different software and hardware configurations are tested and supported byBrocade Communications Systems, Inc. for Network OS v3.0.1, documenting all possibleconfigurations and scenarios is beyond the scope of this document.The following hardware platforms are supported by this release of Network OS:• Brocade VDX 6710-54• Brocade VDX 6720- Brocade VDX 6720-24- Brocade VDX 6720-60• Brocade VDX 6730- Brocade VDX 6730-32- Brocade VDX 6730-76• Brocade VDX 8770- Brocade VDX 8770-4- Brocade VDX 8770-8What’s new in this documentThe following changes have been made since this document was last released:• Information that was added:- EM Messages- LACP Messages- PORT Messages- RAS Messages- SEC Messages- TS Messages- VC Messages• Information that was changed:- BL Messages- HASM Messages- SNMP Messages• Information that was deleted:- RTM MessagesxNetwork OS Message Reference53-1002807-01

Key termsFor definitions specific to Brocade and Fibre Channel, see the technical glossaries on MyBrocade.See “Brocade resources” on page xii for instructions on accessing MyBrocade.For definitions of SAN-specific terms, visit the Storage Networking Industry Association onlinedictionary at:http://www.snia.org/education/dictionaryNotice to the readerThis document may contain references to the trademarks of the following corporations. Thesetrademarks are the properties of their respective companies and corporations.These references are made for informational purposes only.CorporationMicrosoft CorporationRed Hat, Inc.Referenced trademarks and productsWindowsRed Hat package manager (RPM)Additional informationThis section lists additional Brocade and industry-specific documentation that you might findhelpful.Brocade resourcesTo get up-to-the-minute information, go to http://my.brocade.com and register at no cost for a userID and password.White papers, online demonstrations, and data sheets are available through the Brocade websiteat:http://www.brocade.com/products-solutions/products/index.pageFor additional Brocade documentation, visit the Brocade website:http://www.brocade.comOther industry resourcesFor additional resource information, visit the Technical Committee T11 website. This websiteprovides interface standards for high-performance and mass storage applications for FibreChannel, storage management, and other applications:http://www.t11.orgxiiNetwork OS Message Reference53-1002807-01

For information about the Fibre Channel industry, visit the Fibre Channel Industry Associationwebsite:http://www.fibrechannel.orgGetting technical helpContact your switch support supplier for hardware, firmware, and software support, includingproduct repairs and part ordering. To expedite your call, have the following information available:1. General Information• Switch model• Switch operating system version• Software name and software version, if applicable• Error numbers and messages received• copy support command output• Detailed description of the problem, including the switch or network behavior immediatelyfollowing the problem, and specific questions• Description of any troubleshooting steps already performed and the results• Serial console and Telnet session logs• syslog message logs2. Switch Serial NumberThe switch serial number and corresponding bar code are provided on the serial number label,as illustrated below.The serial number label for the Brocade VDX 6710, Brocade VDX 6720, Brocade VDX 6730,and Brocade VDX 8770 is located on the switch ID pull-out tab located on the bottom of theport side of the switch.Document feedbackQuality is our first concern at Brocade and we have made every effort to ensure the accuracy andcompleteness of this document. However, if you find an error or an omission, or you think that atopic needs further development, we want to hear from you. Forward your feedback to:documentation@brocade.comProvide the title and version number of the document and as much detail as possible about yourcomment, including the topic heading and page number and your suggestions for improvement.Network OS Message Reference53-1002807-01xiii

xivNetwork OS Message Reference53-1002807-01

Introduction to RASLog MessagesChapter1In this chapter•Overview of RASLog messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1•Configuring the syslog message destinations . . . . . . . . . . . . . . . . . . . . . . . . . 5•Configuring the SNMP server hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8•Commands for displaying, clearing, and configuring the message logs . . . 10•Viewing and clearing the RASLog messages . . . . . . . . . . . . . . . . . . . . . . . . . 11•Viewing, clearing, and configuring Audit log messages . . . . . . . . . . . . . . . . 14•Understanding the RASLog messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16•Responding to a RASLog message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18•System module descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Overview of RASLog messagesRASLog messages log system events related to configuration changes or system error conditions.Messages are reported at various levels of severity ranging from informational (INFO) to escalatingerror levels (WARNING, ERROR, and CRITICAL). Network OS maintains two separate internalmessage storage repositories, SYSTEM and DCE. Table 1 shows the message types stored in eachof the two repositories. A RASLog message can have one or more type attributes. For example, amessage can be of type DCE, FFDC, and AUDIT. A message cannot have both LOG and DCE typeattributes.TABLE 1Message typeMessage type matrixDCE messagerepositorySYSTEM messagerepositoryLOG No YesDCE Yes NoFFDC Yes YesVCS Yes YesAUDIT Yes YesRASLog message typesNetwork OS supports five types of RASLog messages. The following sections describe in detail themessage types.Network OS Message Reference 153-1002807-01

1Overview of RASLog messagesSystem messagesSystem or LOG messages report significant system-level events or information and are also used toshow the status of the high-level user-initiated actions. System messages are stored in a separatenonvolatile storage and are preserved across the firmware upgrade or downgrade. The systemmessages are forwarded to the console, to the configured syslog servers, and through the SNMPtraps or informs to the SNMP management station.The following is an example of a system message.2011/08/23-22:58:12, [EM-1036], 4,, WARNING, VDX6720-24, Fan 1 is not accessible.For information on displaying and clearing the system messages, refer to “Viewing and clearing theSYSTEM messages” on page 12.DCE RASLog messagesDCE RASLog messages report error-related events and information in the protocol-based modulessuch as network service module (NSM), system services manager (SSM), and so on. DCEmessages are stored in a separate nonvolatile storage and are preserved across the firmwareupgrades. The DCE messages are forwarded to the console, to the configured syslog servers, andthrough the SNMP traps or informs to the SNMP management station.NOTEDCE messages are supported only in Network OS v3.0.0 and later. If you downgrade to an earlierfirmware version, the DCE messages will be dropped.The following is an example of a DCE message.2012/05/30-21:25:55, [ONMD-1002], 59, M1 | DCE, INFO, sw0, LLDP globalconfiguration is changed.For information on displaying and clearing the DCE RASLog messages, refer to “Viewing andclearing the DCE messages” on page 13.VCS RASLog messagesVCS RASLog messages are supported in VCS fabrics only. The VCS RASLog messages are used toindicate events such as node removal and node join from the Brocade VCS fabric. When a switchgenerates a VCS RASLog message, it is forwarded to the system console, remote syslog, and SNMPmanagement station.The following is an example of a VCS RASLog message.2011/08/26-12:40:01, [VCS-1003], 7013/3454, VCS, INFO, VDX6720-60, Event: VCSnode add, Coordinator IP: 10.17.10.31, VCS ID: 1, Status: rBridge ID 1(10.17.10.32) added to VCS cluster., VcsFabAddRejoin, line: 1450, comp:dcmd,ltime:2011/06/27-02:47:04:555942.You can display the VCS RASLog messages using the show logging raslog attribute VCS command.For information on displaying the VCS RASLog messages, refer to “Displaying the VCS messages”on page 14.2 Network OS Message Reference53-1002807-01

Overview of RASLog messages 1Audit log messagesEvent auditing is designed to support post-event audits and problem determination based onhigh-frequency events of certain types, such as security violations, firmware downloads, andconfiguration. Audit log messages are saved in the persistent storage. The storage has a limit of1024 entries and will wrap around if the number of messages exceed the limit. The switch can beconfigured to stream Audit messages to the specified syslog servers. The Audit log messages arenot forwarded to an SNMP management station.The following is an example of an Audit log message.AUDIT,2011/08/26-07:51:32 (GMT), [DCM-2001], INFO, DCMCFG,root/none/127.0.0.1/rpc/cli,, VDX6720-24, Event: noscli start, Status: success,Info: Successful login attempt through console from 127.0.0.1.For any given event, Audit messages capture the following information:• User Name - The name of the user who triggered the action.• User Role - The access level of the user, such as root or admin.• Event Name - The name of the event that occurred.• Status - The status of the event that occurred: success or failure.• Event Info - Information about the event.The three event classes described in Table 2 can be audited.TABLE 2 Event classes of the Audit messagesEvent class Operand DescriptionDCMCFG CONFIGURATION You can audit all the configuration changes in the Network OS.FIRMWARE FIRMWARE You can audit the events occurring during the firmware download process.SECURITY SECURITY You can audit any user-initiated security event for all management interfaces.For events that have an impact on the entire network, an audit is generatedonly for the switch from which the event was initiated.You can enable event auditing by configuring the syslog daemon to send the events to a configuredremote host using the logging syslog-server command. You can set up filters to screen outparticular classes of events using the logging auditlog class command (the classes includeSECURITY, CONFIGURATION, and FIRMWARE). All the Audit classes are enabled by default. Thedefined set of Audit messages are sent to the configured remote host in the Audit message format,so that they are easily distinguishable from other syslog events that may occur in the network. Fordetails on how to configure event auditing, refer to “Configuring event auditing” on page 15.FFDC messagesFirst Failure Data Capture (FFDC) is used to capture failure-specific data when a problem or failureis first noted and before the switch reloads or the trace and log buffer get wrapped. All subsequentiterations of the same error are ignored. This critical debug information is saved in nonvolatilestorage and can be retrieved by executing the copy support command. The data are used fordebugging purposes. FFDC is intended for use by Brocade technical support.FFDC is enabled by default. Execute the support command to enable or disable FFDC. If FFDC isdisabled, the FFDC daemon does not capture any data, even when a message with FFDC attributesis logged.Network OS Message Reference 353-1002807-01

Configuring the syslog message destinations 1Configuring the syslog message destinationsYou can configure a switch to send the syslog messages to the following output locations: syslogdaemon, system console, and SNMP management station.System logging daemonThe system logging daemon (syslogd) is a process on UNIX, Linux, and some Windows systems thatreads and logs messages as specified by the system administrator.Network OS can be configured to use a UNIX-style syslogd process to forward system events anderror messages to log files on a remote host system. The host system can be running UNIX, Linux,or any other operating system that supports the standard syslogd functionality. All the RASLogmessages are forwarded to the syslogd. Configuring for syslogd involves configuring the host,enabling syslogd on the Brocade model, and optionally, setting the facility level.Configuring a syslog serverTo configure the switch to forward all RASLog messages to the syslogd of one or more servers,perform the following steps.1. Execute the configure terminal command to access the global configuration level of the CLI.switch# configure terminalEntering configuration mode terminal2. Execute the logging syslog-server IP address command to add a server to which the messagesare forwarded. You can configure a syslog server in both IPv4 or IPv6 format. The followingexample is for configuring a syslog server with IPv4 address.switch(config)# logging syslog-server 192.0.2.2You can configure up to four syslog servers to receive the syslog messages.3. Execute the show running-config logging syslog-server command to verify the syslogconfiguration on the switch.switch# show running-config logging syslog-serverlogging syslog-server 192.0.2.2The following example configures a syslog server with an IPv6 address.switch# configure terminalEntering configuration mode terminalswitch(config)# logging syslog-server 2001:DB8::32switch(config)# exitswitch# show running-config logging syslog-serverlogging syslog-server 2001:db8::32You can remove a configured syslog server using the no logging syslog-server IP address command.Setting the syslog facilityThe syslog facility is a configurable parameter that specifies the log file to which messages areforwarded. You must configure the syslog servers to receive system messages before you canconfigure the syslog facility.Network OS Message Reference 553-1002807-01

1Configuring the syslog message destinationsTo set the syslog facility, perform the following steps.1. Execute the configure terminal command to access the global configuration level of the CLI.switch# configure terminalEntering configuration mode terminal2. Execute the logging syslog-facility local log_level command to set the syslog facility to aspecified log file.The log_level specifies the syslog facility and can be a value from LOG_LOCAL0 throughLOG_LOCAL7. The default syslog level is LOG_LOCAL7. The following example is for setting thesyslog facility level to LOG_LOCAL2.switch(config)# logging syslog-facility local LOG_LOCAL23. Execute the show running-config logging syslog-facility command to verify the syslog facilityconfiguration on the switch.switch# show running-config logging syslog-facilitylogging syslog-facility local LOG_LOCAL2You can reset the syslog facility to the default (LOG_LOCAL7) using the no logging syslog-facilitylocal command.System consoleThe system console displays all RASLog messages, Audit messages (if enabled), and panic dumpmessages. These messages are mirrored to the system console; they are always saved in one ofthe message logs.The system console displays messages only through the serial port. If you log in to a switch throughthe Ethernet port or modem port, you will not receive system console messages.You can filter messages that display on the system console by severity using the logging raslogconsole command. All messages are still sent to the system message log, syslog (if enabled), andSNMP management station.Setting the RASLog console severity levelYou can limit the types of messages that are logged to the console using the logging raslog consolecommand. The RASLog messages displayed on the console are passed up to and above theconfigured severity level. For example, if you configure the console severity level to ERROR, thenonly ERROR and CRITICAL messages pass through. You can choose one of the following severitylevels: INFO, WARNING, ERROR, or CRITICAL.The default severity level is INFO.To set the severity levels for the RASLog console, perform the following steps.1. Execute the configure terminal command to access the global configuration level of the CLI.switch# configure terminalEntering configuration mode terminal2. Execute the logging rbridge-id rbridge-id raslog console severity level command to set theRASLog console severity level.6 Network OS Message Reference53-1002807-01

Configuring the syslog message destinations 1The severity level can be one of the following: WARNING, ERROR, or CRITICAL. The severity levelvalues are case-sensitive. For example, to set the console severity level to ERROR on switch 1,enter the following command.switch(config)# logging rbridge-id 1 raslog console ERROR3. Execute the copy running-config startup-config command to save the configuration changes.You can reset the console severity level to the default (INFO) using the no logging rbridge-idrbridge-id raslog console command.SNMP management stationWhen an unusual event, error, or a status change occurs on the device, an event notification is sentto the SNMP management station. Network OS v3.0.1 supports two types of event notifications:traps (in SNMPv1, SNMPv2c, and SNMPv3) and informs (in SNMPv3).SNMP trapsAn unsolicited message that comes to the management station from the SNMP agent on thedevice is called a trap. When an event occurs and if the event severity level is at or below the setseverity level, the SNMP trap, swEventTrap, is sent to the configured trap recipients. The VarBind inthe Trap Data Unit contains the corresponding instance of the event index, time information, eventseverity level, the repeat count, and description. The possible severity levels are as follows:• Critical• Debug• Error• Info• None• WarningBy default, the severity level is set to None, implying all traps are filtered and therefore no eventtraps are received. When the severity level is set to Info, all traps with the severity level of Info,Warning, Error, and Critical are received.NOTEThe Audit log messages are not converted into swEventTrap.The SNMP traps are unreliable because the trap recipient does not send any acknowledgmentwhen it receives a trap. Therefore, the SNMP agent cannot determine if the trap was received.Brocade switches send traps out on UDP port 162. To receive traps, the management station IPaddress must be configured on the switch. You can configure the SNMPv1, SNMPv2c, and SNMPv3hosts to receive the traps. For more information, refer to “Configuring the SNMP (version 1 orversion 2c) server host” on page 9.Network OS Message Reference 753-1002807-01

1Configuring the SNMP server hostsSNMP informsAn SNMP inform is similar to the SNMP trap except that the management station that receives anSNMP inform acknowledges the system message with an SNMP response PDU. If the sender doesnot receive the SNMP response, the SNMP inform request can be sent again. An SNMP informrequest is saved in the switch memory until a response is received or the request times out. TheSNMP informs are more reliable and they consume more resources in the device and in thenetwork. Use SNMP informs only if it is important that the management station receives all eventnotifications. Otherwise, use the SNMP traps.Brocade devices support SNMPv3 informs. For more information, refer to “Configuring the SNMPv3server” on page 9.Port logsThe Network OS maintains an internal log of all port activity. Each switch maintains a log file foreach port. Port logs are circular buffers that can save up to 8,000 entries per switch. When the logis full, the newest log entries overwrite the oldest log entries. Port logs capture switch-to-device,device-to-switch, switch-to-switch, some device A-to-device B, and control information. Port logs arenot persistent and are lost across power cycles and reboots.Port log functionality is completely separate from the system message log. Port logs are typicallyused to troubleshoot device connections.Configuring the SNMP server hostsNetwork OS v3.0.1 supports SNMP version 1, version 2c, and version 3. Use the commands listedin Table 4 to configure the SNMPv1, SNMPv2c, and SNMPv3 hosts and their configurations.TABLE 4CommandCommands for configuring SNMP server hostsDescription[no] snmp-server host {ipv4 host |ipv6-host | dns} community-string[severity-level [None |Debug | Info | Warning | Error | Critical][udp-port port_number] [version [1 | 2c][no] snmp-server v3host {ipv4-host |ipv6-host | dns} username [notifytype{traps | informs}] engineid engine-idseverity-level [None | Debug | Info |Warning | Error | Critical] udp-portport_numberThis command sets the destination IP addresses, version, communitystring (for version 1 and version 2c), and destination port for thetraps.The severity-level option is used to filter the traps based on severity.The no form of the command changes the SNMP server hostconfigurations to the default value.This command specifies the recipient of the SNMP version 3notification option.The severity-level option is used to filter the traps or informs based onseverity.Use the no form of the command to remove the specified host.8 Network OS Message Reference53-1002807-01

Configuring the SNMP server hosts 1Configuring the SNMP (version 1 or version 2c) server hostTo set the trap destination IP addresses, version (1 or 2c), community string for SNMP version 1and version 2c, and the destination port for the SNMP traps, perform the following steps.1. Execute the configure terminal command to access the global configuration level of the CLI.switch# configure terminalEntering configuration mode terminal2. Execute the following command to set the trap recipient with IP address 192.0.2.2, whichreceives all traps with the severity levels of Critical, Error, Info, and Warning.switch(config)# snmp-server host 192.0.2.2 public severity-level Info udp-port162 version 1NOTETo receive the traps, the management station IP address must be configured on the switch.3. Execute the do show running-config snmp-server command to verify the configuration.switch(config)# do show running-config snmp-serversnmp-server contact "Field Support."snmp-server location "End User Premise."snmp-server sys-descr "Brocade VDX Switch."snmp-server community ConvergedNetworksnmp-server community OrigEquipMfr rwsnmp-server community "Secret C0de" rwsnmp-server community commonsnmp-server community private rwsnmp-server community publicsnmp-server host 192.0.2.2 publicudp-port 162severity-level InfoConfiguring the SNMPv3 serverUse the snmp-server v3-host command to specify the recipient of SNMP version 3 notifications:traps or informs. The following example explains the procedure to configure the recipient of theSNMPv3 informs.To configure the SNMPv3 host to receive the inform, perform the following steps.1. Execute the configure terminal command to access the global configuration level of the CLI.switch# configure terminalEntering configuration mode terminal2. Execute the following command to set the inform recipient with IP address 192.0.2.2, whichreceives all traps with the severity levels of Critical, Error, Info, and Warning.switch(config)# snmp-server v3host 192.0.2.2 snmpadmin1 notifytype informsengineid 80:00:05:23:01:AC:1A:01:79 severity-level Info udp-port 4425NOTETo receive the SNMP informs, the username, the authentication protocol, the privacy protocol,the UDP port number, and the engine ID must match between the switch and the managementstation.Network OS Message Reference 953-1002807-01

1Commands for displaying, clearing, and configuring the message logs3. Execute the show running-config snmp-server command to verify the configuration.switch# show running-config snmp-serversnmp-server contact "Field Support."snmp-server location "End User Premise."snmp-server sys-descr "Brocade VDX Switch."snmp-server community ConvergedNetworksnmp-server community OrigEquipMfr rwsnmp-server community "Secret C0de" rwsnmp-server community commonsnmp-server community private rwsnmp-server community publicsnmp-server user snmpadmin1 groupname snmpadmin auth md5 auth-password * privDES priv-password *snmp-server user snmpadmin2 groupname snmpadmin auth-password * priv-password*snmp-server user snmpadmin3 groupname snmpadmin auth-password * priv-password*snmp-server user snmpuser1 auth-password * priv-password *snmp-server user snmpuser2 auth-password * priv-password *snmp-server user snmpuser3 auth-password * priv-password *snmp-server v3host 192.0.2.2 snmpadmin1udp-port 4425notifytype informsengineid 80:00:05:23:01:AC:1A:01:79severity-level Info!Commands for displaying, clearing, and configuring the message logsTable 5 describes commands that you can use to view or configure various message logs. Mostcommands require the admin access level. For detailed information on required access levels andcommands, refer to the Network OS Command Reference.TABLE 5CommandCommands for viewing or configuring the message logsDescriptionclear logging auditlogclear logging rasloglogging auditlog classlogging raslog consolelogging syslog-facility locallogging syslog-servershow logging auditlogshow logging raslogThis command clears the Audit log messages from the local switch or the specifiedswitches.This command clears the error log messages from the local switch or the specifiedswitches.This command sets the event classes for Audit log messages.This command sets a filter based on the severity level for the messages to bedisplayed on the system console.This command sets the syslog facility.This command configures a syslog server to which the switch can forward themessages.This command displays the Audit log messages on the local switch or the specifiedswitches.This command displays the error log message on the local switch, the specifiedswitch, or interface module. The command includes options to filter the messagesbased on the message attribute and the severity level, and also to set the count ofmessages to display, and to display messages in reverse order.10 Network OS Message Reference53-1002807-01

Viewing and clearing the RASLog messages 1TABLE 5CommandCommands for viewing or configuring the message logs (Continued)Descriptionshow running-configloggingshow running-configlogging auditlog classshow running-configlogging raslogshow running-configlogging syslog-facilityThis command is used to display the logging settings on the local switch.This command displays the event class configured for the Audit log.This command displays the RASLog console severity level on the local switch or thespecified switch.This command displays the syslog facility level.Viewing and clearing the RASLog messagesYou can display system messages using the show logging raslog command. This commandprovides options to filter the messages by attribute, message type, severity, or message count. Youcan also specify to display messages for a single module by using the blade option. Use the clearlogging raslog command to delete the system messages.Displaying the RASLog messagesTo display the saved RASLog messages, perform the following steps.1. Log in to the switch as admin.2. Enter the show logging raslog command at the command line.switch# show logging raslogNOS: v3.0.12012/06/04-22:57:00, [HASM-1108], 94,, INFO, VDX6720-24, All service instancesbecome active.2012/06/04-22:57:03, [DCM-1002], 96,, INFO, VDX6720-24, PostBoot processing onglobal config has started.2012/06/04-22:57:05, [BL-1000], 100,, INFO, VDX6720-24, Initializing ports...2012/06/13-05:10:22, [NSM-1004], 4428, DCE, INFO, sw0, Interface Vlan 1 iscreated.2012/06/13-05:10:24, [DOT1-1013], 4435, DCE, INFO, sw0, DOT1X test timeoutvalue is set to 10.2012/06/13-05:10:24, [ONMD-1002], 4437, DCE, INFO, sw0, LLDP globalconfiguration is changed.2012/06/13-05:10:28, [RAS-2001], 4438,, INFO, sw0, Audit message log isenabled.[...]Network OS Message Reference 1153-1002807-01

1Viewing and clearing the RASLog messagesDisplaying the messages on an interface moduleTo display the saved messages for a specific interface module, line card (LC), or managementmodule, perform the following steps.1. Log in to the switch as admin.2. Enter the show logging raslog blade command at the command line. You can filter messagesbased on the severity level using the severity option. The following example filters messages bythe severity level of info.switch# show logging raslog blade LC2 severity infoNOS: v3.0.12012/05/29-11:43:06, [HASM-1004], 6919, L2, INFO, VDX8770-4, Processorrebooted - Reset.2012/05/29-11:43:06, [HASM-1104], 6920, L2, INFO, VDX8770-4, Heartbeat to M2up.2012/05/29-11:43:10, [HASM-1004], 6921, L2, INFO, VDX8770-4, Processorrebooted - Reset.2012/05/29-11:43:10, [HASM-1104], 6922, L2, INFO, VDX8770-4, Heartbeat to M2up.[...]Clearing the RASLog messagesTo clear the RASLog messages for a particular switch instance, perform the following steps.1. Log in to the switch as admin.2. Execute the clear logging raslog command to clear all messages from the switch.Viewing and clearing the SYSTEM messagesThis section provides information on viewing and clearing the SYSTEM messages saved on theswitch memory.Displaying the SYSTEM messagesTo display the messages saved in the SYSTEM storage repository, perform the following steps.1. Log in to the switch as admin.2. Enter the show logging raslog message-type SYSTEM command at the command line.switch# show logging raslog message-type SYSTEMNOS: v3.0.12011/09/14-04:52:05, [LOG-1003], 1,, INFO, VDX6720-60, SYSTEM error log hasbeen cleared.2011/09/14-04:56:18, [DCM-1101], 2,, INFO, VDX6720-60, Copy running-config tostartup-config operation successful on this node.2011/09/14-05:05:21, [RAS-1007], 5,, INFO, VDX6720-60, System is about toreboot.[...]12 Network OS Message Reference53-1002807-01

Viewing and clearing the RASLog messages 1Clearing the SYSTEM messagesTo clear the messages saved in the SYSTEM storage repository, perform the following steps.1. Log in to the switch as admin.2. Execute the clear logging raslog message-type SYSTEM command to clear all systemmessages from the local switch.Viewing and clearing the DCE messagesThis section provides information on viewing and clearing the DCE messages saved on the switchmemory.Displaying the DCE messagesTo display the saved DCE messages, perform the following steps.1. Log in to the switch as admin.2. Enter the show logging raslog message-type DCE command at the command line.switch# show logging raslog message-type DCENOS: v3.0.12012/05/30-21:25:34, [NSM-1004], 41, M1 | DCE, INFO, switch, Interface Vlan4093 is created.2012/05/30-21:25:34, [NSM-1019], 42, M1 | DCE, INFO, switch, Interface Vlan4093 is administratively up.2012/05/30-21:25:52, [DOT1-1013], 50, M1 | DCE, INFO, switch, DOT1X testtimeout has set to 10.2012/05/30-21:25:52, [ONMD-1002], 59, M1 | DCE, INFO, switch, LLDP globalconfiguration is changed.2012/05/30-21:25:53, [SSMD-1602], 63, M1 | DCE, INFO, switch, Class mapdefault is created.2012/05/30-21:25:55, [NSM-1004], 58, M1 | DCE, INFO, switch, Interface Vlan1002 is created.2012/05/30-21:25:55, [ONMD-1002], 59, M1 | DCE, INFO, switch, LLDP globalconfiguration is changed.2012/05/30-21:25:59, [SSMD-1602], 63, M1 | DCE, INFO, switch, Class mapdefault is created[...]Clearing the DCE messagesTo clear the DCE messages for a particular switch instance, perform the following steps.1. Log in to the switch as admin.2. Execute the clear logging raslog message-type DCE command to clear all DCE messages fromthe local switch.Network OS Message Reference 1353-1002807-01

1Viewing, clearing, and configuring Audit log messagesDisplaying the VCS messagesThis section provides information on viewing the VCS messages saved on the switch memory.To display the saved VCS messages, perform the following steps.1. Log in to the switch as admin.2. Enter the show logging raslog attribute VCS command at the command line.switch# show logging raslog attribute VCSNOS: v3.0.12012/06/05-03:00:18:101601, [VCS-1009], 8002/3929, VCS, INFO, VDX6720-60,Event: VCS node disconnect, Coordinator IP: 192.0.2.15, VCS Id: 1, Status:Rbridge-id 3 (192.0.2.2) disconnected from VCS cluster.2012/06/05-03:04:11:621996, [VCS-1005], 8051/3935, VCS, INFO, VDX6720-60,Event: VCS node rejoin, Coordinator IP: 192.0.2.15, VCS Id: 1, Status:Rbridge-id 3 (192.0.2.2) rejoined VCS cluster.[...]Displaying the FFDC messagesThis section provides information on viewing the FFDC messages saved on the switch memory.To display the saved FFDC messages, perform the following steps.1. Log in to the switch as admin.2. Enter the show logging raslog attribute FFDC command at the command line.switch# show logging raslog attribute FFDCNOS: v3.0.12012/06/15-10:39:02, [LOG-1002], 4496, FFDC, WARNING, VDX6720-24, A logmessage was not recorded.2012/06/15-10:39:18, [RAS-1001], 4496, FFDC, WARNING, VDX6720-24, Firstfailure data capture (FFDC) event occurred.[...]Viewing, clearing, and configuring Audit log messagesThis section provides information on viewing, clearing, and configuring the Audit log messages.Displaying the Audit messagesTo display the saved Audit messages, perform the following steps.1. Log in to the switch as admin.2. Enter the show logging auditlog command at the command line.You can also display messages in reverse order using the reverse option.switch# show logging auditlog0 AUDIT,2011/08/26-07:51:29 (GMT), [RAS-2001], INFO, SYSTEM,NONE/root/NONE/None/CLI,, switch, Audit message log is enabled.14 Network OS Message Reference53-1002807-01

Viewing, clearing, and configuring Audit log messages 11 AUDIT,2011/08/26-07:51:29 (GMT), [RAS-2003], INFO, SYSTEM,NONE/root/NONE/None/CLI,, switch, Audit message class configuration has beenchanged to 2,6,4,.2 AUDIT,2011/08/26-07:51:32 (GMT), [DCM-2001], INFO, DCMCFG,root/none/127.0.0.1/rpc/cli,, VDX6720-24, Event: noscli start, Status:success, Info: Successful login attempt through console from 127.0.0.1.3 AUDIT,2011/08/26-07:51:34 (GMT), [DCM-2001], INFO, DCMCFG,admin/admin/127.0.0.1/rpc/cli,, VDX6720-24, Event: noscli start, Status:success, Info: Successful login attempt through console from 127.0.0.1.4 AUDIT,2011/08/26-07:51:36 (GMT), [DCM-2002], INFO, DCMCFG,admin/admin/127.0.0.1/rpc/cli,, VDX6720-24, Event: noscli exit, Status:success, Info: Successful logout by user [admin].[...]Clearing the Audit messagesTo clear the Audit log messages for a particular switch instance, perform the following steps.1. Log in to the switch as admin.2. Execute the clear logging auditlog command to clear all messages on the switch memory.Configuring event auditingThe Audit log classes SECURITY, CONFIGURATION, and FIRMWARE are enabled by default. You canenable or disable auditing of these classes using the logging auditlog class class command.To configure and verify the event auditing, perform the following steps.1. Execute the configure terminal command to access the global configuration level of the CLI.switch# configure terminalEntering configuration mode terminal2. Configure the event classes you want to audit. For example, to audit the CONFIGURATON class,execute the following command.You can choose one of the following event classes: CONFIGURATION, FIRMWARE, or SECURITY.switch(config)# logging auditlog class CONFIGURATION3. Execute the show running-config logging auditlog class command to verify the configuration.switch# show running-config logging auditlog classlogging auditlog class CONFIGURATIONNetwork OS Message Reference 1553-1002807-01

1Understanding the RASLog messagesUnderstanding the RASLog messagesThis section provides information about reading the RASLog messages.RASLog messagesThe following example shows the format of a RASLog message., [], , ,,,The following example shows the sample messages from the error log.2011/08/23-22:58:10, [IPAD-1000], 2,, INFO, VDX6720-24, SW/0 Ether/0 IPv4 DHCP10.24.95.252/20 DHCP On.2012/05/30-21:26:00, [FCOE-1035], 67, M1 | DCE, INFO, sw0, Virtual FCoE port 1/1/4is online.2011/08/26-12:39:02, [HAM-1007], 2, FFDC, CRITICAL, VDX6720-24, Need to reboot thesystem for recovery, reason: raslog-test-string0123456-raslog.2011/08/26-12:40:01, [VCS-1003], 7013/3454, VCS, INFO, VDX6720-60, Event: VCSnode add, Coordinator IP: 10.17.10.31, VCS ID: 1, Status: rBridge ID 1(10.17.10.32) added to VCS cluster., VcsFabAddRejoin, line: 1450, comp:dcmd,ltime:2011/06/27-02:47:04:555942.The fields in the error message are described in Table 6.TABLE 6Variable nameRAS message field descriptionDescriptionTimestampEvent IDSequence NumberFlagsThe system time (UTC) when the message was generated on the switch. The RASLogsubsystem supports an internationalized time stamp format base on the “LOCAL” setting.The Event ID is the message module and number. These values uniquely identify eachmessage in the Network OS and reference the cause and actions recommended in thismanual. Note that not all message numbers are used; there can be gaps in the numericmessage sequence.The error message position in the log. When a new message is added to the log, this numberis incremented by 1.The message sequence number starts at 1 after a firmware download and increases up to avalue of 2,147,483,647 (0x7ffffff). The sequence number continues to increase after themessage log wraps around; that is, the oldest message in the log is deleted when a newmessage is added. The message sequence numbering is not split for the system and DCEmessage logs. The sequence number can be reset to 1 using the clear logging raslogcommand. However, the sequence number is not reset if you clear a particular messagetype, for example, DCE. The sequence number is persistent across power cycles and switchreboots.For most messages, this field contains a space character (null value) indicating that themessage is neither a DCE, FFDC, or VCS message. Messages may contain the followingvalues:• DCE–Indicates a message generated by the protocol-based modules.• FFDC–Indicates that additional first failure data capture information has also beengenerated for this event.• VCS–Indicates a VCS message generated by a switch in the Brocade VCS fabric.16 Network OS Message Reference53-1002807-01

Understanding the RASLog messages 1TABLE 6 RAS message field description (Continued)Variable name DescriptionSeveritySwitch nameEvent-specificinformationThe severity level of the message, which can be one of the following:• CRITICAL• ERROR• WARNING• INFOThe defined switch name or the chassis name of the switch. This value is truncated if itexceeds 16 characters in length.A text string explaining the error encountered and provides the parameters supplied by thesoftware at runtime.Audit event messagesCompared to Log error messages, messages flagged as AUDIT provide additional user andsystem-related information of interest for post-event auditing and problem determination.The following example shows the format of the Audit event message. AUDIT, , [], , ,////, , , The following is a sample Audit event message.0 AUDIT,2011/08/26-07:51:32 (GMT), [DCM-2001], INFO, DCMCFG,root/none/127.0.0.1/rpc/cli,, VDX6720-24, Event: noscli start, Status: success,Info: Successful login attempt through console from 127.0.0.1.The fields in the Audit event message are described in Table 7.TABLE 7 Audit message field descriptionVariable nameDescriptionSequence NumberAUDITTimestampEvent IDSeverityEvent ClassThe error message position in the log.Identifies the message as an Audit message.The system time (UTC) when the message was generated on the switch. The RASLogsubsystem supports an internationalized time stamp format base on the “LOCAL”setting.The Event ID is the message module and number. These values uniquely identify eachmessage in the Network OS and reference the cause and actions recommended in thismanual. Note that not all message numbers are used; there can be gaps in thenumeric message sequence.The severity level of the message, which can be one of the following:• CRITICAL• ERROR• WARNING• INFOThe event class, which can be one of the following:• DCMCFG• FIRMWARE• SECURITYNetwork OS Message Reference 1753-1002807-01

1Responding to a RASLog messageTABLE 7 Audit message field description (Continued)Variable nameDescriptionUser IDRoleIP AddressInterfaceApplication NameReserved field forfuture expansionSwitch nameEvent-specificinformationThe user ID.The role of the user.The IP address.The interface being used.The application name being used on the interface.This field is reserved for future use and contains a space character (null value).The defined switch name or the chassis name of the switch. This value is truncated if itis over 16 characters in length.A text string explaining the error encountered and provides the parameters supplied bythe software at runtime.Responding to a RASLog messageThis section provides procedures on gathering information on RASLog messages.Looking up a messageMessages in this manual are arranged alphabetically by Module ID, and then numerically within agiven module. To look up a message, copy down the module (see Table 8 on page 20) and the errorcode and compare this with the Table of Contents or look up lists to determine the location of theinformation for that message.The following information is provided for each message:• Module and code name for the error• Message text• Message type• Class (for Audit messages only)• Message severity• Probable cause• Recommended actionGathering information about the problemThe following are the common steps and questions to ask yourself when troubleshooting a systemmessage:• What is the current Network OS version?• What is the switch hardware version?• Is the switch operational?18 Network OS Message Reference53-1002807-01

Responding to a RASLog message 1• Assess impact and urgency:- Is the switch down?- Is it a standalone switch?- How large is the fabric?- Is the fabric redundant?• Execute the show logging raslog command on each switch.• Execute the copy support command.• Document the sequence of events by answering the following questions:- What happened just before the problem?- Is the problem repeatable?- If so, what are the steps to produce the problem?- What configuration was in place when the problem occurred?• Did a failover occur?• Was Power-On Self-Test (POST) enabled?• Are serial port (console) logs available?• What and when were the last actions or changes made to the system?SupportNetwork OS creates several files that can help support personnel troubleshoot and diagnose aproblem. This section describes those files and how to access and save the information for supportpersonnel.Panic dump, core dump, and FFDC data filesThe Network OS creates panic dump files, core files, and FFDC data files when there are problemsin the Network OS kernel. You can view files using the show support command. These files canbuild up in the persistent storage and may need to be periodically deleted or downloaded using thecopy support command.The software watchdog (SWD) process is responsible for monitoring daemons critical to thefunction of a healthy switch. The SWD holds a list of critical daemons that ping the SWD periodicallyat a predetermined interval defined for each daemon.If a daemon fails to ping the SWD within the defined interval, or if the daemon terminatesunexpectedly, then the SWD dumps information to the panic dump files, which helps to diagnosethe root cause of the unexpected failure.Execute the show support command to view these files or the copy support ftp command to sendthem to a host workstation using FTP. The panic dump files, core files, and FFDC data files areintended for support personnel use only.Trace dumpsThe Network OS produces trace dumps when problems are encountered within Network OSmodules. The Network OS trace dump files are intended for support personnel use only. You canuse the copy support command to collect trace dump files to a specified remote location to providesupport when requested.Network OS Message Reference 1953-1002807-01

1System module descriptionsUsing the copy support commandThe copy support command is used to send the output of the RASLog messages, the trace files,and the output of the copy support command to an off-switch storage location through FTP. You canupload supportsave data from the local switch to an external host or you can save the data on anattached USB device. The copy support command runs a large number of dump and showcommands to provide a global output of the status of the switch. Refer to the Network OSCommand Reference for more information on the copy support command.System module descriptionsTable 8 provides a summary of the system modules for which messages are documented in thisreference guide; a module is a subsystem in the Network OS. Each module generates a set ofnumbered messages.TABLE 8 System module descriptionsSystem DescriptionmoduleAUTHBLBLLC2C3CHSDCMDOT1EANVELDEMERCPESSAUTH messages indicate problems with the authentication module of the Network OS.BL messages are a result of faulty hardware, transient out-of-memory conditions, ASIC errors, orinconsistencies in the software state between an interface module and the environment monitor(EM) module.Bloom is the name of the ASIC used as the building block for third-generation hardware platforms.C2 error messages indicate problems with the 8 Gbps-capable FC module of the Network OS.C3 error messages indicate problems with the 16 Gbps-capable FC module of the Network OS.CHS messages report the problems in the management of the interface modules in the differentslots of the chassis.Distributed Configuration Manager (DCM) messages indicate major switch bootup events, userlogin or logout, and the configuration operations.DOT1 messages indicate problems with the 802.1x authentication module of the Network OS.EANV messages indicate any issues associated with eAnvil ASIC operation and eAnvil ASIC driveroperations.End Loop Detection (ELD) messages notify a loop in the Layer 2 network and the status of the porton which the loop is detected.The environmental monitor (EM) manages and monitors the various field-replaceable units (FRUs),including the port cards, blower assemblies, power supplies, and World Wide Name (WWN) cards.EM controls the state of the FRUs during system startup, hot-plug sequences, and fault recovery.EM provides access to and monitors the sensor and status data from the FRUs and maintains theintegrity of the system using the environmental and power policies. EM reflects system status byway of CLI commands, system light emitting diodes (LEDs), and status and alarm messages. EMalso manages some component-related data.ERCP message indicate any problems associated with Double Data Rate (DDR) errors.Exchange Switch Support (ESS) error messages indicate problems with the ESS module of theNetwork OS. ESS is an SW_ILS mechanism utilized by switches to exchange vendor and supportinformation.20 Network OS Message Reference53-1002807-01

System module descriptions 1TABLE 8SystemmoduleFABRFABSFCMCFCOEFCPHFLODFSPFFSSFVCSFWHASMHAWKHILHLOHSLIGMPIPADSystem module descriptions (Continued)DescriptionFABR (network of Fibre Channel switches) messages come from the fabric daemon. The fabricdaemon follows the FC-SW-3 standard for the fabric initialization process, such as determining theE_Ports, assigning unique domain IDs to switches, creating a spanning tree, throttling the trunkingprocess, and distributing the domain and alias lists to all switches in the fabric.FABS messages indicate problems in the fabric system driver module.Fibre Channel miscellaneous messages relate to problems with the physical layer used to sendFibre Channel traffic to and from the switch.FCOE error messages indicate problems with the Fibre Channel over Ethernet (FCoE) module ofthe Network OS.The Fibre Channel Physical Layer is used to send Fibre Channel traffic to and from the switch.FLOD is a part of the fabric shortest path first (FSPF) protocol that handles synchronization of thelink state database (LSDB) and propagation of the link state records (LSRs).Fabric shortest path first (FSPF) is a link state routing protocol that is used to determine howframes should be routed. FSPF messages are about protocol errors.The fabric state synchronization framework provides facilities by which the active managementmodule can synchronize with the standby management module, enabling the standbymanagement module to take control of the switch nondisruptively during failures and softwareupgrades. These facilities include version negotiation, state information transfer, and internalsynchronization functions, enabling the transition from standby to active operation.FSS is defined both as a component and a service. A component is a module in the Network OS,implementing a related set of functionality. A service is a collection of components groupedtogether to achieve a modular software architecture.The Fabric Services VCS (FVCS) daemon provides fabric distribution services for VCS and VirtualLink Aggregation Group (vLAG).FW messages indicate the warnings when the temperature, voltage, fan speed, and switch statusthresholds are exceeded for the switch subsystems.HASM is the infrastructure for the High Availability System Management, which has thefunctionality to maintain the cluster of high availability switch platforms, deploy and start multipleservice instances with active and standby redundancy in a distributed clustering environment,manage the state synchronizations, and the non-disruptive failovers between active and standbymanagement modules, host the non-disruptive firmware upgrade context, and support thesoftware watchdog and daemon restart.HAWK is a component that connects the fabric ASIC.HIL messages indicate any issues associated with the Hardware Independent Layer (HIL) forgeneral platform components, such as Environmental Monitoring (EM), fan and power supply unit(PSU) subsystems, and other platform FRUs.HLO is a part of the fabric shortest path first (FSPF) protocol that handles the HELLO protocolbetween adjacent switches. The HELLO protocol is used to establish connectivity with a neighborswitch, to establish the identity of the neighbor switch, and to exchange FSPF parameters andcapabilities.HSL messages indicate problems with the Hardware Subsystem Layer (HSL) of the Network OS.IGMP messages indicate any issue associated with the Internet Group Management Protocol(IGMP) snooping feature.IPAD messages are generated by the IP admin demon.Network OS Message Reference 2153-1002807-01

1System module descriptionsTABLE 8SystemmoduleSystem module descriptions (Continued)DescriptionKTRCL2AGL2SSLACPLOGLSDBKTRC messages indicate any problem associated with the RAS-TRACE facility, which provideBrocade internal information to diagnose a failure.L2AG messages indicate problems with the Layer 2 system agent module. L2SS and L2AGtogether control the Layer 2 forwarding engine and are responsible for MAC learning, aging, andforwarding functionalities.L2SS messages indicate problems with the Layer 2 system manager module. L2SS and L2AGtogether control the Layer 2 forwarding engine and are responsible for MAC learning, aging, andforwarding functionalities.LACP error messages indicate problems with the Link Aggregation Control Protocol module of theNetwork OS.LOG messages describe events and problems associated with the RASLog and Audit log facilities.The link state database is a part of the FSPF protocol that maintains records on the status of portlinks. This database is used to route frames.MCAST_SS MCAST_SS messages indicate any problems associated with the Layer 2 and Layer 3.MPTHMSMSTPNBFSNSNSMONMDOSPFPDMPHPPLATPORTRASMulticast path uses the shortest path first (SPF) algorithm to dynamically compute a broadcasttree.The Management Service (MS) enables the user to obtain information about the Fibre Channelfabric topology and attributes by providing a single management access point.MSTP messages indicate problems with Multiple Spanning Tree Protocol (MSTP) modules of theNetwork OS.NBFSM is a part of the fabric shortest path first (FSPF) protocol that handles a neighboring oradjacent switch’s finite state machine (FSM).Input to the FSM changes the local switch from one state to another, based on specific events. Forexample, when two switches are connected to each other using an interswitch link (ISL) cable, theyare in the Init state. After both switches receive HELLO messages, they move to the DatabaseExchange state, and so on.NS messages indicate problems with the simple Name Server module.NSM messages indicate problems with the interface management and VLAN managementmodule of the Network OS.ONMD messages indicate problems with the Operation, Administration and Maintenance moduleof the Network OS.OSPF messages indicate information or problems with the OSPF module of the Network OS.Parity data manager (PDM) is a user-space daemon responsible for the replication of persistentconfiguration files from the primary partition to the secondary partition and from the activemanagement module to the standby management module.PHP messages indicate any important information associated with the discovery and creation,deletion, and updating of the port profiles.PLAT messages indicate hardware problems.PORT messages refer to the front-end user ports on the switch. Front-end user ports are directlyaccessible by users to connect end devices or connect to other switches.RAS messages notify when first failure data capture (FFDC) events are logged to the FFDC log, andsize or roll-over warnings.22 Network OS Message Reference53-1002807-01

System module descriptions 1TABLE 8SystemmoduleRCSRTMRTWRSCNSECSFLOSLCDSNMPSSSSMDSULBSWCHTOAMTRCETSUCSTSystem module descriptions (Continued)DescriptionThe reliable commit service (RCS) daemon generates log entries when it receives a request fromthe zoning or security server for passing data messages to switches. RCS then requests reliabletransport write and read (RTWR) to deliver the message. RCS also acts as a gatekeeper, limitingthe number of outstanding requests for the Zoning or Security modules.Route Manager (RTM) messages indicate status or errors while updating or maintaining the routeand next-hop database.The reliable transport write (RTWR) and read daemon helps deliver data messages either tospecific switches in the fabric or to all the switches in the fabric. For example, if some of theswitches are not reachable or are offline, RTWR returns an “unreachable” message to the caller,allowing the caller to take the appropriate action. If a switch is not responding, RTWR retries 100times.The internal state change notification daemon is used for state change notifications from thekernel to the daemons within Network OS.SEC messages indicate security errors, warnings, or information during security-related datamanagement or fabric merge operations. Administrators must watch for these messages todistinguish between internal switch and fabric operation errors and external attack.sFlow is a standards-based sampling technology embedded within switches and routers, which isused to monitor high speed network traffic.sFlow uses two types of sampling:• Statistical packet-based sampling of switched or routed packet flows.• Time-based sampling of interface counters.SFLO messages indicate errors or information related to the sflow daemon.SLCD messages provide wear level statistics of the western digital (WD) SiliconDrive 2 compactflash.Simple Network Management Protocol (SNMP) is a universally supported low-level protocol thatallows simple get, get next, and set requests to go to the switch (acting as an SNMP agent). It alsoallows the switch to send traps to the defined and configured management station. Brocadeswitches support four management entities that can be configured to receive these traps orinforms.SNMP messages indicate problems in the SNMP operations.SS messages indicate problems during the execution of the copy support command.SSMD messages indicate problems with the System Services Module (SSM) of the Network OS.The software upgrade library provides the firmware download command capability, which enablesfirmware upgrades as well as nondisruptive code load to the switches. SULB messages maydisplay if there are any problems during the firmware download procedure.SWCH messages are generated by the switch driver module that manages a Fibre Channel switchinstance.TRILL OAM (TOAM) messages indicate problems with the l2traceroute family of commands thathelp in VCS cluster data path troubleshooting.TRCE messages describe events and problems associated with the tracedump facility.Time Service (TS) provides switch time-synchronization by synchronizing all clocks in the network.The TS messages indicate information or errors during the switch time synchronization.UCST is a part of the fabric shortest path first (FSPF) protocol that manages the unicast routingtable.Network OS Message Reference 2353-1002807-01

1System module descriptionsTABLE 8SystemmoduleUPTHVCVCSVRRPWLVZONESystem module descriptions (Continued)DescriptionUPATH is a part of the FSPF protocol that uses the SPF algorithm to dynamically compute a unicasttree.VC messages indicate any important information related to the vCenter CLI and its plugins.VCS messages indicate major events related to VCS cluster formation and node operations.VRRP messages indicate information or problems with the VRRP module of the Network OS.Wolverine (WLV) ASIC is a component that connects the front-end port. WLV messages indicatefailures in the front-end port.ZONE messages indicate any problems associated with the zoning features, including commandsassociated with aliases, zones, and configurations.24 Network OS Message Reference53-1002807-01

Log MessagesChapter2AUTH MessagesAUTH-1001AUTH-1002AUTH-1003AUTH-1004AUTH-1006AUTH-1007AUTH-1010AUTH-1012AUTH-1013AUTH-1014AUTH-1017AUTH-1018AUTH-1020AUTH-1022AUTH-1025AUTH-1026AUTH-1027AUTH-1028AUTH-1029AUTH-1030AUTH-1031AUTH-1032AUTH-1033AUTH-1034AUTH-1035AUTH-1036AUTH-1037AUTH-1039AUTH-1040AUTH-1041AUTH-1042AUTH-1044Network OS Message Reference 2553-1002807-01

2BL MessagesBL MessagesBL-1000BL-1001BL-1002BL-1003BL-1004BL-1006BL-1007BL-1008BL-1009BL-1010BL-1011BL-1012BL-1013BL-1014BL-1015BL-1016BL-1017BL-1018BL-1019BL-1020BL-1021BL-1022BL-1023BL-1024BL-1026BL-1027BL-1028BL-1029BL-1031BL-1032BL-1033BL-1034BL-1037BL-1038BL-1039BL-1045BL-1046BL-104726 Network OS Message Reference53-1002807-01

BLL Messages 2BLL MessagesBLL-1000C2 MessagesC2-1004C2-1006C2-1007C2-1008C2-1009C2-1010C2-1011C2-1012C3 MessagesC3-1004C3-1006C3-1010C3-1011C3-1012C3-1014C3-1017C3-1019C3-1020CHS MessagesDCM MessagesCHS-1002CHS-1003CHS-1004CHS-1005DCM-1001DCM-1002DCM-1003DCM-1004DCM-1005Network OS Message Reference 2753-1002807-01

2EANV MessagesEANV MessagesDCM-1007DCM-1008DCM-1009DCM-1010DCM-1011DCM-1012DCM-1101DCM-1102DCM-1103DCM-1104DCM-1105DCM-1106DCM-1107DCM-1108DCM-1109DCM-1201DCM-1202DCM-1203DCM-1204DCM-1205DCM-1206DCM-1207DCM-1208DCM-1209DCM-1210DCM-1211DCM-1212DCM-3005DCM-3051DCM-3052DCM-4001DCM-4002EANV-1001EANV-1002EANV-1003EANV-1004EANV-100528 Network OS Message Reference53-1002807-01

EM Messages 2EANV-1006EM MessagesEM-1001EM-1002EM-1003EM-1004EM-1005EM-1006EM-1008EM-1009EM-1010EM-1011EM-1012EM-1013EM-1014EM-1015EM-1016EM-1020EM-1021EM-1022EM-1023EM-1024EM-1028EM-1029EM-1031EM-1032EM-1033EM-1034EM-1036EM-1037EM-1042EM-1043EM-1045EM-1046EM-1047EM-1048EM-1049EM-1050Network OS Message Reference 2953-1002807-01

2ERCP MessagesERCP MessagesEM-1051EM-1059EM-1064EM-1068EM-1069EM-1070EM-2003ERCP-1000ESS MessagesFABR MessagesESS-1008ESS-1009ESS-1010FABR-1001FABR-1003FABR-1004FABR-1005FABR-1006FABR-1007FABR-1008FABR-1009FABR-1010FABR-1012FABR-1013FABR-1014FABR-1019FABR-1029FABR-1030FABR-1039FABR-1041FABR-105530 Network OS Message Reference53-1002807-01

FABS Messages 2FABS MessagesFCMC MessagesFABS-1001FABS-1002FABS-1004FABS-1005FABS-1006FABS-1007FABS-1008FABS-1009FABS-1010FABS-1011FABS-1013FABS-1014FABS-1015FCMC-1001FCPH MessagesFCPH-1001FLOD MessagesFSPF MessagesFLOD-1001FLOD-1003FLOD-1004FLOD-1005FLOD-1006FSPF-1001FSPF-1002FSPF-1003FSPF-1005FSPF-1006FSPF-1007FSPF-1008Network OS Message Reference 3153-1002807-01

2FSS MessagesFSS MessagesFVCS MessagesFW MessagesFSS-1001FSS-1002FSS-1003FSS-1004FSS-1005FSS-1006FSS-1007FSS-1008FSS-1009FSS-1010FSS-1011FVCS-1003FVCS-2001FVCS-2002FVCS-2003FVCS-2004FVCS-2005FVCS-2006FVCS-3001FVCS-3002FVCS-3003FVCS-3004FVCS-3005FVCS-3006FVCS-3007FVCS-3008FVCS-3009FW-1001FW-1002FW-1003FW-1004FW-100532 Network OS Message Reference53-1002807-01

FW Messages 2FW-1006FW-1007FW-1008FW-1009FW-1010FW-1012FW-1034FW-1035FW-1036FW-1038FW-1039FW-1040FW-1042FW-1043FW-1044FW-1046FW-1047FW-1048FW-1050FW-1051FW-1052FW-1297FW-1298FW-1299FW-1341FW-1342FW-1343FW-1403FW-1404FW-1405FW-1406FW-1407FW-1408FW-1424FW-1425FW-1426FW-1427FW-1428FW-1429Network OS Message Reference 3353-1002807-01

2HASM MessagesHASM MessagesFW-1430FW-1431FW-1432FW-1433FW-1434FW-1435FW-1439FW-1440FW-1441FW-1442FW-1443FW-1444FW-1447FW-1500FW-1501FW-1510FW-3101FW-3102FW-3103FW-3104FW-3105FW-3107FW-3108FW-3109FW-3110FW-3111FW-3113FW-3114FW-3115FW-3116FW-3117FW-3119FW-3120FW-3121FW-3122FW-3123HASM-100034 Network OS Message Reference53-1002807-01

HAWK Messages 2HAWK MessagesHASM-1001HASM-1002HASM-1003HASM-1004HASM-1013HASM-1014HASM-1019HASM-1020HASM-1021HASM-1022HASM-1023HASM-1024HASM-1025HASM-1026HASM-1100HASM-1101HASM-1102HASM-1103HASM-1104HASM-1105HASM-1106HASM-1107HASM-1108HASM-1109HASM-1110HASM-1111HASM-1120HASM-1121HASM-1130HASM-1131HASM-1200HASM-1201HAWK-1002HIL MessagesHIL-1202Network OS Message Reference 3553-1002807-01

2HLO MessagesHIL-1301HIL-1302HIL-1404HIL-1505HIL-1506HIL-1510HIL-1511HIL-1512HIL-1521HIL-1522HIL-1523HIL-1605HLO MessagesHLO-1001HLO-1002HLO-1003HSL MessagesIPAD MessagesKTRC MessagesHSL-1000HSL-1001HSL-1004HSL-1006HSL-1009IPAD-1000IPAD-1001IPAD-1002IPAD-1003IPAD-1004IPAD-1005KTRC-1001KTRC-1002KTRC-100336 Network OS Message Reference53-1002807-01

LOG Messages 2KTRC-1004KTRC-1005LOG MessagesLSDB MessagesMPTH MessagesMS MessagesLOG-1000LOG-1001LOG-1002LOG-1003LOG-1004LOG-1005LOG-1006LSDB-1001LSDB-1002LSDB-1003LSDB-1004MPTH-1001MPTH-1002MPTH-1003MS-1021NBFS MessagesNS MessagesNBFS-1001NBFS-1002NBFS-1003NS-1006NS-1009NS-1012Network OS Message Reference 3753-1002807-01

2PDM MessagesPDM MessagesPHP MessagesPLAT MessagesPORT MessagesPDM-1001PDM-1003PDM-1004PDM-1006PDM-1007PDM-1009PDM-1010PDM-1011PDM-1012PDM-1013PDM-1014PDM-1017PDM-1019PDM-1021PHP-1001PHP-1002PHP-1003PHP-1004PLAT-1000PLAT-1001PLAT-1002PLAT-1004PLAT-1005PLAT-1006PLAT-1007PLAT-1008PLAT-1009PORT-1003PORT-1004PORT-101138 Network OS Message Reference53-1002807-01

RAS Messages 2PORT-1012PORT-1013PORT-1014PORT-1015PORT-1016PORT-1017RAS MessagesRAS-1001RAS-1002RAS-1004RAS-1005RAS-1006RAS-1007RAS-2001RAS-2002RAS-2003RAS-2004RAS-2005RAS-3001RAS-3002RAS-3003RAS-3004RAS-3005RCS MessagesRTWR MessagesRCS-1003RCS-1005RCS-1006RCS-1007RCS-1008RCS-1010RCS-1011RTWR-1001RTWR-1002Network OS Message Reference 3953-1002807-01

2SCN MessagesRTWR-1003SCN MessagesSCN-1001SEC MessagesSEC-1033SEC-1034SEC-1036SEC-1037SEC-1038SEC-1044SEC-1071SEC-1180SEC-1181SEC-1184SEC-1185SEC-1187SEC-1189SEC-1190SEC-1191SEC-1192SEC-1193SEC-1197SEC-1199SEC-1203SEC-1307SEC-1308SEC-1312SEC-1313SEC-1325SEC-1329SEC-1334SEC-1335SEC-1336SEC-1337SEC-3035SEC-303640 Network OS Message Reference53-1002807-01

SLCD Messages 2SLCD MessagesSNMP MessagesSS MessagesSSMD MessagesSEC-3037SEC-3038SEC-3039SEC-3051SEC-3061SEC-3062SEC-3501SLCD-1001SLCD-1002SLCD-1003SLCD-1004SLCD-1005SLCD-1006SLCD-1007SLCD-1008SLCD-1009SLCD-1010SLCD-1011SNMP-1001SNMP-1002SNMP-1003SNMP-1004SNMP-1005SS-1000SS-1001SS-1002SS-1003SS-1004SSMD-1537Network OS Message Reference 4153-1002807-01

2SULB MessagesSULB MessagesSWCH MessagesTRCE MessagesTS MessagesSULB-1100SULB-1101SULB-1102SULB-1103SULB-1104SULB-1105SULB-1106SULB-1107SULB-1108SULB-1109SWCH-1001SWCH-1002SWCH-1003SWCH-1004SWCH-1005SWCH-1007SWCH-1021TRCE-1002TRCE-1003TRCE-1005TRCE-1006TRCE-1007TRCE-1008TRCE-1009TRCE-1010TRCE-1011TRCE-1012TS-1002TS-100842 Network OS Message Reference53-1002807-01

UCST Messages 2UCST MessagesUCST-1003UPTH MessagesUPTH-1001VC MessagesVCS MessagesWLV MessagesVC-1000VC-1001VC-1002VC-1003VC-1004VC-1005VC-1006VC-1007VC-1008VC-1009VC-1010VC-1011VCS-1001VCS-1002VCS-1003VCS-1004VCS-1005VCS-1006VCS-1007VCS-1008VCS-1009WLV-1001WLV-1002WLV-1003Network OS Message Reference 4353-1002807-01

2ZONE MessagesZONE MessagesZONE-1010ZONE-1014ZONE-1015ZONE-1019ZONE-1022ZONE-1023ZONE-1024ZONE-1027ZONE-1028ZONE-1029ZONE-1032ZONE-1033ZONE-1034ZONE-1035ZONE-1036ZONE-1037ZONE-1038ZONE-1039ZONE-1040ZONE-1041ZONE-1042ZONE-1043ZONE-1044ZONE-1045ZONE-104644 Network OS Message Reference53-1002807-01

DCE MessagesChapter3DOT1 MessagesDOT1-1001DOT1-1002DOT1-1003DOT1-1004DOT1-1005DOT1-1006DOT1-1007DOT1-1008DOT1-1009DOT1-1010DOT1-1011DOT1-1012DOT1-1013ELD MessagesELD-1001ELD-1002FCOE MessagesFCOE-1001FCOE-1010FCOE-1019FCOE-1020FCOE-1022FCOE-1023FCOE-1024FCOE-1029FCOE-1030FCOE-1032FCOE-1034FCOE-1035Network OS Message Reference 4553-1002807-01

3IGMP MessagesFCOE-1036IGMP MessagesL2AG MessagesL2SS MessagesLACP MessagesLOG MessagesIGMP-1001IGMP-1002IGMP-1003IGMP-1004L2AG-1001L2AG-1002L2AG-1003L2AG-1004L2AG-1005L2AG-1006L2AG-1007L2SS-1001L2SS-1002L2SS-1003L2SS-1004L2SS-1005L2SS-1006L2SS-1007L2SS-1008L2SS-1009L2SS-1010LACP-1003LACP-1004LOG-100746 Network OS Message Reference53-1002807-01

MCAST_SS Messages 3MCAST_SS MessagesMSTP MessagesNSM MessagesMCAST_SS-1001MCAST_SS-1002MCAST_SS-1003MCAST_SS-1004MCAST_SS-1005MCAST_SS-1006MCAST_SS-1007MCAST_SS-1008MCAST_SS-1009MCAST_SS-1010MCAST_SS-1011MCAST_SS-1012MCAST_SS-1013MCAST_SS-1014MCAST_SS-1015MCAST_SS-1016MCAST_SS-1017MCAST_SS-1018MCAST_SS-1019MCAST_SS-1020MSTP-1001MSTP-1002MSTP-1003MSTP-1004MSTP-2001MSTP-2002MSTP-2003MSTP-2004MSTP-2005MSTP-2006NSM-1001NSM-1002Network OS Message Reference 4753-1002807-01

3NSM MessagesNSM-1003NSM-1004NSM-1007NSM-1009NSM-1010NSM-1011NSM-1012NSM-1013NSM-1014NSM-1015NSM-1016NSM-1017NSM-1018NSM-1019NSM-1020NSM-1021NSM-1022NSM-1023NSM-1024NSM-1025NSM-1026NSM-1027NSM-1028NSM-1029NSM-1030NSM-1031NSM-1032NSM-1033NSM-1034NSM-1035NSM-1036NSM-1037NSM-1038NSM-2000NSM-2001NSM-2002NSM-2003NSM-2004NSM-200548 Network OS Message Reference53-1002807-01

ONMD Messages 3ONMD MessagesNSM-2006NSM-2007NSM-2008NSM-2010NSM-2011NSM-2012NSM-2013NSM-2014NSM-2015NSM-2016NSM-2017NSM-2018NSM-2019NSM-2020NSM-2021NSM-2022NSM-2023NSM-2024NSM-2025NSM-2026NSM-2027NSM-2028NSM-2029NSM-2030NSM-2031NSM-2032NSM-2033NSM-2034NSM-2035NSM-2036ONMD-1000ONMD-1001ONMD-1002ONMD-1003ONMD-1004ONMD-1005Network OS Message Reference 4953-1002807-01

3OSPF MessagesOSPF MessagesRTM MessagesSFLO MessagesSSMD MessagesOSPF-1001OSPF-1002OSPF-1003RTM-1001RTM-1002RTM-1003RTM-1005RTM-1022RTM-1023SFLO-1001SFLO-1002SFLO-1003SFLO-1004SFLO-1005SFLO-1006SFLO-1007SFLO-1008SFLO-1009SSMD-1001SSMD-1002SSMD-1003SSMD-1004SSMD-1005SSMD-1006SSMD-1007SSMD-1200SSMD-1201SSMD-1202SSMD-1203SSMD-120450 Network OS Message Reference53-1002807-01

SSMD Messages 3SSMD-1205SSMD-1206SSMD-1207SSMD-1208SSMD-1209SSMD-1210SSMD-1211SSMD-1212SSMD-1213SSMD-1214SSMD-1215SSMD-1216SSMD-1217SSMD-1218SSMD-1219SSMD-1220SSMD-1221SSMD-1222SSMD-1223SSMD-1224SSMD-1225SSMD-1300SSMD-1301SSMD-1302SSMD-1303SSMD-1304SSMD-1305SSMD-1306SSMD-1307SSMD-1308SSMD-1309SSMD-1312SSMD-1313SSMD-1314SSMD-1315SSMD-1400SSMD-1401SSMD-1402SSMD-1403Network OS Message Reference 5153-1002807-01

3SSMD MessagesSSMD-1404SSMD-1405SSMD-1406SSMD-1407SSMD-1408SSMD-1436SSMD-1437SSMD-1438SSMD-1439SSMD-1500SSMD-1536SSMD-1571SSMD-1600SSMD-1601SSMD-1602SSMD-1603SSMD-1604SSMD-1605SSMD-1606SSMD-1607SSMD-1609SSMD-1610SSMD-1611SSMD-1612SSMD-1613SSMD-1614SSMD-1615SSMD-1618SSMD-1619SSMD-1620SSMD-1621SSMD-1622SSMD-1650SSMD-1651SSMD-1652SSMD-1653SSMD-1654SSMD-1655SSMD-165652 Network OS Message Reference53-1002807-01

TOAM Messages 3TOAM MessagesVRRP MessagesSSMD-1657SSMD-1658SSMD-1659SSMD-1660SSMD-1700SSMD-1701SSMD-1702SSMD-1703SSMD-1704SSMD-1705SSMD-1706SSMD-1707SSMD-1708SSMD-1900SSMD-1901SSMD-1902SSMD-1903SSMD-1904SSMD-1905SSMD-1906SSMD-1907SSMD-1908SSMD-1909SSMD-1910SSMD-1911SSMD-1912SSMD-1913SSMD-1914SSMD-1915SSMD-1916TOAM-1000TOAM-1003VRRP-1001VRRP-1501Network OS Message Reference 5353-1002807-01

3VRRP MessagesVRRP-200154 Network OS Message Reference53-1002807-01

FFDC MessagesChapter4AUTH MessagesAUTH-1014AUTH-1044BL MessagesBL-1002BL-1003BL-1004BL-1008BL-1009BL-1011BL-1016BL-1020BLL MessagesBLL-1000CHS MessagesCHS-1002EANV MessagesEANV-1002EM MessagesEM-1001EM-1002EM-1003EM-1004EM-1005EM-1006Network OS Message Reference 5553-1002807-01

4ERCP MessagesERCP MessagesEM-1008EM-1009EM-1010EM-1011EM-1012EM-1028EM-1032EM-1068ERCP-1000FABR MessagesFABS MessagesFABR-1013FABR-1019FABS-1001FCMC MessagesFCMC-1001FCPH MessagesFCPH-1001FLOD MessagesFLOD-1004HASM MessagesHASM-1105HASM-1200HASM-120156 Network OS Message Reference53-1002807-01

HAWK Messages 4HAWK MessagesHAWK-1002HIL MessagesHLO MessagesIPAD MessagesHIL-1506HIL-1522HIL-1523HLO-1001HLO-1002IPAD-1003LOG MessagesLSDB MessagesLOG-1001LOG-1002LSDB-1003MPTH MessagesNBFS MessagesMPTH-1001MPTH-1002NBFS-1002PDM MessagesPDM-1017Network OS Message Reference 5753-1002807-01

4PLAT MessagesPLAT MessagesRAS MessagesSCN MessagesPLAT-1000PLAT-1004PLAT-1005RAS-1004RAS-1005SCN-1001SNMP MessagesSNMP-1004TRCE MessagesTRCE-1008WLV MessagesWLV-100258 Network OS Message Reference53-1002807-01

Audit MessagesChapter5AUTH MessagesAUTH-3001AUTH-3002AUTH-3004AUTH-3005AUTH-3006AUTH-3007AUTH-3008DCM MessagesDCM-1006DCM-2001DCM-2002HASM MessagesHASM-1004RAS MessagesRAS-2004RAS-2005SEC MessagesSEC-3014SEC-3016SEC-3017SEC-3018SEC-3019SEC-3020SEC-3021SEC-3022Network OS Message Reference 5953-1002807-01

5SULB MessagesSULB MessagesSEC-3023SEC-3024SEC-3025SEC-3026SEC-3027SEC-3028SEC-3030SEC-3034SEC-3035SEC-3036SEC-3037SEC-3038SEC-3039SEC-3045SEC-3046SEC-3049SEC-3051SEC-3061SEC-3062SEC-3067SEC-3068SEC-3069SEC-3070SEC-3071SEC-3072SEC-3073SEC-3074SEC-3075SEC-3076SEC-3501SULB-1100SULB-1101SULB-1102SULB-1103SULB-1104SULB-1105SULB-110660 Network OS Message Reference53-1002807-01

TS Messages 5TS MessagesTS-1009TS-1010TS-1011TS-1012Network OS Message Reference 6153-1002807-01

5TS Messages62 Network OS Message Reference53-1002807-01

VCS MessagesChapter6VCS MessagesVCS-1001VCS-1002VCS-1003VCS-1004VCS-1005VCS-1006VCS-1007VCS-1008VCS-1009Network OS Message Reference 6353-1002807-01

6VCS Messages64 Network OS Message Reference53-1002807-01

Network OS MessagesChapter7AUTH MessagesAUTH-1001MessageMessage TypeSeverityProbable CauseRecommendedAction has been successfully completed.LOGINFOIndicates that the secret database has been updated using the fcsp auth-secret or no fcsp auth-secretcommand. The values for Operation type can be "set" or "remove".No action is required.AUTH-1002MessageMessage TypeSeverityProbable CauseRecommendedAction has failed.LOGERRORIndicates that the specified action to update the secret database using the fcsp auth-secret or no fcspauth-secret command has failed. The values for Operation type can be "set" or "remove".Execute the fcsp auth-secret or no fcsp auth-secret command again.Execute the copy support command and contact your switch service provider.AUTH-1003MessageMessage TypeSeverityProbable Cause type has been successfully set to .LOGINFOIndicates that an authentication configuration parameter was set to a specified value. The data type canbe either authentication type, DH group type, or policy type.Network OS Message Reference 6553-1002807-01

7AUTH-1004RecommendedActionNo action is required.AUTH-1004MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to set type to .LOGERRORIndicates that the fcsp auth command has failed to set the authentication configuration value. The datatype can be either authentication type, DH group type, hash type, or policy type.Execute the fcsp auth command.Execute the copy support command and contact your switch service provider.AUTH-1006MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to open authentication configuration file.LOGWARNINGIndicates an internal problem with the security policy.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.AUTH-1007MessageMessage TypeSeverityProbable CauseRecommendedActionThe proposed authentication protocol(s) are not supported: port .LOGERRORIndicates that the proposed authentication protocol types are not supported by the local port.Execute the fcsp auth command to make sure the local switch supports the following protocols: FibreChannel Authentication Protocol (FCAP) or Diffie-Hellman Challenge Handshake Authentication Protocol(DH-CHAP).66 Network OS Message Reference53-1002807-01

AUTH-1010 7AUTH-1010MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to initialize security policy: switch , error .LOGERRORIndicates an internal problem with the security policy.Reload or power cycle the switch.If the message persists, execute the copy support command and contact your switch service provider.AUTH-1012MessageMessage TypeSeverityProbable CauseRecommendedActionAuthentication is rejected: port explain reason .LOGWARNINGIndicates that the specified authentication is rejected because the remote entity does not supportauthentication.Make sure the entity at the other end of the link supports authentication.AUTH-1013MessageMessage TypeSeverityProbable CauseRecommendedActionCannot perform authentication request message: port , message code.LOGWARNINGIndicates that the system is running low on resources when receiving an authentication request. Usuallythis problem is transient. The authentication may fail.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.Network OS Message Reference 6753-1002807-01

7AUTH-1014AUTH-1014MessageMessage TypeSeverityProbable CauseRecommendedActionInvalid port value to : port .LOG | FFDCERRORIndicates an internal problem with the security policy.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.AUTH-1017MessageMessage TypeSeverityProbable CauseRecommendedActionInvalid value to start authentication request: port , operation code.LOGERRORIndicates an internal problem with the security policy.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.AUTH-1018MessageMessage TypeSeverityProbable CauseRecommendedActionInvalid value to check protocol type: port .LOGERRORIndicates an internal problem with the security policy.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.68 Network OS Message Reference53-1002807-01

AUTH-1020 7AUTH-1020MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to create timer for authentication: port .LOGINFOIndicates that an authentication message timer was not created.Usually this problem is transient. The authentication may fail.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.AUTH-1022MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to extract from payload: port .LOGERRORIndicates that the authentication process failed to extract a particular value from the receiving payload.Usually this problem is transient. The authentication may fail.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.AUTH-1025MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to get during : port .LOGERRORIndicates that the authentication process failed to get expected information during the specifiedauthentication phase. Usually this problem is transient. The authentication may fail.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.Network OS Message Reference 6953-1002807-01

7AUTH-1026AUTH-1026MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to during negotiation phase: port .LOGWARNINGIndicates that the authentication failed to get device or host bus adapter (HBA) information due to aninternal failure. Usually this problem is transient. The authentication may fail.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.AUTH-1027MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to select during : value port .LOGERRORIndicates that the authentication process failed to select an authentication value (for example, DH group,hash value, or protocol type) from a receiving payload during the specified authentication phase. Thiserror occurred because the local switch does not support the specified authentication value.Check the authentication configuration and reset the supported value if needed using the fcsp authcommand.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.AUTH-1028MessageMessage TypeSeverityProbable CauseFailed to allocate for : port .LOGERRORIndicates that the authentication process failed because the system is low on memory. Usually thisproblem is transient. The authentication may fail.The data type is a payload or structure that failed to get memory. The operation phase specifies whichoperation of a particular authentication phase failed.70 Network OS Message Reference53-1002807-01

AUTH-1029 7RecommendedActionReinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.AUTH-1029MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to get for message: port , retval.LOGERRORIndicates that the authentication process failed to get a particular authentication value at certain phase.Usually this problem is transient. The authentication may fail.The data type is a payload or structure that failed to get memory.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.AUTH-1030MessageMessage TypeSeverityProbable CauseRecommendedActionInvalid message code for message: port .LOGERRORIndicates that the receiving payload does not have a valid message code during the specifiedauthentication phase. Usually this problem is transient. The authentication may fail.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.AUTH-1031MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to retrieve secret value: port .LOGERRORIndicates that the secret value was not set properly for the authenticated entity.Reset the secret value using the fcsp auth-secret command.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.Network OS Message Reference 7153-1002807-01

7AUTH-1032AUTH-1032MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to generate for payload: length , error code , port .LOGERRORIndicates that the authentication process failed to generate specific data (for example, challenge, nonce,or response data) for an authentication payload. This usually relates to an internal failure. A nonce is asingle-use, usually random value used in authentication protocols to prevent replay attacks. Usually thisproblem is transient. The authentication may fail.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.AUTH-1033MessageMessage TypeSeverityProbable CauseRecommendedActionDisable port due to unauthorized switch .LOGERRORIndicates that an entity, which was not configured in the switch connection control (SCC) policy tried toconnect to the port.Add the entity World Wide Name (WWN) to the SCC policy using the secpolicy defined-policycommand, then reinitialize authentication using the shutdown and no shutdown commands or thechassis disable and chassis enable commands.AUTH-1034MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to validate name in : port .LOGERRORIndicates that the entity name in the payload is not in the correct format.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.72 Network OS Message Reference53-1002807-01

AUTH-1035 7AUTH-1035MessageMessage TypeSeverityProbable CauseRecommendedActionInvalid length in message: length , port.LOGERRORIndicates that a particular data field in the authentication message has an invalid length field. This errorusually relates to an internal failure.Usually this problem is transient. The authentication may fail.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis disable commands.If the message persists, execute the copy support command and contact your switch service provider.AUTH-1036MessageMessage TypeSeverityProbable CauseRecommendedActionInvalid state for : port .LOGERRORIndicates that the switch received an unexpected authentication message. Usually this problem istransient. The authentication may fail.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis disable commands.If the message persists, execute the copy support command and contact your switch service provider.AUTH-1037MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to response for : init_len , resp_len , port .LOGERRORIndicates that a Diffie-Hellman Challenge Handshake Authentication Protocol (DH-CHAP) authenticationoperation failed on the specified port due to mismatched response values between two entities. The errormay indicate that an invalid entity tried to connect to the switch.Check the connection port for a possible security attack.Reinitialize authentication using the shutdown and no shutdown commands or the chassis disableand chassis disable commands.If the message persists, execute the copy support command and contact your switch service provider.Network OS Message Reference 7353-1002807-01

7AUTH-1039AUTH-1039MessageMessage TypeSeverityProbable CauseRecommendedActionNeighboring switch has conflicting authentication policy: Port disabled.LOGERRORIndicates that the neighboring switch has a conflicting authentication policy enabled. The E_Port hasbeen disabled because the neighboring switch has rejected the authentication negotiation and the localswitch has a strict switch authentication policy.Correct the switch policy configuration on either of the switches using the fcsp auth command, and thenenable the port using the no shutdown command.AUTH-1040MessageMessage TypeSeverityProbable CauseRecommendedActionReject authentication on port , because switch authentication policyis set to OFF.LOGINFOIndicates that the local switch has rejected the authentication because the switch policy is turned off. Ifthe neighboring switch has a strict (ON) switch policy, the port will be disabled due to conflictingconfiguration settings. Otherwise, the E_Port will form without authentication.If the port is disabled, correct the switch policy configuration on either of the switches using the fcsp authcommand, and then enable the port on neighboring switch using the no shutdown command. If theE_Port has formed, no action is required.AUTH-1041MessageMessage TypeSeverityProbable CauseRecommendedActionPort has been disabled, because an authentication-reject wasreceived with code '' and explanation ''.LOGERRORIndicates that the specified port has been disabled because it received an authentication-reject responsefrom the connected switch or device. The error may indicate that an invalid entity tried to connect to theswitch.Check the connection port for a possible security attack.Check the shared secrets using the show fcsp auth-secret dh-chap command and reinitializeauthentication using the shutdown and no shutdown commands or the chassis disable and chassisdisable commands.If the message persists, execute the copy support command and contact your switch service provider.74 Network OS Message Reference53-1002807-01

AUTH-1042 7AUTH-1042MessageMessage TypeSeverityProbable CauseRecommendedActionPort has been disabled, because authentication failed with code'' and explanation ''.LOGERRORIndicates that the specified port has been disabled because the connecting switch or device failed toauthenticate. The error may indicate that an invalid entity attempted to connect to the switch.Check the connection port for a possible security attack.Check the shared secrets using the show fcsp auth-secret dh-chap command and reinitializeauthentication using the shutdown and no shutdown commands or the chassis disable and chassisdisable commands.If the message persists, execute the copy support command and contact your switch service provider.AUTH-1044MessageMessage TypeSeverityProbable CauseRecommendedActionAuthentication . Disabling the port .LOG | FFDCERRORIndicates that the authentication has timed out after multiple retries and as a result, the specified port hasbeen disabled. This problem may be transient due to the system CPU load. In addition, a defective smallform-factor pluggable (SFP) or faulty cable may have caused the failure.Check the SFP and the cable. Then try to enable the port using the no shutdown command.AUTH-3001MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: type has been changed from[] to [].AUDITSECURITYINFOIndicates that a authentication configuration parameter was set to a specified value. The data type canbe either authentication type, DH group type, hash type, or policy type.No action is required.Network OS Message Reference 7553-1002807-01

7AUTH-3002AUTH-3002MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: .AUDITSECURITYINFOIndicates that the secret database has been updated using the fcsp auth-secret command.No action is required.AUTH-3004MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: failed, Info: Neighboring switch has a conflictingauthentication policy; Port disabled.AUDITSECURITYINFOIndicates that the specified E_Port was disabled because the neighboring switch rejected theauthentication negotiation and the local switch has a strict switch authentication policy.Correct the switch policy configuration on either of the switches using the fcsp auth command, and thenenable the port using no shutdown command.AUTH-3005MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: failed, Info: Rejecting authentication request onport because switch policy is turned OFF.AUDITSECURITYINFOIndicates that the local switch has rejected the authentication request because the switch policy is turnedoff. If the neighboring switch has a strict (ON) switch policy, the port will be disabled due to conflictingconfiguration settings. Otherwise, the E_Port will form without authentication.If the specified port is disabled, correct the switch policy configuration on either of the switches using thefcsp auth command, and then enable the port on the neighboring switch using no shutdown command.If the E_Port formed, no action is required.76 Network OS Message Reference53-1002807-01

AUTH-3006 7AUTH-3006MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: failed, Info: Authentication failed on port due to mismatch of DH-CHAP shared secrets.AUDITSECURITYINFOIndicates that a Diffie-Hellman Challenge Handshake Authentication Protocol (DH-CHAP) authenticationoperation failed on the specified port due to mismatched response values between two entities. The errormay indicate that an invalid entity tried to connect to the switch.Check the connection port for a possible security attack.Check the shared secrets using the show fcsp auth-secret dh-chap command and reinitializeauthentication using the shutdown and no shutdown commands or the chassis disable and chassisenable commands.If the message persists, execute the copy support command and contact your switch service provider.AUTH-3007MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: failed, Info: Port disabled, because anauthentication-reject was received with code '' and Explanation''.AUDITSECURITYINFOIndicates that the specified port was disabled because it received an authentication-reject response fromthe connected switch or device. The error may indicate that an invalid entity tried to connect to theswitch.Check the connection port for a possible security attack.Check the shared secrets using show fcsp auth-secret dh-chap and reinitialize authentication usingthe shutdown and no shutdown commands or the chassis disable and chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.Network OS Message Reference 7753-1002807-01

7AUTH-3008AUTH-3008MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: failed, Info: Port has been disableddue to authentication failure with code '' and explanation''.AUDITSECURITYINFOIndicates that the specified port has been disabled because the connecting switch or device failed toauthenticate. The error may indicate that an invalid entity tried to connect to the switch.Check the connection port for a possible security attack.Check the shared secrets using show fcsp auth-secret dh-chap and reinitialize authentication usingthe shutdown and no shutdown commands or the chassis disable and chassis enable commands.If the message persists, execute the copy support command and contact your switch service provider.78 Network OS Message Reference53-1002807-01

BL-1000 7BL MessagesBL-1000MessageMessage TypeSeverityProbable CauseRecommendedActionInitializing ports...LOGINFOIndicates that the switch has started initializing the ports.No action is required.BL-1001MessageMessage TypeSeverityProbable CauseRecommendedActionPort initialization completed.LOGINFOIndicates that the switch has completed initializing the ports.No action is required.BL-1002MessageMessage TypeSeverityProbable CauseRecommendedActionInit Failed: DISABLED because internal ports were not ONLINE, .FFDC | LOGCRITICALIndicates that the interface module initiation failed because one or more of the internal ports were notonline. The interface module is faulted.Make sure that the interface module is seated correctly. If the interface module is seated correctly, reloador power cycle the interface module using the power-off and power-on commands.Execute the diag systemverification command to verify that the interface module does not havehardware problems.Execute the diag post command to make sure that Power-On Self-Test (POST) is enabled.Additional interface module fault messages precede and follow this error, providing more information.Refer to other error messages for the recommended action.If the message persists, replace the interface module.Network OS Message Reference 7953-1002807-01

7BL-1003BL-1003MessageMessage TypeSeverityProbable CauseRecommendedActionFaulty interface module in .FFDC | LOGCRITICALIndicates a faulty interface module in the specified slot.Make sure that the interface module is seated correctly. If the interface module is seated correctly, reloador power cycle the interface module using the power-off and power-on commands.Execute the diag systemverification command to verify that the interface module does not havehardware problems.Execute the diag post command to make sure that Power-On Self-Test (POST) is enabled.If the message persists, replace the interface module.BL-1004MessageMessage TypeSeverityProbable CauseRecommendedActionSuppressing interface module fault in .FFDC | LOGCRITICALIndicates that the specified interface module experienced a failure but was not faulted due to a usersetting.Reload or power cycle the interface module using the power-off and power-on commands.Execute the diag systemverification command to verify that the interface module does not havehardware problems.Execute the diag post command to make sure that Power-On Self-Test (POST) is enabled.If the message persists, replace the interface module.BL-1006MessageMessage TypeSeverityProbable CauseInterface module NOT faulted. Peer interface module experienced abrupt failure.LOGINFOIndicates that the errors (mostly synchronization errors) on this interface module are harmless. Probably,the standby management module connected to the active management module has experiencedtransitory problems.80 Network OS Message Reference53-1002807-01

BL-1007 7RecommendedActionExecute the show ha command to verify that the standby management module is healthy. If the problempersists, remove and reinstall the faulty interface module.If the standby management module was removed or faulted by user intervention, no action is required.BL-1007MessageMessage TypeSeverityProbable CauseRecommendedActioninterface module #: state is inconsistent with EM.bl_cflags 0x, slot_on , slot_off, faulty , status .LOGWARNINGIndicates that a failover occurred while a interface module was initializing on the previously activemanagement module.No action is required. The interface module is re-initialized. Because re-initializing a interface module is adisruptive operation and can stop I/O traffic, you must stop and restart the traffic during this process.BL-1008MessageMessage TypeSeverityProbable CauseRecommendedAction control-plane failure. Expected value: 0x, Actual: 0x.FFDC | LOGCRITICALIndicates that the interface module has experienced a hardware failure or was removed without followingthe recommended removal procedure.Make sure that the interface module is seated correctly. If the interface module is seated correctly, reloador power cycle the interface module using the power-off and power-on commands.Execute the diag systemverification command to verify that the interface module does not havehardware problems.Execute the diag post command to make sure that Power-On Self-Test (POST) is enabled.If the message persists, replace the interface module.BL-1009MessageMessage TypeSeverityProbable CauseInterface module in slot timed out initializing the chips.FFDC | LOGCRITICALIndicates that the interface module has failed to initialize the application-specific integrated circuit (ASIC)chips.Network OS Message Reference 8153-1002807-01

7BL-1010RecommendedActionMake sure that the interface module is seated correctly. If the interface module is seated correctly, reloador power cycle the interface module using the power-off and power-on commands.Execute the diag systemverification command to verify that the interface module does not havehardware problems.Execute the diag post command to make sure that Power-On Self-Test (POST) is enabled.If the message persists, replace the interface module.BL-1010MessageMessage TypeSeverityProbable CauseRecommendedActionInterface module in is inconsistent with the hardware settings.LOGWARNINGIndicates that a failover occurred while some hardware changes (such as changing the domain ID) werebeing made on the previously active management module.No action is required. This interface module has been re-initialized. Because re-initializing a interfacemodule is a disruptive operation and can stop I/O traffic, you must stop and restart the traffic during thisprocess.BL-1011MessageMessage TypeSeverityProbable CauseRecommendedActionBusy with emb-port int for chip in minis oninterface module , chip int is disabled. Interruptstatus=0x.FFDC | LOGCRITICALIndicates that too many interrupts in the embedded port caused the specified chip to be disabled. Theprobable cause is too many abnormal frames; the chip is disabled to prevent the management modulefrom becoming too busy.Make sure to capture the console output during this process.Check for a faulty cable, small form-factor pluggable (SFP) transceiver, or device attached to thespecified port.Execute the diag systemverification command to verify that the interface module or switch does nothave hardware problems.Execute the diag post command to make sure that Power-On Self-Test (POST) is enabled.For a modular switch, execute the power-off and power-on commands to power cycle the interfacemodule.For a compact switch, reload or power cycle the switch.If the message persists, replace the interface module or the switch.82 Network OS Message Reference53-1002807-01

BL-1012 7BL-1012MessageMessage TypeSeverityProbable CauseRecommendedActionbport port int is disabled. Status=0x; Port will be re-enabled in a minute.LOGERRORIndicates that the port generated an excessive number of interrupts that may prove unrecoverable to theswitch operation. The port is disabled to prevent the management module from becoming too busy. Theinterface module port number displayed in the message may not correspond to a user port number.Make sure to capture the console output during this process.Check for a faulty cable, small form-factor pluggable (SFP) transceiver, or device attached to thespecified port.For a modular switch, execute the power-off and power-on commands to power cycle the interfacemodule.For a compact switch, reload or power cycle the switch.If the message persists, replace the interface module or the switch.BL-1013MessageMessage TypeSeverityProbable CauseRecommendedActionbport port is faulted. Status=0x;Port will be re-enabled in a minute.LOGERRORIndicates that the port generated an excessive number of interrupts that may prove fatal to the switchoperation. The port is disabled to prevent the management module from becoming too busy. Theinterface module port number displayed in the message may not correspond to the user port number.Make sure to capture the console output during this process.Check for a faulty cable, small form-factor pluggable (SFP) transceiver, or device attached to thespecified port.For a modular switch, execute the power-off and power-on commands to power cycle the interfacemodule.For a compact switch, reload or power cycle the switch.If the message persists, replace the interface module or the switch.Network OS Message Reference 8353-1002807-01

7BL-1014BL-1014MessageMessage TypeSeverityProbable CauseRecommendedActionbport port int is disabled. Status=0x.LOGERRORIndicates that the port generated an excessive number of interrupts that may prove fatal to the switchoperation. The port is disabled to prevent the management module from becoming too busy. Theinterface module port number displayed in the message may not correspond to the user port number.Make sure to capture the console output during this process.For a modular switch, execute the power-off and power-on commands to power cycle the interfacemodule.For a compact switch, execute the reload command to reload the switch.Execute the diag systemverification command to determine if there is a hardware error.Execute the diag post command to make sure that Power-On Self-Test (POST) is enabled.If there is a hardware error, the power-off or power-on command fails on the modular switch, or theerrors are encountered again, replace the interface module or the switch.BL-1015MessageMessage TypeSeverityProbable CauseRecommendedActionbport port is faulted. status=0x.LOGERRORIndicates that the port generated an excessive number of interrupts that may prove fatal to the switchoperation. The port is disabled to prevent the management module from becoming too busy. Theinterface module port number displayed in the message may not correspond to the user port number.Make sure to capture the console output during this process.For a modular switch, execute the power-off and power-on commands to power cycle the interfacemodule.For a compact switch, execute the reload command to reload the switch.Execute the diag systemverification command to determine if there is a hardware error.Execute the diag post command to ensure that Power-On Self-Test (POST) is enabled.If there is a hardware error, the power-off or power-on command fails on the modular switch, or theerrors are encountered again, replace the interface module or the switch.84 Network OS Message Reference53-1002807-01

BL-1016 7BL-1016MessageMessage TypeSeverityProbable CauseRecommendedActionInterface module port in failed to enable.FFDC | LOGCRITICALIndicates that the specified interface module port could not be enabled.Make sure that the interface module is seated correctly. If the interface module is seated correctly, reloador power cycle the interface module using the power-off and power-on commands.Execute the diag systemverification command to verify that the interface module does not havehardware problems.Execute the diag post command to make sure that Power-On Self-Test (POST) is enabled.If the message persists, replace the interface module.BL-1017MessageMessage TypeSeverityProbable CauseRecommendedAction Initializing.LOGINFOIndicates that the specified slot has started initializing the ports.No action is required.BL-1018MessageMessage TypeSeverityProbable CauseRecommendedAction Initialization completed.LOGINFOIndicates that the specified slot has completed initializing the ports.No action is required.Network OS Message Reference 8553-1002807-01

7BL-1019BL-1019MessageMessage TypeSeverityProbable CauseRecommendedAction, retry , internal port retry initialization, .LOGINFOIndicates that the specified slot had internal ports that are not online. Initiated a retry on ports that failedto go online.No action is required.BL-1020MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch timed out initializing the chips.LOG | FFDCCRITICALIndicates that the switch has failed to initialize the application-specific integrated circuit (ASIC) chips.Reload power cycle the switch.Execute the diag systemverification command to verify that the switch does not have hardwareproblems.Execute the diag post command to make sure that Power-On Self-Test (POST) is enabled.If the message persists, replace the switch.BL-1021MessageMessage TypeSeverityProbable CauseRecommendedActionRetry , internal port retry initialization, .LOGINFOIndicates that the switch had internal ports that are not online. Initiated a retry on ports that failed to goonline.No action is required.86 Network OS Message Reference53-1002807-01

BL-1022 7BL-1022MessageMessage TypeSeverityProbable CauseRecommendedActionInit Failed: Switch DISABLED because internal ports were not ONLINE, .LOGCRITICALIndicates that the switch initiation failed because one or more of the internal ports were not online. Theswitch is faulted.Reload or power cycle the switch.Execute the diag systemverification command to verify that the switch does not have hardwareproblems.Execute the diag post command to make sure that Power-On Self-Test (POST) is enabled.Additional fault messages precede and follow this error providing more information. Refer to other errormessages for recommended action.If the message persists, replace the switch.BL-1023MessageMessage TypeSeverityProbable CauseRecommendedActionInterface module in was reset before initialization completed. As aresult the interface module is faulted.LOGCRITICALIndicates that the interface module was reset before the initialization completed.Reload or power cycle the interface module using the power-off and power-on commands. If themessage persists, replace the interface module.BL-1024MessageMessage TypeSeverityProbable CauseRecommendedActionAll ports on the interface module in will be reset as part of thefirmware upgrade.LOGINFOIndicates that a recent firmware upgrade caused the interface module firmware to be upgraded andresulted in a cold upgrade. As part of the upgrade, all data path elements were reset.No action is required.Network OS Message Reference 8753-1002807-01

7BL-1026BL-1026MessageMessage TypeSeverityProbable CauseRecommendedActionInternal port offline during warm recovery, state (0x).LOGCRITICALIndicates that an internal port went offline during warm recovery of the switch. The switch will reboot andstart a cold recovery.Execute the copy support command and reload the switch.Execute the diag post command to make sure Power-On Self-Test (POST) is enabled.If the problem persists, replace the switch.BL-1027MessageMessage TypeSeverityProbable CauseRecommendedActionInterface module in faulted, boot failed; status 0x0x 0x.LOGCRITICALIndicates that the interface module failed to boot properly.Reload or power cycle the interface module using the power-off and power-on commands. If themessage persists, replace the interface module.BL-1028MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch faulted; internal processor was reset before switch init completed.LOGCRITICALIndicates that the switch internal processor was reset before the initialization completed.Reload or power cycle the switch. If the message persists, replace the switch.88 Network OS Message Reference53-1002807-01

BL-1029 7BL-1029MessageMessage TypeSeverityProbable CauseRecommendedActionAll ports on the switch will be reset as part of the firmware upgrade.LOGINFOIndicates that a recent firmware upgrade caused the switch internal processor firmware to be upgradedand resulted in a cold upgrade. As part of the upgrade, all data path elements were reset.No action is required.BL-1031MessageMessage TypeSeverityProbable CauseRecommendedActionLink timeout in internal port (slot , port ) causedinterface module fault. Use power-off/power-on commands to recover it.LOGCRITICALIndicates that link time out occurred in one of the back-end internal ports.Power cycle the interface module using the power-off and power-on commands.BL-1032MessageMessage TypeSeverityProbable CauseRecommendedAction(,bitmap 0x) ports never came up ONLINE(reason , state ).Disabling slot.LOGCRITICALIndicates that the back-end (non-user) ports have not come online within the time limit.Reload or power cycle the interface module using the power-off and power-on commands.Execute the diag systemverification command to verify that the interface module does not havehardware problems.Execute the diag post command to make sure that Power-On Self-Test (POST) is enabled.If the message persists, replace the interface module.Network OS Message Reference 8953-1002807-01

7BL-1033BL-1033MessageMessage TypeSeverityProbable CauseRecommendedAction(,bitmap 0x) No disable acknowledgmentfrom ports (state ). Disabling slot.LOGCRITICALIndicates that the system has timed out waiting for the disable acknowledgment messages from the userports.Reload or power cycle the interface module using the power-off and power-on commands.Execute the diag systemverification command to verify that the interface module does not havehardware problems.Execute the diag post command to make sure that Power-On Self-Test (POST) is enabled.If the message persists, replace the interface module.BL-1034MessageMessage TypeSeverityProbable CauseRecommendedAction CEE initialization completed.LOGINFOIndicates that the specified slot has completed initializing the Converged Enhanced Ethernet (CEE)ports.No action is required.BL-1037MessageMessage TypeSeverityProbable CauseRecommendedActionFaulting chip in , miniS = ,port = due to BE/BI port fault.LOGCRITICALIndicates that all ports on the chip have been disabled due to a fault on the chip.Execute the diag systemverification command to determine if there is a hardware error.Execute the diag post command to make sure that Power-On Self-Test (POST) is enabled.90 Network OS Message Reference53-1002807-01

BL-1038 7BL-1038MessageMessage TypeSeverityProbable CauseRecommendedActionInconsistent FPGA image version detected, reload the switch for recovery.LOGCRITICALIndicates that the field-programmable gate array (FPGA) image version is incompatible with the softwareversion.Reload the switch. If the message persists, replace the switch.BL-1039MessageMessage TypeSeverityProbable CauseRecommendedActionInconsistent FPGA image version detected, faulting the interface module in .LOGCRITICALIndicates that the field-programmable gate array (FPGA) image version is incompatible with the softwareversion.Power cycle the interface module using the power-off and power-on commands. If the messagepersists, replace the interface module.BL-1045MessageMessage TypeSeverityProbable CauseRecommendedActionmini SFP+ (SN: ) is only supported in certain high portcount interface modules, not interface module in slot with ID .LOGERRORIndicates that the mini (form factor) enhanced small form-factor pluggable (SFP+) transceiver issupported only by a certain type of interface module, but it can be inserted in other interface modules.Replace the mini SFP+ transceiver with an SFP or SFP+ transceiver.Network OS Message Reference 9153-1002807-01

7BL-1046BL-1046MessageMessage TypeSeverityProbable CauseRecommendedAction error on SFP in Slot /Port (). Reseat or replace the SFP.LOGERRORIndicates that checksum in an area on the small form-factor pluggable (SFP) transceiver does not matchwith the computed value or there is problem accessing the data.Reseat the SFP transceiver. If the problem persists, replace the SFP transceiver.BL-1047MessageMessage TypeSeverityProbable CauseRecommendedActionBuffer optimized mode is turned for slot .LOGINFOIndicates that the buffer optimized mode is changed for the specified slot.No action is required.92 Network OS Message Reference53-1002807-01

BLL-1000 7BLL MessagesBLL-1000MessageMessage TypeSeverityProbable CauseRecommendedActionASIC driver detected port as faulty (reason: ).FFDC | LOGCRITICALIndicates that an interface module regulation problem was reported on the specified slot. The interfacemodule is faulted.The reason codes are as follows:• 1 = Available buffer overflow• 2 = Backend port buffer timeout• 3 = Backend port got shut down• 4 = Embedded port buffer timeout• 5 = Excessive busy mini buffer• 6 = Excessive RCC VC on E_Port• 7 = Excessive RCC VC on FL_Port• 8 = Fail detection buffer tag error• 9 = Fail detection TX parity error• 10 = EPI CMEM interrupt error• 11 = Checkpoint Middleware Interface (CMI) interrupt error• 12 = Interrupt overrun• 13 = FDET interrupt• 14 = Interrupt suspended• 15 = Filter LISTD error• 16 = Unknown filter LIST error• 17 = Wait for LPC open state• 18 = Wait for Old port state• 19 = Wait for Open init state• 20 = TX parity error• 21 = RAM parity error• 22 = Built in Self Repair (BISR) or RAMINIT errorMake sure the interface module is seated correctly. If the interface module is seated correctly, reload orpower cycle the interface module using the power-off and power-on commands.Execute the diag systemverification command to verify that the interface module does not havehardware problems.If the message persists, replace the interface module.Network OS Message Reference 9353-1002807-01

7C2-1004C2 MessagesC2-1004MessageMessage TypeSeverityProbable CauseRecommendedActionS,C: Invalid DMA ch pointer, chan:,good_addr:0x bad_addr:0x.LOGERRORIndicates an internal error in the application-specific integrated circuit (ASIC) hardware that may degradethe data traffic.Restart the system at the next maintenance window. If the problem persists, replace the interfacemodule.C2-1006MessageMessage TypeSeverityProbable CauseRecommendedActionS,C: Internal link errors have been reported, no hardwarefaults identified, continuing to monitor for errors: fault1:,fault2:, thresh1:0x.LOGWARNINGIndicates that some internal link errors have been detected. These errors can be normal in an activerunning system.The system automatically starts a more detailed monitoring of the errors reported in the internalhardware. There is no action required by the user at this time. If any actual hardware failures aredetected, the C2-1010 message will be generated identifying the failing field-replaceable unit (FRU).No action is required.C2-1007MessageMessage TypeSeverityProbable CauseS,P (): At next port statechange, best effort QoS will be turned off automatically as it is no longersupported under this configuration.LOGWARNINGIndicates that quality of service (QoS) will be turned off automatically at next port state change becausebest effort is no longer supported on 4 Gbps or 8 Gbps platform long distance ports.94 Network OS Message Reference53-1002807-01

C2-1008 7RecommendedActionNo action is required.C2-1008MessageMessage TypeSeverityProbable CauseRecommendedActionS,P (): QoS overwritesvc-link-init idle. ARB will be used on the link.LOGWARNINGIndicates that quality of service (QoS) overwrites the fill word IDLE used in the long distance links.Arbitrated loop (ARB) will be used on the link.No action is required.C2-1009MessageMessage TypeSeverityProbable CauseRecommendedActionS,P (): vc-link-init arboverwrites fill word IDLE. ARB will be used on the link.LOGWARNINGIndicates that the vc-link-init arb command has overwritten the fill word IDLE. Arbitrated loop (ARB) willbe used on the link.No action is required.C2-1010MessageMessage TypeSeverityProbable CauseRecommendedActionS,C: Internal monitoring of faults has identified suspecthardware, interface module may need to be reset or replaced:fault1:, fault2:, thresh2:0x.LOGCRITICALIndicates that above normal errors were observed in hardware that may or may not impact the datatraffic.Whenever the error is observed persistently, power cycle the specified interface module using thepower-off and power-on commands. If the problem persists, replace the interface module.Network OS Message Reference 9553-1002807-01

7C2-1011C2-1011MessageMessage TypeSeverityProbable CauseRecommendedActionS,P (): Primitive received withEncoding errors, do AL_RESET.LOGWARNINGIndicates encoding errors on the internal links. This error can cause cyclic redundancy check (CRC)errors or frame loss.Whenever the error is observed persistently, power cycle the specified interface module using thepower-off and power-on commands. If the problem persists, check the backplane or replace theinterface module.C2-1012MessageMessage TypeSeverityProbable CauseRecommendedActionS,P (): Link Timeout oninternal port ftx= tov= (>), interface module may need to be reset or replaced.LOGWARNINGIndicates that above normal errors were observed in hardware that may or may not impact the datatraffic.Whenever the error is observed persistently, power cycle the specified interface module using thepower-off and power-on commands. If the problem persists, replace the interface module.96 Network OS Message Reference53-1002807-01

C3-1004 7C3 MessagesC3-1004MessageMessage TypeSeverityProbable CauseRecommendedAction,C: Invalid DMA ch pointer, chan:,good_addr:0x bad_addr:0x.LOGERRORIndicates an internal error in the application-specific integrated circuit (ASIC) hardware that may degradethe data traffic.Reload the system at the next maintenance window. If the problem persists, replace the interfacemodule.C3-1006MessageMessage TypeSeverityProbable CauseRecommendedAction,C: Various non-critical hardware errors were observed:fault1:0x, fault2:0x, thresh1:0x.LOGWARNINGIndicates that some errors were found in hardware that may or may not impact the data traffic.No action is required.C3-1010MessageMessage TypeSeverityProbable CauseRecommendedAction,C: Above normal hardware errors were observed:fault1:, fault2:, thresh2:0x.LOGCRITICALIndicates that above normal errors were observed in hardware that may or may not impact the datatraffic.Whenever this error is observed persistently, power cycle the specified interface module using thepower-off and power-on commands. If the problem persists, replace the interface module.Network OS Message Reference 9753-1002807-01

7C3-1011C3-1011MessageMessage TypeSeverityProbable CauseRecommendedActionDetected a complete loss of credit on internal back-end VC: Slot ,Port () vc_no=crd(s)lost=.LOGINFOIndicates that all credits have been lost on the specified virtual channel (VC) and port.No action is required. The link will be reset to recover the credits.C3-1012MessageMessage TypeSeverityProbable CauseRecommendedAction,P(): Link Timeout oninternal port ftx= tov= (>) vc_no= crd(s)lost=complete_loss:.LOGWARNINGIndicates that above normal errors were observed in hardware that may or may not impact the datatraffic.Whenever this error is observed persistently, power cycle the specified interface module using thepower-off and power-on commands. If the problem persists, replace the interface module.C3-1014MessageMessage TypeSeverityProbable CauseRecommendedActionLink Reset on internal Port ,P() vc_no= crd(s)lost=.LOGWARNINGIndicates that one or more credits were lost and the link is reset.Whenever this error is observed persistently, power cycle the specified interface module using thepower-off and power-on commands. If the problem persists, replace the interface module.98 Network OS Message Reference53-1002807-01

C3-1017 7C3-1017MessageMessage TypeSeverityProbable CauseRecommendedActionInterface module in Slot- failed due to unavailability of ports inthe internal trunk.LOGERRORIndicates that the specified interface module failed due to unavailability of ports in the internal trunk.Whenever this error is observed persistently, power cycle the specified interface module using thepower-off and power-on commands. If the problem persists, replace the interface module.C3-1019MessageMessage TypeSeverityProbable CauseRecommendedAction,C: HW ASIC Chip TXQ FID parity error threshold reachedtype = 0x.LOGWARNINGIndicates an internal error in the application-specific integrated circuit (ASIC) hardware that may degradethe data traffic.Reload the system at the next maintenance window.C3-1020MessageMessage TypeSeverityProbable CauseRecommendedAction,P(): Some non-criticalCRC with good EOF errors were observed: current:0x,last:0x, thresh1:0x.LOGWARNINGIndicates that some non-critical errors were detected in the hardware.No action is required.Network OS Message Reference 9953-1002807-01

7CHS-1002CHS MessagesCHS-1002MessageMessage TypeSeverityProbable CauseRecommendedActionki_gd_register_action failed with rc = .LOG | FFDCERRORIndicates an internal error.Reload or power cycle the switch.CHS-1003Message Slot ENABLED but Not Ready during recovery, disabling slot = , rval =.Message TypeSeverityProbable CauseRecommendedActionLOGERRORIndicates that the slot state has been detected as inconsistent during failover or recovery.For a modular switch, execute the power-off and power-on commands to power cycle the interfacemodule.For a compact switch, reload or power cycle the switch.CHS-1004MessageMessage TypeSeverityProbable CauseRecommendedActionInterface module attach failed during recovery, disabling slot = ,rval = .LOGERRORIndicates that the specified interface module has failed during failover or recovery.For a modular switch, execute the power-off and power-on commands to power cycle the interfacemodule.For a compact switch, reload or power cycle the switch.100 Network OS Message Reference53-1002807-01

CHS-1005 7CHS-1005MessageMessage TypeSeverityProbable CauseRecommendedActionDiag attach failed during recovery, disabling slot = .LOGERRORIndicates that the diagnostic interface module attach operation has failed during failover or recovery.For a modular switch, execute the power-off and power-on commands to power cycle the interfacemodule.For a compact switch, reload or power cycle the switch.Network OS Message Reference 10153-1002807-01

7DCM-1001DCM MessagesDCM-1001MessageMessage TypeSeverityProbable CauseRecommendedActionVCS ID is changed from to .LOGINFOIndicates that the VCS ID has been changed.No action is required.DCM-1002MessageMessage TypeSeverityProbable CauseRecommendedActionPostBoot processing on has started.LOGINFOIndicates that the PostBoot processing on specified configuration group has started.No action is required.DCM-1003MessageMessage TypeSeverityProbable CauseRecommendedActionPostBoot processing on is complete.LOGINFOIndicates that the PostBoot processing on specified configuration group has been completed.No action is required.102 Network OS Message Reference53-1002807-01

DCM-1004 7DCM-1004MessageMessage TypeSeverityProbable CauseRecommendedActionConfiguration File Replay has started.LOGINFOIndicates that the configuration replay has started.No action is required.DCM-1005MessageMessage TypeSeverityProbable CauseRecommendedActionConfiguration Replay is complete.LOGINFOIndicates that the configuration replay has been completed.No action is required.DCM-1006MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: , User command: .AUDITDCMCFGINFOIndicates that the user command has been executed successfully.No action is required.Network OS Message Reference 10353-1002807-01

7DCM-1007DCM-1007MessageMessage TypeSeverityProbable CauseRecommendedActionNo Configuration File Replay.LOGINFOIndicates that configuration file replay will not happen on this system boot up.No action is required.DCM-1008MessageMessage TypeSeverityProbable CauseRecommendedActionConfiguration has been reset to default due to changes in configuration metadata.LOGINFOIndicates that the configuration schema has changed and therefore the old configuration cannot beretained.Replay the saved configuration manually.DCM-1009MessageMessage TypeSeverityProbable CauseRecommendedActionRBridge ID is set to .LOGINFOIndicates that the RBridge ID has changed to the specified value.No action is required.DCM-1010MessageMessage TypeSeverityProbable CauseOperation of setting RBridge ID to failed.LOGINFOIndicates a failure while changing the RBridge ID.104 Network OS Message Reference53-1002807-01

DCM-1011 7RecommendedActionNo action is required.DCM-1011MessageMessage TypeSeverityProbable CauseRecommendedActionVCS enabled: VCS ID is set to .LOGINFOIndicates that the VCS mode has been enabled.No action is required.DCM-1012MessageMessage TypeSeverityProbable CauseRecommendedActionVCS disabled: VCS ID is set to .LOGINFOIndicates that the VCS mode has been disabled.No action is required.DCM-1101MessageMessage TypeSeverityProbable CauseRecommendedActionCopy running-config to startup-config operation successful on this node.LOGINFOIndicates that the running configuration has been copied to the startup configuration on the node.No action is required.Network OS Message Reference 10553-1002807-01

7DCM-1102DCM-1102MessageMessage TypeSeverityProbable CauseRecommendedActionCopy running-config to startup-config operation failed on this node.LOGINFOIndicates failure to copy the running configuration to the startup configuration on the node.No action is required.DCM-1103MessageMessage TypeSeverityProbable CauseRecommendedActionCopy default-config to startup-config operation successful on this node.LOGINFOIndicates that the default configuration has been copied to the startup configuration on the node.No action is required.DCM-1104MessageMessage TypeSeverityProbable CauseRecommendedActionCopy default-config to startup-config operation failed on this node.LOGINFOIndicates failure to copy the default configuration to the startup configuration on the node.No action is required.DCM-1105MessageMessage TypeSeverityProbable CauseCopy of the downloaded config file to the current running-config has completedsuccessfully on this node.LOGINFOIndicates that the downloaded configuration file has been copied to the current running configuration.106 Network OS Message Reference53-1002807-01

DCM-1106 7RecommendedActionNo action is required.DCM-1106MessageMessage TypeSeverityProbable CauseRecommendedActionCopy of the downloaded config file to the current startup-config has completedsuccessfully on this node.LOGINFOIndicates that the downloaded configuration file has been copied to the current startup configuration.No action is required.DCM-1107MessageMessage TypeSeverityProbable CauseRecommendedActionStartup configuration file has been uploaded successfully to the remote location.LOGINFOIndicates that the startup configuration file has been uploaded successfully.No action is required.DCM-1108MessageMessage TypeSeverityProbable CauseRecommendedActionRunning configuration file has been uploaded successfully to the remote location.LOGINFOIndicates that the running configuration file has been uploaded successfully.No action is required.Network OS Message Reference 10753-1002807-01

7DCM-1109DCM-1109MessageMessage TypeSeverityProbable CauseRecommendedActionError () encountered while copying configuration to flash/USB.LOGINFOIndicates a failure to copy configuration file to flash.No action is required.DCM-1201MessageMessage TypeSeverityProbable CauseRecommendedActionFIPS Zeroize operation request received.LOGINFOIndicates that the Federal Information Protection Standard (FIPS) Zeroize operation request has beenreceived.No action is required.DCM-1202MessageMessage TypeSeverityProbable CauseRecommendedActionFIPS Zeroize operation: failed as VCS is enabled for this node.LOGERRORIndicates that the Federal Information Protection Standard (FIPS) Zeroize operation has failed becauseVCS is enabled on the node.Execute the no vcs enable command to disable the VCS mode and then perform the Zeroize operation.108 Network OS Message Reference53-1002807-01

DCM-1203 7DCM-1203MessageMessage TypeSeverityProbable CauseRecommendedActionFIPS Zeroize operation: confirmed that VCS is not enabled for this node.LOGINFOIndicates that VCS is not enabled on the node and therefore the Federal Information Protection Standard(FIPS) Zeroize operation will proceed.No action is required.DCM-1204MessageMessage TypeSeverityProbable CauseRecommendedActionFIPS Zeroize operation: all client sessions are notified that Zeroize in progress.LOGINFOIndicates that all client sessions are notified about the Federal Information Protection Standard (FIPS)Zeroize operation in progress and the commands cannot be executed.No action is required.DCM-1205MessageMessage TypeSeverityProbable CauseRecommendedActionFIPS Zeroize operation: starting with cleanup for Zeroize.LOGINFOIndicates that the configuration files cleanup for Federal Information Protection Standard (FIPS) Zeroizehas started.No action is required.Network OS Message Reference 10953-1002807-01

7DCM-1206DCM-1206MessageMessage TypeSeverityProbable CauseRecommendedActionFIPS Zeroize operation: starting prepare phase for Zeroize.LOGINFOIndicates that the prepare phase for Federal Information Protection Standard (FIPS) Zeroize has started,during which all the services will be shut down.No action is required.DCM-1207MessageMessage TypeSeverityProbable CauseRecommendedActionFIPS Zeroize operation: failed in prepare phase step for Zeroize.LOGINFOIndicates that the Federal Information Protection Standard (FIPS) Zeroize operation has failed during theprepare phase.No action is required.DCM-1208MessageMessage TypeSeverityProbable CauseRecommendedActionFIPS Zeroize operation: Running Zeroize for secure deletion of the userconfiguration data.LOGINFOIndicates that the Federal Information Protection Standard (FIPS) Zeroize operation is running for securedeletion of the user configuration data.No action is required.110 Network OS Message Reference53-1002807-01

DCM-1209 7DCM-1209MessageMessage TypeSeverityProbable CauseRecommendedActionFIPS Zeroize operation: failed during secure deletion of the user configurationdata.LOGERRORIndicates that the Federal Information Protection Standard (FIPS) Zeroize operation has failed duringsecure deletion of the user configuration data.Refer to the reason code indicated in the fips zeroize command output for possible action.DCM-1210MessageMessage TypeSeverityProbable CauseRecommendedActionFIPS Zeroize operation failed.LOGINFOIndicates that the Federal Information Protection Standard (FIPS) Zeroize operation has failed.No action is required.DCM-1211MessageMessage TypeSeverityProbable CauseRecommendedActionFIPS Zeroize operation executed successfully.LOGINFOIndicates that the Federal Information Protection Standard (FIPS) Zeroize operation has been executedsuccessfully.No action is required.Network OS Message Reference 11153-1002807-01

7DCM-1212DCM-1212MessageMessage TypeSeverityProbable CauseRecommendedActionFIPS Zeroize operation failed. Node zeroizing or already zeroized.LOGINFOIndicates that the Federal Information Protection Standard (FIPS) Zeroize operation has failed becausethe node is zeroizing or it was already zeroized.No action is required.DCM-2001MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: Successful login attempt through.AUDITDCMCFGINFOIndicates that the log in was successful. An IP address is displayed when the login occurs over a remoteconnection.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.DCM-2002MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: Successful logout by user [].AUDITDCMCFGINFOIndicates that the specified user has successfully logged out.No action is required.112 Network OS Message Reference53-1002807-01

DCM-3005 7DCM-3005MessageMessage TypeSeverityProbable CauseRecommendedActionDCM ASSERT Service:LOGERRORIndicates an internal failure in the distributed configuration manager (DCM).Execute the copy support command and contact your switch service provider.DCM-3051MessageMessage TypeSeverityProbable CauseRecommendedActionEncountered Database Corruption. System going down for auto-recovery.LOGERRORIndicates that the database operation failed because of database corruption. The system reloads forauto-recovery of the database.No action is required.DCM-3052MessageMessage TypeSeverityProbable CauseRecommendedActionDatabase Corruption was detected. Therefore, system was rebooted for recovery andmay have taken longer than usual.LOGINFOIndicates that the last system reload was for auto-recovery of database because the database corruptionwas detected.No action is required.Network OS Message Reference 11353-1002807-01

7DCM-4001DCM-4001MessageMessage TypeSeverityProbable CauseRecommendedActionDatabase schema conversion succeeded.LOGINFOIndicates that after a firmware download, the database schema was successfully converted to theschema supported by the firmware.No action is required.DCM-4002MessageMessage TypeSeverityProbable CauseRecommendedActionDatabase schema conversion failed.LOGINFOIndicates that after a firmware download, a failure was encountered in converting the database schemato the schema supported by the firmware.No action is required.114 Network OS Message Reference53-1002807-01

DOT1-1001 7DOT1 MessagesDOT1-1001MessageMessage TypeSeverityProbable CauseRecommendedAction802.1X is enabled globally.DCEINFOIndicates that 802.1X is enabled globally.No action is required.DOT1-1002MessageMessage TypeSeverityProbable CauseRecommendedAction802.1X is disabled globally.DCEINFOIndicates that 802.1X is disabled globally.No action is required.DOT1-1003MessageMessage TypeSeverityProbable CauseRecommendedAction802.1X is enabled for port .DCEINFOIndicates that 802.1X is enabled on the specified port.No action is required.Network OS Message Reference 11553-1002807-01

7DOT1-1004DOT1-1004MessageMessage TypeSeverityProbable CauseRecommendedActionPort is forcefully unauthorized.DCEINFOIndicates that the specified port has been unauthorized forcefully using the dot1x port-controlforce-unauthorized command.No action is required.DOT1-1005MessageMessage TypeSeverityProbable CauseRecommendedAction802.1X authentication is successful on port .DCEINFOIndicates that authentication has succeeded on the specified port.No action is required.DOT1-1006MessageMessage TypeSeverityProbable CauseRecommendedAction802.1X authentication has failed on port .DCEWARNINGIndicates that authentication has failed on the specified port due to incorrect credentials or the remoteauthentication dial-in user service (RADIUS) server is not functioning properly.Check the credentials configured with the supplicant and RADIUS server. You can reconfigure theattributes on the RADIUS server using the radius-server command.116 Network OS Message Reference53-1002807-01

DOT1-1007 7DOT1-1007MessageMessage TypeSeverityProbable CauseRecommendedActionNo RADIUS server available for authentication.DCECRITICALIndicates that there is no remote authentication dial-in user service (RADIUS) server available forauthentication.Check whether the configured RADIUS servers are reachable and are functioning.DOT1-1008MessageMessage TypeSeverityProbable CauseRecommendedActionPort is forcefully authorized.DCEINFOIndicates that the specified port has been authorized forcefully using the dot1x port-controlforced-authorized command.No action is required.DOT1-1009MessageMessage TypeSeverityProbable CauseRecommendedAction802.1X is disabled for port .DCEINFOIndicates that 802.1X is disabled on the specified port.No action is required.Network OS Message Reference 11753-1002807-01

7DOT1-1010DOT1-1010MessageMessage TypeSeverityProbable CauseRecommendedActionPort is set in auto mode.DCEINFOIndicates that the specified port is set to auto mode.No action is required.DOT1-1011MessageMessage TypeSeverityProbable CauseRecommendedActionDOT1X_PORT_EAPOL_CAPABLE: Peer with MAC ..connected to port is EAPOL Capable.DCEINFOIndicates that the peer connected to the specified port is DOT1X-capable.No action is required.DOT1-1012MessageMessage TypeSeverityProbable CauseRecommendedActionDOT1X_PORT_EAPOL_CAPABLE: Peer connected to port is NOT EAPOL capable.DCEINFOIndicates that the peer connected to the specified port is not DOT1X-capable.No action is required.DOT1-1013MessageMessage TypeSeverityProbable CauseDOT1X test timeout value is set to .DCEINFOIndicates that the DOT1X test timeout value has been changed to the specified value.118 Network OS Message Reference53-1002807-01

DOT1-1013 7RecommendedActionNo action is required.Network OS Message Reference 11953-1002807-01

7EANV-1001EANV MessagesEANV-1001MessageMessage TypeSeverityProbable CauseRecommendedActionPort port fault. Change the SFP transceiver or check the cable.LOGERRORIndicates a deteriorated small form-factor pluggable (SFP) transceiver, an incompatible SFP transceiverpair, or a faulty cable between the peer ports.Verify that compatible SFP transceivers are used on the peer ports, the SFP transceivers have notdeteriorated, and the Fibre Channel cable is not faulty. Replace the SFP transceivers or the cable ifnecessary.EANV-1002MessageMessage TypeSeverityProbable CauseRecommendedActionPort chip faulted due to an internal error.LOG | FFDCERRORIndicates an internal error. All the ports on this chip will be disabled.Reload the system at the next maintenance window.EANV-1003MessageMessage TypeSeverityProbable CauseRecommendedActionC: HW ASIC Chip error. Type = 0x, Error = .LOGCRITICALIndicates an internal error in the application-specific integrated circuit (ASIC) hardware that may degradethe data traffic.Reload the system at the next maintenance window.120 Network OS Message Reference53-1002807-01

EANV-1004 7EANV-1004MessageMessage TypeSeverityProbable CauseRecommendedActionC: Invalid DMA ch pointer, chan:, good_addr:0x bad_addr:0x.LOGERRORIndicates an internal error in the application-specific integrated circuit (ASIC) hardware that may degradethe data traffic.No action is required. The software will recover from the error.EANV-1005MessageMessage TypeSeverityProbable CauseRecommendedActionC,A: Memory allocation failed.LOGERRORIndicates memory allocation failure in the software.Reload the system at the next maintenance window. If the problem persists, replace the switch or contactyour switch service provider.EANV-1006MessageMessage TypeSeverityProbable CauseRecommendedActionC: HW ASIC Chip fault. Type = 0x, Error = .LOGCRITICALIndicates an internal error in the application-specific integrated circuit (ASIC) hardware that renders thechip not operational.Reload the system at the next maintenance window. If the problem persists, replace the switch or contactyour switch service provider.Network OS Message Reference 12153-1002807-01

7ELD-1001ELD MessagesELD-1001MessageMessage TypeSeverityProbable CauseRecommendedActionInterface is shut down by edge loop detection (ELD) for loop inVLAN .DCEINFOIndicates that a loop has been detected by the edge loop detection (ELD) protocol on the specifiedinterface. The interface has been shut down.Identify and fix the Layer 2 bridging loop and then re-enable the interface using the clearedge-loop-detection command.ELD-1002MessageMessage TypeSeverityProbable CauseRecommendedActionInterface is auto-enabled by edge loop detection (ELD).DCEINFOIndicates that the interface on which a loop was detected has been auto-enabled based on theconfigured shutdown time.No action is required.122 Network OS Message Reference53-1002807-01

EM-1001 7EM MessagesEM-1001MessageMessage TypeSeverityProbable CauseRecommendedAction is overheating: Shutting down.FFDC | LOGCRITICALIndicates that a field replaceable unit (FRU) is shutting down due to overheating. Overheating is mainlydue to a faulty fan and can also be caused by the switch environment.Verify that the location temperature is within the operational range of the switch.Execute the show environment fan command to verify that all fans are running at normal speeds.Replace fans that are missing or not performing at high enough speeds.EM-1002MessageMessage TypeSeverityProbable CauseRecommendedActionSystem fan(s) status .LOG | FFDCINFOIndicates that a compact system has overheated and may shut down. All the fan speeds are dumped tothe console.Verify that the location temperature is within the operational range of the switch.Execute the show environment fan command to verify that all fans are running at normal speeds.Replace fans that are missing or not performing at high enough speeds.EM-1003MessageMessage TypeSeverityProbable CauseRecommendedAction has unknown hardware identifier: FRU faulted.FFDC | LOGCRITICALIndicates that a field-replaceable unit (FRU) header cannot be read or is invalid. The FRU is faulted.Reload or power cycle the switch.Execute the diag systemverification command to verify that the switch does not have hardwareproblems.Network OS Message Reference 12353-1002807-01

7EM-1004EM-1004MessageMessage TypeSeverityProbable CauseRecommendedAction failed to power on.FFDC | LOGCRITICALIndicates that the specified field-replaceable unit (FRU) failed to power on and is not being used. TheFRU ID value is composed of a FRU type string and an optional number to identify the unit, slot, or port.Reseat the FRU. If the problem persists, replace the FRU.EM-1005MessageMessage TypeSeverityProbable CauseRecommendedAction has faulted. Sensor(s) above maximum limits.FFDC | LOGCRITICALIndicates that an interface module in the specified slot or the switch (for compact switches) is being shutdown for environmental reasons; its temperature or voltage is out of range.Check the environment and make sure the room temperature is within the operational range of theswitch. Execute the show environment fan command to verify fans are operating properly. Make surethere are no blockages of the airflow around the chassis. If the temperature problem is isolated to theinterface module itself, replace the interface module.Voltage problems on a interface module are likely a hardware problem on the interface module itself;replace the interface module.EM-1006MessageMessage TypeSeverityProbable CauseRecommendedAction has faulted. Sensor(s) below minimum limits.FFDC | LOGCRITICALIndicates that the sensors show the voltage is below minimum limits. The switch or specified interfacemodule is being shut down for environmental reasons; the voltage is too low.If this problem occurs on an interface module, it usually indicates a hardware problem on the interfacemodule; replace the interface module.If this problem occurs on a switch, it usually indicates a hardware problem on the main board; replace theswitch.124 Network OS Message Reference53-1002807-01

EM-1008 7EM-1008MessageMessage TypeSeverityProbable CauseRecommendedActionUnit in with ID is faulted, it is incompatiblewith the configuration, check firmware version as apossible cause.FFDC | LOGCRITICALIndicates that an interface module inserted in the specified slot or the switch (for compact switches) is notcompatible with the platform configuration (includes the firmware version). The interface module isfaulted.If the interface module is not compatible, upgrade the firmware or replace the interface module and makesure the replacement interface module is compatible with your management module type and firmware.EM-1009MessageMessage TypeSeverityProbable CauseRecommendedAction powered down unexpectedly.FFDC | LOGCRITICALIndicates that the environmental monitor (EM) received an unexpected power-down notification from thespecified field-replaceable unit (FRU). This may indicate a hardware malfunction in the FRU.Reseat the FRU. If the problem persists, replace the FRU.EM-1010MessageMessage TypeSeverityProbable CauseRecommendedActionReceived unexpected power down for but still has power.FFDC | LOGCRITICALIndicates that the environmental monitor (EM) received an unexpected power-down notification from thespecified field-replaceable unit (FRU). However, the specified FRU still appears to be powered up after 4seconds.Reseat the interface module. If the problem persists, replace the interface module.Network OS Message Reference 12553-1002807-01

7EM-1011EM-1011MessageMessage TypeSeverityProbable CauseRecommendedActionReceived unexpected power down for , but cannot determine if it has power.FFDC | LOGCRITICALIndicates that the environmental monitor (EM) received an unexpected power-down notification from thespecified field-replaceable unit (FRU). However, after 4 seconds it could not be determined if it haspowered down or not.Reseat the interface module. If the problem persists, replace the interface module.EM-1012MessageMessage TypeSeverityProbable CauseRecommendedAction failed state transition, unit faulted.FFDC | LOGCRITICALIndicates that a switch interface module or compact switch failed to transition from one state to another. Itis faulted. The specific failed target state is displayed in the message. There are serious internal NetworkOS configuration or hardware problems on the switch.Reload or power cycle the switch.Execute the diag systemverification command to verify that the switch does not have hardwareproblems.If the problem persists, replace the FRU.EM-1013MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to update FRU information for .LOGERRORIndicates that the environmental monitor (EM) was unable to update the time alive or original equipmentmanufacturer (OEM) data in the memory of an field-replaceable unit (FRU).The update is automatically attempted again. If it continues to fail, reseat the FRU.If the problem persists, replace the FRU.126 Network OS Message Reference53-1002807-01

EM-1014 7EM-1014MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to read sensor on ().LOGERRORIndicates that the environmental monitor (EM) was unable to access the sensors on the specifiedfield-replaceable unit (FRU).Reseat the FRU. If the problem persists, replace the FRU.EM-1015MessageMessage TypeSeverityProbable CauseRecommendedActionWarm recovery failed ().LOGWARNINGIndicates that a problem was discovered when performing consistency checks during a warm boot.Monitor the switch. If the problem persists, reload or power cycle the switch.EM-1016MessageMessage TypeSeverityProbable CauseRecommendedActionCold recovery failed ().LOGWARNINGIndicates that a problem was discovered when performing consistency checks during a cold boot.Monitor the switch. If the message persists, execute the copy support command and contact yourswitch service provider.Network OS Message Reference 12753-1002807-01

7EM-1020EM-1020MessageMessage TypeSeverityProbable CauseRecommendedActionA problem was found on one or both CID cards (), run the CIDrecov tool to get more information and recovery options.LOGERRORIndicates that a problem was found either accessing one (or both) of the CID cards or with the content ofthe data stored there. The content problem could be a corrupted data set or a mismatch between the twoCID cards.Execute the CIDrecov command to get details of the problems found and how to recover.EM-1021MessageMessage TypeSeverityProbable CauseRecommendedActionA CID card has been inserted, a CID verification audit will be run to detect anymismatches or other problems.LOGINFOIndicates that the second CID card was enabled. Because the data may not match, the CID verificationaudit will be run.If an EM-1020 follows, execute the CIDrecov command to get details of the problems found and how torecover. If not, no action is required.EM-1022MessageMessage TypeSeverityProbable CauseRecommendedActionA CID card access problem has been encountered, please run the CIDrecov tool toget more information and recovery options.LOGWARNINGIndicates that a problem was encountered while accessing one (or both) of the 2 CID cards or with thecontent of the data stored there.Execute the CIDrecov command to get details of the problems found and how to recover.128 Network OS Message Reference53-1002807-01

EM-1023 7EM-1023MessageMessage TypeSeverityProbable CauseRecommendedActionChassis fan airflow-direction change is failed.LOGINFOIndicates failure to change the fan airflow direction.No action is required.EM-1024MessageMessage TypeSeverityProbable CauseRecommendedActionPlatform is not supported for changing the fan-airflow direction.LOGINFOIndicates that the platform is not supported for changing the configuration.No action is required.EM-1028MessageMessage TypeSeverityProbable CauseRecommendedActionHIL Error: failed to access history log for FRU: (rc=).FFDC | LOGWARNINGIndicates a problem accessing the data on the Chassis ID (CID) card field-replaceable unit (FRU) or theWorld Wide Name (WWN) card storage area on the main logic board.The problems were encountered when the software attempted to write to the history log storage to recordan event for the specified FRU. This error can indicate a significant hardware problem.The FRU ID value is composed of a FRU type string and an optional number to identify the unit, slot, orport. The return code is for internal use only.If the problem persists, reload or power cycle the switch.If the problem still persists, perform one of the following actions:• For compact switches, replace the switch.• For CID cards, run the CIDrecov tool to get more information.Network OS Message Reference 12953-1002807-01

7EM-1029EM-1029MessageMessage TypeSeverityProbable CauseRecommendedAction, a problem occurred accessing a device on the I2C bus ().Operational status () not changed,access is being retried.LOGWARNINGIndicates that the inter-integrated circuit (I2C) bus had problems and a timeout occurred.This is often a transient error.Watch for the EM-1048 message, which indicates that the problem has been resolved.If the error persists, check for loose or dirty connections. Remove all dust and debris prior to reseatingthe field-replaceable unit (FRU). Replace the FRU if it continues to fail.EM-1031MessageMessage TypeSeverityProbable CauseRecommendedAction ejector not closed.LOGERRORIndicates that the environmental monitor (EM) has found a switch interface module that is inserted, butthe optical ejector switch is not latched. The interface module in the specified slot is treated as notinserted.Close the ejector switch (completely screw in the optical (middle) thumbscrew on the switch fabricmodule (SFM)) if the field-replaceable unit (FRU) is intended for use. Refer to the appropriate HardwareReference Manual for instructions on inserting the switch interface modules.EM-1032MessageMessage TypeSeverityProbable CauseRecommendedAction is faulted due to a PCI scan failure.LOG | FFDCERRORIndicates that the blade in the specified slot has been marked as faulty because the PCI scan duringblade validation failed.Power cycle or reseat the blade.Execute the diag systemverification command to verify that the switch does not have hardwareproblems.If the problem persists, replace the blade.130 Network OS Message Reference53-1002807-01

EM-1033 7EM-1033MessageMessage TypeSeverityProbable CauseRecommendedActionMM in set to faulty because MM ERROR asserted.LOGERRORIndicates that the standby management module has been detected as faulty. The high availability (HA)feature will not be available. This message occurs every time the other management module reloads,even as part of a clean warm failover. In most situations, this message is followed by the EM-1047message, and no action is required for the management module; however, find the reason for failover.If the standby management module was just reloaded, wait for the error to clear (execute the show slotscommand to determine if the errors are cleared). Watch for the EM-1047 message to verify that this errorhas cleared.If the standby management module continues to be faulty or if it was not intentionally reloaded, check theerror logs on the other management module (using the show logging raslog command) to determinethe cause of the error state.Reseat the field-replaceable unit (FRU). If the problem persists, replace the FRU.EM-1034MessageMessage TypeSeverityProbable CauseRecommendedAction is set to faulty, rc=.LOGERRORIndicates that the specified field-replaceable unit (FRU) has been marked as faulty for the specifiedreason.Reseat the FRU.Execute the diag systemverification command to verify that the switch does not have hardwareproblems.If the problem persists, replace the FRU.EM-1036MessageMessage TypeSeverityProbable Cause is not accessible.LOGWARNINGIndicates that the specified field-replaceable unit (FRU) is not present on the switch.If the FRU is a Chassis ID (CID) card, then the default WWN and IP addresses are used for the switch.Network OS Message Reference 13153-1002807-01

7EM-1037RecommendedActionReseat the FRU card.If the problem persists, reload or power cycle the switch.Execute the diag systemverification command to verify that the switch does not have hardwareproblems.If the problem still persists, replace the FRU.EM-1037MessageMessage TypeSeverityProbable CauseRecommendedAction is no longer faulted.LOGINFOIndicates that the specified power supply is no longer marked faulty; probably because its AC powersupply has been turned on.No action is required.EM-1042MessageMessage TypeSeverityProbable CauseRecommendedActionImportant FRU header data for is invalid.LOGWARNINGIndicates that the specified field-replaceable unit (FRU) has an incorrect number of sensors in its FRUheader-derived information. This could mean that the FRU header was corrupted or read incorrectly, or itis corrupted in the object database, which contains information about all the FRUs.Reseat the FRU. If the problem persists, replace the FRU.EM-1043MessageMessage TypeSeverityProbable CauseRecommendedActionCannot power .LOGWARNINGIndicates that the specified field-replaceable unit (FRU) could not be powered on or off. The FRU is notresponding to commands.Reseat or replace the FRU.132 Network OS Message Reference53-1002807-01

EM-1045 7EM-1045MessageMessage TypeSeverityProbable CauseRecommendedAction is being powered .LOGWARNINGIndicates that an automatic power adjustment is being made because of the (predicted) failure of a powersupply or the insertion or removal of a port interface module.The new state can be one of the following:• On - A port interface module is being powered on because more power is available (either a powersupply was inserted or a port interface module was removed or powered down).• Off - A port interface module has been powered down because of a (predicted) failure of the powersupply.• Down - A newly inserted port interface module was not powered on because there was not enoughpower available.Refer to the Hardware Reference Manual of your switch for the number of power supplies required forredundancy.EM-1046MessageMessage TypeSeverityProbable CauseRecommendedActionError status received for interface module ID for , .LOGWARNINGIndicates that the specified interface module is incompatible.If the interface module ID listed is incorrect, the field-replaceable unit (FRU) header for the interfacemodule is corrupted and the interface module must be replaced.If the error is due to platform, the interface module ID listed is not supported for that platform(management module) type. Remove the interface module from the chassis.EM-1047MessageMessage TypeSeverityProbable Cause not faulty, MM ERROR deasserted.LOGINFOIndicates that the specified management module is no longer faulted. This message usually follows theEM-1033 message. The new standby management module is in the process of reloading and has turnedoff the MM_ERR signal.Network OS Message Reference 13353-1002807-01

7EM-1048RecommendedActionNo action is required.EM-1048MessageMessage TypeSeverityProbable CauseRecommendedAction I2C access recovered: state .LOGINFOIndicates that the inter-integrated circuit (I2C) bus problems have been resolved and the specifiedfield-replaceable unit (FRU) is accessible on the I2C bus.No action is required. This message is displayed when the EM-1029 error is resolved.EM-1049MessageMessage TypeSeverityProbable CauseRecommendedActionFRU insertion detected.LOGINFOIndicates that the field-replaceable unit (FRU) of the specified type and location was inserted into thechassis.No action is required.EM-1050MessageMessage TypeSeverityProbable CauseRecommendedActionFRU removal detected.LOGINFOIndicates that the field-replaceable unit (FRU) of the specified type and location was removed from thechassis.Verify that the FRU was intended to be removed. Replace the FRU as soon as possible.134 Network OS Message Reference53-1002807-01

EM-1051 7EM-1051MessageMessage TypeSeverityProbable CauseRecommendedAction: Inconsistency detected, FRU re-initialized.LOGINFOIndicates that an inconsistent state was found in the specified field-replaceable unit (FRU). This eventoccurs when the state of the FRU was changing during a failover. The FRU is reinitialized and traffic mayhave been disrupted.No action is required.EM-1059MessageMessage TypeSeverityProbable CauseRecommendedAction with ID may not be supported on thisplatform, check firmware version as a possible cause.LOGERRORIndicates that the interface module inserted in the specified slot or the switch (for compact switches) isnot compatible with the switch configuration software. The interface module will not be completelyusable.The interface module may only be supported by a later (or earlier) version of the firmware.Change the management module firmware or replace the interface module. Make sure the replacementis compatible with your switch type and firmware.EM-1064MessageMessage TypeSeverityProbable CauseRecommendedAction is being powered off (based on user configuration) upon receiving a HWASIC ERROR, reason:.LOGCRITICALIndicates that the interface module has been powered off because a hardware application-specificintegrated circuit (ASIC) error was detected, and you have selected to power off the problem interfacemodule when such a condition occurred.Execute the copy support command and contact your switch service provider.Network OS Message Reference 13553-1002807-01

7EM-1068EM-1068MessageMessage TypeSeverityProbable CauseRecommendedActionHigh Availability Service Management subsystem failed to respond. A requiredcomponent is not operating.FFDC | LOGERRORIndicates that the high availability (HA) subsystem has not returned a response within 4 minutes ofreceiving a request from the environmental monitor (EM). This event usually indicates that somecomponent has not started properly or has terminated. The specific component that has failed may beindicated in other messages or debug data. There are serious internal Network OS configuration orhardware problems on the switch.Reload or power cycle the switch.If the message persists, execute the copy support command and contact your switch service provider.EM-1069MessageMessage TypeSeverityProbable CauseRecommendedAction is being powered off.LOGINFOIndicates that the specified interface module has been intentionally powered off.No action is required.EM-1070MessageMessage TypeSeverityProbable CauseRecommendedAction is being powered on.LOGINFOIndicates that the specified interface module has been intentionally powered on.No action is required.136 Network OS Message Reference53-1002807-01

EM-2003 7EM-2003MessageMessage TypeSeverityProbable CauseRecommendedAction has failed the POST tests. FRU is beingfaulted.LOGERRORIndicates that the specified field-replaceable unit (FRU) has failed the Power-On Self-Test (POST). Referto the /tmp/post[1/2].slot#.log file for more information on the faults. To view this log file you must belogged in at the root level. The login ID is switch name for compact systems.On modular systems, reseat the specified FRU.On compact switches, reload or power cycle the switch.If the problem persists:• Execute the diag systemverification command to verify that the switch does not have hardwareproblems.• On modular systems, replace the specified FRU; For compact switch, replace the switch.Network OS Message Reference 13753-1002807-01

7ERCP-1000ERCP MessagesERCP-1000MessageMessage TypeSeverityProbable CauseRecommendedActionMultiple ECC errors are detected and the system will reload automatically.FFDC | LOGCRITICALIndicates that error checking and correction (ECC) errors occurred due to multi-bit corruption.No action is required. The system will reload automatically to recover from the error.138 Network OS Message Reference53-1002807-01

ESS-1008 7ESS MessagesESS-1008MessageMessage TypeSeverityProbable CauseRecommendedActionFabric Name - configured (received from domain ).LOGINFOIndicates that the specified fabric name has been configured or renamed.No action is required.ESS-1009MessageMessage TypeSeverityProbable CauseRecommendedActionFabric Name Mismatch - local () remote ( - receivedfrom domain ).LOGWARNINGIndicates that the specified fabric name is not unique for this fabric.Select an appropriate fabric name and set it again from any switch in the fabric.ESS-1010MessageMessage TypeSeverityProbable CauseRecommendedActionDuplicate Fabric Name - matching with FID .LOGWARNINGIndicates that the configured fabric name is already used for another partition.Select a different fabric name and reconfigure.Network OS Message Reference 13953-1002807-01

7FABR-1001FABR MessagesFABR-1001MessageMessage TypeSeverityProbable CauseRecommendedActionport , .LOGWARNINGIndicates that the specified switch port is isolated because of a segmentation resulting from mismatchedconfiguration parameters.Based on the segmentation reason displayed in the message, look for a possible mismatch of relevantparameters in the switches at both ends of the link.FABR-1003MessageMessage TypeSeverityProbable CauseRecommendedActionport : ILS bad size , wanted .LOGWARNINGIndicates that an internal link service (ILS) information unit of invalid size has been received. Theneighbor switch has sent a payload with an invalid size.Investigate the neighbor switch for problems. Execute the show logging raslog command on theneighbor switch to view the error log for additional messages.Check for a faulty cable or deteriorated small form-factor pluggable (SFP) transceiver. Replace the cableor SFP transceiver if necessary.If the message persists, execute the copy support command and contact your switch service provider.FABR-1004MessageMessage TypeSeverityProbable Causeport: , req iu: 0x, state: 0x, resp iu: 0x, state 0x,.LOGWARNINGIndicates that the information unit (IU) response was invalid for the specified command sent. The fabricreceived an unknown response. This message is rare and usually indicates a problem with the NetworkOS kernel.140 Network OS Message Reference53-1002807-01

FABR-1005 7RecommendedActionIf this message is due to a one time event because of the incoming data, the system will discard theframe.If the message persists, execute the copy support command and contact your switch service provider.FABR-1005MessageMessage TypeSeverityProbable CauseRecommendedAction: port : status 0x () xid = 0x.LOGWARNINGIndicates that the application failed to send an async command for the specified port. The messageprovides additional details regarding the reason for the failure and the exchange ID of the command. Thiscan happen if a port is about to go down.No action is required. This message is often transitory.If the message persists, execute the copy support command and contact your switch service provider.FABR-1006MessageMessage TypeSeverityProbable CauseRecommendedActionNode free error, caller: .LOGWARNINGIndicates that the Network OS is trying to free or deallocate memory space that has already beendeallocated. This message is rare and usually indicates a problem with the Network OS.If the message persists, execute the copy support command and contact your switch service provider.FABR-1007MessageMessage TypeSeverityProbable CauseRecommendedActionIU free error, caller: .LOGWARNINGIndicates that a failure occurred when deallocating an information unit (IU). This message is rare andusually indicates a problem with the Network OS.If the message persists, execute the copy support command and contact your switch service provider.Network OS Message Reference 14153-1002807-01

7FABR-1008FABR-1008MessageMessage TypeSeverityProbable CauseRecommendedAction.LOGWARNINGIndicates that errors occurred during the request RBridge ID state; the information unit (IU) cannot beallocated or sent. If this message occurs with FABR-1005, the problem is usually transitory. Otherwise,this message is rare and usually indicates a problem with the Network OS. The error descriptions are asfollows:• FAB RDI: cannot allocate IU• FAB RDI: cannot send IUNo action is required if the message appears with the FABR-1005 message.If the message persists, execute the copy support command and contact your switch service provider.FABR-1009MessageMessage TypeSeverityProbable CauseRecommendedAction.LOGWARNINGIndicates that errors were reported during the exchange fabric parameter (EFP) state; cannot allocateRBridge IDs list due to a faulty EFP type. This message is rare and usually indicates a problem with theNetwork OS.The fabric daemon will discard the EFP. The system will recover through the EFP retrial process.If the message persists, execute the copy support command and contact your switch service provider.FABR-1010MessageMessage TypeSeverityProbable CauseRecommendedAction.LOGWARNINGIndicates that errors occurred while cleaning up the request RBridge ID (RDI). The error descriptionprovides further details. This message is rare and usually indicates a problem with the Network OS.If the message persists, execute the copy support command and contact your switch service provider.142 Network OS Message Reference53-1002807-01

FABR-1012 7FABR-1012MessageMessage TypeSeverityProbable CauseRecommendedAction: no such type, .LOGWARNINGIndicates that the fabric is not in the appropriate state for the specified process. This message is rare andusually indicates a problem with the Network OS.The fabric daemon will take proper action to recover from the error.If the message persists, execute the copy support command and contact your switch service provider.FABR-1013MessageMessage TypeSeverityProbable CauseRecommendedActionNo Memory: pid= file= line=.FFDC | LOGCRITICALIndicates that there is not enough memory in the switch for the fabric module to allocate. This message israre and usually indicates a problem with the Network OS.The system will recover by failing over to the standby management module.If the message persists, execute the copy support command and contact your switch service provider.FABR-1014MessageMessage TypeSeverityProbable CauseRecommendedActionPort Disabled: RBridge IDs overlap. Insistent RBridge ID could not be obtained. Principal is trying to assign RBridge ID .LOGERRORIndicates that the switch received an RBridge ID other than the one it requested. The port was disabledbecause the requested insistent RBridge ID could not be obtained.Change the RBridge ID of the local node (if applicable) using the vcs rbridge-id command. You cantoggle the disabled port using the fabric isl enable and no fabric isl enable commands after theRBridge ID change.Network OS Message Reference 14353-1002807-01

7FABR-1019FABR-1019MessageMessage TypeSeverityProbable CauseRecommendedActionCritical fabric size () exceeds supported configuration().FFDC | LOGCRITICALIndicates that this switch is a value-line switch and has exceeded the configured fabric size: that is, aspecified limit to the number of RBridges. This limit is defined by your specific value-line license key. Thefabric size has exceeded this specified limit and the grace period counter has started.Bring the fabric size within the licensed limits. Either a full fabric license must be added or the size of thefabric must be changed to within the licensed limit. Contact your switch provider to obtain a full fabriclicense.FABR-1029MessageMessage TypeSeverityProbable CauseRecommendedActionPort negotiated (mode = ).LOGINFOIndicates that a different flow control mode, as described in the message, is negotiated with the port atthe other end of the link. The flow control is a mechanism of throttling the transmitter port to avoid bufferoverrun at the receiving port. There are three types of flow control modes:• VC_RDY mode: Virtual-channel flow control mode. This is a proprietary protocol.• R_RDY mode: Receiver-ready flow control mode. This is the Fibre Channel standard protocol, thatuses R_RDY primitive for flow control.• DUAL_CR mode: Dual-credit flow control mode. In both of the previous modes, the buffer credits arefixed, based on the port configuration information. In this mode, the buffer credits are negotiated aspart of exchange link parameter (ELP) exchange. This mode also uses R_RDY primitive for flowcontrol.No action is required.FABR-1030MessageMessage TypeSeverityProbable Causefabric: RBridge ID (was ).LOGINFOIndicates that the RBridge ID has changed.144 Network OS Message Reference53-1002807-01

FABR-1039 7RecommendedActionNo action is required.FABR-1039MessageMessage TypeSeverityProbable CauseRecommendedActionInvalid RBridge ID zero received from principal switch (RBridge ID = ).LOGWARNINGIndicates that an invalid RBridge ID zero has been received.Check the reason for the principal switch to assign an invalid RBridge ID zero.FABR-1041MessageMessage TypeSeverityProbable CauseRecommendedActionPort is disabled due to trunk protocol error.LOGERRORIndicates that a link reset was received before the completion of the trunking protocol on the port.Toggle the port using the no fabric isl enable and fabric isl enable commands.The port may recover by re-initialization of the link.If the message persists, execute the copy support command and contact your switch service provider.FABR-1055MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch will be taken offline and back online for RBridge Id autoconfiguration to take effect.LOGWARNINGIndicates that the specified switch has been bounced for the RBridge ID auto configuration to take effecton the unconfigured VCS switch.No action is required.Network OS Message Reference 14553-1002807-01

7FABS-1001FABS MessagesFABS-1001MessageMessage TypeSeverityProbable CauseRecommendedAction .FFDC | LOGCRITICALIndicates that the system is low on memory and cannot allocate more memory for new operations. This isusually an internal Network OS problem or file corruption. The Description of memory need variablespecifies the memory size that was being requested. The value could be any whole number.Reload or power cycle the switch.FABS-1002MessageMessage TypeSeverityProbable CauseRecommendedAction .LOGWARNINGIndicates that an internal problem has been detected by the software. This is usually an internal NetworkOS problem or file corruption.Reload or power cycle the switch.If the message persists, execute the firmware download command to update the firmware.FABS-1004MessageMessage TypeSeverityProbable CauseRecommendedAction process () .LOGWARNINGIndicates that an operation has been interrupted by a signal. This is usually an internal Network OSproblem or file corruption.Reload or power cycle the switch.146 Network OS Message Reference53-1002807-01

FABS-1005 7FABS-1005MessageMessage TypeSeverityProbable CauseRecommendedAction (= ).LOGWARNINGIndicates that an unsupported operation has been requested. This is usually an internal Network OSproblem or file corruption. The following is the possible value for the function name and description ofproblem variable:fabsys_write: Unsupported write operation: process xxxwhere xxx is the process ID (PID), which could be any whole number.Reload or power cycle the active management module (for modular systems) or the switch (for compactsystems).If the message persists, execute the firmware download command to update the firmware.FABS-1006MessageMessage TypeSeverityProbable CauseRecommendedAction: object unit .LOGWARNINGIndicates that there is no device in the slot with the specified object type ID in the system module record.This could indicate a serious Network OS data problem on the switch. The following are the possiblevalues for function name and description of problem variable:• setSoftState: bad object• setSoftState: invalid type or unit• media_sync: Media oid mapping failed• fabsys_media_i2c_op: Media oid mapping failed• fabsys_media_i2c_op: obj is not media type• media_class_hndlr: failed sending media state to blade driverIf the message is isolated, monitor the error messages on the switch. If the error is repetitive or if thefabric failed, fail over or reload the switch.If the message persists, execute the firmware download command to update the firmware.Network OS Message Reference 14753-1002807-01

7FABS-1007FABS-1007MessageMessage TypeSeverityProbable CauseRecommendedAction: Media state is invalid - status=.LOGWARNINGIndicates that the Network OS has detected an invalid value in an object status field. This is usually aninternal Network OS problem or file corruption.Reload or power cycle the switch.If the message persists, execute the firmware download command to update the firmware.FABS-1008MessageMessage TypeSeverityProbable CauseRecommendedAction: Media OID mapping failed.LOGWARNINGIndicates that the Network OS was unable to locate a necessary object handle. This is usually an internalNetwork OS problem or file corruption.Reload or power cycle the switch.FABS-1009MessageMessage TypeSeverityProbable CauseRecommendedAction: type is not media.LOGWARNINGIndicates that the Network OS was unable to locate an appropriate object handle. This is usually aninternal Network OS problem or file corruption.Reload or power cycle the switch.148 Network OS Message Reference53-1002807-01

FABS-1010 7FABS-1010MessageMessage TypeSeverityProbable CauseRecommendedAction: Wrong media_event .LOGWARNINGIndicates that the Network OS detected an unknown event type. This is usually an internal Network OSproblem or file corruption.Reload or power cycle the switch.If the message persists, execute the firmware download command to update the firmware.FABS-1011MessageMessage TypeSeverityProbable CauseRecommendedAction[]:Invalid input state 0x.LOGERRORIndicates that an unrecognized state code was used in an internal Network OS message for afield-replaceable unit (FRU).Reload or power cycle the management module or switch.If the message persists, execute the firmware download command to update the firmware.FABS-1013MessageMessage TypeSeverityProbable CauseRecommendedAction[]:Unknown interface module type 0x.LOGERRORIndicates that an unrecognized type of interface module has been discovered in the system.This error can be caused by one of the following reasons: an incorrect field-replaceable unit (FRU)header, inability to read the FRU header, or the interface module may not be supported by this platformor Network OS version.Verify that the interface module is valid for use in this system and this version of Network OS.Reseat the interface module.If this is a valid interface module and reseating does not solve the problem, replace the interface module.Network OS Message Reference 14953-1002807-01

7FABS-1014FABS-1014MessageMessage TypeSeverityProbable CauseRecommendedAction[]:Unknown FRU type 0x.LOGERRORIndicates that an unrecognized type of field-replaceable unit (FRU) has been discovered in the system.This error can be caused by one of the following reasons: an incorrect FRU header, inability to read theFRU header, or the FRU may not be supported by this platform or Network OS version.Verify that the FRU is valid for use in this system and this version of Network OS.Reseat the FRU.If this is a valid FRU and reseating does not solve the problem, replace the FRU.FABS-1015MessageMessage TypeSeverityProbable CauseRecommendedAction[]:Request to enable FRU type 0x,unit failed. err code .LOGERRORIndicates that the specified field-replaceable unit (FRU) could not be enabled. This is usually an internalNetwork OS problem.Remove and reinsert the FRU.Reload or power cycle the management module or switch.If the message persists, execute the firmware download command to update the firmware.150 Network OS Message Reference53-1002807-01

FCMC-1001 7FCMC MessagesFCMC-1001MessageMessage TypeSeverityProbable CauseRecommendedActionSystem is low on memory and has failed to allocate new memory.FFDC | LOGCRITICALIndicates that the switch is low on memory and therefore failed to allocate new memory for an informationunit (IU).A compact switch will automatically reload.For a modular switch, the active management module will automatically fail over and the standbymanagement module become the active management module.Network OS Message Reference 15153-1002807-01

7FCOE-1001FCOE MessagesFCOE-1001MessageMessage TypeSeverityProbable CauseRecommendedActioncalloc failed for .DCEERRORIndicates a memory failure.Check the switch memory status using the show process memory command.FCOE-1010MessageMessage TypeSeverityProbable CauseRecommendedActionClean up of login failed for port:.DCEERRORIndicates an invalid port number.Execute the copy support command and restart the system. Contact your switch service provider.FCOE-1019MessageMessage TypeSeverityProbable CauseRecommendedActionFLOGI ignored as FCMAP not configured on FCoE VLAN.DCEWARNINGIndicates that FCMAP is not configured on the Fibre Channel over Ethernet (FCoE) VLAN.Configure FCMAP using the fcmap command.152 Network OS Message Reference53-1002807-01

FCOE-1020 7FCOE-1020MessageMessage TypeSeverityProbable CauseRecommendedActionLogin rejected by FC stack.DCEINFOIndicates that the login was rejected by the Fibre Channel (FC) stack.No action is required. The device will try to login again.FCOE-1022MessageMessage TypeSeverityProbable CauseRecommendedActionMax FCoE device login limit reached.DCEWARNINGIndicates that the switch has reached its maximum allowed Fibre Channel over Ethernet (FCoE) devicelimit.Do not add any more FCoE devices to the switch.FCOE-1023MessageMessage TypeSeverityProbable CauseRecommendedActionToo many logins on FCoE controller, max allowed = .DCEWARNINGIndicates that the controller has reached its maximum allowed Fibre Channel over Ethernet (FCoE) loginlimit.Log out some of the logged-in devices using one of the following commands: no fcoeport default,shutdown, and clear fcoe login, and then log in the new device.You can view the list of logged-in devices using the show fcoe login command.Network OS Message Reference 15353-1002807-01

7FCOE-1024FCOE-1024MessageMessage TypeSeverityProbable CauseRecommendedActionFDISC received from Enode without prior FLOGI.DCEWARNINGIndicates that a fabric discovery (FDISC) frame is received from the end node that has not logged in. Theend node must send a fabric login (FLOGI) before it can send an FDISC.No action is required.FCOE-1029MessageMessage TypeSeverityProbable CauseRecommendedActionVersion mismatch between FIP FDISC and root VN port.DCEWARNINGIndicates that the FCoE initialization protocol (FIP) version does not match between the fabric login(FLOGI) and fabric discovery (FDISC) frames.Make sure that the device that is trying to log in conforms to the FC-BB-5 standard.FCOE-1030MessageMessage TypeSeverityProbable CauseRecommendedActionVersion mismatch between FIP LOGO and root VN port.DCEWARNINGIndicates that the switch received an FCoE initialization protocol (FIP) logout (LOGO) request but thedevice logged in with a different FIP version.Make sure that the device that is trying to log in conforms to the FC-BB-5 standard.154 Network OS Message Reference53-1002807-01

FCOE-1032 7FCOE-1032MessageMessage TypeSeverityProbable CauseRecommendedActionThe chassis is in WARM RECOVERING state.DCEINFOIndicates that the chassis is in a warm recovering state and therefore cannot perform theprotocol-specific actions for the time being.Wait until the chassis has fully recovered before you perform any operations.FCOE-1034MessageMessage TypeSeverityProbable CauseRecommendedActionFIP/FCoE frame on priority pri_in> for on interface //discarded because PFC/FCoE not enabled on this priority.DCEWARNINGIndicates that the specified priority is not priority-based flow control (PFC) or Fibre Channel over Ethernet(FCoE) enabled.Change the CEE map assigned to the FCoE map to accommodate the PFC for the specified FCoEpriority or change the FCoE priority using the fabric-map default command under the FCoEconfiguration mode.FCOE-1035MessageMessage TypeSeverityProbable CauseRecommendedActionVirtual FCoE port is online.DCEINFOIndicates an administrative action on the Fibre Channel over Ethernet (FCoE) port.No action is required.Network OS Message Reference 15553-1002807-01

7FCOE-1036FCOE-1036MessageMessage TypeSeverityProbable CauseRecommendedActionVirtual FCoE port is offline.DCEINFOIndicates an administrative action on the Fibre Channel over Ethernet (FCoE) port.No action is required.156 Network OS Message Reference53-1002807-01

FCPH-1001 7FCPH MessagesFCPH-1001MessageMessage TypeSeverityProbable CauseRecommendedAction: failed, out of memory condition.FFDC | LOGCRITICALIndicates that the switch is low on memory and therefore failed to allocate new memory for a FibreChannel driver instance.The function can only be fc_create. This function creates a Fibre Channel driver instance.The failed function call can only be kmalloc_wrapper, which has failed. This function call is for kernelmemory allocation.A compact switch will automatically reload.For a modular switch, the active management module will automatically fail over and the standbymanagement module become the active management module.Network OS Message Reference 15753-1002807-01

7FLOD-1001FLOD MessagesFLOD-1001MessageMessage TypeSeverityProbable CauseRecommendedActionUnknown LSR type: port , type .LOGWARNINGIndicates that the link state record (LSR) type is unknown. The following are the known LSR headertypes: 1 - Unicast and 3 - Multicast.No action is required; the record is discarded.FLOD-1003MessageMessage TypeSeverityProbable CauseRecommendedActionLink count exceeded in received LSR, value = .LOGWARNINGIndicates that the acceptable link count received was exceeded in the link state record (LSR).No action is required; the record is discarded.FLOD-1004MessageMessage TypeSeverityProbable CauseRecommendedActionExcessive LSU length = .LOG | FFDCERRORIndicates that the link state update (LSU) size exceeds the value that the system can support.Reduce the number of switches in the fabric or reduce the number of redundant inter-switch links (ISLs)between two switches.158 Network OS Message Reference53-1002807-01

FLOD-1005 7FLOD-1005MessageMessage TypeSeverityProbable CauseRecommendedActionInvalid received RBridge ID: .LOGWARNINGIndicates that the received link state record (LSR) contained an invalid RBridge number.No action is required; the LSR is discarded.FLOD-1006MessageMessage TypeSeverityProbable CauseRecommendedActionTransmitting invalid RBridge ID: .LOGWARNINGIndicates that the transmit link state record (LSR) contained an invalid RBridge number.No action is required; the LSR is discarded.Network OS Message Reference 15953-1002807-01

7FSPF-1001FSPF MessagesFSPF-1001MessageMessage TypeSeverityProbable CauseRecommendedActionInput Port out of range.LOGERRORIndicates that the specified input port number is out of range because it does not exist on the switch.No action is required. This is a temporary kernel error that does not affect your system. If the problempersists, execute copy support command and contact your service provider.FSPF-1002MessageMessage TypeSeverityProbable CauseRecommendedActionWrong neighbor ID () in Hello message from port ,expected ID = .LOGINFOIndicates that the switch has received a wrong RBridge ID in the Hello message from its neighbor switch.This may happen when the RBridge ID for a switch has been changed.No action is required.FSPF-1003MessageMessage TypeSeverityProbable CauseRecommendedActionRemote RBridge ID out of range, input port = .LOGERRORIndicates that the specified remote RBridge ID is out of range.No action is required. The frame is discarded.160 Network OS Message Reference53-1002807-01

FSPF-1005 7FSPF-1005MessageMessage TypeSeverityProbable CauseRecommendedActionWrong Section Id , should be , input port = .LOGERRORIndicates that an incorrect section ID was reported from the specified input port. The section ID is part ofthe fabric shortest path first (FSPF) protocol and is used to identify a set of switches that share anidentical topology database.This switch does not support a non-zero section ID. Any connected switch from another manufacturerwith a section ID other than 0 is incompatible in a fabric of Brocade switches. Disconnect theincompatible switch.FSPF-1006MessageMessage TypeSeverityProbable CauseRecommendedActionFSPF Version not supported, input port = .LOGERRORIndicates that the fabric shortest path first (FSPF) version is not supported on the specified input port.Update the FSPF version by running the firmware download command. All current versions of theNetwork OS supports FSPF version 2.FSPF-1007MessageMessage TypeSeverityProbable CauseRecommendedActionICL triangular topology is broken between the neighboring RBridges: and . Please fix it ASAP.LOGERRORIndicates that the inter-chassis link (ICL) triangular topology is broken and becomes linear. It may causeframe drop or performance slowdown.Investigate the ICLs and reconnect the switches to form a triangular topology.Network OS Message Reference 16153-1002807-01

7FSPF-1008FSPF-1008MessageMessage TypeSeverityProbable CauseRecommendedActionICL triangular topology is formed among the RBridges: (self),, and .LOGINFOIndicates that the inter-chassis link (ICL) triangular topology is formed.No action is required.162 Network OS Message Reference53-1002807-01

FSS-1001 7FSS MessagesFSS-1001MessageMessage TypeSeverityProbable CauseRecommendedActionComponent () dropping HA data update ().LOGWARNINGIndicates that an application has dropped a high availability (HA) data update.Execute the copy support command and contact your switch service provider.FSS-1002MessageMessage TypeSeverityProbable CauseRecommendedActionComponent () sending too many concurrent HA data updatetransactions ().LOGWARNINGIndicates that an application has sent too many concurrent high availability (HA) data updates.Execute the copy support command and contact your switch service provider.FSS-1003MessageMessage TypeSeverityProbable CauseRecommendedActionComponent () misused the update transaction ()without marking the transaction begining.LOGWARNINGIndicates that the fabric synchronization service (FSS) has dropped the update because an applicationhas not set the transaction flag correctly.Execute the copy support command and contact your switch service provider.Network OS Message Reference 16353-1002807-01

7FSS-1004FSS-1004MessageMessage TypeSeverityProbable CauseRecommendedActionMemory shortage.LOGERRORIndicates that the system ran out of memory.Check memory usage on the switch using the show process memory command.Execute the copy support command and contact your switch service provider.FSS-1005MessageMessage TypeSeverityProbable CauseRecommendedActionFSS read failure.LOGWARNINGIndicates that the read system call to the fabric synchronization service (FSS) device has failed.If the message persists, execute the copy support command and contact your switch service provider.FSS-1006MessageMessage TypeSeverityProbable CauseRecommendedActionNo FSS message available.LOGWARNINGIndicates that data is not available on the fabric synchronization service (FSS) device.If the message persists, execute the copy support command and contact your switch service provider.164 Network OS Message Reference53-1002807-01

FSS-1007 7FSS-1007MessageMessage TypeSeverityProbable CauseRecommendedAction: Faulty Ethernet connection.LOGCRITICALIndicates that the Ethernet connection between the active and standby management modules is nothealthy. The error occurs when the standby management module does not respond to a request from theactive management module within 5 seconds. This usually indicates a problem with the internal Ethernetconnection and a disruption of the synchronization process.Execute the copy support command and contact your switch service provider.FSS-1008MessageMessage TypeSeverityProbable CauseRecommendedActionFSS Error on service component []: .LOGCRITICALIndicates that a fabric synchronization service (FSS) error has occurred.Execute the copy support command and contact your switch service provider.FSS-1009MessageMessage TypeSeverityProbable CauseRecommendedActionFSS Error on service instance []: .LOGERRORIndicates that a fabric synchronization service (FSS) error has occurred.Execute the copy support command and contact your switch service provider.Network OS Message Reference 16553-1002807-01

7FSS-1010FSS-1010MessageMessage TypeSeverityProbable CauseRecommendedActionFSS Warning: .LOGWARNINGIndicates that a fabric synchronization service (FSS) error may have occurred.No action is required.FSS-1011MessageMessage TypeSeverityProbable CauseRecommendedActionFSS Info: .LOGINFOIndicates a fabric synchronization service (FSS) related informational message.No action is required.166 Network OS Message Reference53-1002807-01

FVCS-1003 7FVCS MessagesFVCS-1003MessageMessage TypeSeverityProbable CauseRecommendedActionPossible vLAG Split Detected vLAG - ifindex (), split RBridge().LOGWARNINGIndicates that the RBridge has left the cluster.If the RBridge was not disabled on purpose, check if it is still connected to the cluster using the showfabric isl command.FVCS-2001MessageMessage TypeSeverityProbable CauseRecommendedActionFCS Primary Update Send attempt Failed - reason ().LOGWARNINGIndicates that the remote switch has rejected the update. Refer to the failure reason for more details.Execute the show fabric isl command to check the cluster connection status.If the message persists, execute the copy support command and contact your switch service provider.FVCS-2002MessageMessage TypeSeverityProbable CauseRecommendedActionLink State Update sent to Remote RBridge Failed - reason ().LOGWARNINGIndicates a possible cluster infrastructure problem.Execute the show fabric isl command to check the cluster connection status.If the message persists, execute the copy support command and contact your switch service provider.Network OS Message Reference 16753-1002807-01

7FVCS-2003FVCS-2003MessageMessage TypeSeverityProbable CauseRecommendedActionLag Configureation Update sent to Remote RBridge Failed - reason ().LOGWARNINGIndicates a possible cluster infrastructure problem.Execute the show fabric isl command to check the cluster connection status.If the message persists, execute the copy support command and contact your switch service provider.FVCS-2004MessageMessage TypeSeverityProbable CauseRecommendedActionFCS Commit stage Failed - cfg type , cfg tag , domain , reason ().LOGWARNINGIndicates that the fabric configuration server (FCS) commit stage has failed. The failure reason can beone of the following:• 7 - Memory allocation error• 14 - Reliable Transport Write and Read (RTWR) send failureCheck the status of the virtual link aggregation group (vLAG) identified by the configuration tag.If the message persists, execute the copy support command on both this RBridge and the remoteRBridge specified by the domain field and contact your switch service provider.FVCS-2005MessageMessage TypeSeverityProbable CauseRecommendedActionFCS Cancel stage Failed - cfg type , cfg tag , domain , reason ().LOGWARNINGIndicates that the fabric configuration server (FCS) cancel stage has failed. The failure reason can beone of the following:• 7 - Memory allocation error• 14 - Reliable Transport Write and Read (RTWR) send failureCheck the status of the virtual link aggregation group (vLAG) identified by the configuration tag.If the message persists, execute the copy support command on both this RBridge and the remoteRBridge specified by the domain field and contact your switch service provider.168 Network OS Message Reference53-1002807-01

FVCS-2006 7FVCS-2006MessageMessage TypeSeverityProbable CauseRecommendedActionFCS Transaction Hung - cfg type , cfg tag ,trans state.LOGWARNINGIndicates that the update cannot be completed for an unknown reason.Check the status of the virtual link aggregation group (vLAG) identified by the configuration tag.If the message persists, execute the copy support command and contact your switch service provider.FVCS-3001MessageMessage TypeSeverityProbable CauseRecommendedActionEth_ns Message Queue Overflow. Failed to send Update. MAC or MCAST database may beout of sync. Drop count = ().LOGWARNINGIndicates that the Eth_ns (component of FVCS) that kept the MCAST and L2 databases in sync, cannotsend an update to the remote RBridges because its internal message queue is full. This error is due to atemporary congestion issue on the local RBridge.The RBridge must leave and rejoin the fabric for synchronization of the MCAST and L2 databases.FVCS-3002MessageMessage TypeSeverityProbable CauseRecommendedActionEth_ns Message Queue Overflow. Failed to add recieved Update. MAC or MCASTdatabase may be out of sync. Drop count = ().LOGWARNINGIndicates that the Eth_ns (component of FVCS) that kept the MCAST and L2 databases in sync, cannotprocess an update received from the remote RBridge because its internal message queue is full. Thiserror is due to a temporary congestion issue on the local RBridge.No action is required. The L2 and MCAST databases will synchronize with the fabric after the localcongestion issue is resolved.Network OS Message Reference 16953-1002807-01

7FVCS-3003FVCS-3003MessageMessage TypeSeverityProbable CauseRecommendedActionLocal VRID config attempt failed. Existing VLAN_ID mismatch. VRID , VRB_ID, New VLAN_ID , Existing VLAN_ID .LOGWARNINGIndicates virtual router ID (VRID) configuration conflict.Check existing VRID configurations.FVCS-3004MessageMessage TypeSeverityProbable CauseRecommendedActionLocal VRID config attempt failed. Existing VMAC mismatch. VRID , VRB_ID, New VMAC , Existing VMAC .LOGWARNINGIndicates virtual router ID (VRID) configuration conflict.Check existing VRID configurations.FVCS-3005MessageMessage TypeSeverityProbable CauseRecommendedActionRemote VRB_ID update failed. Existing VRID mismatch. VRB_ID , SRC_Domain New VRID , Existing VRID .LOGWARNINGIndicates virtual router ID (VRID) configuration conflict.Check existing VRID configurations.170 Network OS Message Reference53-1002807-01

FVCS-3006 7FVCS-3006MessageMessage TypeSeverityProbable CauseRecommendedActionRemote VRB_ID update failed. Existing VLAN_ID mismatch. VRB_ID ,SRC_Domain New VLAN_ID , Existing VLAN_ID .LOGWARNINGIndicates virtual router ID (VRID) configuration conflict.Check existing VRID configurations.FVCS-3007MessageMessage TypeSeverityProbable CauseRecommendedActionRemote VRB_ID update failed. Existing VMAC mismatch. VRB_ID , SRC_Domain, New VMAC , Existing VMAC .LOGWARNINGIndicates virtual router ID (VRID) configuration conflict.Check existing VRID configurations.FVCS-3008MessageMessage TypeSeverityProbable CauseRecommendedActionMAC (L2) database out of sync, Down-level domain .LOGWARNINGIndicates that the current media access control (MAC) count is not supported on the specified downleveldomain.Upgrade the firmware to Network OS v3.0.0 or later.Network OS Message Reference 17153-1002807-01

7FVCS-3009FVCS-3009MessageMessage TypeSeverityProbable CauseRecommendedActionEth_ns buffer capacity exceeded - MAC or MCAST database may be out of sync.LOGWARNINGIndicates that the current media access control (MAC) count exceeds the supported limit.Reduce the number of Ethernet devices in the fabric.172 Network OS Message Reference53-1002807-01

FW-1001 7FW MessagesFW-1001MessageMessage TypeSeverityProbable CauseRecommendedAction, value has changed(High=, Low=). Current value is .LOGINFOIndicates that the internal temperature of the switch has changed.Respond to this message as is appropriate to the particular policy of the end-user installation. To preventrecurring messages, disable the changed alarm for this threshold. If you receive a temperature-relatedmessage, check for an accompanying fan-related message and check fan performance. If all fans arefunctioning normally, check the climate control in your lab.FW-1002MessageMessage TypeSeverityProbable CauseRecommendedAction, is below low boundary (High=, Low=). Current valueis .LOGWARNINGIndicates that the internal temperature of the switch has fallen below the low boundary.Respond to this message as is appropriate to the particular policy of the end-user installation. Typically,low temperatures means that the fans and airflow of a switch are functioning normally.Verify that the location temperature is within the operational range of the switch. Refer to the HardwareReference Manual for the environmental temperature range of your switch.FW-1003MessageMessage TypeSeverityProbable CauseRecommendedAction, is above high boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the internal temperature of the switch has risen above the high boundary to a value thatmay damage the switch.This message generally appears when a fan fails. If so, a fan-failure message accompanies thismessage. Replace the fan.Network OS Message Reference 17353-1002807-01

7FW-1004FW-1004MessageMessage TypeSeverityProbable CauseRecommendedAction, is between high and low boundaries(High=, Low=).Current value is .LOGINFOIndicates that the internal temperature of the switch has changed from a value outside of the acceptablerange to a value within the acceptable range.Respond to this message as is appropriate to the particular policy of the end-user installation. If youreceive a temperature-related message, check for an accompanying fan-related message and check fanperformance. If all fans are functioning normally, check the climate control in your lab.FW-1005MessageMessage TypeSeverityProbable CauseRecommendedAction, value has changed(High=, Low=). Current value is .LOGINFOIndicates that the speed of the fan has changed. Fan problems typically contribute to temperatureproblems.No action is required. Respond to this message as is appropriate to the particular policy of the end-userinstallation. Consistently abnormal fan speeds generally indicate that the fan is malfunctioning.FW-1006MessageMessage TypeSeverityProbable CauseRecommendedAction, is below low boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the speed of the fan has fallen below the low boundary. Fan problems typically contributeto temperature problems.Consistently abnormal fan speeds generally indicate that the fan is failing. Replace the fan.174 Network OS Message Reference53-1002807-01

FW-1007 7FW-1007MessageMessage TypeSeverityProbable CauseRecommendedAction, is above high boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the speed of the fan has risen above the high boundary. Fan problems typically contributeto temperature problems.Consistently abnormal fan speeds generally indicate that the fan is failing. Replace the fan.FW-1008MessageMessage TypeSeverityProbable CauseRecommendedAction, is between high and low boundaries(High=, Low=).Current value is .LOGINFOIndicates that the speed of the fan has changed from a value outside of the acceptable range to a valuewithin the acceptable range. Fan problems typically contribute to temperature problems.No action is required. Consistently abnormal fan speeds generally indicate that the fan is failing. If thismessage occurs repeatedly, replace the fan.FW-1009MessageMessage TypeSeverityProbable CauseRecommendedAction, value has changed(High=, Low=). Current value is .LOGINFOIndicates that the state of the power supply has changed from faulty to functional or from functional tofaulty.If the power supply is functioning correctly, no action is required.If the power supply is functioning below the acceptable boundary, verify that it is seated correctly in thechassis. Execute the show environment power command to view the status of the power supply. If thepower supply continues to be a problem, replace the faulty power supply.Network OS Message Reference 17553-1002807-01

7FW-1010FW-1010MessageMessage TypeSeverityProbable CauseRecommendedAction, is below low boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the power supply is faulty. The power supply is not producing enough power.Verify that the power supply is installed correctly and that it is correctly seated in the chassis. If theproblem persists, replace the faulty power supply.FW-1012MessageMessage TypeSeverityProbable CauseRecommendedAction, is between high and low boundaries(High=, Low=).Current value is .LOGINFOIndicates that the power supply counter changed from a value outside of the acceptable range to a valuewithin the acceptable range.No action is required. Respond to this message as is appropriate to the particular policy of the end-userinstallation.FW-1034MessageMessage TypeSeverityProbable CauseRecommendedAction, is below low boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the temperature of the small form-factor pluggable (SFP) transceiver has fallen below thelow boundary.No action is required. Respond to this message as is appropriate to the particular policy of the end-userinstallation.176 Network OS Message Reference53-1002807-01

FW-1035 7FW-1035MessageMessage TypeSeverityProbable CauseRecommendedAction, is above high boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the temperature of the small form-factor pluggable (SFP) transceiver has risen above thehigh boundary.Frequent fluctuations in temperature may indicate a deteriorating SFP transceiver. Replace the SFPtransceiver.FW-1036MessageMessage TypeSeverityProbable CauseRecommendedAction, is between high and low boundaries(High=, Low=).Current value is .LOGINFOIndicates that the temperature of the small form-factor pluggable (SFP) transceiver has changed from avalue outside of the acceptable range to a value within the acceptable range.No action is required.FW-1038MessageMessage TypeSeverityProbable CauseRecommendedAction, is below low boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the receive power value of the small form-factor pluggable (SFP) transceiver has fallenbelow the low boundary. The receive performance area measures the amount of incoming laser to helpyou determine if the SFP transceiver is in good working condition or not. If the counter often exceeds thethreshold, the SFP transceiver is deteriorating.Verify that the optical components are clean and functioning properly. Replace deteriorating cables orSFP transceivers. Check for damage from heat or age.Network OS Message Reference 17753-1002807-01

7FW-1039FW-1039MessageMessage TypeSeverityProbable CauseRecommendedAction, is above high boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the receive power value of the small form-factor pluggable (SFP) transceiver has risenabove the high boundary. The receive performance area measures the amount of incoming laser to helpyou determine if the SFP transceiver is in good working condition or not. If the counter often exceeds thethreshold, the SFP transceiver is deteriorating.Replace the SFP transceiver before it deteriorates.FW-1040MessageMessage TypeSeverityProbable CauseRecommendedAction, is between high and low boundaries(High=, Low=).Current value is .LOGINFOIndicates that the receive power value of the small form-factor pluggable (SFP) transceiver has changedfrom a value outside of the acceptable range to a value within the acceptable range. The receiveperformance area measures the amount of incoming laser to help you determine if the SFP transceiver isin good working condition or not. If the counter often exceeds the threshold, the SFP transceiver isdeteriorating.No action is required. Respond to this message as is appropriate to the particular policy of the end-userinstallation.FW-1042MessageMessage TypeSeverityProbable CauseRecommendedAction, is below low boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the transmit power value of the small form-factor pluggable (SFP) transceiver has fallenbelow the low boundary. The transmit performance area measures the amount of outgoing laser to helpyou determine if the SFP transceiver is in good working condition or not. If the counter often exceeds thethreshold, the SFP transceiver is deteriorating.Verify that the optical components are clean and functioning properly. Replace deteriorating cables orSFP transceivers. Check for damage from heat or age.178 Network OS Message Reference53-1002807-01

FW-1043 7FW-1043MessageMessage TypeSeverityProbable CauseRecommendedAction, is above high boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the transmit power value of the small form-factor pluggable (SFP) transceiver has risenabove the high boundary. The transmit performance area measures the amount of outgoing laser to helpyou determine if the SFP transceiver is in good working condition or not. If the counter often exceeds thethreshold, the SFP transceiver is deteriorating.Replace the SFP transceiver.FW-1044MessageMessage TypeSeverityProbable CauseRecommendedAction, is between high and low boundaries(High=, Low=).Current value is .LOGINFOIndicates that the transmit power value of the small form-factor pluggable (SFP) transceiver has changedfrom a value outside of the acceptable range to a value within the acceptable range. The transmitperformance area measures the amount of outgoing laser to help you determine if the SFP transceiver isin good working condition or not. If the counter often exceeds the threshold, the SFP transceiver isdeteriorating.No action is required. Respond to this message as is appropriate to the particular policy of the end-userinstallation.FW-1046MessageMessage TypeSeverityProbable CauseRecommendedAction, is below low boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the value of the small form-factor pluggable (SFP) transceiver voltage has fallen below thelow boundary.Verify that your optical components are clean and functioning properly. Replace deteriorating cables orSFP transceivers. Check for damage from heat or age.Network OS Message Reference 17953-1002807-01

7FW-1047FW-1047MessageMessage TypeSeverityProbable CauseRecommendedAction, is above high boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the value of the small form-factor pluggable (SFP) transceiver voltage has risen above thehigh boundary.The supplied current of the SFP transceiver is outside of the normal range, indicating possible hardwarefailure. If the current rises above the high boundary, replace the SFP transceiver.FW-1048MessageMessage TypeSeverityProbable CauseRecommendedAction, is between high and low boundaries(High=, Low=).Current value is .LOGINFOIndicates that the value of the small form-factor pluggable (SFP) transceiver voltage has changed from avalue outside of the acceptable range to a value within the acceptable range.No action is required. Respond to this message as is appropriate to the particular policy of the end-userinstallation.FW-1050MessageMessage TypeSeverityProbable CauseRecommendedAction, is below low boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the value of the small form-factor pluggable (SFP) transceiver voltage has fallen below thelow boundary.Configure the low threshold to 1 so that the threshold triggers an alarm when the value falls to 0(Out_of_Range). If continuous or repeated alarms occur, replace the SFP transceiver before itdeteriorates.180 Network OS Message Reference53-1002807-01

FW-1051 7FW-1051MessageMessage TypeSeverityProbable CauseRecommendedAction, is above high boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the value of the small form-factor pluggable (SFP) transceiver voltage has risen above thehigh boundary. High voltages indicate possible hardware failures.Frequent voltage fluctuations are an indication that the SFP transceiver is deteriorating. Replace the SFPtransceiver.FW-1052MessageMessage TypeSeverityProbable CauseRecommendedAction, is between high and low boundaries(High=, Low=).Current value is .LOGINFOIndicates that the value of the small form-factor pluggable (SFP) transceiver voltage has changed from avalue outside of the acceptable range to a value within the acceptable range.No action is required. Respond to this message as is appropriate to the particular policy of the end-userinstallation.FW-1297MessageMessage TypeSeverityProbable CauseRecommendedAction, is below low boundary(High=, Low=). Current valueis .LOGINFOIndicates that the number of Telnet violations has fallen below the low boundary. Telnet violations indicatethat a Telnet connection request has been received from an unauthorized IP address. TheTELNET_POLICY contains a list of IP addresses that are authorized to establish Telnet connections toswitches in the fabric.No action is required.Network OS Message Reference 18153-1002807-01

7FW-1298FW-1298MessageMessage TypeSeverityProbable CauseRecommendedAction, is above high boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the number of Telnet violations has risen above the high boundary. Telnet violationsindicate that a Telnet connection request has been received from an unauthorized IP address. TheTELNET_POLICY contains a list of IP addresses that are authorized to establish Telnet connections toswitches in the fabric.Execute the show logging raslog command to determine the IP address that sent the request.Responses to security-class messages depend on user policies. Consult your security administrator forresponse strategies and policies.FW-1299MessageMessage TypeSeverityProbable CauseRecommendedAction, is between high and low boundaries(High=, Low=).Current value is .LOGINFOIndicates that the number of Telnet violations has changed from a value outside of the acceptable rangeto a value within the acceptable range. Telnet violations indicate that a Telnet connection request hasbeen received from an unauthorized IP address. The TELNET_POLICY contains a list of IP addressesthat are authorized to establish Telnet connections to switches in the fabric.No action is required.FW-1341MessageMessage TypeSeverityProbable CauseRecommendedAction, is below low boundary(High=, Low=). Current valueis .LOGINFOIndicates that the number of login violations has fallen below the low boundary. Login violations indicatethat a login failure has been detected.No action is required.182 Network OS Message Reference53-1002807-01

FW-1342 7FW-1342MessageMessage TypeSeverityProbable CauseRecommendedAction, is above high boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the number of login violations has risen above the high boundary. Login violations indicatethat a login failure has been detected.Execute the show logging raslog command to determine the IP address of the log in attempt.Responses to security-class messages depend on user policies. Consult your security administrator forresponse strategies and policies.FW-1343MessageMessage TypeSeverityProbable CauseRecommendedAction, is between high and low boundaries(High=, Low=).Current value is .LOGINFOIndicates that the number of login violations has changed from a value outside of the acceptable range toa value within the acceptable range. Login violations indicate that a login failure has been detected.No action is required.FW-1403MessageMessage TypeSeverityProbable CauseRecommendedAction,is between high and low boundaries(High=, Low=).Current value is .LOGINFOIndicates that the CPU or memory usage is between the boundary limits.No action is required.Network OS Message Reference 18353-1002807-01

7FW-1404FW-1404MessageMessage TypeSeverityProbable CauseRecommendedAction,is above high boundary(High=, Low=). Current valueis .LOGWARNINGIndicates that the CPU or memory usage is above the configured threshold. If this message pertains tomemory usage, then the usage is above middle memory threshold.No action is required.FW-1405MessageMessage TypeSeverityProbable CauseRecommendedAction,is above high boundary(High=, Low=). Current valueis .LOGINFOIndicates that the memory usage is above low threshold.No action is required.FW-1406MessageMessage TypeSeverityProbable CauseRecommendedAction,is above high boundary(High=, Low=). Current valueis .LOGCRITICALIndicates that the memory usage is above the configured high threshold for memory usage.No action is required.184 Network OS Message Reference53-1002807-01

FW-1407 7FW-1407MessageMessage TypeSeverityProbable CauseRecommendedAction, is between high and low boundaries(High=, Low=).Current value is .LOGINFOIndicates that the memory usage is between the configured high and medium thresholds for memoryusage.No action is required.FW-1408MessageMessage TypeSeverityProbable CauseRecommendedAction, is between high and low boundaries(High=, Low=).Current value is .LOGINFOIndicates that the memory usage is between the configured low and medium thresholds for memoryusage.No action is required.FW-1424MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch status changed from to .LOGWARNINGIndicates that the switch is not in a healthy state. This occurred because of a policy violation.Execute the show system monitor command to determine the policy violation.Network OS Message Reference 18553-1002807-01

7FW-1425FW-1425MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch status changed from to HEALTHY.LOGINFOIndicates that the switch status has changed to a healthy state. This state change occurred because apolicy is no longer violated.No action is required.FW-1426MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch status change contributing factor Power supply: bad, absent.LOGWARNINGIndicates that the switch is not in a healthy state. This occurred because the number of faulty or missingpower supplies is greater than or equal to the policy set by the system-monitor command.Replace the faulty or missing power supplies.FW-1427MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch status change contributing factor Power supply: bad.LOGWARNINGIndicates that the switch is not in a healthy state. This occurred because the number of faulty powersupplies is greater than or equal to the policy set by the system-monitor command.Replace the faulty power supplies.186 Network OS Message Reference53-1002807-01

FW-1428 7FW-1428MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch status change contributing factor Power supply: absent.LOGWARNINGIndicates that the switch is not in a healthy state. This occurred because the number of missing powersupplies is greater than or equal to the policy set by the system-monitor command.Replace the missing power supplies.FW-1429MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch status change contributing factor: Power supplies are not redundant.LOGWARNINGIndicates that the switch is not in a healthy state. This occurred because the power supplies are not in thecorrect slots for redundancy.Rearrange the power supplies so that one is in an odd slot and another in an even slot to make themredundant.FW-1430MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch status change contributing factor .LOGWARNINGIndicates that the switch is not in a healthy state. This occurred because the number of faultytemperature sensors is greater than or equal to the policy set by the system-monitor command. Atemperature sensor is faulty when the sensor value is not in the acceptable range.Replace the field-replaceable unit (FRU) with the faulty temperature sensor.Network OS Message Reference 18753-1002807-01

7FW-1431FW-1431MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch status change contributing factor Fan: bad.LOGWARNINGIndicates that the switch is not in a healthy state. This occurred because the number of faulty fans isgreater than or equal to the policy set by the system-monitor command. A fan is faulty when sensorvalue is not in the acceptable range.Replace the faulty or deteriorating fans.FW-1432MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch status change contributing factor Cid-Card: bad.LOGWARNINGIndicates that the switch is not in a healthy state. This occurred because the number of faulty Chassis ID(CID) cards is greater than or equal to the policy set by the system-monitor command.Replace the faulty CID card.FW-1433MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch status change contributing factor MM: MM non-redundant ()faulty.LOGWARNINGIndicates that the switch is not in a healthy state. This occurred because the number of faultymanagement modules is greater than or equal to the policy set by the system-monitor command. Themanagement modules are non-redundant.Execute the show firmware command to verify if both the management modules have compatiblefirmware levels. Execute the firmware download command to install the same level of firmware to bothmanagement modules. Replace any faulty management modules.If you reset the micro-switch (the latch on the management module) on the active management modulebefore the heartbeat was up on a power cycle, and the management modules came up non-redundant,reload the management modules again to clear the problem.188 Network OS Message Reference53-1002807-01

FW-1434 7FW-1434MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch status change contributing factor LC: LC failures ().LOGWARNINGIndicates that the switch is not in a healthy state. This occurred because the number of line card (LC)failures is greater than or equal to the policy set by the system-monitor command.Replace the faulty LC.FW-1435MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch status change contributing factor Flash: usage out of range.LOGWARNINGIndicates that the switch is not in a healthy state. This occurred because the flash usage is out of range.The policy was set using the system-monitor command.Execute the clear support command to clear the kernel flash.FW-1439MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch status change contributing factor Switch offline.LOGWARNINGIndicates that the switch is not in a healthy state. This occurred because the switch is offline.Execute the chassis enable command to bring the switch online.Network OS Message Reference 18953-1002807-01

7FW-1440FW-1440MessageMessage TypeSeverityProbable CauseRecommendedAction state has changed to .LOGINFOIndicates that the state of the specified field-replaceable unit (FRU) has changed to "absent".Verify if the event was planned. If the event was planned, no action is required. If the event was notplanned, check with your system administrator on the hardware state change.FW-1441MessageMessage TypeSeverityProbable CauseRecommendedAction state has changed to .LOGINFOIndicates that the state of the specified field-replaceable unit (FRU) has changed to "inserted". Thismeans that an FRU is inserted but not powered on.Verify if the event was planned. If the event was planned, no action is required. If the event was notplanned, check with your system administrator on the hardware state change.FW-1442MessageMessage TypeSeverityProbable CauseRecommendedAction state has changed to .LOGINFOIndicates that the state of the specified field-replaceable unit (FRU) has changed to "on".Verify if the event was planned. If the event was planned, no action is required. If the event was notplanned, check with your system administrator on the hardware state change.FW-1443MessageMessage TypeSeverityProbable Cause state has changed to .LOGINFOIndicates that the state of the specified field-replaceable unit (FRU) has changed to "off".190 Network OS Message Reference53-1002807-01

FW-1444 7RecommendedActionVerify if the event was planned. If the event was planned, no action is required. If the event was notplanned, check with your system administrator on the hardware state change.FW-1444MessageMessage TypeSeverityProbable CauseRecommendedAction state has changed to .LOGWARNINGIndicates that the state of the specified field-replaceable unit (FRU) has changed to "faulty".Replace the FRU.FW-1447MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch status change contributing factor SFM: SFM failures ().LOGWARNINGIndicates that the switch is not in a healthy state. This occurred because the number of switch fabricmodule (SFM) failures is greater than or equal to the policy set by the system-monitor command.Replace the faulty SFM.FW-1500MessageMessage TypeSeverityProbable CauseRecommendedActionMail overflow - Alerts being discarded.LOGWARNINGIndicates that a mail alert overflow condition has occurred.Resolve or disable the mail alert using the system-monitor-mail fru command.Network OS Message Reference 19153-1002807-01

7FW-1501FW-1501MessageMessage TypeSeverityProbable CauseRecommendedActionMail overflow cleared - alerts discarded.LOGINFOIndicates that the mail overflow condition has cleared.No action is required.FW-1510MessageMessage TypeSeverityProbable CauseRecommendedAction threshold exceeded: Port disabled.LOGINFOIndicates that the specified port is now disabled because the link on this port had multiple link failuresthat exceed Fabric Watch (FW) threshold on the port. The link failures occurred due to one of followingreasons:• Physical and hardware problems on the switch.• Loss of synchronization.• Hardware failures.• A defective small form-factor pluggable (SFP) transceiver or faulty cable.Protocol errors indicates cyclic redundancy check (CRC) sum disparity. Occasionally, these errors occurdue to software glitches. Persistent errors occur due to hardware problems.Check for concurrent loss of synchronization errors. Check the SFP transceiver and the cable andenable the port using the no shutdown command.FW-3101MessageMessage TypeSeverityProbable CauseRecommendedAction, , is below low boundary(High=, Low=).Current value is .LOGINFOIndicates that the number of invalid cyclic redundancy checks (CRCs) that the port experiences hasfallen below the low boundary.No action is required. Respond to this message as is appropriate to the particular policy of the end-userinstallation. A low number of invalid CRCs means the switch is functioning normally.192 Network OS Message Reference53-1002807-01

FW-3102 7FW-3102MessageMessage TypeSeverityProbable CauseRecommendedAction, , is above high boundary(High=, Low=).Current value is .LOGWARNINGIndicates that the number of invalid cyclic redundancy checks (CRCs) that the port experiences has risenabove the high boundary.This error generally indicates an deteriorating fabric hardware. Check small form-factor pluggable (SFP)transceivers, cables, and connections for faulty hardware. Verify that all optical hardware is clean.FW-3103MessageMessage TypeSeverityProbable CauseRecommendedAction, , is between high and low boundaries(High=,Low=). Current value is .LOGINFOIndicates that the number of invalid cyclic redundancy checks (CRCs) that the port experiences haschanged from a value outside of the acceptable range to a value within the acceptable range.Respond to this message as is appropriate to the particular policy of the end-user installation. Frequentfluctuations in CRC errors generally indicate an aging fabric. Check the small form-factor pluggable(SFP) transceivers, cables, and connections for faulty hardware. Verify that all optical hardware is clean.FW-3104MessageMessage TypeSeverityProbable CauseRecommendedAction, , has crossed lower threshold boundary to inbetween(High=, Low=). Current value is .LOGINFOIndicates that the number of invalid cyclic redundancy checks (CRCs) that the port experiences crossedlower threshold boundary to a value within the acceptable range.Respond to this message as is appropriate to the particular policy of the end-user installation. Frequentfluctuations in CRC errors generally indicate an aging fabric. Check small form-factor pluggable (SFP)transceivers, cables, and connections for faulty hardware. Verify that all optical hardware is clean.Network OS Message Reference 19353-1002807-01

7FW-3105FW-3105MessageMessage TypeSeverityProbable CauseRecommendedAction, , has dropped below upper threshold boundary to inbetween(High=, Low=). Current value is .LOGINFOIndicates that the number of invalid cyclic redundancy checks (CRCs) that the port experiences hasdropped below upper threshold boundary to a value within the acceptable range.Respond to this message as is appropriate to the particular policy of the end-user installation. Frequentfluctuations in CRC errors generally indicate an aging fabric. Check small form-factor pluggable (SFP)transceivers, cables, and connections for faulty hardware. Verify that all optical hardware is clean.FW-3107MessageMessage TypeSeverityProbable CauseRecommendedAction, , is below low boundary(High=, Low=).Current value is .LOGINFOIndicates that the number of Abnormal Frame termination frames that the port experiences has fallenbelow the low boundary.No action is required. Respond to this message as is appropriate to the particular policy of the end-userinstallation. A low number of abnormal frame termination errors means the system is operating normally.FW-3108MessageMessage TypeSeverityProbable CauseRecommendedAction, , is above high boundary(High=, Low=).Current value is .LOGWARNINGIndicates that the number of abnormal frame termination frames that the port experiences has risenabove the high boundary. Flapping interfaces during the traffic flow can generate this error.Check all loose connections in the fabric.194 Network OS Message Reference53-1002807-01

FW-3109 7FW-3109MessageMessage TypeSeverityProbable CauseRecommendedAction, , is between high and low boundaries(High=,Low=). Current value is .LOGINFOIndicates that the number of abnormal frame termination frames that the port experiences has changedfrom a value outside of the acceptable range to a value within the acceptable range.Respond to this message as is appropriate to the particular policy of the end-user installation. Check allloose connections in the fabric.FW-3110MessageMessage TypeSeverityProbable CauseRecommendedAction, , has crossed lower threshold boundary to inbetween(High=, Low=). Current value is .LOGINFOIndicates that the number of abnormal frame termination frames that the port experiences crossed lowerthreshold boundary to a value within the acceptable range.Respond to this message as is appropriate to the particular policy of the end-user installation. Check allloose connections in the fabric.FW-3111MessageMessage TypeSeverityProbable CauseRecommendedAction, , has dropped below upper threshold boundary to inbetween(High=, Low=). Current value is .LOGINFOIndicates that the number of abnormal frame termination frames that the port experiences has droppedbelow upper threshold boundary to a value within the acceptable range.Respond to this message as is appropriate to the particular policy of the end-user installation. Check allloose connections in the fabric.Network OS Message Reference 19553-1002807-01

7FW-3113FW-3113MessageMessage TypeSeverityProbable CauseRecommendedAction, , is below low boundary(High=, Low=).Current value is .LOGINFOIndicates that the number of frames with symbol error that the port experiences has fallen below the lowboundary.Respond to this message as is appropriate to the particular policy of the end-user installation. A lownumber of symbol errors means the system is operating normally.FW-3114MessageMessage TypeSeverityProbable CauseRecommendedAction, , is above high boundary(High=, Low=).Current value is .LOGWARNINGIndicates that the number of frames with symbol error that the port experiences has risen above the highboundary. Flapping interfaces or loose connections can cause this error.A high number of symbol errors indicate a deteriorated device, cable, or hardware.Check your small form-factor pluggables (SFPs), cables, and connections for faulty hardware. Verify thatall optical hardware is clean.FW-3115MessageMessage TypeSeverityProbable CauseRecommendedAction, , is between high and low boundaries(High=,Low=). Current value is .LOGINFOIndicates that the number of frames with symbol error that the port experiences has changed from avalue outside of the acceptable range to a value within the acceptable range.Respond to this message as is appropriate to the particular policy of the end-user installation. Check allcables and form factors in the system.196 Network OS Message Reference53-1002807-01

FW-3116 7FW-3116MessageMessage TypeSeverityProbable CauseRecommendedAction, , has crossed lower threshold boundary to inbetween(High=, Low=). Current value is .LOGINFOIndicates that the number of frames with symbol error that the port experiences crossed lower thresholdboundary to a value within the acceptable range.Respond to this message as is appropriate to the particular policy of the end-user installation. Check allcables and form factors in the system.FW-3117MessageMessage TypeSeverityProbable CauseRecommendedAction, , has dropped below upper threshold boundary to inbetween(High=, Low=). Current value is .LOGINFOIndicates that the number of frames with symbol error that the port experiences has dropped below upperthreshold boundary to a value within the acceptable range.Respond to this message as is appropriate to the particular policy of the end-user installation. Check allcables and form factors in the system.FW-3119MessageMessage TypeSeverityProbable CauseRecommendedAction, , is below low boundary(High=, Low=).Current value is .LOGINFOIndicates that the number of inter frame gap violation errors that the port experiences has fallen belowthe low boundary.Respond to this message as is appropriate to the particular policy of the end-user installation. A lownumber of inter frame gap errors means the system is operating normally.Network OS Message Reference 19753-1002807-01

7FW-3120FW-3120MessageMessage TypeSeverityProbable CauseRecommendedAction, , is above high boundary(High=, Low=).Current value is .LOGWARNINGIndicates that the number of inter frame gap violation errors that the port experiences has risen above thehigh boundary. Flapping interfaces during the traffic flow can generate this error. Congestion ortransmitting multiple frames without an inter frame gap.Check loose connections and congestion in the fabric.FW-3121MessageMessage TypeSeverityProbable CauseRecommendedAction, , is between high and low boundaries(High=,Low=). Current value is .LOGINFOIndicates that the number of inter frame gap violation errors that the port experiences has changed froma value outside of the acceptable range to a value within the acceptable range.Respond to this message as is appropriate to the particular policy of the end-user installation. Checkloose connections and congestion in the fabric.FW-3122MessageMessage TypeSeverityProbable CauseRecommendedAction, , has crossed lower threshold boundary to inbetween(High=, Low=). Current value is .LOGINFOIndicates that the number of inter frame gap violation errors that the port experiences crossed lowerthreshold boundary to a value within the acceptable range.Respond to this message as is appropriate to the particular policy of the end-user installation. Checkloose connections and congestion in the fabric.198 Network OS Message Reference53-1002807-01

FW-3123 7FW-3123MessageMessage TypeSeverityProbable CauseRecommendedAction, , has dropped below upper threshold boundary to inbetween(High=, Low=). Current value is .LOGINFOIndicates that the number of inter frame gap violation errors that the port experiences has dropped belowupper threshold boundary to a value within the acceptable range.Respond to this message as is appropriate to the particular policy of the end-user installation. Checkloose connections and congestion in the fabric.Network OS Message Reference 19953-1002807-01

7HASM-1000HASM MessagesHASM-1000MessageMessage TypeSeverityProbable CauseRecommendedActionComponent terminated. System initiated reload/failover forrecovery.LOGCRITICALIndicates that the software watchdog detected termination of a daemon and the system will reload orfailover to recover.After the system reloads, execute the copy support command and contact your switch service provider.HASM-1001MessageMessage TypeSeverityProbable CauseRecommendedActionNon-restartable component terminated. System initiatedreload/failover for recovery.LOGCRITICALIndicates that the software watchdog detected termination of a daemon and the system will reload orfailover to recover.After the system reloads, execute the copy support command and contact your switch service provider.HASM-1002MessageMessage TypeSeverityProbable CauseRecommendedActionError happens on service instance : (Critical).LOGCRITICALIndicates software failure.Execute the copy support command and reload the system manually to recover.200 Network OS Message Reference53-1002807-01

HASM-1003 7HASM-1003MessageMessage TypeSeverityProbable CauseRecommendedActionError happened on service instance :.LOGWARNINGIndicates software error such as mismatch in the fabric synchronization service (FSS) configuration.Execute the copy support command and reload the system manually to recover.HASM-1004MessageMessage TypeClassSeverityProbable CauseProcessor reloaded - .AUDIT | LOGSECURITYINFOIndicates that the system has been reloaded either because of a user action or an error. The switchreload can be initiated one of the following commands: firmware download, fastboot, ha failover, andreload. Some examples of errors that may initiate this message are hardware errors, software errors,compact flash (CF) errors, or memory errors. The reason for reload can be any of the following:• Hafailover• Reset• Fastboot• Giveup Master:SYSM• CP Faulty:SYSM• FirmwareDownload• ConfigDownload:MS• ChangeWWN:EM• Reboot:WebTool• Fastboot:WebTool• Software Fault:Software Watchdog• Software Fault:Kernel Panic• Software Fault:ASSERT• Reboot:SNMP• Fastboot:SNMP• Reboot• Chassis Config• Reload:API• Reload:HAM• EMFault:EMNetwork OS Message Reference 20153-1002807-01

7HASM-1013RecommendedActionCheck the error log on both management modules for additional messages that may indicate the reasonfor the switch reload.HASM-1013MessageMessage TypeSeverityProbable CauseRecommendedActionRestartable daemon () terminated prematurely. System initiatedfailover/reload for recovery.LOGCRITICALIndicates that a restartable daemon terminated before the system has booted up completely.After the system reloads, execute the copy support command and contact your switch service provider.HASM-1014MessageMessage TypeSeverityProbable CauseRecommendedActionRestartable daemon () terminated while the system was booting up.LOGCRITICALIndicates that a restartable daemon terminated before the system has booted up completely.Execute the copy support command and reload the system manually to recover.HASM-1019MessageMessage TypeSeverityProbable CauseRecommendedActionFirmware operation () was aborted due to disconnection of the peernode.LOGWARNINGIndicates that the peer node has been reloaded or disconnected due to a software error.No action is required. Firmware commit will be started automatically to repair the compact flash (CF)partitions in system.202 Network OS Message Reference53-1002807-01

HASM-1020 7HASM-1020MessageMessage TypeSeverityProbable CauseRecommendedActionFirmware operation () was aborted due to timeout.LOGWARNINGIndicates that the firmware operation took too long to complete due to CPU overload or other softwareerrors.No action is required. Firmware commit will be started automatically to repair the compact flash (CF)partitions in the system.HASM-1021MessageMessage TypeSeverityProbable CauseRecommendedActionFirmware operation () was aborted manually.LOGWARNINGIndicates that the specified firmware operation was aborted manually.No action is required.HASM-1022MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to fork firmware child process.LOGWARNINGIndicates that the firmware operation could not be started due to a software error.Execute the copy support command and contact your switch service provider.HASM-1023MessageMessage TypeSeverityProbable CauseThere is no HA connection between the MMs due to firmware incompatibility.LOGWARNINGIndicates that the firmware in the management modules are not compatible.Network OS Message Reference 20353-1002807-01

7HASM-1024RecommendedActionUpgrade the firmware on the standby management module to be the same as the active managementmodule.HASM-1024MessageMessage TypeSeverityProbable CauseRecommendedActionFirmware is not available at on MM.LOGWARNINGIndicates that the firmware for the line card (LC) is not available in the management module compactflash (CF) card. This event can be due to firmware corruption.Execute the copy support command and contact your switch service provider.HASM-1025MessageMessage TypeSeverityProbable CauseRecommendedActionHA is disconnected between the MMs due to incompatible features.LOGWARNINGIndicates that a feature is enabled and it is not compatible with the firmware running on the standbymanagement module.Upgrade the firmware on the standby management module to be the same as the active managementmodule before enabling the feature.HASM-1026MessageMessage TypeSeverityProbable CauseRecommendedActionThe last reboot is due to Kernel Panic in .LOGWARNINGIndicates that the system has reloaded due to kernel panic in the specified module.Execute the copy support command and contact your switch service provider.204 Network OS Message Reference53-1002807-01

HASM-1100 7HASM-1100MessageMessage TypeSeverityProbable CauseRecommendedActionHA State is in sync.LOGINFOIndicates that the high availability (HA) state for the active management module is in synchronization withthe HA state of the standby management module. If the standby management module is healthy, thefailover will be nondisruptive.No action is required.HASM-1101MessageMessage TypeSeverityProbable CauseRecommendedActionHA State out of sync.LOGWARNINGIndicates that the high availability (HA) state for the active management module is out of synchronizationwith the HA state of the standby management module. If the active management module failover occurswhen the HA state is out of sync, the failover is disruptive.If this message was logged as a result of a user-initiated action, no action is required.Execute the ha dump command to diagnose the problem.If the problem persists, execute the copy support command and contact your switch service provider.HASM-1102MessageMessage TypeSeverityProbable CauseRecommendedActionHeartbeat misses to reached threshold.LOGINFOIndicates that either the active management module Ethernet Media Access Controller (EMAC) or theindicated interface module is down. The active management module will run a diagnostic test on theEMAC and will wait for the interface module to reset it if it is down.No action is requiredNetwork OS Message Reference 20553-1002807-01

7HASM-1103HASM-1103MessageMessage TypeSeverityProbable CauseRecommendedActionHeartbeat to down.LOGINFOIndicates that the active management module has detected that the indicated interface module is down.This event may happen as a result of one of the following conditions: an operator-initiated action such asfirmware download, if the interface module is reset or removed, or an error occurred in the interfacemodule.Monitor the interface module for a few minutes. If this message is due to reloading of the interfacemodule, a message indicating heartbeat up will be displayed after the interface module has reloadedsuccessfully.If the interface module does not successfully connect to the active management module after 10minutes, reload the interface module by ejecting the interface module and reseating it.HASM-1104MessageMessage TypeSeverityProbable CauseRecommendedActionHeartbeat to up.LOGINFOIndicates that the active management module has detected that the specified interface module is up.This message indicates that the interface module is ready to start up services and it is typically displayedwhen the interface module boots up.No action is required. This message indicates that the interface module is healthy.HASM-1105MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch bring-up timed out.FFDC | LOGCRITICALIndicates that the system timed out during a reload or failover sequence, waiting for one or moreprograms to register with system services or to fail over to active status.If the switch is in an inconsistent state, reload or power cycle the chassis. Before reloading the chassis,record the firmware version on the switch or management module and execute the ha dump command.If this is a dual-management module switch, gather the output from the management module in whichthis log message appeared.206 Network OS Message Reference53-1002807-01

HASM-1106 7HASM-1106MessageMessage TypeSeverityProbable CauseRecommendedActionReset the standby management module.LOGINFOIndicates that the standby management module is being reset due to loss of heartbeat. This message istypically seen when the standby management module has been reloaded. Note that in certaincircumstances a management module may experience a double reset and reload twice. A managementmodule can recover automatically even if it has reloaded twice.No action is required.HASM-1107MessageMessage TypeSeverityProbable CauseRecommendedActionTake over the active management module.LOGINFOIndicates that a failover occurred and the standby management module takes over the activemanagement module.No action is required.HASM-1108MessageMessage TypeSeverityProbable CauseRecommendedActionAll service instances become active.LOGINFOIndicates that all service instances became active. Active is an intermediate stage in the boot process.No action is required.Network OS Message Reference 20753-1002807-01

7HASM-1109HASM-1109MessageMessage TypeSeverityProbable CauseRecommendedActionThe system is ready for configuration replay.LOGINFOIndicates that all line cards (LCs) are online and the system is ready for configuration replay.No action is required.HASM-1110MessageMessage TypeSeverityProbable CauseRecommendedActionConfiguration replay has completed on the system.LOGINFOIndicates that configuration replay has completed.No action is required.HASM-1111MessageMessage TypeSeverityProbable CauseRecommendedActionConfiguration replay has completed on .LOGINFOIndicates that configuration replay has completed on the specified slot or partition.No action is required.HASM-1120MessageMessage TypeSeverityProbable CauseCurrent version .LOGINFOIndicates the current firmware version string.208 Network OS Message Reference53-1002807-01

HASM-1121 7RecommendedActionNo action is required.HASM-1121MessageMessage TypeSeverityProbable CauseRecommendedActionNew version .LOGINFOIndicates the new firmware version string after firmware download.No action is required.HASM-1130MessageMessage TypeSeverityProbable CauseRecommendedActionThe Ethernet PHY for slot was reset successfully.LOGINFOIndicates that there was no Ethernet connection between the active management module and thespecified line card (LC). Subsequently, the PHY in the LC was reset automatically and the connectionhas been recovered.No action is required.HASM-1131MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to reset the Ethernet PHY for slot .LOGINFOIndicates that there was no Ethernet connection between the active management module and thespecified line card (LC). The active management module attempted to recover the connection byresetting the PHY in the LC but failed.Execute the copy support command and contact your switch service provider.Network OS Message Reference 20953-1002807-01

7HASM-1200HASM-1200MessageMessage TypeSeverityProbable CauseRecommendedActionDetected termination of process :.FFDC | LOGWARNINGIndicates that a process on the switch has ended unexpectedly.Copy the warning message along with any core file information and contact your switch service provider.HASM-1201MessageMessage TypeSeverityProbable CauseRecommendedAction: failed to refresh (:).FFDC | LOGWARNINGIndicates that one of the daemons is found to be unresponsive. An abort signal is sent.Copy the warning message along with any core file information and contact your switch service provider.210 Network OS Message Reference53-1002807-01

HAWK-1002 7HAWK MessagesHAWK-1002MessageMessage TypeSeverityProbable CauseRecommendedActionPort chip faulted due to internal error.LOG | FFDCERRORIndicates an internal error. All the ports on the interface module or switch will be disrupted.For a modular switch, execute the power-off and power-on commands to power cycle the interfacemodule.For a compact switch, reload or power cycle the switch.Network OS Message Reference 21153-1002807-01

7HIL-1202HIL MessagesHIL-1202MessageMessage TypeSeverityProbable CauseRecommendedActionBlower faulted, speed ( RPM) below threshold.LOGERRORIndicates that the specified fan speed (in RPMs) has fallen below the minimum threshold.Replace the fan field-replaceable unit (FRU). Refer to the Hardware Reference Manual of your switch forinstructions to replace the fan FRU.HIL-1301MessageMessage TypeSeverityProbable CauseRecommendedActionA blower failed or missing. Replace failed or missing blower assembly immediately.LOGWARNINGIndicates that a fan field-replaceable unit (FRU) has failed or has been removed. This message is oftenpreceded by a low speed error message. This problem may overheat the switch.Replace the affected fan FRU immediately. Refer to the Hardware Reference Manual of your switch forinstructions to replace the fan FRU.HIL-1302MessageMessage TypeSeverityProbable CauseRecommendedAction blowers failed or missing. Replace failed or missing blower assembliesimmediately.LOGWARNINGIndicates that multiple fan field-replaceable units (FRUs) have failed or are missing on the switch. Thismessage is often preceded by a low fan speed message.Replace the affected fan FRUs immediately. Refer to the Hardware Reference Manual of your switch forinstructions to replace the fan FRU.212 Network OS Message Reference53-1002807-01

HIL-1404 7HIL-1404MessageMessage TypeSeverityProbable CauseRecommendedAction fan FRUs missing. Install fan FRUs immediately.LOGWARNINGIndicates that one or more fan field-replaceable units (FRUs) have been removed.Install the missing fan FRUs immediately.HIL-1505MessageMessage TypeSeverityProbable CauseRecommendedActionHigh temperature ( C), fan speed increasing perenvironmental specifications.LOGINFOIndicates that temperature in the system has risen above the warning threshold and the fan speed hasbeen increased to prevent overheating of the system.Execute the show environment fan command to verify that all fans are working properly.Make sure that the area is well ventilated and the room temperature is within operational range of yourswitch. Refer to the Hardware Reference Manual of your switch for the operational temperature range.HIL-1506MessageMessage TypeSeverityProbable CauseRecommendedActionHigh temperature ( C) exceeds system temperature limit.System will shut down within 2 minutes.FFDC | LOGCRITICALIndicates that temperature in the system has risen above the critical threshold.Execute the show environment fan command to verify that all fans are working properly. Replace anydeteriorating fan field-replaceable units (FRUs).Make sure that the area is well ventilated and the room temperature is within operational range of yourswitch. Refer to the Hardware Reference Manual of your switch for the operational temperature range.Network OS Message Reference 21353-1002807-01

7HIL-1510HIL-1510MessageMessage TypeSeverityProbable CauseRecommendedActionCurrent temperature ( C) is below shutdown threshold. Systemshut down cancelled.LOGWARNINGIndicates that temperature in the system has dropped below the critical threshold; the system willcontinue operation.To help prevent future problems, execute the show environment fan command to verify all fans areworking properly.Make sure that the area is well ventilated and the room temperature is within operational range of yourswitch. Refer to the Hardware Reference Manual of your switch for the operational temperature range.HIL-1511MessageMessage TypeSeverityProbable CauseRecommendedActionMISMATCH in Fan airflow direction. Replace FRU with fan airflow in same direction.LOGWARNINGIndicates that the airflow of the fan is in the reverse direction. This may heat up the system.Replace the fan field-replaceable units (FRUs) in such a manner that the air flows in the same directionas the remaining fans. Refer to the Hardware Reference Manual of your switch for instructions to replacethe fan FRUs.HIL-1512MessageMessage TypeSeverityProbable CauseRecommendedActionMISMATCH in PSU-Fan FRUs airflow direction. Replace PSU with fan airflow in samedirection.LOGWARNINGIndicates that the airflow of the power supply unit (PSU) fan is in the reverse direction. This may heat upthe system.Replace the PSU fan field-replaceable unit (FRU) in such a manner that the air flows in the samedirection as the remaining fans. Refer to the Hardware Reference Manual of your switch for instructionsto replace the PSU fan FRU.214 Network OS Message Reference53-1002807-01

HIL-1521 7HIL-1521MessageMessage TypeSeverityProbable CauseRecommendedAction, high temperature ().LOGWARNINGIndicates that the temperature of the specified interface module has risen above the warning threshold.Execute the show environment fan command to verify that all fans are working properly.Make sure that the area is well ventilated and that the room temperature is within operational range ofyour switch. Refer to the Hardware Reference Manual of your switch for the operational temperaturerange.HIL-1522MessageMessage TypeSeverityProbable CauseRecommendedAction, high temperature (). Unit will be shutdown in 2 minutes if temperature remains high.FFDC | LOGCRITICALIndicates that the temperature of the specified interface module has risen above the critical threshold.This usually follows a high temperature message.Execute the show environment fan command to verify that all fans are working properly.Make sure that the area is well ventilated and the room temperature is within operational range of yourswitch. Refer to the Hardware Reference Manual of your switch for the operational temperature range.If the message persists, replace the interface module.HIL-1523MessageMessage TypeSeverityProbable CauseRecommendedAction, unit shutting down.FFDC | LOGCRITICALIndicates that the temperature of the specified interface module was above the maximum threshold for atleast two minutes and therefore it has been shut down to prevent damage. This message usually followsa high temperature warning message.Execute the show environment fan command to verify that all fans are working properly.Make sure that the area is well ventilated and the room temperature is within the operational range ofyour switch. Refer to the Hardware Reference Manual of your switch for the operational temperaturerange.If the message persists, replace the faulty interface module.Network OS Message Reference 21553-1002807-01

7HIL-1605HIL-1605MessageMessage TypeSeverityProbable CauseRecommendedActionHigh temperature ( C), fan speed increasing perenvironmental specifications.LOGINFOIndicates that temperature in the system has risen above the threshold and therefore the fan speed hasbeen increased to prevent overheating of the system.No action is required.216 Network OS Message Reference53-1002807-01

HLO-1001 7HLO MessagesHLO-1001MessageMessage TypeSeverityProbable CauseRecommendedActionIncompatible Inactivity timeout from port , correctvalue .LOG | FFDCERRORIndicates that the hello (HLO) message was incompatible with the value specified in the fabric shortestpath first (FSPF) protocol. The Brocade switch will not accept FSPF frames from the remote switch.In the Network OS, the HLO dead timeout value is not configurable, so this error can only occur when theBrocade switch is connected to a switch from another manufacturer.The dead timeout value of the remote switch must be compatible with the value specified in the FSPFprotocol. Refer to the documentation for the other manufacturer's switch to change this value.HLO-1002MessageMessage TypeSeverityProbable CauseRecommendedActionIncompatible Hello timeout from port , correct value.LOG | FFDCERRORIndicates that the hello (HLO) message was incompatible with the value specified in the fabric shortestpath first (FSPF) protocol. The Brocade switch will not accept FSPF frames from the remote switch.In the Network OS, the HLO timeout value is not configurable, so this error can only occur when theBrocade switch is connected to a switch from another manufacturer.The HLO timeout value of the remote switch must be compatible with the value specified in the FSPFprotocol. Refer to the documentation for the other manufacturer's switch to change this value.Network OS Message Reference 21753-1002807-01

7HLO-1003HLO-1003MessageMessage TypeSeverityProbable CauseRecommendedActionInvalid Hello received from port , RBridge = , RemotePort = .LOGERRORIndicates that the hello (HLO) message received was invalid and the frame was dropped. The Brocadeswitch will not accept fabric shortest path first (FSPF) frames from the remote switch.The switch has received an invalid HLO because either the RBridge or port number in the HLO messagehas an invalid value. This error can only occur when the Brocade switch is connected to a switch fromanother manufacturer.The HLO message of the remote switch must be compatible with the value specified in the FSPFprotocol. Refer to the documentation for the other manufacturer's switch to change this value.218 Network OS Message Reference53-1002807-01

HSL-1000 7HSL MessagesHSL-1000MessageMessage TypeSeverityProbable CauseRecommendedActionHSL initialization failed.LOGCRITICALIndicates a hardware subsystem layer (HSL) initialization failure. This error is caused by other systemerrors.Execute the copy support command and contact your switch service provider.HSL-1001MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to acquire the system MAC address pool.LOGCRITICALIndicates the failure to acquire the system address. This error is caused by other system errors.Execute the show logging raslog command to view the error log for other system errors and correct theerrors.HSL-1004MessageMessage TypeSeverityProbable CauseRecommendedActionIncompatible SFP transceiver for interface is detected.LOGERRORIndicates that an incompatible small form-factor pluggable (SFP) transceiver for the interface has beeninserted.Disable the interface using the shutdown command and insert an SFP transceiver that is supported onthe interface. After the SFP transceiver is inserted, re-enable the interface using the no shutdowncommand.Network OS Message Reference 21953-1002807-01

7HSL-1006HSL-1006MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to get the kernel page size bytes for the Memory Map (MMap).LOGCRITICALIndicates that there is not enough contiguous kernel memory.Execute the show logging raslog command to view the error log for other system errors and correct theerrors.HSL-1009MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to create Brocade trunk interface .LOGERRORIndicates failure to create Brocade trunk because the hardware resources are exhausted.Do not exceed the maximum trunk configuration allowed by the system.220 Network OS Message Reference53-1002807-01

IGMP-1001 7IGMP MessagesIGMP-1001MessageMessage TypeSeverityProbable CauseRecommendedActionMsgQ enqueue failed (rc: ).DCEERRORIndicates an internal inter-process communication (IPC) failure due to the scalability scenario.Reduce the number of groups and MRouter ports.IGMP-1002MessageMessage TypeSeverityProbable CauseRecommendedActionIPC with McastSS failed (message-id: , rc: ).DCEERRORIndicates an internal inter-process communication (IPC) failure due to the scalability scenario.Reduce the number of groups and MRouter ports.IGMP-1003MessageMessage TypeSeverityProbable CauseRecommendedActionMRouter eNS update from a VCS RBridge (ID:) running lower firmware version.DCEERRORIndicates an older message update.Upgrade the VCS RBridge firmware to the latest build.Network OS Message Reference 22153-1002807-01

7IGMP-1004IGMP-1004MessageMessage TypeSeverityProbable CauseRecommendedActionIGMP maximum VLANs enabled. Cannot enable IGMP on .DCEINFOIndicates that the number of VLANs on which internet group multicast protocol (IGMP) can be enabledhas reached the maximum limit. Therefore, IGMP cannot be enabled on the specified VLAN.No action is required.222 Network OS Message Reference53-1002807-01

IPAD-1000 7IPAD MessagesIPAD-1000MessageMessage TypeSeverityProbable CauseRecommendedActionIP Config change: Entity:/ Interface:/ Adresss family: Source of change: Address: DHCP:.LOGINFOIndicates that the local IP address has been changed manually or it was reconfigured automatically bythe Dynamic Host Configuration Protocol (DHCP) server.No action is required.IPAD-1001MessageMessage TypeSeverityProbable CauseRecommendedAction/ DHCP .LOGINFOIndicates that the gateway IP address has been changed manually or it was reconfigured automaticallyby the Dynamic Host Configuration Protocol (DHCP) server.No action is required.IPAD-1002MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch name has been successfully changed to .LOGINFOIndicates that the switch name has been changed.No action is required.Network OS Message Reference 22353-1002807-01

7IPAD-1003IPAD-1003MessageMessage TypeSeverityProbable CauseRecommendedActionlibipadm: .LOG | FFDCERRORIndicates that the IP admin library has encountered an unexpected error.Execute the copy support command and contact your switch service provider.IPAD-1004MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to set the host name due to /etc/hosts file corruption.LOGINFOIndicates that the /etc/hosts file was inconsistent and it could not be recovered.Execute the copy support command and contact your switch service provider.IPAD-1005MessageMessage TypeSeverityProbable CauseRecommendedActionThe /etc/hosts file was inconsistent but has been recovered successfully.LOGINFOIndicates that the /etc/hosts file was inconsistent but it was recovered.No action is required.224 Network OS Message Reference53-1002807-01

KTRC-1001 7KTRC MessagesKTRC-1001MessageMessage TypeSeverityProbable CauseRecommendedActionDump memory size exceeds dump file size.LOGWARNINGIndicates that the dump memory size has exceeded the dump file size.Execute the copy support command and reload the switch. If the problem persists, contact your switchservice provider.KTRC-1002MessageMessage TypeSeverityProbable CauseRecommendedActionConcurrent trace dumping.LOGINFOIndicates that the initial background dump has not completed.No action is required.KTRC-1003MessageMessage TypeSeverityProbable CauseRecommendedActionCannot open ATA dump device.LOGERRORIndicates that the advanced technology attachment (ATA) dump driver is not initialized properly.Execute the copy support command and reload the switch. If the problem persists, contact your switchservice provider.Network OS Message Reference 22553-1002807-01

7KTRC-1004KTRC-1004MessageMessage TypeSeverityProbable CauseRecommendedActionCannot write to ATA dump device.LOGERRORIndicates that the write boundary in the advanced technology attachment (ATA) dump device hasexceeded.Execute the copy support command and reload the switch. If the problem persists, contact your switchservice provider.KTRC-1005MessageMessage TypeSeverityProbable CauseRecommendedActionTrace initialization failed. . .LOGERRORIndicates that trace was unable to initialize.Execute the copy support command and reload the switch. If the problem persists, contact your switchservice provider.226 Network OS Message Reference53-1002807-01

L2AG-1001 7L2AG MessagesL2AG-1001MessageMessage TypeSeverityProbable CauseRecommendedActionLinux socket error - error reason: , socket name: , error name.DCEERRORIndicates that an error has occurred in the Linux socket.Reload or power cycle the switch.L2AG-1002MessageMessage TypeSeverityProbable CauseRecommendedActionInitialization error : .DCEERRORIndicates that the Layer 2 Agent (L2AGT) has encountered an error during initialization.Reload or power cycle the switch.L2AG-1003MessageMessage TypeSeverityProbable CauseRecommendedActionMessage Queue Error : Message queue create failed.DCEERRORIndicates that the Layer 2 Agent (L2AGT) has encountered system service manager (SSM) messagequeue errors.Reload or power cycle the switch.Network OS Message Reference 22753-1002807-01

7L2AG-1004L2AG-1004MessageMessage TypeSeverityProbable CauseRecommendedActionFDB error: Error in creating AVL tree.DCEERRORIndicates that the Layer 2 Agent (L2AGT) has encountered an error while initializing the AVL tree.Reload or power cycle the switch.L2AG-1005MessageMessage TypeSeverityProbable CauseRecommendedActionMAC-address-table hash failed even after two attempts for slot chip .DCEERRORIndicates that the media access control (MAC) address table hash failed even after two hash changes onthe specified chip.Reload or power cycle the switch.L2AG-1006MessageMessage TypeSeverityProbable CauseRecommendedActionMAC-address-table on slot chip is 95 percent full.DCEINFOIndicates that the media access control (MAC) address table on the chip is 95 percent full.Clear some of the entries using the clear mac-address-table dynamic command or wait until the oldentries age out.L2AG-1007MessageMessage TypeSeverityProbable CauseMAC-address-table on slot chip is less than 90 percent full.DCEINFOIndicates that the media access control (MAC) address table is less than 90 percent full.228 Network OS Message Reference53-1002807-01

L2AG-1007 7RecommendedActionNo action is required. The Layer 2 Agent (L2AGT) will start learning the entries.Network OS Message Reference 22953-1002807-01

7L2SS-1001L2SS MessagesL2SS-1001MessageMessage TypeSeverityProbable CauseRecommendedActionLinux socket error - error reason: , socket name: , error name.DCEERRORIndicates that an error has occurred in the Linux socket.Reload or power cycle the switch.L2SS-1002MessageMessage TypeSeverityProbable CauseRecommendedActionInitialization error: .DCEERRORIndicates that the Layer 2 system (L2SYS) has encountered an error during initialization.Reload or power cycle the switch.L2SS-1003MessageMessage TypeSeverityProbable CauseRecommendedActionMessage Queue Error: Failed to create a Message Queue.DCEERRORIndicates that the Layer 2 system (L2SYS) has encountered system service manager (SSM) messagequeue errors.Reload or power cycle the switch.230 Network OS Message Reference53-1002807-01

L2SS-1004 7L2SS-1004MessageMessage TypeSeverityProbable CauseRecommendedActionFDB error: Error in creating the AVL tree.DCEERRORIndicates that the Layer 2 system (L2SYS) has encountered an error while initializing the AVL tree.Reload or power cycle the switch.L2SS-1005MessageMessage TypeSeverityProbable CauseRecommendedActionMAC-address-table hash failed even after two attempts for slot chip .DCEERRORIndicates that the media access control (MAC) address table hash failed even after two hash changes onthe specified chip.Reload or power cycle the switch.L2SS-1006MessageMessage TypeSeverityProbable CauseRecommendedActionMAC-address-table is 95 percent full.DCEINFOIndicates that the media access control (MAC) address table on the chip is 95 percent full.Clear some of the entries using the clear mac-address-table dynamic command or wait until the oldentries age out.Network OS Message Reference 23153-1002807-01

7L2SS-1007L2SS-1007MessageMessage TypeSeverityProbable CauseRecommendedActionMAC-address-table on slot chip is less than 90 percent full.DCEINFOIndicates that the media access control (MAC) address table on the specified chip is less than 90 percentfull.No action is required. The Layer 2 system (L2SYS) will start learning the entries.L2SS-1008MessageMessage TypeSeverityProbable CauseRecommendedActionAdding Internal MAC ::::: VID as astatic MAC.DCEINFOIndicates that a static media access control (MAC) is overriding an internal MAC entry (VRRP/SVI).No action is required.L2SS-1009MessageMessage TypeSeverityProbable CauseRecommendedActionFabric-wide Layer 2 flush command issued.DCEINFOIndicates that a fabric-wide Layer 2 flush command is issued and the entire Layer 2 forwarding table willbe cleared.No action is required.232 Network OS Message Reference53-1002807-01

L2SS-1010 7L2SS-1010MessageMessage TypeSeverityProbable CauseRecommendedActionFabric-wide l2 flush completed, status - .DCEINFOIndicates that the entire Layer 2 forwarding table has been cleared.No action is required.Network OS Message Reference 23353-1002807-01

7LACP-1003LACP MessagesLACP-1003MessageMessage TypeSeverityProbable CauseRecommendedActionPort-channel up in defaulted state.DCEINFOIndicates that port-channel is now up in the defaulted state.No action is required.LACP-1004MessageMessage TypeSeverityProbable CauseRecommendedActionPort-channel down from defaulted state.DCEINFOIndicates that port-channel is now down from the defaulted state.No action is required.234 Network OS Message Reference53-1002807-01

LOG-1000 7LOG MessagesLOG-1000MessageMessage TypeSeverityProbable CauseRecommendedActionPrevious message has repeated times.LOGINFOIndicates that the previous message was repeated the specified number of times.No action is required.LOG-1001MessageMessage TypeSeverityProbable CauseRecommendedActionA log message was dropped.LOG | FFDCWARNINGIndicates that a log message was dropped. A trace dump file has been created.Execute the copy support command and contact your switch service provider.LOG-1002MessageMessage TypeSeverityProbable CauseRecommendedActionA log message was not recorded.FFDC | LOGWARNINGIndicates that a log message was not recorded by the error logging system. A trace dump file has beencreated. The message may still be visible through Simple Network Management Protocol (SNMP) orother management tools.Execute the copy support command and contact your switch service provider.Network OS Message Reference 23553-1002807-01

7LOG-1003LOG-1003MessageMessage TypeSeverityProbable CauseRecommendedActionSYSTEM error log has been cleared.LOGINFOIndicates that the persistent system error log has been cleared.No action is required.LOG-1004MessageMessage TypeSeverityProbable CauseRecommendedActionLog message flooding detected and blocked.LOGERRORIndicates that the specified message has been flooding and was blocked.Reload the switch. If the message persists, execute the copy support command and contact your switchservice provider.LOG-1005MessageMessage TypeSeverityProbable CauseRecommendedActionLog message has been disabled.LOGINFOIndicates that the specified message has been disabled from logging.No action is required.LOG-1006MessageMessage TypeSeverityProbable CauseLog message has been enabled.LOGINFOIndicates that the specified message has been enabled for logging.236 Network OS Message Reference53-1002807-01

LOG-1007 7RecommendedActionNo action is required.LOG-1007MessageMessage TypeSeverityProbable CauseRecommendedActionDCE error log has been cleared.DCEINFOIndicates that the persistent DCE error log has been cleared.No action is required.Network OS Message Reference 23753-1002807-01

7LSDB-1001LSDB MessagesLSDB-1001MessageMessage TypeSeverityProbable CauseRecommendedActionLink State ID out of range.LOGINFOIndicates that the specified link state database ID is out of the acceptable range. The valid link state ID isthe same as the valid RBridge ID, whose range is from 1 through 239. The switch will discard the recordbecause it is not supported.No action is required.LSDB-1002MessageMessage TypeSeverityProbable CauseRecommendedActionLocal Link State Record reached max incarnation.LOGINFOIndicates the local link state database reached the maximum incarnations.An "incarnation" is a progressive number that identifies the most recent version of the link state record(LSR). The switch generates its local link state record when first enabled. The incarnation number willbegin again at 0x80000001 after reaching 0x7FFFFFFF.No action is required.LSDB-1003MessageMessage TypeSeverityProbable CauseNo database entry for local Link State Record, RBridge .FFDC | LOGCRITICALIndicates that there is no local link state record (LSR) entry in the link state database. The switch shouldalways generate its own local entry when starting up.An "incarnation" is a progressive number that identifies the most recent version of LSR. The switchgenerates its local LSR when first enabled. By disabling and enabling the switch, a new local link staterecord is generated.238 Network OS Message Reference53-1002807-01

LSDB-1004 7RecommendedActionExecute the chassis disable and chassis enable commands. A new local link state record is generatedduring the switch enable.LSDB-1004MessageMessage TypeSeverityProbable CauseRecommendedActionNo Link State Record for RBridge .LOGWARNINGIndicates there is no link state record (LSR) for the specified local RBridge.No action is required. The other switch will pass the LSR after the fabric is stable.Network OS Message Reference 23953-1002807-01

7MCAST_SS-1001MCAST_SS MessagesMCAST_SS-1001MessageMessage TypeSeverityProbable CauseRecommendedActionSocket Error: () for socket the error code.DCEERRORIndicates that an error has occurred in the Linux socket.Reload or power cycle the switch.MCAST_SS-1002MessageMessage TypeSeverityProbable CauseRecommendedActionSocket Error: sock name Error type seq pid .DCEERRORIndicates that the specified error has occurred while processing the hardware abstraction layer (HAL)message.Reload or power cycle the switch.MCAST_SS-1003MessageMessage TypeSeverityProbable CauseRecommendedActionLearning error: () - VLAN MAC/group .DCEERRORIndicates that the multicast subsystem (mcast_ss) has encountered an error while learning the mediaaccess control (MAC) addresses.Reload or power cycle the switch.240 Network OS Message Reference53-1002807-01

MCAST_SS-1004 7MCAST_SS-1004MessageMessage TypeSeverityProbable CauseRecommendedActionNSM error: () for VLAN port .DCEERRORIndicates that the multicast subsystem (mcast_ss) has encountered an error during a network servicemodule (NSM) event.Reload or power cycle the switch.MCAST_SS-1005MessageMessage TypeSeverityProbable CauseRecommendedActionMessage error: Invalid message type expecting or or.DCEERRORIndicates that the type of the message received from the driver is invalid.Reload or power cycle the switch.MCAST_SS-1006MessageMessage TypeSeverityProbable CauseRecommendedActionMessage error: ()Invalid message length expecting.DCEERRORIndicates that the length of the message received from the driver is invalid.Reload or power cycle the switch.Network OS Message Reference 24153-1002807-01

7MCAST_SS-1007MCAST_SS-1007MessageMessage TypeSeverityProbable CauseRecommendedActionInitialization error: ().DCEERRORIndicates that the multicast subsystem (mcast_ss) has encountered an error during initialization.Reload or power cycle the switch.MCAST_SS-1008MessageMessage TypeSeverityProbable CauseRecommendedActionHAL error: () - VLAN MAC/group .DCEERRORIndicates that the multicast subsystem (mcast_ss) has encountered the hardware abstraction layer(HAL) errors.Reload or power cycle the switch.MCAST_SS-1009MessageMessage TypeSeverityProbable CauseRecommendedActionL2SS error: () VLAN MAC .DCEERRORIndicates that the multicast subsystem (mcast_ss) has encountered the Layer 2 subsystem (L2SS)related errors.Reload or power cycle the switch.242 Network OS Message Reference53-1002807-01

MCAST_SS-1010 7MCAST_SS-1010MessageMessage TypeSeverityProbable CauseRecommendedActionMessage Queue error: ().DCEERRORIndicates that the multicast subsystem (mcast_ss) has encountered the message queue errors.Reload or power cycle the switch.MCAST_SS-1011MessageMessage TypeSeverityProbable CauseRecommendedActionIDB error: () port index not found for VLAN ID.DCEERRORIndicates that the specified port index is invalid.If there is an impact on the data path, reload or power cycle the switch. Refer to the Network OSAdministrator's Guide for instructions to verify the data path.MCAST_SS-1012MessageMessage TypeSeverityProbable CauseRecommendedActionIDB error: () VLAN ID not found.DCEERRORIndicates that the specified VLAN ID (VID) is invalid.If there is an impact on the data path, reload or power cycle the switch. Refer to the Network OSAdministrator's Guide for instructions to verify the data path.Network OS Message Reference 24353-1002807-01

7MCAST_SS-1013MCAST_SS-1013MessageMessage TypeSeverityProbable CauseRecommendedActionSnooping DB error: () Group not found - VLAN group .DCEERRORIndicates that the group address lookup for the specified VLAN has failed.Reload or power cycle the switch.MCAST_SS-1014MessageMessage TypeSeverityProbable CauseRecommendedActionSnooping DB error: () MAC not found - VLAN MAC-addr .DCEERRORIndicates that the media access control (MAC) address lookup for the specified VLAN has failed.Reload or power cycle the switch.MCAST_SS-1015MessageMessage TypeSeverityProbable CauseRecommendedActionHSL error: () failed for message VLAN MAC mgid CPU .DCEERRORIndicates that the specified hardware subsystem layer (HSL) related operation has failed.Reload or power cycle the switch.244 Network OS Message Reference53-1002807-01

MCAST_SS-1016 7MCAST_SS-1016MessageMessage TypeSeverityProbable CauseRecommendedActionMessage error: () ().DCEERRORIndicates that the length of the message received from the driver is invalid.Reload or power cycle the switch.MCAST_SS-1017MessageMessage TypeSeverityProbable CauseRecommendedActionLearning error: () Invalid number for ifindex .DCEERRORIndicates that the multicast subsystem (mcast_ss) has encountered an error while learning the mediaaccess control (MAC) addresses.Reload or power cycle the switch.MCAST_SS-1018MessageMessage TypeSeverityProbable CauseRecommendedActionMemory Alloc Error: () type /.DCEERRORIndicates that the multicast subsystem (mcast_ss) has encountered an error during the memoryallocation.Reload or power cycle the switch.Network OS Message Reference 24553-1002807-01

7MCAST_SS-1019MCAST_SS-1019MessageMessage TypeSeverityProbable CauseRecommendedActionPtree Error: () VLAN MAC/group .DCEERRORIndicates that the multicast subsystem (mcast_ss) has encountered an error during the Ptree operation.Reload or power cycle the switch.MCAST_SS-1020MessageMessage TypeSeverityProbable CauseRecommendedActionList Error: () VLAN MAC group .DCEERRORIndicates that the multicast subsystem (mcast_ss) has encountered an error during the List operation.Reload or power cycle the switch.246 Network OS Message Reference53-1002807-01

MPTH-1001 7MPTH MessagesMPTH-1001MessageMessage TypeSeverityProbable CauseRecommendedActionNull parent, lsId = .LOG | FFDCERRORIndicates that a null parent was reported. The minimum cost path (MPATH) uses a tree structure in whichthe parent is used to connect to the root of the tree.No action is required.MPTH-1002MessageMessage TypeSeverityProbable CauseRecommendedActionNull lsrP, lsId = .LOG | FFDCERRORIndicates that the link state record (LSR) is null.No action is required.MPTH-1003MessageMessage TypeSeverityProbable CauseRecommendedActionNo minimum cost path in candidate list.LOGWARNINGIndicates the fabric shortest path first (FSPF) module has determined that there is no minimum cost path(MPATH) available in the candidate list.No action is required.Network OS Message Reference 24753-1002807-01

7MS-1021MS MessagesMS-1021MessageMessage TypeSeverityProbable CauseRecommendedActionMS WARMBOOT failure (FSS_MS_WARMINIT failed. Reason=).LOGERRORIndicates that fabric synchronization service (FSS) warm recovery failed during the warm initializationphase of the switch reload.If the message persists, execute the copy support command and contact your switch service provider.248 Network OS Message Reference53-1002807-01

MSTP-1001 7MSTP MessagesMSTP-1001MessageMessage TypeSeverityProbable CauseRecommendedAction: .DCEERRORIndicates that the system has failed to allocate memory.Check the memory usage on the switch using the show process memory command.Reload or power cycle the switch.MSTP-1002MessageMessage TypeSeverityProbable CauseRecommendedAction: .DCEERRORIndicates that the system has failed to initialize.Reload or power cycle the switch.MSTP-1003MessageMessage TypeSeverityProbable CauseRecommendedAction: .DCEERRORIndicates a connection, transfer, or receiving error in the socket.If this is a modular switch, execute the ha failover command. If the problem persists or if this is acompact switch, download a new firmware version using the firmware download command.Network OS Message Reference 24953-1002807-01

7MSTP-1004MSTP-1004MessageMessage TypeSeverityProbable CauseRecommendedAction: .DCEERRORIndicates that a port on which PortFast is enabled has received a bridge protocol data unit (BPDU). Theport has been disabled.Disable the PortFast feature on the port using one of the following commands:• For rapid spanning tree protocol (RSTP), execute the no spanning-tree edgeport command.• For spanning tree protocol (STP), execute the no spanning-tree portfast command.After disabling the PortFast feature, execute the no shutdown command to re-enable the port.MSTP-2001MessageMessage TypeSeverityProbable CauseRecommendedAction.DCEINFOIndicates that the multiple spanning tree protocol (MSTP) bridge mode has changed.No action is required.MSTP-2002MessageMessage TypeSeverityProbable CauseRecommendedAction. My Bridge ID: Old Root: NewRoot: .DCEINFOIndicates that the multiple spanning tree protocol (MSTP) bridge or bridge instance root has beenchanged.No action is required.250 Network OS Message Reference53-1002807-01

MSTP-2003 7MSTP-2003MessageMessage TypeSeverityProbable CauseRecommendedActionMSTP instance is created.DCEINFOIndicates that the specified multiple spanning tree protocol (MSTP) instance has been created.No action is required.MSTP-2004MessageMessage TypeSeverityProbable CauseRecommendedActionMSTP instance is deleted.DCEINFOIndicates that the specified multiple spanning tree protocol (MSTP) instance has been deleted.No action is required.MSTP-2005MessageMessage TypeSeverityProbable CauseRecommendedActionVLAN is on MSTP instance .DCEINFOIndicates that the specified multiple spanning tree protocol (MSTP) instance has been modified.No action is required.MSTP-2006MessageMessage TypeSeverityProbable CauseMSTP instance brigde priority is changed from to.DCEINFOIndicates that the specified multiple spanning tree protocol (MSTP) instance priority has been modified.Network OS Message Reference 25153-1002807-01

7MSTP-2006RecommendedActionNo action is required.252 Network OS Message Reference53-1002807-01

NBFS-1001 7NBFS MessagesNBFS-1001MessageMessage TypeSeverityProbable CauseRecommendedActionDuplicate E_Port SCN from port in state ().LOGINFOIndicates that a duplicate E_Port state change number was reported. The neighbor finite state machine(NBFSM) states are as follows:• NB_ST_DOWN - The neighbor is down.• NB_ST_INIT - The neighbor is initializing.• NB_ST_DB_EX - The neighbor and the switch are exchanging data from their link state record(LSR) databases.• NB_ST_DB_ACK_WT - The neighbor is waiting for the switch to acknowledge the LSR database.• NB_ST_DB_WT - The LSR database is in waiting state; synchronization is in process.• NB_ST_FULL - The neighbor is in the finishing state.No action is required.NBFS-1002MessageMessage TypeSeverityProbable CauseRecommendedActionWrong input: to neighbor FSM, state , port.FFDC | LOGERRORIndicates that a wrong input was sent to the neighbor finite state machine (NBFSM). NBFSM states areas follows:• NB_ST_DOWN - The neighbor is down.• NB_ST_INIT - The neighbor is initializing.• NB_ST_DB_EX - The neighbor and the switch are exchanging data from their link state record(LSR) databases.• NB_ST_DB_ACK_WT - The neighbor is waiting for the switch to acknowledge the LSR database.• NB_ST_DB_WT - The LSR database is in waiting state; synchronization is in process.• NB_ST_FULL - The neighbor is in the finishing state.If this error occurs repeatedly, then there is a problem in the protocol implementation between twoswitches.Execute the show fabric route neighbor-state command to check the neighbor state of the port listed inthe message. If the neighbor state is NB_ST_FULL, then this message can safely be ignored. Otherwise,execute the shutdown and no shutdown commands to reset the port.Network OS Message Reference 25353-1002807-01

7NBFS-1003NBFS-1003MessageMessage TypeSeverityProbable CauseRecommendedActionDB_XMIT_SET flag not set in state , input , port.LOGWARNINGIndicates that the database transmit set flag was not set for the specified input state on the specified port.Neighbor finite state machine (NBFSM) states are as follows:• NB_ST_DOWN - The neighbor is down.• NB_ST_INIT - The neighbor is initializing.• NB_ST_DB_EX - The neighbor and the switch are exchanging data from their link state record(LSR) databases.• NB_ST_DB_ACK_WT - The neighbor is waiting for the switch to acknowledge the LSR database.• NB_ST_DB_WT - The LSR database is in waiting state; synchronization is in process.• NB_ST_FULL - The neighbor is in the finishing state.No action is required. The Network OS automatically recovers from this problem.254 Network OS Message Reference53-1002807-01

NS-1006 7NS MessagesNS-1006MessageMessage TypeSeverityProbable CauseRecommendedActionDuplicated WWN was detected with PID 0x and 0x.LOGWARNINGIndicates that an existing device has the same World Wide Name (WWN) as a new device that has comeonline.The switch will process the new process ID (PID) and leave the existing PID intact. Subsequent switchoperations will clean up the obsolete PID. However, administrators can check and remove devices with aduplicated WWN.NS-1009MessageMessage TypeSeverityProbable CauseRecommendedActionNS has detected a device with node WWN as zero, PID 0x.LOGWARNINGIndicates that a port has logged in with node World Wide Name (WWN) as zero, Brocade NetworkAdvisor (BNA) will not show the port connectivity.Check the device that logged in. The device could be misbehaving.NS-1012MessageMessage TypeSeverityProbable CauseRecommendedActionDetected duplicate WWPN [] - devices removed with PID 0x and 0x.LOGWARNINGIndicates that the devices with the same World Wide Port Name (WWPN) have been removed from theName Server database.Administrators should verify the reported devices with a duplicated WWPN.Network OS Message Reference 25553-1002807-01

7NSM-1001NSM MessagesNSM-1001MessageMessage TypeSeverityProbable CauseRecommendedActionInterface is online.DCEINFOIndicates that the specified interface has come online after the protocol dependencies are resolved.No action is required.NSM-1002MessageMessage TypeSeverityProbable CauseRecommendedActionInterface is protocol down.DCEINFOIndicates that the specified interface has gone offline because one of the protocol dependency isunresolved.Check for the reason codes using the show interface command and resolve the protocol dependencies.NSM-1003MessageMessage TypeSeverityProbable CauseRecommendedActionInterface is link down.DCEINFOIndicates that the specified interface has gone offline because the link was down.Check whether the connectivity is proper and the remote link is up.256 Network OS Message Reference53-1002807-01

NSM-1004 7NSM-1004MessageMessage TypeSeverityProbable CauseRecommendedActionInterface is created.DCEINFOIndicates that the specified logical interface has been created.No action is required.NSM-1007MessageMessage TypeSeverityProbable CauseRecommendedActionChassis is .DCEINFOIndicates that the chassis has been enabled or disabled.No action is required.NSM-1009MessageMessage TypeSeverityProbable CauseRecommendedActionInterface is deleted.DCEINFOIndicates that the specified logical interface has been deleted.No action is required.NSM-1010MessageMessage TypeSeverityProbable CauseInterfaceMode changed from to for interface.DCEINFOIndicates that the interface mode has been changed.Network OS Message Reference 25753-1002807-01

7NSM-1011RecommendedActionNo action is required.NSM-1011MessageMessage TypeSeverityProbable CauseRecommendedActionOperationalEndpointMode changed from to for interface.DCEINFOIndicates that the interface operational endpoint mode has been changed.No action is required.NSM-1012MessageMessage TypeSeverityProbable CauseRecommendedActionVLAN classifier group is created.DCEINFOIndicates that the specified VLAN classifier group has been created.No action is required.NSM-1013MessageMessage TypeSeverityProbable CauseRecommendedActionVLAN classifier group is deleted.DCEINFOIndicates that the specified VLAN classifier group has been deleted.No action is required.258 Network OS Message Reference53-1002807-01

NSM-1014 7NSM-1014MessageMessage TypeSeverityProbable CauseRecommendedActionVLAN classifier rule is created.DCEINFOIndicates that the specified VLAN classifier rule has been created.No action is required.NSM-1015MessageMessage TypeSeverityProbable CauseRecommendedActionVLAN classifier rule is deleted.DCEINFOIndicates that the specified VLAN classifier rule has been deleted.No action is required.NSM-1016MessageMessage TypeSeverityProbable CauseRecommendedActionVLAN classifier rule is on VLAN classifier group .DCEINFOIndicates that the specified VLAN classifier group has been modified.No action is required.NSM-1017MessageMessage TypeSeverityProbable CauseInterface is on interface .DCEINFOIndicates that the specified logical interface member list has been changed.Network OS Message Reference 25953-1002807-01

7NSM-1018RecommendedActionNo action is required.NSM-1018MessageMessage TypeSeverityProbable CauseRecommendedAction VLANs will be allowed on interface .DCEINFOIndicates that the VLAN membership has been changed for the specified interface.No action is required.NSM-1019MessageMessage TypeSeverityProbable CauseRecommendedActionInterface is administratively up.DCEINFOIndicates that the interface administrative status has changed to up.No action is required.NSM-1020MessageMessage TypeSeverityProbable CauseRecommendedActionInterface is administratively down.DCEINFOIndicates that the interface administrative status has changed to down.No action is required.260 Network OS Message Reference53-1002807-01

NSM-1021 7NSM-1021MessageMessage TypeSeverityProbable CauseRecommendedActionInterface IP overlap with management IP ifname:.DCEERRORIndicates that the IP address configured on the interface overlaps with the management IP address.Change the interface IP address using the ip address command.NSM-1022MessageMessage TypeSeverityProbable CauseRecommendedActionFCoE configuration has been on interface .DCEINFOIndicates that the Fibre Channel over Ethernet (FCoE) configuration has been enabled or disabled on thespecified interface.No action is required.NSM-1023MessageMessage TypeSeverityProbable CauseRecommendedActionRBridge ID has joined Port-channel . Port-channel is avLAG with RBridge IDs .DCEINFOIndicates that the specified RBridge has joined the virtual link aggregation group (vLAG).No action is required.Network OS Message Reference 26153-1002807-01

7NSM-1024NSM-1024MessageMessage TypeSeverityProbable CauseRecommendedActionRBridge ID has left Port-channel . Port-channel is avLAG with RBridge IDs .DCEINFOIndicates that the specified RBridge has left the virtual link aggregation group (vLAG).No action is required.NSM-1025MessageMessage TypeSeverityProbable CauseRecommendedActionRBridge ID has left Port-channel . Port-channel hasonly RBridge ID and is no longer a vLAG.DCEINFOIndicates that the virtual link aggregation group (vLAG) no longer exists.No action is required.NSM-1026MessageMessage TypeSeverityProbable CauseRecommendedActionSFP transceiver for interface is inserted.DCEINFOIndicates that a small form-factor pluggable (SFP) transceiver has been inserted in the specifiedinterface.No action is required.262 Network OS Message Reference53-1002807-01

NSM-1027 7NSM-1027MessageMessage TypeSeverityProbable CauseRecommendedActionSFP transceiver for interface is removed.DCEINFOIndicates that a small form-factor pluggable (SFP) transceiver has been removed from the specifiedinterface.No action is required.NSM-1028MessageMessage TypeSeverityProbable CauseRecommendedActionIncompatible SFP transceiver for interface is detected.DCEERRORIndicates that an incompatible small form-factor pluggable (SFP) transceiver for the interface has beeninserted.Disable the interface using the shutdown command and insert an SFP transceiver that is supported onthe interface. After the SFP transceiver is inserted, re-enable the interface using the no shutdowncommand.NSM-1029MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to read SFP transceiver for interface .DCEERRORIndicates failure to read the small form-factor pluggable (SFP) transceiver for the specified interface.Disable the interface using the shutdown command and re-insert the SFP transceiver. After the SFPtransceiver is inserted, re-enable the interface using the no shutdown command. If the problem persists,contact your switch service provider.Network OS Message Reference 26353-1002807-01

7NSM-1030NSM-1030MessageMessage TypeSeverityProbable CauseRecommendedActionInterface is administratively down due to speed mismatch inport-channel.DCEINFOIndicates that the specified interface has gone down due to mismatching speed in the port-channel.Set the correct speed for the interface using the speed command.NSM-1031MessageMessage TypeSeverityProbable CauseRecommendedActionSession is created.DCEINFOIndicates that the specified session has been created.No action is required.NSM-1032MessageMessage TypeSeverityProbable CauseRecommendedActionSession is deleted.DCEINFOIndicates that the specified session has been deleted.No action is required.NSM-1033MessageMessage TypeSeverityProbable CauseSession configuration is deleted.DCEINFOIndicates that the specified session configuration has been deleted.264 Network OS Message Reference53-1002807-01

NSM-1034 7RecommendedActionNo action is required.NSM-1034MessageMessage TypeSeverityProbable CauseRecommendedActionSession configuration is added.DCEINFOIndicates that the specified session configuration has been added.No action is required.NSM-1035MessageMessage TypeSeverityProbable CauseRecommendedActionDescription for Session is added.DCEINFOIndicates that the session description has been added.No action is required.NSM-1036MessageMessage TypeSeverityProbable CauseRecommendedActionDescription for Session is deleted.DCEINFOIndicates that the session description has been deleted.No action is required.Network OS Message Reference 26553-1002807-01

7NSM-1037NSM-1037MessageMessage TypeSeverityProbable CauseRecommendedActionInterface is administratively down due to 1Gbps link configured onBrocade Trunk.DCEINFOIndicates that the specified interface has gone down because a 1 Gbps link has been configured on theBrocade trunk.Remove the 1 Gbps link from the Brocade trunk or change the 1 Gbps small form-factor pluggable (SFP)transceiver.NSM-1038MessageMessage TypeSeverityProbable CauseRecommendedActionUnsupported Brocade-branded SFP transceiver for interface isdetected.DCEERRORIndicates that an unsupported Brocade-branded small form-factor pluggable (SFP) transceiver for theinterface has been inserted.Use a Brocade-branded SFP transceiver for the interface because the digital diagnostics will not besupported.NSM-2000MessageMessage TypeSeverityProbable CauseRecommendedActionPort-profile activation succeeded.DCEINFOIndicates that the profile activation was successful.No action is required.266 Network OS Message Reference53-1002807-01

NSM-2001 7NSM-2001MessageMessage TypeSeverityProbable CauseRecommendedActionPort-profile activation failed, reason .DCEERRORIndicates that the profile activation was unsuccessful.Check the configuration and port-profile status using the show port-profile status command. Executethe copy support command and contact your switch service provider.NSM-2002MessageMessage TypeSeverityProbable CauseRecommendedActionPort-profile deactivation succeeded.DCEINFOIndicates that the profile deactivation was successful.No action is required.NSM-2003MessageMessage TypeSeverityProbable CauseRecommendedActionPort-profile deactivation failed, reason DCEERRORIndicates that the profile deactivation was unsuccessful.Check the configuration and port-profile status using the show port-profile status command. Executethe copy support command and contact your switch service provider.NSM-2004MessageMessage TypeSeverityProbable CausePort-profile application succeeded on .DCEINFOIndicates that the profile application was successful.Network OS Message Reference 26753-1002807-01

7NSM-2005RecommendedActionNo action is required.NSM-2005MessageMessage TypeSeverityProbable CauseRecommendedActionPort-profile application failed on , reason, removing any applied configuration.DCEERRORIndicates that the profile application on the specified interface was unsuccessful.Check the configuration and port-profile status using the show port-profile status command. Executethe copy support command and contact your switch service provider.NSM-2006MessageMessage TypeSeverityProbable CauseRecommendedActionPort-profile removed successfully on .DCEINFOIndicates that the specified port-profile has been removed successfully.No action is required.NSM-2007MessageMessage TypeSeverityProbable CauseRecommendedActionInterface became port-profile-port.DCEINFOIndicates that the port-profile configuration mode has been enabled on the specified interface using theport-profile-port command.No action is required.268 Network OS Message Reference53-1002807-01

NSM-2008 7NSM-2008MessageMessage TypeSeverityProbable CauseRecommendedActionInterface became non-port-profile-port.DCEINFOIndicates that the port-profile configuration mode has been disabled on the specified interface using theno port-profile-port command.No action is required.NSM-2010MessageMessage TypeSeverityProbable CauseRecommendedActionInterface could not become non-port-profile-port.DCEERRORIndicates that the port-profile configuration mode could not be disabled on the specified interface usingthe no port-profile-port command.Check the configuration and port-profile status using the show port-profile status command. Executethe copy support command and contact your switch service provider.NSM-2011MessageMessage TypeSeverityProbable CauseRecommendedActionPort-profile removal failed on .DCEERRORIndicates that the specified port-profile could not be removed.Execute the copy support command and contact your switch service provider.Network OS Message Reference 26953-1002807-01

7NSM-2012NSM-2012MessageMessage TypeSeverityProbable CauseRecommendedActionMAC is associated to port-profile .DCEINFOIndicates successful association of the virtual machine (VM) media access control (MAC) address withthe specified port-profile.No action is required.NSM-2013MessageMessage TypeSeverityProbable CauseRecommendedActionMAC is disassociated from port-profile .DCEINFOIndicates successful disassociation of the virtual machine (VM) media access control (MAC) addressfrom the specified port-profile.No action is required.NSM-2014MessageMessage TypeSeverityProbable CauseRecommendedActionVLAN sub-profile for port-profile is created.DCEINFOIndicates that the VLAN sub-profile has been created successfully.No action is required.270 Network OS Message Reference53-1002807-01

NSM-2015 7NSM-2015MessageMessage TypeSeverityProbable CauseRecommendedActionAccess VLAN is configured for port-profile .DCEINFOIndicates that the untagged VLAN has been configured for the specified port-profile.No action is required.NSM-2016MessageMessage TypeSeverityProbable CauseRecommendedActionAccess VLAN is deleted from port-profile .DCEINFOIndicates that the untagged VLAN has been removed from the specified port-profile.No action is required.NSM-2017MessageMessage TypeSeverityProbable CauseRecommendedActionPort-profile is configured for switching properties.DCEINFOIndicates that the switching properties have been configured on the specified port-profile using theswitchport command.No action is required.Network OS Message Reference 27153-1002807-01

7NSM-2018NSM-2018MessageMessage TypeSeverityProbable CauseRecommendedActionSwitching properties are removed for port-profile .DCEINFOIndicates that the switching properties have been removed from the specified port-profile using the noswitchport command.No action is required.NSM-2019MessageMessage TypeSeverityProbable CauseRecommendedActionThe mode is configured for port-profile .DCEINFOIndicates that the specified mode has been configured for the port-profile using the switchport modecommand.No action is required.NSM-2020MessageMessage TypeSeverityProbable CauseRecommendedActionThe mode is de-configured for port-profile .DCEINFOIndicates that the specified mode has been removed for the port-profile using the switchport modecommand.No action is required.272 Network OS Message Reference53-1002807-01

NSM-2021 7NSM-2021MessageMessage TypeSeverityProbable CauseRecommendedActionThe tagged VLANs are configured for port-profile .DCEINFOIndicates that the specified tagged VLANs are configured in the VLAN sub-profile.No action is required.NSM-2022MessageMessage TypeSeverityProbable CauseRecommendedActionThe tagged VLANs are removed for port-profile .DCEINFOIndicates that the specified tagged VLANs have been removed from the VLAN sub-profile.No action is required.NSM-2023MessageMessage TypeSeverityProbable CauseRecommendedActionThe tagged VLANs except are configured for port-profile.DCEINFOIndicates that except the specified tagged VLANs, all other tagged VLANs are configured in the VLANsub-profile.No action is required.Network OS Message Reference 27353-1002807-01

7NSM-2024NSM-2024MessageMessage TypeSeverityProbable CauseRecommendedActionAll VLANs are configured as tagged VLANs for port-profile .DCEINFOIndicates that all the available tagged VLANs are configured in the specified VLAN sub-profile.No action is required.NSM-2025MessageMessage TypeSeverityProbable CauseRecommendedActionAll tagged VLANs are removed for port-profile .DCEINFOIndicates that all the available tagged VLANs have been from the specified VLAN sub-profile.No action is required.NSM-2026MessageMessage TypeSeverityProbable CauseRecommendedActionNative VLAN is configured to port-profile .DCEINFOIndicates that the native VLAN has been configured for the specified port-profile.No action is required.NSM-2027MessageMessage TypeSeverityProbable CauseNative VLAN is deleted from port-profile .DCEINFOIndicates that the native VLAN has been removed from the specified port-profile.274 Network OS Message Reference53-1002807-01

NSM-2028 7RecommendedActionNo action is required.NSM-2028MessageMessage TypeSeverityProbable CauseRecommendedActionFCoE sub-profile for port-profile is created.DCEINFOIndicates that the Fibre Channel over Ethernet (FCoE) sub-profile has been created for the specifiedport-profile.No action is required.NSM-2029MessageMessage TypeSeverityProbable CauseRecommendedActionFCoE port is configured successfully for port-profile .DCEINFOIndicates that the Fibre Channel over Ethernet (FCoE) port has been configured for the specifiedport-profile.No action is required.NSM-2030MessageMessage TypeSeverityProbable CauseRecommendedActionFCoE port is removed successfully for port-profile .DCEINFOIndicates that the Fibre Channel over Ethernet (FCoE) port has been removed from the specifiedport-profile.No action is required.Network OS Message Reference 27553-1002807-01

7NSM-2031NSM-2031MessageMessage TypeSeverityProbable CauseRecommendedActionPort-profile is created.DCEINFOIndicates that the specified port-profile has been created successfully.No action is required.NSM-2032MessageMessage TypeSeverityProbable CauseRecommendedActionPort-profile is removed.DCEINFOIndicates that the specified port-profile has been removed successfully.No action is required.NSM-2033MessageMessage TypeSeverityProbable CauseRecommendedActionVLAN sub-profile for port-profile is deleted.DCEINFOIndicates that the VLAN sub-profile has been deleted successfully.No action is required.NSM-2034MessageMessage TypeSeverityProbable CauseFCoE sub-profile for port-profile is deleted.DCEINFOIndicates that the Fibre Channel over Ethernet (FCoE) sub-profile has been deleted successfully.276 Network OS Message Reference53-1002807-01

NSM-2035 7RecommendedActionNo action is required.NSM-2035MessageMessage TypeSeverityProbable CauseRecommendedActionNon-profiled-macs on profiled ports will be .DCEINFOIndicates that the non-profiled media access control (MAC) entries on the profiled port will be allowed ordropped.No action is required.NSM-2036MessageMessage TypeSeverityProbable CauseRecommendedActionAssociation of MAC address: failed. Reason : .DCEERRORIndicates that an error occurred during port-profile to media access control (MAC) association.Check the configuration and port-profile status using the show port-profile status command. Executethe copy support command and contact your switch service provider.Network OS Message Reference 27753-1002807-01

7ONMD-1000ONMD MessagesONMD-1000MessageMessage TypeSeverityProbable CauseRecommendedActionLLDP is enabled.DCEINFOIndicates that the link layer discovery protocol (LLDP) is enabled globally.No action is required.ONMD-1001MessageMessage TypeSeverityProbable CauseRecommendedActionLLDP is disabled.DCEINFOIndicates that the link layer discovery protocol (LLDP) is disabled globally.No action is required.ONMD-1002MessageMessage TypeSeverityProbable CauseRecommendedActionLLDP global configuration is changed.DCEINFOIndicates that the link layer discovery protocol (LLDP) global configuration has been changed.No action is required.278 Network OS Message Reference53-1002807-01

ONMD-1003 7ONMD-1003MessageMessage TypeSeverityProbable CauseRecommendedActionLLDP is enabled on interface .DCEINFOIndicates that the link layer discovery protocol (LLDP) is enabled on the specified interface.No action is required.ONMD-1004MessageMessage TypeSeverityProbable CauseRecommendedActionLLDP is disabled on interface .DCEINFOIndicates that the link layer discovery protocol (LLDP) is disabled on the specified interface.No action is required.ONMD-1005MessageMessage TypeSeverityProbable CauseRecommendedActionFeature Mismatch: , will re-negotiate.DCEINFOIndicates that the content of the specified feature does not match with the link partner.Change the feature setting at both ends of the link to match.Network OS Message Reference 27953-1002807-01

7OSPF-1001OSPF MessagesOSPF-1001MessageMessage TypeSeverityProbable CauseRecommendedAction.DCEERRORIndicates a configuration error.Make sure to input or pass the right parameter through CLI or other daemon.OSPF-1002MessageMessage TypeSeverityProbable CauseRecommendedAction.DCEINFOIndicates an open shortest path first (OSPF) interface state change or external link-state database(LSDB) overflow notification.No action is required.OSPF-1003MessageMessage TypeSeverityProbable CauseRecommendedAction.DCEERRORIndicates that the length, format, or content of the received packet is incorrect.Check configuration at the local or remote node.280 Network OS Message Reference53-1002807-01

PDM-1001 7PDM MessagesPDM-1001MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to parse the pdm config.LOGWARNINGIndicates that the parity data manager (PDM) process could not parse the configuration file. This may becaused due to a missing configuration file during the installation.Execute the firmware download command to reinstall the firmware.If the message persists, execute the copy support command and contact your switch service provider.PDM-1003MessageMessage TypeSeverityProbable CauseRecommendedActionpdm [-d] -S -s .LOGWARNINGIndicates that a syntax error occurred when trying to launch the parity data manager (PDM) process.Execute the firmware download command to reinstall the firmware.If the message persists, execute the copy support command and contact your switch service provider.PDM-1004MessageMessage TypeSeverityProbable CauseRecommendedActionPDM memory shortage.LOGWARNINGIndicates that the parity data manager (PDM) process ran out of memory.Restart or power cycle the switch.If the message persists, execute the copy support command and contact your switch service provider.Network OS Message Reference 28153-1002807-01

7PDM-1006PDM-1006MessageMessage TypeSeverityProbable CauseRecommendedActionToo many files in sync.conf.LOGWARNINGIndicates that the configuration file sync.conf contains too many entries.Execute the firmware download command to reinstall the firmware.If the message persists, execute the copy support command and contact your switch service provider.PDM-1007MessageMessage TypeSeverityProbable CauseRecommendedActionFile not created: . errno=.LOGWARNINGIndicates that the parity data manager (PDM) process failed to create the specified file.Execute the firmware download command to reinstall the firmware.If the message persists, execute the copy support command and contact your switch service provider.PDM-1009MessageMessage TypeSeverityProbable CauseRecommendedActionCannot update Port Config Data.LOGWARNINGIndicates that the parity data manager (PDM) system call for setting port configuration (setCfg) failed.Execute the firmware download command to reinstall the firmware.If the message persists, execute the copy support command and contact your switch service provider.PDM-1010MessageMessage TypeSeverityProbable CauseFile open failed: , errno=.LOGWARNINGIndicates that the parity data manager (PDM) process could not open the specified file.282 Network OS Message Reference53-1002807-01

PDM-1011 7RecommendedActionExecute the firmware download command to reinstall the firmware.If the message persists, execute the copy support command and contact your switch service provider.PDM-1011MessageMessage TypeSeverityProbable CauseRecommendedActionFile read failed: , Length (read=,expected=), errno=.LOGWARNINGIndicates that the parity data manager (PDM) process could not read data from the specified file.Execute the firmware download command to reinstall the firmware.If the message persists, execute the copy support command and contact your switch service provider.PDM-1012MessageMessage TypeSeverityProbable CauseRecommendedActionFile write failed: . Length (read=,write=), errno=.LOGWARNINGIndicates that the parity data manager (PDM) process could not write data to the specified file.Execute the firmware download command to reinstall the firmware.If the message persists, execute the copy support command and contact your switch service provider.PDM-1013MessageMessage TypeSeverityProbable CauseRecommendedActionFile empty: .LOGWARNINGIndicates that the switch configuration file /etc/fabos/fabos.[0|1].conf is empty.Execute the firmware download command to reinstall the firmware.If the message persists, execute the copy support command and contact your switch service provider.Network OS Message Reference 28353-1002807-01

7PDM-1014PDM-1014MessageMessage TypeSeverityProbable CauseRecommendedActionAccess sysmod failed.LOGWARNINGIndicates that a system call to sysMod failed.Execute the firmware download command to reinstall the firmware.If the message persists, execute the copy support command and contact your switch service provider.PDM-1017MessageMessage TypeSeverityProbable CauseRecommendedActionSystem (): .FFDC | LOGCRITICALIndicates that the specified system call failed.Execute the firmware download command to reinstall the firmware.If the message persists, execute the copy support command and contact your switch service provider.PDM-1019MessageMessage TypeSeverityProbable CauseRecommendedActionFile path or trigger is too long.LOGWARNINGIndicates that a line in the pdm.conf file is too long.Execute the firmware download command to reinstall the firmware.If the message persists, execute the copy support command and contact your switch service provider.PDM-1021MessageMessage TypeSeverityProbable CauseFailed to download area port map.LOGWARNINGIndicates that a system call failed.284 Network OS Message Reference53-1002807-01

PDM-1021 7RecommendedActionExecute the firmware download command to reinstall the firmware.If the message persists, execute the copy support command and contact your switch service provider.Network OS Message Reference 28553-1002807-01

7PHP-1001PHP MessagesPHP-1001MessageMessage TypeSeverityProbable CauseRecommendedAction.LOGINFOIndicates a user-defined informative message.No action is required.PHP-1002MessageMessage TypeSeverityProbable CauseRecommendedAction.LOGWARNINGIndicates a user-defined warning message.No action is required.PHP-1003MessageMessage TypeSeverityProbable CauseRecommendedAction.LOGERRORIndicates a user-defined error message.No action is required.286 Network OS Message Reference53-1002807-01

PHP-1004 7PHP-1004MessageMessage TypeSeverityProbable CauseRecommendedAction.LOGCRITICALIndicates a user-defined critical message.No action is required.Network OS Message Reference 28753-1002807-01

7PLAT-1000PLAT MessagesPLAT-1000MessageMessage TypeSeverityProbable CauseRecommendedAction .FFDC | LOGCRITICALIndicates that nonrecoverable peripheral component interconnect (PCI) errors have been detected.The system will be faulted and may reload automatically.If the system does not reload, execute the reload command.Execute the copy support command and contact your switch service provider.PLAT-1001MessageMessage TypeSeverityProbable CauseRecommendedActionMM resetting other MM (doublereset may occur).LOGINFOIndicates that the other management module is being reset. This message is typically generated by amanagement module that is in the process of becoming the active management module. Note that incertain circumstances a management module may experience a double reset and reload twice. Amanagement module can recover automatically even if it has reloaded twice.No action is required.PLAT-1002MessageMessage TypeSeverityProbable CauseRecommendedActionMM: hk_fence 0x mm_ha0x mm_status 0x.LOGCRITICALIndicates that one of the management modules cannot access the inter-integrated circuit (I2C)subsystem because of an error condition or being isolated from the I2C bus.Reload the management module if it does not reload automatically. Reseat the management module ifreloading does not solve the problem. If the problem persists, replace the management module.288 Network OS Message Reference53-1002807-01

PLAT-1004 7PLAT-1004MessageMessage TypeSeverityProbable CauseRecommendedActionTurning off Fan because of airflow direction mismatch.LOG | FFDCCRITICALIndicates that the specified fan field-replaceable unit (FRU) has been turned off because it isincompatible with the system airflow direction policy.Replace the fan FRU. Refer to the Hardware Reference Manual of your switch for instructions to replacethe fan FRU.PLAT-1005MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to read EEPROM for Global airflow direction. Setting to default Port sideintake.LOG | FFDCCRITICALIndicates a failure to read the electrically erasable programmable read-only memory (EEPROM) todetermine the airflow direction of the fans. Therefore, setting the airflow direction to be from the port sideof the system.Execute the copy support command and contact your switch service provider.PLAT-1006MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to read EEPROM for Global airflow direction. Shutting off Fans now.LOGCRITICALIndicates a failure to read the electrically erasable programmable read-only memory (EEPROM) todetermine the airflow direction of the fans. The fans will be shut down.Execute the copy support command and contact your switch service provider.Network OS Message Reference 28953-1002807-01

7PLAT-1007PLAT-1007MessageMessage TypeSeverityProbable CauseRecommendedActionTurning off Fan because of airflow direction .LOGERRORIndicates that the specified fan is turned off because of an incorrect airflow direction.Replace the fan field-replaceable units (FRUs) in such a manner that the air flows in the same direction,that is, towards the port side or away from the port side of the system. Refer to the Hardware ReferenceManual of your switch for instructions to replace the fan FRU.PLAT-1008MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to read EEPROM for Global airflow direction.LOGERRORIndicates a failure to read the electrically erasable programmable read-only memory (EEPROM) andtherefore unable to determine the global airflow direction of the fans.Execute the copy support command and contact your switch service provider.PLAT-1009MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to read EEPROM Valid Signature for Global airflow direction.LOGERRORIndicates that the content read from electrically erasable programmable read-only memory (EEPROM) isinvalid and therefore unable to determine the global airflow direction of the fans.Execute the copy support command and contact your switch service provider.290 Network OS Message Reference53-1002807-01

PORT-1003 7PORT MessagesPORT-1003MessageMessage TypeSeverityProbable CauseRecommendedActionPort Faulted because of many Link Failures.LOGWARNINGIndicates that the specified port is disabled because of multiple link failures on the port that haveexceeded the threshold internally set on the port. This problem is related to the hardware.Check and replace (if necessary) the hardware attached to both the ends of the specified port, including:• The small form-factor pluggable (SFP)• The cable (fiber-optic or copper inter-switch link (ISL))• The attached devicesAfter checking the hardware, execute the no shutdown command to re-enable the port.PORT-1004MessageMessage TypeSeverityProbable CauseRecommendedActionPort (0x) could not be enabled because it isdisabled due to long distance.LOGINFOIndicates that the specified port cannot be enabled because other ports in the same group have used thebuffers of this port group. This happens when other ports are configured to be long distance.To enable the specified port, perform one of the following actions:• Reconfigure the other E_Ports so that they are not long distance.• Change the other E_Ports so that they are not E_Ports.This will free some buffers and allow the port to be enabled.PORT-1011MessageMessage TypeSeverityProbable CauseAn SFP transceiver for interface Fibre Channel // is removed.LOGINFOIndicates that a small form-factor pluggable (SFP) transceiver has been removed from the specified port.Network OS Message Reference 29153-1002807-01

7PORT-1012RecommendedActionNo action is required.PORT-1012MessageMessage TypeSeverityProbable CauseRecommendedActionAn SFP transceiver for interface Fibre Channel // is inserted.LOGINFOIndicates that a small form-factor pluggable (SFP) transceiver has been inserted into the specified port.No action is required.PORT-1013MessageMessage TypeSeverityProbable CauseRecommendedActionAn incompatible SFP transceiver for interface Fibre Channel // is inserted.LOGINFOIndicates that an incompatible small form-factor pluggable (SFP) transceiver has been inserted into thespecified port.No action is required.PORT-1014MessageMessage TypeSeverityProbable CauseRecommendedActionInterface fibrechannel // is online.LOGINFOIndicates that the interface is online after the protocol dependencies are resolved.No action is required.292 Network OS Message Reference53-1002807-01

PORT-1015 7PORT-1015MessageMessage TypeSeverityProbable CauseRecommendedActionInterface fibrechannel // is linkdown.LOGINFOIndicates that the fibre channel interface is offline because the link is down.Check whether the connectivity is proper and the remote link is up.PORT-1016MessageMessage TypeSeverityProbable CauseRecommendedActionInterface fibrechannel // isadministratively up.LOGINFOIndicates that the fibre channel interface administrative status has changed to up.No action is required.PORT-1017MessageMessage TypeSeverityProbable CauseRecommendedActionInterface fibrechannel // isadministratively down.LOGINFOIndicates that the interface administrative status has changed to down.No action is required.Network OS Message Reference 29353-1002807-01

7RAS-1001RAS MessagesRAS-1001MessageMessage TypeSeverityProbable CauseRecommendedActionFirst failure data capture (FFDC) event occurred.LOGINFOIndicates that a first failure data capture (FFDC) event occurred and the failure data has been captured.Execute the copy support command and contact your switch service provider.RAS-1002MessageMessage TypeSeverityProbable CauseRecommendedActionFirst failure data capture (FFDC) reached maximum storage size (MB).LOGWARNINGIndicates that the storage size for first failure data capture (FFDC) has reached the maximum.Execute the copy support command and contact your switch service provider.RAS-1004MessageMessage TypeSeverityProbable CauseRecommendedActionSoftware 'verify' error detected.LOG | FFDCWARNINGIndicates an internal software error.Execute the copy support command and contact your switch service provider.294 Network OS Message Reference53-1002807-01

RAS-1005 7RAS-1005MessageMessage TypeSeverityProbable CauseRecommendedActionSoftware 'assert' error detected.LOG | FFDCWARNINGIndicates an internal software error.Execute the copy support command and contact your switch service provider.RAS-1006MessageMessage TypeSeverityProbable CauseRecommendedActionSupport data file () automatically transferred to remoteaddress ' '.LOGINFOIndicates that the support data was automatically transferred from the switch to the configured remoteserver.No action is required.RAS-1007MessageMessage TypeSeverityProbable CauseRecommendedActionSystem is about to reload.LOGINFOIndicates that the system reload was initiated.No action is required.Network OS Message Reference 29553-1002807-01

7RAS-2001RAS-2001MessageMessage TypeSeverityProbable CauseRecommendedActionAudit message log is enabled.LOGINFOIndicates that the audit message log has been enabled.No action is required.RAS-2002MessageMessage TypeSeverityProbable CauseRecommendedActionAudit message log is disabled.LOGINFOIndicates that the audit message log has been disabled.No action is required.RAS-2003MessageMessage TypeSeverityProbable CauseRecommendedActionAudit message class configuration has been changed to .LOGINFOIndicates that the audit event class configuration has been changed.No action is required.296 Network OS Message Reference53-1002807-01

RAS-2004 7RAS-2004MessageMessage TypeClassSeverityProbable CauseRecommendedActionprom access is enabled.LOG | AUDITSECURITYINFOIndicates that the PROM access has been enabled.No action is required.RAS-2005MessageMessage TypeClassSeverityProbable CauseRecommendedActionprom access is disabled.LOG | AUDITSECURITYINFOIndicates that the PROM access has been disabled.No action is required.RAS-3001MessageMessage TypeSeverityProbable CauseRecommendedActionUSB storage device plug-in detected.LOGINFOIndicates that the USB storage device plug-in has been detected.No action is required.Network OS Message Reference 29753-1002807-01

7RAS-3002RAS-3002MessageMessage TypeSeverityProbable CauseRecommendedActionUSB storage device enabled.LOGINFOIndicates that the USB storage device has been enabled.No action is required.RAS-3003MessageMessage TypeSeverityProbable CauseRecommendedActionUSB storage device was unplugged before it was disabled.LOGWARNINGIndicates that the USB storage device was unplugged before it was disabled.No action is required. It is recommended to disable the USB storage device using the usb off commandbefore unplugged it from the system.RAS-3004MessageMessage TypeSeverityProbable CauseRecommendedActionUSB storage device disabled.LOGINFOIndicates that the USB storage device has been disabled.No action is required.RAS-3005MessageMessage TypeSeverityProbable CauseFile removed from USB storage.LOGINFOIndicates that the specified file or directory has been removed from the USB storage.298 Network OS Message Reference53-1002807-01

RAS-3005 7RecommendedActionNo action is required.Network OS Message Reference 29953-1002807-01

7RCS-1003RCS MessagesRCS-1003MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to allocate memory: ().LOGERRORIndicates that the specified reliable commit service (RCS) function has failed to allocate memory.This message is usually transitory. Wait for a few minutes and retry the command.Check memory usage on the switch using the show process memory command.Reload or power cycle the switch.RCS-1005MessageMessage TypeSeverityProbable CauseRecommendedActionPhase , Application returned ,0x.LOGINFOIndicates that a receiving switch is rejecting the specified reliable commit service (RCS) phase.If the reject is in acquire change authorization (ACA) phase, wait for several minutes and retry theoperation from the sender switch.If the reject is in the stage fabric configuration (SFC) phase, check if the application license exists for thelocal RBridge and if the application data is compatible.RCS-1006MessageMessage TypeSeverityProbable CauseState , Application AD, RCSCM. RBridge returned 0x. AppResponse Code .LOGINFOIndicates that the specified RBridge rejected the reliable commit service (RCS) phase initiated by anapplication on the local switch.• If the reject phase is acquire change authorization (ACA), the remote RBridge may be busy andcould not process the new request.• If the reject phase is stage fabric configuration (SFC), the data sent by the application may not becompatible or the RBridge does not have the license to support the specified application.300 Network OS Message Reference53-1002807-01

RCS-1007 7RecommendedActionIf the reject is in ACA phase, wait for several minutes and then retry operation.If the reject is in the SFC phase, check if the application license exists for the RBridge and if theapplication data is compatible.RCS-1007MessageMessage TypeSeverityProbable CauseRecommendedActionZone DB size and propagation overhead exceeds RBridge 's maximumsupported Zone DB size . Retry after reducing Zone DB size.LOGERRORIndicates that the specified RBridge cannot handle the zone database being committed.Reduce the zone database size by deleting some zones. Refer to the Network OS Administrator's Guidefor instructions to delete a zone.RCS-1008MessageMessage TypeSeverityProbable CauseRecommendedActionRBridge Lowest Max Zone DB size.LOGERRORIndicates that the specified RBridge has the lowest memory available for the zone database in the fabric.The zone database must be smaller than the memory available on this RBridge.Reduce the zone database size by deleting some zones. Refer to the Network OS Administrator's Guidefor instructions to delete a zone.RCS-1010MessageMessage TypeSeverityProbable CauseRecommendedActionRBridge is RCS incapable. Disabled E_port(s) connected to this RBridge.LOGERRORIndicates inability to retrieve RCS-capable information for the specified RBridge due to some potentialrouting issues.Investigate for routing issue or check the cabling, and re-enable the disabled E_ports to attempt anotherexchange of RCS-capable information.Network OS Message Reference 30153-1002807-01

7RCS-1011RCS-1011MessageMessage TypeSeverityProbable CauseRecommendedActionRemote RBridge is RCS incapable. Configure this RBridge as RCScapable.LOGERRORIndicates inability to retrieve RCS-capable information for the specified RBridge due to some potentialrouting issues.Investigate for routing issue or check the cabling, and re-enable the disabled E_ports to attempt anotherexchange of RCS-capable information.302 Network OS Message Reference53-1002807-01

RTM-1001 7RTM MessagesRTM-1001MessageMessage TypeSeverityProbable CauseRecommendedActionInitialization error: .DCEERRORIndicates that the route management (RTM) has encountered an error during initialization.Reload or power cycle the switch.RTM-1002MessageMessage TypeSeverityProbable CauseRecommendedActionMax capacity reached: .DCEERRORIndicates that the route management (RTM) has reached its maximum capacity.Reduce the number of routes or next hops using the clear ip route command.RTM-1003MessageMessage TypeSeverityProbable CauseRecommendedActionStatic Route Update error: .DCEERRORIndicates that an error has occurred in the route management (RTM) during the static route update.Check the static route configuration using the show ip static route command.Network OS Message Reference 30353-1002807-01

7RTM-1005RTM-1005MessageMessage TypeSeverityProbable CauseRecommendedActionProtocol Route update error: .DCEERRORIndicates that an error has occurred in the route management (RTM) during the protocol route update.Check the protocol statistics and configuration.RTM-1022MessageMessage TypeSeverityProbable CauseRecommendedActionClear Route success: .DCEINFOIndicates that IP routes are cleared by the route management (RTM).No action is required.RTM-1023MessageMessage TypeSeverityProbable CauseRecommendedAction.DCEWARNINGIndicates that a route pointing to the management interface is not redistributed to other protocols.No action is required.304 Network OS Message Reference53-1002807-01

RTWR-1001 7RTWR MessagesRTWR-1001MessageMessage TypeSeverityProbable CauseRecommendedActionRTWR 0x, 0x, 0x, 0x, 0x.LOGERRORIndicates that an error occurred in Reliable Transport Write and Read (RTWR) due to one of the followingreasons:• The system ran out of memory.• The domain may be unreachable.• The frame transmission failed.• An internal error or failure occurred.The message contains the name of the routine that has an error and other error-specific information.Refer to values in details 1 through 5 for more information.Execute the reload command to restart the switch.RTWR-1002MessageMessage TypeSeverityProbable CauseRecommendedActionRTWR 0x, 0x, 0x, 0x, 0x.LOGWARNINGIndicates that Reliable Transport Write and Read (RTWR) has exhausted the maximum number of retriesfor sending data to the specified RBridge.Execute the show fabric all command to verify that the specified RBridge ID is online.If the switch with the specified RBridge ID is offline, enable the switch using the chassis enablecommand.If the message persists, execute the copy support command and contact your switch service provider.Network OS Message Reference 30553-1002807-01

7RTWR-1003RTWR-1003MessageMessage TypeSeverityProbable CauseRecommendedAction: RTWR retry to RBridge ,iu_data .LOGINFOIndicates the number of times Reliable Transport Write and Read (RTWR) has failed to get a responseand retried.Execute the show fabric all command to verify that the specified RBridge ID is reachable.If the message persists, execute the copy support command and contact your switch service provider.306 Network OS Message Reference53-1002807-01

SCN-1001 7SCN MessagesSCN-1001MessageMessage TypeSeverityProbable CauseRecommendedActionSCN queue overflow for process .FFDC | LOGCRITICALIndicates that an attempt to write a state change notification (SCN) message to a specific queue hasfailed because the SCN queue for the specified daemon is full. This may be caused by the daemonhanging or the system being busy.The following are some valid values for the daemon name:• fabricd• asd• evmd• fcpd• webd• msd• nsd• psd• snmpd• zoned• fspfd• tsdIf this message is caused by the system being busy, the condition is temporary.If this message is caused by a hung daemon, the software watchdog will cause the daemon to dump thecore and reload the switch. In this case, execute the copy support ftp command to send the core filesusing FTP to a secure server location.If the message persists, execute the copy support command and contact your switch service provider.Network OS Message Reference 30753-1002807-01

7SEC-1033SEC MessagesSEC-1033MessageMessage TypeSeverityProbable CauseRecommendedActionInvalid character used in member parameter to add switch to SCC policy; commandterminated.LOGERRORIndicates that a member parameter in the secpolicy defined-policy command is invalid (for example, itmay include an invalid character, such as an asterisk). A valid switch identifier (WWN, RBridge ID, orswitch name) must be provided as a member parameter in the secpolicy defined-policy command.Execute the secpolicy defined-policy command using a valid switch identifier (WWN, RBridge ID, orswitch name) to add specific switches to the switch connection control (SCC) policy.SEC-1034MessageMessage TypeSeverityProbable CauseRecommendedActionInvalid member .LOGERRORIndicates that the input list has an invalid member.Verify the member names and input the correct information.SEC-1036MessageMessage TypeSeverityProbable CauseRecommendedActionDevice name is invalid due to a missing colon.LOGERRORIndicates that one or more device names mentioned in the secpolicy defined-policy command does nothave the colon character (:).Execute the secpolicy defined-policy command with a properly formatted device name parameter.308 Network OS Message Reference53-1002807-01

SEC-1037 7SEC-1037MessageMessage TypeSeverityProbable CauseRecommendedActionInvalid WWN format .LOGERRORIndicates that the World Wide Name (WWN) entered in the policy member list had an invalid format.Execute the command again using the standard WWN format, that is, 16 hexadecimal digits grouped aseight colon separated pairs. For example: 50:06:04:81:D6:F3:45:42.SEC-1038MessageMessage TypeSeverityProbable CauseRecommendedActionInvalid domain .LOGERRORIndicates that an invalid RBridge ID was entered.Verify that the RBridge ID is correct. If RBridge ID is not correct, execute the command again using thecorrect RBridge ID.SEC-1044MessageMessage TypeSeverityProbable CauseRecommendedActionDuplicate member in ().LOGERRORIndicates that the specified member is a duplicate in the input list. The list can be a policy list or a switchmember list.Do not specify any duplicate members.SEC-1071MessageMessage TypeSeverityProbable CauseNo new security policy data to apply.LOGERRORIndicates that there are no changes in the defined security policy database to be activated.Network OS Message Reference 30953-1002807-01

7SEC-1180RecommendedActionVerify that the security event was planned. Change some policy definitions and execute the secpolicyactivate command to activate the policies.SEC-1180MessageMessage TypeSeverityProbable CauseRecommendedActionAdded account with authorization.LOGINFOIndicates that the specified new account has been created.No action is required.SEC-1181MessageMessage TypeSeverityProbable CauseRecommendedActionDeleted account LOGINFOIndicates that the specified account has been deleted.No action is required.SEC-1184MessageMessage TypeSeverityProbable CauseRecommendedAction configuration change, action , server ID .LOGINFOIndicates that the specified action is applied to remote AAA (RADIUS/TACACS+) server configuration.The possible actions are ADD, REMOVE, CHANGE, and MOVE.No action is required.310 Network OS Message Reference53-1002807-01

SEC-1185 7SEC-1185MessageMessage TypeSeverityProbable CauseRecommendedAction switch DB.LOGINFOIndicates that the switch database was enabled or disabled as the secondary authentication, accounting,and authorization (AAA) mechanism when the remote authentication dial-in user service (RADIUS) orlightweight directory access protocol (LDAP) is the primary AAA mechanism.No action is required.SEC-1187MessageMessage TypeSeverityProbable CauseRecommendedActionSecurity violation: Unauthorized switch tries to join fabric.LOGINFOIndicates that a switch connection control (SCC) security violation was reported. The specifiedunauthorized switch attempts to join the fabric.Check the switch connection control policy (SCC) policy to verify the switches are allowed in the fabric. Ifthe switch should be allowed in the fabric but it is not included in the SCC policy, add the switch to thepolicy using the secpolicy defined-policy scc_policy member-entry command. If the switch is notallowed access to the fabric, this is a valid violation message and an unauthorized entity is trying toaccess your fabric. Take appropriate action as defined by your enterprise security policy.SEC-1189MessageMessage TypeSeverityProbable CauseRecommendedActionSecurity violation: Unauthorized host with IP address tries to doSNMP write operation.LOGINFOIndicates that a Simple Network Management Protocol (SNMP) security violation was reported. Thespecified unauthorized host attempted to perform an SNMP write operation.Check the WSNMP policy (read/write SNMP policy) and verify which hosts are allowed access to thefabric through SNMP. If the host is allowed access to the fabric but is not included in the policy, add thehost to the policy. If the host is not allowed access to the fabric, this is a valid violation message and anunauthorized entity is trying to access your fabric. Take appropriate action as defined by your enterprisesecurity policy.Network OS Message Reference 31153-1002807-01

7SEC-1190SEC-1190MessageMessage TypeSeverityProbable CauseRecommendedActionSecurity violation: Unauthorized host with IP address tries to doSNMP read operation.LOGINFOIndicates that a Simple Network Management Protocol (SNMP) security violation was reported. Thespecified unauthorized host attempted to perform an SNMP read operation.Check the RSNMP policy (read-only SNMP policy) to verify the hosts that are allowed access to thefabric through SNMP read operations are included in the RSNMP policy. If the host is allowed access butis not included in the RSNMP policy, add the host to the policy. If the host is not allowed access to thefabric, this is a valid violation message and an unauthorized entity is trying to access your fabric. Takeappropriate action as defined by your enterprise security policy.SEC-1191MessageMessage TypeSeverityProbable CauseRecommendedActionSecurity violation: Unauthorized host with IP address tries toestablish HTTP connection.LOGINFOIndicates that a Hypertext Transfer Protocol (HTTP) security violation was reported. The specifiedunauthorized host attempted to establish an HTTP connection.Determine whether the host IP address specified in the message can be used to manage the fabricthrough an HTTP connection. If so, add the host IP address to the HTTP policy of the fabric. If the host isnot allowed access to the fabric, this is a valid violation message and an unauthorized entity is trying toaccess your fabric. Take appropriate action as defined by your enterprise security policy.SEC-1192MessageMessage TypeSeverityProbable CauseRecommendedActionSecurity violation: Login failure attempt via .LOGINFOIndicates that a serial or modem login security violation was reported. An incorrect password was usedwhile trying to log in through a serial or modem connection; the log in failed.Use the correct password.312 Network OS Message Reference53-1002807-01

SEC-1193 7SEC-1193MessageMessage TypeSeverityProbable CauseRecommendedActionSecurity violation: Login failure attempt via . IP Addr: LOGINFOIndicates that a login security violation was reported. The wrong password was used while trying to log inthrough the specified connection method; the log in failed. The violating IP address is displayed in themessage.Verify that the specified IP address is being used by a valid switch administrator. Use the correctpassword.SEC-1197MessageMessage TypeSeverityProbable CauseRecommendedActionChanged account .LOGINFOIndicates that the specified account has changed.No action is required.SEC-1199MessageMessage TypeSeverityProbable CauseRecommendedActionSecurity violation: Unauthorized access to serial port of switch .LOGINFOIndicates that a serial connection policy security violation was reported. An attempt was made to accessthe serial console on the specified switch instance when it is disabled.Check to see if an authorized access attempt was made on the console. If so, add the switch World WideName (WWN) to the serial policy using the secpolicy defined-policy scc_policy member-entrycommand. If the host is not allowed access to the fabric, this is a valid violation message and anunauthorized entity is trying to access your fabric. Take appropriate action as defined by your enterprisesecurity policy.Network OS Message Reference 31353-1002807-01

7SEC-1203SEC-1203MessageMessage TypeSeverityProbable CauseRecommendedActionLogin information: Login successful via TELNET/SSH/RSH. IP Addr: LOGINFOIndicates that the remote log in of the specified IP address was successful.No action is required.SEC-1307MessageMessage TypeSeverityProbable CauseRecommendedAction server authenticated user account''.LOGINFOIndicates that the specified AAA (RADIUS/TACACS+/LDAP) server responded to a switch request aftersome servers timed out.If the message appears frequently, reconfigure the list of servers so that the responding server is the firstserver on the list.SEC-1308MessageMessage TypeSeverityProbable CauseRecommendedActionAll servers failed to authenticate useraccount ''.LOGINFOIndicates that all servers in the remote AAA (RADIUS/TACACS+/LDAP) service configuration have failedto respond to a switch request within the configured timeout period.Verify that the switch has proper network connectivity to the specified AAA (RADIUS/TACACS+/LDAP)servers and the servers are correctly configured.314 Network OS Message Reference53-1002807-01

SEC-1312 7SEC-1312MessageMessage TypeSeverityProbable CauseRecommendedAction.LOGINFOIndicates that the password attributes have been changed.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-1313MessageMessage TypeSeverityProbable CauseRecommendedActionThe password attributes parameters were set to default values.LOGINFOIndicates that the password attributes were set to default values.Verify that the security event was planned. If the security event was planned, no action is required.If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-1325MessageMessage TypeSeverityProbable CauseRecommendedActionSecurity enforcement: Switch connecting to port is notauthorized to stay in fabric.LOGERRORIndicates that the specified switch is being disabled on the specified port because of a switch connectioncontrol (SCC) policy violation.No action is required unless the switch must remain in the fabric. If the switch must remain in the fabric,add the switch World Wide Name (WWN) to the SCC policy using the secpolicy defined-policyscc_policy member-entry command, then attempt to join the switch with the fabric.Network OS Message Reference 31553-1002807-01

7SEC-1329SEC-1329MessageMessage TypeSeverityProbable CauseRecommendedActionIPFilter enforcement:Failed to enforce ipfilter policy of typebecause of .LOGERRORIndicates that the IP filter policy enforcement failed because of an internal system failure.Execute the copy support command and contact your switch service provider.SEC-1334MessageMessage TypeSeverityProbable CauseRecommendedActionlocal security policy .LOGINFOIndicates that the specified event has occurred.Verify that the event was planned. If the event was planned, no action is required. If the event was notplanned, take appropriate action as defined by your enterprise security policy.SEC-1335MessageMessage TypeSeverityProbable CauseRecommendedActionlocal security policy WWN .LOGINFOIndicates that the specified event has occurred.Verify that the event was planned. If the event was planned, no action is required. If the event was notplanned, take appropriate action as defined by your enterprise security policy.SEC-1336MessageMessage TypeSeverityProbable CauseMissing file is replaced with default configuration.LOGINFOIndicates that the specified file is missing and it has been replaced with the default file.316 Network OS Message Reference53-1002807-01

SEC-1337 7RecommendedActionNo action is required.SEC-1337MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to access file and reverted the configuration.LOGINFOIndicates that the specified file was not accessible.No action is required.SEC-3014MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: server for AAA services.AUDITSECURITYINFOIndicates that the AAA (RADIUS/TACACS+) server configuration has been changed manually.Verify that the RADIUS/TACACS+ configuration was changed intentionally. If the RADIU/TACACS+configuration was changed intentionally, no action is required. If the RADIUS/TACACS+ configurationwas not changed intentionally, take appropriate action as defined by your enterprise security policy.SEC-3016MessageMessage TypeClassSeverityProbable CauseEvent: , Status: success, Info: Attribute [] of server changed .AUDITSECURITYINFOIndicates that the specified attribute of the remote AAA (RADIUS/TACACS+) server has been changedmanually.Network OS Message Reference 31753-1002807-01

7SEC-3017RecommendedActionVerify that the attribute was changed intentionally. If the attribute was changed intentionally, no action isrequired. If the attribute was not changed intentionally, take appropriate action as defined by yourenterprise security policy.SEC-3017MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: .AUDITSECURITYINFOIndicates that the remote authentication dial-in user service (RADIUS) or lightweight directory accessprotocol (LDAP) configuration has been changed manually.Verify that the RADIUS or LDAP configuration was changed intentionally. If the RADIUS or LDAPconfiguration was changed intentionally, no action is required. If the RADIUS or LDAP configuration wasnot changed intentionally, take appropriate action as defined by your enterprise security policy.SEC-3018MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: Parameter [] changedfrom [] to [].AUDITSECURITYINFOIndicates that the specified password attribute has been changed.Verify that the password attribute was changed intentionally. If the password attribute was changedintentionally, no action is required. If the password attribute was not changed intentionally, takeappropriate action as defined by your enterprise security policy.SEC-3019MessageMessage TypeClassSeverityProbable CauseEvent: , Status: success, Info: Password attributes set to defaultvalues.AUDITSECURITYINFOIndicates that the password attributes are set to default values.318 Network OS Message Reference53-1002807-01

SEC-3020 7RecommendedActionVerify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3020MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: Successful login attempt via.AUDITSECURITYINFOIndicates that the log in was successful. An IP address is displayed when the login occurs over a remoteconnection.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3021MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: failed, Info: Failed login attempt through.AUDITSECURITYINFOIndicates that the log in attempt has failed.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3022MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: Successful logout by user [].AUDITSECURITYINFOIndicates that the specified user has successfully logged out.No action is required.Network OS Message Reference 31953-1002807-01

7SEC-3023SEC-3023MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: failed, Info: Account [] locked, failedpassword attempts exceeded.AUDITSECURITYINFOIndicates that the number of failed log in attempts due to incorrect password has exceeded the allowedlimit; the account has been locked.The administrator can manually unlock the account.SEC-3024MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: User account [], passwordchanged.AUDITSECURITYINFOIndicates that the password was changed for the specified user.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3025MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: User account [] added.Role: [], Password [], Home Context [], AD/VF list [].AUDITSECURITYINFOIndicates that a new user account was created.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.320 Network OS Message Reference53-1002807-01

SEC-3026 7SEC-3026MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: User account [], rolechanged from [] to [].AUDITSECURITYINFOIndicates that the user account role has been changed.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3027MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: User account [] [].AUDITSECURITYINFOIndicates that the user account properties were changed.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3028MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: User account [] deleted.AUDITSECURITYINFOIndicates that the specified user account has been deleted.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.Network OS Message Reference 32153-1002807-01

7SEC-3030SEC-3030MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: .AUDITSECURITYINFOIndicates that the certificate authority (CA) certificate was imported successfully using the certutil importldapca command.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3034MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: AAA Authentication Login Mode Configuration, Status: success, Info:Authentication configuration changed from to .AUDITSECURITYINFOIndicates that the authentication configuration has been changed.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3035MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: ipfilter, Status: success, Info: ipfilter policy(ies)saved.AUDIT | LOGSECURITYINFOIndicates that the specified IP filter policies have been saved.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.322 Network OS Message Reference53-1002807-01

SEC-3036 7SEC-3036MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: ipfilter, Status: failed, Info: Failed to save changes for ipfilter policy(s).AUDIT | LOGSECURITYINFOIndicates that the specified IP filter policies have not been saved.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3037MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: ipfilter, Status: success, Info: ipfilter policyactivated.AUDIT | LOGSECURITYINFOIndicates that the specified IP filter policy has been activated.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3038MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: ipfilter, Status: failed, Info: Failed to activate ipfilter policy.AUDIT | LOGSECURITYINFOIndicates that the specified IP filter policy failed to activate.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.Network OS Message Reference 32353-1002807-01

7SEC-3039SEC-3039MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent:Security Violation , Status: failed, Info: Unauthorized host with IP address tries to establish connection using .AUDIT | LOGSECURITYINFOIndicates that a security violation was reported. The IP address of the unauthorized host is displayed inthe message.Check for unauthorized access to the switch through the specified protocol connection.SEC-3045MessageMessage TypeClassSeverityProbable CauseRecommendedActionZeroization has been executed on the system.AUDITSECURITYINFOIndicates that the system has been zeroized.Verify the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3046MessageMessage TypeClassSeverityProbable CauseRecommendedActionThe FIPS Self Tests mode has been set to .AUDITSECURITYINFOIndicates that there was a change in the Federal Information Protection Standard (FIPS) self test mode.Verify the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.324 Network OS Message Reference53-1002807-01

SEC-3049 7SEC-3049MessageMessage TypeClassSeverityProbable CauseRecommendedActionStatus of bootprom access is changed using prom-access disable CLI: .AUDITSECURITYINFOIndicates that the status of Boot PROM has changed using prom-access disable command. By default,the Boot PROM is accessible.No action is required.SEC-3051MessageMessage TypeClassSeverityProbable CauseRecommendedActionThe license key is .AUDIT | LOGSECURITYINFOIndicates that the specified license key has been added or removed.No action is required.SEC-3061MessageMessage TypeClassSeverityProbable CauseRecommendedActionRole '' is created.AUDIT | LOGSECURITYINFOIndicates that the specified role has been created.No action is required.Network OS Message Reference 32553-1002807-01

7SEC-3062SEC-3062MessageMessage TypeClassSeverityProbable CauseRecommendedActionRole '' is deleted.AUDIT | LOGSECURITYINFOIndicates that the specified role has been deleted.No action is required.SEC-3067MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: Telnet Server is shutdown.AUDITSECURITYINFOIndicates that the Telnet server in the switch is shut down.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3068MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: Telnet Server is started.AUDITSECURITYINFOIndicates that the Telnet server in the switch is started.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.326 Network OS Message Reference53-1002807-01

SEC-3069 7SEC-3069MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: SSH Server is shutdown.AUDITSECURITYINFOIndicates that the SSH server in the switch is shut down.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3070MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: SSH Server is started.AUDITSECURITYINFOIndicates that the SSH server in the switch is started.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3071MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: SSH Server Key Exchange Algorithm isconfigured to DH Group 14.AUDITSECURITYINFOIndicates that the SSH server in the switch is started.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.Network OS Message Reference 32753-1002807-01

7SEC-3072SEC-3072MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: SSH Server Key Exchange Algorithm isrestored to default.AUDITSECURITYINFOIndicates that the SSH server in the switch is started.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3073MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: Login banner message is set to''.AUDITSECURITYINFOIndicates that the login banner message is set.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3074MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: Login banner message is removed.AUDITSECURITYINFOIndicates that the login banner message is removed.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.328 Network OS Message Reference53-1002807-01

SEC-3075 7SEC-3075MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: '' cipher list is configured.AUDITSECURITYINFOIndicates that the specified LDAP or SSH cipher list is configured.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3076MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: , Status: success, Info: '' cipher list is removed.AUDITSECURITYINFOIndicates that the specified LDAP or SSH cipher list is removed.Verify that the security event was planned. If the security event was planned, no action is required. If thesecurity event was not planned, take appropriate action as defined by your enterprise security policy.SEC-3501MessageMessage TypeClassSeverityProbable CauseRecommendedActionRole '' is changed.AUDIT | LOGSECURITYINFOIndicates that attributes of the specified role have been changed.No action is required.Network OS Message Reference 32953-1002807-01

7SFLO-1001SFLO MessagesSFLO-1001MessageMessage TypeSeverityProbable CauseRecommendedActionsFlow is globally.DCEINFOIndicates that sFlow is enabled or disabled globally.No action is required.SFLO-1002MessageMessage TypeSeverityProbable CauseRecommendedActionsFlow is for port .DCEINFOIndicates that sFlow is enabled or disabled on the specified port.No action is required.SFLO-1003MessageMessage TypeSeverityProbable CauseRecommendedActionGlobal sFlow sampling rate is changed to .DCEINFOIndicates that the global sFlow sampling rate has been changed to the specified value.No action is required.330 Network OS Message Reference53-1002807-01

SFLO-1004 7SFLO-1004MessageMessage TypeSeverityProbable CauseRecommendedActionGlobal sFlow polling interval is changed to .DCEINFOIndicates that the global counter sampling interval has been changed to the specified value.No action is required.SFLO-1005MessageMessage TypeSeverityProbable CauseRecommendedActionsFlow sampling rate on port is changed to .DCEINFOIndicates that the sFlow sampling rate has been changed on the specified port.No action is required.SFLO-1006MessageMessage TypeSeverityProbable CauseRecommendedActionsFlow polling interval on port is changed to .DCEINFOIndicates that the sFlow polling interval has been changed on the specified port.No action is required.SFLO-1007MessageMessage TypeSeverityProbable Cause is as sFlow collector.DCEINFOIndicates that the specified sFlow collector is either configured or not configured.Network OS Message Reference 33153-1002807-01

7SFLO-1008RecommendedActionNo action is required.SFLO-1008MessageMessage TypeSeverityProbable CauseRecommendedActionAll the sFlow collectors are not configured.DCEINFOIndicates that none of the sFlow collectors are configured.No action is required.SFLO-1009MessageMessage TypeSeverityProbable CauseRecommendedActionSocket Operation Failed while connecting with the collector address.DCEWARNINGIndicates that the connection to the sFlow collector server failed.Reconfigure the sFlow collector using the sflow collector command.332 Network OS Message Reference53-1002807-01

SLCD-1001 7SLCD MessagesSLCD-1001MessageMessage TypeSeverityProbable CauseRecommendedActionCF life percentage used up is between 90 - 95 on card No. , Actual percentage .LOGWARNINGIndicates that the compact flash (CF) life span left over is a little more than 5 percent as reported by theCF wear leveling statistics.The CF card must be replaced as soon as possible. Contact your switch service provider for the CF cardreplacement.SLCD-1002MessageMessage TypeSeverityProbable CauseRecommendedActionCF life span percentage is between 95 - 99 on card No. , Actual percentage .LOGWARNINGIndicates that the compact flash (CF) life span left over is between 1 and 5 percent as reported by the CFwear leveling statistics.The CF card must be replaced immediately for proper functioning. Contact your switch service providerfor the CF card replacement.SLCD-1003MessageMessage TypeSeverityProbable CauseRecommendedActionCF life span percentage left is less than 1 on card No. , Actual percentage .LOGERRORIndicates that the compact flash (CF) life span left over is less than 1 percent as reported by the CF wearleveling statistics.A new CF card is required for proper functioning of the chassis. Contact your switch service provider forthe CF card replacement.Network OS Message Reference 33353-1002807-01

7SLCD-1004SLCD-1004MessageMessage TypeSeverityProbable CauseRecommendedActionCF life span percentage left on Card No is - .LOGINFOIndicates the available life span of the compact flash (CF) as reported by the CF wear leveling statistics.No action is required.SLCD-1005MessageMessage TypeSeverityProbable CauseRecommendedActionSpare Blocks percentage left on Card No. is between5-10,Actual percentage is - .LOGWARNINGIndicates that the spare blocks left on the compact flash (CF) card is between 5 and 10 percent asreported by the CF wear leveling statistics.The CF card must be replaced as soon as possible. Contact your switch service provider for the CF cardreplacement.SLCD-1006MessageMessage TypeSeverityProbable CauseRecommendedActionSpare Blocks percentage left on CF Card No. is between1-5,Actual percentage is - .LOGWARNINGIndicates that the spare blocks left on the compact flash (CF) card is between 1 and 5 percent asreported by the CF wear leveling statistics.The CF card must be replaced immediately for proper functioning. Contact your switch service providerfor the CF card replacement.334 Network OS Message Reference53-1002807-01

SLCD-1007 7SLCD-1007MessageMessage TypeSeverityProbable CauseRecommendedActionSpare Blocks percentage left on CF Card No. are lessthan 1,Actual percentage is - .LOGWARNINGIndicates that the spare blocks left on the compact flash (CF) card is less than 1 percent as reported bythe CF wear leveling statistics.A new CF card is required for proper functioning of the chassis. Contact your switch service provider forthe CF card replacement.SLCD-1008Message Spare Blocks percentage left on CF Card No. are -.Message TypeSeverityProbable CauseRecommendedActionLOGINFOIndicates the percentage of the spare blocks left on the compact flash (CF) card as reported by the CFwear leveling statistics.No action is required.SLCD-1009MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to get Wear leveling stats for CF card No. .LOGERRORIndicates that wear leveling data cannot be retrieved from the attached compact flash (CF) card.Check the availability and healthiness of the CF card immediately for proper functioning.Network OS Message Reference 33553-1002807-01

7SLCD-1010SLCD-1010MessageMessage TypeSeverityProbable CauseRecommendedActionCF wear leveling daemon Failed to find any western digital (WD) CF cards attached.LOGERRORIndicates an error in enumerating the attached compact flash (CF) cards.Check the availability and connection to the CF cards immediately for proper functioning.SLCD-1011MessageMessage TypeSeverityProbable CauseRecommendedActionCF life percentage used for card No. is .LOGINFOIndicates the used life span of the compact flash (CF) card as reported by the CF wear leveling statistics.No action is required.336 Network OS Message Reference53-1002807-01

SNMP-1001 7SNMP MessagesSNMP-1001MessageMessage TypeSeverityProbable CauseRecommendedActionSNMP service is not available .LOGERRORIndicates that the Simple Network Management Protocol (SNMP) service could not be started because ofthe specified reason. You will not be able to query the switch through SNMP.Verify that the IP address for the Ethernet and Fibre Channel interface is set correctly using the showinterface management command. If the specified reason is an initialization failure, reload the switch.SNMP-1002MessageMessage TypeSeverityProbable CauseRecommendedActionSNMP initialization failed.LOGERRORIndicates that the initialization of the Simple Network Management Protocol (SNMP) service failed andyou will not be able to query the switch through SNMP.Reload or power cycle the switch. This will automatically initialize SNMP.SNMP-1003MessageMessage TypeSeverityProbable CauseRecommendedActionDistribution of Community Strings to Secure Fabric failed.LOGERRORIndicates that the changes in the Simple Network Management Protocol (SNMP) community stringscould not be propagated to other switches in the secure fabric.Retry changing the SNMP community strings on the primary switch using the snmp-server communitycommand.Network OS Message Reference 33753-1002807-01

7SNMP-1004SNMP-1004MessageMessage TypeSeverityProbable CauseRecommendedActionIncorrect SNMP configuration.FFDC | LOGERRORIndicates that the Simple Network Management Protocol (SNMP) configuration is incorrect and theSNMP service will not work correctly.Change the SNMP configuration using the config snmp-server command.SNMP-1005MessageMessage TypeSeverityProbable CauseRecommendedActionSNMP configuration attribute, , .LOGINFOIndicates that the Simple Network Management Protocol (SNMP) configuration has changed. Theparameter that was modified is displayed along with the old and new values of that parameter.Execute the show running-config snmp-server command to view the new SNMP configuration.338 Network OS Message Reference53-1002807-01

SS-1000 7SS MessagesSS-1000MessageMessage TypeSeverityProbable CauseRecommendedActioncopy support has uploaded support information to the host with IP address .LOGINFOIndicates that the copy support command was used to transfer the support information to a remotelocation.No action is required.SS-1001MessageMessage TypeSeverityProbable CauseRecommendedActioncopy support upload operation to host IP address aborted.LOGWARNINGIndicates that a file copy error occurred during execution of the copy support command. Complete errorinformation cannot always be displayed in this message because of possible errors in the subcommandsbeing executed by the copy support command.The file copy error can occur due to one of the following reasons:• Could not connect to remote host• Could not connect to remote host - timed out• Transfer failed• Transfer failed - timed out• Directory change failed• Directory change failed - timed out• Malformed URL• Usage error• Error in login configuration file• Session initialization failed• Unknown remote host errorCheck and correct the remote server settings and configuration and then execute the copy supportcommand again.If the problem persists, contact your system administrator.Network OS Message Reference 33953-1002807-01

7SS-1002SS-1002MessageMessage TypeSeverityProbable CauseRecommendedActioncopy support has stored support information to the USB storage device.LOGINFOIndicates that the copy support command was used to transfer support information to an attached USBstorage device.No action is required.SS-1003MessageMessage TypeSeverityProbable CauseRecommendedActioncopy support operation to USB storage device aborted.LOGWARNINGIndicates that a USB operation error occurred during execution of the copy support command.Complete error information cannot always be displayed in this message because of possible errors insubcommands being executed by the copy support command.Make sure that the attached USB device is enabled.Execute the usb on command to enable an attached USB device. After the USB problem is corrected,execute the copy support command again.SS-1004MessageMessage TypeSeverityProbable CauseRecommendedActionOne or more modules timed out during copy support. Retry copy support with timeoutoption to collect all modules.LOGWARNINGIndicates timeout in modules during execution of the copy support command.Execute the copy support command again.340 Network OS Message Reference53-1002807-01

SSMD-1001 7SSMD MessagesSSMD-1001MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to allocate memory: ().DCEERRORIndicates that the specified function has failed to allocate memory.Check the memory usage on the switch using the show process memory command.Reload or power cycle the switch.SSMD-1002MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to initialize rc = .DCEERRORIndicates that initialization of a module within the system services manager (SSM) has failed.Download a new firmware version using the firmware download command.SSMD-1003MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to lock semaphore mutex: ().DCEERRORIndicates that the specified function has failed to lock the mutex (semaphore).Reload or power cycle the switch.Network OS Message Reference 34153-1002807-01

7SSMD-1004SSMD-1004MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to unlock semaphore mutex: ().DCEERRORIndicates that the specified function has failed to unlock the mutex (semaphore).Reload or power cycle the switch.SSMD-1005MessageMessage TypeSeverityProbable CauseRecommendedActionSSM startup failed.DCEERRORIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected severe error during basic start up and initialization.Reload or power cycle the switch.If the problem persists, download a new firmware version using the firmware download command.SSMD-1006MessageMessage TypeSeverityProbable CauseRecommendedActionSSM ASIC downlaod buffer overflow (size > max ) in function .DCEERRORIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected severe error when fill in the I/O control (IOCTL) structure.Reload or power cycle the switch.If the problem persists, download a new firmware version using the firmware download command.342 Network OS Message Reference53-1002807-01

SSMD-1007 7SSMD-1007MessageMessage TypeSeverityProbable CauseRecommendedActionError:: .DCEERRORIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anerror.Reload or power cycle the switch.If the problem persists, download a new firmware version using the firmware download command.SSMD-1200MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming ASIC / Multicast RateLimit.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in the programming dataplane application-specific integrated circuit (ASIC) forenforcing the multicast rate limit feature.Delete and reapply the quality of service (QoS) multicast rate limit policy using the qos rcv-queuemulticast rate-limit command.If the problem persists, reload or power cycle the switch.SSMD-1201MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming ASIC / Multicast TailDrop.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in the programming dataplane application-specific integrated circuit (ASIC) forenforcing the multicast tail drop feature.Delete and reapply the quality of service (QoS) multicast tail drop policy using the qos rcv-queuemulticast threshold command.If the problem persists, reload or power cycle the switch.Network OS Message Reference 34353-1002807-01

7SSMD-1202SSMD-1202MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming interface 0x 802.3x Pause flow control.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in the programming dataplane application-specific integrated circuit (ASIC) forenforcing the interface 802.3x pause flow control feature.Delete and reapply the quality of service (QoS) 802.3x pause flow control policy using the qosflowcontrol command.If the problem persists, reload or power cycle the switch.SSMD-1203MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming interface 0x PFC flow control.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) encountered anunexpected error in the programming dataplane application-specific integrated circuit (ASIC) forenforcing the interface priority flow control (PFC) feature.Delete and reapply the quality of service (QoS) PFC policy using the qos flowcontrol pfc coscommand.If the problem persists, reload or power cycle the switch.SSMD-1204MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed initializing ASIC /.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in initializing the dataplane application-specific integrated circuit (ASIC) quality ofservice (QoS) infrastructure.Reload or power cycle the switch.344 Network OS Message Reference53-1002807-01

SSMD-1205 7SSMD-1205MessageMessage TypeSeverityProbable CauseRecommendedActionCEE failed programming ETS policy for CEE Map .DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in programming dataplane application-specific integrated circuit (ASIC) for enforcingthe Converged Enhanced Ethernet (CEE) map enhanced transmission selection (ETS) feature.Delete and reapply the CEE map ETS policy using the cee-map default command.If the problem persists, reload or power cycle the switch.SSMD-1206MessageMessage TypeSeverityProbable CauseRecommendedActionCEE failed programming CoS to PGID policy for CEE Map .DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in programming the dataplane application-specific integrated circuit (ASIC) forenforcing the Converged Enhanced Ethernet (CEE) map CoS-to-priority group ID (PGID) mappingfeature.Delete and reapply the CEE map CoS-to-PGID policy using the cee-map default command.If the problem persists, reload or power cycle the switch.SSMD-1207MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming interface 0x Default CoS.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in programming the dataplane application-specific integrated circuit (ASIC) forenforcing the interface default class of service (CoS) feature.Delete and reapply the quality of service (QoS) interface default CoS policy using the qos coscommand.If the problem persists, reload or power cycle the switch.Network OS Message Reference 34553-1002807-01

7SSMD-1208SSMD-1208MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming interface 0x Trust.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) encountered anunexpected error in programming the dataplane application-specific integrated circuit (ASIC) forenforcing the interface trust feature.Delete and reapply the quality of service (QoS) interface trust policy using the qos trust cos command.If the problem persists, reload or power cycle the switch.SSMD-1209MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming interface 0x CoS Mutation map.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in programming the dataplane application-specific integrated circuit (ASIC) forenforcing the CoS-mutation mapping feature.Delete and reapply the quality of service (QoS) interface CoS-mutation policy using the qoscos-mutation command.If the problem persists, reload or power cycle the switch.SSMD-1210MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming interface 0x CoS to Traffic Class map.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in programming the dataplane application-specific integrated circuit (ASIC) forenforcing the CoS-to-traffic-class mapping feature.Delete and reapply the quality of service (QoS) interface CoS-to-traffic-class policy using the qoscos-traffic-class command.If the problem persists, reload or power cycle the switch.346 Network OS Message Reference53-1002807-01

SSMD-1211 7SSMD-1211MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming ASIC / SchedulerControl.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in programming the dataplane application-specific integrated circuit (ASIC) forenforcing the packet scheduler control feature.Delete and reapply the quality of service (QoS) packet scheduler control policy using the qos queuescheduler command.If the problem persists, reload or power cycle the switch.SSMD-1212MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming ASIC / MulticastScheduler Control.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in programming the dataplane application-specific integrated circuit (ASIC) forenforcing the multicast packet scheduler control feature.Delete and reapply the quality of service (QoS) multicast packet scheduler control policy using the qosqueue multicast scheduler command.If the problem persists, reload or power cycle the switch.SSMD-1213MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming interface 0x CoS Tail Drop Threshold.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in programming the dataplane application-specific integrated circuit (ASIC) forenforcing the interface class of service (CoS) tail drop threshold feature.Delete and reapply the quality of service (QoS) CoS tail drop threshold policy using the qos rcv-queuecos-threshold command.If the problem persists, reload or power cycle the switch.Network OS Message Reference 34753-1002807-01

7SSMD-1214SSMD-1214MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming interface 0x CoS Tail Drop Threshold.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in programming the dataplane application-specific integrated circuit (ASIC) forenforcing the interface class of service (CoS) tail drop threshold feature.Delete and reapply the quality of service (QoS) CoS tail drop threshold policy using the qos rcv-queuecos-threshold command.If the problem persists, reload or power cycle the switch.SSMD-1215MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming interface 0x CoS Tail Drop Threshold.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in programming the dataplane application-specific integrated circuit (ASIC) forenforcing the interface class of service (CoS) tail drop threshold feature.Delete and reapply the quality of service (QoS) CoS tail drop threshold policy using the qos rcv-queuecos-threshold command.If the problem persists, reload or power cycle the switch.SSMD-1216MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming interface 0x Pause.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in programming the dataplane application-specific integrated circuit (ASIC) forenforcing the interface pause feature.Delete and reapply the quality of service (QoS) pause policy.If the problem persists, reload or power cycle the switch.348 Network OS Message Reference53-1002807-01

SSMD-1217 7SSMD-1217MessageMessage TypeSeverityProbable CauseRecommendedActionQoS CEE could not comply with FCoE scheduler policy for CEE Map .DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) was unable to translatethe Converged Enhanced Ethernet (CEE) Map and Fibre Channel over Ethernet (FCoE) configurationinto an Enhanced Transmission Selection (ETS) scheduler policy, which can be implemented by thedataplane application-specific integrated circuit (ASIC).Reconfigure the CEE map and FCoE configuration such that it translates into an ETS scheduler policyrequiring eight or fewer traffic classes.SSMD-1218MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming interface 0x Priority Tag.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in programming the dataplane application-specific integrated circuit (ASIC) forenforcing the interface priority-tag feature.Delete and reapply the QoS interface priority-tag policy using the priority-tag command.If the problem persists, reload or power cycle the switch.SSMD-1219MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed programming interface 0x CoS7 TCAM.DCEWARNINGIndicates that the Data Center Ethernet (DCE) System Services Manager (SSM) has encountered anunexpected error in programming the dataplane application-specific integrated circuit (ASIC) forenforcing the interface CoS7 ternary content addressable memory (TCAM) feature.Delete and reapply the interface CoS7 priority-tag policy using the priority-tag command.If the problem persists, reload or power cycle the switch.Network OS Message Reference 34953-1002807-01

7SSMD-1220SSMD-1220MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed adding member port 0x to LAG 0x.DCEWARNINGIndicates conflicting quality of service (QoS) configurations on the member port.Delete the Converged Enhanced Ethernet (CEE) or Fibre Channel over Ethernet (FCoE) configurationon the member port.SSMD-1221MessageMessage TypeSeverityProbable CauseRecommendedActionQoS configuration rejected due to Long Distance configuration restriction on port.DCEWARNINGIndicates that the number of inter-switch links (ISLs) supported by the long distance configuration hasreached the maximum.Disable the ISL port using the no fabric isl enable command.SSMD-1222MessageMessage TypeSeverityProbable CauseRecommendedActionLong distance configuration cannot be completed for Chip / because ports are not shut down. Maximum retry count exceeded.DCEWARNINGIndicates that the network service module (NSM) has failed to disable all the ports after maximum retryattempts.Delete and reconfigure long distance on the link using the long-distance-isl command.350 Network OS Message Reference53-1002807-01

SSMD-1223 7SSMD-1223MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed applying RED profile to PO member port:0x.DCEERRORIndicates lack of chip resources for configuring a random early drop (RED) profile on the specifiedmember port.Delete RED configuration on other ports of the chip and re-configure RED on port-channel using the qosred-profile command.SSMD-1224MessageMessage TypeSeverityProbable CauseRecommendedActionL3 trust cannot be applied on PO member port:0x, corresponding portgroup has already max 4 L3 trust ports.DCEERRORIndicates lack of chip resources for configuring L3prio trust on the specified member port.Delete some of the Layer 3 trust ports on the chip, to which the member port belong.SSMD-1225MessageMessage TypeSeverityProbable CauseRecommendedActionQoS failed applying CEE to member port:0x as the port group itbelongs to has LD ISL enabled.DCEERRORIndicates that Converged Enhanced Ethernet (CEE) could not be applied on the chip, on which longdistance inter-switch link (ISL) is enabled.Disable long distance ISL using no long-distance-isl command and then enable CEE on the memberport chip.Network OS Message Reference 35153-1002807-01

7SSMD-1300SSMD-1300MessageMessage TypeSeverityProbable CauseRecommendedActionCEE Map is created with precedence .DCEINFOIndicates that the specified Converged Enhanced Ethernet (CEE) map has been created.No action is required.SSMD-1301MessageMessage TypeSeverityProbable CauseRecommendedActionCEE Map is deleted.DCEINFOIndicates that the specified Converged Enhanced Ethernet (CEE) map has been deleted.No action is required.SSMD-1302MessageMessage TypeSeverityProbable CauseRecommendedActionCEE Map priority table is .DCEINFOIndicates that the specified priority groups (PGs) have been added to or removed from the existingConverged Enhanced Ethernet (CEE) map.No action is required.352 Network OS Message Reference53-1002807-01

SSMD-1303 7SSMD-1303MessageMessage TypeSeverityProbable CauseRecommendedActionCEE Map priority group with weight is created withPFC .DCEINFOIndicates that the specified priority group has been created.No action is required.SSMD-1304MessageMessage TypeSeverityProbable CauseRecommendedActionCEE Map priority group is deleted.DCEINFOIndicates that the specified priority group has been deleted.No action is required.SSMD-1305MessageMessage TypeSeverityProbable CauseRecommendedActionCEE Map priority group weight is changed from to .DCEINFOIndicates that the weighting of the specified priority group has been changed.No action is required.Network OS Message Reference 35353-1002807-01

7SSMD-1306SSMD-1306MessageMessage TypeSeverityProbable CauseRecommendedActionCEE Map priority group is PFC .DCEINFOIndicates that the priority-based flow control (PFC) status has been changed for the specified prioritygroup.No action is required.SSMD-1307MessageMessage TypeSeverityProbable CauseRecommendedAction access list is created.DCEINFOIndicates that the specified access list has been created.No action is required.SSMD-1308MessageMessage TypeSeverityProbable CauseRecommendedAction access list is deleted.DCEINFOIndicates that the specified access list has been deleted.No action is required.SSMD-1309MessageMessage TypeSeverityProbable Cause access list rule sequence number is .DCEINFOIndicates that the specified access list rules have been added to or removed from an existing policy.354 Network OS Message Reference53-1002807-01

SSMD-1312 7RecommendedActionNo action is required.SSMD-1312MessageMessage TypeSeverityProbable CauseRecommendedAction assigned to interface .DCEINFOIndicates that a user profile map has been assigned to the specified interface.No action is required.SSMD-1313MessageMessage TypeSeverityProbable CauseRecommendedAction removed from interface .DCEINFOIndicates that a user profile map has been removed from the specified interface.No action is required.SSMD-1314MessageMessage TypeSeverityProbable CauseRecommendedActionCEE Map precedence changed from to .DCEINFOIndicates that the specified Converged Enhanced Ethernet (CEE) map precedence has been changed.No action is required.Network OS Message Reference 35553-1002807-01

7SSMD-1315SSMD-1315MessageMessage TypeSeverityProbable CauseRecommendedActionCEE Map remap to priority .DCEINFOIndicates that the priority cost of service (CoS) value of the specified Converged Enhanced Ethernet(CEE) map has changed.No action is required.SSMD-1400MessageMessage TypeSeverityProbable CauseRecommendedAction access list is created.DCEINFOIndicates that the specified access list has been created.No action is required.SSMD-1401MessageMessage TypeSeverityProbable CauseRecommendedAction access list is recorded.DCEINFOIndicates that the specified access list type and name has been recorded as a reference for ACL bindingin future.No action is required.356 Network OS Message Reference53-1002807-01

SSMD-1402 7SSMD-1402MessageMessage TypeSeverityProbable CauseRecommendedAction access list is deleted.DCEINFOIndicates that the specified access list has been deleted.No action is required.SSMD-1403MessageMessage TypeSeverityProbable CauseRecommendedAction access list record is deleted.DCEINFOIndicates that the access list name and type recorded for bind forward reference has been deleted.No action is required.SSMD-1404MessageMessage TypeSeverityProbable CauseRecommendedAction access list rule sequence number is DCEINFOIndicates that the access list rules are added to or removed from an existing policy.No action is required.SSMD-1405MessageMessage TypeSeverityProbable Cause access list configured on interface at.DCEINFOIndicates that the specified access list has been configured on the interface.Network OS Message Reference 35753-1002807-01

7SSMD-1406RecommendedActionNo action is required.SSMD-1406MessageMessage TypeSeverityProbable CauseRecommendedAction access list is removed from interface at.DCEINFOIndicates that the specified access list has been removed from the interface.No action is required.SSMD-1407MessageMessage TypeSeverityProbable CauseRecommendedAction access list active on interface at.DCEINFOIndicates that the specified access list has been configured on the interface.No action is required.SSMD-1408MessageMessage TypeSeverityProbable CauseRecommendedAction rules added to access list .DCEINFOIndicates that the specified rules are added to the access control list (ACL).No action is required.358 Network OS Message Reference53-1002807-01

SSMD-1436 7SSMD-1436MessageMessage TypeSeverityProbable CauseRecommendedAction access list partially active on interface at .DCEWARNINGIndicates that the specified access control list (ACL) was not fully instantiated into the ternary contentaddressable memory (TCAM).Remove the specified ACL and other unused ACLs that are applied using the ip access-list command,and then instantiate ACL into TCAM again.SSMD-1437MessageMessage TypeSeverityProbable CauseRecommendedAction access list inactive on interface at.DCEWARNINGIndicates the specified access control list (ACL) was not instantiated into the ternary content addressablememory (TCAM).Remove the specified ACL and other unused ACLs that are applied using the ip access-list command,and then instantiate ACL into TCAM again.SSMD-1438MessageMessage TypeSeverityProbable CauseRecommendedAction access list configured on interface at has rule(s) which are not supported on this platform.DCEWARNINGIndicates that the specified access control list (ACL) has rules which are not supported on this platform.Remove inactive rules using the ip access-list command and add rules which are supported on thisplatform.Network OS Message Reference 35953-1002807-01

7SSMD-1439SSMD-1439MessageMessage TypeSeverityProbable CauseRecommendedActionRule with sequence number of access list configured on interface at is notsupported on this platform.DCEWARNINGIndicates that the specified access control list (ACL) has rules which are not supported on this platform.Remove inactive rules using the ip access-list command and add rules which are supported on thisplatform.SSMD-1500MessageMessage TypeSeverityProbable CauseRecommendedAction TCAM region usage on chip / is below percent.DCEWARNINGIndicates that ternary content addressable memory (TCAM) usage on the chip is below threshold.TCAM is full and therefore clear some of the entries or do not add entries.SSMD-1536MessageMessage TypeSeverityProbable CauseRecommendedAction TCAM region usage on chip / is above percent.DCEWARNINGIndicates that the access control list (ACL), which is bound to interfaces in consuming ternary contentaddressable memory (TCAM) entries in the hardware.Remove ACLs which are not required using the ip access-list command.360 Network OS Message Reference53-1002807-01

SSMD-1537 7SSMD-1537MessageMessage TypeSeverityProbable CauseRecommendedAction TCAM region on chip / is percent full.LOGWARNINGIndicates that the access control list (ACL), which is bound to interfaces is consuming ternary contentaddressable memory (TCAM) entries in the hardware.Remove ACLs which are not required using the ip access-list command.SSMD-1571MessageMessage TypeSeverityProbable CauseRecommendedActionError Creating region Feature: Region:Chip:0x.DCEERRORIndicates that the application-specific integrated circuit (ASIC) driver has returned an error.Execute the copy support command and contact your switch service provider.SSMD-1600MessageMessage TypeSeverityProbable CauseRecommendedActionPolicy map is created.DCEINFOIndicates that the specified policy map has been created.No action is required.Network OS Message Reference 36153-1002807-01

7SSMD-1601SSMD-1601MessageMessage TypeSeverityProbable CauseRecommendedActionPolicy map is deleted.DCEINFOIndicates that the specified policy map has been deleted.No action is required.SSMD-1602MessageMessage TypeSeverityProbable CauseRecommendedActionClass map is created.DCEINFOIndicates that the specified class map has been created.No action is required.SSMD-1603MessageMessage TypeSeverityProbable CauseRecommendedActionClass map is deleted.DCEINFOIndicates that the specified class map has been deleted.No action is required.SSMD-1604MessageMessage TypeSeverityProbable CausePolice priority map is created.DCEINFOIndicates that the specified police priority map has been created.362 Network OS Message Reference53-1002807-01

SSMD-1605 7RecommendedActionNo action is required.SSMD-1605MessageMessage TypeSeverityProbable CauseRecommendedActionPolice priority map is deleted.DCEINFOIndicates that the specified police priority map has been deleted.No action is required.SSMD-1606MessageMessage TypeSeverityProbable CauseRecommendedActionClass map is added to policy map .DCEINFOIndicates that the specified class map has been added to the policy map.No action is required.SSMD-1607MessageMessage TypeSeverityProbable CauseRecommendedActionClass map is removed from policy map .DCEINFOIndicates that the specified class map has been removed from the policy map.No action is required.Network OS Message Reference 36353-1002807-01

7SSMD-1609SSMD-1609MessageMessage TypeSeverityProbable CauseRecommendedActionPolicer attribute is to for policy map and class map .DCEINFOIndicates that the specified policer attribute (rate limiting value) is set or updated for the policy and classmap.No action is required.SSMD-1610MessageMessage TypeSeverityProbable CauseRecommendedActionPolicer attribute is removed from policy map and class map .DCEINFOIndicates that the specified policer attribute (rate limiting value) has been removed from the policy andclass map.No action is required.SSMD-1611MessageMessage TypeSeverityProbable CauseRecommendedActionPolicer attribute is to for policy map and class map .DCEINFOIndicates that the specified policer attribute (marking value) is set or updated for the policy and classmap.No action is required.364 Network OS Message Reference53-1002807-01

SSMD-1612 7SSMD-1612MessageMessage TypeSeverityProbable CauseRecommendedActionPolicer attribute is removed from policy map and class map .DCEINFOIndicates that the specified policer attribute (marking value) has been removed from the policy and classmap.No action is required.SSMD-1613MessageMessage TypeSeverityProbable CauseRecommendedActionPolicer attributes removed from policy map and class map .DCEINFOIndicates that all policer attributes have been removed from the specified policy and class map.No action is required.SSMD-1614MessageMessage TypeSeverityProbable CauseRecommendedAction CoS map is to,,,,,,, for police priority mapDCEINFOIndicates that the conform or exceed cost of service (CoS) map is set or updated for the police prioritymap.No action is required.Network OS Message Reference 36553-1002807-01

7SSMD-1615SSMD-1615MessageMessage TypeSeverityProbable CauseRecommendedAction CoS map is removed from police priority map .DCEINFOIndicates that the conform or exceed cost of service (CoS) map has been removed from the policepriority map.No action is required.SSMD-1618MessageMessage TypeSeverityProbable CauseRecommendedActionPolicy map is applied on interface in direction.DCEINFOIndicates that the specified policy map has been applied on the interface.No action is required.SSMD-1619MessageMessage TypeSeverityProbable CauseRecommendedActionPolicy map is removed from interface in direction.DCEINFOIndicates that the specified policy map has been removed from the interface.No action is required.366 Network OS Message Reference53-1002807-01

SSMD-1620 7SSMD-1620MessageMessage TypeSeverityProbable CauseRecommendedActionPolicer attribute priority map is added to policy map and class map .DCEINFOIndicates that the specified policer attribute priority map has been added to the policy and class map.No action is required.SSMD-1621MessageMessage TypeSeverityProbable CauseRecommendedActionPolicer attribute priority map is removed from policy map andclass map .DCEINFOIndicates that the specified policer attribute priority map has been removed from the policy and classmap.No action is required.SSMD-1622MessageMessage TypeSeverityProbable CauseRecommendedActionOperational policer attr CBS value set to on interface in direction for policy map andclass map .DCEINFOIndicates that the operational committed burst size (CBS) is set on the specified interface for the policyand class map.No action is required.Network OS Message Reference 36753-1002807-01

7SSMD-1650SSMD-1650MessageMessage TypeSeverityProbable CauseRecommendedActionPolicer resource limit reached.DCEWARNINGIndicates unavailability of policer resources.Remove unnecessary class maps from policy map using the no class command.SSMD-1651MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to apply policy map on interface .DCEWARNINGIndicates that the specified policy map could not be applied on the interface.Apply the policy map on interface again using the service-policy command.SSMD-1652MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to remove policy map from interface .DCEWARNINGIndicates that the specified policy map could not be removed from the interface.Remove the policy map on interface again using the no service-policy command.SSMD-1653MessageMessage TypeSeverityProbable CauseFailed to retreive police statistics for interface .DCEWARNINGIndicates that an attempt to retrieve the police statistics for policy map on the specified interface hasfailed.368 Network OS Message Reference53-1002807-01

SSMD-1654 7RecommendedActionRetrieve the police statistics for interface again using the show policymap command.SSMD-1654MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to clear police statistics for interface .DCEWARNINGIndicates that an attempt to clear the policy map statistics on the specified interface has failed.Clear the police statistics again using the clear counters policymap interface tengigabitethernetcommand.SSMD-1655MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to clear all police statistics.DCEWARNINGIndicates that an attempt to clear all policy map statistics has failed.Clear the police statistics again using the clear counters policymap command.SSMD-1656MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to update police priority map .DCEWARNINGIndicates that an attempt to update the specified police priority map has failed.Update the police priority map again using the no conform | exceed command.Network OS Message Reference 36953-1002807-01

7SSMD-1657SSMD-1657MessageMessage TypeSeverityProbable CauseRecommendedActionFailed to remove police priority map .DCEWARNINGIndicates that an attempt to delete the specified police priority map has failed.Delete the police priority map again.SSMD-1658MessageMessage TypeSeverityProbable CauseRecommendedActionPolicy map not found for applying it on interface in direction.DCEWARNINGIndicates that the specified policy map is not found for binding policy map to the interface.Check whether the policy map exists. If the policy map does not exist, add a policy map using thepolicy-map command.SSMD-1659MessageMessage TypeSeverityProbable CauseRecommendedActionLossy CoS is remapped to lossless CoS in police priority map for policy map and class map on interface in direction.DCEWARNINGIndicates that a lossy cost of service (CoS) value is remapped to lossless CoS value.Remove conflicting CoS values in conform and exceed map and update prio map using the conform |exceed command.370 Network OS Message Reference53-1002807-01

SSMD-1660 7SSMD-1660MessageMessage TypeSeverityProbable CauseRecommendedActionPolicer attribute TC is set to lossless TC for policy map class map on interface in direction.DCEWARNINGIndicates that the conform or exceed traffic class is set to lossless traffic class.Modify the conform or exceed traffic class using the conform | exceed command.SSMD-1700MessageMessage TypeSeverityProbable CauseRecommendedActionStorm control for traffic with a rate of bpsconfigured on interface .DCEINFOIndicates that the broadcast, unknown unicast, and multicast (BUM) storm control has been enabledmanually for a given protocol on the specified interface.No action is required.SSMD-1701MessageMessage TypeSeverityProbable CauseRecommendedActionStorm control for traffic successfully instantiated oninterface .DCEINFOIndicates that broadcast, unknown unicast, and multicast (BUM) configuration has been instantiated intothe hardware.No action is required.Network OS Message Reference 37153-1002807-01

7SSMD-1702SSMD-1702MessageMessage TypeSeverityProbable CauseRecommendedActionStorm control instantiation for traffic failed interface. Reason code .DCEERRORIndicates that broadcast, unknown unicast, and multicast (BUM) configuration failed to be instantiatedinto the hardware.Action varies depending on reason code.SSMD-1703MessageMessage TypeSeverityProbable CauseRecommendedActionStorm control for traffic removed from interface.DCEINFOIndicates that the broadcast, unknown unicast, and multicast (BUM) storm control has been disabledmanually for a given protocol on a specific interface.No action is required.SSMD-1704MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to remove storm control from interface. Reason code .DCEWARNINGIndicates that broadcast, unknown unicast, and multicast (BUM) storm control could not be disabled onthe specified interface.No action is required.372 Network OS Message Reference53-1002807-01

SSMD-1705 7SSMD-1705MessageMessage TypeSeverityProbable CauseRecommendedAction traffic rate has been exceeded on interface .DCEWARNINGIndicates that the broadcast, unknown unicast, and multicast (BUM) monitor routine has detected rateviolation.No action is required.SSMD-1706MessageMessage TypeSeverityProbable CauseRecommendedAction traffic rate returned to conforming on interface.DCEINFOIndicates that broadcast, unknown unicast, and multicast (BUM) storm control has been disabledmanually for a given protocol on the specified interface.No action is required.SSMD-1707MessageMessage TypeSeverityProbable CauseRecommendedAction traffic rate has been exceeded interface .Interface will be shut down.DCEWARNINGIndicates that the broadcast, unknown unicast, and multicast (BUM) monitor routine has detected rateviolation. The interface has been shut down.Disable BUM storm control on the interface using the no storm-control ingress command; thenre-enable the interface (using the no shutdown command) and BUM storm control (using thestorm-control ingress command).Network OS Message Reference 37353-1002807-01

7SSMD-1708SSMD-1708MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to obtain BUM storm control status for interface . Reasoncode .DCEERRORIndicates that the broadcast, unknown unicast, and multicast (BUM) monitoring routine has failed toobtain the storm control status from the hardware.Execute the copy support command and contact your switch service provider.SSMD-1900MessageMessage TypeSeverityProbable CauseRecommendedActionSecurity sub-profile is created for port-profile .DCEINFOIndicates that a security sub-profile has been created for the specified port profile.No action is required.SSMD-1901MessageMessage TypeSeverityProbable CauseRecommendedActionACL is configured successfully for security sub-profile of port-profile.DCEINFOIndicates that the specified access control list (ACL) has been configured for security sub-profile.No action is required.374 Network OS Message Reference53-1002807-01

SSMD-1902 7SSMD-1902MessageMessage TypeSeverityProbable CauseRecommendedActionACL is removed successfully for security sub-profile of port-profile.DCEINFOIndicates that the specified access control list (ACL) has been removed for security sub-profile.No action is required.SSMD-1903MessageMessage TypeSeverityProbable CauseRecommendedActionCoS is configured successfully for QoS sub-profile of port-profile.DCEINFOIndicates that the specified cost of service (CoS) has been configured for quality of service (QoS)sub-profile.No action is required.SSMD-1904MessageMessage TypeSeverityProbable CauseRecommendedActionTrust is configured successfully for QoS sub-profile of port-profile .DCEINFOIndicates that trust has been configured for quality of service (QoS) sub-profile.No action is required.Network OS Message Reference 37553-1002807-01

7SSMD-1905SSMD-1905MessageMessage TypeSeverityProbable CauseRecommendedActionTrust is removed successfully for QoS sub-profile of port-profile .DCEINFOIndicates that trust has been removed for quality of service (QoS) sub-profile.No action is required.SSMD-1906MessageMessage TypeSeverityProbable CauseRecommendedActionFlowcontrol Tx Rx is configured successfully for QoSsub-profile of port-profile .DCEINFOIndicates that flowcontrol has been configured for quality of service (QoS) sub-profile.No action is required.SSMD-1907MessageMessage TypeSeverityProbable CauseRecommendedActionCoS-mutation is configured successfully for QoS sub-profile ofport-profile .DCEINFOIndicates that CoS-mutation has been configured for quality of service (QoS) sub-profile.No action is required.376 Network OS Message Reference53-1002807-01

SSMD-1908 7SSMD-1908MessageMessage TypeSeverityProbable CauseRecommendedActionCoS-mutation is removed successfully for QoS sub-profile of port-profile .DCEINFOIndicates that the CoS-mutation has been removed for quality of service (QoS) sub-profile.No action is required.SSMD-1909MessageMessage TypeSeverityProbable CauseRecommendedActionCoS-traffic-class is configured successfully for QoS sub-profile ofport-profile .DCEINFOIndicates that the specified CoS-to-traffic-class mapping has been configured for quality of service (QoS)sub-profile.No action is required.SSMD-1910MessageMessage TypeSeverityProbable CauseRecommendedActionCoS-traffic-class is removed successfully for QoS sub-profile of port-profile.DCEINFOIndicates that the CoS-to-traffic-class mapping has been removed for quality of service (QoS) sub-profile.No action is required.Network OS Message Reference 37753-1002807-01

7SSMD-1911SSMD-1911MessageMessage TypeSeverityProbable CauseRecommendedActionCEE is removed successfully for QoS sub-profile of port-profile .DCEINFOIndicates that Converged Enhanced Ethernet (CEE) has been removed for quality of service (QoS)sub-profile.No action is required.SSMD-1912MessageMessage TypeSeverityProbable CauseRecommendedActionCEE is configured successfully for QoS sub-profile of port-profile.DCEINFOIndicates that Converged Enhanced Ethernet (CEE) has been configured for quality of service (QoS)sub-profile.No action is required.SSMD-1913MessageMessage TypeSeverityProbable CauseRecommendedActionFlowcontrol PFC-CoS Tx Rx is configuredsuccessfully for QoS sub-profile of port-profile .DCEINFOIndicates that the flowcontrol priority flow control (PFC) has been configured for quality of service (QoS)sub-profile.No action is required.378 Network OS Message Reference53-1002807-01

SSMD-1914 7SSMD-1914MessageMessage TypeSeverityProbable CauseRecommendedActionQoS sub-profile is created for port-profile .DCEINFOIndicates that the quality of service (QoS) sub-profile has been created.No action is required.SSMD-1915MessageMessage TypeSeverityProbable CauseRecommendedActionSecurity sub-profile is deleted for port-profile .DCEINFOIndicates that the security sub-profile has been deleted.No action is required.SSMD-1916MessageMessage TypeSeverityProbable CauseRecommendedActionQoS sub-profile is deleted for port-profile .DCEINFOIndicates that the specified quality of service (QoS) sub-profile has been deleted.No action is required.Network OS Message Reference 37953-1002807-01

7SULB-1100SULB MessagesSULB-1100MessageMessage TypeClassSeverityProbable CauseRecommendedActionFirmware begins on.AUDIT | LOGFIRMWAREINFOIndicates that the specified firmware operation has started on the specified slot or partition.No action is required.SULB-1101MessageMessage TypeClassSeverityProbable CauseRecommendedActionFirmware ends on.AUDIT | LOGFIRMWAREINFOIndicates that the specified firmware operation has completed successfully on the specified slot orpartition.No action is required.SULB-1102MessageMessage TypeClassSeverityProbable CauseFirmware failed on with error ().AUDIT | LOGFIRMWAREWARNINGIndicates that the specified firmware operation has failed on the specified slot or partition. The error codeindicates the reason for the failure.380 Network OS Message Reference53-1002807-01

SULB-1102 7The following table lists the error codes that provide more details on why the firmware operation failed.TABLE 9Error messages and error codesError message"Upgrade is inconsistent.""OSRootPartition is inconsistent.""Unable to access the package list file. Check whether the file name is specifiedproperly.""Red Hat package manager (RPM) package database is inconsistent. Contact yourservice provider for recovery.""Out of memory.""Failed to download RPM package. Check if the firmware image is accessible.""Unable to create firmware version file.""Unexpected system error.""Another firmware download is in progress.""Error in releasing lock device.""firmware commit failed.""Firmware directory structure is not compatible. Check whether the firmware issupported on this platform.""Failed to load the Linux kernel image. Contact your service provider to assistance.""OSLoader is inconsistent."New image has not been committed. Execute the firmware commit command orthe firmware restore and firmware download commands.""firmware restore is not needed.""Images are not mounted properly.""Unable to uninstall old packages. Contact your service provider for assistance.""firmware download has timed out.""Out of disk space.""Primary filesystem is inconsistent. Execute the firmware restore to restore theoriginal firmware, or contact your service provider for recovery.""The post-install script failed.""Reload (partition) failed.""Primary kernel partition is inconsistent. Contact your service provider for recovery.""The pre-install script failed.""Failed to install RPM package.""Cannot downgrade directly to this version. Downgrade to an intermediate versionand then download the desired version.""Failed to validate firmware signature.""Failed to swap the firmware partitions.""Failed to load the PROM image. Contact your service provider for assistance."Error code0x100x110x120x130x140x150x160x170x180x190x1a0x1b0x1c0x1d0x1e0x1f0x200x210x230x240x250x260x270x280x290x2b0x2c0x3e0x400x41Network OS Message Reference 38153-1002807-01

7SULB-1103RecommendedActionExecute the show firmwaredownloadstatus command for more information. Restart the firmwareoperation if needed.SULB-1103MessageMessage TypeClassSeverityProbable CauseRecommendedActionFirmware download completed successfully on .AUDIT | LOGFIRMWAREINFOIndicates that firmware download has completed successfully on the specified slot or partition.No action is required.Execute the show firmwaredownloadstatus command for more information. Execute the showversion to verify the firmware version.SULB-1104MessageMessage TypeClassSeverityProbable CauseFirmware download failed on with error ().AUDIT | LOGFIRMWARECRITICALIndicates that firmware download has failed on the specified slot. The error code indicates the reason forthe failure.The following table lists the error codes that provide more details on why the firmware operation failed.TABLE 10Error messages and error codesError message"Upgrade is inconsistent.""OSRootPartition is inconsistent.""Unable to access the package list file. Check whether the file name is specifiedproperly.""Red Hat package manager (RPM) package database is inconsistent. Contact yourservice provider for recovery.""Out of memory.""Failed to download RPM package. Check if the firmware image is accessible.""Unable to create firmware version file.""Unexpected system error.""Another firmware download is in progress."Error code0x100x110x120x130x140x150x160x170x18382 Network OS Message Reference53-1002807-01

SULB-1105 7TABLE 10Error messages and error codes (Continued)Error message"Error in releasing lock device.""firmware commit failed.""Firmware directory structure is not compatible. Check whether the firmware issupported on this platform.""Failed to load the Linux kernel image. Contact your service provider to assistance.""OSLoader is inconsistent."New image has not been committed. Execute the firmware commit command orthe firmware restore and firmware download commands.""firmware restore is not needed.""Images are not mounted properly.""Unable to uninstall old packages. Contact your service provider for assistance.""firmware download has timed out.""Out of disk space.""Primary filesystem is inconsistent. Execute the firmware restore to restore theoriginal firmware, or contact your service provider for recovery.""The post-install script failed.""Reload (partition) failed.""Primary kernel partition is inconsistent. Contact your service provider for recovery.""The pre-install script failed.""Failed to install RPM package.""Cannot downgrade directly to this version. Downgrade to an intermediate versionand then download the desired version.""Failed to validate firmware signature.""Failed to swap the firmware partitions.""Failed to load the PROM image. Contact your service provider for assistance."Error code0x190x1a0x1b0x1c0x1d0x1e0x1f0x200x210x230x240x250x260x270x280x290x2b0x2c0x3e0x400x41RecommendedActionExecute the show firmwaredownloadstatus command for more information. Execute the power-offand power-on commands on the slot for recovery.SULB-1105MessageMessage TypeClassSeverityProbable CauseFirmware upgrade session (: ) starts.AUDIT | LOGFIRMWAREINFOIndicates that firmware upgrade has started.Network OS Message Reference 38353-1002807-01

7SULB-1106RecommendedActionNo action is required.SULB-1106MessageMessage TypeClassSeverityProbable CauseRecommendedActionFirmware upgrade session (: ) completes.AUDIT | LOGFIRMWAREINFOIndicates that firmware upgrade has completed successfully.Execute the show firmwaredownloadstatus command for more information.SULB-1107MessageMessage TypeSeverityProbable CauseRecommendedActionFirmware upgrade session (: ) failed but recovered.LOGWARNINGIndicates that firmware upgrade has failed but was recovered.Execute the show firmwaredownloadstatus command for more information. Execute the firmwaredownload command again if needed.SULB-1108MessageMessage TypeSeverityProbable CauseRecommendedActionFirmware upgrade session (: ) failed.LOGCRITICALIndicates that firmware upgrade has failed.Execute the show firmwaredownloadstatus command for more information. Execute the firmwaredownload command again if needed.384 Network OS Message Reference53-1002807-01

SULB-1109 7SULB-1109MessageMessage TypeSeverityProbable CauseRecommendedActionFirmware upgrade session (: ) aborted.LOGCRITICALIndicates that firmware upgrade has been aborted.Execute the firmware download command again if needed.Network OS Message Reference 38553-1002807-01

7SWCH-1001SWCH MessagesSWCH-1001MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch is not in ready state - Switch enable failed switch status= 0x, c_flags = 0x.LOGERRORIndicates failure to enable the switch because it is not in ready state.If the message persists, execute the copy support command and contact your switch service provider.SWCH-1002MessageMessage TypeSeverityProbable CauseRecommendedActionSecurity violation: Unauthorized device tries to flogin toport .LOGINFOIndicates that the specified device is not present in the authorized profile list.Verify that the device is authorized to log in to the switch. If the device is authorized, execute the showsecpolicy command to verify whether the specified device World Wide Name (WWN) is listed. If it is notlisted, execute the secpolicy defined-policy command to add this device to an existing policy.SWCH-1003MessageMessage TypeSeverityProbable CauseRecommendedActionSlot ENABLED but Not Ready during recovery, disabling slot = ().LOGERRORIndicates that the slot state has been detected as inconsistent during failover or recovery.For a modular switch, execute the power-off and power-on commands to power cycle the interfacemodule.For a compact switch, reload or power cycle the switch.386 Network OS Message Reference53-1002807-01

SWCH-1004 7SWCH-1004MessageMessage TypeSeverityProbable CauseRecommendedActionInterface module attach failed during recovery, disabling slot = .LOGERRORIndicates that the specified interface module has failed during failover or recovery.For a modular switch, execute the power-off and power-on commands to power cycle the interfacemodule.For a compact switch, reload or power cycle the switch.SWCH-1005MessageMessage TypeSeverityProbable CauseRecommendedActionDiag attach failed during recovery, disabling slot = .LOGERRORIndicates that the diagnostic interface module attach operation has failed during failover or recovery.For a modular switch, execute the power-off and power-on commands to power cycle the interfacemodule.For a compact switch, reload or power cycle the switch.SWCH-1007MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch port disabled due to \"\".LOGWARNINGIndicates that the specified switch port is disabled due to the reason displayed in the message.Take corrective action to restore the port based on the disable reason displayed in the message and thenexecute the shutdown and no shutdown commands.Network OS Message Reference 38753-1002807-01

7SWCH-1021SWCH-1021MessageMessage TypeSeverityProbable CauseRecommendedActionHA state out of sync: Standby MM (ver = ) does not supportDynamic area on default switch (Active MM version = ).LOGWARNINGIndicates that the standby management module does not support dynamic area on the default switch.Load a firmware version in which the standby management module supports dynamic area on the defaultswitch using the firmware download command.388 Network OS Message Reference53-1002807-01

TOAM-1000 7TOAM MessagesTOAM-1000MessageMessage TypeSeverityProbable CauseRecommendedActionCannot run this command because VCS is disabled.DCEINFOIndicates inability to run the TRILL OAM (TOAM) commands because VCS is disabled.To run the TOAM commands, enable VCS using the vcs enable command.TOAM-1003MessageMessage TypeSeverityProbable CauseRecommendedActionInitilization error: .DCEERRORIndicates that TRILL OAM (TOAM) has encountered an error during initialization.Reload or power cycle the switch.Network OS Message Reference 38953-1002807-01

7TRCE-1002TRCE MessagesTRCE-1002MessageMessage TypeSeverityProbable CauseRecommendedActionTrace dump automaticallytransferred to address ' '.LOGINFOIndicates that a trace dump has occurred on the switch or the specified slot, and the trace dump fileswere automatically transferred from the switch to the specified FTP server.No action is required.TRCE-1003MessageMessage TypeSeverityProbable CauseRecommendedActionTrace dump was nottransferred due to FTP error.LOGERRORIndicates that a trace dump has occurred on the switch or the specified slot, but the trace dump files werenot automatically transferred from the switch due to reasons such as an FTP error, wrong FTP address,FTP site is down, and network is down.If the message persists, execute the copy support command and contact your switch service provider.TRCE-1005MessageMessage TypeSeverityProbable CauseRecommendedActionFTP Connectivity Test failed due to error.LOGERRORIndicates that the connectivity test to the FTP host failed because of reasons such as a wrong FTPaddress, FTP site is down, or network is down.Execute the copy support command and contact your switch service provider.390 Network OS Message Reference53-1002807-01

TRCE-1006 7TRCE-1006MessageMessage TypeSeverityProbable CauseRecommendedActionFTP Connectivity Test succeeded to FTP site ' '.LOGINFOIndicates that a connectivity test to the FTP host has succeeded.No action is required.TRCE-1007MessageMessage TypeSeverityProbable CauseRecommendedActionNotification of this MM has failed. Parameters temporarily out of sync with otherMM.LOGERRORIndicates that the active management module was unable to alert the standby management module of achange in the trace status. This message is only applicable to modular switches.This message is often transitory. Wait a few minutes and try the command again.If the message persists, execute the copy support command and contact your switch service provider.TRCE-1008MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to load trace parameters.FFDC | LOGCRITICALIndicates that the management module is unable to read the stored trace parameters.Reload the switch or the chassis.If the message persists, execute the copy support command and contact your switch service provider.Network OS Message Reference 39153-1002807-01

7TRCE-1009TRCE-1009MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to alert active MM that a dump has occurred.LOGWARNINGIndicates that the standby management module is unable to communicate trace information to the activemanagement module. This message is only applicable to modular switches.Execute the show ha command to verify that the current management module is standby and the activemanagement module is active.If the message persists, execute the copy support command and contact your switch service provider.TRCE-1010MessageMessage TypeSeverityProbable CauseRecommendedActionTraced fails to start.LOGERRORIndicates that the trace daemon (traced), which is used for transferring the trace files has failed to start.The trace capability within the switch is unaffected. The system automatically restarts the traced facilityafter a brief delay.If the message persists, reload the switch or the chassis.Execute the copy support command and contact your switch service provider.TRCE-1011MessageMessage TypeSeverityProbable CauseRecommendedActionTrace dump manually transferred to target ' ': .LOGINFOIndicates that the trace dump files were transferred manually to the specified slot.No action is required.392 Network OS Message Reference53-1002807-01

TRCE-1012 7TRCE-1012MessageMessage TypeSeverityProbable CauseRecommendedActionThe system was unable to retrieve trace information from slot .LOGWARNINGIndicates that the system was unable to retrieve trace information from the specified slot because there isno communication between the main system and the slot.Check that the interface module is enabled and retry the command. If the interface module is alreadyenabled, execute the copy support command and contact your switch service provider.Network OS Message Reference 39353-1002807-01

7TS-1002TS MessagesTS-1002MessageMessage TypeSeverityProbable CauseRecommendedAction Clock Server used instead of : locl: 0x remote: 0x.LOGINFOIndicates that the switch time synchronization was sourced from an alternate clock server instead of theconfigured clock server. The clock server used can be one of the following type:• LOCL - Local switch clock.• External - External Network Time Protocol (NTP) server address configured.This message may be logged during temporary operational issues such as IP network connection issuesto the external clock server. If the message does not recur, it can be ignored.Execute the show ntp status command to verify that the switch clock server IP address is configuredcorrectly. Verify if this clock server is accessible to the switch and functional. If it is not accessible orfunctional, configure an accessible and functional clock server or reset the clock server to local clockserver (LOCL).TS-1008MessageMessage TypeSeverityProbable CauseRecommendedAction Clock Server used instead of .LOGINFOIndicates that the source of switch time synchronization was changed to another configured clock serverbecause the Network Time Protocol (NTP) query to the current active external clock server failed.No action is required. New clock server synchronization will adjust the clock time.TS-1009MessageMessage TypeClassSeverityProbable CauseEvent: change time: attempt.AUDITSECURITYINFOIndicates an attempt to change the switch time.394 Network OS Message Reference53-1002807-01

TS-1010 7RecommendedActionNo action is required.TS-1010MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: change time: , Info: .AUDITSECURITYINFOIndicates the status of the attempt to change the switch time.No action is required.TS-1011MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: change time zone: attempt.AUDITSECURITYINFOIndicates an attempt to change the time zone.No action is required.TS-1012MessageMessage TypeClassSeverityProbable CauseRecommendedActionEvent: change time zone: , Info: AUDITSECURITYINFOIndicates the status of the attempt to change the time zone.No action is required.Network OS Message Reference 39553-1002807-01

7UCST-1003UCST MessagesUCST-1003Message Duplicate Path to RBridge , Output Port = , PDB pointer =0x.Message TypeSeverityProbable CauseRecommendedActionLOGINFOIndicates that duplicate paths were reported to the specified RBridge from the output port. The PDBpointer value displayed in the message is the address of the path database (PDB) and providesdebugging information.No action is required.396 Network OS Message Reference53-1002807-01

UPTH-1001 7UPTH MessagesUPTH-1001MessageMessage TypeSeverityProbable CauseRecommendedActionNo minimum cost path in candidate list.LOGWARNINGIndicates that the switch is unreachable because no minimum cost path (MPATH) exists in the candidatelist (RBridge ID list).No action is required. This error will end the current shortest path first (SPF) computation.Network OS Message Reference 39753-1002807-01

7VC-1000VC MessagesVC-1000MessageMessage TypeSeverityProbable CauseRecommendedActionvCenter configuration is added.LOGINFOIndicates that a new vCenter configuration was added.No action is required.VC-1001MessageMessage TypeSeverityProbable CauseRecommendedActionvCenter configuration is changed.LOGINFOIndicates that the specified vCenter configuration has been updated.No action is required.VC-1002MessageMessage TypeSeverityProbable CauseRecommendedActionvCenter configuration is deleted.LOGINFOIndicates that the specified vCenter configuration has been deleted.No action is required.398 Network OS Message Reference53-1002807-01

VC-1003 7VC-1003MessageMessage TypeSeverityProbable CauseRecommendedActionvCenter configuration has been activated successfully.LOGINFOIndicates that the specified vCenter configuration has been activated.No action is required.VC-1004MessageMessage TypeSeverityProbable CauseRecommendedActionvCenter configuration has been deactivated successfully.LOGINFOIndicates that the specified vCenter configuration has been deactivated.No action is required.VC-1005MessageMessage TypeSeverityProbable CauseRecommendedActionLogin to vCenter failed (attempt(s) ) - checkcredentials for user .LOGWARNINGIndicates that the vCenter login failed due to invalid credentials.Enter the correct username and password for the vCenter.Network OS Message Reference 39953-1002807-01

7VC-1006VC-1006MessageMessage TypeSeverityProbable CauseRecommendedActionvCenter periodic discovery interval has been changed to minutes.LOGINFOIndicates that the periodic discovery timer interval has been changed for the specified vCenter.No action is required.VC-1007MessageMessage TypeSeverityProbable CauseRecommendedActionvCenter : ignore-delete-all-response has been changed to cycles.LOGINFOIndicates that the vCenter ignore invalid discovery cycle count has been changed.No action is required.VC-1008MessageMessage TypeSeverityProbable CauseRecommendedActionIgnoring no data from vCenter - cycle: LOGWARNINGIndicates the cycle for which no data is received from vCenter has been ignored.No action is required.400 Network OS Message Reference53-1002807-01

VC-1009 7VC-1009MessageMessage TypeSeverityProbable CauseRecommendedActionNo data received from vCenter , proceeding with discovery after specified cyclesLOGWARNINGIndicates proceeding with discovery after receiving invalid data from vCenter.No action is required.VC-1010MessageMessage TypeSeverityProbable CauseRecommendedActionvCenter : ignore-delete-all-response value has been changed toALWAYS.LOGINFOIndicates that the vCenter ignore invalid discovery cycle count has been changed to “always”.No action is required.VC-1011MessageMessage TypeSeverityProbable CauseRecommendedActionvCenter : ignoring invalid discovery - ALWAYS.LOGWARNINGIndicates the cycle for which there was an invalid discovery has been ignored.No action is required.Network OS Message Reference 40153-1002807-01

7VCS-1001VCS MessagesVCS-1001MessageMessage TypeSeverityProbable CauseRecommendedActionEvent: VCS cluster create, Coordinator IP: , VCS ID: , Status: VCS cluster failed to be created, Reason: .LOG | VCSERRORIndicates that the VCS cluster failed to be created. Refer to the reason code for the cause of the error.Refer to reason code for possible action.VCS-1003MessageMessage TypeSeverityProbable CauseEvent: VCS node add, Coordinator IP:

VCS-1004 7• Fabric Distribution Service (FDS): VCS is enabled on a node that was not a member of the VCScluster, or the node rejoined the VCS cluster after the reload command was issued, or theinterswitch link (ISL) was toggled.RecommendedActionNo action is required.VCS-1004MessageMessage TypeSeverityProbable CauseRecommendedActionEvent: VCS node add, Coordinator IP: , VCS ID: , Status: rBridge ID ()rejoined VCS cluster.LOG | VCSINFOIndicates that the Distributed Configuration Manager (DCM) node has gone offline and returned onlinewithout any configuration changes.No action is required.Network OS Message Reference 40353-1002807-01

7VCS-1006VCS-1006MessageMessage TypeSeverityProbable CauseRecommendedActionEvent: VCS node rejoin, Coordinator IP: , VCS ID: , Status: rBridge ID ()removed from VCS cluster.LOG | VCSINFOIndicates that VCS is disabled on the node that was part of a VCS cluster.No action is required.VCS-1008MessageMessage TypeSeverityProbable CauseRecommendedActionEvent: VCS node remove, Coordinator IP:

VCS-1009 7VCS-1009MessageMessage TypeSeverityProbable CauseRecommendedActionEvent: VCS node disconnect, Coordinator IP:

7VRRP-1001VRRP MessagesVRRP-1001MessageMessage TypeSeverityProbable CauseRecommendedAction: .DCEERRORIndicates that the system has failed to allocate memory.Check the memory usage on the switch using the show process memory command.Reload or power cycle the switch.VRRP-1501MessageMessage TypeSeverityProbable CauseRecommendedAction: .DCEERRORIndicates that the system has failed to initialize.Reload or power cycle the switch.VRRP-2001MessageMessage TypeSeverityProbable CauseRecommendedAction: .DCEERRORIndicates a connection, transfer, or receiving error in the socket.If this is a modular switch, execute the ha failover command. If the problem persists or if this is acompact switch, download a new firmware version using the firmware download command.406 Network OS Message Reference53-1002807-01

WLV-1001 7WLV MessagesWLV-1001MessageMessage TypeSeverityProbable CauseRecommendedActionPort port fault. Change the SFP transceiver or check cable.LOGERRORIndicates a deteriorated small form-factor pluggable (SFP) transceiver, an incompatible SFP transceiverpair, or a faulty cable between the peer ports.Verify that compatible SFP transceivers are used on the peer ports, the SFP transceivers have notdeteriorated, and the Fibre Channel cable is not faulty. Replace the SFP transceivers or the cable, ifnecessary.WLV-1002MessageMessage TypeSeverityProbable CauseRecommendedActionPort chip faulted due to internal error.LOG | FFDCERRORIndicates an internal error. All the ports on the interface module or switch will be disrupted.For a modular switch, execute the power-off and power-on commands to power cycle the interfacemodule.For a compact switch, reload or power cycle the switch.WLV-1003MessageMessage TypeSeverityProbable CauseRecommendedActionPort faulted due to excessive link flapping. Check the SFPtransceiver/cable and issue shutdown/no shutdown commands to recover.LOGERRORIndicates a deteriorated small form-factor pluggable (SFP) transceiver, an incompatible SFP transceiverpair, or a faulty cable between the peer ports.Verify that compatible SFP transceivers are used on the peer ports, the SFP transceivers have notdeteriorated, and the cable is not faulty. Replace the SFP transceivers or the cable, if necessary. Executethe shutdown and no shutdown commands to restart the link up process.Network OS Message Reference 40753-1002807-01

7ZONE-1010ZONE MessagesZONE-1010MessageMessage TypeSeverityProbable CauseRecommendedActionDuplicate entries in zone () specification.LOGWARNINGIndicates that there are duplicate entries in a zone object. A zone object member is specified twice in agiven zone object. This message occurs only when enabling a zone configuration.Check the members of the zone and delete the duplicate member using the no member-zonecommand.ZONE-1014MessageMessage TypeSeverityProbable CauseRecommendedActionMissing required license - .LOGERRORIndicates that the required zoning license is missing.Install the zoning license using the license add command. Contact your switch supplier to obtain azoning license if you do not have one.ZONE-1015MessageMessage TypeSeverityProbable CauseRecommendedActionNot owner of the current transaction .LOGWARNINGIndicates that a zoning change operation was not allowed because the zoning transaction was openedby another task. Indicates concurrent modification of the zone database by multiple administrators.Wait until the previous transaction is completed. Verify that only one administrator is working with thezone database at a time.408 Network OS Message Reference53-1002807-01

ZONE-1019 7ZONE-1019Message Transaction Commit failed. Reason code () -\"\".Message TypeSeverityProbable CauseRecommendedActionLOGERRORIndicates that the reliable commit service (RCS) had a transmit error. RCS is a protocol used to transmitchanges to the configuration database within a fabric.Often this message indicates a transitory problem. Wait a few minutes and retry the command.Make sure your changes to the zone database are not overwriting the work of another administrator.Execute the show zoning operation-info command to know if there is any outstanding transactionrunning on the local switches.If the message persists, execute the copy support command and contact your switch service provider.ZONE-1022MessageMessage TypeSeverityProbable CauseRecommendedActionThe effective configuration has changed to .LOGINFOIndicates that the effective zone configuration has changed to the specified configuration name.Verify that the event was planned. If the event was planned, no action is required. If the event was notplanned, take appropriate action as defined by your enterprise security policy.ZONE-1023MessageMessage TypeSeverityProbable CauseRecommendedActionSwitch connected to port () is busy. Retrying zone merge.LOGINFOIndicates that the switch is retrying the zone merge operation. This usually occurs if the switch on theother side of the port is busy.If the message persists, execute the copy support command and contact your switch service provider.Network OS Message Reference 40953-1002807-01

7ZONE-1024ZONE-1024MessageMessage TypeSeverityProbable CauseRecommendedAction.LOGINFOIndicates that the zoning enabled-configuration cfg-action cfg-save command was executedsuccessfully.No action is required.ZONE-1027MessageMessage TypeSeverityProbable CauseRecommendedActionZoning transaction aborted .LOGINFOIndicates that the zoning transaction was aborted because of one of the following conditions:• Zone Merge Received: The fabric is in the process of merging two zone databases.• Zone Config update Received: The fabric is in the process of updating the zone database.• Bad Zone Config: The new configuration is not viable.• Zoning Operation failed: A zoning operation failed.• Shell exited: The command shell has exited.• Unknown: An error was received for an unknown reason.• User Command: A user aborted the current zoning transaction.• Switch Shutting Down: The switch is currently shutting down.Most of these error conditions are transitory.Try again after sometime. Verify that only one administrator is modifying the zone database at a time.ZONE-1028MessageMessage TypeSeverityProbable CauseCommit zone DB larger than supported - greater than .LOGWARNINGIndicates that the zone database size is greater than the limit allowed by the fabric. The limit of the zonedatabase size depends on the lowest level switch in the fabric. Older switches have less memory andforce a smaller zone database for the entire fabric.410 Network OS Message Reference53-1002807-01

ZONE-1029 7RecommendedActionEdit the zone database to keep it within the allowable limit for the specific switches in your fabric. You canview the zone database size information using the show zoning operation-info command.ZONE-1029MessageMessage TypeSeverityProbable CauseRecommendedActionRestoring zone cfg from flash failed - bad config saved to [].LOGWARNINGIndicates that the zone configuration restored from the flash was faulty. This error will save the faultyzone configuration in the zoned core file directory.If the message persists, execute the copy support command and contact your switch service provider.ZONE-1032MessageMessage TypeSeverityProbable CauseRecommendedActionRBridge Max Zone DB size .LOGERRORIndicates that the specified RBridge does not have enough memory for the zone database beingcommitted.Reduce the size of the zone database by deleting some zones and retry the operation. Refer to theNetwork OS Administrator's Guide for instructions to delete a zone.ZONE-1033MessageMessage TypeSeverityProbable CauseRecommendedActionRBridge Lowest Max Zone DB size.LOGERRORIndicates that the specified RBridge has the lowest memory available for the zone database in the fabric.The zone database must be smaller than the memory available on this RBridge.Reduce the size of the zone database by deleting some zones and retry the operation. Refer to theNetwork OS Administrator's Guide for instructions to delete a zone.Network OS Message Reference 41153-1002807-01

7ZONE-1034ZONE-1034MessageMessage TypeSeverityProbable CauseRecommendedActionA new zone database file is created.LOGINFOIndicates that a new zone database file has been created.No action is required.ZONE-1035MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to rename to : error message.LOGERRORIndicates that the Network OS cannot rename the zone configuration file. Typically, the zoneconfiguration is too large for the memory available on the switch.Reduce the size of the zone database by deleting some zones and retry the operation. Refer to theNetwork OS Administrator's Guide for instructions to delete a zone.ZONE-1036MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to create : error message .LOGERRORIndicates that the Network OS cannot create the zone configuration file. Typically, the zone configurationis too large for the memory available on the switch.Reduce the size of the zone database by deleting some zones and retry the operation. Refer to theNetwork OS Administrator's Guide for instructions to delete a zone.412 Network OS Message Reference53-1002807-01

ZONE-1037 7ZONE-1037MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to examine : error message .LOGERRORIndicates that the Network OS cannot examine the zone configuration file. Typically, the zoneconfiguration is too large for the memory available on the switch.Reduce the size of the zone database by deleting some zones and retry the operation. Refer to theNetwork OS Administrator's Guide for instructions to delete a zone.ZONE-1038MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to allocate memory for : error message .LOGERRORIndicates that the Network OS cannot allocate enough memory for the zone configuration file. Typically,the zone configuration is too large for the memory available on the switch.Reduce the size of the zone database by deleting some zones and retry the operation. Refer to theNetwork OS Administrator's Guide for instructions to delete a zone.ZONE-1039MessageMessage TypeSeverityProbable CauseRecommendedActionUnable to read contents of : error message .LOGERRORIndicates that the Network OS cannot read the zone configuration file. Typically, the zone configuration istoo large for the memory available on the switch.Reduce the size of the zone database by deleting some zones and retry the operation. Refer to theNetwork OS Administrator's Guide for instructions to delete a zone.Network OS Message Reference 41353-1002807-01

7ZONE-1040ZONE-1040MessageMessage TypeSeverityProbable CauseRecommendedActionMerged zone database exceeds limit.LOGINFOIndicates that the Network OS cannot read the merged zone configuration file. Typically, the zoneconfiguration is too large for the memory available on the switch.Reduce the size of the zone database by deleting some zones and retry the operation. Refer to theNetwork OS Administrator's Guide for instructions to delete a zone.ZONE-1041MessageMessage TypeSeverityProbable CauseRecommendedActionUnstable link detected during merge at port ().LOGWARNINGIndicates a possible unstable link or a faulty cable.Verify that the small form-factor pluggable (SFP) transceiver and cable at the specified port are not faulty.Replace the SFP transceiver and cable if necessary.ZONE-1042MessageMessage TypeSeverityProbable CauseRecommendedActionThe effective configuration has been disabled.LOGINFOIndicates that the effective zone configuration has been disabled.Verify that the event was planned. If the event was planned, no action is required. If the event was notplanned, take appropriate action as defined by your enterprise security policy.ZONE-1043MessageMessage TypeSeverityProbable CauseThe Default Zone access mode is set to No Access.LOGINFOIndicates that the default zone access mode is set to No Access.414 Network OS Message Reference53-1002807-01

ZONE-1044 7RecommendedActionVerify that the event was planned. If the event was planned, no action is required. If the event was notplanned, take appropriate action as defined by your enterprise security policy.ZONE-1044MessageMessage TypeSeverityProbable CauseRecommendedActionThe Default Zone access mode is set to All Access.LOGINFOIndicates that the default zone access mode is set to All Access.Verify that the event was planned. If the event was planned, no action is required. If the event was notplanned, take appropriate action as defined by your enterprise security policy.ZONE-1045MessageMessage TypeSeverityProbable CauseRecommendedActionThe Default Zone access mode is already set to No Access.LOGINFOIndicates that the default zone access mode is already set to No Access.No action is required.ZONE-1046MessageMessage TypeSeverityProbable CauseRecommendedActionThe Default Zone access mode is already set to All Access.LOGINFOIndicates that the default zone access mode is already set to All Access.No action is required.Network OS Message Reference 41553-1002807-01

7ZONE-1046416 Network OS Message Reference53-1002807-01