I suspect a network setup issue. The installation instructions for 8.2.1 for VMwrkstn say to use VMnet8 and also to use it's IP address as assigned (displayed via ipconfig) for cluster mgt and to ignore the gateway request; the gateway request can't be ignored so I used the same address. The Cluster appears to be up and a "net int show" displays the VMnet8 address for cluster_mgmt. I was also able to join in a 2nd controller.
I provided the Cluster Mgt (VMnet8) IP address and credentials to the "add" function in OnCmd and after a few seconds, the box line around the address turns red and a hover produces "500 Connection Refused".
What is the output of net int show? What is the VMNet8 address/gateway/subnet? What is the output of ipconfig of the host with the VM? And, what is the output of ipconfig/ifconfig of the client you have OnCommand System Manager on?
As I suspected from the start, the network setup was a little off. Setting all adapters to VMnet8, using VMnet8's IP as the gateway, and VMnet8's subnet did the trick. All of the other potential areas were set OK (httpd.admin.enable was on). It would be helpful if someone did a small writeup that simplified setup of the VM simulator's network adapters. The 8.2 and 8.2.1 instructions were a little different and basically said that the adapters needed to be configured but didn't specifically say how.
I have recently encountered all kinds of problem after my W7 workstation was patched with MS security updates and java 8 (java is nasty, isn't it?) regarding to NetApp SystemManager 3.1.2 (SM312).
First, the error is "500 Connection Refused"", then "HTTP XML Authentication failed from x.x.x.x (DFM server) on Netapp controller", and last the KS file corruption.
I tried to remove java 8, then remove and re-install Java (jre-7u65) and SM312; did not work.
Of course, you have to install jre-7u65 and SM.
Next, recovere the SM.config file from C:\Users\myusername\NetApp\SystemManager using SMBackup.config, simply deleted the SM.config file then recreate the file using backup (you know how to do this, don't yuo?); deleted the KS file. This restored my previous connections to my filers, great, one step closer.
Next, putty to the filers (controllers) and run this command: "options tls.enable on", bingo, my SM back to work.
Fixed... don't bother with the Java fiasco. Mind you, every time I have a java dependant device, I always have problems; they should stop using the platform all together and use something else, such as .NET
Thank you for All your help lwangnetapp. I've been hitting head against the wall for a while.