Mar 27, 2026 - For details about updated CVE-2025-53521 (BIG-IP APM vulnerability), refer to K000156741.

Forum Discussion

Santhosh0991's avatar
Santhosh0991
Icon for Nimbostratus rankNimbostratus
Jun 14, 2021

After failover from A to B,the traffic is not flowing to B

Even after the failover from A to B is fine, the traffic doesn't flow through B, I have checked for both traffic groups where masquerade is enabled and other is not, same behaviour
application delivery
LTM
Santhosh0991's avatar
Santhosh0991
Icon for Nimbostratus rankNimbostratus
Jun 15, 2021

Hello Alex BCT, thanks for your suggestions, but all the scenarios are there configured , but still we faced the issue

  • AlexBCT's avatar
    AlexBCT
    Icon for Cumulonimbus rankCumulonimbus
    Jun 15, 2021

    Hmm, interesting! Though I very much doubt you'd agree with me... ;)

     

    What platform are you running on? Is it hardware or VM's? If you are running VM's on VMware, you can check the security settings; https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-891147DD-3E2E-45A1-9B50-7717C3443DD7.html -

    Doing a failover especially with MAC masquerading enabled can cause trouble because VMware stops sending traffic to the vSwitch port as it thinks that someone is either hijacking the MAC address or jumping between MAC addresses. - Temporary disabling these security features can help you troubleshoot this.

     

    If hardware devices, have a look at the physical interface configuration and the switch configuration to make sure those are fine.

     

    If no luck, if you do a tcpdump on the B device, do you see traffic coming in at all? Any ARP requests? And when you ping the B device from the gateway, does the gateway get the MAC address from the B device / traffic group?