Upgrading Toolpack: Difference between revisions
(Add v2.4 installation reference to v2.3) |
Cboulanger (talk | contribs) |
||
| Line 4: | Line 4: | ||
== Major Upgrades == | == Major Upgrades == | ||
It is considered a '''major upgrade''' when changing to a full release version or a major point release (e.g., v2.2 to v2.3 or v2.3 to v2.4). Please note that major upgrades require service interruption. | It is considered a '''major upgrade''' when changing to a full release version or a major point release (e.g., v2.2 to v2.3 or v2.3 to v2.4). Please note that major upgrades require service interruption. | ||
*[[Toolpack_version_2.5#Major_Upgrades|Major upgrade procedure for Advanced Development Branch Toolpack v2.5]] | |||
*Major upgrade procedure for Toolpack release v2.4 | *Major upgrade procedure for Toolpack release v2.4 | ||
**From Toolpack release v2.3 (No new prerequisites, just install the new package using the installer) | **From Toolpack release v2.3 (No new prerequisites, just install the new package using the installer) | ||
Revision as of 17:14, 3 December 2009
There are three types of upgrades to Toolpack: minor upgrades, major upgrades, and license upgrades. A fourth type of intervention is a system reconfiguration.
Major Upgrades
It is considered a major upgrade when changing to a full release version or a major point release (e.g., v2.2 to v2.3 or v2.3 to v2.4). Please note that major upgrades require service interruption.
- Major upgrade procedure for Advanced Development Branch Toolpack v2.5
- Major upgrade procedure for Toolpack release v2.4
- From Toolpack release v2.3 (No new prerequisites, just install the new package using the installer)
- From Toolpack release v2.2 (Refer to v2.3 major upgrade procedure)
- Major upgrade procedure for Toolpack release v2.3
Minor Upgrades
It is considered a minor upgrade when moving, for example, from upgrading a minor point release (e.g., v2.3.1 to v2.3.2). Minor upgrades can be done without service interruption if the system is HA.
- Minor upgrade procedure for Toolpack release v2.4 (Refer to v2.3 minor upgrade procedure)
- Minor upgrade procedure for Toolpack release v2.3
License Upgrades
A license upgrade activates new functionality or capacity in the system. Example of license upgrades include adding SS7 signalling or unlocking additional IVR capabilities.
- License upgrade procedure for Toolpack release v2.4 (Refer to v2.3 license upgrade procedure)
- License upgrade procedure for Toolpack release v2.3
System Reconfiguration
A system reconfiguration is required when:
- Upgrading to a multi-host system
- Upgrading to a database HA system
- Modifying basic parameters such as SystemId, Primary local IP, or Secondary local IP
- Modifying configuration databases parameters
It is important to note that system reconfiguration requires service interruption.
To reconfigure the SystemId follow this procedure:
For all other types of reconfiguration follow this procedure: