Initial Setup of a Virtual BIG IP

Hi,

 

So first of donwolad your OVA (I advise you to download last version: v14):

 

https://support.f5.com/csp/my-support/home

 

Then install you OVA in VMWARE/CITRIX. You should have 4 interface (the first one is dedicated for mgmt)

 

So configure your Hardware requirements to host BIG-IP VE (2-core CPU requires at least 4 GB of RAM, it's depending the module you want to provision):

 

• 1 core need 2 Gb
• 2 core need 4 Gb
• 4 core need 8 Gb
• 8 core need 16 Gb

https://support.f5.com/csp/article/K15796

 

Don't forget to fix your interface/vlan on each Interface (Vmware). I advise you to have an Dedicated interface for mgmt.

 

usin cli enter the following command: config

 

then configure mgmt IP (IP/mask and gw).

 

At this point you can reach your VE using GUI and you can install your VE. Install your License and set your SelfIP...

 

If you need help on specific point keep me in touch.

 

You have a greate video that show you all steps: https://www.youtube.com/watch?v=Li9WO2M2YLY

 

for doc: BIG-IP Virtual Edition 13.0.0 and VMware ESXi: Setup : https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-ve-setup-vmware-esxi-13-0-0.html

 

Regards

 

Right now I'm kinda running into some problems,

 

 

I'm getting the above error message when I try to access my set management IP (192.168.1.245) and I've already set my computer's IP address in the same network as my management IP (192.168.1 25) as shown below

 

 

 

It doesn't seem to do the trick. The only problem I see might be in these parts, but sadly I can't identify what the problem is.

 

 

 

I'm thinking that VMnet0 to VMnet 2 aren't supposed to be placed randomly, and that they have been already pre-configured to be what corresponding port in a BIG IP appliance. I'm currently using BIGIP-13.0.0.0.0.1645.ALL-scsi.OVA since I'm still downloading the V 14.1.0.3 version.

 

Can you coIn Virtual network editor set WMnet as:

 

NAT

 

then

 

Check -> Connect a host virtual adapter to this network

 

Check -> Use local DHCP service to disctribut IP address to VMs

 

set subnet IP: 192.168.1.0 - Subnet Mask: 255.255.255.0nfirm that your interface is UP?

 

I checked if all of my VMnet's are UP through pinging them, they did respond, so I assume they are currently UP. Also, I have done what you instructed me to do sir

 

 

but unfortunately, it still shows the same problem.

 

Try making

VMNet 1

the management interface

So something like:

VMnet1 Host-Only 192.168.1.0/24

Unfortunately I'm still having the same issues, I've read some things online about the same matter as well and almost all seems to be pointing at this issue (see image below) could this be the problem?

 

 

I have already done what you sirs have asked me to do to still no avail. I'm starting to think that it may be a problem with my NIC though I don't know if it should have this kind of effect to VE if BIG IP.

 

Can you try this 2 alternatives:

 

• Swith from nat to "host only" on your interface configuration

   

• try to connect your PC to a lan even if your are not in the same subnet. your interface will be UP...

   

regards