UBIQUOSS-STP-MIB :: pvStpTopChanges

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

All MIBs › UBIQUOSS-STP-MIB › pvStpTopChanges

pvStpTopChanges

Module: UBIQUOSS-STP-MIB

OID (symbolic): UBIQUOSS-STP-MIB::pvStpTopChanges

OID (numeric): 1.3.6.1.4.1.7800.2.21.1.1.4.1.1.3

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Description.

What is pvStpTopChanges?

This counts how many topology changes have occurred on this VLAN's spanning tree instance since it was last reset. A high or rapidly climbing count points to an unstable link or a port flapping somewhere within that VLAN's tree.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.7800.2.21.1.1.4.1.1.3
snmpwalk -v2c -c public <target> UBIQUOSS-STP-MIB::pvStpTopChanges

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.7800.2.21.1.1.4.1.1.3.1
snmpget -v2c -c public <target> UBIQUOSS-STP-MIB::pvStpTopChanges.1

Start monitoring Ubiquoss Corp. switching equipment, STP/MSTP (region/instance config and root-bridge election status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the UBIQUOSS-STP-MIB::pvStpTopChanges OID value, configure state conditions and alerts, and monitor any Ubiquoss Corp. switching equipment, STP/MSTP (region/instance config and root-bridge election status) from a single console.

How to Use in IPNetwork Monitor

Select an Ubiquoss Corp. switching equipment, STP/MSTP (region/instance config and root-bridge election status) 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 pvStpTopChanges 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 spanning tree topology changes detected. 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.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.7800ubiquossUBIQUOSS-SMI
1.3.6.1.4.1.7800.2ubiMgmtUBIQUOSS-SMI
Numeric OIDNameModule
1.3.6.1.4.1.7800.2.21ubiStpMIBUBIQUOSS-STP-MIB
1.3.6.1.4.1.7800.2.21.1ubiStpMIBObjectsUBIQUOSS-STP-MIB
1.3.6.1.4.1.7800.2.21.1.1ubiStpTableUBIQUOSS-STP-MIB
1.3.6.1.4.1.7800.2.21.1.1.4pvstpUBIQUOSS-STP-MIB
1.3.6.1.4.1.7800.2.21.1.1.4.1pvStpTableUBIQUOSS-STP-MIB
1.3.6.1.4.1.7800.2.21.1.1.4.1.1pvStpEntryUBIQUOSS-STP-MIB
1.3.6.1.4.1.7800.2.21.1.1.4.1.1.3pvStpTopChangesUBIQUOSS-STP-MIB