12 7302 5523 operator fault management

12
Alcatel-Lucent University Antwerp 1 University Fault management 7302-7330/5523 operator part 1 section K Alcatel-Lucent University University

Upload: belbel4321

Post on 30-Sep-2015

232 views

Category:

Documents


8 download

DESCRIPTION

12 7302 5523 Operator Fault Management

TRANSCRIPT

PowerPoint PresentationAlcatel-Lucent University
University
During class please switch off your mobile, pager or other that may interrupt.
Entry level requirements:
Describe how alarms are handled by the AWS
retrieve a list of all the current alarms (NE or object level) Perform actions on a alarm (acknowledge, …)
describe the different actions that can be performed on an alarm
retrieve detailed information of a specific alarm
*
dynamically updated
CURRENT ALARMS
(Current AS-IM)
HISTORICAL ALARMS
(Historical AS-IM)
Historical Alarms Management
Allows consultation of alarms that are cleared and acknowledged and thus not considered as current anymore
*
sublists
counters
e.g acknowledge, purge
Counter Summary Window
The way alarms are handled is similar in both current and historical parts of the alarm application
AS Current USM
AS Historical USM
The alarms can be displayed in lists while alarm counters keep track of statistics.
Counter Summary Window
In CAL USM there are more predefined sublist than in HAL USM.
In CAL USM there are sublists per severity level and a sublist for all cleared current alarms.
By mouse clicking, the user can
Obtain detailed alarm information
Alarm Sublist Window
More Information Window
Perform action on the alarm when the alarm is raised (only in CAL USM, not in HAL!).
*
Main menu Administration Application Alarms
CAL counter summary window opens up
Application
Alarms
AWS
APL. MGR
*
Via ANEL
Via EML-USM
sublists for:
Via ANEL
Select one NE and go to the menu View - Show - Alarms.
Automatically a sublist for the selected NE will be generated.
Via EML-USM
The system generates an alarm sublist. You can choose if you want to see all the alarms on the NE or only the alarms on the selected object. The selected object can be the rack, subrack, board, physical port, logical port …
*
new alarm(s) occured since the last selection of the sublist
Information box
Indicator field
The sublists are updated according to the flow of incoming alarms. When an alarm arrives, filter matching is tried for each sublist. If the test is successful for a given sublist, the alarm is added to this sublist, according to its display and sort criteria.
In the Current Alarm Counter Summary Window a default/predefined set of sublists exist. The predefined sublists table is composed of:
The Main Alarm Sublist containing all the available alarms. It is a special sublist which filtering properties cannot be changed (filtering panel is insensitive).
The Default Alarm Sublist
The Critical (resp. Major, Minor, Warning, Indeterminate) sublist containing the subset of alarms with severity critical (resp. major, minor, warning, indeterminate).
The Cleared Alarm sublist containing the subset of alarms which have been cleared.
The exclamation tag, on the left of the sublist name, informs the user that new alarms have arrived in the concerned sublist. If the user selects (i.e. single click) or opens (i.e. double click) the sublist, then this flag disappears (until there are new incoming alarms)
For each sublist, each of the counters may be shown or not.
Inactive sublists have all their counters set to X.
The "." character means there is no alarm in the corresponding field.
The information box briefly displays every action the user chooses in the menu bar.
*
pre-defined sublists
Rightclick on alarm perform action on alarm
Sublist Alarm summary
Alarm details
By right-clicking on an alarm you can do a number of actions on that alarm. These actions are
- Acknowledge
- Reserve
- Unreserve
- Manual Purge
- Manual Clear (only possible on certain alarms! Most alarms aren’t manually clearable!)
The Alarm details appear in different colors. These colors give an indication on the status of the alarm.
For each incoming alarm, the alarm line has the same color as the alarm severity.
If the alarm is cleared, the line turns green.
If the alarm is acknowledged, the line turns grey/brown.
If the alarm is reserved, the line turns grey
*
*
When the alarm is CLEARED and ACKed (Auto-ACK is possible)
When the alarm is PURGED
(Auto-purge is possible)
Sublists
(USM)
Sublists
(USM)
Alarm
How to navigate to the HAL USM will be explained in the Advanced AWS Operator course.
You can only navigate to the HAL USM from the CAL USM.
You need to filter which historical alarms you want to list (e.g. only the critical alarms which were archived during the last month).
Alcatel-Lucent University Antwerp
Fault Management – exercises
Before you start these exercises, close all the AWS windows except for the ANEL window.
1.       Make sure you have an additional workspace in your CDE environment to put in the CAL-USM.
2.       Focus on the ANEL window while you remove your LT board (inform your colleagues!). What do you see?
3.       Navigate to the specific object on which the alarm occurred. While doing so, try to analyze the tags and messages on the different screens. When you are on board level, do you still see the alarm? Why (not)?
 
5.       What is the system proposed solution for the generated alarm in exercise 2? How did you find this information?
 
7.      Acknowledge the alarm and see what happens
*
9.       Is it possible to see the alarms of multiple ISAMs at the time? If yes, how?
10.   Can you see the current alarms of an ISAM that is not supervised?
If you stop supervising your NE, can you still see the alarms you saw before in the CAL?
11.   Switch off the power of your CPE modem. Will the ISAM generate an alarm? Do you see this event at the AWS? Why (not)?|
 
 
Review Questions
 
*