Brocade Network Advisor SMI Agent Developer's Guide, 14.4

Supporting Brocade Network Advisor 14.4.2

CONFIGURATION GUIDE

Brocade Network Advisor SMI AgentDeveloper's Guide, 14.4.2

53-1005408-0106 April 2018

Copyright © 2018 Brocade Communications Systems LLC. All Rights Reserved. Brocade and the stylized B logo are among the trademarks of BrocadeCommunications Systems LLC. Broadcom, the pulse logo, and Connecting everything are among the trademarks of Broadcom. The term "Broadcom"refers to Broadcom Inc. and/or its subsidiaries.

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

The product described by this document may contain open source software covered by the GNU General Public License or other open source licenseagreements. To find out which open source software is included in Brocade products, view the licensing terms applicable to the open source software, andobtain a copy of the programming source code, please visit http://www.broadcom.com/support/fibre-channel-networking/tools/oscd.

Brocade Network Advisor SMI Agent Developer's Guide, 14.4.22 53-1005408-01

http://www.broadcom.com/support/fibre-channel-networking/tools/oscd

ContentsAbout This Document........................................................................................................................................................................................................ 7

Supported hardware and software...................................................................................................................................................................................................... 7Fabric OS hardware and software support.............................................................................................................................................................................7HBA hardware and software support.................................................................................................................................................................................... 10IronWare OS hardware and software support....................................................................................................................................................................11Network OS hardware and software support.....................................................................................................................................................................15

Getting technical help............................................................................................................................................................................................................................16What's new in this document............................................................................................................................................................................................................. 17Document conventions.........................................................................................................................................................................................................................17

Notes, cautions, and warnings..................................................................................................................................................................................................17Text formatting conventions......................................................................................................................................................................................................18Command syntax conventions.................................................................................................................................................................................................18

Document feedback.............................................................................................................................................................................................................................. 19

Connecting to the Fabric.................................................................................................................................................................................................21Role-Based Access Control............................................................................................................................................................................................................... 21Admin Domains and the Brocade Network Advisor SMI Agent.........................................................................................................................................21Connecting to the Management application SMI Agent.........................................................................................................................................................22

Connecting to the Management application SMI Agent when security is enabled............................................................................................22Connecting to the Management application SMI Agent when security is not enabled....................................................................................22

Discovering a fabric and a host.........................................................................................................................................................................................................22Fabric discovery using the SMIA extrinsic method......................................................................................................................................................... 23Host discovery using the SMIA extrinsic method............................................................................................................................................................24Discovery using SMIA Configuration Tool.......................................................................................................................................................................... 25

Managed Object Format Files....................................................................................................................................................................................... 29Brocade Managed Object Format files..........................................................................................................................................................................................29Additional MOF description specifications.................................................................................................................................................................................. 30

Creating and deleting instances...............................................................................................................................................................................................30Deprecation qualifier.....................................................................................................................................................................................................................30

Profiles and Subprofiles..................................................................................................................................................................................................31UML diagram conventions................................................................................................................................................................................................................. 31SMI profiles and subprofiles...............................................................................................................................................................................................................31

Other features supported by the Management application SMI Agent..................................................................................................................32Server profile.............................................................................................................................................................................................................................................33

Indications subprofile................................................................................................................................................................................................................... 34Object manager adapter subprofile....................................................................................................................................................................................... 35

Fabric profile..............................................................................................................................................................................................................................................35Rules governing Brocade_SAN.Name................................................................................................................................................................................. 35Registration.......................................................................................................................................................................................................................................36Data model.......................................................................................................................................................................................................................................37Zone control and enhanced zone control subprofiles.................................................................................................................................................... 40Job control profile for SessionControlWithJob and ActivateZoneSetWithJob..................................................................................................... 43Zoning behavior details...............................................................................................................................................................................................................44SAN zoning...................................................................................................................................................................................................................................... 45Fabric virtual fabrics subprofile................................................................................................................................................................................................ 50Sample discovery configuration.............................................................................................................................................................................................. 52

Brocade Network Advisor SMI Agent Developer's Guide, 14.4.253-1005408-01 3

Blades subprofile support..........................................................................................................................................................................................................54Topology view................................................................................................................................................................................................................................. 55FDMI subprofile..............................................................................................................................................................................................................................57Trunking............................................................................................................................................................................................................................................. 60

Switch profile.............................................................................................................................................................................................................................................62Registration.......................................................................................................................................................................................................................................62Data model.......................................................................................................................................................................................................................................63Differentiation between switches and domains................................................................................................................................................................65Physical package, access points, software, blades, and location subprofiles....................................................................................................... 65

CP blades (Brocade extension)......................................................................................................................................................................................................... 68Data model.......................................................................................................................................................................................................................................68Supported classes and associations..................................................................................................................................................................................... 70

FC HBA profile.........................................................................................................................................................................................................................................70Prerequisites.................................................................................................................................................................................................................................... 70Data model.......................................................................................................................................................................................................................................70

Launch In Context profile.....................................................................................................................................................................................................................72LIC names........................................................................................................................................................................................................................................ 72Registration and data model..................................................................................................................................................................................................... 73

CEE switch support................................................................................................................................................................................................................................76Registration.......................................................................................................................................................................................................................................77Data model.......................................................................................................................................................................................................................................77Topology supported..................................................................................................................................................................................................................... 79Zoning support............................................................................................................................................................................................................................... 80Configuration................................................................................................................................................................................................................................... 80LAGs................................................................................................................................................................................................................................................... 82VLANs................................................................................................................................................................................................................................................85CEE ACLs.........................................................................................................................................................................................................................................87CEE maps.........................................................................................................................................................................................................................................90Brocade 8470 FCoE embedded switch support............................................................................................................................................................92Support for Layer 3 features.....................................................................................................................................................................................................93Brocade 8428 FCoE embedded switch support............................................................................................................................................................95

Fabric switch partitioning subprofile................................................................................................................................................................................................95Data model.......................................................................................................................................................................................................................................95Registration.......................................................................................................................................................................................................................................96

FC routing.................................................................................................................................................................................................................................................. 96Data model.......................................................................................................................................................................................................................................96Registration.......................................................................................................................................................................................................................................98Edge-to-edge device sharing (no FCIP configured in backbone).............................................................................................................................99Backbone-to-edge device sharing (no FCIP configured in backbone)............................................................................................................... 101Backbone-to-edge device sharing (using VEX_Port over FCIP)...........................................................................................................................103

Brocade Access Gateway and NPIV............................................................................................................................................................................................106Registration................................................................................................................................................................................................................................... 107Data model....................................................................................................................................................................................................................................107HBA with virtualized ports without AG..............................................................................................................................................................................109Access Gateway Physical Package.....................................................................................................................................................................................110Access Gateway.......................................................................................................................................................................................................................... 111

FRU profiles........................................................................................................................................................................................................................................... 119Registration................................................................................................................................................................................................................................... 119Data model....................................................................................................................................................................................................................................119Limitations..................................................................................................................................................................................................................................... 120


Names...................................................................................................................................................................................................................................................... 121Data model....................................................................................................................................................................................................................................121

Indications....................................................................................................................................................................................................................... 123Introduction.............................................................................................................................................................................................................................................123Alert indications.................................................................................................................................................................................................................................... 123

FC1...................................................................................................................................................................................................................................................123FC2...................................................................................................................................................................................................................................................124FC5...................................................................................................................................................................................................................................................125FC6...................................................................................................................................................................................................................................................125FC7...................................................................................................................................................................................................................................................126FC8...................................................................................................................................................................................................................................................126FC10............................................................................................................................................................................................................................................... 127Core6...............................................................................................................................................................................................................................................127Core6...............................................................................................................................................................................................................................................128Core8...............................................................................................................................................................................................................................................128Core10............................................................................................................................................................................................................................................129BRCD4........................................................................................................................................................................................................................................... 130BRCD5........................................................................................................................................................................................................................................... 130BRCD6........................................................................................................................................................................................................................................... 131BRCD7........................................................................................................................................................................................................................................... 131BRCD8........................................................................................................................................................................................................................................... 132BRCD12........................................................................................................................................................................................................................................ 133BRCD13........................................................................................................................................................................................................................................ 133BRCD16........................................................................................................................................................................................................................................ 134BRCD17........................................................................................................................................................................................................................................ 134BRCD18........................................................................................................................................................................................................................................ 135BRCD19........................................................................................................................................................................................................................................ 136BRCD20........................................................................................................................................................................................................................................ 136BRCD21........................................................................................................................................................................................................................................ 137BRCD24........................................................................................................................................................................................................................................ 137BRCD25........................................................................................................................................................................................................................................ 138BRCD26........................................................................................................................................................................................................................................ 139BRCD27........................................................................................................................................................................................................................................ 139BRCD28........................................................................................................................................................................................................................................ 140BRCD29........................................................................................................................................................................................................................................ 140BRCD30........................................................................................................................................................................................................................................ 141BRCD31........................................................................................................................................................................................................................................ 142BRCD32........................................................................................................................................................................................................................................ 142BRCD33........................................................................................................................................................................................................................................ 143BRCD35........................................................................................................................................................................................................................................ 144BRCD42........................................................................................................................................................................................................................................ 144BRCD43........................................................................................................................................................................................................................................ 145BRCD44........................................................................................................................................................................................................................................ 146BRCD46........................................................................................................................................................................................................................................ 146BRCD48........................................................................................................................................................................................................................................ 147BRCD49........................................................................................................................................................................................................................................ 147BRCD51........................................................................................................................................................................................................................................ 148BRCD52........................................................................................................................................................................................................................................ 149BRCD53........................................................................................................................................................................................................................................ 149BRCD54........................................................................................................................................................................................................................................ 150


BRCD56........................................................................................................................................................................................................................................ 150BRCD57........................................................................................................................................................................................................................................ 151BRCD58........................................................................................................................................................................................................................................ 152BRCD59........................................................................................................................................................................................................................................ 152BRCD60........................................................................................................................................................................................................................................ 153BRCD61........................................................................................................................................................................................................................................ 153BRCD62........................................................................................................................................................................................................................................ 154BRCD63........................................................................................................................................................................................................................................ 154BRCD64........................................................................................................................................................................................................................................ 155BRCD65........................................................................................................................................................................................................................................ 155BRCD66........................................................................................................................................................................................................................................ 156BRCD67........................................................................................................................................................................................................................................ 156BRCD68........................................................................................................................................................................................................................................ 157BRCD69........................................................................................................................................................................................................................................ 157BRCD70........................................................................................................................................................................................................................................ 158BRCD71........................................................................................................................................................................................................................................ 158BRCD72........................................................................................................................................................................................................................................ 159BRCD73........................................................................................................................................................................................................................................ 159BRCD74........................................................................................................................................................................................................................................ 160BRCD75........................................................................................................................................................................................................................................ 160BRCD76........................................................................................................................................................................................................................................ 161BRCD101..................................................................................................................................................................................................................................... 162BRCD102..................................................................................................................................................................................................................................... 162BRCD103..................................................................................................................................................................................................................................... 163BRCD104..................................................................................................................................................................................................................................... 163BRCD105..................................................................................................................................................................................................................................... 164BRCD106..................................................................................................................................................................................................................................... 164BRCD107..................................................................................................................................................................................................................................... 165BRCD109..................................................................................................................................................................................................................................... 165BRCD110..................................................................................................................................................................................................................................... 166BRCD111..................................................................................................................................................................................................................................... 166

Life-cycle indications..........................................................................................................................................................................................................................167

Management Application SMI Agent Error Codes................................................................................................................................................. 171

SMI Agent Certification................................................................................................................................................................................................ 179Generating the certificate..................................................................................................................................................................................................................179Importing the certificate.................................................................................................................................................................................................................... 183


About This Document• Supported hardware and software.................................................................................................................................................................7• Getting technical help.......................................................................................................................................................................................16• What's new in this document........................................................................................................................................................................17• Document conventions................................................................................................................................................................................... 17• Document feedback.........................................................................................................................................................................................19

Supported hardware and softwareWhen procedures or parts of procedures documented in this guide apply to some devices but not to others, this guide identifies exactlywhich devices are supported and which are not.

Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc. forNetwork Advisor 14.4.2, documenting all possible configurations and scenarios is beyond the scope of this guide.

Fabric OS hardware and software supportThe following firmware platforms are supported by this release of the Management application:

• Fabric OS 6.0 or later





NOTEDiscovery of a secure Fabric OS fabric in strict mode is not supported.

NOTETo ensure that a configuration is fully supported, always check the appropriate SAN, storage or blade server product supportpage to verify support of specific code levels on specific switch platforms prior to installing on your switch. Use only Fabric OSversions that are supported by the provider.

The hardware platforms in the following table are supported by this release of the Management application.

NOTEProfessional and Professional Plus (Trial and Licensed) versions of the Management application can discover, but not manage8-slot directors. These devices cannot be used as a Seed switch.

TABLE 1 Hardware supported by Fabric OS

Device name Terminology used in documentation

Brocade 300 Switch 24-port, 8-Gbps FC switch

Brocade 4012 Switch Embedded 12-port, 4- Gbps FC switch

Brocade 4016 Switch Embedded 16-port, 4-Gbps FC switch




TABLE 1 Hardware supported by Fabric OS (continued)





Brocade 5410 Embedded Switch Embedded 12-port, 8-Gbps switch


Brocade 5431 Embedded Switch Embedded 16-port, 8-Gbps stackable switch





Brocade 6505 Switch 24-port, 16-Gbps edge switch

Brocade M6505 Embedded Switch 24-port, 16-Gbps embedded switch

Brocade 6510 Switch 48-port, 16-Gbps switch

Brocade 6520 Switch 96-port, 16-Gbps switch

Brocade 6542 blade server SAN I/O module 48-port, 16-Gbps blade server SAN I/O module






Brocade 7800 Switch 8-Gbps extension switch

Brocade 7840 Switch 16-Gbps 24-FC port, 18-GbE port switch

Brocade 8000 Switch 8-Gbps 8-FC port, 10-GbE 24-DCB port switch

Brocade 8470 FCoE Embedded Switch FCoE embedded switch

Brocade VA-40FC Switch 8-Gbps 40-port switch

Brocade Encryption Switch 8-Gbps encryption switch

Brocade Gen 6 platform (32-Gbps) fixed-port switch (Brocade G610) 24-port, 32-Gbps switch



Brocade DCX 8-slot backbone chassis

Brocade DCX with FC8-16, FC8-32, and FC8-48 Blades 8-slot backbone chassis with 8-Gbps 16-FC port, 8-Gbps 32-FC port,and 8-Gbps 48-FC port blades

Brocade DCX with FC8-64 Blades 8-slot backbone chassis with 8-Gbps 64-FC port blades

Brocade DCX with FC10-6 Blades 8-slot backbone chassis with FC 10 - 6 ISL blade

Brocade DCX with FS8-18 Blades 8-slot backbone chassis with encryption blade

Brocade DCX with FX8-24 Blades 8-slot backbone chassis with 8-Gbps 12-FC port, 10-GbE ports, 2-10GbE ports blade

Brocade DCX with FCoE10-24 Blades 8-slot backbone chassis with 10-Gbps 24-port FCoE blade

Brocade DCX-4S 4-slot backbone chassis

Supported hardware and software




Brocade DCX-4S with FC8-16, FC8-32, and FC8-48 Blades 4-slot backbone chassis with 8-Gbps 16-FC port, 8-Gbps 32-FC port,and 8-Gbps 48-FC port blades

Brocade DCX-4S with FC8-64 Blades 4-slot backbone chassis with 8-Gbps 64-FC port blades

Brocade DCX-4S with FC10-6 Blades 4-slot backbone chassis with FC 10 - 6 ISL blade

Brocade DCX-4S with FS8-18 Blades 4-slot backbone chassis with encryption blade

Brocade DCX-4S with FX8-24 Blades 4-slot backbone chassis with 8-Gbps 12-FC port, 10-GbE ports, 2-10GbE ports blade

Brocade DCX-4S with FCoE10-24 Blades 4-slot backbone chassis with 10-Gbps 24-port FCoE blade

Brocade DCX 8510-4 16-Gbps 4-slot backbone chassis

Brocade DCX 8510-4 with FS8-18 Encryption Blades 16-Gbps 4-slot backbone chassis with encryption blades

Brocade DCX 8510-4 with FC8-64 and FX8-24 Blades 16-Gbps 4-slot backbone chassis with 8-Gbps 64-port and 8-Gbpsrouter extension blades

Brocade DCX 8510-4 with FC16-32 and FC16-48 Blades 16-Gbps 4-slot backbone chassis with 16-Gbps 32-port and 16-Gbps48-port blades

Brocade DCX 8510-4 with FC8-32E and FC8-48E Blades 16-Gbps 4-slot backbone chassis with 8-Gbps 32-port and 8-Gbps 48-port blades

Brocade DCX 8510-4 with FC16-64 Blades 16-Gbps 4-slot backbone chassis with 16-Gbps 64-port blades

Brocade DCX 8510-8 16-Gbps 8-slot backbone chassis

Brocade DCX 8510-8 with FS8-18 Encryption Blades 16-Gbps 8-slot backbone chassis with encryption blades

Brocade DCX 8510-8 with FC8-64 and FX8-24 Blades 16-Gbps 8-slot backbone chassis with 8-Gbps 64-port and 8-Gbpsrouter extension blades

Brocade DCX 8510-8 with FC16-32 and FC16-48 Blades 16-Gbps 8-slot backbone chassis with 16-Gbps 32-port and 16-Gbps48-port blades

Brocade DCX-8510-8 with FCoE10-24 Blades 16-Gbps 8-slot backbone chassis with 10-Gbps 24-port FCoE blade

Brocade DCX 8510-8 16-Gbps 8-slot backbone chassis with 16-Gbps 64-port blades

Brocade X6-4 Director 32-Gbps, 4-slot backbone chassis

Brocade X6-8 Director 32-Gbps, 8-slot backbone chassis

FA4-18 Application Platform Blade Application platform blade

FC8-16 Blade FC 8-GB 16-port blade


FC8-32E Blade FC 8-GB 32-port blade


FC8-48E Blade FC 8-GB 48-port blade


FC10-6 Blade FC 10 - 6 ISL blade

FC16-32 Blade 16-Gbps 32-port blade








FCoE10-24 Blade 10-Gbps FCoE Port router blade

FS8-18 Encryption Blade encryption blade

FX8-24 Blade 8-Gbps extension blade

FC32-48 Port Blade 32-Gbps 48-port blade

SX6 Extension Blade 32-Gbps, router extension blade

HBA hardware and software supportAdapter Software 3.0.0.0 or later is supported by this release of Management application.

The following table lists the hardware platforms supported by this release of Management application.

TABLE 2 HBA-supported hardware

Device name Terminology used in documentation Firmware level required

Brocade 415 Host Bus Adapter 4-Gbps 1-port HBA





Brocade 1010 Adapter



Brocade 1860 Fabric Adapter 16-Gbps FC HBA mode

10-Gbps CNA mode

10-Gbps NIC mode

Adapter Software 3.0.0.0 or later

Brocade 1867 HBA 16-Gbps mezzanine HBA Adapter Software 3.0.3.0 or later

Brocade 1869 HBA

Emulex LPe12002-M8 8-Gbps 2-port HBA

Emulex LPe16000 16-Gbps 2-port HBA

Emulex LPe 32002-M2 32-Gbps FC HBA mode

Emulex LPe32000 Gen 6 HBA

QLogic QLE2562-CK 8-Gbps 2-port FC HBA x4 PCIe

QLogic QLE2672-CK PCI Express 3.0 x4 / PCI Express 2.0 x8low-profile 16-Gbps Fibre Channel x 2

Corp ISP2532 8Gb Fibre Channel to PCI Express HBA

QLogic QLE2742 PCIe 3.0 ×8 (dual-port) 32G FC HBA

QLogic QLE2740 Single-port PCIe 3.0 x8 to 32Gb FibreChannel Adapter – SFP+

QLogic QLE2764 Quad-port PCIe 3.0 x8 to 32Gb FibreChannel Adapter



IronWare OS hardware and software supportThe following firmware platforms are supported by this release of Management application:

• BigIron 2.7.02e (sustaining mode) or later

• FastIron 7.2.0 or later

• NetIron 5.1.0 or later

• ServerIron (JetCore) 11.0 or later

• ServerIron ADX 12.2.0 or later

• TurboIron 4.2.0 or later

For platform-specific firmware requirements, refer to Table 3.

The following table lists the hardware platforms supported by this release of Management application, the terminology used in thedocumentation, as well as any specific firmware requirements.

TABLE 3 IronWare OS supported hardware


BigIron family Ethernet chassis BigIron 2.7.02e or 2.7.01b

BigIron RX-4 (BI-RX-4-AC) Ethernet chassis, 4 interface slots BigIron 2.7.02e or 2.7.01b

BigIron RX-8 (BI-RX-8-AC) Ethernet chassis, 8 interface slots BigIron 2.7.02e or 2.7.01b

BigIron RX-16 (BI-RX-16-AC-A) Ethernet chassis, 16 interface slots BigIron 2.7.02e or 2.7.01b

Brocade 6910 Ethernet Access Switch Ethernet access switch Release 2.0.2.7, loader version 1.0.1.3

FastIron family Ethernet switch See individual device.

FastIron CX 624S (FCX624S) Ethernet L2/L3 edge switch, 24 1-GbE RJ-45ports

FastIron 06.0.00 and later

FastIron CX 648S (FCX648S) Ethernet L2/L3 edge switch, 48 1-GbE RJ-45ports


FastIron CX 624S-HPOE (FCX624S-HPOE) Ethernet L2/L3 edge switch, 24 1-GbE RJ-45ports, 24 POE+ ports


FastIron CX 648S-HPOE (FCX648S-HPOE) Ethernet L2/L3 edge switch, 48 1-GbE RJ-45ports, 48 POE+ ports


FastIron CX 624S-F (FCX624S-F) Ethernet L2/L3 edge switch, 20 SFP ports FastIron 06.0.00 and later

FastIron CX 624-E (FCX624-E) Ethernet L2/L3 edge switch, 24 1-GbE RJ-45ports


FastIron CX 624-I (FCX624-I) Ethernet L2/L3 edge switch, 24 1-GbE RJ-45ports


FastIron CX 648-E (FCX648-E) Ethernet L2/L3 edge switch, 48 1-GbE RJ-45ports


FastIron CX 648-I (FCX648-I) Ethernet L2/L3 edge switch, 48 1-GbE RJ-45ports


ICX 6430 IronStack Switch 24-port campus LAN switch FastIron 07.4.00 and later

ICX 6430 IronStack Base L3 Router Campus LAN base L3 router FastIron 07.4.00 and later

ICX 6430 IronStack Base Router Campus LAN base router FastIron 07.4.00 and later

ICX 6430 IronStack Premium Router Campus LAN premium router FastIron 07.4.00 and later

ICX 6430-24 Switch 24-port campus LAN switch FastIron 07.4.00 and later

ICX 6430-24-HPOE Switch 24-port campus LAN HPOE switch FastIron 07.4.00 and later





TABLE 3 IronWare OS supported hardware (continued)


ICX 6450 Stacking Switch Campus LAN stacking switch FastIron 08.0.00 or later


ICX 6450-24 Base L3 Router 24-port campus LAN Base L3 router FastIron 07.4.00 and later

ICX 6450-24 Base Router 24-port campus LAN Base router FastIron 07.4.00 and later

ICX 6450-24 Premium router 24-port campus LAN Premium router FastIron 07.4.00 and later


ICX 6450-24-HPOE Base L3 Router 24-port campus LAN HPOE Base L3 router FastIron 07.4.00 and later

ICX 6450-24-HPOE Base Router 24-port campus LAN HPOE Base router FastIron 07.4.00 and later

ICX 6450-24-HPOE Premium Router 24-port campus LAN HPOE Premium router FastIron 07.4.00 and later



ICX 6450-48 Base Router 48-port campus LAN Base router FastIron 07.4.00 and later

ICX 6450-48 Premium Router 48-port campus LAN Premium router FastIron 07.4.00 and later


ICX 6450-48-HPOE Base L3 router 48-port campus LAN HPOE base L3 router FastIron 07.4.00 and later

ICX 6450-48-HPOE Base Router 48-port campus LAN HPOE base router FastIron 07.4.00 and later

ICX 6450-48-HPOE Premium Rrouter 48-port campus LAN HPOE premium router FastIron 07.4.00 and later

ICX 6450 IronStack Switch 48-port campus LAN switch FastIron 07.4.00 and later

Hyper Edge stacking requires FastIron 08.0.00or later

ICX 6610 Stackable Switch family Campus LAN edge stackable switch FastIron 07.0.3 and later

HyperEdge stacking requires FastIron 08.0.00or later

ICX 6610-24 Stackable Switch Campus LAN edge stackable switch with 24RJ-45 ports



ICX 6610-48 Stackable Switch 48 RJ-45 ports campus LAN edge stackableswitch



ICX 6610-24F Stackable Switch 24 SFP ports campus LAN edge stackableswitch



ICX 6610-24P Stackable Switch 24 PoE ports campus LAN edge stackableswitch



ICX 6610-48P Stackable Switch 48 PoE ports campus LAN edge stackableswitch



ICX 7150-24 Switch 24-port campus LAN switch Non-stacking mode requires FastIron 08.0.60and later

ICX 7150-24P Switch Campus LAN switch with 48 POE ports Non-stacking mode requires FastIron 08.0.60and later

ICX 7150-48 Switch 48-port campus LAN switch Non-stacking mode requires FastIron 08.0.60and later





ICX 7150-48P Switch Campus LAN switch with 48 PoE ports and 4SFP ports

Non-stacking mode requires FastIron 08.0.60and later

ICX 7150-48PF Switch Campus LAN switch with 48 PoE ports and 4SFP ports

Non-stacking mode requires FastIron 08.0.60and later

ICX 7150-C12P Switch Compact campus LAN switch Non-stacking mode requires FastIron 08.0.60and later



ICX 7250-24 Router 24-port campus LAN router FastIron 08.0.30 and later


ICX 7250-24-HPOE Base L3 Router 24-port campus LAN HPOE Base L3 router FastIron 08.0.30 and later

ICX 7250-24-HPOE Base Router 24-port campus LAN HPOE Base router FastIron 08.0.30 and later





ICX 7250-48-HPOE Base L3 Router 48-port campus LAN HPOE base L3 router FastIron 08.0.30 and later


ICX 7250-24G Switch 24-port 1-GbE campus LAN switch FastIron 08.0.30 and later

ICX 7250-24G Base L3 Router 24-port 1-GbE campus LAN base L3 router FastIron 08.0.30 and later

ICX 7250-24G Router 24-port 1-GbE campus LAN router FastIron 08.0.30 and later


ICX 7450-24 Base L3 Router 24-port campus LAN base L3 router FastIron 08.0.20 and later





ICX 7450-32ZP 24-port 1-GbE or 8-port 2.5-GbE FastIron 08.0.40 and later

ICX 7450-32ZP Switch 24-port 1-GbE or 8-port 2.5-GbE switch FastIron 08.0.40 and later

ICX 7450-32ZP Base Router 24-port 1-GbE or 8-port 2.5-GbE base router FastIron 08.0.40 and later

ICX 7450-32ZP Router 24-port 1-GbE or 8-port 2.5-GbE router FastIron 08.0.40 and later


ICX 7450-48 Base L3 Router 48-port campus LAN base L3 router FastIron 08.0.20 and later





ICX 7450-48F Switch Campus LAN switch with 48 SFP ports FastIron 08.0.20 and later

ICX 7450-48F Base L3 Router Campus LAN router with 48 SFP ports FastIron 08.0.20 and later

ICX 7450-48F Router Campus LAN router with 48 SFP ports FastIron 08.0.20 and later

ICX 7750-26Q Switch 26 10/40-GbE QSFP+ ports FastIron 08.0.10 and later





ICX 7750-48F Switch 48 1/40-GbE SFP+ ports and 6 10/40-GbEQSFP+ ports


ICX 7750-48C Switch 48 1/40-GbE RJ-45 ports and 6 10/40-GbEQSFP+ ports


ICX 7750 and ICX 7450 Campus Fabric FastIron 08.0.40 and later

FastIron GS Ethernet L2/L3 access switch

FastIron GS-STK Ethernet L2/L3 access switch, stackable

FastIron LS Enterprise LAN switch

FastIron LS-STK Enterprise LAN switch, stackable

FastIron SuperX/SX Enterprise LAN chassis FSX 02.4.00 and later

FastIron SX 800 and FastIron SX 1600

FastIron 8-port 10 GbE SFP Blade 8-port 10-GbE SFP Blade

FastIron 24-port Fiber SFP GbE Blade 24-port Fiber SFP GbE Blade

FastIron 24-port GbE Cu Blade 24-port GbE Cu blade

FastIron 2-port 10GbE SFP+ Blade 2-port 10-GbE SFP+ Blade

FastIron Edge Switch X-Series Enterprise LAN edge switch

FastIron Edge X 424 Enterprise LAN edge switch, 24 10/100/1000Mbps ports




FastIron Edge X 424HF Enterprise LAN edge switch, 20 100/1000Mbps SFP ports

FastIron Edge X 624HF Enterprise LAN edge switch, 20 100/1000Mbps SFP ports

FastIron WS devices Enterprise campus switch

Motorola Controllers RFS4000 series Wireless controller Mobility 5.1



Motorola Access Point 5181 Wireless access point Mobility 2.5.X (standalone mode)

Mobility 5.1 32 (adaptive mode)

Motorola Access Point 6511 Wireless access point Mobility 5.1 32 (adaptive mode)

Motorola Access Point 7131 Wireless access point Mobility 4.1.1 (standalone mode)

Mobility 5.132 (adaptive mode)

Motorola Access Point 7131N Wireless access point Mobility 4.1.132 (standalone mode)

Mobility 5.1 32 (adaptive mode)

32 The Management application cannot discover or manage wireless access points running Mobility 5.1.





Ruckus SmartZone 100 Wireless controller 3.1.1.0.442

Ruckus R500 Wireless access point 3.1.1.0.442

Ruckus R700 Wireless access point 3.1.1.0.442

NetIron family Ethernet routers NetIron 5.0.0 or 5.0.1

NetIron MLX

(Supported regardless of license configuration)

Ethernet router NetIron 5.0.0 or 5.0.1

NetIron MLXe


Ethernet core router NetIron 5.0.0 or 5.0.1

NetIron XMR


Ethernet backbone router NetIron 5.0.0 or 5.0.1

NetIron CES 2048CX (NI-CES-2048CX-AC)


Ethernet carrier router NetIron 5.0.0 or 5.0.1

NetIron CER


Ethernet edge router NetIron 5.0.0 or 5.0.1

NetIron XMR/MLX 2-Port 100-GbE Module 2-Port, 100-GbE module NetIron 5.7.0

NetIron XMR/MLX 20-Port 10-GbE Module 20-port, 10-GbE module NetIron 5.7.0

NetIron MLX 4-Port 10-GbE Module 4-port, 10-GbE module NetIron 5.8.0

NetIron MLX MR2 Module Management module NetIron 5.8.0

NetIron MLX 4-Port 10-GbE IPSEC-M 4-port, 10-GbE IPSEC-M blade NetIron 5.8.0

NetIron MLX 2-Port 100-GbE (X2) CFP2 2-port, 100-GbE (X2) CFP2 blade NetIron 5.8.0

NetIron MLX 20-Port 10-GbE/1-GBE (X2) 20-port, 10-GbE (X2) blade NetIron 5.8.0

ServerIron family Application product

ServerIron ADX 1000 Application switch

ServerIron ADX 1000F Application fiber switch ADX 12.3.03 or later

ServerIron ADX 4000 4U application delivery chassis ADX 12.1.00 or later

ServerIron ADX 10000 10U application delivery chassis ADX 12.1.00 or later

TurboIron family Data center switch 4.1.00d or 4.2.00 or later

Brocade 6650 Switch Data center switch FastIron 7.5 and later

Brocade 6650 Base L3 Router Data center base L3 router FastIron 7.5 and later

Brocade 6650 Router Data center router FastIron 7.5 and later

TurboIron 24X (T1-24X-AC) Data center switch 4.1.00d or 4.2.00 or later

Network OS hardware and software supportThis release of Management application supports Network OS 4.1.0 or later firmware. For platform-specific firmware requirements, ifany, refer to the Table 4.

Table 4 lists the hardware platforms supported by this release of Management application, the terminology used in the documentation,and any specific firmware requirements.



TABLE 4 Network OS supported hardware


Brocade VDX 2730 10-Gbps ConnectionBlade

VDX 2730 10-Gbps connection blade 2.1.1_fuj

Brocade VDX 2740 Switch VDX 2740 switch 4.0.0_bbd

Brocade VDX 2746 Switch VDX 2746 switch 6.0 or later


Brocade VDX 6720-24 Switch VDX 6720-24 switch 2.1 or later





Brocade VDX 6740T Switch VDX 6740T switch 4.0 or later

Brocade VDX 6740T-1G Switch VDX 6740T-1G switch 4.1 or later

Brocade VDX 6940-144S Switch VDX 6940-144S switch 6.0.1 or later

Brocade VDX 6940-36Q Switch VDX 6940-36 switch 6.0 or later



Brocade VDX 8770 Switch with 40G/10GBase-T/100G by line card

VDX 8770 switch with 40G/10G Base-T/100G by line card

4.1 or later

Getting technical helpContact your switch support supplier for hardware, firmware, and software support, including product repairs and part ordering. Toexpedite your call, have the following information available:

• Management application serial number

To obtain the Management application serial number, select Help > License. The License dialog box displays.

• 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– Logs from serial console and Telnet sessions– Logs from syslog messages

• Switch serial number

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

Getting technical help


The serial number label is located as follows:

– Brocade 6510, 6505, 6520, G630, G620, G610 — On the switch ID pull-out tab located on the bottom of the port sideof the switch

– Brocade 7840 — On the pull-out tab on the front left side of the chassis underneath the serial console and Ethernetconnection and on the bottom of the switch in a well on the left side underneath (looking from front)

– Brocade DCX 8510-8 — Bottom right of the port side– Brocade DCX 8510-4 — Back, upper left under the power supply– Brocade X6-8, X6-4 — Lower portion of the chassis on the nonport side beneath the fan assemblies

• 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 asthe serial number, except for the Brocade DCX. For the Brocade DCX, access the numbers on the WWN cards by removing theBrocade logo plate at the top of the nonport side of the chassis.

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

• Information that was added:

– None

• Information that was changed:

– Updated release verison wherever applicable.

• Information that was deleted:

– None

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

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

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

hazards.

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

ATTENTIONAn Attention statement indicates a stronger note, for example, to alert you when traffic might be interrupted or the device mightreboot.

Document conventions


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

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

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

Format Description

bold text Identifies command names.

Identifies keywords and operands.

Identifies the names of GUI elements.

Identifies text to enter in the GUI.

italic text Identifies emphasis.

Identifies variables.

Identifies document titles.

Courier font Identifies CLI output.

Identifies command syntax examples.

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

Convention Description

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

italic text Identifies a variable.

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

[ ] Syntax components displayed within square brackets are optional.

Default responses to system prompts are enclosed in square brackets.

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

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

x | y A vertical bar separates mutually exclusive elements.

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

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

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

Document conventions


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

Send your feedback to [email protected]

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

Document feedback


mailto:[email protected]


Connecting to the Fabric• Role-Based Access Control..........................................................................................................................................................................21• Admin Domains and the Brocade Network Advisor SMI Agent................................................................................................... 21• Connecting to the Management application SMI Agent................................................................................................................... 22• Discovering a fabric and a host....................................................................................................................................................................22

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

The RBAC check is performed based on the value of the Storage Management Initiative (SMI) Agent Operations privilege for CommonInformation Model Object Manager (CIMOM) client requests. The following responses are received for the different values of the SMIAgent Operations privilege:

• No Access — If you query the CIMOM without the SMI Agent Operations privilege, the following WBEMException 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 from performing the WBEM queries.

• Read/Write Access — No restriction is imposed on any user who has Read/Write access for the SMI Agent Operationsprivilege.

• If a user A changes the password of a user B who has logged in to the CIMOM, user B can continue querying the CIMOM untilManagement application expires the user B session.

All the Resource Grouping (fabrics and hosts) performed through the user management dialog boxes is honored by the CIMOM. Theresource grouping is not applicable for filtering out indications. The indications from all fabrics managed by Management application aredelivered irrespective of the resource grouped by the user.

If you select the Authentication mode as No Authentication, all previously specified RBAC checks are performed on the credentialsprovided by you in the Authentication tab of the Configuration Tool and the previously described behavior is observed.

You can retrieve all information from the interop namespace, and you can perform the getclass operations even if there is no access forthe SMI Agent Operations privilege.

Refer to the Brocade Network Advisor User Manual for more information about RBAC.

Admin Domains and the Brocade Network AdvisorSMI AgentThe Management application SMI Agent does not support Admin Domains although they are supported in Management application.Brocade recommends excluding fabrics containing Admin Domains using the Resource Grouping option in the user dialog box that canbe launched from the Configuration Tool.


Connecting to the Management application SMIAgentThis section describes how to connect to the Management application SMI Agent when security is enabled and when security is notenabled.

Connecting to the Management application SMI Agent when security isenabledConnect with the Management application SMI Agent as shown in the following sample Java code. The code samples use the Java WebStart (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);

NOTEThe existing mutual authentication certificate is retained while migrating to version 14.0.1 from any previous versions. The userhas to manually generate and import the mutual authentication certificate using SMIA configuration tool, in case the defaultcertificate is used.

Connecting to the Management application SMI Agent when security isnot enabledYou can connect to the SMI Agent using any UserPrincipal and PasswordCredential, as these are not validated by the SMI Agent whensecurity is not enabled.

For more information on authentication, refer to the authentication section in the Brocade Network Advisor User Manual.

Discovering 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

Connecting to the Management application SMI Agent


Fabric discovery using the SMIA extrinsic methodThe CIMOM fabric discovery process enables the user to discover and delete fabrics through an extrinsic method implemented in theBrocade_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 Management application.

• 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 outparameter contains the fabric identifier (FID) and the error code of the fabric that failed to be 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 theunwanted contexts through the DeleteFabric extrinsic method.

• No support for monitor and unmonitor 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 givesthe data to be provided in the discover Fabric dialog box of the Management application 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.

Discovering a fabric and a host


FIGURE 1 Fabric discovery data model

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

Features supported

The following features are supported by the CIMOM host discovery process:

• Option to discover all types of hosts supported by Management application.

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

• No support to discover M model switches.

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.

The following figure 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 FabricDiscovery and Host Discovery links to discover the fabric and host.



FIGURE 3 Fabric discovery using the SMIA Configuration Tool



FIGURE 4 Host discovery using the SMIA Configuration Tool

For more information related to fabric and host discovery, refer to the Brocade Network Advisor User Manual.




Managed Object Format Files• Brocade Managed Object Format files.................................................................................................................................................... 29• Additional MOF description specifications.............................................................................................................................................30

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.

The following table lists the files that contain Brocade MOF definitions.

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

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


TABLE 5 Brocade Managed Object Format files (continued)

MOF filename Description

BrocadeTopologyView.mof Topology view

BrocadeVLAN.mof VLAN discovery and configuration

BrocadeZoning.mof Zone Control and SAN zoning subprofile

NOTEThe Brocade subclasses do not automatically override all of the properties in the superclass. The properties that are notoverridden have a null value unless the superclass has a default value that is defined in the MOF. When the property in theMOF 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 aredescribed:

• If a given instance of a class can be created or deleted by the Management application 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

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 qualifierInstance classes, association classes, properties, or extrinsic methods that have the Common Information Model (CIM) qualifierdeprecated in the MOF definition will continue to be implemented in the Management application SMI Agent. If a new implementation isdocumented, you should use the new implementation as soon as possible to minimize backward-compatibility issues.

Additional MOF description specifications


Profiles and Subprofiles• UML diagram conventions............................................................................................................................................................................31• SMI profiles and subprofiles..........................................................................................................................................................................31• Server profile........................................................................................................................................................................................................33• Fabric profile........................................................................................................................................................................................................ 35• Switch profile....................................................................................................................................................................................................... 62• CP blades (Brocade extension)....................................................................................................................................................................68• FC HBA profile................................................................................................................................................................................................... 70• Launch In Context profile................................................................................................................................................................................72• CEE switch support.......................................................................................................................................................................................... 76• Fabric switch partitioning subprofile.......................................................................................................................................................... 95• FC routing.............................................................................................................................................................................................................96• Brocade Access Gateway and NPIV...................................................................................................................................................... 106• FRU profiles......................................................................................................................................................................................................119• Names.................................................................................................................................................................................................................121

UML diagram conventionsThis chapter provides Unified Modeling Language (UML) diagrams depicting the Brocade additions to the Management application SMIAgent. Each UML diagram corresponds to the Brocade Managed Object Format (MOF) file of the same name.

The following figure illustrates the conventions used in the UML diagrams.

FIGURE 5 UML diagram convention

SMI profiles and subprofilesThe following table lists the features supported by the Management application SMI Agent. All SMI-S profiles and subprofiles conformsto SMI-S 1.4. Other profiles and subprofiles are vendor extensions.

TABLE 6 SMI profiles and subprofiles

Profile Subprofile SMI-S version

Server Indications 1.4


TABLE 6 SMI profiles and subprofiles (continued)

Profile Subprofile SMI-S version

Profile Registration

Object Manager Adapter

1.0.0

1.4

Fabric Fabric Profile

Zone Control

Enhanced Zoning and Enhanced ZoningControl

FDMI

FabricVirtualFabrics

FabricView

1.4

1.4

1.4

1.2

1.2

1.5

Switch Switch Profile

Blades

Physical Package

Software

Access Points

Location

FabricSwitchPartitioning

1.4

1.4

1.4

1.2

1.2

1.5

Host FC HBA Profile

FC Initiator Ports Subprofile

1.3

1.3

Fan, Power Supply, and Sensor Fan Profile

Sensors Profile

Power Supply Profile

1.0.0

1.0.0

1.0.0

Security Role-Based Authorization (CEE ACLonly)

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 PortInitialized Virtualization (NPIV)

N_Port Virtualizer Profile 1.5

Physical Package 1.5

1.5

1.5

Other features supported by the Management application SMI AgentThe following are the additional features supported by the Management application SMI Agent:

• Support for Fibre Channel Routing (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

SMI profiles and subprofiles


Server profileThe Server profile is supported by the Web-Based Enterprise Management (WBEM) Solutions J WBEM Server CIMOM. TheManagement application SMI Agent is a combination of two products, the CIMOM and the provider product. Each product supports itssoftware as shown in the following figure.

NOTEThe Management application SMI Agent's J WBEM Server has been upgraded from version 3.4.3 to version 3.9.0. The 64 bitManagement application will contain a 64 bit JServer with it and the 32 bit Management application will contain a 32 bitJServer.

Server profile


FIGURE 6 Server profile

Indications subprofileThe Indications subprofile is supported by the WBEM Solutions J WBEM Server CIMOM as shown in the following figure.

Server profile


FIGURE 7 Indications profile

Object manager adapter subprofileThe object manager adapter subprofile is supported by the WBEM Solutions J WBEM Server CIMOM.

Fabric profileThe Management application SMI Agent supports the Storage Networking Industry Association SNIA) Fabric profile, which defines themodel 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 ofcomponents that operate together as a single system and should be managed as such. The containment of Brocade_Fabricinstances 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 isopaque and NameFormat identifies how the property name is generated. In the case of Brocade_SAN, the propertyNameFormat 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 been discovered,Brocade_SAN.Name is the principal WWN of the base fabric.

• In virtual fabrics with dedicated ISL between the base switches where some of virtual fabrics have been discovered but there isno 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.

Fabric profile


• In Virtual fabrics with no dedicated ISL between the base switches but with a dedicated ISL between one of the discoveredvirtual fabrics.

– In the absence of a dedicated ISL between the base switches, no actual logical fabrics exist except for those which have adedicated 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 ofthe backbone fabric.

– In the absence of the backbone, each edge fabric is associated to its own SAN instance and the Brocade_SAN.Name is theprincipal 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 singleSAN. 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.

RegistrationThe following figure shows the SMIA profile registration profile model to advertise the Fabric profile and its subprofiles.

Fabric profile


FIGURE 8 Fabric profile registration

Data modelThe following figure shows the Fabric profile data model with the classes and properties that are supported to conform to the Fabricprofile. Only those properties that are mandatory are considered.

Fabric profile


FIGURE 9 Fabric profile

Fabric profile


NOTEThe following properties are mapped with the value specified to differentiate between Brocade_Fabric and Brocade_SANinstances.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 of the SAN. The name can be up to 15 characters.

• The Brocade_SAN.ElementName is not reset unless all fabrics in the SAN have been deleted from Management application.

• If the principal switch of the fabric changes, the associated SAN name for the SAN is retained.

• For a SAN consisting of multiple fabrics, the SAN name is retained until all fabrics in the SAN are deleted.

• For multiple fabrics managed by the Management application merge, the name of the SAN whose SAN key is retainedbecomes the new SAN ElementName.

• For a SAN that splits into multiple fabrics, the SAN that has the same name as the original SAN retains 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 35.

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 switchand 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 thatfabric 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 theconfigured name.

Fabric profile


• The SAN element name is reset to the default value when the principal switch WWN is changed during fabric merge orsegmentation.

– For example, assume there are two switch fabrics where switch1 is the seed switch and switch2 is the principal switch, andthe SAN Element name is configured. If a switch3 joins the fabric as a principal switch, the element name changes toswitch3 WWN and the configured name is lost.

Zone control and enhanced zone control subprofilesThe zone control subprofiles enable discovery of a fabric's zone database and provisioning of zoning operations.

RegistrationRefer to Registration on page 36.

Data modelThe following figure shows the data model with the classes and properties that are supported to conform to these subprofiles. Only thoseproperties that are mandatory are considered.

Fabric profile


FIGURE 10 Zone control and enhanced zone control subprofiles data model

The following table outlines the required CIM elements for the zone control subprofile.

TABLE 7 CIM elements for zone control subprofile

ElementName ElementName Currently supported Y/N?

CIM_HostedService Associates the ZoneService to the AdminDomain representing the fabric.

Yes

Fabric profile


TABLE 7 CIM elements for zone control subprofile (continued)

ElementName ElementName Currently supported Y/N?

CIM_ZoneService The service that allows for all of thezoning configuration changes.

Yes

Extrinsic methodsThe Brocade_ZoneService class contains the following extrinsic methods of the zone control subprofiles:

• CreateZoneSet

• CreateZone

• CreateZoneAlias

• CreateZoneMembershipSettingData

• CreateZoneMembershipSettingDataWithRole

• AddZone

• AddZoneAlias

• AddZoneMembershipSettingData

• AddZoneMembershipSettingDataWithRole

• ActivateZoneSet

• SessionControl

• SessionControl

• SessionControlWithJob

The following method is Brocade extension:

• ClearZoneDB

Zoning operation behaviorThe Management application SMI Agent depends on Management application to support zoning. The Management application SMIAgent 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 the Figure are supported.

• Starting a zoning transaction is done by invoking the SessionControl method. Only one CIM client is allowed to do zoning on aparticular fabric at a time from the same Management application SMI Agent. However, with the Management application SMIAgent, the transaction lock is only local and it is not open on the switch. The operation returns Success without actually doinganything 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 changesmade 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 thescope of a zoning transaction. If a transaction is open, then the changes must be done before activating, deactivating, or clearingthe database.

• A user is identified by Management application user name only, and so a zoning transaction opened by user1 on host1 can beused 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 username.

Fabric profile


• A commit operation is successful once the zoning changes are accepted by the seed switch. The successful completion of acommit operation does not mean that all the changes have been propagated to the entire fabric.

• If a Management application client first starts zoning on a fabric (opens a zoning dialog box for that fabric) and then an SMIclient starts a transaction on the same fabric, a notification is sent to the Management application client that another user isstarting zoning operations. This is a broadcast notification to all the Management application clients that currently have thezoning dialog box open to do zoning configuration on the same fabric. This behavior is the same as between two Managementapplication clients.

• If an SMI client starts a transaction on a fabric and a Management application client opens a zoning dialog box, a notification isissued, which need not be considered. The SMI client could be in the middle of the session changes.

• If the SMI client commits first, the Management application client is notified that the zone database has been changed. TheManagement application client has the option of ignoring or refreshing the zone database copy. This is a warning message andthere is nothing preventing the Management application client from ignoring the warning. This behavior is the same as betweentwo Management application clients.

• If a Management application client commits the changes first, the SMI client's zone transaction is aborted and an indication issent.

• If the time for which an open transaction is idle or greater than Brocade_ZoneService.Timeout (value in seconds), the SMIclient'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 inthe SMI Agent.

Job control profile for SessionControlWithJob andActivateZoneSetWithJobDuring a commit or activate operation, it is possible that the operation takes time to complete. Internally, the ZoningServer posts theoperation to the switch through HTTP, which then keeps polling the result until it receives a success or failure. The time lag between thepost and poll result depends on the zone database size on Fabric OS.

To prevent blocking of the CIMClient, two asynchronous methods have been provided in the Brocade_ZoneService:SessionControlWithJob and ActivateZoneSetWithJob. The execution of these methods returns a Brocade_ConcreteJob instance whenthe CIM client commit SAN Zone changes through the SANSessionControl extrinsic call. The Brocade_ConcreteJob andBrocade_SANZoneService are associated by the Brocade_SANZoneControlOwningJobElement andBrocade_SANZoneControlAffectedElement classes.

Even though this subprofile is used, the Management application SMI Agent will not be 100 percent compliant. For example, theextrinsic GetError() method is not supported. Therefore, this subprofile is not advertised.

Fabric profile


Data modelThe following figure 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 whoseSessionState 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 timeit will indicate 100 percent.

• The DeleteOnCompletion property is always set to false, indicating that all jobs, failed or completed must be deleted explicitlyby 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 Management application SMI Agent, the TimeBeforeRemovalproperty is not applicable and is always set to zero.

Fabric profile


• 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 theold job. The old job is permanently deleted.

• 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 Management application server restart, all existing Brocade_ConcreteJob instances are deleted because they are notpersisted in the Management application database.

Supported indicationsThe following table shows all the supported mandatory indications.

TABLE 8 Supported indications

Indication Description

SELECT * FROM CIM_InstModification WHERE SourceInstance ISACIM_ConcreteJob ANDSourceInstance.CIM_ConcreteJob::PercentComplete <>PreviousInstance.CIM_ConcreteJob::PercentComplete

Modification of PercentComplete for a concrete job.

SELECT * FROM CIM_InstModification WHERE SourceInstance ISACIM_ConcreteJob AND ANYSourceInstance.CIM_ConcreteJob::Operation alStatus[*] = 17 AND ANYSourceInstance.CIM_ConcreteJob::OperationalStatus[*] = 2

The service that allows for all of the zoning configuration changes.Modification of OperationalStatus for a concrete job to Complete and OK.

SELECT * FROM CIM_InstModification WHERE SourceInstance ISACIM_ConcreteJob AND ANYSourceInstance.CIM_ConcreteJob::Operation alStatus[*] = 17 AND ANYSourceInstance.CIM_ConcreteJob::OperationalStatus[*] = 6

Modification of OperationalStatus for a concrete job to Complete andError.

SELECT * FROM CIM_InstModification WHERE SourceInstance ISACIM_ConcreteJob AND SourceInstance.CIM_ConcreteJob::JobState <>PreviousInstance.CIM_ConcreteJob::JobState

Modification of JobState for a concrete job.

SELECT * FROM CIM_InstCreation WHERE SourceInstance ISACIM_ConcreteJob

Creation of a concrete job.

SAN zoningStorage Area Network (SAN) zoning is a method of arranging Fibre Channel devices into logical groups over the physical configuration ofthe fabric. Management application 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 samedevices.The LSANs provide selective device connectivity between fabrics without forcing you to merge those fabrics.

