OMC R Supervision

9153 OMC-R BSS
LR14.G Supervision
Student Guide
TMO60034_V4.0-SG Edition 1
COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.
Passing on and copying of this document, use and communication of its

contents not permitted without written authorization from Alcatel-Lucent
Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

Terms of use and legal notices
Switch
TERMS OFto
USEnotes view!
AND LEGAL NOTICE
Alcatel-Lucent provides this training course to you subject to these Terms of Use and Legal Notice. Your use of this training
course and/or this site constitutes your acceptance of and agreement to these Terms of Use and Legal Notice. These
Terms of Use and Legal Notice, as well as the contents of this training course, may be updated or amended by Alcatel-
Lucent from time to time without prior notice to you. Your use of the Alcatel-Lucent training materials after such update
or amendment constitutes your acceptance of and agreement to said updated or amended Terms of Use and Legal Notice.
SAFETY WARNING
Alcatel-Lucent training materials can be for products or refer to products that have both lethal and dangerous voltages
present. Always observe all safety precautions and do not work on the equipment alone. The user is strongly advised not
to wear conductive jewelry while working on the products. Equipment referred to or used during this course may be
electrostatic sensitive. Please observe correct anti-static precautions.
PERMISSION TO USE CONTENT

The information, communications, scripts, photos, text, video, graphics, music, sounds, images and other materials
provided in this training course (collectively the "Content"), is intended for the lawful use of employees of Alcatel-Lucent
and other authorized participants in this Alcatel-Lucent training course. You are hereby granted a non-exclusive, non-
transferable permission to access and use the Content solely for your personal training and non-commercial use. This
permission may be terminated by Alcatel-Lucent at any time for any reason or no reason, with or without notice. You must
immediately cease use of the Content upon such termination.
COPYRIGHTS AND TRADEMARKS

The unauthorized copying, displaying or other use of any Content from this training course is a violation of the law and
Alcatel-Lucent’s corporate policies. The Content is protected in France, the U.S. and other countries by a variety of laws,
including but not limited to, copyright laws and treaty provisions, trademark laws, patent laws and other proprietary rights
laws (collectively, "IP Rights"). In addition to Alcatel-Lucent’s IP Rights in the Content, in part and in whole, Alcatel-Lucent,
and any of the third parties who have licensed and/or contributed to the Content, owns a copyright in the formatting and
presentation of the Content.
Alcatel-Lucent does not grant you any permission to use the Content other than the permission expressly stated in these
Terms of Use and Legal Notice. All other use of Content from this training course, including, but not limited to,
modification, publication, transmission, participation in the transfer or sale of, copying, reproduction, republishing,
2 creation of derivative works from, distribution, performance,
COPYRIGHT © ALCATEL-LUCENTdisplay, incorporation
2015. ALL RIGHTS RESERVED. into another training course or
presentation,
9153 OMC-R BSS
LR14.G Supervision
or in any other way exploiting any of the Content, in whole or in part, for uses other than those expressly
permitted herein is strictly prohibited and shall not be made without Alcatel-Lucent’s prior written consent. All characters
appearing in this training course are fictitious. Any resemblance to real persons, living or dead, is purely coincidental.
There may be a number of proprietary logos, marks, trademarks, slogans and product designations found in the
Content. Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logos are trademarks of Alcatel-Lucent. All other
trademarks are the property of their respective owners. Alcatel-Lucent does not grant you a license to use any of the
foregoing logos, marks, trademarks, slogans and product designations in any fashion. Granting of the right to access and
use the Content for training purposes does not confer upon you any license under any of Alcatel-Lucent’s or any third
party's IP Rights.
DISCLAIMER
ALCATEL-LUCENT DISCLAIMS ALL WARRANTIES REGARDING THE TRAINING COURSES OR THE CONTENT, EXPRESS OR IMPLIED,
INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. THE ALCATEL-LUCENT WILL NOT BE RESPONSIBLE OR LIABLE FOR ANY INJURY, LOSS, CLAIM, DAMAGE, OR ANY
SPECIAL, EXEMPLARY, PUNITIVE, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING WITHOUT
LIMITATION LOSS PROFITS OR LOSS SAVINGS), WHETHER BASED IN CONTRACT, TORT, STRICT LIABILITY OR OTHERWISE, THAT
ARISES OUT OF OR IS IN ANY WAY CONNECTED WITH (A) ANY USE OR MISUSE OF THE CONTENT OR THE TRAINING COURSES
BY YOU, OR (B) ANY FAILURE OR DELAY BY ALCATEL-LUCENT, ITS OFFICERS, DIRECTORS, AGENTS OR EMPLOYEES IN
CONNECTION WITH THE CONTENT OR THE TRAINING COURSES (INCLUDING, WITHOUT LIMITATION, THE USE OF OR INABILITY
TO USE ANY COMPONENT OF THE CONTENT OR TRAINING BY YOU). SOME JURISDICTIONS LIMIT OR PROHIBIT SUCH
EXCLUSION OF WARRANTIES OR LIMITATION OF LIABILITIES AND SO THE FOREGOING EXCLUSION OF WARRANTIES OR
LIMITATION OF LIABILITY MAY NOT APPLY TO YOU.
GOVERNING LAW
These Terms of Use and Legal Notice are governed by the laws of France. The operation and use of the training course is
governed by the laws of the country that governs your employment contract, if applicable. If any provision of these Terms
of Use and Legal Notice, or the application thereto to a person or circumstance, is held invalid or unenforceable by law,
statute or a court of competent jurisdiction, for any reason, then such provision shall be modified and/or superseded by a
provision that reflects the intent of the original provision as closely as possible. All other provisions of these Terms of Use
and Legal Notice shall remain in full force and effect. You may not assign these Terms of Use or any permission granted
hereunder without Alcatel-Lucent’s prior written consent. Nothing herein shall be deemed an employment agreement or
an offer of employment or an alteration in any way of a user’s terms of employment with or within Alcatel-Lucent.
Copyright © 2013 Alcatel-Lucent. All Rights Reserved

Course outline
1. 9153 OMC-R
Welcome BSS LR13.G
to 9153 OMC-RSupervision
BSS
1. OMC-RSupervision
LR14.G BSS Supervision
2. Abbreviations and Acronyms
1. 9153 OMC-R BSS LR13.G Supervision
1. OMC-R BSS Supervision
2. Abbreviations and Acronyms
3 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

9153 OMC-R BSS
LR14.G Supervision

Course objectives
 9153
Upon OMC-R BSS
completion of this course, you should be able to:
LR14.G Supervision
 Understand the general O&M principles
 Understand the SBLs and the Managed Object states
 Identify the hardware
