Unsolved

This post is more than 5 years old

6 Posts

1863

September 3rd, 2009 07:00

Storage Allocation for VMAX through SMC

We are implementing a VMAX and are trying to determine the best way to allocate through SMC. Are there any standard best practices to assure LUNs obtain the same LUN ID down both FAs?

66 Posts

September 3rd, 2009 09:00

I think the only way to make sure it uses the same addresses is to keep the FAs identical. If it's like ECC it will pick the first available address from each FA.

This is the first reason I never used ECC. When it came out we had EDM which required GKs for all of the systems. We reserved addresses under 10 for them but never filled them up and only added them when we needed to. This made using ECC impractical to do mapping. We were having to re-address one path every time we mapped devs.

The VMAX with FAST sounds like a great product but I will never understand why they are taking SYMCLI configuration from us.

30 Posts

September 3rd, 2009 11:00

Change is good! It keeps us all employed :) Actually, this new method is growing on me, I like it.

Keeping the FA's identical will get you the same lun ID's. I have not tested a scenario where the FA's are not identical, to see if adding devices to a storage group results in the same lun id's on different FA's. But that's an interesting test to try in the lab, I'll give it a shot.

You can override the LUN ID when you add a lun to a storage group in SMC. After selecting the device(s) to add, click on "Set Dynamic LUN Addresses." That opens a dialog that lets you modify the starting lun address for the range of luns you have selected.

You can also override LUN ID's when you add devices to a storage group using symaccess.

92 Posts

September 3rd, 2009 13:00

What's this? VMAX + FAST = no symcli???

30 Posts

September 3rd, 2009 14:00

I guess I should clarify. With the VMax you are NOT losing SYMCLI access. You are actually getting better SYMCLI functionality.

SMC 7.0 is improved over the previous versions, to the point a die-hard command line person like myself is willing to use it...I would call it a win/win.

4 Apprentice

 • 

423 Posts

February 9th, 2010 01:00

dhavalp

when you are creating the initiator group you can use the -consistent_lun option from SMC or SYMCLI

symaccess ‑sid XXX create ‑name solaris_host ‑type initiator ‑file InitiatorFileName  ‑consistent_lun

Use the

-consistent_lun option if the devices of a storage group (in a view) need to be seen on the same LUN on all ports of the port group). If the -consistent_lun option is set on the initiator group, Solutions Enabler will make sure that the LUN number assigned to devices is the same for the ports. If this is not set, then the first available LUN on each individual port will be chosen.

The same option exists as a checkbox in SMC

Note that symaccess by default uses dynamic lun addressing so from the host point of view the lun address will always remain the same on all devices presented within a view.

Hope this helps.

35 Posts

November 16th, 2012 04:00

He Paul,

By default the checkbox within SMC is off, do you know if there is a possibility to set Consistent_lun default to yes ???

Thanks,

Ferry

No Events found!

Top