Status in source: current.
Names: bgpPeerAfiSafiReflectorClient
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"bgpPeerAfiSafiReflectorClient",
"OBJECT-TYPE",
"SYNTAX",
"BgpPeerReflectorClientType",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"Gives finer control of the configuration provided by bgpPeerReflectorClient. This value indicates whether the given peer is a reflector client of this router for this AFI/SAFI, or not. A value of nonClient(0) indicates that this peer is not a reflector client for this AFI/SAFI. A value of client(1) indicates that this peer is a reflector client for this AFI/SAFI that is not fully meshed with other reflector clients. A value of meshedClient(2) indicates that the peer is a reflector client for this AFI/SAFI and is fully meshed with all other reflector clients. The peer's reflector-client setting for this AFI/SAFI is chosen as follows. - If the peer is not a member of a peer group OR the peer group is not used. o If bgpPeerReflectorClient is NOT non-client then use that o Otherwise use bgpPeerAfiSafiReflectorClient. - If the peer is a member of a peer group AND the peer group is used. o If bgpPeergrReflectorClient is NOT non-client then use that. o Otherwise use bgpPeergrAfiSafiReflectorClient. This field can be changed at any time. However, if the field is changed while the peer is admin_status UP, the change will only take effect after the peer has been cycled admin_status DOWN and then UP, thus forcing the peer session to be restarted. In this case, until the peer is set admin_status DOWN, the peer will be marked as out of date (as reported by the config_state field in the AMB_BGP_PEER_STATUS row for the peer). The peer may be configured to ignore this field and instead obtain the value from a peer-group as explained in the table description.\"",
"DEFVAL",
"{",
"nonClient",
"}",
"::=",
"{",
"bgpPeerAfiSafiEntry",
"34",
"}"
],
"syntax_tree": [
[
"row",
"BgpPeerReflectorClientType"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Gives finer control of the configuration provided by bgpPeerReflectorClient. This value indicates whether the given peer is a reflector client of this router for this AFI/SAFI, or not. A value of nonClient(0) indicates that this peer is not a reflector client for this AFI/SAFI. A value of client(1) indicates that this peer is a reflector client for this AFI/SAFI that is not fully meshed with other reflector clients. A value of meshedClient(2) indicates that the peer is a reflector client for this AFI/SAFI and is fully meshed with all other reflector clients. The peer's reflector-client setting for this AFI/SAFI is chosen as follows. - If the peer is not a member of a peer group OR the peer group is not used. o If bgpPeerReflectorClient is NOT non-client then use that o Otherwise use bgpPeerAfiSafiReflectorClient. - If the peer is a member of a peer group AND the peer group is used. o If bgpPeergrReflectorClient is NOT non-client then use that. o Otherwise use bgpPeergrAfiSafiReflectorClient. This field can be changed at any time. However, if the field is changed while the peer is admin_status UP, the change will only take effect after the peer has been cycled admin_status DOWN and then UP, thus forcing the peer session to be restarted. In this case, until the peer is set admin_status DOWN, the peer will be marked as out of date (as reported by the config_state field in the AMB_BGP_PEER_STATUS row for the peer). The peer may be configured to ignore this field and instead obtain the value from a peer-group as explained in the table description."
],
null,
null,
null,
[
"DEFVAL",
"nonClient"
]
]
}