blob: 4e3c9f5a39dc5ceed34f4ad2cae1d67a7b3e51e4 [file] [log] [blame]
Herbert Eiselt092189e2019-04-03 17:24:29 +02001.. contents::
2 :depth: 3
3..
4
5Fault Management
6================
7
8To operate a network, it is important to get an overview about the
9currently raised alarms. The application offers basic fault management
10of devices supporting ONF-TR-532. The alarms are classified according to
11the severity level (warning, minor, major, critical).
12
13Views
14-----
15
Aijana Schumann06fb5292020-02-11 15:44:17 +010016The graphical user interface is separated into three views.
Herbert Eiselt092189e2019-04-03 17:24:29 +020017
Aijana Schumann2c28ede2020-02-28 16:59:53 +010018Current Problem List
19~~~~~~~~~~~~~~~~~~~~
Herbert Eiselt092189e2019-04-03 17:24:29 +020020
Aijana Schumann06fb5292020-02-11 15:44:17 +010021Lists all current active faults in the network. In addition, it also
22lists alarms sent by the SDN controller itself, which detects connection
23losses to the NetConf server (connectionLossOAM) or to a device via a
24mediator to a device (connectionLossNeOAM).
Herbert Eiselt092189e2019-04-03 17:24:29 +020025
26Alarm Notifications
27~~~~~~~~~~~~~~~~~~~
28
Aijana Schumann06fb5292020-02-11 15:44:17 +010029As long as the view is open, all alarm notifications received by the SDN
30Controller are listed. Please note that refreshing the view will start
31the collection again. Previous alarm notification can be viewed in the
32alarm log.
Herbert Eiselt092189e2019-04-03 17:24:29 +020033
34Alarm Log
35~~~~~~~~~
36
37Next to the current active alarms an alarm log lists all alarm
38notifications of the past.
39
40Implementation
41--------------
42
43The application has two parts. While the server is listening for NetConf
Aijana Schumann06fb5292020-02-11 15:44:17 +010044notifications to store them in the database, the client retrieves the
45information from the database and displays them in a table.
Herbert Eiselt092189e2019-04-03 17:24:29 +020046
Aijana Schumann06fb5292020-02-11 15:44:17 +010047The server synchronizes with the current alarm lists of the devices.
48Based on raised and cleared notifications, the current alarm status of
49the network is calculated. The current alarms are stored in a database.
50In addition, all Problem Notifications received by the SDN controller
51are stored. There is no logic implemented on the client side.
Herbert Eiselt092189e2019-04-03 17:24:29 +020052
Aijana Schumann06fb5292020-02-11 15:44:17 +010053An alarm status bar in the header of the web application informs the
Herbert Eiselt092189e2019-04-03 17:24:29 +020054operator about the health status of the network.
55
Aijana Schumann2c28ede2020-02-28 16:59:53 +010056The ODLUX web application uses web sockets to update the graphical user
57interface of the Alarm Notifications (devices) and Connection Status
58Notifications in real-time.