05 OS82125EN80GLA00 License & SW Management

NetAct 8 License and Software Management

Version 1

© Nokia Solutions and Networks

1 (138)

Legal notice

Legal notice Intellectual Property Rights All copyrights and intellectual property rights for Nokia Solutions and Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Solutions and Networks training material, are the exclusive property of Nokia Solutions and Networks. Nokia Solutions and Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Solutions and Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Solutions and Networks training material. Individuals can use the Nokia Solutions and Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Solutions and Networks. The Nokia Solutions and Networks training material cannot be used outside of an agreed Nokia Solutions and Networks training session for development of groups without the prior written agreement of Nokia Solutions and Networks. Indemnity The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia Solutions and Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Solutions and Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products are given “as is” and all liability arising in connection with such hardware or software products shall be defined conclusively in a separate agreement between Nokia Solutions and Networks and the customer. However, Nokia Solutions and Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which may not be covered by the document. Nokia Solutions and Networks will correct errors in the document as soon as possible. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY MONETARY LOSSES,SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT This document and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. The NSN logo is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Export Control Marks: AL: N and ECCN=5E991 or AL: N and ECCN=N (as in TCM course core data) This course is subject to the European Export Control Restrictions. Copyright ©2014 Nokia Solutions and Networks. All rights reserved. .

Version 1


2 (138)

Content

Content 1 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 2 2.1 2.2 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 4 4.1 4.2 4.3 4.4 4.5 5 5.1 5.2 5.3 6 6.1 6.2

Version 1

NetAct 8 Software Licensing NetAct Licensing License keys License usage types NetAct Sales Features NetAct release upgrade protection NetAct hard lock NetAct alarms Licenses for OEM Software Software Asset Protection Managing License Keys vs. Software Asset Monitoring Software Asset Monitoring Managing License Keys License Management Overview License Manager Licensing Concepts: NE Licensing Licensing Concepts: Pool License Licensing Concepts: License Sets License States License Management Tasks License Notifications Viewing Recent Operations Software Asset Monitoring Software Asset Monitoring Application Monitoring Modules Monitoring Modules Types Software Asset Monitoring Notifications Software Asset Monitoring Reports Software Management and Remote NE Backup Software Management in NetAct Software Manager Software Manager Operations Network Element Backup Support Network Elements Remote Backup from NetAct Network Elements Backup Archive


5 6 9 10 12 17 19 22 25 27 28 31 35 36 38 42 44 46 50 52 81 83 85 86 88 90 91 93 97 98 100 103 123 124 126

3 (138)

Content

7 Exercises Exercise 1 Exercise 2 Exercise 3 Exercise 4

Version 1

129 131 133 135 137


4 (138)

NetAct 8 Software Licensing

1

Version 1



5 (138)


1.1

NetAct Licensing

The NetAct system as such is delivered with all the functionality/features, called NetAct Sales Features, which are implemented in particular release of the NetAct. On the other hand, not all functionality/ features are available for use. These functionality/features need to be unlocked using license key files which need to be ordered from the NSN. A license-based application, service, solution, feature, or functionality can only be used with a valid software license. This behavior is related to NetAct SW asset protection concept which assumes that all NetAct Sales Features are protected with License Keys and without the order of proper license, NetAct SW is not delivered and installed. NetAct SW asset protection concept introduces license protection for:  NetAct Features  Network Elements integration  NetAct Capacity  NetAct SW Release upgrade  Term licensing model. As a part of the NetAct SW asset protection concept, NetAct SW Release Upgrade, NetAct Hard Lock and NetAct Alarms functionalities are implemented to ensure proper NetAct system operation, as well as to provide easy and lucid way of NetAct licenses handling. License Manager is the application that is used for managing software licenses in the NetAct. For more information about license management, see Managing License Keys chapter. Software Asset Monitoring is the application that enables monitoring of the NetAct Standard SW capacity features for NetAct Radio. For more information about software asset monitoring principles, see Software Asset Monitoring chapter. Note: All the licenses are bound to each NetAct cluster, which means that they cannot be moved between different NetAct clusters.

Version 1


6 (138)


NetAct 8 SW Licensing Overview • For Network Elements integrations, NetAct Capacity, SW Release Upgrade and Time Based Licensing. • Feature level license protection continues to be based on ON / OFF license Key

Mandatory license key protection

expansion projects have to remember to NetAct Capacity Licenses must • Network order additional capacity for NetAct Standard SW match the actual capacity of the licenses too Managed Network

• No automated NetAct license key migration from OSS5 to NetAct 8 in upgrade. • NetAct 8 licenses have to be ordered in every case.

Current OSS5 License Keys (lic) need to be replaced with NetAct 8 License Keys (LK)

License Keys (LK) are tied to a • License Keys have to be ordered per each cluster. keys CAN NOT be moved between NetAct particular NetAct Cluster with • License clusters Target ID 1

©2014 Nokia Solutions and Networks. All rights reserved.

Fig. 1

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia . . Solutions . . . and . Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . .

. . . . . . .7 (138) . . . . . . .


NetAct 8 SW Licensing Strict License Key protection Area protected

NetAct 8 brings significantly stronger license key protection.

How

SW Release upgrade

NetAct 8 SW license key – this license is mandatorily required for SW release.

Network Elements integration

NetAct Standard SW license keys – these licenses are mandatorily required for Network Elements integration.

NetAct Capacity

Capacity of NetAct Standard SW license key. If managed network capacity vs. ordered capacity is crossed then NetAct hard lock mechanism is activated.

NetAct Features: Standard SW – Optional, High Value SW

Majority of sales features are protected by ON/OFF license keys – ordered features are set to ON, rest of features will be OFF.

Time based licensing: Must for High Value SW, proposed for Standard Optional SW.

License keys with end date, after which if renewal order not in place functionality is off or capacity deducted.

OEM SW licensing

The OEM SW with NetAct Cluster fee by NetAct Standard SW LKs. Few vendors’ technical licenses (VMWare, Citrix, Microsoft).

1


Fig. 2

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia . . Solutions . . . and . Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 (138) . . . . . . .


1.2

License keys

NetAct is licensed with using different types of licenses. In general licenses can be divided into:  Term licenses  Functional and capacity licenses

1.2.1

Term licenses

Term licensing concept requires setting validity period for each term license. Validity time of term licenses includes Right To Use (RTU) period and additional time called grace period. Right To Use period have pre-defined time duration, one month or based on a year level, for example two years, when the customer uses the licensed features or functionalities. One month license key is a short term license used for feature level marketing and trialing, while year based license keys are needed for normal use of features and functionalities. After RTU period ends, license renewal is necessary for further use of licensed functionalities. Beside RTU, license key validity time includes 30 day additional time (grace period), when the customer places an order for a new license key. Grace period as well ensures sufficient delivery time for NSN, without consuming RTU time. After license validity period ends, license key expires and all licensed functionalities are turned off, unless new valid license is installed. Before Right To Use period and license key validity time ends, the customer is notified with different alarms, to be aware of ending license key lifetime. For more information about validity notifications, see NetAct hard lock for term licenses in further section in this document. Among term licenses following license keys can be distinguished:  Time-limited license key  Non-time-limited license key (Perpetual)  Temporary license key Term licenses are divided into licenses that have actual expiration date, after which all licensed features are disabled (time-limited license key), and the one that has no actual expiration date, and do not expire (non-time-limited/perpetual license key). Perpetual license keys are term license keys with endless validity period. Temporary licenses are licenses with 90-day validity period, which are used until the NetAct system obtains an acceptance. Temporary license must be replaced with valid license containing term license period. It is necessary to renewed temporary license to proper term license, to use licensed features continuously.

Version 1


9 (138)


1.2.2

Functional and capacity licenses

 On/Off licenses  Capacity licenses On/Off licenses enable functionality and permit the use of licensed software functionality for one or more features or applications. Capacity licenses enable functionality with volume/capacity limitation based on indicators agreed in the contract.

1.3

License usage types

Sales order based:   

Commercial license key Trial license key Test-bed license key

Non-sales order base: 

Emergency license key

Commercial license key is a normally salable item that unlocks desired functionality. Trial license key is used to present new functionality for marketing purposes. Trial license key is a temporary license with 90-day validity time and with 1000 capacity. Test-bed license key unlocks NetAct functionalities for a test purposes of new kind of features in the customer test environment. Test-bed license key is a temporary license with 1 year validity time and with 50 capacity. Emergency license key is non-commercial target-locked license key with 10-day validity time, that permits the use of the licensed application during an estimated trouble period. An emergency license key can be created only by the Technical Support team and can be used to bypass the effect of licensing in case of troubleshooting.

Version 1


10 (138)


NetAct 8 SW Licensing License Key types Functional and Capacity

Time

On/Off licenses

Perpetual licenses:

• Enable functionality / content.

• Endless.

• Used to protect majority High Value SW, Standard SW – Optional features.

• Option for Standard SW, Standard SW – Optional features.

Capacity licenses

Time limited licenses (Term Licenses):

• Enable functionality with volume / capacity limitation.

• Contain expiry date. Without license renewal order feature/capacity is off.

• Protect Standard SW features, and very few High Value SW.

• Protect term licensing business. Trial, Testbed, Emergency are also time limited.

1


Fig. 3

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version 1 . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . © Nokia Solutions and Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 (138) . . . . . . . .


1.4

NetAct Sales Features

NetAct Sales Features are delivered with NetAct and are protected by License Keys. In other words, to validate desired feature/functionality, proper License Key which unblocks respective NetAct Sales Feature, has to be ordered and installed. NetAct is sold with the following NetAct Sales Features protected with respective license keys: • High-Value SW protected with On/Off License Keys • Standard SW - Optional protected with On/Off License Keys • Standard SW protected with Capacity License Keys • HW/OEM SW with Perpetual License Keys

1.4.1

High-Value SW and Standard SW - Optional Sales Features

NetAct High-Value SW and NetAct Standard SW - Optional Sales Features introduce NetAct applications/ optional features. NetAct High-Value SW and NetAct Standard SW - Optional features are protected by On/Off License Keys which unlock features for applications as well as technology support for optional applications.

1.4.2

Standard SW Sales Features

NetAct Standard SW Sales Features offer Network Element management for particular network technology with functionality of fault management, performance management and configuration management. NetAct Standard SW features are associated with Capacity License Keys which enable capacity protection and Network Elements integration. NetAct Standard SW Sales Features are supported for NetAct Radio, NetAct Core and NetAct MBH domains.

Version 1


12 (138)


NetAct 8 SW Licensing Sales Features

Release upgrade

High-Value SW

LK

Standard SW - Optional

LK

Standard SW

LK

Term licensing

Product / Solution

LK

• • •

Optional large high value sales entities Enable differentiation against competition Pricing: Value based pricing with value argumentation

•

•

Covers product base functionality as needed by all customers Enables a working product with sufficient functionality for system deals May include optional sales entities having significantly larger content compared to existing features Pricing: Capacity based

•

Pricing: OEM: Cost Plus, NSN HW: no change

• •

HW / OEM SW

• High-Value SW, Standard SW – Optional and Standard SW are protected by License Keys. • NetAct Radio Standard SW Sales Features are protected with Capacity License Keys.

• Release upgrade is protected with additional License Key. • Term licensing introduced next to the perpetual licensing. High Value SW sold with Term Licensing only! • A customer order is always needed to generate and deliver License Keys. 1


Fig. 4

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version 1 . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . © Nokia Solutions and Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 (138) . . . . . .


NetAct 8 SW Licensing

NetAct 8 introduces term licensing business model which coexist with perpetual license model.

Term licensing Term License for N years

• License for N (1-5) year time period • Additionally short time license for 1 month

• Allows for flexible deal durations on year level

• Paid fully at the start of agreed & committed period • Covers Right-to-use • OPEX/CAPEX based model according to operator accounting • NetAct 8 High Value SW Features are sold in Term licensing model only. Standard SW and Standard SW – Optional SW Sales Features can be sold in Perpetual and Term licensing models. • Perpetual and Term License model has same content for sales features: right-to-use. Term Licensing adds time dimension. • Term License apply to NSN SW only. 1


Fig. 5

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version 1 . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . © Nokia Solutions and Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 (138) . . . . . . . .


NetAct 8 SW Licensing Time based licensing in practice Start date Temp. LK

Purchase Order

Acceptance Go-live

LK Commercial Term License Key Expiry notifiend Period 1 Expiration cation notifications date

Period 2 Renewal

30 days grace period for license renewal

RTU end date

Term License Right To Use Period 1

No renewal

• NetAct SW Term License Keys (LK) have time limitation (start date, end date). Prior to the start date and after the end date licensed feature is off. • Temporary License Keys are used until system acceptance. Term license period starts after that. • Term License Keys’ Right To Use period is enhanced with 30 days validity time for smoothly re-loading LK in the system. • Before License Keys expire new ones have to be ordered and delivered for the next period. • Notifications before remind about need of ordering new licenses. 1


Fig. 6

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version 1 . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . © Nokia Solutions and Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 (138) . . . . . .


NetAct 8 SW Licensing Time based licensing in practice Feature turn off

Right To Use ends

Backward counting

Right To Use expiration

60 days

37 day

30 day

30 days

7 days

0 day

License Key expiration Configurable options

Alarm level Message

Notification with

7 day

0 day

7 days

0 day

First notification 90-30 days before Right To Use expires.

Minor

Major

Critical

Right to use license for feature X will end up in 30 days.

Right to use license for feature X will end up in 7 days.

Right to use license for feature X has ended up. License key will turn it off in 30 days.

Critical

Critical

No license keys to use feature X in 7 days.

No valid license key for feature X. System prevented the usage of feature X.

Alarm in NetAct Monitor*)

Mail to defined persons (in License Manager app) License Manager user interface (when opening the app)

*) License Key delivery for next period clears all the existing alarms and avoids next level alarms/notifications to be sent.

1


Fig. 7

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 . (138) . . . . . . .


1.5

NetAct release upgrade protection

NetAct Release upgrade protection is a concept of secure the NetAct system with one major license key, SW Release Upgrade license. The major license is necessary to be installed to enable any other NetAct software license keys. It means that without this main license, other licenses are not valid and the NetAct system is not usable. NetAct 8 Level SW licensed feature is required for a NetAct 8 SW release and its Enhanced Packages to work properly, and system is not operable until the SW Release Upgrade license key is ordered and installed. The SW Release Upgrade license key with the NetAct 8 Level SW licensed feature, has to be ordered either as a part of release upgrade or as a new NetAct system order.

Version 1


17 (138)


NetAct 8 SW Licensing SW Release upgrade license

NetAct 8

OSS5.x NetAct 7

Release order

L K

NetAct 8 SW release

Each NetAct major release is protected with one licensed feature called NetAct x SW Release NetAct 9

NetAct 8 EP1, EP2… L K

NetAct 9 SW release

L K

Release order

NetAct 9 EP1, EP2… L K

@Com New systems NetAct 8

Installation w/o the order

NetAct 9

No license key will be delivered, hence system not usable. NetAct 8 SW release LK precondition for any other.

All existing license keys don’t work. System not usable until NetAct upgrade bought and NetAct 9 SW release LK delivered.

Upgrade w/o the order

NetAct 8 SW release License Key

NetAct 9 SW release License Key

1


Fig. 8

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 . (138) . . . . . . .


1.6

NetAct hard lock

NetAct hard lock is associated with validity of the license file and affects licensed features availability. Hard lock is triggered for License Keys which are expired or if License Key capacity is exceeded and results in turning features off in case of no Right To Use.

1.6.1

NetAct hard lock for capacity licenses

Hard lock for capacity licenses applies to NetAct Standard SW license keys. For capacity licenses hard lock is activated in case licensed feature capacity is crossed. As a result new network element integration is blocked, as well as configuration management functionality. If the Software Asset Monitoring application detects that NetAct license capacity is exceeded, critical alarm is raised and hard lock mechanism starts after one day grace period. Grace period lasts 24 hours and allows the customer to order a new license key. Otherwise hard lock is triggered and as a consequence new network elements integration is not possible and configuration management functionalities, like upload and provisioning, does not work. To avoid hard lock activation, in case of approaching capacity limits customer is notified with two other alarms, minor and major, with configurable threshold limits. It allows an operator to order a new license key before hard lock activation and with no harm to NetAct operability. The hard lock for capacity licenses is released and related alarm is cleared after installation of new valid license with additional capacity.

1.6.2

NetAct hard lock for term licenses

Hard lock for term licenses concerns NetAct SW license keys and application software license keys which are On/Off or capacity licenses. For term licenses hard lock is triggered in case of license key end date expires, which means if license validity period ends. Without a valid license key the NetAct licensed functionality is blocked from usage or license capacity is deducted. In case license is timed out, critical alarm is raised and hard lock mechanism starts. The hard lock for term licenses results in blockage of NetAct SW licensed features or application software licensed features. Before the end of the license validity period, the customer is notified with three different alarms - minor, major and critical. Minor and major alarms are raised before Right To Use period ends. Critical alarm is raised if the Right To Use period ends or License Key validity period ends. Such behavior allows an operator to purchase a new license key or extend license validity and use the NetAct continuously. The hard lock for term license is released and related alarm is cleared after installation of new valid license key or 7 days after license key expiration.

Version 1


19 (138)


NetAct 8 SW Licensing Hard Lock mechanism NetAct Hard Lock mechanism uses License Keys to cut off features if there is no Right To Use it: • for Time based licensing when License Key end date expires • for NetAct Capacity when License Key capacity limit is exceeded Hard Lock mechanism informs in advance via alarms and e-mails in case of: • License Keys expiration time closes • approaching NetAct Capacity limit NetAct 8 behavior in case of hard lock mechanism is activated: • NetAct features (ON/OFF license) won’t work as long as valid license is missing • Exceeding capacity e.g. for NetAct Radio Standard SW Sales Features (number of Cells, TRXs, etc) results in blocking new Network Elements integration and configuration management functionality (CM upload, provisioning doesn’t work) as long as valid capacity license is missing

1


Fig. 9

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 . (138) . . . . . . .


NetAct 8 SW Licensing Network Elements integration • Network Elements Integration to NetAct is protected by NetAct Standard SW License Keys.

• There is one-to-one linkage of Standard SW Sales Feature with technical license. • NetAct Standard SW Sales Feature structure defines which Network Elements support are sold and opened for integration by delivered license key. NetAct Radio Standard SW

• GSM • GSM-R • WCDMA • LTE •…

NetAct Core Standard SW • PCS-5000 • Mobile Voice Switches • MGW • Flexi NS • Flexi NG • One-NDS • NT HLR FE • Support Elements • ….

1

NetAct MBH Standard SW • Juniper • Cisco • Symmetricom • NetViewer • MWR • Tellabs •…


Fig. 10

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 . (138) . . . . . . .


1.7

NetAct alarms

NetAct alarms functionality is designed to inform user about closing NetAct software license keys validity end date, as well as exceeding NetAct software licenses capacity thresholds. Alarms are related to NetAct hard lock protection functionality for NetAct software licenses. The main idea of alarms functionality is to remind about need of ordering new licenses and to provide seamlessly NetAct system work. NetAct alarms are divided into two groups:  alarms for capacity licenses  alarms for term licenses

1.7.1

Alarms for capacity licenses

Responsibility of exceeding capacity alarms belongs to the Software Asset Monitoring application. Software Asset Monitoring monitors and reports used capacity of software licenses and in case of capacity thresholds are crossed, respective alarm is raised and visible in the NetAct Monitor application. For capacity licenses there are three alarm levels, minor, major and critical. Minor and major alarms start if capacity usage crosses respective alarm thresholds. Threshold limits for minor and major alarms are configurable and can be set in the Software Asset Monitoring application (see Configuring global settings in the Software Asset Monitoring Help document). Critical alarm is raised in case NetAct license capacity is exceeded. To clear existing alarms and further use of a system, order and installation of new license with additional capacity is necessary.

1.7.2

Alarms for term licenses

For alarming about NetAct software licenses which are about to expire, the License Manager is responsible. The License Manager handles validity dates of term licenses and in case of validity time comes to the end, user is informed with several levels of alarms which are shown in the NetAct Monitor application. First level of alarms is a minor alarm. The minor alarm is raised 30 to 90 days before Right To Use (RTU) period ends. Number of days is configurable and can be set in the License Manager application (see Setting global notifications section in the License Manager Help document). Second alarm level is a major alarm, raised 7 days before RTU expiration. The last level of alarms is a critical alarm level. There are two different critical alarms, raised on the date of RTU expiration, and on the date of license key validity expiration. On each alarm level new license can be ordered and installed what is necessary to clear all existing alarms and further use of the NetAct system. For more information about NetAct hard lock functionality, see NetAct hard lock in previous section in this document.

Version 1


22 (138)


NetAct 8 SW Licensing NetAct capacity Standard SW The Majority of NetAct Sales Features is sold per managed network size.

