Forum Discussion
Help with configuring F5 load-balancing in between two ASA pairs (full routing)
I've tried simply removing the pool and removing the Self-IP, but it just finds the next Pool in line on the same subnet to complain that I will lose connectivity if I remove that Self IP.
I'll try to clarify my current problem:
A node has the IP of 10.104.4.10 on VLAN 104. VLAN 104 currently resides on the F5, with a Self IP of 10.104.4.5. The internal VLAN still exists on the F5 with a floating SelfIP of 10.99.0.1
By redesigning this so that only Routing should direct the load-balanced traffic to the DMZ network (10.104.4.0/24), it should direct any routes destined to 10.0.0.0/8 to the internal gateway of 10.99.0.10, yet the F5 is complaining that removing the SelfIP of 10.104.4.5 will make the node 10.104.4.10 unreachable.
Why is this? Am I perhaps missing some configuration to tell the F5 to use the routing table for referencing load-balance destinations?
Or am I looking at this all wrong?
I realize this problem is different than the original, but they are directly related.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com