Brocade Fabric OS User Manual

53-1003140-01	®
27 June 2014

Fabric OS

Message Reference

Supporting Fabric OS 7.3.0

© 2014, Brocade Communications Systems, Inc. All Rights Reserved.

Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and the On-Demand Data Center are trademarks of Brocade Communications Systems, Inc., in the United States and in other countries. Other brands and product names mentioned may be trademarks of others.

Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in this document may require an export license from the United States government.

The authors and Brocade Communications Systems, Inc. assume no liability or responsibility to any person or entity with respect to the accuracy of this document or any loss, cost, liability, or damages arising from the information contained herein or the computer programs that accompany it.

The product described by this document may contain open source software covered by the GNU General Public License or other open source license agreements. To find out which open source software is included in Brocade products, view the licensing terms applicable to the open source software, and obtain a copy of the programming source code, please visit http://www.brocade.com/support/oscd.

Brocade Communications Systems, Incorporated

Corporate and Latin American Headquarters	Asia-Pacific Headquarters
Brocade Communications Systems, Inc.	Brocade Communications Systems China HK, Ltd.
130 Holger Way	No. 1 Guanghua Road
San Jose, CA 95134	Chao Yang District
Tel: [phone]	Units 2718 and 2818
Fax: [phone]	Beijing 100020, China
E-mail: [e-mail]	Tel: [phone]
	Fax: [phone]
	E-mail: [e-mail]
European Headquarters	Asia-Pacific Headquarters
Brocade Communications Switzerland Sàrl	Brocade Communications Systems Co., Ltd. (Shenzhen WFOE)
Centre Swissair	Citic Plaza
Tour B - 4ème étage	No. 233 Tian He Road North
29, Route de l'Aéroport	Unit 1308 – 13th Floor
Case Postale 105	Guangzhou, China
CH-1215 Genève 15	Tel: [phone]
Switzerland	Fax: [phone]
Tel: [phone]	E-mail: [e-mail]
Fax: [phone]
E-mail: [e-mail]

Document History

Title	Publication	Summary of changes	Date
	number
Diagnostic and System Error	53-0000210-02	First release	March 2002
Message Reference v3.0, v4.0
Diagnostic and System Error	53-0000511-04	Major content reorganization	June 2003
Message Reference v3.1.0
Diagnostic and System Error	54-0000515-02	Major content reorganization	June 2003
Message Reference v4.1.0
Diagnostic and System Error	53-0000515-06	Minor editorial changes	October 2003
Message Reference v4.1.2
Diagnostic and System Error	53-0000515-07	Added FW and PLATFORM messages	December 2003
Message Reference v4.2.0
Diagnostic and System Error	53-0000515-08 Updated software and hardware support		March 2004
Message Reference v4.2.0

Title	Publication	Summary of changes	Date
	number
Fabric OS System Error Message	53-0000515-09	Updated for v4.4.0,	August 2004
Reference Manual		First RASLog release
Fabric OS System Error Message	53-0000515-10 Added 22 ZONE messages		April 2005
Reference Manual
Fabric OS System Error Message	53-0000515-11	Added FICU-1010, HAMK-1004, and	July 2005
Reference Manual		PLAT-1001
Fabric OS System Error Message	53-1000046-01	Added BM, FCR, IPS, FCIP, SEC, and	January 2006
Reference Manual		ZONE messages
Fabric OS System Error Message	53-1000046-02 Minor updates to a few messages.		June 2006
Reference Manual
Fabric OS Message Reference	53-1000242-01	Updated for Fabric OS v5.2.0:	September 2006
		-Changed doc title and number
		-Added the following new modules: IBPD,
		ICPD, ISCSI, ISNSCD.
		Added Audit messages: AUTH, CONF,
		HTTP, SEC, SNMP, SULB, ZONE.
		-Updated Introduction chapter with AUDIT
		log information.
		-Updated chapter titles.
Fabric OS Message Reference	53-1000437-01	Updated for Fabric OS v5.3.0:	June 2007
		-Added new chapters: AG, BKSW, IBD,
		IPAD, SAS.
		Revised and added new messages to:
		AUTH, CDR, CONF, EM, FABR, HAM, ISNS,
		ISW, PDM,SEC,TS, KTRC.SEC, TS.
		Revised/updated BL,BLL,FCPD, FICU,FW,
		HIL,LOG, SNMP, SULB,SWCH,SYSM,
		TRCE, ZOLB, ZONE.
		-Deleted USWD chapter.
		-Updated Introductory chapters.
		-Updated throughout: rebranding,
		supported hardware, CLI changes.
Fabric OS Message Reference	53-1000600-01	Updated for Fabric OS v6.0.0:	October 2007
		-Added new chapters: C2, ESS, FICON
		-Added new messages to: AG, BL, BM,
		C2, FCIP, ISW, NS, PLAT, SS, HIL.
		-Added Audit messages: SEC, SULB
		-Updated Introductory chapters.
Fabric OS Message Reference	53-1000600-02 Updated for Fabric OS v6.1.0:		Jun 2008
		-Revised and added new messages to:
		AG, BL, C2, EM, FABR, FCR, FCIP, FW,
		SEC, NS, PDM, PLAT, SULB, SWCH, ZONE,
		WEBD.
		-Added new Audit chapter: FW.
		-Added new Audit messages to: SEC.
		-Updated Introductory chapters.
