Chris Weldon bio photo

Chris Weldon

A savvy software engineer and agilist, Chris slings code in C#, but has also been known for commanding fleets of systems. He's currently a Tech Lead at Wolters Kluwer.

Email Twitter Facebook Github

As I was looking for ways to better interact with our NetApp FAS2050, I came across an article detailing the Virtual Storage Console. Being intrigued, I decided to install it on our vCenter Server. The install went fine and the application registered fine per documentation. However, the problem came when entering the credentials under the NetApp tab. I was stuck in an infinite loop that stated SSL is not configured.. No matter what I did (whether that was use the root user, the vcenter user I created, checking or unchecking Use SSL, I got the same error message - SSL is not configured.

This was despite installing the software per the Installing NetApp VSC According to Best Practices. SSHv2 and SSL were enabled when executing secureadmin status. Furthermore, httpd.admin.enable was on using legacy access.

I went Googling for the solution to the problem, and came across an old Nabble list scrape that said to put the IP addresses of all of my ESX hosts in /etc/hosts.equiv and turn on httpd.admin.hostsequiv.enable. Sadly, that didn’t work. Yet, further Googling revealed something painfully obvious. If you’ve ever tried accessing your filer via HTTPS (e.g. https://filer/na_admin/) and you were not listed in the trusted.hosts, then you’re flat out denied access. That’s exactly what was going on here. The VSC requires access to the APIs provided through the same console, and thus requires you to manually list all the IP addresses of the ESX servers in the trusted.hosts file.

In Summary

Make sure all of your ESX hosts (and vCenter server) are listed in the options trusted.hosts.