DELLEMC-OS10-BGP4V2-MIB

TEXTUAL-CONVENTION

The representation of a BGP AFI. The value of this object should be restricted to be between the values of 0 and 65535.

TEXTUAL-CONVENTION

The representation of a BGP Identifier. BGP Identifiers are presented in the received network byte order. The BGP Identifier is displayed as if it is an IP address, even if it would be an illegal one.

TEXTUAL-CONVENTION

The representation of a BGP SAFI

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

Table of BGP-4 discontinuities. Discontinuities that have external visibility occur on a per-BGP instance basis. Transitions by a given BGP peer will result in a consistent BGP view within that instance and thus do not represent a discontinuity from a protocol standpoint.

OBJECT-TYPE

Entry repsenting information about a discontinuity event for a given BGP instance.

OBJECT-TYPE

The value of sysUpTime at the most recent occasion at which this BGP management instance has suffered a discontinuity.

OBJECT-TYPE

BGP peer table. This table contains, one entry per BGP peer, information about the connections with BGP peers.

OBJECT-TYPE

Entry containing information about the connection with a remote BGP peer.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The address family of the local end of the peering session.

OBJECT-TYPE

The local IP address of this entry's BGP connection. An implementation is required to support IPv4 peering sessions in which case the length of this object is 4. An implementation MAY support IPv6 peering sessions in which case the length of this object is 16. IPv6 link-local peering sessions MAY be supported by this MIB. In this case the length of this object is 20.

OBJECT-TYPE

The address family of the remote end of the peering session. An implementation is required to support IPv4 peering sessions in which case the length of this object is 4. An implementation MAY support IPv6 peering sessions in which case the length of this object is 16. IPv6 link-local peering sessions MAY be supported by this MIB. In this case the length of this object is 20.

OBJECT-TYPE

The remote IP address of this entry's BGP peer.

OBJECT-TYPE

The local port for the TCP connection between the BGP peers.

OBJECT-TYPE

Some 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.

OBJECT-TYPE

The BGP Identifier of the local system for this peering session. It is REQUIRED that all os10bgp4V2PeerLocalIdentifier values for the same os10bgp4V2PeerInstance be identical.

OBJECT-TYPE

The remote port for the TCP connection between the BGP peers. Note that the objects os10bgp4V2PeerLocalAddr, os10bgp4V2PeerLocalPort, os10bgp4V2PeerRemoteAddr and os10bgp4V2PeerRemotePort provide the appropriate reference to the standard MIB TCP connection table, or even the ipv6 TCP MIB as in RFC 4022.

OBJECT-TYPE

The remote autonomous system number received in the BGP OPEN message.

OBJECT-TYPE

The BGP Identifier of this entry's remote BGP peer. This entry should be 0.0.0.0 unless the os10bgp4V2PeerState is in the openconfirm or the established state.

OBJECT-TYPE

Whether 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 os10bgp4V2PeerState 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.

OBJECT-TYPE

The BGP peer connection state.

OBJECT-TYPE

A 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.

OBJECT-TYPE

On a per-peer basis, this table reflects the last protocol-defined error encountered and reported on the peer session.

OBJECT-TYPE

Each entry contains information about errors sent and received for a particular BGP peer.

OBJECT-TYPE

The last error code received from this peer via NOTIFICATION message on this connection. If no error has occurred, this field is zero.

OBJECT-TYPE

The last subcode received from this peer via NOTIFICATION message on this connection. If no error has occurred, this field is zero.

OBJECT-TYPE

The timestamp that the last NOTIFICATION was received from this peer.

OBJECT-TYPE

This object contains an implementation specific explanation of the error that was reported.

OBJECT-TYPE

The 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.

OBJECT-TYPE

The last error code sent to this peer via NOTIFICATION message on this connection. If no error has occurred, this field is zero.

OBJECT-TYPE

The last subcode sent to this peer via NOTIFICATION message on this connection. If no error has occurred, this field is zero.

OBJECT-TYPE

The timestamp that the last NOTIFICATION was sent to this peer.

OBJECT-TYPE

This object contains an implementation specific explanation of the error that is being reported.

OBJECT-TYPE

The 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.

OBJECT-TYPE

A table reporting the per-peering session amount of time elapsed and update events since the peering session advanced into the established state.

OBJECT-TYPE

Each row contains a set of statistics about time spent and events encountered in the peer session established state.

OBJECT-TYPE

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. If the peer has never reached the established state, the value remains zero.

OBJECT-TYPE

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).

OBJECT-TYPE

Per peer management data on BGP session timers.

OBJECT-TYPE

Each entry corresponds to the current state of BGP timers on a given peering session.

OBJECT-TYPE

Time interval (in seconds) for the ConnectRetry timer. The suggested value for this timer is 120 seconds.

OBJECT-TYPE

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).

OBJECT-TYPE

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 periodic KEEPALIVE messages are sent to the peer after the BGP connection has been established. The suggested value for this timer is 30 seconds.

OBJECT-TYPE

Time interval (in seconds) for the MinASOriginationInterval timer. The suggested value for this timer is 15 seconds.

OBJECT-TYPE

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.

OBJECT-TYPE

Configured values of per-peer timers are seen in the os10bgp4V2PeerConfiguredTimersTable. Values in this table reflect the current operational values, after negotiation from values derived from initial configuration.

OBJECT-TYPE

Each entry reflects a value of the currently operational, negotiated timer as reflected in the Os10Bgp4V2PeerNegotiatedTimersEntry.

OBJECT-TYPE

