Saturday, May 23, Toggle navigation Gabes Virtual World. Next check in the network adapters list to what vmnic this is linked, in this example vmnic2. Reboot and you should be good. Right click the vSwitch, choose properties. Then I can type:.

Uploader: Shasar
Date Added: 19 September 2018
File Size: 51.93 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 97938
Price: Free* [*Free Regsitration Required]

I had to first determine the “interface number” of the NICs from the route print command:.

Here is the script I run on each iSCSI Boot initiator you would obviously change the ip number to suit your environment: By continuing to browse this site, you agree to this use. Proposed as answer by Samsonitered Tuesday, November 4, 3: I knew jntel settings that we set at OS level will be overrode by such software.

Downloads for IntelĀ® Gigabit ET Dual Port Server Adapter

On the first tab you can set CHAP authentication if needed. In this specific configuration that meant setting vmnic3, vmnic4 and vmnic5 to unused and only add vmnic2 as active. Easiest inhel to right click the vmhba adapter and open the properties tab.


The route deletion failed: Yes I can script it. Tuesday, November 22, 2: Thursday, November 24, 7: Toggle navigation Gabes Virtual World. Tuesday, November 4, 5: Sign in to vote.

Wednesday, November 23, 6: This can be beneficial to other community members reading the thread. Thanks for posting here.

Intel ET Quad ports + iSCSI ?? |VMware Communities

Tuesday, July 21, 9: Then I can type: Sunday, November 27, 1: Next check in the network adapters list to what vmnic this is linked, in this example vmnic2. However, I still got the undesired routes in the routing table.

Of course we can also let system automatically do these by customizing these commands into a script file and run it after completed start. Resources for IT Professionals. I did not configure a default route in the Intel setup utility: This is very important!!

Can you verify that? Firstly thanks to Ben-Tempus for highlighting this issue and providing a temporary workaround.


Office Office Exchange Server. Proposed as answer by Samsonitered Wednesday, November 5, 4: Saturday, May 23, After configuring the vmkernel interface we now need to attach the vmkernel interface to the vmhba. Everything boots as 882576. My issue is that the iSCSI networks show up in the routing table like so:. The last part is the mac address.