9153 OMC-R Getting Started

Alcatel-Lucent GSM

9153 OMC-R Getting Started

OMC Document

Sub-System Description

Release B10

3BK 21202 AAAA PCZZA Ed.07

Status RELEASED

Short title 9153 OMC-R Getting Started

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

BLANK PAGE BREAK

2 / 116 3BK 21202 AAAA PCZZA Ed.07

Contents

ContentsPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.1 What is the Alcatel-Lucent 9153 OMC-R? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.1.1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.1.2 Scalability and Flexibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.2 9153 OMC-R Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.1 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.2 Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.3 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

1.3 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.3.1 Network Element Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.3.2 Physical Borders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.3.3 9153 OMC-R Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.3.4 Dimensioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.3.5 Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

1.4 Functional Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.4.1 Software Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.4.2 Hardware Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.4.3 Performance and Trace Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.4.4 Logical Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231.4.5 Network Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251.4.6 Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

1.5 Centralized Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.5.1 Multiple HMI Server Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.5.2 BSS Q3 Mediation Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

1.6 Performance Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281.7 Profiles and Desktop Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

1.7.1 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281.7.2 Desktop Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2 Getting Started with the 9153 OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.1.1 Start and Stop the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.1.2 Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.1.3 Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.1.4 Desktop Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.1.5 9153 OMC-R Icon Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2.2 Types of Application Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352.2.1 Graphical Application Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352.2.2 HTTP Application Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

2.3 Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.3.1 Access to Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.3.2 Navigating Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

2.4 Electronic Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.4.1 Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.4.2 Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402.4.3 Searching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3 9153 OMC-R Graphical Windows Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.1 RNUSM: SC and PRC Radio Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.1.1 RNUSM: SC Radio Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453.1.2 RNUSM: SC Radio Browser Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.1.3 RNUSM: PRC Radio Browser Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.2 BSSUSM: Main View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483.2.1 The [ BSSUSM ] Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3BK 21202 AAAA PCZZA Ed.07 3 / 116

Contents

3.2.2 The [ RNUSM ] Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483.2.3 The [ DCN ] Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493.2.4 Abis View Window Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503.2.5 Find Facility in Abis view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.3 MFSUSM Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523.3.1 The [ MFSUSM ] Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523.3.2 The [ RNUSM ] Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533.3.3 The [ DCN ] Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533.3.4 MFSUSM Window Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543.3.5 MFSUSM in Limited Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553.3.6 Restore the MFSUSM to Normal Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

3.4 MRTG Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563.4.1 MRTG: Main View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563.4.2 9130 BSC Evolution MRTG Index Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573.4.3 MFS MRTG Index Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593.4.4 Detailed Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

3.5 Command Mode Session Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603.6 Alarms Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

3.6.1 Alarm Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623.6.2 AS Current USM: Counter Summary Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633.6.3 AS Current USM: Counter Summary Window Functions . . . . . . . . . . . . . . . . . . . 643.6.4 AS Historical USM: Counter Summary Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.6.5 AS Historical USM: Counter Summary Window Functions . . . . . . . . . . . . . . . . . . 67

3.7 DCN: Management Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.8 SECUSM Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

3.8.1 SECUSM Main Window Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723.8.2 SECUSM GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733.8.3 SECUSM Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

3.9 DSMUSM Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.9.1 DSMUSM Window Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.9.2 DSMUSM Main Window Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

3.10 MFS Backup Manager Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773.11 OBSAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

3.11.1 OBSAL interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.11.2 OBSAL Log and Audit Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

3.12 NPO Analysis Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.12.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.12.2 NPO Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.12.3 Start NPO Client Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.12.4 NPO Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

3.13 NPO Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.14 NPO Import / Export Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.15 NPO NUART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893.16 RIDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903.17 NPO Diagnosis Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913.18 DLS Periodic Check Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923.19 Reduced USM Views on 280R STD HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

4 9153 OMC-R HTTP Windows Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934.1 ACO Management Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

4.1.1 ACO Management Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944.1.2 Filter and Service Management Window Functions . . . . . . . . . . . . . . . . . . . . . . . . 95

4.2 9153 OMC-R Administration Facilities Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964.3 ENSUSM Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974.4 Log Management Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

4.4.1 Log Viewer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004.4.2 User Log Viewer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034.4.3 Log Merge on Demand Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

4 / 116 3BK 21202 AAAA PCZZA Ed.07

Contents

4.4.4 Log Merge on Demand Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1064.4.5 OMC-R Connection to Workstation Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

4.5 Trace Viewer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084.6 9153 OMC-R UFM Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094.7 9153 OMC-R User Facilities Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

5 Routine Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135.1 Change the Default Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145.2 Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

5.2.1 Printing from Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155.2.2 Print Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

3BK 21202 AAAA PCZZA Ed.07 5 / 116

Figures

FiguresFigure 1: 9153 OMC-R External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 2: OMC-R Position in TMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 3: Alcatel BSS Network Management Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 4: Single Master OMC-R Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Figure 5: Logical Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 6: Provisioning Radio Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Figure 7: Multiple HMI Server Access to OMC-R Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 8: 9153 OMC-R Control Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Figure 9: 9153 OMC-R Iconbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Figure 10: Example Graphical Application Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Figure 11: 9153 OMC-R Online Help Window Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Figure 12: Electronic Documentation Home Page Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 13: Example Electronic Documentation Category Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 14: RNUSM: SC Radio Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Figure 15: RNUSM: PRC Radio Browser Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Figure 16: BSSUSM: Controller Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Figure 17: BSSUSM: Main View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Figure 18: BSSUSM: Abis Topology View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Figure 19: MFSUSM: Controller Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Figure 20: MFSUSM Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Figure 21: "9153-MRTG: Main View" Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Figure 22: 9153 OMC-R MRTG MFS View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 23: Command Mode Session Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Figure 24: AS Current USM: Counter Summary Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Figure 25: AS Historical USM: Counter Summary Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Figure 26: DCN: Management Main Window - BSS View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Figure 27: DCN: Management Main Window - MFS View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Figure 28: DCN: Management Main Window - HOST View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Figure 29: DSMUSM Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Figure 30: DSMUSM Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Figure 31: MFS Backup Manager Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Figure 32: OBSAL Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Figure 33: NPO Iconbox Confirm Working Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Figure 34: NPO Analysis Desktop View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Figure 35: NPO Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Figure 36: NPO Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Figure 37: NPO Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Figure 38: NPO Import / Export Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Figure 39: NPO Import Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

6 / 116 3BK 21202 AAAA PCZZA Ed.07

Figures

Figure 40: NPO Import Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Figure 41: NPO Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Figure 42: NPO Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Figure 43: NPO NUART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Figure 44: NPO RIDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Figure 45: NPOe Iconbox Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Figure 46: Diagnosis Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Figure 47: Password Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Figure 48: ACO Management Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Figure 49: 9153 OMC-R Administration Facilities Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Figure 50: ENSUSM Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Figure 51: Log Viewer (Full Log) Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Figure 52: Full Log Report Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Figure 53: Log Viewer (Own Log) Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Figure 54: Own Log Report Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Figure 55: 9153 OMC-R UFM Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Figure 56: 9153 OMC-R User Facilities Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

3BK 21202 AAAA PCZZA Ed.07 7 / 116

Tables

TablesTable 1: 9153 OMC-R Hardware Components Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Table 2: 9153 OMC-R Capacity per BSS Category Description - V880 Hardware . . . . . . . . . . . . . . . . . . . . . . 19Table 3: 9153 OMC-R Capacity per BSS Category Description - V490 Hardware and M4000 Hardware . 19Table 4: Alignment Parameter Values Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Table 5: Graphical Application Window Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Table 6: Graphical Applications and their Associated Windows Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Table 7: HTTP Applications and their Associated Windows Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Table 8: DSMUSM Main Window Functions Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Table 9: NPO NUART Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Table 10: Log Report Parameters Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Table 11: Log Report Parameters Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

8 / 116 3BK 21202 AAAA PCZZA Ed.07

Preface

