Windows Server

Franky M. · Guest

I have a 2 node Exchange 2003 cluster.
Private NIC is at 1 Gbps
Network NIC is at 100 Mbps

When doing backups I keep getting... (every few seconds for the entire time
the backup goes, it just goes up and down. Does not fail over.) Should I
just extend the heartbeat or ???

Event Type: Warning
Event Source: ClusSvc
Event Category: Node Mgr
Event ID: 1123
Date: 11/8/2005
Time: 5:47:26 AM
User: N/A
Computer: HALO
Description:
The node lost communication with cluster node 'EAGLE' on network 'Network'.

MarkFox · Guest

Franky,

Mine shows;
T Cluster Name Value

-- -------------------- ------------------------------ -----------------------

S mailcluster02 MSExchange_InstallDestDir D:\Exchsrvr

S mailcluster02 MSExchange_Domain (not Shown)

D mailcluster02 MulticastClusterDisabled 1 (0x1)

Not sure if this means Multicast is enabled, the command to disable it was
given to me by MS Support, c:\cluster clustername /priv
MulticastClusterDisabled=1:DWORD
If you decide to do it please make sure you typed it correctly, it WILL
accept a bogus command for this.
The only gotcha on this is that each node may need to be rebooted after this
done for the 1122/23's to stop. This is a cluster wide command so you only do
it once as opposed to on each node.
I have one 4 node Exchange cluster and one 3 node Exchange cluster and I had
to do this on both clusters.
--
Mark

"Franky M." wrote:

MarkFox · Guest

Franky,

Are you sure the Private - HeartBeat properties are set to Internal
Communications only in cluster admin? Typically these messages show up when
adding a third node to the Win2k3 cluster since that triggers multicast to
become enabled. At a command prompt C:\cluster clustername /priv, if it
comes up with MulticastClusterEnabled this could also be part of your problem.

Hope this helps, BTW nice servername HALO, why not MasterCheief? :)
--
Mark

"Franky M." wrote:

Franky M. · Guest

typing "cluster rhino /priv"
just shows me this... ?

T Cluster Name Value
-- -------------------- ------------------------------ ---------------------
S rhino MSExchange_InstallDestDir F:\Program Files\Exch
S rhino MSExchange_Domain (rather not post this)

"MarkFox" wrote:

Rodney R. Fournier [MVP] · Guest

This is not the problem, multicast is only enabled when you have 3 or more
Windows Server 2003 nodes. Franky has a two node cluster.

Have tried hardcoding the Speed and Duplex to 1000 Full on both nodes?

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training

"MarkFox" <MarkFox@discussions.microsoft.com> wrote in message
news:0B830F1D-1134-4174-B1AC-399B0904C824@microsoft.com...

Rodney R. Fournier [MVP] · Guest

This turns off the Multicast of heartbeats. You could have done one of two
other things, configured a MCAP DHCP server on the subnet or hardcode 240 IP
Addrs for the heartbeat nics.

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training

"MarkFox" <MarkFox@discussions.microsoft.com> wrote in message
news:2EF3B9C1-61D4-4545-B8D0-7273A345056B@microsoft.com...

Mark Bradley · Guest

It may be useful to look at the following extract.

Communication between Server Cluster nodes is critical for smooth cluster
operations. Therefore, you must configure the networks that you use for
cluster communication are configured optimally and follow all hardware
compatibility list requirements. For networking configuration, two or more
independent networks must connect the nodes of a cluster to avoid a single
point of failure. The use of two local area networks (LANs) is typical.
(Microsoft Product Support Services does not support the configuration of a
cluster with nodes connected by only one network.)

At least two of the cluster networks must be configured to support heartbeat
communication between the cluster nodes to avoid a single point of failure.
To do so, configure the roles of these networks as either "Internal Cluster
Communications Only" or "All Communications" for the Cluster service.
Typically, one of these networks is a private interconnect dedicated to
internal cluster communication.

Additionally, each cluster network must fail independently of all other
cluster networks. This means that two cluster networks must not have a
component in common that can cause both to fail simultaneously. For example,
the use of a multiport network adapter to attach a node to two cluster
networks would not satisfy this requirement in most cases because the ports
are not independent.

