Ce Tmo18261 9353 Wms Ua07 Utran Fault Management

9353 WMS
TMO18261 9353 WMS UAO7

UTRAN Fault Management
TMO18261 Issue D0 SG DEN I1.0
STUDENT GUIDE
All Rights Reserved Alcatel-Lucent 2010
All rights reserved Alcatel-Lucent 2010

Passing on and copying of this document, use and communication of its contents
not permitted without written authorization from Alcatel-Lucent

TMO18261 9353 WMS UAO7 UTRAN Fault Management - Page 1
Empty page
Switch to notes view!
9353 WMS
TMO18261 9353 WMS UAO7 UTRAN Fault Management
This page is left blank intentionally

Terms of Use and Legal Notices

1. Safety to
Warning
Switch
notes view!
Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to wear
conductive jewelry while working on the products. Always observe all safety precautions and do not work on the equipment
alone.
The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.
2. Trade Marks
Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent.
All other trademarks, service marks and logos (Marks) are the property of their respective holders, including Alcatel-Lucent.
Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning the Mark. The
absence of a Mark identifier is not a representation that a particular product or service name is not a Mark.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to change
without notice.
3. Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No other
use or transmission of all or any part of this document is permitted without Alcatel-Lucents written permission, and must
include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may be used,
copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from Alcatel-Lucent.
Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it includes or describes, and
is expressly prohibited from modifying the information or creating derivative works without the express written consent of
Alcatel-Lucent.
All
3 rights reserved Alcatel-Lucent 2010
9353 WMS
4. Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including lost
profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not Alcatel-Lucent has
been advised of the possibility of such damages.
Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an endorsement, nor
a recommendation.
This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The information
contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some cases, due to
contractual limitations, certain compromises have been made and therefore some features are not entirely accurate.
Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment and
its operation, or contact your nearest Alcatel-Lucent representative for more information.
The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. AlcatelLucent disclaims any warranties in connection with the products as used and described in the courses or the related
documentation, whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties, including
warranties of merchantability, non-infringement and fitness for a particular purpose, or arising from a course of dealing, usage
or trade practice.
Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed
internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in nature
5. Governing Law
The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are governed by
the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal Notices, or the
application thereof to any person or circumstances, is held invalid for any reason, unenforceable including, but not limited to,
the warranty disclaimers and liability limitations, then such provision shall be deemed superseded by a valid, enforceable
provision that matches, as closely as possible, the original provision, and the other provisions of these Terms of Use and Legal
Notices shall remain in full force and effect.

Blank Page
9353 WMS

Course Outline
Section
1. Course
Alarm defintion and Open NSP
About
This
4. Topic/Section is Positioned Here
Course Module
outline 1. Alarm definition and Open NSP TMO18261 D0 SG DEN I1.0
Technical
support
Section 2. Modify
alarm display
Course Module
objectives
1. modify alarm display TMO18261 D0 SG DEN I1.0
Section 3. Define UTRAN NE and OAM link
Module 1. Define UTRAN NE and OAM link TMO18261 D0 SG DEN I1.0
Xxx
Section
Xxx 4. Analyse alarm
Xxx
Module 1. Analyse alarm TMO18261 D0 SG DEN I1.0
Section 5. Alarm Correction Process
2. Topic/Section
is Alarm
Positioned
HereProcess TMO18261 D0 SG DEN I1.0
Module 1.
Correction
Section 6. Options
3. Topic/Section
is Options
Positioned
Here D0 SG DEN I1.0
Module 1.
TMO18261
9353 WMS

Course Outline [cont.]

6
9353 WMS

This page
is left blank intentionally

Course Objectives
Welcome to TMO18261 9353 WMS UAO7 UTRAN Fault Management
Upon completion of this course, you should be able to:
Illustrate the Fault Management Architecture

Identify the Fault Detection Mechanisms
Illustrate the Alarm Processing Flow
Describe the Fault Management
Use the Alarm On-Line Help
Filter Alarms
Employ the Access Network Specific Maintenance Tools
9353 WMS

Course Objectives [cont.]

9353 WMS

About this Student Guide
Conventions
used
in this guide
Switch to notes
view!
Note
Provides you with additional information about the topic being discussed.
Although this information is not required knowledge, you might find it useful or
interesting.
Technical Reference
(1) 24.348.98 Points you to the exact section of Alcatel-Lucent Technical
Practices where you can find more information on the topic being discussed.
Warning
Alerts you to instances where non-compliance could result in equipment damage or
personal injury.
Where you can get further information
9353 WMS
If you want further information you can refer to the following:

Technical Practices for the specific product
Technical support page on the Alcatel website: http://www.alcatel-lucent.com

About this Student Guide [cont.]
10
9353 WMS

Self-assessment of Objectives
Contract number :
At the end of each section you will be asked to fill this questionnaire
Please, return this sheet to the trainer at the end of the training
Course title :
Client (Company, Center) :

Language :
Dates from :
Number of trainees :
Location :
to :
Surname, First name :

Did you meet the following objectives ?
Tick the corresponding box
Please, return this sheet to the trainer at the end of the training
Instructional objectives
1
Yes (or
globally
yes)
No (or
globally
no)
To be able to XXX
2
11
9353 WMS

Comments
Self-assessment of Objectives [cont.]

Instructional objectives
12
Yes (or
Globally
yes)
No (or
globally
no)
Comments
9353 WMS
Other comments
Thank you for your answers to this questionnaire

Do not delete this graphic elements in here:
Section 1
Alarm defintion and Open NSP
Module 1
Alarm definition and Open NSP
TMO18261 D0 SG DEN I1.0 Issue 1
9353 WMS

Section 1 Module 1 Page 1
Blank Page
112
Alarm defintion and Open NSP Alarm definition and Open NSP
9353 WMS TMO18261 9353 WMS UAO7 UTRAN Fault Management
Document History
Edition
Date
Author
Remarks
01
YYYY-MM-DD
Last name, first name
First edition

Module Objectives
Upon completion of this module, you should be able to:
Describe
List
Explain
Identify ...
113

Module Objectives [cont.]
114

Table of Contents
Page

1 Name of Level 1
1.1 Name of Level 2
1.1.1 Name of Level 3
1.1.1.1 Name of Level 4
No Level
Text Boxes
Symbols (mentioned in Front-Matter Part of Course)
Tables
Numbered Lists
Unnumbered List
Presentation of Animation Settings on Slide Master
Animation Sequence Complete
Text and Graphic
Annotations
Oversized Screen Snapshots
(1) Detail 1
(2) Detail 2
Notes Page only (Standard Notes Text Field Extended)
Notes Page only (Active X Word Text Field)
Main Colors
Splash Pictures (Samples)
How to Do It
Discover
Answer the Questions
Exercise
115
Alarm defintion and Open
NSP Alarm definition and Open NSP
Summary
Self-Assessment on the Objectives
Abbreviations and Acronyms
Glossary
References
End of Module

7
8
9
10
11
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
37
39
40
Table of Contents [cont.]

116

This page

1 Definition of an alarm
117

1.1 Definition of an alarm

Lets imagine that you are a journalist and you need to retrieve all information
about a specific accident from the newspaper database :
Ref 322234: Old car against a train: impact and consequences
In France, several years ago, an old car stopped on a rail cross and
cannot restart.
The driver went outside his car.
A train came and hurt this car.
The train left the railways.
The train hurt a bridge and fell in the river under this bridge.
The train carried some chemical elements.
These ones went into the ground and then polluted the water for several
months for several towns.
How can you characterize this accident ?
118

1.2 How an alarm is defined in the system

On which type of equipment: Old car, Train
Location: South of France
When?
Time raised: several years ago
How?
Type of accident: train hurt car
Probable Cause: old car cannot restart
Consequence: train destroy old car and bridge
Is there a main problem: from the car.
Are they other problem in consequence:
Yes,pollution, bridge
Is there a correlation between the different parts?
Yes, different level of severity
Active/Acknowledged
Note
Alarm Code
Ne name
Ne Id
Correlation Group Id
In NSP ?
Can we split the accident from a source problem with

several consequences? Yes
Do the rescuer manage completely the accident?
yes they acknowledges all details
Can we add some comment, in addition? Yes hazard
Is there any trouble ticket send to the emergency doctor ?
Yes
Can we define a reference of this accident? 322234
With a title? Old car against a train: impact and
consequences
119

Component
Type
Correlation Alarm Type
Probable cause
Severity
Additional text
Time raised
Trouble Ticketing
Whats an Alarm ?
Alarm !
ITR
Notification
Main
Server
internal
decision
RNC
ITFB
State / Status Change
BTS
1 1 10
Each Manageable entity in the RNC/BTS has in general something like 3 states (administrative state,
operational state & usage state) and 6 status (alarm status, upgrade status, )
When one of this states or status change the NE might send SCN (state or status change notification) to the
Main server.
The main server using it own internal decision mechanism decide to transform this notification (or these
notifications) into an alarm (or several alarms). The Mais server decides also about the severity of this alarm
(Critical, Major or minor)

Alarm life cycle
Bad
state
Good
state
Administrative state
unlocked
locked
SET
Operational state
enabled
Usage state
active
1 1 11
disabled
Clear
idle
When the object state change from good state into bad state, an alarm (or notification) with SET flag is
raised. In the opposite, when the object goes back to the good state the flag CLR is raised in the
notification or the alarm.
The states depend on the object, for example some object support two administrative states only
(locked/unlocked) some others can have a third state (shutting down). The same thing for the usage state
for example: it can be idle, active or busy.

2 How to open the NSP
1 1 12

2.1 Modify the hosts file on your PC

On your PC client Under C:\WINNT\system32\drivers\etc directory
Modify the hosts file like this:
IP Address
of the Main Server
Full name of the Main Server
Short name of the Main Server

1 1 13
The Network Services Platform (NSP) is a network management platform that enables you to
manage your network from within a single user interface.
A basic NSP installation provides standardized fault information about many different types of
network elements. One of its key strengths is that additional Preside products, such as
Historical Fault Browser, can be integrated into and launched directly from within the NSP
interface. Therefore, each NSP installation can be customized to suit your needs.
To install NSP on your PC you need to declare the WMS server\ on your PC, to do that you
need to add a line to your hosts file located on:
C:\WINNT\system32\drivers\etc
on your OS
the first directory could be WINNT or windows depending
The line should contain the IP address of the WMS server, the hostname and the DNS as
mentioned above

2.2 Install the Java version
1 1 14

2.3 Launch NSP
1 1 15

2.4 Main Window
1 1 16
In the main Window, a menu bar provides standardized functional grouping of menus and
dialogs based on TMN recommendations. This consistent user environment increases
efficiency, driving down operational and training costs.
The Resource Browser provides a layered, map-based representation of the network.
The Navigator provides an hierarchical view of the network organized in a Windows
ExplorerTM style tree, based on NE groups (see "Creating Network Element Groups"). The
Navigator also provides a summary count of alarms at each level in the network hierarchy.
The Network Banner provides an "always-on" summary of active alarms in the network.
This main window also provides Layout administration tools (Layout Editor and Network
Definition toolbar), System Administration tools (Application Management, Access Control,
Netscape Directory Service (NDS) configuration, and Custom Commands) and a Status bar,
Management and System Management Indicators.

2.5 Display alarm with the Alarm Manager
1 1 17
A new field is added to the alarm message: the alarm code.
The alarm code identifies uniquely an alarm type within all domains, OAM, RNC, BTS, POC.
In order to harmonize the display and simplify the reporting, this field shall have an
homogeneous format across the nodes:
<NE Type>_<5 digits(0-9)>_ <5 digits(0-9)>
This new field is displayed in a new column in the alarm browser and the HFB.
This field can be used in HFB for statistical reporting.

2.6 Principles
The alarm code shall identify uniquely an alarm type within all domains, OAM,
RNC, BTS, MSS. This new field shall be displayed in a new column in the alarm
browser and the HFB. This field can be used in HFB for statistical reporting.
1 1 18
A new field is added to the alarm message: the alarm code.
The alarm code identifies uniquely an alarm type within all domains, OAM, RNC, BTS, POC.
In order to harmonize the display and simplify the reporting, this field shall have an
homogeneous format across the nodes:
<NE Type>_<5 digits(0-9)>_ <5 digits(0-9)>
This new field is displayed in a new column in the alarm browser and the HFB.
This field can be used in HFB for statistical reporting.


Read this notification and answer the questions:
2010/04/08-19:16:35,000-00:00;2010/04/08-19:16:35,00000:00;ALAR;(RNC.userLabel,RNC1);(RNC.userLabel,RNC1)(RNCEquipment,
0)(INode.neId,RNC1_IN);INode;(RNC.userLabel,RNC1);NE;72939;Communi
cationAlarm;lossOfSignal;70060003;Major;(PPSubEqt,EM RNC1_IN NMIS
$ TELNET $ SESSION 1);'TCP connection from 10.10.10.6 failed. userid =
debug role = dataStreams = ala ~deb ~log ~scn ~rts rem oteTcpPort =
62866 screenWidth = 79 loginTime = 2010-04-08 18:54:02.921 idleTime =
22' componentId: EM RNC1_IN NMIS $ TELNET $ SESSION 1
operationalState: enabled administrativeState: unlocked usageStatus:
usageActive standbyStatus: standbyEmpty unknownStatus: FALSE ;
1 1 19
What happened exactly?
Do you thing that the Main server generated a alarm due to this notification?

Module Summary
You are now able to:
Define an alarm
Show how to have access to the GUI which allow to display alarm
1 1 20

Discussion or Question
1 1 21

Self-assessment on the Objectives
Please be reminded to fill in the form

for this module
The form can be found in the first part
of this course documentation
1 1 22


#
#1
#2
Switch
to notes view!
Full Writing of Term #1
O
O1
O2
Full Writing of Term O1

A
A1
A2
Full Writing of Term A1

P
P1
P2
Full Writing of Term P1

B
B1
B2
Full Writing of Term B1

Q
Q1
Q2
Full Writing of Term Q1

C
C1
C2
Full Writing of Term C1

R
R1
R2
Full Writing of Term R1

D
D1
D2
Full Writing of Term D1

S
S1
S2
Full Writing of Term S1

E
E1
E2
Full Writing of Term E1

T
T1
T2
Full Writing of Term T1

U
U1
U2
Full Writing of Term U1

F
F1
F2
1 1 23
Full
Writing of Term F1
Full Writing of Term F2
G
G1
G2
Full Writing of Term G1

H
H1
H2
V
V1
V2
Full Writing of Term V1

Full Writing of Term H1

I
I1
I2
W
W1
W2
Full Writing of Term W1

Full Writing of Term I1

J
J1
J2
X
X1
X2
Full Writing of Term X1

Full Writing of Term J1

K
K1
K2
Y
Y1
Y2
Full Writing of Term Y1

Full Writing of Term K1

Z
Z1
Z2
Full Writing of Term Z1

L
L1
L2
Full Writing of Term L1

M
M1
M2
Full Writing of Term M1

N
N1
N2
Full Writing of Term N1

Abbreviations and Acronyms [cont.]

1 1 24

Glossary
#
#1
#2
Explanation of Term #1
A
A1
A2
Explanation of Term A1
B
B1
B2
Explanation of Term B1
C
C1
C2
Explanation of Term C1
D
D1
D2
Explanation of Term D1
E
E1
E2
Explanation of Term E1
F
F1
F2
1 1 25
Explanation of Term F1
G
G1
G2
Explanation of Term G1
H
H1
H2
Explanation of Term H1
I
I1
I2
Explanation of Term I1
J
J1
J2
Explanation of Term J1
K
K1
K2
Explanation of Term K1
L
L1
L2
Explanation of Term L1
M
M1
M2
Explanation of Term M1

Glossary [cont.]
N
N1
N2
Explanation of Term N1
O
O1
O2
Explanation of Term O1
P
P1
P2
Explanation of Term P1
Q
Q1
Q2
Explanation of Term Q1
R
R1
R2
Explanation of Term R1
S
S1
S2
Explanation of Term S1
T
T1
T2
1 1 26
Explanation of Term T1
U
U1
U2
Explanation of Term U1
V
V1
V2
Explanation of Term V1
W
W1
W2
Explanation of Term W1
X
X1
X2
Explanation of Term X1
Y
Y1
Y2
Explanation of Term Y1
Z
Z1
Z2
Explanation of Term Z1

References
1 1 27

End of Module
Alarm definition and Open NSP
1 1 28

Section 2
Modify alarm display
Module 1
modify alarm display
9353 WMS

Blank Page
212
Modify alarm display modify alarm display

Document History
Edition
Date
Author
Remarks
01
YYYY-MM-DD
First edition

Module Objectives
Describe
List
Explain
Identify ...
213


214


Table of Contents
Page

1 Name of Level 1
1.1 Name of Level 2
No Level
Text Boxes
Tables
Numbered Lists
Unnumbered List
Text and Graphic
Annotations
(1) Detail 1
(2) Detail 2
Main Colors
How to Do It
Discover
Exercise
215
Modify alarm display modify
alarm display
Summary
Glossary
References
End of Module

7
8
9
10
11
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
37
39
40

216

This page

3 Modify the alarm stream on the NSP
217


3.1 Fault Detection Mechanisms

The Alarm
stream can be
modified
NSP GUI
PC Client
Events
Alarms
Intervention
required
Notifications
Main Server
State
Change
Software
anomaly
Warning
Hardware
fault
RNS 1
RNC
218
Fault
detection
(supervision)
BTS
BTS
BTS
.

Everything that happens during the lifecycle of the NEs is called event. Event reports are sent by all pieces of
equipment to the OAM platform in order to constantly inform the system about the state of the whole
network.
The fault management function manages the unsolicited messages coming from the NEs. These messages are
as follows:
software anomaly: software anomaly messages inform users of anomalies detected in applications
associated with UTRAN processing chains.
hardware fault: hardware fault messages inform users of equipment failures and malfunctions.
Warning: warning messages inform users of operating changes, such as short-lived faults and
inconsistencies detected on managed objects.
State changes usually generate notifications which are stored in the log file for investigation purposes,
later on. However, some state changes may lead to alarms when specific events require intervention of
the OAM staff members.
For instance, the state change to Disabled Dependency is sufficient to generate an alarm. Besides,
some logical objects (FDDCell, ControlPort, neighbouringRnc, ) may also generate OsiState alarms.
Starting from V3.1, the state changes are treated as functional faults (loss of service) and processed as
beginning or end of alarms (QoS).
The OAM link state generates a critical alarm when the link is lost, and only a warning if the link is locked.

3.2 Alarm Stream Management (On/Off)
Alarm Banner Display
ON
Active
Rule Set
GUI
Alarm Panel
Original
Alarm
Stream
(from the NEs)
219
Alarm Stream
Management

Overview
You can manage the alarm stream sent from the server to reduce the number of alarms displayed in the
GUI clients, or perform other actions on alarms; for example, delay alarms, or change alarm severity.
Rules
To implement alarm stream management, you define alarm rules. A rule or multiple rules can then be
applied to the managed alarm stream.
Once you apply a rule and enable alarm stream management, you can reduce, delay, or modify the
severity of incoming alarms in the current Alarm Manager window, and any subsequent Alarm Manager
windows that you launch.
Benefits
This mechanism has been developed to limit the number of alarms that are displayed in the GUI clients.
Reducing the number of alarms displayed helps to focus alarm monitoring tasks and improves the
performance of the GUI clients.

3.3 Alarm Stream Rule Set Access
2 1 10

The Advanced Filters window allows you to apply a configurable alarm filter. Applying a filter reduces
the number of alarms displayed in the Alarm List.
If you want to use an advanced filter, you must apply the filter each time you log in and each time you
open a new layout. You can use an advanced filter in combination with the filtering options available in the
Alarm List options panel.
Alarms can be filtered by criteria such as NE Name, alarm severity, alarm type (as per ITU
recommendations), alarm name, time of occurrence (local time zones are supported).
The Advanced Filter Settings panel allows you to define advanced filter attributes and to Apply advanced
filters
Define advanced filter attributes: the Advanced Filter Settings panel contains three tabs that display
the properties for a filter (Alarm specific, NE specific, problem specific). If a filter is currently
selected in the Retrieve Saved Filters panel, the properties for that filter are displayed.
Apply advanced filters: When you apply an advanced filter to the alarm display for the current layout,
the filter name displays in the Advance Filtering text field.
With the support of the negative criteria in the Alarm Manager Advanced Filtering, the operator is
able to filter alarm information using negation criteria, for instance NE name "does not contain"
instead of only "contain".

3.4 Alarm Stream Rule Set
2 1 11

The Advanced Filters window allows you to apply a configurable alarm filter. Applying a filter reduces
the number of alarms displayed in the Alarm List.
If you want to use an advanced filter, you must apply the filter each time you log in and each time you
open a new layout. You can use an advanced filter in combination with the filtering options available in the
Alarm List options panel.
Alarms can be filtered by criteria such as NE Name, alarm severity, alarm type (as per ITU
recommendations), alarm name, time of occurrence (local time zones are supported).
The Advanced Filter Settings panel allows you to define advanced filter attributes and to Apply advanced
filters
Define advanced filter attributes: the Advanced Filter Settings panel contains three tabs that display
the properties for a filter (Alarm specific, NE specific, problem specific). If a filter is currently
selected in the Retrieve Saved Filters panel, the properties for that filter are displayed.
Apply advanced filters: When you apply an advanced filter to the alarm display for the current layout,
the filter name displays in the Advance Filtering text field.
With the support of the negative criteria in the Alarm Manager Advanced Filtering, the operator is
able to filter alarm information using negation criteria, for instance NE name "does not contain"
instead of only "contain".

3.4 Alarm Stream Management [cont.] Inhibit

INHIBIT
Action Type
Alarm Stream modified

GUI
ON TIME
Alarm Stream
Rule Definition
Other Alarms
2 1 12

Action on Alarms
The parameters of the Rule Definition window must be specified first. To take this mechanism into
account, the Alarm Stream Management window must be turn ON.
These parameters describe the type of action that can be undertaken in front of the alarms raised at NSP
level:
Inhibit: removes the alarms from the managed stream. If multiple actions are defined, only the
inhibit action will be applied.
Delay: postpones the display of alarms that match the rule criteria for a specified period of time.
Modify severity: replaces the default value with a value selected in the Action area. A drop-down box
gives the list of possible severity values.
Manage as toggling: creates a specific alarm. For instance, you specify rule conditions to create a
toggling alarm when 5 alarms matching the criteria are raised (and cleared) for the same NE within 30
minutes.
Manage as threshold: creates a specific alarm so that one single alarm is displayed instead of multiple
alarms. This new alarm prevents a flood of alarms from being displayed in the Alarm Manager.
Launch application: defines a rule to launch an application once the condition has been met. A dropdown box gives the details of the parameters to be filled.
Acknowledge, Send email & Send SMS are described further in this chapter.

3.4 Alarm Stream Management [cont.] delay

WITH A
DELAY
Action Type

GUI
ON TIME
Alarm Stream
Rule Definition
Other Alarms
2 1 13

Action on Alarms
level:
minutes.

3.4 Alarm Stream Management [cont.] Modify Severity

Severity
modified
Action Type

GUI
ON TIME
Alarm Stream
Rule Definition
Other Alarms
2 1 14

Action on Alarms
level:
minutes.

3.4 Alarm Stream Management [cont.] Automatic Acknowledged Alarms

Alarms
Autoacknowledged
Action Type

GUI
ON TIME
Alarm Stream
Rule Definition
Other Alarms
2 1 15

The Alarm Stream Management allows the user to create a new rule, remove or update existing rules, and
specify whether a rule is applied to the received alarms, that is, set the rule as activated or inactivated.
From the alarm stream rule set menu, the user can configure the Acknowledge action.
This feature allows the operator to automatically acknowledge some alarms based on the alarm type.
This feature dramatically helps the operator supervise his network by auto-acknowledging some alarms
according to their type.
This way, the operator can reduce the volume of alarms to handle and treat as some of them will have
been automatically acknowledged.
The operator gains in terms of operational savings.

3.4 Alarm Stream Management [cont.] Manage as Toggling
Action Type
Alarm managed as Toggling

GUI
ON TIME
Alarm Stream
Rule Definition
Other Alarms
2 1 16

Action on Alarms
level:
minutes.

3.4 Alarm Stream Management [cont.] Manage as Thresthold
Action Type
Alarm managed as threshold

GUI
ON TIME
Alarm Stream
Rule Definition
Other Alarms
2 1 17

Action on Alarms
level:
minutes.

3.4 Alarm Stream Management [cont.] Send an email
Action Type
From: abc@Alcatel-Lucent.com
Sent: wednesday 13 october 2005 15:29
To: user1@Alcatel-Lucent.com; operator1@Alcatel-Lucent.com
Subject: Alarm:Rule Name = alarm send mail demo
Rule Name = alarm send mail demo
Node Name = UTRAN-002
Node Id = EM UTRAN-002
Node Address = 47.153.176.119
Managed Object Class = 1003
Managed Object Instance = (, 1030 = NW UTRAN, 1028 = EM UTRAN002) Notification Id = 104203246 Event Time = 20041013210159Z
Specific Problem = 123 Equipment Type =
Unknown Status = false
Probable Cause = alarmIndicationSignal
Additional Text = This machine is crashed.
Severity = Critical
Alarmed Component = ()
Vendor Specific Info = (, alarmSupportAging = true,
alarmSupportManualClear = true, faultCode = 7654, helpVolume
=, NE_TYPE = 214)
Send an email
GUI
ON TIME
Alarm Stream
Rule Definition
Alarm stream
2 1 18

Action on Alarms
level:
minutes.

3.4 Alarm Stream Management [cont.] send a SMS
Action Type
Send a SMS
GUI
ON TIME
Alarm Stream
Rule Definition
Alarm stream
2 1 19

Action on Alarms
level:
minutes.

4 View the alarms with the Alarm Manager
2 1 20


4 View the alarm with the alarm manager
4.1 Show alarm from Resource Browser (Network Level)
2 1 21

NSP provides a graphical indication of which alarms are acknowledged via the alarm balloon icon displayed at the
left-hand side of each alarm in the alarm list.
Alarms that are not acknowledged have a solid color alarm balloon, in the appropriate color for the alarm severity, and
icons for acknowledged alarms are displayed without the balloon.
Some NEs can generate alarms without generating alarm clear notifications. In such cases, the user can manually clear
these alarms using the same mechanism described above for alarm acknowledgement.
Manually clearing an alarm removes the immediate alarm notification associated with the selected network element.
This option is only available for those alarms that require manual alarm clears, preventing users from clearing other
valid, active alarms.
The system administrator uses the Access Control tool to assign permission to manually clear an alarm.
Details about a specific alarm can be displayed by selecting the alarm in the Alarm Manager. These details
are displayed directly below the alarm list. Details include NE name, Alarm ID, Alarm Type, Unit, Probable
Cause, Equipment Type, Common Language Facility Identifier (CLFI), Reason, as well as acknowledgement
information.

4.2 Show alarm from Network Element (Pop-up menus)

BTS
RNC
POC (pp7k)
2 1 22

NSP provides a graphical indication of which alarms are acknowledged via the alarm balloon icon displayed at the
left-hand side of each alarm in the alarm list.
Alarms that are not acknowledged have a solid color alarm balloon, in the appropriate color for the alarm severity, and
icons for acknowledged alarms are displayed without the balloon.
Some NEs can generate alarms without generating alarm clear notifications. In such cases, the user can manually clear
these alarms using the same mechanism described above for alarm acknowledgement.
Manually clearing an alarm removes the immediate alarm notification associated with the selected network element.
This option is only available for those alarms that require manual alarm clears, preventing users from clearing other
valid, active alarms.
The system administrator uses the Access Control tool to assign permission to manually clear an alarm.
Details about a specific alarm can be displayed by selecting the alarm in the Alarm Manager. These details
are displayed directly below the alarm list. Details include NE name, Alarm ID, Alarm Type, Unit, Probable
Cause, Equipment Type, Common Language Facility Identifier (CLFI), Reason, as well as acknowledgement
information.

4.3
Show alarm from Navigator
2 1 23

The Navigator can be defined as a list-based display of NE groups, in a network tree hierarchy.
It also gives the corresponding alarm summary information. All these parts of information are associated
with one specific user-created layout.
The Navigator allows the user to access his network at 3 levels, from top to bottom: Layout, Group, NEs.
NE Store
The NE Store is a system group for the NEs that have not yet been placed in a group.
The Find utility is a search utility for managed network resources. It is particularly useful for editing
layouts, because you use Find to add network elements to groups.
In the NSP window, select Find in the File menu to start the Find utility.
Find

4.4 Show alarm from Equipment Monitor
2 1 24

NE Store
Find

4.5 Show alarm from boards
2 1 25

NE Store
Find

4.6 Show summarize of alarms from Network Banner
Minor
Major
Warning
Critical
Leads to Alarm Manager

window
Loss of
communication
Alarm Stream Management (On / off)

Alarms encountered
Last action performed
Active Critical Alarms reported by SMC

Total Number of NEs in the Layout/Total Number of NEs in the Network
2 1 26

The Network Banner is the highest-level alert window. The status bar (lowest part of NSP window) and the
network banner provide the same information to the OA&M staff members.
The Network Banner sends visual signals to alert the user whenever potential problems occur in the system.
These aids include a summarization of alarm count and an alarm count for each of the different alarm
severities:
Critical,
Major,
Minor,
Warning.
This summary allows users to track network and sub-network status changes.
Note
The Network Banner remains displayed when the Network Services Platform window is minimized. Use
it when you need to minimize NSP window and do other work while keeping an eye on the alarm
states.

4.7 Alarm Manager Overview
Pushbutton
Alarm Details
Additional text
Note
Users
Userscan
caninvestigate
investigatealarms
alarmsand
anddecide
decideto:
to:
Reduce
the
number
of
alarms
displayed
Reduce the number of alarms displayedininthe
thealarm
alarmmanager
manager
Acknowledge
Acknowledgeororunacknowledge
unacknowledgeindividual
individualorormultiple
multiplealarms
alarms
Manually
Manuallyclear
clearindividual
individualorormultiple
multiplealarms
alarmswhen
whenappropriate
appropriate
2 1 27

Basically, the Alarm Manager is the main decision assistant enabling the support engineer to decide how to
react in front of the various situations.
All parts of the UMTS network share a common Fault Management System. All alarms are stored in a single
database and reported to the user thanks to NSP.
The NSP GUI identifies a Network Element in an alarm state by adding a balloon to the NE icon, as well as
changing the icons color. The operator has the ability to:
remove alarms from the Preside system
remove reporting of symptomatic alarms from the Preside system
delay reporting of alarms
control reporting of Toggling alarm conditions in the network
The operator can open the Alarm Manager window to display a more detailed view of the faults that
are reported. More precisely, the operator can open up to 5 Alarm Manager simultaneous windows
during his NSP session.
The Alarm Manager brings up a listing of all the alarms that are associated with the Network Elements.
In the following pages, we are going to deeply discuss the facilities of the Alarm Manager tool.

4.8 Sorting Alarms
Selecting the appropriate

column heading
2 1 28

Display Criteria
Select a column as the key for sorting the Alarm List by clicking on a column heading. Double-clicking
the appropriate column heading displays the alarm list of alarms according to the selected criteria.
Type & Severity are the usual ways to organize the list of alarms.
Selecting Type will show the alarms in the following order:
Communications
environmental
Equipment
processing
quality of service
Selecting Severity as the criterion will show the alarms in the following order:
Critical
Major
Minor
Unknown
Warning
Once selected, the current criterion is associated with a triangle signal. Choosing a new order
doesnt reduce the number of alarms displayed in the list.

4.9 Sorting Alarms [cont.]
Selecting the sort keys
2 1 29

As we have seen earlier, the Alarm Manager brings up a listing of all the alarms that are associated with
the Network Elements.
In addition to the display criteria, the alarm manager allows sorting alarm records. With this feature,
the users can define three sort keys among the available columns in the alarm manager list:
Primary sort key
Secondary sort key
Tertiary sort key
To specify the sort keys, the user opens the Sort Alarm List option from the Action menu and selects
the keys as well as the direction ascending / descending.
Right
In
click any of the sort key column to deactivate this feature.
the slide above, the selected sort keys are:
1) Type,
2) NE Name,
3) Severity.

4.10 Alarm Information Load View
NEs
Tiny
2 1 30

From the OAM 5.0, the Resource Browser provides two kinds of views: the existing topology view and a new
grid layout view called info load. The Grid layout View offers a convenient way to display large numbers
of NEs such as in typical wireless edge networks. This option includes the following capabilities:
In a Grid View only NEs and groups are displayed. They are automatically displayed in a grid pattern
(i.e. uniform rows and columns of objects), with all NEs displayed in front of all groups. The links
between NEs are not displayed.
The Grid Size of a Grid View can be set. Changing the Grid Size enables the user to control the
number of objects that are visible in a single window. When a smaller Grid Size is selected, the
information displayed for each NE or group (alarm balloons, labels, icons, etc.) is reduced to enable
more objects to be visible in the window.
Information in a Grid View can be sorted and filtered according to certain options such as sorting
both NEs and groups by name, filtering so that only the ones with new alarms are displayed, etc..
As shown in the slide above, the new Grid Layout view includes 4 icon sizes. The information load shows
the percentage of criteria selected to be associated with the NEs.

4.11 Info Load View [cont.]
2 1 31

Grid view: sort alarm from left to right according to severity etc. possibility to filter alarms
On the left: not sorted not filtered, max size; on the right, sorted by severity, filtered on new alarms, min
size 25%
4 sizes: max size, 75%, 50%, 25%
Sort - NEs and groups are sorted from left to right and top to bottom. Sort by Name: NE and group
name in alphabetical order and by Severity: alarm severity are possible.
Filter on - You can limit the display to NEs display can be limited by filtering on All alarms, New alarms,
Acknowledged alarms or No alarms
Auto-refresh - When the grid view is sorted by alarm severity or a filter is applied, the display will update dynamically
when the Auto-refresh box is checked

4.12 Info Load View [cont.]

