Solved!
Go to SolutionMUMC and VCenter Plugin
Hello everyone,
To make it quick:
We recently changed the whole infrastructure, including a new UPS: (1920w) http://www.dellups.com/solutionUSS_list.asp?SOLID=793120&ResellerIDCode=1 .
We've got a VMware Essential Plus edition (with a Vcenter) and wanted to use the MUMC to manage the correct shutdown of VMs and ESX hosts.
MUMC is installed on the same VM as the Vcenter, windows firewall is disabled (Vcenter default ports are used).
The main problem is when we add the Vcenter to the virtualization module (tried login with domain\user or user@domain).
We can see this error in the log file:
| Type : | Error |
| Module : | VMwareWebService |
| Message : | Error on the VMware connection process |
| Détails : | Host'Vcenter.xxx.lan': Session is not authenticated. |
The Vcenter plugin has never showed up in the Vcenter.
Any great idea how to solve this will be welcomed.. we didn't find any suggestion or detail concerning this error.
(I can give more details if it can help)
Dell says this is a known issue with VMware Vcenter 5.1 and AD integration This is correct. I received a response from one of our escalation groups and was informed that MUMC will not function when AD is enabled in 5.1. There are plans to make MUMC compatible with the new AD functionality of 5.1, but at this time it is just in the planning stages and there is no ETA of when it will be compatible.
I was informed that ULNM will work with AD enabled, and MUMC will work if AD is disabled.
Thanks
Hello a.giraud
I would suggest reviewing this setup document. The first thing that comes to mind is whether or not Vcenter is installed on port 443. MUMC will only communicate to Vcenter via port 443. The other thing to keep in mind is that only network management is supported through virtualization. You will need the network management card installed in the UPS.
http://www.dellups.com/pdf/Dell-TIN-UPS003_VMware_vCenter_Shutdown_Scenarios-10-11-12.pdf
If the document does not help resolve your issues let us know.
Thanks
What version of VMware are you using, and what OS is installed on this VM?
Add the user account or create a new user account and add it to the ESX Admins group. Make sure the account has full access. Test with that account and see if it has authentication issues.
http://blogs.vmware.com/vsphere/2012/09/joining-vsphere-hosts-to-active-directory.html
I'll continue researching the issue on my end. Let me know the outcome of the elevated user account.
Thanks
Welcome back,
We're using Vsphere 5.1.0 799731 on Vcenter and 5.1.0 838463 on ESXi Hosts.
VCenter is on a Windows Server 2008 R2 Datacenter SP1.
I followed your link to add each users/group to the Vcenter/hosts (ESX Admins, admin & admin group of my domain) and rebooted my VCenter.
We didn't reboot the ESX hosts since the syslog file doesn't show anymore this message :
nssquery: Group lookup failed for ' \ESX Admins
The error keeps happening.
seanpattee
1 Message
2111
1
Posted November 26th, 2012 09:00
A.Giraud,
I am having this same issue using VCenter 5.1 and I am running the Dell MUMC software on a Windows Server 2008 RC2 VM.
After struggling for 2 days I finally called both VMware and Dell technical support. Dell says this is a known issue with VMware Vcenter 5.1 and AD integration. They are currently working on a solution to this issue. If anyone else has gotten the MUMC software to work with VCenter 5.1please chime in because as it now stands there is allegedly no work around known to Dell.