Brocade Fabric OS Message Reference8 Brocade Fabric OS Message Reference 53-1005249-02 Brocade...

53-1005249-0229 December 2017

Brocade Fabric OS Message Reference, 8.2.0

Supporting Fabric OS 8.2.0

REFERENCE GUIDE

Copyright © 2017 Brocade Communications Systems LLC. All Rights Reserved.

Brocade and the stylized B logo are among the trademarks of Brocade Communications Systems LLC. Broadcom, the pulse logo, and Connecting everything are among the trademarks of Broadcom. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries

Brocade, a Broadcom Limited Company, reserves the right to make changes without further notice to any products or data herein to improve reliability, function, or design. Information furnished by Brocade is believed to be accurate and reliable. However, Brocade does not assume any liability arising out of the application or use of this information, nor the application or use of any product or circuit described herein, neither does it convey any license under its patent rights nor the rights of others.

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.

Contents

PrefaceDocument conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Text formatting conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Command syntax conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Notes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Brocade resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Contacting Brocade Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Brocade customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Brocade OEM customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Document feedback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

About this DocumentSupported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Brocade Gen 5 platform (16-Gbps) fixed-port switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Brocade Gen 5 platform (16-Gbps) DCX Backbone family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Brocade Gen 6 platform (32-Gbps) fixed-port switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Brocade Gen 6 platform (32-Gbps) Backbone family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Changes made for this release (53-1005249-01) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Introduction to System MessagesOverview of system messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

System message types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Message severity levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23System error message logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Configuring syslog message destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24System logging daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24System console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25SNMP trap recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25SNMP inform recipient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Port logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Changing the swEventTrap severity level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Commands for displaying and configuring system message logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Displaying message content on the switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Configuring system messages and attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Configuring event auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Disabling a RASLog message or module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Enabling a RASLog message or module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Setting the severity level of a RASLog message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Enabling quiet time for a specified message type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Disabling quiet time for a specified message type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Brocade Fabric OS Message Reference 353-1005249-02

Displaying system message logs and attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Displaying RASLog messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Displaying RASLog messages one message at a time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Displaying audit messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Displaying FFDC messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Displaying the status of system messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Displaying the severity level of RASLog messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Displaying the configured quiet time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Displaying RASLog messages by severity level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Displaying RASLog messages by message ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Displaying messages on a slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Viewing RASLog messages from Web Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Clearing the system message logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Clearing the system message log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Clearing the audit message log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Reading the system messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Reading a RAS system message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Reading an audit message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Responding to a system message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Looking up a system message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Gathering information about the problem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Support for personnel troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

System module descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Audit Messages

FFDC Messages

Log Messages

Fabric OS System MessagesAG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191AMPM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219AN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220ASVR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222AUTH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222BCM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242BL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244BLS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265BLZ Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267BM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270C2 Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275C3 Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284C4 Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295CAL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307CCFG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307CDR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311CH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318CHS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318CNM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320

4 Brocade Fabric OS Message Reference53-1005249-02

CNMC Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .343CONF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .344DIAG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351DOT1 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352ECC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355EM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .356ERCP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378ESM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379ESS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401ESW Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .404EVMD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407FABR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407FABS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .426FBC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .430FCMC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431FCOE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431FCPD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .440FCPH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441FCR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .445FICN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .480FICU Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524FKLB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .532FLOD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .533FSPF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .535FSS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .540FSSM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .544FV Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .545HAM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .553HAMK Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .559HIL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .560HLO Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .585HMON Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .586HSL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .586HTTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .589IPAD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591IPS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .593ISNS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .596KAC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .600KSWD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .605KTRC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .606L2SS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .608L3SS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610LACP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610LFM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611LIC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613LOG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614LSDB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618MAPS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .620MCAST_SS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .925MFIC Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931


MM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .932MPTH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .932MQ Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .933MS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .935MSTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941NBFS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .944NS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946NSM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .953ONMD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .959PDM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961PDTR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .969PLAT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970PMGR Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975PORT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979PS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997PSWP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .998QOSD Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1001RAS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1002RCS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1013RMON Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1018RPCD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1018RTE Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1020RTWR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1021SCN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1023SEC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1024SFLO Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1114SNMP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117SPM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1120SRM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1134SS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1135SSLP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1140SSMD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1140SULB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1154SWCH Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174SYSC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1190SYSM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1191TRCE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1194TS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1198UCID Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1202UCST Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1219UFCS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1224UPTH Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1226VS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1227WEBD Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1230XTUN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1232ZONE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1248


