Technical Note

TN_NETACT_SW_2006_419

Optimizer malfunction due to inconsistencies between NetAct database and actual network configration
Network and Service Management Nokia NetAct Releases:
OSS3.1 ED3
x

OSS4 OSS4.1 OSS4.2

www.online.nokia.com

Company Confidential

1 (5)

Technical Note

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia's customers only for the purposes of the agreement under which the document is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues which may not be covered by the document. Nokia's liability for any errors in the document is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it. This document and the product it describes are considered protected by copyright according to the applicable laws. NOKIA logo is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification purposes only. Copyright Nokia Corporation 2006. All rights reserved.

Contacts:
Contact your local Nokia support or OSS-Care-Services@nokia.com

Summary of changes:
Date 14.4.2006 Version 1.0 Summary of changes First approved version.

www.online.nokia.com

Company Confidential

2 (5)

Technical Note

Purpose
This Technical Note (TN) document contains information related to the products and releases specified in the title page. This TN provides information about security issues (Vulnerability TN), workaround instructions how to recover from problem situations (Corrective TN) or other information related to the product usage or functionality (Informative TN): Vulnerability TN Corrective TN Informative TN

Keywords
Optimizer, optimisation, master BTS, slave BTS, no master in segment, multiple masters in segment

Summary
Inconsistensies between NetAct database and actual network configuration can cause malfunction in Optimizer. Missing Master-BTS definitions and adjacencies pointing to SlaveBTS are illegal situations and and need to be corrected to enable Optimizer to function correctly. This TN provides instructions on how to solve the problematic situation.

Detailed description
This TN is valid for the following configuration: Technology x x 2G 3G Fixed Tetra x Server Type x HP-UX WinAS/GUIS LinAS Other: Cluster x Regional Cluster Global Cluster Mediation Server

Configured servers in the selected Server Type: None, this is informative TN. Configured components: None. Required software versions or CDs: OSS_CD_0877 Other relevant configuration information: None.

Solution / Instructions
Start NetAct TN installation by saving this TN pdf file to /m/ossetc/ossguis/tnlist (OSS4, Tier3). Create this path if it is not available yet. This way it is easy to check and follow later on what TNs have been installed in the system.

www.online.nokia.com

Company Confidential

3 (5)

Technical Note

TN installation requires Downtime? Yes x No Dynco update Cluster package halt Cluster restart Server reboot

TN reconfiguration is needed when Dynco is run Cluster is halted Software e.g. CDs are installed x Not needed

Problem 1 : Multi-BCF cell is missing Master-BTS definition

Problem Description Each cell should always have exactly one Master-BTS. Master-BTS definition is missing when the SEGMENT ID and CELL ID have been changed for the Master-BTS but not for the SlaveBTS. At startup Optimizer will show list of cells with missing Master-BTSs. Master-BTS definition can be missing for the following reasons: o BSS Split has caused the inconsistency When doing the BSS split with Nokia tools this will problem will not occur o o Errors during BSS upload Changes done by MML can cause mismatch in the database if not done in controlled way

How to Solve the Situation 1. List of segments with missing Master-BTSs is listed at Optimizer startup. 2. Upload the configuration information from the network. Use the Managed Object Upload tool: Top-Level UI -> Network Configuration Mgmt -> Upload Managed Objects o o Define new Upload Operation For Uploaded Object Class(es) area, choose Selected, click Add, and choose BTS Choose Upload -> Start Check for errors o o o o o o Choose Upload -> Open Select your upload plan from the list of plans Select Apply and Close In the View-menu, select Show by status -> Error Errors are listed in the Upload Target(s) pane Details for each error can be seen in the Details by Object pane

o o

www.online.nokia.com

Company Confidential

4 (5)

Technical Note

In case there are errors, contact Nokia Technical support. After correcting this problem see if the Problem 2 described below is relevant. Run CM Refresh in Optimizer after fixing both problems

Problem 2: Adjacencies pointing to Slave BTSs

Problem Description Adjacencies should always point to Master-BTSs, never to Slave-BTSs. At the start-up of the Automated Adjacency Optimisation user is informed if there area any adjcencies pointing to Slave-BTSs. At startup Optimizer will show the adjacencies to Slave-BTS. How to Solve the Situation Adjacencies to Slave-BTSs can be corrected by creating a plan and provisioning the changes to network. If the adjacencies are not corrected Optimizer will not function correctly. Optimizer has two database procedures which find the Master-BTS of the same cell and create the needed plans: optdb_adce_to_slave_fix and optdb_adjg_to_slave_fix. Usage: o Login to the database as user optdb and execute the procedures

% sqlplus optdb SQL> begin optdb_adce_to_slave_fix end; / SQL> begin optdb_adjg_to_slave_fix end; /
o The following plans are created in Optimizer. To fix the situation, export and provision the plans with RAC o o ADCE to slave BTS fix <plan ID> ADJG to slave BTS fix <plan ID>

After correcting this problems see if the Problem 1 described above is relevant. Run CM Refresh in Optimizer after fixing both problems.

Notes
CD correction and targeted CD Set: None. The root causes of these problems are not in Optimizer.

References
Problem Report IDs: None.

www.online.nokia.com

Company Confidential

5 (5)