For the Radio network, NetAct doesn’t allow to manage bigger network size (cells/TRXs) than the capacity of the relevant NetAct Standard SW license Key

• The volume is protected by capacity limit in NetAct Standard SW license keys

Running out of License Key capacity is notified by alarms and emails.

• In case limit is exceeded, the capacity hard lock is activated : there would be no valid license key in NetAct for that Standard Software

1

• Notifications sent for 80% and 90% of capacity


Fig. 11

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version 1 . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . © Nokia Solutions and Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 (138) . . . . . .


NetAct 8 SW Licensing NetAct capacity Standard SW Order additional LK capacity +500 cells

LK initial capacity (e.g. 1000 cells) Hard lock

SWAM usage reports

Deal size

Purchase order

RTU limit in LK

Alarming starts

Installation

1000 cells

Network expansion project

New RTU limit in LK

NetAct lifetime

1500 cells

• NetAct Standard SW capacity License Keys (LK) certifies Right To Use (RTU) limit. • NetAct SW Asset Monitoring provides Standard SW feature usage report (in pricing unit like Cells, TRXs). • Notifications for approaching the LK capacity limit. • NetAct refuses to add any new element above the capacity in LK. • Order for additional NetAct capacity if managed Radio network has to be bigger. • Hard lock impacts only NetAct. Network Elements are not impacted. 1


Fig. 12

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 . (138) . . . . . . .


1.8

Licenses for OEM Software

NetAct 8 SW Licensing OEM SW licenses The majority of the OEM SW components is licensed per NetAct system: 1 cluster license per 1 NetAct. OEM SW with NetAct Cluster pricing

OEM SW not following the cluster pricing

Protection relays on NetAct’s Standard SW features license keys:

• VMWare, Citrix, Microsoft • The OEM vendor specific technical licenses in use.

• a customer order per NetAct Cluster is always needed for generation and NSN License Key delivery • NetAct Target ID database is kept and checked at the commissioning, upgrades, and care processes. • Purchase Order, License Key delivery reports provides track record about NetAct installed base.

1


Fig. 13

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia . . Solutions . . . and . Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 25 . . . . . .


Version 1


26 (138)

Software Asset Protection

2

Version 1



27 (138)


2.1

Managing License Keys vs. Software Asset Monitoring

The new License Management Model in NetAct 8 is splitted in two areas: the traditional management of license keys with the License Management Application and the Monitoring of the usage of features for invoicing accordingly as an alternative for the payment of a fixed license. NetAct License Manager provides centralized solution for managing network element licenses. However in NetAct 8 the functionality of License Manager has been extended as well to manage NetAct applications licenses. All license key management operations can be performed using License Manager Software Asset Monitoring application collects and processes the configuration and measurement data based on customer specific settings. It generates a report on the feature usage and forwards the formatted monitoring data to the customer and NSN Customer Team via an encrypted e-mail. The encrypted e-mail can be read and validated by Customer and NSN Customer Team only. The report on the feature usage is used to generate an invoice. One software monitoring report comprises information related to one NetAct cluster. Software Asset Monitoring enables speed and efficiency with fast software activations through bypassing the pre-activation procurement process, and applying alternative pricing models where invoicing is based on network configuration or on used functionality. This results in OPEX savings and in an increased flexibility.

Version 1


28 (138)


NetAct 8 SW Asset Protection License Management Concept

Management of License Keys: NetAct License Manager

SW Monitoring: NetAct SW Asset Monitoring

• Central tool for managing: • Network Elements License Keys (LKs) • NetAct’s License Keys. • Moderately renewed License Manager application with better usability compared with OSS5 License Manager. • Automatic license distribution, auditing features against templates and network level view of licensed features.

• Monitoring based Network Elements features usage reports • Alternative pricing models enabled. Less effort on NE LK management • Mandatory for LTE • NetAct integrated tool

1


Fig. 14

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version 1 . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 (138) . . . . . .


NetAct 8 SW Asset Protection When to Choose Software Asset Monitoring Software Asset Monitoring (SWAM) + Minimized license key related

License Keys + Customers familiar with approach and processes - license key logistics can delay feature activation and capacity increases

network bottlenecks

+ Operator has automatic visibility

- effort for license key handling: training, planning, taking delivery, distribution to network elements

on capacity and feature rollout in the network

+ no hardware replacement impact + fast capacity increase where

- effort of license key handling in case of hardware replacement or modernization - lack of flexibility to react fast to needed changes in the network

needed

+ SWAM client is free

- Some licenses can be activated beyond the agreed limits, e.g. RNC on/off licenses

- Currently only available for LTE, WCDMA, GSM, Flexi-NG

still available on GSM and WCDMA radio

Mandatory for LTE

not an option for LTE

Recommended for GSM, 3G, Flexi NG

1


Fig. 15

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia . . Solutions . . . and . Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 30 . . . . . .


2.2

Software Asset Monitoring

Monitoring data are configuration management (CM) parameters and performance management (PM) counters. Software Asset Monitoring application stores the data for further handling such as pre-processing to make raw monitoring data more accurate and usable, for example, data size is reduced and data are presented in more convenient way to the user. Local storing of data is needed before and after data processing. A report is periodically generated based on monitoring data and sent to NSN side where later on it is used for invoicing purposes. The Monitoring modules are product specific elements, which allow an incorporation of specific reporting methods. Monitoring modules are divided into two groups, PM and CM, particular for each network technology.

Version 1


31 (138)


NetAct 8 SW Asset Protection Monitoring as the alternative for license key management

NetAct 8 CM, PM database

NSN SWAM Client

Operator

• Software Asset monitoring via SWAM client as an alternative for license key management. • Supported use models: • Pay as you grow • Pay as you configure • Pay as you use

1


Fig. 16

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 . (138) . . . . . . .


2.2.1

Software Asset Monitoring functionalities

Aggregation, non-aggregation approach Software monitoring considers aggregation and non-aggregation approach. Aggregation means that the network element functionality can be used for any network element in NetAct cluster. Non-aggregation means that the functionality is assigned to a specific network element just as the conventional license management works. Aggregation and nonaggregation functionality is available for both, PM based and CM based software monitoring, and has an impact on feature delta usage figures accordingly. Note: By default, non-aggregation approach should be selected, as in standard pricing models, licenses are tied to the network elements. The following aggregation, non-aggregation options are available for dedicated radio network technology:  Aggregation off (GSM PM, FlexiNG, FlexiNS, WCDMA, LTE, RACS)  Aggregation on NetAct Cluster level (GSM, FlexiNG, FlexiNS, WCDMA, LTE, RACS)  Aggregation on RNC level (WCDMA)  Aggregation on BSC level (GSM)  Aggregation on Site level (WCDMA PM, LTE PM) Further in this section there are examples explaining aggregation and non-aggregation options. Pricingmodel examples for aggregation off, aggregation on NetAct Cluster level, aggregation on RNC leveland aggregation on Site level are Cell based.

Usage of Nth highest value This functionality allows you to choose which value in the monitoring data should be considered as the peak value used for invoicing purposes. When creating a periodic detailed report, for each element a max function is used for getting maximum value for a day. In case of periodic aggregated report, Nth highest value is taken into consideration to get a maximum value for an invoicing period. By default, Nth highest value is set to 1, which means, that the maximum value is considered as the highest value. When set to other value, for example 3, SWAM will skip first two values and will take the third one as the peak value for the invoicing period for particular feature (in CM module) or counter (in PM module). This peak value is then used to form the delta value, and the delta value is taken into consideration when an invoice is created.

Version 1


33 (138)


NetAct 8 SW Asset Protection Monitoring as the alternative for license key management NetAct 8

NSN

CM, PM data

SWAM Client

Operator

Supported elements: • LTE 2G / 3G / LTE Radio

• RACS • WCDMA • Flexi Direct BTS • GSM • Flexi NS MME • Flexi NG

Packet Core

1


Fig. 17

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 . (138) . . . . . . .

Managing License Keys

3

Version 1



35 (138)


3.1

License Management Overview

Licenses are used to enable new features or functionality. For example, you may need new licenses when you want to upgrade software or hardware, activate new services, add capacity or optimize or expand the network. Licenses are ordered from Nokia Siemens Networks as any other functionality. You must then distribute the license to the network elements in order to make the feature or functionality available in the network. License A license is an agreement from the owner of a product that gives permission to use or produce the product according to the agreed conditions. The information that enables the use of licensed software is called a license key. Nokia Siemens Networks implements license keys as Nokia Siemens Networks-specific license files. Each license file gives the permission to use one or several features or functionalities in the specified network elements. A license file contains the information to which network element the license is targeted. This is done by using each network element's unique identifier which is called a target identifier. There are two types of licenses: on/off and capacity licenses. NE licenses are installed to network elements either using the License Manager application or element managers.

Version 1


36 (138)


Managing License Keys Overview (1) Licenses are generated and sent via NOLS or e-mail

(2) License files are Imported to NetAct via License Manager Application  Import from the user’s terminal or workstation E.g. D1681105.XML The users can get reports on the license status of the NEs

NetAct Regional Cluster LIC_% Licenses Directory

The License status can be synchronized between the Network Element and NetAct

(3) Licenses are distributed to Network Elements HLR MSC

SGSN

WCDMA

GSM

I-HSPA LTE

1


Fig. 18

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 37 . . . . . .


3.2

License Manager

License Manager is a centralized tool for managing hardware and software licenses in the NetAct system. License Manager provides support for performing basic management operations on licenses such as import, distribution, synchronization, feature state change, and deletion. License Manager contains an easy-to-use graphical user interface to perform managing operations, and also a command line interface. The tool provides customized reports which, using license states, give detailed information about the license situation License Manager enables managing of licenses for features in all Nokia Siemens Networks’ network elements using MML or NWI3 mediations. Following operations are available for licensing features:

               

Importing license files to NetAct Downloading NE licenses Distributing pool licenses Browsing installed software licenses Revoking imported licenses from the NetAct Database Browsing network topology Deleting licenses from network elements Changing feature states of network elements Uploading license status Substituting pool licenses Generating reports and exporting report data to the CSV files Managing license labels Setting feature templates and guided distributing Monitoring the status of ongoing operations Scheduling license management tasks License expiration handling

TIP To get information about the License Manager software version, click

Version 1


button.

38 (138)


Managing License Keys License Manager

License Manager provides a centralized tool for managing network element licenses through the whole lifecycle of the network at a single place with clear, user-friendly interface. 1


Fig. 19

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 39 . . . . . .


3.2.1

License Manager Functionalities

