Licence ManagementSync From Netact

Managing licences

2

Managing licences There are two command line user interface tools for the Network Licence Manager application: Network Licence Management command line tool and Licence Reporting command line tool. The Network Licence Management command line tool is used to perform the following operations: .

.

Distributing licence files into network elements. Synchronising licence information in the NetAct database with the network element licence information.

.

.

Setting feature states in network elements. Deleting licence files from network elements.

The Licence Reporting command line tool is used to perform the following operation .

Running reports on licence information.

You can follow how all the operations are performed with the Recent Operations dialog in the Network Licence Manager graphical user interface, if it has been opened before starting the operation. However, generating reports from the command line interface does not show in Recent Operations. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help .

2.1

Distributing licence files into network elements This section describes how you can distribute NE and NMS-generated licence files into network elements by using the Network Licence Manager command line user interface. For more information on NMS-generated licences, see section 1 Licence file distribution in the Licence Management Principles document.

DN0591066 Issue 3-0 en

# NokiaSiemensNetworks

13(108)

Managing Licences

There are two ways to distribute a licence file: to all its target elements, or to specified target network elements. The Distribute licence files to specified network elements option is used if you do not want to distribute the file to all its target elements or if the file has already been distributed to some of its target network elements. During licence file distribution, it is also possible to set the feature state for DX200-based network elements (BSC, MSC, HLR, 2G-SGSN and MGW) with the optional fstat parameter. Redistributing a licence file to a network element is not possible, if the NetAct database considers that the network element already contains the licence file. This can happen, for example, if a licence file has been removed from the element due to hardware replacement. To update the licence file information to NetAct, you must run a synchronisation operation. After that, distributing the licence file is possible again. For more information on the synchronisation operation, see section 2.3.1 Uploading the status of all licence files from network elements .

2.1.1

Distributing licence files to all the target network elements specified in the licence file You can distribute licences to all the network elements whose target identifiers are specified in the licence file. If so instructed in the Feature Activation Manual, you can also set the state of the features for DX200based network elements (BSC, MSC, HLR, 2G-SGSN and MGW) using the fstat parameter. The licences specified in the distribute commands can have different target identifiers.

Note For the DX200-based network elements, Feature State ( fstat) is an optional parameter in the distribute operation. If the feature state is not specified in the commands, the default values defined by the DX200 MML interface are used. For information on the default values for the feature state, refer to the specific network element documentation in Nokia Online Services (NOLS). You can access NOLS at http://www. online.nokia.com. Accessing NOLS requires authentication. For NWI3-based network elements Feature State ( fstat) is a forbidden parameter for the distribute operation.

14 (108)



Managing licences

Prerequisites The licence file has not yet been distributed to any of its target network elements.

.

At least one of the target network elements is integrated to this NetAct Regional Cluster.

.

.

The licence is not expired.

.

The licence file is in the NetAct licence repository. There are no ongoing operations for the same licence or element. This ensures that the operations are performed in the intended order.

.

To distribute licence files to all the network elements 1. 2.

Log into the System Server as a user with Licence_Mgmt. Distribute or Licence_Mgmt.CommandLine_UI.Use permissions. Run the following command:

% ne ta ct _s ta rt .pl li c/l ic cor e -- l ic cu im x -o p dow nlo ad -fileN ame [-fsta t ]

Table 1.

\

Variable list

Variable

Explanation

Replace this variable with the name of the file or files, for example, A123456 7.XML When you enter multiple values, separate the values with a space.

You can choose one of the values ON, OFF, or CONF. The correct value is mentioned in the Feature Activation Manual of the feature. The fstat parameter is optional.

Once the command has been run, you will see a response that shows the task status. If the status is Success, the operation was successful. If the status is Failed, the operation was unsuccessful. You will see the reason for the failure in the Details column of the response. Note that the licences are only distributed to the integrated network elements. The distribution will not be done for all the unintegrated Network Elements present in the licence file. You can also see the result of the operation in the Recent Operations



15(108)

Managing Licences

dialog in the Network Licence Manager graphical user interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help .

2.1.2

Distributing licence files to specified network elements If you do not want to distribute the file to all its target elements or if the file has already been distrib uted to some of its targets, you must distribute the licences only to specified network elemen ts. If so instructed in the Feature Activation Manual, you can also set the state of the features for DX200based network elements (BSC, MSC, HLR, 2G-SGSN and MGW) using the fstat parameter. The licences specified in the distribute commands can have different target identifiers. You can specify the target network elements using either their target identifiers or their internal identifiers.

Note For the DX200-based network elements, Feature State ( fstat) is an optional parameter in the distribute operation. If the feature state is not specified in the commands, the default values defined by the DX200 MML interface are used. For more information, see W7 - Licence and Feature Handling, dn0491791, in Nokia Online Services (NOLS). You can access NOLS at http://www.online.nokia.com. Accessing NOLS requires authentication. For NWI3-based network elements Feature State ( fstat) is a forbidden parameter for the distribute operation.

Prerequisites .

The specified target network elements are integrated to this NetAct Regional Cluster and have their target identifiers specified in the licence file.

.

.

16 (108)

The licence is not expired. The licence file is in the NetAct licence repository.



Managing licences

When distributing several licence files to specified network elements, each licence file must contain the target identifiers of the network elements specified in the command.

.

There are no ongoing operations for the same licence or element. This ensures that the operations are performed in the intended order.

.

To distribute licence files to specified network elements using target identifiers 1.

Log into the System Server as a user with Licence_Mgmt. Distribute or Licence_Mgmt.CommandLine_UI.Use permissions.

2.

