Howto:Migrating a Master/Slave PBX System Step by Step to a newer Firmware Version: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
No edit summary
Line 12: Line 12:
However, in large installations, this is sometimes not possible. In this case a step-by-step migration of each slave PBX is possible. A problem arises when the [[Reference7:Licenses#PBX_Floating_License| floating mechanism]] is used. In such a scenario, the slave PBX has no PBX licenses installed. Instead, all PBX licenses are installed on the master PBX and distributed to the slave PBXs when needed.  
However, in large installations, this is sometimes not possible. In this case a step-by-step migration of each slave PBX is possible. A problem arises when the [[Reference7:Licenses#PBX_Floating_License| floating mechanism]] is used. In such a scenario, the slave PBX has no PBX licenses installed. Instead, all PBX licenses are installed on the master PBX and distributed to the slave PBXs when needed.  


Now you must decide whether you start with upgrading the master PBX or a slave PBX. Either way you will run into problems:
Now you must decide whether you start with upgrading the master PBX or a slave PBX. Either way you might run into problems:


* update the master PBX first
* update the master PBX first
If the master PBX is updated, you will need to update the licenses from the old version to the new version. Otherwise the master PBX has no licenses and cannot accept the incoming registrations of the slave PBXs or IP-phones. However, as soon as the licenses on the master are updated to the new firmware version, there are no valid licenses for the slave PBXs that still run the old firmware available
If the master PBX is updated, you will need to update the licenses from the old version to the new version. Otherwise the master PBX has no licenses and cannot accept the incoming registrations of the slave PBXs or IP-phones. However, as soon as the licenses on the master are updated to the new firmware version, there are no valid licenses for the slave PBXs(which still use the old firmware)


* update a slave PBX first
* update a slave PBX first
In this case the slave PBXs will receive licenses valid only for the previous firmware from the master (as the master still runs the old firmware).  No valid licenses for the slave PBX are available
In this case the slave PBXs will receive licenses valid only for the previous firmware from the master (as the master still uses the old firmware).  No valid licenses for the slave PBX are available


===Resolution===
===Resolution===
The master PBX must distribute licenses of both firmware types. To do this, follow these steps:


# upgrade the master PBX to the new firmware version (e.g. v8).  
===v8 to v9 update===
# use my.innovaphone to download an ''encrypted version'' of the old license - type (e.g. v7)
* Starting with v8 hf15, the update process has been improved. A PBX running with v8hf15 firmware will accept v9 PBX licenses and use them as it would have v8 licenses. Therefore the update process when is simple:
# use my.innovaphone to download an ''encrypted version'' of the new license - type (e.g. v8). This requires that the license assigned to the device is under SSA
 
# upload both license files to the master PBX. The master PBX will now distribute both old- and new-type licenses using the floating model.
# Make sure that the Master PBX and its slave use at least v8hf15 firmware.
# Upgrade Master PBX to latest v9 version and upload only v9 licenses
# Upgrade the Slave's PBX step by step to latest build of v9. During the time of upgrade v8 Slaves will accept and work with the v9 licenses received from the Master PBX.
 
===v7 to v8/v9 update===
* when updating PBXs from v7 firmware, the previously described mechanism cannot be used. A v7 Slave PBX will not work with v8 or v9 licenses (i.e. licenses from another version than v7).
Therefore the master PBX must distribute licenses of both firmware types. To do this, follow these steps:
 
# Upgrade the Master PBX to v8h14 and upload encrypted licenses for v7,v8,v9.
# Upgrade the Slave's PBX to latest build of v9(or v8) desired.
# Upgrade Master PBX to v9(or v8 - similar to version of Slave PBX).


===Known Problems===
===Known Problems===
Line 33: Line 42:
During the migration, no more than the maximum licenses available in any of the versions for a given type must be used.  For example, if there are ''n'' Port8 licenses and ''m'' Port9 licenses available and ''m'' is greater than ''n'', then the sum of all Port8 and Port9 licenses used must not exceed ''m''.  Exceeding this limit is a violation of licensing terms.  This rule does not apply if the different license versions have been bought separately (that is, with no SSA in place).
During the migration, no more than the maximum licenses available in any of the versions for a given type must be used.  For example, if there are ''n'' Port8 licenses and ''m'' Port9 licenses available and ''m'' is greater than ''n'', then the sum of all Port8 and Port9 licenses used must not exceed ''m''.  Exceeding this limit is a violation of licensing terms.  This rule does not apply if the different license versions have been bought separately (that is, with no SSA in place).


 
Note: There are some [[Support:Firmware_v9hotfix3_/_v8hotfix19_/_v7hotfix31_should_not_be_mixed_with_earlier_versions | incompatibilities between v9hf3 and earlier versions]], some features may not work between v9hf3 Slaves and v8hf14 Master during this upgrade process like the blind transfer and CTI. Therefore the customer should be made aware of this limitations during the upgrade process.
* For versions higher than v8hf14 on Master PBX the Slaves PBX's with '''v7 version''' will not be able to receive Registration licenses and register any device. For this scenario where exist v7 slaves it is recommended to:
 
# Upgrade Master PBX to v8h14 and upload encrypted licenses for v7,v8,v9.
# Upgrade the Slave's PBX to latest build of v9 desired.
# Upgrade Master PBX to v9 (similar to version of Slave PBX).
 
* For versions higher than v8hf14 on Master PBX and Slave PBX with '''v8 version''' the process of update will be more simple.
 
# Upgrade Master PBX to latest v9 version and upload only v9 licenses
# Upgrade the Slave's PBX step by step to latest build of v9. During the time of upgrade v8 Slaves will accept and work with the v9 licenses floated by the Master PBX.
 
 
Note: There are some [[Support:Firmware_v9hotfix3_/_v8hotfix19_/_v7hotfix31_should_not_be_mixed_with_earlier_versions | incompatibilities between v9hf3 and earlier versions]], some features may not work between v9hf3 Slaves and v8hf14 Master during this upgrade process like the blind transfer and CTI so costumer should be aware of this limitations during the upgrade process.


== Related Articles ==
== Related Articles ==

Revision as of 18:39, 15 October 2012

Applies To

This information applies to

  • innovaphone PBX Systems V7 and newer

More Information

Problem Details

When performing a firmware version upgrade (e.g. from v7 to v8) in a master/slave installation it is best to do the complete upgrade procedure in one step.

However, in large installations, this is sometimes not possible. In this case a step-by-step migration of each slave PBX is possible. A problem arises when the floating mechanism is used. In such a scenario, the slave PBX has no PBX licenses installed. Instead, all PBX licenses are installed on the master PBX and distributed to the slave PBXs when needed.

Now you must decide whether you start with upgrading the master PBX or a slave PBX. Either way you might run into problems:

  • update the master PBX first

If the master PBX is updated, you will need to update the licenses from the old version to the new version. Otherwise the master PBX has no licenses and cannot accept the incoming registrations of the slave PBXs or IP-phones. However, as soon as the licenses on the master are updated to the new firmware version, there are no valid licenses for the slave PBXs(which still use the old firmware)

  • update a slave PBX first

In this case the slave PBXs will receive licenses valid only for the previous firmware from the master (as the master still uses the old firmware). No valid licenses for the slave PBX are available

Resolution

v8 to v9 update

  • Starting with v8 hf15, the update process has been improved. A PBX running with v8hf15 firmware will accept v9 PBX licenses and use them as it would have v8 licenses. Therefore the update process when is simple:
  1. Make sure that the Master PBX and its slave use at least v8hf15 firmware.
  2. Upgrade Master PBX to latest v9 version and upload only v9 licenses
  3. Upgrade the Slave's PBX step by step to latest build of v9. During the time of upgrade v8 Slaves will accept and work with the v9 licenses received from the Master PBX.

v7 to v8/v9 update

  • when updating PBXs from v7 firmware, the previously described mechanism cannot be used. A v7 Slave PBX will not work with v8 or v9 licenses (i.e. licenses from another version than v7).

Therefore the master PBX must distribute licenses of both firmware types. To do this, follow these steps:

  1. Upgrade the Master PBX to v8h14 and upload encrypted licenses for v7,v8,v9.
  2. Upgrade the Slave's PBX to latest build of v9(or v8) desired.
  3. Upgrade Master PBX to v9(or v8 - similar to version of Slave PBX).

Known Problems

  • If the newer license versions are available to you by virtue of an SSA agreement, you must make sure to obey the licensing conditions.

During the migration, no more than the maximum licenses available in any of the versions for a given type must be used. For example, if there are n Port8 licenses and m Port9 licenses available and m is greater than n, then the sum of all Port8 and Port9 licenses used must not exceed m. Exceeding this limit is a violation of licensing terms. This rule does not apply if the different license versions have been bought separately (that is, with no SSA in place).

Note: There are some incompatibilities between v9hf3 and earlier versions, some features may not work between v9hf3 Slaves and v8hf14 Master during this upgrade process like the blind transfer and CTI. Therefore the customer should be made aware of this limitations during the upgrade process.

Related Articles

Howto:Firmware_Upgrade_V6_V7_and_later
Howto:Firmware_Upgrade_V7_V8
Howto:Firmware_Upgrade_V8_V9

Retrieved from "https://wiki.innovaphone.com/index.php?title=Howto:Migrating_a_Master/Slave_PBX_System_Step_by_Step_to_a_newer_Firmware_Version&oldid=26949"