UNSOLVED
Unisphere plugin for vsphere problems
Hi Guys,
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.
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 consise in showing how to run the script and install the script, but a bit light on the ground in terms of troubleshooting configuration
Thanks Eric,
The plugin works fine, datastores mount ok, fastclones are working and compression works like a gem.
Not sure why the option is there to login and script install the setup of dhsm users on the control station when you can do it from the plugin in DHSM settings with such ease (once i figured out what IP it was actually asking for)
The NS120 I'm running doesn't have native iSCSI or FC enabled, so couldn't play with the block functionality. I'm assuming it just references pre-configured raid groups for LUN creation and that the esx hosts need to be configured into a storage group for it to work, then it just adds LUNs to the storage group, scans adapters and mounts the LUN. Would be nice to see the ability to use iSCSI on the plugin for the celerra elements, that said I could see them taking iSCSI away from the data movers and going native iSCSI only so as not to eat into the capacity limits of the NAS heads now its all unisphere and soon to be VCX/Clariionerra/Celeriion/whatever it'll be called.
My assumption is that the next box (not the Neo Jnr/NX3), will consolidate some of the ports required and deliver IP traffic for both NAS and all SAN over commin ports not NAS interfaces and flexports as seperate and different entities ?
Can't really comment directly on your last question in this forum. Suffice it to say that we are working to keep the plug-in updated in a timely manner as our platforms and platform software releases are updated.
Regarding the block functions on your NS120, this revision of the plug-in does a check to verify that the iSCSI and FC licenses are enabled on the storage processors. So, the plug-in would not allow you to create new data stores on using those protocols on your system.
Eric
EMWagner1
13 Posts
416
0
Posted October 18th, 2010 15:00
It looks like you got your issue resolved on another support forum. Glad it's working for you now. Maybe we need to clarify the documentation a bit to prevent others from having the same problem when setting up the DHSM user credentials in the plug-in. We would definitely like your feedback on your experiences with the plug-in as you use it more.
Thanks,
Eric