Upgrading Toolpack
From TBwiki
(Difference between revisions)
Cboulanger (Talk | contribs) (Undo revision 5854 by Cboulanger (Talk)) |
(Modify upgrade links to remove ADB 2.5 to the 'real' 2.5) |
||
| Line 4: | Line 4: | ||
== Major Upgrades == | == 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. | ||
| − | + | ||
| + | <span style="color:#DC143C; background:#F0E68C"> | ||
| + | '''WARNING: The Advanced Development Branch Toolpack v2.5 is not supported any longer. Please go to [[Toolpack_version_2.5|Advanced Development Branch Toolpack v2.5]] for more details.''' | ||
| + | </span> | ||
| + | *[[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 [[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, just install the new package using the installer) | **From Toolpack release v2.3 (No new prerequisites, just install the new package using the installer) | ||
| − | **From Toolpack release v2.2 (Refer to v2.3 major upgrade procedure) | + | **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]] | *[[toolpack_major_upgrades_2-3|Major upgrade procedure for Toolpack release v2.3]] | ||
| Line 13: | Line 18: | ||
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. | ||
| − | + | <span style="color:#DC143C; background:#F0E68C"> | |
| + | '''WARNING: The Advanced Development Branch Toolpack v2.5 is not supported any longer. Please go to [[Toolpack_version_2.5|Advanced Development Branch Toolpack v2.5]] for more details.''' | ||
| + | </span> | ||
| + | *[[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) | *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]] | *[[toolpack_minor_upgrades_2-3|Minor upgrade procedure for Toolpack release v2.3]] | ||
| Line 20: | Line 28: | ||
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. | ||
| − | *License upgrade procedure for | + | *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.4 (Refer to v2.3 license upgrade procedure) | ||
*[[Add/Change_Licenses#Change Licenses|License upgrade procedure for Toolpack release v2.3]] | *[[Add/Change_Licenses#Change Licenses|License upgrade procedure for Toolpack release v2.3]] | ||
Revision as of 14:48, 25 May 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.
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.
WARNING: The Advanced Development Branch Toolpack v2.5 is not supported any longer. Please go to Advanced Development Branch Toolpack v2.5 for more details.
- 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, just install the new package using the installer)
- 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.
WARNING: The Advanced Development Branch Toolpack v2.5 is not supported any longer. Please go to Advanced Development Branch Toolpack v2.5 for more details.
- 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:
