Академический Документы
Профессиональный Документы
Культура Документы
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 2 of 48
Task 2: Upgrading the peer that has been removed from the cluster 34
Task 3: Configuring the upgraded peer to be a cluster of one peer 34
Task 4: Configuring Unified CM to use the upgraded peer 34
Task 5: Removing the other peers from the original cluster 34
Task 6: Upgrading the other peers 34
Task 7: Adding the remaining peers into the new cluster 35
Task 8: Configuring Unified CM to use the upgraded peer(s) 35
Task 9: Testing the system with calls 35
Peer-specific configuration 36
Cluster configuration 36
Ethernet 36
IP 36
System host name and domain 36
DNS servers 36
Time 36
SNMP 37
Logging 37
Security certificates 37
Administration access 37
Root account password 37
Locations 37
Troubleshooting 38
Unable to cluster the TelePresence Conductor 38
Appendix 1: Unified CM version 8.6.2 configuration 39
Adding the secondary TelePresence Conductor to Unified CM for ad hoc conferences 39
Appendix 2: Unified CM version 9.x configuration 41
Adding the secondary TelePresence Conductor to Unified CM for ad hoc conferences 41
Appendix 3: IP ports and protocols 44
IPSec communications 44
MTU size 44
Appendix 4: Ensuring that Unified CM trusts TelePresence Conductor's server
certificate and vice versa 45
Loading server and trust certificates on TelePresence Conductor 45
Loading server and trust certificates on Unified CM 46
Document revision history 47
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 3 of 48
Introduction
Introduction
About this document
This document assumes that a standalone Cisco TelePresence Conductor integration with Cisco Unified
Communications Manager (Unified CM) ad hoc and rendezvous calls has been set up according to the Cisco
TelePresence Conductor with Cisco Unified Communications Manager Deployment Guide. This guide
provides details on how to:
n Extend the TelePresence Conductor integration with Unified CM to a cluster of TelePresence Conductors
for ad hoc and rendezvous calls.
n Back up a TelePresence Conductor cluster.
n Remove a TelePresence Conductor peer from Unified CM for ad hoc and rendezvous calls.
n Upgrade a TelePresence Conductor cluster.
Related documentation
For details on how to integrate a TelePresence Conductor cluster with Cisco VCS see either Cisco
TelePresence Conductor Clustering with Cisco VCS (Policy Server) Deployment Guide or Cisco
TelePresence Conductor Clustering with Cisco VCS (B2BUA) Deployment Guide depending on the type of
Cisco VCS deployment used.
For more details on Unified CM not covered in this deployment guide, including how to implement a Unified
CM or Unified CM cluster please reference the documentation on Cisco.com under the Cisco Unified
Communications Manager, http://www.cisco.com/en/US/products/sw/voicesw/ps556/index.html.
For details on how to deploy Unified CM, TelePresence Conductor, and the Conference bridges in an end-to-
end secure network see Cisco TelePresence Conductor with Cisco Unified Communications Manager
Deployment Guide.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 4 of 48
Example network deployment
Conference bridges
Conference bridges are network devices that enable multiple video calls to come together in a multipoint
video conference. This version of the TelePresence Conductor supports the conference bridge types
TelePresence MCU and TelePresence Server.
Endpoints
Endpoints are devices that receive and make video calls. They can be software clients on PCs and Macs
such as Cisco Jabber Video for TelePresence, desktop endpoints such as the 9971 and EX90, or room
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 5 of 48
Example network deployment
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 6 of 48
Creating a TelePresence Conductor cluster
Note: The total license capacity of Personal Multiparty (PMP) or Shared Multiparty (SMP) license option
keys in a cluster is the sum of the individual PMP or SMP keys configured on each peer in the cluster.
Integration overview
As part of a solid network design, implementation of redundancy within the system is critical. This can be
achieved for a Unified CM and TelePresence Conductor integration using additional TelePresence
Conductors configured as additional options for Unified CM to use to place ad hoc and rendezvous calls. The
diagram below depicts a resilient scenario in a single site design. We recommend that when configuring the
Unified CM and TelePresence Conductor integration, to ensure that the primary TelePresence Conductor for
ad hoc calls, Conductor_1, is the secondary TelePresence Conductor for rendezvous calls and the opposite
configuration for Conductor_2, where it is the primary TelePresence Conductor for rendezvous calls and
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 7 of 48
Creating a TelePresence Conductor cluster
secondary for the ad hoc calls, or that ad hoc and rendezvous calls use round robin so that calls are load
balanced across the TelePresence Conductor peers.
In a design where a single Unified CM cluster or multiple Unified CM clusters support multiple CAC
locations, TelePresence Conductor must be configured with separate locations for each Unified CM CAC
location. In addition, TelePresence Conductor must be configured to use conference bridge resources that
are in the relevant Unified CM location; otherwise if this design is not followed the Unified CM CAC model
will be broken.
Note: For ad hoc conferences the conference bridges to use are indirectly configured by the template that is
configured on the TelePresence Conductor's Locations page (Conference template > Service Preference >
Conference bridge pools > Conference bridges). The conference bridges to use for rendezvous conferences
are defined by the alias dialed (Conference alias > Conference template > Service Preference > Conference
bridge pools > Conference bridges) therefore for rendezvous conferences the prefix must be location-
specific.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 8 of 48
Creating a TelePresence Conductor cluster
2. Verify that no other TelePresence Conductor already has Conductor_1s IP address in their clustering
peers list. To do this verification:
a. Log into every TelePresence Conductor as a user with administrator rights.
b. Go to System > Clustering.
c. Ensure that all Peer X IP address fields (X = 1, 2, and 3) on this page do not have Conductor_1s IP
address.
If they do:
i. Delete that Peer IP address.
ii. Click Save.
iii. Go to Maintenance > Restart options.
iv. Click Restart.
3. Log into Conductor_1 as a user with administrator rights.
4. Ensure that Conductor_1 has a valid and working NTP server configured:
a. Go to System > Time.
b. In the Status section at the bottom of the page, the State should be Synchronized:
Cluster Enter a password (this will be the same for all peers).
pre-
shared
key
Peer 1 IP Enter the IP address of this TelePresence Conductor peer, Conductor_1 (this is the initial peer
address in the cluster from which the initial configuration will be replicated from to all other peers in the
cluster).
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 9 of 48
Creating a TelePresence Conductor cluster
3. Click Save.
4. Go to Maintenance > Restart options.
5. Click Restart.
6. Log into Conductor_1 as a user with administrator rights.
7. Go to System > Clustering.
8. Verify the status of this peer. It should have This System in green next to the IP address.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 10 of 48
Creating a TelePresence Conductor cluster
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 11 of 48
Creating a TelePresence Conductor cluster
5. Click Save.
Note: Ensure that the initial peer is accessible via the web and is not still restarting. If the second peer is
restarted while the initial peer is restarting, the wrong peer may be selected as the initial peer and
configuration may be lost.
6. Go to Maintenance > Restart options.
7. Click Restart.
8. Log back into Conductor_2 as a user with administrator rights.
9. Go to System > Clustering.
10. Verify the Status of each peer. It should have This system in green next to this systems IP address
and show Active for the other peer.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 12 of 48
Creating a TelePresence Conductor cluster
See Appendix 4: Ensuring that Unified CM trusts TelePresence Conductor's server certificate and vice versa
[p.45] in this document for more information on how to ensure that Unified CM trusts the TelePresence
Conductor server certificate.
See Cisco TelePresence Conductor Certificate Deployment Guide for full details about loading certificates
and how to generate CSRs on TelePresence Conductor to acquire certificates from a Certificate Authority
(CA).
Note: In a clustered environment, you must install CA and server certificates on each peer/node individually.
We strongly recommend that you do not use self-signed certificates in a production environment.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 13 of 48
Creating a TelePresence Conductor cluster
4. Click Next.
5. Enter the following into the relevant fields, leave other fields as their default values:
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 14 of 48
Creating a TelePresence Conductor cluster
Location Select the same Location that was used for Conductor_1.
SIP Trunk Security Select the Secure SIP Trunk Profile from the drop-down list.
Profile
SIP Profile Select the same SIP Profile that was used for Conductor_1.
Normalization Script If you specified a normalization script on the Trunk to Conductor_1, select the same
Normalization script here.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 15 of 48
Creating a TelePresence Conductor cluster
6. Click Save.
7. Click Reset.
SIP Trunk Select the SIP trunk you created in Task 7: Adding a SIP trunk to the secondary TelePresence
Conductor for ad hoc conferences [p.14]
Username Enter the username of the TelePresence Conductor administration user. This appears on the
TelePresence Conductor's Administrator accounts page (Users > Administrator accounts)
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 16 of 48
Creating a TelePresence Conductor cluster
Click Save.
Click Reset.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 17 of 48
Creating a TelePresence Conductor cluster
Resources box. Make sure this conference bridge is the last bridge in the list as it is the redundant
TelePresence Conductor.
5. Click Save.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 18 of 48
Creating a TelePresence Conductor cluster
4. Click Next.
5. Enter the following into the relevant fields, leave other fields as their default values:
Location Select the same Location that was used for Conductor_1.
SIP Trunk Security Select the Secure SIP Trunk Profile from the drop-down list
Profile
SIP Profile Select the same SIP Profile that was used for Conductor_1.
Normalization Script If you specified a normalization script on the Trunk to Conductor_1, select the same
Normalization script here.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 19 of 48
Creating a TelePresence Conductor cluster
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 20 of 48
Creating a TelePresence Conductor cluster
6. Click Save.
7. Click Reset.
4. Under the Route Group Member section, highlight Trunk_Rendezvous_to_Conductor and click Add to
Route Group.
5. Under the Route Group Member section, highlight Trunk_Rendezvous_to_Conductor_redundant and
click Add to Route Group.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 21 of 48
Creating a TelePresence Conductor cluster
6. Once both are added, they will appear in the Current Route Group Members section.
7. For load balancing rendezvous calls to the opposite TelePresence Conductor to the one used for ad hoc
calls, ensure that Trunk_Rendezvous_to_Conductor_redundant is moved to the top of the list.
8. Click Save.
Note: If the original SIP trunk, set up while following the Cisco TelePresence Conductor with Unified
CM Deployment Guide (Trunk_Rendezvous_to_Conductor), is not listed, it may be in use elsewhere. To
work around this:
1. Create the Route Group with only the new SIP trunk (Trunk_Rendezvous_to_Conductor_redundant).
2. Modify the route pattern in Task 13: Editing the route pattern that matches the SIP trunk to TelePresence
Conductor [p.23]
3. Return to Task 11: Adding a route group for the SIP trunks [p.21] to add the SIP trunk Trunk_
Rendezvous_to_Conductor to the route group.
Cisco Unified Communications Manager Group Select the appropriate group from the drop-down list
4. Click Save.
5. Click Add Route Group.
6. Next to the Route Group field select the route group created in Task 11: Adding a route group for the SIP
trunks [p.21].
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 22 of 48
Creating a TelePresence Conductor cluster
7. Click Save.
8. Click Reset.
Task 13: Editing the route pattern that matches the SIP trunk to
TelePresence Conductor
1. Go to Call Routing > Route/Hunt > Route Pattern.
2. Click Find and then select the relevant route pattern.
3. Enter the following into the relevant fields, leave other fields as their default values:
Route Pattern Enter a route pattern to match against the destination string
Gateway/Route List Select the route list used in Task 12: Adding a route list for the route group [p.22]
4. Click Save.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 23 of 48
Creating a system backup
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 24 of 48
Testing system configuration
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 25 of 48
Testing system configuration
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 26 of 48
Testing system configuration
4. To verify the established call on the TelePresence Conductor, Cond_1, go to Status > Conferences.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 27 of 48
Testing system configuration
5. To verify the established call on the TelePresence MCU, go to the Conference Status page
(Conferences on the main tab
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 28 of 48
Testing system configuration
5. To verify on the TelePresence Conductor, Cond_2, that the call has been passed through the B2BUA, go
to Status > Conferences.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 29 of 48
Testing system configuration
6. To verify the establisehd call on the TelePresence MCU, go to the Conference Status page
(Conferences on the main tab).
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 30 of 48
Removing a TelePresence Conductor peer
6. Click Save.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 31 of 48
Removing a TelePresence Conductor peer
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 32 of 48
Removing a TelePresence Conductor peer
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 33 of 48
Upgrading a cluster of TelePresence Conductors
Task 2: Upgrading the peer that has been removed from the
cluster
On the TelePresence Conductor that has been removed from the cluster:
1. Go to the web interface and log in as a user with administrator privileges.
2. Go to Maintenance > Upgrade.
3. Click Browse and select the TelePresence Conductor software image.
4. Click Upgrade.
5. Follow the onscreen prompts.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 34 of 48
Upgrading a cluster of TelePresence Conductors
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 35 of 48
Peer-specific configuration
Peer-specific configuration
Most items of configuration are applied to all peers in a cluster. However, the following items must be
specified separately on each cluster peer.
Cluster configuration
The list of Peer IP addresses (including the peer's own IP address) that make up the cluster has to be
specified on each peer and they must be identical on each peer (the order in which they appear is not
important).
The cluster pre-shared key has to be specified on each peer and must be identical for all peers.
Ethernet
The Ethernet speed is specific to each peer. Each peer may have slightly different requirements for the
connection to their Ethernet switch.
IP
Note: Never change the Primary LAN 1 IP address of a TelePresence Conductor that is part of a cluster. The
only IP settings that can be changed when the system is part of a cluster are the additional IPv4 addresses.
The IPv4 address is specific to each peer. It must be different for each peer in the cluster.
The IPv4 subnet mask is specific to each peer. It can be different for each peer in the cluster.
The IPv4 gateway is specific to each peer. Each peer can use a different gateway.
Any additional IPv4 addresses added for use with Unified CM must be different for each peer in the cluster.
DNS servers
DNS servers are specific to each peer. Each peer can use a different set of DNS servers.
Time
The NTP servers are specific to each peer. Each peer may use one or more different NTP servers.
The time zone is specific to each peer. Each peer may have a different local time.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 36 of 48
Peer-specific configuration
SNMP
SNMP settings are specific to each peer. They can be different for each peer.
Logging
The Event Log and Configuration Log on each peer will only report activity for the local TelePresence
Conductor.
The list of remote syslog servers is specific to each peer. We recommend that you set up a remote syslog
server to which the logs of all peers can be sent. This will allow you to have a global view of activity across all
peers in the cluster.
Security certificates
The Trusted CA Certificate and Server Certificate used by the TelePresence Conductor are specific to each
peer. They must be uploaded individually on each peer.
Administration access
The SSH service and LCD panel settings are specific to each peer. They can be different for each peer.
Note: The username and password for the administrator account is shared across peers.
Locations
All ad hoc or rendezvous IP addresses assigned to Locations must be different for each peer in the cluster.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 37 of 48
Troubleshooting
Troubleshooting
Unable to cluster the TelePresence Conductor
When running a TelePresence Conductor without a valid release key (as TelePresence Conductor
Essentials) clustering is not supported. Contact your Cisco account representative to obtain release key and
option keys.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 38 of 48
Appendix 1: Unified CM version 8.6.2 configuration
Username Enter the username of the TelePresence Conductor administration user. This appears on the
TelePresence Conductor's Administrator accounts page (Users > Administrator accounts)
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 39 of 48
Appendix 1: Unified CM version 8.6.2 configuration
4. Click Save.
5. Click Reset for the changes to take effect.
6. At the top right corner of the screen in the Related Links: field, select Back to Find/List and click Go. You
will be taken back to the to the Conference Bridges page.
7. Verify that the TelePresence Conductor is registered with Unified CM.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 40 of 48
Appendix 2: Unified CM version 9.x configuration
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 41 of 48
Appendix 2: Unified CM version 9.x configuration
3. Enter the following into the relevant fields, leave other fields as their default values:
MCU Modify the SIP listening port, if appropriate for your design, otherwise leave the default.
Conference
bridge SIP
port
Username Enter the username of the TelePresence Conductor administration user. This appears on
the TelePresence Conductor's Administrator accounts page (Users > Administrator
accounts)
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 42 of 48
Appendix 2: Unified CM version 9.x configuration
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 43 of 48
Appendix 3: IP ports and protocols
If you are using the TelePresence Conductor's built-in Firewall rules feature then you must ensure that it is
not configured to drop or reject traffic sent to UDP ports 4369 4380.
IPSec communications
For IPSec between TelePresence Conductor cluster peers:
n AES256 is used for encryption, SHA256 (4096 bit key length) is used for authentication; peers are identified
by their IP address and are authenticated using a pre-shared key
n Main mode is used during the IKE exchange
n diffie-hellman group modp4096 is used
MTU size
The default MTU size on the TelePresence Conductor is 1500 bytes. Under normal conditions this has no
effect on the cluster. However, if there are network elements between the cluster peers (which is not
recommended), you must ensure consistent MTU size throughout the path. Cluster replication could fail if the
MTU is lower on the path between peers, because the synchronization packets are not allowed to fragment.
Determine which network element in the paths between peers has the lowest MTU value, then adjust each
peer's cluster interface to use that value.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 44 of 48
Appendix 4: Ensuring that Unified CM trusts TelePresence Conductor's server certificate and vice versa
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 45 of 48
Appendix 4: Ensuring that Unified CM trusts TelePresence Conductor's server certificate and vice versa
Repeat this process on every Unified CM server that will communicate with TelePresence Conductor.
Typically this is every node that is running the CallManager service.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 46 of 48
Document revision history
Date Description
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 47 of 48
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE
SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND
RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED
WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL
RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE
SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE
INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE
SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR
A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the
University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating
system. All rights reserved. Copyright 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE
OF THESE SUPPLIERS ARE PROVIDED "AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-
NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING,
WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE
PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL,
CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST
PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS
MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other
countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party
trademarks mentioned are the property of their respective owners. The use of the word partner does not imply
a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual
addresses and phone numbers. Any examples, command display output, network topology diagrams, and
other figures included in the document are shown for illustrative purposes only. Any use of actual IP
addresses or phone numbers in illustrative content is unintentional and coincidental.
2015 Cisco Systems, Inc. All rights reserved.
Cisco TelePresence Conductor Clustering with Unified CM Deployment Guide (XC4.2) Page 48 of 48