Upon completion of thisand functional
course, structure
you should be ableof
to:a BSS
 Check the topology of a BSS
 Handle the BSS files
 Check the BSS
Understand thesoftware
general O&M principles
 Handle performance
Understand the SBLs and measurement
the Managed campaigns
Object states
 Check the telecom resources
Identify
 Check theconfiguration
the hardware andof functional
the MFSsstructure of a BSS
 Check
Check the logical parameters
the topology of a BSS of the BSCs and of the radio cells
 Manage the current
Handle the BSS files alarms
 Create alarm filters
Check the
 Manage theBSS softwarealarms
historical
 Configure the alarmmeasurement
Handle performance filters campaigns
 Check the telecom resources
 Check the configuration of the MFSs
 Check the logical parameters of the BSCs and of the radio cells
 Manage the current alarms
 Create alarm filters
4
 Manage the historical alarms
9153 OMC-R BSS
LR14.G Supervision
 Configure the alarm filters
Your feedback is appreciated!

Please feel free to Email your comments to:
training.feedback@alcatel-lucent.com
Please include the following training reference in your email:

Thank you!

Learning experience powered by
Alcatel-Lucent University
Section 1
9153 OMC-R BSS LR13.G Supervision
Module 1
OMC-R BSS Supervision
TMO60034_V4.0-SG-LR14.G-Ed1 Module 1.1 Edition 1
9153 OMC-R BSS
LR14.G Supervision
1·1·1 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

9153 OMC-R BSS LR13.G Supervision · OMC-R BSS Supervision
9153 OMC-R BSS · LR14.G Supervision

Section 1 · Module 1 · Page 1
Blank page

9153 OMC-R BSS · LR14.G Supervision This page is left blank intentionally.
Document History
Edition Date Author Remarks
01 2015-12-05 Goel, Vibhor Update to release LR14.G

Module objectives
Upon completion of this module, you should be able to:
 Describe the general O&M principles

 Describe the SBLs and the Managed Object states
 Identify the hardware and functional structure of a BSS
 Check the topology of a BSS
 Handle the BSS files
 Check the BSS software
 Handle performance measurement campaigns
 Check the telecom resources
 Check the configuration of the MFSs
 Check the logical parameters of the BSCs and of the radio cells
 Manage the current alarms
 Create alarm filters
 Manage the historical alarms
 Configure the alarm filters


Module objectives [cont.]


Table of Contents
1 Introduction Page 7
2 BSS supervision
1 Introduction 7
24
3 MFS supervision
1.1 Operation & maintenance principles 8 58
1.2 Operation & maintenance sub-system 9
4 Radio network supervision
1.3 Fault management processing 10 77
1.4 SBL and RIT definition (internal BSC/BTS view) 12
5 Current1.5Alarm List (CAL)
SBL states 13 100
6 Historical Alarmsobject
1.6 Managed Listdefinition
(HAL) (OMC-R view) 15 127
1.7 Managed object states 16
7 New features
1.8 SBL andfor supervision
managed inmapping
object state LR13.G 17 143
1.9 Connection to the OMC-R 18
1.10 Icon box of the OMC-R 20
1.11 Generic customer documentation 21
1.12 Exercise: Connecting to OMC - R 23
2 BSS supervision 24
2.1 BSSUSM icon & controller 25
2.2 BSSUSM main window 26
2.2.1 Exercise: BSSUSM 28
2.3 TC supervision 29
2.4 BSC supervision 30
2.4.1 Hardware/functions relationships for the BSC 31
2.4.2 Exercise: BSC and TC 33
2.4.3 Actions through the right-click menu 34
2.4.4 Exercise: Action on BSC board 36
2.4.5 Alarm reporting on the Abis 37
1·1·5
9153 OMC-R BSS LR13.G2.4.6
SupervisionFile management
· OMC-R BSS Supervision for theCOPYRIGHT
BSS© ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED. 38
2.4.7 Software management for the BSS 39
2.4.8 Exercise: File and software management 40
2.5 BTS supervision 41
2.5.1 Hardware/functions relationships for the BTS 42
2.5.2 Navigation from BTS to Abis 44
2.5.3 Navigation from sector to cell 45
2.5.4 BTS view 46
2.5.5 Exercise: BTSs and cells 47
2.6 Supervision of performance measurement campaigns 48
2.6.1 Permanent Measurement Campaign (PMC) 49
2.6.2 On-Demand Measurement Campaign (ODMC) 50
2.6.3 Management of measurement campaigns 51
2.7 Usage State on Demand (USD) 52
2.7.1 USD cell overview 53
2.7.2 USD at A interface 55
2.7.3 Exercise: USD 57
3 MFS supervision 58
3.1 MFSUSM icon & controller 59
3.2 MFSUSM – Ater supervision 60
3.2.1 Exercise: MFSUSM 61
3.3 Ater configuration 62
3.4 Ater navigation 63
3.4.1 Exercise: Atermux links to MFS 64
3.5 MFSUSM – Gb supervision 65
3.5.1 Gb configuration 66
3.5.2 Exercise: Gb 68
3.6 Configuration of links 69
3.7 Navigation to the IMT 71
3.7.1 IMT view menu 72
3.7.2 IMT site view 73

Table of Contents [cont.]
Page
3.7.3 IMT front view 74

3.7.4 IMT tools menu 75
3.7.5 Exercises: IMT 76
4 Radio network supervision 77
4.1 RNUSM icon 78
4.2 RNUSM main window 79
4.2.1 Matrix browser 80
4.2.2 Exercises: Matrix browser 82
4.2.3 Tree browser 83
4.2.4 Symbols in RNUSM 85
4.2.5 More states 87
4.3 Additional filters in RNUSM external 3G cells window 88
4.4 Follow-up window of the OMC-R 89
4.5 Cell filters in RNUSM 90
4.6 BTS filters in RNUSM 92
4.7 BSS parameters 94
4.8 Cell parameters 95
4.9 Search function of RNUSM 97
4.10 Exercises: Cell and BTS filtering 99
5 Current Alarm List (CAL) 100
5.1 Fault Management (FM): Current alarms icon 101
5.2 Current alarms list 102
5.2.1 Actions on current alarms 103
5.2.2 Navigation from CAL to the alarm dictionary 104
1·1·6
9153 5.2.3
OMC-R BSS Navigation from
LR13.G Supervision · OMC-R RNUSM to CAL COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.
BSS Supervision 106
5.2.4 Navigation from BSSUSM to CAL 107
5.2.5 Navigate from CAL to the related equipment 108
5.2.6 Exercises: CAL 110
5.3 Alarm sublists 111
5.3.1 Create an alarm sublist 112
5.3.2 Modify an alarm sublist 114
5.3.3 Create an alarm filter 116
5.3.4 Add an alarm filter criterion 117
5.3.5 Apply the alarm filter 118
5.3.6 “Not Superset of” filter 119
5.3.7 “Null intersection” filter 122
5.3.8 Exercises: “Null intersection” filter 126
6 Historical Alarms List (HAL) 127
6.1 Fault management (FM): Historical alarms icon 128
6.2 Navigation from CAL to HAL 129
6.3 Retrieve historical alarms 130
6.3.1 Create an alarm filter 131
6.3.2 Add an alarm filter criterion 132
6.3.3 Define the alarms retrieval date and time 133
6.3.4 Apply the alarm filter 134
6.3.5 Pagination view 135
6.3.6 No pagination view 136
6.3.8 Save alarms 137
6.3.9 Retrieve saved alarms 138
6.4 Save clear alarm in HAL when corresponding active alarm is not in CAL 140
6.5 Exercises: HAL 142
7 New features for supervision in LR13.G 143
7.1 Confirmation dialog for risky operations 144
7.1.1 List of risky commands 145
7.1.2 Example of a confirmation dialog box 146
7.2 OMC-R function and security: Logs improvement 147
7.2.1 Logs improvement 148
7.3 Exercises: New features 149

1 Introduction


1 Introduction
1.1 Operation & maintenance principles
BSS
BTS TC
terminal terminal
BSC
terminal
A
Ater
Mux TC MSC
Abis
BSC
BTS
BSC Gb
BTS MFS
SGSN
PCU
OMC-R IMT

Every equipment has its own local maintenance terminal, and the OMC-R allows the operator to supervise all
the equipment remotely.

1 Introduction
1.2 Operation & maintenance sub-system
The functions provided by the 9153 OMC-R are:

 Supervision NMC
 Configuration
 Performance 9153 OMC-R
DCN
DCN
OMC-R-CN
BSS
BSS
BSS
BTS
BSC BTS Core Network
BSC
BSC
MFS BTS


1 Introduction
1.3 Fault management processing
A failure is detected by a network element and

9153 1 an alarm is generated.
6
OMC-R 2 The alarm is forwarded towards the BSC.
The alarm correlation is performed in the BSC. The

3 alarm is stored in the Alarms in Force List (AIFL) on the
S-CPR.
4 The alarm is forwarded towards the 9153 OMC-R.
5
5 The alarm is translated, stored and displayed to the operator.
6 The operator reacts to solve the problem.

4
X.25
3 2
TC
BSC BTS
1 · 1 · 10 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

The concept of fault detection in the network by the OMC-R is shown in the diagram.
The fault processing task is carried out in 6 steps.
Whenever relevant, the detection of faults or abnormal conditions (due to events occurring in the radio
subsystem) can be reported to the OMC-R through alarm notifications emitted by the appropriate object.

1 Introduction
1.3 Fault management processing [cont.]
Real-time Static
Management: Navigation Navigation analysis:
CAL HAL
External
Sub-list Application
Sub-list
ordering & ordering &
filtering filtering
Auto beeping Alarms retrieving

Overflow purge
Current Alarms Archived Alarms

Auto acknowledgement filter
Archiving
filtering
Auto purge filter
BSC Alarm flow

Network BSC
Resources MFS Alarm ordering
BTS Alarm filtering
BTS

The Current Alarms List (CAL) contains alarms not cleared (except for the purged ones).
The Historical Alarms List (HAL) contains former current alarms that have been archived through one of the
following processes:
 Auto-purge: Such alarms have never been raised up to the CAL.
 Manual purge: Manually removed from the CAL.
 Overflow purge: According to the overflow configuration defined by the administrator.
 Acknowledge and cleared alarms, or cleared and acknowledged alarms.

1 Introduction
1.4 SBL and RIT definition (internal BSC/BTS view)
A Security BLock (SBL) represents an entity of the BSS which is

manageable by the O&M. This entity can be:
 An equipment (“CCF”)
 A resource (“ACH”)
 A support resource (“ATR”)
An SBL has a state which induces the behavior of the corresponding

function or resource of the entity it represents.
A Replaceable ITem (RIT) is the smallest physical module that can be

replaced in case of fault (can be a board for example):
 Several SBLs may correspond to the same RIT (“SUMA” RIT with “CLLK” or
“OMU” as SBLs)
 An SBL may correspond to several RITs (“RA” SBL with “ANY” and “ANC” as
RITs)
 An SBL may correspond to no RIT ( “BTS-O&M” as SBL)


1 Introduction
1.5 SBL states
HUMAN OPERATION:
 OPR (OPeRator-out-of-service): The object is put out of service by an O&M
user or when an SBL is created.
 UT (Under-Test): The object is being tested on O&M user request. The service
is momentarily unavailable.
Transient State:
 WTC (Wait-for-Traffic-Clear) - this state is linked with the "WTC timer"
parameter of a disable SBL command. It indicates that the corresponding SBL
cannot be selected for new transactions, but on-going traffic still goes on.
When the WTC timer expires, all remaining traffic (if any) is released, and the
target SBL goes MSD.
 MSD (Maintenance-SeizeD) - this state indicates that an operator action is
being processed on the corresponding SBL.
 MSD-AUTO or MSA (Autonomous-Maintenance-Seized) - this state indicates
that an action autonomously triggered by the system is running on this SBL.
The MSD-AUTO state is not spontaneously reported to the operator (it is an
internal system state), but it may be provided as the result of a Read SBL
state command.

1 Introduction
1.5 SBL states [cont.]
LEVEL OF SERVICE:
 IT (In-Traffic) - the object is ready to perform all its functions. For an SBL
which carries traffic or signaling, being IT means that the SBL is ready to
operate.
IT for an A trunk means that no trunk alarms have been detected, but it does
not mean that all the channels of the trunk are unblocked and carry traffic.
 FIT (Faulty-In-Traffic) - the object is ready to perform its functions in a
degraded mode. A non fatal error has been detected on it, the object is
declared as FIT.
 FLT (FauLTy) - a fatal error has been detected. The service is unavailable. If
the SBL is repaired [for example by replacement], it can return to IT
automatically, without explicit operator command.
 FOS (Faulty-Out-of-Service) - a fatal error has been detected. The service is
unavailable. If the SBL is repaired [for example by replacement], an operator
command is necessary to bring it back into traffic.
 EF (External Failure) - the object cannot perform its functions because
another cooperating item is out of service.
 SOS (System-Out-of-Service) - the object cannot perform its functions because
a parent object is out of service.


1 Introduction
1.6 Managed object definition (OMC-R view)
A Managed Object can be:
 A function: Carried by one or several boards (supervised in the functional part

of the BSS Main Equipment View)
 TRE, RA, VTCU, and so on
 A board: Represents a hardware replaceable unit performing a function or a
set of function (supervised in the HW part of the BSS Main Equipment View)
SUMA, TRGM, CCP, TCIF, and so on.
 A resource: Used to serve call management (accessible in the RNUSM
Supervised Configuration View)
• Cell, BSS Telecom.
 An equipment: Is a set of Managed Objects representing telecom, transmission
and transcoding functions in the BSS
• BTS, BSC, TC

In ISO standards, « SBLs » are named « Objects ».

The status of « Objects » is composed of the above states as defined in ISO X731 (these states are also used in
the OMC-R view).

1 Introduction
1.7 Managed object states
Availability state: The availability status describes a set of states. Each
state may be present or not:
 Degraded: The service provided by the MO is available in a degraded mode.
 Failed: The service is unavailable due to a fault that prevents it from
operating.
 Dependency: The service is unavailable due to some other objects on which it
depends.
 Off line: The MO is out of service and needs to be initialized.
 In test: A test procedure on the MO is undergoing.
Administrative state: Reflects the willingness of the operator,
independently of operability and usage of a Managed Object:
 Locked: The object is administratively prohibited from performing service.
 Shutting down: The service is currently shutting down.
 Unlocked: The object is administratively permitted to perform services.
Operational state: Describes the operability of the Managed Object:
 Disabled: The object is totally inoperable and unable to provide service.
 Enabled: The resource is partially or fully operable and available for use.


1 Introduction
1.8 SBL and managed object state mapping
MO Administrative
Operational state Availability state Control state
SBL state
OPR Locked No change {} {}
IT Unlocked Enabled {} {}
FIT Unlocked Enabled Degraded {}
FLT Unlocked Disabled Failed {}
EF Unlocked Disabled Dependency/failed {}
FOS Unlocked Disabled Failed/off-line {}

SOS Unlocked Disabled Dependency {}
UT Locked no change Under Test {}
WTC Shutting down Enabled {} {}
MSD/MSA Unlocked No change {} Suspended


1 Introduction
1.9 Connection to the OMC-R
After launching a Citrix client session configured with the IP address

of the OMC-R, you get the Login window.
You need to enter:
 A user name
 A password


1 Introduction
1.9 Connection to the OMC-R [cont.]
Click to launch the

Icon box


1 Introduction
1.10 Icon box of the OMC-R
Main windows launched by single click

The main windows are:

 Supervision of the equipment:
 BSSUSM
 MFSUSM
 Supervision of the Radio Network: RNUSM
 Supervision of the Alarms:
 Current Alarms
 Historical Alarms

1 Introduction
1.11 Generic customer documentation
A documentation is available with all the information needed by the

customer: Description, maintenance procedure, alarm dictionary, and so
on.
Select an element from the

list
or from the graphical view


1 Introduction
1.11 Generic customer documentation [cont.]
List of documents related

to the selected element


1 Introduction
1.12 Exercise: Connecting to OMC - R
1. Connect to the OMC-R.
2. Launch the Iconbox.
Time allowed: 5 min


2 BSS supervision


2 BSS supervision
2.1 BSSUSM icon & controller
Enter the BSS Id

then click Open BSS

It is possible to open several BSS views in the Controller. The maximum number of BSS views is a customizable
parameter.

2 BSS supervision
2.2 BSSUSM main window
Tool bar BSS info:
 Id,
 name
(cipher),
 release
BSC
supervision
status
Whole BSS Functional

hardware view: view
 TC
 BSC
 BTS

There is one BSSUSM window per BSS.

All the windows associated to a BSS are grouped in that BSSUSM main window.

2 BSS supervision
2.2 BSSUSM main window [cont.]
Alarm
synthesis:
The color
shows
Navigation between
BSS right-click menu the highest
all the windows alarm
of the BSS severity of
the element

There are several types of audit:

 Hardware audit
 Alarm/State audit
 Software audit
The Discover BSS command allows you to perform all the audits at once.

2.2 BSSUSM main window
2.2.1 Exercise: BSSUSM
1. Open the BSSUSM controller.
2. Try to open one BSSUSM that doesn’t exist (enter a wrong Id).
• What do you notice?
3. Open one BSSUSM main window.
4. What is the BSS cipher (short name) ?
Time allowed: 20 min


2 BSS supervision
2.3 TC supervision
No function
associated
with the TC
TC tree view

The TC can manage the Atermux links of several BSCs.

The TCIF boards are seen in the BSS for which the BSSIM was associated with the TC in the DCN.

2 BSS supervision
2.4 BSC supervision
BSC functions
BSC tree view


2.4 BSC supervision
2.4.1 Hardware/functions relationships for the BSC
When selecting
a board or a function,
we can see the relationship
Hardware <-> Function

The CP_HW is the SBL associated to the OMC-RP and to the CCP boards, and the CP_LOG is a set of functions
associated with a CP_HW (except for the CCP spare):
CP_HW 1  OMC-RP1  CP_LOG 1
CP_HW 2  OMC-RP2  CP_LOG 2
CP_HW 3  CCP1  CP_LOG 3
CP_HW 4  CCP2 (spare)  no CP_LOG
CP_HW 5  CCP3  CP_LOG 4

2.4 BSC supervision
2.4.1 Hardware/functions relationships for the BSC [cont.]
Selecting a Abis transmission board and

Display related Abis Chain/Ring
shows the transmission links,
supported by this board

When we select an LIU board, it is possible to navigate to the Abis (or Ater, according to the selected LIU)
managed by that board.

2.4 BSC supervision
2.4.2 Exercise: BSC and TC
1. How can we find out the configuration of the BSC?
2. Check the functions associated with the CCP in slot 5.
3. Check the functions associated with the CCP in slot 10.
4. How many Abis and Ater are configured?


2.4 BSC supervision
2.4.3 Actions through the right-click menu
Right-click on the HW or
functional view to get
the actions available for
the selected element
Actions available
by right-click


2.4 BSC supervision
2.4.3 Actions through the right-click menu [cont.]
The allowed
actions depend on
the selected objet


2.4 BSC supervision
2.4.4 Exercise: Action on BSC board
Perform a reset of an active CCP and check the result.


2.4 BSC supervision
2.4.5 Alarm reporting on the Abis

A LOCK of the alarm reporting does not block the traffic but only the alarm reporting.

2.4 BSC supervision
2.4.6 File management for the BSS

The management of the files is done through FTP.
The SCPRDISK contains all the software of the BSS, such as the CPR SYS in the G2 BSC.
THE OCPRDISK contains the PM files of the BSS, such as the CPR OSI in the G2 BSC.

2.4 BSC supervision
2.4.7 Software management for the BSS

The Software Management window allows you to:

 Generate a new software package.
 Download and pre-download a new software package.
 Activate and accept a new software package.
 Display the running, backup, and new software package.
 Perform a backup or restore a BSC database.
 Configure the automatic backup.

2.4 BSC supervision
2.4.8 Exercise: File and software management
1. Open BSS File Management and find out all the BSS specific files.
2. Upload the BSS Master file and check the content.
3. Compare with the view in the Software Management window.


2 BSS supervision
2.5 BTS supervision
BTS tree view BTS functions


2.5 BTS supervision
2.5.1 Hardware/functions relationships for the BTS
1 MC-TRE
can manage
several TREs


2.5 BTS supervision
2.5.1 Hardware/functions relationships for the BTS [cont.]


2.5 BTS supervision
2.5.2 Navigation from BTS to Abis


2.5 BTS supervision
2.5.3 Navigation from sector to cell


2.5 BTS supervision
2.5.4 BTS view


2.5 BTS supervision
2.5.5 Exercise: BTSs and cells
1. Select a BTS. On which Abis is the BTS connected? Is there a secondary Abis?
2. What is the configuration of the BTS (sector, TRE, band, and so on)?
3. Check the TRE types of the BTS.
• Is there any TWIN or MC-TRE?
• If yes, what is their configuration (number of TREs, TX DIV, and so on)?
4. Check the configuration of the cells associated with the BTS sectors.
• How can we see the relationship between the TRE and the TRX?
5. Which TCU manages the RSL 1 of the BTS?
• What are the other LAPD links managed by that TCU?
6. How can we see the relationship between the TRE and the TRX?


2 BSS supervision
2.6 Supervision of performance measurement campaigns
There are 2 types of measurement campaigns:

 Permanent Measurement Campaigns (PMCs)
 On-Demand Measurement Campaigns (ODMCs)

Permanent Measurement Campaign (PMC):

A PMC is a set of recording jobs concerning all the BSSs supervised by the 9153 OMC-R, applied on
standard counter types only (typically type 110).
 An operator can define up to two recording intervals within 24 hours on one PMC.
On-Demand Measurement Campaign (ODMC): An ODMC allows the diagnosis of a problem detected in the
network by using either detailed counter types or standard counter types not used in a PMC.

2.6.1 Permanent Measurement Campaign (PMC)
View of the PMC configuration

Permanent Measurement Campaign (PMC):

 Concern all counters necessary for Basic Front-Office needs:
 PMC scope: Standard counters.
 Reporting period can be set:
 Every 30 min or 1 hour for BSC counters.
 Every 1 hour for GPRS counters.
 Every 4 hours for “Traffic Flow Measurements.”
 Launched systematically when the BSC/MFS is declared in the OMC-R:
 BSC: Typically type 110, standard measurement types.
 MFS: All counters.
From BSSUSM, we can see the configuration of the PMC, but the modification can be done only from UFM.

2.6.2 On-Demand Measurement Campaign (ODMC)
Creation of an ODMC
Name the campaign

Select one or
more raw types
Select one
or more NEs
Click Create Select the

accumulation
period

On Demand Measurement Campaign (ODMC):

 Concern all counters to investigate network malfunction or tuning a precise feature.
 ODMC scope:
 Standard or detailed counters.
 Counters must not be involved in the PMC.
 Several ODMCs applied on single/different BSSs.
 Different reporting periods can be set: Every 15 min, 30 min, or 1 hour.

2.6.3 Management of measurement campaigns
Click on Search
to
list the
campaigns
Select one campaign

to enable the action


2 BSS supervision
2.7 Usage State on Demand (USD)
It possible to monitor the usage of:

 The cells
 The A interface


2.7 Usage state on demand (USD)
2.7.1 USD cell overview
Select one cell and

Click Cell Report


2.7.1 USD cell overview [cont.]


2.7.2 USD at A interface
Select one
DTC and click
DTC Report


2.7.2 USD at A interface [cont.]


2.7.3 Exercise: USD
1. Select a BTS and find the controlling TCU(s)
• Reset the TCU(s) and check the result in USD and in the CAL.
• Lock one TRE and check again the USD of the cell.


3 MFS supervision


3 MFS supervision
3.1 MFSUSM icon & controller
Enter the MFS Id

then click Open MFS


3 MFS supervision
3.2 MFSUSM – Ater supervision
Ater links
configured Information related to
the Ater configuration


3.2 MFSUSM – Ater supervision
3.2.1 Exercise: MFSUSM
1. Draw the topology of the MFS (GP ports to BSC or SGSN ports).
2. What is the transport mode for the BSS 1: TDM or IP?


3 MFS supervision
3.3 Ater configuration
Right-click on the
Ater and select View of the
Configure GPRS Ater configuration
Ater configuration


3 MFS supervision
3.4 Ater navigation
BSC Atermux view
Right-click on
the Ater and
select Navigate
to BSSUSM


3.4 Ater navigation
3.4.1 Exercise: Atermux links to MFS
Are the Atermux links dedicated or mixed?
Time allowed: 2 min


3 MFS supervision
3.5 MFSUSM – Gb supervision
Information related
Ater links configured to the Ater configuration


3.5.1 Gb configuration
Right-click on the Gb link

and select Configure GB


3.5.1 Gb configuration [cont.]
The Gb interface is defined by an NSVC and a PVC.


3.5.2 Exercise: Gb
What is the maximal Gb capacity of the first link of Gb 1?
Time allowed: 2 min


3 MFS supervision
3.6 Configuration of links
Select Configure then Or right-click on one link and select

Links and Connections Configure Links and Connections


3 MFS supervision
3.6 Configuration of links [cont.]
It is possible to display the connections between the MFS and the BSC, the
MFS and the TC, and the MFS and the SGSN.


3 MFS supervision
3.7 Navigation to the IMT
It is possible to navigate to the Installation and Maintenance Terminal

(IMT) from DCN, RNUSM or MFSUSM, by selecting the equipment, right-
clicking and selecting Open IMT with MFS (or GPU) rights.


3.7.1 IMT view menu
The Site view gives a
view of the entire MFS
The front view displays

the front boards of the
ATCA shelf
The Sub-BSS shows

all the BSS and
the associated GPs


3.7.2 IMT site view
GP equipped


3.7.3 IMT front view


3.7.4 IMT tools menu
Switch over of the

MFS (OMC-RP)
Reset of the MFS

(OMC-RP)


3.7.5 Exercises: IMT
1. Open the IMT.
• How many TPs are associated with each GP?
• Which OMC-RP is the active one?




4.1 RNUSM icon

RNUSM displays and allows you to configure the logical parameters of the network elements.
From this window, we have a global view of the network with a hierarchical structure.

4.2 RNUSM main window
Tree Browser Menu bar Matrix Browser
Cell
information


4.2.1 Matrix browser
Types of
elements to
display
List of filters
Number of
Elements
filtered


4.2.1 Matrix browser [cont.]
Selection
of the
BTS view
List all
the BTSs
of the OMC-R
Number
of BTSs


4.2.2 Exercises: Matrix browser
1. List all the BTS and cell types of the network.
• How many cells are there?
• How many BTSs are there?


4.2.3 Tree browser
Radio Network
hierarchical view
Cell
information


4.2.3 Tree browser [cont.]
Selection of
the Cells view
List all the

OMC-R’s cells
per type
Number of
cells


4.2.4 Symbols in RNUSM
Cell: BSC:
Operational state Operational state

Administrative state Administrative state Packet
Packet
(BSS_Tel)
Cell00010_00001 BSC_MX1
Circuit Alignment status

Circuit Alignment status
BTS: MFS:
BTS_001 MFS_MX1
Operational state Operational state

Administrative state Alignment Status
(O&M Capabilities)


4.2.4 Symbols in RNUSM [cont.]
Single cells
Umbrella cell
Mini cell
Micro cell
Sector without cell


4.2.5 More states
The blue color indicates

that there is at least one
Administrative
alarm that is not
state for the
acknowledged
Packet Domain


LR14.G
4.3 Additional filters in RNUSM external 3G cells window
 Additional filters are included

in the RNUSM external 3G cells
window along with the
parameters of RNC-ID, CI_3G,
and LAC_3G.
 These filters allow operators to
have a more flexible filtering
on the display of external 3G
cells in order to find the
interested cells, especially
when the number of interested
cells is increasing.


4.4 Follow-up window of the OMC-R
The follow-up window shows all the actions launched from the OMC-R.
It is possible to navigate to the other windows from the Follow-up.


4.5 Cell filters in RNUSM
Select the OMC-R Cells
Click on the filter

icon
Name the filter
Define the filter then save it (with Apply)

1. Give a name to the filter.

2. Select the option.
3. Apply the filter.

4.5 Cell filters in RNUSM [cont.]
Select the filter


4.6 BTS filters in RNUSM
Select the OMC-R BTSs
Click on the filter icon
Name the filter
Save,
Example of criteria: BTS then
Generation different Apply
than Evolium


4.6 BTS filters in RNUSM [cont.]
Select the created filter
There are Non-Evolium BTS


4.7 BSS parameters
Most of the BSS parameters

can be modified from the SC


4.8 Cell parameters
The timeslot configuration
cannot be modified
from the SC


4.8 Cell parameters [cont.]
Some
parameters
can be
modified from
the SC


4.9 Search function of RNUSM
Search function


4.9 Search function of RNUSM [cont.]
Display of the
parameters
containing
PDCH
Switch to the
next
parameters
containing
PDCH


4.10 Exercises: Cell and BTS filtering
1. List all the cell types of the network.

• How many cells are there?
• How many BTSs are there?
2. Create a filter named degraded cells showing all the cells that are degraded
(availability status). How many BTSs are there?
3. Create a filter named BTS NH showing all the cells not using frequency
hopping.
5. Check and compare the parameter HR_ENABLED of the cells.
6. Create a filter named HR_ENABLED showing all the cells configured in HR.
• What is the preferred band of the BSS?
• What are the frequency bands used in the BSS?
• What are the frequencies used by the first cell? What is the BCCH frequency?
• How many TRXs are declared in in the first cell?
• Is GPRS enabled in the first cell?


5 Current Alarm List (CAL)


5.1 Fault Management (FM): Current alarms icon


5.2 Current alarms list
Alarm information
Indicates that
there are new alarms
Alarms
sublist
summary
Alarm sublist content

The sublists summary area displays statistics on alarms (alarm counters), according to the alarm severity level
or status as follows:
 Critical
 Major
 Minor
 Warning
 Indeterminate
 Cleared
 Not acknowledged.
You can create additional alarm sublists to meet specific filtering criteria. These then appear in the sublists
summary area:
A sublist selected in the sublists summary area is expanded in the sublist content area.
 Detailed
alarm information is displayed in the [More alarm information] window. This window provides
complete information on the selected alarm. This is particularly helpful for locating and diagnosing the
problem that caused the alarm.

5.2.1 Actions on current alarms
Select an alarm then

right-click to list
the possible actions


5.2.2 Navigation from CAL to the alarm dictionary
Select the alarm
Right-click and select

External Applications –
AlarmDictionary


5.2.2 Navigation from CAL to the alarm dictionary [cont.]
The alarm dictionary

gives a
description of the alarm
… and the
corrective actions


5.2.3 Navigation from RNUSM to CAL
Alarms on the selected object


5.2.4 Navigation from BSSUSM to CAL
Alarms on the selected object


5.2.5 Navigate from CAL to the related equipment
It’s possible to navigate from the alarm to the related equipment:
Select the alarm,

right-click and select
External Applications –
BSSEquipment


5.2.5 Navigate from CAL to the related equipment [cont.]
The selected alarm was a

HW FAILURE
on the
BTS_001


5.2.6 Exercises: CAL
1. Open the CAL.

2. Change the display by activating/de-activating Paginate sublist.
3. Change the display to see only the Severity, the Event Date and Time, the
Friendly Name, the Alarm Type and the Specific Problems.
4. Sort the alarms by Severity.
5. Click on the minor sublist. What do you notice?
6. Select an active alarm and navigate to the related equipment.
• What are the actions recommended to solve the problem?


5.3 Alarm sublists
The CAL has several sublists by default:

 Main alarm list
 Default alarm sublist
 Critical
 Major
 Minor
 Warning
 Indeterminate
 Cleared
 QoS alerter alarms
It is possible to create your own sublists.


5.3 Alarm sublists
5.3.1 Create an alarm sublist
To create a sublist, select the main alarm sublist,

click on Sublist then New

In the first step, we select the main alarm sublist to be sure to take into account all the alarms.
By creation of a new sublist, the system will make a copy of the sublist selected before the creation.

5.3 Alarm sublists
5.3.1 Create an alarm sublist [cont.]
To create a sublist, we can also select the main alarm list,

right-click and select New
Give a name to the sublist

then click on OK


5.3 Alarm sublists
5.3.2 Modify an alarm sublist
The new sublist is a copy of the

main alarm list (if this one was
selected before making New)


5.3 Alarm sublists
5.3.2 Modify an alarm sublist [cont.]
Select Filter
Right-click on the new sublist

then select Modify


5.3 Alarm sublists
5.3.3 Create an alarm filter
Select Include alarms matching the following

to activate the New tab
Click on New to create a filter
Name the filter
Click on More
to add a criterion


5.3 Alarm sublists
5.3.4 Add an alarm filter criterion
Choose (for example)

Friendly Name,
Substring, BTS,
then click on OK
The filter is created

We want to make a filter where the Friendly Name field contains the word « BTS ».

5.3 Alarm sublists
5.3.5 Apply the alarm filter
List of all the alarms where the

Friendly Name contains BTS
Select the filter

then Apply

5.3 Alarm sublists
5.3.6 “Not Superset of” filter
Some alarms (example: CLK HW DEGRADED) are polluting the view.

The aim is to suppress the display of those alarms.
Create a new sublist


5.3 Alarm sublists
5.3.6 “Not Superset of” filter [cont.]
Create a new filter
Select the
Select Not Superset of unwanted alarm
then click on OK


5.3 Alarm sublists
5.3.6 “Not Superset of” filter [cont.]
List of the alarms

(without the suppressed ones)
Select the filter

then Apply


5.3 Alarm sublists
5.3.7 “Null intersection” filter
There are still many alarms (example: PROCESS RESET) polluting. So we

would like not to display those ones neither.
Modify the sublist


5.3 Alarm sublists
5.3.7 “Null intersection” filter [cont.]
Select the filter and Edit it
Click on + to add
the unwanted alarms
Select Null intersection


5.3 Alarm sublists
Select the unwanted

alarms then click on OK
You can see the

rule of the filter
Click on OK


5.3 Alarm sublists
List of the alarms without the one filtered
Apply the new filter


5.3 Alarm sublists
5.3.8 Exercises: “Null intersection” filter
1. Create a filter to display only one type of alarm (in Specific Problems).
2. Modify the filter to display all the alarms except for the previous one.
3. Create a filter to display all the equipment alarms.
4. Create a filter to display all the alarms except for the two that happened
most.
5. Create an Aging to purge the Indeterminate alarms present since 60 min.


6 Historical Alarms List (HAL)


6.1 Fault management (FM): Historical alarms icon
By default, the HAL is empty: 0 alarms

By default, the HAL is empty.

We need to retrieve the alarms either from a public archive or from a user file.

6.2 Navigation from CAL to HAL
Select Window then

FM Historical
to navigate to the
HAL

A second way to open the Historical Alarm List is possible from the Current Alarm List.

6.3 Retrieve historical alarms
Select
1) ‘Archive’
2) ‘Retrieve from
public archive’
3) <hostname>

The Historical Alarm List (HAL) does not have a limited size but the HAL graphical Interface displays only up to
50.000 alarms. So, to solve this problem:
 You can clean up historical alarm files.
 You can apply a specific filter (friendly name, event date and time, and so on).
 You can purge the oldest historical alarms by execution of periodic purges in crontab.

6.3.1 Create an alarm filter
Select
Include alarms matching the
following
to active the New tab


6.3.2 Add an alarm filter criterion
Name the filter
Click on More
to add a criterion
Click on + to
define the Event
Date & Time
Select (for example)

Event Date & Time,
Equals


6.3.3 Define the alarms retrieval date and time
Click on More to add a time period
Select From and enter

the beginning date
If there is no end date,

it is by default up to now


6.3.4 Apply the alarm filter
Active your filter then click on OK


6.3.5 Pagination view
Total number of
alarms retrieved
Number of
alarms per page
Change page


6.3.6 No pagination view
Remove the
pagination
function
List of all the alarms


6.3.8 Save alarms
Select the alarms to save
Right-click and select Save As
Name the set of saved alarms then click on Apply


6.3.9 Retrieve saved alarms
Select Archive, Retrieve from user file
Select the user file then move

it to the Selected User Files
Click on Apply


6.3.9 Retrieve saved alarms [cont.]
List of all the alarms saved by the user
Select Include all alarms

then click on OK


6 Historical alarms list (HAL)
LR14.G
6.4 Save clear alarm in HAL when corresponding active alarm is not in CAL
Supervision–fault management:
 Before LR14:
• Clear alarms are lost due to the overflow of Current Alarm List (CAL). This is because
active alarms in CAL are purged into History Alarm List (HAL) before the arrival of the
corresponding clear alarms. This is the normal behaviour with current CAL
implementation.
• When the clear alarm arrives in CAL, it does not find the relevant active alarm and is,
therefore dropped.
• Without knowing the time of clear alarms, the customer does not know when the
alarms were cleared. This impacts network maintenance.
• The operator requests to increase CAL size limit. However, it is not a preferred
solution not only because it can load the OMC-R but also because it will eventually not
solve this issue in a network with a high number of alarms.
 In LR14:
• Clear alarms are transferred to HAL with the event time unchanged and the clear time
specified.
A new parameter is added in Alarm Supervisor (AS) configuration file,

param.cfg: PURGE_UNMATCHED_CLEAR.


6 Historical alarms list (HAL) LR14.G
6.4 Save clear alarm in HAL when corresponding active alarm is not in CAL[cont.]
When AS receives a clear event, there are two possibilities:

 AS checks if an alarm matching the clear event already exists in CAL. If it
does, the status of the alarm is changed to Cleared.
 If there is no alarm matching the clear event, which may be because the
alarm has already been purged, there are two possibilities:
• If PURGE_UNMATCHED_CLEAR is set to True, the clear event is purged out of the CAL.
In this case, if the clear event matches the Archiving filter, it can be archived to HAL
with event time unchanged, which means reflecting the exact clear time of the
alarm.
• If PURGE_UNMATCHED_CLEAR is set to False, the clear event is ignored (dropped).
With the clear event saved in HAL, the operator is able to correlate it
with the associated active alarm so that the life cycle and duration of this
alarm is complete.


6 Historical alarms list (HAL)
6.5 Exercises: HAL
1. Open the HAL.

2. Change the display by activating/de-activating Paginate sublist
3. Retrieve the alarms since the week before.
4. Select all the Major alarms and save them as « Major ».
5. Create a filter to display all the BTS alarms.
6. Save those alarms as « BTS ».
7. Retrieve the alarms saved as « Major ».
8. Export all the « Major » alarms in a text file and view the file.


7 New features for supervision in LR13.G


7.1 Confirmation dialog for risky operations
Before release LR13.G: No confirmation for risky actions (for example

‘Reset’):
 Many accidents
 Outages
 Call drops
In LR14.G:
 Confirmation dialog box for risky operation


7.1.1 List of risky commands
RNUSM:
 Lock /Unlock GPRS
 Lock /Unlock BTS
MFSUSM:
 Lock/ Unlock GSL
 Disable BSC-OMC-R Link Supervision
 TC Purge


7.1.2 Example of a confirmation dialog box
Reset on the BSC


7.2 OMC-R function and security: Logs improvement
Before release LR13.G:

 Different operators can login on the OMC-R from different terminals, and do
some operations.
 It is impossible to track from which terminal some especially risky operation
are done.
In LR14.G:
 Add the terminal IP address info into the application logs.


7.2 OMC-R Function and Security: Logs improvement
7.2.1 Logs improvement
The logs improvement feature gives the possibility to track from which
terminal some especially risky operation are done.


7.3 Exercises: New features
1. Try to reset a BSC
• What do you notice?
2. Check the logs and try to find out your command


Module summary
In this module, we:
 Described the general O&M principles

 Described the SBLs and the Managed Object states
 Identified the hardware and functional structure of a BSS
 Checked the topology of a BSS
 Handled the BSS files
 Checked the BSS software
 Handled performance measurement campaigns
 Checked the telecom resources
 Checked the configuration of the MFSs
 Checked the logical parameters of the BSCs and of the radio cells
 Managed the current alarms
 Created alarm filters
 Managed the historical alarms
 Configured the alarm filters


End of module
OMC-R BSS Supervision


Learning experience powered by
Alcatel-Lucent University
Section 1
9153 OMC-R BSS LR13.G Supervision
Module 2
Abbreviations and Acronyms
9153 OMC-R BSS
LR14.G Supervision

9153 OMC-R BSS LR13.G Supervision · Abbreviations and Acronyms

Blank page

9153 OMC-R BSS · LR14.G Supervision This page is left blank intentionally
Document History
Edition Date Author Remarks
01 2015-12-05 Goel, Vibhor Update to release LR14.G

Abbreviations and acronyms
A M
A BSC-MSC interface MC-TRE Multi-Carrier TRE
Abis BSC-BTSSwitch to notes view!
interface MFS Multi-BSS Fast packet Server
AIFL Alarms in Force List MFSUSM MFS User Service Manager
ATCA Advanced Telecommunications MSD Maintenance-SeizeD
Computing Architecture MSA Autonomous-Maintenance-Seized
Ater telecom interface between the BSS and MSD-AUTO > MSA
the MSC MO Managed Object
Atermux Ater Interface sub-Multiplexed
ATR A-Trunk N
NE Network Element
B NH No Hopping
BCCH Broadcast Control Channel NMC Network Management Center
BSC Base Station Controller NSVC Network Service Virtual Connection
BSS Base Station Subsystem
BSSUSM BSS User Service Manager O
BTS Base Transceiver Station ODMC On-Demand Measurement Campaign
O&M Operation & Maintenance
C OMC Operation and Maintenance Center
CAL Current Alarm List OMCP O&M Control Processing
CCF Cabinet Cooling Fan OMC-R OMC-Radio
CCP Call Control Processing OML Operation and Maintenance Link
CLLK Clock Link OMU
CN Core Network OPR OPeRator-out-of-service
CP Control Processing OS Operating System
D P
DCN 1 · 2 ·Data
3 Communication Network PCU
Packet Control Unit
Div Diversity
9153 OMC-R BSS · LR14.G Supervision PMC Permanent Measurement Campaign
DTC Digital Trunk Controller PVC Permanent Virtual Connection
E R
EF External-Failure RA Routing Area
RIT Replaceable Item
F RNUSM Radio Network User Services Manager
FIT Faulty-In-Traffic
FLT FauLTy S
FOS Faulty-Out-of-Service SBL Security Block
FTP File Transfer Protocol SC Supervised Configuration
SFTP Secured File Transfer Protocol
G SGSN Serving GPRS Support Node
Gb BSS-SGSN interface SOS System-Out-of-Service
GPRS General Packet Radio Service SUMA Station Unit Module A for GSM
GPU GPRS Packet Unit
T
H TC Transcoder
HAL Historical Alarm List TCH Traffic Channel
HR Half Rate TCIF Transcoder Internal Function
HW Hardware TCU TRX Control Unit
TDM Time Division Multiplexing
I TRE Transceiver Equipment
IMT Installation and Maintenance Terminal TX Transmitter Receiver Module
IT In-Traffic
IP Internet Protocol U
ISO International Organization for USD Usage State on Demand
Standardization UT Under-Test
UFM User Facility Management
L USM User Service Manager
LIU Line Interface Unit

End of module
Abbreviations and Acronyms


Last but one page
Congratulations
You have finished the training
Your feedback is appreciated!

Please feel free to Email your comments to:
training.feedback@alcatel-lucent.com
Please include the training reference in your email (see cover page)
Thank you!
1 All Rights Reserved © Alcatel-Lucent 2015

9153 OMC-R BSS
LR14.G Supervision
All Rights Reserved © Alcatel-Lucent @@YEAR

@@COURSENAME - Page 1
All rights reserved © Alcatel-Lucent
Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent
All Rights Reserved © Alcatel-Lucent @@YEAR

@@COURSENAME - Page 2

OMC R Supervision

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

OMC R Supervision

Caricato da

Copyright:

Formati disponibili

9153 OMC-R BSS

COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Passing on and copying of this document, use and communication of its

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

PERMISSION TO USE CONTENT

COPYRIGHTS AND TRADEMARKS

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

3 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

Your feedback is appreciated!

Please include the following training reference in your email:

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

1·1·1 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

1·1·2 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Edition Date Author Remarks

01 2015-12-05 Goel, Vibhor Update to release LR14.G

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

Upon completion of this module, you should be able to:

 Describe the general O&M principles

1·1·3 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

1·1·4 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

3.7.3 IMT front view 74

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

1·1·7 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

1·1·8 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

The functions provided by the 9153 OMC-R are:

1·1·9 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

A failure is detected by a network element and

The alarm correlation is performed in the BSC. The

6 The operator reacts to solve the problem.

1 · 1 · 10 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

The fault processing task is carried out in 6 steps.

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

Auto beeping Alarms retrieving

Current Alarms Archived Alarms

BSC Alarm flow

1 · 1 · 11 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

A Security BLock (SBL) represents an entity of the BSS which is

An SBL has a state which induces the behavior of the corresponding

A Replaceable ITem (RIT) is the smallest physical module that can be

1 · 1 · 12 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

1 · 1 · 14 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

A Managed Object can be:

 A function: Carried by one or several boards (supervised in the functional part

1 · 1 · 15 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

In ISO standards, « SBLs » are named « Objects ».

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

1 · 1 · 16 COPYRIGHT © ALCATEL-LUCENT 2015. ALL RIGHTS RESERVED.

Copyright © 2015 Alcatel-Lucent. All Rights Reserved.

OPR Locked No change {} {}

FIT Unlocked Enabled Degraded {}

FLT Unlocked Disabled Failed {}

EF Unlocked Disabled Dependency/failed {}