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 compo-nents.

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.

2 DN03453584Issue 1-0


Id:0900d80580a02f7a

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 DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, 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 SafetyThis 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 knnen Gefahren durch Laser, Elektrizitt, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter Sicherheitshinweise im Teil Legal, Safety and Environmental Information dieses Dokuments oder dieses Dokumentations-satzes.

DN03453584Issue 1-0

3


Id:0900d80580a02f7a

Table of ContentsThis document has 106 pages.

1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.1 Environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.2 NetAct compatibility and capacity information . . . . . . . . . . . . . . . . . . . . 101.3 Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 Configuring BSC file-based upload, provisioning, and events . . . . . . . . 122.1 Checking and configuring user accounts for FTAM Unix Access service

type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.2 Enabling Node Manager launch functionality. . . . . . . . . . . . . . . . . . . . . 132.3 Configuring BSC file-based events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.3.1 Solving problems with the XML-based events and core files generated by

the zrnevhmx process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

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

type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4 Configuring NetAct Configurator DNS management . . . . . . . . . . . . . . . 174.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174.2 Overview of the operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174.3 Configuring the Primary Name Server . . . . . . . . . . . . . . . . . . . . . . . . . . 184.4 Configuring the p3nprxmx DDNS Proxy process. . . . . . . . . . . . . . . . . . 194.5 Creating and configuring the DDNS access . . . . . . . . . . . . . . . . . . . . . 204.6 Configuring LDAP for NetAct Configurator DNS management . . . . . . . 244.7 Configuring DNS management for the rehosting operation . . . . . . . . . . 244.7.1 Overview of the operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.7.2 Creating shared secret key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.7.3 Adding RAN zone name to LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.7.4 Configuring BIND. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.7.5 Configuring NameSurfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

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

6 Configuring NE3S/WS Agent Port, URL path, Operation timeout and Re-sponse timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

7 Customizing NetAct Configurator applications. . . . . . . . . . . . . . . . . . . . 317.1 Enabling tracing for Connectivity Server services . . . . . . . . . . . . . . . . . 317.1.1 CM Bulk Data (blkdatmx). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317.1.2 GSM Upload Mediator (uplnwmmx). . . . . . . . . . . . . . . . . . . . . . . . . . . . 317.1.3 NetAct Configurator CM BSC Mediation (cmmbscmx) . . . . . . . . . . . . . 327.2 Customizing the settings of CM Bulk Data subsystem . . . . . . . . . . . . . 327.3 Customizing the settings of CM Analyzer . . . . . . . . . . . . . . . . . . . . . . . 337.4 Enabling parameter level audit logging . . . . . . . . . . . . . . . . . . . . . . . . . 337.4.1 Enabling provisioning audit logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347.4.2 Enabling automatic upload audit logging . . . . . . . . . . . . . . . . . . . . . . . . 347.5 Hiding Administrator operations from CM Operations Manager Operation

History view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4 DN03453584Issue 1-0


Id:0900d80580a02f7a

7.6 Customizing the settings of a folder object . . . . . . . . . . . . . . . . . . . . . . . 357.7 Enabling Inter-RAT UTRAN and Inter-RAT GERAN features auto manage-

ment in Plan Prepare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357.8 Handling critical parameters in NetAct Configurator . . . . . . . . . . . . . . . . 367.9 Defining the maximum number of managed objects in one validation file for

LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377.10 Defining the number of waiting operations per BSC, RNC and LTE OMS .

387.11 Enabling skipping BTS, Flexi Direct and/or LTE validation before pre-acti-

vation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387.12 Enabling validation files saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

