OcNOS is the industry’s first full-featured network OS for White Box. Its features include advanced capabilities, such as extensive switching and routing protocol support, MPLS (Multiprotocol Label Switching), and SDN (software defined networking). OcNOS features hybrid, centralized or distribute network support; scalable, modular high performance network; and a robust data plane built on merchant silicon.
OcNOS provides seamless transition from traditional networks to open networks with investment protection. OcNOS gives network operators, carriers and enterprises the physical software solution needed to achieve the disaggregated networking model. Instead of a vendor locked-in model, and proprietary solution models, a disaggregated networking model allows network operators to build networks with diverse, manage networks on their own, and rapidly deploy new networking features and services at less TCO.
Based on the widely-deployed and time-tested ZebOS network stack, OcNOS brings the power of the Open Compute Project, an open hardware movement and foundation, to data networking.
For Current OcNOS Compatible Hardware, Please visit: http://ipinfusion.genacomdev5.com/hardware-compatibility-list/
OcNOS is a robust, programmable and innovative operating system, featuring a single software image that runs across the entire portfolio of Open Compute platforms from leading network device vendors. This guarantees consistent operations, workflow automation and high availability, while significantly reducing operational expenses.
OcNOS borrows heavily from the popular ZebOS line of products, which provides a rich feature density and robustness that has been built up over the years and validated in thousands of diverse customer networks. OcNOS provides industry standard CLI, supports all standard MIBs and other standard operation and management tools. Its integrated centralized management and provisioning layer allows for transaction-based configuration and device feature modelling. The management layer has support for Netconf, REST APIs besides custom CLI generation capability. This allows an OcNOS system to be configured, managed and controlled by Network Management System for scaled topologies and in multiple ways.
OcNOS is a modular, multi-tasking network operating system, with tight integration capabilities on commodity hardware. This design allows for scaled and performance critical deployments. The niche coupling with merchant silicon utilizes key hardware capabilities for better performance and feature set.
OcNOS is designed using several abstraction layers. The hardware abstraction layer, allows the OcNOS 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 and verified with multiple commodity hardware, which again allows seamless portability across diverse network hardware.
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.
OcNOS solution is built using open networking standards, as well as popular vendor specific extensions for device management. The operation and management is provided using CLI and SNMP which is built on top a fully transactional management plane. This allows the OcNOS-based network node to be easy to operate and interoperate with another vendor node. The OcNOS management plane can support a wide variety of management interfaces like CLI, SNMP, REST, NETCONF, SAF IMM-OI and any future or custom north bound management interface.
OcNOS supports technologies required for bandwidth scaling at data centers and interconnects. The OcNOS centralized transaction based managed object modeling layer allows for multiple management interfaces. This, in turn, allows for a central service level provisioning and chaining across multiple devices. OcNOS infrastructure is SDN and NFV ready. The control plane and data plane has support for SDN support through OpenFlow. The SMI based C APIs provides end users the ability to write user defined functions to program the network control and data plane to provide custom programmable network operations.
OcNOS provides standards based redundancy protocols like VRRP, BFD, ring failure recovery protocols, MLAG, UDLD and graceful restart mechanisms. This protocol level redundancy provides guaranteed network level redundancy. For device level redundancy, OcNOS supports service availability frameworks based master-slave hot standby syncing. This feature is supported for several key protocols allowing device level redundancy in the absence of peer level network support. The modularity of OcNOS allows for individual process/protocol level upgrades and restarts without disturbing the running system for easy software upgrades. OcNOS will support ISSU for stateless upgrades. OcNOS has an in-built process heart beat monitoring and restart feature for process survivability in a 1 rack unit or multi-chassis format. This architecture helps in minimizing downtime in mission-critical network deployments.
IP Infusion’s Open Compute Operating System (OcNOS) has been designed from the ground-up and is optimized to address the needs of public/private/hybrid cloud networks, while enabling new applications and ushering in the era of Software Defined Networks (SDN), newer, demanding data center and enterprise network environments.
It is the industry’s most advanced network operating system for open compute platforms. Combining modern-day software and operating system (O/S) concepts, transparently restartable processes, open platform development, an un-modified Linux kernel, and a stateful database model.