- play_arrow gRPC Overview
- play_arrow OpenConfig to Junos Mapping
- Mapping OpenConfig 802.1X Commands to Junos Configuration
- Mapping OpenConfig AAA Commands to Junos Operation
- Mapping OpenConfig BGP Commands to Junos Configuration
- Mapping OpenConfig BFD Commands to Junos Operation
- Mapping OpenConfig Firewall Filter Commands to Junos Configuration
- Mapping OpenConfig Interface Commands to Junos Configuration
- Mapping OpenConfig ISIS Commands to Junos Configuration
- Mapping OpenConfig LACP Commands to Junos Configuration
- Mapping OpenConfig LDP Commands to Junos Configuration
- Mapping OpenConfig LLDP Commands to Junos Configuration
- Mapping OpenConfig Local Routing Commands to Junos Configuration
- Mapping OpenConfig MACsec Model Commands to Junos Configuration
- Mapping OpenConfig MPLS Commands to Junos Configuration
- Mapping OpenConfig Multicast Commands to Junos Configuration
- Mapping OpenConfig Network Instance Commands to Junos Operation
- Mapping OpenConfig OSPF Commands to Junos Configuration
- Mapping OpenConfig QoS Commands to Junos Configuration
- Mapping OpenConfig Routing Policy Commands to Junos Configuration
- Mapping OpenConfig System Logging Model Commands to Junos Configuration
- Mapping OpenConfig System Management Model Commands to Junos Configuration
- Mapping OpenConfig System Model Commands to Junos Configuration
- Mapping OpenConfig System Terminal Model Commands to Junos Configuration
- Mapping OpenConfig Telemetry System Model Commands to Junos Configuration
- Mapping OpenConfig VLAN Commands to Junos Configuration
- play_arrow Configuration Statements and Operational Commands
OpenConfig Overview
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:
BGP
Interfaces
LACP
LLDP
Local routing
MPLS
Network instance
Platform
Routing policy
VLAN
When you configure OpenConfig statements on devices running Junos OS, the following features are not supported:
Using
configure batchorconfigure privatemodeConfiguring statements under the
[edit groups]hierarchy
For more information on the OpenConfig initiative, see http://www.openconfig.net/.
