Upgrading Toolpack: Difference between revisions
No edit summary |
(Added warning on activation errors) |
||
| Line 1: | Line 1: | ||
There are three types of upgrades to Toolpack: minor upgrades, major upgrades, and license upgrades. A fourth type of intervention is a system reconfiguration. | There are three types of upgrades to Toolpack: minor upgrades, major upgrades, and license upgrades. A fourth type of intervention is a system reconfiguration. | ||
! Before any type of upgrade, make sure the active configuration has been activated and there are no errors: | |||
<pre>Global -> Systems -> Edit -> Activate | |||
</pre> | |||
== 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 major upgrades 2-5|Major upgrade procedure for Toolpack release v2.5 from v2.3 or v2.4]] | ||
**For Toolpack release v2.2, follow the [[ | **For Toolpack release v2.2, follow the [[Toolpack major upgrades 2-3|Major upgrade procedure for Toolpack release v2.3]] then the [[Toolpack major upgrades 2-5|Major upgrade procedure for Toolpack release 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, [[ | **From Toolpack release v2.3 (No new prerequisites, [[Toolpack major upgrades 2-4|v2.4 major upgrade procedure]]) | ||
**From Toolpack release v2.2 (Refer to [[ | **From Toolpack release v2.2 (Refer to [[Toolpack major upgrades 2-3|v2.3 major upgrade procedure]]) | ||
*[[ | *[[Toolpack major upgrades 2-3|Major upgrade procedure for Toolpack release v2.3]] | ||
== Minor Upgrades == | == 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. | |||
*[[Toolpack minor upgrades 2-5|Minor upgrade procedure for Toolpack release v2.5]] | |||
*Minor upgrade procedure for Toolpack release v2.4 (Refer to v2.3 minor upgrade procedure) | |||
*[[Toolpack minor upgrades 2-3|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.5 (Refer to v2.3 license upgrade procedure) | |||
* | *License upgrade procedure for Toolpack release v2.4 (Refer to v2.3 license upgrade procedure) | ||
* | *[[Add/Change Licenses#Change_Licenses|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 [[System Id|SystemId]], [[Gateway Address|Primary local IP]], or [[Gateway Address|Secondary local IP]] | |||
*Modifying configuration databases parameters | |||
It is important to note that system reconfiguration requires service interruption. | |||
To reconfigure the [[System Id|SystemId]] follow this procedure: | |||
*[[Toolpack system systemId reconfiguration 2-3|SystemId reconfiguration procedure for Toolpack release v2.3]] | |||
For all other types of reconfiguration follow this procedure: | |||
*[[Toolpack system reconfiguration 2-3|System reconfiguration procedure for Toolpack release v2.3]] | |||
[[Category:Toolpack]] | |||
Revision as of 17:28, 26 November 2010
There are three types of upgrades to Toolpack: minor upgrades, major upgrades, and license upgrades. A fourth type of intervention is a system reconfiguration.
! Before any type of upgrade, make sure the active configuration has been activated and there are no errors:
Global -> Systems -> Edit -> Activate
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 Toolpack release v2.5 from v2.3 or v2.4
- For Toolpack release v2.2, follow the Major upgrade procedure for Toolpack release v2.3 then the Major upgrade procedure for Toolpack release v2.5
- Major upgrade procedure for Toolpack release v2.4
- From Toolpack release v2.3 (No new prerequisites, v2.4 major upgrade procedure)
- 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.5
- 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.5 (Refer to v2.3 license upgrade procedure)
- 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: