Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
which the logs of all peers can be sent. This allows you to have a global view of activity across all peers in the cluster.
See the
See the
Security certificates (Maintenance > Security certificates)
The trusted CA certificate, server certificate and certificate revocation lists (CRLs) used by the VCS must be
uploaded individually per peer.
uploaded individually per peer.
Administration access (System > Administration)
The following system administration access settings are specific to each peer:
■
Serial port / console
■
SSH service
■
Web interface (over HTTPS)
■
Redirect HTTP requests to HTTPS
■
Automated protection service
Option keys (Maintenance > Option keys)
Option keys are specific to each peer. Each peer must have an identical set of option keys installed, but you must
purchase these separately for each peer in the cluster. However, this does not apply to traversal call licenses, non-
traversal call licenses and TURN relay licenses; these licenses can be installed on any cluster peer and are available
for use by any peer in the cluster.
purchase these separately for each peer in the cluster. However, this does not apply to traversal call licenses, non-
traversal call licenses and TURN relay licenses; these licenses can be installed on any cluster peer and are available
for use by any peer in the cluster.
Active Directory Service (Configuration > Authentication > Devices > Active Directory Service)
When configuring the connection to an Active Directory Service for device authentication, the NetBIOS machine
name (override), and domain administrator Username and Password are specific to each peer.
name (override), and domain administrator Username and Password are specific to each peer.
Conference Factory template (Applications > Conference Factory)
The template used by the Conference Factory application to route calls to the MCU is peer-specific, as it must be
unique for each peer in the cluster.
unique for each peer in the cluster.
VCS front panel display mode (configurable through CLI only)
The
xConfiguration Administration LCDPanel Mode
CLI setting is specific to each peer.
Sharing Registrations Across Peers
When a cluster peer receives a search request (such as an LRQ, ARQ or an INVITE), it checks its own and its peers'
registration lists before responding. This allows all endpoints in the cluster to be treated as if they were registered
with a single VCS.
registration lists before responding. This allows all endpoints in the cluster to be treated as if they were registered
with a single VCS.
Peers are periodically queried to ensure they are still functioning. To prevent delays during call setup, any
nonfunctioning peers do not receive LRQs.
nonfunctioning peers do not receive LRQs.
H.323 registrations
All the peers in a cluster share responsibility for their H.323 endpoint community. When an H.323 endpoint registers
with one peer, it receives a registration response which contains a list of alternate gatekeepers, populated with a
randomly ordered list of the IP addresses of all the other peers in that cluster.
with one peer, it receives a registration response which contains a list of alternate gatekeepers, populated with a
randomly ordered list of the IP addresses of all the other peers in that cluster.
If the endpoint loses contact with the initial peer, it will seek to register with one of the other peers. The random
ordering of the list of alternate peers ensures that endpoints that can only store a single alternate peer will failover
evenly across the cluster.
ordering of the list of alternate peers ensures that endpoints that can only store a single alternate peer will failover
evenly across the cluster.
When using a cluster, you may want to reduce the registration Time to live on all peers in the cluster from the default
30 minutes. This setting determines how often endpoints are required to re-register with their VCS, and reducing it
means that if a cluster peer is unavailable, the endpoint will failover more quickly to an available peer.
30 minutes. This setting determines how often endpoints are required to re-register with their VCS, and reducing it
means that if a cluster peer is unavailable, the endpoint will failover more quickly to an available peer.
Note:
By reducing the registration time to live too much, you risk flooding the VCS with registration requests, which
will severely impact performance. This impact is proportional to the number of endpoints, so you should balance the
need for occasional quick failover against the need for continuous good performance.
need for occasional quick failover against the need for continuous good performance.
182
Cisco TelePresence Video Communication Server Administrator Guide
Clustering and Peers