53-1002701-0114 December 2012

Brocade Network Advisor SMI AgentDevelopers Guide

Supporting Brocade Network Advisor SMI Agent 12.0.0

Copyright 2010 - 2012 Brocade Communications Systems, Inc. All Rights Reserved.

Brocade, Brocade Assurance, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, MLX, NetIron, SAN Health, ServerIron, TurboIron, VCS, and VDX are registered trademarks, and AnyIO, Brocade One, CloudPlex, Effortless Networking, ICX, NET Health, OpenScript, and The Effortless Network are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names mentioned may be trademarks of their respective owners.

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

The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that accompany it.

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

Brocade Communications Systems, Incorporated

Document History

Corporate and Latin American HeadquartersBrocade Communications Systems, Inc.130 Holger Way,San Jose, CA 95134Tel: 1-408-333-8000 Fax: 1-408-333-8101 E-mail: info@brocade.com

Asia-Pacific HeadquartersBrocade Communications Systems China HK, Ltd.No. 1 Guanghua RoadChao Yang DistrictUnits 2718 and 2818Beijing 100020, ChinaTel: +8610 6588 8888Fax: +8610 6588 9999E-mail: china-info@brocade.com

European HeadquartersBrocade Communications Switzerland SrlCentre SwissairTour B - 4me tage29, Route de l'AroportCase Postale 105CH-1215 Genve 15Switzerland Tel: +41 22 799 5640Fax: +41 22 799 5641E-mail: emea-info@brocade.com

Asia-Pacific HeadquartersBrocade Communications Systems Co., Ltd. (Shenzhen WFOE)Citic PlazaNo. 233 Tian He Road NorthUnit 1308 13th FloorGuangzhou, ChinaTel: +8620 3891 2000Fax: +8620 3891 2111E-mail: china-info@brocade.com

Title Publication number Summary of changes Date

DCFM SMI Agent Developers Guide 53-1001361-01 New document March 2010

Brocade Network Advisor SMI Agent Developers Guide

53-1002169-01 Updated to support DCX and DCX-4S switches. Updated profiles and subprofiles to conform to SMI-S 1.5.

May 2011

Brocade Network Advisor SMI Agent Developers Guide

53-1002534-01 Updated to support Brocade 6505 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.

March 2012

Brocade Network Advisor SMI Agent Developers Guide

53-1001701-01 Updated to support Brocade 5430, 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.

December 2012

Title Publication number Summary of changes DateBrocade Network Advisor SMI Agent Developers Guide iii53-1002701-01

iv Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Brocade Managed Object Format files . . . . . . . . . . . . . . . . . . . . . . . . 9

Additional MOF description specifications . . . . . . . . . . . . . . . . . . . . 10Creating and deleting instances . . . . . . . . . . . . . . . . . . . . . . . . . 10Deprecation qualifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Contents

About This Document

How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Supported hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Whats new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiText formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiNotes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . xiiKey terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiBrocade resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiOther industry resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Brocade Network Advisor SMI Agent support . . . . . . . . . . . . . . . . . . xiv

Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

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. . . . . . . . . . . 2Connecting the Brocade Network Advisor SMI Agent when security is enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Connecting the Brocade Network Advisor SMI Agent when security is not enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Discovering a fabric and a host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Fabric discovery using SMIA extrinsic method. . . . . . . . . . . . . . . 3Host discovery using SMIA extrinsic method . . . . . . . . . . . . . . . . 4Discovery using SMIA Configuration Tool . . . . . . . . . . . . . . . . . . . 5

Chapter 2 Managed Object Format FilesBrocade Network Advisor SMI Agent Developers Guide v53-1002701-01

Chapter 3 Profiles and Subprofiles

UML diagram conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

SMI profiles and subprofiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Other features supported by Brocade Network Advisor SMI Agent . . . . . . . . . . . . . . . . . . . . .15

Server profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Indications subprofile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Object manager adapter subprofile . . . . . . . . . . . . . . . . . . . . . . 17

Fabric profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Rules governing Brocade_SAN.Name. . . . . . . . . . . . . . . . . . . . . 17Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Zone control and enhanced zone control subprofiles . . . . . . . .22Job control profile for SessionControlWithJob and ActivateZoneSetWithJob . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Zoning behavior details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26SAN zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Fabric virtual fabrics subprofile . . . . . . . . . . . . . . . . . . . . . . . . .33Sample discovery configuration . . . . . . . . . . . . . . . . . . . . . . . . .34Blades subprofile support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Topology view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37FDMI subprofile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Switch profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Physical package, access points, software, blades, and location subprofiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

CP blades (Brocade extension) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Supported classes and associations . . . . . . . . . . . . . . . . . . . . .50

FC HBA profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Launch In Context profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52LIC names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52Registration and data model. . . . . . . . . . . . . . . . . . . . . . . . . . . .54vi Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

CEE switch support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Topology supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Zoning support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61LAGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66CEE ACLs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69CEE maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Brocade 8470 FCoE embedded switch support . . . . . . . . . . . . 74Support for Layer 3 features . . . . . . . . . . . . . . . . . . . . . . . . . . . .75Brocade 8428 FCoE embedded switch support . . . . . . . . . . . . 77

Fabric switch partitioning subprofile . . . . . . . . . . . . . . . . . . . . . . . . . 77Data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

FC routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78Data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Edge-to-edge device sharing (no FCIP configured in backbone). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Backbone-to-edge device sharing (no FCIP configuredin backbone). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83Backbone-to-edge device sharing (using VEX_Port over FCIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Brocade Access Gateway and NPIV . . . . . . . . . . . . . . . . . . . . . . . . . .89Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89Data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90Access Gateway Physical Package . . . . . . . . . . . . . . . . . . . . . . .92Access Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

FRU profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101Data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103Data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Chapter 4 Indications

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Alert indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Life-cycle indications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145

Appendix A Brocade Network Advisor SMI Agent Error CodesBrocade Network Advisor SMI Agent Developers Guide vii53-1002701-01

viii Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Brocade Communications Systems, Inc. for Brocade Network Advisor SMI Agent 12.0.0, documenting all possible configurations and scenarios is beyond the scope of this document. About This Document

In this chapterHow this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixSupported hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xWhats new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiDocument conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiNotice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiAdditional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiGetting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiBrocade Network Advisor SMI Agent support . . . . . . . . . . . . . . . . . . . . . . . . xivDocument feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

How this document is organizedThis 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 Network Advisor SMI Agent Developers Guide ix53-1002701-01

Supported hardwareThe following switches are supported by Brocade Network Advisor SMI Agent 12.0.0:

Brocade 300 Brocade 5100 Brocade 5300 Brocade 5410 Brocade 5424 Brocade 5430 Brocade 5450 Brocade 5460 Brocade 5470 Brocade 5480 Brocade 6505 Brocade 6510 Brocade 6520 Brocade VA-40 FC Brocade 7800 Extension Switch Brocade 8000 FCoE Switch Brocade Encryption Switch Brocade DCX Brocade DCX-4S Brocade DCX 8510-8 Backbone (8-slot) Brocade DCX 8510-4 Backbone (4-slot)The following blades are supported on the Brocade DCX and DCX-4S switches:

FC8-16 port blade FC8-32 port blade FC8-48 port blade FC8-64 port blade FCOE10-24 DCX Blade FS8-18 Encryption Blade FX8-24 DCX Extension BladeThe 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 FC8-64 port blade FC16-32 port bladex Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

FC16-48 port blade FS8-18 Encryption Blade FX8-24 DCX Extension Blade

Whats new in this documentThe following changes have been made since this document was last released:

Information that is added:- Support for Brocade 5430, Brocade 5431, Brocade M6505, and Brocade 6520. (Refer to

Supported hardware on page x.)

- Support for Physical Package is provided for Access Gateways. (Refer to Access Gateway Physical Package on page 92.)

Information that is changed:- Implemented the Role property to the Brocade_Node CIM class and the SwitchId property

in the Brocade_Switch class in the Fabric profile data model. (Refer to Figure 9 on page 20.)

- Modelled the port statistics and the port rate statistic information for the AGFCPorts. (Refer to Figure 44 on page 90.)

- Made enhancements to the Brocade_SAN.ElementName class. (Refer to Brocade_SAN.ElementName properties on page 21.)

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

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

Text formattingThe narrative-text formatting conventions that are used in this document are as follows:

bold text Identifies command namesIdentifies the names of user-manipulated GUI elementsIdentifies keywordIdentifies text to enter at the GUI or CLI

italic text Provides emphasisIdentifies variablesIdentifies paths and Internet addressesIdentifies document titles

code text Identifies CLI outputIdentifies command syntax examplesBrocade Network Advisor SMI Agent Developers Guide xi53-1002701-01

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

Notes, cautions, and warningsThe following notices and statements are used in this manual. They are listed below in order of increasing severity of potential hazards.

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

ATTENTIONAn Attention statement indicates potential damage to hardware or data.

Key termsFor 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 readerThis 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.

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

Corporation Referenced trademarks and products

Microsoft Corporation Windows, Windows NT, Internet Explorer

Red Hat, Inc. Red Hat, Red Hat Network, Maximum RPM, Linux Undercoverxii Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Brocade resourcesTo 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 resourcesFor additional resource information, visit the Technical Committee T11 website. This website provides interface standards for high-performance and mass storage applications for Fibre Channel, storage management, and other applications:

http://www.t11.org

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

http://www.fibrechannel.org

Getting technical helpContact 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 NumberBrocade Network Advisor SMI Agent Developers Guide xiii53-1002701-01

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

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

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 feedbackQuality is our first concern at Brocade and we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. 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.

*FT00X0054E9*

FT00X0054E9xiv Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Brocade Network Advisor SMI Agent Developers Guide53-1002701-01 getclass 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 theoperations 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.Chapter

1Connecting to the Fabric

In this chapterRole-Based Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Admin Domains and Brocade Network Advisor SMI Agent. . . . . . . . . . . . . . . 2Connecting to the Brocade Network Advisor SMI Agent . . . . . . . . . . . . . . . . . 2Discovering a fabric and a host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Role-Based Access ControlRole-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 1

Admin Domains and Brocade Network Advisor SMI Agent1Admin Domains and Brocade Network Advisor SMI AgentThe 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 AgentThis section describes how to connect to the Brocade Network Advisor SMI Agent when security is enabled and when security is not enabled.

Connecting the Brocade Network Advisor SMI Agent when security is enabledConnect 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);

Connecting the Brocade Network Advisor SMI Agent when security is not enabledYou 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 Guide53-1002701-01

Discovering a fabric and a host 1Discovering a fabric and a hostYou 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 methodThe 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 supportedThe 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.

LimitationsThe 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.Brocade Network Advisor SMI Agent Developers Guide 353-1002701-01

Discovering a fabric and a host1FIGURE 1 Fabric discovery data model

Host discovery using SMIA extrinsic methodThe CIMOM host discovery process enables the user to discover and delete hosts through an extrinsic method implemented in the Brocade_DiscoveryService.

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

LimitationsThe 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.4 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Discovering a fabric and a host 1Data 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 ToolThe 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.Brocade Network Advisor SMI Agent Developers Guide 553-1002701-01

Discovering a fabric and a host1FIGURE 3 Fabric discovery using SMIA Configuration Tool

Figure 4 shows the host discovery through the SMIA Configuration Tool.6 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Discovering a fabric and a host 1F

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.Brocade Network Advisor SMI Agent Developers Guide 753-1002701-01

Discovering a fabric and a host18 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Brocade Network Advisor SMI Agent Developers Guide53-1002701-01BrocadeFDMI.mof FDMI subprofile

BrocadeFRU.mof Fan, Power Supply, Sensors profiles

BrocadeIndications.mof Indications

BrocadeJobControl.mof JobControl subprofile

