DCNM is down. I love the tool, but the downside is that you forget how to use the CLI. I faced downtime of our DCNM appliance and was forced to use the CLI instead. No big deal actually, but I still want to post the commands to use when you need to add new hosts to existing zones.
First you might want to create a new device alias for the new hosts:
device-alias name server1 pwwn 20:11:00:15:b9:00:00:00
device-alias name server2 pwwn 20:11:00:15:b9:00:00:01
And then you want to add the new aliases to the existing (smart) zone:
zone name NameOfZone vsan 123
member device-alias server1 init
member device-alias server2 init
zone commit vsan 123
You don’t need to commit the whole zoneset again, since that one didn’t change. Check it by running:
zoneset activate name ZoneSetName vsan 123
That’s it! there’s not much to it, and can save you a lot of time as well!
Over the years I collected a number of useful CLI commands to control the DMX / VMAX machines I worked with. Even though nowadays Unisphere for VMAX is a useful tool, nothing really beats the command line!
Read more »
Creating tdevs and masking them to hosts (storage groups in a masking view) is relatively easy in the Unisphere for VMAX interface, but what if you add a few tdevs of exactly the same size and you want to make sure that the VMware administrator uses the right LUN for each VMFS he’s going to create? One way to make sure he knows which LUN corresponds with what tdev is the Host LUN id. To list the host LUN ids
symaccess -sid 1234 show view mv_some-maskingview-name
or (a bit more verbose)
symaccess -sid 1234 list view -name mv_some-maskingview-name -detail
The second command shows each initiator group nested within other initiator groups as well.
Both generate a table with the following headers:
Dev Dir:Port Physical Device Name Lun Attr Cap(MB)
The column under “Host Lun” shows the Host LUN ids.