MSTP-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsMSTP-MIB

Last Updated: 2000-07-15

Category: STP/RSTP

Description: Manages Multiple Spanning Tree Protocol instance configuration and port state.

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 MSTP-MIB?

MSTP-MIB is a MIB module for managing Multiple Spanning Tree Protocol (MSTP, IEEE 802.1s) instances, which allow multiple spanning-tree instances to be mapped onto VLANs for loop-free Layer 2 topologies. It exposes configuration and status data for each MST instance and its per-port state, including port role, forwarding/blocking state, and bridge priority/region parameters. Its monitoring focus is network topology and port operational status: administrators track port state transitions (blocking, learning, forwarding) and instance-to-VLAN mapping to detect spanning-tree topology changes, loops, or misconfigured regions rather than physical hardware sensors. It commonly builds on the base bridge MIB (BRIDGE-MIB) and IEEE 802.1 spanning-tree conventions, since MSTP is an extension of classic STP/RSTP bridging. It is deployed on enterprise and data-center Ethernet switches running MSTP for VLAN-aware loop prevention, and this MSTP-MIB reference documents the objects available for tracking that state.

IPNetwork Monitor allows you to monitor SNMP objects defined in MSTP-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

  • Enterprise/data-center Ethernet switch

Monitoring Examples

An operator polling the per-instance port table would check a port's spanning-tree state and role for a given MST instance, revealing whether a port is unexpectedly stuck in blocking state, which would indicate a topology change or misconfigured region boundary. Comparing instance-to-VLAN mappings across switches helps confirm consistent MSTP region configuration network-wide, catching a switch that fell out of sync after a topology change.

What Can Be Monitored

  • MST instance port state (forwarding/blocking/learning)
  • port role per instance
  • MST region/bridge priority configuration
  • instance-to-VLAN mapping
  • topology change count
Imported Objects

From DLINK-ID-REC-MIB

dlink-common-mgmt

From RFC1155-SMI

Counter

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
TimeTicks
Unsigned32

From SNMPv2-TC

DisplayString
RowStatus
TruthValue
OIDs

RFC description

Multiple Spanning Tree Protocol management for bridge instance control and port topology state.

Start monitoring Enterprise/data-center Ethernet switches 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 MSTP-MIB