8 Managing the software version and options support . . . . . . . . . . . . . . . 408.1 Setting the RNC version and options . . . . . . . . . . . . . . . . . . . . . . . . . . . 408.2 Setting the MSC options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408.3 Setting the MGW options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408.4 Setting the SGSN options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418.5 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 Command line operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4611.1 Scheduling command line operations . . . . . . . . . . . . . . . . . . . . . . . . . . . 4611.2 Uploading actual values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4711.3 Provisioning plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5111.3.1 GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5111.3.1.1 Validating BTS SC plan before pre-activation. . . . . . . . . . . . . . . . . . . . . 5111.3.1.2 Validating BSC RNW plan after pre-activation . . . . . . . . . . . . . . . . . . . . 5211.3.1.3 Pre-activating and activating GSM plan . . . . . . . . . . . . . . . . . . . . . . . . . 5211.3.1.4 Activating the pre-activated GSM plan . . . . . . . . . . . . . . . . . . . . . . . . . . 5411.3.2 WCDMA, Flexi Direct, LTE, and core . . . . . . . . . . . . . . . . . . . . . . . . . . . 5511.3.2.1 Validating WBTS SC and LTE plans before pre-activation. . . . . . . . . . . 5511.3.2.2 Pre-activating and activating plans for RNC RNW, RNC ATM/IP, AXC,

FTM, Flexi Direct, WBTS SC, core and LTE. . . . . . . . . . . . . . . . . . . . . . 5611.3.2.3 Validating RNC ATM/IP plan content after pre-activation . . . . . . . . . . . . 5911.3.2.4 Activating the pre-activated plan for RNC RNW, AXC, FTM, Flexi Direct,

WBTS SC and LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6011.3.2.5 Activating the pre-activated RNC ATM/IP plan . . . . . . . . . . . . . . . . . . . . 6111.4 Exporting and importing plans, actual configuration and templates . . . . 6211.5 Deleting plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6611.6 Comparing plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6711.6.1 Comparing plans to actual configuration. . . . . . . . . . . . . . . . . . . . . . . . . 6711.7 Send To Network operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6711.8 Policy-Based Compare operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6811.9 Reference Configuration related command line operations . . . . . . . . . . 6911.9.1 Initializing Reference Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7011.9.2 Generating delta . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7011.9.3 Exporting delta . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

DN03453584Issue 1-0

5


Id:0900d80580a02f7a

11.9.4 Merging plans to reference configuration. . . . . . . . . . . . . . . . . . . . . . . . 7111.9.5 Committing reference alignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7211.9.6 Committing network alignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7211.10 CM History related command line operations . . . . . . . . . . . . . . . . . . . . 7211.10.1 Initializing CM History configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7211.10.2 Synchronizing CM History configuration . . . . . . . . . . . . . . . . . . . . . . . . 7311.10.3 Generating CM History differences tabular report . . . . . . . . . . . . . . . . . 7311.10.4 Removing data from CM History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7511.11 Workflow related command line operations. . . . . . . . . . . . . . . . . . . . . . 7511.11.1 Creating workflow related plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7511.11.1.1 Creating a plan based on COCO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7511.11.1.2 Creating a new COCO reconfiguration plan . . . . . . . . . . . . . . . . . . . . . 7611.11.1.3 Creating a new transport reconfiguration plan . . . . . . . . . . . . . . . . . . . . 7611.11.1.4 Merging into selected modification plan the related _CocoAxcFtmPlan and

_CocoDeletion plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7611.11.2 Provisioning workflow related plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7711.11.2.1 Provisioning a plan generated from a COCO modification plan with the suf-

fix _CocoAxcFtmPlan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7711.11.2.2 Provisioning in AXCs and FTMs the plan with the suffix _CocoAxcFtmPlan

