AlwaysOn AG groups issue, both node are primary now

Question

Hi guys,
We have a cluster which has two AG groups in two nodes. Now they are all promary now.
what can I do now?
Many thanks,
SkyRiver
SkyRiver

Answer 1

Actually, on node1, it says node2 is down. On node2, it says nide1 is down.
Windows team needs to fix the cluster issue.
SkyRiver
I dont know how much it helps in your issue, we also had an similar issue,but there was error logged,iam sure you need to look first the eventlogs errors ,cluster logs and sql errorlogs.
so in My case-
I was getting below error( here both the side SQL is able to connect & databases are well synchornized status,also if I login one node other shows off & other shows ON).
Cluster IP address rerource "p-ag2"cannot brought online because a duplicate adress"XX.XXX.XX.XXX" was dected on the network.please ensure all the ip adrresses are unique
Evvent ID ->1049.
along with 1205,1069
Temporary solution ->we have just shutdown secondary & start again  -this was fixing but again" PLEASE DONOT PERFORM UNTIL YOU ARE SURE WITH SAME SPECIFIC ERROR,ALSO SUGGESTING TO OPEN A CASE & SHARE WITH ALL AFTER SOLUTION FIXED"
so we have worked with VM first-
since the our sql was on VM,There were VM rules was incorrect they fixed it & reproted VMs are on single host as per the cluster requirement but again after some the same issue caused.
so this time we have checked with WINDOWS TEAM,they also unable to point out but was intersting that quorum was not configured properly for VM -so
VMware team changes the vm disk configuration of  secondary to point the quorum disk to the one used bt primary, but before this -
1. VMWare team need to configure the vm Secondary in the cluster : VM  restart priority  as disabled  in HA
2. Shutdown secondary
3. Reboot Primary and check if cluster node and resources are ok, if not fix it first  (This will cause a service interruption )
4. VMware team changes the vm disk configuration of  Secondary to point the quorum disk to the one used bt Primary.
5. Start secondary
6 Check the MSCS cluster (no errors)
7. Check SQL and SQL failover of the ag groups.
8. If all validations are OK:  VMWare team need to configure the vm on secondary in the cluster : VM  restart priority  as "cluster setting"  in HA.
so above is fixed,but "PLEASE DONOT TRY ANYONE" -JUST SHARE THE FIRST ERRORLOGS,CLUSTERLOGS,EVENTLOGS information more, if you are not much pretty sure, please open a case with Vendor MS to see. Hope if someone writes this issue in the blog -helps
much better but errors are very improtant from the logs.
Also ensure from windows cluster services is in healthy status & quorum sharing b/w nodes are correct in place.
Thanks, Rama Udaya.K (http://rama38udaya.wordpress.com) ---------------------------------------- Please remember to mark the replies as answers if they help and UN-mark them if they provide no help,Vote if they gives you information.