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.
Parsed from file DOCS-CABLE-DEVICE-MIB.mib
Module: DOCS-CABLE-DEVICE-MIB
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.
docsDevSTPControl OBJECT-TYPE
SYNTAX INTEGER {
stEnabled(1),
noStFilterBpdu(2),
noStPassBpdu(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"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."
View at oid-info.com
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.
Parsed from file rfc4639-DOCSIS-Cable-Device.mib.txt
Company: None
Module: DOCS-CABLE-DEVICE-MIB
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.
docsDevSTPControl OBJECT-TYPE SYNTAX INTEGER { stEnabled(1), noStFilterBpdu(2), noStPassBpdu(3) } MAX-ACCESS read-write STATUS current DESCRIPTION "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." ::= { docsDevBase 5 }
docsDevSTPControl OBJECT-TYPE SYNTAX INTEGER { stEnabled(1), noStFilterBpdu(2), noStPassBpdu(3) } ACCESS read-write STATUS mandatory DESCRIPTION "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." DEFVAL { noStFilterBpdu } ::= { docsDevBase 5 }
Automatically extracted from RFC2669
docsDevSTPControl OBJECT-TYPE SYNTAX INTEGER { stEnabled(1), noStFilterBpdu(2), noStPassBpdu(3) } MAX-ACCESS read-write STATUS current DESCRIPTION "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." DEFVAL { noStFilterBpdu } ::= { docsDevBase 5 }
docsDevSTPControl OBJECT-TYPE SYNTAX INTEGER { stEnabled(1), noStFilterBpdu(2), noStPassBpdu(3) } MAX-ACCESS read-write STATUS current DESCRIPTION "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." DEFVAL { noStFilterBpdu } ::= { docsDevBase 5 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.69.1.1.5.0 | docsDevSTPControl | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.69.1.1.1 | docsDevRole | 1 | 1 | Defines the current role of this device. cm(1) is a Cable Modem, cmtsActive(2) is a Cable Modem Termination System that is contr… |
| 1.3.6.1.2.1.69.1.1.2 | docsDevDateTime | 1 | 1 | docsDevDateTime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-write STATUS current DESCRIPTION "The date and time, with option… |
| 1.3.6.1.2.1.69.1.1.3 | docsDevResetNow | 1 | 1 | Setting this object to true(1) causes the device to reset. Reading this object always returns false(2). |
| 1.3.6.1.2.1.69.1.1.4 | docsDevSerialNumber | 1 | 1 | The manufacturer's serial number for this device. |
| 1.3.6.1.2.1.69.1.1.6 | docsDevIgmpModeControl | 1 | 1 | This object controls the IGMP mode of operation for the CM or CMTS. In passive mode, the device forwards IGMP between interfaces… |
| 1.3.6.1.2.1.69.1.1.7 | docsDevMaxCpe | 1 | 1 | The maximum number of CPEs that can be granted access through a CM during a CM epoch. This value can be obtained from the CM con… |