The local address configured for the peering session, or a zero length address if not specified. For outbound connections, if a local address is specified then DC-BGP will bind to the specified local address. Otherwise the local address is selected by the TCP/IP stack for the NM instance configured in the bgpPeerLocalNm field. For incoming connections, if a local address is specified then the incoming connection must match the specified local address. Otherwise the local address used by the incoming connection is ignored. This should typically be set to the local address that is recognized by the peer, though for directly connected peers (such as EBGP peers) it can be left unspecified. The bgpPeerSelectedLocalAddr field shows the local address actually in use. 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.