Upgrading Toolpack: Difference between revisions
(clean up) |
(clean up and consolidation of content) |
||
| 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. | ||
| Line 7: | Line 5: | ||
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. | 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. | ||
A license upgrade activates new functionality or capacity in the system. Example of license upgrades include adding SS7 signalling or unlocking additional IVR capabilities. | A '''license upgrade''' activates new functionality or capacity in the system. Example of license upgrades include adding SS7 signalling or unlocking additional IVR capabilities. | ||
A system reconfiguration is required when: | A '''system reconfiguration''' is required when: | ||
* Upgrading to a multi-host system | * Upgrading to a multi-host system | ||
* Upgrading to a database HA system | * Upgrading to a database HA system | ||
* Modifying basic parameters | * Modifying basic parameters such as [[Gateway_Port|TbxGwPort]], [[Gateway_Address|TbxGwAddr0]], or [[Gateway_Address|TbxGwAddr1]] | ||
* Modifying configuration databases parameters. | * Modifying configuration databases parameters | ||
It is important to note that system reconfiguration requires service interruption. | |||
== Major Upgrades == | == Major Upgrades == | ||
*[[toolpack_major_upgrades_2-3|Major upgrade procedure for Toolpack release v2.3]] | |||
*[[toolpack_major_upgrades_2-3|Major | |||
== Minor Upgrades == | == Minor Upgrades == | ||
*[[toolpack_minor_upgrades_2-3|Minor upgrade procedure for Toolpack release v2.3]] | |||
== License Upgrades == | == License Upgrades == | ||
*[[toolpack_license_upgrades_2-3|License upgrade procedure for Toolpack release v2.3]] | |||
*[[toolpack_license_upgrades_2-3|License | |||
== System Reconfiguration == | == System Reconfiguration == | ||
*[[toolpack_system_reconfiguration_2-3|System reconfiguration procedure for Toolpack release v2.3]] | |||
* | |||
Revision as of 16:06, 7 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.
It is considered a major upgrade when changing to a full release version or a major point release (e.g., v1 to v2 or v2.2 to v2.3). Please note that major upgrades require service interruption.
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.
A license upgrade activates new functionality or capacity in the system. Example of license upgrades include adding SS7 signalling or unlocking additional IVR capabilities.
A system reconfiguration is required when:
- Upgrading to a multi-host system
- Upgrading to a database HA system
- Modifying basic parameters such as TbxGwPort, TbxGwAddr0, or TbxGwAddr1
- Modifying configuration databases parameters
It is important to note that system reconfiguration requires service interruption.
Major Upgrades
Minor Upgrades
License Upgrades