sara2000
asked on
Removing LUN from Esxi host
We have six ex hosts in the cluster. The cluster is configured for HA and DRS.
i tired to remove an empty LUN (n vas or template) from all Esxis.
I was able to remove the guns from all five except the one.
My procedures are as below.
Select the ex and configuration-Storage adapter-iscsi initator properties-static discovery and remove (please note this is software iscsi initiator).
it remove the ip , but reappears after the re-scan.
I have been doing like this most of the time and was able to remove the Lun.,not sure why this ex does not remove on this ex host.
i tired to remove an empty LUN (n vas or template) from all Esxis.
I was able to remove the guns from all five except the one.
My procedures are as below.
Select the ex and configuration-Storage adapter-iscsi initator properties-static discovery and remove (please note this is software iscsi initiator).
it remove the ip , but reappears after the re-scan.
I have been doing like this most of the time and was able to remove the Lun.,not sure why this ex does not remove on this ex host.
gheist
You can do it with configuration profile from vcenter. It knows if the result needs reboot
There is no screenshot, however the LUN is probably "in use", later versions of vCenter check the LUNS before you try to remove.
Check no ISOS, or VMs, (disks) or logs are on the LUNs.
Also VMware HA might be using it as a heartbeat datastore.
Check no ISOS, or VMs, (disks) or logs are on the LUNs.
Also VMware HA might be using it as a heartbeat datastore.
Setting ESXi in maintenance mode is a good try too...
ASKER
Only diferent in the iscsi initiator properties is that this esxi has "dynamic discovery"
Do we need that, I am reluctant to remove it since this in production?
Do we need that, I am reluctant to remove it since this in production?
It is a predefined CGI variable and you cannot reset it.
You can try something like HHTTPPSS instead?
You can try something like HHTTPPSS instead?
if you remove iSCSI initiator, you lose all iSCSI LUNs.
if there anything in use on the LUN
if there anything in use on the LUN
Sorry for my last "wrong window" commentary.
ASKER
iscsi initiator properties has General, network configuration, Dynamic Discovery and static Discovery tabs.
The "dynamic discovery" has an ip address of the storage , Same time the static discover has ip address and LUN target iqn.
Do we have to have Dynamic Discovery entry?
The "dynamic discovery" has an ip address of the storage , Same time the static discover has ip address and LUN target iqn.
Do we have to have Dynamic Discovery entry?
Yes, I'm aware of the configuration, if you remove any details here, ALL LUNs will be lost to this server!
ASKER
Andrew,
Dell equallogic ip=192.168.1.10, it has four volumes.
The static discovery has only one ip 192.168.1.10:3260
in the static discovery we have four entries for four luns
192.168.10:3260 iqn.*8deleqallogic.vol***
192.168.1.10:3260 iqn.**....equallogic.vol2.
Why removing Dynamic Discovery is going to remove above static discovery entries ?
The static discovery is going to be there for there for those luns.
Dell equallogic ip=192.168.1.10, it has four volumes.
The static discovery has only one ip 192.168.1.10:3260
in the static discovery we have four entries for four luns
192.168.10:3260 iqn.*8deleqallogic.vol***
192.168.1.10:3260 iqn.**....equallogic.vol2.
Why removing Dynamic Discovery is going to remove above static discovery entries ?
The static discovery is going to be there for there for those luns.
Dynamic Discovery is populated, after you have filled in the Static Discovery.
Changing anythere here, is not the method to un-mounting LUNs from an ESXi server.
The next time, your server rescans the HBA, using 192.168.1.10, it will re-discover all the LUNs.
Browse the LUN, and check what is in use.
Changing anythere here, is not the method to un-mounting LUNs from an ESXi server.
The next time, your server rescans the HBA, using 192.168.1.10, it will re-discover all the LUNs.
Browse the LUN, and check what is in use.
ASKER
That lun has has nothing in it, totally empty.
This particular esxi is redicovering that lun, not the other esxi are rediscovering it. I think because of this dynamic discovery entry the esxi is re-discovering it. I may have to wait for downtime and exit to maintenance mode, vacate all the vms from this esxi and try to remove.
This particular esxi is redicovering that lun, not the other esxi are rediscovering it. I think because of this dynamic discovery entry the esxi is re-discovering it. I may have to wait for downtime and exit to maintenance mode, vacate all the vms from this esxi and try to remove.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This worked.