License Manager application contains table footers in each table in the following views: Import license, License Key Browser, Topology, Pool Substitution, Reports, Recent operations, Scheduling, Feature Templates. It helps you to browse items in the table, if the number of items is large. If the number of items is greater than number of items displayed in the table, you can navigate between pages, using navigator pane situated in the middle of the table footer. On the left side of the table footer there is indication of the total number of items and the number of checked items. You can change the number of items displayed in the table per page, using drop-down menu situated on the right side of the table footer. License Manager application can be open simultaneously in a few tabs of web browser, but only one tab will be enabled for all operations. In the other tabs you can perform only operations, for which Cluster ID is not required.

TIP Only Recent operations view can be open in the other tab of a web browser parallel with other views. WARNING During navigating the License Manager application, do not use back and forward buttons in the web browser.

Version 1


40 (138)


Managing License Keys License Manager Features

     

NetAct software license keys management Network Elements license keys management Pool license keys management Automatic license distribution Auditing Network Elements against features template Notifications for license key expiration, running out of feature capacity  Operations history  Reporting for NetAct as well as Network Elements licensed features

1


Fig. 20

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 . (138) . . . . . . .


3.3

Licensing Concepts: NE Licensing

Network element license management allows you to control the network element feature licenses from a centralized location, taking into account the number of network elements in the network and variety of licensed features within one network element. The NE licenses are issued for specific target ID. The network elements to which you will use the license should be known in advance. Once the license is issued for the specific target, it is not valid for other ones. NE licenses are installed to network elements using either the License Manager application or element managers. Network elements license concept is supported for AXC, BSC, CDS, FLEXINS, HLR, MGW, MSC, RNC, SGSN, WBTS network elements. The figure below illustrates the network element license concept:

Version 1


42 (138)


Managing License Keys Licensing Concepts: NE Licensing Network elements license concept is supported for AXC, BSC, CDS, FLEXINS, HLR, MGW, MSC, RNC, SGSN, WBTS

NE licenses are installed to network elements using either the License Manager application or element managers.

1


Fig. 21

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 . (138) . . . . . . .


3.4

Licensing Concepts: Pool License

Pool licenses contain license information for a large number of network elements of the same type. They are used for AXCs, WCDMA BTSs, and Flexi Direct BTSs. Pool licenses are specific to one NetAct cluster and they contain the NetAct Target ID of the NetAct cluster to which the pool license file is designated. They also contain the size of the pool, which is interpreted differently for on/off licenses and capacity licenses. • For on/off licenses, the size of the pool defines the number of network elements, which are permitted to use the functionality. This means that you can create licenses for that number of network elements. • For capacity licenses, the size of the pool represents the total amount of capacity, which can be divided between the network elements. This means that you can generate licenses with different amounts of capacity for several network elements as long as there is capacity left in the pool. In order to take the license into use in the network elements, a license file needs to be generated for the network elements from the pool license. The generated file is called an NMS generated license file and it contains the target identifiers of the network elements. Generating a license from the pool license decreases the amount of free capacity in the pool. The figure below illustrates the pool license concept.

Version 1


44 (138)


Managing License Keys Licensing Concepts: License Pools Pool licenses are used for AXCs, WCDMA BTSs, and Flexi Direct BTSs.

For on/off licenses, the size of the pool defines the number of network elements, which are permitted to use the functionality. For capacity licenses, the size of the pool represents the total amount of capacity, which can be divided between the network elements.

1

Users can generate licenses with different amounts of capacity for several network elements as long as there is capacity left in the pool.


Fig. 22

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 45 . . . . . .


3.5

Licensing Concepts: License Sets

License sets functionality allows to divide pool licenses into groups and then assign them, by means of license set, to chosen Maintenance Region (MR). This concept is useful for managing licenses in more effective way and gives flexibility of managing pool license consumption. License set is an advanced configuration, which enable turning feature on/off during automated license distribution by allocating pool licenses to be consumed by network elements running in dedicated maintenance regions. When license belongs to a license set which is assigned to some maintenance region, it can be used in automatic license distribution only if requested network element also belongs to this maintenance region. In other words, network element can request only for licenses assigned to the same maintenance region. When network element sends a request to generate a license for some feature, License Manager checks to which maintenance region belongs this network element and uses only licenses from a pool assigned to this maintenance region. A license cannot be assigned twice, if license is assigned to one license set, it cannot be used again.

Version 1


46 (138)


Managing License Keys Licensing Concepts: License Sets

• Flexible configuration of Pool license consumption in automatic license distribution. • Assign License sets to work for maintenance regions. • Handle multiple Pool licenses together as License sets. 1


Fig. 23

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 47 . . . . . .


3.5.1

Licensing Concepts: NetAct SW Licenses

NetAct applications license management allows you to control the NetAct software features. NetAct software licenses are meant to activate particular NetAct application functionalities, for example, Table Editor in CM Editor or applications supported for a particular network technology, for example, CM Editor for 2G, CM Editor for 3G. To enable the NetAct licensed functionalities/features it is necessary to install the NetAct 8 Level SW license key, which is mandatorily required in order to let any other license keys be valid. For more information about NetAct 8 Level SW license key, see NetAct Release Upgrade protection in the NetAct Software Licensing document. Software licenses contain target identifiers for NetAct systems. Software licenses are installed in a proper target system using the License Manager application. In the software license concept, License Manager application performs a three-fold check: • verifies whether the NetAct System contains NetAct Release Upgrade license key. • verifies whether an appropriate application contains a licensed feature. • verifies whether the license to this particular feature is installed in the License Manager application License statuses define all possibilities after license check. The figure below illustrates the software license concept.

Version 1


48 (138)


Managing License Keys Licensing Concepts: NetAct SW Licenses NetAct SW licenses are used to activate particular NetAct applic. functionalities, for example, Table Editor in CM Editor or applications supported for a particular network technology, for example, CM Editor for 2G, CM Editor for 3G

1


Fig. 24

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 49 . . . . . .


3.6

License States 3.6.1

Network Elements and OSS Generated Licenses (NMS licenses)

License State

Description

Distributed

The license is distributed to its network element

Not Distributed

The license file has not been distributed to the network element which is in the target identifier list of license file.

Deleted

The license file which was previously distributed to its network element, has been removed from this network element.

Expired

The license validity period has ended or the license signature certificate has expired

Expired still in NE

The license file has been distributed to the network element, but the validity period of license has ended or the license signature certificate has expired.

Not Integrated

The network element is not integrated to NetAct anymore.

Conflicting

The license file in the NetAct repository, and the license file in the NE have different content. For NE licenses the correct license version should be identified. In case the correct version is present in the NE, it should be reimported to NetAct. For NMS licenses, the license should be deleted from the NE. In case the capacity is needed on the NE, new capacity should be distributed from valid pool license.

Invalid

The license file exists in the network element, but it is not used by the network element because the network element does not accept it or xml file has been corrupted.

Version 1


50 (138)


3.6.2

Pool and SW Licenses

License State

Description

Valid

The license file has been accepted by the License Manager application, which means the license xml file and signature are correct.

Expired

The license validity period has ended or the license signature certificate has expired

Invalid

The xml file has been corrupted or the license file has signature, signed with a test certificate, which is not accepted.

Version 1


51 (138)


3.7

License Management Tasks 3.7.1

License Import

Import operation view of the License Manager Web UI makes it possible to introduce a license into the management system in a very easy way. Imported licenses can be totally new, or new versions of already existing licenses in the NetAct. Individual licenses or .zip archives of multiple licenses can be imported from any available folder. To import licenses to NetAct

1. In the main menu click License and select Import License from the drop-down menu. 2. Click the Upload button and browse the folder where the license files are stored. After you choose the file, the upload operation starts and progress bar appears. The License files table is refreshed and shows uploaded licenses. If any license is already imported, it contains information about date of previous import in Last imported column and label, if it was assigned before to this license. If the uploaded license expired or is faulty, it does not contain check box and cannot be imported. Status column in the table provides detailed information about license failure. To remove licenses from the table click the Clear button. Note: You can upload license file in the XML format or you can upload multiple, archived licenses in the following formats: zip, tgz, tar.gz.

TIP You can check the detailed information about the license by clicking on the license file name. 3. Attaching a label to the license file. You can attach the label to the uploaded license files for an easier identification. You must create a label, before it is attached to the license file. To create a new label and attach it to a license(s), check the license(s), click the Labels button and select Create new. Type or paste new label into text field and click Ok. To assign existing label to the license file, check the license(s), click the Labels button and select an appropriate label from the list. To remove label from the license, click the Labels button and select Remove current from the list.

4. Select licenses you want to import and click the Import button. If you do not have LIC_ImportPermission, Import button is disabled. To see the import operation details, follow the link into notification. The Recent Operations view appears with the latest operation highlighted. In the table below there are listed certain tasks of selected request. Successfully imported licenses are available in the License Key Browser view.

Version 1


52 (138)


License Manager License Import

• Licenses should be uploaded first to the server • Single license file or multiple licenses in .zip archive can be uploaded • When the license content is displayed, license can be imported to the license repository • Label can be set to any valid license 1


Fig. 25

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version 1 . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 (138) . . . . . . . .


3.7.2

Viewing Licenses

You can browse all types of licenses using the License Key Browser view. You can also download NE licenses to network elements and distribute pool licenses.

1. In the main menu click License and select License Key Browser from the drop-down menu. License Key Browser view appears. You can choose a type of displayed licenses by selecting appropriate tab in the License Key Browser view. If you highlight a license by clicking on it, second table appears below with information about the license target. You can also click license file name to get the detailed information about the license.

2. You can filter licenses displayed in the table. To filter licenses, click the

button. The Filter dialog appears. In order to browse the installed license easier, you can filter out the irrelevant entries. Filter settings are memorized for each tab. Licenses in the following views: NetAct Software Licenses, NE Licenses, Pool Licenses are filtered by license type and this criterion cannot be removed from the filtering criteria. You can filter which licenses are shown, according to the following criteria: Target type, Feature Code, Feature Name, Label, License code, License name, License file, Serial number, Target ID. a) Select a criterion from Filter by: drop-down menu. You can select multiple criteria by clicking the Add criterion icon. To remove filtering criterion, click the Remove criterion icon. You can merge the filtering criteria using (OR) and (AND) operators. Operator (OR) means that in the License keys table all licenses are shown which fulfill first or second criterion. If you select (AND) operator, in the License keys table only, the licenses which fulfill both criteria will be shown. b) You can define by checking the check boxes, if expired licenses and downloaded to their all or filtered targets licenses in case of NE licenses, or empty pool (capacity equals zero) in case of pool licenses, are shown in the License Keys table.

