BROCADE-MPLS-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › BROCADE-MPLS-MIB

Organization: Extreme Networks, Inc.

Last Updated: 2018-05-29

Category: MPLS and Traffic Engineering, Vendor: Foundry/Brocade

Description: Manages MPLS label switching configuration and LSP statistics on Brocade IP/MPLS network devices.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is BROCADE-MPLS-MIB?

BROCADE-MPLS-MIB (internally prefixed "bcsi" for Brocade Communications Systems Inc., later maintained by Extreme Networks) manages MPLS label-switching configuration on Brocade/Extreme IP/MPLS routing platforms. It exposes administrative group definitions, per-interface MPLS enablement/admin-group membership, and a count of configured label-switched paths. It is primarily a software/control-plane monitoring MIB -- bcsiMplsConfiguredLsps gives a running LSP count useful for detecting unexpected loss or unplanned growth in traffic-engineered paths, and bcsiMplsNotifications reports MPLS-related fault or state-change events, rather than physical hardware sensor data. It is an MPLS-specific extension typically deployed alongside standard IETF MPLS MIBs and the vendor's own system/interface MIBs. It is used on Brocade/Extreme service-provider or enterprise core routers running MPLS traffic engineering. Engineers can download the BROCADE-MPLS-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in BROCADE-MPLS-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Brocade/Extreme IP/MPLS core router

Monitoring Examples

A network engineer reads bcsiMplsInterfaceTable (bcsiMplsInterfaceIndex, bcsiMplsInterfaceAdminGroup, bcsiMplsInterfaceRowStatus) to confirm which interfaces are MPLS-enabled and their administrative group membership used for constrained-path routing. bcsiMplsConfiguredLsps is checked as a running count of provisioned label-switched paths, flagging unexpected drops as a possible signaling failure. bcsiMplsAdminGroupTable (bcsiMplsAdminGroupId, bcsiMplsAdminGroupName) lets the admin verify link-coloring definitions used in traffic-engineering constraints.

What Can Be Monitored

  • MPLS-enabled interface list
  • administrative group assignments
  • configured LSP count
  • MPLS provisioning/row status
  • MPLS fault notifications
Imported Objects

From Brocade-REG-MIB

bcsiModulesOBJECT-IDENTITY

From MPLS-TC-STD-MIB

MplsTunnelAffinity

From SNMPv2-SMI

Counter32
Counter64
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString
RowStatus
TEXTUAL-CONVENTION
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using bcsiMplsLspPackets OID:

Select a Brocade/Extreme IP/MPLS core router as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type bcsiMplsLspPackets into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of egress Layer-3 VPN and IPoMPLS packets meeting the in-label and tunnel criteria. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter64-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Proprietary MPLS MIB for Extreme Networks switches, managing Multi-Protocol Label Switched Paths and tunnel configurations.

Start monitoring Brocade/Extreme IP/MPLS core routers with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download BROCADE-MPLS-MIB