[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 398
  • Last Modified:

Microsoft Cluster Crossover traffic

We have set up a new environment behind an ASA firewall with multiple vlans off of the firewall.   We have three different clusters that have been set up in different vlans, these are windows server 2003 64bit boxes.  We have set up these clusters with crossover cables for the heartbeats.  The problem we are having on all three clusters is that even though we have not put a gateway on the interfaces of the crossovers we are seeing denies in the firewall with a source address of the crossovers.  I don't know if it makes any difference but that address that they are trying to reach are the addresses of our SAN Controllers on port 137. Weird thing is that we have the same environment set up as a "test" environment behind a different firewall and we are not seeing this traffic from the cluster's set up in this environment.  We are using 192.168.100.200 and 201 on one of the servers for the heartbeat, and 10.10.10.x for the other two.  Any help would be greatly appreciated.
0
jiggin23
Asked:
jiggin23
  • 5
  • 5
1 Solution
 
65tdCommented:
Have the appropriate check boxes been cleared on the heartbeat nic properties page?

See:
http://support.microsoft.com/kb/258750
0
 
sabkCommented:
In the heartbeat NIC properties ,Please uncheck all the other option except Internet Protocol(TCP/IP0 and then check.

AB
0
 
jiggin23Author Commented:
I unchecked all the boxes from the crossover nic properties page on one of the clusters, but still seeing denies from that nic's ip (192.168.100.200 and 201).
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
65tdCommented:
From cluster manager is the heart beat configured for Internal traffic only?
0
 
jiggin23Author Commented:
Yes
0
 
65tdCommented:
Need to review the heartbeat settings as port is NetBIOS (name service (UDP)) port.

Could run a network monitor on production nics, using MS network monitor 3.2 looking for the bad requests.

From a cmd prompt review route print or a netstat -r and look for IP address and gateway.
0
 
jiggin23Author Commented:
I have attached a screen shot of the "netstat -r" from one of the trouble boxes.
netstat-r.doc
0
 
65tdCommented:
The clusters here have the following netstat -r information:

C:\WINDOWS\system32>netstat -r

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 19 b9 af a9 81 ...... BASP Virtual Adapter
0x10004 ...00 10 18 26 e0 4c ...... Broadcom BCM5708C NetXtreme II GigE (NDIS VB
D Client) #2
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      1xx.yy.zz..1     1xx.yy.zz.47     10
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
     1xx.yy.zz.0    255.255.255.0     1xx.yy.zz.47     1xx.yy.zz.47     10
     1xx.yy.zz.47  255.255.255.255        127.0.0.1        127.0.0.1     10
     1xx.yy.zz.49  255.255.255.255        127.0.0.1        127.0.0.1     10
     1xx.yy.zz.50  255.255.255.255        127.0.0.1        127.0.0.1     10
   1xx.yy.255.255  255.255.255.255     1xx.yy.zz.47     1xx.yy.zz.47     10
     192.168.30.0    255.255.255.0    192.168.30.13    192.168.30.13     20
    192.168.30.13  255.255.255.255        127.0.0.1        127.0.0.1     20
   192.168.30.255  255.255.255.255    192.168.30.13    192.168.30.13     20
        224.0.0.0        240.0.0.0     1xx.yy.zz.47     1xx.yy.zz.47     10
        224.0.0.0        240.0.0.0    192.168.30.13    192.168.30.13     20
  255.255.255.255  255.255.255.255     1xx.yy.zz.47     1xx.yy.zz.47      1
  255.255.255.255  255.255.255.255    192.168.30.13    192.168.30.13      1
Default Gateway:       1xx.yy.zz.1
===========================================================================
Persistent Routes:
  None
0
 
jiggin23Author Commented:
They look the same to me, am I missing something?
0
 
65tdCommented:
Looked the same to me as well except for the metrics which should be good.

Try network monitor (note the versions):
http://www.microsoft.com/DownLoads/details.aspx?FamilyID=f4db40af-1e08-4a21-a26b-ec2f4dc4190d&displaylang=en
0
 
jiggin23Author Commented:
Found the problem.  Under Advannced TCP/IP Settings I disabled NetBIOS over TCP/IP and this fixed the problem.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now