| Herbert Eiselt | 092189e | 2019-04-03 17:24:29 +0200 | [diff] [blame] | 1 | .. contents:: |
| 2 | :depth: 3 |
| 3 | .. |
| 4 | |
| 5 | Fault Management |
| 6 | ================ |
| 7 | |
| 8 | To operate a network, it is important to get an overview about the |
| 9 | currently raised alarms. The application offers basic fault management |
| 10 | of devices supporting ONF-TR-532. The alarms are classified according to |
| 11 | the severity level (warning, minor, major, critical). |
| 12 | |
| 13 | Views |
| 14 | ----- |
| 15 | |
| 16 | The graphical user interface is separated in three views. |
| 17 | |
| 18 | Current Alarms |
| 19 | ~~~~~~~~~~~~~~ |
| 20 | |
| 21 | It list all current active faults in the network. In addition it also |
| 22 | list alarms sent by the SDN controller itself, which detects connections |
| 23 | losses to the NetConf server (connectionLossOAM) or which detects |
| 24 | connection loss to a devices via a mediator to a device |
| 25 | (connectionLossNeOAM). |
| 26 | |
| 27 | Alarm Notifications |
| 28 | ~~~~~~~~~~~~~~~~~~~ |
| 29 | |
| 30 | As long as the view is open, it lists all alarm notification reached by |
| 31 | the SDN Controller. Please note that refreshing the view will start the |
| 32 | collection again. Previous alarm notification can be viewed in the alarm |
| 33 | log. |
| 34 | |
| 35 | Alarm Log |
| 36 | ~~~~~~~~~ |
| 37 | |
| 38 | Next to the current active alarms an alarm log lists all alarm |
| 39 | notifications of the past. |
| 40 | |
| 41 | Implementation |
| 42 | -------------- |
| 43 | |
| 44 | The application has two parts. While the server is listening for NetConf |
| 45 | notifications to store them in the database the client retrieves the |
| 46 | information from the database and displays them in a grid view. |
| 47 | |
| 48 | The server synchronizes with the current alarm lists of the devices and |
| 49 | calculates based on raise and clear notifications the current alarm |
| 50 | status of the network. The current alarms are stored in a database. In |
| 51 | addition all Problem Notifications received by the SDN controller are |
| 52 | stored. There is no logic implemented on the client. |
| 53 | |
| 54 | An alarm status bar on top of each graphical user interface informs the |
| 55 | operator about the health status of the network. |
| 56 | |
| 57 | The OpenDaylight DLUX web application uses web sockets for updating the |
| 58 | graphical user interface in case of Problem Notification (devices) and |
| 59 | Connection Status Notifications (ODL). |