09-22-2010 03:20 AM
Any body can help me in reading the below logs step by step please
2010/08/25 09:51:22 VCS INFO V-16-1-50135 User admin fired command: haconf -dump from 127.0.0.1
2010/08/25 10:47:41 VCS INFO V-16-1-50133 User admin has logged in from 127.0.0.1
2010/08/25 10:49:52 VCS INFO V-16-1-50135 User admin fired command: hagrp -freeze -persistent sql-Sgroup from 127.0.0.1
2010/08/25 10:49:55 VCS INFO V-16-1-50135 User admin fired command: haconf -dump from 127.0.0.1
2010/08/25 11:33:45 VCS INFO V-16-1-10077 Received new cluster membership
2010/08/25 11:33:45 VCS NOTICE V-16-1-10112 System (DBSERVER-B) - Membership: 0x2, DDNA: 0x1
2010/08/25 11:33:45 VCS ERROR V-16-1-10113 System DBSERVER-A (Node '0') is in DDNA Membership - Membership: 0x2, Visible: 0x0
2010/08/25 11:33:45 VCS NOTICE V-16-1-10449 Group sql-Sgroup autodisabled on node DBSERVER-A until it is probed
2010/08/25 11:33:47 VCS WARNING V-16-1-11155 LLT heartbeat link status changed. Previous status = 0x0; Current status = 0x3.
2010/08/25 11:34:29 VCS INFO V-16-1-10077 Received new cluster membership
2010/08/25 11:34:29 VCS NOTICE V-16-1-10112 System (DBSERVER-B) - Membership: 0x3, DDNA: 0x0
2010/08/25 11:34:29 VCS NOTICE V-16-1-10322 System (Node '0') changed state from UNKNOWN to INITING
2010/08/25 11:34:29 VCS NOTICE V-16-1-10086 System DBSERVER-A (Node '0') is in Regular Membership - Membership: 0x3
2010/08/25 11:34:29 VCS NOTICE V-16-1-10453 Node: 0 changed name from: 'DBSERVER-A' to: 'DBSERVER-A'
2010/08/25 11:34:29 VCS NOTICE V-16-1-10322 System DBSERVER-A (Node '0') changed state from FAULTED to INITING
2010/08/25 11:34:29 VCS NOTICE V-16-1-10322 System DBSERVER-A (Node '0') changed state from INITING to CURRENT_DISCOVER_WAIT
2010/08/25 11:34:29 VCS NOTICE V-16-1-10322 System DBSERVER-A (Node '0') changed state from CURRENT_DISCOVER_WAIT to REMOTE_BUILD
2010/08/25 11:34:29 VCS INFO V-16-1-10463 Sending snapshot to node: 0
2010/08/25 11:34:32 VCS NOTICE V-16-1-10322 System DBSERVER-A (Node '0') changed state from REMOTE_BUILD to RUNNING
2010/08/25 11:34:33 VCS INFO V-16-1-10304 Resource sql-Sgroup-IP (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/08/25 11:34:33 VCS INFO V-16-1-10304 Resource sql-Sgroup-RegRep-MSSQL (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/08/25 11:34:34 VCS INFO V-16-1-10304 Resource sql-Sgroup-Lanman (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/08/25 11:35:54 VCS INFO V-16-1-10304 Resource sql-Sgroup-VMDg (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/08/25 11:35:55 VCS INFO V-16-1-10304 Resource sql-Sgroup-MountV (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/08/25 11:35:55 VCS INFO V-16-1-10304 Resource Rtable (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/08/25 11:35:55 VCS INFO V-16-1-10304 Resource ABC_Live (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/08/25 11:35:55 VCS INFO V-16-1-10304 Resource GGG-HHH (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/08/25 11:35:55 VCS INFO V-16-1-10304 Resource BBB (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/08/25 11:35:55 VCS INFO V-16-1-10304 Resource T_Log (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/08/25 11:36:30 VCS INFO V-16-1-50135 User admin fired command: MSGROUP_RES_PROBE sql-Sgroup-SQLServer2005 DBSERVER-A from 127.0.0.1
2010/08/25 11:36:30 VCS INFO V-16-1-10304 Resource sql-Sgroup-SQLServer2005 (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/08/25 11:36:30 VCS NOTICE V-16-1-10438 Group sql-Sgroup has been probed on system DBSERVER-A
2010/08/25 11:36:30 VCS NOTICE V-16-1-10435 Group sql-Sgroup will not start automatically on System DBSERVER-A as the system is not a part of AutoStartList attribute of the group.
2010/08/25 11:36:38 VCS INFO V-16-1-50135 User admin fired command: hagrp -unfreeze -persistent sql-Sgroup from 127.0.0.1
2010/08/25 11:36:41 VCS INFO V-16-1-50135 User admin fired command: haconf -dump from 127.0.0.1
2010/08/25 11:36:42 VCS INFO V-16-1-50135 User admin fired command: haconf -dump from 127.0.0.1
2010/08/25 11:41:31 VCS INFO V-16-1-10306 Resource sql-Sgroup-SQLServer2005 (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (Previous State = OFFLINE)
2010/08/27 09:05:25 VCS INFO V-16-1-50133 User admin has logged in from 127.0.0.1
2010/08/30 09:27:57 VCS INFO V-16-1-50133 User admin has logged in from 127.0.0.1
2010/09/02 16:16:13 VCS INFO V-16-1-50133 User admin has logged in from 127.0.0.1
2010/09/05 20:32:39 VCS INFO V-16-1-10077 Received new cluster membership
2010/09/05 20:32:39 VCS NOTICE V-16-1-10112 System (DBSERVER-B) - Membership: 0x2, DDNA: 0x0
2010/09/05 20:32:39 VCS ERROR V-16-1-10079 System DBSERVER-A (Node '0') is in Down State - Membership: 0x2
2010/09/05 20:32:39 VCS ERROR V-16-1-10322 System DBSERVER-A (Node '0') changed state from RUNNING to FAULTED
2010/09/05 20:32:39 VCS WARNING V-16-1-11155 LLT heartbeat link status changed. Previous status = 0x3; Current status = 0x0.
2010/09/05 20:32:40 VCS INFO V-16-6-15004 (DBSERVER-B) hatrigger:Failed to send trigger for sysoffline; script doesn't exist
2010/09/06 11:53:53 VCS INFO V-16-1-50133 User admin has logged in from 127.0.0.1
2010/09/06 13:41:31 VCS INFO V-16-1-50133 User admin has logged in from 127.0.0.1
2010/09/06 13:43:09 VCS INFO V-16-1-50135 User admin fired command: hagrp -freeze -persistent sql-Sgroup from 127.0.0.1
2010/09/06 13:43:13 VCS INFO V-16-1-50135 User admin fired command: haconf -dump from 127.0.0.1
2010/09/06 14:47:53 VCS WARNING V-16-1-11155 LLT heartbeat link status changed. Previous status = 0x0; Current status = 0x3.
2010/09/06 14:47:59 VCS INFO V-16-1-10077 Received new cluster membership
2010/09/06 14:47:59 VCS NOTICE V-16-1-10112 System (DBSERVER-B) - Membership: 0x2, DDNA: 0x1
2010/09/06 14:47:59 VCS ERROR V-16-1-10113 System DBSERVER-A (Node '0') is in DDNA Membership - Membership: 0x2, Visible: 0x0
2010/09/06 14:47:59 VCS NOTICE V-16-1-10449 Group sql-Sgroup autodisabled on node DBSERVER-A until it is probed
2010/09/06 14:48:39 VCS INFO V-16-1-10077 Received new cluster membership
2010/09/06 14:48:39 VCS NOTICE V-16-1-10112 System (DBSERVER-B) - Membership: 0x3, DDNA: 0x0
2010/09/06 14:48:39 VCS NOTICE V-16-1-10322 System (Node '0') changed state from UNKNOWN to INITING
2010/09/06 14:48:39 VCS NOTICE V-16-1-10086 System DBSERVER-A (Node '0') is in Regular Membership - Membership: 0x3
2010/09/06 14:48:40 VCS NOTICE V-16-1-10453 Node: 0 changed name from: 'DBSERVER-A' to: 'DBSERVER-A'
2010/09/06 14:48:40 VCS NOTICE V-16-1-10322 System DBSERVER-A (Node '0') changed state from FAULTED to INITING
2010/09/06 14:48:40 VCS NOTICE V-16-1-10322 System DBSERVER-A (Node '0') changed state from INITING to CURRENT_DISCOVER_WAIT
2010/09/06 14:48:40 VCS NOTICE V-16-1-10322 System DBSERVER-A (Node '0') changed state from CURRENT_DISCOVER_WAIT to REMOTE_BUILD
2010/09/06 14:48:40 VCS INFO V-16-1-10463 Sending snapshot to node: 0
2010/09/06 14:48:43 VCS NOTICE V-16-1-10322 System DBSERVER-A (Node '0') changed state from REMOTE_BUILD to RUNNING
2010/09/06 14:48:44 VCS INFO V-16-1-10304 Resource sql-Sgroup-IP (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/09/06 14:48:44 VCS INFO V-16-1-10304 Resource sql-Sgroup-RegRep-MSSQL (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/09/06 14:48:45 VCS INFO V-16-1-10304 Resource sql-Sgroup-Lanman (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/09/06 14:50:44 VCS INFO V-16-1-10304 Resource sql-Sgroup-SQLServer2005 (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/09/06 14:51:11 VCS INFO V-16-1-10304 Resource sql-Sgroup-VMDg (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/09/06 14:51:11 VCS INFO V-16-1-10304 Resource sql-Sgroup-MountV (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/09/06 14:51:11 VCS INFO V-16-1-10304 Resource GGG-HHH (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/09/06 14:51:11 VCS INFO V-16-1-10304 Resource ABC_Live (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/09/06 14:51:11 VCS INFO V-16-1-10304 Resource T_Log (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/09/06 14:51:11 VCS INFO V-16-1-10304 Resource BBB (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/09/06 14:51:11 VCS INFO V-16-1-10304 Resource Rtable (Owner: unknown, Group: sql-Sgroup) is offline on DBSERVER-A (First probe)
2010/09/06 14:51:11 VCS NOTICE V-16-1-10438 Group sql-Sgroup has been probed on system DBSERVER-A
2010/09/06 14:51:11 VCS NOTICE V-16-1-10435 Group sql-Sgroup will not start automatically on System DBSERVER-A as the system is not a part of AutoStartList attribute of the group.
2010/09/06 14:52:04 VCS INFO V-16-1-50135 User admin fired command: hagrp -unfreeze -persistent sql-Sgroup from 127.0.0.1
2010/09/06 14:52:07 VCS INFO V-16-1-50135 User admin fired command: haconf -dump from 127.0.0.1
2010/09/06 14:52:08 VCS INFO V-16-1-50135 User admin fired command: haconf -dump from 127.0.0.1
2010/09/06 14:54:21 VCS INFO V-16-1-50135 User admin fired command: haconf -dump from 127.0.0.1
2010/09/08 10:54:02 VCS INFO V-16-0 (DBSERVER-B) VCS:******:HAGETCF:Dumping output of HAGETCF
2010/09/08 10:54:17 VCS INFO V-16-1-50135 User Administrator fired command: haclus -modify HacliUserLevel COMMANDROOT from 127.0.0.1
2010/09/08 10:54:21 VCS INFO V-16-1-50135 User Administrator fired command: haclus -modify HacliUserLevel NONE from 127.0.0.1
2010/09/09 12:40:20 VCS INFO V-16-0 (DBSERVER-A) VCS:******:HAGETCF:Dumping output of HAGETCF
2010/09/09 12:45:08 VCS INFO V-16-0 (DBSERVER-B) VCS:******:HAGETCF:Dumping output of HAGETCF
Solved! Go to Solution.
09-22-2010 05:22 AM
Hello Zahid,
please find the comments below -
09-22-2010 03:47 AM
Hello Zahid,
The log is big and clear to understand and not easy to explain every linie. If you have doubt on any particular log message, you can put your query, we will try to explain.
09-22-2010 05:22 AM
Hello Zahid,
please find the comments below -
09-23-2010 10:56 PM
Thanks Rajesh for your kind help. Would you please through some light on
Membership: 0x2, DDNA: 0x1
Membership: 0x2, Visible: 0x0
Membership: 0x3, DDNA: 0x0
OR
Membership: 0x3, DDNA: 0x0
Membership: 0x1, DDNA: 0x2
Membership: 0x1, Visible: 0x0
09-24-2010 03:56 AM
Zahid,
Deleted blank post since it appeared to be accidental post / there was no content.
Re: DDNA membership, perhaps see your earlier post from a month ago where Anoop provided technotes explaining what these messages mean:
https://www-secure.symantec.com/connect/forums/membership-0x3-ddna-0x0-membership-0x1-ddna-0x2-ddna-membership-membership-0x1-visible-0x0
regards,
Grace