MCCI Alarm Correlation UAT Test Cases v1.1

MODULE NAME / PROCESS NAME: Test Cases for Alarm Correlation
FUNCTIONALITY TEST SCRIPTS
ALARM CORRELATION
TEST DOCUMENT
Commercial in Confidence
MCCI_Alarm_Correlation_Test_Cases_v1.1
Page 1 of83

Revision History .............................................................................................................................................................................................................. 4

Approvals ....................................................................................................................................................................................................................... 5
Distribution ..................................................................................................................................................................................................................... 6
Introduction.................................................................................................................................................................................................................... 7
Objectives ...................................................................................................................................................................................................................... 8
Test Setup ...................................................................................................................................................................................................................... 9
Summary of Test Cases ................................................................................................................................................................................................. 11
NSN Net Act Alarms Correlation ..................................................................................................................................................................................... 14
Auto Clearing of Alarms older than 1 day (24 hours) .................................................................................................................................................... 14

Change of Alarm Severity when Hitcount reaches 10 ................................................................................................................................................... 16
Alarm correlation and fault generation & verification for Clock failure alarm .................................................................................................................. 18
Alarm correlation & verification for Group1 of BCCH Missing alarm................................................................................................................................ 21
Alarm clearing for Group1 of Correlated BCCH alarm.................................................................................................................................................... 24
Alarm correlation & verification for Group2 of BCCH Missing alarm................................................................................................................................ 26
Alarm clearing for Group2 of Correlated BCCH alarm.................................................................................................................................................... 28
Huawei M2000 Alarms Correlation .................................................................................................................................................................................. 30
Synthetic/Pseudo alarm generation for Signalling Gateway (SG) ................................................................................................................................... 30

Alarm clearing for Synthetic/Pseudo Alarm for Signalling Gateway (SG) alarms .............................................................................................................. 32
Synthetic/Containment alarm generation for group of M3UA alarms .............................................................................................................................. 34
Alarm clearing for Synthetic/Containment Alarm for M3UA group alarms ....................................................................................................................... 36
GPRS Alarms Correlation ............................................................................................................................................................................................... 38
Synthetic/Containment alarm generation for group of IP NS-VC DYNAMIC NEGOTIATION FAULT alarms ........................................................................ 38
Alarm clearing for Synthetic/Containment Alarm for IP NS-VC DYNAMIC NEGOTIATION FAULT group alarms.................................................................. 40
Page 2 of83

Synthetic/Containment alarm generation for group of NO AVAILABLE NS-VC IN NSE alarms .......................................................................................... 42
Alarm clearing for Synthetic/Containment Alarm for NO AVAILABLE NS-VC IN NSE group alarms .................................................................................... 44
Synthetic/Containment alarm generation for group of IP NSVC LINK FAULT alarms ....................................................................................................... 46
Alarm clearing for Synthetic/Containment Alarm for IP NSVC LINK FAULT group alarms ................................................................................................. 48
Ericsson Alarms Correlation ........................................................................................................................................................................................... 50
Synthetic/Containment alarm generation for group of CELL LOGICAL ALARM/ RADIO X-CEIVER alarms .......................................................................... 50
Alarm clearing for Synthetic/Containment Alarm for CELL LOGICAL ALARM/ RADIO X-CEIVER group alarms ................................................................... 52
Synthetic/Containment alarm generation for group of DIGITAL PATH FAULT SUPERVISION alarms ................................................................................ 54
Alarm clearing for Synthetic/Containment Alarm for DIGITAL PATH FAULT SUPERVISION group alarms ......................................................................... 56
Cell Outage Alarm Correlation ........................................................................................................................................................................................ 58
Alarm correlation & verification for Group of Cell Outage alarms for Nokia..................................................................................................................... 58
Alarm correlation & verification for Group of Cell Outage alarms for Ericsson ................................................................................................................. 61
Alarm correlation & verification for Group of Cell Outage alarms for Huawei .................................................................................................................. 64
Appendix A: Test Data .................................................................................................................................................................................................. 67
Appendix B: Alarm & Fault Reference data ..................................................................................................................................................................... 68
Alarm Details ............................................................................................................................................................................................................. 68

Fault Details .............................................................................................................................................................................................................. 82
Appendix C: ACE Configuration for Drools ....................................................................................................................................................................... 83
Page 3 of83

Revision History
Name
Position
Date
Reason For Changes
Version
Rupen
Consultant
30-Jun-2013
Initial Draft
0.1
Rupen
Consultant
18- Aug-2013
Updated after Internal review
0.2
Rupen
Consultant
20- Aug-2013
Updated after Internal review
0.3
Rupen
Consultant
22- Aug-2013
Updated with Minor changes
0.4
Santosh Palve
Project Manager
22-Aug-2013
Submission to MCU
1.0
Rupen Kumar
Consulta
23-Aug-2013
Updated with Minor changes
1.1
Page 4 of83

Approvals
Name
Mr. Hosein Hojatizadeh
Organization
Designation
MCI
General Director
Signature
Date
Page 5 of83

Distribution
Name
Organization
Designation
Tushar Ray
Clarity
Senior Consultant
Sachin Kotrange
Clarity
OSS Consultant
Santosh Palve
Clarity
Project Manager
Anjali Attray
Clarity
Test Manager
Page 6 of83

Introduction
This document provides for the list of test cases for the Testing of Alarm Correlation to the Clarity platform. The test cases would validate the Claritys alarm
manager functionality for correlating alarms as per latest FRS (version listed in reference Documents section).
The test cases will specify the step-by-step procedures including the actual commands to be executed, input test data if any, and the expected output/result.
The tests will be conducted in Clarity C12 Test platform. The interfaces will be used are the thin client ALARM MANAGER GUI, the web-based Clarity forms
and a Telnet/SSH client.
Page 7 of83

Objectives
The following test objectives are covered:
1. To be able to validate the configured Correlation rules including Auto Alarm Clearing, Synthetic Alarm Generation & clearance, Fault Generation for
Group alarms(Combination of alarms which are interdependent on generation of each other from NMS) as per FRS.
2. To be able to perform alarm actions in the Clarity ALARM MANAGER including monitoring of Clarity generated synthetic alarms once group alarms are
encountered from NMS.
3. To be able to validate generated faults in fault manager with pre-defined values like workgroup, description, severity, etc. for generated fault as per
Appendix B.
4. To be able to validate the clearing of Clarity generated synthetic alarm for Group Alarms.
Page 8 of83

Test Setup
CLARITY TEST PLATFORM
Software Version
C12.0.1
Real Time Server IP
10.15.33.22
Database Server IP
10.15.33.20
Application Server IP
10.15.33.21
Page 9 of83

Reference Documents
Document Type
Document Name
Author
Organization
Version
Functional Requirement Specifications
MCCI Alarm Correlation V1.0.docx
Tushar Ray
Clarity
1.0
Business Requirement Specifications
MCI NOC BRS Phase-I to IV_V1 9.docx
Ashish Baranwal
Clarity
1.9
Solution Design Document
Solution Design Phase-I to IV_v1 5.docx
Ashish Baranwal
Clarity
1.5
Page 10 of83

Summary of Test Cases

No.
Test Case
Testability
MCCI_ALARM_CORRELATION_TC_001
Auto Clearing of Alarms older than 1 day (24 hours)
Change of Alarm Severity when Hitcount reaches 10
Alarm correlation and fault generation & verification for Clock

failure alarm
Alarm correlation & verification for Group1 of BCCH Missing alarm
Alarm clearing for Group1 of Correlated BCCH alarm
Synthetic/Pseudo alarm generation for Signalling Gateway (SG)
Alarm clearing for Synthetic/Pseudo Alarm for Signalling Gateway

(SG) alarms
Synthetic/Containment alarm generation for group of M3UA

alarms
Alarm clearing for Synthetic/Containment Alarm for M3UA group

alarms
Synthetic/Containment alarm generation for group of IP NS-VC

DYNAMIC NEGOTIATION FAULT alarms
Tested by
Date
Tested
Page 11 of83

No.
Test Case
Testability
Alarm clearing for Synthetic/Containment Alarm for IP NS-VC

DYNAMIC NEGOTIATION FAULT group alarms
Synthetic/Containment alarm generation for group of NO

AVAILABLE NS-VC IN NSE alarms
Alarm clearing for Synthetic/Containment Alarm for NO AVAILABLE

NS-VC IN NSE group alarms

Link Fault alarms
Alarm clearing for Synthetic/Containment Alarm for IP NSVC LINK

FAULT group alarms
Synthetic/Containment alarm generation for group of CELL

LOGICAL ALARM/ RADIO X-CEIVER alarms
Alarm clearing for Synthetic/Containment Alarm for CELL LOGICAL

ALARM/ RADIO X-CEIVER group alarms
Synthetic/Containment alarm generation for group of DIGITAL

PATH FAULT SUPERVISION alarms
Alarm clearing for Synthetic/Containment Alarm for DIGITAL PATH

FAULT SUPERVISION group alarms
Alarm correlation & verification for Group of Cell Outage alarms

for Nokia
Tested by
Date
Tested
Page 12 of83

No.
Test Case
Testability
Tested by
Date
Tested
for Ericsson

for Huawei
Page 13 of83

NSN Net Act Alarms Correlation

TEST DESCRIPTION
Auto Clearing of Alarms older than 1 day (24 hours)
TEST OBJECTIVE
To verify alarms with Severity as Minor & Threatened are cleared automatically if the last occurrence time stamp is older than 1 day
TEST SCENARIO
Monitor Clearing of Alarms from Thin Client GUI
TEST CATEGORY
Major
User should have installed and have access to Clarity Alarm Management System GUI
Ace instance should be configured for drools and should be running. Refer Appendix C.
PRE-REQUISITES
TESTING STAGE
SIT/UAT
Procedure
Input Test Data
Expected Result
Open Clarity Alarm Manager GUI using

following URL:
Username/Password
Clarity ALARM MANAGER is launched. Alarms will be

displayed.
NEMS: Refer Appendix A
Alarms are displayed on the ALARM MANAGER GUI.
http://10.15.33.23:8080/clarity/alarm.jsp
2
Create or load an alarm dashboard to view the

alarm in a Real-Time grid view in the Alarm
Manager GUI.
Configure or select a channel such that the
alarms from the NMS are viewed.
Monitor Alarms and search for Alarms with Last

occurrence Timestamp as 23 or 23.5 hours
older than current timestamp. And wait for 30
minutes for drool rule to get fired.
Verify under which ace instance Alarm MDD is
running
Alarms would be visible on TC GUI.
Less
$CLARITY_HOME/etc/ace/ace_inst[123]/ace_inst[123]
ACE instance under which Alarm MDD is running would be

known.
Page 14 of83

Procedure
Input Test Data
Expected Result
Monitor for alarms older with Last Occurrence

timestamp older than 1 day on TC Alarm
manager GUI
Refer Appendix A for Alarm Details
Alarms older than one day would not be visible on GUI.
Monitor ace instance logs and mdd logs

whether alarms older than one day are cleared
when their last occurrence timestamp exceeds
24 hours.
less ace.CLogger.ace_inst*.log0
Ace log should confirm as Alarm Clearing Drool Rule fired.

And, Clear alarm would be visible in ACE and MDD logs for
alarms older than one day and having Severity as Minor &
Threatened. No errors & exceptions should occur in Ace logs
for any rule.
Verify whether cleared alarm details matches

with below details
NEMS (from Appendix A)
Last Occurrence Time/DMA Timestamp (>24
hours)
Severity (OK)
(Alarm Occurrence ID)
Use Alarm Occurrence ID from Step 7 & and

Query Alarm History for Severity Details
grep i error ace.CLogger.ace_inst*.log0

grep i exception ace.CLogger.ace_inst*.log0
less MDD log file name
Refer Appendix A for details
Refer Appendix A
Refer Appendix A
Details should match details mentioned in Appendix A & B.

Copy Alarm Occurrence ID details for clear alarm.
Severity should either be Minor or Threatened.
Page 15 of83

TEST DESCRIPTION
Change of Alarm Severity when Hitcount reaches 10
TEST OBJECTIVE
TEST SCENARIO
To verify the alarms severity is changed to Critical when Hitcount reaches 10 for Alarms with Severity as Major
Monitor Severity change in Alarm manager TC
TEST CATEGORY
Major
PRE-REQUISITES
TESTING STAGE
SIT/UAT
Procedure
Input Test Data
Expected Result
Open Clarity Alarm Manager GUI using

following URL:
Username/Password
Clarity ALARM MANAGER is launched. Alarms will be

displayed.
Alarms are displayed on the ALARM MANAGER GUI.
Refer Appendix A & B for details
Less
ACE instance under which Alarm MDD is running would be

known.
Refer Appendix A & B for Alarm Details
Alarms captured from Step 3 would have Severity Changed to

Critical once Hitcount reaches 10. Severity for
acknowledged alarm or Alarm which has Fault
2
Create or load an alarm dashboard to view the

alarm in a Real-Time grid view in the Alarm
Manager GUI.
Configure or select a channel such that the
alarms from the NMS are viewed.
4
5
Monitor Alarms and search for Alarms with

Severity as Major And Hitcount as 8 or 9.
Note down following detailsNE Index, NE Name, Alarm Type/Alarm ID,
CARD/PORT Details & Hitcount.
Wait for Hitcount to reach 10.
Verify under which ace instance Alarm MDD is
running. Search using NMS instance in Ace
instance folder.
Monitor for alarms with details from Step 3 for
Hitcount above 10.
Page 16 of83

Procedure
Input Test Data
Expected Result
associated should not be changed.
Monitor ace instance logs and mdd logs

whether alarms captured from Step 3 have
Severity changed to Critical once hitcount
reached 10.
Change in Severity & Hitcount would be visible in ACE and

MDD logs for alarm details captured in Step 3. No errors &
exceptions should occur in Ace logs for any rule.

7
Compare Alarm Details in Step 3 with Appendix

A&B
Alarm Details from Step 3 should match details in Appendix A

& B.
Page 17 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES
Alarm correlation and fault generation & verification for Clock

failure alarm
TESTING STAGE
SIT/UAT
To verify creation of Auto Faults when a pre-defined rule in Invoked based on the Correlation template
Monitor Correlation ID and auto fault created due to pre-defined Correlation rule
Major
Procedure
Input Test Data
Expected Result
Open Clarity Alarm Manager GUI using following URL:
Username/Password
Clarity ALARM MANAGER is launched. Alarms

will be displayed.
Alarms are displayed on the ALARM

MANAGER GUI.
2
Create or load an alarm dashboard to view the alarm in a

Real-Time grid view in the Alarm Manager GUI.
Configure or select a channel such that the alarms from the
NMS are viewed.
Monitor for alarms with details matching the configured details

in the created alarm correlation rule.
Verify the data from Appendix A & B
The alarms are automatically acknowledged

and a fault is generated for the parent Clock
failure Alarm. The Fault ID field indicates the
fault number of the created fault.
Note: All Alarms would be linked to the same
Fault Ticket.
Monitor Alarms and check Fault ID for Clock failure alarms.

Note down fault id and alarm details NE Name, Alarm
Type/ID, Alarm Severity, Alarm Occurrence ID.
Verify the Correlation ID field for Occurrence ID value
Refer Appendix A & B for Alarm/Fault details
Refer Appendix A & B for Alarm/Fault details
The correlation ID of all the alarms would

contain the value of the occurrence ID of the
parent alarm. Parent alarm will be newly
created alarm and all other alarm
Page 18 of83

Procedure
Input Test Data
Expected Result
mentioned in FRS will be child. Any new
alarm is child or not will be decided if its
time difference
is within 15 minutes of any of the
FAILURE IN SYNCHRONIZATION
SIGNAL alarm and has same BSC code
in description field.
Verify under which ace instance Alarm MDD is running. Search

using NMS instance in Ace instance folder.
Less
ACE instance under which Alarm MDD is

running would be known.
Monitor ace instance logs for created fault id for parent alarm.
Fault Id would be reflected against Parent &

Child Alarm. No errors & exceptions should
occur in Ace logs for any rule.

8
Compare Alarm Details in Step 3 with Appendix A & B
Now, Open Clarity forms from a web browser using the

following URL:
Database: C12FR_TST
Alarm Details from Step 3 should match

details in Appendix A & B.
Clarity forms successfully opened.
Username/ Password
http://10.15.33.21:7777/forms/frmservlet?config=C12FR_TST
10
Open Fault Edit Module form by navigating through:
Fault Edit Module form will open. The form is

defaulted to Add mode.
Assurance ->Fault Manager ->Fault Maintenance

11
Click the Query button to go into Query mode. Fill-in the

fault number field with the Fault ID seen in the ALARM
MANAGER (from Step 4). Click the Query button again to
proceed on searching for the fault.
12
Check the REPORTED BY field of the created fault.
Fault Number
Fault Screen opens with fault Details. Details

should match data in Appendix B
Details should match data in Appendix B
Page 19 of83

Procedure
Input Test Data
Expected Result
13
Check the WORK GROUP field of the created fault.
14
Check the CAUSE field of the created fault.
15
Check the PRIORITY field of the created fault.
16
Check the DESCRIPTION field of the created fault.
Fault description will be "Fault created by

ACE rule for BSC Clock Lost : " + {BSC CODE}
Page 20 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
Major
PRE-REQUISITES
TESTING STAGE
SIT/UAT
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.

and a fault is generated for the Group of
BCCH failure Alarm.
2

NMS are viewed.

Page 21 of83

Procedure
Input Test Data
Expected Result
Monitor Alarms and verify UNIT field for list of BCCH failure
alarms. Note down fault id and alarm details NE Name,
Alarm Type/ID, Alarm Severity, Alarm Occurrence ID.
Refer Appendix A & B for Alarm details

first alarm occurring in the group. Alarms
will be correlated with occurrence id of
newly created alarm and child alarms
will be correlated based on time
difference within 3 minutes with alarms
already correlated.

Less

Fault Id would be reflected only against

Parent Alarm. No errors & exceptions should

8

Page 22 of83

Page 23 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
To verify clearing of correlated Alarm when Group 1 of BCCH Alarms are cleared from NMS
Verify clearing of correlated Alarm (generated for Group 1 of BCCH alarms)
Major
PRE-REQUISITES
SIT/UAT
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.
2
TESTING STAGE

NMS are viewed.
4
5
Identify an sample active Containment Alarm from the Alarm

manager and capture the details for below fields:
NE IDENTIFIER field, NE INDEX field, NE TYPE field, RAW
CARD field, CARD field, NE PORT field, PORT field
Open telnet /ssh session to Clarity RT server.
Monitor the ALARM MANAGER till the identified Clarity
Generated Synthetic/Containment Alarm is cleared and
disappeared from the ALARM MANAGER once Clear Alarm is
received from NMS for Signalling gateway Alarm.
Identify an active alarm with Alarm ID and

details of the Alarm captured.
IP: 10.15.33.22
username/<password>
Refer Appendix A & B.
Telnet/SSH session established and login is

successful
Identified Active group of M3UA group of
alarms got cleared and would not be reflected
in the ALARM MANAGER.
Note: Clearing of single Group alarm would
not cause any effect on rest of the alarms
belonging to same group.
All alarms should get cleared in order to clear
the Clarity Generated Synthetic Alarm.
Page 24 of83

Procedure
Input Test Data
Expected Result
Navigate to Log directory and list the available logs for the
Alarm MDD instance.
cd $CLARITY_HOME/var/log
ls lrt |grep<MDD Instance Name>
The logs will be displayed and listed

chronologically.
Open the latest Discover MDD log. Check for the processing
logs of the received recovery alarms.
less MDD Instance Name

Log file name:
Loader_AlarmMDD.MddInstancename

less
Search for Clear Alarm for M3UA Group of

alarms. Log file will contains the records for
processed recovery alarm for the alarm
group.
Monitor ace instance logs for clearing of Containment Alarm.
tail -50f <Log file Name>

Containment Alarm clearing must be reflected

in ACE logs. No errors & exceptions should
Page 25 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
To verify creation of Auto Faults when a pre-defined rule is Invoked based on the Correlation template
Major
PRE-REQUISITES
TESTING STAGE
SIT/UAT
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.

and a fault is generated for the Group of
BCCH failure Alarm.
2

NMS are viewed.

Monitor Alarms and verify UNIT field for list of BCCH failure
alarms. Note down fault id and alarm details NE Name,
Alarm Type/ID, Alarm Severity, and Alarm Occurrence ID.

parent alarm. Alarms will be correlated
with occurrence id of newly created
alarm and child alarms will be
correlated based on time difference
within 3 minutes with alarms already
correlated.
Page 26 of83

Procedure
Input Test Data
Expected Result

Less



8

Page 27 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
To verify clearing of correlated Alarm when Group 2 of BCCH Alarms are cleared from NMS
Verify clearing of correlated Alarm (generated for Group 2 of BCCH alarms)
Major
PRE-REQUISITES
SIT/UAT
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.
2
TESTING STAGE

NMS are viewed.
4
5


IP: 10.15.33.22
username/<password>

successful
Page 28 of83

Procedure
Input Test Data
Expected Result
Alarm MDD instance.

chronologically.

Log file name:

less

group.


Page 29 of83

Huawei M2000 Alarms Correlation

TEST DESCRIPTION
Synthetic/Pseudo alarm generation for Signalling Gateway (SG)
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
To verify creation of pseudo Alarm when a pre-defined rule in Invoked based on the Correlation template
Verification of Pseudo Alarm generation due to pre-defined Correlation rule
Major
PRE-REQUISITES
TESTING STAGE
SIT/UAT
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.
ONTIME LOCAL exceeds Current System Time by 8