7811.11.2.3 Provisioning a plan with the suffix _CocoDeletion in RNCs. . . . . . . . . . 7911.11.2.4 Provisioning a selected plan in RNCs . . . . . . . . . . . . . . . . . . . . . . . . . . 7911.12 Starting consistency checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8011.13 3GPP operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8211.14 Restoring AXC configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8411.15 Managing the Remote Electrical Tilt using command line . . . . . . . . . . . 8511.15.1 Command Line operations for RET management in WCDMA network . 8511.15.1.1 Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8511.15.1.2 Forced Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8511.15.1.3 Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8511.15.1.4 Download vendor specific configuration file. . . . . . . . . . . . . . . . . . . . . . 8611.15.1.5 Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8611.15.2 Command Line operations for RET management in LTE network . . . . 8711.15.2.1 Upload (with Command Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8711.15.2.2 Download (with Command Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8711.16 Administering RNC RNW and LTE iOMS queues . . . . . . . . . . . . . . . . . 8711.16.1 Pausing/releasing an RNC RNW and LTE iOMS operation queue . . . . 8811.16.2 Provisioning a priority plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8911.16.3 Removing a hanging operation from the RNC RNW or LTE iOMS operation

queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8911.17 Command Manager command line operations . . . . . . . . . . . . . . . . . . . 9011.18 Zero touch BTS configuration command line operations . . . . . . . . . . . . 9111.19 BTS Configuration File Export command line operations . . . . . . . . . . . 9211.20 Plan provisioning to multiple core NEs . . . . . . . . . . . . . . . . . . . . . . . . . 9311.20.1 Plan provisioning to multiple NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9311.21 eNB Cell Trace Restart command line operations. . . . . . . . . . . . . . . . . 94

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

6 DN03453584Issue 1-0


Id:0900d80580a02f7a

13 Appendix A: Parameters related to features under parameter-based li-cense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

DN03453584Issue 1-0

7


Id:0900d80580a02f7a

List of FiguresFigure 1 Overview of configuring the DDNS proxy for NetAct Configurator DNS

management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 2 Overview of the operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

8 DN03453584Issue 1-0


Id:0900d80580a02f7a

List of TablesTable 1 Environment variables used in this document . . . . . . . . . . . . . . . . . . . . 10Table 2 Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Table 3 Command line options for Q3 Version Manager usage . . . . . . . . . . . . . 14Table 4 Options for the Primary Name Server in Network Editor . . . . . . . . . . . . 19Table 5 Value definitions for the preferHiddenPrimary attribute . . . . . . . . . . . . . 19Table 6 Variable list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Table 7 Variable list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Table 8 Variable list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Table 9 q3versmx command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Table 10 Command line options for upload operations . . . . . . . . . . . . . . . . . . . . 47Table 11 Command line options for validating BTS SC plan. . . . . . . . . . . . . . . . . 51Table 12 Command line options for validating BSC RNW plan. . . . . . . . . . . . . . . 52Table 13 Command line options for provisioning . . . . . . . . . . . . . . . . . . . . . . . . . 53Table 14 Command line options for the Activate_Pre-Activation operations . . . . 54Table 15 Command line options for validating plan content . . . . . . . . . . . . . . . . . 56Table 16 Command line options for plan provisioning . . . . . . . . . . . . . . . . . . . . . 56Table 17 Command line options for the IPA_Validation operation . . . . . . . . . . . . 59Table 18 Command line options for activating the pre-activated plan . . . . . . . . . 60Table 19 Command line options for the IPA_Activation operations . . . . . . . . . . . 61Table 20 Command line options for the export and import operations . . . . . . . . . 63Table 21 Command line options for the plan delete operations . . . . . . . . . . . . . . 66Table 22 Command line options for the compare operations . . . . . . . . . . . . . . . . 67Table 23 Command line options for Send To Network operations . . . . . . . . . . . . 68Table 24 Command line options for running Policy-Based compare operation . . 68Table 25 Command line options for initializing Reference Configuration . . . . . . . 70Table 26 Command line options for generating delta . . . . . . . . . . . . . . . . . . . . . . 70Table 27 Command line options for exporting delta . . . . . . . . . . . . . . . . . . . . . . . 71Table 28 Command line options for merging plans to reference configuration . . . 71Table 29 Command line options for committing reference alignments . . . . . . . . . 72Table 30 Command line options for committing network alignments . . . . . . . . . . 72Table 31 Command line options for initializing CM History configuration . . . . . . . 72Table 32 Command line options for synchronizing CM History configuration with ac-

tual configuration or reference configuration . . . . . . . . . . . . . . . . . . . . . 73Table 33 Command line options for generating the CM History differences tabular

report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Table 34 Command line options for removing irrelevant data from CM History

database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Table 35 Workflow related command line operations for creating a plan based on

COCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Table 36 Workflow related command line operations for creating a new COCO? re-

configuration plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Table 37 Workflow related command line operations for creating a new transport re-

configuration plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Table 38 Workflow related command line operations for merging into selected mod-

ification plan the related _COCOdeletion plan . . . . . . . . . . . . . . . . . . . . 77Table 39 Workflow related command line operations for merging into selected mod-

ification plan with the suffix _CocoAxcFtmPlan . . . . . . . . . . . . . . . . . . . 77

DN03453584Issue 1-0

9


Id:0900d80580a02f7a

Table 40 Workflow related command line operations for provisioning in AXCs and FTMs the plan with the suffix _CocoAxcFtmPlan . . . . . . . . . . . . . . . . . 78

Table 41 Workflow related command line operations for provisioning the plan with the suffix _CocoDeletion in RNCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Table 42 Workflow related command line operations for provisioning selected plan in RNCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Table 43 Command line options for consistency checking . . . . . . . . . . . . . . . . . 80Table 44 Command line options for 3GPP upload . . . . . . . . . . . . . . . . . . . . . . . . 83Table 45 Command line options for 3GPP download . . . . . . . . . . . . . . . . . . . . . 83Table 46 Command line options for restoring AXC configurations . . . . . . . . . . . 84Table 47 Command line options for Binary Download operation . . . . . . . . . . . . . 86Table 48 Command line options for Calibration operation . . . . . . . . . . . . . . . . . . 86Table 49 Command line options for pausing/releasing RNC RNW and iOMS opera-

tion queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Table 50 Command line options for removing hanging operation from RNC RNW

and iOMS operation queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Table 51 Command line options for executing Command Manager operations . 90Table 52 Command line options for executing zero touch BTS configuration

operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Table 53 Command line options for executing the BTS SEM Export operations . 93Table 54 Command line options for plan provisioning to multiple NEs . . . . . . . . 93Table 55 eNB Cell Trace Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Table 56 Parameters related to features under parameter-based license . . . . . . 99

10 DN03453584Issue 1-0


Id:0900d80580a02f79

About this document

1 About this documentAdministering NetAct Configurator is an administer document that covers various tech-nical aspects of Nokia Siemens Networks NetAct Configurator, such as command line operations and administrators 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 docu-ments.

1.1 Environment variablesThis document assumes the values of the environment variables as indicated in the fol-lowing table:

1.2 NetAct compatibility and capacity informationFor information on the NetAct system and capacity, and the compatibility between NetAct and network element releases, see the NetAct Compatibility and Capacity Infor-mation document.

1.3 Terms

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

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 Terms

DN03453584Issue 1-0

11

Administering NetAct Configurator About this document

Id:0900d80580a02f79

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

Term Explanation

Table 2 Terms (Cont.)

12 DN03453584Issue 1-0


Id:0900d80580a02f79

Configuring BSC file-based upload, provisioning, and events

2 Configuring BSC file-based upload, provi-sioning, and eventsThis chapter gives instructions for configuring the BSC file-based upload and provision-ing 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 typeThe 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 Configu-rator 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 Permis-sion 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.

DN03453584Issue 1-0

13

Administering NetAct Configurator Configuring BSC file-based upload, provisioning, andevents

Id:0900d80580a02f79

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 functionalityTo enable the NetAct Node Manager launch functionality, ensure that the following con-figuration 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 CMSobriquetsRun 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 eventsBSC 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 possi-ble. 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 manage-ment 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

14 DN03453584Issue 1-0


Id:0900d80580a02f79

Configuring BSC file-based upload, provisioning, and events

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 config-ured in FTP mode), enter the following command:

q3versmx bscid 1234 XMLevents ip:port 10.125.97.51:21 user ftpuse pass useftpThe 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.

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.

-dir 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.This option can be used only for testing purposes.

-compthr 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.

Specific values:

0 - Always compression 2147483647 - No compressionIf this option is not used, the Q3 Version Manager will send as uncompressed to BSC.

-eventcoltime

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

DN03453584Issue 1-0

15

Administering NetAct Configurator Configuring BSC file-based upload, provisioning, andevents

Id:0900d80580a02f79

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 gener-ated 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 -Q3eventsand immediately after that switch on the XML-events back into use with the following command:

q3versmx bscid -XMLevents ip:port :21 -user ftpuse -pass

16 DN03453584Issue 1-0


Id:0900d80580a02f79

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 typeThe 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 appli-cation 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.

DN03453584Issue 1-0

17

Administering NetAct Configurator Configuring NetAct Configurator DNS management

Id:0900d80580a02f79

4 Configuring NetAct Configurator DNS man-agementThis chapter gives instructions for configuring the DDNS (Dynamic Domain Name System) proxy settings and DNS to facilitate communication between NetAct Configu-rator 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 man-agement. 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 PrerequisitesTo ensure that NetAct Configurator DNS management works properly, the following pre-requisites must be met:

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.

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

18 DN03453584Issue 1-0


Id:0900d80580a02f79

Configuring NetAct Configurator DNS management

Figure 1 Overview of configuring the DDNS proxy for NetAct Configurator DNS management

4.3 Configuring the Primary Name ServerTo configure the Primary Name Server

1. Go to NetAct Start: . 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.

Assign the DDNS_ACCESS

service type to the user

Configure the Primary

Name Server

Grant the DDNS access to the user

Configure LDAP for Configurator

DNS management

Start

End

Create the DDNS

access service user

Configure the p3nprxmx

DDNS Proxy process

DN03453584Issue 1-0

19


Id:0900d80580a02f79

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:

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

4.4 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.

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") )

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:

osscore package of this cluster if NameSurfer is the DNS primary

the servers own IP if BIND is the DNS primary the IP address of your sites DNS server another clusters osscore package IP address or server

name.

Name The WS names must be unique under the same MR.

Table 4 Options for the Primary Name Server in Network Editor

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

20 DN03453584Issue 1-0


Id:0900d80580a02f79


)

