Networkadvisor 1400 Smia Devguide

53-1004153-01
07 January 2016
Brocade Network Advisor

SMI Agent
Developers Guide
Supporting Network Advisor 14.0.0

2016, Brocade Communications Systems, Inc.All Rights Reserved.
Brocade, Brocade Assurance, the B-wing symbol,ClearLink, DCX, Fabric OS, HyperEdge, ICX, MLX, MyBrocade, OpenScript, VCS,
VDX, Vplane, and Vyatta are registered trademarks, and Fabric Vision is a trademark 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 others.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning
any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to
this document at any time, without notice, and assumes no responsibility for its use. This informational document describes
features that may not be currently available. Contact a Brocade sales office for information on feature and product availability.
Export of technical data contained in this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. assume no liability or responsibility to any person or entity with respect
to the accuracy of this document or any loss, cost, liability, or damages arising from the information contained herein or the
computer programs that accompany it.
The product described by this document may contain open source software covered by the GNU General Public License or other
open source license agreements. To find out which open source software is included in Brocade products, view the licensing
terms applicable to the open source software, and obtain a copy of the programming source code, please visit http://
www.brocade.com/support/oscd.
Brocade Communications Systems, Incorporated

Corporate and Latin American Headquarters Asia-Pacific Headquarters
Brocade Communications Systems, Inc. Brocade Communications Systems China HK, Ltd.
130 Holger Way No. 1 Guanghua Road
San Jose, CA 95134 Chao Yang District
Tel: 1-408-333-8000 Units 2718 and 2818
Fax: 1-408-333-8101 Beijing 100020, China
E-mail: info@brocade.com Tel: +8610 6588 8888
Fax: +8610 6588 9999
E-mail: china-info@brocade.com
European Headquarters Asia-Pacific Headquarters
Brocade Communications Switzerland Srl Brocade Communications Systems Co., Ltd. (Shenzhen WFOE)
Centre Swissair Citic Plaza
Tour B - 4me tage No. 233 Tian He Road North
29, Route de l'Aroport Unit 1308 13th Floor
Case Postale 105 Guangzhou, China
CH-1215 Genve 15 Tel: +8620 3891 2000
Switzerland Fax: +8620 3891 2111
Tel: +41 22 799 5640 E-mail: china-info@brocade.com
Fax: +41 22 799 5641
E-mail: emea-info@brocade.com
Document History
Title Publication number Summary of changes Date
DCFM SMI Agent Developers Guide 53-1001361-01 New document March 2010
Brocade Network Advisor SMI Agent 53-1002169-01 Updated to support DCX and DCX-4S May 2011
Developers Guide switches. Updated profiles and
subprofiles to conform to SMI-S 1.5.
Brocade Network Advisor SMI Agent 53-1002534-01 Updated to support Brocade 6505 March 2012
Developers Guide switch, FC8-32E port blade, and FC8-
48E port blade. Updated AG class
diagram and Physical Package, Access
Points, Software, Blades, and Location
subprofiles data model.
Brocade Network Advisor SMI Agent 53-1001701-01 Updated to support Brocade 5430, December 2012
Developers Guide and Brocade 6520. Updated the Fabric
profile. Included enhancements for
SAN_Element.Name and AG class
diagram, included AG Physical
package support, and VF support for
Brocade 7800.
Title Publication number Summary of changes Date
Brocade Network Advisor SMI Agent 53-1002996-01 Updated to support Release 12.1.0. July 2013
Developers Guide
Brocade Network Advisor SMI Agent 53-1003061-01 Updated to support Release 12.2.0. February 2014
Developers Guide
Brocade Network Advisor SMI Agent 53-1003159-01 Updated to support Release 12.3.0 July 2014
Developers Guide
Brocade Network Advisor SMI Agent 53-1003750-01 Updated to support Release 12.4.0 April 2015
Developers Guide
Brocade Network Advisor SMI Agent 53-1003750-02 Updated to support Release 12.4.2 August 2015
Developers Guide
Brocade Network Advisor SMI Agent 53-1003750-03 Updated to support Release 12.4.3 December 2015
Developers Guide
Brocade Network Advisor SMI Agent 53-1004153-01 Updated to support Release 14.0.0 January 2016
Developers Guide
Contents
About This Document

How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Supported hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Whats new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Notes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Key terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Brocade resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Other industry resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Brocade Network Advisor SMI Agent support . . . . . . . . . . . . . . . . . . xiv
Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Chapter 1 Connecting to the Fabric

Role-Based Access Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Admin Domains and Brocade Network Advisor SMI Agent . . . . . . . . 2
Connecting to the Brocade Network Advisor SMI Agent. . . . . . . . . . . 2
Connecting the Brocade Network Advisor SMI Agent
when security is enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
when security is not enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Discovering a fabric and a host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Fabric discovery using SMIA extrinsic method. . . . . . . . . . . . . . . 3
Host discovery using SMIA extrinsic method . . . . . . . . . . . . . . . . 4
Discovery using SMIA Configuration Tool . . . . . . . . . . . . . . . . . . . 5
Chapter 2 Managed Object Format Files

Brocade Managed Object Format files . . . . . . . . . . . . . . . . . . . . . . . . 9
Additional MOF description specifications . . . . . . . . . . . . . . . . . . . . 10
Creating and deleting instances . . . . . . . . . . . . . . . . . . . . . . . . . 10
Deprecation qualifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Brocade Network Advisor SMI Agent Developers Guide v

53-1004153-01
Chapter 3 Profiles and Subprofiles
UML diagram conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
SMI profiles and subprofiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Other features supported by
Brocade Network Advisor SMI Agent . . . . . . . . . . . . . . . . . . . . . 15
Server profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Indications subprofile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Object manager adapter subprofile . . . . . . . . . . . . . . . . . . . . . . 17
Fabric profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Rules governing Brocade_SAN.Name. . . . . . . . . . . . . . . . . . . . . 17
Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Zone control and enhanced zone control subprofiles . . . . . . . . 22
Job control profile for SessionControlWithJob and
ActivateZoneSetWithJob . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Zoning behavior details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
SAN zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Fabric virtual fabrics subprofile . . . . . . . . . . . . . . . . . . . . . . . . . 33
Sample discovery configuration . . . . . . . . . . . . . . . . . . . . . . . . . 34
Blades subprofile support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Topology view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
FDMI subprofile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Switch profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Physical package, access points, software, blades, and
location subprofiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
CP blades (Brocade extension) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Supported classes and associations . . . . . . . . . . . . . . . . . . . . . 50
FC HBA profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Launch In Context profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
LIC names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Registration and data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
vi Brocade Network Advisor SMI Agent Developers Guide

53-1004153-01
CEE switch support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Topology supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Zoning support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
LAGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
CEE ACLs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
CEE maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Brocade 8470 FCoE embedded switch support . . . . . . . . . . . . 74
Support for Layer 3 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Brocade 8428 FCoE embedded switch support . . . . . . . . . . . . 77
Fabric switch partitioning subprofile . . . . . . . . . . . . . . . . . . . . . . . . . 77
Data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
FC routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Edge-to-edge device sharing (no FCIP configured
in backbone). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Backbone-to-edge device sharing (no FCIP configured
in backbone). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Backbone-to-edge device sharing
(using VEX_Port over FCIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Brocade Access Gateway and NPIV . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Access Gateway Physical Package . . . . . . . . . . . . . . . . . . . . . . . 92
Access Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
FRU profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
Data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
Data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
Chapter 4 Indications
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Alert indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Life-cycle indications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
Appendix A Brocade Network Advisor SMI Agent Error Codes
Brocade Network Advisor SMI Agent Developers Guide vii

53-1004153-01
viii Brocade Network Advisor SMI Agent Developers Guide
53-1004153-01
About This Document
In this chapter
How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Supported hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Whats new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Brocade Network Advisor SMI Agent support . . . . . . . . . . . . . . . . . . . . . . . . xiv
Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
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, Connecting to the Fabric provides information about getting the fabric connected.
Chapter 2, Managed Object Format Files provides information about the format files.
Chapter 3, Profiles and Subprofiles provides information about the profiles and subprofiles
supported by the Integrated Storage Management Initiative (SMI).
Chapter 4, Indications provides the alert and life-cycle indications of all profiles.
Appendix A, Brocade Network Advisor SMI Agent Error Codes explains the error codes in
Brocade Network Advisor SMI Agent.
The 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 Brocade Network Advisor SMI Agent 14.0.0,
documenting all possible configurations and scenarios is beyond the scope of this document.
Brocade Network Advisor SMI Agent Developers Guide ix

53-1004153-01
Supported hardware
The following switches are supported by Brocade Network Advisor SMI Agent 14.0.0:
Brocade 200E
Brocade 300
Brocade 4012
Brocade 4016
Brocade 4018
Brocade 4020
Brocade 4024
Brocade 4100
Brocade 4900
Brocade 5000
Brocade 5100
Brocade 5300
Brocade 5410
Brocade M5424
Brocade 5450
Brocade 5460
Brocade 5470
Brocade 5480
Brocade NX-220
Brocade 6505
Brocade M6505
Brocade 6510
Brocade 6520
Brocade 6547
Brocade 6548
Brocade 7500
Brocade 7500E
Brocade AP7600
Brocade 7800
Brocade 8000
Brocade 8470 FCoE
Brocade VA-40 FC 3
Brocade 7800 Extension Switch
Brocade 7840 Extension Switch
Brocade 8000 FCoE Switch
Brocade Encryption Switch
x Brocade Network Advisor SMI Agent Developers Guide

53-1004153-01
Brocade DCX
Brocade DCX-4S
Brocade DCX 8510-8 Backbone (8-slot)
Brocade DCX 8510-4 Backbone (4-slot)
Brocade G620
Brocade 6542
Brocade 6543
The following blades are supported on the Brocade DCX and DCX-4S switches:
FR4-18i Blade
FX8-24 Blade
FC10-6 Blade
FC8-16 port blade
FC8-32 port blade
FC8-48 port blade
FC8-64 port blade
FC16-64 port blade
FCOE10-24 DCX Blade
FS8-18 Encryption Blade
FX8-24 DCX Extension Blade
The following blades are supported on the Brocade DCX 8510-8 Backbone (8-slot) and Brocade
DCX 8510-4 Backbone (4-slot) switches:
FC8-32E port blade
FC8-48E port blade
The following HBA hardware platforms are supported by Brocade Network Advisor SMI Agent
14.0.0:
Brocade 415 Host Bus Adapter
Brocade 1860 Fabric Adapter
QLogic QLE2562-CK
QLogic QLE2672-CK
Whats new in this document

The following changes have been made since this document was last released:
Information that was added:
- Updated Supported hardware on page x.
Brocade Network Advisor SMI Agent Developers Guide xi

53-1004153-01
Information that was changed:
- Change of version number (14.0.0) wherever applicable.
Information that was deleted:
- None
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 in this document are as follows:
bold text Identifies command names
Identifies the names of user-manipulated GUI elements
Identifies keyword
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.
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.
xii Brocade Network Advisor SMI Agent Developers Guide

53-1004153-01
Key terms
For definitions specific to Brocade and Fibre Channel, see the technical glossaries on MyBrocade.
See Brocade resources on page xiii 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 purpose only.
Corporation Referenced trademarks and products
Microsoft Corporation Windows, Windows NT, Internet Explorer

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
Brocade Network Advisor SMI Agent Developers Guide xiii

53-1004153-01
For information about the Fibre Channel industry, visit the Fibre Channel Industry Association
website:
http://www.fibrechannel.org
Getting technical help

Contact your switch support supplier for hardware, firmware, and software support, including
product repairs and part ordering. To expedite your call, have the following information available:
1. General Information
Switch model
Switch operating system version
Software name and software version, if applicable
Error numbers and messages received
supportSave command output
Detailed description of the problem, including the switch or fabric behavior immediately
following the problem, and specific questions
Description of any troubleshooting steps already performed and the results
Serial console and Telnet session logs
syslog message logs
2. Switch Serial Number
The switch serial number and corresponding bar code are provided on the serial number
label, as illustrated below.
' "!&'
FT00X0054E9
3. World Wide Name (WWN)

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

Report any problems or issues in using the Brocade Network Advisor SMI Agent to the following
e-mail address:
support@brocade.com
When contacting support at Brocade, provide the following:
xiv Brocade Network Advisor SMI Agent Developers Guide

53-1004153-01
Brocade Network Advisor supportSave. Refer to the Brocade Network Advisor User Manual for
the steps involved in running the supportSave command.
Steps followed to produce the problem
Error messages received
Sample code exhibiting problem (if possible)
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.
Brocade Network Advisor SMI Agent Developers Guide xv

53-1004153-01
xvi Brocade Network Advisor SMI Agent Developers Guide
53-1004153-01
Chapterc
Connecting to the Fabric 1
In this chapter
Role-Based Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Admin Domains and Brocade Network Advisor SMI Agent. . . . . . . . . . . . . . . 2
Connecting to the Brocade Network Advisor SMI Agent . . . . . . . . . . . . . . . . . 2
Discovering a fabric and a host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Role-Based Access Control

Role-Based Access Control (RBAC) defines the capabilities that a user account has based on the
role the account has been assigned. For each role, there is a set of pre-defined permissions on the
jobs and tasks that can be performed on a fabric and its associated fabric elements.
The RBAC check is performed based on the value of the Storage Management Initiative (SMI) Agent
Operations privilege for Common Information Model Object Manager (CIMOM) client requests. The
following responses are received for the different values of the SMI Agent Operations privilege:
No Access - If you query the CIMOM without the SMI Agent Operations privilege, the following
WBEM Exception is returned.
CIM_ERR_ACCESS_DENIED: The specified principal does not have access to perform this
operation.
Read Only Access - If you have the Read Only Access privilege and try to perform any write
operation on any of the profiles, the following WBEM Exception is returned.
CIM_ERR_ACCESS_DENIED: The specified principal does not have access to perform this
operation.
The user is not restricted to perform the WBEM queries.
Read/Write Access - No restriction is imposed on any user who has Read/Write Access for the
SMI Agent Operations privilege.
All the Resource Grouping (fabrics and hosts) performed through the user management dialog
boxes is honored by the CIMOM. The resource grouping is not be applicable for filtering out
indications. The indications from all the fabrics managed by Brocade Network Advisor is
delivered irrespective of the resource grouped by the user.
If you select the Authentication mode as No Authentication, then all the previously specified
RBAC checks are performed on the credentials provided by you in the Authentication tab of the
Configuration Tool and the previously described behavior is observed.
If a user A changes the password of a user B who has logged in to CIMOM, the user B can
continue querying the CIMOM until Brocade Network Advisor expires the user B session.
You can retrieve all the information from the interop namespace and can perform the getclass
operations even if there is no access for the SMI Agent Operations privilege.
Refer to the Brocade Network Advisor User Manual for more information about RBAC.
Brocade Network Advisor SMI Agent Developers Guide 1

53-1004153-01
1 Admin Domains and Brocade Network Advisor SMI Agent
Admin Domains and Brocade Network Advisor SMI Agent

The Brocade Network Advisor SMI Agent does not support Admin Domains though they are
supported in Brocade Network Advisor. It is recommended to exclude fabrics containing Admin
Domains using the Resource Grouping option in the user dialog box that can be launched from the
Configuration Tool.
Connecting to the Brocade Network Advisor SMI Agent

This section describes how to connect to the Brocade Network Advisor SMI Agent when security is
enabled and when security is not enabled.

when security is enabled
Connect with the Brocade Network Advisor SMI Agent as shown in the following sample Java code.
The code samples use the Java Web Start (JWS) client library. Other client libraries might differ
slightly in syntax.
On Windows and Linux:
String strCIMOMIP = "https://localhost";
String strNameSpace = "root/brocade1";
String strUser = "BNA UserName";
String strPasswd = "BNA Password";
String nsStr = protocolType + "://" + hostname + ":" + portNum + "/" +
strNameSpace;
CIMNameSpace objCIMNameSpace = new CIMNameSpace(strCIMOMIP, strNameSpace);

UserPrincipal objUserPrincipal = new UserPrincipal(strUser);
PasswordCredential objPasswordCredential = new PasswordCredential(strPasswd);
CIMClient m_objClient = new CIMClient(objCIMNameSpace, objUserPrincipal,
objPasswordCredential);
CIMNameSpace objCIMNameSpace = new CIMNameSpace (nsStr);
NOTE
The existing mutual authentication certificate is retained while migrating to Network Advisor 12.4.2
from any previous versions. The user has to manually generate and import the mutual
authentication certificate using SMIA configuration tool, in case the default certificate is used.

when security is not enabled
You can connect to the SMI Agent using any UserPrincipal and PasswordCredential, as these are
not validated by the SMI Agent when security is not enabled.
For more information on authentication, refer to the authentication section in the Brocade Network
Advisor User Manual.
2 Brocade Network Advisor SMI Agent Developers Guide

53-1004153-01
Discovering a fabric and a host 1
Discovering a fabric and a host

You can discover, edit, and delete a fabric or a host in two ways:
Using the SMIA extrinsic method
Using the SMIA Configuration Tool
Fabric discovery using SMIA extrinsic method

The CIMOM fabric discovery process enables the user to discover and delete fabrics through an
extrinsic method implemented in the Brocade_DiscoveryService. It allows the user to edit the user
credentials and the Simple Network Management Protocol (SNMP) configurations so that a fabric
containing switches with different credentials and SNMP configurations can be managed
effectively.
Features supported
The following features are supported by the CIMOM fabric discovery:
Option to discover all types of Storage Area Network (SAN) fabrics supported by the Brocade
Network Advisor.
Option to edit the switch credentials and the SNMP configurations used to discover the fabric
after the fabric is discovered.
Option to delete a fabric based on the fabric CIM Object Path (COP).
If the discovery of one of the Virtual Fabric (VF) fails, the return parameter is set to
PARTIALLY_DISCOVERED and the out parameter contains the Fabric Identifier (FID) and the
error code of the fabric that failed to get discovered.
Limitations
The following are the limitations of the CIMOM fabric discovery:
All the contexts are discovered by default in the VF. The user cannot select the contexts to be
discovered, but can delete the unwanted contexts through the DeleteFabric extrinsic method.
No support for Monitor and un-monitor operations.
No provision to change the Seed switch.
No support to discover M model switches.
Data model
The Brocade_Fabric has two new additional properties, SeedSwitchWWN and SeedSwitchIP.
The connection setting of each switch is associated to the discovery service.
Every switch in the discovered fabric is represented with an instance of
Brocade_SwitchConnectionSettings. This instance gives the data to be provided in the discover
Fabric dialog box of the Brocade Network Advisor client, such as switch status, user ID, and so
on.
The discovery service is hosted on the management server.
Figure 1 shows the data model of the fabric discovery through the SMIA extrinsic method.

53-1004153-01
1 Discovering a fabric and a host
FIGURE 1 Fabric discovery data model
Host discovery using SMIA extrinsic method

The CIMOM host discovery process enables the user to discover and delete hosts through an
extrinsic method implemented in the Brocade_DiscoveryService.
Features supported
The following features are supported by the CIMOM host discovery process:
Option to discover all types of hosts supported by Brocade Network Advisor.
Option to delete a host based on the HostDiscovered COP provided.
Option to receive the status of the host discovery information maintained in the
Brocade_HostDiscovered class.
Option to receive the status of discovery or deletion requests on execution of the DiscoverHost
and DeleteHost methods.
Limitations
The following are the limitations of the CIMOM host discovery process:
Supports only direct discovering of the host either through its IP address or its name, but does
not support for discovery from fabric or Virtual Machine (VM) Manager.
Editing the host discovery information through the CIMOM is not supported.
The history of the deleted host is not maintained in the CIMOM.

53-1004153-01
Data model
The Brocade_HostDiscovered class gives the discovery information of each host associated to
the Discovery service.
The discovery service is hosted on the management server.
Figure 2 shows the data model of the host discovery through the SMIA extrinsic method.
FIGURE 2 Host discovery data model
Discovery using SMIA Configuration Tool

The fabric and host can be discovered, edited, and deleted using the SMIA Configuration Tool. The
Home tab includes the Fabric Discovery and Host Discovery links to discover the fabric and host
respectively.
Figure 3 shows the fabric discovery through the SMIA Configuration Tool.

53-1004153-01
FIGURE 3 Fabric discovery using SMIA Configuration Tool
Figure 4 shows the host discovery through the SMIA Configuration Tool.

53-1004153-01
FIGURE 4 Host discovery using SMIA Configuration Tool
For more information related to fabric and host discovery, refer to the Brocade Network Advisor
User Manual.

53-1004153-01

53-1004153-01
Chapter
Managed Object Format Files 2
In this chapter
Brocade Managed Object Format files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Additional MOF description specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Brocade Managed Object Format files

Brocade supplies Managed Object Format (MOF) files for managing Brocade objects.
The following top-level files load MOF files into specific namespaces:
BrocadeNamespace.mof links MOF files loaded in the root/brocade1 namespace.
InteropNamespace.mof links MOF files loaded in the interop namespace.
Table 1 lists the files that contain Brocade MOF definitions.
TABLE 1 Brocade Managed Object Format files
MOF filename Description
BrocadeAccessGateway.mof Access Gateway

BrocadeAccessPoint.mof Access Point subprofile
BrocadeAgent.mof CIMOM Agent
BrocadeAGStatistics.mof AGFCPort statistics
BrocadeBlade.mof Blade subprofile
BrocadeCEEACL.mof CEE ACL discovery and configuration
BrocadeCEEMap.mof CEE Map discovery and configuration
BrocadeEthernet.mof Ethernet switch discovery
BrocadeExtender.mof FCIP-capable switch modeling
BrocadeFabric.mof Fabric profile
BrocadeFabricDiscovery.mof Fabric Discovery
BrocadeFCHBA.mof FC HBA profile
BrocadeFCSwitch.mof FC Switch profile
BrocadeFDMI.mof FDMI subprofile
BrocadeFRU.mof Fan, Power Supply, Sensors profiles
BrocadeIndications.mof Indications
BrocadeJobControl.mof JobControl subprofile
BrocadeLAG.mof LAG discovery and configuration

53-1004153-01
2 Additional MOF description specifications
TABLE 1 Brocade Managed Object Format files (Continued)

MOF filename Description
BrocadeLaunchInContext.mof Launch In Context profile

BrocadePartitioning.mof FabricVirtualFabrics subprofile
FCR subprofile
BrocadePhysicalPackage.mof Location subprofile
Physical Package subprofile
BrocadeProfile.mof Profile Registration
BrocadeSoftware.mof Software subprofile
BrocadeSwitchStatistics.mof SwitchFCPort statistics
BrocadeTopologyView.mof Topology view
BrocadeVLAN.mof VLAN discovery and configuration
BrocadeZoning.mof Zone Control and SAN zoning subprofile
NOTE
The Brocade subclasses do not automatically override all of the properties in the superclass. The
properties that are not overridden have a null value unless the superclass has a default value that
is defined in the MOF.
When the property in the MOF is defined to be of type sint16, then the equivalent Java type is
java.lang.Short.
Additional MOF description specifications

The Brocade MOF files contain additional specification-related information in the Description
qualifier. The following situations are described:
If a given instance of a class can be created or deleted by the Brocade Network Advisor SMI
Agent
If a given class or property applies only to specific switch firmware versions
Creating and deleting instances

If instances of a class can be intrinsically created and deleted, the following line is included in the
Description qualifier:
Instances of this class can be created and deleted by a client
If instances of a class can only be created, the following line is included in the Description qualifier:
Instances of this class can be created by a client
If instances of a class can only be deleted, the following line is included in the Description qualifier:
Instances of this class can be deleted by a client

53-1004153-01
Additional MOF description specifications 2
For example:
[Provider("java:com.brocade.api.cim.provider.zoning.Brocade_ZoneSetProvider"),
Description (
"Brocade_ZoneSet is a container of zones.\n\n"
"Instances of this class can be deleted by a client.")]
class Brocade_ZoneSet: CIM_ZoneSet {
Deprecation qualifier
Instance classes, association classes, properties, or extrinsic methods that have the Common
Information Model (CIM) qualifier deprecated in the MOF definition will continue to be implemented
in the Brocade Network Advisor SMI Agent. If a new implementation is documented, you should use
the new implementation as soon as possible to minimize backward-compatibility issues.

53-1004153-01
2 Additional MOF description specifications

53-1004153-01
Chapter
Profiles and Subprofiles 3
In this chapter
UML diagram conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
SMI profiles and subprofiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Server profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Fabric profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Switch profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
CP blades (Brocade extension). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
FC HBA profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Launch In Context profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
CEE switch support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Fabric switch partitioning subprofile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
FC routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Brocade Access Gateway and NPIV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
FRU profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
UML diagram conventions

This chapter provides Unified Modeling Language (UML) diagrams depicting the Brocade additions
to the Brocade Network Advisor SMI Agent. Each UML diagram corresponds to the Brocade
Managed Object Format (MOF) file of the same name.
Figure 5 illustrates the conventions used in the UML diagrams.
FIGURE 5 UML diagram convention

53-1004153-01
3 SMI profiles and subprofiles
SMI profiles and subprofiles

Table 2 lists the features supported by the Brocade Network Advisor SMI Agent. All SMI-S profiles
and subprofiles conforms to SMI-S 1.4. Other profiles and subprofiles are vendor extensions.
TABLE 2 SMI profiles and subprofiles

Profile Subprofile SMI-S version
Server Indications 1.4

Profile Registration 1.0.0
Object Manager Adapter 1.4
Fabric Fabric Profile 1.4
Zone Control 1.4
Enhanced Zoning and Enhanced Zoning Control 1.4
FDMI 1.2
FabricVirtualFabrics 1.2
FabricView 1.5
Switch Switch Profile 1.3
Blades 1.4
Physical Package 1.3
Software 1.4
Access Points 1.3
Location 1.4
FabricSwitchPartitioning 1.2
Host FC HBA Profile 1.3
FC Initiator Ports Subprofile 1.3
Fan, Power Supply, and Fan Profile 1.0.0
Sensor
Sensors Profile 1.0.0
Power Supply Profile 1.0.0
Security Role-Based Authorization (CEE ACL only) 1.0.0
FC Router Inter-Fabric Routing Profile 1.5
Launch In Context Launch In Context Profile 1.5
Access Gateway (AG) and N_Port Virtualizer Profile 1.5
Node Port Initialized
Physical Package 1.5
Virtualization (NPIV)

53-1004153-01
Server profile 3
Other features supported by

Brocade Network Advisor SMI Agent
The following are the additional features supported by Brocade Network Advisor SMI Agent:
Support for Fibre Channel Router (FCR), modeled through the FabricSwitchPartitioning
subprofile
Names
Support for the Converged Enhanced Ethernet (CEE) switch
Support for Zoning Session operations through Job Control
Support for selected indications
SAN zoning
Support for fabric discovery and host discovery
Server profile
The Server profile is supported by the Web-Based Enterprise Management (WBEM) Solutions J
WBEM Server CIMOM. The Brocade Network Advisor SMI Agent is a combination of two products,
the CIMOM and the provider product. Each product supports its software as shown in Figure 6.
NOTE
The Brocade Network Advisor SMI Agent's J WBEM Server has been upgraded from version 3.4.3 to
version 3.9.0. The 64 bit Network Advisor will contain a 64 bit JServer with it and the 32 bit Network
Advisor will contain a 32 bit JServer.

53-1004153-01
3 Server profile
FIGURE 6 Server profile
Indications subprofile
The Indications subprofile is supported by the WBEM Solutions J WBEM Server CIMOM as shown in
Figure 7.

53-1004153-01
Fabric profile 3
FIGURE 7 Indications profile
Object manager adapter subprofile

The object manager adapter subprofile is supported by the WBEM Solutions J WBEM Server
CIMOM.
Fabric profile
The Brocade Network Advisor SMI Agent supports the Storage Networking Industry Association
(SNIA) Fabric profile, which defines the model and functions of a storage network for topology and
zoning control.
A Brocade_SAN (CIM_AdminDomain) instance represents a SAN containing one or more
Brocade_Fabric (CIM_AdminDomain) instances that are physically interconnected. A SAN and
a fabric are considered to be a group of components that operate together as a single system
and should be managed as such. The containment of Brocade_Fabric instances to
Brocade_SAN instances is through the associated Brocade_FabricInSAN
(CIM_ContainedDomain).
A Brocade_SAN instance in CIM is keyed by the property name with an associated optional
property, NameFormat. Name is opaque and NameFormat identifies how the property name is
generated. In the case of Brocade_SAN, the property NameFormat is set to WWN. Simple
fabric - Brocade_SAN.Name is the principal WWN of the fabric.
A fabric or SAN instance both inheriting CIM_AdminDomain are differentiated using the
OtherIdentifyingInfo property.
For Brocade_SAN, OtherIdentifyingInfo = SAN
For Brocade_Fabric, OtherIdentifyingInfo = FABRIC
For both Brocade_SAN and Brocade_Fabric, IdentifyingDescriptions = SNIA:DetailedType
From a SMI perspective, all fabrics which are physically connected are considered to be contained
in the same SAN.
Rules governing Brocade_SAN.Name

The following are the rules that govern the naming of SANs:
In virtual fabrics with dedicated ISL between the base switches where all virtual fabrics have
been discovered, Brocade_SAN.Name is the principal WWN of the base fabric.

53-1004153-01
3 Fabric profile
In virtual fabrics with dedicated ISL between the base switches where some of virtual fabrics
have been discovered but there is no base fabric.
- If the base fabric is discovered, Brocade_SAN.Name is the principal WWN of the base
fabric.
- If the base fabric is not discovered, the virtual fabrics will be disjointed and in each fabric
one SAN instance will be generated.
In Virtual fabrics with no dedicated ISL between the base switches but with a dedicated ISL
between one of the discovered virtual fabrics.
- In the absence of a dedicated ISL between the base switches, no actual logical fabrics
exist except for those which have a dedicated ISL. The virtual fabrics will be disjointed and
in each fabric one SAN instance will be generated.
A FCR setup where the backbone fabric and edge fabrics have been discovered,
Brocade_SAN.Name is the principal WWN of the backbone fabric.
A FCR setup where only one or more edge fabrics have been discovered.
- In the absence of the backbone, each edge fabric is associated to its own SAN instance
and the Brocade_SAN.Name is the principal WWN of that edge fabric.
When a single edge fabric is connected to more than one separate backbone fabric, all the
fabrics will be discovered as a single SAN. The Brocade_SAN.Name is the principal WWN of
one of the backbone fabric.
A fabric containing a CEE switch, Brocade_SAN.Name is the principal WWN of the Fibre
Channel fabric with the switch.
In a simple Fibre Channel fabric, Brocade_SAN.Name is the principal WWN of the fabric.
Registration
Figure 8 shows the SNIA profile registration profile model to advertise the Fabric profile and its
subprofiles.

53-1004153-01
Fabric profile 3
FIGURE 8 Fabric profile registration
Data model
Figure 9 shows the Fabric profile data model with the classes and properties that are supported to
conform to the Fabric profile. Only those properties that are mandatory are considered.

53-1004153-01
3 Fabric profile
FIGURE 9 Fabric profile

53-1004153-01
Fabric profile 3
NOTE
The following properties are mapped with the value specified to differentiate between
Brocade_Fabric and Brocade_SAN instances.
Brocade_Fabric instance:
OtherIdentifyingInfo[] = {"Fabric"}
IdentifyingDescriptions[] = {"SNIA:DetailedType"}
Brocade_SAN instance:
OtherIdentifyingInfo[] = {"SAN"}
IdentifyingDescriptions[] = {"SNIA:DetailedType"}
NOTE
The SwitchId property will be populated only for switches running FOS 7.1.0 onwards.
Brocade_SAN.ElementName properties
The following are the properties of Brocade_SAN.ElementName:
Brocade_SAN.ElementName is a descriptive name to identify the SAN.
The default value for ElementName is the Brocade_SAN.Name property value.
Supports the set operation that is used to set the user-friendly name to SAN. The name can be
up to 15 characters.
The Brocade_SAN.ElementName will not get reset unless all the fabrics in the SAN have been
deleted from Brocade Network Advisor.
If the principal switch of the fabric changes then the associated SAN name for the SAN will be
retained.
For SAN consisting of multiple fabrics SAN name would be retained until all the fabrics in the
SAN get deleted.
For multiple fabrics managed by BNA merge, the name of the SAN whose SAN key is retained
becomes the new SAN ElementName.
For SAN that splits into multiple fabrics, the SAN which has the same name as the original SAN
would retain its name.
NOTE
The default value for Brocade_SAN.ElementName is the Brocade_SAN.Name property value.
For more information about Brocade_SAN.ElementName default values, refer to Rules governing
Brocade_SAN.Name on page 17.
Limitations
The following are the limitations of the Brocade_SAN.ElementName:
The ElementName is changed whenever the SAN WWN is changed.
The SAN user-friendly name is deleted when the fabric is deleted. For example, assume a
fabric with switch1 as principal switch and you configure a SAN Element Name.
- If the firmware is upgraded in the switch1 and it goes down momentarily, then switch2
becomes the principal switch in that fabric and the Element Name is changed to default.
- When the switch1 comes active and becomes the principal switch, then the configured
SAN ElementName is reset to the configured name.

53-1004153-01
3 Fabric profile
The SAN element name is reset to the default value when the principal switch WWN is changed
during fabric merge or segmentation.
- For example, assume there are two switch fabrics where switch1 is the seed switch and
switch2 is the principal switch, and SAN Element name is configured. If a switch3 joins the
fabric as a principal switch, then the element name changes to switch3 WWN and the
configured name is lost.
Zone control and enhanced zone control subprofiles

The zone control subprofiles enable discovery of a fabric's zone database and provisioning of
zoning operations.
Registration
Refer to Registration on page 18.
Data model
Figure 10 shows the data model with the classes and properties that are supported to conform to
these subprofiles. Only those properties that are mandatory are considered.

53-1004153-01
Fabric profile 3
FIGURE 10 Zone control and enhanced zone control subprofiles data model
Table 3 outlines the required CIM elements for the zone control subprofile.
TABLE 3 CIM elements for zone control subprofile

ElementName Description Currently
supported Y/N?
CIM_HostedService Associates the ZoneService to the Admin Domain Yes

representing the fabric.
CIM_ZoneService The service that allows for all of the zoning Yes
configuration changes.

53-1004153-01
3 Fabric profile
Extrinsic methods
The Brocade_ZoneService class contains the following extrinsic methods of the zone control
subprofiles:
CreateZoneSet
CreateZone
CreateZoneAlias
CreateZoneMembershipSettingData
AddZone
AddZoneAlias
AddZoneMembershipSettingData
ActivateZoneSet
SessionControl
ActivateZoneSetWithJob
SessionControlWithJob
The following method is Brocade extension:
ClearZoneDB
Zoning operation behavior

The Brocade Network Advisor SMI Agent depends on Brocade Network Advisor to support zoning.
The Brocade Network Advisor SMI Agent supports pure Fabric Operating System (FOS), mixed
fabrics, as well as pure Enterprise Operating System (EOS) fabrics.
The following are the zoning operation behaviors:
All the operations as shown in Figure 10 are supported.
Starting a zoning transaction is done by invoking the SessionControl method. Only one CIM
client is allowed to do zoning on a particular fabric at a time from the same Brocade Network
Advisor SMI Agent. However, with the Brocade Network Advisor SMI Agent, the transaction lock
is only local and it is not open on the switch. The operation returns Success without actually
doing anything on the switch. The same applies to the abort operation.
Even though SMI zoning operations appear atomic in nature, the changes are delivered to the
fabric as a whole. The changes made by a CIM client are not visible to any other client, not even
on Telnet until the transaction is committed successfully.
The operations Activate (including with job), Deactivate (including with job), and ClearZoneDB
are supported only outside the scope of a zoning transaction. If a transaction is open, then the
changes must be done before activating, deactivating, or clearing the database.
A user is identified by Brocade Network Advisor user name only, and so a zoning transaction
opened by user1 on host1 can be used by the same user1 on some other host if it is still open.
The IP address of the host does not configure as part of the user name.
A commit operation is successful once the zoning changes are accepted by the seed switch.
The successful completion of a commit operation does not mean that all the changes have
been propagated to the entire fabric.

53-1004153-01
Fabric profile 3
If a Brocade Network Advisor client first starts zoning on a fabric (opens a zoning dialog box for
that fabric) and then an SMI client starts a transaction on the same fabric, a notification is sent
to the Brocade Network Advisor client that another user is starting zoning operations. This is a
broadcast notification to all the Brocade Network Advisor clients that currently have the zoning
dialog box open to do zoning configuration on the same fabric. This behavior is the same as
between two Brocade Network Advisor clients.
If an SMI client starts a transaction on a fabric and a Brocade Network Advisor client opens a
zoning dialog box, a notification is issued, which need not be considered. The SMI client could
be in the middle of the session changes.
If the SMI client commits first, the Brocade Network Advisor client is notified that the zone
database has been changed. The Brocade Network Advisor client has the option of ignoring or
refreshing the zone database copy. This is a warning message and there is nothing preventing
the Brocade Network Advisor client from ignoring the warning. This behavior is the same as
between two Brocade Network Advisor clients.
If a Brocade Network Advisor client commits the changes first, the SMI client's zone
transaction is aborted and an indication is sent.
If the time for which an open transaction is idle or greater than Brocade_ZoneService.Timeout
(value in seconds), the SMI client's zone transaction is aborted and an indication is sent.
Error code 32770 is mapped to Transaction_Not_Started, which is different from the host
agent where it is No_Transaction.
Error code 32772 is mapped to Transaction_Already_Started, which is different from the host
agent where it is Transaction_Already_On.
Error code 32781 is a new error code mapping to Transaction_Not_Available. This will be
returned to a CIMClient on SessionControl in the event that the zoning transaction on that
fabric is already opened by some other CIMClient.
Error code 32775 mapped to Too Many Members no longer exists.
Indication is not delivered when the client intentionally aborts a transaction.
The fabric assist zoning feature is not supported and therefore the H{<WWN>} notation for a
fabric member is not supported in the SMI Agent.
Job control profile for SessionControlWithJob and

During a commit or activate operation, it is possible that the operation takes time to complete.
Internally, the ZoningServer posts the operation to the switch through Hypertext Transfer Protocol
(HTTP), which then keeps polling the result until it receives a success or failure. The time lag
between the post and poll result depends on the zone database size on a Fabric OS.
To prevent blocking of the CIMClient, two asynchronous methods have been provided in the
Brocade_ZoneService, namely SessionControlWithJob and ActivateZoneSetWithJob. The execution
of these methods returns a Brocade_ConcreteJob instance when the CIM client commit SAN Zone
changes through SANSessionControl extrinsic call. The Brocade_ConcreteJob and
Brocade_SANZoneService are associated by Brocade_SANZoneControlOwningJobElement and
Brocade_SANZoneControlAffectedElement classes.
Even though this subprofile is used, the Brocade Network Advisor SMI Agent will not be 100
percent compliant. For example, the extrinsic method GetError() is not supported. Therefore, this
subprofile is not advertised.

53-1004153-01
3 Fabric profile
Data model
Figure 11 shows the classes and properties of the Job control subprofile.
FIGURE 11 Job control subprofile for zoning
Zoning behavior details

Only SessionControlWithJob on a commit operation returns a Brocade_ConcreteJob instance.
Start and abort operations are not asynchronous.
For SessionControlWithJob and ActivateZoneSetWithJob, the affected ManagedElement is the
Brocade_ZoneService whose SessionState and checksums are affected.
Once a job is started and is in progress, its PercentComplete property always indicate 50
percent till job complete, at which time it will indicate 100 percent.
The DeleteOnCompletion property is always set to false, indicating that all jobs, failed or
completed must be deleted explicitly by the CIMClient using the deleteInstance intrinsic
method. Otherwise, they will continue to exist in the Completed state.
Because there is no automatic deletion of completed jobs by the Brocade Network Advisor SMI
Agent, the TimeBeforeRemoval property is not applicable and is always set to zero.
If a completed job is not deleted and a new job for the same operation on the same target is
started, the new job replaces the old job. The old job is permanently deleted.

53-1004153-01
Fabric profile 3
A second job for the same operation and same target cannot be started if a job is already in
progress and in the running state.
A failed job shows an OperationalStatus of {"6", "17"}, while a successful job shows {"2", "17"}.
Although the GetError() method is mandatory, this operation is not supported.
Upon Brocade Network Advisor server restart, all existing Brocade_ConcreteJob instances are
deleted because they are not persisted in the Brocade Network Advisor database.
Supported indications
Table 4 shows all the supported mandatory indications.
TABLE 4 Supported indications

Indication Description
SELECT * FROM CIM_InstModification WHERE Modification of PercentComplete for a concrete job.

SourceInstance ISA CIM_ConcreteJob AND
SourceInstance.CIM_ConcreteJob::PercentComplet
e <> PreviousInstance.CIM_ConcreteJob::Percent
Complete
SELECT * FROM CIM_InstModification WHERE Modification of OperationalStatus for a
SourceInstance ISA CIM_ConcreteJob AND ANY concrete job to Complete and OK.
SourceInstance.CIM_ConcreteJob::Operation
alStatus[*] = 17 AND ANY
alStatus[*] = 2
SELECT * FROM CIM_InstModification WHERE Modification of OperationalStatus for a
SourceInstance ISA CIM_ConcreteJob AND ANY concrete job to Complete and Error.
alStatus[*] = 17 AND ANY
alStatus[*] = 6
SELECT * FROM CIM_InstModification WHERE Modification of JobState for a concrete job.
SourceInstance ISA CIM_ConcreteJob AND
SourceInstance.CIM_ConcreteJob::JobState <>
PreviousInstance.CIM_ConcreteJob::JobState
SELECT * FROM CIM_InstCreation WHERE Creation of a concrete job.
SourceInstance ISA CIM_ConcreteJob
SAN zoning
Storage Area Network (SAN) zoning is a method of arranging Fibre Channel devices into logical
groups over the physical configuration of the fabric. Brocade Network Advisor SMI Agent provides
SAN zoning configuration support such as CreateSANZone, AddSANZoneMemembers,
RemoveSANZoneMembers, and DeleteSANZone through extrinsic methods.
A Logical Storage Area Network (LSAN) consist of zones in two or more edge fabrics or backbone
fabrics that contain the same devices.The LSANs provide selective device connectivity between
fabrics without forcing you to merge those fabrics.

53-1004153-01
3 Fabric profile
Peer zoning
Beginning with Fabric OS 7.4.0 or later, Peer zone Read-Only support is provided on the Brocade
Network Advisor SMI Agent for SAN zoning and LSAN zoning, with user restrictions. The following
are the Peer zone user restrictions:
Creating a Peer zone.
Adding a new member to the existing Peer zone.
Deleting a Peer zone.
Removing a member from an existing Peer zone.
Deleting a member that is part of the Peer zone.
Adding a zone alias to the Peer zone.
Removing a zone alias from the Peer zone.
Differentiating Peer User and Peer Target zones from normal zones.
LSAN zoning configuration guidelines

The following are the guidelines for configuring LSAN zones:
The LSAN zone name starts with the prefix LSAN_.
The LSAN zone name is case-sensitive.
The members must be identified by their port WWN because the port IDs are not unique across
fabrics.
The names and membership of the same LSAN zone in various fabrics need to be the same
while the order of membership is not necessary.
LSAN zoning in Brocade Network Advisor

The following are the behaviors of Brocade Network Advisor client for LSAN zoning:
The LSAN zoning device sharing operations are done only through backbone fabrics. This
option is disabled for other edge fabrics.
The LSAN zone can be added to any managed edge fabrics and backbones during the zone
activation.
The SMI Agent behavior is same as the client.
Registration
There is no profile registration for this model.
Data model
Figure 12 shows the data model of SAN zoning.

53-1004153-01
Fabric profile 3
FIGURE 12 SAN zoning data model
SAN zoning operation behavior

The following are the operation behaviors of SAN zoning:
SAN zoning is available only for SAN with backbone fabrics.
Brocade_SANZoneService, Brocade_SANZoneCapabilities, and Brocade_SANZoneCollection
are associated to Brocade_SAN.
The Brocade_SANZoneCapabilities supports only the mandatory properties such as
InstanceID, ZoneNameMaxLen, ZoneNameFormat, and SupportedConnectivityMemberTypes.

53-1004153-01
3 Fabric profile
The SANZoneSupported property is added in the Brocade_SANZoneCapabilities to indicate the

SAN zone support.
The Brocade_SANZoneService supports the following extrinsic methods:
- SANSessionControl
- SANSessionControlWithJob
- CreateSANZone
- AddSANZoneMembers
- RemoveSANZoneMembers
- DeleteSANZone
The CIM_ZoneService such as CreateZoneSet, CreateZone, and CreateZoneAlias are not
supported in Brocade_SANZoneService.
Use SANSessionControl method with RequestedSessionState=2 to start a session before
configuring SAN zones through CreateSANZone, AddSANZoneMembers,
RemoveSANZoneMembers, and DeleteSANZone extrinsic methods.
The SAN zones are activated while the session is closed using SANSessionControl method with
RequestedSessionState=3.
You cannot open a session for SAN level zoning and Fabric level zoning simultaneously for a
particular backbone fabric. If you start with a session for SAN level zone, it must be closed
before starting the session for fabric level zone and vice versa.
The CreateSANZone() in Brocade_SANZoneService will get the SAN zone name, list of member
WWNs, and SANZoneType as inputs. A zone with multiple members is created and activated in
the backbone or edge fabrics based on the members.
The AddSANZoneMembers() in Brocade_SANZoneService will get the SAN zone name and
member WWNs as input. Add the zone members to LSAN zone and reactivate the LSAN zone.
The RemoveSANZoneMembers() in Brocade_SANZoneService will get the SAN zone name and
member WWNs as input. Remove those zone members from LSAN zone and reactivate the
LSAN zone.
The DeleteSANZone() in Brocade_SANZoneService will get the zone name as input and deletes
the same zone from the fabrics.
Only WWN zone member type is supported, and Domain:PortIndex zone member type is not
supported in SAN level zoning.
CreateSANZone, AddSANZoneMembers, and RemoveSANZoneMembers calls return an error
code 5 (CIM_ERR_INVALID_PARAMETER), if the zone members are not WWN member type.
The AddSANZoneMembers extrinsic call will not return an error, when duplicate members are
already present in zone.
The RemoveSANZoneMembers extrinsic call will not return errors, when the requested
member is not present in the zone.
The Brocade_SANZoneCollection represents the SAN zones in SAN.
The Brocade_ZoneInSANZoneCollection represents the association between
Brocade_SANZoneCollection (SAN Zone) and Brocade_Zone (active zones in backbone or edge
fabrics).
The SAN zone is added under an existing active zone configurations during SAN zone
activation. If there is no active configuration in the edge fabric or backbone fabric, a zone set
with the name of LSAN_CFG_<date/time> is created and the respective SAN zone is added
under this zone set.

53-1004153-01
Fabric profile 3
NOTE
The name of SAN zone must start with LSAN_. Otherwise, the extrinsic call returns an error code:
5 (CIM_ERR_INVALID_PARAMETER). Invalid SANZone name: <SAN Zone name>.
Alert indication support

The following is the alert indication support for SAN zoning:
Alert indication with message ID BRCD102 is delivered to CIM client, if there is a failure in SAN
zone activation through CIM client. It is not delivered if there is a failure in SAN zone activation
through Brocade Network Advisor client.
Alert indication with message ID FC2 is delivered for successful activation because zoning
activation is performed at fabric level.
Use cases
Figure 13 explains a sample SAN configuration.
Target 1 Target 2 Target 3
Host
Fabric 1 Fabric 2 Fabric 3 Fabric 4
E E
E E E E E
EX EX EX
EX EX EX
EX
FC router 1 FC router 2 FC router 3 FC router 4
Backbone fabric
FIGURE 13 Sample SAN configuration
Create a LSAN_Zone1, add WWN of Host, Target3 and activate the same zone. As the
LSAN_Zone1 has end devices from fabric1 and fabric3, it is activated to both the fabrics. The
following extrinsic calls are used for this operation:
- Activate the SAN zoning session with SANSessionControl (RequestedSessionState=2).
- Create an LSAN zone with CreateSANZone (SANZoneName=LSAN_Zone1,
SANZoneType=LSAN, ZoneMembers={Host WWN, Target 3 WWN}).
- Commit the SAN zoning session with SANSessionControl (RequestedSessionState=3).

53-1004153-01
3 Fabric profile
Create a LSAN_Zone2, add WWN of Host, Target1, Target3, and activate the same zone. As the
LSAN_Zone2 has devices from fabric1, fabric2, and fabric3, the LSAN_Zone2 is activated to all
the three fabrics.
Create LSAN_Zone3 with offline zone members. As the LSAN_Zone3 has only offline members,
the operation is failed with error code 4 (FAILED).
Create LSAN_Zone4, add host, and offline members and activate the same zone. It is activated
in fabric1 as the host belongs to fabric1.
Adding a zone member:
- Add member operation is invoked with the input: WWN Target1 on LSAN_Zone1.
- The member is added to the zone in the fabric1 and fabric3. A copy of the zone is added to
the active zoneset of the fabric2.
- The following are the extrinsic calls used for this operation:
Activate the SAN zoning session with SANSessionControl (RequestedSessionState=2).
Add zone members with AddSANZoneMembers (SANZoneName=LSAN_Zone1,
ZoneMembers={Target 1 WWN}).
Commit the SAN zoning session with SANSessionControl (RequestedSessionState=3).
Removing a zone member:
- Remove member operation is invoked with the input: WWN Target1.
- The member is removed from the zone in fabric1 and fabric3 and the copy of zone is
removed from the fabric2.
- The following extrinsic calls are used for this operation:
Remove zone members with RemoveSANZoneMembers
(SANZoneName=LSAN_Zone1, ZoneMembers={Target 1 WWN}).
Delete a zone with input of zone name (LSAN_Zone1). It will be removed from all the edge
fabrics and backbone fabric.
- The following extrinsic calls are used for this operation:
Delete a zone with DeleteSANZone (SANZoneName=LSAN_Zone1).
Delete a zone with input of zone name (LSAN_Zone7), which is not present in any of the
fabrics. The following error code is returned
- 4 (Failed).<LSAN_Zone7>: SAN Zone name is not found in zone DB.
Subscribe BRCD102 indications and create SAN zone with online members. An indication with
message ID BRCD102 is delivered for activation failures.
Create SAN zone with the prefix XSAN_, add some zones member WWNs, and activate the
zone. As there are invalid zone names, the failure error code 5
(CIM_ERR_INVALID_PARAMETER) is returned.
Add some Domain:PortIndex zone members in the SAN zone. Due to invalid zone members,
the error code 5 (CIM_ERR_INVALID_PARAMETER) is returned.

53-1004153-01
Fabric profile 3
Fabric virtual fabrics subprofile

The fabric virtual fabrics subprofile models the partitioning of a physical fabric into one or more
logical fabrics. The physical fabric consists of one or more switches that can be partitioned. The
switch in the physical fabric that can be partitioned is called the partitioning system. The resulting
virtual fabric will consist of one or more switches formed from the partitioning systems. The
resulting virtual switch in the virtual fabric is called the partitioned system. The virtual fabric
topology, along with its virtual switches, is modeled as per the Fabric profile. The underlying
physical fabric topology, along with its partitioning systems, is modeled by the fabric virtual fabrics
subprofile. By using the Fabric profile with the fabric virtual fabrics subprofile, a logically separated
physical fabric can be discovered.
Fabric virtual fabrics form a single physical fabric. This scenario encompasses the following cases:
All virtual fabrics are discovered with dedicated ISLs between the base switches.
- Brocade_SAN.Name is the principal WWN of the base fabric where all virtual fabrics have
been discovered.
- In the absence of a dedicated ISL between the base switches, no actual logical fabrics
exist except for those that have a dedicated ISL. The virtual fabrics are disjointed.
All virtual fabrics are discovered with no dedicated ISLs between the base switches but
dedicated ISLs between logical switches.
Only some virtual fabrics are discovered exclusive of base fabric.
Registration
Each virtual fabric represented by an instance of Brocade_Fabric, is associated to an instance of
Brocade_RegisteredProfile(Fabric). By SMI definition, all virtual fabrics that are physically
interconnected belong to the same SAN. The Brocade_SAN instance containing the virtual fabrics
associates itself to an instance of Brocade_RegisteredSubprofile (FabricVirtualFabrics) only if the
base switch is discovered. Refer to Registration on page 18.
Data model
Figure 14 models the required classes. The classes relevant in the Fabric profile are also included:
Each physical switch is represented by an instance of Brocade_PhysicalComputerSystem.
Each physical port is represented by an instance of Brocade_PCSNetworkPort.
Each virtual fabric is represented by an instance of Brocade_Fabric.
Each virtual switch is represented by an instance of Brocade_Switch.
Each port within a virtual switch is represented by an instance of Brocade_SwitchFCPort.
All virtual fabrics associate to a single Brocade_SAN instance.
All virtual switches carved out from a single switch associate to a single
Brocade_PhysicalComputerSystem instance.
All Brocade_PhysicalComputerSystem instances associate to a single Brocade_SAN instance.

53-1004153-01
3 Fabric profile
FIGURE 14 Fabric virtual fabrics subprofile data model
Sample discovery configuration

Figure 15 shows a sample Virtual Fabrics configuration. In this configuration, there are five physical
chassis. Chassis 1, Chassis 2, and Chassis 3 are physical chassis that are enabled for Virtual
Fabrics and divided into logical switches. Switch A and Switch B are single-switch chassis and are
not enabled for Virtual Fabrics.

53-1004153-01
Fabric profile 3
FIGURE 15 Sample Virtual Fabrics configuration, connecting the SMI Agent to a single chassis
For this example, assume that the SMI Agent is connected to the Chassis 2 IP address. The SMI
Agent can discover the following:
1 SAN
3 fabrics (Fabric ID 1, Fabric ID 2, and Fabric ID 3)
4 physical chassis
- Chassis 1
- Chassis 2
- Chassis 3
- The chassis for Switch B
9 switches
- 2 logical switches in Chassis 1
- Switch B
Logical switch 18 in Chassis 3 and Switch A, which is connected to this logical switch, are not
discovered.
The physical and logical ports corresponding to the discovered switches

53-1004153-01
3 Fabric profile
7 SANActiveConnections corresponding to the discovered switches

- 2 XISLs
- 1 ISL
- 4 LISLs
Zone databases (size = 1 MB for each fabric) corresponding to the three fabrics.
All of the classes corresponding to the three discovered fabrics as defined in the Fabric and
other profiles.
To discover the fabric formed by Switch A and logical switch 18 in Chassis 3, the provider must be
configured to connect to either Chassis 3 or Switch A, because the Fabric OS will not provide the
information for these switches if the SMI Agent is connected only to Chassis 2.
The devices connected to ports in a logical switch are discovered in the fabrics to which these
switch ports belong. For example, a device connected to a port belonging to a logical switch with
Fabric ID 1 is discovered only if you have access to Fabric ID 1. Device discovery follows the existing
model in the Fabric profile.
Blades subprofile support

The following model supports the blade subprofile in Virtual Fabrics setup as the blade subprofile
in Virtual Fabrics scenario on a director switch is not specified in SMI-S 1.4:
There is one instance of Brocade_Blade for each physical blade in the director switch.
For each Brocade_Blade, there can be multiple Brocade_PortModule instances, depending on
the number of existing logical switches and how the ports are allocated throughout the
chassis.
The association Brocade_PortModuleRealizes cannot be one-to-one in a Virtual Fabrics
scenario, but one-to-many.
Figure 16 shows a basic instance diagram for a director switch containing two logical switches,
where both the logical switches contain a port from the blade in slot 1.
FIGURE 16 Director switch instance diagram

53-1004153-01
Fabric profile 3
Topology view
The Topology View class was introduced in SMI-S 1.3 to increase the performance and reduce the
number of traversals required to discover topology.
The Network Advisor SMI Agent cannot provide a complete topology and its related information
including instances of classes like Brocade_TopologyView, Brocade_SanActiveConnection if one of
the switches involved goes unreachable or unmanageable.
Objectives
The objective is to deliver a class that can be enumerated, gives better performance than
enumerating Brocade_SANActiveConnection(CIM_ActiveConnection), and traverse to each
endpoint to gather data about the link between switch ports or between N_Ports and switchports.
Performance considerations
Performance should be significantly better than the combined performance of enumeration of
Brocade_SANActiveConnection (CIM_ActiveConnection) and traversals to endpoint instances
through CIMClient.associators call.
Registration
Figure 17 shows the registration model of Topology view.
FIGURE 17 Topology view registration model

53-1004153-01
3 Fabric profile
Data model
Figure 18 shows the data model of Topology view.
FIGURE 18 Topology view data model
NOTE
Beginning with Network Advisor 12.4.2, Brocade_TopologyView class is changed from association to
provider, in order to support the property name change of AntecedentFCPort, AntecedentSystem,
DependentFCPort, and DependentSystem from REF to String.

53-1004153-01
Fabric profile 3
FDMI subprofile
The Fabric-Device Management Interface (FDMI) enables the management of devices such as Host
Bus Adapters (HBAs) through the fabric. This subprofile models the discovery of HBA type devices
without having the SMI Agent reside on the host containing the HBA. It shows how an HBA is hosted
on the system (host) along with the nodes contained in it and ports controlled by it. It allows HBAs
to expose product information such as firmware version, vendor, serial number, and so on. This
model supports all HBA configurations such as single-node single-port HBA, single-node dual-port
HBA, and dual-node dual-port HBA.
Prerequisites
Only the HBAs that register a FDMI host name in the Name Server (NS) on the switch or fabric
support the Brocade_Platform model. Currently, the EOS switches do not support FDMI. Therefore,
HBAs connected to EOS switches do not support the Brocade_Platform model, including the
instance classes and association classes.
NOTE
The switch connected to an FDMI-enabled HBA runs on Fabric OS v7.0.0 or later. Also, the seed
switch runs on Fabric OS v7.0.0 or later to support this profile.
Registration
Data model
Figure 19 shows the class diagram of the classes and properties supported in the FDMI subprofile.
The instances for the CIM classes Brocade_SoftwareIdentity, Brocade_HBAProduct,
Brocade_PhysicalHBA, and Brocade_PortController are available as part of the FDMI subprofile
provided the switches are running Fabric OS v7.0.0 or later.
For a single-node single-port HBA, there is a single Brocade_Node instance hosted on a
Brocade_Platform and a single Brocade_PortController representing the logical aspects of the
Brocade_PhysicalHBA controlling a single Brocade_NodeFCPort.
For a single-node dual-port HBA, there is a single Brocade_Node hosted on a Brocade_Platform
and a single Brocade_PortController representing the logical aspects of the Brocade_PhysicalHBA
controlling both Brocade_NodeFCPort instances.
For a dual-node dual-port HBA, there are two Brocade_Node instances hosted on the same
Brocade_Platform and a single Brocade_PortController representing the logical aspects of the
Brocade_PhysicalHBA controlling both Brocade_NodeFCPort instances.

53-1004153-01
3 Fabric profile
FIGURE 19 FDMI data model

53-1004153-01
Fabric profile 3
Trunking
This section defines the model for the trunking feature in Brocade Network Advisor SMI Agent. The
trunking model is supported only for FOS switches.
NOTE
The m-EOS switches open trunking feature is not supported in Brocade Network Advisor SMI Agent
and there will not be any modeling m-EOS open trunking.
Both ISL trunking and F_Port trunking are supported for FOS switches.
Data model
Figure 20 shows the trunking class diagram.
FIGURE 20 Trunking class diagram
Refer to the corresponding class diagrams and profiles for Brocade_Switch,

Brocade_SwitchFCPort, and Brocade_AGFCPort properties.

53-1004153-01
3 Fabric profile
Related API and classes

Table 5 represents the group of switch ports forming a trunk.
TABLE 5 Brocade_Trunk: CIM_RedundancySet
Property name Type Description
InstanceID [Key] string InstanceID opaquely and uniquely identifies an instance of this
class.
The format of this key is as follows.
SOURCESWITCHWWN=<value>;
SOURCESWITCHTYPE=<value>:
DESTINATIONWWN=<value>;
SOURCESWITCHPORTWWN=<value>;
DESTPORTWWN=<value>;
CLASSNAME=Brocade_Trunk;
DESTINATIONTYPE=<value>;
SOURCE_WWN is the master switch WWN of one end.
SOURCE_PORT_WWN is the master port WWN of the trunk
members in a trunk group.
DEST_WWN is the WWN of the other end, which is a switch in case
of an ISL trunk and AG in case of an trunk.
DEST_PORT_WWN is the port WWN of the other end.
SOURCE_TYPE is the type of the source (Switch=0, Device=1)
DEST_TYPE is the type of the other end (Switch=0, Device=1)
TypeOfSet[] uint16 TypeOfSet provides information on the type of redundancy.
ElementName string A user-friendly name for the object.
RedundancyStatus uint16 RedundancyStatus provides information on the state of the
RedundancySet.
LoadBalanceAlgorithm uint16 The current load balance algorithm.
OtherTypeOfSet[] string When the corresponding array entry in TypeOfSet[] is Other, this
entry provides a string describing the type of set.
OtherLoadBalanceAlgorithm String When LoadBalanceAlgorithm is Other, this property describes
the algorithm.
Table 6 explains the properties of Brocade_TrunkInSwitch: CIM_HostedCollection class.

TABLE 6 Brocade_TrunkInSwitch: CIM_HostedCollection
Antecedent Brocade_Switch REF Represents the switch objects that

has the trunk.
Dependent Brocade_Trunk REF Represents the trunk object.
Table 7 explains the properties of Brocade_SwitchFCPortInTrunk: CIM_MemberOfCollection class.

TABLE 7 Brocade_SwitchFCPortInTrunk: CIM_MemberOfCollection
Collection Brocade_Trunk REF Represents the trunk object.

Member Brocade_SwitchFCPort REF Represents the member of the
trunk.

53-1004153-01
Switch profile 3
Table 8 explains the properties of Brocade_AGFCPortInTrunk: CIM_ MemberOfCollection class.

TABLE 8 Brocade_AGFCPortInTrunk: CIM_ MemberOfCollection
Collection Brocade_Trunk REF Represents the trunk object.

Member Brocade_AGFCPort REF Represents the member of the
trunk.
Switch profile
The Storage Networking Industry Association (SNIA) switch profile defines the model and functions
of a fibre channel switch including state, status, and control of the device and its connections.
Registration
The SNIA Profile Registration Profile model is followed to advertise Switch profile and its
subprofiles.
Figure 21 shows the instance diagram with the objects and properties for Switch profile
registration. Only for blades, the actual blade instances that conform to the Blades subprofile will
be associated. For the other subprofiles, such as Software, Access Points, and so on, the
association to the actual instances are not supported.
FIGURE 21 Switch profile registration

53-1004153-01
3 Switch profile
Data model
Figure 22 shows the Switch profile data model.
FIGURE 22 Switch profile data model
NOTE
The value of the Dedicated property of Brocade_Switch is Switch (5) and FC Switch (37).
The set operation for the Brocade_SwitchFCPortSettings.RequestedType is supported from Fabric
OS v6.3 and later.

53-1004153-01
Switch profile 3
NOTE
Switch un-monitoring is not supported from SMI perspective and if the switch is un monitored, then
the SMI Agent would return stale information.
Differentiation between switches and domains

The following properties are used in CIM_CompterSystem to differentiate a simple switch, a switch
created through VF, a switch created through Inter-Fabric Routing Profile (IFR), differentiating Front
Domain from the Translate Domain, and the physical system that is partitioned.
IdentifyingDescriptions = {"DomainID", "SNIA:DetailedType"};
OtherIdentifyingInfo = {"1", "Front Domain"}; where "1" is DomainID and type is Front Domain.
OtherIdentifyingInfo has the value of DomainID and switch detailed type (Front Domain, Translate
Domain, Virtual Switch or None).
In case of VF setup, OtherIdentifyingInfo additionally has the values of the VF_ID, and
IdentifyingDescriptions properties additionally has the value SNIA:VF_ID as the detailed type.
PortDiscriminator in CIM_FCPort differentiates among ports that support IFR (FCR), internal and
external ports, Virtual Fabrics (VF), Fibre Channel over IP (FCIP) and Fibre Channel over Ethernet
(FCoE). This property is applicable for only logical ports. The possible values are given in Table 9.
TABLE 9 PortDiscriminator values
No Port PortDiscriminator value
1 FC ports on the FCIP Ethernet port FCIP

2 Virtual FCoE ports inside the Brocade 8000 internal + FCoE
3 Virtualized node ports in NPIV and Access Gateway NPIV
4 Front and xlate phantom FC ports (except the FF port from IFR virtual
the backbone)
5 Front phantom FC port from the backbone connected to the IFR
edge switch
6 ICL ports Chassis
7 Dynamically created FC ports for logical connections in VF
virtual fabrics
8 All other FC ports (like physical ports) Not Applicable
9 CU ports of Blade Switches Internal
Physical package, access points, software, blades, and

location subprofiles
The Physical Package, Access Points, Software, Blades, and Location subprofiles model the
product information of a switch, the URL to launch the element manager of a switch, the blades
within the chassis, and the details such as primary system owner name, contact, and location for a
Brocade_Chassis.
Table 10 explains the subprofiles and their functions.

53-1004153-01
3 Switch profile
TABLE 10 Switch subprofiles

Subprofiles Description
Physical Package Models information about a storage system's physical

package and optionally about internal sub packages.
Access Points Provides remote access points for management tools.
Software Provides information on the installed controller software.
Blades Models the physical aspect of a blade in a director switch.
Location Models the location of a SAN Element.
Registration
Data model
Figure 23 shows the data model with the classes and properties that are supported to conform to
the switch subprofiles.

53-1004153-01
Switch profile 3
FIGURE 23 Physical Package, Access Points, Software, Blades, and Location subprofiles data model

53-1004153-01
3 CP blades (Brocade extension)
NOTE
he Brocade_Chassis.ElementName property is set correctly in the corresponding instance only if the
seed switch is running on a Fabric OS v6.3.x or higher and if the chassisName in the switches of the
fabric are set after the seed switch firmware has been upgraded.
CP blades (Brocade extension)

This section details the modelling of the Core Processor (CP) blade and its associated properties (IP
address, state, and so on) on the director class Brocade switches.
Data model
Figure 24 shows the instance diagram of the CP blades.

53-1004153-01
CP blades (Brocade extension) 3
FIGURE 24 CP blades instances diagram
Brocade_CPModule instances representing CP blades are not associated to

Brocade_RegisteredSubProfile through Brocade_ElementConformsToSubProfile.
Each Brocade_Blade instance representing the CP blade is logically realized as
Brocade_CPModule:CIMLogicalModule. A different class for this logical module is used instead
of PortModule. The PortModule contains NumPorts property, which is not applicable here. The
association between the Brocade_Blade and the Brocade_CPModule is Brocade_CPRealizes.
The Brocade_CPModule.OperationalStatus property shows the status of the CP whether active,
standby, or failed.

53-1004153-01
3 FC HBA profile
The Brocade_CPModule.ModuleNumber shows the slot number of the CP blade.

The Brocade_CPModule is associated to the Brocade_PhysicalComputerSystem using
Brocade_CPInPCS:CIM_SystemDevice. This association shows the containment relationship on
the logical side.
Each Brocade_CPModule is associated to a Brocade_CPMgmtAccessPoint, which shows the IP
address of the CP.
Each Brocade_CPModule is associated to a Brocade_CPSoftwareIdentity instance, which
shows the firmware running on the CP.
The Brocade_CPModule instances is aggregated to the Brocade_PhysicalComputerSystem,
which is the parent system.
Supported classes and associations

The supported classes and associations are shown in Figure 24.
FC HBA profile
The Fibre Channel Host Bus Adapter (FC HBA) profile is similar to the FDMI subprofile. As with
FDMI, this model also supports all HBA configurations such as single node-single port HBA,
single-node dual-port HBA, and dual-node dual-port HBA.
Prerequisites
Only the HBAs discovered in Brocade Network Advisor are exposed through the FC HBA profile.
Data model
Figure 25 shows the data model of the FC HBA profile.

53-1004153-01
FC HBA profile 3
FIGURE 25 FC HBA profile data model

53-1004153-01
3 Launch In Context profile
NOTE
The HBA is represented by the PortController class and the serial number is the key.
Launch In Context profile

Brocade Network Advisor supports a number of services for network management, such as
Configure Names, Historical Performance Report, Fabric Ports Report, and so on. These services
are published through the Launch In Context (LIC) profile.
LIC names
Table 11 shows the list of LIC names and their descriptions.
TABLE 11 Description of LIC names
LIC name Description
About Displays the product and version information.

CEE_CEE_Configuration Configures CEE parameters for QoS (ETS, PFC),
LAG groups, LLDP, DCBX, ACL, STP, 802.1X
authentication.
CEE_QoS_Configuration Configures QoS parameters on CEE switches.
Discovery Allows discovering the fabrics and hosts.
Discovery_Host_Adapters Discovers groups of Brocade host adapters.
Fabric_TopNTalkers_Report Displays the historical performance report for the
top talkers that are using the most bandwidth on
the selected fabric.
Fabric_Switch_Ports_Report Displays the port details report for all the
discovered ports in the given fabric. The port detail
includes switch information, connected device
information, and so on.
Fabric_Switch_Configuration_Backup Backs up the switch configuration from one or
more switches.
Fabric_Switch_Configuration_Restore Restores the switch configuration for one or more
switches.
Fabric_Switch_Software_Update Downloads firmware to one or more switches.
Fabric_Switch_SupportSave Captures supportSave information from one or
more selected switches and hosts. Also, ability to
schedule later to capture the supportSave
information from one or more switches.
Fabric_Switch_Threshold_Policies Configures threshold policies on E_Ports and
F_Ports or FL_Ports for the Tx and Rx percentage
utilization measures. Sends an appropriate alert to
notify when the threshold is exceeded.
Fabric_Device_Connectivity_Diagnostics Identifies the problems preventing communication
between the two selected device ports from the
same fabric or from two different fabrics.

53-1004153-01
Launch In Context profile 3
TABLE 11 Description of LIC names (Continued)

Fabric_Device_TraceRoute Obtains the detailed path information for any two

selected device ports.
Fabric_Device_Sharing_Diagnostics Verifies whether two or more fabrics are configured
to share the same devices between them.
Fabric_Zoning_Configuration Configures and activates zoning for FC, LSAN, and
so on.
Fabric_Realtime_Graph Monitor a device's performance through real-time
performance graphs that displays a variety of
user-selected performance measures.
Fabric_Historical_Graph Monitors a device's performance through historical
performance graphs for predefined performance
measures.
Fabric_Audit_Log Displays all application events raised by the
application modules and all audit syslog messages
from the switches.
Fabric_Binding_Configuration Configures whether switches can merge with a
selected fabric.
Fabric_Bottlenecks_Configuration Configures the bottleneck detection parameters on
the switches to receive alerts.
Fabric_Create_View Creates a custom view that shows a selected list of
switches and hosts.
Fabric_Email_Event_Configuration Configures the e-mail server for event notification.
Fabric_Encryption_Configuration Configures the encryption switch, targetted LUNs
and hosts, HA clusters, master key, and smart
cards.
Fabric_End_To_End_Monitors Provision of end-to-end monitors of selected target
and initiator pairs. These monitors are persisted in
the database and are enabled on one of the
F_Ports on the connected device. Use these
monitors to view both real-time and historical
performance data.
Fabric_Event_Log Displays all product event type events from all
discovered switches.
Fabric_FCIP_Configuration Configures an FCIP extension connection; you can
create FCIP tunnels and FCIP circuits between two
extension switches.
Fabric_Ficon_Log Displays all the LIR and RLIR type events, for
example, link incident type events.
Fabric_Logical_Switches_Configuration Configures the virtual fabrics. Creates base and
logical switches, assigning ports to a logical switch
and configuring fabric-wide parameters.
Fabric_Port_Fencing Port fencing allows users to set policies that will
block switch ports if certain conditions are met.
Configure port fencing to set threshold limits for
the number of specific port events permitted
during a given time period on the selected object.

53-1004153-01
3 Launch In Context profile
TABLE 11 Description of LIC names (Continued)

Fabric_ProductStatus_Log Displays events which indicate a change in switch

status for all discovered switches.
Fabric_Router_Configuration Configures FC routing to connect devices in
different fabrics without merging the fabrics.
Enables you to connect edge fabrics to a backbone
fabric.
Fabric_Security_Log Displays all security events for the discovered
switches.
Fabric_Syslog Displays syslog messages from switches.
Fabric_Syslog_Forwarding Configures forwarding syslog events of this server
to a destination on a different host.
FCoE_Configuration Creates, edits, and deletes the FCoE login groups
and view the connected devices for FCoE ports.
Names Configures a user-defined name to the fabric,
switch, port, or device.
Server_Info Displays all parameters associated with the server.
User_Management Configures the users and their roles in the
management application.
User_Preferences Configures the options available in the
management application.
VLAN_Configuration Configures VLAN on switches.
Registration and data model

Figure 26 shows the class diagram of the LIC profile.
The Brocade_LICServiceAccessPoint of Configuration Tool and Brocade Network Advisor client are
associated to Brocade_ManagementServer through
Brocade_LICMgmtServerHostedServiceAccessPoint. Other than the Configuration Tool and
Brocade Network Advisor client, the service access points are associated to Brocade_SAN through
Brocade_LICSANHostedServiceAccessPoint.
Each Brocade Network Advisor's service launch point is represented by an instance of
Brocade_LICServiceAccessPoint. The access point is hosted on the Brocade_SAN.
The value of Brocade_LICServiceAccessPoint.AccessInfo property is of the following format:
http://<IP Address: port number>/webstart/<JNLP file name>?module=<Network Advisor module
name>&<SSO parameters if any from Network Advisor client>&${parameterName}
Where ${parameterName} specifies the LIC parameters supported for the specific Network Advisor
dialog box URL.
The Brocade_LICServiceAccessPoint.ParameterName is an array holding the LIC parameters
specified in the URL of AccessInfo property value. The Brocade_LICServiceAccessPoint.Parameter
Description is holding the description of the parameters in the ParameterName array.
In the AcessInfo URL, replace the ${parameterName} with name and value of the ParameterName
array in the format mentioned in the description.

53-1004153-01
Launch In Context profile 3
For example,
http:// <IP Address: port number>/webstart/<JNLP file name>?module=<module name>&<SSO
parameters if any>&${<parameter name like WWN>}
The corresponding entries in Brocade_LICServiceAccessPoint.ParameterName is of the following
format.
{<OrgName>:<SpecName>:<SpecVersion>:WWN}.
You have to replace the ${WWN} part of URL. Here, orgName is Brocade; specName and
specVersion are empty. Therefore, the ParameterName is Brocade:::<WWN>
NOTE
Extrinsic methods of launch service are not supported.
FIGURE 26 Launch In Context registration and data model

53-1004153-01
3 CEE switch support
CEE switch support

The Brocade CEE switch behaves as both an FC switch and an Ethernet switch. The FC capabilities
are captured through the Switch profile. This is now enhanced to model the switch's Ethernet
capabilities.
The CEE switch is partitioned into an Ethernet Admin Domain and a Fibre Channel fabric, where the
Ethernet Admin Domain does not have any contained domain association. Only the Fibre Channel
fabric is associated to the SAN instance. Brocade_SAN.name is the principle WWN of the Fibre
Channel fabric.
Registration
Refer to Registration on page 43. The Brocade_Switch instance representing the CEE switch is
associated to the Brocade_RegisteredProfile instance for switch. There is no profile conformance
for the Ethernet portion of the model due to evolving standards.
Data model
Figure 27 shows the FC and Ethernet topologies along with their connections to the physical
elements. This is a general model that covers device and switch connections to the CEE switch:
Two CIM_ComputerSystem instances (Brocade_Switch and Brocade_EthernetSwitch) is shown
to represent the FC and Ethernet sides of the switch. These instances are associated to the
physical counterpart, which is the Brocade_PhysicalComputerSystem.
Brocade_EthernetSwitch is a component of Brocade_EthernetAdminDomain on the Ethernet
topology side. Similarly, the Brocade_Switch is a component of Brocade_Fabric on the FC
topology side.
The value of the dedicated property of Brocade_EthernetSwitch is Ethernet switch (38).
The Ethernet ports is shown as Brocade_EthernetPort instances associated to the physical
counterpart, which is the Brocade_PCSNetworkPort.
The virtual FCoE port is represented as the Brocade_SwitchFCPort instance with the PortType
as G, or F, or E and is not be associated to a Brocade_PCSNetworkPort. It is an internal port
and there is no physical representation for that port. Even though the virtual FCoE ports are
internal to the switch, they will be modeled as visible switch ports in order to show the devices
physically (directly or indirectly) connected to one of the Ethernet interfaces. However, these
internal ports exist in the ASIC and the Brocade_SwitchFCPort.PortDescriminator property has
the value "8" representing that this is an internal port.
The presence of an active FCoE session is registered as a name server node and port entry.
This is depicted in the host topology as the node and node ports.
The Brocade_EthernetPort of the host is associated to the Brocade_NodeFCPort(s)
(HostedDependency). The Brocade_EthernetPort on the host will not have all properties
populated. All key properties are populated. Among the non-key properties, the
OperationalStatus is 2 (OK) and EnabledState is 2 (Enabled).
All LANEndPoints are part of the EthernetLogicalNetwork in the
Brocade_EthernetAdminDomain.

53-1004153-01
CEE switch support 3
Configuration of the virtual FCoE port is supported. It is a normal switch port instance. Each
Brocade_SwitchFCPort instance representing a virtual FCoE port is associated to
Brocade_SwitchFCPortSettings and Brocade_SwitchFCPortCapabilities instances (not shown
in Figure 27 to avoid clutter; refer to Figure 22 on page 44).
Brocade_SwitchFCPortStats and Brocade_SwitchFCPortRateStats is not shown for virtual FCoE
ports. There is no statistics for the Ethernet interfaces due to the lack of an SMI model.

53-1004153-01
FIGURE 27 FCoE topology diagram

53-1004153-01
Topology supported
The Brocade Network Advisor SMI Agent supports the following use cases.
Device
A device connected to one of the eight FC ports - The Switch profile is used to model the
Brocade CEE switch and its eight FC ports. For the devices connected to these eight FC ports,
refer to Data model on page 19 and Data model on page 46. The FC topology portion in
Figure 27 shows the classes and their associations for this use case.
A device directly connected to one of the Ethernet ports on the CEE switch (one or multiple
FCoE login sessions open) with the device port and device node WWN for each session
registered in the NS database. Figure 27 shows elements in both the FC and Ethernet side. If
the host is registered with a FDMI host name, then the node and node port is hosted on the
platform.
A device indirectly connected to the CEE switch (one or multiple FCoE login sessions open) with
the device port and device node WWN for each session registered in the NS database.
Figure 27 shows elements in both the FC and Ethernet side. The elements in orange cannot be
discovered. This means there is no representation of the Ethernet cloud.
Switch
Two CEE switches connected by their FC ports.
Two CEE switches connected by their Ethernet ports in pure Layer 2 - Both the switches must
be individually managed. The Ethernet portion in Figure 28 depicts the elements and their
connections. There will be one Brocade_EthernetAdminDomain and one
Brocade_EthernetLogicalNetwork per subnet.

53-1004153-01
FIGURE 28 CEE instance diagram

53-1004153-01
Zoning support
Zoning is supported only on the front-end FC ports. The Brocade Network Advisor SMI Agent has
the same limitations as Brocade Network Advisor.
Configuration
The Brocade Network Advisor SMI Agent relies on Brocade Network Advisor support to provide CEE
configuration functionality.
All CEE configuration features are supported on Fabric OS v6.3.0 and later.
Requirements
Enable or disable CEE port
Set interface mode of CEE port to Layer 2 or none
Set Layer 2 mode of CEE port to access, trunk, or converged
Discovery of LAGs
- Create LAG
- Delete LAG
- Add members to LAG
- Remove members from LAG
Discovery of VLANs
- Create VLAN
- Delete VLAN
- Add members to VLAN
- Remove members from VLAN
Discovery of CEE ACL policies
- Create ACL policy
- Delete ACL policy
- Modify ACL policy
- Assign ACLs
Discover CEE maps
- Create CEE map
- Delete CEE map
- Modify CEE map
- Assign CEE Map
Enable global LLDP
Disable global LLDP
Indications

53-1004153-01
Enabling or disabling CEE port

The CEE port is represented by Brocade_EthernetPort. The class Brocade_EthernetPort in
BrocadePartitioning.mof is updated with the following content:
A new extrinsic method RequestStateChange is inherited from the standard CIM class
CIM_EnabledLogicalElement. This method should be used to disable or enable the CEE port.
A new property RequestedState is inherited from the standard CIM class
CIM_EnabledLogicalElement. Knowledge of the last RequestedState is not supported for the
CEE port, thus the property will always have the value 12 (Not Applicable).
Setting interface mode of CEE port

Setting the interface mode of a CEE port is done by setting the Interface Mode property of the
Brocade_LANEndpoint associated to the CEE port. The class Brocade_LANEndPoint in
BrocadeEthernet.mof is updated with a new property InterfaceMode, which is a proprietary
property that indicates whether the CEE port is in Layer 2, Layer 3, or none mode. The property is
writable and can be set using the setInstance intrinsic operation. Layer 3 mode is not supported.
Setting Layer 2 mode of CEE port

Setting the Layer 2 mode of a CEE port is done by setting the OperationalEndpointMode property of
the Brocade_LANEndpoint associated to the CEE port. The class Brocade_LANEndpoint in
BrocadeEthernet.mof is updated with a new property OperationalEndpointMode, which is a
proprietary property that indicates whether the CEE port is in access, trunk or converged Layer 2
mode of operation. The property is writable and can be set using the setInstance intrinsic
operation.
BrocadeEthernet.mof is updated to include support for this new property.
Enabling or disabling LLDP-DCBX on Ethernet switch and CEE port

With Layer 2 networks expanding dramatically, it is difficult for a network administrator to statically
monitor and configure each device in the network. Using Link Layer Discovery Protocol (LLDP), the
network devices such as routers and switches advertise information about themselves to other
network devices and store the information they discover.
Data Center Bridging Exchange (DCBX) is used to exchange CEE-related parameters with neighbors
to achieve more efficient scheduling and a priority-based flow control for link traffic. DCBX is built
on the LLDP infrastructure and uses LLDP to exchange parameters between two link peers. DCBX
is on by default.
Brocade Network Advisor SMI Agent supports enabling or disabling the default LLDP-DCBX at the
switch and port levels. Users can enable or disable the global configuration at the switch level. User
can also enable or disable the specific LLDP configuration currently applied at the port level.
There is no support for defining any new LLDP profiles through Brocade Network Advisor SMI Agent.
Saving the running configuration to the startup configuration on the CEE switch
This feature allows you to save all the CEE configuration changes made after startup so that they
are persisted across reboots. The class Brocade_EthernetSwitch in BrocadeEthernet.mof is
updated with a new extrinsic method ConfigSaveRunningToStartup. This method saves the CEE
changes to startup configuration on the switch. The changes are visible even after a reboot.

53-1004153-01
Limitations
The value of LLDP-DCBX for port and switch is not persisted in Brocade Network Advisor. In order to
retrieve the value of this property, a call needs to be executed. As a result, populating this property
for port and switch during an enumerateInstances operation is costly and will lead to a degradation
in discovery timings. The Brocade Network Advisor SMI Agent will populate this property as
Unknown in both Brocade_EthernetSwitch and Brocade_EthernetPort, if the instance is retrieved
through enumerateInstances. Users can get the correct value of this property on demand through
the getInstance() intrinsic operation only.
The value of Brocade_VLANEndPoint is not persisted in Brocade Network Advisor. Brocade Network
Advisor SMI Agent will populate this property as Unknown.
LAGs
Link aggregation allows you to bundle multiple physical Ethernet links to form a single logical trunk
providing enhanced performance and redundancy. The aggregated trunk is referred to as a Link
Aggregation Group (LAG). The LAG is viewed as a single link by connected devices, the Spanning
Tree Protocol (STP), Virtual Local Area Network (VLANs), and so on. When one physical link in the
LAG fails, the other links stay up and there is no disruption to traffic.
Brocade Network Advisor SMI Agent supports discovery of these LAGs. In addition, support will be
provided to create, delete, and modify existing LAGs.
NOTE
To configure links to form a LAG, the physical links must be in the same speed and all links must go
to the same neighboring device.
Data model
There is no SNIA model for LAGs. Some aspects of the Distributed Management Task Force (DMTF)
model are considered while others are completely proprietary. The following detailed notes
describe the class diagram as shown in Figure 29.
The LAG is a protocol endpoint defined at the scope of the switch and is represented by an
instance of Brocade_LAG associated to the scoping system, which is the
Brocade_EthernetSwitch through Brocade_LAGInEthernetSwitch.
The property Brocade_LAG.InterfaceMode indicates whether or not the LAG is in Layer 2 mode
and is writable.
The property Brocade_LAG.OperationalEndPointMode indicates whether the LAG is in access,
trunk mode and is writable.
Each LAG can contain zero or more members. Each LAG member is represented by an instance
of Brocade_LAGPort. The composition is through Brocade_LAGPortInLAG.
The member is also defined at the scope of the switch associated to the scoping system, which
is the Brocade_EthernetSwitch through Brocade_EthernetSwitchHostedLAGPort.
Each Brocade_LAGPort instance represents a concrete Brocade_LANEndPoint of a
Brocade_EthernetPort that has been added to the BrocadeLAG. This relationship between the
Brocade_LAGPort and the Brocade_LANEndPoint is represented as
Brocade_LAGPortOfLANEndPoint.
There is one Brocade_LAGService instance per Brocade_EthernetSwitch. This hosting is
represented by Brocade_LAGServiceInEthernetSwitch.

53-1004153-01
The capabilities of the service are represented by an instance of

Brocade_LAGServiceCapabilities associated to the service through
Brocade_LAGServiceElementCapabilities. The maximum number of lags that can be created
on the switch and the methods supported by the service will be reported in this capabilities
instance.
Brocade_LAGService provides extrinsic methods to create and delete LAGs, and add and
remove members from an existing LAG.
Brocade_LAG can be created using the Brocade_LAGService.CreateLAG() extrinsic method.
Refer to BrocadeLAG.mof for details on the parameters. The path of the newly created
Brocade_LAG instance is returned in the output parameter Lag. The Brocade_LAG is
associated to the appropriate Brocade_EthernetSwitch instance on which it is defined.
Members may be added to an existing Brocade_LAG instance using the
Brocade_LAGService.AddMembers() extrinsic method. Refer to BrocadeLAG.mof for details on
the parameters.
Members may be removed from an existing Brocade_LAG instance using the
Brocade_LAGService.RemoveMembers() extrinsic method. Refer to BrocadeLAG.mof for details
on the parameters.
An existing Brocade_LAG instance may be deleted using the Brocade_LAGService.DeleteLAG()
extrinsic method. This method will delete the instance and its members.

53-1004153-01
FIGURE 29 CEE LAG class diagram
Registration
There is no conformance to any profile, and thus no registration.

53-1004153-01
VLANs
Virtual Local Area Network (VLANs) provide the capability to overlay the physical network with
multiple virtual networks. VLANs allow you to isolate the network traffic between virtual networks
and reduce the size of administrative and broadcast domains. A VLAN contains end stations that
have a common set of requirements that are independent of physical location. You can group end
stations in a VLAN even if they are not physically located in the same LAN segment. VLANs are
typically associated with IP subnetworks and all the end stations in a particular IP subnet belong to
the same VLAN. VLAN membership is configurable on a per-interface basis.
Data model
There is no SNIA model for VLANs. Some aspects of the Distributed Management Task
Force (DMTF) model have been considered while others are completely proprietary. The following
detailed notes describe the class diagram as shown in Figure 30.
The VLAN is a collection of protocol endpoints defined at the scope of the switch and is
represented by an instance of Brocade_VLAN associated to the scoping system, which is the
Brocade_EthernetSwitch through Brocade_VLANInEthernetSwitch.
The property Brocade_VLAN.ElementName gives the VLAN's user-friendly name.
Each VLAN may contain zero or more members. Each VLAN member is represented by an
instance of Brocade_VLANEndPoint. The composition is through
Brocade_VLANEndPointInVLAN.
The member is also defined at the scope of the switch associated to the scoping system, which
is the Brocade_EthernetSwitch through Brocade_EthernetSwitchHostedVLANEndPoint.
Each Brocade_VLANEndPoint instance represents a concrete Brocade_LAG or
Brocade_LANEndPoint of a Brocade_EthernetPort that has been added to the Brocade_VLAN.
This relationship between the Brocade_VLANEndPoint and the Brocade_LANEndPoint is
represented as Brocade_VLANEndPointOfLANEndPoint. And the relationship between the
Brocade_VLANEndPoint and the Brocade_LAG is represented as
Brocade_VLANEndPointOfLAG.
There is one Brocade_VLANService instance per Brocade_EthernetSwitch. This hosting is
represented by Brocade_VLANServiceInEthernetSwitch.
The capabilities of the service are represented by an instance of
Brocade_VLANServiceCapabilities associated to the service through
Brocade_VLANServiceElementCapabilities. The maximum number of VLANs that can be
created on the switch and the methods supported by the service are reported in this
capabilities instance.
Brocade_VLANService provides extrinsic methods to create and delete VLANs, and add and
remove members from an existing VLAN.
Brocade_VLAN can be created using the Brocade_VLANService.CreateVLAN() extrinsic method.
Refer to mof content for details on the parameters.
The path of the newly created Brocade_VLAN instance is returned in the output parameter
VLAN. The Brocade_VLAN will be associated to the appropriate Brocade_EthernetSwitch
instance on which it is defined.
Members may be added to an existing Brocade_VLAN instance using the
Brocade_VLANService.AddMembers() extrinsic method. Refer to BrocadeLAG.mof for details
on the parameters.

53-1004153-01
Members can be removed from an existing Brocade_VLAN instance using the

Brocade_VLANService.RemoveMembers() extrinsic method. Refer to BrocadeLAG.mof for
details on the parameters.
An existing Brocade_VLAN instance may be deleted using the
Brocade_VLANService.DeleteVLAN() extrinsic method. This method will delete the instance
and its members.

53-1004153-01
FIGURE 30 CEE VLAN class diagram

53-1004153-01
Registration
Limitations
The following are the limitations of VLAN profile:
The properties are provided through the capabilities on the endpoint.
There is no support for Generic VLAN Registration Protocol (GVRP) and so the
Brocade_VLANEndPointCapabilities.Dot1QTagging is false. Therefore,
Brocade_VLANEndPoint.GVRPStatus is not applicable.
Brocade_VLANEndPointCapabilities.Dot1QAcceptableVLANFramesTypes is same as
Brocade_VLANEndPoint.FrameType.
Valid values for Brocade_VLANEndPointCapabilities.Dot1QAcceptableVLANFramesTypes is
populated on Enumerate Instance Names and Enumerate Instances only. The value is
Unknown on GetInstance due to performance issue.
Ingress and egress filtering is always enabled.
CEE ACLs
Access Control List (ACL) is used to filter Ethernet traffic of the Ethernet switch. It permits or denies
incoming packets from passing through interfaces that has the ACL policies applied to them. The
primary function is to control the movement of packets through or to the system and also to track
the packet movement.
ACLs are not effective until they are applied to an interface. One can apply ACLs on VLANs and on
the Ethernet switch 10-Gigabit Ethernet Layer 2 interfaces (Physical interfaces, Logical interfaces,
and LAGs). Each ACL is a unique collection of permit and deny statements (rules) that apply to the
packets. When a packet is received on an interface, the switch compares the fields in the packet
against any ACLs applied to the interface to verify that the packet has the required permissions to
be forwarded. The switch compares the packet sequentially against each rule in the ACL and either
forwards the packet or drops the packet.
The Brocade Network Advisor SMI Agent supports the discovery of these ACLs, both standard and
extended. In addition, support is provided to create, delete, and modify existing ACLs.
Resequencing of an ACL is not supported. Displaying and clearing of the ACL statistics counter is
not supported. However, users can enable or disable the tracking of traffic by specifying the count
parameter within the rule of an ACL policy.
There are two types of Layer 2 Media Access Control (MAC) address ACLs, standard and extended.
Layer 2 standard ACLs-permit and deny traffic according to the source MAC address in the
incoming frame. Use standard MAC ACLs if you only need to filter traffic based on source MAC
addresses.
Layer 2 extended ACLs-permit and deny traffic according to the source and destination MAC
addresses in the incoming frame, as well as other information in the MAC header, such as
EtherType.
The ACL name must be unique across both the standard and extended types.
The ACL name can be a maximum of 64 characters.
Special characters can be used in an ACL name.

53-1004153-01
Even though ACLs can be Layer 2-specific (MAC) or Layer 3-specific (IP), they can only be
applied on the same type of interface. Because an interface can only be set to Layer 2 mode,
Layer 2 ACLs and only ACLs with MAC source and destination addresses are supported.
Data model
There is no SNIA model for CEE ACLs. The DMTF DSP1039 version 1.0.0 for the Role-Based
Authorization Profile to model these ACLs will be followed. All mandatory classes and properties as
stated in this profile will be supported. The following detailed notes describe the class diagram as
shown in Figure 31.
The CEE ACL policy is defined at the scope of the switch. This policy represented by an instance
of Brocade_CEEACLPolicy is associated to the scoping system, which is the
Brocade_EthernetSwitch through Brocade_CEEACLPolicyInEthernetSwitch.
Each CEE ACL policy may contain zero or more rules. All the rules within a policy are
represented by a single instance of Brocade_CEEACLRules. The composition is through
Brocade_CEEACLRulesInPolicy. There is one instance of Brocade_CEEACLRules for every
Brocade_CEEACLPolicy on the Brocade_EthernetSwitch.
The Brocade_CEEACLRules.ActivityQualifiers array contains an array of strings, each string
represents one rule within the policy. Each string contains the details of the sequence number,
source, destination, count, Ether Type and privilege of the rule in a specific format.
The Brocade_CEEACLRules.QualifierFormats array contains an array of strings, each string
represents the format for the rule in the Brocade_CEEACLRules.ActivityQualifiers array at the
same index.
All the possible values for the Brocade_CEEACLRules.QualifierFormats array are published in
the Brocade_CEEACLServiceCapabilities.QualifierFormatsSupported as an array of strings. The
value in the Brocade_CEEACLRules.QualifierFormats property is a subset of these formats.
A policy may be empty. In such a case, the Brocade_CEEACLPolicy is associated to a
Brocade_CEEACLRules instance in which the Brocade_CEEACLRules.ActivityQualifiers and
Brocade_CEEACLRules.QualifierFormats properties are empty.
If a CEE ACL policy has been applied to a port, LAG or VLAN, this information can be discovered
by traversing the Brocade_CEEACLPolicyOnEthernetPort, Brocade_CEEACLPolicyOnLAG, or
Brocade_CEEACLPolicyOnVLAN respectively to the appropriate ManagedElement.
For every Brocade_EthernetSwitch instance, there is an instance of Brocade_CEEACLService.
This service provides the ability to create, delete, modify, and assign CEE ACL policies.
The capabilities of the service are published by a single instance of
Brocade_CEEACLServiceCapabilities associated to the service through
Brocade_CEEACLServiceElementCapabilities.
Brocade_CEEACLPolicy can be created using the Brocade_CEEACLService.CreateRole()
extrinsic method. Only the input parameters RoleTemplate and Privileges are supported. The
successful execution of this method results in the creation of an instance of
Brocade_CEEACLPolicy being associated to an instance of Brocade_CEEACLRules. The path of
the newly created Brocade_CEEACLPolicy instance is returned in the output parameter Role.
The Brocade_CEEACLPolicy is associated to the appropriate Brocade_EthernetSwitch instance
on which it is defined. The Brocade_CEEACLPolicy instance is not associated to a port, LAG or
VLAN. This is done as a separate operation.

53-1004153-01
An existing Brocade_CEEACLPolicy instance may be modified using the

Brocade_CEEACLService.ModifyRole() extrinsic method. The input parameters Role and
Privileges are required. Refer to MOF content for details on the parameters. The call replaces
the existing Brocade_CEEACLRules instance for the Brocade_CEEACLPolicy specified in the
input parameter Role with the instance of Brocade_CEEACLRules specified in the input
parameter Privileges. Assigning to targets is not supported during modification. This can be
done separately through the AssignRoles operation.
An existing Brocade_CEEACLPolicy instance may be deleted using the
Brocade_CEEACLService.DeleteRole() extrinsic method. This method deletes the instance and
its associated rules.
A Brocade_CEEACLPolicy may be applied to an Ethernet port, LAG, or VLAN using the
Brocade_CEEACLService.AssignRoles() extrinsic method. Only one policy can be applied at a
time on a Managed Element.
FIGURE 31 CEE ACL class diagram

53-1004153-01
Registration
Because the DMTF DSP 1039 version 1.0.0 for Role-Based Authorization Profile to model these
ACLs is being followed, conformance will be advertised to that profile. Figure 32 shows the profile
registration diagram.
FIGURE 32 CEE ACL profile registration
CEE maps
Data model
There is no SNIA model for CEE maps. The following notes present details on the class diagram in
Figure 33.
The CEE map is defined at the scope of the switch. This map is represented by an instance of
Brocade_CEEMap associated to the scoping system, which is the Brocade_EthernetSwitch
through Brocade_CEEMapInEthernetSwitch.
Each CEE map can contain zero or more priority groups. All the priority groups within a map are
represented by a single instance of Brocade_PriorityGroups. The composition is through
Brocade_ PriorityGroupsInCEEMap. There will be one instance of Brocade_PriorityGroups for
every Brocade_CEEmap on the Brocade_EthernetSwitch.
The Brocade_PriorityGroups.ActivityQualifiers array will contain an array of strings, each string
representing one priority group within the map with the exception of the last entry. The last
entry will contain the priorities for the mapping of the priority groups to the incoming
Converged OS (COS). Each string representing a priority group will contain the details of the
bandwidth and Priority Flow Control (PFC) in a specific format. The last string representing the
priority table will contain the priority group ID for incoming CoS in a specific format.
The Brocade_PriorityGroups.QualifierFormats array will contain an array of strings, each string
representing the format for the priority group or the priority table in the
Brocade_PriorityGroups.ActivityQualifiers array at the same index.
All the possible values for the Brocade_PriorityGroups.QualifierFormats array are published in
the Brocade_CEEMapServiceCapabilities.QualifierFormatsSupported as an array of strings.
The value in the Brocade_PriorityGroups.QualifierFormats property is a subset of these
formats.
A CEE map can be empty. In such a case, the Brocade_CEEMap will be associated to a
Brocade_PriorityGroups instance in which the Brocade_PriorityGroups.ActivityQualifiers and
the Brocade_PriorityGroups.QualifierFormats properties will be empty.

53-1004153-01
If a CEE map has been applied to a port, this information can be discovered by traversing the
Brocade_CEEMapOnEthernetPort to the Brocade_EthernetPort instance.
For every Brocade_EthernetSwitch instance, there will be an instance of
Brocade_CEEMapService. This service will provide the ability to create, delete, modify, and
assign CEE maps.
The capabilities of the service are published by a single instance of
Brocade_CEEMapServiceCapabilities associated to the service through
Brocade_CEEMapServiceElementCapabilities.
Brocade_CEEMap can be created using the Brocade_CEEMapService.CreateRole() extrinsic
method. Only the input parameters RoleTemplate and Privileges are supported. The successful
execution of this method results in the creation of an instance of Brocade_CEEMap being
associated to an instance of Brocade_PriorityGroups. The path of the newly created
Brocade_CEEMap instance is returned in the output parameter Role. The Brocade_CEEMap
will be owned by the Brocade_EthernetSwitch instance on which it is defined. The
Brocade_CEEMap instance will not be associated to any port. That assignment must be done
as a separate operation. Refer to BrocadeCEEMaps.mof description for more details.
An existing Brocade_CEEMap instance may be modified using the
Brocade_CEEMapService.ModifyRole() extrinsic method. The input parameters Role and
Privileges are required. The call will replace the existing Brocade_PriorityGroups instance for
the Brocade_CEEMap specified in the input parameter Role with the instance of
Brocade_PriorityGroups specified in the input parameter Privileges. Assigning to targets is not
supported during modification. This can be done separately through the AssignRoles
operation.
An existing Brocade_CEEMap instance can be deleted using the
Brocade_CEEMapService.DeleteRole() extrinsic method. This method deletes the instance and
its associated priority groups.
A Brocade_CEEMap may be applied to an Ethernet port using the
Brocade_CEEMapService.AssignRoles() extrinsic method. Only one map can be applied at a
time on the port.

53-1004153-01
FIGURE 33 CEE map class diagram
Registration
Brocade 8470 FCoE embedded switch support

Brocade 8470 is the Brocade CEE high speed switching module. CEE discovery and configuration
support is similar to that of the Brocade 8000 and FCOE10-24 as detailed in the previous sections.
There are some distinct differences in Brocade 8470. The following sections provide more details.
Differences from Brocade 8000 and FCoE 10-24

The CEE ports are categorized into two types, internal ports and external ports.
There are eight external CEE ports with the default name starting with "ExT <slot>/<port>".
There are 14 or 12 internal CEE ports (BCH or BCH T chassis) with the default name starting
with "InT <slot>/<port>".

53-1004153-01
Brocade 8470 supports Layer 3 mode of operation. The external ports and LAGs can be in
None, Layer 2 and Layer 3 Interface mode. However, the internal ports can only be in the Layer
2 Interface mode.
SetInstance of the interface mode on external ports to None and Layer 2 is supported.
NOTE
Support for setting of Layer 3 mode is not needed because adding of an IP address to an
ethernet port automatically puts the port in Layer 3 mode.
SetInstance of an interface mode on LAGs to None and Layer 2 is supported.

SetInstance of an OperationalEndPoint mode on external ports to access, trunk, and
converged mode is supported.
SetInstance of an interface mode on internal ports is not supported. They are default to Layer
2 mode.
Support for setting of Layer 3 mode is not required because adding of an IP address to a lag
automatically puts the lag in Layer 3 mode.
Setting on the OperationalEndPoint mode on internal ports is not supported. They are
defaulted to a converged mode.
The external ports are associated to PCSNetworkPort similar to those on the Brocade 8000
and FCOE10-24. However, the internal ports are not associated to PCSNetworkPort.
The LANendpoints of external ports can be part of a LAG similar to those on the Brocade 8000
and FCOE10-24. However, the lanendpoints of internal ports cannot be part of a LAG.
A management VLAN by default with VLANID = 4095 exists Brocade 8470.
Creation and deletion of VLAN is not supported for Brocade 8470.
The internal ports are part of this 4095 VLAN by default and this cannot be changed.
The external ports cannot be added to this 4095 VLAN.
The LANendpoints of external ports can be part of any other VLAN similar to those on the
Brocade 8000 and FCOE10-24. However, the LANendpoints of internal ports cannot be a part
of any other VLAN.
The external and internal ports can be assigned a CEEACLPolicy.
The external and internal ports can be assigned a CEEMap.
Support for Layer 3 features

The Brocade 8470 platform supports some of the basic Internet Protocol version 4 (IPv4) features.
Brocade Network Advisor SMI Agent supports a subset of these as stated in this section.
Brocade Network Advisor SMI Agent supports the configuration of IP addresses on Physical
interfaces such as CEE port and LAG. One can assign a single primary IP address and up to 255
secondary IP addresses on a single interface. When an IP address is assigned to an interface, it
becomes a Layer 3 interface.
Data model
The following data model is supported. Figure 34 shows the classes and associations for discovery
and configuration of IPv4 addresses on CEE ports and LAGs.

53-1004153-01
FIGURE 34 CEE Brocade 8470 support data model

53-1004153-01
Fabric switch partitioning subprofile 3
Brocade 8428 FCoE embedded switch support

Brocade 8428 is the Brocade CEE high speed switching module. CEE discovery and configuration
support is similar to that of the Brocade 8000 and FCOE10-24 as detailed in the previous sections.
There are some distinct differences in Brocade 8428. For more information about the differences,
refer to Differences from Brocade 8000 and FCoE 10-24 on page 74, Support for Layer 3
features on page 75, and Data model on page 75.
Fabric switch partitioning subprofile

This subprofile models all Brocade switches. Every Brocade switch is partitioned into a logical
Brocade_Switch and a physical Brocade_PhysicalComputerSystem instance associated through
HostedDependency. In addition, every port is partitioned into a logical Brocade_SwitchFCPort and
physical Brocade_PCSNetworkPort instance associated through CIM_HostedDependency.
Data model
Figure 35 shows the fabric switch partitioning subprofile data model.
FIGURE 35 Fabric switch partitioning subprofile data model
Registration
Only instances of Brocade_PhysicalComputerSystem that are Virtual Fabrics-enabled are
associated to the Brocade_RegisteredSubProfile instance for fabric switch partitioning. Figure 36
shows the registration for fabric switch partitioning subprofile.

53-1004153-01
3 FC routing
FIGURE 36 Fabric switch partitioning profile registration
FC routing
A Fibre Channel Router (FCR) is a specific case of switch partitioning. The FC-FC routing service
provides connectivity to devices in different fabrics without merging the fabrics. A switch running
the FC-FC routing service is called a Fibre Channel Router.
Data model
Figure 37 shows the FCR data model.

53-1004153-01
FC routing 3
FIGURE 37 Fibre Channel Router data model
FCR devices of Brocade act as normal switches and routers. Therefore, the switch which is
router capable and functioning in multi-domain mode, has both physical and logical
representation in SMIS. The FCR is represented by two instances of CIM_ComputerSystem, a
Brocade_Switch and a Brocade_PhysicalComputerSystem associated by
CIM_HostedDependency(Brocade_SwitchInPCS).
The Brocade_PhysicalComputerSystem, in addition to being associated to the BackBone
Brocade_Switch instance, will also be associated to Brocade_Switch instances of front and
xlate phantoms.
Both the xlate phantom and front phantom switches are represented as Brocade_Switch
instances. The front phantom domain and xlate phantom domain switches are associated by
the Brocade_SANActiveConnection. These phantom switches can be differentiated by
Brocade_Switch.OtherIdentifyingInfo property value (which would have the values as Translate
Domain, Front Domain, and None for translate phantom domain, front phantom domain, and
ordinary switches respectively).
The InteropMode property of front phantom domain and xlate phantom domain switches are
not populated.

53-1004153-01
3 FC routing
Brocade_PCSServiceCapabilities has a Boolean property called FCRCapable. If the property is

true, then the switch is FCR capable and is enabled. If false, the switch is capable and not
enabled. If null, the switch is not FCRcapable. In the case of VF setup, this property is null if the
base switch is not discovered.
Each phantom switch is associated with Brocade_FCSwitchSettings and
Brocade_FCSwitchCapabilities. The FCSwitchSettings has the property called
PreferredDomainID, which is a settable property. A user can set the PreferredDomainID for the
phantom switches in the FCSwitchSettings instance. If the DomainIDConfigurable is true then
it would indicate that the DomainID settings can be modified. Modifying this property is a
fabric-disruptive operation due to intrinsically disabling of all EX_Ports connected to the
respective edge fabric, modifying the domain ID of the phantom switch, and then enabling all
the EX_Ports as required by the firmware. This applies to both the front and translate phantom
domains. In addition, by modifying the translate domain ID, and the need to disable or enable
the EX_Ports, the WWN of the translate domain is changed.
A port on FCR configured as an EX_Port is filtered out during port discovery on the backbone
for edge to edge device sharing.
An association called Brocade_SwitchFCPortOfPCSNetworkPort associates the front phantom
SwitchFCPort instance representing the FCR EX_Port in the edge fabric with the
PCSNetworkPort instance representing the FCR EX_Port on the FCR logical switch.
There is one instance of NodeFCPort for every entry in the name server. The SystemName
property reflects the Fabric WWN of the fabric where the port exists. In case of FCR setup,
where the devices are imported or exported, there may be multiple instances of NodeFCPort
where DeviceID is the same, but SystemName differentiates each instance based on fabric
membership.
The physical ports are represented as Brocade_PCSNetworkPort instances. In the backbone
view for every physical port, there is a CIM_NetworkPortCapabilities, identifying the
configuration capabilities of the port; and a CIM_NetworkPortSettings, identifying the
configuration details of that port. This class can be used to enable configuration of an FCR port
as an EX_Port by writing to the NetworkIDs property of the port's settings. Modifying this
property is a fabric-disruptive operation due to intrinsically disabling the EX_Port, modifying the
value, and then enabling the EX_Port as required by the firmware.
The property NetworkIDsConfigurable will indicate whether or not a port in the fabric is capable
of being configured.
From an SMI perspective, all fabrics which are physically connected are considered to be
contained in the same SAN.
If FCR setup where the backbone fabric and edge fabrics have been discovered -
Brocade_SAN.Name is the principal WWN of the backbone fabric.
If FCR setup where only one or more edge fabrics have been discovered - In the absence of the
backbone, there is no knowledge that the edge fabrics belong to one FCR backbone fabric, so
each edge fabric will be associated to its own SAN instance Brocade_SAN.Name which is the
principal WWN of that edge fabric.
Registration
Brocade_RegisteredProfile is mapped to Brocade_Switch using
Brocade_ElementConformsToProfile association class if edge switch is discovered along with its
backbone.
Figure 38 shows the SNIA Profile Registration model to advertise Inter-Fabric Routing profile.

53-1004153-01
FC routing 3
FIGURE 38 Fibre Channel Router registration model
Edge-to-edge device sharing (no FCIP configured

in backbone)
Figure 39 shows the instance diagram which depicts fabric discovery of the backbone and edge
fabric with edge to edge device sharing.
A port on FCR configured as an EX_Port is filtered out during port discovery on the backbone for
edge-to-edge device sharing.
If only the backbone fabric is being managed through Brocade Network Advisor, then only
instances in the BackBone Fabric view are discovered. For edge fabric managed through Brocade
Network Advisor, refer to the Limitations section. If both the backbone and the edge fabrics are
managed through Brocade Network Advisor, then all instances and associations are discoverable.

53-1004153-01
3 FC routing
FIGURE 39 Data model for edge-to-edge device sharing

53-1004153-01
FC routing 3
Backbone-to-edge device sharing (no FCIP configured

in backbone)
Figure 40 shows the data model for backbone-to-edge device sharing. If only the backbone
fabric is being managed through Brocade Network Advisor, then only instances in the
BackBone fabric view are discovered. If only the edge fabric is being managed through
Brocade Network Advisor, refer to the Limitations section. If both the backbone and the edge
fabrics are being managed through Brocade Network Advisor, then all instances and
associations are discoverable.
In the case of backbone edge device sharing, there is only one front phantom domain and two
xlate phantom domain switches. On the Edge fabric side, there is one front domain and one
xlate domain switch instance created. On the BackBone fabric side, there is only an xlate
domain switch created and no front phantom domain. Because the xlate phantom domain
switch is always behind the front phantom domain switch, the backbone switch itself
represents the front phantom domain. In addition to the logical port instance on the front
phantom in the edge fabric, FOS creates another instance of the logical port on the backbone
logical switch. This is the logical port instance that is connected to another logical port
instance on the xlate phantom through a SANActiveConnection.

53-1004153-01
3 FC routing
FIGURE 40 Data model for backbone-to-edge device sharing

53-1004153-01
FC routing 3
Backbone-to-edge device sharing

(using VEX_Port over FCIP)
An FCR setup with backbone and edge fabrics encompasses the following cases:
The backbone fabric and all edge fabrics are discovered.
Only the backbone fabric is discovered.
Only some or all of the edge fabrics are discovered.
Consider two Routers R1 and R2 connected to each other by FCIP connection as VE-VEX. Here R1
acts as an Edge Fabric and R2 as a Backbone Fabric. Figure 41 shows the data model for
backbone-to-edge device sharing for VEX over FCIP.

53-1004153-01
3 FC routing
FIGURE 41 Backbone-to-edge device sharing for VEX over FCIP

53-1004153-01
FC routing 3
Brocade Network Advisor SMI Agent classes added for this profile
Table 12 explains the classes and MOF files.
TABLE 12 Classes and MOF file
Class MOF file
Brocade_PCSNetworkPortSettings BrocadePartitioning.mof
Brocade_PCSNetworkPortCapabilities BrocadePartitioning.mof
Brocade_PCSServiceCapabilities BrocadePartitioning.mof
Brocade_EthernetPort BrocadePartitioning.mof
Table 13 explains the associated classes and MOF files.

TABLE 13 Association classes and MOF file
Association class MOF file
Brocade_PortSettingsForPCSNetworkPort BrocadePartitioning.mof
Brocade_PortCapabilitiesForPCSNetworkPort BrocadePartitioning.mof
Brocade_EthernetPortOfPCSNetworkPort BrocadeEthernet.mof
Brocade_PCSCapabilities BrocadePartitioning.mof
Brocade_EthernetPortInExtender BrocadeExtender.mof
Brocade_SwitchFCPortOfEthernetPort BrocadePartitioning.mof
Limitations
Brocade Network Advisor SMI Agent does not support MEOS switches.
In order to achieve a full topology discovery of edge fabrics, the backbone fabric must be
managed through the Brocade Network Advisor Server. If the backbone fabric is not managed
through the Brocade Network Advisor server, discovery is limited to the topology shown in
Figure 42.
You can modify the PreferredDomainID value for phantom switches only when the associated
backbone fabric is managed through Brocade Network Advisor.

53-1004153-01
3 FC routing
FIGURE 42 Topology for discovering only edge fabrics
Phantom switch instances are associated to the Brocade_Fabric instance.

Imported device instances of Brocade_NodeFCPort are associated to the Brocade_Fabric
instance.
No instances of Brocade_SwitchFCPort exist for phantom ports.
No instances of Brocade_SANActiveConnection exist to show the topology of ISLs between
the real edge port and the phantom switches or for the imported devices.
The PreferredDomainID value for phantom switches can be modified only if the associated
backbone fabric is managed through Brocade Network Advisor.

53-1004153-01
Brocade Access Gateway and NPIV 3
Brocade Access Gateway and NPIV

Access Gateway (AG) allows you to configure the enterprise fabric to handle additional N_Ports
instead of domains by configuring F_Ports to connect to the fabric as N_Ports. This increases the
number of device ports that can be connected to a single fabric. Multiple AGs can connect to the
DCX enterprise-class platforms, directors, and switches.
The switches in AG mode are logically transparent to the host and the fabric. The number of hosts
that have access to the fabric can be increased without increasing the number of switches. This
simplifies the configuration and management in a large fabric by reducing the number of domain
IDs and ports.
NOTE
The SMI Agent does not support the discovery of an Access Gateway-enabled switch as a seed
switch, using Extrinsic method, except for the Encryption Switch.
Node Port Initialized Virtualization (NPIV) allows a single Fibre Channel port to appear as multiple
distinct ports. It provides a separate port identification and security zoning within the fabric for
each operating system image. Each operating system image has its own unique physical port.
For additional information about Access Gateway, refer to the Access Gateway Administrators
Guide.
For additional information about NPIV, refer to the Fabric OS Administrators Guide.
Registration
Figure 43 shows the SNIA Profile Registration Profile model to advertise the NPIV profile.
FIGURE 43 NPIV profile registration model
When an Access Gateway switch exists with devices attached in the discovered fabric, the
Brocade_RegisteredProfile (N_Port Virtualizer) is mapped to Brocade_AccessGateWay using
Brocade_ElementConformsToProfile association class.

53-1004153-01
3 Brocade Access Gateway and NPIV
Data model
Figure 44 defines the data model and functions of the AG and NPIV.
FIGURE 44 AG class diagram

53-1004153-01
NOTE
The port statistics and the port rate statistic information modeled for the AGFCPorts will be
supported from FOS 5.3 onwards.
FIGURE 45 NPIV instance diagram
HBA with virtualized ports without AG

Figure 45 shows the discovery of a host with a virtualized port, without AG.
Brocade_SwitchFCPort has the property NPIVEnabled. The port supports connecting NPIV
devices if this property value is true.

53-1004153-01
The Brocade_SwitchFCPortCapabilities class has two properties, NPIVSupported and

MaxNPIVLogins.
- The NPIVSupported property indicates the NPIV support for the FC port.
- The MaxNPIVLogins property indicates the maximum number of NPIV logins supported on
the FC port. The value of MaxNPIVLogins is always set to 32.
The end device is represented as the instance of Brocade_Platform. The value of the property
Dedicated is Not Dedicated representing the HBA. The LogicalPortGroup instance is
represented as Brocade_Node and it is associated with Brocade_Platform by
Brocade_NodeInPlatform.
All the ports in end devices are represented as Brocade_NodeFCPort and it associates with
Brocade_Node by Brocade_PortInNode.
The virtualized ports associate with real ports of the end device using the
Brocade_NodeFCPortDependency association. The Brocade_NodeFCport is also associated
with the Brocade_Platform by Brocade_NodePortInPlatform.
The platform instance for the HBA is shown if the HBA is FDMI-enabled.
SANProtocolEndPoint of the switch is associated with the SANProtocolEndPoint of the end
device as Brocade_SANActiveConnection. There is a direct association between the switch and
the virtualized port of the end devices through Brocade_SANActiveConnection. Therefore, the
number of F_Port to N_Port connections is equal to the sum of virtualized ports and real port
of the end device.
Access Gateway Physical Package

The Physical Package support has been provided for Access Gateways. Figure 46 provides the AG
Physical Package model diagram.

53-1004153-01
FIGURE 46 AG Physical Package
Access Gateway
When a AG-capable switch is changed to AG, it will not act as a switch and it cannot be directly
discovered through Brocade Network Advisor. The port on the switch that is connected to AG is the
F_Port and the port on AG that has a connection from switch is the N_Port. AG is considered as a
node from the switchs perspective.
As shown in Figure 47, there are two connections from Switch1 to AG. There are two F_Ports on
switch F1 and F2 connected to ports N1 and N2 of AG. The AG is connected to three HBAs, so the
F_Ports F1, F2, and F3 on AG are connected to the ports n1, n2, and n3 of HBA1, HBA2, and HBA3
correspondingly. There is an internal mapping on AG as N1 is mapped with F1 and F2, and N2 is
mapped with F3.

53-1004153-01
AG connected to a single fabric
HBA1
n1
AG Switch 1
F1 N1 F1
n2 F2
N2 F2
F3
HBA2
n3
HBA3
FIGURE 47 AG mapping
HBA with virtualized ports connected to AG

Figure 48 represents the Brocade Network Advisor SMI Agent model for discovery of a host
attached to AG.
The instance of Brocade_Platform with Dedicated property values as Not dedicated represents
the HBA attached to the AG. This platform instance is shown if the HBA is FDMI-enabled and
the host name is known to Network Advisor. For more details, refer to the FC HBA profile on
page 50.
If the value of Dedicated property is Gateway of Brocade_AccessGateway, then it represents
the AG.
The association between the SANProtocolEndPoint of switch and AGSANProtocolEndPoint of
AG is Brocade_AGSANActiveConnection. The association between AGSANProtocolEndPoint of
AG and SANProtocolEndPoint of the end device (host) is Brocade_AGSANActiveConnection. The
two associations create a direct association between the SANProtocolEndPoint of the switch
and the SANProtocolEndPoint of the end device (host).
The SANProtocolEndPoint of the switch is associated with the F_Ports of AG, by
Brocade_AGSANProtocolEndPointLogicalIdentity. The F_Port of AG is internally mapped to
N_Ports of AG, which is connected to the switch.

53-1004153-01
FIGURE 48 Host with AG

53-1004153-01
AG connected to multiple fabrics

Figure 49 explains an AG connected to multiple fabrics.
As shown in Figure 49, the Fabric 1 and Fabric 2 share the AG. The N1 port of AG is connected to
Fabric 1 and the N4 port of AG is connected to Fabric 2. The internal mapping on AG is done such
that N1 is mapped with F1 and F2, and N4 is mapped with F3.
Though AG is shared with more than one fabric, it allows only one instance of AG to be associated
with both the fabrics. If Brocade Network Advisor SMI Agent is in direct connection with one of the
fabrics connected with the shared AG, the user can see all the ports of AG, but the topology
traversal works only for that fabric alone.The user can also traverse through the mapped F_Ports of
the N_Ports (which is connected to the edge fabric switch) to the end devices.
Switch 1
HBA1
n1
F1
AG
Fabric 1
F1 N1
n2 F2 N2
N3
F3
HBA2 N4
Switch 2
F2
n3
HBA3
Fabric 2
FIGURE 49 AG mapping with multiple fabrics
AG with NPIV
Figure 50 represents the AG with NPIV model where the switch is connected to AG and the AG is
connected to HBAs that has one NPIV-enabled device with two virtualized ports.
Figure 51 is the combination of AG and NPIV data models.

53-1004153-01
HBA1
n1
AG Switch 1
F1 N1 F1
n2 F2
N2 F2
F3
HBA2
n3
Virtualized Ports
HBA3
NPIV Device
FIGURE 50 AG with NPIV mapping

53-1004153-01
FIGURE 51 AG and NPIV data model

53-1004153-01
Figure 52 shows a simplified instance diagram to illustrate the combination of the AG and NPIV,
and Topology View features
FIGURE 52 AG with NPIV instance diagram
The following Brocade Network Advisor SMI Agent classes are defined in
Brocade_AccessGateway.mof:

53-1004153-01
Brocade_AccessGateway
Brocade_AGFCPort
Brocade_AGFCPortStats
Brocade_AGFCPortStatisticsCollection
Brocade_AGFCPortRateStats
Brocade_PortRateStatsForAGFCPort
Brocade_PortStatsForAGFCPort
Brocade_AGFCPortStatsInAGFCPortStatisticsCollection
Brocade_AGFCPortStatisticsCollectionForAG
Brocade_AGNode
Brocade_AGSANProtocolEndPoint
Brocade_AGMgmtAccessPoint
Brocade_AGSoftwareIdentity
Brocade_AGWebGUIRemoteAccessPoint
Brocade_AGInFabric
Brocade_AGNodeInAG
Brocade_AGFCPortInAGNode
Brocade_AGFCPortInTrunk
Brocade_PortInAG
Brocade_AGFCPortSANProtocolEndPoint
Brocade_AGHostedSANAccessPoint
Brocade_AGSANActiveConnection
Brocade_AGHostedRemoteAccessPoint
Brocade_AGHostedMgmtAccessPoint
Brocade_AGSANProtocolEndPointLogicalIdentity
Brocade_NodeFCPortDependency
Brocade_EthernetAccessGateway
Brocade_EthernetPortInEthernetAccessGateway
Brocade_EthernetAGInEthernetAdminDomain
Brocade_EthernetAccessGatewayHostedLANEndPoint
Limitations
The following are the limitations of Brocade Network Advisor SMI Agent:
AG on Ethernet switch
- No Brocade_AGFCPort instances are discovered for the Virtual FCoE ports on the Ethernet
AG.
- Brocade_AGSANActiveConnection, Brocade_TopologyView discovery (and related
associations), Brocade_AGSANProtocolEndPointLogicalIdentity,
Brocade_SANActiveConnection, and Brocade_NodeFCPortDependency will not be
complete for the devices attached to the Ethernet AG.

53-1004153-01
FRU profiles 3
AG on Encryption Switch, where the Encryption Switch AG is the Seed switch.

The loop devices are not supported when attached to AG.
The value of LLDP-DCBX for AG port if AG is not available in Brocade Network Advisor.
- The SMI Agent populates this property as Unknown in Brocade_EthernetAccessGateway
if the instance is retrieved through enumerateInstances.
- The correct value of this property can obtained through the getInstance() intrinsic
operation only.
The Ethernet switch instance is not delivered if Ethernet switch is discovered through IP Tab
alone.
FRU profiles
The Fan, Power Supply, and Sensors (FRU) profiles model discovery of a switch's field-replaceable
units (FRUs).
Registration
Refer to Figure 53 for profile registration details.
Data model
Figure 53 shows the data model with the classes and properties that supports the FRU subprofiles.

53-1004153-01
3 FRU profiles
FIGURE 53 FRUs data model
Limitations
FRU support for EOS switch is limited. If the mandatory properties cannot be fully populated, those
instances will not be advertised as conforming to the respective profile.

53-1004153-01
Names 3
NOTE
The Brocade_NumericSensor returns instances to represent the power usage value for Brocade
6505, 6510 switches, FC 16-32, FC 16-48, FC 8-32E, FC8-48E software Blades, CR16-4, and
CR16-8 core blades which are running on Fabric OS v7.0.1 or later.
Names
Various system objects such as a switch, switch port, device, device port, and so on are identified
by a WWN. For convenience, these system objects may also be assigned a user-friendly name. The
user-friendly name is generally the ElementName property in the instance. This feature provides
the ability to easily discover the user-friendly names for all the system objects.
The following are the functions:
Discovering the list of user-friendly names.
There will be no support for setting of Name for a system object.
Fabric names will not be reported by the Brocade SMI Agent. This is to avoid the conflict where
the fabric and seed or principal switch share the same WWN.
All the detached WWN names are supported by the Brocade SMI Agent.
Data model
A new extrinsic method is defined in the Brocade_Agent class.

53-1004153-01
3 Names

53-1004153-01
Chapter
Indications 4
In this chapter
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Alert indications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Life-cycle indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Introduction
The Brocade Network Advisor SMI Agent delivers events in the form of two types of indications:
alert indications and life-cycle indications.
Alert indications are used to represent all fabric events. To receive the alert indications, the clients
must first register with SNMP traps.
Life-cycle indications are delivered by the classes in reaction to a change in the status of a
connection such as, when elements (for example, switch or node) leave or join the fabric.
The Configuration tool allows you to enable mutual authentication for indications. If this is enabled,
all the indications are received over the HTTPS port. By default, the HTTPS is enabled without
mutual authentication.
Alert indications
Table 14 explains the supported alert indications.

53-1004153-01
4 Alert indications
TABLE 14 Supported alert indications

Message ID Trigger Property Value
FC1 One of the following: AlertingManagedElement COP of Brocade_Fabric

Zoning database merge was AlertingElementFormat COP
completed.
How to trigger: Create a zoning AlertType Device Alert
configuration on two switches. Connect
OtherAlertType N/A
the two switches through an E_Port.
Configuration was saved into AlertSubType Database Change
persistent store. Completed
How to trigger: Change the zoning
PerceivedSeverity 2 (Informational)
configuration and save the configuration.
You can also do this through the CLIs ProbableCause 123
zoneadd and cfgsave.
SystemCreationClassName Brocade_Fabric
Configuration was disabled and now
the previously active configuration is SystemName Fabric WWN
inactive. Note that when a zone
configuration is disabled and the ProviderName Brocade_AlertIndication
default zoning mode is set to Provider
NoAccess, then the zone OwningEntity SNIA
configuration is enabled and the
ConfigEnabled indication is Message Zone database changed
delivered. for <Fabric Identity Type>
How to trigger: Disable the zoning <WWN>
configuration. You can also do this MessageArguments Fabric, Fabric WWN
through the CLI cfgdisable.
Configuration changes made were
committed.
How to trigger: Commit zone changes
using the CLI cfgsave or using the SMI
Brocade_ZoneService.SessionControl
extrinsic method.
Query: SELECT * FROM
CIM_AlertIndication WHERE
OwningEntity=SNIA and MessageID=FC1

53-1004153-01
Alert indications 4
TABLE 14 Supported alert indications (Continued)

FC2 Configuration was enabled, and now this AlertingManagedElement COP of Brocade_Fabric
configuration is the active configuration.
AlertingElementFormat COP
CIM_AlertIndication WHERE AlertType Device Alert
OtherAlertType N/A
How to trigger: Enable the zoning
configuration. You can also do this AlertSubType Config Enabled
through the CLIs zonadd, cfgsave, and
cfgenable. PerceivedSeverity 5 (Major)
ProbableCause 123
SystemName Fabric WWN
ProviderName Brocade_AlertIndication
Provider
OwningEntity SNIA
Message ZoneSet <ZoneSet
Name> was activated for
fabric <WWN>
MessageArguments ZoneSet name Fabric
WWN
FC5 Change in operational status for switch. AlertingManagedElement COP of Brocade_Switch
OwningEntity=SNIA and MessageID=FC5 AlertType Device Alert
OtherAlertType N/A
AlertSubType Switch modified
PerceivedSeverity 5 (Major)
ProbableCause 123
SystemCreationClassName Brocade_Switch
SystemName Switch WWN
Provider
OwningEntity SNIA
Message Switch <Switch Unique
Identifier> in Fabric
<Fabric Name> status
changed to <Switch
OperationalStatus>
MessageArguments Switch WWN, fabric
WWN, switch operational
status

53-1004153-01
4 Alert indications

FC6 For fabric merge and segmentation. AlertingManagedElement COP of Brocade_Fabric

OwningEntity=SNIA and MessageID=FC6 AlertType Device Alert
OtherAlertType N/A
AlertSubType Fabric Merge or Fabric
Segmentation
PerceivedSeverity 4 (Minor)
ProbableCause 123
Provider
OwningEntity SNIA
Message <Fabric Name> has
detected a <Fabric
Change>
MessageArguments Fabric WWN merge or
segmentation
FC7 Switch added or removed. Also, AlertingManagedElement COP of Brocade_Switch
applicable in Virtual Fabrics and FCR.
OtherAlertType N/A
AlertSubType Switch added or Switch
removed
PerceivedSeverity 4 (Minor)
ProbableCause 123
Provider
OwningEntity SNIA
Message The fabric <Fabric
Name> has detected
switch <Switch Unique
Identifier> has been
<Fabric Change Type>
MessageArguments Fabric WWN, switch
WWN, Added or
Removed

53-1004153-01
Alert indications 4

FC8 Fabric added or removed. Also, applicable AlertingManagedElement COP of Brocade_Fabric

in Virtual Fabrics.
OtherAlertType N/A
AlertSubType Fabric added or Fabric
removed
ProbableCause 123
Provider
OwningEntity SNIA
Message Fabric <Fabric Identifier>
was <Change Type>FC
Port <Port Identifier> in
<Device Type>
MessageArguments Fabric WWN, Added or
Removed
FC10 Deactivate the active zone configuration AlertingManagedElement COP of Brocade_Fabric
through Brocade Network Advisor or CLI
or Brocade Network Advisor SMI Agent.
Query: SELECT * FROM AlertType Environmental
OwningEntity=SNIA and OtherAlertType N/A
MessageID=FC10 AlertSubType Config Disabled
PerceivedSeverity Informational
ProbableCause 123
Provider
OwningEntity SNIA
Message Zoning was deactivated
for fabric <WWN>
MessageArguments WWN = string Fabric
Principal WWN

53-1004153-01
4 Alert indications

Core6 Switch login was attempted. AlertingManagedElement COP of Brocade_Switch

OwningEntity=SNIA and AlertType Security
MessageID=Core6
OtherAlertType N/A
How to trigger: Telnet to the switch.
NOTE: Core6 indication is supported only AlertSubType New Login
for FOS switches. This indication PerceivedSeverity Informational
is not delivered if SNMP
registration fails. ProbableCause 123
Core6 indications are delivered
when trackChangeset and SNMP
forward options are enabled in SystemName Switch WWN
switch.
Provider
OwningEntity SNIA
Message <Device Type> <Device
Unique Identifier> user
<User> <Login
Operation>
MessageArguments Device Type = Switch;
Unique Identifier = WWN;
User = UserName;
Login Operation = logged
in

53-1004153-01
Alert indications 4

Core6 Switch logout occured. AlertingManagedElement COP of Brocade_Switch

OwningEntity=SNIA and AlertType Security
MessageID=Core6
OtherAlertType N/A
How to trigger: Exit from the Telnet
session. AlertSubType Logout
NOTE: Core6 indication is supported only PerceivedSeverity 2 (Informational)
for FOS switches. This indication
is not delivered if SNMP ProbableCause 123
registration fails.
Core6 indications are delivered
when trackChangeset and SNMP SystemName Switch WWN
forward options are enabled in
switch. ProviderName Brocade_AlertIndication
Provider
OwningEntity SNIA
<User> <Login
Operation>
Device Unique Identifier
= WWN;
User = UserName;
Login operation = logged
out

53-1004153-01
4 Alert indications

Core8 Change in operational status for port. AlertingManagedElement COP of

Query: SELECT * FROM Brocade_SwitchFCPort
OwningEntity=SNIA and
MessageID=Core8 AlertType Device Alert
OtherAlertType Port Alert
AlertSubType FC Port operational
status modified
ProbableCause 123
Provider
OwningEntity SNIA
Message <Device Unique
Identifier> status
changed to <Port
Status>
MessageArguments SwitchFCPort WWN,
Switch
Core 10 User login failure AlertingManagedElement COP of Brocade_Switch
OwningEntity=SNIA and MessageID=Core AlertType Security
10
OtherAlertType N/A
How to trigger: Telnet to the switch and
provide an incorrect password. AlertSubType User Login Failure
NOTE: BRCD2 is now replaced with PerceivedSeverity 3 (Warning)
Core10. Core 10 indication is
supported only for FOS switches. ProbableCause 123
This indication is not delivered if
SNMP registration fails.
Core 10 indications are delivered SystemName Switch WWN
when trackChangeset and SNMP
forward options are enabled in ProviderName Brocade_AlertIndication
switch. Provider
OwningEntity SNIA
<User> had login failure
Unique Identifier = WWN;
User = UserName

53-1004153-01
Alert indications 4

BRCD4 Configuration changed AlertingManagedElement COP of Brocade_Switch

OwningEntity=BROCADE and AlertType Other
MessageID=BRCD4
OtherAlertType Switch Alert
How to trigger: Perform the CLI
configdownload to the switch. AlertSubType Config Change
NOTE: BRCD4 Indication is a switch Alert PerceivedSeverity 2 (Informational)
indication and it is applicable only
to FOS switches. This indication is ProbableCause 123
not delivered if SNMP registration
is failed.
Provider
OwningEntity BROCADE
Message Configuration changed
for Switch <WWN>
MessageArguments WWN = stringSwitch
WWN
BRDC5 SNMP traps were turned on to alert user AlertingManagedElement COP of Brocade_Switch
login and logout attempts.
CIM_AlertIndication WHERE AlertType Other
OwningEntity=BROCADE and
MessageID=BRCD5 OtherAlertType Switch Alert
How to trigger: Use the trackchangesset AlertSubType Track Change On
CLI command to turn on the SNMP traps.
NOTE: BRCD5 indication is supported
only for FOS switches and is not ProbableCause 123
delivered if SNMP registration is
failed.
Provider
Message Alert configuration for
login, logout or config
updates was turned ON
for Switch <WWN>
MessageArguments WWN = string Switch
WWN

53-1004153-01
4 Alert indications

BRDC6 SNMP traps turned on by Track Change AlertingManagedElement COP of Brocade_Switch

On was turned off.
How to trigger: Use the trackchangesset AlertSubType Track Change Off
CLI command to turn off the SNMP traps.
only for FOS switches and is not ProbableCause 123
delivered if SNMP registration is
failed.
Provider
Message Alert configuration for
login, logout, orconfig
updates was turned OFF
for Switch <WWN>
WWN
BRCD7 The element (port) identified by AlertingManagedElement COP of
AlertingManagedElement is up. Brocade_SwitchFCPort
OwningEntity=SNIA and AlertType Other
MessageID=BRCD7
run the CLI portenable portnumber to AlertSubType Up
enable a connected port, such as an
E_Port, F_Port, or L_Port. PerceivedSeverity 2 (Informational)
ProbableCause 123
Provider
Message Port <PortWWN> of
Switch <SwitchWWN> is
up
MessageArguments SwitchFCPort WWN
Switch WWN

53-1004153-01
Alert indications 4

BRCD8 The element (port) identified by AlertingManagedElement COP of

AlertingManagedElement is down. Brocade_SwitchFCPort
OwningEntity=SNIA and AlertType Other
MessageID=BRCD8
run the CLI portdisable portnumber to AlertSubType Down
disable a connected port, such as an
E_Port, F_Port, or L_Port. PerceivedSeverity 2 (Informational)
ProbableCause 123
Provider
Message Port <PortWWN> of
Switch <SwitchWWN> is
down
MessageArguments PortWWN =
SwitchFCPort WWN
Switch WWN=string
Switch WWN
BRCD12 A single device came online. AlertingManagedElement COP of Brocade_Node
MessageID=BRCD12
run the CLI portenable portnumber where AlertSubType Connected Port Online
the port is an F_Port.
ProbableCause 123
Provider
Message A single device named
<WWN> came online for
fabric named
<FabricWWN>
MessageArguments Device WWN, Fabric
WWN

53-1004153-01
4 Alert indications

BRCD13 A single device went offline. AlertingManagedElement COP of Brocade_Node

MessageID=BRCD13
run the CLI portdisable portnumber AlertSubType Connected Port Offline
where the port is an F_Port.
ProbableCause 123
Provider
<WWN> went offline for
fabric named
<FabricWWN>
WWN
BRCD16 A session (transaction) was aborted and AlertingManagedElement COP of Brocade_Fabric
all changes made within that transaction
were discarded.
Query: SELECT * FROM AlertType Other
OwningEntity=BROCADE and OtherAlertType Zone Alert
MessageID=BRCD16 AlertSubType Zone session aborted
How to trigger: Abort zone changes using
the CLI cfgabort or using the PerceivedSeverity 2 (Informational)
Brocade_ZoneService.SessionControl ProbableCause 123
extrinsic method.
Provider
OwningEntity Brocade
Message A zoning session was
aborted for fabric named
<WWN>
MessageArguments Switch WWN, port
statusFabric WWN

53-1004153-01
Alert indications 4

BRCD17 A change in session status occurred. AlertingManagedElement COP of Brocade_Fabric

MessageID=BRCD17
OtherAlertType Zone Alert
NOTE: BRCD17 iis supported only for
FOS switches and is not delivered AlertSubType Session Status Changed
if SNMP registration is failed.
PerceivedSeverity Informational
BRCD17 indication is delivered for
online zone data base changes ProbableCause 123
and activation or de-activation.
Provider
Message A change in zoning
session status occurred
for fabric named
<WWN>
MessageArguments WWN = string Fabric
Principal WWN
BRCD18 Registration of the managed element AlertingManagedElement COP of Brocade_Node
with the Admin Domain was completed.
MessageID=BRCD18 OtherAlertType Device Alert
How to trigger: Enable switch connected AlertSubType Registered
to HBA.
NOTE: BRCD18 indication is applicable
only for FOS switches. The ProbableCause 123
indications is delivered only for
FDMI-enabled devices.
Provider
<HBA Device WWN>
registered with the fabric
named <WWN>
WWN

53-1004153-01
4 Alert indications

BRCD19 Deregistration of the managed element AlertingManagedElement COP of Brocade_Node

with the Admin Domain was completed.
How to trigger: Disable switch connected AlertSubType Deregistered
to HBA.
NOTE: BRCD19 indication is applicable
only for FOS switches. The ProbableCause 123
indication is delivered only for
FDMI-enabled devices
Provider
<HBA Device WWN>
deregistered with the
fabric named <WWN>
WWN
BRCD20 State change occurred. AlertingManagedElement COP of Brocade_FCPort
MessageID=BRCD20
OtherAlertType Device Alert
How to trigger: Enable or disable an
E_Port or F_Port. AlertSubType State Changed
ProbableCause 123
Provider
Message A state change occurred
for device named
<PortWWN> on fabric
named <WWN>
MessageArguments Port WWN, Fabric WWN

53-1004153-01
Alert indications 4

BRCD21 Database changes for a fabric service AlertingManagedElement COP of Brocade_Node

were completed.
How to trigger: Enable or disable switch AlertSubType Database Change
connected to HBA. Completed
ProbableCause 123
Provider
Message Device database change
completed for fabric
named <WWN>
MessageArguments Fabric WWN
BRCD24 Download of firmware to the element was AlertingManagedElement COP of Brocade_Switch
initiated.
How to trigger: Initiate firmware download AlertSubType Firmware download
from CLI. started
NOTE: BRCD24 indication is not PerceivedSeverity 2 (Informational)
applicable for EOS switches.
ProbableCause 123
Provider
Message Firmware download
started for switch
<WWN>
MessageArguments Switch WWN

53-1004153-01
4 Alert indications

BRCD25 Download of firmware was completed. AlertingManagedElement COP of Brocade_Switch

MessageID=BRCD25
NOTE: BRCD25 indication is not
applicable for EOS switches. AlertSubType Firmware download
completed
ProbableCause 123
Provider
Message Firmware download
completed for switch
<WWN>
BRCD26 HA Failover has completed. AlertingManagedElement COP of Brocade_Switch
MessageID=BRCD26
OtherAlertType HA Alert
How to trigger: After establishing the
connection to switch from Brocade SMI AlertSubType Failover completed
Agent, perform an HA failover on the
switch from the CLI. PerceivedSeverity 2 (Informational)
NOTE: BRCD26 indication is not ProbableCause 123

supported for EOS switches.
Provider
Message HA failover has
completed for Switch
<WWN>
MessageArguments SwitchWWN

53-1004153-01
Alert indications 4

BRCD27 Account is locked out on the switch. This AlertingManagedElement COP of Brocade_Switch
event occurs whenever a switch account
gets locked out.
Query: SELECT * FROM AlertType Security
OwningEntity=BROCADE and OtherAlertType N/A
MessageID=BRCD27 AlertSubType Account locked out
How to trigger: Set the lockout duration
as 1 using the CLI Pasargadae --set for a PerceivedSeverity 2 (Informational)
user account. Attempt to telnet to the ProbableCause 123
switch with a wrong password for that
user account. SystemCreationClassName Brocade_Switch
NOTE: BRCD27 indication is not SystemName Switch WWN
Provider
Message Account for user
<username> was locked
out for Switch <WWN>
MessageArguments Account User Name,
Switch WWN
BRCD28 New user account is added to the switch. AlertingManagedElement COP of Brocade_Switch
OwningEntity=BROCADE and AlertType Security
MessageID=BRCD28
OtherAlertType N/A
How to trigger: Add a new account using
the CLI userconfig. AlertSubType Account added
NOTE: BRCD28 indication is not PerceivedSeverity Informational
delivered for FOS switches, if
SNMP registration fails. ProbableCause 123
Provider
<username> was added
for Switch <WWN>
MessageArguments username = string user
name
WWN = string Switch
WWN

53-1004153-01
4 Alert indications

BRCD29 Account was deleted on the switch. AlertingManagedElement COP of Brocade_Switch

MessageID=BRCD29
OtherAlertType N/A
How to trigger: Delete an existing account
using the CLI userconfig. AlertSubType Account deleted
NOTE: BRCD29 indication is not PerceivedSeverity Informational
delivered for FOS switches, if
SNMP registration fails. ProbableCause 123
Provider
<username> was
deleted for Switch
<WWN>
name
WWN = string Switch
WWN
BRCD30 Role has changed for the user account on AlertingManagedElement COP of Brocade_Switch
the switch.
CIM_AlertIndication WHERE AlertType Security
MessageID=BRCD30 OtherAlertType N/A
How to trigger: Modify the role of an AlertSubType Account role changed
existing account using the CLI userconfig.
NOTE: BRCD30 indication is not
delivered for FOS switches, if ProbableCause 123
SNMP registration fails.
Provider
<username> role
changed for Switch
<WWN>
name
WWN = string Switch
WWN

53-1004153-01
Alert indications 4

BRCD31 Account membership has changed. AlertingManagedElement COP of Brocade_Switch

MessageID=BRCD31
OtherAlertType N/A
How to trigger: Modify the AD
membership of an existing account using AlertSubType Account membership
the CLI userconfig. changed
NOTE: BRCD31 indication is not PerceivedSeverity 2 (Informational)
ProbableCause 123
Provider
<username>
membership changed for
Switch <WWN>
MessageArguments Account username,
Switch WWN
BRCD32 Password is expiring. This indication is AlertingManagedElement COP of Brocade_Switch
delivered only when the Brocade Network
Advisor SMI Agent attempts login to a
fabric in which the login password is AlertType Security
expiring on the seed switch.
Query: SELECT * FROM OtherAlertType N/A
CIM_AlertIndication WHERE AlertSubType Password expiring
MessageID=BRCD32 PerceivedSeverity 2 (Informational)
How to trigger: When the password is in ProbableCause 123
an expiring state, attempt to log in to the
switch from the Brocade Network Advisor SystemCreationClassName Brocade_Switch
SMI Agent. SystemName Switch WWN
BRCD32 indication is not supported for
EOS switches. ProviderName Brocade_AlertIndication
Provider
Message Password is expiring for
the Switch <WWN>

53-1004153-01
4 Alert indications

BRCD33 Password has expired. This indication is AlertingManagedElement COP of Brocade_Switch

delivered only when the Brocade Network
Advisor SMI Agent attempts login to a
fabric in which the login password has AlertType Security
expired on the seed switch.
Query: SELECT * FROM OtherAlertType N/A
CIM_AlertIndication WHERE AlertSubType Password expired
MessageID=BRCD33 PerceivedSeverity 2 (Informational)
How to trigger: Expire a password using ProbableCause 123
the CLI passwdcfg --set user. Attempt
client connection through the Brocade SystemCreationClassName Brocade_Switch
Network Advisor SMI Agent with the SystemName Switch WWN
expired password.
NOTE: BRCD33 indication is not ProviderName Brocade_AlertIndication
supported for EOS switches. Provider
Message Password has expired for
Switch <IP Address>
MessageArguments Switch IP Address
BRCD35 An active connection went inactive. AlertingManagedElement COP of Brocade_Switch
MessageID=BRCD35
OtherAlertType Connection Alert
How to trigger: After establishing the
connection to the switch from the AlertSubType Connection deactivated
Brocade Network Advisor SMI Agent,
reboot the switch. PerceivedSeverity 2 (Informational)
NOTE: BRCD35 indication is supported ProbableCause 123

only for FOS switches. This
indications is not delivered if
SNMP registration fails. SystemName Switch WWN
Provider
Message An active connection for
Switch <WWN> went
inactive
WWN

53-1004153-01
Alert indications 4

BRCD42 enumerateInstanceNames or AlertingManagedElement Failed COP or COP

enumerateInstances failed. without key properties.
OwningEntity=BROCADE and AlertType Processing Error
MessageID=BRCD42
OtherAlertType N/A
NOTE: Mapping of
AlertingManagedElement AlertSubType N/A
property
AlertingManagedElement for
enumerateInstanceNames and ProbableCause 49
enumerateInstances, path of
class which is in error. For SystemCreationClassName Brocade_ManagementS
example, erver
enumerateInstanceNames on SystemName HostName
Brocade_Fabric has this as
CIMObjectPath (Brocade_Fabric, ProviderName Brocade_AlertIndication
root/brocade1). In case of Provider
associatorNames, associators, OwningEntity BROCADE
referenceNames, and references
path, they have the actual Message A processing error
CIMObjectPath of the input. occurred for method
<method name>
MessageArguments method name =
enumerateInstanceNam
es or associatorNames
and so on.
BRCD43 Multiple devices (typically within a loop) AlertingManagedElement COP of Brocade_Node
came online.
MessageID=BRCD43 OtherAlertType Port Alert
How to trigger: Telnet to the switch and AlertSubType Connected Area Online
run the CLI portenable portnumber where
the port is an L_Port. PerceivedSeverity 2 (Informational)
ProbableCause 123
Provider
Message One or more devices
came online for fabric
named <WWN>

53-1004153-01
4 Alert indications

BRCD44 Multiple devices (typically within a loop) AlertingManagedElement COP of Brocade_Node

went offline.
MessageID=BRCD44 OtherAlertType Port Alert
How to trigger: Telnet to the switch and AlertSubType Connected Area Offline
run the CLI portdisable portnumber
where the port is an L_Port. PerceivedSeverity 2 (Informational)
ProbableCause 123
Provider
Message One or more devices
went offline for fabric
named <WWN>
BRCD46 Blade faulted. This happens when a blade AlertingManagedElement COP of Brocade_Switch
is plugged in to a system running an
unsupported chassis configuration.
OwningEntity=BROCADE and OtherAlertType Blade Alert
MessageID=BRCD46 AlertSubType Blade Faulted
NOTE: BRCD46 Indication is applicable
only for FOS switches.
ProbableCause 123
Provider
Message Blade faulted because
the switch <WWN> runs
under unsupported
chassis-configuration

53-1004153-01
Alert indications 4

BRCD48 A data value is greater than the high AlertingManagedElement COP of Brocade_Switch
threshold boundary.
CIM_AlertIndication WHERE AlertType Other Alert
MessageID=BRCD48 OtherAlertType Fabric Watch
NOTE: BRCD48 indication is supported AlertSubType Threshold Above

for the Environment, Port, and
E_Port Fabric Watch classes.
Ignore the Fabric Watch ProbableCause 123
indications for non-supported
Fabric Watch classes (GBIC or SystemCreationClassName Brocade_Switch
SFP, Fabric, F and FL Port, SAM, SystemName Switch WWN
Security), as they are not
supported. ProviderName Brocade_AlertIndication
BRCD48 is supported in switches Provider
running Fabric OS v6.1.0 and OwningEntity BROCADE
later.
Message Fabric Watch Threshold
Above
MessageArguments N/A
BRCD49 A data value is less than the low AlertingManagedElement COP of Brocade_Switch
threshold boundary.
NOTE: BRCD49 indication is supported AlertSubType Threshold Below

SFP, Fabric, F and FL Port, SAM, SystemName Switch WWN
later.
Below

53-1004153-01
4 Alert indications

BRCD51 Successful recovery from a faulty AlertingManagedElement COP of Brocade_Switch

condition.
NOTE: BRCD51 indication is supported AlertSubType Threshold In Between

SFP, Fabric, F and FL Port, SAM, SystemName Fabric WWN
later.
In Between
BRCD52 A counter value between two sample AlertingManagedElement COP of Brocade_Switch
periods has changed.
NOTE: BRCD52 indication is supported AlertSubType Threshold Change

SFP, Fabric, F/FL Port, SAM, SystemName Switch WWN
later.
Changed

53-1004153-01
Alert indications 4

BRCD53 Switch state changed. AlertingManagedElement COP of Brocade_Switch

MessageID=BRCD53
AlertSubType Switch status changed
ProbableCause 123
Provider
Message Switch <WWN> status
changed to <state>
MessageArguments Switch WWN, Switch
state (offline or online)
BRCD54 Switch not reachable AlertingManagedElement COP of Brocade_Switch
MessageID=BRCD54
NOTE: BRCD54 indication is delivered
once the asset collection cycle is AlertSubType Switch not reachable
done in Brocade Network Advisor.
ProbableCause 123
Provider
Message Switch <WWN> is not
reachable

53-1004153-01
4 Alert indications

BRCD56 Fabric ID of a logical fabric changed. AlertingManagedElement COP of Brocade_Fabric

MessageID=BRCD56
OtherAlertType Virtual Fabric Alert
only for FOS switches and it is not AlertSubType VF FID Conflict
delivered if SNMP registration
fails.
ProbableCause 123
Provider
Message FID conflict occured in
Logical Switch
MessageArguments WWN = string switch
WWN
BRCD57 Switch status changed because of the AlertingManagedElement COP of Brocade_Fabric
hardware failures like fans, power supply,
temp sensors.
OwningEntity=BROCADE and OtherAlertType FRU Alert
MessageID=BRCD57 AlertSubType FRU Faulted
only for FOS switches. If SNMP
registration fails, then BRCD57 ProbableCause 123
indication is not delivered for FOS
switches. SystemCreationClassName Brocade_Switch
Provider
Message Switch <WWN> status
change contributing
factor <FRU>
WWN,
FRU = Power Supply,
FAN, or Temperature
Sensor

53-1004153-01
Alert indications 4

BRCD58 Discovered port count is in the grace AlertingManagedElement COP of

limit, and is about to exceed the licensed Brocade_ManagementS
port count. erver
AlertingElementFormat 2
OwningEntity=BROCADE and AlertType 2
MessageID=BRCD58
OtherAlertType N/A
AlertSubType About to exceed licensed
port count
PerceivedSeverity 3 (Degraded or Warning)
ProbableCause 123
SystemCreationClassName Brocade_ManagementS
erver
SystemName Brocade Network Advisor
Server host name
Provider
Message The current number of
managed ports
<managed port count>
is about to exceed your
licensed port count of
<licensed port count>
ports.
MessageArguments Managed port count,
Port count limit

53-1004153-01
4 Alert indications

BRCD59 Discovered port count exceeded the AlertingManagedElement COP of

licensed port count. Brocade_ManagementS
Query: SELECT * FROM erver
AlertingElementFormat 2
MessageID=BRCD59 AlertType 2
OtherAlertType N/A
AlertSubType Port Count Limit
Exceeded
PerceivedSeverity 6 (Critical)
ProbableCause 123
SystemCreationClassName Brocade_ManagementS
erver
SystemName Brocade Network Advisor
Server host name
Provider
Message The current number of
managed ports
<Managed port count>
has exceeded your
licensed port count of
<licensed port count>
ports.
MessageArguments Managed port count,
Port count limit
BRCD60 SNMP registration failed AlertingManagedElement COP of Brocade_Switch
MessageID=BRCD60
only for FOS switches. AlertSubType SNMP registration failed
ProbableCause 123
Provider
Message SNMP registration failed
for switch <SwitchWWN>
WWN

53-1004153-01
Alert indications 4

BRCD61 LAG successfully enabled AlertingManagedElement COP of Brocade_LAG

MessageID=BRCD61
OtherAlertType CEE Switch Alert
AlertSubType Config enabled
ProbableCause 123
SystemCreationClassName Brocade_
EthernetSwitch
Provider
Message LAG <LAG ID> enabled
on EthernetSwitch
<switch IP>
MessageArguments Lag ID, core switch IP
BRCD62 LAG successfully disabled AlertingManagedElement COP of Brocade_LAG
MessageID=BRCD62
AlertSubType Config disabled
ProbableCause 123
EthernetSwitch
Provider
Message LAG <LAG ID disabled on
EthernetSwitch <switch
IP>
MessageArguments Lag ID, core switch IP

53-1004153-01
4 Alert indications

BRCD63 ACL configured on LAG AlertingManagedElement COP of Brocade_LAG

MessageID=BRCD63
ProbableCause 123
EthernetSwitch
Provider
Message CEEACL Policy <ACL
Policy Name> assigned
to LAG <LAG ID> in
EthernetSwitch <Switch
IP>
MessageArguments ACL name, Lag ID, core
switch IP
BRCD64 ACL removed from LAG AlertingManagedElement COP of Brocade_LAG
MessageID=BRCD64
AlertSubType Config removed
ProbableCause 123
EthernetSwitch
Provider
Message CEEACL Policy <ACL
Policy Name> removed
from LAG <LAG ID> in
IP>
MessageArguments ACL name, Lag ID, core
switch IP

53-1004153-01
Alert indications 4

BRCD65 TE port enabled AlertingManagedElement COP of Brocade_

Query: SELECT * FROM EthernetPort
MessageID=BRCD65 AlertType Other
AlertSubType Up
ProbableCause 123
EthernetSwitch
Provider
Message EthernetPort <portmac>
enabled on
IP>
MessageArguments Port mac address, core
switch IP
BRCD66 TE port disabled AlertingManagedElement COP of Brocade_
AlertSubType Down
ProbableCause 123
EthernetSwitch
Provider
Message EthernetPort <portmac>
disabled on
IP>
switch IP

53-1004153-01
4 Alert indications

BRCD67 ACL configured on TE port AlertingManagedElement COP of Brocade_

ProbableCause 123
EthernetSwitch
Provider
Message CEEACL Policy <Policy
name> assigned to
EthernetPort <portmac>
on EthernetSwitch
<Switch ip>
MessageArguments ACL name, port MAC
address, core switch IP

53-1004153-01
Alert indications 4

BRCD68 ACL removed on TE port AlertingManagedElement COP of Brocade_

ProbableCause 123
EthernetSwitch
Provider
Message CEEACL Policy <Policy
name> removed from
EthernetPort
<portmac>on
EthernetSwitch <core
switch IP>
MessageArguments ACL name, port MAC
address, core switch IP

53-1004153-01
4 Alert indications

BRCD69 QoS CEE map configured on TE port. AlertingManagedElement COP of Brocade_

ProbableCause 123
EthernetSwitch
Provider
Message CEEMap <Map name>
assigned to EthernetPort
<portmac> on
IP>
MessageArguments CEE map name, port
mac address, core
switch IP

53-1004153-01
Alert indications 4

BRCD70 QoS CEE map removed on TE port. AlertingManagedElement COP of Brocade_

ProbableCause 123
EthernetSwitch
Provider
Message CEEMap <Map name>
removed from
EthernetPort
<portmac>on
IP>
MessageArguments CEE map name, port
mac address, core
switch IP

53-1004153-01
4 Alert indications

BRCD71 LLDP enabled on TE port. AlertingManagedElement COP of Brocade_

ProbableCause 123
EthernetSwitch
Provider
Message LLDP enabled on
EthernetPort <portmac>
on EthernetSwitch <core
switch IP>
switch IP
BRCD72 Virtual FCoE port enabled. AlertingManagedElement COP of
Query: SELECT * FROM Brocade_switchFCPort
AlertSubType Up
ProbableCause 123
SystemCreationClassName Brocade_EthernetSwitch
Provider
Message Virtual FCoE Port
<portWwn> enabled on
switch IP>
MessageArguments port WWN, core switch IP

53-1004153-01
Alert indications 4

BRCD73 Virtual FCoE port disabled. AlertingManagedElement COP of Brocade_

Query: SELECT * FROM switchFCPort
AlertSubType Down
ProbableCause 123
SystemCreationClassName Brocade_EthernetSwitch
Provider
Message Virtual FCoE Port
<portWWN> disabled on
switch IP>
MessageArguments port WWN, core switch IP
BRCD74 ACL assigned to VLAN. AlertingManagedElement COP of Brocade_VLAN
MessageID=BRCD74
ProbableCause 123
EthernetSwitch
Provider
Message CEEACL<Policy Name>
assigned to VLAN<VLAN
No> on EthernetSwitch
<core switch IP>
MessageArguments ACL name, VLAN ID, Core
switch IP

53-1004153-01
4 Alert indications

BRCD75 ACL removed from VLAN. AlertingManagedElement COP of Brocade_VLAN

MessageID=BRCD75
ProbableCause 123
EthernetSwitch
Provider
Message CEEACL<Policy Name>
removed from
VLAN<VLAN ID> on
switch IP>
MessageArguments ACL name, VLAN ID, Core
switch IP

53-1004153-01
Alert indications 4

BRCD76 VLAN member modified. AlertingManagedElement COP of Brocade_VLAN

MessageID=BRCD76
AlertSubType Config Changed
ProbableCause 123
EthernetSwitch
Provider
Message LAG <LAG ID>
added to VLAN
<VLAN ID>
LAG <LAG ID>
removed from VLAN
<VLAN ID>
EthernetPort
<PortMac> added
to VLAN <VLAN ID>
EthernetPort
<PortMac> added
to VLAN <VLAN ID>
EthernetPort
<PortMac>
removed from VLAN
<VLAN ID>
MessageArguments For I and II
LAG ID, VLAN ID
For III and IV
Port MAC address, VLAN
ID

53-1004153-01
4 Alert indications

BRCD101 Fabric principal switch WWN changed. AlertingManagedElement COP of Brocade_Fabric

OwningEntity=BROCADE and AlertType Device Alert
MessageID=BRCD101
OtherAlertType N/A
AlertSubType Principal switch WWN
changed
ProbableCause 123
Provider
Message Principal switch <WWN>
changed to <WWN>
MessageArguments old principal switch WWN
new principal switch
WWN
BRCD102 SAN zone activation error. This alert AlertingManagedElement COP of Brocade_Switch
indication is delivered for each fabric
failure.
OwningEntity= BROCADE and OtherAlertType Zone alert
MessageID=BRCD102 AlertSubType SANZone activation
NOTE: This indication is delivered only if failed
the operation is done through
Brocade Network Advisor SMI
Agent. ProbableCause 123
Provider
Message SANZone activation
failed for fabric <WWN>

53-1004153-01
Alert indications 4

BRCD103 Switch resources violation. AlertingManagedElement COP of Brocade_Switch

OwningEntity=" BROCADE " and AlertType Device
MessageID="BRCD103"
OtherAlertType N/A
AlertSubType MAPS violation
PerceivedSeverity 3 (WARN)
ProbableCause 123
Provider
Message Condition= <Threshold
Condition> Value=
<Current value>
RuleName=
<RuleName> Category=
<Category>
MessageArguments <Threshold
Condition>,<Current
value>, <RuleName>,
SW_RESOURCES

53-1004153-01
4 Alert indications

BRCD104 Switch policy status violation. AlertingManagedElement COP of Brocade_Switch

MessageID="BRCD104"
OtherAlertType N/A
ProbableCause 123
Provider
Condition> Value=
<Current value>
RuleName=
<Category>
Condition>,<Current
value>, <RuleName>,
SW_RESOURCES
BRCD105 Switch security violation. AlertingManagedElement COP of Brocade_Switch
MessageID="BRCD105"
OtherAlertType N/A
ProbableCause 123

53-1004153-01
Alert indications 4

Provider
Condition> Value=
<Current value>
RuleName=
<Category>
Condition>,<Current
value>, <RuleName>,
SEC_VIOLATIONS
BRCD106 Flow vision violation. AlertingManagedElement COP of
Query: SELECT * FROM Brocade_SwitchFcport
OwningEntity=" BROCADE " and
MessageID="BRCD106" AlertType Device
OtherAlertType N/A
ProbableCause 123
SystemCreationClassName Brocade_SwitchFcport
Provider
Condition> Value=
<Current value>
RuleName=
<Category>
Condition>,<Current
value>, <RuleName>,
TRAF_PERF

53-1004153-01
4 Alert indications

BRCD107 Fabric health violation. AlertingManagedElement COP of Brocade_Fabric

MessageID="BRCD107"
OtherAlertType N/A
ProbableCause 123
Provider
Condition> Value=
<Current value>
RuleName=
<Category>
MessageArguments Threshold
Condition>,<Current
value>, <RuleName>,
FABRIC_HEALTH

53-1004153-01
Alert indications 4

BRCD109 SwitchFcPort level violation. AlertingManagedElement COP of

Query: SELECT * FROM Brocade_SwitchFcport
OwningEntity=" BROCADE " and
MessageID="BRCD109" AlertType Device
OtherAlertType N/A
ProbableCause 123
SystemCreationClassName Brocade_SwitchFCport
Provider
Condition> Value=
<Current value>
RuleName=
<Category>
Condition>,<Current
value>, <RuleName>,
PORT_HEALTH
NOTE
For indications from BRCD61 to BRCD76:
All CEE alert indications and life-cycle indications are only applicable for FOS switches (Brocade
8000 switch and FCOE10-24 blade) with versions from v6.4.0. To get all CEE indications, make sure
that CEE indication is enabled in the switch.
NOTE
For indications from BRC103 to BRC109:
SNMP traps must be registered for the switches to receive the indication.

53-1004153-01
4 Life-cycle indications
Life-cycle indications
Table 15 explains the supported life-cycle indications.
TABLE 15 Supported life-cycle indications

Query Indication type Notes
SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_InstCreation When new fabric is discovered
Brocade_Fabric
SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_InstDeletion When the fabric is deleted
Brocade_Fabric
SELECT * FROM CIM_InstModification WHERE SourceInstance CIM_InstModification The operational status of a switch changes.
ISA Brocade_Switch AND SourceInstance.OperationalStatus
<>PreviousInstance. OperationalStatus
SELECT * FROM CIM_InstModification WHERE SourceInstance CIM_InstModification The operational status of a switch port
ISA CIM_FCPort AND SourceInstance.OperationalStatus changes.
SELECT * FROM CIM_InstModification WHERE SourceInstance CIM_InstModification The enabled state of a switch port changes,
ISA CIM_FCPort AND SourceInstance.EnabledState such as when ISL is unplugged and plugged.
<>PreviousInstance.EnabledState
SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_InstCreation Applicable for logical switch also.
CIM_ComputerSystem
SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_InstDeletion Applicable for ComputerSystem also.
CIM_ComputerSystem
SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_InstCreation Port is moved from one logical switch to
CIM_FCPort another logical switch.
SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_InstDeletion Port is moved from one logical switch to
CIM_FCPort another logical switch.
SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_InstCreation A device is added to a fabric.
CIM_LogicalPortGroup
SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_InstDeletion A device is removed from a fabric.
CIM_LogicalPortGroup
SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_InstCreation When a blade is inserted or powered on in
CIM_LogicalModule the switch
SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_InstDeletion When a blade is removed or powered off
CIM_LogicalModule from the switch
SELECT * FROM CIM_InstModification WHERE SourceInstance Complete Applicable to zoning in
ISA CIM_ConcreteJob AND SourceInstance. CIM_InstModification SessionControlWithJob and
CIM_ConcreteJob::PercentComplete <> ActivateZoneSetWithJob
PreviousInstance.CIM_ConcreteJob::Percent
SELECT * FROM CIM_InstModification WHERE SourceInstance CIM_InstModification Applicable to zoning in
ISA CIM_ConcreteJob AND ANY SessionControlWithJob and
SourceInstance.CIM_ConcreteJob::Operation alStatus[*] = 17 ActivateZoneSetWithJob
AND ANY SourceInstance.CIM_ConcreteJob::Operation
alStatus[*] = 2
ISA CIM_ConcreteJob AND ANY SessionControlWithJob and
SourceInstance.CIM_ConcreteJob::Operation alStatus[*] = 17 ActivateZoneSetWithJob
AND ANY SourceInstance.CIM_ConcreteJob::Operation
alStatus[*] = 6

53-1004153-01
Life-cycle indications 4
TABLE 15 Supported life-cycle indications (Continued)


ISA CIM_ConcreteJob AND SessionControlWithJob and
SourceInstance.CIM_ConcreteJob::JobState <> ActivateZoneSetWithJob
PreviousInstance.CIM_ConcreteJob::JobState
SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_InstCreation Applicable to zoning in
CIM_ConcreteJob SessionControlWithJob and
SELECT * FROM CIM_InstModification WHERE SourceInstance CIM_ InstModification When a blade operational status is changed
ISA CIM_LogicalModule AND SourceInstance.OperationalStatus
SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_InstCreation FAN is inserted to the Brocade Network
Brocade_FAN Advisor managed switch.
SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_InstDeletion FAN is removed from the Brocade Network
Brocade_FAN Advisor managed switch.
SELECT * FROM CIM_InstModification WHERE SourceInstance CIM_InstModification FAN operational status is changed
ISA Brocade_FAN AND SourceInstance.OperationalStatus
SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_InstCreation Power supply is inserted to the Brocade
Brocade_PowerSupply Network Advisor Managed switch.
SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_InstDeletion Power supply is removed from the Brocade
Brocade_PowerSupply Network Advisor Managed switch.
SELECT * FROM CIM_InstModification WHERE SourceInstance CIM_InstModification Power supply operational status is changed
ISA Brocade_PowerSupply AND
SourceInstance.OperationalStatus <>PreviousInstance.
OperationalStatus
SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_InstCreation CEEMap created
Brocade_CEEMap
SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_InstDeletion CEEMap deleted
Brocade_CEEMap
SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_InstCreation ACL policy created
Brocade_CEEACLPolicy
SELECT * FROM CIM_InstModification WHERE SourceInstance CIM_InstModification Rule add or removed in the existing ACL
ISA Brocade_CEEACLRules AND SourceInstance. policy.
ActivityQualifiers <>PreviousInstance. ActivityQualifiers SELECT
* FROM CIM_InstModification WHERE SourceInstance ISA
Brocade_CEEACLRules AND SourceInstance. QualifierFormats
<>PreviousInstance.QualifierFormats
SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_InstDeletion ACL policy deleted
Brocade_CEEACLPolicy
SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_InstCreation LAG created
Brocade_LAG
SELECT * FROM CIM_InstModification WHERE SourceInstance CIM_InstModification LAG interface mode property value is
ISA Brocade_LAG AND changed.
SourceInstance.InterfaceMode<>PreviousInstance.InterfaceMo
de
SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_InstDeletion LAG deleted
Brocade_LAG

53-1004153-01
4 Life-cycle indications
TABLE 15 Supported life-cycle indications (Continued)

SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_InstCreation VLAN created

Brocade_VLAN
SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_InstDeletion VLAN deleted
Brocade_VLAN
SELECT * FROM CIM_InstModification WHERE SourceInstance CIM_InstModification Priority Group modified
ISA Brocade_prioritygroups AND
SourceInstance.ActivityQualifiers <>
PreviousInstance.ActivityQualifiers SELECT * FROM
CIM_InstModification WHERE SourceInstance ISA
Brocade_prioritygroups AND SourceInstance. QualifierFormats
<> PreviousInstance.QualifierFormats
NOTE
Sensors are built in with other FRU elements; and thus InstanceCreation, InstanceDeletion, and
InstanceModification indications are not supported.
When a rule is removed from the ACL policy, indication populates only the sequence number. When
PG ID is removed from CEE map, indication populates only the PG ID. In both the cases, the
indication populates default values for the other properties (priority flow control, bandwidth).

53-1004153-01
Appendix
Brocade Network Advisor SMI Agent Error Codes A
Table 16 lists the Brocade Network Advisor SMI Agent error codes.
TABLE 16 Error codes

Error code Description
4096 Concrete job is started

4099 Concrete job is already running in the fabric
10001 Database error
10002 Unknown error
10003 Brocade Network Advisor error
11001 Fabric not found
11101 Unknown error while accessing the fabric data
11301 Database error while accessing the fabric data
11601 Fabric name set operation failed
11602 Fabric name set operation failed due to unknown error
12001 Switch [XXX] not found
12003 Switch with sequence number XXX not found
12004 Switch not found
12005 Switch model not found
12101 Unknown error while accessing Switch or Topology data)
12102 Error while decrypting password of switch
12104 Switch credential invalid
12301 Database error (while accessing switch)
12401 Switch CAL call connection failed
12402 Switch CAL call error
12403 Switch CAL connection error
12503 Switch name set operation failed
12504 Switch name set operation failed due to unknown error
12505 Switch [SwitchWWN] state [State] not changed
13001 Switch port not found
13101 Unknown error while accessing the Switch FC port
13102 SwitchFCPort statistics failed
13103 SwitchFCPort state set operation failed
13301 Database error while accessing SwitchFCPort

53-1004153-01
A Brocade Network Advisor SMI Agent Error Codes
TABLE 16 Error codes (Continued)

13401 Switch port CAL Error

13402 SwitchFCPort CAL call error
13403 Switch port CAL connection error
13404 SwitchFCPort MPI request failed
13405 Invalid credential for CAL call
13407 SwitchFCPort rate statistics failed
13408 SwitchFCPort rate statistics property is empty
13503 SwitchFCPort name set operation failed
13504 SwitchFCPort name set operation failed due to unknown error
13505 Switch port enabled set operation not supported for M-model
switch
13506 Switch port enabled set operation not supported for TE-ports
13507 Switch port enabled set operation not supported for
unmanaged switch
13508 Switch port enabled set operation not allowed in FMS mode
13509 XISL not found
14001 Blade not found
14101 Blade credential invalid
14102 Unknown error while accessing the blade
14301 Database error while accessing blade
14401 Blade CAL Error
14402 Blade CAL connection error
15001 Device not found
15101 Unknown error while accessing device
15301 Database error while accessing device
16001 Zone does not exist
16002 ZoneSet does not exist
16003 ZoneAlias does not exist
16004 ZoneMember does not exist
16101 Unknown error while accessing zone related data
16102 Unknown interop mode
16103 Zone transaction does not exist
16104 Not a owner of zone transaction
16105 Password encryption error
16106 Zoning session authentication error
16107 Unable to get client interface connected to server
16108 Zoning transaction already exist

53-1004153-01

16109 Zoning transaction commit error

16110 Invalid zoning object or empty zoning object
16111 Save zone database to switch is failed
16112 Save imported zone database to switch is failed
16113 Zoning object already exist
16114 Zoning object parent does not exist
16115 Operation not supported within zone transaction
16116 Online zone database is empty
16117 Zone alias creation operation is not supported by the current
fabric mode
16118 Zonecontrol transaction start error
16119 Zonecontrol transaction abort error
16120 ZoneSet activation failed
16121 ZoneSet de-activation failed
16122 Clearzonedb operation failed
16123 Unable to retrieve zone database
16124 SanZone online member not exist
16125 Invalid backbone fabric
16126 SANZone activation failed
16301 Database error while accessing zoning object
16501 Job does not exist
16502 Cannot delete running job
16503 Job running on fabric
17001 Device port not found
17101 Unknown error while accessing device port data
17301 Database error while accessing device port objects
18101 Unknown error while accessing AG device
18102 Unknown error while getting AG Port statistics
18103 Unknown error while getting AG Port Rate statistics
18301 Database error while accessing AG objects
19001 Failed to set virtual FCoE port state
19002 Failed to set CEE port state
19003 Failed to set CEE port interface mode
19004 Failed to set CEE port Layer 2 mode
19005 Failed to get destination
19006 Failed to get Layer 2 ACL policies

53-1004153-01

19007 Failed to get CEE port interface

19008 Failed to get CEE LAG interface
19009 Failed to create CEE ACL policy
19010 Failed to delete CEE ACL policy
19011 Failed to modify CEE ACL policy
19012 Failed to assign CEE ACL policy
19013 Failed to get LAGs
19014 Failed to get VLANs
19015 Failed to get core switch
19016 Failed to set CEE LAG interface mode
19017 Failed to set CEE LAG Layer 2 mode
19018 Failed to create LAG
19019 Failed to delete LAG
19020 Failed to add members to LAG
19021 Failed to remove members from LAG
19022 Failed to create VLAN
19023 Failed to delete VLAN
19024 Failed to update members to VLAN
19025 Failed to get FCoE port statistics
19026 Gigabit Ethernet port information not found
19027 LAG not found
19028 Failed to get CEE maps
19029 Failed to modify CEE map
19030 Failed to assign CEE map
19031 Failed to get job result
19032 Failed to create CEE map
19033 Failed to delete CEE map
19034 CEE port not found
19035 VLAN not found
19036 Failed to set CEE port IP address
19037 Failed to set LAG IP address
19038 Operation not supported on internal port
19039 CEE port not in Layer 2 mode
19040 LAG not in Layer 2 mode
19041 Failed to set VLAN FCoE enabled state
19042 Failed to set lldpdcbx enabled state

53-1004153-01

19043 Failed to get CEE switch

19044 Operation not supported in Layer 3 mode
19045 Failed to set LAG state
19046 Failed to save running config to startup config
20001 FCR switch not found
20101 FCR unknown error
20102 FCR phantom ports unknown error
20103 FCR switch invalid credential
20301 FCR database error
20302 FCR phantom ports database error
20401 FCR CAL connection error
20402 FCR CAL error
20403 FCR CAL connect error
21101 FDMI port statistics error
21102 FDMI unknown error
21301 FDMI database error
22001 LIC service error
22101 Unknown error
22301 Launch in context error
23101 FRU unknown error
23301 FRU database error
32770 Transaction not started
32772 Transaction already started
32773 Cannot commit empty objects
32775 Too many members
32782 Save zone database to switch failed
32783 Save zone database information failed
32788 Zone database error
32789 Transaction start failed
32790 Transaction end failed
32791 Transaction termination failure
40001 Authentication update failed
40002 SNMP update failed
60001 Fabric monitor operation failed
60002 AD exists error
60003 Discovery DNS error

53-1004153-01

60004 Switch in other fabric error

60005 Fabric does not exist error
60006 Switch does not exist error
60007 Duplicate fabric name error
60008 Seed switch does not exist error
60009 General authentication error
60010 Invalid SNMP credentials error
60011 Switch IP does not match with WWN
60012 Invalid IP address
60013 Session limit reached error
60014 Discovery fabric is unstable
60015 Error due to SNMP survey failure
60016 Unsupported vendor
60017 Invalid credentials error
60018 Error due to switch initialization
60019 Error due to switch link disabled
60020 Switch is not available, trap registration error
60021 Error due to switch product deletion
60022 Error due to SSL switch failure
60023 Switch timeout error
60024 Error due to too many switch sessions
60025 Switch trap registration failure error
60026 Switch trap registration lost error
60027 Connection lost error
60028 Link never connected error
60029 Connection timeout error
60030 Request failed
60031 Switch invalid network address
60032 Switch invalid product type
60033 Switch protocol error
60034 Switch unmanageable due to unknown firmware
60035 HTTP error
60036 The limit of the fabric count is reached
60037 Unsupported switch mode
60038 Unsupported firmware version
60039 FCOE not supported

53-1004153-01

60041 Unknown error

60042 Unsupported edition
60043 Seed switch firmware is not correct
60044 No discovery support for mixed model fabric
60045 No chassis access for discovery
60046 Insufficient discovery privileges
60047 Virtual Fabric discovery list is not visible
60048 Discovery invalid SNMP version
60050 Account locked error
60051 Account disabled error
60052 SNMP survey failed
60053 Mixed fabric discovery
60054 Switch unmanageable
60055 Seed switch is not supported
60056 Unknown error
60057 HTTP moved
60058 Fabric unstable error
60059 General authentication failure
60060 General input and output failure
60061 Web tools license error
60062 Insufficient AD privilege
60063 Insufficient all AD privilege
60064 No chassis access
60065 Insufficient privilege
60066 Virtual Fabric list is not visible
60067 Invalid SNMP version
60068 AD detected
60069 HTTP unavailable
60071 Connection failure
60072 Password expired error
60074 Certificate validation failure
60075 Discovery insufficient privilege
60076 Virtual Fabric discovery list is not visible
60077 Discovery invalid SNMP version

53-1004153-01


60080 Unknown error
60081 Discovery failed
60082 Switch initializing
60083 Switch is not available for trap registrations
60084 Discovery redundant
60085 Seed switch is not available in a fabric
60086 Duplicate fabric name
60087 Switch product deleted
60088 Discovery malformed URL
60089 Discovery internal error
60090 Seed switch discovery authentication failure
60091 Discovery password decryption failure
60092 Seed switch HTTP is not correct
60093 Seed switch HTTPS is not correct
60094 FCS policy is enabled on the fabric and the specified seed
switch is not primary.
60095 Switch protocol mismatch
60096 Seed switch host name verification failure
60097 Discovery AD detected
60098 Fabric name exists
60099 Switch timeout
60100 M-model switch is undiscovered
60101 Discovery invalid firmware
60102 Switch too many sessions
60103 Discovery no chassis access
60104 Switch trap registration failed
60105 Switch trap registration is lost
60106 Link is never connected
60107 Connection lost
60108 Switch link disabled
60109 Not capable
60110 Mixed fabric discovery
60111 Discovery failed for mixed fabric with I10K Virtual Switch
60112 Unsupported EOS firmware version

53-1004153-01

60113 Switch unmanageable

60114 SNMP survey failed
60115 Seed switch is not supported
60116 Partially discovered
60117 Insufficient VF_PRIVILEGE
60118 M model not supported
70001 Request add pending
70002 Request edit pending
70003 Request delete pending
70004 Request internal error
70005 JSON connection failed
70006 JSON authentication failed
70007 JSON unknown failed
70008 JSON option is OFF
70009 Redundant status
70010 Virtual machine status authentication failed
70011 Virtual machine status is timeout
70012 Virtual status no hypervisor
70013 Virtual machine status failed
70014 Discovery service is off
70015 Virtual machine status is pending
70016 Manual enclosure found status
70017 No adapter is found
70018 Output failure request pending
70019 Illegal argument
99010 Opaque key value is not found
99011 WWN format is wrong

53-1004153-01

53-1004153-01

Networkadvisor 1400 Smia Devguide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Networkadvisor 1400 Smia Devguide

Uploaded by

Copyright:

Available Formats

53-1004153-01

Brocade Network Advisor

Supporting Network Advisor 14.0.0

Brocade Communications Systems, Incorporated

Title Publication number Summary of changes Date

About This Document

Chapter 1 Connecting to the Fabric

Chapter 2 Managed Object Format Files

Brocade Network Advisor SMI Agent Developers Guide v

vi Brocade Network Advisor SMI Agent Developers Guide

Appendix A Brocade Network Advisor SMI Agent Error Codes

Brocade Network Advisor SMI Agent Developers Guide vii

How this document is organized

Brocade Network Advisor SMI Agent Developers Guide ix

x Brocade Network Advisor SMI Agent Developers Guide

Whats new in this document

Brocade Network Advisor SMI Agent Developers Guide xi

Notes, cautions, and warnings

xii Brocade Network Advisor SMI Agent Developers Guide

Notice to the reader

Corporation Referenced trademarks and products

Microsoft Corporation Windows, Windows NT, Internet Explorer

Other industry resources

Brocade Network Advisor SMI Agent Developers Guide xiii

Getting technical help

3. World Wide Name (WWN)

Brocade Network Advisor SMI Agent support

xiv Brocade Network Advisor SMI Agent Developers Guide

Brocade Network Advisor SMI Agent Developers Guide xv

Connecting to the Fabric 1

Role-Based Access Control

Brocade Network Advisor SMI Agent Developers Guide 1

Admin Domains and Brocade Network Advisor SMI Agent

Connecting to the Brocade Network Advisor SMI Agent

Connecting the Brocade Network Advisor SMI Agent

CIMNameSpace objCIMNameSpace = new CIMNameSpace(strCIMOMIP, strNameSpace);

Connecting the Brocade Network Advisor SMI Agent

2 Brocade Network Advisor SMI Agent Developers Guide

Discovering a fabric and a host

Fabric discovery using SMIA extrinsic method

Brocade Network Advisor SMI Agent Developers Guide 3

FIGURE 1 Fabric discovery data model

Host discovery using SMIA extrinsic method

4 Brocade Network Advisor SMI Agent Developers Guide

FIGURE 2 Host discovery data model

Discovery using SMIA Configuration Tool

Brocade Network Advisor SMI Agent Developers Guide 5

FIGURE 3 Fabric discovery using SMIA Configuration Tool

6 Brocade Network Advisor SMI Agent Developers Guide

FIGURE 4 Host discovery using SMIA Configuration Tool

Brocade Network Advisor SMI Agent Developers Guide 7

8 Brocade Network Advisor SMI Agent Developers Guide

Managed Object Format Files 2

Brocade Managed Object Format files

BrocadeAccessGateway.mof Access Gateway

Brocade Network Advisor SMI Agent Developers Guide 9

TABLE 1 Brocade Managed Object Format files (Continued)

BrocadeLaunchInContext.mof Launch In Context profile

Additional MOF description specifications

Creating and deleting instances

10 Brocade Network Advisor SMI Agent Developers Guide

Brocade Network Advisor SMI Agent Developers Guide 11

12 Brocade Network Advisor SMI Agent Developers Guide

Profiles and Subprofiles 3