Reboot the ESX when LUN presented?

[Jorge Fabregas]

Hi,

We have a couple of "ProLiant BL460c G6" blades running ESXi 4.1 and every time we present a LUN (or assign new paths) to the ESXi hosts, we need to reboot them so they can see the new LUNs (or new paths to existing LUNs). A rescan of the HBAs (thru the vSphere Client) is not enough.

Is this the normal behavior or are we missing some special driver? Our storage-array is an XP20000.

Thanks,
Jorge

[Amar_Joshi]

Jorge,
Definitely it's not a normal behavior, you should be able to scan through storage HBA.

A couple of things; did you use VMWare image or HP's image to install the ESXi? Not sure what HBAs do you have but it's highly recommended that you use HP image on BL460c. Look for the drivers HP released in their images at http://h30507.www3.hp.com/t5/Eye-on-Blades-Blog-Trends-in/Driver-Versions-in-HP-supplied-VMware-ESX-ESXi-images/ba-p/82926

Also, are you sure that you have similar LUN numbers for each SAN Volume? I have seen this being the problem in cases where many LUNs are presented and they appear in difference sequence on each host.

Lastly, have you tried using CLI: vicfg-rescan to rescan the new volumes?

[Jorge Fabregas]

Thanks Amardeep. I didn't there was an ESX image from HP. I'm going to check that.