Routing issues with Windows Server 2008 and 2 nics: LAN and iSCSI

Will Swetnam — Mon, 19 Oct 2009 14:58:59 GMT

Hardware:
BLC7000 CTO enclosure
BL460C G6 blades
BLC BNT 1GBE2 Switches (installed in back of C7000)
2012L DC MSA

The blades are running Win Server 2008

If I have the nic enabled that is handling the iSCSI traffic, no other machines on the LAN network can contact the machine.

The server in question is a SQL server, one nic (I'll call it NIC1) connects to our LAN segment, the other nic (I'll call it NIC2) connects - via a different switch - to our MSA using iSCSI.

If NIC2 is disabled - other machines on the network can connect to the DB server (and ping it, eg) without issue.

As soon as NIC2 is enabled - other machines on the network can no longer connect to the db server. SQL Connect commands fail, as do PINGs.

If I then disable NIC2 again - traffic passes back and forth just fine.

I've done some searching and found that w/ Windows Server 2008 new "strong vs. weak" send/receive parameters have been added to the ipv4 protocol - defaulting to not allowing weak traffic. I've run the netsh comments to enable weak sends and receives with no luck.

For kicks and grins - to simplify the model - I've also disabled the ipv6 protocols on the NICs... no luck.

I've run microsoft's network monitor 3.3 and can see the pings or other requests hit the machine, but after the "ICMP: echo request message from 10.0.0.179 to 10.0.0.20" there is no other info on the packets - they just seem to get binned.

The iSCSI nic is the onboard 10GbE NC532i Multifunction BL-c Adapter, the LAN connection is on a mez card NC326m PCIe Dual Port Adapter.

Below I'll list an ipconfig /all and a route print from the machine when both NICs are enabled.

I'm trying to figure out why any traffic from the network hits the machine and then gets binned. Is there some sort of cross connect going on in the fabric of the midplane? Something else I'm missing?

Looking for some assistance from a fresh set of eyes...

Thanks in advance!

- Will

IPCONFIG /ALL:

Windows IP Configuration

Host Name . . . . . . . . . . . . : SV-DB01
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 5:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC532i Dual Port 10GbE Multifunction BL-c Adapter
Physical Address. . . . . . . . . : 00-25-B3-A4-A2-10
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.0.200.102(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC326m PCIe Dual Port Adapter
Physical Address. . . . . . . . . : 00-23-7D-A5-DA-86
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.0.0.20(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 209.244.0.3
209.244.0.4
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{A109AB3F-9D59-4C15-B749-1B407968E9ED}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:1cee:6aa:f5ff:ffeb(Preferred)
Link-local IPv6 Address . . . . . : fe80::1cee:6aa:f5ff:ffeb%17(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

*********************************

ROUTE PRINT:

===========================================================================
Interface List
14 ...00 25 b3 a4 a2 10 ...... HP NC532i Dual Port 10GbE Multifunction BL-c Adapter
10 ...00 23 7d a5 da 86 ...... HP NC326m PCIe Dual Port Adapter
1 ........................... Software Loopback Interface 1
16 ...00 00 00 00 00 00 00 e0 isatap.{A109AB3F-9D59-4C15-B749-1B407968E9ED}
28 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
17 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.1 10.0.0.20 20
10.0.0.0 255.255.255.0 On-link 10.0.0.20 266
10.0.0.20 255.255.255.255 On-link 10.0.0.20 266
10.0.0.255 255.255.255.255 On-link 10.0.0.20 266
10.0.200.0 255.255.255.0 On-link 10.0.200.102 266
10.0.200.102 255.255.255.255 On-link 10.0.200.102 266
10.0.200.255 255.255.255.255 On-link 10.0.200.102 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
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.20 266
224.0.0.0 240.0.0.0 On-link 10.0.200.102 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.20 266
255.255.255.255 255.255.255.255 On-link 10.0.200.102 266
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 10.0.0.1 10
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
17 18 ::/0 On-link
1 306 ::1/128 On-link
17 18 2001::/32 On-link
17 266 2001:0:4137:9e50:1cee:6aa:f5ff:ffeb/128
On-link
17 266 fe80::/64 On-link
17 266 fe80::1cee:6aa:f5ff:ffeb/128
On-link
1 306 ff00::/8 On-link
17 266 ff00::/8 On-link
===========================================================================
Persistent Routes:
None

Re: Routing issues with Windows Server 2008 and 2 nics: LAN and iSCSI

HEM_2 — Tue, 20 Oct 2009 13:40:08 GMT

is the Winodws Firewall service turned off? I've seen that cause issues like what you have described.

Re: Routing issues with Windows Server 2008 and 2 nics: LAN and iSCSI

Will Swetnam — Tue, 20 Oct 2009 13:43:49 GMT

Yes - firewall is turned off - the server is behind a firewall device.

Re: Routing issues with Windows Server 2008 and 2 nics: LAN and iSCSI

Kgarland80 — Thu, 11 Feb 2010 19:16:38 GMT

I was wondering if you solved this issue. We are experiencing a similar if not the same issue where we have NLB NICs that will send out traffic on NIC 2 with the wrong MAC address. The teamed MAC is set and as long as the traffic goes out on NIC 1 then it is returned correctly but if the traffic goes out on NIC two then the other MAC address is used even though it should use the teamed NIC MAC of the primary NIC.

topic Re: Routing issues with Windows Server 2008 and 2 nics: LAN and iSCSI in BladeSystem - General

Routing issues with Windows Server 2008 and 2 nics: LAN and iSCSI

Re: Routing issues with Windows Server 2008 and 2 nics: LAN and iSCSI

Re: Routing issues with Windows Server 2008 and 2 nics: LAN and iSCSI

Re: Routing issues with Windows Server 2008 and 2 nics: LAN and iSCSI