Sorting
Sortingby
bySeverity:
Severity:
1-1-Critical
Critical
22Lille
LilleB-182
B-182
22Lille
LilleB-127
B-127
2-2-Major
Major
11Lille
LilleB-152
B-152
Etc
Etc
3-Minor
3-Minor
11Lille
LilleB-070
B-070
Etc
Etc
4-Warning
4-Warning
11Lille
LilleB-078
B-078
Etc
Etc
2 1 32
Info.
Sorting
Load
the NEs
Filtering the
NEs

Sorting capabilities: The position of the NEs in the Grid Layout View can be adjusted to reflect the sorting
of NEs based on two criteria:
The Default order is the order defined by the user when the layout was last saved. This is the only
stable NE positioning reference in the Layout. It enables the user to find a given NE in a given position
in the grid when needed. If "Default order" is selected the position of the NEs does NOT change when
the Alarm State and Status of the NEs changes if the Auto-refresh option is selected or if the
Refresh command is used.
The By severity is the order where NEs are laid out based on the Alarm Status and State of the NE
(listing the worst cases first). If "By severity" is selected the position of the NEs changes when the
Alarm State and Status of the NEs changes if the Auto-refresh option is selected or if the "Refresh"
command is used.
Filtering capabilities: The display of the NEs can be adjusted to show only those alarmed or acknowledged,
etc.. The display option includes the option to filter on the following items:
All Alarms: Only alarmed NEs will be displayed acknowledged or not.
New alarms: Only NEs will unacknowledged alarms will be displayed
Acknowledged alarms: Only NE with ack. alarms will be displayed
No alarms: Only NEs without alarms ack. or not will be displayed
With these enhancements, the customers have the ability to have the entire network view in one window.

4.13 Radio Network Subsystem View
RNCs
RNS#4
2 1 33

This feature provides an additional optional view of UMTS Access Network Elements in the Resource
Browser. The RNS View shows the relationship between one specific RNC and its related Node-B NEs.
It aligns with the designs of other W-NMS browser views, which include the ability to scroll, filter,
sort, and launch other applications.
The screenshot above shows an example, where RNCs are displayed at the top of the window
whereas their related Node-B NEs are grouped below. This example shows a relatively large network
view, with NEs sorted by severity of alarms.
Additional information about a selected NE is shown in an In Focus: description located at the

bottom.
POCs are not seen in this particular RNS view.
Note:
This feature does not position Node-B NE according to an assigned numerical identifier. For example,
Node-B NEs related to a particular RNC are not assigned a position number 0 through 200. Instead,
they are positioned by the users selected sort option.

4.14 Alarm due to Board Insertion & Extraction
Board extraction in
cabinet 0, shelf 0,
2 1 34

Boards inserted in (or extracted from) the BTS automatically generate a warning message. This new
alarm is attached to BTS object in the Equipment Monitor window.
However, the plug & play mechanism is preserved: afterwards, the Equipment Monitor window still
reflects the physical board layout (30s refresh period).
Multi Service Switches provide the ability to add extended information to the alarm comment text
on a per port basis. This feature allows operators to provision text of their choosing to be appended
to the comment field of alarms for specific MSS interface ports.
These additional comments appear in the Alarm browser and the Historical Fault Browser.
This feature allows for instance to indicate the name of the remote node connected to the faulty
interface, hence facilitating troubleshooting.

4.15 Alarm Annotations
2 1 35

The operator has the ability to annotate alarm type (fault code) from the alarm browser by right clicking on
an alarm. An editor is provided to add the annotations.
From the NSP alarm window, the user first selects the concerned alarm type by right clicking on an alarm
record. Next, he presses the Edit (left part) button and writes down his annotation.
Rights
The latest user editing the annotation has the ability to edit the entire annotation. Only authorized
users have the rights to edit the annotation. The rights are controlled by the access control
framework.
Users can edit / modify the Annotation for the alarms which are saved on the Main server and purged
accordingly to the platform administration rules.
The user name, the date and time as well as the hostname and IP @ of the location are recorded in
the annotation.
Display
If there is only one Fault-code and Help Volume per alarm type, then the Alarm Annotation window
will be displayed.
If there are multi Help Volumes for the selected alarm, an Option Panel will popup to select one
specific Help. Next, the Alarm Annotation window will be displayed.

4.16 User Preferences
Sort key:
column name and
order
2 1 36
Column sizes
Sorting order
(chronology)

This facility allows the operator to save his own user preferences related to the alarm manager display.
Starting from OAM 5.0, customers have the capability to save their own user preferences such as column
order, size, and sorting settings.
The size and position of the window are also recorded.
By keeping the alarm manager user preferences, operators save considerable time since they dont have
to set up their preferences each time they log in.
This way, they can immediately start to supervise the network in terms of fault management, based on the
alarm manager tool in concordance with their most optimized display preferences.

4.17 Raw Details
2 1 37

Some alarms include text fields that are too large for the Alarm Manager window.
The Alarm Record Viewer shown above allows you to view the raw alarm fields.
Open the Alarm Record Viewer from the Alarm Manager window (Action menu) by selecting View Raw
Details.
The Alarm Record Viewer displays all the alarm fields in a scrollable text field.
The Alarm Record Viewer window contains an Edit menu with a Copy command.

5 Reduce the alarms displayed in the Alarm

Manager
2 1 38


5 Reduce the alarms display in the alarm manager
5.1 Criteria for filtering (by Severity & Acknowledgment)
2 1 39

In alarm filtering criteria and In Alarm stream rule set, the advance filter GUI and rule
definition GUI should provide the Alarm Code filter in the Problem Specific tab with the
following conditions: Contains, does not contains, equals, not equal to.
Previous OAM05 alarm code values are not maintained.

After OAM upgrade all active alarms raised before upgrade are shown with the legacy
alarm code (OAM05 alarm code) until they are cleared, all new alarms raised after
upgrade are shown with the new OAM06 alarm code value.
The help on-line for alarms (Selected Item Help on contextual menu), is not available
for these remaining OAM05 alarms.

5.2 Criteria for filtering (Advanced Filter)
2 1 40



5.3 New criteria for filtering
You can filter

By
Alarm code
2 1 41



6 Acknowledge the alarms
2 1 42


6 acknowledge the Alarm codes display
6.1 Acknowledge the alarms
2 1 43



7 Clear the alarms
2 1 44


7 Clear the alarms
7.1
Clear the alarms
2 1 45



How to Do it
2 1 46


Discover
2 1 47


2 1 48


Exercise
Alarm Stream Rule Set
What does this sign show ?
The Network Banner is supposed to provide a view of the whole

network. Network banner always active in on Summary of all alarms
Can you tell precisely what part of the network is supervised by the
Banner?
If you click on the Details button in the Network Banner, where does
it lead to?
2 1 49


Exercise
Here are three statements defining the Alarm Stream Rule set. Which one is
true?
The alarm stream rule set allows the user to reduce the number of NEs
displayed in the GUI clients
The alarm stream rule set allows the user to reduce the number of GUI clients
The alarm stream rule set allows the user to filter the alarms displayed in the
GUI clients
Look at the Rule Details below:
What can you deduce from this rule?
Go to the fault menu and create a rule to remove the major and minor alarms
of the BTS from the stream.
Note your actions.
Activate your Alarm Stream rule. Wait for a few minutes (2 min.) and then
reset the BTS. What do you observe ?
Note your actions.
2 1 50


Exercise
Resource Browser
Main Observation with the tool

Among the following statements, which one is true?
The Resource Browser gives the list of alarms for the NEs of the current
layout.
The Resource Browser gives the state of each NE of the current layout.
The Resource Browser gives the detailed list of the NEs of the current layout.
Here is an example of the Resource Browser.
Once you have selected one object, what kind of information can you
find in the Details subpart of the Resource Browser?
2 1 51


Exercise
In this view of the network, several NEs are displayed in blue.

What does it mean? it means it's disconnected in WMS monitroning
At the beginning of the NSP session, there are several ways to

open a Resource Browser window. Give two ways to do it.
Suppose that you only want to display the NEs related to Wireless
and IP technology layers. How can you manage to do it?
The Resource Browser leads to other specific tools dedicated to

fault management. Can you list three or four tools among others?
2 1 52


Exercise
Network Banner
Main Observation with the tool

Two tools provide a summary of the alarm counts. Could you give the
name of these tools?
Here is an example of the Network Banner.
What are the meanings of these four figures?
2 1 53


Module Summary
2 1 54


2 1 55



for this module
2 1 56



#
#1
#2
Switch
to notes view!
O
O1
O2

A
A1
A2

P
P1
P2

B
B1
B2

Q
Q1
Q2

C
C1
C2

R
R1
R2

D
D1
D2

S
S1
S2

E
E1
E2

T
T1
T2

U
U1
U2

F
F1
F2
2 1 57
Full
Writing of Term F1

G
G1
G2

H
H1
H2
V
V1
V2


I
I1
I2
W
W1
W2


J
J1
J2
X
X1
X2


K
K1
K2
Y
Y1
Y2


Z
Z1
Z2

L
L1
L2

M
M1
M2

N
N1
N2


2 1 58


Glossary
#
#1
#2
A
A1
A2
B
B1
B2
C
C1
C2
D
D1
D2
E
E1
E2
F
F1
F2
2 1 59

G
G1
G2
H
H1
H2
I
I1
I2
J
J1
J2
K
K1
K2
L
L1
L2
M
M1
M2

Glossary [cont.]
N
N1
N2
O
O1
O2
P
P1
P2
Q
Q1
Q2
R
R1
R2
S
S1
S2
T
T1
T2
2 1 60

U
U1
U2
V
V1
V2
W
W1
W2
X
X1
X2
Y
Y1
Y2
Z
Z1
Z2

References
2 1 61


End of Module
modify alarm display
2 1 62


Section 3
Define UTRAN NE and OAM link
Module 1
9353 WMS

Blank Page
312
Define UTRAN NE and OAM link Define UTRAN NE and OAM link
Document History
Edition
Date
Author
Remarks
01
YYYY-MM-DD
First edition

Module Objectives
Describe
List
Explain
Identify ...
313

314

Table of Contents
Page

1 Name of Level 1
1.1 Name of Level 2
No Level
Text Boxes
Tables
Numbered Lists
Unnumbered List
Text and Graphic
Annotations
(1) Detail 1
(2) Detail 2
Main Colors
How to Do It
Discover
Exercise
315
Define UTRAN NE and OAM
link Define UTRAN NE and OAM link
Summary
Glossary
References
End of Module

7
8
9
10
11
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
37
39
40

316

This page

8 UTRAN Products
317

8 UTRAN Products
8.1 UTRAN Products

Alcatel-Lucent
BTS
Alcatel-Lucent
9370 RNC
Uu
RNC
POC
Iub (ATM)
Iub (E1)
Circuit Domain
Node B
(BTS)
UE
Iu
(CS & PS)
Iur
Alcatel-Lucent
POC (PP7k or 7670)
Iu CS
ATM
Backbone
ATM
Backbone
Uu
Iu PS
Core
Network
Iur
Iub (E1)
UE
Node B
(BTS)
Iu
(CS & PS)
Iub (ATM)
RNC
POC
318
Packet Domain
The UTRAN contains the following components:
Node B: This is a concept representing a logical node responsible for radio transmission and
reception in one or more cells to/from the UE.
BTS (Base Transceiver Station): The BTS is a UMTS node B element. The node B concept can be
associated to the functionality a BTS performs. The BTS supports the 5-MHz carrier and provides the
W-CDMA coding required to control one or more cells. The maximum capacity of the BTS is more
likely restricted by the number of users data rates possible before the interference level becomes
too high. The Alcatel-Lucent Networks Node B is the UMTS BTS.
POC (Point of Concentration): It converts Iub E1 to Iub ATM in order to be connected to RNC.
RNC (Radio Network Controller): The RNC is the UMTS equivalent of the GSM BSC and GPRS PCU. It is
responsible for RRM (Radio Resource Management) and control of the node Bs.
RNS (Radio Network Subsystem): The RNS is composed of one RNC and its associated node BTSs.
A UTRAN is composed of several RNSs. An RNS covers a certain geographical area and is equivalent to
the GSM BSS.

9 RNC
319

9 RNC
9.1 9370 RNC in ATM Configuration

In the Alcatel-Lucent solution, the RNC is made up of a Control Node, an Interface Node
and an optional network element called the PoC (can be used for PCM to STM-1
conversion).
RNC functionalities
Iub/
STM-1
Iu-CS
9370 RNC
Iub/E1
ATM
backbone
BTS
STM-1
Iu-PS
SGSN
ATM
backbone
C-Node
I-Node
Iur
RNC
STM-1
PoC
BTS
MSC
(Point of
Concentration)
BTS
OAM
link
Conversion for
E1 transmission
OMC
3 1 10
In the Alcatel-Lucent UTRAN architecture, two different types of RNC configurations can be
implemented in the network according to the physical links used by the operator. The first type is the RNC
in full ATM Configuration. The RNC with ATM Optical interfaces (SDH/SONET technology) allows the
operator to directly connect the RNC to the Nodes B through the Iub interface based on an OC-3/STM-1
optical link up to the ATM backbone. In this case, the electrical link for E1/T1 frames covers the second
part of the Iub interface, from the ATM backbone down to the Nodes B.
A Point of Concentration (PoC) associated to the RNC can offer direct PCM connectivity (E1/T1) along the
Iub interface. However, this solution requires an additional equipment which is the A7670 platform (and in
some configurations we use the POC PP7K). This equipment supports electrical links for 120 and 75 E1
frames.
In both cases, the Iu (toward Core Network) and Iur (toward a neighboring RNC) interfaces are based on an
OC-3/STM-1 optical link.
OAM connection to the Wireless Management System (WMS) can be managed with an Ethernet link to a LAN
or In-band through the ATM backbone.

9 RNC
9.2 9370 RNC evolution to IP
Iub/
STM-1
STM-1
Iu-CS
Alcatel-Lucent
RNC
Iub/E1
BTS
MSC
Iur
ATM
backbone
ATM
backbone
Other
RNC
9370 RNC
Fast-Ethernet
Itf-R
Itf-B
IP
backbone
IP
backbone
Giga-Eth
OMC
Giga-Eth
SGSN
Iu-PS
3 1 11
The second type of RNC Configuration supports IP transport on the Iub and Iu-PS interface.
A native IP Iub interface is introduced through a software upgrade and the addition of two 4-ports Gigabit
Ethernet boards on the RNC connected to the IP backbone. In this case, Fast Ethernet frames covers the
second part of the Iub interface, from the IP backbone down to the Nodes B.
IP over Ethernet interface is used to carry HSDPA/HSUPA best effort traffic type (Interactive and
Background). No forklift is required and the existing STM-1 boards can be used for any interfaces that
remain on ATM transport: R99 services and Streaming on HSDPA, newly introduced in release UA06, is
transported over the Iub ATM based interface.
IP over Ethernet is also used to convoy the packet data over the Iu-PS interface toward the SGSN by using
the 4-ports Gigabit Ethernet boards on the RNC. The voice and video calls remain on the Iu-CS ATM based
interfaces.

9 RNC
9.3 9370 RNC Presentation

Power Carrier Grade Platform
SDH configuration (MSS15K):
C-Node / I-Node
on MSS 15K
single cabinet
16 STM-1 connectivity
IP configuration:
9370 RNC
Hybrid Iub and Iu-PS

4 Giga - Ethernet connectivity
Option with PoC or a

2nd 9370 RNC
Scalability: 5 models available
Capacity
Up to 2400 Node B, 2400 cells,
8000 Erlangs per RNC
Low-level telecom
User plane processing
Interface termination (STM-1 and Giga-Eth)
Call processing
Shelf/platform management
3 1 12
The Alcatel-Lucent RNC is called the RNC 9370. The 9370 RNC is implemented on an MSS 15000 (15K)
platform that provide both I-Node and C-Node functions in a single shelf.
The I-Node or Interface Node, with its 16 STM-1 connectivity and 4 Giga Ethernet connectivity, allows to
connect up to 2400 Nodes B and 2400 cells.
The C-Node or Control Node offers the processing capabilities of 8000 Erlangs.
Optionally a Point of Concentration or a 2nd 9370 RNC can be put in the upper shelf.

9 RNC
9.4 9370 RNC Architecture

Network Management
OC3/
OC3/ STMSTM11 FP
FP
CP3
CP3
CP3
CP3
Fabric
Fabric
Fabric
Fabric
. . .
PC
PC
PC
PC
Master
Master
Master
Master
2 per RNC
OMU
OMU
OMU
OMU
2 per RNC
NI
NI
NI
NI
RAB
RAB
RAB
RAB
TMU
TMU
TMU
TMU
. . .
. . .
OC3/
OC3/ STMSTM11 FP
FP
Packet Server
(physical view)
ATM
PC
PC
up to 12
IP
2 per RNC
RAB
RAB
up to 40
TMU
TMU
up to 14
PS Functions (Logical view)
Iub, Iur, Iu
3 1 13
The RNC application runs on 6 PCI Mezzanine Cards (PMCs) on the Packet Server (PS) module. These PMCs
are application independent.
On the 9370 RNC, six PMC roles are supported:
Master (PMC-M): used for the management of all others PMCs.
Protocol Converter (PMC-PC): Segmentation and Reassembly (SAR) functions.
Radio Access Bearer (PMC-RAB).
Network Interface (PMC-NI).
Traffic Management (PMC-TMU).
OAM Management (PMC-OMU).