BrocadeLAG.mof LAG discovery and configurationChapter

2Managed Object Format Files

In this chapterBrocade Managed Object Format files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Additional MOF description specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Brocade Managed Object Format filesBrocade 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 filesMOF 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 profile9

Additional MOF description specifications2NOTEThe 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 specificationsThe 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 instancesIf 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

BrocadeLaunchInContext.mof Launch In Context profile

BrocadePartitioning.mof FabricVirtualFabrics subprofileFCR subprofile

BrocadePhysicalPackage.mof Location subprofilePhysical 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

TABLE 1 Brocade Managed Object Format files (Continued)MOF filename Description10 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Additional MOF description specifications 2For 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 qualifierInstance 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.Brocade Network Advisor SMI Agent Developers Guide 1153-1002701-01

Additional MOF description specifications212 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Brocade Network Advisor SMI Agent Developers Guide53-1002701-01FIGURE 5 UML diagram conventionChapter

3Profiles and Subprofiles

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

UML diagram conventionsThis 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.13

SMI profiles and subprofiles3SMI profiles and subprofilesTable 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 subprofilesProfile 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 Sensor

Fan Profile 1.0.0

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 Node Port Initialized Virtualization (NPIV)

N_Port Virtualizer Profile 1.5

Physical Package 1.514 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Server profile 3Other features supported by Brocade Network Advisor SMI AgentThe 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.

NOTEThe 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.Brocade Network Advisor SMI Agent Developers Guide 1553-1002701-01

Server profile3

FIGURE 6 Server profile

Indications subprofileThe Indications subprofile is supported by the WBEM Solutions J WBEM Server CIMOM as shown in Figure 7.16 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Fabric profile 3FIGURE 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.NameThe 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 Brocade Network Advisor SMI Agent Developers Guide 1753-1002701-01

been discovered, Brocade_SAN.Name is the principal WWN of the base fabric.

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

RegistrationFigure 8 shows the SNIA profile registration profile model to advertise the Fabric profile and its subprofiles.18 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Fabric profile 3FIGURE 8 Fabric profile registration

Data modelFigure 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.Brocade Network Advisor SMI Agent Developers Guide 1953-1002701-01

Fabric profile3FIGURE 9 Fabric profile20 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Fabric profile 3NOTEThe 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"}

NOTEThe SwitchId property will be populated only for switches running FOS 7.1.0 onwards.

Brocade_SAN.ElementName propertiesThe 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,the 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.

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

LimitationsThe 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 Brocade Network Advisor SMI Agent Developers Guide 2153-1002701-01

SAN ElementName is reset to the configured name.

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

RegistrationRefer to Registration on page 18.

Data modelFigure 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.22 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Fabric profile 3FIGURE 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 subprofileElementName Description Currently

supported Y/N?

CIM_HostedService Associates the ZoneService to the Admin Domain representing the fabric.

Yes

CIM_ZoneService The service that allows for all of the zoningconfiguration changes.

YesBrocade Network Advisor SMI Agent Developers Guide 2353-1002701-01

Fabric profile3Extrinsic methodsThe 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. 24 Brocade Network Advisor SMI Agent Developers Guide53-1002701-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{} notation for a

fabric member is not supported in the SMI Agent.

Job control profile for SessionControlWithJob and ActivateZoneSetWithJobDuring 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.Brocade Network Advisor SMI Agent Developers Guide 2553-1002701-01

Fabric profile3Data modelFigure 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.26 Brocade Network Advisor SMI Agent Developers Guide53-1002701-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 indicationsTable 4 shows all the supported mandatory indications.

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

TABLE 4 Supported indicationsIndication Description

SELECT * FROM CIM_InstModification WHERE SourceInstance ISA CIM_ConcreteJob AND SourceInstance.CIM_ConcreteJob::PercentComplete PreviousInstance.CIM_ConcreteJob::Percent Complete

Modification of PercentComplete for a concrete job.