Fabric OS Message Reference	53-1001116-01	Updated for Fabric OS v6.1.1_enc:	Aug 2008
		-Revised and added new messages to AG

-Added new chapters: CNM, CTAP, CVLC, CVLM, KAC, RKD, SPC, SPM.

-Added new Audit chapters: AG, FCIP, FICU, IPAD, PORT, SWCH, UCST. -Updated Introductory chapters.

Title	Publication	Summary of changes	Date
	number
Fabric OS Message Reference	53-1001157-01 Updated for Fabric OS v6.2.0:		November 2008
		-Revised and added new messages to
		FSS, KSWD, CTAP, CNM, CVLM, EM,
		FABR, FCIP, FW, HIL, FCR, SEC, SWCH,
		UCST, ZONE.
		-Added new chapters: CHASSIS, LFM,
		PMGR, TAPE.
		-Updated Introductory chapters.
Fabric OS Message Reference	53-1001338-01 Updated for Fabric OS v6.3.0:		July 2009
		-Modified a message to BKSW, BL,
		BKSW, BLL, CDR, CEE CONFIG, CONF,
		EM, FCOE, FCPD, FCPH, FCR, FICON,
		FICU, FLOD, FSPF, FSSM, FW,
		HAM,,HAMK, HIL, IPS, ISNS, L2SYS,
		MFIC, PDM, PLAT, PORT, RCS, RPCD,
		RTWR, SEC, SNMP, SWCH, TRCE, TRCK,
		WEBD, ZONE.
		-Added new messages to AG, AN, AUTH,
		BLS, C2, CDR, CEE, CONFIG, CHASSIS,
		CNM, CONF, CTAP, CVLC, CVLM, DAUTH,
		EM, FABR, FCIP, FCPH, FCR, FICON, FICU,
		FSPF, FSS, FW, HAM, HSL, KAC, KSWD,
		LANCE, LFM, MS, NS, NSM, PMGR, PORT,
		PSWP, RKD, SEC, SPC, SPM, SS, SULB,
		SWCH, TAPE, UCST, UPTH, XTUN, ZONE.
		-Added new chapters for LANCE, BLS, AN,
		CVLM, DAUTH, XTUN.
		-Updated Introductory chapters.
Fabric OS Message Reference	53-1001338-02 Updated for Fabric OS v6.3.0 patch:		November 2009
		-Modified a message to BL.
		-Added new messages to AG, BL, and
		FCOE.
		-Added new chapters for Audit CNM,
		Audit CVLM, and Audit SPM.
Fabric OS Message Reference	53-1001767-01 Updated for Fabric OS v6.4.0:		March 2010
		-Modified messages to FICU and FW.
		-Deleted messages to BL, FCOE and FW.

-Added new messages to AG, AN, AUTH, BL, C2, CNM, CONF, CVLC, CVLM, FABR, FICU, FW, HAM, HIL, MQ, MS, MSTP, NS, NSM, ONM, PS, PSWP, RKD, SEC, SPM, SS, SSM, SULB, SWCH and ZONE.

-Updated Introductory chapters.

Title	Publication	Summary of changes	Date
	number
Fabric OS Message Reference	53-1002149-01 Updated for Fabric OS v7.0.0:		April 2011
		-Added new chapters: C3, CAL,
		MCAST_SS, RTE, and VS.
		-Added new messages: AG, AN, ANV, BL,
		C2, CDR, CCFG, ECC, EM, ESS, FABR,
		FCOE, FCPH, FICN, FICU, FSPF, FW, HIL,
		IPAD, IPS, KAC, L2SYS, LACP, LOG, MS,
		NS, NSM, ONM, PDM, PS, RAS, RCS,
		SCN, SEC, SNMP, SPM, SS, SSM, SULB,
		SWCH, XTUN, ZEUS, and ZONE.
		-Modified messages: CDR, EM, FABR,
		FCOE, FICU, FW, HIL, L2SYS, PMGR, SEC,
		SPM, SS, and XTUN.
		-Deleted messages: C2, FCOE, FICU, and
		NSM.
		-Added new Audit chapters: ESS, MS,
		PMGR, and RAS.
		-Updated Introductory chapter.
Fabric OS Message Reference	53-1002448-01 Updated for Fabric OS v7.0.1:		December 2011
		-Added new messages: BL, CVLC, FICON,
		FSPF, and PS
		-Modified messages: AG, AN, C2, C3,
		CDR, FABR, FSPF, L2SYS, NSM, RTE, and
		ZONE.
		-Deleted messages: EM, FABR, ISCS,
		SAS, and ZOLB.
		-Updated Introductory chapter.
Fabric OS Message Reference	53-1002749-01 Updated for Fabric OS v7.1.0:		December 2012
		- Added new chapters: MM and VDR.
		- Added new messages: AG, ANV, BL, C2,
		C3, CDR, CONF, CVLM, EM, FABR, FCR,
		FSPF, FW, HAM, HIL, KAC, LOG, MS,
		NBFS, PLAT, PS, RAS, SEC, SS, SWCH,
		TRCE, VDR, XTUN, ZEUS, and ZONE.
		- Modified messages: AN, AUTH, BL, C2,
		C3, CDR, CAL, CNM, DOT1, FABR, FCOE,
		FCPD, FCR, FICU, FSPF, FSS, HIL, HSL,
		HTTP, IPS, KTRC, L2SS, LFM, PMGR, PS,
		RCS, RTWR, SEC, ZONE.
		- Deleted messages: EM, FCOE, HAM,
		SNMP, SYSC, UCST, ZONE.
		- Deleted modules: BLL, CER, FCIP, IBPD,
		and ICPD.
		- Updated Introductory chapter.
