it's not even using the LUN id anymore to identify the LUN. It will be using the NAA identifier... which is unique.
Duncan
VMware Communities User Moderator
-
Blogging: http://www.yellow-bricks.com
Twitter: http://www.twitter.com/depping
If you find this information useful, please award points for "correct" or "helpful".
We also have the same HP array's and also have to reboot host to bring in storage which is annoying.
To avoid a reboot I sometimes unload the HBA driver after I put a host into maintenance mode. We use Qlogic cards
vmkload_mod -u qla2300_707
If you have HP Insight Agents installed you need to stop the agents in order to unload the HBA driver.
Not to hijack the thread but when storage is presented to a host shouldnt the host see an RSCN prior to a rescan ? in vmkernel
I remembered working with EMC Arrays and not having to reboot the host everytime I wanted to bring in storage. But then again I didnt have to bring in storage from different array's. I would present storage and rescan and I would see what I presented right away.
I've seen the same behavior from HDS as well. The issue I've always seen is if the new Lun ID being presented is lower than what you have, then a rescan will not pick it up. That may be a linux thing as opposed to an ESX thing, but does not manifest during a reboot.
-KjB
VMware vExpert
But this is only an issue when dealing with multiple targets correct?
That is correct.
-KjB
VMware vExpert
Thanks for this info ... My new LUNS from the XP24000 San have higher & unique LUN IDs then the LUNS from the EVA ... except for 1 lun from the XP ... based on what you are saying this might be my issue ... So I will test this out and let you know ..
Thank you for this ... will keep you posted .