Cisco Unified Presence, Release 7.x -- How to Configure Intercluster Peers on Cisco Unified Presence
From DocWiki
Main page: Cisco Unified Presence, Release 7.x
Contents |
Previous Topic
How to Configure Intercluster Peers in Cisco Unified Presence Administration
Configuring Intercluster Peers
Perform this procedure on the publisher node of the local Cisco Unified Presence cluster, and on the publisher node of the remote Cisco Unified Presence cluster (that you wish your local cluster to form a peer relationship with).
Before You Begin
- Activate the AXL interface on the local Cisco Unified Presence node.
- Confirm that the AXL interface is activated on the remote Cisco Unified Presence publisher node.
- Acquire the user name and password for the intercluster application user on the Cisco Unified Presence remote server.
Restriction
We recommend that you use TCP as the intercluster trunk transport for all Cisco Unified Presence clusters.
This window is updated every 20 seconds with the latest intercluster status information.
Procedure
1. Perform one of the following actions:
If you want to: Action Add an intercluster peer
- Select Presence > Inter-clustering.
- Select Add New.
Update an intercluster peer
- Find the record. See the Finding a Network Component topic for instructions.
- Edit the record as required.
2. Enter the intercluster remote server settings as described in the table below.
Field Description Peer Address
Enter the IP address of the publisher node of a remote Cisco Unified Presence cluster for the remote address.
AXL Username
Enter the username of the application user on the Cisco Unified Presence remote server that has AXL permissions.
AXL Password
Enter the associated password of the application user on the Cisco Unified Presence remote server that has AXL permissions.
Confirm AXL Password
Reenter the AXL password.
Protocol
Enter the preferred protocol for SIP communication.
Note: If the specified protocol is configured in the remote Cisco Unified Presence cluster, then "Protocol" is used. If the remote cluster does not contain a Cisco Unified Presence SIP Proxy listener of "Protocol" type, then a protocol is selected according to the following precedence: UDP, TCP, TLS.
External Phone Number Mask
(Optional) Enter the External Phone Number Mask value. This is the E164 mask to apply to Directory Numbers retrieved from the remote cluster.
Note: The default E164 mask is overridden by the E164 mask assigned to a Line Appearance from the remote cluster. Cisco IP Phone Messenger (IPPM) uses the DN and E164 mask from the remote cluster for dial back functionality.
Force Sync
Select Force Sync to manually force Cisco Unified Presence to synchronize data with this remote server.
Note: This button displays only after you successfully create an intercluster peer.
3. Review the intercluster remote server status, and repeat the above step if necessary.
4. Select Save.
Troubleshooting Tips
- If DNS is available in your network, the address configured for the intercluster peer could be a DNS SRV FQDN that resolves to the remote Cisco Unified Presence cluster nodes.
- By default, Cisco Unified Presence turns on the Intercluster Sync Agent parameter. You must turn on the Intercluster Sync Agent on all nodes in the Cisco Unified Presence cluster because in addition to synchronizing user information from the local publisher node to the remote publisher node, the Intercluster Sync Agent also handles security between all nodes in the clusters.
Related Topics
What To Do Next
Intercluster Peer Status
The settings in the table below indicate whether your intercluster peer configuration has succeeded or failed.
Table: Intercluster Peer Status
| Field | Description |
|---|---|
|
Peer Connectivity |
If successful, the remote server can be reached using the AXL connection. If a failure occurs, the system is unable to connect to the remote server using AXL. |
|
Peer Compatibility) |
If successful, the remote server has a valid user location table and is enabled for interclustering. If a failure occurs, the remote server does not have a user location table and is not compatible. |
|
Peer Proxy Domain |
If successful, the remote server has a proxy domain that matches the local Cisco Unified Presence proxy domain. If a failure occurs, the proxy domains of the two clusters (local and remote) do not match. |
|
CUP Version |
If successful, the version of the remote server is displayed. |
|
CUCM Publisher Version |
If successful, the version of the Cisco Unified Communications Manager publisher is displayed. |
|
Unique CUCM Cluster |
If successful, the test verifies that two Cisco Unified Communications Manager (local and remote) are not part of the same cluster.
Caution! It is a incorrect to configure two Cisco Unified Presence peers to point at Cisco Unified Communications Manager servers that are in the same cluster. Be aware that Release 6.x Cisco Unified Presence peers cannot verify whether the Cisco Unified Communications Manager cluster is unique, and pass this test by default. |
|
Associated Users |
If successful, the users associated with the remote server are displayed. |
|
Duplicate Users |
If successful, the duplicate users associated with the remote server are displayed. If the number of duplicate users is zero, a View Duplicates hyperlink is displayed allowing you to view a duplicate user report. |
|
Certificate Status Note: This status item only displays if you select TLS as the protocol type. |
If successful, the connection is secure.
|
Related Topics
Verifying the Intercluster Peer Status
Before You Begin
Configure an intercluster peer.
Procedure
- Select Presence > Inter-Clustering.
- Select the intercluster remote server entry under the Peer Address menu.
- Select Find.
- Verify that there are check marks beside each of the result entries for the intercluster remote server.
- Select Diagnostics > System Troubleshooter.
- In the section InterClustering Troubleshooter:
- Verify the status of each of the intercluster remote server entries.
- Make sure that the Associated Users value equals the number of users on the remote cluster.
