Brocade, Brocade Assurance, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, MLX, NetIron, SAN Health, ServerIron,
TurboIron, VCS, and VDX are registered trademarks, and AnyIO, Brocade One, CloudPlex, Effortless Networking, ICX, NET Health,
OpenScript, and The Effortless Network are trademarks of Brocade Communications Systems, Inc., in the United States and/or in
other countries. Other brands, products, or service names mentioned may be trademarks of their respective owners.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning
any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to
this document at any time, without notice, and assumes no responsibility for its use. This informational document describes
features that may not be currently available. Contact a Brocade sales office for information on feature and product availability.
Export of technical data contained in this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with
respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that
accompany it.
The product described by this document may contain “open source” software covered by the GNU General Public License or other
open source license agreements. To find out which open source software is included in Brocade products, view the licensing
terms applicable to the open source software, and obtain a copy of the programming source code, please visit
http://www.brocade.com/support/oscd.
Brocade Communications Systems, Incorporated
Corporate and Latin American Headquarters
Brocade Communications Systems, Inc.
130 Holger way
San Jose, CA 95134
Tel: 1-408-333-8000
Fax: 1-408-333-8101
E-mail: info@brocade.com
European Headquarters
Brocade Communications Switzerland Sàrl
Centre Swissair
Tour B - 4ème étage
29, Route de l'Aéroport
Case Postale 105
CH-1215 Genève 15
Switzerland
Tel: +41 22 799 5640
Fax: +41 22 799 5641
E-mail: emea-info@brocade.com
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
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
Document TitlePublication Number Summary of ChangesPublication Date
Fabric OS MIB Reference53-1001768-01Updated to support the
Brocade FC8-64 port blade
and Brocade VA-40FC. Added
BD MIB details,
swConnUnitPortStatExtention
Table, swMemUsageLimit1,
swMemUsageLimit3,
swFabricReconfigTrap,
swFabricSegmentTrap, and
swExtTrap.
April 2005
January 2006
September 2006
June 2007
October 2007
March 2008
November 2008
July 2009
March 2010
Fabric OS MIB Referenceiii
53-1002750-01
Document TitlePublication Number Summary of ChangesPublication Date
Fabric OS MIB Reference53-1002151-01Updated to support Brocade
6510, Brocade DCX 8510-8
Backbone, and Brocade DCX
8510-4 Backbone. Added
FibreAlliance extension MIB,
SNMPv2 MIB,
ipAddressTable, MIBs for
swConnUnitPortStatExtention
Table, and switch traps.
Fabric OS MIB Reference53-1002750-01Updated to support Brocade
6505, Brocade 6520, and
Brocade VA-40FC. Added
swDeviceStatusTrap,
swConnUnitPCSErrorCounter,
and swConnUnitPortTable.
Updated the MIB objects that
are not supported or
deprecated for this release.
Customized traps are
obsoleted.
April 2011
December 2012
ivFabric OS MIB Reference
53-1002750-01
Contents
About This Document
How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
This document is organized to help you find the information that you want as quickly and easily as
possible.
The document contains the following components:
• Chapter 1, “Understanding Brocade SNMP,” provides an introduction to Brocade SNMP and
MIBs.
• Chapter 2, “MIB-II (RFC1213-MIB),” provides information for MIB-II.
• Chapter 3, “RMON MIB Objects,” provides information for RMON MIB object types.
• Chapter 4, “FE MIB Objects,” provides information for FE MIB object types.
• Chapter 5, “Entity MIB Objects,” provides information for Entity MIB object types.
• Chapter 6, “SW-MIB Objects,” provides information for FC Switch MIB (SW-MIB) object types.
• Chapter 7, “High-Availability MIB Objects,” provides information for High-Availability MIB object
types.
• Chapter 8, “FICON MIB Objects,” provides information for FICON MIB (LINK-INCIDENT-MIB)
object types.
• Chapter 9, “FibreAlliance MIB Objects,” provides information for FibreAlliance MIB
(FCMGMT-MIB) object types.
• Chapter 10, “FibreAlliance Extension MIB Objects,” provides information for FibreAlliance
extension MIB object types.
• Chapter 11, “FCIP MIB Objects,” provides information on FCIP MIB object types.
• Chapter 12, “iSCSI MIB Objects,” provides information on iSCSI MIB object types.
• Chapter 13, “SNMPv2 MIB Objects,” provides information on SNMPv2 MIB object types.
• Chapter 14, “USM MIB Objects,” provides information on USM MIB object types.
Fabric OS MIB Referencexiii
53-1002750-01
Supported hardware and software
• Chapter 15, “IEEE 802.1x PAE MIB Objects,” provides information on IEEE 802.1x PAE MIB
object types.
• Chapter 16, “LLDP MIB Objects,” provides information on LLDP MIB object types.
• Chapter 17, “IEEE 802.3 LAG MIB Objects,” provides information on IEEE 802.3 LAG MIB
object types.
• Chapter 18, “Bridge-MIB Objects,” provides information on Bridge-MIB object types.
• Chapter 19, “BD MIB Objects,” provides information on BD MIB object types.
• Appendix A, “MIB Object Groupings,” is a function-based listing of MIB objects.
• Appendix B, “Mapping of CLI Counters to MIB Objects,” maps the CLI counters to the
corresponding MIB objects.
Supported hardware and software
In those instances in which 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 Fabric OS vx.x.x, documenting all possible
configurations and scenarios is beyond the scope of this document.
This document supports Brocade Fabric OS version 7.1.0 and earlier versions, and all switches
supporting these Fabric OS versions, including:
• Brocade 300
• Brocade 4100
• Brocade 4900
• Brocade 5000
• Brocade 5100
• Brocade 5300
• Brocade 5410
• Brocade 5424
• Brocade 5450
• Brocade 5460
• Brocade 5470
• Brocade 5480
• Brocade 6505
• Brocade 6510
• Brocade 6520
• Brocade 7500
• Brocade 7500E
• Brocade 7600
• Brocade VA-40FC
• Brocade 7800 Extension Switch
xivFabric OS MIB Reference
53-1002750-01
Supported hardware and software
• Brocade 8000 FCoE Switch
• Brocade Encryption Switch
• Brocade DCX Backbone and Brocade DCX-4S Backbone
-FA4-18 Fibre Channel application blade
-FCOE10-24 DCX Blade
-FS8-18 Encryption Blade
-FC8-16 port blade
-FC8-32 port blade
-FC8-48 port blade
-FC8-64 port blade
-FX8-24 DCX Extension Blade
• Brocade 48000 director
-FA4-18 Fibre Channel application blade
-FC4-16 port blade
-FC4-16IP blade
-FC4-32 port blade
-FC4-48 port blade
-FC8-16 port blade
-FC8-32 port blade
-FC8-48 port blade
-FC10-6 port blade
-FR4-18i router blade
• Brocade VA-40FC
• Brocade DCX 8510-8 Backbone and Brocade DCX 8510-4 Backbone
-FC8-64 port blade
-FC16-32 port blade
-FC16-48 port blade
-FCOE10-24 DCX Blade
-FS8-18 Encryption Blade
-FX8-24 DCX Extension Blade
The following platforms can interoperate with switches running Fabric OS v7.0.0, but cannot load
Fabric OS v7.0.0:
• Brocade 4100
• Brocade 4900
• Brocade 5000
• Brocade 7500/7500E
• Brocade 7600
• Brocade 48000
The following blades are not supported in any chassis operating with Fabric OS v7.0.0:
Fabric OS MIB Referencexv
53-1002750-01
What’s new in this document
• FA4-18
• FC4-16IP
• FC4-16
• FC4-32
• FC4-48
What’s new in this document
The following changes have been made since this document was last released:
• Information that was added:
-Support for Brocade 6505, Brocade 6520, and Brocade VA-40FC
For further information about new features and documentation updates for this release, refer to
the release notes.
xviFabric OS MIB Reference
53-1002750-01
Document conventions
NOTE
ATTENTION
CAUTION
DANGER
This section describes text formatting conventions and important notices formats.
Text formatting
The narrative-text formatting conventions that are used in this document are as follows:
bold textIdentifies command names
italic textProvides emphasis
code textIdentifies CLI output
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 often all
lowercase. Otherwise, this manual specifically notes those cases in which a command is case
sensitive.
Document conventions
Identifies the names of user-manipulated GUI elements
Identifies keywords and operands
Identifies text to enter at the GUI or CLI
Identifies variables
Identifies paths and Internet addresses
Identifies document titles
Identifies syntax examples
Notes, cautions, and warnings
The following notices and statements are used in this manual. They are listed below in order of
increasing severity of potential hazards.
A note provides a tip, guidance, or advice, emphasizes important information, or provides a
reference to related information.
An Attention statement indicates potential damage to hardware or data.
A Caution statement alerts you to situations that can be potentially hazardous to you or cause
damage to hardware, firmware, software, or data.
A Danger statement indicates conditions or situations that can be potentially lethal or extremely
hazardous to you. Safety labels are also attached directly to products to warn of these conditions
or situations.
Fabric OS MIB Referencexvii
53-1002750-01
Notice to the reader
Key terms
For definitions specific to Brocade and Fibre Channel, see the technical glossaries on MyBrocade.
See “Brocade resources” on page xviii for instructions on accessing MyBrocade.
For definitions of SAN-specific terms, visit the Storage Networking Industry Association online
dictionary at:
http://www.snia.org/education/dictionary
Notice to the reader
This document may contain references to the trademarks of the following corporations. These
trademarks are the properties of their respective companies and corporations.
These references are made for informational purposes only.
TABLE 1
CorporationReferenced Trademarks and Products
Microsoft CorporationWindows, Windows NT, Internet Explorer
Oracle CorporationOracle, Java
Additional information
This section lists additional Brocade and industry-specific documentation that you might find
helpful.
Brocade resources
To get up-to-the-minute information, go to http://my.brocade.com and register at no cost for a user
ID and password.
White papers, online demonstrations, and data sheets are available through the Brocade website
at:
For additional Brocade documentation, visit the Brocade website:
http://www.brocade.com
Release notes are available on the MyBrocade website and are also bundled with the Fabric OS
firmware.
Other industry resources
For additional resource information, visit the Technical Committee T11 website. This website
provides interface standards for high-performance and mass storage applications for Fibre
Channel, storage management, and other applications:
http://www.t11.org
xviiiFabric OS MIB Reference
53-1002750-01
For information about the Fibre Channel industry, visit the Fibre Channel Industry Association
website:
http://www.fibrechannel.org
Getting technical help
Contact your switch supplier for hardware, firmware, and software support, including product
repairs and part ordering. To expedite your call, have the following information immediately
available:
1. General Information
• Switch model
• Switch operating system version
• Software name and software version, if applicable
• Error numbers and messages received
• supportSave command output
• Detailed description of the problem, including the switch or fabric behavior immediately
following the problem, and specific questions
• Description of any troubleshooting steps already performed and the results
• Serial console and Telnet session logs
• syslog message logs
Getting technical help
2. Switch Serial Number
The switch serial number and corresponding bar code are provided on the serial number label,
as illustrated below:
VA-40FC, and Brocade Encryption Switch—On the switch ID pull-out tab located inside the
chassis on the port side on the left
• Brocade 5000—On the switch ID pull-out tab located on the bottom of the port side of the
switch
• Brocade 5410, 5424, 5450, 5460, 5470, 5480—Serial number label attached to the
module
• Brocade 7600—On the bottom of the chassis
• Brocade 48000—Inside the chassis next to the power supply bays
• Brocade DCX and 8510-8—On the bottom right on the port side of the chassis
• Brocade DCX-4S and 8510-4—On the bottom right on the port side of the chassis, directly
above the cable management comb
3. World Wide Name (WWN)
Fabric OS MIB Referencexix
53-1002750-01
Document feedback
Use the licenseIdShow command to display the WWN of the chassis. If you cannot use the
licenseIdShow command because the switch is inoperable, you can get the WWN from the
same place as the serial number, except for the Brocade DCX. For the Brocade DCX, access the
numbers on the WWN cards by removing the Brocade logo plate at the top of the nonport side
of the chassis.
Document feedback
Because quality is our first concern at Brocade, 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 and as much detail as possible about your comment,
including the topic heading and page number and your suggestions for improvement.
The Simple Network Management Protocol (SNMP) is an industry-standard method of monitoring
and managing network devices. This protocol promotes interoperability because SNMP-capable
systems must adhere to a common set of framework and language rules.
Understanding the components of SNMP makes it possible to use third-party tools to view, browse,
and manipulate Brocade switch variables (MIBs) remotely as well as to set up an enterprise-level
management process. Every Brocade switch and director supports SNMP.
Recipients for SNMP traps are restricted according to security levels. Security levels are selected
and set for a switch using the snmpconfig --set seclevel command. To select and set SNMP security
levels, issue the command snmpconfig --set seclevel after having logged in to the switch as admin.
The following example sets the SNMP security level to 1 (authentication only). This setting allows all
SNMPv1 users to perform GET and SET operations on MIBs, but creates an exception for SNMPv3
users that do not have authentication and privacy privileges (noAuthnoPriv).
switch:admin> snmpconfig --set seclevel
Select SNMP Security Level
(0 = No security, 1 = Authentication only, 2 = Authentication and Privacy, 3 =
sxNo Access): (0..3) [0]
Select SNMP SET Security Level
(0 = No security, 1 = Authentication only, 2 = Authentication and Privacy, 3 =
No Access): (0..3) [0]
Tab le 2 shows the security level options.
Fabric OS MIB Reference1
53-1002750-01
Understanding SNMP basics
Agent
Management Station
SNMP
MIB
Management Station
Agent
get, getnext, set
reply
TRAP
Management Station
Agent
1
TABLE 2Security level options
Security level ProtocolQuery behaviorTraps
No security [0]
(noAuthnoPriv)
Authentication only [1]
(authNoPriv)
Authentication and
Privacy [2]
(authPriv)
No Access [3]SNMPv1
SNMPv1
SNMPv3
SNMPv1
SNMPv3
SNMPv1
SNMPv3
SNMPv3
Understanding SNMP basics
Every Brocade switch carries an agent and management information base (MIB), as shown in
Figure 1. The agent accesses information about a device and makes it available to an SNMP
network management station.
FIGURE 1SNMP structure
Allowed.
Allowed.
Allowed.
All SNMPv3 users allowed except
noAuthNoPriv users.
Not allowed.
Only SNMPv3 users with authPriv
privilege are allowed.
Not allowed.Not Sent.
Sent.
Sent.
Sent.
Sent for all SNMPv3 users
except noAuthNoPriv users.
Not Sent.
Sent only for authPriv users.
When active, the management station can get information or set information when it queries an
agent. SNMP commands, such as get, set, getnext, and getresponse, are sent from the
management station, and the agent replies once the value is obtained or modified (Figure 2).
Agents use variables to report such data as the number of bytes and packets in and out of the
device, or the number of broadcast messages sent and received. These variables are also known
as managed objects. All managed objects are contained in the MIB.
FIGURE 2SNMP query
The management station can also receive traps, unsolicited messages from the switch agent if an
unusual event occurs (Figure 3). For more information, refer to “Understanding SNMP traps” on
page 4.
FIGURE 3SNMP trap
2Fabric OS MIB Reference
53-1002750-01
Understanding SNMP basics
mgmt (2)
sysObjectID (2)
iso (1)
org (3)
Brocade SW MIB
1.3.6.1.4.1.1588.2.1.1.1
dod (6)
internet (1)
experimental (3)
fcmgmt (94)
connSet (1)
enterprise (1)
private (4)
bcsi (1588)
mib-2 (1)
interface (2)
sysDescr (1)
system (1)
directory (1)
1
The agent can receive queries from one or more management stations and can send traps to up to
six management stations.
Understanding MIBs
The management information base (MIB) is a database of monitored and managed information on
a device, in this case a Brocade switch. The MIB structure can be represented by a tree hierarchy.
The root splits into three main branches: International Organization for Standardization (ISO),
Consultative Committee for International Telegraph and Telephone (CCITT), and joint ISO/CCITT.
These branches have short text strings and integers (OIDs) to identify them. Text strings describe
object names, while integers allow software to create compact, encoded representations of the
names.
Each MIB variable is assigned an object identifier (OID). The OID is the sequence of numeric labels
on the nodes along a path from the root to the object. For example, as shown in Figure 4, the
Brocade SW.MIB OID is:
The other branches are part of the standard MIBs, and the portions relevant to configuring SNMP
on a Brocade switch are referenced in the remainder of this reference.
Fabric OS MIB Reference3
53-1002750-01
FIGURE 4Brocade MIB tree location
Use a MIB browser to access the MIB variables: all MIB browsers perform queries and load MIBs.
Understanding SNMP basics
NOTE
1
Since different vendors vary the information in their private enterprise MIBs, it is necessary to verify
their information. The Fibre Channel MIB standards dictate that certain information be included in
all MIBs: it is the vendors’ responsibility to follow the standards. The standards are as follows:
• FibreAlliance (FA) MIB: Brocade supports v4.4. and later releases.
• Fabric Element (FE) MIB: accepted by the Internet Engineering Task Force (IETF).
Once loaded, the MAX-ACCESS provides access levels between the agent and management station.
The access levels are as follows:
• not accessible
• read create
• read only - Public
Brocade supports FE_RFC2837.mib under the MIB-II branch in Fabric OS v7.1.0, v7.0.0,
v6.4.1_fcoe, v6.4.0, v6.3.0, v6.2.0, v6.1.2_CEE, v6.1.0, and v6.0.0. The latest version of the
FE MIB references the FRAMEWORK.MIB and, based on the MIB browser, it is necessary to
load this MIB before the FE.MIB. For more information, refer to “Loading Brocade MIBs” on
page 7.
You cannot read or write to this variable.
Specifies a tabular object that can be read, modified, or created as a new row in a table.
You can only monitor information.
• read-write - Private
You can read or modify this variable.
• accessible-to-notify
You can read this information only through traps.
Understanding SNMP traps
An unsolicited message that comes to the management station from the SNMP agent on the
device is called a trap. Brocade switches send traps out on UDP port 162 and to any configured
port. In order to receive traps, the management station IP address and severity level must be
configured on the switch. Up to six trap recipients can be configured using Web Tools or the
snmpConfig command. You can define a different message severity level for each recipient so that
some recipients receive all trap messages and others receive only the most critical.
Due to design limitation, IP address validation cannot be done for trap recipients.
There are two main MIB trap choices:
• FibreAlliance MIB trap - Associated with the Fibre Alliance MIB (FA-MIB), this MIB manages SAN
switches and devices from any company that complies with Fibre Alliance specifications.
• Brocade-specific MIB trap - Associated with the Brocade-specific Brocade MIB (SW-MIB),
manages Brocade switches only.
There is some overlap in the functionality of these MIBs. If you enable both SW-MIB and FA-MIB
traps, you could receive duplicate messages for the switch events that trigger the trap.
4Fabric OS MIB Reference
53-1002750-01
Understanding SNMP basics
You can also use these additional MIBs and their associated traps: HA-MIB; FICON-MIB; and
SWEXTTRAP. In Fabric OS v6.4.0, you can use the snmpConfig command to enable or disable all
the MIBs.
An event trap (swEventTrap, connUnitEventTrap, or swFabricWatchTrap) is basically an error
message (errShow output) that is SNMP-formatted and delivered.
1
FA traps
Consider enabling the FA traps if you want to use SNMP to monitor multiple connectivity units,
including Brocade switches.
The switchStatusPolicySet command determines the FA-TRAP switch status-related outputs:
• connUnitStatusChange
This trap is generated by Fabric watch such that only the swUnitsStatusChange is controlled by
switchStatusPolicySet command.
• connUnitSensorStatusChange
This trap is generated by any sensor event.
• connUnitPortStatusChange
This trap sends the instance of connUnitPortName as part of the trap; the instance string is
NULL, if the port name is not defined for the specified port.
• connUnitEventTrap
All the external traps gets converted into swEventTrap except for AN-1006, AUTH-3001 to
AUTH-3008, FW-3001, SEC-3001 to SEC-3034, and SEC-3044 to SEC-3048 RASlog messages.
Events in the Error Log of a severity at or above the configured threshold will generate SNMP traps.
The Fibre Alliance Trap (FA-TRAP) can be configured to send traps using the snmpConfig command.
For more information on this command, refer to the Fabric OS Command Reference.
HA traps
Consider enabling these traps to monitor field-replaceable unit (FRU) status and control processor
(CP) status when you have a Brocade director in your environment:
• fruStatusChanged
This trap is generated by a FRU status change, such as a switch reboot or disabling or enabling
a FRU component such as fandisable, fanenable and so on.
• cpStatusChanged
This trap is generated by a change in the status of a CP, including a reboot or firmware
download.
• fruHistoryTrap
This trap is generated when a FRU is added or removed. It is not generated when standby CP is
removed.
The high availability trap (HA-TRAP) can be configured to send traps using the snmpConfig
command. For more information on this command, refer to the Fabric OS Command Reference.
Fabric OS MIB Reference5
53-1002750-01
Understanding SNMP basics
1
SW traps
There are fourteen specific traps defined in Brocade SW-TRAP.
1. swfault (no longer supported)
2. swSensorScn (no longer supported)
3. swFCPortScn
4. swEventTrap
5. swFabricWatchTrap
6. swTrackChangesTrap
This trap is generated by a port state change.
This trap is generated by any switch event reported to the system error log.
The desired severity level is introduced to filter a swEvent trap based on the severity level.
This trap is generated when any Fabric Watch threshold is reached.
The desired severity level is introduced to filter a swFabricWatchTrap based on the severity
level.
This trap is generated by a login or a logout.
7. swIPv6ChangeTrap
This trap is generated when an IPv6 address status change event occurs. It is generated only
when IPv6 stateless state changes to the deprecation state and not for address change
notification.
8. swPmgrEventTrap
This trap is generated when any partition manager change happens.
9. swFabricReconfigTrap
The trap to be sent for tracking fabric reconfiguration.
10. swFabricSegmentTrap
The trap to be sent for tracking segmentation.
11. swExtTrap
The trap adds the SSN binding to the traps if it is enabled.
12. swStateChangeTrap
This trap is sent when the switch changes its state to online or offline.
13. swPortMoveTrap
This trap is sent when the virtual ports are moved from one switch to another.
14. swBrcdGenericTrap
This trap is sent for one of the events, such as fabric change, device change, FAPWWN change,
and FDMI events. This trap is for Brocade use.
15. swDeviceStatusTrap
This trap is sent whenever a device logs in or logs out.
6Fabric OS MIB Reference
53-1002750-01
The Brocade trap (SW-TRAP) can be configured to send traps using the snmpConfig command. For
more information on this command, refer to Table 6 or the Fabric OS Command Reference.
Object instances
MIB objects are defined by the OID, which is the type of object, and by the instance number, which
is an instance of that MIB object. A Fibre Channel port is a MIB object, and port 0 is an instance of
that object. The following is an OID number and an instance number:
1.3.6.1.4.1.1588.2.1.1.1.6.2.1.11.5
where:
1.3.6.1.4.1.1588.2.1.1.1.6.2.1.11 is the OID (of swFCPortTxWords) and 5 is the instance
ID for port 4.
You must add 1 to the port number to get its instance number in SNMP because SNMP numbering
starts at 1; switch port numbering starts at 0.
Loading Brocade MIBs
Loading Brocade MIBs
1
The Brocade MIB is a set of variables that are private extensions to the Internet standard MIB-II.
The Brocade agents support many other Internet-standard MIBs. These standard MIBs are defined
in RFC publications. To find specific MIB information, examine the Brocade proprietary MIB
structure and the standard RFC MIBs supported by Brocade.
Brocade MIB files
The Brocade MIB files are as follows:
• bd.mib
• BRCD_REG.mib
• BRCD_TC.mib
• brcdfcip.mib
• CPQ_HOST.mib
• CPQ_RACK.mib
• FA.mib
• FICON.mib
• HA.mib
• IBMBladeCenterTrapMIB.mib
• SW.mib
• faext.mib
Standard MIBs
Distribution of standard MIBs has been stopped from Fabric OS v6.4.0. Download the following
MIBs from the http://www.oidview.com/ website:
Fabric OS MIB Reference7
53-1002750-01
Loading Brocade MIBs
1
• SNMP-FRAMEWORK-MIB
• IF-MIB
• IANAifType-MIB
• INET-ADDRESS-MIB
• RFC1213-MIB
• SNMPv2-MIB
• ENTITY-MIB
• RMON-MIB
• FC-MGMT-MIB
• FCIP-MGMT-MIB
• ISCSI-MIB
• FIBRE-CHANNEL-FE-MIB
• SNMPv2-PARTY-MIB
• SNMPv2-SMI-MIB
• SNMP-VIEW-BASED-ACM-MIB
• SNMP-USER-BASED-SM-MIB
• SNMP-TARGET-MIB
• IEEE 802.1x PAE MIB
• IEEE 802.3 LAG MIB
• BRIDGE-MIB
• P-BRIDGE MIB
• Q-BRIDGE MIB
• RSTP-MIB
• LLDP MIB
• LLDP-EXT-DOT1-MIB
• LLDP-EXT-DOT3-MIB
• IP MIB
• SNMP-COMMUNITY-MIB
Before loading MIBs
Before loading Brocade MIB files, ensure that you have the correct version of SNMP for your Fabric
OS version (Table 3).
1.SNMPv2 is supported in Fabric OS v5.0.4 and later, but SNMPv2 traps are not supported.
2.Fabric OS v5.x supports the SNMPv3-USM MIB (snmpUsmMIB), which is available as RFC 3414.
MIB loading order
Many MIBs use definitions that are defined in other MIBs. These definitions are listed in the
IMPORTS section near the top of the MIB. When loading the Brocade MIBs, refer to Figure 5 to
ensure any MIB dependencies are loading in the correct order.
1
Fabric OS MIB Reference9
53-1002750-01
RFC1155-SMI
BRCD.mib
Brocade-REG-MIB
Brocade-TC
FOS 2.6.x, 3.x, 4.x, 5.x, 6.x
Brocade_RE.MIB
FOS 6.4, 7.0
FICON_v5_0.mib
FICON.MIB
FOS 6.0
Select one
Brocade_TC.mib
FOS 6.4, 7.0
BD.mib
FOS 6.4, 7.0
RFC2571
SNMP-FRAMEWORK-
MIB
ENTITY_RFC2737.mib
ENTITY-MIB
FCIP.mib
FC_RFC4044.mib
IANA IF-TYPE MIB
SNMPv2-MIB
BRCDFCIP.mib
IF.mib
Dependency
Standard MIB File
Module name
Brocade MIB
Module name
FOS supported
Legend
HA.mib
FA_v2_2.mib
FCMGMT-MIB
FOS 2.6.x
FA.mib
FCMGMT-MIB
FOS 3.x, 4.x, 5.x, 6.x
Select one
SW_v5_5.mib
FOS 2.6.x, 3.x, 4.x,
5.x
SW_v5_7.mib
FOS 6.x
SW.mib
FOS 6.4
BRIDEGE-MIB
P-BRIDEGE
MIB
RFC1213-MIB
MIB-II
RMON MIB
FE_RFC2837.mib
FIBRE-CHANNEL-FE-MIB
FOS 3.1.x, 4.x, 5.x, 6.x, 7.0
ISCSI_RFC4544.mib
IANA-ADDRESS-FAMILY
-NUMBERS-MIB
LLDP-MIB
LLDP-EXT-DOT1-
MIB
LLDP-EXT-DOT3-
MIB
INET-Address
- MIB
IEEE LAG MIB
RFC1271-MIB
RMON2-MIB
TOKEN-RING-
RMON-MIB
Q-BRIDEGE
MIB
RSTP-MIB
IEEE 802.1 PAE
MIB
faext.mib
FOS 7.0
FICON.mib
FOS 7.0
Loading Brocade MIBs
1
10Fabric OS MIB Reference
FIGURE 5Brocade SNMP MIB dependencies and advised installation order
53-1002750-01
Loading...
+ 340 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.