VS is not working

This capture is just on the client/VS side. Can you also post a capture between your F5 and the web server sitting behind your F5? Could you also elaborate on your pool config?

Thanks Cody,

I'm trying to make a capture but is empty:

[root@:Active] config tcpdump -e -i 0.0 -nn -p host 10.190.8.10 and host 10.190.23.1 and port 80 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on 0.0, link-type EN10MB (Ethernet), capture size 96 bytes ^C 0 packets captured 0 packets received by filter 0 packets dropped by kernel [root@Prod_A:Active] config tcpdump -e -i 0.0 -nn -p host 10.190.8.10 and host 10.190.23.2 and port 80 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on 0.0, link-type EN10MB (Ethernet), capture size 96 bytes ^C 0 packets captured 0 packets received by filter 0 packets dropped by kernel [root@Prod_A:Active] config

Status

Status

Status

Thanks for your time

Your tcpdump attempt on the server side is specifying the VIP address. Production traffic will not include the VIP if you are trying to capture on the server side. If you aren't performing SNAT, it'll be from the original client IP address to the servers. If you replace 10.190.8.10 with the client IP address in your two latest tcpdumps, you should see something.

Sorry Cory,

The capture

[root@Prod_A:Active] config tcpdump -e -i 0.0 -nn -p host 10.190.100.159 and port 80

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on 0.0, link-type EN10MB (Ethernet), capture size 96 bytes

17:30:11.952693 ethertype 802.1Q (0x8100), length 372: vlan 23, p 0, ethertype IPv4, 10.190.100.159.19482 > 10.190.23.1.80: P 2765136783:2765137097(314) ack 876391751 win 4380

17:30:16.152410 ethertype 802.1Q (0x8100), length 372: vlan 23, p 0, ethertype IPv4, 10.190.100.159.19482 > 10.190.23.1.80: P 0:314(314) ack 1 win 4380

17:30:24.352379 ethertype 802.1Q (0x8100), length 372: vlan 23, p 0, ethertype IPv4, 10.190.100.159.19482 > 10.190.23.1.80: P 0:314(314) ack 1 win 4380

17:30:33.858194 ethertype 802.1Q (0x8100), length 58: vlan 80, p 0, ethertype IPv4, 10.190.100.159.53435 > 10.190.8.10.80: R 4185587299:4185587299(0) ack 2320324681 win 0

17:30:33.858242 ethertype 802.1Q (0x8100), length 58: vlan 23, p 0, ethertype IPv4, 10.190.100.159.19482 > 10.190.23.1.80: R 314:314(0) ack 1 win 4380

17:30:33.939621 ethertype 802.1Q (0x8100), length 70: vlan 80, p 0, ethertype IPv4, 10.190.100.159.53441 > 10.190.8.10.80: S 3385486892:3385486892(0) win 65535

17:30:33.939666 ethertype 802.1Q (0x8100), length 70: vlan 80, p 0, ethertype IPv4, 10.190.8.10.80 > 10.190.100.159.53441: S 1185017584:1185017584(0) ack 3385486893 win 4014

17:30:34.005386 ethertype 802.1Q (0x8100), length 58: vlan 80, p 0, ethertype IPv4, 10.190.100.159.53441 > 10.190.8.10.80: . ack 1 win 1024

17:30:34.005459 ethertype 802.1Q (0x8100), length 70: vlan 23, p 0, ethertype IPv4, 10.190.100.159.53441 > 10.190.23.2.80: S 3170405114:3170405114(0) win 4380

17:30:34.005712 ethertype 802.1Q (0x8100), length 372: vlan 80, p 0, ethertype IPv4, 10.190.100.159.53441 > 10.190.8.10.80: P 1:315(314) ack 1 win 1024

17:30:34.005742 ethertype 802.1Q (0x8100), length 58: vlan 80, p 0, ethertype IPv4, 10.190.8.10.80 > 10.190.100.159.53441: . ack 315 win 4328

17:30:34.005917 ethertype 802.1Q (0x8100), length 70: vlan 23, p 0, ethertype IPv4, 10.190.23.2.80 > 10.190.100.159.53441: S 1090504938:1090504938(0) ack 3170405115 win 8192

17:30:34.005939 ethertype 802.1Q (0x8100), length 58: vlan 23, p 0, ethertype IPv4, 10.190.100.159.53441 > 10.190.23.2.80: . ack 1 win 4380

17:30:34.005945 ethertype 802.1Q (0x8100), length 372: vlan 23, p 0, ethertype IPv4, 10.190.100.159.53441 > 10.190.23.2.80: P 1:315(314) ack 1 win 4380

17:30:35.205918 ethertype 802.1Q (0x8100), length 372: vlan 23, p 0, ethertype IPv4, 10.190.100.159.53441 > 10.190.23.2.80: P 1:315(314) ack 1 win 4380

17:30:37.405690 ethertype 802.1Q (0x8100), length 372: vlan 23, p 0, ethertype IPv4, 10.190.100.159.53441 > 10.190.23.2.80: P 1:315(314) ack 1 win 4380

17:30:41.605896 ethertype 802.1Q (0x8100), length 372: vlan 23, p 0, ethertype IPv4, 10.190.100.159.53441 > 10.190.23.2.80: P 1:315(314) ack 1 win 4380

^C 17 packets captured 17 packets received by filter 0 packets dropped by kernel

So the three way handshake between your client and the VS completes, and then the three way handshake between the client and server completes. Your client then starts pushing data to your server and no acknowledgements come back after that point. What is your client trying to send to the server? It seems after the three way handshake, the server isn't responding any longer.

Well the client in this case, only request for content (video) to the server, we made a test asking the video directly on the server, "taking out" the LTM and we can see the content.

But could be that the server is not sending "correctly" the content to the LTM? Is correct that the LTM don't have configured AutoMap?

VS for HTTP is type standard and don't have profile the option es NONE :(

yes

Status

You've posted captures from both sides of the LTM and I don't see anything in these captures that points to the problem. Can you run a capture on one of the nodes by chance?

Cory,

I have the capture is helpful for you? or you need all the .pcapng file?