hours
Severity=CRICTICAL
Pseudo Alarm would be generated with

details as given Appendix B.
2

NMS are viewed.
3
4
Verify generation of Clarity generated Synthetic/Pseudo Alarm

when Signalling gateway Alarm is left in unacknowledged tab
for eight or more than eight hours.
Check for the "Root Cause ID" field of the triggered alarm.
After every 8 hours verify whether same alarm is generated

and hitcount is increased.
Verify the details of pseudo alarms with details in Appendix B.
Alarm type ahould be appended with String as COR
ROOT CAUSE ID Field will be set as

Occurrence ID of Signalling Gateway Alarm.
Hitcount of Pseudo Alarm will increase
every 8 hours along with occurrence id
and ontime.
Also, note that ROOT CAUSE ID
Alarm Details should match details from
Page 30 of83

Procedure
Input Test Data
Expected Result
ALRM-
Appendix B.

Less

Monitor ace instance logs for created Pseudo Alarm.
Pseudo Alarm created must be reflected in

ACE logs. No errors & exceptions should occur
in Ace logs for any rule.

9
Check for the SEVERITY field of the triggered alarm.
Details should match details in Appendix B.
10
Check for the DESCRIPTION field of the triggered alarm.
11
Check for the NEMS field of the triggered alarm.
Page 31 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES
Alarm clearing for Synthetic/Pseudo Alarm for Signalling

Gateway (SG) alarms
SIT/UAT
To verify clearing of pseudo Alarm when Signalling gateway Alarm is cleared from NMS
Verify clearing of Pseudo Alarm (generated for Signalling gateway)
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.
2
TESTING STAGE

NMS are viewed.
4
5
Identify an sample active Pseudo Alarm from the Alarm

Generated Synthetic Alarm is cleared and disappeared from
the ALARM MANAGER once Clear Alarm is received from NMS
for Signalling gateway Alarm.
Alarm MDD instance.

IP: 10.15.33.22
username/<password>

successful
Identified Active Signalling Gateway Alarm got
cleared and would not be reflected in the
ALARM MANAGER.

chronologically.
Page 32 of83

Procedure
Input Test Data
Expected Result
Log file name:

Search for Clear Alarm for Signalling gateway.

Log file will contains the records for processed
recovery alarm for the alarm.

less

Monitor ace instance logs for clearing of Pseudo Alarm.
Pseudo Alarm clearing must be reflected in

ACE logs. No errors & exceptions should occur
in Ace logs for any rule.

10
Verify whether Alarm is visible in Alarm History
Alarm should be visible in Alarm History.
Page 33 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES
Synthetic/Containment alarm generation for group of M3UA

alarms
TESTING STAGE
To verify creation of Containment Alarm when a pre-defined rule in Invoked based on the Correlation template
Verification of Containment Alarm generation due to pre-defined Correlation rule
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.
As soon as M3UA alarms comes, and time difference

between them is 10 minutes, rule will fire and
processing will be done. Alarm type=
M3UA association fault
M3UA SCTP fault
M3UA SCTP Path Alarm
Containment Alarm would be generated with

2
SIT/UAT

NMS are viewed.
Verify generation of Clarity generated Synthetic/Containment

Alarm when Group of M3UA Alarm appear within Time Interval
of 10 Minutes
Check for the "Correlation ID" field of the triggered alarm.
When M3UA GROUP Alarm/s are encountered

all the alarms will be grouped under single
correlation ID.
Correlation ID and Root cause Id fields of

child alarms will be updated with
occurrence id of newly created
containment alarm. Note- Correlation ID
Page 34 of83

Procedure
5
6
Input Test Data
Expected Result
Verify the details of containment alarms with details in

Appendix B.
Less
should be same for each M3UA Alarm of the

group of M3UA alarms.
Appendix B.
Monitor ace instance logs for created Containment Alarm.
Containment Alarm created must be reflected

occur in Ace.
10
Page 35 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES
Alarm clearing for Synthetic/Containment Alarm for M3UA group

alarms
SIT/UAT
To verify clearing of containment Alarm when M3UA Group Alarms are cleared from NMS
Verify clearing of containment Alarm (generated for M3UA Group of alarms)
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.
2
TESTING STAGE

NMS are viewed.
4
5
Identify a sample active Containment Alarm from the Alarm


IP: 10.15.33.22
username/<password>

successful
Page 36 of83

Procedure
Input Test Data
Expected Result
Alarm MDD instance.

chronologically.

Log file name:

less

group.


Page 37 of83

GPRS Alarms Correlation

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES

DYNAMIC NEGOTIATION FAULT alarms
TESTING STAGE
SIT/UAT
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.
As soon as alarms comes, and time difference between

them is 10 minutes, rule will fire and processing will be
done. Alarm type= IP NS-VC Dynamic Negotiation
Fault

2

NMS are viewed.

Alarm when Group of IP NS-VC DYNAMIC NEGOTIATION
FAULT Alarm appear within Time Interval of 10 Minutes
When IP NS-VC DYNAMIC NEGOTIATION

FAULT GROUP Alarm/s are encountered all
the alarms will be grouped under single
correlation ID.

Page 38 of83

Procedure
Input Test Data
Expected Result

5
6

Appendix B.
Less
should be same for each IP NS-VC DYNAMIC

NEGOTIATION FAULT Alarm of the group of
alarms.
Appendix B.

occur in Ace logs.
Check for the ALARM ID field of the triggered alarm.
10
11
Page 39 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES
Alarm clearing for Synthetic/Containment Alarm for IP NS-VC

DYNAMIC NEGOTIATION FAULT group alarms
SIT/UAT
To verify clearing of containment Alarm when IP NS-VC DYNAMIC NEGOTIATION FAULT Group Alarms are cleared from NMS
Verify clearing of containment Alarm (generated for IP NS-VC DYNAMIC NEGOTIATION FAULT Group of alarms)
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.
2
TESTING STAGE

NMS are viewed.
4
5


IP: 10.15.33.22
username/<password>

successful
Identified Active group of IP NS-VC DYNAMIC
NEGOTIATION FAULT group of alarms got
ALARM MANAGER.
Page 40 of83

Procedure
Input Test Data
Expected Result

Log file name:

chronologically.

less
Search for Clear Alarm for IP NS-VC DYNAMIC

NEGOTIATION FAULT Group of alarms. Log
file will contains the records for processed
recovery alarm for the alarm group.
Alarm MDD instance.


Page 41 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES
Synthetic/Containment alarm generation for group of NO

AVAILABLE NS-VC IN NSE alarms
TESTING STAGE
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.

done. Alarm type= No Available NS-VC in NSE

2
SIT/UAT

NMS are viewed.

Alarm when Group of NO AVAILABLE NS-VC IN NSE Alarm
appear within Time Interval of 10 Minutes
When NO AVAILABLE NS-VC IN NSE GROUP

Alarm/s are encountered all the alarms will be
grouped under single correlation ID.

should be same for each NO AVAILABLE NSVC IN NSE Alarm of the group of alarms.
Page 42 of83

Procedure
5
6
Input Test Data
Expected Result

Appendix B.
Less

Appendix B.

occur in Ace logs.
10
11
Page 43 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES
Alarm clearing for Synthetic/Containment Alarm for NO

