BGP4V2-MIB :: bgp4V2NlriAsPath

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › BGP4V2-MIB › bgp4V2NlriAsPath

bgp4V2NlriAsPath

Module: BGP4V2-MIB

OID (symbolic): BGP4V2-MIB::bgp4V2NlriAsPath

OID (numeric): 1.3.6.1.4.1.1991.3.5.1.1.9.1.24

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-only

Description: In 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: . 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.

What is bgp4V2NlriAsPath?

This is the raw canonicalized BGP AS_PATH attribute (2-4072 octets) as defined in RFC 4271/RFC 4893, preserving the exact path data for parsing. It complements the human-readable bgp4V2NlriAsPathString. Example: the binary encoding of AS_SEQUENCE containing 65001, 65002, 65003 is stored for exact reconstruction.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1991.3.5.1.1.9.1.24
snmpwalk -v2c -c public <target> BGP4V2-MIB::bgp4V2NlriAsPath

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1991.3.5.1.1.9.1.24.1
snmpget -v2c -c public <target> BGP4V2-MIB::bgp4V2NlriAsPath.1

Start monitoring BGP-speaking routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BGP4V2-MIB::bgp4V2NlriAsPath OID value, configure state conditions and alerts, and monitor any BGP-speaking routers from a single console.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.1991foundryFOUNDRY-SN-ROOT-MIB
1.3.6.1.4.1.1991.3experimentalFOUNDRY-SN-ROOT-MIB
1.3.6.1.4.1.1991.3.5bgp4V2RootFOUNDRY-SN-ROOT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1991.3.5.1bgp4V2BGP4V2-MIB
1.3.6.1.4.1.1991.3.5.1.1bgp4V2ObjectsBGP4V2-MIB
1.3.6.1.4.1.1991.3.5.1.1.9bgp4V2NlriTableBGP4V2-MIB
1.3.6.1.4.1.1991.3.5.1.1.9.1bgp4V2NlriEntryBGP4V2-MIB
1.3.6.1.4.1.1991.3.5.1.1.9.1.24bgp4V2NlriAsPathBGP4V2-MIB