The value of this object is calculated by this BGP Speaker as being; zero (0) - if this was the value sent by the peer and this value is permitted by this BGP Speaker. In this case, no keepalive messages are sent and the Hold Timer is not set. At least three (3). This value is the smaller of the value sent by this peer in the OPEN message and os10bgp4V2PeerHoldTimeConfigured for this peer. If the peer is not in the established state, the value of this object is zero (0).

OBJECT-TYPE

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 os10bgp4V2PeerHoldTime, it has the same proportion as what os10bgp4V2PeerKeepAliveConfigured has when compared with os10bgp4V2PeerHoldTimeConfigured. If the value of this object is zero (0), it indicates that the KeepAlive timer has not been established with the peer, or, the value of os10bgp4V2PeerKeepAliveConfigured is zero (0). If the peer is not in the established state, the value of this object is zero (0).

OBJECT-TYPE

The counters associated with a BGP Peer.

OBJECT-TYPE

Each entry contains counters of message transmissions and FSM transitions for a given BGP Peering session.

OBJECT-TYPE

The number of BGP UPDATE messages received on this connection.

OBJECT-TYPE

The number of BGP UPDATE messages transmitted on this connection.

OBJECT-TYPE

The total number of messages received from the remote peer on this connection.

OBJECT-TYPE

The total number of messages transmitted to the remote peer on this connection.

OBJECT-TYPE

The total number of times the BGP FSM transitioned into the established state for this peer.

OBJECT-TYPE

Additional per-peer, per AFI-SAFI counters for prefixes

OBJECT-TYPE

Entry containing information about a bgp-peers prefix counters.

OBJECT-TYPE

The AFI index of the per-peer, per prefix counters

OBJECT-TYPE

The SAFI index of the per-peer, per prefix counters

OBJECT-TYPE

The number of prefixes received from a peer and are stored in the Adj-Ribs-In for that peer. Note that this number does not reflect prefixes that have been discarded due to policy.

OBJECT-TYPE

The number of prefixes for a peer that are installed in the Adj-Ribs-In and are eligible to become active in the Loc-Rib.

OBJECT-TYPE

The number of prefixes for a peer that are installed in that peer's Adj-Ribs-Out.

OBJECT-TYPE

The 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 os10bgp4V2NlriBest is true represents, for this NLRI, the route that is installed in the LocRib from the Adj-Ribs-In.

OBJECT-TYPE

Information about a path to a network.

OBJECT-TYPE

This 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.

OBJECT-TYPE

The address family of the prefix for this NLRI. Note that the AFI is not necessarily equivalent to the an InetAddressType.

OBJECT-TYPE

The subsequent address family of the prefix for this NLRI

OBJECT-TYPE

The 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 os10bgp4V2NlriAfi field. Where an appropriate InetAddressType is not available, the value of the object must be unknown(0).

OBJECT-TYPE

An IP address prefix in the Network Layer Reachability Information field. This object is an IP address containing the prefix with length specified by os10bgp4V2NlriPrefixLen. Any bits beyond the length specified by os10bgp4V2NlriPrefixLen are zeroed. An implementation is required to support IPv4 prefixes. In this case, the object length is (0..4). An implementation MAY support IPv6 prefixes. In this case, the object length is (0..16)

OBJECT-TYPE

Length in bits of the address prefix in the Network Layer Reachability Information field.

OBJECT-TYPE

An indication of whether or not this route was chosen as the best BGP4 route for this destination.

OBJECT-TYPE

The 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).

OBJECT-TYPE

The ultimate origin of the path information.

OBJECT-TYPE

The address family of the address for the border router that should be used to access the destination network.

OBJECT-TYPE

The 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, os10bgp4V2NlriNextHopAddr will contain the link local nexthop.

OBJECT-TYPE

The 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).

OBJECT-TYPE

This 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.

OBJECT-TYPE

This value is true when the LOCAL_PREF value was sent in the UPDATE message.

OBJECT-TYPE

The originating BGP4 speakers degree of preference for an advertised route.

OBJECT-TYPE

This value is true when the MED value was sent in the UPDATE message.

OBJECT-TYPE

This 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.

OBJECT-TYPE

This value is true when the ATOMIC_AGGREGATE Path Attribute is present and indicates that the NLRI MUST NOT be made more specific.

OBJECT-TYPE

This value is true when the AGGREGATOR path attribute was sent in the UPDATE message.

OBJECT-TYPE

The AS number of the last BGP4 speaker that performed route aggregation. When os10bgp4V2NlriAggregatorPresent is false, the value of this object should be zero (0).

OBJECT-TYPE

The IP address of the last BGP4 speaker that performed route aggregation. When os10bgp4V2NlriAggregatorPresent is false, the value of this object should be 0.0.0.0

OBJECT-TYPE

This value represents the calculated length of the AS Path according to the rules of the BGP specification. This value is used in route selection.

OBJECT-TYPE

This 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, '...'. os10bgp4V2NlriAsPath may give access to the full AS Path.

OBJECT-TYPE

In order to provide a canonicalized form of the BGP-4 AS_PATH along with the human-readable os10bgp4V2NlriAsPathString, 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.

OBJECT-TYPE

Path 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.

OBJECT-TYPE

This table contains on a per-peer basis one or more routes from the os10bgp4V2NlriTable that have been placed in this peer's Adj-Ribs-Out.

OBJECT-TYPE

List of BGP routes that have been placed into a peer's Adj-Ribs-Out.

OBJECT-TYPE

Certain extensions to BGP permit multiple instance of a per afi, per safi prefix to be advertised to a peer. This object allows the enumeration of them.

OBJECT-TYPE

This object points to the route in the os10bgp4V2NlriTable that corresponds to the entry in the peer's Adj-Rib-Out. Outgoing route maps are not reflected at this point as those are part of the Update-Send process.

OBJECT-IDENTITY