Preface

• Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7• Brocade resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8• Contacting Brocade Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8• Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Document conventionsThe document conventions describe text formatting conventions, command syntax conventions, and important notice formats used in Brocade technical documentation.

Text formatting conventionsText formatting conventions such as boldface, italic, or Courier font may be used in the flow of the text to highlight specific words or phrases.

Command syntax conventionsBold and italic text identify command syntax components. Delimiters and operators define groupings of parameters and their logical relationships.

Format Description

bold text Identifies command names

Identifies keywords and operands

Identifies the names of user-manipulated GUI elements

Identifies text to enter at the GUI

italic text Identifies emphasis

Identifies variables

Identifies document titles

Courier font Identifies CLI outputIdentifies command syntax examples

Convention Description

bold text Identifies command names, keywords, and command options.

italic text Identifies a variable.

value In Fibre Channel products, a fixed value provided as input to a command option is printed in plain text, for example, --show WWN.

[ ] Syntax components displayed within square brackets are optional.

Default responses to system prompts are enclosed in square brackets.


Brocade resources

Notes, cautions, and warningsNotes, cautions, and warning statements may be used in this document. They are listed in the order of increasing severity of potential hazards.

NOTEA Note provides a tip, guidance, or advice, emphasizes important information, or provides a reference to related information.

Brocade resourcesVisit the Brocade website to locate related documentation for your product and additional Brocade resources.

You can download additional publications supporting your product at www.brocade.com. Select the Brocade Products tab to locate your product, then click the Brocade product name or image to open the individual product page. The user manuals are available in the resources module at the bottom of the page under the Documentation category.

To get up-to-the-minute information on Brocade products and resources, go to MyBrocade. You can register at no cost to obtain a user ID and password.

Release notes are available on MyBrocade under Product Downloads.

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

Contacting Brocade Technical SupportAs a Brocade customer, you can contact Brocade Technical Support 24x7 online, by telephone, or by e-mail. Brocade OEM customers contact their OEM/Solutions provider.

{ x | y | z } A choice of required parameters is enclosed in curly brackets separated by vertical bars. You must select one of the options.

In Fibre Channel products, square brackets may be used instead for this purpose.

x | y A vertical bar separates mutually exclusive elements.

< > Nonprinting characters, for example, passwords, are enclosed in angle brackets.

... Repeat the previous element, for example, member[member...].

\ Indicates a “soft” line break in command examples. If a backslash separates two lines of a command input, enter the entire command at the prompt without the backslash.

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

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


http://www.brocade.comhttp://my.brocade.comhttp://my.brocade.comhttp://www.brocade.com/products/index.page

Document feedback

Brocade customersFor product support information and the latest information on contacting the Technical Assistance Center, go to http://www.brocade.com/services-support/index.html.

If you have purchased Brocade product support directly from Brocade, use one of the following methods to contact the Brocade Technical Assistance Center 24x7.

Brocade OEM customersIf you have purchased Brocade product support from a Brocade OEM/Solution Provider, contact your OEM/Solution Provider for all of your product support needs.

• OEM/Solution Providers are trained and certified by Brocade to support Brocade® products.• Brocade provides backline support for issues that cannot be resolved by the OEM/Solution Provider.• Brocade Supplemental Support augments your existing OEM support contract, providing direct access to Brocade expertise.

For more information, contact Brocade or your OEM.

• For questions regarding service levels and response times, contact your OEM/Solution Provider.

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

Send your feedback to [email protected].

Provide the publication title, part number, and as much detail as possible, including the topic heading and page number if applicable, as well as your suggestions for improvement.

TABLE 1

Online Telephone

Preferred method of contact for nonurgent

issues:

• My Cases through MyBrocade• Software downloads and licensing tools• Knowledge Base

Required for Sev 1-Critical and Sev

2-High issues:

• Continental US: 1-800-752-8061• Europe, Middle East, Africa, and Asia Pacific:

+800-AT FIBREE (+800 28 34 27 33)• For areas unable to access toll free number:

+1-408-333-6061• Toll-free numbers are available in many countries.


http://www.brocade.com/services-support/index.htmlhttps://fedsso.brocade.com/sps/BrocadeIDPSF/saml20/logininitial?RequestBinding=HTTPPost&PartnerId=https://brocade.my.salesforce.comhttp://my.brocade.com/wps/myportal/!ut/p/b1/hY7NDoIwEIQfaXe7FdNjoWhoqBgThPZiejJNFC_G50eIV8scJ9_8QABPRCz3XDCMEKb4Sff4Tq8pPuC0OKG4lQd9ZclMnbUVNkdz6ZV1AssdDF_EZ5BWrg3OuIpqwYRno7Ahw1bXSiDiL49_pHErP0DInlwerEBm4ul9P2LSM-kStbY!/http://kb.brocade.com/kb/index?page=homehttp://www.brocade.com/services-support/international_telephone_numbers/index.page

Document feedback


About this Document

• Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11• What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Supported hardware and softwareIn those instances in which procedures or parts of procedures documented here apply to some devices but not to others, this list identifies which devices are supported by Fabric OS 8.2.0 and which are not.

The following hardware platforms are supported by Fabric OS 8.2.0 .

Brocade Gen 5 platform (16-Gbps) fixed-port switches• Brocade 6505 Switch• Brocade M6505 Blade Server SAN I/O Module• Brocade 6510 Switch• Brocade 6520 Switch• Brocade 6543 blade server SAN I/O module • Brocade 6545 blade server SAN I/O module • Brocade 6546 blade server SAN I/O module • Brocade 6547 blade server SAN I/O module • Brocade 6548 blade server SAN I/O module • Brocade 7840 Extension Switch

Brocade Gen 5 platform (16-Gbps) DCX Backbone family• Brocade DCX 8510 Backbone-4• Brocade DCX 8510 Backbone-8

Brocade Gen 6 platform (32-Gbps) fixed-port switches• Brocade G610 Switch• Brocade G620 Switch• Brocade G630 Switch

Brocade Gen 6 platform (32-Gbps) Backbone family• Brocade X6 Director-4 • Brocade X6 Director-8


Supported hardware and software

NOTEAlthough many different software and hardware configurations are tested and supported by Brocade Communication Systems, LLC. for Fabric OS 8.2.0 documenting all possible configurations and scenarios is beyond the scope of this document.

Fabric OS 8.2.0 provides features that interoperate with the Brocade Analytics Monitoring Platform running Fabric OS 7.4.0_amp. For more information about the Brocade Analytics Monitoring Platform and Fabric OS 8.2.0, you can find content on MyBrocade.


http://my.brocade.com

What’s new in this document

What’s new in this document The following changes have been made in this document for 8.2.0 release

Changes made for this release (53-1005249-01)• Added Audit log enhancements in Introduction to System Messages Chapter.• Newly added modules:

- AMPM- CH- QOSD- UCID- UFCS

• Messages that were added:- AG-1049 to AG-1085- AUTH-3009- BL-1062- BL-1063- BL-1064- BL-1065- C3-1022- C4-1044- CONF-1046- CONF-1047- CONF-1048- CONF-1049- CONF-1050- CONF-1051- CONF-1052- EM-1100- EM-1101- EM-1226- EM-1227- ESM-2801- ESM-2802- ESM-2803- ESS-2001- ESS-2002- FABR-1059- FABR-1060- FABR-3000- FCOE-1008- FCPH-1010- FCPH-1011- FCPH-1012



- FCPH-1013- FCR-1114- FICU-1026- FICU-1030- FICU-1031- FICU-1032- FV-1017- HAM-1017- HAM-1018- HIL-1652- HTTP-3001- HTTP-3002- HTTP-3003- HTTP-3004- IPAD-1005- IPS-1008- IPS-1009- IPS-1010- LIC-1000- LIC-1001- MAPS-2004 to MAPS-2135- MAPS-2140 to MAPS-2247- MAPS-2256 to MAPS-2331- MAPS-2336 to MAPS-2675- MAPS-2700 to MAPS-2883- MAPS-2936 to MAPS-2959- NS-1017- NS-1018- NS-1019- PLAT-1001- PORT-1027 to PORT-1055- PSWP-1008- RAS-1009 to RAS-1016- RAS-3006- RAS-3007- RAS-3008- RTE-1002- RTE-1003- RTWR-1004- SEC-3043- SEC-3079- SEC-3080- SEC-3082- SEC-3083- SRM-1001



- SWCH-1042 to SWCH-1049- SYSM-1008- TS-1012- UCST-1032- UCST-1033- XTUN-3009- ZONE-1071 to ZONE-1074

• Messages that were changed:- AUTH-1038- AUTH-1045- AUTH-1049- BL-1061- C2-1014- C3-1014- C4-1014- CNM-3012- EM-1001- ESM-2101- FCOE-1007- FCOE-1010- FCOE-1034- FCOE-1039- FCPH-1003- FCPH-1004- FCPH-1009- FCR-1095- FCR-1110- FCR-1116- HAM-1016- HIL-1312- KAC-1006- SEC-3025- SEC-3034- SPM-1008- XTUN-1008- ZONE-1068- ZONE-1069

• Deleted messages- FCOE-1012- FCOE-1014- FCOE-1015- FCOE-1016- FCOE-1017- FCOE-1025



- FCOE-1026- FCOE-1028- FCOE-1031- FCOE-1045- FCOE-1046- FCOE-1047- FCOE-1048

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


Introduction to System Messages

• Overview of system messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17• Configuring syslog message destinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24• Changing the swEventTrap severity level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30• Commands for displaying and configuring system message logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32• Displaying message content on the switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33• Configuring system messages and attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34• Displaying system message logs and attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36• Clearing the system message logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41• Reading the system messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41• Responding to a system message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44• System module descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Overview of system messagesThis guide supports Fabric OS 8.2.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 the 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 typesFabric 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.

RASLog messagesRASLog 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 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 36.


Overview of system messages

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

The following is an example of an audit message.

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

For any given event, audit messages capture the following information:

• User Name: The name of the user who triggered the action.• User Role: The access level of the user, such as root or admin.• Event Name: The name of the event that occurred.• Event Information: Information about the event.

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

Fabric OS 8.2.0 generates component-specific audit messages.

Event auditing is a configurable feature, which is enabled by default. You can also enable event auditing using the auditCfg --enable command to send the events to a configured remote host. The system logging daemon (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 34. For more details, refer to “Displaying audit messages” on page 37 and “Reading an audit message” on page 42.

TABLE 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 changes related to Administration Domain.

7 LS You can audit changes related to Virtual Fabric (Logical Switch)

8 CLI You can audit the CLI commands issued on the switch.

9 MAPS You can audit changes related to Monitoring and Alerting Policy Suite (MAPS).

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.



Audit log enhancementsSeveral audit logs have been enhanced or added for security events. These are listed below.

• Failure to establish HTTPS connection along with the reason for failure.

• Failure to establish HTTPS connection if peer presents an invalid certificate with appropriate reason statement.

• Failure to establish an SSH session when switch acts as client (SSH/scp/sftp) including details of reason for failure and remote IP to which connection was attempted.

• Failure to establish an SSH session due to cipher configuration mismatch or invalid ciphers when switch acts as SSH server including details of reason for failure and remote IP to which connection was attempted. (Use of ciphers that are not compliant with CC are discouraged but not enforced by code. Hence SSH session will not fail in case of using a valid cipher configuration though it is not compliant with CC).

• Failure to establish an SSH session due to supported public key algorithm mismatch or invalid public key algorithm configuration when switch acts as SSH server including details of reason for failure and remote IP to which connection was attempted. (Use of public key algorithms that are not compliant with CC are discouraged but not enforced by code. Hence SSH session will not fail in case of using a valid public key algorithm though it is not compliant with CC).

• Failure to establish an SSH session due to supported MAC mismatch or invalid MAC configuration when switch acts as SSH server including details of reason for failure and remote IP to which connection was attempted. (Use of MAC that are not compliant with CC are discouraged but not enforced by code. Hence SSH session will not fail in case of using a valid MAC configuration though it is not compliant with CC).

• Failure to establish an SSH session due to supported key exchange algorithm mismatch or invalid key exchange algorithm configuration when switch acts as SSH server including details of reason for failure and remote IP to which connection was attempted. (Use of key exchange algorithms that are not compliant with CC are discouraged but not enforced by code. Hence SSH session will not fail in case of using a valid key exchange algorithm configuration though it is not compliant with CC).

• Failure to establish a TLS session due to cipher configuration mismatch or invalid ciphers when switch acts as TLS client (RADIUS, LDAP, SYSLOG) including details of reason for failure. (Use of ciphers that are not compliant with CC are discouraged but not enforced by code. Hence TLS session will not fail in case of using a valid cipher configuration though it is not compliant with CC).

• Failure to establish TLS connection when switch acts as TLS client (RADIUS, LDAP, SYSLOG) if peer presents an invalid certificate with appropriate reason statement.

• Failure to establish TLS connection when switch acts as TLS client (RADIUS, LDAP, SYSLOG) due to mutual authentication failure (using X509v3 certificates) with appropriate reason statement.

• Failure to establish a TLS session due to cipher configuration mismatch or invalid ciphers when switch acts as TLS server (https) including details of reason for failure. (Use of ciphers that are not compliant with CC are discouraged but not enforced by code. Hence TLS session will not fail in case of using a valid cipher configuration though it is not compliant with CC).

• Failure to establish a TLS session due to TLS protocol version configuration mismatch or invalid TLS protocol version when switch acts as TLS server (HTTPS) including details of reason for failure. (Use of TLS protocol versions that are not compliant with CC are discouraged but not enforced by code. Hence TLS session will not fail in case of using a valid cipher configuration though it is not compliant with CC).

• Failure to establish TLS connection when switch acts as TLS server (HTTPS) due to mutual authentication failure (using X509v3 certificates) with appropriate reason statement.



• Failure to establish TLS connection when switch acts as TLS server (HTTPS) if peer presents an invalid certificate with appropriate reason statement.

• Failure to establish TLS connection when switch acts as TLS server (HTTPS) and the distinguished name (DN) or subject alternative name (SAN) of the peer does not match the expected identifier for the peer with appropriate reason statement.

• Successful user authentication including details of username, interface used for login (SSH/ telnet/console/webtools), remote IP address from which user has connected, authentication mechanism used (RADIUS/LDAP/TACACS+/local).

• Failure to validate and X509v3 certificate including details of reason for failure.

• Failure to validate a CA certificate when BasicConstraints extension is not present or when CA flag is not set to true including details of reason for failure.

• Change of date on the switch.

• Query for existing firmware version or latest installed firmware version by administrator

• Firmware signature verification status (success or failure) before the firmware download process.

• Timeout expiry and logout of session due to session inactivity of a remote interactive session (SSH/telnet/webtools).

• Timeout expiry and logout of session due to session inactivity of a local interactive session (console)

• User initiated logout of session

• Successful or failed attempt of establishing a TLS client connection and terminating an existing TLS session (SYSLOG) including details of peer to which connection was made.

• Successful or failed attempt of establishing a TLS server connection or SSH connection and terminating an existing TLS session (HTTPS) or SSH session including details of peer to which connection was made.

• If certificate public key size is less than 2048 in case of TLS, event is audit logged (though connection is allowed).

• If certificate validation fails for "BasicConstraints" field, event is audit logged and connection is not allowed.

• If certificate validation fails for "CN" (common name) field, event is audit logged and connection is not allowed.

• If certificate validation fails for "Extended Key Usage" field, event is audit logged and connection is not allowed.

Audit messages related to SSHThese messages are used for

• Kex mismatch• Cipher mismatch• Key algorithm mismatch• MAC mismatch

Message template

Event: %s, %s, Info: %s.

Event NameEvent actionEven specific info



Indicates a failure to establish an SSH session.

Verify the security event was planned.If the security event was planned, no action is required. If the security event was not planned, takeappropriate action as defined by your enterprise security policy.

Example message

63 AUDIT, 2017/03/20-18:14:00 (UTC), [SEC-3076], INFO, SECURITY, NONE/NONE/NONE/None/CLI, None/sw0/FID128, , Event: SSH, Status: failed, Info: SSH Session establisment failed. Reason: no matching cipher found., IP Addr:10.70.12.112

Audit messages related to TLSThese messages are used for

• Wrong protocol version• Wrong ciphers• Wrong CA certificate• Server keys less than 2048

Message template



Indicates a failure to establish a TLS session.

Verify the security event was planned. If the security event was planned, noaction is required.If the security event was not planned, take appropriate action as defined by your enterprise securitypolicy.

Example message

84 AUDIT, 2017/03/20-18:33:13 (UTC), [SEC-3077], INFO, SECURITY,root/root/NONE/console/CLI, ad_0/sw0/FID 128, , Event: TLS SESSION,TLS handshake failed, Info: Wrong Protocol version number..

Audit messages related to certificate validation

These messages are used for all types of certification validation failure: keyusage, extended key usage, selfsigned certs , login withimporting CA cert, CN mismatch etc …. Openssl errors are presented in the info section as-is.

Message template


Event NameEvent action



Even specific info

Indicates that TLS Certificate Validation failed.

Verify the security event was planned.If the security event was planned, no action is required.If the security event was not planned, take appropriate action as defined by your enterprise securitypolicy.

Example message

94 AUDIT, 2017/03/20-18:37:04 (UTC), [SEC-3081], INFO, SECURITY,swadmin/admin/10.252.200.228/ssh/CLI, ad_0/sw0/FID 128, , Event: TLSSESSION, Certificate Validation failed, Info: Reason = unable to get local issuer certificate

Example messages for TLS initiation and termination

INFO, pizzabox12,2017/04/13-12:19:45, [SEC-3078], 54908, FID 3, INFO, pizzabox12,Event: TLS SESSION, TLS handshake, Info: Establishing TLS connection. Host=10.38.37.161.2017/04/13-12:19:46, [SEC-3078], 54909, FID 3, Event: TLS SESSION, TLS handshake, Info: Terminating TLS connection. Host=10.38.37.161

Audit messages related to when unsecure protocols are allowed or secure protocols are disabledThese messages are used in the following cases:

• When an ipfilter policy, that has HTTP port (80) enabled, is activated.

• When an ipfilter policy, that has telnet port (80) enabled, is activated.

• When an ipfilter policy, that has HTTPS port (443) disabled, is activated

Message template



Indicates that unsecure communication service is activated.

Verify the security event was planned.If the security event was planned, no action is required.If the security event was not planned, take appropriate action as defined by your enterprise securitypolicy.

Example messages for each of the above cases.

3 AUDIT, 2017/02/21-19:39:35 (UTC), [SEC-3075], INFO, SECURITY,root/root/NONE/console/CLI, ad_0/sw0/FID 128, , Event: ipfilter,HTTP PORT STATE: ACTIVE, Info: Activated ipfilter policy has activated HTTP port.4 AUDIT, 2017/02/21-19:39:35 (UTC), [SEC-3075], INFO, SECURITY,root/root/NONE/console/CLI, ad_0/sw0/FID 128, , Event: ipfilter,TELNET PORT STATE: ACTIVE, Info: Activated ipfilter policy has activated Telnet port.3 AUDIT, 2017/02/21-19:27:56 (UTC), [SEC-3075], INFO, SECURITY,



root/root/NONE/console/CLI, ad_0/sw0/FID 128, , Event: ipfilter,HTTPS PORT STATE: DROP, Info: Activated ipfilter policy has blocked HTTPS port.

FFDC messagesFirst 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. Enter 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 an 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 levelsTable 3 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.

System error message loggingThe 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 8196 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 persists across power cycles and switch reboots.

• The RASLog message text can be up to 256 characters long.• Trace dump, FFDC, and core dump files can be uploaded to the FTP server using the supportSave command.

TABLE 3 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 timeouts 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 the online and offline status of a fabric port.


Configuring syslog message destinations

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

• RASLog messages are streamed to the console, and are forwarded to the configured syslog servers and to the SNMP management station through 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.

Configuring syslog message destinationsYou can configure Fabric OS to send syslog messages to the following output locations:

• syslog daemon, • system console• SNMP management station.

System logging daemonThe 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 standard syslogd functionality. Configuring 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 syslogd as the logs on the host computer are then maintained in a single merged file for both CPs and sequential order. Otherwise, you must examine the error logs for both CPs, particularly for events such as firmwareDownload or haFailover which change the active CP.

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 serverTo 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. Use the syslogadmin --set -ip ip_address | hostname [-secure [-port port_num]] command to configure a secure or nonsecure syslog server to which system messages are forwarded. Secure syslog mode is disabled by default.

The following example configures an IPv4 nonsecure syslog server:

switch:admin> syslogadmin --set -ip 172.26.26.173The following example configures an IPv4 secure syslog server:

switch:admin> syslogadmin --set -ip 172.26.26.173 -secure -port 2000The following example configures a nonsecure syslog server using a hostname.



switch:admin> syslogadmin --set -ip win2k8-58-113You can configure up to six syslog servers to receive the syslog messages.

3. Enter the syslogadmin --show -ip command to verify the syslog configuration on the switch.

switch:admin> syslogadmin --show -ipsyslog.1 172.26.26.173syslog.2 win2k8-58-113You can remove a configured syslog server using the syslogadmin --remove -ip ip_address | hostname command.

System consoleThe system console displays RASLog messages, audit messages (if enabled), and panic dump messages. These messages are mirrored to the system console in addition to being saved in one of the system logs.

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. This command allows you to set the minimum severity level to be logged to the console. All error messages at that level or higher will be logged; all error messages below that level will not be displayed, but they are still recorded. 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.


2. Use 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. Enter the errFilterSet command to verify the configured filter settings.

switch:admin> errfiltersetconsole: filter severity = ERROR

SNMP trap recipientAn 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 notification, 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, repeat count, and description. The following severity levels are possible:

• None (0)• Critical (1)• Error (2)



• Warning (3)• Informational (4)• Debug (5)

By default, the severity level is set to None, implying that 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 swEventTrap severity level” on page 30.

NOTEAudit messages are not converted into swEventTrap.

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 on UDP port 162. To receive traps, the management station IP address must be configured on the switch. You can configure SNMPv1 and SNMPv3 hosts to receive traps.

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

Configuring the SNMPv1 trap recipientThe snmpConfig --set snmpv1 command allows you to specify the SNMP trap recipient. To configure the SNMPv1 host to receive the trap, perform the following steps.


2. Enter 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]

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

