npo administration guide

7/29/2019 NPO Administration Guide

1/162

Alcatel-Lucent

NPO Administration Guide

NPO Document

Administration Guide

Release B10, M2, UA5, UA6

3BK 21215 AAAA PCZZA Ed.25


2/162

Status RELEASED

Short title Administration Guide

All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel-Lucent.

BLANK PAGE BREAK

2 / 162 3BK 21215 AAAA PCZZA Ed.25


3/162

Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Key Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.1 NPO Automatic Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.1.1 Data Loading and Consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.1.2 Scheduled Reports Computation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

1.2 Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.2.1 System Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.2.2 Customer Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

1.3 Object Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2 Start Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.1 Start NPO Administration Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.2 Start NPO Import / Export Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3 Close Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4 NPO Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.1 System Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.2 Configure Storage Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4.2.1 Configure Indicators Storage Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.2.2 Configure Parameter Storage Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.2.3 Configure Laser Data Storage Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.3 Storage Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.4 Display Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.5 Change Working Hours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.6 Manage RMS Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.7 Manage GPRS Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.8 Modify Unavailability Origin List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.9 Modify Relevant Hours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.10 Modify Working Zone Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.11 Secure Global Working Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5 Import Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.1 Impor t Management Using Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505.1.1 Import QoS Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505.1.2 Import Reports Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545.1.3 Import Parameters Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 75.1.4 Import Planned Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595.1.5 Import Parameter Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625.1.6 Import Parameter Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635.1.7 Import Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655.1.8 Import GPRS Distribution Threshold Values (GSM specific) . . . . . . . . . . . . . . . . 67

5.1.9 Impor t RMS Template Values (GSM specific) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695.1.10 Import Raster File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.1.11 Import Vector File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755.1.12 Import THL Template Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785.1.13 Import Diagnosis Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815.1.14 Import Customer Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845.1.15 Import Customer Topology Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855.1.16 Import Free Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865.1.17 Import Laser Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875.1.18 Import Laser File On Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895.1.19 Import Customer Acceptance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

5.2 Import Management Using Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

5.2.1 Import QoS Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955.2.2 Import Reports Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

3BK 21215 AAAA PCZZA Ed.25 3 / 162


4/162

Contents

5.2.3 Import Parameters Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 85.2.4 Import Historical Parameters Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985.2.5 Import Planned Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995.2.6 Import THL Template Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 005.2.7 Import Diagnosis Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015.2.8 Import Parameters Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 02

5.2.9 Import Parameter Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.2.10 Import GPRS Distribution Threshold Values (GSM specific) . . . . . . . . . . . . . . . 1035.2.11 Impor t RMS Template Values (GSM specific) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035.2.12 Import Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045.2.13 Update Customer Objects Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055.2.14 Load Customer Topology Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055.2.15 Load Free Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065.2.16 Import Tuning Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065.2.17 Import Laser Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065.2.18 Load Laser Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075.2.19 Import Customer Acceptance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 09

6 Export Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

6.1 Expor t Management Using Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1126.1.1 Export QoS Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1126.1.2 Export Reports Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1146.1.3 Export Diagnosis Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1156.1.4 Export Parameter Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1166.1.5 Export Parameter Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1186.1.6 Export GPRS Distribution Thresholds (GSM specific) . . . . . . . . . . . . . . . . . . . . 1196.1.7 Export RMS Template (GSM Specific) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1216.1.8 Export THL Template Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

6.2 Export Management Using Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246.2.1 Export QoS Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246.2.2 Export Reports Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

6.2.3 Export Diagnosis Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1256.2.4 Export Parameter Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1256.2.5 Export Parameter Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1256.2.6 Export THL Template Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

7 Delete Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

7.1 Delete Management Using Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1287.1.1 Delete QoS Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1287.1.2 Delete Reports Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1307.1.3 Delete Planned Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1317.1.4 Delete Diagnosis Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1327.1.5 Delete Parameter Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1337.1.6 Delete Parameter Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

7.1.7 Delete Cartography File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1357.1.8 Delete Customer Object Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1367.1.9 Delete Customer Acceptance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

7.2 Delete Management Using Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387.2.1 Delete QoS Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387.2.2 Delete Report Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387.2.3 Delete All Planned Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387.2.4 Delete Diagnosis Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387.2.5 Delete Parameter Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387.2.6 Delete Parameter Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1397.2.7 Delete Customer Objects Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1397.2.8 Delete Customer Acceptance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

8 NPO Maintenance Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1418.1 Consolidation Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

4 / 162 3BK 21215 AAAA PCZZA Ed.25


5/162

Contents

8.1.1 On-Demand Consolidation of Unavailability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1428.1.2 Launch Consolidation Follow-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

8.2 Manage Job Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1468.2.1 Download Job Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1468.2.2 Delete Job Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

8.3 Manage Scheduled Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

8.4 Import Follow-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1488.5 Load Radio Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1508.6 Mark Inactive Network Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1518.7 Metadata Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1538.8 Customer Topology Objects Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 54

8.8.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1548.8.2 Create Customer Topology Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1548.8.3 Load Customer Topology Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1558.8.4 Delete Customer Topology Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 57

8.9 Planned Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1578.9.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1578.9.2 Manual Import Planned Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

8.9.3 Schedule Planned Data Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1588.9.4 Automatic Import of Planned Data (Non Delta) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1588.9.5 Delete Planned Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

9 Update Identification Mode from CI to LAC/CI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

9.1 Check Current Identification Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 629.2 Change Identification Mode from CI to LAC/CI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

3BK 21215 AAAA PCZZA Ed.25 5 / 162


6/162

Contents

6 / 162 3BK 21215 AAAA PCZZA Ed.25


7/162

Preface

Preface

Purpose This guide describes how to perform administrative tasks for the NetworkPerformance Optimizer (NPO).

For more information about NPO procedures, refer to the NPO User Guide.

For more information about MUSE administration procedures, refer to the 9953MP / NPO Platform Administration Guide.

The W-CDMA / WiMAX references that appear in the document do not applyfor the 9159 NPO.

Alcatel-Lucent 9953 MS-OMC PORTAL will be later referred as 9953 MP.

Whats NewIn Edition 25Import Parameter Values (Section 5.1.7) was updated. In the first sentence,Vector file for cartography was replaced by parameter values.

Import Raster File (Section 5.1.10) is updated with information about thecoordinates Long/Lat that must be reversed manually before importing theraster file in NPO. There is also an inversion sign to do on longitude.

In Edition 24The following sections are updated:

Import Raster File (Section 5.1.10)

Launch Consolidation Follow-Up (Section 8.1.2).

In Edition 23

The Check Current Identification Mode (Section 9.1) paragraph was introduced.

Import Raster File (Section 5.1.10) is updated.

In Edition 22

Modify Working Zone Dimension (Section 4.10) is updated.


Object Deletion (Section 1.3)

3BK 21215 AAAA PCZZA Ed.25 7 / 162


8/162

Preface

Mark Inactive Network Objects (Section 8.6)

Import Vector File (Section 5.1.11).

New section is added: Close Administration (Section 3).

Launch Consolidation Follow-Up (Section 8.1.2) is updated with a notice

