TANDBERG D14049.04 Network Card User Manual


 
99
D14049.04
JULY 2008
Grey Headline (continued)
TANDBERG VIDEO COMMUNICATIONS SERVER
ADMINISTRATOR GUIDE
Introduction Getting Started
Overview and
Status
System
Conguration
VCS
Conguration
Zones and
Neighbors
Call
Processing
Bandwidth
Control
Firewall
Traversal
Appendices
Applications Maintenance
Clustering, Peers and Alternates
The Alternates page lists the IP Addresses of all the Peers in the
Cluster to which this VCS belongs, including the IP Address of
the VCS to which you are currently logged in.
To view the Alternates page:
VCS Conguration > Alternates
.
You will be taken to the Alternates page.
xConguration Alternate
s
Peer 1...Peer 6 IP address
The IP Addresses of all Peers in the cluster are
shown here. This will include the IP Address of
the local VCS.
Viewing Peers
!
Do not make any
changes directly to
this page; it is for
information only. Adding and
removing Peers from a
Cluster must only be done via
TMS.
!
Systems that are congured as
Alternates (Peers) must not also be
congured as neighbors to each
other, and vice versa.
Clustering supports the use of Presence.
All Peers in the cluster must have identical SIP
Domain, Presence Server and Presence User
Agent (PUA) conguration.
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 on a Peer in a
cluster:
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.
Clustering and Presence
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 conguration information.
Changes to FindMe information can be made on
any Peer and will be shared with all other Peers,
whereas changes to conguration information
can only be made to the master Peer and is
then replicated to all other Peers via TMS.
Conguration
Enabling the Replication of FindMe
Information
If you are using FindMe on your VCS Cluster,
you must rst run a special series of commands
to allow FindMe databases to be replicated
between Peers. Contact your TANDBERG
representative for further information on how to
do this.
Enabling SSH
The replication of FindMe data between Peers
is performed using SSH, so this service must
be enabled on all Peers.
To enable SSH, navigate to System
Conguration > System and ensure that SSH
service is set to On.
Clustering and FindMe