3. Enter 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 Trap recipient Severity level: 2SNMPv1:Enabled

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


2. Enter the snmpConfig --set snmpv3 command to configure the SNMP trap recipient. Ignore the step to enable the SNMP informs: SNMP Informs Enabled.


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

SNMPV3 Password Encryption Enabled (true, t, false, f): [false] tWarning: The encrypted password cannot be decrypted. Do you want to continue? (yes, y, no, n): [no] y

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



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

3. Enter the snmpConfig --show snmpv3 command to verify the SNMP agent configuration.

switch:admin> snmpconfig --show snmpv3SNMP Informs = 0 (OFF)SNMPV3 user password encrypted = 0 (OFF)SNMPv3 USM configuration:User 1 (rw): snmpadmin1Auth Protocol: noAuthPriv Protocol: noPrivUser 2 (rw): snmpadmin2Auth Protocol: MD5Priv Protocol: noPrivUser 3 (rw): snmpadmin3Auth Protocol: MD5Priv Protocol: DESUser 4 (ro): snmpuser1Auth Protocol: noAuthPriv Protocol: noPrivUser 5 (ro): snmpuser2Auth Protocol: noAuthPriv Protocol: noPrivUser 6 (ro): snmpuser3Auth Protocol: noAuthPriv Protocol: noPrivSNMPv3 Trap configuration:Trap Entry 1: 192.0.2.2Trap Port: 162Trap User: snmpadmin1Trap recipient Severity level: 1Trap Entry 2: fe80::224:1dff:fef6:0f21Trap Port: 162[...]

