You can increase throughput of BIG-IP^® VE on Hyper-V by following the recommendations described here. F5^® has certified throughput with these recommendations; however, they are not required for 1Gbps performance.

tmsh modify sys db scheduler.unicasleeprxlimit.ltm value 16

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 an SSH tool to connect to each of the BIG-IP VEs.
2. Ensure you are at the tmsh prompt.
   tmsh
3. On each BIG-IP VE, disable functionality that enforces single NIC setup.
   modify sys db provision.1nicautoconfig value disable
4. Confirm that the value was set correctly by typing list sys db provision.1nicautoconfig.
   The following text is returned: value "disable".
5. On each BIG-IP VE, specify the static private IP address of the BIG-IP VE itself.
   modify cm device <device_name> configsync-ip <private_ip_address>
6. Establish device trust: On one BIG-IP VE, enter the static private IP address of the other BIG-IP VE, along with its user name and password.
   modify cm trust-domain add-device { ca-device true device-ip <peer_ip_address> device-name <peer_device_name> username <peer_username> password <peer_password> }
7. On the same BIG-IP VE as the previous step, create a sync-failover device group with network failover disabled.
   create cm device-group <device_group_name> devices add { <all-bigip-device-names-separated-by-space> } type sync-failover auto-sync enabled network-failover disabled
8. Sync the BIG-IP VE to the other BIG-IP VE.
   run cm config-sync to-group <device_group_name>

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