Unsolved
This post is more than 5 years old
28 Posts
0
5276
Unisphere VMware plugin problems... help !!
I've installed the unisphere plugin for vmware on vi client and run the DHSM pearl script on the celerra control station to create a DHSM user. I've created the DHSM username, password, user ID and Guest ID which are all unque. When using the plugin on vmware, the plugin is installed and the right click features are there, but theres something not working. For example when I go to create an NFS datastore it completes the creation on the NFS export in the task view at the bottom of the vi client, but fails to create the datastore. The plugins finds the celerra ok when i specify the control station ip and credentials, see's the datamovers and disk pools on the celerra... just doesn't complete the task. I'm assuming this is a DHSM authentication issue.
I've gone to the plugin settings and there is a section to enter DHSM credentials. It will not however allow me to enter the credentials I create with the DHSM script on the control station as it says the username already exists on the datamover.... is there something I'm doing wrong here.. I get the impression the DHSM settiing screen in the plugin are to create DHSM user credentials not to allow VMware to effectively handshake with the celerra..
Is there something else I'm meant to do here ? I need to get this up and running to demonstrate the feature at an event, the documentation was concise in showing how to run the script and install the script, but a bit light on the ground in terms of troubleshooting configuration
Rainer_EMC
8.6K Posts
0
October 16th, 2010 14:00
are you already using version 2.0 of the plugin that was released on Friday?
Ev5
28 Posts
0
October 16th, 2010 15:00
Yes, With an NS120 running dart 6 and vsphere 4.1
Rainer_EMC
8.6K Posts
0
October 16th, 2010 16:00
I would suggest to look at
- the data mover log with server_log
- /nas/log/cmd_log
if there are any hints there
clintonskitson
116 Posts
0
October 16th, 2010 16:00
This could possibly due to configuration on your esx server if there are multiple vmk interfaces on different subnets. The last part of adding the NFS datastore sets the export privileges for access to the share based on the IP of your vmk interfaces. Just a shot in the dark, but I've seen this before when using ohter integration points re NFS and VMware.
The symptoms would be a successful addition of the share and export settings to the celerra, but ESX would fail to mount the share due to the wrong subnet being advertised for access. If this is the case you can use options under the Unified Plugin when mounting the NFS share to open access to more subnets, ie. 10.0.0.0 255.0.0.0 or something similar.
Also check the following log file for errors.
C:\Users\kitsoc\AppData\Local\VirtualStore\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Plugins\EMC Virtual Storage Integrator\Logs
Ev5
28 Posts
0
October 16th, 2010 16:00
Thanks guys, appreciate the responses. I'll have a crack at it on monday and post progress.
Incidentally once I've created the dhsm credentials on the control station using the supplied pearl script, should I be having to reference this credentials from vsphere in the plugin ?.. The documentation implies the dhsm setting options are as an alternative to using the scripted cs option... If that's the case.. Where would I reference them?
Rainer_EMC
8.6K Posts
0
October 16th, 2010 17:00
also try creating one NFS export manually
in the past there was a problem with the NFS problem if the Celerra didn't have any exports
Ev5
28 Posts
0
October 18th, 2010 11:00
All sorted. Simple simon solution.. when creating the dhsm user in the control station using the script (or the plugin, which is quite nice), it asks for a client IP address. I had assumed this was asking for the service console address (s) of the ESX hosts/Vcenter, but no.. its the IP address of the workstation I'm running the VI Client on..
Thanks for your feedback
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
October 20th, 2010 14:00
Be sure to use a static IP address from your vSphere client when adding IP addresses to DHSM.
When I run the plug-in on a DHCP-enabled client that gets a different IP address every time I connect over the VPN, I need to append my new client IP address to the Celerra DHSM feature before I can use the plug-in's compression and cloning features. The easiest way to do this is by logging into the control station and executing the command:
server_http -append dhsm -hosts
Ev5
28 Posts
0
October 20th, 2010 14:00
Apparently you can simply type "any" in the client ip address field and it will accept all.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
October 20th, 2010 15:00
This doesn't work for me on DART 5.6:
$ server_http server_2 -append dhsm -hosts any
server_2 :
Error 13156089869: server_2 : Invalid config value for feature DHSM:Bad
IP address/subnet entry 'any'
$ server_http server_2 -modify dhsm -hosts any
server_2 :
Error 13156089869: server_2 : Invalid config value for feature DHSM:Bad
IP address/subnet entry 'any'
clintonskitson
116 Posts
0
October 20th, 2010 15:00
Use the remove option for any ips that are listed when doing the info command, check the recent writeup on this on another thread
Sent from my blackberry
Ev5
28 Posts
0
October 20th, 2010 15:00
I'm at ip expo to and was shown this by a vspecialist. I'll check with him tomorrow as I'm back there.
clintonskitson
116 Posts
0
October 20th, 2010 17:00
https://community.emc.com/thread/111997?tstart=0
The above thread should provide the relevant info to remove the IP restriction.