NPO Administration Guide

Alcatel-Lucent
NPO Administration Guide
NPO Document Administration Guide Release B10, M2, UA5, UA6
3BK 21215 AAAA PCZZA Ed.25
BLANK PAGE BREAK
Status Short title
RELEASED Administration Guide

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent.
2 / 162
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1 Key Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 NPO Automatic Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.1 Data Loading and Consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.2 Scheduled Reports Computation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.1 System Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.2 Customer Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Object Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 Start NPO Administration Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Start NPO Import / Export Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Close Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NPO Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 System Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Configure Storage Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.1 Configure Indicators Storage Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2 Configure Parameter Storage Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.3 Configure Laser Data Storage Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3 Storage Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4 Display Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5 Change Working Hours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6 Manage RMS Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7 Manage GPRS Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8 Modify Unavailability Origin List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9 Modify Relevant Hours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10 Modify Working Zone Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.11 Secure Global Working Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Import Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Import Management Using Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.1 Import QoS Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.2 Import Reports Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.3 Import Parameters Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.4 Import Planned Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.5 Import Parameter Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.6 Import Parameter Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.7 Import Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.8 Import GPRS Distribution Threshold Values (GSM specific) . . . . . . . . . . . . . . . . 5.1.9 Import RMS Template Values (GSM specific) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.10 Import Raster File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.11 Import Vector File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.12 Import THL Template Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.13 Import Diagnosis Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.14 Import Customer Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.15 Import Customer Topology Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.16 Import Free Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.17 Import Laser Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.18 Import Laser File On Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.19 Import Customer Acceptance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 Import Management Using Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.1 Import QoS Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.2 Import Reports Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 16 16 17 18 18 18 20 21 22 24 27 29 30 32 32 33 33 35 35 37 38 41 43 45 46 47 49 50 50 54 57 59 62 63 65 67 69 71 75 78 81 84 85 86 87 89 92 95 95 97
3 4
3 / 162
Contents
5.2.3 Import Parameters Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 5.2.4 Import Historical Parameters Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 5.2.5 Import Planned Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 5.2.6 Import THL Template Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 5.2.7 Import Diagnosis Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 5.2.8 Import Parameters Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 5.2.9 Import Parameter Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 5.2.10 Import GPRS Distribution Threshold Values (GSM specific) . . . . . . . . . . . . . . . 103 5.2.11 Import RMS Template Values (GSM specific) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 5.2.12 Import Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 5.2.13 Update Customer Objects Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 5.2.14 Load Customer Topology Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 5.2.15 Load Free Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 5.2.16 Import Tuning Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 5.2.17 Import Laser Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 5.2.18 Load Laser Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 5.2.19 Import Customer Acceptance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Export Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 6.1 Export Management Using Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 6.1.1 Export QoS Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 6.1.2 Export Reports Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 6.1.3 Export Diagnosis Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 6.1.4 Export Parameter Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 6.1.5 Export Parameter Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 6.1.6 Export GPRS Distribution Thresholds (GSM specific) . . . . . . . . . . . . . . . . . . . . 119 6.1.7 Export RMS Template (GSM Specific) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 6.1.8 Export THL Template Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 6.2 Export Management Using Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 6.2.1 Export QoS Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 6.2.2 Export Reports Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 6.2.3 Export Diagnosis Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 6.2.4 Export Parameter Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 6.2.5 Export Parameter Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 6.2.6 Export THL Template Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Delete Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 7.1 Delete Management Using Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 7.1.1 Delete QoS Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 7.1.2 Delete Reports Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 7.1.3 Delete Planned Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 7.1.4 Delete Diagnosis Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 7.1.5 Delete Parameter Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 7.1.6 Delete Parameter Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 7.1.7 Delete Cartography File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 7.1.8 Delete Customer Object Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 7.1.9 Delete Customer Acceptance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 7.2 Delete Management Using Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 7.2.1 Delete QoS Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 7.2.2 Delete Report Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 7.2.3 Delete All Planned Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 7.2.4 Delete Diagnosis Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 7.2.5 Delete Parameter Reference Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 7.2.6 Delete Parameter Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 7.2.7 Delete Customer Objects Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 7.2.8 Delete Customer Acceptance List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 NPO Maintenance Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 8.1 Consolidation Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
4 / 162
Contents
8.1.1 On-Demand Consolidation of Unavailability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.2 Launch Consolidation Follow-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2 Manage Job Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.1 Download Job Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.2 Delete Job Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3 Manage Scheduled Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4 Import Follow-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5 Load Radio Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6 Mark Inactive Network Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.7 Metadata Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8 Customer Topology Objects Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8.2 Create Customer Topology Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8.3 Load Customer Topology Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8.4 Delete Customer Topology Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9 Planned Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9.2 Manual Import Planned Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9.3 Schedule Planned Data Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9.4 Automatic Import of Planned Data (Non Delta) . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9.5 Delete Planned Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Update Identification Mode from CI to LAC/CI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1 Check Current Identification Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2 Change Identification Mode from CI to LAC/CI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
142 143 146 146 146 147 148 150 151 153 154 154 154 155 157 157 157 158 158 158 160 161 162 162
5 / 162
Contents
6 / 162
Preface
Preface
Purpose
This guide describes how to perform administrative tasks for the Network Performance Optimizer (NPO). For more information about NPO procedures, refer to the NPO User Guide. For more information about MUSE administration procedures, refer to the 9953 MP / NPO Platform Administration Guide. The W-CDMA / WiMAX references that appear in the document do not apply for the 9159 NPO. Alcatel-Lucent 9953 MS-OMC PORTAL will be later referred as 9953 MP.
Whats New
In Edition 25
Import 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 the coordinates Long/Lat that must be reversed manually before importing the raster file in NPO. There is also an inversion sign to do on longitude.
In Edition 24
The 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.
In Edition 21
The following sections are updated: Object Deletion (Section 1.3)
7 / 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) and Start NPO Import / Export Management (Section 2.2) are updated with a notice.
8 / 162
Preface
In Edition 20
The 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).
In Edition 17
The following sections are updated: 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 16
A 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 15
New 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 to Alcatel-Lucent 9953 MS-OMC PORTAL.
In Edition 14
Configure Storage Duration (Section 4.2) is updated. The document administrative part is updated.
9 / 162
Preface
In Edition 13
"1353 MS-OMC Portal name is changed to 9953 MP, and A9159 NPO into 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 by Launch 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
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 10
New 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 the function 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.
11 / 162
Preface
In Edition 04
New chapter added: Metadata Inventory (Section 8.7). Overall document editorial review.
In Edition 03
The following sections are updated: 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 Platform Administration 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" is updated. Step 13 of the Procedure of "Move BSS Inter NPO" is updated.
In Edition 01
First official release of document.
12 / 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.
13 / 162
Preface
14 / 162
1 Key Concepts
1 Key Concepts
This section describes the basic principles of NPO administration.
15 / 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 loading is 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 exchange directory of a declared data source. The exchange directory may be either a local directory, or a directory accessible via FTP. The NPO checks the new PM file version, calculates basic indicators from counters, and loads the new PM indicator data in the data warehouse. Both the topology data and the QoS 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 on the 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 purge process (there is no reorganization, normalization, temporal or special aggregation). By default, the weekly consolidation is done each MONDAY at 01:00 oclock.
16 / 162
1 Key Concepts
The monthly consolidation is automatically done on the first day, at 01:00 oclock 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 using the [ Consolidate ]/[ Recover ] actions described in Launch Consolidation Follow-Up (Section 8.1.2). To perform a manual UA consolidation, refer to On-Demand Consolidation of Unavailability (Section 8.1.1). To view the follow-up of a consolidation process, refer to Launch Consolidation Follow-Up (Section 8.1.2).
1.1.2 Scheduled Reports Computation

Scheduled reports are automatically executed during the night after consolidation is performed. To schedule the reports, refer to the NPO User Guide, to Schedule Reports. All the job results are stored in the result job zone. When the result job zone size is bigger than 2Gb, the oldest job results are automatically purged.
17 / 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 (mostly threshold values) dictionaries are described in XML format. Each dictionary file has a header with the following information. Content Name Version Date Author Comments Dictionary name Version Publishing date Name of the team or person responsible for publishing Free comment (change log or comments)
Description
1.2.1 System Dictionaries

The system dictionaries are delivered with the software and must be imported after 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 Import Management (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 automatically created, if needed, when the operator creates a customer indicator or a threshold. The customer indicator dictionary contains the definitions of customer indicators and of the customer threshold on customer indicator There is only one customer report dictionary in the NPO. It is automatically created, if needed, when the operator creates a customer report.
18 / 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 Import Management (Section 5).
19 / 162
1 Key Concepts
1.3 Object Deletion

The purge of object in NPO database is based on some specific concepts: Root loading objects Root loading object is an equipement in the network that is responsible to collect data (counters for example) from the network elements and to report them to the OMC (e.g.: BSC/MFS in 2G, RNC/NODEB in 3G) Soft-deletion is a procedure consisting in marking in NPO database, the neworks objects that NPO detected as no more operational. The different algorithms are described hereafter. There is a process of soft-deletion performed once a day, during the night, to mark as soft-deleted all root loading objects that have not been reported for a given period (default value is 5 days). This procedure is marking also all children and associated relations of this RLO. There is also a manual maintenance procedure to delete them, described in 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 a datasource is removed from the NPO, they are marked as soft deleted. This process takes place every night. For example, if the RNC does not provide any data for a cell during the day, then during the night the cell is marked as deleted. Also, the list of objects that were part of the removed data source are flagged as deleted. Other objects present in the parameter files. These objects are soft-deleted after any parameter loading (i.e. manual loading 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 removed from the database (hard deleted).
20 / 162
2 Start Administration
This section describes how to open administration pages.
21 / 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 -> Data Management.
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 :Do you want the Firefox to remeber your password?. Click on [ Never on this site ]. The "NPO Data Management" window opens.
22 / 162
Figure 2: "NPO Data Management" Window
23 / 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 :Do you want the Firefox to remeber your password?. Click on [ Never on this site ]. The "NPO Import/Export Management" window opens.
24 / 162
Figure 3: "NPO Import/Export Management" Window This menu is only applicable for products based on the MUSE platform (the NPO and 9953 MP). It may be different for NPO embedded.
25 / 162
26 / 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.
27 / 162
28 / 162
4 NPO Configuration Tasks

This section describes NPO configuration tasks.
29 / 162
4.1 System Scheduling

To set/unset the scheduling of consolidation, job computation and import parameter 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 Consolidation Description Consolidation and Purge (daily, weekly, and monthly). Weekly consolidation is set on Sunday and monthly consolidations on last day of the month. Consolidations are done at local time. Job computation Import Parameters Planned Data Laser Job Scheduled report execution. Automatic load data for parameters. Import of planned data. 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 Scheduling Configuration. 5. Click on [ End ].
30 / 162
31 / 162
4.2 Configure Storage Duration

Alcatel-Lucent does not recommend to change the values from configuration files with values bigger than the default ones! The administrator can launch the configuration of indicators, parameters, and LASER data storage duration. The MUSE_DATA_ADMIN FAD is needed for these operations. Periodicity can be Raw, Normalized, Day, Week or Month. When the storage duration is not defined for an object type, the default storage duration is applied. Refer to NPO User Guide, section PM Data Purge for the 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 root the 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 storage duration file. Do not modify the first two lines of the file NewStorageDuration.csv file.
3. Run the /alcatel/muse/MUSE_ADMIN/bin/ConfigIndDuration.sh script, giving as argument the full pathname of the file that contains the duration 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 less than 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 disk space available. The storage duration values are then updated in the database and the status of the operation is displayed to the administrator. The next time the purge runs (typically the next night), the new duration is taken into account.
32 / 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 root the 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), the MAX_PREV_DAYS attribute to indicate the new maximum number of days for parameters storage duration. 3. Run the following script: /alcatel/muse/MUSE_ADMIN/bin/Configure.sh -p <new_storage_duration_file> Where <new_storage_duration_file> is the absolute path and name of the 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 less than 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 disk space available. The parameter storage duration is updated in the database, and is used for Parameter 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 taken into 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/
33 / 162
Make sure that the new values are not greater than the Alcatel-Lucent recommendations: 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 the laser-partition.properties file with correct values. In case the new values are greater than the Alcatel-Lucent recommendation, the system warns the administrator to check that there is enough disk space available. The next time the purge runs (typically the next night), the new duration is taken into account.
34 / 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 following script: df h /alcatel/oracle/oradata/ 3. In the common.properties file, set the ASM_LIMIT parameter with 250GB smaller 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 -> View Licenses. 2. The NPO Data Management - View Licenses window opens. The main panel displays the host id of the server on which the licenses are installed, 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 column headers. A little arrow marks the ascending or descending order.
35 / 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 launching the command line:
/alcatel/muse/MUSE_ADMIN/bin/viewLicenses.sh
36 / 162
4.5 Change Working Hours

Working hours are used for stored temporal aggregation (refer to the NPO User Guide, to Aggregation). When this option is enabled for an indicator, the daily aggregation takes only the data in the relevant hours. To configure the working hours (also called relevant hours), 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, the parameter must contain the following values RELEVANT_HOUR_BEGINS_ON=9 and RELEVANT_HOUR_ENDS_ON=19
37 / 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 display its groups. From the List of Template Group, select the appropriate template group to display 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 predefined function 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 automatically calculated and displayed as shown in figure below.
38 / 162
The List of Interpolation Method is not displayed if the group contains an heterogeneous set of parameters. Edit the Current Value of the parameter.
Click on: [ Save ], to save modifications on the updated parameter values The The RMS Template data is saved successfully message appears 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 the operation. Wait for the end of the export. When the export is done, another window opens displaying the properties 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 the operation. Wait for the end of the export.
39 / 162
When the export is done, another window opens displaying the properties 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
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 display its 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 predefined function 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.
41 / 162
If a predefined function is chosen, only the first and the last values of the list can be modified. Intermediate values are then automatically calculated and displayed. Edit the Current Value of the parameter.
Click on: [ Save ], to save modifications on the updated parameter values The The GPRS Distribution Thresholds data is saved successfully 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 the operation. 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 exported to the OMC. Click on [ End ] to return to the "NPO Import / Export Management" main view. 5. To export GPRS Threshold:
42 / 162
Click on [ Export to OMC ] Click on [ OK ] at the confirmation message The progress bar displays the progress and eventual completion of the operation. 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 the OMC. Click on [ End ] to return to the "NPO Import / Export Management" main view.
4.8 Modify Unavailability Origin List

This section is not applicable for W-CDMA. The unavailability (UA) origin list defines the alarms and the logs that are potentially the origins of the unavailability start. To modify the Unavailability Origin List: 1. From the NPO Data Management window, select Configuration -> Modify Unavailability Origin. The "Modify Unavailability Origin List" window appears. You can sort by name all the columns of the table by clicking their column headers. A little arrow marks the ascending or descending order.
2. In the Technology Type field, select the appropriate technology for which you want the logs and alarms be displayed. 3. To enable all the alarms, [ All Alarms ] checkbox must be checked. This is done by default.
43 / 162
4. To enable or disable any unavailability origin, check/uncheck the corresponding checkbox. If the UA origins are disabled, at the next Laser dictionary loading, these origins are not taken into account. 5. Click on [ Save ] to save the performed changes.
44 / 162
4.9 Modify Relevant Hours

This section is not applicable for W-CDMA. 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 start and 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.
45 / 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 User Guide, 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 to the needed value. Example: MAX_CORE_OBJECT_COUNT=2000. Changing these parameters is not under Alcatel-Lucent responsibility. Putting higher values then the values tested in Alcatel-Lucent labs may cause higher response time or even request that do not answer.
46 / 162
4.11 Secure Global Working Zone

The administrator can modify the Secured property of the Global Working Zone and also grant this right to other users. 1. In Analysis Desktop window, Working Zone editor, Edit Working Zone and 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 to open the Global Working Zone and modify its attributes.
47 / 162
48 / 162
5 Import Management
5 Import Management
This section describes file import management.
49 / 162
5 Import Management
5.1 Import Management Using Graphical User Interface

After a create/add/update/load of new dictionary, if any Analysis Desktop windows were already opened, perform a Refresh All action for each window.
5.1.1 Import QoS Dictionary

To import counters, indicators or the thresholds dictionary: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 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 to import 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
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 Option column, select the indicator type Restricted Counters or All Counters, as appropriate. 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 one to one with an indicator will be displayed.
The following operations are available: Create to create new QoS dictionaries All previous entries in the database are destroyed.
51 / 162
5 Import Management
Add to add new QoS dictionaries If the imported QoS dictionary contains pre-existing indicators/counters/thresholds, they are overwritten by the imported definition. 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 the database. For customer QoS dictionary import, you can use any option: Create, Add or Replace. For system (Alcatel-Lucent) QoS dictionary import, only use the Create option. 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 well as the import status of each file (OK or NOK). If errors occur during the import operation, the same screen displays the list of errors. Check that the imported .xml file is correct. If not, correct it and re-attempt the import.
52 / 162
5 Import Management
Figure 6: Example of QoS Dictionary Import Window 9. Click on [ End ] to return to the "NPO Import / Export Management" main view.
53 / 162
5 Import Management
5.1.2 Import Reports Dictionary

Note:
In the case of a customer reports import, the "name" attribute from the header tag must be "CUSTOMER_REPORT_DICTIONARY". Example: <Header date="2007-06-12+03:00" name="CUSTOMER_REPORT_DICTIONARY" type="CUSTOMER" version="1"/> To import a reports dictionary: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 2. Select Import Dictionary -> Report Dictionary. 3. In the Select a file for import field, browse for the .xml file(s) to import. 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 to import 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 ]. 5. Click on [ OK ]. A list of the import files along with their properties appears.
54 / 162
5 Import Management
6. The following operations are available: Create to create new Report dictionaries All previous entries in the database are destroyed. Add to add new Report dictionaries If 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 the database. 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 (File Name, Technology, Owner and Number Of Definitions), as well as the import status of each file (OK or NOK). If errors occur during the import operation, the same screen display the list of errors. Check that the imported .xml file is correct. If not, correct it and re-attempt the import.
55 / 162
5 Import Management
9. Click on [ End ] to return to the "NPO Import / Export Management" main view.
56 / 162
5 Import Management
5.1.3 Import Parameters Dictionary

To Import a parameters dictionary: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 2. Select Import Dictionary -> Parameter Dictionary. 3. In the Select a file for import field, browse for the .xml file(s) to import. 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 to import 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 ]. 5. Click on [ OK ]. A list of the import files along with their properties appears.
6. The following operations are available: Create to create new Parameter dictionaries All previous entries in the database are destroyed.
57 / 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 the database, they are added in the database. 7. Click on the appropriate button to create/update 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 (File Name, Type, Release, Creation Date and Number Of Definitions), as well as the import status of each file (OK or NOK). If errors occur during the import operation, the same screen displays the list of errors. Check that the imported .xml file is correct. If not, correct it and re-attempt the import.
58 / 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: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 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.
59 / 162
5 Import Management
5. Click on [ Add ], to add the selected .zip file to the Files selected to import 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 ].
Note:
The .zip files must have a different time stamp from the last import, otherwise the 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 objects The objects already in the database (not part of incoming data) are not taken 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
5 Import Management
In Delta or Non-Delta mode, all RNP project or just a coherent subset is imported. In WiMAX technology, the following dependencies must be taken into account: 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 The progress bar displays the progress and eventual completion of the operation. Wait for the end of the import. 7. When the import is done, the following window opens with the result of the import.
61 / 162
5 Import Management
5.1.5 Import Parameter Reference Values

The feature described in this section is not yet available for W-CDMA. To import Parameter Reference values: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 2. Select Import Data -> Parameter Reference Value. 3. 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. 4. Click on [ OK ]. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the import. 5. 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 (File Name, Type, Dictionary name, Author, Release, Creation Date, Available Worksheets, and Type), as well as the import status of each file (OK or NOK). If errors occur during the import operation, the same screen displays the list of errors. Check that the imported .xls file is correct. If not, correct it and re-attempt the import.
62 / 162
5 Import Management
5.1.6 Import Parameter Rules

The feature described in this section is not yet available for W-CDMA. To import Parameter Rules: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 2. Select Import Data -> Parameter Rules. 3. 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. 4. Click on [ OK ]. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the import. 5. When the import is done, another window opens with the result of the import.
63 / 162
5 Import Management
The window displays the list of imported files and their properties (File Name, Type, Dictionary name, Author, Release, Creation Date, Available Worksheets, and Type), as well as the import status of each file (OK or NOK). If errors occur during the import operation, the same screen display the list of errors. Check that the imported .xls file is correct. If not, correct it and re-attempt the import.
64 / 162
5 Import Management
5.1.7 Import Parameter Values

To import the parameter values: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 2. Select Import Data -> Parameter Values. 3. Click on [ OK ] at the confirmation message.
The progress bar displays the progress and eventual completion of the operation. Wait for the end of the import. 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.
65 / 162
5 Import Management
66 / 162
5 Import Management
5.1.8 Import GPRS Distribution Threshold Values (GSM specific)

This section is not applicable for W-CDMA. To import GPRS Distribution Threshold values from the input (csv) file: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 2. Select Import Data -> GPRS Distribution Thresholds. 3. 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. 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 progress bar displays the progress and eventual completion of the operation. Wait for the end of the import. The threshold values are imported according to the selected mode. 5. 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 (File Name, Dictionary name, BSSVersion, Number of lists), as well as the import status of the file (OK or NOK). If errors occur during the import operation, the same screen displays the list of errors. Check that the imported .csv file is correct. If not, correct it and re-attempt the import.
67 / 162
5 Import Management
68 / 162
5 Import Management
5.1.9 Import RMS Template Values (GSM specific)

