Foglight for Virtualization Enterprise Edition 8.9.3 - Azure Virtual Machine Deployment Guide

Deploying and Monitoring Virtual Appliance

This guide provides instructions for deploying and monitoring the Foglight™ for Virtualization, Enterprise Edition appliance on Microsoft Azure (hereafter called Foglight-FVE-Azure-vApp).

For more information, see the following topics:

•

Deploying virtual machine through Azure portal

•

Accessing Management Server console

•

Creating monitored agent

Deploying virtual machine through Azure portal

Before monitoring the Foglight-FVE-Azure-vApp, make sure to deploy your virtual machine on Microsoft Azure.

To deploy the virtual machine through the Azure portal:

Log into the Azure portal.

On the left navigation panel, select New.

The New MARKETPLACE view opens.

In the New MARKETPLACE view, type “foglight for virtualization” in the search box, and then select Foglight for Virtualization, Enterprise Edition from the search result.

The Foglight for Virtualization, Enterprise Edition view opens.

In the Foglight for Virtualization, Enterprise Edition view, click Create.

The Create virtual machine view opens.

In the Basics step, specify the following information, and then click OK.

•

Name (mandatory): Specify the name of the virtual machine.

•

VM disk type: Indicate the disk type of the virtual machine. Quest recommends selecting SSD for this field.

•

SSD: Premium disks (SSD) are backed by solid state drives and offer consistent, low-latency performance. They provide the best balance between price and performance, and are ideal for I/O-intensive applications and production workloads.

•

HDD: Standard disks (HDD) are backed by magnetic drives and are preferable for applications where data is accessed infrequently.

•

Password (mandatory): Specify the password of the virtual machine.

•

Confirm password (mandatory): Type your password again.

•

Subscription: Select your subscription from the drop-down list.

•

Resource group (mandatory): A resource group is a collection of resources that share the same lifecycle, permissions, and policies. Do either of the following:

•

Select Create new, and then specify the name of this new resource group.

•

Select Use existing, and then select an existing resource group from the drop-down list.

•

Location: Indicate in which the virtual machine is located.

In the Size step, select any of the following, and then click Select.

•

DS11_V2: Select this option for an environment that includes less than 1000 VMs.

•

DS12_V2: Select this option for an environment that includes less than 3000 VMs.

•

DS13_V2: Select this option for an environment that includes more than 3000 VMs.

In the Settings step, specify the following information, and then click OK.

•

Storage: Enable this feature to have Azure automatically manage the availability of disks to provide data redundancy and fault tolerance, without creating and managing storage accounts on your own.

•

Storage account (available for non-managed disks only): Disks for Azure virtual machines are created in storage accounts. Create a new storage account or select an existing account.

•

Network:

•

Virtual network (mandatory): Virtual networks are logically isolated from each other in Azure. You can create a new virtual network or select an existing one. Virtual machines in the same virtual network can access each other by default.

•

Subnet (mandatory): A subnet is a range of IP addresses in your virtual network, which can be used to isolate virtual machines from each other or from the Internet.

•

Public IP address (mandatory): Use a public IP address if you want to communicate with the virtual machine from outside the virtual network.

To create a new public IP address, specify the name of IP address, select dynamic or static alignment, and then click OK.

•

Network security group (firewall) (mandatory): A network security group is a set of firewall rules that control traffic to and from your virtual machine.


	NOTE: Ensure that HTTP (TCP/80) and HTTPS(TCP/443) ports in the Inbound rules area are enabled.

•

Extensions: Add new features, like configuration management or anti-virus protection, to your virtual machine using extensions.

•

Availability set (mandatory): To provide redundancy to your application, we recommend that you group two or more virtual machines in an availability set.

•

Boot diagnostics: Enable this feature to capture serial console output and screenshots of the virtual machine running on a host to help diagnose startup issue.

•

Guest OS diagnostics: Enable this feature to get metrics every minute for your virtual machine. You can use them to create alerts and stay informed on your application.

•

Diagnostics storage account (mandatory): Metrics are written to a storage account so you can analyze them with your own tools.

In the Purchase step, review the summarized information, and then click Purchase.

The virtual machine is now being deployed on Microsoft Azure.