handling instructions - technical particularities€¦ · handling instructions cls 5 2.2. features...

Handling Instructions -

Technical Particularities

CLS - Licensing of integration product (feature)

OpenScape 4000 V8

Handling Instructions CLS

2

History of Change

Ver. Released RDB# Changes

1.0 2016-10-13 6412 Initial Creation

2.0 2017-08-15 The document has been adapted to the new SSP handling


3

Table of Contents

1. Introduction 4

1.1. Purpose of the document 4

2. Product Information 4

2.1. General 4

2.2. Features 5

3. First Licensing 6

4. Add-On Licensing 6

5. Rehost 6

6. Shift 7

7. License Transfer 7

8. Upgrade 7

8.1. Upgrade V6 to V8 Base/User 7

8.2. Partial Upgrade V6 Flex License to V8 Flex License 8

8.3. Upgrade V7 to V8 Base/User 8

8.4. Partial Upgrade V7 Flex/TDM to V8 Flex/TDM License 10

9. Multiple Product Licensing 10


4

1. Introduction 1.1. Purpose of the document The document describes the differences of the CLS licensing process between this product (feature) and the standard

process of OpenScape License Management (see document License Guidelines).

2. Product Information 2.1. General a) Product supports system ID and can be ordered via configuration tool and linear.

b) “OS4K V8 Generating System 730” cannot be used together with other features and will generate a pre-

defined license key with a duration of 730 days.

c) “OS4K V8 Duplex” enables the user to enter a second Locking ID for the Standby server (second license key).

d) The product support network licensing. This means that one license file is generated that contains the aggregated licenses of several systems. To build such a network do this:

o Activate each system to its own Locking Id

o Fill the field “Locking Id of Network CLA”, of all systems that should belong to the network, with the Locking Id of the used CLA.

o For every system select an administration group

e) However new systems added directly to an existing network license do not observe an activation period. They require

regular licenses right away.

f) In case of an OpenScape 4000 V8 network a second license key is generated if on the network CLA Locking ID an OpenScape 4000 Manager with enabled Standby Server exists. In this case the second license key is generated for this Standby Locking ID.

g) The product uses administration groups. For standalone systems the administration group defaults to 1 and needs not to be selected from the drop down. In case of network licensing systems are grouped based on this selection. Systems that belong to the same administration group share license from their pool.

h) Every “OpenScape 4000 V8 Base” license key contains 1 licenses for the “Java Husim Phonetester”. i) Remaining duration of the SUSE Upgrade Protection (updates for the SUSE operating system) is shown by the

feature “OpenScape 4000 V8 SLES Upgr. Prot. 6 y. (initial)”. When activating “OpenScape 4000

V8 SLES Upgr. Prot. 3 y. (prol.)”, the duration of already activated “OpenScape 4000 V8 SLES

Upgr. Prot. 6 y. (initial)” is extended for further 3 years (1095 days).

j) Any number of “OpenScape 4000 V8 SLES Upgr. Prot. 3 y. (prol.)” can be activated under the

condition, that their amount is not exceeding the amount of already activated “OpenScape 4000 V8 SLES Upgr. Prot. 6

y. (initial)”. k) Furthermore, “OpenScape 4000 V8 SLES Upgr. Prot. 6 y. (initial)” and “OpenScape 4000 V8

SLES Upgr. Prot. 3 y. (prol.)” cannot be activated at the same time.

l) Upgrade provides OpenScape 4000 V8 SLES Upgr. Prot. 6 y. (initial) which is valid for 6 years

(2190 days) m) In case of network licensing, an additional license key is created for every HiPath 4000 Assistant which contains the

SUSE component because the network license key does not. The Assistant will inform whether a SUSE upgrade is allowed or not.

n) The product only accepts ALI type of locking id. o) To use OS4K V8 Disaster Recovery, OS4K V8 Duplex is required. p) OS4K V8 Disaster Recovery enables user to enter two additional Locking IDs; one ID used for Disaster A server,

other one is used for Disaster B server. Each Locking ID must be different.


5

2.2. Features

Feature # Feature Name

F31505-K229-B1 OS4K V8/HiPath 4000 SIEL ID for Common Control B

F31505-K124-C18 OS4K V8 Partial Upgrade TDM V7 to V8

F31505-K124-C17 OS4K V8 Upgrade TDM V7 to V8

F31505-K124-C16 OS4K V8 Upgrade Base V7 to V8

F31505-K124-C15 OS4K V8 Partial Upgrade Flex V7 to V8

INFO-UPG-3-ADW00 OS4K V8 Info - Upgraded from V6

F31505-K124-C14 OS4K V8 Upgrade Flex V7 to V8

F31505-K124-C13 OS4K V8 TDM User


F31505-K124-C11 OS4K V8 Upgrade Base V6 to V8

F31505-K124-C10 OS4K V8 Partial Upgrade Flex V6 to V8


F31505-K124-C9 OS4K V8 Upgrade Flex V6 to V8

F31505-K124-C8 OS4K V8 Generating System 730

F31505-K124-C6 OS4K V8 Duplex

F31505-K124-C5 OS4K V8 AP-Emergency

F31505-K124-C4 OS4K V8 Signaling Suvivability

F31505-K124-C3 OS4K V8 Flex User

F31505-K124-C2 OS4K V8 Assistant

F31505-K124-C22 OS4K V8 Upgrade Base RG8350 V7 to V8

F31505-K124-C1 OS4K V8 Base

F31505-K124-C21 OS4K V8 Upgrade Base RG8350 V6 to V8


F31505-K124-C20 OS4K V8 Upgrade TDM to Flex

F31505-K156-C4 OS4K V8 SLES Upgr. Prot. 3 y. (prol.)

F31505-K156-C1 OS4K V8 SLES Upgr. Prot. 6 y. (Initial)


6

F31505-K155-D6 OSMO V9 User for OS4K V8

F31505-K124-C12 OS4K V8 Disaster Recovery

Feature quantity limits:

Feature Min Qty. Limit Max Qty. Limit

OS4K V8/HiPath 4000 SIEL ID for Common Control B 90

OS4K V8 TDM User 32767

OS4K V8 Generating System 730 1

OS4K V8 Duplex 1

OS4K V8 AP-Emergency 83

OS4K V8 Signaling Suvivability 83

OS4K V8 Flex User 32767

OS4K V8 Assistant 1

OS4K V8 Base 1 1

OS4K V8 SLES Upgr. Prot. 6 y. (Initial) 90

OS4K V8 Disaster Recovery 1

OSMO V9 User for OS4K V8 12000

3. First Licensing One of these licenses has to be used:

• OpenScape 4000 V8 Base

• OpenScape 4000 V8 Generating System 730

4. Add-On Licensing In case of linear Add-On activation the Installed Base will be updated.

5. Rehost


7

6. Shift

7. License Transfer Orders with system id should be transferred as whole.

8. Upgrade

8.1. Upgrade V6 to V8 Base/User

It is possible to upgrade the whole HiPath 4000 V6 system to OpenScape 4000 V8. After this upgrade, no licenses

should remain on the old V6 system. If required, flex for trunks should be deactivated in V6 by activating HP4000 V6

deactivate Flex for Trunks (F31505-K124-A19) on the V6 system before the upgrade, then the upgrade should be

carried out.

Upgrade Validation (required upgrade features):

HiPath 4000 V6 Mapping Qty. OpenScape 4000 V8

HiPath 4000 V6 Base 1 OS4K V8 Upgrade Base V6 to V8

HiPath 4000 V6 Flex 1 OS4K V8 Upgrade Flex V6 to V8

Upgrade Mapping Table:


HiPath 4000 V6 Base 1 OS4K V8 Base

1 OS4K V8 Info - Upgraded from V6

HiPath 4000 V6 Assistant 1 OS4K V8 Assistant

HiPath 4000 V6 Signaling

Survivability

1 OS4K V8 Signaling Suvivability

HiPath 4000 V6 AP-Emergency 1 OS4K V8 AP-Emergency


8

HiPath 4000 V6 SLES Upgrade

Protection for 3 years (initial)

1 OS4K V8 SLES Upgr. Prot. 6 y.

(Initial)

HiPath 4000 V6 Duplex 1 OS4K V8 Duplex

HiPath 4000 V6 Flex 1 OS4K V8 Flex User

8.2. Partial Upgrade V6 Flex License to V8 Flex License

It is possible to perform a partial upgrade from a HiPath 4000 V6 system to an existing OpenScape 4000 V8 system with

F31505-K124-C10 feature. Only Flex licenses can be upgraded.



HiPath 4000 V6 Flex 1 OS4K V8 Partial Upgrade Flex V6 to

V8



HiPath 4000 V6 Flex 1 OS4K V8 Flex User

8.3. Upgrade V7 to V8 Base/User

It is possible to upgrade the whole OpenScape 4000 V7 system to OpenScape 4000 V8. After this upgrade, no licenses

should remain on the old V7 system. If required, flex for trunks should be deactivated in V7 by activating OpenScape

4000 V7 deactivate Flex for Trunks (F31505-K124-B19) on the V7 system before the upgrade, then the upgrade should

be carried out.


9


OpenScape 4000 V7 Mapping Qty. OpenScape 4000 V8

OpenScape 4000 V7 Base 1 OS4K V8 Upgrade Base V7 to V8

OpenScape 4000 V7 Flex 1 OS4K V8 Upgrade Flex V7 to V8

OpenScape 4000 V7 TDM 1 OS4K V8 Upgrade TDM V7 to V8



OpenScape 4000 V7 Base 1 OS4K V8 Base

1 OS4K V8 Info - Upgraded from V7

OpenScape 4000 V7 Assistant 1 OS4K V8 Assistant

OpenScape 4000 V7 Signaling

Suvivability

1 OS4K V8 Signaling Suvivability

OpenScape 4000 V7 Duplex 1 OS4K V8 Duplex



OpenScape 4000 V7 SLES Upgr. Prot. 3

y. (initial)

1 OS4K V8 SLES Upgr. Prot. 6 y.

(Initial)

OpenScape 4000 V7 Flex 1 OS4K V8 Flex User

OpenScape 4000 V7 TDM 1 OS4K V8 TDM User


10

8.4. Partial Upgrade V7 Flex/TDM to V8 Flex/TDM License

It is possible to perform a partial upgrade from an OpenScape 4000 V7 system to an existing OpenScape 4000 V8

system with F31505-K124-C15 and F31505-K124-C20 feature. Only Flex and TDM licenses can be upgraded.



OpenScape 4000 V7 Flex 1 OS4K V8 Partial Upgrade Flex V7 to

V8

OpenScape 4000 V7 TDM 1 OS4K V8 Partial Upgrade TDM V7 to

V8



OpenScape 4000 V7 Flex 1 OS4K V8 Flex User

OpenScape 4000 V7 TDM 1 OS4K V8 TDM User

9. Multiple Product Licensing

Multiple Product Licensing is a functionality of CLS which enables feature sharing between two products or two versions

of the same product. OS 4000 V8 can share the features of OS 4000 V7 and HiPath 4000 V6 according to the following

mapping table:


11

OpenScape 4000 V8 HiPath 4000 V6, OpenScape 4000 V7

Component ID Component Name Component ID Component Name

Duplex Duplex System Duplex Duplex System

Flex_User OpenPath Flex User Flex_User OpenPath Flex User

Survivability SIGNALING SURVIVABILITY Survivability SIGNALING SURVIVABILITY

APE CC-AP FUER AP EMERGENCY APE CC-AP FUER AP EMERGENCY

Table: Mapping Configuration between OS 4000 V8, OS 4000 V7 and HP 4000 V6

Note: The components in the table corresponds to the features in the license file.

This table can be read in the following way:

- OS 4000 V8 can use the Flex_User feature of H4000 V6 instead of its’ Flex_User feature i.e. If all the

Flex_User features of OS 4000 V8 are allocated in the network, then CLA can allocate from Flex_User features

that are available on H4000 V6 systems in the same network.

- OS 4000 V8 can use the Duplex feature of H4000 V6 instead of its’ Duplex feature i.e. If all the Duplex features

of OS 4000 V8 are allocated in the network, then CLA can allocate from Duplex features that are available on

H4000 V6 systems in the same network.

- OS 4000 V8 can use the APE feature of H4000 V6 instead of its’ APE feature i.e. If all the APE features of OS

4000 V8 are allocated in the network, then CLA can allocate from APE features that are available on H4000 V6

systems in the same network.

- OS 4000 V8 can use the Survivability feature of H4000 V6 instead of its’ Survivability feature i.e. If all the

Survivability features of OS 4000 V8 are allocated in the network, then CLA can allocate from Survivability

features that are available on H4000 V6 systems in the same network.

About Unify

Unify is the Atos brand for communication and collaboration solutions. At the core of the Atos Digital Workplace portfolio,

Unify technology enables organizations of all sizes to transform the way they collaborate, creating a more connected and

productive workforce which can dramatically improve team performance, individual engagement and business efficiency.

Unify products represent a strong heritage of technology innovation, reliability and flexibility. Their award-winning intuitive

user experience can be delivered through almost any device and in any combination of cloud or on-premise deployment.

Augmented by Atos’ secure digital platforms, vertical solutions and transformation services, they set the global standard for

a rich and reliable collaboration experience that empowers teams to deliver extraordinary results.

Copyright © Unify Software and Solutions GmbH & Co.KG. 2018

Mies-van-der-Rohe-Strasse 6, 80807 Munich, Germany.

All rights reserved.

Reference No.: A31002-P3010-D101-2-7629

The information provided in this document contains merely general descriptions or

characteristics of performance which in case of actual use do not always apply as described

or which may change as a result of further development of the products. An obligation to provide

the respective characteristics shall only exist if expressly agreed in the terms of contract.

Availability and technical specifications are subject to change without notice.

Unify, OpenScape, OpenStage and HiPath are registered trademarks of Unify Software and

Solutions GmbH & Co.KG.

All other company, brand, product and service names are trademarks or registered trademarks of

their respective holders.

handling instructions - technical particularities€¦ · handling instructions cls 5 2.2. features...

Documents