Reference record for OID 1.3.6.1.3.5.1.1.9.1.24

Parent
1.3.6.1.3.5.1.1.9.1 (bgp4V2NlriEntry)
Node code
24
Node name
bgp4V2NlriAsPath
Numeric OID
1.3.6.1.3.5.1.1.9.1.24
URN notation
urn:oid:1.3.6.1.3.5.1.1.9.1.24
ASN.1 notation

{1 3 6 1 3 5 1 1 9 1 24}

  • {iso(1) identified-organization(3) dod(6) internet(1) experimental(3) dECNet-PHIV(5) bgp4V2(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) experimental(3) dECNet-PHIV(5) bgp4V2TC(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) experimental(3) bgp4V2Exp(5) bgp4V2(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) experimental(3) bgp4V2Exp(5) bgp4V2TC(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) experimental(3) frr(5) bgp4V2(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) experimental(3) frr(5) bgp4V2TC(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • {iso(1) org(3) dod(6) internet(1) experimental(3) dECNet-PHIV(5) bgp4V2(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • {iso(1) org(3) dod(6) internet(1) experimental(3) dECNet-PHIV(5) bgp4V2TC(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • {iso(1) org(3) dod(6) internet(1) experimental(3) bgp4V2Exp(5) bgp4V2(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • {iso(1) org(3) dod(6) internet(1) experimental(3) bgp4V2Exp(5) bgp4V2TC(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • {iso(1) org(3) dod(6) internet(1) experimental(3) frr(5) bgp4V2(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • {iso(1) org(3) dod(6) internet(1) experimental(3) frr(5) bgp4V2TC(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) experimental(3) dECNet-PHIV(5) bgp4V2(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) experimental(3) dECNet-PHIV(5) bgp4V2TC(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) experimental(3) bgp4V2Exp(5) bgp4V2(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) experimental(3) bgp4V2Exp(5) bgp4V2TC(1) bgp4V2Objects(1) bgp4V2NlriTable(9) bgp4V2NlriEntry(1) bgp4V2NlriAsPath(24)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/3/5/1/1/9/1/24
  • /ISO/Identified-Organization/6/1/3/5/1/1/9/1/24
  • /ISO/3/6/1/3/5/1/1/9/1/24
Named path variants
  • /iso/identified-organization/dod/internet/experimental/dECNet-PHIV/bgp4V2/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • /iso/identified-organization/dod/internet/experimental/dECNet-PHIV/bgp4V2TC/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • /iso/identified-organization/dod/internet/experimental/DECNet-PHIV/bgp4V2/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • /iso/identified-organization/dod/internet/experimental/DECNet-PHIV/bgp4V2TC/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • /iso/identified-organization/dod/internet/experimental/bgp4V2Exp/bgp4V2/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • /iso/identified-organization/dod/internet/experimental/bgp4V2Exp/bgp4V2TC/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • /iso/identified-organization/dod/internet/experimental/frr/bgp4V2/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • /iso/identified-organization/dod/internet/experimental/frr/bgp4V2TC/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • /iso/org/dod/internet/experimental/dECNet-PHIV/bgp4V2/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • /iso/org/dod/internet/experimental/dECNet-PHIV/bgp4V2TC/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • /iso/org/dod/internet/experimental/DECNet-PHIV/bgp4V2/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • /iso/org/dod/internet/experimental/DECNet-PHIV/bgp4V2TC/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • /iso/org/dod/internet/experimental/bgp4V2Exp/bgp4V2/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • /iso/org/dod/internet/experimental/bgp4V2Exp/bgp4V2TC/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • /iso/org/dod/internet/experimental/frr/bgp4V2/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • /iso/org/dod/internet/experimental/frr/bgp4V2TC/bgp4V2Objects/bgp4V2NlriTable/bgp4V2NlriEntry/bgp4V2NlriAsPath
  • Additional combinations skipped.

Descriptions

bgp4V2NlriAsPath — Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

The contents of the BGP-4 AS_PATH Path Attribute in canonical form.

bgp4V2NlriAsPath — Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

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

Source records

bgp4V2NlriAsPath

Status in source: current.

Names: bgp4V2NlriAsPath

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bgp4V2NlriAsPath",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "(",
    "SIZE",
    "(",
    "2",
    ".",
    ".",
    "4072",
    ")",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The contents of the BGP-4 AS_PATH Path Attribute in canonical form.\"",
    "REFERENCE",
    "\"RFC 4271, Section 4.3. RFC 5065, Section 5. RFC 4893.\"",
    "::=",
    "{",
    "bgp4V2NlriEntry",
    "24",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING",
      [
        "octetStringSubType",
        [
          [
            2,
            4072
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The contents of the BGP-4 AS_PATH Path Attribute in canonical form."
    ],
    [
      "REFERENCE",
      "RFC 4271, Section 4.3. RFC 5065, Section 5. RFC 4893."
    ],
    null,
    null,
    null
  ]
}
  • Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: BGP4V2-MIB

    Vendor MIB copy from the LibreNMS archive.

    Module: BGP4V2-MIB

    Published definition
    bgp4V2NlriAsPath OBJECT-TYPE
            SYNTAX     OCTET STRING (SIZE(2..4072))
            MAX-ACCESS read-only
            STATUS     current
            DESCRIPTION
                "The contents of the BGP-4 AS_PATH Path Attribute in
                 canonical form."
            REFERENCE
                "RFC 4271, Section 4.3.
                 RFC 5065, Section 5.
                 RFC 4893."
            ::= { bgp4V2NlriEntry 24 }
    Module imports
    {'SNMPv2-TC': ['TruthValue', 'RowPointer', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'experimental', 'Gauge32', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'BGP4V2-TC-MIB': ['Bgp4V2IdentifierTC', 'Bgp4V2AddressFamilyIdentifierTC', 'Bgp4V2SubsequentAddressFamilyIdentifierTC'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetPortNumber', 'InetAutonomousSystemNumber', 'InetAddressPrefixLength'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download BGP4V2-MIB

    Related source files and packages:


    Source location: BGP4V2-MIB::bgp4V2NlriAsPath.
    Source version and references

    Downloaded: 2026-10-24T02:14:17.468275+00:00.

bgp4V2NlriAsPath

Status in source: current.

Names: bgp4V2NlriAsPath

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "bgp4V2NlriAsPath",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "(",
    "SIZE",
    "(",
    "2",
    ".",
    ".",
    "4072",
    ")",
    ")",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "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: <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.\"",
    "REFERENCE",
    "\"RFC 4271, Section 4.3. RFC 5065, Section 5. RFC 4893.\"",
    "::=",
    "{",
    "bgp4V2NlriEntry",
    "24",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING",
      [
        "octetStringSubType",
        [
          [
            2,
            4072
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "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: <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."
    ],
    [
      "REFERENCE",
      "RFC 4271, Section 4.3. RFC 5065, Section 5. RFC 4893."
    ],
    null,
    null,
    null
  ]
}
  • Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive.

    Module: BGP4V2-MIB

    Published definition
    bgp4V2NlriAsPath OBJECT-TYPE
            SYNTAX     OCTET STRING (SIZE(2..4072))
            MAX-ACCESS read-only
            STATUS     current
            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:
                 <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."
             REFERENCE
                 "RFC 4271, Section 4.3.
                  RFC 5065, Section 5.
                  RFC 4893."
             ::= { bgp4V2NlriEntry 24 }
    Module imports
    {'SNMPv2-TC': ['TruthValue', 'RowPointer', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'mib-2', 'Counter32', 'Gauge32', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'BGP4V2-TC-MIB': ['Bgp4V2IdentifierTC', 'Bgp4V2AddressFamilyIdentifierTC', 'Bgp4V2SubsequentAddressFamilyIdentifierTC', 'frr'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetPortNumber', 'InetAutonomousSystemNumber', 'InetAddressPrefixLength'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download BGP4V2-MIB

    Related source files and packages:


    Source location: BGP4V2-MIB::bgp4V2NlriAsPath.
    Source version and references

    Downloaded: 2026-10-24T02:14:26.852151+00:00.

First Registration Authority (inferred from ancestor 1.3.6.1.3.5)

Saperia Jon

Current Registration Authority (inferred from ancestor 1.3.6.1.3)

Internet Assigned Numbers Authority

Siblings (24)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.3.5.1.1.9.1.1 bgp4V2NlriIndex00
1.3.6.1.3.5.1.1.9.1.2 bgp4V2NlriAfi00
1.3.6.1.3.5.1.1.9.1.3 bgp4V2NlriSafi00
1.3.6.1.3.5.1.1.9.1.4 bgp4V2NlriPrefixType00
1.3.6.1.3.5.1.1.9.1.5 bgp4V2NlriPrefix00
1.3.6.1.3.5.1.1.9.1.6 bgp4V2NlriPrefixLen00
1.3.6.1.3.5.1.1.9.1.7 bgp4V2NlriBest00
1.3.6.1.3.5.1.1.9.1.8 bgp4V2NlriCalcLocalPref00
1.3.6.1.3.5.1.1.9.1.9 bgp4V2NlriOrigin00
1.3.6.1.3.5.1.1.9.1.10 bgp4V2NlriNextHopAddrType00
1.3.6.1.3.5.1.1.9.1.11 bgp4V2NlriNextHopAddr00
1.3.6.1.3.5.1.1.9.1.12 bgp4V2NlriLinkLocalNextHopAddrType00
1.3.6.1.3.5.1.1.9.1.13 bgp4V2NlriLinkLocalNextHopAddr00
1.3.6.1.3.5.1.1.9.1.14 bgp4V2NlriLocalPrefPresent00
1.3.6.1.3.5.1.1.9.1.15 bgp4V2NlriLocalPref00
1.3.6.1.3.5.1.1.9.1.16 bgp4V2NlriMedPresent00
1.3.6.1.3.5.1.1.9.1.17 bgp4V2NlriMed00
1.3.6.1.3.5.1.1.9.1.18 bgp4V2NlriAtomicAggregate00
1.3.6.1.3.5.1.1.9.1.19 bgp4V2NlriAggregatorPresent00
1.3.6.1.3.5.1.1.9.1.20 bgp4V2NlriAggregatorAS00
1.3.6.1.3.5.1.1.9.1.21 bgp4V2NlriAggregatorAddr00
1.3.6.1.3.5.1.1.9.1.22 bgp4V2NlriAsPathCalcLength00
1.3.6.1.3.5.1.1.9.1.23 bgp4V2NlriAsPathString00
1.3.6.1.3.5.1.1.9.1.25 bgp4V2NlriPathAttrUnknown00