For the complete documentation index, see llms.txt. This page is also available as Markdown.

Brain deployment in Nutanix

How to download the Nutanix Brain image and deploy it within Nutanix.

Downloading the Latest Nutanix Brain Files

The current Nutanix Brain files (.zip containing .ova and python deployment script) can be downloaded from the Vectra Customer Support Portal after logging in.

  • Click on the Download tab.

  • Click on the Nutanix Brain Files and the the File: Download link.

    • A SHA256 hash is also provided to allow you to verify the download completed successfully.

Always download a current copy when you go to deploy a new Nutanix Brain for your organization. This will save time during deployment as fewer updates will need to be downloaded after deployment. Make this file available via the local file system where you will run Prism Central client from.

Uploading the OVA Image to Prism Central

  • After downloading the .zip file from the Vectra support portal, unzip it using the tool of your choice.

    • Save the python script to the location of your choice. The location must have reachability to your Prism Central v3 APIs.

  • Upload the .ova file to your OVA store in Prism Central.

    • Navigate to Infrastructure → Compute → OVAs.

    • Click Upload OVA and fill out the dialog.

      • Choose your AHV cluster.

      • Pick a name for the OVA. This will be used later selecting the image with the deployment script.

      • The Checksum file is not required as the OVA will automatically be verified by Nutanix based on information included in the OVA file.

      • Choose your file and click Upload.

    • It will take a few minutes to upload the OVA and then Prism Central will perform validation of the OVA.

    • You can check the status of these tasks in the All Tasks as seen below:

  • When the validation has completed, you can move on to deployment.

Please choose one of the following two deployment methods for the OVA:

Script Guidance

  • If you would like to pass all arguments to the script instead of running interactively, it is supported.

  • Interactive deployment is recommended because the script will display options for the cluster, OVA image, and subnet names or UUIDs and you will not need to look them up elsewhere.

  • The URL can include a trailing / or it can be left off, both formats will work but you should include the full URL including port, and not just the hostname.

  • After the last question is answered or if all arguments were passed to script for a non-interactive deployment, the execution is nearly instantaneous.

    • You can then find the VM in Prism Central at Infrastructure → Compute → VMs.

  • When choosing static IP addressing, additional questions will be asked during the script execution to capture the static IP details.

Please Note:

Per the Nutanix Brain Resource Requirements and Throughput section, Vectra plans to make additional configurations available in the future.

  • Initially, only the 32 core Brain is supported.

  • Once available, the 4 and 6 core Respond UX specific configuration can only be used in Respond UX deployments. They are NOT supported for Quadrant UX deployments.

  • RespondUX – Choose this option if you are doing a Respond UX for Network deployment.

    • When this option is selected, the Brain will boot directly into a state that is ready to be linked to the Vectra Cloud for use with the Respond UX. There will be no local Quadrant UX GUI served as there normally would be for a standard Nutanix Brain deployment before it is linked with Vectra for use with the Respond UX. Vectra personnel will still need to link your Brain to your Respond UX tenant to complete your deployment.

    • This option should be selected for any Respond UX for Network deployment. i.e. You still need to pick this option even if you previously chose the 6CORE_RespondUX configuration.

Running the Script

  • The python deployment script can be run from any location that has reachability to your Prism Central APIs.

    • Your python interpreter must be v3.7 or higher.

    • Please see below for a sample interactive run using DHCP

      • Lines requiring user input are highlighted below:

  • Help is available if you use the --help argument when running the script:

Deploying the OVA Manually (Alternate Method)

  • Select the check box next to the OVA you uploaded and choose Actions → Deploy as VM.

    • Follow the instructions below for each screen.

    • The OVA should be visible in Infrastructure → Compute → OVAs in Prism Central.

  • A dialog will open with Configuration, Resources, Management, and Review panes.

1

Configuration

  • Set Name and Description as desired.

  • Choose the Cluster you wish to deploy on.

  • Under VM Properties, set the CPUs and Memory to one of the following configurations.

    • In all cases, set Cores Per CPU to 1:

    • 4 CPUs / 48GiB RAM (Respond UX ONLY) – Coming soon, do NOT use until Vectra approved by Vectra!

    • 6 CPUs / 48GiB RAM (Respond UX ONLY) – Coming soon, do NOT use until approved by Vectra!

    • 8 CPUs / 64GiB RAM – Coming soon, do NOT use until approved by Vectra!

    • 16 CPUs / 128GiB RAM – Coming soon, do NOT use until approved by Vectra!

    • 32 CPUs / 256GiB RAM - Only supported choice at initial launch of Nutanix Brain.

  • Under Advanced Settings, do NOT enable Memory Overcommit.

2

Resources

  • Do NOT change Disks, Boot Configuration, or Shield VM Security Settings!

  • Select the edit (pencil) icon next to the NIC and configure it.

    • Choose the desired subnet.

    • For Network Connection State, choose Connected.

    • For NIC Configuration, choose Access and then Save your NIC configuration.

3

Management

  • Default-Storage policy can be enabled if this is your standard.

    • If performance testing (in Post Deployment Guidance) indicates too low of a disk throughput, you may need to alter or remove the policy later if the policy is the reason for the lower performance.

  • Categories are NOT required.

  • Timezone must be set to UTC.

    • Timezone can later be set in your Vectra UI if you desire to have a different timezone.

  • Check Use this VM as an Agent VM if you want the Brain to boot before all other VMs.

    • This is not required, but is supported if desired.

  • Under Guest Customization, choose Script Type: Cloud-init (Linux) and Configuration Method: Custom Script

  • Add your configuration to the template below and paste it into the Startup Script box.

    • You can download the script below or copy it from the code block.

4

Review

  • Review your configuration, make changes if required, and when ready, click Create VM.

  • After creation, you can then find the VM in Prism Central at Infrastructure → Compute → VMs.

Last updated

Was this helpful?