Hello! I am new to NABox. I just deployed it using the appliance, version 3.4. However, I have issues installing the NetApp Harvest 2. I downloaded "harvest-23.12.22-nightly_linux_amd64.tar.gz" and in the Maintenance page I tried to install it. The bar shows the installation and I get a message the installation was successful, but when I click OK on the message the installation bar goes in reverse and it seems the package is un-installing. Any help would be appreciated. Thank you!
#NetApp Harvest 2.x not Installing on NABox v.3.4
smoky vortex
remote geode
The progress bar going reverse can be confusing. But I just installed in and ot seems to be fine, what version does it lists on the right ?
smoky vortex
Thank you, Yann, for the answer. Harvest did installed. I don't know exactly when because I tried multiple times and rebooted the appliance, but eventually I was able to add one of my clusters and today opened the dashboards! This is my POC to show the management and then expand and add the rest of the clusters. The NABOX is on the same closed management subnet as the NetApp clusters. Is this preferable from security standpoint? Thanks again. The dashboards look great!
remote geode
Glad to hear ! It’s entirely up to you where to deploy nabox, security can always be managed. But from a performance perspective, as harvest does many api calls it’s always better to have it on the same physical location at least.
smoky vortex
So, if I have three data centers in different locations, I need to have three NABOX deployments?
junior cargo
not necessarily. you can have all the systems pointing back to the one deployment, as long as they can talk to it and necessary ports and such are open.
remote geode
The point I was making is if there is significant latency between the sites, and many clusters, the 1min refresh interval might be too short to collect everything
So if we're talking about a couple of clusters on the remote location, it's probably fine to do it over WAN, but be mindful of the latency as Harvest might be doing thousands of API calls