c) Click the Ok button to filter licenses in the License keys table according to the selected criteria. The License keys table displays licenses according to selected criteria, which are listed above the table.

TIP To clear filtering criteria, click the

button.

TIP If you checked an expired or empty pool (remaining capacity equals zero) check boxes, Clear filter button does not clear this choice. If you want to uncheck them, you must do it manually. To refresh the License keys view, click the

Version 1


button.

54 (138)


TIP You can check the license detailed information by clicking the license file name. Edit the label of the license files. You can remove the existing license label or change it. You can also add a new one if the label does not exist. NMS generated licenses have the same label as the pool license, it was generated from. To add a label, check the license(s) and click the Labels button. Then select Create new button and type or paste new label into a text field and click Ok. To assign an existing label to the license file, check the license(s), click the Labels button and select appropriate label from the list.

TIP To remove label from the license, click the Labels button and select Remove current. Exporting License Files You can also export license files to the local workstation by clicking the Export button. For more information on how to export license file see Exporting license files.

Version 1


55 (138)


Managing License Keys Viewing Imported Licenses and Licenses details

1


Fig. 26

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version 1 . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia . . Solutions . . . and . Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 56 . . . . . . . .


3.7.3

Uploading Licenses

The purpose of upload license status operation is to synchronize the latest license and feature information from the network elements with the NetAct database and to keep License Manager up-to-date. Synchronization is performed by uploading the status of all licenses from the selected network elements. In case there are licenses on network elements which are not present in the NetAct database, they are uploaded and added to the NetAct database. You can schedule license information synchronization for desired network elements of particular type.

Version 1


57 (138)


Managing License Keys Uploading Licenses

1


Fig. 27

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia . . Solutions . . . and . Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 58 . . . . . . . .


Managing License Keys Uploading Licenses: Scheduling

Schedule upload status for all or selected network elements of given type in simple steps. 1


Fig. 28

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 . (138) . . . . . . .


3.7.4

Exporting Licenses

Exporting license is an operation which allows you to download license file to your local drive. You can download one license as a .xml file or multiple licenses as a .zip archive.

License Manager License Import

• Licenses should be uploaded first to the server • Single license file or multiple licenses in .zip archive can be uploaded • When the license content is displayed, license can be imported to the license repository • Label can be set to any valid license 1


Fig. 29

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia . . Solutions . . . and . Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 . (138) . . . . . . .


3.7.5

Distributing Licenses

Distributing license files entails downloading the selected licenses to the designated network elements. Features can then be taken into use according to the feature activation instructions. There are following distribution options: • NE license distribution is used to distribute NE licenses, and to redistribute NMS generated licenses. • Pool license distribution is used to create and distribute NMS generated licenses.

3.7.5.1

Distributing NE licenses

NE license distribution involves downloading licenses to network elements in one or multiple operation. NetAct users can download an NE license, or an NMS generated license to all integrated network elements mentioned in the license file as a single operation. Download can be executed in several operations so that only some of the network elements are selected at a time. If new targets have been added to the license, the download operation is needed only for the added target network elements.

Version 1


61 (138)


Managing License Keys License Distribution: Distributing NE licenses

• See Network Elements license keys with their target elements and distribution status.

• Download one or multiple licenses for target elements. • Use advance filtering to drill down for needed information. 1


Fig. 30

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version 1 . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 (138) . . . . . . . .


3.7.5.2

Distributing Licenses from a Pool

Distributing licenses from a pool functionality enables multiple pool license distribution to multiple network elements in one operation. When a license from a pool is distributed, network element specific licenses (NMS generated licenses) are created by the License Manager application. NMS generated licenses are then automatically distributed to the network elements. During capacity feature distribution, the user defines the amount of capacity for each element.

Version 1


63 (138)


Managing License Keys License Distribution: Distributing Pool licenses

• See Pool licenses with their consumption by target elements. • Distribute one or multiple licenses for target elements. • Use advance filtering to drill down for needed information. 1


Fig. 31

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version 1 . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 (138) . . . . . . . .


Managing License Keys License Distribution: Distributing Pool licenses

• Use wizard for Pool distribution of multiple features to multiple network elements. • Have the full control for licenses and capacity to be distributed. • Be warned when distribution exceeds max HW capacity of the element. 1


Fig. 32

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 65 . . . . . .


3.7.5.3

Distributing Licenses Using Guided Distribution

Guided distribution allows you to distribute multiple licenses, based on a feature template, to one or multiple network elements. During guided distribution operation, license situation on network element is compared to the one in the feature template and capacity needed for distribution is calculated and then sent to the network element. Needed capacity is summarized from remaining capacity of different pools. This functionality assures that network elements will reach feature template definition.

Version 1


66 (138)


Managing License Keys License Distribution: Guided Distribution

• Distribute license keys according to feature template in one operation. • Let License Manager calculate capacity to be distributed to avoid unnecessary LK generation.

• Have overview of capacity consumed by guided distribution. 1


Fig. 33

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 67 . . . . . .


3.7.5.4

Automatic Licenses Distribution

Automatic license distribution functionality allows to distribute licenses to network elements without manual operations and based on a certain configuration. Mechanism of automatic license distribution provides that licenses automatically follow network configuration. Automatic license distribution is based on network element request. NE request is sent to a NetAct system in case network element needs new license or capacity. Needed licenses are generated out of available pool and sent to the network element automatically. For capacity licenses available pool is summarized from remaining capacity of different pools. Deleted licenses can also be concerned as the available pool and distributed automatically, provided that proper configuration for automatic license distribution is set. Available pool can be defined by license sets functionality. During automatic license distribution you can limit a pool of licenses which can be distributed, by assigning license set to desired maintenance region.

Version 1


68 (138)


Managing License Keys License Distribution: Automatic license key distribution Flexi BTS requests license key distribution after configuration changes

License Manager automatically distributes licenses with requested capacity from a pool of licenses.

NetAct Configurator

Floating licenses supported.

NetAct License Manager

WCDMA BTS 1


Fig. 34

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 69 . . . . . .


Managing License Keys License Distribution: Automatic license key distribution

• Configure features for which licenses will be automatically distributed. • Network elements send generation request for licenses they need. • Licenses are automatically generated and distributed out of pool licenses. 1


Fig. 35

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version 1 . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 (138) . . . . . . . .


3.7.6

Feature Templates

Creating feature template is an operation which allows you to define a set of features and their capacity desired on a network element. Feature template concept is used in guided distribution operation and during auditing network elements. A template can be defined based on existing network element and as a custom template by selecting features from these available in a pool licenses.

Note: If you generate a template from an existing network element, only the distributed licenses are taken into consideration. All features and their capacity values, which are distributed to a network element, are going to be included in the template. If multiple licenses per feature exist in the network element, they will be represented in the template as a single entry for the feature with capacity value which is equal to the sum of all licenses for the feature. By defining a label in a template, you can narrow down the pool licenses which will be used in the guided distribution.

Version 1


71 (138)


Managing License Keys Feature Templates

• Create feature template to be used as the pattern for distribution. • Use feature template for auditing Network Elements. • Apply template to elements by starting guided distribution. 1


Fig. 36

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version 1 . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 (138) . . . . . . . .


Managing License Keys Feature Templates

• Select features for template based on network element or define from available licenses.

• Use labels for automated license keys selection in guided distribution. 1


Fig. 37

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 . (138) . . . . . . .


3.7.7

Network Element Audit against Feature Template

License Manager offers possibility to audit network elements against previously defined feature templates. This functionality compares the licensed features status of the network element with the one defined in a feature template and check if the network elements have sufficient licenses distributed. This option allows user to see if network element status is insufficient, equal or exceeding against to the feature template and to start guided distribution to all network elements having too less licenses.

Version 1


74 (138)


Managing License Keys Network Element Audit against Feature Template

• Audit Network Elements if they have sufficient license for defined features template • Perform Network Element specific or network wide auditing in UI or in report form 1


Fig. 38

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 75 . . . . . .


3.7.8

License Pool Substitution

The pool license substitute process allows you to replace a pool license in case you selected a wrong target in pool license distribution or in case of broken hardware. License pool substitution process consist of three phases, registering licenses for pool substitution, exporting license pool substitution request, and importing license pool substitute permission. If you have selected a wrong target in pool license distribution, the only way to revert the allocation is by applying the pool license substitute process. The incorrect license capacity is released back to the pool. By default the substitution process delete the substituted licenses from the network element.

Version 1


76 (138)


Managing License Keys License Pool Substitution

• Create Pool substitution requests for broken HW and typing error cases. • Register substitution request for multiple network elements and multiple licenses.

• Have full overview of pending substitution requests. • Create report for all Pool substitution requests for any further processing. 1


Fig. 39

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 (138) . . . . . . .


3.7.9

Licenses Reports

You can generate the following reports via the license Manager graphical user interface:

         

Report on NetAct software features Report on operations history Report on license files of network elements Report on license substitutions Report on network element license files of given state Report on licensed features of network elements Report on remaining capacity in pool licenses Report on comparison of templates to network element Report on comparison of templates to network element on feature level Report on NetAct software features

The following information is available in this report: Area, Feature name, Feature code, Feature description, Sales item, Network Technology, License state, Capacity, Expiration date. For all reports you can generate via graphical user interface, data export to a CSV files is available.

Version 1


78 (138)


License Manager Licenses Reports

1


Fig. 40

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 79 . . . . . .


License Manager Feature Reports

• • • •

See on the report all possible NetAct licensed features with their licensing status. Create report for all or one NetAct application area. View licensed features for particular Radio or Core network technology. Export report to CSV file for any further processing.

1


Fig. 41

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia . . Solutions . . . and . Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 80 . . . . . .


3.8

License Notifications

License notifications functionality provides information for user about all licenses which are going to expire as well as about exceeding pool licenses or features capacity. Expiration notifications apply to all types of licenses, NetAct software licenses, pool licenses and NE licenses. Exceeding license/feature capacity notifications pertain only to pool licenses. Two ways of warning user are supported by License Manager, notifications visible in application as a pop up messages, and e-mail notifications. When licenses validity date comes to the end or pool license or feature usage crosses capacity threshold, an expiration dialog appears in the License Manager application right after opening the application. In addition all notifications are listed in License Manager application separately for expiring licenses, features running out of capacity and licenses running out of capacity.. All notifications are configurable. For pool licenses and features running out of capacity, thresholds settings for consumed level of license or feature capacity can be defined globally for all and also for particular pool license or feature. For licenses whose validity date comes to the end configuration can be set only globally and number of days before expiration can be defined. You are also allowed to choose if you want to receive e-mail notifications or not. License Manager supports also alarms for NetAct software licenses related to NetAct hard lock protection for term licenses. For more information about NetAct software licenses alarms, see NetAct alarms in the NetAct Software Licensing document.

Version 1


81 (138)


Managing License Keys License Notifications

• Define notification capacity thresholds on feature or pool license level. • Configure notification for license expiration. • Be notified in License Manage UI or via e-mail. 1


Fig. 42

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 . (138) . . . . . . .


3.9

Viewing Recent Operations

Recent operation functionality shows history of operations performed in the License Manager application and provides an overview of all operations performed by the user, system or network element. You are able to see detailed information about recently executed operations, ongoing or finished, with their status of completion. Overview of the following operations is available: Delete from network, Download, Feature state change, Guided distribution, Import, License generation request, License state change, Pool distribution, Substitution, Synchronization request, Target Id verification, Terminate and Upload status.

Version 1


83 (138)


Managing License Keys Viewing Recent Operations

• See all licensing operations happening in NetAct cluster. • Use filtering and searching to find needed information quickly. • Repeat failed license operation right from recent operation view. 1


Fig. 43

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 . (138) . . . . . . .


4

Version 1



85 (138)


4.1

Software Asset Monitoring Application

Software Asset Monitoring application collects and processes the configuration and measurement data based on customer specific settings. It generates a report on the feature usage and forwards the formatted monitoring data to the customer and NSN Customer Team via an encrypted e-mail. The encrypted e-mail can be read and validated by Customer and NSN Customer Team only. The report on the feature usage is used to generate an invoice. One software monitoring report comprises information related to one NetAct cluster. NetAct Software Asset Monitoring (SWAM) is a web-based application for software asset monitoring purposes. SWAM provides the following operations: • Creating, modifying and deleting monitoring modules for particular network technology • Viewing and exporting monitoring reports • Setting the preferable invoicing period (monthly or quarterly) • Setting notifications and alarms thresholds • Migrating data Note: Access to the operations performed in Software Asset Monitoring requires special permissions. To check which permission you need to perform each operation, check Permission Management Help.

Version 1


86 (138)


SW Asset Monitoring

SWAM is enhanced to protect capacity NetAct Radio Standard SW features. • Features usage reports in terms of network size managed in NetAct 8 cluster: •Number of Cells •Number of TRXs

Capacity usage monitoring for: • • • • • •

1

NetAct Radio GSM Standard SW NetAct Radio GSM-R Standard SW NetAct Radio WCDMA Standard SW NetAct Radio LTE Standard SW Flexi NG Flexi NS


Fig. 44

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 (138) . . . . . . .


4.2

Monitoring Modules

Monitoring data are configuration management (CM) parameters and performance management (PM) counters. Software Asset Monitoring application stores the data for further handling such as pre-processing to make raw monitoring data more accurate and usable, for example, data size is reduced, and data are presented in more convenient way to the user. Local storing of data is needed before and after data processing. A report is periodically generated based on monitoring data and sent to NSN side where later on it is used for invoicing purposes. Monitoring modules are product specific elements, which allow an incorporation of specific reporting methods. Monitoring modules are divided into two groups, PM and CM, particular for each network technology. The table in next page shows the monitoring modules currently available.

Version 1


88 (138)


SW Asset Monitoring Monitoring Modules

Monitoring data are configuration management parameters and performance management counters. SWAM stores the data for further handling. A report is periodically generated based on monitoring data and sent to NSN side where later on it is used for invoicing purposes. Monitoring modules are product specific elements, which allow an incorporation of specific reporting methods. Monitoring modules are divided into two groups, PM and CM, particular for each network technology.

1


Fig. 45

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (138) . 89 . . . . . .


4.3

Monitoring Modules Types

Monitoring Module

Description

NetAct Radio

Monitors configuration management parameters. Note:NetAct Radio monitoring module is default permanent module which is not configurable

LTE FDD

CM Monitors LTE FDD configuration management parameters

LTE TDD CM

Monitors LTE TDD configuration management parameters.

LTE FZ FDD CM

Monitors LTE Flexi Zone FDD configuration management parameters.

WCDMA CM

Monitors WCDMA configuration management parameters.

GSM CM

Monitors GSM configuration management parameters.

RACS CM

Monitors configuration management parameters from the Radio Applications Cloud Servers.

LTE FDD PM

Monitors LTE FDD counters.

LTE TDD PM

Monitors LTE TDD counters.

WCDMA PM

Monitors WCDMA counters.

GSM PM

Monitors GSM counters.

FlexiNG PM

Monitors FlexiNG counters.

FlexiNS PM

Monitors FlexiNS counters.

Version 1


90 (138)


4.4

Software Asset Monitoring Notifications

Software Asset Monitoring supports e-mail notifications and provides information for user about generating reports, as well as warns user about misusing application and crossing capacity thresholds for features. E-mail notifications are sent right after report generation in case one of the following events occurs • summary report (monthly or quarterly) has been generated. • unauthorized modifications have been made to monitoring data or in formerly generated report • feature threshold value, set during module creation, has been exceeded For more information about notifications for exceeding thresholds, see Warning e-mails for crossing thresholds. Notifications are configurable globally, as well as for particular feature during module creation. Software Asset Monitoring supports also alarms for NetAct software capacity licenses related to NetAct hard lock protection for capacity licenses. For more information on NetAct software licenses alarms, see NetAct alarms in the NetAct Software Licensing document.

Version 1


91 (138)


SW Asset Monitoring Notifications SWAM supports e-mail notifications and provides information for the user about generating reports, as well as warns user about misusing application and crossing capacity thresholds for features

SWAM monitors and reports used capacity of NetAct software licenses and in case capacity thresholds are crossed, respective alarm is raised and visible in the NetAct Monitor application (Hard Lock Functionality)

1


Fig. 46

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 . (138) . . . . . . .


4.5

Software Asset Monitoring Reports

The purpose of Software Asset Monitoring is to monitor and report features usage. As a result of this a monitoring report is created. Software Asset Monitoring application allows to view reports, download reports as CSV or XML file, and backup a report in form of raw monitoring data. Software Asset Monitoring application creates following types of reports for CM and PM based monitoring:









Daily report: Contains information about daily change of features/counters usage. In case of CM based monitoring it contains feature parameters collected and reported once a day. In case of PM based monitoring it contains information on counters which have been collected during a day and counters values are reported for every hour. Periodic detailed report: Contains information on features/counters usage for each day of the whole invoicing period. In case of CM based monitoring it assembles features/counters daily values. In case of PM based monitoring it shows results with aggregation approach applied. Reporting results are listed for each network element. Periodic aggregated report: Periodic aggregated report shows aggregated features/counters values for the invoicing period by applying the logic as defined by SWAM parameters. Results are listed for each network element. Summary report: Summary report contains summary values for each feature/counter that is applied for invoicing during the invoicing period for the dedicated NetAct Cluster. In summary reports every Sales Item is listed only once as a basis for invoicing.

Version 1


93 (138)


SW Asset Monitoring Monitoring Reports

1


Fig. 47

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 . (138) . . . . . . .


Next tables show the rows and the columns which can be visible in every Software Asset Monitoring report.

Row Name

Description

Comment

Module name

Module name which is the same module name that is created during module creation.

Module type

Represents technology for which report was created and indicates what type of report it is, CM (configuration management) or PM (performance management), for example: LTE FDD CM, WCDMA PM.

Day/Period

It shows for what time report was created. In case of daily reports there is a Day row, which shows the exact day for which report was created. In case of periodic reports there is a Period row, which shows the period of time for which report was created.

Aggregation

This row informs about type of aggregation which has been used to create a report. Available options are Off, NetAct Cluster, RNC, BSC, Site.

Pricing model

Type of pricing model which has been used to create a report.

For CM reports

Nth highest value

Number of Nth highest value used for calculation.

For Periodic detailedreport

Sum up Channel Elements uplink/downlink

It shows the way in which Channel Elements uplink and downlink values have been counted

For WCDMA PM Daily report

Version 1


95 (138)


Row Name

Description

Comment

Processing Sets

It shows method of calculating processing sets. Available options are: Off, On, Incremental capacity units.

For WCDMA PM reports

HSxPA Processing Sets trigger

Shows unit taken into account when calculating processing sets. Available options are User and User & Mbps.

For WCDMA PM reports using Processing Sets

Processing Set 2 only

It shows if only processing set 2 is used.

For WCDMA PM reports in case of Processing Sets = On

Processing Set 3 weight factor

It shows the weight of processing set 3 compare to processing set 2.

For WCDMA PM reports in case of Processing Set 2 only = No

TargetId

Identification number of NetAct.

Customer names

Shows the customer name

Excluded days

Shows periods excluded from monitoring scope.

Signature

Hash value used for checking the data integrity.

Version 1


96 (138)

Software Management and Remote NE Backup

5

Version 1



97 (138)


5.1

Software Management in NetAct

Configuration changes are constantly needed to evolving networks to secure, maintain, or improve the service level perceived by the end users. With introduction of new services, networks are enhanced to meet high demands of new generation consumers. The configuration changes to complex and large networks must be well planned, documented, controlled, approved, and executed to avoid unplanned conflicts and symptoms in the network, which might cause service level degradation. Software management play a central role in configuration changes and in the change control process. Change requests including software updates in the network can originate from various sources, such as

     

Faults in current software, which need to be fixed. Changes in other elements, which a creates need for compatibility changes in interfacing elements. Introduction of new services, and enhancements to existing ones. Hardware changes in elements (for example, capacity increase). Security patches. End of life of products, causing software replacements.

Version 1


98 (138)


Centralized Software Management and NE Backup NetAct Software Management is used for managing end-to-end process of deploying SW releases and patches, creating SW backups and restoring functionality efficiently in complex and large multi-technology networks. Centralized Software Pool

Secured SW delivery

Nokia Solutions and Networks SW Gateway farms

Software Lifecycle Process

SW inventory

SQA and SW Lifecycle Control

MV SWM Library

Internet

VPN connections Nokia Solutions and Networks EMS

SW update, upgrade via EMS

1

Nokia Solutions and Network NEs


Fig. 48

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia . . Solutions . . . and. Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99 (138) . . . . . . .


5.2

Software Manager

Software Manager allows remote management of software configurations in network elements. It allows to upload the software configuration information from NE to Nokia Siemens Networks NetAct, download the NE software from NetAct to NE, import NE SW, and activate the NE SW. Users can easily search and examine software configuration data from a remote location. The system saves the software configuration information in the NetAct database, which can regularly be updated. An important feature of this application is also that the NEs' software can be stored to the NetAct disk and be downloaded to the managed objects from a remote location. All executed and ongoing tasks can be reviewed in the status view. With Software Manager functionalities, the users can:

          

View the task and corresponding NE details: Network Element information Latest task information Software tree Software details Upload software configuration information from NE to NetAct. Download NE software from NetAct to NE. Activate NE software in network element. Compare network elements’ software versions. Schedule tasks and manage schedules. Manage SW packages in centralized Software Archive.

Version 1


100 (138)


Software Management in NetAct Functionality in NetAct

1


Fig. 49

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 . (138) . . . . . . . . . .


Software Management in NetAct Software Manager Tasks

Software Manager in NetAct 8 allows to:  Manage Network Elements’ software configuration

 Change Network Element’s software  Manage Network Element’s software packages archived in NetAct

 Perform and Store Remote Backups from supported Network Elements:  Full Backup  Full Backup to External Device  Partial Backup  Partial Backup to External device  Partial Backup to NMS 1


Fig. 50

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 . (138) . . . . . . . . . .


5.3

Software Manager Operations

The Software Manager user interface consists of the below four views: Network Status: Software Network Software Status provides a centralized software configuration register for the network element software of the managed network. Network Operations The Tasks view is intended for monitoring the status of the software management tasks. The status of the individual operations can be seen in the Tasks main view. The Details tab includes more detailed information of each operation. Software Archive Software Archive provides a centralized network element software storage for network element releases and NetAct change deliveries. After the software is imported, the software is stored in the NetAct disks in one directory specific per network element type.

Version 1


103 (138)


Centralized Software Management and NE Backup Operations Network Status • Overview of SW status of certain NE type in whole network • Detailed NE(s) or SW packages in network view • Management of customer’s own NE sets • Provisioning tasks (upload, download, activate, pre-check, create full and partial backup)

• NE(s) SW packages compare SW and Backup Archive • Centralized SW and NE Backup repository in NetAct • Browse, import SW to, remove SW from archive, download backup to local storage • Detailed SW and Backup package information view Task management • Creating, viewing, removing and rescheduling the tasks (waiting, ongoing, completed) 1


Fig. 51

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 . (138) . . . . . . . . . .


5.3.1

Software Manager Graphical User Interface

Centralized Software Management and NE Backup Operations: Graphical User Interface Software Manager implements a graphical user interface that integrates SW Management and Network Elements Backup Management in the same window.

1


Fig. 52

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia . . Solutions . . . and . Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 . (138) . . . . . . . . . .


5.3.2

Network Software Status

Network Software Status implements a centralized, up-to-date software configuration status for the network element software of the managed network. Network Software Status is especially useful in troubleshooting cases and when planning software installations. This is because there is no longer need to use remote MML commands for viewing the software configuration, nor to record the existing software manually on spreadsheet documents. Network Software Status provides the following functionalities:

    



 

View the software status of certain network element type in the whole network. View the software configuration of a network element: Software builds, change deliveries, change notes, and files are listed. Upload software configuration from network element(s): You can schedule an upload from network element(s) to the Software Manager at any time. It is also possible to define repeatable tasks (daily, weekly, monthly). Upload status can be monitored in Tasks tab. Download software to network elements: You can schedule software download so that the system automatically downloads software to the network elements as required. Download status can be monitored in Tasks tab. Activate certain network elements: When you download software to network elements, you can set the software to be automatically activated after the download. This is supported for MGW network elements. You can schedule the activation of downloaded network element as required. Activation status can be monitored in Tasks tab. Compare SW status for selected NEs: You can compare currently installed software for MSS and MGW (only) by selecting the network elements and pressing Compare SW button. You can also use filtering to see in which network elements a particular CD set is installed. Search network elements: You can have a list of the network elements which fulfill the search criteria. Search can be run based on any saved database information. Managing own sets: You can create own sets of network elements, export from and import into Software Manager. Import/Export functionality allows you to use other tools (for example Excel) to manage a list of network elements to be downloaded, activated, or uploaded via Software Manager.

Version 1


106 (138)


Centralized Software Management and NE Backup Operations: viewing Network Software Status Network Software Status provides a centralized, up-to-date software configuration status for the network element software of the managed network.

1


Fig. 53

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 . (138) . . . . . . . . . .


5.3.3

Viewing Details of a Managed Object

This section allows viewing detailed information such as software version information or tasking related information of the selected network element.

1. Select the Network Status view. 2. Select the Software tab. 3. Select Parent from View drop-down list. Note: You can also choose Maintenance region option, to view the network divided into maintenance regions. Select managed object type from MO type list.

4. 5. Select parent managed object from the list located on the left side of the window.

Note: If the Maintenance region option was chosen from View drop-down list, then select a maintenance region in this step.

6. Click

(the Show NE Details icon) located on the left of NE name. The details window appears. You can view detailed information such as Managed Object information, Latest task information and Software details.

Version 1


108 (138)


5.3.4

Uploading software configuration information from NE to NetAct

This section describes how to upload the software configuration information from network elements to NetAct (synchronize NE with NetAct). Before downloading and activating new software in any network element it is necessary to know the previous configuration or software version information.

WARNING If a task is in the Ongoing state on a particular network element, then you cannot create a new task on the same network element to be run immediately. If you try to create such a task, then an error message is displayed. To Upload the Software Configuration: 1. Select Software from the Network Status menu bar.

2. Select Parent from View drop-down list. You can also choose Maintenance region option, to view the network divided into maintenance regions.

3. Select managed object type from the MO type list. 4. Select parent managed object from the list located on the left side of the window. If the Maintenance region option was chosen from View drop-down list, then select a maintenance region in this step.

5. Select the network element by clicking the check box placed at the extreme left in the Network Elements table.

6. Click New Task... button. New Task wizard appears.

7. In step 1 of the wizard select Software Upload from Task Type drop-down list and click Next. You can also do the following:

 

Fill in the Task name field. Default value is MO name. Write a description of the task in Task description field. Note: Click the icon to display operation description and the default timeout.

Version 1


109 (138)


8. In step 2: a) Decide when to start the task.

  

If Frequency is set to Immediately, the task will be started when the wizard is completed. If Frequency is set to Once, fill the Start date field. If Frequency is set to Periodically, fill all fields to schedule the number of task executions.

b) Choose the method of starting tasks and click Next.

 

Parallel- tasks on selected network elements are started simultaneously.

Sequence- tasks on selected network elements are started sequentially. Checking the Interrupt on failure check box causes cancelling tasks by the system if the previous task in the sequence failed. If the Interrupt on failure check box is not checked, system retries running task on the network element on which the task could not be done at the first time because the other task was in the Ongoing state on that particular network element. Tasks in group- determines the number of tasks that can be started simultaneously.

9. In step 3 click Finish to create Software Upload task. In this step you can see the summary of the created task. You can also correct task data by clicking the Previous button or close the wizard without creating a new task by clicking the Cancel button. After completing all the steps, a new Software Upload task is created. Steps from 6 to 9 can be substituted by pressing the Synchronize button that also causes that a new Software Upload task is created and can be seen from the Network Operations view’s Tasks tab.

WARNING If there are more than 250 NEs selected for a task, they are not viewed by default. If you want to view them all, click the available link. In the main view in the Status column, a current status of the Software Upload (synchronization) operation is displayed. If you have failed status you can click the status to see further information on the failed uploads in the Status column. If you have completed the steps successfully, the Networks Elements are synchronized with NetAct.

Version 1


110 (138)


Centralized Software Management and NE Backup Operations: Uploading SW Configuration

or

1


Fig. 54

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 . (138) . . . . . . . . . .


5.3.5

Network Operations- Tasks

For a selected NE type, you can view scheduled, ongoing and executed tasks.

1. Select the Network Operations view. 2. Select the Tasks tab. 3. Select the NE type from the MO type drop-down list.

4.

All tasks for selected managed object type are displayed in a tasks table and automatically sorted descending by Start date. Click on Started/Finished time box or (the calendar icon) to set the time range of displayed tasks. The pop-up calendar appears, where you can select the date and enter the hour.

5. Submit changes by clicking the Apply button. The list of tasks is updated accordingly to selected time range. You can view all the tasks for selected network element type and time range.

TIP You can sort the data in the table by the content in each column. Sorting in the following columns: MO DN, MO name, Finished, alternates the order of subtasks in the single group. Sorting in the following columns: Task Name, Task Type, Created on, Start date, Creator alternates task groups order. 6. Click the icon to expand the task group onto single tasks. 7. Follow the link in the Status column to show the details of single task

Version 1


112 (138)


Centralized Software Management and NE Backup Operations: Tasks Network Software Operations – Tasks view is intended for monitoring the status of software management tasks. The status of each individual operation can easily be seen from the main view. Details tab includes more detailed information of each operation.

Tasks can be managed (created, viewed, removed, cancelled, rescheduled) in this view.

1


Fig. 55

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 . (138) . . . . . . . . . .


5.3.6

Software Archive

The Software Archive tab allows to manage software packages, which are already stored in Software Archive. You can examine the details of a single software package, see the list of managed objects compatible with the browsed software package and download the package to compatible network elements. For managed objects for which multi package management is defined, you can create a virtual package, which combine physical software packages stored in Software Archive into one virtual software. The operations available for Software Archive are:



    

Import software to the archive: For the selected MO type, the user can import software from a CD, from the workstation, or from NetAct directory into the software archive and store them in Software Archive. The import SW operation is executed with the SW Import Manager java application. Browse and view archived software: You can have a view of the software stored in the software archive. Remove archived software: You can remove software stored in the software archive. Rename archived software: You can rename software stored in the software archive. Change the internal lifecycle of software build status. Declare different statuses for software builds according to operator-internal business process.

Additionally, the information about the Software Archive current disk space divided into disk usage and available free space is included in the upper right corner of the Software Archive tab.

Version 1


114 (138)


Centralized Software Management and NE Backup Operations: Software Archive Software Archive implements a centralized storage for the software of network element releases and change deliveries in NetAct. With this functionality the user can efficiently import software to the archive, and manage the archived software.

Deletion from Archive, renaming packages and moving SW Package from one folder to another are supported. User is able to drag and drop SW packages from folder to another.

1


Fig. 56

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 . (138) . . . . . . . . . .


Centralized Software Management and NE Backup Operations: Software Archive – Import Manager

SW Import Manager is used to import single or multiple SW packages to NetAct repository. SW package import time can be can be stopped and resumed effectively secure the bandwidth between NetAct and NE.

1


Fig. 57

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 . (138) . . . . . . . . . .


