Forum Discussion

Sanal_Babu's avatar
Sanal_Babu
Icon for Nimbostratus rankNimbostratus
Mar 20, 2018

LTM Issue connecting from node to its own vip.

I have a problem when the pool member initiate a connection towards its own vip. Lets say , i have a vip and 2 pool members where 2 applications running on each node.

 

•Application1: App1 Runs on Node1:8443 and Node2:8443

 

•Application2: App2 Runs on Node1:8443 and Node2:8443

 

Here is the traffic flow. User-> LB VIP:8443/App1 -> Node1:8443/App1

 

Node1 :App1 -> LB VIP:8443/App2 -> Node1:8443/App2 (THIS COMMUNICATION DOES NOT WORK - sometimes)

 

VIP : 192.168.10.10 Self IP : 192.168.10.25 SNAT : Automap Configured. Server gateway : 192.168.10.30

 

What could be the issue...

 

6 Replies

  • This sounds like it may be a persistence issue. Do you have a persistence profile applied to your VIP?

     

  • Can you manually connect from node1 to VIP2?

     

    If not or only works sometimes do you get an error/alert in the LTM logs?

     

  • Normally if you are hosting multiple applications on same servers they should listen on different ports because already port 8443 is used for the first application.

     

    Try to change the different port on node end for app2.

     

    Example:

     

    •Application1: App1 Runs on Node1:8443 and Node2:8443

     

    •Application2: App2 Runs on Node1:8444 and Node2:8444

     

    In our DMZ we have multiple applications on same server but listening on different and all are working fine without any issues

     

    • Surgeon's avatar
      Surgeon
      Ret. Employee

      yes, sounds like port conflict. change the port on app2 to other then 8443

       

  • Normally if you are hosting multiple applications on same servers they should listen on different ports because already port 8443 is used for the first application.

     

    Try to change the different port on node end for app2.

     

    Example:

     

    •Application1: App1 Runs on Node1:8443 and Node2:8443

     

    •Application2: App2 Runs on Node1:8444 and Node2:8444

     

    In our DMZ we have multiple applications on same server but listening on different and all are working fine without any issues

     

    • Surgeon's avatar
      Surgeon
      Ret. Employee

      yes, sounds like port conflict. change the port on app2 to other then 8443