Dell Brocade M6505 Messages Reference Guide 7.1.0 Fabric OS Message

2015-01-05

: Dell Dell-Brocade-M6505-Messages-Reference-Guide-136289 dell-brocade-m6505-messages-reference-guide-136289 dell pdf

Open the PDF directly: View PDF PDF.
Page Count: 934

DownloadDell Dell-Brocade-M6505-Messages-Reference-Guide- Brocade 7.1.0 Fabric OS Message Reference  Dell-brocade-m6505-messages-reference-guide
Open PDF In BrowserView PDF
53-1002749-01
14 December 2012

Fabric OS
Message Reference
Supporting Fabric OS v7.1.0

®

Copyright © 2002-2012 Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, Brocade Assurance, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, MLX, NetIron, SAN Health, ServerIron,
TurboIron, VCS, and VDX are registered trademarks, and AnyIO, Brocade One, CloudPlex, Effortless Networking, ICX, NET Health,
OpenScript, and The Effortless Network are trademarks of Brocade Communications Systems, Inc., in the United States and/or in
other countries. Other brands, products, or service names mentioned may be trademarks of their respective owners.
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. shall have no liability or responsibility to any person or entity with
respect to any loss, cost, liability, or damages arising from the information contained in this book 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
Brocade Communications Systems, Inc.
130 Holger Way
San Jose, CA 95134
Tel: 1-408-333-8000
Fax: 1-408-333-8101
E-mail: info@brocade.com

Asia-Pacific Headquarters
Brocade Communications Systems China HK, Ltd.
No. 1 Guanghua Road
Chao Yang District
Units 2718 and 2818
Beijing 100020, China
Tel: +8610 6588 8888
Fax: +8610 6588 9999
E-mail: china-info@brocade.com

European Headquarters
Brocade Communications Switzerland Sàrl
Centre Swissair
Tour B - 4ème étage
29, Route de l'Aéroport
Case Postale 105
CH-1215 Genève 15
Switzerland
Tel: +41 22 799 5640
Fax: +41 22 799 5641
E-mail: emea-info@brocade.com

Asia-Pacific Headquarters
Brocade Communications Systems Co., Ltd. (Shenzhen WFOE)
Citic Plaza
No. 233 Tian He Road North
Unit 1308 – 13th Floor
Guangzhou, China
Tel: +8620 3891 2000
Fax: +8620 3891 2111
E-mail: china-info@brocade.com

Document History
Title

Publication
number

Summary of changes

Date

Diagnostic and System Error
Message Reference v3.0, v4.0

53-0000210-02

First release

March 2002

Diagnostic and System Error
Message Reference v3.1.0

53-0000511-04

Major content reorganization

June 2003

Diagnostic and System Error
Message Reference v4.1.0

54-0000515-02

Major content reorganization

June 2003

Diagnostic and System Error
Message Reference v4.1.2

53-0000515-06

Minor editorial changes

October 2003

Diagnostic and System Error
Message Reference v4.2.0

53-0000515-07

Added FW and PLATFORM messages

December 2003

Diagnostic and System Error
Message Reference v4.2.0

53-0000515-08

Updated software and hardware support

March 2004

Title

Publication
number

Summary of changes

Date

Fabric OS System Error Message
Reference Manual

53-0000515-09

Updated for v4.4.0,
First RASLog release

August 2004

Fabric OS System Error Message
Reference Manual

53-0000515-10

Added 22 ZONE messages

April 2005

Fabric OS System Error Message
Reference Manual

53-0000515-11

Added FICU-1010, HAMK-1004, and
PLAT-1001

July 2005

Fabric OS System Error Message
Reference Manual

53-1000046-01

Added BM, FCR, IPS, FCIP, SEC, and
ZONE messages

January 2006

Fabric OS System Error Message
Reference Manual

53-1000046-02

Minor updates to a few messages.

June 2006

Fabric OS Message Reference

53-1000242-01

Updated for Fabric OS v5.2.0:
-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.

September 2006

Fabric OS Message Reference

53-1000437-01

Updated for Fabric OS v5.3.0:
-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.

June 2007

Fabric OS Message Reference

53-1000600-01

Updated for Fabric OS v6.0.0:
-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.

October 2007

Fabric OS Message Reference

53-1000600-02

Updated for Fabric OS v6.1.0:
-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.

Jun 2008

Fabric OS Message Reference

53-1001116-01

Updated for Fabric OS v6.1.1_enc:
-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.

Aug 2008

Title

Publication
number

Summary of changes

Date

Fabric OS Message Reference

53-1001157-01

Updated for Fabric OS v6.2.0:
-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.

November 2008

Fabric OS Message Reference

53-1001338-01

Updated for Fabric OS v6.3.0:
-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.

July 2009

Fabric OS Message Reference

53-1001338-02

Updated for Fabric OS v6.3.0 patch:
-Modified a message to BL.
-Added new messages to AG, BL, and
FCOE.
-Added new chapters for Audit CNM,
Audit CVLM, and Audit SPM.

November 2009

Fabric OS Message Reference

53-1001767-01

Updated for Fabric OS v6.4.0:
-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.

March 2010

Title

Publication
number

Summary of changes

Date

Fabric OS Message Reference

53-1002149-01

Updated for Fabric OS v7.0.0:
-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.

April 2011

Fabric OS Message Reference

53-1002448-01

Updated for Fabric OS v7.0.1:
-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.

December 2011

Fabric OS Message Reference

53-1002749-01

Updated for Fabric OS v7.1.0:
- 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.

December 2012

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
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
53-1002749-01

vii

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

Log Messages

Chapter 3

Audit Messages

Chapter 4

FFDC Messages

Chapter 5

Fabric OS System Messages
AG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
AN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
ANV Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140

viii

Fabric OS Message Reference
53-1002749-01

AUTH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
BKSW Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
BL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
BLS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
BM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
C2 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
C3 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194
CAL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202
CCFG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203
CDR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207
CHS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214
CNM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216
CONF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239
CTAP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244
CVLC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245
CVLM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258
DOT1 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273
ECC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277
EM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278
ESS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .297
ESW Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300
EVMD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .303
FABR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .304
FABS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .321
FBC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .326
FCMC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327
FCOE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328
FCPD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .341
FCPH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .343
FCR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345
FICN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
FICU Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .418
FKLB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .425
FLOD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .426
FSPF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .428
FSS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .432
FSSM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .436

Fabric OS Message Reference
53-1002749-01

ix

FW Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .438
HAM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .541
HAMK Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .546
HIL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .548
HLO Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .565
HMON Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .567
HSL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .568
HTTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
IBD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .572
IPAD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .573
IPS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .575
ISNS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .578
KAC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .582
KSWD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .587
KTRC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .588
L2SS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .590
L3SS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .593
LACP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .594
LANCE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .595
LFM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .596
LOG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .598
LSDB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .602
MCAST_SS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .604
MFIC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .611
MM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .613
MPTH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .614
MQ Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .615
MS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
MSTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .624
NBFS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .627
NS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .629
NSM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .633
ONMD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .640
PDM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .642
PDTR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .650
PLAT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .651
PMGR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .653

x

Fabric OS Message Reference
53-1002749-01

PORT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .657
PS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .660
PSWP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .664
RAS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .667
RCS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .672
RKD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .677
RMON Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .679
RPCD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .680
RTE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .683
RTWR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .684
SCN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .686
SEC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .688
SFLO Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
SNMP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
SPC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .777
SPM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .790
SS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .805
SSMD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .810
SULB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .825
SWCH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .843
SYSC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .852
SYSM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .854
TAPE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .857
TRCE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .858
TRCK Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .863
TS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .865
UCST Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .868
UPTH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
VDR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .872
VS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .873
WEBD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
XTUN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .879
ZEUS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .889
ZONE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .892

Fabric OS Message Reference
53-1002749-01

xi

xii

Fabric OS Message Reference
53-1002749-01

About This Document

In this chapter
• How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
• Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
• What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
• Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
• Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
• Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
• Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
• Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xiii
xiii
xv
xvii
xix
xix
xx
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, “Log Messages” includes a lookup list for LOG messages.
Chapter 3, “Audit Messages” includes a lookup list for Audit messages.
Chapter 4, “FFDC Messages” includes a lookup list for FFDC 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.1.0, documenting all possible
configurations and scenarios is beyond the scope of this document.

Fabric OS Message Reference
53-1002749-01

xiii

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 5450
Brocade 5460
Brocade 5470
Brocade 5480
Brocade 6505
Brocade 6510
Brocade 6520
Brocade 7800
Brocade 8000
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
- FS8-18 Encryption Blade
- FX8-24 DCX Extension Blade
• Brocade VA-40FC

xiv

Fabric OS Message Reference
53-1002749-01

What’s new in this document
The following changes have been made since this document was last released:

• The lookup lists in Chapter 2 through Chapter 4 provide hyperlinks to messages by type (LOG,
Audit, and FFDC).

• Information that was added:
- AG Messages
- ANV Messages
- BL Messages
- C2 Messages
- C3 Messages
- CDR Messages
- CONF Messages
- CVLM Messages
- EM Messages
- FABR Messages
- FCR Messages
- FSPF Messages
- FW Messages
- HAM Messages
- HIL Messages
- KAC Messages
- LOG Messages
- MM Messages
- MS Messages
- NBFS Messages
- PLAT Messages
- PS Messages
- RAS Messages
- SEC Messages
- SS Messages
- SWCH Messages
- TRCE Messages
- VDR Messages
- XTUN Messages
- ZEUS Messages
- ZONE Messages

Fabric OS Message Reference
53-1002749-01

xv

• Information that was changed:
- AN Messages
- AUTH Messages
- BL Messages
- C2 Messages
- C3 Messages
- CDR Messages
- CAL Messages
- CNM Messages
- DOT1 Messages
- FABR Messages
- FCOE Messages
- FCPD Messages
- FCR Messages
- FICU Messages
- FSPF Messages
- FSS Messages
- HIL Messages
- HSL Messages
- HTTP Messages
- IPS Messages
- KAC Messages
- KTRC Messages
- L2SS Messages
- LFM Messages
- PMGR Messages
- PS Messages
- RCS Messages
- RTWR Messages
- SEC Messages
- ZONE Messages

xvi

Fabric OS Message Reference
53-1002749-01

• Information that was deleted:
- BLL System Messages
- CER System Messages
- EM Messages
- FCIP System Messages
- FCOE Messages
- HAM Messages
- IBPD System Messages
- ICPD System Messages
- SNMP Messages
- SYSC Messages
- UCST Messages
- ZONE Messages
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

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:

Fabric OS Message Reference
53-1002749-01

xvii

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.

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.

xviii

Fabric OS Message Reference
53-1002749-01

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
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

Fabric OS Message Reference
53-1002749-01

xix

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.

The serial number label is located as follows:

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

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

• 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.

xx

Fabric OS Message Reference
53-1002749-01

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:
documentation@brocade.com
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
53-1002749-01

xxi

xxii

Fabric OS Message Reference
53-1002749-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.1.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
53-1002749-01

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 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.

TABLE 1

2

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.

5

Fabric

You can audit Administration Domain-related changes.

Fabric OS Message Reference
53-1002749-01

Overview of system messages

TABLE 1

1

Event classes (Continued)

Operand Event class

Description

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.

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.1.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.

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
53-1002749-01

3

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.

• 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-1002749-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
53-1002749-01

5

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-1002749-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
53-1002749-01

7

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-1002749-01

Configuring the syslog message destinations

1

3. Execute the snmpConfig --show snmpv3 command to verify the SNMP agent configuration.
switch:admin> snmpconfig --show snmpv3
SNMP Informs = 0 (OFF)
SNMPv3 USM configuration:
User 1 (rw): snmpadmin1
Auth Protocol: noAuth
Priv Protocol: noPriv
User 2 (rw): snmpadmin2
Auth Protocol: MD5
Priv Protocol: noPriv
User 3 (rw): snmpadmin3
Auth Protocol: MD5
Priv Protocol: DES
User 4 (ro): snmpuser1
Auth Protocol: noAuth
Priv Protocol: noPriv
User 5 (ro): snmpuser2
Auth Protocol: noAuth
Priv Protocol: noPriv
User 6 (ro): snmpuser3
Auth Protocol: noAuth
Priv Protocol: noPriv
SNMPv3 Trap configuration:
Trap Entry 1: 192.0.2.2
Trap Port: 162
Trap User: snmpadmin1
Trap recipient Severity level: 1
Trap Entry 2: fe80::224:1dff:fef6:0f21
Trap Port: 162
[...]

SNMP inform recipient
An SNMP inform is similar to the SNMP trap except that the management station that receives an
SNMP inform acknowledges the system message with an SNMP response packet data unit (PDU).
If the sender does not receive the SNMP response PDU, the inform request can be sent again. An
SNMP inform request is saved in the switch memory until a response is received or the request
times out. The informs are more reliable and they consume more resources in the device and in the
network. Use SNMP informs only if it is important that the management station receives all event
notifications. Otherwise, use the SNMP traps. Brocade devices support SNMPv3 informs.

Configuring the SNMPv3 inform recipient
To configure the SNMPv3 host to receive the SNMP informs, perform the following steps.
1. Log in to the switch as admin.
2. Execute the snmpConfig --set snmpv3 command to configure the inform recipient. When
prompted to enable the SNMP informs, enter true or t. Informs are disabled by default.
switch:admin> snmpconfig --set snmpv3
SNMP Informs Enabled (true, t, false, f): [false] t
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]

Fabric OS Message Reference
53-1002749-01

9

1

Configuring the syslog message destinations

Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]):
(2..2) [2]
Engine ID: [0:0:0:0:0:0:0:0:0]
User (rw): [snmpadmin2]
Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3] 1
New Auth Passwd:
Verify Auth Passwd:
Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]):
(1..6) [2] 1
New Priv Passwd:
Verify Priv Passwd:
Engine ID: [0:0:0:0:0:0:0:0:0] 80:00:05:23:01:0A:23:34:1B
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]
Engine ID: [0:0:0:0:0:0:0:0:0]
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]
Engine ID: [0:0:0:0:0:0:0:0:0]
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]
Engine ID: [0:0:0:0:0:0:0:0:0]
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]
Engine ID: [0:0:0:0:0:0:0:0:0]
SNMPv3 trap recipient configuration:
Trap Recipient's IP address : [0.0.0.0] 192.0.2.2
UserIndex: (1..6) [1]
Trap recipient Severity level : (0..5) [0] 4
Trap recipient Port : (0..65535) [162]
Trap Recipient's IP address : [0.0.0.0] 192.0.10.10
UserIndex: (1..6) [2]
Trap recipient Severity level : (0..5) [0] 4
Trap recipient Port : (0..65535) [162]
Trap Recipient's IP address : [0.0.0.0]
Trap Recipient's IP address : [0.0.0.0]
Trap Recipient's IP address : [0.0.0.0]
Trap Recipient's IP address : [0.0.0.0]
Committing configuration.....done.

NOTE
To 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 management
station.
3. Execute the snmpConfig --show snmpv3 command to verify the SNMP agent configuration.
switch:admin> snmpconfig --show snmpv3
SNMP Informs = 1 (ON)
SNMPv3 USM configuration:
User 1 (rw): snmpadmin1
Auth Protocol: noAuth

10

Fabric OS Message Reference
53-1002749-01

Changing the severity level of swEventTrap

1

Priv Protocol: noPriv
Engine ID: 80:00:05:23:01:0a:23:34:21
User 2 (rw): snmpadmin2
Auth Protocol: MD5
Priv Protocol: DES
Engine ID: 80:00:05:23:01:0a:23:34:1b
User 3 (rw): snmpadmin3
Auth Protocol: noAuth
Priv Protocol: noPriv
Engine ID: 00:00:00:00:00:00:00:00:00
User 4 (ro): snmpuser1
Auth Protocol: noAuth
Priv Protocol: noPriv
Engine ID: 00:00:00:00:00:00:00:00:00
User 5 (ro): snmpuser2
Auth Protocol: noAuth
Priv Protocol: noPriv
Engine ID: 00:00:00:00:00:00:00:00:00
User 6 (ro): snmpuser3
Auth Protocol: noAuth
Priv Protocol: noPriv
Engine ID: 00:00:00:00:00:00:00:00:00
SNMPv3 Trap configuration:
Trap Entry 1: 192.0.2.2
Trap Port: 162
Trap User: snmpadmin1
Trap recipient Severity level: 4
Trap Entry 2: 192.0.10.10
Trap Port: 162
Trap User: snmpadmin2
Trap recipient Severity level: 4
Trap Entry 3: No trap recipient configured yet
Trap Entry 4: No trap recipient configured yet
Trap Entry 5: No trap recipient configured yet

Port logs
The Fabric OS maintains an internal log of all port activity. Each switch or logical switch maintains a
log file for each port. Port logs are circular buffers that can save up to 8000 entries per logical
switch. When the log is 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 are not persistent and are lost over power cycles and reboots.
Execute the portLogShow command to display the port logs for a particular port.
Execute the portLogEventShow command to display the specific events reported for each port.
Port log functionality is completely separate from the system message log. Port logs are typically
used to troubleshoot device connections.

Changing the severity level of swEventTrap
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. By default, the severity level is set at 0
(None), implying that all the event traps are sent. Use the snmpConfig --set mibCapability
command to modify the severity level of swEventTrap.

Fabric OS Message Reference
53-1002749-01

11

1

Changing the severity level of swEventTrap

To change the severity level of swEventTrap, perform the following steps.
1. Log in to the switch as admin.
2. Execute the snmpConfig --set mibCapability command to configure MIBs interactively. All the
supported MIBs and associated traps are displayed. You can change the DesiredSeverity for
swEventTrap to 1 (Critical), 2 (Error), 3 (Warning), or 4 (Informational). The default value is 0.
switch:admin> snmpconfig --set mibcapability
FE-MIB: YES
SW-MIB: YES
FA-MIB: YES
FICON-MIB: YES
HA-MIB: YES
FCIP-MIB: YES
ISCSI-MIB: YES
IF-MIB: YES
BD-MIB: YES
SW-TRAP: YES
swFault: YES
swSensorScn: YES
swFCPortScn: YES
swEventTrap: YES
DesiredSeverity:Informational
swFabricWatchTrap: YES
DesiredSeverity:None
swTrackChangesTrap: YES
swIPv6ChangeTrap: YES
swPmgrEventTrap: YES
swFabricReconfigTrap: YES
swFabricSegmentTrap: YES
swExtTrap: NO
swStateChangeTrap: NO
swPortMoveTrap: NO
swBrcdGenericTrap: YES
... 
SW-TRAP (yes, y, no, n): [yes]
swFault (yes, y, no, n): [yes]
swSensorScn (yes, y, no, n): [yes]
swFCPortScn (yes, y, no, n): [yes]
swEventTrap (yes, y, no, n): [yes]
DesiredSeverity: (0..4) [4] 3
swFabricWatchTrap (yes, y, no, n): [yes]
DesiredSeverity: (0..4) [0] 2
swTrackChangesTrap (yes, y, no, n): [yes]
swIPv6ChangeTrap (yes, y, no, n): [yes]
swPmgrEventTrap (yes, y, no, n): [yes]
[...]

3. Execute the snmpConfig --show mibCapability command to verify the severity level of
swEventTrap.
switch:admin> snmpconfig --show mibcapability
FE-MIB: YES
SW-MIB: YES
FA-MIB: YES
FICON-MIB: YES
HA-MIB: YES
FCIP-MIB: YES
ISCSI-MIB: YES

12

Fabric OS Message Reference
53-1002749-01

Commands for displaying and configuring the system message logs

1

IF-MIB: YES
BD-MIB: YES
SW-TRAP: YES
swFault: YES
swSensorScn: YES
swFCPortScn: YES
swEventTrap: YES
DesiredSeverity:Informational
swFabricWatchTrap: YES
DesiredSeverity:Critical
swTrackChangesTrap: YES
swIPv6ChangeTrap: YES
swPmgrEventTrap: YES
swFabricReconfigTrap: YES
[...]

Commands for displaying and configuring the system message logs
Table 3 describes commands that you can use to view or configure the system message logs. Most
commands require the admin access level. For detailed information on required access levels and
commands, refer to the Fabric OS Command Reference.

TABLE 3

Commands for viewing or configuring the system parameters and message logs

Command

Description

auditCfg

Configures the audit message log.

auditDump

Displays or clears the audit log.

errClear

Clears all error log messages for all switch instances on this control processor (CP).

errDelimiterSet

Sets the error log start and end delimiter for messages pushed to the console.

errDump

Displays the entire error log, without page breaks. Use the -r option to show the
messages in reverse order, from newest to oldest.

errFilterSet

Sets an error severity filter for the system console.

errModuleShow

Displays all the defined error log modules.

errShow

Displays the entire error log, with page breaks. Use the -r option to show the messages
in reverse order, from newest to oldest.

pdShow

Displays the contents of the panic dump and core dump files.

portErrShow

Displays the port error summary.

portLogClear

Clears the port log. If the port log is disabled, this command enables it.

portLogDisable

Disables the port log facility.

portLogDump

Displays the port log, without page breaks.

portLogDumpPort

Displays the port log of the specified port, without page breaks.

portLogEnable

Enables the port log facility.

portLogEventShow

Displays which port log events are currently being reported.

portLoginShow

Displays port logins.

portLogPdisc

Sets or clears the debug pdisc_flag.

portLogReset

Enables the port log facility.

Fabric OS Message Reference
53-1002749-01

13

1

Displaying message content on switch

TABLE 3

Commands for viewing or configuring the system parameters and message logs (Continued)

Command

Description

portLogResize

Resizes the port log to the specified number of entries.

portLogShow

Displays the port log, with page breaks.

portLogShowPort

Displays the port log of the specified port, with page breaks.

portLogTypeDisable

Disables an event from reporting to the port log. Port log events are described by the
portLogEventShow command.

portLogTypeEnable

Enables an event to report to the port log. Port log events are described by the
portLogEventShow command.

rasAdmin

Used to enable or disable logging for selected messages or modules, to change the
default severity level for a specified message, and to display configured RASLog
message settings.

rasMan

Displays message documentation on switch.

setVerbose

Sets the verbose level of a particular module within the Fabric OS.

snmpConfig

Manages the SNMP agent configuration.

supportFfdc

Enables and disables FFDC.

supportFtp

Sets, clears, or displays support FTP parameters or a time interval to check the FTP
server.

supportSave

Collects RASLog, trace files, and supportShow (active CP only) information for the local
CP and then transfers the files to an FTP server. The operation can take several
minutes.

supportShow

Executes a list of diagnostic and error display commands. This output is used by your
switch service provider to diagnose and correct problems with the switch. The output
from this command is very long.

syslogdFacility

Changes the syslogd facility.

syslogdIpAdd

Adds an IP address as a recipient of system messages.

syslogdIpRemove

Removes an IP address as a recipient of system messages.

syslogdIpShow

Views the currently configured IP addresses that are recipients of system messages.

traceDump

Displays, initiates, or removes a Fabric OS module trace dump.

Displaying message content on switch
Beginning with Fabric OS v7.1.0, you can view the message documentation such as the message
text, message type, class (for audit messages), message severity, cause, and action on the switch
console by using the rasMan message_ID command.
To display the message documentation on switch, perform the following steps.
1. Log in to the switch as admin.
2. Use the rasMan message_ID command to display the documentation of a message. The
message_ID values are case-sensitive.

14

Fabric OS Message Reference
53-1002749-01

Configuring system messages and attributes

1

For example, execute the following command to display the documentation for PS-1007.
switch:admin> rasman PS-1007
Log Messages
MESSAGE
PS-1007 - Failed to add
Fabricmode
domain=. .

PS-1007(7m)

Top

Talker

on

MESSAGE TYPE
LOG
SEVERITY
WARNING
PROBABLE CAUSE
Indicates that FC Routing (FCR) is enabled on the
fabric.

specified

RECOMMENDED ACTION
Top Talker cannot be installed on a fabric with FCR service
enabled. In case Top Talker must be installed on a fabric,
disable FCR using the fosconfig --disable fcr command.

Configuring system messages and attributes
This section provides information on configuring the system message logs and its attributes. All
admin-level commands mentioned in this section are used to enable or disable only the external
messages.

Configuring event auditing
To configure event auditing, perform the following steps.
1. Log in to the switch as admin.
2. Execute the auditCfg --enable command to enable the audit feature.
switch:admin> auditcfg --enable
Audit filter is enabled.

3. Execute the auditCfg --class command to configure the event classes you want to audit.
switch:admin> auditcfg --class 1,2,3,4,5,6,7,8
Audit filter is configured.

NOTE
The class option 9 (MAPS) is for internal use only. The RAS class is not configurable, and it is
always enabled internally.
4. Execute the auditCfg --severity severity level command if you want to set the Audit severity
level. By default, all messages are logged. When the severity is set, only messages with the
configured severity and higher are displayed. Valid values for severity level are INFO, WARNING,
ERROR, and CRITICAL
switch:admin> auditcfg --severity ERROR

Fabric OS Message Reference
53-1002749-01

15

1

Configuring system messages and attributes

5. Execute the auditCfg --show command to verify the configuration.
switch:admin> auditcfg --show
Audit filter is enabled.
1-ZONE
2-SECURITY
3-CONFIGURATION
4-FIRMWARE
5-FABRIC
6-FW
7-LS
8-CLI
Severity level: ERROR

You must configure the syslog daemon to send the Audit events to a configured remote host using
the syslogdIpAdd command. For more information on configuring the syslog server, refer to
“Configuring a syslog server” on page 5.

Disabling a RASLog message or module
To disable a single RASLog message or all messages in a module, perform the following steps.
1. Log in to the switch as admin.
2. Use the following commands to disable a single RASLog message or all messages that belong
to a module:

• Execute the rasadmin --disable -log messgae_ID command to disable a RASLog message.
For example, execute the following command to disable the BL-1001 message.
switch:admin> rasadmin --disable -log BL-1001
2012/07/20-13:30:41, [LOG-1005], 378, SLOT 4 | CHASSIS, INFO, switch, Log
message NSM-1009 has been disabled.

Use the rasadmin --show -log messgae_ID command to verify the status of the message.

• Execute the rasadmin --disable -module module_ID command to disable all messages in a
module. For example, execute the following command to disable all messages that belong
to the BL module.
switch:admin> rasadmin --disable -module BL
2012/07/20-13:28:37, [LOG-1007], 375, SLOT 4 | CHASSIS, INFO, switch, Log
Module BL has been disabled.

Use the rasadmin --show -module module_ID command to verify the status of the
messages that belong to a module.

NOTE
You cannot disable Audit and FFDC messages using the rasAdmin command.

16

Fabric OS Message Reference
53-1002749-01

Displaying system message logs and attributes

1

Enabling a RASLog message or module
To enable a single RASLog message or all messages in a module that were previously disabled,
perform the following steps.
1. Log in to the switch as admin.
2. Use the following commands to enable a single RASLog message or all messages that belong
to a module:

• Execute the rasadmin --enable -log messgae_ID command to enable a single RASLog
message that has been disabled.
For example, execute the following command to enable BL-1001 message that was
previously disabled.
switch:admin> rasadmin --enable -log BL-1001
2012/10/15-13:24:30, [LOG-1006], 373, SLOT 4 | CHASSIS, INFO, switch, Log
message BL-1001 has been enabled.

Use the rasadmin --show -log messgae_ID command to verify the status of the message.

• Execute the rasadmin --enable -module module_ID command to enable all messages in a
module. For example, execute the following command to enable to all previously disabled
BL messages.
switch:admin> rasadmin --enable -module BL
2012/10/15-13:28:37, [LOG-1007], 375, SLOT 4 | CHASSIS, INFO, switch, Log
Module BL has been enabled.

Use the rasadmin --show -module module_ID command to verify the status of the
messages that belong to a module.

Setting the severity level of a RASLog message
To change the default severity level of a RASLog message, perform the following steps.
1. Log in to the switch as admin.
2. Use the rasadmin --set -log message_ID -severity [DEFAULT | INFO | WARNING | ERROR |
CRITICAL] to change the severity level of a message. For example, execute the following
command to change the severity level of C2-1004 message to WARNING.
switch:admin> rasadmin --set -log C2-1004 -severity WARNING

3. Use the rasadmin --show -severity message_ID command to verify the severity of the message.
switch:admin> rasadmin --show -severity C2-1004
Message
Severity
C2-1004 :
WARNING

Displaying system message logs and attributes
This section provides information on displaying the system message logs. These procedures are
valid for all the supported platforms.

Fabric OS Message Reference
53-1002749-01

17

1

Displaying system message logs and attributes

Displaying RASLog messages
To display the system message log on a switch with no page breaks, perform the following steps.
You can display the messages in reverse order using the reverse option. To display message logs in
all switches (logical switches), use the all option.
1. Log in to the switch as admin.
2. Enter the errDump command at the command line.
switch:admin> errdump
Version: v7.1.0
2000/12/17-05:54:30, [HAM-1004], 1, CHASSIS, INFO, switch, Processor rebooted
- Reset
2000/12/17-05:55:04, [ZONE-1034], 2, FID 128, INFO, switch, A new zone
database file is created.
2000/12/17-05:55:04, [FCR-1069], 3, FID 128, INFO, switch, The FC Routing
service is enabled.
2000/12/17-05:55:04, [FCR-1068], 4, FID 128, INFO, switch, The FC Routing
service is disabled.
2000/12/17-05:55:11, [EM-1034], 5, CHASSIS, ERROR, switch, PS 2 set to faulty,
rc=2000e.
[...]

Displaying RASLog messages one message at a time
To display the system message log one message at a time, perform the following steps.
1. Log in to the switch as admin.
2. Enter the errShow command at the command line.
switch:admin> errshow
Version: v7.1.0
2011/11/11-05:54:30, [HAM-1004], 1, CHASSIS, INFO, switch, Processor rebooted
- Reset
Type  to continue, Q to stop:
2011/11/11-05:55:04, [ZONE-1034], 2, FID 128, INFO, switch, A new zone
database file is created.
Type  to continue, Q to stop:
2011/11/11-05:55:04, [FCR-1069], 3, FID 128, INFO, switch, The FC Routing
service is enabled.
Type  to continue, Q to stop:
[...]

18

Fabric OS Message Reference
53-1002749-01

Displaying system message logs and attributes

1

Displaying Audit messages
To display the Audit messages, perform the following steps. Beginning with Fabric OS v7.1.0
release, the RAS-3005 message is generated for each CLI command executed on switch and is
saved in the Audit message log.
1. Log in to the switch as admin.
2. Enter the auditDump -s command at the command line.
switch:admin> auditdump -s
0 AUDIT, 2011/01/14-06:06:49 (UTC), [RAS-2001], INFO, SYSTEM,
admin/admin/192.0.2.2/telnet/CLI, ad_0/switch/FID 128, , Audit message log is
enabled.
2 AUDIT, 2011/01/14-06:07:03 (UTC), [SEC-3020], INFO, SECURITY,
admin/admin/192.0.2.2/telnet/CLI ad_0/switch, , Event: login, Status: success,
Info: Successful login attempt via SERIAL.
3 AUDIT, 2011/01/14-06:07:33 (UTC), [SULB-1003], INFO, FIRMWARE,
admin/admin/192.0.2.2/telnet/CLI ad_0/switch, , Firmwarecommit has started.
4 AUDIT, 2011/12/11-10:08:58 (UTC), [SULB-1004], INFO, FIRMWARE,
admin/admin/192.0.2.2/telnet/CLI ad_0/switch, , Firmwarecommit has completed.
5 AUDIT, 2012/05/23-03:45:15 (UTC), [RAS-3005], INFO, CLI,
admin/admin/NONE/console/CLI, ad_0/switch/CHASSIS, , CLI: clihistory --all
6 AUDIT, 2012/05/23-04:12:04 (UTC), [RAS-3005], INFO, CLI,
admin/admin/NONE/console/CLI, ad_0/switch/CHASSIS, , CLI: auditdump -s
[...]

Displaying FFDC messages
To display the saved FFDC messages, perform the following steps.
1. Log in to the switch as admin.
2. Enter the errDump --attribute FFDC command at the command line.
switch:admin> errDump --attribute FFDC
Fabric OS: v7.1.0
2012/10/15-10:39:02, [LOG-1002], 4496, FFDC, WARNING, switch, A log
message was not recorded.
2012/10/15-10:39:18, [RAS-1001], 4496, FFDC, WARNING, switch, First
failure data capture (FFDC) event occurred.
[...]

Fabric OS Message Reference
53-1002749-01

19

1

Displaying system message logs and attributes

Displaying status of the system messages
To display the status of the system message, perform the following steps.
1. Log in to the switch as admin.
2. Use the following commands to display the status of all messages in the log, a single message,
or all messages that belong to a module:

• Execute the rasadmin --show -all command to the status of all RASLog messages in the
system log.
switch:admin> rasadmin
Message
Status
FCIP-1000
ENABLED
FCIP-1001
ENABLED
FCIP-1002
ENABLED
[...]

--show -all
Default Severity
CRITICAL
INFO
INFO

Current Severity
CRITICAL
ERROR
INFO

• Execute the rasadmin --show -log message_ID command to display the status of a single
RASLog message.
switch:admin> rasadmin --show -log IPAD-1002
Message
Status
Default Severity
Current Severity
IPAD-1002
DISABLED
INFO
INFO

• Execute the rasadmin --show -module module_ID command to display the status of all
messages that belong to the module.
switch:admin> rasadmin --show -module ECC
Message
Status
Default Severity
Current Severity
ECC-1000 ENABLED
ERROR
ERROR
ECC-1001 DISABLED ERROR
WARNING

• Execute the rasadmin --show -disabled command to display the list of all RASLog
messages that are disabled.
switch:admin> rasadmin --show -disabled
Message
Status
CDR-1001
:
DISABLED
CDR-1003
:
DISABLED
CDR-1004
:
DISABLED
ECC-1001
:
DISABLED
IPAD-1002
:
DISABLED

Displaying the severity level of RASLog messages
To display the severity level of a RASLog message, perform the following steps.
1. Log in to the switch as admin.
2. Use the rasadmin --show -severity message_ID command to display the severity level of a
RASLog message. For example, execute the following command to display the status of the
SEC-1203 message.
switch:admin> rasadmin --show -severity SEC-1203
Message
Severity
SEC-1203 :
WARNING

20

Fabric OS Message Reference
53-1002749-01

Displaying system message logs and attributes

1

Displaying RASLog messages by severity level
To display the RASLog messages based on the severity level, perform the following steps.
1. Log in to the switch as admin.
2. Execute the errdump --severity [DEFAULT | INFO | WARNING | ERROR | CRITICAL] command.
For more information on message severity levels, refer to “Message severity levels” on page 3.
You can set the count of messages to display using the count option. The following example
filters messages by severity level of ERROR.
switch:admin> errdump --count 4 --severity ERROR
Fabric OS: v7.1.0
2012/10/24-11:23:24, [C3-1001], 12, CHASSIS, ERROR, switch, Port 4 failed due
to SFP validation failure. Check if the SFP is valid for the configuration.
2012/10/24-11:23:24, [C3-1001], 13, CHASSIS, ERROR, switch, Port 5 failed due
to SFP validation failure. Check if the SFP is valid for the configuration.
2012/10/24-11:23:25, [C3-1001], 14, CHASSIS, ERROR, switch, Port 18 failed due
to SFP validation failure. Check if the SFP is valid for the configuration.
2012/10/24-11:46:14, [C3-1001], 27, CHASSIS, ERROR, switch, Port 4 failed due
to SFP validation failure. Check if the SFP is valid for the configuration.

Displaying RASLog messages by message ID
To display the RASLog messages based on the message ID, perform the following steps.
1. Log in to the switch as admin.
2. Execute the errdump --message message_ID command. The following example displays all
instances of the message HAM-1004.
switch:admin> errdump --message HAM-1004
Fabric OS: v7.1.0
2012/11/27-16:18:38, [HAM-1004], 1, CHASSIS, INFO, switch, Processor rebooted
- Reset.
2012/11/27-17:26:44, [HAM-1004], 90, CHASSIS, INFO, switch, Processor rebooted
- FirmwareDownload.
2012/11/27-21:06:25, [HAM-1004], 201, CHASSIS, INFO, switch, Processor
rebooted - FirmwareDownload.
[...]

Displaying messages on a slot
To display the saved messages for a specific slot, perform the following steps.
1. Log in to the switch as admin.
2. Execute the errdump --slot slot_num command.
switch:admin> errdump --slot 4
Fabric OS: v7.1.0
2012/06/19-03:26:44, [HAM-1004], 31, SLOT 4 | CHASSIS, INFO, switch, Processor
rebooted - Reboot.

Fabric OS Message Reference
53-1002749-01

21

1

Clearing the system message logs

2012/06/19-03:26:44, [SULB-1003], 32, SLOT 4 | CHASSIS, INFO, switch,
Firmwarecommit has started.
2012/06/19-03:26:44, [IPAD-1001], 33, SLOT 4 | CHASSIS, INFO, switch, CP/1
IPv6 manual fe80::224:38ff:fe1b:4400 DHCP Off.
2012/06/19-03:29:15, [IPAD-1000], 48, SLOT 4 | CHASSIS, INFO, switch, CP/0
Ether/0 IPv6 autoconf fd00:60:69bc:816:205:1eff:fe84:3f49/64 tentative DHCP
Off.
[...]

NOTE
The slot option is not supported on the non-bladed systems.

Viewing RASLog messages from Web Tools
To view the system message log for a switch from Web Tools, perform the following steps.
1. Launch Web Tools.
2. Select the desired switch from the Fabric Tree. The Switch View displays.
3. Click the Switch Events tab. You can view the switch events and messages in the Switch Events
Report displayed.
In dual-domain switches, an Event button exists for each logical switch. Only messages relating to
that switch (and chassis) will be displayed.

Clearing the system message logs
This section provides information on clearing the system message logs. These procedures are valid
for all the supported platforms.

Clearing the system message log
To clear the system message log for a particular switch instance, perform the following steps.
1. Log in to the switch as admin.
2. Execute the errClear command to clear all messages from memory.

NOTE
For products that have a single processor, all error log messages are cleared. For products that have
multiple processors, this command only clears the error logs of the processor from which it is
executed.

22

Fabric OS Message Reference
53-1002749-01

Reading the system messages

1

Clearing the Audit message log
To clear the Audit message log for a particular switch instance, perform the following steps.
1. Log in to the switch as admin.
2. Execute the auditDump -c command to clear all Audit messages from memory.

Reading the system messages
This section provides information about reading the RASLog and Audit messages.

Reading a RAS system message
This section provides information about reading system messages.
The following example shows the format of a RAS system error message.
, [], , , , ,


The following example shows a sample message from the error log.
2011/02/10-14:18:04, [SS-1000], 88, SLOT 6 | FFDC | CHASSIS, INFO, ESNSVT_DCX,
supportSave has uploaded support information to the host with IP address
192.0.2.2.
2011/02/10-14:13:34, [SS-1001], 87, SLOT 6/1 | FFDC | CHASSIS, WARNING,
ESNSVT_DCX, supportSave's upload operation to host IP address aborted.
2011/02/10-15:44:51, [SEC-1203], 89, SLOT 6 | FFDC | FID 128, INFO, ESNSVT_DCX,
Login information: Login successful via TELNET/SSH/RSH. IP Addr:192.0.2.2.

NOTE
Any reference to slot 0 in a system message is a reference to the blade within the switch platform,
for example, Brocade DCX contains FC8-48 blade, FC8-32 blade, FC8-16 blade, and so on.
The fields in the error message are described in Table 4.

TABLE 4

System message field description

Variable name

Description

Time Stamp

The system time (UTC) when the message was generated on the switch. The
RASLog subsystem supports an internationalized time stamp format based on
the “LOCAL” setting.

Event ID

The message module and number. These values uniquely identify each
message in the Fabric OS and reference the cause and actions recommended
in this manual. Note that not all message numbers are used; there can be
gaps in the numeric message sequence.

Fabric OS Message Reference
53-1002749-01

23

1

Reading the system messages

TABLE 4

System message field description (Continued)

Variable name

Description

Sequence Number

The error message position in the log. When a new message is added to the
log, this number is incremented by 1.
The message sequence number starts at 1 after a firmwareDownload and will
increase up to a value of 2,147,483,647 (0x7ffffff).
The sequence number continues to increase after the message log wraps
around, i.e. the oldest message in the log is deleted when a new message is
added. The sequence number can be reset to 1 using the errClear command.
The sequence number is persistent across power cycles and switch reboots.

Flags

For most messages, this field contains a space character (null value)
indicating that the message is neither an AUDIT or FFDC message. Messages
may contain the following values:
• FFDC – Indicates that additional first failure data capture information has
also been generated for this event.
• FID – The Fabric ID that can range from 0 to 128. FID 128 means the
message was generated by the default switch instance.
• CHASSIS – The message that was generated by the chassis instance.
• SLOT number – Indicates the message was generated from slot # blade
main CPU.
• SLOT #/1 – Indicates the message was generated from slot # blade
Co-CPU.

Severity Level

The severity of the error, which can be one of the following:
1 – CRITICAL
2 – ERROR
3 – WARNING
4 – INFO

•
•
•
•

Switch name

The defined switch name or the chassis name of the switch depending on the
action; for example, high availability (HA) messages typically show the chassis
name, and login failures show the logical switch name.
This value is truncated if it exceeds 16 characters in length. Run either the
chassisName command to name the chassis or the switchName command to
rename the logical switch.

Event-specific information

A text string explaining the error encountered and providing parameters
supplied by the software at runtime.

Reading an Audit message
Compared to RASLog error messages, messages flagged as AUDIT provide additional user and
system-related information of interest for post-event auditing and troubleshooting the problem.
The following example shows the format of the Audit event message.
 AUDIT, , [], , ,
////, /, , 

The following is a sample Audit event message.
0 AUDIT, 2005/12/10-09:54:03, [SEC-1000], WARNING, SECURITY,
JohnSmith/root/192.0.2.2/Telnet/CLI, Domain A/JohnsSwitch, , Incorrect password
during login attempt.

24

Fabric OS Message Reference
53-1002749-01

Reading the system messages

1

The fields in the error message are described in Table 5.

TABLE 5

Audit message field description

Variable name

Description

Sequence Number

The error message position in the log.

Audit flag

Identifies the message as an Audit message.

Time Stamp

The system time (UTC) when the message was generated on the switch. The
RASLog subsystem will support an internationalized time stamp format
based on the “LOCAL” setting.

Event ID

The message module and number. These values uniquely identify each
message in the Fabric OS and reference the cause and actions
recommended in this manual. Note that not all message numbers are used;
there can be gaps in the numeric message sequence.

Severity

Event Class

The severity of the error, which can be one of the following:
1 – CRITICAL
2 – ERROR
3 – WARNING
4 – INFO

•
•
•
•

The event class, which can be one of the following:
CFG
CLI
FABRIC
FIRMWARE
FW
LS
MAPS (internal use only)
RAS
SECURITY
ZONE

•
•
•
•
•
•
•
•
•
•

User ID

The user ID.

Role

The role of the user ID.

IP address

The IP address.

Interface

The interface being used.

Application Name

The application name being used on the interface.

Admin Domain

The Admin Domain, if there is one.

Switch name

The defined switch name or the chassis name of the switch depending on
the action; for example, HA messages typically show the chassis name and
login failures show the logical switch name.
This value is truncated if it is over 16 characters in length.
Execute the chassisName command to name the chassis or the switchName
command to rename the logical switch.

Reserved field for future
expansion

This field is reserved for future use and contains a space character (null
value).

Event-specific information

A text string explaining the error encountered and providing parameters
supplied by the software at runtime.

Fabric OS Message Reference
53-1002749-01

25

1

Responding to a system message

Responding to a system message
This section provides procedures on gathering information on system messages.

Looking up a system message
Messages in this manual are arranged alphabetically by Module ID, and then numerically within a
given module. To look up a message, copy down the module (see Table 6 on page 28) and the error
code and compare this with the Table of Contents or look up lists to determine the location of the
information 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 action

Gathering information about the problem
Questions to ask yourself when troubleshooting a system message are as follows:

•
•
•
•

What is the current Fabric OS level?
What is the switch hardware version?
Is the switch operational?
Assess impact and urgency:

-

Is the switch down?
Is it a standalone switch?
How large is the fabric?
Is the fabric redundant?

• Execute the errDump command on each logical switch.
• Execute the supportFtp command (as needed) to set up automatic FTP transfers, and then run
the supportSave command.

• Document the sequence of events by answering the following questions:
- What happened just prior to 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 security enabled?
• Was POST enabled?

26

Fabric OS Message Reference
53-1002749-01

Responding to a system message

1

• Are serial port (console) logs available?
• Which CP was master?
• What and when were the last actions or changes made to the system?
Common steps to be followed when troubleshooting a system message are as follows:

• Execute the errDump command on each logical switch.
• Execute the supportFtp command (as needed) to set up automatic FTP transfers, and then
execute the supportSave command.

Support
Fabric OS creates a number of files that can help support personnel troubleshoot and diagnose a
problem. This section describes those files and how to access or save the information for support
personnel.

Panic dump and core dump files
The Fabric OS creates panic dump files and core files when there are problems in the Fabric OS
kernel. You can view panic dump files using the pdShow command. These files can build up in the
kernel partition (typically because of failovers) and might need to be periodically deleted or
downloaded using the supportSave command.
The software watchdog process (SWD) is responsible for monitoring daemons critical to the
function of a healthy switch. The SWD holds a list of critical daemons that ping the SWD periodically
at a predetermined interval defined for each daemon. The ping interval is set at 133 seconds, with
the exception of the Fabric Watch daemon and the IP storage demon, which ping the SWD every
333 seconds. (For a complete listing of daemons, refer to the KSWD entry in Table 6.)
If a daemon fails to ping the SWD within the defined interval, or if the daemon terminates
unexpectedly, then the SWD dumps information to the panic dump files, which helps to diagnose
the root cause of the unexpected failure.
Execute the pdShow command to view these files or the supportSave command to send them to a
host workstation using FTP. The panic dump files and core files are intended for support personnel
use only.

Trace dumps
The Fabric OS produces trace dumps when problems are encountered within Fabric OS modules.
The Fabric OS trace dump files are intended for support personnel use only. You can use the
supportSave or supportFTP commands to collect trace dump files to a specified remote location to
provide to support when requested.

supportSave command
The supportSave command can be used to send the output of the system messages (RASLog), the
trace files, and the output of the supportShow command to an off-switch storage location through
FTP. Prior to running the supportSave command, you can optionally set up the FTP parameters
using the supportFtp command. The supportShow command runs a large number of dump and
show commands to provide a global output of the status of the switch. Refer to the Fabric OS
Command Reference for more information on these commands.

Fabric OS Message Reference
53-1002749-01

27

1

System module descriptions

System module descriptions
Table 6 provides a summary of the system modules for which messages are documented in this
guide; the system modules are listed alphabetically by name. A module is a subsystem in the Fabric
OS. Each module generates a set of numbered messages.

TABLE 6

28

System module descriptions

System
module

Description

AG

Access Gateway (AG) allows multiple hosts (or HBAs) to access the fabric using fewer physical ports.
Access Gateway mode transforms the Brocade switches as well as embedded switches into a device
management tool that is compatible with different types of fabrics, including Brocade-, Cisco-, and
McDATA-based fabrics.

AN

Error or warning messages from the Bottleneck Detection module, including notification of detected
bottlenecks.

ANV

ANV error messages indicate problems with the driver that deal with the ENET application-specific
integrated circuits (ASICs) on the Fabric OS. They can be software- or hardware-related errors.

AUTH

Authentication error messages indicate problems with the authentication module of the Fabric OS.

BKSW

BKSW messages are generated by the Fabric OS blade kernel software watchdog module.

BL

BL error messages are a result of faulty hardware, transient out-of-memory conditions, ASIC errors,
or inconsistencies in the software state between a blade and the environment monitor (EM) module.

BLS

Fibre Channel over IP port configuration messages over the Brocade 7800 and FX8-24 blade.

BM

Blade management error messages are a result of autoleveling firmware upgrades performed by the
control processor (CP).

C2

C2 error messages indicate problems with the 8 Gbps-capable FC module of the Fabric OS.

C3

C3 error messages indicate problems with the 16 Gbps-capable FC module of the Fabric OS.

CAL

Common Access Layer (CAL) provides XML interface for configuring switch parameters in an object
model.

CCFG

CCFG error messages indicate problems with the Converged Enhanced Ethernet (CEE) configuration
module of the Fabric OS.

CDR

Driver error messages.

CHS

Error messages reporting the problems in the management of the blades in the different slots of the
chassis.

CNM

Cluster Node Manager (CNM) is a software daemon module of the Fabric OS. The messages from
CNM are problems encountered by CNM, warnings, or information to the user of events.

CONF

Status messages for configUpload and configDownload operations.

CTAP

A user-space daemon that forwards non-performance-critical messages from the TAPE driver to the
Crypto Virtual LUN Controller (CVLC) and Security Processor (SP), and vice versa. This module also
maintains a cache of recently acquired keys, reducing requests to the key vault itself.

CVLC

Crypto Virtual LUN Controller (CVLC) is a software module running on blade FOS (BFOS). The
messages of CVLC are problems encountered by CVLC, warnings to alert the user, or information to
the user.

CVLM

Crypto Virtual LUN Manager (CVLM) is a software module of the Fabric OS. The messages of CVLM
are problems encountered by CVLM, warnings to alert the user, or information to the user.

DOT1

DOT1 error messages indicate problems with the 802.1x authentication module of the Fabric OS.

Fabric OS Message Reference
53-1002749-01

System module descriptions

TABLE 6

1

System module descriptions (Continued)

System
module

Description

ECC

Error Checking and Correction (ECC) error messages indicate single-bit and multiple-bit errors in the
Dynamic Random Access Memory (DRAM) devices. ECC is a technology that helps to correct memory
errors.

EM

The environmental monitor (EM) manages and monitors the various field-replaceable units (FRUs),
including the port cards, control processor (CP) blades, 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 the
integrity of the system using the environmental and power policies. EM reflects system status by CLI
commands, system light emitting diodes (LEDs), and status and alarm messages. EM also manages
some component-related data.

ESS

Exchange Switch Support (ESS) error messages indicate problems with the ESS module of the Fabric
OS. ESS is an SW_ILS mechanism utilized by switches to exchange vendor and support information.

ESW

ESW error messages indicate problems with the Ethernet switch module of Fabric OS.

EVMD

EVMD is the event management module.

FABR

FABRIC refers to a network of Fibre Channel switches. The FABR error messages come from the
fabric daemon. The fabric daemon follows the FC-SW-3 standard for the fabric initialization process,
such as determining the E_Ports, assigning unique domain IDs to switches, creating a spanning tree,
throttling the trunking process, and distributing the domain and alias lists to all switches in the
fabric.

FABS

Fabric OS system driver module.

FBC

Firmware blade compatibility errors with the control processor (CP).

FCMC

Fibre Channel miscellaneous messages relate to problems with the physical layer used to send Fibre
Channel traffic to and from the switch.

FCOE

FCoE error messages indicate problems with the FCoE module of the Fabric OS.

FCPD

The Fibre Channel Protocol daemon is responsible for probing the devices attached to the loop port.
Probing is a process the switch uses to find the devices attached to the loop ports and to update the
Name Server with the information.

FCPH

The Fibre Channel Physical Layer is used to send Fibre Channel traffic to and from the switch.

FCR

Fibre Channel router-related traffic and activity on the fabric or back-end fabric.

FICN

The FICN messages are generated during FICON emulation processing on an FCIP Tunnel.

FICU

The FICON-CUP daemon handles communication with fibre connectivity (FICON) on IBM FICON
storage devices. Errors to this module are usually initiation errors or indications that FICON-CUP
prerequisites have not been met, such as a license key, core process ID (PID), and secure mode on
the fabric.

FKLB

Fabric OS I/O kernel library module.

FLOD

FLOD is a part of the Fabric Shortest Path First (FSPF) protocol that handles synchronization of the
link state database (LSDB) and propagation of the link state records (LSRs).

FSPF

Fabric Shortest Path First (FSPF) is a link state routing protocol that is used to determine how frames
should be routed. These messages are about protocol errors.

Fabric OS Message Reference
53-1002749-01

29

1

System module descriptions

TABLE 6

30

System module descriptions (Continued)

System
module

Description

FSS

The Fabric OS state synchronization framework provides facilities by which the active control
processor (CP) can synchronize with the standby CP, enabling the standby CP to take control of the
switch nondisruptively during failures and software upgrades. These facilities include version
negotiation, state information transfer, and internal synchronization 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 Fabric OS,
implementing a related set of functionality. A service is a collection of components grouped together
to achieve a modular software architecture.

FSSM

The Fabric OS state synchronization management module is defined both as a component and a
service. A component is a module in Fabric OS, implementing a related set of functionality. A service
is a collection of components grouped together to achieve a modular software architecture.

FW

FW is the Fabric Watch module. This module monitors thresholds for many switch subsystems; for
example, temperature, voltage, fan speed, and switch status. Any changes that cross a specified
threshold are reported to the system message log.

HAM

HAM is a user-space daemon responsible for high availability management.

HAMK

This is the kernel module for the high availability management (HAM) daemon.

HIL

Hardware independent layer.

HLO

HLO is a part of the Fabric Shortest Path First (FSPF) protocol that handles the HELLO protocol
between adjacent switches. The HELLO protocol is used to establish connectivity with a neighbor
switch, to establish the identity of the neighbor switch, and to exchange FSPF parameters and
capabilities.

HMON

Health monitor.

HSL

HSL error messages indicate problems with the Hardware Subsystem Layer of the Fabric OS.

HTTP

HTTP error messages.

IBD

IBD generates messages related to port restart failure.

IPAD

System messages generated by the IP admin demon.

IPS

Fibre Channel over IP license, tunneling, and port-related messages.

ISNS

ISNS server and client status messages.

KAC

KAC error messages indicate problems associated with Fabric OS and the external key vaults.

KSWD

The kernel software watchdog (KSWD) watches daemons for unexpected terminations and “hang”
conditions and informs the HAM module to take corrective actions such as failover or reboot.
The following daemons are monitored by KSWD:
• Access Gateway daemon (agd)
• Alias Server daemon (asd)
• ARR daemon (arrd)
• Authentication daemon (authd)
• Blade Manager daemon (bmd)
• Cluster Node Manager daemon (cnmd)
• Common Access Layer daemon (cald)
• DAUTH daemon (dauthd)
• Diagnostics daemon (diagd)
• Environment Monitor daemon (emd)
• Event Manager daemon (evmd)
• Exchange Switch Support daemon (essd)
• FA-API rpc daemon (rpcd)

Fabric OS Message Reference
53-1002749-01

System module descriptions

TABLE 6

1

System module descriptions (Continued)

System
module

Description

KSWD
(continued)

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•

KTRC

Kernel RAS trace module.

L2SS

L2SYS error messages indicate problems with the Layer 2 System manager that controls the Layer 2
forwarding engine and controls the learning/aging/forwarding functionality.

LACP

LACP error messages indicate problems with the Link Aggregation Control Protocol module of the
Fabric OS.

LANCE

LANCE error messages indicate problems with the LANCE module of the Fabric OS.

Fabric OS Message Reference
53-1002749-01

Fabric daemon (fabricd)
Fabric Device Management Interface daemon (fdmid)
Fabric Watch daemon (fwd)
FCoE daemon (fcoed)
Fibre Channel Protocol daemon (fcpd)
FICON CUP daemon (ficud)
FSPF daemon (fspfd)
IGMP daemon (igmpd)
IMI daemon (imid)
Inter-fabric Routing daemon (iswitchd)
IP Storage daemon (ipsd)
ISNS client daemon on CP (isnscd)
KAC daemon (kacd)
Layer 2 System daemon (l2sysd)
LFM daemon (lfmd)
Link Aggregation Control Protocol daemon (lacpd)
Management Server daemon (msd)
MM daemon (mmd)
Multicast Sub-System daemon (mcast_ssd)
Multiple Spanning Tree Protocol daemon (mstpd)
Name Server daemon (nsd)
NSM daemon (nsmd)
ONM daemon (onmd)
Parity data manager daemon (pdmd)
Proxy daemon (proxyd)
PS daemon (psd)
RASLOG daemon (raslogd)
RCS daemon (rcsd)
RM daemon (rmd)
RMON daemon (rmond)
Security daemon (secd)
Sigma daemon (sigmad)
SNMP daemon (snmpd)
SP management daemon (spmd)
SVP daemon (svpd)
System services module daemon (ssmd)
Time Service daemon (tsd)
TRACE daemon (traced)
Traffic daemon (trafd)
VS daemon (vsd)
Web linker daemon (weblinkerd)
Web Tools daemon (webd)
ZONE daemon (zoned)

31

1

System module descriptions

TABLE 6

32

System module descriptions (Continued)

System
module

Description

LFM

LFM error messages indicate problems with the logical fabric manager module that is responsible
for making a logical switch use XISLs. This involves creating and managing LISLs in a logical fabric.

LOG

RASLog subsystem.

LSDB

The link state database is a part of the FSPF protocol that maintains records on the status of port
links. This database is used to route frames.

MCAST_SS

The Multicast Sub-System messages indicate any problems associated with the Layer 2 and Layer 3
Multicast platform support, including allocation of global platform resources such as MGIDs,
hardware acceleration resources for Multicast, and route programming into the hardware (Layer 2
EXM for IGMP Snooping).

MFIC

MS-FICON messages relate to Fibre Connection (FICON) installations. Fibre Connection control unit
port (FICON-CUP) messages are displayed under the FICU module.

MM

MM message indicate problems with the management modules.

MPTH

Multicast path uses the shortest path first (SPF) algorithm to dynamically compute a broadcast tree.

MQ

Message queues are used for interprocess communication. Message queues allow many messages,
each of variable length, to be queued. Any process or interrupt service routine (ISR) can write
messages to a message queue. Any process can read messages from a message queue.

MS

The Management Service enables the user to obtain information about the Fibre Channel fabric
topology and attributes by providing a single management access point. MS provides for both
monitoring and control of the following areas:
• Fabric Configuration Server: Provides for the configuration management of the fabric.
• Unzoned Name Server: Provides access to Name Server information that is not subject to zone
constraints.
• Fabric Zone Server: Provides access to and control of zone information.

MSTP

MSTP error messages indicate problems with Multiple Spanning Tree Protocol modules of the Fabric
OS.

NBFS

NBFSM is a part of the Fabric Shortest Path First (FSPF) protocol that handles a neighboring or
adjacent switch’s finite state machine (FSM).
Input to the FSM changes the local switch from one state to another, based on specific events. For
example, when two switches are connected to each other using an interswitch link (ISL) cable, they
are in the Init state. After both switches receive HELLO messages, they move to the Database
Exchange state, and so on.
NBFSM states are Down (0), Init (1), Database Exchange (2), Database Acknowledge Wait (3),
Database Wait (4), and Full (5).

NS

Indicates problems with the simple Name Server module.

NSM

NSM error messages indicate problems with the Interface Management and VLAN Management
module of the Fabric OS.

ONMD

ONMD error messages indicate problems with the Operation, Administration and Maintenance
module of the Fabric OS.

PDM

Parity data manager (PDM) is a user-space daemon responsible for the replication of persistent
configuration files from the primary partition to the secondary partition and from the active CP blade
to the standby CP blade.

PDTR

PDTR messages indicate panic dump trace files have been created.

PLAT

PLAT messages indicate hardware problems.

PMGR

A group of messages relating to logical switch creation, deletion, and configuration.

Fabric OS Message Reference
53-1002749-01

System module descriptions

TABLE 6

1

System module descriptions (Continued)

System
module

Description

PORT

PORT error messages refer to the front-end user ports on the switch. Front-end user ports are
directly accessible by users to connect end devices or connect to other switches.

PS

The performance server daemon measures the amount of traffic between endpoints or traffic with
particular frame formats, such as SCSI frames, IP frames, and customer-defined frames.

PSWP

The portswap feature and associated commands generate these error messages.

RAS

Informational messages when first failure data capture (FFDC) events are logged to the FFDC log
and size or roll-over warning.

RCS

The reliable commit service daemon generates log entries when it receives a request from the
zoning, security, or management server for passing data messages to switches in the fabric. RCS
then requests reliable transport write and read (RTWR) to deliver the message. RCS also acts as a
gatekeeper, limiting the number of outstanding requests for the Zoning, Security, or Management
Server modules.

RKD

These messages are either error or informational messages pertaining to the re-key daemon of the
Fabric OS.

RMON

RMON messages are error or informational messages pertaining to the RMOND daemon.

RPCD

The remote procedure call daemon (RPCD) is used by Fabric Access for API-related tasks.

RTE

RTE is responsible for determining the correct paths for each ingress frame and populating the
routing tables in the ASICs with this information. The ASIC then uses the information available in the
routing tables to determine the path a particular ingress frame needs to take before it exits the
switch.

RTWR

The reliable transport write and read daemon helps deliver data messages either to specific
switches in the fabric or to all of the switches in the fabric. For example, if some of the switches 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 100 times.

SCN

The internal state change notification daemon is used for state change notifications from the kernel
to the daemons within Fabric OS.

SEC

The security daemon generates security errors, warnings, or information during security-related data
management or fabric merge operations. Administrators should watch for these messages to
distinguish between internal switch and fabric operation errors and external attacks.

SFLO

sFlow is a standard-based sampling technology embedded within switches and routers, which is
used to monitor high-speed network traffic for Data Center Ethernet (DCE) and Converged Enhanced
Ethernet (CEE) platforms.
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 sflowd daemon.

SNMP

Simple Network Management Protocol (SNMP) is a universally supported low-level protocol that
allows simple get, get next, and set requests to go to the switch (acting as an SNMP agent). It also
allows the switch to send traps to the defined and configured management station. Brocade
switches support six management entities that can be configured to receive these traps.

SPC

SPC messages indicate problems and informational updates associated with the security processor.
These messages could be triggered by the following three modules: Security processor controller, SP
system controller, and SP Keyapp.

SPM

Error messages indicating problems either with key or SP management.

SS

The supportSave command generates these error messages if problems are encountered.

Fabric OS Message Reference
53-1002749-01

33

1

System module descriptions

TABLE 6

34

System module descriptions (Continued)

System
module

Description

SSMD

SSMD error messages indicate problems with the System Services Module of the Fabric OS.

SULB

The software upgrade library provides the firmwareDownload command capability, which enables
firmware upgrades to both CP blades with a single command, as well as nondisruptive code load to
all Fabric OS switches. These messages might display if there are any problems during the
firmwareDownload procedure. Most messages are informational only and are generated even during
successful firmware download. For additional information, refer to the Fabric OS Administrator’s
Guide.

SWCH

These messages are generated by the switch driver module that manages a Fibre Channel switch
instance.

SYSC

System controller is a daemon that starts up and shuts down all Fabric OS modules in the proper
sequence.

SYSM

General system messages.

TAPE

A kernel-space driver that handles all I/O operations aimed at Tape containers.

TRCE

RAS TRACE error messages.

TRCK

The track change feature tracks the following events:
Turning on or off the track change feature
CONFIG_CHANGE
LOGIN
LOGOUT
FAILED_LOGIN
If any of these events occur, a message is sent to the system message log. Additionally, if the SNMP
trap option is enabled, an SNMP trap is also sent.
For information on configuring the track change feature, refer to the Fabric OS Command Reference
or the Fabric OS Administrator’s Guide.

TS

Time Service provides fabric time-synchronization by synchronizing all clocks in the fabric to the
clock time on the principal switch.

UCST

UCST is a part of the Fabric Shortest Path First (FSPF) protocol that manages the Unicast routing
table.

UPTH

UPATH is a part of the FSPF protocol that uses the SPF algorithm to dynamically compute a Unicast
tree.

VDR

VDR messages indicate Field-Programmable Gate Array (FPGA) parity errors.

VS

The VS module messages indicate any problems or information associated with the Dynamic Fabric
Provisioning feature, including commands associated with the fapwwn command and
configurations.

WEBD

Indicates problems with the Web Tools module.

XTUN

XTUN messages are generated by the FCIP Tunnel implementation. These messages indicate status
of FCIP tunnels, FCIP emulation events for FCP traffic, or FCIP debug information (FTRACE buffer
status changes).

ZEUS

Zeus error messages indicate problems with the Zeus driver module.

ZONE

The zone module messages indicate any problems associated with the zoning features, including
commands associated with aliases, zones, and configurations.

•
•
•
•
•

Fabric OS Message Reference
53-1002749-01

Chapter

Log Messages

2

AG Messages
AG-1001
AG-1002
AG-1003
AG-1004
AG-1005
AG-1006
AG-1007
AG-1008
AG-1009
AG-1010
AG-1011
AG-1012
AG-1013
AG-1014
AG-1015
AG-1016
AG-1017
AG-1018
AG-1019
AG-1020
AG-1021
AG-1022
AG-1023
AG-1024
AG-1025
AG-1026
AG-1027
AG-1028

Fabric OS Message Reference
53-1002749-01

35

2

AN Messages

AG-1029
AG-1030
AG-1031
AG-1032
AG-1033
AG-1034
AG-1035
AG-1036
AG-1037
AG-1038
AG-1039
AG-1040
AG-1041
AG-1042
AG-1043
AG-1044

AN Messages
AN-1001
AN-1002
AN-1003
AN-1004
AN-1005
AN-1010
AN-1011
AN-1012
AN-1013

ANV Messages
ANV-1001
ANV-1002
ANV-1003
ANV-1004
ANV-1005

36

Fabric OS Message Reference
53-1002749-01

AUTH Messages

2

ANV-1006
ANV-1007
ANV-1008
ANV-1015
ANV-1016
ANV-1028

AUTH Messages
AUTH-1001
AUTH-1002
AUTH-1003
AUTH-1004
AUTH-1005
AUTH-1006
AUTH-1007
AUTH-1008
AUTH-1010
AUTH-1011
AUTH-1012
AUTH-1013
AUTH-1014
AUTH-1016
AUTH-1017
AUTH-1018
AUTH-1020
AUTH-1022
AUTH-1023
AUTH-1025
AUTH-1026
AUTH-1027
AUTH-1028
AUTH-1029
AUTH-1030
AUTH-1031
AUTH-1032

Fabric OS Message Reference
53-1002749-01

37

2

BKSW Messages

AUTH-1033
AUTH-1034
AUTH-1035
AUTH-1036
AUTH-1037
AUTH-1038
AUTH-1039
AUTH-1040
AUTH-1041
AUTH-1042
AUTH-1043
AUTH-1044
AUTH-1045
AUTH-1046
AUTH-1047

BKSW Messages
BKSW-1003

BL Messages
BL-1000
BL-1001
BL-1002
BL-1003
BL-1004
BL-1006
BL-1007
BL-1008
BL-1009
BL-1010
BL-1011
BL-1012
BL-1013
BL-1014

38

Fabric OS Message Reference
53-1002749-01

BL Messages

2

BL-1015
BL-1016
BL-1017
BL-1018
BL-1019
BL-1020
BL-1021
BL-1022
BL-1023
BL-1024
BL-1025
BL-1026
BL-1027
BL-1028
BL-1029
BL-1030
BL-1031
BL-1032
BL-1033
BL-1034
BL-1035
BL-1036
BL-1037
BL-1038
BL-1039
BL-1041
BL-1045
BL-1046
BL-1047
BL-1048
BL-1049
BL-1050
BL-1051
BL-1052

Fabric OS Message Reference
53-1002749-01

39

2

BLS Messages

BLS Messages
BLS-1000
BLS-1001
BLS-1002
BLS-1003
BLS-1004
BLS-1005

BM Messages
BM-1001
BM-1002
BM-1003
BM-1004
BM-1005
BM-1006
BM-1007
BM-1008
BM-1009
BM-1010
BM-1053
BM-1054
BM-1055
BM-1056
BM-1058

C2 Messages
C2-1001
C2-1002
C2-1004
C2-1006
C2-1007
C2-1008
C2-1009
C2-1010

40

Fabric OS Message Reference
53-1002749-01

C3 Messages

2

C2-1012
C2-1013
C2-1014
C2-1015
C2-1016
C2-1017
C2-1018
C2-1019
C2-1025
C2-1026
C2-1027
C2-1028

C3 Messages
C3-1001
C3-1002
C3-1004
C3-1006
C3-1007
C3-1008
C3-1009
C3-1010
C3-1011
C3-1012
C3-1013
C3-1014
C3-1015
C3-1016
C3-1017
C3-1018
C3-1019
C3-1020
C3-1021
C3-1023
C3-1025

Fabric OS Message Reference
53-1002749-01

41

2

CAL Messages

C3-1026
C3-1027
C3-1028

CAL Messages
CAL-1001

CCFG Messages
CCFG-1001
CCFG-1002
CCFG-1003
CCFG-1004
CCFG-1005
CCFG-1006
CCFG-1007
CCFG-1008
CCFG-1009
CCFG-1010
CCFG-1011
CCFG-1012

CDR Messages
CDR-1001
CDR-1002
CDR-1003
CDR-1004
CDR-1005
CDR-1006
CDR-1007
CDR-1008
CDR-1009
CDR-1010
CDR-1011
CDR-1012

42

Fabric OS Message Reference
53-1002749-01

CHS Messages

2

CDR-1014
CDR-1015
CDR-1016
CDR-1017
CDR-1018
CDR-1019
CDR-1022
CDR-1028

CHS Messages
CHS-1002
CHS-1003
CHS-1004
CHS-1005

CNM Messages
CNM-1001
CNM-1002
CNM-1003
CNM-1004
CNM-1005
CNM-1006
CNM-1007
CNM-1008
CNM-1009
CNM-1010
CNM-1011
CNM-1012
CNM-1013
CNM-1014
CNM-1015
CNM-1016
CNM-1017
CNM-1018

Fabric OS Message Reference
53-1002749-01

43

2

CNM Messages

CNM-1019
CNM-1020
CNM-1021
CNM-1022
CNM-1023
CNM-1024
CNM-1025
CNM-1026
CNM-1027
CNM-1028
CNM-1029
CNM-1030
CNM-1031
CNM-1032
CNM-1033
CNM-1034
CNM-1035
CNM-1036
CNM-1037
CNM-1038
CNM-1039
CNM-1040
CNM-1041
CNM-1042
CNM-1043
CNM-1044
CNM-1045
CNM-1046
CNM-1047
CNM-1048
CNM-1049
CNM-1050
CNM-1051
CNM-1052
CNM-1053

44

Fabric OS Message Reference
53-1002749-01

CONF Messages

2

CNM-1054
CNM-1055
CNM-1056
CNM-1057
CNM-1058
CNM-1059
CNM-1060
CNM-1061
CNM-1062
CNM-3001
CNM-3002
CNM-3003
CNM-3004
CNM-3005
CNM-3006
CNM-3007
CNM-3008
CNM-3009
CNM-3010
CNM-3011
CNM-3012

CONF Messages
CONF-1000
CONF-1001
CONF-1021
CONF-1023
CONF-1024
CONF-1030
CONF-1031
CONF-1032
CONF-1040
CONF-1041
CONF-1042
CONF-1043

Fabric OS Message Reference
53-1002749-01

45

2

CTAP Messages

CONF-1044

CTAP Messages
CTAP-1001

CVLC Messages
CVLC-1001
CVLC-1002
CVLC-1003
CVLC-1004
CVLC-1005
CVLC-1006
CVLC-1007
CVLC-1008
CVLC-1009
CVLC-1010
CVLC-1011
CVLC-1012
CVLC-1013
CVLC-1014
CVLC-1015
CVLC-1016
CVLC-1017
CVLC-1018
CVLC-1019
CVLC-1020
CVLC-1021
CVLC-1022
CVLC-1023
CVLC-1024
CVLC-1025
CVLC-1026
CVLC-1027
CVLC-1028

46

Fabric OS Message Reference
53-1002749-01

CVLM Messages

2

CVLC-1029
CVLC-1030
CVLC-1031
CVLC-1032
CVLC-1033
CVLC-1034
CVLC-1035
CVLC-1039
CVLC-1041

CVLM Messages
CVLM-1001
CVLM-1002
CVLM-1003
CVLM-1004
CVLM-1005
CVLM-1006
CVLM-1007
CVLM-1008
CVLM-1009
CVLM-1010
CVLM-1011
CVLM-1012
CVLM-1013
CVLM-1014
CVLM-1015
CVLM-1016
CVLM-3001
CVLM-3002
CVLM-3003
CVLM-3004
CVLM-3005
CVLM-3006
CVLM-3007
CVLM-3008

Fabric OS Message Reference
53-1002749-01

47

2

DOT1 Messages

CVLM-3009
CVLM-3010
CVLM-3011
CVLM-3012
CVLM-3013
CVLM-3014
CVLM-3015
CVLM-3016
CVLM-3017
CVLM-3018
CVLM-3019
CVLM-3020
CVLM-3021
CVLM-3022
CVLM-3023
CVLM-3024
CVLM-3025
CVLM-3026
CVLM-3027
CVLM-3028

DOT1 Messages
DOT1-1001
DOT1-1002
DOT1-1003
DOT1-1004
DOT1-1005
DOT1-1006
DOT1-1007
DOT1-1008
DOT1-1009
DOT1-1010

48

Fabric OS Message Reference
53-1002749-01

ECC Messages

2

ECC Messages
ECC-1000
ECC-1001

EM Messages
EM-1001
EM-1002
EM-1003
EM-1004
EM-1005
EM-1006
EM-1008
EM-1009
EM-1010
EM-1011
EM-1012
EM-1013
EM-1014
EM-1015
EM-1016
EM-1017
EM-1018
EM-1019
EM-1020
EM-1028
EM-1029
EM-1031
EM-1033
EM-1034
EM-1035
EM-1036
EM-1037
EM-1042
EM-1043

Fabric OS Message Reference
53-1002749-01

49

2

ESS Messages

EM-1044
EM-1045
EM-1046
EM-1047
EM-1048
EM-1049
EM-1050
EM-1051
EM-1057
EM-1058
EM-1059
EM-1060
EM-1061
EM-1062
EM-1063
EM-1064
EM-1065
EM-1066
EM-1067
EM-1068
EM-1069
EM-1070
EM-1071
EM-1072
EM-2003

ESS Messages
ESS-1001
ESS-1002
ESS-1003
ESS-1004
ESS-1005
ESS-1008
ESS-1009
ESS-1010

50

Fabric OS Message Reference
53-1002749-01

ESW Messages

2

ESW Messages
ESW-1001
ESW-1002
ESW-1003
ESW-1004
ESW-1005
ESW-1006
ESW-1007
ESW-1008

EVMD Messages
EVMD-1001

FABR Messages
FABR-1001
FABR-1002
FABR-1003
FABR-1004
FABR-1005
FABR-1006
FABR-1007
FABR-1008
FABR-1009
FABR-1010
FABR-1011
FABR-1012
FABR-1013
FABR-1014
FABR-1015
FABR-1016
FABR-1017
FABR-1018
FABR-1019
FABR-1020

Fabric OS Message Reference
53-1002749-01

51

2

FABS Messages

FABR-1021
FABR-1022
FABR-1023
FABR-1024
FABR-1029
FABR-1030
FABR-1031
FABR-1032
FABR-1034
FABR-1035
FABR-1036
FABR-1037
FABR-1038
FABR-1039
FABR-1040
FABR-1041
FABR-1043
FABR-1044
FABR-1045
FABR-1046
FABR-1047
FABR-1048
FABR-1049
FABR-1050
FABR-1051
FABR-1052
FABR-1053
FABR-1054
FABR-1055

FABS Messages
FABS-1001
FABS-1002
FABS-1004
FABS-1005

52

Fabric OS Message Reference
53-1002749-01

FBC Messages

2

FABS-1006
FABS-1007
FABS-1008
FABS-1009
FABS-1010
FABS-1011
FABS-1013
FABS-1014
FABS-1015

FBC Messages
FBC-1001

FCMC Messages
FCMC-1001

FCOE Messages
FCOE-1001
FCOE-1002
FCOE-1003
FCOE-1004
FCOE-1005
FCOE-1006
FCOE-1007
FCOE-1009
FCOE-1010
FCOE-1012
FCOE-1014
FCOE-1015
FCOE-1016
FCOE-1017
FCOE-1019
FCOE-1021
FCOE-1022

Fabric OS Message Reference
53-1002749-01

53

2

FCPD Messages

FCOE-1023
FCOE-1024
FCOE-1025
FCOE-1026
FCOE-1027
FCOE-1028
FCOE-1029
FCOE-1030
FCOE-1031
FCOE-1032
FCOE-1033
FCOE-1034
FCOE-1037
FCOE-1038
FCOE-1039
FCOE-1040
FCOE-1041
FCOE-1042
FCOE-1043
FCOE-1044
FCOE-1045
FCOE-1046
FCOE-1047
FCOE-1048

FCPD Messages
FCPD-1001
FCPD-1002
FCPD-1003

FCPH Messages
FCPH-1001
FCPH-1002
FCPH-1003

54

Fabric OS Message Reference
53-1002749-01

FCR Messages

2

FCPH-1004
FCPH-1005

FCR Messages
FCR-1001
FCR-1002
FCR-1003
FCR-1004
FCR-1005
FCR-1006
FCR-1007
FCR-1008
FCR-1009
FCR-1010
FCR-1011
FCR-1012
FCR-1013
FCR-1015
FCR-1016
FCR-1018
FCR-1019
FCR-1020
FCR-1021
FCR-1022
FCR-1023
FCR-1024
FCR-1025
FCR-1026
FCR-1027
FCR-1028
FCR-1029
FCR-1030
FCR-1031
FCR-1032
FCR-1033

Fabric OS Message Reference
53-1002749-01

55

2

FCR Messages

FCR-1034
FCR-1035
FCR-1036
FCR-1037
FCR-1038
FCR-1039
FCR-1040
FCR-1041
FCR-1042
FCR-1043
FCR-1048
FCR-1049
FCR-1053
FCR-1054
FCR-1055
FCR-1056
FCR-1057
FCR-1058
FCR-1059
FCR-1060
FCR-1061
FCR-1062
FCR-1063
FCR-1064
FCR-1065
FCR-1066
FCR-1067
FCR-1068
FCR-1069
FCR-1070
FCR-1071
FCR-1072
FCR-1073
FCR-1074
FCR-1075

56

Fabric OS Message Reference
53-1002749-01

FICN Messages

2

FCR-1076
FCR-1077
FCR-1078
FCR-1079
FCR-1080
FCR-1081
FCR-1082
FCR-1083
FCR-1084
FCR-1085
FCR-1086
FCR-1087
FCR-1088
FCR-1089
FCR-1091
FCR-1092
FCR-1093
FCR-1094
FCR-1095
FCR-1096
FCR-1097
FCR-1098

FICN Messages
FICN-1003
FICN-1004
FICN-1005
FICN-1006
FICN-1007
FICN-1008
FICN-1009
FICN-1010
FICN-1011
FICN-1012
FICN-1013

Fabric OS Message Reference
53-1002749-01

57

2

FICN Messages

FICN-1014
FICN-1015
FICN-1016
FICN-1017
FICN-1018
FICN-1019
FICN-1020
FICN-1021
FICN-1022
FICN-1023
FICN-1024
FICN-1025
FICN-1026
FICN-1027
FICN-1028
FICN-1029
FICN-1030
FICN-1031
FICN-1032
FICN-1033
FICN-1034
FICN-1035
FICN-1036
FICN-1037
FICN-1038
FICN-1039
FICN-1040
FICN-1041
FICN-1042
FICN-1043
FICN-1044
FICN-1045
FICN-1046
FICN-1047
FICN-1048

58

Fabric OS Message Reference
53-1002749-01

FICN Messages

2

FICN-1049
FICN-1050
FICN-1051
FICN-1052
FICN-1053
FICN-1054
FICN-1055
FICN-1056
FICN-1057
FICN-1058
FICN-1059
FICN-1060
FICN-1061
FICN-1062
FICN-1063
FICN-1064
FICN-1065
FICN-1066
FICN-1067
FICN-1068
FICN-1069
FICN-1070
FICN-1071
FICN-1072
FICN-1073
FICN-1074
FICN-1075
FICN-1076
FICN-1077
FICN-1078
FICN-1079
FICN-1080
FICN-1081
FICN-1082
FICN-1083

Fabric OS Message Reference
53-1002749-01

59

2

FICN Messages

FICN-1084
FICN-1085
FICN-1086
FICN-1087
FICN-1088
FICN-1089
FICN-1090
FICN-1091
FICN-1092
FICN-1093
FICN-1094
FICN-1095
FICN-1096
FICN-1097
FICN-1098
FICN-1099
FICN-1100
FICN-1101
FICN-1102
FICN-1103
FICN-1104
FICN-1105
FICN-1106
FICN-1107
FICN-1108
FICN-1109
FICN-1110
FICN-1111
FICN-1112
FICN-1113
FICN-1114
FICN-1115
FICN-1116
FICN-1117
FICN-1118

60

Fabric OS Message Reference
53-1002749-01

FICU Messages

2

FICN-1119
FICN-1120
FICN-1121
FICN-1122
FICN-2005
FICN-2006
FICN-2064
FICN-2065
FICN-2066
FICN-2082
FICN-2083
FICN-2085
FICN-2086
FICN-2087

FICU Messages
FICU-1001
FICU-1002
FICU-1003
FICU-1004
FICU-1005
FICU-1006
FICU-1007
FICU-1008
FICU-1009
FICU-1010
FICU-1011
FICU-1012
FICU-1013
FICU-1017
FICU-1018
FICU-1019
FICU-1020
FICU-1021
FICU-1022

Fabric OS Message Reference
53-1002749-01

61

2

FKLB Messages

FICU-1023
FICU-1024

FKLB Messages
FKLB-1001

FLOD Messages
FLOD-1001
FLOD-1003
FLOD-1004
FLOD-1005
FLOD-1006

FSPF Messages
FSPF-1001
FSPF-1002
FSPF-1003
FSPF-1005
FSPF-1006
FSPF-1007
FSPF-1008
FSPF-1009
FSPF-1010
FSPF-1011
FSPF-1012

FSS Messages
FSS-1001
FSS-1002
FSS-1003
FSS-1004
FSS-1005
FSS-1006
FSS-1007

62

Fabric OS Message Reference
53-1002749-01

FSSM Messages

2

FSS-1008
FSS-1009
FSS-1010
FSS-1011

FSSM Messages
FSSM-1002
FSSM-1003
FSSM-1004

FW Messages
FW-1001
FW-1002
FW-1003
FW-1004
FW-1005
FW-1006
FW-1007
FW-1008
FW-1009
FW-1010
FW-1011
FW-1012
FW-1033
FW-1034
FW-1035
FW-1036
FW-1037
FW-1038
FW-1039
FW-1040
FW-1041
FW-1042
FW-1043

Fabric OS Message Reference
53-1002749-01

63

2

FW Messages

FW-1044
FW-1045
FW-1046
FW-1047
FW-1048
FW-1049
FW-1050
FW-1051
FW-1052
FW-1053
FW-1054
FW-1113
FW-1114
FW-1115
FW-1116
FW-1117
FW-1118
FW-1119
FW-1120
FW-1121
FW-1122
FW-1123
FW-1124
FW-1125
FW-1126
FW-1127
FW-1128
FW-1129
FW-1130
FW-1131
FW-1132
FW-1133
FW-1134
FW-1135
FW-1136

64

Fabric OS Message Reference
53-1002749-01

FW Messages

2

FW-1137
FW-1138
FW-1139
FW-1140
FW-1160
FW-1161
FW-1162
FW-1163
FW-1164
FW-1165
FW-1166
FW-1167
FW-1168
FW-1169
FW-1170
FW-1171
FW-1172
FW-1173
FW-1174
FW-1175
FW-1176
FW-1177
FW-1178
FW-1179
FW-1180
FW-1181
FW-1182
FW-1183
FW-1184
FW-1185
FW-1186
FW-1187
FW-1188
FW-1189
FW-1190

Fabric OS Message Reference
53-1002749-01

65

2

FW Messages

FW-1191
FW-1192
FW-1193
FW-1194
FW-1195
FW-1196
FW-1197
FW-1198
FW-1199
FW-1200
FW-1201
FW-1202
FW-1203
FW-1204
FW-1205
FW-1206
FW-1207
FW-1216
FW-1217
FW-1218
FW-1219
FW-1240
FW-1241
FW-1242
FW-1243
FW-1244
FW-1245
FW-1246
FW-1247
FW-1248
FW-1249
FW-1250
FW-1251
FW-1272
FW-1273

66

Fabric OS Message Reference
53-1002749-01

FW Messages

2

FW-1274
FW-1275
FW-1296
FW-1297
FW-1298
FW-1299
FW-1300
FW-1301
FW-1302
FW-1303
FW-1304
FW-1305
FW-1306
FW-1307
FW-1308
FW-1309
FW-1310
FW-1311
FW-1312
FW-1313
FW-1314
FW-1315
FW-1316
FW-1317
FW-1318
FW-1319
FW-1320
FW-1321
FW-1322
FW-1323
FW-1324
FW-1325
FW-1326
FW-1327
FW-1328

Fabric OS Message Reference
53-1002749-01

67

2

FW Messages

FW-1329
FW-1330
FW-1331
FW-1332
FW-1333
FW-1334
FW-1335
FW-1336
FW-1337
FW-1338
FW-1339
FW-1340
FW-1341
FW-1342
FW-1343
FW-1344
FW-1345
FW-1346
FW-1347
FW-1348
FW-1349
FW-1350
FW-1351
FW-1352
FW-1353
FW-1354
FW-1355
FW-1356
FW-1357
FW-1358
FW-1359
FW-1360
FW-1361
FW-1362
FW-1363

68

Fabric OS Message Reference
53-1002749-01

FW Messages

2

FW-1364
FW-1365
FW-1366
FW-1367
FW-1368
FW-1369
FW-1370
FW-1371
FW-1372
FW-1373
FW-1374
FW-1375
FW-1376
FW-1377
FW-1378
FW-1379
FW-1400
FW-1401
FW-1402
FW-1403
FW-1404
FW-1405
FW-1406
FW-1407
FW-1408
FW-1424
FW-1425
FW-1426
FW-1427
FW-1428
FW-1429
FW-1430
FW-1431
FW-1432
FW-1433

Fabric OS Message Reference
53-1002749-01

69

2

FW Messages

FW-1434
FW-1435
FW-1436
FW-1437
FW-1438
FW-1439
FW-1440
FW-1441
FW-1442
FW-1443
FW-1444
FW-1445
FW-1446
FW-1447
FW-1448
FW-1500
FW-1501
FW-1502
FW-1510
FW-1511
FW-1512
FW-1513
FW-1514
FW-1515
FW-1516
FW-1517
FW-1518
FW-1519
FW-1520
FW-1521
FW-1522
FW-1523
FW-1524
FW-1525
FW-1526

70

Fabric OS Message Reference
53-1002749-01

HAM Messages

2

FW-1527
FW-1528
FW-1529
FW-1530
FW-1531
FW-1532
FW-1533
FW-1534
FW-1535
FW-2000
FW-3010
FW-3011
FW-3012
FW-3013
FW-3014
FW-3015
FW-3016
FW-3017
FW-3018
FW-3019
FW-3020
FW-3021
FW-3022

HAM Messages
HAM-1001
HAM-1002
HAM-1004
HAM-1005
HAM-1006
HAM-1007
HAM-1008
HAM-1009
HAM-1010
HAM-1011

Fabric OS Message Reference
53-1002749-01

71

2

HAMK Messages

HAM-1013
HAM-1014

HAMK Messages
HAMK-1001
HAMK-1002
HAMK-1003
HAMK-1004

HIL Messages
HIL-1101
HIL-1102
HIL-1103
HIL-1104
HIL-1105
HIL-1106
HIL-1107
HIL-1108
HIL-1201
HIL-1202
HIL-1203
HIL-1204
HIL-1206
HIL-1207
HIL-1208
HIL-1301
HIL-1302
HIL-1303
HIL-1304
HIL-1305
HIL-1306
HIL-1307
HIL-1308
HIL-1309

72

Fabric OS Message Reference
53-1002749-01

HLO Messages

2

HIL-1310
HIL-1311
HIL-1401
HIL-1402
HIL-1403
HIL-1404
HIL-1501
HIL-1502
HIL-1503
HIL-1504
HIL-1505
HIL-1506
HIL-1507
HIL-1508
HIL-1509
HIL-1510
HIL-1511
HIL-1601
HIL-1602
HIL-1603
HIL-1605
HIL-1610
HIL-1611
HIL-1612
HIL-1613
HIL-1650

HLO Messages
HLO-1001
HLO-1002
HLO-1003

HMON Messages
HMON-1001

Fabric OS Message Reference
53-1002749-01

73

2

HSL Messages

HSL Messages
HSL-1000
HSL-1001
HSL-1002
HSL-1003
HSL-1004
HSL-1005
HSL-1006
HSL-1007

HTTP Messages
HTTP-1001
HTTP-1002
HTTP-1003

IBD Messages
IBD-1000

IPAD Messages
IPAD-1000
IPAD-1001
IPAD-1002
IPAD-1003
IPAD-1004

IPS Messages
IPS-1001
IPS-1002
IPS-1003
IPS-1004
IPS-1005
IPS-1006
IPS-1007

74

Fabric OS Message Reference
53-1002749-01

ISNS Messages

2

ISNS Messages
ISNS-1001
ISNS-1002
ISNS-1003
ISNS-1004
ISNS-1005
ISNS-1006
ISNS-1008
ISNS-1009
ISNS-1010
ISNS-1011
ISNS-1013
ISNS-1014

KAC Messages
KAC-1002
KAC-1004
KAC-1006
KAC-1007
KAC-1008
KAC-1009
KAC-1010
KAC-1011
KAC-1012
KAC-1013
KAC-1014
KAC-1015
KAC-1016
KAC-1017

KSWD Messages
KSWD-1001
KSWD-1002

Fabric OS Message Reference
53-1002749-01

75

2

KTRC Messages

KTRC Messages
KTRC-1001
KTRC-1002
KTRC-1003
KTRC-1004
KTRC-1005

L2SS Messages
L2SS-1001
L2SS-1002
L2SS-1003
L2SS-1004
L2SS-1005
L2SS-1006
L2SS-1007
L2SS-1008

L3SS Messages
L3SS-1004

LACP Messages
LACP-1001
LACP-1002

LANCE Messages
LANCE-1000

LFM Messages
LFM-1001
LFM-1002
LFM-1003
LFM-1004
LFM-1005

76

Fabric OS Message Reference
53-1002749-01

LOG Messages

2

LFM-1006

LOG Messages
LOG-1000
LOG-1001
LOG-1002
LOG-1003
LOG-1004
LOG-1005
LOG-1006
LOG-1007
LOG-1008
LOG-1009
LOG-1010
LOG-1011

LSDB Messages
LSDB-1001
LSDB-1002
LSDB-1003
LSDB-1004

MCAST_SS Messages
MCAST_SS-1001
MCAST_SS-1002
MCAST_SS-1003
MCAST_SS-1004
MCAST_SS-1005
MCAST_SS-1006
MCAST_SS-1007
MCAST_SS-1008
MCAST_SS-1009
MCAST_SS-1010
MCAST_SS-1011

Fabric OS Message Reference
53-1002749-01

77

2

MFIC Messages

MCAST_SS-1012
MCAST_SS-1013
MCAST_SS-1014
MCAST_SS-1015
MCAST_SS-1016
MCAST_SS-1017
MCAST_SS-1018
MCAST_SS-1019
MCAST_SS-1020

MFIC Messages
MFIC-1001
MFIC-1002
MFIC-1003

MM Messages
MM-1001

MPTH Messages
MPTH-1001
MPTH-1002
MPTH-1003

MQ Messages
MQ-1004
MQ-1005
MQ-1006

MS Messages
MS-1001
MS-1002
MS-1003
MS-1004
MS-1005

78

Fabric OS Message Reference
53-1002749-01

MSTP Messages

2

MS-1006
MS-1008
MS-1009
MS-1021
MS-1022
MS-1023
MS-1024
MS-1025
MS-1026
MS-1027
MS-1028
MS-1029
MS-1030

MSTP Messages
MSTP-1001
MSTP-1002
MSTP-1003
MSTP-2001
MSTP-2002
MSTP-2003
MSTP-2004
MSTP-2005
MSTP-2006

NBFS Messages
NBFS-1001
NBFS-1002
NBFS-1003
NBFS-1004

NS Messages
NS-1001
NS-1002

Fabric OS Message Reference
53-1002749-01

79

2

NSM Messages

NS-1003
NS-1004
NS-1005
NS-1006
NS-1007
NS-1008
NS-1009
NS-1010
NS-1011
NS-1012

NSM Messages
NSM-1001
NSM-1002
NSM-1003
NSM-1004
NSM-1005
NSM-1006
NSM-1007
NSM-1008
NSM-1009
NSM-1010
NSM-1011
NSM-1012
NSM-1013
NSM-1014
NSM-1015
NSM-1016
NSM-1017
NSM-1018
NSM-1019
NSM-1020

80

Fabric OS Message Reference
53-1002749-01

ONMD Messages

2

ONMD Messages
ONMD-1000
ONMD-1001
ONMD-1002
ONMD-1003
ONMD-1004
ONMD-1005

PDM Messages
PDM-1001
PDM-1002
PDM-1003
PDM-1004
PDM-1005
PDM-1006
PDM-1007
PDM-1008
PDM-1009
PDM-1010
PDM-1011
PDM-1012
PDM-1013
PDM-1014
PDM-1017
PDM-1019
PDM-1020
PDM-1021
PDM-1022
PDM-1023
PDM-1024
PDM-1025
PDM-1026

Fabric OS Message Reference
53-1002749-01

81

2

PDTR Messages

PDTR Messages
PDTR-1001
PDTR-1002

PLAT Messages
PLAT-1000
PLAT-1001
PLAT-1002
PLAT-1003
PLAT-1004
PLAT-1072

PMGR Messages
PMGR-1001
PMGR-1002
PMGR-1003
PMGR-1004
PMGR-1005
PMGR-1006
PMGR-1007
PMGR-1008
PMGR-1009
PMGR-1010
PMGR-1011

PORT Messages
PORT-1003
PORT-1004
PORT-1005
PORT-1006
PORT-1007
PORT-1008
PORT-1009
PORT-1010

82

Fabric OS Message Reference
53-1002749-01

PS Messages

2

PS Messages
PS-1000
PS-1001
PS-1002
PS-1003
PS-1004
PS-1005
PS-1006
PS-1007
PS-1008
PS-1009
PS-1010

PSWP Messages
PSWP-1001
PSWP-1002
PSWP-1003
PSWP-1004
PSWP-1005
PSWP-1006
PSWP-1007

RAS Messages
RAS-1001
RAS-1002
RAS-1004
RAS-1005
RAS-1006
RAS-1007
RAS-2001
RAS-2002
RAS-2003
RAS-3001
RAS-3002

Fabric OS Message Reference
53-1002749-01

83

2

RCS Messages

RAS-3003
RAS-3004

RCS Messages
RCS-1001
RCS-1002
RCS-1003
RCS-1004
RCS-1005
RCS-1006
RCS-1007
RCS-1008
RCS-1009
RCS-1010
RCS-1011
RCS-1012
RCS-1013

RKD Messages
RKD-1001
RKD-1002
RKD-1003
RKD-1004
RKD-1005

RMON Messages
RMON-1001
RMON-1002

RPCD Messages
RPCD-1001
RPCD-1002
RPCD-1003
RPCD-1004

84

Fabric OS Message Reference
53-1002749-01

RTE Messages

2

RPCD-1005
RPCD-1006
RPCD-1007

RTE Messages
RTE-1001

RTWR Messages
RTWR-1001
RTWR-1002
RTWR-1003

SCN Messages
SCN-1001
SCN-1002

SEC Messages
SEC-1001
SEC-1002
SEC-1003
SEC-1005
SEC-1006
SEC-1007
SEC-1008
SEC-1009
SEC-1010
SEC-1016
SEC-1022
SEC-1024
SEC-1025
SEC-1026
SEC-1028
SEC-1029
SEC-1030

Fabric OS Message Reference
53-1002749-01

85

2

SEC Messages

SEC-1031
SEC-1032
SEC-1033
SEC-1034
SEC-1035
SEC-1036
SEC-1037
SEC-1038
SEC-1039
SEC-1040
SEC-1041
SEC-1042
SEC-1043
SEC-1044
SEC-1045
SEC-1046
SEC-1049
SEC-1050
SEC-1051
SEC-1052
SEC-1053
SEC-1054
SEC-1055
SEC-1056
SEC-1057
SEC-1059
SEC-1062
SEC-1063
SEC-1064
SEC-1065
SEC-1069
SEC-1071
SEC-1072
SEC-1073
SEC-1074

86

Fabric OS Message Reference
53-1002749-01

SEC Messages

2

SEC-1075
SEC-1076
SEC-1077
SEC-1078
SEC-1079
SEC-1080
SEC-1081
SEC-1082
SEC-1083
SEC-1084
SEC-1085
SEC-1086
SEC-1087
SEC-1088
SEC-1089
SEC-1090
SEC-1091
SEC-1092
SEC-1093
SEC-1094
SEC-1095
SEC-1096
SEC-1097
SEC-1098
SEC-1099
SEC-1100
SEC-1101
SEC-1102
SEC-1104
SEC-1105
SEC-1106
SEC-1107
SEC-1108
SEC-1110
SEC-1111

Fabric OS Message Reference
53-1002749-01

87

2

SEC Messages

SEC-1112
SEC-1113
SEC-1114
SEC-1115
SEC-1116
SEC-1117
SEC-1118
SEC-1119
SEC-1121
SEC-1122
SEC-1123
SEC-1124
SEC-1126
SEC-1130
SEC-1135
SEC-1136
SEC-1137
SEC-1138
SEC-1139
SEC-1142
SEC-1145
SEC-1146
SEC-1153
SEC-1154
SEC-1155
SEC-1156
SEC-1157
SEC-1158
SEC-1159
SEC-1160
SEC-1163
SEC-1164
SEC-1165
SEC-1166
SEC-1167

88

Fabric OS Message Reference
53-1002749-01

SEC Messages

2

SEC-1168
SEC-1170
SEC-1171
SEC-1172
SEC-1173
SEC-1174
SEC-1175
SEC-1176
SEC-1180
SEC-1181
SEC-1182
SEC-1183
SEC-1184
SEC-1185
SEC-1186
SEC-1187
SEC-1188
SEC-1189
SEC-1190
SEC-1191
SEC-1192
SEC-1193
SEC-1194
SEC-1195
SEC-1196
SEC-1197
SEC-1198
SEC-1199
SEC-1200
SEC-1201
SEC-1202
SEC-1203
SEC-1250
SEC-1251
SEC-1253

Fabric OS Message Reference
53-1002749-01

89

2

SEC Messages

SEC-1300
SEC-1301
SEC-1302
SEC-1303
SEC-1304
SEC-1305
SEC-1306
SEC-1307
SEC-1308
SEC-1309
SEC-1310
SEC-1311
SEC-1312
SEC-1313
SEC-1314
SEC-1315
SEC-1316
SEC-1317
SEC-1318
SEC-1319
SEC-1320
SEC-1321
SEC-1322
SEC-1323
SEC-1324
SEC-1325
SEC-1326
SEC-1327
SEC-1328
SEC-1329
SEC-1330
SEC-1331
SEC-1332
SEC-1333
SEC-1334

90

Fabric OS Message Reference
53-1002749-01

SFLO Messages

2

SEC-1335
SEC-1336
SEC-1337
SEC-1338
SEC-1339
SEC-3035
SEC-3036
SEC-3037
SEC-3038
SEC-3039
SEC-3050
SEC-3051
SEC-3061
SEC-3062
SEC-3063
SEC-3064
SEC-3065
SEC-3066
SEC-3067
SEC-4001

SFLO Messages
SFLO-1001
SFLO-1002
SFLO-1003
SFLO-1004
SFLO-1005
SFLO-1006
SFLO-1007
SFLO-1008

SNMP Messages
SNMP-1001
SNMP-1002

Fabric OS Message Reference
53-1002749-01

91

2

SPC Messages

SNMP-1003
SNMP-1004
SNMP-1005
SNMP-1006
SNMP-1009

SPC Messages
SPC-1001
SPC-1002
SPC-1003
SPC-2001
SPC-2002
SPC-2003
SPC-2004
SPC-2005
SPC-2006
SPC-2007
SPC-2008
SPC-2009
SPC-2010
SPC-2011
SPC-2012
SPC-2013
SPC-2014
SPC-2040
SPC-2041
SPC-2042
SPC-2043
SPC-2044
SPC-3001
SPC-3002
SPC-3003
SPC-3004
SPC-3005
SPC-3006

92

Fabric OS Message Reference
53-1002749-01

SPM Messages

2

SPC-3007
SPC-3008
SPC-3009
SPC-3010
SPC-3011
SPC-3012
SPC-3013
SPC-3014
SPC-3015

SPM Messages
SPM-1001
SPM-1002
SPM-1003
SPM-1004
SPM-1005
SPM-1006
SPM-1007
SPM-1008
SPM-1009
SPM-1010
SPM-1011
SPM-1012
SPM-1013
SPM-1014
SPM-1015
SPM-1016
SPM-3001
SPM-3002
SPM-3003
SPM-3004
SPM-3005
SPM-3006
SPM-3007
SPM-3008

Fabric OS Message Reference
53-1002749-01

93

2

SS Messages

SPM-3009
SPM-3010
SPM-3011
SPM-3012
SPM-3013
SPM-3014
SPM-3015
SPM-3016
SPM-3017
SPM-3018
SPM-3019
SPM-3020
SPM-3021
SPM-3022
SPM-3023
SPM-3024
SPM-3025
SPM-3026
SPM-3027
SPM-3028
SPM-3029

SS Messages
SS-1000
SS-1001
SS-1002
SS-1003
SS-1004
SS-1005
SS-1006
SS-1007
SS-1008
SS-1009
SS-1010
SS-1011

94

Fabric OS Message Reference
53-1002749-01

SSMD Messages

2

SS-1012

SSMD Messages
SSMD-1001
SSMD-1002
SSMD-1003
SSMD-1004
SSMD-1005
SSMD-1006
SSMD-1007
SSMD-1008
SSMD-1200
SSMD-1201
SSMD-1202
SSMD-1203
SSMD-1204
SSMD-1205
SSMD-1206
SSMD-1207
SSMD-1208
SSMD-1209
SSMD-1210
SSMD-1211
SSMD-1212
SSMD-1213
SSMD-1214
SSMD-1215
SSMD-1216
SSMD-1217
SSMD-1300
SSMD-1301
SSMD-1302
SSMD-1303
SSMD-1304
SSMD-1305

Fabric OS Message Reference
53-1002749-01

95

2

SULB Messages

SSMD-1306
SSMD-1307
SSMD-1308
SSMD-1309
SSMD-1310
SSMD-1311
SSMD-1312
SSMD-1313
SSMD-1314
SSMD-1315
SSMD-1316
SSMD-1317
SSMD-1318

SULB Messages
SULB-1001
SULB-1002
SULB-1003
SULB-1004
SULB-1005
SULB-1006
SULB-1007
SULB-1008
SULB-1009
SULB-1010
SULB-1011
SULB-1017
SULB-1018
SULB-1020
SULB-1021
SULB-1022
SULB-1023
SULB-1024
SULB-1025
SULB-1026

96

Fabric OS Message Reference
53-1002749-01

SWCH Messages

2

SULB-1030
SULB-1031
SULB-1032
SULB-1033
SULB-1034
SULB-1035
SULB-1036
SULB-1037
SULB-1038
SULB-1039
SULB-1040
SULB-1041
SULB-1042
SULB-1043
SULB-1044

SWCH Messages
SWCH-1001
SWCH-1002
SWCH-1003
SWCH-1004
SWCH-1005
SWCH-1006
SWCH-1007
SWCH-1008
SWCH-1009
SWCH-1010
SWCH-1011
SWCH-1012
SWCH-1013
SWCH-1014
SWCH-1015
SWCH-1016
SWCH-1017
SWCH-1018

Fabric OS Message Reference
53-1002749-01

97

2

SYSC Messages

SWCH-1019
SWCH-1020
SWCH-1021
SWCH-1022
SWCH-1023
SWCH-1024
SWCH-1025
SWCH-1026

SYSC Messages
SYSC-1001
SYSC-1002
SYSC-1004
SYSC-1005

SYSM Messages
SYSM-1001
SYSM-1002
SYSM-1003
SYSM-1004
SYSM-1005
SYSM-1006
SYSM-1007

TAPE Messages
TAPE-1001

TRCE Messages
TRCE-1001
TRCE-1002
TRCE-1003
TRCE-1004
TRCE-1005
TRCE-1006

98

Fabric OS Message Reference
53-1002749-01

TRCK Messages

2

TRCE-1007
TRCE-1008
TRCE-1009
TRCE-1010
TRCE-1011
TRCE-1012
TRCE-1013

TRCK Messages
TRCK-1001
TRCK-1002
TRCK-1003
TRCK-1004
TRCK-1005
TRCK-1006

TS Messages
TS-1001
TS-1002
TS-1006
TS-1007
TS-1008

UCST Messages
UCST-1003
UCST-1007
UCST-1020
UCST-1021
UCST-1022
UCST-1023
UCST-1024
UCST-1026
UCST-1027

Fabric OS Message Reference
53-1002749-01

99

2

UPTH Messages

UPTH Messages
UPTH-1001
UPTH-1002

VDR Messages
VDR-2001

VS Messages
VS-1001
VS-1002
VS-1003
VS-1004
VS-1005
VS-1006
VS-1007
VS-1008

WEBD Messages
WEBD-1001
WEBD-1002
WEBD-1004
WEBD-1005
WEBD-1006
WEBD-1007
WEBD-1008

XTUN Messages
XTUN-1000
XTUN-1001
XTUN-1002
XTUN-1003
XTUN-1004
XTUN-1005

100

Fabric OS Message Reference
53-1002749-01

ZEUS Messages

2

XTUN-1006
XTUN-1007
XTUN-1996
XTUN-1997
XTUN-1998
XTUN-1999
XTUN-2000
XTUN-2001
XTUN-2002
XTUN-2003
XTUN-2004
XTUN-2005
XTUN-2006
XTUN-2007
XTUN-2008
XTUN-2009
XTUN-2010
XTUN-2011
XTUN-2020
XTUN-2021
XTUN-2022
XTUN-2023
XTUN-2024
XTUN-2025

ZEUS Messages
ZEUS-1001
ZEUS-1002
ZEUS-1003
ZEUS-1004
ZEUS-1005
ZEUS-1015
ZEUS-1016
ZEUS-1028

Fabric OS Message Reference
53-1002749-01

101

2

ZONE Messages

ZONE Messages
ZONE-1002
ZONE-1003
ZONE-1004
ZONE-1007
ZONE-1010
ZONE-1013
ZONE-1015
ZONE-1017
ZONE-1019
ZONE-1022
ZONE-1023
ZONE-1024
ZONE-1026
ZONE-1027
ZONE-1028
ZONE-1029
ZONE-1034
ZONE-1036
ZONE-1037
ZONE-1038
ZONE-1039
ZONE-1040
ZONE-1041
ZONE-1042
ZONE-1043
ZONE-1044
ZONE-1045
ZONE-1046
ZONE-1048
ZONE-1049
ZONE-1054
ZONE-1057
ZONE-1058

102

Fabric OS Message Reference
53-1002749-01

ZONE Messages

2

ZONE-1059
ZONE-1060
ZONE-1061
ZONE-1062

Fabric OS Message Reference
53-1002749-01

103

2

104

ZONE Messages

Fabric OS Message Reference
53-1002749-01

Chapter

Audit Messages

3

AG Messages
AG-1033
AG-1034
AG-1035
AG-1036
AG-1037

AN Messages
AN-1003
AN-1004
AN-1005
AN-1006
AN-1010
AN-1011
AN-1012
AN-1013

AUTH Messages
AUTH-1045
AUTH-1046
AUTH-1047
AUTH-3001
AUTH-3002
AUTH-3003
AUTH-3004
AUTH-3005
AUTH-3006
AUTH-3007
AUTH-3008

Fabric OS Message Reference
53-1002749-01

105

3

BLS Messages

BLS Messages
BLS-1002
BLS-1003

CCFG Messages
CCFG-1002
CCFG-1003
CCFG-1013

CNM Messages
CNM-3001
CNM-3002
CNM-3003
CNM-3004
CNM-3005
CNM-3006
CNM-3007
CNM-3008
CNM-3009
CNM-3010
CNM-3011
CNM-3012

CONF Messages
CONF-1000
CONF-1020
CONF-1022
CONF-1042
CONF-1043
CONF-1044

CVLM Messages
CVLM-3001

106

Fabric OS Message Reference
53-1002749-01

ESS Messages

3

CVLM-3002
CVLM-3003
CVLM-3004
CVLM-3005
CVLM-3006
CVLM-3007
CVLM-3008
CVLM-3009
CVLM-3010
CVLM-3011
CVLM-3012
CVLM-3013
CVLM-3014
CVLM-3015
CVLM-3016
CVLM-3017
CVLM-3018
CVLM-3019
CVLM-3020
CVLM-3021
CVLM-3022
CVLM-3023
CVLM-3024
CVLM-3025
CVLM-3026
CVLM-3027
CVLM-3028

ESS Messages
ESS-1008
ESS-1009
ESS-1010

Fabric OS Message Reference
53-1002749-01

107

3

FICU Messages

FICU Messages
FICU-1011
FICU-1012
FICU-1019
FICU-1020
FICU-1021

FW Messages
FW-1202
FW-1274
FW-1402
FW-1404
FW-1405
FW-1406
FW-3001

HAM Messages
HAM-1015

HTTP Messages
HTTP-1002
HTTP-1003

IPAD Messages
IPAD-1002

LOG Messages
LOG-1005
LOG-1006
LOG-1007
LOG-1008
LOG-1011

108

Fabric OS Message Reference
53-1002749-01

MS Messages

3

MS Messages
MS-1027
MS-1028
MS-1029
MS-1030

PMGR Messages
PMGR-1001
PMGR-1003

PORT Messages
PORT-1006
PORT-1007
PORT-1008
PORT-1009

RAS Messages
RAS-2001
RAS-2002
RAS-2003
RAS-3005

SEC Messages
SEC-1113
SEC-1114
SEC-1337
SEC-3001
SEC-3002
SEC-3003
SEC-3004
SEC-3005
SEC-3006
SEC-3007

Fabric OS Message Reference
53-1002749-01

109

3

SEC Messages

SEC-3008
SEC-3009
SEC-3010
SEC-3011
SEC-3012
SEC-3013
SEC-3014
SEC-3015
SEC-3016
SEC-3017
SEC-3018
SEC-3019
SEC-3020
SEC-3021
SEC-3022
SEC-3023
SEC-3024
SEC-3025
SEC-3026
SEC-3027
SEC-3028
SEC-3029
SEC-3030
SEC-3031
SEC-3032
SEC-3033
SEC-3034
SEC-3035
SEC-3036
SEC-3037
SEC-3038
SEC-3039
SEC-3044
SEC-3045
SEC-3046

110

Fabric OS Message Reference
53-1002749-01

SNMP Messages

3

SEC-3047
SEC-3048
SEC-3049
SEC-3050
SEC-3051
SEC-3061
SEC-3062
SEC-3063
SEC-3064
SEC-3065
SEC-3066
SEC-3067
SEC-4001

SNMP Messages
SNMP-1004
SNMP-1005
SNMP-1006
SNMP-1009

SPM Messages
SPM-3001
SPM-3002
SPM-3003
SPM-3004
SPM-3005
SPM-3006
SPM-3007
SPM-3008
SPM-3009
SPM-3010
SPM-3011
SPM-3012
SPM-3013

Fabric OS Message Reference
53-1002749-01

111

3

SULB Messages

SPM-3014
SPM-3015
SPM-3016
SPM-3017
SPM-3018
SPM-3019
SPM-3020
SPM-3021
SPM-3022
SPM-3023
SPM-3024
SPM-3025
SPM-3026
SPM-3027
SPM-3028
SPM-3029

SULB Messages
SULB-1001
SULB-1002
SULB-1003
SULB-1004
SULB-1009
SULB-1010
SULB-1017
SULB-1018
SULB-1020
SULB-1021
SULB-1023
SULB-1024
SULB-1026
SULB-1030
SULB-1031
SULB-1032
SULB-1033

112

Fabric OS Message Reference
53-1002749-01

SWCH Messages

3

SULB-1034
SULB-1035
SULB-1037
SULB-1038
SULB-1039
SULB-1040
SULB-1041
SULB-1042

SWCH Messages
SWCH-1012
SWCH-1013
SWCH-1014

UCST Messages
UCST-1021
UCST-1022
UCST-1023
UCST-1024
UCST-1026
UCST-1027

ZONE Messages
ZONE-3001
ZONE-3002
ZONE-3003
ZONE-3004
ZONE-3005
ZONE-3006
ZONE-3007
ZONE-3008
ZONE-3009
ZONE-3010
ZONE-3011

Fabric OS Message Reference
53-1002749-01

113

3

ZONE Messages

ZONE-3012
ZONE-3013
ZONE-3014
ZONE-3015
ZONE-3016
ZONE-3017
ZONE-3018
ZONE-3019
ZONE-3020
ZONE-3021
ZONE-3022
ZONE-3023
ZONE-3024
ZONE-3025
ZONE-3026

114

Fabric OS Message Reference
53-1002749-01

Chapter

FFDC Messages

4

ANV Messages
ANV-1002

AUTH Messages
AUTH-1014
AUTH-1044

BKSW Messages
BKSW-1003

BL Messages
BL-1002
BL-1003
BL-1004
BL-1008
BL-1009
BL-1011
BL-1016
BL-1020

BLS Messages
BLS-1000
BLS-1001

BM Messages
BM-1003
BM-1053

Fabric OS Message Reference
53-1002749-01

115

4

C2 Messages

C2 Messages
C2-1002
C2-1012

C3 Messages
C3-1002
C3-1012

CDR Messages
CDR-1002

CHS Messages
CHS-1002

EM Messages
EM-1001
EM-1002
EM-1003
EM-1004
EM-1005
EM-1006
EM-1008
EM-1009
EM-1010
EM-1011
EM-1012
EM-1018
EM-1020
EM-1028
EM-1068
EM-1071
EM-1072

116

Fabric OS Message Reference
53-1002749-01

FABR Messages

4

FABR Messages
FABR-1011
FABR-1013
FABR-1019
FABR-1020
FABR-1021
FABR-1022
FABR-1031
FABR-1054

FABS Messages
FABS-1001

FCMC Messages
FCMC-1001

FCPH Messages
FCPH-1001

FLOD Messages
FLOD-1004

HAM Messages
HAM-1001
HAM-1006
HAM-1007
HAM-1008
HAM-1009
HAM-1011

HAMK Messages
HAMK-1001

Fabric OS Message Reference
53-1002749-01

117

4

HIL Messages

HIL Messages
HIL-1107
HIL-1108
HIL-1502
HIL-1503
HIL-1506
HIL-1507
HIL-1508
HIL-1509
HIL-1602
HIL-1603
HIL-1611

HLO Messages
HLO-1001
HLO-1002

HMON Messages
HMON-1001

KSWD Messages
KSWD-1001
KSWD-1002

LFM Messages
LFM-1004

LOG Messages
LOG-1001
LOG-1002

LSDB Messages
LSDB-1003

118

Fabric OS Message Reference
53-1002749-01

MPTH Messages

4

MPTH Messages
MPTH-1001
MPTH-1002

NBFS Messages
NBFS-1002

PDM Messages
PDM-1017

PLAT Messages
PLAT-1000
PLAT-1003
PLAT-1004
PLAT-1072

PS Messages
PS-1000

RAS Messages
RAS-1004
RAS-1005

RCS Messages
RCS-1012
RCS-1013

SCN Messages
SCN-1001
SCN-1002

Fabric OS Message Reference
53-1002749-01

119

4

SNMP Messages

SNMP Messages
SNMP-1004

SYSC Messages
SYSC-1001
SYSC-1002

SYSM Messages
SYSM-1001
SYSM-1005
SYSM-1006

TRCE Messages
TRCE-1008

UCST Messages
UCST-1007

WEBD Messages
WEBD-1008

ZEUS Messages
ZEUS-1002

120

Fabric OS Message Reference
53-1002749-01

Chapter

Fabric OS System Messages

5

AG Messages
AG-1001
Message
Message Type
Severity

N_Port ID virtualization (NPIV) is not supported by fabric port connected to port
.

LOG
ERROR

Probable Cause

Indicates that the N_Port ID virtualization (NPIV) capability is not supported by the fabric port to which
the Access Gateway is connected.

Recommended
Action

•

Execute the portCfgNpivPort command to enable NPIV capability on the port connected to the
Access Gateway.

•

Some blades and ports in a switch may not support NPIV. NPIV functionality cannot be enabled
on such ports and they will not respond to NPIV requests. Refer to the Access Gateway
Administrator's Guide for specific AG-compatibility requirements.

•

On non-Brocade switches, refer to the manufacturer's documentation to determine whether
the switch supports NPIV and how to enable NPIV on these types of switches.

AG-1002
Message
Message Type
Severity

Unable to find alternate N_Port during failover for N_Port .

LOG
WARNING

Probable Cause

Indicates that no other N_Port is configured or the fabric was unstable during failover.

Recommended
Action

Check whether an alternate N_Port is configured using the portCfgShow command.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

Fabric OS Message Reference
53-1002749-01

121

5

AG-1003

AG-1003
Message
Message Type
Severity

Unable to failover N_Port . Failover across different fabric is not
supported.

LOG
WARNING

Probable Cause

Indicates that the failover does not get blocked between two fabrics, although it is not a supported
configuration.

Recommended
Action

Configure two or more N_Ports to connect to the same fabric; then execute the ag --failoverenable
command to enable failover on these N_Ports.

AG-1004
Message
Message Type
Severity

Invalid response to fabric login (FLOGI) request from the fabric for N_Port .

LOG
ERROR

Probable Cause

Indicates that the fabric sent an invalid response to the FLOGI Extended Link Service (ELS) for the
specified N_Port.

Recommended
Action

Check the configuration of the fabric switch.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AG-1005
Message
Message Type
Severity

FDISC response was dropped because F_Port  is offline.

LOG
WARNING

Probable Cause

Indicates that the F_Port connected to the host is offline, which caused the Fabric Discovery (FDISC)
response to drop.

Recommended
Action

Check the configuration of the host connected to the specified F_Port.

122

Fabric OS Message Reference
53-1002749-01

AG-1006

5

AG-1006
Message

Access Gateway mode has been .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the Access Gateway mode has been enabled or disabled.

Recommended
Action

Execute the ag --modeshow command to verify the current status of the Access Gateway mode.

AG-1007
Message
Message Type
Severity

FLOGI response not received for the N_Port  connected to the fabric.

LOG
WARNING

Probable Cause

Indicates that the N_Port connected to the fabric switch is not online. The specified N_Port has been
disabled.

Recommended
Action

Check the connectivity between the Access Gateway N_Port and the fabric switch port.

AG-1008
Message
Message Type
Severity

Invalid Port Login (PLOGI) response from the fabric on the N_Port .

LOG
WARNING

Probable Cause

Indicates that the fabric switch management server did not accept the N_Port Login (PLOGI) request
sent by the Access Gateway.

Recommended
Action

Check the configuration of the fabric switch connected to the Access Gateway.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

Fabric OS Message Reference
53-1002749-01

123

5

AG-1009

AG-1009
Message
Message Type
Severity

Sending FLOGI failed on N_Port .

LOG
WARNING

Probable Cause

Indicates that there was a failure sending a Fabric Login (FLOGI) request from the Access Gateway to
the fabric switch.

Recommended
Action

Check the configuration of the fabric switch connected to the Access Gateway.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AG-1010
Message
Message Type
Severity

Sending PLOGI failed on N_Port .

LOG
WARNING

Probable Cause

Indicates that there was a failure sending an N_Port Login (PLOGI) request from the Access Gateway to
the fabric switch.

Recommended
Action

Check the configuration of the fabric switch connected to the Access Gateway.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AG-1011
Message
Message Type
Severity

Sending FDISC failed on N_Port .

LOG
WARNING

Probable Cause

Indicates that there was a failure sending a discover F_Port service parameter request from the Access
Gateway to the fabric switch.

Recommended
Action

Check the configuration of the fabric switch connected to the Access Gateway.

124

If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

Fabric OS Message Reference
53-1002749-01

AG-1012

5

AG-1012
Message
Message Type
Severity

Sending logout (LOGO) request failed on N_Port .

LOG
WARNING

Probable Cause

Indicates that there was a failure sending an N_Port logout request from the Access Gateway to the
fabric switch.

Recommended
Action

Check the configuration of the fabric switch connected to the Access Gateway.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AG-1013
Message

F_Ports mapped to N_Port  failed over to other N_Port(s).

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the specified N_Port is failing over to other N_Ports connected to the same fabric.

Recommended
Action

Execute the ag --mapshow command to display updated F_Port-to-N_Port mapping.

AG-1014
Message

Failing back F_Ports mapped to N_Port .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the specified N_Port is failing back F_Ports mapped to it.

Recommended
Action

Execute the ag --mapshow command to display updated F_Port-to-N_Port mapping.

Fabric OS Message Reference
53-1002749-01

125

5

AG-1015

AG-1015
Message
Message Type
Severity

Unable to find online N_Ports to connect to the fabric.

LOG
WARNING

Probable Cause

Indicates that no other N_Port is configured or all N_Ports are currently offline.

Recommended
Action

Check whether any other N_Port is configured using the portCfgShow command.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AG-1016
Message

Failing over F_Ports mapped to N_Port  to other N_Port(s).

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the specified N_Port has failed to come online. All F_Ports mapped to this N_Port are
being failed over to other active N_Ports.

Recommended
Action

Execute the ag --mapshow command to display updated F_Port-to-N_Port mapping.

AG-1017
Message
Message Type
Severity

No N_Port(s) are currently Online.

LOG
WARNING

Probable Cause

Indicates that no N_Ports are currently configured in the system or all configured N_Ports have failed to
come online.

Recommended
Action

Execute the switchShow command to display the status of all ports in the system. Execute the
portCfgShow command to display the list of ports currently configured as N_Ports.

126

Fabric OS Message Reference
53-1002749-01

AG-1018

5

AG-1018
Message
Message Type
Severity

Host port should not be connected to port  which is configured as
N_Port.

LOG
ERROR

Probable Cause

Indicates that an initiator or target port is erroneously connected to a port configured for N_Port
operation.

Recommended
Action

Execute the switchShow command to display the status of all ports in the system. Execute the
portCfgShow command to display the list of ports currently configured as N_Ports. Make sure the host
is connected to an F_port.

AG-1019
Message
Message Type
Severity

Unable to failover N_Port . No other N_Port in port group: is
online.

LOG
WARNING

Probable Cause

Indicates that failover across port groups is not supported.

Recommended
Action

Check whether an alternate N_Port is configured in the specified port group using the ag --pgshow
command.

AG-1020
Message

F_Ports to N_Ports route/mapping has been changed.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that F_Port-to-N_Port mapping has been changed because the switch has come online or
some new N_Ports or F_Ports have come online.

Recommended
Action

Execute the ag --mapshow command to display the updated F_Port-to-N_Port mapping.

Fabric OS Message Reference
53-1002749-01

127

5

AG-1021

AG-1021
Message
Message Type
Severity

Unable to do Preferred-Failover of F_Port . Failover across different
fabric is not supported.

LOG
WARNING

Probable Cause

Indicates that failover across N_Ports connected to different fabrics is not supported.

Recommended
Action

Change the preferred N_Port settings of the specified F_Port using the ag --prefset command.
Choose the preferred N_Port so that it is in the same fabric as the primary N_Port of this F_Port. Execute
the ag --show command to check the fabric connectivity of the N_Ports.

AG-1022
Message

F_Port  is failed over to its preferred N_Port .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates the specified F_Port is failing over to its preferred N_Port.

Recommended
Action

Execute the ag --mapshow command to display the updated F_Port-to-N_Port mapping.

AG-1023
Message

F_Port  mapped to offline N_Port  is failed over to its preferred
N_Port .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the specified N_Port has failed to come online. The F_Port mapped to this N_Port had its
preferred set and is online.

Recommended
Action

Execute the ag --mapshow command to display updated F_Port-to-N_Port mapping.

128

Fabric OS Message Reference
53-1002749-01

AG-1024

5

AG-1024
Message

F_Port  is failed back to its preferred N_Port .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the specified N_Port is failing back F_Ports, which are failed over to some other N_Port.

Recommended
Action

Execute the ag --mapshow command to display the updated F_Port-to-N_Port mapping.

AG-1025
Message
Message Type
Severity

Port group of Slave N_Port  is different than its Master N_Port
.

LOG
ERROR

Probable Cause

Indicates that the port groups of the Master and Slave N_Ports are different, while the trunk area
assigned to the attached F_Ports on the edge switch is the same.

Recommended
Action

Execute the porttrunkarea --show command on the attached switch to verify that the trunk area is
assigned to all ports in the system, and execute the porttrunkarea --enable command to reconfigure the
trunk area.

AG-1026
Message
Message Type
Severity

Unable to handle the login request on port  due to insufficient
resources.

LOG
WARNING

Probable Cause

Indicates that there are insufficient resources to accept the login request.

Recommended
Action

Execute the configure command on the Access Gateway switch and increase the number of allowed
logins on the specified port.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

Fabric OS Message Reference
53-1002749-01

129

5

AG-1027

AG-1027
Message
Message Type
Severity

Unable to handle this login request on port  because NPIV capability
is not enabled on this port.

LOG
WARNING

Probable Cause

Indicates that N_Port ID virtualization (NPIV) is not enabled on the specified port.

Recommended
Action

Execute the portCfgNpivPort command on the Access Gateway switch to enable the NPIV capability on
the port.

AG-1028
Message
Message Type
Severity

Device with Port WWN  tried to perform fabric login through port
, without having access permission.

LOG
WARNING

Probable Cause

Indicates that the device does not have login access for the specified port as per Advanced Device
Security (ADS) policy set by the user.

Recommended
Action

Add the device to the ADS allow list for the specified port using the ag --adsadd command.

AG-1029
Message
Message Type
Severity

Port Group (ID: ) has ports going to different fabrics.

LOG
WARNING

Probable Cause

Indicates a misconfiguration.

Recommended
Action

Connect all ports in the port group to the same fabric.

130

Fabric OS Message Reference
53-1002749-01

AG-1030

5

AG-1030
Message
Message Type
Severity

N_Port (ID: ) has been determined to be unreliable.

LOG
WARNING

Probable Cause

Indicates that the port goes online and offline often and therefore the port is marked as unreliable.

Recommended
Action

No action is required. The port will automatically be marked as reliable after a certain interval of time, if
the port toggling remains within the threshold limit.

AG-1031
Message
Message Type
Severity

Loop Detected for device with Port WWN  connected to port .

LOG
WARNING

Probable Cause

Indicates that a routing loop is detected for the device connected to the specified port.

Recommended
Action

Check the device configuration.

AG-1032
Message

N_Port (ID: ) has recovered from an unreliable state.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the port state has been stable for the last five minutes.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

131

5

AG-1033

AG-1033
Message
Message Type

F_Port to N_Port mapping has been updated for N_Port ().

AUDIT | LOG

Class

CFG

Severity

INFO

Probable Cause

Indicates that the F_Ports mapped to an N_Port have changed and the configuration file has been
updated.

Recommended
Action

No action is required.

AG-1034
Message
Message Type

F_Port cannot accept any more logins ().

AUDIT | LOG

Class

CFG

Severity

INFO

Probable Cause

Indicates that the F_Port has already logged in the maximum number of devices.

Recommended
Action

No action is required.

AG-1035
Message
Message Type

Device cannot login as ALPA value is not available ().

AUDIT | LOG

Class

CFG

Severity

INFO

Probable Cause

Indicates that a device has already used the specified arbitrated loop physical address (ALPA) value.

Recommended
Action

No action is required.

132

Fabric OS Message Reference
53-1002749-01

AG-1036

5

AG-1036
Message
Message Type
Class
Severity

Port  is connected to a non-Brocade fabric with Persistent ALPA
enabled. Check the admin guide for supported configuration.

AUDIT | LOG
CFG
WARNING

Probable Cause

Indicates that one of the ports is connected to a non-Brocade fabric.

Recommended
Action

Refer to the Access Gateway Administrator's Guide for the supported configuration.

AG-1037
Message

Message Type

Trunked N_Port () going offline. If switchshow CLI for the connected
fabric switch port displays Persistently disabled: Area has been acquired, then
check cabling: all trunked ports should be in same ASIC Port Group.

AUDIT | LOG

Class

CFG

Severity

INFO

Probable Cause

Indicates an incorrect cabling.

Recommended
Action

If the switchShow command on the connected fabric switch port displays "Persistently disabled: Area
has been acquired", then check cabling on the Access Gateway. All trunked ports in a single trunk must
belong to the same application-specific integrated circuit (ASIC) port group.

AG-1038
Message
Message Type
Severity

Brocade 8000 ports are going to different fabrics, check N_Port ().

LOG
ERROR

Probable Cause

Indicates a misconfiguration.

Recommended
Action

Connect all ports in the port group to the same fabric.

Fabric OS Message Reference
53-1002749-01

133

5

AG-1039

AG-1039
Message

F_Port  was reset because a WWN mapped device using it,
through N_Port , went offline.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the specified F_Port was reset because an N_Port went offline and the changes need to be
propagated to all involved devices.

Recommended
Action

No action is required. This port reset was not an error.

AG-1040
Message
Message Type
Severity

PID of the devices connected to Port  may have changed, as the port
was toggled. Check EE monitor configuration as it might not be functional.

LOG
WARNING

Probable Cause

Indicates that N_Port ID virtualization (NPIV) assigns a new port ID (PID) each time the same port is
disabled and then re-enabled. As the PID has changed, the end-to-end (EE) monitors installed with the
previous PID stops functioning.

Recommended
Action

Install new EE monitors with the new PID of the port to be monitored by using the perfAddEEMonitor
command.

AG-1041
Message
Message Type
Severity

Static F_Ports mapped to N_Port  are disabled as Trunking is enabled
on the N_Port.

LOG
WARNING

Probable Cause

Indicates that a trunk is enabled on the specified N_Port, and therefore the F_Port static mapping is
disabled.

Recommended
Action

Delete static mapping on the Access Gateway using the ag --staticdel command or disable the trunk on
the N_Port using the switchCfgTrunkPort command.

134

Fabric OS Message Reference
53-1002749-01

AG-1042

5

AG-1042
Message
Message Type
Severity

Sending ELS_PORT_OPEN failed on N_Port .

LOG
WARNING

Probable Cause

Indicates there was a failure sending an ELS_PORT_OPEN request from the Access Gateway to the
fabric switch.

Recommended
Action

Check the configuration of the fabric switch connected to the Access Gateway.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AG-1043
Message
Message Type
Severity

Authentication cannot be negotiated with the connected switch/HBA and therefore
disabling the Port .

LOG
WARNING

Probable Cause

Indicates that authentication has failed on the specified port. A possible reason could be that the edge
switch connected to Access Gateway is using firmware earlier than Fabric OS v7.1.0.

Recommended
Action

Check the authentication configuration of the edge switch using the authutil --show command.

AG-1044
Message
Message Type
Severity

Port  has been disabled because switch requires authentication when
device authentication policy is set to ON.

LOG
WARNING

Probable Cause

Indicates a device that does not support authentication has tried to log in to the switch when the device
authentication policy is in ON status on the switch.

Recommended
Action

Enable the authentication on the device or set the device authentication status to PASSIVE/OFF on the
switch if it is not mandatory. Use the authUtil command to change the device authentication policy.

Fabric OS Message Reference
53-1002749-01

135

5

AN-1001

AN Messages
AN-1001
Message
Message Type
Severity

Failed to allocate memory: ().

LOG
ERROR

Probable Cause

Indicates that the specified function has failed to allocate memory.

Recommended
Action

Check memory usage on the switch using the memShow command. Restart or power cycle the switch.

AN-1002
Message
Message Type
Severity

Failed to initialize; rc = .

LOG
ERROR

Probable Cause

Indicates that the initialization of the "trafd" daemon has failed.

Recommended
Action

Download a new firmware version using the firmwareDownload command.

AN-1003
Message

Message Type
Class
Severity
Probable Cause

Latency bottleneck on port /.
 pct. of  secs. affected.
Avg. delay  us. Avg.
slowdown .

LOG | AUDIT
FABRIC
WARNING
For an F_Port, indicates that the attached device is slow in responding to frames going out of the
specified port. This latency may be inherent in the device or due to heavy workload on the device.
For a long-distance E_Port, may indicate too few credits for the distance. For a non-long-distance
E_Port, indicates latency produced by a device downstream of the E_Port and is an indication of
back-pressure produced by that latency.

136

Fabric OS Message Reference
53-1002749-01

AN-1004

Recommended
Action

5

If the port is an F_Port, examine the connected device for the source of the latency. If the port is a
long-distance E_Port, make sure that there are enough buffer credits to service the link distance.

AN-1004
Message

Message Type
Class
Severity

Congestion bottleneck on port /.
 pct. of  secs. affected.

LOG | AUDIT
FABRIC
WARNING

Probable Cause

Indicates that the volume of outgoing traffic at the specified port is too high for the capacity of the link.

Recommended
Action

Add more capacity on the path, using trunk links if possible.

AN-1005
Message
Message Type
Class
Severity

Slot , port  has 
bottleneck cleared.

LOG | AUDIT
FABRIC
INFO

Probable Cause

Indicates that the bottleneck condition on the specified port has cleared.

Recommended
Action

No action is required.

AN-1006
Message
Message Type
Class
Severity

Bottleneck detection configuration is successfully changed.

AUDIT
FABRIC
INFO

Probable Cause

Indicates that the bottleneck detection configuration has been changed.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

137

5

AN-1010

AN-1010
Message
Message Type
Class
Severity

Severe latency bottleneck detected at slot  port .

LOG | AUDIT
FABRIC
WARNING

Probable Cause

Indicates credit loss at the specified port, a downstream port, or a very high latency device at the edge of
the fabric.

Recommended
Action

Contact your switch service provider for assistance.

AN-1011
Message

Message Type
Class
Severity

Could not distinguish between primary and dependent severe latency bottleneck on
slot  port  because port mirroring is
enabled on this port.

LOG | AUDIT
FABRIC
WARNING

Probable Cause

Indicates that resources that are needed to determine whether there is complete credit loss on a virtual
channel (VC) at the specified port are used by port mirroring.

Recommended
Action

Contact your switch service provider for assistance.

AN-1012
Message
Message Type
Class
Severity

Credits did not return from other end. Complete loss of credits on a VC on slot
 port .

LOG | AUDIT
FABRIC
WARNING

Probable Cause

Indicates a credit loss.

Recommended
Action

If this message is not followed by the AN-1013 message, contact your switch service provider for
assistance.

138

Fabric OS Message Reference
53-1002749-01

AN-1013

5

AN-1013
Message
Message Type
Class
Severity

Performed link reset to recover the port credits on slot  port .

LOG | AUDIT
FABRIC
INFO

Probable Cause

Indicates a credit loss.

Recommended
Action

The port is recovered. No action is required.

Fabric OS Message Reference
53-1002749-01

139

5

ANV-1001

ANV Messages
ANV-1001
Message
Message Type
Severity

Port  port fault. Change the SFP or check the cable.

LOG
ERROR

Probable Cause

Indicates a deteriorated small form-factor pluggable (SFP) transceiver, an incompatible SFP transceiver
pair, or a faulty cable between the peer ports.

Recommended
Action

Verify that compatible SFP transceivers are used on the peer ports, the SFP transceivers have not
deteriorated, and the Fibre Channel cable is not faulty. Replace the SFP transceivers or the cable, if
necessary.

ANV-1002
Message
Message Type
Severity

Port  chip faulted due to an internal error.

LOG | FFDC
ERROR

Probable Cause

Indicates an internal error. All the ports on the chip will be disrupted.

Recommended
Action

To recover a bladed system, execute the slotPowerOff and slotPowerOn commands on the blade. To
recover a non-bladed system, execute the fastBoot command on the switch.

ANV-1003
Message
Message Type
Severity

S,C: HW ASIC Chip error. Type = 0x,
Error = .

LOG
CRITICAL

Probable Cause

Indicates an internal error in the application-specific integrated circuit (ASIC) hardware that may degrade
the data traffic.

Recommended
Action

Restart the system at the next maintenance window. If the problem persists, replace the blade.

140

Fabric OS Message Reference
53-1002749-01

ANV-1004

5

ANV-1004
Message
Message Type
Severity

S,C: Invalid DMA ch pointer, chan:,
good_addr:0x bad_addr:0x.

LOG
ERROR

Probable Cause

Indicates an internal error in the application-specific integrated circuit (ASIC) hardware that may degrade
the data traffic.

Recommended
Action

Restart the system at the next maintenance window. If the problem persists, replace the blade.

ANV-1005
Message
Message Type
Severity

S,C,A: Memory allocation failed.

LOG
ERROR

Probable Cause

Indicates memory allocation failure in the software.

Recommended
Action

Restart the system at the next maintenance window. If the problem persists, replace the switch or contact
your switch service provider.

ANV-1006
Message
Message Type
Severity

S,C: HW ASIC Chip fault. Type = 0x,
Error = .

LOG
CRITICAL

Probable Cause

Indicates an internal error in the application-specific integrated circuit (ASIC) hardware that renders the
chip as not operational.

Recommended
Action

Restart the system at the next maintenance window. If the problem persists, replace the blade.

Fabric OS Message Reference
53-1002749-01

141

5

ANV-1007

ANV-1007
Message
Message Type
Severity

S,C: ANVIL PASS 1 low buff pool fault:  0x.

LOG
CRITICAL

Probable Cause

Indicates that Anvil Pass 1 is running out of free buffers, which may cause chip fault.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

ANV-1008
Message
Message Type
Severity

S,C: MAC-VID classifier table is full. No space for new
entry.

LOG
ERROR

Probable Cause

Indicates that the Media Access Control (MAC) VLAN ID (VID) classifier table is full and no more entries
can be added.

Recommended
Action

Delete some of the existing unused rules using the portcfg arp command and then add new entries.

ANV-1015
Message
Message Type
Severity

Port reinitialized due to Link Reset failure on internal port S,P().

LOG
WARNING

Probable Cause

Indicates that the specified port is re-initialized due to link reset failure.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

142

Fabric OS Message Reference
53-1002749-01

ANV-1016

5

ANV-1016
Message
Message Type
Severity

Port is faulted due to port reinitialization failure on internal port S,P() with reason .

LOG
WARNING

Probable Cause

Indicates that the specified port is faulted due to port re-initialization failure.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

ANV-1028
Message
Message Type
Severity

Detected excessive Link resets on the port in a second. Slot , Port
().

LOG
WARNING

Probable Cause

Indicates that the port received excessive link resets from peer port within 1 second and that exceeded
threshold.

Recommended
Action

When this error is observed persistently, change the small form-factor pluggable (SFP) transceiver or the
cable on the peer port to which this port is connected.

Fabric OS Message Reference
53-1002749-01

143

5

AUTH-1001

AUTH Messages
AUTH-1001
Message

 has been successfully completed.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the secret database operation has been updated using the secAuthSecret command. The
values for Operation type can be "set" or "remove".

Recommended
Action

No action is required.

AUTH-1002
Message
Message Type
Severity

 has failed.

LOG
ERROR

Probable Cause

Indicates that the specified action has failed to update the secret database using the secAuthSecret
command. The values for Operation type can be "set" or "remove".

Recommended
Action

Execute the secAuthSecret command again.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1003
Message

 type has been successfully set to .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that an authentication configuration value was set to a specified value. The data type is
authentication type, DH group type, hash type, or policy type.

Recommended
Action

No action is required.

144

Fabric OS Message Reference
53-1002749-01

AUTH-1004

5

AUTH-1004
Message
Message Type
Severity

Failed to set  type to .

LOG
ERROR

Probable Cause

Indicates that the authUtil command has failed to set the authentication configuration value. The data
type can be authentication type, DH group type, hash type, or policy type.

Recommended
Action

Execute the authUtil command again.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1005
Message
Message Type
Severity

Authentication file does not exist: .

LOG
ERROR

Probable Cause

Indicates an authentication file corruption.

Recommended
Action

Execute the firmwareDownload command to reinstall the firmware.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1006
Message
Message Type
Severity

Failed to open authentication configuration file.

LOG
WARNING

Probable Cause

Indicates an internal problem with the Secure Fabric OS.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

Fabric OS Message Reference
53-1002749-01

145

5

AUTH-1007

AUTH-1007
Message
Message Type
Severity

The proposed authentication protocol(s) are not supported: port .

LOG
ERROR

Probable Cause

Indicates that the proposed authentication protocol types are not supported by the specified local port.

Recommended
Action

Execute the authUtil command to make sure the local switch supports the Fibre Channel Authentication
Protocol (FCAP) or Diffie Hellman - Channel Authentication Protocol (DH-CHAP) protocols.

AUTH-1008
Message
Message Type
Severity

No security license, operation failed.

LOG
ERROR

Probable Cause

Indicates that the switch does not have a security license.

Recommended
Action

Verify that the security license is installed using the licenseShow command. If necessary, reinstall the
license using the licenseAdd command.

AUTH-1010
Message
Message Type
Severity

Failed to initialize security policy: switch , error .

LOG
ERROR

Probable Cause

Indicates an internal problem with the Secure Fabric OS.

Recommended
Action

Reboot or power cycle the switch.

146

If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

Fabric OS Message Reference
53-1002749-01

AUTH-1011

5

AUTH-1011
Message
Message Type
Severity

Failed to register for failover operation: switch  error .

LOG
WARNING

Probable Cause

Indicates an internal problem with the Secure Fabric OS.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1012
Message
Message Type
Severity

Authentication  is rejected: port  explain 
reason .

LOG
WARNING

Probable Cause

Indicates that the specified authentication is rejected because the remote entity does not support
authentication.

Recommended
Action

Verify the hash type, protocol, group, and authentication policy using the authutil --show command.

AUTH-1013
Message
Message Type
Severity

Cannot perform authentication request message: port , message code
.

LOG
WARNING

Probable Cause

Indicates that the system is running low on resources when receiving an authentication request. Usually
this problem is transient. The authentication may fail.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

Fabric OS Message Reference
53-1002749-01

147

5

AUTH-1014

AUTH-1014
Message
Message Type
Severity

Invalid port value to : port .

LOG | FFDC
ERROR

Probable Cause

Indicates an internal problem with the Secure Fabric OS.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1016
Message
Message Type
Severity

Invalid value to start HBA authentication port: , pid .

LOG
ERROR

Probable Cause

Indicates an internal failure.

Recommended
Action

Copy the message and collect the switch information using the supportShow command, and contact
your switch service provider.

AUTH-1017
Message
Message Type
Severity

Invalid value to start authentication request: port , operation code
.

LOG
ERROR

Probable Cause

Indicates an internal problem with the Secure Fabric OS.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

148

Fabric OS Message Reference
53-1002749-01

AUTH-1018

5

AUTH-1018
Message
Message Type
Severity

Invalid value to check protocol type: port .

LOG
ERROR

Probable Cause

Indicates an internal problem with the Secure Fabric OS.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1020
Message

Failed to create timer for authentication: port .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that an authentication message timer was not created. Usually this problem is transient. The
authentication may fail.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1022
Message
Message Type
Severity

Failed to extract  from  payload: port .

LOG
ERROR

Probable Cause

Indicates the authentication process failed to extract a particular value from the receiving payload.
Usually this problem is transient. The authentication may fail.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

Fabric OS Message Reference
53-1002749-01

149

5

AUTH-1023

AUTH-1023
Message
Message Type
Severity
Probable Cause

Failed to  during : port .

LOG
ERROR
Indicates an authentication operation failed for a certain authentication phase. The Operation type varies
depending on authentication type:

•

Some operations for Switch Link Authentication Protocol (SLAP): certificate retrieve, certificate
verification, signature verification, or nonce signing.

•

Some operations for Fibre Channel Authentication Protocol (FCAP): certificate retrieve,
certificate verification, signature verification, or nonce signing.

•

Some operations for Diffie Hellman - Challenge Handshake Authentication Protocol (DH-CHAP):
response calculation, challenge generation, or secret retrieve.

The authentication phase specifies which phase of a particular authentication protocol failed.
A nonce is a single-use, usually random value used in authentication protocols to prevent replay attacks.

Recommended
Action

The error may indicate that an invalid entity tried to connect to the switch. Check the connection port for
a possible unauthorized access attack.
It may indicate that the public key infrastructure (PKI) object for SLAP or FCAP or the secret value for
DH-CHAP on the local entity is not set up properly. Reinstall all PKI objects or reset the secret value for
DH-CHAP properly.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1025
Message
Message Type
Severity

Failed to get  during : port .

LOG
ERROR

Probable Cause

Indicates that the authentication process failed to get expected information during the specified
authentication phase. Usually this problem is transient. The authentication may fail.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

150

Fabric OS Message Reference
53-1002749-01

AUTH-1026

5

AUTH-1026
Message
Message Type
Severity

Failed to  during negotiation phase: port .

LOG
WARNING

Probable Cause

Indicates that the authentication failed to get device or Host Bus Adapter (HBA) information due to an
internal failure. Usually this problem is transient. If the authentication failed, retry the login.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1027
Message
Message Type
Severity

Failed to select  during : value
 port .

LOG
ERROR

Probable Cause

Indicates that the authentication process failed to select an authentication value (DH Group, hash value,
or protocol type) from a receiving payload for a particular authentication phase. This indicates that the
local switch does not support the specified authentication value.

Recommended
Action

Check the authentication configuration and reset the supported value if needed using the authUtil
command.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1028
Message
Message Type
Severity
Probable Cause

Failed to allocate  for : port .

LOG
ERROR
Indicates that the authentication process failed because the system is low on memory. Usually this
problem is transient. The authentication may fail.
The Data type is the payload or structure that failed to get memory. The Operation phase specifies which
operation of a particular authentication phase failed.

Fabric OS Message Reference
53-1002749-01

151

5

AUTH-1029

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1029
Message
Message Type
Severity
Probable Cause

Failed to get  for  message: port , retval
.

LOG
ERROR
Indicates that the authentication process failed to get a particular authentication value at a certain phase.
Usually this problem is transient. The authentication may fail.
The Data type is the payload or structure that failed to get memory.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1030
Message
Message Type
Severity

Invalid message code for  message: port .

LOG
ERROR

Probable Cause

Indicates that the receiving payload does not have a valid message code for a particular authentication
phase. Usually this problem is transient. The authentication may fail.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1031
Message
Message Type
Severity
Probable Cause

152

Failed to retrieve secret value: port .

LOG
ERROR
Indicates that the secret value was not set properly for the authenticated entity.

Fabric OS Message Reference
53-1002749-01

AUTH-1032

Recommended
Action

5

Reset the secret value using the secAuthSecret command.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1032
Message
Message Type
Severity
Probable Cause

Failed to generate  for  payload: length , error code , port .

LOG
ERROR
Indicates that the authentication process failed to generate specific data (challenge, nonce, or response
data) for an authentication payload. This usually relates to internal failure.
A nonce is a single-use, usually random value used in authentication protocols to prevent replay attacks.
Usually this problem is transient. The authentication may fail.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1033
Message
Message Type
Severity

Disable port  due to unauthorized switch .

LOG
ERROR

Probable Cause

Indicates that an entity was not configured in the Switch Connection Control (SCC) policy and tried to
connect to the port.

Recommended
Action

Add World Wide Name (WWN) of the entity to the SCC policy and reinitialize authentication by using the
portDisable and portEnable commands or the switchDisable and switchEnable commands.

AUTH-1034
Message
Message Type
Severity
Probable Cause

Failed to validate name  in : port .

LOG
ERROR
Indicates that the specified entity name in the payload is not in the correct format.

Fabric OS Message Reference
53-1002749-01

153

5

AUTH-1035

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1035
Message
Message Type
Severity

Invalid  length in  message: length , port
.

LOG
ERROR

Probable Cause

Indicates that a particular data field in the authentication message has an invalid length field. This error
usually relates to internal failure. Usually this problem is transient. The authentication may fail.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1036
Message
Message Type
Severity

Invalid state  for : port .

LOG
ERROR

Probable Cause

Indicates that the switch received an unexpected authentication message. Usually this problem is
transient. The authentication may fail.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

154

Fabric OS Message Reference
53-1002749-01

AUTH-1037

5

AUTH-1037
Message
Message Type
Severity
Probable Cause

Failed to  response for : init_len , resp_len , port .

LOG
ERROR
Indicates that a Diffie Hellman - Challenge Handshake Authentication Protocol (DH-CHAP)
authentication operation failed on the specified port due to mismatched response values between two
entities.
The error may indicate that an invalid entity tried to connect to the switch. Check the connection port for
a possible security attack.

Recommended
Action

Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1038
Message
Message Type
Severity

Failed to retrieve certificate during : port .

LOG
ERROR

Probable Cause

Indicates that the public key infrastructure (PKI) certificate is not installed properly.

Recommended
Action

Reinstall the PKI certificate using the secCertUtil command.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and
switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1039
Message
Message Type
Severity
Probable Cause

Neighboring switch has conflicting authentication policy: Port 
disabled.

LOG
ERROR
Indicates that the neighboring switch has a conflicting authentication policy enabled. The E_Port has
been disabled because the neighboring switch has rejected the authentication negotiation, and the local
switch has a strict switch authentication policy.

Fabric OS Message Reference
53-1002749-01

155

5

AUTH-1040

Recommended
Action

Correct the switch policy configuration on either of the switches using the authUtil command, and then
enable the port using the portEnable command.

AUTH-1040
Message

Reject authentication on port , because switch authentication policy
is set to OFF.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the local switch has rejected the authentication because the switch policy is turned off. If
the neighboring switch has a strict (ON) switch policy, the port will be disabled due to conflicting
configuration settings. Otherwise, the E_Port will form without authentication.

Recommended
Action

If the port is disabled, correct the switch policy configuration on either of the switches using the authUtil
command, and then enable the port on the neighboring switch using the portEnable command. If the
E_Port has formed, no action is required.

AUTH-1041
Message
Message Type
Severity

Port  has been disabled, because an authentication-reject was
received with code '' and explanation ''.

LOG
ERROR

Probable Cause

Indicates that the specified port has been disabled because it received an authentication-reject response
from the connected switch or device. The error may indicate that an invalid entity tried to connect to the
switch.

Recommended
Action

Check the connection port for a possible security attack.
Check the shared secrets using the secAuthSecret command and reinitialize authentication using the
portDisable and portEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1042
Message
Message Type
Severity
Probable Cause

156

Port  has been disabled, because authentication failed with code
'' and explanation ''.

LOG
ERROR
Indicates that the specified port has been disabled because the connecting switch or device failed to
authenticate. The error may indicate that an invalid entity attempted to connect to the switch.

Fabric OS Message Reference
53-1002749-01

AUTH-1043

Recommended
Action

5

Check the connection port for a possible security attack.
Check the shared secrets using the secAuthSecret command and reinitialize authentication using the
portDisable and portEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1043
Message
Message Type
Severity

Failed to enforce device authentication mode:(error: ).

LOG
ERROR

Probable Cause

Indicates that the Kernel mode setting for F_Port authentication failed. Device authentication will be
defaulted to OFF, and the switch will not participate in Diffie Hellman - Challenge Handshake
Authentication Protocol (DH-CHAP) authentication with other devices.

Recommended
Action

Set the device authentication policy manually using the authUtil command.

AUTH-1044
Message
Message Type
Severity

Authentication . Disabling the port .

LOG | FFDC
ERROR

Probable Cause

Indicates that authentication has timed out after multiple retries. The specified port has been disabled as
a result. This problem may be transient due to the system CPU load. In addition, a defective small
form-factor pluggable (SFP) transceiver or faulty cable may have caused the failure.

Recommended
Action

Check the SFP transceiver and the cable; then enable the port using the portEnable command.

AUTH-1045
Message
Message Type
Class
Severity
Probable Cause

Certificate not present in this switch in  port .

AUDIT | LOG
SECURITY
ERROR
Indicates that the public key infrastructure (PKI) certificate is not installed in this switch.

Fabric OS Message Reference
53-1002749-01

157

5

AUTH-1046

Recommended
Action

Check the certificate availability using the secCertUtil show -fcapall command.
Install the certificate and reinitialize authentication using the portDisable and portEnable commands or
the switchDisable and switchEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-1046
Message
Message Type
Class
Severity

 has been successfully completed.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the certificate database operation has been updated using the secAuthCertificate
command. The values for Operation type can be "set" or "remove".

Recommended
Action

No action is required.

AUTH-1047
Message
Message Type
Class
Severity

 has failed.

AUDIT | LOG
SECURITY
ERROR

Probable Cause

Indicates that the specified action has failed to update the certificate database using the
secAuthCertificate command. The values for Operation type can be "set" or "remove".

Recommended
Action

Execute the secAuthCertificate command again.

158

If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

Fabric OS Message Reference
53-1002749-01

AUTH-3001

5

AUTH-3001
Message
Message Type
Class
Severity

Event: , Status: success, Info:  type has been changed from
[] to [].

AUDIT
SECURITY
INFO

Probable Cause

Indicates that an authentication configuration value was set to a specified value. The Data type can be
authentication type, DH group type, hash type, or policy type.

Recommended
Action

No action is required.

AUTH-3002
Message
Message Type
Class
Severity

Event: , Status: success, Info: .

AUDIT
SECURITY
INFO

Probable Cause

Indicates that the secret database operation has been updated using the secAuthSecret command.

Recommended
Action

No action is required.

AUTH-3003
Message
Message Type
Class
Severity

Event: , Status: success, Info:  the PKI objects.

AUDIT
SECURITY
INFO

Probable Cause

Indicates that the public key infrastructure (PKI) objects were created using the secCertUtil command or
that the PKI objects were removed using the secCertUtil delete -fcapall command. Operation type can
be either "Created" or "Removed".

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

159

5

AUTH-3004

AUTH-3004
Message
Message Type
Class
Severity

Event: , Status: failed, Info: Neighboring switch has a conflicting
authentication policy; Port  disabled.

AUDIT
SECURITY
INFO

Probable Cause

Indicates that the specified E_Port was disabled because the neighboring switch rejected the
authentication negotiation, and the local switch has a strict switch authentication policy.

Recommended
Action

Correct the switch policy configuration on either of the switches using the authUtil command, and then
enable the port using the portEnable command.

AUTH-3005
Message
Message Type
Class
Severity

Event: , Status: failed, Info: Rejecting authentication request on
port  because switch policy is turned OFF.

AUDIT
SECURITY
INFO

Probable Cause

Indicates that the local switch has rejected the authentication request, because the switch policy is
turned off. If the neighboring switch has a strict (ON) switch policy, the port will be disabled due to
conflicting configuration settings. Otherwise, the E_Port will form without authentication.

Recommended
Action

If the specified port is disabled, correct the switch policy configuration on either of the switches using the
authUtil command, and then enable the port on the neighboring switch using the portEnable command.
If the E_Port formed, no action is required.

AUTH-3006
Message
Message Type
Class
Severity
Probable Cause

Event: , Status: failed, Info: Authentication failed on port  due to mismatch of DH-CHAP shared secrets.

AUDIT
SECURITY
INFO
Indicates that a Diffie Hellman - Challenge Handshake Authentication Protocol (DH-CHAP)
authentication operation failed on the specified port due to mismatched response values between two
entities.
The error may indicate that an invalid entity tried to connect to the switch.

160

Fabric OS Message Reference
53-1002749-01

AUTH-3007

Recommended
Action

5

Check the connection port for a possible security attack.
Check the shared secrets using the secAuthSecret command and reinitialize authentication using the
portDisable and portEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-3007
Message

Message Type
Class
Severity
Probable Cause

Event: , Status: failed, Info: Port  disabled due to
receiving an authentication reject with code '' and Explanation
''.

AUDIT
SECURITY
INFO
Indicates that the specified port was disabled because it received an authentication-reject response from
the connected switch or device.
The error may indicate that an invalid entity tried to connect to the switch.

Recommended
Action

Check the connection port for a possible security attack.
Check the shared secrets using the secAuthSecret command and reinitialize authentication using the
portDisable and portEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

AUTH-3008
Message

Message Type
Class
Severity
Probable Cause

Event: , Status: failed, Info: Port  has been disabled
due to authentication failure with code '' and explanation
''.

AUDIT
SECURITY
INFO
Indicates that the specified port has been disabled because the connecting switch or device failed to
authenticate.
The error may indicate that an invalid entity tried to connect to the switch.

Recommended
Action

Check the connection port for a possible security attack.
Check the shared secrets using the secAuthSecret command and reinitialize authentication using the
portDisable and portEnable commands.
If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

Fabric OS Message Reference
53-1002749-01

161

5

BKSW-1003

BKSW Messages
BKSW-1003
Message
Message Type
Severity
Probable Cause

kSWD: .

FFDC | LOG
WARNING
Indicates a warning state within the system.
A critical application error was reported in the watchdog subsystem. This message is used to convey
information regarding the state of the system. The switch will reboot (on single-CP switches) or fail over
(on dual-CP switches).
The Warning message variable will be one of the following:

Recommended
Action

162

•

Detected unexpected termination of: daemon name - One of the critical daemons ended
unexpectedly.

•

daemon name failed to refresh SWD*** Sending SIGABRT to PID process id number - One of the
critical daemons is found to be nonresponsive; sending signal abort (SIGABRT).

Execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the
supportSave command and contact your switch service provider.

Fabric OS Message Reference
53-1002749-01

BL-1000

5

BL Messages
BL-1000
Message

Initializing ports...

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the switch has started initializing the ports.

Recommended
Action

No action is required.

BL-1001
Message

Port initialization completed.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the switch has completed initializing the ports.

Recommended
Action

No action is required.

BL-1002
Message
Message Type
Severity

Init Failed: slot  DISABLED because internal ports were not ONLINE,
.

FFDC | LOG
CRITICAL

Probable Cause

Indicates that the blade initiation failed because one or more of the internal ports was not online. The
blade is faulted.

Recommended
Action

Make sure that the blade is seated correctly.
If the blade is seated correctly, execute the diagPost command to make sure that Power-On Self-Test
(POST) is enabled; then power cycle the blade using the slotPowerOff and slotPowerOn commands or
have the blade's ejector switch cycled to run POST and verify that the blade does not have any hardware
problems.
Additional blade fault messages precede and follow this error, providing more information. Refer to other
error messages for recommended action.
If the message persists, replace the blade.

Fabric OS Message Reference
53-1002749-01

163

5

BL-1003

BL-1003
Message
Message Type
Severity

Faulting blade in slot .

FFDC | LOG
CRITICAL

Probable Cause

Indicates a faulty blade in the specified slot.

Recommended
Action

Make sure that the blade is seated correctly.
If the blade is seated correctly, execute the diagPost command to make sure that Power-On Self-Test
(POST) is enabled; then power cycle the blade using the slotPowerOff and slotPowerOn commands or
have the blade's ejector switch cycled to run POST and verify that the blade does not have any hardware
problems.
If the message persists, replace the blade.

BL-1004
Message
Message Type
Severity

Suppressing blade fault in slot .

FFDC | LOG
CRITICAL

Probable Cause

Indicates that the specified blade experienced a failure but was not faulted due to a user setting.

Recommended
Action

Execute the diagPost command to make sure that Power-On Self-Test (POST) is enabled; then power
cycle the blade using the slotPowerOff and slotPowerOn commands or have the blade's ejector switch
cycled to run POST and verify that the blade does not have any hardware problems.
If the message persists, replace the blade.

BL-1006
Message

Blade  NOT faulted. Peer blade  experienced abrupt
failure.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the errors (mostly synchronization errors) on the specified blade are harmless. Probably,
the standby control processor (CP) blade connected to the active CP blade has experienced transitory
problems.

Recommended
Action

Execute the haShow command to verify that the standby CP is healthy. If the problem persists, remove
and reinstall the faulty blade.
If the standby CP was removed or faulted by user intervention, no action is required.

164

Fabric OS Message Reference
53-1002749-01

BL-1007

5

BL-1007
Message

Message Type
Severity

blade #: blade state is inconsistent with EM. bl_cflags 0x, slot_on , slot_off , faulty , status .

LOG
WARNING

Probable Cause

Indicates that a failover occurred while a blade was initializing on the previously active control processor
(CP).

Recommended
Action

No action is required. The blade is reinitialized. Because reinitializing a blade is a disruptive operation
and can stop I/O traffic, you may need to stop and restart the traffic during this process.

BL-1008
Message
Message Type
Severity

Slot  control-plane failure. Expected value: 0x, Actual:
0x.

FFDC | LOG
CRITICAL

Probable Cause

Indicates that the blade has experienced a hardware failure or was removed without following the
recommended removal procedure.

Recommended
Action

Make sure that the blade is seated correctly.
If the blade is seated correctly, execute the diagPost command to make sure that Power-On Self-Test
(POST) is enabled; then power cycle the blade using the slotPowerOff and slotPowerOn commands or
have the blade's ejector switch cycled to run POST and verify that the blade does not have any hardware
problems.
If the message persists, replace the blade.

BL-1009
Message
Message Type
Severity
Probable Cause

Blade in slot  timed out initializing the chips.

FFDC | LOG
CRITICAL
Indicates that the blade has failed to initialize the application-specific integrated circuit (ASIC) chips.

Fabric OS Message Reference
53-1002749-01

165

5

BL-1010

Recommended
Action

Make sure that the blade is seated correctly.
If the blade is seated correctly, execute the diagPost command to make sure that Power-On Self-Test
(POST) is enabled; then power cycle the blade using the slotPowerOff and slotPowerOn commands or
have the blade's ejector switch cycled to run POST and verify that the blade does not have any hardware
problems.
If the message persists, replace the blade.

BL-1010
Message
Message Type
Severity

Blade in slot  inconsistent with the hardware settings.

LOG
WARNING

Probable Cause

Indicates that a failover occurred while some hardware changes (such as changing the domain ID) were
being made on the previously active control processor (CP).

Recommended
Action

No action is required. This blade has been reinitialized. Because reinitializing a blade is a disruptive
operation and can stop I/O traffic, you may need to stop and restart the traffic during this process.

BL-1011
Message
Message Type
Severity

Busy with emb-port int. for chip  in minis  on blade
, chip int. is disabled. interrupt status=0x.

FFDC | LOG
CRITICAL

Probable Cause

Indicates that too many interrupts in the embedded port caused the specified chip to be disabled. The
probable cause is too many abnormal frames; the chip is disabled to prevent the control processor (CP)
from becoming too busy.

Recommended
Action

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 the
specified port.
On a bladed switch, execute the diagPost command to make sure that Power-On Self-Test (POST) is
enabled; then power cycle the blade using the slotPowerOff and slotPowerOn commands or have the
blade's ejector switch cycled to run POST and verify that the blade does not have any hardware
problems.
On a non-bladed switch, reboot or power cycle the switch.
If the message persists, replace the blade or the (non-bladed) switch.

166

Fabric OS Message Reference
53-1002749-01

BL-1012

5

BL-1012
Message
Message Type
Severity

bport  port int. is disabled. status=0x Port  will be re-enabled in 1 minute.

LOG
ERROR

Probable Cause

Indicates that the port generated an excessive number of interrupts that may prove unrecoverable to the
switch operation. The port is disabled to prevent the control processor (CP) from becoming too busy. The
bport is the blade port; this number may not correspond to a user port number.

Recommended
Action

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 the
specified port.
On a bladed switch, run the slotPowerOff and slotPowerOn commands to power cycle the blade.
On a non-bladed switch, reboot or power cycle the switch.
If the message persists, replace the blade or the (non-bladed) switch.

BL-1013
Message
Message Type
Severity

bport  port is faulted. status=0x Port  will be re-enabled in 1 minute.

LOG
ERROR

Probable Cause

Indicates that the port generated an excessive number of interrupts that may prove fatal to the switch
operation. The port is disabled to prevent the control processor (CP) from becoming too busy. The bport
number displayed in the message is the blade port; this number may not correspond to a user port
number.

Recommended
Action

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 the
specified port.
On a bladed switch, run the slotPowerOff and slotPowerOn commands to power cycle the blade.
On a non-bladed switch, reboot or power cycle the switch.
If the message persists, replace the blade.

Fabric OS Message Reference
53-1002749-01

167

5

BL-1014

BL-1014
Message
Message Type
Severity

bport  port int. is disabled. status=0x.

LOG
ERROR

Probable Cause

Indicates that the port generated an excessive number of interrupts that may prove fatal to the switch
operation. The port is disabled to prevent the control processor (CP) from becoming too busy. The bport
number displayed in the message is the blade port; this number may not correspond to a user port
number.

Recommended
Action

Make sure to capture the console output during this process.
On a bladed switch, execute the diagPost command to make sure that Power-On Self-Test (POST) is
enabled; then power cycle the blade using the slotPowerOff and slotPowerOn commands or have the
blade's ejector switch cycled to run POST and verify that the blade does not have any hardware
problems.
On a non-bladed switch, execute the reboot command to restart the switch.
If there is a hardware error, the slotPowerOff or slotPowerOn fails on the bladed switch, or errors are
encountered again, replace the blade or the (non-bladed) switch.

BL-1015
Message
Message Type
Severity

bport  port is faulted. status=0x.

LOG
ERROR

Probable Cause

Indicates that the port generated an excessive number of interrupts that may prove fatal to the switch
operation. The port is disabled to prevent the control processor (CP) from becoming too busy. The bport
number displayed in the message is the blade port; this number may not correspond to a user port
number.

Recommended
Action

Make sure to capture the console output during this process.
On a bladed switch, execute the diagPost command to make sure that Power-On Self-Test (POST) is
enabled; then power cycle the blade using the slotPowerOff and slotPowerOn commands or have the
blade's ejector switch cycled to run POST and verify that the blade does not have any hardware
problems.
On a non-bladed switch, execute the reboot command to restart the switch.
If there is a hardware error, the slotPowerOff or slotPowerOn fails on the bladed switch, or errors are
encountered again, replace the blade or the (non-bladed) switch.

168

Fabric OS Message Reference
53-1002749-01

BL-1016

5

BL-1016
Message
Message Type
Severity

Blade port  in slot  failed to enable.

FFDC | LOG
CRITICAL

Probable Cause

Indicates that the specified blade port could not be enabled.

Recommended
Action

Make sure that the blade is seated correctly.
If the blade is seated correctly, execute the diagPost command to make sure that Power-On Self-Test
(POST) is enabled; then power cycle the blade using the slotPowerOff and slotPowerOn commands or
have the blade's ejector switch cycled to run POST and verify that the blade does not have any hardware
problems.
If the message persists, replace the blade.

BL-1017
Message

Slot  Initializing...

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the slot has started initializing the ports.

Recommended
Action

No action is required.

BL-1018
Message

Slot  Initialization completed.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the slot has completed initializing the ports.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

169

5

BL-1019

BL-1019
Message

Slot , retry , internal port retry initialization,
.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the slot had internal ports that are not online. Initiated a retry on ports that failed to go
online.

Recommended
Action

No action is required.

BL-1020
Message
Message Type
Severity

Switch timed out initializing the chips.

LOG | FFDC
CRITICAL

Probable Cause

Indicates that the switch has failed to initialize the application-specific integrated circuit (ASIC) chips.

Recommended
Action

Reboot or power cycle the switch. If the message persists, replace the switch.

BL-1021
Message

Retry , internal port retry initialization, .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the switch had internal ports that are not online. Initiated a retry on ports that failed to go
online.

Recommended
Action

No action is required.

170

Fabric OS Message Reference
53-1002749-01

BL-1022

5

BL-1022
Message
Message Type
Severity

Init Failed: Switch DISABLED because internal ports were not ONLINE, .

LOG
CRITICAL

Probable Cause

Indicates that the switch initiation failed because one or more of the internal ports was not online. The
switch is faulted.

Recommended
Action

Reboot or power cycle the switch.
Additional fault messages precede and follow this error providing more information. Refer to other error
messages for recommended action.
If the message persists, replace the switch.

BL-1023
Message
Message Type
Severity

Blade in slot  was reset before blade init completed. As a result the
blade is faulted.

LOG
CRITICAL

Probable Cause

Indicates that the blade was reset before the initialization completed.

Recommended
Action

Reboot or power cycle the blade using the slotPowerOff and slotPowerOn commands.
If the message persists, replace the blade.

BL-1024
Message

All ports on the blade in slot  will be reset as part of the firmware
upgrade.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that a recent firmware upgrade caused the blade firmware to be upgraded and resulted in the
cold upgrade. As part of the upgrade, all datapath elements were reset.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

171

5

BL-1025

BL-1025
Message

All GigE/FCIP/Virtualization/FC Fastwrite ports on the blade in slot 
will be reset as part of the firmware upgrade.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that a recent firmware upgrade caused the blade's firmware to be upgraded and resulted in the
cold upgrade. As part of the upgrade, all the Gigabit Ethernet, Fibre Channel over IP (FCIP),
virtualization data elements, and FC Fastwrite ports were reset.

Recommended
Action

No action is required.

BL-1026
Message
Message Type
Severity

Internal port offline during warm recovery, state  (0x).

LOG
CRITICAL

Probable Cause

Indicates that an internal port went offline during warm recovery of the switch. The switch will reboot and
start cold recovery.

Recommended
Action

Execute the supportSave command and then reboot switch. If the problem persists, replace the switch.

BL-1027
Message
Message Type
Severity

Blade in slot  faulted, boot failed; status 0x 0x<1250 0
boot status> 0x<1250 1 boot status>.

LOG
CRITICAL

Probable Cause

Indicates that the blade failed to boot properly.

Recommended
Action

Reboot or power cycle the blade using the slotPowerOff and slotPowerOn commands.

172

If the message persists, replace the blade.

Fabric OS Message Reference
53-1002749-01

BL-1028

5

BL-1028
Message
Message Type
Severity

Switch faulted; internal processor was reset before switch init completed.

LOG
CRITICAL

Probable Cause

Indicates that the switch internal processor was reset before the initialization completed.

Recommended
Action

Reboot or power cycle the switch using the slotPowerOff and slotPowerOn commands.
If the message persists, replace the switch.

BL-1029
Message

All ports on the switch will be reset as part of the firmware upgrade.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that a recent firmware upgrade caused the switch internal processor firmware to be upgraded
and resulted in a cold upgrade. As part of the upgrade, all the datapath elements were reset.

Recommended
Action

No action is required.

BL-1030
Message

All GigE/FCIP/Virtualization/FC Fastwrite ports on the switch will be reset as
part of the firmware upgrade.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that a recent firmware upgrade caused the switch internal processor firmware to be upgraded
and resulted in the cold upgrade. As part of the upgrade, all Gigabit Ethernet, Fibre Channel over IP
(FCIP), virtualization data elements, and FC Fastwrite ports were reset.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

173

5

BL-1031

BL-1031
Message
Message Type
Severity

Link timeout in internal port (slot , port ) resulted in
blade fault. Use slotpoweroff/slotpoweron to recover the blade.

LOG
CRITICAL

Probable Cause

Indicates that link timeout occurred in one of the back-end internal ports.

Recommended
Action

Power cycle the blade using the slotPowerOff and slotPowerOn commands.

BL-1032
Message

Message Type
Severity

(slot ,bitmap 0x) ports never came up
ONLINE (reason , state ). Disabling
slot.

LOG
CRITICAL

Probable Cause

Indicates that back-end (non-user) ports have not come online within the time limit.

Recommended
Action

Execute the diagPost command to make sure that Power-On Self-Test (POST) is enabled; then power
cycle the blade using the slotPowerOff and slotPowerOn commands or have the blade's ejector switch
cycled to run POST and verify that the blade does not have any hardware problems.
If the message persists, replace the blade.

BL-1033
Message
Message Type
Severity

(slot ,bitmap 0x) No disable
acknowledgment from ports (state ). Disabling slot.

LOG
CRITICAL

Probable Cause

Indicates that the system has timed out waiting for the disable messages from the user ports after
disabling the ports.

Recommended
Action

Execute the diagPost command to make sure that Power-On Self-Test (POST) is enabled; then power
cycle the blade using the slotPowerOff and slotPowerOn commands or have the blade's ejector switch
cycled to run POST and verify that the blade does not have any hardware problems.
If the message persists, replace the blade.

174

Fabric OS Message Reference
53-1002749-01

BL-1034

5

BL-1034
Message

Slot  FC Initialization completed.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the slot has completed initializing the Fibre Channel (FC) ports.

Recommended
Action

No action is required.

BL-1035
Message

Slot  iSCSI port  Initialization completed.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the slot has completed initializing the specified iSCSI port.

Recommended
Action

No action is required.

BL-1036
Message
Message Type
Severity

Faulting 8G blade in slot =  due to incompatible stag mode. All
EX/VEX ports must be disabled in order to enable the 8G blade in the chassis.

LOG
CRITICAL

Probable Cause

Indicates that the 8 Gbps blade with legacy mode (EX_port having stag) will be disabled.

Recommended
Action

Disable all EX_Ports and VEX_Ports and execute the slotPowerOff or slotPowerOn commands on the
8 Gbps blade. All EX_Ports and VEX_Ports can be re-enabled.

Fabric OS Message Reference
53-1002749-01

175

5

BL-1037

BL-1037
Message
Message Type
Severity

Faulting chip in slot = , miniS = ,port = 
due to BE/BI port fault.

LOG
CRITICAL

Probable Cause

Indicates that all ports on the chip have been disabled due to a fault on the chip.

Recommended
Action

Make sure that the blade is seated correctly.
If the blade is seated correctly, execute the diagPost command to make sure that Power-On Self-Test
(POST) is enabled; then power cycle the blade using the slotPowerOff and slotPowerOn commands or
have the blade's ejector switch cycled to run POST and verify that the blade does not have any hardware
problems.
Additional blade fault messages precede and follow this error, providing more information. Refer to other
error messages for recommended action.
If the message persists, replace the blade.

BL-1038
Message
Message Type
Severity

Inconsistent FPGA image version detected, please reboot the switch for recovery.

LOG
CRITICAL

Probable Cause

Indicates that the field-programmable gate array (FPGA) image version is incompatible with the software
version.

Recommended
Action

Reboot the switch. If the message persists, replace the switch.

BL-1039
Message
Message Type
Severity

Inconsistent FPGA image version detected, faulting the blade in slot .

LOG
CRITICAL

Probable Cause

Indicates that the field-programmable gate array (FPGA) image version is incompatible with the software
version.

Recommended
Action

Power cycle the blade using the slotPowerOff and slotPowerOn commands.

176

If the message persists, replace the blade.

Fabric OS Message Reference
53-1002749-01

BL-1041

5

BL-1041
Message

Message Type
Severity

Dynamic area mode is enabled on default switch, Faulting the blade w/ ID  in slot  as
it does not support this mode.

LOG
CRITICAL

Probable Cause

Indicates that the blade does not support dynamic area mode on the default switch.

Recommended
Action

Turn off the dynamic area mode using the configure command.

BL-1045
Message

Message Type
Severity

mini SFP+ (SN: ) is only supported in certain high port
count blades, not blade in slot  w/
ID .

LOG
ERROR

Probable Cause

Indicates that mini-SFP+ is supported only by a certain type of blade (FC8-64), but it can be inserted in
other blades.

Recommended
Action

Replace the mini-SFP+ with an SFP or SFP+.

BL-1046
Message

Message Type
Severity

 error on SFP in Slot /Port  (). Try
reseating or replacing it.

LOG
ERROR

Probable Cause

Indicates that the checksum in an area on the small form-factor pluggable (SFP) transceiver does not
match with the computed value, or there is problem accessing the data.

Recommended
Action

Reseat the SFP transceiver. If problem persists, replace the SFP transceiver.

Fabric OS Message Reference
53-1002749-01

177

5

BL-1047

BL-1047
Message

Buffer optimized mode is turned  for slot .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the buffer optimized mode is changed for the specified slot.

Recommended
Action

No action is required.

BL-1048
Message
Message Type
Severity

FCoE Blade in slot  failed because the Interop mode is enabled on the
switch.

LOG
WARNING

Probable Cause

Indicates that the interop mode is turned on in the default switch while powering on the FCoE blade.

Recommended
Action

Disable the interop mode using the interopmode command; then execute the slotPowerOff and
slotPowerOn commands on the FCoE blade.

BL-1049
Message

Serdestunemode: .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the SerDes tuning mode is changed for the slot.

Recommended
Action

No action is required.

178

Fabric OS Message Reference
53-1002749-01

BL-1050

5

BL-1050
Message
Message Type
Severity

Incompatible Blade Processor FPGA version with FOS7.0 firmware in slot= on FX8-24. Contact support for upgrade instructions.

LOG
WARNING

Probable Cause

Indicates that the blade processor field-programmable gate array (FPGA) version with Fabric OS v7.0.0
is incompatible on the FX8-24 blade.

Recommended
Action

Contact your switch service provider for upgrade instructions.

BL-1051
Message
Message Type
Severity

Incompatible Blade Processor FPGA version with FOS7.0 firmware on 7800. Contact
support for upgrade instructions.

LOG
WARNING

Probable Cause

Indicates that the blade processor field-programmable gate array (FPGA) version with Fabric OS v7.0.0
is incompatible on the Brocade 7800 switch.

Recommended
Action

Contact your switch service provider for upgrade instructions.

BL-1052
Message

Message Type
Severity

Link Reset threshold exceeded in the internal port (slot , port ). No core blade has been faulted because it has only one active core
blade.

LOG
WARNING

Probable Cause

Indicates that the internal port in the core blade exceeded the link reset threshold level. Faulting the peer
edge blade because there is only one active core blade.

Recommended
Action

Replace the core blade.

Fabric OS Message Reference
53-1002749-01

179

5

BLS-1000

BLS Messages
BLS-1000
Message

Message Type
Severity

 of GE  failed. Please retry the command. Data:
inst= st= rsn= fn= oid=.

LOG | FFDC
ERROR

Probable Cause

Indicates that the hardware is not responding to a command request, possibly because it is busy.

Recommended
Action

Retry the command.

BLS-1001
Message
Message Type
Severity

FIPS  failed; algo= type=
slot=.

LOG | FFDC
CRITICAL

Probable Cause

Indicates that a Federal Information Protection Standard (FIPS) failure has occurred and requires faulting
the blade or switch.

Recommended
Action

Retry the command.

BLS-1002
Message
Message Type

An IPsec/IKE policy was added.

AUDIT | LOG

Class

CFG

Severity

INFO

Probable Cause

Indicates that an Internet Protocol Security (IPsec) or Internet Key Exchange (IKE) policy was added and
the configuration file was updated.

Recommended
Action

No action is required.

180

Fabric OS Message Reference
53-1002749-01

BLS-1003

5

BLS-1003
Message
Message Type

An IPsec/IKE policy was deleted.

AUDIT | LOG

Class

CFG

Severity

INFO

Probable Cause

Indicates that an Internet Protocol Security (IPsec) or Internet Key Exchange (IKE) policy was deleted
and the configuration file was updated.

Recommended
Action

No action is required.

BLS-1004
Message

Tape Read Pipelining is being disabled slot () port () tunnel ().

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the Fabric OS version on the remote end of the tunnel does not support Tape Read
Pipelining.

Recommended
Action

No action is required.

BLS-1005
Message

Message Type
Severity

S,P() [OID 0x]: : port faulted due to SFP validation failure. Please check if the SFP is
valid for the configuration.

LOG
ERROR

Probable Cause

Indicates a deteriorated small form-factor pluggable (SFP) transceiver, an incompatible SFP transceiver
pair, or a faulty cable between the peer ports.

Recommended
Action

Verify that compatible SFP transceivers are used on the peer ports, the SFP transceivers have not
deteriorated, and the Fibre Channel cable is not faulty. Replace the SFP transceivers or the cable if
necessary.

Fabric OS Message Reference
53-1002749-01

181

5

BM-1001

BM Messages
BM-1001
Message
Message Type
Severity
Probable Cause

BM protocol version  in slot .

LOG
ERROR
Indicates that the firmware running on the control processor (CP) cannot communicate with the
application processor (AP) blade in the indicated slot and determine the AP blade's firmware version.
The reason can be one of the following:

•
•
Recommended
Action

The CP blade is running a later version of firmware than the AP blade.
The CP blade is running an earlier version of firmware than the AP blade.

The problem can be corrected by changing the firmware version on either the CP or on the AP blade.
You can modify the firmware version on the CP blade by using the firmwareDownload command. Refer
to the release notes to determine whether a non-disruptive firmware download is supported between the
revisions. Because the AP and CP blades cannot communicate, it is not possible to load new firmware
on the AP blade. If necessary, send the AP blade back to the factory for a firmware update.

BM-1002
Message

Connection established between CP and blade in slot .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the control processor (CP) has established a connection to the blade processor (BP) and
can communicate.

Recommended
Action

No action is required.

BM-1003
Message
Message Type
Severity
Probable Cause

182

Failed to establish connection between CP and blade in slot .
Faulting blade.

LOG | FFDC
WARNING
Indicates that the control processor (CP) could not establish a connection to the blade processor (BP) to
communicate.

Fabric OS Message Reference
53-1002749-01

BM-1004

Recommended
Action

5

Execute the slotPowerOff and slotPowerOn commands or reseat the affected blade.

BM-1004
Message

Blade firmware  on slot  is not consistent with system
firmware . Auto-leveling blade firmware to match system firmware.

Message Type

LOG

Severity

INFO

Probable Cause

Recommended
Action

Indicates that the policy of the specified blade is to auto-level the blade firmware to the system firmware.
This may be due to one of the following reasons:

•

Blade firmware was detected to be different from the control processor (CP) firmware due to a
firmware upgrade.

•

The blade was recently inserted and had a different version of the firmware loaded.

No action is required. The blade will automatically download the updated firmware.

BM-1005
Message
Message Type
Severity

Firmwaredownload timed-out for blade in slot . Faulting blade.

LOG
WARNING

Probable Cause

Indicates that the firmwareDownload command failed for the blade in the specified slot.

Recommended
Action

Execute the slotPowerOff and slotPowerOn commands or reseat the affected blade.

BM-1006
Message

Blade is not configured. Persistently disabling all ports for blade in slot .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the policy of the specified blade is set to persistently disable all ports the first time the blade
is detected. The message indicates either of the following:

•
•

The blade was detected in this slot for the first time.
The blade was configured under a different mode.

Fabric OS Message Reference
53-1002749-01

183

5

BM-1007

Recommended
Action

Configure the blade so that it will persistently enable the ports.

BM-1007
Message

If set, clear EX/VEX/FC Fastwrite configuration for all ports for blade in slot
.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates the specified blade was detected for the first time after an FR4-18i was previously configured in
the same slot. The new blade requires the specified port configurations to be cleared.

Recommended
Action

No action is required. The blade ports are cleared automatically.

BM-1008
Message
Message Type
Severity

Download of blade firmware failed for blade in slot . Reissue
firmwaredownload to recover.

LOG
WARNING

Probable Cause

Indicates that the automatic firmware upgrade on the blade failed because the blade firmware version
was detected to be different from the control processor (CP) firmware version.

Recommended
Action

Execute the firmwareDownload command to recover the blade.

BM-1009
Message
Message Type
Severity

Firmwaredownload timed-out for application processor. Faulting switch.

LOG
WARNING

Probable Cause

Indicates that the firmware download on the application processor (AP) blade failed.

Recommended
Action

Execute the slotPowerOff and slotPowerOn commands or reseat the affected blade.

184

Fabric OS Message Reference
53-1002749-01

BM-1010

5

BM-1010
Message

Resetting port configuration and linkcost for all ports for blade in slot .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates the specified blade was detected for the first time after an FC10-6 was previously configured in
the same slot. The new blade requires resetting the port configuration and linkcost.

Recommended
Action

No action is required. The blade ports are cleared automatically.

BM-1053
Message
Message Type
Severity

Failed to establish connection between CP and Application Processor. Faulting
switch.

LOG | FFDC
WARNING

Probable Cause

Indicates that the control processor (CP) could not establish a connection with the application processor
(AP) to communicate.

Recommended
Action

Execute the slotPowerOff and slotPowerOn commands or reseat the affected blade.

BM-1054
Message

AP firmware  is not consistent with system firmware . Auto-leveling AP firmware to match system firmware.

Message Type

LOG

Severity

INFO

Probable Cause

Recommended
Action

Indicates that the policy of the specified blade is set to auto-level the blade firmware to the system
firmware. This may be due to one of the following reasons:

•

Blade firmware was detected to be different from the control processor (CP) firmware due to a
firmware upgrade.

•

The blade was recently inserted and had a different version of the firmware loaded.

No action is required. The blade will automatically download the updated firmware.

Fabric OS Message Reference
53-1002749-01

185

5

BM-1055

BM-1055
Message
Message Type
Severity

Firmwaredownload timed-out for AP. Faulting switch.

LOG
WARNING

Probable Cause

Indicates that firmware download on the application processor (AP) blade has failed.

Recommended
Action

Execute the slotPowerOff and slotPowerOn commands or reseat the affected blade.

BM-1056
Message

AP is not configured. Persistently disabling all ports on the switch.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the policy of the specified switch is to persistently disable all ports the first time the AP is
detected. This may be caused by one of the following reasons:

•
•
Recommended
Action

The AP was detected for the first time on this switch.
The switch was configured under a different mode.

Configure the switch to persistently enable all ports.

BM-1058
Message
Message Type
Severity

Download of AP firmware failed for the switch. Reissue firmwaredownload to
recover.

LOG
WARNING

Probable Cause

Indicates that the automatic firmware upgrade on the application processor (AP) failed because the
firmware version running on the AP was detected to be different from the system firmware.

Recommended
Action

Execute the firmwareDownload command to recover the AP.

186

Fabric OS Message Reference
53-1002749-01

C2-1001

5

C2 Messages
C2-1001
Message
Message Type
Severity

Port  port faulted due to SFP validation failure. Check if the SFP is
valid for the configuration.

LOG
ERROR

Probable Cause

Indicates a deteriorated small form-factor pluggable (SFP) transceiver, an incompatible SFP transceiver
pair, or a faulty cable between the peer ports.

Recommended
Action

Verify that compatible SFP transceivers are used on the peer ports, the SFP transceivers have not
deteriorated, and the Fibre Channel cable is not faulty. Replace the SFP transceivers or the cable if
necessary.

C2-1002
Message
Message Type
Severity

Port  chip faulted due to an internal error.

LOG | FFDC
ERROR

Probable Cause

Indicates an internal error. All the ports on the blade or switch will be disrupted.

Recommended
Action

To recover a bladed system, execute the slotPowerOff and slotPowerOn commands on the blade. To
recover a non-bladed system, execute the fastBoot command on the switch.

C2-1004
Message
Message Type
Severity

S,C: Invalid DMA ch pointer, chan:,
good_addr:0x bad_addr:0x.

LOG
ERROR

Probable Cause

Indicates an internal error in the application-specific integrated circuit (ASIC) hardware that may degrade
the data traffic.

Recommended
Action

Restart the system at the next maintenance window. If the problem persists, replace the blade.

Fabric OS Message Reference
53-1002749-01

187

5

C2-1006

C2-1006
Message

Message Type
Severity
Probable Cause

S,C: Internal link errors reported, no hardware faults
identified, continuing monitoring: fault1:0x, fault2:0x
thresh1:0x.

LOG
WARNING
Indicates that some internal link errors have been detected. These errors can be normal in an active
running system.
The system automatically starts a more detailed monitoring of the errors reported in the internal
hardware. There is no action required by the user at this time. If any actual hardware failures are
detected, the C2-1010 message will be generated identifying the failing field-replaceable unit (FRU).

Recommended
Action

No action is required.

C2-1007
Message
Message Type
Severity

S,P(): best effort QoS will be turned
off at next port state change as it is not supported under this configuration

LOG
WARNING

Probable Cause

Indicates that quality of service (QoS) will be turned off automatically at the next port state change
because best effort QoS is no longer supported on 4 Gbps or 8 Gbps platform long distance ports.

Recommended
Action

No action is required.

C2-1008
Message
Message Type
Severity

S,P(): QoS overwrites
portcfglongdistance vc_translation_link_init. ARB will be used on the link.

LOG
WARNING

Probable Cause

Indicates that quality of service (QoS) has overwritten the fill word IDLE used on the long distance links.
Arbitrated loop (ARB) will be used on the link.

Recommended
Action

No action is required.

188

Fabric OS Message Reference
53-1002749-01

C2-1009

5

C2-1009
Message

Message Type
Severity

S,P(): portcfglongdistance
vc_translation_link_init = 1 overwrites fill word IDLE. ARB will be used on the
link.

LOG
WARNING

Probable Cause

Indicates that the portcfglongdistance vc_translation_link_init 1 command has overwritten the fill
word IDLE. Arbitrated loop (ARB) will be used on the link.

Recommended
Action

No action is required.

C2-1010
Message

Message Type
Severity

S,C: Internal monitoring has identified suspect
hardware, blade may need to be reset or replaced: fau1:0x,
fau2:0x th2:0x.

LOG
CRITICAL

Probable Cause

Indicates that above-normal errors were observed in hardware that may or may not impact the data
traffic.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

C2-1012
Message

Message Type
Severity

S,P(): Link Timeout on internal port
ftx= tov= (>)
vc_no= crd(s)lost= complete_loss:.

LOG | FFDC
CRITICAL

Probable Cause

Indicates that one or more credits have been lost on a back-end port, and there is no traffic on that port
for two seconds.

Recommended
Action

Turn on the back-end credit recovery to reset the link and recover the lost credits. If credit recovery has
already been turned on, the link will be reset to recover the credits and no action is required.

Fabric OS Message Reference
53-1002749-01

189

5

C2-1013

C2-1013
Message
Message Type
Severity

S,P(): Duplicate rte_tbl_select
detected.

LOG
WARNING

Probable Cause

Indicates that the selected table is corrupted.

Recommended
Action

This message must have a matching message for the other duplicate table. Reset both the specified
ports. If it is a trunk, reset the entire trunk.

C2-1014
Message
Message Type
Severity

Link Reset on Port S,P() vc_no= crd(s)lost=  trigger.

LOG
WARNING

Probable Cause

Indicates that one or more credits are lost and the link is reset.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

C2-1015
Message
Message Type
Severity

Port re-initialized due to Link Reset failure on internal Port S,P().

LOG
WARNING

Probable Cause

Indicates that the specified port is re-initialized due to link reset failure.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

190

Fabric OS Message Reference
53-1002749-01

C2-1016

5

C2-1016
Message
Message Type
Severity

Port is faulted due to port re-initialization failure on internal Port S,P() with reason .

LOG
ERROR

Probable Cause

Indicates that the specified port failed due to port re-initialization failure.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

C2-1017
Message
Message Type
Severity

Blade in Slot  failed due to unavailability of ports in the internal
trunk.

LOG
ERROR

Probable Cause

Indicates that the specified blade failed because of the unavailability of the ports in the internal trunk.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

C2-1018
Message
Message Type
Severity

Link reset threshold value exceeded in the link S,P().

LOG
ERROR

Probable Cause

Indicates that the specified blade is faulted because the link reset threshold value has exceeded.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

Fabric OS Message Reference
53-1002749-01

191

5

C2-1019

C2-1019
Message
Message Type
Severity

S,C: HW ASIC Chip TXQ FID parity error threshold reached
type = 0x.

LOG
WARNING

Probable Cause

Indicates that an internal error is observed in the application-specific integrated circuit (ASIC) hardware
that may degrade the data traffic.

Recommended
Action

Restart the system at the next maintenance window.

C2-1025
Message
Message Type
Severity

S,P(): Extra credit on
F_port:ftx= curr_cred= actual_cred=.

LOG
WARNING

Probable Cause

Indicates that the device is returning the wrong number of receiver-ready (R_RDY) frames.

Recommended
Action

When this error is observed persistently, replace the device.

C2-1026
Message

Message Type
Severity

S,P(): Faulting F_port due to extra
credit detected:ftx= curr_cred= actual_cred=.

LOG
WARNING

Probable Cause

Indicates that the device is returning the wrong number of receiver-ready (R_RDY) frames.

Recommended
Action

When this error is observed persistently, replace the device.

192

Fabric OS Message Reference
53-1002749-01

C2-1027

5

C2-1027
Message

Detected credit loss on Peer internal Port of Slot , Port () vc_no= crd(s)lost=
complete_loss:.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that credit loss was detected on the peer port.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

C2-1028
Message
Message Type
Severity

Detected excessive Link resets on the port in a second. Slot , Port
().

LOG
WARNING

Probable Cause

Indicates that the port received excessive link resets from peer port within 1 second and that exceeded
threshold.

Recommended
Action

When this error is observed persistently, change the small form-factor pluggable (SFP) transceiver or the
cable on the peer port to which this port is connected.

Fabric OS Message Reference
53-1002749-01

193

5

C3-1001

C3 Messages
C3-1001
Message
Message Type
Severity

Port  failed due to SFP validation failure. Check if the SFP is valid
for the configuration.

LOG
ERROR

Probable Cause

Indicates a deteriorated small form-factor pluggable (SFP) transceiver, an incompatible SFP transceiver
pair, or a faulty cable between the peer ports.

Recommended
Action

Verify that compatible SFP transceivers are used on the peer ports, the SFP transceivers have not
deteriorated, and the Fibre Channel cable is not faulty. Replace the SFP transceivers or the cable if
necessary.

C3-1002
Message
Message Type
Severity

Port  chip failed due to an internal error.

LOG | FFDC
ERROR

Probable Cause

Indicates an internal error. All the ports on the blade or switch will be disrupted.

Recommended
Action

To recover a bladed system, execute the slotPowerOff and slotPowerOn commands on the blade. To
recover a non-bladed system, execute the fastBoot command on the switch.

C3-1004
Message
Message Type
Severity

S,C: Invalid DMA ch pointer, chan:,
good_addr:0x bad_addr:0x.

LOG
ERROR

Probable Cause

Indicates an internal error in the application-specific integrated circuit (ASIC) hardware that may degrade
the data traffic.

Recommended
Action

Reboot the system at the next maintenance window. If the problem persists, replace the blade.

194

Fabric OS Message Reference
53-1002749-01

C3-1006

5

C3-1006
Message
Message Type
Severity

S,C: Various non-critical hardware errors were observed:
fault1:0x, fault2:0x thresh1:0x.

LOG
WARNING

Probable Cause

Indicates that some errors were found in hardware that may or may not impact the data traffic.

Recommended
Action

No action is required. Usually these errors are transient.

C3-1007
Message
Message Type
Severity

S,P(): best effort QoS will be turned
off at next port state change as it is not supported under this configuration.

LOG
WARNING

Probable Cause

Indicates that quality of service (QoS) will be turned off automatically at the next port state change
because best effort QoS is no longer supported on 4 Gbps or 8 Gbps platform long distance ports.

Recommended
Action

No action is required.

C3-1008
Message
Message Type
Severity

S,P(): QoS overwrites
portcfglongdistance vc_translation_link_init. ARB will be used on the link.

LOG
WARNING

Probable Cause

Indicates that quality of service (QoS) has overwritten the fill word IDLE used on the long distance links.
Arbitrated loop (ARB) will be used on the link.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

195

5

C3-1009

C3-1009
Message

Message Type
Severity

S,P(): portcfglongdistance
vc_translation_link_init = 1 overwrites fill word IDLE. ARB will be used on the
link.

LOG
WARNING

Probable Cause

Indicates that the portcfglongdistance vc_translation_link_init 1 command has overwritten the fill
word IDLE. Arbitrated loop (ARB) will be used on the link.

Recommended
Action

No action is required.

C3-1010
Message
Message Type
Severity

S,C: Above normal hardware errors were observed:
fault1:0x, fault2:0x thresh2:0x.

LOG
CRITICAL

Probable Cause

Indicates that above-normal errors were observed in hardware that may or may not impact the data
traffic.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

C3-1011
Message

Message Type
Severity

Detected a complete loss of credit on internal back-end VC: Slot ,
Port () vc_no= crd(s)lost=.

LOG
WARNING

Probable Cause

Indicates that all credits have been lost on the specified virtual channel (VC) and port.

Recommended
Action

Turn on the back-end credit recovery to reset the link and recover the lost credits. If credit recovery has
already been turned on, the link will be reset to recover the credits and no action is required.

196

Fabric OS Message Reference
53-1002749-01

C3-1012

5

C3-1012
Message

Message Type
Severity

S,P(): Link Timeout on internal port
ftx= tov= (>)
vc_no= crd(s)lost= complete_loss:.

LOG | FFDC
CRITICAL

Probable Cause

Indicates that one or more credits have been lost on a back-end port, and there is no traffic on that port
for two seconds.

Recommended
Action

Turn on the back-end credit recovery to reset the link and recover the lost credits. If credit recovery has
already been turned on, the link will be reset to recover the credits and no action is required.

C3-1013
Message

Message Type
Severity

Multi RDY/Frame Loss detected on Slot , Port () m_rdy(0x)/m_frame(0x).

LOG
WARNING

Probable Cause

Indicates that wait cycles to recover the lost frame or credit are exceeded on the specified port.

Recommended
Action

Turn on the back-end credit recovery to reset the link and recover the lost credits. If credit recovery has
already been turned on, the link will be reset to recover the credits and no action is required.

C3-1014
Message
Message Type
Severity

Link Reset on Port S,P() vc_no= crd(s)lost=  trigger.

LOG
WARNING

Probable Cause

Indicates that one or more credits were lost and the link is reset.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

Fabric OS Message Reference
53-1002749-01

197

5

C3-1015

C3-1015
Message
Message Type
Severity

Port re-initialized due to Link Reset failure on internal Port S,P().

LOG
WARNING

Probable Cause

Indicates that the specified port is re-initialized due to link reset failure.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

C3-1016
Message
Message Type
Severity

Port is faulted due to port re-initialization failure on internal Port S,P() with reason .

LOG
ERROR

Probable Cause

Indicates that the specified port failed due to port re-initialization failure.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

C3-1017
Message
Message Type
Severity

Blade in Slot- failed due to unavailability of ports in the internal
trunk.

LOG
ERROR

Probable Cause

Indicates that the specified blade failed because of the unavailability of the ports in the internal trunk.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

198

Fabric OS Message Reference
53-1002749-01

C3-1018

5

C3-1018
Message
Message Type
Severity

Link reset threshold value exceeded in the link S,P().

LOG
ERROR

Probable Cause

Indicates that the specified blade is faulted because the link reset threshold value has exceeded.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

C3-1019
Message
Message Type
Severity

S,C: HW ASIC Chip TXQ FID parity error threshold reached
type = 0x.

LOG
WARNING

Probable Cause

Indicates that an internal error is observed in the application-specific integrated circuit (ASIC) hardware
that may degrade the data traffic.

Recommended
Action

Restart the system at the next maintenance window.

C3-1020
Message

Message Type
Severity

S,P(): Some non-critical CRC with
good EOF errors were observed: current:0x,
last:0x thresh1:0x.

LOG
WARNING

Probable Cause

Indicates that some non-critical errors were detected in the hardware.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

199

5

C3-1021

C3-1021
Message
Message Type
Severity

S,P(): Port is offline due to
Encryption Compression Block error.

LOG
WARNING

Probable Cause

Indicates that an internal error is observed in the application-specific integrated circuit (ASIC) hardware
that may degrade the data traffic.

Recommended
Action

When this error occurs, the software will automatically recover from the error and no action is required.
However, if the problem persists, replace the blade.

C3-1023
Message
Message Type
Severity

Single RDY/Frame Loss detected and recovered on Slot ,Port () rdy(0x)/frame(0x).

LOG
WARNING

Probable Cause

Indicates that above-normal errors are observed in hardware that may or may not impact the data traffic.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

C3-1025
Message
Message Type
Severity

S,P(): Extra credit on
F_port:ftx= curr_cred= actual_cred=.

LOG
WARNING

Probable Cause

Indicates that the device is returning the wrong number of receiver-ready (R_RDY) frames.

Recommended
Action

When this error is observed persistently, replace the device.

200

Fabric OS Message Reference
53-1002749-01

C3-1026

5

C3-1026
Message

Message Type
Severity

S,P(): Faulting F_port due to extra
credit detected:ftx= curr_cred= actual_cred=.

LOG
WARNING

Probable Cause

Indicates that the device is returning the wrong number of receiver-ready (R_RDY) frames.

Recommended
Action

When this error is observed persistently, replace the device.

C3-1027
Message

Detected credit loss on Peer internal Port of Slot , Port () vc_no= crd(s)lost=
complete_loss:.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that credit loss was detected on the peer port.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

C3-1028
Message
Message Type
Severity

Detected excessive Link resets on the port in a second. Slot , Port
().

LOG
WARNING

Probable Cause

Indicates that the port received excessive link resets from peer port within 1 second and that exceeded
the threshold.

Recommended
Action

When this error is observed persistently, change the small form-factor pluggable (SFP) transceiver or the
cable on the peer port to which this port is connected.

Fabric OS Message Reference
53-1002749-01

201

5

CAL-1001

CAL Messages
CAL-1001
Message

Switch offline requested by remote domain .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the specified remote domain requested the local domain to be disabled.

Recommended
Action

Check the error message log on the remote domain using the errShow command to find the reason.

202

Fabric OS Message Reference
53-1002749-01

CCFG-1001

5

CCFG Messages
CCFG-1001
Message
Message Type
Severity

Failed to initialize , rc = .

LOG
ERROR

Probable Cause

Indicates that the initialization of a module within the Converged Enhanced Ethernet (CEE) configuration
management daemon has failed.

Recommended
Action

Download a new firmware version using the firmwareDownload command.

CCFG-1002
Message
Message Type

Started loading CEE system configuration.

AUDIT | LOG

Class

CFG

Severity

INFO

Probable Cause

Indicates that the Converged Enhanced Ethernet (CEE) system configuration has started loading.

Recommended
Action

No action is required.

CCFG-1003
Message
Message Type

System is ready to accept CEE user commands.

AUDIT | LOG

Class

CFG

Severity

INFO

Probable Cause

Indicates that the Converged Enhanced Ethernet (CEE) shell is ready to accept configuration
commands.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

203

5

CCFG-1004

CCFG-1004
Message
Message Type
Severity

Configuration replay failed due to missing system startup configuration file.

LOG
ERROR

Probable Cause

Indicates that the startup configuration file has been moved or deleted and therefore replaying the
system configuration has failed.

Recommended
Action

Execute the copy file startup-config command to restore the startup configuration file from any backup
retrieved on the server.

CCFG-1005
Message

Startup configuration file is updated.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the startup configuration file has been updated.

Recommended
Action

No action is required.

CCFG-1006
Message

Current system running configuration file is updated.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the current running configuration file has been updated.

Recommended
Action

No action is required.

CCFG-1007
Message

Startup configuration is deleted.

Message Type

LOG

Severity

INFO

Probable Cause

204

Indicates that the startup configuration file has been moved or deleted.

Fabric OS Message Reference
53-1002749-01

CCFG-1008

Recommended
Action

5

No action is required.

CCFG-1008
Message
Message Type
Severity

CMSH init failed: .

LOG
ERROR

Probable Cause

Indicates that the CEE Management Shell (CMSH) initialization has failed.

Recommended
Action

No action is required.

CCFG-1009
Message

Successfully copied to .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that a configuration file has been copied to the specified destination.

Recommended
Action

No action is required.

CCFG-1010
Message

Current system running configuration file is updated partially.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the current running configuration file has been updated partially.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

205

5

CCFG-1011

CCFG-1011
Message

Linecard configuration mismatch on slot .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the inserted line card is different from the pre-configured line card on the specified slot.

Recommended
Action

Execute the no linecard command to remove the line card configuration.

CCFG-1012
Message
Message Type
Severity

Blade in slot  failed to reach ONLINE state within  seconds after
receiving system ready.

LOG
ERROR

Probable Cause

Indicates that the blade in the specified slot has failed to come online within the specified timeout interval
after receiving the system ready event.

Recommended
Action

Execute the slotPowerOff and slotPowerOn commands on the specified slot to bring the blade online.

CCFG-1013
Message
Message Type

.

AUDIT

Class

CFG

Severity

INFO

Probable Cause

Indicates that the switch state has changed.

Recommended
Action

No action is required.

206

Fabric OS Message Reference
53-1002749-01

CDR-1001

5

CDR Messages
CDR-1001
Message
Message Type
Severity

Port  port fault. Change the SFP or check cable.

LOG
ERROR

Probable Cause

Indicates a deteriorated small form-factor pluggable (SFP) transceiver, an incompatible SFP transceiver
pair, a faulty cable between the peer ports, or the port speed configuration does not match the capability
of the SFP transceiver.

Recommended
Action

Verify that compatible SFP transceivers are used on the peer ports, the SFP transceivers have not
deteriorated, and the Fibre Channel cable is not faulty. Replace the SFP transceivers or the cable if
necessary.

CDR-1002
Message
Message Type
Severity

Port  chip faulted due to internal error.

LOG | FFDC
ERROR

Probable Cause

Indicates an internal error. All the ports on the blade or switch will be disrupted.

Recommended
Action

To recover a bladed system, execute the slotPowerOff and slotPowerOn commands on the blade. To
recover a non-bladed system, execute the fastBoot command on the switch.

CDR-1003
Message
Message Type
Severity

S,C: HW ASIC Chip error type = 0x. If
the problem persists, blade may need to be reset or replaced.

LOG
WARNING

Probable Cause

Indicates an internal error in the application-specific integrated circuit (ASIC) hardware that may degrade
the data traffic.

Recommended
Action

Restart the system at the next maintenance window. If the problem persists, replace the blade.

Fabric OS Message Reference
53-1002749-01

207

5

CDR-1004

CDR-1004
Message
Message Type
Severity

S,C: Invalid DMA ch pointer, chan:,
good_addr:0x bad_addr:0x.

LOG
ERROR

Probable Cause

Indicates an internal error in the application-specific integrated circuit (ASIC) hardware that may degrade
the data traffic.

Recommended
Action

Restart the system at the next maintenance window. If the problem persists, replace the blade.

CDR-1005
Message
Message Type
Severity

S,P(): best effort QoS will be turned
off at next port state change as it is not supported under this configuration.

LOG
WARNING

Probable Cause

Indicates that quality of service (QoS) will be turned off automatically at the next port state change
because best effort QoS is no longer supported on 4 Gbps or 8 Gbps platform long distance ports.

Recommended
Action

No action is required.

CDR-1006
Message
Message Type
Severity

S,P(): QoS overwrites
portcfglongdistance vc_translation_link_init. ARB will be used on the link.

LOG
WARNING

Probable Cause

Indicates that quality of service (QoS) has overwritten the fill word IDLE used on the long distance links.
Arbitrated loop (ARB) will be used on the link.

Recommended
Action

No action is required.

208

Fabric OS Message Reference
53-1002749-01

CDR-1007

5

CDR-1007
Message

Message Type
Severity

S,C: Internal link errors have been reported, no hardware
faults identified, continuing to monitor for errors: flt1:0x,
flt2:0x thresh1:0x.

LOG
WARNING

Probable Cause

Indicates that some errors were found in hardware that may or may not impact the data traffic.

Recommended
Action

No action is required.

CDR-1008
Message
Message Type
Severity

S,C: HW ASIC Chip warning Level 1 type = 0x.

LOG
WARNING

Probable Cause

Indicates an internal error in the application-specific integrated circuit (ASIC) hardware that may or may
not degrade the data traffic.

Recommended
Action

Restart the system at the next maintenance window.

CDR-1009
Message
Message Type
Severity

S,C: HW ASIC Chip warning Level 2 type = 0x.

LOG
WARNING

Probable Cause

Indicates an internal error in the application-specific integrated circuit (ASIC) hardware that may or may
not degrade the data traffic.

Recommended
Action

Restart the system at the next maintenance window.

Fabric OS Message Reference
53-1002749-01

209

5

CDR-1010

CDR-1010
Message

Message Type
Severity

S,C: Internal monitoring of faults has identified suspect
hardware, blade may need to be reset or replaced: fault1:0x,
fault2:0x thresh2:0x.

LOG
CRITICAL

Probable Cause

Indicates that above-normal errors observed in hardware that may or may not impact the data traffic.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

CDR-1011
Message

Message Type
Severity

S,P(): Link Timeout on internal port
ftx= tov= (>)
vc_no= crd(s)lost= complete_loss:.

LOG
WARNING

Probable Cause

Indicates that one or more credits have been lost on a back-end port, and there is no traffic on that port
for two seconds.

Recommended
Action

Turn on the back-end credit recovery to reset the link and recover the lost credits. If credit recovery has
already been turned on, the link will be reset to recover the credits and no action is required.

CDR-1012
Message

Message Type
Severity

S,P(): Port Fault: Hard () fault1= fault2= (0x 0x 0x).

LOG
WARNING

Probable Cause

Indicates that the specified port has failed. Port initialization will be retried.

Recommended
Action

Replace the SFP transceiver and the cable and then re-enable the port.

210

Fabric OS Message Reference
53-1002749-01

CDR-1014

5

CDR-1014
Message
Message Type
Severity

Link Reset on Internal Port S,P()
vc_no= crd(s)lost=.

LOG
WARNING

Probable Cause

Indicates that one or more credits were lost and the link is reset.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

CDR-1015
Message
Message Type
Severity

Port re-initialized due to Link Reset failure on internal Port S,P().

LOG
WARNING

Probable Cause

Indicates that specified port got re-initialized due to link reset failure.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

CDR-1016
Message
Message Type
Severity

Port is faulted due to port re-initialization failure on internal Port S,P() with reason .

LOG
ERROR

Probable Cause

Indicates that the specified port is faulted due to port re-initialization failure.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

Fabric OS Message Reference
53-1002749-01

211

5

CDR-1017

CDR-1017
Message
Message Type
Severity

Blade in Slot  faulted due to unavailable ports in internal Trunk.

LOG
ERROR

Probable Cause

Indicates that the specified blade is faulted due to unavailable ports in internal trunk.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

CDR-1018
Message
Message Type
Severity

Blade in Slot  faulted due to Link reset threshold value exceeded.

LOG
ERROR

Probable Cause

Indicates that the specified blade is faulted because the link reset threshold is exceeded.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

CDR-1019
Message
Message Type
Severity

S,C: HW ASIC Chip TXQ FID parity error threshold reached
type = 0x.

LOG
WARNING

Probable Cause

Indicates that an internal error is observed in the application-specific integrated circuit (ASIC) hardware
that may degrade the data traffic.

Recommended
Action

Restart the system at the next maintenance window.

212

Fabric OS Message Reference
53-1002749-01

CDR-1022

5

CDR-1022
Message

Message Type
Severity

S,P(): Link Timeout on External port,
ftx= tov= (>)
vc_no= crd(s)lost=.

LOG
WARNING

Probable Cause

Indicates that above-normal errors are observed in hardware that may or may not impact the data traffic.

Recommended
Action

When this error is observed persistently, power cycle the specified blade using the slotPowerOff and
slotPowerOn commands. If the problem persists, replace the blade.

CDR-1028
Message
Message Type
Severity

Detected excessive Link resets on the port in a second. Slot , Port
().

LOG
WARNING

Probable Cause

Indicates that the port received excessive link resets from peer port within 1 second and that exceeded
threshold.

Recommended
Action

When this error is observed persistently, change the small form-factor pluggable (SFP) transceiver or the
cable on the peer port to which this port is connected.

Fabric OS Message Reference
53-1002749-01

213

5

CHS-1002

CHS Messages
CHS-1002
Message
Message Type
Severity

ki_gd_register_action failed with rc = .

LOG | FFDC
ERROR

Probable Cause

Indicates an internal error.

Recommended
Action

To recover a bladed system, execute the slotPowerOff and slotPowerOn commands on the blade. To
recover a non-bladed system, execute the fastBoot command on the switch.

CHS-1003
Message
Message Type
Severity

Slot ENABLED but Not Ready during recovery, disabling slot =  rval =
.

LOG
ERROR

Probable Cause

Indicates that the slot state has been detected as inconsistent during failover or recovery.

Recommended
Action

For a bladed switch, execute the slotPowerOff and slotPowerOn commands to power cycle the blade.
For a non-bladed switch, restart or power cycle the switch.

CHS-1004
Message
Message Type
Severity

Blade attach failed during recovery, disabling slot = , rval =
.

LOG
ERROR

Probable Cause

Indicates that the specified blade has failed during failover or recovery.

Recommended
Action

For a bladed switch, execute the slotPowerOff and slotPowerOn commands to power cycle the blade.

214

For a non-bladed switch, restart or power cycle the switch.

Fabric OS Message Reference
53-1002749-01

CHS-1005

5

CHS-1005
Message
Message Type
Severity

Diag attach failed during recovery, disabling slot = .

LOG
ERROR

Probable Cause

Indicates that the diagnostic blade attach operation has failed during failover or recovery.

Recommended
Action

For a bladed switch, execute the slotPowerOff and slotPowerOn commands to power cycle the blade.
For a non-bladed switch, restart or power cycle the switch.

Fabric OS Message Reference
53-1002749-01

215

5

CNM-1001

CNM Messages
CNM-1001
Message
Message Type
Severity

Failed to allocate memory: ().

LOG
ERROR

Probable Cause

Indicates that the specified function has failed to allocate memory.

Recommended
Action

Check memory usage on the switch using the memShow command.
Restart or power cycle the switch.

CNM-1002
Message
Message Type
Severity

Failed to initialize  rc = .

LOG
ERROR

Probable Cause

Indicates that the initialization of a module within the Cluster Node Manager (CNM) has failed.

Recommended
Action

Download a new firmware version using the firmwareDownload command.

CNM-1003
Message
Message Type
Severity

Crypto device cfg between local switch () and peer () out of sync. New encryption session not allowed.

LOG
WARNING

Probable Cause

Indicates that the encryption engine nodes in the cluster encryption group have different configurations.

Recommended
Action

Synchronize the configuration in the cluster group using the cryptocfg command.

216

Fabric OS Message Reference
53-1002749-01

CNM-1004

5

CNM-1004
Message

iSCSI service is  on the switch.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the crypto service is enabled or disabled on the switch.

Recommended
Action

No action is required.

CNM-1005
Message

Posting event CNM_EVT_GRP_LEADER_ELECTED Name [], WWN [].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the cluster Encryption Group (EG) leader is elected.

Recommended
Action

No action is required.

CNM-1006
Message

Posting event CNM_EVT_NODE_JOIN nodeName [], WWN [], ipaddress
[].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the member node has joined.

Recommended
Action

No action is required.

CNM-1007
Message

Posting event CNM_EVT_GRP_LEADER_FAILED Name []

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the Encryption Group (EG) leader has failed.

Fabric OS Message Reference
53-1002749-01

217

5

CNM-1008

Recommended
Action

No action is required.

CNM-1008
Message

Posting event CNM_EVT_NODE_EJECT nodeName [], WWN [].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the specified node is ejected from the Encryption Group (EG).

Recommended
Action

No action is required.

CNM-1009
Message

Posting event CNM_EVT_STANDALONE_MODE.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the node is in standalone mode.

Recommended
Action

No action is required.

CNM-1010
Message

Posting event CNM_EVT_CLUSTER_UDATA_UPDATE cid [], ulen [].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates the client data update.

Recommended
Action

No action is required.

218

Fabric OS Message Reference
53-1002749-01

CNM-1011

5

CNM-1011
Message

Posting event CNM_EVT_NODE_JOIN_TIMEOUT nodeName [], WWN [],
ipaddress [].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates the node join timeout.

Recommended
Action

Take the peer node offline, and rejoin the node to Encryption Group (EG).

CNM-1012
Message

Posting event CNM_EVT_EG_DELETED.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the Encryption Group (EG) is deleted.

Recommended
Action

No action is required.

CNM-1013
Message

Posting event GL Node Split condition, isolating peer GL node .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the Encryption Group (EG) is split.

Recommended
Action

No action is required.

CNM-1014
Message

Posting event Node Admission Control passed, admitting node [].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the node admission control was successful.

Fabric OS Message Reference
53-1002749-01

219

5

CNM-1015

Recommended
Action

No action is required.

CNM-1015
Message

Posting event Potential Cluster Split condition.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates a Potential Cluster Split condition.

Recommended
Action

No action is required.

CNM-1016
Message

Posting event Detected a EG degrade condition.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates an Encryption Group (EG) degrade condition.

Recommended
Action

No action is required.

CNM-1017
Message

Got JOIN REQUEST from un-recognized GL node [], configured GL node is
[].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates a join request was received from an invalid group leader (GL) node.

Recommended
Action

No action is required.

220

Fabric OS Message Reference
53-1002749-01

CNM-1018

5

CNM-1018
Message

Got CNM_FSM_EVT_JOIN_REQ when already a member, My assigned name [],
dropping request.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates the node is already a member of the Encryption Group (EG).

Recommended
Action

No action is required.

CNM-1019
Message

Join Rejected by GL node, fix certificate and later add member node from GL node,
or reboot the member node.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates an invalid member node certificate.

Recommended
Action

Install a valid certificate and add member node to the group leader (GL) node, or reboot the member
node.

CNM-1020
Message

Node Admission Control failed due to mismatch in certificates, rejecting node
[].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that node admission control has failed.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

221

5

CNM-1021

CNM-1021
Message

Failed to sign the node authentication message, admission control might fail.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that node admission control has failed.

Recommended
Action

No action is required.

CNM-1022
Message

Operation not allowed on GL Node.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates an operation is not allowed on a group leader (GL) node.

Recommended
Action

No action is required.

CNM-1023
Message

Group Leader node eject is not allowed.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates an eject operation is not allowed in group leader (GL) node.

Recommended
Action

No action is required.

CNM-1024
Message

Operation not required on GL node.

Message Type

LOG

Severity

INFO

Probable Cause

222

Indicates an operation is not required on a group leader (GL) node.

Fabric OS Message Reference
53-1002749-01

CNM-1025

Recommended
Action

5

No action is required.

CNM-1025
Message

Operation not allowed, as member is active with the Cluster. Eject member node and
retry.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates an operation is not allowed on a member node.

Recommended
Action

Eject member node and retry the operation.

CNM-1026
Message

Recvd HBT Msg with version mismatch, Recvd Hdr version 0x Exp Hdr version 0x Node .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that a version mismatch has occurred.

Recommended
Action

Upgrade the firmware or delete the node from the Encryption Group (EG).

CNM-1027
Message

Received HBT from non-Group Member Node [].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates an operation is not allowed on a non-group member node.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

223

5

CNM-1028

CNM-1028
Message

Certfile  already exists. No need to sync up.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the certificate file for the node already exists.

Recommended
Action

No action is required.

CNM-1029
Message
Message Type
Severity

Certfile  content does not match the cert sent by GL.

LOG
WARNING

Probable Cause

Indicates that the contents of the node's certificate file is different from the certificate file sent by the
group leader (GL) node.

Recommended
Action

No action is required.

CNM-1030
Message
Message Type
Severity

Certfile  read less number of bytes .

LOG
WARNING

Probable Cause

Indicates that the read operation of the certificate file returned a fewer number of bytes than expected.

Recommended
Action

No action is required.

CNM-1031
Message
Message Type
Severity
Probable Cause

224

Certfile  open failed with errno .

LOG
WARNING
Indicates that an attempt to open the certificate file has failed.

Fabric OS Message Reference
53-1002749-01

CNM-1032

Recommended
Action

5

No action is required.

CNM-1032
Message
Message Type
Severity

Certfile  size  does not match cert file size
 sent by GL.

LOG
WARNING

Probable Cause

Indicates that there is a size mismatch between a node's certificate file and the certificate file received
from the group leader (GL).

Recommended
Action

No action is required.

CNM-1033
Message
Message Type
Severity

Some of the defined nodes in the Encryption Group are not ONLINE. Encryption Group
is in degraded state.

LOG
WARNING

Probable Cause

Indicates that the cluster is in a degraded state.

Recommended
Action

No action is required.

CNM-1034
Message

All the defined nodes in the Encryption Group are ONLINE. Cluster is in converged
state.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the cluster is in a converged state.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

225

5

CNM-1035

CNM-1035
Message
Message Type
Severity

Cluster is in degraded state. Posting degrade event.

LOG
WARNING

Probable Cause

Indicates an event is being posted to specify the cluster is in a degraded state.

Recommended
Action

No action is required.

CNM-1036
Message

All the active nodes of the cluster are in ONLINE state. Posting converged event.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates an event is being posted to specify the cluster is in a converged state.

Recommended
Action

No action is required.

CNM-1037
Message

Split-Brain Arbitration lost, minority GL Node, remote:local
[:].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that split-brain arbitration is lost.

Recommended
Action

No action is required.

226

Fabric OS Message Reference
53-1002749-01

CNM-1038

5

CNM-1038
Message

Split-Brain Arbitration won, majority GL Node, remote:local
[:].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that split-brain arbitration is won.

Recommended
Action

No action is required.

CNM-1039
Message

Split-Brain Arbitration lost, Minority WWN/GL Node, remote_WWN:local_WWN .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that split-brain arbitration is lost.

Recommended
Action

No action is required.

CNM-1040
Message

Split-Brain Arbitration won, Majority WWN/GL Node, remote_WWN:local_WWN .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that split-brain arbitration is won.

Recommended
Action

No action is required.

CNM-1041
Message

Updating persistent Cluster DB, please avoid powering off the switch.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates the system is updating the persistent database.

Fabric OS Message Reference
53-1002749-01

227

5

CNM-1042

Recommended
Action

No action is required.

CNM-1042
Message

Completed updating persistent Cluster DB.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates the persistent database update is complete.

Recommended
Action

No action is required.

CNM-1043
Message
Message Type
Severity

Received HBT from undefined node IpAddress [], WWN []. Possible
configuration error.

LOG
ERROR

Probable Cause

Indicates that the remote node's WWN may be changed.

Recommended
Action

No action is required.

CNM-1044
Message
Message Type
Severity

Cluster Create Failed as the Certificate files not found, Please do the initnode.

LOG
ERROR

Probable Cause

Indicates that the initnode is not invoked.

Recommended
Action

Execute the cryptocfg --initnode command.

228

Fabric OS Message Reference
53-1002749-01

CNM-1045

5

CNM-1045
Message
Message Type
Severity

Member node [] is having dual IP stack.Registering member node with dual IP
in an EG with only IPv6 is not allowed.

LOG
ERROR

Probable Cause

Indicates that the member node with dual IP stack was registered with the IPv6 Encryption Group (EG).

Recommended
Action

No action is required.

CNM-1046
Message

Posting event CNM_EVT_NODE_LEAVE nodeName [], WWN [].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the node has decided to leave the Encryption Group (EG).

Recommended
Action

No action is required.

CNM-1047
Message

Network Interface to Remote Node [] is [].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the status of the network interface is up or down.

Recommended
Action

No action is required.

CNM-1048
Message

Posting .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates the event that is posted.

Fabric OS Message Reference
53-1002749-01

229

5

CNM-1049

Recommended
Action

No action is required.

CNM-1049
Message
Message Type
Severity

Failed to define node, Node Name [].

LOG
ERROR

Probable Cause

Indicates the failure to define the node object.

Recommended
Action

No action is required.

CNM-1050
Message
Message Type
Severity

Node Admission Control failed due to mismatch in Access Gateway Daemon (AGD) mode
settings, rejecting node [].

LOG
ERROR

Probable Cause

Indicates mode mismatch between the switches, such as the Access Gateway mode mismatch.

Recommended
Action

No action is required.

CNM-1051
Message
Message Type
Severity

Join Rejected by GL Node due to Access Gateway Daemon mode mismatch, ensure mode
settings are same across all nodes in EG.

LOG
ERROR

Probable Cause

Indicates mode mismatch between the switches, such as the Access Gateway mode mismatch.

Recommended
Action

No action is required.

230

Fabric OS Message Reference
53-1002749-01

CNM-1052

5

CNM-1052
Message
Message Type
Severity

Member node registered with another Encryption Group. To proceed eject the member
node [] from other EG.

LOG
ERROR

Probable Cause

Indicates that the member node is registered with another Encryption Group (EG).

Recommended
Action

No action is required.

CNM-1053
Message
Message Type
Severity

Node is already a registered member of another EG. First eject the current node
[] from the existing EG and then try.

LOG
ERROR

Probable Cause

Indicates that the node is already a registered member of another Encryption Group (EG).

Recommended
Action

Eject the specified node from EG and retry the operation.

CNM-1054
Message

Encryption Group database state [] with node IP [], WWN [].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates the status of the cluster database.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

231

5

CNM-1055

CNM-1055
Message

Got CNM_FSM_EVT_JOIN_REQ when already a member from same GL node, rejoining EG
with GL [].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates the node is rejoining the Encryption Group (EG).

Recommended
Action

No action is required.

CNM-1056
Message

Posting event CNM_EVT_EE_INITIALIZING Slot [], WWN [], IP [], flags
[].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the encryption engine is added into the Encryption Group (EG).

Recommended
Action

No action is required.

CNM-1057
Message

Posting event CNM_EVT_ONLINE Slot [], WWN [], IP [], flags
[].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the encryption engine is online in the Encryption Group (EG).

Recommended
Action

No action is required.

232

Fabric OS Message Reference
53-1002749-01

CNM-1058

5

CNM-1058
Message

Posting event CNM_EVT_OFFLINE Slot [], WWN [], IP [], flags
[].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the encryption engine is removed from the Encryption Group (EG).

Recommended
Action

No action is required.

CNM-1059
Message

Local Node CP certificate pair mismatch detected, re-initialize the node.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the certificate pair is mismatched.

Recommended
Action

No action is required.

CNM-1060
Message

Local Node CP certificate pair match detected.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the certificate pair is matched.

Recommended
Action

No action is required.

CNM-1061
Message

IP of the switch changed from [] to [].

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the switch IP address has changed.

Fabric OS Message Reference
53-1002749-01

233

5

CNM-1062

Recommended
Action

No action is required.

CNM-1062
Message

Copied certificate to [] due to change in IP.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the certificate was copied to the file with new IP name.

Recommended
Action

No action is required.

CNM-3001
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: encryption group
\"\" created.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified encryption group was created.

Recommended
Action

No action is required.

CNM-3002
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: encryption group deleted.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates an encryption group was deleted.

Recommended
Action

No action is required.

234

Fabric OS Message Reference
53-1002749-01

CNM-3003

5

CNM-3003
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Membernode \"\" added to
encryption group.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified member node was added to an encryption group.

Recommended
Action

No action is required.

CNM-3004
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Membernode \"\" ejected
from encryption group.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified member node was ejected from an encryption group.

Recommended
Action

No action is required.

CNM-3005
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Membernode \"\" left
encryption group.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified member node left an encryption group.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

235

5

CNM-3006

CNM-3006
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Heartbeat miss count set to
.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the heartbeat miss value was set.

Recommended
Action

No action is required.

CNM-3007
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Heartbeat timeout set to
.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the heartbeat timeout value was set.

Recommended
Action

No action is required.

CNM-3008
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Routing mode of EE in slot  set to
.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the encryption engine routing mode was set.

Recommended
Action

No action is required.

236

Fabric OS Message Reference
53-1002749-01

CNM-3009

5

CNM-3009
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info:   registered.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified member node was registered.

Recommended
Action

No action is required.

CNM-3010
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Membernode  unregistered.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified member node was unregistered.

Recommended
Action

No action is required.

CNM-3011
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Encryption group synchronized.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates an encryption group was synchronized.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

237

5

CNM-3012

CNM-3012
Message
Message Type
Class
Severity

Deleteing an EG with LUNs setup for encryption can lead to LUNs being disabled if
Encryption Group name is not preserved ().

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the Encryption Group (EG) was deleted. Recreate EG with the same name if LUNs are set
up for encryption.

Recommended
Action

Preserve the EG name when EG is recreated if LUNs are set up for encryption.

238

Fabric OS Message Reference
53-1002749-01

CONF-1000

5

CONF Messages
CONF-1000
Message
Message Type

configDownload completed successfully .

LOG | AUDIT

Class

CFG

Severity

INFO

Probable Cause

Indicates that the configDownload operation was initiated and completed successfully. The Info about
the parameters and AD variable is the description of the classes of configuration parameters that were
downloaded. If Admin Domain (AD) is enabled, the AD number is specified in the description.

Recommended
Action

No action is required.

CONF-1001
Message

configUpload completed successfully .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the configUpload operation was initiated and completed successfully. The Info about the
parameters and AD variable is the description of the classes of configuration parameters that were
uploaded. If Admin Domain (AD) is enabled, the AD number is specified in the description.

Recommended
Action

No action is required.

CONF-1020
Message
Message Type

configDownload not permitted .

AUDIT

Class

CFG

Severity

INFO

Probable Cause

Indicates that a configDownload operation is not permitted. There are many possible causes.

Recommended
Action

Execute the errShow command to view the error log. Correct the error and execute the
configDownload command again.

Fabric OS Message Reference
53-1002749-01

239

5

CONF-1021

CONF-1021
Message

configUpload not permitted .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that a configUpload operation is not permitted. There are many possible causes.

Recommended
Action

Execute the errShow command to view the error log. Correct the error and execute the configUpload
command again.

CONF-1022
Message
Message Type
Class
Severity

Downloading configuration without disabling the switch was unsuccessful.

AUDIT
CFG
WARNING

Probable Cause

Indicates an attempt to download the configuration without disabling the switch was unsuccessful
because there are one or more parameters that require the switch to be disabled.

Recommended
Action

Disable the switch using the switchDisable command and download the configuration.

CONF-1023
Message

configDownload failed .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that a configDownload operation has failed.

Recommended
Action

Execute the errShow command to view the error log. Correct the error and execute the
configDownload command again.

240

Fabric OS Message Reference
53-1002749-01

CONF-1024

5

CONF-1024
Message

configUpload failed .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates a configUpload operation has failed.

Recommended
Action

Execute the errShow command to view the error log. Correct the error and execute the configUpload
command again.

CONF-1030
Message
Message Type
Severity

Configuration database full, data not committed (key: ).

LOG
WARNING

Probable Cause

Indicates that the previous configuration commands have resulted in a database full
condition.Configuration changes associated with the specified key was not applied.

Recommended
Action

Use configure command and various other commands to erase configuration parameters that are no
longer required. As a last resort, execute the configDefault command and reconfigure the system.

CONF-1031
Message

configDefault completed successfully .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the configDefault command was initiated and completed successfully.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

241

5

CONF-1032

CONF-1032
Message

configRemove completed successfully .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the configRemove command was initiated and completed successfully.

Recommended
Action

No action is required.

CONF-1040
Message

configDefault Failed. .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that an error occurred while executing the configDefault command.

Recommended
Action

Execute the errShow command to view the error log. Correct the error and execute the configDefault
command again.

CONF-1041
Message

configRemove Failed. .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that an error occurred while executing the configRemove command.

Recommended
Action

Execute the errShow command to view the error log. Correct the error and execute the configRemove
command again.

242

Fabric OS Message Reference
53-1002749-01

CONF-1042

5

CONF-1042
Message
Message Type

Fabric Configuration Parameter  changed to 

LOG | AUDIT

Class

CFG

Severity

INFO

Probable Cause

Indicates that the fabric configuration parameter value has been changed.

Recommended
Action

No action is required.

CONF-1043
Message
Message Type

Fabric Configuration Parameter  changed to 

LOG | AUDIT

Class

CFG

Severity

INFO

Probable Cause

Indicates that the fabric configuration parameter value has been changed.

Recommended
Action

No action is required.

CONF-1044
Message
Message Type

Fabric Configuration Parameter  changed from  to


LOG | AUDIT

Class

CFG

Severity

INFO

Probable Cause

Indicates that the fabric configuration parameter value has been changed by a user.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

243

5

CTAP-1001

CTAP Messages
CTAP-1001
Message

Key acquisition for  .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that a change in the tape pool database has triggered the key acquisition process for each
pool.

Recommended
Action

Do not start tape backup or restore operations involving tape pools until the process is complete.

244

Fabric OS Message Reference
53-1002749-01

CVLC-1001

5

CVLC Messages
CVLC-1001
Message

 re-key , LUN SN: . Container:
, Initiator: , LUN ID: .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the first-time encryption, key expired, or manual re-key operation is performed. The
operation has been started, completed, failed, or cancelled.

Recommended
Action

No action is required.

CVLC-1002
Message

Tape session . Container: , Initiator: , LUN ID: .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that a tape session was started, failed, or cancelled.

Recommended
Action

No action is required.

CVLC-1003
Message

Forceful LUN policy change to clear text while re-key session is still active.
Container: , Initiator: , LUN ID:
.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the encryption LUN policy was forcefully changed while a re-key session was still active.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

245

5

CVLC-1004

CVLC-1004
Message

Forceful encryption LUN removal while re-key session is still active. Container:
, Initiator: , LUN ID: .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the encryption LUN was forcefully removed while a re-key session was still active.

Recommended
Action

No action is required.

CVLC-1005
Message

There are no LUNs found from the target. Container: ,
Initiator: , LUN ID: .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that there are no LUNs found from the target-initiator pair.

Recommended
Action

No action is required.

CVLC-1006
Message
Message Type
Severity

Duplicate LUN serial number  found. Container: ,
Initiator: .

LOG
WARNING

Probable Cause

Indicates that there is more than one LUN serial number discovered from the same target. Therefore,
encryption on this target is disabled.

Recommended
Action

No action is required.

246

Fabric OS Message Reference
53-1002749-01

CVLC-1007

5

CVLC-1007
Message

Message Type
Severity

Removal of encryption LUN is not allowed when decrypt of existing data is enabled.
Container: , Initiator: , LUN ID:
.

LOG
ERROR

Probable Cause

Indicates that there has been an attempt to remove the encryption LUN while decryption of existing data
is still enabled.

Recommended
Action

To preserve the user data, execute the cryptocfg --modify -LUN -cleartext command to convert to
cleartext LUN.
Use the cryptocfg --modify -LUN -cleartext command to disable decryption of existing data.
Then try to delete the LUN again.

CVLC-1008
Message
Message Type
Severity

LUN discovery failure: , Container: ,
Initiator: , LUN ID: .

LOG
ERROR

Probable Cause

Indicates that LUN discovery failed.

Recommended
Action

No action is required.

CVLC-1009
Message

Message Type
Severity

Wrong device type: should be , found . Container: , Initiator:
, LUN ID: .

LOG
ERROR

Probable Cause

Indicates that LUN discovery failed.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

247

5

CVLC-1010

CVLC-1010
Message
Message Type
Severity

Tape license is required for tape container: .

LOG
ERROR

Probable Cause

Indicates that the tape container is configured with non-Brocade mode but there is no valid license.

Recommended
Action

Obtain a license for non-Brocade mode.

CVLC-1011
Message
Message Type
Severity

Third party license is required for encryption LUN in third party mode. Container:
, Initiator: , LUN ID: .

LOG
ERROR

Probable Cause

Indicates that the encryption LUN is configured with non-Brocade mode but there is no valid license.

Recommended
Action

Obtain a license for non-Brocade mode.

CVLC-1012
Message

Message Type
Severity

Disk metadata is in wrong format ().
Container: , Initiator: , LUN ID:
.

LOG
ERROR

Probable Cause

Indicates that the metadata found on the disk LUN is in the wrong format.

Recommended
Action

Use the cryptoCfg command to change the metadata mode of the LUN.

248

Fabric OS Message Reference
53-1002749-01

CVLC-1013

5

CVLC-1013
Message
Message Type
Severity

Unable to retrieve key record from the key archive. Container: , Initiator: , LUN ID: .

LOG
ERROR

Probable Cause

Indicates that the encryption engine is unable to retrieve the key record base on the key ID found in the
metadata.

Recommended
Action

No action is required.

CVLC-1014
Message
Message Type
Severity

Missing Key ID from user input. Container: , Initiator:
, LUN ID: .

LOG
ERROR

Probable Cause

Indicates that the data state in the LUN configuration is in the encrypted state without a key ID and there
is no metadata found on the LUN.

Recommended
Action

Use the cryptoCfg command to add the key ID, if available.

CVLC-1015
Message

LUN is set to read only mode. Reason: .
Container: , Initiator: , LUN ID:
.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the LUN is set to read-only mode because there is a conflict in the configuration.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

249

5

CVLC-1016

CVLC-1016
Message

LUN is out of read only mode. Reason: .
Container: , Initiator: , LUN ID:
.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the LUN is set to read/write mode.

Recommended
Action

No action is required.

CVLC-1017
Message
Message Type
Severity

Event: . Container: , Initiator:
, LUN ID: .

LOG
ERROR

Probable Cause

Indicates a warning or an error event.

Recommended
Action

No action is required.

CVLC-1018
Message

Event: . Container: , Initiator:
, LUN ID: .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates an informational event.

Recommended
Action

No action is required.

250

Fabric OS Message Reference
53-1002749-01

CVLC-1019

5

CVLC-1019
Message
Message Type
Severity

Metadata exists while data state is clear text. Container: , Initiator: , LUN ID: .

LOG
ERROR

Probable Cause

Indicates that the data state in the LUN configuration is cleartext, but metadata exists on the LUN.

Recommended
Action

Use the cryptoCfg command to confirm the configuration.

CVLC-1020
Message
Message Type
Severity

Metadata exists while LUN is clear text. Container: ,
Initiator: , LUN ID: .

LOG
ERROR

Probable Cause

Indicates that metadata exists on the LUN that is in cleartext state.

Recommended
Action

Use the cryptoCfg command to confirm the configuration.

CVLC-1021
Message

User provided key ID  is ignored while metadata  exists. Container: , Initiator:
, LUN ID: .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the key ID provided is ignored because metadata exists on the LUN.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

251

5

CVLC-1022

CVLC-1022
Message

User provided key ID  is ignored while data state is
clear text. Container: , Initiator: , LUN ID: .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the key ID provided is ignored because the data state is cleartext.

Recommended
Action

No action is required.

CVLC-1023
Message

Rebalance recommended on EE: .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that due to container configuration changes, weights are not balanced on OB1s.

Recommended
Action

Run the cryptocfg --rebalance command to increase system performance.

CVLC-1024
Message

Device Decommission operation . Container:
, Initiator: , LUN ID: .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the device decommission process has either succeeded or failed.

Recommended
Action

No action is required.

252

Fabric OS Message Reference
53-1002749-01

CVLC-1025

5

CVLC-1025
Message

Message Type
Severity

Secondary Metadata exists for encrypted LUN not configured with -newLUN option.
Container: , Initiator: , LUN ID:
.

LOG
ERROR

Probable Cause

Indicates that the secondary metadata exists on the LUN that is not configured with the -newLUN option.

Recommended
Action

Use the cryptoCfg command to remove and add the LUN with the -newLUN option.

CVLC-1026
Message

Some secondary metadata missing for encrypted LUN configured with -newLUN option.
Container: , Initiator: , LUN ID:
.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the secondary metadata does not exist on all logical block addresses (LBAs) for a LUN that
is configured with the -newLUN option.

Recommended
Action

No action is required.

CVLC-1027
Message

Message Type
Severity

Encrypted LUN configured with -newLUN option does not contain any metadata.
Container: , Initiator: , LUN ID:
.

LOG
ERROR

Probable Cause

Indicates that the metadata was corrupted.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

253

5

CVLC-1028

CVLC-1028
Message
Message Type
Severity

Not starting auto rekey on LUN with uncompressible blocks 1-16. Container: , Initiator: , LUN ID: .

LOG
WARNING

Probable Cause

Indicates a warning event.

Recommended
Action

Perform a manual re-key on this LUN.

CVLC-1029
Message

Message Type
Severity

Mirror LUN is disabled as primary LUN is being rekeyed without splitting the
mirror. Container: , Initiator: ,
LUN ID: .

LOG
WARNING

Probable Cause

Indicates that performing first-time encryption or manual re-key of primary LUN without splitting the
mirror.

Recommended
Action

Break the mirror and re-establish the mirror after re-key on primary LUN is complete.

CVLC-1030
Message
Message Type
Severity

Primary LUN may be out of sync with mirror LUN. Container: , Initiator: , LUN ID: .

LOG
WARNING

Probable Cause

Indicates the manual re-key was completed on primary LUN.

Recommended
Action

Perform the following steps.

1. Make the target ports of the mirror LUN offline to hosts.
2. Re-establish the mirror.
3. After the mirror is in sync, split the mirror.
4. Bring back the target ports of the mirror LUN online.

254

Fabric OS Message Reference
53-1002749-01

CVLC-1031

5

CVLC-1031
Message
Message Type
Severity

Primary LUN is restored from mirror LUN. LUN in read-only mode. Container: , Initiator: , LUN ID: .

LOG
WARNING

Probable Cause

Indicates that a re-keyed primary LUN may have been restored from a mirror LUN without synchronizing.

Recommended
Action

Perform the following steps.

1. Create a new primary LUN.
2. Add the new primary LUN to its container with the -newLUN option.
3. Using host-based migration application, copy data from the old to the new primary LUN.

CVLC-1032
Message

Secondary metadata for LUN has been restored. Container: ,
Initiator: , LUN ID: .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates the host I/Os to secondary metadata region.

Recommended
Action

No action is required.

CVLC-1033
Message

Rebalance completed for EE: . Device login in progress.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that a rebalance operation was performed.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

255

5

CVLC-1034

CVLC-1034
Message

Rekey failed on Container: , Initiator: , LUN ID:  because .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the first-time encryption, key expired, or manual re-key operation failed.

Recommended
Action

No action is required.

CVLC-1035
Message
Message Type
Severity

A decommissioned LUN has been added back as encrypted LUN. Container: , Initiator: , LUN ID: .

LOG
ERROR

Probable Cause

Indicates that a decommissioned LUN has been added as an encrypted LUN.

Recommended
Action

Perform the following steps.

1. Remove the LUN from the container.
2. Add the LUN back as a cleartext LUN.
3. Modify the LUN policy to encrypt.

CVLC-1039
Message

Refresh DEK operation . Container: , Initiator: , LUN ID: .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates the status of the refresh DEK operation.

Recommended
Action

No action is required.

256

Fabric OS Message Reference
53-1002749-01

CVLC-1041

5

CVLC-1041
Message
Message Type
Severity

. Container: , Initiator: , LUN ID: .

LOG
WARNING

Probable Cause

Indicates that the host write operation on secondary metadata block region failed.

Recommended
Action

Disable the initiator port.

Fabric OS Message Reference
53-1002749-01

257

5

CVLM-1001

CVLM Messages
CVLM-1001
Message
Message Type
Severity

Failed to allocate memory: ().

LOG
ERROR

Probable Cause

Indicates that the specified function has failed to allocate memory.

Recommended
Action

Check the memory usage on the switch using the memShow command.
Restart or power cycle the switch.

CVLM-1002
Message
Message Type
Severity

Failed to initialize  rc = .

LOG
ERROR

Probable Cause

Indicates that the initialization of a module within the Crypto Virtual LUN Manager (CVLM) daemon has
failed.

Recommended
Action

Download a new firmware version using the firmwareDownload command.

CVLM-1003
Message

Crypto device configuration has been committed by switch ().

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the specified switch has committed a crypto device configuration.

Recommended
Action

No action is required.

258

Fabric OS Message Reference
53-1002749-01

CVLM-1004

5

CVLM-1004
Message
Message Type
Severity

Crypto device configuration between local switch () and peer
() is out of sync. New encryption session is not allowed.

LOG
WARNING

Probable Cause

Indicates that encryption engine nodes in the cluster encryption group have different configurations.

Recommended
Action

Synchronize the configuration in the cluster group using the cryptocfg --commit command.

CVLM-1005
Message

Crypto service is  on the switch.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the crypto service is enabled or disabled on the switch.

Recommended
Action

No action is required.

CVLM-1006
Message
Message Type
Severity

Crypto device  in target container  is not in AD0.

LOG
WARNING

Probable Cause

Indicates that the crypto device in the crypto target container is not in root zone database (AD0).

Recommended
Action

Use the ad command to move the crypto device into AD0.

CVLM-1007
Message
Message Type
Severity
Probable Cause

Redirect zone update failure. Status is .

LOG
WARNING
Indicates that the redirect zone update has failed.

Fabric OS Message Reference
53-1002749-01

259

5

CVLM-1008

Recommended
Action

Run the cryptocfg --commit command again.

CVLM-1008
Message
Message Type
Severity

The member ( ) of HAC () is not in the fabric.

LOG
WARNING

Probable Cause

Indicates that the member of the HA cluster (HAC) is not in the fabric.

Recommended
Action

Check the inter-switch link (ISL) port connected to the fabric.

CVLM-1009
Message

The member ( ) of HAC () is in the fabric.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the member of the HA cluster (HAC) is found in the fabric.

Recommended
Action

No action is required.

CVLM-1010
Message
Message Type
Severity

The IP address of EE ( ) IO link is not configured.

LOG
WARNING

Probable Cause

Indicates that the IP address of the encryption engine IO link is not configured.

Recommended
Action

Configure the encryption engine IO link IP address using the ipAddrSet command.

260

Fabric OS Message Reference
53-1002749-01

CVLM-1011

5

CVLM-1011
Message

The HAC failover occurs at EE ( ).

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the HA cluster (HAC) failover occurs at the encryption engine.

Recommended
Action

No action is required.

CVLM-1012
Message

The HAC failback occurs at EE ( ).

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the HA cluster (HAC) failback occurs at the encryption engine.

Recommended
Action

No action is required.

CVLM-1013
Message
Message Type
Severity

Redirect zone create failed because no Host/Target
(/) L2 zone exists.

LOG
ERROR

Probable Cause

Indicates that creation of the redirect zone has failed.

Recommended
Action

Create the Layer 2 zone for host and target and run the cryptocfg --commit command again.

Fabric OS Message Reference
53-1002749-01

261

5

CVLM-1014

CVLM-1014
Message
Message Type
Severity

RD zone getting deleted for which there is no Host/Target
(/) L2 zone exists in effective configuration.

LOG
ERROR

Probable Cause

Indicates deletion of Frame Redirect (RD) zone and there is no corresponding Layer 2 zone present, but
IT pair is in crypto configuration.

Recommended
Action

Disable the target access to the host, recreate the Layer 2 zone for host and target, and run the
cryptocfg --commit command again to recreate the RD zone.

CVLM-1015
Message
Message Type
Severity

Unable to read basewwn from blade in slot .

LOG
ERROR

Probable Cause

Indicates a failure to read the base WWN programmed on SEEPROM from this blade. Probably,
SEEPROM is not programmed properly.

Recommended
Action

WWN allocation is not possible from this blade, but the blade can be used for crypto operations.
SEEPROM needs to be reprogrammed on this blade.

CVLM-1016
Message
Message Type
Severity

Invalid base WWN () and/or page index () received from the blade in
slot .

LOG
ERROR

Probable Cause

Indicates that invalid base WWN and index are read from SEEPROM on this blade. Probably,
SEEPROM is not programmed properly.

Recommended
Action

WWN allocation is not possible from this blade, but the blade can be used for crypto operations.
SEEPROM needs to be reprogrammed on this blade.

262

Fabric OS Message Reference
53-1002749-01

CVLM-3001

5

CVLM-3001
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Failback mode set to .

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the failback mode was set.

Recommended
Action

No action is required.

CVLM-3002
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: HA cluster \"\" created.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified HA cluster was created.

Recommended
Action

No action is required.

CVLM-3003
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: HA cluster \"\" deleted.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified HA cluster was deleted.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

263

5

CVLM-3004

CVLM-3004
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Cluster member added to HA cluster
\"\".

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that an HA cluster member was added.

Recommended
Action

No action is required.

CVLM-3005
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Cluster member removed from HA cluster
\"\".

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that an HA cluster member was removed.

Recommended
Action

No action is required.

CVLM-3006
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Current node WWN/slot  /
 replaced with new node WWN/slot:  / .

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that an HA cluster member was replaced.

Recommended
Action

No action is required.

264

Fabric OS Message Reference
53-1002749-01

CVLM-3007

5

CVLM-3007
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info:  container
\"\" created.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified crypto-target container was created.

Recommended
Action

No action is required.

CVLM-3008
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Container \"\" deleted.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified crypto-target container was deleted.

Recommended
Action

No action is required.

CVLM-3009
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Manual failback from EE
/ to EE /.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that a manual failback was performed to an encryption engine.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

265

5

CVLM-3010

CVLM-3010
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Move crypto target container
\"\" to EE /.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified crypto-target container was moved to another encryption engine.

Recommended
Action

No action is required.

CVLM-3011
Message

Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Initiator PWWN \"\"
Initiator NWWN \"\" added to crypto target container
\"\".

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that an initiator was added to a crypto-target container.

Recommended
Action

No action is required.

CVLM-3012
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Initiator \"\" removed from
crypto target container \"\".

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified initiator was removed from the crypto-target container.

Recommended
Action

No action is required.

266

Fabric OS Message Reference
53-1002749-01

CVLM-3013

5

CVLM-3013
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: LUN , attached through Initiator
\"\", added to crypto target container \"\".

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that a LUN was added to a crypto-target container.

Recommended
Action

No action is required.

CVLM-3014
Message

Message Type
Class
Severity

Event: cryptocfg Status: success, Info: LUN , attached through
Initiator \"\" in crypto target container \"\",
modified.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified LUN in the crypto-target container was modified.

Recommended
Action

No action is required.

CVLM-3015
Message

Message Type
Class
Severity

Event: cryptocfg Status: success, Info: LUN , attached through
initiator \"\", removed from crypto target container
\"\".

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified LUN was removed from the crypto-target container.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

267

5

CVLM-3016

CVLM-3016
Message

Message Type
Class
Severity

Event: cryptocfg Status: success, Info: LUN , attached through
Initiator \"\" in crypto target container \"\",
enabled.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified LUN in a crypto-target container was enabled.

Recommended
Action

No action is required.

CVLM-3017
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Tape pool \"\"
created.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified tape pool was created.

Recommended
Action

No action is required.

CVLM-3018
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Tape pool \"\"
deleted.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified tape pool was deleted.

Recommended
Action

No action is required.

268

Fabric OS Message Reference
53-1002749-01

CVLM-3019

5

CVLM-3019
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Tapepool \"\"
modified.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the specified tape pool was modified.

Recommended
Action

No action is required.

CVLM-3020
Message

Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Manual rekey of LUN  attached
through Initiator \"\" in crypto tgt container
\"\".

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that a manual re-key of a LUN was performed.

Recommended
Action

No action is required.

CVLM-3021
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Manual rekey all performed.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that a complete manual re-key was performed.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

269

5

CVLM-3022

CVLM-3022
Message

Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Resume rekey of LUN  attached
through Initiator \"\" in crypto tgt container
\"\".

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that a resume re-key was performed.

Recommended
Action

No action is required.

CVLM-3023
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Transaction committed.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that a transaction commit operation was performed.

Recommended
Action

No action is required.

CVLM-3024
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Transaction  aborted.

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that a transaction abort operation was performed.

Recommended
Action

No action is required.

270

Fabric OS Message Reference
53-1002749-01

CVLM-3025

5

CVLM-3025
Message
Message Type
Class
Severity

Event: cryptocfg Status: started, Info: Decommission of device (container
 initiator , LUN ).

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the decommission operation has started.

Recommended
Action

No action is required.

CVLM-3026
Message
Message Type
Class
Severity

Event: cryptocfg Status: Failed, Info : Decommission of device (container
, Initiator , LUN ).

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the decommission operation has failed for the device.

Recommended
Action

Run the cryptocfg --decommission command.

CVLM-3027
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: Decommission of device (container
, initiator , LUN ).

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the decommission operation has been completed for the device.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

271

5

CVLM-3028

CVLM-3028
Message
Message Type
Class
Severity

Event: cryptocfg Status: success, Info: SRDF mode set to .

AUDIT | LOG
SECURITY
INFO

Probable Cause

Indicates that the Symmetrix Remote Data Facility (SRDF) mode was set.

Recommended
Action

No action is required.

272

Fabric OS Message Reference
53-1002749-01

DOT1-1001

5

DOT1 Messages
DOT1-1001
Message

802.1X is enabled globally.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that 802.1X is enabled globally.

Recommended
Action

No action is required.

DOT1-1002
Message

802.1X is disabled globally.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that 802.1X is disabled globally.

Recommended
Action

No action is required.

DOT1-1003
Message

802.1X is enabled for port .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that 802.1X is enabled on the specified port.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

273

5

DOT1-1004

DOT1-1004
Message

Port  is forcefully unauthorized.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the specified port has been unauthorized forcefully using the dot1x port-control
force-unauthorized command.

Recommended
Action

No action is required.

DOT1-1005
Message

802.1X authentication is successful on port .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that 802.1X authentication has succeeded on the specified port.

Recommended
Action

No action is required.

DOT1-1006
Message
Message Type
Severity

802.1X authentication has failed on port .

LOG
WARNING

Probable Cause

Indicates that 802.1X authentication has failed on the specified port due to incorrect credentials or the
remote authentication dial-in user service (RADIUS) server is not functioning properly.

Recommended
Action

Check the credentials configured with the supplicant and the RADIUS server.

274

Fabric OS Message Reference
53-1002749-01

DOT1-1007

5

DOT1-1007
Message
Message Type
Severity

No RADIUS server available for authentication.

LOG
CRITICAL

Probable Cause

Indicates that there is no remote authentication dial-in user service (RADIUS) server available for
authentication.

Recommended
Action

Execute the aaaConfig --show command to verify that the configured RADIUS servers are reachable
and functioning.

DOT1-1008
Message

Port  is forcefully authorized.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the specified port has been authorized forcefully using the dot1x port-control
forced-authorized command.

Recommended
Action

No action is required.

DOT1-1009
Message

802.1X is disabled for port .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that 802.1X is disabled on the specified port.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

275

5

DOT1-1010

DOT1-1010
Message

Port  is set in auto mode.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the specified port is set to auto mode.

Recommended
Action

No action is required.

276

Fabric OS Message Reference
53-1002749-01

ECC-1000

5

ECC Messages
ECC-1000
Message

Message Type
Severity

ECC Error 
occurrence of .

LOG
ERROR

Probable Cause

Indicates that the processor memory controller has detected one of the several types of double data rate
(DDR) memory errors. Single bit errors are corrected, but other errors indicate either software errors or
problems with the target system DRAM. Single bit errors can be expected to occur infrequently and can
be caused by uncontrollable external events like cosmic rays, but frequent single bit errors can be
indications of a degrading DRAM device.

Recommended
Action

Frequent single bit errors and all other error types should be reported to technical support for further
action.

ECC-1001
Message

Message Type
Severity

ECC Error 
detected.

LOG
ERROR

Probable Cause

Indicates that the processor memory controller has detected one of the several types of double data rate
(DDR) memory errors. Single bit errors are corrected, but other errors indicate either software errors or
problems with the target system DRAM. Single bit errors can be expected to occur infrequently and can
be caused by uncontrollable external events like cosmic rays, but frequent single bit errors can be
indications of a degrading DRAM device.

Recommended
Action

Frequent single bit errors and all other error types should be reported to technical support for further
action.

Fabric OS Message Reference
53-1002749-01

277

5

EM-1001

EM Messages
EM-1001
Message
Message Type
Severity

 is overheating: Shutting down.

FFDC | LOG
CRITICAL

Probable Cause

Indicates that the specified field-replaceable unit (FRU) is shutting down due to overheating. This event
is typically due to a faulty fan and can also be caused by the switch environment.

Recommended
Action

Verify that the location temperature is within the operational range of the switch. Refer to the Hardware
Reference Manual for the environmental temperature range of your switch.
Execute the fanShow command to verify that all fans are running at normal speeds. If any fans are
missing or not performing at high enough speed, they should be replaced.

EM-1002
Message
Message Type
Severity

System fan(s) status .

LOG | FFDC
INFO

Probable Cause

Indicates that a non-bladed system has overheated and may shutdown. All fan speeds are dumped to
the console.

Recommended
Action

Verify that the location temperature is within the operational range of the switch. Refer to the Hardware
Reference Manual for the environmental temperature range of your switch.
Execute the fanShow command to verify that all fans are running at normal speeds. If any fans are
missing or are not performing at a high enough speed, they should be replaced.

EM-1003
Message
Message Type
Severity

 has unknown hardware identifier: FRU faulted.

FFDC | LOG
CRITICAL

Probable Cause

Indicates that a field-replaceable unit (FRU) header could not be read or is not valid. The FRU is faulted.

Recommended
Action

Execute the diagPost command to make sure that Power-On Self-Test (POST) is enabled; then power
cycle the blade by using the slotPowerOff and slotPowerOn commands or have the blade's ejector
switch cycled to run POST and verify that the blade does not have any hardware problems.
For the Brocade 300 and 6510, replace the switch.

278

Fabric OS Message Reference
53-1002749-01

EM-1004

5

EM-1004
Message
Message Type
Severity
Probable Cause

 failed to power on.

FFDC | LOG
CRITICAL
Indicates that the specified field-replaceable unit (FRU) failed to power on and is not being used.
The FRU ID value is composed of a FRU type string and an optional number to identify the unit, slot, or
port.
The Brocade 300 switch has 4 fans and 1 power supply, but these parts cannot be replaced: the entire
switch is a FRU.

Recommended
Action

Reseat the FRU. If the problem persists, replace the FRU.

EM-1005
Message
Message Type
Severity

 has faulted. Sensor(s) above maximum limits.

FFDC | LOG
CRITICAL

Probable Cause

Indicates that a blade in the specified slot or the switch (for non-bladed switches) is shutdown for
environmental reasons; its temperature or voltage is out of range.

Recommended
Action

Check the environment and make sure the room temperature is within the operational range of the
switch. Execute the fanShow command to verify fans are operating properly. Make sure there are no
blockages of the airflow around the chassis. If the temperature problem is isolated to the blade itself,
replace the blade.
Voltage problems on a blade are likely a hardware problem on the blade itself; replace the blade.

EM-1006
Message
Message Type
Severity

 has faulted. Sensor(s) below minimum limits.

FFDC | LOG
CRITICAL

Probable Cause

Indicates that the voltage on a switch is below minimum limits. The switch or specified blade is being
shutdown for environmental reasons; the voltage is too low.

Recommended
Action

If this problem occurs on a blade, it usually indicates a hardware problem on the blade; replace the
blade.
If this problem occurs on a switch, it usually indicates a hardware problem on the main board; replace the
switch.

Fabric OS Message Reference
53-1002749-01

279

5

EM-1008

EM-1008
Message

Message Type
Severity

Unit in  with ID  is faulted, it is incompatible
with the  configuration, check FOS firmware version as a
possible cause.

FFDC | LOG
CRITICAL

Probable Cause

Indicates that a blade inserted in the specified slot or the switch (for non-bladed switches) is not
compatible with the platform configuration (includes the firmware version) or the switch configuration.
The blade is faulted.

Recommended
Action

If the blade is incompatible, upgrade the firmware or replace the blade and make sure the replacement
blade is compatible with your control processor (CP) type and firmware.
If the incompatibility is with the logical switch configuration, change the configuration by using the lscfg
command to be consistent with the blade type, or remove the blade.

EM-1009
Message
Message Type
Severity

 powered down unexpectedly.

FFDC | LOG
CRITICAL

Probable Cause

Indicates that the environmental monitor (EM) received an unexpected power-down notification from the
specified field-replaceable unit (FRU). This may indicate a hardware malfunction in the FRU.

Recommended
Action

Reseat the FRU. If the problem persists, replace the FRU.

EM-1010
Message
Message Type
Severity

Received unexpected power down for  But  still has power.

FFDC | LOG
CRITICAL

Probable Cause

Indicates that the environmental monitor (EM) received an unexpected power-down notification from the
specified field-replaceable unit (FRU). However, the specified FRU still appears to be powered up after
four seconds.

Recommended
Action

Reseat the blade. If the problem persists, replace the blade.

280

Fabric OS Message Reference
53-1002749-01

EM-1011

5

EM-1011
Message
Message Type
Severity

Received unexpected power down for , but cannot determine if it has power.

FFDC | LOG
CRITICAL

Probable Cause

Indicates that the environmental monitor (EM) received an unexpected power-down notification from the
specified field-replaceable unit (FRU). However, after four seconds, it cannot be determined if it has
powered down or not.

Recommended
Action

Reseat the blade. If the problem persists, replace the blade.

EM-1012
Message
Message Type
Severity

 failed  state transition, unit faulted.

FFDC | LOG
CRITICAL

Probable Cause

Indicates that a switch blade or non-bladed switch failed to transition from one state to another. It is
faulted. The specific failed target state is displayed in the message. There are serious internal Fabric OS
configuration or hardware problems on the switch.

Recommended
Action

Reseat the specified field-replaceable unit (FRU).
If the problem persists, restart or power cycle the switch.
Execute the diagPost command to make sure that Power-On Self-Test (POST) is enabled; then power
cycle the blade by using the slotPowerOff and slotPowerOn commands or have the blade's ejector
switch cycled to run POST and verify that the blade does not have any hardware problems.
If the problem still persists, replace the FRU.

EM-1013
Message
Message Type
Severity

Failed to update FRU information for .

LOG
ERROR

Probable Cause

Indicates that the environmental monitor (EM) was unable to update the time alive or original equipment
manufacturer (OEM) data in the memory of a field-replaceable unit (FRU).

Recommended
Action

If you executed the fruInfoSet command, execute the command again; otherwise, the update is
automatically attempted again. If it continues to fail, reseat the FRU.
If the problem persists, replace the FRU.

Fabric OS Message Reference
53-1002749-01

281

5

EM-1014

EM-1014
Message
Message Type
Severity

Unable to read sensor on  ().

LOG
ERROR

Probable Cause

Indicates that the environmental monitor (EM) was unable to access the sensors on the specified
field-replaceable unit (FRU).

Recommended
Action

Reseat the FRU. If the problem persists, replace the FRU.

EM-1015
Message
Message Type
Severity

Warm recovery failed ().

LOG
WARNING

Probable Cause

Indicates that a problem was discovered when performing consistency checks during a warm boot.

Recommended
Action

Monitor the switch. If the problem persists, restart or power cycle the switch.

EM-1016
Message
Message Type
Severity

Cold recovery failed ().

LOG
WARNING

Probable Cause

Indicates that a problem was discovered when performing consistency checks during a cold boot.

Recommended
Action

Monitor the switch.

282

If the problem persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

Fabric OS Message Reference
53-1002749-01

EM-1017

5

EM-1017
Message
Message Type
Severity

Uncommitted WWN change detected. Cold reboot required.

LOG
WARNING

Probable Cause

Indicates that a user did not commit a changed World Wide Name (WWN) value before performing a
system restart, power cycle, or firmware download operation.

Recommended
Action

Change and commit the new WWN value.

EM-1018
Message
Message Type
Severity

CP blade in slot  failed to retrieve current chassis type (//0x).

FFDC | LOG
CRITICAL

Probable Cause

Indicates that there was a failure to read the chassis type from the system.

Recommended
Action

Verify that the control processor (CP) blade is operational and is properly seated in its slot.

EM-1019
Message
Message Type
Severity

Current chassis configuration option ()
is not compatible with standby firmware version (Pre 4.4), cannot allow HA Sync.

LOG
WARNING

Probable Cause

Indicates that the current chassis configuration option is not supported by the firmware on the standby
control processor (CP). This is true even if the standby CP comes up and is operational. High availability
(HA) synchronization of the CPs will not be allowed.

Recommended
Action

Change the chassis configuration option to 1 using the chassisConfig command, or upgrade the
firmware on the standby CP to the version running on the active CP.

Fabric OS Message Reference
53-1002749-01

283

5

EM-1020

EM-1020
Message
Message Type
Severity

Unit in  with ID  is faulted, it's an FCoE blade and the
Ethernet switch service is not enabled. Please run .

FFDC | LOG
ERROR

Probable Cause

Indicates that a blade inserted in the specified slot requires the Ethernet switch service, which is not
enabled. The blade is faulted.

Recommended
Action

Execute the fosconfig --enable ethsw command to enable the Ethernet switch service. Note that this is
a disruptive command, which requires the system to be restarted. Otherwise, remove the blade.

EM-1028
Message
Message Type
Severity
Probable Cause

HIL Error:  failed to access history log for FRU:  (rc=).

FFDC | LOG
WARNING
Indicates a problem accessing the data on the World Wide Name (WWN) card field-replaceable unit
(FRU) or the 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 record
an event for the specified FRU. The return code is for internal use only. This 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, or
port.

Recommended
Action

If the problem persists, restart or power cycle the switch.
If the problem still persists, replace the WWN card, or the switch (for non-bladed switches).

EM-1029
Message

Message Type
Severity
Probable Cause

284

, a problem occurred accessing a device on the I2C bus ().
Operational status () not changed,
access is being retried.

LOG
WARNING
Indicates that the Inter-Integrated Circuit (I2C) bus had problems and a timeout occurred.

Fabric OS Message Reference
53-1002749-01

EM-1031

Recommended
Action

5

This is often a transient error.
Watch for the EM-1048 message, which indicates that the problem has been resolved.
If the problem persists, check for loose or dirty connections. Remove all dust and debris before reseating
the field-replaceable unit (FRU). If it continues to fail, replace the FRU.

EM-1031
Message
Message Type
Severity

 ejector not closed.

LOG
ERROR

Probable Cause

Indicates that the environmental monitor (EM) has found a switch blade that is inserted, but at least one
ejector switch is not latched. The blade in the specified slot is treated as not inserted.

Recommended
Action

Close the ejector switch (raise the slider in most blades or completely screw in the upper thumbscrew) if
the field-replaceable unit (FRU) is intended for use. Refer to the appropriate Hardware Reference
Manual for instructions on inserting the switch blades.

EM-1033
Message
Message Type
Severity

CP in  set to faulty because CP ERROR asserted.

LOG
ERROR

Probable Cause

Indicates that the standby control processor (CP) has been detected as faulty. The high availability (HA)
feature will not be available. This message occurs every time the other CP restarts, even as part of a
clean warm failover. In most situations, this message is followed by the EM-1047 message, and no
action is required for the standby CP; however, find the reason for failover.

Recommended
Action

If the standby CP was restarted, wait for the error to clear (execute the slotShow command to determine
if it has cleared). Watch for the EM-1047 message to verify that this error has cleared.
If the standby CP continues to be faulty or if it was not intentionally restarted, check the error logs on the
other CP (using the errDump command) to determine the cause of the error state.
Reseat the field-replaceable unit (FRU). If the problem persists, replace the FRU.

EM-1034
Message
Message Type
Severity
Probable Cause

 set to faulty, rc=.

LOG
ERROR
Indicates that the specified field-replaceable unit (FRU) has been marked as faulty for the specified
reason.

Fabric OS Message Reference
53-1002749-01

285

5

EM-1035

Recommended
Action

Reseat the FRU.
Execute the diagPost command to make sure that Power-On Self-Test (POST) is enabled; then power
cycle the blade by using the slotPowerOff and slotPowerOn commands or have the blade's ejector
switch cycled to run POST and verify that the blade does not have any hardware problems.
If the problem persists, replace the FRU.

EM-1035
Message
Message Type
Severity
Probable Cause

2 circuit paired Power Supplies are faulty, please check the  AC main
switch/circuit to see if it has power.

LOG
ERROR
Indicates that both power supplies associated with one of the two main circuits are present but faulty, the
circuit's switch may have been turned off, or the AC power source has been interrupted for that circuit.
The Switch side value designates the circuit switch facing the cable side of the chassis, and is one of the
following values:

•
•
Recommended
Action

left - Controls the odd-numbered power supply units.
right - Controls the even-numbered power supply units.

Verify that the identified AC circuit switch is turned on, the power cord is properly attached and
undamaged, and the power source is operating properly.

EM-1036
Message
Message Type
Severity
Probable Cause

 is not accessible.

LOG
WARNING
Indicates that the specified field-replaceable unit (FRU) is not present on the switch.
If the FRU is a World Wide Name (WWN) card, the default WWN and IP addresses are used for the
switch.

Recommended
Action

Reseat the FRU.
If the problem persists, restart or power cycle the switch.
Execute the diagPost command to make sure that Power-On Self-Test (POST) is enabled; then power
cycle the blade by using the slotPowerOff and slotPowerOn commands or have the blade's ejector
switch cycled to run POST and verify that the blade does not have any hardware problems.
If the problem still persists, replace the FRU.

286

Fabric OS Message Reference
53-1002749-01

EM-1037

5

EM-1037
Message

 is no longer faulted.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the specified power supply is no longer marked faulty; probably because its AC power
supply has been turned on.

Recommended
Action

No action is required.

EM-1042
Message
Message Type
Severity

Important FRU header data for  is not valid.

LOG
WARNING

Probable Cause

Indicates that the specified field-replaceable unit (FRU) has an incorrect number of sensors in its FRU
header-derived information. This could mean that the FRU header was corrupted or read incorrectly, or
corrupted in the object database, which contains information about all FRUs.

Recommended
Action

Reseat the FRU. If the problem persists, replace the FRU.

EM-1043
Message
Message Type
Severity

Can't power  .

LOG
WARNING

Probable Cause

Indicates that the specified field-replaceable unit (FRU) cannot be powered on or off.

Recommended
Action

The specified FRU is not responding to the commands and should be replaced.

Fabric OS Message Reference
53-1002749-01

287

5

EM-1044

EM-1044
Message
Message Type
Severity

Can't power on , its logical switch is shut down.

LOG
WARNING

Probable Cause

Indicates that the specified field-replaceable unit (FRU) cannot be powered on because the associated
logical switch is shutdown.

Recommended
Action

Execute the switchStart command on the associated logical switch.

EM-1045
Message
Message Type
Severity
Probable Cause

Recommended
Action

 is being powered .

LOG
WARNING
Indicates that an automatic power adjustment is being made because of the (predicted) failure of a power
supply or the insertion or removal of a port blade. The new state value can be one of the following values:

•

On - A port blade is being powered on because the power is available (a power supply was
inserted or a port blade was removed or powered down).

•

Off - A port blade has been powered down because of the (predicted) failure of the power
supply.

•

Down - A newly inserted port blade was not powered on because there was not enough power
available.

The Brocade 24000 requires only a single power supply for a fully populated chassis; however, you must
always operate the system with at least two power supplies for redundancy.

EM-1046
Message
Message Type
Severity
Probable Cause

288

Error status received for blade ID  for the blade in slot ,
.

LOG
WARNING
Indicates that the specified blade is incompatible.

Fabric OS Message Reference
53-1002749-01

EM-1047

Recommended
Action

5

If the blade ID listed is incorrect, the field-replaceable unit (FRU) header for the blade is corrupted and
the blade must be replaced.
If the error is due to the platform, the blade ID listed is not supported for that platform (CP) type. Remove
the blade from the chassis.
If the error is due to the backplane, the CP type (CP256) is not supported on that chassis (backplane
revision D2). Remove the blade from the chassis.
If the error is due to the switch configuration, the logical switch configuration of the blade is incorrect.
Execute the lscfg command to correct the switch or port configuration for the ports on the blade.

EM-1047
Message

CP in slot  not faulty, CP ERROR deasserted.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the control processor (CP) is no longer faulted. This message usually follows the EM-1033
message. The new standby CP is in the process of restarting and has turned off the CP_ERR signal.

Recommended
Action

No action is required.

EM-1048
Message

 I2C access recovered: state .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the Inter-Integrated Circuit (I2C) bus problems have been resolved and I2C access to the
field-replaceable unit (FRU) has become available again.

Recommended
Action

No action is required. The EM-1048 message is displayed when the EM-1029 error is resolved.

EM-1049
Message

FRU  insertion detected.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that a field-replaceable unit (FRU) of the type and location specified by the FRU ID value was
detected as having been inserted into the chassis.

Fabric OS Message Reference
53-1002749-01

289

5

EM-1050

Recommended
Action

No action is required.

EM-1050
Message

FRU  removal detected.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that a field-replaceable unit (FRU) of the type and location specified by the FRU ID value was
removed from the chassis.

Recommended
Action

Verify that the FRU was intended to be removed. If not, replace the FRU as soon as possible.

EM-1051
Message

: Inconsistency detected, FRU reinitialized.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that an inconsistent state was found in the field-replaceable unit (FRU). This occurs if the state
of the FRU was changing during a failover. The FRU is reinitialized and the traffic may have been
disrupted.

Recommended
Action

No action is required.

EM-1057
Message
Message Type
Severity

Blade: is getting reset:.

LOG
WARNING

Probable Cause

Indicates that the blade is being automatically reset because of known resetable transient errors such as
an application-specific integrated circuit (ASIC) parity error.

Recommended
Action

No action is required if the switch does not reach the reset threshold for the switch or blade. If the reset
threshold is reached on the switch or blade, the switch or blade will be faulted and should be replaced.

290

Fabric OS Message Reference
53-1002749-01

EM-1058

5

EM-1058
Message
Message Type
Severity

Switch gets reset:.

LOG
WARNING

Probable Cause

Indicates that the switch is being automatically reset because of a known resetable transient problem
such as an application-specific integrated circuit (ASIC) parity error.

Recommended
Action

No action is required if the switch does not reach the reset threshold for the switch or blade. If the reset
threshold is reached on the switch or blade, the switch or blade will be faulted and should be replaced.

EM-1059
Message
Message Type
Severity
Probable Cause

 with ID  may not be supported on this platform,
check FOS firmware version as a possible cause.

LOG
ERROR
Indicates that a a blade inserted in the specified slot or the switch (for non-bladed switches) is
incompatible with the switch configuration software. The blade will not be completely usable.
The blade may only be supported by a later (or earlier) version of the firmware.

Recommended
Action

Change the control processor (CP) firmware or replace the blade. Make sure the replacement is
compatible with your switch type and firmware.

EM-1060
Message
Message Type
Severity

Stopping synchronization of the system due to blade incompatibility with software
version on standby CP.

LOG
WARNING

Probable Cause

Indicates that a blade in the system is not supported by the firmware on the standby control processor
(CP).

Recommended
Action

Remove all blades of this type or upgrade the standby CP. After an appropriate action is taken, restart the
standby CP or execute the haSyncStart command to enable the high availability (HA) state
synchronization. Until this is done, the system will remain out of synchronization.

Fabric OS Message Reference
53-1002749-01

291

5

EM-1061

EM-1061
Message
Message Type
Severity

Synchronization halted. Remove all blades of type  or upgrade your
standby CP, then reboot or run haSyncStart.

LOG
WARNING

Probable Cause

Indicates that the blade in the system is not supported by the firmware on the standby control processor
(CP).

Recommended
Action

Remove all blades of the specified type or upgrade the standby CP. After an appropriate action is taken,
restart the standby CP or execute the haSyncStart command to enable the high availability (HA) state
synchronization. Until this is done, the system will remain out of synchronization.

EM-1062
Message
Message Type
Severity

Blade in slot  faulted as it exceeds the maximum support limit of 
blades with Blade ID  in the chassis.

LOG
CRITICAL

Probable Cause

Indicates that too many blades of a particular type are in the system.

Recommended
Action

Remove the faulted blade.

EM-1063
Message
Message Type
Severity

Blade in slot  faulted because it exceeds the maximum support limit of
 blades with Blade IDs  in the chassis.

LOG
CRITICAL

Probable Cause

Indicates that too many blades of a set of particular types are in the system.

Recommended
Action

Remove the faulted blade.

292

Fabric OS Message Reference
53-1002749-01

EM-1064

5

EM-1064
Message
Message Type
Severity

Blade: is being powered off (based on user configuration) upon receiving
a HW ASIC ERROR, reason:.

LOG
CRITICAL

Probable Cause

Indicates that the blade is being powered off because a hardware (HW) application-specific integrated
circuit (ASIC) error was detected, and you have selected to power off the problem blade when such a
condition occurred.

Recommended
Action

Contact your switch service provider for assistance.

EM-1065
Message
Message Type
Severity

SAS Virtualization Services are not available due to incompatibility between the
FOS and SAS versions.

LOG
WARNING

Probable Cause

Indicates that the version of the control processor firmware (CFOS) or the blade processor firmware
(BFOS) is not compatible with the Storage Application Services (SAS) or other application firmware
versions.

Recommended
Action

Upgrade the Fabric OS firmware or the SAS firmware by using the firmwareDownload command. Refer
to the release notes for a compatible version of firmware.

EM-1066
Message

SAS Virtualization Services are now available .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the previously incompatible Fabric OS or Storage Application Services (SAS) firmware has
been upgraded and is now compatible.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

293

5

EM-1067

EM-1067
Message
Message Type
Severity

Stopping synchronization of the system due to  incompatibility with
standby CP.

LOG
WARNING

Probable Cause

Indicates that the software version on the standby control processor (CP) is incompatible with this
software feature enabled on this Fabric OS firmware version.

Recommended
Action

Upgrade the software on the standby CP or disable the software feature on this CP.
To disable the Ethernet switch service, execute the fosconfig --disable ethsw command.
To view the buffer optimization mode for the slots, execute the bufopmod --showall command, and then
execute the bufopmode --reset slot command to disable the feature for those slots before downgrading.
To disable FC8-16 Serdes tuning mode, execute the serdestunemode --reset command.

EM-1068
Message
Message Type
Severity

High Availability Service Management subsystem failed to respond. A required
component is not operating.

FFDC | LOG
ERROR

Probable Cause

Indicates that the high availability (HA) subsystem has not returned a response within four minutes of the
request from the environmental monitor (EM). It usually indicates that some component has not started
properly or has terminated. The specific component that has failed may be indicated in other messages
or debug data. There are serious internal Fabric OS configuration or hardware problems on the switch.

Recommended
Action

Restart or power cycle the switch.
If the problem persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

EM-1069
Message

Slot  is being powered off.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the blade in the specified slot is being intentionally powered off.

Recommended
Action

No action is required.

294

Fabric OS Message Reference
53-1002749-01

EM-1070

5

EM-1070
Message

Slot  is being powered on.

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the blade in the specified slot is being intentionally powered on.

Recommended
Action

No action is required.

EM-1071
Message
Message Type
Severity

Unit in  with ID  is faulted, it is incompatible with the
following blade id(s): .

FFDC | LOG
CRITICAL

Probable Cause

Indicates that a blade inserted in the specified slot is incompatible with another blade in the system.

Recommended
Action

Determine which blade is essential to your configuration and remove blades that are incompatible with it.

EM-1072
Message
Message Type
Severity

Chassis cannot become ready since no Core Blades are available.

FFDC | LOG
CRITICAL

Probable Cause

Indicates that all core blades are either missing, faulted, or powered off. There must be at least one core
blade in enabled state for the chassis to be considered ready.

Recommended
Action

Insert and close the ejector switch on missing core blades. Reseat or replace core blades that are faulted
or powered off.

Fabric OS Message Reference
53-1002749-01

295

5

EM-2003

EM-2003
Message
Message Type
Severity

 has failed the POST tests. FRU is being
faulted.

LOG
ERROR

Probable Cause

Indicates that a field-replaceable unit (FRU) has failed the Power-On Self-Test (POST). Refer to the
/tmp/post[1/2].slot#.log file for more information on the faults. To view this log file, you must be logged in
at the root level. The ID will be Switch for non-bladed systems.

Recommended
Action

On bladed systems, reseat the specified FRU.
On non-bladed switches, restart or power cycle the switch.
If the problem persists, perform the following actions:

296

•

Execute the diagPost command to make sure that Power-On Self-Test (POST) is enabled; then
power cycle the blade by using the slotPowerOff and slotPowerOn commands or have the
blade's ejector switch cycled to run POST and verify that the blade does not have any hardware
problems.

•

On bladed systems, replace the specified FRU; otherwise, replace the switch.

Fabric OS Message Reference
53-1002749-01

ESS-1001

5

ESS Messages
ESS-1001
Message
Message Type
Severity

A few switches in the fabric do not support the Coordinated HotCode protocol.

LOG
WARNING

Probable Cause

Indicates one or more switches in the fabric do not support the Coordinated HotCode protocol.
Continuing with the firmware download may cause data traffic disruption.

Recommended
Action

Discontinue the firmware download, identify the down-level switch or switches that do not support the
Coordinated HotCode protocol, and upgrade the down-level switches. Then, restart the firmware
download on this switch. Note that upgrading a down-level Brocade switch in a mixed interop fabric may
still cause data traffic disruption.

ESS-1002
Message
Message Type
Severity

The pause message is rejected by the domain .

LOG
WARNING

Probable Cause

Indicates that during the Coordinated HotCode protocol, a switch in the fabric has rejected the pause
message which prevented the protocol from completing. Any data traffic disruption observed during the
firmware download may have been due to the rejected pause message.

Recommended
Action

No action is required.

ESS-1003
Message
Message Type
Severity

The pause retry count is exhausted for the domain .

LOG
WARNING

Probable Cause

Indicates that during the Coordinated HotCode protocol, a switch in the fabric did not accept the pause
message which prevented the protocol from completing. Any data traffic disruption observed during the
firmware download may have been due to this issue.

Recommended
Action

No action is required.

Fabric OS Message Reference
53-1002749-01

297

5

ESS-1004

ESS-1004
Message
Message Type
Severity

The resume message is rejected by the domain .

LOG
WARNING

Probable Cause

Indicates that during the Coordinated HotCode protocol, a switch in the fabric has rejected the resume
message which prevented the protocol from completing. Any data traffic disruption observed during the
firmware download may have been due to the rejected resume message.

Recommended
Action

No action is required.

ESS-1005
Message
Message Type
Severity

The resume retry count is exhausted for the domain .

LOG
WARNING

Probable Cause

Indicates that during the Coordinated HotCode protocol, a switch in the fabric did not accept the resume
message which prevented the protocol from completing. Any data traffic disruption observed during the
firmware download may have been due to this issue.

Recommended
Action

No action is required.

ESS-1008
Message
Message Type
Class
Severity

Fabric Name -  configured (received from domain ).

AUDIT | LOG
FABRIC
INFO

Probable Cause

Indicates that the fabric name is configured or renamed.

Recommended
Action

No action is required.

298

Fabric OS Message Reference
53-1002749-01

ESS-1009

5

ESS-1009
Message
Message Type
Class
Severity

Fabric Name Mismatch - local() remote( - received
from domain ).

AUDIT | LOG
FABRIC
WARNING

Probable Cause

Indicates that the specified fabric name is not unique for this fabric.

Recommended
Action

Select an appropriate fabric name and set it again from any switch.

ESS-1010
Message
Message Type
Class
Severity

Duplicate Fabric Name -  matching with FID .

AUDIT | LOG
FABRIC
WARNING

Probable Cause

Indicates that the configured fabric name is already used for another partition.

Recommended
Action

Select a different fabric name and reconfigure.

Fabric OS Message Reference
53-1002749-01

299

5

ESW-1001

ESW Messages
ESW-1001
Message
Message Type
Severity

Switch is not in ready state - Switch enable failed, switch status= 0x, c_flags = 0x.

LOG
ERROR

Probable Cause

Indicates that the switch enable operation has failed.

Recommended
Action

If the message persists, execute the supportFtp command (as needed) to set up automatic FTP
transfers; then execute the supportSave command and contact your switch service provider.

ESW-1002
Message

Security violation: Unauthorized device  tries to FLOGI to
port .

Message Type

LOG

Severity

INFO

Probable Cause

Indicates that the specified device is not present in the authorized profile list.

Recommended
Action

Verify that the device is authorized to log in to the switch. If the device is authorized, execute the
secPolicyDump command to verify whether the World Wide Name (WWN) of the specified device is
listed. If it is not listed, execute the secPolicyAdd command to add this device to an existing policy.

ESW-1003
Message
Message Type
Severity

Slot ENABLED but Not Ready during recovery, disabling slot = ().

LOG
ERROR

Probable Cause

Indicates that the slot state has been detected as inconsistent during failover or recovery.

Recommended
Action

For a bladed switch, execute the slotPowerOff and slotPowerOn commands to power cycle the blade.

300

For a non-bladed switch, restart or power cycle the switch.

Fabric OS Message Reference
53-1002749-01

ESW-1004

5

ESW-1004
Message
Message Type
Severity

Blade attach failed during recovery, disabling slot = .

LOG
ERROR

Probable Cause

Indicates that the specified blade has failed during failover or recovery.

Recommended
Action

For a bladed switch, execute the slotPowerOff and slotPowerOn commands to power cycle the blade.
For a non-bladed switch, restart or power cycle the switch.

ESW-1005
Message
Message Type
Severity

Diag attach failed during recovery, disabling slot = .

LOG
ERROR

Probable Cause

Indicates that the diagnostic blade attach operation has failed during failover or recovery.

Recommended
Action

For a bladed switch, execute the slotPowerOff and slotPowerOn commands to power cycle the blade.
For a non-bladed switch, restart or power cycle the switch.

ESW-1006
Message

Message Type
Severity

HA state out of sync: Standby CP (ver = ) does not support
NPIV functionality. (active ver = , NPIV devices = <'1' if
NPIV devices exist; Otherwise '0'>).

LOG
WARNING

Probable Cause

Indicates that the standby control processor (CP) does not support N_Port ID Virtualization (NPIV)
functionality, but the switch has some NPIV devices logged in to the fabric.

Recommended
Action

Load a firmware version on the standby CP that supports NPIV functionality using the
firmwareDownload command.

Fabric OS Message Reference
53-1002749-01

301

5

ESW-1007

ESW-1007
Message
Message Type
Severity

Switch port  disabled due to \"\".

LOG
WARNING

Probable Cause

Indicates that the switch port is disabled due to the reason displayed in the message.

Recommended
Action

Based on the disable reason displayed, take appropriate action to restore the port.
If the disable reason is "Insufficient frame buffers", reduce the distance or speed settings for the port to
reduce the buffer requirement of the link. Alternatively, one or more ports in the port group must be
disabled to make more buffers available for the link.
Refer to the Fabric OS Administrator's Guide for more information.

ESW-1008
Message
Message Type
Severity

 are port swapped on ports that do not support port swap. Slot  will be faulted.

LOG
WARNING

Probable Cause

Indicates that the blade is enabled with the port configuration that already has the area swapped.

Recommended
Action

Replace the blade with ports that support port swap. Then swap ports back to the port's default area.

302

Refer to the Fabric OS Administrator's Guide for more information.

Fabric OS Message Reference
53-1002749-01

EVMD-1001

5

EVMD Messages
EVMD-1001
Message
Message Type
Severity

Event could not be sent to remote proxy = .

LOG
WARNING

Probable Cause

Indicates that the event could not be sent to remote proxy. This could happen if the remote proxy switch
cannot be reached through in-band.

Recommended
Action

Make sure that the specified remote domain is present in the fabric.

Fabric OS Message Reference
53-1002749-01

303

5

FABR-1001

FABR Messages
FABR-1001
Message
Message Type
Severity

port , .

LOG
WARNING

Probable Cause

Indicates that the specified switch port is isolated because of a segmentation resulting from mismatched
configuration parameters.

Recommended
Action

Based on the segmentation reason displayed with the message, look for a possible mismatch of relevant
configuration parameters in the switches at both ends of the link.
Run the configure command to modify the appropriate switch parameters on both the local and remote
switch.

FABR-1002
Message
Message Type
Severity

fabGaid: no free multicast alias IDs.

LOG
WARNING

Probable Cause

Indicates that the fabric does not have any available multicast alias IDs to assign to the alias server.

Recommended
Action

Verify alias IDs using the fabricShow command on the principal switch.

FABR-1003
Message
Message Type
Severity
Probable Cause

304

port : ILS  bad size , wanted .

LOG
WARNING
Indicates that an internal link service (ILS) information unit of invalid size has been received. The
neighbor switch has sent a payload with an invalid size.

Fabric OS Message Reference
53-1002749-01

FABR-1004

Recommended
Action

5

Investigate the neighbor switch for problems. Run the errShow command on the neighbor switch to view
the error log for additional messages.
Check for a faulty cable or deteriorated small form-factor pluggable (SFP). Replace the cable or the SFP
if necessary.
Run the portLogDumpPort command on both the receiving and transmitting ports.
Run the fabStatsShow command on both the receiving and transmitting switches.
If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers;
then run the supportSave command and contact your switch service provider.

FABR-1004
Message

Message Type
Severity

port: , req iu: 0x
, state: 0x, resp iu: 0x
, state 0x, . LOG WARNING Probable Cause Indicates that the information unit response was invalid for the specified command sent. The fabric received an unknown response. This message is rare and usually indicates a problem with the Fabric OS kernel. Recommended Action If this message is due to a one-time event because of the incoming data, the system will discard the frame. If it is due to problems with the kernel, the system will recover by performing a failover. If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. FABR-1005 Message Message Type Severity : port : status 0x () xid = 0x. LOG WARNING Probable Cause Indicates that the application failed to send an async command for the specified port. The message provides additional details regarding the reason for the failure and the exchange ID of the command. This can happen if a port is about to go down. Recommended Action No action is required. This message is often transitory. If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Fabric OS Message Reference 53-1002749-01 305 5 FABR-1006 FABR-1006 Message Message Type Severity Node free error, caller: . LOG WARNING Probable Cause Indicates that the Fabric OS is trying to free or deallocate memory space that has already been deallocated. This message is rare and usually indicates a problem with the Fabric OS. Recommended Action In case of severe memory corruption, the system may recover by performing an automatic failover. If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. FABR-1007 Message Message Type Severity IU free error, caller: . LOG WARNING Probable Cause Indicates that a failure occurred when deallocating an information unit. This message is rare and usually indicates a problem with the Fabric OS. Recommended Action In case of severe memory corruption, the system may recover by performing an automatic failover. If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. FABR-1008 Message Message Type Severity Probable Cause . LOG WARNING Indicates that errors occurred during the request domain ID state; the information unit cannot be allocated 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 Fabric OS. The error descriptions are as follows: • • Recommended Action 306 FAB RDI: cannot allocate IU FAB RDI: cannot send IU No action is required if the message appears with the FABR-1005 message. If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Fabric OS Message Reference 53-1002749-01 FABR-1009 5 FABR-1009 Message Message Type Severity . LOG WARNING Probable Cause Indicates that errors were reported during the exchange fabric parameter state; cannot allocate domain list due to a faulty exchange fabric parameter (EFP) type. This message is rare and usually indicates a problem with the Fabric OS. Recommended Action The fabric daemon will discard the EFP. The system will recover through the EFP retrial process. If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. FABR-1010 Message Message Type Severity . LOG WARNING Probable Cause Indicates that errors occurred while cleaning up the request domain ID (RDI). The error description provides further details. This message is rare and usually indicates a problem with the Fabric OS. Recommended Action If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. FABR-1011 Message Message Type Severity . LOG | FFDC ERROR Probable Cause Indicates that the Fabric OS is unable to inform the Fabric OS State Synchronization Management module (FSSME) that the fabric is stable or unstable. This message is rare and usually indicates a problem with the Fabric OS. Recommended Action If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Fabric OS Message Reference 53-1002749-01 307 5 FABR-1012 FABR-1012 Message Message Type Severity : no such type, . LOG WARNING Probable Cause Indicates that the fabric is not in the appropriate state for the specified process. This message is rare and usually indicates a problem with the Fabric OS. Recommended Action The fabric daemon will take proper action to recover from the error. If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. FABR-1013 Message Message Type Severity No Memory: pid= file= line=. FFDC | LOG CRITICAL Probable Cause Indicates that there is not enough memory in the switch for the fabric module to allocate. This message is rare and usually indicates a problem with the Fabric OS. Recommended Action The system will recover by failing over to the standby CP. If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. FABR-1014 Message Message Type Severity Port Disabled: Insistent Domain ID could not be obtained. Principal Assigned Domain ID = . LOG ERROR Probable Cause Indicates that the specified port received a request domain ID (RDI) accept message containing a principal-switch-assigned domain ID that is different from the insistent domain ID (IDID). Fibre connectivity (FICON) mode requires an insistent domain ID. If an RDI response has a different domain ID, then the port is disabled. Recommended Action Run the configShow command to view the fabric.ididmode. A 0 means the IDID mode is disabled; a 1 means it is enabled. Set the switch to insistent domain ID mode. This mode is set under the configure command or in Web Tools on the Switch Admin > Configure window. 308 Fabric OS Message Reference 53-1002749-01 FABR-1015 5 FABR-1015 Message Message Type Severity FICON Insistent DID max retry exceeded: All E_Ports will be disabled. Switch is isolated. LOG ERROR Probable Cause Indicates that the application exceeded request domain ID (RDI) requests for the insistent domain ID. All E_Ports are disabled; isolating the specified switch from the fabric. Recommended Action Verify that the insistent domain ID is unique in the fabric and then re-enable the E_Ports. Run the fabricShow command to view the domain IDs across the fabric and the configure command to change the insistent domain ID mode. Refer to the Fabric OS Command Reference for more information on these commands. FABR-1016 Message Message Type Severity ficonMode is enabled. LOG WARNING Probable Cause Indicates that FICON mode is enabled on the switch through a user interface command. Recommended Action No action is required. FABR-1017 Message Message Type Severity ficonMode is disabled. LOG WARNING Probable Cause Indicates that FICON mode is disabled on the switch through a user interface command. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 309 5 FABR-1018 FABR-1018 Message Message Type Severity Probable Cause PSS principal failed (: ). LOG WARNING Indicates that a failure occurred when trying to set the principal switch using the fabricPrincipal command. The message notifies you that the switch failed to become the principal switch because of one of the following reasons: • • Recommended Action The switch joined an existing fabric and bypassed the F0 state. The fabric already contains a principal switch that has a lower World Wide Name (WWN). Make sure that no other switch is configured as the principal switch. Force a fabric rebuild by using the switchDisable and switchEnable commands. Refer to the Fabric OS Command Reference for more information about the fabricPrincipal command. FABR-1019 Message Message Type Severity Critical fabric size () exceeds supported configuration (). FFDC | LOG CRITICAL Probable Cause Indicates that this switch is a value-line switch and has exceeded the limited fabric size: that is, a specified limit to the number of domains. This limit is defined by your specific value-line license key. The fabric size has exceeded this specified limit, and the grace period counter has started. If the grace period is complete and the size of the fabric is still outside the specified limit, Web Tools is disabled. Recommended Action Bring the fabric size within the licensed limits. Either a full fabric license must be added or the size of the fabric must be changed to within the licensed limit. Contact your switch provider to obtain a full fabric license. FABR-1020 Message Message Type Severity Probable Cause 310 Web Tools will be disabled in days hours and minutes. FFDC | LOG CRITICAL Indicates that this switch has a value-line license and has a limited number of domains. If more than the specified number of domains are in the fabric, a counter is started to disable Web Tools. This message displays the number of days left in the grace period. After this time, Web Tools is disabled. Fabric OS Message Reference 53-1002749-01 FABR-1021 Recommended Action 5 Bring the fabric size within the licensed limits. Either a full fabric license must be added or the size of the fabric must be changed to within the licensed limit. Contact your switch provider to obtain a full fabric license. FABR-1021 Message Message Type Severity Web Tools is disabled. FFDC | LOG CRITICAL Probable Cause Indicates that this switch has a value-line license and has a limited number of domains. If more than the specified number of domains are in the fabric, a counter is started to disable Web Tools. This grace period has expired and Web Tools has been disabled. Recommended Action Bring the fabric size within the licensed limits. Either a full fabric license must be added or the size of the fabric must be changed to within the licensed limit. Contact your switch provider to obtain a full fabric license. FABR-1022 Message Message Type Severity Fabric size () exceeds supported configuration (). Fabric limit timer () started from . FFDC | LOG CRITICAL Probable Cause Indicates that the fabric size has exceeded the value-line limit, and the grace period counter has started. If the grace period is complete and the size of the fabric is still outside the specified limit, Web Tools is disabled. Recommended Action Bring the fabric size within the licensed limits. Either a full fabric license must be added or the size of the fabric must be changed to within the licensed limit. Contact your switch provider to obtain a full fabric license. FABR-1023 Message Fabric size is within supported configuration (). Fabric limit timer () stopped at . Message Type LOG Severity INFO Probable Cause Indicates that the fabric size is within specified limits. Either a full fabric license was added or the size of the fabric was changed to within the licensed limit. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 311 5 FABR-1024 FABR-1024 Message Initializing fabric size limit timer . Message Type LOG Severity INFO Probable Cause Indicates that the fabric size has exceeded the limit set by your value-line switches. Value-line switches have a limited fabric size (for example, a specified limit on the number of domains). This value is defined by your specific value-line license key. The fabric size has exceeded this specified limit. The grace period timer has been initialized. If the grace period is complete and the size of the fabric is still outside the specified limit, Web Tools is disabled. Recommended Action Bring the fabric size within the licensed limits. Either a full fabric license must be added or the size of the fabric must be changed to within the licensed limit. Contact your switch provider to obtain a full fabric license. FABR-1029 Message Port negotiated (mode = ). Message Type LOG Severity INFO Probable Cause Recommended Action Indicates that a different flow control mode, as described in the message, is negotiated with the port at the other end of the link. The flow control is a mechanism of throttling the transmitter port to avoid buffer overrun 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. • DUAL_CR mode: Dual-credit flow control mode. In both of the previous modes, the buffer credits are fixed, based on the port configuration information. In this mode, the buffer credits are negotiated as part of exchange link parameter (ELP) exchange. This mode also uses the R_RDY primitive for flow control. R_RDY mode: Receiver-ready flow control mode. This is the Fibre Channel standard protocol, that uses R_RDY primitive for flow control. No action is required. FABR-1030 Message fabric: Domain (was ). Message Type LOG Severity INFO Probable Cause 312 Indicates that the domain ID has changed. Fabric OS Message Reference 53-1002749-01 FABR-1031 Recommended Action 5 No action is required. FABR-1031 Message Message Type Severity Maximum number of retries sending ILS from port exceeded. LOG | FFDC WARNING Probable Cause Indicates the fabric exhausted the maximum number of retries sending internal link service (ILS) to the iswitch daemon on the specified E_Port. Recommended Action Run the top command to see if iswitchd is extremely busy or if another process is using excessive CPU resources. FABR-1032 Message Message Type Severity Remote switch with domain ID and switchname running an unsupported FOS version v2.x has joined the fabric. LOG WARNING Probable Cause Indicates that a switch with an unsupported Fabric OS version 2.x has joined the fabric. Recommended Action Remove the switch with the unsupported Fabric OS version 2.x from the fabric FABR-1034 Message Area have been acquired by port . Persistently disabling port . Message Type LOG Severity INFO Probable Cause Indicates you must enable Trunk Area on a port for another port to use the same area. Recommended Action Move the cable to a port area that is not in use, or disable Trunk Area. You must manually enable the port or the port remains disabled forever. Refer to the Fabric OS Administrator's Guide for more information. Fabric OS Message Reference 53-1002749-01 313 5 FABR-1035 FABR-1035 Message Slave area does not match Master port . Persistently disabling port . Message Type LOG Severity INFO Probable Cause Indicates the Slave port's Trunk Area differs from that of the Master port. Recommended Action Move the cable to a port to match with the same Master Trunk Area, or disable Trunk Area. You must manually enable the port or the port remains disabled forever. Refer to the Fabric OS Administrator's Guide for more information. FABR-1036 Message F_Port trunks are only allowed on Trunk Area enabled port. Persistently disabling port . Message Type LOG Severity INFO Probable Cause Indicates the specified port is being disabled because when the port on a switch is Trunk Area-enabled, it does not allow other devices like Access Gateway (AG) or HBA that are not Trunk Area-enabled. Recommended Action Move the cable to a port that does not have Trunk Area enabled. FABR-1037 Message Port configuration incompatible with Trunk Area enabled port. Persistently disabling port . Message Type LOG Severity INFO Probable Cause Indicates the specified port is being disabled because when the port attempts to go online, the switch finds the Trunk Area enabled is incompatible with port configurations such as long distance, port mirror, fast write, or EX_Port. Recommended Action Check the port configurations to disable long distance, port mirror, fast write, or EX_Port. 314 Fabric OS Message Reference 53-1002749-01 FABR-1038 5 FABR-1038 Message Trunking license not present with F port trunking enabled. Persistently disabling port . Message Type LOG Severity INFO Probable Cause Indicates the specified port is being disabled because F_Port trunking is enabled without a trunking license being present. Recommended Action Install a trunking license or disable F_Port trunking on the port. FABR-1039 Message Message Type Severity Invalid domain ID zero received from principal switch(domain id=). LOG WARNING Probable Cause Indicates an invalid domain ID zero has been received. Recommended Action Check the principal switch for the invalid domain ID zero. FABR-1040 Message Speed is not 2G, 4G, or 8G with F_Port trunking enabled. Persistently disabling port . Message Type LOG Severity INFO Probable Cause Indicates that the speed is not compatible for F_Port trunks. Recommended Action Change the speed for the port or disable F_Port trunking on the port. Fabric OS Message Reference 53-1002749-01 315 5 FABR-1041 FABR-1041 Message Message Type Severity Port is disabled due to trunk protocol error. LOG ERROR Probable Cause Indicates a link reset was received before the completion of the trunking protocol on the port. Recommended Action Enable the port by running the portEnable command. The port may recover by re-initialization of the link. If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. FABR-1043 Message Message Type Severity Detected Fabric ID conflict with remote (not neighbor) switch (domain ), FID . No local E_Ports disabled. LOG ERROR Probable Cause Indicates that the remote switch has a Fabric ID (FID) conflict with the local switch. But no ports are disabled because the remote switch is not an adjacent to the local switch. Recommended Action Make sure that all the switches in the fabric have the same FID or upgrade the switch firmware to a VF-capable firmware. FABR-1044 Message Message Type Severity Detected Fabric ID conflict with neighbor switch (domain ), FID . E_Ports () connected to the switch are disabled. LOG ERROR Probable Cause Indicates that the neighbor switch has a Fabric ID (FID) conflict with the local switch. All E_Ports directly connected to the conflicting switch are disabled. Recommended Action Make sure that all the switches in the fabric have the same FID or upgrade the switch firmware to a VF-capable firmware. 316 Fabric OS Message Reference 53-1002749-01 FABR-1045 5 FABR-1045 Message Message Type Severity Detected Base Switch conflict with remote (not neighbor) switch (domain ), BS . No local E_Ports disabled. LOG ERROR Probable Cause Indicates that the remote switch has a Base Switch attribute conflict with the local switch. But no ports are disabled because the remote switch is not an adjacent to the local switch. Recommended Action Make sure that all the switches in the fabric have the same Base Switch attribute or disable VF mode for the conflicting switch using the fosConfig command. FABR-1046 Message Message Type Severity Detected Base Switch conflict with neighbor switch (domain ), BS . E_Ports () connected to the switch are disabled. LOG ERROR Probable Cause Indicates that the remote switch has a Base Switch attribute conflict with the local switch. All the E_Ports directly connected to the conflicting switch are disabled. Recommended Action Make sure that all the switches in the fabric have the same Base Switch attribute or upgrade the switch firmware to a VF-capable firmware. FABR-1047 Message Area unavailable to assign to the port. Persistently disabling port . Message Type LOG Severity INFO Probable Cause Indicates that there are no areas available to assign to the port during port creation. Recommended Action Move some ports out of the default switch to make areas available. Fabric OS Message Reference 53-1002749-01 317 5 FABR-1048 FABR-1048 Message Message Type Severity Detected Fabric ID (FID inherited) conflict with switch (domain , FID ). LOG ERROR Probable Cause Indicates that a switch in the fabric has a Fabric ID (FID) conflict with the inherited FID of the local switch. Recommended Action Make sure that all the switches in the fabric have the same FID or upgrade the switch firmware to a VF-capable firmware. FABR-1049 Message Message Type Severity Detected Fabric ID (FID inherited) conflict with neighbor switch (domain , FID ). E_Ports () connected to the switch are disabled. LOG ERROR Probable Cause Indicates that the neighbor switch has a Fabric ID (FID) conflict with the inherited FID of the local switch. All E_Ports directly connected to the conflicting switch are disabled. Recommended Action Make sure that all the switches in the fabric have the same FID or upgrade the switch firmware to a VF-capable firmware. FABR-1050 Message license not present. F_Port trunking cannot be enabled on port(). Message Type LOG Severity INFO Probable Cause Indicates that the trunking or Server Application Optimization (SAO) license is not installed. Recommended Action Install the license required. 318 Fabric OS Message Reference 53-1002749-01 FABR-1051 5 FABR-1051 Message Message Type Severity Probable Cause D-Port test failed for slot and port . LOG ERROR Indicates that the D_Port test failed for the given slot and port due to one of the following reasons: • • • Recommended Action The small form-factor pluggable (SFP) fault detected by electrical loopback test failure. The cable fault detected by optical loopback test failure. An application-specific integrated circuit (ASIC) issue detected by link traffic test failure. Replace the faulty SFPs, cables, or blade. FABR-1052 Message The configured port speed (16G/10G on non FC16 blade or 1G on FC16 blade) is invalid. Persistently disabling port . Message Type LOG Severity INFO Probable Cause Indicates that the configured speed (16 Gbps or 10 Gbps on the non-FC16 blade or 1 Gbps on the FC16 blade) for the specified port is invalid. Recommended Action Execute the portCfgSpeed command to change the port speed. FABR-1053 Message Message Type Severity The switch is disabled due to an inconsistency found in the interop config parameters. LOG CRITICAL Probable Cause Indicates that the configuration keys have interopmode parameters such as switch.interopMode and switch.mcdtFabricmode set. Recommended Action Execute the interopmode command to reset the parameters. Fabric OS Message Reference 53-1002749-01 319 5 FABR-1054 FABR-1054 Message Message Type Severity Rebooting the standby as it received an update before port [] is expanded. LOG | FFDC INFO Probable Cause Indicates that the standby control processor (CP) did not have the port because the port expand operation is still in progress and the standby CP has received a port update. The standby CP reboots automatically to ensure sync and attain the normal state. This is a rare occurrence. Recommended Action No action is required. FABR-1055 Message F_Port trunking cannot be enabled on the slot port due to inconsistent port configuration. Message Type LOG Severity INFO Probable Cause Indicates that the specified F_Port is unable to join its assigned trunk area group because of mismatch in the port configuration with the other trunk area members. Recommended Action Check the configuration of the port with all other ports intended to be part of the same trunk group. Use the porttrunkarea --show to identify the trunk members of the specified F_Port and the portcfgshow command to identify the conflicting configuration between the trunk members. 320 Fabric OS Message Reference 53-1002749-01 FABS-1001 5 FABS Messages FABS-1001 Message Message Type Severity . FFDC | LOG CRITICAL Probable Cause Indicates that the system is low on memory and cannot allocate more memory for new operations. This is usually an internal Fabric OS problem or file corruption. The Description of memory need variable specifies the memory size that was being requested. The value can be any whole number. Recommended Action Reboot or power cycle the switch. FABS-1002 Message Message Type Severity . LOG WARNING Probable Cause Indicates that an internal problem has been detected by the software. This is usually an internal Fabric OS problem or file corruption. Recommended Action Reboot or power cycle the switch. If the message persists, run the firmwareDownload command to update the firmware. FABS-1004 Message Message Type Severity process () . LOG WARNING Probable Cause Indicates that an operation has been interrupted by a signal. This is usually an internal Fabric OS problem or file corruption. Recommended Action Reboot or power cycle the switch. Fabric OS Message Reference 53-1002749-01 321 5 FABS-1005 FABS-1005 Message Message Type Severity Probable Cause (= ). LOG WARNING Indicates that an unsupported operation has been requested. This is usually an internal Fabric OS problem or file corruption. The following is a possible value for function name and description of problem variable: fabsys_write: Unsupported write operation: process xxx In this value, xxx is the process ID (PID), which could be any whole number. Recommended Action Reboot or power cycle the active CP (for modular systems) or the switch (for single-board systems). If the message persists, run the firmwareDownload command to update the firmware. FABS-1006 Message Message Type Severity Probable Cause : object unit . LOG WARNING Indicates that there is no device in the slot with the specified object type ID in the system module record. This could indicate a serious Fabric OS data problem on the switch. The possible values for function name and description of problem variable are: • • • • • • Recommended Action 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 driver If the message is isolated, monitor the error messages on the switch. If the error is repetitive or if the fabric failed, failover or reboot the switch. If the message persists, run the firmwareDownload command to update the firmware. 322 Fabric OS Message Reference 53-1002749-01 FABS-1007 5 FABS-1007 Message Message Type Severity : Media state is invalid - status=. LOG WARNING Probable Cause Indicates that the Fabric OS has detected an invalid value in an object status field. This is usually an internal Fabric OS problem or file corruption. Recommended Action Reboot or power cycle the switch. If the message persists, run the firmwareDownload command to update the firmware. FABS-1008 Message Message Type Severity : Media oid mapping failed. LOG WARNING Probable Cause Indicates that the Fabric OS was unable to locate a necessary object handle. This is usually an internal Fabric OS problem or file corruption. Recommended Action Reboot or power cycle the switch. FABS-1009 Message Message Type Severity : type is not media. LOG WARNING Probable Cause Indicates that the Fabric OS was unable to locate an appropriate object handle. This is usually an internal Fabric OS problem or file corruption. Recommended Action Reboot or power cycle the switch. Fabric OS Message Reference 53-1002749-01 323 5 FABS-1010 FABS-1010 Message Message Type Severity : Wrong media_event . LOG WARNING Probable Cause Indicates that the Fabric OS detected an unknown event type. This is usually an internal Fabric OS problem or file corruption. Recommended Action Reboot or power cycle the switch. If the message persists, run the firmwareDownload command to update the firmware. FABS-1011 Message Message Type Severity []:Invalid input state 0x. LOG ERROR Probable Cause Indicates that an unrecognized state code was used in an internal Fabric OS message for a field-replaceable unit (FRU). Recommended Action Reboot or power cycle the CP or system. If the message persists, run the firmwareDownload command to update the firmware. FABS-1013 Message Message Type Severity Probable Cause []:Unknown blade type 0x. LOG ERROR Indicates an unrecognized type of blade has been discovered in the system. This may be caused by an incorrect field-replaceable unit (FRU) header, inability to read the FRU header, or the blade may not be supported by this platform or Fabric OS version. Recommended Action Verify that the blade is valid for use in this system and this version of Fabric OS. Reseat the blade. If this is a valid blade and reseating does not solve the problem, replace the blade. 324 Fabric OS Message Reference 53-1002749-01 FABS-1014 5 FABS-1014 Message Message Type Severity Probable Cause []:Unknown FRU type 0x. LOG ERROR Indicates an unrecognized type of field-replaceable unit (FRU) has been discovered in the system. This may be caused by an incorrect FRU header, inability to read the FRU header, or the FRU may not be supported by this platform or Fabric OS version. Recommended Action Verify that the FRU is valid for use in this system and this version of Fabric OS. Reseat the FRU. If this is a valid FRU and reseating does not solve the problem, replace the FRU FABS-1015 Message Message Type Severity []:Request to enable FRU type 0x, unit failed. err code . LOG ERROR Probable Cause Indicates the specified FRU could not be enabled. This is usually an internal Fabric OS problem. Recommended Action Remove and reinsert the FRU. Reboot or power cycle the CP or system. If the message persists, run the firmwareDownload command to update the firmware. Fabric OS Message Reference 53-1002749-01 325 5 FBC-1001 FBC Messages FBC-1001 Message Message Type Severity Firmware version on AP blade is incompatible with that on the CP. LOG ERROR Probable Cause Indicates the control processor (CP) blade determined that the firmware version running on the application processor (AP) blade is not compatible with that running on CP. The AP and CP blades cannot communicate. Recommended Action The problem can be corrected by changing the firmware version on either the CP or on the AP blade. You can modify the firmware version on the CP blade by using the firmwareDownload command. Refer to the release notes to determine whether a non-disruptive firmware download is supported between the revisions. Because the AP and CP blades cannot communicate, it is not possible to load new firmware on the AP blade. If necessary, send the AP blade back to the factory for a firmware update. 326 Fabric OS Message Reference 53-1002749-01 FCMC-1001 5 FCMC Messages FCMC-1001 Message Message Type Severity System is low on memory and has failed to allocate new memory. FFDC | LOG CRITICAL Probable Cause Indicates that the switch is low on memory and failed to allocate new memory for an information unit (IU). Recommended Action A non-bladed switch will automatically reboot. For a bladed switch, the active CP blade will automatically fail over and the standby CP will become the active CP. Fabric OS Message Reference 53-1002749-01 327 5 FCOE-1001 FCOE Messages FCOE-1001 Message Message Type Severity calloc failed for . LOG ERROR Probable Cause Indicates a memory failure. Recommended Action Check the memory usage on the switch using the memShow command. FCOE-1002 Message Message Type Severity Max logingroup limit reached at . LOG WARNING Probable Cause Indicates that too many login groups have been added. Recommended Action Check the maximum login group value displayed in the message. FCOE-1003 Message : member in another logingroup being removed. Message Type LOG Severity INFO Probable Cause Indicates that the device World Wide Name (WWN) you are trying to add is present in some other login group, and therefore it will be removed from that login group and added to the new login group. Recommended Action Check the login group changes using the fcoelogincfg --show command. 328 Fabric OS Message Reference 53-1002749-01 FCOE-1004 5 FCOE-1004 Message Message Type Severity : removing member from failed. LOG ERROR Probable Cause Indicates that removing a device from the login group has failed. Recommended Action Execute the supportSave command and restart the system. If the problem persists, contact your switch service provider. FCOE-1005 Message Message Type Severity : membership check failed in logingroup: . LOG ERROR Probable Cause Indicates that the membership check for the device has failed. Recommended Action Check the device for failed membership using the fcoelogincfg --show command. FCOE-1006 Message Message Type Severity file operation failed on for operation: errno:. LOG ERROR Probable Cause Indicates a file operation failure. Recommended Action Check the error code for the file operation failure and contact your switch service provider for assistance. FCOE-1007 Message Message Type Severity Probable Cause IfIndex Limit Reached . LOG ERROR Indicates that the interface index (IfIndex) limit has reached the maximum. Fabric OS Message Reference 53-1002749-01 329 5 FCOE-1009 Recommended Action Check the IfIndex limit displayed in the message. FCOE-1009 Message Addition of N_Port mapping failed. Max N_Port mapping limit reached: . Message Type LOG Severity INFO Probable Cause Indicates that the N_Port mapping has reached its maximum limit. Recommended Action Remove unwanted N_Port mappings using the fcoelogingroup --remove command and try adding N_Port mapping using the fcoelogingroup --add command. FCOE-1010 Message Message Type Severity FSS Registration or FCoE Trace initialization failed. LOG ERROR Probable Cause Indicates that the Fabric OS state synchronization (FSS) registration or initialization of the FCoE trace has failed. Recommended Action Execute the supportSave command and restart the system. If the problem persists, contact your switch service provider. FCOE-1012 Message Message Type Severity Request to delete port from VLAN failed. LOG ERROR Probable Cause Indicates that a request to delete ports from the specified VLAN has failed. Recommended Action Execute the supportSave command and restart the system. If the problem persists, contact your switch service provider. 330 Fabric OS Message Reference 53-1002749-01 FCOE-1014 5 FCOE-1014 Message Message Type Severity Request to add ports to VLAN failed. LOG ERROR Probable Cause Indicates that a request to add ports to the specified VLAN has failed. Recommended Action Execute the supportSave command and restart the system. If the problem persists, contact your switch service provider. FCOE-1015 Message Message Type Severity Request to add MACs to Layer 2 for ifindex 0x failed, rc:. LOG ERROR Probable Cause Indicates that a request to add MAC entries to Layer 2 for the specified slot or port has failed. Recommended Action Check the reason code for the failure and contact your switch service provider for assistance. FCOE-1016 Message Message Type Severity Request to delete VLAN failed. LOG ERROR Probable Cause Indicates a request to delete the specified VLAN has failed because the VLAN may be in use. Recommended Action Disable the active FCoE login session using the no fcoe command and try deleting the VLAN again. FCOE-1017 Message Message Type Severity Probable Cause Request to add FCMAP failed for VLAN . LOG ERROR Indicates that a request to add FCMAP has failed. When the VLAN is in use, its FCMAP cannot be modified. Fabric OS Message Reference 53-1002749-01 331 5 FCOE-1019 Recommended Action Disable the active FCoE session on VLAN using the no fcoe command and try adding the FCMAP again. FCOE-1019 Message Message Type Severity FLOGI ignored as FCMAP is not configured on FCoE VLAN. LOG WARNING Probable Cause Indicates that FCMAP has not been configured on FCoE VLAN. Recommended Action Configure FCMAP on the FCoE VLAN using the fcoe --fcmapset command. FCOE-1021 Message Port is already logged in. Message Type LOG Severity INFO Probable Cause Indicates that the N_Port device has already logged in or is in the process; duplicate FLOGI received. Recommended Action No action is required. FCOE-1022 Message Message Type Severity Max FCoE device login limit reached. LOG WARNING Probable Cause Indicates that the switch has reached its maximum allowed FCoE device limit. Recommended Action Do not add any more FCoE devices to the switch. 332 Fabric OS Message Reference 53-1002749-01 FCOE-1023 5 FCOE-1023 Message Message Type Severity , Too many logins on FCoE controller, max allowed = . LOG WARNING Probable Cause Indicates that the controller has reached its maximum allowed FCoE login limit. Recommended Action Log out some of the logged-in devices using the fcoe --resetlogin command and then log in a new device. You can view the list of logged-in devices using the fcoe --loginshow command. FCOE-1024 Message Message Type Severity FDISC received from E_node without prior FLOGI. LOG WARNING Probable Cause Indicates that a FDISC frame is received from the end node that has not logged in. The end node must send a fabric login (FLOGI) before it can send an FDISC. Recommended Action It is due to a CNA or target driver issue. Contact CNA or target driver support team for assistance. FCOE-1025 Message Message Type Severity FCoE logout received on FIP VN port. LOG WARNING Probable Cause Indicates pre-FIP logout for a device that has logged in using the FCoE Initialization Protocol (FIP). Recommended Action It is due to a CNA or target driver issue. Contact CNA or target driver support team for assistance. Fabric OS Message Reference 53-1002749-01 333 5 FCOE-1026 FCOE-1026 Message Message Type Severity FDISC/FLOGI mismatch. FDISC addressed to different FCF than base FLOGI. LOG WARNING Probable Cause Indicates that the base port has sent a fabric login (FLOGI) but the subsequent FDISC frames that were received on the switch do not match the original FLOGI. Recommended Action It is due to a CNA or target driver issue. Contact CNA or target driver support team for assistance. FCOE-1027 Message Message Type Severity : :::::. LOG ERROR Probable Cause Indicates that the Fibre Channel Forwarders (FCF) controller is not found for the DA. The end node may be sending the FLOGI with a wrong DA MAC address. Recommended Action Some parameters are not exchanged correctly between the switch and the end device. Reconfigure the port. FCOE-1028 Message Message Type Severity : :::::::. LOG ERROR Probable Cause Indicates that the FCoE device with the specified World Wide Name (WWN) is not a member of the login group. Recommended Action Change the FCoE login group policy on the switch using the fcoelogingroup command so that the device can log in. 334 Fabric OS Message Reference 53-1002749-01 FCOE-1029 5 FCOE-1029 Message Message Type Severity Version mismatch between FIP FDISC and root VN port. LOG WARNING Probable Cause Indicates a version mismatch between the fabric login (FLOGI) and FDISC. Recommended Action It is due to a CNA or target driver issue. Contact CNA or target driver support team for assistance. FCOE-1030 Message Message Type Severity Version mismatch between FIP LOGO and root VN port. LOG WARNING Probable Cause Indicates a version mismatch between the FCoE initialization protocol (FIP) logout and the base fabric login (FLOGI). Recommended Action It is due to a CNA or target driver issue. Contact CNA or target driver support team for assistance. FCOE-1031 Message FCoE port deleted port slot . Message Type LOG Severity INFO Probable Cause Indicates that an FCoE port has been deleted. Recommended Action No action is required. FCOE-1032 Message Message Type Severity Probable Cause We are in WARM RECOVERING state... LOG WARNING Indicates that high availability (HA) failover or switch reboot may be in progress. Fabric OS Message Reference 53-1002749-01 335 5 FCOE-1033 Recommended Action Wait until the chassis has fully recovered before you perform any operations. FCOE-1033 Message FIP v1 FLOGI received - VF port in use. Message Type LOG Severity INFO Probable Cause Indicates that a device is trying to log in to a port that already has a device logged in. Recommended Action No action is required. FCOE-1034 Message Message Type Severity Discarded frame received on priority pri_in> for which PFC/FCoE is disabled. LOG WARNING Probable Cause Indicates that a frame is received on the specified priority, for which priority-based flow control (PFC) or FCoE is disabled. Recommended Action Change the CEE map assigned to the FCoE map to accommodate the PFC for the specified FCoE priority or change the FCoE priority using the fabric-map default command under the FCoE configuration mode. FCOE-1037 Message Message Type Severity Logingroup dropped for switch WWN: , due to name conflict while merging. LOG WARNING Probable Cause Indicates that same login group name exists for two different switches that have different organizationally unique identifiers (OUIs), but the last three bytes are same. Recommended Action Create the login group for the switch World Wide Name (WWN) with another name that will not lead to a name conflict. 336 Fabric OS Message Reference 53-1002749-01 FCOE-1038 5 FCOE-1038 Message logingroup# () created. Message Type LOG Severity INFO Probable Cause Indicates that the specified login group is added to the switch login group table. Recommended Action No action is required. FCOE-1039 Message Logingroup deleted. Message Type LOG Severity INFO Probable Cause Indicates that the specified login group is deleted from the switch login group table. Recommended Action No action is required. FCOE-1040 Message Logingroup name changed from to . Message Type LOG Severity INFO Probable Cause Indicates that the login group has been renamed. Recommended Action No action is required. FCOE-1041 Message Transaction aborted. Message Type LOG Severity INFO Probable Cause Indicates that the ongoing FCoE login configuration transaction is aborted. Fabric OS Message Reference 53-1002749-01 337 5 FCOE-1042 Recommended Action No action is required. FCOE-1042 Message FCoE login configuration transaction saved fabric-wide. Message Type LOG Severity INFO Probable Cause Indicates that the FCoE login configuration transaction is saved fabric-wide. Recommended Action No action is required. FCOE-1043 Message FCoE login configuration management disabled. Message Type LOG Severity INFO Probable Cause Indicates that the FCoE login configuration management is disabled. Recommended Action No action is required. FCOE-1044 Message FCoE login configuration management enabled. Message Type LOG Severity INFO Probable Cause Indicates that the FCoE login configuration management is enabled. Recommended Action No action is required. 338 Fabric OS Message Reference 53-1002749-01 FCOE-1045 5 FCOE-1045 Message FCoE port is configured as VE port. Message Type LOG Severity INFO Probable Cause Indicates that the specified FCoE port is configured as a virtual expansion (VE) port. Recommended Action No action is required. FCOE-1046 Message fcoed.conf file is truncated. Please reconfigure FCoE ports. Message Type LOG Severity INFO Probable Cause Indicates that the magic number in the fcoed.conf file does not match. Therefore, the fcoed.conf file is truncated and updated with a new magic number. Recommended Action Reconfigure the FCoE ports as all the port configurations will be lost. FCOE-1047 Message fcoed.conf file is not present, therefore creating. Message Type LOG Severity INFO Probable Cause Indicates that the fcoed.conf file is not available and therefore creating a new file. Recommended Action No action is required. FCOE-1048 Message FCoE port is configured as VF port. Message Type LOG Severity INFO Probable Cause Indicates that the specified FCoE port is configured as a virtual fabric (VF) port. Fabric OS Message Reference 53-1002749-01 339 5 FCOE-1048 Recommended Action 340 No action is required. Fabric OS Message Reference 53-1002749-01 FCPD-1001 5 FCPD Messages FCPD-1001 Message Message Type Severity Probable Cause Probing failed on . LOG WARNING Indicates that a Fibre Channel Protocol (FCP) switch probed devices on a loop port, and probing failed on the L_Port, arbitrated loop physical address (AL_PA), or the F_Port. For ALPA, the valid range is 0x00 through 0xFF. The error variable can be either of the following: • • L_Port port_number ALPA alpa_number F_Port port_number This could happen due to some firmware issue with the device controller on the specified port. Recommended Action Contact the device vendor for any firmware-related issues. Also, consider upgrading the device firmware. FCPD-1002 Message Message Type Severity port , bad R_CTL for fcp probing: 0x. LOG WARNING Probable Cause Indicates that the response frame received on the specified port for an inquiry request contains an invalid value in the routing control field. This could happen due to some firmware issue with the device controller on the specified port. Recommended Action Contact the device vendor for any firmware-related issues. Also, consider upgrading the device firmware. FCPD-1003 Message Probing failed on which is possibly a private device which is not supported in this port type. Message Type LOG Severity INFO Probable Cause Indicates that device probing has failed because private devices will not respond to the switch port login (PLOGI) during probing. Fabric OS Message Reference 53-1002749-01 341 5 FCPD-1003 Recommended Action 342 The Brocade 4100, 4900, 5000, 7500, and AP 7600 do not support private loop devices. Refer to the switch vendor for a list of other port types that support private devices for inclusion into the fabric. Fabric OS Message Reference 53-1002749-01 FCPH-1001 5 FCPH Messages FCPH-1001 Message Message Type Severity Probable Cause : failed, out of memory condition. FFDC | LOG CRITICAL Indicates that the switch is low on memory and failed to allocate new memory for a Fibre Channel driver instance. The function value 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 kernel memory allocation. Recommended Action A non-bladed switch will automatically reboot. For a bladed switch, the active CP blade will automatically fail over and the standby CP will become the active CP. FCPH-1002 Message Message Type Severity Port has been disabled since switch requires authentication when device authentication policy is set to ON. LOG WARNING Probable Cause Indicates a device that does not support authentication has tried to log in to the switch when the device authentication policy is in ON status on the switch. Recommended Action Enable the authentication on the device or set the device authentication status to PASSIVE/OFF on the switch if it is not mandatory. Use the authUtil command to change the device authentication policy. FCPH-1003 Message Message Type Severity New port has same Port WWN as old port as part of duplicate Port WWN detection policy. LOG WARNING Probable Cause Indicates that the specified new port has the same Port World Wide Name (PWWN) as the old port. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 343 5 FCPH-1004 FCPH-1004 Message Message Type Severity NPIV port has same Port WWN as old port with pid 0x as part of duplicate Port WWN detection policy. LOG WARNING Probable Cause Indicates that the specified N_Port ID virtualization (NPIV) port has the same Port World Wide Name (PWWN) as the old port. Recommended Action No action is required. FCPH-1005 Message Message Type Severity FDISC exch=0x sid=0x did=0x on port rejected; temporary mem alloc error. Please bounce port of affected device. LOG WARNING Probable Cause Indicates that in busy login conditions, the buffer used for quick memory allocations (known as atomic malloc) can be quickly depleted and not replenished before the next allocation occurs. Recommended Action Reset the specified port using the portDisable and portEnable commands. 344 Fabric OS Message Reference 53-1002749-01 FCR-1001 5 FCR Messages FCR-1001 Message FC router proxy device in edge created at port . Message Type LOG Severity INFO Probable Cause Indicates that a proxy device at a port in the edge fabric has been imported at the specified port. Recommended Action No action is required. FCR-1002 Message FC router proxy device in edge deleted at port . Message Type LOG Severity INFO Probable Cause Indicates that a proxy device at a port in the edge fabric has been deleted at the specified port. Recommended Action No action is required. FCR-1003 Message FC router physical DEVICES newly exported at port . Message Type LOG Severity INFO Probable Cause Indicates that one or more physical devices have been newly exported through the specified port. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 345 5 FCR-1004 FCR-1004 Message FC router physical devices offline at port . Message Type LOG Severity INFO Probable Cause Indicates that one or more physical devices connected to the specified port have gone offline. Recommended Action Verify that the devices were intended to be taken offline. If not, verify that the devices are functioning properly. Verify that all small form-factor pluggables (SFPs) are seated correctly. Check for faulty cables, deteriorated SFPs, or dirty connections. Replace the cables and the SFPs if necessary. FCR-1005 Message FC router LSAN zone device removed at port . Message Type LOG Severity INFO Probable Cause Indicates that a device is removed from the logical storage area network (LSAN) zone in the edge fabric. Recommended Action No action is required. FCR-1006 Message FC router LSAN zone device added at port . Message Type LOG Severity INFO Probable Cause Indicates that a device is added to a logical storage area network (LSAN) zone in the edge fabric. Recommended Action No action is required. 346 Fabric OS Message Reference 53-1002749-01 FCR-1007 5 FCR-1007 Message FC router LSAN zone deleted at port . Message Type LOG Severity INFO Probable Cause Indicates that a logical storage area network (LSAN) zone attached to the specified port was deleted in the edge fabric. Recommended Action No action is required. FCR-1008 Message FC router LSAN zone created at port . Message Type LOG Severity INFO Probable Cause Indicates that a logical storage area network (LSAN) zone was created at the specified port in the edge fabric. Recommended Action No action is required. FCR-1009 Message FC router LSAN zone enabled at port : . Message Type LOG Severity INFO Probable Cause Indicates that a logical storage area network (LSAN) zone was enabled in the edge fabric attached to the specified port. The enabled LSAN zone configuration is listed. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 347 5 FCR-1010 FCR-1010 Message FC router LSAN zone disabled at port . Message Type LOG Severity INFO Probable Cause Indicates that a logical storage area network (LSAN) zone is disabled in the edge fabric attached to the specified port. Recommended Action No action is required. FCR-1011 Message Remote LSAN zone updated in domain . Message Type LOG Severity INFO Probable Cause Indicates that a logical storage area network (LSAN) zone update was received from another domain. Recommended Action No action is required. FCR-1012 Message FC Router fabric build completed on port . Message Type LOG Severity INFO Probable Cause Indicates that the Fibre Channel router has completed a fabric build at the specified port. Recommended Action No action is required. 348 Fabric OS Message Reference 53-1002749-01 FCR-1013 5 FCR-1013 Message Phantom FSPF database exchange completed on port . Message Type LOG Severity INFO Probable Cause Indicates that the specified EX_Port has completed the fabric shortest path first (FSFP) database exchange. Recommended Action No action is required. FCR-1015 Message New EX_Port or VEX_Port added on port in domain . Message Type LOG Severity INFO Probable Cause Indicates that an EX_Port was created on the specified port in the specified domain. Recommended Action No action is required. FCR-1016 Message FCR fabric no longer reachable at port id (0x) fabric ID . Message Type LOG Severity INFO Probable Cause Indicates that a fabric is no longer accessible through the backbone fabric. This may be caused by a link or switch failure. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 349 5 FCR-1018 FCR-1018 Message Message Type Severity FC router proxy device entries exhausted on port . LOG ERROR Probable Cause Indicates that the number of proxy devices is greater than allowed by the port resource. Recommended Action Remove excess logical storage area network (LSAN) zones or devices until the number of proxy devices exported is within the range allowed by the port resource. Use the fcrResourceShow command to view resources including LSAN zone resources, LSAN device resources, and proxy device port resources. Use the fcrProxyDevshow command to view how many proxy devices are created in the fabric with the port resource problem. LSAN zones are removed using standard zoning commands such as zoneShow, zoneRemove, zoneDelete, cfgDelete, and cfgDisable in the edge fabric. Proxy devices can be removed by zoning operations or by bringing physical devices offline (for example, disabling the port that a device is attached to, and then disconnecting the cable or disabling the device. FCR-1019 Message Message Type Severity EX_Port or VEX_Port entries exhausted at port . LOG ERROR Probable Cause Indicates that the number of EX_Port or VEX_Port entries being created is greater than allowed by the port resource. Recommended Action Disable EX_Ports or VEX_Ports until the number of ports is within the range allowed by the port resource. The EX_Port or VEX_Port limit is displayed using the fcrRouteShow command. Use the portDisable command to disable EX_Ports. FCR-1020 Message Message Type Severity Local LSAN zone entries for FC router exhausted; max limit: . LOG WARNING Probable Cause Indicates that the number of LSAN zones created within a MetaSAN exceeds the local LSAN zone database limitations. Recommended Action Remove excess LSAN zones so that the number of LSAN zones created is within the range of the local database limitations. To do that, perform the following steps: 1. Use the portDdisable command to disable all the EX_Ports that received this error message. 2. Use the portDdisable command to disable all the other EX_Ports on that FCR connected to the same edge fabrics to which the EX_Ports disabled in step 1 are connected. 350 Fabric OS Message Reference 53-1002749-01 FCR-1021 5 3. Use zoning commands on the edge fabrics, to reduce the LSAN zone entries on the edge fabrics. 4. Use the portEnable command on each EX_Port, one at a time, and verify that this error is not reported again. FCR-1021 Message Message Type Severity Local LSAN device entries exhausted. LOG WARNING Probable Cause Indicates that the number of devices created through logical storage area network (LSAN) zones within the MetaSAN exceeds the local LSAN zone database limitations. Recommended Action Remove excess device entries within LSAN zones so that the number of devices is within the range of the local zone database limitations. FCR-1022 Message Message Type Severity Local proxy device slot entries exhausted. LOG ERROR Probable Cause Indicates that resources to persistently store the proxy device slot to the remote world wide name (WWN) have been consumed. Recommended Action Remove the proxy device slots by using the fcrProxyConfig command or limit proxy devices by removing logical storage area network (LSAN) zone entries. FCR-1023 Message Message Type Severity Local phantom port WWN entries exhausted. LOG WARNING Probable Cause Indicates that the number of port World Wide Names (WWNs) detected to be in use exceeds the local port WWN resources. Recommended Action Limit the number of port WWNs required by limiting the remote edge fabric connectivity (which limits the number of translate domains). You can also limit the number of proxy devices for a translate domain (which limits the number of translate domain ports required) by limiting the devices specified in logical storage area network (LSAN) zones. Fabric OS Message Reference 53-1002749-01 351 5 FCR-1024 FCR-1024 Message Message Type Severity Local LSAN zone device entries for edge LSAN exhausted. LOG WARNING Probable Cause Indicates that the number of devices in a logical storage area network (LSAN) defined in the edge fabric is greater than allowed by the local LSAN zone database limitations. Recommended Action Remove excess device entries from this LSAN zone until the number of devices is within the range of the local LSAN zone database limitations. FCR-1025 Message Message Type Severity Local phantom node WWN entries exhausted. LOG WARNING Probable Cause Indicates that the number of node World Wide Names (WWNs) detected to be in use exceeds the local node WWN resources. Recommended Action Reduce the number of node WWNs required by limiting the remote edge fabric connectivity (which limits the number of translate domains). FCR-1026 Message In slot , Node WWN roll over. Message Type LOG Severity INFO Probable Cause Indicates that the node World Wide Name (WWN) pool has rolled over in the specified slot, and WWN entries not detected to be in use are reused as needed. Recommended Action It is unlikely that WWN conflicts will occur as a result of pool rollover unless the switch is deployed in a very large MetaSAN environment with a large number of logical storage area network (LSAN) devices and fabrics, or there are highly dynamic changes to EX_Port connectivity. WWN conflicts might cause unpredictable behavior in management applications. To avoid WWN conflicts, all EX_Ports attached to fabrics with highly dynamic changes to EX_Port connectivity should be disabled and then re-enabled. 352 Fabric OS Message Reference 53-1002749-01 FCR-1027 5 FCR-1027 Message In slot , Port WWN roll over. Message Type LOG Severity INFO Probable Cause Indicates that the port World Wide Name (WWN) pool has rolled over in the specified slot, and WWN entries not detected to be in use are reused as needed. Recommended Action It is unlikely that WWN conflicts will occur as a result of pool rollover unless the switch is deployed in a very large MetaSAN environment with a large number of logical storage area network (LSAN) devices and fabrics, or there are highly dynamic changes to EX_Port connectivity. WWN conflicts might cause unpredictable behavior in management applications. To avoid WWN conflicts, all EX_Ports attached to fabrics with highly dynamic changes to EX_Port or VEX_Port connectivity should be disabled and then re-enabled. FCR-1028 Message In slot , node WWN pool 95 percent allocated. Message Type LOG Severity INFO Probable Cause Indicates that the node World Wide Name (WWN) pool is close to rollover in the specified slot, and that the WWN entries not detected to be in use will be reused as needed. Recommended Action It is unlikely that WWN conflicts will occur as a result of pool rollover unless the switch is deployed in a very large MetaSAN environment with a large number of logical storage area network (LSAN) devices and fabrics, or there are highly dynamic changes to EX_Port or VEX_Port connectivity. WWN conflicts might cause unpredictable behavior in management applications. To avoid WWN conflicts, all EX_Ports attached to fabrics with highly dynamic changes to EX_Port connectivity should be disabled and then re-enabled. FCR-1029 Message In slot , Port WWN pool 95 percent allocated. Message Type LOG Severity INFO Probable Cause Indicates that the port World Wide Name (WWN) pool has rolled over in the specified slot, and WWN entries not detected to be in use are reused as needed. Recommended Action It is unlikely that WWN conflicts will occur as a result of pool rollover unless the switch is deployed in a very large MetaSAN environment with a large number of logical storage area network (LSAN) devices and fabrics, or there are highly dynamic changes to EX_Port connectivity. WWN conflicts might cause unpredictable behavior in management applications. To avoid WWN conflicts, all EX_Ports attached to fabrics with highly dynamic changes to EX_Port connectivity should be disabled and then re-enabled. Fabric OS Message Reference 53-1002749-01 353 5 FCR-1030 FCR-1030 Message Physical device came online at fabric . Message Type LOG Severity INFO Probable Cause Indicates that the physical device World Wide Name (WWN) came online in the specified fabric. Recommended Action No action is required. FCR-1031 Message Physical device went offline in fabric . Message Type LOG Severity INFO Probable Cause Indicates that the physical device World Wide Name (WWN) went offline in the specified fabric. Recommended Action No action is required. FCR-1032 Message Edge fabric enabled security on port in fabric . Message Type LOG Severity INFO Probable Cause Indicates that Secure mode was turned on in the edge fabric. Recommended Action No action is required. FCR-1033 Message Edge fabric disabled security on port in fabric . Message Type LOG Severity INFO Probable Cause 354 Indicates that Secure mode was turned off in the edge fabric. Fabric OS Message Reference 53-1002749-01 FCR-1034 Recommended Action 5 No action is required. FCR-1034 Message LSAN zone added in backbone fabric. Message Type LOG Severity INFO Probable Cause Indicates that a new logical storage area network (LSAN) zone was added to the backbone fabric. Recommended Action No action is required. FCR-1035 Message LSAN zone device added in the backbone fabric. Message Type LOG Severity INFO Probable Cause Indicates that a new device to a logical storage area network (LSAN) zone was added to the backbone fabric. Recommended Action No action is required. FCR-1036 Message LSAN zone enabled in the backbone fabric. Message Type LOG Severity INFO Probable Cause Indicates that the specified logical storage area network (LSAN) zone was enabled in the backbone fabric. The enabled LSAN zone configuration is listed. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 355 5 FCR-1037 FCR-1037 Message LSAN zone disabled in the backbone fabric. Message Type LOG Severity INFO Probable Cause Indicates that a logical storage area network (LSAN) zone is disabled in the backbone fabric. Recommended Action No action is required. FCR-1038 Message Message Type Severity Total zone entries exceeded local fabric limits by entries, in zone: , zone limit: . LOG WARNING Probable Cause Indicates that the number of cfg, zone, or alias entries created in a local fabric is greater than the local switch's zone database limitations. Recommended Action Remove excess cfg, zone, or alias entries so that the number of logical storage area network (LSAN) zones created is within the range of the local database limitations. FCR-1039 Message Local LSAN zone device entries for backbone LSAN exhausted. Message Type LOG Severity INFO Probable Cause Indicates that the number of devices in the specified logical storage area network (LSAN) defined in the backbone fabric is greater than allowed by the local LSAN zone database limitations. Recommended Action Remove excess device entries from this LSAN zone until the number of devices is within the range of the local LSAN zone database limitations. 356 Fabric OS Message Reference 53-1002749-01 FCR-1040 5 FCR-1040 Message Proxy device deleted in the backbone fabric. Message Type LOG Severity INFO Probable Cause Indicates that a proxy device created in the backbone fabric was deleted. Recommended Action No action is required. FCR-1041 Message LSAN zone device removed in the backbone fabric. Message Type LOG Severity INFO Probable Cause Indicates that a logical storage area network (LSAN) zone device within the backbone fabric was removed. Recommended Action No action is required. FCR-1042 Message LSAN zone removed in the backbone fabric. Message Type LOG Severity INFO Probable Cause Indicates that a logical storage area network (LSAN) zone within the backbone fabric was removed. Recommended Action No action is required. FCR-1043 Message Proxy device created in the backbone fabric. Message Type LOG Severity INFO Probable Cause Indicates that a proxy device was created in the backbone fabric. Fabric OS Message Reference 53-1002749-01 357 5 FCR-1048 Recommended Action No action is required. FCR-1048 Message Message Type Severity On EX port () setting port credits failed. LOG ERROR Probable Cause Indicates that the indicated credit type was not set. Setting port credits failed. Recommended Action Execute the portEnable command. If the problem persists, reboot the switch. If the message persists, collect switch information using the supportSave command, and contact your switch service provider. FCR-1049 Message Message Type Severity EX_Port () received an ELP command that is not supported. LOG ERROR Probable Cause Indicates an incoming exchange link parameter (ELP) command that is not supported. Recommended Action Use the portEnable and portDisable to enable or disable the port. If the problem persists, contact your switch service provider. FCR-1053 Message Message Type Severity Port was disabled, . LOG WARNING Probable Cause Indicates that the specified port was disabled because of a mismatched configuration parameter. Recommended Action Use the specified disable reason to identify a possible configuration parameter mismatch between the EX_Port and the switch at the other end of the link. 358 Fabric OS Message Reference 53-1002749-01 FCR-1054 5 FCR-1054 Message Message Type Severity Port received ILS of incorrect size (); valid ILS size is . LOG WARNING Probable Cause Indicates that an internal link service (ILS) IU of invalid size was received from the switch on the other end of the link. Recommended Action Check the error message log on the other switch using the errShow command for additional messages. Check for a faulty cable or deteriorated small form-factor pluggable (SFP). Replace the cable or the SFP if necessary. Run the portLogDumpPort command on both the receiving and transmitting ports. Run the fabStatsShow command on the transmitting switch. If the message persists, collect switch information using the supportSave command, and contact your switch service provider. FCR-1055 Message Switch with domain ID does not support backbone to edge imports. Message Type LOG Severity INFO Probable Cause Indicates that a switch that does not support backbone-to-edge routing was detected in the backbone. Edge-to-edge routing will work, but backbone-to-edge routing may fail. Recommended Action No action is required if backbone-to-edge routing is not required. Otherwise, replace the switch with one that supports backbone-to-edge routing. FCR-1056 Message Switch with front domain ID does not support backbone to edge imports. Message Type LOG Severity INFO Probable Cause Indicates that a switch that does not support backbone-to-edge routing is running in the MetaSAN. Recommended Action No action is required if backbone-to-edge routing is not needed. Otherwise, replace the switch with one that supports backbone-to-edge routing. Fabric OS Message Reference 53-1002749-01 359 5 FCR-1057 FCR-1057 Message Message Type Severity EX_Port() incompatible long distance parameters on link. LOG ERROR Probable Cause Indicates that the port, which is configured in long distance mode, has incompatible long distance parameters. Recommended Action Check the port configuration on both sides of the link using the portCfgShow command. Investigate the other switch for more details. Run the errShow command on the other switch to view the error log for additional messages. FCR-1058 Message Message Type Severity Port isolated due to mismatched configuration parameter; . LOG WARNING Probable Cause Indicates that the specified port was isolated after segmentation caused by mismatched configuration parameters or by a domain ID assigned by the principal switch that did not match the insistent domain ID of this port. Recommended Action Check the switches on both ends of the link for a possible mismatch in switch or port configuration parameters such as Operating Mode, E_D_TOV, R_A_TOV, Domain ID Offset, and so on. Run the portCfgExport command to modify the appropriate parameters on the local switch. Run the appropriate configuration command to modify the switch or port parameters on the remote switch. FCR-1059 Message EX_Port was disabled due to an authentication failure. Message Type LOG Severity INFO Probable Cause Indicates that the authentication, which uses the Diffie Hellman - Challenge Handshake Authentication Protocol (DH-CHAP), failed on the EX_Port. Recommended Action Verify that the shared secrets on both sides of the link match. 360 Disable and enable the ports by using the portDisable and the portEnable commands to restart authentication. Fabric OS Message Reference 53-1002749-01 FCR-1060 5 FCR-1060 Message Message Type Severity EX_Port() has an incompatible configuration setting. LOG WARNING Probable Cause Indicates that virtual channel (VC) Link Init is enabled on the local switch and the remote switch is negotiating in R_RDY mode. The fabric might not form properly. Recommended Action Check the configuration on the local switch using the portCfgShow command to verify that the VC Link Init is disabled, if the remote switch is configured in R_RDY mode or only capable of R_RDY mode. • • 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, that uses R_RDY primitive for flow control. FCR-1061 Message Backbone fabric created on port . Message Type LOG Severity INFO Probable Cause Indicates that a backbone fabric was built on the specified port. Recommended Action No action is required. FCR-1062 Message Port disabled, system only supports EX/VEX_ports. Message Type LOG Severity INFO Probable Cause Indicates that the maximum number of supported EX_Ports or VEX_Ports was exceeded. To enable the specified port, disable any other operational port and then re-enable the port. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 361 5 FCR-1063 FCR-1063 Message Fabric for switch with domain ID: mismatch with local fabric ID . Message Type LOG Severity INFO Probable Cause Indicates that the fabric ID of the switch does not match the local switch. Recommended Action Run the switchShow command to display the fabric ID. Change the fabric ID to match on both ends by modifying either the local or remote host using the fcrConfigure command. FCR-1064 Message Message Type Severity Fabric ID of backbone FC-Routers mismatch or overlap. LOG ERROR Probable Cause Indicates that either a backbone fabric split and both are connected to a common edge fabric, or the fabric ID of two backbone fabrics connected to an edge fabric are the same. Recommended Action If the backbone fabric split, merge the fabrics. If two (or more) backbone fabrics have the same IDs, make the fabric IDs unique using the fcrConfigure command. FCR-1065 Message Message Type Severity Fabric on port was assigned two different fabric IDs. LOG ERROR Probable Cause Indicates that another port on the switch is connected to the same edge fabric with a different fabric ID assignment. Recommended Action Change the port fabric ID to the same value as the other ports connected to the edge fabric using the portCfgExport or portCfgVexport commands. 362 Fabric OS Message Reference 53-1002749-01 FCR-1066 5 FCR-1066 Message Message Type Severity Fabric on port has the same fabric ID as another fabric. LOG ERROR Probable Cause Indicates that either the fabric split, or there is another fabric (possibly the backbone) that has the same fabric ID as the fabric connected to the specified port. Recommended Action If the fabric split, merge the fabrics and manually re-enable the port. If there is another fabric with the same ID, change the fabric ID for the port using the portCfgExport or portcfgVExport commands. FCR-1067 Message Message Type Severity Probable Cause Zone configurations, total LSAN zones and aliases, exceeded on port by entries; max entries: . LOG WARNING Indicates that the total number of zone configurations created in connected fabric exceeds the maximum number supported by the Fibre Channel. The limit includes both active and configured information that is part of be zoning database in the edge fabric. Non-LSAN zones are not counted in the limit. Recommended Action Limit the logical storage area network (LSAN) zoning-related zone configuration in the edge fabric connected to this port. FCR-1068 Message The FC Routing service is disabled. Message Type LOG Severity INFO Probable Cause Indicates that the FC Routing service is disabled. This is caused by issuing the fosConfig –-disable fcr, configDefault, or the configDownload command with the fcrState set to 2 (disabled). Note that the FC Routing service is disabled by the factory. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 363 5 FCR-1069 FCR-1069 Message The FC Routing service is enabled. Message Type LOG Severity INFO Probable Cause Indicates that the FC Routing service is enabled. This is caused by the fosConfig –-enable fcr or the configDownload command with the fcrState set to 1 (enabled). Note that the FC Routing service is disabled by the factory. Recommended Action No action is required. FCR-1070 Message The FC Routing configuration is set to default. Message Type LOG Severity INFO Probable Cause Indicates that the FC Routing configuration is set to the default by the user. This removes all prior FC Routing configurations. Recommended Action No action is required. FCR-1071 Message Port is changed from non FCR port to FCR port. Message Type LOG Severity INFO Probable Cause Indicates that the port became an EX_Port or VEX_Port. Recommended Action No action is required. 364 Fabric OS Message Reference 53-1002749-01 FCR-1072 5 FCR-1072 Message Port is changed from FCR port to non FCR port. Message Type LOG Severity INFO Probable Cause Indicates that the port is no longer an EX_Port or VEX_Port. Recommended Action No action is required. FCR-1073 Message Switch with domain ID in fabric has lower limit of LSAN Zones supported. Message Type LOG Severity INFO Probable Cause Indicates that an older version switch in the backbone or edge that supports a different limit of logical storage area network (LSAN) zones was detected. Recommended Action Use the fcrResourceShow command on all Fibre Channel Routers in the Meta-SAN to find lowest supported LSAN zone limits. Ensure the total number of LSAN zones in the Meta-SAN are within the lowest supported limit of LSAN zones. FCR-1074 Message Message Type Severity HA sync lost as remote CP supports only LSAN Zones. LOG ERROR Probable Cause Indicates that the remote control processor (CP) has older firmware, which supports a lower number of logical storage area network (LSAN) zones. This is causing the loss of high availability (HA) sync. Recommended Action Keep the number of LSAN zones to the lower limit of the two CPs or upgrade the remote CP. Fabric OS Message Reference 53-1002749-01 365 5 FCR-1075 FCR-1075 Message Message Type Severity Probable Cause Zone Name configuration is larger than characters in the edge fabric connected to port . LOG ERROR Indicates that the zone name configuration size created in the connected fabric exceeds the maximum supported by the FC Router. This size is equal to the total number of characters used by all the zone names in the edge fabric zoning database. The limit includes both LSAN and non-LSAN zone names defined in the zoning name database of the edge fabric. Recommended Action Limit the zone configuration size in the edge fabric connected to this port by either reducing the number of zones or changing the zone names to smaller names. FCR-1076 Message Port disabled, system only supports front domains. Message Type LOG Severity INFO Probable Cause Indicates that the maximum number of supported front domains was exceeded. To enable the specified port, disable any other operational front domain and then re-enable the port. Recommended Action Make sure to remain within the maximum number of supported front domains. FCR-1077 Message Message Type Severity Port rejected fabric binding request/check from the M-Model switch; . LOG WARNING Probable Cause Indicates that an M-Model edge switch attempted to either activate or check the fabric binding. This port will be disabled if this event occurred during a check of fabric binding and not during failure to activate fabric binding. The error is caused when the binding list details configured on the M-Model switch do not match with the currently configured front port domain ID and WWN of the EX_Port on which this operation was attempted. Recommended Action Ensure that the M-Model switch has the same currently configured details such as the front port domain ID and WWN of the EX_Port on which this operation was attempted. 366 Fabric OS Message Reference 53-1002749-01 FCR-1078 5 FCR-1078 Message Message Type Severity LSAN name is too long. It is dropped. LOG WARNING Probable Cause Indicates the length of the logical storage area network (LSAN) name exceeds the limit of 64 characters. Recommended Action Change the name and reactivate the zone database. FCR-1079 Message Message Type Severity Domain has conflict matrix database with local domain. LOG WARNING Probable Cause Indicates the specified domain has a different matrix database from the local domain. Recommended Action Change the matrix database. FCR-1080 Message Message Type Severity The pause response timer for domain expired. LOG WARNING Probable Cause Indicates that during the Coordinated HotCode protocol, a switch in the fabric has not responded to the pause message which prevented the protocol from completing. Any data traffic disruption observed during the firmware download may have been the result of the rejected pause message. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 367 5 FCR-1081 FCR-1081 Message Message Type Severity The pause message is rejected by the domain . LOG WARNING Probable Cause Indicates that during the Coordinated HotCode protocol, a switch in the fabric has rejected the pause message which prevented the protocol from completing. Any data traffic disruption observed during the firmware download may have been the result of the rejected pause message. Recommended Action No action is required. FCR-1082 Message Message Type Severity The pause retry count is exhausted for the domain . LOG WARNING Probable Cause Indicates that during the Coordinated HotCode protocol, a switch in the fabric did not accept the pause message which prevented the protocol from completing. Any data traffic disruption observed during the firmware download may have been the result of this issue. Recommended Action No action is required. FCR-1083 Message Message Type Severity The resume message is rejected by the domain . LOG WARNING Probable Cause Indicates that during the Coordinated HotCode protocol, a switch in the fabric has rejected the pause message which prevented the protocol from completing. Any data traffic disruption observed during the firmware download may have been the result of the rejected resume message. Recommended Action No action is required. 368 Fabric OS Message Reference 53-1002749-01 FCR-1084 5 FCR-1084 Message Message Type Severity The resume retry count is exhausted for the domain . LOG WARNING Probable Cause Indicates that during the Coordinated HotCode protocol, a switch in the fabric did not accept the resume message which prevented the protocol from completing. Any data traffic disruption observed during the firmware download may have been the result of this issue. Recommended Action No action is required. FCR-1085 Message Message Type Severity HA sync lost as remote CP does not support FCR based matrix. LOG ERROR Probable Cause Indicates that the remote control processor (CP) has older firmware, which does not support the FCR-based matrix while the local CP has the feature enabled. This is causing the loss of the high availability (HA) synchronization. Recommended Action Disable the FCR-based matrix or upgrade the remote CP. FCR-1086 Message Message Type Severity HA sync lost as remote CP does not support 8 Gbps-capable FC based EX_Ports. LOG ERROR Probable Cause Indicates that the remote control processor (CP) has older firmware, which does not support 8 Gbps-capable FC based EX_Port. This is causing the loss of the high availability (HA) synchronization. Recommended Action Disable 8 Gbps-capable FC based EX_Ports or upgrade the remote CP. Fabric OS Message Reference 53-1002749-01 369 5 FCR-1087 FCR-1087 Message Message Type Severity ExPort connects to fabric with capability to use XISL domain . LOG ERROR Probable Cause Indicates that the EX_Port connects to the logical fabric containing a domain that has the capability to use extended ISL (XISL). Recommended Action Disable "Allow to use XISL" mode of the domain by using the configure command. FCR-1088 Message LSAN tag added. Message Type LOG Severity INFO Probable Cause Indicates that the user has added a LSAN tag. Recommended Action No action is required. FCR-1089 Message LSAN tag removed. Message Type LOG Severity INFO Probable Cause Indicates that the user has removed a LSAN tag. Recommended Action No action is required. 370 Fabric OS Message Reference 53-1002749-01 FCR-1091 5 FCR-1091 Message Backbone Fabric ID changed to . Message Type LOG Severity INFO Probable Cause Indicates that the backbone fabric ID has been changed. Recommended Action No action is required. FCR-1092 Message Message Type Severity FCR ELS trap entries exhausted. LOG ERROR Probable Cause Indicates that the FCR ELS trap entries are exhausted. Recommended Action Execute the supportSave command and contact your switch service provider. FCR-1093 Message Slave EX-Port interopmode conflicts with trunk master . Disabling the port. Message Type LOG Severity INFO Probable Cause Indicates that the slave EX_Port is disabled due to interop conflict with trunk master Recommended Action Configure the slave EX_Port with the trunk master interop mode. Fabric OS Message Reference 53-1002749-01 371 5 FCR-1094 FCR-1094 Message Message Type Severity No Integrated Routing license present. EX-Port will not perform device sharing with other Brocade Native mode fabric(s). LOG WARNING Probable Cause Indicates that an EX_Port has been configured in Brocade Native mode. Device sharing will not occur with other Brocade Native mode fabrics because the Integrated Routing license is not installed. Recommended Action Install Integrated Routing license if device sharing is needed with other Brocade Native mode fabrics. FCR-1095 Message Message Type Severity The EX-Port is configured in 'McData/Open' Mode which is no longer supported, hence will be disabled next time port is offline and online. LOG WARNING Probable Cause Indicates that an EX_Port has been configured in 'McData/Open' mode. Initially after HA failover, the EX_Port will come up in McDATA mode. Further toggling will disable the port. Recommended Action Remove the 'McData/Open' interop modes in all EX_Ports FCR-1096 Message Message Type Severity Probable Cause Failed to allocate for : port . LOG ERROR Indicates that the authentication process failed because the system is low on memory. Data type is the payload or structure that failed to get memory. Operation phase specifies which operation of a particular authentication phase failed. Recommended Action Usually this problem is transient. The authentication may fail. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. 372 Fabric OS Message Reference 53-1002749-01 FCR-1097 5 FCR-1097 Message Message Type Severity Probable Cause Failed to get for message: port , retval . LOG ERROR Indicates that the authentication process failed to get a particular authentication value at certain phase. Data type is the payload or structure that failed to get memory. Recommended Action Usually this problem is transient. The authentication may fail. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. FCR-1098 Message Message Type Severity Invalid message code for message: port . LOG ERROR Probable Cause Indicates the receiving payload does not have valid message code for a particular authentication phase. Recommended Action Usually this problem is transient. The authentication may fail. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Fabric OS Message Reference 53-1002749-01 373 5 FICN-1003 FICN Messages FICN-1003 Message Message Type Severity FICON Tape Emulation License Key is not installed. LOG WARNING Probable Cause Indicates FICON Tape Emulation requires a License Key. Recommended Action Use the appropriate License Key. FICN-1004 Message Message Type Severity FICON XRC Emulation License Key is not installed. LOG WARNING Probable Cause Indicates FICON eXtended Remote Copy (XRC) Emulation requires a License Key. Recommended Action Use the appropriate License Key. FICN-1005 Message FICON GEPort TID Feature Change verified Xrc <1 or 0 - XRC Emulation Enabled or Disabled> TapeWrt <1 or 0 - Tape Write Emulation Enabled or Disabled> TapeRd <1 or 0 - FICON Tape Read Emulation Enabled or Disabled> TinTir <1 or 0 - FICON TIN/TIR Emulation Enabled or Disabled> DvcAck <1 or 0 - FICON Device Level Ack Emulation Enabled or Disabled> RdBlkId <1 or 0 FICON Write Emulation Read Block ID Emulation Enabled or Disabled>. Message Type LOG Severity INFO Probable Cause Indicates the configuration was changed manually. Recommended Action No action is required. 374 Fabric OS Message Reference 53-1002749-01 FICN-1006 5 FICN-1006 Message Message Type Severity FICON GEPort TID Feature Change failed Xrc <1 or 0 - XRC Emulation Enabled or Disabled> TapeWrt <1 or 0 - Tape Write Emulation Enabled or Disabled> TapeRd <1 or 0 - FICON Tape Read Emulation Enabled or Disabled> TinTir <1 or 0 - FICON TIN/TIR Emulation Enabled or Disabled> DvcAck <1 or 0 - FICON Device Level Ack Emulation Enabled or Disabled> RdBlkId <1 or 0 FICON Write Emulation Read Block ID Emulation Enabled or Disabled>. LOG WARNING Probable Cause Indicates that the feature change has failed because the FCIP tunnel ID associated with the FICON tunnel is still active. Recommended Action Disable the applicable FCIP tunnel to make the feature change effective. FICN-1007 Message Message Type Severity DevDiskEgr:FICON Selective Reset:Path=0x State=0x stat_array=0x. LOG ERROR Probable Cause Indicates a Selective Reset from the channel was received as either a normal part of path recovery or the starting sequence in an error case. Recommended Action If there was a job failure associated with this event, contact your vendor's customer support. FICN-1008 Message Message Type Severity DevDiskEgr:FICON Purge Path received Path=0x. LOG ERROR Probable Cause Indicates a FICON Purge Path was received from the channel as a part of path recovery. Recommended Action If there was a job failure associated with this event, contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 375 5 FICN-1009 FICN-1009 Message DevIng:CmdReject Sense Data rcvd:Path=0x LastCmds=0x Sense Data:Bytes0-0xB=0x. Message Type LOG Severity INFO Probable Cause Indicates a Unit Check status was received from a device and a sense command was issued to read the sense data. Recommended Action If there was a job failure associated with this event, contact your vendor's customer support for assistance. FICN-1010 Message DevDiskEgr:Device level exception flag found for Path=0x: Oxid=0x. Message Type LOG Severity INFO Probable Cause Indicates a Device Level Exception frame was received from the FICON channel. Recommended Action If there was a job or I/O failure associated with this event, contact your vendor's customer support for assistance. FICN-1011 Message Message Type Severity DevDiskIng:XRC Incorrect RRS SeqNum Rcvd Path=0x Expected=0x Received=0x Oxid=0x. LOG ERROR Probable Cause Indicates the Control unit or device presented a Read Record Set Sequence number different from the SDM's expected sequence number. Recommended Action If there was an XRC volume or session suspended associated with this event, contact your vendor's customer support for assistance. 376 Fabric OS Message Reference 53-1002749-01 FICN-1012 5 FICN-1012 Message Message Type Severity DevDiskIng:Device level exception found for Path=0x: Oxid=0x. LOG ERROR Probable Cause Indicates a Device Level Exception frame received from the FICON direct attached storage device (DASD) Control Unit. Recommended Action If there was a job or I/O failure associated with this event, contact your vendor's customer support for assistance. FICN-1013 Message DevDiskIng:Status=0x received in odd state=0x from Path=0x sent LBY. Message Type LOG Severity INFO Probable Cause Indicates that when the device sent the status in an incorrect state, the emulation processing rejected the status with an LBY frame. Recommended Action If there was a job or I/O failure associated with this event, contact your vendor's customer support for assistance. FICN-1014 Message DevEgr:Device level exception flag found for Path=0x: Oxid=0x. Message Type LOG Severity INFO Probable Cause Indicates a frame was received that indicated a device level exception. Recommended Action If there was an I/O failure associated with this event, contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 377 5 FICN-1015 FICN-1015 Message Message Type Severity DevEgr:cuPath=0x******:Discarding Invalid LRCd SOF=0x count=. LOG ERROR Probable Cause Indicates a frame was received from the peer emulation processing with an invalid Longitudinal Redundancy Checking (LRC) values. This indicates data corruption between the emulation processing components. Recommended Action Contact your vendor's customer support for assistance. FICN-1016 Message DevIng:Received Logical Path Removed response:Path=0x**. Message Type LOG Severity INFO Probable Cause Indicates the FICON Control Unit sent a Logical Path Removed (LPR) frame to the FICON channel. Recommended Action No action is required. FICN-1017 Message DevIng:Received Logical Path Established response:Path=0x**. Message Type LOG Severity INFO Probable Cause Indicates the FICON Control Unit sent an Logical Path Established (LPE) frame to the FICON channel. Recommended Action No action is required. 378 Fabric OS Message Reference 53-1002749-01 FICN-1018 5 FICN-1018 Message Message Type Severity DevIng:FCUB Lookup failed for Path=0x******. LOG ERROR Probable Cause Indicates the FICON Control Unit sent a frame that cannot be associated with a FICON Control Unit number (CUADDR). Recommended Action Contact your vendor's customer support for assistance. FICN-1019 Message Message Type Severity DevTapeEgr:AS Link Level Reject (LRJ) from Chan on Path=0x LastCmd=0x LastStatus=0x. LOG ERROR Probable Cause Indicates the FICON channel indicated in the path issued a Link Level Reject (LRJ) frame for a sequence from the device. Recommended Action If there was a job failure associated with this event, contact your vendor's customer support for assistance. FICN-1020 Message Message Type Severity DevTapeEgr:FICON Cancel received Path=0x state=0x tflags=0x sflags=0x. LOG WARNING Probable Cause Indicates the FICON channel issued a Cancel sequence for a device in emulation. Recommended Action If there was an unexpected job failure associated with this event, contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 379 5 FICN-1021 FICN-1021 Message Message Type Severity DevTapeEgr:FICON Tape Cancel:Path=0x Elapsed Time=. seconds. LOG WARNING Probable Cause Indicates the FICON channel issued a Cancel sequence for a device in emulation. Recommended Action If there was an unexpected job failure associated with this event, contact your vendor's customer support for assistance. FICN-1022 Message Message Type Severity DevTapeEgr:FICON Selective Reset:Path=0x State=0x statArray=0x cmdArray=0x tflags=0x sflags=0x. LOG ERROR Probable Cause Indicates the FICON channel issued a Selective Reset for a device that was active in emulation. Recommended Action If there was an unexpected job failure associated with this event, contact your vendor's customer support for assistance. FICN-1023 Message Message Type Severity DevTapeEgr:FICON Selective Reset:Path=0x Elapsed Time=. seconds. LOG ERROR Probable Cause Indicates the FICON channel issued a Selective Reset sequence for a device. Recommended Action If there was an unexpected job failure associated with this event, contact your vendor's customer support for assistance. 380 Fabric OS Message Reference 53-1002749-01 FICN-1024 5 FICN-1024 Message Message Type Severity DevTapeEgr:FICON Purge received Path=0x. LOG ERROR Probable Cause Indicates the FICON channel issued a Purge Path command sequence for a device. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. FICN-1025 Message Message Type Severity DevTapeIng:Auto Sense Data received on Path=0x Bytes0-0xB=0x. LOG WARNING Probable Cause Indicates the FICON Tape Write Pipelining processed sense data from a FICON device. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. FICN-1026 Message DevTapeIng:UnusualStatus:WriteCancelSelr:Generating Final Ending Status Path=0x. Message Type LOG Severity INFO Probable Cause Indicates the FICON Tape Write Pipelining is completing an emulated Selective Reset sequence. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 381 5 FICN-1027 FICN-1027 Message Message Type Severity DevTapeIng:Device level exception found for Path=0x: Oxid=0x. LOG ERROR Probable Cause Indicates an active emulation device delivered a Device Level Exception frame to the emulation processing. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. FICN-1028 Message Message Type Severity HostDiskIng:FICON Cancel received Path=0x state=0x. LOG WARNING Probable Cause Indicates an active emulation device received a cancel operation from the FICON channel. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. FICN-1029 Message Message Type Severity HostDiskIng:FICON Selective Reset:Path=0x state=0x LastCmds=0x LastStatus=0x. LOG ERROR Probable Cause Indicates an active disk emulation device received a Selective Reset from the FICON channel. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. 382 Fabric OS Message Reference 53-1002749-01 FICN-1030 5 FICN-1030 Message Message Type Severity HostDiskIng:FICON Purge received:Path=0x. LOG ERROR Probable Cause Indicates an active disk emulation device received a FICON Purge Path from the channel. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. FICN-1031 Message Message Type Severity HostDiskIng:FICON System Reset received on Path=0x**. LOG WARNING Probable Cause Indicates the FICON channel sent a System Reset to the disk control unit. Recommended Action No action is required. The MVS system was either set to initial program load (IPL) or performing error recovery. FICN-1032 Message HostDiskIng:XRC Read Channel Extender Capabilities detected on Path: 0x. Message Type LOG Severity INFO Probable Cause Indicates the eXtended Remote Copy (XRC) System Data mover was restarted to discover the capabilities of the channel extension equipment. Recommended Action No action is required. This is a part of the XRC initialization. Fabric OS Message Reference 53-1002749-01 383 5 FICN-1033 FICN-1033 Message HostEgr:Logical Path Established on Path=0x**. Message Type LOG Severity INFO Probable Cause Indicates the peer-side FICON Control Unit has accepted a logical path establishment command sequence with the FICON channel. Recommended Action No action is required. This is a part of the FICON path initialization. FICN-1034 Message Message Type Severity HostEgr:Discarding Invalid LRCd Frame on Path=0x****** count=. LOG ERROR Probable Cause Indicates the channel emulation processing received a frame with an invalid FICON LRC from the peer. This indicates that the channel side noted corruption from the Control Unit- or device-side processing. Recommended Action Contact your vendor's customer support for assistance. FICN-1035 Message Message Type Severity HostIng:FICON System Reset received on Path=0x**. LOG WARNING Probable Cause Indicates a locally connected FICON channel issued a System Reset to the specified FICON Control Unit. Recommended Action No action is required. This is a part of the FICON path initialization. 384 Fabric OS Message Reference 53-1002749-01 FICN-1036 5 FICN-1036 Message HostIng:FICON RLP Request on Path=0x**. Message Type LOG Severity INFO Probable Cause Indicates a locally connected FICON channel issued a Remove Logical Path sequence to the specified FICON Control Unit. Recommended Action No action is required. This is a part of the FICON path deactivation. FICN-1037 Message HostIng:FICON ELP Request on Path=0x**. Message Type LOG Severity INFO Probable Cause Indicates a locally connected FICON channel issued an Establish Logical Path sequence to the specified FICON Control Unit. Recommended Action No action is required. This is a part of the FICON path activation. FICN-1038 Message Message Type Severity fcFicIngHost:FDCB Lookup failed for Path=0x******. LOG ERROR Probable Cause Indicates a locally connected FICON channel sent a frame that could not be associated with a FICON device. Recommended Action Contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 385 5 FICN-1039 FICN-1039 Message Message Type Severity HostIng:FCUB Lookup failed for Path=0x********. LOG ERROR Probable Cause Indicates a locally connected FICON channel sent a frame that could not be associated with a FICON Control Unit. Recommended Action Contact your vendor's customer support for assistance. FICN-1040 Message Message Type Severity HostTapeEgr:Tape:CmdReject Sense Data Rcvd:Path=0x LastCmds=0x SenseData:Bytes0-0xB=0x. LOG ERROR Probable Cause Indicates an active disk emulation device received a FICON Purge Path from the channel. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. FICN-1041 Message Message Type Severity HostTapeEgr:AS Link Level Reject (LRJ) from CU Rx Path=0x LastCmd=0x LastStatus=0x. LOG ERROR Probable Cause Indicates that a Link Level Reject (LRJ) received from a device indicates that the Control Unit has lost the logical path to the Logical Partition (LPAR). Recommended Action If this was an unexpected event, contact your vendor's customer support for assistance. 386 Fabric OS Message Reference 53-1002749-01 FICN-1042 5 FICN-1042 Message Message Type Severity HostTapeIng:FICON Cancel received Path=0x state=0x. LOG WARNING Probable Cause Indicates a job was canceled during a Tape Write Pipelining. Recommended Action If this was an unexpected event (cancel is normally an operator event), contact your vendor's customer support for assistance. FICN-1043 Message Message Type Severity HostTapeIng::FICON Selective Reset:Path=0x state=0x LastCmds=0x LastStatus=0x. LOG ERROR Probable Cause Indicates that protocol errors in emulation in the Control Unit or network errors can cause a Selective Reset. Recommended Action If this was an unexpected event, contact your vendor's customer support for assistance. FICN-1044 Message Message Type Severity HostTapeIng:FICON Selective Reset:Path=0x Elapsed Time=. seconds. LOG ERROR Probable Cause Indicates that protocol errors in emulation in the Control Unit or network errors can cause a Selective Reset. Recommended Action If this was an unexpected event, contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 387 5 FICN-1045 FICN-1045 Message Message Type Severity HostTapeIng:FICON Purge received:Path=0x. LOG WARNING Probable Cause Indicates a Purge Path was received from the locally connected FICON channel. This is performed during the path recovery. Recommended Action If this was an unexpected event, contact your vendor's customer support for assistance. FICN-1046 Message Message Type Severity HostTapeIng:LRJ received on Path=0x lastCmds=0x lastStatus=0x treating as system reset event. LOG WARNING Probable Cause Indicates that a Link Level Reject (LRJ) from a FICON channel indicates that the channel no longer has a path established to the Control Unit. Recommended Action This is normally an unexpected event; contact your vendor's customer support for assistance. FICN-1047 Message Message Type Severity fcFicSetEmulation:Path=0x FDCB Not Idle state=0x prevState=0x set to state=0x. LOG ERROR Probable Cause Indicates there is an internal emulation error. This message should not be encountered. Recommended Action This is an unexpected event; contact your vendor's customer support for assistance. 388 Fabric OS Message Reference 53-1002749-01 FICN-1048 5 FICN-1048 Message Message Type Severity DevDiskEgr:FICON Cancel received Path=0x state=0x sflags=0x. LOG WARNING Probable Cause Indicates the operator has canceled a read or write job. Recommended Action This is an unexpected event; contact your vendor's customer support for assistance. FICN-1049 Message Message Type Severity ProcessIngTirData:Lost Logical Path for Path=0x** Index=. LOG WARNING Probable Cause Indicates a TIR received from a FICON endpoint indicates that it no longer has an established path to its peer. Recommended Action This is an unexpected event; contact your vendor's customer support for assistance. FICN-1050 Message Message Type Severity ProcessEgrTirData:Lost Logical Path for Path=0x** Index=. LOG WARNING Probable Cause Indicates a TIR received from a far-side FICON endpoint indicates that it no longer has an established path to its peer. Recommended Action This is an unexpected event; contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 389 5 FICN-1051 FICN-1051 Message XRC Session Established: SessID=, Path=0x Message Type LOG Severity INFO Probable Cause Indicates a PSF command has been received to initiate an eXtended Remote Copy (XRC) session with the extended direct attached storage device (DASD) device. Recommended Action No action is required. This is a part of the XRC session establishment. FICN-1052 Message XRC Session Terminated: SessID=, Path=0x. Message Type LOG Severity INFO Probable Cause Indicates a PSF command has been received to break an eXtended Remote Copy (XRC) session with the extended direct attached storage device (DASD) device. Recommended Action If this was an unexpected event, contact your vendor's customer support for assistance. FICN-1053 Message XRC Withdraw From Session: SessID=, Path=0x. Message Type LOG Severity INFO Probable Cause Indicates a PSF command has been received to withdraw from the eXtended Remote Copy (XRC) session with the extended direct attached storage device (DASD) device. Recommended Action If this was an unexpected event, contact your vendor's customer support for assistance. 390 Fabric OS Message Reference 53-1002749-01 FICN-1054 5 FICN-1054 Message Message Type Severity XRC Device Suspended: SessID=, Path=0x. LOG WARNING Probable Cause Indicates a PSF command has been received to suspend an eXtended Remote Copy (XRC) session with the extended direct attached storage device (DASD) device. Recommended Action If this was an unexpected event, contact your vendor's customer support for assistance. FICN-1055 Message Message Type Severity XRC All Devices Suspended: SessID=, Path=0x. LOG WARNING Probable Cause Indicates a PSF command has been received to suspend all extended direct attached storage device (DASD) devices from the eXtended Remote Copy (XRC) session. Recommended Action If this was an unexpected event, contact your vendor's customer support for assistance. FICN-1056 Message Message Type Severity FICON Emulation Error Error Code=, Path=0x LastStates=0x. LOG ERROR Probable Cause Indicates an internal coding error within emulation processing. Recommended Action This is an unexpected event; contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 391 5 FICN-1057 FICN-1057 Message Message Type Severity Error return from frame generation processing for a FICON device: Path=0x. LOG ERROR Probable Cause Indicates an internal resource shortage caused an error so that an emulation frame could not be created and sent to a device. Recommended Action This is an unexpected event; contact your vendor's customer support for assistance. FICN-1058 Message Message Type Severity Error return from frame generation processing for a FICON control unit: Path=0x. LOG ERROR Probable Cause Indicates an internal resource shortage caused an error so that an emulation frame could not be created and sent to a Control Unit. Recommended Action This is an unexpected event; contact your vendor's customer support for assistance. FICN-1059 Message Message Type Severity Error return from frame generation for a FICON Image: Path=0x. LOG ERROR Probable Cause Indicates an internal resource shortage caused an error so that an emulation frame could not be created and sent to an Logical Partition (LPAR). Recommended Action This is an unexpected event; contact your vendor's customer support for assistance. 392 Fabric OS Message Reference 53-1002749-01 FICN-1060 5 FICN-1060 Message Message Type Severity Error return from fcFwdPrcEgressFrame: Path=0x. LOG ERROR Probable Cause Indicates an internal resource shortage caused an error so that an emulation frame could not be created and sent to a device. Recommended Action This is an unexpected event; contact your vendor's customer support for assistance. FICN-1061 Message Message Type Severity Error return from fcFwdRemoveEmulHashEntry: Path=0x. LOG ERROR Probable Cause Indicates an internal issue has been encountered in the removal of an existing fast path hash table entry. Recommended Action This is an unexpected event; contact your vendor's customer support for assistance. FICN-1062 Message Message Type Severity Ingress Abort:Oxid=0x:Path=0x:LastStates=0x. LOG ERROR Probable Cause Indicates an abort operation has been received from the local FC interface for an active emulation exchange. Recommended Action This is an unexpected event; contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 393 5 FICN-1063 FICN-1063 Message Message Type Severity Egress Abort:Oxid=0x:Path=0x:LastStates=0x. LOG ERROR Probable Cause Indicates an abort operation has been received from a peer FC interface for an active emulation exchange. Recommended Action This is an unexpected event; contact your vendor's customer support for assistance. FICN-1064 Message Ingress Abort:Oxid=0x:Unknown Path on GEPort= VEPort= from SID=0x to DID=0x. Message Type LOG Severity INFO Probable Cause Indicates an abort operation has been received from a local FC interface for an exchange. Recommended Action If there were associated I/O errors at the same time as this event, contact your vendor's customer support for assistance. FICN-1065 Message Egress Abort:Oxid=0x:Unknown Path on GEPort= VEPort= from SID=0x to DID=0x. Message Type LOG Severity INFO Probable Cause Indicates an abort operation has been received from a peer FC interface for an exchange. Recommended Action If there were associated I/O errors at the same time as this event, contact your vendor's customer support for assistance. 394 Fabric OS Message Reference 53-1002749-01 FICN-1066 5 FICN-1066 Message Message Type Severity MemAllocFailed for GEPort= VEport= could not create required structure. LOG WARNING Probable Cause Indicates an internal resource limit has been encountered so that additional control block memory could not be allocated. Recommended Action This is an unexpected event; either the maximum number of emulation devices are already in use or there is an internal memory leak. Contact your vendor's customer support for assistance. FICN-1067 Message Message Type Severity Ingress Abort:Oxid=0x:Abort for CH=0x****. LOG ERROR Probable Cause Indicates an abort operation has been received from a local FC interface for an emulation CH exchange. Recommended Action If there were associated I/O errors at the same time as this event, contact your vendor's customer support for assistance. FICN-1068 Message Message Type Severity Ingress Abort:Oxid=0x:Abort for CU=0x**. LOG ERROR Probable Cause Indicates an abort operation has been received from a local FC interface for an emulation Control Unit exchange. Recommended Action If there were associated I/O errors at the same time as this event, contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 395 5 FICN-1069 FICN-1069 Message Message Type Severity Emulation Configuration Error on TunnelId :. LOG ERROR Probable Cause Indicates an error has been noted in the FICON configuration. Refer to the string for the nature of the configuration issue. Recommended Action If resolution of the configuration issue cannot be completed, contact your vendor's customer support for assistance. FICN-1070 Message DevTapeIngr:Exceptional Status rcvd on Path=0x state=0x status=0x. Message Type LOG Severity INFO Probable Cause Indicates the normal end of tape status (0x0D or 0x05) is received from the device or error status (including Unit Check 0x02) is received from an active emulation device. Recommended Action The end of tape is a normal event during pipelining and not the unit check. If there are associated I/O error messages with this event, contact your vendor's customer support for assistance. FICN-1071 Message HostTapeIngr:Tape Loaded on Path=0x. Message Type LOG Severity INFO Probable Cause Indicates the tape I/Os are processed from a locally connected Logical Partition (LPAR), which indicates that a tape is loaded on a device. Recommended Action No action is required. 396 Fabric OS Message Reference 53-1002749-01 FICN-1072 5 FICN-1072 Message DevTapeEgr:Tape Loaded on Path=0x. Message Type LOG Severity INFO Probable Cause Indicates the tape I/Os are processed from a locally connected Logical Partition (LPAR), which indicates that a tape is loaded on a device. Recommended Action No action is required. FICN-1073 Message HostTapeIngr:Unloaded:Path=0x:states=0x<4 prior emulation states>:cmds=0x:status=0x:flags=0x. Message Type LOG Severity INFO Probable Cause Indicates a Rewind and Unload I/O has been processed from a locally connected Logical Partition (LPAR), which indicates that a tape should be unloaded on a device. Recommended Action No action is required. FICN-1074 Message HostTapeIngr:WriteReport:Path=0x:Emuls=0x:Cmds=0x:Chains=0x:MBytes=. Message Type LOG Severity INFO Probable Cause Indicates a Rewind and Unload I/O has been processed from a locally connected Logical Partition (LPAR) and Tape Write Pipelining was performed on the currently loaded tape. Fabric OS Message Reference 53-1002749-01 397 5 FICN-1075 Recommended Action No action is required. FICN-1075 Message HostTapeIngr:ReadBlkReport:Path=0x:Emuls=0x:Cmds=0x:Chains=0x:MBytes=. Message Type LOG Severity INFO Probable Cause Indicates a Rewind and Unload I/O has been processed from a locally connected Logical Partition (LPAR) and Read Block pipelining was performed on the currently loaded tape. Recommended Action No action is required. FICN-1076 Message HostTapeIngr:ReadCpReport:Path=0x:Emuls=0x:Cmds=0x:Chains=0x:MBytes=. Message Type LOG Severity INFO Probable Cause Indicates a Rewind and Unload I/O has been processed from a locally connected Logical Partition (LPAR) and Read Channel Program pipelining was performed on the currently loaded tape. Recommended Action No action is required. 398 Fabric OS Message Reference 53-1002749-01 FICN-1077 5 FICN-1077 Message DevTapeEgr:Unloaded:Path=0x:states=0x<4 prior emulation states>:cmds=0x:status=0x:flags=0x. Message Type LOG Severity INFO Probable Cause Indicates a Rewind and Unload I/O has been processed from a remotely connected Logical Partition (LPAR), which indicates that a tape should be unloaded on a device. Recommended Action No action is required. FICN-1078 Message DevTapeEgr:WriteReport:Path=0x:Emuls=0x:Cmds=0x:Chains=0x:MBytes=. Message Type LOG Severity INFO Probable Cause Indicates a Rewind and Unload I/O has been processed from a remotely connected Logical Partition (LPAR) and Write Tape Pipelining was performed on the currently loaded tape. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 399 5 FICN-1079 FICN-1079 Message DevTapeEgr:ReadBlkReport:Path=0x:Emuls=0x:Cmds=0x:Chains=0x:MBytes=. Message Type LOG Severity INFO Probable Cause Indicates a Rewind and Unload I/O has been processed from a remotely connected Logical Partition (LPAR) and Read Block pipelining was performed on the currently loaded tape. Recommended Action No action is required. FICN-1080 Message DevTapeEgr:ReadCpReport:Path=0x:Emuls=0x:Cmds=0x:Chains=0x:MBytes=. Message Type LOG Severity INFO Probable Cause Indicates a Rewind and Unload I/O has been processed from a remotely connected Logical Partition (LPAR) and Read Channel Program pipelining was performed on the currently loaded tape. Recommended Action No action is required. FICN-1081 Message Message Type Severity Probable Cause 400 DevTapeIng:LRJ received on Path=0x lastCmds=0x lastStatus=0x treating as system reset event. LOG WARNING Indicates a Link Level Reject (LRJ) from a FICON channel indicates that the channel does not have a path established to the Control Unit. Fabric OS Message Reference 53-1002749-01 FICN-1082 Recommended Action 5 This is normally an unexpected event; contact your vendor's customer support for assistance. FICN-1082 Message Message Type Severity EmulEls:CSWR_RSCN received on GEPort= VEPort= Domain=0x Port=0x. LOG WARNING Probable Cause Indicates an attached port which had a FICON emulated path established has logged out from the switch. Recommended Action This may be an unexpected event; contact your vendor's customer support for assistance. FICN-1083 Message Message Type Severity EmulEls:SW_RSCN received on GEPort= VEPort= Domain=0x Port=0x. LOG WARNING Probable Cause Indicates an attached port with the established FICON emulated path has logged out from the switch. Recommended Action This may be an unexpected event; contact your vendor's customer support for assistance. FICN-1084 Message Message Type Severity fcFicInit: No DRAM2 memory available, FICON emulation is disabled. LOG ERROR Probable Cause Indicates a faulty DRAM2 was detected and access to its address range is prohibited. Recommended Action This is an unexpected event; contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 401 5 FICN-1085 FICN-1085 Message FICON FCIP Tunnel is Up on GE,tunnel Id=. Message Type LOG Severity INFO Probable Cause Indicates a FICON FCIP tunnel has been established successfully to the peer switch. Recommended Action No action is required. FICN-1086 Message Message Type Severity FICON FCIP Tunnel is Down on GE,tunnel Id=. LOG ERROR Probable Cause Indicates a FICON FCIP tunnel to the peer switch has been terminated. Recommended Action This is an unexpected event; contact your vendor's customer support for assistance. FICN-1087 Message Message Type Severity DevTeraEgr:AS Link Level Reject (LRJ) from Chan on Path=0x LastCmd=0x LastStatus=0x. LOG ERROR Probable Cause Indicates the FICON channel indicated in the path issued an Link Level Reject (LRJ) frame for a sequence from the device. Recommended Action If there was a job failure associated with this event, contact your vendor's customer support for assistance. 402 Fabric OS Message Reference 53-1002749-01 FICN-1088 5 FICN-1088 Message Message Type Severity DevTeraEgr:FICON Cancel received Path=0x state=0x tflags=0x sflags=0x. LOG WARNING Probable Cause Indicates the FICON channel issued a Cancel sequence for a device in emulation. Recommended Action If there was an unexpected job failure associated with this event, contact your vendor's customer support for assistance. FICN-1089 Message Message Type Severity DevTeraEgr:FICON Tera Cancel:Path=0x Elapsed Time=. seconds. LOG WARNING Probable Cause Indicates the FICON channel issued a Cancel sequence for a device in emulation. Recommended Action If there was an unexpected job failure associated with this event, contact your vendor's customer support for assistance. FICN-1090 Message Message Type Severity DevTeraEgr:FICON Selective Reset:Path=0x State=0x statArray=0x cmdArray=0x tflags=0x sflags=0x. LOG ERROR Probable Cause Indicates the FICON channel issued a Selective Reset for a device that was active in emulation. Recommended Action If there was an unexpected job failure associated with this event, contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 403 5 FICN-1091 FICN-1091 Message Message Type Severity DevTeraEgr:FICON Selective Reset:Path=0x Elapsed Time=. seconds. LOG ERROR Probable Cause Indicates the FICON channel issued a Selective Reset sequence for a device. Recommended Action If there was an unexpected job failure associated with this event, contact your vendor's customer support for assistance. FICN-1092 Message Message Type Severity DevTeraEgr:FICON Purge received Path=0x. LOG ERROR Probable Cause Indicates the FICON channel issued a Purge Path command sequence for a device. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. FICN-1093 Message Message Type Severity DevTeraIng:Auto Sense Data received on Path=0x Bytes0-0xB=0x. LOG WARNING Probable Cause Indicates the FICON tera write pipelining processed sense data from a FICON device. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. 404 Fabric OS Message Reference 53-1002749-01 FICN-1094 5 FICN-1094 Message DevTeraIng:UnusualStatus:WriteCancelSelr:Generating Final Ending Status Path=0x. Message Type LOG Severity INFO Probable Cause Indicates the FICON tera write pipeline is completing an emulated Selective Reset sequence. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. FICN-1095 Message Message Type Severity DevTeraIng:Device level exception found for Path=0x: Oxid=0x. LOG ERROR Probable Cause Indicates an active emulation device delivered a Device Level Exception frame to the emulation processing. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. FICN-1096 Message Message Type Severity HostTeraEgr:CmdReject Sense Data Rcvd:Path=0x LastCmds=0x SenseData:Bytes0-0xB=0x. LOG ERROR Probable Cause Indicates an active Teradata emulation sequence received a Command Reject Sense from the device. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 405 5 FICN-1097 FICN-1097 Message Message Type Severity HostTeraEgr:AS Link Level Reject (LRJ) from CU Rx Path=0x LastCmd=0x LastStatus=0x. LOG ERROR Probable Cause Indicates a Link Level Reject (LRJ) received from a device indicates that the Control Unit has lost the logical path to the Logical Partition (LPAR). Recommended Action If this was an unexpected event; contact your vendor's customer support for assistance. FICN-1098 Message Message Type Severity HostTeraIng:FICON Cancel received Path=0x state=0x. LOG WARNING Probable Cause Indicates a job was canceled during a Write Tape Pipelining. Recommended Action If this was an unexpected event (cancel is normally an operator event), contact your vendor's customer support for assistance. FICN-1099 Message Message Type Severity HostTeraIng::FICON Selective Reset:Path=0x state=0x LastCmds=0x LastStatus=0x. LOG ERROR Probable Cause Indicates that the channel recognized a timeout condition and issued a Selective Reset. Recommended Action If this was an unexpected event, contact your vendor's customer support for assistance. 406 Fabric OS Message Reference 53-1002749-01 FICN-1100 5 FICN-1100 Message Message Type Severity HostTeraIng:FICON Selective Reset:Path=0x Elapsed Time=. seconds. LOG ERROR Probable Cause Indicates that protocol errors in emulation in the Control Unit or network errors can cause Selective Reset. Recommended Action If this was an unexpected event, contact your vendor's customer support for assistance. FICN-1101 Message Message Type Severity HostTeraIng:FICON Purge received:Path=0x. LOG WARNING Probable Cause Indicates a Purge Path was received from the locally connected FICON channel. This is performed during the path recovery. Recommended Action If this was an unexpected event, contact your vendor's customer support for assistance. FICN-1102 Message Message Type Severity HostTeraIng:LRJ received on Path=0x lastCmds=0x lastStatus=0x treating as system reset event. LOG WARNING Probable Cause Indicates a Link Level Reject (LRJ) from a FICON channel indicates that the channel believes that it no longer has a path established to the Control Unit. Recommended Action This is normally an unexpected event; contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 407 5 FICN-1103 FICN-1103 Message DevTeraIngr:Exceptional Status rcvd on Path=0x state=0x status=0x. Message Type LOG Severity INFO Probable Cause Indicates that the status (0x0D or 0x05) indicating the device is going down was received from the device or error status (including Unit Check 0x02) is received from an active emulation device. Recommended Action The device doing down is a normal event during pipelining and not the unit check. If there are associated I/O error messages with this event, contact your vendor's customer support for assistance. FICN-1104 Message DevTeraEgr:Device Ready on Path=0x. Message Type LOG Severity INFO Probable Cause Indicates the Teradata device has been initialized and is ready for emulation operations. Recommended Action No action is required. FICN-1105 Message Message Type Severity DevTeraIng:LRJ received on Path=0x lastCmds=0x lastStatus=0x treating as system reset event. LOG WARNING Probable Cause Indicates a Link Level Reject (LRJ) from a FICON channel indicates that the channel does not have a path established to the Control Unit. Recommended Action This is normally an unexpected event; contact your vendor's customer support for assistance. 408 Fabric OS Message Reference 53-1002749-01 FICN-1106 5 FICN-1106 Message Message Type Severity DevPrintEgr:AS Link Level Reject (LRJ) from Chan on Path=0x LastCmd=0x LastStatus=0x. LOG ERROR Probable Cause Indicates the FICON channel indicated in the path issued a Link Level Reject (LRJ) frame for a sequence from the device. Recommended Action If there was a job failure associated with this event, contact your vendor's customer support for assistance. FICN-1107 Message Message Type Severity DevPrintEgr:FICON Cancel received Path=0x state=0x tflags=0x sflags=0x. LOG WARNING Probable Cause Indicates the FICON channel issued a Cancel sequence for a device in emulation. Recommended Action If there was an unexpected job failure associated with this event, contact your vendor's customer support for assistance. FICN-1108 Message Message Type Severity DevPrintEgr:FICON Tera Cancel:Path=0x Elapsed Time=. seconds. LOG WARNING Probable Cause Indicates the FICON channel issued a Cancel sequence for a device in emulation. Recommended Action If there was an unexpected job failure associated with this event, contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 409 5 FICN-1109 FICN-1109 Message Message Type Severity DevPrintEgr:FICON Selective Reset:Path=0x State=0x statArray=0x cmdArray=0x tflags=0x sflags=0x. LOG ERROR Probable Cause Indicates the FICON channel issued a Selective Reset for a device that was active in emulation. Recommended Action If there was an unexpected job failure associated with this event, contact your vendor's customer support for assistance. FICN-1110 Message Message Type Severity DevPrintEgr:FICON Selective Reset:Path=0x Elapsed Time=. seconds. LOG ERROR Probable Cause Indicates the FICON channel issued a Selective Reset sequence for a device. Recommended Action If there was an unexpected job failure associated with this event, contact your vendor's customer support for assistance. FICN-1111 Message Message Type Severity DevPrintEgr:FICON Purge received Path=0x. LOG ERROR Probable Cause Indicates the FICON channel issued a Purge Path command sequence for a device. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. 410 Fabric OS Message Reference 53-1002749-01 FICN-1112 5 FICN-1112 Message Message Type Severity DevPrintIng:Auto Sense Data received on Path=0x Bytes0-0xB=0x. LOG WARNING Probable Cause Indicates the FICON Printer write pipelining processed sense data from a FICON device. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. FICN-1113 Message Message Type Severity DevPrintIng:LRJ received on Path=0x lastCmds=0x lastStatus=0x treating as system reset event. LOG WARNING Probable Cause Indicates a Link Level Reject (LRJ) from a FICON channel indicates that the channel does not have a path established to the Control Unit. Recommended Action This is normally an unexpected event; contact your vendor's customer support for assistance. FICN-1114 Message Message Type Severity DevPrintIng:Device level exception found for Path=0x: Oxid=0x. LOG ERROR Probable Cause Indicates an active emulation device delivered a Device Level Exception frame to the emulation processing. Recommended Action If there was an unexpected job failure or I/O Error associated with this event, contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 411 5 FICN-1115 FICN-1115 Message Message Type Severity HostPrintEgr:CmdReject Sense Data Rcvd:Path=0x LastCmds=0x SenseData:Bytes0-0xB=0x. LOG ERROR Probable Cause Indicates an active Print emulation sequence received Command Reject Sense data from the device. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. FICN-1116 Message Message Type Severity HostPrintEgr:AS Link Level Reject (LRJ) from CU Rx Path=0x LastCmd=0x LastStatus=0x. LOG ERROR Probable Cause Indicates that a Link Level Reject (LRJ) was received from a device indicating that the Control Unit has lost the logical path to the Logical Partition (LPAR). Recommended Action If this was an unexpected event; contact your vendor's customer support for assistance. FICN-1117 Message Message Type Severity HostPrintIng:FICON Cancel received Path=0x state=0x. LOG WARNING Probable Cause Indicates a job was canceled during Print write pipelining. Recommended Action If this was an unexpected event (cancel is normally an operator event), contact your vendor's customer support for assistance. 412 Fabric OS Message Reference 53-1002749-01 FICN-1118 5 FICN-1118 Message Message Type Severity HostPrintIng::FICON Selective Reset:Path=0x state=0x LastCmds=0x LastStatus=0x. LOG ERROR Probable Cause Indicates that the channel recognized a timeout condition and issued a Selective Reset. Recommended Action If this was an unexpected event, contact your vendor's customer support for assistance. FICN-1119 Message Message Type Severity HostPrintIng:FICON Selective Reset:Path=0x Elapsed Time=. seconds. LOG ERROR Probable Cause Indicates that the channel recognized a timeout condition and issued a Selective Reset. Recommended Action If this was an unexpected event, contact your vendor's customer support for assistance. FICN-1120 Message Message Type Severity HostPrintIng:FICON Purge received:Path=0x. LOG WARNING Probable Cause Indicates a Purge Path was received from the locally connected FICON channel. This is performed during FICON path recovery. Recommended Action If this was an unexpected event, contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 413 5 FICN-1121 FICN-1121 Message Message Type Severity HostPrintIng:LRJ received on Path=0x lastCmds=0x lastStatus=0x treating as system reset event. LOG WARNING Probable Cause Indicates than a Link Level Reject (LRJ) received from a FICON channel indicates that the channel no longer has a path established to the Control Unit. Recommended Action This is normally an unexpected event; contact your vendor's customer support for assistance. FICN-1122 Message DevPrintIng:UnusualStatus:WriteCancelSelr:Generating Final Ending Status Path=0x. Message Type LOG Severity INFO Probable Cause Indicates the FICON Print write pipeline sequence has received unit check status. Recommended Action If there was an unexpected job failure or I/O error associated with this event, contact your vendor's customer support for assistance. FICN-2005 Message FICON VEPort Feature Change verified Xrc <1 or 0 - XRC Emulation Enabled or Disabled> TapeWrt <1 or 0 - Tape Write Emulation Enabled or Disabled> TapeRd <1 or 0 - FICON Tape Read Emulation Enabled or Disabled> TinTir <1 or 0 FICON TIN/TIR Emulation Enabled or Disabled> DvcAck <1 or 0 - FICON Device Level Ack Emulation Enabled or Disabled> RdBlkId <1 or 0 - FICON Write Emulation Read Block ID Emulation Enabled or Disabled>. Message Type LOG Severity INFO Probable Cause Indicates the configuration was changed manually. Recommended Action No action is required. 414 Fabric OS Message Reference 53-1002749-01 FICN-2006 5 FICN-2006 Message Message Type Severity FICON VEPort Feature Change failed Xrc <1 or 0 - XRC Emulation Enabled or Disabled> TapeWrt <1 or 0 - Tape Write Emulation Enabled or Disabled> TapeRd <1 or 0 - FICON Tape Read Emulation Enabled or Disabled> TinTir <1 or 0 FICON TIN/TIR Emulation Enabled or Disabled> DvcAck <1 or 0 - FICON Device Level Ack Emulation Enabled or Disabled> RdBlkId <1 or 0 - FICON Write Emulation Read Block ID Emulation Enabled or Disabled>. LOG WARNING Probable Cause Indicates the FCIP Tunnel ID associated with the FICON tunnel must be down or disabled for a feature change to become effective. Recommended Action Disable the applicable FCIP tunnel to make the feature change effective. FICN-2064 Message Ingress Abort:Oxid=0x:Unknown Path on VEPort= from SID=0x to DID=0x. Message Type LOG Severity INFO Probable Cause Indicates an abort operation has been received from a local FC interface for an exchange. Recommended Action If there were associated I/O errors at the same time as this event, contact your vendor's customer support for assistance. FICN-2065 Message Egress Abort:Oxid=0x:Unknown Path on VEPort= from SID=0x to DID=0x. Message Type LOG Severity INFO Probable Cause Indicates an abort operation has been received from a peer FC interface for an exchange. Recommended Action If there were associated I/O errors at the same time as this event, contact your vendor's customer support for assistance. Fabric OS Message Reference 53-1002749-01 415 5 FICN-2066 FICN-2066 Message Message Type Severity MemAllocFailed for VEport= could not create required structure. LOG WARNING Probable Cause Indicates an internal resource limit has been encountered so that additional control block memory could not be allocated. Recommended Action This is an unexpected event; either the maximum number of emulation devices are already in use or there is an internal memory leak. Contact your vendor's customer support for assistance. FICN-2082 Message Message Type Severity EmulEls:CSWR_RSCN received on VEPort= Domain=0x Port=0x. LOG WARNING Probable Cause Indicates an attached port which had a FICON emulated path established has logged out from the switch. Recommended Action This may be an unexpected event; contact your vendor's customer support for assistance. FICN-2083 Message Message Type Severity EmulEls:SW_RSCN received on VEPort= Domain=0x Port=0x. LOG WARNING Probable Cause Indicates an attached port with the established FICON emulated path has logged out from the switch. Recommended Action This may be an unexpected event; contact your vendor's customer support for assistance. 416 Fabric OS Message Reference 53-1002749-01 FICN-2085 5 FICN-2085 Message FICON or FCP Emulation Enabled FCIP Tunnel is Up on VEPort=. Message Type LOG Severity INFO Probable Cause Indicates a FICON or Fibre Channel Protocol (FCP) emulation-enabled FCIP tunnel has been established successfully to the peer switch. Recommended Action No action is required. FICN-2086 Message Message Type Severity FICON or FCP Emulation Enabled FCIP Tunnel is Down on VEport=. LOG ERROR Probable Cause Indicates a FICON or Fibre Channel Protocol (FCP) emulation-enabled FCIP tunnel to the peer switch has been terminated. Recommended Action This is an unexpected event; contact your vendor's customer support for assistance. FICN-2087 Message Message Type Severity FICON connected 3900 printer discovered Path=0x-invalid compression mode. LOG ERROR Probable Cause Indicates that FICON Printer emulation is enabled, but cannot be performed for this device because the compression mode on the tunnel is not set to None or Aggressive. Recommended Action If you desire FICON Printer emulation for this device, modify the tunnel compression mode to None (mode 0) or Aggressive (mode 3). Fabric OS Message Reference 53-1002749-01 417 5 FICU-1001 FICU Messages FICU-1001 Message Message Type Severity . LOG ERROR Probable Cause Indicates that one of the configuration management functions have failed. The key variable is a component of the Fabric OS configuration database and is for support use only. The error variable is an internal error number. Recommended Action Execute the haFailover command on the switch if it has redundant control processors (CPs) or reboot the switch. Execute the switchStatusShow command to check if the flash memory is full. If the flash memory is full, execute the supportSave command to clear the core files. FICU-1002 Message Message Type Severity : Failed to get RNID from Management Server Domain= rc=. LOG ERROR Probable Cause Indicates that the fibre connectivity control unit port (FICON-CUP) daemon failed to get the switch request node ID (RNID) from the management server because of a Fabric OS problem. The domain variable displays the domain ID of the target switch for this RNID. The error variable is an internal error number. Recommended Action If this is a bladed switch, execute the haFailover command. If the problem persists, or if this is a non-bladed switch, download a new firmware version using the firmwareDownload command. FICU-1003 Message Message Type Severity : FICON-CUP License Not Installed: (). LOG WARNING Probable Cause Indicates that the fibre connectivity control unit port (FICON-CUP) license is not installed on the switch. Recommended Action Execute the licenseShow command to check the installed licenses on the switch. The switch cannot be managed using FICON-CUP commands until the FICON-CUP license is installed. Contact your switch supplier for a FICON-CUP license. Execute the licenseAdd command to add the license to your switch. 418 Fabric OS Message Reference 53-1002749-01 FICU-1004 5 FICU-1004 Message Message Type Severity Probable Cause : Failed to set FICON Management Server (FMS) mode: conflicting PID Format:, FMS Mode:. LOG WARNING Indicates that a process ID (PID) format conflict was encountered. The core PID format is required for fibre connectivity control unit port (FICON-CUP). The pid_format variable displays the PID format currently running on the fabric, and is one of the following: • • • 0 - VC-encoded PID format 1 - Core PID format 2 - Extended-edge PID format The mode variable displays whether FICON Management Server (FMS) mode is enabled, and is one of the following: 0 means FMS mode is enabled and 1 means FMS mode is disabled. Recommended Action To enable FMS mode, the core PID format must be used in the fabric. Change the PID format to core PID using the configure command and re-enable FMS Mode using the ficonCupSet command. Refer to the Fabric OS Administrator's Guide for information on core PID mode. FICU-1005 Message Message Type Severity Failed to initialize , rc = . LOG ERROR Probable Cause Indicates that initialization of a module within the fibre connectivity control unit port (FICON-CUP) daemon failed. Recommended Action Download a new firmware version using the firmwareDownload command. FICU-1006 Message Message Type Severity Probable Cause Control Device Allegiance Reset: (Logical Path: 0x:0x). LOG WARNING Indicates that the path with the specified process ID (PID) and channel image ID lost allegiance to a fibre connectivity control unit port (FICON-CUP) device. Fabric OS Message Reference 53-1002749-01 419 5 FICU-1007 Recommended Action Check if the FICON channel corresponding to the PID in the message is functioning correctly. FICU-1007 Message Message Type Severity : Failed to allocate memory while performing . LOG WARNING Probable Cause Indicates that memory resources are low. This may be a transient problem. Recommended Action Check the memory usage on the switch using the memShow command. If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the supportSave command and contact your switch service provider. FICU-1008 Message FMS mode has been enabled. Port(s): have been disabled due to port address conflict. Message Type LOG Severity INFO Probable Cause Indicates that the specified ports were disabled when the FICON Management Server (FMS) mode was enabled. This is due to a port address conflict or the port address being reserved for the CUP management port. Recommended Action No action is required. FICU-1009 Message Message Type Severity FMS Mode enable failed due to insufficient frame filtering resources on some ports. LOG WARNING Probable Cause Indicates that the frame filtering resources required to enable FICON Management Server mode (fmsMode) were not available on some of the ports. Recommended Action Execute the haFailover command on the switch if it has redundant control processors (CPs) or reboot the switch. 420 Fabric OS Message Reference 53-1002749-01 FICU-1010 5 FICU-1010 Message Message Type Severity FMS mode enable failed due to port(s) with areas 0xFE or 0xFF is(are) connected to device(s). LOG WARNING Probable Cause Indicates that the FICON Management Server (FMS) mode was not enabled because ports with areas 0xFE or 0xFF are connected to devices. Recommended Action Disable ports with areas 0xFE or 0xFF using the portDisable command. FICU-1011 Message Message Type FMS mode has been enabled. AUDIT | LOG Class CFG Severity INFO Probable Cause Indicates that the FICON Management Server mode (fmsMode) has been enabled. Recommended Action No action is required. FICU-1012 Message Message Type FMS mode has been disabled. AUDIT | LOG Class CFG Severity INFO Probable Cause Indicates that the FICON Management Server mode (fmsMode) has been disabled. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 421 5 FICU-1013 FICU-1013 Message Message Type Severity Host data file cannot be reset to proper size. LOG WARNING Probable Cause Indicates that the file system is too full to create the host data file at the proper size. Recommended Action Execute the switchStatusShow command to check if the flash memory is full. If the flash memory is full, execute the supportSave command to clear the core files. FICU-1017 Message Message Type Severity FMSMODE enable failed because reserved area is bound to a device. LOG WARNING Probable Cause Indicates that one or both of the reserved areas 0xFE and 0xFF is bound to a device. Recommended Action Execute the wwnaddress --show command to display all devices currently bound to areas. Execute the wwnaddress --unbind command to release the reserved area from the device. FICU-1018 Message Message Type Severity FMSMODE enable noticed swapped ports. LOG WARNING Probable Cause Indicates that some ports are swapped at the time FICON Management Server mode (fmsMode) is enabled. Recommended Action Verify the expected FICON port address and port number relationship. For more information, refer to the "FICON and FICON CUP in Virtual Fabrics" section of the FICON Administrator's Guide. 422 Fabric OS Message Reference 53-1002749-01 FICU-1019 5 FICU-1019 Message Message Type Switch has been set offline by LP(). AUDIT | LOG Class CFG Severity INFO Probable Cause Indicates that the FICON Management Server (FMS) has disabled the switch. Recommended Action No action is required. FICU-1020 Message Message Type Port Addrs () have been Blocked by . AUDIT | LOG Class CFG Severity INFO Probable Cause Indicates that the FICON Management Server (FMS) has blocked ports. Recommended Action No action is required. FICU-1021 Message Message Type Port Addrs () have been Unblocked by . AUDIT | LOG Class CFG Severity INFO Probable Cause Indicates the FICON Management Server (FMS) has unblocked ports. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 423 5 FICU-1022 FICU-1022 Message Detected FC8-48 and/or FC8-64 that are not manageable when FMS mode is enabled. Message Type LOG Severity INFO Probable Cause Indicates the presence of unmanageable ports such as 48-port blade ports in the virtual fabric-disabled chassis. Recommended Action No action is required. For more information on the FICON CUP restrictions, refer to the FICON Administrator's Guide. FICU-1023 Message Detected 48 port blade when FMS mode is enabled. Message Type LOG Severity INFO Probable Cause Indicates presence of 48-port blade ports in the switch. Recommended Action No action is required. For more information on the FICON CUP restrictions, refer to the FICON Administrator's Guide. FICU-1024 Message Detected 64 port blade when FMS mode is enabled. Message Type LOG Severity INFO Probable Cause Indicates presence of 64-port blade ports in the switch. Recommended Action No action is required. For more information on the FICON CUP restrictions, refer to the FICON Administrator's Guide. 424 Fabric OS Message Reference 53-1002749-01 FKLB-1001 5 FKLB Messages FKLB-1001 Message Message Type Severity exchange overlapped, pid=. LOG WARNING Probable Cause Indicates that the FC kernel driver has timed out the exchange while the application is still active. When the FC kernel driver reuses the exchange, the application will overlap. This happens on a timed-out exchange; it automatically recovers after the application times out the exchange. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 425 5 FLOD-1001 FLOD Messages FLOD-1001 Message Message Type Severity Probable Cause Unknown LSR type: port , type . LOG WARNING Indicates that the link state record (LSR) type is unknown. The following two LSR header types are the only known types: • • Recommended Action 1 - Unicast 3 - Multicast No action is required; the record is discarded. FLOD-1003 Message Message Type Severity Link count exceeded in received LSR, value = . LOG WARNING Probable Cause Indicates that the acceptable link count received was exceeded in the link state record (LSR). Recommended Action No action is required; the record is discarded. FLOD-1004 Message Message Type Severity Excessive LSU length = . LOG | FFDC ERROR Probable Cause Indicates that the link state update (LSU) size exceeds the value the system can support. Recommended Action Reduce the number of switches in the fabric or reduce the number of redundant inter-switch links (ISLs) between two switches. 426 Fabric OS Message Reference 53-1002749-01 FLOD-1005 5 FLOD-1005 Message Message Type Severity Invalid received domain ID: . LOG WARNING Probable Cause Indicates that the received link state record (LSR) contained an invalid domain number. Recommended Action No action is required; the LSR is discarded. FLOD-1006 Message Message Type Severity Transmitting invalid domain ID: . LOG WARNING Probable Cause Indicates that the transmitted link state record (LSR) contained an invalid domain number. Recommended Action No action is required; the LSR is discarded. Fabric OS Message Reference 53-1002749-01 427 5 FSPF-1001 FSPF Messages FSPF-1001 Message Message Type Severity Input Port out of range. LOG ERROR Probable Cause Indicates that the specified input port number is out of range because it does not exist on the switch. Recommended Action No action is required. This is a temporary kernel error that does not affect your system. If the problem persists, execute the supportSave command and contact your service provider. FSPF-1002 Message Wrong neighbor ID () in Hello message from port , expected ID = . Message Type LOG Severity INFO Probable Cause Indicates that the switch has received a wrong domain ID from its neighbor switch in the HELLO message from a specified port. This may happen when a domain ID for a switch has been changed. Recommended Action No action is required. FSPF-1003 Message Message Type Severity Remote Domain ID out of range, input port = . LOG ERROR Probable Cause Indicates that the specified remote domain ID is out of range. Recommended Action No action is required. The frame is discarded. 428 Fabric OS Message Reference 53-1002749-01 FSPF-1005 5 FSPF-1005 Message Message Type Severity Wrong Section Id
, should be
, input port = . LOG ERROR Probable Cause Indicates that an incorrect section ID was reported from the specified input port. The section ID is part of the fabric shortest path first (FSPF) protocol and is used to identify a set of switches that share an identical topology database. Recommended Action This switch does not support a non-zero section ID. Any connected switch from another manufacturer with a section ID other than 0 is incompatible in a fabric of Brocade switches. Disconnect the incompatible switch. FSPF-1006 Message Message Type Severity FSPF Version not supported, input port = . LOG ERROR Probable Cause Indicates that the fabric shortest path first (FSPF) version is not supported on the specified input port. Recommended Action Update the FSPF version by running the firmwareDownload command. All current versions of the Fabric OS support FSPF version 2. FSPF-1007 Message Message Type Severity ICL triangular topology is broken between the neighboring domains: and . Please fix it ASAP. LOG ERROR Probable Cause Indicates that the inter-chassis link (ICL) triangular topology is broken and becomes linear. It may cause frame drop or performance slowdown. Recommended Action Connect the two domains using ICL or regular inter-switch link (ISL) to form a triangular topology. Fabric OS Message Reference 53-1002749-01 429 5 FSPF-1008 FSPF-1008 Message ICL triangular topology is formed among the domains: (self), , and . Message Type LOG Severity INFO Probable Cause Indicates that the inter-chassis link (ICL) triangular topology is formed. Recommended Action No action is required. FSPF-1009 Message 16G ICL topology is not recommended on local domain . Message Type LOG Severity INFO Probable Cause Indicates that the current 16 Gbps inter-chassis link (ICL) topology is not recommended. Recommended Action Use the switchShow, islShow, and lsdbShow commands to identify the neighbor domains that violate the ICL connectivity requirement. FSPF-1010 Message ICL Topology is valid on local domain . Message Type LOG Severity INFO Probable Cause Indicates that the current inter-chassis link (ICL) topology is valid for routing from the local switch. Recommended Action No action is required. FSPF-1011 Message Message Type Severity Probable Cause 430 16G ICL topology is unbalanced. LOG WARNING Indicates that the current configuration of inter-chassis link (ICL) paths are unbalanced. Fabric OS Message Reference 53-1002749-01 FSPF-1012 Recommended Action 5 Investigate current ICL configuration to ensure that all recommendations for cabling are satisfied. FSPF-1012 Message All existing ICL topology imbalances have been corrected. Message Type LOG Severity INFO Probable Cause Indicates that the existing inter-chassis link (ICL) configuration that was resulting in an unbalanced topology has been corrected. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 431 5 FSS-1001 FSS Messages FSS-1001 Message Message Type Severity Component () dropping HA data update (). LOG WARNING Probable Cause Indicates that an application has dropped a high availability (HA) data update. Recommended Action For a dual control processor (CP) system, enable the HA state synchronization using the haSyncStart command. For non-bladed systems, restart the switch using the reboot command. If the problem persists, execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the supportSave command and contact your switch service provider. FSS-1002 Message Message Type Severity Component () sending too many concurrent HA data update transactions (). LOG WARNING Probable Cause Indicates that an application has sent too many concurrent high availability (HA) data updates. Recommended Action For a dual CP system, enable the HA state synchronization using the haSyncStart command. For non-bladed systems, restart the switch using the reboot command. If the problem persists, execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the supportSave command and contact your switch service provider. FSS-1003 Message Message Type Severity Component () misused the update transaction () without marking the transaction begining. LOG WARNING Probable Cause Indicates that the Fabric OS state synchronization (FSS) service has dropped the update because an application did not set the transaction flag correctly. Recommended Action For a dual CP system, enable the high availability (HA) state synchronization using the haSyncStart command. For non-bladed systems, restart the switch using the reboot command. If the problem persists, execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the supportSave command and contact your switch service provider. 432 Fabric OS Message Reference 53-1002749-01 FSS-1004 5 FSS-1004 Message Message Type Severity Memory shortage. LOG ERROR Probable Cause Indicates that the system ran out of memory. Recommended Action Execute the memShow command to view memory usage in the switch. For a dual CP system, enable the high availability (HA) state synchronization using the haSyncStart command. For non-bladed systems, restart the switch using the reboot command. If the problem persists, execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the supportSave command and contact your switch service provider. FSS-1005 Message Message Type Severity FSS read failure. LOG WARNING Probable Cause Indicates that the read system call to the Fabric OS state synchronization (FSS) device has failed. Recommended Action If the problem persists, execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the supportSave command and contact your switch service provider. FSS-1006 Message Message Type Severity No FSS message available. LOG WARNING Probable Cause Indicates that data is not available on the Fabric OS state synchronization (FSS) device. Recommended Action If the problem persists, execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the supportSave command and contact your switch service provider. Fabric OS Message Reference 53-1002749-01 433 5 FSS-1007 FSS-1007 Message Message Type Severity : Faulty Ethernet connection. LOG CRITICAL Probable Cause Indicates that the Ethernet connection between the active control processor (CP) and the standby CP is not healthy. This error occurs when the standby CP does not respond to a request from the active CP within five seconds. This usually indicates a problem with the internal Ethernet connection and the disruption of the synchronization process. Recommended Action Execute the supportShow or supportSave command to validate the network configuration and then execute the haSyncStart command to restore the high availability (HA) synchronization. If the problem persists, contact your switch service provider. FSS-1008 Message Message Type Severity FSS Error: . LOG CRITICAL Probable Cause Indicates that a Fabric OS state synchronization (FSS) error has occurred. Recommended Action Execute the supportSave command and contact your switch service provider. FSS-1009 Message Message Type Severity FSS Error: . LOG ERROR Probable Cause Indicates that a Fabric OS state synchronization (FSS) error has occurred for the specified component. The error code is displayed in the message. Recommended Action Execute the supportSave command and contact your switch service provider. 434 Fabric OS Message Reference 53-1002749-01 FSS-1010 5 FSS-1010 Message Message Type Severity FSS Warning: . LOG WARNING Probable Cause Indicates that a Fabric OS state synchronization (FSS) error may have occurred. Recommended Action Execute the supportSave command and contact your switch service provider. FSS-1011 Message FSS Info: . Message Type LOG Severity INFO Probable Cause Indicates a Fabric OS state synchronization (FSS) related informational message. Recommended Action No action is required. Fabric OS Message Reference 53-1002749-01 435 5 FSSM-1002 FSSM Messages FSSM-1002 Message HA State is in sync. Message Type LOG Severity INFO Probable Cause Indicates that the high availability (HA) state of the active control processor (CP) is in synchronization with the HA state of the standby CP. If the standby CP is healthy, the failover will be nondisruptive. Recommended Action No action is required. FSSM-1003 Message Message Type Severity HA State out of sync. LOG WARNING Probable Cause Indicates that the high availability (HA) state of the active control processor (CP) is out of synchronization with the HA state of the standby CP. If the active CP failover occurs when the HA state is out of synchronization, the failover is disruptive. Recommended Action If this message was logged as a result of a user-initiated action (such as running the reboot command), no action is required. Otherwise, execute the haSyncStart command on the active CP to resynchronize the HA state. If the HA state does not synchronize, execute the haDump command to diagnose the problem. If the problem persists, execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the supportSave command and contact your switch service provider. FSSM-1004 Message Message Type Severity Probable Cause Incompatible software version in HA synchronization. LOG CRITICAL Indicates that the active control processor (CP) and the standby CP in a dual CP system are running firmware that is incompatible with each other. If the active CP fails, the failover will be disruptive. In a switch system, this message is logged when a firmware upgrade or downgrade was invoked. The new firmware version is not compatible with the current running version. This causes a disruptive firmware upgrade or downgrade. 436 Fabric OS Message Reference 53-1002749-01 FSSM-1004 Recommended Action 5 For a dual CP system, execute the firmwareDownload command to load compatible firmware on the standby CP. Fabric OS Message Reference 53-1002749-01 437 5 FW-1001 FW Messages FW-1001 Message