vmbha LUN number is not matching with LUN ID

[piseema]

After adding new LUN, here is what we see, Please see the attachded.It should match the LUN number L:144 to LUN ID which says 1 for example, why? Please help.

[mcowger]

This can happen if you used to have a LUN on address 1, then removed it and presented a new one.  The runtime name would be still incremented, but would be discovered first.

If so, a reboot would fix this.

[piseema]

Thanks Matt for a quick response. I am not sure if there was a Lun on address 1 but could be. would rescan of vmbha fix this or reboot is necessary? I have 8 esx hosts in a cluster and rebooting all of them is not something I want to go through.

[mcowger]

I doubt a rescan would help the runtime ID change - as thats supposed to be consistent for the runtime of the host.

[piseema]

Thanks again, can you please eloborate on what the runtime ( name ) is in esx? I am gogleing but not seeing any good info.

[mcowger]

The runtime name is the name VMware assigns to a newly idenitfied device that remains static for the duration of the time the system is up.