Run the following command that specifies the network elements using their target identifiers:

% net act _st art .pl lic /li ccor e -- lic cui mx -op dow nlo ad \ -fi leN ame -t arg etI d

Table 2.

[-fs tat ]

Variable list

Variable

Explanation Replace this variable with the name of the file or files, for example, A1234567. XML When you enter multiple values, separate the values with a space.

Replace this variable with the target identifier(s), for example, 12345. When you enter multiple values, separate the values with a space.

Choose one of the following values OFF, or CONF.

ON ,

The correct value is mentioned in the Feature Activation Manual of the feature. The fstat parameter is optional.

Once the command has been run, you will see a response that shows the task status. If the status is Success, the operation was successful. If the status is Failed, the operation was unsuccessful. You will see the reason for the failure in the Details column of the response. You can also see the result of the operation in the Recent



17(108)

Managing Licences

Operations dialog in the Network Licence Manager graphical user interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help

To distribute licence files to specified network elements using internal identifiers 1.

Log into the System Server as a user with Licence_Mgmt. Distribute or Licence_Mgmt.CommandLine_UI.Use permissions.

2.

Run the following command that specifies the network element using the NetAct internal identifier:

% net act _st art .pl lic/ lic cor e -- liccu imx -op downl oad \ -fi leN ame -i ntI d

Table 3.

[-fs tat ]

Variable list

Variable

Explanation Replace this variable with the name of the file or files, for example, A1234567. XML When you enter multiple values , separate the values with a space.

Replace this variable with the internal identifier(s), for example, 24. When you enter multiple values , separate the values with a space.


ON,

The correct value is mentioned in the Feature Activation Manual of the feature. The fstat parameter is optional.

Once the command has been run, you will see a response that shows the task status. If the status is Success, the operation was successful. If the status is Failed, the operation was unsuccessful. You will see the reason for the failure in the Details column of the response. You can also see the result of the operation in the Recent Operations dialog in the Network Licence Manager graphical user interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help

18 (108)



Managing licences

2.2

Setting feature states in network elements This section explains the process of setting feature states for DX200 network elements (BSC, MSC, HLR, 2G-SGSN and MGW) and NWI3 network elements (RNC) and describes the commands used to do it. Setting feature states for NWI3-based elements is not possible except for RNC. There are six different ways to set the feature state. You can: .

.

.

.

.

set the state of features in specified target network elements set the state of all features of licence files in all their target network elements set the state of all features of licence files for specified network elements set the state of some features of specified licence files to all their target network elements set the state of some features of licence files in specified network elements

.

set the state of features of a specified licence code in network elements. For more information on feature states, see section 1 Feature states in network elements in the Licence Management Principles document.

2.2.1

Setting the state of features in specified target network elements You can specify the target network elements using either their target identifiers or their internal identifiers. Prerequisites .

.

Licences for the features must exist in the specified network elements. The specified target network elements are integrated to this NetAct Regional Cluster. For instructions on integrating network elements, see the integration documents of each network element.

.




19(108)

Managing Licences

To set the state of features in specified target network elements using target identifiers 1.

Log into the System Server as a user with Licence_Mgmt. CommandLine_UI.Use permission.

2.


% net ac t_ st ar t. pl li c/ li cc or e -- li cc ui mx -o p sta te Ch an ge \ -t ar ge tI d -ne Ty pe \ -ft r -fs tat

Table 4.

Variable list

Variable

Explanation

Replace this variable with the target identifier(s), for example, 12345. When you enter multiple values , separate the values with a space.

Replace this variable with the type of the network element, for example BSC.

Replace this variable with the feature code. When you enter multiple values , separate the values with a space.

Enter one of the values

ON , OFF, or CONF.

Once the command has been run, you will see a response that shows the status of the operation. If the status is Success, the operation was successful. The response then also lists all features in the network element and their states. If the status is Failed, the operation was unsuccessful. You will see the reason for the failure in the Details column of the response. You can also see the result of the operation in the Recent Operations dialog in the Network Licence Manager graphical user interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help

To set the state of features in specified target network elements using internal identifiers

20 (108)



Managing licences

1.


2.

Run the following command that specifies the network elements using the NetAct internal identifier:

% net ac t_ st ar t. pl li c/l ic cor e -- li cc ui mx -o p sta te Ch ang e \ -in tId -f tr - fst at

Table 5.

Variable list

Variable

Explanation

Replace this variable with the internal identifier(s), for example, 24. When you enter multiple values, separate the values with a space.

Replace this variable with the feature code. When you enter multiple values, separate the values with a space.


ON , OFF, or CONF.


2.2.2

Setting the state of all features of licence files in all their target network elements Prerequisites .

The licence files must already be distributed to all of their target network elements For instructions on distributing licence s, see 2.1 Distributing licence files into network elements .



21(108)

Managing Licences

.

.

If the licence files are distributed from NetAct using Licence management application, this information is already present in the NetAct database. If the licence files are distributed from using Element manager, then the upload/synchronisation process should be run on that network element to synchronise the NetAct database.

For instructions on synchronising the licence files to NetAct database, see 2.3 Synchronising licence information in the NetAct database with the network element licence information The target network elements must be integrated to the NetAct Regional Cluster

.

For instructions on integrating network elements, see the integration documents of each network element. All licences must have the same target identifiers.

.


.

To set the state of all features of licence files in all their target network elements 1.


2.

Run the following command:

% net ac t_ st ar t. pl li c/ li cc or e -- li cc ui mx -o p sta te Ch an ge \ -fi leN ame -fs tat

Table 6.

Variable list

Variable



ON,