AVAILABLE NS-VC IN NSE group alarms
SIT/UAT
To verify clearing of containment Alarm when NO AVAILABLE NS-VC IN NSE Group Alarms are cleared from NMS
Verify clearing of containment Alarm (generated for NO AVAILABLE NS-VC IN NSE Group of alarms)
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.
2
TESTING STAGE

NMS are viewed.
4
5


IP: 10.15.33.22
username/<password>

successful
Identified Active group of NO AVAILABLE NSVC IN NSE group of alarms got cleared and
would not be reflected in the ALARM
MANAGER.
Page 44 of83

Procedure
Input Test Data
Expected Result

Log file name:

chronologically.

less
Search for Clear Alarm for NO AVAILABLE NSVC IN NSE Group of alarms. Log file will
contains the records for processed recovery
alarm for the alarm group.
Alarm MDD instance.


Page 45 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES
Synthetic/Containment alarm generation for group of IP NSVC

LINK FAULT alarms
TESTING STAGE
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.

done. Alarm type= IP NSVC Link Fault

2
SIT/UAT

NMS are viewed.

Alarm when Group of IP NSVC LINK FAULT Alarm appear
within Time Interval of 10 Minutes
When IP NSVC LINK FAULT GROUP Alarm/s

are encountered all the alarms will be
grouped under single correlation ID.

should be same for each IP NSVC LINK FAULT

Alarm of the group of alarms.
Page 46 of83

Procedure
5
6
Input Test Data
Expected Result

Appendix B.
Less

Appendix B.

10
11
Page 47 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES
Alarm clearing for Synthetic/Containment Alarm for IP NSVC

LINK FAULT group alarms
SIT/UAT
To verify clearing of containment Alarm when IP NSVC LINK FAULT Group Alarms are cleared from NMS
Verify clearing of containment Alarm (generated for IP NSVC LINK FAULT Group of alarms)
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.
2
TESTING STAGE

NMS are viewed.
4
5


IP: 10.15.33.22
username/<password>

successful
Identified Active group of IP NSVC LINK
FAULT group of alarms got cleared and would
not be reflected in the ALARM MANAGER.
Page 48 of83

Procedure
Input Test Data
Expected Result
Alarm MDD instance.

chronologically.

Log file name:

less
Search for Clear Alarm for IP NSVC LINK

FAULT Group of alarms. Log file will contains
the records for processed recovery alarm for
the alarm group.


Page 49 of83

Ericsson Alarms Correlation

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES
Synthetic/Containment alarm generation for group of CELL

LOGICAL ALARM/ RADIO X-CEIVER alarms
TESTING STAGE
SIT/UAT
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.

done. Alarm type= Cell Logical Alarm/ Radio X-Ceiver

2

NMS are viewed.

Alarm when Group of CELL LOGICAL ALARM/ RADIO X-CEIVER
Alarm appear within Time Interval of 10 Minutes
When CELL LOGICAL ALARM/ RADIO XCEIVER GROUP Alarm/s are encountered all
the alarms will be grouped under single
correlation ID.

Page 50 of83

Procedure
Input Test Data
Expected Result

5
6

Appendix B.
Less
should be same for each CELL LOGICAL

ALARM/ RADIO X-CEIVER Alarm of the group
of alarms.
Appendix B.

10
11
Page 51 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES
Alarm clearing for Synthetic/Containment Alarm for CELL

LOGICAL ALARM/ RADIO X-CEIVER group alarms
SIT/UAT
To verify clearing of containment Alarm when CELL LOGICAL ALARM/ RADIO X-CEIVER Group Alarms are cleared from NMS
Verify clearing of containment Alarm (generated for CELL LOGICAL ALARM/ RADIO X-CEIVER Group of alarms)
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.
2
TESTING STAGE

NMS are viewed.
4
5


IP: 10.15.33.22
username/<password>

successful
Identified Active group of CELL LOGICAL
ALARM/ RADIO X-CEIVER group of alarms got
ALARM MANAGER.
Page 52 of83

Procedure
Input Test Data
Expected Result

Log file name:

chronologically.

less
Search for Clear Alarm for CELL LOGICAL

ALARM/ RADIO X-CEIVER Group of alarms.
Log file will contains the records for processed
Alarm MDD instance.


Page 53 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES
Synthetic/Containment alarm generation for group of DIGITAL

PATH FAULT SUPERVISION alarms
TESTING STAGE
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.

done. Alarm type= DIGITAL PATH FAULT
SUPERVISION

2
SIT/UAT

NMS are viewed.

Alarm when Group of DIGITAL PATH FAULT SUPERVISION
Alarm appear within Time Interval of 10 Minutes
When DIGITAL PATH FAULT SUPERVISION

GROUP Alarm/s are encountered all the
alarms will be grouped under single
correlation ID.

Page 54 of83

Procedure
5
6
Input Test Data
Expected Result

Appendix B.
Less
should be same for each DIGITAL PATH

FAULT SUPERVISION Alarm of the group of
alarms.
Appendix B.

10
11
Page 55 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES
Alarm clearing for Synthetic/Containment Alarm for DIGITAL

PATH FAULT SUPERVISION group alarms
SIT/UAT
To verify clearing of containment Alarm when DIGITAL PATH FAULT SUPERVISION Group Alarms are cleared from NMS
Verify clearing of containment Alarm (generated for DIGITAL PATH FAULT SUPERVISION Group of alarms)
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.
2
TESTING STAGE

NMS are viewed.
4
5


IP: 10.15.33.22
username/<password>

successful
Identified Active group of DIGITAL PATH
FAULT SUPERVISION group of alarms got
ALARM MANAGER.
Page 56 of83

Procedure
Input Test Data
Expected Result

Log file name:

chronologically.

less
Search for Clear Alarm for DIGITAL PATH

FAULT SUPERVISION Group of alarms. Log
file will contains the records for processed
Alarm MDD instance.


Page 57 of83

Cell Outage Alarm Correlation

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES

for Nokia
SIT/UAT
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.
2
TESTING STAGE

NMS are viewed.


and for the Group of cell outage Alarm.
Monitor Alarms and verify Description & Probable Cause field

for list of Cell outage alarms. Note down alarm details NE
Name, Alarm Type/ID, Alarm Severity, and Alarm Occurrence
ID.
Refer Appendix A & B for Alarm details.
5a

first alarm occurring in the group. Probable
Cause field should have data populated
Page 58 of83

Procedure
Input Test Data
Expected Result
as Mains Failure when "BTS O&M LINK
FAILURE" alarm appears after
1. "AC FAIL" for AC power
disconnection.
2. "LOW BATTERY" for low battery
5b

as Mains Failure in appropriate
external alarms when "BTS O&M LINK
FAILURE" alarm appears after
disconnection.
5c
5d

as Mains Failure-Sites without battery
backup, inappropriate external alarms
when "BTS O&M LINK FAILURE" alarm
appears when none of the alarms from
below 1, 2 or 3 appears1. "AC FAIL" for AC power
disconnection.
3. "AIS RECEIVED" or LOSS OF CRC
MULTIFRAME ALIGNMENT for TX
disconnection.
as Transmission Fault when "BTS O&M
Page 59 of83

Procedure
Input Test Data
5e

