Forum Discussion
Devansu_22043
Nimbostratus
Sep 27, 2011Packets are dropping at F5 on new created Virtual Server
Hi,
We have just setup a new F5 BIG IP 1600 to our Development lab. Big IP 1600 connects to switch on one interface with VLAN and taggeded port. I created new Virtual Server using Template. Sef IP and Vitaul address are accessble but whenever I browese to a website runningon nodes that are part of Virtual Server pool, IE just hangs for a while and comes back with Page disconnected error while packets on F5 shows as droped.
Vietual Server, pool, and nodes helath monitor shows they are up and i can ping Virtual Server address.
Am i missing any configuration?
Thanks.
12 Replies
- The_Bhattman
Nimbostratus
Hi Devansu,
This could be caused by a number of different settings. As a first check try recreating the VIP and pool without the a template and see the difference. I am not suggesting that the template is at fault but you tend to look under the hood without the template and sometimes you can spot a setting or configuration.
I hope this helps
Bhattman - Devansu_22043
Nimbostratus
Hi Bhattman,
I rectreat VIP and pool without template but result is smae. VIP, Pool, and nodes are up but packet are being dropped at F5. I am thinking something misconfigured at network or translation. I have set SNAT Pool to "Auto map" on virtual server.
One thing that i have doubt is that single interface from F5 to my foundry switch is the only connection plus port on foundry switch is in VLAN and tagged. is this type of network configuration is common for F5?
Thanks! - Devansu_22043
Nimbostratus
Hi Bhattman,
I rectreat VIP and pool without template but result is smae. VIP, Pool, and nodes are up but packet are being dropped at F5. I am thinking something misconfigured at network or translation. I have set SNAT Pool to "Auto map" on virtual server.
One thing that i have doubt is that single interface from F5 to my foundry switch is the only connection plus port on foundry switch is in VLAN and tagged. is this type of network configuration is common for F5?
Thanks! - The_Bhattman
Nimbostratus
Hi Devansu,
What are you seeing on the interface on the foundry switch? Are you seeing any record of packet drops there?
Bhattman - Devansu_22043
Nimbostratus
Hi Bhattman,
No. foundry switch is not dropping packets. However F5 is one who is not accepting packets and just drops them. It looks like packets are recheing to virtual address, verified by ping, but https request is not passing through from virtual address to pool member instead it shows as dropped packet in Network statistics. - Gortguy_105156
Nimbostratus
I'm having a similar issue. It happens intermittently. In my case, it seems to happen most frequently with pools containing a single member server, but does occur with pools containing multiple nodes. It acts as if the nodes are being flagged as "down", but nothing is posted to the LTM logs. - Devansu_22043
Nimbostratus
I am seeing same thing...I can see https request connections come to Virtual Server then to Virtual Address but beyoned that nothing happens so packets are not forwarding to pools then to nodes. something in middle cuasing F5 to stop forwarding packes and https request from virtual servers to pool. - The_Bhattman
Nimbostratus
At this point you might want to simply contact F5 Support where they can run through your configuration and identify what it might be.
Bhattman - Gortguy_105156
Nimbostratus
Been there, done that and F5 Support is just as perplexed as we are at this point. Was hoping that someone in the community has seen this before and had some suggestions. - Gortguy_105156
Nimbostratus
Been there, done that and F5 Support is just as perplexed as we are at this point. Was hoping that someone in the community has seen this before and had some suggestions.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects
