Clustering And Findme; Overview; Configuration; Enabling The Replication Of Findme Information - TANDBERG Video Communication Server Administrator's Manual

Grey Headline (continued)
Clustering and peers

Clustering and FindMe

Overview

Clustering supports the use of FindMe. Each peer has its own
FindMe database containing all FindMe account information for
the cluster. When a FindMe account is created or edited on one
peer, that peer shares the information about the changes to all
other peers in the cluster, which then update their own FindMe
databases accordingly.
Note that the replication of FindMe database information is a
completely separate process and uses a different mechanism to
the replication of configuration information. Changes to FindMe
information can be made on any peer and will be shared with all
other peers, whereas changes to configuration information can
only be made to the master peer and is then replicated to all
other peers.
Configuration

Enabling the replication of FindMe information

If you are using FindMe on your VCS version X4 cluster, FindMe
databases will be automatically replicated between peers.

Enabling SSH

The replication of all configuration (including FindMe data)
between peers is performed using SSH, so this service must
be enabled on all peers. To enable SSH, navigate to
configuration > System and ensure that SSH service
On.
Clustering also requires access to the root account via SSH. To
configure this, see the section Accessing the root account over
SSH and Telnet.
Overview and
Introduction Getting started
status
D14049.05
February 2009

Clustering and presence

Clustering supports the use of Presence.
All peers in the cluster must have identical SIP domain,
Presence Server and Presence User Agent (PUA) configuration.
If peers in the cluster have the PUA enabled, each peer will
publish information about its own local registrations. This
information will be routed to a Presence Server authoritative for
the cluster's domain.
If peers have the Presence Server enabled, the Presence
database is replicated across all peers in the cluster.
When viewing presence status
•
Publishers will show all presentities across the cluster for
whom presence information is being published.
•
Presentities will show any presentity for whom a subscription
request has been received on the local VCS only.
•
Subscribers will show each endpoint from whom a
subscription request has been received on the local VCS only.

Backup and restore

The Backup and restore process saves all configuration
information for a particular VCS. We recommend that you
System
regularly backup not just the master peer but all peers in
is set to
the cluster. This will ensure that peer-specific configuration
information (see the section
replicated?) is saved and can be restored individually for each
peer.
Do not restore a backup made on one peer to another
!
peer.
System VCS Zones and
configuration configuration neighbors
The clustering feature was introduced to the VCS in software
release X3.0.

Upgrading to X3.0 or later

If you are upgrading to VCS software version X3.0 or later from a
previous version and wish to implement clustering, you must:
1.
2.
on a peer in a cluster:
3.

Downgrading from X3.0 or later

If you have clustering configured and subsequently downgrade to
a version of VCS software prior to X3.0, the VCS will retain all its
existing configuration but will no longer act as a peer in a cluster.
This will have the following impact:
•
•
•
What configuration is and isn't
Call Bandwidth
processing control
88
TANDBERG VIDEO COMMUNICATIONS SERVER

Upgrades and downgrades

Remove any existing Alternate configuration.
Upgrade all VCSs to be added to the cluster to the latest VCS
software version (X3.0 or later).
Follow the steps outlined in the section Configuring
Changes to the master peer will not be replicated to the
VCS, or if the VCS is the master peer, its changes will not be
replicated to any other VCS.
The VCS's FindMe database will be a copy of that shared
across all peers in the cluster at the point when the VCS was
downgraded. The FindMe database will then be accessible to
the local VCS only.
Other VCSs that were peers to this VCS will now be treated
as Alternates. (See the X2 Administrator Guide for full
information on Alternates.)
Firewall
Applications Maintenance
traversal
ADMINISTRATOR GUIDE
clusters.
Appendices