SRM Protection Groups

[slemont]

I have gone through the Protection Setup except for the "Protection Groups" part. It is greyed out. The account I am using has SRM permissions. Does anyone have any idea on how to fix this?

[Michelle_Laveri]

I have gone through the Protection Setup except for the "Protection Groups" part. It is greyed out. The account I am using has SRM permissions. Does anyone have any idea on how to fix this?

Have you gone through the "Array Managers" part of the set-up and confirmed that SRM can see LUNs/Volumes at are replicated and contain VMs???

Regards

Mike

[slemont]

I am using EMC DMX-3 Symmetrix. I get a green check mark next to the array but I can't see the luns and vms on the finaly page.

[Michelle_Laveri]

Are your LUNS replicated - and more importantly do they contain virtual machines files... The SRA looks to see if the LUNs that are replicated contain virtual machines. If not - it supresses the visability of that LUN...

Regards

Mike

[crittenden]

also make certain that the FA ports you are connecting the ESX hosts to (on both sides) have the SPC-2 bit enabled. the problem you are seeing is generally related to something not being configured correctly in the array or the SRA not being able to correctly discover the LUNs and replicated datastores.

[Michelle_Laveri]

also make certain that the FA ports you are connecting the ESX hosts to (on both sides) have the SPC-2 bit enabled. the problem you are seeing is generally related to something not being configured correctly in the array or the SRA not being able to correctly discover the LUNs and replicated datastores.

That's interesting - what is the SPC-2 bit - what does it do?

Regards

Mike

[crittenden]

the SPC-2 bit is a setting on the Symmetrix which allows the OS which is communicating to the LUN to issue advanced commands. with ESX in particular, this is what allows some of the advanced features such as SVmotion. the SC3 setting allows the ability to use ANSI 4 ability. this is related to performance more than anything. with ESX 3.5, the SPC-2 bit setting is a requirement, and the SC3 setting should be set as well.

regards,

will

[Itzikr]

Hi,

i set the SPC2 and the Iscsi on all the esx initiators and still do not see the datastores..

[jbloo2]

Hi Itzikr -

SRM will report replicated datastores if there is a VMFS on a replicated device and at least one VM configured within that datastore. It seems that you might have placed datastores on non-replicated Symmetrix devices, and that there are no datastores on R1 LUNs. It may be that the logs are somewhat cryptic but I see in your logs the following:

SRM discovers 4 VMFS datastores on 4 LUNs (host LUN numbers 168, 168, 170 and 171)

Added vmfs extent 'host-28;vmhba4:0:168' with key 'host-28;48ea125c-094a9ae8-453b-001a64c56344;0'

Added vmfs extent 'host-28;vmhba4:0:169' with key 'host-28;48d784e6-033126b6-c793-000e0cb80056;0'

Added vmfs extent 'host-28;vmhba4:0:171' with key 'host-28;48ea2ba8-8ee81990-d919-001a64c1b044;0'

Added vmfs extent 'host-28;vmhba4:0:170' with key 'host-28;48ea2bc1-051ef018-aad9-001a64c1b044;0'

Looking a few lines above you can get information about those LUNs:

Added LUN '10:00:00:00:c9:75:95:30;0;50:06:04:84:52:a5:84:76' with keys 'host-28;vmhba4:0:0' and 'host-28;02000000006006048000029010075353303044463553594d4d4554'

Added LUN '10:00:00:00:c9:75:95:30;168;50:06:04:84:52:a5:84:76' with keys 'host-28;vmhba4:0:168' and 'host-28;0200a800006006048000029010075353303037423053594d4d4554'

Added LUN '10:00:00:00:c9:75:95:30;169;50:06:04:84:52:a5:84:76' with keys 'host-28;vmhba4:0:169' and 'host-28;0200a900006006048000029010075353303038434553594d4d4554'

Added LUN '10:00:00:00:c9:75:95:30;170;50:06:04:84:52:a5:84:76' with keys 'host-28;vmhba4:0:170' and 'host-28;0200aa00006006048000029010075353303038433653594d4d4554'

Added LUN '10:00:00:00:c9:75:95:30;171;50:06:04:84:52:a5:84:76' with keys 'host-28;vmhba4:0:171' and 'host-28;0200ab00006006048000029010075353303039423353594d4d4554'

Added LUN '10:00:00:00:c9:75:95:30;172;50:06:04:84:52:a5:84:76' with keys 'host-28;vmhba4:0:172' and 'host-28;0200ac00006006048000029010075353303038423953594d4d4554'

Added LUN '10:00:00:00:c9:75:95:30;173;50:06:04:84:52:a5:84:76' with keys 'host-28;vmhba4:0:173' and 'host-28;0200ad00006006048000029010075353303038424353594d4d4554'

Embedded within the last token of each line is the UUID of each LUN, and embedded within each UUID is the WWN of the LUN (the 32 characters starting from character 11). For example, vmhba4:0:168 has wwn 60060480000290100753533030374230 (the SPC-2 bit is necessary for this to work)

However, looking at the output of the discoverLuns script from the EMC adapter, I cannot find that wwn listed at all in the list of R1 LUNs. So LUN 168 is not replicated. The only WWN's from the output of discoverLuns that match WWN's of LUNs with VMFS extents is LUNs 172 and 173, however there do not appear to be any datastores on them, so this is why SRM is reporting back empty.

Please try to create a datastore on vmhba4:0:172 or vmhba4:0:173 and place a VM in that datastore, then go through the array manager configuration again and see if SRM picks up that datastore. Mapping VMFS extents to SRDF LUNs can be quite challenging sometimes.