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
5 + BGP4-MIB DEFINITIONS ::= BEGIN
8 + MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
9 + IpAddress, Integer32, Counter32, Gauge32, mib-2
11 + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
15 + LAST-UPDATED "9902100000Z"
16 + ORGANIZATION "IETF IDR Working Group"
17 + CONTACT-INFO "E-mail: idr@merit.net
19 + Susan Hares (Editor)
23 + Ann Arbor, MI 48105-2785
24 + Tel: +1 734 936 2095
25 + Fax: +1 734 647 3185
26 + E-mail: skh@merit.edu
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"
36 + "The MIB module for BGP-4."
37 + REVISION "9902100000Z"
39 + "Corrected duplicate OBJECT IDENTIFIER
40 + assignment in the conformance information."
41 + REVISION "9601080000Z"
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."
49 + bgpVersion OBJECT-TYPE
50 + SYNTAX OCTET STRING (SIZE (1..255))
51 + MAX-ACCESS read-only
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
68 + bgpLocalAs OBJECT-TYPE
69 + SYNTAX INTEGER (0..65535)
70 + MAX-ACCESS read-only
73 + "The local autonomous system number."
78 + -- BGP Peer table. This table contains, one entry per BGP
79 + -- peer, information about the BGP peer.
81 + bgpPeerTable OBJECT-TYPE
82 + SYNTAX SEQUENCE OF BgpPeerEntry
83 + MAX-ACCESS not-accessible
86 + "BGP peer table. This table contains,
87 + one entry per BGP peer, information about the
88 + connections with BGP peers."
91 + bgpPeerEntry OBJECT-TYPE
93 + MAX-ACCESS not-accessible
96 + "Entry containing information about the
97 + connection with a BGP peer."
98 + INDEX { bgpPeerRemoteAddr }
99 + ::= { bgpPeerTable 1 }
101 + BgpPeerEntry ::= SEQUENCE {
108 + bgpPeerNegotiatedVersion
124 + bgpPeerInTotalMessages
126 + bgpPeerOutTotalMessages
130 + bgpPeerFsmEstablishedTransitions
132 + bgpPeerFsmEstablishedTime
134 + bgpPeerConnectRetryInterval
140 + bgpPeerHoldTimeConfigured
142 + bgpPeerKeepAliveConfigured
144 + bgpPeerMinASOriginationInterval
146 + bgpPeerMinRouteAdvertisementInterval
148 + bgpPeerInUpdateElapsedTime
152 + bgpPeerIdentifier OBJECT-TYPE
154 + MAX-ACCESS read-only
157 + "The BGP Identifier of this entry's BGP peer."
158 + ::= { bgpPeerEntry 1 }
160 + bgpPeerState OBJECT-TYPE
169 + MAX-ACCESS read-only
172 + "The BGP peer connection state."
173 + ::= { bgpPeerEntry 2 }
175 + bgpPeerAdminStatus OBJECT-TYPE
180 + MAX-ACCESS read-write
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
192 + ::= { bgpPeerEntry 3 }
194 + bgpPeerNegotiatedVersion OBJECT-TYPE
196 + MAX-ACCESS read-only
199 + "The negotiated version of BGP running between
201 + ::= { bgpPeerEntry 4 }
203 + bgpPeerLocalAddr OBJECT-TYPE
205 + MAX-ACCESS read-only
208 + "The local IP address of this entry's BGP
210 + ::= { bgpPeerEntry 5 }
212 + bgpPeerLocalPort OBJECT-TYPE
213 + SYNTAX INTEGER (0..65535)
214 + MAX-ACCESS read-only
217 + "The local port for the TCP connection between
219 + ::= { bgpPeerEntry 6 }
221 + bgpPeerRemoteAddr OBJECT-TYPE
223 + MAX-ACCESS read-only
226 + "The remote IP address of this entry's BGP
228 + ::= { bgpPeerEntry 7 }
230 + bgpPeerRemotePort OBJECT-TYPE
231 + SYNTAX INTEGER (0..65535)
232 + MAX-ACCESS read-only
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 }
243 + bgpPeerRemoteAs OBJECT-TYPE
244 + SYNTAX INTEGER (0..65535)
245 + MAX-ACCESS read-only
248 + "The remote autonomous system number."
249 + ::= { bgpPeerEntry 9 }
251 + bgpPeerInUpdates OBJECT-TYPE
253 + MAX-ACCESS read-only
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
260 + ::= { bgpPeerEntry 10 }
262 + bgpPeerOutUpdates OBJECT-TYPE
264 + MAX-ACCESS read-only
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
271 + ::= { bgpPeerEntry 11 }
273 + bgpPeerInTotalMessages OBJECT-TYPE
275 + MAX-ACCESS read-only
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 }
284 + bgpPeerOutTotalMessages OBJECT-TYPE
286 + MAX-ACCESS read-only
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 }
295 + bgpPeerLastError OBJECT-TYPE
296 + SYNTAX OCTET STRING (SIZE (2))
297 + MAX-ACCESS read-only
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 }
308 + bgpPeerFsmEstablishedTransitions OBJECT-TYPE
310 + MAX-ACCESS read-only
313 + "The total number of times the BGP FSM
314 + transitioned into the established state."
315 + ::= { bgpPeerEntry 15 }
317 + bgpPeerFsmEstablishedTime OBJECT-TYPE
319 + MAX-ACCESS read-only
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 }
329 + bgpPeerConnectRetryInterval OBJECT-TYPE
330 + SYNTAX INTEGER (1..65535)
331 + MAX-ACCESS read-write
334 + "Time interval in seconds for the ConnectRetry
335 + timer. The suggested value for this timer is
337 + ::= { bgpPeerEntry 17 }
339 + bgpPeerHoldTime OBJECT-TYPE
340 + SYNTAX INTEGER ( 0 | 3..65535 )
341 + MAX-ACCESS read-only
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 }
356 + bgpPeerKeepAlive OBJECT-TYPE
357 + SYNTAX INTEGER ( 0 | 1..21845 )
358 + MAX-ACCESS read-only
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 }
374 + bgpPeerHoldTimeConfigured OBJECT-TYPE
375 + SYNTAX INTEGER ( 0 | 3..65535 )
376 + MAX-ACCESS read-write
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 }
392 + bgpPeerKeepAliveConfigured OBJECT-TYPE
393 + SYNTAX INTEGER ( 0 | 1..21845 )
394 + MAX-ACCESS read-write
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 }
412 + bgpPeerMinASOriginationInterval OBJECT-TYPE
413 + SYNTAX INTEGER (1..65535)
414 + MAX-ACCESS read-write
417 + "Time interval in seconds for the
418 + MinASOriginationInterval timer.
419 + The suggested value for this timer is 15 seconds."
420 + ::= { bgpPeerEntry 22 }
422 + bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE
423 + SYNTAX INTEGER (1..65535)
424 + MAX-ACCESS read-write
427 + "Time interval in seconds for the
428 + MinRouteAdvertisementInterval timer.
429 + The suggested value for this timer is 30 seconds."
430 + ::= { bgpPeerEntry 23 }
432 + bgpPeerInUpdateElapsedTime OBJECT-TYPE
434 + MAX-ACCESS read-only
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 }
445 + bgpIdentifier OBJECT-TYPE
447 + MAX-ACCESS read-only
450 + "The BGP Identifier of local system."
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.
461 + bgpRcvdPathAttrTable OBJECT-TYPE
462 + SYNTAX SEQUENCE OF BgpPathAttrEntry
463 + MAX-ACCESS not-accessible
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
472 + bgpPathAttrEntry OBJECT-TYPE
473 + SYNTAX BgpPathAttrEntry
474 + MAX-ACCESS not-accessible
477 + "Information about a path to a network."
478 + INDEX { bgpPathAttrDestNetwork,
480 + ::= { bgpRcvdPathAttrTable 1 }
482 + BgpPathAttrEntry ::= SEQUENCE {
485 + bgpPathAttrDestNetwork
493 + bgpPathAttrInterASMetric
497 + bgpPathAttrPeer OBJECT-TYPE
499 + MAX-ACCESS read-only
502 + "The IP address of the peer where the path
503 + information was learned."
504 + ::= { bgpPathAttrEntry 1 }
506 + bgpPathAttrDestNetwork OBJECT-TYPE
508 + MAX-ACCESS read-only
511 + "The address of the destination network."
512 + ::= { bgpPathAttrEntry 2 }
514 + bgpPathAttrOrigin OBJECT-TYPE
516 + igp(1),-- networks are interior
517 + egp(2),-- networks learned via EGP
518 + incomplete(3) -- undetermined
520 + MAX-ACCESS read-only
523 + "The ultimate origin of the path information."
524 + ::= { bgpPathAttrEntry 3 }
526 + bgpPathAttrASPath OBJECT-TYPE
527 + SYNTAX OCTET STRING (SIZE (2..255))
528 + MAX-ACCESS read-only
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:
538 + first-byte-of-pair = ASNumber / 256;
539 + second-byte-of-pair = ASNumber & 255;"
540 + ::= { bgpPathAttrEntry 4 }
542 + bgpPathAttrNextHop OBJECT-TYPE
544 + MAX-ACCESS read-only
547 + "The address of the border router that should
548 + be used for the destination network."
549 + ::= { bgpPathAttrEntry 5 }
551 + bgpPathAttrInterASMetric OBJECT-TYPE
553 + MAX-ACCESS read-only
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 }
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.
567 + bgp4PathAttrTable OBJECT-TYPE
568 + SYNTAX SEQUENCE OF Bgp4PathAttrEntry
569 + MAX-ACCESS not-accessible
572 + "The BGP-4 Received Path Attribute Table contains
573 + information about paths to destination networks
574 + received from all BGP4 peers."
577 + bgp4PathAttrEntry OBJECT-TYPE
578 + SYNTAX Bgp4PathAttrEntry
579 + MAX-ACCESS not-accessible
582 + "Information about a path to a network."
583 + INDEX { bgp4PathAttrIpAddrPrefix,
584 + bgp4PathAttrIpAddrPrefixLen,
586 + ::= { bgp4PathAttrTable 1 }
588 + Bgp4PathAttrEntry ::= SEQUENCE {
591 + bgp4PathAttrIpAddrPrefixLen
593 + bgp4PathAttrIpAddrPrefix
597 + bgp4PathAttrASPathSegment
599 + bgp4PathAttrNextHop
601 + bgp4PathAttrMultiExitDisc
603 + bgp4PathAttrLocalPref
605 + bgp4PathAttrAtomicAggregate
607 + bgp4PathAttrAggregatorAS
609 + bgp4PathAttrAggregatorAddr
611 + bgp4PathAttrCalcLocalPref
615 + bgp4PathAttrUnknown
619 + bgp4PathAttrPeer OBJECT-TYPE
621 + MAX-ACCESS read-only
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
632 + "Length in bits of the IP address prefix in the
633 + Network Layer Reachability Information field."
634 + ::= { bgp4PathAttrEntry 2 }
636 + bgp4PathAttrIpAddrPrefix OBJECT-TYPE
638 + MAX-ACCESS read-only
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 }
649 + bgp4PathAttrOrigin OBJECT-TYPE
651 + igp(1),-- networks are interior
652 + egp(2),-- networks learned via EGP
653 + incomplete(3) -- undetermined
655 + MAX-ACCESS read-only
658 + "The ultimate origin of the path information."
659 + ::= { bgp4PathAttrEntry 4 }
661 + bgp4PathAttrASPathSegment OBJECT-TYPE
662 + SYNTAX OCTET STRING (SIZE (2..255))
663 + MAX-ACCESS read-only
666 + "The sequence of AS path segments. Each AS
667 + path segment is represented by a triple
668 + <type, length, value>.
670 + The type is a 1-octet field which has two
672 + 1 AS_SET: unordered set of ASs a
673 + route in the UPDATE message
675 + 2 AS_SEQUENCE: ordered set of ASs
676 + a route in the UPDATE message
679 + The length is a 1-octet field containing the
680 + number of ASs in the value field.
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:
687 + first-byte-of-pair = ASNumber / 256;
688 + second-byte-of-pair = ASNumber & 255;"
689 + ::= { bgp4PathAttrEntry 5 }
691 + bgp4PathAttrNextHop OBJECT-TYPE
693 + MAX-ACCESS read-only
696 + "The address of the border router that should
697 + be used for the destination network."
698 + ::= { bgp4PathAttrEntry 6 }
700 + bgp4PathAttrMultiExitDisc OBJECT-TYPE
701 + SYNTAX INTEGER (-1..2147483647)
702 + MAX-ACCESS read-only
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
709 + ::= { bgp4PathAttrEntry 7 }
711 + bgp4PathAttrLocalPref OBJECT-TYPE
712 + SYNTAX INTEGER (-1..2147483647)
713 + MAX-ACCESS read-only
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 }
721 + bgp4PathAttrAtomicAggregate OBJECT-TYPE
723 + lessSpecificRrouteNotSelected(1),
724 + lessSpecificRouteSelected(2)
726 + MAX-ACCESS read-only
729 + "Whether or not a system has selected
730 + a less specific route without selecting a
731 + more specific route."
732 + ::= { bgp4PathAttrEntry 9 }
734 + bgp4PathAttrAggregatorAS OBJECT-TYPE
735 + SYNTAX INTEGER (0..65535)
736 + MAX-ACCESS read-only
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 }
744 + bgp4PathAttrAggregatorAddr OBJECT-TYPE
746 + MAX-ACCESS read-only
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 }
754 + bgp4PathAttrCalcLocalPref OBJECT-TYPE
755 + SYNTAX INTEGER (-1..2147483647)
756 + MAX-ACCESS read-only
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
763 + ::= { bgp4PathAttrEntry 12 }
765 + bgp4PathAttrBest OBJECT-TYPE
767 + false(1),-- not chosen as best route
768 + true(2) -- chosen as best route
770 + MAX-ACCESS read-only
773 + "An indication of whether or not this route
774 + was chosen as the best BGP4 route."
775 + ::= { bgp4PathAttrEntry 13 }
777 + bgp4PathAttrUnknown OBJECT-TYPE
778 + SYNTAX OCTET STRING (SIZE(0..255))
779 + MAX-ACCESS read-only
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 }
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.
799 + -- { bgp 7 } is unused
801 + bgpTraps OBJECT IDENTIFIER ::= { bgp 0 }
803 + bgpEstablished NOTIFICATION-TYPE
804 + OBJECTS { bgpPeerRemoteAddr,
809 + "The BGP Established event is generated when
810 + the BGP FSM enters the ESTABLISHED state."
813 + bgpBackwardTransition NOTIFICATION-TYPE
814 + OBJECTS { bgpPeerRemoteAddr,
819 + "The BGPBackwardTransition Event is generated
820 + when the BGP FSM moves from a higher numbered
821 + state to a lower numbered state."
824 + -- conformance information
826 + bgpMIBConformance OBJECT IDENTIFIER ::= { bgp 8 }
827 + bgpMIBCompliances OBJECT IDENTIFIER ::= { bgpMIBConformance 1 }
828 + bgpMIBGroups OBJECT IDENTIFIER ::= { bgpMIBConformance 2 }
830 + -- compliance statements
832 + bgpMIBCompliance MODULE-COMPLIANCE
835 + "The compliance statement for entities which
836 + implement the BGP4 mib."
837 + MODULE -- this module
838 + MANDATORY-GROUPS { bgp4MIBGlobalsGroup,
840 + bgp4MIBPathAttrGroup,
841 + bgp4MIBNotificationGroup }
842 + ::= { bgpMIBCompliances 1 }
844 + -- units of conformance
846 + bgp4MIBGlobalsGroup OBJECT-GROUP
847 + OBJECTS { bgpVersion,
852 + "A collection of objects providing information
853 + on global BGP state."
854 + ::= { bgpMIBGroups 1 }
856 + bgp4MIBPeerGroup OBJECT-GROUP
857 + OBJECTS { bgpPeerIdentifier,
859 + bgpPeerAdminStatus,
860 + bgpPeerNegotiatedVersion,
868 + bgpPeerInTotalMessages,
869 + bgpPeerOutTotalMessages,
871 + bgpPeerFsmEstablishedTransitions,
872 + bgpPeerFsmEstablishedTime,
873 + bgpPeerConnectRetryInterval,
876 + bgpPeerHoldTimeConfigured,
877 + bgpPeerKeepAliveConfigured,
878 + bgpPeerMinASOriginationInterval,
879 + bgpPeerMinRouteAdvertisementInterval,
880 + bgpPeerInUpdateElapsedTime }
883 + "A collection of objects for managing
885 + ::= { bgpMIBGroups 2 }
887 + bgp4MIBRcvdPathAttrGroup OBJECT-GROUP
888 + OBJECTS { bgpPathAttrPeer,
889 + bgpPathAttrDestNetwork,
892 + bgpPathAttrNextHop,
893 + bgpPathAttrInterASMetric }
896 + "A collection of objects for managing BGP
899 + This conformance group is obsolete,
900 + replaced by bgp4MIBPathAttrGroup."
901 + ::= { bgpMIBGroups 3 }
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,
917 + bgp4PathAttrUnknown }
920 + "A collection of objects for managing
922 + ::= { bgpMIBGroups 4 }
924 + bgp4MIBNotificationGroup NOTIFICATION-GROUP
925 + NOTIFICATIONS { bgpEstablished,
926 + bgpBackwardTransition }
929 + "A collection of notifications for signaling
930 + changes in BGP peer relationships."
931 + ::= { bgpMIBGroups 5 }
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
938 +BRIDGE-MIB DEFINITIONS ::= BEGIN
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
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.
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.
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
970 +BridgeId ::= OCTET STRING (SIZE (8)) -- the
971 + -- Bridge-Identifier
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).
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:
997 +Timeout ::= INTEGER -- a STP timer in units of 1/100 seconds
999 +-- To convert a Timeout value into a value in units of
1000 +-- 1/256 seconds, the following algorithm should be used:
1002 +-- b = floor( (n * 256) / 100)
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
1009 +-- To convert the value from 1/256 second units back to
1010 +-- 1/100 seconds, the following algorithm should be used:
1012 +-- n = ceiling( (b * 100) / 256)
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
1020 +-- Note: it is important that the arithmetic operations are
1021 +-- done in the order specified (i.e., multiply first, divide
1024 + dot1dBridge OBJECT IDENTIFIER ::= { mib-2 17 }
1026 +-- groups in the Bridge MIB
1028 +dot1dBase OBJECT IDENTIFIER ::= { dot1dBridge 1 }
1030 +dot1dStp OBJECT IDENTIFIER ::= { dot1dBridge 2 }
1032 +dot1dSr OBJECT IDENTIFIER ::= { dot1dBridge 3 }
1033 +-- separately documented
1035 +dot1dTp OBJECT IDENTIFIER ::= { dot1dBridge 4 }
1037 +dot1dStatic OBJECT IDENTIFIER ::= { dot1dBridge 5 }
1039 +-- the dot1dBase group
1041 +-- Implementation of the dot1dBase group is mandatory for all
1044 +dot1dBaseBridgeAddress OBJECT-TYPE
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."
1058 + "IEEE 802.1D-1990: Sections 6.4.1.1.3 and 3.12.5"
1059 + ::= { dot1dBase 1 }
1061 +dot1dBaseNumPorts OBJECT-TYPE
1066 + "The number of ports controlled by this bridging
1069 + "IEEE 802.1D-1990: Section 6.4.1.1.3"
1070 + ::= { dot1dBase 2 }
1072 +dot1dBaseType OBJECT-TYPE
1075 + transparent-only(2),
1076 + sourceroute-only(3),
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 }
1088 +-- The Generic Bridge Port Table
1090 +dot1dBasePortTable OBJECT-TYPE
1091 + SYNTAX SEQUENCE OF Dot1dBasePortEntry
1092 + ACCESS not-accessible
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
1099 + ::= { dot1dBase 4 }
1101 +dot1dBasePortEntry OBJECT-TYPE
1102 + SYNTAX Dot1dBasePortEntry
1103 + ACCESS not-accessible
1106 + "A list of information for each port of the
1109 + "IEEE 802.1D-1990: Section 6.4.2, 6.6.1"
1110 + INDEX { dot1dBasePort }
1111 + ::= { dot1dBasePortTable 1 }
1113 +Dot1dBasePortEntry ::=
1117 + dot1dBasePortIfIndex
1119 + dot1dBasePortCircuit
1121 + OBJECT IDENTIFIER,
1122 + dot1dBasePortDelayExceededDiscards
1124 + dot1dBasePortMtuExceededDiscards
1128 +dot1dBasePort OBJECT-TYPE
1129 + SYNTAX INTEGER (1..65535)
1133 + "The port number of the port for which this entry
1134 + contains bridge management information."
1135 + ::= { dot1dBasePortEntry 1 }
1137 +dot1dBasePortIfIndex OBJECT-TYPE
1142 + "The value of the instance of the ifIndex object,
1143 + defined in MIB-II, for the interface corresponding
1145 + ::= { dot1dBasePortEntry 2 }
1147 +dot1dBasePortCircuit OBJECT-TYPE
1148 + SYNTAX OBJECT IDENTIFIER
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.
1162 + For a port which has a unique value of
1163 + dot1dBasePortIfIndex, this object can have the
1165 + ::= { dot1dBasePortEntry 3 }
1167 +dot1dBasePortDelayExceededDiscards OBJECT-TYPE
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
1178 + "IEEE 802.1D-1990: Section 6.6.1.1.3"
1179 + ::= { dot1dBasePortEntry 4 }
1181 +dot1dBasePortMtuExceededDiscards OBJECT-TYPE
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."
1190 + "IEEE 802.1D-1990: Section 6.6.1.1.3"
1191 + ::= { dot1dBasePortEntry 5 }
1193 +-- the dot1dStp group
1195 +-- Implementation of the dot1dStp group is optional. It is
1196 +-- implemented by those bridges that support the Spanning Tree
1199 +dot1dStpProtocolSpecification OBJECT-TYPE
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."
1217 + ::= { dot1dStp 1 }
1219 +dot1dStpPriority OBJECT-TYPE
1220 + SYNTAX INTEGER (0..65535)
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."
1230 + "IEEE 802.1D-1990: Section 4.5.3.7"
1231 + ::= { dot1dStp 2 }
1233 +dot1dStpTimeSinceTopologyChange OBJECT-TYPE
1238 + "The time (in hundredths of a second) since the
1239 + last time a topology change was detected by the
1242 + "IEEE 802.1D-1990: Section 6.8.1.1.3"
1243 + ::= { dot1dStp 3 }
1245 +dot1dStpTopChanges OBJECT-TYPE
1250 + "The total number of topology changes detected by
1251 + this bridge since the management entity was last
1252 + reset or initialized."
1254 + "IEEE 802.1D-1990: Section 6.8.1.1.3"
1255 + ::= { dot1dStp 4 }
1257 +dot1dStpDesignatedRoot OBJECT-TYPE
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
1266 + the Root Identifier parameter in all Configuration
1267 + Bridge PDUs originated by this node."
1269 + "IEEE 802.1D-1990: Section 4.5.3.1"
1270 + ::= { dot1dStp 5 }
1272 +dot1dStpRootCost OBJECT-TYPE
1277 + "The cost of the path to the root as seen from
1280 + "IEEE 802.1D-1990: Section 4.5.3.2"
1281 + ::= { dot1dStp 6 }
1283 +dot1dStpRootPort OBJECT-TYPE
1288 + "The port number of the port which offers the
1289 + lowest cost path from this bridge to the root
1292 + "IEEE 802.1D-1990: Section 4.5.3.3"
1293 + ::= { dot1dStp 7 }
1295 +dot1dStpMaxAge OBJECT-TYPE
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."
1306 + "IEEE 802.1D-1990: Section 4.5.3.4"
1307 + ::= { dot1dStp 8 }
1309 +dot1dStpHelloTime OBJECT-TYPE
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
1322 + "IEEE 802.1D-1990: Section 4.5.3.5"
1323 + ::= { dot1dStp 9 }
1325 +dot1dStpHoldTime OBJECT-TYPE
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."
1335 + "IEEE 802.1D-1990: Section 4.5.3.14"
1336 + ::= { dot1dStp 10 }
1338 +dot1dStpForwardDelay OBJECT-TYPE
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.]"
1358 + "IEEE 802.1D-1990: Section 4.5.3.6"
1359 + ::= { dot1dStp 11 }
1361 +dot1dStpBridgeMaxAge OBJECT-TYPE
1362 + SYNTAX Timeout (600..4000)
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
1377 + "IEEE 802.1D-1990: Section 4.5.3.8"
1378 + ::= { dot1dStp 12 }
1380 +dot1dStpBridgeHelloTime OBJECT-TYPE
1381 + SYNTAX Timeout (100..1000)
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."
1392 + "IEEE 802.1D-1990: Section 4.5.3.9"
1393 + ::= { dot1dStp 13 }
1395 +dot1dStpBridgeForwardDelay OBJECT-TYPE
1396 + SYNTAX Timeout (400..3000)
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
1410 + "IEEE 802.1D-1990: Section 4.5.3.10"
1411 + ::= { dot1dStp 14 }
1413 +-- The Spanning Tree Port Table
1415 +dot1dStpPortTable OBJECT-TYPE
1416 + SYNTAX SEQUENCE OF Dot1dStpPortEntry
1417 + ACCESS not-accessible
1420 + "A table that contains port-specific information
1421 + for the Spanning Tree Protocol."
1422 + ::= { dot1dStp 15 }
1424 +dot1dStpPortEntry OBJECT-TYPE
1425 + SYNTAX Dot1dStpPortEntry
1426 + ACCESS not-accessible
1429 + "A list of information maintained by every port
1430 + about the Spanning Tree Protocol state for that
1432 + INDEX { dot1dStpPort }
1433 + ::= { dot1dStpPortTable 1 }
1435 +Dot1dStpPortEntry ::=
1439 + dot1dStpPortPriority
1443 + dot1dStpPortEnable
1445 + dot1dStpPortPathCost
1447 + dot1dStpPortDesignatedRoot
1449 + dot1dStpPortDesignatedCost
1451 + dot1dStpPortDesignatedBridge
1453 + dot1dStpPortDesignatedPort
1455 + dot1dStpPortForwardTransitions
1459 +dot1dStpPort OBJECT-TYPE
1460 + SYNTAX INTEGER (1..65535)
1465 + "The port number of the port for which this entry
1466 + contains Spanning Tree Protocol management
1469 + "IEEE 802.1D-1990: Section 6.8.2.1.2"
1470 + ::= { dot1dStpPortEntry 1 }
1472 +dot1dStpPortPriority OBJECT-TYPE
1473 + SYNTAX INTEGER (0..255)
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
1483 + "IEEE 802.1D-1990: Section 4.5.5.1"
1484 + ::= { dot1dStpPortEntry 2 }
1486 +dot1dStpPortState OBJECT-TYPE
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)."
1507 + "IEEE 802.1D-1990: Section 4.5.5.2"
1508 + ::= { dot1dStpPortEntry 3 }
1510 +dot1dStpPortEnable OBJECT-TYPE
1518 + "The enabled/disabled status of the port."
1520 + "IEEE 802.1D-1990: Section 4.5.5.2"
1521 + ::= { dot1dStpPortEntry 4 }
1523 +dot1dStpPortPathCost OBJECT-TYPE
1524 + SYNTAX INTEGER (1..65535)
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."
1534 + "IEEE 802.1D-1990: Section 4.5.5.3"
1535 + ::= { dot1dStpPortEntry 5 }
1537 +dot1dStpPortDesignatedRoot OBJECT-TYPE
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."
1547 + "IEEE 802.1D-1990: Section 4.5.5.4"
1548 + ::= { dot1dStpPortEntry 6 }
1550 +dot1dStpPortDesignatedCost OBJECT-TYPE
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
1561 + "IEEE 802.1D-1990: Section 4.5.5.5"
1562 + ::= { dot1dStpPortEntry 7 }
1564 +dot1dStpPortDesignatedBridge OBJECT-TYPE
1569 + "The Bridge Identifier of the bridge which this
1570 + port considers to be the Designated Bridge for
1571 + this port's segment."
1573 + "IEEE 802.1D-1990: Section 4.5.5.6"
1574 + ::= { dot1dStpPortEntry 8 }
1576 +dot1dStpPortDesignatedPort OBJECT-TYPE
1577 + SYNTAX OCTET STRING (SIZE (2))
1581 + "The Port Identifier of the port on the Designated
1582 + Bridge for this port's segment."
1584 + "IEEE 802.1D-1990: Section 4.5.5.7"
1585 + ::= { dot1dStpPortEntry 9 }
1587 +dot1dStpPortForwardTransitions OBJECT-TYPE
1592 + "The number of times this port has transitioned
1593 + from the Learning state to the Forwarding state."
1594 + ::= { dot1dStpPortEntry 10 }
1596 +-- the dot1dTp group
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
1603 +dot1dTpLearnedEntryDiscards OBJECT-TYPE
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."
1621 + "IEEE 802.1D-1990: Section 6.7.1.1.3"
1624 +dot1dTpAgingTime OBJECT-TYPE
1625 + SYNTAX INTEGER (10..1000000)
1629 + "The timeout period in seconds for aging out
1630 + dynamically learned forwarding information.
1631 + 802.1D-1990 recommends a default of 300 seconds."
1633 + "IEEE 802.1D-1990: Section 6.7.1.1.3"
1636 +-- The Forwarding Database for Transparent Bridges
1638 +dot1dTpFdbTable OBJECT-TYPE
1639 + SYNTAX SEQUENCE OF Dot1dTpFdbEntry
1640 + ACCESS not-accessible
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."
1650 +dot1dTpFdbEntry OBJECT-TYPE
1651 + SYNTAX Dot1dTpFdbEntry
1652 + ACCESS not-accessible
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 }
1661 +Dot1dTpFdbEntry ::=
1671 +dot1dTpFdbAddress OBJECT-TYPE
1676 + "A unicast MAC address for which the bridge has
1677 + forwarding and/or filtering information."
1679 + "IEEE 802.1D-1990: Section 3.9.1, 3.9.2"
1680 + ::= { dot1dTpFdbEntry 1 }
1682 +dot1dTpFdbPort OBJECT-TYPE
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 }
1701 +dot1dTpFdbStatus OBJECT-TYPE
1712 + "The status of this entry. The meanings of the
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
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 }
1744 +-- Port Table for Transparent Bridges
1746 +dot1dTpPortTable OBJECT-TYPE
1747 + SYNTAX SEQUENCE OF Dot1dTpPortEntry
1748 + ACCESS not-accessible
1751 + "A table that contains information about every
1752 + port that is associated with this transparent
1756 +dot1dTpPortEntry OBJECT-TYPE
1757 + SYNTAX Dot1dTpPortEntry
1758 + ACCESS not-accessible
1761 + "A list of information for each port of a
1762 + transparent bridge."
1763 + INDEX { dot1dTpPort }
1764 + ::= { dot1dTpPortTable 1 }
1766 +Dot1dTpPortEntry ::=
1770 + dot1dTpPortMaxInfo
1772 + dot1dTpPortInFrames
1774 + dot1dTpPortOutFrames
1776 + dot1dTpPortInDiscards
1780 +dot1dTpPort OBJECT-TYPE
1781 + SYNTAX INTEGER (1..65535)
1785 + "The port number of the port for which this entry
1786 + contains Transparent bridging management
1788 + ::= { dot1dTpPortEntry 1 }
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).
1796 +dot1dTpPortMaxInfo OBJECT-TYPE
1801 + "The maximum size of the INFO (non-MAC) field that
1802 + this port will receive or transmit."
1803 + ::= { dot1dTpPortEntry 2 }
1805 +dot1dTpPortInFrames OBJECT-TYPE
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
1818 + "IEEE 802.1D-1990: Section 6.6.1.1.3"
1819 + ::= { dot1dTpPortEntry 3 }
1821 +dot1dTpPortOutFrames OBJECT-TYPE
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
1834 + "IEEE 802.1D-1990: Section 6.6.1.1.3"
1835 + ::= { dot1dTpPortEntry 4 }
1837 +dot1dTpPortInDiscards OBJECT-TYPE
1842 + "Count of valid frames received which were
1843 + discarded (i.e., filtered) by the Forwarding
1846 + "IEEE 802.1D-1990: Section 6.6.1.1.3"
1847 + ::= { dot1dTpPortEntry 5 }
1848 +-- The Static (Destination-Address Filtering) Database
1850 +-- Implementation of this group is optional.
1852 +dot1dStaticTable OBJECT-TYPE
1853 + SYNTAX SEQUENCE OF Dot1dStaticEntry
1854 + ACCESS not-accessible
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."
1870 + "IEEE 802.1D-1990: Section 6.7.2"
1871 + ::= { dot1dStatic 1 }
1873 +dot1dStaticEntry OBJECT-TYPE
1874 + SYNTAX Dot1dStaticEntry
1875 + ACCESS not-accessible
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."
1884 + "IEEE 802.1D-1990: Section 6.7.2"
1885 + INDEX { dot1dStaticAddress, dot1dStaticReceivePort }
1886 + ::= { dot1dStaticTable 1 }
1888 +Dot1dStaticEntry ::=
1890 + dot1dStaticAddress
1892 + dot1dStaticReceivePort
1894 + dot1dStaticAllowedToGoTo
1900 +dot1dStaticAddress OBJECT-TYPE
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."
1910 + "IEEE 802.1D-1990: Section 3.9.1, 3.9.2"
1911 + ::= { dot1dStaticEntry 1 }
1913 +dot1dStaticReceivePort OBJECT-TYPE
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 }
1926 +dot1dStaticAllowedToGoTo OBJECT-TYPE
1927 + SYNTAX OCTET STRING
1931 + "The set of ports to which frames received from a
1932 + specific port and destined for a specific MAC
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
1951 + ::= { dot1dStaticEntry 3 }
1953 +dot1dStaticStatus OBJECT-TYPE
1959 + deleteOnTimeout(5)
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
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
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
1982 + ::= { dot1dStaticEntry 4 }
1984 +-- Traps for use by Bridges
1986 +-- Traps for the Spanning Tree Protocol
1989 + ENTERPRISE dot1dBridge
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
2000 +topologyChange TRAP-TYPE
2001 + ENTERPRISE dot1dBridge
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
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
2017 +GNOME-SMI DEFINITIONS ::= BEGIN
2025 +gnome MODULE-IDENTITY
2026 + LAST-UPDATED "200709070000Z"
2027 + ORGANIZATION "GNOME project"
2029 + "GNU Network Object Model Environment project
2031 + see http://www.gnome.org for contact persons of a particular
2032 + area or subproject of GNOME.
2034 + Administrative contact for MIB module:
2041 + email: jochen@scram.de"
2043 + "The Structure of GNOME."
2045 + -- revision history
2047 + REVISION "200709070000Z" -- Sep 07, 2007
2049 + "Fixed wrong enterprise number (how comes this
2050 + typo was unnoticed for so long?)."
2052 + REVISION "200505070000Z" -- May 07, 2005
2054 + "Added gnomeLDAP subtree for LDAP definitions."
2056 + REVISION "200312070000Z" -- December 07, 2003
2058 + "Added gnomeSysadmin subtree for GNOME project system administration.
2059 + Updated contact info."
2061 + REVISION "9809010000Z" -- September 01, 1998
2063 + "Initial version."
2065 + ::= { enterprises 3319 } -- assigned by IANA
2067 +gnomeProducts OBJECT-IDENTITY
2070 + "gnomeProducts is the root OBJECT IDENTIFIER from
2071 + which sysObjectID values are assigned."
2074 +gnomeMgmt OBJECT-IDENTITY
2077 + "gnomeMgmt defines the subtree for production GNOME related
2078 + MIB registrations."
2081 +gnomeTest OBJECT-IDENTITY
2084 + "gnomeTest defines the subtree for testing GNOME related
2085 + MIB registrations."
2088 +gnomeSysadmin OBJECT-IDENTITY
2091 + "gnomeSysadmin defines the subtree for GNOME related Sysadmin
2092 + MIB registrations."
2095 +gnomeLDAP OBJECT-IDENTITY
2098 + "gnomeLDAP defines the subtree for GNOME related LDAP
2102 +-- more to come if necessary.
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
2109 +OSPF-MIB DEFINITIONS ::= BEGIN
2112 + MODULE-IDENTITY, OBJECT-TYPE, Counter32, Gauge32,
2113 + Integer32, IpAddress
2115 + TEXTUAL-CONVENTION, TruthValue, RowStatus
2117 + MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
2118 + mib-2 FROM RFC1213-MIB;
2120 +-- This MIB module uses the extended OBJECT-TYPE macro as
2123 +ospf MODULE-IDENTITY
2124 + LAST-UPDATED "9501201225Z" -- Fri Jan 20 12:25:50 PST 1995
2125 + ORGANIZATION "IETF OSPF Working Group"
2128 + Postal: Cisco Systems
2130 + Santa Barbara, California 93111
2131 + Tel: +1 805 681 0115
2132 + E-Mail: fred@cisco.com
2135 + Postal: RainbowBridge Communications
2136 + Tel: (301) 340-9416
2137 + E-Mail: rcoltun@rainbow-bridge.com"
2139 + "The MIB module to describe the OSPF Version 2
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
2147 +AreaID ::= TEXTUAL-CONVENTION
2150 + "An OSPF Area Identifier."
2154 +-- The Router ID, in OSPF, has the same format as an IP Address,
2155 +-- but identifies the router independent of its IP Address.
2157 +RouterID ::= TEXTUAL-CONVENTION
2160 + "A OSPF Router Identifier."
2164 +-- The OSPF Metric is defined as an unsigned value in the range
2166 +Metric ::= TEXTUAL-CONVENTION
2169 + "The OSPF Internal Metric."
2170 + SYNTAX Integer32 (0..'FFFF'h)
2172 +BigMetric ::= TEXTUAL-CONVENTION
2175 + "The OSPF External Metric."
2176 + SYNTAX Integer32 (0..'FFFFFF'h)
2180 +Status ::= TEXTUAL-CONVENTION
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) }
2188 +-- Time Durations measured in seconds
2190 +PositiveInteger ::= TEXTUAL-CONVENTION
2193 + "A positive integer. Values in excess are precluded as
2194 + unnecessary and prone to interoperability issues."
2195 + SYNTAX Integer32 (0..'7FFFFFFF'h)
2197 +HelloRange ::= TEXTUAL-CONVENTION
2200 + "The range of intervals on which hello messages are
2202 + SYNTAX Integer32 (1..'FFFF'h)
2204 +UpToMaxAge ::= TEXTUAL-CONVENTION
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)
2212 +-- The range of ifIndex
2214 +InterfaceIndex ::= TEXTUAL-CONVENTION
2217 + "The range of ifIndex."
2221 +-- Potential Priorities for the Designated Router Election
2223 +DesignatedRouterPriority ::= TEXTUAL-CONVENTION
2226 + "The values defined for the priority of a system for
2227 + becoming the designated router."
2228 + SYNTAX Integer32 (0..'FF'h)
2230 +TOSType ::= TEXTUAL-CONVENTION
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
2236 + +-----+-----+-----+-----+-----+-----+-----+-----+
2238 + | PRECEDENCE | TYPE OF SERVICE | 0 |
2240 + +-----+-----+-----+-----+-----+-----+-----+-----+
2243 + Field Policy Field Policy
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
2255 + The remaining values are left for future definition."
2256 + SYNTAX Integer32 (0..30)
2259 +-- OSPF General Variables
2261 +-- These parameters apply globally to the Router's
2264 +ospfGeneralGroup OBJECT IDENTIFIER ::= { ospf 1 }
2267 + ospfRouterId OBJECT-TYPE
2269 + MAX-ACCESS read-write
2272 + "A 32-bit integer uniquely identifying the
2273 + router in the Autonomous System.
2275 + By convention, to ensure uniqueness, this
2276 + should default to the value of one of the
2277 + router's IP interface addresses."
2279 + "OSPF Version 2, C.1 Global parameters"
2280 + ::= { ospfGeneralGroup 1 }
2283 + ospfAdminStat OBJECT-TYPE
2285 + MAX-ACCESS read-write
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-
2293 + ::= { ospfGeneralGroup 2 }
2295 + ospfVersionNumber OBJECT-TYPE
2296 + SYNTAX INTEGER { version2 (2) }
2297 + MAX-ACCESS read-only
2300 + "The current version number of the OSPF proto-
2303 + "OSPF Version 2, Title"
2304 + ::= { ospfGeneralGroup 3 }
2307 + ospfAreaBdrRtrStatus OBJECT-TYPE
2309 + MAX-ACCESS read-only
2312 + "A flag to note whether this router is an area
2315 + "OSPF Version 2, Section 3 Splitting the AS into
2317 + ::= { ospfGeneralGroup 4 }
2320 + ospfASBdrRtrStatus OBJECT-TYPE
2322 + MAX-ACCESS read-write
2325 + "A flag to note whether this router is config-
2326 + ured as an Autonomous System border router."
2328 + "OSPF Version 2, Section 3.3 Classification of
2330 + ::= { ospfGeneralGroup 5 }
2332 + ospfExternLsaCount OBJECT-TYPE
2334 + MAX-ACCESS read-only
2337 + "The number of external (LS type 5) link-state
2338 + advertisements in the link-state database."
2340 + "OSPF Version 2, Appendix A.4.5 AS external link
2342 + ::= { ospfGeneralGroup 6 }
2345 + ospfExternLsaCksumSum OBJECT-TYPE
2347 + MAX-ACCESS read-only
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
2357 + ::= { ospfGeneralGroup 7 }
2360 + ospfTOSSupport OBJECT-TYPE
2362 + MAX-ACCESS read-write
2365 + "The router's support for type-of-service rout-
2368 + "OSPF Version 2, Appendix F.1.2 Optional TOS
2370 + ::= { ospfGeneralGroup 8 }
2372 + ospfOriginateNewLsas OBJECT-TYPE
2374 + MAX-ACCESS read-only
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
2381 + ::= { ospfGeneralGroup 9 }
2384 + ospfRxNewLsas OBJECT-TYPE
2386 + MAX-ACCESS read-only
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-
2394 + ::= { ospfGeneralGroup 10 }
2396 + ospfExtLsdbLimit OBJECT-TYPE
2397 + SYNTAX Integer32 (-1..'7FFFFFFF'h)
2398 + MAX-ACCESS read-write
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.
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)."
2416 + ::= { ospfGeneralGroup 11 }
2418 + ospfMulticastExtensions OBJECT-TYPE
2420 + MAX-ACCESS read-write
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.
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-
2433 + Bit 1, if set, indicates that the router can
2434 + forward IP multicast datagrams between OSPF
2435 + areas (called inter-area multicast routing).
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-
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."
2450 + ::= { ospfGeneralGroup 12 }
2452 + ospfExitOverflowInterval OBJECT-TYPE
2453 + SYNTAX PositiveInteger
2454 + MAX-ACCESS read-write
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."
2464 + ::= { ospfGeneralGroup 13 }
2467 + ospfDemandExtensions OBJECT-TYPE
2469 + MAX-ACCESS read-write
2472 + "The router's support for demand routing."
2474 + "OSPF Version 2, Appendix on Demand Routing"
2475 + ::= { ospfGeneralGroup 14 }
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
2484 + ospfAreaTable OBJECT-TYPE
2485 + SYNTAX SEQUENCE OF OspfAreaEntry
2486 + MAX-ACCESS not-accessible
2489 + "Information describing the configured parame-
2490 + ters and cumulative statistics of the router's
2493 + "OSPF Version 2, Section 6 The Area Data Struc-
2498 + ospfAreaEntry OBJECT-TYPE
2499 + SYNTAX OspfAreaEntry
2500 + MAX-ACCESS not-accessible
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 }
2515 + ospfImportAsExtern
2519 + ospfAreaBdrRtrCount
2525 + ospfAreaLsaCksumSum
2533 + ospfAreaId OBJECT-TYPE
2535 + MAX-ACCESS read-only
2538 + "A 32-bit integer uniquely identifying an area.
2539 + Area ID 0.0.0.0 is used for the OSPF backbone."
2541 + "OSPF Version 2, Appendix C.2 Area parameters"
2542 + ::= { ospfAreaEntry 1 }
2545 + ospfAuthType OBJECT-TYPE
2548 + -- simplePassword (1)
2550 + -- reserved for specification by IANA (> 2)
2551 + MAX-ACCESS read-create
2554 + "The authentication type specified for an area.
2555 + Additional authentication types may be assigned
2556 + locally on a per Area basis."
2558 + "OSPF Version 2, Appendix E Authentication"
2559 + DEFVAL { 0 } -- no authentication, by default
2560 + ::= { ospfAreaEntry 2 }
2562 + ospfImportAsExtern OBJECT-TYPE
2564 + importExternal (1),
2565 + importNoExternal (2),
2568 + MAX-ACCESS read-create
2571 + "The area's support for importing AS external
2572 + link- state advertisements."
2574 + "OSPF Version 2, Appendix C.2 Area parameters"
2575 + DEFVAL { importExternal }
2576 + ::= { ospfAreaEntry 3 }
2579 + ospfSpfRuns OBJECT-TYPE
2581 + MAX-ACCESS read-only
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 }
2591 + ospfAreaBdrRtrCount OBJECT-TYPE
2593 + MAX-ACCESS read-only
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 }
2601 + ospfAsBdrRtrCount OBJECT-TYPE
2603 + MAX-ACCESS read-only
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
2610 + ::= { ospfAreaEntry 6 }
2613 + ospfAreaLsaCount OBJECT-TYPE
2615 + MAX-ACCESS read-only
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 }
2624 + ospfAreaLsaCksumSum OBJECT-TYPE
2626 + MAX-ACCESS read-only
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
2638 + ::= { ospfAreaEntry 8 }
2640 + ospfAreaSummary OBJECT-TYPE
2642 + noAreaSummary (1),
2643 + sendAreaSummary (2)
2645 + MAX-ACCESS read-create
2648 + "The variable ospfAreaSummary controls the im-
2649 + port of summary LSAs into stub areas. It has
2650 + no effect on other areas.
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-
2657 + If it is sendAreaSummary, the router will both
2658 + summarize and propagate summary LSAs."
2659 + DEFVAL { noAreaSummary }
2660 + ::= { ospfAreaEntry 9 }
2663 + ospfAreaStatus OBJECT-TYPE
2665 + MAX-ACCESS read-create
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 }
2675 +-- OSPF Area Default Metric Table
2677 +-- The OSPF Area Default Metric Table describes the metrics
2678 +-- that a default Area Border Router will advertise into a
2682 + ospfStubAreaTable OBJECT-TYPE
2683 + SYNTAX SEQUENCE OF OspfStubAreaEntry
2684 + MAX-ACCESS not-accessible
2687 + "The set of metrics that will be advertised by
2688 + a default Area Border Router into a stub area."
2690 + "OSPF Version 2, Appendix C.2, Area Parameters"
2694 + ospfStubAreaEntry OBJECT-TYPE
2695 + SYNTAX OspfStubAreaEntry
2696 + MAX-ACCESS not-accessible
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."
2703 + "OSPF Version 2, Appendix C.2, Area Parameters"
2704 + INDEX { ospfStubAreaId, ospfStubTOS }
2705 + ::= { ospfStubAreaTable 1 }
2707 +OspfStubAreaEntry ::=
2717 + ospfStubMetricType
2721 + ospfStubAreaId OBJECT-TYPE
2723 + MAX-ACCESS read-only
2726 + "The 32 bit identifier for the Stub Area. On
2727 + creation, this can be derived from the in-
2729 + ::= { ospfStubAreaEntry 1 }
2732 + ospfStubTOS OBJECT-TYPE
2734 + MAX-ACCESS read-only
2737 + "The Type of Service associated with the
2738 + metric. On creation, this can be derived from
2740 + ::= { ospfStubAreaEntry 2 }
2743 + ospfStubMetric OBJECT-TYPE
2745 + MAX-ACCESS read-create
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 }
2755 + ospfStubStatus OBJECT-TYPE
2757 + MAX-ACCESS read-create
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 }
2766 + ospfStubMetricType OBJECT-TYPE
2768 + ospfMetric (1), -- OSPF Metric
2769 + comparableCost (2), -- external type 1
2770 + nonComparable (3) -- external type 2
2772 + MAX-ACCESS read-create
2775 + "This variable displays the type of metric ad-
2776 + vertised as a default route."
2777 + DEFVAL { ospfMetric }
2778 + ::= { ospfStubAreaEntry 5 }
2780 +-- OSPF Link State Database
2782 +-- The Link State Database contains the Link State
2783 +-- Advertisements from throughout the areas that the
2784 +-- device is attached to.
2787 + ospfLsdbTable OBJECT-TYPE
2788 + SYNTAX SEQUENCE OF OspfLsdbEntry
2789 + MAX-ACCESS not-accessible
2792 + "The OSPF Process's Link State Database."
2794 + "OSPF Version 2, Section 12 Link State Adver-
2799 + ospfLsdbEntry OBJECT-TYPE
2800 + SYNTAX OspfLsdbEntry
2801 + MAX-ACCESS not-accessible
2804 + "A single Link State Advertisement."
2805 + INDEX { ospfLsdbAreaId, ospfLsdbType,
2806 + ospfLsdbLsid, ospfLsdbRouterId }
2807 + ::= { ospfLsdbTable 1 }
2825 + ospfLsdbAdvertisement
2828 + ospfLsdbAreaId OBJECT-TYPE
2830 + MAX-ACCESS read-only
2833 + "The 32 bit identifier of the Area from which
2834 + the LSA was received."
2836 + "OSPF Version 2, Appendix C.2 Area parameters"
2837 + ::= { ospfLsdbEntry 1 }
2839 +-- External Link State Advertisements are permitted
2840 +-- for backward compatibility, but should be displayed in
2841 +-- the ospfExtLsdbTable rather than here.
2843 + ospfLsdbType OBJECT-TYPE
2848 + asSummaryLink (4),
2849 + asExternalLink (5), -- but see ospfExtLsdbTable
2850 + multicastLink (6),
2851 + nssaExternalLink (7)
2853 + MAX-ACCESS read-only
2856 + "The type of the link state advertisement.
2857 + Each link state type has a separate advertise-
2860 + "OSPF Version 2, Appendix A.4.1 The Link State
2861 + Advertisement header"
2862 + ::= { ospfLsdbEntry 2 }
2864 + ospfLsdbLsid OBJECT-TYPE
2866 + MAX-ACCESS read-only
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."
2874 + "OSPF Version 2, Section 12.1.4 Link State ID"
2875 + ::= { ospfLsdbEntry 3 }
2876 + ospfLsdbRouterId OBJECT-TYPE
2878 + MAX-ACCESS read-only
2881 + "The 32 bit number that uniquely identifies the
2882 + originating router in the Autonomous System."
2884 + "OSPF Version 2, Appendix C.1 Global parameters"
2885 + ::= { ospfLsdbEntry 4 }
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.
2892 + ospfLsdbSequence OBJECT-TYPE
2894 + MAX-ACCESS read-only
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
2904 + "OSPF Version 2, Section 12.1.6 LS sequence
2906 + ::= { ospfLsdbEntry 5 }
2909 + ospfLsdbAge OBJECT-TYPE
2910 + SYNTAX Integer32 -- Should be 0..MaxAge
2911 + MAX-ACCESS read-only
2914 + "This field is the age of the link state adver-
2915 + tisement in seconds."
2917 + "OSPF Version 2, Section 12.1.1 LS age"
2918 + ::= { ospfLsdbEntry 6 }
2920 + ospfLsdbChecksum OBJECT-TYPE
2922 + MAX-ACCESS read-only
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."
2934 + "OSPF Version 2, Section 12.1.7 LS checksum"
2935 + ::= { ospfLsdbEntry 7 }
2938 + ospfLsdbAdvertisement OBJECT-TYPE
2939 + SYNTAX OCTET STRING (SIZE (1..65535))
2940 + MAX-ACCESS read-only
2943 + "The entire Link State Advertisement, including
2946 + "OSPF Version 2, Section 12 Link State Adver-
2948 + ::= { ospfLsdbEntry 8 }
2951 +-- Address Range Table
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
2959 + ospfAreaRangeTable OBJECT-TYPE
2960 + SYNTAX SEQUENCE OF OspfAreaRangeEntry
2961 + MAX-ACCESS not-accessible
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"
2970 + "OSPF Version 2, Appendix C.2 Area parameters"
2972 + ospfAreaRangeEntry OBJECT-TYPE
2973 + SYNTAX OspfAreaRangeEntry
2974 + MAX-ACCESS not-accessible
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"
2983 + "OSPF Version 2, Appendix C.2 Area parameters"
2984 + INDEX { ospfAreaRangeAreaId, ospfAreaRangeNet }
2985 + ::= { ospfAreaRangeTable 1 }
2987 +OspfAreaRangeEntry ::=
2989 + ospfAreaRangeAreaId
2995 + ospfAreaRangeStatus
2997 + ospfAreaRangeEffect
3001 + ospfAreaRangeAreaId OBJECT-TYPE
3003 + MAX-ACCESS read-only
3006 + "The Area the Address Range is to be found
3009 + "OSPF Version 2, Appendix C.2 Area parameters"
3010 + ::= { ospfAreaRangeEntry 1 }
3013 + ospfAreaRangeNet OBJECT-TYPE
3015 + MAX-ACCESS read-only
3018 + "The IP Address of the Net or Subnet indicated
3021 + "OSPF Version 2, Appendix C.2 Area parameters"
3022 + ::= { ospfAreaRangeEntry 2 }
3025 + ospfAreaRangeMask OBJECT-TYPE
3027 + MAX-ACCESS read-create
3030 + "The Subnet Mask that pertains to the Net or
3033 + "OSPF Version 2, Appendix C.2 Area parameters"
3034 + ::= { ospfAreaRangeEntry 3 }
3036 + ospfAreaRangeStatus OBJECT-TYPE
3038 + MAX-ACCESS read-create
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 }
3048 + ospfAreaRangeEffect OBJECT-TYPE
3050 + advertiseMatching (1),
3051 + doNotAdvertiseMatching (2)
3053 + MAX-ACCESS read-create
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 }
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.
3071 + ospfHostTable OBJECT-TYPE
3072 + SYNTAX SEQUENCE OF OspfHostEntry
3073 + MAX-ACCESS not-accessible
3076 + "The list of Hosts, and their metrics, that the
3077 + router will advertise as host routes."
3079 + "OSPF Version 2, Appendix C.6 Host route param-
3084 + ospfHostEntry OBJECT-TYPE
3085 + SYNTAX OspfHostEntry
3086 + MAX-ACCESS not-accessible
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 }
3108 + ospfHostIpAddress OBJECT-TYPE
3110 + MAX-ACCESS read-only
3113 + "The IP Address of the Host."
3115 + "OSPF Version 2, Appendix C.6 Host route parame-
3117 + ::= { ospfHostEntry 1 }
3120 + ospfHostTOS OBJECT-TYPE
3122 + MAX-ACCESS read-only
3125 + "The Type of Service of the route being config-
3128 + "OSPF Version 2, Appendix C.6 Host route parame-
3130 + ::= { ospfHostEntry 2 }
3133 + ospfHostMetric OBJECT-TYPE
3135 + MAX-ACCESS read-create
3138 + "The Metric to be advertised."
3140 + "OSPF Version 2, Appendix C.6 Host route parame-
3142 + ::= { ospfHostEntry 3 }
3144 + ospfHostStatus OBJECT-TYPE
3146 + MAX-ACCESS read-create
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 }
3156 + ospfHostAreaID OBJECT-TYPE
3158 + MAX-ACCESS read-only
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"
3165 + "OSPF Version 2, Appendix C.2 Area parameters"
3166 + ::= { ospfHostEntry 5 }
3169 +-- OSPF Interface Table
3171 +-- The OSPF Interface Table augments the ipAddrTable
3172 +-- with OSPF specific information.
3174 + ospfIfTable OBJECT-TYPE
3175 + SYNTAX SEQUENCE OF OspfIfEntry
3176 + MAX-ACCESS not-accessible
3179 + "The OSPF Interface Table describes the inter-
3180 + faces from the viewpoint of OSPF."
3182 + "OSPF Version 2, Appendix C.3 Router interface
3187 + ospfIfEntry OBJECT-TYPE
3188 + SYNTAX OspfIfEntry
3189 + MAX-ACCESS not-accessible
3192 + "The OSPF Interface Entry describes one inter-
3193 + face from the viewpoint of OSPF."
3194 + INDEX { ospfIfIpAddress, ospfAddressLessIf }
3195 + ::= { ospfIfTable 1 }
3210 + DesignatedRouterPriority,
3211 + ospfIfTransitDelay
3213 + ospfIfRetransInterval
3215 + ospfIfHelloInterval
3217 + ospfIfRtrDeadInterval
3219 + ospfIfPollInterval
3223 + ospfIfDesignatedRouter
3225 + ospfIfBackupDesignatedRouter
3235 + ospfIfMulticastForwarding
3241 + ospfIfIpAddress OBJECT-TYPE
3243 + MAX-ACCESS read-only
3246 + "The IP address of this OSPF interface."
3247 + ::= { ospfIfEntry 1 }
3249 + ospfAddressLessIf OBJECT-TYPE
3251 + MAX-ACCESS read-only
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
3262 + MAX-ACCESS read-create
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 }
3271 + ospfIfType OBJECT-TYPE
3276 + pointToMultipoint (5)
3278 + MAX-ACCESS read-create
3281 + "The OSPF interface type.
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 }
3293 + ospfIfAdminStat OBJECT-TYPE
3295 + MAX-ACCESS read-create
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 }
3306 + ospfIfRtrPriority OBJECT-TYPE
3307 + SYNTAX DesignatedRouterPriority
3308 + MAX-ACCESS read-create
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
3320 + ::= { ospfIfEntry 6 }
3323 + ospfIfTransitDelay OBJECT-TYPE
3325 + MAX-ACCESS read-create
3328 + "The estimated number of seconds it takes to
3329 + transmit a link state update packet over this
3332 + ::= { ospfIfEntry 7 }
3335 + ospfIfRetransInterval OBJECT-TYPE
3337 + MAX-ACCESS read-create
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."
3346 + ::= { ospfIfEntry 8 }
3349 + ospfIfHelloInterval OBJECT-TYPE
3351 + MAX-ACCESS read-create
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."
3359 + ::= { ospfIfEntry 9 }
3362 + ospfIfRtrDeadInterval OBJECT-TYPE
3363 + SYNTAX PositiveInteger
3364 + MAX-ACCESS read-create
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."
3374 + ::= { ospfIfEntry 10 }
3377 + ospfIfPollInterval OBJECT-TYPE
3378 + SYNTAX PositiveInteger
3379 + MAX-ACCESS read-create
3382 + "The larger time interval, in seconds, between
3383 + the Hello packets sent to an inactive non-
3384 + broadcast multi- access neighbor."
3386 + ::= { ospfIfEntry 11 }
3389 + ospfIfState OBJECT-TYPE
3395 + designatedRouter (5),
3396 + backupDesignatedRouter (6),
3397 + otherDesignatedRouter (7)
3399 + MAX-ACCESS read-only
3402 + "The OSPF Interface State."
3404 + ::= { ospfIfEntry 12 }
3407 + ospfIfDesignatedRouter OBJECT-TYPE
3409 + MAX-ACCESS read-only
3412 + "The IP Address of the Designated Router."
3413 + DEFVAL { '00000000'H } -- 0.0.0.0
3414 + ::= { ospfIfEntry 13 }
3417 + ospfIfBackupDesignatedRouter OBJECT-TYPE
3419 + MAX-ACCESS read-only
3422 + "The IP Address of the Backup Designated
3424 + DEFVAL { '00000000'H } -- 0.0.0.0
3425 + ::= { ospfIfEntry 14 }
3427 + ospfIfEvents OBJECT-TYPE
3429 + MAX-ACCESS read-only
3432 + "The number of times this OSPF interface has
3433 + changed its state, or an error has occurred."
3434 + ::= { ospfIfEntry 15 }
3437 + ospfIfAuthKey OBJECT-TYPE
3438 + SYNTAX OCTET STRING (SIZE (0..256))
3439 + MAX-ACCESS read-create
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.
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-
3454 + When read, ospfIfAuthKey always returns an Oc-
3455 + tet String of length zero."
3457 + "OSPF Version 2, Section 9 The Interface Data
3459 + DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0
3460 + ::= { ospfIfEntry 16 }
3462 + ospfIfStatus OBJECT-TYPE
3464 + MAX-ACCESS read-create
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 }
3474 + ospfIfMulticastForwarding OBJECT-TYPE
3476 + blocked (1), -- no multicast forwarding
3477 + multicast (2), -- using multicast address
3478 + unicast (3) -- to each OSPF neighbor
3480 + MAX-ACCESS read-create
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 }
3494 + ospfIfDemand OBJECT-TYPE
3496 + MAX-ACCESS read-create
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."
3504 + ::= { ospfIfEntry 19 }
3507 + ospfIfAuthType OBJECT-TYPE
3508 + SYNTAX INTEGER (0..255)
3510 + -- simplePassword (1)
3512 + -- reserved for specification by IANA (> 2)
3513 + MAX-ACCESS read-create
3516 + "The authentication type specified for an in-
3517 + terface. Additional authentication types may
3518 + be assigned locally."
3520 + "OSPF Version 2, Appendix E Authentication"
3521 + DEFVAL { 0 } -- no authentication, by default
3522 + ::= { ospfIfEntry 20 }
3525 +-- OSPF Interface Metric Table
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
3532 +-- Types of service, as defined by RFC 791, have the ability
3533 +-- to request low delay, high bandwidth, or reliable linkage.
3535 +-- For the purposes of this specification, the measure of
3538 +-- Metric = 10^8 / ifSpeed
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:
3544 +-- Network Type/bit rate Metric
3547 +-- Ethernet/802.3 10
3555 +-- Routes that are not specified use the default (TOS 0) metric
3557 + ospfIfMetricTable OBJECT-TYPE
3558 + SYNTAX SEQUENCE OF OspfIfMetricEntry
3559 + MAX-ACCESS not-accessible
3562 + "The TOS metrics for a non-virtual interface
3563 + identified by the interface index."
3565 + "OSPF Version 2, Appendix C.3 Router interface
3569 + ospfIfMetricEntry OBJECT-TYPE
3570 + SYNTAX OspfIfMetricEntry
3571 + MAX-ACCESS not-accessible
3574 + "A particular TOS metric for a non-virtual in-
3575 + terface identified by the interface index."
3577 + "OSPF Version 2, Appendix C.3 Router interface
3579 + INDEX { ospfIfMetricIpAddress,
3580 + ospfIfMetricAddressLessIf,
3582 + ::= { ospfIfMetricTable 1 }
3584 +OspfIfMetricEntry ::=
3586 + ospfIfMetricIpAddress
3588 + ospfIfMetricAddressLessIf
3594 + ospfIfMetricStatus
3598 + ospfIfMetricIpAddress OBJECT-TYPE
3600 + MAX-ACCESS read-only
3603 + "The IP address of this OSPF interface. On row
3604 + creation, this can be derived from the in-
3606 + ::= { ospfIfMetricEntry 1 }
3608 + ospfIfMetricAddressLessIf OBJECT-TYPE
3610 + MAX-ACCESS read-only
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 }
3622 + ospfIfMetricTOS OBJECT-TYPE
3624 + MAX-ACCESS read-only
3627 + "The type of service metric being referenced.
3628 + On row creation, this can be derived from the
3630 + ::= { ospfIfMetricEntry 3 }
3633 + ospfIfMetricValue OBJECT-TYPE
3635 + MAX-ACCESS read-create
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 }
3643 + ospfIfMetricStatus OBJECT-TYPE
3645 + MAX-ACCESS read-create
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 }
3655 +-- OSPF Virtual Interface Table
3657 +-- The Virtual Interface Table describes the virtual
3658 +-- links that the OSPF Process is configured to
3661 + ospfVirtIfTable OBJECT-TYPE
3662 + SYNTAX SEQUENCE OF OspfVirtIfEntry
3663 + MAX-ACCESS not-accessible
3666 + "Information about this router's virtual inter-
3669 + "OSPF Version 2, Appendix C.4 Virtual link
3674 + ospfVirtIfEntry OBJECT-TYPE
3675 + SYNTAX OspfVirtIfEntry
3676 + MAX-ACCESS not-accessible
3679 + "Information about a single Virtual Interface."
3680 + INDEX { ospfVirtIfAreaId, ospfVirtIfNeighbor }
3681 + ::= { ospfVirtIfTable 1 }
3683 +OspfVirtIfEntry ::=
3687 + ospfVirtIfNeighbor
3689 + ospfVirtIfTransitDelay
3691 + ospfVirtIfRetransInterval
3693 + ospfVirtIfHelloInterval
3695 + ospfVirtIfRtrDeadInterval
3701 + ospfVirtIfAuthType
3709 + ospfVirtIfAreaId OBJECT-TYPE
3711 + MAX-ACCESS read-only
3714 + "The Transit Area that the Virtual Link
3715 + traverses. By definition, this is not 0.0.0.0"
3716 + ::= { ospfVirtIfEntry 1 }
3719 + ospfVirtIfNeighbor OBJECT-TYPE
3721 + MAX-ACCESS read-only
3724 + "The Router ID of the Virtual Neighbor."
3725 + ::= { ospfVirtIfEntry 2 }
3728 + ospfVirtIfTransitDelay OBJECT-TYPE
3730 + MAX-ACCESS read-create
3733 + "The estimated number of seconds it takes to
3734 + transmit a link- state update packet over this
3737 + ::= { ospfVirtIfEntry 3 }
3740 + ospfVirtIfRetransInterval OBJECT-TYPE
3742 + MAX-ACCESS read-create
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-
3753 + ::= { ospfVirtIfEntry 4 }
3756 + ospfVirtIfHelloInterval OBJECT-TYPE
3758 + MAX-ACCESS read-create
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."
3766 + ::= { ospfVirtIfEntry 5 }
3769 + ospfVirtIfRtrDeadInterval OBJECT-TYPE
3770 + SYNTAX PositiveInteger
3771 + MAX-ACCESS read-create
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-
3781 + ::= { ospfVirtIfEntry 6 }
3784 + ospfVirtIfState OBJECT-TYPE
3786 + down (1), -- these use the same encoding
3787 + pointToPoint (4) -- as the ospfIfTable
3789 + MAX-ACCESS read-only
3792 + "OSPF virtual interface states."
3794 + ::= { ospfVirtIfEntry 7 }
3797 + ospfVirtIfEvents OBJECT-TYPE
3799 + MAX-ACCESS read-only
3802 + "The number of state changes or error events on
3803 + this Virtual Link"
3804 + ::= { ospfVirtIfEntry 8 }
3807 + ospfVirtIfAuthKey OBJECT-TYPE
3808 + SYNTAX OCTET STRING (SIZE(0..256))
3809 + MAX-ACCESS read-create
3812 + "If Authentication Type is simplePassword, the
3813 + device will left adjust and zero fill to 8 oc-
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-
3823 + When read, ospfVifAuthKey always returns a
3824 + string of length zero."
3826 + "OSPF Version 2, Section 9 The Interface Data
3828 + DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0
3829 + ::= { ospfVirtIfEntry 9 }
3832 + ospfVirtIfStatus OBJECT-TYPE
3834 + MAX-ACCESS read-create
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 }
3844 + ospfVirtIfAuthType OBJECT-TYPE
3845 + SYNTAX INTEGER (0..255)
3847 + -- simplePassword (1)
3849 + -- reserved for specification by IANA (> 2)
3850 + MAX-ACCESS read-create
3853 + "The authentication type specified for a virtu-
3854 + al interface. Additional authentication types
3855 + may be assigned locally."
3857 + "OSPF Version 2, Appendix E Authentication"
3858 + DEFVAL { 0 } -- no authentication, by default
3859 + ::= { ospfVirtIfEntry 11 }
3862 +-- OSPF Neighbor Table
3864 +-- The OSPF Neighbor Table describes all neighbors in
3865 +-- the locality of the subject router.
3867 + ospfNbrTable OBJECT-TYPE
3868 + SYNTAX SEQUENCE OF OspfNbrEntry
3869 + MAX-ACCESS not-accessible
3872 + "A table of non-virtual neighbor information."
3874 + "OSPF Version 2, Section 10 The Neighbor Data
3879 + ospfNbrEntry OBJECT-TYPE
3880 + SYNTAX OspfNbrEntry
3881 + MAX-ACCESS not-accessible
3884 + "The information regarding a single neighbor."
3886 + "OSPF Version 2, Section 10 The Neighbor Data
3888 + INDEX { ospfNbrIpAddr, ospfNbrAddressLessIndex }
3889 + ::= { ospfNbrTable 1 }
3895 + ospfNbrAddressLessIndex
3902 + DesignatedRouterPriority,
3907 + ospfNbrLsRetransQLen
3911 + ospfNbmaNbrPermanence
3913 + ospfNbrHelloSuppressed
3917 + ospfNbrIpAddr OBJECT-TYPE
3919 + MAX-ACCESS read-only
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 }
3929 + ospfNbrAddressLessIndex OBJECT-TYPE
3930 + SYNTAX InterfaceIndex
3931 + MAX-ACCESS read-only
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
3939 + ::= { ospfNbrEntry 2 }
3942 + ospfNbrRtrId OBJECT-TYPE
3944 + MAX-ACCESS read-only
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 }
3954 + ospfNbrOptions OBJECT-TYPE
3956 + MAX-ACCESS read-only
3959 + "A Bit Mask corresponding to the neighbor's op-
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.
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.
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
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."
3982 + "OSPF Version 2, Section 12.1.2 Options"
3984 + ::= { ospfNbrEntry 4 }
3987 + ospfNbrPriority OBJECT-TYPE
3988 + SYNTAX DesignatedRouterPriority
3989 + MAX-ACCESS read-create
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
3998 + ::= { ospfNbrEntry 5 }
4001 + ospfNbrState OBJECT-TYPE
4007 + exchangeStart (5),
4012 + MAX-ACCESS read-only
4015 + "The State of the relationship with this Neigh-
4018 + "OSPF Version 2, Section 10.1 Neighbor States"
4020 + ::= { ospfNbrEntry 6 }
4023 + ospfNbrEvents OBJECT-TYPE
4025 + MAX-ACCESS read-only
4028 + "The number of times this neighbor relationship
4029 + has changed state, or an error has occurred."
4030 + ::= { ospfNbrEntry 7 }
4033 + ospfNbrLsRetransQLen OBJECT-TYPE
4035 + MAX-ACCESS read-only
4038 + "The current length of the retransmission
4040 + ::= { ospfNbrEntry 8 }
4043 + ospfNbmaNbrStatus OBJECT-TYPE
4045 + MAX-ACCESS read-create
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 }
4055 + ospfNbmaNbrPermanence OBJECT-TYPE
4057 + dynamic (1), -- learned through protocol
4058 + permanent (2) -- configured address
4060 + MAX-ACCESS read-only
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 }
4070 + ospfNbrHelloSuppressed OBJECT-TYPE
4072 + MAX-ACCESS read-only
4075 + "Indicates whether Hellos are being suppressed
4077 + ::= { ospfNbrEntry 11 }
4080 +-- OSPF Virtual Neighbor Table
4082 +-- This table describes all virtual neighbors.
4083 +-- Since Virtual Links are configured in the
4084 +-- virtual interface table, this table is read-only.
4086 + ospfVirtNbrTable OBJECT-TYPE
4087 + SYNTAX SEQUENCE OF OspfVirtNbrEntry
4088 + MAX-ACCESS not-accessible
4091 + "A table of virtual neighbor information."
4093 + "OSPF Version 2, Section 15 Virtual Links"
4097 + ospfVirtNbrEntry OBJECT-TYPE
4098 + SYNTAX OspfVirtNbrEntry
4099 + MAX-ACCESS not-accessible
4102 + "Virtual neighbor information."
4103 + INDEX { ospfVirtNbrArea, ospfVirtNbrRtrId }
4104 + ::= { ospfVirtNbrTable 1 }
4106 +OspfVirtNbrEntry ::=
4114 + ospfVirtNbrOptions
4120 + ospfVirtNbrLsRetransQLen
4122 + ospfVirtNbrHelloSuppressed
4126 + ospfVirtNbrArea OBJECT-TYPE
4128 + MAX-ACCESS read-only
4131 + "The Transit Area Identifier."
4132 + ::= { ospfVirtNbrEntry 1 }
4135 + ospfVirtNbrRtrId OBJECT-TYPE
4137 + MAX-ACCESS read-only
4140 + "A 32-bit integer uniquely identifying the
4141 + neighboring router in the Autonomous System."
4142 + ::= { ospfVirtNbrEntry 2 }
4145 + ospfVirtNbrIpAddr OBJECT-TYPE
4147 + MAX-ACCESS read-only
4150 + "The IP address this Virtual Neighbor is us-
4152 + ::= { ospfVirtNbrEntry 3 }
4155 + ospfVirtNbrOptions OBJECT-TYPE
4157 + MAX-ACCESS read-only
4160 + "A Bit Mask corresponding to the neighbor's op-
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.
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
4178 + exchangeStart (5),
4183 + MAX-ACCESS read-only
4186 + "The state of the Virtual Neighbor Relation-
4188 + ::= { ospfVirtNbrEntry 5 }
4191 + ospfVirtNbrEvents OBJECT-TYPE
4193 + MAX-ACCESS read-only
4196 + "The number of times this virtual link has
4197 + changed its state, or an error has occurred."
4198 + ::= { ospfVirtNbrEntry 6 }
4201 + ospfVirtNbrLsRetransQLen OBJECT-TYPE
4203 + MAX-ACCESS read-only
4206 + "The current length of the retransmission
4208 + ::= { ospfVirtNbrEntry 7 }
4211 + ospfVirtNbrHelloSuppressed OBJECT-TYPE
4213 + MAX-ACCESS read-only
4216 + "Indicates whether Hellos are being suppressed
4218 + ::= { ospfVirtNbrEntry 8 }
4220 +-- OSPF Link State Database, External
4222 +-- The Link State Database contains the Link State
4223 +-- Advertisements from throughout the areas that the
4224 +-- device is attached to.
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.
4232 + ospfExtLsdbTable OBJECT-TYPE
4233 + SYNTAX SEQUENCE OF OspfExtLsdbEntry
4234 + MAX-ACCESS not-accessible
4237 + "The OSPF Process's Links State Database."
4239 + "OSPF Version 2, Section 12 Link State Adver-
4244 + ospfExtLsdbEntry OBJECT-TYPE
4245 + SYNTAX OspfExtLsdbEntry
4246 + MAX-ACCESS not-accessible
4249 + "A single Link State Advertisement."
4250 + INDEX { ospfExtLsdbType, ospfExtLsdbLsid, ospfExtLsdbRouterId }
4251 + ::= { ospfExtLsdbTable 1 }
4253 +OspfExtLsdbEntry ::=
4259 + ospfExtLsdbRouterId
4261 + ospfExtLsdbSequence
4265 + ospfExtLsdbChecksum
4267 + ospfExtLsdbAdvertisement
4271 + ospfExtLsdbType OBJECT-TYPE
4273 + asExternalLink (5)
4275 + MAX-ACCESS read-only
4278 + "The type of the link state advertisement.
4279 + Each link state type has a separate advertise-
4282 + "OSPF Version 2, Appendix A.4.1 The Link State
4283 + Advertisement header"
4284 + ::= { ospfExtLsdbEntry 1 }
4287 + ospfExtLsdbLsid OBJECT-TYPE
4289 + MAX-ACCESS read-only
4292 + "The Link State ID is an LS Type Specific field
4293 + containing either a Router ID or an IP Address;
4294 + it identifies the piece of the routing domain
4295 + that is being described by the advertisement."
4297 + "OSPF Version 2, Section 12.1.4 Link State ID"
4298 + ::= { ospfExtLsdbEntry 2 }
4301 + ospfExtLsdbRouterId OBJECT-TYPE
4303 + MAX-ACCESS read-only
4306 + "The 32 bit number that uniquely identifies the
4307 + originating router in the Autonomous System."
4309 + "OSPF Version 2, Appendix C.1 Global parameters"
4310 + ::= { ospfExtLsdbEntry 3 }
4312 +-- Note that the OSPF Sequence Number is a 32 bit signed
4313 +-- integer. It starts with the value '80000001'h,
4314 +-- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h
4315 +-- Thus, a typical sequence number will be very negative.
4316 + ospfExtLsdbSequence OBJECT-TYPE
4318 + MAX-ACCESS read-only
4321 + "The sequence number field is a signed 32-bit
4322 + integer. It is used to detect old and dupli-
4323 + cate link state advertisements. The space of
4324 + sequence numbers is linearly ordered. The
4325 + larger the sequence number the more recent the
4328 + "OSPF Version 2, Section 12.1.6 LS sequence
4330 + ::= { ospfExtLsdbEntry 4 }
4333 + ospfExtLsdbAge OBJECT-TYPE
4334 + SYNTAX Integer32 -- Should be 0..MaxAge
4335 + MAX-ACCESS read-only
4338 + "This field is the age of the link state adver-
4339 + tisement in seconds."
4341 + "OSPF Version 2, Section 12.1.1 LS age"
4342 + ::= { ospfExtLsdbEntry 5 }
4345 + ospfExtLsdbChecksum OBJECT-TYPE
4347 + MAX-ACCESS read-only
4350 + "This field is the checksum of the complete
4351 + contents of the advertisement, excepting the
4352 + age field. The age field is excepted so that
4353 + an advertisement's age can be incremented
4354 + without updating the checksum. The checksum
4355 + used is the same that is used for ISO connec-
4356 + tionless datagrams; it is commonly referred to
4357 + as the Fletcher checksum."
4359 + "OSPF Version 2, Section 12.1.7 LS checksum"
4360 + ::= { ospfExtLsdbEntry 6 }
4363 + ospfExtLsdbAdvertisement OBJECT-TYPE
4364 + SYNTAX OCTET STRING (SIZE(36))
4365 + MAX-ACCESS read-only
4368 + "The entire Link State Advertisement, including
4371 + "OSPF Version 2, Section 12 Link State Adver-
4373 + ::= { ospfExtLsdbEntry 7 }
4376 +-- OSPF Use of the CIDR Route Table
4378 +ospfRouteGroup OBJECT IDENTIFIER ::= { ospf 13 }
4380 +-- The IP Forwarding Table defines a number of objects for use by
4381 +-- the routing protocol to externalize its information. Most of
4382 +-- the variables (ipForwardDest, ipForwardMask, ipForwardPolicy,
4383 +-- ipForwardNextHop, ipForwardIfIndex, ipForwardType,
4384 +-- ipForwardProto, ipForwardAge, and ipForwardNextHopAS) are
4387 +-- Those that leave some discretion are defined here.
4389 +-- ipCidrRouteProto is, of course, ospf (13).
4391 +-- ipCidrRouteAge is the time since the route was first calculated,
4392 +-- as opposed to the time since the last SPF run.
4394 +-- ipCidrRouteInfo is an OBJECT IDENTIFIER for use by the routing
4395 +-- protocol. The following values shall be found there depending
4396 +-- on the way the route was calculated.
4398 +ospfIntraArea OBJECT IDENTIFIER ::= { ospfRouteGroup 1 }
4399 +ospfInterArea OBJECT IDENTIFIER ::= { ospfRouteGroup 2 }
4400 +ospfExternalType1 OBJECT IDENTIFIER ::= { ospfRouteGroup 3 }
4401 +ospfExternalType2 OBJECT IDENTIFIER ::= { ospfRouteGroup 4 }
4403 +-- ipCidrRouteMetric1 is, by definition, the primary routing
4404 +-- metric. Therefore, it should be the metric that route
4405 +-- selection is based on. For intra-area and inter-area routes,
4406 +-- it is an OSPF metric. For External Type 1 (comparable value)
4407 +-- routes, it is an OSPF metric plus the External Metric. For
4408 +-- external Type 2 (non-comparable value) routes, it is the
4409 +-- external metric.
4411 +-- ipCidrRouteMetric2 is, by definition, a secondary routing
4412 +-- metric. Therefore, it should be the metric that breaks a tie
4413 +-- among routes having equal metric1 values and the same
4414 +-- calculation rule. For intra-area, inter-area routes, and
4415 +-- External Type 1 (comparable value) routes, it is unused. For
4416 +-- external Type 2 (non-comparable value) routes, it is the metric
4417 +-- to the AS border router.
4419 +-- ipCidrRouteMetric3, ipCidrRouteMetric4, and ipCidrRouteMetric5 are
4423 +-- The OSPF Area Aggregate Table
4425 +-- This table replaces the OSPF Area Summary Table, being an
4426 +-- extension of that for CIDR routers.
4428 + ospfAreaAggregateTable OBJECT-TYPE
4429 + SYNTAX SEQUENCE OF OspfAreaAggregateEntry
4430 + MAX-ACCESS not-accessible
4433 + "A range of IP addresses specified by an IP
4434 + address/IP network mask pair. For example,
4435 + class B address range of X.X.X.X with a network
4436 + mask of 255.255.0.0 includes all IP addresses
4437 + from X.X.0.0 to X.X.255.255. Note that if
4438 + ranges are configured such that one range sub-
4439 + sumes another range (e.g., 10.0.0.0 mask
4440 + 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the
4441 + most specific match is the preferred one."
4443 + "OSPF Version 2, Appendix C.2 Area parameters"
4447 + ospfAreaAggregateEntry OBJECT-TYPE
4448 + SYNTAX OspfAreaAggregateEntry
4449 + MAX-ACCESS not-accessible
4452 + "A range of IP addresses specified by an IP
4453 + address/IP network mask pair. For example,
4454 + class B address range of X.X.X.X with a network
4455 + mask of 255.255.0.0 includes all IP addresses
4456 + from X.X.0.0 to X.X.255.255. Note that if
4457 + ranges are range configured such that one range
4458 + subsumes another range (e.g., 10.0.0.0 mask
4459 + 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the
4460 + most specific match is the preferred one."
4462 + "OSPF Version 2, Appendix C.2 Area parameters"
4463 + INDEX { ospfAreaAggregateAreaID, ospfAreaAggregateLsdbType,
4464 + ospfAreaAggregateNet, ospfAreaAggregateMask }
4465 + ::= { ospfAreaAggregateTable 1 }
4468 +OspfAreaAggregateEntry ::=
4470 + ospfAreaAggregateAreaID
4472 + ospfAreaAggregateLsdbType
4474 + ospfAreaAggregateNet
4476 + ospfAreaAggregateMask
4478 + ospfAreaAggregateStatus
4480 + ospfAreaAggregateEffect
4484 + ospfAreaAggregateAreaID OBJECT-TYPE
4486 + MAX-ACCESS read-only
4489 + "The Area the Address Aggregate is to be found
4492 + "OSPF Version 2, Appendix C.2 Area parameters"
4493 + ::= { ospfAreaAggregateEntry 1 }
4496 + ospfAreaAggregateLsdbType OBJECT-TYPE
4499 + nssaExternalLink (7)
4501 + MAX-ACCESS read-only
4504 + "The type of the Address Aggregate. This field
4505 + specifies the Lsdb type that this Address Ag-
4506 + gregate applies to."
4508 + "OSPF Version 2, Appendix A.4.1 The Link State
4509 + Advertisement header"
4510 + ::= { ospfAreaAggregateEntry 2 }
4513 + ospfAreaAggregateNet OBJECT-TYPE
4515 + MAX-ACCESS read-only
4518 + "The IP Address of the Net or Subnet indicated
4521 + "OSPF Version 2, Appendix C.2 Area parameters"
4522 + ::= { ospfAreaAggregateEntry 3 }
4525 + ospfAreaAggregateMask OBJECT-TYPE
4527 + MAX-ACCESS read-only
4530 + "The Subnet Mask that pertains to the Net or
4533 + "OSPF Version 2, Appendix C.2 Area parameters"
4534 + ::= { ospfAreaAggregateEntry 4 }
4537 + ospfAreaAggregateStatus OBJECT-TYPE
4539 + MAX-ACCESS read-create
4542 + "This variable displays the status of the en-
4543 + try. Setting it to 'invalid' has the effect of
4544 + rendering it inoperative. The internal effect
4545 + (row removal) is implementation dependent."
4546 + ::= { ospfAreaAggregateEntry 5 }
4549 + ospfAreaAggregateEffect OBJECT-TYPE
4551 + advertiseMatching (1),
4552 + doNotAdvertiseMatching (2)
4554 + MAX-ACCESS read-create
4557 + "Subnets subsumed by ranges either trigger the
4558 + advertisement of the indicated aggregate (ad-
4559 + vertiseMatching), or result in the subnet's not
4560 + being advertised at all outside the area."
4561 + DEFVAL { advertiseMatching }
4562 + ::= { ospfAreaAggregateEntry 6 }
4565 +-- conformance information
4567 +ospfConformance OBJECT IDENTIFIER ::= { ospf 15 }
4569 +ospfGroups OBJECT IDENTIFIER ::= { ospfConformance 1 }
4570 +ospfCompliances OBJECT IDENTIFIER ::= { ospfConformance 2 }
4572 +-- compliance statements
4574 + ospfCompliance MODULE-COMPLIANCE
4577 + "The compliance statement "
4578 + MODULE -- this module
4579 + MANDATORY-GROUPS {
4582 + ospfStubAreaGroup,
4584 + ospfIfMetricGroup,
4588 + ospfAreaAggregateGroup
4590 + ::= { ospfCompliances 1 }
4593 +-- units of conformance
4595 + ospfBasicGroup OBJECT-GROUP
4599 + ospfVersionNumber,
4600 + ospfAreaBdrRtrStatus,
4601 + ospfASBdrRtrStatus,
4602 + ospfExternLsaCount,
4603 + ospfExternLsaCksumSum,
4605 + ospfOriginateNewLsas,
4608 + ospfMulticastExtensions,
4609 + ospfExitOverflowInterval,
4610 + ospfDemandExtensions
4614 + "These objects are required for OSPF systems."
4615 + ::= { ospfGroups 1 }
4618 + ospfAreaGroup OBJECT-GROUP
4621 + ospfImportAsExtern,
4623 + ospfAreaBdrRtrCount,
4624 + ospfAsBdrRtrCount,
4626 + ospfAreaLsaCksumSum,
4632 + "These objects are required for OSPF systems
4633 + supporting areas."
4634 + ::= { ospfGroups 2 }
4637 + ospfStubAreaGroup OBJECT-GROUP
4643 + ospfStubMetricType
4647 + "These objects are required for OSPF systems
4648 + supporting stub areas."
4649 + ::= { ospfGroups 3 }
4652 + ospfLsdbGroup OBJECT-GROUP
4661 + ospfLsdbAdvertisement
4665 + "These objects are required for OSPF systems
4666 + that display their link state database."
4667 + ::= { ospfGroups 4 }
4670 + ospfAreaRangeGroup OBJECT-GROUP
4672 + ospfAreaRangeAreaId,
4674 + ospfAreaRangeMask,
4675 + ospfAreaRangeStatus,
4676 + ospfAreaRangeEffect
4680 + "These objects are required for non-CIDR OSPF
4681 + systems that support multiple areas."
4682 + ::= { ospfGroups 5 }
4685 + ospfHostGroup OBJECT-GROUP
4687 + ospfHostIpAddress,
4695 + "These objects are required for OSPF systems
4696 + that support attached hosts."
4697 + ::= { ospfGroups 6 }
4700 + ospfIfGroup OBJECT-GROUP
4703 + ospfAddressLessIf,
4707 + ospfIfRtrPriority,
4708 + ospfIfTransitDelay,
4709 + ospfIfRetransInterval,
4710 + ospfIfHelloInterval,
4711 + ospfIfRtrDeadInterval,
4712 + ospfIfPollInterval,
4714 + ospfIfDesignatedRouter,
4715 + ospfIfBackupDesignatedRouter,
4720 + ospfIfMulticastForwarding,
4725 + "These objects are required for OSPF systems."
4726 + ::= { ospfGroups 7 }
4729 + ospfIfMetricGroup OBJECT-GROUP
4731 + ospfIfMetricIpAddress,
4732 + ospfIfMetricAddressLessIf,
4734 + ospfIfMetricValue,
4735 + ospfIfMetricStatus
4739 + "These objects are required for OSPF systems."
4740 + ::= { ospfGroups 8 }
4743 + ospfVirtIfGroup OBJECT-GROUP
4746 + ospfVirtIfNeighbor,
4747 + ospfVirtIfTransitDelay,
4748 + ospfVirtIfRetransInterval,
4749 + ospfVirtIfHelloInterval,
4750 + ospfVirtIfRtrDeadInterval,
4753 + ospfVirtIfAuthType,
4754 + ospfVirtIfAuthKey,
4759 + "These objects are required for OSPF systems."
4760 + ::= { ospfGroups 9 }
4763 + ospfNbrGroup OBJECT-GROUP
4766 + ospfNbrAddressLessIndex,
4772 + ospfNbrLsRetransQLen,
4773 + ospfNbmaNbrStatus,
4774 + ospfNbmaNbrPermanence,
4775 + ospfNbrHelloSuppressed
4779 + "These objects are required for OSPF systems."
4780 + ::= { ospfGroups 10 }
4783 + ospfVirtNbrGroup OBJECT-GROUP
4787 + ospfVirtNbrIpAddr,
4788 + ospfVirtNbrOptions,
4790 + ospfVirtNbrEvents,
4791 + ospfVirtNbrLsRetransQLen,
4792 + ospfVirtNbrHelloSuppressed
4796 + "These objects are required for OSPF systems."
4797 + ::= { ospfGroups 11 }
4800 + ospfExtLsdbGroup OBJECT-GROUP
4804 + ospfExtLsdbRouterId,
4805 + ospfExtLsdbSequence,
4807 + ospfExtLsdbChecksum,
4808 + ospfExtLsdbAdvertisement
4812 + "These objects are required for OSPF systems
4813 + that display their link state database."
4814 + ::= { ospfGroups 12 }
4817 + ospfAreaAggregateGroup OBJECT-GROUP
4819 + ospfAreaAggregateAreaID,
4820 + ospfAreaAggregateLsdbType,
4821 + ospfAreaAggregateNet,
4822 + ospfAreaAggregateMask,
4823 + ospfAreaAggregateStatus,
4824 + ospfAreaAggregateEffect
4828 + "These objects are required for OSPF systems."
4829 + ::= { ospfGroups 13 }
4832 diff -ruN net-snmp-5.4.1.orig/mibs/OSPF-TRAP-MIB.txt net-snmp-5.4.1/mibs/OSPF-TRAP-MIB.txt
4833 --- net-snmp-5.4.1.orig/mibs/OSPF-TRAP-MIB.txt 1970-01-01 01:00:00.000000000 +0100
4834 +++ net-snmp-5.4.1/mibs/OSPF-TRAP-MIB.txt 2007-09-20 16:30:52.000000000 +0200
4836 +OSPF-TRAP-MIB DEFINITIONS ::= BEGIN
4839 + MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, IpAddress
4841 + MODULE-COMPLIANCE, OBJECT-GROUP
4843 + ospfRouterId, ospfIfIpAddress, ospfAddressLessIf, ospfIfState,
4844 + ospfVirtIfAreaId, ospfVirtIfNeighbor, ospfVirtIfState,
4845 + ospfNbrIpAddr, ospfNbrAddressLessIndex, ospfNbrRtrId,
4846 + ospfNbrState, ospfVirtNbrArea, ospfVirtNbrRtrId, ospfVirtNbrState,
4847 + ospfLsdbType, ospfLsdbLsid, ospfLsdbRouterId, ospfLsdbAreaId,
4848 + ospfExtLsdbLimit, ospf
4851 + ospfTrap MODULE-IDENTITY
4852 + LAST-UPDATED "9501201225Z" -- Fri Jan 20 12:25:50 PST 1995
4853 + ORGANIZATION "IETF OSPF Working Group"
4856 + Postal: Cisco Systems
4858 + Santa Barbara, California 93111
4859 + Tel: +1 805 681 0115
4860 + E-Mail: fred@cisco.com
4863 + Postal: RainbowBridge Communications
4864 + Tel: (301) 340-9416
4865 + E-Mail: rcoltun@rainbow-bridge.com"
4867 + "The MIB module to describe traps for the OSPF
4868 + Version 2 Protocol."
4871 +-- Trap Support Objects
4873 +-- The following are support objects for the OSPF traps.
4875 +ospfTrapControl OBJECT IDENTIFIER ::= { ospfTrap 1 }
4876 +ospfTraps OBJECT IDENTIFIER ::= { ospfTrap 2 }
4878 + ospfSetTrap OBJECT-TYPE
4879 + SYNTAX OCTET STRING (SIZE(4))
4880 + MAX-ACCESS read-write
4883 + "A four-octet string serving as a bit map for
4884 + the trap events defined by the OSPF traps. This
4885 + object is used to enable and disable specific
4886 + OSPF traps where a 1 in the bit field
4887 + represents enabled. The right-most bit (least
4888 + significant) represents trap 0."
4889 + ::= { ospfTrapControl 1 }
4892 + ospfConfigErrorType OBJECT-TYPE
4896 + unknownNbmaNbr (3), -- Router is Dr eligible
4897 + unknownVirtualNbr (4),
4898 + authTypeMismatch(5),
4900 + netMaskMismatch (7),
4901 + helloIntervalMismatch (8),
4902 + deadIntervalMismatch (9),
4903 + optionMismatch (10) }
4904 + MAX-ACCESS read-only
4907 + "Potential types of configuration conflicts.
4908 + Used by the ospfConfigError and ospfConfigVir-
4910 + ::= { ospfTrapControl 2 }
4913 + ospfPacketType OBJECT-TYPE
4920 + MAX-ACCESS read-only
4923 + "OSPF packet types."
4924 + ::= { ospfTrapControl 3 }
4927 + ospfPacketSrc OBJECT-TYPE
4929 + MAX-ACCESS read-only
4932 + "The IP address of an inbound packet that can-
4933 + not be identified by a neighbor instance."
4934 + ::= { ospfTrapControl 4 }
4940 + ospfIfStateChange NOTIFICATION-TYPE
4942 + ospfRouterId, -- The originator of the trap
4944 + ospfAddressLessIf,
4945 + ospfIfState -- The new state
4949 + "An ospfIfStateChange trap signifies that there
4950 + has been a change in the state of a non-virtual
4951 + OSPF interface. This trap should be generated
4952 + when the interface state regresses (e.g., goes
4953 + from Dr to Down) or progresses to a terminal
4954 + state (i.e., Point-to-Point, DR Other, Dr, or
4956 + ::= { ospfTraps 16 }
4959 + ospfVirtIfStateChange NOTIFICATION-TYPE
4961 + ospfRouterId, -- The originator of the trap
4963 + ospfVirtIfNeighbor,
4964 + ospfVirtIfState -- The new state
4968 + "An ospfIfStateChange trap signifies that there
4969 + has been a change in the state of an OSPF vir-
4971 + This trap should be generated when the inter-
4972 + face state regresses (e.g., goes from Point-
4973 + to-Point to Down) or progresses to a terminal
4974 + state (i.e., Point-to-Point)."
4975 + ::= { ospfTraps 1 }
4978 + ospfNbrStateChange NOTIFICATION-TYPE
4980 + ospfRouterId, -- The originator of the trap
4982 + ospfNbrAddressLessIndex,
4984 + ospfNbrState -- The new state
4988 + "An ospfNbrStateChange trap signifies that
4989 + there has been a change in the state of a non-
4990 + virtual OSPF neighbor. This trap should be
4991 + generated when the neighbor state regresses
4992 + (e.g., goes from Attempt or Full to 1-Way or
4993 + Down) or progresses to a terminal state (e.g.,
4994 + 2-Way or Full). When an neighbor transitions
4995 + from or to Full on non-broadcast multi-access
4996 + and broadcast networks, the trap should be gen-
4997 + erated by the designated router. A designated
4998 + router transitioning to Down will be noted by
4999 + ospfIfStateChange."
5000 + ::= { ospfTraps 2 }
5003 + ospfVirtNbrStateChange NOTIFICATION-TYPE
5005 + ospfRouterId, -- The originator of the trap
5008 + ospfVirtNbrState -- The new state
5012 + "An ospfIfStateChange trap signifies that there
5013 + has been a change in the state of an OSPF vir-
5014 + tual neighbor. This trap should be generated
5015 + when the neighbor state regresses (e.g., goes
5016 + from Attempt or Full to 1-Way or Down) or
5017 + progresses to a terminal state (e.g., Full)."
5018 + ::= { ospfTraps 3 }
5019 + ospfIfConfigError NOTIFICATION-TYPE
5021 + ospfRouterId, -- The originator of the trap
5023 + ospfAddressLessIf,
5024 + ospfPacketSrc, -- The source IP address
5025 + ospfConfigErrorType, -- Type of error
5030 + "An ospfIfConfigError trap signifies that a
5031 + packet has been received on a non-virtual in-
5032 + terface from a router whose configuration
5033 + parameters conflict with this router's confi-
5034 + guration parameters. Note that the event op-
5035 + tionMismatch should cause a trap only if it
5036 + prevents an adjacency from forming."
5037 + ::= { ospfTraps 4 }
5040 + ospfVirtIfConfigError NOTIFICATION-TYPE
5042 + ospfRouterId, -- The originator of the trap
5044 + ospfVirtIfNeighbor,
5045 + ospfConfigErrorType, -- Type of error
5050 + "An ospfConfigError trap signifies that a pack-
5051 + et has been received on a virtual interface
5052 + from a router whose configuration parameters
5053 + conflict with this router's configuration
5054 + parameters. Note that the event optionMismatch
5055 + should cause a trap only if it prevents an ad-
5056 + jacency from forming."
5057 + ::= { ospfTraps 5 }
5060 + ospfIfAuthFailure NOTIFICATION-TYPE
5062 + ospfRouterId, -- The originator of the trap
5064 + ospfAddressLessIf,
5065 + ospfPacketSrc, -- The source IP address
5066 + ospfConfigErrorType, -- authTypeMismatch or
5072 + "An ospfIfAuthFailure trap signifies that a
5073 + packet has been received on a non-virtual in-
5074 + terface from a router whose authentication key
5075 + or authentication type conflicts with this
5076 + router's authentication key or authentication
5078 + ::= { ospfTraps 6 }
5081 + ospfVirtIfAuthFailure NOTIFICATION-TYPE
5083 + ospfRouterId, -- The originator of the trap
5085 + ospfVirtIfNeighbor,
5086 + ospfConfigErrorType, -- authTypeMismatch or
5092 + "An ospfVirtIfAuthFailure trap signifies that a
5093 + packet has been received on a virtual interface
5094 + from a router whose authentication key or au-
5095 + thentication type conflicts with this router's
5096 + authentication key or authentication type."
5097 + ::= { ospfTraps 7 }
5100 + ospfIfRxBadPacket NOTIFICATION-TYPE
5102 + ospfRouterId, -- The originator of the trap
5104 + ospfAddressLessIf,
5105 + ospfPacketSrc, -- The source IP address
5110 + "An ospfIfRxBadPacket trap signifies that an
5111 + OSPF packet has been received on a non-virtual
5112 + interface that cannot be parsed."
5113 + ::= { ospfTraps 8 }
5115 + ospfVirtIfRxBadPacket NOTIFICATION-TYPE
5117 + ospfRouterId, -- The originator of the trap
5119 + ospfVirtIfNeighbor,
5124 + "An ospfRxBadPacket trap signifies that an OSPF
5125 + packet has been received on a virtual interface
5126 + that cannot be parsed."
5127 + ::= { ospfTraps 9 }
5130 + ospfTxRetransmit NOTIFICATION-TYPE
5132 + ospfRouterId, -- The originator of the trap
5134 + ospfAddressLessIf,
5135 + ospfNbrRtrId, -- Destination
5143 + "An ospfTxRetransmit trap signifies than an
5144 + OSPF packet has been retransmitted on a non-
5145 + virtual interface. All packets that may be re-
5146 + transmitted are associated with an LSDB entry.
5147 + The LS type, LS ID, and Router ID are used to
5148 + identify the LSDB entry."
5149 + ::= { ospfTraps 10 }
5152 + ospfVirtIfTxRetransmit NOTIFICATION-TYPE
5154 + ospfRouterId, -- The originator of the trap
5156 + ospfVirtIfNeighbor,
5164 + "An ospfTxRetransmit trap signifies than an
5165 + OSPF packet has been retransmitted on a virtual
5166 + interface. All packets that may be retransmit-
5167 + ted are associated with an LSDB entry. The LS
5168 + type, LS ID, and Router ID are used to identify
5170 + ::= { ospfTraps 11 }
5173 + ospfOriginateLsa NOTIFICATION-TYPE
5175 + ospfRouterId, -- The originator of the trap
5176 + ospfLsdbAreaId, -- 0.0.0.0 for AS Externals
5183 + "An ospfOriginateLsa trap signifies that a new
5184 + LSA has been originated by this router. This
5185 + trap should not be invoked for simple refreshes
5186 + of LSAs (which happesn every 30 minutes), but
5187 + instead will only be invoked when an LSA is
5188 + (re)originated due to a topology change. Addi-
5189 + tionally, this trap does not include LSAs that
5190 + are being flushed because they have reached
5192 + ::= { ospfTraps 12 }
5195 + ospfMaxAgeLsa NOTIFICATION-TYPE
5197 + ospfRouterId, -- The originator of the trap
5198 + ospfLsdbAreaId, -- 0.0.0.0 for AS Externals
5205 + "An ospfMaxAgeLsa trap signifies that one of
5206 + the LSA in the router's link-state database has
5208 + ::= { ospfTraps 13 }
5211 + ospfLsdbOverflow NOTIFICATION-TYPE
5213 + ospfRouterId, -- The originator of the trap
5218 + "An ospfLsdbOverflow trap signifies that the
5219 + number of LSAs in the router's link-state data-
5220 + base has exceeded ospfExtLsdbLimit."
5221 + ::= { ospfTraps 14 }
5224 + ospfLsdbApproachingOverflow NOTIFICATION-TYPE
5226 + ospfRouterId, -- The originator of the trap
5231 + "An ospfLsdbApproachingOverflow trap signifies
5232 + that the number of LSAs in the router's link-
5233 + state database has exceeded ninety percent of
5234 + ospfExtLsdbLimit."
5235 + ::= { ospfTraps 15 }
5238 +-- conformance information
5240 +ospfTrapConformance OBJECT IDENTIFIER ::= { ospfTrap 3 }
5242 +ospfTrapGroups OBJECT IDENTIFIER ::= { ospfTrapConformance 1 }
5243 +ospfTrapCompliances OBJECT IDENTIFIER ::= { ospfTrapConformance 2 }
5245 +-- compliance statements
5247 + ospfTrapCompliance MODULE-COMPLIANCE
5250 + "The compliance statement "
5251 + MODULE -- this module
5252 + MANDATORY-GROUPS { ospfTrapControlGroup }
5255 + GROUP ospfTrapControlGroup
5257 + "This group is optional but recommended for all
5259 + ::= { ospfTrapCompliances 1 }
5262 +-- units of conformance
5264 + ospfTrapControlGroup OBJECT-GROUP
5267 + ospfConfigErrorType,
5273 + "These objects are required to control traps
5274 + from OSPF systems."
5275 + ::= { ospfTrapGroups 1 }
5279 diff -ruN net-snmp-5.4.1.orig/mibs/RIPv2-MIB.txt net-snmp-5.4.1/mibs/RIPv2-MIB.txt
5280 --- net-snmp-5.4.1.orig/mibs/RIPv2-MIB.txt 1970-01-01 01:00:00.000000000 +0100
5281 +++ net-snmp-5.4.1/mibs/RIPv2-MIB.txt 2007-09-20 16:30:52.000000000 +0200
5283 + RIPv2-MIB DEFINITIONS ::= BEGIN
5286 + MODULE-IDENTITY, OBJECT-TYPE, Counter32,
5287 + TimeTicks, IpAddress FROM SNMPv2-SMI
5288 + TEXTUAL-CONVENTION, RowStatus FROM SNMPv2-TC
5289 + MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
5290 + mib-2 FROM RFC1213-MIB;
5292 + -- This MIB module uses the extended OBJECT-TYPE macro as
5293 + -- defined in [9].
5295 + rip2 MODULE-IDENTITY
5296 + LAST-UPDATED "9407272253Z" -- Wed Jul 27 22:53:04 PDT 1994
5297 + ORGANIZATION "IETF RIP-II Working Group"
5300 + Postal: Cisco Systems
5302 + Santa Barbara, California 93111
5303 + Tel: +1 805 681 0115
5304 + E-Mail: fbaker@cisco.com
5306 + Postal: Gary Malkin
5309 + Burlington, MA 01803
5311 + Phone: (617) 272-8140
5312 + EMail: gmalkin@Xylogics.COM"
5314 + "The MIB module to describe the RIP2 Version 2 Protocol"
5317 + -- RIP-2 Management Information Base
5319 + -- the RouteTag type represents the contents of the
5320 + -- Route Domain field in the packet header or route entry.
5321 + -- The use of the Route Domain is deprecated.
5323 + RouteTag ::= TEXTUAL-CONVENTION
5326 + "the RouteTag type represents the contents of the Route Domain
5327 + field in the packet header or route entry"
5328 + SYNTAX OCTET STRING (SIZE (2))
5330 +--4.1 Global Counters
5332 +-- The RIP-2 Globals Group.
5333 +-- Implementation of this group is mandatory for systems
5334 +-- which implement RIP-2.
5336 +-- These counters are intended to facilitate debugging quickly
5337 +-- changing routes or failing neighbors
5339 +rip2Globals OBJECT IDENTIFIER ::= { rip2 1 }
5341 + rip2GlobalRouteChanges OBJECT-TYPE
5343 + MAX-ACCESS read-only
5346 + "The number of route changes made to the IP Route
5347 + Database by RIP. This does not include the refresh
5348 + of a route's age."
5349 + ::= { rip2Globals 1 }
5351 + rip2GlobalQueries OBJECT-TYPE
5353 + MAX-ACCESS read-only
5356 + "The number of responses sent to RIP queries
5357 + from other systems."
5358 + ::= { rip2Globals 2 }
5360 +--4.2 RIP Interface Tables
5362 +-- RIP Interfaces Groups
5363 +-- Implementation of these Groups is mandatory for systems
5364 +-- which implement RIP-2.
5366 +-- The RIP Interface Status Table.
5368 + rip2IfStatTable OBJECT-TYPE
5369 + SYNTAX SEQUENCE OF Rip2IfStatEntry
5370 + MAX-ACCESS not-accessible
5373 + "A list of subnets which require separate
5374 + status monitoring in RIP."
5377 + rip2IfStatEntry OBJECT-TYPE
5378 + SYNTAX Rip2IfStatEntry
5379 + MAX-ACCESS not-accessible
5382 + "A Single Routing Domain in a single Subnet."
5383 + INDEX { rip2IfStatAddress }
5384 + ::= { rip2IfStatTable 1 }
5386 + Rip2IfStatEntry ::=
5390 + rip2IfStatRcvBadPackets
5392 + rip2IfStatRcvBadRoutes
5394 + rip2IfStatSentUpdates
5400 + rip2IfStatAddress OBJECT-TYPE
5402 + MAX-ACCESS read-only
5405 + "The IP Address of this system on the indicated
5406 + subnet. For unnumbered interfaces, the value 0.0.0.N,
5407 + where the least significant 24 bits (N) is the ifIndex
5408 + for the IP Interface in network byte order."
5409 + ::= { rip2IfStatEntry 1 }
5411 + rip2IfStatRcvBadPackets OBJECT-TYPE
5413 + MAX-ACCESS read-only
5416 + "The number of RIP response packets received by
5417 + the RIP process which were subsequently discarded
5418 + for any reason (e.g. a version 0 packet, or an
5419 + unknown command type)."
5420 + ::= { rip2IfStatEntry 2 }
5422 + rip2IfStatRcvBadRoutes OBJECT-TYPE
5424 + MAX-ACCESS read-only
5427 + "The number of routes, in valid RIP packets,
5428 + which were ignored for any reason (e.g. unknown
5429 + address family, or invalid metric)."
5430 + ::= { rip2IfStatEntry 3 }
5432 + rip2IfStatSentUpdates OBJECT-TYPE
5434 + MAX-ACCESS read-only
5437 + "The number of triggered RIP updates actually
5438 + sent on this interface. This explicitly does
5439 + NOT include full updates sent containing new
5441 + ::= { rip2IfStatEntry 4 }
5443 + rip2IfStatStatus OBJECT-TYPE
5445 + MAX-ACCESS read-create
5448 + "Writing invalid has the effect of deleting
5450 + ::= { rip2IfStatEntry 5 }
5452 +-- The RIP Interface Configuration Table.
5454 + rip2IfConfTable OBJECT-TYPE
5455 + SYNTAX SEQUENCE OF Rip2IfConfEntry
5456 + MAX-ACCESS not-accessible
5459 + "A list of subnets which require separate
5460 + configuration in RIP."
5463 + rip2IfConfEntry OBJECT-TYPE
5464 + SYNTAX Rip2IfConfEntry
5465 + MAX-ACCESS not-accessible
5468 + "A Single Routing Domain in a single Subnet."
5469 + INDEX { rip2IfConfAddress }
5470 + ::= { rip2IfConfTable 1 }
5472 + Rip2IfConfEntry ::=
5478 + rip2IfConfAuthType
5481 + OCTET STRING (SIZE(0..16)),
5486 + rip2IfConfDefaultMetric
5490 + rip2IfConfSrcAddress
5494 + rip2IfConfAddress OBJECT-TYPE
5496 + MAX-ACCESS read-only
5499 + "The IP Address of this system on the indicated
5500 + subnet. For unnumbered interfaces, the value 0.0.0.N,
5501 + where the least significant 24 bits (N) is the ifIndex
5502 + for the IP Interface in network byte order."
5503 + ::= { rip2IfConfEntry 1 }
5505 + rip2IfConfDomain OBJECT-TYPE
5507 + MAX-ACCESS read-create
5510 + "Value inserted into the Routing Domain field
5511 + of all RIP packets sent on this interface."
5512 + DEFVAL { '0000'h }
5513 + ::= { rip2IfConfEntry 2 }
5515 + rip2IfConfAuthType OBJECT-TYPE
5517 + noAuthentication (1),
5518 + simplePassword (2),
5521 + MAX-ACCESS read-create
5524 + "The type of Authentication used on this
5526 + DEFVAL { noAuthentication }
5527 + ::= { rip2IfConfEntry 3 }
5529 + rip2IfConfAuthKey OBJECT-TYPE
5530 + SYNTAX OCTET STRING (SIZE(0..16))
5531 + MAX-ACCESS read-create
5534 + "The value to be used as the Authentication Key
5535 + whenever the corresponding instance of
5536 + rip2IfConfAuthType has a value other than
5537 + noAuthentication. A modification of the corresponding
5538 + instance of rip2IfConfAuthType does not modify
5539 + the rip2IfConfAuthKey value. If a string shorter
5540 + than 16 octets is supplied, it will be left-
5541 + justified and padded to 16 octets, on the right,
5542 + with nulls (0x00).
5544 + Reading this object always results in an OCTET
5545 + STRING of length zero; authentication may not
5546 + be bypassed by reading the MIB object."
5548 + ::= { rip2IfConfEntry 4 }
5550 + rip2IfConfSend OBJECT-TYPE
5554 + rip1Compatible (3),
5559 + MAX-ACCESS read-create
5562 + "What the router sends on this interface.
5563 + ripVersion1 implies sending RIP updates compliant
5564 + with RFC 1058. rip1Compatible implies
5565 + broadcasting RIP-2 updates using RFC 1058 route
5566 + subsumption rules. ripVersion2 implies
5567 + multicasting RIP-2 updates. ripV1Demand indicates
5568 + the use of Demand RIP on a WAN interface under RIP
5569 + Version 1 rules. ripV2Demand indicates the use of
5570 + Demand RIP on a WAN interface under Version 2 rules."
5571 + DEFVAL { rip1Compatible }
5572 + ::= { rip2IfConfEntry 5 }
5574 + rip2IfConfReceive OBJECT-TYPE
5581 + MAX-ACCESS read-create
5584 + "This indicates which version of RIP updates
5585 + are to be accepted. Note that rip2 and
5586 + rip1OrRip2 implies reception of multicast
5588 + DEFVAL { rip1OrRip2 }
5589 + ::= { rip2IfConfEntry 6 }
5591 + rip2IfConfDefaultMetric OBJECT-TYPE
5592 + SYNTAX INTEGER ( 0..15 )
5593 + MAX-ACCESS read-create
5596 + "This variable indicates the metric that is to
5597 + be used for the default route entry in RIP updates
5598 + originated on this interface. A value of zero
5599 + indicates that no default route should be
5600 + originated; in this case, a default route via
5601 + another router may be propagated."
5602 + ::= { rip2IfConfEntry 7 }
5604 + rip2IfConfStatus OBJECT-TYPE
5606 + MAX-ACCESS read-create
5609 + "Writing invalid has the effect of deleting
5611 + ::= { rip2IfConfEntry 8 }
5613 + rip2IfConfSrcAddress OBJECT-TYPE
5615 + MAX-ACCESS read-create
5618 + "The IP Address this system will use as a source
5619 + address on this interface. If it is a numbered
5620 + interface, this MUST be the same value as
5621 + rip2IfConfAddress. On unnumbered interfaces,
5622 + it must be the value of rip2IfConfAddress for
5623 + some interface on the system."
5624 + ::= { rip2IfConfEntry 9 }
5630 +-- The RIP Peer Group
5631 +-- Implementation of this Group is Optional
5633 +-- This group provides information about active peer
5634 +-- relationships intended to assist in debugging. An
5635 +-- active peer is a router from which a valid RIP
5636 +-- updated has been heard in the last 180 seconds.
5638 + rip2PeerTable OBJECT-TYPE
5639 + SYNTAX SEQUENCE OF Rip2PeerEntry
5640 + MAX-ACCESS not-accessible
5643 + "A list of RIP Peers."
5646 + rip2PeerEntry OBJECT-TYPE
5647 + SYNTAX Rip2PeerEntry
5648 + MAX-ACCESS not-accessible
5651 + "Information regarding a single routing peer."
5652 + INDEX { rip2PeerAddress, rip2PeerDomain }
5653 + ::= { rip2PeerTable 1 }
5661 + rip2PeerLastUpdate
5665 + rip2PeerRcvBadPackets
5667 + rip2PeerRcvBadRoutes
5671 + rip2PeerAddress OBJECT-TYPE
5673 + MAX-ACCESS read-only
5676 + "The IP Address that the peer is using as its source
5677 + address. Note that on an unnumbered link, this may
5678 + not be a member of any subnet on the system."
5679 + ::= { rip2PeerEntry 1 }
5681 + rip2PeerDomain OBJECT-TYPE
5683 + MAX-ACCESS read-only
5686 + "The value in the Routing Domain field in RIP
5687 + packets received from the peer. As domain suuport
5688 + is deprecated, this must be zero."
5689 + ::= { rip2PeerEntry 2 }
5691 + rip2PeerLastUpdate OBJECT-TYPE
5693 + MAX-ACCESS read-only
5696 + "The value of sysUpTime when the most recent
5697 + RIP update was received from this system."
5698 + ::= { rip2PeerEntry 3 }
5700 + rip2PeerVersion OBJECT-TYPE
5701 + SYNTAX INTEGER ( 0..255 )
5702 + MAX-ACCESS read-only
5705 + "The RIP version number in the header of the
5706 + last RIP packet received."
5707 + ::= { rip2PeerEntry 4 }
5709 + rip2PeerRcvBadPackets OBJECT-TYPE
5711 + MAX-ACCESS read-only
5714 + "The number of RIP response packets from this
5715 + peer discarded as invalid."
5716 + ::= { rip2PeerEntry 5 }
5719 + rip2PeerRcvBadRoutes OBJECT-TYPE
5721 + MAX-ACCESS read-only
5724 + "The number of routes from this peer that were
5725 + ignored because the entry format was invalid."
5726 + ::= { rip2PeerEntry 6 }
5728 +-- conformance information
5730 +rip2Conformance OBJECT IDENTIFIER ::= { rip2 5 }
5732 +rip2Groups OBJECT IDENTIFIER ::= { rip2Conformance 1 }
5733 +rip2Compliances OBJECT IDENTIFIER ::= { rip2Conformance 2 }
5735 +-- compliance statements
5736 +rip2Compliance MODULE-COMPLIANCE
5739 + "The compliance statement "
5740 + MODULE -- this module
5741 + MANDATORY-GROUPS {
5747 + GROUP rip2GlobalGroup
5749 + "This group defines global controls for RIP-II systems."
5750 + GROUP rip2IfStatGroup
5752 + "This group defines interface statistics for RIP-II systems."
5753 + GROUP rip2IfConfGroup
5755 + "This group defines interface configuration for RIP-II systems."
5756 + GROUP rip2PeerGroup
5758 + "This group defines peer information for RIP-II systems."
5759 + ::= { rip2Compliances 1 }
5761 +-- units of conformance
5763 +rip2GlobalGroup OBJECT-GROUP
5765 + rip2GlobalRouteChanges,
5770 + "This group defines global controls for RIP-II systems."
5771 + ::= { rip2Groups 1 }
5772 +rip2IfStatGroup OBJECT-GROUP
5774 + rip2IfStatAddress,
5775 + rip2IfStatRcvBadPackets,
5776 + rip2IfStatRcvBadRoutes,
5777 + rip2IfStatSentUpdates,
5782 + "This group defines interface statistics for RIP-II systems."
5783 + ::= { rip2Groups 2 }
5784 +rip2IfConfGroup OBJECT-GROUP
5786 + rip2IfConfAddress,
5787 + rip2IfConfAuthType,
5788 + rip2IfConfAuthKey,
5790 + rip2IfConfReceive,
5791 + rip2IfConfDefaultMetric,
5793 + rip2IfConfSrcAddress
5797 + "This group defines interface configuration for RIP-II systems."
5798 + ::= { rip2Groups 3 }
5799 +rip2PeerGroup OBJECT-GROUP
5803 + rip2PeerLastUpdate,
5805 + rip2PeerRcvBadPackets,
5806 + rip2PeerRcvBadRoutes
5810 + "This group defines peer information for RIP-II systems."
5811 + ::= { rip2Groups 4 }
5813 diff -ruN net-snmp-5.4.1.orig/mibs/SOURCE-ROUTING-MIB.txt net-snmp-5.4.1/mibs/SOURCE-ROUTING-MIB.txt
5814 --- net-snmp-5.4.1.orig/mibs/SOURCE-ROUTING-MIB.txt 1970-01-01 01:00:00.000000000 +0100
5815 +++ net-snmp-5.4.1/mibs/SOURCE-ROUTING-MIB.txt 2007-09-20 16:30:52.000000000 +0200
5817 +SOURCE-ROUTING-MIB DEFINITIONS ::= BEGIN
5822 + dot1dBridge, dot1dSr
5827 +-- groups in the SR MIB
5829 +-- dot1dSr is imported from the Bridge MIB
5831 +dot1dPortPair OBJECT IDENTIFIER ::= { dot1dBridge 10 }
5833 +-- the dot1dSr group
5835 +-- this group is implemented by those bridges that
5836 +-- support the source route bridging mode, including Source
5837 +-- Routing and SRT bridges.
5839 +dot1dSrPortTable OBJECT-TYPE
5840 + SYNTAX SEQUENCE OF Dot1dSrPortEntry
5841 + ACCESS not-accessible
5844 + "A table that contains information about every
5845 + port that is associated with this source route
5849 +dot1dSrPortEntry OBJECT-TYPE
5850 + SYNTAX Dot1dSrPortEntry
5851 + ACCESS not-accessible
5854 + "A list of information for each port of a source
5856 + INDEX { dot1dSrPort }
5858 + ::= { dot1dSrPortTable 1 }
5860 +Dot1dSrPortEntry ::=
5864 + dot1dSrPortHopCount
5866 + dot1dSrPortLocalSegment
5868 + dot1dSrPortBridgeNum
5870 + dot1dSrPortTargetSegment
5872 + dot1dSrPortLargestFrame
5874 + dot1dSrPortSTESpanMode
5876 + dot1dSrPortSpecInFrames
5878 + dot1dSrPortSpecOutFrames
5880 + dot1dSrPortApeInFrames
5882 + dot1dSrPortApeOutFrames
5884 + dot1dSrPortSteInFrames
5886 + dot1dSrPortSteOutFrames
5888 + dot1dSrPortSegmentMismatchDiscards
5890 + dot1dSrPortDuplicateSegmentDiscards
5892 + dot1dSrPortHopCountExceededDiscards
5894 + dot1dSrPortDupLanIdOrTreeErrors
5896 + dot1dSrPortLanIdMismatches
5900 +dot1dSrPort OBJECT-TYPE
5901 + SYNTAX INTEGER (1..65535)
5905 + "The port number of the port for which this entry
5907 + contains Source Route management information."
5908 + ::= { dot1dSrPortEntry 1 }
5910 +dot1dSrPortHopCount OBJECT-TYPE
5915 + "The maximum number of routing descriptors allowed
5916 + in an All Paths or Spanning Tree Explorer frames."
5917 + ::= { dot1dSrPortEntry 2 }
5919 +dot1dSrPortLocalSegment OBJECT-TYPE
5924 + "The segment number that uniquely identifies the
5925 + segment to which this port is connected. Current
5926 + source routing protocols limit this value to the
5927 + range: 0 through 4095. (The value 0 is used by
5928 + some management applications for special test
5929 + cases.) A value of 65535 signifies that no segment
5930 + number is assigned to this port."
5931 + ::= { dot1dSrPortEntry 3 }
5933 +dot1dSrPortBridgeNum OBJECT-TYPE
5938 + "A bridge number uniquely identifies a bridge when
5939 + more than one bridge is used to span the same two
5940 + segments. Current source routing protocols limit
5941 + this value to the range: 0 through 15. A value of
5942 + 65535 signifies that no bridge number is assigned
5944 + ::= { dot1dSrPortEntry 4 }
5946 +dot1dSrPortTargetSegment OBJECT-TYPE
5951 + "The segment number that corresponds to the target
5952 + segment this port is considered to be connected to
5953 + by the bridge. Current source routing protocols
5954 + limit this value to the range: 0 through 4095.
5956 + (The value 0 is used by some management
5957 + applications for special test cases.) A value of
5958 + 65535 signifies that no target segment is assigned
5960 + ::= { dot1dSrPortEntry 5 }
5962 +-- It would be nice if we could use ifMtu as the size of the
5963 +-- largest frame, but we can't because ifMtu is defined to be
5964 +-- the size that the (inter-)network layer can use which can
5965 +-- differ from the MAC layer (especially if several layers of
5966 +-- encapsulation are used).
5968 +dot1dSrPortLargestFrame OBJECT-TYPE
5973 + "The maximum size of the INFO field (LLC and
5974 + above) that this port can send/receive. It does
5975 + not include any MAC level (framing) octets. The
5976 + value of this object is used by this bridge to
5977 + determine whether a modification of the
5978 + LargestFrame (LF, see [14]) field of the Routing
5979 + Control field of the Routing Information Field is
5982 + 64 valid values are defined by the IEEE 802.5M SRT
5983 + Addendum: 516, 635, 754, 873, 993, 1112, 1231,
5984 + 1350, 1470, 1542, 1615, 1688, 1761, 1833, 1906,
5985 + 1979, 2052, 2345, 2638, 2932, 3225, 3518, 3812,
5986 + 4105, 4399, 4865, 5331, 5798, 6264, 6730, 7197,
5987 + 7663, 8130, 8539, 8949, 9358, 9768, 10178, 10587,
5988 + 10997, 11407, 12199, 12992, 13785, 14578, 15370,
5989 + 16163, 16956, 17749, 20730, 23711, 26693, 29674,
5990 + 32655, 35637, 38618, 41600, 44591, 47583, 50575,
5991 + 53567, 56559, 59551, and 65535.
5993 + An illegal value will not be accepted by the
5995 + ::= { dot1dSrPortEntry 6 }
5997 +dot1dSrPortSTESpanMode OBJECT-TYPE
6006 + "Determines how this port behaves when presented
6007 + with a Spanning Tree Explorer frame. The value
6008 + 'disabled(2)' indicates that the port will not
6009 + accept or send Spanning Tree Explorer packets; any
6010 + STE packets received will be silently discarded.
6011 + The value 'forced(3)' indicates the port will
6012 + always accept and propagate Spanning Tree Explorer
6013 + frames. This allows a manually configured
6014 + Spanning Tree for this class of packet to be
6015 + configured. Note that unlike transparent
6016 + bridging, this is not catastrophic to the network
6017 + if there are loops. The value 'auto-span(1)' can
6018 + only be returned by a bridge that both implements
6019 + the Spanning Tree Protocol and has use of the
6020 + protocol enabled on this port. The behavior of the
6021 + port for Spanning Tree Explorer frames is
6022 + determined by the state of dot1dStpPortState. If
6023 + the port is in the 'forwarding' state, the frame
6024 + will be accepted or propagated. Otherwise, it
6025 + will be silently discarded."
6026 + ::= { dot1dSrPortEntry 7 }
6028 +dot1dSrPortSpecInFrames OBJECT-TYPE
6033 + "The number of Specifically Routed frames, also
6034 + referred to as Source Routed Frames, that have
6035 + been received from this port's segment."
6036 + ::= { dot1dSrPortEntry 8 }
6038 +dot1dSrPortSpecOutFrames OBJECT-TYPE
6043 + "The number of Specifically Routed frames, also
6044 + referred to as Source Routed Frames, that this
6045 + port has transmitted on its segment."
6046 + ::= { dot1dSrPortEntry 9 }
6048 +dot1dSrPortApeInFrames OBJECT-TYPE
6053 + "The number of All Paths Explorer frames, also
6054 + referred to as All Routes Explorer frames, that
6055 + have been received by this port from its segment."
6056 + ::= { dot1dSrPortEntry 10 }
6058 +dot1dSrPortApeOutFrames OBJECT-TYPE
6063 + "The number of all Paths Explorer Frames, also
6064 + referred to as All Routes Explorer frames, that
6065 + have been transmitted by this port on its
6067 + ::= { dot1dSrPortEntry 11 }
6069 +dot1dSrPortSteInFrames OBJECT-TYPE
6074 + "The number of spanning tree explorer frames that
6075 + have been received by this port from its segment."
6076 + ::= { dot1dSrPortEntry 12 }
6078 +dot1dSrPortSteOutFrames OBJECT-TYPE
6083 + "The number of spanning tree explorer frames that
6084 + have been transmitted by this port on its
6086 + ::= { dot1dSrPortEntry 13 }
6088 +dot1dSrPortSegmentMismatchDiscards OBJECT-TYPE
6093 + "The number of explorer frames that have been
6094 + discarded by this port because the routing
6095 + descriptor field contained an invalid adjacent
6097 + ::= { dot1dSrPortEntry 14 }
6099 +dot1dSrPortDuplicateSegmentDiscards OBJECT-TYPE
6104 + "The number of frames that have been discarded by
6105 + this port because the routing descriptor field
6106 + contained a duplicate segment identifier."
6107 + ::= { dot1dSrPortEntry 15 }
6109 +dot1dSrPortHopCountExceededDiscards OBJECT-TYPE
6114 + "The number of explorer frames that have been
6115 + discarded by this port because the Routing
6116 + Information Field has exceeded the maximum route
6117 + descriptor length."
6118 + ::= { dot1dSrPortEntry 16 }
6120 +dot1dSrPortDupLanIdOrTreeErrors OBJECT-TYPE
6125 + "The number of duplicate LAN IDs or Tree errors.
6126 + This helps in detection of problems in networks
6127 + containing older IBM Source Routing Bridges."
6128 + ::= { dot1dSrPortEntry 17 }
6130 +dot1dSrPortLanIdMismatches OBJECT-TYPE
6135 + "The number of ARE and STE frames that were
6136 + discarded because the last LAN ID in the routing
6137 + information field did not equal the LAN-in ID.
6138 + This error can occur in implementations which do
6139 + only a LAN-in ID and Bridge Number check instead
6140 + of a LAN-in ID, Bridge Number, and LAN-out ID
6141 + check before they forward broadcast frames."
6142 + ::= { dot1dSrPortEntry 18 }
6144 +-- scalar object in dot1dSr
6146 +dot1dSrBridgeLfMode OBJECT-TYPE
6154 + "Indicates whether the bridge operates using older
6155 + 3 bit length negotiation fields or the newer 6 bit
6156 + length field in its RIF."
6159 +-- The Port-Pair Database
6161 +-- Implementation of this group is optional.
6163 +-- This group is implemented by those bridges that support
6164 +-- the direct multiport model of the source route bridging
6165 +-- mode as defined in the IEEE 802.5 SRT Addendum to
6168 +-- Bridges implementing this group may report 65535 for
6169 +-- dot1dSrPortBridgeNumber and dot1dSrPortTargetSegment,
6170 +-- indicating that those objects are not applicable.
6172 +dot1dPortPairTableSize OBJECT-TYPE
6177 + "The total number of entries in the Bridge Port
6179 + ::= { dot1dPortPair 1 }
6181 +-- the Bridge Port-Pair table
6183 +-- this table represents port pairs within a bridge forming
6184 +-- a unique bridge path, as defined in the IEEE 802.5M SRT
6187 +dot1dPortPairTable OBJECT-TYPE
6188 + SYNTAX SEQUENCE OF Dot1dPortPairEntry
6189 + ACCESS not-accessible
6192 + "A table that contains information about every
6194 + port pair database entity associated with this
6195 + source routing bridge."
6196 + ::= { dot1dPortPair 2 }
6198 +dot1dPortPairEntry OBJECT-TYPE
6199 + SYNTAX Dot1dPortPairEntry
6200 + ACCESS not-accessible
6203 + "A list of information for each port pair entity
6205 + INDEX { dot1dPortPairLowPort, dot1dPortPairHighPort }
6206 + ::= { dot1dPortPairTable 1 }
6208 +Dot1dPortPairEntry ::=
6210 + dot1dPortPairLowPort
6212 + dot1dPortPairHighPort
6214 + dot1dPortPairBridgeNum
6216 + dot1dPortPairBridgeState
6220 +dot1dPortPairLowPort OBJECT-TYPE
6221 + SYNTAX INTEGER (1..65535)
6225 + "The port number of the lower numbered port for
6226 + which this entry contains port pair database
6228 + ::= { dot1dPortPairEntry 1 }
6230 +dot1dPortPairHighPort OBJECT-TYPE
6231 + SYNTAX INTEGER (1..65535)
6235 + "The port number of the higher numbered port for
6236 + which this entry contains port pair database
6238 + ::= { dot1dPortPairEntry 2 }
6240 +dot1dPortPairBridgeNum OBJECT-TYPE
6246 + "A bridge number that uniquely identifies the path
6247 + provided by this source routing bridge between the
6248 + segments connected to dot1dPortPairLowPort and
6249 + dot1dPortPairHighPort. The purpose of bridge
6250 + number is to disambiguate between multiple paths
6251 + connecting the same two LANs."
6252 + ::= { dot1dPortPairEntry 3 }
6254 +dot1dPortPairBridgeState OBJECT-TYPE
6263 + "The state of dot1dPortPairBridgeNum. Writing
6264 + 'invalid(3)' to this object removes the
6265 + corresponding entry."
6266 + ::= { dot1dPortPairEntry 4 }
projects / openwrt / svn-archive / archive.git / blob