Once the command has been run, you will see a response that shows the status of the operation. If the status is Success, the operation was successful. The response then also lists all features in the network element and their states. If the status is Failed, the

22 (108)



Managing licences

operation was unsuccessful. You will see the reason for the failure in the Details column of the response. You can also see the result of the operation in the Recent Operations dialog in the Network Licence Manager graphical user interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help

2.2.3

Setting the state of all features of licence files for specified network elements You can specify the target network elements using either their target identifiers or their internal identifiers. Prerequisites .

The licence files must already be distributed to the specified network elements. For instructions on distributing licences, see 2.1 Distributing licence files into network elements . .

.


For instructions on synchronising the licence files to NetAct database, see 2.3 Synchronising licence information in the NetAct database with the network element licence information .

.

All of the specified target network elements must be in all of the specified licence files The specified target network elements must be integrated to the NetAct Regional Cluster. For instructions on integrating network elements, see the integration documents of each network element.

.


To set all the state of all features of licence files for specified network elements using target identifiers



23(108)

Managing Licences

1.


2.


% net ac t_ st ar t. pl li c/ li cc or e -- li cc ui mx -o p sta te Ch an ge \ -fi leN ame -t arg etI d -f sta t

Table 7.

Variable list

Variable

Explanation Replace this variable with the name of the file or files, for example, A1234567. XML When you enter multiple values , separate the values with a space. The licences mention ed in the command must be for the same network element type.

Replace this variable with the target identifier(s), for example, 12345. When youthe enter multiple , separate values with avalues space.


ON,


To set all the state of all features of licence files for specified network elements using internal identifiers

24 (108)



Managing licences

1.


2.


% net ac t_ st ar t. pl li c/l ic cor e -- li cc ui mx -o p sta te Ch ang e \ -fi leN ame -intI d -fs tat

Table 8.

Variable list

Variable

Explanation Replace this variable with the name of the file or files, for example, A1234567.XML When you enter multiple values, separate the values with a space. The licences mention ed in the command must be for the same network element type.

Replace this variable with the internal identifier(s), for example, 24. When you enter multiple values, separate

the values with a space. Enter one of the values ON , OFF, or CONF.




25(108)

Managing Licences

2.2.4

Setting the state of some features of specified licence files to all their target network elements Prerequisites .

The specified licence files must already be distributed to all the relevant network elements. For files instructions on distributing licences,target see 2.1 Distributing licence into network elements . .

.



The specified features must belong to the specified licence files.

.

All licences must have the same target identifiers.

.

The target network elements must be integrated to the NetAct Regional Cluster. For instructions on integrating network elements, see the integration documents of each network element.

.


To set the state of some features of specified licence files to all their target network elements 1.


2.

Run the following command:

% net act _st art .pl lic /li cco re -- lic cui mx -op sta teC han ge \ -fi leN ame -ft r -fs tat

26 (108)



Managing licences

Table 9.

Variable list

Variable


Replace this variable with the feature code. When you enter multiple values, separate the values with a space. The specified features must be available for all the specified licence files.


ON , OFF, or CONF.


2.2.5

Setting the state of some features of licence files in specified network elements You can specify the target network elements using either their target identifiers or their internal identifiers.



27(108)

Managing Licences

Prerequisites .

The licence files must already be distributed to the specified network elements. For instructions on distributing licences, see 2.1 Distributing licence files into network elements . .

If the licence files are distributed from NetAct using Licence management application, this information is already present in the NetAct database.

.

If the licence files are distributed from using Element manager, then the upload/synchronisation process should be run on that network element to synchronise the NetAct database.


.

.

All of the specified target network elements must be in all of the specified licence files The specified features must belong to the specified licence files. The specified target network elements must be integrated to the NetAct Regional Cluster. For instructions on integrating network elements, see the integration documents of each network element.

.


To set the state of some features of licence files in specified network elements using target identifiers 1.


2.


% net ac t_ st ar t. pl li c/ li cc or e -- li cc ui mx -o p sta te Ch an ge \ -fi leN ame -ta rge tId \ -ft r -fs tat

28 (108)



Managing licences

Table 10.

Variable list

Variable



Replace this variable with the feature code. When you enter multiple values, separate the values with a space. The specified features must be available for all the specified licence files.


ON , OFF, or CONF.


To set the state of some features of licence files in specified network elements using internal identifiers 1.

Log into the System Server as a user with Licence_Mgmt.

2.

Run the following command that specifies the network elements using the internal identifier:

CommandLine_UI.Use permission.

% net ac t_ st ar t. pl li c/l ic cor e -- li cc ui mx -o p sta te Ch ang e \ -fi leN ame -i ntI d \ -ft r -fs tat



29(108)

Managing Licences

Table 11.

Variable list

Variable



Replace this variable with the feature code. When you enter multiple values , separate the values with a space. The specified features must be available for all the specified licence files.


ON , OFF, or CONF.


2.2.6

Setting the state of features of a specified licence code in network elements You can specify the target network elements using either their target identifiers or their internal identifiers.

30 (108)



Managing licences

Prerequisites The specified network elements must contain a licence file with the specified licence code.

.

The specified target network elements must be integrated to the NetAct Regional Cluster.

.

For instructions on integrating network elements, see the integration documents of each network element. There are no ongoing operations for the same licence or element. This ensures that the operations are performed in the intended order.

.

To set the state of features of a specified licence code in network elements using target identifiers 1.


2.


% net act _st art .pl lic /li ccor e -- lic cui mx -op sta teC han ge \ -li cCo de
-t arg etI d \ -n eT yp e -f st at

Table 12.

Variable list