9 RNC
9.5 Distribution of PMC function according to PS-FP card

slot Card/Pm c
0
0
CP
1
CP
2
PSFP PMC-M
3
PSFP PMC-M
4
PSFP
RAB
5
PSFP
RAB
6
PSFP
RAB
7
PSFP
RAB
8
OC3
9
OC3
10
PSFP
RAB
11
PSFP
RAB
12
PSFP
RAB
13
PSFP
RAB
14
PSFP
RAB
15
PSFP
RAB
PMC ID within PSFP

1
2
3
TMU
TMU
TMU
TMU
TMU
TMU
RAB
RAB
NI
NI
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
PC
PC
PC
PC
PC
PC
RAB
RAB
OMU
OMU
RAB
RAB
TMU
TMU
TMU
TMU
TMU
TMU
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
RAB
PC
PC
PC
PC
PC
PC
RAB
RAB
TMU
TMU
RAB
RAB
Roles
Rolesare
arefixed
fixedby
byRNC
RNCsoftware
software
3 1 14
The distribution of the PMC role according to the PSFP cards are shown in the table above.

9 RNC
9.7 PS- FP Functions

Packet Server FP
PMC-TMU
OA&M
OA&M
PMC-OMU
UMTS Call Processing

Call
Processing
Data server
Node Bs
Management
UE Management
Radio Resource
Management
RNC
Management
Network Interface protocol termination

NBAP
Iub
RANAP
RNSAP
Iur
3 1 15
Iu
Performance
Configuration
and Fault
Management
Overload and
Load balancing
Management
Two new functions, previously assumed by the Control Node, are now introduced in the PS-FP:
Traffic Management: the TMU-R FP software is provided by the PMC-TMU:
It terminates radio network interface protocols (RANAP, RNSAP, NBAP...).
It supports RRM (RRC, Always-On, QoS management, Call Admission, iRM scheduling).
OAM Management: it manages the Control plane functions of the 9370 RNC:
Performance, Configuration and Fault management
Call Trace management
overloads controls and load balancing of Control planes resources
radio network subsystem OAM&P.

9 RNC
9.8 RNC Fault Detection Mechanisms

PMCs on PS-FP
M
NI
RAB
TMU-R
PC
OMU
WMS
Interface
Node
Fabric
FabricModule
Module
PS-FP
MDM
Alarm Display
CP3
3 1 16
OC3 / STM1
The equipment described here is the 9370 RNC.

A major alarm is raised when the OSI state of one the following boards is unlocked / disabled / failed:
Fabric, CP3, OC3/STM1 and PS FP boards for the Interface Node and POC (Passport).
The OMU (Operation & Maintenance Unit) is in charge of the following functions:
Monitoring of Control Node elements
Disk management
Ethernet access to Preside platform and TML (through TCP/IP links)
OA&M functions
The Control Processor board (CP) manages and controls the Interface Node applications supporting both
system and network functions.

10 POC (pp7k)
3 1 17

10 POC (pp7k)
10.1 POC Architecture (based on Passport7k)
STM1 to 9370 RNC

(Interface Node)
9370
RNC
STM1/OC3
Optical link
Iub
E1s to sparing panel

(and then to BTS)
POC
POC
E1
Electrical link
Iub
CP2
MSA32
/STM1
MSA32
Node B
3 1 18
The 9370 RNC platform only supports the ATM transport network through OC3/STM1 links, thus to provide
PCM connectivity, on the Iub interface, there is a need for a specific additional equipment, unless the
Operator provides their own ATM backbone.
The Alcatel-lucent (previously Alcatel-Lucent) Point of Concentration is needed to physically convert the
STM1 links from the Interface Node into PCM links, so that Node Bs with E1 interfaces can be connected to
the RNC.
The Point of Concentration has been selected among Alcatel-lucent switch range: it is based on the
Passport 7480 or 7670.
This equipment has to carry out the translation from OC-3/STM-1 to E1 format, based on PCM frames. More
precisely, it must convert the STM1 links from the 9370 RNC into PCM links, so that Node Bs with E1
interfaces can be connected to the RNC.
This additional equipment has to be co-localized with the 9370 RNC.

11 POC (7670)
3 1 19

11 POC (A7670)
11.1 Situation
3 1 20
The EMS of the Transport Node 7670 RSP/ESE is called the 5620 NM. It is required to
be deployed on its dedicated HW machine since the scope of the integration is
limited to Fault management. The functions such as NE configuration, NE
performance, NE security and NE administration are handled by the EMS 5620 NM.

11 POC (A7670)
11.2 Integration in WMS

WMS provides integrated Fault Management support for the Transport
Node 7670 type ESE (small/medium) and RSP (medium/large). On the
WMS GUI, the user is seeing one icon representing the Transport Node
7670 RSP/ESE.
WMS Server
Fault and Topology Infrastructure:
HFB, Enh FM, Alarm correlation,
Layout, etc
SNMP
FM Flow
5620 NM
7670 RSP/ESE
3 1 21
The following are the key benefits offered by this feature:

Device Discovery
NSP Layouts
First Alert Fault Management (in both Resource Browser and Alarm Manager)
In-context reach-through to the devices or any associated EMS as appropriate
from the NSP desktop
Support of northbound CORBA Fault and NE Discovery OSS Interfaces

11 POC (A7670)
11.3 Icon
Alcatel 7670 RSP and ESE are declared and managed as separate network
elements. It must be visible from Network layout/Grid layout and
declared to NSP. Particularly In access EMS, it is now considered as a
standard NE.
These NE types have the following characteristics:
The icon should be the same than the one actually used for the POC for
both ESE and RSP
A specific access NE type is declared for this kind of Network element
3 1 22
For the alarms concerning the 7670 transmission node :

Alarm Code format
The alarm code uses the faultCode field as seen in the alarm record details. It specifies the
alarm
type according to the following generic pattern:
[Equipment type]_[Alarm code on 4 digits (0-9)]_[MO Object Id on 5 digits (0-9)]
where
"Equipment type" is OAM, ESE or RSP
"Alarm code" is the alarm code of the equipment type
"MO Object Id" is the Managed Object Id of the alarmed component.

11 POC (A7670)
11.4 Contextual menu

WMS provides integrated Fault Management support for the AlcatelLucent 7670 Transport node (ESE and RSP types):
New objects in RAN model (ESE / RSP)
New icon in resource browser:
3 1 23
Associated contextual menus contain the following items:

Show Alarms and Show Alarms in New window:
7670 Alarms are managed in Alarm manager (filters, rules, on-line help,
audible alarms)
5620 EMS: In context launch of the 5620 EMS (from an XSession window): AlcatelLucent 5620 is the dedicated Alcatel-Lucent 7670 product line EMS. It offers
functionalities to perform: Observation collection, CM management, Fault management
and Network element upgrade management.
Telnet on NE: launch a telnet session with the 7670
Configuration / setOAMLinkAdministrativeState: lock / unlock the OAM administrative
link.
Configuration / CM XML / Export NE: Export 7670 configuration data.
Fault / Notification Log Tool: 7670 Alarms are managed in NLT
Information: User Label, type (ESE/RSP), SNMP Version used, description, and IP
address information in a specific window.
Set Maintenance Mode On

12 BTS
3 1 24

12 BTS
12.1 UMTS Node B Functions

Call Processing
Radio access and Modem

DDDDDDDD
12345678
1 2 3 4 5 6 7 8
Coding
Cell
management
Management of
common channels
Interleaving
Management of
dedicated channels
01
Power
control
11
QPSK
Softer Handover
Measurement
processing
00
10
Modulation
Network Interface
3 1 25
D DD D DD DD
123456 78
00
2
00
2
10
4
10
4
01
7
01
7
11
3
11
3
Demodulation
Synchronization
The UMTS BTS supports the following basic functions:
Call processing: channel setup and management for both common and dedicated channels, cell
management, power control, softer handover and measurement.
Radio access and modem: modulation/demodulation, frequency up/down-conversion, amplification.
Network interface: interface management with the RNC, optional interfaces for enhanced capacity
or remote network connectivity.
Synchronization: to retrieve a highly stable radio frequency from the network interface.

12 BTS
12.2 UMTS BTS Block Diagram

Sector 2
Sector 1
Sector 3
RF Feeders
BTS
Power supply:
- 48 V DC
AC main
RF block
TX amplification
coupling
Interco
module
RNC
Rx
signal
Tx
signal
Digital shelf
Iub
Network interface
Call processing
Signal processing
Frequency up/down conversion
3 1 26
External
alarms
The BTS is built around 2 main blocks: the Digital shelf and the RF block.
The main functions of the Digital shelf are:
network interface,
call processing,
signal processing,
frequency up/down conversion.
The main functions of the RF block are:
TX amplification,
coupling.
The Interco module is a passive module that carries digital signals between the two blocks.

12 BTS
12.3 BTS Architecture

45W 60W amplifier
3-carrier capable
CDMA baseband signal processing

Dynamically shared 6 carriers
Common/Control functions,
OAM management, switching, routing
Node B
RF Block
TMA
(option)
DDM
Digital Block
MCPA
xCEM
TMA
(option)
DDM
MCPA
TMA
(option)
DDM
MCPA
RF interconnection panel
Iub
xCCM
RNC
xTRM
Modulation/Demodulation, Power control/detection

3x15MHz Transmit Chains, 6x10MHz Receive Chains
3 1 27
All the modules included in the cabinet, can be gathered into two separate units depending on the role
played in the BTS:
The Digital shelf: CEM, CCM, TRM, GPSAM.
The RF block: DDM and MCPA.
The main functions of the Digital shelf are the following ones:
The call processing and the transmit and receive baseband signal processing functions are performed
by the CEM/iCEM (Channel Element Module).
The OAM management and part of the call processing and internal/external data flow switching /
combining is carried out by the iCCM/xCCM (Core Control Module).
The receive / transmit channelizer function and the support of radio shelf connectivity interface
goes to the iTRM/xTRM (Transmit Receive Module).
The external / internal alarm connectivity and the external synchronization reference interface is
achieved by the GPSAM/cGPSAM (GPS and Alarm).
The main functions of the RF block are the following ones:
The RF signal amplification is performed by the MCPA (Multi-Carrier Power Amplifier).
The isolation of Tx / Rx frequency bands as well as the filtering is done by the DDM (Dual Duplexer
Modules).

12 BTS
12.4 Alcatel-Lucent NodeB Product Family

Standard Node B Solutions
Distributed Node B Solutions
Macro
Indoor & Outdoor
d2U
RRH 40W
Street
Compact
RRH 60W
Multi-Standard
BTS (2G/3G)
3 1 28
In the Alcatel-Lucent Portfolio, a large range of Node B product exists. There is always a Node B solution
whatever the coverage or the capacity issue the operator is facing.
The Macro BTS solution allows to provide high capacity and large coverage with indoor and outdoor
solutions. The compact Node B solution also exists when the operator is facing space issue on site.
The Distributed Node B solutions allow to optimize power and capacity at the antenna when facing
coverage issue such as high feeder length or provide hot spot for indoor location solutions.

12 BTS
12.5 Distributed NodeB Portfolio

9341 RRH40-21
(2100 MHz and AWS)
9341 RRH40-08 (850 MHz)
RRH40-19 (1900 MHz)
High power compact

RRH: 40W/60W,
3 carriers
High power compact

RRH: 40W/60W,
2 carriers
230W power
consumption
34 litres 22 kg
9326 Digital 2U Node B

(9326 d2U)
24 litres 19 kg
3 1 29
For locations with limited space such as urban rooftops, at top mast near the antenna or water tower sites,
installation of a Distributed Node B is the solution.
In the Alcatel-Lucent Distributed Node B portfolio, you can use a 9326 Digital 2U Node B (9326 d2U), which is
a rackable solution that can be integrated into existing cabinets for easy and quick deployments and used in
combination 9341 RRH modules.
9341 Remote Radio Head (9341 RRH) enables remote placement of the radio modules and filter functions used
near the radiating antenna, the rooftop or at ground level, connected with any digital unit via optical fibers.

12 BTS
Rectifiers
alarms
12.9 BTS Fault Detection Mechanisms

Interco
Door
alarm Alarms,
User area
alarms
LP Box
&
AC main
SPCM
alarms
DACS alarms
inventory and presence detection for non CPU modules
O&M bus (1-wire bus)

11 wires
to the
Digital
Shelf
boards
GPSAM
MUX
Backplane
External
alarms
ASIC / FPGA (1-wire master)

CCM
For FPGA
Downloading
W-NMS
IRQ
Host CPU
On the iCCM
IRQ
IC
IC
Host CPU
master
iCCM/xCCM
On the iCCM
Alarms, inventory and presence detection

for CPU modules
TRM
OMC-B
3 1 30
The GPS and Alarm Management module (GPSAM/cGPSAM) provides two different functions:
collection of the information about the state of the BTS: alarms, inventory and presence of FRUs,
commissioning information,
supply of timing information (optional).
Alarm and inventory management: according to the BTS modules, the GPSAM collects the alarms and/or
the inventory information. The inventory information allows the OAM access to know the state of the
BTS and its hardware composition.
Alarms, remote inventory information, and commissioning information are collected through a O&M bus
(Dallas type) and then are stored by the GPSAM.
The O&M bus is connected to the internal modules of the BTS: GPSAM, cooling unit, rectifiers, SPCM, AC
main or plinth, AC box, interconnection module, external alarm protection module, lightning
protection module, BIP (BTS Indoor), and MCA.
The GPSAM collects a part of the alarms of the BTS:
internal alarms,
16 external alarms, that are open current loops,
6 remote control loops (relays).
The CCM manages the GPSAM through an I2C bus (backplane).

13 OAM Links
3 1 31

13 OAM Links
13.1 Checking the OAM-NE Link
3 1 32
Before dealing with any supervision activity there is a need to insure that the information displayed at the
Preside level are correct. The NEs which are painted in blue in the Network view (unknown status) are not
connected to the OAM servers.
This could mean that:
The OAM modules in charge of the management of this NE are in trouble. Thanks to the OAM
supervision mechanism, this is a temporary state as the processes that are crashing are automatically
re-launched. Then, in such a case, the icon color switch from blue to an operational color
automatically. This can takes several minutes to go back to an operational color.
Real link supervision between access module and MDM is not managed. Use MDM toolset in such
situation to check if MDM processes are up and running.
The OAM link Administrative State has been locked, but in this case there is a warning alarm on the
NE. To unlock/lock, use right click -> Configuration -> Set NE's OAM Link Admin. State to consult
current state or to unlock the object.
There is a transmission problem between the NE and the OAM server.

13 OAM Links
13.2 End to end Alarm Flows

PA,
Tx Splitter
DDM
TRM
BTS
CCM
CEM
Uu
Iub
POC
MSA32 / PCM
CP2
Towards Core
Packet / Circuit
MSA32 / Optic
Iu
16PoC3 / Optic
Iur
Processing Board
RNC1500
Interface
Node
Other RNCs
CP3
OAM Network
3 1 33
The diagram above represents the various interfaces between all the modules in the UTRAN subsystem,
which is part of the UMTS end-to-end network.
The NEs are not precisely described here but sum-up the various connections between modules from the
OAM to the BTS.
This diagram gives an example of topology of the network.
The various modules of RNC can be connected differently. Only the 9370 RNC is shown here.
The boards that communicate together are always the same ones.

13 OAM Links
13.3 IP Sub-Networks
W-NMS
Desktop GUI
(NSP client)
LAN
OAM Sub-Network
Out-band
configuration
In-band
configuration
IP/ETH
IP/ETH
BTS OAM Sub-Network
POC
RNC
OAM UTRAN Sub-Network

(Optional)
ATM
Switch
BTS
IP/ATM
3 1 34
Preside manages all the parts of the UMTS equipment. The OAM information is transported over IP subnetworks.
Here are two types of UTRAN / OAM IP networks:
a dedicated one connecting Preside platform, the ATM Switch, and (according to the configuration
type) the RNC,
two other ones in an in-band configuration connecting the BTS with the RNC, and (optionally) the
RNC with the ATM Switch. In that case, IP is implemented over SDH (optical fiber) and PCM.
Two OAM configurations are available:
Out-of band configuration: the BTS OAM information goes to the RNC through the POC, then BTS,
POC and RNC OAM information go the NSP through the dedicated OAM network.
In-band configuration: the BTS OAM information goes to the RNC through the POC, then BTS, POC
and RNC OAM information go to the MGW (in-band over the optical fibers) and are rerouted towards
the OAM Sub-Network. No link is needed between the RNC, the POC and the OAM sub-network.

13 OAM Links
13.4 Remote Launch of OAM Support

Fault Management
Resource Display
Alarm Manager
OSS
Remote
Access
W-NMS
Desktop GUI
(NSP client)
LAN
W-NMS
servers
FM, CM, R-T PM

PM
Primary
Secondary
Main
Main
Server
Server
Perf.
Server
(option)
NEs
Node B
3 1 35
RNC
POC
(IN+CN
inside IN)
Definition
The Operation Sub-System (OSS) is in charge of the control and management of the UMTS Network.
The OSS contains the Operation and Maintenance Center (OMC).
Remote launch
Starting from OAM 5.0, the operator is able to launch the W-NMS GUIs in context, from an OSS. There
are 2 options provided, the NE context launch, and the alarm manager context launch:
Within the NE context launch, if implemented at the OSS, the W-NMS Network Resource Display
can be opened with the context of the NE specified in the OSS interface. The layout and the
group for the specified NE is opened and the NE selected.
The Alarm Manager context launch is an extension to the NE context launch functionality. If
the OSS optionally provides the alarm context, the Alarm Manager is opened with the particular
alarm selected. The group of the NE on which the NE on which the alarm occurred will also be
opened similarly to the NE context.
The main benefits of this feature is to enable a flexible and easy manner to remotely access W-NMS
fault management capabilities.

13 OAM Links
13.5 Identification Parameters (NEId)

Serial Number
& Internal IP
Address
Node Name
& IP Address
Node Name
& IP Address
( IN physical)
POC
Interface Node
2 OMU
IP Addresses
(CN virtual)
Control Node
BTS
IP Network
W-NMS
3 1 36
An identification system, based on Key Parameters, has been designed to allow the operator to check that
one given network element (NE) is taken in charge by the OAM platform.
The Passport (Interface Node, POC) identifier is the NodeName attribute.
The IN simulated Control Node identifier has the IP adress of the 1st OMU PMC, patched into the MIB.
The BTS equipment is identified by its serialization number which is a unique manufactured value for
each BTS (stored in the MCA Module).

How to Do it
3 1 37

Discover
3 1 38

3 1 39

Exercise
RNC Equipment Monitor
EXAMINING THE RNC WITH THE TOOL

Launch the tool Equipment Monitor to supervise one identified RNC.
Is there any way to directly launch this tool through the Navigator?
Yes
No
Resource
management
How can you manage to do it?
Looking at a standard Access Network, the RNC object is most of time
the first object inserted in the layout.
RNC LOGICAL VIEW PART RNC is C-Note
What is the current software version of the RNC?
How can you get this information?
LP14,Lp15
NB:LAPS 128 is compining of Lp9+Lp8

PDR for the packet switch in SGSN
3 1 40

this should
have to Hup
switch if we
need good
redundancy
Exercise
Examine the logical view of the RNC and try to

explain the reasons why this tree-structure has
been chosen:
4500000000001000fffffffffffffff
The ATM address of the RNC is contained in the

rncNSAPAddress parameter. Could you find the
ATM address of our RNC?
Have a look at the RNCEquipment/0 -> CNode/0
object.
Could you explain the values of the two
parameters IPadress and SecondaryIPadress
10.100.30.4
parameter ? 10.100.30.3
Ip of the OMU PMC's
Now look at the PsCoreNetworkAccess object.
How many DscpPerTrafficClass objects can you
find? What do these objects stand for? What about
the DscpPerOlympicServices objects?
3 1 41

Exercise
RNC PHYSICAL VIEW PART

Please fill in the table below, using the
physical view of the RNC:
Board
In service CP
Stand-by CP
PSFP
Activation State
Card/1
unlocked
Enabled
unlocked
unlocked
Enabled
Enabled
unlocked
Enabled
Card/0
Card/2,3,4,5
16pOC3/STM1
Location
card/8,9
car/14,15
BoardLocationActivation StateOperational
StateIn service CP Stand-by CP PSFP
16POC3/STM1
Whats the meaning of the letter w shown
on a board ?
Can you launch these configuration & fault
tools to control all the boards?
Yes
No
3 1 42

Operational State
Providing
service
Hotstanby
Providing
providing
Exercise
Now, go to the Interface Node thumb. Can you launch the configuration &
fault tools to control all the boards?
Yes
No
What is the IP address of the Interface Node (CP board)?
Did you find this information ? Yes
No
3 1 43

Exercise
OPERATIONS
Make sure that we can lock a BTS (NodeB) from the RNC (dont do it!). Of
course, you must first select the FDDCell object, then click on configuration
set Administrative State.
When you have to lock several BTS / sectors belonging to the same RNC, it is
easier to first launch the RNC Equipment Monitor and next to select the
FDDCells and to lock them.
OPERATIONS PERFORMED FROM THE OBJECT EDITOR
Click right on the RNC and open the object editor. Whats the value of the
CnodeCapacity ? Could you explain the use of this parameter ?
3 1 44

Exercise
COMPONENT ADMINISTRATION SYSTEM (CAS)

Now, look at the Interface Node part of the RNC and examine the tree-structure :
How many objects can you find? What do these objects stand for?
Do you know one another method to find these types of information ? Explain it in a
few words
The trainer will give you now several usefull informations concerning CAS usage.
3 1 45

Exercise
EXAMINING THE BTS WITH THE TOOL
Launch the Equipment Monitor tool to supervise one BTS.

Is there any way to directly launch this tool through the Navigator?
Yes
No
How can you manage to do it?
What model of BTS is this?
How did you find this information?
Try to find the IP address of this BTS. Write it down: 10.100.40.1
How did you manage to get this information?
Look at the value of supervisedExternalAlarmMask and write it down: oooooooooooo
o000000000
Same for the supervisedUserAlarmMask value:
What is the role of these parameters?

Where can you get help? customer documents
Examine the logical view of the BTS (similar to the one below) and try to
explain the reasons why this tree-structure has been chosen.
3 1 46

Exercise
Why do we find one arrow ( ) before the

Node B component?
Right click on this Node B component.
Can you access the Find in RNC Equipment
Monitor option?
Yes
No
Now launch the RNC Equipment Monitor
and have a look at both components in
the respective windows.
Result:
3 1 47

Exercise
BTS PHYSICAL VIEW
Looking at the physical view of the BTS equipment, please fill in the
chart below:
Board
Serial
Number
Location
Administrative
State
iTRM
iTRM
CEM
CEM
GPSAM
MCPA
DDM
DDM
DDM
3 1 48

Operational State
Exercise
BTS PHYSICAL VIEW
Right click on each board displayed in the window and check whether you can perform the various
operations or not. Dont necessarily launch them!
Object
Lock
Object Editor
DDM
iCEM
iTRM
MCPA
GPSAM
3 1 49

Reset
Exercise
BTS PHYSICAL VIEW
OPERATIONS PERFORMED FROM THE EM

In order to take some measurements, you will have first to lock either a BTS as a whole or some
sectors. By the way, we tend to say: to stop the BTS which is not true provided that the power is
still on.
When locking a sector, we can choose between two options:
lock the MCPA (from the graphical display part)
lock the FDDCell object.
Which one of these options seems to be the proper answer?
Why?
Starting from the Node B object, we are going to lock one FDDCell .
To perform this operation, first right click on this suite of options:
Configuration Set Administrative State Lock
Have a look at the alarms again. Any change?
Look at the BTS icon in the Resource Browser window.
Can you find the relevant alarm?
Why?
Never forget to write down the sites names or sectors that you have locked. It is not so obvious to
find them again and to unlock them afterwards.
Launch a telnet session upon the BTS from your PC client. Does it work properly? Why?
You can launch a telnet session upon the BTS (from the server). The trouble is that the BTS software
has been designed for one single telnet session at a time. If several users try simultaneously to
access the BTS, it becomes pretty awkward (try and see).
Now, the instructor is going to access the BTS. Pay attention to the commands he is going to enter:
Now, the instructor is going to unlock the BTS (from the Preside server, of course).
Now try again to perform the commands executed for question #14 (one group after each other).
What are the differences that you can notice?
This type of hands-on allows you to make sure that the concerned BTS is actually emitting.
3 1 50

Exercise
BTS PHYSICAL VIEW
OPERATIONS PERFORMED FROM THE OBJECT EDITOR

Click right on the BTS and open an object editor.
What are the different classes of parameters :
Is it possible to change the IP address and the serial number of the BTS ? How can you do it ?
3 1 51

Module Summary
3 1 52

3 1 53


for this module
3 1 54


#
#1
#2
Switch
to notes view!
O
O1
O2

A
A1
A2

P
P1
P2

B
B1
B2

Q
Q1
Q2

C
C1
C2

R
R1
R2

D
D1
D2

S
S1
S2

E
E1
E2

T
T1
T2

U
U1
U2

F
F1
F2
3 1 55
Full
Writing of Term F1
G
G1
G2

H
H1
H2
V
V1
V2


I
I1
I2
W
W1
W2


J
J1
J2
X
X1
X2


K
K1
K2
Y
Y1
Y2


Z
Z1
Z2

L
L1
L2

M
M1
M2

N
N1
N2


3 1 56

Glossary
#
#1
#2
A
A1
A2
B
B1
B2
C
C1
C2
D
D1
D2
E
E1
E2
F
F1
F2
3 1 57
G
G1
G2
H
H1
H2
I
I1
I2
J
J1
J2
K
K1
K2
L
L1
L2
M
M1
M2

Glossary [cont.]
N
N1
N2
O
O1
O2
P
P1
P2
Q
Q1
Q2
R
R1
R2
S
S1
S2
T
T1
T2
3 1 58
U
U1
U2
V
V1
V2
W
W1
W2
X
X1
X2
Y
Y1
Y2
Z
Z1
Z2

References
3 1 59

End of Module
3 1 60

Section 4
Analyse alarm
Module 1
Analyse alarm
9353 WMS

Blank Page
412
Analyse alarm Analyse alarm

Document History
Edition
Date
Author
Remarks
01
YYYY-MM-DD
First edition

Module Objectives
Describe
List
Explain
Identify ...
413


414


Table of Contents
Page

1 Name of Level 1
1.1 Name of Level 2
No Level
Text Boxes
Tables
Numbered Lists
Unnumbered List
Text and Graphic
Annotations
(1) Detail 1
(2) Detail 2
Main Colors
How to Do It
Discover
Exercise
415
Analyse alarm AnalyseSummary
alarm
Glossary
References
End of Module

7
8
9
10
11
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
37
39
40

416

This page

14 Alarm Correlation
417


14 Alarm correlation
14.1 Principle
Alarm correlation is an optional
application that performs alarm
grouping and finds dependencies
between root causes and symptoms
Alarm1
Alarm 2
Main
Alarm 3
NE Topology extracted from

CM data (XMLsnapshot) is used to
correlate alarms
418

Mobile Network operators are flooded by alarms raised by managed Network Elements. A
typical 3G network can produce more than 200000 alarms per week. To ensure an efficient
management and troubleshooting, it is critical to reduce this number and provide operators
with tools to easily spot alarms that are service affecting. Personnel can therefore
concentrate on few critical alarms and fix problems more efficiently.
Alarm Correlation consists in running pre-defined rules in order to group alarms in
Correlation Groups by setting to them the same CorrelationGroupId alarm attribute. There
is no alarm suppression.
Correlation rules group alarms when at least 2 alarms or more could be correlated, one of
them (1) is declared Primary Main alarm (the main root cause).
Other alarms of the group could be declared Main (other possible root causes)
orSymptom (consequence of Main or Primary Main alarm).
Some Topology links are used to correlate alarms, those topology relationships are
hierarchical links or relationship links between objects, components ). They are extracted
from WMS configuration (CM) data. This extract is automatic (every night) and reuses the
XMLsnapshot automatic generation. A manual command is available to force a topology
links refresh in case of reparenting
.

14.2 Example
operator
419

