Friday, December 21, 2018

Weird F5 ip-forwarding virtual server not liking external floating IP.

So I got a lab setup in GNS3 to study. I have 10.0.2.250 as external vlan floating IP, .251 for bigip01 and .252 for bigip02. Bigip02 is active. I can ping from 10.0.1.111 which is in internal vlan to .251 and forwarding VS kicks in and ping works. However when ping from the 10.0.1.111 to .250 or .252 , VS not kick in. I tried with auto map on and off. I can ping internet etc.. with automap. But not the floating IP for external vlan or bigip02.

i run tcp dump.

Not working dump to 10.0.2.250

10.0.1.112 > 10.0.2.250: ICMP echo request, id 1995, seq 4, length 64 in slot1/tmm1 lis=

Working tcpdump to 10.0.2.251

10.0.2.251 > 10.0.1.111: ICMP echo reply, id 1985, seq 13, length 64 out slot1/tmm1 lis=/Common/default_gw

forwarding webserver setting

type: forwarding IP

source: 0.0.0.0/0

destination: 0.0.0.0/0

service port: all ports

protocol: all protocols

fastL4

SNAT: Tried auto map or none. Internet works eitherway.

Also I created another virtual server just to cover 2.250 floating IP or 2.252 floating IP and it works when this VS enabled. However, when I made the VS subnet /29 to cover both .250 and .252, it stops working again. It is really weird. I double checked webserver routing table which has only default gateway(bigip floating IP 10.0.1.250). I checked F5 routing table and virtual servers and did not find any other configuration interfering with it.

is this a bug or something wrong with my config? It is not a big deal for the purpose of the lab I am doing. But It is really bugging me.

My lab diagram here -> https://imgur.com/a/hnnPXyJ



No comments:

Post a Comment