Slap a GUI on it : New EMC UBER DHSM Tool

uber_dhsmI hate long running steps. I am the shortcut king which can be both a bad and good thing. And as awesome as the Celerra NFS Plug and our new Unified Plug-in are, there was one minor thing I didn’t like as much about the install process. The DHSM config.

I had got an email from a teammate on an issue he was having this week. It turned out to be the same thing that had happened to me a month before, user error. Messing around with Linux console CLI commands is easy if your are Clint Kitson. But, if you are tired or hungry or a Window guy it isn’t your favorite thing to do. The new Perl script is great for a one way setup. But, this wasn’t good enough for me.

I was sitting in the EMC Innovation Conference with my buddy Ed Saipetch when I had a crazy idea. What if someone wrote a GUI for the DHSM setup that would explain everything and make it easy to configure. “But Nick…”, you might say. “How can you configure DHSM from a Windows GUI when it is done from a Linux CLI?” Well I also happen to be working on another much bigger project that solved this problem. So using the progress I made on the big project and some XAML stuff I do with my VMware tools I have created the UBER Celerra DHSM Tool.

All you need is a Windows workstation with network access to the Unisphere/Control Station Web interface. This tool will allow you to:

  • Create, modify or delete users.
  • Add or Remove Users from Allowed Users List
  • Add or Remove Hosts from Allowed Hosts List
  • Start or Stop DHSM Services

It is designed to be as GUI-centric as possible so you get cool feature like just selecting a user from a list to add to an allowed user rule(no having to type!).

Couple things to look out for:

  1. If an operation for adding a user gets locked you may need to reboot the datamover or clear the lock file. I could have created a process to manage this but I have my limits.
  2. You do need to login as root to create a new user. If just changing rules you only need nasadmin.
  3. Speed is relative to the Celerra. The app stays single threaded so if it locks up it is waiting on the Celerra to respond.

*** New update ***
I just updated the tool with a couple new features:

  1. It will now expose the UID and GID values in the creation of the user (credit for the idea to Pete Richardson). It will auto populate the values but allow you to customize. It will also validate your values.
  2. Now when you delete a DHSM user it will remove them from the Allowed User list if they are there also.

*** Back to your regularly scheduled blog post ***

Check out the video below for a quick run through and download the tool here: (x86 Version / x64 Version)

UBER Celerra DHSM Tool Video Demo from Nicholas Weaver on Vimeo.

And as always, let me know how this works for you. Feedback is gold.


Celerra VSA EMC Tools

14 Comments Leave a comment

  1. Awesome tool Nick, especially since I’m setting up the Unified plugin later today or tomorrow. Good timing for me. Think you could add in the option to mask the password in case we had any unwanted shoulder surfers. ; ‘ ) Thanks again man!!

  2. Hi Nick, awesome work. Prompted no doubt by the issues people had either running the server_* commands manually or the perl script, looks like v2.0.6.52 now has it in the plug-in’s GUI to “Setup Dhsm”. Doesn’t have all the features you offer such as deleting users or IP’s from the access list and doesn’t let you stop/start the DHSM service. So until that gets blended in, will keep using your tool.

  3. Thanks for the great utility, when I installed the new unified plugin it would not allow me to create the DHSM user…after I used your utility I was able finish the DHSM setup.

  4. I can’t get it to log in. Is it because we are using a numbersign in the password field? Perhaps this also acts as a control character or some special character in the program, so it’s not passing it along?

  5. Hey, Nick – tried this on 2 VSAs; one had the datamover still named server_2, while one I had renamed to ubervsam1. I can get it to log in to the dm named server_2, but not to the VSA with the dm named ubervsam1…. other than that, they should be the same in all respects; they were both deployed from the same OVA, just configured with different ip addresses…

  6. Ok yeah your program does not like a # in the password field. It’s our company policy to use strong passwords which make use of at least 1 capital, 1 lower, 1 number and 1 special character. We changed the # to an underscore and it works now.

  7. Nick, I found the tool failed to download now, could you check it? Or post a new URL for download. I feel it’s a very good tool for me.

%d bloggers like this: