Cluster
Create Cluster
In this procedure, we refer to the primary server as primary and to the two secondary servers as node A and node B.
Before you begin
When a secondary server joins a cluster, all of the data on the secondary server is discarded. If you need to retain the data for future use, back up the secondary server before joining it to the cluster.
Procedure
Step 1 |
Deploy the .OVA to all three servers. |
Step 2 |
For all three Cisco Jabber Guest servers, make sure that you set the FQDN. For more information, see Set FQDN of Cisco Jabber Guest Server. |
Step 3 |
Sign in to each server as root. |
Step 4 |
To establish the primary, on one of the three servers: |
Step 5 |
To join node A to the cluster, on one of the remaining servers: |
Step 6 |
To join node B to the cluster, on the remaining server: |
Step 7 |
Allow node A to communicate with node B: |
Step 8 |
Allow node B to communicate with node A: |
What to do next
For each of the three servers in the cluster, configure the appropriate SIP trunk in Cisco Unified Communications Manager or zones in Cisco TelePresence Video Communication Server, depending on the type of servers deployed in your network.
Change IP Address or Hostname of Server in Cluster
You can modify the IP address or hostname of a server in the cluster if it changes for any reason.
In this procedure, we refer to the server that we change the IP address or hostname of as the target server.
Procedure
Step 1 |
Make a note of the current IP address or hostname of the target server. You need to enter it during Step 4.b. |
Step 2 |
(Optional) If you are changing the IP address or hostname of the primary server, demote the primary server to a secondary server, otherwise proceed to Step 3:
|
Step 3 |
Change the IP address or hostname of the target server. |
Step 4 |
In the cluster, change the IP address or hostname of the target server:
|
Step 5 |
On the other secondary server (node B), block communication from the old IP address or hostname of the target server and allow communication with the new IP address or hostname of the target server:
|
Step 6 |
Make sure that each server in the cluster is healthy by typing: |
Step 7 |
On the target server, restart Tomcat:
|
Step 8 |
If you changed the IP address or hostname of the primary server, in Cisco Jabber Guest Administration, update the domain used for links:
|
What to do next
If you are using a self-signed certificate, you must generate a new certificate after you change the IP address or hostname of the server.
Demote Primary Server to Secondary Server
You can demote or stepdown a primary server to a secondary server. For example, if you need to do maintenance on the primary server.
A new primary server is elected from the remaining servers in the cluster.
Procedure
Step 1 |
Sign in to the primary server as root. |
Step 2 |
Type
|
Step 3 |
Verify that
the server has been demoted to secondary by typing
|
Upgrade Cluster
In this procedure, we refer to the primary server as node A and to the two secondary servers as node B and node C.
Procedure
Step 1 |
Make a note of which nodes are the primary and secondary servers:
|
Step 2 |
Make sure that you have backed up each server in the cluster. |
Step 3 |
Download JabberGuest-11.x.x.x-Upgrade-Only.iso. |
Step 4 |
Open vSphere Client. |
Step 5 |
If a CD/DVD drive is not connected to the virtual machine, add one:
|
Step 6 |
On each server, connect the CD/DVD drive to the ISO image:
|
Step 7 |
Prepare to upgrade node B by updating the reverse proxy so that call requests are sent to node A first, node C second, and no call requests are sent to node B:
|
Step 8 |
Make sure that there are no calls on node B:
|
Step 9 |
Upgrade node B by doing the following: |
Step 10 |
Prepare to upgrade node C by updating the reverse proxy so that call requests are sent to node A first, node B second, and no call requests are sent to node C:
|
Step 11 |
Make sure that there are no calls on node C:
|
Step 12 |
Upgrade node C by repeating Step 9. |
Step 13 |
Verify that node B and node C are back up and running by signing in to Cisco Jabber Guest Administration as an administrator.
|
Step 14 |
Prepare to upgrade node A by updating the reverse proxy so that call requests are sent to node C first, node B second, and no call requests are sent to node A:
|
Step 15 |
Wait until there are no calls on node A: |
Step 16 |
Demote node A to a secondary server:
---> <IP address/hostname of node B or node C> PRIMARY .
|
Step 17 |
Upgrade node A by repeating Step 9. |
Step 18 |
Verify that node A is back up and running by signing in to Cisco Jabber Guest Administration as an administrator. |
Step 19 |
Promote node A to the primary server: |
Step 20 |
Update the order of the reverse proxy. |
Step 21 |
To ensure that the latest version of Cisco Jabber Guest Administration is loaded in your browser, refresh any browser instances that are signed in to Cisco Jabber Guest Administration or that have the Cisco Jabber Guest Administration sign-in page loaded. |
Remove Server from Cluster
Important |
After a server is removed from a cluster, it cannot be run as a standalone Cisco Jabber Guest instance. To do this, the server must be reinstalled. |
In this procedure, we refer to the secondary server that we want to remove as node A, and to the other secondary server as node B
Procedure
Step 1 |
Sign in to each server in the cluster as root. |
Step 2 |
On the primary server: |
Step 3 |
On node A,
block communication from node B by typing
|
Step 4 |
On node B,
block communication with node A by typing |