53-1003159-01 11 July 2014 Brocade Network Advisor SMI Agent Developer’s Guide Supporting Network Advisor SMI Agent 12.3.
© 2014, Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and the On-Demand Data Center are trademarks of Brocade Communications Systems, Inc., in the United States and in other countries. Other brands and product names mentioned may be trademarks of others.
Title Publication number Summary of changes Date Brocade Network Advisor SMI Agent Developer’s Guide 53-1002996-01 Updated to support Release 12.1.0. July 2013 Brocade Network Advisor SMI Agent Developer’s Guide 53-1003061-01 Updated to support Release 12.2.0. February 2014 Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01 Updated to support Release 12.3.
Contents About This Document How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Supported hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 3 Profiles and Subprofiles UML diagram conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 SMI profiles and subprofiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Other features supported by Brocade Network Advisor SMI Agent . . . . . . . . . . . . . . . . . . . . . 15 Server profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Indications subprofile . . . . . . . . . . . . . . . . . . . . . . . . . .
CEE switch support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Data model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Topology supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Zoning support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Configuration . . . . . . . .
viii Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
About This Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix • Supported hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii • Notice to the reader . . . . . . .
Supported hardware The following switches are supported by Brocade Network Advisor SMI Agent 12.3.
• • • • Brocade DCX Brocade DCX-4S Brocade DCX 8510-8 Backbone (8-slot) Brocade DCX 8510-4 Backbone (4-slot) The following blades are supported on the Brocade DCX and DCX-4S switches: • • • • • • • • • • • FR4-18i Blade FX8-24 Blade FC10-6 Blade FC8-16 port blade FC8-32 port blade FC8-48 port blade FC8-64 port blade FC16-64 port blade FCOE10-24 DCX Blade FS8-18 Encryption Blade FX8-24 DCX Extension Blade The following blades are supported on the Brocade DCX 8510-8 Backbone (8-slot) and Brocade DCX 8510
Document conventions This section describes text formatting conventions and important notice formats used in this document.
Notice to the reader This document may contain references to the trademarks of the following corporations. These trademarks are the properties of their respective companies and corporations. These references are made for informational purpose only. Corporation Referenced trademarks and products Microsoft Corporation Windows, Windows NT, Internet Explorer Red Hat, Inc.
Getting technical help Contact your switch support supplier for hardware, firmware, and software support, including product repairs and part ordering. To expedite your call, have the following information available: 1.
Document feedback Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. Forward your feedback to: documentation@brocade.com Provide the title and version number of the document and as much detail as possible about your comment, including the topic heading and page number and your suggestions for improvement.
xvi Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
Chapterc 1 Connecting to the Fabric In this chapter • Role-Based Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Admin Domains and Brocade Network Advisor SMI Agent. . . . . . . . . . . . . . . • Connecting to the Brocade Network Advisor SMI Agent . . . . . . . . . . . . . . . . . • Discovering a fabric and a host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Admin Domains and Brocade Network Advisor SMI Agent Admin Domains and Brocade Network Advisor SMI Agent The Brocade Network Advisor SMI Agent does not support Admin Domains though they are supported in Brocade Network Advisor. It is recommended to exclude fabrics containing Admin Domains using the Resource Grouping option in the user dialog box that can be launched from the Configuration Tool.
Discovering a fabric and a host 1 Discovering a fabric and a host You can discover, edit, and delete a fabric or a host in two ways: • Using the SMIA extrinsic method • Using the SMIA Configuration Tool Fabric discovery using SMIA extrinsic method The CIMOM fabric discovery process enables the user to discover and delete fabrics through an extrinsic method implemented in the Brocade_DiscoveryService.
1 Discovering a fabric and a host FIGURE 1 Fabric discovery data model Host discovery using SMIA extrinsic method The CIMOM host discovery process enables the user to discover and delete hosts through an extrinsic method implemented in the Brocade_DiscoveryService. Features supported The following features are supported by the CIMOM host discovery process: • Option to discover all types of hosts supported by Brocade Network Advisor. • Option to delete a host based on the HostDiscovered COP provided.
Discovering a fabric and a host 1 Data model • The Brocade_HostDiscovered class gives the discovery information of each host associated to the Discovery service. • The discovery service is hosted on the management server. Figure 2 shows the data model of the host discovery through the SMIA extrinsic method. FIGURE 2 Host discovery data model Discovery using SMIA Configuration Tool The fabric and host can be discovered, edited, and deleted using the SMIA Configuration Tool.
1 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.
Discovering a fabric and a host 1 F 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.
1 8 Discovering a fabric and a host Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
Chapter 2 Managed Object Format Files In this chapter • Brocade Managed Object Format files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 • Additional MOF description specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Brocade Managed Object Format files Brocade supplies Managed Object Format (MOF) files for managing Brocade objects. The following top-level files load MOF files into specific namespaces: • BrocadeNamespace.
2 Additional MOF description specifications TABLE 1 Brocade Managed Object Format files (Continued) MOF filename Description BrocadeLaunchInContext.mof Launch In Context profile BrocadePartitioning.mof FabricVirtualFabrics subprofile FCR subprofile BrocadePhysicalPackage.mof Location subprofile Physical Package subprofile BrocadeProfile.mof Profile Registration BrocadeSoftware.mof Software subprofile BrocadeSwitchStatistics.mof SwitchFCPort statistics BrocadeTopologyView.
Additional MOF description specifications 2 For example: [Provider("java:com.brocade.api.cim.provider.zoning.Brocade_ZoneSetProvider"), Description ( "Brocade_ZoneSet is a container of zones.\n\n" "Instances of this class can be deleted by a client.
2 12 Additional MOF description specifications Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
Chapter Profiles and Subprofiles 3 In this chapter • UML diagram conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 • SMI profiles and subprofiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 • Server profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 • Fabric profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 SMI profiles and subprofiles SMI profiles and subprofiles Table 2 lists the features supported by the Brocade Network Advisor SMI Agent. All SMI-S profiles and subprofiles conforms to SMI-S 1.4. Other profiles and subprofiles are vendor extensions. TABLE 2 SMI profiles and subprofiles Profile Subprofile SMI-S version Server Indications 1.4 Profile Registration 1.0.0 Object Manager Adapter 1.4 Fabric Profile 1.4 Zone Control 1.4 Enhanced Zoning and Enhanced Zoning Control 1.4 FDMI 1.
Server profile 3 Other features supported by Brocade Network Advisor SMI Agent The following are the additional features supported by Brocade Network Advisor SMI Agent: • Support for Fibre Channel Router (FCR), modeled through the FabricSwitchPartitioning subprofile • • • • • • Names Support for the Converged Enhanced Ethernet (CEE) switch Support for Zoning Session operations through Job Control Support for selected indications SAN zoning Support for fabric discovery and host discovery Server profile
3 Server profile FIGURE 6 Server profile Indications subprofile The Indications subprofile is supported by the WBEM Solutions J WBEM Server CIMOM as shown in Figure 7.
Fabric profile FIGURE 7 3 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.
3 Fabric profile • In virtual fabrics with dedicated ISL between the base switches where some of virtual fabrics have been discovered but there is no base fabric. - If the base fabric is discovered, Brocade_SAN.Name is the principal WWN of the base fabric. - If the base fabric is not discovered, the virtual fabrics will be disjointed and in each fabric one SAN instance will be generated.
Fabric profile FIGURE 8 3 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.
3 Fabric profile FIGURE 9 20 Fabric profile Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
Fabric profile 3 NOTE The following properties are mapped with the value specified to differentiate between Brocade_Fabric and Brocade_SAN instances. Brocade_Fabric instance: OtherIdentifyingInfo[] = {"Fabric"} IdentifyingDescriptions[] = {"SNIA:DetailedType"} Brocade_SAN instance: OtherIdentifyingInfo[] = {"SAN"} IdentifyingDescriptions[] = {"SNIA:DetailedType"} NOTE The SwitchId property will be populated only for switches running FOS 7.1.0 onwards. Brocade_SAN.
3 Fabric profile • The SAN element name is reset to the default value when the principal switch WWN is changed during fabric merge or segmentation. - For example, assume there are two switch fabrics where switch1 is the seed switch and switch2 is the principal switch, and SAN Element name is configured. If a switch3 joins the fabric as a principal switch, then the element name changes to switch3 WWN and the configured name is lost.
Fabric profile FIGURE 10 3 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. Yes CIM_ZoneService The service that allows for all of the zoning configuration changes.
3 Fabric profile Extrinsic methods The Brocade_ZoneService class contains the following extrinsic methods of the zone control subprofiles: • • • • • • • • • • • CreateZoneSet CreateZone CreateZoneAlias CreateZoneMembershipSettingData AddZone AddZoneAlias AddZoneMembershipSettingData ActivateZoneSet SessionControl ActivateZoneSetWithJob SessionControlWithJob The following method is Brocade extension: • ClearZoneDB Zoning operation behavior The Brocade Network Advisor SMI Agent depends on Brocade Netwo
Fabric profile 3 • If a Brocade Network Advisor client first starts zoning on a fabric (opens a zoning dialog box for that fabric) and then an SMI client starts a transaction on the same fabric, a notification is sent to the Brocade Network Advisor client that another user is starting zoning operations. This is a broadcast notification to all the Brocade Network Advisor clients that currently have the zoning dialog box open to do zoning configuration on the same fabric.
3 Fabric profile Data model Figure 11 shows the classes and properties of the Job control subprofile. FIGURE 11 Job control subprofile for zoning Zoning behavior details • Only SessionControlWithJob on a commit operation returns a Brocade_ConcreteJob instance. Start and abort operations are not asynchronous. • For SessionControlWithJob and ActivateZoneSetWithJob, the affected ManagedElement is the Brocade_ZoneService whose SessionState and checksums are affected.
Fabric profile 3 • A second job for the same operation and same target cannot be started if a job is already in progress and in the running state. • A failed job shows an OperationalStatus of {"6", "17"}, while a successful job shows {"2", "17"}. • Although the GetError() method is mandatory, this operation is not supported. • Upon Brocade Network Advisor server restart, all existing Brocade_ConcreteJob instances are deleted because they are not persisted in the Brocade Network Advisor database.
3 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. • The names and membership of the same LSAN zone in various fabrics need to be the same while the order of membership is not necessary.
Fabric profile FIGURE 12 3 SAN zoning data model SAN zoning operation behavior The following are the operation behaviors of SAN zoning: • SAN zoning is available only for SAN with backbone fabrics. • Brocade_SANZoneService, Brocade_SANZoneCapabilities, and Brocade_SANZoneCollection are associated to Brocade_SAN. • The Brocade_SANZoneCapabilities supports only the mandatory properties such as InstanceID, ZoneNameMaxLen, ZoneNameFormat, and SupportedConnectivityMemberTypes.
3 Fabric profile • The SANZoneSupported property is added in the Brocade_SANZoneCapabilities to indicate the SAN zone support. • The Brocade_SANZoneService supports the following extrinsic methods: - SANSessionControl - SANSessionControlWithJob - CreateSANZone - AddSANZoneMembers - RemoveSANZoneMembers - DeleteSANZone • The CIM_ZoneService such as CreateZoneSet, CreateZone, and CreateZoneAlias are not supported in Brocade_SANZoneService.
Fabric profile 3 NOTE The name of SAN zone must start with “LSAN_”. Otherwise, the extrinsic call returns an error code: 5 (CIM_ERR_INVALID_PARAMETER). Invalid SANZone name: . Alert indication support The following is the alert indication support for SAN zoning: • Alert indication with message ID BRCD102 is delivered to CIM client, if there is a failure in SAN zone activation through CIM client.
3 Fabric profile • Create a LSAN_Zone2, add WWN of Host, Target1, Target3, and activate the same zone. As the LSAN_Zone2 has devices from fabric1, fabric2, and fabric3, the LSAN_Zone2 is activated to all the three fabrics. • Create LSAN_Zone3 with offline zone members. As the LSAN_Zone3 has only offline members, the operation is failed with error code 4 (FAILED). • Create LSAN_Zone4, add host, and offline members and activate the same zone. It is activated in fabric1 as the host belongs to fabric1.
Fabric profile 3 Fabric virtual fabrics subprofile The fabric virtual fabrics subprofile models the partitioning of a physical fabric into one or more logical fabrics. The physical fabric consists of one or more switches that can be partitioned. The switch in the physical fabric that can be partitioned is called the partitioning system. The resulting virtual fabric will consist of one or more switches formed from the partitioning systems.
3 Fabric profile FIGURE 14 Fabric virtual fabrics subprofile data model Sample discovery configuration Figure 15 shows a sample Virtual Fabrics configuration. In this configuration, there are five physical chassis. Chassis 1, Chassis 2, and Chassis 3 are physical chassis that are enabled for Virtual Fabrics and divided into logical switches. Switch A and Switch B are single-switch chassis and are not enabled for Virtual Fabrics.
Fabric profile FIGURE 15 3 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.
3 Fabric profile • 7 SANActiveConnections corresponding to the discovered switches - 2 XISLs - 1 ISL - 4 LISLs • Zone databases (size = 1 MB for each fabric) corresponding to the three fabrics. • All of the classes corresponding to the three discovered fabrics as defined in the Fabric and other profiles.
Fabric profile 3 Topology view The Topology View class was introduced in SMI-S 1.3 to increase the performance and reduce the number of traversals required to discover topology. The Network Advisor SMI Agent cannot provide a complete topology and its related information including instances of classes like Brocade_TopologyView, Brocade_SanActiveConnection if one of the switches involved goes unreachable or unmanageable.
3 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. It shows how an HBA is hosted on the system (host) along with the nodes contained in it and ports controlled by it.
Fabric profile 3 Prerequisites Only the HBAs that register a FDMI host name in the Name Server (NS) on the switch or fabric support the Brocade_Platform model. Currently, the EOS switches do not support FDMI. Therefore, HBAs connected to EOS switches do not support the Brocade_Platform model, including the instance classes and association classes. NOTE The switch connected to an FDMI-enabled HBA runs on Fabric OS v7.0.0 or later. Also, the seed switch runs on Fabric OS v7.0.
3 Fabric profile FIGURE 19 40 FDMI data model Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
Fabric profile 3 Trunking This section defines the model for the trunking feature in Brocade Network Advisor SMI Agent. The trunking model is supported only for FOS switches. NOTE The m-EOS switches open trunking feature is not supported in Brocade Network Advisor SMI Agent and there will not be any modeling m-EOS open trunking. Both ISL trunking and F_Port trunking are supported for FOS switches. Data model Figure 20 shows the trunking class diagram.
3 Fabric profile Related API and classes Table 5 represents the group of switch ports forming a trunk. TABLE 5 Brocade_Trunk: CIM_RedundancySet Property name Type Description InstanceID [Key] string InstanceID opaquely and uniquely identifies an instance of this class. The format of this key is as follows.
Switch profile 3 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.
3 Switch profile Data model Figure 22 shows the Switch profile data model. FIGURE 22 Switch profile data model NOTE The value of the Dedicated property of Brocade_Switch is Switch (5) and FC Switch (37). The set operation for the Brocade_SwitchFCPortSettings.RequestedType is supported from Fabric OS v6.3 and later.
Switch profile 3 NOTE Switch un-monitoring is not supported from SMI perspective and if the switch is un monitored, then the SMI Agent would return stale information. Differentiation between switches and domains The following properties are used in CIM_CompterSystem to differentiate a simple switch, a switch created through VF, a switch created through Inter-Fabric Routing Profile (IFR), differentiating Front Domain from the Translate Domain, and the physical system that is partitioned.
3 Switch profile TABLE 10 Switch subprofiles Subprofiles Description Physical Package Models information about a storage system's physical package and optionally about internal sub packages. Access Points Provides remote access points for management tools. Software Provides information on the installed controller software. Blades Models the physical aspect of a blade in a director switch. Location Models the location of a SAN Element. Registration Refer to “Registration” on page 43.
Switch profile FIGURE 23 3 Physical Package, Access Points, Software, Blades, and Location subprofiles data model Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01 47
3 CP blades (Brocade extension) NOTE he Brocade_Chassis.ElementName property is set correctly in the corresponding instance only if the seed switch is running on a Fabric OS v6.3.x or higher and if the chassisName in the switches of the fabric are set after the seed switch firmware has been upgraded. CP blades (Brocade extension) This section details the modelling of the Core Processor (CP) blade and its associated properties (IP address, state, and so on) on the director class Brocade switches.
CP blades (Brocade extension) FIGURE 24 3 CP blades instances diagram • Brocade_CPModule instances representing CP blades are not associated to Brocade_RegisteredSubProfile through Brocade_ElementConformsToSubProfile. • Each Brocade_Blade instance representing the CP blade is logically realized as Brocade_CPModule:CIMLogicalModule. A different class for this logical module is used instead of PortModule. The PortModule contains NumPorts property, which is not applicable here.
3 FC HBA profile • The Brocade_CPModule.ModuleNumber shows the slot number of the CP blade. • The Brocade_CPModule is associated to the Brocade_PhysicalComputerSystem using Brocade_CPInPCS:CIM_SystemDevice. This association shows the containment relationship on the logical side. • Each Brocade_CPModule is associated to a Brocade_CPMgmtAccessPoint, which shows the IP address of the CP.
FC HBA profile FIGURE 25 3 FC HBA profile data model Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01 51
3 Launch In Context profile NOTE The HBA is represented by the PortController class and the serial number is the key. Launch In Context profile Brocade Network Advisor supports a number of services for network management, such as Configure Names, Historical Performance Report, Fabric Ports Report, and so on. These services are published through the Launch In Context (LIC) profile. LIC names Table 11 shows the list of LIC names and their descriptions.
Launch In Context profile TABLE 11 3 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.
3 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. Fabric_Security_Log Displays all security events for the discovered switches.
Launch In Context profile 3 For example, http:// /webstart/?module=&&${} The corresponding entries in Brocade_LICServiceAccessPoint.ParameterName is of the following format. {:::WWN}. You have to replace the ${WWN} part of URL. Here, orgName is Brocade; specName and specVersion are empty.
3 CEE switch support CEE switch support The Brocade CEE switch behaves as both an FC switch and an Ethernet switch. The FC capabilities are captured through the Switch profile. This is now enhanced to model the switch's Ethernet capabilities. The CEE switch is partitioned into an Ethernet Admin Domain and a Fibre Channel fabric, where the Ethernet Admin Domain does not have any contained domain association. Only the Fibre Channel fabric is associated to the SAN instance. Brocade_SAN.
CEE switch support 3 • Configuration of the virtual FCoE port is supported. It is a normal switch port instance. Each Brocade_SwitchFCPort instance representing a virtual FCoE port is associated to Brocade_SwitchFCPortSettings and Brocade_SwitchFCPortCapabilities instances (not shown in Figure 27 to avoid clutter; refer to Figure 22 on page 44). • Brocade_SwitchFCPortStats and Brocade_SwitchFCPortRateStats is not shown for virtual FCoE ports.
3 CEE switch support FIGURE 27 58 FCoE topology diagram Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
CEE switch support 3 Topology supported The Brocade Network Advisor SMI Agent supports the following use cases. Device • A device connected to one of the eight FC ports - The Switch profile is used to model the Brocade CEE switch and its eight FC ports. For the devices connected to these eight FC ports, refer to “Data model” on page 19 and “Data model” on page 46. The FC topology portion in Figure 27 shows the classes and their associations for this use case.
3 CEE switch support FIGURE 28 60 CEE instance diagram Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
CEE switch support 3 Zoning support Zoning is supported only on the front-end FC ports. The Brocade Network Advisor SMI Agent has the same limitations as Brocade Network Advisor. Configuration The Brocade Network Advisor SMI Agent relies on Brocade Network Advisor support to provide CEE configuration functionality. All CEE configuration features are supported on Fabric OS v6.3.0 and later.
3 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. • A new property RequestedState is inherited from the standard CIM class CIM_EnabledLogicalElement.
CEE switch support 3 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.
3 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. • Brocade_LAGService provides extrinsic methods to create and delete LAGs, and add and remove members from an existing LAG.
CEE switch support FIGURE 29 3 CEE LAG class diagram Registration There is no conformance to any profile, and thus no registration.
3 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. You can group end stations in a VLAN even if they are not physically located in the same LAN segment.
CEE switch support 3 • 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.
3 CEE switch support FIGURE 30 68 CEE VLAN class diagram Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
CEE switch support 3 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. Therefore, Brocade_VLANEndPoint.GVRPStatus is not applicable. • Brocade_VLANEndPointCapabilities.
3 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. The DMTF DSP1039 version 1.0.0 for the Role-Based Authorization Profile to model these ACLs will be followed.
CEE switch support 3 • 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.
3 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. The following notes present details on the class diagram in Figure 33. • The CEE map is defined at the scope of the switch.
CEE switch support 3 • 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.
3 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. There are some distinct differences in Brocade 8470. The following sections provide more details.
CEE switch support 3 • Brocade 8470 supports Layer 3 mode of operation. The external ports and LAGs can be in None, Layer 2 and Layer 3 Interface mode. However, the internal ports can only be in the Layer 2 Interface mode. • SetInstance of the interface mode on external ports to None and Layer 2 is supported. NOTE Support for setting of Layer 3 mode is not needed because adding of an IP address to an ethernet port automatically puts the port in Layer 3 mode.
3 CEE switch support FIGURE 34 76 CEE Brocade 8470 support data model Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
Fabric switch partitioning subprofile 3 Brocade 8428 FCoE embedded switch support Brocade 8428 is the Brocade CEE high speed switching module. CEE discovery and configuration support is similar to that of the Brocade 8000 and FCOE10-24 as detailed in the previous sections. There are some distinct differences in Brocade 8428. For more information about the differences, refer to “Differences from Brocade 8000 and FCoE 10-24” on page 74, “Support for Layer 3 features” on page 75, and “Data model” on page 75.
3 FC routing FIGURE 36 Fabric switch partitioning profile registration FC routing A Fibre Channel Router (FCR) is a specific case of switch partitioning. The FC-FC routing service provides connectivity to devices in different fabrics without merging the fabrics. A switch running the FC-FC routing service is called a Fibre Channel Router. Data model Figure 37 shows the FCR data model.
FC routing FIGURE 37 3 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).
3 FC routing • Brocade_PCSServiceCapabilities has a Boolean property called FCRCapable. If the property is true, then the switch is FCR capable and is enabled. If false, the switch is capable and not enabled. If null, the switch is not FCRcapable. In the case of VF setup, this property is null if the base switch is not discovered. • Each phantom switch is associated with Brocade_FCSwitchSettings and Brocade_FCSwitchCapabilities.
FC routing 3 . FIGURE 38 Fibre Channel Router registration model Edge-to-edge device sharing (no FCIP configured in backbone) Figure 39 shows the instance diagram which depicts fabric discovery of the backbone and edge fabric with edge to edge device sharing. A port on FCR configured as an EX_Port is filtered out during port discovery on the backbone for edge-to-edge device sharing.
3 FC routing FIGURE 39 82 Data model for edge-to-edge device sharing Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
FC routing 3 Backbone-to-edge device sharing (no FCIP configured in backbone) • Figure 40 shows the data model for backbone-to-edge device sharing. If only the backbone fabric is being managed through Brocade Network Advisor, then only instances in the BackBone fabric view are discovered. If only the edge fabric is being managed through Brocade Network Advisor, refer to the “Limitations” section.
3 FC routing FIGURE 40 84 Data model for backbone-to-edge device sharing Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
FC routing 3 Backbone-to-edge device sharing (using VEX_Port over FCIP) An FCR setup with backbone and edge fabrics encompasses the following cases: • The backbone fabric and all edge fabrics are discovered. • Only the backbone fabric is discovered. • Only some or all of the edge fabrics are discovered. Consider two Routers R1 and R2 connected to each other by FCIP connection as VE-VEX. Here R1 acts as an Edge Fabric and R2 as a Backbone Fabric.
3 FC routing FIGURE 41 86 Backbone-to-edge device sharing for VEX over FCIP Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
FC routing 3 Brocade Network Advisor SMI Agent classes added for this profile Table 12 explains the classes and MOF files. TABLE 12 Classes and MOF file Class MOF file Brocade_PCSNetworkPortSettings BrocadePartitioning.mof Brocade_PCSNetworkPortCapabilities BrocadePartitioning.mof Brocade_PCSServiceCapabilities BrocadePartitioning.mof Brocade_EthernetPort BrocadePartitioning.mof Table 13 explains the associated classes and MOF files.
3 FC routing FIGURE 42 Topology for discovering only edge fabrics • Phantom switch instances are associated to the Brocade_Fabric instance. • Imported device instances of Brocade_NodeFCPort are associated to the Brocade_Fabric instance. • No instances of Brocade_SwitchFCPort exist for phantom ports. • No instances of Brocade_SANActiveConnection exist to show the topology of ISLs between the real edge port and the phantom switches or for the imported devices.
Brocade Access Gateway and NPIV 3 Brocade Access Gateway and NPIV Access Gateway (AG) allows you to configure the enterprise fabric to handle additional N_Ports instead of domains by configuring F_Ports to connect to the fabric as N_Ports. This increases the number of device ports that can be connected to a single fabric. Multiple AGs can connect to the DCX enterprise-class platforms, directors, and switches. The switches in AG mode are logically transparent to the host and the fabric.
3 Brocade Access Gateway and NPIV Data model Figure 44 defines the data model and functions of the AG and NPIV.
Brocade Access Gateway and NPIV 3 NOTE The port statistics and the port rate statistic information modeled for the AGFCPorts will be supported from FOS 5.3 onwards. FIGURE 45 NPIV instance diagram HBA with virtualized ports without AG Figure 45 shows the discovery of a host with a virtualized port, without AG. • Brocade_SwitchFCPort has the property NPIVEnabled. The port supports connecting NPIV devices if this property value is true.
3 Brocade Access Gateway and NPIV • The Brocade_SwitchFCPortCapabilities class has two properties, NPIVSupported and MaxNPIVLogins. - The NPIVSupported property indicates the NPIV support for the FC port. The MaxNPIVLogins property indicates the maximum number of NPIV logins supported on the FC port. The value of MaxNPIVLogins is always set to 32. • The end device is represented as the instance of Brocade_Platform. The value of the property Dedicated is Not Dedicated representing the HBA.
Brocade Access Gateway and NPIV FIGURE 46 3 AG Physical Package Access Gateway When a AG-capable switch is changed to AG, it will not act as a switch and it cannot be directly discovered through Brocade Network Advisor. The port on the switch that is connected to AG is the F_Port and the port on AG that has a connection from switch is the N_Port. AG is considered as a node from the switch’s perspective. As shown in Figure 47, there are two connections from Switch1 to AG.
3 Brocade Access Gateway and NPIV AG connected to a single fabric HBA1 n1 AG n2 F2 F3 HBA2 F1 Switch 1 N1 N2 F1 F2 n3 HBA3 FIGURE 47 AG mapping HBA with virtualized ports connected to AG Figure 48 represents the Brocade Network Advisor SMI Agent model for discovery of a host attached to AG. • The instance of Brocade_Platform with Dedicated property values as Not dedicated represents the HBA attached to the AG.
Brocade Access Gateway and NPIV FIGURE 48 3 Host with AG Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01 95
3 Brocade Access Gateway and NPIV AG connected to multiple fabrics Figure 49 explains an AG connected to multiple fabrics. As shown in Figure 49, the Fabric 1 and Fabric 2 share the AG. The N1 port of AG is connected to Fabric 1 and the N4 port of AG is connected to Fabric 2. The internal mapping on AG is done such that N1 is mapped with F1 and F2, and N4 is mapped with F3. Though AG is shared with more than one fabric, it allows only one instance of AG to be associated with both the fabrics.
Brocade Access Gateway and NPIV HBA1 3 n1 AG n2 F2 F1 N1 N2 F3 HBA2 Switch 1 F1 F2 n3 Virtualized Ports HBA3 NPIV Device FIGURE 50 AG with NPIV mapping Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01 97
3 Brocade Access Gateway and NPIV FIGURE 51 98 AG and NPIV data model Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
Brocade Access Gateway and NPIV 3 Figure 52 shows a simplified instance diagram to illustrate the combination of the AG and NPIV, and Topology View features FIGURE 52 AG with NPIV instance diagram The following Brocade Network Advisor SMI Agent classes are defined in Brocade_AccessGateway.
3 Brocade Access Gateway and NPIV • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Brocade_AccessGateway Brocade_AGFCPort Brocade_AGFCPortStats Brocade_AGFCPortStatisticsCollection Brocade_AGFCPortRateStats Brocade_PortRateStatsForAGFCPort Brocade_PortStatsForAGFCPort Brocade_AGFCPortStatsInAGFCPortStatisticsCollection Brocade_AGFCPortStatisticsCollectionForAG Brocade_AGNode Brocade_AGSANProtocolEndPoint Brocade_AGMgmtAccessPoint Brocade_AGSoftwareIdentity Brocade_AGWebGUIRemoteAccessPoint Bro
FRU profiles 3 • AG on Encryption Switch, where the Encryption Switch AG is the Seed switch. • The loop devices are not supported when attached to AG. • The value of LLDP-DCBX for AG port if AG is not available in Brocade Network Advisor. - The SMI Agent populates this property as “Unknown” in Brocade_EthernetAccessGateway if the instance is retrieved through enumerateInstances. - The correct value of this property can obtained through the getInstance() intrinsic operation only.
3 FRU profiles FIGURE 53 FRUs data model Limitations FRU support for EOS switch is limited. If the mandatory properties cannot be fully populated, those instances will not be advertised as conforming to the respective profile.
Names 3 NOTE The Brocade_NumericSensor returns instances to represent the power usage value for Brocade 6505, 6510 switches, FC 16-32, FC 16-48, FC 8-32E, FC8-48E software Blades, CR16-4, and CR16-8 core blades which are running on Fabric OS v7.0.1 or later. Names Various system objects such as a switch, switch port, device, device port, and so on are identified by a WWN. For convenience, these system objects may also be assigned a user-friendly name.
3 104 Names Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
Chapter 4 Indications In this chapter • Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 • Alert indications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 • Life-cycle indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 Alert indications TABLE 14 106 Supported alert indications Message ID Trigger Property Value FC1 One of the following: • Zoning database merge was completed. How to trigger: Create a zoning configuration on two switches. Connect the two switches through an E_Port. • Configuration was saved into persistent store. How to trigger: Change the zoning configuration and save the configuration. You can also do this through the CLIs zoneadd and cfgsave.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value FC2 Configuration was enabled, and now this configuration is the active configuration. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=SNIA and MessageID=FC2 How to trigger: Enable the zoning configuration. You can also do this through the CLIs zonadd, cfgsave, and cfgenable.
4 Alert indications TABLE 14 Trigger Property Value FC6 For fabric merge and segmentation.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value FC8 Fabric added or removed. Also, applicable in Virtual Fabrics.
4 Alert indications TABLE 14 110 Supported alert indications (Continued) Message ID Trigger Property Value Core6 Switch login was attempted. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=SNIA and MessageID=Core6 How to trigger: Telnet to the switch. AlertingManagedElement COP of Brocade_Switch AlertingElementFormat COP AlertType Security OtherAlertType N/A NOTE: Core6 indication is supported only for FOS switches. This indication is not delivered if SNMP registration fails.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value Core6 Switch logout occured. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=SNIA and MessageID=Core6 How to trigger: Exit from the Telnet session. AlertingManagedElement COP of Brocade_Switch AlertingElementFormat COP AlertType Security OtherAlertType N/A AlertSubType Logout NOTE: Core6 indication is supported only for FOS switches.
4 Alert indications TABLE 14 Trigger Property Value Core8 Change in operational status for port.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD4 Configuration changed Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD4 How to trigger: Perform the CLI configdownload to the switch.
4 Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRDC6 SNMP traps turned on by Track Change On was turned off. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD6 How to trigger: Use the trackchangesset CLI command to turn off the SNMP traps.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD8 The element (port) identified by AlertingManagedElement is down. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=SNIA and MessageID=BRCD8 How to trigger: Telnet to the switch and run the CLI portdisable portnumber to disable a connected port, such as an E_Port, F_Port, or L_Port.
4 Alert indications TABLE 14 Trigger Property Value BRCD13 A single device went offline. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD13 How to trigger: Telnet to the switch and run the CLI portdisable portnumber where the port is an F_Port.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD17 A change in session status occurred.
4 Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD19 Deregistration of the managed element with the Admin Domain was completed. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD19 How to trigger: Disable switch connected to HBA.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD21 Database changes for a fabric service were completed. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD21 How to trigger: Enable or disable switch connected to HBA.
4 Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD25 Download of firmware was completed.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD27 Account is locked out on the switch. This event occurs whenever a switch account gets locked out. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD27 How to trigger: Set the lockout duration as 1 using the CLI Pasargadae --set for a user account. Attempt to telnet to the switch with a wrong password for that user account.
4 Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD29 Account was deleted on the switch. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD29 How to trigger: Delete an existing account using the CLI userconfig.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD31 Account membership has changed. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD31 How to trigger: Modify the AD membership of an existing account using the CLI userconfig.
4 Alert indications TABLE 14 Trigger Property Value BRCD33 Password has expired. This indication is delivered only when the Brocade Network Advisor SMI Agent attempts login to a fabric in which the login password has expired on the seed switch. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD33 How to trigger: Expire a password using the CLI passwdcfg --set user. Attempt client connection through the Brocade Network Advisor SMI Agent with the expired password.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD42 enumerateInstanceNames or enumerateInstances failed. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD42 AlertingManagedElement Failed COP or COP without key properties.
4 Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD44 Multiple devices (typically within a loop) went offline. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD44 How to trigger: Telnet to the switch and run the CLI portdisable portnumber where the port is an L_Port.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD48 A data value is greater than the high threshold boundary. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD48 AlertingManagedElement COP of Brocade_Switch AlertingElementFormat COP AlertType Other Alert OtherAlertType Fabric Watch NOTE: BRCD48 indication is supported for the Environment, Port, and E_Port Fabric Watch classes.
4 Alert indications TABLE 14 Trigger Property Value BRCD51 Successful recovery from a faulty condition. Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD51 AlertingManagedElement COP of Brocade_Switch AlertingElementFormat COP AlertType Other Alert OtherAlertType Fabric Watch NOTE: BRCD51 indication is supported for the Environment, Port, and E_Port Fabric Watch classes.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD53 Switch state changed.
4 Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD56 Fabric ID of a logical fabric changed.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD58 Discovered port count is in the grace limit, and is about to exceed the licensed port count.
4 Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD59 Discovered port count exceeded the licensed port count.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD61 LAG successfully enabled Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD61 AlertingManagedElement COP of Brocade_LAG AlertingElementFormat COP AlertType Other OtherAlertType CEE Switch Alert AlertSubType Config enabled PerceivedSeverity 2 (Informational) ProbableCause 123 SystemCreationClassName Brocade_ EthernetSwitch SystemName Swit
4 Alert indications TABLE 14 Trigger Property Value BRCD63 ACL configured on LAG Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD63 AlertingManagedElement COP of Brocade_LAG AlertingElementFormat COP AlertType Other OtherAlertType CEE Switch Alert AlertSubType Config enabled PerceivedSeverity 2 (Informational) ProbableCause 123 SystemCreationClassName Brocade_ EthernetSwitch SystemName Switch WWN ProviderName Brocade_AlertIndication Provider
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD65 TE port enabled Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD65 AlertingManagedElement COP of Brocade_ EthernetPort AlertingElementFormat COP AlertType Other OtherAlertType Port Alert AlertSubType Up PerceivedSeverity 2 (Informational) ProbableCause 123 SystemCreationClassName Brocade_ EthernetSwitch SystemName Switch WWN ProviderN
4 Alert indications TABLE 14 136 Supported alert indications (Continued) Message ID Trigger Property Value BRCD67 ACL configured on TE port Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD67 AlertingManagedElement COP of Brocade_ EthernetPort AlertingElementFormat COP AlertType Other OtherAlertType Port Alert AlertSubType Config enabled PerceivedSeverity 2 (Informational) ProbableCause 123 SystemCreationClassName Brocade_ EthernetSwitch System
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD68 ACL removed on TE port Query: SELECT * FROM CIM_AlertIndication WHERE OwningEntity=BROCADE and MessageID=BRCD68 AlertingManagedElement COP of Brocade_ EthernetPort AlertingElementFormat COP AlertType Other OtherAlertType Port Alert AlertSubType Config removed PerceivedSeverity 2 (Informational) ProbableCause 123 SystemCreationClassName Brocade_ EthernetSwitch SystemName Sw
4 Alert indications TABLE 14 138 Supported alert indications (Continued) Message ID Trigger Property Value BRCD69 QoS CEE map configured on TE port.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD70 QoS CEE map removed on TE port.
4 Alert indications TABLE 14 Trigger Property Value BRCD71 LLDP enabled on TE port.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD73 Virtual FCoE port disabled.
4 Alert indications TABLE 14 142 Supported alert indications (Continued) Message ID Trigger Property Value BRCD75 ACL removed from VLAN.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD76 VLAN member modified.
4 Alert indications TABLE 14 Supported alert indications (Continued) Message ID Trigger Property Value BRCD101 Fabric principal switch WWN changed.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD103 Switch resources violation.
4 Alert indications TABLE 14 Trigger Property Value BRCD104 Switch policy status violation.
Alert indications TABLE 14 Message ID BRCD106 4 Supported alert indications (Continued) Trigger Flow vision violation.
4 Alert indications TABLE 14 148 Supported alert indications (Continued) Message ID Trigger Property Value BRCD107 Fabric health violation.
Alert indications TABLE 14 4 Supported alert indications (Continued) Message ID Trigger Property Value BRCD109 SwitchFcPort level violation.
4 Life-cycle indications Life-cycle indications Table 15 explains the supported life-cycle indications.
Life-cycle indications TABLE 15 4 Supported life-cycle indications (Continued) Query Indication type Notes SELECT * FROM CIM_InstModification WHERE SourceInstance ISA CIM_ConcreteJob AND SourceInstance.CIM_ConcreteJob::JobState <> PreviousInstance.
4 TABLE 15 Life-cycle indications Supported life-cycle indications (Continued) Query Indication type Notes SELECT * FROM CIM_InstCreation WHERE SourceInstance ISA Brocade_VLAN CIM_InstCreation VLAN created SELECT * FROM CIM_InstDeletion WHERE SourceInstance ISA Brocade_VLAN CIM_InstDeletion VLAN deleted SELECT * FROM CIM_InstModification WHERE SourceInstance ISA Brocade_prioritygroups AND SourceInstance.ActivityQualifiers <> PreviousInstance.
Appendix Brocade Network Advisor SMI Agent Error Codes A Table 16 lists the Brocade Network Advisor SMI Agent error codes.
A Brocade Network Advisor SMI Agent Error Codes TABLE 16 154 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 SwitchFCPort rate statistics property is empty 13503 SwitchFCPort name set operation failed 13504 SwitchFCPort name set operation failed due to unknown err
Brocade Network Advisor SMI Agent Error Codes TABLE 16 A 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 Zoning object parent does not exist 16115 Operation not supported within zone transaction 16116 Online zone database is empty 16117 Zone alias creation opera
A Brocade Network Advisor SMI Agent Error Codes TABLE 16 156 Error codes (Continued) Error code Description 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 C
Brocade Network Advisor SMI Agent Error Codes TABLE 16 A Error codes (Continued) Error code Description 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
A Brocade Network Advisor SMI Agent Error Codes TABLE 16 158 Error codes (Continued) Error code Description 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 uns
Brocade Network Advisor SMI Agent Error Codes TABLE 16 A Error codes (Continued) Error code Description 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 fai
A Brocade Network Advisor SMI Agent Error Codes TABLE 16 160 Error codes (Continued) Error code Description 60078 Account locked error 60079 Account disabled error 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 6009
Brocade Network Advisor SMI Agent Error Codes TABLE 16 A Error codes (Continued) Error code Description 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 7000
A 162 Brocade Network Advisor SMI Agent Error Codes Brocade Network Advisor SMI Agent Developer’s Guide 53-1003159-01
