212060000 e 06

Alcatel-Lucent GSM

BSS Surveillance Handbook

BSS Document

Procedural Handbook

Release B10

3BK 21206 AAAA PCZZA Ed.06

Status RELEASED

Short title BSS Surveillance Handbook

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 / 56 3BK 21206 AAAA PCZZA Ed.06

Contents

Contents

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

1 Network Supervision and Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.1.1 ALMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.1.2 Status of Managed Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.1.3 CAL and HAL Alarm Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.1.4 Alarm Acknowledgement in RNUSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.2 Alarm Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.3 Network Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

1.3.1 Managed Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.3.2 Network Supervision Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2 Network Supervision and Alarm Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.1 Audit GPRS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.2 Configure External Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.2.1 Customize External Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.2.2 Add Client Customized External Alarm for BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.2.3 Delete Client Customized External Alarm for BTS . . . . . . . . . . . . . . . . . . . . . . . . . 212.2.4 Undo Last Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.3 Create Alarm Sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.4 Create Alarm Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.5 Delete Alarm Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.6 Display APC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.7 Modify APC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.8 Display MFS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.9 Inhibit / Allow Alarm Reporting on Abis TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.10 Inhibit / Allow Alarm Reporting on All A TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.11 Inhibit / Allow Alarm Reporting on One A TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.12 Inhibit / Allow Alarm Reporting on Ater Mux (BSC or TC Side) . . . . . . . . . . . . . . . . . . . . . . . . . 242.13 Inhibit / Allow Alarm Reporting on MFS TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.14 Lock A Channel Support Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.15 Lock Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.15.1 Basic Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.15.2 QoS Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.16 Lock Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.17 Lock BTS O&M Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.18 Lock BSC or BTS Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.19 Lock RSL and / or N7 Support Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.19.1 RSL Support Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.19.2 N7 Support Resource (HSL or LSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.20 Modify Alarm Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.21 OMC-R Alarm Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.22 Open / Close Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.23 Reset Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.23.1 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.23.2 Impact on Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.24 Reset Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.24.1 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.24.2 Impact on Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2.25 Reset BTS Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.26 Restart Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30


2.27 Restart Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3BK 21206 AAAA PCZZA Ed.06 3 / 56

Contents


2.28 Restart BTS Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.29 Shut Down A Channel Support Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.30 Shut Down Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.31 Shut Down BTS Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.32 Shut Down RSL Support Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.33 Test Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.34 Unlock A Channel Support Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332.35 Unlock Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2.35.1 Basic Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332.35.2 QoS Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2.36 Unlock Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332.37 Unlock BTS O&M Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342.38 Unlock BSC or BTS Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342.39 Unlock RSL, N7 Support Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

2.39.1 RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342.39.2 N7 (HSL or LSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

2.40 Verify Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352.41 View Status of Managed Objects and Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

2.41.1 BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352.41.2 X.25 (Only for 9120 BSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362.41.3 N7 (HSL or LSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362.41.4 ACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362.41.5 BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372.41.6 Active Telecom SSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372.41.7 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372.41.8 Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.41.9 Ater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.41.10 TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

3 Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.2 Standard Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.3 Detailed Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

4 Performance Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.1 Activate BSC Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.2 Audit BSC Alarms and Administrative State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.3 Audit PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.4 Audit Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.5 Copy RMS BSC Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.6 Create ODMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.7 De-activate BSC Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.8 Define PMC List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.9 Delete ODMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.10 Display Cell Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.11 Display Cell List Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.12 Display MFS Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.13 Display USD A Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.14 Display USD A DTC Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504.15 Display USD Cell Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504.16 Display USD Detailed Cell Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504.17 Display USD Detailed DTC Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.18 Edit RMS BSC Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.19 Lock / Shut Down IMSI Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.20 Lock ODMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514.21 Lock PMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

4 / 56 3BK 21206 AAAA PCZZA Ed.06

Contents

4.22 Modify BSC Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.23 Modify IMSI Trace Control Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.24 Modify ODMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.25 Modify PMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.26 Query BSC Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.27 Query BSC Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.28 Query ODMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.29 Stop / Start USD Cell Overview Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.30 Stop / Start USD A Interface Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.31 Unlock IMSI Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.32 Unlock ODMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564.33 Unlock PMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3BK 21206 AAAA PCZZA Ed.06 5 / 56

Contents

6 / 56 3BK 21206 AAAA PCZZA Ed.06

Preface

Preface

Purpose This document describes the surveillance and performance tasks of theOMC-R.

It is applicable to BSS at technical level release B10.

What’s New In Edition 06Update with the new equipment naming.

In Edition 05Update in section Inhibit / Allow Alarm Reporting on Abis TP (Section 2.9)

In Edition 04Update in View Status of Managed Objects and Alarms

In Edition 03Update in:

Create ODMC (Section 4.6)

Modify ODMC (Section 4.24)

In Edition 02Delivered in release.

First official release of the document for B10 MR2.

In Edition 01First official release of the document for B10.

3BK 21206 AAAA PCZZA Ed.06 7 / 56

Preface

Audience This document is intended for:

Operations and Maintenance technicians and systems designers

Operators who are responsible for carrying out O&M surveillance and

performance functions on assigned BSSs.

Assumed Knowledge The reader must have a general knowledge of:

Telecommunications systems

Telecommunications terminology

Electronics

BSC functions

Windows environment.

8 / 56 3BK 21206 AAAA PCZZA Ed.06

1 Network Supervision and Alarm Management


This section describes the network management, and includes customizingalarm profiles and supervising network equipment.

3BK 21206 AAAA PCZZA Ed.06 9 / 56


1.1 IntroductionNetwork Supervision and Alarm Management covers the area of networkmanagement. This includes customizing alarm profiles and supervisingnetwork equipment.

1.1.1 ALMAP

The software architecture of the 9153 OMC-R is based on ALMAP,Alcatel-Lucent’s object-oriented open management platform that complies withall major TMN and system management standards. The alarm surveillancecomponent of ALMAP provides:

Centralized alarm integration

Distributed access

Current and historical alarms

HMI navigation with other applications.

The 9153 OMC-R allows the operator to analyze an alarm and to identifya faulty managed object (see Status of Managed Objects (Section 1.1.2)).For more information about managed objects, refer to the Operations &Maintenance Principles manual. Once the problem is corrected, the operatorcan analyze the success of the correction by checking that the alarm is clearedand monitoring the state of the managed object again.

10 / 56 3BK 21206 AAAA PCZZA Ed.06


1.1.2 Status of Managed Objects

Network supervision is based on managing the status of the managed objects.This status comprises five states, as shown in the following table:

State Values Meaning

Locked Prohibited from performing services.

Shuttingdown

No new request is accepted by the managed object during the shuttingdown phase.

Administrative

Unlocked Permitted to perform services.

Disabled Inoperable. Cannot provide service.Operational

Enabled Partially or completely operable. Available for use.

Degraded Service is degraded, for example, in speed or operating capacity.

Failed Internal fault preventing operation.

Dependency Cannot operate because another, dependent resource is unavailable.

Offline Requires an operation to be performed to place the resource online.

Availability

In-test Undergoing a test procedure.

Control Suspended Service is suspended.

Unknown Indicates if all other states are valid.

Table 1: Managed Objects Description States

All supervised managed objects have a current alarm list that identifies all thecurrent alarms of the managed object.

The status of a managed object can be affected by several events:

An operation performed at an OMC-R terminal

An operation performed at a local terminal inducing state change

notifications on SBLs

Detection of loss and recovery of resource.

3BK 21206 AAAA PCZZA Ed.06 11 / 56


1.1.3 CAL and HAL Alarm Processes

The 9153 OMC-R uses two main alarm processes:

The Current Alarm List (CAL) for real-time management

The Historical Alarm List (HAL) for static analysis.

The following figure illustrates these processes.

navigation navigation

Real−timeManagement:

CAL

Staticanalysis:

HALExternalApplication

Sublistordering &

filtering

Sublistordering &

filtering

Current Alarms

Auto beeping

Archived Alarms

Auto retrievingOverflow purge

Auto acknowledgement filter

Auto purge filter

BSCBSC

MFS

BTSBTS

NetworkRessources

Archivingfiltering

Alarm flow

Alarm ordering

Alarm filtering

Figure 1: CAL and HAL Alarm Processes

1.1.3.1 CALCAL contains all alarms present on the managed objects. By default, an alarmstays in CAL as long as it is not cleared and acknowledged. It is possible todefine filters (auto-purge, auto-acknowledge) to customize the management ofalarms displayed in CAL. Any new alarm is reported to the operator after beingprocessed by the filters. It is possible to define alarm sublists to access alarmsmore easily. Alarm lists are updated dynamically.

1.1.3.2 HALHAL contains alarms that have been acknowledged and cleared. It is possibleto use the same sublist, ordering, and filtering facilities as in CAL, this timeto consult archived alarms.

12 / 56 3BK 21206 AAAA PCZZA Ed.06


1.1.3.3 AS FacilitiesAS provides the following facilities:

Create / Delete / Modify an alarm filter

Create an alarm sublist

Activate / De-activate an alarm filter on CAL

Enable / Disable an alarm filter on HAL

Export CAL / HAL

Acknowledge alarm: allow an alarm to be removed from CAL once cleared

Purge alarm: manual transfer from CAL to HAL

Reserve / Unreserve alarm: allow one user to reserve an alarm. Onlythat user can unreserve it.

Activate / De-activate alarm filter indicator. Allows an indicator to launch

a specific action.

1.1.4 Alarm Acknowledgement in RNUSM

Alarm acknowledgement refers to label and icon colors for the items in theRNUSM: Tree Browser window.

Due to the coloring of items and icons, the operator has a better visibility of thealarms in RNUSM. The alarms update dynamically, so the operator can seequickly whether there are non-acknowledged alarms or not.

The label of an item is blue when there is a non-acknowledged alarm with aseverity higher than, or equal to minor on the related object.

The BSC icon is drawn in blue and is bold when there is a non-acknowledgedalarm with a severity higher than, or equal to minor on the BSC or one of itscontained objects (alarms synthesis).

3BK 21206 AAAA PCZZA Ed.06 13 / 56


The following table describes the alarm status in release B10.

Icon Icon Meaning Background Color Meaning

1st Equipment symbol. Only used for BSC: alarmsynthesis.

2nd Synthesis of GSM ’administrative, operational andunknown’ states.

Alarm status

MFS alarm synthesis.

3rd GSM alignment status. Alarm status


4th (only if GPRS) Synthesis of GPRS ’administrative, operational andunknown’ states.

Alarm status


5th (only if GPRS) MFS alignment status for the GPRS part. Alarm status


Alarm status.

The status of one object, concerning active alarms on it. It displaysthe highest severity of all active alarms on this object.

Alarm synthesis.

A status attached to one father object containing several childrenobjects, concerning active alarms on all of them. It displays thehighest severity of all active alarms on the father object andits children.

1.2 Alarm CustomizationCustomizing alarm profiles involves associating a new alarm severity to anyalarm produced by the BSS.

The available alarm customization tasks are:

Configure External Alarms (Section 2.2)

Display APC (Section 2.6)

Modify APC (Section 2.7).

1.3 Network SupervisionNetwork supervision provides the operator with a view of the network from theequipment and radio point of view. The operator can detect abnormal behaviorof the system and perform maintenance and repair actions.

14 / 56 3BK 21206 AAAA PCZZA Ed.06


1.3.1 Managed Objects

The following table describes BSS supervision behavior in terms of sixcategories of managed objects.

Managed Objects Description

Board A board performs a set of specific functions. Examplesof boards are omua, estp, and fcps.

Function A function carried out by one or more boards. Examplesof functions are RA, FU, DISC, and X.25.

Support Resource A telecom logical unit. Examples of support resourcesare circuit group and Abis TP.

Resource A resource performs telecom tasks. It is supported byboards and support resources to perform a service.

O&M Capability O&M capability represents the ability to supervise a setof support resources and boards. An example of O&Mcapability is BTS O&M.

Equipment A set of managed objects representingtelecommunication, transmission, and transcodingequipment within the BSS. These managed objects areBSCs, BTSs, and TCs.

Table 2: Managed Objects Category Description

3BK 21206 AAAA PCZZA Ed.06 15 / 56


Each SBL can be mapped to one of these managed objects (except theboards), as described in the following table.

Managed Object SBL Mapping Type of Object

N N7

Circuit Group ATR

Ater Mux TP Ater-Hway TP

Abis TP Abis-Hway TP

A TP A-PCM-TP

ACH ACH

RSL RSL

OML OML

GSL GSL

N7 Synthesis

Support resource

Cell BTS_TEL

BSC BSS_TEL

TRX TRX

Resource

BTS BTS_O&M O&M Capabilities

BSC BSC RIT

BTS BTS RIT

TC TC RIT

Equipment

All BSC boards (DTC, TCUC...) All BSC boards

All TC boards (TC16, DB2M...) All TC boards

All BTS boards (DRFU, SMBI...) All BTS boards

Board

All BSC functions (X.25,BSC-ADAPT...)

All BSC functions

All BTS functions (FU, CU, RA...) All BTS functions

Function

Table 3: Managed Objects Mapped to SBLs Description

16 / 56 3BK 21206 AAAA PCZZA Ed.06


1.3.2 Network Supervision Tasks

The available network supervision tasks are:

Audit GPRS Alarms (Section 2.1)

Create Alarm Filter (Section 2.4)

Create Alarm Sublist (Section 2.3)

Configure External Alarms (Section 2.2)

Delete Alarm Filter (Section 2.5)

Display APC (Section 2.6)

Display MFS Alarms (Section 2.8)

Inhibit / Allow Alarm Reporting on Abis TP (Section 2.9)

Inhibit / Allow Alarm Reporting on All A TPs (Section 2.10)

Inhibit / Allow Alarm Reporting on Ater Mux (BSC or TC Side) (Section 2.12)

Inhibit / Allow Alarm Reporting on MFS TP (Section 2.13)

Lock A Channel Support Resource (Section 2.14)

Lock Alerter (Section 2.15)

Lock Board (Section 2.16)

Lock BSC or BTS Functions (Section 2.18)

Lock BTS O&M Capability (Section 2.17)

Lock RSL and / or N7 Support Resource (Section 2.19)

Modify Alarm Filter (Section 2.20)

Modify APC (Section 2.7)

OMC-R Alarm Handling (Section 2.21)

Open / Close Loop (Section 2.22)

Reset Board (Section 2.23)

Reset BTS Function (Section 2.25)

Reset Equipment (Section 2.24)

Restart Board (Section 2.26)

Restart BTS Function (Section 2.28)

Restart Equipment (Section 2.27)

Shut Down A Channel Support Resource (Section 2.29)

Shut Down Board (Section 2.30)

Shut Down BTS Function (Section 2.31)

Shut Down RSL Support Resource (Section 2.32)

Test Board (Section 2.33)

3BK 21206 AAAA PCZZA Ed.06 17 / 56


Unlock A Channel Support Resource (Section 2.34)

Unlock Alerter (Section 2.35)

Unlock BSC or BTS Functions (Section 2.38)

Unlock Board (Section 2.36)

Unlock BTS O&M Capability (Section 2.37)

Unlock RSL, N7 Support Resource (Section 2.39)

Verify Board (Section 2.40).

View Status of Managed Objects and Alarms (Section 2.41).

18 / 56 3BK 21206 AAAA PCZZA Ed.06

2 Network Supervision and Alarm Management Tasks


This section describes how to perform network supervision and alarmmanagement tasks.

3BK 21206 AAAA PCZZA Ed.06 19 / 56


2.1 Audit GPRS AlarmsThis task resynchronizes alarms between the MFS-NE and the Unique FunctionManagement (UFM) module. New GPRS alarms are updated in the UFM.

In the MFSUSM main window, select Views -> Audit Alarm.

2.2 Configure External AlarmsThis task configures BTS and BSC external alarms.

Note: The first time you access UFM, you must provide a username and password.

In the 9153 OMC-R Unique Function Management main window, click on[ External Alarms ].

The External Alarms Definition window opens.

There are three external alarm tables:

’Alcatel Default Definition’ contains all predefined Alcatel-Lucent externalalarms for the BTS

’Customer BTS’ contains client customized external alarms for the BTS

’BSC Table’ contains the external alarms for the BSC.

2.2.1 Customize External Alarm

To customize external alarms:

1. To change a table row from the ’Customer BTS’ or ’BSC Table’ tables, clickon its corresponding [ Update ] button.

The Change Table Row window opens.

2. Modify one or more of the following parameters:

Alarm Name

Additional Text

Alarm Severity

Probable Cause

Alarm Type Numbers.

3. Click on [ Apply Changes ].

The External Alarms Definition window opens with the changes applied.

To update the values of the ’Alcatel Default Definition’ table, you have toperform the necessary customization in the ’Customer BTS’ table. Thecustomer configuration has priority over the Alcatel-Lucent proposed values,and will overwrite the Alcatel-Lucent customization.

20 / 56 3BK 21206 AAAA PCZZA Ed.06


2.2.2 Add Client Customized External Alarm for BTS

To add a client customized external alarm for BTS:

1. Click on [ Add ] below the ’Customer BTS’ table.

The Add Table Row window opens.

2. Modify one or more of the following parameters:

Alarm Name

Additional Text

Alarm Severity

Probable Cause

Alarm Type Numbers.

3. Click on [ Apply ].


2.2.3 Delete Client Customized External Alarm for BTS

To delete a client customized external alarm for BTS:

1. Click on its corresponding [ Update ] button.

The Change Table Row window opens.

2. Click on [ Delete ].


2.2.4 Undo Last Changes

To undo the last change performed, click on [ Undo Last Change ].

The External Alarms Definition window refreshes with the undo of the lastchange applied.

2.3 Create Alarm SublistTo create an alarm sublist:

1. In the 9153 OMC-R Icon Box, click on the [ AS:Current Alarms ] icon.

The AS Current USM: Counter Summary window opens.

2. Select Sublist -> Create.

The AS Current USM: Sublist Name Chooser window opens.

3. Enter a name for the new sublist, and click on [ Ok ].

The new sublist appears in the Sublist list.

3BK 21206 AAAA PCZZA Ed.06 21 / 56


2.4 Create Alarm Filter

To create an alarm filter, you must first create an alarm sublist. Complete theCreate Alarm Sublist (Section 2.3) task first.

To create an alarm filter:



2. Select the required sublist.

3. Select Sublist -> Modify....The Sublist Properties window opens.

4. Expand the Sublist Properties menu on the left side of the screen, thenexpand the Filter menu.You can choose from four filter types:

Basic

Source

Extended

Advanced.

5. Modify the filter attributes as required, and click on [ Apply ].

When modifying Specific Problems in the ’Advanced filter’ field, the alarm filtermust be set as Non NullIntersection, and not as Equal.

2.5 Delete Alarm FilterTo delete an alarm filter:



2. Select the required sublist(s).

3. Select Sublist -> Delete...A Question window opens.

4. Click on [ Yes ] to delete selected sublists.

22 / 56 3BK 21206 AAAA PCZZA Ed.06


2.6 Display APCTo display the Alarm Profile Customization for specific alarm classes andclassifications:

1. In the 9153 OMC-R Unique Function Management main window, click on[ APC ].

The Alarm Profile Customization window opens.

2. Select an alarm classification from the Alarm Classification selection list.

3. Select an alarm class from the Alarm Class selection list.

4. Click on [ Apply Filter ].

To return to the original default alarm values, click on the [ Reset ] buttonwhich is in the first part of the window.All the profile customizations are lost.

2.7 Modify APCYou can declare new alarm severities for any alarm class and type. To editthe APC:

1. In the 9153 OMC-R Unique Function Management main window, click on[ APC ].

The Alarm Profile Customization window opens.

2. Select an alarm classification from the Alarm Classification selection list.

3. Select an alarm class from the Alarm Class selection list, and click on[ Apply Filter ].

The alarm filter is displayed for the alarm class and classification selected.

4. Select an alarm classification from the Change Classification selection list,and click on [ Apply Changes ].

The alarm filter is redisplayed for the selected alarm class and classification.

To go back to the original alarm values for the current edited alarm filter, clickon the [ Reset ] button which is in the second part of the window.

2.8 Display MFS AlarmsTo open the AS Current USM: Counter Summary and Alarm Sublist windowsand display a general report on MFS alarms:

1. In the MFSUSM main window, select Views -> Display Alarms.

2. For a detailed report on a specific item, click on the required sublist item inthe AS Current USM: Counter Summary window.

3BK 21206 AAAA PCZZA Ed.06 23 / 56


2.9 Inhibit / Allow Alarm Reporting on Abis TPTo inhibit or allow alarm reporting on an Abis TP:

1. In the BSSUSM: Main View window, click on the [ Abis ] icon in theFunctional Alarm Synthesis panel.

The Abis Topology View window opens.

2. Expand the required Abis chain.

3. Select the required BTS TP.

4. Right click, and select Inhibit Alarm Reporting on TP Up / Down or AllowAlarm Reporting on TP Up / Down from the popup menu.

Note: This task Inhibit Alarm Reporting on TP Up / Down , allocates extra-TS andinhibits alarm reporting on the impacted TP of secondary Abis.

2.10 Inhibit / Allow Alarm Reporting on All A TPsTo inhibit or allow alarm reporting on all A TPs:

1. In the BSSUSM: Main View window, click on the [ A / Ater Mux ] icon in theFunctional Alarm Synthesis panel.

The Ater Topology View window opens.

2. Select the required Ater Mux Connection.

3. Right click, and select Inhibit Alarm Reporting on all A TPs or AllowAlarm Reporting on all A TPs from the popup menu.

2.11 Inhibit / Allow Alarm Reporting on One A TPTo inhibit or allow alarm reporting on one A TP:



2. Select the required A TP.

3. Right click, and select Inhibit Alarm Reporting on TC Side or Allow AlarmReporting on TC Side from the popup menu.

2.12 Inhibit / Allow Alarm Reporting on Ater Mux (BSC or TCSide)

To inhibit or allow alarm reporting on an entire Ater Mux connection, BSCor TC side:



2. Select the required Ater Mux connection.

3. Right click, and select Inhibit Alarm Reporting on TC Side , Inhibit AlarmReporting on BSC Side , Allow Alarm Reporting on TC Side , or AllowAlarm Reporting on BSC Side from the popup menu.

24 / 56 3BK 21206 AAAA PCZZA Ed.06


2.13 Inhibit / Allow Alarm Reporting on MFS TPTo inhibit or allow alarm reporting on an MFS TP without interrupting traffic:

1. In the MFSUSM main window, click on the [ Ater supervision ] tab.

2. Select the required TP.

3. Select Supervise -> Inhibit Alarm Reporting or Supervise ->AllowAlarm Reporting as required.

2.14 Lock A Channel Support ResourceTo lock an A Channel support resource:

1. In the BSSUSM: Main View window, click on the [ BSS ] icon in theFunctional Alarm Synthesis panel.

2. In the GSM Functional View panel, select [ ACH Synthesis ].

3. Right click, and select ACH Synthesis from the popup menu.

The AChannels Panel window opens.

4. Select the required support resource, and click on [ Lock ].

2.15 Lock AlerterWith this task you can lock a:

Basic Alerter

QoS Alerter.

2.15.1 Basic Alerter

To lock a basic alerter:

1. Open Parser, Obsynt & Alerter (OBSAL), select Basic Alerter

The Basic Alerters window opens.

2. Deselect the box next to ’Alerter Enabled’.

3. Click on [ Save ], and then on [ Exit ].

2.15.2 QoS Alerter

To lock a QoS alerter:

1. In OBSAL, select QoS AlerterThe QoS Alerters window opens.

2. Select alerter and click on [ Edit ]

3. Deselect the box next to ’QoS Alerter Enabled’.

4. Click on [ OK ], and then on [ Exit ].

2.16 Lock BoardWhen the board is Locked, telecom activity and resources supported by theboard are stopped, including alarms. Supervision of the board and relatedsupport resources are stopped.

3BK 21206 AAAA PCZZA Ed.06 25 / 56


To lock a board:

1. In the BSSUSM: Main View window, click on the required icon in theEquipment Alarm Synthesis panel.

2. In the HW Equipment View panel, select the required board.

3. Right click, and select Lock from the popup menu.

The Administrative State in the Information panel changes from Unlocked toLocked.

2.17 Lock BTS O&M CapabilityThis task locks the O&M supervision capability of BTS equipment. Themanaged object is in stand-alone mode. It can still manage telecom activitiesbut without alarm and state supervision of the OMC-R.

To lock BTS O&M capability:

1. In the BSSUSM: Main View window, click on the [ BTS Syn. ] icon in theEquipment Alarm Synthesis panel.

2. Select the required BTS in the HW Equipment View panel.

3. In the GSM Functional View panel, select the BTS.


The Administrative State in the Information panel changes from Unlocked toLocked.

2.18 Lock BSC or BTS FunctionsTo lock a BSC or a BTS function.

1. In the HW Equipment View panel of the BSSUSM: Main View window,select the required BSC or BTS.

The selected BSC or BTS appears in the GSM Functional View panel.

2. In the GSM Functional View panel, select the BSC or BTS.

3. Right click, and select Expand All from the popup menu.

4. Select the required function.


The Administrative state in the Information panel changes from Unlocked toLocked. The function is put out of service.

26 / 56 3BK 21206 AAAA PCZZA Ed.06


2.19 Lock RSL and / or N7 Support ResourceA Locked RSL and / or N7 support resource is no longer supervised or involvedin telecom activities.

2.19.1 RSL Support Resource

To lock an RSL support resource:

1. In the BSSUSM: Main View window, select the required BTS in the HWEquipment View panel.

The selected BTS appears in the GSM Functional View panel.



4. Select the required support resource.


2.19.2 N7 Support Resource (HSL or LSL)

To lock an N7 (HSL or LSL) support resource:

1. In the BSSUSM: Main View window, select the BSS in the HW EquipmentView panel.

The selected BSS appears in the GSM Functional View panel.

2. In the GSM Functional View panel, expand the N7 Synthesis tree.



2.20 Modify Alarm FilterTo modify an alarm filter:



2. Select the required sublist.

3. Select Sublist -> Modify...The Sublist Properties window opens.

4. Modify the filter attributes as required, and click on [ Apply ].

3BK 21206 AAAA PCZZA Ed.06 27 / 56


2.21 OMC-R Alarm HandlingTo navigate to the Alarm Dictionary and view corrective action on an alarm:

1. In the AS: (Current Alarms or Histo Alarms) Counter Summary window,double click on the required subset of alarms from the default set of sublists.

The Alarm Sublist window opens.

2. Select the required alarm.

3. Select Navigation -> External Application -> AlarmDictionary...

2.22 Open / Close Loop

You cannot open or close a loop on a GPRS time slot.

To check the functional status of a time slot:

1. In the BSSUSM: Main View window, select the BSS.

The BSS appears in the GSM Functional View panel.

2. Select ACH Synthesis.


The BSSUSM: AChannels Panel window opens.

4. Enter the required Ater TP identifier in the ’Tp Id’ field, and click on [ DisplayTS ].

5. Select the required time slot, and click on [ Open Loop ] or [ Close Loop ] asappropriate.

The Follow up window displays the changes.

2.23 Reset BoardThis task clears transient faults and allows recovery from deadlock situations.The processor software is reloaded and re-initialized, and the board and itsrelated support resources are returned to service.

Perform a Restart Board (Section 2.26) if you do not want the processorsoftware to be reloaded.

2.23.1 Procedure

To reset a board:



3. Right click, and select Reset from the popup menu.

2.23.2 Impact on Calls

If the board has ongoing calls, they are impacted by the reset. New callsinvolving the board are not possible until completion of the reset.

28 / 56 3BK 21206 AAAA PCZZA Ed.06


2.24 Reset EquipmentThis task clears transient faults and allows recovery from deadlock situations.The processor software is reloaded and initialized, and the equipment andrelated support resources are returned to service.

Perform a Restart Equipment (Section 2.27) if you do not want the processorsoftware to be reloaded.

2.24.1 Procedure

To reset equipment:

1. In the BSSUSM: Main View window, HW Equipment View panel, selectthe required equipment.


3. If the selected equipment is a BSC, a confirmation window opens:Do you confirm reset BSC? (all on-going calls and new calls

are lost).

Click on [ OK ].


If the equipment has ongoing calls, they are impacted by the reset. New callsinvolving the equipment are not possible until completion of the reset.

2.25 Reset BTS FunctionTo reset a function and return its related support resources to service:


2. In the HW Equipment View, select the required BTS.


3. In the GSM Functional View panel, select the required BTS.


5. Select the required BTS function.


3BK 21206 AAAA PCZZA Ed.06 29 / 56


2.26 Restart BoardThis task clears transient faults and allows recovery from deadlock situations.The processor software is not reloaded but is re-initialized, and the board andits related support resources are returned to service.

Perform a Reset Board (Section 2.23) if you want the processor softwareto be reloaded.

2.26.1 Procedure

To restart a board:



3. Right click, and select Restart from the popup menu.


If the board has ongoing calls, they are not impacted by the restart. New callsinvolving the board are not possible until completion of the restart.

2.27 Restart EquipmentThis task clears transient faults and allows recovery from deadlock situations.The processor software is not reloaded but is re-initialized, and the equipmentand its related support resources are returned to service.

Perform a Reset Equipment (Section 2.24) if you want the processor softwareto be reloaded.

2.27.1 Procedure

To restart equipment:

1. In the BSSUSM: Main View window, HW Equipment View panel, selectthe required equipment.


3. If the selected equipment is a BSC, a confirmation window opens:Do you confirm restart BSC? (all new calls are lost).

Click on [ OK ].


If the selected equipment is the BSC and there are ongoing calls, they are notimpacted by the restart. New calls involving the equipment are not possibleuntil completion of the restart.

For the restart of the BTS, there is an outage (the impacted calls are lost).

30 / 56 3BK 21206 AAAA PCZZA Ed.06


2.28 Restart BTS FunctionTo restart a function and return it and related support resources to service:

1. In the BSSUSM: Main View window, click on the [ BTS Syn. ] icon in theEquipment Alarm Synthesis.

2. In the HW Equipment View, select the required BTS.






2.29 Shut Down A Channel Support ResourceTo shut down an A Channel support resource:

1. In the BSSUSM: Main View window, click on the BSS icon in the FunctionalAlarm Synthesis panel.

2. In the GSM Functional View panel, select ACH Synthesis.



4. Enter the required Ater TP identifier in the ’TP Id’ field, and click on [ DisplayTS ].

5. Select the support resource, and click on [ Shutdown ].

The Lock Panel window opens.

6. Enter the required time (0 to 10 minutes) in the ’Wait Traffic Clear (min)’field, and click on [ OK ].

The support resource is put out of service at the required time.

2.30 Shut Down BoardWhen the board is shut down, telecom activity and resources supported by theboard are stopped. Supervision of the board and related support resources,including alarms, are stopped.

To shut down a board:



3. Right click, and select Shutdown from the popup menu.



The Control Status in the Information panel changes to Suspended. TheAdministrative State changes to Locked.

3BK 21206 AAAA PCZZA Ed.06 31 / 56


2.31 Shut Down BTS FunctionTo shut down a function:


2. In the HW Equipment View panel, select the required BTS.





6. Right click, and select Shutdown from the popup menu.



The Administrative state in the Information panel changes from Unlockedto Locked if not already locked.

2.32 Shut Down RSL Support ResourceTo shut down an RSL support resource:

1. In the BSSUSM: Main View window, click on the BTS icon in the FunctionalAlarm Synthesis panel.

2. In the GSM Functional View panel select the required BTS.



5. Right click, and select Shut Down from the popup menu.


6. Enter the required time (0 to 10 minutes) in the’ Wait Traffic Clear (min)’field, and click on [ OK ].

The RSL is put out of service at the required time.

2.33 Test Board

Perform Lock Board (Section 2.16) before testing a board.

To test a board:



3. Right click, and select Test from the popup menu.

The Test / Verify window opens and displays the test results.

32 / 56 3BK 21206 AAAA PCZZA Ed.06


2.34 Unlock A Channel Support ResourceTo unlock an A Channel support resource:


2. In the GSM Functional View, select ACH Synthesis .



4. Enter the required Ater TP identifier in the ’TP Id’ field, and click on [ DisplayTS ].

5. Select the support resource, and click on [ Unlock ].

2.35 Unlock AlerterWith this task you can unlock a:

Basic Alerter

QoS Alerter.

2.35.1 Basic Alerter

To unlock a basic alerter:

1. Open Parser, Obsynt & Alerter (OBSAL) and select Basic AlerterThe Basic Alerters window opens.

2. Select the box next to [ Alerter Enabled ].

3. Click on [ Save ], and then on [ Exit ].

2.35.2 QoS Alerter

To unlock a QoS alerter:

1. In OBSAL, select QoS AlerterThe QoS Alerters window opens.

2. Select alerter and click on [ Edit ].

3. Select the box next to [ QoS Alerter Enabled ].

4. Click on [ OK ], and then on [ Exit ].

2.36 Unlock BoardTo unlock a board and return its related support resources to service:



3. Right click, and select Unlock from the popup menu.

3BK 21206 AAAA PCZZA Ed.06 33 / 56


2.37 Unlock BTS O&M CapabilityTo unlock the O&M supervision capability of BTS equipment:


2. In the HW Equipment View panel, select the required BTS.



The Administrative state in the Information panel changes from Lockedto Unlocked.

2.38 Unlock BSC or BTS FunctionsThis task explains how to unlock a BSC or BTS function and return it to service.

1. In the HW Equipment View panel of the BSSUSM: Main View window,select the required BSC or BTS.

The selected BSC or BTS appears in the GSM Functional View panel.

2. In the GSM Functional View panel, select the BSC or BTS.


4. Select the required function.


The Administrative state in the Information panel changes from Lockedto Unlocked.

2.39 Unlock RSL, N7 Support Resource

2.39.1 RSL

To unlock an RSL support resource:

1. In the BSSUSM: Main View window, click on the [ BTS ] icon in theFunctional Alarm Synthesis panel.





2.39.2 N7 (HSL or LSL)

To unlock an N7 support resource:


2. In the GSM Functional View, expand the N7 Synthesis tree.



34 / 56 3BK 21206 AAAA PCZZA Ed.06


2.40 Verify BoardTo verify the operational state of a board:



3. Right click, and select Verify from the popup menu.



The Test / Verify window opens and displays the verification results.

2.41 View Status of Managed Objects and AlarmsYou can access all these reports through the BSSUSM: Main View window.

The following scenario tells you how to display managed objects and alarmreports on the:

BSS

X.25 (Only for 9120 BSC)

N7 (HSL or LSL)

ACH

BSC

Active Telecom SSW

BTS

Abis and Ater links

TC.

2.41.1 BSS

To display managed objects and alarm reports on the BSS:

1. In the HW Equipment View panel, select the BSS.


3. Re-select the BSS, right click, and select Report from the popup menu.

The HW Equipment View window opens, showing a report listing the statusof the BSC, TC, and BTS boards.


5. Right click, and select Show Alarms from the popup menu.

The AS Current USM: Counter Summary and the AS Current USM: AlarmSublist windows open, showing reports on the counters and alarms.

3BK 21206 AAAA PCZZA Ed.06 35 / 56


2.41.2 X.25 (Only for 9120 BSC)

To display a report on the X.25, disc and functions:

1. In the HW Equipment View panel, select the required BSC.

2. In the GSM Functional View, double click on the BSC name.

The tree expands, showing the X.25, discs, tr_om, and additional functions.

In the ’Information’ panel, check the ’Operational State’ and ’AvailabilityStatus’.

3. Right click on the BSC name, and select Report from the popup menu.

A report on the status of the X.25, discs, tr_om and additional functionsappears.

2.41.3 N7 (HSL or LSL)

To display a report on N7 resources:


2. In the GSM Functional View panel, expand the N7 Synthesis tree.

3. Select the required N7.



2.41.4 ACH

To display a report on the ACHs:


2. In the GSM Functional View panel, select ACH Synthesis.



4. Enter the Termination Point identification number in the ’Tp Id’ field, and clickon [ Display Ts ].

5. Click on [ Report ].

The AChannels Panel window opens, showing a report on the status ofthe ACHs from the selected TP.

36 / 56 3BK 21206 AAAA PCZZA Ed.06


2.41.5 BSC

To display reports for the BSC:

1. In the Equipment Alarm Synthesis panel, click on the [ BSC ] icon.

2. Right click, and select Expand All from the popup menu (if needed).

3. In the HW Equipment View panel, select the BSC, right click, and selectReport from the popup menu.

The HW Equipment View window opens, showing a report on the statusof the BSC boards (resources).

4. In the HW Equipment View panel, select the required BSC, right click, andselect Show Alarms from the popup menu.


2.41.6 Active Telecom SSW

To view the active telecom SSW

1. In the Equipment Alarm Synthesis panel, click on the [ BSC ] icon.


If the active JBMUX is in slot 10, then the active telecom SSW is in slot 7

If the active JBMUX is in slot 12, then the active telecom SSW is in slot 8

2.41.7 BTS

To display reports for the BTS:

1. In the Equipment Alarm Synthesis panel, click on the [ BTS Syn. ] icon.


3. In the HW Equipment View panel, select the required BTS, right click, andselect Report from the popup menu.

The HW Equipment View window opens, showing a report on the statusof the BTS boards.

4. In the HW Equipment View panel, select the required BTS, right click, andselect Show Alarms from the popup menu.


3BK 21206 AAAA PCZZA Ed.06 37 / 56


2.41.8 Abis

To display reports for the Abis link:

1. In the Functional Alarm Synthesis panel, click on the [ Abis ] icon.

The Abis Topology View window opens.

2. Select the BSC.

For 9120 BSC 3. Right click, and select Tcu Load Report from the popup menu.

The Tcu Load Report window opens, showing a report on the status of theBSC’s TSU.

For 9130 BSC Evolution 4. Right click, and select Display CCP Resources Usage or Display AbisResources Usage from the popup menu.

The CCP Resources Usage / Abis Resources Usage window opens,showing a report on the status of the BSC (CCPs / declared Abis).

In the Abis Topology View window, select the required Abis.

5. In the Abis Topology View window, select the required TSU (only for 9120BSC) or Abis.



2.41.9 Ater

To display reports for the Ater link:

1. In the Functional Alarm Synthesis panel, click on the [ A / Ater ] Mux icon.


2. Select the required Ater Mux Connection.



2.41.10 TC

To display reports for the TC:

1. In the Equipment Alarm Synthesis panel, click on the TC icon.


3. In the HW Equipment View panel, select the TC, right click, and selectReport from the popup menu.

The HW Equipment View window opens, showing a report on the statusof all TC boards.

4. In the HW Equipment View panel, select the TC, right click, and selectShow Alarms from the popup menu.


38 / 56 3BK 21206 AAAA PCZZA Ed.06

3 Performance Management


This section describes how to manage standard and detailed counters.

3BK 21206 AAAA PCZZA Ed.06 39 / 56


3.1 IntroductionPerformance management provides measurements and statistics about varioustraffic events and resource use in the BSS, based on counters or parameterswhich are located in the BSC. These counters and parameters of the BSC aretransferred to the OMC-R during each reporting period. There are two differenttypes of performance measurement counters:

Standard counters

Detailed counters.

Standard counters are global. They provide an overview of the network, forexample, A-interface measurements. Detailed counters are analytical. Theyanalyze a particular occurrence, for example, internal handovers. The operatormust define a list of Standard and Detailed measurement counters. This isdone respectively in:

PMC

ODMC.

For detailed descriptions of counter types and indicators, refer to PM Counters.

40 / 56 3BK 21206 AAAA PCZZA Ed.06


3.2 Standard CountersStandard counters are used in the PMC. PMC reports occur at 30 or 60 minuteintervals for a maximum of 24 hours. The following table describes thestandard counters.

Measurement Type Object Observed

7: LapD Per BSC

8: X.25 Per BSC

9: N7 Per BSC

18: A Interface Per BSC

19: SMS PP Per cell

25: SCCP Per BSC

28: SDCCH HO Per cell

29: Directed retry Per cell

30: SMS CB Per BSC

31: RMS Per cell

32: Change of frequency band Per BSC

33: EME Per cell

34: Voice Group Call Services Per cell

110: Overview Per BSC

180: Traffic flow Per BSC

The tasks related to managing PMCs are:

Define PMC List (Section 4.8)

Lock PMC (Section 4.21)

Modify PMC (Section 4.25)

Unlock PMC (Section 4.33).

3BK 21206 AAAA PCZZA Ed.06 41 / 56


3.3 Detailed CountersDetailed counters or non-selected standard counters analyze particularoccurrences in the ODMC. They run during a predefined interval between twodates. The following table describes the detailed counters.


1: Traffic Per cell

2: Resource availability Per cell

3: Resource use on CCCH Per TRX_TS of a cell

4: Resource use on SDCCH Per TRX_TS of a cell

5: Resource use on TCH Per TRX_TS of a cell

6: TCH HO Per cell

7: LapD Per BSC

8: X.25 Per BSC

9: N7 Per BSC

10: SDCCH Per cell

11: TCH measurement observations Per cell

12: Internal HO Per cell

13: Incoming external HO Per cell

14: Outgoing external HO Per cell

15: TCH Per cell

18: A Interface Per BSC

19: SMS PP Per cell

21: BSC load Per BSC

25: SCCP Per BSC

26: TCH outgoing HO per adjacency Per cell

27: TCH incoming HO per adjacency Per cell

28: SDCCH HO Per cell

29: Directed Retry Per cell

30: SMS CB Per BSC

42 / 56 3BK 21206 AAAA PCZZA Ed.06



31: RMS Per BSC

32: Change of frequency band Per BSC

ODMCs cannot share the same raw measurement types at the same time.

Note Detailed counters cannot be used in a PMC list. Also, the same measurementtype cannot be used in a PMC list and an ODMC list at the same time. Tasksrelated to managing ODMCs are:

1. Create ODMC (Section 4.6)

2. Delete ODMC (Section 4.9)

3. Lock ODMC (Section 4.20)

4. Modify ODMC (Section 4.24)

5. Query ODMC (Section 4.28)

6. Unlock ODMC (Section 4.32).

3BK 21206 AAAA PCZZA Ed.06 43 / 56


44 / 56 3BK 21206 AAAA PCZZA Ed.06

4 Performance Management Tasks


This section describes PMC and ODMC management tasks.

3BK 21206 AAAA PCZZA Ed.06 45 / 56


4.1 Activate BSC AlerterTo activate a BSC alerter:

1. In the BSSUSM: Main View window, select Performance -> BSC Alerter-> Configure.

The BSC Alerter Configuration window opens.

2. Select the alerter to activate in the ’Functions’ field.

3. Click on [ Activate ].

The alerter status is changed to Activated in the ’Functions’ field.

4.2 Audit BSC Alarms and Administrative StateThis task performs a check between the OMC-R and the BSC, BTS, and BSS.The network element updates the OMC-R with the current administrativestate and alarms.

To audit the administrative state and alarms:

1. In the BSSUSM: Main View window, select the required BSS, BSC, or BTS.

2. Right click, and select Alarm / State Audit from the popup menu.

4.3 Audit PMThis task checks for alignment and consistency between performancemeasurement campaigns at the OMC-R and BSC. The areas of non-alignmentand inconsistency, and the corrective action, are displayed in the Audit Resultwindow.

To audit PM:

1. In the BSSUSM: Main View window, select Performance -> Campaigns.

The BSSUSM: Campaigns Supervision window opens.

2. (Optional) Create a filter by completing the fields in the Filter parameterspanel, and click on [ Search ].

The filtered information appears in the BSSUSM: Campaigns Supervisionwindow.

3. Click on [ Audit ].

4.4 Audit TraceThis task performs a check between the OMC-R and the BSC. The BSCupdates the OMC-R with the current data of the administrative state and thetrace timer value of the IMSI trace control.

To audit traces, in the BSSUSM: Main View window, select Audit -> BSCTraces Audit.

46 / 56 3BK 21206 AAAA PCZZA Ed.06


4.5 Copy RMS BSC TemplateTo copy the parameters from a source RMS BSC template to a target RMSBSC template:

1. In the RNUSM: PRC main window, select General -> Merge RMS Template.

The Merge RMS Template window opens.

2. (Optional) In the Source RMS Template panel, select a filter.

3. Select a BSC from the BSC Name list.

A list of the RMS templates associated with the BSC opens.

4. Select the required template.

5. (Optional) In the Target RMS Template panel, select a filter.

6. Select the target template, and click on [ Apply ].

4.6 Create ODMCTo create a new ODMC:

1. In the BSSUSM: Main View window, select Performance -> ODMC.

The BSSUSM: ODMC Definition window opens.

2. Enter a new campaign name in the ’Campaign Name’ field.

3. Click on [ Network Elements ].

The Network Elements List window opens.

4. Select the required network element(s), and click on [ OK ].

5. Click on [ Raw Types ].

The Raw Types List window opens.

6. Select the required raw type(s), and click on [ OK ].

7. Complete the fields in the Date and Time parameters panel, and clickon [ Create ].

Note: If you select an ODMC campaign and an accumulation period of 15 minutes,and click on [ Create ], you receive a warning message because with suchparameters, it is not possible to store all indicators in the table. The operatoris warned that the indicators table of the 9159 NPO is not available for morethan 12 hours, if the accumulation period is 15 minutes. You can choose tochange the accumulation period but it is not obligatory.

The OMC-R authorizes the scheduling of several ODMC type 31 (RMS) jobsper day, but only the last period results are stored in the MPM / 9159 NPOdatabases.

The date must be entered as a four-digit year, two-digit month, two-digit day.For example: 2001/02/23.

8. Click on [ Close ].

9. Go to Unlock ODMC (Section 4.32) to start the ODMC.

Note: Type 110 and type 33 are not allowed.

3BK 21206 AAAA PCZZA Ed.06 47 / 56


4.7 De-activate BSC AlerterTo de-activate a BSC alerter:



2. In the Functions panel, select the required alerter.

3. Click on [ De-activate ].

4.8 Define PMC ListThis task defines the list of permanent raw types. If a raw type is not used as apermanent raw type, it can be used as an on-demand raw type.

Note: If you select [Cell] Radio Measurement Statistics from the Available RawTypes list, you must specify the start and end times in the ’Interval 3’ fields.

Only counters with scope BSC can be included in a PMC.

To define a PMC list:

1. In the 9153 OMC-R Unique Function Management main window, click on[ PMC ].

The Permanent Measurement Campaign window opens.

2. Complete the fields in the Change Campaign Characteristics panel, andclick on [ Apply ].

4.9 Delete ODMC

Perform Lock ODMC (Section 4.20) before deleting an ODMC and all relatedinformation from the OMC-R.

To delete an ODMC:



2. Click on [ Search ].

The current campaigns are displayed.

3. Select the required ODMC, and click on [ Delete ].


48 / 56 3BK 21206 AAAA PCZZA Ed.06


4.10 Display Cell ReportTo open the Cell Parameters window and display a report on the parametersof a given cell:

1. In the RNUSM: PRC or SC main window, select the required cell.

2. Right click, and select Edit... from the popup menu.

The Edit Cell window opens.


If the internal processing of the BSC is overloaded, the values of the cellare set to 0!

4.11 Display Cell List ReportTo open the Matrix Report window and display a report on the main parametersof a cell list:

1. In the RNUSM: PRC or SC main window, select a filter in the matrix panel.


4.12 Display MFS ReportTo display a global report on the Gb interface, including GPU status, links,alarms and administrative state:

1. In the MFSUSM main window, select the required GPU.

2. Select Configure -> GB.

The GB Configuration window opens.

3. Select Views -> Global Report...

For a global view on Ater and Gb interfaces, in MFSUSM main window, selectViews -> Global Report...

For a detailed image on the TPs:

In the MFSUSM main window, select the desired TP in Ater or Gb

supervision window

Select Views ->Report on selected TP.

4.13 Display USD A Interface OverviewTo open the USD A Interface window and display an overview of BSSinformation:

1. In the BSSUSM: Main View window, select USD -> USD A Interface.

The USD A Interface window opens.

2. To close the window, click on [ Close ].

3BK 21206 AAAA PCZZA Ed.06 49 / 56


4.14 Display USD A DTC BoardTo display a USD A DTC related board:



2. Select the required DTC in the DTC Information panel, and select Showequipment.

The related board is highlighted in the HW Equipment panel in theBSSUSM: Main View window.

If the internal processing of the BSC is overloaded, the values of the DTCare set to 0!

4.15 Display USD Cell OverviewTo display an overview of cell information:

1. In the BSSUSM: Main View window, select USD -> USD Cell Overview.

The USD Cell Overview window opens.



4.16 Display USD Detailed Cell InformationTo open the Cell Report window and display detailed cell information:



2. Select the required cells from the ’Cell Information’ field, and click on [ CellReport ].



50 / 56 3BK 21206 AAAA PCZZA Ed.06


4.17 Display USD Detailed DTC InformationTo open the DTC Report window and display detailed DTC information:



2. Select the required DTCs from the DTC Information panel, and clickon [ DTC Report ].



4.18 Edit RMS BSC TemplateAn RMS BSC template is a model in which you select radio measurementstatistic parameters to be applied to BSCs. You can edit up to 16 differenttemplates, or you can edit one template and apply it to several BSCs, asdescribed in Copy RMS BSC Template (Section 4.5).

RMS BSC templates can only be edited in a PRC.

To edit an RMS BSC template:

1. In the RNUSM: PRC main window, select the required BSC.

2. Right click, and select a template from Edit RMS Template in the popupmenu.

The Edit RMS Template Parameters window opens.

3. Modify the parameters in each view as required, and click on [ Apply ].

4.19 Lock / Shut Down IMSI TraceTo lock or shut down an IMSI trace:

1. In the BSSUSM: Main View window, select Trace -> IMSI TraceManagement.The IMSI Trace Control Parameters window opens.

2. Click on [ Lock ] or [ Shutdown ] as appropriate.


4.20 Lock ODMCTo suspend the recording of ODMC for one or several BSSs:



2. In the ’Administrative State’ field, select Unlocked, and click on [ Search ].

The unlocked ODMCs appear in the ’Results’ field.

3. Select the required ODMC, and click on [ Lock ].


3BK 21206 AAAA PCZZA Ed.06 51 / 56


4.21 Lock PMCTo suspend recording of the PMC for one or more BSSs:



2. In the ’Administrative State’ field, select Unlocked, and click on [ Search ].

The unlocked PMCs appear in the ’Results’ field.

3. Select the required PMC, and click on [ Lock ].


4.22 Modify BSC AlerterThis task modifies the parameters of a specified BSC alerter for one BSS ora set of cells. The previous alarms related to the designated BSC alerterare cleared.

To modify a BSC alerter:



2. Change the required parameters in the ’Alerter Parameters’ field, andclick on [ Modify ].

4.23 Modify IMSI Trace Control ParametersTo modify the IMSI trace control parameters for all the IMSI traces of the BSS:


2. Change the required parameters, and click on [ Modify ].


52 / 56 3BK 21206 AAAA PCZZA Ed.06


4.24 Modify ODMC

You must first Lock ODMC (Section 4.20) before modifying an ODMC.

To modify an ODMC on one BSS:



2. Click on [ Search ].

3. From the Campaign name panel, select the ODMC to be modified.

4. Click on [ Config ].

The BSSUSM: ODMC Definition window opens.

5. Modify the ODMC parameters as required.

Note: If you select an ODMC campaign and an accumulation period of 15 minutes,and click on [ Create ], you receive a warning message because with suchparameters, it is not possible to store all indicators in the table. The operator iswarned that the indicators table of 9159 NPO is not available for more than 12hours, if the accumulation period is 15 minutes. You can choose to changethe accumulation period but you are not obliged to.

The OMC-R authorizes the scheduling of several ODMC type 31 (RMS) jobsper day, but only the last period results are stored in the MPM / 9159 NPOdatabases.

The date must be entered as a four-digit year, two-digit month, two-digit day.For example: 2001/02/23.

6. Click on [ Modify ].

The ODMC is modified.


3BK 21206 AAAA PCZZA Ed.06 53 / 56


4.25 Modify PMCThis task modifies the raw types, granularity period, or interval times in PMCs.The modified values are displayed in the Current Campaign panel.

Note: You must:

Specify the start and end times in the ’Interval 3’ fields if you select [Cell]Radio Measurement Statistics from the Available Raw Types list

Set the start time to 0:00 local time for T180 Type and all other counters

having a granularity period of more than 1 hour.

To modify a PMC:

1. In the 9153 OMC-R Unique Function Management main window, click on[ PMC ].

The Permanent Measurement Campaign window opens.

2. Modify the values as required in the Change Campaign Characteristicspanel, and click on [ Apply ].

4.26 Query BSC AlerterTo open the BSC Alerter Overview window and see a list of the alerters runningin the BSC, in the BSSUSM: Main View window, select Performance ->BSC Alerter -> Overview.

4.27 Query BSC TracesTo open the BSC Traces Overview window and see a list of IMSI tracesrunning in the BSC, in the BSSUSM: Main View window, select Trace -> BSCTraces Overview.

4.28 Query ODMCTo display the ODMC characteristics of a BSS:



2. Create a filter by completing the fields in the Filter parameters panel, andclick on [ Search ].

The ODMC parameters are displayed in the ’Results’ field.


54 / 56 3BK 21206 AAAA PCZZA Ed.06


4.29 Stop / Start USD Cell Overview RefreshThis task stops or starts the refreshing periods of the USD Cell Overview.When you select Stop Refresh, all data on the screen is frozen. When youselect Restart Refresh, the screen is refreshed periodically.

To stop / start a USD cell overview refresh:



2. Click on [ Stop Refresh ] or [ Restart Refresh ] as required.

3. Click on [ Close ] to exit the USD Cell Overview window.

4.30 Stop / Start USD A Interface RefreshThis task stops or starts the refreshing period of the USD A Interface overview.When you select Stop Refresh, all data on the screen is frozen. When youselect Restart Refresh, the screen is refreshed periodically.

To stop / start a USD A interface refresh:



2. Click on [ Stop Refresh ] or [ Restart Refresh ] as required.

3. Click on [ Close ] to exit the USD A Interface window.

4.31 Unlock IMSI TraceTo unlock an IMSI trace:


2. Click on [ Unlock ].


3BK 21206 AAAA PCZZA Ed.06 55 / 56


4.32 Unlock ODMCThis task starts or restarts the recording of on-demand counters for one orseveral BSSs.

You must first Create ODMC (Section 4.6) before you can start or restartrecording.

To unlock an ODMC:




The defined campaigns appear in the Campaign name panel.

3. Select the required campaign, and click on [ Unlock ].


4.33 Unlock PMCTo start or restart the recording of permanent PM counters for one or severalBSSs:




3. The defined campaigns appear in the Campaign name panel.

4. Select the required PMC, and click on [ Unlock ].


56 / 56 3BK 21206 AAAA PCZZA Ed.06

212060000 e 06

Documents

alarm reporting

alarm filter

alarm acknowledgement

alarm management91

alarm sublist

alarm customization

alarm management tasks

hal alarm processes121