Polycom, Inc. 359
Possible explanations:
●Someone upgraded one server of the cluster while the other was turned off or otherwise unavailable.
●An expansion server was added to a single-server cluster, but the new server wasn’t patched to the
same software level as the existing server.
●An RMA replacement server wasn’t patched to the same software level as the existing server.
If you’re logged into that cluster, click the link to go to the Software Upgrade page. If not, log into that cluster
and go to Maintenance > Software Upgrade. Check Operation History.
Log into the physical address of the server that was unable to join the cluster and upgrade it to match the
other server. After it restarts, it will join the cluster.
See also:
Alerts on page 342
Alert 3602 Cluster <cluster>: Local time differs by more than ten seconds between servers.
The time on the two servers in the specified cluster has drifted apart by an unusually large amount. This
may indicate a configuration issue or a problem with one of the servers. Contact Polycom Global Services.
See also:
Alerts on page 342
Alert 3603 Cluster <cluster>: Active Directory integration is not consistent between servers.
In the specified cluster, the Active Directory integration status information is different on the two servers,
indicating that their internal databases aren’t consistent.
Try to determine which server’s data is incorrect and reboot it.
See also:
Alerts on page 342
Alert 3604 Cluster <cluster>: Enterprise conference rooms differ between servers.
In the specified cluster, the enterprise conference room counts are different on the two servers, indicating
that their internal databases aren’t consistent.
Try to determine which server’s data is incorrect and reboot it.
See also:
Alerts on page 342