Setup guide

Troubleshooting BIG-IP Virtual Edition
If you have followed the setup procedures as described in this guide, BIG-IP
®
VE should be working
correctly with the hypervisor. However, because BIG-IP VE emulates BIG-IP hardware running in a virtual
environment, you might encounter some issues as you try new congurations for BIG-IP VE that are outside
the scope of this setup guide, or unsupported in BIG-IP VE with certain hypervisor environments. Use this
troubleshooting information to solve problems and address limitations that you might encounter with BIG-IP
VE.
Event log reports insufficient video RAM
On VMware ESXi systems only, the following event message is logged:
The maximum resolution of the virtual machine will be limited to 1176x885 at 16 bits per pixel. To use
the congured maximum resolution of 2360x1770 at 16 bits per pixel, increase the amount of video
RAM allocated to this virtual machine by setting svga.vramSize="16708800" in the virtual machine's
conguration le.
You can ignore this message or follow the recommended action without adverse effects.
Time synchronization using VMware Tools or NTP protocol
If you want to use VMware Tools to enable time synchronization, you must select the Synchronize
guest time with host check box within vSphere Client. If you want to use network time protocol (NTP)
instead, you must rst disable time synchronization in VMware Tools by clearing the check box within
vSphere Client. For more information, see the VMware vSphere
™
Client documentation. Note that the
two units of a BIG-IP VE redundant system conguration must share the same time synchronization
source.
Incorrect status of VMware Tools in vSphere
VMware vSphere incorrectly shows the status of VMware Tools as Not Installed. You can verify that
VMware Tools are installed by viewing the IP Address and DNS Name elds on the vSphere screen.
Note that if you migrate the virtual machine or start a snapshot or cloned image of the virtual machine,
the status correctly shows as Unmanaged.
Lack of VMXNET3 availability
The VMXNET3 driver can become unavailable after you suspend and resume BIG-IP VE. Resetting
the BIG-IP VE will resolve the problem.
Use of VLAN groups
Use of VLAN groups with BIG-IP VE requires proper conguration of the VMware vSwitch. To use
the VLAN group feature, you must congure security policies on the vSwitch. The properties of the
security policy that you need to congure are Promiscuous Mode and Forged Transmits. For any
transparency mode, you must congure these properties to accept (rather than reject) the security policy
exceptions on the vSwitch. For information about how to congure these options, see the VMware ESX
®
or ESXi
®
Conguration Guide.
Use of Single Configuration File (SCF) feature
Copying an SCF from a VMware host system to an F5 hardware platform causes an error related to
interface mismatching. Edit the SCF and remove speed and duplex media statements from the network
interface statements before importing.
Configuration of an OVF with additional interfaces
When you deploy an OVF with more than ve interfaces (one management interface and more than
four TMM interfaces), the interface numbering might appear out of order. To view the actual
TMM-to-vSwitch portgroup interface mapping, compare the MAC addresses of the interfaces displayed
in the BIG-IP Conguration utility to those displayed in the vSphere Client.
22
Troubleshooting BIG-IP Virtual Edition