Applies To:

Show Versions Show Versions

Manual Chapter: Troubleshooting BIG-IP Virtual Edition
Manual Chapter
Table of Contents   |   << Previous Chapter

Troubleshooting the BIG-IP Virtual Edition

If you have followed the setup procedures in this document, 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 configurations for BIG-IP VE that are outside the scope of this setup guide or altogether not supported in BIG-IP VE with certain hypervisor environments. Use the following troubleshooting information to solve problems and learn of limitations that you might encounter with BIG-IP VE.

XenCenter OVF wizard's Run Operating System Fixups option blocks appliance import
When importing the OVA into XenCenter, make sure the Run Operating System Fixups check box is not selected.
XenServer reservations should be set
When importing an OVA into XenServer, CPU priority is not set. F5 Networks recommends setting a higher priority for the virtual machine (VM). To do this, using XenCenter, click the General tab for the VM, click Properties, and under the CPU and Memory tab, move the scheduling priority to the highest setting.
XenServer deployments are not allocated on demand
BIG-IP system deployments will automatically consume 40 GB of space on Thick configured storage repositories. Utilize Thin deployment strategies on the Storage Repository to make use of allocate on-demand disk allocation strategies.
XenServer allocates less RAM than configured
XenServer virtual machine memory allocations are inclusive of the emulated hardware. A slight difference between memory allocated and memory presented to the virtual machine can be noticed. BIG-IP software has been written to accommodate this difference with no adverse effects on traffic.
Virtual network interface status is wrong
The BIG-IP VE system reports the status of host-only network interfaces as UNINITIALIZED, even though the interface is functioning normally.
Auto-licensing and the default management route
If you have not defined a default route to the management port, the default interface 1.1 is used, which does not work. To prevent this from occurring, verify that you have defined a default route for the management port before attempting to activate a license.
BIG-IP licensing and User Configuration Sets
When you import a User Configuration Set (UCS) from another BIG-IP or BIG-IP VE system, the system overwrites the local license with the license contained in the UCS. To work around this issue, you can re-license the local system after importing the UCS by accessing a backup copy of the license file, located in /config/bigip.license.bak. Also, when importing a UCS, you should ensure that the host names of the two systems differ. When the host names differ, the system correctly imports only the configuration data that is common to both the originating platform and the target platform. If the host names match, the system attempts to import all of the UCS configuration data, which can cause the import process to fail.
Editing the virtual guest configuration
F5 Networks strongly recommends that you do not edit the virtual configuration of BIG-IP VE, except for the virtual network interface mappings.
SSL::sessionid iRule command
The SSL::sessionid command within an iRule returns a blank value with BIG-IP VE.
Errors when using the bigpipe import command
Use of the b import default command can generate Security Enhanced Linux (SELinux) errors. You can ignore these errors.
Use of SNMP OID for RMON tables
Setting the source OID for RMON alarm, event, and history tables generates an error message. This OID will be disabled in future releases.
Media speed messages in log file
When starting the BIG-IP VE system or when removing an interface from a VLAN, the system logs media-related messages to the file /var/log/ltm. You can ignore these messages.
Exiting the shell at a MOS bash prompt
When you type exit at a Maintenance Operating System (MOS) prompt, the system appears unresponsive. Use the hypervisor's reset controls, or power off and power on the BIG-IP VE virtual machine to restore functionality.
Importing a UCS from the BIG-IP Virtual Edition Trial
When you import a UCS from the BIG-IP Virtual Edition Trial, the system displays an error message. You can ignore this message.
The virtual switch clears the QoS field in 802.1q headers
A hypervisor's Layer 2 bridging device might remove quality of service (QoS) classification from packets.
Table of Contents   |   << Previous Chapter

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)