Status in source: current.
Names: bgpPeergrDisableRouteRefresh
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"bgpPeergrDisableRouteRefresh",
"OBJECT-TYPE",
"SYNTAX",
"TruthValue",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"Indicates that DC-BGP should not advertise support for Route Refresh messages to peers in this peer group. When this flag is set, DC-BGP will not advertise support for Route Refresh messages to the peer. When this flag is not set, DC-BGP will advertise support for Route Refresh messages to the peer. This field can be changed at any time. However, if a peer is configured to use the peer group field and the field is changed while the peer is active, depending on the setting of the bgpPeergrResetPeerOnCfgChange field, the peer session may either be immediately reset, or the configuration change is not applied until the peer session is restarted.\"",
"DEFVAL",
"{",
"false",
"}",
"::=",
"{",
"bgpPeergrEntry",
"41",
"}"
],
"syntax_tree": [
[
"row",
"TruthValue"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Indicates that DC-BGP should not advertise support for Route Refresh messages to peers in this peer group. When this flag is set, DC-BGP will not advertise support for Route Refresh messages to the peer. When this flag is not set, DC-BGP will advertise support for Route Refresh messages to the peer. This field can be changed at any time. However, if a peer is configured to use the peer group field and the field is changed while the peer is active, depending on the setting of the bgpPeergrResetPeerOnCfgChange field, the peer session may either be immediately reset, or the configuration change is not applied until the peer session is restarted."
],
null,
null,
null,
[
"DEFVAL",
"false"
]
]
}