Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, MLX, SAN Health, 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
TitlePublication numberSummary of changesDate
Unified IP MIB Reference 53-1002223-01New document.June 2011
Unified IP MIB Reference 53-1002371-01Included the support for
MP-MR2 MIBs for the
NetIron release 05.2.00b.
Unified IP MIB Reference 53-1002391-01Included the MIBs to
support Brocade FCX and
Brocade ICX 6610 of
FastIron devices.
Unified IP MIB Reference 53-1002428-01Included the MIBs to
support the NetIron release
05.3.00.
Unified IP MIB Reference 53-1002428-02Included the MIBs to
support Brocade ICX 6430
and Brocade ICX 6450
devices.
August 2011
October 2011
January 2012
February 2012
TitlePublication numberSummary of changesDate
Unified IP MIB Reference 53-1002428-03Released to support the
patch release.
Unified IP MIB Reference 53-1002428-04Released to support the
patch release.
Unified IP MIB Reference 53-1002549-01Included MIBs to support
the Multi-Service IronWare
release 05.4.00 and
FastIron release 07.4.00.
Unified IP MIB Reference 53-1002549-02Released to support the
Multi-Service IronWare
release 05.4.00a, FastIron
releases 07.4.00 and
This document provides information for the following devices that support the Unified IP MIB:
Brocade FastIron and TurboIron devices running software release 07.3.00 and later:
• Brocade FastIron Edge Switch X Series (IPv6)
• Brocade FastIron SX 800 and FastIron SX 1600
• Brocade FastIron WS
• Brocade FCX
• Brocade ICX Series
• Brocade TurboIron
Brocade NetIron devices running software release 05.2.00 and later:
• Brocade NetIron MLX
• Brocade MLXe
• Brocade NetIron XMR
• Brocade NetIron CES
• Brocade NetIron CER series
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:
Unified IP MIB Referencexxv
53-1002549-02
NOTE
ATTENTION
bold textIdentifies command names
Identifies the names of user-manipulated GUI elements
Identifies keywords
Identifies text to enter at the GUI or CLI
italic textProvides emphasis
Identifies variables
Identifies document titles
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 all lowercase.
Command syntax conventions
Command syntax in this manual follows these conventions:
commandCommands are printed in bold.
--option, optionCommand options are printed in bold.
-argument, argArguments.
[ ]Optional elements appear in brackets.
variableVariables are printed in italics. In the help pages, values are underlined
enclosed in angled brackets < >.
...Repeat the previous element, for example “member[;member...]”
valueFixed values following arguments are printed in plain font. For example,
--show WWN
|Boolean. Elements are exclusive. Example:
--show -mode egress | ingress
Notes
The following notice statements are used in this manual.
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.
or
xxviUnified IP MIB Reference
53-1002549-02
Trademark references
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.
CorporationReferenced Trademarks and Products
Hewlett-Packard Development CompanyHP OpenView
The Open GroupUNIX
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 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.
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 scope of the MIB.
1
The Unified IP MIB consolidates proprietary MIBs used by all Brocade IP devices into one
proprietary MIB file. With this consolidation, all MIBs from IP devices are fully synchronized from
one device to another. It also ensures that each MIB object across various IP products have
consistent definition. The SNMP Manager can compile MIBs safely from various platforms and not
expect to get warnings due to conflicting OIDs, data types, or enumeration. The supported standard
MIBs are not affected.
The Unified IP MIB is not backward-compatible; for this reason, if you have Brocade devices that do
not support the Unified IP MIB, you may need to rewrite your SNMP scripts if the scripts contain
objects that were changed in the Unified IP MIB.
Obtaining and installing the Unified IP MIBs
You can obtain the Unified IP MIBs by downloading the file from the Brocade Technical Support
website.
After obtaining the MIB, follow the instructions for your network management system (NMS) to be
able to use the MIB with your system.
Downloading the MIB from the Technical Support website
To download the MIB from the Brocade Technical Support website, you must have a user name and
password to access the Brocade support site and perform the following steps.
Unified IP MIB Reference1
53-1002549-02
Standard objects
1. Go to http://www.brocade.com in your Web browser.
2. Log in with your user name and password.
3. Click the Downloads tab, and then click the Knowledge Portal link.
4. Log in to the Knowledge Portal, and then click the Software tab.
5. Click the product name. Each product release has a link for its corresponding MIB.
6. Navigate to the link for the MIB and either open the file or save it to disk.
Downloading the MIB from the Brocade FTP site
You can also download the MIB from the Knowledge Portal. Contact Brocade Technical Support for
details. For the latest edition of this document, which contains the most up-to-date information,
refer to the Product Manuals tab at http://www.brocade.com.
Importing Unified IP MIB into a UNIX environment
You can import the Unified IP MIB into third-party network management applications, such as HP
OpenView. By default, the Unified IP MIB files are in DOS ASCII format that uses the following
characters:
• 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 Unified IP 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 problems reloading
MIB files. Ensure that you must upload the following when reloading the Brocade Unified IP MIBs:
• Unload the Enterprise MIBs which were installed from the previous upgrade before reloading
any new Enterprise MIB file.
• Unload the Standard MIBs which were installed from the previous upgrade before reloading
any new Standard MIB file.
Standard objects
The Unified IP MIB supports certain standard MIB objects, which are derived from Request for
Comments (RFCs) documents. Refer to Chapter 2, “Supported Standard MIBs” for details on the
supported standard MIBs.
2Unified IP MIB Reference
53-1002549-02
Proprietary objects
NOTE
Proprietary objects are MIB objects that have been developed specifically to manage Brocade IP
devices. The object identifier (OID) for these MIB objects begin with 1.3.6.1.4.1.1991. In this
manual, the prefix 1.3.6.1.4.1.1991 is represented by the characters brcdIp.
For example, the OID for the object snChassis is 1.3.6.1.4.1.1991.1.1.1, but documented as brcdIp.1.1.1 in this manual.
SNMP support
The SNMPv3 engine is supported on the Brocade IP devices. The SNMPv3 engine can accept V1,
V2c, and V3 packet formats.
If the SNMP GET-BULK request with a high count of max-repetitions, then the device will respond
with the total count of 10.
This section summarizes the standard objects that are supported in the Unified IP MIB. It does not
document all the supported standard objects, but presents those standard MIBs that are not fully
supported.
For example, although RFC 1493 is supported in the Unified IP MIB, some groups and tables in that
MIB are not supported.
Supported on FastIron devices
FastIron devices support the following RFCs:
• 2863 –The Interfaces Group MIB
• 3411 – SNMP Framework MIB
• 3412 – Message Processing and Dispatching (MPD) for the SNMP MIB
• 3413 – SNMP Target MIB
• 3414 – User-Security Model for SNMPv3 MIB
• 3415 – View-based Access Control Model for SNMP MIB
• 4188 – Definitions of Managed Objects for Bridges
• 4273 – Definitions of Managed Objects for BGP-4
FastIron X Series IPv6 devices support the following standard MIBs:
• 2452 – IP Version 6 Management Information Base for the Transmission Control Protocol
• 2454 – IP Version 6 Management Information Base for the User Datagram Protocol
• 2465 – Management Information Base for IP Version 6: Textual Conventions and General
Group
RFC 2465 MIB support on FastIron X Series IPv6 devices is limited to ipv6NetToMediaTable
and ipv6AddrTable only.
• 2466 – Management Information Base for IP Version 6: ICMPv6 Group
• 2932 – IPv4 Multicast Routing MIB
• 2933 – Internet Group Management Protocol MIB
• 2934 – Protocol Independent Multicast MIB for IPv4
• 4001 – Textual Conventions for Internet Network Addresses
Supported on NetIron devices
The following RFCs are supported on the Brocade NetIron XMR, Brocade NetIron MLX, Brocade
MLXe, Brocade NetIron CES, and Brocade NetIron CER series devices.
• 1213 — MIB II
6Unified IP MIB Reference
53-1002549-02
Supported on NetIron devices
• 1493 — Bridge MIB (excluding filtering of objects)
• 1724 — RIPv 2 MI B
• 1850 — OSPF Version 2 Management Information Base
• 2665 — Ethernet-Like MIB
• 2674 — 802.1Q and 802.1p Bridge MIB
• 2787 — VRRP MIB (Refer to “RFC 2787: Definitions of Managed Objects for the Virtual Router
Redundancy Protocol” on page 14 for details.)
• 2819 — Remote Network Monitoring Management Information Base
• 2863 — Interfaces Group MIB
• 2932 — Multicast Routing MIB for IPv4 (Refer to “RFC 2932: IPv4 Multicast Routing MIB” on
page 23 for details.)
• 2933 — IGMP MIB (Refer to “RFC 2933: Internet Group Management Protocol MIB” on page 27
for details.)
• 2934 — PIM MIB (Refer to “RFC 2934: Protocol Independent Multicast MIB for IPv4” on
page 29 details.)
• 3289 — Management Information Base for the Differentiated Services Architecture
• 3418 — Management Information Base (MIB) for the SNMP
The following standard MIBs are supported on Brocade NetIron devices with LLDP capability.
The following MIBs are in the 802.1AB standard, Station and Media Access Control Connectivity
Discovery:
• “LLDP-MIB”
• “LLDP-EXT-DOT1-MIB”
• “LLDP-EXT-DOT3-MIB”
LLDP\LLDP-MED MIB support
The following standard MIBs are not supported on Brocade NetIron devices with LLDP\LLDP-MED
capability.
LLDP MIB support
• LLDP-EXT-DOT1-MIB
• LLDP-EXT-DOT3-MIB
The following MIB is in the ANSI/TIA-1057 standard, Link Layer Discovery Protocol (LLDP) for Media
Endpoint Devices (MED):
• LLDP-EXT-MED-MIB
RFC 1493: Definitions of Managed Objects for Bridges
The following groups are supported on the NetIron devices.
RFC 4188 obsoletes RFC 1493 on the Brocade NetIron XMR, Brocade NetIron MLX, Brocade MLXe,
Brocade NetIron CES, and Brocade NetIron CER series devices.
Object group nameObject identifier
dot1dBridge1.3.6.1.2.1.17
dot1dBase 1.3.6.1.2.1.17.1
dot1dStp1.3.6.1.2.1.17.2
dot1dTp 1.3.6.1.2.1.17.4
Unified IP MIB Reference9
53-1002549-02
RFC 1757: Remote Network Monitoring Management Information Base
NOTE
NOTE
NOTE
NOTE
The dot1dTpFdbTable (OID 1.3.6.1.2.1.17.4.4) in RFC 1493 is used to find dynamically learned MAC
addresses. Statically configured MAC addresses are in the snFdbTable (refer to “Forwarding
database static table information” on page 313).
The SNMP MIB object dot1dStpPortTable (OID 1.3.6.1.2.1.17.2.15) does not display information for
tagged ports that belong to an 802.1W RSTP configuration. The design of that MIB table is based
on a Single STP standard, and does not accommodate Multiple STPs. Thus, the table displays
information only for SSTP and for untagged ports.
RFC 4188 has been converted to SMIv2 format. The object dot1dStpPortPathCost32 was added to
support IEEE 802. The existing MIB dot1dStpPortPathCost has an upper range of 65535. Over that
value, this MIB stays at the upper value and you should access dot1dStpPortPathCost32, which has
a higher upper-range value.
RFC 1757: Remote Network Monitoring Management
Information Base
The following groups from this RFC are supported on NetIron devices.
This RFC is obsolete and is replaced by RFC 2819 for the Brocade NetIron XMR, Brocade NetIron
MLX, Brocade MLXe, Brocade NetIron CES, and Brocade NetIron CER series devices.
Object group nameObject identifier
rmon1.3.6.1.2.1.16
NOTE: This group is not supported on FastIron devices.
statistics1.3.6.1.2.1.16.1
history1.3.6.1.2.1.16.2
alarm1.3.6.1.2.1.16.3
event1.3.6.1.2.1.16.9
The following object groups in RFC 1757 are not supported on NetIron devices:
• hosts
• hostTopN
• matrix
• filter
• capture (packet capture)
10Unified IP MIB Reference
53-1002549-02
RFC 1850: OSPF Version 2 Management Information Base
RFC 1850: OSPF Version 2 Management Information Base
The following tables from RFC 1850 are supported on the Brocade NetIron XMR, Brocade NetIron
MLX, Brocade MLXe, Brocade NetIron CES, and Brocade NetIron CER series devices.
ObjectObject identifier
ospfAreaTable1.3.6.1.2.1.14.2
ospfAreaId 1.3.6.1.2.1.14.2.1.1
ospfAuthType 1.3.6.1.2.1.14.2.1.2
ospfImportAsExtern 1.3.6.1.2.1.14.2.1.3
ospfSpfRuns 1.3.6.1.2.1.14.2.1.4
ospfAreaBdrRtrCount 1.3.6.1.2.1.14.2.1.5
ospfAsBdrRtrCount 1.3.6.1.2.1.14.2.1.6
ospfAreaLsaCount 1.3.6.1.2.1.14.2.1.7
ospfAreaLsaCksumSum 1.3.6.1.2.1.14.2.1.8
ospfAreaSummary 1.3.6.1.2.1.14.2.1.9
ospfAreaStatus 1.3.6.1.2.1.14.2.1.10
ospfStubAreaTable1.3.6.1.2.1.14.3
ospfStubAreaId1.3.6.1.2.1.14.3.1.1
ospfStubTOS 1.3.6.1.2.1.14.3.1.2
ospfStubMetric 1.3.6.1.2.1.14.3.1.3
ospfStubStatus 1.3.6.1.2.1.14.3.1.4
ospfStubMetricType 1.3.6.1.2.1.14.3.1.5
ospfHostTable1.3.6.1.2.1.14.6
ospfHostIpAddress 1.3.6.1.2.1.14.6.1.1
ospfHostTOS 1.3.6.1.2.1.14.6.1.2
ospfHostMetric 1.3.6.1.2.1.14.6.1.3
ospfHostStatus 1.3.6.1.2.1.14.6.1.4
ospfHostAreaID 1.3.6.1.2.1.14.6.1.5
RFC 2096: IP Forwarding Table MIB
RFC 2096 is supported on the following devices:
• On FastIron devices, RFC 2096 replaces RFC 1213.
• On NetIron devices, RFC 2096 is obsoleted by RFC 4292 and it supports both IPv4 and IPv6
forwarding tables.
Unified IP MIB Reference11
53-1002549-02
RFC 2233: The Interfaces Group MIB using SMIv2
Object group nameObject identifier
ipCidrRouteDest1.3.6.1.2.1.4.24.4.1.1
ipCidrRouteMask1.3.6.1.2.1.4.24.4.1.2
ipCidrRouteTos1.3.6.1.2.1.4.24.4.1.3
ipCidrRouteNextHop1.3.6.1.2.1.4.24.4.1.4
ipCidrRouteIfIndex1.3.6.1.2.1.4.24.4.1.5
ipCidrRouteType1.3.6.1.2.1.4.24.4.1.6
ipCidrRouteProto1.3.6.1.2.1.4.24.4.1.7
ipCidrRouteAge1.3.6.1.2.1.4.24.4.1.8
ipCidrRouteInfo1.3.6.1.2.1.4.24.4.1.9
ipCidrRouteNextHopAS1.3.6.1.2.1.4.24.4.1.10
ipCidrRouteMetric11.3.6.1.2.1.4.24.4.1.11
ipCidrRouteMetric21.3.6.1.2.1.4.24.4.1.12
ipCidrRouteMetric31.3.6.1.2.1.4.24.4.1.13
ipCidrRouteMetric41.3.6.1.2.1.4.24.4.1.14
ipCidrRouteMetric51.3.6.1.2.1.4.24.4.1.15
ipCidrRouteStatus1.3.6.1.2.1.4.24.4.1.16
RFC 2233: The Interfaces Group MIB using SMIv2
The interface entry table or ifXTable is based on RFC 2233. It contains information about the
interfaces. Each sub-layer is considered to be an interface. This table contains entries for the ATM
physical ports, as well as for any sub-interfaces that have been configured.
Object group nameObject identifier
ifMIB1.3.6.1.2.1.31
ifMIBObjects1.3.6.1.2.1.31.1
ifTable1.3.6.1.2.1.2.2
ifXtable1.3.6.1.2.1.31.1.1
ifStackTable1.3.6.1.2.1.31.1.2
ifConformance1.3.6.1.2.1.31.2
ifCounterDiscontinuityGroup
NOTE: Supported on the Brocade NetIron
XMR, Brocade NetIron MLX, Brocade
MLXe, Brocade NetIron CES, and
Brocade NetIron CER series devices.
1.3.6.1.2.1.31.2.1.13
12Unified IP MIB Reference
53-1002549-02
RFC 2515: Definitions of Managed Objects for ATM Management
RFC 2515: Definitions of Managed Objects for
ATM Management
Only the following object groups from RFC 2515 are supported on devices that support ATM.
ATM interface configuration parameters table
The ATM Interface Configuration Table from RFC 2515 contains the configuration of cell layers on
the ATM interface of a local device. This information is in addition to the information contained in
the ifTable.
The table contains one entry for each ATM interface port. Table 1 has the object identifier for the
atmInterfaceConf table.
The ATM Interface Transmission Convergence sub-layer table from RFC 2515 contains
configuration and state parameters of the ATM interfaces that use the Transmission Convergence
sub-layer for carrying ATM cells over SONET/SDH or DS3. Table 1 has the object identifier for the
atmInterfaceTC table.
The ATM Adaptation Layer Type 5 (AAL5) virtual channel connection performance statistics table
from RFC 2515 contains the performance statistics of a virtual channel connection at the interface
associated with an AAL5 entity in an ATM host or ATM switch. Table 1 has the object identifier for
the aal5Vcc table.
TABLE 1Object group names and OIDs
Object group nameObject identifier
atmMIB1.3.6.1.2.1.37
atmMIBObjects1.3.6.1.2.1.37.1
atmInterfaceConfTable1.3.6.1.2.1.37.1.2
atmInterfaceTCTable1.3.6.1.2.1.37.1.4
aal5VccTable1.3.6.1.2.1.37.1.12
atmTCMIB1.3.6.1.2.1.37.3
Other object groups from this RFC are not supported.
Unified IP MIB Reference13
53-1002549-02
RFC 2787: Definitions of Managed Objects for the Virtual Router Redundancy Protocol
NOTE
RFC 2787: Definitions of Managed Objects for the Virtual Router
Redundancy Protocol
The Brocade NetIron XMR, Brocade NetIron MLX, Brocade MLXe, Brocade NetIron CES, and
Brocade NetIron CER series devices support RFC 2787, Definitions of Managed Objects for the
Virtual Router Redundancy Protocol.
SNMP support for VRRP MIBs is limited only to IPv4.
The following are the VRRP MIB groups:
• vrrpOperations (OID: 1.3.6.1.2.1.68.1)
• vrrpStatistics (OID: 1.3.6.1.2.1.68.2)
• vrrpConformance (OID: 1.3.6.1.2.1.68.3)
VRRP operations table (vrrpOperTable)
The operations table for a VRRP router that consists of a sequence (one or more conceptual rows)
of vrrpOperEntry objects.
The following table lists the supported notifications for RFC 2787.
Object group nameObject identifier
vrrpTrapNewMaster 1.3.6.1.2.1.68.0.1
vrrpTrapAuthFailure 1.3.6.1.2.1.68.0.2
vrrpTrapPacketSrc 1.3.6.1.2.1.68.1.5
vrrpTrapAuthErrorType 1.3.6.1.2.1.68.1.6
RFC 2819: Remote Network Monitoring Management
Information Base
On the Brocade MLXe devices, interface statistics from the following objects of the etherStatsTable
are preserved when the clear statistics command is entered on the CLI, if the snmp-server
preserve-statistics command is enabled:
• etherStatsDropEvents
Unified IP MIB Reference15
53-1002549-02
RFC 2819: Remote Network Monitoring Management Information Base
• etherStatsOctets
• etherStatsPkts
• etherStatsBroadcastPkts
• etherStatsMulticastPkts
• etherStatsCRCAlignErrors
• etherStatsUndersizePkts
• etherStatsOversizePkts
• etherStatsFragments
• etherStatsPkts64Octets
• etherStatsPkts65to127Octets
• etherStatsPkts128to255Octets
• etherStatsPkts256to511Octets
• etherStatsPkts512to1023Octets
• etherStatsPkts1024to1518Octets
History control group
On the NetIron devices, the history control group controls the periodic statistical sampling of data
from various types of networks. The following objects in the historyControlTable store configuration
entries that each define an interface, polling period, and other parameters:
• historyControlIndex
• historyControlDataSource
• historyControlBucketsRequested
• historyControlBucketsGranted
• historyControlInterval
• historyControlOwner
• historyControlStatus
Ethernet history group
On the NetIron devices, the Ethernet history group records periodic statistical samples from a
network and stores them for later retrieval. The following objects of the group define the
etherHistoryTable for Ethernet networks:
• etherHistoryIndex
• etherHistorySampleIndex
• etherHistoryIntervalStart
• etherHistoryDropEvents
• etherHistoryOctets
• etherHistoryPkts
• etherHistoryBroadcastPkts
• etherHistoryMulticastPkts
16Unified IP MIB Reference
53-1002549-02
RFC 2819: Remote Network Monitoring Management Information Base
• etherHistoryCRCAlignErrors
• etherHistoryUndersizePkts
• etherHistoryOversizePkts
• etherHistoryFragments
• etherHistoryJabbers
• etherHistoryCollisions
• etherHistoryUtilization
Alarm group
On the NetIron devices, the Alarm group periodically takes statistical samples from variables in the
probe and compares them to thresholds that have been configured. The alarm table stores
configuration entries that each define a variable, polling period, and threshold parameters:
• alarmIndex
• alarmInterval
• alarmVariable
• alarmSampleType
• alarmValue
• alarmStartupAlarm
• alarmRisingThreshold
• alarmFallingThreshold
• alarmRisingEventIndex
• alarmFallingEventIndex
• alarmOwner
• alarmStatus
Event group
On the NetIron devices, the following objects in the Event group control the generation and
notification of events from the devices. Each entry in the eventTable describes the parameters of
the event that can be triggered:
• eventIndex
• eventDescription
• eventType
• eventCommunity
• eventLastTimeSent
• eventOwner
• eventStatus
Unified IP MIB Reference17
53-1002549-02
RFC 2863: The Interfaces Group MIB
RFC 2863: The Interfaces Group MIB
RFC 2863 is supported only on the Brocade NetIron XMR, Brocade NetIron MLX, Brocade MLXe,
Brocade NetIron CES, and Brocade NetIron CER series devices.
ifIndex
On the Brocade NetIron XMR, Brocade NetIron MLX, and Brocade MLXe devices, there can be 20,
40, 48, or 64 ifIndexes per module. (Refer to the Configuring SNMP ifIndex section of the Configuring Basic Parameters chapter in the NetIron Configuration Guide for details.) The default
is 20. Issue the snmp-server max-ifindex-per-module 40 CLI command to change the ifIndex to 40
(for example, for backward-compatibility).
On the Brocade NetIron XMR, Brocade NetIron MLX, and Brocade MLXe devices, every trunk group
will appear as a row within the ifTable and ifXTable. The ifIndex range involves all the physical ports,
virtual ports, loopback ports, multicast tunnels, GRE tunnels, MPLS tunnels, and Trunks in that
order.
Use the Get operations on snInterfaceLookupIfIndex (indexed by ifIndex) to get InterfaceId (in a
simple OID form).
Tab le 2 details the XMR or MLX index ranges and they are subject to change from one release to
the next.
TABLE 2XMR or MLX index ranges
4-slot8-slot16-slot32-slotAllocation
Physical port1-1921-3841-7681-153620 per slot
(NetIron release
3.7 and later)
40 per slot
(NetIron releases
prior to 3.7)
48 per slot
(NetIron releases
prior to 5.2)
The following interfaces on the Brocade NetIron XMR, Brocade MLXe, and Brocade NetIron MLX
have ifIndex assignments that are persistent across reboots and switchover operations:
• Physical ports
• Virtual ports
• Loopback ports
The ifIndex should be derived from the snIfIndexLookupTable using the InterfaceId (in OID form),
instead of assuming that the ifIndex will always stay persistent across reloads.
On the following interfaces, IfIndex assignments are not persistent across reboots and switchover
operations:
• MPLS tunnel interfaces
• Trun k po r ts
• IP tunnels
ifType for interfaces
On Brocade NetIron XMR, Brocade NetIron MLX, Brocade MLXe, Brocade NetIron CES, and Brocade
NetIron CER series devices, ifType for all Ethernet interfaces (10/100/1G/10G) returns the value
ethernetCsmacd(6) as mandated by RFC 2665.
If the command snmp-server legacy iftype is configured on the device CLI, ifType returns
gigabitEthernet(117) or fastEther(62). If the command is not configured (or no snmp-server legacy
iftype is issued), then ifType returns the value ethernetCsmacd(6).
Statistics for virtual routing interfaces on 8x10 modules
The ifTable and ifXTable display information for switched and routed packets on virtual routing
interface of the 8x10 modules installed on the Brocade MLXe, Brocade NetIron XMR, and Brocade
NetIron MLX devices. This feature is available on Brocade NetIron XMR, Brocade NetIron MLX, and
Brocade MLXe devices. The extended-counter routed-switched command must be configured to
enable separate accounting of routed and switched packets on virtual routing interfaces.
ifTable attributes
The following MIB attributes of the ifTable return information for switched and routed packets for
the 8x10 modules.
SNMP statistics in the ifTable and ifXTable for physical interfaces on Brocade MLXe and NetIron
devices are preserved when the snmp-server preserve-statistics command is configured. After
configuring snmp-server preserve-statistics, the SNMP statistics listed in the following tables are
separated from the CLI statistics. When the clear statistics <interface-type> <interface-id>
command is entered on the CLI, the command clears only CLI statistics, leaving the SNMP
statistics intact.
20Unified IP MIB Reference
53-1002549-02
RFC 2863: The Interfaces Group MIB
IF-MIB (RFC 2863) ifTable objects
Statistics from the following objects in the ifTable are preserved when the snmp-server
preserve-statistics command is enabled on the CLI.
ifTable objectsSyntax
ifInOctetsCounter32
ifInUcastPktsCounter32
ifInNUcastPkts
NOTE: This object is deprecated in the
8x10 modules installed on the
Brocade NetIron MLX, Brocade
MLXe, and Brocade NetIron
XMR devices.
ifInDiscardsCounter32
ifInErrorsCounter32
ifInUnknownProtosCounter32
ifOutOctetsCounter32
ifOutUcastPktsCounter32
ifOutNUcastPkts
NOTE: This object is deprecated in the
8x10 modules installed on the
Brocade NetIron MLX, Brocade
MLXe, and Brocade NetIron
XMR devices.
ifOutDiscardsCounter32
ifOutErrorsCounter32
Counter32
Counter32
IF-MIB (RFC 2863) ifXTable objects
Statistics from the following objects in the ifXTable are preserved when the snmp-server
preserve-statistics command is enabled on the CLI.
Statistics from the following objects in the etherStatsTable are preserved when the snmp-server
preserve-statistics command is enabled on the CLI.
etherStatsTable objectsSyntax
etherStatsDropEventsCounter32
etherStatsOctetsCounter32
etherStatsPktsCounter32
etherStatsBroadcastPktsCounter32
22Unified IP MIB Reference
53-1002549-02
NOTE
etherStatsTable objectsSyntax
etherStatsMulticastPktsCounter32
etherStatsCRCAlignErrorsCounter32
etherStatsUndersizePktsCounter32
etherStatsOversizePktsCounter32
etherStatsFragmentsCounter32
etherStatsPkts64OctetsCounter32
etherStatsPkts65to127OctetsCounter32
etherStatsPkts128to255OctetsCounter32
etherStatsPkts256to511OctetsCounter32
etherStatsPkts512to1023OctetsCounter32
etherStatsPkts1024to1518OctetsCounter32
RFC 2932: IPv4 Multicast Routing MIB
RFC 2932: IPv4 Multicast Routing MIB
Support for RFC 2932 is available on the Brocade NetIron MLX, Brocade MLXe, Brocade NetIron
XMR, Brocade NetIron CES, and Brocade NetIron CER series devices.
This MIB is not VRF-aware. MIB entries are based on the default VRF IP multicast routing tables.
IP multicast scalar
ObjectObject identifierSupported?
ipMRouteEnable1.3.6.1.2.1.83.1.1.1Yes. Use either the [no] ip multicast-routing or
[no] router pim command to configure IP multicast
routing on the router.
ipMRouteEntryCount1.3.6.1.2.1.83.1.1.7Yes. Use the show ip pim mcache [count] command
to display the the number of rows in the
ipMRouteTable.
ipMRouteTable (IP multicast route table)
Use the show ip pim mcache CLI command to display the information for the IP multicast route
table.
Use the show ip route and show ip mroute commands to display the route information
(ipMRouteRtAddress, ipMRouteRtMask, and ipMRouteRtType).
The SET request is not supported for this table.
Unified IP MIB Reference23
53-1002549-02
RFC 2932: IPv4 Multicast Routing MIB
ObjectObject identifierSupported?
ipMRouteGroup1.3.6.1.2.1.83.1.1.2.1.1Yes
ipMRouteSource1.3.6.1.2.1.83.1.1.2.1.2Yes
ipMRouteSourceMask 1.3.6.1.2.1.83.1.1.2.1.3Yes
ipMRouteUpstreamNeighbor 1.3.6.1.2.1.83.1.1.2.1.4Yes, but read-only.
ipMRouteInIfIndex 1.3.6.1.2.1.83.1.1.2.1.5Yes, but read-only.
ipMRouteUpTime1.3.6.1.2.1.83.1.1.2.1.6Yes, but read-only.
ipMRouteExpiryTime 1.3.6.1.2.1.83.1.1.2.1.7Yes, but read-only.
ipMRoutePkts 1.3.6.1.2.1.83.1.1.2.1.8Yes, but read-only.
on the Brocade MLXe,
Brocade NetIron MLX,
Brocade NetIron XMR,
Brocade NetIron CES, and
Brocade NetIron CER series
devices.
NOTE: This object is not supported
on the Brocade MLXe,
Brocade NetIron MLX,
Brocade NetIron XMR,
Brocade NetIron CES, and
Brocade NetIron CER series
devices.
NOTE: This object is not supported
on the Brocade MLXe,
Brocade NetIron MLX,
Brocade NetIron XMR,
Brocade NetIron CES, and
Brocade NetIron CER series
devices.
NOTE: This object is not supported
on the Brocade MLXe,
Brocade NetIron MLX,
Brocade NetIron XMR,
Brocade NetIron CES, and
Brocade NetIron CER series
devices.
The ipMRouteBoundaryTable and ipMRouteScopeNameTable tables are not supported on the
Brocade NetIron XMR, Brocade NetIron MLX, Brocade MLXe, Brocade NetIron CES, and Brocade
NetIron CER series devices.
26Unified IP MIB Reference
53-1002549-02
RFC 2933: Internet Group Management Protocol MIB
RFC 2933: Internet Group Management Protocol MIB
Support on FastIron devices
FastIron devices support the following objects from RFC 2933.
igmpInterfaceTable (IGMP interface table)
ObjectObject identifier
igmpInterfaceStatus1.3.6.1.2.1.85.1.1.1.3
igmpInterfaceQuerier1.3.6.1.2.1.85.1.1.1.5
igmpCacheTable (IGMP cache table)
ObjectObject identifier
igmpCacheSelf 1.3.6.1.2.1.85.1.2.1.3
igmpCacheLastReporter 1.3.6.1.2.1.85.1.2.1.4
igmpCacheStatus 1.3.6.1.2.1.85.1.2.1.7
Support on other devices
RFC 2933 is supported on the Brocade NetIron MLX, Brocade MLXe, Brocade NetIron XMR,
Brocade NetIron CES, and Brocade NetIron CER series devices:
The following limitations apply to the support of RFC 2933 on the Brocade MLXe devices:
• IGMP Snooping is not supported.
• Tables are read-only.
• VRF support is only for the default VRF.
• Data is available only for physical ports.
igmpInterfaceTable (IGMP interface table)
The show ip igmp interface command is used to display information about the IGMP interface table.
The SET request is not supported for this table.
ObjectObject identifierSupported?
igmpInterfaceIfIndex 1.3.6.1.2.1.85.1.1.1.1Yes
igmpInterfaceQueryInterval 1.3.6.1.2.1.85.1.1.1.2Yes, but read-only
RFC 2934 is supported on the following other Brocade devices:
• Brocade NetIron XMR devices
• Brocade NetIron MLX devices
• Brocade MLXe devices
• Brocade NetIron CES and Brocade NetIron CER series devices
On the Brocade NetIron XMR, Brocade NetIron MLX, Brocade NetIron CES, and Brocade NetIron CER
series devices, only default VRF is supported.
Support for RFC 2934 in these devices is presented in the following sections.
ObjectObject identifierSupported?
pimJoinPruneInterval 1.3.6.1.3.61.1.1.1Yes, but read-only.
pimInterfaceTable (PIM interface table)
Use the show ip pim interface command to display information about the PIM interface table.
The SET request is not supported for this table.
30Unified IP MIB Reference
53-1002549-02
RFC 2934: Protocol Independent Multicast MIB for IPv4
NOTE
ObjectObject identifierSupported?
pim InterfaceIfIndex 1.3.6.1.3.61.1.1.2.1.1Yes
pimInterfaceAddress 1.3.6.1.3.61.1.1.2.1.2Yes, but read-only.
pimInterfaceNetMask1.3.6.1.3.61.1.1.2.1.3Yes, but read-only.
pimInterfaceMode 1.3.6.1.3.61.1.1.2.1.4Yes, but read-only.
NOTE: On Brocade NetIron MLX
Brocade MLXe, Brocade
NetIron XMR
NetIron CES
NetIron CER series
only dense and sparse
modes are supported.
pimInterfaceDR 1.3.6.1.3.61.1.1.2.1.5Yes, but read-only.
pimInterfaceHelloInterval 1.3.6.1.3.61.1.1.2.1.6Yes, but read-only.
pimInterfaceStatus 1.3.6.1.3.61.1.1.2.1.7Yes, but read-only. Returns “active”.
pimInterfaceJoinPruneInter
val
pimInterfaceCBSRPreferen
ce
1.3.6.1.3.61.1.1.2.1.8Yes, but read-only.
1.3.6.1.3.61.1.1.2.1.9Yes, but read-only.
NOTE: On Brocade NetIron MLX
Brocade MLXe, Brocade
NetIron XMR
NetIron CES
NetIron CER series
the constant value for this
object is 0.
, Brocade
, and Brocade
, Brocade
, and Brocade
,
devices,
,
devices,
pimNeighborTable (PIM neighbor table)
Use the show ip pim neighbor command to display information about the PIM neighbor table.
The SET request is not supported for this table.
)
ObjectObject identifierSupported?
pim NeighborAddress 1.3.6.1.3.61.1.1.3.1.1Yes
pimNeighborIfIndex 1.3.6.1.3.61.1.1.3.1.2Yes, but read-only.
pimNeighborUpTime1.3.6.1.3.61.1.1.3.1.3Yes, but read-only.
pimNeighborExpiryTime 1.3.6.1.3.61.1.1.3.1.4Yes, but read-only.
pimNeighborMode 1.3.6.1.3.61.1.1.3.1.5Yes, but read-only.
pimIpMRouteTable (PIM IP multicast route table)
The PIM IP multicast route table MIBs are not supported on the Brocade NetIron XMR, Brocade
NetIron MLX, Brocade MLXe, Brocade NetIron CES, and Brocade NetIron CER series devices.
The show ip pim mcache command displays information about the PIM IP multicast route table.
Unified IP MIB Reference31
53-1002549-02
RFC 2934: Protocol Independent Multicast MIB for IPv4
NOTE
ObjectObject identifierSupported?
ipMRouteGroup1.3.6.1.2.1.83.1.1.2.1.1Yes, but read-only.
ipMRouteSource1.3.6.1.2.1.83.1.1.2.1.2Yes, but read-only.
ipMRouteSourceMask1.3.6.1.2.1.83.1.1.2.1.3Yes, but read-only.
pimIpMRouteUpstreamAssertT
imer
pimIpMRouteAssertMetric 1.3.6.1.3.61.1.1.4.1.2Yes, but read-only.
pimIpMRouteAssertMetricPref 1.3.6.1.3.61.1.1.4.1.3Yes, but read-only.
devices, only read-only is supported for
this object.
, Brocade MLXe,
pimRpTable (PIM RP table)
On the Brocade NetIron MLX, Brocade MLXe, Brocade NetIron XMR, Brocade NetIron CES, and
Brocade NetIron CER series devices, this table has been replaced by “pimRpSetTable (PIM RP set
table)”
32Unified IP MIB Reference
53-1002549-02
RFC 2934: Protocol Independent Multicast MIB for IPv4
ObjectObject identifierSupported?
pim RPGroupAddress 1.3.6.1.3.61.1.1.5.1.1Yes, but read-only and only active g roups.
pimRPAddress1.3.6.1.3.61.1.1.5.1.2Yes, but read-only.
pimRPState1.3.6.1.3.61.1.1.5.1.3Yes, but read-only and value is always up(1).
pimRPStateTimer1.3.6.1.3.61.1.1.5.1.4No.
pimRPLastChange1.3.6.1.3.61.1.1.5.1.5No.
pimRPRowStatus 1.3.6.1.3.61.1.1.5.1.6Yes, but read-only.
pimRpSetTable (PIM RP set table)
Use the show ip pim rp-set command to display information about the PIM RP set table.
ObjectObject identifierSupported?
pim RpS etGroupAddress1.3.6.1.3.61.1.1.6.1.1Yes
pimRpSetGroupMask1.3.6.1.3.61.1.1.6.1.2Yes
pimRpSetAddress1.3.6.1.3.61.1.1.6.1.3Yes
pimRpSetHoldTime1.3.6.1.3.61.1.1.6.1.4Yes, but read-only.
pimRpSetExpiryTime1.3.6.1.3.61.1.1.6.1.5Yes, but read-o nly.
pimRpSetComponent1.3.6.1.3.61.1.1.6.1.6Yes, but only one PIM domain is
supported.
pimCandidateRPTable (PIM candidate-RP table)
The show ip pim bsr command displays information about the PIM candidate-RP table.
RFC 3289: Management Information Base for the
Differentiated Services Architecture
The Brocade NetIron MLX, Brocade MLXe, Brocade NetIron XMR, Brocade NetIron CES, and
Brocade NetIron CER series devices support RFC 3289, Management Information Base for the
Differentiated Services Architecture.
diffServMultiFieldClfrTable
collectors, use
snSflowCollectorTable. (Refer to
“sFlow collector table” on
page 290.)
The following table defines the MIB objects that describe a classifier element for matching on
various fields of an IP address and upper-layer protocol header.
The following table supports only the SNMP GET and GET-NEXT options.
The diffServDataPathTable, diffServClfrTable, diffServClfrElementTable, diffServMeterTable,
diffServTBParamTable, diffServActionTable, diffServDscpMarkActTable, diffServCountActTable,
diffServAlgDropTable, diffServRandomDropTable, diffServQTable, diffServSchedulerTable,
diffServMinRateTable, and diffServMaxRateTable are not supported on the Brocade NetIron XMR,
Brocade NetIron MLX, Brocade MLXe, Brocade NetIron CES, and Brocade NetIron CER series
devices.
RFC 3635: Definitions of Managed Objects for the
minimum.
maximum.
Ethernet-like interface types
The following groups from RFC 3635 are supported on the Brocade NetIron MLX, Brocade MLXe,
Brocade NetIron XMR, Brocade NetIron CES, and Brocade NetIron CER series devices.
RFC 3635 obsoletes RFC 2665.
dot3StatsTable
The following table lists the dot3StatsTable MIB objects.
The tables mplsInterfacePerfTable, mplsOutSegmentPerfTa ble , mplsLabelStackTable, and
mplsInSegmentMapTable are not supported.
MPLS label stack scalar object
The following table lists the MPLS label stack scalar objects. The scalar objects
mplsInSegmentIndexNext, mplsOutSegmentIndexNext, mplsXCIndexNext, and
mplsLabelStackIndexNext are not supported.
ObjectObject identifierSupported?
mplsMaxLabelStackDepth1.3.6.1.2.1.10.166.2.1.11Yes. Always returns the maximum label stack
RFC 3815: Definitions of Managed Objects
for the Multiprotocol Label Switching (MPLS),
Label Distribution Protocol (LDP)
The Brocade NetIron XMR, Brocade NetIron MLX, Brocade MLXe, Brocade NetIron CES, and
Brocade NetIron CER series devices support RFC 3815, Definitions of Managed Objects for the
Multiprotocol Label Switching (MPLS), and Label Distribution Protocol (LDP).
Support for this MIB enables configuration and monitoring of the LDP.
mplsLdpLsr objects
depth of 3.
ObjectObject identifierSupported?
mplsLdpLsrId1.3.6.1.2.1.10.166.4.1.1 Yes
mplsLdpLsrLoopDetectionCapable 1.3.6.1.2.1.10.166.4.1.2 Returns none(1) or hopCountAndPathVector(5).
40Unified IP MIB Reference
53-1002549-02
RFC 3815: Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution
This mplsLdpEntity table contains information about MPLS Label Distribution Protocol Entities
which exist on this Label Switching Router (LSR) or Label Edge Router (LER).
The following table currently supports the read-only access.
The mplsLdpEntityStats table is a read-only table which augments the mplsLdpEntityTable. This
table keeps statistical information about the LDP Entities on the LSR. This table is read-only.
The mplsLdpPeer table has information about LDP peers known by Entities in the
mplsLdpEntityTable. The information in this table is based on information from the Entity-Peer
interaction during session initialization but is not appropriate for the mplsLdpSessionTable,
because objects in this table may or may not be used in session establishment.
The mplsLdpSession table contains information of sessions between the LDP Entities and LDP
Peers. This table augments the mplsLdpPeerTable. Each row in this table represents a single
session. This table is read-only.
The mplsLdpSessionPeerAddr table extends the mplsLdpSessionTable. This table is used to store
Label Address information from Label Address Messages received by this LSR from Peers. This
table is read-only and should be updated when Label Withdraw Address Messages are received (for
example, rows should be deleted as appropriate).
As more than one address may be contained in a Label Address Message, this table sparse
augments the mplsLdpSessionTable's information.
RFC 4022: Management Information Base for the
Transmission Control Protocol (TCP)
The Brocade NetIron XMR, Brocade NetIron MLX, Brocade MLXe, Brocade NetIron CES, and
Brocade NetIron CER series devices support RFC 4022, Management Information Base for
Transmission Control Protocol (TCP). All objects have read-only access, except for the
tcpConnectionState object in the tcpConnectionTable. The tcpConnectionState object has
read-write access.
address type of this Next Hop
Address as specified in the Label
Address Message associated with
this Session.
Possible values:
• ipv4(1)
• ipv6(2)
• unknown(0)
Unified IP MIB Reference45
53-1002549-02
RFC 4087: IP Tunnel MIB
RFC 4087: IP Tunnel MIB
The following tables in RFC 4087 are supported on the Brocade NetIron XMR, Brocade NetIron
MLX, Brocade MLXe, Brocade NetIron CES, and Brocade NetIron CER series devices.
tunnelIfTable
The tunnelIfTable contains information on configured tunnels.
Object namesDescription
tunnelIfLocalAddressNot supported as it is deprecated.
tunnelIfRemoteAddressNot supported as it is deprecated.
tunnelIfEncapsMethodRead-only. Only 6to4 and GRE tunnel types are supported. This is
tunnelIfHopLimitRead-only. This is the IPv4 time-to-live (TTL) or IPv6 Hop Limit to
tunnelIfFlowLabelRead-only. Always returns -1 which indicates a wildcard as
tunnelIfAddressTypeRead-only.
tunnelIfLocalInetAddressRead-only.
tunnelIfRemoteInetAddressRead-only.
tunnelIfEncapsLimitRead-only. This is the maximum number of additional
the encapsulation method used by the tunnel.
use in the outer IP header. A value of 0 indicates that the value is
copied from the payload's header.
suggested by RFC 3595.
encapsulations permitted for packets undergoing encapsulation at
this node. A value of -1 indicates that no limit is present, except as
a result of the packet size.
tunnelInetConfigTable
The tunnelInetConfigTable can be used to map a set of tunnel endpoints to the associated ifIndex
value. Every row in the tunnelIfTable with a fixed destination address should have a corresponding
row in the tunnelInetConfigTable.
Object namesDescription
tunnelInetConfigAddressTypeRead-only. Index value.
tunnelInetConfigLocalAddressRead-only. Index value.
tunnelInetConfigRemoteAddressRead-only. Index value.
tunnelInetConfigEncapsMethodRead-only. Index value. This is the encapsulation method used by
the tunnel. Only 6to4 and GRE tunnel types are supported.
tunnelInetConfigIDRead-only. Index value. Always 1 in 6to4 tunnel type.
RFC 4113: Management Information Base for the
User Datagram Protocol (UDP)
RFC 4113, Management Information Base for the User Datagram Protocol (UDP) is supported on
the Brocade NetIron XMR, Brocade NetIron MLX, Brocade MLXe, Brocade NetIron CES, and
Brocade NetIron CER series devices.
All objects have read-only access.
RFC 4273: Definitions of Managed Objects for BGP-4
RFC 4273 is supported on the Brocade NetIron XMR, Brocade NetIron MLX, Brocade MLXe,
Brocade NetIron CES, and Brocade NetIron CER series devices.
The definitions of managed objects for BGP-4 (OID 1.3.6.1.2.1.15.3) is used instead of RFC 1567,
Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using
SMIv2. RFC 1657 has been obsoleted in RFC 4273.
48Unified IP MIB Reference
53-1002549-02
RFC 4273: Definitions of Managed Objects for BGP-4
Object group nameObject identifierNotes
bgpVersion1.3.6.1.2.1.15.1The vector of the supported BGP version
numbers.
bgpLocalAS1.3.6.1.2.1.15.2The local autonomous system number.
The Brocade MLXe and NetIron devices return
“AS_TRANS (23456)” if the number is greater
than 16 bits.
bgpPeerTable1.3.6.1.2.1.15.3The bgpPeerRemoteAs object is the remote
autonomous system number received in the
BGP OPEN message.
The Brocade MLXe and NetIron devices return
“AS_TRANS (23456)” for this object if the
number is greater than 16 bits.
bgp4PathAttrTable1.3.6.1.2.1.15.6This table is supported on the Brocade MLXe
and NetIron devices.
Unified IP MIB Reference49
53-1002549-02
draft-ietf-idr-bgp4-mibv2-12 MIB
NOTE
Object group nameObject identifierNotes
bgp4PathAttrASPathSegment1.3.6.1.2.1.15.6.1.5This object is the sequence of AS path
bgp4PathAttrAggregatorAS1.3.6.1.2.1.15.6.1.10The AS number of the last BGP4 speaker that
segments. Each AS path segment is
represented by a triplet of <type>, <length>,
and <value>.
The Brocade NetIron XMR, Brocade NetIron
MLX, Brocade MLXe, Brocade NetIron CES, and
Brocade NetIron CER series devices return
“AS_TRANS” if the AS number is greater than 2
bytes.
performed route aggregation. A value of zero
(0) indicates the absence of this attribute.
The Brocade NetIron XMR, Brocade NetIron
MLX, Brocade MLXe, Brocade NetIron CES, and
Brocade NetIron CER series devices return
“AS_TRANS (23456)” for this object if remote
AS is greater than 16 bits.
draft-ietf-idr-bgp4-mibv2-12 MIB
The following section of draft-ietf-idr-bgp4-mibv2-12 defines MIB objects for managing the Border
Gateway Protocol, version 4.
BGP4v2 per-peer session management information
The following table displays information about the BGP4v2 per-peer session management
information group. Use the show ip bgp neighbor <id> command to display the BGP4v2 per-peer
session management information.
The following table is supported only on the Brocade NetIron MLX, Brocade MLXe, Brocade NetIron
XMR, and Brocade NetIron CER series devices and it is not supported on the Brocade NetIron CES
2000 series BASE Packages device.
NoneThe BGP4v2 per-peer table. The table contains one entry
per BGP peer and the information about the connections
with the BGP peers.
NoneSpecifies the routing instance index. Some of the BGP
implementations permit the creation of multiple instances
of a BGP routing process. The implementations that do not
support multiple routing instances, return 1 for this object.
The VRF index is used to identify the peer instance. The VRF
index is a zero-based index.
NoneSpecifies the address family of a local-end peering session.
NoneSpecifies the local IP address of the received BGP
connection.
NoneSpecifies the address family of a remote end peering
session.
The following address types are supported:
• ipv4(1)
• ipv6(2)
NoneSpecifies the remote IP address of the received BGP peer.
Read-onlyIndicates the local port for the TCP connection between the
BGP peers.
Read-onlyIndicates a Autonomous System (AS) is the peering session
that represents itself to the remote peer.
Some implementations of BGP can represent itself as
multiple autonomous systems.
Read-onlySpecifies the BGP identifier of the local system for the
peering session. It is required that all the values of
bgp4V2PeerLocalIdentifier and bgp4V2PeerInstance
objects must be identical.
Read-onlySpecifies the remote port for the TCP connection between
the BGP peers.
NOTE: The objects bgp4V2PeerLocalAddr,
bgp4V2PeerLocalPort, bgp4V2PeerRemoteAddr,
and bgp4V2PeerRemotePort provides the
appropriate references to the standard MIB TCP
connection table or to the IPv6 TCP MIB as
referenced in RFC 4022.
Read-onlySpecifies the remote AS number received in the BGP OPEN
message.
Read-onlySpecifies the BGP identifier of the received remote BGP
peer.
The entry received must be 0.0.0.0 unless the
bgp4V2PeerState is in the openconfirm(5) or in
established(6) state.
Read-onlySpecifies whether the BGP finite state machine (FSM) for
the remote peer is halted or running, the BGP FSM for a
remote peer is halted after processing a stop event.
Likewise, if in the running state after processing a start
event.
The bgp4V2PeerState is in the idle state when the FSM is
halted. Although, some extensions such as Graceful Restart
leaves the peer in the idle state with the FSM running.
Read-onlySpecifies a user-configured description identifying the peer.
The object must contain a description that is unique within
the existing BGP instance for the peer.
BGP4v2 per-peer error management information
The following table contains the BGP4v2 per-peer error management information objects.
The following table is supported only on the Brocade NetIron MLX, Brocade MLXe, Brocade NetIron
XMR, and Brocade NetIron CER series devices and it is not supported on the Brocade NetIron CES
2000 series BASE Packages device.
on Brocade NetIron MLX,
Brocade MLXe, Brocade
NetIron XMR, Brocade
NetIron CES, and Brocade
NetIron CER series devices
Read-onlySpecifies the last error code sent to the peer through a
notification message on the connection. The field is zero(0), if
no error occurs.
Read-onlySpecifies the last error subcode sent to the peer through a
notification message on the connection. The field is zero(0), if
no error occurs.
Read-onlyIndicates the time stamp when the last notification is sent to
the peer.
Read-onlySpecifies the implementation-specific explanation of the error
reported.
Read-onlySpecifies the data of the last error code sent to the peer.
As per RFC 2578, some implementations have limitations
dealing with Octet Strings that are larger than 255. So, the
data is truncated.
BGP4v2 per-peer event times table
The following table contains the BGP4v2 per-peer event times-related objects.
The following table is supported only on the Brocade NetIron MLX, Brocade MLXe, Brocade NetIron
XMR, and Brocade NetIron CER series devices and it is not supported on the Brocade NetIron CES
2000 series BASE Packages device.
NoneA table reporting the per-peering session amount of time
elapsed and update events while the peering session
advanced into the established state.
Read-onlyIndicates how long (in seconds) the peer has been in the
established state or how long since the peer was last in the
established state. The value of the object is set to zero(0)
when a new peer is configured or when the router is booted.
The value remains zero if the peer has never reached the
established state.
Read-onlyIndicates the elapsed time (in seconds) since the last BGP
update message was received from the peer. The value of the
object is set to zero(0) each time bgpPeerInUpdates is
incremented.
Unified IP MIB Reference53
53-1002549-02
draft-ietf-idr-bgp4-mibv2-12 MIB
NOTE
BGP4v2 NLRI table
The following table contains the BGP4v2 Network Layer Reachability Information (NLRI) objects.
Use the show ip bgp routes detail command to display all the BGP attributes of a route, such as
communities. Use the show ip bgp routes command to display the entries learned through NLRI
available in the update.
The following table is supported only on the Brocade NetIron MLX, Brocade MLXe, Brocade NetIron
XMR, and Brocade NetIron CER series devices and it is not supported on the Brocade NetIron CES
2000 series BASE Packages device.
information about paths to destination networks received
from all the BGP4 peers. Collectively, this represents the
Adj-Ribs-In. For NLRI, the route in which the bgp4V2NlriBest
object is true represents the route that is installed in the
LocRib from the Adj-Ribs-In.
NoneSpecifies the index that allows multiple instances of a base
prefix for a certain AFI-SAFI from a given peer. This is used to
allow a peer in future implementations to send more than a
single route instance and allow extensions that extend an
NLRI field to send the same prefix while utilizing other
extension-specific information.
The index is always 1.
NoneSpecifies the address family of the prefix for NLRI.
NOTE: It is not necessary that an AFI definition is equivalent
to an InetAddressType.
NoneSpecifies the subsequent address family of the prefix for
NLRI.
NoneSpecifies the type of the IP address prefix in an NLRI field.
The value of the object is derived from the appropriate value
from the bgp4V2NlriAfi field. Where an appropriate
InetAddressType is not available, the value of the object is
unknown(0).
NoneIndicates an IP address prefix in an NLRI field. The object is
an IP address containing the prefix with the length specified
by the bgp4V2NlriPrefixLen object. Any bits beyond the length
specified by the bgp4V2NlriPrefixLen object are set to zero(0).
NoneIndicates the length in bits of the address prefix in an NLRI
Read-onlyIndicates whether the route is chosen as the best BGP4 route
for the destination.
Read-onlySpecifies the degree of preference calculated by the receiving
BGP4 speaker for an advertised route.
The value of the object is zero (0) where the prefix is
ineligible.
Read-onlySpecifies the ultimate origin of the path information:
• igp(1) - The networks that are interior.
• egp(2) - The networks learned through an Exterior
Gateway Protocol (EGP).
• incomplete(3) - The networks that are learned by some
other means.
Read-onlySpecifies the address family of the address for the border
router that is used to access the destination network.
Read-onlySpecifies the address of the border router that is used to
access the destination network. The address is the next-hop
address received in the update packet associated with the
prefix:
• For RFC 2545 style double nexthops, the object contains
the global scope next hop.
• For bgpPathAttrLinkLocalNextHop, the object contains
the link local scope next hop, if it is present.
• For bgp4V2NlriNextHopAddr, the object contains the link
local next hop, if a mechanism is developed to use only a
link local next hop.
Read-onlySpecifies the address type for an IPv6 link local address.
The object is present only when receiving RFC 2545 style
double nexthops.
The object is present optionally in BGP implementations that
do not support IPv6. The value of the object is unknown(0)
when there is no IPv6 link local next hop present.
Read-onlyIndicates the value that contains an IPv6 link local address
and is present only when receiving RFC 2545 style double
nexthops.
The object is present optionally in BGP implementations that
do not support IPv6. The length of the object is zero(0) when
there is no IPv6 link local next hop present.
Read-onlyIndicates if the value is true when the LOCAL_PREF value is
sent in the UPDATE message.
The value is always true.
Read-onlySpecifies the degree of preference of the originating BGP4
speaker for an advertised route.
Read-onlyIndicates if the value is true when a Multi-Exit Discriminator
Read-onlyIndicates the metric used to discriminate between multiple
exit points to an adjacent autonomous system. When an MED
value is absent but has a calculated default value, the object
will contain the calculated value.
Read-onlyIndicates if the value is true when the ATOMIC_AGGREGATE
path attribute is present and indicates that NLRI cannot be
made more specific.
Read-onlyIndicates if the value is true when the AGGREGATOR path
attribute is sent in the UPDATE message.
Read-onlySpecifies an AS number of the last BGP4 speaker that
performed route aggregation. The value of the object is
zero(0) when the bgp4V2NlriAggregatorPresent object is
false.
Read-onlySpecifies the IP address of the last BGP4 speaker that
performed route aggregation. The value of the object is
0.0.0.0 when the bgp4V2NlriAggregatorPresent object is
false.
Read-onlyIndicates the value that represents the calculated length of
the AS-Path according to the rules in the BGP specification.
The value is used in route selection.
Read-onlySpecifies a string depicting the AS-Path to the network, which
is received from the peer that is advertised.
The format of the string is implementation-dependent and it
must be designed for operator readability.
SnmpAdminString is capable of representing a maximum of
255 characters. This may lead to the string being truncated in
the presence of a large AS-Path.
NOTE: It is recommended that when the content of the
object is truncated, the final three octets should be
reserved for the ellipses string (...). The
bgp4V2NlriAsPath object gives access to the full
AS-Path.
Read-onlySpecifies the contents of the BGP4 AS_PATH attribute to
provide an authorized form of the BGP4 AS_PATH along with
the human-readable bgp4V2NlriAsPathString object that can
be truncated. The object is parsed using the rules defined for
four-octet autonomous systems as defined in RFC 4893. RFC
4271 and RFC 5065 define the general format of the
AS_PATH attribute and its code points.
The AS_PATH attribute is composed of a sequence of AS
segments. Each AS segment is represented in the following
fields:
• The path segment type and path segment are one octet
in length each. Any one of the following can represent
the path segment type field:
-1 - AS_SET (RFC 4721)
-2 - AS_SEQUENCE (RFC 4721)
-3 - AS_CONFED_SEQUENCE (RFC 3065)
-4 - AS_CONFED_SET (RFC 3065)
• The path segment length field contains the number of
autonomous systems (not the number of octets) in the
path segment value field.
• The path segment value field contains one or more
autonomous system numbers, each encoded as a four
octet length field in network-byte order.
NOTE: An SNMP agent can truncate the objects that are less
than its maximum theoretical length of 4072 octets. It
is recommended that when such truncation occurs on
the boundary of an encoded AS, the partial AS be
discarded from the object and the object size
adjusted accordingly. When such truncation happens,
either alone or in conjunction with the truncation of a
partially encoded AS, it will yield an empty path
segment value. In that case, the path segment type
and path segment length components of the
truncated AS_PATH attributue are also discarded and
the object size is adjusted accordingly.
Read-onlySpecifies the path attributes that are not understood by the
implementation are presented. These path attributes use the
type, length, and value encoding from RFC 4271.
NOTE: An SNMP agent can truncate the objects that are less
than its maximum theoretical length of 4072 octets.
RFC 4292: IP Forwarding Table MIB
The Brocade NetIron XMR, Brocade NetIron MLX, Brocade MLXe, Brocade NetIron CES, and
Brocade NetIron CER series devices support the entire RFC 4292 with the following exceptions.
RFC 4292 replaces RFC 2096 and RFC 2465.
• The object inetCidrRouteDiscards is not supported.
• The objects inetCidrRouteMetric2, inetCidrRouteMetric3, inetCidrRouteMetric4, and
inetCidrRouteMetric5 in the inetCidrRouteTable are not supported.
• All objects have read-only access.
Unified IP MIB Reference57
53-1002549-02
RFC 4293: Management Information Base for the Internet Protocol (IP)
RFC 4293: Management Information Base for the
Internet Protocol (IP)
RFC 4293, Management Information Base for the Internet Protocol (IP) obsoletes the following:
• RFC 2011: SNMPv2 Management Information Base for the Internet Protocol using SMIv2
• RFC 2465: Management Information Base for IP Version 6: Textual Conventions and General
Group
• RFC 2466: Management Information Base for IP Version 6: ICMPv6 Group
This RFC is supported on the Brocade NetIron XMR, Brocade NetIron MLX, Brocade MLXe, Brocade
NetIron CES, and Brocade NetIron CER series devices.
The following table summarizes the tables from the RFC that are supported.
Object group nameObject identifierSupported IP
version
IP scalar variables1.3.6.1.2.1.4IPv4 and IPv6Only the following objects have
ipv4InterfaceTable1.3.6.1.2.1.4.28IPv4All objects are read-only.
ipv6InterfaceTable1.3.6.1.2.1.4.30IPv6All objects are read-only.
ipSystemStatsTable1.3.6.1.2.1.4.31.1 IPv4 and IPv6All objects are read-only.
ipIfStatsTableLastChange1.3.6.1.2.1.4.31.2 IPv4 and IPv6All objects are read-only.
ipIfStatsTable1.3.6.1.2.1.4.31.3 IPv4 and IPv6Not supported.
ipAddressPrefixTable1.3.6.1.2.1.4.32IPv4 and IPv6All objects are read-only.
ipAddressTable1.3.6.1.2.1.4.34IPv4 and IPv6All objects are read-only.
ipNetToPhysicalTable
NOTE: Only ARP entries that are
currently being used are
included in the ARP table.
ipv6ScopeZoneIndexTable1.3.6.1.2.1.4.36IPv6All objects are read-only
ipDefaultRouterTable1.3.6.1.2.1.4.37IPv4 and IPv6All objects are read-only.
1.3.6.1.2.1.4.35IPv4 and IPv6Only the following objects have
Access
read-write access:
• ipDefaultTTL
• ipv6IpDefaultHopLimit
• ipv6IpForwarding
All other scalar variables are
read-only.
read-create access:
• ipNetToPhysicalPhysAddress
• ipNetToPhysicalType
• ipNetToPhysicalRowStatus
All other objects are read-only.
58Unified IP MIB Reference
53-1002549-02
RFC 4363: Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN
NOTE
Object group nameObject identifierSupported IP
version
Ipv6RouterAdvertTable1.3.6.1.2.1.4.39IPv6Only the following objects have
icmpStatsTable1.3.6.1.2.1.5.29IPv4 and IPv6All objects are read-only.
icmpMsgStatsTable1.3.6.1.2.1.5.30IPv4 and IPv6All objects are read-only.
RFC 4363: Definitions of Managed Objects
for Bridges with Traffic Classes, Multicast Filtering,
and Virtual LAN Extensions
The following groups from RFC 4363 are supported on the Brocade NetIron MLX, Brocade MLXe,
and Brocade NetIron XMR devices.
The following table lists the dot1vProtocolGroupTable mapping for the frame type and protocol
value to the groupID.
Group IDFrame typeProtocol value
1Ethernet0x0800(IPv4)
2Ethernet0x86DD(IPv6)
3Ethernet0x8137(IPX)
4Ethernet0x809B(AppleTalk)
5rfc_10420x0800(IPv4)
6rfc_10420x86DD(IPv6)
7rfc_10420x8137(IPX)
8rfc_10420x809B(AppleTalk)
9snap8021H0x0800(IPv4)
10snap8021H0x86DD(IPv6)
11snap8021H0x8137(IPX)
12snap8021H0x809B(AppleTalk)
60Unified IP MIB Reference
53-1002549-02
RFC 4444: Management Information Base for Intermediate System to Intermediate System (IS-IS)
NOTE
RFC 4444: Management Information Base for
Intermediate System to Intermediate System (IS-IS)
This RFC 4444, Management Information Base for Intermediate System to Intermediate System
(IS-IS) is supported on the Brocade NetIron XMR, Brocade NetIron MLX, Brocade MLXe, Brocade
NetIron CES, and Brocade NetIron CER series devices.
Scalar isisSys objects
The following scalar objects are supported in the Unified IP MIB; however, only read-only access is
provided.
The following tables in RFC 4444 are supported; however, only read-only access is allowed.
Tables in RFC 4444 that are not listed in the table below are not supported. For example, the
isisRATable is not supported.
Object group nameObject identifierComments
isisManAreaAddrTable 1.3.6.1.2.1.138.1.1.2-
isisAr eaAddrTable1. 3.6.1.2.1.138.1.1.3-
Unified IP MIB Reference61
53-1002549-02
RFC 4444: Management Information Base for Intermediate System to Intermediate System (IS-IS)
NOTE
Object group nameObject identifierComments
isisSummAddrTable 1.3.6.1.2.1.138.1.1.4-
isisRedistributeAdd rTable1.3.6.1.2.1.138.1.1.5-
isisRouterTable1. 3.6.1.2.1.138.1.1.6-
isisSysLevelTable1.3.6.1.2 .1.138.1.2.1-
isisCircTable1.3.6.1.2.1.138.1.3.2The following objects from this table
are not supported:
• isisCircMeshGroupEnabled will
return INACTIVE.
• isisCircMeshGroup will return
zero (0).
Also, the object isisCirc3WayEnabled
is always ON for Pt 2 Pt.
isisCircLevelTable1.3.6.1.2.1.138.1.4.1-
isisSystemCounterTable 1.3.6.1.2.1.138.1.5.1-
isisCircuitCounterTable1.3.6.1.2.1.138.1.5.2-
isisPacketCounterTable1.3.6.1.2.1.138.1.5.3-
isisIsAdjTable1.3.6.1.2.1.138.1.6.1-
isisIsAdjAreaAddrTable1.3.6.1.2.1.138.1.6.2-
isisIsAdjIPAddrTable1.3.6.1.2.1.138.1.6.3-
isisIsAdjProtSuppTable1.3.6.1.2.1.138.1.6.4-
isisIPRATable1.3.6.1.2.1.138.1.8.1-
isisLSPSummaryTable 1.3.6.1.2.1.138.1.9.1-
isisLSPTLV Table1.3.6.1.2.1.138.1.9.2-
isisNOTIFICATION1.3.6.1.2.1.138.1.10-
Notifications
IS-IS notification is enabled by default. To disable notification, issue the no snmp-server enable
traps isis command at the device CLI. Use snmp-server enable traps isis command to re-enable
notification.
Tab le 3 lists the notifications in RFC 4444 that are supported on the Brocade NetIron XMR,
Brocade NetIron MLX, Brocade MLXe, Brocade NetIron CES, and Brocade NetIron CER series
devices.
Only one IS-IS trap is generated for each notification type within a 60-second (1 minute) period. For
example, if several authentication failure notification types occur within a 60-second period, only
one trap is generated for the authentication failure notification type. This duration is different from
what is specified in RFC 4444.
The tables spdCompoundFilterTable, spdSubfiltersTable, spdIpOffsetFilterTable,
spdTimeFilterTable, spdIpsoHeaderFilterTable, spdCompoundActionTable, and spdSubactionsTable
are not supported.
The following tables of scalar objects are supported, except the scalar object
diffServMultiFieldClfrNextFree.
spdStaticFilters
The following table lists the SPD static filter scalar object.
The following table lists the SPD static actions scalar objects.
ObjectObject identifierAccess
spdDropAction1.3.6.1.2.1.153.1.13.1Indicate s that a packet must be
spdDropActionLog1.3.6.1.2.1.153.1.13.2Indicates that a packet must be
spdAcceptAction1.3.6.1.2.1.153.1.13.3Indicates that a packet must be
spdAcceptActionLog1.3.6.1.2.1.153.1.13.4Indicates that a packet must be
dropped and no action or packet
logging is done.
dropped and an action or packet
logging is required.
accepted (or passed-through) and no
action or packet logging is done.
accepted (or passed-through) and an
action or packet logging is required.
MEF Service OAM PM
The Brocade NetIron MLX, Brocade MLXe, Brocade NetIron XMR, Brocade NetIron CES, and
Brocade NetIron CER series devices are provided with the following Metro Ethernet Forum (MEF)
Service OAM (SOAM) Performance Monitoring (PM) MIB.
Ethernet global performance monitoring
configuration table
The mefSoamPmGlobalTable represents the Ethernet global performance monitoring configuration
MIB objects. The SNMP GET and GET-NEXT requests are supported.
The mefSoamDmCfgTable represents the Ethernet delay measurement configuration table MIB
objects. The SNMP GET, GET-NEXT, and SET requests are supported.
Ethernet delay measurement current statistic table
The mefSoamDmCurrentStatsTable represents the Ethernet delay measurement current statistic
MIB objects. The SNMP GET and GET-NEXT requests are supported.
The mefSoamDmHistoricStatsTable represents the Ethernet delay measurement historic statistic
MIB objects. The table supports maximum of 32 rows. Whenever, a new delay measurement
happens, the last row of the table is replaced with the new entry.
The following tables in the IEEE8021-CFM-MIB are supported on the Brocade NetIron XMR,
Brocade NetIron MLX, Brocade MLXe, Brocade NetIron CES, and Brocade NetIron CER series
devices.
The following scalars are supported, but read-only access is available:
• dot1agCfmDefaultMdDefLevel (OID: 1.3.111.2.802.1.1.8.1.2.1) - This object always returns 0.
• dot1agCfmDefaultMdDefMhfCreation (OID: 1.3.111.2.802.1.1.8.1.2.2) - This object always
returns defMHFdefault(2).
• dot1agCfmDefaultMdDefIdPermission (OID: 1.3.111.2.802.1.1.8.1.2.3) - This object always
returns sendIdNone(1).
1.3.6.1.4.1.15007.1.3.1.3.7.1.11No
1.3.6.1.4.1.15007.1.3.1.3.7.1.12No
The following tables are supported, but read-only access for these tables is available at this time:
• dot1agCfmMdTable
• dot1agCfmMaNetTable
• dot1agCfmMaCompTable
70Unified IP MIB Reference
53-1002549-02
IEEE8021-CFM-MIB
• dot1agCfmMaMepListTable
• dot1agCfmMepTable
• dot1agCfmLtrTable
• dot1agCfmMepDbTable
Other tables or the dot1agCfmFaultAlarm notification are not supported.
dot1agCfmMdTable
The dot1agCfmMdTable is the Maintenance Domain table. Each row in the domain represents a
different Maintenance Domain. It is indexed by the dot1agCfmMdIndex object. Only read-only
access is available for the objects listed in the below table.
Each row in the dot1agCfmMaNetTable represents an Maintenance Association (MA), which is a set
of maintenance association end points (MEPs). Each MEP is configured with a single service
instance. It is indexed by the dot1agCfmMdIndex and dot1agCfmMaIndex objects.
Only read-only access is available for these objects.
Object group nameTypeObject identifierComments
dot1agCfmMaIndexUnsigned321.3.111.2.802.1.1.8.1.6.1.1.1 Index variable.
The dot1agCfmMaCompTable is the MA component table. Each row in the table represents an MA,
which is a set of MEPs. Each MEP is configured with a single service instance. It is indexed by
dot1agCfmMaComponentId, dot1agCfmMdIndex, and dot1agCfmMaIndex. Only read-only access is
available for this table.
The dot1agCfmMaMepListTable contains the list of known MEPs for a given MA. It is indexed by
dot1agCfmMdIndex, dot1agCfmMaIndex, and dot1agCfmMaMepListIdentifier.
Object group nameTypeObject identifierComments
dot1agCfmMaMepListIdentifierdot1agCfmMepId1.3.111.2.802.1.1.8.1.6.3.1.1 Index variable.
The dot1agCfmMepTable is the Maintenance Association End Point (MEP) table. Each row in the
table represents a different MEP. It is indexed by dot1agCfmMdIndex, dot1agCfmMaIndex, and
dot1agCfmMepIdentifier.
72Unified IP MIB Reference
53-1002549-02
Loading...
+ 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.