Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Clustering and peers
Cisco VCS Administrator Guide (X7.0)
Page 146 of 488
If peers have the Presence Server enabled, the Presence database is replicated across all peers in the
cluster.
cluster.
When viewing presence status on a peer in a cluster:
n
Publishers shows all presentities across the cluster for whom presence information is being
published.
published.
n
Presentities shows any presentity for whom a subscription request has been received on the local
VCS only.
VCS only.
n
Subscribers shows each endpoint from which a subscription request has been received on the local
VCS only.
VCS only.
Clustering and TMS
You are recommended to use TMS when running a cluster of VCSs. For full information, refer to the TMS
documentation.
documentation.
n
TMS (version 12.5 or later) is mandatory if your cluster is configured to use FindMe or Device
Provisioning.
Provisioning.
If you were using TMS to manage a cluster running a version of the VCS software prior to X5, refer to the
Cluster creation and maintenance deployment guide [
Cluster creation and maintenance deployment guide [
] for upgrade instructions.
In previous VCS releases, replication between peers was managed by TMS. From VCS version X4
onwards, replication is managed by the VCSs themselves.
onwards, replication is managed by the VCSs themselves.
About the Cluster Subzone
When two or more VCSs are clustered together, a new subzone is created within the cluster’s Local
Zone. This is the Cluster Subzone (see the diagram in the
Zone. This is the Cluster Subzone (see the diagram in the
section). Any calls between
two peers in the cluster will briefly pass via this subzone during call setup.
The Cluster Subzone is (like the Traversal Subzone) a virtual subzone used for call routing only, and
endpoints cannot register to this subzone. After a call has been established between two peers, the
Cluster Subzone will no longer appear in the call route and the call will appear as having come from (or
being routed to) the Default Subzone.
endpoints cannot register to this subzone. After a call has been established between two peers, the
Cluster Subzone will no longer appear in the call route and the call will appear as having come from (or
being routed to) the Default Subzone.
The two situations in which a call will pass via the Cluster Subzone are:
n
Calls between two endpoints registered to different peers in the cluster.
For example, Endpoint A is registered in the Default Subzone to Peer 1. Endpoint B is also registered in
the Default Subzone, but to Peer 2. When A calls B, the call route is shown on Peer 1 as Default
Subzone -> Cluster Subzone, and on Peer 2 as Cluster Subzone -> Default Subzone.
For example, Endpoint A is registered in the Default Subzone to Peer 1. Endpoint B is also registered in
the Default Subzone, but to Peer 2. When A calls B, the call route is shown on Peer 1 as Default
Subzone -> Cluster Subzone, and on Peer 2 as Cluster Subzone -> Default Subzone.
n
Calls received from outside the cluster by one peer, for an endpoint registered to another peer.
For example, we have a single VCS for the Branch Office, which is neighbored to a cluster of 4 VCSs
at the Head Office. A user in the Branch Office calls Endpoint A in the Head Office. Endpoint A is
registered in the Default Subzone to Peer 1. The call is received by Peer 2, as it has the lowest
resource usage at that moment. Peer 2 then searches for Endpoint A within the cluster’s Local Zone,
and finds that it is registered to Peer 1. Peer 2 then forwards the call to Peer 1, which forwards it to
For example, we have a single VCS for the Branch Office, which is neighbored to a cluster of 4 VCSs
at the Head Office. A user in the Branch Office calls Endpoint A in the Head Office. Endpoint A is
registered in the Default Subzone to Peer 1. The call is received by Peer 2, as it has the lowest
resource usage at that moment. Peer 2 then searches for Endpoint A within the cluster’s Local Zone,
and finds that it is registered to Peer 1. Peer 2 then forwards the call to Peer 1, which forwards it to