Gives finer control of the sender-side loop detection configuration provided by bgpPeerDisableSenderLoopDetect. By default, BGP performs sender side loop detection. That is, it will not advertise a route to a peer if the AS-Path of the route already contains the peer's AS number. A peer would typically discard such routes, so this is normally a useful optimization. However, the peer may be configured to accept such routes (see bgpPeerAfiSafiAllowLocalAs). In this case it is necessary to disable sender-side loop detection. When bgpPeerDisableSenderLoopDetect is 'true', BGP disables sender-side loop detection for those address families for which bgpPeerAfiSafiDisableSndLpDetect is 'true'. When bgpPeerDisableSenderLoopDetect is 'false', sender-side loop detection is not disabled for any address families. If the value of this object is changed while the peer session is active, BGP will check for any routes that need to be advertised or withdrawn as a result of the change. The peer may be configured to ignore this field and instead obtain the value from a peer-group as explained in the table description. Note that sender-side loop detection does not operate on peers in an update group.