The following procedure is completed through the Azure classic deployment method. Additional configuration steps might be required for Azure Resource Manager deployments.

1. On your Linux client, open a terminal application and run the following commands.
   1. Install npm and node.js-legacy:

      sudo apt-get install npm nodejs-legacy

   2. Install the Azure command-line interface tools:

      sudo npm install -g azure-cli@0.9.7

      Note:

      Version 0.9.7 is not the most recent version of the Azure command-line tools. However, in order to upload VHD files to Azure, you must install the older version of the tool.

   3. Download your publish settings file from Azure:

      azure account download

      Your default browser automatically opens to http://go.microsoft.com/fwlink/?LinkId=254432
2. Sign into your Azure account.
3. Save the .publishsettings file to your computer.
4. Return to your terminal application and run the following commands:
   1. Import your publish settings file:

      azure account import <path_to_publishsettings_file>

   2. Create a boot image in the Azure blob storage location. The <azure-EXA5100v.vhd> file is uploaded to blob storage, and then the new virtual instance is created from this boot image.

      azure vm image create <boot_image_name> <path_to_extrahop.vhd> -o linux -u <storage_account_url>

      Where <boot_image_name> is the name of your boot image, <path_to_extrahop_extrahop.vhd> is the name of the ExtraHop VHD file on your local machine, and <storage_account_url> is the location of your storage account in Azure.

      For example:

      azure vm image create example-image /temp/azure-EXA5100v-5.1.0.983.vhd -o linux -u https://exstorage1.blob.core.windows.net/vm-images/example-vm.vhd

      Note:

      The VHD name in the URL (example-vm.vhd, in the example above) must be unique. If you try to overwrite an existing VHD file with the same name, this step will fail and you will need to repeat this step with a new VHD name.

   3. Create and start an Azure VM instance:

      azure vm create <vm_name> <boot_image_name> --ssh -z <instance_size> -l '<zone_name>' --userName user --password 'Ignored@Password1'

      Where <vm_name> is the name of your Explore VM, <boot_image_name> is the name of the boot image you created in step 4b, <instance_size> is the Azure instance size, and <zone_name> is your local time zone.

      Note:

      Choose an Azure instance size that most closely matches the Explore VM ( Basic_A4, Standard_A7, or Standard_DS13).

      For example:

      azure vm create example-vm example-image --ssh -z Basic_A4 -l 'West US' --userName user --password 'Ignored@Password1'

      Note:

      Azure requires that you specify a username and password to create and start the VM instance; however, the username and password are not required for the Discover virtual appliance.

   4. Create HTTP, HTTPS, and EXA endpoints. The HTTP and HTTPS Endpoints are required to direct the inbound network traffic to the Discover virtual appliance. The EXA endpoint enables Explore nodes to communicate with other Explore nodes in the same cluster.

      azure vm endpoint create -n HTTP <vm_name> 80 80

      azure vm endpoint create -n HTTPS <vm_name> 443 443

      azure vm endpoint create -n EXA <vm_name> 9443 9443