SNMP inform recipientThe SNMP inform notification 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. Informs are more reliable than traps, but 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 SNMP traps.

Configuring the SNMPv3 inform recipientTo configure an SNMPv3 host to receive SNMP informs, perform the following steps.


2. Enter the snmpConfig --set snmpv3 command to configure the inform recipient. When prompted to enable the SNMP informs, enter true or t. SNMP Informs are disabled by default.


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

SNMPV3 Password Encryption Enabled (true, t, false, f): [false] t



Warning: The encrypted password cannot be decrypted. Do you want to continue? (yes, y, no, n): [no] y

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

NOTETo 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. Enter the snmpConfig --show snmpv3 command to verify the SNMP agent configuration.

switch:admin> snmpconfig --show snmpv3SNMP Informs = 1 (ON)SNMPV3 user password encrypted = 0 (OFF)SNMPv3 USM configuration:


Changing the swEventTrap severity level

User 1 (rw): snmpadmin1Auth Protocol: noAuthPriv Protocol: noPrivEngine ID: 80:00:05:23:01:0a:23:34:21User 2 (rw): snmpadmin2Auth Protocol: MD5Priv Protocol: DESEngine ID: 80:00:05:23:01:0a:23:34:1bUser 3 (rw): snmpadmin3Auth Protocol: noAuthPriv Protocol: noPrivEngine ID: 00:00:00:00:00:00:00:00:00User 4 (ro): snmpuser1Auth Protocol: noAuthPriv Protocol: noPrivEngine ID: 00:00:00:00:00:00:00:00:00User 5 (ro): snmpuser2Auth Protocol: noAuthPriv Protocol: noPrivEngine ID: 00:00:00:00:00:00:00:00:00User 6 (ro): snmpuser3Auth Protocol: noAuthPriv Protocol: noPrivEngine ID: 00:00:00:00:00:00:00:00:00SNMPv3 Trap configuration:Trap Entry 1: 192.0.2.2Trap Port: 162Trap User: snmpadmin1Trap recipient Severity level: 4Trap Entry 2: 192.0.10.10Trap Port: 162Trap User: snmpadmin2Trap recipient Severity level: 4Trap Entry 3: No trap recipient configured yetTrap Entry 4: No trap recipient configured yetTrap Entry 5: No trap recipient configured yet

