1 SOURCE-ROUTING-MIB DEFINITIONS ::= BEGIN
13 -- groups in the SR MIB
15 -- dot1dSr is imported from the Bridge MIB
17 dot1dPortPair OBJECT IDENTIFIER ::= { dot1dBridge 10 }
21 -- this group is implemented by those bridges that
22 -- support the source route bridging mode, including Source
23 -- Routing and SRT bridges.
26 dot1dSrPortTable OBJECT-TYPE
27 SYNTAX SEQUENCE OF Dot1dSrPortEntry
31 "A table that contains information about every
32 port that is associated with this source route
36 dot1dSrPortEntry OBJECT-TYPE
37 SYNTAX Dot1dSrPortEntry
41 "A list of information for each port of a source
44 ::= { dot1dSrPortTable 1 }
52 dot1dSrPortLocalSegment
56 dot1dSrPortTargetSegment
58 dot1dSrPortLargestFrame
60 dot1dSrPortSTESpanMode
62 dot1dSrPortSpecInFrames
64 dot1dSrPortSpecOutFrames
66 dot1dSrPortApeInFrames
68 dot1dSrPortApeOutFrames
70 dot1dSrPortSteInFrames
72 dot1dSrPortSteOutFrames
74 dot1dSrPortSegmentMismatchDiscards
76 dot1dSrPortDuplicateSegmentDiscards
78 dot1dSrPortHopCountExceededDiscards
80 dot1dSrPortDupLanIdOrTreeErrors
82 dot1dSrPortLanIdMismatches
86 dot1dSrPort OBJECT-TYPE
87 SYNTAX INTEGER (1..65535)
91 "The port number of the port for which this entry
92 contains Source Route management information."
93 ::= { dot1dSrPortEntry 1 }
95 dot1dSrPortHopCount OBJECT-TYPE
100 "The maximum number of routing descriptors allowed
101 in an All Paths or Spanning Tree Explorer frames."
102 ::= { dot1dSrPortEntry 2 }
104 dot1dSrPortLocalSegment OBJECT-TYPE
109 "The segment number that uniquely identifies the
110 segment to which this port is connected. Current
111 source routing protocols limit this value to the
112 range: 0 through 4095. (The value 0 is used by
113 some management applications for special test
114 cases.) A value of 65535 signifies that no segment
115 number is assigned to this port."
116 ::= { dot1dSrPortEntry 3 }
118 dot1dSrPortBridgeNum OBJECT-TYPE
123 "A bridge number uniquely identifies a bridge when
124 more than one bridge is used to span the same two
125 segments. Current source routing protocols limit
126 this value to the range: 0 through 15. A value of
127 65535 signifies that no bridge number is assigned
129 ::= { dot1dSrPortEntry 4 }
131 dot1dSrPortTargetSegment OBJECT-TYPE
136 "The segment number that corresponds to the target
137 segment this port is considered to be connected to
138 by the bridge. Current source routing protocols
139 limit this value to the range: 0 through 4095.
140 (The value 0 is used by some management
141 applications for special test cases.) A value of
142 65535 signifies that no target segment is assigned
144 ::= { dot1dSrPortEntry 5 }
146 -- It would be nice if we could use ifMtu as the size of the
147 -- largest frame, but we can't because ifMtu is defined to be
148 -- the size that the (inter-)network layer can use which can
149 -- differ from the MAC layer (especially if several layers of
150 -- encapsulation are used).
152 dot1dSrPortLargestFrame OBJECT-TYPE
157 "The maximum size of the INFO field (LLC and
158 above) that this port can send/receive. It does
159 not include any MAC level (framing) octets. The
160 value of this object is used by this bridge to
161 determine whether a modification of the
162 LargestFrame (LF, see [14]) field of the Routing
163 Control field of the Routing Information Field is
166 64 valid values are defined by the IEEE 802.5M SRT
167 Addendum: 516, 635, 754, 873, 993, 1112, 1231,
168 1350, 1470, 1542, 1615, 1688, 1761, 1833, 1906,
169 1979, 2052, 2345, 2638, 2932, 3225, 3518, 3812,
170 4105, 4399, 4865, 5331, 5798, 6264, 6730, 7197,
171 7663, 8130, 8539, 8949, 9358, 9768, 10178, 10587,
172 10997, 11407, 12199, 12992, 13785, 14578, 15370,
173 16163, 16956, 17749, 20730, 23711, 26693, 29674,
174 32655, 35637, 38618, 41600, 44591, 47583, 50575,
175 53567, 56559, 59551, and 65535.
177 An illegal value will not be accepted by the
179 ::= { dot1dSrPortEntry 6 }
181 dot1dSrPortSTESpanMode OBJECT-TYPE
190 "Determines how this port behaves when presented
191 with a Spanning Tree Explorer frame. The value
192 'disabled(2)' indicates that the port will not
193 accept or send Spanning Tree Explorer packets; any
194 STE packets received will be silently discarded.
195 The value 'forced(3)' indicates the port will
196 always accept and propagate Spanning Tree Explorer
197 frames. This allows a manually configured
198 Spanning Tree for this class of packet to be
199 configured. Note that unlike transparent
200 bridging, this is not catastrophic to the network
201 if there are loops. The value 'auto-span(1)' can
202 only be returned by a bridge that both implements
203 the Spanning Tree Protocol and has use of the
204 protocol enabled on this port. The behavior of the
205 port for Spanning Tree Explorer frames is
206 determined by the state of dot1dStpPortState. If
207 the port is in the 'forwarding' state, the frame
208 will be accepted or propagated. Otherwise, it
209 will be silently discarded."
210 ::= { dot1dSrPortEntry 7 }
212 dot1dSrPortSpecInFrames OBJECT-TYPE
217 "The number of Specifically Routed frames, also
218 referred to as Source Routed Frames, that have
219 been received from this port's segment."
220 ::= { dot1dSrPortEntry 8 }
222 dot1dSrPortSpecOutFrames OBJECT-TYPE
227 "The number of Specifically Routed frames, also
228 referred to as Source Routed Frames, that this
229 port has transmitted on its segment."
230 ::= { dot1dSrPortEntry 9 }
232 dot1dSrPortApeInFrames OBJECT-TYPE
237 "The number of All Paths Explorer frames, also
238 referred to as All Routes Explorer frames, that
239 have been received by this port from its segment."
240 ::= { dot1dSrPortEntry 10 }
242 dot1dSrPortApeOutFrames OBJECT-TYPE
247 "The number of all Paths Explorer Frames, also
248 referred to as All Routes Explorer frames, that
249 have been transmitted by this port on its
251 ::= { dot1dSrPortEntry 11 }
253 dot1dSrPortSteInFrames OBJECT-TYPE
258 "The number of spanning tree explorer frames that
259 have been received by this port from its segment."
260 ::= { dot1dSrPortEntry 12 }
262 dot1dSrPortSteOutFrames OBJECT-TYPE
267 "The number of spanning tree explorer frames that
268 have been transmitted by this port on its
270 ::= { dot1dSrPortEntry 13 }
272 dot1dSrPortSegmentMismatchDiscards OBJECT-TYPE
277 "The number of explorer frames that have been
278 discarded by this port because the routing
279 descriptor field contained an invalid adjacent
281 ::= { dot1dSrPortEntry 14 }
283 dot1dSrPortDuplicateSegmentDiscards OBJECT-TYPE
288 "The number of frames that have been discarded by
289 this port because the routing descriptor field
290 contained a duplicate segment identifier."
291 ::= { dot1dSrPortEntry 15 }
293 dot1dSrPortHopCountExceededDiscards OBJECT-TYPE
298 "The number of explorer frames that have been
299 discarded by this port because the Routing
300 Information Field has exceeded the maximum route
302 ::= { dot1dSrPortEntry 16 }
304 dot1dSrPortDupLanIdOrTreeErrors OBJECT-TYPE
309 "The number of duplicate LAN IDs or Tree errors.
310 This helps in detection of problems in networks
311 containing older IBM Source Routing Bridges."
312 ::= { dot1dSrPortEntry 17 }
314 dot1dSrPortLanIdMismatches OBJECT-TYPE
319 "The number of ARE and STE frames that were
320 discarded because the last LAN ID in the routing
321 information field did not equal the LAN-in ID.
322 This error can occur in implementations which do
323 only a LAN-in ID and Bridge Number check instead
324 of a LAN-in ID, Bridge Number, and LAN-out ID
325 check before they forward broadcast frames."
326 ::= { dot1dSrPortEntry 18 }
329 -- scalar object in dot1dSr
331 dot1dSrBridgeLfMode OBJECT-TYPE
339 "Indicates whether the bridge operates using older
340 3 bit length negotiation fields or the newer 6 bit
341 length field in its RIF."
345 -- The Port-Pair Database
347 -- Implementation of this group is optional.
349 -- This group is implemented by those bridges that support
350 -- the direct multiport model of the source route bridging
351 -- mode as defined in the IEEE 802.5 SRT Addendum to
354 -- Bridges implementing this group may report 65535 for
355 -- dot1dSrPortBridgeNumber and dot1dSrPortTargetSegment,
356 -- indicating that those objects are not applicable.
358 dot1dPortPairTableSize OBJECT-TYPE
363 "The total number of entries in the Bridge Port
365 ::= { dot1dPortPair 1 }
368 -- the Bridge Port-Pair table
370 -- this table represents port pairs within a bridge forming
371 -- a unique bridge path, as defined in the IEEE 802.5M SRT
374 dot1dPortPairTable OBJECT-TYPE
375 SYNTAX SEQUENCE OF Dot1dPortPairEntry
376 ACCESS not-accessible
379 "A table that contains information about every
380 port pair database entity associated with this
381 source routing bridge."
382 ::= { dot1dPortPair 2 }
384 dot1dPortPairEntry OBJECT-TYPE
385 SYNTAX Dot1dPortPairEntry
386 ACCESS not-accessible
389 "A list of information for each port pair entity
391 INDEX { dot1dPortPairLowPort, dot1dPortPairHighPort }
392 ::= { dot1dPortPairTable 1 }
394 Dot1dPortPairEntry ::=
398 dot1dPortPairHighPort
400 dot1dPortPairBridgeNum
402 dot1dPortPairBridgeState
406 dot1dPortPairLowPort OBJECT-TYPE
407 SYNTAX INTEGER (1..65535)
411 "The port number of the lower numbered port for
412 which this entry contains port pair database
414 ::= { dot1dPortPairEntry 1 }
416 dot1dPortPairHighPort OBJECT-TYPE
417 SYNTAX INTEGER (1..65535)
421 "The port number of the higher numbered port for
422 which this entry contains port pair database
424 ::= { dot1dPortPairEntry 2 }
426 dot1dPortPairBridgeNum OBJECT-TYPE
431 "A bridge number that uniquely identifies the path
432 provided by this source routing bridge between the
433 segments connected to dot1dPortPairLowPort and
434 dot1dPortPairHighPort. The purpose of bridge
435 number is to disambiguate between multiple paths
436 connecting the same two LANs."
437 ::= { dot1dPortPairEntry 3 }
439 dot1dPortPairBridgeState OBJECT-TYPE
448 "The state of dot1dPortPairBridgeNum. Writing
449 'invalid(3)' to this object removes the
450 corresponding entry."
451 ::= { dot1dPortPairEntry 4 }