The MIB module for the BGP-4 protocol.
Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4273; see the RFC itself for full legal notices.
Vector of supported BGP protocol version numbers. Each peer negotiates the version from this vector. Versions are identified via the string of bits contained within this object. The first octet contains bits 0 to 7, the second octet contains bits 8 to 15, and so on, with the most significant bit referring to the lowest bit number in the octet (e.g., the MSB of the first octet refers to bit 0). If a bit, i, is present and set, then the version (i+1) of the BGP is supported. Reference: RFC 4271, Section 4.2.
bgpLocalAs
1.3.6.1.2.1.15.2
Integer32 (0..65535)
The local autonomous system number. Reference: RFC 4271, Section 4.2, 'My Autonomous System'.
bgpIdentifier
1.3.6.1.2.1.15.4
IpAddress SIZE (4)
The BGP Identifier of the local system. Reference: RFC 4271, Section 4.2.
Table details
bgpPeerTable
1.3.6.1.2.1.15.3
Index: bgpPeerRemoteAddr
BGP peer table. This table contains, one entry per BGP peer, information about the connections with BGP peers.
bgpPeerIdentifier
1.3.6.1.2.1.15.3.1.1
IpAddress SIZE (4)
The BGP Identifier of this entry's BGP peer. This entry MUST be 0.0.0.0 unless the bgpPeerState is in the openconfirm or the established state. Reference: RFC 4271, Section 4.2, 'BGP Identifier'.
The BGP peer connection state. Reference: RFC 4271, Section 8.2.2.
bgpPeerAdminStatus
1.3.6.1.2.1.15.3.1.3
INTEGER1 = stop2 = start · Integer32
The desired state of the BGP connection. A transition from 'stop' to 'start' will cause the BGP Manual Start Event to be generated. A transition from 'start' to 'stop' will cause the BGP Manual Stop Event to be generated. This parameter can be used to restart BGP peer connections. Care should be used in providing write access to this object without adequate authentication. Reference: RFC 4271, Section 8.1.2.
bgpPeerNegotiatedVersion
1.3.6.1.2.1.15.3.1.4
Integer32
The negotiated version of BGP running between the two peers.
This entry MUST be zero (0) unless the bgpPeerState is in the openconfirm or the established state.
Note that legal values for this object are between 0 and 255. Reference: RFC 4271, Section 4.2. RFC 4271, Section 7.
bgpPeerLocalAddr
1.3.6.1.2.1.15.3.1.5
IpAddress SIZE (4)
The local IP address of this entry's BGP connection.
bgpPeerLocalPort
1.3.6.1.2.1.15.3.1.6
Integer32 (0..65535)
The local port for the TCP connection between the BGP peers.
bgpPeerRemoteAddr
1.3.6.1.2.1.15.3.1.7
IpAddress SIZE (4)
The remote IP address of this entry's BGP peer.
bgpPeerRemotePort
1.3.6.1.2.1.15.3.1.8
Integer32 (0..65535)
The remote port for the TCP connection between the BGP peers. Note that the objects bgpPeerLocalAddr, bgpPeerLocalPort, bgpPeerRemoteAddr, and bgpPeerRemotePort provide the appropriate reference to the standard MIB TCP connection table.
bgpPeerRemoteAs
1.3.6.1.2.1.15.3.1.9
Integer32 (0..65535)
The remote autonomous system number received in the BGP OPEN message. Reference: RFC 4271, Section 4.2.
bgpPeerInUpdates
1.3.6.1.2.1.15.3.1.10
Counter32
The number of BGP UPDATE messages received on this connection. Reference: RFC 4271, Section 4.3.
bgpPeerOutUpdates
1.3.6.1.2.1.15.3.1.11
Counter32
The number of BGP UPDATE messages transmitted on this connection. Reference: RFC 4271, Section 4.3.
bgpPeerInTotalMessages
1.3.6.1.2.1.15.3.1.12
Counter32
The total number of messages received from the remote peer on this connection. Reference: RFC 4271, Section 4.
bgpPeerOutTotalMessages
1.3.6.1.2.1.15.3.1.13
Counter32
The total number of messages transmitted to the remote peer on this connection. Reference: RFC 4271, Section 4.
bgpPeerLastError
1.3.6.1.2.1.15.3.1.14
OCTET STRING SIZE (2)
The last error code and subcode seen by this peer on this connection. If no error has occurred, this field is zero. Otherwise, the first byte of this two byte OCTET STRING contains the error code, and the second byte contains the subcode. Reference: RFC 4271, Section 4.5.
bgpPeerFsmEstablishedTransitions
1.3.6.1.2.1.15.3.1.15
Counter32
The total number of times the BGP FSM transitioned into the established state for this peer. Reference: RFC 4271, Section 8.
bgpPeerFsmEstablishedTime
1.3.6.1.2.1.15.3.1.16
Gauge32 · seconds
This timer indicates how long (in seconds) this peer has been in the established state or how long since this peer was last in the established state. It is set to zero when a new peer is configured or when the router is booted. Reference: RFC 4271, Section 8.
bgpPeerConnectRetryInterval
1.3.6.1.2.1.15.3.1.17
Integer32 (1..65535) · seconds
Time interval (in seconds) for the ConnectRetry timer. The suggested value for this timer is 120 seconds. Reference: RFC 4271, Section 8.2.2. This is the value used to initialize the 'ConnectRetryTimer'.
bgpPeerHoldTime
1.3.6.1.2.1.15.3.1.18
Integer32 (0 | 3..65535) · seconds
Time interval (in seconds) for the Hold Timer established with the peer. The value of this object is calculated by this BGP speaker, using the smaller of the values in bgpPeerHoldTimeConfigured and the Hold Time received in the OPEN message.
This value must be at least three seconds if it is not zero (0).
If the Hold Timer has not been established with the peer this object MUST have a value of zero (0).
If the bgpPeerHoldTimeConfigured object has a value of (0), then this object MUST have a value of (0). Reference: RFC 4271, Section 4.2.
bgpPeerKeepAlive
1.3.6.1.2.1.15.3.1.19
Integer32 (0 | 1..21845) · seconds
Time interval (in seconds) for the KeepAlive timer established with the peer. The value of this object is calculated by this BGP speaker such that, when compared with bgpPeerHoldTime, it has the same proportion that bgpPeerKeepAliveConfigured has, compared with bgpPeerHoldTimeConfigured.
If the KeepAlive timer has not been established with the peer, this object MUST have a value of zero (0).
If the of bgpPeerKeepAliveConfigured object has a value of (0), then this object MUST have a value of (0). Reference: RFC 4271, Section 4.4.
bgpPeerHoldTimeConfigured
1.3.6.1.2.1.15.3.1.20
Integer32 (0 | 3..65535) · seconds
Time interval (in seconds) for the Hold Time configured for this BGP speaker with this peer. This value is placed in an OPEN message sent to this peer by this BGP speaker, and is compared with the Hold Time field in an OPEN message received from the peer when determining the Hold Time (bgpPeerHoldTime) with the peer. This value must not be less than three seconds if it is not zero (0). If it is zero (0), the Hold Time is NOT to be established with the peer. The suggested value for this timer is 90 seconds. Reference: RFC 4271, Section 4.2. RFC 4271, Section 10.
bgpPeerKeepAliveConfigured
1.3.6.1.2.1.15.3.1.21
Integer32 (0 | 1..21845) · seconds
Time interval (in seconds) for the KeepAlive timer configured for this BGP speaker with this peer. The value of this object will only determine the KEEPALIVE messages' frequency relative to the value specified in bgpPeerHoldTimeConfigured; the actual time interval for the KEEPALIVE messages is indicated by bgpPeerKeepAlive. A reasonable maximum value for this timer would be one third of that of bgpPeerHoldTimeConfigured. If the value of this object is zero (0), no periodical KEEPALIVE messages are sent to the peer after the BGP connection has been established. The suggested value for this timer is 30 seconds. Reference: RFC 4271, Section 4.4. RFC 4271, Section 10.
bgpPeerMinASOriginationInterval
1.3.6.1.2.1.15.3.1.22
Integer32 (1..65535) · seconds
Time interval (in seconds) for the MinASOriginationInterval timer. The suggested value for this timer is 15 seconds. Reference: RFC 4271, Section 9.2.1.2. RFC 4271, Section 10.
bgpPeerMinRouteAdvertisementInterval
1.3.6.1.2.1.15.3.1.23
Integer32 (1..65535) · seconds
Time interval (in seconds) for the MinRouteAdvertisementInterval timer. The suggested value for this timer is 30 seconds for EBGP connections and 5 seconds for IBGP connections. Reference: RFC 4271, Section 9.2.1.1. RFC 4271, Section 10.
bgpPeerInUpdateElapsedTime
1.3.6.1.2.1.15.3.1.24
Gauge32 · seconds
Elapsed time (in seconds) since the last BGP UPDATE message was received from the peer. Each time bgpPeerInUpdates is incremented, the value of this object is set to zero (0). Reference: RFC 4271, Section 4.3. RFC 4271, Section 8.2.2, Established state.
bgpRcvdPathAttrTable
1.3.6.1.2.1.15.5
Index: bgpPathAttrDestNetwork · bgpPathAttrPeer
The BGP Received Path Attribute Table contains information about paths to destination networks, received from all peers running BGP version 3 or less.
bgpPathAttrPeer
1.3.6.1.2.1.15.5.1.1
IpAddress SIZE (4)
The IP address of the peer where the path information was learned.
bgpPathAttrDestNetwork
1.3.6.1.2.1.15.5.1.2
IpAddress SIZE (4)
The address of the destination network. Reference: RFC 1267, Section 4.3.
bgpPathAttrOrigin
1.3.6.1.2.1.15.5.1.3
INTEGER1 = igp2 = egp3 = incomplete · Integer32
The ultimate origin of the path information. Reference: RFC 1267, Section 4.3. RFC 1267, Section 5.
bgpPathAttrASPath
1.3.6.1.2.1.15.5.1.4
OCTET STRING SIZE (2..255)
The set of ASes that must be traversed to reach the network. This object is probably best represented as SEQUENCE OF INTEGER. For SMI compatibility, though, it is represented as OCTET STRING. Each AS is represented as a pair of octets according to the following algorithm:
first-byte-of-pair = ASNumber / 256; second-byte-of-pair = ASNumber & 255; Reference: RFC 1267, Section 4.3. RFC 1267, Section 5.
bgpPathAttrNextHop
1.3.6.1.2.1.15.5.1.5
IpAddress SIZE (4)
The address of the border router that should be used for the destination network. Reference: RFC 1267, Section 4.3. RFC 1267, Section 5.
bgpPathAttrInterASMetric
1.3.6.1.2.1.15.5.1.6
Integer32
The optional inter-AS metric. If this attribute has not been provided for this route, the value for this object is 0. Reference: RFC 1267, Section 4.3. RFC 1267, Section 5.
The BGP-4 Received Path Attribute Table contains information about paths to destination networks, received from all BGP4 peers.
bgp4PathAttrPeer
1.3.6.1.2.1.15.6.1.1
IpAddress SIZE (4)
The IP address of the peer where the path information was learned.
bgp4PathAttrIpAddrPrefixLen
1.3.6.1.2.1.15.6.1.2
Integer32 (0..32)
Length in bits of the IP address prefix in the Network Layer Reachability Information field.
bgp4PathAttrIpAddrPrefix
1.3.6.1.2.1.15.6.1.3
IpAddress SIZE (4)
An IP address prefix in the Network Layer Reachability Information field. This object is an IP address containing the prefix with length specified by bgp4PathAttrIpAddrPrefixLen. Any bits beyond the length specified by bgp4PathAttrIpAddrPrefixLen are zeroed. Reference: RFC 4271, Section 4.3.
bgp4PathAttrOrigin
1.3.6.1.2.1.15.6.1.4
INTEGER1 = igp2 = egp3 = incomplete · Integer32
The ultimate origin of the path information. Reference: RFC 4271, Section 4.3. RFC 4271, Section 5.1.1.
bgp4PathAttrASPathSegment
1.3.6.1.2.1.15.6.1.5
OCTET STRING SIZE (2..255)
The sequence of AS path segments. Each AS path segment is represented by a triple <type, length, value>.
The type is a 1-octet field that has two possible values:
1 AS_SET: unordered set of ASes that a
route in the UPDATE message has traversed
2 AS_SEQUENCE: ordered set of ASes that
a route in the UPDATE message has traversed.
The length is a 1-octet field containing the number of ASes in the value field.
The value field contains one or more AS numbers. Each AS is represented in the octet string as a pair of octets according to the following algorithm:
first-byte-of-pair = ASNumber / 256; second-byte-of-pair = ASNumber & 255;
Known Issues: o BGP Confederations will result in a type of either 3 or 4. o An AS Path may be longer than 255 octets. This may result in this object containing a truncated AS Path. Reference: RFC 4271, Section 4.3. RFC 4271, Section 5.1.2.
bgp4PathAttrNextHop
1.3.6.1.2.1.15.6.1.6
IpAddress SIZE (4)
The address of the border router that should be used for the destination network. This address is the NEXT_HOP address received in the UPDATE packet. Reference: RFC 4271, Section 4.3. RFC 4271, Section 5.1.3.
bgp4PathAttrMultiExitDisc
1.3.6.1.2.1.15.6.1.7
Integer32 (-1..2147483647)
This metric is used to discriminate between multiple exit points to an adjacent autonomous system. A value of -1 indicates the absence of this attribute.
Known Issues: o The BGP-4 specification uses an unsigned 32 bit number. Thus, this object cannot represent the full range of the protocol. Reference: RFC 4271, Section 4.3. RFC 4271, Section 5.1.4.
bgp4PathAttrLocalPref
1.3.6.1.2.1.15.6.1.8
Integer32 (-1..2147483647)
The originating BGP4 speaker's degree of preference for an advertised route. A value of -1 indicates the absence of this attribute.
Known Issues: o The BGP-4 specification uses an unsigned 32 bit number and thus this object cannot represent the full range of the protocol. Reference: RFC 4271, Section 4.3. RFC 4271, Section 5.1.5.
If the ATOMIC_AGGREGATE attribute is present in the Path Attributes then this object MUST have a value of 'lessSpecificRouteNotSelected'.
If the ATOMIC_AGGREGATE attribute is missing in the Path Attributes then this object MUST have a value of 'lessSpecificRouteSelected'.
Note that ATOMIC_AGGREGATE is now a primarily informational attribute. Reference: RFC 4271, Sections 5.1.6 and 9.1.4.
bgp4PathAttrAggregatorAS
1.3.6.1.2.1.15.6.1.10
Integer32 (0..65535)
The AS number of the last BGP4 speaker that performed route aggregation. A value of zero (0) indicates the absence of this attribute.
Note that propagation of AS of zero is illegal in the Internet. Reference: RFC 4271, Section 5.1.7. RFC 4271, Section 9.2.2.2.
bgp4PathAttrAggregatorAddr
1.3.6.1.2.1.15.6.1.11
IpAddress SIZE (4)
The IP address of the last BGP4 speaker that performed route aggregation. A value of 0.0.0.0 indicates the absence of this attribute. Reference: RFC 4271, Section 5.1.7. RFC 4271, Section 9.2.2.2.
bgp4PathAttrCalcLocalPref
1.3.6.1.2.1.15.6.1.12
Integer32 (-1..2147483647)
The degree of preference calculated by the receiving BGP4 speaker for an advertised route. A value of -1 indicates the absence of this attribute.
Known Issues: o The BGP-4 specification uses an unsigned 32 bit number and thus this object cannot represent the full range of the protocol. Reference: RFC 4271, Section 9.1.1.
bgp4PathAttrBest
1.3.6.1.2.1.15.6.1.13
INTEGER1 = false2 = true · Integer32
An indication of whether this route was chosen as the best BGP4 route for this destination. Reference: RFC 4271, Section 9.1.2.
bgp4PathAttrUnknown
1.3.6.1.2.1.15.6.1.14
OCTET STRING SIZE (0..255)
One or more path attributes not understood by this BGP4 speaker.
Path attributes are recorded in the Update Path attribute format of type, length, value.
Size zero (0) indicates the absence of such attributes.
Octets beyond the maximum size, if any, are not recorded by this object.
Known Issues: o Attributes understood by this speaker, but not represented in this MIB, are unavailable to the agent. Reference: RFC 4271, Section 5.
Trap details
bgpEstablishedNotification
1.3.6.1.2.1.15.0.1
The bgpEstablishedNotification event is generated when the BGP FSM enters the established state.
This Notification replaces the bgpEstablished Notification.
bgpPeerRemoteAddr
1.3.6.1.2.1.15.3.1.7
IpAddress SIZE (4)
The remote IP address of this entry's BGP peer.
bgpPeerLastError
1.3.6.1.2.1.15.3.1.14
OCTET STRING SIZE (2)
The last error code and subcode seen by this peer on this connection. If no error has occurred, this field is zero. Otherwise, the first byte of this two byte OCTET STRING contains the error code, and the second byte contains the subcode. Reference: RFC 4271, Section 4.5.
The BGP peer connection state. Reference: RFC 4271, Section 8.2.2.
bgpBackwardTransNotification
1.3.6.1.2.1.15.0.2
The bgpBackwardTransNotification event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state.
This Notification replaces the bgpBackwardsTransition Notification.
bgpPeerRemoteAddr
1.3.6.1.2.1.15.3.1.7
IpAddress SIZE (4)
The remote IP address of this entry's BGP peer.
bgpPeerLastError
1.3.6.1.2.1.15.3.1.14
OCTET STRING SIZE (2)
The last error code and subcode seen by this peer on this connection. If no error has occurred, this field is zero. Otherwise, the first byte of this two byte OCTET STRING contains the error code, and the second byte contains the subcode. Reference: RFC 4271, Section 4.5.
The BGP peer connection state. Reference: RFC 4271, Section 8.2.2.
bgpEstablished
1.3.6.1.2.1.15.7.1
The bgpEstablished event is generated when the BGP FSM enters the established state.
This Notification has been replaced by the bgpEstablishedNotification Notification.
bgpPeerLastError
1.3.6.1.2.1.15.3.1.14
OCTET STRING SIZE (2)
The last error code and subcode seen by this peer on this connection. If no error has occurred, this field is zero. Otherwise, the first byte of this two byte OCTET STRING contains the error code, and the second byte contains the subcode. Reference: RFC 4271, Section 4.5.
The BGP peer connection state. Reference: RFC 4271, Section 8.2.2.
bgpBackwardTransition
1.3.6.1.2.1.15.7.2
The bgpBackwardTransition event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state.
This Notification has been replaced by the bgpBackwardTransNotification Notification.
bgpPeerLastError
1.3.6.1.2.1.15.3.1.14
OCTET STRING SIZE (2)
The last error code and subcode seen by this peer on this connection. If no error has occurred, this field is zero. Otherwise, the first byte of this two byte OCTET STRING contains the error code, and the second byte contains the subcode. Reference: RFC 4271, Section 4.5.