RESTRICTION
3BKA17CBR211154 Only one RMS file can be loaded per day.
This section is not applicable for W-CDMA. To Import RMS Template Values from input (csv) file: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 2. Select Import Data -> RMS Template. 3. 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. 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 progress bar displays the progress and eventual completion of the operation. Wait for the end of the import. The RMS template values are imported according to the selected mode. 5. 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 (File Name, Dictionary name, Version, Number of templates), as well as the import status of the file (OK or NOK). If errors occur during the import operation, the same screen displays the list of errors. Check that the imported .csv file is correct. If not, correct it and re-attempt the import.
69 / 162
5 Import Management
70 / 162
5 Import Management
5.1.10 Import Raster File

The raster file is a bitmap image consisting of a matrix of pixels. Raster files can 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 its georeference file. The georeference file can be of .txt or .rast type. Its supported 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 points At least two points must be given. If less than two points are present, an exception 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 signifies East. In the Analysis Desktop is shown E (EAST), W (West), N (North) and S (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. These coordinates should be the upper left and lower right pixels of the raster, needed to minimize numerical errors at the projection. Example: for a raster of 3000x2000, the points should be (0,0) and (3000,2000). An ASCII file coming from MapInfo for a Long/Lat wgs84 projection has Longitude 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 inversion sign 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 Table File "map.bmp"
71 / 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 format conversion if you need. The formula for convert the degree minute second format to real number format is: Degrees+(Minutes*60+Seconds)/3600.
Procedure
To Import raster file for cartography: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 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. 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.
72 / 162
5 Import Management
5. Click on [ OK ]. 6. In the Select a georeference data file for import field, browse for the georeference data file that must match the raster file. 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.
7. Click on [ OK ]. 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 layer imported with properties such as File Name (both raster file name and georeference file name), as well as the import status of the file (OK or NOK). If errors occur during the import operation, the same screen display the list of errors. Check that the imported file is correct. If not, correct it and re-attempt the import.
73 / 162
5 Import Management
74 / 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 using mathematical coordinate systems and formulas. The supported file formats for vectors are the MIF/MID formats from the Alcatel RNP V6 tool and MAPInfo version 300 and 450.
Note:
The name of the vector files must be of the following type: <object_type>_<name>.mid and <object_type>_<name>.mif respectively, where <object_type> is the network object type (can be Cell, BTS, etc.). Colors and rendering attributes of the vectors are stored in the database and used 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 450 Charset "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.154241 94.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: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 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. 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.
75 / 162
5 Import Management
7. Click on [ OK ]. 8. Optionally, In the Select a MID file for import field, browse for the .MID file that must match the raster file. The name of the CCA .MID file should be of the following type: <object_type>_<filename>.mid, where <object_type> is the object type supported 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. 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. 9. Click on [ OK ]. The progress bar displays the progress and eventual completion of the operation.
76 / 162
5 Import Management
Wait for the end of the import. 10. When the import is done, another window opens with the result of the import. The window displays the name of the layer imported along with properties such as MID/MIF File Name, as well as the import status of the file (OK or NOK). If errors occur during the import operation, the same screen displays the list of errors. Check that the imported file is correct. If not, correct it and re-attempt the import.
77 / 162
5 Import Management
5.1.12 Import THL Template Dictionary

To import a Thematic Layer Template dictionary: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 2. Select Import Dictionary -> Import THL Template Dictionary. 3. In the Select a file for import field, browse for the .xml file(s) to import. 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 to import 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 ]. 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 dictionary in create/add mode) appears.The following operations are available: Create to create new THL Template dictionaries All previous entries in the database are destroyed. Add to add new THL Template dictionaries. If the database already contains other THL Template dictionaries, they are overwritten by the imported one. The Create option is only available for Customer dictionaries. It is automatically pre-selected for all dictionaries.
78 / 162
5 Import Management
6. Click on the appropriate radio button to create/add THL Template dictionaries, then click on [ OK ]. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the import. 7. 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 (File Name, Dictionary Name, Type, Release, Creation Date ), as well as the import status of each file (OK or NOK). If errors occur during the import operation, the same screen displays the list of errors. Check that the imported .xml file is correct. If not, correct it and re-attempt the import.
79 / 162
5 Import Management
80 / 162
5 Import Management
5.1.13 Import Diagnosis Dictionary

To import the Diagnosis Dictionary: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 2. Select Import Dictionary -> Diagnosis Dictionary. 3. 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. 4. Click on [ Add ], to add the selected .xml file to the Files selected to import 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 ].
Figure 7: Example of Diagnosis Dictionary Import Window 5. Click on [ OK ]. A window appears, listing the import files along with their properties: File Name, Type, Dictionary Name, Release, Creation Date, and No. Of Scenarios, and option to import the dictionary in create/add mode.
81 / 162
5 Import Management
6. Select the appropriate mode to create/add the diagnosis dictionary, by clicking on the appropriate radio button: [ Create ], to create a new diagnosis dictionary. All previous entries are destroyed. [ Add ], to add a new diagnosis dictionary in the database. If a pre-existing scenario is not in the imported file, it is not affected, otherwise it is overwritten by the imported definition only if the old version is not referenced into other scenarios. Notice that: For system dictionaries, only Create option is available. By default, the Create option is pre-selected for all dictionaries. For customer dictionaries, both Create and Add modes are available. 7. Click on [ OK ]. 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 (File Name, Type, Technology, Release and No. Of Scenarios), as well as the import status of each file (OK or NOK). If errors occur during the import operation, the same screen displays the list of errors. Check that the imported file is correct. If not, correct it and re-attempt the import.
82 / 162
5 Import Management
Figure 8: Example of Diagnosis Dictionary Import Window 9. Click on [ End ] to return to the "NPO Import / Export Management" main view.
83 / 162
5 Import Management
5.1.14 Import Customer Object Types

To import customer object types: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 2. Select Import Dictionary -> Customer Object Types. 3. 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. 4. Click on [ Add ] to create the customer object and relations types. 5. When the import is done, the following window opens with the result of the import.
84 / 162
5 Import Management
5.1.15 Import Customer Topology Objects

To import customer topology objects: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 2. Select Import Data -> Customer Topology Objects. 3. 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. 4. Click on [ Add ] to create the customer topology objects and relations. 5. When the import is done, the following window opens with the result of the import.
85 / 162
5 Import Management
5.1.16 Import Free Fields

To import free fields: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 2. Select Import Data -> Free Fields. 3. 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. 4. Click on [ Add ]. All the free fields for the given type are first deleted, then the new free field values coming from the import file are stored in the database. 5. When the import is done, the following window opens with the result of the import.
86 / 162
5 Import Management
5.1.17 Import Laser Dictionary

The feature described in this section is not planned for W-CDMA. Use a Laser dictionary to describe and define data useful for unavailability. Laser dictionaries are delivered by Alcatel-Lucent and can be updated by import. To import a laser dictionary: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 2. Select Import Dictionary -> Laser Dictionary. 3. 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. 4. Click on [ OK ]. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the import. If the imported Laser file contains already existing dictionaries in the database, they are overwritten by the imported definition, otherwise they are not affected. 5. When the import is done, the following window opens with the result of the import. The window displays the list of imported files and their properties (Name, Version, Technology, Supplier, Description), as well as the import status of each file (OK or NOK). If errors occur during the import operation, the same screen displays the list of errors. Check that the imported file is correct. If not, correct it and re-attempt the import.
87 / 162
5 Import Management
88 / 162
5 Import Management
5.1.18 Import Laser File On Demand

The feature described in this section is not planned for W-CDMA. If you do not want to wait for the automatic nightly Laser file import, and wish to import it in recovery mode: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 2. Select Import Data -> Laser Files on Demand. A new window opens, displaying the available Laser datasources.
3. Select the checkbox corresponding to the appropriate Laser datasource, then click on [ OK ]. A new window opens, displaying the list of selected datasources and the available domains (such as Basic Unavailabilities, Alarms, Logs, etc.) with all the available files listed in the respective domains.
89 / 162
5 Import Management
4. Select the checkboxes corresponding to the Laser files to import, then click on [ Next ]. An information window appears, showing all the selected files to import.
5. Click on [ Next ]. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the import. 6. When the import is done, the following window opens with the result of the import.
90 / 162
5 Import Management
91 / 162
5 Import Management
5.1.19 Import Customer Acceptance List

The feature described in this section is not planned for W-CDMA. The Customer Acceptance List (CAL) is described in an ASCII file. To import a customer acceptance list: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. The "NPO Import/Export Management" window opens. 2. Select Import Data -> Customer Acceptance List. 3. 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. 4. Click on [ Add ], to add the selected file to the File(s) selected to import 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 the file and click on [ Remove ].
Figure 9: Example of Customer Acceptance List Import Window 5. Click on [ OK ].
92 / 162
5 Import Management
A window appears, listing the import files along with their properties: Customer Mnemonics, Customer Description, Date, Version, CAL Description.
6. Click on [ OK ], to create a new Customer Acceptance List. Any old already loaded CAL, with the same header (except the date field), is erased and replaced by the new loaded one. 7. Click on [ OK ]. 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 (Customer Mnemonic, Customer Description, Date, Version, CAL Description and Status ), as well as the import status of each file (OK or NOK). If errors occur during the import operation, the same screen displays the list of errors. Check that the imported file is correct. If not, correct it and re-attempt the import.
93 / 162
5 Import Management
94 / 162
5 Import Management
5.2 Import Management Using Command Line

After a create/add/update/load of new dictionary, if any Analysis Desktop windows were already opened, perform a Refresh All action for each window.
5.2.1 Import QoS Dictionary

