I agree with asrarguna that this should be a VM only network (not vmkernel, so don't check the box). My recommendation was to take a NIC from the current bundle that makes up the VM guest network (as opposed to mgmt.). Removing/re-adding ESXi host management NICs could cause a blip on the host (i.e. false isolation event). Since you are moving around what seems to be a mgmt. NIC, you might consider unchecking the "Enable Host Monitoring" setting on the cluster while working on this issue. To do so, right-click the cluster, then navigate to Edit Settings > vSphere HA > Enable Host Monitoring, then uncheck the box for "Enable Host Monitoring". Failure to do so may cause an HA event.
Also, you should consider using the vmxnet3 adapter. Anything else is a risk (there are known issues with the e1000 and e1000e). Looking at the screenshot, I see all vNICs have been removed from this VM and you are adding a new vNIC. Make it vmxnet3 and log in locally to set the IP address on this vCenter VM. Once connected and pingable, flip it back to the proper DVS port group.
PS - Nice 40Gb NICs! Are you running the new Nexus 9k's?