in the step 1.The sections: Start NPO Administration Data Management (Section 2.1) andStart NPO Import / Export Management (Section 2.2) are updated with a notice.

8 / 162 3BK 21215 AAAA PCZZA Ed.25


9/162

Preface

In Edition 20The following sections are updated with information about WiMAX:

Import QoS Dictionary (Section 5.1.1)

Import QoS Dictionary (Section 5.2.1) Using Command Line

Import Reports Dictionary (Section 5.2.2)

Import Parameters Dictionary (Section 5.2.3).Updates of the sections:

Import Laser Dictionary (Section 5.2.17)

Load Laser Data (Section 5.2.18)

In Edition 19

Update the section Consolidation Administration (Section 8.1).

Update the sections with information about W-CMDA.

In Edition 18

New section is added:Storage Monitoring (Section 4.3).


Import Parameter Reference Values (Section 5.1.5)

Import Parameter Rules (Section 5.1.6).

Load Customer Topology Data (Section 8.8.3)

In Edition 16A notice is added in the following sections:

On-Demand Consolidation of Unavailability (Section 8.1.1)

Launch Consolidation Follow-Up (Section 8.1.2).

In Edition 15New sections are added:

Modify Working Zone Dimension (Section 4.10)

Secure Global Working Zone (Section 4.11).

"Alcatel-Lucent 9953 MP MS-OMC PORTAL name is changed toAlcatel-Lucent 9953 MS-OMC PORTAL.

In Edition 14

Configure Storage Duration (Section 4.2) is updated.

The document administrative part is updated.

3BK 21215 AAAA PCZZA Ed.25 9 / 162


10/162

Preface

In Edition 13

"1353 MS-OMC Portal name is changed to 9953 MP, and A9159 NPOinto 9159 NPO.

In Edition 12

The following sections are updated:

Import Planned Data (Section 5.1.4)

Import Planned Data (Section 5.2.5)

Mark Inactive Network Objects (Section 8.6).

A restriction is removed from Import RMS Template Values (GSM specific) via GUI (5.1.9) and via command line (5.2.11).

In Edition 11

New chapter added: Configure Laser Data Storage Duration (Section 4.2.3).

Configure Parameter Storage Duration (Section 4.2.2) is updated.A note is added in Import Vector File (Section 5.1.11).

Change Identification Mode from CI to LAC/CI (Section 9.2) is updated.

Import Follow-Up (Section 8.4) is updated.

"Manual Consolidation" task is removed from the document, as it is replaced byLaunch Consolidation Follow-Up (Section 8.1.2).The following chapters are removed:

Recover Data

"Time Zone Configuration

New sections is added: Import Historical Parameters Data (Section 5.2.4).

Import Raster File (Section 5.1.10) is updated.

Restriction removed from Export Parameter Reference Values (Section 6.1.4).New sections are added:

On-Demand Consolidation of Unavailability (Section 8.1.1)

Launch Consolidation Follow-Up (Section 8.1.2)

Modify Unavailability Origin List (Section 4.8)

Modify Relevant Hours (Section 4.9)

Import Laser Dictionary (Section 5.1.17) via GUI

Import Laser Dictionary (Section 5.2.17) via command line

Import Laser File On Demand (Section 5.1.18)

Import Customer Acceptance List (Section 5.1.19) via GUI

Import Customer Acceptance List (Section 5.2.19) via command line

Load Laser Data (Section 5.2.18)

Import Basic Unavailabilities (Section 5.2.18.1)

Import Alarms (Section 5.2.18.2)

10 / 162 3BK 21215 AAAA PCZZA Ed.25


11/162

Preface

Import Logs (Section 5.2.18.3)

Import Topology (Section 5.2.18.4)

Import Files On Demand (Section 5.2.18.5)

Load Inventory (Section 5.2.18.6)

Delete Reports Dictionary (Section 7.1.2) via GUI

Delete Report Dictionary (Section 7.2.2) via Command Line

Delete Customer Acceptance List (Section 7.1.9) via GUI

Delete Customer Acceptance List (Section 7.2.8) via Command Line

Object Deletion (Section 1.3) is updated.

Overall document quality was improved following an editorial review.

In Edition 10New chapters are added:

Import GPRS Distribution Threshold Values (GSM specific) (Section 5.2.10)

Import RMS Template Values (GSM specific) (Section 5.2.11)New chapters are added:

Import THL Template Dictionary via GUI (5.1.12) and via command line

(5.2.6)

Export THL Template Dictionary via GUI (6.1.8) and via command line

(6.2.6)

Change Identification Mode from CI to LAC/CI (Section 9.2).

In Edition 05

The procedure to Import Parameters Dictionary (Section 5.2.3) is updated.A notice is added in:

Import Reports Dictionary (Section 5.1.2) via GUI

Import Reports Dictionary (Section 5.2.2) via command line.

System Scheduling (Section 4.1) is updated.

Chapter Change Day of Weekly Data Consolidation is removed, as thefunction is no loger available.Restrictions are added in:

Import RMS Template Values (GSM specific) via GUI (5.1.9) and via

command line (5.2.11)

Export Parameter Reference Values (Section 6.1.4) via GUI

Manual Consolidation.

3BK 21215 AAAA PCZZA Ed.25 11 / 162


12/162

Preface

In Edition 04

New chapter added: Metadata Inventory (Section 8.7).

Overall document editorial review.


Update Customer Objects Types (Section 5.2.13)

Load Customer Topology Objects (Section 5.2.14)

Delete Customer Objects Types (Section 7.2.7)

Import Planned Data (Section 5.1.4).

Section "Move BSS Inter NPO" is moved to MS-OMC Portal/NPO PlatformAdministration Guide.

In Edition 02

Change Identification Mode from CI to LAC/CI (Section 9.2) is updated.

Move RNS procedure is not functional in W-CDMA, "Move BSS Inter NPO" isupdated.

Step 13 of the Procedure of "Move BSS Inter NPO" is updated.

In Edition 01

First official release of document.

12 / 162 3BK 21215 AAAA PCZZA Ed.25


13/162

Preface

Audience This document is intended for:

Field service technicians

Project managers

Site administrators

System support engineers (specialists)

Occasional users (e.g. subcontractors).

Assumed Knowledge You must have a basic understanding of the following:

Alcatel operations and maintenance concepts for the BSS and RNS

NPO operations

Solaris system installation

Installation tools and materials.

3BK 21215 AAAA PCZZA Ed.25 13 / 162


14/162

Preface

14 / 162 3BK 21215 AAAA PCZZA Ed.25


15/162

1 Key Concepts

1 Key Concepts

This section describes the basic principles of NPO administration.

3BK 21215 AAAA PCZZA Ed.25 15 / 162


16/162

1 Key Concepts

1.1 NPO Automatic Actions

1.1.1 Data Loading and Consolidation

The NPO stores all of its data in an Oracle 10g database. The data is loaded

from the following sources:

PM files exported by the OMC-R (proprietary format in GSM, 3GPP in

W-CDMA, or WiMAX technology)

Parameters exported by the OMC-R (ACIE in GSM, 3GPP XML in W-CDMA,

or WiMAX technology).

Loading configuration is done though data source administration. The loadingis done periodically, the period being defined in the data source:

For parameters, the NPO automatically loads the data once per 24 hour

period, at night. It is also possible to force the loading at any time, as

described in Load Radio Parameters (Section 8.5).

For PM counters, the NPO automatically loads the data from the current

day, or recovered data (PM data of the previous 5 days). Data older than

5 days is not taken into account.

For W-CDMA, it is recommended 3 days for recovery.

The new PM counter file to be loaded must be located in the exchangedirectory of a declared data source. The exchange directory may be either alocal directory, or a directory accessible via FTP. The NPO checks the newPM file version, calculates basic indicators from counters, and loads the new

PM indicator data in the data warehouse. Both the topology data and theQoS data are updated. Once the PM counter files are successfully loaded,they are deleted from the NPO and only kept on the OMC-R.

For QoS indicators, the NPO loads the data as soon as a new PM is

discovered (every hour).

Every night, the data loaded during the day is consolidated. For example,for QoS Indicators:

The data is reorganized to allow more efficient access

Normalized data is computed (refer to the NPO User Guide, to

Normalization; note that for some groups, the normalization is not onthe fly and not during the night)

Temporal and spatial aggregation is computed (refer to the NPO User

Guide, to Aggregation)

Old data is purged (refer to the NPO User Guide, to PM Data Purge).

For parameters, the consolidation is simpler, as it only consists of the purgeprocess (there is no reorganization, normalization, temporal or specialaggregation).

By default, the weekly consolidation is done each MONDAY at 01:00 oclock.

16 / 162 3BK 21215 AAAA PCZZA Ed.25


17/162

1 Key Concepts

The monthly consolidation is automatically done on the first day, at 01:00oclock of the next month.

Apart from the consolidations that are performed periodically by the system,the user can perform consolidations on-demand at any point of time, by usingthe [ Consolidate ]/[ Recover ] actions described in Launch Consolidation

Follow-Up(Section 8.1.2).To perform a manual UA consolidation, refer to On-Demand Consolidation ofUnavailability(Section 8.1.1).

To view the follow-up of a consolidation process, refer to Launch ConsolidationFollow-Up(Section 8.1.2).

1.1.2 Scheduled Reports Computation

Scheduled reports are automatically executed during the night afterconsolidation is performed. To schedule the reports, refer to the NPO UserGuide, to Schedule Reports.

All the job results are stored in the result job zone. When the result job zonesize is bigger than 2Gb, the oldest job results are automatically purged.

3BK 21215 AAAA PCZZA Ed.25 17 / 162


18/162

1 Key Concepts

1.2 Dictionaries

There are two types of dictionaries:

System dictionaries

Customer dictionaries.

The system parameter, counter, indicator, report and customer data (mostlythreshold values) dictionaries are described in XML format. Each dictionary filehas a header with the following information.

Content Comments

Name Dictionary name

Version Version

Date Publishing date

Author Name of the team or person responsible forpublishing

Description Free comment (change log or comments)

1.2.1 System Dictionaries

The system dictionaries are delivered with the software and must be importedafter NPO installation, as described in Import Reports Dictionary (Section

5.1.2):The parameter system dictionary contains the parameter definitions

The counter system dictionary contains the counter definitions

The indicator system dictionary contains the indicator definitions, based on

parameters and counters

The reports system dictionary contains Alcatel-Lucent predefined reports

and views definitions based on system indicators.

For more information about dictionary management, refer to ImportManagement (Section 5).

1.2.2 Customer Dictionaries

There are customer data dictionaries for indicators and reports.

There is only one customer indicators dictionary in the NPO. It is automaticallycreated, if needed, when the operator creates a customer indicator or athreshold.

The customer indicator dictionary contains the definitions of customer indicatorsand of the customer threshold on customer indicator

There is only one customer report dictionary in the NPO. It is automaticallycreated, if needed, when the operator creates a customer report.

18 / 162 3BK 21215 AAAA PCZZA Ed.25


19/162

1 Key Concepts

The customer report dictionary contains the definition of customer reports ,customer views and references to system views.

For more information about dictionary management, refer to ImportManagement (Section 5).

3BK 21215 AAAA PCZZA Ed.25 19 / 162


20/162

1 Key Concepts

1.3 Object Deletion

The purge of object in NPO database is based on some specific concepts:

Root loading objectsRoot loading object is an equipement in the network that is responsible to

collect data (counters for example) from the network elements and to reportthem to the OMC (e.g.: BSC/MFS in 2G, RNC/NODEB in 3G)Soft-deletion is a procedure consisting in marking in NPO database, theneworks objects that NPO detected as no more operational. The differentalgorithms are described hereafter.There is a process of soft-deletion performed once a day, during the night, tomark as soft-deleted all root loading objects that have not been reported fora given period (default value is 5 days). This procedure is marking also allchildren and associated relations of this RLO.There is also a manual maintenance procedure to delete them, describedin Mark Inactive Network Objects (Section 8.6).

Other objects present in PM files

For the other objects, if they were not reported during the day, or if adatasource is removed from the NPO, they are marked as soft deleted.This process takes place every night. For example, if the RNC does notprovide any data for a cell during the day, then during the night the cell ismarked as deleted. Also, the list of objects that were part of the removeddata source are flagged as deleted.

Other objects present in the parameter files.These objects are soft-deleted after any parameter loading (i.e. manualloading or automatic loading during the night).

Deleted objects remain visible in the Analysis Desktop but they are marked with

a red cross (refer to the NPO User Guide, to Topology Icons.

Objects that are marked as soft deleted for more than three years are removedfrom the database (hard deleted).

20 / 162 3BK 21215 AAAA PCZZA Ed.25


21/162

2 Start Administration


This section describes how to open administration pages.

3BK 21215 AAAA PCZZA Ed.25 21 / 162


22/162


2.1 Start NPO Administration Data Management

To open the NPO Admin Data Management page:

1. From the icon box, select MUSE Applications -> Optimization -> DataManagement.

Figure 1: Open Administration Page from NPO Icon Box

A login window opens.

2. Type the administrator user name and the password.

If you use Mozilla web browser and a new page is opened for the first time,after you enter the login and password, the following message appears :Doyou want the Firefox to remeber your password?. Click on [ Neveron this site ].

The "NPO Data Management" window opens.

22 / 162 3BK 21215 AAAA PCZZA Ed.25


23/162


Figure 2: "NPO Data Management" Window

3BK 21215 AAAA PCZZA Ed.25 23 / 162


24/162


2.2 Start NPO Import / Export Management

To open the NPO Import / Export Management page:

1. From the icon box, select MUSE Applications -> Optimization ->Import/Export Management.

A login window opens.

2. Type the administrator user name and the password.

If you use Mozilla web browser and a new page is opened for the first time,after you enter the login and password, the following message appears :Doyou want the Firefox to remeber your password?. Click on [ Neveron this site ].

The "NPO Import/Export Management" window opens.

24 / 162 3BK 21215 AAAA PCZZA Ed.25


25/162


Figure 3: "NPO Import/Export Management" Window

This menu is only applicable for products based on the MUSE platform (theNPO and 9953 MP). It may be different for NPO embedded.

3BK 21215 AAAA PCZZA Ed.25 25 / 162


26/162


26 / 162 3BK 21215 AAAA PCZZA Ed.25


27/162

3 Close Administration


This section describes how to close administration pages.

To close the NPO Admin Data Management page and the NPO Import /Export Management page, from the "NPO Administration" window click on[ Exit ] button.

You must not click on the icon from the right corner.

3BK 21215 AAAA PCZZA Ed.25 27 / 162


28/162


28 / 162 3BK 21215 AAAA PCZZA Ed.25


29/162

4 NPO Configuration Tasks


This section describes NPO configuration tasks.

3BK 21215 AAAA PCZZA Ed.25 29 / 162


30/162


4.1 System Scheduling

To set/unset the scheduling of consolidation, job computation and importparameter and planned data activities:

1. In the NPO Data Management window, select Configuration -> System

Scheduling.2. The System Scheduling Configuration window appears, showing the

existing configuration (enabled/disabled status).

Name Description

Consolidation Consolidation and Purge (daily, weekly, and monthly).

Weekly consolidation is set on Sunday and monthlyconsolidations on last day of the month.

Consolidations are done at local time.

Job computation Scheduled report execution.

Import Parameters Automatic load data for parameters.

Planned Data Import of planned data.

Laser Job Automatic load of Laser data.

3. To enable/disable a scheduled activity, check/uncheck its corresponding

checkbox: . By default, all boxes are checked.

Note: Disabled tasks are automatically enabled when restarting the NPO.

Alcatel-Lucent does not recommend unchecking all checkboxes.

4. Click on [ Save ].

A new window appears, showing the result of the System SchedulingConfiguration.

5. Click on [ End ].

30 / 162 3BK 21215 AAAA PCZZA Ed.25


31/162


3BK 21215 AAAA PCZZA Ed.25 31 / 162


32/162


4.2 Configure Storage Duration

Alcatel-Lucent does not recommend to change the values from configurationfiles with values bigger than the default ones!

The administrator can launch the configuration of indicators, parameters, andLASER data storage duration. The MUSE_DATA_ADMIN FAD is neededfor these operations.

Periodicity can be Raw, Normalized, Day, Week or Month.

When the storage duration is not defined for an object type, the default storageduration is applied. Refer to NPO User Guide, section PM Data Purge forthe default duration values.

4.2.1 Configure Indicators Storage Duration

The administrator can change the storage duration of indicators per periodicity

and per object type or per group of indicators.

To configure the indicators storage duration perform from the server as rootthe following steps:

1. Copy and rename the Storage duration file into a saved location.

Example:

cp

/alcatel/muse/MUSE_COMMON/config/StorageDuration.csv

/alcatel/muse/MUSE_ADMIN/bin/NewStorageDuration.csv

2. Modify as appropiate the duration values in the new configuration storageduration file.

Do not modify the first two lines of the file NewStorageDuration.csv file.

3. Run the /alcatel/muse/MUSE_ADMIN/bin/ConfigIndDuration.shscript, giving as argument the full pathname of the file that contains theduration values.

Example:/alcatel/muse/MUSE_ADMIN/bin/ConfigIndDuration.sh

/alcatel/muse/MUSE_ADMIN/bin/NewStorageDuration.csv

In case the new values are smaller than the Alcatel-Lucent recommendations(recommended min values: Raw/Daily 5days, Weekly 1 week, Monthly 1

month), a warning is displayed.The administrator is not allowed to change the storage duration to a lessthan zero value. An error is displayed in case of setting a negative value.Only a positive or null value is allowed.

In case the new values are greater than the Alcatel-Lucent recommendation,the system warns the administrator to check that there is enough diskspace available.

The storage duration values are then updated in the database and the statusof the operation is displayed to the administrator.

The next time the purge runs (typically the next night), the new duration istaken into account.

32 / 162 3BK 21215 AAAA PCZZA Ed.25


33/162


4.2.2 Configure Parameter Storage Duration

The administrator can change the storage duration of all parameters.

To configure the parameter storage duration, run from the server as rootthe following steps:

1. Copy and rename the Parameter Storage duration file into a save location.Example:

cp

/alcatel/muse/MUSE_ADMIN/config/paramStorageDuration.cfg

/alcatel/muse/MUSE_ADMIN/bin/NewParamStorage.cfg

2. Modify in the new storage duration file (e.g. NewParamStorage.cfg), theMAX_PREV_DAYS attribute to indicate the new maximum number of daysfor parameters storage duration.

3. Run the following script:/alcatel/muse/MUSE_ADMIN/bin/Configure.sh -p

Where is the absolute path and name ofthe file that contains the new parameters storage duration values.

Example

/alcatel/muse/MUSE_ADMIN/bin/Configure.sh -p

/alcatel/muse/MUSE_ADMIN/bin/NewParamStorage.cfg

In case the new values are greater than the Alcatel-Lucent recommendations(recommended max values: 400 days), a warning is displayed.

The administrator is not allowed to change the storage duration to a lessthan zero value. An error is displayed in case of setting a negative value.Only a positive or null value is allowed.


The parameter storage duration is updated in the database, and is used forParameter Purging. The status of the operation is displayed to the administrator.

The next time the purge runs (typically the next night), the new duration is takeninto account. Therefore, parameter values older than MAX_PREV_DAYS days(default 400 days) are not reliable.

4.2.3 Configure Laser Data Storage Duration

This section is not applicable for W-CDMA.

The administrator can change the storage duration of LASER data:

Alarms storage duration

Logs storage duration

HW Inventory items storage duration.

To configure the Laser storage duration, perform as root the following:

1. Edit the laser-partition.properties file with the appropriate new values,from the following directory:

/alcatel/muse/MUSE_QOS/Laser/partition/config/

3BK 21215 AAAA PCZZA Ed.25 33 / 162


34/162


Make sure that the new values are not greater than the Alcatel-Lucentrecommendations: 180 days!

2. Check the new duration values by launching the following file:/alcatel/muse/MUSE_ADMIN/bin/LaserStorageDuration.sh

The newly set values are displayed. In case the values are less than

the default purge values, a warning appears and you must update thelaser-partition.properties file with correct values.


The next time the purge runs (typically the next night), the new duration istaken into account.

34 / 162 3BK 21215 AAAA PCZZA Ed.25


35/162


4.3 Storage Monitoring

Procedure To configure the ASM_LIMIT parameter:

1. Perform the following as root:cd /alcatel/muse/MUSE_COMMON/config/

2. To find the current value for the ASM_LIMIT parameter, run the followingscript:

df h /alcatel/oracle/oradata/

3. In the common.properties file, set the ASM_LIMIT parameter with 250GBsmaller than the value obtained at the previous step.

Note: In case of disks added to the configuration, this parameter must be updated.

4.4 Display Licenses

Display a list of the installed licenses on a server:

1. In the NPO Administration window, select Administration -> ViewLicenses.

2. The NPO Data Management - View Licenses window opens.

The main panel displays the host id of the server on which the licenses areinstalled, along with a list of licenses and their details.

If no license is installed, the user is warned that no licenses are installed.

You can sort by name all the columns of the table by clicking their columnheaders. A little arrow marks the ascending or descending order.

3BK 21215 AAAA PCZZA Ed.25 35 / 162


36/162


3. Click on [ End ] to return to the NPO Data Management main view.

The installed licenses can be displayed from the server, as root, by launchingthe command line:/alcatel/muse/MUSE_ADMIN/bin/viewLicenses.sh

36 / 162 3BK 21215 AAAA PCZZA Ed.25


37/162


4.5 Change Working Hours

Working hours are used for stored temporal aggregation (refer to the NPO UserGuide, to Aggregation). When this option is enabled for an indicator, the dailyaggregation takes only the data in the relevant hours.

To configure the working hours (also called relevanthours), from the server, update as root the/alcatel/muse/MUSE_QOS/config/Consolidation.properties file:

Set the RELEVANT_HOUR_BEGINS_ON to contain the hour of the day when the

working hour starts

Set the RELEVANT_HOUR_ENDS_ON to contain the hour of the day when the

working hour ends.

For example, to define the relevant hours to be between 9 AM and 7 PM, theparameter must contain the following values RELEVANT_HOUR_BEGINS_ON=9and RELEVANT_HOUR_ENDS_ON=19

3BK 21215 AAAA PCZZA Ed.25 37 / 162


38/162


4.6 Manage RMS Template

This section is applicable only for GSM.

To manage the RMS Template:1. From the NPO Data Management window, select Configuration ->

Manage RMS Template.

2. The Manage RMS Template - Step 1 window appears.

3. From the List of Template, select the appropriate template to displayits groups.

From the List of Template Group, select the appropriate template group todisplay the values you wants to modify.

The RMS Template values update according to the selections.

4. To edit RMS Template, click on [ Edit ].In the newly opened window:

Select the appropriate List of Template

Select the appropriate List of Template Group

Type the needed Template Name

Select the appropriate Interpolation Method.Each parameter can be modified in Custom mode, or predefinedfunction modes can be used (Linear, Logarithmic, Exponential, Gauss).If a predefined function is chosen, only the first and the last values of

the list can be modified. Intermediate values are then automaticallycalculated and displayed as shown in figure below.

38 / 162 3BK 21215 AAAA PCZZA Ed.25


39/162


The List of Interpolation Method is not displayed if the group contains anheterogeneous set of parameters.

Edit the Current Value of the parameter.

Click on:

[ Save ], to save modifications on the updated parameter valuesThe The RMS Template data is saved successfully messageappears in the same window.

[ Save & Export ], to save and export the modifications of all templates

to the OMC.Click on [ OK ] at the confirmation message.

The progress bar displays the progress and eventual completion of theoperation. Wait for the end of the export.When the export is done, another window opens displaying theproperties and status of the exported RMS template file.The modified values are saved in database and exported to the OMC.Click on [ End ] to return to the "NPO Import / Export Management"main view.

5. To export RMS template:

Click on [ Export to OMC ]

Click on [ OK ] at the confirmation message.

The progress bar displays the progress and eventual completion of theoperation. Wait for the end of the export.

3BK 21215 AAAA PCZZA Ed.25 39 / 162


40/162


When the export is done, another window opens displaying theproperties and status of the exported RMS template file.The modified values are saved in database and exported to the OMC.

Click on [ End ] to return to the "NPO Import / Export Management"

main view.

40 / 162 3BK 21215 AAAA PCZZA Ed.25


41/162


4.7 Manage GPRS Thresholds

This section is applicable only for GSM.

To manage GPRS Thresholds:1. From the NPO Data Management window, select Configuration ->

Manage GPRS Thresholds.

2. The Manage GPRS Thresholds - Step 1 window appears.

3. From the List of Thresholds, select the appropriate threshold to displayits parameters.

The GPRS Threshold values update according to the selection.

4. To edit GPRS Thresholds, click on [ Edit ].In the newly opened window:

Select the appropriate GPRS Threshold value from the List of

Thresholds

Type the needed Threshold Name

Select the appropriate Interpolation Method.Each parameter can be modified in Custom mode, or predefinedfunction modes can be used (Linear, Logarithmic, Exponential, Gauss)for a group of thresholds using an ordering rule. The functions are not

applicable if the group contains a heterogeneous set of parameters.

3BK 21215 AAAA PCZZA Ed.25 41 / 162


42/162


If a predefined function is chosen, only the first and the last values ofthe list can be modified. Intermediate values are then automaticallycalculated and displayed.

Edit the Current Value of the parameter.

Click on:

[ Save ], to save modifications on the updated parameter valuesThe The GPRS Distribution Thresholds data is savedsuccessfully message appear in the same window.

[ Save & Export ], to save and export the modifications of all GPRS

Distribution Thresholds to the OMC.Click on [ OK ] at the confirmation message.The progress bar displays the progress and eventual completion of theoperation. Wait for the end of the export.When the export is done, another window opens displaying theproperties and status of the exported GPRS Distribution Thresholds.The modified values are saved in database and exported to the OMC.Click on [ End ] to return to the "NPO Import / Export Management"main view.

5. To export GPRS Threshold:

42 / 162 3BK 21215 AAAA PCZZA Ed.25


43/162


Click on [ Export to OMC ]

Click on [ OK ] at the confirmation messageThe progress bar displays the progress and eventual completion of theoperation. Wait for the end of the export.When the export is done, another window opens displaying the

properties and status of the exported GPRS Distribution Thresholds.The modified values are saved in database and then exported to theOMC.

Click on [ End ] to return to the "NPO Import / Export Management"

main view.

4.8 Modify Unavailability Origin List


The unavailability (UA) origin list defines the alarms and the logs that arepotentially the origins of the unavailability start.

To modify the Unavailability Origin List:

1. From the NPO Data Management window, select Configuration -> ModifyUnavailability Origin.

The "Modify Unavailability Origin List" window appears.

You can sort by name all the columns of the table by clicking their columnheaders. A little arrow marks the ascending or descending order.

2. In the Technology Type field, select the appropriate technology for whichyou want the logs and alarms be displayed.

3. To enable all the alarms, [ All Alarms ] checkbox must be checked. Thisis done by default.

3BK 21215 AAAA PCZZA Ed.25 43 / 162


44/162


4. To enable or disable any unavailability origin, check/uncheck thecorresponding checkbox.

If the UA origins are disabled, at the next Laser dictionary loading, theseorigins are not taken into account.

5. Click on [ Save ] to save the performed changes.

44 / 162 3BK 21215 AAAA PCZZA Ed.25


45/162


4.9 Modify Relevant Hours


To modify the unavailability relevant hours:1. From the NPO Data Management window, select Configuration -> Modify

Relevant Hours.

The "Define Relevant Hours" window appears, displaying the current startand end of relevant hours.

2. Type the appropriate Start Time and End Time of relevant hours.

End Time must be greater than Start Time.

3. Click on [ Save ] to save the performed changes.

3BK 21215 AAAA PCZZA Ed.25 45 / 162


46/162


4.10 Modify Working Zone Dimension

The administrator can update the number of cells in a working zone.

Read more information about Standard and Large working zones in NPO UserGuide, section Working Zone - Presentation

1. Perform the following as root:cd /alcatel/muse/MUSE_MAAT/topology/rsc/com/alcatel

cd muse/maat/topology/config

2. Update in the maatTopo.cfg file, the MAX_CORE_OBJECT_COUNT parameter tothe needed value.

Example: MAX_CORE_OBJECT_COUNT=2000.

Changing these parameters is not under Alcatel-Lucent responsibility. Puttinghigher values then the values tested in Alcatel-Lucent labs may cause higherresponse time or even request that do not answer.

46 / 162 3BK 21215 AAAA PCZZA Ed.25


47/162


4.11 Secure Global Working Zone

The administrator can modify the Secured property of the Global Working Zoneand also grant this right to other users.

1. In Analysis Desktop window, Working Zone editor, Edit Working Zoneand

make sure the Secured checkbox is selected.2. Open the Access Rights Definitions (SEC) window by selecting from the

iconbox Muse Applications-> Security -> Access Rights Definition(SEC).In the "Authentication box" window:

Type the administrator Name and Password.

Click on [ Apply ].

3. From SEC window create a new operator profile named NPO_WZ_Global:

From the toolbar, select Tools -> Show -> Operator profiles

In the "Edit Operator Profile" window, Friendly Name field, type:

NPO_WZ_Global

Click on [ Apply ].The NPO_WZ_Global profile appears in the left "Operators Profile" frame.

4. From SEC window, add the NPO_WZ_Global profile to the desired operators:

From the toolbar, select Tools -> Show -> Operators

Select the appropriate operator from the left "Operator" frame

In the right "Edit" frame, left Profile Name column, click on

NPO_WZ_Global profile

Click on > to add it to Profile Name right column

Click on [ Apply ].The NPO_WZ_Global profile is assigned to the selected operator.

Only the administrator or operators with NPO_WZ_Global profile are now able toopen the Global Working Zone and modify its attributes.

3BK 21215 AAAA PCZZA Ed.25 47 / 162


48/162


48 / 162 3BK 21215 AAAA PCZZA Ed.25


49/162

5 Import Management

5 Import Management

This section describes file import management.

3BK 21215 AAAA PCZZA Ed.25 49 / 162


50/162

5 Import Management

5.1 Import Management Using Graphical User Interface

After a create/add/update/load of new dictionary, if any Analysis Desktopwindows were already opened, perform a Refresh Allaction for each window.

5.1.1 Import QoS Dictionary

To import counters, indicators or the thresholds dictionary:



2. Select Import Dictionary -> QoS Dictionary.

3. In the Select a file for import field, browse for the .xml file(s) to import.

Figure 4: Example of .xml File Browsing

Select the appropriate .xml file, then click on [ Open ].

The Select a file for import field is filled in with the name of the .xml file.

4. Click on [ Add ], to add the selected .xml file to the Files selected toimport field.

To select multiple files for import, browse for the appropriate files and

click on [ Add ] repeatedly to add them to the list

To remove a file from the list, select a file and click on [ Remove ].

50 / 162 3BK 21215 AAAA PCZZA Ed.25


51/162

5 Import Management

Figure 5: Example of QoS Dictionary Import Window

5. Click on [ OK ].

A list of the import files along with their properties appears.

6. In the case of the GSM and WiMAX Indicator Dictionary, in the Optioncolumn, select the indicator type Restricted Counters or All Counters, asappropriate.

In the case of the W-CDMA Indicator Dictionary, in the Option column,select the Restricted Counters option.

If you chose Restricted Counters only the counters having a mapping oneto one with an indicator will be displayed.

The following operations are available:

Create to create new QoS dictionariesAll previous entries in the database are destroyed.

3BK 21215 AAAA PCZZA Ed.25 51 / 162


52/162

5 Import Management

Add to add new QoS dictionariesIf the imported QoS dictionary contains pre-existingindicators/counters/thresholds, they are overwritten by the importeddefinition. Otherwise, the database is not affected.

Replace to replace the new values in the database for QoS dictionaries,

from the import file.All replaced indicators/counters/thresholds must already be in thedatabase.

For customer QoS dictionary import, you can use any option: Create, Add orReplace.For system (Alcatel-Lucent) QoS dictionary import, only use the Createoption.

7. Click on the appropriate button to create/add/replace dictionaries.

The progress bar displays the progress and eventual completion of the

operation.Wait for the end of the import.

8. When the import is done, another window opens with the result of the import.

The window displays the list of imported files and their properties, as wellas the import status of each file (OK or NOK).

If errors occur during the import operation, the same screen displays thelist of errors.

Check that the imported .xml file is correct. If not, correct it and re-attemptthe import.

52 / 162 3BK 21215 AAAA PCZZA Ed.25


53/162

5 Import Management

Figure 6: Example of QoS Dictionary Import Window

9. Click on [ End ] to return to the "NPO Import / Export Management" mainview.

3BK 21215 AAAA PCZZA Ed.25 53 / 162


54/162

5 Import Management

5.1.2 Import Reports Dictionary

Note: In the case of a customer reports import, the "name" attribute from the headertag must be "CUSTOMER_REPORT_DICTIONARY".

Example:

To import a reports dictionary:



2. Select Import Dictionary -> Report Dictionary.








5. Click on [ OK ].


54 / 162 3BK 21215 AAAA PCZZA Ed.25


55/162

5 Import Management

6. The following operations are available:

Create to create new Report dictionariesAll previous entries in the database are destroyed.

Add to add new Report dictionariesIf a pre-existing reports is not in the imported file, it is not affected,otherwise it is overwritten by the imported definition.

Replace to update dictionaries in the database with the values provided

in the imported file.All Report dictionaries to be updated must already be present in thedatabase.

7. Click on the appropriate button to create/add/replace dictionaries.

The progress bar displays the progress and eventual completion of theoperation.

Wait for the end of the import.


The window displays the list of imported files and their properties (FileName, Technology, Owner and Number Of Definitions), as well as the importstatus of each file (OK or NOK).

If errors occur during the import operation, the same screen display thelist of errors.

Check that the imported .xml file is correct. If not, correct it and re-attempt

the import.

3BK 21215 AAAA PCZZA Ed.25 55 / 162


56/162

5 Import Management

9. Click on [ End ] to return to the "NPO Import / Export Management" main

view.

56 / 162 3BK 21215 AAAA PCZZA Ed.25


57/162

5 Import Management

5.1.3 Import Parameters Dictionary

To Import a parameters dictionary:


The "NPO Import/Export Management" window opens.2. Select Import Dictionary -> Parameter Dictionary.






click on [ Add ] repeatedly to add them to the list.


5. Click on [ OK ].


6. The following operations are available:

Create to create new Parameter dictionaries

All previous entries in the database are destroyed.

3BK 21215 AAAA PCZZA Ed.25 57 / 162


58/162

5 Import Management

Update to update dictionaries in the database with the values provided

from the import file.If the definitions in the imported file are not already present in thedatabase, they are added in the database.

7. Click on the appropriate button to create/update dictionaries.




The window displays the list of imported files and their properties (FileName, Type, Release, Creation Date and Number Of Definitions), as wellas the import status of each file (OK or NOK).


Check that the imported .xml file is correct. If not, correct it and re-attemptthe import.


58 / 162 3BK 21215 AAAA PCZZA Ed.25


59/162

5 Import Management

5.1.4 Import Planned Data

The feature described in this section is not yet available for W-CDMA.

To import an RNP Planned Data dictionary:



2. Select Import Data -> Planned Data.

3. Select the appropriate technology standard, then click on [ OK ].

4. In the Select a file for import field, browse for the file(s) to import.

Select the appropriate input file, then click on [ Open ].

The Select a file for import field is filled in with the name of the selected file.

3BK 21215 AAAA PCZZA Ed.25 59 / 162


60/162

5 Import Management

5. Click on [ Add ], to add the selected .zip file to the Files selected to importfield.




Note: The .zip files must have a different time stamp from the last import, otherwisethe import is not done (and no error message appears).

6. Click as appropriate on one of the following buttons:

[ Delta ], to take into account only new objectsThe objects already in the database (not part of incoming data) are nottaken into consideration.

[ Non-Delta ], to take into account only existing/common objects; if not

present in the new import, they are deleted.In Non-Delta mode, if objects are missing, then their planned data is

deleted, whereas it is not deleted in Delta mode.

60 / 162 3BK 21215 AAAA PCZZA Ed.25


61/162

5 Import Management

In Delta or Non-Delta mode, all RNP project or just a coherent subset isimported.

In WiMAX technology, the following dependencies must be taken intoaccount:SUBMAP + CELL

SUBALLOCATION + CELL

RAC_CSN + CELL

UIUC + CELL

DIUC + CELL

WW_ADJ + CELL

W_BPR_DL + W_CELL

W_BPR_UL + W_CELL

W_PMS_UL + W_CELL

W_PMS_DL + W_CELL

W_PG+W_CELL

W_CELL +W_ANT+W_SITE



7. When the import is done, the following window opens with the resultof the import.


3BK 21215 AAAA PCZZA Ed.25 61 / 162


62/162

5 Import Management

5.1.5 Import Parameter Reference Values


To import Parameter Reference values:



2. Select Import Data -> Parameter Reference Value.




4. Click on [ OK ].


operation.Wait for the end of the import.


The window displays the list of imported files and their properties (FileName, Type, Dictionary name, Author, Release, Creation Date, AvailableWorksheets, and Type), as well as the import status of each file (OK or NOK).


Check that the imported .xls file is correct. If not, correct it and re-attemptthe import.

62 / 162 3BK 21215 AAAA PCZZA Ed.25


63/162

5 Import Management


view.

5.1.6 Import Parameter Rules


To import Parameter Rules:



2. Select Import Data -> Parameter Rules.




4. Click on [ OK ].




3BK 21215 AAAA PCZZA Ed.25 63 / 162


64/162

5 Import Management

The window displays the list of imported files and their properties (FileName, Type, Dictionary name, Author, Release, Creation Date, AvailableWorksheets, and Type), as well as the import status of each file (OK or NOK).


Check that the imported .xls file is correct. If not, correct it and re-attemptthe import.


64 / 162 3BK 21215 AAAA PCZZA Ed.25


65/162

5 Import Management

5.1.7 Import Parameter Values

To import the parameter values:


The "NPO Import/Export Management" window opens.2. Select Import Data -> Parameter Values.

3. Click on [ OK ] at the confirmation message.



4. When the import is done, another window opens with the result of the import.If the parameter loading is successful then a success message appears,otherwise the same screen displays the list of errors.

3BK 21215 AAAA PCZZA Ed.25 65 / 162


66/162

5 Import Management


66 / 162 3BK 21215 AAAA PCZZA Ed.25


67/162

5 Import Management

5.1.8 Import GPRS Distribution Threshold Values (GSM specific)


To import GPRS Distribution Threshold values from the input (csv) file:



2. Select Import Data -> GPRS Distribution Thresholds.




4. Click as appropriate on:

[ Replace ] to replace the old GPRS Distribution Threshold values with

the new ones. The old threshold values are destroyed.

[ Update ] to update the old values with the new ones from the import file.

Only the old threshold values that must be updated are destroyed.



The threshold values are imported according to the selected mode.


The window displays the list of imported files and their properties (File

Name, Dictionary name, BSSVersion, Number of lists), as well as theimport status of the file (OK or NOK).


Check that the imported .csv file is correct. If not, correct it and re-attemptthe import.

3BK 21215 AAAA PCZZA Ed.25 67 / 162


68/162

5 Import Management


68 / 162 3BK 21215 AAAA PCZZA Ed.25


69/162

5 Import Management

5.1.9 Import RMS Template Values (GSM specific)

RESTRICTION3BKA17CBR211154

Only one RMS file can be loaded per day.


To Import RMS Template Values from input (csv) file:



2. Select Import Data -> RMS Template.




4. Click as appropriate on:

[ Replace ] to replace the old RMS template values with the new ones.

The old RMS values are destroyed.

[ Update ] to update the old values with the new ones from the import file.

Only the old RMS template values that must be updated are destroyed.



The RMS template values are imported according to the selected mode.


The window displays the list of imported files and their properties (FileName, Dictionary name, Version, Number of templates), as well as theimport status of the file (OK or NOK).


Check that the imported .csv file is correct. If not, correct it and re-attemptthe import.

3BK 21215 AAAA PCZZA Ed.25 69 / 162


70/162

5 Import Management


view.

70 / 162 3BK 21215 AAAA PCZZA Ed.25


71/162

5 Import Management

5.1.10 Import Raster File

The raster file is a bitmap image consisting of a matrix of pixels. Raster filescan be of the following format: .jpg. .jpeg, .bmp, .tif, .tiff, .png.

A raster file is available in the local file system of the client with itsgeoreference file. The georeference file can be of .txt or .rast type. Itssupported geographical coordinates is Long/Lat wgs84.

The georeference file is composed of:

A field that specifies the name of the raster map to import.

A Long/Lat wgs84 projection

A list of points that allows to calibrate the background map and calculate

the geo-referencing pointsAt least two points must be given. If less than two points are present, anexception is raised and associated background map is not imported.

For a Long/Lat wgs84 projection, units field must be degrees. Moreover,

geo-referencing points must be expressed in decimal degrees.

In raster map, plus sign for latitude means North and minus sign means South.Similarly, plus sign for longitude stands for West and minus sign signifiesEast. In the Analysis Desktop is shown E (EAST), W (West), N (North) andS (South) instead of sign.

The only supported Coordinate System Earth Projection is 1, 104.

The Label values are the coordinates of the pixels in the raster file. Thesecoordinates should be the upper left and lower right pixels of the raster, neededto minimize numerical errors at the projection. Example: for a raster of3000x2000, the points should be (0,0) and (3000,2000).

An ASCII file coming from MapInfo for a Long/Lat wgs84 projection hasLongitude in X axis and Latitude in Y axis.

Example of ASCII file coming from MapInfo for a Long/Lat wgs84 projection:

!table

!version 300

!charset WindowsLatin1

Definition Table

File "map.bmp"

Type "RASTER"

(-88.18435555,13.49508333) (0,0) Label "",

(-88.18435555,13.47986944) (0,699) Label "",

(-88.160075,13.47986944) (1072,699) Label ""CoordSys Earth Projection 1, 104

Units "degree"

In this example the coordonates (-88.18435555,13.49508333) are for LONG,LAT.

NPO uses Latitude in X axis and Longitude in Y axis. There is also an inversionsign to do on longitude, before importing the raster file in NPO.

Example of how the georeference file must be modified, before import:

!table

!version 300

!charset WindowsLatin1

Definition TableFile "map.bmp"

3BK 21215 AAAA PCZZA Ed.25 71 / 162


72/162

5 Import Management

Type "RASTER"

(13.49508333, 88.18435555) (0,0) Label "",

(13.47986944, 88.18435555) (0,699) Label "",

(13.47986944, 88.160075) (1072,699) Label ""

CoordSys Earth Projection 1, 104

Units "degree"

In this example the coordonates (13.49508333, 88.18435555) are for LAT,LONG.

You can use the default windows calculator for degree minute second formatconversion if you need. The formula for convert the degree minute secondformat to real number format is: Degrees+(Minutes*60+Seconds)/3600.

Procedure To Import raster file for cartography:



2. Select Import -> Raster File.

3. In the newly opened window, type the preferred label for the Layer Name.

For raster file, Layer Type is always Background.

4. In the Select a Raster file field, browse for the file to import.



72 / 162 3BK 21215 AAAA PCZZA Ed.25


73/162

5 Import Management

5. Click on [ OK ].

6. In the Select a georeference data file for import field, browse for thegeoreference data file that must match the raster file.



7. Click on [ OK ].




The window displays the list of layer imported with properties such as FileName (both raster file name and georeference file name), as well as theimport status of the file (OK or NOK).


Check that the imported file is correct. If not, correct it and re-attemptthe import.

3BK 21215 AAAA PCZZA Ed.25 73 / 162


74/162

5 Import Management


74 / 162 3BK 21215 AAAA PCZZA Ed.25


75/162

5 Import Management

5.1.11 Import Vector File

The feature described in this section is not planned for W-CDMA.

The vector file is a cartography file that contains objects and shapes usingmathematical coordinate systems and formulas.

The supported file formats for vectors are the MIF/MID formats from the AlcatelRNP V6 tool and MAPInfo version 300 and 450.

Note: The name of the vector files must be of the following type:_.mid and _.mif respectively,where is the network object type (can be Cell, BTS, etc.).

Colors and rendering attributes of the vectors are stored in the database andused by the Cartography module to render the vector layers.

The only supported Coordinate System Earth Projection is 1, 104.

Example of a MIF V450 vector file:VERSION 450Charset "WindowsLatin1"

Delimiter ","

CoordSys Earth Projection 1,104 Bounds (94,95) (-1,0)

COLUMNS 1

LEGEND Char(50)

DATA

Region 1

31

94.558724 -0.156045

94.558724 -0.155143

94.556932 -0.155143

94.556932 -0.15424194.556036 -0.154241

94.561412 -0.156046

94.558724 -0.156045

Region 1

15

94.559619 -0.161458

94.559620 -0.156046

94.561412 -0.156046

94.561412 -0.155144

Procedure To import a vector file for cartography:



2. Select Import Data -> Vector File.

3. In the newly opened window, type the preferred label for the Layer Name.

4. For Layer Type, select as appropriate Background or CCA.

5. For Technology, select the appropriate standard.

6. In the Select a MIF file field, browse for a .MIF file to import.



3BK 21215 AAAA PCZZA Ed.25 75 / 162


76/162

5 Import Management

7. Click on [ OK ].

8. Optionally, In the Select a MID file for import field, browse for the .MIDfile that must match the raster file.

The name of the CCA .MID file should be of the following type:_.mid, where is the object typesupported by the parameter domain (e.g. Cell_TestFile.mid).

Only one combination of MID/MIF file is allowed.Only one MIF file can be selected for import, but this is not the case of MID files.



9. Click on [ OK ].


operation.

76 / 162 3BK 21215 AAAA PCZZA Ed.25


77/162

5 Import Management



The window displays the name of the layer imported along with propertiessuch as MID/MIF File Name, as well as the import status of the file (OKor NOK).


Check that the imported file is correct. If not, correct it and re-attemptthe import.


view.

3BK 21215 AAAA PCZZA Ed.25 77 / 162


78/162

5 Import Management

5.1.12 Import THL Template Dictionary

To import a Thematic Layer Template dictionary:


The "NPO Import/Export Management" window opens.2. Select Import Dictionary -> Import THL Template Dictionary.








5. Click on [ OK ].

A list of the import files along with their properties (File Name, Type,Dictionary Name, Release, Creation Date and option to import the dictionaryin create/add mode) appears.The following operations are available:

Create to create new THL Template dictionariesAll previous entries in the database are destroyed.

Add to add new THL Template dictionaries.If the database already contains other THL Template dictionaries, theyare overwritten by the imported one.

The Create option is only available for Customer dictionaries. It isautomatically pre-selected for all dictionaries.

78 / 162 3BK 21215 AAAA PCZZA Ed.25


79/162

5 Import Management

6. Click on the appropriate radio button to create/add THL Templatedictionaries, then click on [ OK ].



7. When the import is d

npo administration guide

Documents