Objects and OID | Access | Description |
---|---|---|
extremeBgp4V2NlriTable 1.3.6.1.4.1.1916.1.51.1.9 |
None |
This entity contains information of the bgp4PathAttr Table. |
extremeBgp4V2NlriEntry 1.3.6.1.4.1.1916.1.51.1.9.1 |
None |
An entry containing information about the bgp4PathAttr. |
extremeBgp4V2NlriIndex 1.3.6.1.4.1.1916.1.51.1.9.1.1 |
None |
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:
An example of this is RFC 3107 - Carrying MPLS labels in BGP. |
extremeBgp4V2NlriAfi 1.3.6.1.4.1.1916.1.51.1.9.1.2 |
None |
The address family of the prefix for this NLRI. Note that the AFI is not necessarily equivalent to the InetAddressType. |
extremeBgp4V2NlriSafi 1.3.6.1.4.1.1916.1.51.1.9.1.3 |
None |
The subsequent address family of the prefix for this NLRI. |
extremeBgp4V2NlriPrefixType 1.3.6.1.4.1.1916.1.51.1.9.1.4 |
None |
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 extremeBgp4V2NlriAfi field. Where an appropriate InetAddressType is not available, the value of the object must be unknown (0). |
extremeBgp4V2NlriPrefix 1.3.6.1.4.1.1916.1.51.1.9.1.5 |
None |
An IP address prefix in the Network Layer Reachability Information field. This object is an IP address containing the prefix with length specified by extremeBgp4V2NlriPrefixLen. Any bits beyond the length specified by extremeBgp4V2NlriPrefixLen are zeroed. |
extremeBgp4V2NlriPrefixLen 1.3.6.1.4.1.1916.1.51.1.9.1.6 |
None |
Length in bits of the address prefix in the Network Layer Reachability Information field. |
extremeBgp4V2NlriBest 1.3.6.1.4.1.1916.1.51.1.9.1.7 |
Read-Only |
An indication of whether or not this route was chosen as the best BGP4 route for this destination. |
extremeBgp4V2NlriCalcLocalPref 1.3.6.1.4.1.1916.1.51.1.9.1.8 |
Read-Only |
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). |
extremeBgp4V2NlriOrigin 1.3.6.1.4.1.1916.1.51.1.9.1.9 |
Read-Only |
The ultimate origin of the path information. |
extremeBgp4V2Nlrinext-hopAddrType 1.3.6.1.4.1.1916.1.51.1.9.1.10 |
Read-Only |
The address family of the address for the border router that should be used to access the destination network. |
extremeBgp4V2Nlrinext-hopAddr 1.3.6.1.4.1.1916.1.51.1.9.1.11 |
Read-Only |
The address of the border router that should be used to access the destination network. This address is the next-hop address received in the UPDATE packet associated with this prefix. Note:
For RFC2545 style double next-hops, this object will always contain the global scope next-hop. bgpPathAttrLinkLocalnext-hop will contain the link-local scope next-hop, if it is present. In the case a mechanism is developed to use only a link local next-hop, extremeBgp4V2Nlrinext-hopAddr will contain the link local next-hop. |
extremeBgp4V2NlriLinkLocalnext-hopAddrType 1.3.6.1.4.1.1916.1.51.1.9.1.12 |
Read-Only |
The address type for IPv6 link local addresses. This is present only when receiving RFC 2545 style double next-hops. This object is optionally present in BGP implementations that do not support IPv6. When no IPv6 link local next-hop is present, the value of this object should be unknown(0). |
extremeBgp4V2NlriLinkLocalnext-hopAddr 1.3.6.1.4.1.1916.1.51.1.9.1.13 |
Read-Only |
This value contains an IPv6 link local address and is present only when receiving RFC 2545 style double next-hops. This object is optionally present in BGP implementations that do not support IPv6 When no IPv6 link local next-hop is present, the length of this object should be zero. |
extremeBgp4V2NlriLocalPrefPresent 1.3.6.1.4.1.1916.1.51.1.9.1.14 |
Read-Only |
This value is true when the LOCAL_PREF value was sent in the UPDATE message. |
extremeBgp4V2NlriLocalPref 1.3.6.1.4.1.1916.1.51.1.9.1.15 |
Read-Only |
The originating BGP4 speaker‘s degree of preference for an advertised route. |
extremeBgp4V2NlriMedPresent 1.3.6.1.4.1.1916.1.51.1.9.1.16 |
Read-Only |
This value is true when the MED value was sent in the UPDATE message. |
extremeBgp4V2NlriMed 1.3.6.1.4.1.1916.1.51.1.9.1.17 |
Read-Only |
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. |
extremeBgp4V2NlriAtomicAggregate 1.3.6.1.4.1.1916.1.51.1.9.1.18 |
Read-Only |
This value is true when the ATOMIC_AGGREGATE Path Attribute is present and indicates that the NLRI MUST NOT be made more specific. |
extremeBgp4V2NlriAggregatorPresent 1.3.6.1.4.1.1916.1.51.1.9.1.19 |
Read-Only |
This value is true when the AGGREGATOR path attribute was sent in the UPDATE message. |
extremeBgp4V2NlriAggregatorAS 1.3.6.1.4.1.1916.1.51.1.9.1.20 |
Read-Only |
The AS number of the last BGP4 speaker that performed route aggregation. When extremeBgp4V2NlriAggregatorPresent is false, the value of this object should be zero (0). |
extremeBgp4V2NlriAggregatorAddr 1.3.6.1.4.1.1916.1.51.1.9.1.21 |
Read-Only |
The IP address of the last BGP4 speaker that performed route aggregation. When extremeBgp4V2NlriAggregatorPresent is false, the value of this object should be a default value. |
extremeBgp4V2NlriAsPathCalcLength 1.3.6.1.4.1.1916.1.51.1.9.1.22 |
Read-Only |
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. |
extremeBgp4V2NlriAsPathString 1.3.6.1.4.1.1916.1.51.1.9.1.23 |
Read-Only |
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:
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, '...'. extremeBgp4V2NlriAsPath may give access to the full AS Path. |
extremeBgp4V2NlriAsPath 1.3.6.1.4.1.1916.1.51.1.9.1.24 |
Read-Only |
In order to provide a canonicalized form of the BGP-4 AS_PATH along with the human-readable extremeBgp4V2NlriAsPathString, 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:
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:
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 conjunction 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. |
extremeBgp4V2NlriPathAttrUnknown 1.3.6.1.4.1.1916.1.51.1.9.1.25 |
Read-Only |
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. |