BigIP (f5) 16.0.1 v0.0.3 problem with gateway

bXunter

New Member
Apr 17, 2019
5
1
3
40
Hello guy's,

In our company we are at stage to implement and buy 2 physical f5 hardware and 2 BigIP virtual edition appliance.

We have a couple of Proxmox hypervisor, also we have a cluster of 3 identical nodes. We try on an every of it to run BigIP virtual edition, but on every server we face a strange/same problem that we can't ping gateway from VM.

We also have own AS number and 100+ VM (on public IP and around 300 VMs on private IP) and everything work like a charm, only this BigIP had a problem running on Proxmox obviously.

I've downloaded BigIP virtual edition from official website, in qcow2 format, then SCP it to server, do convert to .RAW then import in previously created VM for BigIP, then attach disk to VM, and boot it. It was straightforward. (we also try without converting and actually using qcow2 from source, same thing/problem occurs)

After booting BigIP, logging with credentials next thing is to type "config" and you got simple CLI interface where is 1st step to chose between using IPv4 or IPv6, we chose ipv4, then next step is to configure Mngmt IP, netmask and GW.

In our case that is 10.100.200.200 IP, 255.255.255.0 and GW is 10.100.200.1

That's it, after that you should get settings over web GUI at https://10.100.200.200 but we are stuck at that point. Browser say connection timeout.

After troubleshooting we notice that from VM we can't ping 10.100.200.1 (we don't have any firewall). That's actually pretty explain WHY we don't get user interface at browser, but mystery is WHY BigIP don't see gateway.

Things I've tried to resolve this is:

1. Changing IP
2. Switching to different network controller (all of them actually).
3. Changing MAC address
4. Adding more network interfaces.
5. Booting like .RAW also like QCOW2.
6. Putting public IP from our AS number.

None of these helps us.

Does anyone have some suggestion regarding this?

Cheers.
 

wolfgang

Proxmox Staff Member
Staff member
Oct 1, 2014
6,483
454
103
Hi,

maybe you have MAC filtering enabled on your switch (Phy Network) and your Vm is not allowed to communicate whit this MAc on this port?
Or maybe BigIP is not compatible with the used vNIC.
 

bXunter

New Member
Apr 17, 2019
5
1
3
40
Hello,

After 2 days of searching and even setup whole new proxmox server for testing, without proper BigIP documentation, Ive figured out that in initial boot I must create 3 virtual NIC, then after boot to setup only 1 for mngt, other 2 must be empty for BigIP to fill it with his own information.

After that I got Web UI.

So that is solution in my case, maybe this information will be useful to someone.

By the way, I've been testing for two days now and BigIP behaves great inside Proxmox, unlike previous versions that didn't want to work properly.

Regards.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!