dns npath problems

There are a lot of unknowns in your question. I'm assuming you are referring to npath routing: ">https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-implementations-11-5-0/4.html?" target="_blank">">https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-implementations-11-5-0/4.html? THe most common mistake I have seen is that people do not have their loopback addresses to include the same destination address as the VS. Based on you saying you need to 're-enable your VS server', it sounds like your problem.

Given that your pool members are on the same network, I would be checking your arp table (tmsh show net arp) and running digs against your pool members in question.

I'm reposting due to the devcentral horible WYSIWYG:

There are a lot of unknowns in your question. I'm assuming you are referring to npath routing: https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-implementations-11-5-0/4.html? The most common mistake I have seen is that people do not have their loopback addresses to include the same destination address as the VS. Based on you saying you need to 're-enable your VS server', it sounds like your problem.

Given that your pool members are on the same network, I would be checking your arp table (tmsh show net arp) and running digs against your pool members in question.

Hi Riley,

thx for the info, but.. :)

Well I fixed the issue. The problem was with arp announce. I have cisco asa in front of F5 lb, and the servers we're announcing arp faster to the asa than f5, so the traffic bypassed f5 and went directly to one node.