Less
Expected Result
LINK FAILURE" alarm appears after
AIS RECEIVED" or LOSS OF CRC
disconnection alarms appears, without,
any occurrence of either 1. "AC FAIL" for
AC power disconnection.
or
as NO POWERBACK UP AVAILABLE
when "BTS O&M LINK FAILURE" alarm
appears without any opccurence of
either of these alarms1. "AC FAIL" for AC power
disconnection.
or
2. "LOW BATTERY" for low battery.
or
3. "AIS RECEIVED" or LOSS OF CRC
disconnection.


Page 60 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES

for Ericsson
TESTING STAGE
SIT/UAT
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.
2

NMS are viewed.


and Group of cell outage Alarm.

ID.
5a

as Mains Failure when CELL LOGICAL
CHANNEL AVAILABILITY
Page 61 of83

Procedure
Input Test Data
Expected Result
SUPERVISION" alarm appears after

disconnection.
5b

external alarms when CELL LOGICAL
disconnection.
5c
5d

when CELL LOGICAL CHANNEL
AVAILABILITY SUPERVISION" alarm
appears when none of the alarms from
below 1, 2 or 3 appears1. "AC FAIL" for AC power
disconnection.
3. " DIGITAL PATH FAULT
SUPERVISION for TX disconnection
as Transmission Fault when CELL
Page 62 of83

Procedure
Input Test Data
5e

Less
Expected Result
LOGICAL CHANNEL AVAILABILITY
DIGITAL PATH FAULT SUPERVISION
alarms appears, without, any
occurrence of either 1. "AC FAIL" for AC
power disconnection.
or
when CELL LOGICAL CHANNEL
AVAILABILITY SUPERVISION" alarm
appears without any occurrence of
disconnection.
or
or
SUPERVISION for TX disconnection


8

Page 63 of83

TEST DESCRIPTION
TEST OBJECTIVE
TEST SCENARIO
TEST CATEGORY
PRE-REQUISITES

for Huawei
TESTING STAGE
SIT/UAT
Major
Procedure
Input Test Data
Expected Result
Username/Password

will be displayed.

MANAGER GUI.

and a fault is generated for the Group of cell
outage Alarm.
2

NMS are viewed.


ID.
5a

as Mains Failure when "OML
Fault" alarm appears after
Page 64 of83

Procedure
Input Test Data
Expected Result
disconnection.
5b

external alarms when OML
Fault alarm appears after
disconnection.
5c

when OML Fault alarm appears when
none of the alarms from below 1, 2 or 3
appears1. "AC FAIL" for AC power
disconnection.
3. " AC FAIL for TX disconnection.
5d

as Transmission Fault when OML
Fault alarm appears after AIS
RECEIVED" or LOSS OF CRC
Page 65 of83

Procedure
Input Test Data
5e

Less
Expected Result
disconnection alarms appears, without,
any occurrence of either 1. "AC FAIL" for
or
when OML Fault alarm
appears without any opccurence of
disconnection.
or
or
3. " AC FAIL for TX disconnection.


8

Page 66 of83

Appendix A: Test Data

Test case#
Alarm ID
Alarm Generation Pattern
Domain
Remarks
HUAWEI%M2000%ALARM_BSS
HUAWEI%M2000%ALARM_NSS
NSN%NETACT%ALARM
NSN%NETACT%ALARM_CLUSTER2
Page 67 of83

Appendix B: Alarm & Fault Reference data

Alarm Details
Test
Case
#
Scenario
Alarm Type
Actual
Severity
before
Correlat
ion
Auto Clearing of Alarms older than 1 day

(24 hours)
All
MINOR &
THREATE
NED
Change of Alarm Severity when Hitcount

reaches 10
Alarm correlation and fault generation &

verification for Clock failure alarm
MAJOR
FAILURE IN
SYNCHRONIZATION
SIGNAL- for each CLS
unit
Multiple instances of
these alarms-FAILURE IN SIGNALLING
LINK ACTIVATION OR
RESTORATION
FAULT RATE
MONITORING
CHANNEL FAILURE RATE
ABOVE DEFINED
THRESHOLD
BTS OPERATION
DEGRADED
FAILURE IN SENDING
MAJOR
Due to BSC Alarms Multiple BTS

failure under same BSC will
raise alarms.
Time
Inter
val
for
Corr
elati
on/A
ction
24
hours
Equip
ment
Type
Domain
Generated
Alarms
Details (if
any)
ALL
ALL
15
Minut
es
BTS &
BSC
NSN%NETACT%A
LARM
NSN%NETACT%A
LARM_CLUSTER2
NSN%NETACT%A
LARM
NSN%NETACT%A
LARM_CLUSTER2
NSN%NETACT%A
LARM
NSN%NETACT%A
LARM_CLUSTER2
Severity
changed from
MAJOR to
CRITICAL
Alarm Type:
COOR:CLOCK
LOST IN BSC
Severity:
CRITICAL
Description:
CLOCK LOST
IN BSC PLMNPLMN/BSC_C
ode
Page 68 of83

Test
Case
#
Scenario
Alarm Type
Actual
Severity
before
Correlat
ion
Time
Inter
val
for
Corr
elati
on/A
ction
Equip
ment
Type
Domain
Generated
Alarms
Details (if
any)
Raise a co-related critical ACE

alarm
Clear the correlated alarm
when the root cause alarm is
cleared
3
minut
es
BSC &
BTS.
Alarms
should
be from
Same
BSC
NSN%NETACT%A
LARM
NSN%NETACT%A
LARM_CLUSTER2

alarm
cleared
3
minut
es
BSC.
Alarms
are
from
same
BSC
NSN%NETACT%A
LARM
NSN%NETACT%A
LARM_CLUSTER2
NE: BSC
Loacation
Type: BSC
Index: NE ID
of BSC
Alarm Type:
CORR: BCCH
Missing
Raw Port:
Card:
Severity:
CRITICAL
Unit: BCD
value i
NE: BSC
Loacation
Type: BSC
Index: NE ID
of BSC
Alarm Type:
CORR: GPRS
NSVC Alarm
in BSS
Raw Port:
Card:
Severity:
CRITICAL
SYSTEM INFORMATION
TO BTS SITE
CH CONGESTION IN CELL
ABOVE DEFINED
THRESHOLD
4
Alarm correlation & verification for Group1

of BCCH Missing alarm
Alarm correlation & verification for Group2

of BCCH Missing alarm
BTS O&M LINK FAILURE

BCCH MISSIG
BTS OPERATION
DEGRADED
ALARM INDICATION
SIGNAL (AIS) RECEIVED
FAULT RATE
MONITORING
SUB NETWORK SERVICE

SIZE PROCEDURE FAILED
SUB NETWORK SERVICE
CONFIGURATION
PROCEDURE FAILED
Page 69 of83

Test
Case
#
Scenario
Synthetic/Pseudo alarm generation for

Signalling Gateway (SG)
10
Synthetic/Containment alarm generation

for group of M3UA alarms
Alarm Type
oM3UA association fault

oM3UA SCTP fault
oM3UA SCTP Path Alarm
Actual
Severity
before
Correlat
ion
Time
Inter
val
for
Corr
elati
on/A
ction
Equip
ment
Type
Domain
Generated
Alarms
Details (if
any)
CRITICAL
After every 8 hours generate

the same alarm at a new time
thus increasing the hit count.
After 8 hours of generation of
new alarm if root cause alarm is
not cleared hit count of the
pseudo alarm to be raise by
generating ON alarms for same
alarm again
8
hours
Signalli
ng
Gatewa
y (SG)
HUAWEI%M2000
%ALARM_NSS
CRITICAL

