For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Aquib_156189's avatar
Aquib_156189
Icon for Nimbostratus rankNimbostratus
Jun 06, 2014

e-Load request is getting processed through VIP

Can anyone help me, We are facing the issues, When e-Load request is getting processed through NLB VIP as per e-Load log the IP’s are getting swap or not matching and session is getting invalidated

 

7 Replies

  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Jun 06, 2014

    Are you using any type of persistence to ensure clients are always being directed at the same pool member?

     

    http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm_configuration_guide_10_0_0/ltm_persist_profiles.html

     

    • Aquib_156189's avatar
      Aquib_156189
      Icon for Nimbostratus rankNimbostratus
      Jun 10, 2014
      ltm virtual e-Load_Virtual { description "e Load Virtual IP" destination 20.74.89.113:8980 ip-protocol tcp mask 255.255.255.255 pool e-Load_Pool profiles { fastL4 { } } source 0.0.0.0/0 source-address-translation { type automap } vs-index 56 ltm pool e-Load_Pool { description e-Load_Pool load-balancing-mode least-connections-member members { e-Load_Server1:8980 { address 20.74.73.88 session monitor-enabled state up } e-Load_Server2:8980 { address 20.74.73.89 session monitor-enabled state up } } monitor Monitor_8980
  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Jun 10, 2014

    I don't see any persistence enabled on your virtual server. How are you persisting by source IP address?

     

    • Aquib_156189's avatar
      Aquib_156189
      Icon for Nimbostratus rankNimbostratus
      Jun 11, 2014
      Yes, it is persisting by source IP address ltm virtual e-Load_Virtual { description "e Load Virtual IP" destination 20.74.89.113:8980 ip-protocol tcp mask 255.255.255.255 persist { source_addr { default yes } } pool e-Load_Pool profiles { fastL4 { } } source 0.0.0.0/0 source-address-translation { type automap } vs-index 56 ltm pool e-Load_Pool { description e-Load_Pool load-balancing-mode least-connections-member members { e-Load_Server1:8980 { address 20.74.73.88 session monitor-enabled state up } e-Load_Server2:8980 { address 20.74.73.89 session monitor-enabled state up } } monitor Monitor_8980
  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Jun 11, 2014

    You mentioned IPs getting swapped and sessions getting invalidated. Can you elaborate a bit more on this behavior? Where are you seeing this behavior?