Status in source: current.
Names: bgpAdjRibOutASPathStr
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"bgpAdjRibOutASPathStr",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"(",
"SIZE",
"(",
"0",
".",
".",
"128",
")",
")",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"This is a string containing the autonomous system path sent to this peer in the AS_PATH attribute for this Adj-RIB-Out route. If this path contains four-octet AS numbers and the peer does not support these a two-octet AS_PATH attribute and associated AS4_PATH attribute will be advertised to the peer instead as detailed in RFC 4893. However, this field will report the four-octet AS_PATH that would have been advertised to the peer if it had supported four-byte AS numbers. Two-octet AS numbers appear as four-octet numbers by adding two bytes of zero padding. The format of the string is simply the AS_PATH attribute. This can be converted to a more readable format by the management agent.\"",
"::=",
"{",
"bgpAdjRibOutEntry",
"10",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING",
[
"octetStringSubType",
[
[
0,
128
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This is a string containing the autonomous system path sent to this peer in the AS_PATH attribute for this Adj-RIB-Out route. If this path contains four-octet AS numbers and the peer does not support these a two-octet AS_PATH attribute and associated AS4_PATH attribute will be advertised to the peer instead as detailed in RFC 4893. However, this field will report the four-octet AS_PATH that would have been advertised to the peer if it had supported four-byte AS numbers. Two-octet AS numbers appear as four-octet numbers by adding two bytes of zero padding. The format of the string is simply the AS_PATH attribute. This can be converted to a more readable format by the management agent."
],
null,
null,
null,
null
]
}