ALU eNodeB Supervision Using SAM GUI

Do not delete this graphic elements in here:

2·1 All Rights Reserved © Alcatel-Lucent 2011

Module 1 eNodeB Supervision Overview

Issue

Section 2 eNodeB Supervision using 5620 SAM

9400 LTE LA3.0 eNodeB Supervision via 5620 SAM

TMO18235 D0 SG DEN Issue 1

All Rights Reserved © Alcatel-Lucent 2011

9400 LTE · LA3.0 eNodeB Supervision via 5620 SAM eNodeB Supervision using 5620 SAM · eNodeB Supervision Overview

2 · 1 · 2

Module Objectives

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

Describe alarm management in 5620 SAM,

Identify some interesting eNodeB alarms,

Check status of eNodeB objects on alarm reception.



2 · 1 · 3

1 eNodeB Supervision overview



2 · 1 · 4


Event Notification Policies

5620 SAM

Trap

SNMPv3

Event Notification Policy is used to control specifics traps received by SAM.



2 · 1 · 5


Event Notification Policies [cont.]

Fill in name and description

On selection, new fields appear

Once configure, click ok



2 · 1 · 6


Event Notification Policies [cont.]

Traps processing can be disable



2 · 1 · 7


Hour Default Sync for eNodeB

eNodeB are resync every 24 hours by default. This is configurable in the MIB Entry Policy

MIB SNMPv3

5620 SAM

Get



2 · 1 · 8


Hour Default Sync for eNodeB [cont.]



2 · 1 · 9

2 eNodeB Alarm Management Overview



2 · 1 · 10


Alarms Processing

Trap

5620 SAM

Alarm or event converted to X.733-standard alarm fields

Associated with managed equipment, configured services and policies

Alarm 1

Alarm 2 Alarm 3

correlation

Event

Fault

Alarm 4



2 · 1 · 11


Alarms Processing [cont.]

Time

Event Message

« Begin »

• Delete

• Clear

• Ack

Active Alarm Clear Alarm

Event Message

« End »

Purge



2 · 1 · 12


Alarm severity

Default color Alarm Severity

Red Critical – Service-affecting fault / Requires immediate attention

Orange Major - Possibly service affecting / Requires attention ASAP

Yellow Minor - Non service affecting / Requires attention when possible

Cyan Warning – Could potentially affect service / Requires investigation

Mocha Condition

Green Cleared – Alarm no longer current regardless of the previous state

White Indeterminate – 5620 SAM is determining the severity level

Light blue Info - Information only / Does not signify a fault condition

The 5620 SAM GUI uses color to indicate alarm severity.



2 · 1 · 13


Affecting, aggregated and related alarms definition

For a given object :

Aggregated alarms are alarms that are generated due to objects hierarchy.

Correlated alarms are alarms raised for other objects that are dependent on the alarmed object.

Aggregated alarm generated on eNB Equipment

eNB cell down



2 · 1 · 14


Affecting, aggregated and related alarms definition [cont.]

Related alarms, also called affecting alarms, are alarms that have impact on another object.

affecting

eNB1

Rack–eNB-1

Affected by

contains

eNBEquip

Shelf-1

CardSlot-1

Card

CBCard

eNBInst

Cell-eNB1-0

Rack–eNB-2

RFM



2 · 1 · 15


Alarm status in object form



2 · 1 · 16


Alarm status in object form [cont.]



2 · 1 · 17


Alarms status in navigation tree

Aggregated Alarms :Highest severity alarm status in child objects displayed in the circle

Object Alarms : object that has declared an alarm conditio. The alarm status is displayed in the square box.

Warning

If alarms are cleared manually the

color in the navigation tree returns

to green even if the operational

status is still down



2 · 1 · 18


Alarms status in navigation tree in topology map

Aggregated Alarms

Object Alarms

Highest Severity Contained Alarms

Highest Severity Contained Status

Highest Severity Edge Status

NE icon

NE Group icon



2 · 1 · 19

3 Alarm Window on 5620 SAM



2 · 1 · 20

3 Alarm Window

Alarm Table

Alarm history

Filter Alarm count

Pause Alarm Window

Right-click on the Title Bar to add or remove the alarm information columns on the list

The first tab of the Alarm windows displays the Alarm Table.



2 · 1 · 21

3 Alarm Window

Alarm statistics

The second tab of the Alarm windows displays the Alarm Statistics.



2 · 1 · 22

3 Alarm Window

Alarm Flags



2 · 1 · 23

3 Alarm Window

Alarm Flags [cont.]

Reset counter

Alarm counter

Last Alarm time

Alarm Type



2 · 1 · 24

3 Alarm Window

Interesting fields

Right click to display fields list

For Multiple occurences of the same alarm

Maintenance or in service



2 · 1 · 25

3 Alarm Window

Historical Alarms



2 · 1 · 26

3 Alarm Window

Historical Alarms [cont.]



2 · 1 · 27

3 Alarm Window

Alarm Info Form

Right click



2 · 1 · 28

4 Policy management



2 · 1 · 29

4 policy Management

Global Alarm Policy Setting

An alarm policy specified how to process alarms and how to create and store the alarm logs

Alarm severity can be changed automatically or by manually



2 · 1 · 30

4 policy Management

Global Alarm Policy Setting [cont.]

Must be enable to allow the change of the deletion policy

… manually deleted

Alarm is deleted when alarm is …

… cleared by the system



2 · 1 · 31

4 policy Management

Alarm history behavior

Deleted entries from Historical alarm database are logged in 5620 SAM files



2 · 1 · 32

4 policy Management

Specific Alarm Policy Setting

For that alarm, add a rule that changes severity when the alarm frequency exceeds thereshold



2 · 1 · 33

5 Operations for Alarms management



2 · 1 · 34

5 Operations for Alarms Management

Operator Commands

Alarm moved to Historical Alarms

in case of same triggering event, If deleted, a new alarm is raised If cleared, alarm is raised again with updated time ans statistics

Alarm moved to Historical Alarms

Depending on configuration, alarm is moved or not to the historical Alarms.



2 · 1 · 35

In service

5 Operations for Alarms Management

Operator Commands [cont.]

Change severity of alarm

Update the state of the eNodeB

maintenance



2 · 1 · 36

6 Use cases



2 · 1 · 37

6 Use cases

Alarms Domains

Alarms are divided into domains :

Activation domain includes all alarms that concern activation session management

LTE domain concerns backup and restore functions, software upgrade functions, communication state, call traces, eNodeB and cells states…

LTE MME domain concerns MME alarms

LTE Serice domain concerns mobile service alarms

RAN licence domain concerns all alarms that relates to tokens and licence management.



2 · 1 · 38

6 Use cases

Activation domain

5620 SAM

Activation Manager

WO

Configuration data



2 · 1 · 39

6 Use cases

LTE domain - Configuration backup/restore overview

5620 SAM

Backup/restore policy

Alpha and beta parameters

Backup/restore Policy can be associated to the eNodeB upon eNodeB discovery or at policy level

DB

Local file



2 · 1 · 40

6 Use cases

LTE domain - Configuration backup/restore failure alarms

Possible issue is that 5620 SAM samadmin user can’t write in destination directory



2 · 1 · 41

6 Use cases

LTE domain – eNodeB status alarms Overview



2 · 1 · 42

6 Use cases

LTE domain – eNodeB offline

ENodeB could be locally managed by maintenance Terminal



2 · 1 · 43

6 Use cases

LTE domain – eNodeB offline [cont.]



2 · 1 · 44

6 Use cases

LTE domain - bCEM locked



2 · 1 · 45

6 Use cases

LTE domain - bCEM locked [cont.]



2 · 1 · 46

6 Use cases

LTE domain - Equipment Alarm



