Upgrading Toolpack

From TBwiki
(Difference between revisions)
Jump to: navigation, search
(add gw port and gw address links)
(clean up)
Line 1: Line 1:
This section explains how to upgrade toolpack
+
__NoTOC__
  
 +
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.
  
== 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.
  
Upgrades are considered minor when moving, for example, from 2-3-1 to 2-3-2.
+
A license upgrade activates new functionality or capacity in the system. Example of license upgrades include adding SS7 signalling or unlocking additional IVR capabilities.
  
'''Note''': Minor upgrades can be done without service interruption if the system is HA.
+
A system reconfiguration is required when:
 
+
* Upgrading to a multi-host system.
 
+
* Upgrading to a database HA system.
=== Release 2-3 ===
+
* Modifying basic parameters like [[Gateway_Port|TbxGwPort]], [[Gateway_Address|TbxGwAddr0]], [[Gateway_Address|TbxGwAddr1]].
 
+
* Modifying configuration databases parameters.
: [[toolpack_minor_upgrades_2-3|Minor upgrades procedure for release 2-3]]
+
  
  
 
== Major Upgrades ==
 
== Major Upgrades ==
  
Upgrades are considered major when moving, for example, from 2-2-20 to 2-3-2.
+
*[[toolpack_major_upgrades_2-3|Major upgrades procedure for release 2-3]]
  
'''Warning''': Major upgrades require service interruption.
 
  
=== Release 2-3 ===
+
== Minor Upgrades ==
  
: [[toolpack_major_upgrades_2-3|Major upgrades procedure for release 2-3]]
+
: [[toolpack_minor_upgrades_2-3|Minor upgrade procedure for Toolpack release v2.3]]
  
  
 
== License Upgrades ==
 
== License Upgrades ==
  
License upgrade can occurs adding a new feature (i.e ss7) or replacing a temporary license.
+
*[[toolpack_license_upgrades_2-3|License upgrades procedure for release 2-3]]
 
+
=== Release 2-3 ===
+
 
+
: [[toolpack_license_upgrades_2-3|License upgrades procedure for release 2-3]]
+
  
  

Revision as of 14:52, 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 like TbxGwPort, TbxGwAddr0, TbxGwAddr1.
  • Modifying configuration databases parameters.


Major Upgrades


Minor Upgrades

Minor upgrade procedure for Toolpack release v2.3


License Upgrades


System Reconfiguration

This procedure is required when:

  • Upgrading to a multi-host system.
  • Upgrading to a database HA system.
  • Modifying basic parameters like TbxGwPort, TbxGwAddr0, TbxGwAddr1.
  • Modifying configuration databases parameters.

Warning: System reconfiguration requires service interruption.

Release 2-3

System reconfiguration procedure for release 2-3
Personal tools