DELLEMC-OS10-BGP4V2-MIB
AI MIB Summary
The DELLEMC-OS10-BGP4V2-MIB module enables monitoring and management of Border Gateway Protocol version 4 (BGP-4) operations on Dell EMC OS10 switches, specifically tracking BGP peer session states, route advertisements, and protocol counters. It provides granular visibility into BGP neighbor relationships, including up/down transitions, prefix counts, and error statistics for network path analysis and troubleshooting.
The MIB module for the BGP-4 protocol.
Main OID:
os10Bgp4V2Mib.1.3.6.1.4.1.674.11000.5000.200.1
95
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
95 total| Object Name |
|---|
os10Bgp4V2MibThe MIB module for the BGP-4 protocol. MODULE-IDENTITY .1.3.6.1.4.1.674.11000.5000.200.1 |
os10bgp4V2Notifications OBJECT IDENTIFIER .1.3.6.1.4.1.674.11000.5000.200.1.0 |
os10bgp4V2Objects OBJECT IDENTIFIER .1.3.6.1.4.1.674.11000.5000.200.1.1 |
os10bgp4V2DiscontinuityTableTable 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. SEQUENCE OF Os10Bgp4V2DiscontinuityEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.1 |
os10bgp4V2DiscontinuityEntryEntry repsenting information about a discontinuity event for a given BGP instance. Os10Bgp4V2DiscontinuityEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.1.1 |
os10bgp4V2DiscontinuityTimeThe value of sysUpTime at the most recent occasion at which this BGP management instance has suffered a discontinuity.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.674.11000.5000.200.1.1.1.1.1 |
os10bgp4V2PeerTableBGP peer table. This table contains, one entry per BGP peer, information about the connections with BGP peers. SEQUENCE OF Os10Bgp4V2PeerEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.2 |
os10bgp4V2PeerEntryEntry containing information about the connection with a remote BGP peer. Os10Bgp4V2PeerEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.2.1 |
os10bgp4V2PeerInstanceThe 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.674.11000.5000.200.1.1.2.1.1 |
os10bgp4V2PeerLocalAddrTypeThe address family of the local end of the peering session.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.674.11000.5000.200.1.1.2.1.2 |
os10bgp4V2PeerLocalAddrThe 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.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.674.11000.5000.200.1.1.2.1.3 |
os10bgp4V2PeerRemoteAddrTypeThe 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. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.674.11000.5000.200.1.1.2.1.4 |
os10bgp4V2PeerRemoteAddrThe remote IP address of this entry's BGP peer. InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.674.11000.5000.200.1.1.2.1.5 |
os10bgp4V2PeerLocalPortThe local port for the TCP connection between the BGP peers.ro InetPortNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.674.11000.5000.200.1.1.2.1.6 |
os10bgp4V2PeerLocalAsSome 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.674.11000.5000.200.1.1.2.1.7 |
os10bgp4V2PeerLocalIdentifierThe BGP Identifier of the local system for this peering session. It is REQUIRED that all os10bgp4V2PeerLocalIdentifier values for the same os10bgp4V2PeerInstance be identical.ro Os10Bgp4V2IdentifierTC .1.3.6.1.4.1.674.11000.5000.200.1.1.2.1.8 |
os10bgp4V2PeerRemotePortThe 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.ro InetPortNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.674.11000.5000.200.1.1.2.1.9 |
os10bgp4V2PeerRemoteAsThe remote autonomous system number received in the BGP OPEN message.ro InetAutonomousSystemNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.674.11000.5000.200.1.1.2.1.10 |
os10bgp4V2PeerRemoteIdentifierThe 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.ro Os10Bgp4V2IdentifierTC .1.3.6.1.4.1.674.11000.5000.200.1.1.2.1.11 |
os10bgp4V2PeerAdminStatusWhether 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.ro Enumeration .1.3.6.1.4.1.674.11000.5000.200.1.1.2.1.12 |
os10bgp4V2PeerStateThe BGP peer connection state.ro Enumeration .1.3.6.1.4.1.674.11000.5000.200.1.1.2.1.13 |
os10bgp4V2PeerDescriptionA 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.674.11000.5000.200.1.1.2.1.14 |
os10bgp4V2PeerErrorsTableOn a per-peer basis, this table reflects the last protocol-defined error encountered and reported on the peer session. SEQUENCE OF Os10Bgp4V2PeerErrorsEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.3 |
os10bgp4V2PeerErrorsEntryEach entry contains information about errors sent and received for a particular BGP peer. Os10Bgp4V2PeerErrorsEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.3.1 |
os10bgp4V2PeerLastErrorCodeReceivedThe 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.674.11000.5000.200.1.1.3.1.1 |
os10bgp4V2PeerLastErrorSubCodeReceivedThe 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.674.11000.5000.200.1.1.3.1.2 |
os10bgp4V2PeerLastErrorReceivedTimeThe timestamp that the last NOTIFICATION was received from this peer.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.674.11000.5000.200.1.1.3.1.3 |
os10bgp4V2PeerLastErrorReceivedTextThis object contains an implementation specific explanation of the error that was reported.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.674.11000.5000.200.1.1.3.1.4 |
os10bgp4V2PeerLastErrorReceivedDataThe 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.674.11000.5000.200.1.1.3.1.5 |
os10bgp4V2PeerLastErrorCodeSentThe 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.674.11000.5000.200.1.1.3.1.6 |
os10bgp4V2PeerLastErrorSubCodeSentThe 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.674.11000.5000.200.1.1.3.1.7 |
os10bgp4V2PeerLastErrorSentTimeThe timestamp that the last NOTIFICATION was sent to this peer.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.674.11000.5000.200.1.1.3.1.8 |
os10bgp4V2PeerLastErrorSentTextThis object contains an implementation specific explanation of the error that is being reported.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.674.11000.5000.200.1.1.3.1.9 |
os10bgp4V2PeerLastErrorSentDataThe 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.674.11000.5000.200.1.1.3.1.10 |
os10bgp4V2PeerEventTimesTableA table reporting the per-peering session amount of time elapsed and update events since the peering session advanced into the established state. SEQUENCE OF Os10Bgp4V2PeerEventTimesEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.4 |
os10bgp4V2PeerEventTimesEntryEach row contains a set of statistics about time spent and events encountered in the peer session established state. Os10Bgp4V2PeerEventTimesEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.4.1 |
os10bgp4V2PeerFsmEstablishedTimeThis 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.674.11000.5000.200.1.1.4.1.1 |
os10bgp4V2PeerInUpdatesElapsedTimeElapsed 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.674.11000.5000.200.1.1.4.1.2 |
os10bgp4V2PeerConfiguredTimersTablePer peer management data on BGP session timers. SEQUENCE OF Os10Bgp4V2PeerConfiguredTimersEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.5 |
os10bgp4V2PeerConfiguredTimersEntryEach entry corresponds to the current state of BGP timers on a given peering session. Os10Bgp4V2PeerConfiguredTimersEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.5.1 |
os10bgp4V2PeerConnectRetryIntervalTime interval (in seconds) for the ConnectRetry timer. The suggested value for this timer is 120 seconds.ro Unsigned32 .1.3.6.1.4.1.674.11000.5000.200.1.1.5.1.1 |
os10bgp4V2PeerHoldTimeConfiguredTime 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).ro Unsigned32 ( 0 | 3..65535 ) UNITS "seconds" .1.3.6.1.4.1.674.11000.5000.200.1.1.5.1.2 |
os10bgp4V2PeerKeepAliveConfiguredTime 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.ro Unsigned32 ( 0 | 1..21845 ) UNITS "seconds" .1.3.6.1.4.1.674.11000.5000.200.1.1.5.1.3 |
os10bgp4V2PeerMinASOrigIntervalTime interval (in seconds) for the MinASOriginationInterval timer. The suggested value for this timer is 15 seconds.ro Unsigned32 .1.3.6.1.4.1.674.11000.5000.200.1.1.5.1.4 |
os10bgp4V2PeerMinRouteAdverIntervalTime 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.ro Unsigned32 .1.3.6.1.4.1.674.11000.5000.200.1.1.5.1.5 |
os10bgp4V2PeerNegotiatedTimersTableConfigured 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. SEQUENCE OF Os10Bgp4V2PeerNegotiatedTimersEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.6 |
os10bgp4V2PeerNegotiatedTimersEntryEach entry reflects a value of the currently operational, negotiated timer as reflected in the Os10Bgp4V2PeerNegotiatedTimersEntry. Os10Bgp4V2PeerNegotiatedTimersEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.6.1 |
os10bgp4V2PeerHoldTimeThe 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).ro Unsigned32 ( 0 | 3..65535 ) UNITS "seconds" .1.3.6.1.4.1.674.11000.5000.200.1.1.6.1.1 |
os10bgp4V2PeerKeepAliveTime 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).ro Unsigned32 ( 0 | 1..21845 ) UNITS "seconds" .1.3.6.1.4.1.674.11000.5000.200.1.1.6.1.2 |
os10bgp4V2PeerCountersTableThe counters associated with a BGP Peer. SEQUENCE OF Os10Bgp4V2PeerCountersEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.7 |
os10bgp4V2PeerCountersEntryEach entry contains counters of message transmissions and FSM transitions for a given BGP Peering session. Os10Bgp4V2PeerCountersEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.7.1 |
os10bgp4V2PeerInUpdatesThe number of BGP UPDATE messages received on this connection.ro Counter32 .1.3.6.1.4.1.674.11000.5000.200.1.1.7.1.1 |
os10bgp4V2PeerOutUpdatesThe number of BGP UPDATE messages transmitted on this connection.ro Counter32 .1.3.6.1.4.1.674.11000.5000.200.1.1.7.1.2 |
os10bgp4V2PeerInTotalMessagesThe total number of messages received from the remote peer on this connection.ro Counter32 .1.3.6.1.4.1.674.11000.5000.200.1.1.7.1.3 |
os10bgp4V2PeerOutTotalMessagesThe total number of messages transmitted to the remote peer on this connection.ro Counter32 .1.3.6.1.4.1.674.11000.5000.200.1.1.7.1.4 |
os10bgp4V2PeerFsmEstablishedTransitionsThe total number of times the BGP FSM transitioned into the established state for this peer.ro Counter32 .1.3.6.1.4.1.674.11000.5000.200.1.1.7.1.5 |
os10bgp4V2PrefixGaugesTableAdditional per-peer, per AFI-SAFI counters for prefixes SEQUENCE OF Os10Bgp4V2PrefixGaugesEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.8 |
os10bgp4V2PrefixGaugesEntryEntry containing information about a bgp-peers prefix counters. Os10Bgp4V2PrefixGaugesEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.8.1 |
os10bgp4V2PrefixGaugesAfiThe AFI index of the per-peer, per prefix counters Os10Bgp4V2AddressFamilyIdentifierTC .1.3.6.1.4.1.674.11000.5000.200.1.1.8.1.1 |
os10bgp4V2PrefixGaugesSafiThe SAFI index of the per-peer, per prefix counters Os10Bgp4V2SubsequentAddressFamilyIdentifierTC .1.3.6.1.4.1.674.11000.5000.200.1.1.8.1.2 |
os10bgp4V2PrefixInPrefixesThe 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.ro Gauge32 .1.3.6.1.4.1.674.11000.5000.200.1.1.8.1.3 |
os10bgp4V2PrefixInPrefixesAcceptedThe number of prefixes for a peer that are installed in the Adj-Ribs-In and are eligible to become active in the Loc-Rib.ro Gauge32 .1.3.6.1.4.1.674.11000.5000.200.1.1.8.1.4 |
os10bgp4V2PrefixOutPrefixesThe number of prefixes for a peer that are installed in that peer's Adj-Ribs-Out.ro Gauge32 .1.3.6.1.4.1.674.11000.5000.200.1.1.8.1.5 |
os10bgp4V2NlriTableThe 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. SEQUENCE OF Os10Bgp4V2NlriEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.9 |
os10bgp4V2NlriEntryInformation about a path to a network. Os10Bgp4V2NlriEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1 |
os10bgp4V2NlriIndexThis 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.674.11000.5000.200.1.1.9.1.1 |
os10bgp4V2NlriAfiThe address family of the prefix for this NLRI. Note that the AFI is not necessarily equivalent to the an InetAddressType. Os10Bgp4V2AddressFamilyIdentifierTC .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1.2 |
os10bgp4V2NlriSafiThe subsequent address family of the prefix for this NLRI Os10Bgp4V2SubsequentAddressFamilyIdentifierTC .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1.3 |
os10bgp4V2NlriPrefixTypeThe 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). InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1.4 |
os10bgp4V2NlriPrefixAn 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) InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1.5 |
os10bgp4V2NlriPrefixLenLength in bits of the address prefix in the Network Layer Reachability Information field. InetAddressPrefixLength (INET-ADDRESS-MIB) .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1.6 |
os10bgp4V2NlriBestAn 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.674.11000.5000.200.1.1.9.1.7 |
os10bgp4V2NlriCalcLocalPrefThe 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.674.11000.5000.200.1.1.9.1.8 |
os10bgp4V2NlriOriginThe ultimate origin of the path information.ro Enumeration .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1.9 |
os10bgp4V2NlriNextHopAddrTypeThe 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.674.11000.5000.200.1.1.9.1.10 |
os10bgp4V2NlriNextHopAddrThe 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.ro InetAddress .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1.11 |
os10bgp4V2NlriLinkLocalNextHopAddrTypeThe 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.674.11000.5000.200.1.1.9.1.12 |
os10bgp4V2NlriLinkLocalNextHopAddrThis 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.674.11000.5000.200.1.1.9.1.13 |
os10bgp4V2NlriLocalPrefPresentThis value is true when the LOCAL_PREF value was sent in the UPDATE message.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1.14 |
os10bgp4V2NlriLocalPrefThe originating BGP4 speakers degree of preference for an advertised route.ro Unsigned32 .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1.15 |
os10bgp4V2NlriMedPresentThis value is true when the MED value was sent in the UPDATE message.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1.16 |
os10bgp4V2NlriMedThis 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.674.11000.5000.200.1.1.9.1.17 |
os10bgp4V2NlriAtomicAggregateThis 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.674.11000.5000.200.1.1.9.1.18 |
os10bgp4V2NlriAggregatorPresentThis value is true when the AGGREGATOR path attribute was sent in the UPDATE message.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1.19 |
os10bgp4V2NlriAggregatorASThe AS number of the last BGP4 speaker that performed route aggregation. When os10bgp4V2NlriAggregatorPresent is false, the value of this object should be zero (0).ro InetAutonomousSystemNumber (INET-ADDRESS-MIB) .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1.20 |
os10bgp4V2NlriAggregatorAddrThe 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.0ro Os10Bgp4V2IdentifierTC .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1.21 |
os10bgp4V2NlriAsPathCalcLengthThis 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.674.11000.5000.200.1.1.9.1.22 |
os10bgp4V2NlriAsPathStringThis 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.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1.23 |
os10bgp4V2NlriAsPathIn 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.ro OCTET STRING .1.3.6.1.4.1.674.11000.5000.200.1.1.9.1.24 |
os10bgp4V2NlriPathAttrUnknownPath 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.674.11000.5000.200.1.1.9.1.25 |
os10bgp4V2AdjRibsOutTableThis 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. SEQUENCE OF Os10Bgp4V2AdjRibsOutEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.10 |
os10bgp4V2AdjRibsOutEntryList of BGP routes that have been placed into a peer's Adj-Ribs-Out. Os10Bgp4V2AdjRibsOutEntry .1.3.6.1.4.1.674.11000.5000.200.1.1.10.1 |
os10bgp4V2AdjRibsOutIndexCertain 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. Unsigned32 .1.3.6.1.4.1.674.11000.5000.200.1.1.10.1.1 |
os10bgp4V2AdjRibsOutRouteThis 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.ro RowPointer (SNMPv2-TC) .1.3.6.1.4.1.674.11000.5000.200.1.1.10.1.2 |
os10bgp4V2Conformance OBJECT IDENTIFIER .1.3.6.1.4.1.674.11000.5000.200.1.2 |