5. Save and close the file.6. Check the PID for the p3nprxmx process and kill it with PID. Use the following com-

mands:

root% ps -ef | grep p3nprxmxroot% 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 accessThe 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

DN03453584Issue 1-0

21


Id:0900d80580a02f79

Rehosting operation. For instructions, see Managing views/profiles in User Group Profiles Help.

To assign the DDNS_ACCESS service type to the userAfter 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

g 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 userNext, 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 managements 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 hexadec-imal 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

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

the password assigned in NetAct Permission Manager for example, Omc0mc123

Table 6 Variable list

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


22 DN03453584Issue 1-0


Id:0900d80580a02f79


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.4Shared 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 def-inition, 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:

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.)

$ORIGIN .$TTL 3600 ; 1 hourmnc0003.mcc0106.gprs IN SOA tehi.netact.noklab.net.root.tehi.netact.noklab.net. (

DN03453584Issue 1-0

23


Id:0900d80580a02f79

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 d429ff3a8bc88d3345ef399a66b33c57dchp.server 1ef399ab33c5766429ff3a8bc88d3345

For example:

localhost d429ff3a8bc88d3345ef399a66b33c57dchp.server 1ef399ab33c5766429ff3a8bc88d3345ddnsuser 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 state-ment as it is not using the default port 53. The following is an example of the content of the /etc/named.conf file:

2005092101 ; serial28800 ; 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.

24 DN03453584Issue 1-0


Id:0900d80580a02f79


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 manage-mentPrerequisitesIt 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.

UsersThe DDNSProxyUserName is inserted into the LDAP ossRacDNSManagerDDNSProxyUserName field.Example: ossRacDNSManagerDDNSProxyUserName = ddnsuserossRacDNSManagerDDNSProxyUserName = NokiaOSS.local.services.subsystems.dnsirp.GenericServiceHome.

g The user group must have DDNS_ACCESS.Query operations defined for its role.For more information on how to modify Configurator LDAP parameters, see section Configuring LDAP for NetAct Configurator.

4.7 Configuring DNS management for the rehosting operationThis section describes configuring DNS management for the rehosting operation.

4.7.1 Overview of the operationThe 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.

DN03453584Issue 1-0

25


Id:0900d80580a02f79

Figure 2 Overview of the operation

4.7.2 Creating shared secret keyA 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

BIND/NameSurfer ?

Start

End

Create shared secret key

Add ran zone to LDAP

Allow TSIG key signed

Dynamic DNS update

Restart BIND process

Run rehost operation

Clean up DNS setups

Allow TSIG key signed

Dynamic DNS update

Restart NameSurfer

Run rehost operation

BIND NameSurfer

26 DN03453584Issue 1-0


Id:0900d80580a02f79


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.4Shared 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 BINDTo configure BIND

1. Allow TSIG key signed Dynamic DNS updateThe 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 If RAN zone is added to master DNS server, then update the /etc/named.conf file in all slave DNS servers as shown below:

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.


DN03453584Issue 1-0

27


Id:0900d80580a02f79

zone "ran.netact.noklab.net" {type slave;file "db.ran.netact.noklab.net";masters { 10.8.65.4; };} ;

2. Restart BINDTo restart BIND Name Server execute the following command:

omc% service named restart

3. Run rehost operationDNS 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 setupsTo 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 NameSurferTo configure NameSurfer

1. Allow TSIG key signed Dynamic DNS update1. 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:

28 DN03453584Issue 1-0


Id:0900d80580a02f79


localhost d429ff3a8bc88d3345ef399a66b33c57dchp.server 1ef399ab33c5766429ff3a8bc88d3345

For example:localhost d429ff3a8bc88d3345ef399a66b33c57dchp.server 1ef399ab33c5766429ff3a8bc88d3345ddnsuser 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 NameSurferTo restart NameSurfer, execute the following command:

root# hamgrmx.pl start package dns

3. Run rehost operationIf the IP is changed, each WBTS IP address needs to be changed manually with Network Editor.

DN03453584Issue 1-0

29

Administering NetAct Configurator Configuring LDAP for NetAct Configurator

Id:0900d80580a02f79

5 Configuring LDAP for NetAct ConfiguratorNetAct uses LDAP (Lightweight Directory Access Protocol) for centralizing configuration data. The directory resides mainly in the Linux servers but there are also LDAP subsys-tems 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 inter-face applications in System Platform Technical Reference Guide. For detailed informa-tion on Configurator LDAP parameters, see NetAct Configurator LDAP parameters in NetAct Configurator Technical Reference Guide.

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

30 DN03453584Issue 1-0


Id:0900d80580a02f79

Configuring NE3S/WS Agent Port, URL path, Opera-tion timeout and Response timeout

6 Configuring NE3S/WS Agent Port, URL path, Operation timeout and Response timeoutThe 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 fileex-

ists in the location:$ETCROOT/custom/conf/racIf the file does not exist, follow the instructions:1 Go to the location $ETCROOT/rac/conf by typing the command:

[omc]$ cd $ETCROOT/rac/conf2 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 adapta-tion. 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 Operation timeout and Response timeout must be given in seconds. Timeouts should not be zero or negative.

DN03453584Issue 1-0

31

Administering NetAct Configurator Customizing NetAct Configurator applications

Id:0900d80580a02f79

7 Customizing NetAct Configurator applica-tionsYou can customize the settings of NetAct Configurator applications by editing configu-ration files.

7.1 Enabling tracing for Connectivity Server servicesThis section contains information on the tracing procedure for Connectivity Server ser-vices.

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 blkdatmx123 ? 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 Trace information is written to $OMCLOGDIR/info#blkdatmx#*.log

7.1.2 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"

32 DN03453584Issue 1-0


Id:0900d80580a02f79

Customizing NetAct Configurator applications

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

g The trace file is /var/opt/nokia/oss/tmp/trace/uplnwmmx.trc on the server where the NetAct Configurator package is running.7.1.3 NetAct Configurator CM BSC Mediation (cmmbscmx)

To enable cmmbscmx trace:1. Check if cmmbscmx.properties already exists in $ETCROOT/rac/conf2. 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 Con-

figurator package is running:

[omc]$ ps -ef | grep cmmbscmx123 ? 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.21671Trace information is written to $OMCLOGDIR/info#cmmbscmx#*.log

7.2 Customizing the settings of CM Bulk Data subsystemThe 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:

DN03453584Issue 1-0

33


Id:0900d80580a02f79

[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 Trace information is written to $OMCLOGDIR/info#blkdatmx#*.logFor more information on the blkdatmx.properties file, see system.properties (NetAct Configurator CM Bulk Data) in NetAct Configurator Technical Reference Guide.

7.3 Customizing the settings of CM AnalyzerEnabling email notifications for CM AnalyzerCM 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 Analyzers user interface, see Notifying about the check results in CM Analyzer Help.

Validating and importing rulesFor 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 loggingThis chapter describes enabling parameter level audit logging for BSC (S15), Ultra Site (AXC), Flexi Site (FTM), MGW and MSS.

34 DN03453584Issue 1-0


Id:0900d80580a02f79


g 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.

7.4.1 Enabling provisioning audit loggingTo 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 loggingTo 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 viewTo 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:


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

DN03453584Issue 1-0

35


Id:0900d80580a02f79

7.6 Customizing the settings of a folder objectFolder 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 racThe 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 RacFolderThe default outcome is the following:ossRacFolderObjectLimits=default=30;nokaxc:axc=20;nokbsc:adce,nokbsc:adjw,nokrnc:adjg,nokrnc:adji,nokrnc:adjs,nokrnc:adjd=5;nokrnc:hops,nokrnc:hopi,nokrnc:hopg,nokrnc:fmcs,nokrnc:fmci=1For 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 PrepareYou 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 adja-cency 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 Adja-cencies 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 If the file does not exist, follow the below instruction:1. Go to the location $ETCROOT/rac/conf2. Copy a configurator.properties file to the following location:


36 DN03453584Issue 1-0


Id:0900d80580a02f79


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=trueand/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 ConfiguratorNetAct 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 parame-ters 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



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:


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

DN03453584Issue 1-0

37


Id:0900d80580a02f79

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/ direc-tory and edit the already mentioned xml file adding the following line to the file:

If such a file does not exist, create your own xml file in the $ETCROOT/custom/conf/rac/abstraction/customannotations/ direc-tory 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/ direc-tory.

4. Restart Mercury server.

7.9 Defining the maximum number of managed objects in one validation file for LTEYou 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





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 The default value is 1000.

38 DN03453584Issue 1-0


Id:0900d80580a02f79


7.10 Defining the number of waiting operations per BSC, RNC and LTE OMSYou 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 oper-ations 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:


$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/rac3. 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-activationThere is a possibility to skip the BTS, Flexi Direct and/or LTE data validation with unse-lecting 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) proper-ties 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 unse-lected 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.

DN03453584Issue 1-0

39


Id:0900d80580a02f79

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 attri-bute 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 savingWhen 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, neverthe-less 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 Oper-ations Manager





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 This feature supports all operations where BTS plan is validated: Activate, Pre-Acti-vate, 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.

40 DN03453584Issue 1-0


Id:0900d80580a02f79

Managing the software version and options support

8 Managing the software version and options supportThe 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 optionsFor 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 optionsThe 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 optionsThe 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.

DN03453584Issue 1-0

41

Administering NetAct Configurator Managing the software version and options support

Id:0900d80580a02f79

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 optionsThe 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 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.

42 DN03453584Issue 1-0


Id:0900d80580a02f79

Managing the software version and options support

8.5 Setting the BSC version and optionsThis 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]$ ouimanmxvterm> hostvterm> 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 C-

number 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 q3versmx command line options

DN03453584Iss

pdn 03453584

Documents