OpenConfig is a collaborative effort in the networking industry to move toward a more dynamic, programmable method for configuring and managing multivendor networks. OpenConfig supports the use of vendor-neutral data models to configure and manage the network. These data models define the configuration and operational state of network devices for common network protocols or services. The data models are written in YANG, a standards-based, data modeling language that is modular, easy to read, and supports remote procedure calls (RPCs). Using industry standard models greatly benefits an operator with devices in a network from multiple vendors. The goal of OpenConfig is for operators to be able to use a single set of data models to configure and manage all the network devices that support the OpenConfig initiative.
OpenConfig for Junos OS supports the YANG data models and uses RPC frameworks to facilitate communications between a client and the router. You have the flexibility to configure your router directly by using Junos OS, or by using a third-party schema, such as OpenConfig. OpenConfig modules define a data model through its data, and the hierarchical organization of and constraints on that data. Each module is uniquely identified by a namespace URL to avoid possible conflicts with the Junos OS name.
The configuration and operational statements in Junos OS have corresponding path statements in OpenConfig. The following is a list of data modules for which mapping of OpenConfig and Junos OS configuration and operational statements is supported:
When you configure OpenConfig statements on devices running Junos OS, the following features are not supported:
Using configure batch or configure private mode
Configuring statements under the [edit groups] hierarchy
For more information on the OpenConfig initiative, see http://www.openconfig.net/.