Backend nodes goes unreachable from active F5

Question

Hi Team ,&nbsp;We are facing node reachability issue from Active f5 on evryweeknd (sunday ) but this happens only from the Active F5 and for few VIP/pools only ..We simply failover the f5 to standby and issue resolves and then failback to standby ..Has anyone faced such issue ? We have virtual appliance configured on the ESXi host .&nbsp;Before opening a TAC case , Can anyone confirm if you have faced similar problem ?&nbsp;I did not find anything on the audit logs which indicates some sceduled jobs running at tht time ..What else can be checked ?

emad · Answer

We had a similar issue. It was resolved after disabling Proxy ARP at gateway firewalls.&nbsp;

blue_whale · Answer

But this happens for only few pool emebers and only on the weekend at 11:00 am CET .

blue_whale · Answer

HI Team ,Cn anyone please suggest what we can check ?

boneyard · Answer

if it is that predictable you should run a packet capture on the big-ip and one of the servers. you will probably see the traffic stop and arps not being answered. that is what to focus on next, where does it get lost.

blue_whale · Answer

On F5 I am getting reset packet from backend server but I don't think its server who is sending the reset packet ... Because on standby f5 we do have issue .&nbsp;

Forum Discussion

Backend nodes goes unreachable from active F5

Recent Discussions

APM webtop customization header message

Installing a PKCS 12 File onto an F5 Device

Irule to allow specific IPs

Uploading SKCS 12 File to F5 Device

F5 not Identifying Parameter in Text/Plain Upload

Related Content

Active/Active load balancing examples with F5 BIG-IP and Azure load balancer

Code to create unreachable ELA license files from BIG-IQ

DESTINATION HOST UNREACHABLE

Azure Active Directory and BIG-IP APM Integration

DNS load balancing to backend servers using GTM/LTM.