Alarm management

OP00003-V11.xSG123D3D - V11x_Ed1
©
1 Nokia 2018 Nokia Confidential

© Nokia 2018 - Nokia Confidential

Learning objectives
Upon completion of this module, you should be able to:
• Describe how to access the current alarms of the system
• Explain the reference for alarm maintenance actions
• Explain the principles of alarm maintenance procedures
• Explain the principle of alarm severity assignment profiles (ASAPs)
• Manage ASAPs
• Explain the concept of LPT.

©
2 Nokia 2018 Nokia Confidential

© Nokia 2018 - Nokia Confidential

Table of contents

Alarm notification 4
Alarm maintenance 8
ASAP management 11
Link Pass Through (LPT) 18
Wrap-up 21

©
3 Nokia 2018 Nokia Confidential

© Nokia 2018 - Nokia Confidential

 Alarm notification parameters

1 Fault detection 2 Fault processing 3 Current alarms

and conditions

Fault management
process

Alarm information:
▪ Time
▪ Source
• Port monitoring mode ▪ Category
• ASAP ▪ Severity
• Alarm confirmation ▪ Description

©
4 Nokia 2018 Nokia Confidential

Alarm information can be accessed through main menu: Reports  Alarm List  Total
(or Critical or Major or Minor) or directly from the alarm space in the tool bar.

© Nokia 2018 - Nokia Confidential

 How to view current alarms

To view current system alarms click on one of the following items

All current alarms

Alternatively go to menu list, click on “Reports” -> “Alarm List” -> “Total” (“Critical”, “Major”, “Minor”)

©
5 Nokia 2018 Nokia Confidential

Parameters:
• Time: indicates the date and time at which the alarm was raised.
• Source: identifier of the component on which the alarm occurred.
• Card: indicates the type of card on which the alarm occurred.
• Category: indicates the category of the component where the alarm occurred, e.g. EQPT
(equipment).
• Severity: indicates the severity of the reported alarm:
• CR – Critical
• MJ – Major
• MN – Minor
• WR – Warning (intended for the ETSI market)
• Description: an optional text description of the condition or problem
• Condition for details check 1830 PSS Maintenance and Trouble-Clearing Guide
• SA Service Affecting

The alarm queues for critical, major, minor, and warning alarms have a size of 500 entries
each. The total number of alarms shows the sum of critical, major, minor, warning alarms.
History alarm buffer may store up to 5,000 alarms. If this limit is reached the oldest
alarm will be overwritten.

© Nokia 2018 - Nokia Confidential

How to view current alarms
Shelf/slot/card level
Alarm severity colored bells are shown on level where alarm is detected
and can be used as shortcut to open the alarm list for the related object

Alarm severity colored Plus/Minus shows that there is an alarm

propagated from a lower level.

To display the alarms select the alarmed object and

press Fault or just press the bell.

©
6 Nokia 2018 Nokia Confidential

© Nokia 2018 - Nokia Confidential

 How to view current conditions

To view current system conditions:

“Reports” -> “Condition List”

©
7 Nokia 2018 Nokia Confidential

The condition list contains all alarms additionally “not alarmed” and “not reported”
events.

© Nokia 2018 - Nokia Confidential

 Perform alarm maintenance actions: overview

Search alarm
Analyze Perform
in Get detailed
Current Alarms maintenance
Maintenance alarm
and procedure to
and Trouble information
Conditions clear alarm
Clearing Guide

©
8 Nokia 2018 Nokia Confidential

For general alarm maintenance topics like

- alarm reference
- trouble clearing procedures
- routine maintenance
please refer to the 1830 Photonic Service Switch (PSS) Maintenance and Trouble-Clearing
Guide.

© Nokia 2018 - Nokia Confidential

Exercise: alarm notification

1. Check the current alarms of the system.

2. Generate a new alarm, e.g. by removing a module (pls. note that module must be assigned
to your team).
Now check where you find the newly generated alarm.

Alarm:_________________

3. Search the alarm in the 1830-PSS Maintenance and Trouble Clearing Guide.

4. Bring back the system into the previous state.

