SymINQ on the host will give you the device ID, symm serial number, local disk ID, etc. You can find it at ftp://ftp.emc.com/pub/symm3000/inquiry/  The device name is an attribute that can be set/removed/changed without impact to the host.
Hi all,   Can anyone suggest any safeguards that might help in a process for safelyremoving VMAX storage from a production host?    As we're using auto-provisioning the old trick of removing one path for theLUN as a method of cross-checking that the correct LUN is being worked on isnot possible so I was just wondering if anyone had any good ideas.    Basically, are there any ways apart from the obvious of confirming the devID of WWN to identify a LUN before removing it? For example is it possible toset an attribute on a LUN that the Platform guys use to identify it usingnative OS\volume management tools?   I have heard that some other Vendor Arrays are able to tell if the LUN is inuse on the host but presumably this would require a host agent?   Cheers!
Bets method to safely decommission VMAX Storage