Forum Discussion

anshubathla's avatar
anshubathla
Icon for Altostratus rankAltostratus
Jan 18, 2021

One 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...
application delivery
BIG-IP
LTM
  • Mayur_Sutare's avatar
    Mayur_Sutare
    Jan 19, 2021

    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's avatar
Mayur_Sutare
Icon for MVP rankMVP
Jan 19, 2021

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.
  • anshubathla's avatar
    anshubathla
    Icon for Altostratus rankAltostratus
    Jan 19, 2021

    We are able to telnet the working and non working pool members from F5.

    do you think we need to change any other thing when we are using One ARM mode with VS and pool member in different VLAN while using SNAT.

  • anshubathla's avatar
    anshubathla
    Icon for Altostratus rankAltostratus
    Jan 19, 2021

      Sorry , 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.