PrefacePurpose This document explains the basic concepts of the Alcatel-Lucent Radio

Solutions 9153 OMC-R and introduces some of the OMC-R specific terms. Italso explains the applications and user interfaces of the 9153 OMC-R.

Whats New In Edition 07Description improvement in all the document.

In Edition 06Description improvement in:

Dimensioning (Section 1.3.4)Reduced USM Views on 280R STD HMI (Section 3.19).

In Edition 05The section 9153 OMC-R User Facilities Window was updated.The 9153 OMC-R Iconbox was updated in chapters NPO Import / ExportManagement (Section 3.14) and NPO Data Management (Section 3.13)The section NPO NUART (Section 3.15) has been added

In Edition 04Editorial updates.

In Edition 03Update with the new equipment naming.NPO Diagnosis Editor tool is now available on OMC platform.Overall document quality was improved following an editorial review.

In Edition 02Editorial improvement in Reduced USM Views on 280R STD HMI (Section3.19).

In Edition 01

3BK 21202 AAAA PCZZA Ed.07 9 / 116

Preface

First official release of document for B10.

Audience This document is intended for OMC-R operators and anyone interested in theconcepts and applications of the 9153 OMC-R.

Assumed Knowledge Operators must have a good working knowledge of UNIX and windows-basedenvironments.In addition, they must also be familiar with:

The basic architecture and functions of GSM networks

Network protocols and networking techniques

The Alcatel BSS

The BSS System Description and BSS System Introduction.

10 / 116 3BK 21202 AAAA PCZZA Ed.07

1 Introduction

1 Introduction

This section explains the basic concepts of the Alcatel-Lucent Radio SolutionsAlcatel 9153 OMC-R and introduces some of the OMC-R specific terms.

3BK 21202 AAAA PCZZA Ed.07 11 / 116

1 Introduction

1.1 What is the Alcatel-Lucent 9153 OMC-R?The 9153 OMC-R is the third generation Alcatel OMC-R. The OMC-R is used tooperate and maintain the BSS, with one OMC-R supporting a set of BSSs.The 9153 OMC-R manages the network elements and sub-network of theBSS sub-system:

The whole set of BSSs, that is, BSCs, BTSs, TCs, and transmission systems

The GPRS 9135 Multi-BSS Fast packet Server (9135 MFS).The 9153 OMC-R also provides a Q3 interface to the NMC for centralizedmanagement. The 9153 OMC-R is built on the generic TMN services of theAlcatel management platform, ALMAP, which allows it to be distributed onseveral servers on a LAN and to offer remote access.

1.1.1 InterfacesImport/export facilities are provided to external tools such as network planningand optimization tools (for example, Alcatels NPO). Refer to the followingfigure for further information.

Or Customer Applications

Impo

rt/expo

rtA 1353 RA

Q3

Network ManagementCenter GSM

HMI

CommandMode

Operator

BSC

OMC

R

Import/export

MFS

NetworkPlanning Tool

BSC BSC

Figure 1: 9153 OMC-R External Interfaces

12 / 116 3BK 21202 AAAA PCZZA Ed.07

1 Introduction

1.1.2 Scalability and FlexibilityThe 9153 OMC-R can manage a complete region of up to 6000 cells. Usingseveral servers, the 9153 OMC-R can share the supervision and displayprocesses for the best BSS network operability. The flexibility of the architectureallows the OMC-R topologies to fit all operator organizations and smooth theincrease in OMC-R capacity.

1.2 9153 OMC-R FunctionsOperation and maintenance functions used for BSS and GPRS managementare organized into some of the functional management domains specified byITU-T M.3010:

Configuration management

Performance management

Fault management.

1.2.1 Configuration ManagementThe main benefit of the configuration management feature is the reduced timeneeded to perform operations and reduced telecom outages. This is achievedby having fewer operator commands and providing smooth migration andequipment configuration.The main functions of configuration management include:

Radio configuration managementSupervised configuration viewProvisioning radio configurationExtensive logical configuration updateLogical parameters templatesUsage states on demandGPRS service handlingRadio configuration import/export.

Equipment managementHardware online extension-reductionHierarchical browser (network element, rack, shelf, board, transmission)Equipment configuration export.

1.2.2 Performance ManagementThe 9153 OMC-R provides measurements and statistics about various eventsand resource usage in the BSC. Indicators computed by the OMC-R enrichthe raw data retrieved from the field. The operator can display measurementsas graphs and activate alerters to send alarms when preset thresholds arecrossed.

3BK 21202 AAAA PCZZA Ed.07 13 / 116

1 Introduction

1.2.3 Fault ManagementThe AS alarm manager collects all network events in real time and presentsdefault or customized alarm lists dynamically, using colors to indicate levelsof urgency.Alarms can be managed on a large number of network elements in real time,with the radio and equipment view panels providing a clear status on radioresources and equipment. Alarm sub-lists can be customized using powerfulsort and filter services, enabling the operator to react quickly.The main functions of fault management include:

DetectionGraphic synthesis viewFault localizationAlarm countersAlarm severity assignment.

TrackingAlarm views with sort and filterAlarm reservationEvent/alarm logging.

ResolutionAlarm acknowledgmentFault correction.

Post analysisAlarm historyEvolution of events.

14 / 116 3BK 21202 AAAA PCZZA Ed.07

1 Introduction

1.3 System ArchitectureThe 9153 OMC-R supports the management functions used to operate one ormore BSSs. It takes the functional role of an element manager of the AlcatelBSS network elements. The following figure shows the position of the OMC-Rin the TMN hierarchical network management standard.

OMCR

BTS BSC MFS

Business Management

Service Management

Network Management

Element Management

Network Element

Figure 2: OMC-R Position in TMN

The 9153 OMC-R interfaces with:

The NMC, which manages both the BSS and NSS parts of the GSM PLMN.It supervises the OMC.

Radio network planning and optimizing software tools, such as Alcatels9159 NPO. These tools can be used to help define and optimize the radionetwork configuration.

Refer to the following figure for further information.

A9125 MFSNetwork Elements

A1353RA OMCRElement Manager

A900/1800/1900BSS

Network Elements

NMCNetwork Manager

A9159 NPO

Radio NetworkPlanning Tool

Configuration Data

Cell Design Data

Figure 3: Alcatel BSS Network Management Environment

3BK 21202 AAAA PCZZA Ed.07 15 / 116

1 Introduction

1.3.1 Network Element InterfaceEach network element is assigned to exactly one OMC-R at a time. However,re-assignment functions allow a network element to be "moved" from oneOMC-R to another, without interrupting the management service of othernetwork elements.To manage the BSS as a whole, the 9153 OMC-R is connected, via a CMISEinterface, to:

The BSC; the interface is based on the ISO 7 layer systems managementprotocol stack.

The MFS; the interface is based on the TCP/IP protocol.

1.3.2 Physical BordersThe 9153 OMC-R is not a dedicated hardware platform. Rather, it represents asoftware package containing a number of applications. Application services areimplemented using a set of distributed software components. This distributedarchitecture means that the borders of the 9153 OMC-R are purely functional.For an individual operator, the 9153 OMC-R is seen as a single system,distributed on several computing nodes across multiple locations.

16 / 116 3BK 21202 AAAA PCZZA Ed.07

1 Introduction

1.3.3 9153 OMC-R ComponentsThe architecture of the 9153 OMC-R allows a flexible distribution ofmanagement components across the different nodes of the network accordingto specific needs. For example, network dimensions and performancerequirements. This configuration flexibility means that the system can evolveand adapt to new dimensioning requirements, adding new machines wherenecessary.

1.3.3.1 HardwareThe main hardware configurations supported by the 9153 OMC-R are:

Single-server configuration with front-end workstations