Fabric OS Message Reference	53-1002749-02	Modified C2, C3, and HSL messages.	March 2013
Fabric OS Message Reference	53-1002929-01 Updated for Fabric OS v7.2.0:		July 2013
		- Added new chapters: FV and MAPS

- Added new messages: AG, C2, C3, FCR, FSPF, KAC, PLAT, PORT, RAS, SEC, SS, SULB, -WEBD, and XTUN.

- Modified messages: AG, BL, C2, C3, FCR, FSS, HIL, MM, MQ, SEC, and SULB.

- Deleted messages: FW and SULB.

Title	Publication	Summary of changes	Date
	number
Fabric OS Message Reference	53-1003109-01	Updated for Fabric OS v7.2.1:	December 2013
		- Added new messages: FCR and PLAT.
		- Modified messages: BL.
Fabric OS Message Reference	53-1003140-01	Updated for Fabric OS v7.3.0:	June 2014

- Added new chapters: BCM, BLZ, and ESM.

- Added new messages: AG, AN, AUTH, BL, C2, C3, CVLM, EM, FV, HIL, MAPS, NBFS, NS, RAS, SEC, SNMP, SULB, SWCH, UCST, XTUN, and ZONE.

- Modified messages: C3, FABR, FCR, FV, NBFS, SNMP, and XTUN.

Contents

About This Document

How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii What’s new in this document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Command syntax conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Command examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Notes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Key terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Brocade resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Other industry resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx Getting technical help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xx Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Chapter 1 Introduction to System Messages

Overview of system messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 System message types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Message severity levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 System error message logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Configuring the syslog message destinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 System logging daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 System console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 SNMP trap recipient. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 SNMP inform recipient. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Port logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Changing the severity level of swEventTrap . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Commands for displaying and configuring the system message logs. . . . . . . . 13 Displaying message content on switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Fabric OS Message Reference	vii
53-1003140-01

Configuring system messages and attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Configuring event auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Disabling a RASLog message or module . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Enabling a RASLog message or module. . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Setting the severity level of a RASLog message . . . . . . . . . . . . . . . . . . . . . 17

Displaying system message logs and attributes. . . . . . . . . . . . . . . . . . . . . . . . . 17

Displaying RASLog messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Displaying RASLog messages one message at a time . . . . . . . . . . . . . . . . 18

Displaying Audit messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Displaying FFDC messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Displaying status of the system messages . . . . . . . . . . . . . . . . . . . . . . . . .20

Displaying the severity level of RASLog messages . . . . . . . . . . . . . . . . . . .20

Displaying RASLog messages by severity level . . . . . . . . . . . . . . . . . . . . . . 21

Displaying RASLog messages by message ID . . . . . . . . . . . . . . . . . . . . . . . 21

Displaying messages on a slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Viewing RASLog messages from Web Tools. . . . . . . . . . . . . . . . . . . . . . . . .22

Clearing the system message logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Clearing the system message log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Clearing the Audit message log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Reading the system messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Reading a RAS system message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Reading an Audit message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Responding to a system message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Looking up a system message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Gathering information about the problem . . . . . . . . . . . . . . . . . . . . . . . . . .26

Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

System module descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Chapter 2 Audit Messages

Chapter 3 FFDC Messages

Chapter 4

Log Messages

Chapter 5 Fabric OS System Messages

AG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

AN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

ANV Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151

viii	Fabric OS Message Reference
	53-1003140-01

AUTH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

BCM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

BKSW Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

BL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

BLS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

BLZ Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

BM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

C2 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204

C3 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213

CAL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223

CCFG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224

CDR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228

CHS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235

CNM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237

CONF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260

CTAP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265

CVLC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266

CVLM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279

DOT1 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294

ECC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .298

EM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299

ESM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319

ESS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332

ESW Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .335

EVMD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .338

FABR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339

FABS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .356

FBC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .361

FCMC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .362

FCOE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363

FCPD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

FCPH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .378

FCR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .380

FICN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .411

FICU Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .455

FKLB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .462

FLOD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .463

Fabric OS Message Reference	ix
53-1003140-01

FSPF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .465

FSS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .469

FSSM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .473

FV Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .475

FW Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .481

HAM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .584

HAMK Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .589

HIL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .591

HLO Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .609

HMON Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .611

HSL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .612

HTTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .615

IBD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .616

IPAD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617

IPS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .619

ISNS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .622

KAC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .626

KSWD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .631

KTRC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .632

L2SS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .634

L3SS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .637

LACP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .638

LANCE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .639

LFM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .640

LOG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .642

LSDB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .646

MAPS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .648

MCAST_SS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .660

MFIC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .667

MM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .669

MPTH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .670

MQ Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .671

MS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .673

MSTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .680

NBFS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .683

NS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .686

NSM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .691

x	Fabric OS Message Reference
	53-1003140-01

ONMD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .698

