VCS-C Cluster Failing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2018 07:16 AM - edited 03-18-2019 02:26 PM
I am prepping for a upcoming cut over in lab and have 2 VCS-C server that I have set up for clustering. All have NTP, DNS, H.323 on. Forward and reverse looks up are fine. TLS cluster is set to permissive mode so I am not enforcing TLS.
So just to sum up two nodes VCSC 10.101.8.90 and VCS3 10.101.8.92.
No matter what I seem to do I get the following error message on the non primary node.
Cluster replication error |
This peer's configuration conflicts with the primary's configuration, manual synchronization of configuration is required.
Per the documentation I have run xcommand forceconfigupdate on the secondary node and I get a OK. I then wait and nothing happens.
I have rebooted both nodes series times after creating the cluster. I have attached screen shots of clustering config and a xcommand forceupdateconfig.
Open to any and all suggestions as I have thrown my head against this way for to long.
Below is copy and paste of secondary node VCS3
xcommand forceconfigupdate
OK
- Labels:
-
Room Endpoints
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2018 08:03 AM - edited 11-07-2018 08:53 AM
Something at is even more interesting to me is that when I clear out my cluster configuration on VCS3 node 2 and reboot, I always get a pop up that next restart will trigger factory reset. Done this like 3 times same error message.
When I readd it error goes away cluster looks good like a minute and then back to that same error message.
The only thing I can think is something with having invalid release keys since this is a lab server is messing up the process?
Edited GLO was able to generate some temp release keys for me. Even after I applied and reset the VCS3 is still constantly showing that next restart will factory reset. This message seems to be buggy behavior to me.
So as it stand now even with template license I get the following errors. Version 8.11.3
Cluster replication error | This peer's configuration conflicts with the primary's configuration, manual synchronization of configuration is required | Raised | Warning | This system | View cluster replication instructions | 2018-11-07 16:45:48 | 2018-11-07 16:51:37 | 20011 | |
Cluster TLS permissive | Cluster TLS verification mode permits invalid certificates | Raised | Notice | 10.101.8.90 | Connect to the remote peer to investigate this alarm. | 2018-11-07 16:32:12 | 2018-11-07 16:42:55 | 40049 | |
Cluster TLS permissive | Cluster TLS verification mode permits invalid certificates | Raised | Notice | This system | Change the cluster's TLS verification mode to Enforcing | 2018-11-07 16:43:11 | 2018-11-07 16:43:11 | 40049 |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2018 05:52 AM - edited 11-08-2018 12:23 PM
So got so frustrated did a fresh 8.8 install and got a cluster up and running in no time.
Upgrading that 8.8 cluster to see what happens. 8.8 cluster was set up no problem no errors... Doing a fresh install of 8.11.3 and restoring my configs to it to see if that will get me past this cluster update error message.
And Fresh install with back up config problem comes right back....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2018 01:05 PM
Well considering I can't download the software anymore probably going to let this sit and worry about it when the software has been updated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2018 01:19 PM
Well ran into this problem with a customer now. Apparently the Error message may never go away or so says TAC. Unlike other alarms once you clear the problem it doesn't remove itself from the log. They are searching for documentation on this.