Distributed configuration with three dedicated servers and front-endworkstations.

The following table shows the different hardware components:

Component Description

MasterServer

UNIX server. Hosts the system administration functions,alarm database, and surveillance module. Takes datafrom a set of network elements, stores the data in theBSS distributed database, and runs OMC-R managementapplications.

AgentServer

UNIX server. Present only in the distributed configuration.Hosts the additional management of other network elementgroups to increase OMC-R capacity.

HMI Server UNIX server. Enhances system performance by taking userinterface processing from the host server (master or agent).For remote user terminals, an HMI server is needed to ensureterminal performance due to potential weak transmissioncapability.

UserTerminal

Graphical workstations connected to the Master Host or HMI.

Table 1: 9153 OMC-R Hardware Components Description

1.3.3.2 SoftwareThe software architecture of the 9153 OMC-R is based on ALMAP, anobject-oriented open management platform that complies with all major TMNand system management standards. It provides a comprehensive family ofreusable generic components for developing network management productssuch as alarm surveillance, network visualization, or system management.Other software used by the 9153 OMC-R comprises:

Communication stacks

Graphical window management

OMC-R database

3BK 21202 AAAA PCZZA Ed.07 17 / 116

1 Introduction

BSS Performance Management.

1.3.4 DimensioningThere are seven generic 9153 OMC-R configurations, depending on thesize of the BSS network:

Small

Small/ NPO embedded

Standard

Large1

Large2

XLarge

XXLarge

There are three types of 9153 OMC-R Master and Agent hardware:

V880 HW composed of Sun Fire V880.

V490 HW composed of Sun Fire V490.

M4000 HW composed of SPARC Enterprise M4000.

The Small, Standard, Large1, and Large2 configurations have only one Masterserver and no Agent server.The XLarge configuration (for V880 HW, V490 HW and M4000 HW) has oneMaster server and one Agent servers.The XXLarge configuration (for V490 HW and M4000 HW) has one Masterand 2 Agents.The following tables are showing the BSS capacity for each configuration.

Note: The values proposed here are not contractual.

Configuration No. Servers BSS Equivalents Cells TRXs

Small 1 10 250 1250

Standard 1 20 500 2500

Large1 1 35 1200 6000

18 / 116 3BK 21202 AAAA PCZZA Ed.07

1 Introduction


Large2 1 45 1500 7500

XLarge 2 100 4000 20000

Table 2: 9153 OMC-R Capacity per BSS Category Description - V880 Hardware


Small 1 10 250 1250

Standard 1 20 500 2500

Large1 1 35 1200 6000

Large2 1 50 1800 9000

XLarge 2 100 4000 20000

XXLarge 3 120 6000 30000

Table 3: 9153 OMC-R Capacity per BSS Category Description - V490 Hardware and M4000 Hardware

Note: BSS equivalent is defined as:

1 BSC equivalent = 1 9120 BSC

2 BSC equivalent = 1 MFS

1 BSC equivalent = 1 BSC Evolution

2 BSC equivalent = 1 MFS Evolution.

3BK 21202 AAAA PCZZA Ed.07 19 / 116

1 Introduction

1.3.5 TopologiesThe architecture of the 9153 OMC-R offers several topologies that provide wideflexibility for network management.The following figure shows a typical topology comprising:

One master server and several terminals at the local OMC-R site

Three remote sites with HMI servers and several remote terminals.

BSS

OMCRMaster Server

R

WAN

PSDNHMI ServerR Remote site 1

Remote site 2Remote site 3

Local site

HMI ServerHMI Server

Figure 4: Single Master OMC-R Topology

The terminals are connected with a LAN (Ethernet 10 or 100 Mbits/s) eitherdirectly to the OMC-R host server (master) or, where used, to the HMI server.In the case of remote installations, a routing device (R) is needed to establishthe necessary WAN connection to the HMI clients or other OMC-R agents.

1.3.5.1 OMC-R - BSC InterconnectionThe 9153 OMC-R host can be connected to the BSC in several ways thatprovide a large degree of flexibility in choosing the OMC-R site:

Via PSDN

Collocated site

Dedicated links with X.25 concentrator

Via A interface - transcoder connection

Via A interface - MSC connection.

20 / 116 3BK 21202 AAAA PCZZA Ed.07

1 Introduction

1.3.5.2 OMC-R - 9135 MFS (GPRS) InterconnectionThis interface supports TCP/IP and FTP protocol using standard UNIXcommunications facilities. The 9135 MFS supports two Ethernet ports toconnect directly to the LMT and the 9153 OMC-R via a LAN.The 9153 OMC-R can also be connected remotely via an X.25 WAN used totransmit IP traffic between the 9153 OMC-R and the 9135 MFS. DedicatedIP routers perform any adapting of IP traffic to the WAN, regardless of theWAN technology used.

1.4 Functional ArchitectureThe functional architecture of the 9153 OMC-R comprises these functionaldomains:

Software configuration management

Hardware configuration management

Performance and trace management

Logical configuration management

Network supervision

Alarm management.

1.4.1 Software Configuration ManagementSoftware configuration management allows the operator to download new BSSsoftware to a BSC, and the BTSs attached to it, for upgrade or maintenance.

1.4.1.1 Software ProductionThe software to be downloaded includes some or all of the followingcomponents, depending on the purpose of the download:

BSC application software, complete database, steerfiles, or command files

BTS application software.

The new BSC database is produced from the uploaded database. Dependingon the extent of the modifications that are needed, the OMC-R either producesa new database, or a set of steerfiles or DLS command files that are used bythe BSC to upgrade its database locally.

1.4.1.2 Software DownloadThe system performs the software replacement differently, depending on whichcomponents are present.If a new BSC database is present, the system performs an offline databasereplacement. This implies a general telecom outage on the BSC.If only steerfiles or DLS command files are present, the system performs anonline database replacement. This implies a telecom outage limited to cellsimpacted by the change, unless it is associated with an application softwareupgrade.

3BK 21202 AAAA PCZZA Ed.07 21 / 116

1 Introduction

1.4.2 Hardware Configuration ManagementHardware configuration management allows the operator to:

Display the current hardware configuration

Update the configuration according to extension-reduction operations

Configure certain BSS parameters, such as Abis link characteristics andsome BTS characteristics.

Online extension-reduction allows the operator to perform hardwareconfiguration operations without having to generate and download a newsoftware package.For additional information about online and offline hardware extensionreduction, refer to the Operations and Maintenance Principles document.

1.4.3 Performance and Trace ManagementPerformance management provides measurements and statistics about trafficand resource usage in the BSS and the MFS. These measurements are basedon counters or parameters that are located in the BSC, as well as GPRScounters from the MFS. Trace management allows the operator to trace andgather information about a transaction.

1.4.3.1 Counter TypesRaw counters are located in the BSC and the MFS and give a value toan event or related events.For example, the number of attempted handovers to a particular cell. Rawcounters are grouped by counter type:

Standard counters

Detailed counters.

1.4.3.2 IndicatorsIndicators are traffic overview counters. They are calculated from the value ofstandard counters retrieved during a permanent measurement campaign.

1.4.3.3 AlertersAlerters are thresholds calculated from raw counters (or, for an OMC, fromindicators). When the threshold is reached, an alarm is generated.

1.4.3.4 Measurement Campaign TypesTwo types of measurement campaign are provided by the 9153 OMC-R:

Permanent measurement campaign (PMC)On-demand measurement campaign (ODMC).

A PMC is a set of recording jobs concerning all the BSSs supervised by the9153 OMC-R, applied on standard counter types only. An operator can defineup to two recording intervals within 24 hours on one PMC.An ODMC allows the diagnosis of a problem detected in the network by usingeither detailed counter types, or standard counter types not used in a PMC.

22 / 116 3BK 21202 AAAA PCZZA Ed.07

1 Introduction

1.4.3.5 Usage State on DemandA USD observation provides the operator with a view of the current resourceuse at BSC level.Two levels of USD are available:

An overall observation showing the evolution of the resource use in a BSS

A detailed observation showing a snapshot of the current resource usein a BSS.

1.4.3.6 TracesTrace continuation in the case of a handover is handled by the MSC. If thehandover is within the scope of the current OMC-R, the results are automaticallyforwarded to the OMC-R. If the handover is to another MSC, the results can beimported from the OMC-R related to the target MSC.

1.4.4 Logical Configuration ManagementLogical configuration management is a set of services that allow theconfiguration of telecom parameters attached to the GSM telecom resources.Refer to the following figure for further information.

Create, Configure, and Delete Cells

Create, Configure, andDelete HO/Reselection links

BSC BTS and BTS Sector(s)

Set BSS/BSC (GSM/GPRS)Telecom Parameters

Map/Unmap Cellsto BTS Sectors

MFS

Associate/Disassociatea BSC to MFS

Figure 5: Logical Configuration Management

1.4.4.1 Supervised ConfigurationLogical configuration management can be performed either on the supervisedconfiguration (SC) or on a provisioning radio configuration (PRC), dependingon the type of operation.The supervised configuration is the representation of the network in its presentstate (active domain). Modifications performed on this configuration are appliedto the equipment and are activated immediately.

3BK 21202 AAAA PCZZA Ed.07 23 / 116

1 Introduction

1.4.4.2 Provisioning Radio ConfigurationProvisioning radio configuration allows an operator to prepare changes on theradio configuration in advance, check them, then activate them as a whole. ThePRC can be resynchronized with the active domain before application. It ispossible to create several PRCs concurrently. Refer to the following figure forfurther information.

xPRC

Copy

yPRCImport/Export

Update Network

Copy

SC

Synchronization with Network

External OMC world

1

Synchronization with Network

BSC NBSC

1MFS PMFS

UpdateNetwork

Figure 6: Provisioning Radio Configuration

The alignment status parameter informs the operator of the synchronizationstatus between the current network configuration and the OMC-R. Thisparameter, which applies to a BSC or a cell, can have five values, as shown inthe following table.

This value ... Indicates that ...

In configuration A configuration operation is being performed. That is,a PRC is open but has not yet been activated.

Aligning up A logical audit is being performed but is not yetcomplete (only valid for BSC).

Aligning down A BSS update is being performed. The BSS is beingsynchronized with the OMC-R

24 / 116 3BK 21202 AAAA PCZZA Ed.07

1 Introduction

This value ... Indicates that ...

Aligned A BSS update has completed successfully. The BSS issynchronized with the OMC-R.

Misaligned A BSS update was unsuccessful. For example, thecommunication link with the BSC is not operational.

Table 4: Alignment Parameter Values Description

If a BSS is misaligned, the operator can force the current OMC-R configurationon the faulty BSS.

Note: During PRC activation, no other configuration operation, BSS upload, migrationor software replacement (except via steerfile) concerning the BSS/MFSinvolved in the activation can be triggered.

1.4.5 Network SupervisionSupervision operations apply to:

Boards: identifies a hardware replaceable unit performing a set of specificfunctions

Functions: identifies a function carried by one or several boards

Support resources: identifies a telecom logical object. The support resourceis itself supported by boards

Resource objects: identifies a resource used for serving call management.This resource uses support resources and boards to perform the service

O&M capabilities: identifies the capability of supervision of a set of supportresources and boards

Equipment: can be identified as a container for all previous categoriesof object (BSC, BTS, and so on).

3BK 21202 AAAA PCZZA Ed.07 25 / 116

1 Introduction

1.4.6 Alarm ManagementWhen the O&M controller of a subsystem in the BSS detects irregularconditions, an alarm report is forwarded to the OMC-R. This is displayedto the operator as an X.733 alarm.

1.4.6.1 Types of AlarmTwo types of alarms exist:

Alarms with a severity of warning, minor, major, or critical are generatedwhen a fault is detected

Alarms with the severity indeterminate correspond to BSS events. They areautomatically sent to the list of historical alarms.

1.4.6.2 AttributesPrimary attributes of an alarm are attributes that can be used for filtering.The primary attributes of an alarm are:

MOC (Managed Object Class) of object impacted by the alarmMOI (Managed Object Instance) of object impacted by the alarmEvent type

Event time

Probable cause

Perceived severity.

The operator can customize the alarm display using filtering and sorting criteriabased on these attributes.Sorting criteria can be based on any primary attributes, or other attributessuch as:

Friendly name

Specific problems

State change associated with the alarm (optional)Proposed repair actions

Additional text

Monitored attributes

State change definitions.

Current alarms are stored in the current alarm list until they are either purged,or cleared and acknowledged. They are then archived in the historical alarmlist. Both current and historical alarms are accessible through a similar userinterface.

26 / 116 3BK 21202 AAAA PCZZA Ed.07

1 Introduction

1.5 Centralized ManagementThe 9153 OMC-R provides the facility to supervise several OMC-Rs fromone central location:

A single HMI server can access several OMC-Rs

Open interface to any network management entity (NMC).

1.5.1 Multiple HMI Server AccessMultiple HMI server access allows a single operator to perform managementactions that are usually performed by several OMC-Rs. Connections to OMC-Rhosts are sequential. This feature can be installed on a dedicated HMI serverthat does not belong to a specific OMC-R. Refer to the following figure forfurther information.

OMCRHost 1

Operating Site 2

OMCRHost 2

Operating Site 3

MultipleHMIs

Central Operating Site

OMCRHost 3

X.25PSDNor WAN

Figure 7: Multiple HMI Server Access to OMC-R Hosts

1.5.2 BSS Q3 Mediation InterfaceA BSS Q3 mediation interface to an upper-level O&M system (for example, anNMC) can also be provided. This interface supports BSS supervision functionsneeded for a large or multi-vendor network.

3BK 21202 AAAA PCZZA Ed.07 27 / 116

1 Introduction

1.6 Performance AnalysisThe 9153 OMC-R provides an embedded component for QoS surveillance andalerts on the BSS network. This component is based on a Metrica databaseand allows the collection, processing, and online display of BSS observationcounters. The component warns the operator if the QoS thresholds are crossedby generating alarms that are handled in the same way as other BSS alarms.Network Performance Optimization application ( NPO) is embedded in anOMC-R or used as standalone (9159 NPO).The main advantage of the NPO is the single access point to all applicationsof the toolchain, instead of having to login independently on each of theapplications. Second advantage is the capacity of the NPO: up to 10500 cellscapacity. Third advantage: NPO is multi-standard by definition and can managesimultaneously GSM, UMTS and WiMAX networks provided by Alcatel-Lucent.

1.7 Profiles and Desktop CustomizationThe security management facility manages the rights of operators to objectsand functions in the 9153 OMC-R and is based on the ALMAP genericcomponent, SEC.

1.7.1 ProfilesTo help with managing access rights, a set of predefined user profiles aresupplied with the 9153 OMC-R. A profile allows operator access to a given listof object access domains and functional access domains.A profile can be assigned to one or more operators and, in turn, one or moreprofiles can be assigned to the same operator.For detailed information about profiles, refer to the 9153 OMC-R NetworkAdministration Handbook.

1.7.2 Desktop CustomizationEach operators desktop is defined by the profile or profiles assigned to them.The only functions that are visible on their desktop are those to which they haveaccess. When an operator logs in, the desktop is automatically customizedaccording to the assigned profile or profiles.

28 / 116 3BK 21202 AAAA PCZZA Ed.07

2 Getting Started with the 9153 OMC-R


This section explains the 9153 OMC-R applications and user interfaces.

3BK 21202 AAAA PCZZA Ed.07 29 / 116


2.1 Getting StartedThis section describes how you start and stop the system, and the applicationsthat are available to you.

2.1.1 Start and Stop the SystemOnly the Administrator can start or stop the OMC-R.The Administrator can perform the following functions:

Global start

Global stop

Workstation start

Workstation stop.

For additional information, refer to the 9153 OMC-R Network AdministrationHandbook.

2.1.2 LoginThe OMC-R Administrator provides you with your login name and access rights.Your access rights are specified in the profile or profiles that the Administratorassigns to you. These rights define the functions that you can perform and thenetwork elements that you can access.The first screen display that you see when you switch on your OMC-R terminaldepends upon your terminal set-up and your network configuration. Forexample, you might be able to access more than one OMC-R machine fromthe same OMC-R terminal. If so, you must either select the required OMC-Rmachine from a list or enter a command to connect to it.

2.1.2.1 How to Log InTo log in:1. In the Access field, enter your login name. The Login field is skipped and

the login to the OMC-R begins.2. After a short time a new window pops up and requests that you enter your

password. The password is not displayed on the screen as you type it.

Note: You have a limited amount of time to enter your password.Once the login is successful, the standard CDE desktop opens.

2.1.2.2 Starting a SessionThe Administrator assigns one or more profiles to your login name. Afteryou enter your login name and password, the system checks your profile toverify your access rights.The session starts if your user name and password are valid.

30 / 116 3BK 21202 AAAA PCZZA Ed.07


2.1.3 LogoutTo end an OMC-R session:1. Ensure that all pending applications are complete.2. From the desktop, click on [ Exit ].3. Click on [ Yes ] in the pop-up confirmation box.

2.1.4 Desktop DescriptionWhen you log in to the OMC-R, you see a standard CDE desktop. The desktopcontains an 9153 OMC-R control button on the front panel, as shown in thefollowing figure.

Figure 8: 9153 OMC-R Control Button

When you click on the control button, the 9153 OMC-R Iconbox opens, asshown in the following figure.

Figure 9: 9153 OMC-R Iconbox

The 9153 OMC-R Iconbox shows all possible applications. The type andnumber of applications shown in the window depends on the profile or profilesassigned to you.For a description of each icon, refer to 9153 OMC-R Icon Description (Section2.1.5).

3BK 21202 AAAA PCZZA Ed.07 31 / 116


2.1.5 9153 OMC-R Icon DescriptionIcons are described in alphabetical order below. You may not see all the iconsdescribed. The icons displayed depend on the users profile.

Click on ... To ...

[ Access RightsManagement (SEC) ]

Create, delete and manage operator profiles.Refer to SECUSM Main Window.

[ Administration Facilities ] Open the 9153 OMC-R Administration Facilities window. This tool is used tochange passwords and default printers.Refer to 9153 OMC-R Administration Facilities Window.

[ Alarm Call-OutManagement (ACO) ]

Start the Alarm Call Out Management tool.Refer to ACO Management Window (Section 4.1).

[ BSS Equipment &Transmission (BSSUSM) ]

Open the BSSUSM: Main View window. This application is used to managethe BSS software and hardware components and transmission elements.Refer to BSSUSM: Main View Window.

[ Command Mode Session ] Open a UNIX Command window.Refer to Command Mode Session Window.

[ Current Alarms (AS) ] View current alarms in the Alarm Surveillance application.Refer to Alarms Windows (Section 3.6).

[ Distributed SystemMonitoring (DSM) ]

Start the System Management application. This application ensures that theOMC-R software processes remain operational, that dependent processesare synchronized and that any failures are logged.Refer to DSMUSM Window.

[ Documentation ] Access the Electronic Documentation.Refer to Electronic Documentation.

[ Equipment Management(DCN) ]

Start the DCN: Management application. This manages connectionsbetween network elements and the OMC-R.Refer to DCN: Management Main Window.

[ Global FunctionManagement (UFM) ]

Start the Unique Function Management application. This applicationcustomizes alarms and measurements.Refer to 9153 OMC-R UFM Window.

[ History Alarms (AS) ] View archived alarms in the Alarm Surveillance application.Refer to Alarms Windows (Section 3.6).

[ Log Viewer ] Open the Log Viewer (Full Log) and Logs Merge on Demand (Full Log)windows. This enables you to view logged actions performed by users andcreate reports on merged logs.Refer to Log Viewer Window and Log Merge on Demand Window.

32 / 116 3BK 21202 AAAA PCZZA Ed.07


Click on ... To ...

[ MFS Backup ] Start the MFS Backup Manager application.Refer to MFS Backup Manager Window.

[ MFS Equipment &Transmission MFSUSM ]

Open the MFSUSM main window. This enables you to configure links, AterMuxes and Gbs.Refer to MFSUSM Main Window.

[ Parser, Obsynt & Alerter(OBSAL) ]

OBSAL is a new OMC-R component developed in the scope of B10 forMS-Portal features.Refer to OBSAL.

[ NPO Analysis Desktop ] NPO offers a full range of multi-standard QoS Monitoring and radio networkoptimization facilities. Refer to NPO Analysis Desktop.

[ NPO Data Management ] Open NPO Data ManagementRefer to NPO Data Management.

[ NPO Import/ExportManagement ]

Open NPO Import/Export ManagementRefer to NPO Import / Export Management.

[ NPO Tuning Browser ] Convert files generated by the NPO into a format that is importable by theOMC-R.

[ Radio Network (RNUSM) ] Open the RNUSM: SC and PRC Radio Browsers.Refer to RNUSM: SC and PRC Radio Browsers.

[ Remote Inventory(ENSUSM) ]

Open the ENSUSM Equipment View window. This enables you to configureand manage of network element data.Refer to ENSUSM Window.

[ Resource Monitoring(MRTG) ]

Open the MRTG main window. This enables you to monitor the 9130 BSCEvolution and MFS resources in realtime.Refer to MRTG Main Window.

[ Trace Viewer ] View IMSI trace results, carry out trace management, and file managementon the BSS.Refer to Trace Viewer Window.

[ UNIX Access ] Open a UNIX level window.

3BK 21202 AAAA PCZZA Ed.07 33 / 116


Click on ... To ...

[ User Facilities ] Open the 9153 OMC-R User Facilities window. This enables you to changeyour password, view a list of the people who recently logged on to theOMC-R, change the default printer, and to gain access to log managementfunctions.Refer to 9153 OMC-R User Facilities Window.

[ User Log Viewer ] Open the Log Viewer (Own Log) and Logs Merge on Demand (Own Log)windows. This enables you to view restrictive logged actions performed byusers and create restrictive reports on merged logs.Refer to User Log Viewer Window and Log Merge on Demand Window.

34 / 116 3BK 21202 AAAA PCZZA Ed.07


2.2 Types of Application Window

In B10 the number of views per configuration is adapted. One application (i.e.RNUSMSC) can be opened by a limited number of users. The number of theviews is depending of the OMC-R configuration.

The 9153 OMC-R uses two types of application window:

Graphical

HTTP.

2.2.1 Graphical Application Windows2.2.1.1 Graphical Window Description

Graphical windows are each divided into logical areas. Not all windows containall the areas. The following table describes these areas:

Area Description

Header Bar Identifies the window.

Menu Bar Lists the application menu options.

Frame Groups related fields and/or buttons.

Status Bar Displays the latest operating information.

Table 5: Graphical Application Window Description

The following figure shows an example of a graphical application window.

3BK 21202 AAAA PCZZA Ed.07 35 / 116


Figure 10: Example Graphical Application Window

2.2.1.2 Graphical Applications ListThe following table gives the list of the OMC-R graphical applications.

Application For More Information

Alarm Management (AS) Alarms Windows (Section 3.6)Command Mode Session Command Mode Session Window (Section 3.5)DCN: Management (DCN) DCN: Management Main Window (Section 3.7)Equipment Management Layer (EML) BSSUSM: Main View Window (Section 3.2)MFS Administration MFSUSM Main Window (Section 3.3)Parser, Obsynt & Alerter (OBSAL) OBSAL (Section 3.11)Radio Network Supervision, Configuration andAdministration

RNUSM: SC and PRC Radio Browsers (Section 3.1)

System Management (DSM) DSMUSM Window (Section 3.9)

Table 6: Graphical Applications and their Associated Windows Description

36 / 116 3BK 21202 AAAA PCZZA Ed.07


2.2.2 HTTP Application WindowsHTTP applications run in Mozilla windows. If you require information aboutusing Mozilla, refer to the Mozilla online help.

Application For More Information

ACO Management. ACO Management Window (Section 4.1)Administration Facilities 9153 OMC-R Administration Facilities Window

(Section 4.2)Alcatel documentation library Electronic Documentation (Section 2.4)ENSUSM window ENSUSM Window (Section 4.3)Log Viewer window Log Viewer Window (Section 4.4.1)User Log Viewer window User Log Viewer Window (Section 4.4.2)Trace Viewer Trace Viewer Window (Section 4.5)Unique Function Management (UFM) 9153 OMC-R UFM Window (Section 4.6)User Facilities 9153 OMC-R User Facilities Window (Section 4.7)

Table 7: HTTP Applications and their Associated Windows Description

3BK 21202 AAAA PCZZA Ed.07 37 / 116


2.3 Online HelpThe 9153 OMC-R provides a context-sensitive online help system in mostwindows. Using online help, you can quickly obtain information about aparticular part of an application.The online help is structured hierarchically and provides hyperlinks to navigatebetween help topics. This means that, from within one help window, you canaccess additional information or entries in the glossary.Highlighted abbreviations are defined in the glossary.

2.3.1 Access to HelpTo obtain help, click on [ Help ] in the current window. The 9153 OMC-Rdisplays help information relevant to the current window. The help window canalso provide cross-references to other appropriate sections in the help system.

Note: It is recommended that you increase the width of your help window to the fullwidth of your screen.

2.3.2 Navigating HelpThe 9153 OMC-R Online Help opens in an Modzilla window, as shown inthe following figure.

Figure 11: 9153 OMC-R Online Help Window Example

38 / 116 3BK 21202 AAAA PCZZA Ed.07


The window is divided into three frames:

NavigationThe navigation frame contains three buttons: Back, Forward, and Exit.

TopicThe topic frame contains a list of topics, like headings in a book. When youclick on a topic, the help information for that topic appears in the informationframe on the right of the window.

Information.Displays help information for a topic.

2.4 Electronic DocumentationThis section describes the structure and facilities of the Alcatel electronicdocumentation library.

2.4.1 AccessTo access the electronic documentation library:From the 9153 OMC-R Iconbox, click on the [ Documentation ] icon.The Electronic Documentation home page window opens, as shown in thefollowing figure

Figure 12: Electronic Documentation Home Page Window

3BK 21202 AAAA PCZZA Ed.07 39 / 116


2.4.2 StructureFrom any of the icons representing equipment on the Electronic Documentationhome page, you get access to the following categories:

Descriptive Documentation

O&M Documentation

Maintenance Task Procedures

Surveillance Task Procedures

Configuration Task Procedures

Administration Task Procedures.

The following facilities are also available:

Whats New

Recommendations

Parameters and Counters

Advanced Search

Help

Notices.

To see the list of documents available in a category, click on the name ofthe appropriate item of equipment.In each category, you see a list of document types to choose from. Thefollowing figure shows an example of the documentation categories.

Figure 13: Example Electronic Documentation Category Window

40 / 116 3BK 21202 AAAA PCZZA Ed.07


2.4.3 SearchingThe search panel lets you search through all the documents in the categoryto find specific information.You can use Advanced Search to find a specific document by entering eitherthe complete document title or only part of it.

3BK 21202 AAAA PCZZA Ed.07 41 / 116


42 / 116 3BK 21202 AAAA PCZZA Ed.07

3 9153 OMC-R Graphical Windows Applications


This section provides brief descriptions of the 9153 OMC-R graphical windowsapplications and their purposes. For more information, refer to the onlinehelp for each application.

3BK 21202 AAAA PCZZA Ed.07 43 / 116


3.1 RNUSM: SC and PRC Radio BrowsersThe radio browsers in the RNUSM main window type are the starting point forall logical configuration management operations. The browsers can displayviews of the supervised configuration (SC) or the provisional configuration(PRC) of the network. The SC represents the live OMC-R managed network.The PRC enables you to prepare a new radio network configuration.The PRC is used to:

Create a model of the whole or part of the network controlled by 9153OMC-R

Populate the model

Make modifications

Check the modifications for consistency and impact

Apply the model to the existing live SC

Modifications are performed offline in the PRC and then applied instantaneouslyto the SC, thereby minimizing outage time.It is possible to show the differences between the PRC and the existing SC(before applying it)The RNUSM radio browsers present a view of the radio network showing cells,and also give more detailed views of specific cells. They give direct access tothe radio network, via the SC or the PRC. Access to BSSUSM is also possible,via a list of supervised BSC/MFSs.

44 / 116 3BK 21202 AAAA PCZZA Ed.07


3.1.1 RNUSM: SC Radio BrowserTo access the RNUSM: SC radio browser, from the 9153 OMC-R Iconbox,click on the [ RNUSM ] icon.The RNUSM: SC radio browser opens, as shown in the following figure.

Figure 14: RNUSM: SC Radio Browser

For additional information, refer to the RNUSM: PRC/SC Main Windows onlinehelp.

3BK 21202 AAAA PCZZA Ed.07 45 / 116


3.1.2 RNUSM: SC Radio Browser FunctionsFor RNUSM mode, the SC functions that are available allow you to:

Configure cells, adjacencies, BSSs, and so onSupervise the network

Open a PRC, as shown in the following figure.

Figure 15: RNUSM: PRC Radio Browser Window

Create a PRC. To do this, enter the name of the new PRC then open it. Theresulting screen is similar to the figure above, but the fields are empty.

Create an external cell.

From the Main Menu bar of the RNUSM: SC radio browser, there are a numberof options available. These include options that allow you to make changes tothe PRC, then activate them on the SC.

46 / 116 3BK 21202 AAAA PCZZA Ed.07


3.1.3 RNUSM: PRC Radio Browser OptionsFor RNUSM mode, the PRC functions that are available allow you to:

Perform the configuration

Populate a PRC (you can drag and drop MFS, BSC, BTS, OMC cells andexternal cells from another PRC or SC)Check the impact of the changes, synchronize the PRC and the SC, andthen activate the new PRC

Generate, download, apply, abort, accept, reject or even close an MLUsession

Access the online help.

3BK 21202 AAAA PCZZA Ed.07 47 / 116


3.2 BSSUSM: Main View WindowThe BSSUSM: Main View window is used to manage hardware and softwarecomponents of the BSS and the transmission elements.Click on the required icon to access the corresponding functions.

3.2.1 The [ BSSUSM ] Icon1. From the 9153 OMC-R Iconbox, click on the [ BSSUSM ] icon.

The BSSUSM: Controller window opens, as shown in the following figure.

Figure 16: BSSUSM: Controller Window

2. Enter the BSS Id in the box provided and click on [ Open BSS ].The BSSUSM: Main View window opens, as shown in the following figure.

