AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | Infra | IoT | IT Service | Linux | Network/System | Performance | Protocol | SaaS | Security | Service Level | SNMP | Storage | VMware | VoIP | Web | Wireless

Crumbtrail

MonitorTools.com » Technical documentation » SNMP » MIB » RFC » SOURCE-ROUTING-MIB » Objects

SOURCE-ROUTING-MIB.mib object view, vendor RFC

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file SOURCE-ROUTING-MIB and use it to monitor vendor specific OID's.

SOURCE-ROUTING-MIB file content

Object view of SOURCE-ROUTING-MIB:

Scalar Object
dot1dSrPortEntry .1.3.6.1.2.1.17.3.1.1
A list of information for each port of a source route bridge.
dot1dSrBridgeLfMode .1.3.6.1.2.1.17.3.2
Indicates whether the bridge operates using older 3 bit length negotiation fields or the newer 6 bit length field in its RIF.
dot1dPortPairTableSize .1.3.6.1.2.1.17.10.1
The total number of entries in the Bridge Port Pair Database.
dot1dPortPairEntry .1.3.6.1.2.1.17.10.2.1
A list of information for each port pair entity of a bridge.
Tabular Object
dot1dSrPort .1.3.6.1.2.1.17.3.1.1.1
The port number of the port for which this entry contains Source Route management information.
dot1dSrPortHopCount .1.3.6.1.2.1.17.3.1.1.2
The maximum number of routing descriptors allowed in an All Paths or Spanning Tree Explorer frames.
dot1dSrPortLocalSegment .1.3.6.1.2.1.17.3.1.1.3
The 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.
dot1dSrPortBridgeNum .1.3.6.1.2.1.17.3.1.1.4
A 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.
dot1dSrPortTargetSegment .1.3.6.1.2.1.17.3.1.1.5
The 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.
dot1dSrPortLargestFrame .1.3.6.1.2.1.17.3.1.1.6
The 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.
dot1dSrPortSTESpanMode .1.3.6.1.2.1.17.3.1.1.7
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.
dot1dSrPortSpecInFrames .1.3.6.1.2.1.17.3.1.1.8
The number of Specifically Routed frames, also referred to as Source Routed Frames, that have been received from this port's segment.
dot1dSrPortSpecOutFrames .1.3.6.1.2.1.17.3.1.1.9
The number of Specifically Routed frames, also referred to as Source Routed Frames, that this port has transmitted on its segment.
dot1dSrPortApeInFrames .1.3.6.1.2.1.17.3.1.1.10
The number of All Paths Explorer frames, also referred to as All Routes Explorer frames, that have been received by this port from its segment.
dot1dSrPortApeOutFrames .1.3.6.1.2.1.17.3.1.1.11
The number of all Paths Explorer Frames, also referred to as All Routes Explorer frames, that have been transmitted by this port on its segment.
dot1dSrPortSteInFrames .1.3.6.1.2.1.17.3.1.1.12
The number of spanning tree explorer frames that have been received by this port from its segment.
dot1dSrPortSteOutFrames .1.3.6.1.2.1.17.3.1.1.13
The number of spanning tree explorer frames that have been transmitted by this port on its segment.
dot1dSrPortSegmentMismatchDiscards .1.3.6.1.2.1.17.3.1.1.14
The number of explorer frames that have been discarded by this port because the routing descriptor field contained an invalid adjacent segment value.
dot1dSrPortDuplicateSegmentDiscards .1.3.6.1.2.1.17.3.1.1.15
The number of frames that have been discarded by this port because the routing descriptor field contained a duplicate segment identifier.
dot1dSrPortHopCountExceededDiscards .1.3.6.1.2.1.17.3.1.1.16
The number of explorer frames that have been discarded by this port because the Routing Information Field has exceeded the maximum route descriptor length.
dot1dSrPortDupLanIdOrTreeErrors .1.3.6.1.2.1.17.3.1.1.17
The number of duplicate LAN IDs or Tree errors. This helps in detection of problems in networks containing older IBM Source Routing Bridges.
dot1dSrPortLanIdMismatches .1.3.6.1.2.1.17.3.1.1.18
The 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.
dot1dPortPairLowPort .1.3.6.1.2.1.17.10.2.1.1
The port number of the lower numbered port for which this entry contains port pair database information.
dot1dPortPairHighPort .1.3.6.1.2.1.17.10.2.1.2
The port number of the higher numbered port for which this entry contains port pair database information.
dot1dPortPairBridgeNum .1.3.6.1.2.1.17.10.2.1.3
A 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.
dot1dPortPairBridgeState .1.3.6.1.2.1.17.10.2.1.4
The state of dot1dPortPairBridgeNum. Writing 'invalid(3)' to this object removes the corresponding entry.
Table
dot1dSrPortTable .1.3.6.1.2.1.17.3.1
A table that contains information about every port that is associated with this source route bridge.
dot1dPortPairTable .1.3.6.1.2.1.17.10.2
A table that contains information about every port pair database entity associated with this source routing bridge.
Object Identifier
dot1dPortPair .1.3.6.1.2.1.17.10