Variable

Explanation Replace this variable with the licence code, for example, BSC00038. You cannot enter multiple values.


Replace this variable with the network element type, for example BSC. You cannot enter multiple values


ON , OFF, or CONF.

Once the command has been run, you will see a response that shows the status of the operation. If the status is Success, the operation was successful. The response then also lists all features in the network element and their states. If the status is Failed, the



31(108)

Managing Licences

operation was unsuccessful. You will see the reason for the failure in the Details column of the response. You can also see the result of the operation in the Recent Operations dialog in the Network Licence Manager graphical user interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help

To set the state of features of a specified licence code in network elements using internal identifiers 1.


2.


% net act _st art .pl lic/l icc ore --li cCo de
- int Id

Table 13.

lic cui mx -op sta teC han ge \ -f sta t

Variable list

Variable

Explanation Replace this variable with the licence code, for example, BSC00038. You cannot enter multiple values



ON , OFF, or CONF.

Once the command has been run, you will see a response that shows the status of the operation. If the status is Success, the operation was successful. The response then also lists all features in the network element and their states. If the status is Failed, the operation was unsuccessful. You will see the reason for the failure in the column of the response. You can also see the result of Details in the Recent Operations dialog in the Network the operation Licence Manager graphical user interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help

32 (108)



Managing licences

2.3

Synchronising licence information in the NetAct database with the network element licence information This section explains how to update the licence information in the NetAct database to include licence information from the network element and describes the commands used to do it. Licence and feature information update to Network Licence Manager can be done in the following ways: .

Uploading the status of all licences from network elements. This is the preferred method of synchronisation.

.

.

.

Uploading the status of specified licence files from network elements. Uploading licence files from network elements. Updating network element information for licence management operations after rehosting.

For more information on the principles of licence synchronisation, see chapter 1 Licence information synchronisation in the Licence Management Principles document.

Note Synchronisation may be triggered automatically as a result of an operation related to licences that is made with element managers . This is not shown in the Recent Operations dialog.

2.3.1

Uploading the status of all licences from network elements The Upload status operation is used to synchronise NetAct database with the network elements. Upload status gets all the information related to licences and features from the network elements and updates the NetAct database accordingly. This is the preferred way of synchronising licence information. You can specify the target network elements using either their target identifiers or their internal identifiers.



33(108)

Managing Licences

Prerequisites There are no ongoing operations for the same licence or element. This ensures that the operations are performed in the intended order.

.

To upload the status of all licences from network elements using target identifiers 1.


2.


% net ac t_ st ar t. pl li c/ li cc or e -- li cc ui mx -o p upl oa dS ta tu s \ -ta rge tId -n eTy pe

Table 14.

Variable list

Variable

Explanation

Replace this variable with the target identifier(s), for example, 12345. When you enter multiple values , separate the values with a space. Replace this variable with the type of the network element, for example BSC.

After the operation, if the operation status is Success, the following information is shown, indicating which files: .

.

.

.

exist in the network element is in NetAct licence repository but do not exist in the network element (deleted) exist in network element but not in NetAct (the upload was started) are in the network element but are no longer valid for the element (conflicting).

If the status is Failed, the operation was unsuccessful. You will see the reason for the failure in the Details column of the response. If the synchronisation detects that a licence file exists in the element but is not yet in the NetAct licence repository, NetAct starts an automatic upload of the licence file. For instructions on how to verify the result of the automatic upload procedure, see section To verify the automatic upload of a missing licence file . You can also check the result of the upload operations from the Recent Operations dialog in the Network Licence Manager graphical user interface, if it

34 (108)



Managing licences

has been opened before starting the operation. For each of the automatic file upload operation, you can see a separate operation is the Network Licence Manager graphical user interface. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help .

Note Multiple target identifiers can be given as input. If the given target identifier is not found in topology database, it is considered as an invalid target identifier. If this input contains any invalid target identifiers, the status of such target identifiers will be shown as Failed in the command line result. Such invalid target identifiers will not be shown in Recent Operations dialog of Network Licence Manager graphical user interface.

To upload the status of all licences from network elements using internal identifiers 1.

Log into the System Server as a user with Licence_Mgmt.

2.

CommandLine_UI.Use permission. Run the following command that specifies the network elements using the NetAct internal identifier:

% net ac t_ st ar t. pl li c/l ic cor e -- li cc ui mx -in tId

Table 15.

-o p upl oa dS tat us \

Variable list

Variable

Explanation

Replace this variable with the internal identifier(s), for example, 24. When you enter multiple values, separate the values with a space.

For more information on the procedure to collect internal identifiers of AXC/WBTS located under an RNC, see section Script to prepare synchronization parameters for AXC/WBTS network elements under a given RNC . After the operation, if the operation status is Success, the following information is shown, indicating which files:



35(108)

Managing Licences

.

.

.

.

exist in the network element is in NetAct licence repository do not exist in the network element (deleted) exist in network element but not in NetAct (the upload was started) are in the network element but are no longer valid for the

element (conflicting). If the status is Failed, the operation was unsuccessful. You will see the reason for the failure in the Details column of the response. You can also see the result of the operation in the Recent Operations dialog in the Network Licence Manager graphical user interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help . If the synchronisation detects that a licence file exists in the element but is not yet in the NetAct licence repository, NetAct starts an automatic upload of the licence file. For instructions on how to verify the result of the automatic upload procedure, see section To verify the automatic upload of a licence file . You can also check the result of the upload operations from the Recent Operations dialog in the Network Licence Manager graphical user interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help.