3.2.2 The [ RNUSM ] Icon1. From the 9153 OMC-R Iconbox, click on the [ RNUSM ] icon.

The RNUSM: SC radio browser opens, as shown in the following figure .2. Click on the [ Configuration ] tab.3. Select the appropriate BSS and click with the right mouse button to view a

pop-up menu.4. Select [ Show Equipment ].

The BSSUSM: Main View window opens, as shown in the figure 17.

48 / 116 3BK 21202 AAAA PCZZA Ed.07


3.2.3 The [ DCN ] Icon1. From the 9153 OMC-R Iconbox, click on the [ DCN ] icon.

The DCN: Management main window opens, as shown in Figure 26.2. Click on the [ BSS ] tab.3. Select the appropriate BSS and click with the right mouse button to view a

pop-up menu.4. Select [ Show Equipment ].

The BSSUSM: Main View window opens, as shown in the following figure:

Figure 17: BSSUSM: Main View Window

For additional information, refer to the BSSUSM: Main View window online help.

3BK 21202 AAAA PCZZA Ed.07 49 / 116


3.2.4 Abis View Window IconsThere are two types of BTS from Abis point of view: Single BTS andDouble-Abis BTS.The visualization of the BTS:

for Single BTS is an empty triangle.

for Double-Abis BTS on the primary Abis is a triangle containing a Pletter inside.

for Double-Abis BTS on the secondary Abis is a triangle containing a Sletter inside.

To get the information on which Abis is a given BTS: right click on it thenselect [ Navigate to Abis view ] option.

50 / 116 3BK 21202 AAAA PCZZA Ed.07


Figure 18: BSSUSM: Abis Topology View

3.2.5 Find Facility in Abis viewTo search for a string in the tree gadget under Abis Navigator window , you

can use the binocular icon .

3BK 21202 AAAA PCZZA Ed.07 51 / 116


3.3 MFSUSM Main WindowThe MFSUSM main window is used to configure links, Ater Muxes and Gbs. Itcan also be used to navigate to the BSSUSM and ASUSM functions.

Note: The MFSUSM main window can be accessed from the [ MFSUSM ], [ RNUSM ]or [ DCN ] icons.To access the MFSUSM main window, click on the required icon.

3.3.1 The [ MFSUSM ] Icon1. From the 9153 OMC-R Iconbox, click on the [ MFSUSM ] icon.

The MFSUSM: Controller window opens, as shown in the following figure.

Figure 19: MFSUSM: Controller Window

2. Create an MFS by entering an MFS Id in the box provided and clickon [ Create ].The MFSUSM main window opens, as shown in Figure 20.

52 / 116 3BK 21202 AAAA PCZZA Ed.07


3.3.2 The [ RNUSM ] Icon1. From the 9153 OMC-R Iconbox, click on the [ RNUSM ] icon.

The RNUSM: SC radio browser opens, as shown in Figure 14.2. Click on the [ Configuration ] tab.3. Select the appropriate MFS.4. Click with the right mouse button to view a pop-up menu.5. Click on [ Show Equipment ].

The MFSUSM main window opens, as shown in Figure 20.

3.3.3 The [ DCN ] Icon1. From the 9153 OMC-R Iconbox, click on the [ DCN ] icon.

The DCN: Management main window opens, as shown in Figure 26.2. Select the appropriate MFS.3. Click with the right mouse button to view a pop-up menu.4. Click on [ Show Equipment ].

The MFSUSM main window opens, as shown in the following figure.

Figure 20: MFSUSM Main Window

3BK 21202 AAAA PCZZA Ed.07 53 / 116


3.3.4 MFSUSM Window FunctionsThe functions available from the MFSUSM window include the following:

The ability to configure links (or cabling), including:MFS to BSC. This is set up on the BSC (BSSIM) side first, then alignedin the BSC and the MFSMFS to TC. This is set up on the BSC (BSSIM) side first, then alignedin the MFSMFS to SGSN. Set up entirely in the MFS.

The ability to configure the Ater Muxes, including:Division of time slots between the GPRS and the circuitGSL to LAPD links. These are set up on the BSC (BSSIM) side first,then aligned in the MFS.

The ability to configure Gbs, including:NSEsNS-VCsFrame Relay PVCsBearer channels.

From the MFSUSM main window, you can navigate to the following:

BSSUSM. For example, to view the Ater Mux configuration, to unlock timeslots formerly assigned to GPRS, to add hardware to the network, to modifyit or to view it down to the level of the individual boards in their racks. Afurther view allows you to view the functions of these boards.

ASUSM. For example, to view the MFS alarms.

From the Main Menu bar, you can:

Check the Ater Mux and Gb configurations

Check the Ater Mux/Gb links for mis-alignments and link conflicts

Allow alarm reporting for GPRS transport resources

Assign and check NSE to BSC association

Create, modify or delete bearer channels, NSVCs, PVCs, NSEs, andGSLs channels

Link and unlink BSC/TC

Lock/unlock Ater Mux/Gb resources

Reserve and unreserve Ater Mux time slots for GPRS

Link and unlink BSC/TC


54 / 116 3BK 21202 AAAA PCZZA Ed.07


3.3.5 MFSUSM in Limited ModeThe MFUSM main window operates in limited mode when one or more BSS arenot operational. This means that the user can only supervise the MFS. Theuser cannot configure the MFS from the MFSUSM main window in this mode.If one or more BSS are not operational, a message box opens:

BSSIM problem! Do you want to restart in limited mode?

Click on [ OK ] to open the MFSUSM main window in "limited mode".The message Limited mode opens in the title bar of the MFSUSM main window.

3.3.6 Restore the MFSUSM to Normal ModeTo restore MFSUSM to normal mode:From the MFSUSM Main Menu bar, select:View -> Refresh .

Note: The MFSUSM remains in limited mode until all BSSs have been restored.

3BK 21202 AAAA PCZZA Ed.07 55 / 116


3.4 MRTG Main WindowThe MRTG: Main View window is used to monitor the 9130 BSC Evolution andMFS (both 9135 MFS and the 9130 MFS Evolution) resources in realtime.Only the 9130 BSC Evolution and the MFS with the Enable collection functionselected, and the value for Community string set to public can be monitored.

3.4.1 MRTG: Main View WindowYou can navigate to MRTG page from the:

Iconbox, by clicking on the [ MRTG ] iconMFSUSM window, by following the menu: Views -> Navigate to MRTG

DCN window, by selecting the appropriate 9130 BSC Evolution or MFS,then following the menu: Function -> Navigate to MRTG

DCN window, by right clicking on the appropriate 9130 BSC Evolution orMFS, then selecting: Navigate to MRTG.

The "9153-MRTG: Main View" window opens, as shown in the following figure.

Figure 21: "9153-MRTG: Main View" Window

56 / 116 3BK 21202 AAAA PCZZA Ed.07


From the"9153-MRTG: Main View" window, select the appropriate equipmenton which you want to visualize the traffic load.Depending on your previous choice, a new window opens, displaying a list ofeither the declared 9130 BSC Evolution or the declared MFS.

Figure 22: 9153 OMC-R MRTG MFS View

When you select an 9130 BSC Evolution or an MFS, the MRTG Index Pageopens.

3.4.2 9130 BSC Evolution MRTG Index PageThe "9130 BSC Evolution MRTG window" displays the following types of report:

CPU Load

Memory Usage

Swap Usage

Network traffic:Ethernet 0 TrafficEthernet 0 Traffic ErrorsEthernet 1 TrafficEthernet 1 Traffic Errors.

Disk Usage, for the /, /common and /alternate partitions

Failed allocation requests for the /, /common and /alternate partitions.

3BK 21202 AAAA PCZZA Ed.07 57 / 116


