Forum Discussion
nitass
Mar 08, 2013Employee
When we test, we point our browser to the internal VIP FQDN which resolves to the correct (.5) IP address, but it takes ages for the page to load - and only that which loads (content missing and incorrectly placed in browser). Traces on F5 showing loads of resent requests etc. suggesting the traffic is not getting through as it should.where did you test from? was it internal or external vlan?
I don't have access to the F5, but I have been assured the virtual server and pool are pretty basic configurations - nothing too fancy.i think it might be easier if you can post configuration.
Also, with the i-VIP configured with a web VLAN address, we are unable to ping it (ICMP is enabled). We are also unable to ping the F5's interface IP address on the web VLAN. However, as there is a 2nd F5 set up in active/passive failover ... we can ping it's internal interface IP AND we can ping the floating IP. Each F5 can ping ALL of the other F5's IP too. However, both of our web servers cannot ping the two IPs mentioned above.you are not using packet filter (in bigip), are you?