PDM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .700

PDTR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .708

PLAT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .709

PMGR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713

PORT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717

PS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .721

PSWP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .725

RAS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .728

RCS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .734

RKD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .739

RMON Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741

RPCD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742

RTE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745

RTWR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746

SCN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748

SEC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .750

SFLO Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .835

SNMP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .838

SPC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .841

SPM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .854

SS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .869

SSMD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874

SULB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .889

SWCH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .908

SYSC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .918

SYSM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .920

TAPE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .923

TRCE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .924

TRCK Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .929

TS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .931

UCST Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .934

UPTH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .938

VDR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .939

VS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .940

WEBD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .943

XTUN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .946

Fabric OS Message Reference	xi
53-1003140-01

ZEUS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .961

ZONE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .964

xii	Fabric OS Message Reference
	53-1003140-01

About This Document

In this chapter

•How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	xiii
•Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	xiii
•What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	xv
•Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	xvii
•Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	xix
•Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	xix
•Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	xx
•Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	xxi

How this document is organized

This document is organized to help you find the information that you want as quickly and easily as possible.

The document contains the following components:

•Chapter 1, “Introduction to System Messages” provides basic information on system messages.

•Chapter 2, “Audit Messages” includes a lookup list for Audit messages.

•Chapter 3, “FFDC Messages” includes a lookup list for FFDC messages.

•Chapter 4, “Log Messages” includes a lookup list for LOG messages.

•Chapter 5, “Fabric OS System Messages” provides message text, probable cause, recommended action, and severity for each of the messages.

Supported hardware and software

In those instances in which procedures or parts of procedures documented here apply to some switches but not to others, this guide identifies exactly which switches are supported and which are not.

Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc. for Fabric OS v7.3.0, documenting all possible configurations and scenarios is beyond the scope of this document.

Fabric OS Message Reference	xiii
53-1003140-01

The following hardware platforms are supported by this release of Fabric OS:

•Brocade 300

•Brocade 5100

•Brocade 5300

•Brocade 5410

•Brocade 5424

•Brocade 5430

•Brocade 5431

•Brocade 5432

•Brocade 5450

•Brocade 5460

•Brocade 5470

•Brocade 5480

•Brocade 6505

•Brocade M6505

•Brocade 6510

•Brocade 6520

•Brocade 6547

•Brocade 6548

•Brocade 7800 Extension Switch

•Brocade 7840 Extension Switch

•Brocade Encryption Switch

•Brocade DCX Backbone and Brocade DCX-4S Backbone

-FC8-16 port blade

-FC8-32 port blade

-FC8-48 port blade

-FC8-64 port blade

-FCOE10-24 DCX Blade

-FS8-18 Encryption Blade

-FX8-24 DCX Extension Blade

•Brocade DCX 8510-8 Backbone and Brocade DCX 8510-4 Backbone

-FC8-32E port blade

-FC8-48E port blade

-FC8-64 port blade

-FC16-32 port blade

-FC16-48 port blade

-FC16-64 port blade

-FCOE10-24 DCX Blade (not supported on Brocade DCX 8510-4)

xiv	Fabric OS Message Reference
	53-1003140-01

-FS8-18 Encryption Blade

-FX8-24 DCX Extension Blade

•Brocade VA-40FC

What’s new in this document

The following changes have been made since this document was last released:

•New modules added:

-BCM Messages

-BLZ Messages

-ESM Messages

•Information that was added:

-AG-1046

-AG-1047

-AN-1014

-AUTH-1048

-AUTH-1049

-BL-1053

-BL-1054

-BL-1055

-C2-1031

-C2-1032

-C3-1032

-C3-1033

-C3-1034

-CVLM-1017

-EM-1073

-EM-1134

-FV-3012

-FV-3013

-FV-3014

-HIL-1512

-HIL-1614

-HIL-1615

-HIL-1651

-MAPS-1011

-MAPS-1012

-NBFS-1005

Fabric OS Message Reference	xv
53-1003140-01

-NS-1013

-NS-1014

-NS-1015

-RAS-2004

-RAS-2005

-SEC-1341

-SEC-1342

-SEC-1343

-SEC-1344

-SEC-1343

-SNMP-1010

-SULB-1051

-SULB-1052

-SULB-1053

-SULB-1054

-SWCH-1027

-SWCH-1028

-SWCH-1029

-SWCH-1030

-UCST-1028

-UCST-1029

-XTUN-1009

-XTUN-4104

-XTUN-4105

-XTUN-4106

-XTUN-4107

-XTUN-4115

-XTUN-4120

-XTUN-4121

-XTUN-4122

-XTUN-4123

-XTUN-4124

-XTUN-4125

-XTUN-4126

-XTUN-4127

-XTUN-4137

-ZONE-1064

-ZONE-1065

-ZONE-1066

xvi	Fabric OS Message Reference
	53-1003140-01

•Information that was changed:

-C3-1012

-FABR-1052

-FCR-1048

-FV-3006

-FV-3007

-FV-3008

-FV-3009

-NBFS-1001

-SNMP-1005

-XTUN-1000

-XTUN-1001

-XTUN-1002

-XTUN-1003

-XTUN-1004

-XTUN-1006

-XTUN-1007

-XTUN-1008

-XTUN-1996

-XTUN-1997

For further information about new features and documentation updates for this release, refer to the release notes.

