Unsolved
This post is more than 5 years old
15 Posts
0
35442
April 25th, 2011 09:00
Dell Management Plugin Configuation Wizard fails
I've installed the VMware Management Appliance v1.0.0.40 on ESXi 4.1 host and then hit the following issues.
I regularly use the vSphere Client 4.1 on Windows 7 SP1 against our vCentre 4.1 on Server 2008 R2 using AD credentials that have Adminsitrator priveleges on vCenter.
1. When using the MA Administration Console to register the vCenter it will only accept the AD credentials that my vSphere client runs as: registration fails with other AD accounts that have Admin priveleges on vCenter.
2. So I register with my AD credentials and the Extensions are loaded into vCenter - I check with https:///mob - and the Plugin ispicked up by my vSphere client.
3. In vSphere attempt to load the plugin - usually works 2 o outo f 3 times :-(
4. I run the Connection Profile Wizard and it fails with:
"Severity: CRITICAL
Error Code: 1050
Time (Appliance server time): 2011-04-25T16:13:22.849+01:00
Details: There are either too many Virtual Management Console connections, an incorrect user name or password or session ID, or an incorrect SSL certificate. Please verify these items and try again."
Now there are not too many console connections, the username and password is OK and the SSL certificate is installed on my local certificate store.
I have not been able to find a simple architectural diagram of the MA and its relationship to vSpere and vCenter and what ports and protocols are in use between them. I'm assuming 443 TCP (HTTPS) but this does not explain the issue with the AD credentials and the MA.
Can anyone fill in some of the gaps here then maybe I can figure out what is goig on
Thanks
john
I regularly use the vSphere Client 4.1 on Windows 7 SP1 against our vCentre 4.1 on Server 2008 R2 using AD credentials that have Adminsitrator priveleges on vCenter.
1. When using the MA Administration Console to register the vCenter it will only accept the AD credentials that my vSphere client runs as: registration fails with other AD accounts that have Admin priveleges on vCenter.
2. So I register with my AD credentials and the Extensions are loaded into vCenter - I check with https:///mob - and the Plugin ispicked up by my vSphere client.
3. In vSphere attempt to load the plugin - usually works 2 o outo f 3 times :-(
4. I run the Connection Profile Wizard and it fails with:
"Severity: CRITICAL
Error Code: 1050
Time (Appliance server time): 2011-04-25T16:13:22.849+01:00
Details: There are either too many Virtual Management Console connections, an incorrect user name or password or session ID, or an incorrect SSL certificate. Please verify these items and try again."
Now there are not too many console connections, the username and password is OK and the SSL certificate is installed on my local certificate store.
I have not been able to find a simple architectural diagram of the MA and its relationship to vSpere and vCenter and what ports and protocols are in use between them. I'm assuming 443 TCP (HTTPS) but this does not explain the issue with the AD credentials and the MA.
Can anyone fill in some of the gaps here then maybe I can figure out what is goig on
Thanks
john
No Events found!
Kong Yang
180 Posts
0
April 26th, 2011 15:00
Let me ask the PG Engineering team. I will post their response as soon as I get it.
Regards,
KongY
kickmaleerie
15 Posts
0
April 27th, 2011 05:00
Appreciated.
I've resolved this by moving the appliance to the same VLAN as the vCenter instance server so that we don't have any firewall issues: we run FWSM on our routers.
I can confirm the issue with the credentials: vCenter instances can be registered via the Management Console OK using a local account in the Administrators group on the 2008 R2 server running the vCenter instance. I can also register with an AD account that is in the same AD domain as the 2008 R2 server hosting the vCenter. Of course both accounts have Administrator priveleges grnated in vCenter.
Registration fails whenever I try to use an account in the other domain in our AD forest that has admin privleges on both the 2008 R2 server and vCenter.
Unambiguous documentation on as to what protocols and ports are used between the Dell Plugin Appliance, the vSphere client and vCenter would be very useful.
Thanks
john
kickmaleerie
15 Posts
0
April 27th, 2011 07:00
162 & 11620 - For SNMP trap listener
Now as far as I am aware SNMP traps are sent over UDP 162 i.e. the plugin appliance only needs to allow UDP 162 inbound from the ESXi 4 hosts to be monitored as ESXi does not support SNMP GETs and SETs over UDP 161. To quote the "Dell OpenManage With VMware ESX/ESXi 4 Systems Management Guide" on page 43
"Server Administrator supports SNMP traps on ESXi 4. Server Administrator
does not support SNMP Get and Set operations because ESXi 4 does not
provide the required SNMP support."
Cold we have confirmation of this?
Thanks
john
Kong Yang
180 Posts
0
April 28th, 2011 13:00
I was told "The plug-in appliance requires port 162 in order to receive the SNMP trap that send by server administrator from other ESX or ESXi hosts that the vCenter manages." Did that answer your question? If not, can you please clarify?
Regards,
KongY
kickmaleerie
15 Posts
0
April 30th, 2011 03:00
But as I indicated in my post, the Dell documentation is misleading; in fact I think that whole section I mentioned has a number of errors - it also refers to 4433 (HTTPS) - and needs proof reading again.
I would still really appreciate a definitive statement as to what protocols (TCP | UDP) and which ports need to be open between vSphere, the Management Plugin appliance, vCenter and the ESX/ESXi hosts.