VMware Cloud Community
muetstem
Enthusiast
Enthusiast

Software iSCSI static discovery returns after remove server target

I running a test with vSphere 5 using software iSCSI. I first used a network 192.168.1.0 for the iSCSI. I then created a separate network 172.20.0.0.

In the static section I delete the 192.168.1.45:3260  iSCSI server location and I created two new iSCSI server locations with the dynamic discovery 172.20.0.45:3260 and 172.20.0.46:3260. I rescaned the host bus adapter and the 192.168.1.45:3260 is back. I then deleted all iSCSI settings even the software iSCSI HBA, reboot the server, but when I install the iSCSI software HBA the iSCSI server location is back again. I think there is some config file with the iSCSI server location. Is this a known bug in ESX 5? and does anybody know how to remove the the iSCSI forever?

Thanks for the answer,

Greetings Michael Muetstege

PS I test this setting for a migration from vSphere 4.0 to 5.0

Reply
0 Kudos
6 Replies
jose_maria_gonz
Virtuoso
Virtuoso

uhnnn. very interesting finding.

Did you uninstall the iSCSI software before rebooting the host?

I hope I have helped you out

My Company: http://www.jmgvirtualconsulting.com

My Blog: http://www.josemariagonzalez.es

My Web TV show: http://www.virtualizacion.tv

My linkedin: http://es.linkedin.com/in/jmgvirtualconsulting

My Twitter: http://twitter.com/jose_m_gonzalez

Reply
0 Kudos
muetstem
Enthusiast
Enthusiast

Yes, that is in my story, I deinstall the iSCSI HBA and then I reboot te server.

After the iSCSI is installed the iSCSI server location in static Discovery is still showing the 192.168.1.45:3260 Target.

Greetings Michael

Reply
0 Kudos
psplnalin123
Enthusiast
Enthusiast

First of all delete the iSCSI SP ip address and remove the Path from the discovery options & disabled the iSCSI adapter and reboot the host if downtime available. Also check the vCenter database table whether the information is stored over there. If yes then delete the information. Right now i am not aware where it will store the information but yes there should be some table where it is stored  this information

Reply
0 Kudos
jose_maria_gonz
Virtuoso
Virtuoso

Hi there,

That is bizzare now. I have deleted IPs for my iSCSI SAN,  disabled iSCSI software initiator, reboot the host on my lab environment and it is clean as a whistle. What ESXi version and built do you have?

I hope I have helped you out

My Company: http://www.jmgvirtualconsulting.com

My Blog: http://www.josemariagonzalez.es

My Web TV show: http://www.virtualizacion.tv

My linkedin: http://es.linkedin.com/in/jmgvirtualconsulting

My Twitter: http://twitter.com/jose_m_gonzalez

Reply
0 Kudos
muetstem
Enthusiast
Enthusiast

Some information about this test setting: I run the test environment inside a VMWare workstation 8 on a laptop with lots of memory. I uses VMware v-Center Appliance version 5.0.0.3324-472350. The appliance is running direct into my Workstation 8 (not inside VMware vSphere). I run one ESXI 5.0.0 ESX server (VMKernel build 469512). For storage I use a Openfiler ISCSI target. On my laptop I run 64 bits Ubuntu 11.10 (uses less memory than Windows 7). Yesterday I did a test changing my network. I have a network for my virtual machines. This network is also used by my management interface. My management interface is on 192.168.1.60 and uses a bridged network with my wifi lan of my laptop. My Openfiler uses on the same network 192.168.1.45. First I used this network also for my iSCSI but I changed it to a nother network (seperated from 192.168.1.0) 172.20.0.0. The change I did yesterday was from 192.168.1.0 network bridged to my wifi to 192.168.2.0 host only network. I changed al nics to that segment. The Openfiler gets the IP adres 192.168.2.45 and my ESX management interface gets 192.168.2.60. Then I log in the vSphere client and I see that the iSCSI server target has changed to 192.168.2.45. This is weird, I do not have a VMKernel configured for iSCSI traffic on the network 192.168.2.0. The only VMKernel on that network is the management network and when I look into its settings I see: "iSCSI Port Binding: Disable"  When I go to edit of my management network in the general tab I see iSCSI port Bindig: Enabled, but is grayed out and I cannot change this setting.

The next test I will try is to set de management interface to factory default and look wat is happening.

Do I have discovered a new bug in vSphere 5?

Greetings Michael

Reply
0 Kudos
muetstem
Enthusiast
Enthusiast

I vind out that Openfiler publish the IP-address to the ESXi server. No bug in VMware ESXi in this case.

Problem solved

Reply
0 Kudos