Hi folks -- sometimes it is possible that a naa id points at a different VML ID than the actual one -- for example if a lun is presented with ID 0 and then ID is changed to 1 - the naa.id in /vmfs/devices/disks still points to the old VML ID unless rescanned -- now if someone before rescan attached this LUN ID to a VM it is perfectly accepted and the guest is not vmotionable any more because a rescan would have taken place by then on the other hosts 
how do I make sure an auto-rescan(storage) is kicked off before anyone tries to attach an RDM LUN ?
thanks,
~Sai Garimella