Peer zoningIn Fabric OS 7.4.0 and later, Peer zone Read-Only support is provided on the Management application SMI Agent for LSAN zoning withfollowing 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.

Fabric profile


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

LSAN zoning in Management applicationThe following are the behaviors of Management application client for LSAN zoning:

• The LSAN zoning device sharing operations are done only through backbone fabrics. This option is disabled for other edgefabrics.

• 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 modelThe following figure shows the data model of SAN zoning.

Fabric profile


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

Fabric profile


• The Brocade_SANZoneCapabilities supports only the mandatory properties such as InstanceID, ZoneNameMaxLen,ZoneNameFormat, and SupportedConnectivityMemberTypes.

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

• Use SANSessionControl method with RequestedSessionState=2 to start a session before configuring SAN zones throughCreateSANZone, 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 youstart 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 asinputs. 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 thezone 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 thefabrics.

• 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) andBrocade_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 activeconfiguration in the edge fabric or backbone fabric, a zone set with the name of “LSAN_CFG_<date/time>” is created and therespective SAN zone is added under this zone set.

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

Fabric profile


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 CIMclient. It is not delivered if there is a failure in SAN zone activation through Management application client.

• Alert indication with message ID FC2 is delivered for successful activation because zoning activation is performed at fabriclevel.

Use casesThe following figure 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 fromfabric1 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).

• Create a LSAN_Zone2, add WWN of Host, Target1, Target3, and activate the same zone. As the LSAN_Zone2 has devicesfrom 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 witherror code 4 (FAILED).

• Create LSAN_Zone4, add host, and offline members and activate the same zone. It is activated in fabric1 as the host belongsto fabric1.

Fabric profile


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

– 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 isdelivered for activation failures.

• Create SAN zone with the prefix “XSAN_”, add some zones member WWNs, and activate the zone. As there are invalid zonenames, 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.

Fabric virtual fabrics subprofileThe fabric virtual fabrics subprofile models the partitioning of a physical fabric into one or more logical fabrics. The physical fabricconsists of one or more switches that can be partitioned. The switch in the physical fabric that can be partitioned is called the partitioningsystem. The resulting virtual fabric will consist of one or more switches formed from the partitioning systems. The resulting virtual switchin the virtual fabric is called the partitioned system. The virtual fabric topology, along with its virtual switches, is modeled as per the Fabricprofile. The underlying physical fabric topology, along with its partitioning systems, is modeled by the fabric virtual fabrics subprofile. Byusing 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.

Fabric profile


• 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). BySMI definition, all virtual fabrics that are physically interconnected belong to the same SAN. The Brocade_SAN instance containing thevirtual fabrics associates itself to an instance of Brocade_RegisteredSubprofile (FabricVirtualFabrics) only if the base switch is discovered.Refer to Registration on page 36.

Data modelThe following figure 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.

Fabric profile


FIGURE 14 Fabric virtual fabrics subprofile data model

Sample discovery configurationThe following figure shows a sample Virtual Fabrics configuration. In this configuration, there are five physical chassis. Chassis 1, Chassis2, and Chassis 3 are physical chassis that are enabled for Virtual Fabrics and divided into logical switches. Switch A and Switch B aresingle-switch chassis and are not enabled for Virtual Fabrics.

Fabric profile


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– 3 logical switches in Chassis 2– 3 logical switches in Chassis 3– Switch B

Fabric profile


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

• 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 eitherChassis 3 or Switch A, because the Fabric OS will not provide the information for these switches if the SMI Agent is connected only toChassis 2.

The devices connected to ports in a logical switch are discovered in the fabrics to which these switch ports belong. For example, a deviceconnected to a port belonging to a logical switch with Fabric ID 1 is discovered only if you have access to Fabric ID 1. Device discoveryfollows 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 directorswitch 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 logicalswitches 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.

The following figure shows a basic instance diagram for a director switch containing two logical switches, where both the logical switchescontain a port from the blade in slot 1.

Fabric profile


FIGURE 16 Director switch instance diagram

Topology viewThe Topology View class was introduced in SMI-S 1.3 to increase the performance and reduce the number of traversals required todiscover topology.

The Management application SMI Agent cannot provide a complete topology and its related information including instances of classeslike 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 enumeratingBrocade_SANActiveConnection(CIM_ActiveConnection), and traverse to each endpoint to gather data about the link between switchports 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.

RegistrationThe following figure shows the registration model of Topology view.

Fabric profile


FIGURE 17 Topology view registration model

Data modelThe following figure shows the data model of Topology view.

Fabric profile


FIGURE 18 Topology view data model

NOTEBeginning with version 12.4.2, Brocade_TopologyView class is changed from association to provider, in order to support theproperty name change of AntecedentFCPort, AntecedentSystem, DependentFCPort, and DependentSystem from REF toString.

FDMI subprofileThe Fabric-Device Management Interface (FDMI) enables the management of devices such as Host Bus Adapters (HBAs) through thefabric. This subprofile models the discovery of HBA type devices without having the SMI Agent reside on the host containing the HBA. Itshows how an HBA is hosted on the system (host) along with the nodes contained in it and ports controlled by it. It allows HBAs toexpose product information such as firmware version, vendor, serial number, and so on. This model supports all HBA configurationssuch as single-node single-port HBA, single-node dual-port HBA, and dual-node dual-port HBA.

Fabric profile


PrerequisitesOnly 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_Platformmodel, 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 OSv7.0.0 or later to support this profile.


Data modelThe following figure 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, andBrocade_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 singleBrocade_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_PortControllerrepresenting 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 singleBrocade_PortController representing the logical aspects of the Brocade_PhysicalHBA controlling both Brocade_NodeFCPort instances.

Fabric profile


FIGURE 19 FDMI data model

Fabric profile


TrunkingThis section defines the model for the trunking feature in Management application SMI Agent. The trunking model is supported only forFOS switches.

NOTEThe m-EOS switches open trunking feature is not supported in Management application SMI Agent and there will not be anymodeling m-EOS open trunking.

Both ISL trunking and F_Port trunking are supported for FOS switches.

Data modelThe following figure 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.

Related API and classesThe following table represents the group of switch ports forming a trunk.

TABLE 9 Brocade_Trunk: CIM_RedundancySet

Property name Type Description

InstanceID [Key] string InstanceID opaquely and uniquely identifies an instance of thisclass.

The format of this key is as follows.

Fabric profile


TABLE 9 Brocade_Trunk: CIM_RedundancySet (continued)


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 trunkmembers in a trunk group.

DEST_WWN is the WWN of the other end, which is a switch incase of an ISL trunk and an 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 theRedundancySet.

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

The following table explains the properties of Brocade_TrunkInSwitch: CIM_HostedCollection class.

TABLE 10 Brocade_TrunkInSwitch: CIM_HostedCollection


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

Dependent Brocade_Trunk REF Represents the trunk object.

The following table explains the properties of Brocade_SwitchFCPortInTrunk: CIM_MemberOfCollection class.

TABLE 11 Brocade_SwitchFCPortInTrunk: CIM_MemberOfCollection


Collection Brocade_Trunk REF Represents the trunk object.

Member Brocade_SwitchFCPort REF Represents the member of the trunk.

The following table explains the properties of Brocade_AGFCPortInTrunk: CIM_ MemberOfCollection class.

Fabric profile


TABLE 12 Brocade_AGFCPortInTrunk: CIM_ MemberOfCollection


Collection Brocade_Trunk REF Represents the trunk object.

Member Brocade_AGFCPort REF Represents the member of the trunk.

Switch profileThe Storage Networking Industry Association (SNIA) switch profile defines the model and functions of a fibre channel switch includingstate, status, and control of the device and its connections.

RegistrationThe SNIA Profile Registration Profile model is followed to advertise Switch profile and its subprofiles.

The following figure shows the instance diagram with the objects and properties for Switch profile registration. Only for blades, the actualblade instances that conform to the Blades subprofile will be associated. For the other subprofiles, such as Software, Access Points, andso on, the association to the actual instances are not supported.

Switch profile


FIGURE 21 Switch profile registration

Data modelThe following figure shows the Switch profile data model.

Switch profile


FIGURE 22 Switch profile data model

Switch profile


NOTEThe value of the Dedicated property of Brocade_Switch is Switch (5) and FC Switch (37). The set operation for theBrocade_SwitchFCPortSettings.RequestedType is supported from Fabric OS v6.3 and later.

NOTESwitch unmonitoring is not supported from the SMI perspective, and if the switch is unmonitored, the SMI Agent returns staleinformation.

Differentiation between switches and domainsThe following properties are used in CIM_CompterSystem to differentiate a simple switch, a switch created through VF, a switch createdthrough Inter-Fabric Routing Profile (IFR), differentiating Front Domain from the Translate Domain, and the physical system that ispartitioned.

• IdentifyingDescriptions = {"DomainID", "SNIA:DetailedType"}

• OtherIdentifyingInfo = {"1", "Front Domain"}; where "1" is DomainID and Front Domain is the type.

• OtherIdentifyingInfo has the value of DomainID and switch detailed type (Front Domain, Translate Domain, Virtual Switch, orNone).

• In case of VF setup, OtherIdentifyingInfo additionally has the values of the VF_ID, and the IdentifyingDescriptions propertiesadditionally 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(VFs), Fibre Channel over IP (FCIP) and Fibre Channel over Ethernet (FCoE). This property is applicable only to logical ports.The possible values are given in following table.

TABLE 13 PortDiscriminator values

No Port PortDiscriminator value

1 FC ports on the FCIP Ethernet port FCIP

2 Virtual FCoE ports inside the Brocade8000

internal + FCoE

3 Virtualized node ports in NPIV andAccess Gateway

NPIV

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

IFR virtual

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

IFR

6 ICL ports Chassis

7 Dynamically created FC ports for logicalconnections in virtual fabrics

VF

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 subprofilesThe Physical Package, Access Points, Software, Blades, and Location subprofiles model the product information of a switch, the URL tolaunch the element manager of a switch, the blades within the chassis, and the details such as the primary system owner name, contact,and location of a Brocade chassis.

The following table explains the subprofiles and their functions.

Switch profile


TABLE 14 Switch subprofiles

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


Data modelThe following figure shows the data model with the classes and properties that are supported to conform to the switch subprofiles.

Switch profile


FIGURE 23 Physical Package, Access Points, Software, Blades, and Location subprofiles data model

Switch profile


NOTEThe Brocade_Chassis.ElementName property is set correctly in the corresponding instance only if the seed switch is runningon Fabric OS v6.3.x or higher and if the chassisName in the switches of the fabric are set after the seed switch firmware hasbeen upgraded.

CP blades (Brocade extension)This section details the modeling of the Core Processor (CP) blade and its associated properties (IP address, state, and so on) on thedirector class Brocade switches.

Data modelThe following figure shows the instance diagram of the CP blades.

CP blades (Brocade extension)


FIGURE 24 CP blades instances diagram

• Brocade_CPModule instances representing CP blades are not associated to Brocade_RegisteredSubProfile throughBrocade_ElementConformsToSubProfile.

• Each Brocade_Blade instance representing the CP blade is logically realized as Brocade_CPModule:CIMLogicalModule. Adifferent class for this logical module is used instead of PortModule. The PortModule contains NumPorts property, which is notapplicable 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.

• The Brocade_CPModule.ModuleNumber shows the slot number of the CP blade.

CP blades (Brocade extension)


• The Brocade_CPModule is associated to the Brocade_PhysicalComputerSystem usingBrocade_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 theCP.

• The Brocade_CPModule instances is aggregated to the Brocade_PhysicalComputerSystem, which is the parent system.

Supported classes and associationsThe supported classes and associations are shown in the above figure.

FC HBA profileThe Fibre Channel Host Bus Adapter (FC HBA) profile is similar to the FDMI subprofile. As with FDMI, this model also supports all HBAconfigurations such as single node-single port HBA, single-node dual-port HBA, and dual-node dual-port HBA.

PrerequisitesOnly the HBAs discovered in Management application are exposed through the FC HBA profile.

Data modelThe following figure shows the data model of the FC HBA profile.

FC HBA profile


FIGURE 25 FC HBA profile data model

NOTEThe HBA is represented by the PortController class and the serial number is the key.

FC HBA profile


Launch In Context profileManagement application supports a number of services for network management, such as Configure Names, Historical PerformanceReport, and Fabric Ports Report. These services are published through the Launch In Context (LIC) profile.

LIC namesThe following table shows the list of LIC names and their descriptions.

TABLE 15 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 usingthe most bandwidth on the selected fabric.

Fabric_Switch_Ports_Report Displays the port details report for all the discovered ports in the givenfabric. The port detail includes switch information, connected deviceinformation, 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 switchesand hosts. Also, ability to schedule later to capture the supportSaveinformation from one or more switches.

Fabric_Switch_Threshold_Policies Configures threshold policies on E_Ports and F_Ports or FL_Ports for theTx and Rx percentage utilization measures. Sends an appropriate alert tonotify when the threshold is exceeded.

Fabric_Device_Connectivity_Diagnostics Identifies the problems preventing communication between the twoselected device ports from the same fabric or from two different fabrics.

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 samedevices 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 graphsthat displays a variety of user-selected performance measures.

Fabric_Historical_Graph Monitors a device's performance through historical performance graphsfor predefined performance measures.

Fabric_Audit_Log Displays all application events raised by the application modules and allaudit 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 receivealerts.

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.

Launch In Context profile


TABLE 15 Description of LIC names (continued)

LIC name Description

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 ofthe F_Ports on the connected device. Use these monitors to view bothreal-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 tunnelsand FCIP circuits between two extension switches.

Fabric_Ficon_Log Displays all the LIR and RLIR type events, for example, link incident typeevents.

Fabric_Logical_Switches_Configuration Configures the virtual fabrics. Creates base and logical switches, assigningports to a logical switch and configuring fabric-wide parameters.

Fabric_Port_Fencing Port fencing allows users to set policies that will block switch ports ifcertain conditions are met. Configure port fencing to set threshold limitsfor the number of specific port events permitted during a given timeperiod on the selected object.

Fabric_ProductStatus_Log Displays events which indicate a change in switch status for all discoveredswitches.

Fabric_Router_Configuration Configures FC routing to connect devices in different fabrics withoutmerging the fabrics. Enables you to connect edge fabrics to a backbonefabric.

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

FCoE_Configuration Creates, edits, and deletes the FCoE login groups and view the connecteddevices 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 modelThe following figure shows the class diagram of the LIC profile.

The Brocade_LICServiceAccessPoint of Configuration Tool and Management application client are associated toBrocade_ManagementServer through Brocade_LICMgmtServerHostedServiceAccessPoint. Other than the Configuration Tool andManagement application client, the service access points are associated to Brocade_SAN throughBrocade_LICSANHostedServiceAccessPoint.

Each Management application service launch point is represented by an instance of Brocade_LICServiceAccessPoint. The access pointis 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 modulename>&<SSO parameters if any from Network Advisor client>&${parameterName}



http://<IP Address: port number>/webstart/<JNLP file name>?module=<Network Advisor module name>&<SSO parameters if any fromNetwork Advisor client>&${parameterName}

Where ${parameterName} specifies the LIC parameters supported for the specific Management application dialog box URL.

The Brocade_LICServiceAccessPoint.ParameterName is an array holding the LIC parameters specified in the URL of AccessInfoproperty value. The Brocade_LICServiceAccessPoint.Parameter Description is holding the description of the parameters in theParameterName array.

In the AcessInfo URL, replace the ${parameterName} with name and value of the ParameterName array in the format mentioned in thedescription.



For example,http:// <IP Address: port number>/webstart/<JNLP file name>?module=<module name>&<SSO parameters ifany>&${<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, theParameterName is Brocade:::<WWN>

NOTEExtrinsic methods of launch service are not supported.



FIGURE 26 Launch In Context registration and data model

CEE switch supportThe Brocade CEE switch behaves as both an FC switch and an Ethernet switch. The FC capabilities are captured through the Switchprofile. 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 nothave any contained domain association. Only the Fibre Channel fabric is associated to the SAN instance. Brocade_SAN.name is theprinciple WWN of the Fibre Channel fabric.

CEE switch support


RegistrationRefer to Registration on page 62. The Brocade_Switch instance representing the CEE switch is associated to theBrocade_RegisteredProfile instance for switch. There is no profile conformance for the Ethernet portion of the model due to evolvingstandards.

Data modelThe following figure shows the FC and Ethernet topologies along with their connections to the physical elements. This is a general modelthat covers device and switch connections to the CEE switch:

• Two CIM_ComputerSystem instances (Brocade_Switch and Brocade_EthernetSwitch) is shown to represent the FC andEthernet sides of the switch. These instances are associated to the physical counterpart, which is theBrocade_PhysicalComputerSystem.

• Brocade_EthernetSwitch is a component of Brocade_EthernetAdminDomain on the Ethernet topology side. Similarly, theBrocade_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 theBrocade_PCSNetworkPort.

• The virtual FCoE port is represented as the Brocade_SwitchFCPort instance with the PortType as G, or F, or E and is not beassociated to a Brocade_PCSNetworkPort. It is an internal port and there is no physical representation for that port. Eventhough the virtual FCoE ports are internal to the switch, they will be modeled as visible switch ports in order to show the devicesphysically (directly or indirectly) connected to one of the Ethernet interfaces. However, these internal ports exist in the ASIC andthe 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 hosttopology as the node and node ports.

• The Brocade_EthernetPort of the host is associated to the Brocade_NodeFCPort(s) (HostedDependency). TheBrocade_EthernetPort on the host will not have all properties populated. All key properties are populated. Among the non-keyproperties, the OperationalStatus is 2 (OK) and EnabledState is 2 (Enabled).

