As I understand you .......... If you have Storage port binding then the chosen NIC's are only talking to the SAN .... if you remove NIC's from the port group or want to do away with SAN connection then ESXi will be ok however there will dead paths and the storage will be gone from that esxi ..... be careful here
I have always been doing Port binding with Dynamic Port ..... why do you want to do away with dynamic binding --- what is that you are trying to achieve
If you remove the VMkernel interfaces from the port binding configuration, the iSCSI connections will disconnect and reconnect to the LUN.
The use of dynamic or static binding depends on your configuration. If you use dynamic binding all available network interfaces on the storage system will be used to connect to. If you do not want to connect to all network interfaces you will need to use static binding. If it is possible on the storage system to restrict the available network interfaces to be seen by the hosts, you can also use dynamic binding.
We are using EMC VNX. It has active-active storage processors. VNX's best practice is not to use port binding.
I am not going to remove vmkernel. I am trying to remove port binding.
Yes, I understand. You want to remove the VMkernel interface port binding from the iSCSI adapter. If you do this, a disconnect and reconnect of the iSCSI connection will occur.
I did unbind the vmk on both nics (vmk3 on vmnic3 and vmk5 was on vmnic5). Esxi host was disconnected from all data stores. i rebooted the esxi and did not reconnect the datastore.
Here is the message on the vDswitch when i click on network port binding tab" No VMkernel network adapters are bound to this iscsi host bus adapter"
Is it because I am not using iSCSI HBA?