Forum Discussion
NimbostratusOutbound Link Redundancy
NimbostratusThe ping is being treated as a connection so it is getting load balanced ONCE, which is expected behavior. When you stop the ping and try again(after simulating a failure) the ltm will NEVER load balance to a failed pool member.
So you ping test is probably not the best on for testing this. Put the action on service down in the pool to 'reject' and test again using a browser or whatever application your expect to traverse the load balancer for your users.
Martin_297498Hi Soda Cup, thank you for your words.
I was imagining that maybe the ping could not be a good test. But its odd since the users are expecting something transparent when a link outage happens.
Great tip about the action on service down, I'm quit new to the BIG IP world, so I was checking that there's also the reselect option instead of reject (The BIG-IP system manages established client connections by moving them to an alternate pool member without a connection teardown or setup.).
I'll test both and let you know.
Thanks.
- Soda_Cup_148395
Great- how transparent a failed link could be I think depends on the service. HTTP would be transparent, clients respond well to just trying again after getting a reset.
But I am not sure about something like a file transfer, I bet that would have to be retried as a new connection.