Document conventions

This section describes text formatting conventions and important notice formats used in this document.

Text formatting

The narrative-text formatting conventions that are used are as follows:

bold text	Identifies command names
	Identifies the names of user-manipulated GUI elements
	Identifies keywords and operands
	Identifies text to enter at the GUI or CLI
italic text	Provides emphasis
	Identifies variables
	Identifies paths and Internet addresses
	Identifies document titles
code text	Identifies CLI output
	Identifies command syntax examples

Fabric OS Message Reference	xvii
53-1003140-01

For readability, command names in the narrative portions of this guide are presented in mixed lettercase: for example, switchShow. In actual examples, command lettercase is all lowercase.

Command syntax conventions

Command syntax in this manual follows these conventions:

command	Commands are printed in bold.
--option, option	Command options are printed in bold.
-argument, arg	Arguments.
[ ]	Optional element.
variable	Variables are printed in italics. In the help pages, values are underlined or
	enclosed in angled brackets < >.
...	Repeat the previous element, for example “member[;member...]”
value	Fixed values following arguments are printed in plain font. For example,
	--show WWN
|	Boolean. Elements are exclusive. Example: --show -mode egress | ingress

Command examples

This book describes how to perform configuration tasks using the Fabric OS command line interface, but does not describe the commands in detail. For complete descriptions of all Fabric OS commands, including syntax, operand description, and sample output, see the Fabric OS Command Reference.

Notes, cautions, and warnings

The following notices and statements are used in this manual. They are listed below in order of increasing severity of potential hazards.

NOTE

A note provides a tip, guidance, or advice, emphasizes important information, or provides a reference to related information.

ATTENTION

An Attention statement indicates potential damage to hardware or data.

xviii	Fabric OS Message Reference
	53-1003140-01

CAUTION

A Caution statement alerts you to situations that can be potentially hazardous to you or cause damage to hardware, firmware, software, or data.

DANGER

A Danger statement indicates conditions or situations that can be potentially lethal or extremely hazardous to you. Safety labels are also attached directly to products to warn of these conditions or situations.

Key terms

For definitions specific to Brocade and Fibre Channel, see the technical glossaries on MyBrocade. See “Brocade resources” on page xix for instructions on accessing MyBrocade.

For definitions of SAN-specific terms, visit the Storage Networking Industry Association online dictionary at:

http://www.snia.org/education/dictionary

Notice to the reader

This document may contain references to the trademarks of the following corporations. These trademarks are the properties of their respective companies and corporations.

These references are made for informational purposes only.

Corporation	Referenced Trademarks and Products
Red Hat, Inc.	Red Hat, Red Hat Network, Maximum RPM, Linux Undercover

Additional information

This section lists additional Brocade and industry-specific documentation that you might find helpful.

Brocade resources

To get up-to-the-minute information, go to http://my.brocade.com to register at no cost for a user ID and password.

White papers, online demonstrations, and data sheets are available through the Brocade website at:

http://www.brocade.com/products-solutions/products/index.page

Fabric OS Message Reference	xix
53-1003140-01

For additional Brocade documentation, visit the Brocade website:

http://www.brocade.com

Release notes are available on the MyBrocade website.

Other industry resources

For additional resource information, visit the Technical Committee T11 website. This website provides interface standards for high-performance and mass storage applications for Fibre Channel, storage management, and other applications:

http://www.t11.org

For information about the Fibre Channel industry, visit the Fibre Channel Industry Association website:

http://www.fibrechannel.org

Getting technical help

Contact your switch support supplier for hardware, firmware, and software support, including product 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

•supportSave command output

•Detailed description of the problem, including the switch or fabric behavior immediately following the problem, and specific questions

•Description of any troubleshooting steps already performed and the results

•Serial console and Telnet session logs

•syslog message logs

2.Switch Serial Number

The switch serial number and corresponding bar code are provided on the serial number label, as illustrated below.

:

*FT00X0054E9

FT00X0054E9

The serial number label is located as follows:

•Brocade 300, 5100, 5300, 6505, M6505, 6520, 6547, 6548, 7800, 7840, VA-40FC, and Brocade Encryption Switch—On the switch ID pull-out tab located inside the chassis on the port side on the left.

xx	Fabric OS Message Reference
	53-1003140-01

•Brocade 5410, 5424, 5430, 5431, 5432, 5450, 5460, 5470, 5480—Serial number label attached to the module.

•Brocade 6510—On the pull-out tab on the front of the switch

•Brocade DCX and DCX 8510-8—On the port side of the chassis, on the lower right side and directly above the cable management comb.

•Brocade DCX-4S and DCX 8510-4—On the non-port side of the chassis, on the lower left side.

3.World Wide Name (WWN)

Use the licenseIdShow command to display the WWN of the chassis.

If you cannot use the licenseIdShow command because the switch is inoperable, you can get the WWN from the same place as the serial number, except for the Brocade DCX. For the Brocade DCX, access the numbers on the WWN cards by removing the Brocade logo plate at the top of the non-port side of the chassis.

Document feedback

Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. Forward your feedback to:

[e-mail]

Provide the title and version number of the document and as much detail as possible about your comment, including the topic heading and page number and your suggestions for improvement.

Fabric OS Message Reference	xxi
53-1003140-01

xxii	Fabric OS Message Reference
	53-1003140-01

	Chapter
