HP Brocade 8/24c Developer's Manual

Brocade network advisor smi agent developer's guide v11.1.0 (53-1002169-01, may 2011).
Hide thumbs
53-1002169-01
®
13 May 2011
Brocade Network Advisor
SMI Agent
Developer's Guide
Supporting Brocade Network Advisor SMI Agent 11.1.0

Advertising

   Also See for HP Brocade 8/24c

   Related Manuals for HP Brocade 8/24c

   Summary of Contents for HP Brocade 8/24c

  • Page 1

    53-1002169-01 ® 13 May 2011 Brocade Network Advisor SMI Agent Developer’s Guide Supporting Brocade Network Advisor SMI Agent 11.1.0...

  • Page 2: Document History

    Copyright © 2010-2011 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, BigIron, DCFM, DCX, Fabric OS, FastIron, IronView, NetIron, SAN Health, ServerIron, TurboIron, and Wingspan are registered trademarks, and Brocade Assurance, Brocade NET Health, Brocade One, Extraordinary Networks, MyBrocade, VCS, and VDX are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.

  • Page 3: Table Of Contents

    Contents About This Document In this chapter ......... . . vii How this document is organized .

  • Page 4: Table Of Contents

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

  • Page 5: Table Of Contents

    CEE switch support ........56 Registration .

  • Page 6

    Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 7: About This Document, How This Document Is Organized

    About This Document In this chapter • How this document is organized ........vii •...

  • Page 8: Supported Hardware

    Supported hardware The following switches are supported by Brocade Network Advisor SMI Agent 11.1.0: • Brocade 300 • Brocade 5100 • Brocade 5300 • Brocade 5410 • Brocade 5424 • Brocade 5450 • Brocade 5460 • Brocade 5470 • Brocade 5480 •...

  • Page 9: Document Conventions

    What’s new in this document The following changes have been made since this document was last released: • Information that is added: Fabric and host discovery SAN zoning Brocade_SAN.ElementName properties • Information that is changed: Access Gateway (AG) and Node Port Initialized Virtualization (NPIV) profile Launch In Context (LIC) profile Fabric Views subprofile.

  • Page 10: Key Terms, Additional Information

    NOTE A note provides a tip, guidance, or advice, emphasizes important information, or provides a reference to related information. ATTENTION An Attention statement indicates potential damage to hardware or data. Key terms For definitions specific to Brocade and Fibre Channel, see the technical glossaries on MyBrocade. “Brocade resources”...

  • Page 11

    For additional Brocade documentation, visit the Brocade website: http://www.brocade.com Release notes are available on the MyBrocade website. Other industry resources For additional resource information, visit the Technical Committee T11 website. This website provides interface standards for high-performance and mass storage applications for Fibre Channel, storage management, and other applications: http://www.t11.org For information about the Fibre Channel industry, visit the Fibre Channel Industry Association...

  • Page 12: Document Feedback

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

  • Page 13: In This Chapter, Role-based Access Control

    Chapter Connecting to the Fabric In this chapter • Role-Based Access Control ........1 •...

  • Page 14: Admin Domains And Brocade Network Advisor Smi Agent

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

  • Page 15: Discovering A Fabric And A Host, Fabric Discovery Using Smia Extrinsic Method

    Discovering a fabric and a host Discovering a fabric and a host You can discover, edit, and delete a fabric or a host in two ways: • Using the SMIA extrinsic method • Using the SMIA Configuration Tool Fabric discovery using SMIA extrinsic method The CIMOM fabric discovery process enables the user to discover and delete fabrics through an extrinsic method implemented in the Brocade_DiscoveryService.

  • Page 16: Host Discovery Using Smia Extrinsic Method

    Discovering a fabric and a host FIGURE 1 Fabric discovery data model Host discovery using SMIA extrinsic method The CIMOM host discovery process enables the user to discover and delete hosts through an extrinsic method implemented in the Brocade_DiscoveryService. Features supported The following features are supported by the CIMOM host discovery process: •...

  • Page 17: Discovery Using Smia Configuration Tool

    Discovering a fabric and a host Data model • The Brocade_HostDiscovered class gives the discovery information of each host associated to the Discovery service. • The discovery service is hosted on the management server. Figure 2 shows the data model of the host discovery through the SMIA extrinsic method. FIGURE 2 Host discovery data model Discovery using SMIA Configuration Tool...

  • Page 18

    Discovering a fabric and a host FIGURE 3 Fabric discovery using SMIA Configuration Tool Figure 4 shows the host discovery through the SMIA Configuration Tool. Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 19

    Discovering a fabric and a host FIGURE 4 Host discovery using SMIA Configuration Tool For more information related to fabric and host discovery, refer to the Brocade Network Advisor User Manual. Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 20

    Discovering a fabric and a host Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 21: Brocade Managed Object Format Files, In This Chapter

    Chapter Managed Object Format Files In this chapter • Brocade Managed Object Format files....... 9 •...

  • Page 22: Additional Mof Description Specifications, Creating And Deleting Instances

    Additional MOF description specifications TABLE 1 Brocade Managed Object Format files (Continued) MOF filename Description BrocadePhysicalPackage.mof Location subprofile Physical Package subprofile BrocadeProfile.mof Profile Registration BrocadeSoftware.mof Software subprofile BrocadeSwitchStatistics.mof SwitchFCPort statistics BrocadeTopologyView.mof Topology view BrocadeVLAN.mof VLAN discovery and configuration BrocadeFabricDiscovery.mof Fabric discovery BrocadeZoning.mof Zone Control subprofile BrocadeSANZoning.mof...

  • Page 23: Deprecation Qualifier

    Additional MOF description specifications For example: [Provider("java:com.brocade.api.cim.provider.zoning.Brocade_ZoneSetProvider"), Description ( "Brocade_ZoneSet is a container of zones.\n\n" "Instances of this class can be deleted by a client.")] class Brocade_ZoneSet: CIM_ZoneSet { Deprecation qualifier Instance classes, association classes, properties, or extrinsic methods that have the Common Information Model (CIM) qualifier deprecated in the MOF definition will continue to be implemented in the Brocade Network Advisor SMI Agent.

  • Page 24

    Additional MOF description specifications Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 25: Uml Diagram Conventions, In This Chapter

    Chapter Profiles and Subprofiles In this chapter • UML diagram conventions ........13 •...

  • Page 26: Smi Profiles And Subprofiles

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

  • Page 27: Brocade Network Advisor Smi Agent, Server Profile

    Server profile Other features supported by Brocade Network Advisor SMI Agent The following are the additional features supported by Brocade Network Advisor SMI Agent: • Support for Fibre Channel Router (FCR), modeled through the FabricSwitchPartitioning subprofile • Names • Support for the Converged Enhanced Ethernet (CEE) switch •...

  • Page 28: Indications Subprofile

    Server profile FIGURE 6 Server profile Indications subprofile The Indications subprofile is supported by the WBEM Solutions J WBEM Server CIMOM as shown in Figure Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 29: Object Manager Adapter Subprofile, Fabric Profile, Rules Governing Brocade_san.name

    Fabric profile FIGURE 7 Indications profile Object manager adapter subprofile The object manager adapter subprofile is supported by the WBEM Solutions J WBEM Server CIMOM. Fabric profile The Brocade Network Advisor SMI Agent supports the Storage Networking Industry Association (SNIA) Fabric profile, which defines the model and functions of a storage network for topology and zoning control.

  • Page 30: Registration

    Fabric profile • Virtual fabrics with dedicated ISL between the base switches where some of virtual fabrics have been discovered but there is no base fabric. If the base fabric is discovered, Brocade_SAN.Name is the principal WWN of the base fabric.

  • Page 31: Data Model

    Fabric profile FIGURE 8 Fabric profile registration Data model Figure 9 shows the Fabric profile data model with the classes and properties that are supported to conform to the Fabric profile. Only those properties that are mandatory are considered. Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 32

    Fabric profile FIGURE 9 Fabric profile Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 33

    Fabric profile NOTE The following properties are mapped with the value specified to differentiate between Brocade_Fabric and Brocade_SAN instances. Brocade_Fabric instance: OtherIdentifyingInfo[] = {"Fabric"} IdentifyingDescriptions[] = {"SNIA:DetailedType"} Brocade_SAN instance: OtherIdentifyingInfo[] = {"SAN"} IdentifyingDescriptions[] = {"SNIA:DetailedType"} Brocade_SAN.ElementName properties The following are the properties of Brocade_SAN.ElementName: •...

  • Page 34: Zone Control And Enhanced Zone Control Subprofiles

    Fabric profile Zone control and enhanced zone control subprofiles The zone control subprofiles enable discovery of a fabric's zone database and provisioning of zoning operations. Registration Refer to “Registration” on page 18. Data model Figure 10 shows the data model with the classes and properties that are supported to conform to these subprofiles.

  • Page 35

    Fabric profile FIGURE 10 Zone control and enhanced zone control subprofiles data model Table 3 outlines the required CIM elements for the zone control subprofile. TABLE 3 CIM elements for zone control subprofile ElementName Description Currently supported Y/N? CIM_HostedService Associates the ZoneService to the Admin Domain representing the fabric.

  • Page 36

    Fabric profile Extrinsic methods The Brocade_ZoneService class contains the following extrinsic methods of the zone control subprofiles: • CreateZoneSet • CreateZone • CreateZoneAlias • CreateZoneMembershipSettingData • AddZone • AddZoneAlias • AddZoneMembershipSettingData • ActivateZoneSet • SessionControl • ActivateZoneSetWithJob • SessionControlWithJob The following method is Brocade extension: •...

  • Page 37: Activatezonesetwithjob

    Fabric profile • If a Brocade Network Advisor client first starts zoning on a fabric (opens a zoning dialog box for that fabric) and then an SMI client starts a transaction on the same fabric, a notification is sent to the Brocade Network Advisor client that another user is starting zoning operations. This is a broadcast notification to all the Brocade Network Advisor clients that currently have the zoning dialog box open to do zoning configuration on the same fabric.

  • Page 38: Zoning Behavior Details, Data Model

    Fabric profile Data model Figure 11 shows the classes and properties of the Job control subprofile. FIGURE 11 Job control subprofile for zoning Zoning behavior details • Only SessionControlWithJob on a commit operation returns a Brocade_ConcreteJob instance. Start and abort operations are not asynchronous. •...

  • Page 39: San Zoning

    Fabric profile • 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"}. •...

  • Page 40

    Fabric profile LSAN zoning configuration guidelines The following are the guidelines for configuring LSAN zones: • The LSAN zone name starts with the prefix “LSAN_”. • The LSAN zone name is case-sensitive. • The members must be identified by their port WWN because the port IDs are not unique across fabrics.

  • Page 41

    Fabric profile FIGURE 12 SAN zoning data model SAN zoning operation behavior The following are the operation behaviors of SAN zoning: • SAN zoning is available only for SAN with backbone fabrics. • Brocade_SANZoneService, Brocade_SANZoneCapabilities, and Brocade_SANZoneCollection are associated to Brocade_SAN. •...

  • Page 42

    Fabric profile • The SANZoneSupported property is added in the Brocade_SANZoneCapabilities to indicate the SAN zone support. • The Brocade_SANZoneService supports the following extrinsic methods: SANSessionControl SANSessionControlWithJob CreateSANZone AddSANZoneMembers RemoveSANZoneMembers DeleteSANZone • The CIM_ZoneService such as CreateZoneSet, CreateZone, and CreateZoneAlias are not supported in Brocade_SANZoneService.

  • Page 43

    Fabric profile NOTE The name of SAN zone must start with “LSAN_”. Otherwise, the extrinsic call returns an error code: 5 (CIM_ERR_INVALID_PARAMETER). Invalid SANZone name: <SAN Zone name>. Alert indication support The following is the alert indication support for SAN zoning: •...

  • Page 44

    Fabric profile • Create a LSAN_Zone2, add WWN of Host, Target1, Target3, and activate the same zone. As the LSAN_Zone2 has devices from fabric1, fabric2, and fabric3, the LSAN_Zone2 is activated to all the three fabrics. • Create LSAN_Zone3 with offline zone members. As the LSAN_Zone3 has only offline members, the operation is failed with error code 4 (FAILED).

  • Page 45: Fabric Virtual Fabrics Subprofile

    Fabric profile Fabric virtual fabrics subprofile The fabric virtual fabrics subprofile models the partitioning of a physical fabric into one or more logical fabrics. The physical fabric consists of one or more switches that can be partitioned. The switch in the physical fabric that can be partitioned is called the partitioning system. The resulting virtual fabric will consist of one or more switches formed from the partitioning systems.

  • Page 46: Sample Discovery Configuration

    Fabric profile FIGURE 14 Fabric virtual fabrics subprofile data model Sample discovery configuration Figure 15 shows a sample Virtual Fabrics configuration. In this configuration, there are five physical chassis. Chassis 1, Chassis 2, and Chassis 3 are physical chassis that are enabled for Virtual Fabrics and divided into logical switches.

  • Page 47

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

  • Page 48: Blades Subprofile Support

    Fabric profile • 7 SANActiveConnections corresponding to the discovered switches 2 XISLs 1 ISL 4 LISLs • Zone databases (size = 2 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.

  • Page 49: Topology View

    Fabric profile Topology view The Topology View class was introduced in SMI-S 1.3 to increase the performance and reduce the number of traversals required to discover topology. The Network Advisor SMI Agent cannot provide a complete topology and its related information including instances of classes like Brocade_TopologyView, Brocade_SanActiveConnection if one of the switches involved goes unreachable or unmanageable.

  • Page 50: Fdmi Subprofile

    Fabric profile Data model Figure 18 shows the data model of Topology view. FIGURE 18 Topology view data model FDMI subprofile The Fabric-Device Management Interface (FDMI) enables the management of devices such as Host Bus Adapters (HBAs) through the fabric. This subprofile models the discovery of HBA type devices without having the SMI Agent reside on the host containing the HBA.

  • Page 51

    Fabric profile Prerequisites Only the HBAs that register a FDMI host name in the Name Server (NS) on the switch or fabric support the Brocade_Platform model. Currently, the EOS switches do not support FDMI. Therefore, HBAs connected to EOS switches do not support the Brocade_Platform model, including the instance classes and association classes.

  • Page 52

    Fabric profile FIGURE 19 FDMI data model Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 53: Trunking

    Fabric profile Trunking This section defines the model for the trunking feature in Brocade Network Advisor SMI Agent. The trunking model is supported only for FOS switches. NOTE The m-EOS switches open trunking feature is not supported in Brocade Network Advisor SMI Agent and there will not be any modeling m-EOS open trunking.

  • Page 54

    Fabric profile Related API and classes Table 5 represents the group of switch ports forming a trunk. TABLE 5 Brocade_Trunk: CIM_RedundancySet Property name Type Description InstanceID [Key] string InstanceID opaquely and uniquely identifies an instance of this class. The format of this key is as follows. SOURCESWITCHWWN=<value>;...

  • Page 55: Switch Profile, Registration

    Switch profile Table 8 explains the properties of Brocade_AGFCPortInTrunk: CIM_ MemberOfCollection class. TABLE 8 Brocade_AGFCPortInTrunk: CIM_ MemberOfCollection Property name Type Description Collection Brocade_Trunk REF Represents the trunk object. Member Brocade_AGFCPort REF Represents the member of the trunk. Switch profile The Storage Networking Industry Association (SNIA) switch profile defines the model and functions of a fibre channel switch including state, status, and control of the device and its connections.

  • Page 56

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

  • Page 57: Location Subprofiles

    Switch profile Differentiation between switches and domains The following properties are used in CIM_CompterSystem to differentiate a simple switch, a switch created through VF, a switch created through Inter-Fabric Routing Profile (IFR), differentiating Front Domain from the Translate Domain, and the physical system that is partitioned. IdentifyingDescriptions = {"DomainID", "SNIA:DetailedType"};...

  • Page 58

    Switch profile TABLE 10 Switch subprofiles (Continued) Subprofiles Description Software Provides information on the installed controller software. Blades Models the physical aspect of a blade in a director switch. Location Models the location of a SAN Element. Registration Refer to “Registration”...

  • Page 59

    Switch profile FIGURE 23 Physical Package, Access Points, Software, Blades, and Location subprofiles data model Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 60: Cp Blades (brocade Extension), Data Model, Cp Blades (brocade Extension)

    CP blades (Brocade extension) NOTE he Brocade_Chassis.ElementName property is set correctly in the corresponding instance only if the seed switch is running on a Fabric OS v6.3.x or higher and if the chassisName in the switches of the fabric are set after the seed switch firmware has been upgraded. CP blades (Brocade extension) This section details the modelling of the Core Processor (CP) blade and its associated properties (IP address, state, and so on) on the director class Brocade switches.

  • Page 61

    CP blades (Brocade extension) FIGURE 24 CP blades instances diagram • Brocade_CPModule instances representing CP blades are not associated to Brocade_RegisteredSubProfile through Brocade_ElementConformsToSubProfile. • Each Brocade_Blade instance representing the CP blade is logically realized as Brocade_CPModule:CIMLogicalModule. A different class for this logical module is used instead of PortModule.

  • Page 62: Supported Classes And Associations, Fc Hba Profile, Prerequisites, Data Model

    FC HBA profile • The Brocade_CPModule.ModuleNumber shows the slot number of the CP blade. • The Brocade_CPModule is associated to the Brocade_PhysicalComputerSystem using Brocade_CPInPCS:CIM_SystemDevice. This association shows the containment relationship on the logical side. • Each Brocade_CPModule is associated to a Brocade_CPMgmtAccessPoint, which shows the IP address of the CP.

  • Page 63

    FC HBA profile FIGURE 25 FC HBA profile data model Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 64: Launch In Context Profile, Lic Names

    Launch In Context profile NOTE The HBA is represented by the PortController class and the serial number is the key. Launch In Context profile Brocade Network Advisor supports a number of services for network management, such as Configure Names, Historical Performance Report, Fabric Ports Report, and so on. These services are published through the Launch In Context (LIC) profile.

  • Page 65

    Launch In Context profile TABLE 11 Description of LIC names (Continued) LIC name Description Fabric_Device_TraceRoute Obtains the detailed path information for any two selected device ports. Fabric_Device_Sharing_Diagnostics Verifies whether two or more fabrics are configured to share the same devices between them. Fabric_Zoning_Configuration Configures and activates zoning for FC, LSAN, and so on.

  • Page 66: Registration And Data Model

    Launch In Context profile TABLE 11 Description of LIC names (Continued) LIC name Description Fabric_ProductStatus_Log Displays events which indicate a change in switch status for all discovered switches. Fabric_Router_Configuration Configures FC routing to connect devices in different fabrics without merging the fabrics. Enables you to connect edge fabrics to a backbone fabric.

  • Page 67

    Launch In Context profile For example, http:// <IP Address: port number>/webstart/<JNLP file name>?module=<module name>&<SSO parameters if any>&${<parameter name like “WWN”>} The corresponding entries in Brocade_LICServiceAccessPoint.ParameterName is of the following format. {<OrgName>:<SpecName>:<SpecVersion>:WWN}. You have to replace the ${WWN} part of URL. Here, orgName is Brocade; specName and specVersion are empty.

  • Page 68: Cee Switch Support, Registration, Data Model

    CEE switch support CEE switch support The Brocade CEE switch behaves as both an FC switch and an Ethernet switch. The FC capabilities are captured through the Switch profile. This is now enhanced to model the switch's Ethernet capabilities. The CEE switch is partitioned into an Ethernet Admin Domain and a Fibre Channel fabric, where the Ethernet Admin Domain does not have any contained domain association.

  • Page 69

    CEE switch support • Configuration of the virtual FCoE port is supported. It is a normal switch port instance. Each Brocade_SwitchFCPort instance representing a virtual FCoE port is associated to Brocade_SwitchFCPortSettings and Brocade_SwitchFCPortCapabilities instances (not shown Figure 27 to avoid clutter; refer to Figure 22 on page 44).

  • Page 70

    CEE switch support FIGURE 27 FCoE topology diagram Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 71: Topology Supported

    CEE switch support Topology supported The Brocade Network Advisor SMI Agent supports the following use cases. Device • A device connected to one of the eight FC ports - The Switch profile is used to model the Brocade CEE switch and its eight FC ports. For the devices connected to these eight FC ports, refer to “Data model”...

  • Page 72

    CEE switch support FIGURE 28 CEE instance diagram Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 73: Zoning Support, Configuration

    CEE switch support Zoning support Zoning is supported only on the front-end FC ports. The Brocade Network Advisor SMI Agent has the same limitations as Brocade Network Advisor. Configuration The Brocade Network Advisor SMI Agent relies on Brocade Network Advisor support to provide CEE configuration functionality.

  • Page 74

    CEE switch support Enabling or disabling CEE port The CEE port is represented by Brocade_EthernetPort. The class Brocade_EthernetPort in BrocadePartitioning.mof is updated with the following content: • A new extrinsic method RequestStateChange is inherited from the standard CIM class CIM_EnabledLogicalElement. This method should be used to disable or enable the CEE port. •...

  • Page 75: Lags

    CEE switch support Limitations The value of LLDP-DCBX for port and switch is not persisted in Brocade Network Advisor. In order to retrieve the value of this property, a call needs to be executed. As a result, populating this property for port and switch during an enumerateInstances operation is costly and will lead to a degradation in discovery timings.

  • Page 76

    CEE switch support • The capabilities of the service are represented by an instance of Brocade_LAGServiceCapabilities associated to the service through Brocade_LAGServiceElementCapabilities. The maximum number of lags that can be created on the switch and the methods supported by the service will be reported in this capabilities instance.

  • Page 77

    CEE switch support FIGURE 29 CEE LAG class diagram Registration There is no conformance to any profile, and thus no registration. Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 78: Vlans

    CEE switch support VLANs Virtual Local Area Network (VLANs) provide the capability to overlay the physical network with multiple virtual networks. VLANs allow you to isolate the network traffic between virtual networks and reduce the size of administrative and broadcast domains. A VLAN contains end stations that have a common set of requirements that are independent of physical location.

  • Page 79

    CEE switch support • Members can be removed from an existing Brocade_VLAN instance using the Brocade_VLANService.RemoveMembers() extrinsic method. Refer to BrocadeLAG.mof for details on the parameters. • An existing Brocade_VLAN instance may be deleted using the Brocade_VLANService.DeleteVLAN() extrinsic method. This method will delete the instance and its members.

  • Page 80

    CEE switch support FIGURE 30 CEE VLAN class diagram Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 81: Cee Acls

    CEE switch support Registration There is no conformance to any profile, and thus no registration. Limitations The following are the limitations of VLAN profile: • The properties are provided through the capabilities on the endpoint. • There is no support for Generic VLAN Registration Protocol (GVRP) and so the Brocade_VLANEndPointCapabilities.Dot1QTagging is false.

  • Page 82

    CEE switch support • Even though ACLs can be Layer 2-specific (MAC) or Layer 3-specific (IP), they can only be applied on the same type of interface. Because an interface can only be set to Layer 2 mode, Layer 2 ACLs and only ACLs with MAC source and destination addresses are supported. Data model There is no SNIA model for CEE ACLs.

  • Page 83

    CEE switch support • An existing Brocade_CEEACLPolicy instance may be modified using the Brocade_CEEACLService.ModifyRole() extrinsic method. The input parameters Role and Privileges are required. Refer to MOF content for details on the parameters. The call replaces the existing Brocade_CEEACLRules instance for the Brocade_CEEACLPolicy specified in the input parameter Role with the instance of Brocade_CEEACLRules specified in the input parameter Privileges.

  • Page 84: Cee Maps

    CEE switch support Registration Because the DMTF DSP 1039 version 1.0.0 for Role-Based Authorization Profile to model these ACLs is being followed, conformance will be advertised to that profile. Figure 32 shows the profile registration diagram. FIGURE 32 CEE ACL profile registration CEE maps Data model There is no SNIA model for CEE maps.

  • Page 85

    CEE switch support • If a CEE map has been applied to a port, this information can be discovered by traversing the Brocade_CEEMapOnEthernetPort to the Brocade_EthernetPort instance. • For every Brocade_EthernetSwitch instance, there will be an instance of Brocade_CEEMapService. This service will provide the ability to create, delete, modify, and assign CEE maps.

  • Page 86: Brocade 8470 Fcoe Embedded Switch Support

    CEE switch support FIGURE 33 CEE map class diagram Registration There is no conformance to any profile, and thus no registration. Brocade 8470 FCoE embedded switch support Brocade 8470 is the Brocade CEE high speed switching module. CEE discovery and configuration support is similar to that of the Brocade 8000 and FCOE10-24 as detailed in the previous sections.

  • Page 87: Support For Layer 3 Features

    CEE switch support • Brocade 8470 supports Layer 3 mode of operation. The external ports and LAGs can be in None, Layer 2 and Layer 3 Interface mode. However, the internal ports can only be in the Layer 2 Interface mode. •...

  • Page 88

    CEE switch support FIGURE 34 CEE Brocade 8470 support data model Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 89: Brocade 8428 Fcoe Embedded Switch Support, Fabric Switch Partitioning Subprofile, Data Model, Registration

    Fabric switch partitioning subprofile Brocade 8428 FCoE embedded switch support Brocade 8428 is the Brocade CEE high speed switching module. CEE discovery and configuration support is similar to that of the Brocade 8000 and FCOE10-24 as detailed in the previous sections. There are some distinct differences in Brocade 8428.

  • Page 90: Fc Routing, Data Model

    FC routing FIGURE 36 Fabric switch partitioning profile registration FC routing A Fibre Channel Router (FCR) is a specific case of switch partitioning. The FC-FC routing service provides connectivity to devices in different fabrics without merging the fabrics. A switch running the FC-FC routing service is called a Fibre Channel Router.

  • Page 91

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

  • Page 92

    FC routing • Brocade_PCSServiceCapabilities has a Boolean property called FCRCapable. If the property is true, then the switch is FCR capable and is enabled. If false, the switch is capable and not enabled. If null, the switch is not FCRcapable. •...

  • Page 93

    FC routing FIGURE 38 Fibre Channel Router registration model Edge-to-edge device sharing (no FCIP configured in backbone) Figure 39 shows the instance diagram which depicts fabric discovery of the backbone and edge fabric with edge to edge device sharing. A port on FCR configured as an EX_Port is filtered out during port discovery on the backbone for edge-to-edge device sharing.

  • Page 94

    FC routing FIGURE 39 Data model for edge-to-edge device sharing Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 95

    FC routing Backbone-to-edge device sharing (no FCIP configured in backbone) • Figure 40 shows the data model for backbone-to-edge device sharing. If only the backbone fabric is being managed through Brocade Network Advisor, then only instances in the BackBone fabric view are discovered. If only the edge fabric is being managed through Brocade Network Advisor, refer to the “Limitations”...

  • Page 96

    FC routing FIGURE 40 Data model for backbone-to-edge device sharing Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 97

    FC routing Backbone-to-edge device sharing (using VEX_Port over FCIP) An FCR setup with backbone and edge fabrics encompasses the following cases: • The backbone fabric and all edge fabrics are discovered. • Only the backbone fabric is discovered. • Only some or all of the edge fabrics are discovered. Consider two Routers R1 and R2 connected to each other by FCIP connection as VE-VEX.

  • Page 98

    FC routing FIGURE 41 Backbone-to-edge device sharing for VEX over FCIP Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 99

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

  • Page 100

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

  • Page 101: Brocade Access Gateway And Npiv, Registration

    Brocade Access Gateway and NPIV Brocade Access Gateway and NPIV Access Gateway (AG) allows you to configure the enterprise fabric to handle additional N_Ports instead of domains by configuring F_Ports to connect to the fabric as N_Ports. This increases the number of device ports that can be connected to a single fabric.

  • Page 102

    Brocade Access Gateway and NPIV Data model Figure 44 defines the data model and functions of the AG and NPIV. FIGURE 44 AG class diagram Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 103

    Brocade Access Gateway and NPIV FIGURE 45 NPIV instance diagram HBA with virtualized ports without AG Figure 45 shows the discovery of a host with a virtualized port, without AG. • Brocade_SwitchFCPort has the property NPIVEnabled. The port supports connecting NPIV devices if this property value is true.

  • Page 104: Access Gateway

    Brocade Access Gateway and NPIV • The end device is represented as the instance of Brocade_Platform. The value of the property Dedicated is Not Dedicated representing the HBA. The LogicalPortGroup instance is represented as Brocade_Node and it is associated with Brocade_Platform by Brocade_NodeInPlatform.

  • Page 105

    Brocade Access Gateway and NPIV AG connected to a single fabric HBA1 Switch 1 HBA2 HBA3 FIGURE 46 AG mapping HBA with virtualized ports connected to AG Figure 47 represents the Brocade Network Advisor SMI Agent model for discovery of a host attached to AG.

  • Page 106

    Brocade Access Gateway and NPIV FIGURE 47 Host with AG Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 107

    Brocade Access Gateway and NPIV AG connected to multiple fabrics Figure 48 explains an AG connected to multiple fabrics. As shown in Figure 48, the Fabric 1 and Fabric 2 share the AG. The N1 port of AG is connected to Fabric 1 and the N4 port of AG is connected to Fabric 2.

  • Page 108

    Brocade Access Gateway and NPIV HBA1 Switch 1 HBA2 Virtualized Ports HBA3 NPIV Device FIGURE 49 AG with NPIV mapping Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 109

    Brocade Access Gateway and NPIV FIGURE 50 AG and NPIV data model Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 110

    Brocade Access Gateway and NPIV Figure 51 shows a simplified instance diagram to illustrate the combination of the AG and NPIV, and Topology View features FIGURE 51 AG with NPIV instance diagram The following Brocade Network Advisor SMI Agent classes are defined in Brocade_AccessGateway.mof: Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 111

    Brocade Access Gateway and NPIV • Brocade_AccessGateway • Brocade_AGFCPort • 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 •...

  • Page 112: Fru Profiles, Registration, Data Model

    FRU profiles • The Ethernet switch instance is not delivered if Ethernet switch is discovered through IP Tab alone. FRU profiles The Fan, Power Supply, and Sensors (FRU) profiles model discovery of a switch's field-replaceable units (FRUs). Registration Refer to Figure 52 for profile registration details.

  • Page 113: Limitations

    FRU profiles FIGURE 52 FRUs data model Limitations FRU support for EOS switch is limited. If the mandatory properties cannot be fully populated, those instances will not be advertised as conforming to the respective profile. Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 114: Names, Data Model

    Names Names Various system objects such as a switch, switchport, device, deviceport, and so on are identified by a WWN. For convenience, these system objects may also be assigned a user-friendly name. The user-friendly name is generally the ElementName property in the instance. This feature provides the ability to easily discover the user-friendly names for all the system objects.

  • Page 115: Introduction, In This Chapter, Alert Indications

    Chapter Indications In this chapter • Introduction ..........103 •...

  • Page 116

    Alert indications TABLE 14 Supported alert indications Message ID Trigger Property Value One of the following: AlertingManagedElement COP of Brocade_Fabric • Zoning database merge was AlertingElementFormat completed. How to trigger: Create a zoning AlertType Device Alert configuration on two switches. Connect OtherAlertType the two switches through an E_Port.

  • Page 117

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value Configuration was enabled, and now this AlertingManagedElement COP of Brocade_Fabric configuration is the active configuration. AlertingElementFormat Query: SELECT * FROM CIM_AlertIndication WHERE AlertType Device Alert OwningEntity=SNIA and MessageID=FC2 OtherAlertType How to trigger: Enable the zoning configuration.

  • Page 118

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value For fabric merge and segmentation. AlertingManagedElement COP of Brocade_Fabric Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=SNIA and MessageID=FC6 AlertType Device Alert OtherAlertType AlertSubType Fabric Merge or Fabric Segmentation PerceivedSeverity 4 (Minor)

  • Page 119

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value Fabric added or removed. Also, applicable AlertingManagedElement COP of Brocade_Fabric in Virtual Fabrics. AlertingElementFormat Query: SELECT * FROM CIM_AlertIndication WHERE AlertType Device Alert OwningEntity=SNIA and MessageID=FC8 OtherAlertType AlertSubType Fabric added or Fabric removed...

  • Page 120

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value Core6 Switch login was attempted. AlertingManagedElement COP of Brocade_Switch Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=SNIA and AlertType Security MessageID=Core6 OtherAlertType How to trigger: Telnet to the switch. AlertSubType New Login NOTE: Core6 indication is supported only...

  • Page 121

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value Core6 Switch logout occured. AlertingManagedElement COP of Brocade_Switch Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=SNIA and AlertType Security MessageID=Core6 OtherAlertType How to trigger: Exit from the Telnet session.

  • Page 122

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value Core8 Change in operational status for port. AlertingManagedElement COP of Brocade_SwitchFCPort Query: SELECT * FROM CIM_AlertIndication WHERE AlertingElementFormat OwningEntity=SNIA and MessageID=Core8 AlertType Device Alert OtherAlertType Port Alert AlertSubType FC Port operational status modified...

  • Page 123

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD4 Configuration changed AlertingManagedElement COP of Brocade_Switch Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=BROCADE and AlertType Other MessageID=BRCD4 OtherAlertType Switch Alert How to trigger: Perform the CLI configdownload to the switch.

  • Page 124

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRDC6 SNMP traps turned on by Track Change AlertingManagedElement COP of Brocade_Switch On was turned off. AlertingElementFormat Query: SELECT * FROM CIM_AlertIndication WHERE AlertType Other OwningEntity=BROCADE and OtherAlertType Switch Alert MessageID=BRCD6...

  • Page 125

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD8 The element (port) identified by AlertingManagedElement COP of AlertingManagedElement is down. Brocade_SwitchFCPort Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=SNIA and AlertType Other MessageID=BRCD8 OtherAlertType Port Alert How to trigger: Telnet to the switch and run the CLI portdisable portnumber to AlertSubType...

  • Page 126

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD13 A single device went offline. AlertingManagedElement COP of Brocade_Node Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=BROCADE and AlertType Other MessageID=BRCD13 OtherAlertType Port Alert How to trigger: Telnet to the switch and run the CLI portdisable portnumber AlertSubType Connected Port Offline...

  • Page 127

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD17 A change in session status occurred. AlertingManagedElement COP of Brocade_Fabric Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=BROCADE and AlertType Other MessageID=BRCD17 OtherAlertType Zone Alert NOTE: BRCD17 iis supported only for AlertSubType Session Status Changed FOS switches and is not delivered...

  • Page 128

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD19 Deregistration of the managed element AlertingManagedElement COP of Brocade_Node with the Admin Domain was completed. AlertingElementFormat Query: SELECT * FROM CIM_AlertIndication WHERE AlertType Other OwningEntity=BROCADE and OtherAlertType Device Alert MessageID=BRCD19...

  • Page 129

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD21 Database changes for a fabric service AlertingManagedElement COP of Brocade_Node were completed. AlertingElementFormat Query: SELECT * FROM CIM_AlertIndication WHERE AlertType Other OwningEntity=BROCADE and OtherAlertType Device Alert MessageID=BRCD21 How to trigger: Enable or disable switch AlertSubType...

  • Page 130

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD25 Download of firmware was completed. AlertingManagedElement COP of Brocade_Switch Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=BROCADE and AlertType Other MessageID=BRCD25 OtherAlertType Switch Alert NOTE: BRCD25 indication is not AlertSubType Firmware download applicable for EOS switches.

  • Page 131

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD27 Account is locked out on the switch. This AlertingManagedElement COP of Brocade_Switch event occurs whenever a switch account AlertingElementFormat gets locked out. Query: SELECT * FROM AlertType Security CIM_AlertIndication WHERE...

  • Page 132

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD29 Account was deleted on the switch. AlertingManagedElement COP of Brocade_Switch Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=BROCADE and AlertType Security MessageID=BRCD29 OtherAlertType How to trigger: Delete an existing account using the CLI userconfig.

  • Page 133

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD31 Account membership has changed. AlertingManagedElement COP of Brocade_Switch Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=BROCADE and AlertType Security MessageID=BRCD31 OtherAlertType How to trigger: Modify the AD membership of an existing account using AlertSubType Account membership...

  • Page 134

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD33 Password has expired. This indication is AlertingManagedElement COP of Brocade_Switch delivered only when the Brocade Network AlertingElementFormat Advisor SMI Agent attempts login to a fabric in which the login password has AlertType Security expired on the seed switch.

  • Page 135

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD42 enumerateInstanceNames or AlertingManagedElement Failed COP or COP enumerateInstances failed. without key properties. Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=BROCADE and AlertType Processing Error MessageID=BRCD42 OtherAlertType NOTE: Mapping of AlertSubType AlertingManagedElement...

  • Page 136

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD44 Multiple devices (typically within a loop) AlertingManagedElement COP of Brocade_Node went offline. AlertingElementFormat Query: SELECT * FROM CIM_AlertIndication WHERE AlertType Other OwningEntity=BROCADE and OtherAlertType Port Alert MessageID=BRCD44 How to trigger: Telnet to the switch and AlertSubType...

  • Page 137

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD48 A data value is greater than the high AlertingManagedElement COP of Brocade_Switch threshold boundary. AlertingElementFormat Query: SELECT * FROM CIM_AlertIndication WHERE AlertType Other Alert OwningEntity=BROCADE and OtherAlertType Fabric Watch MessageID=BRCD48...

  • Page 138

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD51 Successful recovery from a faulty AlertingManagedElement COP of Brocade_Switch condition. AlertingElementFormat Query: SELECT * FROM CIM_AlertIndication WHERE AlertType Other Alert OwningEntity=BROCADE and OtherAlertType Fabric Watch MessageID=BRCD51 AlertSubType Threshold In Between NOTE: BRCD51 indication is supported...

  • Page 139

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD53 Switch state changed. AlertingManagedElement COP of Brocade_Switch Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=BROCADE and AlertType Other MessageID=BRCD53 OtherAlertType Switch Alert AlertSubType Switch status changed PerceivedSeverity 2 (Informational) ProbableCause...

  • Page 140

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD56 Fabric ID of a logical fabric changed. AlertingManagedElement COP of Brocade_Fabric Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=BROCADE and AlertType Other MessageID=BRCD56 OtherAlertType Virtual Fabric Alert NOTE: BRCD56 indication is supported AlertSubType VF FID Conflict...

  • Page 141

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD58 Discovered port count is in the grace AlertingManagedElement COP of limit, and is about to exceed the licensed Brocade_ManagementS port count. erver Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=BROCADE and...

  • Page 142

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD59 Discovered port count exceeded the AlertingManagedElement COP of licensed port count. Brocade_ManagementS erver Query: SELECT * FROM CIM_AlertIndication WHERE AlertingElementFormat OwningEntity=BROCADE and MessageID=BRCD59 AlertType OtherAlertType AlertSubType Port Count Limit Exceeded PerceivedSeverity...

  • Page 143

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD61 LAG successfully enabled AlertingManagedElement COP of Brocade_LAG Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=BROCADE and AlertType Other MessageID=BRCD61 OtherAlertType CEE Switch Alert AlertSubType Config enabled PerceivedSeverity 2 (Informational) ProbableCause...

  • Page 144

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD63 ACL configured on LAG AlertingManagedElement COP of Brocade_LAG Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=BROCADE and AlertType Other MessageID=BRCD63 OtherAlertType CEE Switch Alert AlertSubType Config enabled PerceivedSeverity 2 (Informational) ProbableCause...

  • Page 145

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD65 TE port enabled AlertingManagedElement COP of Brocade_ EthernetPort Query: SELECT * FROM CIM_AlertIndication WHERE AlertingElementFormat OwningEntity=BROCADE and MessageID=BRCD65 AlertType Other OtherAlertType Port Alert AlertSubType PerceivedSeverity 2 (Informational) ProbableCause SystemCreationClassName Brocade_...

  • Page 146

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD67 ACL configured on TE port AlertingManagedElement COP of Brocade_ EthernetPort Query: SELECT * FROM CIM_AlertIndication WHERE AlertingElementFormat OwningEntity=BROCADE and MessageID=BRCD67 AlertType Other OtherAlertType Port Alert AlertSubType Config enabled PerceivedSeverity 2 (Informational)

  • Page 147

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD68 ACL removed on TE port AlertingManagedElement COP of Brocade_ EthernetPort Query: SELECT * FROM CIM_AlertIndication WHERE AlertingElementFormat OwningEntity=BROCADE and MessageID=BRCD68 AlertType Other OtherAlertType Port Alert AlertSubType Config removed PerceivedSeverity 2 (Informational)

  • Page 148

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD69 QoS CEE map configured on TE port. AlertingManagedElement COP of Brocade_ EthernetPort Query: SELECT * FROM CIM_AlertIndication WHERE AlertingElementFormat OwningEntity=BROCADE and MessageID=BRCD69 AlertType Other OtherAlertType Port Alert AlertSubType Config enabled PerceivedSeverity...

  • Page 149

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD70 QoS CEE map removed on TE port. AlertingManagedElement COP of Brocade_ EthernetPort Query: SELECT * FROM CIM_AlertIndication WHERE AlertingElementFormat OwningEntity=BROCADE and MessageID=BRCD70 AlertType Other OtherAlertType Port Alert AlertSubType Config removed PerceivedSeverity...

  • Page 150

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD71 LLDP enabled on TE port. AlertingManagedElement COP of Brocade_ EthernetPort Query: SELECT * FROM CIM_AlertIndication WHERE AlertingElementFormat OwningEntity=BROCADE and MessageID=BRCD71 AlertType Other OtherAlertType Port Alert AlertSubType Config enabled PerceivedSeverity 2 (Informational)l...

  • Page 151

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD73 Virtual FCoE port disabled. AlertingManagedElement COP of Brocade_ switchFCPort Query: SELECT * FROM CIM_AlertIndication WHERE AlertingElementFormat OwningEntity=BROCADE and MessageID=BRCD73 AlertType Other OtherAlertType Port Alert AlertSubType Down PerceivedSeverity 2 (Informational) ProbableCause...

  • Page 152

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD75 ACL removed from VLAN. AlertingManagedElement COP of Brocade_VLAN Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=BROCADE and AlertType Other MessageID=BRCD75 OtherAlertType CEE Switch Alert AlertSubType Config removed PerceivedSeverity 2 (Informational) ProbableCause...

  • Page 153

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD76 VLAN member modified. AlertingManagedElement COP of Brocade_VLAN Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=BROCADE and AlertType Other MessageID=BRCD76 OtherAlertType CEE Switch Alert AlertSubType Config Changed PerceivedSeverity 2 (Informational) ProbableCause...

  • Page 154

    Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD101 Fabric principal switch WWN changed. AlertingManagedElement COP of Brocade_Fabric Query: SELECT * FROM AlertingElementFormat CIM_AlertIndication WHERE OwningEntity=BROCADE and AlertType Device Alert MessageID=BRCD101 OtherAlertType AlertSubType Principal switch WWN changed PerceivedSeverity 2 (Informational)

  • Page 155: Life-cycle Indications

    Life-cycle indications Life-cycle indications Table 15 explains the supported life-cycle indications. TABLE 15 Supported life-cycle indications Query Indication type Notes SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_InstCreation When new fabric is discovered Brocade_Fabric SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_InstDeletion When the fabric is deleted Brocade_Fabric...

  • Page 156

    Life-cycle indications TABLE 15 Supported life-cycle indications (Continued) Query Indication type Notes SELECT * FROM CIM_InstModification WHERE SourceInstance CIM_InstModification Applicable to zoning in ISA CIM_ConcreteJob AND SessionControlWithJob and SourceInstance.CIM_ConcreteJob::JobState <> ActivateZoneSetWithJob PreviousInstance.CIM_ConcreteJob::JobState SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_InstCreation Applicable to zoning in CIM_ConcreteJob SessionControlWithJob and...

  • Page 157

    Life-cycle indications TABLE 15 Supported life-cycle indications (Continued) Query Indication type Notes SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA CIM_InstCreation VLAN created Brocade_VLAN SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA CIM_InstDeletion VLAN deleted Brocade_VLAN SELECT * FROM CIM_InstModification WHERE SourceInstance CIM_InstModification Priority Group modified ISA Brocade_prioritygroups AND...

  • Page 158

    Life-cycle indications Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

  • Page 159

    Appendix Brocade Network Advisor SMI Agent Error Codes Table 16 lists the Brocade Network Advisor SMI Agent error codes. TABLE 16 Error codes Error code Description 4096 Concrete job is started 4099 Concrete job is already running in the fabric 10001 Database error 10002...

  • Page 160

    Brocade Network Advisor SMI Agent Error Codes TABLE 16 Error codes (Continued) Error code Description 13401 Switch port CAL Error 13402 SwitchFCPort CAL call error 13403 Switch port CAL connection error 13404 SwitchFCPort MPI request failed 13405 Invalid credential for CAL call 13407 SwitchFCPort rate statistics failed 13408...

  • Page 161

    Brocade Network Advisor SMI Agent Error Codes TABLE 16 Error codes (Continued) Error code Description 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...

  • Page 162

    Brocade Network Advisor SMI Agent Error Codes TABLE 16 Error codes (Continued) Error code Description 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...

  • Page 163

    Brocade Network Advisor SMI Agent Error Codes TABLE 16 Error codes (Continued) Error code Description 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...

  • Page 164

    Brocade Network Advisor SMI Agent Error Codes TABLE 16 Error codes (Continued) Error code Description 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...

  • Page 165

    Brocade Network Advisor SMI Agent Error Codes TABLE 16 Error codes (Continued) Error code Description 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...

  • Page 166

    Brocade Network Advisor SMI Agent Error Codes TABLE 16 Error codes (Continued) Error code Description 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...

  • Page 167

    Brocade Network Advisor SMI Agent Error Codes TABLE 16 Error codes (Continued) Error code Description 60115 Seed switch is not supported 60116 Partially discovered 70001 Request add pending 70002 Request edit pending 70003 Request delete pending 70004 Request internal error 70005 JSON connection failed 70006...

  • Page 168

    Brocade Network Advisor SMI Agent Error Codes Brocade Network Advisor SMI Agent Developer’s Guide 53-1002169-01...

This manual also for:

Brocade bladesystem 4/24

Comments to this Manuals

Symbols: 0
Latest comments: