BGP4V2-MIB
The MIB module for the BGP-4 protocol.
Copyright (C) The IETF Trust (2011). This version of this MIB module is part of RFC XXX; see the RFC itself for full legal notices.
Main OID:
bgp4V2.1.3.6.1.4.1.1991.3.5.1
64
Objects
Active
Status
7
Dependencies
Imported Objects
Objects
64 total| Object Name |
|---|
bgp4V2The MIB module for the BGP-4 protocol.
Copyright (C) The IETF Trust (2011). This
version of this MIB module is part of RFC XXX;
see the RFC itself for full legal notices. MODULE-IDENTITY .1.3.6.1.4.1.1991.3.5.1 |
bgp4V2Notifications OBJECT IDENTIFIER .1.3.6.1.4.1.1991.3.5.1.0 |
bgp4V2EstablishedNotificationThe BGP Established event is generated when
the BGP FSM enters the established state. NOTIFICATION-TYPE .1.3.6.1.4.1.1991.3.5.1.0.1 |
bgp4V2BackwardTransitionNotificationThe BGPBackwardTransition Event is generated
when the BGP FSM moves from a higher numbered
state to a lower numbered state.
Due to the nature of the BGP state machine, an
implementation MAY rate limit the generation of this event.
An implementation MAY also generate this notification ONLY
when the state machine moves out of the established state.
An implementation should document its specific behavior. NOTIFICATION-TYPE .1.3.6.1.4.1.1991.3.5.1.0.2 |
bgp4V2Objects OBJECT IDENTIFIER .1.3.6.1.4.1.1991.3.5.1.1 |
bgp4V2PeerTableBGP peer table. This table contains, one entry per BGP
peer, information about the connections with BGP peers. SEQUENCE OF Bgp4V2PeerEntry .1.3.6.1.4.1.1991.3.5.1.1.2 |
bgp4V2PeerEntryEntry containing information about the connection with
a remote BGP peer. Bgp4V2PeerEntry .1.3.6.1.4.1.1991.3.5.1.1.2.1 |
bgp4V2PeerInstanceThe routing instance index.
Some BGP implementations permit the creation of
multiple instances of a BGP routing process. An
example includes routers running BGP/MPLS IP Virtual
Private Networks.
Implementations that do not support multiple
routing instances should return 1 for this object. Unsigned32 .1.3.6.1.4.1.1991.3.5.1.1.2.1.1 |
bgp4V2PeerLocalAddrTypeThe address family of the local end of the peering
session. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.1991.3.5.1.1.2.1.2 |
bgp4V2PeerLocalAddrThe local IP address of this entry's BGP connection. InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.1991.3.5.1.1.2.1.3 |
bgp4V2PeerRemoteAddrTypeThe address family of the remote end of the peering
session. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.1991.3.5.1.1.2.1.4 |
bgp4V2PeerRemoteAddrThe remote IP address of this entry's BGP peer. InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.1991.3.5.1.1.2.1.5 |
bgp4V2PeerLocalPortThe local port for the TCP connection between the BGP
peers.ro InetPortNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.1991.3.5.1.1.2.1.6 |
bgp4V2PeerLocalAsSome implementations of BGP can represent themselves
as multiple ASes. This is the AS that this peering
session is representing itself as to the remote peer.ro InetAutonomousSystemNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.1991.3.5.1.1.2.1.7 |
bgp4V2PeerLocalIdentifierThe BGP Identifier of the local system for this peering
session. It is REQUIRED that all bgp4V2PeerLocalIdentifier
values for the same bgp4V2PeerInstance be identical.ro Bgp4V2IdentifierTC (BGP4V2-TC-MIB) .1.3.6.1.4.1.1991.3.5.1.1.2.1.8 |
bgp4V2PeerRemotePortThe remote port for the TCP connection between the BGP
peers.
Note that the objects bgp4V2PeerLocalAddr,
bgp4V2PeerLocalPort, bgp4V2PeerRemoteAddr and
bgp4V2PeerRemotePort provide the appropriate reference to
the standard MIB TCP connection table, or even the ipv6
TCP MIB as in RFC 4022.ro InetPortNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.1991.3.5.1.1.2.1.9 |
bgp4V2PeerRemoteAsThe remote autonomous system number received in the BGP
OPEN message.ro InetAutonomousSystemNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.1991.3.5.1.1.2.1.10 |
bgp4V2PeerRemoteIdentifierThe BGP Identifier of this entry's remote BGP peer.
This entry should be 0.0.0.0 unless the
bgp4V2PeerState is in the openconfirm or the
established state.ro Bgp4V2IdentifierTC (BGP4V2-TC-MIB) .1.3.6.1.4.1.1991.3.5.1.1.2.1.11 |
bgp4V2PeerAdminStatusWhether or not the BGP FSM for this remote peer is
halted or running. The BGP FSM for a remote peer is
halted after processing a Stop event. Likewise, it is
in the running state after a Start event.
The bgp4V2PeerState will generally be in the idle state
when the FSM is halted, although some extensions such
as Graceful Restart will leave the peer in the Idle
state but with the FSM running.ro Enumeration .1.3.6.1.4.1.1991.3.5.1.1.2.1.12 |
bgp4V2PeerStateThe BGP peer connection state.ro Enumeration .1.3.6.1.4.1.1991.3.5.1.1.2.1.13 |
bgp4V2PeerDescriptionA user configured description identifying this peer. When
this object is not the empty string, this object SHOULD
contain a description that is unique within a given BGP
instance for this peer.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.1991.3.5.1.1.2.1.14 |
bgp4V2PeerErrorsTableOn a per-peer basis, this table reflects the last
protocol-defined error encountered and reported on
the peer session. SEQUENCE OF Bgp4V2PeerErrorsEntry .1.3.6.1.4.1.1991.3.5.1.1.3 |
bgp4V2PeerErrorsEntryEach entry contains information about errors sent
and received for a particular BGP peer. Bgp4V2PeerErrorsEntry .1.3.6.1.4.1.1991.3.5.1.1.3.1 |
bgp4V2PeerLastErrorCodeReceivedThe last error code received from this peer via
NOTIFICATION message on this connection. If no error has occurred, this field is zero.ro Unsigned32 .1.3.6.1.4.1.1991.3.5.1.1.3.1.1 |
bgp4V2PeerLastErrorSubCodeReceivedThe last subcode received from this peer via NOTIFICATION
message on this connection. If no error has occurred, this
field is zero.ro Unsigned32 .1.3.6.1.4.1.1991.3.5.1.1.3.1.2 |
bgp4V2PeerLastErrorReceivedTimeThe timestamp that the last NOTIFICATION was received from
this peer.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.1991.3.5.1.1.3.1.3 |
bgp4V2PeerLastErrorReceivedTextThis object contains an implementation specific
explanation of the error that was reported.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.1991.3.5.1.1.3.1.4 |
bgp4V2PeerLastErrorReceivedDataThe last error code's data seen by this peer.
Per RFC 2578, some implementations may have limitations
dealing with OCTET STRINGS larger than 255. Thus, this
data may be truncated.ro OCTET STRING .1.3.6.1.4.1.1991.3.5.1.1.3.1.5 |
bgp4V2PeerLastErrorCodeSentThe last error code sent to this peer via NOTIFICATION
message on this connection. If no error has occurred, this
field is zero.ro Unsigned32 .1.3.6.1.4.1.1991.3.5.1.1.3.1.6 |
bgp4V2PeerLastErrorSubCodeSentThe last subcode sent to this peer via NOTIFICATION
message on this connection. If no error has occurred, this field is zero.ro Unsigned32 .1.3.6.1.4.1.1991.3.5.1.1.3.1.7 |
bgp4V2PeerLastErrorSentTimeThe timestamp that the last NOTIFICATION was sent to
this peer.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.1991.3.5.1.1.3.1.8 |
bgp4V2PeerLastErrorSentTextThis object contains an implementation specific
explanation of the error that is being reported.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.1991.3.5.1.1.3.1.9 |
bgp4V2PeerLastErrorSentDataThe last error code's data sent to this peer.
Per RFC 2578, some implementations may have limitations
dealing with OCTET STRINGS larger than 255. Thus, this
data may be truncated.ro OCTET STRING .1.3.6.1.4.1.1991.3.5.1.1.3.1.10 |
bgp4V2PeerEventTimesTableA table reporting the per-peering session amount
of time elapsed and update events since the peering
session advanced into the established state. SEQUENCE OF Bgp4V2PeerEventTimesEntry .1.3.6.1.4.1.1991.3.5.1.1.4 |
bgp4V2PeerEventTimesEntryEach row contains a set of statistics about time
spent and events encountered in the peer session
established state. Bgp4V2PeerEventTimesEntry .1.3.6.1.4.1.1991.3.5.1.1.4.1 |
bgp4V2PeerFsmEstablishedTimeThis 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. If the peer has never reached the established
state, the value remains zero.ro Gauge32 UNITS "seconds" .1.3.6.1.4.1.1991.3.5.1.1.4.1.1 |
bgp4V2PeerInUpdatesElapsedTimeElapsed 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).ro Gauge32 UNITS "seconds" .1.3.6.1.4.1.1991.3.5.1.1.4.1.2 |
bgp4V2NlriTableThe BGP-4 Received Path Attribute Table contains
information about paths to destination networks
received from all BGP4 peers. Collectively, this
represents the Adj-Ribs-In. The route where
bgp4V2NlriBest is true represents, for this NLRI,
the route that is installed in the LocRib from the
Adj-Ribs-In. SEQUENCE OF Bgp4V2NlriEntry .1.3.6.1.4.1.1991.3.5.1.1.9 |
bgp4V2NlriEntryInformation about a path to a network. Bgp4V2NlriEntry .1.3.6.1.4.1.1991.3.5.1.1.9.1 |
bgp4V2NlriIndexThis index allows for multiple instances of a base
prefix for a certain AFI-SAFI from a given peer.
This is currently useful for two things:
1. Allowing for a peer in future implementations to
send more than a single route instance.
2. Allow for extensions which extend the NLRI field
to send the same prefix while utilizing other
extension specific information. An example of
this is RFC 3107 - Carrying MPLS labels in BGP. Unsigned32 .1.3.6.1.4.1.1991.3.5.1.1.9.1.1 |
bgp4V2NlriAfiThe address family of the prefix for this NLRI.
Note that the AFI is not necessarily equivalent to
the an InetAddressType. Bgp4V2AddressFamilyIdentifierTC (BGP4V2-TC-MIB) .1.3.6.1.4.1.1991.3.5.1.1.9.1.2 |
bgp4V2NlriSafiThe subsequent address family of the prefix for
this NLRI Bgp4V2SubsequentAddressFamilyIdentifierTC (BGP4V2-TC-MIB) .1.3.6.1.4.1.1991.3.5.1.1.9.1.3 |
bgp4V2NlriPrefixTypeThe type of the IP address prefix in the
Network Layer Reachability Information field.
The value of this object is derived from the
appropriate value from the bgp4V2NlriAfi field.
Where an appropriate InetAddressType is not
available, the value of the object must be
unknown(0). InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.1991.3.5.1.1.9.1.4 |
bgp4V2NlriPrefixAn IP address prefix in the Network Layer
Reachability Information field. This object
is an IP address containing the prefix with
length specified by bgp4V2NlriPrefixLen.
Any bits beyond the length specified by
bgp4V2NlriPrefixLen are zeroed. InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.1991.3.5.1.1.9.1.5 |
bgp4V2NlriPrefixLenLength in bits of the address prefix in
the Network Layer Reachability Information field. InetAddressPrefixLength (INET-ADDRESS-MIB) .1.3.6.1.4.1.1991.3.5.1.1.9.1.6 |
bgp4V2NlriBestAn indication of whether or not this route
was chosen as the best BGP4 route for this
destination.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.1991.3.5.1.1.9.1.7 |
bgp4V2NlriCalcLocalPrefThe degree of preference calculated by the
receiving BGP4 speaker for an advertised
route.
In the case where this prefix is ineligible, the
value of this object will be zero (0).ro Unsigned32 .1.3.6.1.4.1.1991.3.5.1.1.9.1.8 |
bgp4V2NlriOriginThe ultimate origin of the path information.ro Enumeration .1.3.6.1.4.1.1991.3.5.1.1.9.1.9 |
bgp4V2NlriNextHopAddrTypeThe address family of the address for
the border router that should be used
to access the destination network.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.1991.3.5.1.1.9.1.10 |
bgp4V2NlriNextHopAddrThe address of the border router that
should be used to access the destination
network. This address is the nexthop
address received in the UPDATE packet associated with
this prefix.
Note that for RFC2545 style double nexthops,
this object will always contain the global scope
nexthop. bgpPathAttrLinkLocalNextHop will contain
the linklocal scope nexthop, if it is present.
In the case a mechanism is developed to use only a link
local nexthop, bgp4V2NlriNextHopAddr will contain the
link local nexthop.ro InetAddress .1.3.6.1.4.1.1991.3.5.1.1.9.1.11 |
bgp4V2NlriLinkLocalNextHopAddrTypeThe address type for IPv6 link local addresses.
This is present only when receiving RFC 2545
style double nexthops.
This object is optionally present in BGP
implementations that do not support IPv6.
When no IPv6 link local nexthop is present, the value of
this object should be unknown(0).ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.1991.3.5.1.1.9.1.12 |
bgp4V2NlriLinkLocalNextHopAddrThis value contains an IPv6 link local address
and is present only when receiving RFC 2545 style
double nexthops.
This object is optionally present in BGP
implementations that do not support IPv6.
When no IPv6 link local nexthop is present, the length of
this object should be zero.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.1991.3.5.1.1.9.1.13 |
bgp4V2NlriLocalPrefPresentThis value is true when the LOCAL_PREF value was sent in
the UPDATE message.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.1991.3.5.1.1.9.1.14 |
bgp4V2NlriLocalPrefThe originating BGP4 speakers degree of preference for an
advertised route.ro Unsigned32 .1.3.6.1.4.1.1991.3.5.1.1.9.1.15 |
bgp4V2NlriMedPresentThis value is true when the MED value was sent in
the UPDATE message.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.1991.3.5.1.1.9.1.16 |
bgp4V2NlriMedThis metric is used to discriminate between multiple
exit points to an adjacent autonomous system. When the MED
value is absent but has a calculated default value, this
object will contain the calculated value.ro Unsigned32 .1.3.6.1.4.1.1991.3.5.1.1.9.1.17 |
bgp4V2NlriAtomicAggregateThis value is true when the ATOMIC_AGGREGATE Path Attribute
is present and indicates that the NLRI MUST NOT be made
more specific.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.1991.3.5.1.1.9.1.18 |
bgp4V2NlriAggregatorPresentThis value is true when the AGGREGATOR path attribute
was sent in the UPDATE message.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.1991.3.5.1.1.9.1.19 |
bgp4V2NlriAggregatorASThe AS number of the last BGP4 speaker that performed route
aggregation. When bgp4V2NlriAggregatorPresent is
false, the value of this object should be zero (0).ro InetAutonomousSystemNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.1991.3.5.1.1.9.1.20 |
bgp4V2NlriAggregatorAddrThe IP address of the last BGP4 speaker that performed
route aggregation. When bgp4V2NlriAggregatorPresent is
false, the value of this object should be 0.0.0.0ro Bgp4V2IdentifierTC (BGP4V2-TC-MIB) .1.3.6.1.4.1.1991.3.5.1.1.9.1.21 |
bgp4V2NlriAsPathCalcLengthThis value represents the calculated length of the
AS Path according to the rules of the BGP
specification. This value is used in route selection.ro Unsigned32 .1.3.6.1.4.1.1991.3.5.1.1.9.1.22 |
bgp4V2NlriAsPathStringThis is a string depicting the autonomous system
path to this network which was received from the
peer which advertised it. The format of the string
is implementation-dependent, and should be designed
for operator readability.
Note that SnmpAdminString is only capable of representing a
maximum of 255 characters. This may lead to the string
being truncated in the presence of a large AS Path. It is
RECOMMENDED that when this object's contents will be
truncated that the final 3 octets be reserved for the
ellipses string, '...'. bgp4V2NlriAsPath may give access
to the full AS Path.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.1991.3.5.1.1.9.1.23 |
bgp4V2NlriAsPathIn order to provide a canonicalized form of the BGP-4
AS_PATH along with the human-readable
bgp4V2NlriAsPathString, which may be truncated, this object
contains the contents of the BGP-4 AS_PATH Path Attribute.
This object may be parsed using the rules defined for
Four-octet ASes as defined in RFC 4893. RFC 4271, Section
4.3, 'Path Attributes: b) AS_PATH' as amended by RFC 5065,
Section 3 defines the general format of the AS_PATH path
attribute and its code points.
In brief, the AS_PATH is composed of a sequence of AS
Segments. Each AS Segment is represented by a triple:
<path segment type, path segment length,
path segment value>.
The path segment type and path segment length fields are
one octet in length each.
The path segment type field may be one of:
1 - AS_SET (RFC 4721, Section 4.3)
2 - AS_SEQUENCE (RFC 4721, Section 4.3)
3 - AS_CONFED_SEQUENCE (RFC 3065, Section 5)
4 - AS_CONFED_SET (RFC 3065, Section 5)
The path segment length field contains the number of ASes
(not the number of octets) in the path segment value field.
The path segment value field contains one or more AS
numbers, each encoded as a 4-octet length field in network
byte order.
Note that since an SNMP agent may truncate this object to
less than its maximum theoretical length of 4072 octets
users of this object should be prepared to deal with a
truncated and thus malformed AS_PATH. It is RECOMMENDED
that when such truncation would occur on the boundary of an
encoded AS that the partial AS be discarded from this
object and the object's size be adjusted accordingly.
Further, it is also RECOMMENDED that when such truncation,
either alone or in conjuction with the truncation of a
partially encoded AS described previously, would yield an
empty path segment value field that the path segment type
and path segment length components of the truncated AS_PATH
also be discarded and the object's size be adjusted
accordingly.ro OCTET STRING .1.3.6.1.4.1.1991.3.5.1.1.9.1.24 |
bgp4V2NlriPathAttrUnknownPath Attributes not understood by this implementation
SHOULD be be presented in this object. Those Path
Attributes use the type, length, value encoding documented
in RFC 4271, Section 4.3, 'Path Attributes'.
Note that since an SNMP agent may truncate this object to
less than its maximum theoretical length of 4072 octets
users of this object should be prepared to deal with a
truncated and thus malformed Path Attribute.ro OCTET STRING .1.3.6.1.4.1.1991.3.5.1.1.9.1.25 |