Upgrading Toolpack
(→Major Upgrades: add possible major upgrades) |
(added category) |
||
| Line 25: | Line 25: | ||
It is important to note that system reconfiguration requires service interruption. | It is important to note that system reconfiguration requires service interruption. | ||
*[[toolpack_system_reconfiguration_2-3|System reconfiguration procedure for Toolpack release v2.3]] | *[[toolpack_system_reconfiguration_2-3|System reconfiguration procedure for Toolpack release v2.3]] | ||
| + | |||
| + | |||
| + | [[category:Toolpack]] | ||
Revision as of 15:20, 27 July 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.
Contents |
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.
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.
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.
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.
