All MIBs › HH3C-LswRSTP-MIB
Organization: Hangzhou H3C Tech. Co., Ltd.
Last Updated: 2001-06-29
Category: Technology: Switching/L2, Vendor: H3C/HH3C
Description: Manages Rapid Spanning Tree Protocol (RSTP) port states, edge ports, and topology changes on H3C switches.
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 HH3C-LswRSTP-MIB?
HH3C-LswRSTP-MIB is an H3C vendor MIB implementing management objects for Rapid Spanning Tree Protocol (RSTP) on H3C Layer 2 switches. It exposes per-port and per-bridge data such as port role, port state, edge-port designation, and topology-change event counts, extending the standard bridge/spanning-tree data model with H3C-specific detail. Operationally it is used to monitor the software health of the Layer 2 topology: a port stuck in a non-forwarding state, frequent topology-change notifications, or an edge port flapping all indicate network instability or a misconfigured/failing link. It works alongside the IETF BRIDGE-MIB and P-BRIDGE/Q-BRIDGE MIBs which define the base spanning-tree object model that RSTP extends. It is deployed on H3C campus and enterprise Layer 2 switches forming redundant Ethernet topologies where fast convergence after a link failure is required. Engineers can download the HH3C-LswRSTP-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in HH3C-LswRSTP-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
- H3C Layer 2 switch
Monitoring Examples
No specific object names were supplied in the source for this MIB, so concrete OIDs cannot be cited, but a network engineer would typically poll per-port RSTP role/state (root, designated, alternate, forwarding, discarding) and topology-change counters to verify the ring or tree has converged. A port that remains in discarding state longer than expected, or a rapidly incrementing topology-change counter, signals a flapping link or a spanning-tree misconfiguration.
What Can Be Monitored
- per-port RSTP role and state
- edge-port designation
- topology-change count
- port forwarding/discarding status
Imported Objects
From BRIDGE-MIB
| dot1dStpPort | |
| dot1dStpPortEntry |
From HH3C-OID-MIB
| hh3clswCommon | OBJECT-IDENTITY |
From SNMPv2-SMI
| Counter32 | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| MacAddress | |
| TEXTUAL-CONVENTION | |
| TruthValue |
How to Use in IPNetwork Monitor
Example using hh3cdot1dStpRXStpBPDU OID:
OIDs
RFC description
Manages Rapid Spanning Tree Protocol (RSTP) configuration and statistics for H3C switches.
Start monitoring H3C Layer 2 switch (Rapid Spanning Tree Protocol) 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.