SELECT * FROM CIM_InstModification WHERE SourceInstance ISA CIM_ConcreteJob AND ANY SourceInstance.CIM_ConcreteJob::Operation alStatus[*] = 17 AND ANY SourceInstance.CIM_ConcreteJob::Operation alStatus[*] = 2

Modification of OperationalStatus for aconcrete job to Complete and OK.

SELECT * FROM CIM_InstModification WHERE SourceInstance ISA CIM_ConcreteJob AND ANY SourceInstance.CIM_ConcreteJob::Operation alStatus[*] = 17 AND ANY SourceInstance.CIM_ConcreteJob::Operation alStatus[*] = 6

Modification of OperationalStatus for aconcrete job to Complete and Error.

SELECT * FROM CIM_InstModification WHERE SourceInstance ISA CIM_ConcreteJob AND SourceInstance.CIM_ConcreteJob::JobState PreviousInstance.CIM_ConcreteJob::JobState

Modification of JobState for a concrete job.

SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_ConcreteJob

Creation of a concrete job.Brocade Network Advisor SMI Agent Developers Guide 2753-1002701-01

Fabric profile3LSAN zoning configuration guidelinesThe 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 AdvisorThe 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.

RegistrationThere is no profile registration for this model.

Data model Figure 12 shows the data model of SAN zoning.28 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Fabric profile 3FIGURE 12 SAN zoning data model

SAN zoning operation behaviorThe 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 Brocade Network Advisor SMI Agent Developers Guide 2953-1002701-01

InstanceID, ZoneNameMaxLen, ZoneNameFormat, and SupportedConnectivityMemberTypes.

Fabric profile3 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_ is created and the respective SAN zone is added 30 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

under this zone set.

Fabric profile 3NOTEThe name of SAN zone must start with LSAN_. Otherwise, the extrinsic call returns an error code: 5 (CIM_ERR_INVALID_PARAMETER). Invalid SANZone name: .

Alert indication supportThe 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 casesFigure 13 explains a sample SAN configuration.

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

E

Host

Target 1 Target 3Target 2

Fabric 1 Fabric 2 Fabric 4Fabric 3

FC router 1 FC router 2

Backbone fabric

FC router 3 FC router 4

EX EX EXEX EX

EXEX

EEEE

EEBrocade Network Advisor SMI Agent Developers Guide 3153-1002701-01

Fabric profile3 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: Activate the SAN zoning session with SANSessionControl (RequestedSessionState=2). Remove zone members with RemoveSANZoneMembers

(SANZoneName=LSAN_Zone1, ZoneMembers={Target 1 WWN}). Commit the SAN zoning session with SANSessionControl (RequestedSessionState=3).

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: Activate the SAN zoning session with SANSessionControl (RequestedSessionState=2). Delete a zone with DeleteSANZone (SANZoneName=LSAN_Zone1). Commit the SAN zoning session with SANSessionControl (RequestedSessionState=3).

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).: 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.32 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Fabric profile 3Fabric 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.

RegistrationEach 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 modelFigure 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.Brocade Network Advisor SMI Agent Developers Guide 3353-1002701-01

Fabric profile3FIGURE 14 Fabric virtual fabrics subprofile data model

Sample discovery configurationFigure 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.34 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Fabric profile 3FIGURE 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- 3 logical switches in Chassis 2- 3 logical switches in Chassis 3- 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 switchesBrocade Network Advisor SMI Agent Developers Guide 3553-1002701-01

Fabric profile3 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 supportThe 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 diagram36 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Fabric profile 3Topology viewThe 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.

ObjectivesThe 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 considerationsPerformance 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 modelBrocade Network Advisor SMI Agent Developers Guide 3753-1002701-01

Fabric profile3Data modelFigure 18 shows the data model of Topology view.

FIGURE 18 Topology view data model

FDMI subprofileThe 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.38 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Fabric profile 3PrerequisitesOnly 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.

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

RegistrationRefer to Registration on page 18.

Data modelFigure 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.Brocade Network Advisor SMI Agent Developers Guide 3953-1002701-01

