Enable a 10 Gb Interface (Optional)

Follow one of the two procedures below depending on whether you are adding a single network interface or multiple network interfaces to the LoadMasterMOVEit WAF.

To enable 10 Gb throughput for a LoadMasterMOVEit WAF virtual machine (VM) in Azure, you must select an Azure VM instance type that supports the 10 Gb Mellanox driver. Accelerated Networking is supported on most general purpose and compute-optimized instance sizes with two or more vCPUs. These supported series are: D/DSv2 and F/Fs. On instances that support hyperthreading, Accelerated Networking is supported on VM instances with four or more vCPUs. Supported series are: D/Dsv3, E/Esv3, Fsv2, Lsv2, Ms/Mms and Ms/Mmsv2. Refer to the Sizes for Linux virtual machines in Azure page for further details.

Add a Single Interface to the LoadMasterMOVEit WAF

To enable 10 Gb interfaces on the LoadMasterMOVEit WAF, perform the following steps:

1. Deploy the LoadMasterMOVEit WAF.
   Note: When you instantiate a 10 Gb interface, it appears as two interfaces in the LoadMasterMOVEit WAF Web User Interface (WUI). The two interfaces are related and have the same MAC address. Only the first interface has an IP address. If you want to modify the interface, you must do this on the interface that has the IP address listed.
   Note: For the purposes of this document, the Standard DSv2 machine size is used.
2. License and log into the LoadMasterMOVEit WAF.
3. Navigate to System Configuration > System Administration > System Reboot.
4. Click Shutdown.
5. In the Azure Portal, navigate to the LoadMasterMOVEit WAF Virtual Machine and click Stop.
6. In the Azure Portal, navigate to the Network Interface associated with the LoadMasterMOVEit WAF Virtual Machine.
7. Click Edit accelerated networking.
8. Click Enabled and select the validation box.
9. Click Save.
10. In the Azure Portal, navigate back to the LoadMasterMOVEit WAF Virtual Machine and click Start.
11. Log into the LoadMasterMOVEit WAF and verify that the Mellanox driver has instantiated correctly by performing the following steps:
    1. If the LoadMasterMOVEit WAF was deployed with a single interface, two interfaces are displayed under System Configuration > Interfaces on the LoadMasterMOVEit WAF WUI. If only one interface is displayed this means that the Mellanox driver has not instantiated.

       

    2. You can also verify that two interfaces are active by checking performing an Ifconfig. To perform an Ifconfig, navigate to System Configuration > Troubleshooting. On the Troubleshooting screen, click Ifconfig. This displays two interfaces with the same hardware address.

Add Multiple Interfaces to the LoadMasterMOVEit WAF

The Azure WUI does not allow interfaces with accelerated networking to be added. You must add the interface by using the Azure command line interface (CLI) or by using PowerShell.

1. Create the interface using the Azure CLI similarly to the example below:

   PS C:\Users\test> az network nic create --resource-group testdoc --name myNic2 --vnet-name myVnet --subnet subnet2 --accelerated-networking true --public-ip-address myPublicIp2 --network-security-group myNetworkSecurityGroup --location eastus

2. When the interface is created, you can add this interface to the LoadMasterMOVEit WAF when it is in a powered off state. Navigate to the Networking tab of the LoadMasterMOVEit WAF on the Azure WUI.

   

3. Click Attach network interface.

   

4. When the attachment is complete, both interfaces appear on the Azure WUI.
5. Restart the LoadMasterMOVEit WAF.
6. Verify that the interfaces are displayed under System Configuration > Interfaces on the LoadMasterMOVEit WAF WUI. The LoadMasterMOVEit WAF WUI should now display four interfaces.

You can also verify that four interfaces are active by checking performing an Ifconfig. To perform an Ifconfig, navigate to System Configuration > Troubleshooting. On the Troubleshooting screen, click Ifconfig.

Unlike the single interface case where eth0 and eth1 are related, for multiple interfaces, eth0 and eth2 and eth1 and eth3 are related (with the same MAC address). eth0 and eth1 have the IP addresses, the other interfaces without the IP addresses are related by the HWaddr (the MAC address).