Upgrading Toolpack
(add v2.6 link) |
|||
| Line 1: | Line 1: | ||
| − | There are three types of | + | There are three types of Toolpack upgrades. They are major, minor and license upgrades. |
| − | + | Note: A fourth type of intervention, not considered an upgrade, is a system reconfiguration. | |
| + | |||
| + | ! Before proceeding with an upgrade, ensure that the active configuration is activated and that there are no errors: | ||
<pre>Global -> Systems -> Edit -> Activate | <pre>Global -> Systems -> Edit -> Activate | ||
</pre> | </pre> | ||
== Major Upgrades == | == Major Upgrades == | ||
| − | It is considered a '''major upgrade''' when changing | + | It is considered to be a '''major upgrade''' when changing from one full release version or a major point release to another. For example, v2.2 to v2.3 or v2.3 to v2.4. |
| + | 'Major upgrades require service interruption.' | ||
*[[Toolpack major upgrades 2-6|Major upgrade procedure for Toolpack release v2.6 from v2.3, v2.4 or v2.5]] | *[[Toolpack major upgrades 2-6|Major upgrade procedure for Toolpack release v2.6 from v2.3, v2.4 or v2.5]] | ||
Revision as of 09:45, 25 March 2014
There are three types of Toolpack upgrades. They are major, minor and license upgrades.
Note: A fourth type of intervention, not considered an upgrade, is a system reconfiguration.
! Before proceeding with an upgrade, ensure that the active configuration is activated and that there are no errors:
Global -> Systems -> Edit -> Activate
Contents |
Major Upgrades
It is considered to be a major upgrade when changing from one full release version or a major point release to another. For example, v2.2 to v2.3 or v2.3 to v2.4. 'Major upgrades require service interruption.'
- Major upgrade procedure for Toolpack release v2.6 from v2.3, v2.4 or v2.5
- For Toolpack release v2.2, follow the Major upgrade procedure for Toolpack release v2.3 then the Major upgrade procedure for Toolpack release v2.6
- 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.6
- 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.6 (Refer to v2.3 license upgrade procedure)
- 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:
