Installing the ATP Appliance Appliance Virtual Core OVA
Juniper’s Advanced Threat Prevention extensible deployment options include a Virtual Core (vCore) detection engine product as an Open Virtual Appliance, or OVA, that runs as a virtual machine. Specifically, an OVA-packaged image is available for VMware Hypervisor for vSphere 6.5, 6.0, 5.5, and 5.0.
The OVF package consists of several files contained in a single directory with an OVF descriptor file that describes the Juniper ATP Appliance virtual machine template and package (metadata for the OVF package and a Juniper ATP Appliance software image). The directory is distributed as an OVA package (a tar archive file with the OVF directory inside).
Juniper generates an .ovf and a .vmdk file for every ATP Appliance build. Download both the OVF and the VMDK into the same directory. Then, from the vSphere client, click on File -> Deploy OVF Template. Choose the .ovf file and then complete the deployment of the ovf wizard. The configuration wizard prompts for collector/core properties such as IP address, hostname, device key. Log in to the CLI and configure each setting.
vCore Provisioning Requirements and Sizing Options
VM vCenter Version Support |
Recommended vCore ESXi Hardware |
vCore CPUs |
vCore Memory |
---|---|---|---|
VM vCenter Server Versions: 6.5, 6.0, 5.5, and 5.0 vSphere Client Versions: 6.5, 6.0, 5.5, and 5.0 ESXi version: 5.5.1, and 5.5 |
Processor speed 2.3-3.3 GHz As many physical CORES as virtual CPUs Hyperthreading: either enable or disable |
CPU Reservation: Default CPU Limit: Unlimited Hyperthreaded Core Sharing Mode: None (if Hyperthreading is enabled on the ESXi) |
Memory Reservation: Default Memory Limit: Unlimited |
Model |
Number of vCPUs |
Memory |
Disk Storage |
---|---|---|---|
v500M |
8 |
32 GB |
Disk 1: 512 G Disk 2: 1 TB |
v1G |
24 |
96 GB |
Disk 1: 512 G Disk 2: 2 TB |
Install the ATP Appliance OVA to a VM
To install the ATP Appliance Appliance OVA to a VM
Connect the power cable and power up the appliance.
When an OVA is cloned to a create another virtual Secondary Core, the value for column "id" in the Central Manager Appliance table is the same by default. Admins must reset the UUID to make it unique. A new Virtual Core CLI command “set id” is available to reset the UUID on a cloned Virtual Core from the CLI’s core mode. Refer to the Juniper ATP Appliance CLI Command Reference to review the Core mode "set id" and "show id" commands. Special characters used in CLI parameters must be enclosed in double quotation marks.