alarm
cleared
10
Minut
es
GPRS
Nodes
(GGSN)
HUAWEI%M2000
%ALARM_NSS
Unit: BCD
value i
NE: Same as
root Cause
Alarm
Type: Same as
root Cause
Alarm
Index: Same
as root Cause
Alarm
Alarm Type:
CORR:<Alarm
Type of root
cause alarm>
Raw Port:
Same as root
Cause Alarm
Card: Same as
root Cause
Alarm
Severity:
Same as root
Cause Alarm
NE: NE from
the Alam (
Considering
all alarm are
from same
NE)
Type: Same
as root cause
Page 70 of83

Test
Case
#
12
Scenario

for group of IP NS-VC DYNAMIC
NEGOTIATION FAULT alarms
Alarm Type
IP NS-VC Dynamic
Negotiation Fault
Actual
Severity
before
Correlat
ion

alarm
cleared
Time
Inter
val
for
Corr
elati
on/A
ction
10
Minut
es
Equip
ment
Type
SGSN
Domain
Generated
Alarms
Details (if
any)
HUAWEI%M2000
%ALARM_GPRS
alarm
Index: Same
as root cause
alarm
Alarm Type:
COOR: GPRS
M3UA Fail
Raw Port:
Same as root
cause alarm
Card:
Severity:
Same as root
cause alarm
Che
ck the
association
index in
description of
all alarms
with above
alarm type,
They should
carry same
association
index
NE: NE from
Alarm
Type: Value
should be
taken from
Page 71 of83

Test
Case
#
14
Scenario

for group of NO AVAILABLE NS-VC IN NSE
alarms
Alarm Type
No Available NS-VC in
NSE
Actual
Severity
before
Correlat
ion

alarm
cleared
Time
Inter
val
for
Corr
elati
on/A
ction
10
Minut
es
Equip
ment
Type
BSC
Correlat
ion rule
must be
applied
for
Alarms
coming
for
single
BSC
Domain
Generated
Alarms
Details (if
any)
HUAWEI%M2000
%ALARM_GPRS
alarm
Index: Value
should be
taken from
alarm
Alarm Type:
COOR:
Correlated
IPNSVC Alarm
and COOR:
Correlated
NS-VC Alarm
Raw Port:
Card:
Severity:
Value should
be taken from
alarm
NE: NE from
Alarm
Type: Value
should be
taken from
alarm
Index: Value
should be
taken from
alarm
Alarm Type:
CORR: No
Available NSVC in NSE
Page 72 of83

Test
Case
#
Scenario
Alarm Type
Actual
Severity
before
Correlat
ion
Time
Inter
val
for
Corr
elati
on/A
ction
Equip
ment
Type
Domain
Generated
Alarms
Details (if
any)
16

for group of IP NS-VC Link Fault alarms
IP NS-VC Link Fault

alarm
cleared
10
Minut
es
BSC
Correlat
ion rule
must be
applied
for
Alarms
coming
for
single
BSC
HUAWEI%M2000
%ALARM_GPRS
18

for group of CELL LOGICAL ALARM/ RADIO
X-CEIVER alarms
CELL LOGICAL CHENNEL

AVAILABILITY
SUPERVISION and
RADIO X-CEVIER
ADMINISTRATION
MANAGED OBJECT
FAULT

alarm
cleared
10
Minut
es
BTS &
BSC
NE
same as
BSC in
Cell
logical
ERICSSON%ALAR
M%OSS_RC
Raw Port:
Card:
Severity:
Value should
be taken from
alarm
NE: NE from
Alarm
Type: Value
should be
taken from
alarm
Index: Value
should be
taken from
alarm
Alarm Type:
CORR: IP MSVC Link Fault
Raw Port:
Card:
Severity:
Value should
be taken from
alarm
NE: BSC NE
Type: BSC
Index: BSC ID
Alarm Type:
CORR: CELL
LOGICAL
AVAILABILITY
Page 73 of83

Test
Case
#
Scenario
Alarm Type
Actual
Severity
before
Correlat
ion
Time
Inter
val
for
Corr
elati
on/A
ction
Equip
ment
Type
Domain
Generated
Alarms
Details (if
any)
alarm
ALARM
Raw Port:
Card:
Severity:
CRITICAL
20

for group of DIGITAL PATH FAULT
SUPERVISION alarms
DIGITAL PATH FAULT

SUPERVISION

alarm
cleared
10
Minut
es
BTS &
BSC
NE
same as
BSC in
Cell
logical
alarm
ERICSSON%ALAR
M%OSS_RC
23
Alarm correlation & verification for Group

of Cell Outage alarms for Nokia
1. "AC FAIL"
for
2. "LOW BATTERY" for
low battery
3. "AIS RECEIVED" or
LOSS OF CRC
MULTIFRAME
ALIGNMENT for TX
disconnection

alarm
BTS &
BSC
All
BTSs
belong
to same
BSC
NSN%NETACT%A
LARM
NSN%NETACT%A
LARM_CLUSTER2
NE: BSC NE
Type: BSC
Index: BSC ID
Alarm Type:
CORR:
DIGITAL PATH
FAULT
SUPERVISION
Raw Port:
Card:
Severity:
CRITICAL
Unit: Count of
the alarms
correlated to
generate the
ACE alarm
The sites
which have
"BTS O&M
LINK FAILURE"
after reason
"1" AND "2
Reason for fail
Mains
Failure
Page 74 of83

Test
Case
#
Scenario
Alarm Type
4. BTS O&M LINK

FAILURE
Actual
Severity
before
Correlat
ion
Time
Inter
val
for
Corr
elati
on/A
ction
Equip
ment
Type
Domain
Generated
Alarms
Details (if
any)
The sites
which have "
BTS O&M
LINK FAILURE"
after reason
"1" OR "2
Reason for fail
Mains Failure
in
appropriate
external
alarms
The sites
which have "
BTS O&M
LINK FAILURE
" without
reason "1"
AND "2"
AND 3
reason for
failure Mains
Failure-Sites
without
battery
backup,
inappropriate
external
alarms
The sites
which have
BTS O&M
Page 75 of83

Test
Case
#
23
Scenario

of Cell Outage alarms for Ericsson
Alarm Type
1. "AC FAIL" for AC

power disconnection.
2. "LOW BATTERY" for
low battery
SUPERVISION for TX
disconnection
4. CELL LOGICAL
Actual
Severity
before
Correlat
ion

alarm
Time
Inter
val
for
Corr
elati
on/A
ction
Equip
ment
Type
BTS &
BSC
All
BTSs
belong
to same
BSC
Domain
Generated
Alarms
Details (if
any)
ERICSSON%ALAR
M%OSS_RC
LINK FAILURE"
AND after
reason "3"
without "1"
OR "2"
Reason for
failure
Transmission
Fault
If all three
conditions are
not available
meaning any
of alarm for
cell outage
alarms not
received then
reason for fail
should be
NO
POWERBACK
UP
AVAILABLE
The sites
which have "
CELL LOGICAL
CHANNEL
AVAILABILITY
SUPERVISION
" after
reason "1"
AND "2
Page 76 of83

