Hello, Our team has inherited the F5 with Chassis serial number is bip216816s, and i’d like to test the simple LBM web server for our lab. This is our network: We have around 20 internal VLANS interconnected with each other. I uplink one trunk port from this F5 into one of our network switch which allowed 2 vlan 300 and vlan 301. I configured: server 1 with IIS installed : 10.10.10.10 vlan 300 server 2 with IIS installed : 10.10.10.11 vlan 300 I put these 2 servers into the pool, then put this pool to Virtual Server with IP 10.10.20.20 in vlan 301.(set port 80, http, Round Robin) I created a SNAT list with Translation Address is 10.10.20.20, Origin Address are: 10.10.10.10, 10.10.10.11. This is what i suppose it works but obviously it’s not: When i type ip 10.10.20.20 in web-browser, i suppose it will load either the default web-page of either server 1 or server 2.
I can ping the ip 10.10.20.20 port 80 from any vlans. i can browser default webpage of server 1 and server 2 by typing its ip in web-browser directly.
Please kindly help as i am very new with F5.
Thanks, Ivy
Change your virtual server to SNAT auto map and see if this fixes your issue.
Thanks for your reply, but it’s still not fixed.
Try doing a tcpdump on your BIG-IP to see what communications are going between it and the servers: tcpdump -nni 0.0 host 10.10.10.10 or host 10.10.10.11
Under System>Console, i ran the command, i got the message below BIGpipe parsing error: 012e0008:3: The requested command (tcpdump -nni 0.0 host 10.10.10.11) is invalid
You’ll need to do this from CLI, in the bash shell. To get to bash from TMSH, type ‘run util bash’
Is the System>Console is the CLI ? The console is the only option where we can type the commands in.
You should be able to SSH to the BIG-IP using Putty or some other SSH client.
This is my version BIG-IP 9.4.5 Build 1049.80 Final. Sorry i am still finding how to open the bash shell and TMSH
Now I can have the tcpdump on host 10.10.10.10 and .11, what would we expect to see ?
You are looking for two way traffic between the BIG-IP and your two servers. Look to see if a three-way handshake is completing (SYN, SYN ACK, ACK). Feel free to post the tcpdump results here for us to take a look at. Though if there are sensitive IP addresses used, you might want to sanitize those before posting.
Okay, so your BIG-IP (10.10.10.13) is attempting to contact the server (10.10.10.10) on port 80. You can see the SYN packets leaving the BIG-IP on vlan 300, but no SYN ACK ever comes back from the server. ARP is working, so layer 2 looks to be good. Is there a firewall or some other device that could be blocking the packets from getting to your 10.10.10.10 server?
Please see the extract, i don’t know why i have the IP 10.10.10.13 tcpdump -nni 0.0 host 10.10.10.10 tcpdump: listening on 0.0 07:50:47.596993 802.1Q vlan300 P0 10.10.10.10 > 224.0.0.22: igmp v3 report, 1 group record(s) [ttl 1] 07:50:53.861256 802.1Q vlan300 P0 arp who-has 10.10.10.1 tell 10.10.10.10 07:51:00.300554 802.1Q vlan300 P0 arp who-has 10.10.10.10 tell 10.10.10.13 07:51:00.300699 802.1Q vlan300 P0 arp reply 10.10.10.10 is-at 0:26:b9:51:6d:62 07:51:00.300703 802.1Q vlan300 P0 10.10.10.13.15376 > 10.10.10.10.80: S 1143421786:1143421786(0) win 4380 07:51:06.784879 802.1Q vlan300 P0 10.10.10.13.15376 > 10.10.10.10.80: S 1143421786:1143421786(0) win 4380 07:51:13.184930 802.1Q vlan300 P0 10.10.10.13.15376 > 10.10.10.10.80: S 1143421786:1143421786(0) win 4380 07:51:50.902001 802.1Q vlan300 P0 10.10.10.10.137 > 10.10.10.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 07:51:51.679871 802.1Q vlan300 P0 10.10.10.10.137 > 10.10.10.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 07:51:52.465949 802.1Q vlan300 P0 10.10.10.10.137 > 10.10.10.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 07:52:51.089916 802.1Q vlan300 P0 10.10.10.10 > 224.0.0.22: igmp v3 report, 1 group record(s) [ttl 1] 07:54:17.598708 802.1Q vlan300 P0 10.10.10.10.137 > 10.10.10.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 07:54:17.599002 802.1Q vlan300 P0 10.10.10.10.61801 > 224.0.0.252.5355: udp 24 [ttl 1] 07:54:18.008792 802.1Q vlan300 P0 10.10.10.10.61801 > 224.0.0.252.5355: udp 24 [ttl 1] 07:54:18.393994 802.1Q vlan300 P0 10.10.10.10.137 > 10.10.10.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 07:54:19.180953 802.1Q vlan300 P0 10.10.10.10.137 > 10.10.10.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 07:55:01.085261 802.1Q vlan300 P0 10.10.10.10 > 224.0.0.22: igmp v3 report, 1 group record(s) [ttl 1] 07:56:42.852276 802.1Q vlan300 P0 arp who-has 10.10.10.1 tell 10.10.10.10 07:56:52.381906 802.1Q vlan300 P0 arp who-has 10.10.10.10 tell 10.10.10.13 07:56:52.382121 802.1Q vlan300 P0 arp reply 10.10.10.10 is-at 0:26:b9:51:6d:62 07:56:52.382125 802.1Q vlan300 P0 10.10.10.13.15378 > 10.10.10.10.80: S 1587047468:1587047468(0) win 4380 07:56:58.784901 802.1Q vlan300 P0 10.10.10.13.15378 > 10.10.10.10.80: S 1587047468:1587047468(0) win 4380 07:57:01.088986 802.1Q vlan300 P0 10.10.10.10 > 224.0.0.22: igmp v3 report, 1 group record(s) [ttl 1]
10.10.10.13 is likely a self IP address on your BIG-IP. You can view it under Network → Self IPs.
oho, that’s right, i forgot that i set the self IP for vlan 300.
I think the server 10.10.10.10 and .11 itself is on the company domain and i cannot turn off Windows Firewall. I am not aware of any Firewall in my network. Is that possible that the Big-IP is set the firewall for itself to regulate the traffic ? So basically the server 10.10.10.10 cannot response to BIG-IP on port 80, because i can open its default webpage on web-browser.
The BIG-IP isn’t blocking anything in this case. From the packet capture, you can see that the BIG-IP is sending out SYN packets to the server on port 80, but no response ever comes back. The server administrator should be able to perform a packet capture on the server to determine if the SYN packets from the self IP are ever arriving there. If not, it is almost certainly some network security device like a firewall blocking the traffic.
After i un-joined the domain and disable firewall of the server 10.10.10.10, i don’t see the 10.10.10.13 in tcpdump anymore. tcpdump -nni 0.0 host 10.10.10.10 tcpdump: listening on 0.0 13:47:42.507730 802.1Q vlan304 P0 10.10.10.10.137 > 10.10.10.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 13:47:42.508024 802.1Q vlan304 P0 10.10.10.10.62031 > 224.0.0.252.5355: udp 22 [ttl 1] 13:47:42.921451 802.1Q vlan304 P0 10.10.10.10.62031 > 224.0.0.252.5355: udp 22 [ttl 1] 13:47:43.295719 802.1Q vlan304 P0 10.10.10.10.137 > 10.10.10.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 13:47:44.091308 802.1Q vlan304 P0 10.10.10.10.137 > 10.10.10.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 13:48:47.194302 802.1Q vlan304 P0 10.10.10.10 > 224.0.0.22: igmp v3 report, 1 group record(s) [ttl 1] 13:48:47.195035 802.1Q vlan304 P0 10.10.10.10 > 224.0.0.22: igmp v3 report, 1 group record(s) [ttl 1] 13:48:47.199278 802.1Q vlan304 P0 10.10.10.10 > 224.0.0.22: igmp v3 report, 1 group record(s) [ttl 1] 13:48:47.200455 802.1Q vlan304 P0 10.10.10.10.51884 > 224.0.0.252.5355: udp 27 [ttl 1] 13:48:47.250465 802.1Q vlan304 P0 10.10.10.10 > 224.0.0.22: igmp v3 report, 2 group record(s) [ttl 1] 13:48:47.257773 802.1Q vlan304 P0 10.10.10.10.137 > 10.10.10.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 13:48:47.258064 802.1Q vlan304 P0 10.10.10.10.57557 > 224.0.0.252.5355: udp 22 [ttl 1] 13:48:47.609328 802.1Q vlan304 P0 10.10.10.10.51884 > 224.0.0.252.5355: udp 27 [ttl 1] 13:48:47.671769 802.1Q vlan304 P0 10.10.10.10.57557 > 224.0.0.252.5355: udp 22 [ttl 1] 13:48:48.031091 802.1Q vlan304 P0 10.10.10.10 > 224.0.0.22: igmp v3 report, 1 group record(s) [ttl 1] 13:48:48.031242 802.1Q vlan304 P0 10.10.10.10 > 224.0.0.22: igmp v3 report, 1 group record(s) [ttl 1] 13:48:48.031967 802.1Q vlan304 P0 10.10.10.10.60172 > 224.0.0.252.5355: udp 27 [ttl 1] 13:48:48.046007 802.1Q vlan304 P0 10.10.10.10.137 > 10.10.10.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 13:48:48.248852 802.1Q vlan304 P0 10.10.10.10 > 224.0.0.22: igmp v3 report, 1 group record(s) [ttl 1] 13:48:48.451684 802.1Q vlan304 P0 10.10.10.10.60172 > 224.0.0.252.5355: udp 27 [ttl 1] 13:48:48.825909 802.1Q vlan304 P0 10.10.10.10.137 > 10.10.10.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 13:48:50.261970 802.1Q vlan304 P0 10.10.10.10.137 > 10.10.10.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 13:48:50.262124 802.1Q vlan304 P0 10.10.10.10.52989 > 224.0.0.252.5355: udp 22 [ttl 1] 13:48:50.682401 802.1Q vlan304 P0 10.10.10.10.52989 > 224.0.0.252.5355: udp 22 [ttl 1] 13:48:51.056486 802.1Q vlan304 P0 10.10.10.10.137 > 10.10.10.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 13:48:51.852035 802.1Q vlan304 P0 10.10.10.10.137 > 10.10.10.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST 13:49:00.244310 802.1Q vlan304 P0 10.10.10.10 > 224.0.0.22: igmp v3 report, 1 group record(s) [ttl 1] 13:49:03.738189 802.1Q vlan304 P0 10.10.10.10 > 224.0.0.22: igmp v3 report, 1 group record(s) [ttl 1]
THIS IS TCPDUMP IN VIRTUAL SERVER INTERFACE tcpdump -nni 0.0 host 10.10.20.20 tcpdump: listening on 0.0 13:49:56.493263 802.1Q vlan301 P0 10.111.148.60.58668 > 10.10.20.20.80: S 793623215:793623215(0) win 8192 (DF) 13:49:56.493272 802.1Q vlan301 P0 10.10.20.20.80 > 10.111.148.60.58668: R 0:0(0) ack 793623216 win 0 (DF) 13:49:56.505670 802.1Q vlan301 P0 10.111.148.60.58669 > 10.10.20.20.80: S 3973000868:3973000868(0) win 8192 (DF) 13:49:56.505674 802.1Q vlan301 P0 10.10.20.20.80 > 10.111.148.60.58669: R 0:0(0) ack 3973000869 win 0 (DF) 13:49:56.753524 802.1Q vlan301 P0 10.111.148.60.58670 > 10.10.20.20.80: S 2472106228:2472106228(0) win 8192 (DF) 13:49:56.753528 802.1Q vlan301 P0 10.10.20.20.80 > 10.111.148.60.58670: R 0:0(0) ack 2472106229 win 0 (DF) 13:49:56.989606 802.1Q vlan301 P0 10.111.148.60.58668 > 10.10.20.20.80: S 793623215:793623215(0) win 8192 (DF) 13:49:56.989610 802.1Q vlan301 P0 10.10.20.20.80 > 10.111.148.60.58668: R 0:0(0) ack 1 win 0 (DF) 13:49:57.006444 802.1Q vlan301 P0 10.111.148.60.58669 > 10.10.20.20.80: S 3973000868:3973000868(0) win 8192 (DF) 13:49:57.006447 802.1Q vlan301 P0 10.10.20.20.80 > 10.111.148.60.58669: R 0:0(0) ack 1 win 0 (DF) 13:49:57.252624 802.1Q vlan301 P0 10.111.148.60.58670 > 10.10.20.20.80: S 2472106228:2472106228(0) win 8192 (DF) 13:49:57.252628 802.1Q vlan301 P0 10.10.20.20.80 > 10.111.148.60.58670: R 0:0(0) ack 1 win 0 (DF) 13:49:57.493539 802.1Q vlan301 P0 10.111.148.60.58668 > 10.10.20.20.80: S 793623215:793623215(0) win 8192 (DF) 13:49:57.493543 802.1Q vlan301 P0 10.10.20.20.80 > 10.111.148.60.58668: R 0:0(0) ack 1 win 0 (DF) 13:49:57.510538 802.1Q vlan301 P0 10.111.148.60.58669 > 10.10.20.20.80: S 3973000868:3973000868(0) win 8192 (DF) 13:49:57.510541 802.1Q vlan301 P0 10.10.20.20.80 > 10.111.148.60.58669: R 0:0(0) ack 1 win 0 (DF) 13:49:57.753497 802.1Q vlan301 P0 10.111.148.60.58670 > 10.10.20.20.80: S 2472106228:2472106228(0) win 8192 (DF) 13:49:57.753301 802.1Q vlan301 P0 10.10.20.20.80 > 10.111.148.60.58670: R 0:0(0) ack 1 win 0 (DF)
The most recent tcpdump that you ran on the server side that you said the BIG-IP self IP was missing is because of your tcpdump syntax. You were only watching for 10.10.10.10 and not your self IP. Use this: tcpdump -nni 0.0 -s0 host 10.10.10.13 and host 10.10.10.10 The virtual server side capture is what I would expect to see given that the pool members are not reachable. The BIG-IP resets the client connection immediately.