Manual Upgrade of a Sentinel VoLTE 2.7.0 install in a Rhino Production Cluster
|
This manual procedure is no longer the recommended way to upgrade VoLTE in production. Use the semi-automated VoLTE upgrade procedure instead. |
|
This document assumes a 2 node cluster, with each node on a separate server. Modify the steps accordingly if you have more nodes. |
Upgrade Steps
1 |
From the Rhino client bin directory |
||
|---|---|---|---|
2 |
Run a Rhino full export |
||
3 |
On the node101 server, stop Rhino |
||
4 |
On the node102 server, stop Rhino |
||
5 |
Stop REM from the init-d directory (if you followed these post install Instructions otherwise you can stop Catalina. |
||
6 |
Backup your Apache Tomcat install to a new location |
||
7 |
If you have configured REM redundancy, repeat steps 5 and 6 on each node where you have Apache Tomcat REM installed |
||
8 |
On the node101 server, backup the node101 directory to a new location |
||
9 |
On the node101 server, recreate node101 (say yes to initializing the db) |
||
10 |
Copy any configuration settings that you changed during your initial install from your old node101 directory to your new node101 directory. e.g. jvm settings, paths, ports etc. |
||
11 |
Start node101 |
||
12 |
On the node102 server, backup the node102 directory to a new location |
||
13 |
On the node102 server, recreate node102 (say yes to initializing the db) |
||
14 |
Copy any configuration settings that you changed during your initial install from your old node102 directory to your new node102 directory. e.g. jvm settings, paths, ports etc. |
||
15 |
Start node102 |
||
16 |
Install your license into Rhino |
||
17 |
Install the new Sentinel VoLTE version and REM extension as per these instructions:
|
||
18 |
Import the exported profiles into Rhino |
||
19 |
Restart Rhino nodes and REM |