To import a QoS dictionary, as root, run the following commands: cd /alcatel/muse/MUSE_QOS/offlinetool/bin/ ./import.sh <option> <dictionary_filepath_1> <dictionary_filepath_2> <dictionary_filepath_3] Where: <option> can be: For customer QoS dictionary: -N or -NR, to create new QoS indicators/counters/thresholds. All previous entries are destroyed. -U or -UR, to update Qos indicators/counters/thresholds in the database with the new values provided in the input file. All indicators updated must be already inthe database. -A or -AR, to add a new QoS dictionary. If a pre-existing QoS indicator/counter/threshold is not in the imported file, it is not affected, otherwise it is overwritten by the imported definition. -NC, to import new QoS indicators for counters dictionary. This is the only indicated option for 2G (GSM) technology. -UC, to update an existing QoS indicator for counters dictionary. This is the only indicated option for 2G (GSM) technology. -AC, to add a new QoS indicators for counters dictionary. This is the only indicated option for 2G (GSM) technology. For system (Alcatel-Lucent) QoS dictionary: -N or -NR, to import a new dictionary Option -C is used in the case of QoS indicators that do not have a one to one mapping with indicators in order to be able to display all Counters. Option -R is used in the case of counters that have a one to one mapping with an indicator (Restricted set of counters).
Note:
If no option is provided, then the loading is done with the option described inside the dictionary itself (in the header of the dictionary). <dictionary_filepath_n>, is the absolute path for the dictionary file (n=1,2,3)
Note:
By default, the QoS system dictionary is available at the following locations: For GSM at: /alcatel/muse/technologies/GSM/QoS/dictionary For W-CDMA at: /alcatel/muse/technologies/UMTS/QoS/dictionary. For WiMAX at: /alcatel/muse/technologies/WIMAX/QoS/dictionary.
95 / 162
5 Import Management
Examples: /import.sh -N
/alcatel/muse/technologies/UMTS/QoS/dictionary/MSNPO_M1_QoSCounters_ Cnt-3G.xml
./import.sh -N
/alcatel/muse/technologies/UMTS/QoS/dictionary/MSNPO_M1_QoSIndicators_ Ind-3G.xml
/import.sh -A
/alcatel/muse/technologies/GSM/QoS/dictionary/ MSNPO_M1_QoSCounters_Cnt-2G-Ev(2G-Ev-B9_G06-P06)_2005-11-30_14-24.xml
./import.sh -U
/alcatel/muse/M1Dictionary/2G/ MSNPO_M1_QoSIndicators_Ind-2G-Ev(2G-Ev-B9_MR2_p5-1)_2005-11-16_18-37.xml
./import.sh -NC
/alcatel/muse/technologies/GSM/QoS/dictionary/indicator1.xml /alcatel/muse/technologies/GSM/QoS/dictionary/counter.xml /alcatel/muse/technologies/GSM/QoS/dictionary/indicator2.xml
./import.sh -N
/alcatel/muse/technologies/WIMAX/QoS/dictionary/WimaxW3MR1Counters.xml /alcatel/muse/technologies/WIMAX/QoS/dictionary/WimaxW41Counters.xml /alcatel/muse/technologies//WIMAX/QoS/dictionary/WimaxIndicators.xml
A check of the dictionary consistency starts, according to the dictionary scheme definitions. In the case of problems, the operation aborts and the problem is logged and reported to the administrator. When the consistency checks are passed, the following elements are taken into consideration: If a dictionary does not exist for this technology, the new database scheme for operational and planned parameters is created If a dictionary already exists for this technology, the import script compares the new dictionary with the existing one: If a new parameter is added in the new dictionary definition, it is created in the database scheme If existing parameter properties are modified, but the name of the parameter is the same, no update is done in the database If an existing parameter changes its name (and also other properties), it is considered as new and it is created in the database scheme. A notification is then generated to indicate to all the radio parameters system clients that a new dictionary has been successfully imported.
96 / 162
5 Import Management
5.2.2 Import Reports Dictionary

Note:
In the case of a customer reports import, the "name" attribute from the header tag must be "CUSTOMER_REPORT_DICTIONARY". Example: <Header date="2007-06-12+03:00" name="CUSTOMER_REPORT_DICTIONARY" type="CUSTOMER" version="1"/> To import a report dictionary, as root, run the following commands: cd /alcatel/muse/MUSE_MAAT/reports/bin ./import.sh <option> <Dictionary File Name> Where: <option> can be: -N, to import a new report dictionary -U, to update an existing report dictionary -A, to add a new dictionary. <Dictionary File Name> is a absolute path and name of the dictionary file
Note:
By default, the reports dictionary location is available at the following locations: For GSM: /alcatel/muse/technologies/GSM/QoS/dictionary For W-CDMA: /alcatel/muse/technologies/UMTS/QoS/dictionary For WiMAX: /alcatel/muse/technologies/WIMAX/QoS/dictionary.
97 / 162
5 Import Management
5.2.3 Import Parameters Dictionary

To import a parameter dictionary, as root, run the following commands from the server: cd /alcatel/muse/MUSE_PARAM/offlinetool/bin ./run_import.sh <Technology Name> <Dictionary File> Where: <Technology Name> is GSM or W-CDMA <Dictionary File Name> is a absolute path and name of the dictionary file.
Note:
By default, the parameter dictionary location is available at the following locations: For GSM:
/alcatel/muse/technologies/GSM/Parameter/specificloader/dictionary
For W-CDMA:
/alcatel/muse/technologies/UMTS/Parameter/specificloader/dictionary
For WiMAX:
/alcatel/muse/technologies//WIMAX/Parameter/specificloader/dictionary.
Example of an import of a new GSM Parameter dictionary: ./run_import.sh GSM /alcatel/muse/technologies /GSM/Parameter/specificloader/dictionary/MSNPO_GSM_RP_M2.3S1.xml Example of an import of a new W-CDMA Parameter dictionary: ./run_import.sh UMTS /alcatel/muse/technologies /UMTS/Parameter/specificloader/dictionary/PARAM_UMTS_DICTIONARY Example of import of a new WiMAX Parameter dictionary: ./run_import.sh WiMAX/alcatel/muse/technologies /WIMAX/Parameter/specificloader/dictionary/Radio_WIMAX.xml
5.2.4 Import Historical Parameters Data

Before performing this procedure, make sure you comply with the following prerequisites: The import of historical parameters must be done only a clean database, i.e. no current/historical data must already be present The directory <Input_Directory>/<OMC_NAME> must exist and it should contain .gz files The <OMC_NAME> argument of the script must to equal to OWN_ID of the data source The archive files name should contain the date in YYMMDD format. e.g. export_0_AutomaticExport_1.tar.old.070319.220101.gz To import radio historical parameters, run as root the following commands: cd /alcatel/muse/MUSE_PARAM/loader/bin ./loadhistparam.sh <OMC Name> <OMC File Path> Example: ./loadhistparam.sh omc1_name /alcatel/omc1
98 / 162
5 Import Management
Where:
omc1_name is the directory name, and it should be same as OWN_ID of
the Parameter data source

/alcatel/omc1 is the relative path of the directory omc1_name. This
Directory contains the Parameter history archive files.
5.2.5 Import Planned Data

The feature described in this section is not yet available for W-CDMA. To import planned data, as root, run the following commands from the server: cd /alcatel/muse/MUSE_PARAM/plannedData/loader/bin ./runManualRnploader.sh <FileType Option> <zip File path> <Standard> [<Release>] <Mode> Where for: <FileType Option>, the following options are available: -NG, for non generic files such as GSM B9 files -G, for generic format files loading. Generic files should be inline with the planned data generic interface format. <zip File path> is the absolute path and name of the file <Standard> is the technology for which the files are to be loaded [<Release>] is the supported release of the technology for which files are to be loaded Note: In case of generic format (-G option used) zip file, this parameter is not required. <Mode> is the mode of the file import. This can be NON_DELTA_MODE or DELTA_MODE.
Note:
The .zip files must have a different time stamp from the last import, otherwise the import is not done (and no error message is displayed). In Delta or Non-Delta mode, all RNP project or just a coherent subset is imported. In WiMAX technology, the following dependencies must be taken into account: 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 Examples of planned data import scripts: Technology specific planned data files(GSM B9): DELTA MODE:
99 / 162
5 Import Management
./runManualRnploader.sh -NG /alcatel/muse/MUSE_PARAM/plannedData/loader/sampleFiles/ b9_rno.zip GSM B9 DELTA_MODE Technology specific planned data files(GSM B9): NON_DELTA MODE: ./runManualRnploader.sh -NG /alcatel/muse/MUSE_PARAM/plannedData/loader/sampleFiles/ b9_rno.zip GSM B9 NON_DELTA_MODE Generic format planned data files: DELTA_MODE (Ex. GSM files) ./runManualRnploader.sh -G /alcatel/muse/MUSE_PARAM/plannedData/loader/sampleFiles/ genericFormatFiles zip GSM DELTA_MODE Generic format planned data files: NON_DELTA_MODE (Ex. GSM files) ./runManualRnploader.sh -G /alcatel/muse/MUSE_PARAM/plannedData/loader/sampleFiles/ genericFormatFiles.zip GSM NON_DELTA_MODE The planned data is imported, as indicated by a confirmation notification.
5.2.6 Import THL Template Dictionary

To import THL Template dictionary, as root, run the following commands from the server: cd /alcatel/muse/MUSE_MAAT/cartography/bin ./importTHLDict.sh <option> <fileName> Where: <option> is the supported options for this build = {-N | -A} -N, to create a new THL dictionary If a THL template dictionary is being imported, the existing dictionary of the same name is completely replaced by the imported one. All previous entries are destroyed. So if the new dictionary has fewer scenarios, the old data for non-existing indicator in the new system is lost. -A, to add a new THL dictionary. If a pre-existing THL template dictionary is not in the imported file, it is not affected, otherwise it is overwritten by the imported definition. This option is only available for customer THL template dictionaries. <fileName> is the absolute path and name of the THL file. Example: ./importTHLDict.sh /alcatel/muse/technologies/GSM/cartography/TLD.xml
100 / 162
5 Import Management
5.2.7 Import Diagnosis Dictionary

To import a Diagnosis Dictionary, as root, run the following commands from the server: cd /alcatel/muse/MUSE_MAAT/diagnosis/bin ./importDiagDict.sh <option> <file name with full path> Where: <option> may be: -N, to create a new Diagnosis Dictionary. All previous entries are destroyed. -A, to add a new Diagnosis Dictionary. If a pre-existing scenario is not in the imported file, it is not affected, otherwise it is overwritten by the imported definition only if the old version is not referenced into other scenarios. <fileName> is the absolute path and name of the diagnosis dictionary.
Note:
For system dictionary, only -N (New) option is available. For customer dictionary, both -N and -A options are available. Example: ./importDiagDict.sh -N /tmp/SystemGSMDiagnosisMigratedFromRNOv5.xml The Diagnosis Dictionary is imported, as indicated by a confirmation notification.
101 / 162
5 Import Management
5.2.8 Import Parameters Reference Values

The feature described in this section is not yet available for W-CDMA. To import Reference Values, as root, run the following commands from the server: cd /alcatel/muse/MUSE_PARAM/rulesandrefs/bin/ ref_import.sh <fileName> Where <fileName> is the absolute path and name of the reference value excel file. Example: ref_import.sh /alcatel/muse/technologies/GSM/ Rules_Refs/M2_GSM_B10_Reference_Values.xls A check of the reference values file starts: On the first sheet of the workbook, the system checks that the file contains the name of the parameters dictionary and the release to use The reference values must conform to the dictionary grammar constraints If the new reference values file has a unique name and contains new values for the database, it is created in the Oracle database scheme If the new reference values file has the same name as an already existing file, a replace is performed. The reference values file is imported, as indicated by a confirmation notification.
5.2.9 Import Parameter Rules

The feature described in this section is not yet available for W-CDMA.
It is recommended to import System/Alcatel-Lucent Rules in separate files from Customer Rules, so that the Customer Rules are not deleted when importing a new file with System/Alcatel-Lucent Rules. To import rules, as root, run the following commands from the server: cd /alcatel/muse/MUSE_PARAM/rulesandrefs/bin/ rule_import.sh <fileName> Where <fileName> is the absolute path and name of the rule excel file. Example: rule_import.sh /alcatel/muse/technologies/GSM/Rules_Refs/M2_GSM_B9_Rules.xls A check of the rules file is performed: If the new rule file has a unique name and contains new rules for the database, it is created in the Oracle database scheme If the new rule file has the same name as an already existing rule file, a replace is performed
102 / 162
5 Import Management
If the new rule file contains already existing rules in the database, than those are not imported and a confirmation message appears If the new rule file contains both new and existing rules, than only the new rules are imported in the database; for the rest, the system displays a message that the rules are not imported If the new rule file name does not have the name in the first sheet, or the object type, or supplier are missing in one of the sheets, the import is cancelled and an error message appears. The rules are imported, as indicated by a confirmation notification.
5.2.10 Import GPRS Distribution Threshold Values (GSM specific)

This section is not applicable for W-CDMA. To import GPRS Distribution Thresholds Values, as root, run the following commands from the server: cd /alcatel/muse/MUSE_ADMIN/bin ./add_MUSE_RMS_GPRS_Values.sh <GPRSValues_name> GPRS Where <GPRSValues_name> is the absolute path and name of the GPRS Distribution Thresholds Values file. Example: ./add_MUSE_RMS_GPRS_Values.sh /alcatel/muse/MUSE_ADMIN/config/ ImportValGPRSDistributionThreshold.csv GPRS The GPRS Distribution Thresholds Values file is imported, as indicated by a confirmation notification.
5.2.11 Import RMS Template Values (GSM specific)

This section is not applicable for W-CDMA.
RESTRICTION
3BKA17CBR211154 Only one RMS file can be loaded per day. To import RMS Template values, as root, run the following commands from the server: cd /alcatel/muse/MUSE_ADMIN/bin ./add_MUSE_RMS_GPRS.sh <RMSValues_name> RMS Where <RMSValues_name> is the absolute path and name of the RMS Template Values file. Example: ./add_MUSE_RMS_GPRS.sh /alcatel/muse/MUSE_ADMIN/config/ImportValTmpl.csv RMS The RMS Template Values file is imported, as indicated by a confirmation notification.
103 / 162
5 Import Management
5.2.12 Import Event

The feature described in this section is not planned for W-CDMA. To import Events dictionary, as root, run the following commands from the server: cd /alcatel/muse/MUSE_PARAM/eventofflinetool/bin ./run_import.sh <technology> <fileName> <event dictionary xml file> Where: <technology> is the used technology name <fileName> is the absolute path and name of the Event Dictionary XML file.
104 / 162
5 Import Management
5.2.13 Update Customer Objects Types

To update customer object types, as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/topology/bin/ ./updateCOTypes.sh <fileName> Where <fileName> is the absolute path and name of the customer objects file. Example: ./updateCOTypes.sh /alcatel/muse/MUSE_QOS/topology/files/CustomerTypes.txt
5.2.14 Load Customer Topology Objects

To update customer topology objects, as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/topology/bin ./loadCOObjects.sh <fileName> Where <fileName> is the absolute path and name of the customer topology file. Example: ./loadCOObjects.sh /alcatel/muse/MUSE_QOS/topology/files/CustomerData.txt This sample file contains the customer objects instances for MSC and associated relations. The system type specified in the CustomerData file must already be present in the topology database.
105 / 162
5 Import Management
5.2.15 Load Free Fields

To update free fields, as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/topology/bin ./loadFreeFields.sh <fileName> Where <fileName> is the absolute path and name of the Free Fields file. Example: ./loadFreeFields.sh /alcatel/muse/MUSE_QOS/topology/files/FF.txt The NPO checks the operator access rights and that the maximum number of allowed free fields is not reached. The OEXIDs (Object External ID) in the free fields file must match the ones imported by either the Qos/Param topology import of the customer topology import.
5.2.16 Import Tuning Metadata

The feature described in this section is not yet available for W-CDMA. To import tuning metadata, as root, run the following commands from the server: cd /alcatel/muse/MUSE_TUNING/metadataimport/bin ./importTuningMetadata.sh <fileName> Where <fileName> is the absolute path and name of the tuning file. Example: ./importTuningMetadata.sh
/alcatel/muse/MUSE_TUNING/metadataimport/samplexml/gsmTuningMetadata.xml
The tuning metadata is imported, as indicated by a confirmation notification.
5.2.17 Import Laser Dictionary

The feature described in this section is not planned for W-CDMA. To import a laser dictionary, as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/Laser/offlinetool/bin ./laser_import.sh <fileName> Where <fileName> is the absolute path and name of the Laser Dictionary XML File. Example: ./laser_import.sh /alcatel/muse/technologies/GSM/Laser/dictionary/Laser.xml The Laser dictionary is imported and the basic unavailabilities (BU), as well as the other relevant tables are created.
106 / 162
5 Import Management
5.2.18 Load Laser Data

The feature described in this section is not planned for W-CDMA. Laser data indicates the daily (usual) mode of the Generic Loader run. Before running the loader, if needed, remove the entries for the given file (most recent one) from the LASER_GL_PMFILES table. To load Laser data, as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/Laser/loader/bin ./run_lasergl.sh <mode> <DOMAINS> Where: <mode> is DAILY or RECOVERY <DOMAINS> is any/all of the following: ALARM, LOGS, BU, HWINV, TOPO, or ALL. Several Domains can be used in one command, separated by comma. Examples: ./run_lasergl.sh DAILY ALL ./run_lasergl.sh RECOVERY ALARM,LOGS The Laser Loader loads the Laser data into the data warehouse. You can check the traces in
/alcatel/muse/data/trace/laser_loader_tracefile_*
5.2.18.1 Import Basic Unavailabilities

The feature described in this section is not planned for W-CDMA. To import basic unavailabilities (BU), as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/Laser/loader/bin ./run_lasergl.sh DAILY BU Laser data specific for the Basic UA is imported.
5.2.18.2 Import Alarms

The feature described in this section is not planned for W-CDMA. To import alarms, as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/Laser/loader/bin ./run_lasergl.sh DAILY ALARM Laser data specific for the alarms data is imported.
5.2.18.3 Import Logs

The feature described in this section is not planned for W-CDMA. To import logs, as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/Laser/loader/bin ./run_lasergl.sh DAILY LOGS
107 / 162
5 Import Management
Laser data specific for logs is imported.
5.2.18.4 Import Topology

The feature described in this section is not planned for W-CDMA. To import topology data, as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/Laser/loader/bin ./run_lasergl.sh DAILY TOPO Laser data specific for topology is imported.
108 / 162
5 Import Management
5.2.18.5 Import Files On Demand

The feature described in this section is not planned for W-CDMA. To import files on demand, as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/Laser/loader/bin ./run_lasergl.sh RECOVERY <Domain names> Where <Domain names> can be ALL or may be selectively chosen. Laser data specific for logs is imported.
5.2.18.6 Load Inventory

The feature described in this section is not planned for W-CDMA. To import logs, as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/Laser/loader/bin ./run_lasergl.sh RDAILY HWINV Laser data specific for logs is imported.
5.2.19 Import Customer Acceptance List

The feature described in this section is not planned for W-CDMA. To import a Customer Acceptance List (CAL), as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/Laser/CAL/bin ./run_importCAL.sh <fileName> Where <fileName> is the absolute path and name of the CAL files to be imported.
Note:
You can import multiple CAL files in one command, adding all CAL files separated by space. The Customer Acceptance List is imported, as indicated by a confirmation notification.
109 / 162
5 Import Management
110 / 162
6 Export Management
6 Export Management
This section describes the file export management.
111 / 162
6 Export Management
6.1 Export Management Using Graphical User Interface

6.1.1 Export QoS Dictionary
To export a QoS dictionary: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Export -> QoS Dictionary. The QoS Dictionary export window appears. It displays the list of dictionaries available for export, along with the radio buttons for unique selection.
3. Select the file to export, then click on [ OK ]. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the export. 4. The "NPO Export Management - QoS Dictionary" window appears, showing the export status (OK or NOK).
112 / 162
6 Export Management
Select one of the following options: Save file to disk, to save the file locally Type/browse for the location where the file must be saved, then click on [ OK ]. Open the file from current location, to visualize the file. The file opens in the browser. 5. Click on [ End ] to complete the operation.
113 / 162
6 Export Management
6.1.2 Export Reports Dictionary

To export a report dictionary: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Export -> Report Dictionary. The Report Dictionary export window appears. It displays the list of dictionaries available for export, along with the radio buttons for unique selection. 3. Select the file to export, then click on [ OK ]. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the export. 4. The "NPO Export Management - Report Dictionary" window appears, showing the export status (OK or NOK).
Select one of the following options: Save file to disk, to save the file locally. Type/browse for the location where the file must be saved, then click on [ OK ]. Open the file from current location, to visualize the file. The file opens in the browser.
114 / 162
6 Export Management
5. Click on [ End ] to complete the operation.
6.1.3 Export Diagnosis Dictionary

To export a diagnosis dictionary to an output (xml) file: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Export -> Diagnosis Dictionary. The "Diagnosis Dictionary Export" window appears. It displays the list of dictionaries available for export, along with the radio buttons for unique selection. 3. Select the file to export, then click on [ OK ]. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the export. 4. The "NPO Export Management - Diagnosis Dictionary" window appears, displaying the number of diagnosis definitions exported and the export status (OK or NOK).
Select one of the following options: Save file to disk, to save the file locally. Type/browse for the location where the file must be saved, then click on [ OK ].
115 / 162
6 Export Management
Open the file from current location, to visualize the file. The file opens in the browser. 5. Click on [ End ] to complete the operation.
6.1.4 Export Parameter Reference Values

To export parameter reference values: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Export -> Parameter Reference Values. The Parameter Reference Values export window appears. It displays the list of files available for export, along with the radio buttons for unique selection. 3. Select the file to export, then click on [ OK ]. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the export. 4. The "NPO Export Management - Parameter Reference Values" window appears, showing the export status (OK or NOK).
Select one of the following options: Save file to disk, to save the file locally.
116 / 162
6 Export Management
Type/browse for the location where the file must be saved, then click on [ OK ]. Open the file from current location, to visualize the file. The file opens in the browser. 5. Click on [ End ] to complete the operation.
117 / 162
6 Export Management
6.1.5 Export Parameter Rules

To export parameter rules: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Export -> Parameter Rules. The "Parameter Rules Export" window appears. It displays the list of files available for export, along with the radio buttons for unique selection. 3. Select the file to export, then click on [ OK ]. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the export. 4. The "NPO Export Management - Parameter Rules" window appears, showing the export status (OK or NOK).
Select one of the following options: Save file to disk, to save the file locally. Type/browse for the location where the file must be saved, then click on [ OK ]. Open the file from current location, to visualize the file. The file opens in the browser. 5. Click on [ End ] to complete the operation.
118 / 162
6 Export Management
6.1.6 Export GPRS Distribution Thresholds (GSM specific)

This section is not applicable for W-CDMA. To export GPRS distribution threshold values to an output (xml) file: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Export -> GPRS Distribution Thresholds. The "GPRS Distribution Thresholds Export" window appears. It displays the list of files available for export, along with the radio buttons for unique selection. 3. Select the file to export, then click on [ OK ]. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the export. 4. The "NPO Export Management - GPRS Distribution Thresholds" window appears, displaying the number of threshold lists exported and the export status (OK or NOK).
Select one of the following options: Save file to disk, to save the file locally.
119 / 162
6 Export Management
Type/browse for the location where the file must be saved, then click on [ OK ]. Open the file from current location, to visualize the file. The file opens in the browser. 5. Click on [ End ] to complete the operation. The export of GPRS Distribution Thresholds can also be done via Configuration -> Manage GPRS Thresholds menu. Refer to Manage GPRS Thresholds (Section 4.7).
120 / 162
6 Export Management
6.1.7 Export RMS Template (GSM Specific)

This section is not applicable for W-CDMA. To export RMS template value definition to an output (csv) file: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Export -> RMS Template. The "RMS Template Export" window appears. It displays the list of files available for export, along with the radio buttons for unique selection. 3. Select the file to export, then click on [ OK ]. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the export. 4. The "NPO Export Management - RMS Template" window appears, displaying the number of templates exported and the export status (OK or NOK).
Select one of the following options: Save file to disk, to save the file locally. Type/browse for the location where the file must be saved, then click on [ OK ].
121 / 162
6 Export Management
Open the file from current location, to visualize the file. The file opens in the browser. 5. Click on [ End ] to complete the operation. The export of RMS Templates can also be done via Configuration -> Manage RMS Template menu. Refer to Manage RMS Template (Section 4.6).
6.1.8 Export THL Template Dictionary

To export a Thematic Layer Template dictionary to an output .xml file: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Export -> THL Template Dictionary. The "THL Template Dictionary Export" window appears. It displays the list of dictionaries available for export, along with the radio buttons for unique selection. 3. Select the file to export, then click on [ OK ]. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the export. 4. The "NPO Export Management - THL Template Dictionary" window appears, showing the list of existing THL Template Dictionaries.
122 / 162
6 Export Management
5. Select the radio button corresponding to the THL Template Dictionary you want to export, then click on [ OK ]. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the export. When the export is done, another window opens with the result of the export. The name of the exported file as well as its exported status (OK or NOK) appear.
6. In the download dialog box, you can: Select to open the file from the current location The .xml file opens. Save the file to disk. Browse for the appropriate location to save the file. The file is saved. 7. Click on [ End ] to complete the operation.
123 / 162
6 Export Management
6.2 Export Management Using Command Line

6.2.1 Export QoS Dictionary
To export a QoS dictionary, as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/offlinetool/bin ./export.sh <option> <dictionary_name> [<dictionary_output_path>] Where: <option> can be: -C, for Counter Dictionary -SI, for System Indicator Dictionary -ST, for System Threshold Dictionary -CI, for Customer Indicator Dictionary -CT, for Customer Threshold Dictionary <dictionary_name> can be either: CUSTOMER_INDICATOR_DICTIONARY, for customer indicator dictionary, or CUSTOMER_THRESHOLD_DICTIONARY, for customer threshold dictionary For more information, refer to Export QoS Dictionary (Section 6.1.1) Using Graphical User Interface. <dictionary_output_path> is an optional parameter, which indicates the XML file name where the exported data is put.
6.2.2 Export Reports Dictionary

cd /alcatel/muse/MUSE_MAAT/reports/bin/ ./export.sh <fileName> <file_output_path> Where: <fileName> is the name of the customer report dictionary . Example: SYSTEM_REPORT_DICTIONARY, for system QoS reports CUSTOMER_REPORT_DICTIONARY, for customer QoS reports For more information, refer to Export Reports Dictionary (Section 6.1.2) Using Graphical User Interface. <file_output_path> indicates the XML file name where the exported data is put. Example: ./export.sh Rep-2G-Ev Rep_2G_Ev.xml
124 / 162
6 Export Management
6.2.3 Export Diagnosis Dictionary

To export a Diagnosis Dictionary, as root, run the following commands from the server: cd /alcatel/muse/MUSE_MAAT/diagnosis/bin ./exportDiagDict.sh <fileName> <file_output_path> Where: <fileName> is the absolute path and name of the Diagnosis xml file <file_output_path> indicates the absolute path where the exported data is put. The indicated diagnosis dictionary is exported to the specified location.
6.2.4 Export Parameter Reference Values

To export Reference Values, as root, run the following commands from the server: cd /alcatel/muse/MUSE_PARAM/rulesandrefs/bin/ ./ref_export.sh <file_output_path> Where <file_output_path> is the absolute path where the exported reference values excel file is put. Example: ./ref_export.sh /tmp/reference.xls The list of available reference value files in the data warehouse is displayed after the message: Select one of the following files. Select any of the displayed numbers and press [ Enter ]. The reference values file is exported to the specified location.
6.2.5 Export Parameter Rules

To export rules, as root, run the following commands from the server: cd /alcatel/muse/MUSE_PARAM/rulesandrefs/bin/ ./rule_export.sh <file_output_path> Where <file_output_path> is the absolute path where the exported rule excel file is put. Example: ./rule_export.sh /tmp/rule.xls The list of available reference value files in the data warehouse is displayed after the message: Select one of the following files. Select any of the displayed numbers and press [ Enter ]. The rule file is exported to the specified location.
125 / 162
6 Export Management
6.2.6 Export THL Template Dictionary

To export a THL Template dictionary, as root, run the following commands from the server: cd /alcatel/muse/MUSE_MAAT/cartography/bin ./exportTHLDict.sh <fileName> <file_output_path> Where: <fileName> is the Dictionary Name <file_output_path> indicates the absolute path where the exported data is put.
126 / 162
7 Delete Management
7 Delete Management
This section describes the dictionary deletion management.
127 / 162
7 Delete Management
7.1 Delete Management Using Graphical User Interface

Note:
It is not possible to delete a customer dictionary, if the indicators belonging to the dictionary are referred to either by a view / report template, or by another dictionary. The order of performing customer dictionaries deletion is: reports, indicators, counters, parameters. Do not delete the system dictionary.
7.1.1 Delete QoS Dictionary

To delete a customer QoS dictionary: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Delete -> QoS Dictionary. The "Delete QoS Dictionary" window appears.
Figure 10: Example of QoS Deletion Window 3. In the "Delete QoS Dictionary" window, select one or more file(s) to delete, then click on [ OK ]. 4. The progress bar displays the progress and eventual completion of the operation.
128 / 162
7 Delete Management
Wait for the end of the deletion. 5. The "NPO Import/Export Management - Delete QoS Dictionary" window appears, showing the deletion status (OK or NOK).
129 / 162
7 Delete Management
7.1.2 Delete Reports Dictionary

To delete a customer Reports dictionary: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Delete -> Reports Dictionary. The "Delete Reports Dictionary" window appears. 3. In the "Delete Reports Dictionary" window, select one or more file(s) to delete, then click on [ Delete ]. To select all customer reports, select the check box from the table header. 4. Click on [ OK ] at the confirmation window. 5. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the deletion. 6. The "NPO Import/Export Management - Delete Reports Dictionary" window appears, showing the deletion status (OK or NOK).
130 / 162
7 Delete Management
7.1.3 Delete Planned Data

To delete planned data: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Delete -> Planned Data. The "Delete Planned Data" window appears, with the following message:
Are All and are you sure you want to delete the planned data in MUSE. the planned data (planned network resource parameters interference matrix) will be deleted in MUSE.The maps not deleted..
3. Click on [ OK ]. 4. A confirmation message appears: Do you want to continue with

delete operation?
Click on [ OK ]. 5. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the deletion. 6. The status of the deletion appears.
131 / 162
7 Delete Management
7.1.4 Delete Diagnosis Dictionary

To delete diagnosis dictionaries from the database: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Delete -> Diagnosis Dictionary. The "Delete Diagnosis Dictionary" window appears. 3. Select one or more dictionaries to delete, then click on [ Delete ]. 4. A confirmation message appears:
Are you sure you want to delete the selected dictionary? The operation cannot be canceled once triggered.
Click on [ OK ]. 5. The progress bar displays the progress and eventual completion of the operation. Wait for the end of the deletion. 6. The status of the deletion appears (OK or NOK).
132 / 162
7 Delete Management
7.1.5 Delete Parameter Reference Values

To delete parameter reference values: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Delete -> Parameter Reference Values. The "Delete Parameter Reference Values" window appears. 3. Select one or more file(s) to delete, then click on [ Delete ]. 4. A confirmation message appears:
Are you sure you want to delete the selected files? The operation cannot be canceled once triggered.
133 / 162
7 Delete Management
7.1.6 Delete Parameter Rules

To delete parameter rules: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Delete -> Parameter Rules. The "Delete Parameter Rules" window appears. 3. Select one or more file(s) to delete, then click on [ Delete ]. 4. A confirmation message appears:
Are you sure you want to delete the selected files? The operation cannot be canceled once triggered.
134 / 162
7 Delete Management
7.1.7 Delete Cartography File

To delete existing cartography layers from database: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Delete -> Cartography File. The "Delete Cartography Layer " window appears. 3. Select one or more cartography files to delete, then click on [ Delete ]. 4. A confirmation message appears:
Are you sure you want to delete the selected cartography layer(s)?
135 / 162
7 Delete Management
7.1.8 Delete Customer Object Type

To delete a customer object type dictionary: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Delete -> Customer Object Types. The "Remove Customer Object Types" window appears. 3. In the window, select one or more file(s) to delete, then click on [ Delete ]. 4. A confirmation message appears:
Are you sure you want to delete the selected Customer Type(s)?
Click on [ OK ]. 5. The status of the deletion appears.
136 / 162
7 Delete Management
7.1.9 Delete Customer Acceptance List

The feature described in this section is not planned for W-CDMA. To delete a customer acceptance list and all the items associated with that CAL definition: 1. From the icon box, select MUSE Applications -> Optimization -> Import/Export Management. 2. The "NPO Import/Export Management" window opens. Select Delete -> Customer Acceptance List. The "Delete Customer Acceptance List" window appears. 3. In the window, select one or more file(s) to delete, then click on [ OK ]. To select all CALs, select the check box from the table header. 4. Click on [ OK ] for the confirmation message. 5. The status of the deletion appears.
137 / 162
7 Delete Management
7.2 Delete Management Using Command Line

The order of performing customer dictionaries deletion is: reports, indicators, counters, parameters. Do not delete the system dictionary.
7.2.1 Delete QoS Dictionary

Note:
It is not possible to delete a customer dictionary, if the indicators belonging to the dictionary are referred to either by a view / report template, or by another dictionary. To delete QoS customer dictionary, as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/offlinetool/bin ./deleteDB.sh <dictionary_name1> [<dictionary_name2> <dictionary_name3> ...] Where the <dictionary_name> is the absolute path and name of the dictionary mentioned as Header in the Dictionary.
7.2.2 Delete Report Dictionary

To delete a report dictionary, as root, run the following commands: cd /alcatel/muse/MUSE_MAAT/reports/bin ./delete.sh <absolute path and name of report dctionary> The indicated report dictionary is deleted.
7.2.3 Delete All Planned Data

To delete all planned data files from the database, as root, run the following commands from the server: cd /alcatel/muse/MUSE_PARAM/plannedData/loader/bin ./deletePlannedData.sh All planned data is deleted.
7.2.4 Delete Diagnosis Dictionary

To delete a Diagnosis Dictionary, as root, run the following commands from the server: cd /alcatel/muse/MUSE_MAAT/diagnosis/bin ./deleteDiagDict.sh <absolute path and name of diagnosis dictionary> The indicated diagnosis dictionary is deleted.
7.2.5 Delete Parameter Reference Values

The feature described in this section is not yet available for W-CDMA. To delete Reference Values, as root, run the following commands from the server: cd /alcatel/muse/MUSE_PARAM/rulesandrefs/bin/
138 / 162
7 Delete Management
./ref_delete.sh <absolute path and name of diagnosis dictionary> The list of available reference value files in the data warehouse is displayed after the Select one of the following files message. Select any of the displayed numbers and press [ Enter ]. The reference values corresponding to the selected file are purged from data warehouse.
7.2.6 Delete Parameter Rules

The feature described in this section is not yet available for W-CDMA. To delete rules, as root, run the following commands from the server: cd /alcatel/muse/MUSE_PARAM/rulesandrefs/bin/ ./rule_delete.sh <fileName> The list of available rules files in the data warehouse is displayed after the Select one of the following files message. Select any of the displayed numbers and press [ Enter ]. The rules corresponding to the selected file are purged from data warehouse.
7.2.7 Delete Customer Objects Types

To delete customer objects types, as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/topology/bin ./deleteCOTypes.sh <absolute path and name of CO type> Example: ./deleteCOTypes.sh /alcatel/muse/MUSE_QOS/topology/files/CustomerTypesDel.txt
7.2.8 Delete Customer Acceptance List

The feature described in this section is not planned for W-CDMA. To delete a Customer Acceptance List (CAL), as root, run the following commands from the server: cd /alcatel/muse/MUSE_QOS/Laser/CAL/bin ./run_deleteCAL.sh <mnemonic> <CAL Date> <CAL Version> <CAL Description> Where <mnemonic> is the absolute path and name of the CAL files to be deleted <CAL Date> must be of the format dd.mm.yyyy <CAL Version> is the version of the CAL files to be deleted <CAL Description> is the description of the CAL files to be deleted.
Note:
One Customer Acceptance List entry can be deleted at a time.
139 / 162
7 Delete Management
140 / 162
8 NPO Maintenance Tasks

This section describes NPO day to day maintenance tasks.
141 / 162
8.1 Consolidation Administration

Use the consolidation follow-up to display the status of the consolidation activity (complete or ongoing) and if needed, to manually start the recovery consolidation. The number of days managed by NPO is configurable. The default value is 5 days and the maximum allowed value is 7 days. For W-CDMA, it is recommended 3 days for recovery.
8.1.1 On-Demand Consolidation of Unavailability

Apart from the consolidations performed periodically by the system, the administrator can trigger manual consolidation for unavailability (UA) indicators at any desired time. This action is only available for the last 30 days. If the manual consolidation is interrupted due to the transfer of data from normalized to daily tables, it cannot be resumed. For that specific day, no consolidated data is available. To trigger manual consolidation for unavailability (UA) indicators: 1. In the NPO Administration window, select Administration -> Consolidation UA On-Demand. A window displays the list of dates for which recovered data exists.
2. Select the appropriate date, then click on [ Start ].
142 / 162
The progress bar displays the progress and eventual completion of the operation. Wait for the end of the UA On-Demand consolidation for the required date. 3. When it is done, a new window opens, informing the user that the consolidation of the required date was successfully completed. This window also provides a complete list of the operations that took place during the consolidation process.
4. You can only select one day at a time. If you want to perform data consolidation for several days, click on [ Consolidation ], then repeat steps 2 to 4 for each required day. Otherwise, click on [ End ] to return to the NPO Data Management main view.
8.1.2 Launch Consolidation Follow-Up

To launch consolidation follow-up: 1. In the NPO Administration window, select Administration -> Consolidation Follow-Up. A window displays the consolidation activity status. Each row displays the status of the consolidation for a day (five recoverable days appear by default).The columns contain the following information: Date of the consolidation Status: OK when the consolidation was successful, Not performed, Failed, or Ongoing Last Performed Step: RR/HR Transfer, Normalization, etc. This information appears only if the Status of that consolidation is Failed or Ongoing. Recovered data: Yes or No
143 / 162
Yes means that since the consolidation, new data is loaded (is present in RR tables) and so a recovery consolidation can be launched in order to take it into account. No means that no data has been loaded since the consolidation. An action hyperlink: Recover/Consolidate. If the consolidation failed or has not been performed, you can re-launch it manually using the [ Consolidate ] action hyperlink. If a recovery is proposed, it means some PM files had been loaded after the consolidation was performed. Launch the [ Recover ] action. There is no action hyperlink if the status is OK or NotPerformed and the Recovered Data is No, or if there is at least one Ongoing consolidation for another displayed day.
2. Click on [ Recover/Consolidate ] hyperlink. 3. Click on [ OK ] at the confirmation question: Are you sure to perform
this action?
The progress bar displays the progress and eventual completion of the consolidation operation for the required date. Wait for the end of the operations. 4. The next window displays the successful completion of the consolidation, along with the list of operations that took place during the consolidation process. Click on [ End ] to return to the NPO Data Management main view.
144 / 162
145 / 162
8.2 Manage Job Results

There is a job each time a report is scheduled (refer to NPO User Guide, sectionSchedule Reports). In order to Manage Jobs there are operations which can be performed from Administration menu, from the Analysis Desktop, or from both (see the following table). ADMIN Create Job View job result Delete job result * * Analysis Desktop * * * Note: Automatically done after the job is viewed. Delete job * -
8.2.1 Download Job Results

Download job results: 1. In the NPO Administration window, select Administration -> Manage Job Result. The Manage Jobs Result window opens. You can sort by name all the columns of the table by clicking their column headers. A little arrow marks the ascending or descending order. The Administrator can filter the results to see only the jobs results belonging to a given user. To do so, select a user from the Owner field and click on [ List ]. 2. Click on [ Download ] to open / save job results. 3. In the File Download window, click on [ Open ] or [ Save ], as appropriate. 4. In the Manage Job Results, click on [ Cancel ].
8.2.2 Delete Job Results

Delete job results: 1. In the NPO Administration window, select Administration -> Manage Job Result. The Manage Jobs Result window opens. The Administrator can filter the results to see only the jobs results belonging to a given user. To do so, select a user from the Owner field and click on [ List ]. 2. Select one or more job results and click on [ Delete ]. Click on [ OK ] in the a confirmation dialog box. A window with the status of the job result deletion appears. 3. Click on [ End ].
146 / 162
8.3 Manage Scheduled Jobs

1. In the NPO Administration window, select Administration -> Manage Scheduled Jobs. The Manage Jobs window opens. You can sort by name all the columns of the table by clicking their column headers. A little arrow marks the ascending or descending order. The Administrator can filter the results to see only the jobs belonging to a given user. To do so, select a user from the Owner field and click on [ List ]. 2. To delete scheduled job(s), select one or more jobs and click on [ Delete ]. Click on [ OK ] in the a confirmation dialog box. A window with the status (OK / NOK) of each job deletion appears. 3. Click on [ End ].
147 / 162
8.4 Import Follow-Up

To view the status of PM import activity: 1. In the NPO Administration window, select Administration -> Import Follow-Up. The Import Follow-up window opens. 2. For the Domain Type, select from the available drop-down list the appropriate domain value among: QOS, LASER, PARAMETER, or PLANNED DATA. 3. In the case of QoS domain, the Display Type box becomes available. Select the needed value among Per Root Loading Object, and Per Data Source. 4. If the display type is Per Data Source, select from the Datasource field the datasource for the OMC-R you want to visualize. 5. In the File Type filed, select the type of file which you want to visualize. 6. Click on [ List ]. A report appears showing the correct files relative to the selected root loading object / datasource, imported in the last 6 days plus the current day related to each network object for the PM follow up. In case of Laser, the report displays information for the last 30 days. The entries are shown in one of the following colors: White, when all imported files are successfully loaded Orange, when some of the imported files are failed to load, so are missing (the number of imported files is lower than the theoretical value which is declared by the plug ) Red, no import has been done on a particular day. The X / Y numbers show the Loaded / Failed Count. You can sort by date all the columns of the table by clicking their column headers. A little arrow marks the ascending descending order. or
148 / 162
7. To display information about a specific import, click on its entry. A report with the file names, date when each file was imported, as well as the status of the import appears. You can sort by name/date all the columns of the table by clicking their column headers. A little arrow marks the ascending or descending order. Click on [ End ] to return to the previous page.
149 / 162
8. Click on [ End ] to return to the NPO Data Management main view.
8.5 Load Radio Parameters

The new radio parameter data files must be located in the exchange directory of a declared NPO data source. The radio parameters are automatically loaded once per day. This operation could be forced at one moment during the day, by using and run the following command from command prompt window: /alcatel/muse/MUSE_PARAM/loader/bin/run_gl.sh
150 / 162
8.6 Mark Inactive Network Objects

This module allows the operator to mark as inactive the network objects. Only root loading objects and objects that are not RLO and are below the Geran/Utran/Wran in the topology model (not attached to a RLO) can be marked as inactive. All the objects that the selected network objects manage will also automatically be marked. 1. In the NPO Administration window, select Administration -> Mark Inactive Network Objects. The NPO Data Management - Mark Inactive Network Objects window opens. 2. Select the checkboxes corresponding to the objects you want to classify as inactive.You can select objects: Individually, by using the checkboxes adjacent to the network object names, or All at once, by using the checkbox in the title row. Note that all the objects that the selected network objects manage are also automatically be marked.
3. Click on [ Mark inactive ].
151 / 162
The progress bar displays the progress and eventual completion of the operation. Wait for the end of the operation. 4. Another window opens displaying the list of marked network objects and their properties (Name, OEXID), as well as the operation status (OK or NOK).
152 / 162
8.7 Metadata Inventory

The Metadata Inventory helps the administrator to view which versions of dictionaries are installed on the system for all the MUSE domains. 1. In the NPO Administration window, select Administration -> Metadata Inventory. 2. The NPO Data Management - Metadata Inventory window opens, displaying the list of domain, name, version, author, description, type, date, technology, release, system, import mode. You can sort by name all the columns of the table by clicking their column headers. A little arrow marks the ascending or descending order.
153 / 162
8.8 Customer Topology Objects Management

8.8.1 Presentation
NPO allows the declaration of customer specific topology equipments and the import of customer topology attributes. This customized topology can be one of the inputs of the data consolidation, as the other topology objects. The following operations can be performed in order to manage the customer objects values: Create the customer objects types (refer to Create Customer Topology Object Types (Section 8.8.2)) Load the customer objects and data in the data warehouse (refer to Load Customer Topology Data (Section 8.8.3)) Update the customer object types and data (refer to Create Customer Topology Object Types (Section 8.8.2)) Delete the customer object types (refer to Delete Customer Topology Objects (Section 8.8.4)). After a new customer topology object(s) types were created these new objects can be found in Analysis Desktop, Topology Classification (refer to the NPO User Guide, to Open Topology Classification). The operator can use these new objects to create new Topology Classification (refer to the NPO User Guide, to Create Topology Classification).
8.8.2 Create Customer Topology Object Types

The customer topology object types contain the fields described in the following tables.
Note:
Mandatory means that the value can not be empty. When the line defines a network object:
154 / 162
Evolium provides a sample file. This sample file contains the customer object MSC and associated relations. The sample file can be found at the following location: /alcatel/muse/MUSE_QOS/topology/files/CustomerTypes.txt
8.8.3 Load Customer Topology Data

The following prerequisites must be met to load customer topology objects: The operator must define a file with customer objects and customer relations (including type and external identifiers for each object and relation). This must be located in /alcatel/muse/MUSE_QOS/topology/files/ The file type can be comma-separated or semicolon-separated. When an object has more than one external identifier, one of these identifiers is tagged as being the one used in NPO. The customer object and relations types must already exist in the data warehouse. By default, there is a sample file at /alcatel/muse/MUSE_QOS/topology/files/CustomerData.txt, using the new created MSC customer object. The corresponding data file conteins for each line the following columns shown in the tables below..
Note:
Mandatory means that the value can not be empty. When the line defines a network object:
155 / 162
For example, to load data for the new created customer object: MSC, perform the following steps: Rename /alcatel/muse/MUSE_QOS/topology/files/CustomerData.txt such as NewCustomerData.txt and modify the file as follows: MSC;001;MSC-Paris-1;GERAN;1;Site_X_Coord;W-10-59-31;Site_Y_Coord;N-50-12-32 MSC;002;MSC-Paris-2;GERAN;1;Site_X_Coord;W-10-01-12;Site_Y_Coord;N-50-16-41 MSC_BSC;001/BSS_137;BSCMSCLink-Paris-1;MSC;001;BSC;BSS_137; MSC_BSC;002/BSS_140;BSCMSCLink-Paris-2;MSC;002;BSC;BSS_140; where BSS_134 and BSS_137 are the existing external identifiers for each object. Load the NewCustomerdata.txt file using the Graphical User Interface (refer to Import Customer Topology Objects (Section 5.1.15)) or using the command line (refer to Load Customer Topology Objects (Section 5.2.14)). The NPO checks the operator access rights and that the maximum number of allowed topology objects is not attained. If the number of cells is greater than 90% of the allowed limit, license MUSE_MAX_CELLS creates a warning log. If an object or relation with the same external identifier already exists, it is updated. Otherwise it is created and stored in the data warehouse. The Analysis Desktop application is updated. UIDs are provided to new objects. A generic notification is sent to notify users that the topology is updated.
156 / 162
8.8.4 Delete Customer Topology Objects

Customer Topology Objects can be deleted using: Graphical User Interface (refer to Delete Customer Object Type (Section 7.1.8)) Command line (refer to:Delete Customer Objects Types (Section 7.2.7))
8.9 Planned Data Management

8.9.1 Presentation
The Alcatel A9155 RNP (Radio Network Planning Tool ) offers radio network planning services for GSM and W-CDMA. It supports planning tasks as: license bid planning, initial design, network design and rollout, optimization and capacity planning. Alcatel A9155 RNP includes a number of export functions that allow the user to export radio planning data. The NPO planned data sub-system is, in particular, in charge of importing the planned data provided by the RNP application into the NPO data warehouse. It imports planned data for all the supported standards. Planned data is composed of: Planned parameter files Interference matrix file CCA (Cell Coverage Area) / Best Server maps Background maps. The following operations can be performed in order to manage planned data via NPO: Import planned data in non delta mode and delta mode Schedule planned data import Automatic Import of planned data (non delta) Delete planned data.
Note:
Reference is the W-CDMA Network Planning.
157 / 162
8.9.2 Manual Import Planned Data

The feature described in this section is not yet available for W-CDMA. As prerequisites of the manual planned data import, you must have a set of files representing the planned data from the RNP project. This set of files depends on the standard (and release), and can include planned network resource parameters, interference matrix and planned maps. For network resource parameters, one data file contains planned parameters for only one type of object (e.g. CELL2G).
Note:
Only NPO administrators are allowed to trigger the import of planned data. The procedure to manually import the planned data files from the provided zip files is described in the following sections: Import Planned Data (Section 5.1.4), using graphical user interface Import Planned Data (Section 5.2.5), using command line.
8.9.3 Schedule Planned Data Import

The feature described in this section is not yet available for W-CDMA. As prerequisites of the scheduled planned data import, you must have a set of files representing the planned network resource parameters from the RNP project available at a given URL.
Note:
Scheduling of RNP is available only for NON_DELTA_MODE Only NPO administrators are allowed to schedule the import of planned data. When Data source is declared for RNP (generic or Non generic format files) then one job is created and scheduled to run once in a day. The following parameters must be set for the scheduling of planned data: RNP_GL_SCHEDULE_HOUR, the hour at which the planned data Loader is scheduled; the default value is 01 RNP_GL_SCHEDULE_MINUTE, the minute at which the planned data Loader is scheduled; the default value is 00 RNP_GL_SCHEDULE_SECOND, the second at which the planned data Loader is scheduled; the default value is 00 RNP_GL_START_DATE, start date of job RNP_GL_END_DATE, end date of job.
8.9.4 Automatic Import of Planned Data (Non Delta)

The feature described in this section is not yet available for W-CDMA. The automatic import of planned data is performed by the NPO scheduler.
158 / 162
The import must be scheduled in non delta mode, and all the planned data files from the RNP project to import must be available at the URL and for the format (technology standard and release) specified in the RNP data source. At the scheduled time, the system retrieves the planned data files to import and imports them automatically.
159 / 162
8.9.5 Delete Planned Data

The feature described in this section is not yet available for W-CDMA. As prerequisites of the planned data deletion, a planned data import must not be currently running. For information about he procedure to delete the planned data files from the database: Delete Planned Data (Section 7.1.3), using graphical user interface Delete All Planned Data (Section 7.2.3), using command line.
160 / 162
9 Update Identification Mode from CI to LAC/CI

This section describes how to check and how to change the identification mode. This section is applicable only for GSM.
161 / 162
9.1 Check Current Identification Mode

The current identification mode is set by the CI_MODE parameter value from the following files:
/install/data/OMC_INSTALL_<active_instance_number> /alcatel/muse/MUSE_COMMON/config/common.properties /install/data/MUSE_INSTALL_<active_instance_number>
Note:
The value for the CI_MODE parameter must be the same in all the three files. If CI_MODE parameter value is: true, then the current identification mode is CI false, then the current identification mode is LAC/CI.
9.2 Change Identification Mode from CI to LAC/CI

The identification modes supported by NPO are MCC/MNC/CI and MCC/MNC/LAC/CI. It is possible to swap from the first identification to the later identification (but not the reverse!). The identification swap affects all the external identifications that may contain the LAC id (e.g. TRX, TSL, etc). The LAC id is inserted in all such external ids. To change the identification mode: 1. Stop NPO: Network Performance Optimization (NPO). 2. For GSM only, check that in
/alcatel/muse/technologies/GSM/gsmconfig.cfg file, the user label
value is different from 3. If it is equal to 3 (corresponding to CI mode), then change it to 0, 1, or 2 and save the file. 3. As root user, perform the following: cd /alcatel/muse/MUSE_MIGRATION/bin/ ./changeIdentificationMode 4. The script checks that the current identification mode is MCC/MNC/CI.If the current identification mode is: LAC/CI, the following message appears and you are not allowed to perform the procedure.
>> ERROR: This machine is currently configured for full identification, no change mode can be performed
CI, the following message appears:

WARNING: No topology update service may run during this operation. Make sure NPO is stopped. Continue? (y/n) >>
Type y. 5. The procedure starts and the displayed messages inform you of the progress of the operation. 6. When the swap is finished, Start NPO: Network Performance Optimization (NPO)
162 / 162

NPO Administration Guide

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

NPO Administration Guide

Hochgeladen von

Copyright:

Verfügbare Formate

Alcatel-Lucent

NPO Administration Guide

NPO Document Administration Guide Release B10, M2, UA5, UA6

3BK 21215 AAAA PCZZA Ed.25

BLANK PAGE BREAK

Status Short title

RELEASED Administration Guide

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

1.1 NPO Automatic Actions

3BK 21215 AAAA PCZZA Ed.25

1.1.2 Scheduled Reports Computation

3BK 21215 AAAA PCZZA Ed.25

1.2.1 System Dictionaries

1.2.2 Customer Dictionaries

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

1.3 Object Deletion

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

2.1 Start NPO Administration Data Management

3BK 21215 AAAA PCZZA Ed.25

Figure 2: "NPO Data Management" Window

3BK 21215 AAAA PCZZA Ed.25

2.2 Start NPO Import / Export Management

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

3BK 21215 AAAA PCZZA Ed.25

4 NPO Configuration Tasks

4 NPO Configuration Tasks

3BK 21215 AAAA PCZZA Ed.25

4 NPO Configuration Tasks

4.1 System Scheduling

3BK 21215 AAAA PCZZA Ed.25

4 NPO Configuration Tasks

3BK 21215 AAAA PCZZA Ed.25

4 NPO Configuration Tasks

4.2 Configure Storage Duration

4.2.1 Configure Indicators Storage Duration

3BK 21215 AAAA PCZZA Ed.25

4 NPO Configuration Tasks

4.2.2 Configure Parameter Storage Duration

4.2.3 Configure Laser Data Storage Duration

3BK 21215 AAAA PCZZA Ed.25

4 NPO Configuration Tasks

3BK 21215 AAAA PCZZA Ed.25

4 NPO Configuration Tasks

4.3 Storage Monitoring

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