Unsolved
This post is more than 5 years old
2 Intern
•
522 Posts
0
1971
June 20th, 2016 07:00
Slave MDM isn't synchronized
During a recent power failure (lab) the second MDM seems to be in a status of "Not Synchronized" and thus is showing as the MDM cluster not being clustered. There doesn't seem to be any CLI command to force a re-sync or anything (or I have not located it yet) and was curious what a fix might be. I have rebooted the SVM for the MDM2 (this is an ESX deployment). I thought about removing and re-adding the MDM, but before I did that I wanted to exhaust there was no "refresh/re-sync" command I was missing...any thoughts?
I haven't tried to switch ownership either...might try that to see if I can force it back and forth.
thanks!
No Events found!
echolaughmk
2 Intern
•
522 Posts
0
June 20th, 2016 10:00
Switch ownership change failed because the cluster is in a degraded mode so that didn't work
I didn't remove/re-add yet...working with support and will update the thread once I get it working...thx.
pawelw1
306 Posts
0
June 20th, 2016 10:00
Hi,
Yes, please try that - or switch to single mode, then back to cluster mode and let us know if that worked?
Thanks,
Pawel
pawelw1
306 Posts
0
June 25th, 2016 01:00
Hi,
Any news on this yet :-)?
Can you let me know the SR# you have with support?
Thanks!
Pawel
echolaughmk
2 Intern
•
522 Posts
0
July 9th, 2016 04:00
Hi Pawel,
Yes - I totally forgot to reply to this. The issue was caused by network latency. I have the SVM's on a mgmt network and on an SDS-only network and one of the ESX hosts seemed to have negotiated to 100/HD upon the power outage and therefore the virtual NIC associated with that host for the SDS-only network was giving high latencies in a ping. Once I corrected the negotiation, it corrected itself.
Thanks!
-Keith
pawelw1
306 Posts
0
July 11th, 2016 05:00
Thanks Keith!