Documentos de Académico
Documentos de Profesional
Documentos de Cultura
14 December 2012
Copyright 2010 - 2012 Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, Brocade Assurance, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, MLX, NetIron, SAN Health, ServerIron,
TurboIron, VCS, and VDX are registered trademarks, and AnyIO, Brocade One, CloudPlex, Effortless Networking, ICX, NET Health,
OpenScript, and The Effortless Network are trademarks of Brocade Communications Systems, Inc., in the United States and/or in
other countries. Other brands, products, or service names mentioned may be trademarks of their respective owners.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning
any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to
this document at any time, without notice, and assumes no responsibility for its use. This informational document describes
features that may not be currently available. Contact a Brocade sales office for information on feature and product availability.
Export of technical data contained in this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with
respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that
accompany it.
The product described by this document may contain open source software covered by the GNU General Public License or other
open source license agreements. To find out which open source software is included in Brocade products, view the licensing
terms applicable to the open source software, and obtain a copy of the programming source code, please visit
http://www.brocade.com/support/oscd.
Asia-Pacific Headquarters
Brocade Communications Systems China HK, Ltd.
No. 1 Guanghua Road
Chao Yang District
Units 2718 and 2818
Beijing 100020, China
Tel: +8610 6588 8888
Fax: +8610 6588 9999
E-mail: china-info@brocade.com
European Headquarters
Brocade Communications Switzerland Srl
Centre Swissair
Tour B - 4me tage
29, Route de l'Aroport
Case Postale 105
CH-1215 Genve 15
Switzerland
Tel: +41 22 799 5640
Fax: +41 22 799 5641
E-mail: emea-info@brocade.com
Asia-Pacific Headquarters
Brocade Communications Systems Co., Ltd. (Shenzhen WFOE)
Citic Plaza
No. 233 Tian He Road North
Unit 1308 13th Floor
Guangzhou, China
Tel: +8620 3891 2000
Fax: +8620 3891 2111
E-mail: china-info@brocade.com
Document History
Title
Publication number
Summary of changes
Date
53-1001361-01
New document
March 2010
53-1002169-01
May 2011
Title
Publication number
Summary of changes
Date
53-1002534-01
March 2012
53-1001701-01
December 2012
iii
iv
Contents
Chapter 1
Chapter 2
Chapter 3
vi
Chapter 4
Indications
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Alert indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Life-cycle indications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
Appendix A
vii
viii
In this chapter
How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Supported hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Whats new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Brocade Network Advisor SMI Agent support . . . . . . . . . . . . . . . . . . . . . . . . xiv
Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Chapter 1, Connecting to the Fabric provides information about getting the fabric connected.
Chapter 2, Managed Object Format Files provides information about the format files.
Chapter 3, Profiles and Subprofiles provides information about the profiles and subprofiles
supported by the Integrated Storage Management Initiative (SMI).
Chapter 4, Indications provides the alert and life-cycle indications of all profiles.
Appendix A, Brocade Network Advisor SMI Agent Error Codes explains the error codes in
Brocade Network Advisor SMI Agent.
The procedures or parts of procedures documented here apply to some switches but not to others;
this guide identifies exactly which switches are supported and which are not.
Although many different software and hardware configurations are tested and supported by
Brocade Communications Systems, Inc. for Brocade Network Advisor SMI Agent 12.0.0,
documenting all possible configurations and scenarios is beyond the scope of this document.
ix
Supported hardware
The following switches are supported by Brocade Network Advisor SMI Agent 12.0.0:
Brocade 300
Brocade 5100
Brocade 5300
Brocade 5410
Brocade 5424
Brocade 5430
Brocade 5450
Brocade 5460
Brocade 5470
Brocade 5480
Brocade 6505
Brocade 6510
Brocade 6520
Brocade VA-40 FC
Brocade 7800 Extension Switch
Brocade 8000 FCoE Switch
Brocade Encryption Switch
Brocade DCX
Brocade DCX-4S
Brocade DCX 8510-8 Backbone (8-slot)
Brocade DCX 8510-4 Backbone (4-slot)
The following blades are supported on the Brocade DCX and DCX-4S switches:
The following blades are supported on the Brocade DCX 8510-8 Backbone (8-slot) and Brocade
DCX 8510-4 Backbone (4-slot) switches:
Support for Physical Package is provided for Access Gateways. (Refer to Access Gateway
Physical Package on page 92.)
Modelled the port statistics and the port rate statistic information for the AGFCPorts.
(Refer to Figure 44 on page 90.)
For further information about new features and documentation updates for this release, refer to
the release notes.
Document conventions
This section describes text formatting conventions and important notice formats used in this
document.
Text formatting
The narrative-text formatting conventions that are used in this document are as follows:
bold text
italic text
Provides emphasis
Identifies variables
Identifies paths and Internet addresses
Identifies document titles
code text
xi
For readability, command names in the narrative portions of this guide are presented in mixed
lettercase: for example, switchShow. In actual examples, command lettercase is all lowercase.
NOTE
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.
See Brocade resources on page xiii for instructions on accessing MyBrocade.
For definitions of SAN-specific terms, visit the Storage Networking Industry Association online
dictionary at:
http://www.snia.org/education/dictionary
Microsoft Corporation
Additional information
This section lists additional Brocade and industry-specific documentation that you might find
helpful.
xii
Brocade resources
To get up-to-the-minute information, go to http://my.brocade.com to register at no cost for a user ID
and password.
White papers, online demonstrations, and data sheets are available through the Brocade website
at:
http://www.brocade.com/products-solutions/products/index.page
For additional Brocade documentation, visit the Brocade website:
http://www.brocade.com
Release notes are available on the MyBrocade website.
Switch model
Switch operating system version
Software name and software version, if applicable
Error numbers and messages received
supportSave command output
Detailed description of the problem, including the switch or fabric behavior immediately
following the problem, and specific questions
xiii
The switch serial number and corresponding bar code are provided on the serial number
label, as illustrated below.
*FT00X0054E9*
FT00X0054E9
3. World Wide Name (WWN)
Brocade Network Advisor supportSave. Refer to the Brocade Network Advisor User Manual for
the steps involved in running the supportSave command.
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.
xiv
Chapter
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
2
2
3
No Access - If you query the CIMOM without the SMI Agent Operations privilege, the following
WBEM Exception is returned.
CIM_ERR_ACCESS_DENIED: The specified principal does not have access to perform this
operation.
Read Only Access - If you have the Read Only Access privilege and try to perform any write
operation on any of the profiles, the following WBEM Exception is returned.
CIM_ERR_ACCESS_DENIED: The specified principal does not have access to perform this
operation.
The user is not restricted to perform the WBEM queries.
Read/Write Access - No restriction is imposed on any user who has Read/Write Access for the
SMI Agent Operations privilege.
All the Resource Grouping (fabrics and hosts) performed through the user management dialog
boxes is honored by the CIMOM. The resource grouping is not be applicable for filtering out
indications. The indications from all the fabrics managed by Brocade Network Advisor is
delivered irrespective of the resource grouped by the user.
If you select the Authentication mode as No Authentication, then all the previously specified
RBAC checks are performed on the credentials provided by you in the Authentication tab of the
Configuration Tool and the previously described behavior is observed.
If a user A changes the password of a user B who has logged in to CIMOM, the user B can
continue querying the CIMOM until Brocade Network Advisor expires the user B session.
You can retrieve all the information from the interop namespace and can perform the getclass
operations even if there is no access for the SMI Agent Operations privilege.
Refer to the Brocade Network Advisor User Manual for more information about RBAC.
Features supported
The following features are supported by the CIMOM fabric discovery:
Option to discover all types of Storage Area Network (SAN) fabrics supported by the Brocade
Network Advisor.
Option to edit the switch credentials and the SNMP configurations used to discover the fabric
after the fabric is discovered.
Option to delete a fabric based on the fabric CIM Object Path (COP).
If the discovery of one of the Virtual Fabric (VF) fails, the return parameter is set to
PARTIALLY_DISCOVERED and the out parameter contains the Fabric Identifier (FID) and the
error code of the fabric that failed to get discovered.
Limitations
The following are the limitations of the CIMOM fabric discovery:
All the contexts are discovered by default in the VF. The user cannot select the contexts to be
discovered, but can delete the unwanted contexts through the DeleteFabric extrinsic method.
Data model
The Brocade_Fabric has two new additional properties, SeedSwitchWWN and SeedSwitchIP.
The connection setting of each switch is associated to the discovery service.
Every switch in the discovered fabric is represented with an instance of
Brocade_SwitchConnectionSettings. This instance gives the data to be provided in the discover
Fabric dialog box of the Brocade Network Advisor client, such as switch status, user ID, and so
on.
FIGURE 1
Features supported
The following features are supported by the CIMOM host discovery process:
Option to receive the status of discovery or deletion requests on execution of the DiscoverHost
and DeleteHost methods.
Limitations
The following are the limitations of the CIMOM host discovery process:
Supports only direct discovering of the host either through its IP address or its name, but does
not support for discovery from fabric or Virtual Machine (VM) Manager.
Editing the host discovery information through the CIMOM is not supported.
The history of the deleted host is not maintained in the CIMOM.
Data model
The Brocade_HostDiscovered class gives the discovery information of each host associated to
the Discovery service.
FIGURE 2
FIGURE 3
Figure 4 shows the host discovery through the SMIA Configuration Tool.
FIGURE 4
For more information related to fabric and host discovery, refer to the Brocade Network Advisor
User Manual.
Chapter
In this chapter
Brocade Managed Object Format files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Additional MOF description specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . 10
TABLE 1
MOF filename
Description
BrocadeAccessGateway.mof
Access Gateway
BrocadeAccessPoint.mof
BrocadeAgent.mof
CIMOM Agent
BrocadeAGStatistics.mof
AGFCPort statistics
BrocadeBlade.mof
Blade subprofile
BrocadeCEEACL.mof
BrocadeCEEMap.mof
BrocadeEthernet.mof
BrocadeExtender.mof
BrocadeFabric.mof
Fabric profile
BrocadeFabricDiscovery.mof
Fabric Discovery
BrocadeFCHBA.mof
FC HBA profile
BrocadeFCSwitch.mof
FC Switch profile
BrocadeFDMI.mof
FDMI subprofile
BrocadeFRU.mof
BrocadeIndications.mof
Indications
BrocadeJobControl.mof
JobControl subprofile
BrocadeLAG.mof
TABLE 1
MOF filename
Description
BrocadeLaunchInContext.mof
BrocadePartitioning.mof
FabricVirtualFabrics subprofile
FCR subprofile
BrocadePhysicalPackage.mof
Location subprofile
Physical Package subprofile
BrocadeProfile.mof
Profile Registration
BrocadeSoftware.mof
Software subprofile
BrocadeSwitchStatistics.mof
SwitchFCPort statistics
BrocadeTopologyView.mof
Topology view
BrocadeVLAN.mof
BrocadeZoning.mof
NOTE
The Brocade subclasses do not automatically override all of the properties in the superclass. The
properties that are not overridden have a null value unless the superclass has a default value that
is defined in the MOF.
When the property in the MOF is defined to be of type sint16, then the equivalent Java type is
java.lang.Short.
If a given instance of a class can be created or deleted by the Brocade Network Advisor SMI
Agent
If instances of a class can only be created, the following line is included in the Description qualifier:
Instances of this class can be created by a client
If instances of a class can only be deleted, the following line is included in the Description qualifier:
Instances of this class can be deleted by a client
10
For example:
[Provider("java:com.brocade.api.cim.provider.zoning.Brocade_ZoneSetProvider"),
Description (
"Brocade_ZoneSet is a container of zones.\n\n"
"Instances of this class can be deleted by a client.")]
class Brocade_ZoneSet: CIM_ZoneSet {
Deprecation qualifier
Instance classes, association classes, properties, or extrinsic methods that have the Common
Information Model (CIM) qualifier deprecated in the MOF definition will continue to be implemented
in the Brocade Network Advisor SMI Agent. If a new implementation is documented, you should use
the new implementation as soon as possible to minimize backward-compatibility issues.
11
12
Chapter
In this chapter
UML diagram conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
SMI profiles and subprofiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Server profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Fabric profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Switch profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
CP blades (Brocade extension). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
FC HBA profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Launch In Context profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
CEE switch support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Fabric switch partitioning subprofile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
FC routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Brocade Access Gateway and NPIV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
FRU profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
FIGURE 5
13
TABLE 2
Profile
Subprofile
SMI-S version
Server
Indications
1.4
Profile Registration
1.0.0
1.4
Fabric Profile
1.4
Zone Control
1.4
1.4
FDMI
1.2
FabricVirtualFabrics
1.2
FabricView
1.5
Switch Profile
1.3
Blades
1.4
Physical Package
1.3
Software
1.4
Access Points
1.3
Location
1.4
FabricSwitchPartitioning
1.2
FC HBA Profile
1.3
1.3
Fan Profile
1.0.0
Sensors Profile
1.0.0
1.0.0
Security
1.0.0
FC Router
1.5
Launch In Context
1.5
1.5
Physical Package
1.5
Fabric
Switch
Host
14
Server profile
Support for Fibre Channel Router (FCR), modeled through the FabricSwitchPartitioning
subprofile
Names
Support for the Converged Enhanced Ethernet (CEE) switch
Support for Zoning Session operations through Job Control
Support for selected indications
SAN zoning
Support for fabric discovery and host discovery
Server profile
The Server profile is supported by the Web-Based Enterprise Management (WBEM) Solutions J
WBEM Server CIMOM. The Brocade Network Advisor SMI Agent is a combination of two products,
the CIMOM and the provider product. Each product supports its software as shown in Figure 6.
NOTE
The Brocade Network Advisor SMI Agent's J WBEM Server has been upgraded from version 3.4.3 to
version 3.9.0. The 64 bit Network Advisor will contain a 64 bit JServer with it and the 32 bit Network
Advisor will contain a 32 bit JServer.
15
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.
16
Fabric profile
FIGURE 7
Indications profile
Fabric profile
The Brocade Network Advisor SMI Agent supports the Storage Networking Industry Association
(SNIA) Fabric profile, which defines the model and functions of a storage network for topology and
zoning control.
A Brocade_SAN instance in CIM is keyed by the property name with an associated optional
property, NameFormat. Name is opaque and NameFormat identifies how the property name is
generated. In the case of Brocade_SAN, the property NameFormat is set to WWN. Simple
fabric - Brocade_SAN.Name is the principal WWN of the fabric.
A fabric or SAN instance both inheriting CIM_AdminDomain are differentiated using the
OtherIdentifyingInfo property.
In virtual fabrics with dedicated ISL between the base switches where all virtual fabrics have
been discovered, Brocade_SAN.Name is the principal WWN of the base fabric.
17
Fabric profile
In virtual fabrics with dedicated ISL between the base switches where some of virtual fabrics
have been discovered but there is no base fabric.
If the base fabric is discovered, Brocade_SAN.Name is the principal WWN of the base
fabric.
If the base fabric is not discovered, the virtual fabrics will be disjointed and in each fabric
one SAN instance will be generated.
In Virtual fabrics with no dedicated ISL between the base switches but with a dedicated ISL
between one of the discovered virtual fabrics.
In the absence of a dedicated ISL between the base switches, no actual logical fabrics
exist except for those which have a dedicated ISL. The virtual fabrics will be disjointed and
in each fabric one SAN instance will be generated.
A FCR setup where the backbone fabric and edge fabrics have been discovered,
Brocade_SAN.Name is the principal WWN of the backbone fabric.
A FCR setup where only one or more edge fabrics have been discovered.
- In the absence of the backbone, each edge fabric is associated to its own SAN instance
and the Brocade_SAN.Name is the principal WWN of that edge fabric.
When a single edge fabric is connected to more than one separate backbone fabric, all the
fabrics will be discovered as a single SAN. The Brocade_SAN.Name is the principal WWN of
one of the backbone fabric.
A fabric containing a CEE switch, Brocade_SAN.Name is the principal WWN of the Fibre
Channel fabric with the switch.
In a simple Fibre Channel fabric, Brocade_SAN.Name is the principal WWN of the fabric.
Registration
Figure 8 shows the SNIA profile registration profile model to advertise the Fabric profile and its
subprofiles.
18
Fabric profile
FIGURE 8
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.
19
Fabric profile
FIGURE 9
20
Fabric profile
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"}
NOTE
The SwitchId property will be populated only for switches running FOS 7.1.0 onwards.
Brocade_SAN.ElementName properties
The following are the properties of Brocade_SAN.ElementName:
The Brocade_SAN.ElementName will not get reset unless all the fabrics in the SAN have been
deleted from Brocade Network Advisor.
If the principal switch of the fabric changes then the associated SAN name for the SAN will be
retained.
For SAN consisting of multiple fabrics,the SAN name would be retained until all the fabrics in
the SAN get deleted.
For multiple fabrics managed by BNA merge, the name of the SAN whose SAN key is retained
becomes the new SAN ElementName.
For SAN that splits into multiple fabrics, the SAN which has the same name as the original SAN
would retain its name.
NOTE
Limitations
The following are the limitations of the Brocade_SAN.ElementName:
If the firmware is upgraded in the switch1 and it goes down momentarily, then switch2
becomes the principal switch in that fabric and the Element Name is changed to default.
When the switch1 comes active and becomes the principal switch, then the configured
SAN ElementName is reset to the configured name.
21
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.
Registration
Refer to Registration on page 18.
Data model
Figure 10 shows the data model with the classes and properties that are supported to conform to
these subprofiles. Only those properties that are mandatory are considered.
22
Fabric profile
FIGURE 10
Table 3 outlines the required CIM elements for the zone control subprofile.
TABLE 3
ElementName
Description
Currently
supported Y/N?
CIM_HostedService
Yes
CIM_ZoneService
Yes
23
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
ClearZoneDB
Even though SMI zoning operations appear atomic in nature, the changes are delivered to the
fabric as a whole. The changes made by a CIM client are not visible to any other client, not even
on Telnet until the transaction is committed successfully.
The operations Activate (including with job), Deactivate (including with job), and ClearZoneDB
are supported only outside the scope of a zoning transaction. If a transaction is open, then the
changes must be done before activating, deactivating, or clearing the database.
A user is identified by Brocade Network Advisor user name only, and so a zoning transaction
opened by user1 on host1 can be used by the same user1 on some other host if it is still open.
The IP address of the host does not configure as part of the user name.
A commit operation is successful once the zoning changes are accepted by the seed switch.
The successful completion of a commit operation does not mean that all the changes have
been propagated to the entire fabric.
24
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. This behavior is the same as
between two Brocade Network Advisor clients.
If an SMI client starts a transaction on a fabric and a Brocade Network Advisor client opens a
zoning dialog box, a notification is issued, which need not be considered. The SMI client could
be in the middle of the session changes.
If the SMI client commits first, the Brocade Network Advisor client is notified that the zone
database has been changed. The Brocade Network Advisor client has the option of ignoring or
refreshing the zone database copy. This is a warning message and there is nothing preventing
the Brocade Network Advisor client from ignoring the warning. This behavior is the same as
between two Brocade Network Advisor clients.
If a Brocade Network Advisor client commits the changes first, the SMI client's zone
transaction is aborted and an indication is sent.
If the time for which an open transaction is idle or greater than Brocade_ZoneService.Timeout
(value in seconds), the SMI client's zone transaction is aborted and an indication is sent.
Error code 32770 is mapped to Transaction_Not_Started, which is different from the host
agent where it is No_Transaction.
Error code 32772 is mapped to Transaction_Already_Started, which is different from the host
agent where it is Transaction_Already_On.
Error code 32781 is a new error code mapping to Transaction_Not_Available. This will be
returned to a CIMClient on SessionControl in the event that the zoning transaction on that
fabric is already opened by some other CIMClient.
25
Fabric profile
Data model
Figure 11 shows the classes and properties of the Job control subprofile.
FIGURE 11
Once a job is started and is in progress, its PercentComplete property always indicate 50
percent till job complete, at which time it will indicate 100 percent.
The DeleteOnCompletion property is always set to false, indicating that all jobs, failed or
completed must be deleted explicitly by the CIMClient using the deleteInstance intrinsic
method. Otherwise, they will continue to exist in the Completed state.
Because there is no automatic deletion of completed jobs by the Brocade Network Advisor SMI
Agent, the TimeBeforeRemoval property is not applicable and is always set to zero.
If a completed job is not deleted and a new job for the same operation on the same target is
started, the new job replaces the old job. The old job is permanently deleted.
26
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"}.
Although the GetError() method is mandatory, this operation is not supported.
Upon Brocade Network Advisor server restart, all existing Brocade_ConcreteJob instances are
deleted because they are not persisted in the Brocade Network Advisor database.
Supported indications
Table 4 shows all the supported mandatory indications.
TABLE 4
Supported indications
Indication
Description
SAN zoning
Storage Area Network (SAN) zoning is a method of arranging Fibre Channel devices into logical
groups over the physical configuration of the fabric. Brocade Network Advisor SMI Agent provides
SAN zoning configuration support such as CreateSANZone, AddSANZoneMemembers,
RemoveSANZoneMembers, and DeleteSANZone through extrinsic methods.
A Logical Storage Area Network (LSAN) consist of zones in two or more edge fabrics or backbone
fabrics that contain the same devices.The LSANs provide selective device connectivity between
fabrics without forcing you to merge those fabrics.
27
Fabric profile
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.
The LSAN zoning device sharing operations are done only through backbone fabrics. This
option is disabled for other edge fabrics.
The LSAN zone can be added to any managed edge fabrics and backbones during the zone
activation.
Registration
There is no profile registration for this model.
Data model
Figure 12 shows the data model of SAN zoning.
28
Fabric profile
FIGURE 12
29
Fabric profile
The SAN zones are activated while the session is closed using SANSessionControl method with
RequestedSessionState=3.
You cannot open a session for SAN level zoning and Fabric level zoning simultaneously for a
particular backbone fabric. If you start with a session for SAN level zone, it must be closed
before starting the session for fabric level zone and vice versa.
The CreateSANZone() in Brocade_SANZoneService will get the SAN zone name, list of member
WWNs, and SANZoneType as inputs. A zone with multiple members is created and activated in
the backbone or edge fabrics based on the members.
The AddSANZoneMembers() in Brocade_SANZoneService will get the SAN zone name and
member WWNs as input. Add the zone members to LSAN zone and reactivate the LSAN zone.
The RemoveSANZoneMembers() in Brocade_SANZoneService will get the SAN zone name and
member WWNs as input. Remove those zone members from LSAN zone and reactivate the
LSAN zone.
The DeleteSANZone() in Brocade_SANZoneService will get the zone name as input and deletes
the same zone from the fabrics.
Only WWN zone member type is supported, and Domain:PortIndex zone member type is not
supported in SAN level zoning.
The AddSANZoneMembers extrinsic call will not return an error, when duplicate members are
already present in zone.
The RemoveSANZoneMembers extrinsic call will not return errors, when the requested
member is not present in the zone.
The SAN zone is added under an existing active zone configurations during SAN zone
activation. If there is no active configuration in the edge fabric or backbone fabric, a zone set
with the name of LSAN_CFG_<date/time> is created and the respective SAN zone is added
under this zone set.
30
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 with message ID BRCD102 is delivered to CIM client, if there is a failure in SAN
zone activation through CIM client. It is not delivered if there is a failure in SAN zone activation
through Brocade Network Advisor client.
Alert indication with message ID FC2 is delivered for successful activation because zoning
activation is performed at fabric level.
Use cases
Figure 13 explains a sample SAN configuration.
Target 2
Target 1
Target 3
Host
Fabric 1
E
Fabric 2
Fabric 4
Fabric 3
E
E
EX
EX
FC router 1
EX
EX
EX
EX
EX
FC router 2
FC router 3
FC router 4
Backbone fabric
FIGURE 13
Create a LSAN_Zone1, add WWN of Host, Target3 and activate the same zone. As the
LSAN_Zone1 has end devices from fabric1 and fabric3, it is activated to both the fabrics. The
following extrinsic calls are used for this operation:
31
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.
The following are the extrinsic calls used for this operation:
The member is removed from the zone in fabric1 and fabric3 and the copy of zone is
removed from the fabric2.
Subscribe BRCD102 indications and create SAN zone with online members. An indication with
message ID BRCD102 is delivered for activation failures.
Create SAN zone with the prefix XSAN_, add some zones member WWNs, and activate the
zone. As there are invalid zone names, the failure error code 5
(CIM_ERR_INVALID_PARAMETER) is returned.
Add some Domain:PortIndex zone members in the SAN zone. Due to invalid zone members,
the error code 5 (CIM_ERR_INVALID_PARAMETER) is returned.
32
Fabric profile
All virtual fabrics are discovered with dedicated ISLs between the base switches.
- Brocade_SAN.Name is the principal WWN of the base fabric where all virtual fabrics have
been discovered.
In the absence of a dedicated ISL between the base switches, no actual logical fabrics
exist except for those that have a dedicated ISL. The virtual fabrics are disjointed.
All virtual fabrics are discovered with no dedicated ISLs between the base switches but
dedicated ISLs between logical switches.
Registration
Each virtual fabric represented by an instance of Brocade_Fabric, is associated to an instance of
Brocade_RegisteredProfile(Fabric). By SMI definition, all virtual fabrics that are physically
interconnected belong to the same SAN. The Brocade_SAN instance containing the virtual fabrics
associates itself to an instance of Brocade_RegisteredSubprofile (FabricVirtualFabrics) only if the
base switch is discovered. Refer to Registration on page 18.
Data model
Figure 14 models the required classes. The classes relevant in the Fabric profile are also included:
33
Fabric profile
FIGURE 14
34
Fabric profile
FIGURE 15
Sample Virtual Fabrics configuration, connecting the SMI Agent to a single chassis
For this example, assume that the SMI Agent is connected to the Chassis 2 IP address. The SMI
Agent can discover the following:
1 SAN
3 fabrics (Fabric ID 1, Fabric ID 2, and Fabric ID 3)
4 physical chassis
- Chassis 1
- Chassis 2
- Chassis 3
- The chassis for Switch B
9 switches
- 2 logical switches in Chassis 1
- 3 logical switches in Chassis 2
- 3 logical switches in Chassis 3
- Switch B
Logical switch 18 in Chassis 3 and Switch A, which is connected to this logical switch, are not
discovered.
35
Fabric profile
There is one instance of Brocade_Blade for each physical blade in the director switch.
For each Brocade_Blade, there can be multiple Brocade_PortModule instances, depending on
the number of existing logical switches and how the ports are allocated throughout the
chassis.
FIGURE 16
36
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.
Objectives
The objective is to deliver a class that can be enumerated, gives better performance than
enumerating Brocade_SANActiveConnection(CIM_ActiveConnection), and traverse to each
endpoint to gather data about the link between switch ports or between N_Ports and switchports.
Performance considerations
Performance should be significantly better than the combined performance of enumeration of
Brocade_SANActiveConnection (CIM_ActiveConnection) and traversals to endpoint instances
through CIMClient.associators call.
Registration
Figure 17 shows the registration model of Topology view.
FIGURE 17
37
Fabric profile
Data model
Figure 18 shows the data model of Topology view.
FIGURE 18
FDMI subprofile
The Fabric-Device Management Interface (FDMI) enables the management of devices such as Host
Bus Adapters (HBAs) through the fabric. This subprofile models the discovery of HBA type devices
without having the SMI Agent reside on the host containing the HBA. It shows how an HBA is hosted
on the system (host) along with the nodes contained in it and ports controlled by it. It allows HBAs
to expose product information such as firmware version, vendor, serial number, and so on. This
model supports all HBA configurations such as single-node single-port HBA, single-node dual-port
HBA, and dual-node dual-port HBA.
38
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.
NOTE
The switch connected to an FDMI-enabled HBA runs on Fabric OS v7.0.0 or later. Also, the seed
switch runs on Fabric OS v7.0.0 or later to support this profile.
Registration
Refer to Registration on page 18.
Data model
Figure 19 shows the class diagram of the classes and properties supported in the FDMI subprofile.
The instances for the CIM classes Brocade_SoftwareIdentity, Brocade_HBAProduct,
Brocade_PhysicalHBA, and Brocade_PortController are available as part of the FDMI subprofile
provided the switches are running Fabric OS v7.0.0 or later.
For a single-node single-port HBA, there is a single Brocade_Node instance hosted on a
Brocade_Platform and a single Brocade_PortController representing the logical aspects of the
Brocade_PhysicalHBA controlling a single Brocade_NodeFCPort.
For a single-node dual-port HBA, there is a single Brocade_Node hosted on a Brocade_Platform
and a single Brocade_PortController representing the logical aspects of the Brocade_PhysicalHBA
controlling both Brocade_NodeFCPort instances.
For a dual-node dual-port HBA, there are two Brocade_Node instances hosted on the same
Brocade_Platform and a single Brocade_PortController representing the logical aspects of the
Brocade_PhysicalHBA controlling both Brocade_NodeFCPort instances.
39
Fabric profile
FIGURE 19
40
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.
Both ISL trunking and F_Port trunking are supported for FOS switches.
Data model
Figure 20 shows the trunking class diagram.
FIGURE 20
41
Fabric profile
TABLE 5
Brocade_Trunk: CIM_RedundancySet
Property name
Type
Description
InstanceID [Key]
string
TypeOfSet[]
uint16
ElementName
string
RedundancyStatus
uint16
LoadBalanceAlgorithm
uint16
OtherTypeOfSet[]
string
OtherLoadBalanceAlgorithm
String
TABLE 6
Brocade_TrunkInSwitch: CIM_HostedCollection
Property name
Type
Description
Antecedent
Brocade_Switch REF
Dependent
Brocade_Trunk REF
TABLE 7
42
Brocade_SwitchFCPortInTrunk: CIM_MemberOfCollection
Property name
Type
Description
Collection
Brocade_Trunk REF
Member
Brocade_SwitchFCPort REF
Switch profile
TABLE 8
Property name
Type
Description
Collection
Brocade_Trunk REF
Member
Brocade_AGFCPort REF
Switch profile
The Storage Networking Industry Association (SNIA) switch profile defines the model and functions
of a fibre channel switch including state, status, and control of the device and its connections.
Registration
The SNIA Profile Registration Profile model is followed to advertise Switch profile and its
subprofiles.
Figure 21 shows the instance diagram with the objects and properties for Switch profile
registration. Only for blades, the actual blade instances that conform to the Blades subprofile will
be associated. For the other subprofiles, such as Software, Access Points, and so on, the
association to the actual instances are not supported.
FIGURE 21
43
Switch profile
Data model
Figure 22 shows the Switch profile data model.
FIGURE 22
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.
44
Switch profile
NOTE
Switch un-monitoring is not supported from SMI perspective and if the switch is unmonitored, then
the SMI Agent would return stale information.
TABLE 9
PortDiscriminator values
No
Port
PortDiscriminator value
FCIP
internal + FCoE
NPIV
IFR virtual
IFR
ICL ports
Chassis
VF
Not Applicable
Internal
45
Switch profile
TABLE 10
Switch subprofiles
Subprofiles
Description
Physical Package
Access Points
Software
Blades
Location
Registration
Refer to Registration on page 43.
Data model
Figure 23 shows the data model with the classes and properties that are supported to conform to
the switch subprofiles.
46
Switch profile
FIGURE 23
Physical Package, Access Points, Software, Blades, and Location subprofiles data model
47
NOTE
Data model
Figure 24 shows the instance diagram of the CP blades.
48
FIGURE 24
49
FC HBA profile
FC HBA profile
The Fibre Channel Host Bus Adapter (FC HBA) profile is similar to the FDMI subprofile. As with
FDMI, this model also supports all HBA configurations such as single node-single port HBA,
single-node dual-port HBA, and dual-node dual-port HBA.
Prerequisites
Only the HBAs discovered in Brocade Network Advisor are exposed through the FC HBA profile.
Data model
Figure 25 shows the data model of the FC HBA profile.
50
FC HBA profile
FIGURE 25
51
NOTE
The HBA is represented by the PortController class and the serial number is the key.
LIC names
Table 11 shows the list of LIC names and their descriptions.
TABLE 11
52
LIC name
Description
About
CEE_CEE_Configuration
CEE_QoS_Configuration
Discovery
Discovery_Host_Adapters
Fabric_TopNTalkers_Report
Fabric_Switch_Ports_Report
Fabric_Switch_Configuration_Backup
Fabric_Switch_Configuration_Restore
Fabric_Switch_Software_Update
Fabric_Switch_SupportSave
Fabric_Switch_Threshold_Policies
Fabric_Device_Connectivity_Diagnostics
TABLE 11
LIC name
Description
Fabric_Device_TraceRoute
Fabric_Device_Sharing_Diagnostics
Fabric_Zoning_Configuration
Fabric_Realtime_Graph
Fabric_Historical_Graph
Fabric_Audit_Log
Fabric_Binding_Configuration
Fabric_Bottlenecks_Configuration
Fabric_Create_View
Fabric_Email_Event_Configuration
Fabric_Encryption_Configuration
Fabric_End_To_End_Monitors
Fabric_Event_Log
Fabric_FCIP_Configuration
Fabric_Ficon_Log
Fabric_Logical_Switches_Configuration
Fabric_Port_Fencing
53
TABLE 11
LIC name
Description
Fabric_ProductStatus_Log
Fabric_Router_Configuration
Fabric_Security_Log
Fabric_Syslog
Fabric_Syslog_Forwarding
FCoE_Configuration
Names
Server_Info
User_Management
User_Preferences
VLAN_Configuration
54
For example,
http:// <IP Address: port number>/webstart/<JNLP file name>?module=<module name>&<SSO
parameters if any>&${<parameter name like WWN>}
The corresponding entries in Brocade_LICServiceAccessPoint.ParameterName is of the following
format.
{<OrgName>:<SpecName>:<SpecVersion>:WWN}.
You have to replace the ${WWN} part of URL. Here, orgName is Brocade; specName and
specVersion are empty. Therefore, the ParameterName is Brocade:::<WWN>
NOTE
FIGURE 26
55
Registration
Refer to Registration on page 43. The Brocade_Switch instance representing the CEE switch is
associated to the Brocade_RegisteredProfile instance for switch. There is no profile conformance
for the Ethernet portion of the model due to evolving standards.
Data model
Figure 27 shows the FC and Ethernet topologies along with their connections to the physical
elements. This is a general model that covers device and switch connections to the CEE switch:
The virtual FCoE port is represented as the Brocade_SwitchFCPort instance with the PortType
as G, or F, or E and is not be associated to a Brocade_PCSNetworkPort. It is an internal port
and there is no physical representation for that port. Even though the virtual FCoE ports are
internal to the switch, they will be modeled as visible switch ports in order to show the devices
physically (directly or indirectly) connected to one of the Ethernet interfaces. However, these
internal ports exist in the ASIC and the Brocade_SwitchFCPort.PortDescriminator property has
the value "8" representing that this is an internal port.
The presence of an active FCoE session is registered as a name server node and port entry.
This is depicted in the host topology as the node and node ports.
56
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).
57
FIGURE 27
58
Topology supported
The Brocade Network Advisor SMI Agent supports the following use cases.
Device
A device connected to one of the eight FC ports - The Switch profile is used to model the
Brocade CEE switch and its eight FC ports. For the devices connected to these eight FC ports,
refer to Data model on page 19 and Data model on page 46. The FC topology portion in
Figure 27 shows the classes and their associations for this use case.
A device directly connected to one of the Ethernet ports on the CEE switch (one or multiple
FCoE login sessions open) with the device port and device node WWN for each session
registered in the NS database. Figure 27 shows elements in both the FC and Ethernet side. If
the host is registered with a FDMI host name, then the node and node port is hosted on the
platform.
A device indirectly connected to the CEE switch (one or multiple FCoE login sessions open) with
the device port and device node WWN for each session registered in the NS database.
Figure 27 shows elements in both the FC and Ethernet side. The elements in orange cannot be
discovered. This means there is no representation of the Ethernet cloud.
Switch
Two CEE switches connected by their FC ports.
Two CEE switches connected by their Ethernet ports in pure Layer 2 - Both the switches must
be individually managed. The Ethernet portion in Figure 28 depicts the elements and their
connections. There will be one Brocade_EthernetAdminDomain and one
Brocade_EthernetLogicalNetwork per subnet.
59
FIGURE 28
60
Zoning support
Zoning is supported only on the front-end FC ports. The Brocade Network Advisor SMI Agent has
the same limitations as Brocade Network Advisor.
Configuration
The Brocade Network Advisor SMI Agent relies on Brocade Network Advisor support to provide CEE
configuration functionality.
All CEE configuration features are supported on Fabric OS v6.3.0 and later.
Requirements
Create LAG
Delete LAG
Add members to LAG
Remove members from LAG
Discovery of VLANs
- Create VLAN
- Delete VLAN
- Add members to VLAN
- Remove members from VLAN
Discovery of CEE ACL policies
- Create ACL policy
- Delete ACL policy
- Modify ACL policy
- Assign ACLs
Discover CEE maps
- Create CEE map
- Delete CEE map
- Modify CEE map
- Assign CEE Map
Enable global LLDP
Disable global LLDP
Indications
61
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.
Saving the running configuration to the startup configuration on the CEE switch
This feature allows you to save all the CEE configuration changes made after startup so that they
are persisted across reboots. The class Brocade_EthernetSwitch in BrocadeEthernet.mof is
updated with a new extrinsic method ConfigSaveRunningToStartup. This method saves the CEE
changes to startup configuration on the switch. The changes are visible even after a reboot.
62
Limitations
The value of LLDP-DCBX for port and switch is not persisted in Brocade Network Advisor. In order to
retrieve the value of this property, a call needs to be executed. As a result, populating this property
for port and switch during an enumerateInstances operation is costly and will lead to a degradation
in discovery timings. The Brocade Network Advisor SMI Agent will populate this property as
Unknown in both Brocade_EthernetSwitch and Brocade_EthernetPort, if the instance is retrieved
through enumerateInstances. Users can get the correct value of this property on demand through
the getInstance() intrinsic operation only.
The value of Brocade_VLANEndPoint is not persisted in Brocade Network Advisor. Brocade Network
Advisor SMI Agent will populate this property as Unknown.
LAGs
Link aggregation allows you to bundle multiple physical Ethernet links to form a single logical trunk
providing enhanced performance and redundancy. The aggregated trunk is referred to as a Link
Aggregation Group (LAG). The LAG is viewed as a single link by connected devices, the Spanning
Tree Protocol (STP), Virtual Local Area Network (VLANs), and so on. When one physical link in the
LAG fails, the other links stay up and there is no disruption to traffic.
Brocade Network Advisor SMI Agent supports discovery of these LAGs. In addition, support will be
provided to create, delete, and modify existing LAGs.
NOTE
To configure links to form a LAG, the physical links must be in the same speed and all links must go
to the same neighboring device.
Data model
There is no SNIA model for LAGs. Some aspects of the Distributed Management Task Force (DMTF)
model are considered while others are completely proprietary. The following detailed notes
describe the class diagram as shown in Figure 29.
The LAG is a protocol endpoint defined at the scope of the switch and is represented by an
instance of Brocade_LAG associated to the scoping system, which is the
Brocade_EthernetSwitch through Brocade_LAGInEthernetSwitch.
The property Brocade_LAG.InterfaceMode indicates whether or not the LAG is in Layer 2 mode
and is writable.
Each LAG can contain zero or more members. Each LAG member is represented by an instance
of Brocade_LAGPort. The composition is through Brocade_LAGPortInLAG.
The member is also defined at the scope of the switch associated to the scoping system, which
is the Brocade_EthernetSwitch through Brocade_EthernetSwitchHostedLAGPort.
63
Brocade_LAGService provides extrinsic methods to create and delete LAGs, and add and
remove members from an existing LAG.
64
FIGURE 29
Registration
There is no conformance to any profile, and thus no registration.
65
VLANs
Virtual Local Area Network (VLANs) provide the capability to overlay the physical network with
multiple virtual networks. VLANs allow you to isolate the network traffic between virtual networks
and reduce the size of administrative and broadcast domains. A VLAN contains end stations that
have a common set of requirements that are independent of physical location. You can group end
stations in a VLAN even if they are not physically located in the same LAN segment. VLANs are
typically associated with IP subnetworks and all the end stations in a particular IP subnet belong to
the same VLAN. VLAN membership is configurable on a per-interface basis.
Data model
There is no SNIA model for VLANs. Some aspects of the Distributed Management Task
Force (DMTF) model have been considered while others are completely proprietary. The following
detailed notes describe the class diagram as shown in Figure 30.
The VLAN is a collection of protocol endpoints defined at the scope of the switch and is
represented by an instance of Brocade_VLAN associated to the scoping system, which is the
Brocade_EthernetSwitch through Brocade_VLANInEthernetSwitch.
The member is also defined at the scope of the switch associated to the scoping system, which
is the Brocade_EthernetSwitch through Brocade_EthernetSwitchHostedVLANEndPoint.
Brocade_VLANService provides extrinsic methods to create and delete VLANs, and add and
remove members from an existing VLAN.
The path of the newly created Brocade_VLAN instance is returned in the output parameter
VLAN. The Brocade_VLAN will be associated to the appropriate Brocade_EthernetSwitch
instance on which it is defined.
66
67
FIGURE 30
68
Registration
There is no conformance to any profile, and thus no registration.
Limitations
The following are the limitations of VLAN profile:
Brocade_VLANEndPointCapabilities.Dot1QAcceptableVLANFramesTypes is same as
Brocade_VLANEndPoint.FrameType.
CEE ACLs
Access Control List (ACL) is used to filter Ethernet traffic of the Ethernet switch. It permits or denies
incoming packets from passing through interfaces that has the ACL policies applied to them. The
primary function is to control the movement of packets through or to the system and also to track
the packet movement.
ACLs are not effective until they are applied to an interface. One can apply ACLs on VLANs and on
the Ethernet switch 10-Gigabit Ethernet Layer 2 interfaces (Physical interfaces, Logical interfaces,
and LAGs). Each ACL is a unique collection of permit and deny statements (rules) that apply to the
packets. When a packet is received on an interface, the switch compares the fields in the packet
against any ACLs applied to the interface to verify that the packet has the required permissions to
be forwarded. The switch compares the packet sequentially against each rule in the ACL and either
forwards the packet or drops the packet.
The Brocade Network Advisor SMI Agent supports the discovery of these ACLs, both standard and
extended. In addition, support is provided to create, delete, and modify existing ACLs.
Resequencing of an ACL is not supported. Displaying and clearing of the ACL statistics counter is
not supported. However, users can enable or disable the tracking of traffic by specifying the count
parameter within the rule of an ACL policy.
There are two types of Layer 2 Media Access Control (MAC) address ACLs, standard and extended.
Layer 2 standard ACLs-permit and deny traffic according to the source MAC address in the
incoming frame. Use standard MAC ACLs if you only need to filter traffic based on source MAC
addresses.
Layer 2 extended ACLs-permit and deny traffic according to the source and destination MAC
addresses in the incoming frame, as well as other information in the MAC header, such as
EtherType.
The ACL name must be unique across both the standard and extended types.
The ACL name can be a maximum of 64 characters.
Special characters can be used in an ACL name.
69
Even though ACLs can be Layer 2-specific (MAC) or Layer 3-specific (IP), they can only be
applied on the same type of interface. Because an interface can only be set to Layer 2 mode,
Layer 2 ACLs and only ACLs with MAC source and destination addresses are supported.
Data model
There is no SNIA model for CEE ACLs. The DMTF DSP1039 version 1.0.0 for the Role-Based
Authorization Profile to model these ACLs will be followed. All mandatory classes and properties as
stated in this profile will be supported. The following detailed notes describe the class diagram as
shown in Figure 31.
The CEE ACL policy is defined at the scope of the switch. This policy represented by an instance
of Brocade_CEEACLPolicy is associated to the scoping system, which is the
Brocade_EthernetSwitch through Brocade_CEEACLPolicyInEthernetSwitch.
Each CEE ACL policy may contain zero or more rules. All the rules within a policy are
represented by a single instance of Brocade_CEEACLRules. The composition is through
Brocade_CEEACLRulesInPolicy. There is one instance of Brocade_CEEACLRules for every
Brocade_CEEACLPolicy on the Brocade_EthernetSwitch.
All the possible values for the Brocade_CEEACLRules.QualifierFormats array are published in
the Brocade_CEEACLServiceCapabilities.QualifierFormatsSupported as an array of strings. The
value in the Brocade_CEEACLRules.QualifierFormats property is a subset of these formats.
If a CEE ACL policy has been applied to a port, LAG or VLAN, this information can be discovered
by traversing the Brocade_CEEACLPolicyOnEthernetPort, Brocade_CEEACLPolicyOnLAG, or
Brocade_CEEACLPolicyOnVLAN respectively to the appropriate ManagedElement.
70
FIGURE 31
71
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 maps
Data model
There is no SNIA model for CEE maps. The following notes present details on the class diagram in
Figure 33.
The CEE map is defined at the scope of the switch. This map is represented by an instance of
Brocade_CEEMap associated to the scoping system, which is the Brocade_EthernetSwitch
through Brocade_CEEMapInEthernetSwitch.
Each CEE map can contain zero or more priority groups. All the priority groups within a map are
represented by a single instance of Brocade_PriorityGroups. The composition is through
Brocade_ PriorityGroupsInCEEMap. There will be one instance of Brocade_PriorityGroups for
every Brocade_CEEmap on the Brocade_EthernetSwitch.
All the possible values for the Brocade_PriorityGroups.QualifierFormats array are published in
the Brocade_CEEMapServiceCapabilities.QualifierFormatsSupported as an array of strings.
The value in the Brocade_PriorityGroups.QualifierFormats property is a subset of these
formats.
A CEE map can be empty. In such a case, the Brocade_CEEMap will be associated to a
Brocade_PriorityGroups instance in which the Brocade_PriorityGroups.ActivityQualifiers and
the Brocade_PriorityGroups.QualifierFormats properties will be empty.
72
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.
73
FIGURE 33
Registration
There is no conformance to any profile, and thus no registration.
74
Brocade 8470 supports Layer 3 mode of operation. The external ports and LAGs can be in
None, Layer 2 and Layer 3 Interface mode. However, the internal ports can only be in the Layer
2 Interface mode.
SetInstance of the interface mode on external ports to None and Layer 2 is supported.
NOTE
Support for setting of Layer 3 mode is not needed because adding of an IP address to an
ethernet port automatically puts the port in Layer 3 mode.
SetInstance of an interface mode on internal ports is not supported. They are default to Layer
2 mode.
Support for setting of Layer 3 mode is not required because adding of an IP address to a lag
automatically puts the lag in Layer 3 mode.
Setting on the OperationalEndPoint mode on internal ports is not supported. They are
defaulted to a converged mode.
The external ports are associated to PCSNetworkPort similar to those on the Brocade 8000
and FCOE10-24. However, the internal ports are not associated to PCSNetworkPort.
The LANendpoints of external ports can be part of a LAG similar to those on the Brocade 8000
and FCOE10-24. However, the lanendpoints of internal ports cannot be part of a LAG.
Data model
The following data model is supported. Figure 34 shows the classes and associations for discovery
and configuration of IPv4 addresses on CEE ports and LAGs.
75
FIGURE 34
76
Data model
Figure 35 shows the fabric switch partitioning subprofile data model.
FIGURE 35
Registration
Only instances of Brocade_PhysicalComputerSystem that are Virtual Fabrics-enabled are
associated to the Brocade_RegisteredSubProfile instance for fabric switch partitioning. Figure 36
shows the registration for fabric switch partitioning subprofile.
77
FC routing
FIGURE 36
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.
78
FC routing
FIGURE 37
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).
Both the xlate phantom and front phantom switches are represented as Brocade_Switch
instances. The front phantom domain and xlate phantom domain switches are associated by
the Brocade_SANActiveConnection. These phantom switches can be differentiated by
Brocade_Switch.OtherIdentifyingInfo property value (which would have the values as Translate
Domain, Front Domain, and None for translate phantom domain, front phantom domain, and
ordinary switches respectively).
The InteropMode property of front phantom domain and xlate phantom domain switches are
not populated.
79
FC routing
A port on FCR configured as an EX_Port is filtered out during port discovery on the backbone
for edge to edge device sharing.
There is one instance of NodeFCPort for every entry in the name server. The SystemName
property reflects the Fabric WWN of the fabric where the port exists. In case of FCR setup,
where the devices are imported or exported, there may be multiple instances of NodeFCPort
where DeviceID is the same, but SystemName differentiates each instance based on fabric
membership.
The property NetworkIDsConfigurable will indicate whether or not a port in the fabric is capable
of being configured.
From an SMI perspective, all fabrics which are physically connected are considered to be
contained in the same SAN.
If FCR setup where the backbone fabric and edge fabrics have been discovered Brocade_SAN.Name is the principal WWN of the backbone fabric.
If FCR setup where only one or more edge fabrics have been discovered - In the absence of the
backbone, there is no knowledge that the edge fabrics belong to one FCR backbone fabric, so
each edge fabric will be associated to its own SAN instance Brocade_SAN.Name which is the
principal WWN of that edge fabric.
Registration
Brocade_RegisteredProfile is mapped to Brocade_Switch using
Brocade_ElementConformsToProfile association class if edge switch is discovered along with its
backbone.
Figure 38 shows the SNIA Profile Registration model to advertise Inter-Fabric Routing profile.
80
FC routing
FIGURE 38
81
FC routing
FIGURE 39
82
FC routing
In the case of backbone edge device sharing, there is only one front phantom domain and two
xlate phantom domain switches. On the Edge fabric side, there is one front domain and one
xlate domain switch instance created. On the BackBone fabric side, there is only an xlate
domain switch created and no front phantom domain. Because the xlate phantom domain
switch is always behind the front phantom domain switch, the backbone switch itself
represents the front phantom domain. In addition to the logical port instance on the front
phantom in the edge fabric, FOS creates another instance of the logical port on the backbone
logical switch. This is the logical port instance that is connected to another logical port
instance on the xlate phantom through a SANActiveConnection.
83
FC routing
FIGURE 40
84
FC routing
85
FC routing
FIGURE 41
86
FC routing
Brocade Network Advisor SMI Agent classes added for this profile
Table 12 explains the classes and MOF files.
TABLE 12
Class
MOF file
Brocade_PCSNetworkPortSettings
BrocadePartitioning.mof
Brocade_PCSNetworkPortCapabilities
BrocadePartitioning.mof
Brocade_PCSServiceCapabilities
BrocadePartitioning.mof
Brocade_EthernetPort
BrocadePartitioning.mof
TABLE 13
Association class
MOF file
Brocade_PortSettingsForPCSNetworkPort
BrocadePartitioning.mof
Brocade_PortCapabilitiesForPCSNetworkPort
BrocadePartitioning.mof
Brocade_EthernetPortOfPCSNetworkPort
BrocadeEthernet.mof
Brocade_PCSCapabilities
BrocadePartitioning.mof
Brocade_EthernetPortInExtender
BrocadeExtender.mof
Brocade_SwitchFCPortOfEthernetPort
BrocadePartitioning.mof
Limitations
Brocade Network Advisor SMI Agent does not support MEOS switches.
In order to achieve a full topology discovery of edge fabrics, the backbone fabric must be
managed through the Brocade Network Advisor Server. If the backbone fabric is not managed
through the Brocade Network Advisor server, discovery is limited to the topology shown in
Figure 42.
You can modify the PreferredDomainID value for phantom switches only when the associated
backbone fabric is managed through Brocade Network Advisor.
87
FC routing
FIGURE 42
The PreferredDomainID value for phantom switches can be modified only if the associated
backbone fabric is managed through Brocade Network Advisor.
88
NOTE
The SMI Agent does not support the discovery of an Access Gateway-enabled switch as a seed
switch, using Extrinsic method, except for the Brocade Encryption Switch.
Node Port Initialized Virtualization (NPIV) allows a single Fibre Channel port to appear as multiple
distinct ports. It provides a separate port identification and security zoning within the fabric for
each operating system image. Each operating system image has its own unique physical port.
For additional information about Access Gateway, refer to the Access Gateway Administrators
Guide.
For additional information about NPIV, refer to the Fabric OS Administrators Guide.
Registration
Figure 43 shows the SNIA Profile Registration Profile model to advertise the NPIV profile.
FIGURE 43
When an Access Gateway switch exists with devices attached in the discovered fabric, the
Brocade_RegisteredProfile (N_Port Virtualizer) is mapped to Brocade_AccessGateWay using
Brocade_ElementConformsToProfile association class.
89
Data model
Figure 44 defines the data model and functions of the AG and NPIV.
FIGURE 44
90
AG class diagram
NOTE
The port statistics and the port rate statistic information modeled for the AGFCPorts will be
supported from FOS 5.3 onwards.
FIGURE 45
Brocade_SwitchFCPort has the property NPIVEnabled. The port supports connecting NPIV
devices if this property value is true.
91
The NPIVSupported property indicates the NPIV support for the FC port.
The MaxNPIVLogins property indicates the maximum number of NPIV logins supported on
the FC port. The value of MaxNPIVLogins is always set to 32.
The end device is represented as the instance of Brocade_Platform. The value of the property
Dedicated is Not Dedicated representing the HBA. The LogicalPortGroup instance is
represented as Brocade_Node and it is associated with Brocade_Platform by
Brocade_NodeInPlatform.
All the ports in end devices are represented as Brocade_NodeFCPort and it associates with
Brocade_Node by Brocade_PortInNode.
The virtualized ports associate with real ports of the end device using the
Brocade_NodeFCPortDependency association. The Brocade_NodeFCport is also associated
with the Brocade_Platform by Brocade_NodePortInPlatform.
The platform instance for the HBA is shown if the HBA is FDMI-enabled.
SANProtocolEndPoint of the switch is associated with the SANProtocolEndPoint of the end
device as Brocade_SANActiveConnection. There is a direct association between the switch and
the virtualized port of the end devices through Brocade_SANActiveConnection. Therefore, the
number of F_Port to N_Port connections is equal to the sum of virtualized ports and real port
of the end device.
92
FIGURE 46
AG Physical Package
Access Gateway
When a AG-capable switch is changed to AG, it will not act as a switch and it cannot be directly
discovered through Brocade Network Advisor. The port on the switch that is connected to AG is the
F_Port and the port on AG that has a connection from switch is the N_Port. AG is considered as a
node from the switchs perspective.
As shown in Figure 47, there are two connections from Switch1 to AG. There are two F_Ports on
switch F1 and F2 connected to ports N1 and N2 of AG. The AG is connected to three HBAs, so the
F_Ports F1, F2, and F3 on AG are connected to the ports n1, n2, and n3 of HBA1, HBA2, and HBA3
correspondingly. There is an internal mapping on AG as N1 is mapped with F1 and F2, and N2 is
mapped with F3.
93
HBA1
n1
AG
n2
F2
F3
HBA2
F1
Switch 1
N1
N2
F1
F2
n3
HBA3
FIGURE 47
AG mapping
The instance of Brocade_Platform with Dedicated property values as Not dedicated represents
the HBA attached to the AG. This platform instance is shown if the HBA is FDMI-enabled and
the hostname is known to Network Advisor. For more details, refer to the FC HBA profile on
page 50.
94
FIGURE 48
Host with AG
95
Switch 1
HBA1
n1
F1
AG
n2
F1
F2
F3
HBA2
Fabric 1
N1
N2
N3
N4
F2
Switch 2
n3
HBA3
FIGURE 49
Fabric 2
AG with NPIV
Figure 50 represents the AG with NPIV model where the switch is connected to AG and the AG is
connected to HBAs that has one NPIV-enabled device with two virtualized ports.
Figure 51 is the combination of AG and NPIV data models.
96
HBA1
n1
AG
n2
F2
F1
N1
N2
F3
HBA2
Switch 1
F1
F2
n3
Virtualized Ports
HBA3
NPIV Device
FIGURE 50
97
FIGURE 51
98
Figure 52 shows a simplified instance diagram to illustrate the combination of the AG and NPIV,
and Topology View features
FIGURE 52
The following Brocade Network Advisor SMI Agent classes are defined in
Brocade_AccessGateway.mof:
99
Brocade_AccessGateway
Brocade_AGFCPort
Brocade_AGFCPortStats
Brocade_AGFCPortStatisticsCollection
Brocade_AGFCPortRateStats
Brocade_PortRateStatsForAGFCPort
Brocade_PortStatsForAGFCPort
Brocade_AGFCPortStatsInAGFCPortStatisticsCollection
Brocade_AGFCPortStatisticsCollectionForAG
Brocade_AGNode
Brocade_AGSANProtocolEndPoint
Brocade_AGMgmtAccessPoint
Brocade_AGSoftwareIdentity
Brocade_AGWebGUIRemoteAccessPoint
Brocade_AGInFabric
Brocade_AGNodeInAG
Brocade_AGFCPortInAGNode
Brocade_AGFCPortInTrunk
Brocade_PortInAG
Brocade_AGFCPortSANProtocolEndPoint
Brocade_AGHostedSANAccessPoint
Brocade_AGSANActiveConnection
Brocade_AGHostedRemoteAccessPoint
Brocade_AGHostedMgmtAccessPoint
Brocade_AGSANProtocolEndPointLogicalIdentity
Brocade_NodeFCPortDependency
Brocade_EthernetAccessGateway
Brocade_EthernetPortInEthernetAccessGateway
Brocade_EthernetAGInEthernetAdminDomain
Brocade_EthernetAccessGatewayHostedLANEndPoint
Limitations
The following are the limitations of Brocade Network Advisor SMI Agent:
AG on Ethernet switch
- No Brocade_AGFCPort instances are discovered for the Virtual FCoE ports on the Ethernet
AG.
100
FRU profiles
AG on Brocade Encryption Switch, where the Brocade Encryption Switch AG is the Seed switch.
The loop devices are not supported when attached to AG.
The value of LLDP-DCBX for AG port if AG is not available in Brocade Network Advisor.
- The SMI Agent populates this property as Unknown in Brocade_EthernetAccessGateway
if the instance is retrieved through enumerateInstances.
The correct value of this property can obtained through the getInstance() intrinsic
operation only.
The Ethernet switch instance is not delivered if Ethernet switch is discovered through IP Tab
alone.
FRU profiles
The Fan, Power Supply, and Sensors (FRU) profiles model discovery of a switch's field-replaceable
units (FRUs).
Registration
Refer to Figure 53 for profile registration details.
Data model
Figure 53 shows the data model with the classes and properties that supports the FRU subprofiles.
101
FRU profiles
FIGURE 53
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.
102
Names
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, 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.
The following are the functions:
All the detached WWN names are supported by the Brocade SMI Agent.
Data model
A new extrinsic method is defined in the Brocade_Agent class.
103
104
Names
Chapter
Indications
In this chapter
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Alert indications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Life-cycle indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Introduction
The Brocade Network Advisor SMI Agent delivers events in the form of two types of indications:
alert indications and life-cycle indications.
Alert indications are used to represent all fabric events. To receive the alert indications, the clients
must first register with SNMP traps.
Life-cycle indications are delivered by the classes in reaction to a change in the status of a
connection such as, when elements (for example, switch or node) leave or join the fabric.
The Configuration tool allows you to enable mutual authentication for indications. If this is enabled,
all the indications are received over the HTTPS port. By default, the HTTPS is enabled without
mutual authentication.
Alert indications
Table 14 explains the supported alert indications.
105
Alert indications
TABLE 14
106
Message ID
Trigger
Property
Value
FC1
AlertingManagedElement
COP of Brocade_Fabric
AlertingElementFormat
COP
AlertType
Device Alert
OtherAlertType
N/A
AlertSubType
Database Change
Completed
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
SNIA
Message
MessageArguments
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
FC2
AlertingManagedElement
COP of Brocade_Fabric
AlertingElementFormat
COP
AlertType
Device Alert
OtherAlertType
N/A
AlertSubType
Config Enabled
PerceivedSeverity
5 (Major)
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
SNIA
Message
ZoneSet <ZoneSet
Name> was activated for
fabric <WWN>
MessageArguments
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Device Alert
OtherAlertType
N/A
AlertSubType
Switch modified
PerceivedSeverity
5 (Major)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
SNIA
Message
MessageArguments
FC5
107
Alert indications
TABLE 14
Trigger
Property
Value
FC6
AlertingManagedElement
COP of Brocade_Fabric
AlertingElementFormat
COP
AlertType
Device Alert
OtherAlertType
N/A
AlertSubType
PerceivedSeverity
4 (Minor)
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
SNIA
Message
MessageArguments
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Device Alert
OtherAlertType
N/A
AlertSubType
PerceivedSeverity
4 (Minor)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
SNIA
Message
MessageArguments
FC7
108
Message ID
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
FC8
AlertingManagedElement
COP of Brocade_Fabric
AlertingElementFormat
COP
AlertType
Device Alert
OtherAlertType
N/A
AlertSubType
PerceivedSeverity
5 (Major)
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
SNIA
Message
MessageArguments
AlertingManagedElement
COP of Brocade_Fabric
AlertingElementFormat
COP
AlertType
Environmental
OtherAlertType
N/A
AlertSubType
Config Disabled
PerceivedSeverity
Informational
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
SNIA
Message
MessageArguments
FC10
109
Alert indications
TABLE 14
110
Message ID
Trigger
Property
Value
Core6
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Security
OtherAlertType
N/A
AlertSubType
New Login
PerceivedSeverity
Informational
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
SNIA
Message
MessageArguments
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
Core6
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Security
OtherAlertType
N/A
AlertSubType
Logout
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
SNIA
Message
MessageArguments
111
Alert indications
TABLE 14
Trigger
Property
Value
Core8
AlertingManagedElement
COP of
Brocade_SwitchFCPort
AlertingElementFormat
COP
AlertType
Device Alert
OtherAlertType
Port Alert
AlertSubType
FC Port operational
status modified
PerceivedSeverity
5 (Major)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
SNIA
Message
<Device Unique
Identifier> status
changed to <Port
Status>
MessageArguments
SwitchFCPort WWN ,
Switch
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Security
OtherAlertType
N/A
AlertSubType
PerceivedSeverity
3 (Warning)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
SNIA
Message
MessageArguments
Core 10
112
Message ID
Alert indications
TABLE 14
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.
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Switch Alert
AlertSubType
Config Change
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
Configuration changed
for Switch <WWN>
MessageArguments
WWN = stringSwitch
WWN
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Switch Alert
AlertSubType
Track Change On
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
BRDC5
113
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRDC6
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Switch Alert
AlertSubType
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
AlertingManagedElement
COP of
Brocade_SwitchFCPort
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Port Alert
AlertSubType
Up
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
Port <PortWWN> of
Switch <SwitchWWN> is
up
MessageArguments
SwitchFCPort WWN
Switch WWN
BRCD7
114
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD8
AlertingManagedElement
COP of
Brocade_SwitchFCPort
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Port Alert
AlertSubType
Down
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
Port <PortWWN> of
Switch <SwitchWWN> is
down
MessageArguments
PortWWN =
SwitchFCPort WWN
Switch WWN=string
Switch WWN
AlertingManagedElement
COP of Brocade_Node
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Port Alert
AlertSubType
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
BRCD12
115
Alert indications
TABLE 14
Trigger
Property
Value
BRCD13
AlertingManagedElement
COP of Brocade_Node
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Port Alert
AlertSubType
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
AlertingManagedElement
COP of Brocade_Fabric
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Zone Alert
AlertSubType
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
Brocade
Message
MessageArguments
BRCD16
116
Message ID
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD17
AlertingManagedElement
COP of Brocade_Fabric
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Zone Alert
AlertSubType
PerceivedSeverity
Informational
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
A change in zoning
session status occurred
for fabric named
<WWN>
MessageArguments
AlertingManagedElement
COP of Brocade_Node
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Device Alert
AlertSubType
Registered
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
BRCD18
117
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD19
AlertingManagedElement
COP of Brocade_Node
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Device Alert
AlertSubType
Deregistered
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
AlertingManagedElement
COP of Brocade_FCPort
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Device Alert
AlertSubType
State Changed
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
BRCD20
118
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD21
AlertingManagedElement
COP of Brocade_Node
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Device Alert
AlertSubType
Database Change
Completed
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
Fabric WWN
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Switch Alert
AlertSubType
Firmware download
started
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
Firmware download
started for switch
<WWN>
MessageArguments
Switch WWN
BRCD24
119
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD25
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Switch Alert
AlertSubType
Firmware download
completed
PerceivedSeverity
5 (Major)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
Firmware download
completed for switch
<WWN>
MessageArguments
Switch WWN
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
HA Alert
AlertSubType
Failover completed
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
HA failover has
completed for Switch
<WWN>
MessageArguments
SwitchWWN
BRCD26
120
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD27
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Security
OtherAlertType
N/A
AlertSubType
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Security
OtherAlertType
N/A
AlertSubType
Account added
PerceivedSeverity
Informational
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
BRCD28
121
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD29
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Security
OtherAlertType
N/A
AlertSubType
Account deleted
PerceivedSeverity
Informational
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Security
OtherAlertType
N/A
AlertSubType
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
BRCD30
122
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD31
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Security
OtherAlertType
N/A
AlertSubType
Account membership
changed
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
Account username,
Switch WWN
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Security
OtherAlertType
N/A
AlertSubType
Password expiring
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
Switch WWN
BRCD32
123
Alert indications
TABLE 14
Trigger
Property
Value
BRCD33
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Security
OtherAlertType
N/A
AlertSubType
Password expired
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
Switch IP Address
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Connection Alert
AlertSubType
Connection deactivated
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
BRCD35
124
Message ID
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD42
enumerateInstanceNames or
enumerateInstances failed.
Query: SELECT * FROM
CIM_AlertIndication WHERE
OwningEntity=BROCADE and
MessageID=BRCD42
AlertingManagedElement
AlertingElementFormat
COP
AlertType
Processing Error
OtherAlertType
N/A
AlertSubType
N/A
PerceivedSeverity
2 (Informational)
ProbableCause
49
SystemCreationClassName
Brocade_ManagementS
erver
SystemName
HostName
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
A processing error
occurred for method
<method name>
MessageArguments
method name =
enumerateInstanceNam
es or associatorNames
and so on.
AlertingManagedElement
COP of Brocade_Node
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Port Alert
AlertSubType
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
Fabric WWN
NOTE: Mapping of
AlertingManagedElement
property
AlertingManagedElement for
enumerateInstanceNames and
enumerateInstances, path of
class which is in error. For
example,
enumerateInstanceNames on
Brocade_Fabric has this as
CIMObjectPath (Brocade_Fabric,
root/brocade1). In case of
associatorNames, associators,
referenceNames, and references
path, they have the actual
CIMObjectPath of the input.
BRCD43
125
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD44
AlertingManagedElement
COP of Brocade_Node
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Port Alert
AlertSubType
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
Fabric WWN
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Blade Alert
AlertSubType
Blade Faulted
PerceivedSeverity
5 (Major)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
Switch WWN
BRCD46
126
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD48
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other Alert
OtherAlertType
Fabric Watch
AlertSubType
Threshold Above
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
N/A
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other Alert
OtherAlertType
Fabric Watch
AlertSubType
Threshold Below
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
N/A
BRCD49
127
Alert indications
TABLE 14
Trigger
Property
Value
BRCD51
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other Alert
OtherAlertType
Fabric Watch
AlertSubType
Threshold In Between
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
N/A
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other Alert
OtherAlertType
Fabric Watch
AlertSubType
Threshold Change
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
N/A
BRCD52
128
Message ID
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD53
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Switch Alert
AlertSubType
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Switch Alert
AlertSubType
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
Switch WWN
BRCD54
129
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD56
AlertingManagedElement
COP of Brocade_Fabric
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
AlertSubType
VF FID Conflict
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
AlertingManagedElement
COP of Brocade_Fabric
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
FRU Alert
AlertSubType
FRU Faulted
PerceivedSeverity
5 (Major)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
BRCD57
130
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD58
AlertingManagedElement
COP of
Brocade_ManagementS
erver
AlertingElementFormat
AlertType
OtherAlertType
N/A
AlertSubType
PerceivedSeverity
3 (Degraded or Warning)
ProbableCause
123
SystemCreationClassName
Brocade_ManagementS
erver
SystemName
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
131
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD59
AlertingManagedElement
COP of
Brocade_ManagementS
erver
AlertingElementFormat
AlertType
OtherAlertType
N/A
AlertSubType
PerceivedSeverity
6 (Critical)
ProbableCause
123
SystemCreationClassName
Brocade_ManagementS
erver
SystemName
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Switch Alert
AlertSubType
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Switch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
BRCD60
132
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD61
AlertingManagedElement
COP of Brocade_LAG
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
AlertSubType
Config enabled
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_
EthernetSwitch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
AlertingManagedElement
COP of Brocade_LAG
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
AlertSubType
Config disabled
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_
EthernetSwitch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
BRCD62
133
Alert indications
TABLE 14
Trigger
Property
Value
BRCD63
AlertingManagedElement
COP of Brocade_LAG
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
AlertSubType
Config enabled
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_
EthernetSwitch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
AlertingManagedElement
COP of Brocade_LAG
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
AlertSubType
Config removed
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_
EthernetSwitch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
BRCD64
134
Message ID
Alert indications
TABLE 14
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
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
EthernetPort <portmac>
enabled on
EthernetSwitch <Switch
IP>
MessageArguments
AlertingManagedElement
COP of Brocade_
EthernetPort
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Port Alert
AlertSubType
Down
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_
EthernetSwitch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
EthernetPort <portmac>
disabled on
EthernetSwitch <Switch
IP>
MessageArguments
BRCD66
TE port disabled
Query: SELECT * FROM
CIM_AlertIndication WHERE
OwningEntity=BROCADE and
MessageID=BRCD66
135
Alert indications
TABLE 14
136
Message ID
Trigger
Property
Value
BRCD67
AlertingManagedElement
COP of Brocade_
EthernetPort
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Port Alert
AlertSubType
Config enabled
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_
EthernetSwitch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
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
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
137
Alert indications
TABLE 14
138
Message ID
Trigger
Property
Value
BRCD69
AlertingManagedElement
COP of Brocade_
EthernetPort
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Port Alert
AlertSubType
Config enabled
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_
EthernetSwitch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD70
AlertingManagedElement
COP of Brocade_
EthernetPort
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Port Alert
AlertSubType
Config removed
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_
EthernetSwitch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
139
Alert indications
TABLE 14
Trigger
Property
Value
BRCD71
AlertingManagedElement
COP of Brocade_
EthernetPort
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Port Alert
AlertSubType
Config enabled
PerceivedSeverity
2 (Informational)l
ProbableCause
123
SystemCreationClassName
Brocade_
EthernetSwitch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
LLDP enabled on
EthernetPort <portmac>
on EthernetSwitch <core
switch IP>
MessageArguments
AlertingManagedElement
COP of
Brocade_switchFCPort
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Port Alert
AlertSubType
Up
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_EthernetSwitch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
BRCD72
140
Message ID
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD73
AlertingManagedElement
COP of Brocade_
switchFCPort
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Port Alert
AlertSubType
Down
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_EthernetSwitch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
AlertingManagedElement
COP of Brocade_VLAN
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
AlertSubType
Config enabled
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_
EthernetSwitch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
CEEACL<Policy Name>
assigned to VLAN<VLAN
No> on EthernetSwitch
<core switch IP>
MessageArguments
BRCD74
141
Alert indications
TABLE 14
142
Message ID
Trigger
Property
Value
BRCD75
AlertingManagedElement
COP of Brocade_VLAN
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
AlertSubType
Config removed
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_
EthernetSwitch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
CEEACL<Policy Name>
removed from
VLAN<VLAN ID> on
EthernetSwitch <core
switch IP>
MessageArguments
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD76
AlertingManagedElement
COP of Brocade_VLAN
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
AlertSubType
Config Changed
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_
EthernetSwitch
SystemName
Switch WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
For I and II
LAG ID, VLAN ID
For III and IV
Port MAC address, VLAN
ID
143
Alert indications
TABLE 14
Message ID
Trigger
Property
Value
BRCD101
AlertingManagedElement
COP of Brocade_Fabric
AlertingElementFormat
COP
AlertType
Device Alert
OtherAlertType
N/A
AlertSubType
PerceivedSeverity
2 (Informational)
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
BROCADE
Message
MessageArguments
AlertingManagedElement
COP of Brocade_Switch
AlertingElementFormat
COP
AlertType
Other
OtherAlertType
Zone alert
AlertSubType
SANZone activation
failed
PerceivedSeverity
5 (Major)
ProbableCause
123
SystemCreationClassName
Brocade_Fabric
SystemName
Fabric WWN
ProviderName
Brocade_AlertIndication
Provider
OwningEntity
Brocade
Message
SANZone activation
failed for fabric <WWN>
MessageArguments
Fabric WWN
BRCD102
NOTE
For indications from BRCD61 to BRCD76:
All CEE alert indications and life-cycle indications are only applicable for FOS switches (Brocade
8000 switch and FCOE10-24 blade) with versions from v6.4.0. To get all CEE indications, make sure
that CEE indication is enabled in the switch.
144
Life-cycle indications
Life-cycle indications
Table 15 explains the supported life-cycle indications.
TABLE 15
Query
Indication type
Notes
CIM_InstCreation
CIM_InstDeletion
CIM_InstModification
CIM_InstModification
CIM_InstModification
CIM_InstCreation
CIM_InstDeletion
CIM_InstCreation
CIM_InstDeletion
CIM_InstCreation
CIM_InstDeletion
CIM_InstCreation
CIM_InstDeletion
Complete
CIM_InstModification
Applicable to zoning in
SessionControlWithJob and
ActivateZoneSetWithJob
CIM_InstModification
Applicable to zoning in
SessionControlWithJob and
ActivateZoneSetWithJob
CIM_InstModification
Applicable to zoning in
SessionControlWithJob and
ActivateZoneSetWithJob
145
4
TABLE 15
Life-cycle indications
Query
Indication type
Notes
CIM_InstModification
Applicable to zoning in
SessionControlWithJob and
ActivateZoneSetWithJob
CIM_InstCreation
Applicable to zoning in
SessionControlWithJob and
ActivateZoneSetWithJob
CIM_ InstModification
CIM_InstCreation
CIM_InstDeletion
CIM_InstModification
CIM_InstCreation
CIM_InstDeletion
CIM_InstModification
CIM_InstCreation
CEEMap created
CIM_InstDeletion
CEEMap deleted
CIM_InstCreation
CIM_InstModification
CIM_InstDeletion
CIM_InstCreation
LAG created
CIM_InstModification
CIM_InstDeletion
LAG deleted
146
Life-cycle indications
TABLE 15
Query
Indication type
Notes
CIM_InstCreation
VLAN created
CIM_InstDeletion
VLAN deleted
CIM_InstModification
NOTE
Sensors are built in with other FRU elements; and thus InstanceCreation, InstanceDeletion, and
InstanceModification indications are not supported.
When a rule is removed from the ACL policy, indication populates only the sequence number. When
PG ID is removed from CEE map, indication populates only the PG ID. In both the cases, the
indication populates default values for the other properties (priority flow control, bandwith).
147
148
Life-cycle indications
Appendix
Table 16 lists the Brocade Network Advisor SMI Agent error codes.
TABLE 16
Error codes
Error code
Description
4096
4099
10001
Database error
10002
Unknown error
10003
11001
11101
11301
11601
11602
12001
12003
12004
12005
12101
12102
12104
12301
12401
12402
12403
12503
12504
12505
13001
13101
13102
13103
13301
149
TABLE 16
150
Error code
Description
13401
13402
13403
13404
13405
13407
13408
13503
13504
13505
13506
13507
13508
13509
14001
14101
14102
14301
14401
14402
15001
15101
15301
16001
16002
16003
16004
16101
16102
16103
16104
16105
16106
16107
16108
TABLE 16
Error code
Description
16109
16110
16111
16112
16113
16114
16115
16116
16117
16118
16119
16120
16121
16122
16123
16124
16125
16126
16301
16501
16502
16503
17001
17101
17301
18101
18102
18103
18301
19001
19002
19003
19004
19005
19006
151
TABLE 16
152
Error code
Description
19007
19008
19009
19010
19011
19012
19013
19014
19015
19016
19017
19018
19019
19020
19021
19022
19023
19024
19025
19026
19027
19028
19029
19030
19031
19032
19033
19034
19035
19036
19037
19038
19039
19040
19041
19042
TABLE 16
Error code
Description
19043
19044
19045
19046
20001
20101
20102
20103
20301
20302
20401
20402
20403
21101
21102
21301
22001
22101
Unkown error
22301
23101
23301
32770
32772
32773
32775
32782
32783
32788
32789
32790
32791
40001
40002
60001
60002
AD exists error
60003
153
TABLE 16
154
Error code
Description
60004
60005
60006
60007
60008
60009
60010
60011
60012
Invalid IP address
60013
60014
60015
60016
Unsupported vendor
60017
60018
60019
60020
60021
60022
60023
60024
60025
60026
60027
60028
60029
60030
Request failed
60031
60032
60033
60034
60035
HTTP error
60036
60037
60038
60039
TABLE 16
Error code
Description
60041
Unknown error
60042
Unsupported edition
60043
60044
60045
60046
60047
60048
60050
60051
60052
60053
60054
Switch unmanageable
60055
60056
Unknown error
60057
HTTP moved
60058
60059
60060
60061
60062
Insufficient AD privilege
60063
60064
No chassis access
60065
Insufficient privilege
60066
60067
60068
AD detected
60069
HTTP unavailable
60070
60071
Connection failure
60072
60073
60074
60075
60076
60077
155
TABLE 16
156
Error code
Description
60078
60079
60080
Unknown error
60081
Discovery failed
60082
Switch initializing
60083
60084
Discovery redundant
60085
60086
60087
60088
60089
60090
60091
60092
60093
60094
60095
60096
60097
Discovery AD detected
60098
60099
Switch timeout
60100
60101
60102
60103
60104
60105
60106
60107
Connection lost
60108
60109
Not capable
60110
60111
60112
TABLE 16
Error code
Description
60113
Switch unmanageable
60114
60115
60116
Partially discovered
60117
Insufficient VF_PRIVILEGE
60118
70001
70002
70003
70004
70005
70006
70007
70008
70009
Redundant status
70010
70011
70012
70013
70014
70015
70016
70017
No adapter is found
70018
70019
Illegal argument
99010
99011
157
158