Forum Discussion
NimbostratusVS is not working
Hi Guys,
My name is Marian, I'm a new user in DevCentral. I have problems with a VS (10.190.8.10) we create one is for http, one for rtsp and one for rtmp. The thing is when a client (10.190.100.150) ask for the content the VS looks like is not working. The LTM is the gateway for the nodes (10.190.23.254). I have a default route for this so I don't have Snat. I have a tcpdump, If someone can be so kind as to give me a review. Thanks a lot!!
[root@Prod_A:Active] config tcpdump -e -i 0.0 -nn -p host 10.190.100.159 and host 10.190.8.10 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 12:18:17.590753 ethertype 802.1Q (0x8100), length 70: vlan 4093, p 0, ethertype IPv4, 10.190.100.159.56320 > 10.190.8.10.80: S 3178197221:3178197221(0) win 65535 12:18:17.590796 ethertype 802.1Q (0x8100), length 70: vlan 4093, p 0, ethertype IPv4, 10.190.8.10.80 > 10.190.100.159.56320: S 3466574693:3466574693(0) ack 3178197222 win 4014 12:18:17.656727 ethertype 802.1Q (0x8100), length 58: vlan 4093, p 0, ethertype IPv4, 10.190.100.159.56320 > 10.190.8.10.80: . ack 1 win 1024 12:18:17.657617 ethertype 802.1Q (0x8100), length 372: vlan 4093, p 0, ethertype IPv4, 10.190.100.159.56320 > 10.190.8.10.80: P 1:315(314) ack 1 win 1024 12:18:17.657642 ethertype 802.1Q (0x8100), length 58: vlan 4093, p 0, ethertype IPv4, 10.190.8.10.80 > 10.190.100.159.56320: . ack 315 win 4328 12:18:21.336715 ethertype 802.1Q (0x8100), length 70: vlan 4093, p 0, ethertype IPv4, 10.190.100.159.56327 > 10.190.8.10.80: S 4045256497:4045256497(0) win 8192 12:18:21.336765 ethertype 802.1Q (0x8100), length 70: vlan 4093, p 0, ethertype IPv4, 10.190.8.10.80 > 10.190.100.159.56327: S 1795969471:1795969471(0) ack 4045256498 win 4014 12:18:21.402397 ethertype 802.1Q (0x8100), length 58: vlan 4093, p 0, ethertype IPv4, 10.190.100.159.56327 > 10.190.8.10.80: . ack 1 win 64 12:18:21.402988 ethertype 802.1Q (0x8100), length 144: vlan 4093, p 0, ethertype IPv4, 10.190.100.159.56327 > 10.190.8.10.80: P 1:87(86) ack 1 win 64 12:18:21.403009 ethertype 802.1Q (0x8100), length 58: vlan 4093, p 0, ethertype IPv4, 10.190.8.10.80 > 10.190.100.159.56327: . ack 87 win 4100 12:18:21.468875 ethertype 802.1Q (0x8100), length 113: vlan 4093, p 0, ethertype IPv4, 10.190.100.159.56327 > 10.190.8.10.80: P 87:142(55) ack 1 win 64 12:18:21.468906, ethertype 802.1Q (0x8100), length 58: vlan 4093, p 0, ethertype IPv4, 10.190.8.10.80 > 10.190.100.159.56327: . ack 142 win 4155 12:18:24.353261 ethertype 802.1Q (0x8100), length 70: vlan 4093, p 0, ethertype IPv4, 10.190.100.159.56328 > 10.190.8.10.80: S 2939790242:2939790242(0) win 8192 12:18:24.353312 ethertype 802.1Q (0x8100), length 70: vlan 4093, p 0, ethertype IPv4, 10.190.8.10.80 > 10.190.100.159.56328: S 2100515138:2100515138(0) ack 2939790243 win 4014 12:18:24.353072 ethertype 802.1Q (0x8100), length 58: vlan 4093, p 0, ethertype IPv4, 10.190.100.159.56327 > 10.190.8.10.80: F 142:142(0) ack 1 win 64 12:18:24.353106 ethertype 802.1Q (0x8100), length 58: vlan 4093, p 0, ethertype IPv4, 10.190.8.10.80 > 10.190.100.159.56327: . ack 143 win 4155 12:18:24.354174 ethertype 802.1Q (0x8100), length 70: vlan 4093, p 0, ethertype IPv4, 10.190.100.159.56331 > 10.190.8.10.80: S 164731020:164731020(0) win 8192 12:18:24.354240 ethertype 802.1Q (0x8100), length 70: vlan 4093, p 0, ethertype IPv4, 10.190.8.10.80 > 10.190.100.159.56331: S 2135722860:2135722860(0) ack 164731021 win 4014 12:18:24.418076 ethertype 802.1Q (0x8100), length 58: vlan 4093, p 0, ethertype IPv4, 10.190.100.159.56328 > 10.190.8.10.80: R 2939790243:2939790243(0) win 0
20 Replies
Marian_A_142180how can I check that?
Cory_50405Noctilucent
I didn't see the three-way handshake in your server side pcap snippet above, but you'll be able to find it there. When your server responds to the client's original SYN packet (which will contain the client's MSS), your server should specify an MSS in response. So in your server's SYN ACK packet, you should see an MSS specified in your Wireshark capture.
- Marian_A_142180
Cory, With the MSS
12:09:50.900397, ethertype 802.1Q (0x8100), length 70: vlan 80, p 0, ethertype IPv4, 10.190.8.10.80 > 10.190.100.185.54688: S 301435182:301435182(0) ack 3658454735 win 4014
I'm checking the pcap and I have this
10.190.23.1 is the server production and the 10.190.23.5 ip the self ip for standby ltm
- Cory_50405That looks to be http keepalive traffic from your standby LTM. I would guess based on that 403 error that the node 23.1 does not show as active in your standby LTM. I don't see the MSS specified in that tcpdump line. It should come after the window size. I think specifying -e will omit the MSS. Please try the tcpdump again without the -e
- Marian_A_142180
[root@Pod_A:Active] config tcpdump -i 0.0 -nn -p host 10.190.100.185 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on 0.0, link-type EN10MB (Ethernet), capture size 96 bytes
13:16:51.839228 IP 10.190.100.185.57047 > 10.190.8.10.80: S 206167606:206167606(0) win 8192
13:16:51.839241 IP 10.190.100.185.57047 > 10.190.8.10.80: S 206167606:206167606(0) win 8192
- Cory_50405
Just following up on this for closure, the issue turned out to be a network device in between the servers and the F5 that was preventing the return traffic.
- Marian_A_142180Thanks Cory for all your help!! The Automap works ok!!
