Brocade, Fabric OS, File Lifecycle Manager, MyView, and StorageX are registered trademarks and the Brocade B-wing symbol,
DCX, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or
services 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 Headquarters
Brocade Communications Systems, Inc.
1745 Technology Drive
San Jose, CA 95110
Tel: 1-408-333-8000
Fax: 1-408-333-8101
Email: info@brocade.com
European and Latin American Headquarters
Brocade Communications Switzerland Sàrl
Centre Swissair
Tour A - 2ème étage
29, Route de l'Aéroport
Case Postale 105
CH-1215 Genève 15
Switzerland
Tel: +41 22 799 56 40
Fax: +41 22 799 56 41
Email: emea-info@brocade.com
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, “FE MIB Objects” provides information for FE MIB object types.
• Chapter 4, “Entity MIB Objects” provides information for Entity MIB object types.
• Chapter 5, “SW-MIB Objects” provides information for FC Switch MIB (SW-MIB) object types.
• Chapter 6, “High-Availability MIB Objects” provides information for High-Availability MIB object
types.
• Chapter 7, “FICON MIB Objects” provides information for FICON MIB (LINK-INCIDENT-MIB)
object types.
• Chapter 8, “FibreAlliance MIB Objects” provides information for FibreAlliance MIB
(FCMGMT-MIB) object types.
• Chapter 9, “FCIP MIB Objects”provides information on FCIP MIB support for 7500 switches and
FC4-18i blades.
• Chapter 10, “iSCSI MIB Objects”provides information on iSCSI MIB support for 7500 switches
and FC4-18i blades.
• Appendix A, “MIB Object Groupings” is a function-based listing of MIB objects.
• Appendix B, “MIB OIDs and Their Matching Object Names” provides a listing of the MIB object
names and the corresponding MIB Object ID (OID) associated with each.
Fabric OS MIB Referencexi
53-1000602-02
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 6.1.0, documenting all possible configurations and
scenarios is beyond the scope of this document.
This document supports Brocade Fabric OS versions v6.1.0 and earlier versions, v6.0..0, v5.3.x, v
5.2.x, v5.1.x, v5.0.x, v4.4.0, v4.2.x, v4.1.x, v3.2.x, v3.1.x and all switches supporting these Fabric
OS versions, including:
• Brocade 200E Switch
• Brocade 300 switch
• Brocade 3014 Switch
• Brocade 3016 Switch
• Brocade 3200 Switch
• Brocade 3250 Switch
• Brocade 3800 Switch
• Brocade 3850 Switch
• Brocade 3900 Switch
• Brocade 4012 Switch
• Brocade 4100 Switch
• Brocade 4020 Switch
• Brocade 4900 Switch
• Brocade 5000 Switch
• Brocade 5100 switch
• Brocade 5300 switch
• Brocade 7500 Switch
• Brocade 7600 Switch
• Brocade 12000 Director
• Brocade 24000 Director
• Brocade 48000 Director
• Brocade DCX
• FA4-16 Blade
• FC10-6 Blade
• FC4-16IP Blade
• FC4-48C Blade
• FR4-18i Blade
• FC8-16 Blade
• FC8-32 Blade
xiiFabric OS MIB Reference
53-1000602-02
• FC8-48 Blade
Although many different software and hardware configurations are tested and supported by
Brocade Communications Systems, Inc. for the Fabric OS v6.1.0 release, documenting all possible
configurations and scenarios is beyond the scope of this document. This document supports only
the Fabric OS versions and switches listed above.
What’s New in This Document
The following changes have been made since this document was last released:
• Information that was changed:
-Information included for support of Brocade 300, 5100 and 5300
-Miscellaneous additions and corrections have been made throughout
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 notices formats.
TEXT FORMATTING
The narrative-text formatting conventions that are used in this document are as follows:
bold textIdentifies command names
Identifies the names of user-manipulated GUI elements
Identifies keywords and operands
Identifies text to enter at the GUI or CLI
italic textProvides emphasis
Identifies variables
Identifies paths and Internet addresses
Identifies document titles
code textIdentifies CLI output
Identifies syntax examples
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.
Fabric OS MIB Referencexiii
53-1000602-02
NOTES, CAUTIONS, AND WARNINGS
The following notices appear in this document.
NOTE
A note provides a tip, emphasizes important information, or provides a reference to related
information.
CAUTION
A caution alerts you to potential damage to hardware, firmware, software, or data.
A warning alerts you to potential danger to personnel.
SPECIAL TERM USES
For definitions of SAN-specific terms, visit the Storage Networking Industry Association online
dictionary at http://www.snia.org/education/dictionary.
Additional Information
This section lists additional Brocade and industry-specific documentation that you might find
helpful.
BROCADE RESOURCES
The following related documentation is provided on the Brocade Documentation CD-ROM and on
the Brocade Web site, through Brocade Connect.
NOTE
Go to http://www.brocade.com and click Brocade Connect to register at no cost for a user ID and
password.
Fabric OS
• Fabric OS Administrator’s Guide
• Fabric OS Command Reference Manual
• Fabric OS Message Reference
• Brocade Glossary
Fabric OS Optional Features
• Web Tools Administrator’s Guide
• Fabric Watch Administrator’s Guide
• Fabric Manager Administrator’s Guide
• Secure Fabric OS Administrator’s Guide
xivFabric OS MIB Reference
53-1000602-02
For practical discussions about SAN design, implementation, and maintenance, you can obtain
Building SANs with Brocade Fabric Switches through:
http://www.amazon.com
For additional Brocade documentation, visit the Brocade SAN Info Center and click the Resource
Library location:
http://www.brocade.com
OTHER INDUSTRY RESOURCES
In addition to this manual, the following information about fabric security and the Secure Fabric OS
product is available:
• White papers, online demos, and data sheets are available through the Brocade Web site at:
http:// www.brocade.com/products/software.jhtml
• Best practice guides, including the SAN Security Best Practice Guide, white papers, online
demos, data sheets, and other documentation is available through the Brocade Partner Web
site.
• The CERT
information about certification at:
http://www.cert.org
For additional resource information, visit the Technical Committee T11 Web site. This Web site
provides interface standards for high-performance and mass storage applications for Fibre
Channel, storage management, and other applications:
®
Coordination Center of Carnegie Mellon University provides industry-level
http://www.t11.org
For information about the Fibre Channel industry, visit the Fibre Channel Industry Association Web
site:
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
-Technical Support contract number, if applicable
-Switch model
-Switch operating system version
-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
Fabric OS MIB Referencexv
53-1000602-02
-Serial console and Telnet session logs
-Syslog message logs
2. Switch Serial Number
The switch serial number and corresponding bar code are provided on the serial number label,
as shown here:
*FT00X0054E9*
FT00X0054E9
The serial number label is located as follows:
-Brocade 200E—On the nonport side of the chassis
-Brocade 300, 4100, 4900, 5100, 5300, and 7500—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 7600—On the bottom of the chassis
-Brocade 48000 and Brocade DCX—Inside the chassis next to the power supply bays.
3. World Wide Name (WWN)
-Use the wwn command to display the switch WWN. If you cannot use the wwn command
because the switch is inoperable, you can get the WWN from the same place as the serial
number.
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.
xviFabric OS MIB Reference
53-1000602-02
Chapter
Understanding Brocade SNMP
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]
TABLE 1Security Level Options
security level ProtocolQuery BehaviorTraps
No security [0]
(noAuthnoPriv)
Authentication only [1]
(authNoPriv)
SNMPv1
SNMPv3
SNMPv1
SNMPv3
Allowed.
Allowed.
Allowed.
All SNMPv3 users allowed except
noAuthNoPriv users.
Sent.
Sent.
Sent.
Sent for all SNMPv3 users
except noAuthNoPriv users.
Fabric OS MIB Reference1
53-1000602-02
Understanding SNMP Basics
t
1
TABLE 1Security Level Options (Continued)
security level ProtocolQuery BehaviorTraps
Authentication and
Privacy [2]
(authPriv)
No Access [3]SNMPv1
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.
Management Station
FIGURE 1SNMP Structure
When active, the management station can get information or set information when it queries an
agent. SNMP commands, such as get, set, getnext, setnext, 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.
Not allowed.
Only SNMPv3 users with authPriv
privilege are allowed.
Not allowed.Not Sent.
SNMP
Agent
Not Sent.
Sent only for authPriv users.
MIB
get, getnext, se
Management Station
reply
Agent
FIGURE 2SNMP Query
The management station can also receive traps, unsolicited messages from the switch agent if an
unusual event occurs. Refer to “Understanding SNMP Traps” on page 4 for more information.
Management Station
TRAP
Agent
FIGURE 3SNMP Trap
The agent can receive queries from one or more management stations and can send traps to up to
six management stations.
2Fabric OS MIB Reference
53-1000602-02
Understanding SNMP Basics
1
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:
1.3.6.1.4.1.1588
The corresponding name is:
iso.org.dod.internet.private.enterprise.bsci
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.
iso (1)
org (3)
Brocade SW MIB
1.3.6.1.4.1.1588
private (4)
enterprise (1)
bcsi (1588)
directory (1)
sysDescr (1)
system (1)
mgmt (2)
mib-2 (1)
interface (2)
sysObjectID (2)
dod (6)
internet (1)
experimental (3)
fibreChannel (42)
fcFe (1)
fcFabric (2)
FIGURE 4Brocade MIB Tree Location
Use a MIB browser to access the MIB variables: all MIB browsers perform queries and load MIBs.
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:
• FibreAlliance (FA) MIB: Brocade supports version 3.0.
• Fabric Element (FE) MIB: accepted by the Internet Engineering Task Force (IETF).
Fabric OS MIB Reference3
53-1000602-02
Understanding SNMP Basics
1
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
• read-write - Private
Brocade supports FE_RCF2837.mib under the MIB-II branch in Fabric OS v6.1.0, v6.0.0, v4.x,
v3.2.0, and v3.1.x and the experimental version, FE_EXP.mib, in Fabric OS v2.6.x and 3.0.x.
This 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. Refer to “Loading Brocade MIBs”
on page 6 for more information.
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.
You can read or modify this variable.
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.
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.
You can also use these additional MIBs and their associated traps: HA-MIB; FICON-MIB; and
SW-EXTTRA. You can use the snmpConfig command to disable the FA-MIB, HA-MIB, FICON-MIB, and
SW_EXTTRA; but neither the SW-MIB or the FE-MIB can be disabled.
An event trap (swEventTrap, connUnitEventTrap, or swFabricWatchTrap) is basically an error
message (errShow output) that is SNMP-formatted and delivered.
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
• connUnitSensorStatusChange
4Fabric OS MIB Reference
53-1000602-02
Understanding SNMP Basics
1
• connUnitPortStatusChange
• connUnitEventTrap
The MIB-II system description swEventTrapLevel determines the output for the connUnitEventTrap.
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.
Refer to the Fabric OS Command Reference for more information on this command.
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, etc).
• 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. fruHistoryTrap is not generated when
standby CP is removed.
The high availability trap (HA-TRAP) can be configured to send traps using the snmpConfig
command. Refer to the Fabric OS Command Reference for more information on this command.
SW Traps
There are six specific traps defined in Brocade SW-TRAP:
1. swfault (no longer supported)
2. swSensorScn (no longer supported)
3. swFCPortScn
This trap is generated by a port state change.
4. swEventTrap
This trap is generated by any switch event reported to the system error log.
5. swFabricWatchTrap
This trap is generated when any Fabric Watch threshold is reached.
6. swTrackChangesTrap
This trap is generated by a login or a logout.
The Brocade trap (SW-TRAP) can be configured to send traps using the snmpConfig command.
Refer to the Fabric OS Command Reference for more information on this command.
Fabric OS MIB Reference5
53-1000602-02
Loading Brocade MIBs
1
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
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:
• BRCD_v5_0.mib
• brcdfcip.mib
• CPQ_HOST.mib
• CPQ_RACK.mib
• ENTITY_RFC2737.mib
• FA_v3_0.mib
• fcip.mib
• FE_RFC2837.mib
• FICON_v5_0.mib
• HA_v5_1.mib
• IF.mib
• IF_TYPE.mib
• INET_ADDR.mib
• ISCSI_RFC4544.mib
• SW_v5_7.mib
Before Loading MIBs
Before loading Brocade MIB files, ensure that you have the correct version of SNMP for your Fabric
OS version ( Table 2).
6Fabric OS MIB Reference
53-1000602-02
Loading Brocade MIBs
TABLE 2Fabric OS Supported SNMP Versions
FirmwareSNMPv1SNMPv2SNMPv3
Fabric OS v2.6.2 and previousYesNo
Fabric OS v3.2.0 and previousYesNo
Fabric OS v4.2.0 and previousYesNo
Fabric OS v4.4.0YesNo
Fabric OS v5.xYesYes
Fabric OS v6.0.0YesYesYes
Fabric OS v6.1.0YesyesYes
1.The corresponding Fabric OS has SNMPv2 capabilities, but it is not officially supported by Brocade.
2.Fabric OS v4.4.0 and v5.x support SNMPv3-USM MIB (snmpUsmMIB), which is available as
RFC 3414.
3.SNMPv2 is supported from FOS v5.0.4 and higher, but SNMP v2 traps are not supported.
1
1
1
1
3
No
No
No
Yes
Yes
2
2
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 Reference7
53-1000602-02
Loading Brocade MIBs
1
RFC1213-MIB
MIB-II
RFC1155-SMI
SNMPv2-SMI
SMNPv2-TC
SNMPv2-CONF
Select one
FA_v2_2.mib
FCMGMT-MIB
FOS 2.6.x
FA_v3_0.mib
FCMGMT-MIB
FOS 3.x, 4.x, 5.x
BRCD_v5_0.mib
Brocade-REG-MIB
Brocade-TC
FOS 2.6.x, 3.x, 4.x, 5.x
INET-ADDRESS-MIB
snmpUsmMIB
User-based Security Model
SNMP-FRAMEWORK-MIB
RFC2571
Select one or both
FE_EXP.mib
FCFABRIC-ELEMENT-MIB
FE_RFC2837.mib
FIBRE-CHANNEL-FE-MIB
FOS 3.1.x, 4.x, 5.x
FICON_v5_0.mib
FICON-MIB
FOS 4.x, 5.x
SW_v5_5.mib
FOS 2.6.x, 3.x, 4.x, 5.x
ENTITY_RFC2737.mib
ENTITY-MIB
FOS 4.x, 5.x
HA_v5_1.mib
HA-MIB
FOS 4.x, v5.x
fcip.mib
brcdfcip.mib
ISCSI_RFC4544.mib
Legend
Standard MIB File
Module name
Dependency
Brocade MIB
Module name
FOS supported
NOTE
FA_v3_0.mib obsoletes the use of the connUnitPortStatFabricTable used in the FA_v2_2.mib.
FA_v3_0.mib now uses the connUnitPortStatTable for port statistics. The FA_v3_0.mib and the
FA_v2_2.mib cannot be loaded concurrently on the same SNMP management system.
The FE_RFC2837.mib and the FE_EXP.mib can be loaded concurrently on the same SNMP
management system. The FE_EXP.mib was listed in the experimental OID section. The
FE_RFC2837.mib has subsequently been ratified by the standards organizations.|
All versions of Fabric OS support SNMPv1. Fabric v2.6.x and v3.2.x partially support SNMPv2. Fabric
OS v4.4.0 and v5.0.1 support SNMPv3-USM (snmpUsmMIB) MIB. Fabric OS version 5.3.0 supports
the FCIP MIB and ifXtable.
FIGURE 5Brocade SNMP MIB Dependencies and Advised Installation Order
SNMP CLI usage
An example of the SNMPv3 User/Traps configuration is provided below.
8Fabric OS MIB Reference
53-1000602-02
Loading Brocade MIBs
Configuring SNMPv3 User/Traps
1. Create user on switch using CLI userconfig, with the required role.
switch:admin> userconfig --add fa_adm -r fabricadmin -h0 -a 0-255
Setting initial password for fa_adm
Enter new password:********
Re-type new password:********
Account fa_adm has been successfully added.
switch:admin>
2. Create the SNMPv3 user as shown below.
switch:admin> snmpconfig --set snmpv3
SNMPv3 user configuration(snmp user not configured in FOS user database will
have physical AD and admin role as the default):
User (rw): [snmpadmin1] fa_adm
Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3] 1
New Auth Passwd:********
Verify Auth Passwd:********
Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]):
(1..6) [2] 1
New Priv Passwd:********
Verify Priv Passwd:********
User (rw): [snmpadmin2]
Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3]
Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]):
(2..2) [2]
User (rw): [snmpadmin3]
Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3]
Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]):
(2..2) [2]
User (ro): [snmpuser1]
Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3]
Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]):
(2..2) [2]
User (ro): [snmpuser2]
Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3]
Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]):
(2..2) [2]
User (ro): [snmpuser3]
Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3]
Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]):
(2..2) [2]
1
SNMPv3 trap recipient configuration:
Trap Recipient's IP address : [0.0.0.0] 10.202.95.70
UserIndex: (1..6) [1]
Trap recipient Severity level : (0..5) [0] 5
Trap recipient Port : (0..65535) [162] 65000
Trap Recipient's IP address : [0.0.0.0]
Trap Recipient's IP address : [0.0.0.0]
Trap Recipient's IP address : [0.0.0.0]
Trap Recipient's IP address : [0.0.0.0]
Trap Recipient's IP address : [0.0.0.0]
switch:admin> snmpconfig --set secLevel
Select SNMP GET Security Level
(0 = No security, 1 = Authentication only, 2 = Authentication and Privacy, 3 =
No Access): (0..3) [0] 2
Select SNMP SET Security Level
(0 = No security, 1 = Authentication only, 2 = Authentication and Privacy, 3 =
No Access): (2..3) [2] 2
switch:admin> snmpconfig --show secLevel
GET security level = 2, SET level = 2
SNMP GET Security Level: Authentication and Privacy
SNMP SET Security Level: Authentication and Privacy
4. In the Manager (SNMP Browser) , create a user fa_adm with Authentication protocol as MD5,
Privacy protocol as DES, set the password and set the trap port as 65000. (same values are
set as in the switch SNMPv3 configuration).
10Fabric OS MIB Reference
53-1000602-02
Brocade 7500 / FR4-18i and Brocade MIBs
Brocade 7500 / FR4-18i and Brocade MIBs
Beginning with release Fabric OS 5.3.0, statistics are available for FCIP tunnels, VEX_Ports, or
VE_Ports through the portstatshow command.
The changes in the sensor details for FR4-18i Blade has been incorporated into SNMP. The
“connUnitSensorTable 1.3.6.1.3.94.1.8” on page 902 and “swSensorTable
1.3.6.1.4.1.1588.2.1.1.1.1.22” on page 547 display information consistent with the Fabric OS
sensorShow command.
Access Gateway and Brocade MIBs
Brocade Access Gateway supports the following MIBs:
TABLE 3Access Gateway MIB Support
MIB NameSupportedDescription
MIB-2YesUpdated to support Access Gateway in v5.2.1.
Entity-MIBYes
HA MIBYes
SW-MIBNoDisabled in Access Gateway because the conventions are specific to
fabric switches.
FA-MIBYesThe connUnitSnsTable is not supported because a switch in Access
Gateway does support name server services.
FE-MIBNoDisabled in Access Gateway because the conventions are specific to
fabric switches.
CPQ-Rack MIBLimitedSupported on embedded switches only.
FCIP MIB LimitedImplemented to support WAN interfaces in Fabric OS v5.3.0
iSCSI MIBLimitedSupports displaying information about virtual targets (VTs), iSCSI
sessions, and TCP connection tables, as derived from specific MIB
tables
1
Firmware Upgrades and Enabled Traps
Prior to Fabric OS v4.4, traps were turned on and off as a group (for example, the SW-Trap, or
FA-Trap). In these versions of the Fabric OS it was not possible to set individual traps (such as,
swSensorStatusChangeTrap, swTrackChangesTrap, or connUnitEventTrap).
In Fabric OS v4.4 or above you can to turn on and off traps individually within a trap group. After the
trap group is enabled, the individual traps need to be enabled explicitly.
Because the pre- Fabric OS v4.4 firmware only has trap group level settings, when you upgrade to
the Fabric OS v4.4 firmware or above, individual traps are turned off by default even if the
corresponding trap group was enabled before upgrading. When moving from a downlevel version to
Fabric OS v4.4 or above you must use the snmpconfig command to turn on explicitly the individual
traps within each trap group.
Fabric OS MIB Reference11
53-1000602-02
Fabric OS Commands for Configuring SNMP
1
Fabric OS Commands for Configuring SNMP
Use the following commands to configure MIBs in the Fabric OS. Refer to the Fabric OS
Administrator’s Guide for procedures for configuring SNMP on the Brocade switches.
TABLE 4Commands for Configuring SNMP
CommandDescription
snmpConfig This command has all the features of the existing the agtcfg* commands; in
addition, it has SNMPv3 configuration parameters.
snmpMibCapSetEnhanced in Fabric OS v4.4 to provide a filter facility at the trap level (previously the
filter facility was at MIB level for traps).
Enhanced in Fabric OS 5.3.0 to support enabling and disabling of MIBs and traps
for the FCIP MIB and the ifTable and ifXTable for FC ports (MIB II Intefaces group).
snmpMibCapShowDisplays the snmpMibCapSet command settings.
agtcfgDefaultThis command is deprecated.Only the snmpConfig command is working.
agtcfgSetThis command is deprecated.Only the snmpConfig command is working.
agtcfgShowThis command is deprecated.Only the snmpConfig command is working.
SNMPMibCapSetThis command is deprecated.Only the snmpConfig command is working.
SNMPMibCapShowThis command is deprecated.Only the snmpConfig command is working.
Support for Administrative Domains
Administrative Domains are supported in Fabric OS Version 5.3.0 and later releases. An
Administrative Domain (AD) is a domain within a fabric. Administrative domains can be used to limit
administrator access within a fabric, and to provide service providers with a means to assign
portions of a fabric to individual consumers. An AD may contain switches, devices, and ports. An AD
may also limit access to a configured set of users.
Support for Role Based Access Control
Role Based Access Control (RBAC) is supported in Fabric OS Version 5.3.0 and later releas RBAC
applies a fixed set of roles that address the access control needs of a majority of customers. Each
role is a set of permissions that can be applied to a user that controls the kinds of jobs and tasks
the user can perform on a fabric or fabric element.
Support for IP V6 Addressing
IP V6 addressing is supported in Fabric OS Version 5.3.0 and later releases.
12Fabric OS MIB Reference
53-1000602-02
Chapter
MIB-II (RFC1213-MIB)
This chapter provides descriptions and other information specific to MIB-II, and includes the
following sections:
The descriptions of each of the MIB variables in this chapter come directly from the MIB-II itself.
The notes that follow the descriptions refer to Brocade-specific information and are provided by
Brocade.
Fabric OS MIB Reference13
53-1000602-02
MIB-II Object Hierarchy
2
MIB-II Object Hierarchy
Figure 6 through Figure 15 depicts the organization and structure of MIB-II.
- iso
- org
- dod
FIGURE 6MIB-II Overall Hierarchy
- internet
- directory
- mgmt
- mib-2
- system
- interfaces
- at
- ip
- icmp
- tcp
- udp
- egp
- transmission
- snmp
- iFMIB
- system (1.3.6.1.2.1.1)
- sysDescr 1.3.6.1.2.1.1.1
- sysObjectID 1.3.6.1.2.1.1.2
- sysUpTime 1.3.6.1.2.1.1.3
- sysContact 1.3.6.1.2.1.1.4
- sysName 1.3.6.1.2.1.1.5
- sysLocation 1.3.6.1.2.1.1.6
- sysServices 1.3.6.1.2.1.1.7
FIGURE 7System Hierarchy
14Fabric OS MIB Reference
53-1000602-02
Loading...
+ 1182 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.