Skip navigation
VMware

This Question is Not Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
1,052 Views 20 Replies Last post: May 5, 2009 8:47 AM by vmware_lic RSS
depping Champion VMware Employees User Moderators vExpert 4,238 posts since
Jan 17, 2005
Currently Being Moderated
15. May 3, 2009 7:52 AM in response to: kjb007
Re: Rescan for new LUNS  from XP24000 .... Not showing up ... ?

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".

Duncan | Yellow-Bricks.com | Author of the vSphere 5.0 Clustering Deepdive
CITITECHS Enthusiast 41 posts since
Feb 4, 2008
Currently Being Moderated
16. May 4, 2009 8:21 AM in response to: vmware_lic
Re: Rescan for new LUNS  from XP24000 .... Not showing up ... ?

 

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.

kjb007 Guru vExpert 6,682 posts since
Sep 18, 2006
Currently Being Moderated
17. May 4, 2009 8:26 AM in response to: CITITECHS
Re: Rescan for new LUNS  from XP24000 .... Not showing up ... ?

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

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
Chamon Master 976 posts since
Aug 15, 2007
Currently Being Moderated
18. May 4, 2009 8:57 AM in response to: kjb007
Re: Rescan for new LUNS  from XP24000 .... Not showing up ... ?

But this is only an issue when dealing with multiple targets correct?

kjb007 Guru vExpert 6,682 posts since
Sep 18, 2006
Currently Being Moderated
19. May 4, 2009 9:25 AM in response to: Chamon
Re: Rescan for new LUNS  from XP24000 .... Not showing up ... ?

That is correct.

 

 

 

 

-KjB

VMware vExpert

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB

Bookmarked By (0)

Share This Page

Communities