Todo #2397
closed
Added by Warren Baker over 13 years ago.
Updated over 13 years ago.
Description
Currently when defining a new Gateway group, the default trigger level is set to 'Member Down'.
It ideally should be set to 'Packet Loss or High Latency' as 'Member Down' will only cause a failover when a member interface has lost its link. Which might not happen in most WAN environments.
Make sure to touch gwlb.inc return_gateways_array(); it defaults to memberdown for any dynamic gateway. That needs to be changed there.
- Status changed from New to Feedback
- % Done changed from 0 to 100
"member down" doesn't mean link down, or it never has historically up to and including recent 2.1, it means it's completely down (100% loss) in apinger. Packet loss or high latency is more suitable in some instances, but I'm not sure that should be the default. That will lead to flapping for some users, especially where under load they normally have high latency and some packet loss (which comprises probably a slight majority of all users). I think that's probably too touchy of a default.
- Status changed from Feedback to Rejected
Currently when defining a new Gateway group, the default trigger level is set to 'Member Down'.
It ideally should be set to 'Packet Loss or High Latency' as 'Member Down' will only cause a failover when a member interface has lost its link. Which might not happen in most WAN environments.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by