Upgrading Toolpack
From TBwiki
(Difference between revisions)
| (12 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{DISPLAYTITLE:Upgrading Toolpack System}} | ||
| + | |||
There are three types of Toolpack upgrades. They are major, minor and license upgrades. | 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. | + | 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''' | |
| + | |||
<pre>Global -> Systems -> Edit -> Activate | <pre>Global -> Systems -> Edit -> Activate | ||
</pre> | </pre> | ||
| − | == | + | == Software Upgrades == |
| + | |||
| + | === Toolpack Upgrades === | ||
| + | '''Since v2.7.148''', it is possible to do minor and major upgrades using the web portal: | ||
| + | |||
| + | *[[Toolpack:System_Settings_B#Package_Upgrade|Toolpack v2.9: Package Upgrade]] | ||
| + | *[[Toolpack:System_Settings_A#Package_Upgrade|Toolpack v2.8: Package Upgrade]] | ||
| + | *[[Web_Portal_Tutorial_Guide_v2.7#Minor Package Upgrade|Toolpack v2.7: Package Upgrade]] | ||
| + | |||
| + | |||
| + | '''Major Upgrade (previous to 2.7.148)''' | ||
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. | 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 | + | <span style="color:#B22222"> |
| + | ''NOTE'': Major upgrades needs service interruption. | ||
| + | </span> | ||
| + | * [[Tmedia_Major_Upgrade|Major upgrade procedure for Toolpack release v2.7]] (previous to 2.7.148) | ||
*[[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]] | ||
| − | **For Toolpack release v2.2, follow the [[Toolpack major upgrades 2-3|Major upgrade procedure for Toolpack release v2.3]] | + | **For Toolpack release v2.2, follow the [[Toolpack major upgrades 2-3|Major upgrade procedure for Toolpack release v2.3]] followed by the [[Toolpack major upgrades 2-6|Major upgrade procedure for Toolpack release v2.6]] |
*[[Toolpack major upgrades 2-5|Major upgrade procedure for Toolpack release v2.5 from v2.3 or v2.4]] | *[[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]] | + | **For Toolpack release v2.2, follow the [[Toolpack major upgrades 2-3|Major upgrade procedure for Toolpack release v2.3]] followed by 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, [[Toolpack major upgrades 2-4|v2.4 major upgrade procedure]]) | **From Toolpack release v2.3 (No new prerequisites, [[Toolpack major upgrades 2-4|v2.4 major upgrade procedure]]) | ||
| Line 21: | Line 38: | ||
*[[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]] | ||
| − | |||
| − | + | '''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). | ||
| + | |||
| + | *[[Web_Portal_Tutorial_Guide_v2.7#Minor Package Upgrade|Minor upgrade procedure for Toolpack release v2.7]] | ||
*[[Tmedia_Minor_Upgrade|Minor upgrade procedure for Toolpack release v2.6]] | *[[Tmedia_Minor_Upgrade|Minor upgrade procedure for Toolpack release v2.6]] | ||
*[[Tmedia_Minor_Upgrade|Minor upgrade procedure for Toolpack release v2.5]] | *[[Tmedia_Minor_Upgrade|Minor upgrade procedure for Toolpack release v2.5]] | ||
| Line 30: | Line 49: | ||
*[[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]] | ||
| − | |||
| − | |||
| − | + | === Operating System Upgrades === | |
| − | *License upgrade | + | The TMG-CONTROL software is running over CentOS operating system. To upgrade the operating system, it requires the following procedure: |
| − | + | *[[Upgrade_CentOS|Upgrade TMG Linux packages]] | |
| − | *[[Add/Change Licenses#Change_Licenses|License upgrade procedure for Toolpack | + | |
| + | |||
| + | == 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. | ||
| + | *[[Add/Change Licenses#Change_Licenses|License upgrade procedure for Toolpack]] | ||
| + | |||
== System Reconfiguration == | == System Reconfiguration == | ||
| Line 48: | Line 70: | ||
*Modifying configuration databases parameters | *Modifying configuration databases parameters | ||
| − | + | ||
| + | '''Important: System reconfiguration requires an interruption of service.''' | ||
To reconfigure the [[System Id|SystemId]] follow this procedure: | To reconfigure the [[System Id|SystemId]] follow this procedure: | ||
| Line 60: | Line 83: | ||
[[Category:Toolpack]] | [[Category:Toolpack]] | ||
[[Category:Tdev_OAM%26P|Upgrade]] | [[Category:Tdev_OAM%26P|Upgrade]] | ||
| + | [[Category:Tmonitor_OAM%26P|Upgrade]] | ||
| + | [[Category:Revise on Major]] | ||
Latest revision as of 16:58, 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
Toolpack Upgrades
Since v2.7.148, it is possible to do minor and major upgrades using the web portal:
Major Upgrade (previous to 2.7.148)
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.7 (previous to 2.7.148)
- 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
Operating System Upgrades
The TMG-CONTROL software is running over CentOS operating system. To upgrade the operating system, it requires the following procedure:
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.
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:
