Upgrading Toolpack

From TBwiki
(Difference between revisions)
Jump to: navigation, search
 
(44 intermediate revisions by 9 users not shown)
Line 1: Line 1:
This section explains how to upgrade toolpack
+
{{DISPLAYTITLE:Upgrading Toolpack System}}
  
 +
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.
  
  
== Minor Upgrades ==
+
'''Before proceeding with an upgrade, ensure that the active configuration is activated and that there are no errors'''
 +
 +
<pre>Global -&gt;&nbsp;Systems -&gt; Edit -&gt;&nbsp;Activate
 +
</pre>
 +
== Software Upgrades ==
  
Upgrades are considered minor when moving, for example, from 2-3-1 to 2-3-2.
+
=== Toolpack Upgrades ===
 +
'''Since v2.7.148''', it is possible to do minor and major upgrades using the web portal:
  
'''Note''': Minor upgrades can be done without service interruption if the system is HA.
+
*[[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]]
  
=== Release 2-3 ===
 
  
==== Run Toolpack Installer ====
+
'''Major Upgrade (previous to 2.7.148)'''
  
: [[toolpack_installer_2-3|Toolpack Installer]]
+
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.
  
==== Active New package ====
+
<span style="color:#B22222">
 +
''NOTE'': Major upgrades needs service interruption.
 +
</span>
  
: Create a new package in web portal
+
* [[Tmedia_Major_Upgrade|Major upgrade procedure for Toolpack release v2.7]] (previous to 2.7.148)
: Active new package
+
*[[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]] 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]]
 +
**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
 +
**From Toolpack release v2.3 (No new prerequisites, [[Toolpack major upgrades 2-4|v2.4 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]]
  
  
== Major Upgrades ==
+
'''Minor Upgrades'''
  
Upgrades are considered major when moving, for example, from 2-2-20 to 2-3-2.
+
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).  
  
'''Warning''': Major upgrades require service interruption.
+
*[[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.5]]
 +
*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]]
  
=== Release 2-3 ===
 
  
==== Stop Toolpack Service ====
 
  
  tbtoolpack stop
+
=== Operating System Upgrades ===
 +
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]]
  
==== Follow Migration Guide ====
 
  
: [[toolpack_migration_2-3|Toolpack system 2-3 migration guide]]
+
== 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]]
  
==== Run Toolpack Installer ====
 
  
: [[toolpack_installer_2-3|Toolpack Installer]]
+
== System Reconfiguration  ==
  
==== Start Toolpack Service ====
+
A '''system reconfiguration''' is required when:
  
  tbtoolpack start
+
*Upgrading to a multi-host system
 +
*Upgrading to a database HA system
 +
*Modifying basic parameters such as [[System Id|SystemId]], [[Gateway Address|Primary local IP]], or [[Gateway Address|Secondary local IP]]
 +
*Modifying configuration databases parameters
 +
 
 +
 
 +
'''Important:  System reconfiguration requires an interruption of service.'''
 +
 
 +
To reconfigure the [[System Id|SystemId]] follow this procedure:
 +
 
 +
*[[Toolpack system systemId reconfiguration 2-3|SystemId reconfiguration procedure for Toolpack release v2.3]]
 +
 
 +
For all other types of reconfiguration follow this procedure:
 +
 
 +
*[[Toolpack system reconfiguration 2-3|System reconfiguration procedure for Toolpack release v2.3]]
 +
 
 +
[[Category:Toolpack]]
 +
[[Category:Tdev_OAM%26P|Upgrade]]
 +
[[Category:Tmonitor_OAM%26P|Upgrade]]
 +
[[Category:Revise on Major]]

Latest revision as of 17: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.


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).


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:


Important: System reconfiguration requires an interruption of service.

To reconfigure the SystemId follow this procedure:

For all other types of reconfiguration follow this procedure:

Personal tools