Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"bgpPeerLocalAddr",
"OBJECT-TYPE",
"SYNTAX",
"InetAddress",
"(",
"SIZE",
"(",
"0",
".",
".",
"32",
")",
")",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The address of the local end of the peering session. This is used as an index to the row. If a zero length address is used, DC-BGP will not bind a specific address but use whatever is available through the NM instance configured in the bgpPeerLocalNm field. In this case the bgpPeerSelectedLocalAddr field shows which local address is actually used. If a specific local address is configured, then outbound socket connections will be bound to this address. If a non-zero bgpPeerLocalPort is specified, then outbound socket connections will be bound to this port. Note that you can have 2 peer entries to the same remote <address, port> if they come from a different local <address, port>. To configure this each local <address, port> must be specified explicitly and not be zero length. You will not be allowed to do this if you are listening on all addresses as it will be impossible to tell which peer an incoming connection is for. You must explicitly listen on each local address in this case. It is equivalent to the bgpM2PeerTable entry bgpM2PeerLocalAddr.\"",
"::=",
"{",
"bgpPeerEntry",
"8",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"InetAddress",
[
"octetStringSubType",
[
[
0,
32
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The address of the local end of the peering session. This is used as an index to the row. If a zero length address is used, DC-BGP will not bind a specific address but use whatever is available through the NM instance configured in the bgpPeerLocalNm field. In this case the bgpPeerSelectedLocalAddr field shows which local address is actually used. If a specific local address is configured, then outbound socket connections will be bound to this address. If a non-zero bgpPeerLocalPort is specified, then outbound socket connections will be bound to this port. Note that you can have 2 peer entries to the same remote <address, port> if they come from a different local <address, port>. To configure this each local <address, port> must be specified explicitly and not be zero length. You will not be allowed to do this if you are listening on all addresses as it will be impossible to tell which peer an incoming connection is for. You must explicitly listen on each local address in this case. It is equivalent to the bgpM2PeerTable entry bgpM2PeerLocalAddr."
],
null,
null,
null,
null
]
}