Why my event viewer is giving me this message

[Zahid_Haseeb]

i am using VCS (SFHA 5.0) and my SQL2005 is clustered with 2 nodes and the OS is win2003 datacentre edition. kindly suggest me Why my event viewer is giving me below message. I feel that NODE-1 is busy(because of virus or heavy work load) thats why its not able to send the LLT/GAB packets.....

Source: GAB   

Type:    information

The description for Event ID ( 18 ) in Source ( GAB ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:

Source:   LLT

Type:      Warning

The description for Event ID ( 10035 ) in Source ( LLT ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: , (ticks=273).

[Zahid_Haseeb]

kindly also help me that what is the meaning of the below notifications which i am getting by VCS notifier

Event Time: Wed Jan 28 06:16:47 2009

Entity Name:   DBCLUSTER-PRI

Entity Type: System

Entity Subtype: WINNT:  DBCLUSTER-PRI,5.2

Entity State: VCS is being restarted by hashadow Traps Origin: Veritas_Cluster_Server System Name: DBCLUSTER-PRI Entities Container Name: SQL_CLUSTER Entities Container Type: VCS

Event Time: Wed Jan 28 06:16:47 2009

Entity Name:   DBCLUSTER-PRI

Entity Type: System

Entity Subtype: WINNT:  DBCLUSTER-PRI,5.2

Entity State: A node running VCS has joined cluster Traps Origin: Veritas_Cluster_Server System Name: DBCLUSTER-PRI Entities Container Name: SQL_CLUSTER Entities Container Type: VCS

Message Edited by Zahid.Haseeb on 01-29-2009 10:01 PM

Message Edited by Zahid.Haseeb on 01-29-2009 10:01 PM

[Zahid_Haseeb · Accepted solution]

I have found my answer

thanks for the below link

http://mailman.eng.auburn.edu/pipermail/veritas-ha/2006-March/009595.html

http://sfdoccentral.symantec.com/sf/5.0MP3/aix/html/vcs_users/gl_vcs_users.html

It appears that VCS is abruptly going down and being restarted by
hashadow. This can be caused by the node on which it is running
at such a high load that GAB cannot heartbeat with
HAD. If GAB and VCS do not communicate for 15 seconds, HAD is killed by
GAB to ensure that HAD is not hung. Had is then restarted by hashadow.
The constant change in membership is evidence, plus the node goes to
FAULTED indicating that HAD abruptly terminated without sending messages
to partner Cluster NODE that it was leaving the cluster.