2015-05-04 03:28 PM
So, yeah. 5.1x does require all RDMs to be mapped to the same LUN # on all hosts in the VMware cluster. Otherwise vmotion and failover won't work.
My advice: Do what Bob said. Create one new igroup for all initiators in the ESXi cluster.
Now, the question becomes, how do you get there from here?
There's a million ways to do it, but for RDMs you basically are going to have to schedule maintenance so that you can unmap and remap the LUNs if you want to keep them.
The other problem is that you have the wrong multiprotocol type for your LUN. Since this is Windows 2008 you need to use the Windows_2008 LUN type, not the Windows type (confusing, I know).
So... Maybe you need to look at creating a new LUN of the correct type, mapping it to your ESXi cluster, adding it to your Windows VM, and then copying the data from your old LUN to your new LUN using the guest OS (robocopy?).
2015-05-04 03:37 PM
ok thanks. but still if its RDM, is there a big different in using say vmware vs windows 2008 vs windows protocol if I do not plan to use snapdrive inside the GOS.
why not use vmware instead?
2015-05-04 03:40 PM
Terminology first. You are concerned about the LUN "ostype", not protocol. Protocol for block is either iSCSI or Fibre Channel. I mention this for clarity for everyone reading.
Both LUNs and igroups have a "ostype". The "ostype" value is tied to the controlling Operating System and adjusts certain behaviors and settings that are unique to the Operating System. That's why the "ostype" exists.
For igroups, the "ostype" controls behaviors associated with how the controlling OS talks over the wire - either iSCSI or Fibre Channel - using the SCSI-2/3 command set. For LUNs, the ostype controls behaviors associated with how the controlling OS reads and writes data to the logical "disk". For instance, a LUN with an "ostype" of "windows" will trigger the NetApp controller to fake the starting offset to get better partition alignment for better performance, whereas an "ostype" of "windows_2008" won't do that because W2k8 changed the default alignment. So the LUN "ostype" is all about the contents, while the igroup "ostype" is about the wire protocol. In general of course.
Typically, the "ostype" for both LUN and igroup are essentially the same or within the same family - for instance an igroup of ostype "windows" and a LUN of ostype "windows_2008" are within the same family. Natural of course because typically the controlling server is the same for both the igroup and the LUN.
In virtualization, you introduce the possibility that the controlling server is different between the igroup and the LUN. With RDMs, ESX acts as a pass through. That is, the ESX host takes the read/write request from the Guest OS and puts it out on the wire essentially as is (there are a couple of exceptions, of course). So - what you have is ESX (VMWare) controlling the "wire" (igroup) while the Guest OS controls the contents of the disk (LUN). So for an RDM that is mounted to a Windows guest, the igroup should be of ostype "vmware" and the LUN should be of ostype "windows" (or one of the other ostypes in the windows family as appropriate like "windows_2008").
Bonus question - if you are not using SnapDrive, why use an RDM at all in this example? Do you have some other need to snapshot this LUN independently of ESX control at the NetApp level? Need to take NetApp FlexClones for some reason? If not, why RDM at all? It does introduce a level of complexity but shouldn't be done just because. If it was done for "performance" I'll say it is a common misconception that RDMs are, in general, faster. In most cases you can't get a difference in performance, since you still go through both the guest OS kernel and the ESX kernel to process any disk request. Of course there are rare exceptions, but RDMs are primarily for when you need advanced "native" storage capabilities.
Lead Storage Engineer, Huron Legal
Huron Consulting Group
NCDA | NCIE-SAN Clustered Data OnTap