Note Multiple internal identifiers can be given as input. If the given internal identifier is not found in topology database, it is considered as an invalid internal identifier. If this input contains any invalid internal identifiers, the status of such internal identifiers will be shown as Failed in the command line result. Such invalid internal identifiers will not be shown in Recent Operations dialog of Network Licence Manager graphical user interface.

To verify the automatic upload of a licence file

36 (108)

1.


2.

Run the Licences of Network Element report based on network element type and target identifier. For instructions, see section 3.2.1 Generating Licences of NE report based on network element type and target identifier .



Managing licences

If the licence file for which automatic upload operation was started by NetAct is listed in the report, then the upload operation was successful. If the licence file is not listed in the report, the upload operation was unsuccessful. Check Recent Operations for the reason why the operation failed. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help . If you do not have user rights to the Network Licence Manager graphical user interface, you can run the upload file operation manually to see the error message in the command line user interface. For instructions, see section 2.3.4 Uploading licence files from network elements .

2.3.2

Uploading the status of specified licence files from network elements This procedure synchronises the status of the specified licenc e files in the NetAct database with the status and feature information in the network elements. You can specify the target network elements using either their target identifiers or their internal identifiers. Prerequisites .

.

The licence file must be in the NetAct licence repository (imported or uploaded from the network element). There are no ongoing operations for the same licence or element. This ensures that the operations are performed in the intended order

To upload the status of specified licence files from a network element using target identifiers 1.


2.


% net ac t_ st ar t. pl li c/l ic cor e -- li cc ui mx -o p upl oa dS tat us \ -fi leN ame -ta rge tId



37(108)

Managing Licences

Table 16.

Variable list

Variable

Explanation

Replace this variable with the name of the file or files, for example, A1234567. XML When you enter multiple values , separate the values with a space.

Replace this variable with the target identifier(s), for example, 12345. When you enter multiple values , separate the values with a space. In this command the target identifiers do not need to be specified in the licence file.

After the operation, if the operation status is Success, the following information is shown, indicating which files: .

.

.

exist in the network element is in NetAct licence repository but do not exist in the network element (deleted) are in the network element but are no longer valid for the element (conflicting).

If the status is Failed, the operation was unsuccessful. You will see the reason for the failure in the Details column of the response. You can also see the result of the operation in the Recent Operations dialog in the Network Licence Manager graphical user interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help

Note Multiple target identifiers can be given as input. If the given target identifier is not found in topology database, it is considered as an invalid target identifier. If this input contains any invalid target identifiers, the status of such target identifiers will be shown as Failed in the command line result. Such invalid target identifiers will not be shown in Recent Operations dialog of Network Licence Manager graphical user interface.

38 (108)



Managing licences

To upload the status of specified licence files from a network element using internal identifiers 1.


2.


% n et ac t_ st ar t. pl li c/l ic cor e -fileN ame -intId

Table 17.

-- li cc ui mx -o p u pl oa dS tat us

\

Variable list

Variable

Explanation

Replace this variable with the name of the file or files, for example, A1234567. XML When you enter multiple values, separate the values with a space.

Replace this variable with the internal identifier(s), for example, 24. When youthe enter multiple separate values with avalues, space. In this command the target identifiers related to the internal identifiers do not need to be specified in the licence file.

For more information on the procedure to collect internal identifiers of AXC/WBTS under an RNC, see section Script to prepare synchronization parameters for AXC/WBTS network elements under a given RNC . After the operation, if the operation status is Success, the following information is shown, indicating which files: .

exist in the network element

.

do not exist in the network element (deleted)

.

are in the network element but are no longer valid (conflicting).

If the statusfor is Failed , the was unsuccessful. You will see the reason the failure in operation the Details column of the response. You can also see the result of the operation in the Recent Operations dialog in the Network Licence Manager graphical user interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help .



39(108)

Managing Licences

Note Multiple internal identifiers can be given as input. If the given internal identifier is not found in topology database, it is considered as an invalid internal identifier. If this input contains any invalid target identifiers, the status of such internal identifiers will be shown as Failed in the command line result. Such invalid internal identifiers will not be shown in Recent Operations dialog of Network Licence Manager graphical user interface.

2.3.3

Script to prepare synchronization parameters for AXC/WBTS network elements under a given RNC This chapter explains how to gather the internal identifiers of all AXC or WBTS elements located under a given RNC to a file and describes the commands used to do it. Internal identifiers are used as parameters for several command line operation s. There is a method to cellect the internal identifiers from topology databa se to a file to ease up the mass operations like running synchronisation to several elements in one go. All AXC or WBTS elements located under the given RNC are checked from the topology database and the ones with versions that are supported by Network element licence manager are picked to the generated file. There are two options that can be used, either the internal identifiers are collected to a txt file or a file containing a synchronisation command for the elements is created. The txt file contains only the internal identifiers (separated from each other by a space) and user can copy and pase the internal identifiers from the file to command line operations. This file can also be given as input. A script file licFindNEmx.pl is used to get the identifiers. The script supports two different options:

40 (108)



Managing licences

1.

generateOpfile: This collects the internal identifiers of all AXC/

WBTS as specified under the given RNC and writes the opfile with the needed parameters to perform synchronization for all the AXC/ WBTS under the RNC. The opfile can be used with liccuimx, the Licence Command Line tool to execute the synchronization. 2.

collectIntIds: This collects the internal identifiers of all AXC/

WBTS as specified under the given RNC and writes the internal identifiers to a text file (specified by the user). The internal identifiers are written space separated. The user can copy the internal identifiers from this file and use them while defining the command line for the liccuimx to perform synchronization. 2.3.3.1

