This section describes how to deploy two Central Management System virtual appliances (nodes) in Azure in a high availability (HA) cluster. It covers the following deployment options:
The two HA nodes are in the same Azure region.
The two HA nodes are in different Azure regions. Azure virtual network peering must be used for the nodes to communicate with each other.
Note
For comprehensive information about Central Management System HA features and operation, see the Central Management System High Availability Guide.
The procedures in this section assume that the IP addresses for the nodes are obtained from a DHCP server. Because a Central Management System HA cluster requires a static IP address for the default HA interface, you must assign a "dummy" static IP address for it. You must assign the "dummy" IP address before you do the initial configuration of the appliances; otherwise a DHCP release will be issued immediately. If you are using the second deployment option, you must configure virtual network peering before you assign the "dummy" IP address.
Task lists
The following table summarizes the tasks to perform for each deployment option.
Important
You must perform the tasks in the listed order.
Single Azure Region
Ensure that requirements are met. See Azure requirements.
Create the virtual machines. See Creating a Central Management System virtual machine.
Log in for the first time, change the "admin" password (if using password authentication), and accept the license agreement. See Logging in for the first time.
Assign a "dummy" static IP address to the ether1 interface. See Assigning a "dummy" static IP address.
Perform the initial configuration. See Performing the Central Management System HA initial configuration on Microsoft Azure.
Repeat steps 2—5 on the other node.
See the Central Management System High Availability Guide for information about monitoring, administering, and troubleshooting the HA cluster.
Different Azure Regions
Ensure that requirements are met. See Azure requirements.
Create the virtual machines. See Creating a Central Management System virtual machine.
Log in to the node for the first time, change the "admin" password (if using password authentication), and accept the license agreement. See Logging in for the first time.
Configure Azure virtual network peering to allow the nodes to communicate with each other. Configuring virtual network peering
Assign a "dummy" static IP address to the ether1 interface. See Assigning a "dummy" static IP address.
Perform the initial configuration. See Performing the Central Management System HA initial configuration on Microsoft Azure.
Repeat steps 2—6 on the other node.
See the Central Management System High Availability Guide for information about monitoring, administering, and troubleshooting the HA cluster.
Important
The navigation instructions and user interface may vary based on the Azure portal version that is running when you launch your instances. These procedures show only one way to navigate to resources in the Azure portal.
Note
This procedure covers the required settings for a virtual Trellix appliance deployed in a Central Management System HA cluster. You can accept the default values for the other settings, or specify values that are appropriate for your environment.
This document provides the basic steps for launching Trellix virtual appliances, and assumes familiarity with launching virtual machines in Azure. For comprehensive information, see the Azure documentation provided by Microsoft.