Test
Case
#
Scenario
Alarm Type
SUPERVISION
Actual
Severity
before
Correlat
ion
Time
Inter
val
for
Corr
elati
on/A
ction
Equip
ment
Type
Domain
Generated
Alarms
Details (if
any)
Reason for fail

Mains
Failure
The sites
which have "
CELL LOGICAL
CHANNEL
AVAILABILITY
SUPERVISION
" after
reason "1"
OR "2
Reason for fail
Mains Failure
in
appropriate
external
alarms
The sites
which have "
CELL LOGICAL
CHANNEL
AVAILABILITY
SUPERVISION
" without
reason "1"
AND "2"
AND 3
reason for
failure Mains
Failure-Sites
without
Page 77 of83

Test
Case
#
Scenario
Alarm Type
Actual
Severity
before
Correlat
ion
Time
Inter
val
for
Corr
elati
on/A
ction
Equip
ment
Type
Domain
Generated
Alarms
Details (if
any)
battery
backup,
inappropriate
external
alarms
The sites
which have
CELL
LOGICAL
CHANNEL
AVAILABILITY
SUPERVISION
" AND after
reason "3"
without "1"
OR "2"
Reason for
failure
Transmission
Fault
If all three
conditions are
not available
meaning any
of alarm for
cell outage
alarms not
received then
reason for fail
should be
NO
POWERBACK
Page 78 of83

Test
Case
#
24
Scenario

of Cell Outage alarms for Huawei
Alarm Type
1. " Mains Input Out of

Range" for AC power
disconnection.
2. " Low Battery" for low
battery
3. " AC FAIL for TX
disconnection.
4. OML Fault
Actual
Severity
before
Correlat
ion

alarm
Time
Inter
val
for
Corr
elati
on/A
ction
Equip
ment
Type
BTS &
BSC
All
BTSs
belong
to same
BSC
Domain
Generated
Alarms
Details (if
any)
HUAWEI%M2000
%ALARM_BSS
UP
AVAILABLE
The sites
which have "
OML Fault "
after reason
"1" AND "2
Reason for fail
Mains
Failure
The sites
which have "
OML Fault "
after reason
"1" OR "2
Reason for fail
Mains Failure
in
appropriate
external
alarms
The sites
which have "
OML Fault "
without
reason "1"
AND "2"
AND 3
reason for
failure Mains
Failure-Sites
without
Page 79 of83

Test
Case
#
Scenario
Alarm Type
Actual
Severity
before
Correlat
ion
Time
Inter
val
for
Corr
elati
on/A
ction
Equip
ment
Type
Domain
Generated
Alarms
Details (if
any)
battery
backup,
inappropriate
external
alarms
The sites
which have
OML Fault "
AND after
reason "3"
without "1"
OR "2"
Reason for
failure
Transmission
Fault
If all three
conditions are
not available
meaning any
of alarm for
cell outage
alarms not
received then
reason for fail
should be
NO
POWERBACK
UP
AVAILABLE
Page 80 of83

Page 81 of83

Fault Details
Scenario
Alarm
correlation
and fault
generation
&
verification
for Clock
failure
alarm
Workgroup
CLARITY
Fault Description
Fault created by ACE
rule for BSC Clock
Lost
Fault Cause
BSC:CLOCK
Fault priority
1
Reported by
ACE
Domain
NSN%NETACT%ALARM
NSN%NETACT%ALARM_CLUSTER2
Page 82 of83

Appendix C: ACE Configuration for Drools
Page 83 of83

MCCI Alarm Correlation UAT Test Cases v1.1

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

MCCI Alarm Correlation UAT Test Cases v1.1

Uploaded by

Copyright:

Available Formats

MODULE NAME / PROCESS NAME: Test Cases for Alarm Correlation

FUNCTIONALITY TEST SCRIPTS

MODULE NAME / PROCESS NAME: Test Cases for Alarm Correlation

Revision History .............................................................................................................................................................................................................. 4

Auto Clearing of Alarms older than 1 day (24 hours) .................................................................................................................................................... 14

Synthetic/Pseudo alarm generation for Signalling Gateway (SG) ................................................................................................................................... 30

MODULE NAME / PROCESS NAME: Test Cases for Alarm Correlation

Alarm Details ............................................................................................................................................................................................................. 68

MODULE NAME / PROCESS NAME: Test Cases for Alarm Correlation

Reason For Changes

Updated after Internal review

Updated after Internal review

Updated with Minor changes

Updated with Minor changes

MODULE NAME / PROCESS NAME: Test Cases for Alarm Correlation

Mr. Hosein Hojatizadeh

MODULE NAME / PROCESS NAME: Test Cases for Alarm Correlation

MODULE NAME / PROCESS NAME: Test Cases for Alarm Correlation

MODULE NAME / PROCESS NAME: Test Cases for Alarm Correlation

MODULE NAME / PROCESS NAME: Test Cases for Alarm Correlation

Real Time Server IP

MODULE NAME / PROCESS NAME: Test Cases for Alarm Correlation

Functional Requirement Specifications

MCCI Alarm Correlation V1.0.docx

Business Requirement Specifications

MCI NOC BRS Phase-I to IV_V1 9.docx

Solution Design Document

Solution Design Phase-I to IV_v1 5.docx

MODULE NAME / PROCESS NAME: Test Cases for Alarm Correlation

Summary of Test Cases

Auto Clearing of Alarms older than 1 day (24 hours)

Change of Alarm Severity when Hitcount reaches 10

Alarm correlation and fault generation & verification for Clock

Alarm correlation & verification for Group1 of BCCH Missing alarm

Alarm clearing for Group1 of Correlated BCCH alarm

Alarm correlation & verification for Group2 of BCCH Missing alarm

Alarm clearing for Group2 of Correlated BCCH alarm

Synthetic/Pseudo alarm generation for Signalling Gateway (SG)

Alarm clearing for Synthetic/Pseudo Alarm for Signalling Gateway

Synthetic/Containment alarm generation for group of M3UA

Alarm clearing for Synthetic/Containment Alarm for M3UA group

Synthetic/Containment alarm generation for group of IP NS-VC

MODULE NAME / PROCESS NAME: Test Cases for Alarm Correlation

Alarm clearing for Synthetic/Containment Alarm for IP NS-VC

Synthetic/Containment alarm generation for group of NO

Alarm clearing for Synthetic/Containment Alarm for NO AVAILABLE

Synthetic/Containment alarm generation for group of IP NS-VC

Alarm clearing for Synthetic/Containment Alarm for IP NSVC LINK

Synthetic/Containment alarm generation for group of CELL

Alarm clearing for Synthetic/Containment Alarm for CELL LOGICAL

Synthetic/Containment alarm generation for group of DIGITAL

Alarm clearing for Synthetic/Containment Alarm for DIGITAL PATH

Alarm correlation & verification for Group of Cell Outage alarms

Alarm correlation & verification for Group of Cell Outage alarms

MODULE NAME / PROCESS NAME: Test Cases for Alarm Correlation

Alarm correlation & verification for Group of Cell Outage alarms

MODULE NAME / PROCESS NAME: Test Cases for Alarm Correlation

NSN Net Act Alarms Correlation

Auto Clearing of Alarms older than 1 day (24 hours)

Monitor Clearing of Alarms from Thin Client GUI

Input Test Data

Open Clarity Alarm Manager GUI using

Clarity ALARM MANAGER is launched. Alarms will be

NEMS: Refer Appendix A