Table of Contents
Advertisement
Grey Headline (continued)
Clustering and peers
A VCS can be part of a cluster of up to six VCSs. Each VCS in the cluster is a peer of every other
VCS in the cluster.
The purpose of a cluster is twofold:
1.
to increase the capacity of your VCS deployment compared with a single VCS
2.
to provide redundancy in the rare case that a VCS becomes unavailable (for example, due to a
network or power outage).
Peers have identical configuration, and share information with each other about their use of
bandwidth, registrations, and FindMe users. This allows the cluster to act as one large VCS Local
Zone.
The diagram opposite shows four peers clustered together to form one large Local Zone.
About the configuration master
All peers in a cluster must be configured identically for subzones, zones, links, pipes,
authentication, bandwidth control and call policy. To achieve this, one peer is nominated as
the configuration master. Every minute or so all other peers in the cluster request updated
configuration information from the master, and overwrite their existing configuration with these new
settings.
"Alternate" is an H.323 term for a system used to provide redundancy to a Primary
gatekeeper, and prior to version X3.0 the VCS supported Alternates. From X3.0 onwards,
redundancy (along with other features) is provided by clusters of peers, which support both
H.323 and SIP and work as equals. However, peers may sometimes be referred to as Alternates.
Overview and
Introduction
Getting started
status
D14049.05
February 2009
About clustering
System
VCS
Zones and
configuration
configuration
neighbors
PEER 1
LOCAL
ZONE
Subzone
Default
Subzone
Default
Zone
Call
Bandwidth
processing
control
85
TANDBERG
VIDEO COMMUNICATIONS SERVER
VCS CLUSTER
PEER 2
PEER 3
PEER 4
Cluster
Subzone
Traversal
Subzone
DNS
ENUM
Zone
Zone
Firewall
Applications
Maintenance
traversal
ADMINISTRATOR GUIDE
Traversal
Client Zone
Neighbor
Zone
Appendices
Advertisement
Table of Contents
