ZebM provides a framework and APIs for building management systems for a switch or router. It offers two different sets of programmatic APIs, Transactional API also called CML API and Non transactional API (CLI Equivalent programmatic APIs) also called SMI API. The APIs can be easily integrated with any third party management application. Management of a third party southbound application can also be integrated with ZebM using its framework.
ZebM Framework provides a set of tools for automatically generating most of the backend code for the management APIs. This reduces the effort involved in programming the APIs. ZebM also supports configuration of Linux Based Host Protocols.
ZebM is designed using several inbuilt abstraction layers. These abstraction layers, allow the software to run over multiple control plane CPU and forwarding chipset hardware. The system calls are also well abstracted allowing to switch across operating systems if required. It has been integrated with verified with multiple commodity hardware, which again allows transition easily.
ZebM software design is highly modular with multiple processes handing each individual key protocols. The processes are managed and contained by a process handler framework, which also monitors the processes, restarts and maintains event logging for them. ZebM can be built and packaged with minimal software features, reducing Capex and device footprint.
ZebM solution is built using standards based definitions, as well as has popular vendor specific extensions. The operation and management is provided using CLI and SNMP. This allows the ZebM enabled device to be easily operate and interoperate in a heterogeneous vendor deployment network environments.
ZebM supports next generation technologies like SDN and NFV. ZebM’s centralized transaction based modelling layer allows for service level provisioning and chaining.
OcNOS control plane software design is highly modular with multiple processes handling each individual key protocols. The processes are managed and contained by a process handler framework, which also monitors the processes, restarts and maintains event logging for them.
OcNOS can be customized, built and packaged with minimal software features, reducing CapEx and device footprint. The control plane features support for layer 2 switching, Carrier, Data Center Switching, MPLS/MPLS-TP, comprehensive support for multicast and unicast routing support.