Alarms are tagged Main or Symptom or Main/Symptom (according to the context) by OAM
alarm enrichment feature from OAM alarm data model. This is a static definition.
Rules could change the type Main/Symptom depending of the context (e.g. main alarm on
the father object will force the alarm on the child object to symptom. Main Alarm should be
automatically cleared. An alarm without clear cannot be a main alarm.
Main Alarm:
A main alarm designates an alarm linked to a NE failure or a link failure that triggers
symptoms. When a main alarm is cleared, all associated symptoms shall be cleared.
Symptom Alarm:
Consequences of a Main alarm, for example most of the state changes alarms are
symptoms.
Topology link:
Link between NE or sub-equipment inside a NE helpful for alarm correlation.

14.3 Alarm manager

Correlation
Alarm Type
Column
Correlation
Group ID
Column
New Alarm
correlation
dialog boxes
Correlation
Group Count
Column
Alarm Correlation allows operators to focus on most service

affecting problems and improve troubleshooting efficiency
4 1 10

Three new columns to show new alarm correlation attributes have been added. If alarm is
not correlated
those columns are set to -.
The Correlation Alarm Type column is highlighted with fixed colors as below.
bold white on dark blue for PrimaryMain
regular black on light blue for Main
regular black on grey for Symptom
The new columns could be moved in the same way as the existing columns do.
Sort capabilities have been extended to alarm correlation attributes.
New dialog boxes have been added to filter on PrimaryMain, Main, Symptom or
Uncorrelated alarms.

14.4 New actions in Alarm Manager

Expand All Groups in New Window:
Open in a new alarm browser all the
alarms with same correlation group Ids1
of current alarms list
Expand All Groups in current Window:

Inserts in the current alarm browser
all the alarms with same correlation
group Ids1 of current alarms list.
4 1 11
Expand Selected Groups in New Window:

Open in a new alarm browser all
the alarms with the same correlation
group Id1 of the selected alarms.
Expand Selected Groups in Current Window:

Inserts in the current alarm browser
all the alarms with the same correlation
group Id1 of the selected alarms

Expand Selected Groups in New Window: Open in a new alarm browser all
the alarms with the same correlation group Id1 of the selected alarms. Only correlated
alarms are shown. When no alarms are selected or selected alarms are not correlated,
these menu items are disabled.
Expand Selected Groups in Current Window: Inserts in the current alarm browser all
the alarms with the same correlation group Id1 of the selected alarms. Uncorrelated alarms
are still shown. When no alarms are selected or selected alarms are not correlated, these
menu items are disabled.
Expand All Groups in New Window: Open in a new alarm browser all the alarms with
same correlation group Ids1 of current alarms list. Only correlated alarms are shown.
When selected alarms are not correlated, these menu items are disabled.
Expand All Groups in current Window: Inserts in the current alarm browser all the
alarms with same correlation group Ids1 of current alarms list. Uncorrelated alarms are still
shown. When selected alarms are not correlated, these menu items are disabled.

14.5 Activation/Deactivation
The operator selects the rules to be applied among a list of
predefined rules
4 1 12

All rules are activated by default when the correlation feature is installed.
Rules of the same group respect the rule:
<Rule group name>_x with x is the rule number in the group
UTRAN_BTS_01 RULE GROUP
This rule group correlates BTSEquipment alarms which generate RSI or audit NBAP message from BTS to RNC
and state change alarms on FDDcells (disabled failed /dependency and notinstalled).
The Primary Main is the BTSEquipment alarms or In case of BTS Loss of Supervision, the LoS alarm is the
Primary Main. State change alarms on FDDcells are Symptom Alarms.
The topology link RNC/NodeB/FDDCell <-> BTSEquipment/BTSCell obtained by the
CellId attribute equality is used for this rule.
UTRAN_BTS_02 RULE GROUP
This rule group correlates HSDPA or E-DCH (aka HSUPA) alarms with related FDDCell state changes (enabled
degraded). The Primary Main is the HSDPA or E-DCH alarms on
RNC/NodeB/FDDcell/HsdpaResource or RNC/NodeB/FDDcell/edchResource.
State change alarms on FDDcells are Symptom Alarms.
Same RNC/NodeB DN root on object path in the alarm component id field is used for
this rule.
UTRAN_RNC_01 RULE GROUP
This rule group correlates RNC board and transmission failure with related FDDCell
state changes (disabled failed / dependency, enabled degraded)
The Primary Main is RNC alarm on RNC/NodeB/ControlPort or
RNC/RNCEquipment/INode/EM/Atmif.State change alarms on FDDcells are Symptom Alarms.
Same RNC/NodeB DN root on object path in the alarm component id field
and NodeB <-> Atmif/VCC/VPT/VPC relationship are used for this rule.
14.6 Access rights for Alarm correlation
The administrator can

enable/disable the alarm
correlation rule management
for each role through the
Access Control GUI
4 1 13

Expand correlation group and access control:

The user is reminded in the following cases:
There are alarms not retrieved because of access control when opening Alarm Manager
triggered by expanding group.
The user will not be reminded if alarm update after Alarm Manager Window is
opened is not presented because of access control. E.g. a new alarm comes. It is
invisible in the Alarm Manager because the user is not allowed to see this alarm. But
we will not remind users about this because the Alarm Manager has been already
opened.
The user is reminder that he/she cannot Open Group over an NE in the Alarm
Manager because the user is not privileged to do this or the NE is not in the current
layout

14.7 UTRAN_BTS_01 / UTRAN_ONEBTS_01

RNC
RSI/ Audit NBAP
iBTS/oneBTS
Main
state change alarms on FDDcells

(disabled failed / dependency).
Symptom
4 1 14

These rule group correlate BTSEquipment alarms which generate RSI or audit NBAP
message from BTS (iBTS/oneBTS) to RNC and state change alarms on FDDcells (disabled
failed / dependency and notinstalled).
The Primary Main is the BTSEquipment alarms or In case of BTS Loss of Supervision, the
LoS alarm is the Primary Main.
The topology link RNC/NodeB/FDDCell <-> BTSEquipment/BTSCell obtained by the CellId
attribute equality is used for this rule.
NBAP Audit
The audit is to ensure that the configuration of the logical resources are the same in the RNC
and Node B, after a link failure, NBAP message timeout, NBAP protocol reset, full or partial
node restart.
RSI
Resource Status Indication : a message sent from the NodeB to indicate changes in the
resources availability.

14.8 UTRAN_BTS_01 / UTRAN_ONEBTS_01
Symptom
RNC
state change alarms

on FDDcells
(degraded)
EdchResources Alarm
(or HsdpaResource)
Main
4 1 15

These rules group correlate HSDPA or E-DCH (aka HSUPA) alarms with related FDDCell
state changes (enabled degraded).
The Primary Main is the HSDPA or E-DCH alarms on RNC/NodeB/FDDcell/HsdpaResource or
RNC/NodeB/FDDcell/edchResource.
Same RNC/NodeB DN root on object path in the alarm component id field is used for this rule.
.

14.9 UTRAN_RNC_01
RNC
Atmif is reporting
alarm
FDDcells are disabled
Main
Symptom
4 1 16

This rule group correlates RNC board and transmission failure with related FDDCell state
changes (disabled failed / dependency, enabled degraded).
The
Primary
Main
is
RNC
RNC/RNCEquipment/INode/EM/Atmif.
alarm
on
RNC/NodeB/ControlPort
or

Same RNC/NodeB DN root on object path in the alarm component id field and NodeB <->
Atmif/VCC/VPT/VPC relationship are used for this rule..

15 Select Item Help
4 1 17


15 Select Item help
15.1 On-line Contextual Help
Example of online-help sent

by the Alarm Library
4 1 18

Thanks to the on-line help, some significant advice and recommendations can be provided to the OAM staff
within Preside NSP applications.
Right clicking the mouse from the Alarm Manager will lead through the Show alarms submenu to the
relevant description of the alarm.
More precisely, the concerned alarm points at the right Customer Documentation volume which contains
the list of alarms, thanks to the alarm code number.

16 FM Audit Request
4 1 19


16 FM Audit Request
16.1 FM Audit Request
4 1 20


16 FM Audit Request
16.2 RNC Active Alarm Management
NSP GUI
NSP
Client
Alarms
RNC
BTS
BTS
BTS
.
RNS 1
4 1 21

This feature ensures that the operator can access the current view of active alarms on the RNC after
OAM link reconnection: the link between the OAM platform and the RNC was broken and then
recovered.
With this feature in UA05.0 / OAM5.1, the RNC sends the complete list of active alarms to the W-NMS
system as soon as the OAM link is recovered.
Feature Benefits:
Customer benefits from the RNC active alarm list support in the context of an OAM disaster recovery.
This increases the OAM global availability by allowing quicker alarm re-synchronization between the
NE and the OAM system.
This feature has the following benefits:
The Operator has an accurate view of the active alarms on the RNC, after an OAM connection to the
RNC is interrupted.
RNC Interface Node proxy alarms which were used in previous releases to cover cases where an
alarm caused an OSI state change prior to the OAM connection being broken are not required.
Alarms that do not result in an OSI-state change of a provisioned component are included in the
active alarm list. Previously, these alarms were lost when the OAM connection to the RNC was
interrupted.

16 FM Audit Request
16.3 FM Audit Request Result
4 1 22


17 Notification Log Tool
4 1 23


17 Notification logs tool
17.1 Notification Logs
Detailed information
related to the currently
selected notification
4 1 24

The Notifications Log Tool is used to display the notifications log / notifications history.
This tool has been designed to help the user to:
Enter filters to limit the amount of displayed notifications
Easily navigate among all the displayed notifications (Navigation part, sort by column, Find)
Each time the user launches a command (Build, Audit, Reset, Set Administrative State, Set OAM Link State),
2 lines are written in the log file:
The first one indicating that a command has been launched on a particular Network Element
Another line telling that the command has ended (either successfully or not).
All the errors that occur during a session are written in the appropriate log files:
RadioAccessGUIClient.log
RadioAccessClientErrors.preside.log

18 OSI State Reporting
4 1 25


18 OSI State reporting
18.1 OSI State Reporting

Last
update
date
List of NEs of the

layout with
number of their
sub-objects in
failed state
RNC
Node B
Current
progression
List of sub-objects of
the selected NE in
failed state, with their
OSI states.
Progression
control
buttons
4 1 26

The NSP Fault applications are based on OSI node state indicators designed to identify the operational,
usage, and administrative state for all objects.
The OSI state reporting window describes the states of the BTS and the RNC parts of equipment
belonging to the current layout.
In order to allow the user to focus on the potential problems encountered in the network, the OSI State
Window only displays the bad states.
A bad state is different from the following nominal OSI state combination:
Administrative
unlocked
Operational
enabled
Availability
idle
Control
idle if present
Standby
providing service if present
The OSI state reporting window can lead either to the Equipment Monitor or to the Resource Brower
through the FindBTSEquipment searching option.

18 OSI State reporting
18.2 Passport OSI State & Status Attributes

Values
Attributes
OSI
State
OSI
Status
Operational state
enabled, disabled
Usage state
idle, active, busy
Administrative state
unlocked, locked, shutting down
Alarm status
empty, under repair, critical, major, minor, alarm,

outstanding
Procedural status
empty, initialization required, not initialized,

initializing, reporting, terminating
Availability status
empty, in text, failed, power off, off line, off

duty, dependency, degraded, not installed, log full
Control status
empty, subject to test, part of services locked,

reserved for test, suspended.
Standby status
not set, hot standby, cold standby, providing

Service
Unknown status
true or false
4 1 27

OSI States
These fields describe the possible OSI states. Passport uses component state definitions according to the
OSI standards. Components that do not provide any behavior do not require any component state variables
defined.
A component has three high-level state variables:
operational state,
usage state,
administrative state.
These states are the primary factors affecting the management state of a component.
OSI Attributes
These are additional OSI attributes, OSI status attributes, which provide additional information on
components operability and usage.
In general, only the component that fails or detects the failure generates the alarm. A fault on a
component may have an impact on other related components and may result in the generation of a chain of
alarms.
To avoid this problem, those components impacted by a fault on the component that generated the alarm,
will generate a State Change Notification if at least one of the OSIOperationalState or OSIProceduralStatus
attributes has changed.

States of RNC & related objects
This diagram gives the different states of the RNC, focusing on the Control Node side (operational,
administrative, availability).
It shows the dependency between the objects, from bottom to top.
Obviously, this tree is similar to the left part (logical objects) of the Equipment Monitor window.
It helps the Access Network supervisor correlate the alarms and eventually identify the root cause.
RNC
InAccessOp
erationalState
operationalState
PsCoreNetworkAccess
AvailabilityStatus
OperationalState
CsCoreNetworkAccess
AvailabilityStatus
OperationalState
NeighbouringRnc
AvailabilityStatus
OperationalState
RouteSet
AvailabilityStatus
OperationalState
AvailabilityStatus
OperationalState
PerfScanner
administrativeState
RNC MIB
MIBState
RNC equipment
OAM linkAdministrativeState
UnknownStatus
upgradeStatus
INODE
AvailabilityStatus
OperationalState
UnknownStatus
upgradeStatus
ANODE
AvailabilityStatus
OperationalState
UnknownStatus
upgradeStatus
NodeB
administrativeState
SignallinLink
FDDCell
AdministrativeState
AvailabilityStatus
OperationalState
ControlPORT
AvailabilityStatus
OperationalState

States of BTS & related objects
The diagram above shows the supported states and dependency relationship for the BTS object and its
sub-trees.
Supported BTS boards: CCM, CEM, TRM, RRH, CxCOIM.
Supported passive components: GPSAM, MCPA, DDM, TX SPLITTER.
A mapping may be required at OAM level on BTS slots for 600mm and street BTS.
This diagram helps the Access Network supervisor correlate the alarms and eventually identify the root
cause.
BTSEQUIPMENT
OAMLinkAdminState
unknownStatus
PCM
AdministrativeState
AvailabilityStatus
OperationalState
BTSEquipmentSoft
UpgradeStatus
BOARD
AdministrativeState
AvailabilityStatus
OperationalState
StandbyStatus
PassiveComponent
AdministrativeState
AvailabilityStatus
OperationalState

19 Object Display meaning
4 1 30


19 Object display meaning
19.1 Object State Display
Administrative & Operational

MIB State & Activation State
4 1 31


Physical objects: Combining administrative and operational states
The administrative state attribute is single valued and read-write. It can have one of the following
values, not all of which are applicable to every class of managed object:
locked: The resource is administratively prohibited from performing services for its users. In
other words, the operator has decided to temporarily lock the OAM link, that is the connection
between the OAM system and one specific NE.
unlocked: The resource is administratively permitted to perform services for its users. This is
independent of its inherent operability.
The operational state attribute is single-valued and read-only. It can have one of the following values:
disabled: The resource is totally inoperable and unable to provide service to the user(s).
enabled: The resource is partially or fully operable and available for use.
Operational: enabled
Administrative: unlocked
Operational: enabled
Administrative: locked
Operational: disabled
Administrative: unlocked
Operational: disabled
Administrative: locked
The resource is available

And has capacity to accept
Services from another source.
If active, the resource is in use.
The resource is available
but is administratively prohibited
from performing user Services.
The resource is not available
Or depends upon another source
that is not available.
The resource is not available
and its administratively prohibited
from performing user services.
The resource is not installed yet

or has been temporarily removed.
Availability: notInstalled
Physical objects: States and status display
notBuilt
builtUpToDate
no icon
builtNotUpToDate
Inconsistency
MIB
State
resetRequested
resetRunning
updateinProgress
activatedSynchronized
Not applicable
Activation
State
NotActivated
activatedDesynchronized
activatedSynchronizedWithErrors
Unset

no icon
20 Connection to NE (RNC)
4 1 34


20 Connect to NE (RNC)
20.1 Connect to the RNC
4 1 35

The Local Maintenance Terminal tool (TML) is the on-site maintenance tool used to perform the following
operations:
RNC local commissioning
tests after an RNC installation
an audit before an important operation
software or hardware upgrades
localization of any RNC problem
corrective maintenance.

20.2 CAS Commands to launch on the RNC 1/3
Check what version of software is

available on the CP hard drive
L sw av/*
Check what version of software is

running on the RNC
d sw avl
Check what are the

configured in the RNC
cards
d sh ca/* cardtype
Check what are the cards inserted

in the RNC
d sh ca/* ins
or
os pcsShowCards
Check if all the configured cards

are inserted
D sh ca/* cardtype , ins
4 1 36


To check if the CPs hard drivers are

synchronized
D fs
To force the synchronization of the two

CPs HDDs
Sync fs
To switchover the two CPs (the active

becomes stand by and vice versa)
Switchover lp/0
To lock a card
Lock sh ca/x
To unlock a card
Unlock
To lock an optical fiber
Lock lp/x sdh/y
To unlock an optical fiber

4 1 37
sh ca/x
Unlock lp/x sdh/y



Check the role of the atmif
D atmif/* remote
Check if the ATM circuits are up and

running
D atmif/* vcc/*
Check if we have traffic on the ATM vcc
D atmif/* vcc/* rxcell , txcell
To know what the role of an ATM VCC is
D atmif/* vcc/* vcd tag
Check if the LAPS is working
D laps/*
Check the state of the optical fibers
D lp/* sdh/*
List the optical fibers that are having a

problem
D lp/* sdh/(osioper != enabled)
Check if a BTS (or any IP address) is

reachable
Ping i(BTS IP address) vr/0 ip icmp

Note :
Use in the command vr/0 if you want to
check the BTS or the W-NMS availability,
and vr/1 to check if the SGSN cards are
reachable.
4 1 38


20.3 Components and Attributes Summary

Component Administration System (CAS) Root
LP/
(LogicalProcessor)
Sh
(Shelf)
mainboard
spareboard
logicalProcessorType(Lpt
)
RESET
board/
Bus/
Test
Eng
(Engineering)
RESET, RESTART,
LOCK, Unlock
LOCK, Unlock
Test
START, STOP
Enet/
(Ethernet)
DS/
(DataStream)
Test
agentQueueSize
START, STOP
Tidy
DELete, LOCK, Unlock
Framer
Eth100/
(Ethernet100BaseT)
Lpt/
(LogicalProcessorType)
featureList
interfaceName
Av/
(ApplicationVersion)
compatibleAvList
Remove
LOCK, Unlock
Test
Test
Vr/
(VirtualRouter)
NMIS
(NetworkManagementInterfaceSystem)
IpAccess/
Local
Telnet
LOCK, Unlock
adminState
maxAllowedSessions
activeSessions
Session/
userid
hostboard
loginTime
dataStreams
Ftp
LOCK, Unlock
Session/
Session/
userid
remoteIpAddr
remoteTcpPort
loginTime
dataStreams
userid
remoteIpAddr
loginTime
CLEAR
Ip
Fmip
Fs
(FileSystem)
ICMP
Session/
userid
remoteIpAddr
loginTime
dataStreams
CLEAR
Pp/
(ProtocolPort)
LOCK, Unlock
LOCK, Unlock
Ping
IpPort
Static
Route/
(RouteEntry)
LogicalIF/
(IpLogicalInterface)
netMask
broadcastAddress
Required component
DELete
Branch
Dynamic component
Nh/
(NextHop)
metric
Optional component
Top level component
Provisional Attribute
Operational Attribute
Verb1, Ver2,
4 1 39
volumeName
activeDisk
syncStatus
syncProgress
capacity
freeSpace
SYNChronize,
ListFile, Move, Copy,
REMOVE, Protect,
Unprotect,
MakeDirectory,Chdir,
LOCK, Unlock
AtmIf/
(AtmInterface)
CA
(Connection
Administrator)
Vcc/
(Agent)
AtmMpe/
()
Disk/
CLEAR
Legend
View/
User
checkState
formats
version
creationDate
baseView
components
TELNET, LOCK, Unlock
Userid/
ACTivate,APPly, Check,
CLEAR, COMMIT, Confirm,
Continue, Copy, End, Load,
Save, Start,
STOP, Tidy
Feature/
Mod
(ModuleData)
nodeId
nodeName
regionId
Override
ipAddressMask
password
commandScope
commandImpact
allowedAccess
allowedOutAccess
loginDirectory
Dld
(Download)
avBeingDownloade
d
status
filesToTransfer
avListToDownload
downloadedAvList
committedFileName
currentViewFileName
lastUsedFileName
provisioningSession
provisioningUser
editViewName
Start, Stop
Start, Stop
Start, Stop
agentQueueSize
Ac
(AccessControl)
avList
linkToProtocolPort
RESET, RESTART,
RELOADcp, SWITCHover,
LOCK, Unlock
boardType
operationalState RUN
insertedboardTypeclockSource
operationalState LOCK, Unlock
productCode
Prov
(ProvisioningSystem)
Sw
(Software)
La/
(LanApplication)
volumeName
capacity
freeSpace
FORMAT, LOCK,
Unlock
AC
NS
(NetworkSynchroniz.)
primaryReference
secondaryReference
tertiaryReference
clockSyncState
activeReference
standbyReference

This hierarchic tree structure shows the relationship between the components included in the Interface
Node and PCM Access Node software.
The Logical Processor (lp) plays the role of logical link between software and hardware components.
CAS language
CAS has an object-oriented language based on Components. These components form a database
containing information on hardware, software and services (for example a board, a physical port, the
file system, a bus, ) in the node and are represented in a hierarchical structure also called the
component instance tree.
A top level component is a component directly attached to the CAS root and is the highest component
in a branch.
Components may be either added to the tree by an operator, or automatically, or exist by default.
After a component is added, some subcomponents may be added automatically under that component.
Some components may have several instances (for example board/) while others are unique (for
example Shelf).

21 Connection to NE (MacroBTS,BTSCompact)
4 1 40


21 Connect to NE (MacroBTS, BTS Compact)
21.1 BTS On-site Maintenance (TIL)
Ethernet (Port 1)
Fast Ethernet (Port 2)
IP over ATM
interface
TIL
Terminal
TIL
Terminal
RNC
LAN/WAN
Peer-to-peer connection
Directly on BTS
(External IP Address)
Network connection
From NSP
(Internal IP Address)
4 1 41

The TIL (Local Installation Terminal) is composed of 2 parts:
TIL terminal which supports a Java enabled Web browser,
TIL software which is embedded in the CCM module.
The TIL terminal is a Windows-based personal computer and is completely independent from the BTS.
The TIL software is part of the CCM software. It is downloaded onto the TIL terminal once connection is
established. This TIL software is executed on the TIL terminal in the java Virtual Machine and provides a
graphical user interface (GUI).
The BTS also has the capability of downloading its software from a TIL CD-ROM. This could be used to speed
up installation time if network software is different from software loaded at manufacturing or when the
BTS is not connected to the network.
The TIL application activates a TCP/IP connection with the CCM module, in order to:
convey all the TIL users requests/responses to or from the BTS,
notify the TIL of current activity and events in the BTS.

21.2 BTS On-site Maintenance (TIL) [cont.]
4 1 42
LED indications on CCM, CEM, TRM and

GPSAM/GPxOIM boards :
SB (standby)
Yellow : the board is in cold stdby
Orange : the board is in hot stdby
Green : the board is providing service
AS (Administrative State)
Orange : the board is locked
Green : the board is unlocked
AL (Alarm)
Green : No alarms in the board
Red : At least one alarm in the board
Black : Hardware fault
White : board is present but not connected
MS (MCA Status)
Green : the MCA is Ok
Red : the MCA is not Ok


21.3 BTS On-site Maintenance (TIL) [cont.]
LED indications on CxCOIM :

SB (standby)
Orange/Green : the board is in cold stdby/providing service
Orange/Green : the board is locked/Unlocked
AL (Alarm)
Red : At least one alarm in the board
White : no RRH connected
Tx and Rx (Status of the optical link between the RRH and the CxOIM)
Green : Optical Tx ON. Laser is powered
white : Optical Tx OFF. Laser is unpowered
4 1 43
LED indications on RRH :

SB (standby)
Orange/Green : RRH is in cold stdby / providing service
Orange/Green : RRH is locked/Unlocked
AL (Alarm)
Red : alarm sent to the BTS
White : no RRH connected
Tx and Rx (Status of the optical link between the RRH and the CxOIM)
Green : Optical Tx ON. Laser is powered
White : Optical Tx OFF/ Laser is unpowered


How to Do it
4 1 44


Discover
4 1 45


4 1 46


Exercise
Alarms & Notifications
Launch a ftp session to the Main Server.

Go to:
/opt/nortel/data/stability/utran/
In this folder you can find the following items:
The "users commands" saved in the usc*.dat files
The alarmes in hfb*.dat files
The notificationss in the ntf*.dat files
The "State change" in the stc*.dat files
Ftp an alarm file to your PC.
Change its name from *.dat to *.csv and open it with Excell.
What do you find?
Ftp a user command file to your PC.
Change its name from *.dat to *.csv and open it with Excell.
What do you find?
4 1 47


Module Summary
4 1 48


4 1 49



for this module
4 1 50



#
#1
#2
Switch
to notes view!
O
O1
O2

A
A1
A2

P
P1
P2

B
B1
B2

Q
Q1
Q2

C
C1
C2

R
R1
R2

D
D1
D2

S
S1
S2

E
E1
E2

T
T1
T2

U
U1
U2

F
F1
F2
4 1 51
Full
Writing of Term F1

G
G1
G2

H
H1
H2
V
V1
V2


I
I1
I2
W
W1
W2


J
J1
J2
X
X1
X2


K
K1
K2
Y
Y1
Y2


Z
Z1
Z2

L
L1
L2

M
M1
M2

N
N1
N2


4 1 52


Glossary
#
#1
#2
A
A1
A2
B
B1
B2
C
C1
C2
D
D1
D2
E
E1
E2
F
F1
F2
4 1 53

G
G1
G2
H
H1
H2
I
I1
I2
J
J1
J2
K
K1
K2
L
L1
L2
M
M1
M2

Glossary [cont.]
N
N1
N2
O
O1
O2
P
P1
P2
Q
Q1
Q2
R
R1
R2
S
S1
S2
T
T1
T2
4 1 54

U
U1
U2
V
V1
V2
W
W1
W2
X
X1
X2
Y
Y1
Y2
Z
Z1
Z2

References
4 1 55


End of Module
Analyse alarm
4 1 56


Section 5
Alarm Correction Process
Module 1
9353 WMS

Blank Page
512
Alarm Correction Process Alarm Correction Process

Document History
Edition
Date
Author
Remarks
01
YYYY-MM-DD
First edition

Module Objectives
Describe
List
Explain
Identify ...
513


514


Table of Contents
Page

1 Name of Level 1
1.1 Name of Level 2
No Level
Text Boxes
Tables
Numbered Lists
Unnumbered List
Text and Graphic
Annotations
(1) Detail 1
(2) Detail 2
Main Colors
How to Do It
Discover
Exercise
515
Summary
Glossary
References
End of Module

7
8
9
10
11
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
37
39
40

516

This page

23 Alarm Resolution Methods
517


23 Alarm Resolution Method
23.1 Five Alarm Types
Environment
Equipment
518
Communications
Quality
Of Service
Processing

The alarm reporting process is based on the detection mechanisms that propagate the new coming events
through the OAM platform.
Five types of alarm have been defined to face all circumstances and events that can generate alarms during
the network lifecycle:
communications alarm type (com): An alarm of this type is principally associated with the procedures
and/or processes required to convey information from one point to another,
quality of service alarm type (ser): An alarm of this type is principally associated with a degradation
in the quality of a service,
processing error alarm type (proc): An alarm of this type is principally associated with a software or
processing fault,
equipment alarm type (eqp): An alarm of this type is principally associated with an equipment fault,
environmental alarm type (env): An alarm of this type is principally associated with a condition
relating to an enclosure in which the equipment resides.
The following pages will discuss in detail the root causes of these types of alarms.

23.2 Alarm Type Resolution Method

Resource Browser
part of equipment involved
(right click) Show alarms
Alarm Manager
What is the type of alarm?
Equipment
Communications
Quality of Service
Processing
Environment
Alarm Manager
What is the probable cause?
Define the action to be undertaken

Select the appropriate tool
from Preside NSP
519

This general flow diagram above shows the main steps of remote fault management carried out by the
maintenance staff at Preside client level.
The network supervision at Preside level can be summarized in the following tasks:
Detect a problem in the Access Network (alarm identification)
Find the root cause of the problem (alarm analysis & interpretation)
Fix the problem itself (troubleshooting)

23.3 UTRAN Main Probable Causes

Alarm Type
RNC (CN)
Probable cause
BTS
Communication
(Comm)
Communications
Subsystem Failure
Or Customization Error
Underlying Resource Unavailable
Communication protocol error

Degraded signal
Framing error
Loss of frame
Loss of signal
Remote Node Transmission Error
Equipment
(Eqp)
Equipment
Malfunction
Problem
Suspended Upgrade
Transmit Failure
Upgrade State
Version Mismatch
Adapter error
Equipment mal function
I/O device error
Input device error
Power problem
Receive failure
Receiver failure
Timing problem
Transmit failure
Transmitter failure
Processing Error
(Proc)
Communications
Configuration or Customization
Out of memory
Software program error
Quality Of Service
(Ser)
Congestion
Queue size exceeded

Threshold crossed
Environment
(Env)
Temperature
Enclosure door open

Heating / ventilation
Configuration
Power
Software
error
Protocol Error
Corrupt
Data
Software Environment Problem
Software Program Abnormally Terminated
Version Mismatch
unacceptable (heat / cold)
/ fire detected
Power supply failure
Smoke
5 1 10
error
/ cooling system
problem
Temperature unacceptable

This table gives the list of the main probable causes of alarms sent by the UTRAN equipment to Preside
NSP:
RNC
BTS
As we have said earlier, the operator can open the Alarm Manager window to display a detailed view of the
faults that are reported.
The Alarm Manager brings up a listing of all the alarms related to the Network Elements of the selected
UTRAN sub-network. It also gives the probable cause associated with each identified alarm.
Based on this list of probable causes, the operator can define the most suitable method for solving the
alarms of his network. In the following pages, we study 2 interesting methods:
Top-down processing
Domain per domain processing
The choice of either method mainly depends on the type of organization implemented by the network
supervisors.

23.4 Methods
Top-Down Processing
based on Geographical Supervision
limited to the layout managed by the supervisor
Domain per Domain Processing

based on alarm types
within each RNS
5 1 11


24 Top-down Search
5 1 12


24 Top-down Search
24.1 Defining the Supervisor Field

Geographical Distribution
5 1 13

In the example shown above, the responsibility of maintaining the access network is shared between
several groups of supervisors.
The country (England) has been logically divided into RNS (one RNC and its associated BTS). Each BTS is
called with a location name. To make things clear, one single supervisor is in charge of one single RNS,
which is a sub-group of the highest level of the current layout.
Access rights
The Access Control window is designed to facilitate two approaches to setting access permissions.
The administrator can:
select a specific user group and define which resources the user group has access to (By User
Group tab)
select a specific resource and define which user groups have access to that resource (By
Resource tab)

24 Top-down Search
24.1 Defining the Supervisor Field [cont.]

RNS1
RNS 1
RNS 1/Bedford
RNS 1/Luton
RNS 1/Mid Bedfordshire
RNS 1/South Bedfordshire
RNS 2
5 1 14

Next to the creation of the layouts, the administrator has assigned access rights to all supervisors, based on
the dependency described above.
For instance, John is in charge of the supervision of the RNS1, including the following sites:
Bedford
Luton
Mid Bedfordshire
South Bedforshire
Mike supervises the RNS2 sub-network whereas Peter only deals with RNS3, etc..
This approach enables the maintenance of layout groups with a limited number of NEs.
In short, well organizing the tree-structure of the Navigator will be very helpful for network supervision
throughout the lifecycle of the UTRAN.

25 Domain per Domain search
5 1 15


25.1 Equipment Alarms
5 1 16


25.1 equipment alarms
25.1.1 Equipment
One of the fans has his supply cable disconnected

Then the following error message appears
on the RNC on the NSP :
5 1 17

Alarm detection
An alarm may be generated after a hardware failure that triggers the sending of a notification.
The alarm is ceased if one of the following events occurs:
An end-of-alarm message is received
The defective object is logically deleted or unlocked
The defective object depends on an unlocked object.

25.1.2 Equipment [cont.]
5 1 18


25.1.3 Equipment [cont.]

Resource Browser: RNC
Alarm Manager
Probable cause:
EquipmentMalfunction
Powerproblem
.
Equipment Monitor
Check the node state (right part)
Check the board state
NO
Investigation:
Hardware
Failure?
YES
On-site intervention
Fix (or replace, if required) the faulty
part of equipment.
Search for other causes
5 1 19

This flowchart above shows the supervision process when the OAM server generates a Equipment Alarm
type of alarm. In this study case, the alarm comes from one identified faulty hardware module.
The table below gives an example of EquipmentAlarm case occurred in the Control Node. This table
summarizes the main information the reader can find in the relevant NTP called RNC Fault Analysis.
Alarm
Description
Equipment Type:
Control Node
Type:
Equipment Alarm
Probable cause:
Equipment malfunction
ANO_HARDWARE
_FAILURE
Action
Replace the corresponding module with a
new one. For more information on
replacement, refer to procedure
Replacing a module in a Control Node
RNC Hardware Maintenance Guide
(UMT/DCL/DD/0008).

25.1.4 Handling Objects

Equipment mapping
Example: BTS
Network (OAM)
BtsEquipment
Rnc
NodeB
FddCell
BtsCell
LocalCellGroupId
CellId
Hardware Equipment
(Equipment Monitor view)
5 1 20
Logical Equipment
(3GPP related)
Physical Equipment
(manufacturer related)

The slide above gives an overview of the object model applied to the BTS:
The logical part of the equipment (managed by the OMC-R) is generic and must be compliant with
3GPP recommendations.
The physical part of the equipment (managed by the OMC-B) is specific and depends on the technical
options chosen by the manufacturer.
All the objects described in the RAN model are stored in the MIB.
The OAM staff at Preside NSP level can handled all these objects:
The logical part Node B => FddCell describes logical parameters such as the number of frequency
carriers (nbFrequency), the borders of frequency (ulFrequency & dlFrequency), the scrambling code
(primary ScramblingCode), etc.
The physical part BtsEquipment => BtsCell describes some specific parameters such as the size of
the cell (cellSize), the type of rake in use (rakeMode), etc.
This slide also shows the hardware components of the BTS (via the Equipment Monitor view). This approach
of the BTS is based on the hardware configuration of the equipment, that is the modules themselves:
digital shelf, RF block with DDM,

25.2 Environment Alarms
5 1 21


25.2.1 Environment
Smoke / Fire ?
Hot?
+ 50 C / 122 F
Power supply?
- 40 C / - 40 F
Atmospheric
Pressure
(kPA)
Cold?
5 1 22

Each part of the Access Network equipment is built to withstand a wide range of environmental conditions.
An alarm of this type is triggered by the environmental conditions due to the premises in which the
equipment resides. For instance, the following events can be seen as external causes:
Temperature (heat / cold)
Smoke / fire
Power supply
Note: In case of an indoor installation, there are specific requirements to be taken into account.

25.2.2 Environment [cont.]
The BTS door is opened.

Object Class : BTS_EQUIPMENT
Event Type : EnvironmentalAlarm
Probable Cause : Enclosure Door Open
Equipment Type : DOOR_CONTACT
Cause : DOOR
Perceived Severity : minor (indoor) or major (outdoor)
Close imperatively the door for the BTS outdoor.
If the door is already closed, perform the following actions:
Equipment:
BTS
Check the I2C connections.
Check that the door contact is correct when the door is closed.
Replace, if necessary, the door contact.
5 1 23


25.2.3 Environment [cont.]

Resource Browser: BTS
Type:
EnvironmentalAlarm
Alarm Manager
Probable causes:
Enclosure door open
Heating / ventilation / cooling system
Temperature unacceptable
Launch notification log tool

for detailed information on events
YES
On-site inspection
Undertaken by entitled
staff members
NO
External
cause?
Search for:
fan (BTS indoor)
iDACS (BTS outdoor) faults
treat them if necessary.
Verify external temperature of the BTS.
Cf. Other causes
5 1 24

The flowchart above shows the supervision process when the OAM server generates a EnvironmentalAlarm
type of alarm. In most cases, this type of alarm is likely to involve one on-site intervention of the skilled
OAM staff.
The table below gives an example of EnvironmentalAlarm case. It summarizes the main information the
reader can find in the relevant NTP called Fault management BTS alarms - volume 6.
This publication contains the alarm description and maintenance actions required for the BTS.
Note: There is no environmental cause of alarm for the RNC. This type only applies to the BTS equipment.
Alarm
BTS:
Temperature overload
Type: EnvironmentalAlarm
Probable cause:
HeatingOrVentilationOrCoolin
gSystemProblem
Description
The second temperature
threshold is reached.
Action
The PA is stopped.
Equipment Type: MCPA
Search for fan (BTS indoor)

or iDACS (BTS outdoor)
faults and treat them if
necessary.
Verify external temperature
of the BTS.
If there is no environmental
problem, replace the faulty
MCPA..

25.3 Communication Alarms
5 1 25


25.3 Communication alarms
25.3.1 Communication
Transport Network
NodeB
POC
E1
MSA32
iCCM
ATM
ATM Switch
Switch
The E1 link from the NodeB is disconnected

Then the following error message appears
on the POC NE on the NSP :
5 1 26

Example: alarm details of the POC

ALARM: 7011 5003 Loss of Signal
The Communication fault with the NodeB alarm has been detected.
Component
EM/RNC
Severity
Critical
Details
If the status is set, the link has been in an loss of Signal (LOS) state for a minimum of 2 seconds.
A clear is issued when the LOS has been cleared for a minimum of 10 seconds.
Remedial action
Check the cabling between this port and the far end port.

25.3.2 Communication [cont.]
5 1 27

In this case, the network controller may be able to solve up the problem without any on-site intervention.
Alarm detection
An alarm may be generated if the system operating conditions are severely degraded. This type of
alarm is only ceased on time-out.

25.3.3 Communication [cont.]

Type:
CommunicationAlarm
Alarm Manager
Probable causes:
Communications Subsystem Failure
Configuration Or Customization Error
YES
NO
Hardware failure of
remote equipment?
Cf. Eqpt Cause
NO
Transmission
Problem?
YES
Resource Browser
Show MDM toolset
Cf. Other causes

MDM
MDM Component
Information Viewer
5 1 28

The flowchart above shows the supervision process when the OAM server generates a
CommunicationAlarm type of alarm.
The operator needs the following information in order to supervise properly the network:
Administrative state of the OAM links: if the links are locked, the operator needs to have
this information, as there may be some cases where the lock state is not the desired state
(the operator forget to open it, etc.).
Operational state of the OAM links: when the links are unlocked but the communication
with one or more Network Elements is lost for some reason, the operator needs to know it
quickly, as he looses supervision for those NEs. This state is known as Unknown status.

25.4 Quality of Service Alarms
5 1 29


25.4 Quality of Service
25.4.1 Quality of Service

Constant
Voice
Bit
Rate
IPX
Video
Available
Bit
Rate
Super
computer
Distance Learning
Variable
Bit
Rate
Videoconferencing
Low cost data transfer
Compressed
Video
LAN/WAN
Ethernet/
Token-ring
Frame
Relay
Compressed
Voice
5 1 30
Unspecified
Bit
Rate
E-mail
Music
on demand
Large file transfer

The Quality of Service (QoS) concept implies a collective measurement of the level of service delivered to
the customer.
QoS is typically characterized by the following performance criteria:
Service availability (issue: saturation)
Latency (issue: excessive response time)
Throughput (issue: no bandwidth guaranteed)
Delay variation (issue: degraded Performance / Queue size exceeded)
Packet loss rate (re-transmission rate excessive)
The first goal of the supervision is to identify as soon as possible the impact on the quality of services (i.e.
the fact that there is no way to have a call in a given area).
As these problems are the most critical ones they have to be identified in order to be solved as soon as
possible.
Note: The software upgrade mechanism can also generate some QoS alarms if the installation process fails.

25.4.2 Quality of Service [cont.]

Network Congestion
ALARM: ANO_OVERLOAD_THRESHOLD
This notification is sent when a pre-defined overload threshold (overload level 3) is crossed. The
alarm is CLEARED when the overload value crosses again under the threshold (including an
hysteresis value). Ensure that the alarm disappears when the overload decreases under the
threshold.
Severity
MAJOR CLEARED
Possible cause
Congestion
Remedial action
Not Applicable
Equipment:
RNC
5 1 31
FDD Cell State changes:

Disabled Failed
Disabled Dependency
Alarm !!!

The impact on the Quality of Service is mainly represented by the loss of the FDD cells managed by the
Control Node within the RNC.
When this issue happens, it means that no more call can be properly carried out in the area covered by
these cells.
Network congestion occurs when the volume of outgoing traffic exceeds outgoing link capacity.
To avoid this type of issue, some thresholds have to be defined in order to prevent the O&M system from
network congestion. Once the overload value is reached, the QoS alarm is triggered and sent to the O&M
staff members.
The table below gives another example of a QoS alarm located in the Control Node of the RNC.
Alarm
Control Node:
software installation
failed
Type:
QualityOfServiceAlarm
Probable cause:
sfwrDownloadFailure
Description
Inform the user that the
Upgrade Software
installation on the
Control Node is failed.
Action
The user must start
again to download the
new software version.

25.4.3 Quality of Service [cont.]

Type:
QualityOfServiceAlarm
Alarm Manager
Probable causes:
Network Congestion
Corrupt data
ATM frames
..
YES
NO
ATM frames?
QoS parameters?
Resource Browser
Show MDM toolset
NO
Network
Congestion?
YES
MDM
MDM Component
Information Viewer
Cf. Other causes

Performance Mnt
Check the definition of ATM parameters

Check the negotiated QoS parameters
Check the non-negotiated QoS parameters
Cf. Performance
5 1 32

This flowchart above shows the supervision process when the OAM server generates a
QualityOfServiceAlarm type of alarm.
Qos detection
An alarm may be generated when a permanent observation counter crosses a high or low threshold.
The alarm is ceased when the end-of-alarm message is received, indicating that the counter is
operating normally. The operator can set threshold values dynamically for each observation counter
occurrence.
If a counter alarm was reported and the newly read value is no longer above or below the defined
threshold, an end-of-fault message is automatically generated.
Starting from V3.1, some new QoS alarms have been introduced for the RNC:
Hardware objects: , OMU and MMS modules,
Logical objects: FDDCell, CsCoreNetwork, PsCoreNetwork, NeighbouringRNC.

25.5 Processing Error Alarms
5 1 33


25.6 Processing error alarms
25.5.1 Processing
?
?
?
Software Repository
Server
5 1 34
OAM Servers
Radio Access

Example: alarms details of the Interface Node

ALARM: 00009000 Software Exception
The Software Exception alarm has been detected.
Component
AP
Severity
Minor
Status
Message
Details
An internal software exception has been detected. Additional information in the alarm details
indicates the point of failure detected by the subsystem.
Remedial action
The operator should contact Alcatel-Lucent Support Services to report this failure occurred. Other
operational checks will bring this processor back into service if the fault will cause service issues.

25.5.2 Processing [cont.]

ALARM: 70120503 Starting Software Upgrade
The Starting Software Upgrade alarm has been detected.
Component
LP
Severity
Warning
Status
Message
Details
Incremental software upgrade is started. The upgrade may choose
one LP at a time, or in critical conditions, such as a simultaneous
Control Node / Interface Node upgrade, then all LPs may be upgraded
at once.
Remedial action
Equipment:
Interface Node
PCM Access Node
5 1 35
The upgrade has been started and no further action is required from
the operator. When the upgrade is complete, another alarm (70120504)
will declare the upgrade done.

Here is another typical example of processing cause of alarm:

Alarm
Incoherent Running Software Version
Object
Control Node
Description
Running software version reported by NE is not coherent with the OMC one
Action
Install the same RNC software on both OAM SRS and Control Node. Building a new MIB may be
required.
Alarm detection
An alarm may be generated when this message is received. This type of alarm can be ceased either
by users or on time-out.

25.5.3 Processing [cont.]

Alarm Manager
Probable cause:
Incoherent Running Software Version
Equipment Monitor
Tree View (logical objects):
CnodeSoftware, 0
(right click)
Value
FallbackSoftwareVersion xxx
RunningSoftwareVersionxxxx
Object Editor
Details
List of parameters
NO
MIB
Investigation:
Software
inconsistency?
YES
Comparing software versions

Software upgrade
Audit
Rebuild
5 1 36

The flowchart above shows the supervision process when the OAM server generates a Processing Error
Alarm type of alarm. In this study case, the alarm comes from the inconsistency between 2 software
versions. It might be the result of the last RNC software upgrade.
The software upgrade process will be thoroughly studied in another courseware.
The table below gives an example of Processing Error Alarm case occurred in the BTS. This table
summarizes the main information the reader can find in the relevant NTP called Fault management BTS
alarms - volume 6.
Alarm
Description
Equipment Type: TRM

Equipment number Type:
ProcessingErrorAlarm
Probable cause:
Out of Memory
Fault detected when

available free memory
is less than 5%.
Action
Proposed Maintenance
Action:
1) Since one possibility is a
software problem, reset
the TRM board.
2) In all cases, inform global
product support

How to Do it
5 1 37


Discover
5 1 38


5 1 39


Module Summary
5 1 40


5 1 41



for this module
5 1 42



#
#1
#2
Switch
to notes view!
O
O1
O2

A
A1
A2

P
P1
P2

B
B1
B2

Q
Q1
Q2

C
C1
C2

R
R1
R2

D
D1
D2

S
S1
S2

E
E1
E2

T
T1
T2

U
U1
U2

F
F1
F2
5 1 43
Full
Writing of Term F1

G
G1
G2

H
H1
H2
V
V1
V2


I
I1
I2
W
W1
W2


J
J1
J2
X
X1
X2


K
K1
K2
Y
Y1
Y2


Z
Z1
Z2

L
L1
L2

M
M1
M2

N
N1
N2


5 1 44


Glossary
#
#1
#2
A
A1
A2
B
B1
B2
C
C1
C2
D
D1
D2
E
E1
E2
F
F1
F2
5 1 45

G
G1
G2
H
H1
H2
I
I1
I2
J
J1
J2
K
K1
K2
L
L1
L2
M
M1
M2

Glossary [cont.]
N
N1
N2
O
O1
O2
P
P1
P2
Q
Q1
Q2
R
R1
R2
S
S1
S2
T
T1
T2
5 1 46

U
U1
U2
V
V1
V2
W
W1
W2
X
X1
X2
Y
Y1
Y2
Z
Z1
Z2

References
5 1 47


End of Module
5 1 48


Section 6
Options
Module 1
Options
9353 WMS

Blank Page
612
Options Options
Document History
Edition
Date
Author
Remarks
01
YYYY-MM-DD
First edition

Module Objectives
Describe
List
Explain
Identify ...
613
Options Options

614
Options Options

Table of Contents
Page

1 Name of Level 1
1.1 Name of Level 2
No Level
Text Boxes
Tables
Numbered Lists
Unnumbered List
Text and Graphic
Annotations
(1) Detail 1
(2) Detail 2
Main Colors
How to Do It
Discover
Exercise
615
Options Options
Summary
Glossary
References
End of Module

7
8
9
10
11
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
37
39
40

616
Options Options

This page

26 HFB
617
Options Options

26 HFB
26.1 Historical Fault Browser

http://wnms01.dnsaul.alcatel.fr:8080/hfb
618
Options Options
The Historical Fault Browser (HFB) provides a generic event history capability across Preside-managed
network elements. It has a flexible query mechanism allowing users to aggregate selective alarm history
information. Specifically, Preside HFB captures all alarm data for historical analysis, incident reporting,
and customer impact analysis. A Web-based GUI provides easy accessibility to fault information for
troubleshooting in Operations Centers or remote locations.
The HFB allows the user to perform the following tasks:
Filter an alarm list on any displayed field from the database
Display multiple queries at the same time, each in a separate window
Sort alarms by any column in the table
Display retrieved alarm data in hypertext mark-up language (HTML) report format
Store queried data to file
Print selective alarm event data from the database
The HFB retrieves raise alarm and clear alarm events from the network via the Building Block architecture.
The HFB automatically supports newly added network elements without any additional configuration
required. Alarm events are stored in an Oracle Relational Database Management System (RDBMS).

26 HFB
26.2 Historical Fault Browser (count)
619
Options Options

26 HFB
26.3 Historical Fault Browser (Export Report)
6 1 10
Options Options

26 HFB
26.4 Historical Fault Browser (View Records)
6 1 11
Options Options

27 Trouble Ticketing
6 1 12
Options Options

27 Trouble Ticketing
27.1 Trouble Ticketing
6 1 13
Options Options
The Trouble Ticketing Interface provides a bridge between the Alarm Manager and 3rd party Trouble
Management Systems (TMS) to automate the creation of trouble tickets, thus improving help-desk
performance and reducing the risk of error.
It allows network operators to create:
trouble reports with complete fault and originator information
Trouble tickets for alarm events raised within Preside are seamlessly managed by Clarify Clear
Support.
The system accepts responses from the trouble management systems, allowing bi-directional inter-working
between the two mechanisms.
The interface is based on simple & complete solution:
Alarm Dialog pull down menu
Full fault details forwarded to Trouble Ticket System.

28 UTRAN Service View
6 1 14
Options Options

28 Utran Service view
28.1 Principles
The UTRAN Service View window enables an easy service and status
based monitoring.
It displays, for each group included in the current layout, the counts
of objects in bad states. Any change in the Navigator is reflected in
the UTRAN Service View window that can be used as a first alert.
One Raw
Per Group
6 1 15
Options Options
The UTRAN Service View window automatically opens after you open the layout or group(s) in
View mode
The UTRAN Service View window details in a table format alarm and status counts on radio
cells and interfaces. It displays for each group:
cell information:
enabled cell number
disabled cell number (available by default)
locked cell number
enabled/total cell ratio
link information:
enabled link number
disabled link number (available by default)
locked link number
enabled/total link ratio
alarm information:
active unacknowledged alarm number
active acknowledged alarm number
total active alarms of the highest severity (available by default)
The most severe alarm count is displayed. Cell color, alarm severity letter, and "plus"
information are displayed according to this most severe alarm. A white frame indicates that there are
unacknowledged alarms.
Group Name (always available)
28.2 Show/Hide Columns

Disabled
link ?
Enabled
Cell ?
Cell Count
Disabled Cell Count
locked
link ?
Locked Cell Count
Disabled
Cell ?
Enabled Cell Ratio
You can select the information

you want to display
Link Count
Disabled link count
Locked Link Count
Enabled Link ratio
Unacknowledged alarms
acknowledged alarms
alarms
6 1 16
Options Options
View customization The UTRAN service can be easily customized by showing/hiding

columns among the set of proposed ones, thus matching the information displayed to the
operators monitoring strategy.
The view consists of a unique panel in a separate window titled UTRAN service view,
containing a table that presents the counts per NE group in the current layout, and a button
used to reset the highlights

28.3 Contextual menu
6 1 17
Options Options
Double click on a UTRAN service view cell open the resource browser window of current
selected group.
By right-clicking on a UTRAN Service View cell, a contextual menu appears allowing the
user to launch the Alarm Manager, the Resource Browser or export the UTRAN Service
View table into clipboard file or printer,
For each column except alarms and group names, a list of up to five items RNCXXX
(YY) popup menus will be shown at the top position.
Selecting one of these items in the context menu will open the equipment monitor of this
RNC. This section of the context menu will not be displayed when the count in the cell is
0.
In the case of Enabled cells / links ratio columns, the RNCs with the lowest percentages
are shown in increasing order.

29 Configure Colors
6 1 18
Options Options

29 Configure Colour
29.1 Configure colors
AND
6 1 19
Options Options
In previous releases, colors for alarms were predefined and fixed.

To discriminate the different severities for alarms, client-configurable colors can be set on such and such
alarms.
Configuring alarm severity colors
To configure the alarm severity color display, you must launch the Alarm Color Chooser. You can
open this tool from the NSP window Admin menu.
You must have the appropriate permission settings to open the tool.
Once they have been modified, the alarm severity colors apply globally to all users.

30 Manage Audible Alarms
6 1 20
Options Options

30 Manage Audible Alarm
30.1 Audible Alarms
6 1 21
Options Options
This feature enhances the alarm management solution by providing audible alarm support on alarms.
When an alarm occurs, if this capability is invoked, audible indications will be given to alert the operator of
the arrival of the alarms, if this feature capability is selected by the operators.
This feature provides operators with the ability to have unique audible alarms based on each alarm severity
type.
The combination of audio & visual signals ensures better means of network supervision for the operators.

30 Manage Audible Alarm
30.2 Audible Alarms
6 1 22
Options Options

How to Do it
6 1 23
Options Options

Discover
6 1 24
Options Options

6 1 25
Options Options

Exercise
Historical Fault Browser
The Historical Fault Browser (HFB) provides a generic event history capability across WNMS-managed network elements. It has a flexible query mechanism allowing users to
aggregate selective alarm history information.
Launch HFB (from Internet Explorer http://main-server-name:8080/hfb/ for example
http://HAL:8080/hfb)
Login and password: administrator / adminpass
We want to check the alarms raised yesterday from the RNC.
In the Select Retrieval Criteria / Network part create a filter:

Search by: NE NAME
Equals
RNC1
Click on Add to list
Then
Click on date / time
Write yesterdays date
Click on Add to list
Click on count
Click on view records
We want now to check:
Save your filter.

Export the alarms into an Excell file.
All the major alarms

Send by the BTS
Yesterday between 10:00 am and 10:00 pm
6 1 26
Options Options

Exercise
TROUBLESHOUTING
The trainer will generate different alarms by complexity and depending

on the different NEs.
Using the different tools provided by W-NMS, you will have to :
identify the alarm and analyse if you are able or not to solve the
problem with the NSP tools.
explain precisely and simply to the on-site persons the exact location of
the fault and you will try to fix it.
When the alarm is solved, acknowledge it and verify that it is stored in
the historical list.
6 1 27
Options Options

Module Summary
6 1 28
Options Options

6 1 29
Options Options


for this module
6 1 30
Options Options


#
#1
#2
Switch
to notes view!
O
O1
O2

A
A1
A2

P
P1
P2

B
B1
B2

Q
Q1
Q2

C
C1
C2

R
R1
R2

D
D1
D2

S
S1
S2

E
E1
E2

T
T1
T2

U
U1
U2

F
F1
F2
6 1 31
Full
Writing of Term F1
Options Options
G
G1
G2

H
H1
H2
V
V1
V2


I
I1
I2
W
W1
W2


J
J1
J2
X
X1
X2


K
K1
K2
Y
Y1
Y2


Z
Z1
Z2

L
L1
L2

M
M1
M2

N
N1
N2


6 1 32
Options Options

Glossary
#
#1
#2
A
A1
A2
B
B1
B2
C
C1
C2
D
D1
D2
E
E1
E2
F
F1
F2
6 1 33
Options Options
G
G1
G2
H
H1
H2
I
I1
I2
J
J1
J2
K
K1
K2
L
L1
L2
M
M1
M2

Glossary [cont.]
N
N1
N2
O
O1
O2
P
P1
P2
Q
Q1
Q2
R
R1
R2
S
S1
S2
T
T1
T2
6 1 34
Options Options
U
U1
U2
V
V1
V2
W
W1
W2
X
X1
X2
Y
Y1
Y2
Z
Z1
Z2

References
6 1 35
Options Options

End of Module
Options
6 1 36
Options Options

Last But One Page

1
@@PRODUCT
@@COURSENAME
All Rights Reserved Alcatel-Lucent @@YEAR

This page

@@COURSENAME - Page 1
All rights reserved Alcatel-Lucent @@YEAR

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent
@@COURSENAME - Page 2

Ce Tmo18261 9353 Wms Ua07 Utran Fault Management

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ce Tmo18261 9353 Wms Ua07 Utran Fault Management

Uploaded by

Copyright:

Available Formats

9353 WMS

TMO18261 9353 WMS UAO7

All Rights Reserved Alcatel-Lucent 2010

All rights reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2010

Terms of Use and Legal Notices

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2010

4. Topic/Section is Positioned Here

Section 3. Define UTRAN NE and OAM link

1. Topic/Section is Positioned Here

6. Topic/Section is Positioned Here

Module 1. Define UTRAN NE and OAM link TMO18261 D0 SG DEN I1.0

Section 5. Alarm Correction Process

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

Course Outline [cont.]

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

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

Illustrate the Fault Management Architecture

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

Course Objectives [cont.]

All Rights Reserved Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2010

About this Student Guide

Where you can get further information

All Rights Reserved Alcatel-Lucent 2010

If you want further information you can refer to the following:

All Rights Reserved Alcatel-Lucent 2010

About this Student Guide [cont.]

Switch to notes view!

All Rights Reserved Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2010

Client (Company, Center) :

Switch to notes view!

Surname, First name :

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

Self-assessment of Objectives [cont.]

All Rights Reserved Alcatel-Lucent 2010

Thank you for your answers to this questionnaire

All Rights Reserved Alcatel-Lucent 2010

Do not delete this graphic elements in here:

TMO18261 D0 SG DEN I1.0 Issue 1

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

This page is left blank intentionally

Last name, first name

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

Module Objectives [cont.]

All Rights Reserved Alcatel-Lucent 2010