Introduction to System Messages	1

In this chapter

•Overview of system messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

•Configuring the syslog message destinations . . . . . . . . . . . . . . . . . . . . . . . . . 5

•Changing the severity level of swEventTrap. . . . . . . . . . . . . . . . . . . . . . . . . . 11

•Commands for displaying and configuring the system message logs . . . . . 13

•Displaying message content on switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

•Configuring system messages and attributes . . . . . . . . . . . . . . . . . . . . . . . . 15

•Displaying system message logs and attributes . . . . . . . . . . . . . . . . . . . . . . 17

•Clearing the system message logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

•Reading the system messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

•Responding to a system message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

•System module descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Overview of system messages

This guide supports Fabric OS v7.3.0 and documents system messages that can help you diagnose and fix problems with a switch or fabric. The messages are organized alphabetically by module name. A module is a subsystem in the Fabric OS. Each module generates a set of numbered messages. For each message, this guide provides message text, probable cause, recommended action, and severity level. There may be more than one cause and more than one recommended action for any given message. This guide discusses the most probable cause and typical action recommended.

System message types

Fabric OS supports three types of system messages. A system message can be of one or more of the following types:

•RASLog messages

•Audit log messages

•FFDC messages

Fabric OS supports a different methodology for storing and accessing each type of message.

Fabric OS Message Reference	1
53-1003140-01

TABLE 1

1 Overview of system messages

RASLog messages

RASLog messages report significant system events (failure, error, or critical conditions) or information and are also used to show the status of the high-level user-initiated actions. RASLog messages are forwarded to the console, to the configured syslog servers, and to the SNMP management station through the Simple Network Management Protocol (SNMP) traps or informs.

The following is an example of a RASLog system message.

2012/10/25-17:51:05, [C3-1001], 937, CHASSIS, ERROR, switch, Port 18 failed due to SFP validation failure. Check if the SFP is valid for the configuration.

For information on displaying and clearing the RASLog messages, refer to “Displaying system message logs and attributes” on page 17.

Audit log messages

Event auditing is designed to support post-event audits and problem determination based on high-frequency events of certain types such as security violations, zoning configuration changes, firmware downloads, and certain types of fabric events. Audit messages flagged only as AUDIT are not saved in the switch error logs. The switch can be configured to stream Audit messages to the switch console and to forward the messages to specified syslog servers. The Audit log messages are not forwarded to an SNMP management station. There is no limit to the number of audit events.

The following is an example of an Audit message.

0 AUDIT, 2012/10/14-06:07:33 (UTC), [SULB-1003], INFO, FIRMWARE, admin/admin/192.0.2.2/telnet/CLI ad_0/switch, , Firmwarecommit has started.

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.

•Event Information - Information about the event.

The seven event classes described in Table 1 can be audited.

Event classes

Operand	Event class	Description
1	Zone	You can audit zone event configuration changes, but not the actual
		values that were changed. For example, you may receive a message
		that states “Zone configuration has changed,” but the message
		does not display the actual values that were changed.
2	Security	You can audit any user-initiated security event for all management
		interfaces. For events that have an impact on the entire fabric, an
		audit is only generated for the switch from which the event was
		initiated.
3	Configuration	You can audit configuration downloads of existing SNMP
		configuration parameters. Configuration uploads are not audited.
4	Firmware	You can audit configuration downloads of existing SNMP
		configuration parameters. Configuration uploads are not audited.

2	Fabric OS Message Reference
	53-1003140-01

		Overview of system messages		1
TABLE 1	Event classes (Continued)
Operand	Event class	Description
5	Fabric	You can audit Administration Domain-related changes.
6	FW	You can audit Fabric Watch (FW)-related changes.
7	LS	You can audit Virtual Fabric (Logical Switch)-related changes.
8	CLI	You can audit the CLI commands executed on the switch.
9	MAPS	You can audit Monitoring and Alerting Policy Suite (MAPS)-related
		changes.
N/A	RAS	Used to audit or track the RASLog messages or modules that are
		enabled or disabled using the rasAdmin command.

NOTE: The RAS class is not configurable, and it is always enabled internally.

Fabric OS v7.3.0 generates component-specific Audit messages.

Event auditing is a configurable feature, which is by default disabled. You must enable event auditing using the auditCfg --enable command to send the events to a configured remote host. Syslogd must be configured for logging audit messages. You can set up filters to screen out particular classes of events using the auditCfg command. The defined set of Audit messages is 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. For details on how to configure event auditing, refer to “Configuring event auditing” on page 15. For more details, refer to “Displaying Audit messages” on page 19 and “Reading an Audit message” on page 24.

FFDC messages

First Failure Data Capture (FFDC) is used to capture failure-specific data when a problem or failure is noted for the first time and before the switch reboots, or trace and log buffer get wrapped. All subsequent iterations of the same error are ignored. This critical debug information is saved in nonvolatile storage and can be retrieved using the supportSave command. The FFDC data is used for debugging or analyzing the problem. FFDC is intended for use by Brocade technical support.

FFDC is enabled by default. Execute the supportFfdc command to enable or disable FFDC. If FFDC is disabled, the FFDC daemon does not capture any data, even when a message with an FFDC attribute is logged.

The following is an example of the FFDC message.

