Cisco Unified Presence, Release 7.x -- How to Configure the Load Balancer for Redundancy
From DocWiki
Main page: Cisco Unified Presence, Release 7.x
Contents |
Previous Topic
About the Load Balancer
For redundancy and high-availability purposes, you can incorporate a load balancer into the federated network. Cisco recommends the Cisco CSS 11500 Content Services Switch, which is placed between the Cisco Unified Presence server and the Cisco Adaptive Security Appliance (see Figure: Federated Network between Cisco Unified Presence and Microsoft OCS with High Availability).
The load balancer terminates incoming TLS connections from Cisco Adaptive Security Appliance, and initiates a new TLS connection to route the content to the appropriate backend Cisco Unified Presence server.
Related Topics
Updating the Cisco Unified Presence Servers
When using a load balancer for redundancy, you must update settings on the Cisco Unified Presence publisher and subscriber nodes.
Procedure
| Task | Procedure |
|---|---|
|
Update the federation routing parameter |
Select Cisco Unified Presence Administration > System > Service Parameters > Cisco UP SIP Proxy from the Service menu and enter these values:
|
|
Create a new TLS peer subject |
|
|
Add the TLS peer to the TLS peer subjects list |
|
Related Topics
- Configuring the Federation Routing Parameter
- Creating a new TLS Peer Subject
- Adding the TLS Peer to the Selected TLS Peer Subjects List on Cisco Unified Presence
- How to Exchange Certificates Using CA-Signed Certificates
- Getting More Information
How to Update the Cisco Adaptive Security Appliance
When using a load balancer, the foreign domain still sends messages to the public CUP address, but the Cisco Adaptive Security Appliance maps that address to a virtual IP address on the load balancer. Thus, when the Cisco Adaptive Security Appliance receives messages from the foreign domain, it forwards it to the load balancer. The load balancer then passes it on to the appropriate Cisco Unified Presence servers.
To support this configuration, you must make some changes to the Cisco Adaptive Security Appliance:
Updating the Static PAT Messages
You must update the static PAT messages to include the load balancer details.
Procedure
| Task | Configuration Example |
|---|---|
| Changes Required for Cisco Unified Presence Publisher | |
|
Change the static PAT to use an arbitrary, unused port for the public CUP address. |
Change: static (inside,outside) tcp <Public CUP IP address> 5061 <Routing CUP private IP address> 5062 netmask 255.255.255.255 to: static (inside,outside) tcp <Public CUP IP address> 55061 <Routing CUP/Publisher private IP address> 5062 netmask 255.255.255.255 |
|
Add a new static PAT to allow messages sent to the public Cisco Unified Presence address to be forwarded to the virtual port address (on whichever port the load balancer is listening for TLS messages). |
static (inside,outside) tcp <Public CUP address> 5061 <Load Balancer VIP> 5062 netmask 255.255.255.255 |
| Changes Required for Cisco Unified Presence Subscriber | |
|
Add a new access list for the load balancer virtual IP address. You must add an access list for each foreign domain that Cisco Unified Presence needs to access. |
access-list ent_lber_to_foreign_ocs extended permit tcp host <subscriber private ip address> host <foreign domain public IP address> 5061 |
|
Add a new access list for a foreign domain to initiate messages to a Cisco Unified Presence server when the load balancer virtual IP address is in place. You must add an access list for each foreign domain that needs to access Cisco Unified Presence. |
access-list ent_lcs_to_lber_routgcup extended permit tcp host <foreign domain public ip address> host <cup public ip address> 65061 |
Related Topics
Updating the Access Lists
To support the load balancer, you also need to update the access lists on the Cisco Adaptive Security Appliance specific to your deployment scenario.
Procedure
| Deployment Scenario | Task | Configuration Example |
|---|---|---|
|
A Cisco Unified Presence server federating with one or more foreign domains |
Add a new access list for the new load balancer virtual IP address. You must add an access list for each foreign domain that Cisco Unified Presence needs to access. |
Publisher: access-list ent_lber_to_foreign_ocs extended permit tcp host <Virtual IP address> host <foreign domain public IP address> 5061
access-list ent_lber_to_foreign_ocs extended permit tcp host <subscriber private ip address> host <foreign domain public IP address> 5061 |
|
Add a new access list for a foreign domain to initiate messages to a Cisco Unified Presence server when the load balancer virtual IP address is in place. You must add an access list for each foreign domain that needs to access Cisco Unified Presence. |
Publisher: access-list ent_lcs_to_lber_routgcup extended permit tcp host <foreign domain public ip address> host <cup public ip address> eq 55061
access-list ent_lcs_to_lber_routgcup extended permit tcp host <foreign domain public ip address> host <cup public ip address> eq 65061 | |
|
For each access list, add a new class to incorporate the new access list. |
class ent_lber_to_foreign_ocs match access-list ent_lber_to_foreign_ocs | |
|
For each class, make an entry in the policy-map global_policy for messages initiated by Cisco Unified Presence. |
policy-map global_policy class ent_lber_to_foreign_ocs inspect sip sip_inspect tls-proxy ent_cup_to_foreign | |
|
For each class, make an entry in the policy-map global_policy for messages initiated on a foreign domain. |
policy-map global_policy class ent_lcs_to_lber_routgcup inspect sip sip_inspect tls-proxy ent_foreign_to_cup | |
|
|
The foreign domain ASA must allow access to the arbitrary ports which have been chosen for our local domain publisher and the subscriber. |
access-list ent_cup_to_foreignPubcupwlber extended permit tcp host <foreign domain private CUP address> host <public CUP address of our local domain> 55061 access-list ent_cup_to_foreignSubcupwlber extended permit tcp host <foreign domain private CUP address> host <public CUP address of our local domain> 65061 |
|
For each access list, add a new class to incorporate the new access list. | ||
|
For each class, make an entry in the policy-map global_policy. |
Related Topics
- Access List Configuration Requirements
- Updating the Static PAT Messages
- Updating the TLS Proxy Instances
- Getting More Information
Updating the TLS Proxy Instances
Update the TLS proxy instances on the Cisco Adaptive Security Appliance.
Procedure
| Task | Configuration Example |
|---|---|
|
Update TLS-PROXY |
Change tls-proxy ent_foreign_to_cup server trust-point msoft_publicfqdn client trust-point cup_proxy client cipher-suite aes128-sha1 aes256-sha1 3des-sha1 null-sha1 ! tls-proxy ent_cup_to_foreign server trust-point cup_proxy client trust-point msoft_publicfqdn client cipher-suite aes128-sha1 aes256-sha1 3des-sha1 null-sha1 to: tls-proxy ent_foreign_to_cup server trust-point msoft_publicfqdn client trust-point msoft_publicfqdn client cipher-suite aes128-sha1 aes256-sha1 3des-sha1 null-sha1 ! tls-proxy ent_cup_to_foreign server trust-point msoft_publicfqdn client trust-point msoft_publicfqdn client cipher-suite aes128-sha1 aes256-sha1 3des-sha1 null-sha1 |
Related Topics
- Updating the TLS Proxy Instances
- Updating the Static PAT Messages
- Updating the Access Lists
- Getting More Information
How to Update the CA-Signed Security Certificates
When adding the load balancer to the configuration, you must also generate CA-signed security certificates between the load balancer and the Cisco Adaptive Security Appliance and Cisco Unified Presence server as described in these sections:
- Configuring the Security Certificate between the Load Balancer and the Cisco Unified Presence Server
Configuring the Security Certificate between the Load Balancer and the Cisco Adaptive Security Appliance
This topic provides an overview of the required steps for configuring the security certificate between the load balancer and the Cisco Adaptive Security Appliance. For details, refer to Cisco CSS 11500 Content Services Switch documentation: http://www.cisco.com/en/US/products/hw/contnetw/ps792/products_installation_and_configuration_guides_list.html
Procedure
| Task | Procedure |
|---|---|
|
Generate CA-signed certificate for the load balancer on the Cisco Adaptive Security Appliance. |
Use the crypto ca enroll command and specify the FQDN of the load balancer. |
|
Import the CA-signed certificate from the Cisco Adaptive Security Appliance to the load balancer.. |
Use the copy ssl command. |
|
Generate a CA-signed certificate for the Cisco Adaptive Security Appliance on the load balancer.. |
These steps provide an overview but refer to the CSS SSL Configuration Guide for details:
|
|
Import the CA-signed certificate from the load balancer to the Cisco Adaptive Security Appliance |
Use the crypto ca trustpoint command.
|
Related Topics
- Configuring the Security Certificate between the Load Balancer and the Cisco Unified Presence Server
- Configuring the Certificate on Cisco Adaptive Security Appliance using SCEP Enrollment
- Importing the Certificate onto Cisco Unified Presence Server1
- Importing the Certificate onto Cisco Unified Presence Server2
- How to Configure Security Certificate Exchange Between Cisco Adaptive Security Appliance and Microsoft Access Edge (External Interface) Using a Microsoft CA
- How to Exchange Certificates Using CA-Signed Certificates
- Getting More Information
Configuring the Security Certificate between the Load Balancer and the Cisco Unified Presence Server
This topic provides an overview of the required steps for configuring the security certificate between the load balancer and the Cisco Unified Presence nodes.
Procedure
| Task | Procedure |
|---|---|
|
Generate a CA-signed certificate on both the publisher and subscriber nodes. |
Follow the instructions to exchange certificates using CA-signed certificates. |
|
Import the CA-signed certificates (from the publisher and subscriber nodes) to the load balancer |
Use the copy ssl and ssl associate commands. |
Related Topics
- Configuring the Security Certificate between the Load Balancer and the Cisco Adaptive Security Appliance
- How to Exchange Certificates Using CA-Signed Certificates
- Updating the TLS Proxy Instances
- Getting More Information
Updating the Microsoft Components
You must update some Microsoft components with the load balancer details.
Procedure
| Task | Procedure |
|---|---|
|
Update all instances of the FQDN to correspond to the load balancer FQDN. | |
|
Update the domain name in the IM Provider list with the load balancer. |
Define the network address of the IM service provider as the public FQDN of the Load Balancer |
Related Topics
Configuring the Load Balancer
This topic gives an overview of the necessary tasks for configuring the Cisco CSS 11500 Content Services Switch for this integration. The Cisco CSS 11500 Content Services Switch must have an SSL Accelerator Module installed and configured in back-end SSL mode.For detailed information on each task, refer to the Cisco CSS 11500 Content Services Switch documentation at the following URL:
Procedure
| Task | Additional Notes |
|---|---|
|
Configure certificate exchange between Cisco CSS 11500 Content Services Switch and Cisco Unified Presence. |
|
|
Configure certificate exchange between Cisco CSS 11500 Content Services Switch and Cisco Adaptive Security Appliance. | |
|
You must define a virtual SSL server in an SSL proxy list for an SSL module to properly process and terminate SSL communications from the client and initiate a HTTP connection to the server. |
|
|
Create a Back-End SSL server entry in SSL Proxy List for each Cisco Unified Presence server. |
|
|
Create an SSL service for SSL termination for each Cisco Unified Presence server. |
|
|
Create the SSL module. |
|
|
Create an internal content rule to route the decrypted data from the ASA to CUP server. | |
|
Create content rule to route TLS data to the SSL module for decryption and load-balancing. | |
|
Create a NAT association between the VIP and the back-end Cisco Unified Presence servers. | |
|
When using a Cisco CSS 11500 Content Services Switch directly between Cisco Unified Presence and Microsoft OCS (no Cisco Adaptive Security Appliance), you must be able to resolve the certificate Subject Common Name for the Cisco Unified Presence server to Cisco Unified Presence IP address from OCS. Also each Cisco Unified Presence server Subject Common Name must be in the OCS host authorization list. |