ODSLANBlazer7000-MIB :: lanBlazer7000SwitchSTPConfig

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › ODSLANBlazer7000-MIB › lanBlazer7000SwitchSTPConfig

lanBlazer7000SwitchSTPConfig

Module: ODSLANBlazer7000-MIB

OID (symbolic): ODSLANBlazer7000-MIB::lanBlazer7000SwitchSTPConfig

OID (numeric): 1.3.6.1.4.1.50.8.1.2.1.5.1.1.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: When set to ieee8021dStp(1), the switch executes spanning tree conformant to the IEEE 802.1D bridging standard. The switch runs one instance of spanning tree.

When set to stpPerVlan(2), the switch executes a separate instance of spanning tree for each virtual LAN. This configuration conforms to the model that instances of virtual LANs within the switch are separate virtual bridging functions. This method may not work well with bridge/routers that are also running spanning tree.

When set to twoLayerStp(3), the switch executes a two-layer spanning tree to prevent loops. Two layer spanning tree creates a higher 'plane' of spanning tree between VLAN devices. This method of running spanning tree is 'plug and play' with bridge/router type devices and also scales better than the other two methods for large environments.

When set to disable(4), spanning tree is disabled in the switch.

What is lanBlazer7000SwitchSTPConfig?

Selects the switch's overall spanning-tree operating mode: ieee8021dStp(1) runs one standard 802.1D instance across the whole switch, stpPerVlan(2) runs a separate spanning-tree instance per VLAN (useful for per-VLAN virtual bridging but potentially awkward with routers also running STP), twoLayerStp(3) adds a higher-level plane of spanning tree between VLANs for better interoperability and scaling in large environments, and disable(4) turns spanning tree off entirely. An admin running many VLANs in a large campus would choose twoLayerStp(3) for its 'plug and play' behavior with routers, while a small flat network might just use ieee8021dStp(1).

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.50.8.1.2.1.5.1.1.1
snmpwalk -v2c -c public <target> ODSLANBlazer7000-MIB::lanBlazer7000SwitchSTPConfig

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.50.8.1.2.1.5.1.1.1.1
snmpget -v2c -c public <target> ODSLANBlazer7000-MIB::lanBlazer7000SwitchSTPConfig.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.50.8.1.2.1.5.1.1.1.1 i <value>

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> lanBlazer7000SwitchSTPConfig.1

Start monitoring ODS LANBlazer 7000 WAN test/analysis instrument with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ODSLANBlazer7000-MIB::lanBlazer7000SwitchSTPConfig OID value, configure state conditions and alerts, and monitor any ODS LANBlazer 7000 WAN test/analysis instrument from a single console.

OID Breakdown

Upper-level ancestors (6 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
Numeric OIDNameModule
1.3.6.1.4.1.50odsODSLANBlazer7000-MIB
1.3.6.1.4.1.50.8odsTPSODSLANBlazer7000-MIB
1.3.6.1.4.1.50.8.1odsLANBlazerODSLANBlazer7000-MIB
1.3.6.1.4.1.50.8.1.2odsLANBlazerMibsODSLANBlazer7000-MIB
1.3.6.1.4.1.50.8.1.2.1odsLANBlazer7000MibODSLANBlazer7000-MIB
1.3.6.1.4.1.50.8.1.2.1.5lanBlazer7000SwitchingODSLANBlazer7000-MIB
1.3.6.1.4.1.50.8.1.2.1.5.1lanBlazer7000SwitchingLayerIIODSLANBlazer7000-MIB
1.3.6.1.4.1.50.8.1.2.1.5.1.1lanBlazer7000SwitchGenODSLANBlazer7000-MIB
1.3.6.1.4.1.50.8.1.2.1.5.1.1.1lanBlazer7000SwitchSTPConfigODSLANBlazer7000-MIB