#harvest-nabox : basic setup failure

1 messages · Page 1 of 1 (latest)

lunar bluff
#

Hi everyone.

I’m having very basic setup problems, and am maybe missing something obvious.

  1. We have deployed the 3.2 nabox, to monitor a 7-mode 8.2.3 metro cluster.
  2. The deployment runs as expected with no errors, and the NAbox is accessible from the network.

When I go to the SYSTEMS page to input the storage details it returns an error each time “an error occurred”

Using IP or host name and deliberately setting username/password incorrectly results in the same error.

I’ve looked on the nabox-harvest2 docker, there are two harvest.yml files ( /net app-harvest/harvest.yml and /conf/harvest.yml) neither seems to have had entries added for the parameters I have supplied.

When I attempt to refresh the details I can see new lines in in nabox-harvest2 log (via dc logs -f — tail nabox-harvest2) that read

Netapp api error reason url error (sslerror sslv3 handshake alert handshake failure)

I’m not trying to use the system with certificates, just username and password.

The netapp options “tls.enable on” and “ssl.enable on” “ssl.v2.enable on” “ssl.v3.enable on” “httpd.admin.ssl.enable on” “httpd.admin.access legacy” “httpd.admin.hostsequiv.enable off”

Any thoughts or advice would be gratefully received
Zach

tame gulch
#

hi @lunar bluff @nova nebula can shed more light on the nabox questions. Your 7-mode handshake issue may be related to old TLS version on that filer. Can you confirm that the poller in question has use_insecure_tls: true and maybe try setting tls_min_version https://github.com/NetApp/harvest/issues/1007#issuecomment-1404067132

That issue also includes a curl command you can try to confirm there are no issues talking to the filer

GitHub

Started seeing harvest failures on 7mode filers. Any idea about this issue? Is it TLS version issue? I'm not aware of any TLS update on 7mode systems. {"level":"warn","...