Use Static Discovery instead of Dynamic Discovery in VMware 5.0 settings
Noticed on our ESXi 5.0 hosts:
I try to enter iSCSI targets by type VirtualIP on Dynamic Discovery, first.
After rescan process, there are list of all discovered targets on Static Discovery tab.
Now, I can remove all list on Dynamic Discovery and physical IP targets on Static Discovery list.
There are only VirtualIP targets left on the Static list.
It's quite fast and "precise" methode.
And it should work!?! Yes and NO
It works till host is restarted.
iSCSI targets entered using Dynamic Discovery methode are some-how not saved in host initial configuration , but manually entered targets are.
So don't be lazy and define all targets with manual methode.
Last edited by Toni Bizjak; 03-03-2012 at 01:45 PM.
Already test the steps you mentioned, I already do the following :
- Go to Dynamic Discovery, add VIPs, save and close the discovery window.
- Go to Static Discovery, found all the VIPs there ( and removed the unwanted IPs ).
- Save and close the window.
- Run the Discovery window again, and all are there. so YES it should work fine.
Also could you please let us know which DSS version/build that you were using when you did the mentioned steps? you may update or downgrade your build to see if that makes any difference.
One more thing, please check the format of the target name, as it should be like this: iqn.year-month:hostname.target0
You can change the values of the host name, and the 'target0' but the format and punctuation must remain in order to enter them on the static tab in VMware.
And as an example : iqn.2013-6:HOST.target7
while the following example are wrong:
iqn.dss-san-a-0202.mirror0