SOURCE-ROUTING-MIB

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsSOURCE-ROUTING-MIB

Category: Network Interfaces, Routing Protocols, VLAN and Bridging

Description: Defines managed objects for source routing bridges used in Token Ring networks.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring SOURCE-ROUTING-MIB with a free 30-day trial of IPNetwork Monitor.

What Is SOURCE-ROUTING-MIB?

SOURCE-ROUTING-MIB is a vendor-neutral IETF/IEEE standards MIB (part of the dot1d bridge MIB family, RFC 1525, built on IEEE 802.5 Token Ring source routing) defining managed objects for source-routing transparent bridges. It exposes per-port bridge configuration and topology data: hop count limits, local/target ring segment numbers, bridge number, largest frame size, and spanning tree explorer (STE) mode. Its data is primarily configuration/topology-oriented rather than hardware health telemetry, though counters for specifically-routed and all-paths-explorer frames let an operator gauge traffic load and detect misconfigured bridging loops - a form of software/protocol health monitoring. It builds directly on the IETF Bridge MIB (BRIDGE-MIB, dot1dBridge subtree) and IEEE 802.5 Token Ring standards. Typical deployment is legacy Token Ring source-route bridging/switching equipment, now largely of historical interest. Engineers can download the SOURCE-ROUTING-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in SOURCE-ROUTING-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • vendor-neutral, standards-based MIB, not tied to a specific manufacturer
  • Token Ring source-routing bridge/switch

Monitoring Examples

dot1dSrPortTable/Entry lists each bridge port's dot1dSrPortHopCount, dot1dSrPortLocalSegment/TargetSegment, and dot1dSrPortBridgeNum, letting an operator verify the source-route path topology is configured correctly. Polling dot1dSrPortSpecInFrames and dot1dSrPortApeInFrames reveals whether explorer frame traffic (used for route discovery) is unusually high, which could indicate a bridging loop or excessive broadcast storm across the Token Ring segment.

What Can Be Monitored

  • hop count per port
  • local/target ring segment numbers
  • bridge number
  • largest frame size
  • specifically-routed frame counts
  • all-paths-explorer frame counts
Imported Objects

From BRIDGE-MIB

dot1dBridgeMODULE-IDENTITY
dot1dSrOBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
Gauge
OIDs

RFC description

Monitors source route bridging ports, tracking hop counts, frame statistics, and bridging parameters for SR and SRT bridges.

Start monitoring vendor-neutral, standards-based MIB, Token Ring source-routing bridge/switch (source-route port/topology configuration) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download SOURCE-ROUTING-MIB