2000/12/17-08:30:13, [SS-1000], 88, SLOT 6 | FFDC | CHASSIS, INFO, DCX, supportSave has uploaded support information to the host with IP address 192.0.2.2.

Message severity levels

Table 2 shows the four levels of severity for system messages, ranging from CRITICAL (1) to INFO

(4). In general, the definitions are wide ranging and are to be used as general guidelines for troubleshooting. For all cases, you must look at each specific error message description thoroughly before taking action.

Fabric OS Message Reference	3
53-1003140-01

1 Overview of system messages

TABLE 2		Severity levels of a message
Severity level		Description
1	= CRITICAL	Critical-level messages indicate that the software has detected serious problems that
		will cause a partial or complete failure of a subsystem if not corrected immediately; for
		example, a power supply failure or rise in temperature must receive immediate
		attention.
2	= ERROR	Error-level messages represent an error condition that does not impact overall system
		functionality significantly. For example, error-level messages might indicate time-outs
		on certain operations, failures of certain operations after retries, invalid parameters, or
		failure to perform a requested operation.
3	= WARNING	Warning-level messages highlight a current operating condition that should be
		checked or it may lead to a failure in the future. For example, a power supply failure in
		a redundant system relays a warning that the system is no longer operating in
		redundant mode unless the failed power supply is replaced or fixed.
4	= INFO	Info-level messages report the current non-error status of the system components: for
		example, detecting online and offline status of a fabric port.

System error message logging

The RASLog service generates and stores messages related to abnormal or erroneous system behavior. It includes the following features:

•All RASLog error messages are saved to nonvolatile storage by default.

•The system error message log can save a maximum of 1024 messages in random access memory (RAM).

•The system message log is implemented as a circular buffer. When more than the maximum entries are added to the log file, old entries are overwritten by new entries.

•Messages are numbered sequentially from 1 to 2,147,483,647 (0x7ffffff). The sequence number will continue to increase beyond the storage limit of 1024 messages. The sequence number can be reset to 1 using the errClear command. The sequence number is persistent across power cycles and switch reboots.

•The message log size is 256.

•Trace dump, FFDC, and core dump files can be uploaded to the FTP server using the supportSave command.

•Brocade recommends that you configure the syslogd facility as a management tool for error logs. This is particularly important for dual-domain switches because the syslogd facility saves messages from two logical switches as a single file and in sequential order. For more information, refer to “System logging daemon” on page 5.

•RASLog messages are streamed to the console, and are forwarded to the configured syslog servers and to the SNMP management station through the SNMP traps (in SNMPv1 and SNMPv3) or informs (in SNMPv3). Use the snmpConfig command to configure the SNMPv1 and SNMPv3 hosts and their configurations.

•Audit messages are streamed to the switch console, and are forwarded to the configured syslog servers. The Audit log messages are not forwarded to an SNMP management station.

4	Fabric OS Message Reference
	53-1003140-01

Configuring the syslog message destinations

1

Configuring the syslog message destinations

You can configure the Fabric OS to send the syslog messages to the following output locations: syslog daemon, system console, and SNMP management station.

System logging daemon

The system logging daemon (syslogd) is a process on UNIX, Linux, and some Windows systems that reads and logs messages as specified by the system administrator.

Fabric OS can be configured to use a UNIX-style syslogd process to forward system events and error 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. Configuring for syslogd involves configuring the host, enabling syslogd on the Brocade model, and, optionally, setting the facility level.

For the Brocade DCX family of switches, each control processor (CP) has a unique error log, depending on which CP was active when that message was reported. To fully understand message logging, you should enable the syslogd, because the logs on the host computer are maintained in a single merged file for both CPs and are in sequential order. Otherwise, you must examine the error logs in both CPs, particularly for events such as firmwareDownload or haFailover, for which the active CP changes.

For the Brocade DCX family of switches, any security violations that occur through Telnet, HTTP, or serial connections are not propagated between CPs. Security violations on the active CP are not propagated to the standby CP counters in the event of a failover, nor do security violations on the standby CP get propagated to the active CP counters.

Configuring a syslog server

To configure the switch to forward all system events and error messages to the syslogd of one or more servers, perform the following steps.

1.Log in to the switch as admin.

2.Execute the syslogdIpAdd IP address command to add a server to which system messages are forwarded.

switch:admin> syslogdipadd 192.0.2.2

You can configure up to six syslog servers to receive the syslog messages.

3. Execute the syslogdIpShow command to verify the syslog configuration on the switch.

switch:admin> syslogdipshow syslog.1 192.0.2.2

You can remove a configured syslog server using the syslogdIpRemove IP address command.

System console

The system console displays RASLog messages, Audit messages (if enabled), and panic dump messages. These messages are mirrored to the system console; they are always saved in one of the system logs.

Fabric OS Message Reference	5
53-1003140-01

1 Configuring the syslog message destinations

The system console displays messages only through the serial port. If you log in to a switch through the 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 errFilterSet command. All messages are still sent to the system message log and syslogd (if configured).

Setting the system console severity level

You can limit the types of messages that are logged to the console using the errFilterSet command. The system messages displayed on the console are filtered up to and include the configured severity level. You can choose one of the following severity levels: INFO, WARNING, ERROR, or CRITICAL.

To set the severity levels for the system console, perform the following steps.

1.Log in to the switch as admin.

