SOURCE-ROUTING-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for SOURCE-ROUTING-MIB.
30
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
30 total| Object Name |
|---|
dot1dSrPortTableA table that contains information about every
port that is associated with this source route
bridge. SEQUENCE OF Dot1dSrPortEntry .1.3.6.1.2.1.17.3.1 |
dot1dSrPortEntryA list of information for each port of a source
route bridge. Dot1dSrPortEntry .1.3.6.1.2.1.17.3.1.1 |
dot1dSrPortThe port number of the port for which this entry
contains Source Route management information.ro INTEGER .1.3.6.1.2.1.17.3.1.1.1 |
dot1dSrPortHopCountThe maximum number of routing descriptors allowed
in an All Paths or Spanning Tree Explorer frames.rw INTEGER .1.3.6.1.2.1.17.3.1.1.2 |
dot1dSrPortLocalSegmentThe segment number that uniquely identifies the
segment to which this port is connected. Current
source routing protocols limit this value to the
range: 0 through 4095. (The value 0 is used by
some management applications for special test
cases.) A value of 65535 signifies that no segment
number is assigned to this port.rw INTEGER .1.3.6.1.2.1.17.3.1.1.3 |
dot1dSrPortBridgeNumA bridge number uniquely identifies a bridge when
more than one bridge is used to span the same two
segments. Current source routing protocols limit
this value to the range: 0 through 15. A value of
65535 signifies that no bridge number is assigned
to this bridge.rw INTEGER .1.3.6.1.2.1.17.3.1.1.4 |
dot1dSrPortTargetSegmentThe segment number that corresponds to the target
segment this port is considered to be connected to
by the bridge. Current source routing protocols
limit this value to the range: 0 through 4095.
(The value 0 is used by some management
applications for special test cases.) A value of
65535 signifies that no target segment is assigned
to this port.rw INTEGER .1.3.6.1.2.1.17.3.1.1.5 |
dot1dSrPortLargestFrameThe maximum size of the INFO field (LLC and
above) that this port can send/receive. It does
not include any MAC level (framing) octets. The
value of this object is used by this bridge to
determine whether a modification of the
LargestFrame (LF, see [14]) field of the Routing
Control field of the Routing Information Field is
necessary.
64 valid values are defined by the IEEE 802.5M SRT
Addendum: 516, 635, 754, 873, 993, 1112, 1231,
1350, 1470, 1542, 1615, 1688, 1761, 1833, 1906,
1979, 2052, 2345, 2638, 2932, 3225, 3518, 3812,
4105, 4399, 4865, 5331, 5798, 6264, 6730, 7197,
7663, 8130, 8539, 8949, 9358, 9768, 10178, 10587,
10997, 11407, 12199, 12992, 13785, 14578, 15370,
16163, 16956, 17749, 20730, 23711, 26693, 29674,
32655, 35637, 38618, 41600, 44591, 47583, 50575,
53567, 56559, 59551, and 65535.
An illegal value will not be accepted by the
bridge.rw INTEGER .1.3.6.1.2.1.17.3.1.1.6 |
dot1dSrPortSTESpanModeDetermines 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.rw Enumeration .1.3.6.1.2.1.17.3.1.1.7 |
dot1dSrPortSpecInFramesThe number of Specifically Routed frames, also
referred to as Source Routed Frames, that have
been received from this port's segment.ro Counter .1.3.6.1.2.1.17.3.1.1.8 |
dot1dSrPortSpecOutFramesThe number of Specifically Routed frames, also
referred to as Source Routed Frames, that this
port has transmitted on its segment.ro Counter .1.3.6.1.2.1.17.3.1.1.9 |
dot1dSrPortApeInFramesThe number of All Paths Explorer frames, also
referred to as All Routes Explorer frames, that
have been received by this port from its segment.ro Counter .1.3.6.1.2.1.17.3.1.1.10 |
dot1dSrPortApeOutFramesThe number of all Paths Explorer Frames, also
referred to as All Routes Explorer frames, that
have been transmitted by this port on its
segment.ro Counter .1.3.6.1.2.1.17.3.1.1.11 |
dot1dSrPortSteInFramesThe number of spanning tree explorer frames that
have been received by this port from its segment.ro Counter .1.3.6.1.2.1.17.3.1.1.12 |
dot1dSrPortSteOutFramesThe number of spanning tree explorer frames that
have been transmitted by this port on its
segment.ro Counter .1.3.6.1.2.1.17.3.1.1.13 |
dot1dSrPortSegmentMismatchDiscardsThe number of explorer frames that have been
discarded by this port because the routing
descriptor field contained an invalid adjacent
segment value.ro Counter .1.3.6.1.2.1.17.3.1.1.14 |
dot1dSrPortDuplicateSegmentDiscardsThe number of frames that have been discarded by
this port because the routing descriptor field
contained a duplicate segment identifier.ro Counter .1.3.6.1.2.1.17.3.1.1.15 |
dot1dSrPortHopCountExceededDiscardsThe number of explorer frames that have been
discarded by this port because the Routing
Information Field has exceeded the maximum route
descriptor length.ro Counter .1.3.6.1.2.1.17.3.1.1.16 |
dot1dSrPortDupLanIdOrTreeErrorsThe number of duplicate LAN IDs or Tree errors.
This helps in detection of problems in networks
containing older IBM Source Routing Bridges.ro Counter .1.3.6.1.2.1.17.3.1.1.17 |
dot1dSrPortLanIdMismatchesThe number of ARE and STE frames that were
discarded because the last LAN ID in the routing
information field did not equal the LAN-in ID.
This error can occur in implementations which do
only a LAN-in ID and Bridge Number check instead
of a LAN-in ID, Bridge Number, and LAN-out ID
check before they forward broadcast frames.ro Counter .1.3.6.1.2.1.17.3.1.1.18 |
dot1dSrBridgeLfModeIndicates whether the bridge operates using older
3 bit length negotiation fields or the newer 6 bit
length field in its RIF.rw Enumeration .1.3.6.1.2.1.17.3.2 |
dot1dPortPair OBJECT IDENTIFIER .1.3.6.1.2.1.17.10 |
BRIDGE-MIB Unknown .1.3.6.1.2.1.17.10 |
dot1dPortPairTableSizeThe total number of entries in the Bridge Port
Pair Database.ro Gauge .1.3.6.1.2.1.17.10.1 |
dot1dPortPairTableA table that contains information about every
port pair database entity associated with this
source routing bridge. SEQUENCE OF Dot1dPortPairEntry .1.3.6.1.2.1.17.10.2 |
dot1dPortPairEntryA list of information for each port pair entity
of a bridge. Dot1dPortPairEntry .1.3.6.1.2.1.17.10.2.1 |
dot1dPortPairLowPortThe port number of the lower numbered port for
which this entry contains port pair database
information.rw INTEGER .1.3.6.1.2.1.17.10.2.1.1 |
dot1dPortPairHighPortThe port number of the higher numbered port for
which this entry contains port pair database
information.rw INTEGER .1.3.6.1.2.1.17.10.2.1.2 |
dot1dPortPairBridgeNumA bridge number that uniquely identifies the path
provided by this source routing bridge between the
segments connected to dot1dPortPairLowPort and
dot1dPortPairHighPort. The purpose of bridge
number is to disambiguate between multiple paths
connecting the same two LANs.rw INTEGER .1.3.6.1.2.1.17.10.2.1.3 |
dot1dPortPairBridgeStateThe state of dot1dPortPairBridgeNum. Writing
'invalid(3)' to this object removes the
corresponding entry.rw Enumeration .1.3.6.1.2.1.17.10.2.1.4 |