f06eedb1970cd8e5f9d48d37acedfe8c2d678060
[openwrt/svn-archive/archive.git] / libs / net-snmp / patches / 130-debian-extramibs.patch
1 diff -ruN net-snmp-5.4.1.orig/mibs/BGP4-MIB.txt net-snmp-5.4.1/mibs/BGP4-MIB.txt
2 --- net-snmp-5.4.1.orig/mibs/BGP4-MIB.txt 1970-01-01 01:00:00.000000000 +0100
3 +++ net-snmp-5.4.1/mibs/BGP4-MIB.txt 2007-09-20 16:30:52.000000000 +0200
4 @@ -0,0 +1,929 @@
5 + BGP4-MIB DEFINITIONS ::= BEGIN
6 +
7 + IMPORTS
8 + MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
9 + IpAddress, Integer32, Counter32, Gauge32, mib-2
10 + FROM SNMPv2-SMI
11 + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
12 + FROM SNMPv2-CONF;
13 +
14 + bgp MODULE-IDENTITY
15 + LAST-UPDATED "9902100000Z"
16 + ORGANIZATION "IETF IDR Working Group"
17 + CONTACT-INFO "E-mail: idr@merit.net
18 +
19 + Susan Hares (Editor)
20 + Merit Network
21 + 4251 Plymouth Road
22 + Suite C
23 + Ann Arbor, MI 48105-2785
24 + Tel: +1 734 936 2095
25 + Fax: +1 734 647 3185
26 + E-mail: skh@merit.edu
27 +
28 + Jeff Johnson (Editor)
29 + RedBack Networks, Inc.
30 + 1389 Moffett Park Drive
31 + Sunnyvale, CA 94089-1134
32 + Tel: +1 408 548 3516
33 + Fax: +1 408 548 3599
34 + E-mail: jeff@redback.com"
35 + DESCRIPTION
36 + "The MIB module for BGP-4."
37 + REVISION "9902100000Z"
38 + DESCRIPTION
39 + "Corrected duplicate OBJECT IDENTIFIER
40 + assignment in the conformance information."
41 + REVISION "9601080000Z"
42 + DESCRIPTION
43 + "1) Fixed the definitions of the traps to
44 + make them equivalent to their initial
45 + definition in RFC 1269.
46 + 2) Added compliance and conformance info."
47 + ::= { mib-2 15 }
48 +
49 + bgpVersion OBJECT-TYPE
50 + SYNTAX OCTET STRING (SIZE (1..255))
51 + MAX-ACCESS read-only
52 + STATUS current
53 + DESCRIPTION
54 + "Vector of supported BGP protocol version
55 + numbers. Each peer negotiates the version
56 + from this vector. Versions are identified
57 + via the string of bits contained within this
58 + object. The first octet contains bits 0 to
59 + 7, the second octet contains bits 8 to 15,
60 + and so on, with the most significant bit
61 + referring to the lowest bit number in the
62 + octet (e.g., the MSB of the first octet
63 + refers to bit 0). If a bit, i, is present
64 + and set, then the version (i+1) of the BGP
65 + is supported."
66 + ::= { bgp 1 }
67 +
68 + bgpLocalAs OBJECT-TYPE
69 + SYNTAX INTEGER (0..65535)
70 + MAX-ACCESS read-only
71 + STATUS current
72 + DESCRIPTION
73 + "The local autonomous system number."
74 + ::= { bgp 2 }
75 +
76 +
77 +
78 + -- BGP Peer table. This table contains, one entry per BGP
79 + -- peer, information about the BGP peer.
80 +
81 + bgpPeerTable OBJECT-TYPE
82 + SYNTAX SEQUENCE OF BgpPeerEntry
83 + MAX-ACCESS not-accessible
84 + STATUS current
85 + DESCRIPTION
86 + "BGP peer table. This table contains,
87 + one entry per BGP peer, information about the
88 + connections with BGP peers."
89 + ::= { bgp 3 }
90 +
91 + bgpPeerEntry OBJECT-TYPE
92 + SYNTAX BgpPeerEntry
93 + MAX-ACCESS not-accessible
94 + STATUS current
95 + DESCRIPTION
96 + "Entry containing information about the
97 + connection with a BGP peer."
98 + INDEX { bgpPeerRemoteAddr }
99 + ::= { bgpPeerTable 1 }
100 +
101 + BgpPeerEntry ::= SEQUENCE {
102 + bgpPeerIdentifier
103 + IpAddress,
104 + bgpPeerState
105 + INTEGER,
106 + bgpPeerAdminStatus
107 + INTEGER,
108 + bgpPeerNegotiatedVersion
109 + Integer32,
110 + bgpPeerLocalAddr
111 + IpAddress,
112 + bgpPeerLocalPort
113 + INTEGER,
114 + bgpPeerRemoteAddr
115 + IpAddress,
116 + bgpPeerRemotePort
117 + INTEGER,
118 + bgpPeerRemoteAs
119 + INTEGER,
120 + bgpPeerInUpdates
121 + Counter32,
122 + bgpPeerOutUpdates
123 + Counter32,
124 + bgpPeerInTotalMessages
125 + Counter32,
126 + bgpPeerOutTotalMessages
127 + Counter32,
128 + bgpPeerLastError
129 + OCTET STRING,
130 + bgpPeerFsmEstablishedTransitions
131 + Counter32,
132 + bgpPeerFsmEstablishedTime
133 + Gauge32,
134 + bgpPeerConnectRetryInterval
135 + INTEGER,
136 + bgpPeerHoldTime
137 + INTEGER,
138 + bgpPeerKeepAlive
139 + INTEGER,
140 + bgpPeerHoldTimeConfigured
141 + INTEGER,
142 + bgpPeerKeepAliveConfigured
143 + INTEGER,
144 + bgpPeerMinASOriginationInterval
145 + INTEGER,
146 + bgpPeerMinRouteAdvertisementInterval
147 + INTEGER,
148 + bgpPeerInUpdateElapsedTime
149 + Gauge32
150 + }
151 +
152 + bgpPeerIdentifier OBJECT-TYPE
153 + SYNTAX IpAddress
154 + MAX-ACCESS read-only
155 + STATUS current
156 + DESCRIPTION
157 + "The BGP Identifier of this entry's BGP peer."
158 + ::= { bgpPeerEntry 1 }
159 +
160 + bgpPeerState OBJECT-TYPE
161 + SYNTAX INTEGER {
162 + idle(1),
163 + connect(2),
164 + active(3),
165 + opensent(4),
166 + openconfirm(5),
167 + established(6)
168 + }
169 + MAX-ACCESS read-only
170 + STATUS current
171 + DESCRIPTION
172 + "The BGP peer connection state."
173 + ::= { bgpPeerEntry 2 }
174 +
175 + bgpPeerAdminStatus OBJECT-TYPE
176 + SYNTAX INTEGER {
177 + stop(1),
178 + start(2)
179 + }
180 + MAX-ACCESS read-write
181 + STATUS current
182 + DESCRIPTION
183 + "The desired state of the BGP connection. A
184 + transition from 'stop' to 'start' will cause
185 + the BGP Start Event to be generated. A
186 + transition from 'start' to 'stop' will cause
187 + the BGP Stop Event to be generated. This
188 + parameter can be used to restart BGP peer
189 + connections. Care should be used in providing
190 + write access to this object without adequate
191 + authentication."
192 + ::= { bgpPeerEntry 3 }
193 +
194 + bgpPeerNegotiatedVersion OBJECT-TYPE
195 + SYNTAX Integer32
196 + MAX-ACCESS read-only
197 + STATUS current
198 + DESCRIPTION
199 + "The negotiated version of BGP running between
200 + the two peers."
201 + ::= { bgpPeerEntry 4 }
202 +
203 + bgpPeerLocalAddr OBJECT-TYPE
204 + SYNTAX IpAddress
205 + MAX-ACCESS read-only
206 + STATUS current
207 + DESCRIPTION
208 + "The local IP address of this entry's BGP
209 + connection."
210 + ::= { bgpPeerEntry 5 }
211 +
212 + bgpPeerLocalPort OBJECT-TYPE
213 + SYNTAX INTEGER (0..65535)
214 + MAX-ACCESS read-only
215 + STATUS current
216 + DESCRIPTION
217 + "The local port for the TCP connection between
218 + the BGP peers."
219 + ::= { bgpPeerEntry 6 }
220 +
221 + bgpPeerRemoteAddr OBJECT-TYPE
222 + SYNTAX IpAddress
223 + MAX-ACCESS read-only
224 + STATUS current
225 + DESCRIPTION
226 + "The remote IP address of this entry's BGP
227 + peer."
228 + ::= { bgpPeerEntry 7 }
229 +
230 + bgpPeerRemotePort OBJECT-TYPE
231 + SYNTAX INTEGER (0..65535)
232 + MAX-ACCESS read-only
233 + STATUS current
234 + DESCRIPTION
235 + "The remote port for the TCP connection between
236 + the BGP peers. Note that the objects
237 + bgpPeerLocalAddr, bgpPeerLocalPort,
238 + bgpPeerRemoteAddr and bgpPeerRemotePort
239 + provide the appropriate reference to the
240 + standard MIB TCP connection table."
241 + ::= { bgpPeerEntry 8 }
242 +
243 + bgpPeerRemoteAs OBJECT-TYPE
244 + SYNTAX INTEGER (0..65535)
245 + MAX-ACCESS read-only
246 + STATUS current
247 + DESCRIPTION
248 + "The remote autonomous system number."
249 + ::= { bgpPeerEntry 9 }
250 +
251 + bgpPeerInUpdates OBJECT-TYPE
252 + SYNTAX Counter32
253 + MAX-ACCESS read-only
254 + STATUS current
255 + DESCRIPTION
256 + "The number of BGP UPDATE messages received on
257 + this connection. This object should be
258 + initialized to zero (0) when the connection is
259 + established."
260 + ::= { bgpPeerEntry 10 }
261 +
262 + bgpPeerOutUpdates OBJECT-TYPE
263 + SYNTAX Counter32
264 + MAX-ACCESS read-only
265 + STATUS current
266 + DESCRIPTION
267 + "The number of BGP UPDATE messages transmitted
268 + on this connection. This object should be
269 + initialized to zero (0) when the connection is
270 + established."
271 + ::= { bgpPeerEntry 11 }
272 +
273 + bgpPeerInTotalMessages OBJECT-TYPE
274 + SYNTAX Counter32
275 + MAX-ACCESS read-only
276 + STATUS current
277 + DESCRIPTION
278 + "The total number of messages received from the
279 + remote peer on this connection. This object
280 + should be initialized to zero when the
281 + connection is established."
282 + ::= { bgpPeerEntry 12 }
283 +
284 + bgpPeerOutTotalMessages OBJECT-TYPE
285 + SYNTAX Counter32
286 + MAX-ACCESS read-only
287 + STATUS current
288 + DESCRIPTION
289 + "The total number of messages transmitted to
290 + the remote peer on this connection. This object
291 + should be initialized to zero when the
292 + connection is established."
293 + ::= { bgpPeerEntry 13 }
294 +
295 + bgpPeerLastError OBJECT-TYPE
296 + SYNTAX OCTET STRING (SIZE (2))
297 + MAX-ACCESS read-only
298 + STATUS current
299 + DESCRIPTION
300 + "The last error code and subcode seen by this
301 + peer on this connection. If no error has
302 + occurred, this field is zero. Otherwise, the
303 + first byte of this two byte OCTET STRING
304 + contains the error code, and the second byte
305 + contains the subcode."
306 + ::= { bgpPeerEntry 14 }
307 +
308 + bgpPeerFsmEstablishedTransitions OBJECT-TYPE
309 + SYNTAX Counter32
310 + MAX-ACCESS read-only
311 + STATUS current
312 + DESCRIPTION
313 + "The total number of times the BGP FSM
314 + transitioned into the established state."
315 + ::= { bgpPeerEntry 15 }
316 +
317 + bgpPeerFsmEstablishedTime OBJECT-TYPE
318 + SYNTAX Gauge32
319 + MAX-ACCESS read-only
320 + STATUS current
321 + DESCRIPTION
322 + "This timer indicates how long (in seconds) this
323 + peer has been in the Established state or how long
324 + since this peer was last in the Established state.
325 + It is set to zero when a new peer is configured or
326 + the router is booted."
327 + ::= { bgpPeerEntry 16 }
328 +
329 + bgpPeerConnectRetryInterval OBJECT-TYPE
330 + SYNTAX INTEGER (1..65535)
331 + MAX-ACCESS read-write
332 + STATUS current
333 + DESCRIPTION
334 + "Time interval in seconds for the ConnectRetry
335 + timer. The suggested value for this timer is
336 + 120 seconds."
337 + ::= { bgpPeerEntry 17 }
338 +
339 + bgpPeerHoldTime OBJECT-TYPE
340 + SYNTAX INTEGER ( 0 | 3..65535 )
341 + MAX-ACCESS read-only
342 + STATUS current
343 + DESCRIPTION
344 + "Time interval in seconds for the Hold Timer
345 + established with the peer. The value of this
346 + object is calculated by this BGP speaker by
347 + using the smaller of the value in
348 + bgpPeerHoldTimeConfigured and the Hold Time
349 + received in the OPEN message. This value
350 + must be at lease three seconds if it is not
351 + zero (0) in which case the Hold Timer has
352 + not been established with the peer, or, the
353 + value of bgpPeerHoldTimeConfigured is zero (0)."
354 + ::= { bgpPeerEntry 18 }
355 +
356 + bgpPeerKeepAlive OBJECT-TYPE
357 + SYNTAX INTEGER ( 0 | 1..21845 )
358 + MAX-ACCESS read-only
359 + STATUS current
360 + DESCRIPTION
361 + "Time interval in seconds for the KeepAlive
362 + timer established with the peer. The value of
363 + this object is calculated by this BGP speaker
364 + such that, when compared with bgpPeerHoldTime,
365 + it has the same proportion as what
366 + bgpPeerKeepAliveConfigured has when compared
367 + with bgpPeerHoldTimeConfigured. If the value
368 + of this object is zero (0), it indicates that
369 + the KeepAlive timer has not been established
370 + with the peer, or, the value of
371 + bgpPeerKeepAliveConfigured is zero (0)."
372 + ::= { bgpPeerEntry 19 }
373 +
374 + bgpPeerHoldTimeConfigured OBJECT-TYPE
375 + SYNTAX INTEGER ( 0 | 3..65535 )
376 + MAX-ACCESS read-write
377 + STATUS current
378 + DESCRIPTION
379 + "Time interval in seconds for the Hold Time
380 + configured for this BGP speaker with this peer.
381 + This value is placed in an OPEN message sent to
382 + this peer by this BGP speaker, and is compared
383 + with the Hold Time field in an OPEN message
384 + received from the peer when determining the Hold
385 + Time (bgpPeerHoldTime) with the peer. This value
386 + must not be less than three seconds if it is not
387 + zero (0) in which case the Hold Time is NOT to be
388 + established with the peer. The suggested value for
389 + this timer is 90 seconds."
390 + ::= { bgpPeerEntry 20 }
391 +
392 + bgpPeerKeepAliveConfigured OBJECT-TYPE
393 + SYNTAX INTEGER ( 0 | 1..21845 )
394 + MAX-ACCESS read-write
395 + STATUS current
396 + DESCRIPTION
397 + "Time interval in seconds for the KeepAlive timer
398 + configured for this BGP speaker with this peer.
399 + The value of this object will only determine the
400 + KEEPALIVE messages' frequency relative to the value
401 + specified in bgpPeerHoldTimeConfigured; the actual
402 + time interval for the KEEPALIVE messages is
403 + indicated by bgpPeerKeepAlive. A reasonable
404 + maximum value for this timer would be configured to
405 + be one third of that of bgpPeerHoldTimeConfigured.
406 + If the value of this object is zero (0), no
407 + periodical KEEPALIVE messages are sent to the peer
408 + after the BGP connection has been established. The
409 + suggested value for this timer is 30 seconds."
410 + ::= { bgpPeerEntry 21 }
411 +
412 + bgpPeerMinASOriginationInterval OBJECT-TYPE
413 + SYNTAX INTEGER (1..65535)
414 + MAX-ACCESS read-write
415 + STATUS current
416 + DESCRIPTION
417 + "Time interval in seconds for the
418 + MinASOriginationInterval timer.
419 + The suggested value for this timer is 15 seconds."
420 + ::= { bgpPeerEntry 22 }
421 +
422 + bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE
423 + SYNTAX INTEGER (1..65535)
424 + MAX-ACCESS read-write
425 + STATUS current
426 + DESCRIPTION
427 + "Time interval in seconds for the
428 + MinRouteAdvertisementInterval timer.
429 + The suggested value for this timer is 30 seconds."
430 + ::= { bgpPeerEntry 23 }
431 +
432 + bgpPeerInUpdateElapsedTime OBJECT-TYPE
433 + SYNTAX Gauge32
434 + MAX-ACCESS read-only
435 + STATUS current
436 + DESCRIPTION
437 + "Elapsed time in seconds since the last BGP
438 + UPDATE message was received from the peer.
439 + Each time bgpPeerInUpdates is incremented,
440 + the value of this object is set to zero (0)."
441 + ::= { bgpPeerEntry 24 }
442 +
443 +
444 +
445 + bgpIdentifier OBJECT-TYPE
446 + SYNTAX IpAddress
447 + MAX-ACCESS read-only
448 + STATUS current
449 + DESCRIPTION
450 + "The BGP Identifier of local system."
451 + ::= { bgp 4 }
452 +
453 +
454 +
455 + -- Received Path Attribute Table. This table contains,
456 + -- one entry per path to a network, path attributes
457 + -- received from all peers running BGP version 3 or less.
458 + -- This table is obsolete, having been replaced in
459 + -- functionality with the bgp4PathAttrTable.
460 +
461 + bgpRcvdPathAttrTable OBJECT-TYPE
462 + SYNTAX SEQUENCE OF BgpPathAttrEntry
463 + MAX-ACCESS not-accessible
464 + STATUS obsolete
465 + DESCRIPTION
466 + "The BGP Received Path Attribute Table contains
467 + information about paths to destination networks
468 + received from all peers running BGP version 3 or
469 + less."
470 + ::= { bgp 5 }
471 +
472 + bgpPathAttrEntry OBJECT-TYPE
473 + SYNTAX BgpPathAttrEntry
474 + MAX-ACCESS not-accessible
475 + STATUS obsolete
476 + DESCRIPTION
477 + "Information about a path to a network."
478 + INDEX { bgpPathAttrDestNetwork,
479 + bgpPathAttrPeer }
480 + ::= { bgpRcvdPathAttrTable 1 }
481 +
482 + BgpPathAttrEntry ::= SEQUENCE {
483 + bgpPathAttrPeer
484 + IpAddress,
485 + bgpPathAttrDestNetwork
486 + IpAddress,
487 + bgpPathAttrOrigin
488 + INTEGER,
489 + bgpPathAttrASPath
490 + OCTET STRING,
491 + bgpPathAttrNextHop
492 + IpAddress,
493 + bgpPathAttrInterASMetric
494 + Integer32
495 + }
496 +
497 + bgpPathAttrPeer OBJECT-TYPE
498 + SYNTAX IpAddress
499 + MAX-ACCESS read-only
500 + STATUS obsolete
501 + DESCRIPTION
502 + "The IP address of the peer where the path
503 + information was learned."
504 + ::= { bgpPathAttrEntry 1 }
505 +
506 + bgpPathAttrDestNetwork OBJECT-TYPE
507 + SYNTAX IpAddress
508 + MAX-ACCESS read-only
509 + STATUS obsolete
510 + DESCRIPTION
511 + "The address of the destination network."
512 + ::= { bgpPathAttrEntry 2 }
513 +
514 + bgpPathAttrOrigin OBJECT-TYPE
515 + SYNTAX INTEGER {
516 + igp(1),-- networks are interior
517 + egp(2),-- networks learned via EGP
518 + incomplete(3) -- undetermined
519 + }
520 + MAX-ACCESS read-only
521 + STATUS obsolete
522 + DESCRIPTION
523 + "The ultimate origin of the path information."
524 + ::= { bgpPathAttrEntry 3 }
525 +
526 + bgpPathAttrASPath OBJECT-TYPE
527 + SYNTAX OCTET STRING (SIZE (2..255))
528 + MAX-ACCESS read-only
529 + STATUS obsolete
530 + DESCRIPTION
531 + "The set of ASs that must be traversed to reach
532 + the network. This object is probably best
533 + represented as SEQUENCE OF INTEGER. For SMI
534 + compatibility, though, it is represented as
535 + OCTET STRING. Each AS is represented as a pair
536 + of octets according to the following algorithm:
537 +
538 + first-byte-of-pair = ASNumber / 256;
539 + second-byte-of-pair = ASNumber & 255;"
540 + ::= { bgpPathAttrEntry 4 }
541 +
542 + bgpPathAttrNextHop OBJECT-TYPE
543 + SYNTAX IpAddress
544 + MAX-ACCESS read-only
545 + STATUS obsolete
546 + DESCRIPTION
547 + "The address of the border router that should
548 + be used for the destination network."
549 + ::= { bgpPathAttrEntry 5 }
550 +
551 + bgpPathAttrInterASMetric OBJECT-TYPE
552 + SYNTAX Integer32
553 + MAX-ACCESS read-only
554 + STATUS obsolete
555 + DESCRIPTION
556 + "The optional inter-AS metric. If this
557 + attribute has not been provided for this route,
558 + the value for this object is 0."
559 + ::= { bgpPathAttrEntry 6 }
560 +
561 +
562 +
563 + -- BGP-4 Received Path Attribute Table. This table contains,
564 + -- one entry per path to a network, path attributes
565 + -- received from all peers running BGP-4.
566 +
567 + bgp4PathAttrTable OBJECT-TYPE
568 + SYNTAX SEQUENCE OF Bgp4PathAttrEntry
569 + MAX-ACCESS not-accessible
570 + STATUS current
571 + DESCRIPTION
572 + "The BGP-4 Received Path Attribute Table contains
573 + information about paths to destination networks
574 + received from all BGP4 peers."
575 + ::= { bgp 6 }
576 +
577 + bgp4PathAttrEntry OBJECT-TYPE
578 + SYNTAX Bgp4PathAttrEntry
579 + MAX-ACCESS not-accessible
580 + STATUS current
581 + DESCRIPTION
582 + "Information about a path to a network."
583 + INDEX { bgp4PathAttrIpAddrPrefix,
584 + bgp4PathAttrIpAddrPrefixLen,
585 + bgp4PathAttrPeer }
586 + ::= { bgp4PathAttrTable 1 }
587 +
588 + Bgp4PathAttrEntry ::= SEQUENCE {
589 + bgp4PathAttrPeer
590 + IpAddress,
591 + bgp4PathAttrIpAddrPrefixLen
592 + INTEGER,
593 + bgp4PathAttrIpAddrPrefix
594 + IpAddress,
595 + bgp4PathAttrOrigin
596 + INTEGER,
597 + bgp4PathAttrASPathSegment
598 + OCTET STRING,
599 + bgp4PathAttrNextHop
600 + IpAddress,
601 + bgp4PathAttrMultiExitDisc
602 + INTEGER,
603 + bgp4PathAttrLocalPref
604 + INTEGER,
605 + bgp4PathAttrAtomicAggregate
606 + INTEGER,
607 + bgp4PathAttrAggregatorAS
608 + INTEGER,
609 + bgp4PathAttrAggregatorAddr
610 + IpAddress,
611 + bgp4PathAttrCalcLocalPref
612 + INTEGER,
613 + bgp4PathAttrBest
614 + INTEGER,
615 + bgp4PathAttrUnknown
616 + OCTET STRING
617 + }
618 +
619 + bgp4PathAttrPeer OBJECT-TYPE
620 + SYNTAX IpAddress
621 + MAX-ACCESS read-only
622 + STATUS current
623 + DESCRIPTION
624 + "The IP address of the peer where the path
625 + information was learned."
626 + ::= { bgp4PathAttrEntry 1 }
627 + bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE
628 + SYNTAX INTEGER (0..32)
629 + MAX-ACCESS read-only
630 + STATUS current
631 + DESCRIPTION
632 + "Length in bits of the IP address prefix in the
633 + Network Layer Reachability Information field."
634 + ::= { bgp4PathAttrEntry 2 }
635 +
636 + bgp4PathAttrIpAddrPrefix OBJECT-TYPE
637 + SYNTAX IpAddress
638 + MAX-ACCESS read-only
639 + STATUS current
640 + DESCRIPTION
641 + "An IP address prefix in the Network Layer
642 + Reachability Information field. This object
643 + is an IP address containing the prefix with
644 + length specified by bgp4PathAttrIpAddrPrefixLen.
645 + Any bits beyond the length specified by
646 + bgp4PathAttrIpAddrPrefixLen are zeroed."
647 + ::= { bgp4PathAttrEntry 3 }
648 +
649 + bgp4PathAttrOrigin OBJECT-TYPE
650 + SYNTAX INTEGER {
651 + igp(1),-- networks are interior
652 + egp(2),-- networks learned via EGP
653 + incomplete(3) -- undetermined
654 + }
655 + MAX-ACCESS read-only
656 + STATUS current
657 + DESCRIPTION
658 + "The ultimate origin of the path information."
659 + ::= { bgp4PathAttrEntry 4 }
660 +
661 + bgp4PathAttrASPathSegment OBJECT-TYPE
662 + SYNTAX OCTET STRING (SIZE (2..255))
663 + MAX-ACCESS read-only
664 + STATUS current
665 + DESCRIPTION
666 + "The sequence of AS path segments. Each AS
667 + path segment is represented by a triple
668 + <type, length, value>.
669 +
670 + The type is a 1-octet field which has two
671 + possible values:
672 + 1 AS_SET: unordered set of ASs a
673 + route in the UPDATE message
674 + has traversed
675 + 2 AS_SEQUENCE: ordered set of ASs
676 + a route in the UPDATE message
677 + has traversed.
678 +
679 + The length is a 1-octet field containing the
680 + number of ASs in the value field.
681 +
682 + The value field contains one or more AS
683 + numbers, each AS is represented in the octet
684 + string as a pair of octets according to the
685 + following algorithm:
686 +
687 + first-byte-of-pair = ASNumber / 256;
688 + second-byte-of-pair = ASNumber & 255;"
689 + ::= { bgp4PathAttrEntry 5 }
690 +
691 + bgp4PathAttrNextHop OBJECT-TYPE
692 + SYNTAX IpAddress
693 + MAX-ACCESS read-only
694 + STATUS current
695 + DESCRIPTION
696 + "The address of the border router that should
697 + be used for the destination network."
698 + ::= { bgp4PathAttrEntry 6 }
699 +
700 + bgp4PathAttrMultiExitDisc OBJECT-TYPE
701 + SYNTAX INTEGER (-1..2147483647)
702 + MAX-ACCESS read-only
703 + STATUS current
704 + DESCRIPTION
705 + "This metric is used to discriminate between
706 + multiple exit points to an adjacent autonomous
707 + system. A value of -1 indicates the absence of
708 + this attribute."
709 + ::= { bgp4PathAttrEntry 7 }
710 +
711 + bgp4PathAttrLocalPref OBJECT-TYPE
712 + SYNTAX INTEGER (-1..2147483647)
713 + MAX-ACCESS read-only
714 + STATUS current
715 + DESCRIPTION
716 + "The originating BGP4 speaker's degree of
717 + preference for an advertised route. A value of
718 + -1 indicates the absence of this attribute."
719 + ::= { bgp4PathAttrEntry 8 }
720 +
721 + bgp4PathAttrAtomicAggregate OBJECT-TYPE
722 + SYNTAX INTEGER {
723 + lessSpecificRrouteNotSelected(1),
724 + lessSpecificRouteSelected(2)
725 + }
726 + MAX-ACCESS read-only
727 + STATUS current
728 + DESCRIPTION
729 + "Whether or not a system has selected
730 + a less specific route without selecting a
731 + more specific route."
732 + ::= { bgp4PathAttrEntry 9 }
733 +
734 + bgp4PathAttrAggregatorAS OBJECT-TYPE
735 + SYNTAX INTEGER (0..65535)
736 + MAX-ACCESS read-only
737 + STATUS current
738 + DESCRIPTION
739 + "The AS number of the last BGP4 speaker that
740 + performed route aggregation. A value of zero (0)
741 + indicates the absence of this attribute."
742 + ::= { bgp4PathAttrEntry 10 }
743 +
744 + bgp4PathAttrAggregatorAddr OBJECT-TYPE
745 + SYNTAX IpAddress
746 + MAX-ACCESS read-only
747 + STATUS current
748 + DESCRIPTION
749 + "The IP address of the last BGP4 speaker that
750 + performed route aggregation. A value of
751 + 0.0.0.0 indicates the absence of this attribute."
752 + ::= { bgp4PathAttrEntry 11 }
753 +
754 + bgp4PathAttrCalcLocalPref OBJECT-TYPE
755 + SYNTAX INTEGER (-1..2147483647)
756 + MAX-ACCESS read-only
757 + STATUS current
758 + DESCRIPTION
759 + "The degree of preference calculated by the
760 + receiving BGP4 speaker for an advertised route.
761 + A value of -1 indicates the absence of this
762 + attribute."
763 + ::= { bgp4PathAttrEntry 12 }
764 +
765 + bgp4PathAttrBest OBJECT-TYPE
766 + SYNTAX INTEGER {
767 + false(1),-- not chosen as best route
768 + true(2) -- chosen as best route
769 + }
770 + MAX-ACCESS read-only
771 + STATUS current
772 + DESCRIPTION
773 + "An indication of whether or not this route
774 + was chosen as the best BGP4 route."
775 + ::= { bgp4PathAttrEntry 13 }
776 +
777 + bgp4PathAttrUnknown OBJECT-TYPE
778 + SYNTAX OCTET STRING (SIZE(0..255))
779 + MAX-ACCESS read-only
780 + STATUS current
781 + DESCRIPTION
782 + "One or more path attributes not understood
783 + by this BGP4 speaker. Size zero (0) indicates
784 + the absence of such attribute(s). Octets
785 + beyond the maximum size, if any, are not
786 + recorded by this object."
787 + ::= { bgp4PathAttrEntry 14 }
788 +
789 +
790 + -- Traps.
791 +
792 + -- note that in RFC 1657, bgpTraps was incorrectly
793 + -- assigned a value of { bgp 7 }, and each of the
794 + -- traps had the bgpPeerRemoteAddr object inappropriately
795 + -- removed from their OBJECTS clause. The following
796 + -- definitions restore the semantics of the traps as
797 + -- they were initially defined in RFC 1269.
798 +
799 + -- { bgp 7 } is unused
800 +
801 + bgpTraps OBJECT IDENTIFIER ::= { bgp 0 }
802 +
803 + bgpEstablished NOTIFICATION-TYPE
804 + OBJECTS { bgpPeerRemoteAddr,
805 + bgpPeerLastError,
806 + bgpPeerState }
807 + STATUS current
808 + DESCRIPTION
809 + "The BGP Established event is generated when
810 + the BGP FSM enters the ESTABLISHED state."
811 + ::= { bgpTraps 1 }
812 +
813 + bgpBackwardTransition NOTIFICATION-TYPE
814 + OBJECTS { bgpPeerRemoteAddr,
815 + bgpPeerLastError,
816 + bgpPeerState }
817 + STATUS current
818 + DESCRIPTION
819 + "The BGPBackwardTransition Event is generated
820 + when the BGP FSM moves from a higher numbered
821 + state to a lower numbered state."
822 + ::= { bgpTraps 2 }
823 +
824 + -- conformance information
825 +
826 + bgpMIBConformance OBJECT IDENTIFIER ::= { bgp 8 }
827 + bgpMIBCompliances OBJECT IDENTIFIER ::= { bgpMIBConformance 1 }
828 + bgpMIBGroups OBJECT IDENTIFIER ::= { bgpMIBConformance 2 }
829 +
830 + -- compliance statements
831 +
832 + bgpMIBCompliance MODULE-COMPLIANCE
833 + STATUS current
834 + DESCRIPTION
835 + "The compliance statement for entities which
836 + implement the BGP4 mib."
837 + MODULE -- this module
838 + MANDATORY-GROUPS { bgp4MIBGlobalsGroup,
839 + bgp4MIBPeerGroup,
840 + bgp4MIBPathAttrGroup,
841 + bgp4MIBNotificationGroup }
842 + ::= { bgpMIBCompliances 1 }
843 +
844 + -- units of conformance
845 +
846 + bgp4MIBGlobalsGroup OBJECT-GROUP
847 + OBJECTS { bgpVersion,
848 + bgpLocalAs,
849 + bgpIdentifier }
850 + STATUS current
851 + DESCRIPTION
852 + "A collection of objects providing information
853 + on global BGP state."
854 + ::= { bgpMIBGroups 1 }
855 +
856 + bgp4MIBPeerGroup OBJECT-GROUP
857 + OBJECTS { bgpPeerIdentifier,
858 + bgpPeerState,
859 + bgpPeerAdminStatus,
860 + bgpPeerNegotiatedVersion,
861 + bgpPeerLocalAddr,
862 + bgpPeerLocalPort,
863 + bgpPeerRemoteAddr,
864 + bgpPeerRemotePort,
865 + bgpPeerRemoteAs,
866 + bgpPeerInUpdates,
867 + bgpPeerOutUpdates,
868 + bgpPeerInTotalMessages,
869 + bgpPeerOutTotalMessages,
870 + bgpPeerLastError,
871 + bgpPeerFsmEstablishedTransitions,
872 + bgpPeerFsmEstablishedTime,
873 + bgpPeerConnectRetryInterval,
874 + bgpPeerHoldTime,
875 + bgpPeerKeepAlive,
876 + bgpPeerHoldTimeConfigured,
877 + bgpPeerKeepAliveConfigured,
878 + bgpPeerMinASOriginationInterval,
879 + bgpPeerMinRouteAdvertisementInterval,
880 + bgpPeerInUpdateElapsedTime }
881 + STATUS current
882 + DESCRIPTION
883 + "A collection of objects for managing
884 + BGP peers."
885 + ::= { bgpMIBGroups 2 }
886 +
887 + bgp4MIBRcvdPathAttrGroup OBJECT-GROUP
888 + OBJECTS { bgpPathAttrPeer,
889 + bgpPathAttrDestNetwork,
890 + bgpPathAttrOrigin,
891 + bgpPathAttrASPath,
892 + bgpPathAttrNextHop,
893 + bgpPathAttrInterASMetric }
894 + STATUS obsolete
895 + DESCRIPTION
896 + "A collection of objects for managing BGP
897 + path entries.
898 +
899 + This conformance group is obsolete,
900 + replaced by bgp4MIBPathAttrGroup."
901 + ::= { bgpMIBGroups 3 }
902 +
903 + bgp4MIBPathAttrGroup OBJECT-GROUP
904 + OBJECTS { bgp4PathAttrPeer,
905 + bgp4PathAttrIpAddrPrefixLen,
906 + bgp4PathAttrIpAddrPrefix,
907 + bgp4PathAttrOrigin,
908 + bgp4PathAttrASPathSegment,
909 + bgp4PathAttrNextHop,
910 + bgp4PathAttrMultiExitDisc,
911 + bgp4PathAttrLocalPref,
912 + bgp4PathAttrAtomicAggregate,
913 + bgp4PathAttrAggregatorAS,
914 + bgp4PathAttrAggregatorAddr,
915 + bgp4PathAttrCalcLocalPref,
916 + bgp4PathAttrBest,
917 + bgp4PathAttrUnknown }
918 + STATUS current
919 + DESCRIPTION
920 + "A collection of objects for managing
921 + BGP path entries."
922 + ::= { bgpMIBGroups 4 }
923 +
924 + bgp4MIBNotificationGroup NOTIFICATION-GROUP
925 + NOTIFICATIONS { bgpEstablished,
926 + bgpBackwardTransition }
927 + STATUS current
928 + DESCRIPTION
929 + "A collection of notifications for signaling
930 + changes in BGP peer relationships."
931 + ::= { bgpMIBGroups 5 }
932 +
933 + END
934 diff -ruN net-snmp-5.4.1.orig/mibs/BRIDGE-MIB.txt net-snmp-5.4.1/mibs/BRIDGE-MIB.txt
935 --- net-snmp-5.4.1.orig/mibs/BRIDGE-MIB.txt 1970-01-01 01:00:00.000000000 +0100
936 +++ net-snmp-5.4.1/mibs/BRIDGE-MIB.txt 2007-09-20 16:30:52.000000000 +0200
937 @@ -0,0 +1,1075 @@
938 +BRIDGE-MIB DEFINITIONS ::= BEGIN
939 +
940 +IMPORTS
941 + Counter, TimeTicks
942 + FROM RFC1155-SMI
943 + mib-2
944 + FROM RFC1213-MIB
945 + OBJECT-TYPE
946 + FROM RFC-1212
947 + TRAP-TYPE
948 + FROM RFC-1215;
949 +
950 +-- All representations of MAC addresses in this MIB Module
951 +-- use, as a textual convention (i.e. this convention does
952 +-- not affect their encoding), the data type:
953 +MacAddress ::= OCTET STRING (SIZE (6)) -- a 6 octet address
954 + -- in the
955 + -- "canonical"
956 + -- order
957 +-- defined by IEEE 802.1a, i.e., as if it were transmitted
958 +-- least significant bit first, even though 802.5 (in
959 +-- contrast to other n802.x protocols) requires MAC
960 +-- addresses to be transmitted most significant bit first.
961 +--
962 +-- 16-bit addresses, if needed, are represented by setting
963 +-- their upper 4 octets to all 0's, i.e., AAFF would be
964 +-- represented as 00000000AAFF.
965 +
966 +-- Similarly, all representations of Bridge-Id in this MIB
967 +-- Module use, as a textual convention (i.e. this
968 +-- convention does not affect their encoding), the data
969 +-- type:
970 +BridgeId ::= OCTET STRING (SIZE (8)) -- the
971 + -- Bridge-Identifier
972 + -- as used in the
973 + -- Spanning Tree
974 +-- Protocol to uniquely identify a bridge. Its first two
975 +-- octets (in network byte order) contain a priority
976 +-- value and its last 6 octets contain the MAC address
977 +-- used to refer to a bridge in a unique fashion
978 +-- (typically, the numerically smallest MAC address
979 +-- of all ports on the bridge).
980 +
981 +-- Several objects in this MIB module represent values of
982 +-- timers used by the Spanning Tree Protocol. In this
983 +-- MIB, these timers have values in units of hundreths of
984 +-- a second (i.e. 1/100 secs).
985 +-- These timers, when stored in a Spanning Tree Protocol's
986 +-- BPDU, are in units of 1/256 seconds. Note, however,
987 +-- that 802.1D-1990 specifies a settable granularity of
988 +-- no more than 1 second for these timers. To avoid
989 +-- ambiguity, a data type is defined here as a textual
990 +-- convention and all representation of these timers
991 +-- in this MIB module are defined using this data type. An
992 +-- algorithm is also defined for converting between the
993 +-- different units, to ensure a timer's value is not
994 +-- distorted by multiple conversions.
995 +-- The data type is:
996 +
997 +Timeout ::= INTEGER -- a STP timer in units of 1/100 seconds
998 +
999 +-- To convert a Timeout value into a value in units of
1000 +-- 1/256 seconds, the following algorithm should be used:
1001 +--
1002 +-- b = floor( (n * 256) / 100)
1003 +--
1004 +-- where:
1005 +-- floor = quotient [ignore remainder]
1006 +-- n is the value in 1/100 second units
1007 +-- b is the value in 1/256 second units
1008 +--
1009 +-- To convert the value from 1/256 second units back to
1010 +-- 1/100 seconds, the following algorithm should be used:
1011 +--
1012 +-- n = ceiling( (b * 100) / 256)
1013 +--
1014 +-- where:
1015 +-- ceiling = quotient [if remainder is 0], or
1016 +-- quotient + 1 [if remainder is non-zero]
1017 +-- n is the value in 1/100 second units
1018 +-- b is the value in 1/256 second units
1019 +--
1020 +-- Note: it is important that the arithmetic operations are
1021 +-- done in the order specified (i.e., multiply first, divide
1022 +-- second).
1023 +
1024 + dot1dBridge OBJECT IDENTIFIER ::= { mib-2 17 }
1025 +
1026 +-- groups in the Bridge MIB
1027 +
1028 +dot1dBase OBJECT IDENTIFIER ::= { dot1dBridge 1 }
1029 +
1030 +dot1dStp OBJECT IDENTIFIER ::= { dot1dBridge 2 }
1031 +
1032 +dot1dSr OBJECT IDENTIFIER ::= { dot1dBridge 3 }
1033 +-- separately documented
1034 +
1035 +dot1dTp OBJECT IDENTIFIER ::= { dot1dBridge 4 }
1036 +
1037 +dot1dStatic OBJECT IDENTIFIER ::= { dot1dBridge 5 }
1038 +
1039 +-- the dot1dBase group
1040 +
1041 +-- Implementation of the dot1dBase group is mandatory for all
1042 +-- bridges.
1043 +
1044 +dot1dBaseBridgeAddress OBJECT-TYPE
1045 + SYNTAX MacAddress
1046 + ACCESS read-only
1047 + STATUS mandatory
1048 + DESCRIPTION
1049 + "The MAC address used by this bridge when it must
1050 + be referred to in a unique fashion. It is
1051 + recommended that this be the numerically smallest
1052 + MAC address of all ports that belong to this
1053 + bridge. However it is only required to be unique.
1054 + When concatenated with dot1dStpPriority a unique
1055 + BridgeIdentifier is formed which is used in the
1056 + Spanning Tree Protocol."
1057 + REFERENCE
1058 + "IEEE 802.1D-1990: Sections 6.4.1.1.3 and 3.12.5"
1059 + ::= { dot1dBase 1 }
1060 +
1061 +dot1dBaseNumPorts OBJECT-TYPE
1062 + SYNTAX INTEGER
1063 + ACCESS read-only
1064 + STATUS mandatory
1065 + DESCRIPTION
1066 + "The number of ports controlled by this bridging
1067 + entity."
1068 + REFERENCE
1069 + "IEEE 802.1D-1990: Section 6.4.1.1.3"
1070 + ::= { dot1dBase 2 }
1071 +
1072 +dot1dBaseType OBJECT-TYPE
1073 + SYNTAX INTEGER {
1074 + unknown(1),
1075 + transparent-only(2),
1076 + sourceroute-only(3),
1077 + srt(4)
1078 + }
1079 + ACCESS read-only
1080 + STATUS mandatory
1081 + DESCRIPTION
1082 + "Indicates what type of bridging this bridge can
1083 + perform. If a bridge is actually performing a
1084 + certain type of bridging this will be indicated by
1085 + entries in the port table for the given type."
1086 + ::= { dot1dBase 3 }
1087 +
1088 +-- The Generic Bridge Port Table
1089 +
1090 +dot1dBasePortTable OBJECT-TYPE
1091 + SYNTAX SEQUENCE OF Dot1dBasePortEntry
1092 + ACCESS not-accessible
1093 + STATUS mandatory
1094 + DESCRIPTION
1095 + "A table that contains generic information about
1096 + every port that is associated with this bridge.
1097 + Transparent, source-route, and srt ports are
1098 + included."
1099 + ::= { dot1dBase 4 }
1100 +
1101 +dot1dBasePortEntry OBJECT-TYPE
1102 + SYNTAX Dot1dBasePortEntry
1103 + ACCESS not-accessible
1104 + STATUS mandatory
1105 + DESCRIPTION
1106 + "A list of information for each port of the
1107 + bridge."
1108 + REFERENCE
1109 + "IEEE 802.1D-1990: Section 6.4.2, 6.6.1"
1110 + INDEX { dot1dBasePort }
1111 + ::= { dot1dBasePortTable 1 }
1112 +
1113 +Dot1dBasePortEntry ::=
1114 + SEQUENCE {
1115 + dot1dBasePort
1116 + INTEGER,
1117 + dot1dBasePortIfIndex
1118 + INTEGER,
1119 + dot1dBasePortCircuit
1120 +
1121 + OBJECT IDENTIFIER,
1122 + dot1dBasePortDelayExceededDiscards
1123 + Counter,
1124 + dot1dBasePortMtuExceededDiscards
1125 + Counter
1126 + }
1127 +
1128 +dot1dBasePort OBJECT-TYPE
1129 + SYNTAX INTEGER (1..65535)
1130 + ACCESS read-only
1131 + STATUS mandatory
1132 + DESCRIPTION
1133 + "The port number of the port for which this entry
1134 + contains bridge management information."
1135 + ::= { dot1dBasePortEntry 1 }
1136 +
1137 +dot1dBasePortIfIndex OBJECT-TYPE
1138 + SYNTAX INTEGER
1139 + ACCESS read-only
1140 + STATUS mandatory
1141 + DESCRIPTION
1142 + "The value of the instance of the ifIndex object,
1143 + defined in MIB-II, for the interface corresponding
1144 + to this port."
1145 + ::= { dot1dBasePortEntry 2 }
1146 +
1147 +dot1dBasePortCircuit OBJECT-TYPE
1148 + SYNTAX OBJECT IDENTIFIER
1149 + ACCESS read-only
1150 + STATUS mandatory
1151 + DESCRIPTION
1152 + "For a port which (potentially) has the same value
1153 + of dot1dBasePortIfIndex as another port on the
1154 + same bridge, this object contains the name of an
1155 + object instance unique to this port. For example,
1156 + in the case where multiple ports correspond one-
1157 + to-one with multiple X.25 virtual circuits, this
1158 + value might identify an (e.g., the first) object
1159 + instance associated with the X.25 virtual circuit
1160 + corresponding to this port.
1161 +
1162 + For a port which has a unique value of
1163 + dot1dBasePortIfIndex, this object can have the
1164 + value { 0 0 }."
1165 + ::= { dot1dBasePortEntry 3 }
1166 +
1167 +dot1dBasePortDelayExceededDiscards OBJECT-TYPE
1168 + SYNTAX Counter
1169 +
1170 + ACCESS read-only
1171 + STATUS mandatory
1172 + DESCRIPTION
1173 + "The number of frames discarded by this port due
1174 + to excessive transit delay through the bridge. It
1175 + is incremented by both transparent and source
1176 + route bridges."
1177 + REFERENCE
1178 + "IEEE 802.1D-1990: Section 6.6.1.1.3"
1179 + ::= { dot1dBasePortEntry 4 }
1180 +
1181 +dot1dBasePortMtuExceededDiscards OBJECT-TYPE
1182 + SYNTAX Counter
1183 + ACCESS read-only
1184 + STATUS mandatory
1185 + DESCRIPTION
1186 + "The number of frames discarded by this port due
1187 + to an excessive size. It is incremented by both
1188 + transparent and source route bridges."
1189 + REFERENCE
1190 + "IEEE 802.1D-1990: Section 6.6.1.1.3"
1191 + ::= { dot1dBasePortEntry 5 }
1192 +
1193 +-- the dot1dStp group
1194 +
1195 +-- Implementation of the dot1dStp group is optional. It is
1196 +-- implemented by those bridges that support the Spanning Tree
1197 +-- Protocol.
1198 +
1199 +dot1dStpProtocolSpecification OBJECT-TYPE
1200 + SYNTAX INTEGER {
1201 + unknown(1),
1202 + decLb100(2),
1203 + ieee8021d(3)
1204 + }
1205 + ACCESS read-only
1206 + STATUS mandatory
1207 + DESCRIPTION
1208 + "An indication of what version of the Spanning
1209 + Tree Protocol is being run. The value
1210 + 'decLb100(2)' indicates the DEC LANbridge 100
1211 + Spanning Tree protocol. IEEE 802.1d
1212 + implementations will return 'ieee8021d(3)'. If
1213 + future versions of the IEEE Spanning Tree Protocol
1214 + are released that are incompatible with the
1215 + current version a new value will be defined."
1216 +
1217 + ::= { dot1dStp 1 }
1218 +
1219 +dot1dStpPriority OBJECT-TYPE
1220 + SYNTAX INTEGER (0..65535)
1221 + ACCESS read-write
1222 + STATUS mandatory
1223 + DESCRIPTION
1224 + "The value of the write-able portion of the Bridge
1225 + ID, i.e., the first two octets of the (8 octet
1226 + long) Bridge ID. The other (last) 6 octets of the
1227 + Bridge ID are given by the value of
1228 + dot1dBaseBridgeAddress."
1229 + REFERENCE
1230 + "IEEE 802.1D-1990: Section 4.5.3.7"
1231 + ::= { dot1dStp 2 }
1232 +
1233 +dot1dStpTimeSinceTopologyChange OBJECT-TYPE
1234 + SYNTAX TimeTicks
1235 + ACCESS read-only
1236 + STATUS mandatory
1237 + DESCRIPTION
1238 + "The time (in hundredths of a second) since the
1239 + last time a topology change was detected by the
1240 + bridge entity."
1241 + REFERENCE
1242 + "IEEE 802.1D-1990: Section 6.8.1.1.3"
1243 + ::= { dot1dStp 3 }
1244 +
1245 +dot1dStpTopChanges OBJECT-TYPE
1246 + SYNTAX Counter
1247 + ACCESS read-only
1248 + STATUS mandatory
1249 + DESCRIPTION
1250 + "The total number of topology changes detected by
1251 + this bridge since the management entity was last
1252 + reset or initialized."
1253 + REFERENCE
1254 + "IEEE 802.1D-1990: Section 6.8.1.1.3"
1255 + ::= { dot1dStp 4 }
1256 +
1257 +dot1dStpDesignatedRoot OBJECT-TYPE
1258 + SYNTAX BridgeId
1259 + ACCESS read-only
1260 + STATUS mandatory
1261 + DESCRIPTION
1262 + "The bridge identifier of the root of the spanning
1263 + tree as determined by the Spanning Tree Protocol
1264 + as executed by this node. This value is used as
1265 +
1266 + the Root Identifier parameter in all Configuration
1267 + Bridge PDUs originated by this node."
1268 + REFERENCE
1269 + "IEEE 802.1D-1990: Section 4.5.3.1"
1270 + ::= { dot1dStp 5 }
1271 +
1272 +dot1dStpRootCost OBJECT-TYPE
1273 + SYNTAX INTEGER
1274 + ACCESS read-only
1275 + STATUS mandatory
1276 + DESCRIPTION
1277 + "The cost of the path to the root as seen from
1278 + this bridge."
1279 + REFERENCE
1280 + "IEEE 802.1D-1990: Section 4.5.3.2"
1281 + ::= { dot1dStp 6 }
1282 +
1283 +dot1dStpRootPort OBJECT-TYPE
1284 + SYNTAX INTEGER
1285 + ACCESS read-only
1286 + STATUS mandatory
1287 + DESCRIPTION
1288 + "The port number of the port which offers the
1289 + lowest cost path from this bridge to the root
1290 + bridge."
1291 + REFERENCE
1292 + "IEEE 802.1D-1990: Section 4.5.3.3"
1293 + ::= { dot1dStp 7 }
1294 +
1295 +dot1dStpMaxAge OBJECT-TYPE
1296 + SYNTAX Timeout
1297 + ACCESS read-only
1298 + STATUS mandatory
1299 + DESCRIPTION
1300 + "The maximum age of Spanning Tree Protocol
1301 + information learned from the network on any port
1302 + before it is discarded, in units of hundredths of
1303 + a second. This is the actual value that this
1304 + bridge is currently using."
1305 + REFERENCE
1306 + "IEEE 802.1D-1990: Section 4.5.3.4"
1307 + ::= { dot1dStp 8 }
1308 +
1309 +dot1dStpHelloTime OBJECT-TYPE
1310 + SYNTAX Timeout
1311 + ACCESS read-only
1312 + STATUS mandatory
1313 + DESCRIPTION
1314 +
1315 + "The amount of time between the transmission of
1316 + Configuration bridge PDUs by this node on any port
1317 + when it is the root of the spanning tree or trying
1318 + to become so, in units of hundredths of a second.
1319 + This is the actual value that this bridge is
1320 + currently using."
1321 + REFERENCE
1322 + "IEEE 802.1D-1990: Section 4.5.3.5"
1323 + ::= { dot1dStp 9 }
1324 +
1325 +dot1dStpHoldTime OBJECT-TYPE
1326 + SYNTAX INTEGER
1327 + ACCESS read-only
1328 + STATUS mandatory
1329 + DESCRIPTION
1330 + "This time value determines the interval length
1331 + during which no more than two Configuration bridge
1332 + PDUs shall be transmitted by this node, in units
1333 + of hundredths of a second."
1334 + REFERENCE
1335 + "IEEE 802.1D-1990: Section 4.5.3.14"
1336 + ::= { dot1dStp 10 }
1337 +
1338 +dot1dStpForwardDelay OBJECT-TYPE
1339 + SYNTAX Timeout
1340 + ACCESS read-only
1341 + STATUS mandatory
1342 + DESCRIPTION
1343 + "This time value, measured in units of hundredths
1344 + of a second, controls how fast a port changes its
1345 + spanning state when moving towards the Forwarding
1346 + state. The value determines how long the port
1347 + stays in each of the Listening and Learning
1348 + states, which precede the Forwarding state. This
1349 + value is also used, when a topology change has
1350 + been detected and is underway, to age all dynamic
1351 + entries in the Forwarding Database. [Note that
1352 + this value is the one that this bridge is
1353 + currently using, in contrast to
1354 + dot1dStpBridgeForwardDelay which is the value that
1355 + this bridge and all others would start using
1356 + if/when this bridge were to become the root.]"
1357 + REFERENCE
1358 + "IEEE 802.1D-1990: Section 4.5.3.6"
1359 + ::= { dot1dStp 11 }
1360 +
1361 +dot1dStpBridgeMaxAge OBJECT-TYPE
1362 + SYNTAX Timeout (600..4000)
1363 +
1364 + ACCESS read-write
1365 + STATUS mandatory
1366 + DESCRIPTION
1367 + "The value that all bridges use for MaxAge when
1368 + this bridge is acting as the root. Note that
1369 + 802.1D-1990 specifies that the range for this
1370 + parameter is related to the value of
1371 + dot1dStpBridgeHelloTime. The granularity of this
1372 + timer is specified by 802.1D-1990 to be 1 second.
1373 + An agent may return a badValue error if a set is
1374 + attempted to a value which is not a whole number
1375 + of seconds."
1376 + REFERENCE
1377 + "IEEE 802.1D-1990: Section 4.5.3.8"
1378 + ::= { dot1dStp 12 }
1379 +
1380 +dot1dStpBridgeHelloTime OBJECT-TYPE
1381 + SYNTAX Timeout (100..1000)
1382 + ACCESS read-write
1383 + STATUS mandatory
1384 + DESCRIPTION
1385 + "The value that all bridges use for HelloTime when
1386 + this bridge is acting as the root. The
1387 + granularity of this timer is specified by 802.1D-
1388 + 1990 to be 1 second. An agent may return a
1389 + badValue error if a set is attempted to a value
1390 + which is not a whole number of seconds."
1391 + REFERENCE
1392 + "IEEE 802.1D-1990: Section 4.5.3.9"
1393 + ::= { dot1dStp 13 }
1394 +
1395 +dot1dStpBridgeForwardDelay OBJECT-TYPE
1396 + SYNTAX Timeout (400..3000)
1397 + ACCESS read-write
1398 + STATUS mandatory
1399 + DESCRIPTION
1400 + "The value that all bridges use for ForwardDelay
1401 + when this bridge is acting as the root. Note that
1402 + 802.1D-1990 specifies that the range for this
1403 + parameter is related to the value of
1404 + dot1dStpBridgeMaxAge. The granularity of this
1405 + timer is specified by 802.1D-1990 to be 1 second.
1406 + An agent may return a badValue error if a set is
1407 + attempted to a value which is not a whole number
1408 + of seconds."
1409 + REFERENCE
1410 + "IEEE 802.1D-1990: Section 4.5.3.10"
1411 + ::= { dot1dStp 14 }
1412 +
1413 +-- The Spanning Tree Port Table
1414 +
1415 +dot1dStpPortTable OBJECT-TYPE
1416 + SYNTAX SEQUENCE OF Dot1dStpPortEntry
1417 + ACCESS not-accessible
1418 + STATUS mandatory
1419 + DESCRIPTION
1420 + "A table that contains port-specific information
1421 + for the Spanning Tree Protocol."
1422 + ::= { dot1dStp 15 }
1423 +
1424 +dot1dStpPortEntry OBJECT-TYPE
1425 + SYNTAX Dot1dStpPortEntry
1426 + ACCESS not-accessible
1427 + STATUS mandatory
1428 + DESCRIPTION
1429 + "A list of information maintained by every port
1430 + about the Spanning Tree Protocol state for that
1431 + port."
1432 + INDEX { dot1dStpPort }
1433 + ::= { dot1dStpPortTable 1 }
1434 +
1435 +Dot1dStpPortEntry ::=
1436 + SEQUENCE {
1437 + dot1dStpPort
1438 + INTEGER,
1439 + dot1dStpPortPriority
1440 + INTEGER,
1441 + dot1dStpPortState
1442 + INTEGER,
1443 + dot1dStpPortEnable
1444 + INTEGER,
1445 + dot1dStpPortPathCost
1446 + INTEGER,
1447 + dot1dStpPortDesignatedRoot
1448 + BridgeId,
1449 + dot1dStpPortDesignatedCost
1450 + INTEGER,
1451 + dot1dStpPortDesignatedBridge
1452 + BridgeId,
1453 + dot1dStpPortDesignatedPort
1454 + OCTET STRING,
1455 + dot1dStpPortForwardTransitions
1456 + Counter
1457 + }
1458 +
1459 +dot1dStpPort OBJECT-TYPE
1460 + SYNTAX INTEGER (1..65535)
1461 +
1462 + ACCESS read-only
1463 + STATUS mandatory
1464 + DESCRIPTION
1465 + "The port number of the port for which this entry
1466 + contains Spanning Tree Protocol management
1467 + information."
1468 + REFERENCE
1469 + "IEEE 802.1D-1990: Section 6.8.2.1.2"
1470 + ::= { dot1dStpPortEntry 1 }
1471 +
1472 +dot1dStpPortPriority OBJECT-TYPE
1473 + SYNTAX INTEGER (0..255)
1474 + ACCESS read-write
1475 + STATUS mandatory
1476 + DESCRIPTION
1477 + "The value of the priority field which is
1478 + contained in the first (in network byte order)
1479 + octet of the (2 octet long) Port ID. The other
1480 + octet of the Port ID is given by the value of
1481 + dot1dStpPort."
1482 + REFERENCE
1483 + "IEEE 802.1D-1990: Section 4.5.5.1"
1484 + ::= { dot1dStpPortEntry 2 }
1485 +
1486 +dot1dStpPortState OBJECT-TYPE
1487 + SYNTAX INTEGER {
1488 + disabled(1),
1489 + blocking(2),
1490 + listening(3),
1491 + learning(4),
1492 + forwarding(5),
1493 + broken(6)
1494 + }
1495 + ACCESS read-only
1496 + STATUS mandatory
1497 + DESCRIPTION
1498 + "The port's current state as defined by
1499 + application of the Spanning Tree Protocol. This
1500 + state controls what action a port takes on
1501 + reception of a frame. If the bridge has detected
1502 + a port that is malfunctioning it will place that
1503 + port into the broken(6) state. For ports which
1504 + are disabled (see dot1dStpPortEnable), this object
1505 + will have a value of disabled(1)."
1506 + REFERENCE
1507 + "IEEE 802.1D-1990: Section 4.5.5.2"
1508 + ::= { dot1dStpPortEntry 3 }
1509 +
1510 +dot1dStpPortEnable OBJECT-TYPE
1511 + SYNTAX INTEGER {
1512 + enabled(1),
1513 + disabled(2)
1514 + }
1515 + ACCESS read-write
1516 + STATUS mandatory
1517 + DESCRIPTION
1518 + "The enabled/disabled status of the port."
1519 + REFERENCE
1520 + "IEEE 802.1D-1990: Section 4.5.5.2"
1521 + ::= { dot1dStpPortEntry 4 }
1522 +
1523 +dot1dStpPortPathCost OBJECT-TYPE
1524 + SYNTAX INTEGER (1..65535)
1525 + ACCESS read-write
1526 + STATUS mandatory
1527 + DESCRIPTION
1528 + "The contribution of this port to the path cost of
1529 + paths towards the spanning tree root which include
1530 + this port. 802.1D-1990 recommends that the
1531 + default value of this parameter be in inverse
1532 + proportion to the speed of the attached LAN."
1533 + REFERENCE
1534 + "IEEE 802.1D-1990: Section 4.5.5.3"
1535 + ::= { dot1dStpPortEntry 5 }
1536 +
1537 +dot1dStpPortDesignatedRoot OBJECT-TYPE
1538 + SYNTAX BridgeId
1539 + ACCESS read-only
1540 + STATUS mandatory
1541 + DESCRIPTION
1542 + "The unique Bridge Identifier of the Bridge
1543 + recorded as the Root in the Configuration BPDUs
1544 + transmitted by the Designated Bridge for the
1545 + segment to which the port is attached."
1546 + REFERENCE
1547 + "IEEE 802.1D-1990: Section 4.5.5.4"
1548 + ::= { dot1dStpPortEntry 6 }
1549 +
1550 +dot1dStpPortDesignatedCost OBJECT-TYPE
1551 + SYNTAX INTEGER
1552 + ACCESS read-only
1553 + STATUS mandatory
1554 + DESCRIPTION
1555 + "The path cost of the Designated Port of the
1556 + segment connected to this port. This value is
1557 + compared to the Root Path Cost field in received
1558 +
1559 + bridge PDUs."
1560 + REFERENCE
1561 + "IEEE 802.1D-1990: Section 4.5.5.5"
1562 + ::= { dot1dStpPortEntry 7 }
1563 +
1564 +dot1dStpPortDesignatedBridge OBJECT-TYPE
1565 + SYNTAX BridgeId
1566 + ACCESS read-only
1567 + STATUS mandatory
1568 + DESCRIPTION
1569 + "The Bridge Identifier of the bridge which this
1570 + port considers to be the Designated Bridge for
1571 + this port's segment."
1572 + REFERENCE
1573 + "IEEE 802.1D-1990: Section 4.5.5.6"
1574 + ::= { dot1dStpPortEntry 8 }
1575 +
1576 +dot1dStpPortDesignatedPort OBJECT-TYPE
1577 + SYNTAX OCTET STRING (SIZE (2))
1578 + ACCESS read-only
1579 + STATUS mandatory
1580 + DESCRIPTION
1581 + "The Port Identifier of the port on the Designated
1582 + Bridge for this port's segment."
1583 + REFERENCE
1584 + "IEEE 802.1D-1990: Section 4.5.5.7"
1585 + ::= { dot1dStpPortEntry 9 }
1586 +
1587 +dot1dStpPortForwardTransitions OBJECT-TYPE
1588 + SYNTAX Counter
1589 + ACCESS read-only
1590 + STATUS mandatory
1591 + DESCRIPTION
1592 + "The number of times this port has transitioned
1593 + from the Learning state to the Forwarding state."
1594 + ::= { dot1dStpPortEntry 10 }
1595 +
1596 +-- the dot1dTp group
1597 +
1598 +-- Implementation of the dot1dTp group is optional. It is
1599 +-- implemented by those bridges that support the transparent
1600 +-- bridging mode. A transparent or SRT bridge will implement
1601 +-- this group.
1602 +
1603 +dot1dTpLearnedEntryDiscards OBJECT-TYPE
1604 + SYNTAX Counter
1605 +
1606 + ACCESS read-only
1607 + STATUS mandatory
1608 + DESCRIPTION
1609 + "The total number of Forwarding Database entries,
1610 + which have been or would have been learnt, but
1611 + have been discarded due to a lack of space to
1612 + store them in the Forwarding Database. If this
1613 + counter is increasing, it indicates that the
1614 + Forwarding Database is regularly becoming full (a
1615 + condition which has unpleasant performance effects
1616 + on the subnetwork). If this counter has a
1617 + significant value but is not presently increasing,
1618 + it indicates that the problem has been occurring
1619 + but is not persistent."
1620 + REFERENCE
1621 + "IEEE 802.1D-1990: Section 6.7.1.1.3"
1622 + ::= { dot1dTp 1 }
1623 +
1624 +dot1dTpAgingTime OBJECT-TYPE
1625 + SYNTAX INTEGER (10..1000000)
1626 + ACCESS read-write
1627 + STATUS mandatory
1628 + DESCRIPTION
1629 + "The timeout period in seconds for aging out
1630 + dynamically learned forwarding information.
1631 + 802.1D-1990 recommends a default of 300 seconds."
1632 + REFERENCE
1633 + "IEEE 802.1D-1990: Section 6.7.1.1.3"
1634 + ::= { dot1dTp 2 }
1635 +
1636 +-- The Forwarding Database for Transparent Bridges
1637 +
1638 +dot1dTpFdbTable OBJECT-TYPE
1639 + SYNTAX SEQUENCE OF Dot1dTpFdbEntry
1640 + ACCESS not-accessible
1641 + STATUS mandatory
1642 + DESCRIPTION
1643 + "A table that contains information about unicast
1644 + entries for which the bridge has forwarding and/or
1645 + filtering information. This information is used
1646 + by the transparent bridging function in
1647 + determining how to propagate a received frame."
1648 + ::= { dot1dTp 3 }
1649 +
1650 +dot1dTpFdbEntry OBJECT-TYPE
1651 + SYNTAX Dot1dTpFdbEntry
1652 + ACCESS not-accessible
1653 + STATUS mandatory
1654 + DESCRIPTION
1655 + "Information about a specific unicast MAC address
1656 + for which the bridge has some forwarding and/or
1657 + filtering information."
1658 + INDEX { dot1dTpFdbAddress }
1659 + ::= { dot1dTpFdbTable 1 }
1660 +
1661 +Dot1dTpFdbEntry ::=
1662 + SEQUENCE {
1663 + dot1dTpFdbAddress
1664 + MacAddress,
1665 + dot1dTpFdbPort
1666 + INTEGER,
1667 + dot1dTpFdbStatus
1668 + INTEGER
1669 + }
1670 +
1671 +dot1dTpFdbAddress OBJECT-TYPE
1672 + SYNTAX MacAddress
1673 + ACCESS read-only
1674 + STATUS mandatory
1675 + DESCRIPTION
1676 + "A unicast MAC address for which the bridge has
1677 + forwarding and/or filtering information."
1678 + REFERENCE
1679 + "IEEE 802.1D-1990: Section 3.9.1, 3.9.2"
1680 + ::= { dot1dTpFdbEntry 1 }
1681 +
1682 +dot1dTpFdbPort OBJECT-TYPE
1683 + SYNTAX INTEGER
1684 + ACCESS read-only
1685 + STATUS mandatory
1686 + DESCRIPTION
1687 + "Either the value '0', or the port number of the
1688 + port on which a frame having a source address
1689 + equal to the value of the corresponding instance
1690 + of dot1dTpFdbAddress has been seen. A value of
1691 + '0' indicates that the port number has not been
1692 + learned but that the bridge does have some
1693 + forwarding/filtering information about this
1694 + address (e.g. in the dot1dStaticTable).
1695 + Implementors are encouraged to assign the port
1696 + value to this object whenever it is learned even
1697 + for addresses for which the corresponding value of
1698 + dot1dTpFdbStatus is not learned(3)."
1699 + ::= { dot1dTpFdbEntry 2 }
1700 +
1701 +dot1dTpFdbStatus OBJECT-TYPE
1702 + SYNTAX INTEGER {
1703 + other(1),
1704 + invalid(2),
1705 + learned(3),
1706 + self(4),
1707 + mgmt(5)
1708 + }
1709 + ACCESS read-only
1710 + STATUS mandatory
1711 + DESCRIPTION
1712 + "The status of this entry. The meanings of the
1713 + values are:
1714 + other(1) : none of the following. This would
1715 + include the case where some other
1716 + MIB object (not the corresponding
1717 + instance of dot1dTpFdbPort, nor an
1718 + entry in the dot1dStaticTable) is
1719 + being used to determine if and how
1720 + frames addressed to the value of
1721 + the corresponding instance of
1722 + dot1dTpFdbAddress are being
1723 + forwarded.
1724 + invalid(2) : this entry is not longer valid
1725 + (e.g., it was learned but has since
1726 + aged-out), but has not yet been
1727 + flushed from the table.
1728 + learned(3) : the value of the corresponding
1729 + instance of dot1dTpFdbPort was
1730 + learned, and is being used.
1731 + self(4) : the value of the corresponding
1732 + instance of dot1dTpFdbAddress
1733 + represents one of the bridge's
1734 + addresses. The corresponding
1735 + instance of dot1dTpFdbPort
1736 + indicates which of the bridge's
1737 + ports has this address.
1738 + mgmt(5) : the value of the corresponding
1739 + instance of dot1dTpFdbAddress is
1740 + also the value of an existing
1741 + instance of dot1dStaticAddress."
1742 + ::= { dot1dTpFdbEntry 3 }
1743 +
1744 +-- Port Table for Transparent Bridges
1745 +
1746 +dot1dTpPortTable OBJECT-TYPE
1747 + SYNTAX SEQUENCE OF Dot1dTpPortEntry
1748 + ACCESS not-accessible
1749 + STATUS mandatory
1750 + DESCRIPTION
1751 + "A table that contains information about every
1752 + port that is associated with this transparent
1753 + bridge."
1754 + ::= { dot1dTp 4 }
1755 +
1756 +dot1dTpPortEntry OBJECT-TYPE
1757 + SYNTAX Dot1dTpPortEntry
1758 + ACCESS not-accessible
1759 + STATUS mandatory
1760 + DESCRIPTION
1761 + "A list of information for each port of a
1762 + transparent bridge."
1763 + INDEX { dot1dTpPort }
1764 + ::= { dot1dTpPortTable 1 }
1765 +
1766 +Dot1dTpPortEntry ::=
1767 + SEQUENCE {
1768 + dot1dTpPort
1769 + INTEGER,
1770 + dot1dTpPortMaxInfo
1771 + INTEGER,
1772 + dot1dTpPortInFrames
1773 + Counter,
1774 + dot1dTpPortOutFrames
1775 + Counter,
1776 + dot1dTpPortInDiscards
1777 + Counter
1778 + }
1779 +
1780 +dot1dTpPort OBJECT-TYPE
1781 + SYNTAX INTEGER (1..65535)
1782 + ACCESS read-only
1783 + STATUS mandatory
1784 + DESCRIPTION
1785 + "The port number of the port for which this entry
1786 + contains Transparent bridging management
1787 + information."
1788 + ::= { dot1dTpPortEntry 1 }
1789 +
1790 +-- It would be nice if we could use ifMtu as the size of the
1791 +-- largest INFO field, but we can't because ifMtu is defined
1792 +-- to be the size that the (inter-)network layer can use which
1793 +-- can differ from the MAC layer (especially if several layers
1794 +-- of encapsulation are used).
1795 +
1796 +dot1dTpPortMaxInfo OBJECT-TYPE
1797 + SYNTAX INTEGER
1798 + ACCESS read-only
1799 + STATUS mandatory
1800 + DESCRIPTION
1801 + "The maximum size of the INFO (non-MAC) field that
1802 + this port will receive or transmit."
1803 + ::= { dot1dTpPortEntry 2 }
1804 +
1805 +dot1dTpPortInFrames OBJECT-TYPE
1806 + SYNTAX Counter
1807 + ACCESS read-only
1808 + STATUS mandatory
1809 + DESCRIPTION
1810 + "The number of frames that have been received by
1811 + this port from its segment. Note that a frame
1812 + received on the interface corresponding to this
1813 + port is only counted by this object if and only if
1814 + it is for a protocol being processed by the local
1815 + bridging function, including bridge management
1816 + frames."
1817 + REFERENCE
1818 + "IEEE 802.1D-1990: Section 6.6.1.1.3"
1819 + ::= { dot1dTpPortEntry 3 }
1820 +
1821 +dot1dTpPortOutFrames OBJECT-TYPE
1822 + SYNTAX Counter
1823 + ACCESS read-only
1824 + STATUS mandatory
1825 + DESCRIPTION
1826 + "The number of frames that have been transmitted
1827 + by this port to its segment. Note that a frame
1828 + transmitted on the interface corresponding to this
1829 + port is only counted by this object if and only if
1830 + it is for a protocol being processed by the local
1831 + bridging function, including bridge management
1832 + frames."
1833 + REFERENCE
1834 + "IEEE 802.1D-1990: Section 6.6.1.1.3"
1835 + ::= { dot1dTpPortEntry 4 }
1836 +
1837 +dot1dTpPortInDiscards OBJECT-TYPE
1838 + SYNTAX Counter
1839 + ACCESS read-only
1840 + STATUS mandatory
1841 + DESCRIPTION
1842 + "Count of valid frames received which were
1843 + discarded (i.e., filtered) by the Forwarding
1844 + Process."
1845 + REFERENCE
1846 + "IEEE 802.1D-1990: Section 6.6.1.1.3"
1847 + ::= { dot1dTpPortEntry 5 }
1848 +-- The Static (Destination-Address Filtering) Database
1849 +
1850 +-- Implementation of this group is optional.
1851 +
1852 +dot1dStaticTable OBJECT-TYPE
1853 + SYNTAX SEQUENCE OF Dot1dStaticEntry
1854 + ACCESS not-accessible
1855 + STATUS mandatory
1856 + DESCRIPTION
1857 + "A table containing filtering information
1858 + configured into the bridge by (local or network)
1859 + management specifying the set of ports to which
1860 + frames received from specific ports and containing
1861 + specific destination addresses are allowed to be
1862 + forwarded. The value of zero in this table as the
1863 + port number from which frames with a specific
1864 + destination address are received, is used to
1865 + specify all ports for which there is no specific
1866 + entry in this table for that particular
1867 + destination address. Entries are valid for
1868 + unicast and for group/broadcast addresses."
1869 + REFERENCE
1870 + "IEEE 802.1D-1990: Section 6.7.2"
1871 + ::= { dot1dStatic 1 }
1872 +
1873 +dot1dStaticEntry OBJECT-TYPE
1874 + SYNTAX Dot1dStaticEntry
1875 + ACCESS not-accessible
1876 + STATUS mandatory
1877 + DESCRIPTION
1878 + "Filtering information configured into the bridge
1879 + by (local or network) management specifying the
1880 + set of ports to which frames received from a
1881 + specific port and containing a specific
1882 + destination address are allowed to be forwarded."
1883 + REFERENCE
1884 + "IEEE 802.1D-1990: Section 6.7.2"
1885 + INDEX { dot1dStaticAddress, dot1dStaticReceivePort }
1886 + ::= { dot1dStaticTable 1 }
1887 +
1888 +Dot1dStaticEntry ::=
1889 + SEQUENCE {
1890 + dot1dStaticAddress
1891 + MacAddress,
1892 + dot1dStaticReceivePort
1893 + INTEGER,
1894 + dot1dStaticAllowedToGoTo
1895 + OCTET STRING,
1896 + dot1dStaticStatus
1897 + INTEGER
1898 + }
1899 +
1900 +dot1dStaticAddress OBJECT-TYPE
1901 + SYNTAX MacAddress
1902 + ACCESS read-write
1903 + STATUS mandatory
1904 + DESCRIPTION
1905 + "The destination MAC address in a frame to which
1906 + this entry's filtering information applies. This
1907 + object can take the value of a unicast address, a
1908 + group address or the broadcast address."
1909 + REFERENCE
1910 + "IEEE 802.1D-1990: Section 3.9.1, 3.9.2"
1911 + ::= { dot1dStaticEntry 1 }
1912 +
1913 +dot1dStaticReceivePort OBJECT-TYPE
1914 + SYNTAX INTEGER
1915 + ACCESS read-write
1916 + STATUS mandatory
1917 + DESCRIPTION
1918 + "Either the value '0', or the port number of the
1919 + port from which a frame must be received in order
1920 + for this entry's filtering information to apply.
1921 + A value of zero indicates that this entry applies
1922 + on all ports of the bridge for which there is no
1923 + other applicable entry."
1924 + ::= { dot1dStaticEntry 2 }
1925 +
1926 +dot1dStaticAllowedToGoTo OBJECT-TYPE
1927 + SYNTAX OCTET STRING
1928 + ACCESS read-write
1929 + STATUS mandatory
1930 + DESCRIPTION
1931 + "The set of ports to which frames received from a
1932 + specific port and destined for a specific MAC
1933 +
1934 + address, are allowed to be forwarded. Each octet
1935 + within the value of this object specifies a set of
1936 + eight ports, with the first octet specifying ports
1937 + 1 through 8, the second octet specifying ports 9
1938 + through 16, etc. Within each octet, the most
1939 + significant bit represents the lowest numbered
1940 + port, and the least significant bit represents the
1941 + highest numbered port. Thus, each port of the
1942 + bridge is represented by a single bit within the
1943 + value of this object. If that bit has a value of
1944 + '1' then that port is included in the set of
1945 + ports; the port is not included if its bit has a
1946 + value of '0'. (Note that the setting of the bit
1947 + corresponding to the port from which a frame is
1948 + received is irrelevant.) The default value of
1949 + this object is a string of ones of appropriate
1950 + length."
1951 + ::= { dot1dStaticEntry 3 }
1952 +
1953 +dot1dStaticStatus OBJECT-TYPE
1954 + SYNTAX INTEGER {
1955 + other(1),
1956 + invalid(2),
1957 + permanent(3),
1958 + deleteOnReset(4),
1959 + deleteOnTimeout(5)
1960 + }
1961 + ACCESS read-write
1962 + STATUS mandatory
1963 + DESCRIPTION
1964 + "This object indicates the status of this entry.
1965 + The default value is permanent(3).
1966 + other(1) - this entry is currently in use but
1967 + the conditions under which it will
1968 + remain so are different from each of the
1969 + following values.
1970 + invalid(2) - writing this value to the object
1971 + removes the corresponding entry.
1972 + permanent(3) - this entry is currently in use
1973 + and will remain so after the next reset
1974 + of the bridge.
1975 + deleteOnReset(4) - this entry is currently in
1976 + use and will remain so until the next
1977 + reset of the bridge.
1978 + deleteOnTimeout(5) - this entry is currently
1979 + in use and will remain so until it is
1980 + aged out."
1981 +
1982 + ::= { dot1dStaticEntry 4 }
1983 +
1984 +-- Traps for use by Bridges
1985 +
1986 +-- Traps for the Spanning Tree Protocol
1987 +
1988 +newRoot TRAP-TYPE
1989 + ENTERPRISE dot1dBridge
1990 + DESCRIPTION
1991 + "The newRoot trap indicates that the sending agent
1992 + has become the new root of the Spanning Tree; the
1993 + trap is sent by a bridge soon after its election
1994 + as the new root, e.g., upon expiration of the
1995 + Topology Change Timer immediately subsequent to
1996 + its election. Implementation of this trap is
1997 + optional."
1998 + ::= 1
1999 +
2000 +topologyChange TRAP-TYPE
2001 + ENTERPRISE dot1dBridge
2002 + DESCRIPTION
2003 + "A topologyChange trap is sent by a bridge when
2004 + any of its configured ports transitions from the
2005 + Learning state to the Forwarding state, or from
2006 + the Forwarding state to the Blocking state. The
2007 + trap is not sent if a newRoot trap is sent for the
2008 + same transition. Implementation of this trap is
2009 + optional."
2010 + ::= 2
2011 +
2012 +END
2013 diff -ruN net-snmp-5.4.1.orig/mibs/GNOME-SMI.txt net-snmp-5.4.1/mibs/GNOME-SMI.txt
2014 --- net-snmp-5.4.1.orig/mibs/GNOME-SMI.txt 1970-01-01 01:00:00.000000000 +0100
2015 +++ net-snmp-5.4.1/mibs/GNOME-SMI.txt 2007-09-20 16:33:55.000000000 +0200
2016 @@ -0,0 +1,88 @@
2017 +GNOME-SMI DEFINITIONS ::= BEGIN
2018 +
2019 +IMPORTS
2020 + MODULE-IDENTITY,
2021 + OBJECT-IDENTITY,
2022 + enterprises
2023 + FROM SNMPv2-SMI;
2024 +
2025 +gnome MODULE-IDENTITY
2026 + LAST-UPDATED "200709070000Z"
2027 + ORGANIZATION "GNOME project"
2028 + CONTACT-INFO
2029 + "GNU Network Object Model Environment project
2030 +
2031 + see http://www.gnome.org for contact persons of a particular
2032 + area or subproject of GNOME.
2033 +
2034 + Administrative contact for MIB module:
2035 +
2036 + Jochen Friedrich
2037 + Ramsaystr. 9
2038 + 63450 Hanau
2039 + Germany
2040 +
2041 + email: jochen@scram.de"
2042 + DESCRIPTION
2043 + "The Structure of GNOME."
2044 +
2045 + -- revision history
2046 +
2047 + REVISION "200709070000Z" -- Sep 07, 2007
2048 + DESCRIPTION
2049 + "Fixed wrong enterprise number (how comes this
2050 + typo was unnoticed for so long?)."
2051 +
2052 + REVISION "200505070000Z" -- May 07, 2005
2053 + DESCRIPTION
2054 + "Added gnomeLDAP subtree for LDAP definitions."
2055 +
2056 + REVISION "200312070000Z" -- December 07, 2003
2057 + DESCRIPTION
2058 + "Added gnomeSysadmin subtree for GNOME project system administration.
2059 + Updated contact info."
2060 +
2061 + REVISION "9809010000Z" -- September 01, 1998
2062 + DESCRIPTION
2063 + "Initial version."
2064 +
2065 + ::= { enterprises 3319 } -- assigned by IANA
2066 +
2067 +gnomeProducts OBJECT-IDENTITY
2068 + STATUS current
2069 + DESCRIPTION
2070 + "gnomeProducts is the root OBJECT IDENTIFIER from
2071 + which sysObjectID values are assigned."
2072 + ::= { gnome 1 }
2073 +
2074 +gnomeMgmt OBJECT-IDENTITY
2075 + STATUS current
2076 + DESCRIPTION
2077 + "gnomeMgmt defines the subtree for production GNOME related
2078 + MIB registrations."
2079 + ::= { gnome 2 }
2080 +
2081 +gnomeTest OBJECT-IDENTITY
2082 + STATUS current
2083 + DESCRIPTION
2084 + "gnomeTest defines the subtree for testing GNOME related
2085 + MIB registrations."
2086 + ::= { gnome 3 }
2087 +
2088 +gnomeSysadmin OBJECT-IDENTITY
2089 + STATUS current
2090 + DESCRIPTION
2091 + "gnomeSysadmin defines the subtree for GNOME related Sysadmin
2092 + MIB registrations."
2093 + ::= { gnome 4 }
2094 +
2095 +gnomeLDAP OBJECT-IDENTITY
2096 + STATUS current
2097 + DESCRIPTION
2098 + "gnomeLDAP defines the subtree for GNOME related LDAP
2099 + registrations."
2100 + ::= { gnome 5 }
2101 +
2102 +-- more to come if necessary.
2103 +
2104 +END
2105 diff -ruN net-snmp-5.4.1.orig/mibs/OSPF-MIB.txt net-snmp-5.4.1/mibs/OSPF-MIB.txt
2106 --- net-snmp-5.4.1.orig/mibs/OSPF-MIB.txt 1970-01-01 01:00:00.000000000 +0100
2107 +++ net-snmp-5.4.1/mibs/OSPF-MIB.txt 2007-09-20 16:30:52.000000000 +0200
2108 @@ -0,0 +1,2723 @@
2109 +OSPF-MIB DEFINITIONS ::= BEGIN
2110 +
2111 + IMPORTS
2112 + MODULE-IDENTITY, OBJECT-TYPE, Counter32, Gauge32,
2113 + Integer32, IpAddress
2114 + FROM SNMPv2-SMI
2115 + TEXTUAL-CONVENTION, TruthValue, RowStatus
2116 + FROM SNMPv2-TC
2117 + MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
2118 + mib-2 FROM RFC1213-MIB;
2119 +
2120 +-- This MIB module uses the extended OBJECT-TYPE macro as
2121 +-- defined in [9].
2122 +
2123 +ospf MODULE-IDENTITY
2124 + LAST-UPDATED "9501201225Z" -- Fri Jan 20 12:25:50 PST 1995
2125 + ORGANIZATION "IETF OSPF Working Group"
2126 + CONTACT-INFO
2127 + " Fred Baker
2128 + Postal: Cisco Systems
2129 + 519 Lado Drive
2130 + Santa Barbara, California 93111
2131 + Tel: +1 805 681 0115
2132 + E-Mail: fred@cisco.com
2133 +
2134 + Rob Coltun
2135 + Postal: RainbowBridge Communications
2136 + Tel: (301) 340-9416
2137 + E-Mail: rcoltun@rainbow-bridge.com"
2138 + DESCRIPTION
2139 + "The MIB module to describe the OSPF Version 2
2140 + Protocol"
2141 + ::= { mib-2 14 }
2142 +
2143 +-- The Area ID, in OSPF, has the same format as an IP Address,
2144 +-- but has the function of defining a summarization point for
2145 +-- Link State Advertisements
2146 +
2147 +AreaID ::= TEXTUAL-CONVENTION
2148 + STATUS current
2149 + DESCRIPTION
2150 + "An OSPF Area Identifier."
2151 + SYNTAX IpAddress
2152 +
2153 +
2154 +-- The Router ID, in OSPF, has the same format as an IP Address,
2155 +-- but identifies the router independent of its IP Address.
2156 +
2157 +RouterID ::= TEXTUAL-CONVENTION
2158 + STATUS current
2159 + DESCRIPTION
2160 + "A OSPF Router Identifier."
2161 + SYNTAX IpAddress
2162 +
2163 +
2164 +-- The OSPF Metric is defined as an unsigned value in the range
2165 +
2166 +Metric ::= TEXTUAL-CONVENTION
2167 + STATUS current
2168 + DESCRIPTION
2169 + "The OSPF Internal Metric."
2170 + SYNTAX Integer32 (0..'FFFF'h)
2171 +
2172 +BigMetric ::= TEXTUAL-CONVENTION
2173 + STATUS current
2174 + DESCRIPTION
2175 + "The OSPF External Metric."
2176 + SYNTAX Integer32 (0..'FFFFFF'h)
2177 +
2178 +-- Status Values
2179 +
2180 +Status ::= TEXTUAL-CONVENTION
2181 + STATUS current
2182 + DESCRIPTION
2183 + "The status of an interface: 'enabled' indicates that
2184 + it is willing to communicate with other OSPF Routers,
2185 + while 'disabled' indicates that it is not."
2186 + SYNTAX INTEGER { enabled (1), disabled (2) }
2187 +
2188 +-- Time Durations measured in seconds
2189 +
2190 +PositiveInteger ::= TEXTUAL-CONVENTION
2191 + STATUS current
2192 + DESCRIPTION
2193 + "A positive integer. Values in excess are precluded as
2194 + unnecessary and prone to interoperability issues."
2195 + SYNTAX Integer32 (0..'7FFFFFFF'h)
2196 +
2197 +HelloRange ::= TEXTUAL-CONVENTION
2198 + STATUS current
2199 + DESCRIPTION
2200 + "The range of intervals on which hello messages are
2201 + exchanged."
2202 + SYNTAX Integer32 (1..'FFFF'h)
2203 +
2204 +UpToMaxAge ::= TEXTUAL-CONVENTION
2205 + STATUS current
2206 + DESCRIPTION
2207 + "The values that one might find or configure for
2208 + variables bounded by the maximum age of an LSA."
2209 + SYNTAX Integer32 (0..3600)
2210 +
2211 +
2212 +-- The range of ifIndex
2213 +
2214 +InterfaceIndex ::= TEXTUAL-CONVENTION
2215 + STATUS current
2216 + DESCRIPTION
2217 + "The range of ifIndex."
2218 + SYNTAX Integer32
2219 +
2220 +
2221 +-- Potential Priorities for the Designated Router Election
2222 +
2223 +DesignatedRouterPriority ::= TEXTUAL-CONVENTION
2224 + STATUS current
2225 + DESCRIPTION
2226 + "The values defined for the priority of a system for
2227 + becoming the designated router."
2228 + SYNTAX Integer32 (0..'FF'h)
2229 +
2230 +TOSType ::= TEXTUAL-CONVENTION
2231 + STATUS current
2232 + DESCRIPTION
2233 + "Type of Service is defined as a mapping to the IP Type of
2234 + Service Flags as defined in the IP Forwarding Table MIB
2235 +
2236 + +-----+-----+-----+-----+-----+-----+-----+-----+
2237 + | | | |
2238 + | PRECEDENCE | TYPE OF SERVICE | 0 |
2239 + | | | |
2240 + +-----+-----+-----+-----+-----+-----+-----+-----+
2241 +
2242 + IP TOS IP TOS
2243 + Field Policy Field Policy
2244 +
2245 + Contents Code Contents Code
2246 + 0 0 0 0 ==> 0 0 0 0 1 ==> 2
2247 + 0 0 1 0 ==> 4 0 0 1 1 ==> 6
2248 + 0 1 0 0 ==> 8 0 1 0 1 ==> 10
2249 + 0 1 1 0 ==> 12 0 1 1 1 ==> 14
2250 + 1 0 0 0 ==> 16 1 0 0 1 ==> 18
2251 + 1 0 1 0 ==> 20 1 0 1 1 ==> 22
2252 + 1 1 0 0 ==> 24 1 1 0 1 ==> 26
2253 + 1 1 1 0 ==> 28 1 1 1 1 ==> 30
2254 +
2255 + The remaining values are left for future definition."
2256 + SYNTAX Integer32 (0..30)
2257 +
2258 +
2259 +-- OSPF General Variables
2260 +
2261 +-- These parameters apply globally to the Router's
2262 +-- OSPF Process.
2263 +
2264 +ospfGeneralGroup OBJECT IDENTIFIER ::= { ospf 1 }
2265 +
2266 +
2267 + ospfRouterId OBJECT-TYPE
2268 + SYNTAX RouterID
2269 + MAX-ACCESS read-write
2270 + STATUS current
2271 + DESCRIPTION
2272 + "A 32-bit integer uniquely identifying the
2273 + router in the Autonomous System.
2274 +
2275 + By convention, to ensure uniqueness, this
2276 + should default to the value of one of the
2277 + router's IP interface addresses."
2278 + REFERENCE
2279 + "OSPF Version 2, C.1 Global parameters"
2280 + ::= { ospfGeneralGroup 1 }
2281 +
2282 +
2283 + ospfAdminStat OBJECT-TYPE
2284 + SYNTAX Status
2285 + MAX-ACCESS read-write
2286 + STATUS current
2287 + DESCRIPTION
2288 + "The administrative status of OSPF in the
2289 + router. The value 'enabled' denotes that the
2290 + OSPF Process is active on at least one inter-
2291 + face; 'disabled' disables it on all inter-
2292 + faces."
2293 + ::= { ospfGeneralGroup 2 }
2294 +
2295 + ospfVersionNumber OBJECT-TYPE
2296 + SYNTAX INTEGER { version2 (2) }
2297 + MAX-ACCESS read-only
2298 + STATUS current
2299 + DESCRIPTION
2300 + "The current version number of the OSPF proto-
2301 + col is 2."
2302 + REFERENCE
2303 + "OSPF Version 2, Title"
2304 + ::= { ospfGeneralGroup 3 }
2305 +
2306 +
2307 + ospfAreaBdrRtrStatus OBJECT-TYPE
2308 + SYNTAX TruthValue
2309 + MAX-ACCESS read-only
2310 + STATUS current
2311 + DESCRIPTION
2312 + "A flag to note whether this router is an area
2313 + border router."
2314 + REFERENCE
2315 + "OSPF Version 2, Section 3 Splitting the AS into
2316 + Areas"
2317 + ::= { ospfGeneralGroup 4 }
2318 +
2319 +
2320 + ospfASBdrRtrStatus OBJECT-TYPE
2321 + SYNTAX TruthValue
2322 + MAX-ACCESS read-write
2323 + STATUS current
2324 + DESCRIPTION
2325 + "A flag to note whether this router is config-
2326 + ured as an Autonomous System border router."
2327 + REFERENCE
2328 + "OSPF Version 2, Section 3.3 Classification of
2329 + routers"
2330 + ::= { ospfGeneralGroup 5 }
2331 +
2332 + ospfExternLsaCount OBJECT-TYPE
2333 + SYNTAX Gauge32
2334 + MAX-ACCESS read-only
2335 + STATUS current
2336 + DESCRIPTION
2337 + "The number of external (LS type 5) link-state
2338 + advertisements in the link-state database."
2339 + REFERENCE
2340 + "OSPF Version 2, Appendix A.4.5 AS external link
2341 + advertisements"
2342 + ::= { ospfGeneralGroup 6 }
2343 +
2344 +
2345 + ospfExternLsaCksumSum OBJECT-TYPE
2346 + SYNTAX Integer32
2347 + MAX-ACCESS read-only
2348 + STATUS current
2349 + DESCRIPTION
2350 + "The 32-bit unsigned sum of the LS checksums of
2351 + the external link-state advertisements con-
2352 + tained in the link-state database. This sum
2353 + can be used to determine if there has been a
2354 + change in a router's link state database, and
2355 + to compare the link-state database of two
2356 + routers."
2357 + ::= { ospfGeneralGroup 7 }
2358 +
2359 +
2360 + ospfTOSSupport OBJECT-TYPE
2361 + SYNTAX TruthValue
2362 + MAX-ACCESS read-write
2363 + STATUS current
2364 + DESCRIPTION
2365 + "The router's support for type-of-service rout-
2366 + ing."
2367 + REFERENCE
2368 + "OSPF Version 2, Appendix F.1.2 Optional TOS
2369 + support"
2370 + ::= { ospfGeneralGroup 8 }
2371 +
2372 + ospfOriginateNewLsas OBJECT-TYPE
2373 + SYNTAX Counter32
2374 + MAX-ACCESS read-only
2375 + STATUS current
2376 + DESCRIPTION
2377 + "The number of new link-state advertisements
2378 + that have been originated. This number is in-
2379 + cremented each time the router originates a new
2380 + LSA."
2381 + ::= { ospfGeneralGroup 9 }
2382 +
2383 +
2384 + ospfRxNewLsas OBJECT-TYPE
2385 + SYNTAX Counter32
2386 + MAX-ACCESS read-only
2387 + STATUS current
2388 + DESCRIPTION
2389 + "The number of link-state advertisements re-
2390 + ceived determined to be new instantiations.
2391 + This number does not include newer instantia-
2392 + tions of self-originated link-state advertise-
2393 + ments."
2394 + ::= { ospfGeneralGroup 10 }
2395 +
2396 + ospfExtLsdbLimit OBJECT-TYPE
2397 + SYNTAX Integer32 (-1..'7FFFFFFF'h)
2398 + MAX-ACCESS read-write
2399 + STATUS current
2400 + DESCRIPTION
2401 + "The maximum number of non-default AS-
2402 + external-LSAs entries that can be stored in the
2403 + link-state database. If the value is -1, then
2404 + there is no limit.
2405 +
2406 + When the number of non-default AS-external-LSAs
2407 + in a router's link-state database reaches
2408 + ospfExtLsdbLimit, the router enters Overflow-
2409 + State. The router never holds more than
2410 + ospfExtLsdbLimit non-default AS-external-LSAs
2411 + in its database. OspfExtLsdbLimit MUST be set
2412 + identically in all routers attached to the OSPF
2413 + backbone and/or any regular OSPF area. (i.e.,
2414 + OSPF stub areas and NSSAs are excluded)."
2415 + DEFVAL { -1 }
2416 + ::= { ospfGeneralGroup 11 }
2417 +
2418 + ospfMulticastExtensions OBJECT-TYPE
2419 + SYNTAX Integer32
2420 + MAX-ACCESS read-write
2421 + STATUS current
2422 + DESCRIPTION
2423 + "A Bit Mask indicating whether the router is
2424 + forwarding IP multicast (Class D) datagrams
2425 + based on the algorithms defined in the Multi-
2426 + cast Extensions to OSPF.
2427 +
2428 + Bit 0, if set, indicates that the router can
2429 + forward IP multicast datagrams in the router's
2430 + directly attached areas (called intra-area mul-
2431 + ticast routing).
2432 +
2433 + Bit 1, if set, indicates that the router can
2434 + forward IP multicast datagrams between OSPF
2435 + areas (called inter-area multicast routing).
2436 +
2437 + Bit 2, if set, indicates that the router can
2438 + forward IP multicast datagrams between Auto-
2439 + nomous Systems (called inter-AS multicast rout-
2440 + ing).
2441 +
2442 + Only certain combinations of bit settings are
2443 + allowed, namely: 0 (no multicast forwarding is
2444 + enabled), 1 (intra-area multicasting only), 3
2445 + (intra-area and inter-area multicasting), 5
2446 + (intra-area and inter-AS multicasting) and 7
2447 + (multicasting everywhere). By default, no mul-
2448 + ticast forwarding is enabled."
2449 + DEFVAL { 0 }
2450 + ::= { ospfGeneralGroup 12 }
2451 +
2452 + ospfExitOverflowInterval OBJECT-TYPE
2453 + SYNTAX PositiveInteger
2454 + MAX-ACCESS read-write
2455 + STATUS current
2456 + DESCRIPTION
2457 + "The number of seconds that, after entering
2458 + OverflowState, a router will attempt to leave
2459 + OverflowState. This allows the router to again
2460 + originate non-default AS-external-LSAs. When
2461 + set to 0, the router will not leave Overflow-
2462 + State until restarted."
2463 + DEFVAL { 0 }
2464 + ::= { ospfGeneralGroup 13 }
2465 +
2466 +
2467 + ospfDemandExtensions OBJECT-TYPE
2468 + SYNTAX TruthValue
2469 + MAX-ACCESS read-write
2470 + STATUS current
2471 + DESCRIPTION
2472 + "The router's support for demand routing."
2473 + REFERENCE
2474 + "OSPF Version 2, Appendix on Demand Routing"
2475 + ::= { ospfGeneralGroup 14 }
2476 +
2477 +
2478 +-- The OSPF Area Data Structure contains information
2479 +-- regarding the various areas. The interfaces and
2480 +-- virtual links are configured as part of these areas.
2481 +-- Area 0.0.0.0, by definition, is the Backbone Area
2482 +
2483 +
2484 + ospfAreaTable OBJECT-TYPE
2485 + SYNTAX SEQUENCE OF OspfAreaEntry
2486 + MAX-ACCESS not-accessible
2487 + STATUS current
2488 + DESCRIPTION
2489 + "Information describing the configured parame-
2490 + ters and cumulative statistics of the router's
2491 + attached areas."
2492 + REFERENCE
2493 + "OSPF Version 2, Section 6 The Area Data Struc-
2494 + ture"
2495 + ::= { ospf 2 }
2496 +
2497 +
2498 + ospfAreaEntry OBJECT-TYPE
2499 + SYNTAX OspfAreaEntry
2500 + MAX-ACCESS not-accessible
2501 + STATUS current
2502 + DESCRIPTION
2503 + "Information describing the configured parame-
2504 + ters and cumulative statistics of one of the
2505 + router's attached areas."
2506 + INDEX { ospfAreaId }
2507 + ::= { ospfAreaTable 1 }
2508 +
2509 +OspfAreaEntry ::=
2510 + SEQUENCE {
2511 + ospfAreaId
2512 + AreaID,
2513 + ospfAuthType
2514 + Integer32,
2515 + ospfImportAsExtern
2516 + INTEGER,
2517 + ospfSpfRuns
2518 + Counter32,
2519 + ospfAreaBdrRtrCount
2520 + Gauge32,
2521 + ospfAsBdrRtrCount
2522 + Gauge32,
2523 + ospfAreaLsaCount
2524 + Gauge32,
2525 + ospfAreaLsaCksumSum
2526 + Integer32,
2527 + ospfAreaSummary
2528 + INTEGER,
2529 + ospfAreaStatus
2530 + RowStatus
2531 + }
2532 +
2533 + ospfAreaId OBJECT-TYPE
2534 + SYNTAX AreaID
2535 + MAX-ACCESS read-only
2536 + STATUS current
2537 + DESCRIPTION
2538 + "A 32-bit integer uniquely identifying an area.
2539 + Area ID 0.0.0.0 is used for the OSPF backbone."
2540 + REFERENCE
2541 + "OSPF Version 2, Appendix C.2 Area parameters"
2542 + ::= { ospfAreaEntry 1 }
2543 +
2544 +
2545 + ospfAuthType OBJECT-TYPE
2546 + SYNTAX Integer32
2547 + -- none (0),
2548 + -- simplePassword (1)
2549 + -- md5 (2)
2550 + -- reserved for specification by IANA (> 2)
2551 + MAX-ACCESS read-create
2552 + STATUS obsolete
2553 + DESCRIPTION
2554 + "The authentication type specified for an area.
2555 + Additional authentication types may be assigned
2556 + locally on a per Area basis."
2557 + REFERENCE
2558 + "OSPF Version 2, Appendix E Authentication"
2559 + DEFVAL { 0 } -- no authentication, by default
2560 + ::= { ospfAreaEntry 2 }
2561 +
2562 + ospfImportAsExtern OBJECT-TYPE
2563 + SYNTAX INTEGER {
2564 + importExternal (1),
2565 + importNoExternal (2),
2566 + importNssa (3)
2567 + }
2568 + MAX-ACCESS read-create
2569 + STATUS current
2570 + DESCRIPTION
2571 + "The area's support for importing AS external
2572 + link- state advertisements."
2573 + REFERENCE
2574 + "OSPF Version 2, Appendix C.2 Area parameters"
2575 + DEFVAL { importExternal }
2576 + ::= { ospfAreaEntry 3 }
2577 +
2578 +
2579 + ospfSpfRuns OBJECT-TYPE
2580 + SYNTAX Counter32
2581 + MAX-ACCESS read-only
2582 + STATUS current
2583 + DESCRIPTION
2584 + "The number of times that the intra-area route
2585 + table has been calculated using this area's
2586 + link-state database. This is typically done
2587 + using Dijkstra's algorithm."
2588 + ::= { ospfAreaEntry 4 }
2589 +
2590 +
2591 + ospfAreaBdrRtrCount OBJECT-TYPE
2592 + SYNTAX Gauge32
2593 + MAX-ACCESS read-only
2594 + STATUS current
2595 + DESCRIPTION
2596 + "The total number of area border routers reach-
2597 + able within this area. This is initially zero,
2598 + and is calculated in each SPF Pass."
2599 + ::= { ospfAreaEntry 5 }
2600 +
2601 + ospfAsBdrRtrCount OBJECT-TYPE
2602 + SYNTAX Gauge32
2603 + MAX-ACCESS read-only
2604 + STATUS current
2605 + DESCRIPTION
2606 + "The total number of Autonomous System border
2607 + routers reachable within this area. This is
2608 + initially zero, and is calculated in each SPF
2609 + Pass."
2610 + ::= { ospfAreaEntry 6 }
2611 +
2612 +
2613 + ospfAreaLsaCount OBJECT-TYPE
2614 + SYNTAX Gauge32
2615 + MAX-ACCESS read-only
2616 + STATUS current
2617 + DESCRIPTION
2618 + "The total number of link-state advertisements
2619 + in this area's link-state database, excluding
2620 + AS External LSA's."
2621 + ::= { ospfAreaEntry 7 }
2622 +
2623 +
2624 + ospfAreaLsaCksumSum OBJECT-TYPE
2625 + SYNTAX Integer32
2626 + MAX-ACCESS read-only
2627 + STATUS current
2628 + DESCRIPTION
2629 + "The 32-bit unsigned sum of the link-state ad-
2630 + vertisements' LS checksums contained in this
2631 + area's link-state database. This sum excludes
2632 + external (LS type 5) link-state advertisements.
2633 + The sum can be used to determine if there has
2634 + been a change in a router's link state data-
2635 + base, and to compare the link-state database of
2636 + two routers."
2637 + DEFVAL { 0 }
2638 + ::= { ospfAreaEntry 8 }
2639 +
2640 + ospfAreaSummary OBJECT-TYPE
2641 + SYNTAX INTEGER {
2642 + noAreaSummary (1),
2643 + sendAreaSummary (2)
2644 + }
2645 + MAX-ACCESS read-create
2646 + STATUS current
2647 + DESCRIPTION
2648 + "The variable ospfAreaSummary controls the im-
2649 + port of summary LSAs into stub areas. It has
2650 + no effect on other areas.
2651 +
2652 + If it is noAreaSummary, the router will neither
2653 + originate nor propagate summary LSAs into the
2654 + stub area. It will rely entirely on its de-
2655 + fault route.
2656 +
2657 + If it is sendAreaSummary, the router will both
2658 + summarize and propagate summary LSAs."
2659 + DEFVAL { noAreaSummary }
2660 + ::= { ospfAreaEntry 9 }
2661 +
2662 +
2663 + ospfAreaStatus OBJECT-TYPE
2664 + SYNTAX RowStatus
2665 + MAX-ACCESS read-create
2666 + STATUS current
2667 + DESCRIPTION
2668 + "This variable displays the status of the en-
2669 + try. Setting it to 'invalid' has the effect of
2670 + rendering it inoperative. The internal effect
2671 + (row removal) is implementation dependent."
2672 + ::= { ospfAreaEntry 10 }
2673 +
2674 +
2675 +-- OSPF Area Default Metric Table
2676 +
2677 +-- The OSPF Area Default Metric Table describes the metrics
2678 +-- that a default Area Border Router will advertise into a
2679 +-- Stub area.
2680 +
2681 +
2682 + ospfStubAreaTable OBJECT-TYPE
2683 + SYNTAX SEQUENCE OF OspfStubAreaEntry
2684 + MAX-ACCESS not-accessible
2685 + STATUS current
2686 + DESCRIPTION
2687 + "The set of metrics that will be advertised by
2688 + a default Area Border Router into a stub area."
2689 + REFERENCE
2690 + "OSPF Version 2, Appendix C.2, Area Parameters"
2691 + ::= { ospf 3 }
2692 +
2693 +
2694 + ospfStubAreaEntry OBJECT-TYPE
2695 + SYNTAX OspfStubAreaEntry
2696 + MAX-ACCESS not-accessible
2697 + STATUS current
2698 + DESCRIPTION
2699 + "The metric for a given Type of Service that
2700 + will be advertised by a default Area Border
2701 + Router into a stub area."
2702 + REFERENCE
2703 + "OSPF Version 2, Appendix C.2, Area Parameters"
2704 + INDEX { ospfStubAreaId, ospfStubTOS }
2705 + ::= { ospfStubAreaTable 1 }
2706 +
2707 +OspfStubAreaEntry ::=
2708 + SEQUENCE {
2709 + ospfStubAreaId
2710 + AreaID,
2711 + ospfStubTOS
2712 + TOSType,
2713 + ospfStubMetric
2714 + BigMetric,
2715 + ospfStubStatus
2716 + RowStatus,
2717 + ospfStubMetricType
2718 + INTEGER
2719 + }
2720 +
2721 + ospfStubAreaId OBJECT-TYPE
2722 + SYNTAX AreaID
2723 + MAX-ACCESS read-only
2724 + STATUS current
2725 + DESCRIPTION
2726 + "The 32 bit identifier for the Stub Area. On
2727 + creation, this can be derived from the in-
2728 + stance."
2729 + ::= { ospfStubAreaEntry 1 }
2730 +
2731 +
2732 + ospfStubTOS OBJECT-TYPE
2733 + SYNTAX TOSType
2734 + MAX-ACCESS read-only
2735 + STATUS current
2736 + DESCRIPTION
2737 + "The Type of Service associated with the
2738 + metric. On creation, this can be derived from
2739 + the instance."
2740 + ::= { ospfStubAreaEntry 2 }
2741 +
2742 +
2743 + ospfStubMetric OBJECT-TYPE
2744 + SYNTAX BigMetric
2745 + MAX-ACCESS read-create
2746 + STATUS current
2747 + DESCRIPTION
2748 + "The metric value applied at the indicated type
2749 + of service. By default, this equals the least
2750 + metric at the type of service among the inter-
2751 + faces to other areas."
2752 + ::= { ospfStubAreaEntry 3 }
2753 +
2754 +
2755 + ospfStubStatus OBJECT-TYPE
2756 + SYNTAX RowStatus
2757 + MAX-ACCESS read-create
2758 + STATUS current
2759 + DESCRIPTION
2760 + "This variable displays the status of the en-
2761 + try. Setting it to 'invalid' has the effect of
2762 + rendering it inoperative. The internal effect
2763 + (row removal) is implementation dependent."
2764 + ::= { ospfStubAreaEntry 4 }
2765 +
2766 + ospfStubMetricType OBJECT-TYPE
2767 + SYNTAX INTEGER {
2768 + ospfMetric (1), -- OSPF Metric
2769 + comparableCost (2), -- external type 1
2770 + nonComparable (3) -- external type 2
2771 + }
2772 + MAX-ACCESS read-create
2773 + STATUS current
2774 + DESCRIPTION
2775 + "This variable displays the type of metric ad-
2776 + vertised as a default route."
2777 + DEFVAL { ospfMetric }
2778 + ::= { ospfStubAreaEntry 5 }
2779 +
2780 +-- OSPF Link State Database
2781 +
2782 +-- The Link State Database contains the Link State
2783 +-- Advertisements from throughout the areas that the
2784 +-- device is attached to.
2785 +
2786 +
2787 + ospfLsdbTable OBJECT-TYPE
2788 + SYNTAX SEQUENCE OF OspfLsdbEntry
2789 + MAX-ACCESS not-accessible
2790 + STATUS current
2791 + DESCRIPTION
2792 + "The OSPF Process's Link State Database."
2793 + REFERENCE
2794 + "OSPF Version 2, Section 12 Link State Adver-
2795 + tisements"
2796 + ::= { ospf 4 }
2797 +
2798 +
2799 + ospfLsdbEntry OBJECT-TYPE
2800 + SYNTAX OspfLsdbEntry
2801 + MAX-ACCESS not-accessible
2802 + STATUS current
2803 + DESCRIPTION
2804 + "A single Link State Advertisement."
2805 + INDEX { ospfLsdbAreaId, ospfLsdbType,
2806 + ospfLsdbLsid, ospfLsdbRouterId }
2807 + ::= { ospfLsdbTable 1 }
2808 +
2809 +OspfLsdbEntry ::=
2810 + SEQUENCE {
2811 + ospfLsdbAreaId
2812 + AreaID,
2813 + ospfLsdbType
2814 + INTEGER,
2815 + ospfLsdbLsid
2816 + IpAddress,
2817 + ospfLsdbRouterId
2818 + RouterID,
2819 + ospfLsdbSequence
2820 + Integer32,
2821 + ospfLsdbAge
2822 + Integer32,
2823 + ospfLsdbChecksum
2824 + Integer32,
2825 + ospfLsdbAdvertisement
2826 + OCTET STRING
2827 + }
2828 + ospfLsdbAreaId OBJECT-TYPE
2829 + SYNTAX AreaID
2830 + MAX-ACCESS read-only
2831 + STATUS current
2832 + DESCRIPTION
2833 + "The 32 bit identifier of the Area from which
2834 + the LSA was received."
2835 + REFERENCE
2836 + "OSPF Version 2, Appendix C.2 Area parameters"
2837 + ::= { ospfLsdbEntry 1 }
2838 +
2839 +-- External Link State Advertisements are permitted
2840 +-- for backward compatibility, but should be displayed in
2841 +-- the ospfExtLsdbTable rather than here.
2842 +
2843 + ospfLsdbType OBJECT-TYPE
2844 + SYNTAX INTEGER {
2845 + routerLink (1),
2846 + networkLink (2),
2847 + summaryLink (3),
2848 + asSummaryLink (4),
2849 + asExternalLink (5), -- but see ospfExtLsdbTable
2850 + multicastLink (6),
2851 + nssaExternalLink (7)
2852 + }
2853 + MAX-ACCESS read-only
2854 + STATUS current
2855 + DESCRIPTION
2856 + "The type of the link state advertisement.
2857 + Each link state type has a separate advertise-
2858 + ment format."
2859 + REFERENCE
2860 + "OSPF Version 2, Appendix A.4.1 The Link State
2861 + Advertisement header"
2862 + ::= { ospfLsdbEntry 2 }
2863 +
2864 + ospfLsdbLsid OBJECT-TYPE
2865 + SYNTAX IpAddress
2866 + MAX-ACCESS read-only
2867 + STATUS current
2868 + DESCRIPTION
2869 + "The Link State ID is an LS Type Specific field
2870 + containing either a Router ID or an IP Address;
2871 + it identifies the piece of the routing domain
2872 + that is being described by the advertisement."
2873 + REFERENCE
2874 + "OSPF Version 2, Section 12.1.4 Link State ID"
2875 + ::= { ospfLsdbEntry 3 }
2876 + ospfLsdbRouterId OBJECT-TYPE
2877 + SYNTAX RouterID
2878 + MAX-ACCESS read-only
2879 + STATUS current
2880 + DESCRIPTION
2881 + "The 32 bit number that uniquely identifies the
2882 + originating router in the Autonomous System."
2883 + REFERENCE
2884 + "OSPF Version 2, Appendix C.1 Global parameters"
2885 + ::= { ospfLsdbEntry 4 }
2886 +
2887 +-- Note that the OSPF Sequence Number is a 32 bit signed
2888 +-- integer. It starts with the value '80000001'h,
2889 +-- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h
2890 +-- Thus, a typical sequence number will be very negative.
2891 +
2892 + ospfLsdbSequence OBJECT-TYPE
2893 + SYNTAX Integer32
2894 + MAX-ACCESS read-only
2895 + STATUS current
2896 + DESCRIPTION
2897 + "The sequence number field is a signed 32-bit
2898 + integer. It is used to detect old and dupli-
2899 + cate link state advertisements. The space of
2900 + sequence numbers is linearly ordered. The
2901 + larger the sequence number the more recent the
2902 + advertisement."
2903 + REFERENCE
2904 + "OSPF Version 2, Section 12.1.6 LS sequence
2905 + number"
2906 + ::= { ospfLsdbEntry 5 }
2907 +
2908 +
2909 + ospfLsdbAge OBJECT-TYPE
2910 + SYNTAX Integer32 -- Should be 0..MaxAge
2911 + MAX-ACCESS read-only
2912 + STATUS current
2913 + DESCRIPTION
2914 + "This field is the age of the link state adver-
2915 + tisement in seconds."
2916 + REFERENCE
2917 + "OSPF Version 2, Section 12.1.1 LS age"
2918 + ::= { ospfLsdbEntry 6 }
2919 +
2920 + ospfLsdbChecksum OBJECT-TYPE
2921 + SYNTAX Integer32
2922 + MAX-ACCESS read-only
2923 + STATUS current
2924 + DESCRIPTION
2925 + "This field is the checksum of the complete
2926 + contents of the advertisement, excepting the
2927 + age field. The age field is excepted so that
2928 + an advertisement's age can be incremented
2929 + without updating the checksum. The checksum
2930 + used is the same that is used for ISO connec-
2931 + tionless datagrams; it is commonly referred to
2932 + as the Fletcher checksum."
2933 + REFERENCE
2934 + "OSPF Version 2, Section 12.1.7 LS checksum"
2935 + ::= { ospfLsdbEntry 7 }
2936 +
2937 +
2938 + ospfLsdbAdvertisement OBJECT-TYPE
2939 + SYNTAX OCTET STRING (SIZE (1..65535))
2940 + MAX-ACCESS read-only
2941 + STATUS current
2942 + DESCRIPTION
2943 + "The entire Link State Advertisement, including
2944 + its header."
2945 + REFERENCE
2946 + "OSPF Version 2, Section 12 Link State Adver-
2947 + tisements"
2948 + ::= { ospfLsdbEntry 8 }
2949 +
2950 +
2951 +-- Address Range Table
2952 +
2953 +-- The Address Range Table acts as an adjunct to the Area
2954 +-- Table; It describes those Address Range Summaries that
2955 +-- are configured to be propagated from an Area to reduce
2956 +-- the amount of information about it which is known beyond
2957 +-- its borders.
2958 +
2959 + ospfAreaRangeTable OBJECT-TYPE
2960 + SYNTAX SEQUENCE OF OspfAreaRangeEntry
2961 + MAX-ACCESS not-accessible
2962 + STATUS obsolete
2963 + DESCRIPTION
2964 + "A range if IP addresses specified by an IP
2965 + address/IP network mask pair. For example,
2966 + class B address range of X.X.X.X with a network
2967 + mask of 255.255.0.0 includes all IP addresses
2968 + from X.X.0.0 to X.X.255.255"
2969 + REFERENCE
2970 + "OSPF Version 2, Appendix C.2 Area parameters"
2971 + ::= { ospf 5 }
2972 + ospfAreaRangeEntry OBJECT-TYPE
2973 + SYNTAX OspfAreaRangeEntry
2974 + MAX-ACCESS not-accessible
2975 + STATUS obsolete
2976 + DESCRIPTION
2977 + "A range if IP addresses specified by an IP
2978 + address/IP network mask pair. For example,
2979 + class B address range of X.X.X.X with a network
2980 + mask of 255.255.0.0 includes all IP addresses
2981 + from X.X.0.0 to X.X.255.255"
2982 + REFERENCE
2983 + "OSPF Version 2, Appendix C.2 Area parameters"
2984 + INDEX { ospfAreaRangeAreaId, ospfAreaRangeNet }
2985 + ::= { ospfAreaRangeTable 1 }
2986 +
2987 +OspfAreaRangeEntry ::=
2988 + SEQUENCE {
2989 + ospfAreaRangeAreaId
2990 + AreaID,
2991 + ospfAreaRangeNet
2992 + IpAddress,
2993 + ospfAreaRangeMask
2994 + IpAddress,
2995 + ospfAreaRangeStatus
2996 + RowStatus,
2997 + ospfAreaRangeEffect
2998 + INTEGER
2999 + }
3000 +
3001 + ospfAreaRangeAreaId OBJECT-TYPE
3002 + SYNTAX AreaID
3003 + MAX-ACCESS read-only
3004 + STATUS obsolete
3005 + DESCRIPTION
3006 + "The Area the Address Range is to be found
3007 + within."
3008 + REFERENCE
3009 + "OSPF Version 2, Appendix C.2 Area parameters"
3010 + ::= { ospfAreaRangeEntry 1 }
3011 +
3012 +
3013 + ospfAreaRangeNet OBJECT-TYPE
3014 + SYNTAX IpAddress
3015 + MAX-ACCESS read-only
3016 + STATUS obsolete
3017 + DESCRIPTION
3018 + "The IP Address of the Net or Subnet indicated
3019 + by the range."
3020 + REFERENCE
3021 + "OSPF Version 2, Appendix C.2 Area parameters"
3022 + ::= { ospfAreaRangeEntry 2 }
3023 +
3024 +
3025 + ospfAreaRangeMask OBJECT-TYPE
3026 + SYNTAX IpAddress
3027 + MAX-ACCESS read-create
3028 + STATUS obsolete
3029 + DESCRIPTION
3030 + "The Subnet Mask that pertains to the Net or
3031 + Subnet."
3032 + REFERENCE
3033 + "OSPF Version 2, Appendix C.2 Area parameters"
3034 + ::= { ospfAreaRangeEntry 3 }
3035 +
3036 + ospfAreaRangeStatus OBJECT-TYPE
3037 + SYNTAX RowStatus
3038 + MAX-ACCESS read-create
3039 + STATUS obsolete
3040 + DESCRIPTION
3041 + "This variable displays the status of the en-
3042 + try. Setting it to 'invalid' has the effect of
3043 + rendering it inoperative. The internal effect
3044 + (row removal) is implementation dependent."
3045 + ::= { ospfAreaRangeEntry 4 }
3046 +
3047 +
3048 + ospfAreaRangeEffect OBJECT-TYPE
3049 + SYNTAX INTEGER {
3050 + advertiseMatching (1),
3051 + doNotAdvertiseMatching (2)
3052 + }
3053 + MAX-ACCESS read-create
3054 + STATUS obsolete
3055 + DESCRIPTION
3056 + "Subnets subsumed by ranges either trigger the
3057 + advertisement of the indicated summary (adver-
3058 + tiseMatching), or result in the subnet's not
3059 + being advertised at all outside the area."
3060 + DEFVAL { advertiseMatching }
3061 + ::= { ospfAreaRangeEntry 5 }
3062 +
3063 +
3064 +
3065 +-- OSPF Host Table
3066 +
3067 +-- The Host/Metric Table indicates what hosts are directly
3068 +-- attached to the Router, and what metrics and types of
3069 +-- service should be advertised for them.
3070 +
3071 + ospfHostTable OBJECT-TYPE
3072 + SYNTAX SEQUENCE OF OspfHostEntry
3073 + MAX-ACCESS not-accessible
3074 + STATUS current
3075 + DESCRIPTION
3076 + "The list of Hosts, and their metrics, that the
3077 + router will advertise as host routes."
3078 + REFERENCE
3079 + "OSPF Version 2, Appendix C.6 Host route param-
3080 + eters"
3081 + ::= { ospf 6 }
3082 +
3083 +
3084 + ospfHostEntry OBJECT-TYPE
3085 + SYNTAX OspfHostEntry
3086 + MAX-ACCESS not-accessible
3087 + STATUS current
3088 + DESCRIPTION
3089 + "A metric to be advertised, for a given type of
3090 + service, when a given host is reachable."
3091 + INDEX { ospfHostIpAddress, ospfHostTOS }
3092 + ::= { ospfHostTable 1 }
3093 +
3094 +OspfHostEntry ::=
3095 + SEQUENCE {
3096 + ospfHostIpAddress
3097 + IpAddress,
3098 + ospfHostTOS
3099 + TOSType,
3100 + ospfHostMetric
3101 + Metric,
3102 + ospfHostStatus
3103 + RowStatus,
3104 + ospfHostAreaID
3105 + AreaID
3106 + }
3107 +
3108 + ospfHostIpAddress OBJECT-TYPE
3109 + SYNTAX IpAddress
3110 + MAX-ACCESS read-only
3111 + STATUS current
3112 + DESCRIPTION
3113 + "The IP Address of the Host."
3114 + REFERENCE
3115 + "OSPF Version 2, Appendix C.6 Host route parame-
3116 + ters"
3117 + ::= { ospfHostEntry 1 }
3118 +
3119 +
3120 + ospfHostTOS OBJECT-TYPE
3121 + SYNTAX TOSType
3122 + MAX-ACCESS read-only
3123 + STATUS current
3124 + DESCRIPTION
3125 + "The Type of Service of the route being config-
3126 + ured."
3127 + REFERENCE
3128 + "OSPF Version 2, Appendix C.6 Host route parame-
3129 + ters"
3130 + ::= { ospfHostEntry 2 }
3131 +
3132 +
3133 + ospfHostMetric OBJECT-TYPE
3134 + SYNTAX Metric
3135 + MAX-ACCESS read-create
3136 + STATUS current
3137 + DESCRIPTION
3138 + "The Metric to be advertised."
3139 + REFERENCE
3140 + "OSPF Version 2, Appendix C.6 Host route parame-
3141 + ters"
3142 + ::= { ospfHostEntry 3 }
3143 +
3144 + ospfHostStatus OBJECT-TYPE
3145 + SYNTAX RowStatus
3146 + MAX-ACCESS read-create
3147 + STATUS current
3148 + DESCRIPTION
3149 + "This variable displays the status of the en-
3150 + try. Setting it to 'invalid' has the effect of
3151 + rendering it inoperative. The internal effect
3152 + (row removal) is implementation dependent."
3153 + ::= { ospfHostEntry 4 }
3154 +
3155 +
3156 + ospfHostAreaID OBJECT-TYPE
3157 + SYNTAX AreaID
3158 + MAX-ACCESS read-only
3159 + STATUS current
3160 + DESCRIPTION
3161 + "The Area the Host Entry is to be found within.
3162 + By default, the area that a subsuming OSPF in-
3163 + terface is in, or 0.0.0.0"
3164 + REFERENCE
3165 + "OSPF Version 2, Appendix C.2 Area parameters"
3166 + ::= { ospfHostEntry 5 }
3167 +
3168 +
3169 +-- OSPF Interface Table
3170 +
3171 +-- The OSPF Interface Table augments the ipAddrTable
3172 +-- with OSPF specific information.
3173 +
3174 + ospfIfTable OBJECT-TYPE
3175 + SYNTAX SEQUENCE OF OspfIfEntry
3176 + MAX-ACCESS not-accessible
3177 + STATUS current
3178 + DESCRIPTION
3179 + "The OSPF Interface Table describes the inter-
3180 + faces from the viewpoint of OSPF."
3181 + REFERENCE
3182 + "OSPF Version 2, Appendix C.3 Router interface
3183 + parameters"
3184 + ::= { ospf 7 }
3185 +
3186 +
3187 + ospfIfEntry OBJECT-TYPE
3188 + SYNTAX OspfIfEntry
3189 + MAX-ACCESS not-accessible
3190 + STATUS current
3191 + DESCRIPTION
3192 + "The OSPF Interface Entry describes one inter-
3193 + face from the viewpoint of OSPF."
3194 + INDEX { ospfIfIpAddress, ospfAddressLessIf }
3195 + ::= { ospfIfTable 1 }
3196 +
3197 +OspfIfEntry ::=
3198 + SEQUENCE {
3199 + ospfIfIpAddress
3200 + IpAddress,
3201 + ospfAddressLessIf
3202 + Integer32,
3203 + ospfIfAreaId
3204 + AreaID,
3205 + ospfIfType
3206 + INTEGER,
3207 + ospfIfAdminStat
3208 + Status,
3209 + ospfIfRtrPriority
3210 + DesignatedRouterPriority,
3211 + ospfIfTransitDelay
3212 + UpToMaxAge,
3213 + ospfIfRetransInterval
3214 + UpToMaxAge,
3215 + ospfIfHelloInterval
3216 + HelloRange,
3217 + ospfIfRtrDeadInterval
3218 + PositiveInteger,
3219 + ospfIfPollInterval
3220 + PositiveInteger,
3221 + ospfIfState
3222 + INTEGER,
3223 + ospfIfDesignatedRouter
3224 + IpAddress,
3225 + ospfIfBackupDesignatedRouter
3226 + IpAddress,
3227 + ospfIfEvents
3228 + Counter32,
3229 + ospfIfAuthType
3230 + INTEGER,
3231 + ospfIfAuthKey
3232 + OCTET STRING,
3233 + ospfIfStatus
3234 + RowStatus,
3235 + ospfIfMulticastForwarding
3236 + INTEGER,
3237 + ospfIfDemand
3238 + TruthValue
3239 + }
3240 +
3241 + ospfIfIpAddress OBJECT-TYPE
3242 + SYNTAX IpAddress
3243 + MAX-ACCESS read-only
3244 + STATUS current
3245 + DESCRIPTION
3246 + "The IP address of this OSPF interface."
3247 + ::= { ospfIfEntry 1 }
3248 +
3249 + ospfAddressLessIf OBJECT-TYPE
3250 + SYNTAX Integer32
3251 + MAX-ACCESS read-only
3252 + STATUS current
3253 + DESCRIPTION
3254 + "For the purpose of easing the instancing of
3255 + addressed and addressless interfaces; This
3256 + variable takes the value 0 on interfaces with
3257 + IP Addresses, and the corresponding value of
3258 + ifIndex for interfaces having no IP Address."
3259 + ::= { ospfIfEntry 2 }
3260 + ospfIfAreaId OBJECT-TYPE
3261 + SYNTAX AreaID
3262 + MAX-ACCESS read-create
3263 + STATUS current
3264 + DESCRIPTION
3265 + "A 32-bit integer uniquely identifying the area
3266 + to which the interface connects. Area ID
3267 + 0.0.0.0 is used for the OSPF backbone."
3268 + DEFVAL { '00000000'H } -- 0.0.0.0
3269 + ::= { ospfIfEntry 3 }
3270 +
3271 + ospfIfType OBJECT-TYPE
3272 + SYNTAX INTEGER {
3273 + broadcast (1),
3274 + nbma (2),
3275 + pointToPoint (3),
3276 + pointToMultipoint (5)
3277 + }
3278 + MAX-ACCESS read-create
3279 + STATUS current
3280 + DESCRIPTION
3281 + "The OSPF interface type.
3282 +
3283 + By way of a default, this field may be intuited
3284 + from the corresponding value of ifType. Broad-
3285 + cast LANs, such as Ethernet and IEEE 802.5,
3286 + take the value 'broadcast', X.25 and similar
3287 + technologies take the value 'nbma', and links
3288 + that are definitively point to point take the
3289 + value 'pointToPoint'."
3290 + ::= { ospfIfEntry 4 }
3291 +
3292 +
3293 + ospfIfAdminStat OBJECT-TYPE
3294 + SYNTAX Status
3295 + MAX-ACCESS read-create
3296 + STATUS current
3297 + DESCRIPTION
3298 + "The OSPF interface's administrative status.
3299 + The value formed on the interface, and the in-
3300 + terface will be advertised as an internal route
3301 + to some area. The value 'disabled' denotes
3302 + that the interface is external to OSPF."
3303 + DEFVAL { enabled }
3304 + ::= { ospfIfEntry 5 }
3305 +
3306 + ospfIfRtrPriority OBJECT-TYPE
3307 + SYNTAX DesignatedRouterPriority
3308 + MAX-ACCESS read-create
3309 + STATUS current
3310 + DESCRIPTION
3311 + "The priority of this interface. Used in
3312 + multi-access networks, this field is used in
3313 + the designated router election algorithm. The
3314 + value 0 signifies that the router is not eligi-
3315 + ble to become the designated router on this
3316 + particular network. In the event of a tie in
3317 + this value, routers will use their Router ID as
3318 + a tie breaker."
3319 + DEFVAL { 1 }
3320 + ::= { ospfIfEntry 6 }
3321 +
3322 +
3323 + ospfIfTransitDelay OBJECT-TYPE
3324 + SYNTAX UpToMaxAge
3325 + MAX-ACCESS read-create
3326 + STATUS current
3327 + DESCRIPTION
3328 + "The estimated number of seconds it takes to
3329 + transmit a link state update packet over this
3330 + interface."
3331 + DEFVAL { 1 }
3332 + ::= { ospfIfEntry 7 }
3333 +
3334 +
3335 + ospfIfRetransInterval OBJECT-TYPE
3336 + SYNTAX UpToMaxAge
3337 + MAX-ACCESS read-create
3338 + STATUS current
3339 + DESCRIPTION
3340 + "The number of seconds between link-state ad-
3341 + vertisement retransmissions, for adjacencies
3342 + belonging to this interface. This value is
3343 + also used when retransmitting database descrip-
3344 + tion and link-state request packets."
3345 + DEFVAL { 5 }
3346 + ::= { ospfIfEntry 8 }
3347 +
3348 +
3349 + ospfIfHelloInterval OBJECT-TYPE
3350 + SYNTAX HelloRange
3351 + MAX-ACCESS read-create
3352 + STATUS current
3353 + DESCRIPTION
3354 + "The length of time, in seconds, between the
3355 + Hello packets that the router sends on the in-
3356 + terface. This value must be the same for all
3357 + routers attached to a common network."
3358 + DEFVAL { 10 }
3359 + ::= { ospfIfEntry 9 }
3360 +
3361 +
3362 + ospfIfRtrDeadInterval OBJECT-TYPE
3363 + SYNTAX PositiveInteger
3364 + MAX-ACCESS read-create
3365 + STATUS current
3366 + DESCRIPTION
3367 + "The number of seconds that a router's Hello
3368 + packets have not been seen before it's neigh-
3369 + bors declare the router down. This should be
3370 + some multiple of the Hello interval. This
3371 + value must be the same for all routers attached
3372 + to a common network."
3373 + DEFVAL { 40 }
3374 + ::= { ospfIfEntry 10 }
3375 +
3376 +
3377 + ospfIfPollInterval OBJECT-TYPE
3378 + SYNTAX PositiveInteger
3379 + MAX-ACCESS read-create
3380 + STATUS current
3381 + DESCRIPTION
3382 + "The larger time interval, in seconds, between
3383 + the Hello packets sent to an inactive non-
3384 + broadcast multi- access neighbor."
3385 + DEFVAL { 120 }
3386 + ::= { ospfIfEntry 11 }
3387 +
3388 +
3389 + ospfIfState OBJECT-TYPE
3390 + SYNTAX INTEGER {
3391 + down (1),
3392 + loopback (2),
3393 + waiting (3),
3394 + pointToPoint (4),
3395 + designatedRouter (5),
3396 + backupDesignatedRouter (6),
3397 + otherDesignatedRouter (7)
3398 + }
3399 + MAX-ACCESS read-only
3400 + STATUS current
3401 + DESCRIPTION
3402 + "The OSPF Interface State."
3403 + DEFVAL { down }
3404 + ::= { ospfIfEntry 12 }
3405 +
3406 +
3407 + ospfIfDesignatedRouter OBJECT-TYPE
3408 + SYNTAX IpAddress
3409 + MAX-ACCESS read-only
3410 + STATUS current
3411 + DESCRIPTION
3412 + "The IP Address of the Designated Router."
3413 + DEFVAL { '00000000'H } -- 0.0.0.0
3414 + ::= { ospfIfEntry 13 }
3415 +
3416 +
3417 + ospfIfBackupDesignatedRouter OBJECT-TYPE
3418 + SYNTAX IpAddress
3419 + MAX-ACCESS read-only
3420 + STATUS current
3421 + DESCRIPTION
3422 + "The IP Address of the Backup Designated
3423 + Router."
3424 + DEFVAL { '00000000'H } -- 0.0.0.0
3425 + ::= { ospfIfEntry 14 }
3426 +
3427 + ospfIfEvents OBJECT-TYPE
3428 + SYNTAX Counter32
3429 + MAX-ACCESS read-only
3430 + STATUS current
3431 + DESCRIPTION
3432 + "The number of times this OSPF interface has
3433 + changed its state, or an error has occurred."
3434 + ::= { ospfIfEntry 15 }
3435 +
3436 +
3437 + ospfIfAuthKey OBJECT-TYPE
3438 + SYNTAX OCTET STRING (SIZE (0..256))
3439 + MAX-ACCESS read-create
3440 + STATUS current
3441 + DESCRIPTION
3442 + "The Authentication Key. If the Area's Author-
3443 + ization Type is simplePassword, and the key
3444 + length is shorter than 8 octets, the agent will
3445 + left adjust and zero fill to 8 octets.
3446 +
3447 + Note that unauthenticated interfaces need no
3448 + authentication key, and simple password authen-
3449 + tication cannot use a key of more than 8 oc-
3450 + tets. Larger keys are useful only with authen-
3451 + tication mechanisms not specified in this docu-
3452 + ment.
3453 +
3454 + When read, ospfIfAuthKey always returns an Oc-
3455 + tet String of length zero."
3456 + REFERENCE
3457 + "OSPF Version 2, Section 9 The Interface Data
3458 + Structure"
3459 + DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0
3460 + ::= { ospfIfEntry 16 }
3461 +
3462 + ospfIfStatus OBJECT-TYPE
3463 + SYNTAX RowStatus
3464 + MAX-ACCESS read-create
3465 + STATUS current
3466 + DESCRIPTION
3467 + "This variable displays the status of the en-
3468 + try. Setting it to 'invalid' has the effect of
3469 + rendering it inoperative. The internal effect
3470 + (row removal) is implementation dependent."
3471 + ::= { ospfIfEntry 17 }
3472 +
3473 +
3474 + ospfIfMulticastForwarding OBJECT-TYPE
3475 + SYNTAX INTEGER {
3476 + blocked (1), -- no multicast forwarding
3477 + multicast (2), -- using multicast address
3478 + unicast (3) -- to each OSPF neighbor
3479 + }
3480 + MAX-ACCESS read-create
3481 + STATUS current
3482 + DESCRIPTION
3483 + "The way multicasts should forwarded on this
3484 + interface; not forwarded, forwarded as data
3485 + link multicasts, or forwarded as data link uni-
3486 + casts. Data link multicasting is not meaning-
3487 + ful on point to point and NBMA interfaces, and
3488 + setting ospfMulticastForwarding to 0 effective-
3489 + ly disables all multicast forwarding."
3490 + DEFVAL { blocked }
3491 + ::= { ospfIfEntry 18 }
3492 +
3493 +
3494 + ospfIfDemand OBJECT-TYPE
3495 + SYNTAX TruthValue
3496 + MAX-ACCESS read-create
3497 + STATUS current
3498 + DESCRIPTION
3499 + "Indicates whether Demand OSPF procedures (hel-
3500 + lo supression to FULL neighbors and setting the
3501 + DoNotAge flag on proogated LSAs) should be per-
3502 + formed on this interface."
3503 + DEFVAL { false }
3504 + ::= { ospfIfEntry 19 }
3505 +
3506 +
3507 + ospfIfAuthType OBJECT-TYPE
3508 + SYNTAX INTEGER (0..255)
3509 + -- none (0),
3510 + -- simplePassword (1)
3511 + -- md5 (2)
3512 + -- reserved for specification by IANA (> 2)
3513 + MAX-ACCESS read-create
3514 + STATUS current
3515 + DESCRIPTION
3516 + "The authentication type specified for an in-
3517 + terface. Additional authentication types may
3518 + be assigned locally."
3519 + REFERENCE
3520 + "OSPF Version 2, Appendix E Authentication"
3521 + DEFVAL { 0 } -- no authentication, by default
3522 + ::= { ospfIfEntry 20 }
3523 +
3524 +
3525 +-- OSPF Interface Metric Table
3526 +
3527 +-- The Metric Table describes the metrics to be advertised
3528 +-- for a specified interface at the various types of service.
3529 +-- As such, this table is an adjunct of the OSPF Interface
3530 +-- Table.
3531 +
3532 +-- Types of service, as defined by RFC 791, have the ability
3533 +-- to request low delay, high bandwidth, or reliable linkage.
3534 +
3535 +-- For the purposes of this specification, the measure of
3536 +-- bandwidth
3537 +
3538 +-- Metric = 10^8 / ifSpeed
3539 +
3540 +-- is the default value. For multiple link interfaces, note
3541 +-- that ifSpeed is the sum of the individual link speeds.
3542 +-- This yields a number having the following typical values:
3543 +
3544 +-- Network Type/bit rate Metric
3545 +
3546 +-- >= 100 MBPS 1
3547 +-- Ethernet/802.3 10
3548 +-- E1 48
3549 +-- T1 (ESF) 65
3550 +-- 64 KBPS 1562
3551 +-- 56 KBPS 1785
3552 +-- 19.2 KBPS 5208
3553 +-- 9.6 KBPS 10416
3554 +
3555 +-- Routes that are not specified use the default (TOS 0) metric
3556 +
3557 + ospfIfMetricTable OBJECT-TYPE
3558 + SYNTAX SEQUENCE OF OspfIfMetricEntry
3559 + MAX-ACCESS not-accessible
3560 + STATUS current
3561 + DESCRIPTION
3562 + "The TOS metrics for a non-virtual interface
3563 + identified by the interface index."
3564 + REFERENCE
3565 + "OSPF Version 2, Appendix C.3 Router interface
3566 + parameters"
3567 + ::= { ospf 8 }
3568 +
3569 + ospfIfMetricEntry OBJECT-TYPE
3570 + SYNTAX OspfIfMetricEntry
3571 + MAX-ACCESS not-accessible
3572 + STATUS current
3573 + DESCRIPTION
3574 + "A particular TOS metric for a non-virtual in-
3575 + terface identified by the interface index."
3576 + REFERENCE
3577 + "OSPF Version 2, Appendix C.3 Router interface
3578 + parameters"
3579 + INDEX { ospfIfMetricIpAddress,
3580 + ospfIfMetricAddressLessIf,
3581 + ospfIfMetricTOS }
3582 + ::= { ospfIfMetricTable 1 }
3583 +
3584 +OspfIfMetricEntry ::=
3585 + SEQUENCE {
3586 + ospfIfMetricIpAddress
3587 + IpAddress,
3588 + ospfIfMetricAddressLessIf
3589 + Integer32,
3590 + ospfIfMetricTOS
3591 + TOSType,
3592 + ospfIfMetricValue
3593 + Metric,
3594 + ospfIfMetricStatus
3595 + RowStatus
3596 + }
3597 +
3598 + ospfIfMetricIpAddress OBJECT-TYPE
3599 + SYNTAX IpAddress
3600 + MAX-ACCESS read-only
3601 + STATUS current
3602 + DESCRIPTION
3603 + "The IP address of this OSPF interface. On row
3604 + creation, this can be derived from the in-
3605 + stance."
3606 + ::= { ospfIfMetricEntry 1 }
3607 +
3608 + ospfIfMetricAddressLessIf OBJECT-TYPE
3609 + SYNTAX Integer32
3610 + MAX-ACCESS read-only
3611 + STATUS current
3612 + DESCRIPTION
3613 + "For the purpose of easing the instancing of
3614 + addressed and addressless interfaces; This
3615 + variable takes the value 0 on interfaces with
3616 + IP Addresses, and the value of ifIndex for in-
3617 + terfaces having no IP Address. On row crea-
3618 + tion, this can be derived from the instance."
3619 + ::= { ospfIfMetricEntry 2 }
3620 +
3621 +
3622 + ospfIfMetricTOS OBJECT-TYPE
3623 + SYNTAX TOSType
3624 + MAX-ACCESS read-only
3625 + STATUS current
3626 + DESCRIPTION
3627 + "The type of service metric being referenced.
3628 + On row creation, this can be derived from the
3629 + instance."
3630 + ::= { ospfIfMetricEntry 3 }
3631 +
3632 +
3633 + ospfIfMetricValue OBJECT-TYPE
3634 + SYNTAX Metric
3635 + MAX-ACCESS read-create
3636 + STATUS current
3637 + DESCRIPTION
3638 + "The metric of using this type of service on
3639 + this interface. The default value of the TOS 0
3640 + Metric is 10^8 / ifSpeed."
3641 + ::= { ospfIfMetricEntry 4 }
3642 +
3643 + ospfIfMetricStatus OBJECT-TYPE
3644 + SYNTAX RowStatus
3645 + MAX-ACCESS read-create
3646 + STATUS current
3647 + DESCRIPTION
3648 + "This variable displays the status of the en-
3649 + try. Setting it to 'invalid' has the effect of
3650 + rendering it inoperative. The internal effect
3651 + (row removal) is implementation dependent."
3652 + ::= { ospfIfMetricEntry 5 }
3653 +
3654 +
3655 +-- OSPF Virtual Interface Table
3656 +
3657 +-- The Virtual Interface Table describes the virtual
3658 +-- links that the OSPF Process is configured to
3659 +-- carry on.
3660 +
3661 + ospfVirtIfTable OBJECT-TYPE
3662 + SYNTAX SEQUENCE OF OspfVirtIfEntry
3663 + MAX-ACCESS not-accessible
3664 + STATUS current
3665 + DESCRIPTION
3666 + "Information about this router's virtual inter-
3667 + faces."
3668 + REFERENCE
3669 + "OSPF Version 2, Appendix C.4 Virtual link
3670 + parameters"
3671 + ::= { ospf 9 }
3672 +
3673 +
3674 + ospfVirtIfEntry OBJECT-TYPE
3675 + SYNTAX OspfVirtIfEntry
3676 + MAX-ACCESS not-accessible
3677 + STATUS current
3678 + DESCRIPTION
3679 + "Information about a single Virtual Interface."
3680 + INDEX { ospfVirtIfAreaId, ospfVirtIfNeighbor }
3681 + ::= { ospfVirtIfTable 1 }
3682 +
3683 +OspfVirtIfEntry ::=
3684 + SEQUENCE {
3685 + ospfVirtIfAreaId
3686 + AreaID,
3687 + ospfVirtIfNeighbor
3688 + RouterID,
3689 + ospfVirtIfTransitDelay
3690 + UpToMaxAge,
3691 + ospfVirtIfRetransInterval
3692 + UpToMaxAge,
3693 + ospfVirtIfHelloInterval
3694 + HelloRange,
3695 + ospfVirtIfRtrDeadInterval
3696 + PositiveInteger,
3697 + ospfVirtIfState
3698 + INTEGER,
3699 + ospfVirtIfEvents
3700 + Counter32,
3701 + ospfVirtIfAuthType
3702 + INTEGER,
3703 + ospfVirtIfAuthKey
3704 + OCTET STRING,
3705 + ospfVirtIfStatus
3706 + RowStatus
3707 + }
3708 +
3709 + ospfVirtIfAreaId OBJECT-TYPE
3710 + SYNTAX AreaID
3711 + MAX-ACCESS read-only
3712 + STATUS current
3713 + DESCRIPTION
3714 + "The Transit Area that the Virtual Link
3715 + traverses. By definition, this is not 0.0.0.0"
3716 + ::= { ospfVirtIfEntry 1 }
3717 +
3718 +
3719 + ospfVirtIfNeighbor OBJECT-TYPE
3720 + SYNTAX RouterID
3721 + MAX-ACCESS read-only
3722 + STATUS current
3723 + DESCRIPTION
3724 + "The Router ID of the Virtual Neighbor."
3725 + ::= { ospfVirtIfEntry 2 }
3726 +
3727 +
3728 + ospfVirtIfTransitDelay OBJECT-TYPE
3729 + SYNTAX UpToMaxAge
3730 + MAX-ACCESS read-create
3731 + STATUS current
3732 + DESCRIPTION
3733 + "The estimated number of seconds it takes to
3734 + transmit a link- state update packet over this
3735 + interface."
3736 + DEFVAL { 1 }
3737 + ::= { ospfVirtIfEntry 3 }
3738 +
3739 +
3740 + ospfVirtIfRetransInterval OBJECT-TYPE
3741 + SYNTAX UpToMaxAge
3742 + MAX-ACCESS read-create
3743 + STATUS current
3744 + DESCRIPTION
3745 + "The number of seconds between link-state ad-
3746 + vertisement retransmissions, for adjacencies
3747 + belonging to this interface. This value is
3748 + also used when retransmitting database descrip-
3749 + tion and link-state request packets. This
3750 + value should be well over the expected round-
3751 + trip time."
3752 + DEFVAL { 5 }
3753 + ::= { ospfVirtIfEntry 4 }
3754 +
3755 +
3756 + ospfVirtIfHelloInterval OBJECT-TYPE
3757 + SYNTAX HelloRange
3758 + MAX-ACCESS read-create
3759 + STATUS current
3760 + DESCRIPTION
3761 + "The length of time, in seconds, between the
3762 + Hello packets that the router sends on the in-
3763 + terface. This value must be the same for the
3764 + virtual neighbor."
3765 + DEFVAL { 10 }
3766 + ::= { ospfVirtIfEntry 5 }
3767 +
3768 +
3769 + ospfVirtIfRtrDeadInterval OBJECT-TYPE
3770 + SYNTAX PositiveInteger
3771 + MAX-ACCESS read-create
3772 + STATUS current
3773 + DESCRIPTION
3774 + "The number of seconds that a router's Hello
3775 + packets have not been seen before it's neigh-
3776 + bors declare the router down. This should be
3777 + some multiple of the Hello interval. This
3778 + value must be the same for the virtual neigh-
3779 + bor."
3780 + DEFVAL { 60 }
3781 + ::= { ospfVirtIfEntry 6 }
3782 +
3783 +
3784 + ospfVirtIfState OBJECT-TYPE
3785 + SYNTAX INTEGER {
3786 + down (1), -- these use the same encoding
3787 + pointToPoint (4) -- as the ospfIfTable
3788 + }
3789 + MAX-ACCESS read-only
3790 + STATUS current
3791 + DESCRIPTION
3792 + "OSPF virtual interface states."
3793 + DEFVAL { down }
3794 + ::= { ospfVirtIfEntry 7 }
3795 +
3796 +
3797 + ospfVirtIfEvents OBJECT-TYPE
3798 + SYNTAX Counter32
3799 + MAX-ACCESS read-only
3800 + STATUS current
3801 + DESCRIPTION
3802 + "The number of state changes or error events on
3803 + this Virtual Link"
3804 + ::= { ospfVirtIfEntry 8 }
3805 +
3806 +
3807 + ospfVirtIfAuthKey OBJECT-TYPE
3808 + SYNTAX OCTET STRING (SIZE(0..256))
3809 + MAX-ACCESS read-create
3810 + STATUS current
3811 + DESCRIPTION
3812 + "If Authentication Type is simplePassword, the
3813 + device will left adjust and zero fill to 8 oc-
3814 + tets.
3815 +
3816 + Note that unauthenticated interfaces need no
3817 + authentication key, and simple password authen-
3818 + tication cannot use a key of more than 8 oc-
3819 + tets. Larger keys are useful only with authen-
3820 + tication mechanisms not specified in this docu-
3821 + ment.
3822 +
3823 + When read, ospfVifAuthKey always returns a
3824 + string of length zero."
3825 + REFERENCE
3826 + "OSPF Version 2, Section 9 The Interface Data
3827 + Structure"
3828 + DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0
3829 + ::= { ospfVirtIfEntry 9 }
3830 +
3831 +
3832 + ospfVirtIfStatus OBJECT-TYPE
3833 + SYNTAX RowStatus
3834 + MAX-ACCESS read-create
3835 + STATUS current
3836 + DESCRIPTION
3837 + "This variable displays the status of the en-
3838 + try. Setting it to 'invalid' has the effect of
3839 + rendering it inoperative. The internal effect
3840 + (row removal) is implementation dependent."
3841 + ::= { ospfVirtIfEntry 10 }
3842 +
3843 +
3844 + ospfVirtIfAuthType OBJECT-TYPE
3845 + SYNTAX INTEGER (0..255)
3846 + -- none (0),
3847 + -- simplePassword (1)
3848 + -- md5 (2)
3849 + -- reserved for specification by IANA (> 2)
3850 + MAX-ACCESS read-create
3851 + STATUS current
3852 + DESCRIPTION
3853 + "The authentication type specified for a virtu-
3854 + al interface. Additional authentication types
3855 + may be assigned locally."
3856 + REFERENCE
3857 + "OSPF Version 2, Appendix E Authentication"
3858 + DEFVAL { 0 } -- no authentication, by default
3859 + ::= { ospfVirtIfEntry 11 }
3860 +
3861 +
3862 +-- OSPF Neighbor Table
3863 +
3864 +-- The OSPF Neighbor Table describes all neighbors in
3865 +-- the locality of the subject router.
3866 +
3867 + ospfNbrTable OBJECT-TYPE
3868 + SYNTAX SEQUENCE OF OspfNbrEntry
3869 + MAX-ACCESS not-accessible
3870 + STATUS current
3871 + DESCRIPTION
3872 + "A table of non-virtual neighbor information."
3873 + REFERENCE
3874 + "OSPF Version 2, Section 10 The Neighbor Data
3875 + Structure"
3876 + ::= { ospf 10 }
3877 +
3878 +
3879 + ospfNbrEntry OBJECT-TYPE
3880 + SYNTAX OspfNbrEntry
3881 + MAX-ACCESS not-accessible
3882 + STATUS current
3883 + DESCRIPTION
3884 + "The information regarding a single neighbor."
3885 + REFERENCE
3886 + "OSPF Version 2, Section 10 The Neighbor Data
3887 + Structure"
3888 + INDEX { ospfNbrIpAddr, ospfNbrAddressLessIndex }
3889 + ::= { ospfNbrTable 1 }
3890 +
3891 +OspfNbrEntry ::=
3892 + SEQUENCE {
3893 + ospfNbrIpAddr
3894 + IpAddress,
3895 + ospfNbrAddressLessIndex
3896 + InterfaceIndex,
3897 + ospfNbrRtrId
3898 + RouterID,
3899 + ospfNbrOptions
3900 + Integer32,
3901 + ospfNbrPriority
3902 + DesignatedRouterPriority,
3903 + ospfNbrState
3904 + INTEGER,
3905 + ospfNbrEvents
3906 + Counter32,
3907 + ospfNbrLsRetransQLen
3908 + Gauge32,
3909 + ospfNbmaNbrStatus
3910 + RowStatus,
3911 + ospfNbmaNbrPermanence
3912 + INTEGER,
3913 + ospfNbrHelloSuppressed
3914 + TruthValue
3915 + }
3916 +
3917 + ospfNbrIpAddr OBJECT-TYPE
3918 + SYNTAX IpAddress
3919 + MAX-ACCESS read-only
3920 + STATUS current
3921 + DESCRIPTION
3922 + "The IP address this neighbor is using in its
3923 + IP Source Address. Note that, on addressless
3924 + links, this will not be 0.0.0.0, but the ad-
3925 + dress of another of the neighbor's interfaces."
3926 + ::= { ospfNbrEntry 1 }
3927 +
3928 +
3929 + ospfNbrAddressLessIndex OBJECT-TYPE
3930 + SYNTAX InterfaceIndex
3931 + MAX-ACCESS read-only
3932 + STATUS current
3933 + DESCRIPTION
3934 + "On an interface having an IP Address, zero.
3935 + On addressless interfaces, the corresponding
3936 + value of ifIndex in the Internet Standard MIB.
3937 + On row creation, this can be derived from the
3938 + instance."
3939 + ::= { ospfNbrEntry 2 }
3940 +
3941 +
3942 + ospfNbrRtrId OBJECT-TYPE
3943 + SYNTAX RouterID
3944 + MAX-ACCESS read-only
3945 + STATUS current
3946 + DESCRIPTION
3947 + "A 32-bit integer (represented as a type IpAd-
3948 + dress) uniquely identifying the neighboring
3949 + router in the Autonomous System."
3950 + DEFVAL { '00000000'H } -- 0.0.0.0
3951 + ::= { ospfNbrEntry 3 }
3952 +
3953 +
3954 + ospfNbrOptions OBJECT-TYPE
3955 + SYNTAX Integer32
3956 + MAX-ACCESS read-only
3957 + STATUS current
3958 + DESCRIPTION
3959 + "A Bit Mask corresponding to the neighbor's op-
3960 + tions field.
3961 +
3962 + Bit 0, if set, indicates that the system will
3963 + operate on Type of Service metrics other than
3964 + TOS 0. If zero, the neighbor will ignore all
3965 + metrics except the TOS 0 metric.
3966 +
3967 + Bit 1, if set, indicates that the associated
3968 + area accepts and operates on external informa-
3969 + tion; if zero, it is a stub area.
3970 +
3971 + Bit 2, if set, indicates that the system is ca-
3972 + pable of routing IP Multicast datagrams; i.e.,
3973 + that it implements the Multicast Extensions to
3974 + OSPF.
3975 +
3976 + Bit 3, if set, indicates that the associated
3977 + area is an NSSA. These areas are capable of
3978 + carrying type 7 external advertisements, which
3979 + are translated into type 5 external advertise-
3980 + ments at NSSA borders."
3981 + REFERENCE
3982 + "OSPF Version 2, Section 12.1.2 Options"
3983 + DEFVAL { 0 }
3984 + ::= { ospfNbrEntry 4 }
3985 +
3986 +
3987 + ospfNbrPriority OBJECT-TYPE
3988 + SYNTAX DesignatedRouterPriority
3989 + MAX-ACCESS read-create
3990 + STATUS current
3991 + DESCRIPTION
3992 + "The priority of this neighbor in the designat-
3993 + ed router election algorithm. The value 0 sig-
3994 + nifies that the neighbor is not eligible to be-
3995 + come the designated router on this particular
3996 + network."
3997 + DEFVAL { 1 }
3998 + ::= { ospfNbrEntry 5 }
3999 +
4000 +
4001 + ospfNbrState OBJECT-TYPE
4002 + SYNTAX INTEGER {
4003 + down (1),
4004 + attempt (2),
4005 + init (3),
4006 + twoWay (4),
4007 + exchangeStart (5),
4008 + exchange (6),
4009 + loading (7),
4010 + full (8)
4011 + }
4012 + MAX-ACCESS read-only
4013 + STATUS current
4014 + DESCRIPTION
4015 + "The State of the relationship with this Neigh-
4016 + bor."
4017 + REFERENCE
4018 + "OSPF Version 2, Section 10.1 Neighbor States"
4019 + DEFVAL { down }
4020 + ::= { ospfNbrEntry 6 }
4021 +
4022 +
4023 + ospfNbrEvents OBJECT-TYPE
4024 + SYNTAX Counter32
4025 + MAX-ACCESS read-only
4026 + STATUS current
4027 + DESCRIPTION
4028 + "The number of times this neighbor relationship
4029 + has changed state, or an error has occurred."
4030 + ::= { ospfNbrEntry 7 }
4031 +
4032 +
4033 + ospfNbrLsRetransQLen OBJECT-TYPE
4034 + SYNTAX Gauge32
4035 + MAX-ACCESS read-only
4036 + STATUS current
4037 + DESCRIPTION
4038 + "The current length of the retransmission
4039 + queue."
4040 + ::= { ospfNbrEntry 8 }
4041 +
4042 +
4043 + ospfNbmaNbrStatus OBJECT-TYPE
4044 + SYNTAX RowStatus
4045 + MAX-ACCESS read-create
4046 + STATUS current
4047 + DESCRIPTION
4048 + "This variable displays the status of the en-
4049 + try. Setting it to 'invalid' has the effect of
4050 + rendering it inoperative. The internal effect
4051 + (row removal) is implementation dependent."
4052 + ::= { ospfNbrEntry 9 }
4053 +
4054 +
4055 + ospfNbmaNbrPermanence OBJECT-TYPE
4056 + SYNTAX INTEGER {
4057 + dynamic (1), -- learned through protocol
4058 + permanent (2) -- configured address
4059 + }
4060 + MAX-ACCESS read-only
4061 + STATUS current
4062 + DESCRIPTION
4063 + "This variable displays the status of the en-
4064 + try. 'dynamic' and 'permanent' refer to how
4065 + the neighbor became known."
4066 + DEFVAL { permanent }
4067 + ::= { ospfNbrEntry 10 }
4068 +
4069 +
4070 + ospfNbrHelloSuppressed OBJECT-TYPE
4071 + SYNTAX TruthValue
4072 + MAX-ACCESS read-only
4073 + STATUS current
4074 + DESCRIPTION
4075 + "Indicates whether Hellos are being suppressed
4076 + to the neighbor"
4077 + ::= { ospfNbrEntry 11 }
4078 +
4079 +
4080 +-- OSPF Virtual Neighbor Table
4081 +
4082 +-- This table describes all virtual neighbors.
4083 +-- Since Virtual Links are configured in the
4084 +-- virtual interface table, this table is read-only.
4085 +
4086 + ospfVirtNbrTable OBJECT-TYPE
4087 + SYNTAX SEQUENCE OF OspfVirtNbrEntry
4088 + MAX-ACCESS not-accessible
4089 + STATUS current
4090 + DESCRIPTION
4091 + "A table of virtual neighbor information."
4092 + REFERENCE
4093 + "OSPF Version 2, Section 15 Virtual Links"
4094 + ::= { ospf 11 }
4095 +
4096 +
4097 + ospfVirtNbrEntry OBJECT-TYPE
4098 + SYNTAX OspfVirtNbrEntry
4099 + MAX-ACCESS not-accessible
4100 + STATUS current
4101 + DESCRIPTION
4102 + "Virtual neighbor information."
4103 + INDEX { ospfVirtNbrArea, ospfVirtNbrRtrId }
4104 + ::= { ospfVirtNbrTable 1 }
4105 +
4106 +OspfVirtNbrEntry ::=
4107 + SEQUENCE {
4108 + ospfVirtNbrArea
4109 + AreaID,
4110 + ospfVirtNbrRtrId
4111 + RouterID,
4112 + ospfVirtNbrIpAddr
4113 + IpAddress,
4114 + ospfVirtNbrOptions
4115 + Integer32,
4116 + ospfVirtNbrState
4117 + INTEGER,
4118 + ospfVirtNbrEvents
4119 + Counter32,
4120 + ospfVirtNbrLsRetransQLen
4121 + Gauge32,
4122 + ospfVirtNbrHelloSuppressed
4123 + TruthValue
4124 + }
4125 +
4126 + ospfVirtNbrArea OBJECT-TYPE
4127 + SYNTAX AreaID
4128 + MAX-ACCESS read-only
4129 + STATUS current
4130 + DESCRIPTION
4131 + "The Transit Area Identifier."
4132 + ::= { ospfVirtNbrEntry 1 }
4133 +
4134 +
4135 + ospfVirtNbrRtrId OBJECT-TYPE
4136 + SYNTAX RouterID
4137 + MAX-ACCESS read-only
4138 + STATUS current
4139 + DESCRIPTION
4140 + "A 32-bit integer uniquely identifying the
4141 + neighboring router in the Autonomous System."
4142 + ::= { ospfVirtNbrEntry 2 }
4143 +
4144 +
4145 + ospfVirtNbrIpAddr OBJECT-TYPE
4146 + SYNTAX IpAddress
4147 + MAX-ACCESS read-only
4148 + STATUS current
4149 + DESCRIPTION
4150 + "The IP address this Virtual Neighbor is us-
4151 + ing."
4152 + ::= { ospfVirtNbrEntry 3 }
4153 +
4154 +
4155 + ospfVirtNbrOptions OBJECT-TYPE
4156 + SYNTAX Integer32
4157 + MAX-ACCESS read-only
4158 + STATUS current
4159 + DESCRIPTION
4160 + "A Bit Mask corresponding to the neighbor's op-
4161 + tions field.
4162 +
4163 + Bit 1, if set, indicates that the system will
4164 + operate on Type of Service metrics other than
4165 + TOS 0. If zero, the neighbor will ignore all
4166 + metrics except the TOS 0 metric.
4167 +
4168 + Bit 2, if set, indicates that the system is
4169 + Network Multicast capable; ie, that it imple-
4170 + ments OSPF Multicast Routing."
4171 + ::= { ospfVirtNbrEntry 4 }
4172 + ospfVirtNbrState OBJECT-TYPE
4173 + SYNTAX INTEGER {
4174 + down (1),
4175 + attempt (2),
4176 + init (3),
4177 + twoWay (4),
4178 + exchangeStart (5),
4179 + exchange (6),
4180 + loading (7),
4181 + full (8)
4182 + }
4183 + MAX-ACCESS read-only
4184 + STATUS current
4185 + DESCRIPTION
4186 + "The state of the Virtual Neighbor Relation-
4187 + ship."
4188 + ::= { ospfVirtNbrEntry 5 }
4189 +
4190 +
4191 + ospfVirtNbrEvents OBJECT-TYPE
4192 + SYNTAX Counter32
4193 + MAX-ACCESS read-only
4194 + STATUS current
4195 + DESCRIPTION
4196 + "The number of times this virtual link has
4197 + changed its state, or an error has occurred."
4198 + ::= { ospfVirtNbrEntry 6 }
4199 +
4200 +
4201 + ospfVirtNbrLsRetransQLen OBJECT-TYPE
4202 + SYNTAX Gauge32
4203 + MAX-ACCESS read-only
4204 + STATUS current
4205 + DESCRIPTION
4206 + "The current length of the retransmission
4207 + queue."
4208 + ::= { ospfVirtNbrEntry 7 }
4209 +
4210 +
4211 + ospfVirtNbrHelloSuppressed OBJECT-TYPE
4212 + SYNTAX TruthValue
4213 + MAX-ACCESS read-only
4214 + STATUS current
4215 + DESCRIPTION
4216 + "Indicates whether Hellos are being suppressed
4217 + to the neighbor"
4218 + ::= { ospfVirtNbrEntry 8 }
4219 +
4220 +-- OSPF Link State Database, External
4221 +
4222 +-- The Link State Database contains the Link State
4223 +-- Advertisements from throughout the areas that the
4224 +-- device is attached to.
4225 +
4226 +-- This table is identical to the OSPF LSDB Table in
4227 +-- format, but contains only External Link State
4228 +-- Advertisements. The purpose is to allow external
4229 +-- LSAs to be displayed once for the router rather
4230 +-- than once in each non-stub area.
4231 +
4232 + ospfExtLsdbTable OBJECT-TYPE
4233 + SYNTAX SEQUENCE OF OspfExtLsdbEntry
4234 + MAX-ACCESS not-accessible
4235 + STATUS current
4236 + DESCRIPTION
4237 + "The OSPF Process's Links State Database."
4238 + REFERENCE
4239 + "OSPF Version 2, Section 12 Link State Adver-
4240 + tisements"
4241 + ::= { ospf 12 }
4242 +
4243 +
4244 + ospfExtLsdbEntry OBJECT-TYPE
4245 + SYNTAX OspfExtLsdbEntry
4246 + MAX-ACCESS not-accessible
4247 + STATUS current
4248 + DESCRIPTION
4249 + "A single Link State Advertisement."
4250 + INDEX { ospfExtLsdbType, ospfExtLsdbLsid, ospfExtLsdbRouterId }
4251 + ::= { ospfExtLsdbTable 1 }
4252 +
4253 +OspfExtLsdbEntry ::=
4254 + SEQUENCE {
4255 + ospfExtLsdbType