• All LANEndPoints are part of the EthernetLogicalNetwork in the Brocade_EthernetAdminDomain.

• Configuration of the virtual FCoE port is supported. It is a normal switch port instance. Each Brocade_SwitchFCPort instancerepresenting a virtual FCoE port is associated to Brocade_SwitchFCPortSettings and Brocade_SwitchFCPortCapabilitiesinstances (not shown in the above figure 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 forthe Ethernet interfaces due to the lack of an SMI model.

CEE switch support


FIGURE 27 FCoE topology diagram

CEE switch support


Topology supportedThe Management application 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 37 and Data model on page 66. The FCtopology 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 thedevice port and device node WWN for each session registered in the NS database. Figure 27 shows elements in both the FCand 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 devicenode WWN for each session registered in the NS database. Figure 27 shows elements in both the FC and Ethernet side. Theelements 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. TheEthernet portion in the following figure depicts the elements and their connections. There will be oneBrocade_EthernetAdminDomain and one Brocade_EthernetLogicalNetwork per subnet.

CEE switch support


FIGURE 28 CEE instance diagram

Zoning supportZoning is supported only on the front-end FC ports. The Management application SMI Agent has the same limitations as Managementapplication.

ConfigurationThe Management application SMI Agent relies on Management application 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

CEE switch support


• 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

Enabling or disabling the CEE portThe CEE port is represented by Brocade_EthernetPort. The class Brocade_EthernetPort in BrocadePartitioning.mof is updated with thefollowing content:

• A new extrinsic method RequestStateChange is inherited from the standard CIM class CIM_EnabledLogicalElement. Thismethod 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 lastRequestedState is not supported for the CEE port, thus the property will always have the value 12 (Not Applicable).

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

Setting the Layer 2 mode of the CEE portSetting the Layer 2 mode of a CEE port is done by setting the OperationalEndpointMode property of the Brocade_LANEndpointassociated to the CEE port. The class Brocade_LANEndpoint in BrocadeEthernet.mof is updated with a new property

CEE switch support


OperationalEndpointMode, which is a proprietary property that indicates whether the CEE port is in access, trunk or converged Layer 2mode 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 an Ethernet switch and CEE portWith Layer 2 networks expanding dramatically, it is difficult for a network administrator to statically monitor and configure each device inthe network. Using Link Layer Discovery Protocol (LLDP), network devices such as routers and switches advertise information aboutthemselves 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 efficientscheduling and a priority-based flow control for link traffic. DCBX is built on the LLDP infrastructure and uses LLDP to exchangeparameters between two link peers. DCBX is on by default.

Management application SMI Agent supports enabling or disabling the default LLDP-DCBX at the switch and port levels. Users canenable or disable the global configuration at the switch level. User can also enable or disable the specific LLDP configuration currentlyapplied at the port level.

There is no support for defining any new LLDP profiles through Management application SMI Agent.

Saving the running configuration to the startup configuration on the CEE switchThis feature allows you to save all the CEE configuration changes made after startup so that they are persisted across reboots. The classBrocade_EthernetSwitch in BrocadeEthernet.mof is updated with a new extrinsic method ConfigSaveRunningToStartup. This methodsaves the CEE changes to startup configuration on the switch. The changes are visible even after a reboot.

LimitationsThe value of LLDP-DCBX for port and switch is not persisted in Management application. In order to retrieve the value of this property, acall needs to be executed. As a result, populating this property for port and switch during an enumerateInstances operation is costly andwill lead to a degradation in discovery timings. The Management application SMI Agent will populate this property as Unknown in bothBrocade_EthernetSwitch and Brocade_EthernetPort, if the instance is retrieved through enumerateInstances. Users can get the correctvalue of this property on demand through the getInstance() intrinsic operation only.

The value of Brocade_VLANEndPoint is not persisted in Management application. Management application SMI Agent will populate thisproperty as Unknown.

LAGsLink aggregation allows you to bundle multiple physical Ethernet links to form a single logical trunk providing enhanced performance andredundancy. The aggregated trunk is referred to as a Link Aggregation Group (LAG). The LAG is viewed as a single link by connecteddevices, the Spanning Tree Protocol (STP), Virtual Local Area Network (VLANs), and so on. When one physical link in the LAG fails, theother links stay up and there is no disruption to traffic.

Management application SMI Agent supports discovery of these LAGs. In addition, support will be provided to create, delete, and modifyexisting LAGs.

NOTETo configure links to form a LAG, the physical links must be in the same speed and all links must go to the same neighboringdevice.

CEE switch support


Data modelThere is no SNIA model for LAGs. Some aspects of the Distributed Management Task Force (DMTF) model are considered while othersare completely proprietary. The following detailed notes describe the class diagram as shown in the following figure.

• The LAG is a protocol endpoint defined at the scope of the switch and is represented by an instance of Brocade_LAGassociated 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. Thecomposition is through Brocade_LAGPortInLAG.

• The member is also defined at the scope of the switch associated to the scoping system, which is the Brocade_EthernetSwitchthrough Brocade_EthernetSwitchHostedLAGPort.

• Each Brocade_LAGPort instance represents a concrete Brocade_LANEndPoint of a Brocade_EthernetPort that has beenadded to the BrocadeLAG. This relationship between the Brocade_LAGPort and the Brocade_LANEndPoint is represented asBrocade_LAGPortOfLANEndPoint.

• There is one Brocade_LAGService instance per Brocade_EthernetSwitch. This hosting is represented byBrocade_LAGServiceInEthernetSwitch.

• The capabilities of the service are represented by an instance of Brocade_LAGServiceCapabilities associated to the servicethrough Brocade_LAGServiceElementCapabilities. The maximum number of lags that can be created on the switch and themethods 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 existingLAG.

• Brocade_LAG can be created using the Brocade_LAGService.CreateLAG() extrinsic method. Refer to BrocadeLAG.mof fordetails on the parameters. The path of the newly created Brocade_LAG instance is returned in the output parameter Lag. TheBrocade_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() extrinsicmethod. 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. Thismethod will delete the instance and its members.

CEE switch support


FIGURE 29 CEE LAG class diagram

RegistrationThere is no conformance to any profile, and thus no registration.

CEE switch support


VLANsVirtual Local Area Network (VLANs) provide the capability to overlay the physical network with multiple virtual networks. VLANs allowyou to isolate the network traffic between virtual networks and reduce the size of administrative and broadcast domains. A VLANcontains end stations that have a common set of requirements that are independent of physical location. You can group end stations in aVLAN even if they are not physically located in the same LAN segment. VLANs are typically associated with IP subnetworks and all theend stations in a particular IP subnet belong to the same VLAN. VLAN membership is configurable on a per-interface basis.

Data modelThere is no SNIA model for VLANs. Some aspects of the Distributed Management Task Force (DMTF) model have been consideredwhile others are completely proprietary. The following detailed notes describe the class diagram as shown in the following figure.

• The VLAN is a collection of protocol endpoints defined at the scope of the switch and is represented by an instance ofBrocade_VLAN associated to the scoping system, which is the Brocade_EthernetSwitch throughBrocade_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 ofBrocade_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_EthernetSwitchthrough Brocade_EthernetSwitchHostedVLANEndPoint.

• Each Brocade_VLANEndPoint instance represents a concrete Brocade_LAG or Brocade_LANEndPoint of aBrocade_EthernetPort that has been added to the Brocade_VLAN. This relationship between the Brocade_VLANEndPoint andthe Brocade_LANEndPoint is represented as Brocade_VLANEndPointOfLANEndPoint. And the relationship between theBrocade_VLANEndPoint and the Brocade_LAG is represented as Brocade_VLANEndPointOfLAG.

• There is one Brocade_VLANService instance per Brocade_EthernetSwitch. This hosting is represented byBrocade_VLANServiceInEthernetSwitch.

• The capabilities of the service are represented by an instance of Brocade_VLANServiceCapabilities associated to the servicethrough Brocade_VLANServiceElementCapabilities. The maximum number of VLANs that can be created on the switch andthe 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 anexisting VLAN.

• Brocade_VLAN can be created using the Brocade_VLANService.CreateVLAN() extrinsic method. Refer to mof content fordetails on the parameters.

• The path of the newly created Brocade_VLAN instance is returned in the output parameter VLAN. The Brocade_VLAN will beassociated 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() extrinsicmethod. Refer to BrocadeLAG.mof for details on the parameters.

• Members can be removed from an existing Brocade_VLAN instance using theBrocade_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. Thismethod will delete the instance and its members.

CEE switch support


FIGURE 30 CEE VLAN class diagram

CEE switch support



LimitationsThe 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 theBrocade_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 InstanceNames and Enumerate Instances only. The value is Unknown on GetInstance due to performance issue.

• Ingress and egress filtering is always enabled.

CEE ACLsAccess Control List (ACL) is used to filter Ethernet traffic of the Ethernet switch. It permits or denies incoming packets from passingthrough interfaces that has the ACL policies applied to them. The primary function is to control the movement of packets through or tothe 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-GigabitEthernet Layer 2 interfaces (Physical interfaces, Logical interfaces, and LAGs). Each ACL is a unique collection of permit and denystatements (rules) that apply to the packets. When a packet is received on an interface, the switch compares the fields in the packetagainst any ACLs applied to the interface to verify that the packet has the required permissions to be forwarded. The switch comparesthe packet sequentially against each rule in the ACL and either forwards the packet or drops the packet.

The Management application SMI Agent supports the discovery of these ACLs, both standard and extended. In addition, support isprovided to create, delete, and modify existing ACLs. Resequencing of an ACL is not supported. Displaying and clearing of the ACLstatistics counter is not supported. However, users can enable or disable the tracking of traffic by specifying the count parameter withinthe 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 standardMAC 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.

• Even though ACLs can be Layer 2-specific (MAC) or Layer 3-specific (IP), they can only be applied on the same type ofinterface. Because an interface can only be set to Layer 2 mode, Layer 2 ACLs and only ACLs with MAC source anddestination addresses are supported.

CEE switch support


Data modelThere is no SNIA model for CEE ACLs. The DMTF DSP1039 version 1.0.0 for the Role-Based Authorization Profile to model theseACLs will be followed. All mandatory classes and properties as stated in this profile will be supported. The following detailed notesdescribe the class diagram as shown in the following figure.

• The CEE ACL policy is defined at the scope of the switch. This policy represented by an instance of Brocade_CEEACLPolicy isassociated 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 ofBrocade_CEEACLRules. The composition is through Brocade_CEEACLRulesInPolicy. There is one instance ofBrocade_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 thepolicy. Each string contains the details of the sequence number, source, destination, count, Ether Type and privilege of the rulein a specific format.

• The Brocade_CEEACLRules.QualifierFormats array contains an array of strings, each string represents the format for the rule inthe Brocade_CEEACLRules.ActivityQualifiers array at the same index.

• All the possible values for the Brocade_CEEACLRules.QualifierFormats array are published in theBrocade_CEEACLServiceCapabilities.QualifierFormatsSupported as an array of strings. The value in theBrocade_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 inwhich 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 theBrocade_CEEACLPolicyOnEthernetPort, Brocade_CEEACLPolicyOnLAG, or Brocade_CEEACLPolicyOnVLAN respectively tothe appropriate ManagedElement.

• For every Brocade_EthernetSwitch instance, there is an instance of Brocade_CEEACLService. This service provides the abilityto create, delete, modify, and assign CEE ACL policies.

• The capabilities of the service are published by a single instance of Brocade_CEEACLServiceCapabilities associated to theservice through Brocade_CEEACLServiceElementCapabilities.

• Brocade_CEEACLPolicy can be created using the Brocade_CEEACLService.CreateRole() extrinsic method. Only the inputparameters RoleTemplate and Privileges are supported. The successful execution of this method results in the creation of aninstance of Brocade_CEEACLPolicy being associated to an instance of Brocade_CEEACLRules. The path of the newly createdBrocade_CEEACLPolicy instance is returned in the output parameter Role. The Brocade_CEEACLPolicy is associated to theappropriate Brocade_EthernetSwitch instance on which it is defined. The Brocade_CEEACLPolicy instance is not associated toa port, LAG or VLAN. This is done as a separate operation.

• An existing Brocade_CEEACLPolicy instance may be modified using the Brocade_CEEACLService.ModifyRole() extrinsicmethod. The input parameters Role and Privileges are required. Refer to MOF content for details on the parameters. The callreplaces the existing Brocade_CEEACLRules instance for the Brocade_CEEACLPolicy specified in the input parameter Rolewith the instance of Brocade_CEEACLRules specified in the input parameter Privileges. Assigning to targets is not supportedduring modification. This can be done separately through the AssignRoles operation.

• An existing Brocade_CEEACLPolicy instance may be deleted using the Brocade_CEEACLService.DeleteRole() extrinsicmethod. This method deletes the instance and its associated rules.

• A Brocade_CEEACLPolicy may be applied to an Ethernet port, LAG, or VLAN using theBrocade_CEEACLService.AssignRoles() extrinsic method. Only one policy can be applied at a time on a Managed Element.

CEE switch support


FIGURE 31 CEE ACL class diagram

RegistrationBecause the DMTF DSP 1039 version 1.0.0 for Role-Based Authorization Profile to model these ACLs is being followed, conformancewill be advertised to that profile. The following figure shows the profile registration diagram.

CEE switch support


FIGURE 32 CEE ACL profile registration

CEE maps

Data modelThere is no SNIA model for CEE maps. The following notes present details on the class diagram in the following figure.

• The CEE map is defined at the scope of the switch. This map is represented by an instance of Brocade_CEEMap associated tothe 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 singleinstance of Brocade_PriorityGroups. The composition is through Brocade_ PriorityGroupsInCEEMap. There will be oneinstance 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 groupwithin the map with the exception of the last entry. The last entry will contain the priorities for the mapping of the priority groupsto the incoming Converged OS (COS). Each string representing a priority group will contain the details of the bandwidth andPriority Flow Control (PFC) in a specific format. The last string representing the priority table will contain the priority group ID forincoming CoS in a specific format.

• The Brocade_PriorityGroups.QualifierFormats array will contain an array of strings, each string representing the format for thepriority 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 theBrocade_CEEMapServiceCapabilities.QualifierFormatsSupported as an array of strings. The value in theBrocade_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 inwhich the Brocade_PriorityGroups.ActivityQualifiers and the Brocade_PriorityGroups.QualifierFormats properties will be empty.

• If a CEE map has been applied to a port, this information can be discovered by traversing theBrocade_CEEMapOnEthernetPort to the Brocade_EthernetPort instance.

• For every Brocade_EthernetSwitch instance, there will be an instance of Brocade_CEEMapService. This service will provide theability to create, delete, modify, and assign CEE maps.

• The capabilities of the service are published by a single instance of Brocade_CEEMapServiceCapabilities associated to theservice through rocade_CEEMapServiceElementCapabilities.

• Brocade_CEEMap can be created using the Brocade_CEEMapService.CreateRole() extrinsic method. Only the inputparameters RoleTemplate and Privileges are supported. The successful execution of this method results in the creation of aninstance of Brocade_CEEMap being associated to an instance of Brocade_PriorityGroups. The path of the newly createdBrocade_CEEMap instance is returned in the output parameter Role. The Brocade_CEEMap will be owned by the

CEE switch support


Brocade_EthernetSwitch instance on which it is defined. The Brocade_CEEMap instance will not be associated to any port. Thatassignment 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 theBrocade_CEEMap specified in the input parameter Role with the instance of Brocade_PriorityGroups specified in the inputparameter Privileges. Assigning to targets is not supported during modification. This can be done separately through theAssignRoles operation.

• An existing Brocade_CEEMap instance can be deleted using the Brocade_CEEMapService.DeleteRole() extrinsic method. Thismethod 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.

FIGURE 33 CEE map class diagram

CEE switch support



Brocade 8470 FCoE embedded switch supportBrocade 8470 is the Brocade CEE high speed switching module. CEE discovery and configuration support is similar to that of theBrocade 8000 and FCOE10-24 as detailed in the previous sections. There are some distinct differences in Brocade 8470. Thefollowing 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>".

• Brocade 8470 supports Layer 3 mode of operation. The external ports and LAGs can be in None, Layer 2 and Layer 3Interface 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.

NOTESupport for setting of Layer 3 mode is not needed because adding of an IP address to an ethernet port automaticallyputs 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 Layer3 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, theinternal 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.

CEE switch support


Support for Layer 3 featuresThe Brocade 8470 platform supports some of the basic Internet Protocol version 4 (IPv4) features. Management application SMI Agentsupports a subset of these as stated in this section.

Management application SMI Agent supports the configuration of IP addresses on Physical interfaces such as CEE port and LAG. Onecan assign a single primary IP address and up to 255 secondary IP addresses on a single interface. When an IP address is assigned toan interface, it becomes a Layer 3 interface.

Data modelThe following data model is supported. The following figure shows the classes and associations for discovery and configuration of IPv4addresses on CEE ports and LAGs.

CEE switch support


FIGURE 34 CEE Brocade 8470 support data model

CEE switch support


Brocade 8428 FCoE embedded switch supportBrocade 8428 is the Brocade CEE high speed switching module. CEE discovery and configuration support is similar to that of theBrocade 8000 and FCOE10-24 as detailed in the previous sections. There are some distinct differences in Brocade 8428. For moreinformation about the differences, refer to Differences from Brocade 8000 and FCoE 10-24 on page 92, Support for Layer 3 featureson page 93, and Data model on page 93.

Fabric switch partitioning subprofileThis subprofile models all Brocade switches. Every Brocade switch is partitioned into a logical Brocade_Switch and a physicalBrocade_PhysicalComputerSystem instance associated through HostedDependency. In addition, every port is partitioned into a logicalBrocade_SwitchFCPort and physical Brocade_PCSNetworkPort instance associated through CIM_HostedDependency.

Data modelThe following figure shows the fabric switch partitioning subprofile data model.

FIGURE 35 Fabric switch partitioning subprofile data model

Fabric switch partitioning subprofile


RegistrationOnly instances of Brocade_PhysicalComputerSystem that are Virtual Fabrics-enabled are associated to theBrocade_RegisteredSubProfile instance for fabric switch partitioning. The following figure shows the registration for fabric switchpartitioning subprofile.

FIGURE 36 Fabric switch partitioning profile registration

FC routingA Fibre Channel Routing (FCR) is a specific case of switch partitioning. The FC-FC routing service provides connectivity to devices indifferent fabrics without merging the fabrics. A switch running the FC-FC routing service is called a Fibre Channel Router.

Data modelThe following figure shows the FCR data model.

FC routing


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 inmulti-domain mode, has both physical and logical representation in SMIS. The FCR is represented by two instances ofCIM_ComputerSystem, a Brocade_Switch and a Brocade_PhysicalComputerSystem associated byCIM_HostedDependency(Brocade_SwitchInPCS).

• The Brocade_PhysicalComputerSystem, in addition to being associated to the BackBone Brocade_Switch instance, will also beassociated 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 domainand xlate phantom domain switches are associated by the Brocade_SANActiveConnection. These phantom switches can be

FC routing


differentiated by Brocade_Switch.OtherIdentifyingInfo property value (which would have the values as Translate Domain, FrontDomain, 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.

• Brocade_PCSServiceCapabilities has a Boolean property called FCRCapable. If the property is true, then the switch is FCRcapable and is enabled. If false, the switch is capable and not enabled. If null, the switch is not FCRcapable. In the case of VFsetup, this property is null if the base switch is not discovered.

• Each phantom switch is associated with Brocade_FCSwitchSettings and Brocade_FCSwitchCapabilities. The FCSwitchSettingshas the property called PreferredDomainID, which is a settable property. A user can set the PreferredDomainID for the phantomswitches in the FCSwitchSettings instance. If the DomainIDConfigurable is true then it would indicate that the DomainIDsettings can be modified. Modifying this property is a fabric-disruptive operation due to intrinsically disabling of all EX_Portsconnected to the respective edge fabric, modifying the domain ID of the phantom switch, and then enabling all the EX_Ports asrequired by the firmware. This applies to both the front and translate phantom domains. In addition, by modifying the translatedomain 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 instancerepresenting the FCR EX_Port in the edge fabric with the PCSNetworkPort instance representing the FCR EX_Port on the FCRlogical switch.

• There is one instance of NodeFCPort for every entry in the name server. The SystemName property reflects the Fabric WWN ofthe fabric where the port exists. In case of FCR setup, where the devices are imported or exported, there may be multipleinstances of NodeFCPort where DeviceID is the same, but SystemName differentiates each instance based on fabricmembership.

• The physical ports are represented as Brocade_PCSNetworkPort instances. In the backbone view for every physical port, thereis 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 bywriting to the NetworkIDs property of the port's settings. Modifying this property is a fabric-disruptive operation due tointrinsically 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 ofthe backbone fabric.

• If FCR setup where only one or more edge fabrics have been discovered - In the absence of the backbone, there is noknowledge that the edge fabrics belong to one FCR backbone fabric, so each edge fabric will be associated to its own SANinstance Brocade_SAN.Name which is the principal WWN of that edge fabric.

RegistrationBrocade_RegisteredProfile is mapped to Brocade_Switch using Brocade_ElementConformsToProfile association class if edge switch isdiscovered along with its backbone.

The following figure shows the SNIA Profile Registration model to advertise Inter-Fabric Routing profile.

FC routing


FIGURE 38 Fibre Channel Router registration model

Edge-to-edge device sharing (no FCIP configured in backbone)The following figure shows the instance diagram which depicts fabric discovery of the backbone and edge fabric with edge to edgedevice 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 Management application, then only instances in the BackBone Fabric view arediscovered. For edge fabric managed through Management application, refer to the Limitations on page 105 section. If both thebackbone and the edge fabrics are managed through Management application, then all instances and associations are discoverable.

FC routing


FIGURE 39 Data model for edge-to-edge device sharing

FC routing


Backbone-to-edge device sharing (no FCIP configured in backbone)• The following figure shows the data model for backbone-to-edge device sharing. If only the backbone fabric is being managed

through Management application, then only instances in the BackBone fabric view are discovered. If only the edge fabric isbeing managed through Management application, refer to the Limitations on page 105 section. If both the backbone and theedge fabrics are being managed through Management application, 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 alwaysbehind the front phantom domain switch, the backbone switch itself represents the front phantom domain. In addition to thelogical port instance on the front phantom in the edge fabric, FOS creates another instance of the logical port on the backbonelogical switch. This is the logical port instance that is connected to another logical port instance on the xlate phantom through aSANActiveConnection.

FC routing


FIGURE 40 Data model for backbone-to-edge device sharing

FC routing


Backbone-to-edge device sharing (using VEX_Port over FCIP)An FCR setup with backbone and edge fabrics encompasses the following cases:

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 aBackbone Fabric. The following figure shows the data model or backbone-to-edge device sharing for VEX over FCIP.

FC routing


FIGURE 41 Backbone-to-edge device sharing for VEX over FCIP

FC routing


Management application SMI Agent classes added for this profileThe following table explains the classes and MOF files.

TABLE 16 Classes and MOF file

Class MOF file

Brocade_PCSNetworkPortSettings BrocadePartitioning.mof

Brocade_PCSNetworkPortCapabilities BrocadePartitioning.mof

Brocade_PCSServiceCapabilities BrocadePartitioning.mof

Brocade_EthernetPort BrocadePartitioning.mof

The following table explains the associated classes and MOF files.

TABLE 17 Association classes and MOF file

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• Management application 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 Managementapplication Server. If the backbone fabric is not managed through the Management application server, discovery is limited to thetopology shown in the following figure.

• You can modify the PreferredDomainID value for phantom switches only when the associated backbone fabric is managedthrough Management application.

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 thephantom switches or for the imported devices.

• The PreferredDomainID value for phantom switches can be modified only if the associated backbone fabric is managedthrough Management application.

Brocade Access Gateway and NPIVThe Access Gateway (AG) feature allows you to configure the enterprise fabric to handle additional N_Ports instead of domains byconfiguring F_Ports to connect to the fabric as N_Ports. This increases the number of device ports that can be connected to a singlefabric. Multiple AGs can connect to the DCX enterprise-class platforms, directors, and switches.

Brocade Access Gateway and NPIV


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 beincreased without increasing the number of switches. This simplifies the configuration and management in a large fabric by reducing thenumber of domain IDs and ports.

NOTEThe SMI Agent does not support the discovery of an AG-enabled switch as a seed switch, using the extrinsic method, exceptfor the encryption switch.Node Port Initialized Virtualization (NPIV) allows a single Fibre Channel port to appear as multiple distinct ports. It provides aseparate port identification and security zoning within the fabric or each operating system image. Each operating system imagehas its own unique physical port.For additional information about Access Gateway, refer to the Access Gateway Administrator’s Guide.For additional information about NPIV, refer to the Fabric OS Administrator’s Guide.

RegistrationThe following figure 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.

Data modelThe following figure defines the data model and functions of AG and NPIV.



FIGURE 44 AG class diagram

NOTEThe 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 AGThe figure above 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 istrue.



• 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 Dedicatedrepresenting the HBA. The LogicalPortGroup instance is represented as Brocade_Node and it is associated withBrocade_Platform by Brocade_NodeInPlatform.

• All the ports in end devices are represented as Brocade_NodeFCPort and it associates with Brocade_Node byBrocade_PortInNode.

• The virtualized ports associate with real ports of the end device using the Brocade_NodeFCPortDependency association. TheBrocade_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 asBrocade_SANActiveConnection. There is a direct association between the switch and the virtualized port of the end devicesthrough Brocade_SANActiveConnection. Therefore, the number of F_Port to N_Port connections is equal to the sum ofvirtualized ports and real port of the end device.

Access Gateway Physical PackageThe Physical Package support has been provided for Access Gateways. The following figure provides the AG Physical Package modeldiagram.

FIGURE 46 AG Physical Package



Access GatewayWhen an AG-capable switch is changed to an AG, it will not act as a switch and it cannot be directly discovered through Managementapplication. The port on the switch that is connected to the AG is the F_Port, and the port on the AG that has a connection from theswitch is the N_Port. The AG is considered as a node from the switch’s perspective.

As shown in the following figure, there are two connections from Switch 1 to the AG. There are two F_Ports on switch F1 and F2connected to ports N1 and N2 of the AG. The AG is connected to three HBAs, so F_Ports F1, F2, and F3 on the AG are connected toports n1, n2, and n3 of HBA1, HBA2, and HBA3 respectively. There is an internal mapping on the AG as N1 is mapped with F1 andF2, and N2 is mapped with F3.

AG connected to a single fabric

FIGURE 47 AG mapping

HBA with virtualized ports connected to the AGThe following figure represents the Management application SMI Agent model for discovery of a host attached to the 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 Management application. For moredetails, refer to the FC HBA profile on page 70.

• If the value of Dedicated property is Gateway of Brocade_AccessGateway, it represents the AG.

• The association between the SANProtocolEndPoint of the switch and the AGSANProtocolEndPoint of the AG isBrocade_AGSANActiveConnection. The association between AGSANProtocolEndPoint of the AG and SANProtocolEndPoint



of the end device (host) is Brocade_AGSANActiveConnection. The two associations create a direct association between the theSANProtocolEndPoint of the switch and the SANProtocolEndPoint of the end device (host).

• The SANProtocolEndPoint of the switch is associated with the F_Ports of the AG byBrocade_AGSANProtocolEndPointLogicalIdentity. The F_Port of the AG is internally mapped to the N_Ports of the AG, whichis connected to the switch.



FIGURE 48 Host with the AG



AG connected to multiple fabricsThe following figure shows an AG connected to multiple fabrics .

As shown in the following figure, Fabric 1 and Fabric 2 share the AG. The N1 port of the AG is connected to Fabric 1, and the N4 port ofthe AG is connected to Fabric 2. The internal mapping on the AG is done such that N1 is mapped with F1 and F2, and N4 is mappedwith F3.

Although the AG is shared with another fabric, only one instance of AG is allowed to be associated with both fabrics. If Managementapplication SMI Agent is in direct connection with one of the fabrics connected with the shared AG, the user can see all ports of teh AG,but the topology traversal works only for that fabric alone. The user can also traverse the mapped F_Ports of the N_Ports (which isconnected to the edge fabric switch) to the end devices.

FIGURE 49 AG mapping with multiple fabrics

AG with NPIVThe following figure represents the AG with NPIV model where the switch is connected to the AG and the AG is connected to HBAs thathave one NPIV-enabled device with two virtualized ports.



FIGURE 50 AG with NPIV mapping

The following figure is the combination of the AG and NPIV data model.



FIGURE 51 AG and NPIV data model

The following figure shows a simplified instance diagram to illustrate the combination of the AG and NPIV and the Topology Viewfeatures.



FIGURE 52 AG with NPIV instance diagram

The following Management application SMI Agent classes are defined in Brocade_AccessGateway.mof:

• Brocade_AccessGateway

• Brocade_AGFCPort

• Brocade_AGFCPortStats



• Brocade_AGFCPortStatisticsCollection

• Brocade_AGFCPortRateStats

• Brocade_PortRateStatsForAGFCPort

• Brocade_PortStatsForAGFCPort

• Brocade_AGFCPortStatsInAGFCPortStatisticsCollection

• Brocade_AGFCPortStatisticsCollectionForA

• 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

LimitationsThe following are the limitations of Management application 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, andBrocade_NodeFCPortDependency will not be complete for the devices attached to the Ethernet AG.

• 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 the AG port if AG is not available in Management application.

– The SMI Agent populates this property as “Unknown” in Brocade_EthernetAccessGateway if the instance is retrievedthrough enumerateInstances.



– The correct value of this property can be obtained through the getInstance() intrinsic operation only.

• The Ethernet switch instance is not delivered if the Ethernet switch is discovered through IP Tab alone.

FRU profilesThe Fan, Power Supply, and Sensors (FRU) profiles model discovery of a switch's field-replaceable units (FRUs).

RegistrationRefer to the below figure for profile registration details.

Data modelThe following figure shows the data model with the classes and properties that supports the FRU subprofiles.

FRU profiles


FIGURE 53 FRUs data model

LimitationsFRU support for EOS switch is limited. If the mandatory properties cannot be fully populated, those instances will not be advertised asconforming to the respective profile.

NOTEThe Brocade_NumericSensor returns instances to represent the power usage value for Brocade 6505, 6510 switches, FC16-32, FC 16-48, FC 8-32E, FC8-48E software Blades, CR16-4, and CR16-8 core blades which are running on Fabric OSv7.0.1 or later.

FRU profiles


NamesVarious system objects such as a switch, switch port, device, device port, and so on are identified by a WWN. For convenience, thesesystem objects may also be assigned a user-friendly name. The user-friendly name is generally the ElementName property in theinstance. 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 principalswitch share the same WWN.

• All the detached WWN names are supported by the Brocade SMI Agent.

Data modelA new extrinsic method is defined in the Brocade_Agent class.

Names



Indications• Introduction....................................................................................................................................................................................................... 123• Alert indications...............................................................................................................................................................................................123• Life-cycle indications.................................................................................................................................................................................... 167

IntroductionIndications are explanations of events detected by the software.

The Management application SMI Agent delivers events in the form of two types of indications:

• Alert indications

• 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 (forexample, 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 overthe HTTPS port. By default, the HTTPS is enabled without mutual authentication.

Alert indicationsSupported alert indications by message ID:

FC1Triggered by one of the following actions:

• Zoning database merge was completed.

Action trigger:

– Create a zoning configuration on two switches.– Connect the two switches through an E_Port.

• Configuration was saved into persistent store.

Action trigger:

– Change the zoning configuration and save the configuration. You can also do this through the CLIs zoneadd and cfgsave.

• Configuration was disabled and now the previously active configuration is inactive. When a zone configuration is disabled andthe default zoning mode is set to NoAccess, then the zone configuration is enabled and the ConfigEnabled indication isdelivered.

Action trigger:

– Disable the zoningconfiguration. You can also do this through the CLI cfgdisable.

• Configuration changes made were committed.


Action 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

TABLE 18 FC1 properties and values

Property Value

AlertingManagedElement COP of Brocade_Fabric

AlertingElementFormat COP

AlertType Device Alert

OtherAlertType N/A

AlertSubType Database Change Completed

PerceivedSeverity 2 (Informational)

ProbableCause 123

SystemCreationClassName Brocade_Fabric

SystemName Fabric WWN

ProviderName Brocade_AlertIndication Provider

OwningEntity SNIA

Message Zone database changed for <Fabric Identity Type> <WWN>

MessageArgument Fabric, Fabric WWN

FC2Triggered by one of the following actions:

• Configuration was enabled, and now this configuration is the active configuration.

Action trigger:

– Enable the zoning configuration. You can also do this through the CLIs zonadd, cfgsave, and cfgenable.



Property Value




OtherAlertType N/A

AlertSubType Config Enabled

PerceivedSeverity 5 (Major)

ProbableCause 123




OwningEntity SNIA

Message ZoneSet <ZoneSetName> was activated for fabric <WWN>

MessageArgument ZoneSet name Fabric WWN

Alert indications


FC5Triggered by the following action:

• Change in operational status for switch.



Property Value

AlertingManagedElement COP of Brocade_Switch



OtherAlertType N/A

AlertSubType Switch modified


ProbableCause 123

SystemCreationClassName Brocade_Switch

SystemName Switch WWN


OwningEntity SNIA

Message Switch <Switch Unique Identifier> in Fabric <Fabric Name> status changed to <Switch Operational Status>

MessageArgument Switch WWN, fabric WWN, switch operational status


• For fabric merge and segmentation.



Property Value




OtherAlertType N/A

AlertSubType Fabric Merge or Fabric Segmentation

PerceivedSeverity 4 (Minor)

ProbableCause 123




OwningEntity SNIA

Message <Fabric Name> has detected a <Fabric Change>

MessageArguments Fabric WWN merge or segmentation

Alert indications



• Switch added or removed. Also, applicable in Virtual Fabrics and FCR.



Property Value




OtherAlertType N/A

AlertSubType Switch added or Switch removed

PerceivedSeverity 4 (Minor)

ProbableCause 123




OwningEntity SNIA

Message The fabric <Fabric Name> has detected switch <Switch Unique Identifier> has been <Fabric Change Type>

MessageArgument Fabric WWN, switch WWN, Added or Removed


• Fabric added or removed. Also, applicable in Virtual Fabrics.



Property Value




OtherAlertType N/A

AlertSubType Fabric added or Fabric removed


ProbableCause 123




OwningEntity SNIA

Message Fabric <Fabric Identifier> was <Change Type>FC Port <Port Identifier> in <Device Type>

MessageArguments Fabric WWN, Added or Removed

Alert indications



• Deactivate the active zone configuration through Management application or CLI or Management application SMI Agent.



Property Value



AlertType Environmental

OtherAlertType N/A

AlertSubType Config Disabled

PerceivedSeverity Informational

ProbableCause 123




OwningEntity SNIA

Message Zoning was deactivated for fabric <WWN>

MessageArgument WWN = string Fabric Principal WWN

Core6Triggered by the following action:

• Switch login was attempted.

Action trigger:Telnet to the switch.

Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=SNIA and MessageID=Core6

NOTECore6 indication is supported only for FOS switches. This indication is not delivered if SNMP registration fails. Core6indications are delivered when trackChangeset and SNMP forward options are enabled in switch.

TABLE 25 Core6 properties and values

Property Value



AlertType Security

OtherAlertType N/A

AlertSubType New Login


ProbableCause 123



Alert indications


TABLE 25 Core6 properties and values (continued)

Property Value


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


• Switch logout occurred.

Action trigger:

Exit from the Telnet session.


NOTECore6 indication is supported only for FOS switches. This indication is not delivered if SNMP registration fails. Core6indications are delivered when trackChangeset and SNMP forward options are enabled in switch.


Property Value



AlertType Security

OtherAlertType N/A

AlertSubType Logout


ProbableCause 123




OwningEntity SNIA

Message <Device Type> <Device Unique Identifier> user <User> <Login Operation>

MessageArguments Device Type = Switch; Unique Identifier = WWN; User = UserName; Login operation = logged out


• Change in operational status for port.



Property Value


Alert indications


TABLE 27 Core8 properties and values (continued)

Property Value



OtherAlertType Port Alert

AlertSubType FC Port operational status modified


ProbableCause 123




OwningEntity SNIA

Message <Device Unique Identifier> status changed to <Port Status>

MessageArguments SwitchFCPort WWN, Switch


• User login failure

Action trigger:

– Telnet to the switch and provide an incorrect password.


NOTEBRCD2 is now replaced with Core10. Core 10 indication is supported only for FOS switches. This indication is not delivered ifSNMP registration fails. Core 10 indications are delivered when trackChangeset and SNMP forward options are enabled inswitch.


Property Value



AlertType Security

OtherAlertType N/A

AlertSubType User Login Failure

PerceivedSeverity 3 (Warning)

ProbableCause 123




OwningEntity SNIA

Message <Device Type> <Device Unique Identifier> user <User> had login failure

MessageArguments Device Type = Switch; Unique Identifier = WWN; User = UserName

Alert indications


BRCD4Triggered by the following action:

• Configuration changed

Action trigger:

– Perform the CLI configdownload to the switch.

Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD4

NOTEBRCD4 Indication is a switch Alert indication and it is applicable only to FOS switches. This indication is not delivered if SNMPregistration is failed.

TABLE 29 BRCD4 properties and values

Property Value



AlertType Other

OtherAlertType Switch Alert

AlertSubType Config Change


ProbableCause 123




OwningEntity BROCADE

Message Configuration changed for Switch <WWN>

MessageArgument WWN = stringSwitch WWN


• SNMP traps were turned on to alert user login and logout attempts.

Action trigger:

– Use the trackchangesset CLI command to turn on the SNMP traps.


NOTEBRCD5 indication is supported only for FOS switches and is not delivered if SNMP registration is failed.


Property Value



AlertType Other


Alert indications


TABLE 30 BRCD5 properties and values (continued)

Property Value

AlertSubType Track Change On


ProbableCause 123





Message Alert configuration for login, logout or config updates was turned ON for Switch <WWN>



• SNMP traps turned on by Track Change On was turned off.

Action trigger:

– Use the trackchangesset CLI command to turn off the SNMP traps


NOTEBRCD6 indication is supported only for FOS switches and is not delivered if SNMP registration is failed.


Property Value



AlertType Other


AlertSubType Track Change Off


ProbableCause 123





Message Alert configuration for login, logout, orconfig updates was turned OFF for Switch <WWN>



• The element (port) identified by AlertingManagedElement is up.

Alert indications


Action trigger:

– Telnet to the switch and run the CLI portenable portnumber to enable a connected port, such as an E_Port, F_Port, orL_Port.

Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=SNIA and MessageID=BRCD7


Property Value

AlertingManagedElement COP of Brocade_SwitchFCPort


AlertType Other


AlertSubType Up


ProbableCause 123





Message Port <PortWWN> of Switch <SwitchWWN> is up

MessageArguments SwitchFCPort WWN

Switch WWN


• The element (port) identified by AlertingManagedElement is down.

Action trigger:

– Telnet to the switch and run the CLI portdisable portnumber to disable a connected port, such as an E_Port, F_Port, orL_Port.

Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=SNIA and MessageID=BRCD8


Property Value

AlertingManagedElement COP of Brocade_SwitchFCPort


AlertType Other


AlertSubType Down


ProbableCause 123




Alert indications



Property Value


Message Port <PortWWN> of Switch <SwitchWWN> is down

MessageArguments PortWWN = SwitchFCPort WWN

Switch WWN=string Switch WWN


• A single device came online.

Action trigger:

– Telnet to the switch and run the CLI portenable portnumber where the port is an F_Port.



Property Value

AlertingManagedElement COP of Brocade_Node


AlertType Other


AlertSubType Connected Port Online


ProbableCause 123





Message A single device named <WWN> came online for fabric named <FabricWWN>

MessageArguments Device WWN, Fabric WWN


• A single device went offline.

Action trigger:

– Telnet to the switch and run the CLI portdisable portnumber where the port is an F_Port.



Property Value



Alert indications



Property Value

AlertType Other


AlertSubType Connected Port Offline


ProbableCause 123





Message A single device named <WWN> went offline for fabric named <FabricWWN>



• A session (transaction) was aborted and all changes made within that transaction were discarded.

Action trigger:

– Abort zone changes using the CLI cfgabort or using the Brocade_ZoneService.SessionControl extrinsic method.



Property Value



AlertType Other

OtherAlertType Zone Alert

AlertSubType Zone session aborted


ProbableCause 123




OwningEntity Brocade

Message A zoning session was aborted for fabric named <WWN>

MessageArguments Switch WWN, port statusFabric WWN


• A change in session status occurred.


Alert indications


NOTEBRCD17 is supported only for FOS switches and is not delivered if SNMP registration is failed. BRCD17 indication isdelivered for online zone data base changes and activation or de-activation.


Property Value



AlertType Other

OtherAlertType Zone Alert

AlertSubType Session Status Changed


ProbableCause 123





Message A change in zoning session status occurred for fabric named <WWN>

MessageArgument WWN = string Fabric Principal WWN


• Registration of the managed element with the Admin Domain was completed.

Action trigger:

– Enable switch connected to HBA.


NOTEBRCD18 indication is applicable only for FOS switches. The indications is delivered only for FDMI-enabled devices.


Property Value



AlertType Other

OtherAlertType Device Alert

AlertSubType Registered


ProbableCause 123





Message A single device named <HBA Device WWN> registered with the fabric named <WWN>

Alert indications



Property Value

MessageArgument Device WWN, Fabric WWN


• Deregistration of the managed element with the Admin Domain was completed.

Action trigger:

– Disable switch connected to HBA.


NOTEBRCD19 indication is applicable only for FOS switches. The indication is delivered only for FDMI-enabled devices


Property Value



AlertType Other


AlertSubType Deregistered


ProbableCause 123





Message A single device named <HBA Device WWN> deregistered with the fabric named <WWN>



• State change occurred.

Action trigger:

– Enable or disable an E_Port or F_Port.



Property Value

AlertingManagedElement COP of Brocade_FCPort


AlertType Other

Alert indications



Property Value


AlertSubType State Changed


ProbableCause 123





Message A state change occurred for device named <PortWWN> on fabric named <WWN>

MessageArguments Port WWN, Fabric WWN


• Database changes for a fabric service were completed.

Action trigger:

– Enable or disable switch connected to HBA.



Property Value



AlertType Other


AlertSubType Database Change Completed


ProbableCause 123





Message Device database change completed for fabric named <WWN>

MessageArgument Fabric WWN


• Download of firmware to the element was initiated.

Action trigger:

– Initiate firmware download from CLI.

Alert indications



NOTEBRCD24 indication is not applicable for EOS switches.


Property Value



AlertType Other


AlertSubType Firmware download started


ProbableCause 123




OwningEntity Brocade

Message Firmware download started for switch <WWN>

MessageArguments Switch WWN


• Download of firmware was completed.


NOTEBRCD25 indication is not applicable for EOS switches.


Property Value



AlertType Other


AlertSubType Firmware download completed


ProbableCause 123





Message Firmware download completed for switch <WWN>

MessageArgument Switch WWN

Alert indications



• HA Failover has completed.

Action trigger:

– After establishing the connection to switch from Brocade SMI Agent, perform an HA failover on the switch from the CLI.


NOTEBRCD26 indication is not supported for EOS switches.


Property Value



AlertType Other

OtherAlertType HA Alert

AlertSubType Failover completed


ProbableCause 123





Message HA failover has completed for Switch <WWN>



• Account is locked out on the switch. This event occurs whenever a switch account gets locked out.

Action trigger:

– Set the lockout duration as 1 using the CLI Pasargadae --set for a user account. Attempt to telnet to the switch with awrong password for that user account.




Property Value



AlertType Security

OtherAlertType N/A

Alert indications



Property Value

AlertSubType Account locked out


ProbableCause 123





Message Account for user <username> was locked out for Switch <WWN>

MessageArguments Account User Name, Switch WWN


• New user account is added to the switch.

Action trigger:

– Add a new account using the CLI userconfig.


NOTEBRCD28 indication is not delivered for FOS switches, if SNMP registration fails.


Property Value



AlertType Security

OtherAlertType N/A

AlertSubType Account added


ProbableCause 123





Message Account for user <username> was added for Switch <WWN>

MessageArguments username = string user name

WWN = string Switch WWN


• Account was deleted on the switch.

Alert indications


Action trigger:

– Delete an existing account using the CLI userconfig.




Property Value



AlertType Security

OtherAlertType N/A

AlertSubType Account deleted


ProbableCause 123





Message Account for user <username> was deleted for Switch <WWN>




• Role has changed for the user account on the switch.

Action trigger:

– Modify the role of an existing account using the CLI userconfig.




Property Value



AlertType Security

OtherAlertType N/A

AlertSubType Account role changed


ProbableCause 123


Alert indications



Property Value




Message Account for user <username> role changed for Switch <WWN>




• Account membership has changed.

Action trigger:

– Modify the AD membership of an existing account using the CLI userconfig.




Property Value



AlertType Security

OtherAlertType N/A

AlertSubType Account membership changed.


ProbableCause 123





Message Account for user <username> membership changed for Switch <WWN>

MessageArguments Account username, Switch WWN


• Password is expiring. This indication is delivered only when the Management application SMI Agent attempts login to a fabric inwhich the login password is expiring on the seed switch.

Action trigger:

– When the password is in an expiring state, attempt to log in to the switch from the Management application SMI Agent.

Alert indications





Property Value



AlertType Security

OtherAlertType N/A

AlertSubType Password expiring


ProbableCause 123





Message Password is expiring for the Switch <WWN>



• Password has expired. This indication is delivered only when the Management application SMI Agent attempts login to a fabricin which the login password has expired on the seed switch.

Action trigger:

– Expire a password using the CLI passwdcfg --set user. Attempt client connection through the Management applicationSMI Agent with the expired password.




Property Value



AlertType Security

OtherAlertType N/A

AlertSubType Password expired


ProbableCause 123



Alert indications



Property Value



Message Password has expired for Switch <IP Address>

MessageArguments Switch IP Address


• An active connection went inactive.

Action trigger:

– After establishing the connection to the switch from the Management application SMI Agent, reboot the switch.


NOTEBRCD35 indication is supported only for FOS switches. This indications is not delivered if SNMP registration fails.


Property Value



AlertType Other

OtherAlertType Connection Alert

AlertSubType Connection deactivated


ProbableCause 123





Message An active connection for Switch <WWN> went inactive

MessageArguments WWN = string Switch WWN


• enumerateInstanceNames or enumerateInstances failed.


Alert indications


NOTEMapping of AlertingManagedElement property AlertingManagedElement for enumerateInstanceNames andenumerateInstances, path of class which is in error. For example, enumerateInstanceNames on Brocade_Fabric has this asCIMObjectPath (Brocade_Fabric, root/brocade1). In case of associatorNames, associators, referenceNames, and referencespath, they have the actual CIMObjectPath of the input.


Property Value

AlertingManagedElement Failed COP or COP without key properties.


AlertType Processing Error

OtherAlertType N/A

AlertSubType N/A


ProbableCause 49

SystemCreationClassName Brocade_ManagementServer

SystemName HostName



Message A processing error occurred for method <method name>

MessageArguments method name = enumerateInstanceNam es or associatorNames and so on.


• Multiple devices (typically within a loop) came online.


NOTETelnet to the switch and run the CLI portenable portnumber where the port is an L_Port.


Property Value



AlertType Other


AlertSubType Connected Area Online


ProbableCause 123





Message One or more devices came online for fabric named <WWN>

Alert indications



Property Value

MessageArguments Fabric WWN


• Multiple devices (typically within a loop) went offline.

Action trigger:

– Telnet to the switch and run the CLI portdisable portnumber where the port is an L_Port.



Property Value



AlertType Other


AlertSubType Connected Area Offline


ProbableCause 123





Message One or more devices went offline for fabric named <WWN>



• Blade faulted. This happens when a blade is plugged in to a system running an unsupported chassis configuration.


NOTEBRCD46 Indication is applicable only for FOS switches.


Property Value



AlertType Other

OtherAlertType Blade Alert

AlertSubType Blade Faulted

Alert indications



Property Value


ProbableCause 123





Message Blade faulted because the switch <WWN> runs under unsupported chassis-configuration



• A data value is greater than the high threshold boundary.


NOTEBRCD48 indication is supported for the Environment, Port, and E_Port Fabric Watch classes. Ignore the Fabric Watchindications for non-supported Fabric Watch classes (GBIC or SFP, Fabric, F and FL Port, SAM, Security), as they are notsupported. BRCD48 is supported in switches running Fabric OS v6.1.0 and later.


Property Value



AlertType Other Alert

OtherAlertType Fabric Watch

AlertSubType Threshold Above


ProbableCause 123





Message Fabric Watch Threshold Above

MessageArguments N/A


• A data value is less than the low threshold boundary.


Alert indications




Property Value





AlertSubType Threshold Below


ProbableCause 123





Message Fabric Watch Threshold Below



• Successful recovery from a faulty condition.




Property Value





AlertSubType Threshold In Between


ProbableCause 123





Alert indications



Property Value

Message Fabric Watch Threshold In Between



• A counter value between two sample periods has changed.




Property Value





AlertSubType Threshold Change


ProbableCause 123





Message Fabric Watch Threshold Changed



• Switch state changed.



Property Value



AlertType Other


Alert indications



Property Value

AlertSubType Switch status changed


ProbableCause 123





Message Switch <WWN> status changed to <state>

MessageArguments Switch WWN, Switch state (offline or online)


• Switch not reachable.


NOTEBRCD54 indication is delivered once the asset collection cycle is done in Management application.


Property Value



AlertType Other


AlertSubType Switch not reachable


ProbableCause 123





Message Switch <WWN> is not reachable



• Fabric ID of a logical fabric changed.


Alert indications


NOTEBRCD56 indication is supported only for FOS switches and it is not delivered if SNMP registration fails.


Property Value



AlertType Other

OtherAlertType Virtual Fabric Alert

AlertSubType VF FID Conflict


ProbableCause 123





Message FID conflict occured in Logical Switch

MessageArguments WWN = string switch WWN


• Switch status changed because of the hardware failures like fans, power supply, temp sensors.


NOTEBRCD57 indication is supported only for FOS switches. If SNMP registration fails, then BRCD57 indication is not delivered forFOS switches.


Property Value



AlertType Other

OtherAlertType FRU Alert

AlertSubType FRU Faulted


ProbableCause 123





Message Switch <WWN> status change contributing factor <FRU>

MessageArguments WWN = string Switch WWN, FRU = Power Supply, FAN, or Temperature Sensor

Alert indications



• Discovered port count is in the grace limit, and is about to exceed the licensed port count.



Property Value

AlertingManagedElement COP of Brocade_ManagementServer

AlertingElementFormat 2

AlertType 2

OtherAlertType N/A

AlertSubType About to exceed licensed port count

PerceivedSeverity 3 (Degraded or Warning)

ProbableCause 123


SystemName Management application Server host name



Message The current number of managed ports <managed port count> is about to exceed your licensed port countof <licensed port count> ports.

MessageArguments Managed port count, Port count limit


• Discovered port count exceeded the licensed port count.



Property Value

AlertingManagedElement COP of Brocade_ManagementServer

AlertingElementFormat 2

AlertType 2

OtherAlertType N/A

AlertSubType Port Count Limit Exceeded

PerceivedSeverity 6 (Critical)

ProbableCause 123


SystemName Management application Server host name



Message The current number of managed ports <managed port count> has exceeded your licensed port count of<licensed port count> ports.

Alert indications



Property Value

MessageArguments Managed port count, Port count limit


• SNMP registration failed


NOTEBRCD60 indication is supported only for FOS switches.


Property Value



AlertType Other


AlertSubType SNMP registration failed


ProbableCause 123





Message SNMP registration failed for switch <SwitchWWN>

MessageArguments WWN = string Switch WWN


• LAG successfully enabled



Property Value

AlertingManagedElement COP of Brocade_LAG


AlertType Other

OtherAlertType CEE Switch Alert

AlertSubType Config enabled


ProbableCause 123

Alert indications



Property Value

SystemCreationClassName Brocade_EthernetSwitch




Message LAG <LAG ID> enabled on EthernetSwitch <switch IP>

MessageArguments Lag ID, core switch IP


• LAG successfully disabled



Property Value



AlertType Other


AlertSubType Config disabled


ProbableCause 123





Message LAG <LAG ID> disabled on EthernetSwitch <switch IP>

MessageArguments Lag ID, core switch IP


• ACL configured on LAG



Property Value



AlertType Other


Alert indications



Property Value



ProbableCause 123





Message CEEACL Policy <ACL Policy Name> assigned to LAG <LAG ID> in EthernetSwitch <Switch IP>

MessageArguments ACL name, Lag ID, core switch IP


• ACL removed from LAG



Property Value



AlertType Other


AlertSubType Config removed


ProbableCause 123





Message CEEACL Policy <ACL Policy Name> removed from LAG <LAG ID> in EthernetSwitch <Switch IP>

MessageArguments ACL name, Lag ID, core switch IP


• TE port enabled



Property Value

AlertingManagedElement COP of Brocade_EthernetPort

Alert indications



Property Value


AlertType Other


AlertSubType Up


ProbableCause 123





Message EthernetPort <portmac> enabled on EthernetSwitch <Switch IP>

MessageArguments Port mac address, core switch IP


• TE port disabled



Property Value



AlertType Other


AlertSubType Down


ProbableCause 123





Message EthernetPort <portmac> disabled on EthernetSwitch <Switch IP>



• ACL configured on TE port


Alert indications



Property Value



AlertType Other




ProbableCause 123





Message CEEACL Policy <Policy name> assigned to EthernetPort <portmac> on EthernetSwitch <Switch ip>

MessageArguments ACL name, port MAC address, core switch IP


• ACL removed on TE port



Property Value



AlertType Other




ProbableCause 123





Message CEEACL Policy <Policy name> removed from EthernetPort <portmac> on EthernetSwitch <core switch ip>

MessageArguments ACL name, port MAC address, core switch IP


• QoS CEE map configured on TE port.


Alert indications



Property Value



AlertType Other




ProbableCause 123





Message CEEMap <Map name> assigned to EthernetPort <portmac> on EthernetSwitch <Switch IP>

MessageArguments CEE map name, port mac address, core switch IP


• QoS CEE map removed on TE port.



Property Value



AlertType Other




ProbableCause 123





Message CEEMap <Map name> removed from EthernetPort <portmac> on EthernetSwitch <Switch IP>

MessageArguments CEE map name, port mac address, core switch IP


• LLDP enabled on TE port.


Alert indications



Property Value



AlertType Other




ProbableCause 123





Message LLDP enabled on EthernetPort <portmac> on EthernetSwitch <core switch IP>



• Virtual FCoE port enabled.



Property Value

AlertingManagedElement COP of Brocade_switchFCPort


AlertType Other


AlertSubType Up


ProbableCause 123





Message Virtual FCoE Port <portWwn> enabled on EthernetSwitch <core switch IP>

MessageArguments Port WWN, core switch IP


• Virtual FCoE port disabled.


Alert indications



Property Value

AlertingManagedElement COP of Brocade_switchFCPort


AlertType Other


AlertSubType Down


ProbableCause 123





Message Virtual FCoE Port <portWWN> disabled on EthernetSwitch <core switch IP>

MessageArguments Port WWN, core switch IP


• ACL assigned to VLAN.



Property Value

AlertingManagedElement COP of Brocade_VLAN


AlertType Other




ProbableCause 123





Message CEEACL<Policy Name> assigned to VLAN<VLAN No> on EthernetSwitch <core switch IP>

MessageArguments ACL name, VLAN ID, Core switch IP


• ACL removed from VLAN.


Alert indications



Property Value



AlertType Other




ProbableCause 123





Message CEEACL<Policy Name> removed from VLAN<VLAN No> on EthernetSwitch <core switch IP>

MessageArguments ACL name, VLAN ID, Core switch IP


• VLAN member modified.



Property Value



AlertType Other


AlertSubType Config Changed


ProbableCause 123





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

Alert indications



• Fabric principal switch WWN changed.



Property Value




OtherAlertType N/A

AlertSubType Principal switch WWN changed


ProbableCause 123





Message Principal switch <WWN> changed to <WWN>

MessageArguments old principal switch WWN new principal switch WWN


• SAN zone activation error. This alert indication is delivered for each fabric failure.


NOTEThis indication is delivered only if the operation is done through Management application SMI Agent.


Property Value



AlertType Zone Alert

OtherAlertType SANZone activation failed

AlertSubType Principal switch WWN changed


ProbableCause 123





Message SANZone activation failed for fabric <WWN>

Alert indications



Property Value



• Switch resources violation.



Property Value



AlertType Device

OtherAlertType N/A

AlertSubType MAPS violation

PerceivedSeverity 3 (WARN)

ProbableCause 123





Message Condition= <Threshold Condition> Value= <Current value> RuleName= <RuleName> Category= <Category>

MessageArguments <Threshold Condition>,<Current value>, <RuleName>, SW_RESOURCES


• Switch policy status violation.



Property Value



AlertType Device

OtherAlertType N/A



ProbableCause 123



Alert indications



Property Value




MessageArguments <Threshold Condition>,<Current value>, <RuleName>, SW_RESOURCES


• Switch security violation.



Property Value



AlertType Device

OtherAlertType N/A



ProbableCause 123






MessageArguments <Threshold Condition>,<Current value>, <RuleName>, SEC_VIOLATIONS


• Flow vision violation.



Property Value

AlertingManagedElement COP of Brocade_SwitchFcport


AlertType Device

OtherAlertType N/A



Alert indications



Property Value

ProbableCause 123

SystemCreationClassName Brocade_SwitchFcport





MessageArguments <Threshold Condition>,<Current value>, <RuleName>, TRAF_PERF


• Fabric health violation.



Property Value



AlertType Device

OtherAlertType N/A



ProbableCause 123






MessageArguments <Threshold Condition>,<Current value>, <RuleName>, FABRIC_HEALTH


• SwitchFcPort level violation.



Property Value

AlertingManagedElement COP of Brocade_SwitchFcport


AlertType Device

Alert indications



Property Value

OtherAlertType N/A



ProbableCause 123

SystemCreationClassName Brocade_SwitchFcport





MessageArguments <Threshold Condition>,<Current value>, <RuleName>, PORT_HEALTH


• HA Failover state out of sync.

Action trigger:





Property Value



AlertType Other


AlertSubType Fail over out of sync


ProbableCause 123





Message HA Failover state out of sync for switch <WWN>



• HA Failover state in sync.

Alert indications


Action trigger:





Property Value



AlertType Other


AlertSubType Fail over out of sync


ProbableCause 123





Message HA Failover state in sync for switch <WWN>


NOTEFor indications from BRCD61 to BRCD76: All CEE alert indications and life-cycle indications are only applicable for FOSswitches (Brocade 8000 switch and FCOE10-24 blade) with versions from v6.4.0. To get all CEE indications, make sure thatCEE indication is enabled in the switch.

NOTEFor indications from BRC103 to BRC111: SNMP traps must be registered for the switches to receive the indication.

Life-cycle indicationsThe following table explains the supported life-cycle indications.

TABLE 94 Supported life-cycle indications

Query Indication type Notes

SELECT * FROM CIM_InstCreation WHERE SourceInstance ISABrocade_Fabric

CIM_InstCreation When new fabric is discovered

SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISABrocade_Fabric

CIM_InstDeletion When the fabric is deleted

SELECT * FROM CIM_InstModification WHERE SourceInstance ISABrocade_Switch AND SourceInstance.OperationalStatus<>PreviousInstance. OperationalStatus

CIM_InstModification The operational status of a switch changes.

SELECT * FROM CIM_InstModification WHERE SourceInstance ISACIM_FCPort AND SourceInstance.OperationalStatus<>PreviousInstance. OperationalStatus

CIM_InstModification The operational status of a switch port changes.

Life-cycle indications


TABLE 94 Supported life-cycle indications (continued)


SELECT * FROM CIM_InstModification WHERE SourceInstance ISACIM_FCPort AND SourceInstance.EnabledState<>PreviousInstance.EnabledState

CIM_InstModification The enabled state of a switch port changes, suchas when ISL is unplugged and plugged.

SELECT * FROM CIM_InstCreation WHERE SourceInstance ISASELECT * FROM CIM_InstCreation WHERE SourceInstance ISA

CIM_InstCreation Applicable for logical switch also.

SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISACIM_ComputerSystem

CIM_InstDeletion Applicable for ComputerSystem also.

SELECT * FROM CIM_InstCreation WHERE SourceInstance ISACIM_FCPort

CIM_InstCreation Port is moved from one logical switch to anotherlogical switch.

SELECT * FROM CIM_InstCreation WHERE SourceInstance ISACIM_LogicalPortGroup

CIM_InstCreation A device is added to a fabric.

SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISACIM_LogicalPortGroup

CIM_InstDeletion A device is removed from a fabric.

SELECT * FROM CIM_InstCreation WHERE SourceInstance ISACIM_LogicalModule

CIM_InstCreation When a blade is inserted or powered on in theswitch.

SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISACIM_LogicalModule

CIM_InstDeletion When a blade is removed or powered off from theswitch.

SELECT * FROM CIM_InstModification WHERE SourceInstance ISACIM_ConcreteJob AND SourceInstance.CIM_ConcreteJob::PercentComplete <>PreviousInstance.CIM_ConcreteJob::Percent

CompleteCIM_InstModification

Applicable to zoning in SessionControlWithJoband ActivateZoneSetWithJob

SELECT * FROM CIM_InstModification WHERE SourceInstance ISACIM_ConcreteJob AND ANYSourceInstance.CIM_ConcreteJob::Operation alStatus[*] = 17 ANDANY SourceInstance.CIM_ConcreteJob::Operation alStatus[*] = 2

CIM_InstModification Applicable to zoning in SessionControlWithJoband ActivateZoneSetWithJob

SELECT * FROM CIM_InstModification WHERE SourceInstance ISACIM_ConcreteJob AND ANYSourceInstance.CIM_ConcreteJob::Operation alStatus[*] = 17 ANDANY SourceInstance.CIM_ConcreteJob::Operation alStatus[*] = 6


SELECT * FROM CIM_InstModification WHERE SourceInstance ISACIM_ConcreteJob AND SourceInstance.CIM_ConcreteJob::JobState <>PreviousInstance.CIM_ConcreteJob::JobState


SELECT * FROM CIM_InstCreation WHERE SourceInstance ISACIM_ConcreteJob

CIM_InstCreation Applicable to zoning in SessionControlWithJoband ActivateZoneSetWithJob

SELECT * FROM CIM_InstModification WHERE SourceInstance ISACIM_LogicalModule AND SourceInstance.OperationalStatus<>PreviousInstance. OperationalStatus

CIM_ InstModification When a blade operational status is changed

SELECT * FROM CIM_InstCreation WHERE SourceInstance ISABrocade_FAN

CIM_InstCreation FAN is inserted to the Management applicationswitch.

SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISABrocade_FAN

CIM_InstDeletion FAN is removed from the Management applicationmanaged switch.

SELECT * FROM CIM_InstModification WHERE SourceInstance ISABrocade_FAN AND SourceInstance.OperationalStatus<>PreviousInstance. OperationalStatus

CIM_InstModification FAN operational status is changed

SELECT * FROM CIM_InstCreation WHERE SourceInstance ISABrocade_PowerSupply

CIM_InstCreation Power supply is inserted to the Managementapplication Managed switch.

SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISABrocade_PowerSupply

CIM_InstDeletion Power supply is removed from the Managementapplication Managed switch.

SELECT * FROM CIM_InstModification WHERE SourceInstance ISABrocade_PowerSupply AND SourceInstance.OperationalStatus<>PreviousInstance. OperationalStatus

CIM_InstModification Power supply operational status is changed



TABLE 94 Supported life-cycle indications (continued)


SELECT * FROM CIM_InstCreation WHERE SourceInstance ISABrocade_CEEMap

CIM_InstCreation CEEMap created

SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISABrocade_CEEMap

CIM_InstDeletion CEEMap deleted

SELECT * FROM CIM_InstCreation WHERE SourceInstance ISABrocade_CEEACLPolicy

CIM_InstCreation ACL policy created

SELECT * FROM CIM_InstModification WHERE SourceInstance ISABrocade_CEEACLRules AND SourceInstance. ActivityQualifiers<>PreviousInstance. ActivityQualifiers SELECT * FROMCIM_InstModification WHERE SourceInstance ISABrocade_CEEACLRules AND SourceInstance. QualifierFormats<>PreviousInstance.QualifierFormats

CIM_InstModification Rule add or removed in the existing ACL policy.

SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISABrocade_CEEACLPolicy

CIM_InstDeletion ACL policy deleted

SELECT * FROM CIM_InstCreation WHERE SourceInstance ISABrocade_LAG

CIM_InstCreation LAG created

SELECT * FROM CIM_InstModification WHERE SourceInstance ISABrocade_LAG ANDSourceInstance.InterfaceMode<>PreviousInstance.InterfaceMode

CIM_InstModification LAG interface mode property value is changed.

SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISABrocade_LAG

CIM_InstDeletion LAG deleted

SELECT * FROM CIM_InstCreation WHERE SourceInstance ISABrocade_VLAN

CIM_InstCreation VLAN created

SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISABrocade_VLAN

CIM_InstDeletion VLAN deleted

SELECT * FROM CIM_InstModification WHERE SourceInstance ISABrocade_prioritygroups AND SourceInstance.ActivityQualifiers <>PreviousInstance.ActivityQualifiers SELECT * FROMCIM_InstModification WHERE SourceInstance ISABrocade_prioritygroups AND SourceInstance. QualifierFormats <>PreviousInstance.QualifierFormats

CIM_InstModification Priority Group modified

NOTESensors are built in with other FRU elements; and thus InstanceCreation, InstanceDeletion, and InstanceModification indicationsare not supported. When a rule is removed from the ACL policy, indication populates only the sequence number. When PG IDis removed from CEE map, indication populates only the PG ID. In both the cases, the indication populates default values forthe other properties (priority flow control, bandwidth).




Management Application SMI Agent ErrorCodesThe following table displays the Management application SMI Agent error codes.

TABLE 95 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 Management application 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

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


TABLE 95 Error codes (continued)


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

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

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

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

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

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



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 10K Virtual Switch

60112 Unsupported EOS firmware version

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


SMI Agent Certification• Generating the certificate.............................................................................................................................................................................179• Importing the certificate...............................................................................................................................................................................183

Generating the certificateTo generate the certificate for the SMI Agent, complete the following steps.

1. Once you have created the certificate signing request, refresh the MMC tab and expand the Certificates (Local Computer)folder.

2. Select the Certificates folder under the Certificate Enrollment Requests folder.The Issued To menu displays the list of certificates with the common name that is used when you the certificate.

FIGURE 54 MMC tab


3. Right-click a common name of the certificate, and select All Tasks > Export.The Certificate Export Wizard page displays.

4. Click Next.

Generating the certificate


5. Select the Yes, export the private key option.

6. Click Next.



7. Select the Include all certificates in the certification path if possible check box by clicking the Personal Information Exchange- PKCS #12(.PFX) format from the list of formats.

8. Click Next.



9. Enter your password in the Password and Confirm password fields, and click Next.

10. Enter the destination location and click Next.

11. Click Finish to generate the certificate.

Importing the certificateTo import the certificate for the SMI Agent, complete the following steps.

1. Make sure that the "openssl" application is installed.

2. Open SMC and stop all services.

3. Go to <Management application_HOME>\cimom\server\jserver\bin folder, and copy the .Keystore file (exported private keyfile), and move the server.cer file from this folder to any other location as a backup.

4. Create a separate folder, and paste the .Keystore file into that folder.

5. Open the command window in the same location, and issue the following commands to get the certificate and the private key.

• openssl pkcs12 -in <privatekey filename> -nodes -nocerts -out key.pemo

• openssl pkcs12 -in privatekey.pfx -nokeys -out cert.pemWhile issuing the commands, enter the password that you used when you generated the certificate.

Importing the certificate


6. Issue the following command to combine the certificate and the private key.

openssl pkcs12 -export -in cert.pem -inkey key.pem -name brocadeserver -out brocadeserver.p12

After issuing this command, enter the password as SSL110sdalGHfn30, and use the same for all subsequent passwordprompts until the keystore is generated.

7. Issue the following commands to create the certificate and server file.

• Keytool.exe -importkeystore -deststorepass SSL110sdalGHfn30 -destkeystore .keystore-srckeystore brocadeserver.p12 -srcstoretype PKCS12

• keytool.exe -export -alias brocadeserver -storepass SSL110sdalGHfn30 -file server.cer-keystore .keystore

8. Copy the generated .keystore and server.cer files into <Management application_HOME>\cimom\server\jserver\bin folder.

9. Start all services from SMC.

NOTEThe values are not populated in the Configure SMI Agent > Summarytab.

10. Confirm that the SMI Agent is working with the imported certificate by an SMI Agent query.The Keytool.exe file is located in the <Management application_HOME>\jre\bin\ folder.

Importing the certificate


Documents

Brocade Network Advisor SMI Agent Developer's Guide, 14.4