Check whether the respective alarm disappeared.

Time allowed:
10 minutes

©
9 Nokia 2018 Nokia Confidential

© Nokia 2018 - Nokia Confidential

Exercise: alarm maintenance

1. Check the existing alarms of the NE.

2. Open the Maintenance and Trouble Clearing Guide and search for one of the
existing current alarms.
3. Check the corresponding alarm description.
4. Find the procedure to clear the alarm.

Time allowed:
10 minutes

©
10Nokia 2018 Nokia Confidential

© Nokia 2018 - Nokia Confidential

 ASAP management

System-defined ASAP User-defined ASAP

Transmission
ASAPEQPT-0 None
Equipment
Synchronization ASAPEQPT-5
ASAPEQPT-1 SYSDFLT
ASAPEQPT-0 None User Label: UserXYZ
Security NotPrimary
ASAPEQPT-2
ASAPEQPT-1
ASAPEQPT-3 SYSDFLT
FerfAis
ASAPEQPT-0
ASAPEQPT-2 None User defined
ASAPEQPT-4 NotPrimary
QOS ALL
ASAPEQPT-1
ASAPEQPT-3 SYSDFLT
FerfAis
ASAPEQPT-0 None
Management
ASAPEQPT-2
ASAPEQPT-4 NotPrimary
ALL
ASAPEQPT-1 SYSDFLT
communication
ASAPEQPT-3 FerfAis
ASAPEQPT-2
ASAPEQPT-4 NotPrimary
ALL
ASAPEQPT-0 None
Control plane
ASAPEQPT-3 FerfAis 2. Edit ASAP
ASAPEQPT-1 SYSDFLT
ASAPEQPT-4 ALL
ASAPEQPT-0 None
Equipment
ASAPEQPT-2 NotPrimary
ASAPEQPT-1
ASAPEQPT-3 SYSDFLT
FerfAis Equipment
ASAPEQPT-0
ASAPEQPT-2 None
NotPrimary
ASAPEQPT-4 ALL 1. Create ASAP ASAPEQPT-5
ASAPEQPT-1
ASAPEQPT-3 SYSDFLT
FerfAis User Label: UserXYZ
ASAPEQPT-2
ASAPEQPT-4 NotPrimary
ALL
-> clone
ASAPEQPT-3 FerfAis
Clone from ASAPEQPT-4
ASAPEQPT-4 ALL

©
11Nokia 2018 Nokia Confidential

Enable/disable autonomous alarm forwarding

Users have the option to temporarily inhibit the forwarding of autonomously generated alarms
and state events from the NE to the NMS for their session, by assigning a “None” profile. To
restart the autonomous forwarding of alarms again, an enable command has to be issued by the
user.
Alarm suppression
To provision each alarm instance as “reported” or “not reported”. As long as an alarm is
provisioned as “not reported”, it acts as if it has temporarily been removed from the list of
potential alarms.
The condition severities are managed by means of Alarm Severity Assignment Profiles (ASAP). For
each condition, the ASAP indicates the SA/NSA severity and the notification code.
System-defined ASAP
Can neither be modified nor removed.
For each alarm category (profile type), a maximum of five system-defined ASAPs with index
values from 0 to 4 are defined:
ASAP[alarm category]- 0 None All conditions with severity “Not Reported”
ASAP[alarm category]- 1 SYSDFLT Factory default severities
ASAP[alarm category]- 2 Not Primary Not primary conditions with severity disabled
ASAP[alarm category]- 3 FERF & AIS FERF and AIS conditions disabled
ASAP[alarm category]- 4 ALL All conditions enabled

User-defined ASAP
• Users with appropriate privileges are able to create new ASAP instances (profiles) for each
ASAP type.
• To create user-defined ASAPs, an existing ASAP is created by cloning and can be edited
afterwards.
• For each alarm category (profile type), user defined ASAP with index values from 5 to 255
can be created.
© Nokia 2018 - Nokia Confidential
 How to manage ASAP

1. Create ASAP

©
12Nokia 2018 Nokia Confidential

In the first step, a new ASAP shall be created by using a copy of an existing ASAP profile.

