Status in source: current.
Names: eltexBgpPeerGroupRemoteAs
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"eltexBgpPeerGroupRemoteAs",
"OBJECT-TYPE",
"SYNTAX",
"EltexBgpAutonomousSystemNumber",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The remote autonomous system number. For individual peers, this can be configured using eltexBgpPeerRemoteAs. 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 eltexBgpPeerStatusTable row for the peer).\"",
"::=",
"{",
"eltexBgpPeerGroupEntry",
"3",
"}"
],
"syntax_tree": [
[
"row",
"EltexBgpAutonomousSystemNumber"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The remote autonomous system number. For individual peers, this can be configured using eltexBgpPeerRemoteAs. 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 eltexBgpPeerStatusTable row for the peer)."
],
null,
null,
null,
null
]
}