After reading the blog article by Erik Bussink on how to use the VSAN Observer software on a Windows vCenter Server, I quickly got annoyed by manually having to start the Ruby rvc script and the VSAN Observer every time
I created a little batch file that can be put on your desktop to launch the VSAN Observer
Just enter your credentials, vCenter server Name, Datacenter Name and Cluster Name and make sure the path to the rvc directory is correct, and of you go
After you started VSAN Observer, just connect to it via port 8010 on your vCenter Server, or add an exception for port 8010 in your Windows firewall to access VSAN Observer remotely, like described in Eriks’ blog
I saw ur post on Vmware virtual san observer here and used ur script.
I am trying to connect to my windows based vcenter server(running vsan cluster) from a secondary vcenter server appliance, that has been created dedicatedly for this purpose. I run the vsan.observer command using that, the command keeps running and loads infor. for 2 hours, but nothing comes up if I try to connect to 8010 port on the vcenter server.
I read in a post that it might be due to nokogiri -v 1.5.6. My vcenter server is on windows server 2008 R2 datacenter(http://vinfrastructure.it/2014/05/vmware-virtual-san-observer/)
When I try running this command directly on vcenter server by navigating to the rvc folder in programfiles amd running the RVC command, I am unable to navigate to the Cluster, I get this error: RuntimeError: unknown VMODL type AnyType
Now I just upgraded my vcenter server to 5.5 U1b from 5.5 U 1a, still the issue persists and even after successful start of the webserver, nothing comes up on 8010 port. It is mentioned in release notes of 5.5 U1b that this issue for unable to navigate has been fixed in this release.
I would be highly obliged for your help and patience. Please help me.
Rizul Khanna(email@example.com, India)
Whoa, I just found this small Jewel on your site. Thanks for creating this ‘simple’ yet very elegant script. If you run into issues due to the OpenSSL Certificate and Time errors like
OpenSSL::X509::CertificateError: error getting time”
then you can just add the –no-https at the near end of the script like
–run-webserver –force –no-https’ %admin%@%vCenter%
Thanks for commenting up! The –no-https option did it for me.
No-https worked for me as well, thanks!