58 / 116 3BK 21202 AAAA PCZZA Ed.07


3.4.3 MFS MRTG Index PageThe "MFS MRTG" window displays the following types of report:

Memory & Swap Usage and Allocation Failure

OMC-MFS Traffic and Errors

MFS LSN1, LSN2 Traffic and Errors

CPU Usage

Disk Usage for different partitions.

3.4.4 Detailed StatisticsDisplay a detailed daily / weekly / monthly / yearly report, by clicking on therequired graph either from the 9130 BSC Evolution, or the MFS MRTG IndexPage.

3BK 21202 AAAA PCZZA Ed.07 59 / 116


3.5 Command Mode Session WindowThe Command Mode Session window allows you to:

Run a series of procedures

Schedule procedures to run on a given date and time

Perform migrations.

Command Mode Session for the 9153 OMC-R allows you to perform varioustasks in both O&M and BSSUSM in a dedicated terminal window. Through thissingle interface, you can submit requests in any UNIX shell script language.Everything that can be done in a UNIX environment, can also be done inCommand Mode Session. Common functions such as saving, deleting,printing, copying, viewing, editing, renaming and scheduling are performedusing standard UNIX commands.Depending on your requirements, Command Mode Session can be used inone of the following ways:

Dedicated Command Mode Session, which allows you to run proceduresimmediately.

Implicit Command Mode Session, which allows you to create files andschedule Command Mode Session procedures to run later.

Explicit Command Mode Session, which allows you to schedule CommandMode Session procedures to run with other sessions.

Refer to the 9153 OMC-R Command Mode document for further informationabout the [ Command Mode Session ] function.To access the Command Mode Session window:From the 9153 OMC-R Iconbox, click on the [ Command Mode Session ] icon.The "Command Mode Session" window opens, as shown in the following figure.

Figure 23: Command Mode Session Window

60 / 116 3BK 21202 AAAA PCZZA Ed.07


For command mode, the following functions are available:

OMC Domain Management

BSS Management

PMC Management

ODMC management

BSC management

BSC SW Management

BSC HW Management

TC Management

BTS management

Cell management

MFS management

PRC management

Support resource management

Function management

Audit Commands

Query Adjacencies.

3BK 21202 AAAA PCZZA Ed.07 61 / 116


3.6 Alarms WindowsWhen the O&M controller of a subsystem in the BSS detects irregularconditions, an alarm report is forwarded to the OMC-R, which then displaysit to you.There are two kinds of alarm:

Alarms with severity levels of warning, minor, major or critical. These aregenerated whenever a fault is detected.

Alarms with a severity level of indeterminate. These correspond tomaintenance information (that is, BSS events). They are automaticallypurged and sent to the historical alarm lists.

3.6.1 Alarm AttributesAlarms have the following primary attributes:

A user-friendly name

A Managed Object Class (MOC) of the object that is impacted by the alarmA Managed Object Instance (MOI) of the object that is impacted by the alarmAn event type

An event time

A probable cause

A perceived severity level.

To customize the alarm display, you can filter and sort based on these attributes.Although you cannot filter or sort based on the following attributes, they can bedisplayed on request:

Specific problem types

Threshold information (if the alarm cause is the crossing of a threshold)Notification identifiers

State changes associated with the alarm

Proposed repair actions

Additional text

Alarm/availability status

Administrative/operational/usage state.

Current alarms are stored in the current alarm list until they are purgedautomatically (once they reach a pre-defined age), or cleared andacknowledged. They are then archived in the historical alarm list.

62 / 116 3BK 21202 AAAA PCZZA Ed.07


3.6.2 AS Current USM: Counter Summary WindowThe AS Current USM: Counter Summary window displays information aboutthe list of current alarms.To access the AS Current USM: Counter Summary window:From the 9153 OMC-R Iconbox, click on the [ AS:Current Alarms ] icon.The "AS Current USM: Counter Summary" window opens, as shown in thefollowing figure.

Figure 24: AS Current USM: Counter Summary Window

Lists of current alarms are displayed according to user-defined criteria.These criteria are:

Alarm severity

Alarm type

Probable cause

Affected NEs

Alarm time and date

Alarm states.

The current alarm list display can be based on a combination of the abovecriteria.

3BK 21202 AAAA PCZZA Ed.07 63 / 116


3.6.3 AS Current USM: Counter Summary Window FunctionsFor current alarms, the following functions are available:

Alarm processing. When an alarm report is received from the BSC orthe MFS, the state of the corresponding managed object is updated inthe OMC-R and you are notified.

List of alarms display.You can access three different levels of alarm display:

Counter summary: displays alarm counters for each alarm sublist.Alarm sublist: groups alarms according to user-defined filter and sortcriteria.More information: displays complete information for a given alarm,including text information which can be attached to each alarm.

The display is refreshed in realtime.

New alarm indicator activation/deactivation. An incoming alarm in agiven sublist can trigger a beep. You can also associate the execution ofa script with an upper/lower threshold related to the number of alarms ina given sublist. The script can then trigger a flashing light, or activatean external device.

Navigation to radio and equipment management windows. Displays of thestatus of current alarms are also provided in the radio and equipmentmanagement windows. Faulty items are colored according to the alarmseverity. Navigation is possible between these windows and the alarm listwhich corresponds to the faulty item.

Alarm acknowledgment. Indicates that the alarm has been taken intoaccount for analysis and repair. User-defined criteria can also be used totrigger this operation automatically.

Alarm reservation/de-reservation. This operation locks/unlocks an alarm forexclusive use by the operator who performs the reservation.

Manual Alarm export. You can export the primary attributes of one ormore current alarms or complete alarm information for a current alarm toa printer or an ASCII file.

Automatic Alarm export. At pre-defined intervals, export all the informationthat relates to the current alarms to an ASCII file.

Current alarms clear. When the end of an alarm is reported to the OMC-R,the alarm clears automatically. However, you must acknowledge the alarmbefore it disappears from the current alarms list.

64 / 116 3BK 21202 AAAA PCZZA Ed.07


From the Main Menu bar, you can:

Create, modify, delete, activate or de-activate sublists

View administration and synchronization alarm reports

View aging information for the alarm reports

View trigger information for the alarm reports

Display severity counters

Display inactive sublists

Access the archives and retrieve alarm information

Navigate between various types of alarm reports, including:Alarm report summariesVarious sublistsCurrent alarm reportsArchived alarm reports

Exit the window and, optionally, save any changes you have made


3BK 21202 AAAA PCZZA Ed.07 65 / 116


3.6.4 AS Historical USM: Counter Summary WindowThis window allows you to manage the display of historical alarms. These arealarms which have been purged from the current alarm list and archived.Historical alarms are stored in public files, organized by date with one file foreach day. You can save these files to your private files, which you can thenmanage as you wish.

Note: The process of archiving an alarm into the historical alarm list is not reversible.The content of a historical alarm is frozen.To access the AS Historical USM: Counter Summary window:From the 9153 OMC-R Iconbox, click on the [ AS:Histo Alarms ] icon.The "AS Historical USM: Counter Summary" window opens, as shown inthe following figure.

Figure 25: AS Historical USM: Counter Summary Window

Alarms are deleted from the current alarm list, and stored in the historical alarmlist once they are no longer current. Additional information, describing why analarm is no longer current, is also stored.An alarm is no longer current:

After it is cleared and acknowledged

After it is manually purged, at the request of the operator

After it is automatically purged. This is done according to pre-defineduser criteria.

After the storage capacity reaches the overflow criteria level.

66 / 116 3BK 21202 AAAA PCZZA Ed.07


3.6.5 AS Historical USM: Counter Summary Window FunctionsFor historical alarms, the following functions are available:

Export historical alarms/e

Documents

9153 OMC-R Getting Started