2.Execute the errFilterSet [-d console -v severity] command to set the console severity level. The severity can be one of the following: INFO, WARNING, ERROR, or CRITICAL. The severity values are not case-sensitive.

For example, to set the filter severity level for the console to ERROR, enter the following command.

switch:admin> errfilterset -d console -v error

3. Execute the errFilterSet command to verify the configured filter settings.

switch:admin> errfilterset console: filter severity = ERROR

SNMP trap recipient

An unsolicited message that comes to the management station from the SNMP agent on the device is called a trap. When an event occurs and if the event severity level is at or below the set severity level, the SNMP trap, swEventTrap, is sent to the configured trap recipients. The VarBind in the Trap Data Unit contains the corresponding instance of the event index, time information, event severity level, the repeat count, and description. The following are the possible severity levels:

•None (0)

•Critical (1)

•Error (2)

•Warning (3)

•Informational (4)

•Debug (5)

By default, the severity level is set to None, implying all traps are filtered and therefore no event traps are received. When the severity level is set to Informational, all traps with the severity level of Informational, Warning, Error, and Critical are received. For more information on changing the severity level of swEventTrap, refer to “Changing the severity level of swEventTrap” on page 11.

NOTE

The Audit messages are not converted into swEventTrap.

6	Fabric OS Message Reference
	53-1003140-01

Configuring the syslog message destinations

1

The SNMP traps are unreliable because the trap recipient does not send any acknowledgment when 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 IP address must be configured on the switch. You can configure the SNMPv1 and SNMPv3 hosts to receive the traps.

For more information on the swEventTrap, refer to the Fabric OS MIB Reference.

Configuring the SNMPv1 trap recipient

Use the snmpConfig --set snmpv1 command to specify the recipient of the SNMP trap. To configure the SNMPv1 host to receive the trap, perform the following steps.

1.Log in to the switch as admin.

2.Execute the snmpConfig --set snmpv1 command to configure the SNMP trap recipient.

switch:admin> snmpconfig --set snmpv1

SNMP community and trap recipient configuration: Community (rw): [Secret C0de]

Trap Recipient's IP address : [192.0.2.2] Trap recipient Severity level : (0..5) [4] Trap recipient Port : (0..65535) [162] Community (rw): [OrigEquipMfr]

Trap Recipient's IP address : [fec0:60:22bc:200:313:72ff:fe64:78b2]

NOTE

To receive the traps, the management station IP address must be configured on the switch.

3. Execute the snmpConfig --show snmpv1 command to verify the SNMPv1 agent configuration.

switch:admin> snmpconfig --show snmpv1

SNMPv1 community and trap recipient configuration:

Community 1: Secret C0de (rw)

Trap recipient: 192.0.2.2

Trap port: 162

Trap recipient Severity level: 5

Community 2: OrigEquipMfr (rw)

Trap recipient: fec0:60:22bc:200:313:72ff:fe64:78b2

Trap port: 162

Trap recipient Severity level: 5

Community 3: private (rw)

Trap recipient: tools.lab.brocade.com

Trap port: 162

Trap recipient Severity level: 5

Community 4: public (ro)

Trap recipient: 192.0.10.10

Trap port: 65530

Trap recipient Severity level: 1

Community 5: common (ro)

Trap recipient: fec0:60:69bc:200:213:72ff:fe64:069f

Trap port: 11

Trap recipient Severity level: 2

Community 6: FibreChannel (ro)

Trap recipient: WT.org.brocade.com

Trap port: 65521

Fabric OS Message Reference	7
53-1003140-01

1 Configuring the syslog message destinations

Trap recipient Severity level: 2

SNMPv1:Enabled

Configuring the SNMPv3 trap recipient

To configure the SNMPv3 host to receive the trap, perform the following steps.

1.Log in to the switch as admin.

2.Execute the snmpConfig --set snmpv3 command to configure the SNMP trap recipient. Ignore the step to enable the SNMP informs “SNMP Informs Enabled”.

switch:admin> snmpconfig --set snmpv3

SNMP Informs Enabled (true, t, false, f): [false]

SNMPv3 user configuration(snmp user not configured in FOS user database will have physical AD and admin role as the default):

User (rw): [snmpadmin1]

Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3]

Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]): (2..2) [2]

User (rw): [snmpadmin2]

Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3]

Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]): (2..2) [2]

User (rw): [snmpadmin3]

Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3]

Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]): (2..2) [2]

User (ro): [snmpuser1]

Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3]

Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]): (2..2) [2]

User (ro): [snmpuser2]

Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3]

Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]): (2..2) [2]

User (ro): [snmpuser3]

Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3]

Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]): (2..2) [2]

SNMPv3 trap recipient configuration:

Trap Recipient's IP address : [192.0.2.2] UserIndex: (1..6) [1]

Trap recipient Severity level : (0..5) [1] Trap recipient Port : (0..65535) [35432] Trap Recipient's IP address : [192.0.10.10] UserIndex: (1..6) [2]

Trap recipient Severity level : (0..5) [5] Trap recipient Port : (0..65535) [162]

Trap Recipient's IP address : [192.0.20.20] [...]

NOTE

To receive the SNMP traps, the username, the authentication protocol, the UDP port number, and the privacy protocol must match between the switch and the management station.

8	Fabric OS Message Reference
	53-1003140-01