A good strategy moving forward might be to use the "Volume Identifier" field on your VMAX TDEVs to name them appropriately and rename the LUN itself on CLARiiON.  For instance, you could use "Server1_C" and "WebServer2_F" as useful names.  It might be time-consuming at first, but it could save you time down the road.

hey Karl , how do I set the Volume Identifier field 

Hi,

If you have access to the host in question, you can download and execute the inq utility to resolve the relationships between host devices and VMAX or Clariion/CX/VNX devices. You can get inq at ftp://ftp.emc.com/pub/symm3000/inquiry/v7.6.2.0. There are a bunch of different CLI arguments -- just run it with a -h to see the list of options.

Thanks,

- Sean

apparently my admins aint user friendly lol . I will defnitely try the inq utility .

cheers aran

the admins are repulsive when it comes to installing any s/w on their systems , they go crazy .

I can probably suggest the inq utility  when there is a new server build in our environment thats san connected  , better done during the initial set up  .

Thanks for the info Sean .

Cheers !!

I second the use of inq on the host, makes local device discovery quick and easy. I have found that the sysadmins/dbas like it as well and are willing to run it and send me the output once I show them how to use it.

sorry, correct syntax is:

set dev device_name=' ';

forgot the single quote for the device name.

one nice thing about inq is you don't have to install anything, just drop the executable in a directory and call it from the cli.

the volume identfier or 'device name' can be set as follows with the cli (or in Unisphere):

set dev devcie_name= ;

my personal experience with device names on a symm is that they aren't viewable in the output you may want to see them, so i don't bother with them anymore. dynamox may have some good examples about how he uses them.

Hi Aran,

never considered using that option because most of our boxes are either running SE, inq or we simply rely on the output from PowerPath.  Back in RedHat 4.5 days we actually had some issues where running sympd list would panic the box, so system admin got kind of skittish after that. We since have moved on to RHEL 6.x so it has not been an issue. Just like you i like the inq utility, drop it, make it executable (on *nix) and go ..no need to mess around with solutions enabler.