If an address is specified with a type matching bgpPeergrRemoteAddrType, and bgpPeergrAddrSourceIf is NOT specified, then BGP will use this address as the source address for the BGP session to this peer. This field is ignored for peers identified only by interface (bgpPeerLocalAddr and bgpPeerRemoteAddr are both zero). If the type does not match bgpPeergrRemoteAddrType, or bgpPeergrAddrSourceIf is specified, then the source address is chosen as described in bgpPeergrAddrSourceIf. If this address is used for peer sessions in this group then, for dynamic peers, the local address of the incoming TCP connection must match the address, or else the connection is rejected. This field is only taken into account for peer-group members if the conditions described in the bgpPeerTable description are met. This field can be changed at any time. However, if a peer is configured to use the peer group field and the field is changed while the peer is row_status ACTIVE, the change will only take effect after the peer has been cycled row_status NOT_IN_SERVICE and then ACTIVE, thus forcing the peer session to be recreated. In this case, until the peer is set row_status NOT_IN_SERVICE, 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).