You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 7
Next »
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkhlcmJlcnQgRWlzZWx0Iiwib3V0cHV0VHlwZSI6ImJsb2NrIiwibGFzdE1vZGlmaWVyTmFtZSI6IkhlcmJlcnQgRWlzZWx0IiwibGFuZ3VhZ2UiOiJlbiIsImRpYWdyYW1EaXNwbGF5TmFtZSI6IiIsInNGaWxlSWQiOiIiLCJhdHRJZCI6IjcxODI4ODY3IiwiZGlhZ3JhbU5hbWUiOiJzZG5yLWNvbnRyb2xsZXItYnVuZGxlcyIsImFzcGVjdCI6IiIsImxpbmtzIjoiYXV0byIsImNlb05hbWUiOiJDb250cm9sbGVyIGJ1bmRsZXMiLCJ0YnN0eWxlIjoidG9wIiwiY2FuQ29tbWVudCI6ZmFsc2UsImRpYWdyYW1VcmwiOiIiLCJjc3ZGaWxlVXJsIjoiIiwiYm9yZGVyIjp0cnVlLCJtYXhTY2FsZSI6IjEiLCJvd25pbmdQYWdlSWQiOjcxODI4ODY2LCJlZGl0YWJsZSI6ZmFsc2UsImNlb0lkIjo3MTgyODkxNSwicGFnZUlkIjoiIiwibGJveCI6dHJ1ZSwic2VydmVyQ29uZmlnIjp7ImVtYWlscHJldmlldyI6IjEifSwib2RyaXZlSWQiOiIiLCJyZXZpc2lvbiI6NiwibWFjcm9JZCI6IjliYzAwZWM0LTNjN2MtNDViNi04OTY5LThlN2M2ODZjNjUyMiIsInByZXZpZXdOYW1lIjoic2Ruci1jb250cm9sbGVyLWJ1bmRsZXMucG5nIiwibGljZW5zZVN0YXR1cyI6Ik9LIiwic2VydmljZSI6IiIsImlzVGVtcGxhdGUiOiIiLCJ3aWR0aCI6IjEwNjEiLCJzaW1wbGVWaWV3ZXIiOmZhbHNlLCJsYXN0TW9kaWZpZWQiOjE1ODkyMTM5MDMwMDAsImV4Y2VlZFBhZ2VXaWR0aCI6ZmFsc2UsIm9DbGllbnRJZCI6IiJ9
In words:
- the base is a Service which provides a Netconfnode-state-API by using a netconf-change-listener
- on top of this service several devicemanagers which can register a callback function for a connected netconfnode
- the devicemanager can then decide if it wants to keep the netconfsession (based on capabilities) and register a notification listener on this or it wants to ignore it
- the notification-service provides the messages for the websevice cluster, so that GUI clients can be informed about changes
- these messages are:
- mountpoint created
- mountpoint deleted
- ProblemNotification
- AttributeValueChangedNotification
- data-provider has to register on netconfnode-state-API for filling tables:
- network-element-connection
- faultlog
- faultcurrent
- maintenancemode