The following table summarizes the methods you can use to deploy a Network Security appliance (known as a virtual machine) in Microsoft Azure.
The first and second methods use an Azure Resource Manager (ARM) template to quickly deploy a Network Security virtual machine. You define the resources for the virtual machine by entering values in an Azure ARM template. The template methods offer more flexibility and require fewer steps. The third method uses the image available in the Private Products Listing in Marketplace to deploy the virtual machine.
Method | Description |
|---|---|
Private products in Marketplace | Uses the ARM template listing available at Private Products in Marketplace to open a custom user interface to create a virtual machine with four network interfaces and associated resources. You can optionally create and attach two additional network interfaces if your instance size supports six interfaces. A new or empty resource group must be used to comply with Azure Marketplace restrictions at the time of this writing. See Deploying a virtual machine using the Azure ARM template in marketplace. |
Standalone ARM template | Uses a standalone ARM template downloaded from the Trellix Customer Support site to open a custom user interface to create a virtual machine with the minimum requirement of four network interfaces and associated resources. You can optionally create and attach two additional network interfaces if your instance size supports six interfaces. A new or existing resource group must be used. See Creating the virtual machine using the standalone Azure ARM template. |
Private products in Marketplace | Uses the Private Products listing in Marketplace to open the default Azure user interface to create a virtual machine with a single network interface. An existing or new resource group can be used. You must create and attach three additional network interfaces for proper functioning. You can optionally create and attach two additional network interfaces if your instance size supports six interfaces. See Deploying a Network Security virtual machine using the private products listing in marketplace. |
Note
This document provides the basic steps for launching virtual Trellix appliances, and assumes familiarity with launching virtual machines in Azure. For comprehensive information, see the Azure documentation provided by Microsoft.
Network interfaces are placed in the following VRF namespaces:
ether1, ether2—vrf0
pether3, pether4—vrfA
pether5, pether6—vrfB
pether7, pether8—vrfC
pether9, pether10—vrfD
For details about virtual routing and forwarding (VRF), see the "Layer 3 Forwarding Using VRF Instances" information in the Network Security System Administration Guide