Generating Opfile for all AXC/WBTS network elements as specified under the given RNC This chapter describes the procedure to generate the Opfile for all AXC/ WBTS network elements under the specified RNC. The Opfile can be generated using either the network element identifier or the internal identifier of RNC. The following sections explain in detail the steps to be followed for creating the Opfile.

Using the network element identifier of RNC 1.


2.

Run the following command that specifies the RNC using the network element identifier:

% netact _start .pl lic/li ccore -- licFin dNEmx. pl --op= genera teOpfi le --\ neId=< ne-id of RNC> --neTy pe= --file Name=\

Table 18.

Variable list

Variable

Explanation Replace this variable with Network Element identifier of the RNC. This variable represents the NE Type. Replace this variable with either AXC or WBTS. No other NE Type is accepted.



41(108)

Managing Licences

Table 18.

Variable list (cont.)

Variable

Explanation

Replace this variable with the name of the opfile that has to be generated. For example AXCopfile.txt By default the file will be generated in the current directory. To generate the file in a different location full path along with the file name should be given. For example /tmp/AXCopfile.txt

Using the internal identifier of RNC. 1.


2.

Run the following command that specifies the RNC using the internal identifier:

% netact _start .pl lic/li ccore -- licFin dNEmx. pl --op=g enerate Opfile --\ intId= --neTy pe= --file Name=\

Table 19.

Variable list

Variable

Explanation Replace this variable with internal identifier of the RNC. For example, 123456789 This variable represents the NE Type. Replace this variable with either AXC or WBTS. No other NE Type is accepted.

Replace this variable with the name of the opfile that has to be generated. For example AXCopfile.txt By default the file will be generated in the current directory. To generate the file in a different location, full path along with the file name should be given. For example /tmp/AXCopfile.txt

42 (108)



Managing licences

2.3.3.2

Generating space separated internal identifiers file for all AXC/WBTS network elements under the specified RNC This chapter describes the procedure to generate the space separated internal identifier file for all AXC/WBTS network elements under the specified RNC. The space separated internal identifiers file can be generated using either the network element identifier or the internal identifier of RNC. The following sections explain in detail the steps to be followed for generating the space separated internal identifiers file.

Using the network element identifier of RNC. 1.


2.

Run the following command that specifies the RNC using the network element identifier:

% netact _start .pl lic/li ccore -- licFin dNEmx. pl --op= collec tIntId s --\ neId=< ne-id of RNC> --neTy pe= --file Name=\

Table 20.

Variable list

Variable

Explanation

Replace this variable with Network Element identifier of the RNC. For example, RNC-3Q123456789

This variable represents the NE Type. Replace this variable with either AXC or WBTS. No other NE Type is accepted.

Replace this variable with the name of the file that has to be generated. For example AXCfile.txt By default the file will be generated in the current directory. To generate the file in a different location, full path along with the file name should be given. For example /tmp/AXCfile.txt



43(108)

Managing Licences

Using the internal identifier of RNC. 1.


2.

Run the following command that specifies the RNC using the internal identifier:

% netact _start .pl lic/li ccore -- licFin dNEmx. pl --op=c ollectI ntIds --\ intId= --neTy pe= --file Name=\

Table 21.

Variable list

Variable

Explanation Replace this variable with internal identifier of the RNC. For example, 123456789 This variable represents the NE Type. Replace this variable with either AXC or WBTS. No other NE Type is accepted.

Replace this variable with the name of the file that has to be generated. For example AXCfile.txt By default the file will be generated in the current directory. To generate the file in a different location, full path along with the file name should be given. For example /tmp/AXCfile.txt

2.3.4

Uploading licence files from network elements This procedure either compares the contents of the licence files in the network elements and NetAct or if the licence file does not yet exist in NetAct, copies the licence file from the network element to NetAct licence repository. You can specify the target network elements using either their target identifiers or their internal identifiers. You can also give the optional NE type parameter to specify a network element type.

44 (108)



Managing licences

Prerequisites If the licence file exists in NetAct licence repository, the network elements must be in the target identifier list.

.

There are no ongoing operations for the same licence or element. This ensures that the operations are performed in the intended order

.

To upload licence files from network elements using target identifiers 1.


2.


% ne ta ct _s ta rt .p l li c/ li cc or e -- l ic cu im x -o p up lo ad \ -fi leN ame - tar getI d [-n eTy pe ]

Table 22.

Variable list

Variable



Replace this variable with the type of the network element, for example BSC. This is an optional parameter.

Once the command has been run, you will see a response that shows the task status. If the status is Success, the operation was successful. If the status is Failed, the operation was unsuccessful. You will see the reason for the failure in the Details column of the response. If the licence file in NetAct and the network element differ in content, a Conflicting licence file message is shown. You can also check the result of the upload operations from the Recent



45(108)

Managing Licences

Operations dialog in the Network Licence Manager graphical user interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help .

To upload licence files from network elements using internal identifiers 1.


2.


% ne ta ct _s ta rt .p l li c/ li cc or e -- l ic cu im x -o p up lo ad \ -fi leN ame -in tId

Table 23.

Variable list

Variable



Once the command has been run, you will see a response that shows the task status. If the status is Success, the operation was successful. If the status is Failed, the operation was unsuccessful. You will see the reason for the failure in the Details column of the response. If the licence file in NetAct and the network element differ in content, a Conflicting licence file message is shown. You can also check the result of the upload operations from the Recent Operations dialog in the Network Licence Manager graphical user interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help .

46 (108)



Managing licences

2.3.5

Content of licence file verified in synchronisation The following fields in the licence file are compared when the Uploading specified licence files operation is run. If the content in any of the fields differs, the licence file will be marked as conflicting. .

.

Licence File Name Serial Number

.

Licence Code

.

Customer ID

.

Order ID

.

Start Time

.

End Time

.

.

.

.

MaxValue (For capacity NE licence, this is the value of capacity for each network element. For capacity pool licence, this is the size of the pool.) Feature Code Target network element Type Target identifiers.

The target identifier of the network element in question must be in the NetAct version of the licence file. In addition, the target identifiers field may contain target identifiers of other network elements. They are not verified in synchronisation.

2.3.6

Updating network element information for licence management operations after rehosting This section explains how to update the network element information for licence management operations and describes the command used to do it. This process is needed when Multiple MOs for Target ID icon is shown in the Network Licence Manager graphical user interface of Network Licence Manager or when the corresponding error message is shown in the command line user interface. For example, this process is needed when you are rehosting a WCDMA BTS site and the O&M connection is changed. In this case, multiple managed objects describing a single network element may exist in topology. The Network Licence Manager application needs to know which of these managed objects currently describes the network element.



47(108)

Managing Licences

The following section describes how to update the information to Network Licence Manager. You can specify the network elements using either their internal identifiers or their distinguis hed names.

To update the changed network element information for licence management operations using internal identifiers 1.


2.

Run the following command that specifies the network elements using their NetAct internal identifier:

% netact _start .pl lic/li ccore

Table 24.

-- licUpd ateMOm x.pl --intI d=
identi fier(s )>

Variable list

Variable

Explanation

Replace this variable with the internal identifier(s), for example, 24. In this command this value is the internal identifier of the managed object which has the O&M link. You can give multiple values in single quotes separated by commas and a space between the values, or without quotes if there is no space.

You will see a response indicating whether the operation succeeded or failed.

To update the changed network element information for licence management operations using distinguished name 1.


2.

Run the following command that specifies the network elements using their distinguished names:

% netact _start .pl lic/li ccore

48 (108)

-- licUpd ateMOm x.pl --dn=< distin guishe d name(s )>



Managing licences

Table 25.

Variable list

Variable

Explanation

Replace this variable with the distinguished name of the network element, for example PLMN-PLMN/RNC-123/WBTS-123. In this command this value is the distinguished name of the managed object which has the O&M link. You can give multiple values in single quotes separated by commas and a space between the values, or without quotes if there is no space.

You will see a response indicating whether the operation succeeded or failed.

2.3.7

Updating the licence management database with information on new network elements The licence about management shouldelements. be updated with information licencesdatabase of new network This isthe done by executing the licsynmx.pl script. This script is used to synchronise the licence management database tables with the Topology DB. This script is configured as a cron job to be executed once every night. This script can also be executed manually.

Updating the licence management database 1.

Log into the System Server as omc user or any user belonging to the sysop.

2.

Execute the following command: omc % net act _st art .pl



lic /li cco re

-- li csy ncm x.pl

49(108)

Managing Licences

2.4

Deleting licence files from network elements This section describes the commands used to delete licence files from network elements. There are four cases: deleting expired licence files using the file name, deleting licences that have not expired using the file name, deleting expired licences using the name of the pool licence file, and deleting licence files that have not expired using the name of the pool licence file. To delete licences that have not expired, a special forceDelete parameter is used.

2.4.1

Deleting expired licence files from network elements With these procedures you can delete expired licences from network elements by specifying the licence file names. You can give both NE and NMS-generated licence file names in these commands. For more information on NMS-generated licences, see section 1 Licence file distribution in the Licence Management Principles document. You can specify the target network elements using either their target identifiers or their internal identifiers. Prerequisites .

.

The licence must have been expired The target network elements must be integrated to the NetAct Regional Cluster. For instructions on integrating network elements, see the integration documents of each network element.

.

.

The target identifiers of the specified network elements must be in the NetAct version of the licence file. There are no ongoing operations for the same licence or element. This ensures that the operations are performed in the intended order.

To delete expired licence files from network elements using target identifiers

50 (108)

1.


2.




Managing licences

% ne ta ct _s ta rt .pl li c/l ic cor e -- l ic cu im x -o p de le te \ -fi leN ame -ta rge tId

Table 26.

Variable list

Variable



Once the command has been run, you will see a response that shows the task status. If the status is Success, the operation was successful. If the status is Failed, the operation was unsuccessful. You will see the reason for the failure in the Details column of the response. You caninalso see the result of the operation in the user Recent Operations dialog the Network Licence Manager graphical interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help

To delete expired licence files from network elements using internal identifiers 1.


2.


% ne ta ct _s ta rt .pl li c/l ic cor e -- l ic cu im x -o p de le te \ -fileN ame -intId



51(108)

Managing Licences

Table 27.

Variable list

Variable




2.4.2

Deleting licence files that have not expired from network elements With these procedures you can delete licences generated from the specified pool licence file that have not expired from the specified networ k elements. You also have to use it if you want to delete a licence from a network element which is no longer mentioned as a target in the NetAct version of the licence file. You can give both NE and NMS-generated licence file names in these commands. For more information on NMS-generated licences, see section 1 Licence file distribution in the Licence Management Principles document. You can specify target identifiers. network elements using either their target identifiers or theirthe internal

52 (108)



Managing licences

Prerequisites If the target network elements are specified in the Command Line, then those target network element s must be integrated to the NetAct Regional Cluster.

.


.

To delete licences that have not expired from network elements using target identifiers 1.


2.


% ne ta ct _s ta rt .pl li c/l ic cor e -- l ic cu im x -o p de le te \ -fileN ame -tar getId -forc eDelet e T

Table 28.

Variable list

Variable



Once the command has been run, you will see a response that shows the task status, istheSuccess , the was successful. If thestatus. statusIfistheFailed operation wasoperation unsuccessful. You will see the reason for the failure in the Details column of the response. You can also see the result of the operation in the Recent Operations dialog in the Network Licence Manager graphical user interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help



53(108)

Managing Licences

To delete licences that have not expired from network elements using internal identifiers 1.


2.


% ne ta ct _s ta rt .p l li c/ li cc or e -- l ic cu im x -o p de le te \ -fi leN ame -int Id -for ceD ele te T

Table 29.

Variable list

Variable


Replace this variable with the internal identifier(s), for example, 24. When youthe enter multiple , separate values with avalues space.


2.4.3

Deleting expired licences using pool licence file name With these procedures you can delete licences generated from the specified pool licence file that have expired from the specified network elements. You can delete all expired licences from all network elements or delete them only from specified target network elements. You can specify the target network elements using either their target identifiers or their internal identifiers.

54 (108)



Managing licences

Prerequisites If the target network elements are specified in the Command Line, then those target network element s must be integrated to the NetAct Regional Cluster.

.


.

To delete all expired licences from all network elements using pool licence file name 1.


2.

To delete all licences generated from pool licences from all network elements, run the following command:

% ne ta ct _s ta rt .pl li c/l ic cor e -fileN ame

Table 30.

-- l ic cu im x

-o p de le te \

Variable list

Variable

Explanation Replace this variable with the name of the pool licence file, for example, CA1234567.XML

Once the command has been run, you will see a response that lists the NMS-generated licence files and the task status for each file. If the status is Success, the operation was successful. If the status is Failed, the operation was unsuccessful. You will see the reason for the failure in the Details column of the response. You can also see the result of the operation in the Recent Operations dialog in the Network Licence Manager graphical user interface, if it has been opened before starting the operation. For more information on Recent Operations, see section Recent Operations in the Network Licence Manager Help

To delete all expired licences from specified target elements using target identifiers and pool licence file name



55(108)

Managing Licences

1.


2.

Run the following command which uses target identifiers to specify the network elements:

% ne ta ct _s ta rt .p l li c/ li cc or e -- l ic cu im x -o p de le te \ -fi leN ame -tar get Id

Table 31.

Variable list

Variable

Explanation Replace this variable with the name of the pool licence file or files, for example, CA1234567.XML Replace this variable with the target identifier(s), for example, 12345. When you enter multiple values , separate the values with a space.


To delete all expired licences from specified target elements using internal identifiers and pool licence file name 1.


2.

Run the following command which uses internal identifiers to specify the network elements:

% ne ta ct _s ta rt .p l li c/ li cc or e -- l ic cu im x -o p de le te \ -fi leN ame -in tId

56 (108)



Managing licences

Table 32.

Variable list

Variable

Explanation Replace this variable with the name of the pool licence file or files, for example, CA1234567.XML Replace this variable with the internal identifier(s), for example, 24. When you enter multiple values, separate the values with a space.


2.4.4

Deleting licences that have not expired using pool licence file name With these procedures you can delete licences that have not expired from network elements by specifying the name of the pool licence file. You can delete all licences that have not expired from all network elements or delete them only from specified target network elements. You can specify the target network elements using either their target identifiers or their internal identifiers. Prerequisites .

The target network elements must be integrated to the NetAct Regional Cluster. For instructions on integrating network elements, see the integration documents of each network element.

.


To delete all licences that have not expired from all network elements using pool licence file name



57(108)

Managing Licences

1.


2.

To delete all licences generated from pool licences from all network elements, run the following command:

% ne ta ct _s ta rt .p l li c/ li cc or e -- l ic cu im x -o p de le te \ -fi leN ame -fo rce Del ete T

Table 33.

Variable list

Variable

Explanation

Replace this variable with the name of the pool licence file or files, for example, CA1234567.XML


To delete all licences that have not expired from specified target elements using target identifiers and pool licence file name 1.


2.

Run the following command which uses target identifiers to specify the network elements:

% ne ta ct _s ta rt .p l li c/ li cc or e -- l ic cu im x -o p de le te \ -fi leN ame -ta rge tId -forc eDe let e T

Table 34.

Variable list

Variable

58 (108)


Explanation Replace this variable with the name of the pool licence file or files, for example, CA1234567.XML


Managing licences

Table 34.

Variable list (cont.)

Variable

Explanation

Replace this variable with the target identifier(s), for example, 12345.


To delete all licences that have not expired from specified target elements using internal identifiers and pool licence file name 1.


2.

Run the following command which uses internal identifiers to specify the network elements:

% ne ta ct _s ta rt .pl li c/l ic cor e -- l ic cu im x -o p de le te \ -fi leN ame -in tId -fo rce Del ete T

Table 35.

Variable list

Variable

Explanation Replace this variable with the name of the pool licence file or files, for example, CA1234567.XML Replace this variable with the internal identifier(s), for example, 24. When you enter multiple values, separate the values with a space.



59(108)

Managing Licences

Once the command has been run, you will see a response that lists the NMS-generated licence files and the task status for each file. If the status is Success, the operation was successful. If the status is Failed, the operation was unsuccessful. You will see the reason for the failure in the Details column of the response. You can also see the result of the operation in the Recent Operations dialog in the Network Licence Manager graphical user interface, if it has on been opened before starting the operation. For more information Recent Operations, see section Recent Operations in the Network Licence Manager Help

60 (108)



Licence ManagementSync From Netact

Recommend Documents