Forum Discussion
Cirrushealthcheck problem with one armed design and multiple vlan
Hi,
I still was looking around the forum, but didn't found a solution for my problem.
Here is a little example picture:
We want to replace our old slb by a f5 ltm. It is a one armed design with multiple VLANs via one trunk. The core switch is the default gateway for all the network stuff.
What I still did do:
* did create the trunk
* did create the tagged VLANs
* did create a floating and a non floating self IP, mapped to the VLANs
* no routes
* did create a Node (S1), and a pool (Pool1) with monitor
* did create a VS (DNS1) mapped with VLAN1 and SNAT auto map
My problem is that the healthcheck (green) should use the self ip and trunk interface. But it use the management ip and interface.
Can someone explain my mistake or what is wrong?
thanks!
4 Replies
amolariCirrostratus
you have no route at the TMM level, but have one at the management. It will use this one, as the selfIPs are not in the same subnet as the pool member. You should define TMM routes (Network tab)
TortiBut there, I can only create routes depending on destination.
I want that the healthcheck use an IP depending on the IP of the VS - so the source.
For a VS at VLAN1 (10.10.1.x) it schould use a self IP mapped with that VLAN (self1).
For a VS at VLAN2 (10.10.2.x) it schould use a self IP mapped with that VLAN (self2).
Is it possible?- amolarithe monitor has no relationship to the VS. It's bound to the pool/pool member/node and will take the source IP / interface depending on the route to reach the target
arpydaysNimbostratus
The Healthcheck Source IP will be based on the dest route to the pool and the egress vlan/selfip to get there.
route Pool1 via 10.10.1.254 (F5 will use 10.10.1.1 selfip as source)
route Pool2 via 10.10.2.254 (F5 will use 10.10.2.1 selfip as source)
cheers