To eliminate possible communication issues, remove all unnecessary network
traffic from the network adapter that is set to Internal Cluster
communications only (this adapter is also known as the heartbeat or private
network adapter). Clustering communicates by using Remote Procedure Call
(RPC) calls on IP sockets with User Datagram Protocol (UDP) packets. The
process described in this article:
Removes NetBIOS from the interconnect.
Sets the proper Cluster communication priority order.
Sets the proper adapter binding order.
Defines the proper network adapter speed and mode.
Configures TCP/IP correctly.
Disable the Media Sense feature (in Windows 2000 only).
MORE INFORMATION
Recommended Configuration for the Private Adapter in Windows 2000 and
Windows 2003
Click Start, point to Settings, click Control Panel, and then double-click
Network and Dial-up Connections.
On the Advanced menu, click Advanced Settings.
In the Connections box, make sure that your bindings are in the following
order, and then click OK:
External public network
Internal private network (Heartbeat)
[Remote Access Connections]
Right-click the network connection for your heartbeat adapter, and then
click Properties.

Note: You may want to rename this connection for simplicity (for example,
rename it to "Private").
On the General tab, make sure that only the Internet Protocol (TCP/IP) check
box is selected. Click to clear all other check boxes.

WARNING: If you fail to clear all check boxes except TCP/IP, you could
experience random and unexpected connectivity problems.
If you have a network adapter that can transmit at multiple speeds, and the
adapter can specify a speed and duplex mode, manually specify a speed and
duplex mode.

With network adapters that can manually specify a speed and duplex mode,
make sure that you hard set them to the same on all nodes and according to
the manufacturers' specifications. For network adapters that do not support
manual settings, follow the card manufacturer's specifications.

The information that is traveling across the heartbeat network is small, but
latency is critical for communication. If you have the same the speed and
duplex settings, this helps to make sure that you have reliable
communication.

If you are not sure of the supported speed of your card and connecting
devices, or your manufacturer's recommended settings, Microsoft recommends
that you set all the devices on that path of 10 MB/Sec and Half Duplex. This
configuration will provide sufficient bandwidth and reliable communication.
For additional information, click the article number below to view the
article in the Microsoft Knowledge Base:

174812 Effects of Using Autodetect Setting on Cluster Network Interface Card
(NIC)

Note: Microsoft does not recommend the use of any type of fault-tolerant
adapter or "Teaming" for the heartbeat. If you require redundancy for your
heartbeat connection, use multiple network adapters set to Internal
Communication Only and define their network priority in the Cluster
configuration. Issues seen with early multi-ported network adapters, verify
that your firmware and driver are at the most current revision if you use
this technology.

Contact your network adapter manufacturer for information about
compatibility on a Server Cluster.

For additional information, click the article number below to view the
article in the Microsoft Knowledge Base:

254101 Network Adapter Teaming and Server Clustering

Click Internet Protocol (TCP/IP), and then click Properties.
On the General tab, verify that you have selected a static IP address that
is not on the same subnet or network as another one of the public network
adapters. An example of good IP addresses to use for the private adapters is
10.10.10.10 on node 1 and 10.10.10.11 on node 2 with a subnet mask of
255.0.0.0. If your public network uses the 10.x.x.x network and 255.0.0.0
subnet mask please use an alternate private network IP and subnet.

For additional information about valid IP addressing for a private network,
click the article number below to view the article in the Microsoft Knowledge
Base: 142863 Valid IP Addressing for a Private Network

Make sure that there is no value set in the Default Gateway box.
Verify that there are no values defined in the Use the following DNS server
addresses box.

Note: If the cluster nodes are also DNS servers, "127.0.0.1" is displayed in
the Use the following DNS server addresses box (the box will not be blank);
this is acceptable.
Click Advanced.
On the DNS tab, verify that there are no values defined. Make sure that the
Register this connection's addresses in DNS and Use this connection's DNS
suffix in DNS registration check boxes are cleared.
On the WINS tab, verify that there are no values defined. Click Disable
NetBIOS over TCP/IP.
When you close the dialog box, you may receive the following prompt. If you
receive this prompt, click Yes:

This connection has an empty primary WINS address. Do you want to continue?
Complete the previous steps on all other nodes in the cluster.
Start Cluster Administrator.
Click the cluster name at the root of Administrator. On the File menu, click
Properties.
On the Network Priority tab, verify that the private network is listed at
the top. If it is not, use the Move Up button to increase its priority.
Click the private network, and then click Properties.
Click to select the Enable this network for cluster use check box.
Click Internal cluster communications only (private Network).

"Rodney R. Fournier [MVP]" wrote:

	Windows Server Forum Index -> Clustering	All times are GMT
Page 1 of 1