Status in source: current.
Names: bgpPeerAfiSafiExportMap
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"bgpPeerAfiSafiExportMap",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"The index of the Route Map to use for route exports to the peer for this AFI/SAFI. The peer may be configured to ignore this field and instead obtain the value from a peer-group as explained in the table description. If the peer is a member of a peer group then using the peer group export policy allows DC-BGP to take advantage of the economies of using peer groups. Route export uses a single export route map chosen as follows. - If using the peer group value and it is non-zero, then use that (even if the route map does not exist). - If using the peer value and it is non-zero, then use that (even if the route map does not exist). - Otherwise use configuration from the Policy Configuration Table.\"",
"DEFVAL",
"{",
"0",
"}",
"::=",
"{",
"bgpPeerAfiSafiEntry",
"29",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The index of the Route Map to use for route exports to the peer for this AFI/SAFI. The peer may be configured to ignore this field and instead obtain the value from a peer-group as explained in the table description. If the peer is a member of a peer group then using the peer group export policy allows DC-BGP to take advantage of the economies of using peer groups. Route export uses a single export route map chosen as follows. - If using the peer group value and it is non-zero, then use that (even if the route map does not exist). - If using the peer value and it is non-zero, then use that (even if the route map does not exist). - Otherwise use configuration from the Policy Configuration Table."
],
null,
null,
null,
[
"DEFVAL",
0
]
]
}