Frinx ODL Distribution
Targeted at end-users and resellers/developers/OEM customers, releases are synchronized to the ODL release schedule.
Curated and tested – each release passes through stages of rigorous quality assurance before we make it available to our customers.
Production Support – FRINX offers support options to address the needs of your deployment stage from lab to production.
FRINX components and modules – make our distribution more useful and simpler to use and operate compared with the public ODL version.
The most recent addition to the FRINX modules in FRINX ODL is the UniConfig Framework. Its purpose is to manage configuration of networking devices with a unified OpenConfig based interface. In addition, the UniConfig framework enables device and network wide transactions so that the network will always remain in a well-defined state without leftovers from failed configuration attempts.
The UniConfig framework consists of 3 layers that can be accessed individually or through the UniConfig manager API.
[expand title=”Southbound layer“]
The lowest layer (Southbound layer) provides connectivity to the network devices through NETCONF and CLI via Telnet and SSH. It includes translation units that map data in OpenConfign format to vendor specific CLI implementations. This translation unit library is open source and publicly available on GitHub (https://github.com/FRINXio/translation-units-docs). [/expand]
[expand title=”Unified layer“]
The next layer (Unified layer) combines devices mounted under various protocols (e.g. NETCONF and CLI) and makes them accessible under a unified mount point to higher layers. This abstracts the type of southbound protocol used away from the user for regular device interaction. The unified layer also provides Openconfig YANG to vendor specific YANG translation capabilities. [/expand]
[expand title=”UniConfig layer“]
The top layer (UniConfig layer) provides the ability to read and write OpenConfig based configurations to and from devices. It also adds the capability to create configuration snapshots that can be committed and can be rolled back by the system if they have failed. The UniConfig layer also adds the capabilities to compare network intent (located in the configuration data store), analyze the diffs between intended state and actual state (located in the operational data store) and finally apply the new state to the devices connected through lower layers in an atomic operation. This means that only configuration elements that were changed in the most recent operation need to be sent to the devices and not the complete configuration. [/expand]
The UniConfig layer can be used by applications (e.g. L3VPN and L2VPN service modules provided by FRINX or customer applications by our customers) or by users directly through REST calls (e.g. via Postman collections or via the FrinxIT CLI).
Figure 1: FRINX UniConfig Framework
Figure 2: Accessing UniConfig Manager through FrinxIT CLI
FRINX also offers service modules that take advantage of the UniConfig framework device configuration functionality. Those service modules provide L2VPN and L3VPN service API based on the IETF standards and drafts respectively.
Figure 3: L3VPN service module
Frinx also offers training, customized consulting and development packages to bootstrap, accelerate or implement your ODL and open source based networking projects.
For questions and orders please contact our team at firstname.lastname@example.org.
Frinx ODL Base Support
The Frinx ODL Base Support option allows for unlimited SW upgrades for the duration of the support contract (12 months). Support is available via our support portal. Our support team will respond to you no later than the next business day.
Frinx ODL Production Support
Includes all components of the Base Support package with the following additions: You have access to email and phone support available 8×5 during CET business hours and our support team will get back to you no later than 4 hours after you have contacted us. Please contact our team email@example.com for 24×7 support options and more options regarding SLAs.
Chosen when critical network resources and service revenue depend on the uptime of Frinx ODL instances.
A detailed description of FRINX services and support options can be found in the Frinx Master Service Agreement. Please contact us at firstname.lastname@example.org.