RFC 1525 (rfc1525) - Page 3 of 18
Definitions of Managed Objects for Source Routing Bridges
Alternative Format: Original Text Document
RFC 1525 Source Routing Bridge MIB September 1993
layer. There are two major modes defined for this bridging;
transparent and source route. The transparent method of bridging is
defined in the IEEE 802.1d MAC Bridge specification [11]. Source
route bridging has been defined by I.B.M. and is described in the
Token Ring Architecture Reference [12], as well as the IEEE 802.5M
SRT Bridge Operations Addendum [14] to 802.1d. This memo defines
objects needed for management of a source routing bridge, and is an
extension to the SNMP Bridge MIB [6].
An explicit attempt was made to keep this MIB as simple as possible.
This was accomplished by applying the following criteria to objects
proposed for inclusion:
(1) Start with a small set of essential objects and add only
as further objects are needed.
(2) Require objects be essential for either fault or
configuration management.
(3) Consider evidence of current use and/or utility.
(4) Limit the total of objects.
(5) Exclude objects which are simply derivable from others in
this or other MIBs.
(6) Avoid causing critical sections to be heavily
instrumented. The guideline that was followed is one
counter per critical section per layer.
3.1. Structure of MIB
Objects in this MIB are arranged into groups. Each group is
organized as a set of related objects. The overall structure and
assignment of objects to their groups is shown below. Where
appropriate, the corresponding management object name found in IEEE
802.1d [11] and IEEE 802.5M [14] is also included.
SR Bridge MIB Name IEEE Name
dot1dSr
PortTable
Port
HopCount SourceRoutingPort
.PortHopCount
LocalSegment .SegmentNumber
BridgeNum .BridgeNumber
TargetSegment
Decker, McCloghrie, Langille & Rijsinghani