Determines how this port behaves when presented
with a Spanning Tree Explorer frame. The value
'disabled(2)' indicates that the port will not
accept or send Spanning Tree Explorer packets; any
STE packets received will be silently discarded.
The value 'forced(3)' indicates the port will
always accept and propagate Spanning Tree Explorer
frames. This allows a manually configured
Spanning Tree for this class of packet to be
configured. Note that unlike transparent
bridging, this is not catastrophic to the network
if there are loops. The value 'auto-span(1)' can
only be returned by a bridge that both implements
the Spanning Tree Protocol and has use of the
protocol enabled on this port. The behavior of the
port for Spanning Tree Explorer frames is
determined by the state of dot1dStpPortState. If
the port is in the 'forwarding' state, the frame
will be accepted or propagated. Otherwise, it
will be silently discarded.
dot1dSrPortSTESpanMode OBJECT-TYPE
SYNTAX INTEGER {
auto-span(1),
disabled(2),
forced(3)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Determines how this port behaves when presented
with a Spanning Tree Explorer frame. The value
disabled(2) indicates that the port will not
accept or send Spanning Tree Explorer packets; any
STE packets received will be silently discarded.
The value
orced(3) indicates the port will
always accept and propagate Spanning Tree Explorer
frames. This allows a manually configured
Spanning Tree for this class of packet to be
configured. Note that unlike transparent
bridging, this is not catastrophic to the network
if there are loops. The value auto-span(1) can
only be returned by a bridge that both implements
the Spanning Tree Protocol and has use of the
protocol enabled on this port. The behavior of the
port for Spanning Tree Explorer frames is
determined by the state of dot1dStpPortState. If
the port is in the
orwarding state, the frame
will be accepted or propagated. Otherwise, it
will be silently discarded."
View at oid-info.com
Determines how this port behaves when presented
with a Spanning Tree Explorer frame. The value
'disabled(2)' indicates that the port will not
accept or send Spanning Tree Explorer packets; any
STE packets received will be silently discarded.
The value 'forced(3)' indicates the port will
always accept and propagate Spanning Tree Explorer
frames. This allows a manually configured
Spanning Tree for this class of packet to be
configured. Note that unlike transparent
bridging, this is not catastrophic to the network
if there are loops. The value 'auto-span(1)' can
only be returned by a bridge that both implements
the Spanning Tree Protocol and has use of the
protocol enabled on this port. The behavior of the
port for Spanning Tree Explorer frames is
determined by the state of dot1dStpPortState. If
the port is in the 'forwarding' state, the frame
will be accepted or propagated. Otherwise, it
will be silently discarded.
Parsed from file rfc1525.mib.txt
Company: None
Module: SOURCE-ROUTING-MIB
Determines how this port behaves when presented
with a Spanning Tree Explorer frame. The value
'disabled(2)' indicates that the port will not
accept or send Spanning Tree Explorer packets; any
STE packets received will be silently discarded.
The value 'forced(3)' indicates the port will
always accept and propagate Spanning Tree Explorer
frames. This allows a manually configured
Spanning Tree for this class of packet to be
configured. Note that unlike transparent bridging
this is not catastrophic to the network if there
are loops. The value 'auto-span(1)' can only be
returned by a bridge that both implements the
Spanning Tree Protocol and has use of the protocol
enabled on this port. The behavior of the port for
Spanning Tree Explorer frames is determined by the
state of dot1dStpPortState. If the port is in the
'forwarding' state, the frame will be accepted or
propagated. Otherwise it will be silently
discarded.
Parsed from file RFC1286-MIB.mib
Module: RFC1286-MIB
dot1dSrPortSTESpanMode OBJECT-TYPE SYNTAX INTEGER { auto-span(1), disabled(2), forced(3) } ACCESS read-write STATUS mandatory DESCRIPTION "Determines how this port behaves when presented with a Spanning Tree Explorer frame. The value 'disabled(2)' indicates that the port will not accept or send Spanning Tree Explorer packets; any STE packets received will be silently discarded. The value 'forced(3)' indicates the port will always accept and propagate Spanning Tree Explorer frames. This allows a manually configured Spanning Tree for this class of packet to be configured. Note that unlike transparent bridging, this is not catastrophic to the network if there are loops. The value 'auto-span(1)' can only be returned by a bridge that both implements the Spanning Tree Protocol and has use of the protocol enabled on this port. The behavior of the port for Spanning Tree Explorer frames is determined by the state of dot1dStpPortState. If the port is in the 'forwarding' state, the frame will be accepted or propagated. Otherwise, it will be silently discarded." ::= { dot1dSrPortEntry 7 }
Automatically extracted from RFC1525
dot1dSrPortSTESpanMode OBJECT-TYPE SYNTAX INTEGER { auto-span(1), disabled(2), forced(3) } ACCESS read-write STATUS mandatory DESCRIPTION "Determines how this port behaves when presented with a Spanning Tree Explorer frame. The value 'disabled(2)' indicates that the port will not accept or send Spanning Tree Explorer packets; any STE packets received will be silently discarded. The value 'forced(3)' indicates the port will always accept and propagate Spanning Tree Explorer frames. This allows a manually configured Spanning Tree for this class of packet to be configured. Note that unlike transparent bridging, this is not catastrophic to the network if there are loops. The value 'auto-span(1)' can only be returned by a bridge that both implements the Spanning Tree Protocol and has use of the protocol enabled on this port. The behavior of the port for Spanning Tree Explorer frames is determined by the state of dot1dStpPortState. If the port is in the 'forwarding' state, the frame will be accepted or propagated. Otherwise, it will be silently discarded." ::= { dot1dSrPortEntry 7 }
dot1dSrPortSTESpanMode OBJECT-TYPE SYNTAX INTEGER { auto-span(1), disabled(2), forced(3) } ACCESS read-write STATUS mandatory DESCRIPTION "Determines how this port behaves when presented with a Spanning Tree Explorer frame. The value 'disabled(2)' indicates that the port will not accept or send Spanning Tree Explorer packets; any STE packets received will be silently discarded. The value 'forced(3)' indicates the port will always accept and propagate Spanning Tree Explorer frames. This allows a manually configured Spanning Tree for this class of packet to be configured. Note that unlike transparent bridging this is not catastrophic to the network if there are loops. The value 'auto-span(1)' can only be returned by a bridge that both implements the Spanning Tree Protocol and has use of the protocol enabled on this port. The behavior of the port for Spanning Tree Explorer frames is determined by the state of dot1dStpPortState. If the port is in the 'forwarding' state, the frame will be accepted or propagated. Otherwise it will be silently discarded." ::= { dot1dSrPortEntry 7 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.17.3.1.1.1 | dot1dSrPort | 0 | 0 | The port number of the port for which this entry contains Source Route management information. |
| 1.3.6.1.2.1.17.3.1.1.2 | dot1dSrPortHopCount | 0 | 0 | The maximum number of routing descriptors allowed in an All Paths or Spanning Tree Explorer frames. |
| 1.3.6.1.2.1.17.3.1.1.3 | dot1dSrPortLocalSegment | 0 | 0 | The segment number that uniquely identifies the segment to which this port is connected. Current source routing protocols limit t… |
| 1.3.6.1.2.1.17.3.1.1.4 | dot1dSrPortBridgeNum | 0 | 0 | A bridge number uniquely identifies a bridge when more than one bridge is used to span the same two segments. Current source rou… |
| 1.3.6.1.2.1.17.3.1.1.5 | dot1dSrPortTargetSegment | 0 | 0 | The segment number that corresponds to the target segment this port is considered to be connected to by the bridge. Current sour… |
| 1.3.6.1.2.1.17.3.1.1.6 | dot1dSrPortLargestFrame | 0 | 0 | The maximum size of the INFO field (LLC and above) that this port can send/receive. It does not include any MAC level (framing) … |
| 1.3.6.1.2.1.17.3.1.1.8 | dot1dSrPortSpecInFrames | 0 | 0 | The number of specifically routed frames that have been received from this port's segment. |
| 1.3.6.1.2.1.17.3.1.1.9 | dot1dSrPortSpecOutFrames | 0 | 0 | The number of specifically routed frames that this port has transmitted on its segment. |
| 1.3.6.1.2.1.17.3.1.1.10 | dot1dSrPortApeInFrames | 0 | 0 | The number of all paths explorer frames that have been received by this port from its segment. |
| 1.3.6.1.2.1.17.3.1.1.11 | dot1dSrPortApeOutFrames | 0 | 0 | The number of all paths explorer frames that have been transmitted by this port on its segment. |
| 1.3.6.1.2.1.17.3.1.1.12 | dot1dSrPortSteInFrames | 0 | 0 | The number of spanning tree explorer frames that have been received by this port from its segment. |
| 1.3.6.1.2.1.17.3.1.1.13 | dot1dSrPortSteOutFrames | 0 | 0 | The number of spanning tree explorer frames that have been transmitted by this port on its segment. |
| 1.3.6.1.2.1.17.3.1.1.14 | dot1dSrPortSegmentMismatchDiscards | 0 | 0 | The number of explorer frames that have been discarded by this port because the routing descriptor field contained an invalid adj… |
| 1.3.6.1.2.1.17.3.1.1.15 | dot1dSrPortDuplicateSegmentDiscards | 0 | 0 | The number of frames that have been discarded by this port because the routing descriptor field contained a duplicate segment ide… |
| 1.3.6.1.2.1.17.3.1.1.16 | dot1dSrPortHopCountExceededDiscards | 0 | 0 | The number of explorer frames that have been discarded by this port because the Routing Information Field has exceeded the maximu… |
| 1.3.6.1.2.1.17.3.1.1.17 | dot1dSrPortDupLanIdOrTreeErrors | 0 | 0 | The number of duplicate LAN IDs or Tree errors. This helps in detection of problems in networks containing older IBM Source Routi… |
| 1.3.6.1.2.1.17.3.1.1.18 | dot1dSrPortLanIdMismatches | 0 | 0 | The number of ARE and STE frames that were discarded because the last LAN ID in the routing information field did not equal the L… |