Fabric profile3FIGURE 19 FDMI data model40 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Fabric profile 3TrunkingThis section defines the model for the trunking feature in Brocade Network Advisor SMI Agent. The trunking model is supported only for FOS switches.

NOTEThe 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 modelFigure 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. Brocade Network Advisor SMI Agent Developers Guide 4153-1002701-01

Fabric profile3Related API and classesTable 5 represents the group of switch ports forming a trunk.

Table 6 explains the properties of Brocade_TrunkInSwitch: CIM_HostedCollection class.

Table 7 explains the properties of Brocade_SwitchFCPortInTrunk: CIM_MemberOfCollection class.

TABLE 5 Brocade_Trunk: CIM_RedundancySetProperty 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=;SOURCESWITCHTYPE=:DESTINATIONWWN=;SOURCESWITCHPORTWWN=;DESTPORTWWN=;CLASSNAME=Brocade_Trunk;DESTINATIONTYPE=;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 Brocade_TrunkInSwitch: CIM_HostedCollectionProperty name Type Description

Antecedent Brocade_Switch REF Represents the switch objects that has the trunk.

Dependent Brocade_Trunk REF Represents the trunk object.

TABLE 7 Brocade_SwitchFCPortInTrunk: CIM_MemberOfCollectionProperty name Type Description

Collection Brocade_Trunk REF Represents the trunk object.

Member Brocade_SwitchFCPort REF Represents the member of the trunk.42 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Switch profile 3Table 8 explains the properties of Brocade_AGFCPortInTrunk: CIM_ MemberOfCollection class.

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.

RegistrationThe 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

TABLE 8 Brocade_AGFCPortInTrunk: CIM_ MemberOfCollectionProperty name Type Description

Collection Brocade_Trunk REF Represents the trunk object.

Member Brocade_AGFCPort REF Represents the member of the trunk.Brocade Network Advisor SMI Agent Developers Guide 4353-1002701-01

Switch profile3Data modelFigure 22 shows the Switch profile data model.

FIGURE 22 Switch profile data model

NOTEThe 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.44 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Switch profile 3NOTESwitch un-monitoring is not supported from SMI perspective and if the switch is unmonitored, then the SMI Agent would return stale information.

Differentiation between switches and domainsThe 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.

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.

TABLE 9 PortDiscriminator valuesNo Port PortDiscriminator value

1 FC ports on the FCIP Ethernet port FCIP

2 Virtual FCoE ports inside the Elara internal + FCoE

3 Virtualized node ports in NPIV and Access Gateway NPIV

4 Front and xlate phantom FC ports (except the FF port from the backbone)

IFR virtual

5 Front phantom FC port from the backbone connected to the edge switch

IFR

6 ICL ports Chassis

7 Dynamically created FC ports for logical connections in virtual fabrics

VF

8 All other FC ports (like physical ports) Not Applicable

9 CU ports of Blade Switches InternalBrocade Network Advisor SMI Agent Developers Guide 4553-1002701-01

Switch profile3RegistrationRefer to Registration on page 43.

Data modelFigure 23 shows the data model with the classes and properties that are supported to conform to the switch subprofiles.

TABLE 10 Switch subprofilesSubprofiles Description

Physical Package Models information about a storage system's physical package and optionally about internal subpackages.

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.46 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

Switch profile 3FIGURE 23 Physical Package, Access Points, Software, Blades, and Location subprofiles data modelBrocade Network Advisor SMI Agent Developers Guide 4753-1002701-01

CP blades (Brocade extension)3NOTEhe 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 modelFigure 24 shows the instance diagram of the CP blades.48 Brocade Network Advisor SMI Agent Developers Guide53-1002701-01

CP blades (Brocade extension) 3FIGURE 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, Brocade Network Advisor SMI Agent Developers Guide 4953-1002701-01

standby, or failed.

FC HBA profile3 The Brocade_CPModule.ModuleNumber shows the slot number of the CP blade. The Brocade_CPModule is associated to the Brocade_PhysicalComputerSystem using

Broca