Forum Discussion

swo0sh_gt_13163's avatar
swo0sh_gt_13163
Icon for Altostratus rankAltostratus
Aug 16, 2014

F5 Virtual appliance - VLAN Management

Hello Folks,   Can someone help me deploying my virtual F5 appliance for a small lab purpose? I have F5 Management bridged with my wireless, so I can access the management interface as and when I ...
application delivery
deployment
LTM
management
virtualization
  • Kevin_Davies_40's avatar
    Kevin_Davies_40
    Aug 18, 2014

    When you provision a Host Only interface you must tick the option which says to create the interface in Windows otherwise it will not actually create a virtual interface which the OS needs to talk to the VM.

     

    Also when you have a NAT interface your default route should be to the .2 address and not the .1 address.

     

Kevin_Davies_40's avatar
Kevin_Davies_40
Icon for Nacreous rankNacreous
Aug 16, 2014

The VLAN's you want the F5 VE to communicate with the Internet must be set to NAT in Vmware. By default the PC address in the network is .1. When using NAT the route to the Internet is via .2.

For example an external vlan you might set it to host-only because it does not require any Internet access. This will be requests generated by you sent to VIP's on the BIGIP. Then the internal vlan would be set to NAT and a default route created on the BIGIP that points to .2 address. This means your bigip can not only reach services on your PC via .1 it can also reach servers beyond your PC via .2 using the default route.

There really is no need to have the management address available externally to the PC if you are the only person using it so I recommend Host only.

Sample Addressing - First Interface assigned to VM (Host only)
Management (eth0)
Existing

External VLAN (1.1) - Second Interface assigned to VM (NAT)
PC 192.168.74.1
SelfIP 192.168.74.10
Default Route to 192.168.74.2

Internal VLAN (1.2) - Third Interface assigned to VM (Host Only)
PC 192.168.87.1
SelfIP 192.168.87.10