Thank you all for helpful answers but there is another key technology involved. If I am presenting iSCSI LUNs from DM2 to my VMWare hosts what would be the ideal naming convention? When I am browsing my Virtual Center all presented LUNs would need to make sense too

Thanks

Please refer to the Documents located in the following locations:

Home  >Support  >Technical Documentation and Advisories  >Hardware/Platforms Documentation  >Celerra Network Server  >Installation/Configuration
Home > Support >Technical Documentation and Advisories > Hardware/Platforms Documentation > Celerra Network Server > General Reference

Good luck.

The naming convention for the Data Mover variable in the command line interface is (default = server_2 to server_15).
The commands are prefixed, then appear in alphabetical order.

Celerra Network Servers with a CLARiiON CX4 backend also support virtually provisioned backend Thin Pools. One CLARiiON backend Thin Pool is mapped to one Celerra system-defined virtual AVM pool, with a default naming convention of “ _ ”.

By default, the destination file system name will be the same as the source file system name. If a file system with the same name as the source file system already exists on the destination, the naming convention _replica<#> will be used. A number 1–4 is assigned according to how many replicas of that file system already exist.

With Reference from:

Command Reference Manual
P/N 300-004-156
REV A12

is this for you (Celerra admin) or for VMware admin ?

we are still on VI3 but it does not matter in this case. Just for admin purposes what you think of this naming items?

dm2_r5_repl_01

dm2_r5_01

dm2_r10_01

Data Mover first -> Raid 5 or 10 -> replication (not all LUNs are being replicated) - > number

So when admin looks at it it should give him the good information about the LUN

when you are in vSphere you are browsing datastores, i think naming datastore with appropriate name (could be class of storage) would be more beneficial than the actual iSCSI LUN name.

Hi,

I understand that you want to rename the iscsi lun Ex: Local Disk to some name , and I think this would be not possible as this feature is not available from Celerra.

Sameer Kulkarni

I am the one and the same

that works if you are looking from Celerra perspective. Correct me if i am wrong but from ESX host you don't see the LUN name unless you are running vSphere Virtual storage intigrator ( i know you are not there yet ) . In that case i would match Celerra LUN name with Datastore name in VI ?

using the Vcenter or vSphere you can see the luns. otherwise you would not be able to place any VMs to fiber or iSCSI storage (LUNs)

Thank you all. I think i will go that route