Upgrading Toolpack
| Line 78: | Line 78: | ||
[[Category:Toolpack]] | [[Category:Toolpack]] | ||
[[Category:Tdev_OAM%26P|Upgrade]] | [[Category:Tdev_OAM%26P|Upgrade]] | ||
| + | [[Category:Revise on Major]] | ||
Revision as of 09:55, 17 May 2016
There are three types of Toolpack upgrades. They are major, minor and license upgrades.
Note: A fourth type of intervention, not considered to be 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 |
Software Upgrades
Since v2.7.145, it is possible to do minor and major upgrades using the web portal:
Major Upgrade (previous to 2.7.145)
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.
NOTE: Major upgrades needs service interruption.
- Major upgrade procedure for Toolpack release v2.9
- Major upgrade procedure for Toolpack release v2.8
- Major upgrade procedure for Toolpack release v2.7
- For Toolpack release previous to 2.7.145, follow the Major upgrade procedure for Toolpack release v2.7 first to upgrade to at least release 2.7.145.
- 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 followed by 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 followed by 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 to be a minor upgrade when moving from one minor point release to another. For example, v2.3.1 to v2.3.2. Minor upgrades can be done without service interruption if the system is configured as High Availability (HA).
- Minor upgrade procedure for Toolpack release v2.7
- 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. Examples 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
Important: System reconfiguration requires an interruption of service.
To reconfigure the SystemId follow this procedure:
For all other types of reconfiguration follow this procedure:
