blob: 9678dd6ffab19951d248a9dfc7053faa10f1b513 [file] [log] [blame]
Herbert Eiselt092189e2019-04-03 17:24:29 +02001.. contents::
2 :depth: 3
3..
4
5Connect
6=======
7
8The 'Connect' application on OpenDaylight provides up-to-date
9connectivity information about the wireless devices in the network. It
10automatically displays new network elements and their connection status.
11Despite the network elements usually automatically mount themselves, an
12additional small window allows manually mounting devices/mediators. For
13better understanding alarms and status, a connection status log lists
14all the connection status changes of OpenDaylight mount points.
15
16Views
17-----
18
19The graphical user interfaces is divided in three sections.
20
21Required Network Elements
22~~~~~~~~~~~~~~~~~~~~~~~~~
23
24Required Network Elements are physical network functions, which are
25planned or expected in the network. This means the identifier, IP
26addresses and its required configuration is well-known and available in
27a planning database or in ONAP A&AI.
28
29This view also offer to manually configure/mount the device with the '+'
30icon. The SDN controller will then start connecting the Netconf server.
31
32Unknown Network Elements
33~~~~~~~~~~~~~~~~~~~~~~~~
34
35Most of the physical network function support an automatic registration
36procedure to the SDN controller. It may happen, that devices are
37connected to the SDN Controller but not available in planning data.
38
39It might be a normal occurrence for very cheap devices, where an entire
40planning process to too expensive. But is may also happen that the
41identifier used in planning process differ from the identifier currently
42configured in the device.
43
44Connection Status Log
45~~~~~~~~~~~~~~~~~~~~~
46
47The log lists the connections status changes between SDN Controller and
48NetConf servers (devices).