Port logsFabric OS maintains an internal log of all port activity, with each switch or logical switch maintaining 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 automatically 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. Port log functionality is completely separate from the system message log. Port logs are typically used to troubleshoot device connections.

To display the port logs for a particular port, enter the portLogShow command.

To display the specific events logged for each port, enter the portLogEventShow command.

Changing the swEventTrap severity levelWhen an event occurs and the event severity level is at or below the set severity level, the SNMP event trap notification, swEventTrap, is sent to the configured trap recipients. By default, the severity level is set at 0 (None), resulting in all event traps being sent. Use the snmpConfig --set mibCapability command to modify the severity level of swEventTrap.

To change the severity level of swEventTrap, perform the following steps.


Changing the swEventTrap severity level


2. Enter the snmpConfig --set mibCapability command to configure MIBs interactively. All supported MIBs and associated traps are displayed. You can change the desired severity for swEventTrap to 1 (Critical), 2 (Error), 3 (Warning), or 4 (Informational). The default value is 0.

switch:admin> snmpconfig --set mibcapabilityFE-MIB: YESSW-MIB: YESFA-MIB: YESFICON-MIB: YESHA-MIB: YESFCIP-MIB: YESISCSI-MIB: YESIF-MIB: YESBD-MIB: YESSW-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. Enter the snmpConfig --show mibCapability command to verify the severity level of swEventTrap.

switch:admin> snmpconfig --show mibcapabilityFE-MIB: YESSW-MIB: YESFA-MIB: YESFICON-MIB: YESHA-MIB: YESFCIP-MIB: YESISCSI-MIB: YESIF-MIB: YESBD-MIB: YESSW-TRAP: YES swFault: YES


Commands for displaying and configuring system message logs

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 system message logsTable 4 describes commands that you can use to view or configure the system message logs. Most commands require admin-level access privileges. For detailed information on required access levels and commands, refer to the Brocade Fabric OS Command Reference.

TABLE 4 Commands for viewing or configuring sy

Date post:	13-Jul-2020
Category:	Documents
Upload:	others
View:	40 times
Download:	3 times

Brocade Fabric OS Message Reference8 Brocade Fabric OS Message Reference 53-1005249-02 Brocade...

Documents