MSCS: Outbound traffic to different subnet on wrong NIC

Discussion in 'Clustering' started by tachnem, Jul 21, 2007.

  1. tachnem

    tachnem Guest

    We've built a two node SQL05 cluster and a two node MSMQ cluster. Both
    clusters are experiencing this issue. Any outbound traffic to the same
    subnet goes out the appropriate public NIC. Any outbound traffic directed to
    a different subnet attempts to go out the private NIC. Both clusters have
    the private NICs connected via crossover cable. Traffic to other subnets
    will only make it's way if I disable the private NIC. I've verified this by
    running a netstat while attempting to ping and telnet.

    Here is an ipconfig, there are 3 cluster resource IPs on the public adapter,
    which also has the gateway. The private NIC is just the crossover with no
    gateway.

    I've tried setting metrics on the adapters, changing the private/public
    position in the Advanced Properties in Network Connections, and also in
    Cluster Admin setting the Private interfaces for internal communication only
    and the Public interfaces for client access only.


    Windows IP Configuration

    Ethernet adapter Public:
    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : 10.0.40.X
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IP Address. . . . . . . . . . . . : 10.0.40.X
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IP Address. . . . . . . . . . . . : 10.0.40.X
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IP Address. . . . . . . . . . . . : 10.0.40.X
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 10.0.40.X
    Ethernet adapter Private:
    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : 10.0.0.101
    Subnet Mask . . . . . . . . . . . : 255.0.0.0
    Default Gateway . . . . . . . . . :


    Here is a netstat on a telnet to a different subnet:
    TCP 10.0.0.101:3126 10.0.X.X:80 SYN_SENT 2664


    Any insight/suggestions into what could be causing this issue would be much
    appreciated.

    Thanks
     
    tachnem, Jul 21, 2007
    #1
    1. Advertisements

  2. This is a TCP/IP configuration problem. Your private network of 10/8 also
    includes 10.0/16 because you are using a class A mask. TCP/IP routing looks
    at the routing table and sees the 10.0.0.101 interface and thinks, because
    of the mask, that it will also include everything in 10.0.x.x.

    Change the subnet mask or change the private range to a different range,
    i.e. 192.168.0.0/24.

    --
    Russ Kaufmann
    MVP - Windows Server - Clustering
    ClusterHelp.com, a Microsoft Certified Gold Partner
    Web http://www.clusterhelp.com
    Blog http://msmvps.com/clusterhelp

    The next ClusterHelp classes are:
    Sep 3 - 6 in Copenhagen
    Oct 8 - 11 in New York
     
    Russ Kaufmann [MVP], Jul 22, 2007
    #2
    1. Advertisements

  3. tachnem

    tachnem Guest

    Thanks Russ! You were right.

     
    tachnem, Jul 22, 2007
    #3
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.