iSCSI boot with Intel NICs added to windows 2008 r2 routing table causes non iscsi traffic to attempt default routes on iscsi networks
I have a server with Intel 82576 Gigabit Dual Port Nics. I have configured them to use iSCSI boot the primary looks to 10.0.0.1/24 and the secondary looks to 10.0.1.1/24. The target is configured correctly. Everything boots as expected. I have added the MPIO feature and configured MPIO for the iscsi initiator as per: http://blogs.technet.com/b/migreene/archive/2009/08/29/3277914.aspx. My issue is that the iSCSI networks show up in the routing table like so: I did not configure a default route in the Intel setup utility: I tried to explicitly remove the 0.0.0.0 entry and leave blank, with no change. As you can see with the above routing table traffic attempts to travel over these routes: C:\Users\Administrator>ping google.com Pinging google.com [209.85.145.99] with 32 bytes of data: Reply from 10.0.0.201: Destination host unreachable. Reply from 10.0.1.201: Destination host unreachable. Reply from 209.85.145.99: bytes=32 time=23ms TTL=51 Reply from 209.85.145.99: bytes=32 time=22ms TTL=51 Ping statistics for 209.85.145.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: A ping to the outside world first attempts on 10.0.0.x/24 network, then on 10.0.1.x/24 network and then finally on the network the traffic should go over. I don't want my iSCSI traffic to ever show up with a default route. How do I get rid of it? route delete 0.0.0.0 mask 0.0.0.0 "on-link" results in: The route deletion failed: The parameter is incorrect. route delete 0.0.0.0 mask 0.0.0.0 on-link results in: The route deletion failed: The parameter is incorrect. route delete 0.0.0.0 deletes all default routes, then I have to add back in the "valid default route" of 192.168.100.6. I would like to not have to do a route delete though.
November 22nd, 2011 9:04am

OK, I figured out how to manually delete the entries. I had to first determine the "interface number" of the NICs from the route print command: =========================================================================== Interface List 24...00 25 90 14 cc 19 ......Intel(R) 82599 Dual 10 Gigabit Network Connection #2 23...00 25 90 14 cc 18 ......Intel(R) 82599 Dual 10 Gigabit Network Connection 19...00 25 90 0e 15 25 ......Intel(R) PRO/1000 PT Dual Port Network Connection #4 18...00 25 90 0e 15 24 ......Intel(R) PRO/1000 PT Dual Port Network Connection #3 17...00 25 90 0e 15 27 ......Intel(R) PRO/1000 PT Dual Port Network Connection #2 15...00 25 90 0e 15 26 ......Intel(R) PRO/1000 PT Dual Port Network Connection 12...00 25 90 14 cc 1b ......Intel(R) 82576 Gigabit Dual Port Network Connection #2 11...00 25 90 14 cc 1a ......Intel(R) 82576 Gigabit Dual Port Network Connection 1...........................Software Loopback Interface 1 13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 16...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3 20...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4 21...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #5 22...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #6 25...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #7 26...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #8 =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 On-link 10.0.0.201 266 0.0.0.0 0.0.0.0 On-link 10.0.1.201 266 0.0.0.0 0.0.0.0 192.168.100.6 192.168.100.127 266 10.0.0.0 255.255.255.0 On-link 10.0.0.201 266 10.0.0.1 255.255.255.255 On-link 10.0.0.201 266 10.0.0.201 255.255.255.255 On-link 10.0.0.201 266 10.0.0.255 255.255.255.255 On-link 10.0.0.201 266 10.0.1.0 255.255.255.0 On-link 10.0.1.201 266 10.0.1.1 255.255.255.255 On-link 10.0.1.201 266 10.0.1.201 255.255.255.255 On-link 10.0.1.201 266 10.0.1.255 255.255.255.255 On-link 10.0.1.201 266 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 192.168.100.0 255.255.255.0 On-link 192.168.100.127 266 192.168.100.127 255.255.255.255 On-link 192.168.100.127 266 192.168.100.255 255.255.255.255 On-link 192.168.100.127 266 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 10.0.0.201 266 224.0.0.0 240.0.0.0 On-link 10.0.1.201 266 224.0.0.0 240.0.0.0 On-link 192.168.100.127 266 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 10.0.0.201 266 255.255.255.255 255.255.255.255 On-link 10.0.1.201 266 255.255.255.255 255.255.255.255 On-link 192.168.100.127 266 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 192.168.100.6 Default =========================================================================== In my case it was the bold entries above interface numbers 11 & 12. I knew this by comparing ipconfig results for the names of the interfaces. Then I can type: route delete 0.0.0.0 mask 0.0.0.0 if 11 route delete 0.0.0.0 mask 0.0.0.0 if 12 However, I still do not want the Intel iSCSI DHCP responder in the NIC to return a default route in the first place, any Ideas?
Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2011 9:45am

Yes I can script it. I suppose I can even use task scheduler to make sure the script runs on boot, but I guess I find it incomprehensible how a feature now so prevalent as iSCSI boot requires such a workaround. Why does Intel's card respond to the DHCP request with gateway setting when none is specified? So, Tiger Li, I take it from your response that I am just stuck with this "reality" and need to implement the workaround?
November 23rd, 2011 8:31am

Hi Ben, Thanks for posting here. Have you installed any NIC configuration software from Intel on this server ? I knew some settings that we set at OS level will be overrode by such software. Can you verify that ? If system will keep binding the default route to this interface even if we empty the gateway entry on this interface ,we might also try to change the interface binding to make the interface 192.168.100.127 top one to see how is going: Thanks. Tiger LiPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
November 24th, 2011 2:12am

A valiant effort for an idea, however, the nics being used for ISCI are already low in the order:
November 26th, 2011 8:11pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics