If you like to locate all your vcenter add-ons in one location, you may notice this is problematic. The NetApp VASA Provider 1.0 is no exception. By default, the VASA provider listens on TCP/8443. Bad move, NetApp.
Unlike everyone else who says just to install it somewhere else, I leveraged my extremely stubborn streak and discovered if you modify the port number in this file, and start the service - it works flawlessly:
%programfiles%\netapp\vasa\config\vasa.properties
I changed the following line to port 8444 (from 8443)
https.port=8444
If vCenter is already running and you installed the VASA provider - the VASA provider won't start until you make this change. or reboot :) And then you'll get this:
The VMware VirtualCenter Management Webservices service terminated unexpectedly. It has done this 6 million time(s).
Enjoy!
Subscribe to:
Post Comments (Atom)
Featured Post
Remove 3D Objects and other annoying folders on Windows 10
Microsoft just keeps adding more crap to clutter up the navigation in Windows 10. Seriously, who needs a 3D Objects folder? The tiny perc...
-
Sometimes a VM snapshot can get corrupted. You can check for consistency by running vmkfstools against the last snapshot in the chain for a...
-
I recently deployed a new UCS blade, and I was greeted with the error: " configuration failed due to compute-unavailable,insufficient...
-
So I updated to Windows 8.1 because I figured it's been out long enough and the vendors got the driver issues fixed...apparently not! ...
No comments:
Post a Comment