Status in source: current.
Names: bgpPeergrAfiSafiAcceptRmtNxtHop
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"bgpPeergrAfiSafiAcceptRmtNxtHop",
"OBJECT-TYPE",
"SYNTAX",
"TruthValue",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"If set to false, then for any directly connected eBGP peers in the peer group, routes received from the peer with a next-hop that is not the peer's remote address and is not in a subnet shared with the remote device will be rejected, in accordance with RFC 4271 section 6.3. If set to true, this check is not performed, and such routes may be accepted. This is useful when communicating with an eBGP peer that preserves the next-hop of routes that it advertises. This field is used for dynamic and configured peers. For a description of how this field is used for the latter, see the description of bgpPeerTable.\"",
"DEFVAL",
"{",
"false",
"}",
"::=",
"{",
"bgpPeergrAfiSafiEntry",
"37",
"}"
],
"syntax_tree": [
[
"row",
"TruthValue"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"If set to false, then for any directly connected eBGP peers in the peer group, routes received from the peer with a next-hop that is not the peer's remote address and is not in a subnet shared with the remote device will be rejected, in accordance with RFC 4271 section 6.3. If set to true, this check is not performed, and such routes may be accepted. This is useful when communicating with an eBGP peer that preserves the next-hop of routes that it advertises. This field is used for dynamic and configured peers. For a description of how this field is used for the latter, see the description of bgpPeerTable."
],
null,
null,
null,
[
"DEFVAL",
"false"
]
]
}