1 BGP4-MIB DEFINITIONS ::= BEGIN
4 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
5 IpAddress, Integer32, Counter32, Gauge32, mib-2
7 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
11 LAST-UPDATED "200601110000Z"
12 ORGANIZATION "IETF IDR Working Group"
13 CONTACT-INFO "E-mail: idr@ietf.org
15 Jeffrey Haas, Susan Hares (Editors)
19 Ann Arbor, MI 48108-2738
22 E-mail: jhaas@nexthop.com
26 "The MIB module for the BGP-4 protocol.
28 Copyright (C) The Internet Society (2006). This
29 version of this MIB module is part of RFC 4273;
30 see the RFC itself for full legal notices."
32 REVISION "200601110000Z"
34 "Changes from RFC 1657:
36 1) Fixed the definitions of the notifications
37 to make them equivalent to their initial
38 definition in RFC 1269.
39 2) Added compliance and conformance info.
40 3) Updated information for the values of
41 bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref,
42 bgp4PathAttrCalcLocalPref,
43 bgp4PathAttrMultiExitDisc,
44 bgp4PathAttrASPathSegement.
45 4) Added additional clarification comments where
50 5) Noted where objects do not fully reflect
51 the protocol as Known Issues.
52 6) Updated the DESCRIPTION for the
53 bgp4PathAttrAtomicAggregate object.
54 7) The following objects have had their DESCRIPTION
55 clause modified to remove the text that suggested
56 (using 'should' verb) initializing the counter
57 to zero on a transition to the established state:
58 bgpPeerInUpdates, bgpPeerOutUpdates,
59 bgpPeerInTotalMessages, bgpPeerOutTotalMessages
60 Those implementations that still do this are
61 still compliant with this new wording.
62 Applications should not assume counters have
65 Published as RFC 4273."
67 REVISION "199405050000Z"
69 "Translated to SMIv2 and published as RFC 1657."
71 REVISION "199110261839Z"
73 "Initial version, published as RFC 1269."
76 bgpVersion OBJECT-TYPE
77 SYNTAX OCTET STRING (SIZE (1..255))
81 "Vector of supported BGP protocol version
82 numbers. Each peer negotiates the version
83 from this vector. Versions are identified
84 via the string of bits contained within this
85 object. The first octet contains bits 0 to
86 7, the second octet contains bits 8 to 15,
87 and so on, with the most significant bit
88 referring to the lowest bit number in the
89 octet (e.g., the MSB of the first octet
90 refers to bit 0). If a bit, i, is present
91 and set, then the version (i+1) of the BGP
94 "RFC 4271, Section 4.2."
97 bgpLocalAs OBJECT-TYPE
101 SYNTAX Integer32 (0..65535)
105 "The local autonomous system number."
107 "RFC 4271, Section 4.2, 'My Autonomous System'."
110 -- BGP Peer table. This table contains, one entry per
111 -- BGP peer, information about the BGP peer.
113 bgpPeerTable OBJECT-TYPE
114 SYNTAX SEQUENCE OF BgpPeerEntry
115 MAX-ACCESS not-accessible
118 "BGP peer table. This table contains,
119 one entry per BGP peer, information about the
120 connections with BGP peers."
123 bgpPeerEntry OBJECT-TYPE
125 MAX-ACCESS not-accessible
128 "Entry containing information about the
129 connection with a BGP peer."
130 INDEX { bgpPeerRemoteAddr }
131 ::= { bgpPeerTable 1 }
133 BgpPeerEntry ::= SEQUENCE {
140 bgpPeerNegotiatedVersion
159 bgpPeerInTotalMessages
161 bgpPeerOutTotalMessages
165 bgpPeerFsmEstablishedTransitions
167 bgpPeerFsmEstablishedTime
169 bgpPeerConnectRetryInterval
175 bgpPeerHoldTimeConfigured
177 bgpPeerKeepAliveConfigured
179 bgpPeerMinASOriginationInterval
181 bgpPeerMinRouteAdvertisementInterval
183 bgpPeerInUpdateElapsedTime
187 bgpPeerIdentifier OBJECT-TYPE
192 "The BGP Identifier of this entry's BGP peer.
193 This entry MUST be 0.0.0.0 unless the
194 bgpPeerState is in the openconfirm or the
197 "RFC 4271, Section 4.2, 'BGP Identifier'."
198 ::= { bgpPeerEntry 1 }
203 bgpPeerState OBJECT-TYPE
215 "The BGP peer connection state."
217 "RFC 4271, Section 8.2.2."
218 ::= { bgpPeerEntry 2 }
220 bgpPeerAdminStatus OBJECT-TYPE
225 MAX-ACCESS read-write
228 "The desired state of the BGP connection.
229 A transition from 'stop' to 'start' will cause
230 the BGP Manual Start Event to be generated.
231 A transition from 'start' to 'stop' will cause
232 the BGP Manual Stop Event to be generated.
233 This parameter can be used to restart BGP peer
234 connections. Care should be used in providing
235 write access to this object without adequate
238 "RFC 4271, Section 8.1.2."
239 ::= { bgpPeerEntry 3 }
241 bgpPeerNegotiatedVersion OBJECT-TYPE
246 "The negotiated version of BGP running between
249 This entry MUST be zero (0) unless the
250 bgpPeerState is in the openconfirm or the
256 Note that legal values for this object are
259 "RFC 4271, Section 4.2.
260 RFC 4271, Section 7."
261 ::= { bgpPeerEntry 4 }
263 bgpPeerLocalAddr OBJECT-TYPE
268 "The local IP address of this entry's BGP
270 ::= { bgpPeerEntry 5 }
272 bgpPeerLocalPort OBJECT-TYPE
273 SYNTAX Integer32 (0..65535)
277 "The local port for the TCP connection between
279 ::= { bgpPeerEntry 6 }
281 bgpPeerRemoteAddr OBJECT-TYPE
286 "The remote IP address of this entry's BGP
288 ::= { bgpPeerEntry 7 }
290 bgpPeerRemotePort OBJECT-TYPE
291 SYNTAX Integer32 (0..65535)
295 "The remote port for the TCP connection
296 between the BGP peers. Note that the
297 objects bgpPeerLocalAddr,
298 bgpPeerLocalPort, bgpPeerRemoteAddr, and
299 bgpPeerRemotePort provide the appropriate
300 reference to the standard MIB TCP
305 ::= { bgpPeerEntry 8 }
307 bgpPeerRemoteAs OBJECT-TYPE
308 SYNTAX Integer32 (0..65535)
312 "The remote autonomous system number received in
313 the BGP OPEN message."
315 "RFC 4271, Section 4.2."
316 ::= { bgpPeerEntry 9 }
318 bgpPeerInUpdates OBJECT-TYPE
323 "The number of BGP UPDATE messages
324 received on this connection."
326 "RFC 4271, Section 4.3."
327 ::= { bgpPeerEntry 10 }
329 bgpPeerOutUpdates OBJECT-TYPE
334 "The number of BGP UPDATE messages
335 transmitted on this connection."
337 "RFC 4271, Section 4.3."
338 ::= { bgpPeerEntry 11 }
340 bgpPeerInTotalMessages OBJECT-TYPE
345 "The total number of messages received
346 from the remote peer on this connection."
348 "RFC 4271, Section 4."
349 ::= { bgpPeerEntry 12 }
351 bgpPeerOutTotalMessages OBJECT-TYPE
359 "The total number of messages transmitted to
360 the remote peer on this connection."
362 "RFC 4271, Section 4."
363 ::= { bgpPeerEntry 13 }
365 bgpPeerLastError OBJECT-TYPE
366 SYNTAX OCTET STRING (SIZE (2))
370 "The last error code and subcode seen by this
371 peer on this connection. If no error has
372 occurred, this field is zero. Otherwise, the
373 first byte of this two byte OCTET STRING
374 contains the error code, and the second byte
375 contains the subcode."
377 "RFC 4271, Section 4.5."
378 ::= { bgpPeerEntry 14 }
380 bgpPeerFsmEstablishedTransitions OBJECT-TYPE
385 "The total number of times the BGP FSM
386 transitioned into the established state
389 "RFC 4271, Section 8."
390 ::= { bgpPeerEntry 15 }
392 bgpPeerFsmEstablishedTime OBJECT-TYPE
398 "This timer indicates how long (in
399 seconds) this peer has been in the
400 established state or how long
401 since this peer was last in the
402 established state. It is set to zero when
403 a new peer is configured or when the router is
409 "RFC 4271, Section 8."
410 ::= { bgpPeerEntry 16 }
412 bgpPeerConnectRetryInterval OBJECT-TYPE
413 SYNTAX Integer32 (1..65535)
415 MAX-ACCESS read-write
418 "Time interval (in seconds) for the
419 ConnectRetry timer. The suggested value
420 for this timer is 120 seconds."
422 "RFC 4271, Section 8.2.2. This is the value used
423 to initialize the 'ConnectRetryTimer'."
424 ::= { bgpPeerEntry 17 }
426 bgpPeerHoldTime OBJECT-TYPE
427 SYNTAX Integer32 ( 0 | 3..65535 )
432 "Time interval (in seconds) for the Hold
433 Timer established with the peer. The
434 value of this object is calculated by this
435 BGP speaker, using the smaller of the
436 values in bgpPeerHoldTimeConfigured and the
437 Hold Time received in the OPEN message.
439 This value must be at least three seconds
440 if it is not zero (0).
442 If the Hold Timer has not been established
443 with the peer this object MUST have a value
446 If the bgpPeerHoldTimeConfigured object has
447 a value of (0), then this object MUST have a
450 "RFC 4271, Section 4.2."
451 ::= { bgpPeerEntry 18 }
453 bgpPeerKeepAlive OBJECT-TYPE
454 SYNTAX Integer32 ( 0 | 1..21845 )
462 "Time interval (in seconds) for the KeepAlive
463 timer established with the peer. The value
464 of this object is calculated by this BGP
465 speaker such that, when compared with
466 bgpPeerHoldTime, it has the same proportion
467 that bgpPeerKeepAliveConfigured has,
468 compared with bgpPeerHoldTimeConfigured.
470 If the KeepAlive timer has not been established
471 with the peer, this object MUST have a value
474 If the of bgpPeerKeepAliveConfigured object
475 has a value of (0), then this object MUST have
478 "RFC 4271, Section 4.4."
479 ::= { bgpPeerEntry 19 }
481 bgpPeerHoldTimeConfigured OBJECT-TYPE
482 SYNTAX Integer32 ( 0 | 3..65535 )
484 MAX-ACCESS read-write
487 "Time interval (in seconds) for the Hold Time
488 configured for this BGP speaker with this
489 peer. This value is placed in an OPEN
490 message sent to this peer by this BGP
491 speaker, and is compared with the Hold
492 Time field in an OPEN message received
493 from the peer when determining the Hold
494 Time (bgpPeerHoldTime) with the peer.
495 This value must not be less than three
496 seconds if it is not zero (0). If it is
497 zero (0), the Hold Time is NOT to be
498 established with the peer. The suggested
499 value for this timer is 90 seconds."
501 "RFC 4271, Section 4.2.
502 RFC 4271, Section 10."
503 ::= { bgpPeerEntry 20 }
505 bgpPeerKeepAliveConfigured OBJECT-TYPE
509 SYNTAX Integer32 ( 0 | 1..21845 )
511 MAX-ACCESS read-write
514 "Time interval (in seconds) for the
515 KeepAlive timer configured for this BGP
516 speaker with this peer. The value of this
517 object will only determine the
518 KEEPALIVE messages' frequency relative to
519 the value specified in
520 bgpPeerHoldTimeConfigured; the actual
521 time interval for the KEEPALIVE messages is
522 indicated by bgpPeerKeepAlive. A
523 reasonable maximum value for this timer
524 would be one third of that of
525 bgpPeerHoldTimeConfigured.
526 If the value of this object is zero (0),
527 no periodical KEEPALIVE messages are sent
528 to the peer after the BGP connection has
529 been established. The suggested value for
530 this timer is 30 seconds."
532 "RFC 4271, Section 4.4.
533 RFC 4271, Section 10."
534 ::= { bgpPeerEntry 21 }
536 bgpPeerMinASOriginationInterval OBJECT-TYPE
537 SYNTAX Integer32 (1..65535)
539 MAX-ACCESS read-write
542 "Time interval (in seconds) for the
543 MinASOriginationInterval timer.
544 The suggested value for this timer is 15
547 "RFC 4271, Section 9.2.1.2.
548 RFC 4271, Section 10."
549 ::= { bgpPeerEntry 22 }
551 bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE
552 SYNTAX Integer32 (1..65535)
554 MAX-ACCESS read-write
560 "Time interval (in seconds) for the
561 MinRouteAdvertisementInterval timer.
562 The suggested value for this timer is 30
563 seconds for EBGP connections and 5
564 seconds for IBGP connections."
566 "RFC 4271, Section 9.2.1.1.
567 RFC 4271, Section 10."
568 ::= { bgpPeerEntry 23 }
570 bgpPeerInUpdateElapsedTime OBJECT-TYPE
576 "Elapsed time (in seconds) since the last BGP
577 UPDATE message was received from the peer.
578 Each time bgpPeerInUpdates is incremented,
579 the value of this object is set to zero (0)."
581 "RFC 4271, Section 4.3.
582 RFC 4271, Section 8.2.2, Established state."
583 ::= { bgpPeerEntry 24 }
585 bgpIdentifier OBJECT-TYPE
590 "The BGP Identifier of the local system."
592 "RFC 4271, Section 4.2."
595 -- BGP Received Path Attribute Table. This table contains
596 -- one entry per path to a network, and path attributes
597 -- received from all peers running BGP version 3 or less.
598 -- This table is obsolete, having been replaced in
599 -- functionality by the bgp4PathAttrTable.
601 bgpRcvdPathAttrTable OBJECT-TYPE
602 SYNTAX SEQUENCE OF BgpPathAttrEntry
603 MAX-ACCESS not-accessible
606 "The BGP Received Path Attribute Table
607 contains information about paths to
611 destination networks, received from all
612 peers running BGP version 3 or less."
615 bgpPathAttrEntry OBJECT-TYPE
616 SYNTAX BgpPathAttrEntry
617 MAX-ACCESS not-accessible
620 "Information about a path to a network."
621 INDEX { bgpPathAttrDestNetwork,
623 ::= { bgpRcvdPathAttrTable 1 }
625 BgpPathAttrEntry ::= SEQUENCE {
628 bgpPathAttrDestNetwork
636 bgpPathAttrInterASMetric
640 bgpPathAttrPeer OBJECT-TYPE
645 "The IP address of the peer where the path
646 information was learned."
647 ::= { bgpPathAttrEntry 1 }
649 bgpPathAttrDestNetwork OBJECT-TYPE
654 "The address of the destination network."
656 "RFC 1267, Section 4.3."
657 ::= { bgpPathAttrEntry 2 }
662 bgpPathAttrOrigin OBJECT-TYPE
664 igp(1),-- networks are interior
665 egp(2),-- networks learned via the
667 incomplete(3) -- networks that
668 -- are learned by some other
674 "The ultimate origin of the path information."
676 "RFC 1267, Section 4.3.
677 RFC 1267, Section 5."
678 ::= { bgpPathAttrEntry 3 }
680 bgpPathAttrASPath OBJECT-TYPE
681 SYNTAX OCTET STRING (SIZE (2..255))
685 "The set of ASes that must be traversed to reach
686 the network. This object is probably best
687 represented as SEQUENCE OF INTEGER. For SMI
688 compatibility, though, it is represented as
689 OCTET STRING. Each AS is represented as a pair
690 of octets according to the following algorithm:
692 first-byte-of-pair = ASNumber / 256;
693 second-byte-of-pair = ASNumber & 255;"
695 "RFC 1267, Section 4.3.
696 RFC 1267, Section 5."
697 ::= { bgpPathAttrEntry 4 }
699 bgpPathAttrNextHop OBJECT-TYPE
704 "The address of the border router that should
705 be used for the destination network."
707 "RFC 1267, Section 4.3.
708 RFC 1267, Section 5."
709 ::= { bgpPathAttrEntry 5 }
713 bgpPathAttrInterASMetric OBJECT-TYPE
718 "The optional inter-AS metric. If this
719 attribute has not been provided for this route,
720 the value for this object is 0."
722 "RFC 1267, Section 4.3.
723 RFC 1267, Section 5."
724 ::= { bgpPathAttrEntry 6 }
726 -- BGP-4 Received Path Attribute Table. This table
727 -- contains one entry per path to a network, and path
728 -- attributes received from all peers running BGP-4.
730 bgp4PathAttrTable OBJECT-TYPE
731 SYNTAX SEQUENCE OF Bgp4PathAttrEntry
732 MAX-ACCESS not-accessible
735 "The BGP-4 Received Path Attribute Table
736 contains information about paths to
737 destination networks, received from all
741 bgp4PathAttrEntry OBJECT-TYPE
742 SYNTAX Bgp4PathAttrEntry
743 MAX-ACCESS not-accessible
746 "Information about a path to a network."
747 INDEX { bgp4PathAttrIpAddrPrefix,
748 bgp4PathAttrIpAddrPrefixLen,
750 ::= { bgp4PathAttrTable 1 }
752 Bgp4PathAttrEntry ::= SEQUENCE {
755 bgp4PathAttrIpAddrPrefixLen
757 bgp4PathAttrIpAddrPrefix
764 bgp4PathAttrASPathSegment
768 bgp4PathAttrMultiExitDisc
770 bgp4PathAttrLocalPref
772 bgp4PathAttrAtomicAggregate
774 bgp4PathAttrAggregatorAS
776 bgp4PathAttrAggregatorAddr
778 bgp4PathAttrCalcLocalPref
786 bgp4PathAttrPeer OBJECT-TYPE
791 "The IP address of the peer where the path
792 information was learned."
793 ::= { bgp4PathAttrEntry 1 }
795 bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE
796 SYNTAX Integer32 (0..32)
800 "Length in bits of the IP address prefix in
801 the Network Layer Reachability
803 ::= { bgp4PathAttrEntry 2 }
805 bgp4PathAttrIpAddrPrefix OBJECT-TYPE
810 "An IP address prefix in the Network Layer
811 Reachability Information field. This object
815 is an IP address containing the prefix with
817 bgp4PathAttrIpAddrPrefixLen.
818 Any bits beyond the length specified by
819 bgp4PathAttrIpAddrPrefixLen are zeroed."
821 "RFC 4271, Section 4.3."
822 ::= { bgp4PathAttrEntry 3 }
824 bgp4PathAttrOrigin OBJECT-TYPE
826 igp(1),-- networks are interior
827 egp(2),-- networks learned via the
829 incomplete(3) -- networks that
830 -- are learned by some other
836 "The ultimate origin of the path
839 "RFC 4271, Section 4.3.
840 RFC 4271, Section 5.1.1."
841 ::= { bgp4PathAttrEntry 4 }
843 bgp4PathAttrASPathSegment OBJECT-TYPE
844 SYNTAX OCTET STRING (SIZE (2..255))
848 "The sequence of AS path segments. Each AS
849 path segment is represented by a triple
850 <type, length, value>.
852 The type is a 1-octet field that has two
854 1 AS_SET: unordered set of ASes that a
855 route in the UPDATE message
858 2 AS_SEQUENCE: ordered set of ASes that
859 a route in the UPDATE message
862 The length is a 1-octet field containing the
866 number of ASes in the value field.
868 The value field contains one or more AS
869 numbers. Each AS is represented in the octet
870 string as a pair of octets according to the
873 first-byte-of-pair = ASNumber / 256;
874 second-byte-of-pair = ASNumber & 255;
877 o BGP Confederations will result in
878 a type of either 3 or 4.
879 o An AS Path may be longer than 255 octets.
880 This may result in this object containing
881 a truncated AS Path."
883 "RFC 4271, Section 4.3.
884 RFC 4271, Section 5.1.2."
885 ::= { bgp4PathAttrEntry 5 }
887 bgp4PathAttrNextHop OBJECT-TYPE
892 "The address of the border router that
893 should be used for the destination
894 network. This address is the NEXT_HOP
895 address received in the UPDATE packet."
897 "RFC 4271, Section 4.3.
898 RFC 4271, Section 5.1.3."
899 ::= { bgp4PathAttrEntry 6 }
901 bgp4PathAttrMultiExitDisc OBJECT-TYPE
902 SYNTAX Integer32 (-1..2147483647)
906 "This metric is used to discriminate
907 between multiple exit points to an
908 adjacent autonomous system. A value of -1
909 indicates the absence of this attribute.
912 o The BGP-4 specification uses an
913 unsigned 32 bit number. Thus, this
917 object cannot represent the full
918 range of the protocol."
920 "RFC 4271, Section 4.3.
921 RFC 4271, Section 5.1.4."
922 ::= { bgp4PathAttrEntry 7 }
924 bgp4PathAttrLocalPref OBJECT-TYPE
925 SYNTAX Integer32 (-1..2147483647)
929 "The originating BGP4 speaker's degree of
930 preference for an advertised route. A
931 value of -1 indicates the absence of this
935 o The BGP-4 specification uses an
936 unsigned 32 bit number and thus this
937 object cannot represent the full
938 range of the protocol."
940 "RFC 4271, Section 4.3.
941 RFC 4271, Section 5.1.5."
942 ::= { bgp4PathAttrEntry 8 }
944 bgp4PathAttrAtomicAggregate OBJECT-TYPE
946 lessSpecificRouteNotSelected(1),
947 -- Typo corrected from RFC 1657
948 lessSpecificRouteSelected(2)
953 "If the ATOMIC_AGGREGATE attribute is present
954 in the Path Attributes then this object MUST
955 have a value of 'lessSpecificRouteNotSelected'.
957 If the ATOMIC_AGGREGATE attribute is missing
958 in the Path Attributes then this object MUST
959 have a value of 'lessSpecificRouteSelected'.
961 Note that ATOMIC_AGGREGATE is now a primarily
962 informational attribute."
964 "RFC 4271, Sections 5.1.6 and 9.1.4."
968 ::= { bgp4PathAttrEntry 9 }
970 bgp4PathAttrAggregatorAS OBJECT-TYPE
971 SYNTAX Integer32 (0..65535)
975 "The AS number of the last BGP4 speaker that
976 performed route aggregation. A value of
977 zero (0) indicates the absence of this
980 Note that propagation of AS of zero is illegal
983 "RFC 4271, Section 5.1.7.
984 RFC 4271, Section 9.2.2.2."
985 ::= { bgp4PathAttrEntry 10 }
987 bgp4PathAttrAggregatorAddr OBJECT-TYPE
992 "The IP address of the last BGP4 speaker
993 that performed route aggregation. A
994 value of 0.0.0.0 indicates the absence
997 "RFC 4271, Section 5.1.7.
998 RFC 4271, Section 9.2.2.2."
999 ::= { bgp4PathAttrEntry 11 }
1001 bgp4PathAttrCalcLocalPref OBJECT-TYPE
1002 SYNTAX Integer32 (-1..2147483647)
1003 MAX-ACCESS read-only
1006 "The degree of preference calculated by the
1007 receiving BGP4 speaker for an advertised
1008 route. A value of -1 indicates the
1009 absence of this attribute.
1012 o The BGP-4 specification uses an
1013 unsigned 32 bit number and thus this
1014 object cannot represent the full
1015 range of the protocol."
1020 "RFC 4271, Section 9.1.1."
1021 ::= { bgp4PathAttrEntry 12 }
1023 bgp4PathAttrBest OBJECT-TYPE
1025 false(1),-- not chosen as best route
1026 true(2) -- chosen as best route
1028 MAX-ACCESS read-only
1031 "An indication of whether this route
1032 was chosen as the best BGP4 route for this
1035 "RFC 4271, Section 9.1.2."
1036 ::= { bgp4PathAttrEntry 13 }
1038 bgp4PathAttrUnknown OBJECT-TYPE
1039 SYNTAX OCTET STRING (SIZE(0..255))
1040 MAX-ACCESS read-only
1043 "One or more path attributes not understood by
1046 Path attributes are recorded in the Update Path
1047 attribute format of type, length, value.
1049 Size zero (0) indicates the absence of such
1052 Octets beyond the maximum size, if any, are not
1053 recorded by this object.
1056 o Attributes understood by this speaker, but not
1057 represented in this MIB, are unavailable to
1060 "RFC 4271, Section 5."
1061 ::= { bgp4PathAttrEntry 14 }
1064 -- Note that in RFC 1657, bgpTraps was incorrectly
1065 -- assigned a value of { bgp 7 } and each of the
1066 -- traps had the bgpPeerRemoteAddr object inappropriately
1070 -- removed from their OBJECTS clause. The following
1071 -- definitions restore the semantics of the traps as
1072 -- they were initially defined in RFC 1269.
1074 bgpNotification OBJECT IDENTIFIER ::= { bgp 0 }
1076 bgpEstablishedNotification NOTIFICATION-TYPE
1077 OBJECTS { bgpPeerRemoteAddr,
1082 "The bgpEstablishedNotification event is generated
1083 when the BGP FSM enters the established state.
1085 This Notification replaces the bgpEstablished
1087 ::= { bgpNotification 1 }
1089 bgpBackwardTransNotification NOTIFICATION-TYPE
1090 OBJECTS { bgpPeerRemoteAddr,
1095 "The bgpBackwardTransNotification event is
1096 generated when the BGP FSM moves from a higher
1097 numbered state to a lower numbered state.
1099 This Notification replaces the
1100 bgpBackwardsTransition Notification."
1101 ::= { bgpNotification 2 }
1103 -- { bgp 7 } is deprecated. Do not allocate new objects or
1104 -- notifications underneath this branch.
1106 bgpTraps OBJECT IDENTIFIER ::= { bgp 7 } -- deprecated
1108 bgpEstablished NOTIFICATION-TYPE
1109 OBJECTS { bgpPeerLastError,
1113 "The bgpEstablished event is generated when
1114 the BGP FSM enters the established state.
1116 This Notification has been replaced by the
1117 bgpEstablishedNotification Notification."
1123 bgpBackwardTransition NOTIFICATION-TYPE
1124 OBJECTS { bgpPeerLastError,
1128 "The bgpBackwardTransition event is generated
1129 when the BGP FSM moves from a higher numbered
1130 state to a lower numbered state.
1132 This Notification has been replaced by the
1133 bgpBackwardTransNotification Notification."
1136 -- Conformance information
1138 bgp4MIBConformance OBJECT IDENTIFIER
1140 bgp4MIBCompliances OBJECT IDENTIFIER
1141 ::= { bgp4MIBConformance 1 }
1142 bgp4MIBGroups OBJECT IDENTIFIER
1143 ::= { bgp4MIBConformance 2 }
1145 -- Compliance statements
1147 bgp4MIBCompliance MODULE-COMPLIANCE
1150 "The compliance statement for entities which
1151 implement the BGP4 mib."
1152 MODULE -- this module
1153 MANDATORY-GROUPS { bgp4MIBGlobalsGroup,
1155 bgp4MIBPathAttrGroup }
1156 GROUP bgp4MIBNotificationGroup
1158 "Implementation of BGP Notifications are
1159 completely optional in this MIB."
1160 ::= { bgp4MIBCompliances 1 }
1162 bgp4MIBDeprecatedCompliances MODULE-COMPLIANCE
1165 "The compliance statement documenting deprecated
1166 objects in the BGP4 mib."
1167 MODULE -- this module
1168 GROUP bgp4MIBTrapGroup
1173 "Group containing TRAP objects that were
1174 improperly converted from SMIv1 in RFC 1657.
1175 The proper semantics have been restored
1176 with the objects in bgp4MIBNotificationGroup."
1177 ::= { bgp4MIBCompliances 2 }
1179 bgp4MIBObsoleteCompliances MODULE-COMPLIANCE
1182 "The compliance statement documenting obsolete
1183 objects in the BGP4 mib."
1184 MODULE -- this module
1185 GROUP bgpRcvdPathAttrGroup
1187 "Group containing objects relevant to BGP-3
1188 and earlier objects."
1189 ::= { bgp4MIBCompliances 3 }
1191 -- Units of conformance
1193 bgp4MIBGlobalsGroup OBJECT-GROUP
1194 OBJECTS { bgpVersion,
1199 "A collection of objects providing
1200 information on global BGP state."
1201 ::= { bgp4MIBGroups 1 }
1203 bgp4MIBPeerGroup OBJECT-GROUP
1204 OBJECTS { bgpPeerIdentifier,
1207 bgpPeerNegotiatedVersion,
1215 bgpPeerInTotalMessages,
1216 bgpPeerOutTotalMessages,
1218 bgpPeerFsmEstablishedTransitions,
1219 bgpPeerFsmEstablishedTime,
1223 bgpPeerConnectRetryInterval,
1226 bgpPeerHoldTimeConfigured,
1227 bgpPeerKeepAliveConfigured,
1228 bgpPeerMinASOriginationInterval,
1229 bgpPeerMinRouteAdvertisementInterval,
1230 bgpPeerInUpdateElapsedTime }
1233 "A collection of objects for managing
1235 ::= { bgp4MIBGroups 2 }
1237 bgpRcvdPathAttrGroup OBJECT-GROUP
1238 OBJECTS { bgpPathAttrPeer,
1239 bgpPathAttrDestNetwork,
1243 bgpPathAttrInterASMetric }
1246 "A collection of objects for managing BGP-3 and
1247 earlier path entries.
1249 This conformance group, like BGP-3, is obsolete."
1250 ::= { bgp4MIBGroups 3 }
1252 bgp4MIBPathAttrGroup OBJECT-GROUP
1253 OBJECTS { bgp4PathAttrPeer,
1254 bgp4PathAttrIpAddrPrefixLen,
1255 bgp4PathAttrIpAddrPrefix,
1257 bgp4PathAttrASPathSegment,
1258 bgp4PathAttrNextHop,
1259 bgp4PathAttrMultiExitDisc,
1260 bgp4PathAttrLocalPref,
1261 bgp4PathAttrAtomicAggregate,
1262 bgp4PathAttrAggregatorAS,
1263 bgp4PathAttrAggregatorAddr,
1264 bgp4PathAttrCalcLocalPref,
1266 bgp4PathAttrUnknown }
1269 "A collection of objects for managing
1274 ::= { bgp4MIBGroups 4 }
1276 bgp4MIBTrapGroup NOTIFICATION-GROUP
1277 NOTIFICATIONS { bgpEstablished,
1278 bgpBackwardTransition }
1281 "A collection of notifications for signaling
1282 changes in BGP peer relationships.
1284 Obsoleted by bgp4MIBNotificationGroup"
1285 ::= { bgp4MIBGroups 5 }
1287 bgp4MIBNotificationGroup NOTIFICATION-GROUP
1288 NOTIFICATIONS { bgpEstablishedNotification,
1289 bgpBackwardTransNotification }
1292 "A collection of notifications for signaling
1293 changes in BGP peer relationships.
1295 Obsoletes bgp4MIBTrapGroup."
1296 ::= { bgp4MIBGroups 6 }