RIVERSTONE-STP-MIB

All MIBs › RIVERSTONE-STP-MIB

Organization: Riverstone Networks, Inc

Last Updated: 2000-07-16

Category: Riverstone Networks, Spanning Tree

Description: Manages Spanning Tree Protocol configuration and bridge port states on Riverstone Networks 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 RIVERSTONE-STP-MIB?

RIVERSTONE-STP-MIB extends the standard Spanning Tree Protocol MIB (RFC 1493) with additional configuration and statistics objects specific to Riverstone Networks switches. It exposes data on STP protocol state, supported protocol versions, bridge port base parameters, BPDU send/receive counters, and error/change history for the spanning tree process. This is a network-software status MIB, letting an admin monitor whether STP is enabled and functioning correctly on a switch, when it last changed state, and whether BPDU processing is healthy, which is critical for detecting loop-prevention failures or misconfigurations. It explicitly builds on and extends the IETF Bridge MIB (RFC 1493/BRIDGE-MIB) for spanning tree. It is deployed in Layer 2 switched network monitoring to catch topology instability or blocked-port issues on Riverstone switch infrastructure. Engineers can download the RIVERSTONE-STP-MIB file directly to load it into their MIB browser.

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

Riverstone Networks switches

Monitoring Examples

An admin would poll rsStpStatus and rsStpProtocol to confirm STP is active and which variant (e.g. RSTP, MSTP) is running, and check rsStpLastChanged plus rsStpLastSetErrorReason to spot recent topology changes or configuration errors. The rsStpBaseTable (rsStpBaseEntry) with rsStpBaseBpduSends/rsStpBaseBpduReceives per bridge port reveals whether BPDUs are flowing normally; a port with zero received BPDUs when peers expect it could indicate a misconfigured or blocked link. rsStpBaseBlockBpdu would be checked to confirm intentional BPDU blocking on edge ports.

What Can Be Monitored

STP operational status and protocol version
last STP topology change time
STP configuration error reason
per-port BPDU send/receive counts
BPDU blocking configuration per port

Imported Objects

From BRIDGE-MIB

dot1dBasePortEntry

OBJECT-TYPE

From RSTONE-SMI-MIB

riverstoneMibs

OBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
OBJECT-IDENTITY
OBJECT-TYPE
TimeTicks

From SNMPv2-TC

TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using rsStpBaseBpduSends OID:

Select a Riverstone Networks switch (Spanning Tree Protocol state/BPDU statistics) 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 rsStpBaseBpduSends 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 BPDUs sent out on this port. 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 Counter32-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

OID symbolic	OID numeric	Type	Access	Description
T/F rsStpBaseBlockBpdu	1.3.6.1.4.1.5567.2.12.2.2.1.2	TruthValue	read-write	Set or get the state of BPDU filtering on this port.
C32 rsStpBaseBpduReceives	1.3.6.1.4.1.5567.2.12.2.2.1.4	Counter32	read-only	The number of BPDUs received on this port.
C32 rsStpBaseBpduSendsEx	1.3.6.1.4.1.5567.2.12.2.2.1.3	Counter32	read-only	The number of BPDUs sent out on this port.
T/F rsStpBaseEnableProtocol	1.3.6.1.4.1.5567.2.12.2.2.1.1	TruthValue	read-write	Set or get the state of spanning tree protocol (send/receive) on the port.
rsStpBaseEntry	1.3.6.1.4.1.5567.2.12.2.2.1		not-accessible	Additional configuration capabilities not found in standard mibs such as configuring STP to run on a given port. All ports shown in dot1dBasePortEntry are capable of bridging, and thus can run STP.
rsStpBaseGroup	1.3.6.1.4.1.5567.2.12.10.1.1			A collection of objects providing configuration and monitoring capabilites of Spanning Tree Protocol on a given switch.
rsStpBaseTable	1.3.6.1.4.1.5567.2.12.2.2		not-accessible	This table provides per port control of spanning tree protocol.
rsStpCompliances	1.3.6.1.4.1.5567.2.12.10.2
rsStpConformance	1.3.6.1.4.1.5567.2.12.10
rsStpGlobals	1.3.6.1.4.1.5567.2.12.1			Objects of global scope over one or more instances of Spanning Tree in a given switch.
rsStpGroups	1.3.6.1.4.1.5567.2.12.10.1
TIK rsStpLastChanged	1.3.6.1.4.1.5567.2.12.2.1	TimeTicks	read-only	The last time any object in this table was changed by SNMP or other local management means.
STR rsStpLastSetErrorReason	1.3.6.1.4.1.5567.2.12.1.4	SnmpAdminString	read-only	Reports the agent error code and reason for last failure to set any writable object in this mib. Format of the error code is NNN - reason string where NNN is a numeric identifer.
rsStpMib	1.3.6.1.4.1.5567.2.12			This mib module defines addtional configuration and statistics for Spanning Tree Protocol Management as defined in RFC 1493 Copyright (C) Riverstone Networks, Inc 2000
rsStpMibCompliance	1.3.6.1.4.1.5567.2.12.10.2.1			The compliance statement for device support of Priority and Multicast Filtering extended bridging services.
rsStpPortsLevel	1.3.6.1.4.1.5567.2.12.2			Objects of port level scope providing information about the Spanning tree on that port.
RSS rsStpProtocol	1.3.6.1.4.1.5567.2.12.1.2	RSStpProtocolVersion	read-write	Specify the type of Spanning tree to run for the default instance of Spanning Tree. Changing this object has the effect of causing an existing spanning tree to lose convergence.
I32 rsStpProtocolsSupported	1.3.6.1.4.1.5567.2.12.1.3	Integer32	read-only	Represents range of STP protocols supported. For example the value 6 would mean the switch is capable of both fastSTP(4) + ieee802(2) protocols.
T/F rsStpStatus	1.3.6.1.4.1.5567.2.12.1.1	TruthValue	read-write	The global state of spanning tree protocol on this system. Individual ports may be enabled or disabled as necessary or this master switch can be used to turn all ports on or off. This object will cause a loss of convergence when set.

RFC description

Provides additional Spanning Tree Protocol configuration and statistics for Riverstone switches, supporting IEEE 802.1 and proprietary fast STP variants.

Start monitoring Riverstone Networks switches (Spanning Tree Protocol state/BPDU statistics) 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 RIVERSTONE-STP-MIB