Collect statistics, status, and run and manage your network solution in a model-driven, standards-based way.

Enea Element On-Device Management

Network Management with NETCONF and YANG - Enea On-Device Management is a model driven network function management agent that provide standard-based Northbound interfaces for configuration, monitoring and control of both Physical and Virtual Network Functions (PNFs and VNFs).


The importance of standards in a multi-vendor network cannot be exaggerated. In order to be cost efficient, the Operator wants to be able to manage all network devices with one Network Management System. Such a task is significantly simplified if all network devices provide northbound interfaces that follow standards like NETCONF. Similarly, the network devices should be modelled in a standardized fashion, e.g in YANG.

Enea Element On-Device Management provides support for both modelling in YANG or SMI, as well as standards based Northbound Interfaces like NETCONF and SNMP.


As the networks grow in size and complexity, it becomes important to manage the network devices more intelligently. To configure network devices individually is both time consuming and costly, but this has historically been the predominant method. Northbound interfaces like SNMP and CLI simply are not designed for managing network devices at scale.

Element ODM supports NETCONF, a Northbound Interface designed to address the shortcomings of legacy network management protocols like SNMP and CLI.


Evaluation and trial software

Want to try Enea Element On-Device Management on your own and evaluate what it can do for you? Get a copy of the latest trial software now.

Sign up

Why Enea Element On-Device Management


Element ODM can be extended with high availability support in Enea Element High Availability offering 99,999% availability, support for software management including in-service upgrades, etc.


Enea On-Device Management is pre-integrated with Enea ElementCenter (Enea’s solution for orchestration and EMS/NMS). The integration is optimized and full of added value. 


Enea is an independent vendor, and Enea Element On-Device management supports approved standards to avoid any potential vendor lock-in.


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.


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.


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.


Download a product overview for Enea Element  On-Device Management.

Download PDF 

VNF Management Agent

Software Defined Networking (SDN) and Network Functions Virtualization (NFV) bring a host of benefits to the communications service provider/carrier community.

Download PDF 


How Enea Element On-Device Management can be configured to manage a fault-tolerant pair of Polyhedra database servers.

Download PDF 


Simplify Distributed Systems with Frameworks from Enea Element - a whitepaper on how to design systems that are scalable, manageable, and highly available.

Download PDF 

Enea Device Management and Orchestration

Enea's Network Management solutions reduce risk and accelerate time-to-market, and enable a seamless transition to NFV devices.

NFV Management

We manage VNFs with NETCONF and YANG thanks to the integration of Enea ElementCenter NMS and Enea On-device Management. This demo shows our network management offering which provides a standards-based and integrated framework suitable for NFV service orchestration.


Building a system that is always on and always providing service requires a full spectrum commitment. This starts with a reliable hardware platform that is architected for high availability and ends with an overall hardware and software system architecture and software solution that runs non-stop. These software solutions require redundancy and scalability, leading to distributed system design.