Status in source: current.
Names: bgpPeerStatusConfigState
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"bgpPeerStatusConfigState",
"OBJECT-TYPE",
"SYNTAX",
"BgpPeerConfigStates",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"This field reports the state of the peer configuration. The peer configuration may be in one of the following states. - Up to date. That is, all configuration set by MIBs for this peer has been applied to the current peer session (if it exists). - Out of date, requiring the peer's admin status to be set to down before all the current MIB configuration for this peer can be applied. - Out of date, requiring the peer's row status to be set to inactive before all the current MIB configuration for this peer can be applied. A peer's configuration can become out of date for several reasons, including the following. - A field in the bgpPeerTable or bgpPeerAfiSafiTable has changed in the case where the peer uses the value from a Peer Table (not a Peer Group Table) but where the new value cannot be applied while the peer session is active. - A field in the bgpPeergrTable or bgpPeergrAfiSafiTable has changed in the case where the peer uses the value from a Peer Group Table (not a Peer Table) but where the new value cannot be applied while the peer session is active. connection has been created or activated. - The peer setting (bgpPeerConfigUsage) which determines whether the peer uses values from a Peer Table or from a Peer Group Table has been changed.\"",
"::=",
"{",
"bgpPeerStatusEntry",
"74",
"}"
],
"syntax_tree": [
[
"row",
"BgpPeerConfigStates"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This field reports the state of the peer configuration. The peer configuration may be in one of the following states. - Up to date. That is, all configuration set by MIBs for this peer has been applied to the current peer session (if it exists). - Out of date, requiring the peer's admin status to be set to down before all the current MIB configuration for this peer can be applied. - Out of date, requiring the peer's row status to be set to inactive before all the current MIB configuration for this peer can be applied. A peer's configuration can become out of date for several reasons, including the following. - A field in the bgpPeerTable or bgpPeerAfiSafiTable has changed in the case where the peer uses the value from a Peer Table (not a Peer Group Table) but where the new value cannot be applied while the peer session is active. - A field in the bgpPeergrTable or bgpPeergrAfiSafiTable has changed in the case where the peer uses the value from a Peer Group Table (not a Peer Table) but where the new value cannot be applied while the peer session is active. connection has been created or activated. - The peer setting (bgpPeerConfigUsage) which determines whether the peer uses values from a Peer Table or from a Peer Group Table has been changed."
],
null,
null,
null,
null
]
}