topic Re: NetApp Host Utilities on a Guest using ESXi and RDM LUNs in VMware Solutions Discussions

NetApp Host Utilities on a Guest using ESXi and RDM LUNs

jarred — Thu, 05 Jun 2025 07:14:22 GMT

Hey folks, quick question:

What's the requirement for the Host Utilities for a Windows 2008 guest running SDW 6.2 inside an ESXi environment, when using FC RDM's for LUNs?

I cannot find anything directly on point, typically I would install the Host Utilities on any physical host, or virtual host using iSCSI from within the Guest. However, the ESX host utilities are not supported on ESXi, and the matrix doesn't go into detail about host utilities on the Guest OS.

Anyone know? TIA!

Jarred Medlock

PS Consultant,

NetApp, Inc.

Re: NetApp Host Utilities on a Guest using ESXi and RDM LUNs

lele — Wed, 19 May 2010 14:46:56 GMT

Jared

You dont need to install the host utilities on the guest OS, however you need to set the disk timeouts correctly.

You have to use Virtual Storage console on Vcenter which replaces host utilities as you cant have them on the esxi.

Thanks

Abhijit

Re: NetApp Host Utilities on a Guest using ESXi and RDM LUNs

chriskranz — Wed, 19 May 2010 20:41:50 GMT

It makes no real difference if this is ESX or ESXi as this is a Guest OS configuration. The recommendation is to always install the NetApp Host Utilities when you are connecting NetApp storage to a system. In this case you are connecting it to a Virtual Machine, so you want to make sure the host utils as loaded into the Guest OS.

Obviously you want to make sure the correct timeouts are set for ESXi at the ESX layer, and also the Guest OS timeout values, but I would definitely install the NetApp Host Utils within the Guest OS if you are giving it any NetApp storage directly (RDM or iSCSI within the guest).

Hope this helps...

Re: NetApp Host Utilities on a Guest using ESXi and RDM LUNs

amiller_1 — Sat, 22 May 2010 03:01:56 GMT

Complete agreement -- if I'm installing SnapDrive on a box (physical, virtual, whatever), I always install the Host Utilities first (possibly overkill but just avoids potential issues).