79
D14049.07
March 2010
Grey Headline
(continued)
TANDBERG
VIDEO COMMUNICATION SERVER
ADMINISTRATOR GUIDE
Introduction
Overview and
status
System
configuration
VCS
configuration
Zones and
neighbors
Clustering and
peers
Call
processing
Bandwidth
control
Firewall
traversal
Appendices
Applications
Maintenance
Cluster configuration
Configuring clusters
Setting up a cluster
Before creating your cluster, ensure that all the VCSs to be added
to the cluster:
•
are using
TMS
version 12.5 or later as their external manager
•
have the same software version and
option keys
installed
•
each have a different
system name
•
are configured with a working
NTP Server
.
•
each have a different
LAN
configuration (a different
IPv4 address and a different IPv6 address, where enabled)
•
have
H.323
enabled (even if all endpoints in the cluster
are SIP only, H.323 signaling is used for endpoint location
searching and sharing bandwidth usage information with other
peers in the cluster)
•
have
SSH
enabled (data replication between peers uses SSH)
•
have
access to the root account via SSH
enabled
Configuring the master peer
One of the VCSs in the cluster must act as the master peer for
controlling updates to configuration data.
1. Decide which VCS is to be the master and configure it with the
settings you want to apply to the entire cluster.
2. Go to the
Clustering
page (
VCS configuration > Clustering
) of
the master VCS:
a. Enter a
Cluster name
(see
Cluster name
, right).
b. Enter the IP addresses of the master VCS and the other
peers into the
Peer IP address
fields.
c. Select the
Configuration master
to match the
Peer IP
address
number of the master VCS.
Running the clustering script
On each peer in the cluster, log in as
root
and run the cluster
configuration script.
A full step-by-step guide on using the clustering script and
configuring clusters is available in the
Clustering deployment
guide [27]
.
Maintaining a cluster
The
Clustering
page lists the IP addresses of all the peers in the
cluster, to which this VCS belongs, and identifies the master peer.
To view the
Clustering
page:
•
VCS configuration > Clustering
.
To view this information from the CLI:
•
xConfiguration Alternates
Setting configuration for the cluster
You should make configuration changes on the master VCS.
Any changes made on other peers are not reflected across
the cluster, and will be overwritten the next time the master’s
configuration is replicated across the peers.
The only exceptions to this are:
•
some
specific configuration items that are not replicated
•
user account details (you can maintain these on any peer —
FindMe data uses a different replication mechanism)
You may need to wait up to one minute before changes are
updated across all peers in the cluster.
Adding and removing peers from a cluster
After a cluster has been set up you can add new peers to the
cluster or remove peers from it. Instructions for this are also
contained in the
Clustering deployment guide [27]
.
!
Systems that are configured as peers must not also be
configured as neighbors to each other, and vice versa.
!
If peers are deployed on different LANs, there must be
sufficient connectivity between the networks to ensure
a low degree of latency between the peers - a maximum
delay of 15ms one way, 30ms round-trip.
Deploying all peers in a cluster on the same LAN means they can
be configured with the same routing information such as local
domain names and local domain subnet masks.
Cluster name
The
Cluster name
is used to identify one cluster of VCSs
from another. Set it to the fully qualified domain name used
in SRV records that address this VCS cluster, for example
"cluster1.example.com".
See the
Clustering and FindMe
section if you are using FindMe.
Changing the master peer
You should only need to change the
Configuration master
when:
•
The original master peer fails
: in this case you must log in to
every other VCS in the cluster and change the configuration
master on each. Note that if the master fails, the remaining
peers will continue to function normally, except they are no
longer able to copy their configuration from the master so may
become out of sync with each other.
•
You want to take the master VCS unit out of service
: in
this case you must log in to the master peer and change the
configuration master to another peer. (If you use any other
VCS to change the configuration master, this setting, like all
other configuration, will be overwritten when that peer next
replicates its configuration from the master.)
To change the master peer:
1. Log into the current master VCS and go to the
Clustering
page.
2. Change the
Configuration master
to the peer you want to set
as the new master (the numbers match against the
Peer IP
address
fields underneath).
3. Click
Save
.
You may need to wait up to one minute before the change is
updated across all peers in the cluster.
Monitoring the status of the cluster
The status areas at the bottom of the
Clustering
page show you
the current status of the cluster, and the time of the previous and
next synchronization.
From here you can also go to the
TMS Agent replication status
page. This shows the current status of the
TMS Agent
service and
can be used to assist in troubleshooting replication problems.
