Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Clustering / April 2008

Tip: Looking for answers? Try searching our database.

The node lost communication with cluster

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Hasan - 15 Feb 2006 16:35 GMT
I have a cluster with 3 nodes, under SYSTEM in the event
viewer I receive those Warning message every 3 secondes.  

ID 1123:The node lost communication with cluster
node 'NODE1' on network 'PublicA'.
ID 1123:The node lost communication with cluster
node 'NODE3' on network 'PublicA'.
ID 1122:The node (re)established communication with
cluster node 'Node1' on network 'PublicA'.
ID 1122:The node (re)established communication with
cluster node 'Node2' on network 'PublicA'.

The cluster works well, the faileover works like it's
suppose to do but we want to eliminate this tons of
warning in the event viewer ...

We have already change the adapter, the cable, the switch
port, check the adapter config etc.... SO

Thanks...
John Toner [MVP] - 15 Feb 2006 17:09 GMT
Have you updated your NIC drivers?

Regards,
John

> I have a cluster with 3 nodes, under SYSTEM in the event
> viewer I receive those Warning message every 3 secondes.
[quoted text clipped - 16 lines]
>
> Thanks...
Geoff N. Hiten - 15 Feb 2006 17:28 GMT
Clusters with more than two nodes use multi-cast messages to send
cluster-wide communications.  Some switches have problems with multi-cast.
Then there is the issue of multi-cast addressing.  You can tell there is an
issue when you get an error message mentioning the absence of a MADCAP
server.  MADCAP is to multi-cast what DHCP is to single-cast IP.   Read up
on multicast IP messaging and you will likely find how to tune your network
switches to avoid this problem.

Signature

Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP

>I have a cluster with 3 nodes, under SYSTEM in the event
> viewer I receive those Warning message every 3 secondes.
[quoted text clipped - 16 lines]
>
> Thanks...
Hasan - 15 Feb 2006 19:51 GMT
Hi Geoff,

Thank you so much for your prompt attention.  This question was sent to you
on my behalf by one of my co-workers.  Thank you so much.  Have a great day.

> I have a cluster with 3 nodes, under SYSTEM in the event
> viewer I receive those Warning message every 3 secondes.  
[quoted text clipped - 16 lines]
>
> Thanks...
CShane - 23 Feb 2006 18:55 GMT
You may want to first verify that the Heartbeat Adapter is set at the top of
the intracluster communications list.  It looks like the server is sending
heartbeats across the public network.

Shane

> I have a cluster with 3 nodes, under SYSTEM in the event
> viewer I receive those Warning message every 3 secondes.  
[quoted text clipped - 16 lines]
>
> Thanks...
Denny - 24 Apr 2008 07:58 GMT
I need some help on how to correct getting Event ID 1123 and Event ID 1122 on one of two cluster nodes every hour or some times frequently. Two times a not main node was removed from active cluster membership(Event ID 1135). This is a two node cluster running Windows Server 2003 EE SP1 (NovaScale 3045 Itanium2 )

In the event viewer every hour on one of two cluster nodes I receive such Warnings(one after another):
a)Event ID – 1123. The node lost communication with cluster node 'Cluster0' on network 'Heartbeat Cluster Connection'.
b) Event ID – 1123. The node lost communication with cluster node ' Cluster0' on network 'Public Network Connection'.

Or the other way

a) Event ID – 1123. The node lost communication with cluster node ' Cluster0' on network 'Public Network Connection'.
b)Event ID – 1123. The node lost communication with cluster node 'Cluster0' on network 'Heartbeat Cluster Connection'.

I have already read such articles:
•    Recommended private "Heartbeat" configuration on a cluster server - http://support.microsoft.com/?id=258750
•    Multicast support enabled for the cluster heartbeat http://support.microsoft.com/default.aspx?scid=kb;EN-US;307962

I have replaced Heartbeat connection on another pair of NIC‘s but still have same problem.

Settings of my Connections

The Heartbeat connection:
a)    not using team adapter.
b)    Internal cluster communication only (private only)
c)    Cluster properties->Network priority:  set on upper level
d)    Network Connection->Advanced->Advanced Settings->Connections: not on upper level, after Private connection  
The Public connection:
a)    Using team adapter.
b)    All comunications (mixed network)
c)    Cluster properties->Network priority:  after Heartbeat (not on upper level)
d)    Network Connection->Advanced->Advanced Settings->Connections: set on upper level

May bee problem is in Heartbeat connection, or with node(which was removed from active cluster membership two times ) something wrong?

When I want to see Multicast configuration I type in CMD:  cluster „ClusterName“ network „NetworkName“ /priv
And then I see empty columns - /T/Network/Name/Value/.  Changing names of cluster and connection in command I have the same result. What does it means? The multicasting is enable or disable? And how to see corect Multicast settings?
I can disable multicasting  (but there is important data and I afraid to lost it!) This is a correct way, or what shall I do?

May bee you can help me to eliminate this problem? Any suggestions?

From http://www.developmentnow.com/g/99_2006_2_0_0_698577/The-node-lost-communication
-with-cluster.ht


Posted via DevelopmentNow.com Group
http://www.developmentnow.com
Anthony Thomas - 27 Apr 2008 20:17 GMT
Three things you should look at:

1. You cannot use the public network for internal cluster communications
(heartbeat) because it is in a teaming configuration, even if you have a
dedicated heartbeat established.  It is not supported.  Switch the public
network for Client Only communication.
http://support.microsoft.com/?id=254101.

2. Make sure you have followed the heartbeat configuration best practices.
http://technet2.microsoft.com/windowsserver/en/library/8638a855-0ea3-4428-84d5-f
745966ecb131033.mspx?mfr=true

and
http://technet2.microsoft.com/windowsserver/en/library/68d8ec40-3cda-46d7-bc13-4
a91764eaff81033.mspx?mfr=true
.

3. Make sure the public network has been optimized for network optimization.
The corresponding registry entry
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters Size value
should be set to 3.  http://support.microsoft.com/kb/892422.

Sincerely,

Anthony Thomas, MCDBA, MCSA
Senior Consultant
Sogeti USA

>I need some help on how to correct getting Event ID 1123 and Event ID 1122
>on one of two cluster nodes every hour or some times frequently. Two times
[quoted text clipped - 60 lines]
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.