Pdn 03453584

Administering NetAct Configurator DN03453584 Issue 1-0

Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Siemens Networks for any additional information.

Administering NetAct Configurator

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens 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 Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation 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 and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens 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 Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document. Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY 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 documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright © Nokia Siemens Networks 2013/9/10. All rights reserved

f

Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

The same text in German:

f

Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen. Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheitsanforderungen erfolgen. Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentationssatzes.

2

Id:0900d80580a02f7a

DN03453584 Issue 1-0


Table of Contents This document has 106 pages. 1 1.1 1.2 1.3

About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NetAct compatibility and capacity information . . . . . . . . . . . . . . . . . . . . Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 2.1

Configuring BSC file-based upload, provisioning, and events . . . . . . . . 12 Checking and configuring user accounts for FTAM Unix Access service type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Enabling Node Manager launch functionality. . . . . . . . . . . . . . . . . . . . . 13 Configuring BSC file-based events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Solving problems with the XML-based events and core files generated by the zrnevhmx process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.2 2.3 2.3.1

DN03453584 Issue 1-0

10 10 10 10

3 3.1

Configuring HTTP file transfer for RNC and WBTS . . . . . . . . . . . . . . . . 16 Checking and configuring user accounts for HTTPS Unix Access service type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.7.1 4.7.2 4.7.3 4.7.4 4.7.5

Configuring NetAct Configurator DNS management . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of the operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Primary Name Server . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the p3nprxmx DDNS Proxy process. . . . . . . . . . . . . . . . . . Creating and configuring the DDNS access . . . . . . . . . . . . . . . . . . . . . Configuring LDAP for NetAct Configurator DNS management . . . . . . . Configuring DNS management for the rehosting operation . . . . . . . . . . Overview of the operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating shared secret key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding RAN zone name to LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring BIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring NameSurfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5

Configuring LDAP for NetAct Configurator . . . . . . . . . . . . . . . . . . . . . . 29

6

Configuring NE3S/WS Agent Port, URL path, Operation timeout and Response timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

7 7.1 7.1.1 7.1.2 7.1.3 7.2 7.3 7.4 7.4.1 7.4.2 7.5

Customizing NetAct Configurator applications. . . . . . . . . . . . . . . . . . . . 31 Enabling tracing for Connectivity Server services . . . . . . . . . . . . . . . . . 31 CM Bulk Data (blkdatmx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 GSM Upload Mediator (uplnwmmx). . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 NetAct Configurator CM BSC Mediation (cmmbscmx) . . . . . . . . . . . . . 32 Customizing the settings of CM Bulk Data subsystem . . . . . . . . . . . . . 32 Customizing the settings of CM Analyzer . . . . . . . . . . . . . . . . . . . . . . . 33 Enabling parameter level audit logging . . . . . . . . . . . . . . . . . . . . . . . . . 33 Enabling provisioning audit logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Enabling automatic upload audit logging . . . . . . . . . . . . . . . . . . . . . . . . 34 Hiding Administrator operations from CM Operations Manager Operation History view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Id:0900d80580a02f7a

17 17 17 18 19 20 24 24 24 25 26 26 27

3


7.6 7.7

7.12

Customizing the settings of a folder object . . . . . . . . . . . . . . . . . . . . . . . 35 Enabling Inter-RAT UTRAN and Inter-RAT GERAN features auto management in Plan Prepare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Handling critical parameters in NetAct Configurator . . . . . . . . . . . . . . . . 36 Defining the maximum number of managed objects in one validation file for LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Defining the number of waiting operations per BSC, RNC and LTE OMS . 38 Enabling skipping BTS, Flexi Direct and/or LTE validation before pre-activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Enabling validation files saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

8 8.1 8.2 8.3 8.4 8.5

Managing the software version and options support . . . . . . . . . . . . . . . 40 Setting the RNC version and options . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Setting the MSC options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Setting the MGW options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Setting the SGSN options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Setting the BSC version and options . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

9

Maintaining the NetAct Configurator database using the NetAct Doctor 44

10

NetAct Parameter-based Licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

11 11.1 11.2 11.3 11.3.1 11.3.1.1 11.3.1.2 11.3.1.3 11.3.1.4 11.3.2 11.3.2.1 11.3.2.2

Command line operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Scheduling command line operations . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Uploading actual values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Provisioning plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Validating BTS SC plan before pre-activation. . . . . . . . . . . . . . . . . . . . . 51 Validating BSC RNW plan after pre-activation . . . . . . . . . . . . . . . . . . . . 52 Pre-activating and activating GSM plan . . . . . . . . . . . . . . . . . . . . . . . . . 52 Activating the pre-activated GSM plan . . . . . . . . . . . . . . . . . . . . . . . . . . 54 WCDMA, Flexi Direct, LTE, and core . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Validating WBTS SC and LTE plans before pre-activation . . . . . . . . . . . 55 Pre-activating and activating plans for RNC RNW, RNC ATM/IP, AXC, FTM, Flexi Direct, WBTS SC, core and LTE. . . . . . . . . . . . . . . . . . . . . . 56 Validating RNC ATM/IP plan content after pre-activation . . . . . . . . . . . . 59 Activating the pre-activated plan for RNC RNW, AXC, FTM, Flexi Direct, WBTS SC and LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Activating the pre-activated RNC ATM/IP plan . . . . . . . . . . . . . . . . . . . . 61 Exporting and importing plans, actual configuration and templates . . . . 62 Deleting plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Comparing plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Comparing plans to actual configuration. . . . . . . . . . . . . . . . . . . . . . . . . 67 Send To Network operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Policy-Based Compare operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Reference Configuration related command line operations . . . . . . . . . . 69 Initializing Reference Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Generating delta . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Exporting delta . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

7.8 7.9 7.10 7.11

11.3.2.3 11.3.2.4 11.3.2.5 11.4 11.5 11.6 11.6.1 11.7 11.8 11.9 11.9.1 11.9.2 11.9.3

4

Id:0900d80580a02f7a

DN03453584 Issue 1-0


11.9.4 11.9.5 11.9.6 11.10 11.10.1 11.10.2 11.10.3 11.10.4 11.11 11.11.1 11.11.1.1 11.11.1.2 11.11.1.3 11.11.1.4

11.17 11.18 11.19 11.20 11.20.1 11.21

Merging plans to reference configuration. . . . . . . . . . . . . . . . . . . . . . . . 71 Committing reference alignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Committing network alignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 CM History related command line operations . . . . . . . . . . . . . . . . . . . . 72 Initializing CM History configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Synchronizing CM History configuration . . . . . . . . . . . . . . . . . . . . . . . . 73 Generating CM History differences tabular report . . . . . . . . . . . . . . . . . 73 Removing data from CM History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Workflow related command line operations . . . . . . . . . . . . . . . . . . . . . . 75 Creating workflow related plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Creating a plan based on COCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Creating a new COCO reconfiguration plan . . . . . . . . . . . . . . . . . . . . . 76 Creating a new transport reconfiguration plan . . . . . . . . . . . . . . . . . . . . 76 Merging into selected modification plan the related _CocoAxcFtmPlan and _CocoDeletion plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Provisioning workflow related plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Provisioning a plan generated from a COCO modification plan with the suffix _CocoAxcFtmPlan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Provisioning in AXCs and FTMs the plan with the suffix _CocoAxcFtmPlan 78 Provisioning a plan with the suffix _CocoDeletion in RNCs. . . . . . . . . . 79 Provisioning a selected plan in RNCs . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Starting consistency checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 3GPP operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Restoring AXC configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Managing the Remote Electrical Tilt using command line . . . . . . . . . . . 85 Command Line operations for RET management in WCDMA network . 85 Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Forced Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Download vendor specific configuration file. . . . . . . . . . . . . . . . . . . . . . 86 Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Command Line operations for RET management in LTE network . . . . 87 Upload (with Command Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Download (with Command Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Administering RNC RNW and LTE iOMS queues . . . . . . . . . . . . . . . . . 87 Pausing/releasing an RNC RNW and LTE iOMS operation queue . . . . 88 Provisioning a priority plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Removing a hanging operation from the RNC RNW or LTE iOMS operation queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Command Manager command line operations . . . . . . . . . . . . . . . . . . . 90 Zero touch BTS configuration command line operations . . . . . . . . . . . . 91 BTS Configuration File Export command line operations . . . . . . . . . . . 92 Plan provisioning to multiple core NEs . . . . . . . . . . . . . . . . . . . . . . . . . 93 Plan provisioning to multiple NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 eNB Cell Trace Restart command line operations. . . . . . . . . . . . . . . . . 94

12

Where to find more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

11.11.2 11.11.2.1 11.11.2.2 11.11.2.3 11.11.2.4 11.12 11.13 11.14 11.15 11.15.1 11.15.1.1 11.15.1.2 11.15.1.3 11.15.1.4 11.15.1.5 11.15.2 11.15.2.1 11.15.2.2 11.16 11.16.1 11.16.2 11.16.3

DN03453584 Issue 1-0

Id:0900d80580a02f7a

5


13

Appendix A: Parameters related to features under parameter-based license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

6

Id:0900d80580a02f7a

DN03453584 Issue 1-0


List of Figures Figure 1 Figure 2

DN03453584 Issue 1-0

Overview of configuring the DDNS proxy for NetAct Configurator DNS management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Overview of the operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Id:0900d80580a02f7a

7


List of Tables Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 Table 25 Table 26 Table 27 Table 28 Table 29 Table 30 Table 31 Table 32 Table 33 Table 34 Table 35 Table 36 Table 37 Table 38 Table 39

8

Environment variables used in this document . . . . . . . . . . . . . . . . . . . . 10 Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Command line options for Q3 Version Manager usage . . . . . . . . . . . . . 14 Options for the Primary Name Server in Network Editor . . . . . . . . . . . . 19 Value definitions for the preferHiddenPrimary attribute . . . . . . . . . . . . . 19 Variable list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Variable list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Variable list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 q3versmx command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Command line options for upload operations . . . . . . . . . . . . . . . . . . . . 47 Command line options for validating BTS SC plan. . . . . . . . . . . . . . . . . 51 Command line options for validating BSC RNW plan. . . . . . . . . . . . . . . 52 Command line options for provisioning . . . . . . . . . . . . . . . . . . . . . . . . . 53 Command line options for the Activate_Pre-Activation operations . . . . 54 Command line options for validating plan content . . . . . . . . . . . . . . . . . 56 Command line options for plan provisioning . . . . . . . . . . . . . . . . . . . . . 56 Command line options for the IPA_Validation operation . . . . . . . . . . . . 59 Command line options for activating the pre-activated plan . . . . . . . . . 60 Command line options for the IPA_Activation operations . . . . . . . . . . . 61 Command line options for the export and import operations . . . . . . . . . 63 Command line options for the plan delete operations . . . . . . . . . . . . . . 66 Command line options for the compare operations . . . . . . . . . . . . . . . . 67 Command line options for Send To Network operations . . . . . . . . . . . . 68 Command line options for running Policy-Based compare operation . . 68 Command line options for initializing Reference Configuration . . . . . . . 70 Command line options for generating delta . . . . . . . . . . . . . . . . . . . . . . 70 Command line options for exporting delta . . . . . . . . . . . . . . . . . . . . . . . 71 Command line options for merging plans to reference configuration . . . 71 Command line options for committing reference alignments . . . . . . . . . 72 Command line options for committing network alignments . . . . . . . . . . 72 Command line options for initializing CM History configuration . . . . . . . 72 Command line options for synchronizing CM History configuration with actual configuration or reference configuration . . . . . . . . . . . . . . . . . . . . . 73 Command line options for generating the CM History differences tabular report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Command line options for removing irrelevant data from CM History database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Workflow related command line operations for creating a plan based on COCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Workflow related command line operations for creating a new COCO? reconfiguration plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Workflow related command line operations for creating a new transport reconfiguration plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Workflow related command line operations for merging into selected modification plan the related _COCOdeletion plan . . . . . . . . . . . . . . . . . . . . 77 Workflow related command line operations for merging into selected modification plan with the suffix _CocoAxcFtmPlan . . . . . . . . . . . . . . . . . . . 77

Id:0900d80580a02f7a

DN03453584 Issue 1-0


Table 40 Table 41 Table 42 Table 43 Table 44 Table 45 Table 46 Table 47 Table 48 Table 49 Table 50 Table 51 Table 52 Table 53 Table 54 Table 55 Table 56

DN03453584 Issue 1-0

Workflow related command line operations for provisioning in AXCs and FTMs the plan with the suffix _CocoAxcFtmPlan . . . . . . . . . . . . . . . . . 78 Workflow related command line operations for provisioning the plan with the suffix _CocoDeletion in RNCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Workflow related command line operations for provisioning selected plan in RNCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Command line options for consistency checking . . . . . . . . . . . . . . . . . 80 Command line options for 3GPP upload . . . . . . . . . . . . . . . . . . . . . . . . 83 Command line options for 3GPP download . . . . . . . . . . . . . . . . . . . . . 83 Command line options for restoring AXC configurations . . . . . . . . . . . 84 Command line options for Binary Download operation . . . . . . . . . . . . . 86 Command line options for Calibration operation . . . . . . . . . . . . . . . . . . 86 Command line options for pausing/releasing RNC RNW and iOMS operation queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Command line options for removing hanging operation from RNC RNW and iOMS operation queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Command line options for executing Command Manager operations . 90 Command line options for executing zero touch BTS configuration operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Command line options for executing the BTS SEM Export operations . 93 Command line options for plan provisioning to multiple NEs . . . . . . . . 93 eNB Cell Trace Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Parameters related to features under parameter-based license . . . . . . 99

Id:0900d80580a02f7a

9

About this document


1 About this document Administering NetAct Configurator is an administer document that covers various technical aspects of Nokia Siemens Networks NetAct Configurator, such as command line operations and administrator’s tasks. This document describes the procedures for administering Configurator. It is not intended to be used as a stand-alone guide, but to complement other NetAct documents.

1.1

Environment variables This document assumes the values of the environment variables as indicated in the following table:

Variable

Value

$ETCROOT

/etc/opt/nokia/oss

$PRODUCTROOT

/opt/nokia/oss

$VARROOT

/var/opt/nokia/oss

$OMCLOGDIR

/var/opt/nokia/oss/local/common/log

Table 1

Environment variables used in this document

1.2

NetAct compatibility and capacity information For information on the NetAct system and capacity, and the compatibility between NetAct and network element releases, see the NetAct Compatibility and Capacity Information document.

1.3

Terms Term

Explanation

BIND

Berkeley Internet Name Domain. DNS software running on Linux.

BSC

Base Station Controller

CS

Connectivity Server

DDNS

Dynamic Domain Name System

DNS

Domain Name Server

DS

Data Server

GUIS

Graphical User Interface Server

LDAP

Lightweight Directory Access Protocol A protocol for accessing directory information.

LinAS

Linux Application Server

MSC

DX MSC

Table 2

10

Terms

Id:0900d80580a02f79

DN03453584 Issue 1-0


Term

Explanation

NameSurfer

Distributed administration tool with a web-based graphical user interface for domain name system data.

NS

Name Server

RNC

Radio Network Controller

SGSN

Serving GPRS Support Node

SC

Site Configuration

Table 2

DN03453584 Issue 1-0

About this document

Terms (Cont.)

Id:0900d80580a02f79

11

Configuring BSC file-based upload, provisioning, and events


2 Configuring BSC file-based upload, provisioning, and events This chapter gives instructions for configuring the BSC file-based upload and provisioning feature with the FTAM file transfer service and configuring BSC XML file-based events.

2.1

Checking and configuring user accounts for FTAM Unix Access service type The following check is required before BSC file-based upload and provisioning can be used with the FTAM file transfer service. Check the default FTAM Unix Access service type user in NetAct by using the following instructions: To check the default FTAM Unix Access service type user in NetAct 1. Start the Service User Management application. For more information about this application, see Service User Management Help. 2. Select the service type as FTAM Unix Access. 3. Select the maintenance region which contains workstation objects (WS) for the NetAct cluster. The existing configured maintenance region service users for FTAM Unix Access service type are displayed in the bottom panel of the application window. The user name has a maximum length of eight characters. If the existing configured FTAM Unix Access service type user has a name longer than eight characters, it must be replaced with a new user account with a shorter user name before NetAct Configurator BSC file-based upload and provisioning features with FTAM can be used. To change the default FTAM Unix Access service type user in NetAct 1. Create a new user account user name (maximum length eight characters) and password (maximum length 15 characters) using the NetAct Account Manager application. See Creating users in Managing Users for instructions on creating new user accounts. 2. The new user account must be added to the sysop group using the NetAct Permission Manager application. See Adding users to groups in NetAct Permission Manager Help for more information. 3. Create a new maintenance region service user for FTAM Unix Access service type using the Service User Management application. You must create this user in the maintenance region which includes the NetAct cluster workstation objects (WS) and you must have the same user name and password as the NetAct user account created in step 1. See Creating a maintenance region service user in Service User Management Help for more information. 4. Disconnect the NetAct user group sysop from the old existing maintenance region (MR) service user for FTAM Unix Access service type for the maintenance region containing NetAct cluster workstation objects (WS). See Disconnecting a user group from a maintenance region service user in Service User Management Help for more information.

12

Id:0900d80580a02f79

DN03453584 Issue 1-0



5. Connect the NetAct user group sysop to the new MR service user for FTAM Unix Access service type. See Connecting a user group to a maintenance region service user in Service User Management Help for more information.

2.2

Enabling Node Manager launch functionality To enable the NetAct Node Manager launch functionality, ensure that the following configuration changes have been done. The sobriquet information needs to be present in the NetAct topology database. Updates need to be done with NetAct Doctor tool after BSCs have been uploaded to Configurator. To update sobriquet information for all BSC objects currently present in the Configurator database, enter the following command as the omc user: [omc]$ /opt/oss/bin/doctormx.sh -case --run CMSobriquets Run this command when new TRE, DMR, DN2 or BSTE objects have been created for BSCs that are uploaded with file-based upload. The command can be configured to run automatically at scheduled times. For more information about the NetAct Doctor cases, see Troubleshooting Configuration Management Problems document. For NetAct Node Manager services, see Node Manager Administration Principles and Installing and Configuring Node Managers.

2.3

Configuring BSC file-based events BSC Q3 events are not anymore supported, therefore all BSCs have to be configured to send XML file-based events. The enabling/disabling and configuration management of the XML file-based events handling in the BSC is possible by using Q3 Version Manager (q3versmx).

g

Because Q3 events are not anymore supported, switching from XML based events to the Q3 based events is needed only in the following special cases: •

•

Resetting / modifying XML event parameters using q3versmx - this can be done only in the Q3 events mode. After modifying these parameters XML based events have to be switched on again. For troubleshooting purposes. For details, see section Solving problems with the XML-based events and core files generated by the zrnevhmx process.

It is strongly recommended to configure file-based events to use FTP when ever possible. File-based events over FTAM may cause OSI stack overload and severely slow down all Q3 traffic between BSC and NetAct.

g

Only the omc user is allowed to perform enabling/disabling and configuration management of the XML file-based events. Q3 Version Manager command line structure and options are listed below:

q3versmx [-allbscs] [-bscid ] [-bscintid ] -XMLevents | -Q3events [-dir ] [-compthr ] [-eventcoltime ] [-ip:port [:]] -user -pass

DN03453584 Issue 1-0

Id:0900d80580a02f79

13



Option

Description

-allbscs

Activate/deactivate XML file-based events to all BSCs.

-bscid

C-number of BSC. Activate/deactivate XML file-based events to this BSC only.

-bscintid

Internal ID of BSC. Activate/deactivate XML file-based events to this BSC only.

-XMLevents

This option activates XML event file sending.

-Q3events

This option deactivates the XML event file sending and activates Q3 event sending. This option is mutually exclusive with the -XMLevents option. BSC Q3 events are not anymore supported, therefore switching to the Q3 based events is needed only in the following special cases:

• •

Resetting / modifying XML event parameters using q3versmx - this can be done only in the Q3 events mode. After modifying these parameters XML based events have to be switched on again. For troubleshooting purposes. For details, see section Solving problems with the XML-based events and core files generated by the zrnevhmx process.

The root path in NetAct where the folder for the events will be stored. By default the value is fetched from the configuration file at the location /opt/nokia/oss/conf/zrnconcmplamx.cf.

-dir

This option can be used only for testing purposes. The size of the event (in Kbytes) above which the compression starts. If the size of the event is bigger, it will be compressed in the BSC.

-compthr

Specific values:

• •

0 - Always compression 2147483647 - No compression

If this option is not used, the Q3 Version Manager will send as uncompressed to BSC. eventcolti me

Event Collection Time range is 5-120 seconds. It affects only the events ending time of File Based Plan Provisioning. Events are being sent immediately, if change is made with MML or Send to Network in CM Editor.

-ip:port

The IP address and port of the FTP server to be used, from NetAct. IP address of rac package should be used. If this option is not used, the Q3 Version Manager will set the connection type to FTAM.

-user

The access user name from NetAct.

-pass

The access password from NetAct.

Table 3

Command line options for Q3 Version Manager usage

g

XML event can be configured to use either FTP or FTAM. In case of FTP the ftpuse user should be used and in case of FTAM the trafadmi user should be used. Example: To set XMLevents to FTP mode (when the value for ip:port is given it will be configured in FTP mode), enter the following command:

q3versmx –bscid 1234 –XMLevents –ip:port 10.125.97.51:21 –user ftpuse –pass useftp The expected result is that BSC-1234 will send XML file-based events to the directory mentioned in the zrnconcmplamx.cf file using the FTP server with no compression.

14

Id:0900d80580a02f79

DN03453584 Issue 1-0



Example: To set XMLevents to FTAM mode (when the value for ip:port is not given it will be configured in FTAM mode), enter the following command: q3versmx –bscid 1234 –XMLevents –user trafadmi –pass allpassw Example: To send the XMLevents for a collection time of 30sec, use the following command: q3versmx -bscid 253972 -XMLevents -eventcoltime 30 -ip:port 10.9.222.18:21 -user ftpuse -pass Useftp12 -trace

2.3.1

Solving problems with the XML-based events and core files generated by the zrnevhmx process A lot of core dump files might be generated by the zrnevhmx process when the CM events flow via Q3-event pipe is in use instead of XML-event pipe for BSC S15 and S14 network elements. Q3 event pipe is not supported for S15 and S14 BSC network elements, therefore switch on the XML-event pipe into use using the following procedure: 1. Switch on the XML-events back into use with the following command: q3versmx –bscid -XMLevents –ip:port :21 -user ftpuse -pass 2. In case core dump files are still generated, switch on the Q3-event pipe into use for a moment with the following command: q3versmx -bscid -Q3events and immediately after that switch on the XML-events back into use with the following command: q3versmx –bscid -XMLevents –ip:port :21 -user ftpuse -pass

DN03453584 Issue 1-0

Id:0900d80580a02f79

15

Configuring HTTP file transfer for RNC and WBTS


3 Configuring HTTP file transfer for RNC and WBTS 3.1

Checking and configuring user accounts for HTTPS Unix Access service type The following check is required in NetAct Configurator before RNC RN4.0 and WBTS WN5.0 CM upload and provisioning can be used with the HTTP file transfer service. The HTTPS Unix Access service type is also needed for HTTP file transfer since both HTTP and HTTPS file transfer are using the same service type. Check the default HTTPS Unix Access service type user in NetAct by using the following instructions: To check the default HTTPS Unix Access service type user in NetAct 1. Start the Service User Management application. For more information about the application, see Service User Management Help. 2. Select the HTTPS Unix Access from the Service Type drop-down list on the right side of the application window. 3. From the Maintenance Region list, on the left side of the application window, select the maintenance region which contains workstation objects (WS) for the NetAct cluster. Expected outcome: The existing configured maintenance region service users for HTTPS Unix Access service type are displayed in the MR Service Users list at the bottom of the application window. 4. Click the Connect button in the toolbar. Expected output: The Connection Between a User Group and a Maintenance Region Service User dialog opens. 5. From the Maintenance Regions list in the Scope pane select the Maintenance Region which contains workstations and check that NetAct user group of the user used for CM upload and provisioning is connected to the service user for HTTPS Unix Access service type.

16

Id:0900d80580a02f79

DN03453584 Issue 1-0


Configuring NetAct Configurator DNS management

4 Configuring NetAct Configurator DNS management This chapter gives instructions for configuring the DDNS (Dynamic Domain Name System) proxy settings and DNS to facilitate communication between NetAct Configurator DNS management and the DNS. With Configurator DNS management, you can manage the IP address of the Routing Area in the DNS. The DDNS proxy acts as the interface between the DNS and Configurator DNS management. It uses the DDNS protocol for communication with the DNS. This protocol is an extension made to the DNS protocol to support dynamic names.

4.1

Prerequisites To ensure that NetAct Configurator DNS management works properly, the following prerequisites must be met: •

•

•

• •

4.2

The DNS has been configured correctly (that is, names have been resolved and zones have been found). For more information, see the document Managing the DNS in NetAct. The Primary Name Server has been configured and the necessary UNIX users have been created, with the rights to access the DDNS proxy. For more information on the required steps, see section Overview of the operation. Routing Area Object(s) for BSC exists in the database. You can check this, as well as create new Routing Area objects, using CM Editor. For more information, see Creating new managed objects in the network in CM Editor Help. The Packet Core integration has been done. An IP address has been defined for the Routing Area Object for the BSC (the IP address can also be empty, if not yet defined). The IP address is defined with CM Editor.

Overview of the operation The following figure gives an overview of the steps for configuring NetAct Configurator DNS management. Click a process in the figure for more information.

DN03453584 Issue 1-0

Id:0900d80580a02f79

17



Start

Configure the Primary Name Server

Configure the p3nprxmx DDNS Proxy process

Create the DDNS access service user

Assign the DDNS_ACCESS service type to the user

Grant the DDNS access to the user

Configure LDAP for Configurator DNS management

End

Figure 1

4.3

Overview of configuring the DDNS proxy for NetAct Configurator DNS management

Configuring the Primary Name Server To configure the Primary Name Server 1. Go to NetAct Start: /netact/>. 2. Log in as the omc user. 3. Start Network Editor either from Application Manager or from NetAct Start. 4. In Network Editor, search for the Name Server (NS) object for the Primary Name Server to see if it already exists in the PLMN/NS hierarchy. If the NS object does not exist, create it as instructed in Step 5. 5. Create the NS object to the PLMN/NS hierarchy. Use a Network Editor view where the Workstation (WS) object is present.

18

Id:0900d80580a02f79

DN03453584 Issue 1-0



6. Get the IP address of the Primary Name Server from the /etc/resolv.conf file. Use this IP address only when creating the NS object. Create the NS under the same maintenance region where the WS object is present. 7. Use the following values for the NE Type, IP and Hostname parameters: Field

Value

NE Type

DNS

IP

The IP address of the Primary Server for the DNS.

Hostname

If the Hostname is given instead of IP address, it should be one of the following servers:

• • • • Name

Table 4

g 4.4

osscore package of this cluster if NameSurfer is the DNS primary the server’s own IP if BIND is the DNS primary the IP address of your site’s DNS server another cluster’s osscore package IP address or server name.

The WS names must be unique under the same MR.

Options for the Primary Name Server in Network Editor

Make sure the Foreign Object check box is not selected. 8. Save the view and exit Network Editor.

Configuring the p3nprxmx DDNS Proxy process To configure the p3nprxmx DDNS Proxy process 1. Log in to the CS server as the omc user. 2. Copy p3nprxmxm.cf from /etc/opt/nokia/oss/dns/conf/ to /etc/opt/nokia/oss/custom/conf directory. 3. Open /etc/opt/nokia/oss/custom/conf/p3nprxmx.cf for editing. 4. Set the preferHiddenPrimary attribute according to the following table. Value

Description

true

Set if NameSurfer Hidden Primary DNS solution is in use in NetAct.

false

Set if BIND primary DNS solution is in use in NetAct

Table 5

Value definitions for the preferHiddenPrimary attribute

Example of the preferHiddenPrimary setup in the p3nprxmxm.cf file: (processOptions "p3nprxmx.cf" ... # Define if Hidden Primary should be preferred (true/false) (p3nprxmx "" (preferHiddenPrimary "false") )

DN03453584 Issue 1-0

Id:0900d80580a02f79

19



) 5. Save and close the file. 6. Check the PID for the p3nprxmx process and kill it with PID. Use the following commands: root% ps -ef | grep p3nprxmx root% kill -USR2

g

You need to wait until wpmana re-starts the process, since the p3nprxmx process is under wpmana supervision. You can use the ps -ef | grep p3nprxmx command again to check if the process is running. 7. Logout from the system.

4.5

Creating and configuring the DDNS access The DDNS access service user is a user who has access to write to the DDNS proxy. To check if this user already exists, look for the DDNS proxy user name from LDAP. See section Configuring LDAP for NetAct Configurator for more information. If the user does not exist, create it as instructed below. To create the DDNS access 1. Start the NetAct Account Manager application to create the DDNS access service user and assign a password to it. For instructions, see Creating users and Managing passwords in Managing Users.

g

The default user name for the DDNS access service user is ddnsuser, but it can be changed. The password is not related to other NetAct passwords, so it can be set freely. When creating users, reconciliation may be required to synchronize the account information between the NetAct Account Manager and the target repositories. For instructions, see Reconciling user account information in Managing Users. 2. Assign the created user to the dnsusr group. • •

If this group already exists, follow the instructions in Modifying users’ primary group for POSIX account in Managing Users. If this group does not exist, create it by using NetAct Permission Manager and use dnsusr as the name of the group. See the instructions in Creating groups in NetAct Permission Manager Help.

3. Make sure that the dnsusr group, whether an existing or a newly created one, has the DDNS_ACCESS.Query permission.

g

Network Administrator role has the DDNS_ACCESS.Query permission. These can be checked in NetAct Permission Manager. For more information, see Managing permissions in Managing Users. 4. To enable the newly created user to access NetAct Configurator DNS management and other NetAct applications, grant the necessary rights with the User Group Profiles application. Add all the necessary views and profiles that are needed for the

20

Id:0900d80580a02f79

DN03453584 Issue 1-0



Rehosting operation. For instructions, see Managing views/profiles in User Group Profiles Help. To assign the DDNS_ACCESS service type to the user After the user has been created, the DDNS_ACCESS service type needs to be assigned to it. To do it, perform the following steps: 1. Log in as the omc user. 2. Enter the following command: [omc]$

nuptummx -add DDNS_ACCESS -user -password

the user name created in NetAct Account Manager; for example, ddnsuser

the password assigned in NetAct Permission Manager for example, Omc0mc123

Table 6

g

Variable list

The user name ddnsuser is the default user name, and it is also mentioned in the LDAP. If a different user name is given, remember to modify the value of the DDNS proxy user name in LDAP. To grant the DDNS access to the user Next, configure the Name Server so that it is accessible for the user created in NetAct Account Manager (for example, ddnsuser). The necessary zones must be modified in the /etc/named.conf file. From NetAct Configurator DNS management’s point of view, the zone string has the following format: mncxxxx.mccxxxx.gprs, where xxxx represents the hexadecimal values of MNC and MCC parameters of the Routing Area object. The length of the converted hexadecimal value of MNC and MCC parameters should be 4.

t

For example, if the MNC parameter value is 003 and the MCC parameter value is 106 for the RA object, the zone for which Configurator DNS management looks into the Name Server is mnc0003.mcc0106.gprs. A key file is required to edit your zone files. It has to contain the same key as defined in the /etc/named.conf file. If you are modifying the key or creating it for the first time, generate the key file on the server. Also see section Controlling access to BIND DNS data and Controlling access to NameSurfer DNS data in the Managing the DNS in NetAct document for more information. 1. Log in to the Connectivity Server as the root user and enter the following command:

root% /opt/nokia/oss/bin/p3nkeymx.pl \ -f

Table 7

DN03453584 Issue 1-0

the user name assigned in NetAct Account Manager, for example, ddnsuser

Variable list

Id:0900d80580a02f79

21



the password assigned in NetAct Permission Manager, for example, Omc0mc123

the IP of your Primary Name Server for example, 10.8.65.4

Table 7

Variable list (Cont.)

As output, you are given the shared secret and the key file is generated. For example: root% /opt/nokia/oss/bin/p3nkeymx.pl -f \ ddnsuser Omc0mc123 10.8.65.4 Shared secret in Base64 format (BIND and NameSurfer): ddnsuser 2bvUxmG1H1qt97Us6Xktuw== root% 2. Enter the shared secret as follows: For BIND a. The shared secret key must be entered to the server where the primary DNS is running. Enter the shared secret for BIND in the /etc/named.conf file under key definition. Also add the values for the Routing Area object under zone definition, as shown below: key ddnsuser. { algorithm hmac-md5; secret "2bvUxmG1H1qt97Us6XKtuw=="; }; zone "mnc0003.mcc0106.gprs" { type master; file "db.mnc0003.mcc0106.gprs"; allow-update { key ddnsuser. ;}; };

g

The allow-update { key ddnsuser. ;}; needs to be added in every zone of the/etc/named.conf file that is managed with Configurator tool. b. Update the /etc/named.conf file in all secondary DNS servers as shown below: zone "mnc0003.mcc0106.gprs" { type slave; file "db.mnc0003.mcc0106.gprs"; masters { 10.8.65.4 ; } ; }; c. Make sure that the file db.mnc0003.mcc0106.gprs exists in/var/named directory in the Primary Name Server. Also check that the file db.mnc0003.mcc0106.gprs has the entry of Primary Name Server (tehi.netact.noklab.net) as shown below:

$ORIGIN . $TTL 3600 ; 1 hour mnc0003.mcc0106.gprs

IN SOA

root.tehi.netact.noklab.net.

(

22

tehi.netact.noklab.net.

Id:0900d80580a02f79

DN03453584 Issue 1-0



2005092101 ; serial 28800

; refresh (8 hours)

3600

; minimum (1 hour)

1200

; retry (20 minutes)

604800 ; expire (1 week) 3600

; minimum (1 hour)

) NS

ohio.netact.noklab.net.

NS

tehi.netact.noklab.net.

d. Restart BIND name server with the following command: #

service named

restart

For NameSurfer a. Configure the primary NaSu Name Server with the following steps: 1. Open NameSurfer GUI in the primary Name Server. 2. Select Transaction keys from the left side menu. 3. Select the key you are about to modify, or select HMAC-MD5 from the left side menu when you are adding a new key. 4. Type the key name when adding new and modify the key information: copy the key string that was generated in step 1 of the procedure to Key secret part field. 5. Select Can be used for Dynamic DNS updates check box. 6. After modifications click OK and press Continue Submission in the appearing Security warning box. Log in to the primary Name Server as the root user and insert the shared secret key to the bottom row of the file /opt/namesurfer/config/secrets behind the user name. Syntax: localhost d429ff3a8bc88d3345ef399a66b33c57 dchp.server 1ef399ab33c5766429ff3a8bc88d3345 For example: localhost d429ff3a8bc88d3345ef399a66b33c57 dchp.server 1ef399ab33c5766429ff3a8bc88d3345 ddnsuser 2bvUxmG1H1qt97Us6XKtuw== b. Configure the secondary Name Servers as slaves. The only difference is that a slave to NameSurfer also has a port specification (8054) in every masters statement as it is not using the default port 53. The following is an example of the content of the /etc/named.conf file:

DN03453584 Issue 1-0

Id:0900d80580a02f79

23



options { directory "/var/named"; //running directory for named } ; zone "mnc0003.mcc0106.grs" { type slave; file " db.mnc0003.mcc0106.gprs"; masters port 8054 {10.8.65.4;}; }; c. Restart NameSurfer with the following command: root# hamgrmx.pl start package dns

4.6

Configuring LDAP for NetAct Configurator DNS management Prerequisites It is important to ensure that the DNS has been configured and is working correctly, for example names have been resolved, zones have been found by the application and Packet Core integration has already been done. Users The DDNSProxyUserName is inserted into the LDAP ossRacDNSManagerDDNSProxyUserName field. Example: ossRacDNSManagerDDNSProxyUserName = ddnsuser ossRacDNSManagerDDNSProxyUserName = NokiaOSS.local.services.subsystems.dnsirp.GenericServiceHome.

g

The user group must have DDNS_ACCESS.Query operations defined for its role.

4.7

Configuring DNS management for the rehosting operation

For more information on how to modify Configurator LDAP parameters, see section Configuring LDAP for NetAct Configurator.

This section describes configuring DNS management for the rehosting operation.

4.7.1

Overview of the operation The following figure gives an overview of the steps for configuring DNS management for the rehosting operation. Click a process in the figure for more information.

24

Id:0900d80580a02f79

DN03453584 Issue 1-0



Start

Create shared secret key

Add ran zone to LDAP

BIND Allow TSIG key signed Dynamic DNS update

NameSurfer

BIND/NameSurfer ?

Restart BIND process

Restart NameSurfer

Run rehost operation

Run rehost operation

Clean up DNS setups Figure 2

4.7.2

Allow TSIG key signed Dynamic DNS update

End

Overview of the operation

Creating shared secret key A key file is required to edit your zone files. It has to contain the same key as defined in the /etc/named.conf file. If you are modifying the key or creating it for the first time, generate the key file on the server. To create shared secret key 1. Log in to the Connectivity Server as the root user. 2. Execute the following command:

# /opt/nokia/oss/bin/p3nkaymx.pl \ -f

DN03453584 Issue 1-0

Id:0900d80580a02f79

25



Variable

Description

The user name assigned in NetAct Account Manager, for example, ddnsuser.

The password assigned in NetAct Permission Manager, for example, OmcOmc 123.

The IP of your Primary Name Server, for example, 10.8.65.4.

Table 8

Variable list

As an output, you are given the shared secret and the key file is generated. For example: root% /opt/nokia/oss/bin/p3nkeymx.pl -f \ ddnsuser OmcOmc123 10.8.65.4 Shared secret in Base64 format (BIND and NameSurfer): ddnsuser 2bvUxmG1H1qt97Us6Xktuw== root%

4.7.3

Adding RAN zone name to LDAP To add zone name to LDAP 1. Insert the zone name into the LDAP ossRacDefaultRANDomainSuffix field. For example: ossRacDefaultRANDomainSuffix = ran.netact.noklab.net

4.7.4

Configuring BIND To configure BIND 1. Allow TSIG key signed Dynamic DNS update The shared secret key must be entered to the server where the primary DNS is running. Enter the shared secret for BIND to the /etc/named.conf file under key statement. Also add allow-update {;} rows for the under zone definition, as shown below: key ddnsuser. { algorithm hmac-md5; secret " 2bvUxmG1H1qt97Us6XKtuw=="; } ; zone "ran.netact.noklab.net" { type master; file "db.ran.netact.noklab.net"; allow-update { key ddnsuser. ; } ; } ;

g 26

If RAN zone is added to master DNS server, then update the /etc/named.conf file in all slave DNS servers as shown below:

Id:0900d80580a02f79

DN03453584 Issue 1-0



zone "ran.netact.noklab.net" { type slave; file "db.ran.netact.noklab.net"; masters { 10.8.65.4; }; } ; 2. Restart BIND To restart BIND Name Server execute the following command: omc% service named restart 3. Run rehost operation DNS update can be run successfully only if the allow-update row is modified. If the IP is changed, each WBTS IP address needs to be changed manually with Network Editor. 4. Clean up the DNS setups To clean up the DNS setups: 1. Clear all created DNS setups by removing all allow-update { ; } rows. Example of the zone statement: zone "" { ... allow-update { ; } ; ... } ; 2. Restart BIND Name Server process by executing the following command: root% rndc reload

4.7.5

Configuring NameSurfer To configure NameSurfer 1. Allow TSIG key signed Dynamic DNS update 1. Configure the Primary NaSu Name Server with the following steps: a) Open NameSurfer GUI in the Primary Name Server. b) Select Transaction keys from the left side menu. c) Select the key you are about to modify, or select HMAC-MD5 from the left side menu when you are adding a new key. d) Type the key name when adding a new key and modify the key information. Copy the key string generated in section Creating shared secret key to the Key secret part field. e) Select Can be used for Dynamic DNS updates check box. f) Click OK after modifications and press Continue Submission in the appearing Security warning box. g) Log in to the Primary Name Server as the root user and insert the shared secret key to the bottom row of the /opt/namesurfer/config/secrets file behind the user name. Syntax:

DN03453584 Issue 1-0

Id:0900d80580a02f79

27



localhost d429ff3a8bc88d3345ef399a66b33c57 dchp.server 1ef399ab33c5766429ff3a8bc88d3345 For example: localhost d429ff3a8bc88d3345ef399a66b33c57 dchp.server 1ef399ab33c5766429ff3a8bc88d3345 ddnsuser 2bvUxmG1H1qt97Us6XKtuw== 2. Configure the Secondary Name Servers as slaves. The only difference is that a slave to NameSurfer also has a port specification (8054) in every masters statement as it is not using the default port. The following is an example of the content of the/etc/named.conf file: options { directory "/var/named"; // running directory for named } ; zone "mnc0003.mcc0106. grs" { type slave; file " db.mnc0003.mcc0106.gprs"; masters port 8054 {10.8.65.4;}; }; 2. Restart NameSurfer To restart NameSurfer, execute the following command: root# hamgrmx.pl start package dns 3. Run rehost operation If the IP is changed, each WBTS IP address needs to be changed manually with Network Editor.

28

Id:0900d80580a02f79

DN03453584 Issue 1-0


Configuring LDAP for NetAct Configurator

5 Configuring LDAP for NetAct Configurator NetAct uses LDAP (Lightweight Directory Access Protocol) for centralizing configuration data. The directory resides mainly in the Linux servers but there are also LDAP subsystems on the LinAS and GUIS servers. For general information about the LDAP directory, see LDAP directory management in System Administration Principles. The {basedn} is the default path included in the Jxplorer. Initial LDAP configurations for NetAct Configurator are made during commissioning. The locations for the Configurator parameters in the LDAP directory are: • •

{basedn} → netact → regions → region-{id} → config → scconfig → rac for the racapplications object {basedn} → scconfig → rac for the racadaptations object.

The LDAP directory and Configurator-specific parameters can be modified using the JXplorer tool. For more information on the JXplorer tool see System platform user interface applications in System Platform Technical Reference Guide. For detailed information on Configurator LDAP parameters, see NetAct Configurator LDAP parameters in NetAct Configurator Technical Reference Guide.

g

DN03453584 Issue 1-0

The LDAP user account is needed to access Configurator information in LDAP. For more information, see Default NetAct user accounts in System Administration Principles.

Id:0900d80580a02f79

29

Configuring NE3S/WS Agent Port, URL path, Operation timeout and Response timeout


6 Configuring NE3S/WS Agent Port, URL path, Operation timeout and Response timeout The default configuration file for NE3S/WS SOAP endpoints and timeouts for CM NE3S Mediation (CMMNE3S) is present in $ETCROOT/rac/conf/cmmne3s/ne3s_soap_endpoints.xml. This file can be used for configuring NE3S/WS agent endpoints and timeouts for each adaptation supported by CMMNE3S. If NE3S/WS agent default endpoints (port or URLpath) and timeouts(Operation timeout and response timeout) is changed, copy ne3s_soap_endpoints.xml file to $ETCROOT/custom/conf/rac/cmmne3s folder and configure the correct endpoints (port or URL path) and timeouts (Operation timeout and response timeout). To configure NE3S/WS Agent Port, URL path, Operation timeout andResponse timeout 1. Log in to a Connectivity Server as the omc user. 2. Check if ne3s_soap_endpoints.xml and ne3s_soap_endpoints.dtd fileexists in the location: $ETCROOT/custom/conf/rac If the file does not exist, follow the instructions: 1 Go to the location $ETCROOT/rac/conf by typing the command: [omc]$ cd $ETCROOT/rac/conf 2 Copy a ne3s_soap_endpoints.xml and ne3s_soap_endpoints.dtd file to the following location: $ETCROOT/custom/conf/rac 3. Update the endpoints (port or URL path) and timeouts (Operation timeout and response timeout) in ne3s_soap_endpoints.xml file for corresponding adaptation. The exemplary entry is as follows: 4. After copying the file, restart RAC_cmmne3s service from the Websphere console. In Websphere Administration Console • select Applications -> Enterprise Applications • Select RAC_cmmne3s and press the ‘Stop’ button. • Once the service has stopped successfully, select RAC_cmmne3s and press the ‘Start’ button.

g

30

Operation timeout and Response timeout must be given in seconds. Timeouts should not be zero or negative.

Id:0900d80580a02f79

DN03453584 Issue 1-0


Customizing NetAct Configurator applications

7 Customizing NetAct Configurator applications You can customize the settings of NetAct Configurator applications by editing configuration files.

7.1

Enabling tracing for Connectivity Server services This section contains information on the tracing procedure for Connectivity Server services.

7.1.1

CM Bulk Data (blkdatmx) To enable blkdatmx trace: 1. Check if blkdatmx.properties exists in $ETCROOT/rac/conf/ If not, create new: blkdatmx.properties file using ASCII text editor. 2. Edit blkdatmx.properties Add the following line: trace = true

g

Check that there are no extra spaces at the end of the line. 3. Find the process id of NetAct Configurator CM Bulk Data (on the server where the Configurator package is running): [omc]$ ps -ef | grep blkdatmx 123 ? 0:13 java1... 4. Kill the process: [omc]$ kill -TERM . The is the process ID number shown as 123 in the example in point 3. 5. Restart the process: omc& kill -HUP An example of pid can be found with the following command: ll $VARROOT/local/common/ref/*wpmana* | grep rac -rw-rw-r-- 1 omc sysop 5576 Sep 18 16:11 it15.rac.wpmanamx.21671

g 7.1.2

Trace information is written to $OMCLOGDIR/info#blkdatmx#*.log

GSM Upload Mediator (uplnwmmx) To enable uplnwmmx trace using the 2G Legacy Upload Mediator process: 1. Check if uplnnwmmx.cf already exists in $ETCROOT/rac/conf/ 2. Edit uplnwmmx.cf and change the trace options to the following: (TRACE "True"

DN03453584 Issue 1-0

Id:0900d80580a02f79

31



(LEVEL "detailed") (REMOVE_TRACE_FILE_"True") )

g 7.1.3

The trace file is /var/opt/nokia/oss/tmp/trace/uplnwmmx.trc on the server where the NetAct Configurator package is running.

NetAct Configurator CM BSC Mediation (cmmbscmx) To enable cmmbscmx trace: 1. Check if cmmbscmx.properties already exists in $ETCROOT/rac/conf 2. Edit cmmbscmx.properties and add the following line: trace = true

g

Check that there are no extra spaces at the end of the line. 3. Find the pid of NetAct Configurator CM BSC Mediation on the server where the Configurator package is running: [omc]$ ps -ef | grep cmmbscmx 123 ? 0:19 java... 4. Kill the process: [omc]$ kill -TERM . The is the process ID number shown as 123 in the example in point 3. 5. Restart the process: omc& kill -HUP An example of pid can be found with the following command: ll $VARROOT/local/common/ref/*wpmana* -rw-rw-r-- 1 omc sysop 5576 Sep 18 16:11 it15rac.wpmanamx.21671 Trace information is written to $OMCLOGDIR/info#cmmbscmx#*.log

7.2

Customizing the settings of CM Bulk Data subsystem The CM Bulk Data subsystem automatically cleans all log files of Downloading RNW Parameters (mtnmanmx, used from the command line only), if they are more than seven days old. You can change the timing of the cleanup by editing a configuration file. For example, if there are lots of GSM operations, you can shorten the cleanup period to decrease the number of mtnman logs in the $OMCLOGDIR directory. For correcting GSM operations over a longer period of time, it may be necessary to keep the log files for more than just one week. To modify the default timing for the log cleanup 1. Log in to a Connectivity Server as the omc user. 2. Move to the correct directory:

32

Id:0900d80580a02f79

DN03453584 Issue 1-0



[omc]$ cd $ETCROOT/rac/conf 3. Edit the blkdatmx.properties file. 4. Modify the default timing by changing the mtnman_log_del_time property. 5. Save the file. 6. Find the process ID of NetAct Configurator CM Bulk Data (on the server where the Configurator package is running): [omc]$ ps -ef | grep cmbulk ? 0:13 java... 7. Kill the process: [omc]$ kill -TERM 8. Restart the process: omc& kill -HUP An example of pid can be found with the following command: ll $VARROOT/local/common/ref/*wpmana* -rw-rwsr-- 1 omc sysop 5658 Sep 21 19:38 /var/opt/nokia/oss/ref/rc71rac.wpmanamx.22395

g 7.3

Trace information is written to $OMCLOGDIR/info#blkdatmx#*.log For more information on the blkdatmx.properties file, see system.properties (NetAct Configurator CM Bulk Data) in NetAct Configurator Technical Reference Guide.

Customizing the settings of CM Analyzer Enabling email notifications for CM Analyzer CM Analyzer sends email notifications about the completed consistency checks and includes the check results in these messages. To enable the notifications, information about the IP address of email server needs to be in the LDAP in the {basedn} > netact > regions > region-{id} > config > cluster > ossSmtpFQDN attribute. This is done during NetAct installation. For instructions on how to activate email notifications on CM Analyzer’s user interface, see Notifying about the check results in CM Analyzer Help. Validating and importing rules For more information on validating rules and importing them by copying, see Rule creation in Rules and Rule Syntax for NetAct Configurator.

7.4

Enabling parameter level audit logging This chapter describes enabling parameter level audit logging for BSC (S15), Ultra Site (AXC), Flexi Site (FTM), MGW and MSS.

DN03453584 Issue 1-0

Id:0900d80580a02f79

33


g 7.4.1


To enable parameter level audit logging for both provisioning and automatic upload, the step Restart Mercury server does not need to be performed twice. One restart after finishing all actions is enough.

Enabling provisioning audit logging To enable plan file archiving: 1. In the WebSphere Administration Console select Servers → Application Servers → Process Definition → Java Virtual Machine → Custom Properties and add the following settings to the path: com.nokia.oss.configurator.rac.mediation.mld.files.automatic _cleanup = false 2. Repeat the step above for all LinAs nodes. 3. Restart Mercury server.

7.4.2

Enabling automatic upload audit logging To enable parameter level audit logging for automatic upload: 1. Log in to a Connectivity Server as the omc user. 2. Check if a configurator.properties file exists in the location: $ETCROOT/custom/conf/rac

g

If the file does not exist, follow the instructions: 1. Go to the location $ETCROOT/rac/conf by typing the command: [omc]$ cd $ETCROOT/rac/conf 2. Copy a configurator.properties file to the following location: $ETCROOT/custom/conf/rac 3. Add the following line to the configurator.properties file: AuditTrailAutomaticUpload = true

7.5

Hiding Administrator operations from CM Operations Manager Operation History view To hide Administrator operations from CM Operations Manager Operation History view: 1. Log in to a Connectivity Server as the omc user. 2. Check if a configurator.properties file exists in the location: $ETCROOT/custom/conf/rac

g

If the file does not exist, follow the instructions: 1. Go to the location $ETCROOT/rac/conf by typing the command: [omc]$ cd $ETCROOT/rac/conf 2. Copy a configurator.properties file to the following location: $ETCROOT/custom/conf/rac 3. Add the following line to the configurator.properties file: hideAdminOperations=true

34

Id:0900d80580a02f79

DN03453584 Issue 1-0


7.6


Customizing the settings of a folder object Folder object is used in CM Editor and CM Operation Manager User Interface for object collection within the same object class. Size of the folder object is defined in LDAP. The parameter for the RAC application object is located in: {basedn} netact → regions → region -{id} → config → scconfig → rac The name of the parameter is ossRacFolderObjectLimits. To check the current folder settings by Jxplorer or the command line tool: 1. Login to the Connectivity Server as the omc user. 2. Execute the following command: ldapacmx.pl -directQuery "(cn=racapplications)" | grep RacFolder The default outcome is the following: ossRacFolderObjectLimits=default=30;nokaxc:axc=20;nokbsc:adc e,nokbsc:adjw,nokrnc:adjg,nokrnc:adji,nokrnc:adjs,nokrnc:adj d=5;nokrnc:hops,nokrnc:hopi,nokrnc:hopg,nokrnc:fmcs,nokrnc:f mci=1 For objects which are not included in the ssRacFolderObjectLimits parameter the default value is 30. Folder limits can be both modified and added. New folder limits need to be separated by a ; sign. To disable the folder object for some object, set the folder object's value to -1 as in the following example: nokbsc:bsc=-1

7.7

Enabling Inter-RAT UTRAN and Inter-RAT GERAN features auto management in Plan Prepare You can enable / disable the automatic management of Inter-RAT UTRAN and GERAN relations which is performed by the Plan Prepare functionality of NetAct Configurator. If the automatic Inter-RAT UTRAN/GERAN management is enabled, the Plan Prepare functionality helps to complete the LTE Inter-RAT adjacency plan and to keep the adjacency relations consistent. For more information about LTE Inter-RAT UTRAN/GERAN adjacencies, see Inter-RAT LTE -> WCDMA adjacencies and Inter-RAT LTE -> GSM adjacencies in Managing Adjacencies document. To enable Inter-RAT UTRAN and Inter-RAT GERAN features auto management in Plan Prepare: 1. Log in to the Connectivity Server as the omc user. 2. Check if the configurator.properties file exists in the $ETCROOT/custom/conf/rac location.

g

DN03453584 Issue 1-0

If the file does not exist, follow the below instruction: 1. Go to the location $ETCROOT/rac/conf 2. Copy a configurator.properties file to the following location: $ETCROOT/custom/conf/rac

Id:0900d80580a02f79

35



3. Edit the configurator.properties file in the $ETCROOT/custom/conf/rac location and change the value of the anrInterRatUtranEnabled or/and anrInterRatGeranEnabled attributes to true like below: • anrInterRatUtranEnabled=true and/or • anrInterRatGeranEnabled=true anrInterRatUtranEnabled entry is used to enable / disable the Inter-RAT UTRAN feature, and anrInterRatGeranEnabled is used to enable / disable the Inter-RAT GERAN feature. To disable Inter-RAT UTRAN and Inter-RAT GERAN features auto management in Plan Prepare, set the values of above attributes to false.

7.8

Handling critical parameters in NetAct Configurator NetAct Configurator can be configured so that the critical parameters can be provisioned to the network only by the users having the dedicated user permission: RAC.Cell_Power_Limitation. This permission is attached to the default role: Network Planning Engineer. When this feature is turned on, the parameters defined as critical can be planned by all NetAct Configurator users, but a special permission is needed for provisioning the plan containing these parameters changes. The same applies to the modification of the critical parameters using the Send to Network function. The critical parameters are, for example, output power parameters. NetAct Configurator provides the default list of the critical parameters that require a special permission for provisioning, but this list can be modified according to your needs by adding and / or removing desired parameters to / from the list. The list of critical parameters is defined as the LimitedEdit custom annotation. The feature of checking the required permission when provisioning the critical parameters to the network can be enabled / disabled by the Administrator. To enable / disable the checking of a required permission when provisioning the critical parameters to the network 1. Log in to the Connectivity Server as the omc user. 2. Check if the configurator.properties file exists in the $ETCROOT/custom/conf/rac location.

g

If the file does not exist, follow the below instruction: 1. Go to the $ETCROOT/rac/conf location. 2. Copy the configurator.properties file to the following location: $ETCROOT/custom/conf/rac 3. Edit the configurator.properties file in the $ETCROOT/custom/conf/rac location and change the value of the cellPowerLimitation entry according to your needs (true or false). Set it to true to enable this feature or to false to disable it.

g

The default value of the feature property is set to false (feature is turned off), meaning that the Configurator doesn't distinguish between casual parameters and critical parameters when provisioning a plan. To customize the default list of the critical parameters

36

Id:0900d80580a02f79

DN03453584 Issue 1-0



1. Log in to the Connectivity Server as the omc user. 2. Copy the default critical parameters list file, abstractattributes_limited_edit.xml from the $ETCROOT/rac/conf/abstraction/customannotations/ directory to the $ETCROOT/custom/conf/rac/abstraction/customannotations/ directory and edit the already mentioned xml file adding the following line to the file: ::" name=""/> If such a file does not exist, create your own xml file in the $ETCROOT/custom/conf/rac/abstraction/customannotations/ directory according to the below example: 3. Copy the schema file, customannotations.xsd from the $ETCROOT/rac/conf/abstraction/customannotations/ directory to the $ETCROOT/custom/conf/rac/abstraction/customannotations/ directory. 4. Restart Mercury server.

7.9

Defining the maximum number of managed objects in one validation file for LTE You can define the number of the MRBTSs that are included in one validation file. If the number of the MRBTSs in a validated plan is greater than configured value, then multiple validation files are created and validated separately. To define the maximum number of manage objects in one validation file 1. Log in to the Connectivity Server as the omc user. 2. Check if the configurator.properties file exists in the $ETCROOT/custom/conf/rac location.

g

If the file does not exist, follow the below instruction: 1. Go to the $ETCROOT/rac/conf location. 2. Copy the configurator.properties file to the following location: $ETCROOT/custom/conf/rac 3. Edit the configurator.properties file in the $ETCROOT/custom/conf/rac location and change the value of the validationFileMOLimit entry according to your needs.

g DN03453584 Issue 1-0

The default value is 1000.

Id:0900d80580a02f79

37


7.10


Defining the number of waiting operations per BSC, RNC and LTE OMS You can define the maximum number of waiting operations per BSC, RNC and LTE OMS. For LTE OMS, upload operations for MRBTSs and OMSs and provisioning operations for plans containing MRBTSs and/or PREBTSs from CM Operations Manager or command line, the Activate (combined Pre-activate and Activate), Pre-Activate and Upload operations are automatically queued when OMS is no longer accepting new CM operations.

g

The Activate Pre-activated Plan -operations are not queued. To define the maximum number of waiting operations per BSC, RNC and LTE OMS: 1. Log in to the Connectivity Server as the omc user. 2. Check if the configurator.properties file exists in the $ETCROOT/custom/conf/rac location. If the file does not exist, follow the below instruction: 2.1 Go to the $ETCROOT/rac/conf location. 2.2 Copy the configurator.properties file to the following location: $ETCROOT/custom/conf/rac 3. Edit the configurator.properties file in the $ETCROOT/custom/conf/rac location and change the value of the ssRacBSCMaxNumberOfWaitingOperations (BSC), ossRacRNCMaxNumberOfWaitingOperations (RNC) and/or ossRacLTEMaxNumberOfWaitingOperations (MRBTS and LTE OMS) entry according to your needs. The default value is 20 for LTE OMS, and 5 for BSC and RNC.

7.11

Enabling skipping BTS, Flexi Direct and/or LTE validation before pre-activation There is a possibility to skip the BTS, Flexi Direct and/or LTE data validation with unselecting Validate plan before pre-activation and BTS file generation (BTS and LTE tab) and Validate BTS plan before pre-activation (Flexi Direct tab) check box in the Provision dialog only if allowSkippingOfBTSDataValidation=true (for BTS and Flexi Direct) and/or allowSkippingOfLTEDataValidation=true (for LTE) properties have been set in $ETCROOT/custom/conf/rac/configurator.properties file. When these properties are not set in configurator.properties file, BTS, Flexi Direct and LTE data validation is always selected and dimmed, so that it cannot be unselected and BTS, Flexi Direct and LTE data is always validated before pre-activation. To enable the Validate plan before pre-activation and BTS file generation (BTS and LTE tab) and/or Validate BTS plan before pre-activation (Flexi Direct tab) check box in the Provision dialog in CM Operations Manager: 1. Log in to the Connectivity Server as the omc user. Check if the configurator.properties file exists in the $ETCROOT/custom/conf/rac location. If the file does not exist, follow the below instruction: 1.1 Go to the $ETCROOT/rac/conf location.

38

Id:0900d80580a02f79

DN03453584 Issue 1-0



1.2 Copy the configurator.properties file to the following location: $ETCROOT/custom/conf/rac. 2. Copy the configurator.properties file to the following location: $ETCROOT/custom/conf/rac. 3. Edit the configurator.properties file in the $ETCROOT/custom/conf/rac location and change the value of the allowSkippingOfBTSDataValidation=true (for BTS and Flexi Direct) and/or allowSkippingOfLTEDataValidation=true (for LTE) attribute (add the attribute if missing from the file) according to your needs (true or false). Set the value to true to enable Validate plan before pre-activation and BTS file generation (BTS and LTE tab) and/or Validate BTS plan before pre-activation (Flexi Direct tab) check box in the Provision dialog or to false to disable it.

7.12

Enabling validation files saving When a plan (for GSM, WCDMA, Flexi Direct or LTE BTS) has been validated, validation files are by default deleted after the operation has been finished. For troubleshooting purposes you can force the validation files to be stored in the file system by selecting the Save validation files option in the Provision dialog in CM Operations Manager. By default the Save validation files check box is disabled in the user interface, nevertheless you can enable the check box by defining a new attribute in the configurator.properties file. To enable the Save validation files check box in the Provision dialog in CM Operations Manager 1. Log in to the Connectivity Server as the omc user. 2. Check if the configurator.properties file exists in the $ETCROOT/custom/conf/rac location.

g

If the file does not exist, follow the below instruction: 1. Go to the $ETCROOT/rac/conf location. 2. Copy the configurator.properties file to the following location: $ETCROOT/custom/conf/rac 3. Edit the configurator.properties file in the $ETCROOT/custom/conf/rac location and change the value of the allowSavingOfValidationFiles attribute (add the attribute if missing from the file) according to your needs (true or false). Set the value to true to enable saving the validation files option selected from the provisioning view or to false to disable it.

g

DN03453584 Issue 1-0

This feature supports all operations where BTS plan is validated: Activate, Pre-Activate, Validate, and Generate BTS configuration file. Notice that validation files remain in the file system until you delete them, therefore before enabling this feature make sure that there is enough free disk space available in the global disc since the validation files can be very large. Remove the validation files which are no longer needed for troubleshooting purposes in order to free disc capacity.

Id:0900d80580a02f79

39

Managing the software version and options support


8 Managing the software version and options support The required procedures depend on whether you are bringing a completely new network element (BSC, MSC, MGW or SGSN) into use or updating the information in an old one. New network elements are created with Network Editor. For instructions, refer to Network Editor Help.

8.1

Setting the RNC version and options For information on managing software versionand options support, see Adding the RNC to a network view in Integrating RNC to NetAct.

8.2

Setting the MSC options The MSC options can be set using CM Editor. To open CM Editor 1. Open the NetAct Start for the server. 2. Click on Configuration in the browser to the left. 3. Click on the CM Editor icon on the page. To modify MSC options 1. Click on the MSC icon in the browser to the left. The MSC actual parameters are loaded. 2. Select the Modify Actual Value(s) check box in the parameter definition area. 3. Click on the Actual Value column for MSC Options parameter. A drop-down menu appears. 4. Click on Add. This adds a new row for MSC options. 5. Click on the newly added row to select the MSC option to be set. 6. To set another MSC option, repeat steps 3 to 5. 7. When you have finished modifying MSC options, right click on the MSC icon in the browser to the left and select Send to Network. This saves the MSC options to the NetAct database.

g

This procedure only updates the values in the NetAct Configurator database, but does not make the changes in the network elements. Use MML commands to change the settings in the MSCs in the network.

8.3

Setting the MGW options The MGW options can be set using CM Editor. To open CM Editor 1. Open the NetAct Start for the server. 2. Click on Configuration in the browser to the left.

40

Id:0900d80580a02f79

DN03453584 Issue 1-0



3. Click on the CM Editor icon on the page. To modify MGW options 1. Click on the MGW icon in the browser to the left. The MGW actual parameters are loaded. 2. Select the Modify Actual Value(s) check box in the parameter definition area. 3. Click on the Actual Value column for MGW Options parameter. A drop-down menu appears. 4. Click on Add. This adds a new row for MGW options. 5. Click on the newly added row to select the MGW option to be set. 6. To set another MGW option, repeat steps 3 to 5. 7. When you have finished modifying MGW options, right click on the MGW icon in the browser to the left and select Send to Network. This saves the MGW options to the NetAct database.

g

This procedure only updates the values in the NetAct Configurator database, but does not make the changes in the network elements. Use MML commands to change the settings in the MGWs in the network.

8.4

Setting the SGSN options The SGSN options can be set using CM Editor. To open CM Editor 1. Open the NetAct Start for the server. 2. Click on Configuration in the browser to the left. 3. Click on the CM Editor icon on the page. To modify SGSN options 1. Click on the SGSN icon in the browser to the left. The SGSN actual parameters is loaded. 2. Select the Modify Actual Value(s) check box in the parameter definition area. 3. Click on the Actual Value column for SGSN Options parameter. A drop-down menu appears. 4. Click on Add. This adds a new row for SGSN options. 5. Click on the newly added row to select the SGSN option to be set. 6. To set another SGSN option, repeat steps 3 to 5. 7. When you have finished modifying SGSN options, right-click on the SGSN icon in the browser to the left and select Send to Network. This saves the SGSN options to the NetAct database.

g

DN03453584 Issue 1-0

This procedure only updates the values in the NetAct Configurator database, but does not make the changes in the network elements. Use MML commands to change the settings in the SGSNs in the network.

Id:0900d80580a02f79

41


8.5


Setting the BSC version and options This feature enables NetAct to set q3PreferredConf, which indicates the BSC software package related to Q3 primitive exchanging that NetAct wants BSC to emulate. For example, with value S14, BSC sends primitive exchange and events according to BSC S14 package Q3 specifications, with value S15 according to S15 Q3 specifications, and so on. This process is for updating the version of the BSCs to the network element and to the NetAct database. To set the BSC version 1. Log in to a Connectivity Server as the omc user. 2. Log in to the BSC by entering the following command: [omc]$ ouimanmx vterm> host vterm> open In the command, refers to the application entity (AE) name of the BSC network element.

g

An MML session to a network element can also be launched from the Top-level User Interface. Right-click the network element object and select MML session from the pop-up menu that is displayed. 3. Enter your user name and password when requested. 4. To find out the C-number of the BSC, type the following command and check the Cnumber from the displayed output: ZQNI; 5. To find out the software version for the BSC, type the following command and check the version from the displayed output: ZWQO:CR; 6. To set the BSC version, execute the following command: [omc]$ q3versmx and use the following command line options: Options

Explanation

-trace

Writes trace. The default option is no trace.

-help

Prints the help for q3versmx

-allbscs

Sets the Q3 version and enables Q3 events for all BSCs.

-bscvers

If you do not want to use the default version (S15), specify the Q3 version with this option.

Table 9

42

q3versmx command line options

Id:0900d80580a02f79

DN03453584 Issue 1-0


Options

Explanation

-bscid

This option identifies the BSC with a C number. The Q3 version is set only for the identified BSC.

-bscintid

This option identifies the BSC with an internal ID. The Q3 version is set only for the identified BSC.

Table 9

g


q3versmx command line options (Cont.)

You must enter either -allbscs, -bscid, or -bscintid. You cannot enter several of these. For example, the following command line sets the default version S15 for the BSC identified with the internal ID 23456789 in the NetAct database: [omc]$ q3versmx -bscintid 23456789 The default value is BSC S15.

g

The length of the version field is 5 characters.

g

BCFs and BTSs must be included in the initial BSC upload, but adjacencies must be uploaded later in another upload. Handling optional BSC features Many BSC features are optional, meaning that they are not included in the basic system and that the operator can acquire them separately. Management of certain radio parameters is relevant only if the related optional feature is available in the network (BSCs) and the option is enabled in the BSCs. Information of optional feature usage (enabled or not) is stored per BSC in NetAct Configurator database (using CM Editor user interface and by uploading from the network). Option-dependent parameters and commands are not available for users in the MML interface if the option is not enabled. At plan activation (download) from Configurator, option dependent parameters are skipped and they are not sent to BSCs. Configurator applications such as CM Editor do not use option information. Instead, in CM Editor, user views can be configured so that the user interface includes/does not include parameters according to the user’s requirements. If user views are not used, all parameters are available to the user in the CM Editor window, even if the options are not available in the BSC or they are disabled. This is the case with the All parameters view. Plan Editor does not use option information. User’s access/view to parameters is configured by views. Only relevant/wanted parameters can be edited and shown. Unnecessary parameters are not displayed in the user interface. See Plan Editor Principles and Plan Editor Help for more information.

DN03453584 Issue 1-0

Id:0900d80580a02f79

43

Maintaining the NetAct Configurator database using the NetAct Doctor


9 Maintaining the NetAct Configurator database using the NetAct Doctor The NetAct Configurator Database can be checked and corrected in various situations using the NetAct Doctor command line tool in Linux environment. NetAct Doctor has the number of use cases for the regular customer use. These cases and their usage are described in more detail in the Troubleshooting Configuration Management Problems document.

44

g

Do not run any other cases unless you have received a permission and instructions from Nokia Siemens Networks personnel

g

It is recommend that you always run the report and view the current situation first, and then decide if running the case that corrects the situation is necessary.

Id:0900d80580a02f79

DN03453584 Issue 1-0


NetAct Parameter-based Licences

10 NetAct Parameter-based Licences CM parameters related to the following licences can be managed by using NetAct Configurator tools only if a proper licence is purchased from Nokia Siemens Networks. • • •

NetAct Configurator functionality for basic HSPA NetAct Configurator for HSPA QoS Management NetAct Configurator for Native IP Management

If the proper parameter-based licence is not purchased for the CM parameters being under the licence, you cannot change the parameter values in the Network Element and get the actual values updated via the upload operation or events. In order to check which CM parameters are related to the mentioned licences, see Appendix A: Parameters related to features under parameter-based license. To check which parameter-based licences are purchased and installed in the system 1. Login to Connectivity Server as omc user. 2. Open lmdlicmx.dat license file by running the following command: less /etc/opt/nokia/oss/common/conf/lmdlicmx.dat The parameter-based licences have the following IDs in the file: • NetAct Configurator functionality for basic HSPA (CM_MGMT_HSPA) • NetAct Configurator for HSPA QoS Management (CM_MGMT_HSPA_QOS) • NetAct Configurator for Native IP Management (CM_MGMT_IPIU) If you purchased one or more of these features and they are missing from the licence file, a new NetAct licence file containing the purchased licences need to be requested from OBS SW Maintenance and Delivery Support: [email protected] To install the needed parameter-based licences 1. Login to Connectivity Server as omc user. 2. Run the following command to take a backup copy of the existing licence file: cp /etc/opt/nokia/oss/common/conf/lmdlicmx.dat /etc/opt/nokia/oss/common/conf/lmdlicmx_backup.dat 3. Run the following command to copy the received new licence file (here located in home directory of the omc user) to replace the existing NetAct licence file: cp ~/lmdlicmx.dat /etc/opt/nokia/oss/common/conf/lmdlicmx.dat

DN03453584 Issue 1-0

Id:0900d80580a02f79

45

Command line operations


11 Command line operations This chapter gives instructions for the command line usage of NetAct Configurator. Many of the commands are executed by using the racclimx.sh tool. This tool is by default defined in the user’s PATH environment variable in the following directory: $PRODUCTROOT/bin.

g

The racclimx.sh tool can be run on the Connectivity Server of the NetAct clusters. To run command line operations with the racclimx.sh tool 1. Log in to one of the Connectivity Servers as omc user. 2. Enter the following command: [omc]$ racclimx.sh and choose the command line options you want.

g 11.1

If you enter only the command (racclimx.sh) without any options, all the options are displayed on the screen.

Scheduling command line operations Most command line operations executed using the racclimx.sh tool can be scheduled to be automatically executed at specific time and date with or without recurrence. You can schedule command line operations by using -schedule option with proper arguments when running a command line operation.

g

You can also schedule these operations by entering the command of your choice to a line in the crontab file in Linux. For more information on the cron scheduler, see Managing crontab files in Managing the Linux System. Command line options/arguments for scheduling one-time operation To execute this operation, add the following option to your command: -schedule date= Where: - operation execution date given in the yyyy-mm-dd format optionally followed by a time in the THH:mm or THH:mm:ss format, for example, 2010-10-27T15:00 - operation execution hour given in the hh:mm format, for example, 15:00 Example: [omc]$ racclimx.sh -op -schedule date=2010-1027T15:00 Command line options/arguments for scheduling recurring operation To execute this operation, add the following option to your command: -schedule [daily | weekdays= | dayOfMonth=] start= end= Where:

46

Id:0900d80580a02f79

DN03453584 Issue 1-0



- operation execution hour given in the hh:mm format, for example, 15:00 - specifies in which days of the week the scheduled operation should be executed; possible values: Mon, Tue, Wed, Thu, Fri, Sat, Sun; to specify more than one day in the week, list the days by using comma between them; - specifies the number of the day within a month (1..31) when the scheduled operation should be executed - date when the period of running recurrent operation starts - date when the period of running recurrent operation ends Examples: 1) Scheduling operation to be executed daily at 3 pm between 27.03.2013 and 28.03.2013 [omc]$ racclimx.sh -op -schedule 15:00 daily start=2013-03-27 end=2013-03-28 2) Scheduling operation to be executed at 3 pm every Monday and Wednesday between 27.03.2013 and 28.03.2013 [omc]$ racclimx.sh -op -schedule 15:00 weekdays=Mon, Wed start=2013-03-27 end=2013-03-28 3) Scheduling operation to be executed at 3 pm every 13th day of the month between 13.03.2013 and 15.04.2013 [omc]$ racclimx.sh -op -schedule 15:00 dayOfMonth=13 start=2013-03-13 end=2013-04-15

11.2

Uploading actual values The command line racclimx.sh upload operation is used for uploading actual values from: • • • • • •

GSM (BSC RNW, BTS SC), WCDMA (RNC RNW, RNC ATM/IP, AXC, FTM, WBTS SC), Flexi Direct, LTE Core (MSC, MGW), OMC

to the NetAct Configurator database. For more information on how to upload actual configurations with the CM Operations Manager user interface, see CM Operations Manager Help. The upload operation is used for uploading actual values from GSM, RNC RNW, RNC ATM/IP, AXC, FTM, Flexi Direct, WBTS SC, LTE, and core network objects to the NetAct Configurator database. The starting parameters

Explanation

-op

Choose Upload for this operation.

-v

If this option is given, the feedback of the operation is printed on the screen.

Table 10

Command line options for upload operations

DN03453584 Issue 1-0

Id:0900d80580a02f79

47



The starting parameters

Explanation

-DN

Defines the scope of the operation (comma separated Distinguished Names).

-feedbackLevel

Specifies the level of feedback in the Upload operation:

• • •

summaryLevel objectLevel parameterLevel

-ipContentInUse

Specifies if IP-related objects of an RNC are handled with an upload operation. The default value is false. This argument is optional.

-bssRNWContentInUse

Indicates if BSS related RNW objects are handled with a provisioning or upload operation. The default value is true. This argument is optional.

-btsContentInUse

Indicates whether Site Configuration data is handled with a provisioning and upload operation. Applicable for RNC RN5.0 onwards, WCDMA FlexiBTS, WCDMA Ultra/MetroBTS, and WCDMA FlexiBTS transport data and BSC S15 onwards for GSM Flexi BTS. The default value is false. This argument is optional

-atmContentInUse

Specifies if ATM-related objects of an RNC are handled with an upload operation. The default value is false. This argument is optional.

-rncAxcContentInUse

Indicates if AXC Configuration data of RNC is handled with a provisioning or upload operation. The default value is true. This argument is optional.

-rnwContentInUse

Specifies if RNW-related objects of an RNC are handled with an upload operation. The default value is true. This argument is optional.

-signalingContentInUse

Indicates if Signaling related objects of an RNC are handled with a provisioning or upload operation. The default value is false. This argument is optional.

-ftmContentInUse

Indicates if FTM related objects are handled with a provisioning or upload operation. Applies with RNC versions up to RN4.0. The default value is false. This argument is optional.

-lteContentInUse

Indicates if LTE related objects are handled with provisioning or upload operation. The default value is true. This argument is optional.

-ihspaBTSSCContentInUse

Indicates if Flexi Direct related BTSSC objects are handled with a provisioning or upload operation. The default value is true. This argument is optional.

-onlyAutoconnDataForGOMS

Uploads only PREBTS objects from GOMS database. PREBTSs are used for auto connection. The default value is false. This argument is optional.

-takeAMLFileBackups

Specifies if AML files are stored as backup after upload. In RNC case this applies with versions starting from RN5.0. This argument is optional.

Table 10

48

Command line options for upload operations (Cont.)

Id:0900d80580a02f79

DN03453584 Issue 1-0




Explanation

-takeLTEFileBackups

Specifies if LTE mediation files are stored as backup after upload. The default value is false. This argument is optional.

-takeBTSFileBackups

Specifies if mediation files are stored as backup after upload. Applicable for RNC RN5.0 onwards, WCDMA FlexiBTS, WCDMA Ultra/MetroBTS, and WCDMA FlexiBTS transport data and BSC S15 onwards for GSM Flexi BTS. The default value is false. This argument is optional.

-takeFlexiTRSFileBackups

Specifies if FTM configuration files are stored as backup after upload. Applies with RNC versions up to RN4.0. The default value is false. This argument is optional.

-forcedUpload

This option selects Forced Upload option. For more information, see Forced Upload section.

-ihspaRNWContentInUse

Specifies if Flexi Direct related RNW objects are handled with an upload operation. The default value is true. This argument is optional.

-ihspaFTMContentInUse

Specifies if Flexi Direct related FTM objects are handled with an upload operation. The default value is true. This argument is optional.

-ihspaAXCContentInUse

Specifies if IHSPA related AXC objects are handled with an upload operation. The default value is true. This argument is optional.

-ihspaIPContentInUse

Specifies if Flexi Direct related IP objects are handled with an upload operation. The default value is true. This argument is optional.

-ihspaSIGContentInUse

Specifies if Flexi Direct related SIG objects are handled with an upload operation. The default value is true. This argument is optional.

-ihspaFileBackups

Specifies if OMS files are stored as backup after upload of Flexi Direct. The default value is false. This argument is optional.

-coreMSCRNWContentInUse

Specifies if MSC related RNW objects are handled with an upload operation. The default value is true. This argument is optional.

-coreMSCROUContentInUse

Specifies if MSC related ROUTING objects are handled with an upload operation. The default value is true. This argument is optional.

-coreMSCSIGContentInUse

Specifies if MSC related SIG objects are handled with an upload operation. The default value is true. This argument is optional.

-coreMSCIPContentInUse

Indicates if MSC related IP objects are handled with an upload operation.

-coreMSCANALYSEContentInUse

Specifies if MSC related ANALYSE objects are handled with an upload operation. The default value is true. This argument is optional.

Table 10

Command line options for upload operations (Cont.)

DN03453584 Issue 1-0

Id:0900d80580a02f79

49




Explanation

-coreMSCCONNContentInUse

Specifies if MSC related CONNECTION objects are handled with an upload operation. The default value is true. This argument is optional.

-coreMSCGENContentInUse

Specifies if MSC related GENERAL objects are handled with an upload operation. The default value is true. This argument is optional.

-coreMGWATMContentInUse

Specifies if MGW related ATM objects are handled with an upload operation. The default value is true. This argument is optional.

-coreMGWROUContentInUse

Specifies if MGW related ROUTING objects are handled with an upload operation. The default value is true. This argument is optional.

-coreMGWSIGContentInUse

Specifies if MGW related SIG objects are handled with an upload operation. The default value is true. This argument is optional.

-coreMGWIPContentInUse

Indicates if MGW related IP objects are handled with an upload operation.

-coreMGWANALYSEContentInUse

Specifies if MGW related ANALYSE objects are handled with an upload operation. The default value is true. This argument is optional.

-coreMGWCONNContentInUse

Specifies if MGW related CONNECTION objects are handled with an upload operation. The default value is true. This argument is optional.

-coreMGWGENContentInUse

Specifies if MGW related GENERAL objects are handled with an upload operation. The default value is true. This argument is optional.

-corePBXContentInUse

Specifies if PBX objects are handled with an upload operation. The default value is false. This argument is optional.

-coreOPUContentInUse

Specifies if OPU objects are handled with an upload operation.

-coreSpecialOutputFile

Specifies if special name of output files has to be used. This is valid with PBX fragment. The default value is false. This argument is optional.

-coreFINGSERVAWRContentInUse

Indicates if FING related SERVAWR objects are handled with an upload operation.

-coreFINGSESSIONContentInUse

Indicates if FING related SESSION objects are handled with an upload operation.

Table 10

Command line options for upload operations (Cont.) Example of GSM upload To view feedback for objects on a summary level after upload, enter the following command: [omc]$ racclimx.sh -op Upload -DN PLMN-PLMN/BSC-1000 feedbackLevel summaryLevel

50

Id:0900d80580a02f79

DN03453584 Issue 1-0



Example of WCDMA upload To view feedback for objects on a summary level after upload, enter the following command: [omc]$ racclimx.sh -op Upload -DN PLMN-PLMN/RNC-1000 feedbackLevel summaryLevel To upload RNW changes (default true) and IP changes, enter the following command: [omc]$ racclimx.sh -op Upload -DN PLMN-PLMN/RNC-1000 ipContentInUse true Example of Flexi Direct upload The following commands show the GOMS and IADA objects upload examples: [omc]$ racclimx.sh -op Upload -DN PLMN-PLMN/GOMS-70 ihspaFTMContentInUse false –v [omc]$ racclimx.sh -op Upload -DN PLMN-PLMN/IADA-80 ihspaIPContentInUse false -v Example of core network upload The following commands show the MGW and MSC objects upload examples: [omc]$ racclimx.sh -op Upload -DN PLMN-PLMN/MSC-50 -feedbackLevel summaryLevel -coreMSCSIGContentInUse false coreMSCRNWContentInUse false –v [omc]$ racclimx.sh -op Upload -DN PLMN-PLMN/MGW-60 -feedbackLevel summaryLevel -coreMGWSIGContentInUse false coreMGWATMContentInUse false -coreMGWROUContentInUse false –v

g 11.3

For more information on how to upload actual configurations with the CM Operations Manager user interface, see CM Operations Manager Help.

Provisioning plans This chapter provides information on the command line options for plan provisioning.

11.3.1

GSM This section provides information on the command line options for GSM file-based plan provisioning.

11.3.1.1

Validating BTS SC plan before pre-activation The BTS SC plan is validated in NetAct before pre-activation.


Explanation

-op

Choose Validate for this operation.

-DN


-planName

The name of the plan that is used in the operation.

Table 11

Command line options for validating BTS SC plan.

DN03453584 Issue 1-0

Id:0900d80580a02f79

51




Explanation

-btsContentInUse

Indicates whether Site Configuration data for WCDMA Flexi BTS and GSM Flexi BTS transport data is handled with a validation operation. Applicable for RNC RN5.0 onwards and BSC S15 onwards. Default value is false. The argument is optional.

Table 11

Command line options for validating BTS SC plan. (Cont.) Example To validate plan content in the BTS before pre-activation, enter the following command: [omc]$ racclimx.sh -op Validate -DN PLMN-PLMN/BSC-1000/BTS1 -planName PLMN_plan -btsContentInUse true

11.3.1.2

Validating BSC RNW plan after pre-activation The validation operation checks the consistency of the plan that already exists in the BSC plan database. The separate validation operation is useful, for example, in case local changes have been done in BSC after the plan pre-activation. The starting parameters

Explanation

-op

Choose Validate_BSC for this operation.

-v


-planName


-bssRNWContentInUse

Indicates if BSC content in plan is validated. Note: this operation is valid only for the downloaded plan in BSC. The default value is false. This argument is optional.

-localChangesBlocked

Specifies whether local changes must be blocked during BSC validation operation.

Table 12

Command line options for validating BSC RNW plan.

Example of validating plan content in the BSC To validate plan content in the BSC after pre-activation, enter the following command: [omc]$ racclimx.sh -op Validate_BSC -v -planName PLMN_plan -localChangesBlocked

g 11.3.1.3

For more information on provisioning plans with the CM Operations Manager user interface, see CM Operations Manager Help.

Pre-activating and activating GSM plan The Pre-activate operation performs the following operations on the BSC RNW plan: 1. Download the plan to BSC 2. Validate the plan The Pre-activate operation performs the following operation on the BTS SC plan:

52

Id:0900d80580a02f79

DN03453584 Issue 1-0



1. Download the plan to BSC The Activate operation performs the following operations on the BSC RNW plan: 1. Download the plan to BSC 2. Activate the plan in BSC (including validation) The Activate operation performs the following operations on the BTS SC plan: 1. Validate the plan 2. Download the plan to BTS via BSC 3. Activate the plan in BTS The starting parameters

Explanation

-op

Choose Provision for this operation.

-v


-DN


-planName


-provisioningOperation

Defines a provisioning operation (activate/preactivate). The default value is activate.

-detailedProvFBNeededForBsc

Specifies whether user wants to see detailed feedback about BSC provisioning.

-serviceImpactLevel

Specifies the service impact level for the activation operation. Allowed values are 0-20. Value 0 means that the BSC activates simultaneously as many BCF objects as possible. Values 1-20 mean that the BSC activates 120% of the BCF objects simultaneously. A high number of BCF objects activated simultaneously means that the probability of dropped calls during the activation is higher. The default value is 5.

-fallbackInActivation

Specifies whether a fallback must be taken during BSC activation operation.

-localChangesBlocked

Specifies whether local changes must be blocked during BSC validation operation.

-gsmForcedHOTimeLimit

Specifies the forced handover time limit between 1...500 seconds. The default value is 2 seconds.

-createBackupPlan

Specifies whether backup plan is created or not. The default value is false. This parameter is not manadatory.

-backupPlanName

Specifies a backup plan name. The default value is Backup_plan. This parameter is not mandatory.

-btsContentInUse

Indicates whether Site Configuration data is handled with Provisioning and Upload operation. Applicable for RNC RN5.0 onwards, WCDMA FlexiBTS, WCDMA Ultra/MetroBTS, and WCDMA FlexiBTS transport data and BSC S15 onwards for GSM Flexi BTS. Default value is false. This argument is optional.

Table 13

Command line options for provisioning

DN03453584 Issue 1-0

Id:0900d80580a02f79

53




Explanation

-btsUploadAfterActivate

Specifies whether Site Configuration data upload is needed after activation. Applicable for RNC RN5.0 onwards, WCDMA FlexiBTS, WCDMA Ultra/MetroBTS, and WCDMA FlexiBTS transport data and BSC S15 onwards for GSM Flexi BTS. Default value is true. This argument is optional.

-validateBeforePreactivation

Specifies if validation is enabled for GSM and WCDMAFlexiBTS plan before Activate and Pre-Activate provisioning operations. Default value is true. This argument is optional.

Table 13

Command line options for provisioning (Cont.) Example of provisioning To activate a BSC RNW plan with file based plan provisioning to the 20% of the BSC sites at a time, enter the following command: [omc]$ racclimx.sh -op Provision -provisioningOperation activate -serviceImpactLevel 20 -planName BSCRNW_plan To activate BTS site configuration plan, enter the following command: [omc]$ racclimx.sh -op Provision -provisioningOperation activate -btsContentInUse true -planName BTSSC_plan

g 11.3.1.4


Activating the pre-activated GSM plan The Activating the pre-activated plan operation performs the following operation on the BSC RNW plan: 1. Activate the plan that already exists in the BSC plan database The Activating the pre-activated plan operation performs the following operations on the BTS SC plan: 1. Download the plan from BSC to BTS 2. Activate the plan in BTS The starting parameters

Explanation

-op

Choose Activate_Pre-Activation for this operation.

-v


-planName


-fallbackInActivation

Specifies whether a fallback must be taken during BSC activation operation.

Table 14

54

Command line options for the Activate_Pre-Activation operations

Id:0900d80580a02f79

DN03453584 Issue 1-0




Explanation

-serviceImpactLevel

Specifies the service impact level for the activation operation. Allowed values are 0-20. Value 0 means that the BSC activates simultaneously as many BCF objects as possible. Values 1-20 mean that the BSC activates 120% of the BCF objects simultaneously. A high number of BCF objects activated simultaneously means that the probability of dropped calls during the activation is higher. The default value is 5.

-btsContentInUse

Indicates whether Site Configuration data is handled with Provisioning and Upload operation. Applicable for RNC RN5.0 onwards, WCDMA FlexiBTS, WCDMA Ultra/MetroBTS, and WCDMA FlexiBTS transport data and BSC S15 onwards for GSM Flexi BTS. Default value is false. This argument is optional.

-gsmForcedHOTimeLimit

Specifies the forced handover time limit between 1...500 seconds. The default value is 2 seconds.


Specifies whether Site Configuration data upload is needed after activation. Applicable for RNC RN5.0 onwards, WCDMA FlexiBTS, WCDMA Ultra/MetroBTS, and WCDMA FlexiBTS transport data and BSC S15 onwards for GSM Flexi BTS. Default value is true. This argument is optional.

detailedProvFBNeededForBs c

Specifies whether user wants to see detailed feedback about BSC provisioning.

Table 14

Command line options for the Activate_Pre-Activation operations (Cont.)

Example of activation after the pre-activation To activate the plan after pre-activation in the BSC, enter the following command: [omc]$ racclimx.sh -op Activate_Pre-Activation -v -planName PLMN_plan -fallbackInActivation -serviceImpactLevel 1

g 11.3.2 11.3.2.1


WCDMA, Flexi Direct, LTE, and core Validating WBTS SC and LTE plans before pre-activation The plan is validated using technology specified validation method.

g

DN03453584 Issue 1-0

Validation of WBTS SC and LTE RNW, FTM and SC data is done before pre-activation (download) in NetAct.

Id:0900d80580a02f79

55




Explanation

-op

Choose Validate for this operation.

-DN

Specifies the scope of the operation (comma separated Distinguished Names without spaces). This argument is optional.

-planName

Specifies a plan name.

-btsContentInUse

Indicates if FlexiBTS Site Configuration and Transport data or Ultra/MetroBTS Site Configuration data of RNC are handled with a validation operation (this operation is valid only before download of the BTS plan). The default value is false. This argument is optional.

-ihspaBTSContentInUse

Indicates whether Site Configuration data for WCDMA FlexiBTS transport data is handled with a validation operation. Applicable for IADA IH3.0 onwards. The default value is false. This argument is optional.

-noFileCleanup

Indicates if a configuration and feedback file should be left on disk after operation. The default value is false. This argument is optional.

-lteContentInUse

Indicates if MRBTS and child objects are handled with a validation operation. Default value is false. This argument is optional.

splitIntoSuccessfulAndFail edPlans

Specifies that separate plans are generated for successful and failed MRBTSs if errors are found during validation. Applies to LTE objects only. The default value is false. This argument is optional.

Table 15

Command line options for validating plan content

Example of validating WBTS SC data under specified scope To validate WBTS SC data under specified scope, enter the following command: [omc]$ racclimx.sh -op Validate -planName plan1 -btsContentInUse true -DN PLMN-PLMN/RNC-123/WBTS-1

11.3.2.2

Pre-activating and activating plans for RNC RNW, RNC ATM/IP, AXC, FTM, Flexi Direct, WBTS SC, core and LTE


Explanation

-op

Choose Provision for this operation.

-v


-DN


-planName


-provisioningOperation

Defines a provisioning operation (activate/pre-activate). The default value is activate.

Table 16

56

Command line options for plan provisioning

Id:0900d80580a02f79

DN03453584 Issue 1-0




Explanation

-lockingAllowed

Specifies whether locking is allowed or not. Default value is true. This argument is optional.

-validateBeforePreactivation

Specifies if validation is enabled for GSM and WCDMAFlexiBTS plan before Activate and Pre-Activate provisioning operations. Default value is true. This argument is optional.

-axcUploadAfterActivation

Specifies if AXC upload is needed after activation. The default value is true.


Specifies whether BTS site configuration data and Flexi transport data upload is needed after activation. Applies with RNC versions starting from RN5.0. The default value is true. This argument is optional.

-flexiTRSUploadAfterActivate

Specifies if FTM upload is needed after activation. Applies with RNC versions up to RN4.0. The default value is true. This argument is optional.

-rncUploadAfterActivate

Specifies if RNC upload is needed after activation. The default value is true.

-detailedProvFBNeeded

Specifies whether user wants to see detailed feedback about WCDMA provisioning.

-atmContentInUse

Specifies if ATM-related objects of an RNC are handled with a provisioning operation. The default value is false. This argument is optional.

-btsContentInUse

Indicates if FlexiBTS Site Configuration and Transport data or Ultra/MetroBTS Site Configuration data of RNC are handled with a provisioning or upload operation. Applies with RNC versions starting from RN5.0. The default value is false. This argument is optional.

-ftmContentInUse


-ipContentInUse

Specifies if IP-related objects of an RNC are handled with a provisioning operation. The default value is false. This argument is optional.

-rncAxcContentInUse


-rnwContentInUse

Specifies if RNW-related objects of an RNC are handled with a provisioning operation. The default value is true. This argument is optional.

-signalingContentInUse

Indicates if Signaling related objects of an RNC are handled with a provisioning or upload operation. The default value is false. This argument is optional.

-lteContentInUse

Indicates if LTE related objects are handled with a provisioning operation. The default value is true. This argument is optional.

Table 16

Command line options for plan provisioning (Cont.)

DN03453584 Issue 1-0

Id:0900d80580a02f79

57




Explanation

-ihspaBTSSCContentInUse

Indicates if Flexi Direct related BTSSC objects are handled with a provisioning or upload operation. The default value is true. This argument is optional.

-lteCellLockingNeeded

Specifies if LTE automatic locking is performed when parameter modification requires object locking or BTS restart. Not valid for FTM modifications. The default value is true. This argument is optional.

-forceUploadAfterActivate

Specifies if ATM/IP fragments in RNC are needed to be uploaded. The default value is false.

-MRBTSUploadAfterActivate

Specifies if MRBTS upload is needed after LTE plan activation. The default value is true. This argument is optional. Valid only for RL10.

-rnwActivationMode

Specifies the RNW activation mode for RNW activation operation. The allowed values are 1, 2, and 3. Value 1 is Safe mode, 2 is Normal mode, and 3 is Fast mode. The default value is 1, Safe mode. This argument is optional.

-backupPlanName

Specifies a backup plan name. Default value is Backup_plan. This argument is optional

-enablePriorityOperation

Specifies whether operation is run with priority. Priority operations are allowed only for administrators and for RNC RNW Activate operations. Before running a priority operation RNC RNW operation queue must be paused and RNC must be free to handle the operation. The default value is false. This argument is optional.

-ihspaTransportUploadAfterActivate

Specifies if upload of Flexi Direct fragments controlled by Transport Licences needed after activation. The default value is true.This argument is optional.

-coreUploadAfterActivateNeeded

Specifies if core network upload is needed after activation. The default value is true. This argument is optional.

-coreGenerateMmls

Specifies if MML commands are generated to feedback. The default value is false. This argument is optional.

-coreStopAtFirstError

Specifies if operation should stop after first error is encountered. The default value is true. This argument is optional.

-splitIntoSuccessfulAndFailedPlans

Specifies that separate plans are generated for successful and failed MRBTSs if errors are found during validation. The default value is false. This argument is optional.

provisionOnlyAfterSuccessfulValida tion

Specifies that MRBTSs are provisioned only after successful LTE validation. Applies to LTE objects only. The default value is false. This argument is optional.

-validateBeforePreactivationIHSPA

Specifies if validation is enabled for Flexi Direct FlexiBTS plan before Activate and Pre-Activate provisioning operations. Default value is true. This argument is optional.

-validateBeforePreactivationForLTE

Specifies if validation is enabled for LTE plan before Activate and Pre-Activate provisioning options. Default value is true. Argument is optional.

Table 16

58

Command line options for plan provisioning (Cont.)

Id:0900d80580a02f79

DN03453584 Issue 1-0



Example of plan provisioning To provision a plan to the entire network (PLMN-PLMN), with network elements locked during download, forced handover taking place within 120 seconds and GPRS disabled during download, enter the following command: [omc]$ racclimx.sh -op Provision -gprsDisablingAllowed true gsmForcedHOTimeLimit 120 -lockingAllowed true -planName PLMN_plan -v To provision a plan to certain network elements without locking allowed: [omc]$ racclimx.sh -op Provision -gprsDisablingAllowed false -DN PLMN-PLMN/RNC-120,PLMN-PLMN/RNC-2000,PLMN-PLMN/RNC-22 lockingAllowed false -planName PLMN_plan -v Example of Flexi Direct plan provisioning To provision a plan to Flexi Direct elements without transport uploading after activation, enter the following command: [omc]$ racclimx.sh -op Provision ihspaTransportUploadAfterActivate false -DN PLMN-PLMN/GOMS-200, PLMN-PLMN/GOMS-300 -planName Ihspa_plan -v Example of core network plan provisioning To provision a plan to core network elements without uploading after activation, without stopping operation after first error, and with generating the MML commands to feedback, enter the following command: [omc]$ racclimx.sh -op Provision –coreUploadAfterActivateNeeded false –coreStopAtFirstError false –coreGenerateMmls true -DN PLMN-PLMN/MSC-200, PLMN-PLMN/MGW-300 -planName core_plan -v

g 11.3.2.3


Validating RNC ATM/IP plan content after pre-activation It is necessary to validate the plan content in the RNC after pre-activation (download) to make sure that the plan can be activated, because local changes might have been made during the time between pre-activation and activation. The starting parameters

Explanation

-op

Choose IPA_Validation for this operation.

-v


-planName


-ipContentInUse

Specifies if IP-related objects of an RNC are handled with a validation operation. The default value is false. This argument is optional.

-atmContentInUse

Specifies if ATM-related objects of an RNC are handled with a validation operation. The default value is false. This argument is optional.

Table 17

DN03453584 Issue 1-0

Command line options for the IPA_Validation operation

Id:0900d80580a02f79

59



Example of RNC ATM/IP plan content validation in the RNC To validate plan content in the RNC after pre-activation, enter the following command: [omc]$ racclimx.sh -op IPA_Validation -v -planName

11.3.2.4

Activating the pre-activated plan for RNC RNW, AXC, FTM, Flexi Direct, WBTS SC and LTE The starting parameters

Explanation

-op

Choose Activate_Pre-Activation for this operation.

-v


-DN


-planName


-lockingAllowed

Specifies whether locking is allowed or not. The default value is true. This argument is optional.

-btsContentInUse

Indicates if FlexiBTS Site Configuration and Transport data or Ultra/MetroBTS Site Configuration data of RNC are handled with a provisioning or upload operation. Applies with RNC versions starting from RN5.0. The default value is false. This argument is optional.


Specifies whether BTS site configuration data and Flexi transport data upload is needed after activation. Applies with RNC versions starting from RN5.0. The default value is true. This argument is optional.


Specifies if FTM upload is needed after activation. Applies with RNC versions up to RN4.0. The default value is true. This argument is optional.

-ftmContentInUse



Specifies if FTM upload is needed after activation. The default value is true. This argument is optional.

-rncAxcContentInUse


-axcUploadAfterActivation

Specifies if AXC upload is needed after activation. The default value is true.

Table 18

60

Command line options for activating the pre-activated plan

Id:0900d80580a02f79

DN03453584 Issue 1-0




Explanation

-lteContentInUse

Indicates if LTE related objects are handled with a provisioning or upload operation. This argument should be used only when creating or deleting objects, because of automatic locking feature when modifying objects. The default value is true. This argument is optional.

-MRBTSUploadAfterActivate

Specifies if MRBTS upload is needed after LTE plan activation. The default value is true. This argument is optional. Valid only for RL10.

ihspaTransportUploadAfterActiv ate

Specifies if upload of Flexi Direct fragments controlled by Transport Licence is needed after activation. The default value is true. This argument is optional.

-rnwContentInUse

Indicates if RNW related objects of an RNC are handled with a provisioning or upload operation. The default value is true. This argument is optional.

Table 18

Command line options for activating the pre-activated plan (Cont.)

Example of activating the pre-activated Flexi Direct plan To activate the pre-activated plan to Flexi Direct elements without uploading transport after activation, enter the following command: [omc]$ racclimx.sh -op Activate_Pre-Activation ihspaTransportUploadAfterActivate false -DN PLMN-PLMN/GOMS-200, PLMN-PLMN/GOMS-300 -planName Ihspa_plan -v

11.3.2.5

Activating the pre-activated RNC ATM/IP plan When the RNC ATM/IP plan content in the RNC has been pre-activated (downloaded) and validated, it can then be activated. The starting parameters

Explanation

-op

Choose IPA_Activation for this operation.

-v


-planName


-ipContentInUse

Specifies if IP-related objects of an RNC are handled with an activation operation. The default value is false. This argument is optional.

-atmContentInUse

Specifies if ATM-related objects of an RNC are handled with an activation operation. The default value is false. This argument is optional.

-rnwContentInUse

Specifies if RNW-related objects of an RNC are handled with an activation operation. The default value is false. This argument is optional.

Table 19

DN03453584 Issue 1-0

Command line options for the IPA_Activation operations

Id:0900d80580a02f79

61




Explanation

-rncUploadAfterActivate

Specifies if RNC upload is needed after activation. The default value is true.

Table 19

g

Command line options for the IPA_Activation operations (Cont.)

If only RNWContent is activated via this operation, validation is not needed. Example of RNC ATM/IP activation after the pre-activation To activate the plan after pre-activation and validation in the RNC, enter the following command: [omc]$ racclimx.sh -op IPA_Activation -v -planName -ipContentInUse true -atmContentInUse true

11.4

Exporting and importing plans, actual configuration and templates The plan import operation reads the imported plan configuration file from the $VARROOT/global/racops/import Connectivity Server directory. The import operation writes log files into the $VARROOT/global/racops/logs Connectivity Server directory. Actual export, plan export, and template export operations write the exported configuration files into the $VARROOT/global/racops/export Connectivity Server directory. Import operation logs The import operation writes three different log files from import operations: • •

•

The error log contains information about managed objects that cannot be imported. The warning log contains information about events that do not prevent managed objects from being imported but are considered to be planning errors, for example, the imported managed object contains an unknown parameter or has a parameter whose value is out of range. The full import log contains all warnings and errors that have occurred during the import operation.

Log files produced by import operations are user-dependent. Separate log files are written for each user and plan configuration file combination. If, however, the same user imports the same configuration file several times, the last log is appended to the previous ones. Naming convention for log files The naming convention for log files is: racpmg___.txt For example: if the omc user imports a configuration file test.xml, the import operation provides three log files into $VARROOT/global/racops/logs: racpmg_omc_test.sml_err.txt racpmg_omc_test.sml_war.txt racpmg_omc_test.sml_log.txt

62

Id:0900d80580a02f79

DN03453584 Issue 1-0



CSV profile file locations Profile files for export are searched for from the following directories in the listed order: $ETCROOT/custom/conf/rac/profiles $VARROOT/global/racops/export $ETCROOT/rac/conf/profiles Profile files for import are searched for from the following directories in the listed order: $ETCROOT/custom/conf/rac/profiles $VARROOT/global/racops/import $ETCROOT/rac/conf/profiles Running the export and import operations

g

Once active, the import and export operation status can be viewed from the CM Operations Manager Operation History view. Operation feedback can also be seen from the Linux command line by adding the -v argument to the start command of an operation.

g

If a value such as a file name or plan name contains spaces, use quotation marks around it. For example, the plan name New Plan would be entered into a command as follows: -planName ”New Plan”


Explanation

-op

Choose Import_Export for this operation.

-v


-DN


-fileFormat

The format of the import or export file: RAML2.0 (default) or CSV. NOTE: CSV format is not supported for template export or template import operation. Specifies a file name. In case of planImport or templateImport this parameter or inputFile must be specified.

-fileName

The name of the import or export file. Note: Before importing plans, make sure the files you want to import are stored in the following directory: $VARROOT/global/racops/import The results of export are written to the following directory: $VARROOT/global/racops/export -importExportOperation

Defines the type of the import or export operation:

• •

planImport, templateImport planExport, actualExport, templateExport, referenceExport

See examples below the table.

Table 20

DN03453584 Issue 1-0

Command line options for the export and import operations

Id:0900d80580a02f79

63




Explanation

-inputFile

Specifies a full file path for the planImport or templateImport operation. This parameter or the fileName parameter must be filled. If both are present then the inputFile is used.

-csvProfile

Specifies the name of the XML-formatted profile file that is used as the structure for CSV (Comma Separated Values) data files.

-includeSiteInfo

Specifies if site information should be included in the operation. The default value is false.

-includeMaintenanceregionInfo

Specifies if maintenance region information should be included in the operation.

-planner

Specifies if Planner-specific parameters should be added to the operation. The default value is false.

-mergeImport

Specifies if the imported plan should be merged to an existing plan. The default value is false.

-UIValues

Specifies if file using user interface values in parameters is imported or exported. If this parameter is not defined internal values are used. The value is true or false. NOTE: user interface values are not supported for template export or template import operation.

-btsm

Specifies if related BTSM objects are included in the operation. The default value is false.

-setSystemTemplate

Specifies if the system template is assigned to imported objects when no other template is defined. The default value is true.

-planName


-templateName

Specifies a list of template names that are included in the operation. Multiple template names are comma-separated.

-templateClass

Specifies a list of class abbreviations for the templates to be included in the operation, if the templateName argument is not given. The abbreviations are comma-separated, for example:-templateClass NOKRNC:WCEL,NOKRNC:ADJS,NOKRNC:ADJI .

-classFilter

Specifies a list of managed object class abbreviations used to scope the operation. Multiple managed objects are comma-separated, for example: classFilter NOKRNC:WCEL,NOKRNC:ADJS,NO KRNC:ADJI

-sitesOnly

Specifies if only site information is imported. The default value is false.

-incomingAdjacencies

Specifies if incoming adjacencies are included in the operation. The default value is false.

Table 20

64

Command line options for the export and import operations (Cont.)

Id:0900d80580a02f79

DN03453584 Issue 1-0




Explanation

validateAgainstReferenceConfi guration

Indicates that a plan is imported on the top of Reference Configuration. Default value is false. This argument is optional.

useQualifiedClassAbbreviation

Specifies whether qualified class abbreviations are used in export operation.

-siteTemplateImport

Specifies if the plan import is treated as site template import. This argument is optional.

-skipExisting

Specifies if existing objects are overwritten in create operation. This argument is optional.

-recreate

Allow recreate objects in plan for core. This argument is optional.

-prioritizeRealCells

Specifies if real cells are prioritized over external cells in cell identification. This argument is optional.

-showImportFeedbacks

Specifies if import feedback should be displayed. This argument is optional.

useObjectOperationDefinedInIm portFile

If true, object operation (create, update, delete) is set like defined in import file. If true and operation is missing from import file, create operation is set. If false, object operation is set based on object existence in NetAct database.

Table 20

Command line options for the export and import operations (Cont.)

Example of export The following command exports actual configuration from the entire network to an XML file (RAML2.0):

g

In commands, enter the file format as “RAML2” instead of “RAML2.0”. [omc]$ racclimx.sh -op Import_Export -fileFormat RAML2 importExportOperation actualExport -fileName ACTUAL_EXPORT_RESULT.xml To export actual configuration from all managed objects under a WBTS: [omc]$ racclimx.sh -op Import_Export -fileFormat RAML2 importExportOperation actualExport -DN PLMN-PLMN/RNC-1000/WBTS-5 -fileName ACTUAL_EXPORT_RESULT.xml To export actual configuration with all the WCELs and ADJSs from an RNC: [omc]$ racclimx.sh -op Import_Export -fileFormat RAML2 importExportOperation actualExport -DN PLMN-PLMN/RNC-1000 classFilter NOKRNC:WCEL,NOKRNC:ADJS -fileName ACTUAL_EXPORT_RESULT.xml To export a plan with all the WCELs and ADJSs from an RNC: [omc]$ racclimx.sh -op Import_Export -fileFormat RAML2 importExportOperation planExport -DN PLMN-PLMN/RNC-1000 classFilter NOKRNC:WCEL,NOKRNC:ADJS -fileName ACTUAL_EXPORT_RESULT.xml -planName [PlanName] CSV plan export command line example, using quoted plan name with spaces:

DN03453584 Issue 1-0

Id:0900d80580a02f79

65



[omc]$ racclimx.sh -op Import_Export -fileFormat CSV importExportOperation planExport -csvProfile myprofile.xml fileName PlannedConfiguration_test.csv -planName “Mavu Test Plan 01” To export XML template to a file: [omc]$ racclimx.sh -op Import_Export -importExportOperation templateExport -templateName BTS_template -fileName TEMPLATE_EXPORT.xml -v To export multiple XML templates to a file: [omc]$ racclimx.sh -op Import_Export -importExportOperation templateExport -templateName BTS_template,TRX_template,ADCE_template -fileName TEMPLATE_EXPORT.xml -v Example of import To import an XML-formatted plan to a new plan: [omc]$ racclimx.sh -op Import_Export -fileFormat RAML2 importExportOperation planImport -fileName PlannedConfiguration_test.xml -planName [PlanName] To merge an XML-formatted imported plan to an existing plan: [omc]$ racclimx.sh -op Import_Export -fileFormat RAML2 importExportOperation planImport -fileName PlannedConfiguration_test.xml -planName [PlanName] -mergeImport true CSV plan import command line example, using quoted plan name with spaces: [omc]$ racclimx.sh -op Import_Export -fileFormat CSV importExportOperation planImport -csvProfile myprofile.xml fileName PlannedConfiguration_test.csv -planName “Test Plan” To import XML template from a file: [omc]$ racclimx.sh -op Import_Export -importExportOperation templateImport -fileName ADCE_template.xml -v

g 11.5

For more information on importing and exporting by using the CM Operations Manager user interface, see CM Operations Manager Help.

Deleting plans The starting parameters

Explanation

-op

Choose planDeletion for this operation.

-planName

Specifies the plan name in the NetAct Configurator database to be deleted.

-v


Table 21

66

Command line options for the plan delete operations

Id:0900d80580a02f79

DN03453584 Issue 1-0


g


If a plan name contains spaces, use quotation marks around it. For example, the plan name New Plan would be entered into a command as follows: -planName “New Plan“. Example of plan deletion The following command deletes a plan from the Configurator database: [omc]$ racclimx.sh -op planDeletion -planName Example_plan -v

g 11.6 11.6.1

For more information on deleting plans using the CM Operations Manager user interface, see To delete a plan in CM Operations Manager Help.

Comparing plans Comparing plans to actual configuration The starting parameters

Explanation

-op

Choose Compare for this operation.

-v


-planName


-deltaPlanName

Specifies a plan name that will be created from the differences found when comparing the plan against the actual configuration. This argument is optional.

-feedbackLevel

Specifies the level of feedback in the Compare operation:

• • •


The default value is Summary. This argument is optional.

Table 22

Command line options for the compare operations

Example of plan comparison against the actual configuration The following command compares a plan against the actual configuration: [omc]$ racclimx.sh -op Compare -planName Example_plan deltaPlanName Delta_plan -feedbackLevel objectLevel -v

g 11.7

For more information on comparing plans to actual configuration by using the CM Operations Manager user interface, see CM Operations Manager Help.

Send To Network operations This operation is used to send changes specified in input file directly to the network. It is supported only for RNC RNW and Flexi Direct RNC RNW objects. Dependant objects (e.g. adjacencies) of the managed object are automatically created/deleted/updated, except for the adjacencies in the LTE BTS. This operation requires Direct activation for RNC license and additionally you need to have Send to network permission to be able to perform it.

DN03453584 Issue 1-0

Id:0900d80580a02f79

67



If the planned parameter value equals to its actual value, no modification is sent to network. If the planned parameter value differs from its actual value, modification is sent to network. The following table describes command line options for running Send To Network operation. The starting parameters

Explanation

-op

Choose Send_To_Network for this operation.

-v


-fileName

Specifies the name of the RAML2 file containing Managed Object(s) to be created/deleted/updated. The input file (xml) must contain only one managed object, but may contain multiple parameters. Parameter values must be of internal format (not user interface format). Qualified class abbreviations must be used (e.g. NOKRNC:WCEL instead of WCEL).

-path

Specifies the directory of the input file.

Table 23

Command line options for Send To Network operations

The following example shows a valid RAML2 input file for Send to Network command line operation:

1

11.8

Policy-Based Compare operations The following table describes command line operations for running Policy-Based Compare operation. Parameter

Choose Policy_Based_Compare for running Policy-Based Compare operation.

–op

Table 24

68

Description

Command line options for running Policy-Based compare operation

Id:0900d80580a02f79

DN03453584 Issue 1-0



Parameter

Description

–DN

Specifies the scope of the Policy-Based Compare operation (comma separated Distinguished Names without spaces).

-targetConfiguration

Specifies the target configuration of this operation. Possible values are: • •

actual reference

The default value is actual. This argument is optional. -excludedItemsFile

Indicates the name of the file which specifies the templates, adaptations, MO classes and/or MO class parameters which should be excluded in the comparison operation. This argument is optional.

-enableExceptions

Indicates that MOs in exception plans are considered in comparison. The default value is true. This argument is optional.

-deltaPlanName

Specifies a plan name that will be created of the found differences when comparing configuration against templates. This argument is optional.

-feedbackLevel

Specifies the level of feedback. Possible values are: • • •


The default value is summaryLevel. This argument is optional. Table 24

Command line options for running Policy-Based compare operation (Cont.)

Example of running Policy-Based Compare operation: [omc]$ racclimx.sh -op Policy_Based_Compare -DN PLMN-PLMN/RNC-14 -excludedItemsFile Excluded_Items.xml -deltaPlanName Delta_plan -feedbackLevel objectLevel

11.9

Reference Configuration related command line operations This chapter provides information on the command line operations for reference configuration.

DN03453584 Issue 1-0

Id:0900d80580a02f79

69


11.9.1


Initializing Reference Configuration The starting parameters

Explanation

-op

Choose Init_Reference_Conf to initialize the reference configuration for all the objects in actual configuration.

-DN


-classFilter

Specifies a list of class abbreviations (comma separated) that scopes the operation. This argument is optional.

-initOverwriteReference

Choose true if a complete re-initialization is needed. After re-initialization the reference configuration is identical with the actual configuration. Choose false to initialize only objects which exist in actual configuration but not in reference configuration. No deletions or modifications are done to existing objects in reference configuration then. Default value is false. This argument is optional.

Table 25

Command line options for initializing Reference Configuration

Example of initializing reference configuration To initialize reference configuration which is identical with the actual configuration, enter the following command: [omc]$ racclimx.sh -op Init_Reference_Conf -DN PLMNPLMN/RNC-1000 -initOverwriteReference true

11.9.2

Generating delta The starting parameters

Explanation

-op

Choose Delta_Generation to compare actual and reference configurations and to find out differences between them.

-DN


Table 26

Command line options for generating delta

Example of generating delta To generate delta, enter the following command: [omc]$ racclimx.sh -op Delta_Generation -DN PLMN-PLMN/RNC1000

70

Id:0900d80580a02f79

DN03453584 Issue 1-0


11.9.3


Exporting delta The starting parameters

Explanation

-op

Choose Delta_Export to export selected deltas to CSV file.

-DN


-classFilter

Specifies a list of qualified class abbreviations (comma separated) that scopes the operation. This argument is optional.

-fileName

Specifies a file name.

Table 27

Command line options for exporting delta

Example of exporting delta To export delta, enter the following command: [omc]$ racclimx.sh -op Delta_Export -DN PLMN-PLMN/RNC-1000 file_Name Example_file

11.9.4

Merging plans to reference configuration The starting parameters

Explanation

-op

Choose Merge_Plan to merge a new configuration plan to reference configuration. This option creates new objects, removes deleted objects introduced in the plan, and updates existing objects with the new values to reference configuration.

-planName


-mergeNoFallback

Specifies if the fallback plan is not needed for the merge. Default value is false. When merging a fallback plan choose true because a fallback plan cannot be created for another fallback plan. This argument is optional.

Table 28

Command line options for merging plans to reference configuration

Example of merging a plan to reference configuration To merge a plan to reference configuration and to create a fallback plan for the merge, enter the following command: [omc]$ racclimx.sh -op Merge_Plan -planName Example_plan mergeNoFallback false

DN03453584 Issue 1-0

Id:0900d80580a02f79

71


11.9.5


Committing reference alignments The starting parameters

Explanation

-op

Choose Commit_Align_Reference to commit all reference alignments done in CM Reference user interface by all users in the system.

-userName

Specifies a user name.

Table 29

Command line options for committing reference alignments

Example of committing reference alignments To commit reference alignments, enter the following command: [omc]$ racclimx.sh -op Commit_Align_Reference

11.9.6

Committing network alignments The starting parameters

Explanation

-op

Choose Commit_Align_Network to create a plan containing all the network alignments done in CM Reference user interface by all users in the system.

-planName


-userName

Specifies a user name.

Table 30

Command line options for committing network alignments

Example of committing network alignments To commit network alignments, enter the following command: [omc]$ racclimx.sh -op Commit_Align_Network -planName PLMN_plan

11.10

CM History related command line operations This chapter provides information on the command line operations for CM History.

11.10.1

Initializing CM History configuration The starting parameters

Explanation

-op

Choose Init_History to initialize the CM History configuration for all the objects in actual or reference configuration.

-v


Table 31

72

Command line options for initializing CM History configuration

Id:0900d80580a02f79

DN03453584 Issue 1-0




Explanation

-configuration

Specifies if the CM History configuration is initialized for actual configuration or reference configuration. This argument is optional. Possible values are actual or reference. The default value is actual.

Table 31

Command line options for initializing CM History configuration (Cont.)

Example of initializing the CM History configuration To initialize the CM History configuration for the reference configuration, enter the following command: [omc]$ racclimx.sh -op Init_History -configuration reference

11.10.2

Synchronizing CM History configuration This operation synchronizes the current objects in the CM History with the objects of the given configuration. The starting parameters

Explanation

-op

Choose Synchronize_History to synchronize the current objects in the CM History with the objects of the given configuration.

-DN


-v


-configuration

Specifies if the CM History configuration is synchronized with the actual configuration or reference configuration. This argument is optional. Possible values are actual or reference. The default value is actual.

Table 32

Command line options for synchronizing CM History configuration with actual configuration or reference configuration

Example of synchronizing the CM History configuration To synchronize the CM History with the actual configuration, enter the following command: [omc]$ racclimx.sh -op Synchronize_History -configuration actual

11.10.3

Generating CM History differences tabular report This operation generates the CM History differences tabular report for the selected configuration for the given period of time. The results are stored in the file.

DN03453584 Issue 1-0

Id:0900d80580a02f79

73




Explanation

-op

Choose Diff_History to generate the tabular report with the managed objects / parameters changes which occurred in the given period of time.

-DN


-configuration

Specifies if the tabular report is generated for the actual configuration or reference configuration. This argument is optional. Possible values are actual or reference. The default value is actual.

-classFilter

Specifies a list of qualified class abbreviations (comma separated) that are taken into account in the tabular report. This argument is optional.

-periodStart

Specifies the start date of the period for which the tabular report will be created.

-periodEnd

Specifies the end date of the period for which the tabular report will be created.

-pastInterval

Specifies period interval as a specified number of pastUnit. This argument is optional. Exclude using periodStart/periodEnd attribute. The pastInterval variable is mandatory if you specify pastUnit.

-pastUnit

Specifies time period unit for pastInterval. The available values are [D | W | M | Y] for day/week/month/year. This argument is optional. Exclude using periodStart/periodEnd attribute.

-maintenanceRegion

Specifies Maintenance Region ID which will be used in filtering changes. This argument is optional.

-site

Site Admin ID which will be used in filtering changes. This argument is optional.

-changeOrigin

Specifies a filter for changing origin. This argument is optional.

-dnContains

Specifies part of the Distinguished Name. Scope of the operation will be Managed Objects whose DNs contain a given DN specified part. Exclude DN attribute. This argument is optional.

-fileName

Specifies the name of the file where the tabular report result will be stored.

Table 33

Command line options for generating the CM History differences tabular report.

Example of generating the CM History tabular report To generate the CM History tabular report for actual configuration, enter the following command: [omc]$ racclimx.sh -op Diff_History -DN PLMN-PLMN/RNC-1 -configuration actual -periodStart 21/3/2011 -periodEnd 21/5/2011 -maintenanceRegion MR-NWI3 -changeOrigin example -fileName diff_report

74

Id:0900d80580a02f79

DN03453584 Issue 1-0


11.10.4


Removing data from CM History This operation removes all irrelevant data from CM History database at a given time. The starting parameters

Explanation

-op

Choose Remove_History to remove all irrelevant data from CM History database at a given time.

-time

Specifies the time in which all irrelevant data will be removed from CM History database. This argument is mandatory.

Table 34

Command line options for removing irrelevant data from CM History database

Example of removing irrelevant data from CM History database To remove all irrelevant data from CM History database, enter the following command: [omc]$ racclimx.sh -op Remove_History -time 2011-12-21

11.11

Workflow related command line operations This chapter provides information on workflow related command line operations.

g

racclimx.sh process is not enough to call workflow related operations. To call workflow related operations additional workflow xml file have to be specified: -opsFile $ETCROOT/rac/conf/opdefs/ops/workflow_ops.xml

11.11.1

Creating workflow related plans

11.11.1.1

Creating a plan based on COCO


Explanation

-op

Choose axc_ftm_reconfig for this operation.

-v


-masterPlanName


-fileChooser

Browse File System to specify input file name. This argument is optional.

Table 35

Workflow related command line operations for creating a plan based on COCO Example of creating a plan based on COCO To create a plan based on COCO, enter the following command: [omc] $ racclimx.sh -op axc_ftm_reconfig -v -masterPlanName -fileChooser

DN03453584 Issue 1-0

Id:0900d80580a02f79

75


11.11.1.2


Creating a new COCO reconfiguration plan


Explanation

-op

Choose generate_coco_plan for this operation.

-v


-masterPlanName


-fileChooser


Table 36

Workflow related command line operations for creating a new COCO? reconfiguration plan Example of creating a new COCO reconfiguration plan To create a new COCO reconfiguration plan, enter the following command: [omc] $ racclimx.sh -op generate_coco_plan -v -masterPlanName -fileChooser

11.11.1.3

Creating a new transport reconfiguration plan This operation creates a new transport reconfiguration plan with the given name based on the selected input file. It provides a possibility to generate ATM removal plan for the RNC when migrating into IP-based lub.


Explanation

-op

Choose generate_ip_transport_plan for this operation.

-v


-removeOetMlink

It specifies if O&M link should be kept. The default value is true. This argument is optional.

-removeCOCO

Specifies if COCO should be removed. The default value is true. This argument is optional.

-fileChooser


Table 37

Workflow related command line operations for creating a new transport reconfiguration plan Example of creating a new COCO reconfiguration plan To create a new transport reconfiguration plan, enter the following command: [omc] $ racclimx.sh -op generate_ip_transport_plan -v removeOetMLink true -removeCOCO true -fileChooser

11.11.1.4

Merging into selected modification plan the related _CocoAxcFtmPlan and _CocoDeletion plan This operation merges into selected modification plan the related _CocoAxcFtmPlan and _CocoDeletion plan in the Configurator database. You can use it if you want to pro-

76

Id:0900d80580a02f79

DN03453584 Issue 1-0



vision the IP and ATM layer changes in one provisioning operation in the RNCs and AXCs/FTMs. The starting parameters

Explanation

-op

Choose merge_atm_changes_with_ip_plan for this operation.

-v


-keepOldPlans

It specifies if old plans should be kept. The default value is true. This argument is optional.

-masterPlanName


-moOverwrite

If overlapping objects are found and the value of the attribute is no, the system leaves the merge undone and inform the user about the reason. Otherwise, the system complete the merge and overwrite the overlapping objects in the master plan. The default value is no.

Table 38

Workflow related command line operations for merging into selected modification plan the related _COCOdeletion plan Example of merging into selected modification plan the related _CocoAxcFtmPlan and _CocoDeletion plan To merge into selected modification plan the related _CocoAxcFtmPlan and _CocoDeletion plan, enter the following command: [omc] $ racclimx.sh -op merge_atm_changes_with_ip_plan -v keepOldPlans true -masterPlanName -omOverwrite

11.11.2 11.11.2.1

Provisioning workflow related plans Provisioning a plan generated from a COCO modification plan with the suffix _CocoAxcFtmPlan This operation prepares and provisions in the AXC(s) and/or FTM(s) the plan generated from the COCO modification plan with the suffix _CocoAxcFtmPlan. It uploads the configuration from the AXC(s) and FTM(s) once the provisioning is finished.


Explanation

-op

Choose provision_axc_ftm_reconfig for this operation.

-v


-masterPlanName


-feedbackLevel

Specifies the level of feedback (summaryLevel/objectLevel/ parameterLevel). The default value is summaryLevel. This argument is optional.

Table 39

Workflow related command line operations for merging into selected modification plan with the suffix _CocoAxcFtmPlan

DN03453584 Issue 1-0

Id:0900d80580a02f79

77



Example of provisioning a plan generated from a COCO modification plan with the suffix _CocoAxcFtmPlan To provision a plan generated from a COCO modification plan with the suffix _CocoAxcFtmPlan, enter the following command: [omc] $ racclimx.sh -op provision_axc_ftm_reconfig -v masterPlanName -feedbackLevel

11.11.2.2

Provisioning in AXCs and FTMs the plan with the suffix _CocoAxcFtmPlan This operation provisions in AXCs and FTMs the plan with the suffix _CocoAxcFtmPlan. You can use it when "Merge ATM Changes with IP Transport Plan" was not run and you want to provision the ATM layer changes separately.


Explanation

-op

Choose provision_atm_removal_in_axc_ftm for this operation.

-v


-masterPlanName


-feedbackLevel


-ipContentInUse

Indicates if IP related objects of an RNC are handled with a provisioning or upload operation. The default value is false. This argument is optional.

-atmContentInUse

Indicates if ATM related objects of an RNC are handled with a provisioning or upload operation. The default value is false. This argument is optional.

-rnwContentInUse

Indicates if RNW related objects of an RNC are handled with a provisioning or upload operation. The default value is false. This argument is optional.

-ftmContentInUse

Indicates if FTM related objects are handled with a provisioning or upload operation. The default value is true. This argument is optional.

-provisionAXC

It includes AXC. The default value is true. This argument is optional.

-provisionFTM

It includes FTM. The default value is true. This argument is optional.

Table 40

Workflow related command line operations for provisioning in AXCs and FTMs the plan with the suffix _CocoAxcFtmPlan Example of provisioning in AXCs and FTMs a plan with the suffix_CocoAxcFtmPlan To provision in AXCs and FTMs a plan with the suffix _CocoAxcFtmPlan, enter the following command: [omc] $ racclimx.sh -op provision_atm_removal_in_axc_ftm -v masterPlanName -feedbackLevel ipContentInUse false -atmContentInUse false rnwContentInUsefalse -ftmContentInUse true -provisionAXC true provisionFTMtrue

78

Id:0900d80580a02f79

DN03453584 Issue 1-0


11.11.2.3


Provisioning a plan with the suffix _CocoDeletion in RNCs This operation provisions in RNCs the plan with the suffix _CocoDeletion. You can use it when "Merge ATM Changes with IP Transport Plan" was not run and you want to provision the COCO and O&M link deletions separately.


Explanation

-op

Choose provision_atm_removal_in_axc_ftm for this operation.

-v


-masterPlanName


-feedbackLevel


-ipContentInUse

Indicates if IP related objects of an RNC are handled with a provisioning or upload operation. The default value is true. This argument is optional.

-atmContentInUse

Indicates if ATM related objects of an RNC are handled with a provisioning or upload operation. The default value is true. This argument is optional.

-rnwContentInUse


-ftmContentInUse

Indicates if FTM related objects are handled with a provisioning or upload operation. The default value is false. This argument is optional.

-provisionAXC

It includes AXC. The default value is false. This argument is optional.

-provisionFTM

It includes FTM. The default value is false. This argument is optional.

Table 41

Workflow related command line operations for provisioning the plan with the suffix _CocoDeletion in RNCs Example of provisioning a plan with the suffix _CocoDeletion in RNCs To provision a plan with the suffix _CocoDeletion in RNCs, enter the following command: [omc] $ racclimx.sh -op provision_atm_removal_in_rnc -v masterPlanName -feedbackLevel ipContentInUse true -atmContentInUse true -rnwContentInUsetrue -ftmContentInUse false -provisionAXC false -provisionFTM false

11.11.2.4

Provisioning a selected plan in RNCs This operation provisions the selected plan in the RNCs. The plan may contain RNW, IP and ATM layer data. In case "Merge ATM Changes with IP Transport Plan" operation has been run, COCO and O&M deletions are included in the plan. If not, COCO and O&M deletions are not included in the plan.


Explanation

-op

Choose provision_rnc_plan for this operation.

-v


Table 42

Workflow related command line operations for provisioning selected plan in RNCs

DN03453584 Issue 1-0

Id:0900d80580a02f79

79




Explanation

-masterPlanName


-feedbackLevel


-ipContentInUse

Indicates if IP related objects of an RNC are handled with a provisioning or upload operation. The default value is true. This argument is optional.

-atmContentInUse

Indicates if ATM related objects of an RNC are handled with a provisioning or upload operation. The default value is true. This argument is optional.

-rnwContentInUse


-ftmContentInUse

Indicates if FTM related objects are handled with a provisioning or upload operation. The default value is false. This argument is optional.

-provisionAXC

It includes AXC. The default value is false. This argument is optional.

-provisionFTM

It includes FTM. The default value is false. This argument is optional.

Table 42

Workflow related command line operations for provisioning selected plan in RNCs (Cont.) Example of provisioning a selected plan in RNCs To provision the selected plan in RNCs, enter the following command: [omc] $ racclimx.sh -op provision_rnc_plan -v -masterPlanName -feedbackLevel -ipContentInUse true -atmContentInUse true -rnwContentInUse true ftmContentInUse false -provisionAXC false -provisionFTM false

11.12

Starting consistency checks


Explanation

-op

Choose the operation to be performed:

• • •

Actual_Check for checking the actual configuration Reference_Check for checking the reference configuration Plan_Check for checking plans on top of the actual configuration

-v


-DN

(For Actual_Check and Reference_Check) Defines the scope of the operation (comma-separated Distinguished Names).

-planName

(For Plan_Check.) The name of the plan that is used in the operation.

-checkName

The name of the consistency check you want to run.

Table 43

80

Command line options for consistency checking

Id:0900d80580a02f79

DN03453584 Issue 1-0




Explanation

-ruleNames

The rule or rule set to be used in consistency check. Syntax:

• •

Nokia.[filename of rule].[rule name] or Nokia.[filename of ruleset group].[ruleset name]

The [filename of rule] is the name of the file where the rule is specified. It is always the same as the rule name. All rule files are stored in $ETCROOT/rac/conf/rules, so you can check the rule filenames there. The [filename of ruleset group] is the name of the file which groups the rule sets related to specific area. The following ruleset group files are available:

• • • • • •

BSC_sets RNC_sets MGW_sets MSC_sets MSS_sets SGSN_sets

The ruleset group files are located in the same directory as the rule files ($ETCROOT/rac/conf/rules). For a list of available rule sets, see section Rule sets in Rules and Rule Syntax for NetAct Configurator document. If you want to use multiple rules or rule sets in the check, separate them using comma, for example:

• •

Nokia.[filename of rule1].[rule name1], Nokia.[filename of rule2].[rule name2] or Nokia.[filename of ruleset group1].[ruleset name1],Nokia.[filename of ruleset group2].[ruleset name2]

Specifies the name for the correction plan. This argument is optional. correctionPlanName -emailAddress

Specifies the email address to which the results of the consistency check are sent. This argument is optional.

-maxResults

Defines the maximum result count for consistency checks. The default value is 10 000. This argument is optional.

Table 43

Command line options for consistency checking (Cont.) Example of starting consistency checks You can start a consistency check with a desired scope using the object’s Distinguished Name and rule set. [omc]$ racclimx.sh -op Actual_Check -DN [DNs] ruleNames Nokia.[filename of ruleset group].[ruleset name] checkName [check name]

-

For running the rules for 3G actual adjacency checking you can use the example shown below:

DN03453584 Issue 1-0

Id:0900d80580a02f79

81



[omc]$ racclimx.sh -op Actual_Check -checkName myCheck -DN PLMNPLMN -ruleNames Nokia.RNC_sets.ActualAdjacencyChecking_3G You can also define a correction plan where the corrections are done if errors are found during the consistency check: When a single rule is used: [omc]$ racclimx.sh -op Actual_Check -DN [DNs] ruleNames Nokia.[filename of rule].[rule name] checkName [check name] correctionPlanName [name of the correction plan] When a ruleset is used: [omc]$ racclimx.sh -op Actual_Check -DN [DNs] ruleNames Nokia.[filename of ruleset group].[ruleset name] checkName [check name] correctionPlanName [name of the correction plan] Examples of checking the planned configuration against the actual configuration You can check the target plan configuration on top of the actual configuration by using rule or rule set names and by defining the plan using the planName attribute. To do this, give the following command (the check is named by giving the argument): When a single rule is used: [omc]$ racclimx.sh -op Plan_check -planName [plan name] ruleNames Nokia.[filename of rule].[rule name] -checkName [check name] When a ruleset is used: [omc]$ racclimx.sh -op Plan_check -planName [plan name] ruleNames [filename of ruleset group].[ruleset name] checkName [check name] You can also check the target plan configuration on top of the actual configuration by defining a correction plan name: When a single rule is used: [omc]$ racclimx.sh -op Plan_check -planName [plan name] ruleNames Nokia.[filename of rule].[rule name] -checkName [check name] -correctionPlanName [name of the corrections plan] When a ruleset is used: [omc]$ racclimx.sh -op Plan_check -planName [plan name] ruleNames Nokia.[filename of ruleset group].[ruleset name] checkName [check name] correctionPlanName [name of the corrections plan]

g 11.13

For more information on making consistency checks with the CM Analyzer user interface, see CM Analyzer Help.

3GPP operations This section contains information about 3GPP operations.

82

Id:0900d80580a02f79

DN03453584 Issue 1-0



3GPP Upload The starting parameters

Explanation

-op

Choose 3GPP_Upload for this operation.

-v


-technologies

Specifies supported technologies (NOKBSC/NOKRNC/NOKMSC/NOKSGSN/NetActOMC). This argument is optional.

-fileName

Specifies a file name where configuration data in 3GPP format is uploaded. By default, files are located in $VARROOT/rac/rac3gp/work directory.

-scopeLevel

Defines how many levels of the object hierarchy to include. This argument is optional. Valid only for scope types BASE_NTH_LEVEL and BASE_SUBTREE.

-scopeType

Possible values: BASE_ONLY, BASE_NTH_LEVEL, BASE_SUBTREE, BASE_ALL. The default value is baseAll. This argument is optional.

-baseObject

3GPP DN of the base object to be uploaded.

-classFilter

Specifies a list of 3GPP classes (space separated) that scopes the operation. This argument is optional.

Table 44

Command line options for 3GPP upload

Example of 3GPP upload Use the following command to upload the whole Subnetwork: [omc]$ racclimx.sh -op 3GPP_Upload -baseObject SubNetwork=Nokia1 -scopeType BASE_ALL -fileName upload_file -v Use the following command to upload COCOs and WBTSs only [omc]$ racclimx.sh -op 3GPP_Upload -baseObject SubNetwork=Nokia1,ManagedElement=RNC-1 -fileName upload_file -technologies NOKRNC -classFilter RncFunction -v 3GPP download The starting parameters

Explanation

-op

Choose 3GPP_Download for this operation.

-v


-planName

The name of the plan that is created.

-fileName

Specifies a file name of the plan in 3GPP format that is downloaded. By default, files are located in $VARROOT/rac/rac3gp/work.

Table 45

DN03453584 Issue 1-0

Command line options for 3GPP download

Id:0900d80580a02f79

83




Explanation

-mergeImport

Specifies if the imported plan should be merged to an existing plan. The effect of this parameter depends on the planName parameter. If the value of this parameter is false and planName is given, the existing plan is replaced. If the value of this parameter is true and planName is given, the plan is merged. This argument is optional.

Table 45

Command line options for 3GPP download (Cont.)

Example of 3GPP download Use the following command to download 3GPP data to the network: [omc]$ racclimx.sh -op 3GPP_Download -planName Example_plan fileName Example_file -v For more information about 3GPP interfaces in NetAct, see 3GPP CORBA Bulk CM Northbound Interface Principles.

11.14

Restoring AXC configurations This section contains information on restoring AXC configurations. The following table lists the command line options for restoring AXC configurations. The starting parameters

Explanation

-op

Choose Restore_Configuration for this operation.

-v


-DN

Specifies the scope of the operation (comma separated Distinguished Names).

-amlFile

Specifies an input file name.

Table 46

Command line options for restoring AXC configurations

The given input file name specifies the name of the AML backup file containing the AXC restore configuration. The name of the input file, which is located in LinAS, must contain the full path. If the SCT Tool is installed, the path for AXC backup files should be: /var/opt/Nokia/shared/rac/sct/backup_sites/axc If the SCT Tool is not installed, the path for AXC backup files should be: /var/opt/Nokia/shared/rac/cmmaxc/backup_sites The AXC restore configuration file name includes the system ID and the timestamp, for example, AXC857_1139241193366.aml. Example of restoring AXC configuration The following command is an example of restore AXC configuration command: [omc]$ racclimx.sh -op Restore_Configuration -amlFile Example_file -DN PLMN-PLMN/AXC-1 -v

84

Id:0900d80580a02f79

DN03453584 Issue 1-0


11.15


Managing the Remote Electrical Tilt using command line This section describes command line operations related to Remote Electrical Tilt (RET) feature. For more information about the feature, see Managing Remote Electrical Tilt document. The following RET management commands can be run from the NetAct Configurator command line: • • • •

11.15.1 11.15.1.1

-op Upload -op Provision -op Calibrate (only for RET management in WCDMA networks) -op Binary_Download (only for RET management in WCDMA networks)

Command Line operations for RET management in WCDMA network Upload This operation uploads RET parameters during standard upload operation for the WBTS. Example of upload operation The following command uploads configuration without force option. racclimx.sh -op Upload -DN PLMN-PLMN/RNC-190/WBTS-967 btsContentInUse true For more information about Upload operation, see Uploading actual values chapter. For more information on how to upload actual configurations with the CM Operations Manager user interface, see CM Operations Manager Help.

11.15.1.2

Forced Upload This operation performs the ordinary upload preceded by synchronization of RETam data. This option may be used if there is a suspicion that the data in RETam database is not up to date. The Forced Upload performs the Synchronization operation in background. Example of Forced Upload operation With the following command you can initialize upload configuration with force option. racclimx.sh -op Upload -DN PLMN-PLMN/RNC-190/WBTS-967 forcedUpload true -btsContentInUse true For more information about Upload operation, see Uploading actual values chapter. For more information on how to upload actual configurations with the CM Operations Manager user interface, see CM Operations Manager Help.

11.15.1.3

Download This operation executes download of configuration file to RETam using plan file name. Provisioning RET plans is done by standard provisioning operation. Example of provisioning operation The following command provisions RET plans.

DN03453584 Issue 1-0

Id:0900d80580a02f79

85



racclimx.sh -op Provision -planName RETplan For more information about Provision operation, see Provisioning plans chapter. For more information on how to upload actual configurations with the CM Operations Manager user interface, see CM Operations Manager Help.

11.15.1.4

Download vendor specific configuration file This operation downloads the vendor specific configuration file to the RET.

g

This option is supported only by FlexiBTS.

Parameter

Description

–op

Choose Binary_Download for this operation.

–DN

Specifies the scope of the operation (comma separated RET Distinguished Names without spaces).

–binaryInputFile

Specifies the binary file name.

Table 47

Command line options for Binary Download operation

Example of binary download operation racclimx.sh -op Binary_download -DN PLMN-PLMN/RNC-190/WBTS967/BTSSC-1/RET-1 -binaryInputFile KA_739664_824-960.bin

11.15.1.5

Calibration This operation calibrates RET(s) under WBTS. Parameter

Description

–op

Choose Calibrate for this operation.

–DN

Specifies the scope of the operation (comma separated RET Distinguished Names without spaces).

Table 48

Command line options for Calibration operation

Example of calibration operation The following command starts Calibration operation with scope provided as DN parameter. racclimx.sh -op Calibrate -DN PLMN-PLMN/RNC-190/WBTS-967/BTSSC1/RET-1, PLMN-PLMN/RNC-190/WBTS-968/BTSSC-1/RET-1

86

Id:0900d80580a02f79

DN03453584 Issue 1-0


11.15.2 11.15.2.1


Command Line operations for RET management in LTE network Upload (with Command Line) This operation uploads RET parameters during standard Upload operation for the FlexiMultiradio BTS (eNB). Example of upload operation The following command uploads the configuration. racclimx.sh -op Upload -DN PLMN-PLMN/MRBTS-123 For more information about Upload operation, see Uploading actual values chapter. For more information on how to upload actual configurations with the CM Operations Manager user interface, see CM Operations Manager Help.

11.15.2.2

Download (with Command Line) Provisioning RET plans is done by standard Provision operation. Example of provisioning operation The following command provisions RET plans. racclimx.sh -op Provision -planName RETplan For more information about Provision operation, see Provisioning plans chapter. For more information on how to upload actual configurations with the CM Operations Manager user interface, see CM Operations Manager Help.

11.16

Administering RNC RNW and LTE iOMS queues RNC RNW and LTE iOMS plan operations are queued before executing them to the network. There is one queue per each RNC/iOMS. In case of LTE iOMS, configuration management operations to MRBTSs and PREBTSs are being queued. The following operations are put to queue if RNC or iOMS is busy when user starts the operation: • • •

Activate Pre-Activate Upload

The following plan operations fail immediately if RNC or iOMS is busy when user starts the operation: • •

Activate Pre-Activated Plan Fall Back RNC RNW (for RNC RNW only)

Note that in case of RNC, the operations for the following configurations are not queued: • • • •

RNC ATM/IP AXC FTM WBTS Site Configuration

In case of LTE iOMS, operations to all fragments are queued.

DN03453584 Issue 1-0

Id:0900d80580a02f79

87


11.16.1


Pausing/releasing an RNC RNW and LTE iOMS operation queue Administrator can pause the RNC RNW and iOMS operation queue so that none of the queueing operations is started to RNC/iOMS. Pausing the queue does not affect to the currently ongoing operation in the RNC/iOMS. Configurator users can start new RNC RNW or iOMS operations which will be put at the end of the queue without any notification about the paused state of the queue. If scheduled RNC RNW or iOMS operations are started those will also be put to the end of the queue.

g

After pausing the queue, statuses of all operations in the queue remain ‘Started’ in the Operation History tab of CM Operations Manager. When Administrator releases the RNC RNW or iOMS operation queue the first operation in the queue will be started to RNC/iOMS and the queue will proceed normally. The racopsopqctrl.sh command is used to run pause queue and resume queue operations. The following parameters are used for this operation: Parameter –operation

Description Specifies the type of the operation. Choose: • •

–queueName

pauseQueue - if you want to pause the queue resumeQueue - if you want to resume the queue

Specifies the name of the queue for which you want to perform the operation. Example: PLMN-PLMN/RNC-123

g In case of the operation queue for iOMS, you have to add the “LTE:” prefix before the queue name, for example, LTE:PLMNPLMN/OMS-1

Table 49

Command line options for pausing/releasing RNC RNW and iOMS operation queue

Examples of the pause queue operations: [omc]$ racopsopqctrl.sh -operation pauseQueue -queueName PLMNPLMN/RNC-123 [omc]$ racopsopqctrl.sh -operation pauseQueue -queueName LTE:PLMN-PLMN/OMS-1 Examples of the resume queue operations: [omc]$ racopsopqctrl.sh -operation resumeQueue -queueName PLMNPLMN/RNC-123 [omc]$ racopsopqctrl.sh -operation resumeQueue -queueName LTE:PLMN-PLMN/OMS-1 When Administrator pauses/releases RNC RNW or iOMS operation queue, this operation is visible in the CM Operations Manager Operation History views of all users. Pausing/releasing RNC RNW or iOMS operation queues can be configured to be hidden by

88

Id:0900d80580a02f79

DN03453584 Issue 1-0



editing the configurator.properties file in Connectivity Server. After editing configurator.properties file CM Operations Manager needs to be restarted. For instructions on how to edit configurator.properties file to hide Administrator operations, see Hiding Administrator operations from CM Operations Manager Operation History view.

11.16.2

Provisioning a priority plan Administrator can start an RNC RNW or iOMS Activate (combined Pre-Activate & Activate Pre-Activated Plan) operation with a priority flag so that the RNC RNW or iOMS operation queue is bypassed. Priority provisioning operation makes sense only when RNC or iOMS has no ongoing operation and RNC RNW or iOMS operation queue has been paused. Priority provisioning (activating) of the RNC RNW or iOMS plan can be performed by using command line provisioning operation (racclimx.sh -op Provision) with the -enablePriorityOperation true option. For more information about command line operations for activating RNC RNW plans, see Pre-activating and activating plans for RNC RNW, RNC ATM/IP, AXC, FTM, Flexi Direct, WBTS SC, core and LTE.

11.16.3

Removing a hanging operation from the RNC RNW or LTE iOMS operation queue Hanging provisioning operation means an RNC RNW or iOMS operation that stays in ongoing state in NetAct for a long time. Administrator can remove the hanging operation so that the RNC RNW or iOMS operation queue can proceed. Removing a hanging operation does not stop anything in the RNC or iOMS but affects NetAct only. The racopsopqctrl.sh command is used to remove a hanging operation from an RNC RNW or iOMS operation queue. The following parameters are used for this operation: Parameter

Description

–operation

Choose removeFromQueue for this operation.

–queueName

Specifies the name of the queue from which you want to remove a hanging operation. Example: PLMN-PLMN/RNC-123

g In case of the operation queue for iOMS, you have to add the “LTE:” prefix before the queue name, for example, LTE:PLMNPLMN/OMS-1

Table 50

Command line options for removing hanging operation from RNC RNW and iOMS operation queue

Examples of removing hanging RNC RNW or iOMS operation from the queue: [omc]$ racopsopqctrl.sh -operation removeFromQueue -queueName PLMN-PLMN/RNC-123

DN03453584 Issue 1-0

Id:0900d80580a02f79

89



[omc]$ racopsopqctrl.sh -operation removeFromQueue -queueName LTE:PLMN-PLMN/OMS-1

11.17

Command Manager command line operations This section provides information on executing Command Manager operations using the Command Line Interface. For the list of supported network elements, see Command Manager in NetAct Configurator Principles. The following table lists the command line options for executing MML commands or command files in network elements using the Command Line Interface: The starting parameters

Explanation

-op

Choose MMLCommandExecution to execute a single command or command file to single or multiple network elements. Use below arguments to specify operation properties.

-DN

Distinguished Name of the network element(s) to which you want to send a command or command file. Use comma separated values to specify multiple network elements. This argument is mandatory.

-mmlCommand

Specifies MML command that you want to execute in given network element(s).

g The MML command has to be enclosed within double quotes, for example, "ZUSI;".

If the MML command itself contains double quotes as a part of the command, then it has to be enclosed within single quotes. This option is mutually exclusive with the -fileName option. Specifies the file with the group of MML commands that you want to execute in given network element(s).

-fileName

g Command file has to be stored in the /var/opt/nokia/oss/global/cmmmld/mmli nput directory. This option is mutually exclusive with the -mmlCommand option. -coreStopAtFirstError

Specifies if the command file execution is stopped when the first error occurs. This argument is optional. Possible values are: true or false. The default value is false.

Specifies the connection timeout in seconds. This commandManagerConnectionTime argument is optional. Argument range is 1..3600 seconds. The default value is 20. out

Table 51

90

Command line options for executing Command Manager operations

Id:0900d80580a02f79

DN03453584 Issue 1-0




Explanation

-coreIsToUpperCase

Specifies if the user input is converted to the upper case when sending MML commands to the network element. This argument is optional. Possible values are: true or false. The default value is true.

Table 51

Command line options for executing Command Manager operations

If the MML command or command file execution is successful, the MML printouts are stored in the following directory: /var/opt/nokia/oss/global/cmmmld/mmloutput

g

There is no warning / confirmation for dangerous commands when executing Command Manager operations using the Command Line Interface. Examples of Command Manager command line operations: Executing a single command on a single network element: [omc]$ racclimx.sh -op MMLCommandExecution -coreStopAtFirstError -DN -mmlCommand <“command”> commandManagerConnectionTimeout -coreIsToUpperCase Executing a command file on a single network element: [omc]$ racclimx.sh -op MMLCommandExecution -coreStopAtFirstError -DN -fileName commandManagerConnectionTimeout -coreIsToUpperCase Executing a single command on multiple network elements: [omc]$ racclimx.sh -op MMLCommandExecution -coreStopAtFirstError -DN -mmlCommand <“command”> commandManagerConnectionTimeout -coreIsToUpperCase Executing a command file on multiple network elements: [omc]$ racclimx.sh -op MMLCommandExecution -coreStopAtFirstError -DN - fileName -commandManagerConnectionTimeout -coreIsToUpperCase

11.18

Zero touch BTS configuration command line operations This section provides information on executing zero touch BTS configuration operations in LTE and WCDMA networks using the Command Line Interface. For more information about automated site plan preparation in WCDMA and LTE networks using zero touch BTS configuration feature, see the Zero touch BTS configuration chapter in the Configuring WCDMA Flexi BTS Using Auto Connection and Auto Configuration document or the Zero touch BTS configuration chapter in the Configuring LTE Flexi Multiradio BTS Using Auto Connection and Auto Configuration document. To execute zero touch BTS configuration operation using the Command Line Interface, run the following command:

DN03453584 Issue 1-0

Id:0900d80580a02f79

91



racclimx.sh -op BTS_Automated Site Plan Preparation | eNB_Automated Site Plan Preparation -planName fileFormat -inputFile <"input file path"> profileFile The following table explains the command line options for running zero touch BTS configuration operation using the Command Line Interface: The starting parameters

Explanation

-op

Use BTS_Automated_Site_Plan_Preparation to run the Zero touch BTS configuration operation for WCDMA. Use eNB_Automated_Site_Plan_Preparation to run the Zero touch BTS configuration operation for LTE.

-planName

Specifies the name of the plan to be created. If the given plan name already exists, the new configuration is merged to this plan. This argument is mandatory.

-inputFile

Specifies the full path to the configuration input file imported from the planning tool. The file needs to be located on LinAS Server. Quotation mark needs to be used for the path. This argument is mandatory.

-fileFormat

Specifies the format of the input file. Possible values are RAML2 or CSV. This argument is optional. The default value is RAML2.

-profileFile

Specifies the path to the CSV profile file. This argument is optional and it is needed only if the input file is in the CSV format.

Table 52

Command line options for executing zero touch BTS configuration operations

Example of the zero touch BTS configuration command line operation for WCDMA: [omc]$ racclimx.sh -op BTS_Automated_Site_Plan_Preparation planName example_plan -fileFormat RAML2 -inputFile "/mnt/sharedrw/rac/racops/import/WBTS1.xml" Example of the zero touch BTS configuration command line operation for LTE: [omc]$ racclimx.sh -op eNB_Automated_Site_Plan_Preparation planName example_plan -fileFormat RAML2 -inputFile "/mnt/sharedrw/rac/racops/import/MRBTS1.xml"

11.19

BTS Configuration File Export command line operations This section provides information on exporting the BTS configuration contained in the plan to the BTS configuration plan in the BTS Site Manager format using the Command Line Interface. To export the BTS configuration in the BTS Site Manager format using the Command Line Interface, run the following command:

92

Id:0900d80580a02f79

DN03453584 Issue 1-0



racclimx.sh -op BTS_SEM_Export -DN -planName -fileLocation validateBeforePreactivation The following table explains the command line options for exporting the BTS configuration in the BTS Site Manager format using the Command Line Interface: The starting parameters

Explanation

-op

Use BTS_SEM_Export to export the BTS configuration in the BTS Site Manager format.

-DN

Specifies the network elements scope of the operation (comma separated Distinguished Names without spaces). This argument is optional.

-planName

Specifies the name of the plan from which the BTS configuration file in the BTS Site Manager format is to be created. This argument is mandatory.

-fileLocation

Name of the directory within sct/planned_sites under which exported plan will be saved. This argument is optional.

-validateBeforePreactivation Specifies if a validation is needed before BTS SEM Export. Possible values are true or false. This argument is optional. The default value is true.

Table 53

Command line options for executing the BTS SEM Export operations

Example of the BTS SEM Export command line operation: [omc]$ racclimx.sh -op BTS_SEM_Export -DN WBTS-123 -planName example_plan -validateBeforePreactivation false

11.20

Plan provisioning to multiple core NEs This section provides information on plan provisioning to multiple core NEs, comparing MMS configuration and generating MML commands using the Command Line Interface.

11.20.1

Plan provisioning to multiple NEs To provision a plan to multiple NEs using the Command Line Interface, run the following command: racclimx.sh -op Provision_Broadcast -DN planName -createBackupPlan coreStopAtFirstError -coreUploadAfterActivateNeeded The following table explains the command line options for plan provisioning to multiple NEs using the Command Line Interface:


Explanation

-op

Use Provision_Broadcast to provision plan to multiple NEs.

Table 54

Command line options for plan provisioning to multiple NEs

DN03453584 Issue 1-0

Id:0900d80580a02f79

93




Explanation

-DN

Specifies the scope of the operation (comma separated Distinguished Names without spaces). This argument is mandatory.

-planName

Specifies a plan name.This argument is mandatory.

-createBackupPlan

Specifies if backup plan generation is enabled. This argument is optional. The default value is true.

-coreStopAtFirstError

Specifies if provisioning should stop at first error occured. This argument is optional. The default value is true.

-coreUploadAfterActivateNeeded Specifies if upload has to be done after activation. This argument is optional. The default value is false. -coreGenerateMmls

Indicates if MML commands are generated to feedback. The default value is false.

-planActualCompareNeeded

Specifies if plan actual compare is required after provision. The default value is false.

-targetConfiguration

Specifies the target configuration of this operation (actual/reference).

-deltaPlanName

Specifies a plan name that will be created of the found differences when comparing the plan against actual configuration.

Table 54

Command line options for plan provisioning to multiple NEs (Cont.) Example of the plan provisioning to multiple NEs command line operation: [omc]$ racclimx.sh -op Provision_Broadcast -DN WBTS-123 -planName example_plan -createBackupPlan true -coreStopAtFirstError true coreUploadAfterActivateNeeded false -coreGenerateMmls false planActualCompareNeeded false -deltaPlanName example_plan_name

11.21

eNB Cell Trace Restart command line operations This section describes command line operations related to eNB Cell Trace Restart which supports LN4.0 and LNT2.0 eNB versions. The command is provided to perform an automatic restart of cell trace sessions that are stopped at an eNB restart. The following operation is run automatically when LTE Cell Trace Restart operation is started from the CLI: •

eNB_Cell_Trace_Restart

The scheduling executes an additional administrative operation. The following operations are run automatically when LTE Cell Trace Restart operation is scheduled from the CLI: • •

Admin:eNB_Cell_Trace_Restart to start the workflow. eNB_Cell_Trace_Restart

The administrative operation can be hidden from the Operation History by modifying configurator.properties file variable hideAdminOperation as true (default value is false). See chapter 7.5 Hiding Administrator operations from CM Operations Manager Operation History view for instructions. eNB_Cell_Trace_Restart operation contains below sub operations:

94

Id:0900d80580a02f79

DN03453584 Issue 1-0


•

• • •


Preparing the Cell Trace Restart • Finding MTRACE MOI(s) with Cell trace mode (cellTrcMode) parameter set FALSE in the scope of all operational eNBs that are managed by this NetAct • Creating temporary deletion plan eNB_Cell_Trace_Restart_deletion_ for MTRACE MOI(s) • Creating temporary creation plan eNB_Cell_Trace_Restart_creation_ for MTRACE MOI(s) Provisioning the deletion plan to eNB(s) Provisioning the creation plan to eNB(s) Cell Trace Restart Verify checks that MTRACE objects are created with cellTrcMode TRUE.

The status of the operation can be seen in the Operation History tab of CM Operations Manager. General operation row functionalities are supported in CM Operations Manager except restart. For more information, see CM Operations Manager Help.

g

Note that: •

• •

•

g

The operation makes the best effort to restart trace session by deleting and recreating MTRACE object. Note that plan provisioning failure brings a potential risk that MTRACE object is lost from eNB. In case when Refresh operation fails, analyze an error using the CM Operations Manager feedbacks. You can create an MTRACE object back using the create plan that the operation has generated e.g. with the help of plan actual compare tool, you can run only one operation at a time. If several Restart operations are running in parallel there is a potential risk of the loss of MTRACE objects, you can keep the scheduled interval not more frequently than on every 60 minutes to avoid an extensive system load caused by the various operation tasks that will be executed. Also possible parallel operations for eNBs may cause delayed provisions extending the execution time, thus allowing the consequent executions to be run in parallel and causing a loss of Traces and erroneous executions. The recommended interval is preferably several hours or daily interval. For an additional info, please see the Scheduling command line operations chapter. you can use interrupt from the CM Operation Manager Operation History tab only if the eNB Cell Trace command is jammed and is not proceeding. Operation interruption in the wrong place can cause the loss of MTRACE objects.

You can search MTRACE MOI(s) with cellTrcMode FALSE using the Search and modify functionality in CM Editor. For more information, see the Searching managed objects from the database section in CM Editor Help.


Explanation

-op

Choose eNB_Cell_Trace_Restart for this operation.

-v


-schedule

Enter a date in format yyyy-MM-dd for starting/stopping the operation and the interval in format hhh:mm.

Table 55

DN03453584 Issue 1-0

eNB Cell Trace Restart

Id:0900d80580a02f79

95




Explanation

-opsName

With this option you can define the user specific operation name.

Table 55

eNB Cell Trace Restart (Cont.)

Example of eNB cell trace restart To print out cell trace help, enter the following command: [omc]$ racclimx.sh –op eNB_Cell_Trace_Restart –h To run cell trace immediately, enter the following command: [omc]$ racclimx.sh –op eNB_Cell_Trace_Restart To schedule a command to be run in 1 hour interval, enter the following command: [omc]$ racclimx.sh -op eNB_Cell_Trace_Restart -schedule start=2012-09-21 end=2012-09-22 interval=001:00 For more information, see Scheduling command line operations.

96

Id:0900d80580a02f79

DN03453584 Issue 1-0


Where to find more information

12 Where to find more information For more information on checking and correcting the NetAct Configurator database, refer to the Troubleshooting Configuration Management Problems document. For more technical information, such as descriptions of Configurator user interface applications, processes and configuration files, see NetAct Configurator Technical Reference Guide. For information on DNS management in the NetAct system, see Managing the DNS in NetAct. For general principles for system administration in NetAct, see System Administration Principles. For more information on user management and setting user permissions, see Managing Users. For more information on crontab files, see Managing crontab files in Managing the Linux System. For information about creating BTS Sites, see Creating BTS Sites. For more information on server roles and server configurations, see NetAct hardware in NetAct System Principles.

DN03453584 Issue 1-0

Id:0900d80580a02f79

97

Appendix A: Parameters related to features under parameter-based license


13 Appendix A: Parameters related to features under parameter-based license

98

Id:0900d80580a02f79

DN03453584 Issue 1-0


Parameter-based license name

Sales item

HSPA Parameter Man- CM_MGMT_HSPA agement


Managed Object RNC

Parameters under license ActivityFactorForHSPA AMRLCBufMaxOverbook2NRT AMRLCBufMaxOverbook3NRT AMRLCOnEDCHOfNRTPSCount AMRLCOnEDCHOfNRTPSMaxDAT AMRLCOnEDCHOfNRTPSMaxMRW AMRLCOnEDCHOfNRTPSMaxRST AMRLCOnEDCHOfNRTPSPeriodMax AMRLCOnEDCHOfNRTPSPeriodMin AMRLCOnEDCHOfNRTPSPollPDU AMRLCOnEDCHOfNRTPSPollSDU AMRLCOnEDCHOfNRTPSPollWindow AMRLCOnEDCHOfNRTPSTriggers AMRLCOnHSDSCHOfNRTPSCount AMRLCOnHSDSCHOfNRTPSFilterReTX AMRLCOnHSDSCHOfNRTPSMaxDAT AMRLCOnHSDSCHOfNRTPSMaxMRW AMRLCOnHSDSCHOfNRTPSMaxRST AMRLCOnHSDSCHOfNRTPSPeriodMax AMRLCOnHSDSCHOfNRTPSPeriodMin AMRLCOnHSDSCHOfNRTPSPollPDU AMRLCOnHSDSCHOfNRTPSPollSDU AMRLCOnHSDSCHOfNRTPSPollWindow AMRLCOnHSDSCHOfNRTPSTriggers AMRWithEDCH AMRWithHSDSCH DCHSlopeOfTheCurve DRRCForHSDPALayerServices DirectedRRCForHSDPALayerEnhanc DisablePowerInHSDPALayeringDecision EDCHQOSClasses FactorEDCHMaxBitRate HappyBitDelayConditionEDCH HSDPACPICHAveWindow HSDPACPICHCTSRepPer HSDPACPICHEcNoThreshold HSDPAChaTypeSwitchWindow HSDPAFlowControlLowThresholdDedicatedVCC HSDPAMaxCellChangeRepetition HSDPAPriority

Table 56

Parameters related to features under parameter-based license

DN03453584 Issue 1-0

Id:0900d80580a02f79

99


Sales item


Managed Object


Parameters under license HSDPARRCdiversity HSDSCHQoSclasses HSPDSCHAdjustPeriod HSUPACtrlChanAdjPeriod HsdschGuardTimerHO IurPriority MACdflowutilRelThr MaxBitRateNRTMACDFlow MaxReWaitTime ServicesToHSDPALayer StepSizeForDCHBLER StepSizeForEDCHBLER TGPLAMRHSDPAInterFreq TGPLHSDPAInterFreq ThresholdMaxEDPDCHSR1920kbps ThresholdMaxEDPDCHSR3840kbps ThresholdMaxEDPDCHSR960kbps

WBTS

BTSSupportForHSPACM DelayThresholdMax DelayThresholdMid DelayThresholdMin HSDPACCEnabled MaxNumberEDCHLCG ProbabilityFactorMax WinLCHSDPA WinLCHSUPA

Table 56

100

Parameters related to features under parameter-based license (Cont.)

Id:0900d80580a02f79

DN03453584 Issue 1-0



Sales item


Managed Object WCEL

Parameters under license CellWeightForHSDPALayering DirectedRRCForHSDPALayerEnabled EDCHCapability EDCHMinimumSetETFCI EDCHOpState HSDPA64UsersEnabled HSDPAFmcgIdentifier HSDPAFmciIdentifier HSDPAFmcsIdentifier HSDPALayeringCommonChEnabled HSDPAMPOHSDPAMaxBitrateUL HSDPAcapability HSDPAenabled HSPAFmcsIdentifier HSPA72UsersPerCell HSPDSCHCodeSet HSUPAEnabled HspaMultiNrtRabSupport MaxNumberEDCHCell MaxNumberHSDPAUsers MaxNumberHSDSCHMACdFlows MaxTotalUplinkSymbolRate NonHSEventECommMeas NumberEDCHReservedSHOBranchAdditions OCULNRTDCHGrantedMinAllocT PrxLoadMarginEDCH PrxMaxTargetBTS PrxTargetPSMax PrxTargetPSMin PrxTargetPSStepDown PtxHighHSDPAPwr PtxMaxEHICH PtxMaxHSDPA PtxOffsetEAGCH PtxOffsetEAGCHDPCCH PtxOffsetEHICHDPCCH PtxOffsetERGCH PtxOffsetERGCHDPCCH PtxOffsetExxCH2ms PtxOffsetExxCHSHO

Table 56


DN03453584 Issue 1-0

Id:0900d80580a02f79

101


Sales item


Managed Object


Parameters under license PtxOffsetHSDPA PtxTargetHSDPA PtxTargetPSAdjustPeriod PtxTargetPSMax PtxTargetPSMin PtxTargetPSStepDown PtxTargetPSStepUp RTWithHSDPAFmcgIdentifier RTWithHSDPAFmciIdentifier RTWithHSDPAFmcsIdentifier RTWithHSPAFmcsIdentifier RsrvdSignaturesOffset SIRDPCCHOffsetEDPCH

ADJD

AdjdHSDPAHopsId AdjdRTWithHSDPAHopsId

ADJI

AdjiNCHOHSPASupport

ADJS

HSDPAHopsIdentifier RTWithHSDPAHopsIdentifier

COCO

AAL2QueueHSDPAWithoutFC AAL2QueueHSUPA InternalHSDPAFCMethodBTS

FMCS

EDCHAddEcNoOffset EDCHRemEcNoOffset

HOPI

Table 56

102

AdjiPriorityHSCAHO


Id:0900d80580a02f79

DN03453584 Issue 1-0



Sales item HSPA Quality of Service Parameter Management

CM_MGMT_HSPA_QO S


Managed Object RNC

Parameters under license EDCHStrPSCount EDCHStrPSDiscardTime EDCHStrPSMaxDAT EDCHStrPSMaxMRW EDCHStrPSMaxRST EDCHStrPSPeriodMax EDCHStrPSPeriodMin EDCHStrPSPollPDU EDCHStrPSPollSDU EDCHStrPSPollWindow EDCHStrPSTriggers HSDSCHStrDiscardTime HSDSCHStrPSCount HSDSCHStrPSFilterReTX HSDSCHStrPSMaxDAT HSDSCHStrPSMaxMRW HSDSCHStrPSMaxRST HSDSCHStrPSPeriodMax HSDSCHStrPSPeriodMin HSDSCHStrPSPollPDU HSDSCHStrPSPollSDU HSDSCHStrPSPollWindow HSDSCHStrPSTriggers EDCHMACdflowtputStrTtT EDCHMaxHARQReTxStr FreePtxSafetyMarginStr HSDPAInitialBRULStrNRT HSDPAMinBRULStrNRT NBRForPri0DL NBRForPri0UL NBRForPri10DL NBRForPri10UL NBRForPri11DL NBRForPri11UL NBRForPri12DL NBRForPri12UL NBRForPri1DL NBRForPri1UL NBRForPri2DL NBRForPri2UL

Table 56


DN03453584 Issue 1-0

Id:0900d80580a02f79

103



Sales item

Managed Object


Parameters under license NBRForPri3DL NBRForPri3UL NBRForPri4DL NBRForPri4UL NBRForPri5DL NBRForPri5UL NBRForPri6DL NBRForPri6UL NBRForPri7DL NBRForPri7UL NBRForPri8DL NBRForPri8UL NBRForPri9DL NBRForPri9UL MACdflowtputStrTtT MaxReWaitTimeRT NRTRBBRWithEDCHStr TDMultForHSDPAStreaming

IP based Iu interfaces parameter management

CM_MGMT_IPIU

WBTS

TQMId

WCEL

HSPAQoSEnabled

IUCS

DestIPAddrListCS MinUDPPortCS RtcpActivation

IUR

IPBasedRouteIdIur MinUDPPortIur NRTDCHToDSCP RTDCHToDSCP

WBTS

HSDPAULCToDSCP HSUPADLCToDSCP IPBasedRouteIdIub IPNBId MinUDPPortIub NRTDCHToDSCP NRTHSPAToDSCP RTDCHToDSCP ToAWEOffsetNRTDCHIP ToAWEOffsetRTDCHIP ToAWSOffsetNRTDCHIP ToAWSOffsetRTDCHIP

Table 56

104


Id:0900d80580a02f79

DN03453584 Issue 1-0


Index A Application Manager 18 applications CM Editor 43 CM Operations Manager 47, 51, 52, 54, 55, 59, 66, 67 DNS management 20 Plan Editor 43 Radio Network Manager 43

B BSC optional features 43 BSC version and options 42

C C -number BSC 42 checking actual configuration 80 plans 80 cleaning up log files 32 CM Editor 43 CM Operations Manager 47, 51, 52, 54, 55, 59, 66, 67 command line operations 46 configuration files system.properties 33 zrnconcmplamx.cf 24 configuring DDNS proxy 17 Name Server 21 zones 21 CSV 63 customizing CM Bulk Data subsystem 32

IP address 33

K key files 21

L LDAP 29, 33 Lightweight Directory Access Protocol 29

M MGW version and options 40, 41 MML 40, 41, 42, 43 MSC version and options 40

N naamanmx.cf 33 Name Server 21 NetAct Permission Manager 20 NetAct Start 18 Network Editor 18, 40

P parameters in LDAP 29 Plan Editor 43 Primary Name Server 17, 22

Q Q3 version 42 Q3 Version Control syntax of 42

R

DDNS access user 17, 20 DDNS proxy 17 defining email notifications in LDAP 33 DNS management 20, 24

racclimx.sh 46 Radio Network Manager 43 RAML2.0 63 RNC version and options 40 Routing Area object 21, 22 rules importing 33 validating 33

F

S

D

feedback levels for upload 48, 67

I importing rules 33

DN03453584 Issue 1-0

scripts racclimx.sh 46 servers Name Server 21 Primary Name Server 17, 22

Id:0900d80580a02f7a

105


setting version and options RNC 40 SGSN options 41 shared secret 22 system.properties file 33

T Top -level User Interface 42

U User Group Profiles 20 user management applications NetAct Permission Manager 20 User Group Profiles 20 users DDNS access user 17

V validating rules 33

Z zones 21

106

Id:0900d80580a02f7a

DN03453584 Issue 1-0

Pdn 03453584

Recommend Documents