5.3.7

Attaching / Viewing Software Package Documentation

In the Software Archive tab you can also attach additional documentation to the software packages, both for physical software packages and virtual ones. In particular, for network elements which require additional installation scripts for some operations, you can attach installation scripts to the regular software packages. Note: Documentation can be attached only to software packages that are located in Software Manager repository, both for packages from Local repository and virtual packages To attach documentation tot he software packages: 1. Select the Software Archive tab. 2. From the MO type drop-down list, select the managed object type or subtype. 3. From the list located on the left side of the window, select a package name under a desired release folder. As a result, the selected software package is highlighted with blue color. The software package information is populated in the Summary tab. 4. Click the Documentation tab. 5. Click the Attach... button. Expected outcome The Attach Documentation to Software Package dialog opens. 6. In the Attach Documentation to Software Package dialog click the Attach file... button. 7. By using the file chooser, select the file you want to attach to the software package. The maximum file size for import to Software Manager is 25 MB. 8. Click the Open button The selected file is attached to the Software Archive. In the Attach Documentation to Software Package dialog, you can see the progress message of the uploaded file. 9. Click the Close button. The selected file is added to the software package. In the Documentation table there is information about file size. In the Action column, there are two options available. Note: If you add more than one file with the same name, the next files are visible in the Documentation table as _x.. Where, • x- numbers {1,2,3,...} added after the file name depending on the attaching files with the same name order. Example: If you add three documentation.txt files they are visible in Documentation table in the following way: documentation.txt documentation_1.txt

Version 1


117 (138)


Centralized Software Management and NE Backup Operations: View / Attach Software package release documentation NetAct 8: The software package release documentation and additional information about specific handling can be attached per each imported software package

1


Fig. 58

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 . (138) . . . . . . . . . .


5.3.8

Viewing Compatible Managed Objects

The prerequisite for searching database against the compatible managed object is the support of the Active Software operations, which require a software package as a parameter (for example Software Download, Software Provision). The conditions listed below determine the software package compatibility: • software package is assigned to the same MO type/subtype and has at least one common release version; • software package is assigned to the common Maintenance Region which is defined by Lifecycle status To see the compatible managed objects:

1. Select the Software Archive tab. 2. From the MO type drop-down list, select the managed object type or subtype. 3. From the navigation tree located on the left side of the window, select a package name under a desired release folder. As a result, the selected software package is highlighted with blue color. 4. Click the Compatible Managed Objects tab to see a table listing managed objects that are compatible with the browsed software package. All managed objects that can use the selected software package are listed in the network element table. The list of compatible managed objects to the selected virtual package is generated based on the given virtual package properties (MO Type, Release, Lifecycle status). In that case, the target dependencies of physical software packages forming the given virtual package are not taken into account. If, during the importing of a software package the managed object subtype was defined, in the Compatible Managed Objects frame you can see the network element table filtered by MO type and set MO subtype. If the selected MO type does not support the backup operations, the last column showing the backup information in the network element table becomes hidden.

Version 1


119 (138)


Centralized Software Management and NE Backup Operations: View Compatible network elements for SW package installation NetAct 8: The application has capability to filter compatible network elements for new software deployment based on software package release version.

1


Fig. 59

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 . (138) . . . . . . . . . .


5.3.9

Changing status of software package in Software Archive

To change status of the software package in the Software Archive, execute the following steps:

1. Select the Software Archive tab. 2. From the MO type drop-down list, select the managed object type or subtype. 3. From the list located on the left side of the window, select a package name under a desired release folder by clicking a desired node. As a result, the selected software package is highlighted with blue color. The software package information is populated in the Summary tab.

4. Click change status... link next to the Lifecycle status attribute in the Summary tab. The Change lifecycle status dialog opens.

5. From drop-down list, select a desired lifecycle status. 6. Click OK. The Lifecycle status is updated in Summary tab. Click see history... link to see the history of lifecycle status changes. You can see maximum 10 previous statuses in the list.

Version 1


121 (138)


Centralized Software Management and NE Backup Operations: Setting Software package Lifecycle Status support and software Quality Enforcement NetAct 8: • The package version and lifecycle status is used to filter compatible network element for software deployment • Software Quality Enforcement is used to validate operation requests with software package lifecycle status

1


Fig. 60

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version . . 1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 . (138) . . . . . . . . . .

Network Element Backup Support

6

Version 1



123 (138)


6.1

Network Elements Remote Backup from NetAct

Taking a regular backup of the software and databases of the network elements ensures that you have a functional copy of the software which you can use if there are any problems with the software or hardware of the network element. This backup is called a fallback. How often you need to take a fallback depends on various factors. It is recommended to take a fallback before and after changes in the software or hardware of a network element. Make sure that the network element works with the new software or hardware before taking a fallback after the changes. The procedure of creating a fallback and storing and copying the fallback build of the network element data remotely from a NetAct Server comprises three main phases: 1. Controlling a fallback of the network software build Take an automatic fallback of the network element software build. The fallback build is saved on a disk in the network element. The fallback build may comprise all files (full fallback), data files (data fallback), or only the changed files (archive fallback). 2. Copying a fallback build into a network element local media There are two options available for copying a fallback build into a local media: • You can copy the fallback build from the disk of the network element onto a DDS tape in the network element. • You can copy the fallback build from the disk of the network element onto a magnetic optical disk (MOD) in the network element. 3. Copying a fallback build into the fallback archive in NetAct You can copy the fallback build from the disk in the network element to a disk in NetAct (fallback archive) using FTP

Version 1


124 (138)


Centralized Software Management and NE Backup NE Backup Support

Take a fallback of Network Element SW build: The FB build is saved on disk in the NE

Copy the FB build into a NE local media (DDS tape or MOD)

Copy the FB build into the fallback archive in NetAct

Remote backup operations can executed on demand or periodically (scheduled) 1


Fig. 61

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 . (138) . . . . . . . . . .


6.2

Network Elements Backup Archive

Software Manager supports Flexi Platform based Network Elements (OMS, mcRNC, FlexiNG) data file backup from NE to NetAct. Data files are stored in a global disk in NetAct. The size of one file may exceed 2 GB, so the global disk space can be easily consumed after several rounds of backup operations. It is recommended to estimate the needed space for NE backups in order to have at least 30% of the global disk free. WARNING Filling up the global disk to its maximum can endanger the correct operations of the whole NetAct system. In order to prevent disturbances in normal operation of NetAct, it is possible to link the default backup repository to different storage location. The default solution is to add a shared storage for NetAct Software Manager application and link it as a default backup storage folder. Note: It is recommended to perform this operation by NSN Technical Support. The Network Elements Backup Archive view displays all existing backups of the selected network element. The created backups are stored on the network element's disks and additionally can be sent to an external device or to NetAct. With the Storage type filter can be used to display data in a desired manner. If the backup is stored in NetAct you can also find the URL Images, from where the NetAct user can download the backup files. In the upper right corner of this tab you can find the information about the Backup Archive current disk space divided into disk usage and available free space.

Version 1


126 (138)


Centralized Software Management and NE Backup Network Elements Backup Archive

The backup files are stored on the network element side or copied to NetAct backup repository. User is able view the last available backup on specific network element and can save it to local machine.

1


Fig. 62

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Version . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .


. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 . (138) . . . . . . . . . .


6.2.1

Creating Network Elements Backups

Centralized Software Management and NE Backup Creating Network Elements Backups

1


Fig. 63

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Version 1 . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia . . Solutions . . . and . Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 . (138) . . . . . . . . . .

Exercises

7

Version 1

Exercises


129 (138)

Exercises

Version 1


130 (138)

Exercises

Exercise 1 Title:

SW Asset Monitoring and License Management Concepts

Objectives:

Describe the License Manager functionality Differentiate the use cases for SW Asset Monitoring and License Manager

Pre-requisite:

none

Query 1. What are the advantages of SW Asset Monitoring compared with the traditional License Manager?

2. What is the purpose of NetAct License Manager?

3. What types of Licenses can be handled with License Manager?

4. List the new restrictions in the NetAct licensing in NetAct 8.

Version 1


131 (138)

Exercises

5. What is the “Hard Lock” mechanism?

6. What are the two types of time licenses in NetAct 8?

7. How are license pools used?

8. What are the SW Licenses used for?

9. Why a license can be in “conflicting” state?

10. What is the difference between “Guided Distribution” and “Automatic Distribution”?

11. What are Templates used for?

12. In what cases is necessary to execute a License Pool substitution?

Version 1


132 (138)

Exercises

Exercise 2 Title:


Objectives:

Import licenses to the License Repository Synchronize the License Information Report the existing licenses for network elements and NetAct Report the Features in Network Elements

Pre-requisite:

none

Task Open License Manager Application

Query 1. Synchronize the license information for one (or several) network elements. List the steps required for this task. How can you verify the licenses were synchronized?

2. Execute a report for the licenses installed for NetAct. How many licenses can you find? List some of the licensed products

3. Revise the features installed in one of the NetAct installed licenses. Verify if the feature “Optimizer for LTE” is available

Version 1


133 (138)

Exercises

4. Execute a Feature Report for one of the supported network elements.

5. Export one of the licenses synchronized in the step 1.

6. Distribute one License available in the test system, accordingly to the instructions of your trainer.

Version 1


134 (138)

Exercises

Exercise 3 Title:


Objectives:

Describe Software Asset functionality Revise the software for specific network elements Upload Software configuration Setup Backup for Network elements

Pre-requisite:

none

Task Open Software Asset Monitoring Application

Query 1. What is the purpose of SW Asset Monitoring?

2. What is the purpose of the modules used for in Software Asset Monitoring?

3. How the customer can get the SWAM Reports?

4. Check in SWAM the available reports and download one of them. List some of the monitored features.

Version 1


135 (138)

Exercises

Version 1


136 (138)

Exercises

Exercise 4 Title:

Software Management

Objectives:

Describe Software Management functionality Revise the software for specific network elements Upload Software configuration Setup Backup for Network elements

Pre-requisite:

none

Task Open Software Manager Application

Query 1. Explain the main functionalities of Software Manager

2. Upload the Software configuration for one supported network element. Describe the procedure. How can you check the operation status in the application?

3. Revise the Software configuration of your network element. Export the results into a file and list the main steps for these two tasks.

Version 1


137 (138)

Exercises

4. Execute a Fallback Backup of a supported network element and copy it to NetAct. How can you verify the correct execution of this task?

5. Download the backup file to your computer.

Version 1


138 (138)

05 OS82125EN80GLA00 License & SW Management

Recommend Documents