Installation

Requirements

Product	Versions
Web Browser	Safari 14+, Google Chrome 92+, Firefox 91, Edge 94
vSphere	vCenter & ESX 6.5
ONTAP	NetApp Harvest is compatible with recent and old versions of ONTAP. Regarding 7-mode, it is recommended to run the last available release to avoid deprecated versions of TLS

Compute Resources

NAbox will require more or less resources depending on the amount of systems (and objects) under monitoring.

Size	Controllers	vCPU	Memory	Disk
Small	< 10	4	6 GB	30 GB
Medium	< 50	8	12 GB	300 GB
Large	< 200	8	24 GB	1 TB

Attention

Please take these numbers as a loose recommendation and test drive in your envionment, if you find this does not work for you please contact us.

Networking

NAbox uses the following ports that needs to be open on your firewall.

Workstation designates the computer used to run the web browser to access NAbox components.

Source	Destination	Port	Protocol	Role
Web Browser	NAbox	443	TCP	Web interface
Web Browser	NAbox	22	TCP	SSH for troubleshooting and maintenance
NAbox	NetApp systems	443	TCP	HTTPS for data collection
NAbox	LDAP / AD server	389 or 636	TCP	LDAP(s) Grafana user authentication
NAbox	support.netapp.com, or 216.240.21.18	443	TCP	Optional, Autosupport
NAbox 3	NAbox 4	443	TCP	Optional, to migrate data from NAbox 3 to NAbox 4

Installing NAbox

There is a few steps to get the virtual appliance up and running :

Deploy the virtual machine,
Configure your systems in NAbox
Go on with your day

Deploying the OVA

Point your browser to your vSphere Web Client, and use the Deploy OVF Template feature.

“Deploy OVF Template” contextual menu.

You can deploy use the "Local File" option, or use a URL if you have NAbox available in a central repository.

You cannot use NAbox download link to install directly from the web site.

Deploy OVF Template window.

Choose a name and a folder where you want to deploy NAbox

Deployment location.

Choose the compute resource in which you want to deploy NAbox

Compute resource selection

Review OVA details

OVA details

Choose a datastore to deploy NAbox. You can deploy NAbox on NFS or VMFS datastores.

Datastore selection

Choose the network on which NAbox should be connected. On first boot, NAbox will get its IP address automatically from the network unless specified otherwise on the next screen.

Network selection

You can deploy NAbox with a static IP address by filling out the network settings.

If you leave everything by default (blank) then DHCP will be used.

IP address notation

Note that IP address must be in the form a.b.c.d/m with the netask bits after /

Network Parameters

Check parameters and accept the deployment settings

Deployment summary

Wait for the deployment to finish and boot the appliance.

Once booted, you can find out the IP address of NAbox from the Virtual Machine Summary page.

VM summary

It takes a few minutes for NAbox to finish configuration, then the web site will be available.

Proxmox deployment

To deploy NAbox on Proxmox, you need to create a disk-less VM first, and then import qcow2 image from a Proxmox server CLI.

Creating a new disk-less VM

In Proxmox, create a new VM

Click Next

Create Virtual Machine - General

Check Do not use any media

Click Next

Create Virtual Machine - OS

Leave defaults for System tab

Click Next

Create Virtual Machine - System

By default, Proxmox creates a boot disk, make sure you remove it here

Click Next

Create Virtual Machine - Disks

Assign desired CPU according to Requirements

Click Next

Create Virtual Machine - CPU

Assign desired Memory according to Requirements

Click Next

Create Virtual Machine - Memory

Assign appropriate network interfaces

Click Next

Create Virtual Machine - Network

Confirm settings

Click Next

VM summary

Once the VM is provisioned, take note of its vmid.

Import qcow2 file

Using SSH or another transfer protocol, copy NAbox qcow2 file to Proxmox and attach the imported disk to the VM

id=<vm_id>
storage=<storage_name>
qm importdisk $id /root/NAbox-4.1.0.qcow2 $storage
Use of uninitialized value $dev in hash element at /usr/share/perl5/PVE/QemuServer/Drive.pm line 555.
importing disk '/root/NAbox-4.1.0.qcow2' to VM 137 ...
Formatting '/mnt/pve/nfs1/images/137/vm-137-disk-0.raw', fmt=raw size=9116319744 preallocation=off
transferred 0.0 B of 8.5 GiB (0.00%)
[...]
transferred 8.5 GiB of 8.5 GiB (100.00%)
unused0: successfully imported disk 'nfs1:137/vm-137-disk-0.raw'

Double click on the unused disk that we just attached to the VM

VM Hardware - Unused Disk

Add it as SCSI0

Add: Unused disk

Double click Boot order in Options

Options - Boot Order

Change boot order to "scsi0" only

Edit: Boot order

Attach an additional data disk

Hardware - Add Disk

Select "Add" > "Hard Disk"

Add: Hard Disk

Add a 200GB data disk

Finished !

You can now start NAbox, wait for the IP address to be visible in Summary, and continue configuration using a web browser.

Note that by default, NAbox gets IP address with DHCP. If you do not have a DHCP server, you can follow the instructions to manually configure IP