EDIT:
I am now thinking that this is a bug. When ESXi is installed to an iSCSI target, the static iSCSI target is created automatically. Even after the initial iSCSI target is no longer in service (as a new iSCSI target is created connecting to the same LUN), the initial iSCSI target still cannot be removed.
What I do:
From the vSphere client;
Configuration -> Storage Adapters -> iSCSI Software adapter vmhba38 -> Properties -> Static Discovery -> Highlight the iSCSI Server Location that I want to remove and click Remove.
I receive the following error.
Call "HostStorageSystem.RemoveInternetScsiStaticTargets" for object "storageSystem" on ESXi "192.168.2.10" failed.
What I am trying to accomplish:
Originally I had a single connection between my hypervisor and my LAN (192.168.2.0/24) that all traffic flowed over. All of my virtual machines live on iSCSI Luns on my SAN. Even my hypervisor boots over iSCSI. Now I would like to have a dedicated link between my hypervisor and my SAN.
I've created a new vmkernel port configured for a new network (172.16.1.0/24) and added an available physical adapter to it. I added a direct cable connection between the hypervisor and the SAN and configured the adapter on the SAN to be on the same new network.
I then added a new static iSCSI target using the new network, rescanned all HBAs, and I now have a new iSCSI connection to the SAN. I also reconfigured bootup so the iSCSI connection used to boot ESXi uses the new network.
All of that works. What doesn't work is removing the old iSCSI target and I don't know why. The error is always the same. I have rebooted many times, and I've disconnected the SAN from my LAN such that I know the legacy iSCSI connection cannot be established upon boot.
What can I do?
Thanks,
Donald
Message was edited by: seijirou