Summary of the content on the page No. 1
53-1002582-01
®
9 May 2012
Brocade 6910
Ethernet Access Switch
MIB Reference
Supporting R2.1.0.x
Summary of the content on the page No. 2
Copyright © 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 servic
Summary of the content on the page No. 3
Document History Title Publication number Summary of changes Date Brocade 6910 Ethernet Access Switch 53-1002582-01 Added MIB objects for May 2012 MIB Reference Brocade 6910 Ethernet Access Switch Software Release 2.1.0.2, including fdryLinkAggregationGroup LacpTimeout, snTrapSys MemoryLowThreshold, snTrapTemperatureOK, snTrapPortSecurityViolation, snTrapStackingChasPwr SupplyOK, snTrapStacking ChasPwrSupplyFailed, snTrapStackingTemperature Warning Brocade 6910 Ethernet Access Switch
Summary of the content on the page No. 4
iv Brocade 6910 Ethernet Access Switch MIB Reference 53-1002582-01
Summary of the content on the page No. 5
Contents About This Document In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary of the content on the page No. 6
RFC 2674: Definitions of managed objects for bridges with traffic classes, multicast filtering and virtual LAN extensions . . . 10 RFC 2737: Entity MIB, Version 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 RFC 2819: Remote Network Monitoring Management Information Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 RFC 2863: Interfaces Group MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . .12 RFC 2925: Ping MIB . . . . . . . . . . . . .
Summary of the content on the page No. 7
Chapter 7 Multi-Device Port Authentication Multi-device port authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Global multi-device port authentication objects . . . . . . . . . . . . 37 Clear interface multi-device port authentication objects . . . . . 37 Multi-device port authentication objects . . . . . . . . . . . . . . . . . .38 Multi-device port authentication clear sessions . . . . . . . . . . . .38 Chapter 8 Traffic Security Dynamic ARP Inspection VLAN configuratio
Summary of the content on the page No. 8
Standard traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 System status traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 Traps for spanning tree protocol . . . . . . . . . . . . . . . . . . . . . . . . .59 Traps for RMON events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 IronWare traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 General traps . . . . . . . . .
Summary of the content on the page No. 9
About This Document In this chapter •Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix •Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x •Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x •Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi •Document feedback .
Summary of the content on the page No. 10
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 are as follows: bold text Identifies command names Identifies the names of user-manipulated GUI elements Identifies keywords Identifies text to enter at the GUI or CLI italic text Provides emphasis Identifies variables Identifies document titles code text Identifies CLI output Notes The following notic
Summary of the content on the page No. 11
Getting technical help To contact Technical Support, go to http://www.brocade.com/services-support/index.page for the latest e-mail and telephone contact information. 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
Summary of the content on the page No. 12
xii Brocade 6910 Ethernet Access Switch MIB Reference 53-1002582-01
Summary of the content on the page No. 13
Chapter Overview of the Brocade 6910 MIB 1 Introduction The Management Information Base (MIB) is a database of objects that can be used by a Network Management System (NMS) to manage and monitor devices on the network. The MIB can be retrieved by a network management system that uses Simple Network Management Protocol (SNMP). The MIB structure determines the scope of management access allowed by a device. By using SNMP, a manager application can issue read or write operations within the scop
Summary of the content on the page No. 14
Standard objects • CR/LF – Indicates the end of a line • ^Z - Indicates the end of a file However, in a UNIX environment, the characters LF are used to indicate the end of a line. No character indicates the end of a file. Thus, if you need to import the Brocade 6910 MIB into a UNIX environment, you must use a tool that converts the DOS ASCII into UNIX ASCII, such as the dos2unix tool. Reloading MIBs into a third-party NMS Third party network management systems, such as HP OpenView may have
Summary of the content on the page No. 15
Proprietary objects For example, the OID for the object snSwitch is 1.3.6.1.4.1.1991.1.1.3, but appears as brcdIp.1.1.3 in this guide. The Description column indicates the section in this guide that contains details for that object. TABLE 1 Summary of MIB Objects Proprietary to the Brocade 6910 Object Group Name Object Identifier Sections to Refer To foundry All sections in this manual brcdIp products brcdIp.1 All sections in this manual switch brcdIp.1.1 All sections under the switch br
Summary of the content on the page No. 16
Structure of this guide Structure of this guide All chapters in this guide contain details about the MIB objects that are in the Brocade 6910 MIB. Each object is presented with its object name and OID, the access type available for that object (for example, read-write or read only), and a description. Objects are grouped according to their function. The chapter “Traps and Objects to Enable Traps” on page 57 contains both the objects used to enable a particular type of trap and the objects th
Summary of the content on the page No. 17
Chapter Supported Standard MIBs 2 This section summarizes the standard objects that are supported in the Brocade 6910 MIB. It does not document all the supported standard objects, but presents those standard MIBs that are not fully supported. For example, although RFC1213 is supported in the Brocade 6910 MIB, some groups and tables in that MIB are not supported. The section “RFC 1213: Management Information Base (MIB-II)” on page 7 identifies the groups and tables that are supported and the
Summary of the content on the page No. 18
LLDP MIB support • RFC 3635 – Ethernet-like Interface Types MIB • RFC 3636 – IEEE 802.3 Medium Attachment Units (MAU) MIB IEEE standards • IEEE 802.1 – Port Access Entity (PAE) MIB • IEEE 802.1ag – Connectivity Fault Management (CFM) MIB • IEEE 802.3 – Link Aggregation (LAG) MIB • V-Bridge MIB draft – Bridges with RSTP and VLAN Classification Extensions (IEEE 802.1v) LLDP MIB support The following MIBs are in the IEEE 802.1AB standard, Station and Media Access Control Connectivity Discovery. •
Summary of the content on the page No. 19
RFC 1213: Management Information Base (MIB-II) RFC 1213: Management Information Base (MIB-II) The following objects from RFC1213 are supported on Brocade 6910 switches. Object Group Name Object Identifier system 1.3.6.1.2.1.1 snmp 1.3.6.1.2.1.11 The following groups from RFC 1213 are not supported on Brocade 6910 switches. • interfaces – Replaced by IF-MIB.interfaces • at – atTable has been deprecated • ip – Replaced by IP-MIB.ip • icmp – Replaced by IP-MIB.icmp • tcp – Replaced by IP-MIB.icmp •
Summary of the content on the page No. 20
RFC 1612: DNS Resolver MIB Extensions Object Group Name Object Identifier dnsServCounterAuthAns 1.3.6.1.2.1.32.1.1.2.2 dnsServCounterAuthNoNames 1.3.6.1.2.1.32.1.1.2.3 dnsServCounterAuthNoDataResps 1.3.6.1.2.1.32.1.1.2.4 dnsServCounterNonAuthDatas 1.3.6.1.2.1.32.1.1.2.5 dnsServCounterNonAuthNoDatas 1.3.6.1.2.1.32.1.1.2.6 dnsServCounterReferrals 1.3.6.1.2.1.32.1.1.2.7 dnsServCounterErrors 1.3.6.1.2.1.32.1.1.2.8 dnsServCounterRelNames 1.3.6.1.2.1.32.1.1.2.9 dnsServCounterReqRefusals 1.3.6.1.2.1.32
