Subscribe

SnapDrive 6.2 and iGroups

Hello!

I recently installed Snapdrive 6.2 on my windows test VM running in a VMware ESX cluster.  I am having a problem finding my existing igroup whenever I create a new disk or connect an existing disk from my NetApp storage.  It keeps stating “No Igroups Found” and wants to create a new igroup with my ESX initiator that is hosting my test VM.  My existing igroup that was previously defined has every ESX initiator in that group including the ESX server currently hosting my test VM.  Why does snap drive not see this??  The only way I can get this to work using my existing igroup is to map the RDM LUN in filer, then within vCenter edit my test VM and add disk as a RDM.   Once I boot the VM I add this using windows disk management.  Once disk is added, snap drive will see the drive and I am able to manage.  I am not sure if this is supposed to be the way.  Any thought?  TIA!

Re: SnapDrive 6.2 and iGroups

What is the igroup type that you have set on the filer? Can you check if it is set to "VMWare"?

Re: SnapDrive 6.2 and iGroups

Yes, it's set to vmware.

Re: SnapDrive 6.2 and iGroups

I have the same problem. It seems that snapdrive 6.2 don't recognize igroups already created (I've tried creating one manually and also with one created by rcu).

I had to make snapdrive create it's own igroup and then I've added the other vmware machines to that igroup to be able to vmotion switch the host where the machine run.

Re: SnapDrive 6.2 and iGroups

Does anyone know the difference between igroups created manually and igroups created by snapdirve?  Also, is it safe to have two igroups with all esx servers in my cluster within both igroups?  thanks!

Re: SnapDrive 6.2 and iGroups

I think SnapDrive follows certain naming convention when creating igroups. You can name the igroups anything you want when you create them manually. But they are essentially the same. As long as you only use one igroup to map a LUN, there shouldn't be any problem to have more than one igroups.

Thanks,

Wei

Re: SnapDrive 6.2 and iGroups

I have exactly the same issue. This has to be a bug. Have you found a resolution? When does one use type Windows for an igroup? I thought if I created an RDM within a Windows VM via snapdrive and needed to map that RDM to an igroup I'd need to create an igroup of type Windows? I know that the RDM is created as type Windows. Should the igroup also be of type Windows or VMware? This presents a dilema. Netapp states you cannot have the same initiators in different igroups of different types (i.e one igroup type Windows and the other type VMWare). I already map luns to ESX for datastores and those luns are mapped to an igroup of type VMware. If Snapdrive creates an RDM and needs an igroup of type Windows how can i use the same initiators when they are already part of another igroup of type VMware? Would I have to use NPIV - generate a new set of WWNN/WWPN for the Windows VM and put those into a different igroup.

Thanks

Re: SnapDrive 6.2 and iGroups

Hello,

If you believe there is a bug, you probably should raise the issue with NetApp support.

Thanks,

Wei

Re: SnapDrive 6.2 and iGroups

Guys,

I was pointed to this issue last night and to the posts here.

This issue was a Bug with SnapDrive v6.2 which has been fixed with 6.2D3

http://now.netapp.com/NOW/download/software/snapdrive_win/6.2D3/

Re: SnapDrive 6.2 and iGroups

Hi Nick. Someone recently reported the issue was fixed in 6.2P1:

http://now.netapp.com/NOW/download/software/snapdrive_win/6.2P1/download.cgi

What's the difference between that version and the one you reported (6.2D3)?

Thanks

Ian