The easiest test is to just shutdown the port on the physical switch connected to the first vmhba and then see if the failover works. Can you verify that? To connect the second vmhba, you should follow the same steps again. Saturday, May 23, I was able to delete them manually from the command line.
|Date Added:||3 October 2010|
|File Size:||43.40 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Have you installed any NIC configuration software from Intel on this server? Switch to the Storage Adapters section and select the vmhba that correspondents to the vmnic you just configured the inrel interface for. Can you verify that?
I had to first determine the “interface number” of the NICs from the route print command: I agree that changing the routing metric on the interfaces is the solution.
By continuing to browse this site, you agree to this use. This may be many years too late but I think I may have a solution for this. Sunday, November 27, 1: I did not configure a default route in the Intel setup utility: Reboot and you should be good.
Learn Which Adapters Support Intel® iSCSI Remote Boot
In this specific configuration that meant setting vmnic3, vmnic4 and vmnic5 to unused and only add vmnic2 as active. I insured that my DHCP server gave out no default gateway entry. OK, I figured out how to manually delete the entries. So, Tiger Li, I take it from your response that I am just stuck with this “reality” and need to implement the workaround?
Tuesday, November 22, 2: The parameter is incorrect. I don’t want my iSCSI traffic to ever show up with a default route. Echo off Rem fixes iscsi route problem as shown below: I had to first determine the “interface number” of the NICs from the route print command:.
Edited by Max Saturday, May 23, Easiest is to right click the vmhba adapter and open the properties tab. Not an IT pro? Then I can type: Next add it to corresponding vmhba.
Dependent hardware iSCSI adapter on ESXi5
I was able to delete them manually from the command line. The target is configured correctly. Thanks for posting here. After pressing OK and a rescan of the vmhba, you should now see the LUN s that have been presented to your host. After configuring the vmkernel interface we now need to attach the vmkernel interface to the vmhba. The easiest test is to just shutdown the port on the physical switch connected to the first vmhba and then see if the failover works.
My issue is that the iSCSI networks show up in the routing table like so: Tuesday, November 4, 5: Remove From My Forums.
Office Office Exchange Server.