© Nokia 2018 - Nokia Confidential

 How to manage ASAP [cont.]
ASAP Types:

1. Create ASAP [cont.]

©
13Nokia 2018 Nokia Confidential

The system provides 28 different ASAP classes.

© Nokia 2018 - Nokia Confidential

 How to manage ASAP [cont.]

2. Edit ASAP

©
14Nokia 2018 Nokia Confidential

As a second step, the new ASAP profile shall be edited.

© Nokia 2018 - Nokia Confidential

 How to manage ASAP [cont.]

2. Edit ASAP [cont.]

©
15Nokia 2018 Nokia Confidential

Note that each ASAP type consists of a different numbers of records. E.g. ASAP Type
EQPT (equipment) contains 236 records (ASAP Type BITS only consists of 4 records).
For each record the severity can be changed (e.g. to a different alarm severity or to “Not
Alarmed” or “Not Reported”).
In this screenshot example the alarm condition for “CARDBOOT” shall be changed from
“Not Reported” to “Major”.

© Nokia 2018 - Nokia Confidential

 How to manage ASAP [cont.]

3. Assign newly created ASAP profile to a board

©
16Nokia 2018 Nokia Confidential

Now the newly created ASAP profile can be assigned to the system.

© Nokia 2018 - Nokia Confidential

Exercise: manage ASAP

1. Check the list of current alarms.

Pick out one alarm whose severity you want to change.
Which alarm did you pick out? _____________________
2. Display the List of ASAP.
3. Create and modify your own ASAP according to the alarm you were picking out under step1.
• Which ASAP do you have to clone? _______________________
• Note: All other alarms should be reported as given in the default ASAP.
4. Assign your newly created ASAP to the alarmed object of step 1.
Check the list of current alarms again.
5. Delete your ASAP and check the alarm list again.

Time allowed:
20 minutes

©
17Nokia 2018 Nokia Confidential

© Nokia 2018 - Nokia Confidential

 LPT - Client Signal Failure (CSF) Scenario

CSF consequent action:

- Disabled/No Laser shutdown
Failure LPT insertion - Laser Off (default)
1 2 3
GFP CSF
PSS-8x ODU PSS-8x

Ethernet Client Ethernet Client

Equipment 1 Equipment 2

LPT supported for all Ethernet ports

©
18Nokia 2018 Nokia Confidential

Link Pass Through (LPT) functionality provides failure detection with triggering of
consequent actions. LPT is supported by all Ethernet interfaces.
The idea of LPT is to propagate failure information of the LAN or WAN link to the remote
end in order to inform the remote end Ethernet equipment about the failure.
Basically LPT behaves, as if the Ethernet-over-OTH equipment is not present and the
Ethernet devices at both ends are directly coupled by a fiber.

For Ethernet interfaces, LPT is always enabled because GFP mapping into ODU is used. By
default, the laser will be switched off when CSF (Client Signal Failure) is detected.

© Nokia 2018 - Nokia Confidential

 LPT - Server Signal Failure (SSF) Scenario

SSF consequent action:

- Disabled/No Laser shutdown (default)
Failure - Laser Off
1 2

PSS-8x ODU PSS-8x

Ethernet Client Ethernet Client

Equipment 1 Equipment 2

LPT supported for all Ethernet ports

©
19Nokia 2018 Nokia Confidential

“Disabled/No Laser shutdown” is the default setting for SSF (Server Signal Failure)
detection.

© Nokia 2018 - Nokia Confidential

LPT settings

1. LPT port settings

• Select Eth-Port (e.g. 10Gb on 20AX200)
• Select “GBE LAN Details” tab
• Configure options for CSF/SSF consequent actions

©
20Nokia 2018 Nokia Confidential

© Nokia 2018 - Nokia Confidential

Wrap-up
In this module we have covered the following items:
Describe how to access the current alarms of the system
Explain the reference for alarm maintenance actions
Explain the principles of alarm maintenance procedures
Explain the principle of alarm severity assignment profiles (ASAPs)
Manage ASAPs
Explain the concept of LPT.

©
21Nokia 2018 Nokia Confidential

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential