In order to use BIG-IP VE, you must have a license from F5. Starting with BIG-IP VE version 13.1, you can revoke the license from a virtual machine and re-use it on another virtual machine.

From the Configuration utility, to revoke the license, go to System > License and click Revoke.

From tmsh, to revoke the license, run the command tmsh revoke sys license.

This functionality works for BIG-IP VE BYOL only.

1. Use an SSH tool to access the BIG-IP^® VE command line.
2. Log in as root.
3. Type tmsh to open the tmsh utility.
   You will see tmsh at the prompt once the utility is opened.
4. To determine whether TSO support is currently enabled, use the command:
   show sys db tm.tcpsegmentationoffload
5. To enable support for TSO, use the command:
   sys db tm.tcpsegmentationoffload enable
6. To disable support for TSO, use the command:
   sys db tm.tcpsegmentationoffload disable

1. Shut down the guest.
2. Edit the guest’s XML by using a tool like virsh edit.
3. In each desired virtio <interface> section, add the following element:
   <driver name='vhost' queues=’#’/>
   where # equals the number of queues.

   Note: The default number of queues for a KVM guest is 1. The optimum number of queues varies by deployment and depends on throughput needs and total desired guest footprint.
4. Save the file.
5. Start the guest.

NIC teaming, also known as port channels, bonding, or in BIG-IP, trunking, is defined by the Link Aggregation standard IEEE 802.1AX-2008 (formerly IEEE 802.3ad). This standard offers both increased bandwidth and link failure redundancy at Layer 2.

In a virtual environment, the same MAC address must be assigned to all teamed/aggregated ports. Either the hypervisor or the guest (in kernel trusted mode) can do this assignment.

SR-IOV uses virtual functions to send packets from two or more separate physical ports to the guest. The hypervisor never sees these packets.

In this case, LACP active monitoring in the guest is not possible because the guest does not receive bridge control packets.

1. Use an SSH tool to access the BIG-IP VE tmsh utility.
2. From the command line, log in as root.
3. List the current size of the directories on your disk so you can determine which ones need to be resized.
   tmsh show sys disk directory
4. Expand the size of the directories in which you need additional space.
   tmsh modify sys disk directory <directory name> new-size <new directory size in 1KB blocks>
   For example, use tmsh modify sys disk directory /config new-size 3145740 to increase the size of /config directory to 3145740 1KB blocks (or roughly 3,221,237,760 bytes).
5. To confirm that the command you just submitted is properly scheduled, you can show the new list of directories again.
   tmsh show sys disk directory
6. If you change your mind about a submitted size change, you can revoke the size change.
   tmsh modify sys disk directory /config new-size 0
   In this example, the size of the /config directory is left as is, revoking any scheduled size changes.
   After you submit this sequence of tmsh commands, the directory size changes will be scheduled to occur the next time the BIG-IP VE virtual machine (VM) is rebooted.

1. Use SSH to connect to BIG-IP VE.
2. If you need to determine which NICs are available, stop TMM by typing bigstart stop tmm. Then type ip addr to view the list of available NICs.
3. Change the management NIC by typing tmsh modify sys db provision.managementeth value eth1 where eth1 is the NIC you want to use for management. You can use any available NIC.
4. Press Enter.
5. Reboot BIG-IP VE by typing reboot and pressing Enter.

1. Use an SSH tool to connect to BIG-IP VE.
2. Return to the default configuration.
   tmsh load sys config default
3. Save the changes.
   tmsh save sys config
4. Set a database variable so that the number of NICs will be recognized on reboot.
   setdb provision.1nic enable
5. Reboot BIG-IP VE.
   reboot

1. Use an SSH tool to connect to BIG-IP VE.
2. Return to the default configuration of BIG-IP VE.
   tmsh load sys config default
3. Save the changes.
   tmsh save sys config
4. Set a database variable so that the number of NICs will be recognized on reboot.
   setdb provision.1nic forced_enable
5. Reboot BIG-IP VE.
   reboot