DATA MODELING AND AUTO RENDERING
Data modeling involves the ability to model a device and the services provided by the device. A data model is a conceptual abstraction of the device and its implementation. The data model will provide the interface for the network device, for the configuration services and the monitoring services supported by the network device.
YANG is a data modelling language well suited to writing data models. YANG is based on XML, a language designed to be both human- and machine-readable. YANG also supports the distinction between ‘configuration data’ and ‘state data’ – the latter being of operational nature and suited for ‘read-operations’.
Some strengths of YANG are:
- Human readable data models
- Support of hierarchal object models through XML foundation
- Formal constraints can be used for the validation of data model configurations
Element ODM supports auto-rendering of all Northbound Interfaces from YANG models.
The Northbound Interface of Element ODM connects with the Southbound Interface of the Element Management System or Network Management System (EMS/NMS).
Element ODM provides a rich set of Northbound Interfaces:
- NETCONF (NETwork CONFiguration protocol)
- REST (REpresental State Transfer protocol)
- SNMP (Simple Network Management Protocol)
- CLI (Command Line Interface)
The support for standardized interfaces like NETCONF and SNMP enable true multi-vendor solutions.
The Northbound interfaces will typically provide information on configuration and state data, alarms, performance data, and access/session control.
THE SOUTHBOUND INTERFACE
In Element On-Device Management, the Southbound Interface handles the integration between the ‘Object Manager’ component and the resources of the managed device. The Southbound Interface integration is transparent, i.e there is one single interface regardless of the number of Northbound Interfaces.
The Element On-Device Management programming model is simple and powerful. Its API is well designed to handle hierarchical Managed Object models, and a true strength thereof is that it is location transparent, in the sense that all distribution of data is handled by Element On-Device Management. Further, the API has a powerful subscription service where notifications are issued when events occur. Hence, polling is no longer needed and the developer is thus greatly relieved of these burdens.
LOGGING, INSTRUMENTATION, AND HIGH AVAILABILITY
Element On-Device Management is enhanced with a number of optional yet powerful services that will add value to the product, or be of great help during the development of the product.
The logging services are fully customizable, and include support for features like classification and filtering of logs.
The run-time debug services offer the user the possibility to create own commands for instrumentation and trouble shooting. Such commands can be extremely valuable during product development.