2 · 1 · 47

6 Use cases

LTE domain – cells alarms overview



2 · 1 · 48

6 Use cases

LTE domain – cells down alarm

Cell object is part of eNodeB logical instance



2 · 1 · 49

6 Use cases

LTE domain - cell Not available alarm

Other objects are impacted by this alarm, as neigboring or measurement



2 · 1 · 50

6 Use cases

LTE domain – software upgrade

5620 SAM

Software upgrade policy

Download

DB

import file

activation

Accept/Reject



2 · 1 · 51

6 Use cases

LTE domain – software upgrade [cont.]

Succesful upgrade alarm



2 · 1 · 52

6 Use cases

LTE domain

X2 interface between eNodeB is used for Handover purposes



2 · 1 · 53

6 Use cases

Ranlicence domain



2 · 1 · 54

6 Use cases

Database Corruption Alarm

eNodeB databse is corrupted, the gamma configuration should be pushed to the eNodeB using the reconfigure button

This alarm has impact on eNodeB logical instance



2 · 1 · 55

6 Use cases

Database Corruption Alarm [cont.]



2 · 1 · 56

6 Use cases

Node Rebooted Alarm

The 5620 SAM detects that eNodeB has rebooted comparing system up time.



2 · 1 · 57

Configuration data is pushed to the template suing an activation session

6 Use cases

Integration process Overview

5620 SAM Pre-Provisionned

NE Manager

DB

Activation Manager

WO

eNodeB and pre-proviosned NE match during eNodeB discovery

Pre-provison manager creates an eNodeB template 1

2

2



2 · 1 · 58

6 Use cases

Integration Alarms - Incomplete configuration Alarm

This alarm is raised when an activation session has failed to provison a preprovisoned NE. Step 2



2 · 1 · 59

6 Use cases

Integration Alarms - Discovery Alarm

This alarm eNodeB and pre-provisoned NE can’t match. Step 3



2 · 1 · 60

6 Use cases

CPRI alarms

CPRI Link

BBU is composed of Control borad and Modem boards

Radio modules are connected to control board using CPRI links.

In addition to specific alarms, cells and ENBEquipment alarms are raised as CPRI failure affects other objects.



2 · 1 · 61

6 Use cases

CPRI alarms [cont.]

Control board releated alarm



2 · 1 · 62

6 Use cases

CPRI alarms [cont.]

Control board has lost connectivity to RFM



2 · 1 · 63

6 Use cases

CPRI alarms [cont.]

One CPRI port failed



2 · 1 · 64

6 Use cases

CPRI alarms [cont.]

No CPRI port available (othe only one connected ahs failed)



2 · 1 · 65

6 Use cases

CPRI alarms [cont.]

RFM related alarm



2 · 1 · 66

6 Use cases

bCEM disconnected



2 · 1 · 67

6 Use cases

bCEM disconnected [cont.]



2 · 1 · 68

6 Use cases

GPS antenna disconnected

Synchronization needed for Handover and Radio Framing accuracy in TDD systems

DL | UL | DL | UL

DL | UL | DL | UL



2 · 1 · 69

6 Use cases

GPS antenna disconnected [cont.]



2 · 1 · 70

6 Use cases




2 · 1 · 71

6 Use cases




2 · 1 · 72

6 Use cases


eNodeB can stay in free-running for 24 hours without impact on telecom operations



2 · 1 · 73

6 Use cases

NTP error

NTP synchronization is used for OAM purposes.



2 · 1 · 74

6 Use cases

Ethernet Transport Failure

Alarm can be raised during intensive ethernet port use



2 · 1 · 75

6 Use cases

S1 MME association failure



2 · 1 · 76

6 Use cases

SNMP failure



2 · 1 · 77

6 Use cases

Poller issue

Network issue on OAM network should be suspected



2 · 1 · 78

End of Module eNodeB Supervision Overview

Documents

ALU eNodeB Supervision Using SAM GUI