Forum Discussion
anshubathla
Altostratus
AltostratusOne ARM mode with pool members in different VLAN
Hi Team, I have one Virtual Server and 2 Pool members configured in the same VLAN (One arm mode) . I am using SNAT Pool of two IP's from the same subnet . This setup was working perfectly f...
Hi,
- Did you tried to telnet non-working pool member from F5 self IP as source ? If not, you can try it once using -
telnet -b Self-IP Dest-IP Port- If you have specific Route Domains, first change the route domain then telnet or try to reach pool member from there.
To change the route domain use command rdsh
- If telnet is failing in any of the above cases, you can check by adding route for the pool member host on F5 towards the gateway/IP where its L3 is configured.
Mayur_Sutare
MVP
MVPHi,
- Did you tried to telnet non-working pool member from F5 self IP as source ? If not, you can try it once using -
telnet -b Self-IP Dest-IP Port- If you have specific Route Domains, first change the route domain then telnet or try to reach pool member from there.
To change the route domain use command rdsh
- If telnet is failing in any of the above cases, you can check by adding route for the pool member host on F5 towards the gateway/IP where its L3 is configured.
anshubathlaAltostratus
AltostratusSorry , we have tried tried telnet directly without taking the Self IP and it was working
But when we tried with the command provided by you it is shows connection refused .
Regarding the route addition , could you please explain a bit more as we have self IP's configured for both working and non working pool member , so F5 should have route to reach both vlans then why their is a requirement of adding aa route ?
Even I have tried adding route for 192.168.20.201 next hop 192.168.20.1 ( gateway configured on switch) but still telnet is not working. Its looks like a communication issue between the two vlans. Could you please advise further.