docsDevSTPControl

DOCS-CABLE-DEVICE-MIB · .1.3.6.1.2.1.69.1.1.5
Commands MIB view Table view

Object

scalar r/w Enumeration 
This object controls operation of the spanning tree
protocol (as distinguished from transparent bridging).
          
If set to stEnabled(1), then the spanning tree protocol
is enabled, subject to bridging constraints.
          
If noStFilterBpdu(2), then spanning tree is not active,
and Bridge PDUs received are discarded.
          
If noStPassBpdu(3), then spanning tree is not active,
and Bridge PDUs are transparently forwarded.
          
Note that a device need not implement all of these
options, but that noStFilterBpdu(2) is required.

Context

MIB
DOCS-CABLE-DEVICE-MIB
OID
.1.3.6.1.2.1.69.1.1.5
Type
scalar
Access
readwrite
Status
current
Parent
docsDevBase
Groups
1

Net-SNMP examples

How SNMP and these commands work

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'DOCS-CABLE-DEVICE-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DOCS-CABLE-DEVICE-MIB::docsDevSTPControl.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'DOCS-CABLE-DEVICE-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'DOCS-CABLE-DEVICE-MIB::docsDevSTPControl'

Syntax

Enumeration

Values & Constraints

Enumerated Values
1stEnabled
2noStFilterBpdu
3noStPassBpdu

Conformance

Member of
docsDevBaseGroup
Compliance refinements
docsDevBasicCompliance readonly
It is compliant to implement this object as read-only.
Devices need only support noStFilterBpdu(2).
docsDevCmCompliance readonly Enumeration
Values: noStFilterBpdu(2)
It is compliant to implement this object as read-only.
Devices need only support noStFilterBpdu(2).
docsDevCmtsCompliance readonly Enumeration
Values: noStFilterBpdu(2)
It is compliant to implement this object as read-only.
Devices need only support noStFilterBpdu(2).