ONTAP Discussions

What's the best protocol to use for Hyper-V on ONTAP

swordfish
1,290 Views

Hello Everyone,

 

We have deployed Hyper-V last year on CIFS and we have been running into issue with that. One ONTAP upgrade led to lifmgr going into non-responsive state and another was with the domain authentications, rebooting all the VMs. This has led us to think about moving to iSCSI instead of using CIFS. In your opinion what would be the best protocol for Hyper-V and what could be the downsides related to that.

 

Thank You

 

1 ACCEPTED SOLUTION

Mjizzini
1,209 Views

Depending on your environment, DC/Network stability, setup and config,  each protocol can have advantages over the other one. 

 

That been said, Since ISCSI is a SAN protocol, It has no interactions with the domain controller.

ISCSI LIF dont migrate. ISCSI MPIO sets up multiple paths between a server and its storage. It provides failover path incase of any link/path failure. 

View solution in original post

5 REPLIES 5

SpindleNinja
1,279 Views

I've not ever deployed Hyper-V with SMB3. Always iSCSI.

TMACMD
1,252 Views

I agree that iSCSI should be the first thing to use.

 

With SMB, are you using SMB3 and CA (Continuously-AVailable) shares? You have to enable the option per-share.

If not, that might explain all the woes

swordfish
1,249 Views

O yes. We enabled everything following the TR from NetApp to ensure NDA

Mjizzini
1,210 Views

Depending on your environment, DC/Network stability, setup and config,  each protocol can have advantages over the other one. 

 

That been said, Since ISCSI is a SAN protocol, It has no interactions with the domain controller.

ISCSI LIF dont migrate. ISCSI MPIO sets up multiple paths between a server and its storage. It provides failover path incase of any link/path failure. 

GidonMarcus
1,160 Views

Hi

 

I think that the answer is depend on your circumstances.

If you can get the same (or acceptable) performance and availability with other protocol that been proven or theoretically more fit - that's a win.

 

Beside MPIO that was mentioned before. I do want to add that by doing that you're moving what now been your point of failure - to another; Windows clustering... in the last few years iv'e seen the CMS process crashes, indefinite WMI leaks (some recovered gracefully,  required a VM shutdown or just crashed) and lot's of finger pointing between software and hardware vendor when these go south.  yes - the majority is for a single host and not affected the whole cluster, but I did see a few that did.

Gidi Marcus (Linkedin) - Storage and Microsoft technologies consultant - Hydro IT LTD - UK
Public