Upload
others
View
45
Download
0
Embed Size (px)
Citation preview
Junos® OS
OpenConfig User Guide
Published
2021-12-15
Juniper Networks, Inc.1133 Innovation WaySunnyvale, California 94089USA408-745-2000www.juniper.net
Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc.in the United States and other countries. All other trademarks, service marks, registered marks, or registered servicemarks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the rightto change, modify, transfer, or otherwise revise this publication without notice.
Junos® OS OpenConfig User GuideCopyright © 2021 Juniper Networks, Inc. All rights reserved.
The information in this document is current as of the date on the title page.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-relatedlimitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for usewith) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User LicenseAgreement ("EULA") posted at https://support.juniper.net/support/eula/. By downloading, installing or using suchsoftware, you agree to the terms and conditions of that EULA.
ii
Table of Contents
About This Guide | v
1 OpenConfig Overview
OpenConfig Overview | 2
OpenConfig Data Model Version | 3
Installing the OpenConfig Package | 12
2 gRPC Overview
Understanding OpenConfig and gRPC on Junos Telemetry Interface | 15
Installing the Network Agent Package (Junos Telemetry Interface) | 44
gRPC Services for Junos Telemetry Interface | 47
Configuring gRPC for the Junos Telemetry Interface | 48
Configuring Bidirectional Authentication for gRPC for Junos Telemetry Interface | 50
Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface) | 52
3 OpenConfig to Junos Mapping
Mapping OpenConfig AAA Commands to Junos Operation | 124
Mapping OpenConfig BGP Commands to Junos Configuration | 129
Mapping OpenConfig Interface Commands to Junos Configuration | 152
Mapping OpenConfig LLDP Commands to Junos Configuration | 159
Mapping OpenConfig Local Routing Commands to Junos Configuration | 160
Mapping OpenConfig MPLS Commands to Junos Configuration | 162
Mapping OpenConfig Network Instance Commands to Junos Operation | 178
Mapping OpenConfig Routing Policy Commands to Junos Configuration | 183
Mapping OpenConfig System Logging Model Commands to Junos Configuration | 188
Mapping OpenConfig System Management Model Commands to Junos Configuration | 191
iii
Mapping OpenConfig System Model Commands to Junos Configuration | 194
Mapping OpenConfig System Terminal Model Commands to Junos Configuration | 199
Mapping OpenConfig VLAN Commands to Junos Configuration | 204
4 Configuration Statements
netconf | 208
schema | 211
track-igp-metric (LSP) | 213
iv
About This Guide
Use this guide to configure and model both configurational and operational data of your switches androuters using OpenConfig data models.
v
1CHAPTER
OpenConfig Overview
OpenConfig Overview | 2
OpenConfig Data Model Version | 3
Installing the OpenConfig Package | 12
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 theuse of vendor-neutral data models to configure and manage the network. These data models define theconfiguration and operational state of network devices for common network protocols or services. Thedata models are written in YANG, a standards-based, data modeling language that is modular, easy toread, and supports remote procedure calls (RPCs). Using industry standard models greatly benefits anoperator with devices in a network from multiple vendors. The goal of OpenConfig is for operators to beable to use a single set of data models to configure and manage all the network devices that support theOpenConfig initiative.
OpenConfig for Junos OS supports the YANG data models and uses RPC frameworks to facilitatecommunications between a client and the router. You have the flexibility to configure your routerdirectly by using Junos OS, or by using a third-party schema, such as OpenConfig. OpenConfig modulesdefine 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 OSname.
The configuration and operational statements in Junos OS have corresponding path statements inOpenConfig. The following is a list of data modules for which mapping of OpenConfig and Junos OSconfiguration 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 arenot supported:
2
• 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/.
RELATED DOCUMENTATION
OpenConfig Data Model Version | 3
Understanding YANG on Devices Running Junos OS
NETCONF XML Management Protocol Developer Guide
OpenConfig Data Model Version
Table 1 on page 3 lists the OpenConfig data model versions.
Table 1: OpenConfig Data Model Versions
OpenConfig Data Model Junos OS Release OpenConfig SupportedVersion
Supported Platform
• AAA (openconfig-aaa.yang)
• AAA Types (openconfig-aaa-types.yang)
• AAA TACACS(openconfig-aaa-tacacs.yang)
• AAA RADIUS(openconfig-aaa-radius.yang)
19.3 0.4.1 Juniper Networks ACX Series,EX Series, MX Series, PTXSeries, and QFX Series
• BGP (openconfig-bgp.yang)
16.1 2.0.1 Juniper Networks MX Seriesand PTX Series
17.1 2.1.1
3
Table 1: OpenConfig Data Model Versions (Continued)
OpenConfig Data Model Junos OS Release OpenConfig SupportedVersion
Supported Platform
• BGP NEIGHBOR(openconfig-bgp-neighbor.yang)
• BGP POLICY(openconfig-bgp-policy.yang)
• BGP TYPES (openconfig-bgp-types.yang)
17.2, 17.2X75,17.3, 17.4, 18.1,18.2, 18.3
Juniper Networks MX Series,PTX Series, and QFX Series
18.4, 19.1, 19.2 4.0.1
• BGP COMMON(openconfig-bgp-common.yang)
• BGP COMMONMULTIPROTOCOL(openconfig-bgp-common-multiprotocol.yang)
• BGP COMMONSTRUCTURE(openconfig-bgp-common- structure.yang)
• BGP GLOBAL(openconfig-bgp-global.yang)
• BGP PEER GROUP(openconfig-bgp-peer-group.yang)
17.1 2.1.1 Juniper Networks MX Seriesand PTX Series
17.2, 17.2X75,17.3, 17.4, 18.1,18.2, 18.3
Juniper Networks MX Series,PTX Series, and QFX Series
18.4, 19.1, 19.2 4.0.1
BGP ERRORS (openconfig-bgp-errors.yang)
18.4, 19.1, 19.2 4.0.1 Juniper Networks MX Seriesand PTX Series
4
Table 1: OpenConfig Data Model Versions (Continued)
OpenConfig Data Model Junos OS Release OpenConfig SupportedVersion
Supported Platform
• IF AGGREGATE(openconfig-if-aggregate.yang)
• IF ETHERNET(openconfig-if-ethernet.yang)
• IF IP (openconfig-if-ip.yang)
• IF IP EXT (openconfig-if-ip-ext.yang)
• INTERFACES(openconfig-interfaces.yang)
16.1, 17.1, 17.2,17.2X75, 17.3,17.4, 18.1, 18.2,18.3, 18.4, 19.1,19.2
1.0.1 Juniper Networks MX Seriesand PTX Series
INET TYPES (openconfig-inet-types.yang)
17.2X75, 17.3,17.4, 18.1, 18.2,18.3, 18.4
0.1.0 Juniper Networks MX Series,PTX Series, and QFX Series
IKE INTERFACES(openconfig-ike.yang)
18.1R3, 18.2DCB,18.2X75-D5
1.0.0 Juniper Networks MX Series
• ISIS ( openconfig-isis.yang)
• ISIS LSDB TYPES(openconfig-isis-lsdb-types.yang)
• ISIS LSP (openconfig-isis-lsp.yang)
• ISIS POLICY (openconfig-isis-policy.yang)
17.2X75, 17.4,18.1, 18.2, 18.3
0.2.1 Juniper Networks MX Seriesand PTX Series
5
Table 1: OpenConfig Data Model Versions (Continued)
OpenConfig Data Model Junos OS Release OpenConfig SupportedVersion
Supported Platform
• ISIS ROUTING(openconfig-isis-routing.yang)
• ISIS TYPES (openconfig-isis-types)
18.4, 19.1, 19.2 0.3.3
LACP (openconfig-lacp.yang) 16.1, 17.1 1.0.2 Juniper Networks MX Seriesand PTX Series
17.2, 17.2X75,17.3, 17.4, 18.1
Juniper Networks MX Series,PTX Series, and QFX Series
18.2, 18.3, 18.4,19.1, 19.2
1.1.0
LACP (openconfig-lacp.yang) 21.4R1 Evolved 1.1.1 Juniper NetworksPTX10001-36MR,PTX10003,PTX10004, PTX10008, andPTX10016 routers.
• LLDP (openconfig-lldp.yang)
• LLDP TYPES (openconfig-lldp-types.yang)
16.1, 17.1, 17.2,17.2X75, 17.3,17.4, 18.1, 18.2,18.3, 18.4, 19.1,19.2
0.1.0 Juniper Networks MX Seriesand PTX Series
LLDP (openconfig-lldp.yang) 21.4R1 Evolved 0.2.1 Juniper Networks PTX10008and PTX10016 routers
LOCAL ROUTING(openconfig-local-routing.yang)
16.1, 17.1 1.0.0 Juniper Networks MX Seriesand PTX Series
6
Table 1: OpenConfig Data Model Versions (Continued)
OpenConfig Data Model Junos OS Release OpenConfig SupportedVersion
Supported Platform
17.2, 17.2X75,17.3, 17.4, 18.1,18.2, 18.3, 18.4,19.1, 19.2, 20.2R1Junos OS Evolved
Juniper Networks MX Series,PTX Series, and QFX Series
MPLS (openconfig-mpls.yang)
16.1, 17.1 1.0.0 Juniper Networks MX Seriesand PTX Series
17.2 Juniper Networks MX Series,PTX Series, and QFX Series
17.3 1.0.1
17.2X75, 17.4,18.1, 18.2, 18.3,18.4, 19.1, 19.2
2.2.0
• MPLS IDP (openconfig-mpls-ldp.yang)
• MPLS IGP (openconfig-mpls-igp.yang)
• MPLS RSVP (openconfig-mpls-rsvp.yang)
• MPLS SR (openconfig-mpls-sr.yang)
• MPLS STATIC(openconfig-mpls-static.yang)
• MPLS TE (openconfig-mpls-te.yang)
16.1, 17.1 1.0.0 Juniper Networks MX Seriesand PTX Series
17.2, 17.3 Juniper Networks MX Series,PTX Series, and QFX Series
7
Table 1: OpenConfig Data Model Versions (Continued)
OpenConfig Data Model Junos OS Release OpenConfig SupportedVersion
Supported Platform
• MPLS TYPES(openconfig-mpls-types.yang)
17.2X75, 17.4,18.1, 18.2, 18.3,18.4, 19.1, 19.2
2.2.0
NETWORK INSTANCE(openconfig-network-instance.yang)
17.3, 17.4, 18.1,18.2, 18.3, 18.4,19.1, 19.2, 20.2R1Junos OS Evolved
0.4.0 Juniper Networks ACX Series,EX Series, MX Series, PTXSeries, and QFX Series
17.2X75 0.4.1
• NETWORK INSTANCE l2(openconfig-network-instance-l2.yang)
• NETWORK INSTANCE l3(openconfig-network-instance-l3.yang)
• NETWORK INSTANCETYPES (openconfig-network- instance-types.yang)
17.2X75, 17.3,17.4, 18.1, 18.2,18.3, 18.4, 19.1,19.2
0.4.0 Juniper Networks MX Series,PTX Series, and QFX Series
• PLATFORM (openconfig-platform.yang)
• PLATFORM TYPES(openconfig-platform-types.yang)
16.1, 17.1, 17.2,17.2X75, 17.3,17.4, 18.1, 18.2,18.3, 18.4, 19.1,19.2
0.3.0 Juniper Networks MX Seriesand PTX Series
PLATFORM TRANSCEIVERS(openconfig-platform-transceiver.yang)
19.1, 19.2 0.1.0 Juniper Networks MX Series
8
Table 1: OpenConfig Data Model Versions (Continued)
OpenConfig Data Model Junos OS Release OpenConfig SupportedVersion
Supported Platform
POLICY TYPES (openconfig-policy-types.yang)
16.1, 17.1 2.0.0 Juniper Networks MX Seriesand PTX Series
17.2, 17.2X75,17.3, 17.4, 18.1,18.2, 18.3, 18.4,19.1, 19.2
Juniper Networks MX Series,PTX Series, and QFX Series
• RIB BGP (openconfig-rib-bgp.yang)
• RIB BGP EXT(openconfig-rib-bgp-ext.yang)
• RIB BGP TYPES(openconfig-rib-bgp-types.yang)
16.1, 17.1 0.2.0 Juniper Networks MX Seriesand PTX Series
17.2, 17.2X75,17.3, 17.4, 18.1,18.2, 18.3, 18.4,19.1, 19.2
Juniper Networks MX Series,PTX Series, and QFX Series
ROUTING POLICY(openconfig-routing-policy.yang)
16.1, 17.1 2.0.0 Juniper Networks MX Seriesand PTX Series
17.2, 17.2X75,17.3, 17.4, 18.1,18.2, 18.3, 18.4,19.1, 19.2
Juniper Networks MX Series,PTX Series, and QFX Series
20.3 2.0.1 EX2300, EX3400, EX4300,EX4600, and EX9200 switches
RPC API (openconfig-rpc-api.yang)
, 19.1, 19.2 0.1.0 Juniper Networks MX Series,PTX Series, and QFX Series
9
Table 1: OpenConfig Data Model Versions (Continued)
OpenConfig Data Model Junos OS Release OpenConfig SupportedVersion
Supported Platform
SEGMENT ROUTING(openconfig-segment-routing.yang)
17.2X75, 17.3,17.4, 18.1, 18.2,18.3, 18.4, 19.1,19.2
0.0.3 Juniper Networks MX Seriesand PTX Series
SYSTEM LOGGING MODEL(openconfig-syste-logging.yang)
21.4R1 Evolved 0.3.1 PTX10008 and PTX10016routers
SYSTEM MANAGEMENTMODEL (openconfig-syste-management.yang)
21.4R1 Evolved 0.3.0 PTX10008 and PTX10016routers
SYSTEM MODEL(openconfig-system.yang)
21.4R1 Evolved 0.6.1 PTX10008 and PTX10016routers
SYSTEM TERMINAL MODEL(openconfig-system-terminal.yang)
21.4R1 Evolved 0.3.1 PTX10008 and PTX10016routers
TELEMETRY (openconfig-telemetry.yang)
16.1, 17.1, 17.2,17.2X75, 17.3,17.4, 18.1, 18.2,18.3, 18.4, 19.1,19.2
0.2.0 Juniper Networks MX Series,PTX Series, and QFX Series
TERMINAL DEVICE(openconfig-terminal-device.yang)
19.1, 19.2 0.3.1 Juniper Networks MX Series,PTX Series, and QFX Series
TRANSPORT TYPES(openconfig-transport-types.yang)
16.1 0.2.0 Juniper Networks MX Seriesand PTX Series
10
Table 1: OpenConfig Data Model Versions (Continued)
OpenConfig Data Model Junos OS Release OpenConfig SupportedVersion
Supported Platform
17.1, 17.2,17.2X75, 17.3,17.4, 18.1, 18.2,18.3, 18.4, 19.1,19.2
0.3.1
TYPES (openconfig-types.yang)
16.1 0.1.1 Juniper Networks MX Seriesand PTX Series
17.1 0.2.0 Juniper Networks MX Seriesand PTX Series
17.2, 17.3 Juniper Networks MX Series,PTX Series, and QFX Series
17.2X75, 17.4,18.1, 18.2, 18.3,18.4, 19.1, 19.2
0.3.2
• VLAN CONFIGURATIONSUPPORT (openconfig-vlan.yang)
• VLAN TYPES(openconfig-vlan-types.yang)
16.1, 17.1, 17.2 1.0.1 Juniper Networks EX Seriesand QFX Series
17.2X75, 17.3,17.4, 18.1, 18.2,18.3, 18.4, 19.1,19.2
YANG TYPES (openconfig-yang-types.yang)
17.2X75, 17.3,17.4, 18.1, 18.2,18.3, 18.4, 19.1,19.2
0.1.0 Juniper Networks MX Series,PTX Series, and QFX Series
RELATED DOCUMENTATION
OpenConfig Overview | 2
11
Understanding YANG on Devices Running Junos OS
NETCONF XML Management Protocol Developer Guide
Installing the OpenConfig Package
Starting in Junos OS Release 18.3R1, the Junos OS image includes the OpenConfig package; therefore,you do not need to install OpenConfig separately on your device.
By default, the OpenConfig schema is not available through CLI. To unhide the OpenConfig knob fromthe CLI, run the following command:
set system schema openconfig unhide
NOTE: The show system yang package command in the operational mode does not display nativeJunos OS OpenConfig package. This is because the Junos OS image includes the OpenConfigpackage.
OpenConfig package includes the following files:
• OpenConfig set of data models—Data models are written in YANG.
• Translation scripts—Translates OpenConfig configuration schemas to Junos OS configurationschemas for each supported Junos OS release.
• Deviation modules—Specifies the unsupported nodes within the schema for each supported JunosOS release.
• Augmentation module—Specifies additions to various OpenConfig specified models.
• Dynamic rendering files—Maps operational state data for each supported Junos OS release.
In releases before Junos OS Release 18.3R1, OpenConfig for Junos OS software package have thefollowing naming convention:
junos-openconfig-XX.YY.ZZ.JJ-signed.tgz (Junos OS) junos-openconfig-x86-32-XX.YY.ZZ.JJ.tgz (Junos OS with Upgraded FreeBSD)
where:
• XX represents the OpenConfig major release number.
12
• YY represents the OpenConfig minor release number.
• ZZ represents the OpenConfig patch release number.
• JJ represents the Juniper Networks release number.
NOTE: The junos-openconfig-x86-32-XX.YY.ZZ.JJ.tgz package supports both 32 and 64 bit systems.
To install the OpenConfig for Junos OS software package, use the following command:
request system software add
For example:
user@router> request system software add junos-openconfig-XX.YY.ZZ.JJ-signed.tgz
or
user@router> request system software add junos-openconfig-x86-32-XX.YY.ZZ.JJ.tgz
For more details on the OpenConfig for Junos OS software package, see Release Notes available withthe package on the Juniper Software Download website.
Release History Table
Release Description
18.3R1 Starting in Junos OS Release 18.3R1, the Junos OS image includes the OpenConfig package; therefore,you do not need to install OpenConfig separately on your device.
RELATED DOCUMENTATION
Understanding YANG on Devices Running Junos OS
NETCONF XML Management Protocol Developer Guide
Software Installation and Upgrade Guide
Release Information for Junos OS with Upgraded FreeBSD
schema | 211
13
2CHAPTER
gRPC Overview
Understanding OpenConfig and gRPC on Junos Telemetry Interface | 15
Installing the Network Agent Package (Junos Telemetry Interface) | 44
gRPC Services for Junos Telemetry Interface | 47
Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface) | 52
Understanding OpenConfig and gRPC on JunosTelemetry Interface
IN THIS SECTION
Network Agent Software | 18
Using OpenConfig for Junos OS to Enable Junos telemetry interface | 18
Using gRPC to Stream Data | 19
Exporting Packet Forwarding Engine Traffic Sensor Data | 21
Enabling “ON CHANGE” Sensor Support Through gNMI | 24
Enabling “TARGET_DEFINED” Subscription Mode through gNMI | 25
Enabling “INITIAL_SYNC” Subscription Mode through gNMI | 26
Enabling Client Streaming and Bidirectional Streaming of Telemetry Sensor Information | 28
Enabling Streaming of Telemetry Sensor Information for SR-TE policies (BGP or Static) | 29
Support for LSP Statistics | 30
Dynamic Tunnel Statistics Support | 33
FPC and Optics Support | 33
JTI Broadband Edge Statistics Support for Junos Fusion on MX Series | 34
CPU and NPU Sensor Support for MX Series Routers with MPC10E-15C-MRATE Line Cards | 34
Interface Express Sensor | 35
Standby Routing Engine Sensors for Subscribers | 35
Diameter Application Protocol and Diameter Peer Sensors for Subscribers | 36
Interface Burst Monitoring | 37
Transceiver Diagnostics | 38
Physical Ethernet Interface Sensor | 39
VLAN Sensors | 39
Starting in Junos OS Release 16.1R3, you can use a set of remote procedure call (RPC) interfaces toconfigure the Junos telemetry interface and stream telemetry data using the gRPC framework.OpenConfig supports the use of vendor-neutral data models for configuring and managing multivendornetworks. gRPC is an open source framework that provides secure and reliable transport of data.
15
NOTE: OpenConfig for Junos OS and gRPC are supported only on MPCs on MX Series and onPTX Series routers starting with Junos OS Release 16.1R3.
Starting with Junos OS Release 17.2R1, OpenConfig and gRPC are also supported on QFX10000switches, QFX5200 switches, and PTX1000 routers.
Starting with Junos OS Release 17.3R1, Junos telemetry interface is supported on the RoutingControl and Board (RCB) on PTX3000 routers, QFX5110 switches, and EX4600 and EX9200switches.OpenConfig and gRPC are not supported on MX80 and MX104 routers.
Starting with Junos OS Release 17.4R1, MX2008 routers are supported.
Starting with Junos OS Release 18.3R1, ON_CHANGE streaming of LLDP telemetry sensor informationis supported through gRPC for MX Series and PTX Series routers.
Starting with Junos OS Release 18.3R1, QFX5120-48Y and EX4650 switches are also supported.
Starting with Junos OS Release 18.4R1, EX4600 switches are also supported.
Starting with Junos OS Release 18.4R1, MX480, MX960, MX2010, MX2020, MX2008 and MX-ELMrouters are also supported.
Starting with Junos OS Release 19.1R1, MX Series routers operating with MS-MIC and MS-MPC,QFX10002 switches, and PTX10002 routers are also supported.
Starting in Junos OS Evolved Release 19.1R1, OpenConfig (OC) and Junos telemetry interface (JTI) aresupported. Both gRPC APIs and the customer-facing CLI remain the same as for the Junos OS. As wasstandard for Junos OS, Network Agent (NA) and OC packages are part of the Junos OS Evolved image.
Starting with Junos OS Evolved 19.1R1, Packet Forwarding Engine sensors on PTX10003 routers arealso supported.
Starting with Junos OS Release 19.2R1, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800,and vSRX Series Services Gateways.
Starting with Junos OS Release 19.2R1, gNMI services for streaming Packet Forwarding Engine statisticsis supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, andQFX5100 and QFX5200 switches.
Starting with Junos OS Release 19.2R1, gNMI services for streaming statistics is supported onQFX5100, QFX5110, QFX5120, QFX5200 and QFX5210 switches.
Starting with Junos OS Release 19.3R1, gRPC service for exporting statistics is supported on MX Seriesrouters hosting MPC10E-10C-MRATE and MPC10E-15C-MRATE line cards.
16
Starting with Junos OS Evolved Release 19.3R1, gRPC service for exporting statistics is supported onQFX5220-128C and QFX5220-32CD switches.
Starting with Junos Release 19.4R1, gRPC service for streaming Packet Forwarding Engine and RoutingEngine statistics is supported on EX4300-MP switches.
NOTE: JTI support for PTX10008 routers is documented for Junos OS Evolved Release 19.4R1,but not supported.
Starting with Junos Release 20.R1, gNMI service for streaming telemetry sensors for Packet ForwardingEngine statistics is supported on MX2K-MPC11E line cards on MX2010 and MX2020 routers.
Starting with Junos OS Release 20.1R1, gRPC services version v1.18.0 is supported with JTI. Thisversion includes important enhancements for gRPC. In earlier Junos OS releases, gRPC version v1.3.0 issupported with JTI.
Starting with Junos OS Evolved Release 20.2R1, gRPC service for streaming NDP statistics is supportedon PTX10001 routers.
Starting with Junos OS Release 20.2R1, gRPC service for streaming Packet forwarding Engine andRouting Engine statistics is supported on EX2300, EX2300-MP, and EX3400 switches.
Starting with Junos OS Release 20.2R1, gRPC service for streaming BGP routing information base (RIB)and BGP peer statistics is supported on any platform family that supports containerized routing protocolprocess (cRPD). cRPD is Juniper’s routing protocol process (rpd) decoupled from Junos OS and packagedas a Docker container to run in Linux-based environments.
Starting with Junos OS Release 20.2R1, ON_CHANGE BGP peer statistics export using gRPC servicesand gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000,PTX10000 routers and QFX5100 and QFX5200 switches.
Starting with Junos OS Release 20.2R1, streaming BGP global, peer and perr groups statistics usinggRPC services is supported on EX2300, EX3400, EX4300, EX4600, and EX9200 switches.
Starting with Junos OS Release 20.2R1, streaming revenue interface statistics through PacketForwarding Engine sensors and pseudo interface statistics through Routing Engine sensors using gRPCservices and gNMI services is supported on SRX5400, SRX5600, and SRX5800 Services Gateways..
Starting with Junos OS Release 20.2R1, streaming revenue interface statistics through PacketForwarding Engine sensors and pseudo interface statistics through Routing Engine sensors using gRPCservices and gNMI services is supported on SRX5400, SRX5600, and SRX5800 Services Gateways.
Starting with Junos OS Release 20.2R1 sensors to stream standby Routing Engine statistics aresupported on MX480, MX960, MX10003, MX2010, and MX2020 routers.
17
Starting with Junos OS Release 20.2R1 sensors to stream EVPN statistics using gRPC services aresupported with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008,and QFX10016 switches.
Network Agent Software
Implementing OpenConfig with gRPC for Junos telemetry interface requires that you download andinstall a package called Network Agent if your Juniper Networks device is running a version of Junos OSwith Upgraded FreeBSD. For all other versions of Junos OS, the Network Agent functionality isembedded in the software. Network Agent functions as a gRPC server and terminates the OpenConfigRPC interfaces. It is also responsible for streaming the telemetry data according to the OpenConfigspecification. To view the OpenConfig specification for telemetry, see the OpenConfig Telemetryspecification. For more information about OpenConfig for Junos OS, see the OpenConfig User Guide.
The Network Agent component also supports server-based Secure Sockets Layer (SSL) authentication.Client-based SSL authentication is not supported. You must install SSL certificates on your JuniperNetworks device.
For information about installing the Network Agent package, see Installing the Network Agent Package.
Using OpenConfig for Junos OS to Enable Junos telemetry interface
OpenConfig for Junos OS specifies an RPC model to enable the Junos telemetry interface. You mustdownload and install the OpenConfig for Junos OS package on your Juniper Networks device Thispackage also includes the required YANG models. Using a Web browser, navigate to the All JunosPlatforms software download URL on the Juniper Networks webpage: https://www.juniper.net/support/downloads/. From the Network Management tab, scroll down to select OpenConfig. Select the Softwaretab. Select the appropriate version of OpenConfig module. Two versions are available, one for devicesrunning Junos OS with Upgraded FreeBSD and another for devices running all other versions of JunosOS. For more information, see "Installing the OpenConfig Package" on page 12 and Understanding JunosOS YANG Modules.
The programmatic interface OpenConfigTelemetry that is installed by the Network Agent package definesthe telemetry gRPC service. The telemetrySubscribe RPC specifies the following subscription parameters:
• OpenConfig path that identifies the system resource to stream telemetry data, for example:/interfaces/interface/state/counters/
• Interval at which data is reported and streamed to the collector server, in milliseconds, for example:sample_frequency = 4000
18
The telemetrySubscribe RPC is used by a streaming server, or collector, to request an inline subscription fordata at the specified path. The device should then send telemetry data back on the same connection asthe subscription request.
Using gRPC to Stream Data
Per the OpenConfig specification, only gRPC-based transport is supported for streaming data. The gRPCserver that is installed by the Network Agent package terminates the gRPC sessions from themanagement system that runs the client. RPC calls trigger the creation of Junos OS sensors that eitherstream data periodically or report events, which are then funneled onto the appropriate gRPC channelby Network Agent.
NOTE: Starting in Junos OS Release 18.2R1, when an external streaming server, or collector,provisions sensors to export data through gRPC on devices running Junos OS, the sensorconfiguration is committed to the junos-analytics instance of the ephemeral configurationdatabase, and the configuration can be viewed by using the show ephemeral-configuration instancejunos-analytics operational command. In earlier releases, the sensor configuration is committed tothe default instance of the ephemeral configuration database.
NOTE: The Juniper telemetry header that was exported as part of updates is now exported as anextension header. GnmiJuniperTelemetryHeader.proto is used to decode the updates fromJuniper devices running Junos OS Release 19.3 or earlier andGnmiJuniperTelemetryHeaderExtension.proto is used for devices running Junos OS Release 19.4or later.
See Table 2 on page 19 for a list and descriptions of the RPCs implemented to support the Junostelemetry interface.
Table 2: Telemetry RPCs
RPC Name Description
telemetrySubscribe Specify telemetry parameters and stream data for the specified listof OpenConfig paths.
19
Table 2: Telemetry RPCs (Continued)
RPC Name Description
getTelemetrySubscriptions Retrieve the list of subscriptions that are created throughtelemetrySubscribe.
cancelSubscription Unsubscribe a subscription created through telemetrySubscribe.
Data streamed through gRPC is formatted in OpenConfig key/value pairs in protocol buffers (gpb)messages. In this universal format, keys are strings that correspond to the path of the system resourcesin the OpenConfig schema for the device being monitored. The values correspond to integers or stringsthat identify the operational state of the system resource, such as interface counters, and the state ofthe resource.
NOTE: Starting in Junos OS Release 18.2R1, data streamed through gRPC can be formatted asprotobuf in addition to key/value pairs for OpenConfig-based routing engine (RE) sensors. Thesesensors are in addition to the packet forwarding engine (PFE) sensors.
The following shows the universal key/value format:
message KeyValue { string key = 1 [(telemetry_options).is_key = true]; uint64 int_value = 2; string str_value = 3; string prefix_str = 4;}
message TelemetryStream { // router name or export IP address required string system_id = 1 [(telemetry_options).is_key = true]; // line card / RE (slot number) optional uint32 component_id = 2 [(telemetry_options).is_key = true]; // PFE (if applicable) optional uint32 sub_component_id = 3 [(telemetry_options).is_key = true]; // timestamp (common to all entries in the kv array)
20
optional uint64 timestamp = 4 [(telemetry_options).is_timestamp = true]; // key / value pairs repeated KeyValue kv;}
The following example shows how a set of counters for an interface can be represented:
key = “/interfaces/counters/rx-bytes”, int_value = 1000key = “/interfaces/counters/tx-bytes”, int_value = 2000key = “/interfaces/counters/rx-packets”, int_value = 10key = “/interfaces/counters/rx-bytes” , int_value = 20key = “/interfaces/counters/oper-state”, str_value = “up”
The Network Agent package provides a mapping table that maps field names to the OpenConfig keystrings.
Exporting Packet Forwarding Engine Traffic Sensor Data
Starting with Junos OS Release 17.4R1, you can export Packet Forwarding Engine traffic statisticsthrough the Junos telemetry interface for MX Series and PTX Series routers. Both UDP and gRPC aresupported.
This sensor tracks reporting of Packet Forwarding Engine statistics counters and provides visibility intoPacket Forwarding Engine error and drop statistics. The resource name for the sensor is /junos/system/linecard/packet/usage/. The OpenConfig paths report data specific to CPU, NPU and center chip (CC). Thefollowing paths are supported:
• /components/component[name='FPCid:NPUid']/properties/property[name='counter']/state/value, where FPC refersto the Flexible PIC Concentrator and NPU refers to the network processing unit (packet forwardingengine). A sample resource path is /components/component[name='FPC0:NPU3']/properties/property[name='ts-output-pps']/state/value where hwds-data-error is the counter for Hardware Discards: Data Error.
• /components/component[name='FPCid:CCid’]/properties/property[name='counter’]/state/value , where FPC refersto the Flexible PIC Concentrator and CC refers to the center chip. A sample resource path is /components/component[name='FPC0:CC1']/properties/property[name='lpbk-packets’']/state/value where lpbk-packets is the count of Forward packets specific to FPC0, center chip 1.
• /components/component[name='FPCid’]/properties/property[name='counter’]/state/value , where FPC refers tothe Flexible PIC Concentrator. A sample resource path is /components/component[name='FPC0']/properties/
21
property[name='lts-input-packets’']/state/value where lts-input-packets is the CPU counter Local packetsinput.
To provision the sensor to export data through gRPC, use the telemetrySubcribe RPC to specify telemetryparameters. For streaming through UDP, all parameters are configured at the [edit services analytics]hierarchy level.
The following is a map of counters to output fields in the show pfe statistics traffic command or show pfestatistics traffic detail command (supported only on MX Series routers).
CPU stats: (FPCX:CPUY)Packet Forwarding Engine local traffic statistics: Local packets input : 2 Local packets output : 1 Software input control plane drops : 0 Software input high drops : 0 Software input medium drops : 0 Software input low drops : 0 Software output drops : 0 Hardware input drops : 0
Counterlts-input-packets Local packets input lts-output-packets Local packets output lts-sw-input-control-drops Software input control plane drops lts-sw-input-high-drops Software input high drops lts-sw-input-medium-drops Software input medium drops lts-sw-input-low-drops Software input low drops lts-sw-output-low-drops Software output drops
NPU stats: (FPCX:CCY) Input packets: 1169 0 pps Output packets: 0 0 pps Fabric Input : 277235149 16078 pps Fabric Output : 277235149 16079 pps
Counterts-input-packets Input packetsts-input-packets-pps Input packets in pps
22
ts-output-packets Output packets ts-output-packets-pps Output packets in ppsts-fabric-input-packets Fabric Input ts-fabric-input-packets-pps Fabric Input in ppsts-fabric-output-packets Fabric Outputts-fabric-output-packets-pps Fabric Output in pps
Packet Forwarding Engine loopback statistics: Forward packets : 0 0 pps Forward bytes : 0 0 bps Drop packets : 0 0 pps Drop bytes : 0 0 bps
Counterlpbk-packets Forward packetslpbk-packets-pps Forward packets ppslpbk-packets-byte Forward bytes lpbk-packets-bps Forward bytes bps
lpbk-drop-packets Drop packets lpbk-drop-packets Drop packets ppslpbk-drop-packets Drop bytes lpbk-drop-packets Drop bytes bps
Lu chips stats: FPCx:NPUYCounterlts-hw-input-dropshwds-normal Hardware discards normal discardhwds-fabric Hardware discards fabric dropshwds-info-cell Hardware discards info cell dropshwds-timeout Hardware discards timeourhwds-truncated-key Hardware discards truncated keyhwds-bits-to-test Hardware discards bits to testhwds-stack-underflow Hardware discards stack underflowhwds-stack-overflow Hardware discards stack overflowhwds-data-error Hardware discards data errorhwds-extended Hardware discards extended discardhwds-invalid-iif Hardware discards invalid interfacehwds-input-checksum Hardware discards input checksumhwds-output-mtu
23
hwds-inet-bad-routehwds-inet6-bad-routehwds-filter-discardhwds-dlu-not-routable
Enabling “ON CHANGE” Sensor Support Through gNMI
Periodical streaming of OpenConfig operational states and counters has been supported since Junos OSRelease 16.1, exporting telemetry data from Juniper equipment to an external collector. While useful incollecting all the needed information and creating a baseline “snapshot,” periodical streaming is lessuseful for time-critical missions. In such instances, you can configure ON_CHANGE streaming for anexternal collector to receive information only when operational states experience a change in state.
To support ON_CHANGE streaming, a new specification called gRPC Network Management Interface(gNMI) is implemented for the modification and retrieval of configurations from a network element.Additionally, the gNMI specification can be used to generate and control telemetry streams from anetwork element to a data collection system. Using the new gNMI specification, one gRPC servicedefinition can provide a single implementation on a network element for both configuration andtelemetry as well as a single NMS element to interact with a device by means of telemetry andconfiguration RPCs.
The Junos file package (junos-telemetry-interface) includes the gnmi.proto file andGnmiJuniperTelemetryHeader.proto Juniper extension for gNMI support.
Information about the RPCs supporting this feature can be found in the gNMI Proto file version 0.4.0(the supported version) and the specification released
• https://github.com/openconfig/reference/blob/primary/rpc/gnmi/gnmi-specification.md
• https://github.com/openconfig/gnmi/blob/primary/proto/gnmi/gnmi.proto
The telemetry RPC subscribe under gNMI service supports ON_CHANGE streaming. RPC subscribe allowsa client to request the target to send it values of particular paths within the data tree. Values may bestreamed (STREAM), sent one-off on a long-lived channel (POLL), or sent one-off as a retrieval (ONCE).
If a subscription is made for a top level container with a sample frequency of 0, leaves withON_CHANGE support are streamed based on events. Other leaves will not be streamed.
NOTE: In order to permit a device to decide which nodes will be streamed as ON_CHANGE andwhich will SAMPLE, the collector must subscribe for TARGET_DEFINED with sample_interval.
24
Enabling “TARGET_DEFINED” Subscription Mode through gNMI
Starting with Junos OS Release 20.2R1, TARGET_DEFINED subscription mode with gRPC NetworkManagement Interface (gNMI) services is supported for JTI on MX5, MX10, MX40, MX80, MX104,MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, andMX10016 routers.
Using a gNMI subscription, an external collector stipulates how sensor data should be delivered:
• STREAMING mode periodically streams sensor data from the DUT at a specified interval.
• ON_CHANGE mode sends updates for sensor data from the DUT only when data values change.
• Newly supported TARGET_DEFINED mode (submode 0) instructs the DUT to select the relevantmode (STREAMING or ON_CHANGE) to deliver each element (leaf) of sensor data to the externalcollector. When a subscription for a sensor with submode 0 is sent from the external collector to theDUT, the DUT responds, activating the sensor subscription so that periodic streaming does notinclude any of the ON_CHANGE updates. However, the DUT will notify the collector wheneverqualifying ON_CHANGE events occur.
Subscriptions will default to a periodic streaming frequency of 30 seconds unless otherwise specified bythe collector in the subscription request.
The Java Script Object Notification (JSON) file below shows a sample gNMI subscription.TARGET_DEFINED mode is set using submode=0 for the resource (sensor) path /interfaces/interface[name='lo0']/state.
$ cat gnmi.json{ "dut_list":[ { "port":50051, "rpc":["sub_request"], "sub_request":{ "subscription":[ { "path":"/interfaces/interface[name='lo0']/state", "submode":0, "sample_interval":30 } ], "mode":0, "encoding":2 }
25
} ]$ python ./gnmi_subscribe_client_sample.py -c ./gnmi.json -d 10.53.32.102 -l client.log
The Junos file package (junos-telemetry-interface) includes the gnmi.proto file andGnmiJuniperTelemetryHeader.proto Juniper extension for gNMI support.
For more information, see the gNMI specifications and gNMI protocol file here:
gNMI telemetry specification gNMI protocol definition
• https://github.com/openconfig/reference/blob/primary/rpc/gnmi/gnmi-specification.md#35152-stream-subscriptions
• https://github.com/openconfig/gnmi/blob/primary/proto/gnmi/gnmi.proto
Enabling “INITIAL_SYNC” Subscription Mode through gNMI
Starting in Junos OS Release 20.2R1, INITIAL_SYNC statistics from Packet Forwarding Engine sensorsusing gNMI services on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers, PTX10000line of routers, and QFX5100 and QFX5200 switches is supported.
Starting in Junos OS Evolved Release 20.4R1, INITIAL_SYNC statistics from Packet Forwarding Enginesensors using gNMI services on QFX5130-32CD switches is supported.
When an external collector sends a subscription request for a sensor with INITIAL_SYNC (gnmi-submode 2), the host sends all supported target leaves (fields) under that resource path at least once tothe collector with the current value. This is valuable because:
• The collector has a complete view of the current state of every field on the device for that sensorpath.
• Event-driven data (ON_CHANGE) is received by the collector at least once before the next event isseen. In this way, the collector is aware of the data state before the next event happens.
• Packet Forwarding Engine sensors that contain zero counter values (zero-suppressed) that normallydo not show up in streamed data are sent, ensuring that all fields from each line card (also referred toas source) are known to the collector.
INITIAL_SYNC submode requires that at least one copy to be sent to the collector; however, sendingmore than one is acceptable.
Subscriptions will default to a periodic streaming frequency of 30 seconds unless otherwise specified bythe collector in the subscription request.
26
The Java Script Object Notification (JSON) file below shows a sample gNMI subscription. INITIAL_SYNCmode is set using gnmi_submode 2 for the resource (sensor) path /interfaces/. The gnmi_mode is set to 0. Theprotocol encoding is set to 2 for GBP.
{ "influx": { "server": "server1", "port": 8086, "dbname": "gD40", "measurement": "OC", "user": "influx", "password": "influxdb", "recreate": true }, "gnmi": { "mode": 0, <---- STREAM "encoding": 2, <--- PROTO encoding "prefix": "/x/y/z" }, "host": "10.10.130.73", "port": 10162, "user": "user1", "password": "password1", "cid": "cid-1jk", "paths":[ { "path": "/interfaces/", "Freq": 10000000000, "gnmi_submode": 2 <---- SAMPLE } ] }
The Junos file package (junos-telemetry-interface) includes the gnmi.proto file andGnmiJuniperTelemetryHeader.proto Juniper extension for gNMI support.
For more information, see the gNMI specifications and gNMI protocol file here:
gNMI telemetry specification gNMI protocol definition
• https://github.com/openconfig/reference/blob/primary/rpc/gnmi/gnmi-specification.md#35152-stream-subscriptions
27
• https://github.com/openconfig/gnmi/blob/primary/proto/gnmi/gnmi.proto
Enabling Client Streaming and Bidirectional Streaming of TelemetrySensor Information
Starting with Junos OS Release 18.1R1, OpenConfig support through Remote Procedure Calls (gRPC)and JTI is extended to support client streaming and bidirectional streaming of telemetry sensorinformation on MX Series and PTX Series routers.
APIs are implemented in Junos based on Protobuf specifications for OpenConfig. These APIs performconfiguration, operational state retrieval, and telemetry on Junos routers using gRPC as the transportmechanism.
With client streaming, the client sends a stream of requests to the server instead of a single request. Theserver typically sends back a single response containing status details and optional trailing metadata.With bidirectional streaming, both client and server send a stream of requests and responses. The clientstarts the operation by invoking the RPC and the server receives the client metadata, method name, anddeadline. The server can choose to send back its initial metadata or wait for the client to start sendingrequests. The client and server can read and write in any order. The streams operate completelyindependently.
Junos devices can be managed through API (RPC) prototypes:
• rpc Capabilities (CapabilityRequest)
Returns (CapabilityResponse). Allows the client to retrieve the set of capabilities that is supported bythe target.
• rpc Get (GetRequest)
Returns (GetResponse). Retrieves a snapshot of data from the target.
• rpc Set (SetRequest)
Returns (SetResponse). Allows the client to modify the state of data on the target.
• rpc Subscribe (stream SubscribeRequest)
Returns (stream SubscribeResponse). Allows a client to request the target to send it values forparticular paths within the data tree. These values may be streamed (STREAM) or sent one-off on along-lived channel (POLL), or sent as a one-off retrieval (ONCE). If a subscription is made for a top-level container with a sample frequency of 0, leaves with ON_CHANGE support are streamed basedon events. Other leaves will not be streamed.
28
Juniper Extension Toolkit (JET) support provides insight to users regarding the status of clientsconnected to JSD. JET support for gRPC includes expanding the maximum number of clients that canconnect to JSD from 8 to 30 (the default remains 5). To specify the maximum number of connections,include the max-connections statement at the [edit system services extension-service request-response grpc]hierarchy level.
To provide information regarding the status of clients connected to JSD, issue the enhanced showextension-service client information command and include the clients or servers options. The clients optiondisplays request-response client information. The servers option displays request-response serverinformation.
Enabling Streaming of Telemetry Sensor Information for SR-TE policies(BGP or Static)
Starting with Junos OS Release 18.3R1, OpenConfig support for MX Series and PTX Series throughgRPC and JTI provides continuous statistics streaming via the same sensor irrespective of the route thatis active (BGP or static) for a given Segment Routing Traffic Engineering (SR-TE) policy.
Support is available in Junos OS Evolved Release 21.4R1EVO for PTX10001-36MR, PTX10004,PTX10008, and PTX10016 routers.
This feature provides support for BGP [DRAFT-SRTE] and statically configured SR-TE policies at ingressrouters.
To provision the sensor to export data through gRPC streaming, use the telemetrySubscribe RPC tospecify telemetry parameters. Include the resource path /mpls/signaling-protocols/segment-routing/ toexport these statistics.
In addition to configuring the sensor, you must enable statistics collection through the Junos OS. To dothis, include the statistics configuration statement at the [edit protocols source-packet-routing telemetry]hierarchy level. Optionally, you can limit statistics by including the no-transit or no-ingress parameter.
See Configure a NETCONF Proxy Telemetry Sensor in Junos for instructions on configuring a sensor.
See Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface) for further information aboutresource paths.
29
Support for LSP Statistics
You can provision the LSP statistics sensor /junos/services/label-switched-path/usage/ to monitor per-MPLS LSP statistics. Telemetry data is streamed from Junos devices and exported through JTI toexternal collectors at configurable intervals through gRPC without involving polling.
Initial support of this feature in Junos OS Release 15.1F6 supported ingress LSPs only when asubscription was made to /junos/services/label-switched-path/usage/. With bypass support added tothis feature in Junos OS Release 17.4R1, this subscription now streams both ingress LSP and bypass LSPstatistics to a collector.
Statistics that are streamed are similar to the output displayed by the operational mode commands showmpls lsp bypass statistics and show mpls lsp ingress statistics.
For bypass LSPs, the following are exported:
• Bypass LSP originating at the ingress router of the protected LSP.
• Bypass LSP originating at the transit router of the protected LSP.
• Bypass LSP protecting the transit LSP as well as the locally originated LSP.
When the bypass LSP is active, traffic is exported both on the bypass LSP and the ingress (protected)LSP.
To provision a sensor to export data through gRPC, use the telemetrySubscribe RPC to specify telemetryparameters. Streaming telemetry data through gRPC also requires the OpenConfig for Junos OS module.Both OpenConfig and Network Agent packages are bundled into the Junos OS image by default.
See Configuring a Junos Telemetry Interface Sensor (CLI Procedure) for information about configuring aUDP (native) sensor.
See Table 3 on page 30 for the level of LSP sensor support by platform.
Table 3: LSP Support by Platform
Platform Ingress LSP, UDP
Feature Introduced
Ingress LSP, gRPC Streaming
Feature Introduced
Bypass LSP
Feature Introduced
ACX6360 Junos 19.2R1
RSVP bypass LSP originating at transit node
30
Table 3: LSP Support by Platform (Continued)
Platform Ingress LSP, UDP
Feature Introduced
Ingress LSP, gRPC Streaming
Feature Introduced
Bypass LSP
Feature Introduced
MX80/MX104 Junos OS Release 15.1F6
Junos OS Release 16.1R3
Junos OS Release 17.2R1
Junos OS Release 17.4R1
Junos OS Release 17.2X75D50+
MX Series with MPC Junos OS Release 15.1F6 Junos OS Release 16.1R4
Junos OS Release 17.2R1
Junos OS Release 17.4R1
Junos OS Release 17.2X75D50+
PTX5000 with FPC3 Junos OS Release 18.2R1 Junos OS Release 17.4R1
PTX3000 with FPC3 Junos OS Release 15.1F6
Junos OS Release 16.1R3
Junos OS Release 17.2R1
Junos OS Release 16.1R4
Junos OS Release 17.2R1
Junos OS Release 18.2R1
Junos OS Release 17.4R1
Junos OS Release 17.2X75D50+
PTX Series with FPC1/2 Junos OS Release 15.1F6
Junos OS Release 16.1R3
Junos OS Release 17.2R1
Junos OS Release 16.1R4
Junos OS Release 17.2R1
Junos OS Release 18.2R1
Junos OS Release 17.4R1
Junos OS Release 17.2X75D50+
PTX1000 Junos OS Release 16.1R3 Junos OS Release 16.1R4
Junos OS Release 17.2R1
Junos OS Release 17.4R1
Junos OS Release 17.2X75D50+
PTX10000 Junos OS Release 17.3R1 Junos OS Release 17.3R1 Junos OS Release 17.4R1
Junos OS Release 17.2X75D50+
PTX10001-20C Junos OS Release 19.1R1
RSVP bypass LSP originating at transit node
PTX10002 Junos OS Release 19.1R1 Junos OS Release 19.1R1
31
Table 3: LSP Support by Platform (Continued)
Platform Ingress LSP, UDP
Feature Introduced
Ingress LSP, gRPC Streaming
Feature Introduced
Bypass LSP
Feature Introduced
VMX Junos OS Release 17.3R1 Junos OS Release 17.3R1 Junos OS Release 17.4R1
Junos OS Release 17.2X75D50+
MX150 Junos OS Release 17.4R1 Junos OS Release 17.4R1
EX4600 Junos OS Release 18.4R1
EX4650 Junos OS Release 18.3R1 Junos OS Release 18.3R1
EX9200 Junos OS Release 17.3R1
QFX10000
QFX5200 Junos OS Release 17.2R1 Junos OS Release 17.2R1
QFX10002 Junos OS Release 19.1R1 Junos OS Release 19.1R1
QFX5100 Junos OS Release 18.2R1 Junos OS Release 18.2R1
QFX5110 Junos OS Release 18.2R1 Junos OS Release 18.2R1
QFX5120-48Y Junos OS Release 18.3R1 Junos OS Release 18.3R1
QFX5200 Junos OS Release 18.2R1 Junos OS Release 18.2R1
32
Dynamic Tunnel Statistics Support
Starting with Junos OS Release 17.4R1, you can export counter statistics for Packet Forwarding Enginedynamic tunnels to an outside collector using either native (UDP) or OpenConfig telemetry sensorsthrough JTI.
The statistics are used to report various network element performance metrics in a scalable and efficientway, providing visibility into Packet Forwarding Engine errors and drops.
A timestamp indicating when the counters were last reset is included with all the exported data to allowcollectors to determine if and when a reset event happened; for example, if the P acket ForwardingEngine hardware restarted.
Exported statistics are similar to the output of the operational mode command show nhdb hw dynamic-ip-tunnels.
To provision statistics export through gRPC, use the telemetrySubcribe RPC to create a subscription andspecify telemetry parameters. Include the resource path /junos/services/ip-tunnel[name='tunnel-name']/usage/counters[name='counter-name']/ in the subscription.
Streaming telemetry data through gRPC also requires the OpenConfig for Junos OS module. Starting inJunos OS Release 18.3R1, OpenConfig and Network Agent packages are bundled into the Junos OSimage by default. Both packages support JTI.
To configure export of statistics through UDP, include the sensor /junos/services/ip-tunnel/usage/ in thesensor (Junos Telemetry Interface) configuration statement at the [edit services analytics] hierarchy level.All parameters for UDP sensors are configured at that hierarchy level. MX80 and MX104 routerssupport only UDP streaming. They do not support gRPC.
FPC and Optics Support
Starting in Junos OS Release 19.2R1, JTI supports streaming of Flexible PIC Concentrator (FPC) andoptics statistics for the MX Series using Remote Procedure Calls (gRPC). gRPC is a protocol forconfiguration and retrieval of state information. Support includes the addition of a new process(SensorD daemon) to export telemetry data for integration with AFTTelementry and LibTelemetrylibraries in the OpenConfig model called AFT platform.
The following base resource paths are supported:
• /junos/system/linecard/environment/
• /junos/system/linecard/optics/
33
To provision the sensor to export data through gRPC, use the telemetrySubcribe RPC to specifytelemetry parameters. Streaming telemetry data through gRPC also requires the OpenConfig for JunosOS module. Starting in Junos OS Release 18.3R1, OpenConfig and Network Agent packages are bundledinto the Junos OS image by default. Both packages support JTI.
JTI Broadband Edge Statistics Support for Junos Fusion on MX Series
Starting in Junos OS Release 19.2R1, subscriber-based telemetry streaming is enabled when an MXrouter is configured for Broadband Network Gateway (BNG) and Junos Fusion where subscribers areconnected through Junos Fusion Satellite devices. You can use remote procedure calls (gRPC) to exportbroadband edge (BBE) telemetry statistics to external collectors.
You can stream all BBE resource paths except for the following:
• /junos/system/subscriber-management/access-network/ancp
• /junos/system/subscriber-management/client-protocols/l2tp
• /junos/system/subscriber-management/infra/network/l2tp/
To stream BBE statistics, include a resource path starting with /junos/system/subscriber-management/in your gRPC subscription.
To provision the sensor to export data through gRPC, use the telemetrySubscribe RPC to specify telemetryparameters.
CPU and NPU Sensor Support for MX Series Routers with MPC10E-15C-MRATE Line Cards
Junos OS Release 19.3R1 supports CPU and network processing unit (NPU) sensors on MX Seriesrouters with MPC10E-10C-MRATE and MPC10E-15C-MRATE line cards. JTI enables the export ofstatistics from these sensors to outside collectors at configurable intervals using gRPC services.
Unlike the Junos kernel implementation for the CPU and NPU sensors in previous Junos releases, thisfeature uses the OpenConfig AFT model. Because of this, there is a difference in the resource path andkey-value (kv) pair output compared to the Junos kernel output.
Use the following resource path to export statistics:
/junos/system/linecard/cpu/memory/
/junos/system/linecard/npu/memory/
34
/junos/system/linecard/npu/utilization/
To provision the sensor to export data through gRPC services, use the telemetrySubcribe RPC to specifytelemetry parameters. Streaming telemetry data through gRPC also requires the OpenConfig for JunosOS module. Starting in Junos OS Release 18.3R1, OpenConfig and Network Agent packages are bundledinto the Junos OS image by default. Both packages support JTI.
For more information about gRPC resource paths, see Guidelines for gRPC Sensors (Junos TelemetryInterface).
Interface Express Sensor
The interface express sensor is supported by JTI to export interface operational UP and DOWN status at auser-configurable rate. This sensor leverages statistics out of the physical interface sensor, providingfaster and more frequent operational status statistics. Only the physical interfaces’ operational statusfrom the Flexible PIC Concentrator (FPC) is collected and reported. Statistics from the Routing Engineinterface are not reported.
You can use the sensor to export statistics either through UDP (native) export or through gRPC services.
For either export method, include the following resource path:
• /junos/system/linecard/intf-exp/
Junos OS Release 18.1R1 supports interface express sensor for PTX1000, PTX3000, PTX5000, andPTX10000 routers.
Junos OS Release 19.3R1 supports interface express sensor for MX960, MX2010, and MX2020 routers.
For more information about gRPC resource paths, see Guidelines for gRPC and gNMI Sensors (JunosTelemetry Interface).
Standby Routing Engine Sensors for Subscribers
JTI supports streaming standby Routing Engine statistics using gRPC services. This feature is supportedon both single chassis and virtual chassis unless otherwise indicated. Use this feature to better track thestate of software components running on a standby Routing Engine. Statistics exported to an outsidecollector through the following sensors (primarily under subscriber management) provide a morecomplete view of the system health and resiliency state:
35
• Chassis role (backup or primary) sensor /junos/system/subscriber-management/chassis and /junos/system/subscriber-management/chassis[chassis-index=chassis-index] (for specifying an index for anMX Series Virtual Chassis)
• Routing Engine status and GRES notification sensor /junos/system/subscriber-management/chassis/routing-engines/routing-engine and /junos/system/subscriber-management/chassis/routing-engines/routing-engine[re-index=RoutingEngineIndex] (to specify an index number for aspecific Routing Engine)
• Subscriber management process sensor /junos/system/subscriber-management/chassis/routing-engines/process-status/subscriber-management-processes/subscriber-management-process and /junos/system/subscriber-management/chassis/routing-engines/process-status/subscriber-management-processes/subscriber-management-process[pid=ProcessIdentifier] (to specify a PIDfor a specific process)
• Per Routing Engine DHCP binding statistics for server or relay sensor /junos/system/subscriber-management/chassis/routing-engines/routing-engine/dhcp-bindings/dhcp-element[dhcp-type-name=RelayOrServer/v4] and /junos/system/subscriber-management/chassis/routing-engines/routing-engine/dhcp-bindings/dhcp-element[dhcp-type-name=RelayOrServer/v6]
• Virtual Chassis port counter sensor /junos/system/subscriber-management/chassis/virtual-chassis-ports/virtual-chassis-port and /junos/system/subscriber-management/chassis/virtual-chassis-ports/virtual-chassis-port[vcp-interface-name=vcp-interface-port-string] (to specify the interfacename). This resource path is only supported on a virtual chassis.
Junos OS Release 20.2R1 supports standby Routing Engine sensors for MX480, MX960, MX10003,MX2010, and MX2020 routers.
For more information about gRPC and gNMI resource paths, see Guidelines for gRPC and gNMI Sensors(Junos Telemetry Interface).
Diameter Application Protocol and Diameter Peer Sensors forSubscribers
JTI supports streaming statistics for subscribers for the diameter application protocols Network AccessServer Application (NASREQ), policy and charging rules function (PCRF), and Online Charging System(OCS). There are also new diameter peer sensors that provide response time measurements formessages exchanged between an MX router and the peer for each of the diameter applications.Statistics are exported using JTI and the Juniper AAA Model, which covers telemetry export using gRPC,gNMI, or Juniper proprietary RPC or UDP.
To stream diameter application statistics, include the resource paths:
36
• For NASREQ statistics, /junos/system/subscriber-management/aaa/diameter/clients/nasreq
• For PCRF statistics, /junos/system/subscriber-management/aaa/diameter/clients/gx
• For OCS statistics, /junos/system/subscriber-management/aaa/diameter/clients/gy
To stream response time measurements for the diameter applications, include the resource paths in asubscription or using the sensor configuration statement:
• For NASREQ measurements, /junos/system/subscriber-management/aaa/diameter/peers/peer[peer_address=’peer-address’]/nasreq/response-time
• For PCRF measurements, /junos/system/subscriber-management/aaa/diameter/peers/peer[peer_address=’peer-address’]/gx/response-time
• For OCS measurements, /junos/system/subscriber-management/aaa/diameter/peers/peer[peer_address=’peer-address’]/gy/response-time
To enable these statistics for an MX Series router for native (UDP) export, include the sensors statementat the [edit services analytics] hierarchy level.
To provision the sensor to export data through gNMI, use the Subscribe RPC defined in the gnmi.prototo specify request parameters.
To provision the sensor to export data through gRPC, use the telemetrySubscribe RPC to specify telemetryparameters. Streaming telemetry data through gRPC also requires the OpenConfig for Junos OS module.Starting in Junos OS Release 18.3R1, OpenConfig and Network Agent packages are bundled into theJunos OS image by default. Both packages support JTI.
Junos OS Release 19.3R1 supports diameter application protocol sensors for MX5, MX10, MX40,MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, andMX100016 routers.
For more information about gRPC and gNMI resource paths, see Guidelines for gRPC and gNMI Sensors(Junos Telemetry Interface).
Interface Burst Monitoring
Junos OS Evolved Release 19.3R1supports interface burst monitoring on Junos telemetry interface (JTI)to monitor physical interfaces for bursts on QFX5220-128C and QFX5220-32CD switches. Useinterface burst monitoring to help troubleshoot problems, make decisions, and adjust resources asneeded.
The sampling is done in the millisecond granularity during the export interval (window). The exportinterval is configured in the sensor with the subscription from the collector. When the sensor is installed,
37
a timer is started in the Packet Forwarding Engine to poll the hardware in 30-100ms intervals. Rates inthe first export batch will be 0.
The peak byte is the average of the number of bytes seen in a sampling interval. For bursts lasting lessthan the sampling interval, the peak byte is averaged out over the interval. Exported statistics alsoinclude the time peak bytes are detected, as well as the direction (transmit or receive). The maximumbyte rate detected during the export interval among all the samples is considered as the burst. If thereare multiple bursts of the same number of bytes rate in the interval, then the first occurring burst isconsidered as the maximum burst and the timestamp of that burst is considered as the burst timestamp.
Data for all physical interfaces that are UP is exported. Aggregate interfaces are not supported.
You can export interface burst statistics from the Juniper device to an outside collector by including thesensor /junos/system/linecard/bmon-sw/ in a subscription using remote procedure call (gRPC) services.Only one collector is supported with this sensor.
To provision the sensor to export data through gRPC services, use the telemetrySubcribe RPC to specifytelemetry parameters. Streaming telemetry data through gRPC also requires the OpenConfig for JunosOS module.
NOTE: This feature does not detect microbursts.
Transceiver Diagnostics
Junos OS Release 19.4R1 supports transciever diagnostic sensors for ON_CHANGE and streamingstatistics using JTI and gRPC services or gNMI services on MX960, MX2010, MX2020, PTX1000,PTX5000, and the PTX10000 line of routers. Use transceiver diagnostics to help troubleshoot problems,make decisions, and adjust resources as needed.
This feature supports OpenConfig transceiver model openconfig-platform-transceiver.yang 0.5.0.
Use the base resource path /components/component/transceiver/ in a gRPC or gNMI subscription toexport statistics from the Juniper device to an outside collector.
Fields that change continuously, such as temperature, input power, and output power, and laser biascurrent are not supported for ON_CHANGE.
38
Physical Ethernet Interface Sensor
Junos OS Release 19.4R1 supports physical Ethernet interface statistics for ON_CHANGE andstreaming statistics using JTI and gRPC services or gNMI services on MX960, MX2020, PTX1000, andPTX5000 routers.
This feature supports OpenConfig model openconfig-if-ethernet.yang (physical interface level) version2.6.2 (no configuration).
Use the base resource path /interfaces/interface/ethernet/state/ in a gRPC or gNMI subscription toexport statistics from the Juniper device to an outside collector.
VLAN Sensors
Junos OS Release 19.4R1 supports streaming VLAN statistics for ON_CHANGE using JTI and gRPCservices on EX4650 and QFX5120 switches.
This feature supports OpenConfig model openconfig-vlan.yang configuration version 1.0.2.
Use the base resource path /vlans/ in a gRPC subscription to export statistics from the Juniper device toan outside collector.
Other end points you can use in a subscription include:
• /vlans/vlan/state/name
• /vlans/vlan/state/vlan-id
• /vlans/vlan/members/
• /vlans/vlan/members/member/interface-ref/state/interface/
• /vlans/vlan/members/member/interface-ref/state/interface/switched-vlan/state/interface-mode
• /vlans/vlan/members/member/interface-ref/state/interface/switched-vlan/state/native-vlan
• /vlans/vlan/members/member/interface-ref/state/interface/switched-vlan/state/access-vlan
• /vlans/vlan/members/member/interface-ref/state/interface/switched-vlan/state/trunk-vlan
• /vlans/vlan/members/member/interface-ref/state/interface/vlan/state/vlan-id
39
Release History Table
Release Description
20.4R1Evolved
Starting in Junos OS Evolved Release 20.4R1, INITIAL_SYNC statistics from Packet ForwardingEngine sensors using gNMI services on QFX5130-32CD switches is supported.
20.2R1 Starting with Junos OS Evolved Release 20.2R1, gRPC service for streaming NDP statistics issupported on PTX10001 routers.
20.2R1 Starting with Junos OS Release 20.2R1, gRPC service for streaming Packet forwarding Engine andRouting Engine statistics is supported on EX2300, EX2300-MP, and EX3400 switches.
20.2R1 Starting with Junos OS Release 20.2R1, gRPC service for streaming BGP routing information base(RIB) and BGP peer statistics is supported on any platform family that supports containerizedrouting protocol process (cRPD). cRPD is Juniper’s routing protocol process (rpd) decoupled fromJunos OS and packaged as a Docker container to run in Linux-based environments.
20.2R1 Starting with Junos OS Release 20.2R1, ON_CHANGE BGP peer statistics export using gRPCservices and gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000,PTX5000, PTX10000 routers and QFX5100 and QFX5200 switches.
20.2R1 Starting with Junos OS Release 20.2R1, streaming BGP global, peer and perr groups statistics usinggRPC services is supported on EX2300, EX3400, EX4300, EX4600, and EX9200 switches.
20.2R1 Starting with Junos OS Release 20.2R1, streaming revenue interface statistics through PacketForwarding Engine sensors and pseudo interface statistics through Routing Engine sensors usinggRPC services and gNMI services is supported on SRX5400, SRX5600, and SRX5800 ServicesGateways..
20.2R1 Starting with Junos OS Release 20.2R1, streaming revenue interface statistics through PacketForwarding Engine sensors and pseudo interface statistics through Routing Engine sensors usinggRPC services and gNMI services is supported on SRX5400, SRX5600, and SRX5800 ServicesGateways.
20.2R1 Starting with Junos OS Release 20.2R1 sensors to stream standby Routing Engine statistics aresupported on MX480, MX960, MX10003, MX2010, and MX2020 routers.
20.2R1 Starting with Junos OS Release 20.2R1 sensors to stream EVPN statistics using gRPC services aresupported with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002,QFX10008, and QFX10016 switches.
40
20.2R1 Starting with Junos OS Release 20.2R1, TARGET_DEFINED subscription mode with gRPC NetworkManagement Interface (gNMI) services is supported for JTI on MX5, MX10, MX40, MX80, MX104,MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008,and MX10016 routers.
20.2R1 Starting in Junos OS Release 20.2R1, INITIAL_SYNC statistics from Packet Forwarding Enginesensors using gNMI services on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000routers, PTX10000 line of routers, and QFX5100 and QFX5200 switches is supported.
20.2R1 Junos OS Release 20.2R1 supports standby Routing Engine sensors for MX480, MX960,MX10003, MX2010, and MX2020 routers.
20.1R1 Starting with Junos Release 20.R1, gNMI service for streaming telemetry sensors for PacketForwarding Engine statistics is supported on MX2K-MPC11E line cards on MX2010 and MX2020routers.
20.1R1 Starting with Junos OS Release 20.1R1, gRPC services version v1.18.0 is supported with JTI. Thisversion includes important enhancements for gRPC. In earlier Junos OS releases, gRPC versionv1.3.0 is supported with JTI.
19.4R1Evolved
Starting with Junos Release 19.4R1, gRPC service for streaming Packet Forwarding Engine andRouting Engine statistics is supported on EX4300-MP switches.
19.4R1 Junos OS Release 19.4R1 supports transciever diagnostic sensors for ON_CHANGE and streamingstatistics using JTI and gRPC services or gNMI services on MX960, MX2010, MX2020, PTX1000,PTX5000, and the PTX10000 line of routers.
19.4R1 Junos OS Release 19.4R1 supports physical Ethernet interface statistics for ON_CHANGE andstreaming statistics using JTI and gRPC services or gNMI services on MX960, MX2020, PTX1000,and PTX5000 routers.
19.4R1 Junos OS Release 19.4R1 supports streaming VLAN statistics for ON_CHANGE using JTI andgRPC services on EX4650 and QFX5120 switches.
19.3R1-Evolved
Starting with Junos OS Evolved Release 19.3R1, gRPC service for exporting statistics is supportedon QFX5220-128C and QFX5220-32CD switches.
19.3R1-Evolved
Junos OS Evolved Release 19.3R1supports interface burst monitoring on Junos telemetry interface(JTI) to monitor physical interfaces for bursts on QFX5220-128C and QFX5220-32CD switches.
19.3R1 Starting with Junos OS Release 19.3R1, gRPC service for exporting statistics is supported on MXSeries routers hosting MPC10E-10C-MRATE and MPC10E-15C-MRATE line cards.
41
19.3R1 Junos OS Release 19.3R1 supports CPU and network processing unit (NPU) sensors on MX Seriesrouters with MPC10E-10C-MRATE and MPC10E-15C-MRATE line cards.
19.3R1 Junos OS Release 19.3R1 supports interface express sensor for MX960, MX2010, and MX2020routers.
19.3R1 Junos OS Release 19.3R1 supports diameter application protocol sensors for MX5, MX10, MX40,MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008,and MX100016 routers.
19.2R1 Starting with Junos OS Release 19.2R1, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600,SRX5800, and vSRX Series Services Gateways.
19.2R1 Starting with Junos OS Release 19.2R1, gNMI services for streaming Packet Forwarding Enginestatistics is supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 andPTX10000 routers, and QFX5100 and QFX5200 switches.
19.2R1 Starting with Junos OS Release 19.2R1, gNMI services for streaming statistics is supported onQFX5100, QFX5110, QFX5120, QFX5200 and QFX5210 switches.
19.2R1 Starting in Junos OS Release 19.2R1, JTI supports streaming of Flexible PIC Concentrator (FPC)and optics statistics for the MX Series using Remote Procedure Calls (gRPC).
19.2R1 Starting in Junos OS Release 19.2R1, subscriber-based telemetry streaming is enabled when anMX router is configured for Broadband Network Gateway (BNG) and Junos Fusion wheresubscribers are connected through Junos Fusion Satellite devices.
19.1R1 EVO Starting in Junos OS Evolved Release 19.1R1, OpenConfig (OC) and Junos telemetry interface (JTI)are supported. Both gRPC APIs and the customer-facing CLI remain the same as for the Junos OS.As was standard for Junos OS, Network Agent (NA) and OC packages are part of the Junos OSEvolved image.
19.1R1 Starting with Junos OS Release 19.1R1, MX Series routers operating with MS-MIC and MS-MPC,QFX10002 switches, and PTX10002 routers are also supported.
19.1R1 Starting with Junos OS Evolved 19.1R1, Packet Forwarding Engine sensors on PTX10003 routersare also supported.
18.4R1 Starting with Junos OS Release 18.4R1, MX480, MX960, MX2010, MX2020, MX2008 and MX-ELM routers are also supported.
42
18.3R1 Starting with Junos OS Release 18.3R1, ON_CHANGE streaming of LLDP telemetry sensorinformation is supported through gRPC for MX Series and PTX Series routers.
18.3R1 Starting with Junos OS Release 18.3R1, QFX5120-AY and EX4650 switches are also supported.
18.3R1 Starting with Junos OS Release 18.4R1, EX4600 switches are also supported.
18.3R1 Starting in Junos OS Release 18.3R1, OpenConfig and Network Agent packages are bundled intothe Junos OS image by default. Both packages support JTI.
18.3R1 Starting in Junos OS Release 18.3R1, OpenConfig and Network Agent packages are bundled intothe Junos OS image by default. Both packages support JTI.
18.2R1 Starting in Junos OS Release 18.2R1, when an external streaming server, or collector, provisionssensors to export data through gRPC on devices running Junos OS, the sensor configuration iscommitted to the junos-analytics instance of the ephemeral configuration database, and theconfiguration can be viewed by using the show ephemeral-configuration instance junos-analyticsoperational command.
18.1R1 Starting with Junos OS Release 18.1R1, OpenConfig support through Remote Procedure Calls(gRPC) and JTI is extended to support client streaming and bidirectional streaming of telemetrysensor information on MX Series and PTX Series routers.
18.1R1 Starting with Junos OS Release 18.3R1, OpenConfig support through gRPC and JTI providescontinuous statistics streaming via the same sensor irrespective of the route that is active (BGP orstatic) for a given Segment Routing Traffic Engineering (SR-TE) policy.
18.1R1 Junos OS Release 18.1R1 supports interface express sensor for PTX1000, PTX3000, PTX5000,and PTX10000 routers.
17.4R1 Starting with Junos OS Release 17.4R1, MX2008 routers are supported.
17.4R1 Starting with Junos OS Release 17.4R1, you can export Packet Forwarding Engine traffic statisticsthrough the Junos telemetry interface for MX Series and PTX Series routers. Both UDP and gRPCare supported.
17.4R1 With bypass support added to this feature in Junos OS Release 17.4R1, this subscription nowstreams both ingress LSP and bypass LSP statistics to a collector.
17.4R1 Starting with Junos OS Release 17.4R1, you can export counter statistics for Packet ForwardingEngine dynamic tunnels to an outside collector using either native (UDP) or OpenConfig telemetrysensors through JTI.
43
17.3R1 Starting with Junos OS Release 17.3R1, Junos telemetry interface is supported on the RoutingControl and Board (RCB) on PTX3000 routers, QFX5110 switches, and EX4600 and EX9200switches.
17.2R1 Starting with Junos OS Release 17.2R1, OpenConfig and gRPC are also supported on QFX10000switches, QFX5200 switches, and PTX1000 routers.
16.1R3 Starting in Junos OS Release 16.1R3, you can use a set of remote procedure call (RPC) interfaces toconfigure the Junos telemetry interface and stream telemetry data using the gRPC framework.
16.1R3 OpenConfig for Junos OS and gRPC are supported only on MPCs on MX Series and on PTX Seriesrouters starting with Junos OS Release 16.1R3.
15.1F6 Initial support of this feature in Junos OS Release 15.1F6 supported ingress LSPs only when asubscription was made to /junos/services/label-switched-path/usage/.
RELATED DOCUMENTATION
Installing the Network Agent Package (Junos Telemetry Interface)
Release Information for Junos OS with Upgraded FreeBSD
Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface)
statistics
telemetry
Installing the Network Agent Package (JunosTelemetry Interface)
Before you begin:
• Install Junos OS Release 16.1R3 or later.
• Install the OpenConfig for Junos OS module. Using a Web browser, navigate to the All JunosPlatforms software download URL on the Juniper Networks webpage: https://www.juniper.net/support/downloads/. From the Network Management tab, scroll down to select OpenConfig. Selectthe Software tab. Select the OpenConfig Package (Junos with upgraded FreeBSD). For moreinformation, see "Installing the OpenConfig Package" on page 12.
44
• Install Secure Sockets Layer (SSL) certificates of authentication on your Juniper Networks device.
NOTE: Only server-based SSL authentication is supported. Client-based authentication is notsupported.
Starting with Junos OS Release 16.1R3, the Junos Network Agent software package provides aframework to support OpenConfig and gRPC for the Junos Telemetry Interface on MX Series routersand PTX5000 routers. The Network Agent package functions as a gRPC server that terminates theOpenConfig remote procedure call (RPC) interfaces and streams the telemetry data according to theOpenConfig specification. The Junos Network Agent package, which runs on the Routing Engine,implements local statistics collection and reports data to active telemetry stream subscribers.
Starting with Junos OS Release 17.2R1, the Junos Network Agent Package is also supported onQFX10000 switches and QFX5200 switches.
Starting with Junos OS Release 17.3R1, the Junos Network Agent Package is supported on QFX5110switches and EX9200 switches.
Starting in Junos OS Release 18.3R1, the Junos OS image includes the Network Agent. You do not needto install Network Agent separately. This is true for Junos OS with upgraded FreeBSD and legacy JunosOS.
The Junos Network Agent is available as a separate package only for Junos OS with Upgraded FreeBSD.This package also includes the required YANG models. For other versions of Junos OS, Network Agentfunctionality is embedded in the software. For more information about Junos OS with UpgradedFreeBSD, see Release Information for Junos OS with Upgraded FreeBSD.
Network Agent for Junos OS software package has the following naming conventions:
• Package Name—This is Network-Agent.
• Architecture—This field indicates the CPU architecture of the platforms, such as x86.
• Application Binary Interface (ABI)—This field indicates the “word length” of the CPU architecture. Thealue is 32 for 32-bit architectures.
• Release—This field indicates the Junos OS release number, such as 16.1R3.16.
• Package release and spin number—This field indicates the package version and spin number, such asC1.1.
All Junos Network Agent packages are in tarred and gzipped (.tgz) format.
45
NOTE: Each version of the Network Agent package is supported on a single release of Junos OSonly. The Junos OS version supported is identified by the Junos OS release number included inthe Network Agent package name.
An example of a valid Network Agent package name is:
• network-agent-x86-32-16.1R4.12-C1.1.tgz
Use the 32-bit Network Agent package for both 32-bit and 64-bit versions of Junos OS or Junos OSEvolved.
To download and install the Network Agent package:
1. Using a Web browser, navigate to the All Junos Platforms software download URL on the JuniperNetworks webpage: https://www.juniper.net/support/downloads/.
2. Select the name of the Junos OS platform for the software that you want to download.
3. Select the release number (the number of the software version that you want to download) fromthe Release drop-down list to the right of the Download Software page.
4. Select the Software tab.
5. In the Tools section of the Software tab, select the Junos Network Agent package for the release.
6. Log in to the Juniper Networks authentication system using the username (generally your e-mailaddress) and password supplied by a Juniper Networks representative.
7. Download the software to a local host.
8. Copy the software to Juniper Networks device or to your internal software distribution site.
9. Install the new network-agent package on the device by issuing the request system software add package-name from the operational mode:
For example:
user@host > request system software add network-agent-x86-32-16.1R3.16-C1.0.tgz
NOTE: The command uses the validate option by default. This option validates the softwarepackage against the current configuration as a prerequisite to adding the software packageto ensure that the device reboots successfully. This is the default behavior when thesoftware package being added is a different release.
46
10. Issue the show version | grep na\ telemetry command to verify that the Network Agent package wassuccessfully installed.
user@host> show version | grep na\ telemetryJUNOS na telemetry[20161109.201405_builder_junos_161_r3]
For information about configuring gRPC services on your Juniper Networks device, see gRPC Servicesfor Junos Telemetry Interface.
Release History Table
Release Description
18.3R1 Starting in Junos OS Release 18.3R1, the Junos OS image includes the Network Agent.
17.3R1 Starting with Junos OS Release 17.3R1, the Junos Network Agent Package is supported on QFX5110switches and EX9200 switches.
17.2R1 Starting with Junos OS Release 17.2R1, the Junos Network Agent Package is also supported onQFX10000 switches and QFX5200 switches.
16.1R3 Starting with Junos OS Release 16.1R3, the Junos Network Agent software package provides aframework to support OpenConfig and gRPC for the Junos Telemetry Interface on MX Series routersand PTX5000 routers.
RELATED DOCUMENTATION
Understanding OpenConfig and gRPC on Junos Telemetry Interface
gRPC Services for Junos Telemetry Interface
IN THIS SECTION
Configuring gRPC for the Junos Telemetry Interface | 48
Configuring Bidirectional Authentication for gRPC for Junos Telemetry Interface | 50
47
Configuring gRPC for the Junos Telemetry Interface
Starting with Junos OS Release 16.1R3 on MX Series routers and PTX3000 and PTX5000 routers, youcan stream telemetry data for various network elements through gRPC, an open source framework forhandling remote procedure calls based on TCP. The Junos Telemetry Interface relies on a so-called pushmodel to deliver data asynchronously, which eliminates polling. For all Juniper devices that run a versionof Junos OS with upgraded FreeBSD kernel, you must install the Junos Network Agent softwarepackage, which provides the interfaces to manage gRPC subscriptions. For Juniper Network devices thatrun other all other versions of the Junos OS, this functionality is embedded in the Junos OS software.For more information about installing the Junos Network Agent package, see Installing the NetworkAgent Package.
The Junos Telemetry Interface and gRPC streaming are supported on QFX10000 and QFX5200switches, and PTX1000 routers starting with Junos OS Release 17.2R1.
The Junos Telemetry Interface and gRPC streaming are supported on QFX5110, EX4600, and EX9200switches starting with Junos OS Release 17.3R1.
Before you begin:
• Install Junos OS Release 16.1R3 or later on your Juniper Networks device.
• If your Juniper Networks device is running a version of Junos OS with an upgraded FreeBSD kernel,install the Junos Network Agent software package.
• Install the OpenConfig for Junos module. For more information see, "Installing the OpenConfigPackage" on page 12.
To configure your system for gRPC services:
1. Specify the API connection setting either based on Secure Socket Layer (SSL) technology.
For example, to set the API connection based on a SSL:
[edit system services]user@host# set extension-service request-response grpc ssl
For an SSL-based connection, you must specify a local-certificate name and you can rely on thedefault IP address (::) to enable Junos to “listen” for all IPv4 and IPv6 addresses on incomingconnections. If you would rather specify an IP address, follow stp b. below.
48
a. Specify a local certificate-name. The certificate can be any user-defined value from the certificateconfiguration (not shown here). The certificate name should used in thisexample is jsd_certificate:
[edit system services extension-service request-response grpc]user@host# set ssl local-certificate jsd_certificate
NOTE: Enter the name of a certificate you have configured with the local certificate-namestatement at the [edit security certificates] hierarchy level.
b. (Optional) Specify an IP address to listen to for incoming connections. for example, 192.0.2.0:
[edit system services extension-service request-response grpc]user@host# set ssl ip-address 192.0.2.0
NOTE: If you do not specify an IP address, the default address of :: is used to listen forincoming connections.
2. Specify port 32767 for accepting incoming connections through gRPC.
NOTE: Port 32767 is the required port for gRPC streaming for both unsecured and SSL-basedconnections.
[edit system services extension-service request-response grpc]user@host# set ssl port 32767
SEE ALSO
Understanding OpenConfig and gRPC on Junos Telemetry Interface
Importing SSL Certificates for Junos XML Protocol Support
49
Configuring Bidirectional Authentication for gRPC for Junos TelemetryInterface
Starting with Junos OS Release 17.4R1, you can configure bidirectional authentication for gRPC sessionsused to stream telemetry data. Previously, only authentication of the server, that is, Juniper device, wassupported. Now the external client, that is management station that collects data, can also beauthenticated using SSL certificates. The JET service process (jsd), which supports applicationinteraction with Junos OS, uses the credentials provided by the external client to authenticate the clientand authorize a connection.
Before you begin:
• If your Juniper device is running a version of Junos OS with an upgraded FreeBSD kernel, install theJunos Network Agent software package.
• Install the OpenConfig for Junos module. For more information see, "Installing the OpenConfigPackage" on page 12.
• Configure the gRPC server. For more information, see Configuring gRPC for the Junos TelemetryInterface.
To configure authentication for the external client, that is, management station that collects telemetrydata streamed from the Juniper device:
1. Enable bidirectional authentication and specify the requirements for a client certificate.
For example, to specify the strongest authentication, which requires a certificate and its validation:
[edit system services extention-service request-response grpc ssl]user@host# set mutual-authentication client-certificate-request require-certificate-and-verify
NOTE: The default is no-certificate. The other options are: request-certificate, request-certificate-and-verify, require-certificate, require-certificate-and-verfiy.We recommend that you use no-certificate option in a test environment only.
2. Specify the certificate authority.
NOTE: For the certificate authority, specify a certificate-authority profile you have configuredat the [edit security pki ca-profile] hierarchy level. This profile is used to validate thecertificate provided by the client.
50
A digital certificate provides a way of authenticating users through a trusted third-party calleda certificate authority (CA). The CA validates the identity of a certificate holder and “signs”the certificate to attest that it has not been forged or altered. For more information, seeDigital Certificates Overview and Example: Requesting a CA Digital Certificate.
For example, to specify a certificate-authority profile named jsd_certificate:
[edit system services extention-service request-response grpc ssl mutual-authentication]user@host# set certificate-authority jsd_certificate
3. Verify that an external client can successfully connect with the Juniper device through the jsdprocess and invoke OpenConfig RPCs.
The external client passes username and password credentials as part of metadata in each RPC. TheRPC is allowed if valid credentials are used. Otherwise an error message is returned.
SEE ALSO
ssl
Release History Table
Release Description
17.4R1 Starting with Junos OS Release 17.4R1, you can configure bidirectional authentication for gRPC sessionsused to stream telemetry data.
17.3R1 The Junos Telemetry Interface and gRPC streaming are supported on QFX5110, EX4600, and EX9200switches starting with Junos OS Release 17.3R1.
17.2R1 The Junos Telemetry Interface and gRPC streaming are supported on QFX10000 and QFX5200switches, and PTX1000 routers starting with Junos OS Release 17.2R1.
16.1R3 Starting with Junos OS Release 16.1R3 on MX Series routers and PTX3000 and PTX5000 routers, youcan stream telemetry data for various network elements through gRPC, an open source framework forhandling remote procedure calls based on TCP.
51
Guidelines for gRPC and gNMI Sensors (JunosTelemetry Interface)
IN THIS SECTION
Supported gRPC and gNMI Sensors | 55
Starting with Junos OS Release 16.1R3, the Junos Telemetry Interface supports gRPC remote procedurecalls (gRPC) to provision sensors and to subscribe to and receive telemetry data on MX Series routersand PTX3000 and PTX5000 routers.
Starting with JunosOS Release 17.2R1, QFX10002, QFX10008, and QFX10016 switches, QFX5200switches, and PTX1000 and PTX10008 routers are also supported.
Starting with Junos OS Release 17.3R1, QFX5110 switches, EX4600, EX4600-VC, and EX9200 switchesand the Routing and Control Board (RCB) on PTX3000 routers are also supported.
Starting with Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensors are supported.
Starting with Junos OS Release 18.2R1, PTX10002 routers are also supported.
Starting with Junos OS Release 17.4R1, PTX10016 routers and virtual MX Series (vMX) routers are alsosupported.
Starting with Junos OS Release 18.1R1, QFX5210-64C switches and QFX5100 switches are alsosupported.
Starting with Junos OS Release 18.1R1, ON_CHANGE streaming of ARP, ND, and IP sensor informationassociated with interfaces is supported through gRPC for MX Series routers and PTX Series routers.
Starting with Junos OS Release 18.3R1, ON_CHANGE streaming of LLDP telemetry sensor informationis supported through gRPC for MX Series and PTX Series routers.
Starting with Junos OS Release 18.3R1, QFX5120-AY and EX4650 switches are also supported.
Starting with Junos OS Release 18.4R1, EX4600 switches are also supported.
Starting with Junos OS Release 18.4R1, MX480, MX960, MX2010, MX2020, MX2008 and MX-ELMrouters are also supported.
52
Starting in Junos OS Evolved Release 19.1R1, OpenConfig (OC) and Junos Telemetry Interface (JTI) aresupported. Both gRPC APIs and the customer-facing CLI remain the same as for the Junos OS. As wasstandard for Junos OS, Network Agent (NA) and OC packages are part of the Junos OS Evolved image.
Starting with Junos OS Evolved 19.1R1, Packet Forwarding Engine sensors on PTX10003 routers arealso supported.
Starting with Junos OS Release 19.2R1, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, SRX5800,and vSRX Series Services Gateways.are supported.
Starting with Junos OS Release 19.2R1, gNMI services for streaming Packet Forwarding Engine statisticsis supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 and PTX10000 routers, andQFX5100 and QFX5200 switches.
Starting with Junos OS Release 19.2R1, gNMI services for streaming statistics is supported onQFX5110, QFX5120, QFX5200 and QFX5210 switches.
Starting with Junos OS Release 19.3R1, gNMI services for streaming Packet Forwarding Engine statisticsis supported on MX240, MX480 and MX960 routers.
Starting with Junos OS Release 19.3R1, gNMI services for streaming and ON_CHANGE export ofRouting Engine statistics is supported on MX960, MX2010, MX2020, PTX5000, PTX1000, andPTX10000 routers.
Starting with Junos OS Release 19.3R1, gRPC service for exporting statistics is supported on MX Seriesrouters hosting MPC10E-10C-MRATE and MPC10E-15C-MRATE line cards. The resource paths /junos/system/linecard/cpu/memory/, /junos/system/linecard/npu/memory/, and /junos/system/linecard/npu/utilization/ can be updated to call out individual sensors (leaves) and their respectivepaths for better clarity.
Starting with Junos OS Evolved Release 19.3R1, gRPC service for exporting statistics is supported onQFX5220-128C and QFX5220-32CD switches.
Starting with Junos OS Release 19.4R1, gRPC service for streaming Packet Forwarding Engine andRouting Engine statistics is supported on EX4300-MP switches.
Starting with Junos Release 20.R1, gNMI service for streaming telemetry sensors for Packet ForwardingEngine statistics is supported on MX2K-MPC11E line cards on MX2010 and MX2020 routers.
Starting with Junos OS Evolved Release 20.2R1, gRPC service for streaming NDP statistics is supportedon PTX10001 routers.
Starting with Junos OS Release 20.2R1, gRPC service for streaming Packet forwarding Engine andRouting Engine statistics is supported on EX2300, EX2300-MP, and EX3400 switches.
Starting with Junos OS Release 20.2R1, gRPC service for streaming BGP routing information base (RIB)and BGP peer statistics is supported on any platform family that supports containerized routing protocol
53
process (cRPD). cRPD is Juniper’s routing protocol process (rpd) decoupled from Junos OS and packagedas a Docker container to run in Linux-based environments.
Starting with Junos OS Release 20.2R1, ON_CHANGE BGP peer statistics export using gRPC servicesand gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000,PTX10000 routers and QFX5100 and QFX5200 switches.
Starting with Junos OS Release 20.2R1, streaming BGP global, peer and perr groups statistics usinggRPC services is supported on EX2300, EX3400, EX4300, EX4600, and EX9200 switches.
Starting with Junos OS Release 20.2R1, streaming revenue interface statistics through PacketForwarding Engine sensors and pseudo interface statistics through Routing Engine sensors using gRPCservices and gNMI services is supported on SRX5400, SRX5600, and SRX5800 Services Gateways..
Starting with Junos OS Release 20.2R1, streaming revenue interface statistics through PacketForwarding Engine sensors and pseudo interface statistics through Routing Engine sensors using gRPCservices and gNMI services is supported on SRX5400, SRX5600, and SRX5800 Services Gateways.
Starting with Junos OS Release 20.2R1 sensors to stream standby Routing Engine statistics aresupported on MX480, MX960, MX10003, MX2010, and MX2020 routers.
Starting with Junos OS Release 20.2R1 sensors to stream EVPN statistics using gRPC services aresupported with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002, QFX10008,and QFX10016 switches.
Starting with Junos OS Release 20.2R1, gRPC service for exporting LDP and mLDP statistics issupported on MX Series routers.
Starting with Junos OS Release 20.3R1, gRPC service for exporting LDP and mLDP statistics issupported on MPC10E-10C-MRATE, MPC10E-15C-MRATE, and MX2K-MPC11E line cards.
The Telemetry Explorer tool is the best location to search for and view information about telemetrysensors.
For information that is not yet supported by Telemetry Explorer (mainly Packet Forwarding Enginesensors) please refer to Table 4 on page 55 and Table 5 on page 116.
To activate a sensor, use the corresponding resource path. Each resource path enables data streamingfor the system resource globally, that is, systemwide. You can also modify each resource path, such as tospecify a specific logical or physical interface. For example, to specify a specific interface, include thefollowing at the end of the path: [name='interface-name']/
54
Supported gRPC and gNMI Sensors
See Table 4 on page 55 for a description of supported gRPC and gNMI sensors and Table 5 on page116 for a description of supported broadband edge (BBE) gRPC sensors, including the subscription pathyou use to provision the sensors.
Starting with Junos OS Release 20.1R1, the on-device gRPC framework is upgraded to version v1.18.0and is applicable to both JET and JTI. This version includes important enhancements for gRPC. Earlierlegacy Junos OS platform versions (non-Occam) will continue to use version v1.3.0.
Starting with Junos OS Release 20.2R1, JTI supports MX routers with dual Routing Engines or MX SeriesVirtual Chassis on all Packet Forwarding Engine and Routing Engine sensors currently supported on MXSeries routers. The level of sensor support currently available for MX Series routers applies, whetherthrough streaming or ON_CHANGE statistics export, using UDP, remote procedure call (gRPC) servicesor gRPC Network Management Interface (gNMI) services. Additionally, JTI operational mode commandswill provide details for all Routing Engines and MX Series Virtual Chassis, too.
Table 4: gRPC Sensors
resource path Description
/interfaces/interface/state/forwarding-viable Packet Forwarding Engine sensor for non-viable aggregated interfacemember links. This feature does not support non-LAG link members
Starting in Junos OS Evolved Release 21.4R1, streaming statistics bymeans of gRPC and gNMI is supported on PTX10008 and PTX10016routers.
55
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/ike-security-associations/ike-security-association/routing-instance [name=’ routing-instance-name]
Sensor for Internet Key Exchange (IKE) security statistics.
When you configure a subscription request, use the reporting-interval parameter to configure the interval (in seconds) in whichstatistics are reported.
Starting with Junos OS Release 18.1R1, MX Series routers aresupported.
• remote-ip
• local-ip
• number-ipsec-sa-created
• number-ipsec-sa-deleted
• number-ipsec-sa-rekey
• exchange-type
• in-bytes
• in-packets
• out-bytes
• out-packets
• delete-payload-received
• delete-payload-transmitted
• dpd-request-payload-received
• dpd-request-payload-transmitted
• dpd-response-payload-received
• dpd-response-payload-transmitted
• dpd-response-payload-missed
• dpd-response-payload-maximum-delay
56
Table 4: gRPC Sensors (Continued)
resource path Description
• dpd-response-seq-payload-missed
• invalid-spi-notify-received
• invalid-spi-notify-transmitted
• routing-instance
/junos/kernel/tcpip/rtstock Sensor for kernel routing table socket (RTSOCK) information.
Starting with Junos OS Release 19.3R1, EX9200, EX9251, EX9253,MX240, MX480, MX960, MX2010, MX2020, vMX, PTX1000,PTX10008, PTX10016, PTX3000 with RE-PTX-X8-64G, andPTX5000 with RE-PTX-X8-64G are supported.
You can also add the following as the end path for /junos/kernel/rtsock/:
• total-error-cnt
• total-veto-cnt
/junos/npu/memory Starting with Junos OS Release 19.1R1, periodic streaming onQFX10002 switches and PTX10002 routers is supported.
/junos/services/health-monitor/config/ Sensor for the health monitoring configuraiton.
Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010and MX2020 routers, PTX1000 and PTX10000 routers, andQFX5100 and QFX5200 switches are supported on gRPC and gNMIservices.
/junos/services/health-monitor/data/ Sensor for health monitoring data.
Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010and MX2020 routers, PTX1000 and PTX10000 routers, andQFX5100 and QFX5200 switches are supported on gRPC and gNMIservices.
57
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/services/ip-tunnel[name='tunnel-name']/usage/counters[name='counter-name']/
Sensor for Packet Forwarding Engine dynamic tunnels statistics.
The statistics are used to report various network elementperformance metrics in a scalable and efficient way, providingvisibility into Packet Forwarding Engine errors and drops.
A timestamp indicating when the counters were last reset is includedwith all the exported data to allow collectors to determine if andwhen a reset event happened; for example, if the Packet ForwardingEngine hardware restarted.
Exported statistics are similar to the output of the operational modecommand show nhdb hw dynamic-ip-tunnels.
Starting with Junos OS Release 17.4R1, MX Series devices aresupported on gRPC services, with the exception of MX80 andMX104 routers. These routers support UDP export only for thissensor. To configure UDP export, include the sensor /junos/services/ip-tunnel/usage/ in the sensor (Junos Telemetry Interface)configuration statement at the [edit services analytics] hierarchylevel.
58
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/services/label-switched-path/usage/ Sensor for LSP statistics. On MX Series routers only, the followingare also supported: bidirectional LSPs for ultimate-hop popping(UHP).
Starting with Junos OS Release 17.2R1, QFX10000 switches andPTX1000 routers are also supported.
Starting with Junos OS Release 17.3R1, EX9200 switches are alsosupported.
Starting with Junos OS Release 17.4R1 on MX Series and PTX Seriesrouters only, statistics for bypass LSPs are also exported. Previously,only statistics for ingress LSPs were exported.
Starting with Junos OS Release 18.2R1, QFX5100, QFX5110, andQFX5200 switches are also supported.
Starting with Junos OS Release 18.3R1, QFX5120-48Y and EX4650switches are also supported.
Starting with Junos OS Release 18.4R1, EX4600 switches are alsosupported.
Starting with Junos OS Release 19.1R1, PTX10001-20C routerssupport RSVP bypass LSPs originating at the transit node
Starting with Junos OS Release 19.1R1, periodic streaming onQFX10002 switches and PTX10002 routers is supported.
Starting in Junos OS Evolved Release 19.1R1, PTX10003 routers aresupported.
Starting with Junos OS Release 19.2R1, ACX6360 routers aresupported.
Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010and MX2020 routers, PTX1000 and PTX10000 routers, andQFX5100 and QFX5200 switches are supported on gRPC and gNMIservices.
Supported on QFX5200 switches starting with Junos OS Release19.2R1 for streaming telemetry information using gNMI services.
Starting with Junos OS Evolved Release 19.4R1, periodic streamingusing gNMI services with PTX10003 routers is supported.
59
Table 4: gRPC Sensors (Continued)
resource path Description
Starting with Junos OS Evolved Release 20.2R1, periodic streamingusing gRPC services with PTX10001 routers is supported.
For bypass LSPs, the following are exported:
• Bypass LSP originating at the ingress router of the protected LSP.
• Bypass LSP originating at the transit router of the protected LSP.
• Bypass LSP protecting the transit LSP as well as the locallyoriginated LSP.
When the bypass LSP is active, traffic is exported both on the bypassLSP and the ingress (protected) LSP.
NOTE: When you enable a sensor for LSP statistics only, you mustalso configure the sensor-based-stats statement at the [editprotocols mpls] hierarchy level. MX Series routers should operate inenhanced mode. If not enabled by default, include either theenhanced-ip statement or the enhanced-ethernet statement at the [editchassis network-services] hierarchy level.
/junos/system/cmerror/configuration Sensor for error monitoring configuration.
Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 andMX2020 routers, PTX1000 and PTX10000 routers, and QFX5100and QFX5200 switches are supported on gRPC and gNMI services.
/junos/system/cmerror/counters Sensor for error monitoring counters.
Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 andMX2020 routers, PTX1000 and PTX10000 routers, and QFX5100and QFX5200 switches are supported on gRPC and gNMI services.
60
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/bmon-sw/ Sensor for interface burst monitoring.
Starting in Junos OS Evolved Release 19.3R1, QFX5220-128C andQFX5220-32CD switches are supported for streaming statistics ongRPC services.
You can also add the following to the end of the path to streamspecific statistics for interface burst monitoring:
• rx_bytes-Total number of bytes received during the exportinterval.
• tx_bytes-Total number of bytes transmitted during the exportinterval.
• start_ts-Start timestamp for the data collection window.
• rx_peak_byte_rate-Maximum bytes rate per millisecond receivedfrom all the sampling intervals in the export interval.
• rx_peak_ts-Timestamp of the first burst.
• tx_peak_byte_rate-Maximum bytes rate per millisecond,transmitted from all the sampling intervals in the export interval.
• tx_peak_byte_ts-Timestamp of the first transmit burst.
junos/system/linecard/npu/memory/ Sensor for network processing unit (NPU) memory.
Supported on EX4650, QFX5110, QFX5120-48Y, QFX5200, andQFX5210 switches starting with Junos OS Release 21.4R1 forexporting telemetry information using gRPC or gNMI services.
You can also add the following leaves to the end of the path tostream specific statistics:
• resource_name
• size
• allocated
• utilization
61
Table 4: gRPC Sensors (Continued)
resource path Description
junos/system/linecard/npu/memory/ Sensor for network processing unit (NPU) memory.
Supported on MX Series routers with MPC10E-10C-MRATE andMPC10E-15C-MRATE line cards starting with Junos OS Release19.3R1 for exporting telemetry information using gRPC services. Thisfeature provides a different level of exported statistics in comparisonto previous releases because it use the OpenConfig AFT model.
Supported on MX2010 and MX2020 routers with MX2K-MPC11Eline cards starting with Junos OS Release 20.1R1 for streamingtelemetry information using gRPC services.
You can also add the following to the end of the path to streamspecific statistics for NPU memory:
• mem-util-edmem-size
• mem-util-edmem-allocated
• mem-util-edmem-utilization
• mem-util-idmem-size
• mem-util-idmem-allocated
• mem-util-idmem-utilization
• mem-util-bulk-dmem-size
• mem-util-bulk-dmem-allocated
• mem-util-bulk-dmem-utilization
• mem-util-next-hop-edmem-size
• mem-util-next-hop-edmem-allocated
• mem-util-next-hop-edmem-utilization
• mem-util-next-hop-bulk-dmem-size
• mem-util-next-hop-bulk-dmem-allocated
• mem-util-next-hop-bulk-dmem-utilization
62
Table 4: gRPC Sensors (Continued)
resource path Description
• mem-util-next-hop-idmem-size
• mem-util-next-hop-idmem-allocated
• mem-util-next-hop-inline-services-free-count
• mem-util-next-hop-mobile:-timing-profile-bytes-allocated
• mem-util-next-hop-mobile:-timing-profile-allocation-count
• mem-util-next-hop-mobile:-timing-profile-free-count
• mem-util-next-hop-packet-reassembly-(rw)-bytes-allocated
• mem-util-next-hop-packet-reassembly-(rw)-allocation-count
• mem-util-next-hop-packet-reassembly-(rw)-free-count
• mem-util-next-hop-packet-reassembly---persistent-(rw)-bytes-allocated
• mem-util-next-hop-packet-reassembly---persistent-(rw)-allocation-count
• mem-util-next-hop-packet-reassembly---persistent-(rw)-free-count
• mem-util-next-hop-ml-bundle-bytes-allocated
• mem-util-next-hop-ml-bundle-allocation-count
• mem-util-next-hop-ml-bundle-free-count
• mem-util-next-hop-ddos-scfd-params-bytes-allocated
• mem-util-next-hop-ddos-scfd-params-allocation-count
• mem-util-next-hop-ddos-scfd-params-free-count
• mem-util-next-hop-vbf-bytes-allocated
• mem-util-next-hop-vbf-allocation-count
• mem-util-next-hop-vbf-free-count
63
Table 4: gRPC Sensors (Continued)
resource path Description
• mem-util-next-hop-ptp-ieee-1588-nhs-bytes-allocated
• mem-util-next-hop-ptp-ieee-1588-nhs-allocation-count
• mem-util-next-hop-ptp-ieee-1588-nhs-free-count
• mem-util-next-hop-cos-bytes-allocated
• mem-util-next-hop-cos-allocation-count
• mem-util-next-hop-cos-free-count
• mem-util-next-hop-inline-hash-sessions-bytes-allocated
• mem-util-next-hop-inline-hash-sessions-allocation-count
• mem-util-next-hop-inline-hash-sessions-free-count
• mem-util-next-hop-inline-mdi-bytes-allocated
• mem-util-next-hop-inline-mdi-allocation-count
• mem-util-next-hop-inline-mdi-free-count
• mem-util-next-hop-cos-enhanced-priority-bytes-allocated
• mem-util-next-hop-cos-enhanced-priority-allocation-count
• mem-util-next-hop-cos-enhanced-priority-free-count
• mem-util-firewall-fw-bytes-allocated
• mem-util-firewall-fw-allocation-count
• mem-util-firewall-fw-free-count
• mem-util-counters-fw-counter-bytes-allocated
• mem-util-counters-fw-counter-allocation-count
• mem-util-counters-fw-counter-free-count
• mem-util-counters-fw-policer-bytes-allocated
64
Table 4: gRPC Sensors (Continued)
resource path Description
• mem-util-counters-fw-policer-allocation-count
• mem-util-counters-fw-policer-free-count
• mem-util-counters-ifd-error-cntr-bytes-allocated
• mem-util-counters-ifd-error-cntr-allocation-count
• mem-util-counters-ifd-error-cntr-free-count
• mem-util-counters-nh-cntr-bytes-allocated
• mem-util-counters-nh-cntr-allocation-count
• mem-util-counters-nh-cntr-free-count
• mem-util-counters-ifl-cntr-bytes-allocated
• mem-util-counters-ifl-cntr-allocation-count
• mem-util-counters-ifl-cntr-free-count
• mem-util-counters-bridge-domain-counter0-bytes-allocated
• mem-util-counters-bridge-domain-counter0-allocation-count
• mem-util-counters-bridge-domain-counter0-free-count
• mem-util-counters-bridge-domain-counter0-free-count
• mem-util-counters-bridge-domain-cntr-bytes-allocated
• mem-util-counters-bridge-domain-cntr-allocation-count
• mem-util-counters-bridge-domain-cntr-free-count
• mem-util-counters-sample-inline-params-bytes-allocated
• mem-util-counters-sample-inline-params-allocation-count
• mem-util-counters-sample-inline-params-free-count
• mem-util-counters-services-counters-bytes-allocated
65
Table 4: gRPC Sensors (Continued)
resource path Description
• mem-util-counters-services-counters-allocation-count
• mem-util-counters-services-counters-free-count
• mem-util-counters-exception-counter-bytes-allocated
• mem-util-counters-exception-counter-allocation-count
• mem-util-counters-exception-counter-free-count
• mem-util-counters-issu-policer-bytes-allocated
• mem-util-counters-issu-policer-allocation-count
• mem-util-counters-issu-policer-free-count
• mem-util-counters-ddos-scfd-counters-bytes-allocated
• mem-util-counters-ddos-scfd-counters-allocation-count
• mem-util-counters-ddos-scfd-counters-free-count
• mem-util-counters-ip-reassembly-counter-bytes-allocated
• mem-util-counters-ip-reassembly-counter-allocation-count
• mem-util-counters-ip-reassembly-counter-free-count
• mem-util-hash-hash-edmem-overhead-bytes-allocated
• mem-util-hash-hash-edmem-overhead-bytes-allocated
• mem-util-hash-hash-edmem-overhead-bytes-allocated
• mem-util-hash-hash-edmem-overhead-bytes-allocated
• mem-util-hash-hash-edmem-overhead-bytes-allocated
• mem-util-hash-hash-edmem-overhead-allocation-count
• mem-util-hash-hash-edmem-overhead-free-count
• mem-util-hash-hash-edmem-bkt-bytes-allocated
66
Table 4: gRPC Sensors (Continued)
resource path Description
• mem-util-hash-hash-edmem-bkt-allocation-count
• mem-util-hash-hash-edmem-bkt-free-count
• mem-util-hash-hash-edmem-rec-bytes-allocated
• mem-util-hash-hash-edmem-rec-allocation-count
• mem-util-hash-hash-edmem-rec-free-count
• mem-util-hash-hash-edmem-sideband-bytes-allocated
• mem-util-hash-hash-edmem-sideband-allocation-count
• mem-util-hash-hash-edmem-sideband-free-count
• mem-util-hash-hash-dmem-bkt-bytes-allocated
• mem-util-hash-hash-dmem-bkt-allocation-count
• mem-util-hash-hash-dmem-bkt-free-count
• mem-util-hash-hash-dmem-rec-bytes-allocated
• mem-util-hash-hash-dmem-rec-allocation-count
• mem-util-hash-hash-dmem-rec-free-count
• mem-util-hash-hash-dmem-sideband-bytes-allocated
• mem-util-hash-hash-dmem-sideband-allocation-count
• mem-util-hash-hash-dmem-sideband-free-count
• mem-util-encaps-ueid-bytes-allocated
• mem-util-encaps-ueid-allocation-count
• mem-util-encaps-ueid-free-count
• mem-util-encaps-ueid-shared-bytes-allocated
• mem-util-encaps-ueid-shared-bytes-allocated
67
Table 4: gRPC Sensors (Continued)
resource path Description
• mem-util-encaps-ueid-shared-allocation-count
• mem-util-encaps-ueid-shared-free-count
• mem-util-encaps-fabric-bytes-allocated
• mem-util-encaps-fabric-allocation-count
• mem-util-encaps-fabric-free-count
• mem-util-services-nh-inline-jflow-sample-rr-(svcs)-bytes-allocated
• mem-util-services-nh-inline-jflow-sample-rr-(svcs)-allocation-count
• mem-util-services-nh-inline-jflow-sample-rr-(svcs)-free-count
• mem-util-services-nh-inline-jflow-sample-nh-(svcs)-bytes-allocated
• mem-util-services-nh-inline-jflow-sample-nh-(svcs)-allocation-count
• mem-util-services-nh-inline-jflow-sample-nh-(svcs)-free-count
68
Table 4: gRPC Sensors (Continued)
resource path Description
junos/system/linecard/npu/memory/ Sensor for network processing unit (NPU) memory, NPU memoryutilization, and total memory available for each memory type.
Supported on QFX10000 switches and PTX1000 routers startingwith Junos OS Release 17.2R1.
Supported on EX9200 switches starting with Junos OS Release17.3R1.
NOTE: Starting with Junos Release 17.4R1, FPC1 and FCP2 on PTXSeries routers export data for NPU memory and NPU memoryutilization. Previously, this sensor was supported only on FPC 3.
Starting with Junos OS Release 18.3R1, EX4650 switches aresupported.
Starting with Junos OS Release 19.1R1, periodic streaming onPTX10002 routers is supported.
Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 andMX2020 routers and PTX1000 and PTX10000 routers are supportedon gRPC and gNMI services.
The OpenConfig path is /components/component[name="FPC<fpc-id>:NPU<npu-id>"] /properties/property/
You can also add the following to the end of the path to streamspecific statistics for NPU memory:
• [name="mem-util-<memory-name>-size"]/value
• [name="mem-util-<memory-name>-bytes-allocated"]/value
• [name="mem-util-<memory-name>-utilization"]/value
• [name="mem-util-<partition-name>-< app-name>-allocation-count"]/value
• [name="mem-util-<partition-name>-< app-name>-bytes-allocated"]/value
• [name="mem-util-<partition-name>-< app-name>-free-count"]/value
You can also add the following to the end of the path to streamspecific statistics for NPU:
69
Table 4: gRPC Sensors (Continued)
resource path Description
• [name="util-<memory-name>-average-util">/value
• [name="util-<memory-name>-highest-util">/value
• [name="util-<memory-name>-lowest-util">/value
• [name="util-<memory-name>-average-cache-hit-rate">/value
• [name="util-<memory-name>-lowest-cache-hit-rate">/value
• [name="util-<packet-identifier>-rate">/value
You can also export the following statistics for NPU memory for PTXrouters only
• pfe_name
• combined_pool_name
• combined_size
• combined_usage_cnt
• combined_utilization
• global_pool_name
• global_usage_cnt
• global_alloc_cnt
• global_free_cnt
• local_pool_name
• local_usage_cnt
• local_alloc_cnt
• local_free_cnt
70
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/node-slicing/af-fab-stats/ Sensor to export abstracted fabric (AF) interface-specific load-balancing and fabric queue statistics. This sensor is only supportedfor in node virtualization configurations on MX routers with an AFInterface as the connecting link between guest network functions(GNFs).The sensor also reports aggregated statistics across all AFinterfaces hosted on a source packet forwarding engine of local guestGNFs along with the fabric statistics for all traffic ingressing from andegressing to the fabric from that the packet forwarding engine.
Supported on MX480, MX960, MX2010, MX2020, MX2008 andMX-ELM routers with Junos OS Release 18.4R1.
/junos/system/linecard/cpu/memory/ Sensor for CPU memory. This sensor exports the CPU and memoryutilization per process and CPU usage for threads per process. Thecurrent implementation is Linux-based; therefore, the exportinformation and gathered output format differs significantly from thissensor’s performance on previous platforms.
Supported on MX Series routers with MPC10E-10C-MRATE andMPC10E-15C-MRATE line cards starting with Junos OS Release19.3R1 for exporting telemetry information using gRPC services. Thisfeature provides a different level of exported statistics in comparisonto previous releases because it use the OpenConfig AFT model.
Supported on MX2010 and MX2020 routers with MX2K-MPC11Eline cards starting with Junos OS Release 20.1R1 for streamingtelemetry information using gRPC services.
Supported on EX2300, EX2300-MP, and EX3400 switches startingwith Junos OS Release 20.2R1 and later for streaming telemetryinformation using gRPC services.
Supported on MX960, MX2008, MX2010, MX2020, PTX1000,PTX5000 routers, PTX10000 line of routers, and QFX5100 andQFX5200 switches starting with Junos OS Release 20.2R1 and laterfor INITIAL_SYNC statistics using gNMI services.
The statistics exported from this sensor are found in the followingoperational mode commands: show system info, show systemprocesses, and show system cpu.
71
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/cpu/memory/ Sensor for CPU memory.
NOTE: On PTX Series routers, FPC1 and FPC2 are not supported.
Supported on QFX10000 switches and PTX1000 routers startingwith Junos OS Release 17.2R1.
Supported on EX9200 switches starting with Junos OS Release17.3R1.
Supported on QFX5100, QFX5110, and QFX5200 switches startingwith Junos OS Release 18.2R1.
Supported on QFX5120-48Y and EX4650 switches starting withJunos OS Release 18.3R1.
Supported on EX4600 switches starting with Junos OS Release18.4R1.
Periodic streaming is supported on on QFX10002 switches andPTX10002 routers starting with Junos OS Release 19.1R1.
Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010and MX2020 routers, PTX1000 and PTX10000 routers, andQFX5100 and QFX5200 switches are supported on gRPC and gNMIservices.
Supported on QFX5200 switches starting with Junos OS Release19.2R1 for streaming telemetry information using gNMI services.
Periodic streaming using gRPC services is supported on EX4300-MPswitches starting with Junos OS Release 19.4R1,
Periodic streaming using gRPC services is supported on EX2300,EX2300-MP, and EX3400 switches starting with Junos OS Release20.2R1.
You can also include the following to end of the resource path forCPU memory:
• [name="mem-util-<memory-name>-size"]/value
• [name="mem-util-<memory-name>-bytes-allocated"]/value
• [name="mem-util-<memory-name>-utilization"]/value
72
Table 4: gRPC Sensors (Continued)
resource path Description
• [name="mem-util-<memory-name>-< app-name>-allocations"]/value
• [name="mem-util-<memory-name>-< app-name>-frees"]/value
• [name="mem-util-<memory-name>-< app-name>-allocations-failed"]/value
73
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/npu/memory/ Sensor for NPU Memory utilization statistics.
Shown below, statistics are exported for the default FPC (FPC0).Multiples FPCs are supported. The component values and propertyvalues are names (like interface names).
Starting in Junos OS Evolved Release 19.4R1, streaming statisticsusing gRPC and gNMI services on PTX10008 routers is supported.
Starting in Junos OS Release 20.2R1, INITIAL_SYNC statistics usinggNMI services on MX960, MX2008, MX2010, MX2020, PTX1000,PTX5000 routers, PTX10000 line of routers, and QFX5100 andQFX5200 switches are supported.
Starting in Junos OS Evolved Release 21.4R1, streaming statistics bymeans of gRPC and gNMI is supported on PTX10001-36MR,PTX10004, and PTX10008 routers.
The following statistics are exported:
• /components-memory/component[name='FPC0:NPU17']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-epp-mapid-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-epp-mapid-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-epp-mapid-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-l2domain-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-l2domain-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-l2domain-utilizationn']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash00-size']/
74
Table 4: gRPC Sensors (Continued)
resource path Description
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash00-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash00-utilization']/
• :/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash10-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash10-allocatedd']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-tunnell2domainhash10-utilization']/
• :/components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-slu-my-mac-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-slu-my-mac-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-slu-my-mac-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-dlu-idb-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-dlu-idb-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-kht-dlu-idb-utilization']/ }
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-final-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-final-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-final-utilization']/
75
Table 4: gRPC Sensors (Continued)
resource path Description
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-remap-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-remap-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-remap-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-refbits-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-refbits-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-refbits-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-nh-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-nh-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-nh-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-mpls-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-mpls-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name=' mem-util-jnh-mpls-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-loadbal-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-loadbal-allocated']/
76
Table 4: gRPC Sensors (Continued)
resource path Description
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-loadbal-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-egress-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-egress-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jnh-egress-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jtree-memory-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jtree-memory-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-jtree-memory-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-vfilter-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-vfilter-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-vfilter-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-phyfilter-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-phyfilter-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-phyfilter-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-action-size']/
77
Table 4: gRPC Sensors (Continued)
resource path Description
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-action-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-action-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-tcam-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name=' mem-util-flt-tcam-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-tcam-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-0-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-0-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-0-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-1-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-1-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-1-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='']/
78
Table 4: gRPC Sensors (Continued)
resource path Description
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-2-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-2-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-2-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-3-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-3-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-3-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-4-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-4-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-fcv-blk-4-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-scv-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-scv-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-scv-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-0-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-0-allocated']/
79
Table 4: gRPC Sensors (Continued)
resource path Description
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-0-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-1-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-1-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-1-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-2-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-2-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-2-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-3-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-3-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-3-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-4-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-4-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-4-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-5-size']/
80
Table 4: gRPC Sensors (Continued)
resource path Description
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-5-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-5-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-6-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-6-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-6-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-7-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-7-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-0-bank-7-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name=' mem-util-flt-beta-1-bank-0-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-0-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-0-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-1-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-1-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-1-utilization']/
81
Table 4: gRPC Sensors (Continued)
resource path Description
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-2-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-2-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-2-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-3-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-3-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-3-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-4-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-4-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-4-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-5-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-5-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-5-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-6-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-6-allocated']/
82
Table 4: gRPC Sensors (Continued)
resource path Description
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-6-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-7-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-7-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-beta-1-bank-7-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-kht-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-kht-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-kht-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-bft-0-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-bft-0-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-bft-0-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-plt-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-plt-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-0-plt-utilization']/
83
Table 4: gRPC Sensors (Continued)
resource path Description
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-kht-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-kht-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-kht-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-bft-0-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-bft-0-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-bft-0-utilization']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-plt-size']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-plt-allocated']/
• /components-memory/component[name='FPC0:NPU17']/properties/property[name='mem-util-flt-alpha-1-plt-utilization']/
84
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/npu/utilization Sensor for NPU utilization on the Packet Forwarding Engine.
Packet Forwarding Engine utilization is exported exported as apercentage using input notifications.
The following packet statistics are also exported as part of this field:
• Loopback (pps)
• Recirculation (pps)
• WAN and host inject (pps)
• ASIC to host (pps)
Shown below, statistics are exported for the default FPC (FPC0).Multiples FPCs are supported. The component values and propertyvalues are names (like interface names).
Starting in Junos OS Evolved Release 19.4R1, streaming statisticsusing gRPC and gNMI services on PTX10008 routers is supported.
The following statistics are exported:
• /components-utilization/component[name='FPC0:NPU17'
• /components-utilization/component[name='FPC0:NPU17']/properties/property[name='util-metric']
• /components-utilization/component[name='FPC0:NPU17']/properties/property[name='util-Loopback-packet-rate']
• components-utilization/component[name='FPC0:NPU17']/properties/property[name='util-Recirculation-packet-rate']
• /components-utilization/component[name='FPC0:NPU17']/properties/property[name='util-Wan and Host inject-packet-rate']
• /components-utilization/component[name='FPC0:NPU17']/properties/property[name='util-ASIC to host-packet-rate']
85
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/npu/utilization/ Packet Forwarding Engine sensor for NPU processor utilization.
Supported on MX Series routers with MPC10E-10C-MRATE andMPC10E-15C-MRATE line cards starting with Junos OS Release19.3R1 for streaing telemetry information using gRPC services. Thisfeature provides a different level of exported statistics in comparisonto previous releases because it uses the OpenConfig AFT model.
Supported on MX2010 and MX2020 routers with MX2K-MPC11Eline cards starting with Junos OS Release 20.1R1 for streamingtelemetry information using gRPC services.
Supported on MX960, MX2008, MX2010, MX2020, PTX1000,PTX5000 routers, PTX10000 line of routers, and QFX5100 andQFX5200 switches starting with Junos OS Release 20.2R1 and laterfor INITIAL_SYNC statistics using gNMI services.
You can also include the following to the end of the resource path forNPU utilization:
• util-metric
• util-Disp 0 Pkts-packet-rate
• util-Disp 0 Pkts-average-instructions-per-packet
• util-Disp 0 Pkts-average-wait-cycles-per-packet
• util-Disp 0 Pkts-average-cycles-per-packet
• util-Disp 1 Pkts-packet-rate
• util-Disp 1 Pkts-average-instructions-per-packet
• util-Disp 1 Pkts-average-wait-cycles-per-packet
• util-Disp 1 Pkts-average-cycles-per-packet
•
• util-Disp 2 Pkts-packet-rate
• util-Disp 2 Pkts-average-instructions-per-packet
86
Table 4: gRPC Sensors (Continued)
resource path Description
• util-Disp 2 Pkts-average-wait-cycles-per-packet
• util-Disp 2 Pkts-average-cycles-per-packet
• util-Disp 3 Pkts-packet-rate
•
• util-Disp 3 Pkts-average-instructions-per-packet
• util-Disp 3 Pkts-average-wait-cycles-per-packet
• util-Disp 3 Pkts-average-cycles-per-packet
• mem-util-EDMEM-average-util
• mem-util-EDMEM-highest-util
• mem-util-EDMEM-lowest-util
• mem-util-EDMEM-average-cache-hit-rate
• mem-util-EDMEM-highest-cache-hit-rate
• mem-util-EDMEM-lowest-cache-hit-rate
• mem-util-IDMEM-average-util
• mem-util-IDMEM-highest-util
• mem-util-IDMEM-lowest-util
• mem-util-IDMEM-average-cache-hit-rate
• mem-util-IDMEM-highest-cache-hit-rate
• mem-util-IDMEM-lowest-cache-hit-rate
• mem-util-Bulk DMEM-average-util
• mem-util-Bulk DMEM-highest-util
• mem-util-Bulk DMEM-lowest-util
87
Table 4: gRPC Sensors (Continued)
resource path Description
• mem-util-Bulk DMEM-average-cache-hit-rate
• mem-util-Bulk DMEM-highest-cache-hit-rate
• mem-util-Bulk DMEM-lowest-cache-hit-rate
/junos/system/linecard/npu/utilization/ Packet Forwarding Engine sensor for NPU processor utilization.
Periodic streaming is supported on PTX10002 routers starting withJunos OS Release 19.1R1.
Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010and MX2020 routers and PTX1000 and PTX10000 routers aresupported on gRPC and gNMI services.
Starting in Junos OS Evolved Release 21.4R1, streaming statistics bymeans of gRPC and gNMI is supported on PTX10001-36MR,PTX10004, and PTX10008 routers.
88
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/interface/ Packet Forwarding Engine sensor for physical interface traffic.
NOTE: For PTX Series routers, for a specific interface, queuestatistics are exported for each line card. For MX series routers,interface queue statistics are exported only from the slot on whichan interface is configured.
For Aggregated Ethernet interfaces, statistics are exported for themember physical interfaces. You must aggregate the counters at thedestination server, or collector.
If a physical interface is administratively down or operationally down,interface counters are not exported.
Issuing an operational clear command, such as clear interfacesstatistics all, does not reset statistics exported by the line card.
Supported on PTX Series routers starting with Junos OS Release15.1F3. Supported on MX Series routers starting with Junos OSRelease 15.1F5.
Supported on QFX10000 switches and PTX1000 routers startingwith Junos OS Release 17.2R1.
Supported on EX9200 switches and MX150 routers starting withJunos OS Release 17.3R1.
Supported on QFX5100, QFX5110, and QFX5200 switches startingwith Junos OS Release 18.2R1.
Supported on QFX5120-48Y and EX4650 switches starting withJunos OS Release 18.3R1.
Supported on EX4600 switches Starting with Junos OS Release18.4R1.
Periodic streaming is supported on QFX10002 switches andPTX10002 routers starting with Junos OS Release 19.1R1.
Supported on MX960, MX2008, MX2010 and MX2020 routers,PTX1000 and PTX10000 routers, and QFX5100 and QFX5200switches with Junos OS Release 19.2R1 on gRPC and gNMI services.
Supported on MX240, MX480, and MX960 routers starting withJunos OS Release 19.3R1 for exporting telemetry information usinggNMI services. This feature includes support to export telemetry
89
Table 4: gRPC Sensors (Continued)
resource path Description
data for integration with AFTTelemetry and LibTelemetry librarieswith the OpenConfig model openconfig-aft.
Starting with Junos OS Release 19.4R1, periodic streaming usinggRPC services with EX4300-MP switches is supported.
Periodic streaming using gNMI services on MX2K-MPC11E line cardson MX2010 and MX2020 routers is supported starting with JunosOS Release 20.1R1.
Periodic streaming using gRPC services is supported on EX2300,EX2300-MP, and EX3400 switches starting with Junos OS Release20.2R1.
INITIAL_SYNC statistics using gNMI services is supported onMX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers,PTX10000 line of routers, and QFX5100 and QFX5200 switchesstarting with Junos OS Release 20.2R1.
Streaming statistics using gRPC services or gNMI services issupported on PTX10008 routers starting with Junos OS Release20.2R1.
90
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/interface/logical/usage Packet Forwarding Engine sensor for logical interface statistics.
NOTE: If a logical interface is operationally down, interface statisticscontinue to be exported.
Issuing an operational clear command, such as clear interfacesstatistics all, does not reset statistics exported by the line card.
NOTE: If a logical interface is operationally down, interface statisticscontinue to be exported.
Issuing an operational clear command, such as clear interfacesstatistics all, does not reset statistics exported by the line card.
NOTE: Locally injected packets from the Routing Engine are notexported.
NOTE: Locally injected packets from the Routing Engine are notexported.
Supported in Junos OS Release 15.1F5.
Supported QFX10000 switches starting with on Junos OS Release17.2R1.
Supported on EX9200 switches and MX150 routers starting withJunos OS Release 17.3R1.
Supported on QFX5100, QFX5110, and QFX5200 switches startingwith Junos OS Release 18.2R1.
Supported on QFX5120-48Y and EX4650 switches starting withJunos OS Release 18.3R1.
Supported on EX4600 switches starting with Junos OS Release18.4R1.
Starting with Junos OS Release 19.1R1, periodic streaming issupported on QFX10002 switches and PTX10002 routers.
Supported on MX960, MX2008, MX2010 and MX2020 routers,PTX1000 and PTX10000 routers, and QFX5100 and QFX5200switches with Junos OS Release 19.2R1 on gRPC and gNMI services.
Supported on QFX5200 switches starting with Junos OS Release19.2R1 for streaming telemetry information using gNMI services.
91
Table 4: gRPC Sensors (Continued)
resource path Description
Supported on MX240, MX480, and MX960 routers starting withJunos OS Release 19.3R1 for exporting telemetry information usinggNMI services. This feature includes support to export telemetrydata for integration with AFTTelemetry and LibTelemetry librarieswith the OpenConfig model openconfig-aft.
Starting with Junos OS Release 19.4R1, periodic streaming usinggRPC services with EX4300-MP switches is supported.
Periodic streaming using gNMI services on MX2K-MPC11E line cardson MX2010 and MX2020 routers is supported starting with JunosOS Release 20.1R1.
Periodic streaming using gRPC services is supported on EX3400switches starting with Junos OS Release 20.2R1.
INITIAL_SYNC statistics using gNMI services is supported onMX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers,PTX10000 line of routers, and QFX5100 and QFX5200 switchesstarting with Junos OS Release 20.2R1.
92
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/interface/queue/ Sensor for interface queue statistics.
Starting with Junos OS Release 18.3R1, when a subscription is madeto /interfaces on MX, EX, QFX, PTX, and ACX platforms, traffic andqueue statistics are delivered in two separate sensors:
• /junos/system/linecard/interface/traffic/
• /junos/system/linecard/interface/queue/
This can reduce the reap time for non-queue data for platformssupporting Virtual Output Queues (VOQ), such as PTX Seriesrouters.
Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 andMX2020 routers, PTX1000 and PTX10000 routers, and QFX5100and QFX5200 switches are supported on gRPC and gNMI services.
Supported on MX240, MX480, and MX960 routers starting withJunos OS Release 19.3R1 for exporting telemetry information usinggNMI services. This feature includes support to export telemetrydata for integration with AFTTelemetry and LibTelemetry librarieswith the OpenConfig model openconfig-aft.
Periodic streaming using gNMI services on MX2K-MPC11E line cardson MX2010 and MX2020 routers is supported starting with JunosOS Release 20.1R1.
INITIAL_SYNC statistics using gNMI services is supported onMX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers,PTX10000 line of routers, and QFX5100 and QFX5200 switchesstarting with Junos OS Release 20.2R1.
93
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/interface/traffic/ Sensor for interface traffic, exporting all fields except queuestatistics.
Starting with Junos OS Release 18.3R1, when a subscription is madeto /interfaces on MX, EX, QFX, PTX, and ACX platforms, traffic andqueue statistics are delivered in two separate sensors:
• /junos/system/linecard/interface/traffic/
• /junos/system/linecard/interface/queue/
This can reduce the reap time for non-queue data for platformssupporting Virtual Output Queues (VOQ), such as PTX Seriesrouters.
Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 andMX2020 routers, PTX1000 and PTX10000 routers, and QFX5100and QFX5200 switches are supported on gRPC and gNMI services.
Supported on MX240, MX480, and MX960 routers starting withJunos OS Release 19.3R1 for exporting telemetry information usinggNMI services. This feature includes support to export telemetrydata for integration with AFTTelemetry and LibTelemetry librarieswith the OpenConfig model openconfig-aft.
Periodic streaming using gNMI services on MX2K-MPC11E line cardson MX2010 and MX2020 routers is supported starting with JunosOS Release 20.1R1.
INITIAL_SYNC statistics using gNMI services is supported onMX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers,PTX10000 line of routers, and QFX5100 and QFX5200 switchesstarting with Junos OS Release 20.2R1.
Streaming statistics using gRPC services or gNMI services issupported on PTX10008 routers starting with Junos OS Release20.2R1.
94
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/intf-exp/ Sensor for physical interface express statistics.
Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 andMX2020 routers, PTX1000 and PTX10000 routers, and QFX5100and QFX5200 switches are supported on gRPC and gNMI services.
/junos/system/linecard/optical Sensor for optical alarms. Configure this sensor for et-type-fpc/pic/port (100-Gigabit Ethernet) interfaces.
Supported on ACX6360 Universal Metro, MX Series, and PTX Seriesrouters with a CFP2-DCO optics module starting with Junos OSRelease 18.3R1. This module provides a high-density, long-haul OTNtransport solution with MACSec capability.
Supported on MX960, MX2008, MX2010 and MX2020 routers,PTX1000 and PTX10000 routers, and QFX5100 and QFX5200switches starting with Junos OS Release 19.2R1 on gRPC and gNMIservices.
/junos/system/linecard/otn Sensor for G.709 optical transport network (OTN) alarms. Configurethis sensor on ot-type-fpc/pic/port interfaces.
Supported on ACX6360 Universal Metro, MX Series, and PTX Seriesrouters with a CFP2-DCO optics module starting with Junos OSRelease 18.3R1. This module provides a high-density, long-haul OTNtransport solution with MACSec capability.
Supported on MX960, MX2008, MX2010 and MX2020 routers,PTX1000 and PTX10000 routers, and QFX5100 and QFX5200switches starting with Junos OS Release 19.2R1 on gRPC and gNMIservices.
95
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/qmon-sw/ Sensor for congestion and latency monitoring statistics.
Supported on QFX5100, QFX5110, and QFX5200 switches startingwith Junos OS Release 18.2R1.
Supported on QFX5120-48Y and EX4650 switches starting withJunos OS Release 18.3R1.
Supported on EX4600 switches starting with Junos OS Release18.4R1.
Supported on MX960, MX2008, MX2010 and MX2020 routers,PTX1000 and PTX10000 routers, and QFX5100 and QFX5200switches starting with Junos OS Release 19.2R1 on gRPC and gNMIservices.
Supported on QFX5200 switches starting with Junos OS Release19.2R1 for streaming telemetry information using gNMI services.
Periodic streaming using gRPC services with EX4300-MP switches issupported starting with Junos OS Release 19.4R1.
Periodic streaming using gRPC services is supported on EX3400switches starting with Junos OS Release 20.2R1.
INITIAL_SYNC statistics using gNMI services is supported onMX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers,PTX10000 line of routers, and QFX5100 and QFX5200 switchesstarting with Junos OS Release 20.2R1.
96
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/services/inline-jflow Sensor for inline active flow monitoring services statistics.
Supported on MX960, MX2008, MX2010 and MX2020 routers,PTX1000 and PTX10000 routers, and QFX5100 and QFX5200switches starting with Junos OS Release 19.2R1 on gRPC and gNMIservices.
When configuring inline active flow monitoring in Junos, you canapply version 9 or IPFIX flow templates to define a flow recordtemplate suitable for IPv4 or IPv6 MPLS and bridging traffic. Formore information, see Configuring Flow Aggregation on MX, M, vMXand T Series Routers and NFX250 to Use Version 9 Flow Templates.
Supported on MX Series operating with MPC10E-15C-MRATE line-rate cards starting with Junos OS Release 19.2R1.
Supported on MX240, MX480, and MX960 routers starting withJunos OS Release 19.3R1 for exporting telemetry information usinggNMI services. This feature includes support to export telemetrydata for integration with AFTTelemetry and LibTelemetry librarieswith the OpenConfig model openconfig-aft.
Periodic streaming using gNMI services on MX2K-MPC11E line cardson MX2010 and MX2020 routers is supported starting with JunosOS Release 20.1R1.
Periodic streaming using gRPC services on PTX10008 routers issupported starting with Junos OS Evolved Release 20.1R1.
/network-instances/network-instance[instance-name='name']/protocols/protocol/evpn/irb-interfaces/
Local integrated routing and bridging (IRB) interface informationsensor.
Use the Telemetry Explorer tool to see leafs for this resource path.
Starting with Junos OS Release 20.2R1, streaming statistics issupported using gRPC services with QFX5100, QFX5110, QFX5120,QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016switches.
97
Table 4: gRPC Sensors (Continued)
resource path Description
/network-instances/network-instance[instance-name='name']/protocols/protocol/evpn/vxlan-tunnel-end-point/
Overlay VX-LAN tunnel information sensor. This sensor also deliversVTEP information ON_CHANGE leafs:
• source_ip_address
• remote_ip_address
• status
• mode
• nexthop-index
• event-type
• source-interface
Starting with Junos OS Release 20.2R1, streaming statistics issupported using gRPC services with QFX5100, QFX5110, QFX5120,QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016switches.
/network-instances/network-instance[instance-name='name']/mac_db/entries/entry/
EVPN MAC table information sensor.
Use the Telemetry Explorer tool to see leafs for this resource path.
Starting with Junos OS Release 20.2R1, streaming statistics issupported using gRPC services with QFX5100, QFX5110, QFX5120,QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016switches.
/network-instances/network-instance[instance-name='name']/macip_db/entries/entry/
MAC-IP or ARP-ND table sensor.
Use the Telemetry Explorer tool to see leafs for this resource path.
Starting with Junos OS Release 20.2R1, streaming statistics issupported using gRPC services with QFX5100, QFX5110, QFX5120,QFX5200, QFX10002-60C, QFX10002, QFX10008, and QFX10016switches.
98
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/firewall/ Sensor for firewall filter counters and policer counters. Each line cardreports counters separately.
Supported on QFX10000 switches starting with Junos OS Release17.2R1.
Supported on PTX1000 routers and EX9200 switches starting withJunos OS Release 17.3R1.
Supported on QFX5100, QFX5110, and QFX5200 switches startingwith Junos OS Release 18.2R1.
Supported on QFX5120-48Y and EX4650 switches starting withJunos OS Release 18.3R1.
Supported on EX4600 switches starting with Junos OS Release18.4R1.
Starting with Junos OS Release 19.1R1, periodic streaming issupported on QFX10002 switches and PTX10002 routers.
Starting in Junos OS Evolved Release 19.1R1, PTX10003 routers aresupported.
Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 andMX2020 routers, PTX1000 and PTX10000 routers, and QFX5100and QFX5200 switches are supported on gRPC and gNMI services.
Supported on QFX5200 switches starting with Junos OS Release19.2R1 for streaming telemetry information using gNMI services.
Supported on MX240, MX480, and MX960 routers starting withJunos OS Release 19.3R1 for exporting telemetry information usinggNMI services. This feature includes support to export telemetrydata for integration with AFTTelemetry and LibTelemetry librarieswith the OpenConfig model openconfig-aft.
Periodic streaming using gRPC services with EX4300-MP switches issupported starting with Junos OS Release 19.4R1.
Periodic streaming using gNMI services with PTX10003 routers issupported starting with Junos OS Evolved Release 19.4R1.
Periodic streaming using gNMI services on MX2K-MPC11E line cardson MX2010 and MX2020 routers is supported starting with JunosOS Release 20.1R1.
99
Table 4: gRPC Sensors (Continued)
resource path Description
Periodic streaming using gRPC services is supported on EX2300,EX2300-MP, and EX3400 switches starting with Junos OS Release20.2R1.
INITIAL_SYNC statistics using gNMI services is supported onMX960, MX2008, MX2010, MX2020, PTX1000, PTX5000 routers,PTX10000 line of routers, and QFX5100 and QFX5200 switchesstarting with Junos OS Release 20.2R1.
NOTE: Hierarchical policer statistics are collected for MX Seriesrouters only. Traffic-class counter statistics are collected for PTXSeries routers and QFX10000 switches only.
Firewall counters are exported even if the interface to which thefirewall filter is attached is operationally down.
The following OpenConfig paths are supported:
• junos/firewall/firewall-stats/[name='filter-name']/timestamp
• /junos/firewall/firewall-stats/[name='filter-name']/ memory-usage/[name='memory-type']/allocated
• /junos/firewall/firewall-stats/[name='filter-name']/ counter-stats/[name='counter-name']/packets
• /junos/firewall/firewall-stats/[name='filter-name']/ counter-stats/[name='couner-name']/bytes
• /junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/out-of-spec-packets
• /junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/out-of-spec-bytes
• /junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/offered-packets
• /junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/offered-bytes
• /junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/transmitted-packets
100
Table 4: gRPC Sensors (Continued)
resource path Description
• /junos/firewall/firewall-stats/[name='filter-name']/ policer-stats/[name='policer-name']/transmitted-bytes
• /junos/firewall/firewall-stats/[name='filter-name']/hierarchical-policer-stats/[name='hierarchical-policer-name']/premium-packets (MX Series only)
• /junos/firewall/firewall-stats/[name='filter-name']/hierarchical-policer-stats/[name='hierarchical-policer-name']/premium-bytes (MX Series only)
• /junos/firewall/firewall-stats/[name='filter-name']/hierarchical-policer-stats/[name='hierarchical-policer-name']/aggregate-packets (MX Series only)
• /junos/firewall/firewall-stats/[name='filter-name']/hierarchical-policer-stats/[name='hierarchical-policer-name']/aggregate-bytes (MX Series only)
/junos/system/linecard/intf-exp/ Interface express sensor.
This sensor leverages statistics out of the physical interface sensor,providing faster and more frequent operational status statistics. Onlythe physical interfaces’ operational status from the Flexible PICConcentrator (FPC) is collected and reported. Statistics from theRouting Engine interface are not reported.
Supported on PTX1000, PTX3000, PTX5000, and PTX10000starting with Junos OS Release 18.1R1.
Supported on MX960, MX2010, and MX2020 routers starting withJunos OS Release 19.3R1.
101
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/optics/ Sensor for various optical interface performance metrics, such astransmit and receive power levels.
Supported on QFX10000 switches starting with Junos OS Release17.2R1.
Supported on PTX1000 routers and EX9200 switches starting withJunos OS Release 17.3R1.
Supported on EX4650 switches starting with Junos OS Release18.3R1.
Supported on MX960, MX2008, MX2010 and MX2020 routers,PTX1000 and PTX10000 routers, and QFX5100 and QFX5200switches starting with Junos OS Release 19.2R1 on gRPC and gNMIservices.
/mpls/lsps-constrained-path/tunnels/tunnel[name='foo-name',source='foo-source']/p2p-tunnel-attributes/p2p-primary-paths[name='foo-path']/state/name
Sensor to export the path name for ingress point-to-point LSPs,point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs.
This sensor is supported on indicated platforms up to and includingJunos OS Release 17.3R1. See the following resource paths for LSPsupport in Junos OS Release 17.4R1 and higher:
• /network-instances/network-instance[name='instance-name']/mpls/lsps-constrained-path/tunnels/tunnel/p2p-tunnel-attributes/p2p-primary-paths/
• /network-instances/network-instance[name='instance-name']/mpls/signaling-protocols/rsvp-te/sessions/session/state/notify-status
Supported on PTX Series routers, MX Series routers , andQFX10002, QFX10008, and QFX10016 switches starting with JunosOS Release 17.2R1.
102
Table 4: gRPC Sensors (Continued)
resource path Description
/mpls/lsps-constrained-path/tunnels/tunnel[name='foo-name',source='foo-source']/p2p-tunnel-attributes/p2p-primary-paths[name='foo-path']/lsp-instances[index='local-index']/state/
Sensor to export LSP properties for ingress point-to-point LSPs,point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs
Supported on PTX Series routers, MX Series routers, and QFX10002,QFX10008, and QFX10016 switches starting with Junos OS Release17.2R1.
The following end paths are also supported for the resource path:
• bandwidth
• metric
• max-average-bandwidth
• explicit-route-objects
• record-route-objects
/mpls/signaling-protocols/ldp/lsp-transit-policies/lsp-transit-policy/state/counters
Sensor to export statistics for LDP LSP transit traffic.
Supported on MX Series routers starting with Junos OS Release20.2R1.
/mpls/signaling-protocols/ldp/lsp-ingress-policies/lsp-ingress-policy/state/counters
Sensor to export statistics for LDP LSP ingress traffic.
Supported on MX Series routers starting with Junos OS Release20.2R1.
/mpls/signaling-protocols/ldp/p2mp-lsps/p2mp-lsp/state/counters
Sensor to export statistics for multipoint LDP LSP traffic.
Supported on MX Series routers starting with Junos OS Release20.2R1.
/mpls/signalling-protocols/ldp/p2mp-interfaces/p2mp-interface/state/counters/
Sensor to export statistics for multipoint LDP egress traffic perinterface.
Supported on MX Series routers starting with Junos OS Release20.2R1.
103
Table 4: gRPC Sensors (Continued)
resource path Description
/mpls/signalling-protocols/ldp/p2mp-egress-interfaces/p2mp-interface/state/counters/
Sensor to export statistics for multipoint LDP egress traffic perinterface.
Supported only on MPC10E-10C-MRATE, MPC10E-15C-MRATE,and MX2K-MPC11E line cards line cards on MX Series routersstarting with Junos OS Release 20.3R1.
/mpls/signalling-protocols/ldp/p2mp-interfaces/p2mp-interface/
Sensor to export statistics for multipoint LDP ingress traffic perinterface.
Supported on MX Series routers starting with Junos OS Release20.2R1.
/mpls/lsps/signaling-protocols/rsvp-te/sessions/session[local-index='foo-index']/state/notify-status
Sensor to export statistics for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs.
ON_CHANGE support for LSP events is only activated when thereporting interval is set to 0 in the subscription request.
Supported on PTX Series routers, MX Series routers, and QFX10002,QFX10008, and QFX10016 switches starting with Junos OS Release17.2R1.
The following events are exported under this resource path:
• PATHERR_RECEIVED
• TTL_EXPIRED
• NON_RSVP_CAPABLE_ROUTER
• RESVTEAR_RECEIVED
• PATH_MTU_CHANGE
104
Table 4: gRPC Sensors (Continued)
resource path Description
/network-instances/network-instance/mpls/signaling-protocols/rsvp-te/
Sensor to export events for ingress point-to-point LSPs, point-to-multipoint LSPs, bypass LSPs, and dynamically created LSPs.
Starting in Junos OS Evolved Release 19.2R1, PTX10003 routerssupport streaming statistics.
The following end paths are also supported:
• interface-attributes/interface/bandwidth-reservations/state/active-reservations-count
• interface-attributes/interface/bandwidth-reservations/state/available-bandwidth
• interface-attributes/interface/bandwidth-reservations/state/highwater-mark
• interface-attributes/interface/bandwidth-reservations/state/reserved-bandwidth
• interface-attributes/interface/counters/in-ack-messages
• interface-attributes/interface/counters/in-hello-messages
• interface-attributes/interface/counters/in-path-messages
• interface-attributes/interface/counters/in-path-tear-messages
• interface-attributes/interface/counters/in-reservation-error-messages
• interface-attributes/interface/counters/in-reservation-messages
• interface-attributes/interface/counters/in-reservation-tear-messages
• interface-attributes/interface/counters/in-srefresh-messages
• interface-attributes/interface/counters/out-path-tear-messages
• interface-attributes/interface/counters/out-ack-messages
• interface-attributes/interface/counters/out-hello-messages
105
Table 4: gRPC Sensors (Continued)
resource path Description
• interface-attributes/interface/counters/out-path-messages
• interface-attributes/interface/counters/out-reservation-error-messages
• interface-attributes/interface/counters/out-reservation-messages
• interface-attributes/interface/counters/out-reservation-tear-messages
• interface-attributes/interface/counters/out-srefresh-messages
• neighbors/neighbor/state/neighbor-status
• sessions/session/record-route-objects/record-route-object
• sessions/session/state/destination-address
• sessions/session/state/label-in
• sessions/session/state/label-out
• sessions/session/state/lsp-id
106
Table 4: gRPC Sensors (Continued)
resource path Description
/mpls/signaling-protocols/segment-routing/ Sensor for traffic statistics for both ingress IP traffic and transit MPLStraffic..
Supported on MX Series and PTX Series routers starting with JunosOS Release 18.3R1.
The following end points are also supported and specify BGPSegment Routing traffic Engineering (SR-TE) transit statistics:
• /sr-te-bsid-policies/sr-te-bsid-policy[binding-sid=‘80001’, to-address=’foo-to' color=’foo-color’]/state/counters[name=’oc-xxx’]/packets
• /sr-te-bsid-policies/sr-te-bsid-policy[binding-sid=‘80001’, to-address=’foo-to' color=’foo-color’]/state/counters[name=’oc-xxx’]/bytes
The following end points are also supported and specify BGPSegment Routing traffic Engineering (SR-TE) ingress statistics:
• /sr-te-ip-policies/sr-te-ip-policy[to-address=’foo-to'color=’foo-color’]/state/counters[name=’oc-xxx’]/packets
• /sr-te-ip-policies/sr-te-ip-policy[to-address=’foo-to'color=’foo-color’]/state/counters[name=’oc-xxx’]/bytes
In addition to configuring the sensor, you must enable statisticscollection using the statistics statement at the [[edit protocolssource-packet-routing telemetry statistics] hierarchy level.
107
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/packet/usage/ Sensor for Packet Forwarding Engine Statistics. This sensor exportsstatistics for counters and provides visibility into Packet ForwardingEngine error and drop statistics.
This sensor is supported starting on MX Series and PTX Seriesrouters starting with Junos OS Release 17.4R1.
Starting in Junos OS Evolved Release 19.1R1, PTX10003 routers aresupported.
Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 andMX2020 routers, PTX1000 and PTX10000 routers, and QFX5100and QFX5200 switches are supported on gRPC and gNMI services.
Starting with Junos OS Evolved Release 19.4R1, periodic streamingusing gNMI services with PTX10003 routers is supported.
108
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/system/linecard/packet/usage/ Sensor for Packet Forwarding Engine Statistics. This sensor exportsstatistics and provides visibility into Packet Forwarding Engine errorand drop statistics. Statistics include counters (CC, CPU, and NPU)for traffic data. Note that NPU statistics are different than thosestreamed from the sensors /junos/system/linecard/npu/memory/and /junos/system/linecard/npu/utilization/ . Sensor output iscomparable to the output using the operational mode commandshow pfe statistics traffic.
Shown below, statistics are exported for the default FPC (FPC0).Multiples FPCs are supported. The component values and propertyvalues are names (like interface names).
Starting in Junos OS Evolved Release 19.4R1, streaming statisticsusing gRPC and gNMI services on PTX10008 routers is supported.
Starting in Junos OS Release 20.2R1, INITIAL_SYNC statistics usinggNMI services on MX960, MX2008, MX2010, MX2020, PTX1000,PTX5000 routers, PTX10000 line of routers, and QFX5100 andQFX5200 switches are supported.
Starting in Junos OS Evolved Release 21.4R1, streaming statistics bymeans of gRPC and gNMI is supported on PTX10001-36MR,PTX10004, and PTX10008 routers.
The following paths are also supported:
• :/components/component[name='FPC0:CC0']/properties/property[name='ts-input-packets']/
• /components/component[name='FPC0:CC0']/properties/property[name='ts-output-packets']/
• //components/component[name='FPC0:CC0']/properties/property[name='ts-input-packets-pps']/
• /components/component[name='FPC0:CC0']/properties/property[name='ts-output-packets-pps']/
• /components/component[name='FPC0:CC0']/properties/property[name='ts-fabric-input-packets']/
109
Table 4: gRPC Sensors (Continued)
resource path Description
• /components/component[name='FPC0:CC0']/properties/property[name='ts-fabric-input-packets-pps']/
• /components/component[name='FPC0:CC0']/properties/property[name='ts-fabric-output-packets']/
• /components/component[name='FPC0:CC0']/properties/property[name='ts-fabric-output-packets-pps']/
• /components/component[name='FPC0:CPU0']/properties/property[name='lts-input-packets']/
• /components/component[name='FPC0:CPU0']/properties/property[name='lts-output-packets']/
• /components/component[name='FPC0:CPU0']/properties/property[name='lts-sw-input-control-drops']/
• /components/component[name='FPC0:CPU0']/properties/property[name='lts-sw-input-high-drops']/
• /components/component[name='FPC0:CPU0']/properties/property[name='lts-sw-input-medium-drops']/
• /components/component[name='FPC0:CPU0']/properties/property[name='lts-sw-input-low-drops']/
• /components/component[name='FPC0:CPU0']/properties/property[name='lts-sw-output-low-drops']/
• /components/component[name='FPC0:CPU0']/properties/property[name='lts-hw-input-drops']/
• /components/component[name='FPC0:NPU0']/properties/property[name='hwdsNormal']/
• /components/component[name='FPC0:NPU0']/properties/property[name='hwds-data-error']/
• /components/component[name='FPC0:NPU0']/properties/property[name='hwds-tcp-error']/
110
Table 4: gRPC Sensors (Continued)
resource path Description
• /components/component[name='FPC0:NPU0']/properties/property[name='hwds-illegal-nh']/
• /components/component[name='FPC0:NPU0']/properties/property[name='hwds-invalid-iif']/
//components/component[name='FPC0:NPU0']/properties/property[name='hwds-fabric']/
111
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/services/segment-routing/interface/ingress/usage/
/junos/services/segment-routing/interface/egress/usage/
/junos/services/segment-routing/sid/usage/
Sensors for aggregate segment routing traffic with IS-IS.
This sensor is supported on MX Series and PTX5000 routers startingwith Junos OS Release 17.4R1.
Starting with Junos OS Release 19.2R1, MX960, MX2008, MX2010and MX2020 routers, PTX1000 and PTX10000 routers, andQFX5100 and QFX5200 switches are supported on gRPC and gNMIservices.
Statistics are exported separately for each routing instance.
The first path exports inbound traffic. The second path exportsoutbound traffic. The third path exports inbound segment routingtraffic for each segment identifier.
NOTE: When you enable a sensor for segment routing statistics, youmust also configure the sensor-based-stats statement at the [editprotocols isis source-packet-routing] hierarchy level.
All MX and PTX5000 routers with FPC3 onwards support enhancedmode. If enhanced mode is not enabled, configure either theenhanced-ip statement or the enhanced-ethernet statement at the [editchassis network-services] hierarchy level. On PTX Series routers,configure the enhanced-mode statement at the [edit chassis network-services] hierarchy level.
NOTE: Currently, MPLS labels correspond only to only one instance,instance 0. Since each SID corresponds to a singleinstance_identifier, no aggregation is required to be done by thecollector. The instance_identifier is stamped as 0.
The following OpenConfig paths are supported:
• /network-instances/network-instance/mpls/signaling-protocols/segment-routing/interfaces/interface/state/in-pkts
• /network-instances/network-instance/mpls/signaling-protocols/segment-routing/interfaces/interface/state/in-octets
• /network-instances/network-instance/mpls/signaling-protocols/segment-routing/interfaces/interface/state/out-octets
112
Table 4: gRPC Sensors (Continued)
resource path Description
• /network-instances/network-instance/mpls/signaling-protocols/segment-routing/interfaces/interface/state/out-pkts
• /network-instances/network-instance/mpls/aggregate-sid-counters/aggregate-sid-counter/state/in-octets
• /network-instances/network-instance/mpls/aggregate-sid-counters/aggregate-sid-counter/state/in-pkts
• /network-instances/network-instance/mpls/aggregate-sid-counters/aggregate-sid-counter/state/out-octets
• /network-instances/network-instance/mpls/aggregate-sid-counters/aggregate-sid-counter/state/out-pkts
• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/state/in-octets
• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/state/in-pkts
• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/state/out-octets
• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/state/out-pkts
• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/forwarding-classes/forwarding-class/state/in-octets
• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/forwarding-classes/forwarding-class/state/in-pkts
• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/forwarding-classes/forwarding-class/state/out-octets
• /network-instances/network-instance/mpls/interfaces/interface/sid-counters/sid-counter/forwarding-classes/forwarding-class/state/out-pkts
113
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/services/segment-routing/sid/usage/ Sensors for aggregate segment routing traffic with IS-IS.
This sensor is supported on PTX3000 routers and PTX5000 routerswith FPC2 starting with Junos OS Release 19.1R1.
Statistics are exported separately for each routing instance.
The first path exports inbound traffic. The second path exportsoutbound traffic. The third path exports inbound segment routingtraffic for each segment identifier.
NOTE: When you enable a sensor for segment routing statistics, youmust also configure the sensor-based-stats statement at the [editprotocols isis source-packet-routing] hierarchy level.
/junos/services/segment-routing/traffic-engineering/ingress/usage
Packet Forwarding Engine sensor for ingress segment routing trafficengineering statistics.
Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 andMX2020 routers, PTX1000 and PTX10000 routers, and QFX5100and QFX5200 switches are supported on gRPC and gNMI services.
Starting in Junos OS Evolved Release 21.4R1,PTX10001-36MR,PTX10003, PTX10004, PTX10008,and PTX10016 routers aresupported on gRPC and gNMI services.
/junos/services/segment-routing/traffic-engineering/transit/usage
Packet Forwarding Engine sensor for ingress segment routing trafficengineering statistics.
Starting in Junos OS Release 19.2R1, MX960, MX2008, MX2010 andMX2020 routers, PTX1000 and PTX10000 routers, and QFX5100and QFX5200 switches are supported on gRPC and gNMI services.
Starting in Junos OS Evolved Release 21.4R1,PTX10001-36MR,PTX10003, PTX10004, PTX10008,and PTX10016 routers aresupported on gRPC and gNMI services.
114
Table 4: gRPC Sensors (Continued)
resource path Description
/junos/services/segment-routing/traffic-engineering/tunnel/lsp/ingress/usage/
/junos/services/segment-routing/traffic-engineering/tunnel/lsp/transit/usage/
Sensor for Segment Routing Traffic Engineering (SR-TE) per LabelSwitched Path (LSP) route statistics.
You can stream SR-TE telemetry statistics for uncolored SR-TEpolicies to an outside collector. Ingress statistics include statistics forall traffic steered by means of an SR-TE LSP. Transit statistics includestatistics for traffic to the Binding-SID (BSID) of the SR-TE policy.
To enable these statistics, include the per-source per-segment-listoption at the [edit protocols source-packet-routing telemetrystatistics] hierarchy level.
Starting in Junos OS Release 20.1R1, MX Series and PTX Seriesrouters support streaming statistics using gRPC services.
Starting in Junos OS Release 20.2R1, MX240. MX480, MX960,MX2010, and MX2020 with MPC-10E or MPC-11E routers supportstreaming statistics using gRPC services.
When a subscription is made to these resource paths, the followingoutput format is displayed:
• /mpls/signaling-protocols/segment-routing/sr-te-per-lsp-ingress-policies/sr-te-ingress-lsp-policy\[tunnel-name='srtelsp1' andsource='st' and origin='0' and distinguisher='f' and lsp-name='sr1'\]/state/counters\[name='.*'\]/packets
• /mpls/signaling-protocols/segment-routing/sr-te-per-lsp-transit-policies/sr-te-transit-lsp-policy\[tunnel-name='srtelsp1' andsource='st' and origin='0' and distinguisher='f' and lsp-name='sr1'\]/state/counters\[name='.*'\]/packets
For the output format above, the field source, values can be ST (statictunnel) or PC (PCEP tunnel). For the field lsp-name, the value is thetransit output. Other fields, such as Origin and Distinguisher are fixedfor uncolored tunnels.
115
Table 4: gRPC Sensors (Continued)
resource path Description
/system/alarms/alarm INITIAL_SYNC support for OpenConfig data model openconfig-platform.yang and openconfig-alarms.yang. This feature lets thecollector have a complete view of the current state of every sensor itis subscribed to. INITIAL_SYNC requires that at least one copy of allthe sensors be sent to the collector.
Starting in Junos OS Evolved Release 21.4R1, streaming statistics bymeans of gRPC and gNMI is supported on PTX10001-36MR,PTX10003, PTX10004, PTX10008, and PTX10016 routers.
Table 5: Broadband Edge gRPC Sensors
resource path Description
/junos/system/subscriber-management/chassis/virtual-chassis-ports/virtual-chassis-port
/junos/system/subscriber-management/chassis/virtual-chassis-ports/virtual-chassis-port[vcp-interface-name=vcp-interface-port-string] (tospecify the interface name)
Virtual chassis port counter sensor.
The sensor includes these statistics:
• Input packets
• Output packets
• Input bytes
• Output bytes
Starting with Junos OS Release 20.2R1, streaming statistics from avirtual chassis is supported using gRPC services with MX480,MX960, MX10003, MX2010, and MX2020 routers.
116
Table 5: Broadband Edge gRPC Sensors (Continued)
resource path Description
/junos/system/subscriber_management/dynamic-interfaces/interface-sets/meta-data/interface[sid-id='sid-value']/
Sensor for subscriber interface information.
ON-CHANGE streaming is supported.
The following end paths are supported:
• interface-index-The system assigned interface index for theinterface.
• session-type-The type of client session (e.g VLAN, DHCP, PPPoE).
• user-name-The login name for this interface and session.
• profile-name-The name of the client profile used to create theinterface.
• underlying-interface-name-The name of the associated underlyinginterface.
• cvlan-tag-The innermost VLAN tag value associated with theinterface.
• svlan-tag-The outermost VLAN tag value associated with theinterface.
117
Table 5: Broadband Edge gRPC Sensors (Continued)
resource path Description
/junos/system/subscriber_management/dynamic-interfaces/interface-sets/meta-data/interface[sid-id='sid-value']/
Sensor for actual accounting statistics for dynamic subscriberinterfaces.
The following end paths are supported:
• ip-in-packets-The number of actual transit IPv4 & IPv6 packetsreceived by the interface.
• ip-out-packets-The number of actual transit IPv4 & IPv6 packetssent to the interface.
• ip-in-bytes-The number of actual transit IPv4 & IPv6 bytesreceived by the interface.
• ip-out-bytes-The number of actual transit IPv4 & IPv6 bytesreceived by the interface.
• ipv6-in-packets-The number of actual transit IPv6 packetsreceived by the interface.
• ipv6-out-packets-The number of actual transit IPv6 packets sentto the interface.
• ipv6-in-bytes-The number of actual transit IPv6 bytes receivedby the interface.
• ipv6-out-bytes-The number of actual transit IPv6 bytes sent tothe interface.
/junos/system/linecard/ddos/ This PFE sensor exports the statistics of DDOS from MPC1, MPC2,MPC3, MPC5, MPC6, MPC7, MPC8, and MPC9 line cards.
Release History Table
Release Description
20.3R1 Starting with Junos OS Release 20.3R1, gRPC service for exporting LDP and mLDP statistics issupported on MPC10E-10C-MRATE, MPC10E-15C-MRATE, and MX2K-MPC11E line cards.
20.2R1 Starting with Junos OS Evolved Release 20.2R1, gRPC service for streaming NDP statistics issupported on PTX10001 routers.
118
20.2R1 Starting with Junos OS Release 20.2R1, gRPC service for streaming Packet forwarding Engine andRouting Engine statistics is supported on EX2300, EX2300-MP, and EX3400 switches.
20.2R1 Starting with Junos OS Release 20.2R1, gRPC service for streaming BGP routing information base(RIB) and BGP peer statistics is supported on any platform family that supports containerizedrouting protocol process (cRPD). cRPD is Juniper’s routing protocol process (rpd) decoupled fromJunos OS and packaged as a Docker container to run in Linux-based environments.
20.2R1 Starting with Junos OS Release 20.2R1, ON_CHANGE BGP peer statistics export using gRPCservices and gNMI services is supported on MX960, MX2008, MX2010, MX2020, PTX1000,PTX5000, PTX10000 routers and QFX5100 and QFX5200 switches.
20.2R1 Starting with Junos OS Release 20.2R1, streaming BGP global, peer and perr groups statistics usinggRPC services is supported on EX2300, EX3400, EX4300, EX4600, and EX9200 switches.
20.2R1 Starting with Junos OS Release 20.2R1, streaming revenue interface statistics through PacketForwarding Engine sensors and pseudo interface statistics through Routing Engine sensors usinggRPC services and gNMI services is supported on SRX5400, SRX5600, and SRX5800 ServicesGateways..
20.2R1 Starting with Junos OS Release 20.2R1, streaming revenue interface statistics through PacketForwarding Engine sensors and pseudo interface statistics through Routing Engine sensors usinggRPC services and gNMI services is supported on SRX5400, SRX5600, and SRX5800 ServicesGateways.
20.2R1 Starting with Junos OS Release 20.2R1 sensors to stream standby Routing Engine statistics aresupported on MX480, MX960, MX10003, MX2010, and MX2020 routers.
20.2R1 Starting with Junos OS Release 20.2R1 sensors to stream EVPN statistics using gRPC services aresupported with QFX5100, QFX5110, QFX5120, QFX5200, QFX10002-60C, QFX10002,QFX10008, and QFX10016 switches.
20.2R1 Starting with Junos OS Release 20.2R1, gRPC service for exporting LDP and mLDP statistics issupported on MX Series routers.
20.1R1 Starting with Junos Release 20.R1, gNMI service for streaming telemetry sensors for PacketForwarding Engine statistics is supported on MX2K-MPC11E line cards on MX2010 and MX2020routers.
19.4R1 Starting with Junos OS Release 19.4R1, gRPC service for streaming Packet Forwarding Engine andRouting Engine statistics is supported on EX4300-MP switches.
119
19.3R1 Starting with Junos OS Release 19.3R1, gNMI services for streaming Packet Forwarding Enginestatistics is supported on MX240, MX480 and MX960 routers.
19.3R1 Starting with Junos OS Release 19.3R1, gRPC service for exporting statistics is supported on MXSeries routers hosting MPC10E-10C-MRATE and MPC10E-15C-MRATE line cards. The resourcepaths /junos/system/linecard/cpu/memory/, /junos/system/linecard/npu/memory/, and /junos/system/linecard/npu/utilization/ can be updated to call out individual sensors (leaves) and theirrespective paths for better clarity.
19.3R1 Starting with Junos OS Evolved Release 19.3R1, gRPC service for exporting statistics is supportedon QFX5220-128C and QFX5220-32CD switches.
19.2R1 Starting with Junos OS Release 19.2R1, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600,SRX5800, and vSRX Series Services Gateways.are supported.
19.2R1 Starting with Junos OS Release 19.2R1, gNMI services for streaming Packet Forwarding Enginestatistics is supported on MX960, MX2008, MX2010 and MX2020 routers, PTX1000 andPTX10000 routers, and QFX5100 and QFX5200 switches.
19.2R1 Starting with Junos OS Release 19.2R1, gNMI services for streaming statistics is supported onQFX5110, QFX5120, QFX5200 and QFX5210 switches.
19.2R1 Starting with Junos OS Release 19.3R1, gNMI services for streaming and ON_CHANGE export ofRouting Engine statistics is supported on MX960, MX2010, MX2020, PTX5000, PTX1000, andPTX10000 routers.
19.1R1 EVO Starting in Junos OS Evolved Release 19.1R1, OpenConfig (OC) and Junos Telemetry Interface (JTI)are supported. Both gRPC APIs and the customer-facing CLI remain the same as for the Junos OS.As was standard for Junos OS, Network Agent (NA) and OC packages are part of the Junos OSEvolved image.
19.1R1 Starting with Junos OS Evolved 19.1R1, Packet Forwarding Engine sensors on PTX10003 routers arealso supported.
18.4R1 Starting with Junos OS Release 18.4R1, MX480, MX960, MX2010, MX2020, MX2008 and MX-ELMrouters are also supported.
18.3R1 Starting with Junos OS Release 18.3R1, ON_CHANGE streaming of LLDP telemetry sensorinformation is supported through gRPC for MX Series and PTX Series routers.
18.3R1 Starting with Junos OS Release 18.3R1, QFX5120-AY and EX4650 switches are also supported.
120
18.3R1 Starting with Junos OS Release 18.4R1, EX4600 switches are also supported.
18.2R1 Starting with Junos OS Release 18.2R1, PTX10002 routers are also supported.
18.1R1 Starting with Junos OS Release 18.1R1, QFX5210-64C switches and QFX5100 switches are alsosupported.
18.1R1 Starting with Junos OS Release 18.1R1, ON_CHANGE streaming of ARP, ND, and IP sensorinformation associated with interfaces is supported through gRPC for MX Series routers and PTXSeries routers.
17.4R1 Starting with Junos OS Release 17.4R1, PTX10016 routers and virtual MX Series (vMX) routers arealso supported.
17.3R1 Starting with Junos OS Release 17.3R1, QFX5110 switches, EX4600, EX4600-VC, and EX9200switches and the Routing and Control Board (RCB) on PTX3000 routers are also supported.
17.3R1 Starting with Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensors are supported.
17.3R1 In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’] /server/statistics/ the only value supported for routing-instance-name is default.
17.3R1 In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-ancpinstance[ri-name=’ routing-instance-name’] /server/statistics/ the onlyvalue supported for routing-instance-name is default.
17.3R1 In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v4/routing-instances/routing-instance[ri-name=’ routing-instance-name’]/relay/statistics/ the only value supported for the value routing-instance-name isdefault.
17.3R1 In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v6/ routing-instances/routing-instance[ri-name=’ routing-instance-name’]/server/statistics the only value supported for routing-instance-name is default.
17.3R1 In Junos OS Release 17.3R1, broadband edge (BBE) gRPC sensor /junos/system/subscriber-management/client-protocols/dhcp/v6/ routing-instances/routing-instance[ri-name=’ routing-instance-name’]/relay/statistics the only value supported for routing-instance-name is default.
17.2R1 Starting with JunosOS Release 17.2R1, QFX10002, QFX10008, and QFX10016 switches, QFX5200switches, and PTX1000 and PTX10008 routers are also supported.
121
16.1R3 Starting with Junos OS Release 16.1R3, the Junos Telemetry Interface supports gRPC remoteprocedure calls (gRPC) to provision sensors and to subscribe to and receive telemetry data on MXSeries routers and PTX3000 and PTX5000 routers.
RELATED DOCUMENTATION
Understanding OpenConfig and gRPC on Junos Telemetry Interface
122
3CHAPTER
OpenConfig to Junos Mapping
Mapping OpenConfig AAA Commands to Junos Operation | 124
Mapping OpenConfig BGP Commands to Junos Configuration | 129
Mapping OpenConfig Interface Commands to Junos Configuration | 152
Mapping OpenConfig LLDP Commands to Junos Configuration | 159
Mapping OpenConfig Local Routing Commands to Junos Configuration | 160
Mapping OpenConfig MPLS Commands to Junos Configuration | 162
Mapping OpenConfig Network Instance Commands to Junos Operation | 178
Mapping OpenConfig Routing Policy Commands to Junos Configuration | 183
Mapping OpenConfig System Logging Model Commands to Junos Configuration | 188
Mapping OpenConfig System Management Model Commands to JunosConfiguration | 191
Mapping OpenConfig System Model Commands to Junos Configuration | 194
Mapping OpenConfig System Terminal Model Commands to Junos Configuration | 199
Mapping OpenConfig VLAN Commands to Junos Configuration | 204
Mapping OpenConfig AAA Commands to JunosOperation
NOTE: See "OpenConfig Data Model Version" on page 3 topic to understand the data modelssupported version and its Junos OS release for Juniper Networks ACX Series, EX Series, MXSeries, PTX Series, and QFX Series.
The following tables show the mapping of OpenConfig AAA commands with the relevant configurationin Junos OS.
Table 6: Global AAA Configuration
CommandName
OpenConfig Command Path Junos Configuration
Command path prefix:
/system/aaa
Config-Name /server-groups/server-group/config/name
Not supported
NOTE: There is no equivalent configuration in the Junos OSfor this path. The configured server group name is used inthe RADIUS/TACACS attributes configuration.
Server-Config-Address
/server-groups/server-group/servers/server/config/address
Not supported
NOTE: There is no equivalent configuration in the Junos OSfor this path. The configured server address is used in theRADIUS/TACACS attributes configuration.
Server-Config-Name
/server-groups/server-group/servers/server/config/name
Not supported
NOTE: There is no equivalent configuration in the Junos OSfor this path. You can configure a server name to identify theserver.
124
Table 6: Global AAA Configuration (Continued)
CommandName
OpenConfig Command Path Junos Configuration
Config-Timeout /server-groups/server-group/servers/server/config/timeout
Not supported
NOTE: There is no equivalent configuration in the Junos OSfor this path. However, the timeout configured is derivedfrom the timeout parameter at the Junos OS edit radius-server or edit tacplus-server hierarchy level.
Table 7: RADIUS Server Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
/system/aaa
Auth-Port /server-groups/server-group/servers/server/radius/config/auth-port
set system radius-server addressport port
NOTE: The address value isderived from the value configuredafter server. The port value is thesame value as auth-port.
Retransmit-Attempts /server-groups/server-group/servers/server/radius/config/retransmit-attempts
set system radius-server addressretryretry
NOTE: The address value isderived from the value configuredafter server. The retry value is thesame value as that specified forretransmit-attempts.
125
Table 7: RADIUS Server Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Secret-Key /server-groups/server-group/servers/server/radius/config/secret-key
set system radius-server addresssecret secret
NOTE: The address value isderived from the value configuredafter server. The secret value isthe same value as that specifiedfor secret-key.
Source-Address /server-groups/server-group/servers/server/radius/config/source-address
set system radius-server addresssource-address source-address
NOTE: The address value isderived from the value configuredafter server. The source-addressvalue is the same value as thatspecified for source-address.
Table 8: TACACS Server Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
/system/aaa
Config-Port /server-groups/server-group/servers/server/tacacs/config/port
set system tacplus-server addressport port
NOTE: The address value isderived from the valueconfigured after server. The portvalue is the same value as thatspecified for port.
126
Table 8: TACACS Server Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Secret-Key /server-groups/server-group/servers/server/tacacs/config/secret-key
set system tacplus-server addresssecret secret
NOTE: The address value isderived from the valueconfigured after server. Thesecret value is the same value asthat specified for secret-key.
Source-Address /server-groups/server-group/servers/server/tacacs/config/source-address
set system tacplus-server addresssource-address source-address
NOTE: The address value isderived from the valueconfigured after server. Thesource-address value is the samevalue as that specified for source-address.
Table 9: AAA Admin and User Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
/system/aaa
Admin-Password /authentication/admin-user/config/admin-password
set system root-authenticationplain-text-password
NOTE: The plain-text-password-authentication value is derivedfrom the value configured foradmin-password.
127
Table 9: AAA Admin and User Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Admin-Password-Hashed /authentication/admin-user/config/admin-password-hashed
set system root-authenticationencrypted-password encrypted-password
NOTE: The encrypted-passwordvalue is derived from the valueconfigured for admin-password-hashed.
Authentication-Method /authentication/config/authentication-method
set system authentication-order
NOTE: The authentication-ordervalue is derived from the valueconfigured for authentication-method.
Password /authentication/users/user/config/password set system login user user-nameauthentication plain-text-passwordplain-text-password
NOTE: The user-name value isderived from the value configuredfor user. The plain-text-passwordvalue is derived from the valueconfigured for password.
Password-Hashed /authentication/users/user/config/password-hashed
set system login user user-nameauthentication encrypted-passwordencrypted-password
NOTE: The user-name value isderived from the value configuredfor user. The encrypted-passwordvalue is derived from the valueconfigured for password-hashed.
128
Table 9: AAA Admin and User Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Role /authentication/users/user/config/role set system login user user-nameclass class
NOTE: The user-name value isderived from the value configuredfor user. The class value is derivedfrom the value configured for role.
Username /authentication/users/user/config/username Not supported
NOTE: There is no equivalentconfiguration in the Junos OS.
Mapping OpenConfig BGP Commands to JunosConfiguration
NOTE: See "OpenConfig Data Model Version" on page 3 topic to understand the data modelssupported version and its Junos OS release for Juniper Networks MX Series, PTX Series, andQFX Series.
Table 10 on page 129 to Table 24 on page 148 show the mapping of OpenConfig BGP commands withthe relevant configuration in Junos.
Table 10: Global BGP Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
/network-instances/network-instance/protocols/protocol/bgp/global
129
Table 10: Global BGP Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
As /config/as set routing-options autonomous-systemas_number
Router-ID /config/router-id set routing-options router-id router-id
Confederation /confederation/config/identifier /confederation/config/member-as
set routing-options confederationconfederation_as set routing-optionsconfederation members value
Always-Compare-MED
/route-selection-options/config/always-compare-med
set protocols bgp path-selection always-compare-med
Ignore-AS-Path-Length
/route-selection-options/config/ignore-as-path-length
set protocols bgp path-selection as-path-ignore
Enable-AIGP /route-selection-options/config/enable-aigp
set protocols bgp family family aigp
Ignore-Nexthop-IGP-Metric
/route-selection-options/config/ignore-next-hop-igp-metric
Not supported
Dynamic-Neighbor-Prefixes
/dynamic-neighbor-prefixes/dynamic-neighbor-prefix/config/prefix /dynamic-neighbor-prefixes/dynamic-neighbor-prefix/config/peer-group
set protocols bgp group group allow ipaddress
Graceful-Restart /graceful-restart/config/enabled /graceful-restart/config/restart-time /graceful-restart/config/stale-routes-time /graceful-restart/config/helper-only
set protocols bgp graceful-restartdisable set protocols bgp graceful-restart restart-time restart -time setprotocols bgp graceful-restart stale-routes-time stale- routes -time
130
Table 11: AFI-SAFI Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
• Global—/network-instances/network-instance/ protocols/protocol/bgp/global/afi-safi/afi-safi
• Peer-Group—/network-instances/network-instance/ protocols/protocol/bgp/peer-groups/ peer-group/afi-safi/afi-safi
• Neighbors—/network-instances/network-instance/ protocols/protocol/bgp/neighbors/ neighbor/afi-safi/afi-safi
Set the values for address family:protocol/bgp/global/afi-safi/afi-safi/ <afi-safi-name>/<family-type>/config
131
Table 11: AFI-SAFI Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Where, afi-safi-name is one of thefollowing:
• IPV4_LABELED_UNICAST LabeledIPv4 unicast (AFI,SAFI = 1,4)
• IPV4_MULTICAST Base identify typefor IPv4 multicast address family
• IPV4_UNICAST IPv4 unicast (AFI,SAFI= 1,1)
• IPV6_LABELED_UNICAST LabeledIPv6 unicast (AFI,SAFI = 2,4)
• IPV6_MULTICAST Base identify typefor IPv6 multicast address family
• IPV6_UNICAST IPv6 unicast (AFI,SAFI= 2,1)
• L2VPN_EVPN BGP MPLS BasedEthernet VPN (AFI,SAFI = 25,70)
• L2VPN_VPLS BGP-signalled VPLS(AFI,SAFI = 25,65)
• L3VPN_IPV4_MULTICAST MulticastIPv4 MPLS L3VPN (AFI,SAFI = 1,129)
• L3VPN_IPV4_UNICAST Unicast IPv4MPLS L3VPN (AFI,SAFI = 1,128)
• L3VPN_IPV6_MULTICAST MulticastIPv6 MPLS L3VPN (AFI,SAFI = 2,129)
• L3VPN_IPV6_UNICAST Unicast IPv6MPLS L3VPN (AFI,SAFI = 2,128)
132
Table 11: AFI-SAFI Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Where, family-type is one of the following:
• ipv4-labeled-unicast IPv4 LabeledUnicast configuration options
• ipv4-unicast IPv4 unicast configurationoptions
• ipv6-labeled-unicast IPv6 LabeledUnicast configuration options
• ipv6-unicast IPv6 unicast configurationoptions
• l2vpn-evpn BGP EVPN configurationoptions
• l2vpn-vpls BGP-signalled VPLSconfiguration options
• l3vpn-ipv4-multicast Multicast IPv4L3VPN configuration options
• l3vpn-ipv4-unicast Unicast IPv4L3VPN configuration options
• l3vpn-ipv6-multicast Multicast IPv6L3VPN configuration options
• l3vpn-ipv6-unicast Unicast IPv6L3VPN configuration options
AFI-SAFI /config/afi-safi-name/config/enabled
set protocols bgp family family
Add-Path: Send /add-paths/config/send set protocols bgp group group-namefamily family add-path send path-count number
133
Table 11: AFI-SAFI Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Add-Paths: Receive /add-paths/config/receive set protocols bgp group group-namefamily family add-path receive
Add-Paths: Send-Max /add-paths/config/send-max
NOTE: You must set send-max to non-zerovalue before setting send to true. If not,you will receive an error message to setthe correct values.
set protocols bgp group group-namefamily family add-path send path-count path-count
Add-Paths: Eligible PrefixPolicy
/add-paths/config/eligible-prefix-policy set protocols bgp group group-namefamily family add-path sendprefix-policy policy
Always-Compare-MED /route-selection-options/config/always-compare-med
set protocols bgp path-selectionalways-compare-med
Ignore-AS-Path-Length /route-selection-options/config/ignore-as-path-length
set protocols bgp path-selectionas-path-ignore
Enable-AIGP /route-selection-options/config/enable-aigp
set protocols bgp family familyaigp
Use-Multiple-Paths:Maximum-Paths
/use-multiple-paths/ebgp/config/maximum-paths /use-multiple-paths/ibgp/config/maximum-paths
set chassis maximum-ecmp <num-next-hops>
Use-Multiple-Paths: Allow-Multiple-AS
/use-multiple-paths/ebgp/config/allow-multiple-as
set protocols bgp group group-namemultipath multiple-as
134
Table 12: AFI-SAFI IPv4-Unicast Prefix-Limit Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
• Global—/network-instances/network-instance/ protocols/protocol/bgp/global/afi-safi/ afi-safi-name/<afi-safi-name>/ipv4-unicast
• Peer-Group—/network-instances/network-instance/ protocols/protocol/bgp/peer-groups/ peer-group/afi-safi/afi-safi-name/<afi-safi-name>/ ipv4-unicast
• Neighbors—/network-instances/network-instance/ protocols/protocol/bgp/neighbors/ neighbor/afi-safi/afi-safi-name/<afi-safi-name>/ipv4-unicast
Send-Default-Route /config/send-default-route Not supported
Max-Prefixes /prefix-limit/config/max-prefixes set protocols bgp family inetunicast accepted-prefix-limitmaximum maximum
Prevent-Teardown /prefix-limit/config/prevent-teardown set protocols bgp family familyprefix-limit teardown
Shutdown-Threshold-PCT /prefix-limit/config/shutdown-threshold-pct set protocols bgp family inetunicast accepted-prefix-limitteardown limit-threshold
Restart-Timer /prefix-limit/config/restart-timer set protocols bgp family inetunicast accepted-prefix-limitteardown idle-timeout timeout
135
Table 13: AFI-SAFI IPv6-Unicast Prefix-Limit Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
• Global—/network-instances/network-instance/ protocols/protocol/bgp/global/afi-safi/ afi-safi-name/<afi-safi-name>/ipv6-unicast
• Peer-Group—/network-instances/network-instance/ protocols/protocol/bgp/peer-groups/ peer-group/afi-safi/afi-safi-name/<afi-safi-name>/ipv6-unicast
• Neighbors—/network-instances/network-instance/ protocols/protocol/bgp/neighbors/ neighbor/afi-safi/afi-safi-name/<afi-safi-name>/ipv6-unicast
Send-Default-Route /config/send-default-route Not supported
Max-Prefixes /prefix-limit/config/max-prefixes set protocols bgp family inet6unicast accepted-prefix-limitmaximum maximum
Prevent-Teardown /prefix-limit/config/prevent-teardown set protocols bgp family familyprefix-limit teardown
Shutdown-Threshold-PCT /prefix-limit/config/shutdown-threshold-pct set protocols bgp family inet6unicast accepted-prefix-limitteardown limit-threshold
Restart-Timer /prefix-limit/config/restart-timer set protocols bgp family inet6unicast accepted-prefix-limitteardown idle-timeout timeout
136
Table 14: AFI-SAFI IPv4-Lbl-Unicast Prefix-Limit Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
• Global—/network-instances/network-instance/ protocols/protocol/bgp/global/afi-safi/ afi-safi-name/<afi-safi-name>/ipv4-labelled-unicast/ prefix-limit
• Peer-Group—/network-instances/network-instance/ protocols/protocol/bgp/peer-groups/ peer-group/afi-safi/afi-safi-name/<afi-safi-name>/ ipv4-labelled-unicast/prefix-limit
• Neighbors—/network-instances/network-instance/ protocols/protocol/bgp/neighbors/ neighbor/afi-safi/afi-safi-name/<afi-safi-name>/ipv4-labelled-unicast/prefix-limit
Max-Prefixes /config/max-prefixes set protocols bgp family inetlabeled-unicast accepted-prefix-limit maximum maximum
Prevent-Teardown /config/prevent-teardown set protocols bgp family familyprefix-limit teardown
Shutdown-Threshold-PCT /config/shutdown-threshold-pct set protocols bgp family inetlabeled-unicast accepted-prefix-limit teardown limit-threshold
Restart-Timer /config/restart-timer set protocols bgp family inetlabeled-unicast accepted-prefix-limit teardown idle-timeouttimeout
137
Table 15: AFI-SAFI IPv6-Lbl-Unicast Prefix-Limit Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
• Global—/network-instances/network-instance/ protocols/protocol/bgp/global/afi-safi/ afi-safi-name/<afi-safi-name>/ipv6-labelled-unicast/ prefix-limit
• Peer-Group—/network-instances/network-instance/ protocols/protocol/bgp/peer-groups/ peer-group/afi-safi/afi-safi-name/<afi-safi-name>/ ipv6-labelled-unicast/prefix-limit
• Neighbors—/network-instances/network-instance/ protocols/protocol/bgp/neighbors/ neighbor/afi-safi/afi-safi-name/<afi-safi-name>/ipv6-labelled-unicast/prefix-limit
Max-Prefixes /config/max-prefixes set protocols bgp family inet6labeled-unicast accepted-prefix-limit maximum maximum
Prevent-Teardown /config/prevent-teardown set protocols bgp family familyprefix-limit teardown
Shutdown-Threshold-PCT /config/shutdown-threshold-pct set protocols bgp family inet6labeled-unicast accepted-prefix-limit teardown limit-threshold
Restart-Timer /config/restart-timer set protocols bgp family inet6labeled-unicast accepted-prefix-limit teardown idle-timeouttimeout
138
Table 16: AFI-SAFI L3VPN-IPv4-Ucast Prefix-Limit Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
• Global—/network-instances/network-instance/ protocols/protocol/bgp/global/afi-safi/ afi-safi-name/<afi-safi-name>/l3vpn-ipv4-unicast/ prefix-limit
• Peer-Group—/network-instances/network-instance/ protocols/protocol/bgp/peer-groups/ peer-group/afi-safi/afi-safi-name/<afi-safi-name>/ l3vpn-ipv4-unicast/prefix-limit
• Neighbors—/network-instances/network-instance/ protocols/protocol/bgp/neighbors/ neighbor/afi-safi/afi-safi-name/<afi-safi-name>/l3vpn-ipv4-unicast/prefix-limit
Max-Prefixes /config/max-prefixes set protocols bgp family inet-vpnunicast accepted-prefix-limitmaximum maximum
Prevent-Teardown /config/prevent-teardown set protocols bgp family familyprefix-limit teardown
Shutdown-Threshold-PCT /config/shutdown-threshold-pct set protocols bgp family inet-vpnunicast accepted-prefix-limitteardown limit-threshold
Restart-Timer /config/restart-timer set protocols bgp family inet-vpnunicast accepted-prefix-limitteardown idle-timeout timeout
139
Table 17: AFI-SAFI L3VPN-IPv6-Ucast Prefix-Limit Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
• Global—/network-instances/network-instance/ protocols/protocol/bgp/global/afi-safi/ afi-safi-name/<afi-safi-name>/ l3vpn-ipv6-unicast/prefix-limit
• Peer-Group—/network-instances/network-instance/ protocols/protocol/bgp/peer-groups/ peer-group/afi-safi/afi-safi-name/<afi-safi-name>/ l3vpn-ipv6-unicast/prefix-limit
• Neighbors—/network-instances/network-instance/ protocols/protocol/bgp/neighbors/neighbor/ afi-safi/afi-safi-name/<afi-safi-name>/l3vpn-ipv6-unicast/prefix-limit
Max-Prefixes /config/max-prefixes set protocols bgp family inet6-vpnunicast accepted-prefix-limitmaximum maximum
Prevent-Teardown /config/prevent-teardown set protocols bgp family familyprefix-limit teardown
Shutdown-Threshold-PCT /config/shutdown-threshold-pct set protocols bgp family inet6-vpnunicast accepted-prefix-limitteardown limit-threshold
Restart-Timer /config/restart-timer set protocols bgp family inet6-vpnunicast accepted-prefix-limitteardown idle-timeout timeout
140
Table 18: AFI-SAFI L3VPN-IPv4-Mcast Prefix-Limit Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
• Global—/network-instances/network-instance/ protocols/protocol/bgp/global/afi-safi/ afi-safi-name/<afi-safi-name>/ l3vpn-ipv4-multicast/prefix-limit
• Peer-Group—/network-instances/network-instance/ protocols/protocol/bgp/peer-groups/ peer-group/afi-safi/afi-safi-name/<afi-safi-name>/ l3vpn-ipv4-multicast/prefix-limit
• Neighbors—/network-instances/network-instance/ protocols/protocol/bgp/neighbors/ neighbor/afi-safi/afi-safi-name/<afi-safi-name>/l3vpn-ipv4-multicast/prefix-limit
Max-Prefixes /config/max-prefixes set protocols bgp family inet-vpnmulticast accepted-prefix-limitmaximum maximum
Prevent-Teardown /config/prevent-teardown set protocols bgp family familyprefix-limit teardown
Shutdown-Threshold-PCT /config/shutdown-threshold-pct set protocols bgp family inet-vpnmulticast accepted-prefix-limitmaximum maximum
Restart-Timer /config/restart-timer set protocols bgp family inet-vpnmulticast accepted-prefix-limitteardown idle-timeout timeout
141
Table 19: AFI-SAFI L3VPN-IPv6-Mcast Prefix-Limit Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
• Global—/network-instances/network-instance/ protocols/protocol/bgp/global/afi-safi/ afi-safi-name/<afi-safi-name>/ l3vpn-ipv6-multicast/prefix-limit
• Peer-Group—/network-instances/network-instance/ protocols/protocol/bgp/peer-groups/ peer-group/afi-safi/afi-safi-name/<afi-safi-name>/ l3vpn-ipv6-multicast/prefix-limit
• Neighbors—/network-instances/network-instance/ protocols/protocol/bgp/neighbors/ neighbor/afi-safi/afi-safi-name/<afi-safi-name>/l3vpn-ipv6-multicast/prefix-limit
Max-Prefixes /config/max-prefixes set protocols bgp family inet6-vpnmulticast accepted-prefix-limitmaximum maximum
Prevent-Teardown /config/prevent-teardown set protocols bgp family familyprefix-limit teardown
Shutdown-Threshold-PCT /config/shutdown-threshold-pct set protocols bgp family inet6-vpnmulticast accepted-prefix-limitteardown limit-threshold
Restart-Timer /config/restart-timer set protocols bgp family inet6-vpnmulticast accepted-prefix-limitteardown idle-timeout timeout
142
Table 20: AFI-SAFI L2VPN-VPLS Prefix-Limit Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
• Global—/network-instances/network-instance/ protocols/protocol/bgp/global/afi-safi/ afi-safi-name/<afi-safi-name>/l2vpn-vpls/ prefix-limit
• Peer-Group—/network-instances/network-instance/ protocols/protocol/bgp/peer-groups/ peer-group/afi-safi/afi-safi-name/<afi-safi-name>/ l2vpn-vpls/prefix-limit
• Neighbors—/network-instances/network-instance/ protocols/protocol/bgp/neighbors/ neighbor/afi-safi/afi-safi-name/<afi-safi-name>/l2vpn-vpls/prefix-limit
Max-Prefixes /config/max-prefixes set protocols bgp family l2vpnsignaling accepted-prefix-limitmaximum maximum
Prevent-Teardown /config/prevent-teardown set protocols bgp family familyprefix-limit teardown
Shutdown-Threshold-PCT /config/shutdown-threshold-pct set protocols bgp family l2vpnsignaling accepted-prefix-limitteardown limit-threshold
Restart-Timer /config/restart-timer set protocols bgp family l2vpnsignaling accepted-prefix-limitteardown idle-timeout timeout
143
Table 21: AFI-SAFI L2VPN-EVPN Prefix-Limit Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
• Global—/network-instances/network-instance/ protocols/protocol/bgp/global/afi-safi/ afi-safi-name/<afi-safi-name>/l2vpn-evpn/ prefix-limit
• Peer-Group—/network-instances/network-instance/ protocols/protocol/bgp/peer-groups/ peer-group/afi-safi/afi-safi-name/<afi-safi-name>/ l2vpn-evpn/prefix-limit
• Neighbors—/network-instances/network-instance/ protocols/protocol/bgp/neighbors/ neighbor/afi-safi/afi-safi-name/<afi-safi-name>/l2vpn-evpn/prefix-limit
Max-Prefixes /config/max-prefixes set protocols bgp family evpnsignaling accepted-prefix-limitmaximum maximum
Prevent-Teardown /config/prevent-teardown set protocols bgp family familyprefix-limit teardown
Shutdown-Threshold-PCT /config/shutdown-threshold-pct set protocols bgp family evpnsignaling accepted-prefix-limitteardown limit-threshold
Restart-Timer /config/restart-timer set protocols bgp family evpnsignaling accepted-prefix-limitteardown idle-timeout timeout
144
Table 22: Peer-Group Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
/network-instances/network-instance/ protocols/protocol/bgp/peer-groups/ peer-group
Peer-Group-Name /config/peer-group-name set protocols bgp group group-name
Peer-AS /config/peer-as set protocols bgp group group-name peer-as peer-as
Peer-Type /config/peer-type set protocols bgp group group-name type<external | internal>
Auth-Password /config/auth-password set protocols bgp group group-nameauthentication-key authentication-key
Remove-Private-AS /config/remote-private-as set protocols bgp group group-nameremove-private all
set protocols bgp group group-nameremove-private all replace
Route-Flap-Damping /config/route-flap-damping set protocols bgp group group-namedamping
Send-Community /config/send-community Not supported
Description /config/description set protocols bgp group group-namedescription description
Timers: Connect-Retry /timers/config/connect-retry set protocols bgp group group-nameconnect-retry-interval connect-retry
145
Table 22: Peer-Group Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Timers: Hold-Time /timers/config/hold-time set protocols bgp group group-name hold-time hold-time
Timers: Keepalive-Interval /timers/config/keepalive-interval Not supported
Timers: Minimum-Advertisement-Interval
/timers/config/minimum-advertisement-interval
set protocols bgp group group-name out-delay out-delay
Timers: Send-Update-Delay /timers/config/send-update-delay Not supported
Transport: TCP-MSS /transport/config/tcp-mss set protocols bgp group group-name tcp-mss tcp-mss
Transport: MTU-Discovery /transport/config/mtu-discovery set protocols bgp group group-name mtu-discovery
Transport: Passive-Mode /transport/config/passive-mode set protocols bgp group group-namepassive
Transport: Local-Address /transport/config/local-address set protocols bgp group group-namelocal-address local-address
Error-Handling: Treat-AS-Withdraw
/error-handling/config/treat-as-withdraw
set protocols bgp group group-name bgp-error-tolerance
Logging-Options: Log-Neighbor-State-Changes
/logging-options/config/ log-neighbor-state-changes
set protocols bgp group group-name log-updown
EBGP-Multihop: MultiHop-TTL
/ebgp-multihop/config/multihop-ttl set protocols bgp group group-namemultihop ttl ttl
146
Table 22: Peer-Group Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Route-Reflector: Route-Reflector-Cluster-ID
/route-reflector/config/route-reflector-cluster-id
set protocols bgp group group-namecluster cluster
Route-Reflector: Route-Reflector-Client
/route-reflector/config/route-reflector-client
set protocols bgp group group-name no-client-reflect
AS-Path-Options: Allow-Own-AS
/as-path-options/config/allow-own-as set protocols bgp group group-namelocal-as loops loops
AS-Path-Options: Replace-Peer-AS
/as-path-options/config/replace-peer-as
set protocols bgp group group-name as-override
AS-Path-Options: Disable-Peer-As-Filter
/as-path-options/config/disable-peer-as-filter
set protocols bgp group group-nameadvertise-peer-as
AFI-SAFI /afi-safis/afi-safi/ Supported. See Table 11 on page 131 toTable 21 on page 144
Graceful-Restart /graceful-restart/config/ Supported. See Table 10 on page 129.
Apply-Policy /apply-policy/ Supported. See Table 23 on page 147.
Table 23: Peer-Group Apply-Policy Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
/network-instances/network-instance/ protocols/protocol/bgp/peer-groups/ peer-group/apply-policy
147
Table 23: Peer-Group Apply-Policy Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Import-Policies /import-policies set protocols bgp import value
Default-Import-Policy /default-import-policy
Export-Policies /export-policies set protocols bgp export value
Default-Export-Policy /default-export-policy
Table 24: Neighbors Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
/network-instances/network-instance/ protocols/protocol/bgp/neighbors/ neighbor
Neighbor-Address /config/neighbor-address set protocols bgp group group-nameneighbor address
Peer-AS /config/peer-as set protocols bgp group group-nameneighbor address peer-as peer-as
Peer-Type /config/peer-type set protocols bgp group group-nametype <external|internal>
Auth-Password /config/auth-password set protocols bgp group group-nameneighbor address authentication-keyauthentication-key
148
Table 24: Neighbors Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Remove-Private-AS /config/remote-private-as set protocols bgp group group-nameneighbor address remove-private all
set protocols bgp group group-nameneighbor address remove-private allreplace
Route-Flap-Damping /config/route-flap-damping set protocols bgp group group-nameneighbor address damping
Send-Community /config/send-community Not supported
Description /config/description set protocols bgp group group-nameneighbor address description
Peer-Group /config/peer-group set protocols bgp group group-nameneighbor address
Timers – Connect-Retry /timers/config/connect-retry set protocols bgp group group-nameneighbor address connect-retry-interval
Timers – Hold-Time /timers/config/hold-time set protocols bgp group group-nameneighbor address hold-time hold-time
Timers - Keepalive-Interval /timers/config/keepalive-interval Not supported
Timers – Minimum-Advertisement-Interval
/timers/config/minimum-advertisement-interval
set protocols bgp group group-nameneighbor address out-delay out-delay
Timers - Send-Update-Delay /timers/config/send-update-delay Not supported
149
Table 24: Neighbors Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Transport – TCP-MSS /transport/config/tcp-mss set protocols bgp group group-nameneighbor address tcp-mss tcp-mss
Transport – MTU-Discovery /transport/config/mtu-discovery set protocols bgp group group-nameneighbor address mtu-discovery
Transport – Passive-Mode /transport/config/passive-mode set protocols bgp group group-nameneighbor address passive
Transport – Local-Address /transport/config/local-address set protocols bgp group group-nameneighbor address local-addresslocal-address
Error-Handling – Treat-AS-Withdraw
/error-handling/config/treat-as-withdraw
set protocols bgp group group-nameneighbor address bgp-error-tolerance
Logging-Options – Log-Neighbor-State-Changes
/logging-options/config /log-neighbor-state-changes
set protocols bgp group group-nameneighbor address log-updown
EBGP-Multihop – Multihop-TTL /ebgp-multihop/config/multihop-ttl set protocols bgp group group-nameneighbor address multihop ttl ttl
Route-Reflector – Route-Reflector-Cluster-ID
/route-reflector/config/route-reflector-cluster-id
set protocols bgp group group-nameneighbor address cluster cluster
Route-Reflector – Route-Reflector-Client
/route-reflector/config/route-reflector-client
set protocols bgp group group-nameneighbor address no-client-reflect
AS-Path-Options – Allow-Own-AS
/as-path-options/config/allow-own-as set protocols bgp group group-nameneighbor address local-as loopsloops
150
Table 24: Neighbors Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
AS-Path-Options – Replace-Peer-AS
/as-path-options/config/replace-peer-as
set protocols bgp group group-nameneighbor address as-override
AS-Path-Options – Disable-Peer-As-Filter
/as-path-options/config/disable-peer-as-filter
set protocol bgp group group-nameneighbor address advertise-peer-as
AFI-SAFI /afi-safis/afi-safi/ Supported. See Table 11 on page131 to Table 21 on page 144
Graceful-Restart /graceful-restart/config/ Supported. See Table 10 on page129.
Apply-Policy /apply-policy/ Supported. See Table 25 on page151.
Table 25: Neighbors Apply-Policy Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/apply-policy
Import-Policies /import-policies set protocols bgp import value
Default-Import-Policy /default-import-policy
Export-Policies /export-policies set protocols bgp export value
Default-Export-Policy /default-export-policy
151
RELATED DOCUMENTATION
Mapping OpenConfig Routing Policy Commands to Junos Configuration | 183
Mapping OpenConfig Interface Commands to Junos Configuration | 152
Mapping OpenConfig LLDP Commands to Junos Configuration | 159
Mapping OpenConfig Local Routing Commands to Junos Configuration | 160
Mapping OpenConfig MPLS Commands to Junos Configuration | 162
Mapping OpenConfig Interface Commands to JunosConfiguration
NOTE: See "OpenConfig Data Model Version" on page 3 topic to understand the data modelssupported version and its Junos OS release for Juniper Networks MX Series, PTX Series, andQFX Series.
Table 26 on page 152 to Table 33 on page 158 shows the mapping of OpenConfig interface commandsto the relevant configuration in Junos.
Table 26: VRRP Configuration
CommandName
OpenConfig Command Path Junos Configuration
VirtualRouter ID
ifa/vrrp/vrrp-group/config/virtual-router-id
set interfaces interface-name unit unit-number family inetaddress address vrrp-group virtual-router-id
set interfaces interface-name unit unit-number family inet6address address vrrp-inet6-group virtual-router-id
152
Table 26: VRRP Configuration (Continued)
CommandName
OpenConfig Command Path Junos Configuration
VirtualAddress
ifa/vrrp/vrrp-group/config/virtual-address
set interfaces interface-name unit unit-number family inetaddress address vrrp-group virtual-router-id virtual-addressaddress
set interfaces interface-name unit unit-number family inet6address address vrrp-inet6-group virtual-router-id virtual-inet6-address
VRRP Priority ifa/vrrp/vrrp-group/config/priority
set interfaces interface-name unit unit-number family inetaddress address vrrp-group virtual-router-id priority
set interfaces interface-name unit unit-number family inet6address address vrrp-inet6-group virtual-router-id priority
VRRPPreempt
ifa/vrrp/vrrp-group/config/preempt
set interfaces interface-name unit unit-number family inetaddress address vrrp-group virtual-router-id preempt
set interfaces interface-name unit unit-number family inet6address address vrrp-inet6-group virtual-router-id preempt
VRRPPreemptHold Time
ifa/vrrp/vrrp-group/config/preempt-delay
set interfaces interface-name unit unit-number family inetaddress address vrrp-group virtual-router-id preempt hold-time time
set interfaces interface-name unit unit-number family inet6address address vrrp-inet6-group virtual-router-id preempthold-time time
153
Table 26: VRRP Configuration (Continued)
CommandName
OpenConfig Command Path Junos Configuration
Accept Data ifa/vrrp/vrrp-group/config/accept_mode
set interfaces interface-name unit unit-number family inetaddress address vrrp-group virtual-router-id accept-data
set interfaces interface-name unit unit-number family inet6address address vrrp-inet6-group virtual-router-id accept-data
AdvertiseInterval
ifa/vrrp/vrrp-group/config/advertisement_interval
set interfaces interface-name unit unit-number family inetaddress address vrrp-group virtual-router-id advertise-interval
set interfaces interface-name unit unit-number family inet6address address vrrp-inet6-group virtual-router-id inet6-advertise-interval
TrackInterface
ifa/vrrp/vrrp-group/interface-tracking/config/track-interface
set interfaces interface-name unit unit-number family inetaddress address vrrp-group virtual-router-id track interfaceinterface-name
set interfaces interface-name unit unit-number family inet6address address vrrp-inet6-group virtual-router-id trackinterface interface-name
Priority Cost ifa/vrrp/vrrp-group/interface-tracking/config/priority-decrement
set interfaces interface-name unit unit-number family inetaddress address vrrp-group virtual-router-id track interfaceinterface-name priority-cost cost
set interfaces interface-name unit unit-number family inet6address address vrrp-inet6-group virtual-router-id trackinterface interface-name priority-cost cost
Virtual LinkLocal Address
ifa/vrrp/vrrp-group/config/virtual-link-local
set interfaces interface-name unit unit-number family inet6address address vrrp-inet6-group virtual-router-id virtual-link-local-address
154
Table 27: IPv4 and IPv6 Address Configuration
Command Name OpenConfig Command Path Junos Configuration
ConfigurationAddress
ipv4/addresses/address/ip
ipv4/addresses/address/prefix-length
set interfaces interface-name unit unit-number family inetaddress address
set interfaces interface-name unit unit-number familyinet6 address address
Neighbor Address ipv4/neighbors/neighbor/ip
ipv6/neighbors/neighbor/ip
set interfaces interface-name unit unit-number family inetaddress address arp address
set interfaces interface-name unit unit-number familyinet6 address address ndp address
Link Layer Address ip4/neighbors/neighbor/ip/link-layer-address
ip6/neighbors/neighbor/ip/link-layer-address
set interfaces interface-name unit unit-number family inetaddress address arp address mac address
set interfaces interface-name unit unit-number familyinet6 address address ndp address mac address
Table 28: Interface AE Configuration
Command Name OpenConfig Command Path Junos Configuration
LAG Type /aggregation/config/lag-type/lacp
/aggregation/config/lag-type/static
set interfaces ae-name aggregated-ether-options lacp
Minimum Links /aggregation/config/min-links set interfaces ae-name aggregated-ether-optionsminimum-links
155
Table 29: LACP Configuration
Command Name OpenConfig Command Path Junos Configuration
LACP Interval /lacp/interfaces/interface/config/interval
set interfaces ae-name aggregated-ether-options lacpperiodic fast
set interfaces ae-name aggregated-ether-options lacpperiodic slow
LACP Mode /lacp/interfaces/interface/config/lacp-mode
set interfaces ae-name aggregated-ether-options lacpactive
set interfaces ae-name aggregated-ether-options lacppassive
System ID /lacp/interfaces/interface/config/system-id-mac
set interfaces ae-name aggregated-ether-options lacpsystem-id address
System Priority /lacp/interfaces/interface/config/system-priority
set interfaces ae-name aggregated-ether-options lacpsystem-priority system-priority
Ethernet Options /lacp/interfaces/interface/members/member
set interface interface gigether-options 802.3ad
set interface interface fastether-options 802.3ad
set interface interface ether-options 802.3ad
Table 30: Member Interface Configuration
Command Name OpenConfig Command Path Junos Configuration
Aggregate ID /interface/aggregate-id set interface interface gigether-options 802.3ad aggregate-id
set interface interface fastether-options 802.3ad aggregate-id
set interface interface ether-options 802.3ad aggregate-id
156
Table 31: Ethernet Configuration
Command Name OpenConfig Command Path Junos Configuration
Auto-negotiate /ethernet/config/auto-negotiate set interfaces interface gigether-options auto-negotiation/no-auto-negotiation
MAC Address /ethernet/config/mac-address set interfaces interface mac
Duplex Mode /ethernet/config/duplex-mode set interfaces interface link-mode
Port Speed /ethernet/config/port-speed set interface interface speed
Flow Control /ethernet/config/enable-flow-control set interface interface gigether-options flow-control
Table 32: IFD Configuration
Command Name OpenConfig Command Path Junos Configuration
Interface Type /interfaces/interface/config/type Not supported.
Type is derived from the interface name.
Interface MTU /interfaces/interface/config/mtu set interface interface mtu
Interface Name /interfaces/interface/config/name set interface interface
Interface Description /interfaces/interface/config/description set interface interface description
Interface Enabled/Disabled
/interfaces/interface/config/enabled set interface interface disabled
set interface interface enabled
Hold Time Up /interfaces/interface/config/hold-time/config/up
set interface interface hold-time up
157
Table 32: IFD Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Hold Time Down /interfaces/interface/config/hold-time/config/down
set interface interface hold-time down
Table 33: IFL Configuration
Command Name OpenConfig Command Path Junos Configuration
Unit Name /interfaces/interface/subinterfaces/subinterface/config/index
set interfaces interface unit unit
Unnumbered Address /interfaces/interface/config/subinterfaces/subinterface/config/unnumbered
set interfaces interface unit unit familyfamily unnumbered-address source ifl
Unit Description /interfaces/interface/subinterfaces/subinterface/config/description
set interfaces interface unit unitdescription
Unit Enabled/Disabled /interfaces/interface/subinterfaces/subinterface/config/enabled
set interfaces interface unit unit enabled
set interfaces interface unit unit disabled
Interface Alias /interfaces/interface/subinterfaces/subinterface/config/name
set interfaces interface alias
RELATED DOCUMENTATION
Mapping OpenConfig Routing Policy Commands to Junos Configuration | 183
Mapping OpenConfig BGP Commands to Junos Configuration | 129
Mapping OpenConfig LLDP Commands to Junos Configuration | 159
Mapping OpenConfig Local Routing Commands to Junos Configuration | 160
Mapping OpenConfig MPLS Commands to Junos Configuration | 162
158
Mapping OpenConfig LLDP Commands to JunosConfiguration
NOTE: See "OpenConfig Data Model Version" on page 3 topic to understand the data modelssupported version and its Junos OS release for Juniper Networks MX Series and PTX Series.
Table 34 on page 159 and Table 35 on page 159 show the mapping of OpenConfig LLDP commandswith the relevant configuration in Junos.
Table 34: Global LLDP Configuration
Command Name OpenConfig Command Path Junos Configuration
Enable /lldp/config/enabled
NOTE:
set protocols lldp enable/disable
Hello time /lldp/config/hello-timer set protocols lldp tlv-filter
TLV advertisement /lldp/config/suppress-tlv-advertisement
NOTE:
set protocols lldp advertisement-intervaladvertisement-interval
System Information /lldp/config/system-name/lldp/config/system-description/lldp/config/chassis-id/lldp/config/chassis-id-type
Not supported
Table 35: Interface Configuration
Command Name OpenConfig Command Path Junos Configuration
Interface /lldp/interfaces/interface/NOTE:
set protocols lldp interface interface-name
159
Table 35: Interface Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Interface Config /lldp/interfaces/interface/config/name/lldp/interfaces/interface/config/enabled
NOTE:
set protocols lldp interface interface-nameenable
RELATED DOCUMENTATION
Mapping OpenConfig Routing Policy Commands to Junos Configuration | 183
Mapping OpenConfig Interface Commands to Junos Configuration | 152
Mapping OpenConfig Local Routing Commands to Junos Configuration | 160
Mapping OpenConfig BGP Commands to Junos Configuration | 129
Mapping OpenConfig MPLS Commands to Junos Configuration | 162
Mapping OpenConfig Local Routing Commands toJunos Configuration
NOTE: See "OpenConfig Data Model Version" on page 3 topic to understand the data modelssupported version and its Junos OS release for Juniper Networks ACX Series, EX Series, MXSeries, PTX Series, and QFX Series.
Table 36 on page 161 and Table 37 on page 161 show the mapping of OpenConfig local routingcommands to the relevant configuration in Junos.
160
Table 36: Static Route Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
/local-routes/static-routes
NOTE: Supported in Junos OSRelease 21.2R1 for PTX Series andMX Series. Supported in JunosEvolved OS Release 21.3R1 forPTX10003 and PTX10008 routers.Supported in Junos Evolved OSRelease 21.4R1 for PTX10016routers.
Local Static Routes
/static/next-hops/next-hop/config/metric
set routing-options static routeprefix qualified-next-hop nexthopmetric value
Local Static Prefix /static/config/prefix set routing-options static routeprefix
Local Static Next Hop /static/config/prefix
/static/config/next-hop/ip-address
/static/config/next-hop/local-defined-next-hop
/static/config/next-hop/string
set routing-options static routeprefix next-hop (address |interface)
set routing-options static routeprefix discard
Local Static Tag /static/config/prefix
/static/config/set-tag
set routing-options static routeprefix tag tag
Table 37: Local Aggregate Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
/local-routes/local-aggregates
161
Table 37: Local Aggregate Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Local Aggregate Prefix /aggregate/config/prefix set routing-options aggregate route prefix
Local Aggregate Discard /aggregate/config/prefix
/aggregate/config/discard
set routing-options aggregate route prefix discard
Local Aggregate Tag /aggregate/config/prefix
/aggregate/config/set-tag
set routing-options aggregate route prefix tag tag
RELATED DOCUMENTATION
Mapping OpenConfig BGP Commands to Junos Configuration | 129
Mapping OpenConfig Interface Commands to Junos Configuration | 152
Mapping OpenConfig LLDP Commands to Junos Configuration | 159
Mapping OpenConfig MPLS Commands to Junos Configuration | 162
Mapping OpenConfig Routing Policy Commands to Junos Configuration | 183
Mapping OpenConfig MPLS Commands to JunosConfiguration
NOTE: See "OpenConfig Data Model Version" on page 3 topic to understand the data modelssupported version and its Junos OS release for Juniper Networks MX Series, PTX Series, andQFX Series.
Table 38 on page 163 to Table 43 on page 173 show the mapping of OpenConfig MPLS commands withthe relevant configuration in Junos.
162
Table 38: Global MPLS Configuration
CommandName
OpenConfig Command Path Junos Configuration
Explicit Null /mpls/global/config/null-label/explicit
/mpls/global/config/null-label/implicit
set protocols mpls explicit-null
Interface /mpls/global/interface-attributes/interface/config/interface-id
/mpls/global/interface-attributes/interface/config/mpls-enabled
/mpls/global/interface-attributes/interface/interface-ref/config/interface
/mpls/global/interface-attributes/interface/interface-ref/config/subinterface
set protocols mpls interfaceinterface
set protocols mpls interfaceinterface disable
Table 39: TE Global Attributes
Command Name OpenConfig Command Path Junos Configuration
SRLGs /mpls/te-global-attributes/srlg/srlg/config/name Flooded:
set routing-options srlg name
Static:
set routing-options fate-sharing group name
SRLG Value /mpls/te-global-attributes/srlg/srlg/config/value set routing-options fate-sharing group name srlg-valuevalue
163
Table 39: TE Global Attributes (Continued)
Command Name OpenConfig Command Path Junos Configuration
SRLG Cost /mpls/te-global-attributes/srlg/srlg/config/cost Flooded:
set routing-options srlg namesrlg-cost cost
Static:
set routing-options fate-sharing group name cost cost
Address /mpls/te-global-attributes/srlg/srlg/static-srlg-members/ members-list/config/from-address
/mpls/te-global-attributes/srlg/srlg/static-srlg-members/ members-list/config/to-address
set routing-options fate-sharing group name from addressto address
Admin Groups /mpls/te-global-attributes/mpls-admin-groups/admin-group/ config/admin-group-name
/mpls/te-global-attributes/mpls-admin-groups/admin-group/ config/bit-position
Bit position (group-value) 0-31:
set protocols mpls admin-groupsgroup-name group-value
Bit position (group-value)32-4294967295:
set routing-options admin-groups-extended group-namegroup-value group-value
Delay /mpls/te-global-attributes/te-lsp-timers/config/install-delay
/mpls/te-global-attributes/te-lsp-timers/config/cleanup-delay
/mpls/te-global-attributes/te-lsp-timers/config/reoptimize-timer
set protocols mpls optimize-switchover-delay delay
set protocols mpls optimize-hold-dead-delay delay
set protocols mpls optimize-timer timer
164
Table 40: TE Interface Attributes
Command Name OpenConfig Command Path Junos Configuration
TE Interface /mpls/te-interface-attributes/interface/config/interface-id
/mpls/te-interface-attributes/interface/interface-ref/config/interface
/mpls/te-interface-attributes/interface/interface-ref/config/subinterface
set protocols ospf area id interfaceinterface
TE Metric /mpls/te-interface-attributes/interface/config/te-metric
set protocols ospf area id interfaceinterface te-metric te-metric
set protocols isis interface interfacelevel level te-metric te-metric
SRLGMembership
/mpls/te-interface-attributes/interface/config/srlg-membership
set protocols mpls interface name srlgname
Admin Groups /mpls/te-interface-attributes/interface/config/admin-group
If protocols mpls admin-groups name isconfigured:
set protocols mpls interface nameadmin-group name
If routing-options admin-groups-extendedname is configured:
set protocols mpls interface nameadmin-group-extended name
IGP FloodingBandwidth
/mpls/te-interface-attributes/interface/igp-flooding-bandwidth/config/threshold-type
/mpls/te-interface-attributes/interface/igp-flooding-bandwidth/config/delta-percentage
set protocols rsvp interface nameupdate-threshold threshold
165
Table 40: TE Interface Attributes (Continued)
Command Name OpenConfig Command Path Junos Configuration
/mpls/te-interface-attributes/interface/igp-flooding-bandwidth/config/threshold-specification
/mpls/te-interface-attributes/interface/igp-flooding-bandwidth/config/up-thresholds
/mpls/te-interface-attributes/interface/igp-flooding-bandwidth/config/down-thresholds
/mpls/te-interface-attributes/interface/igp-flooding-bandwidth/config/up-down-thresholds
Not supported
Table 41: RSVP Signaling Protocols
Command Name OpenConfig Command Path Junos Configuration
Graceful Restart /mpls/signaling-protocols/rsvp-te/global/graceful-restart/config/enable
/mpls/signaling-protocols/rsvp-te/global/graceful-restart/config/restart-time
/mpls/signaling-protocols/rsvp-te/global/graceful-restart/config/recovery-time
set protocols rsvp graceful-restart enable
set protocols rsvp graceful-restart maximum-helper-recovery-time time
set protocols rsvp graceful-restart maximum-helper-restart-time time
Cleanup Timer /mpls/signaling-protocols/rsvp-te/global/ soft-preemption/config/enable
/mpls/signaling-protocols/rsvp-te/global/ soft-preemption/config/soft-preemption-timeout
set protocols rsvppreemption soft-preemptioncleanup-timer timer
Hello Interval (All Interfaces) /mpls/signaling-protocols/rsvp-te/global/ hellos/config/hello-interval
/mpls/signaling-protocols/rsvp-te/global/ hellos/config/refresh-reduction
set protocols rsvp interfaceall hello-interval interval
set protocols rsvp interfaceall no-reliable
166
Table 41: RSVP Signaling Protocols (Continued)
Command Name OpenConfig Command Path Junos Configuration
Hello Interval (SingleInterface)
/mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/config/interface-id
/mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/interface-ref/config/interface
/mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/config/interface-name
/mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/hellos/config/hello-interval
/mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/hellos/config/refresh-reduction
set protocols rsvp interfacename hello-interval interval
set protocols rsvp interfacename no-reliable
Authentication Key /mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/config/interface-id
/mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/interface-ref/config/interface
/mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/interface-ref/config/subinterface
/mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/authentication/config/enable
/mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/authentication/config/authentication-key
set protocols rsvp interfacename authentication-key key
167
Table 41: RSVP Signaling Protocols (Continued)
Command Name OpenConfig Command Path Junos Configuration
Subscription /mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/config/interface-id
/mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/interface-ref/config/interface
/mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/interface-ref/config/subinterface
/mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/subscription/config/subscription
set protocols rsvp interfacename subscriptionsubscription
168
Table 41: RSVP Signaling Protocols (Continued)
Command Name OpenConfig Command Path Junos Configuration
Link Protection /mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/config/interface-id
/mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/interface-ref/config/interface
/mpls/signaling-protocols/rsvp-te/interface-attributes/ interface/interface-ref/config/subinterface
/mpls/signaling-protocols/rsvp-te/interface-attributes/interface/ protection/config/link-protection-style-requested/unprotected
/mpls/signaling-protocols/rsvp-te/interface-attributes/interface/protection/ config/link-protection-style-requested/link-protection-requested
/mpls/signaling-protocols/rsvp-te/interface-attributes/interface/protection/ config/link-protection-style-requested/link-node-protection-requested
/mpls/signaling-protocols/rsvp-te/interface-attributes/interface/protection/ config/bypass-optimize-interval
set protocols rsvp interfacename link-protection
To disable node-protection:
set protocols rsvp interfacename link-protection no-node-protection
set protocols rsvp interfacename link-protectionoptimize-timer timer
169
Table 42: Label Switched Paths
CommandName
OpenConfig Command Path Junos Configuration
Path /mpls/lsps/constrained-path/named-explicit-paths/config/name
/mpls/lsps/constrained-path/named-explicit-paths/explicit-route-objects/ config/address
/mpls/lsps/constrained-path/named-explicit-paths/explicit-route-objects/ config/hop-type
/mpls/lsps/constrained-path/named-explicit-paths/explicit-route-objects/ config/index
set protocols mpls path nameaddress hop-type
Name /mpls/lsps/constrained-path/tunnel/config/name
/mpls/lsps/constrained-path/tunnel/config/type/P2P
/mpls/lsps/constrained-path/tunnel/config/ signaling-protocol/path-setup-rsvp
set protocols mpls label-switched-path name
Description /mpls/lsps/constrained-path/tunnel/config/description set protocols mpls label-switched-path name description description
Admin-Status /mpls/lsps/constrained-path/tunnel/config/admin-status set protocols mpls label-switched-path name disable
Preference /mpls/lsps/constrained-path/tunnel/config/preference set protocols mpls label-switched-path name preference preference
Metric /mpls/lsps/constrained-path/tunnels/tunnel/config/metric-type
/mpls/lsps/constrained-path/tunnels/tunnel/config/shortcut-eligible
/mpls/lsps/constrained-path/tunnel/config/metric
set protocols mpls label-switched-path name metric metric
170
Table 42: Label Switched Paths (Continued)
CommandName
OpenConfig Command Path Junos Configuration
Link Protection /mpls/lsps/constrained-path/tunnel/config/ protection-style-requested/unprotected
/mpls/lsps/constrained-path/tunnel/config/ protection-style-requested/link-protection-requested
/mpls/lsps/constrained-path/tunnel/config/ protection-style-requested/link-node-protection-requested
set protocols mpls label-switched-path name link-protection
set protocols mpls label-switched-path name node-link-protection
Optimize Timer /mpls/lsps/constrained-path/tunnel/config/reoptimize-timer
set protocols mpls label-switched-path name optimize-timer timer
Source /mpls/lsps/constrained-path/tunnel/config/source set protocols mpls label-switched-path name from from
Soft Preemption /mpls/lsps/constrained-path/tunnel/config/soft-preemption
set protocols mpls label-switched-path name soft-preemption
Priority /mpls/lsps/constrained-path/tunnel/config/setup-priority
/mpls/lsps/constrained-path/tunnel/config/hold-priority
set protocols mpls label-switched-path name priority setupreservation
Bandwidth /mpls/lsps/constrained-path/tunnel/bandwidth/config/specification-type/specified
/mpls/lsps/constrained-path/tunnel/bandwidth/config/set-bandwidth
set protocols mpls label-switched-path name bandwidth bandwidth
171
Table 42: Label Switched Paths (Continued)
CommandName
OpenConfig Command Path Junos Configuration
Min/MaxBandwidth
/mpls/lsps/constrained-path/tunnel/bandwidth/config/specification-type/auto
/mpls/lsps/constrained-path/tunnel/bandwidth/auto-bandwidth/ config/enabled
/mpls/lsps/constrained-path/tunnel/bandwidth/auto-bandwidth/ config/min-bw
/mpls/lsps/constrained-path/tunnel/bandwidth/auto-bandwidth/ config/max-bw
/mpls/lsps/constrained-path/tunnel/bandwidth/auto-bandwidth/ config/adjust-interval
/mpls/lsps/constrained-path/tunnel/bandwidth/auto-bandwidth/ config/adjust-threshold
set protocols mpls label-switched-path name minimum-bandwidth minimum
set protocols mpls label-switched-path name maximum-bandwidth maximum
set protocols mpls label-switched-path name adjust-interval interval
set protocols mpls label-switched-path name adjust-thresholdthreshold
OverflowBandwidth
/mpls/lsps/constrained-path/tunnel/bandwidth/ config/specification-type/auto
/mpls/lsps/constrained-path/tunnel/auto-bandwidth/overflow/ config/enabled
/mpls/lsps/constrained-path/tunnel/bandwidth/auto-bandwidth/ overflow/config/overflow-threshold
/mpls/lsps/constrained-path/tunnel/bandwidth/auto-bandwidth/ overflow/config/trigger-event-count
set protocols mpls label-switched-path name auto-bandwidth adjust-threshold-overflow-limit
172
Table 42: Label Switched Paths (Continued)
CommandName
OpenConfig Command Path Junos Configuration
UnderflowBandwidth
/mpls/lsps/constrained-path/tunnel/bandwidth/config/specification-type/auto
/mpls/lsps/constrained-path/tunnel/auto-bandwidth/underflow/ config/enabled
/mpls/lsps/constrained-path/tunnel/bandwidth/auto-bandwidth/ underflow/config/underflow-threshold
/mpls/lsps/constrained-path/tunnel/bandwidth/auto-bandwidth/ underflowflow/config/trigger-event-count
set protocols mpls label-switched-path name auto-bandwidth adjust-threshold-underflow-limit
Table 43: RSVP P2P Tunnel
Command Name OpenConfig Command Path Junos Configuration
Destination /mpls/lsps/constrained-path/tunnel/ p2p-tunnel-attributes/config/destination
set protocols mpls label-switched-path name to to
Primary Path /mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-primary-paths/config/name
set protocols mpls label-switched-path name
173
Table 43: RSVP P2P Tunnel (Continued)
Command Name OpenConfig Command Path Junos Configuration
Primary Path - Locally-Computed
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-primary-paths/config/path-computation-method/ locally-computed
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-primary-paths/config/use-cspf
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-primary-paths/config/cspf-tiebreaker/random
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-primary-paths/config/cspf-tiebreaker/least-fill
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-primary-paths/config/cspf-tiebreaker/most-fill
set protocols mpls label-switched-path name no-cspf
set protocols mpls label-switched-path name random
set protocols mpls label-switched-path name least-fill
set protocols mpls label-switched-path name most-fill
Primary Path - ExternallyQueried
/mpls/lsps/constrained-path/tunnel/ p2p-tunnel-attributes/p2p-primary-paths/config/path-computation-method/externally-queried
set protocols mpls label-switched-path name lsp-external-controller pccd
set protocols pcep pce namedestination-ipv4-addressaddress
set protocols pcep pce namedestination-port 4189
Primary Path - ExplicitlyDefined
/mpls/lsps/constrained-path/tunnel/ p2p-tunnel-attributes/p2p-primary-paths/config/path-computation-method/explicitly-defined
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-primary-paths/config/explicit-path-name
set protocols mpls label-switched-path name primarypath
174
Table 43: RSVP P2P Tunnel (Continued)
Command Name OpenConfig Command Path Junos Configuration
Primary Path - Preference /mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-primary-paths/config/preference
set protocols mpls label-switched-path name primarypath preference preference
Primary Path - Priorities /mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-primary-paths/config/setup-priority
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-primary-paths/config/hold-priority
set protocols mpls label-switched-path name primarypath priority setupreservation
Primary Path - Retry Timer /mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-primary-paths/config/retry-timer
set protocols mpls label-switched-path name retry-timer
Primary Path - CandidateSecondary Paths
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-primary-paths/candidate-secondary-paths
Not supported
Primary Path – Admin-Groups /mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-primary-paths/admin-groups/config/exclude-group
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-primary-paths/admin-groups/config/include-all-group
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-primary-paths/admin-groups/config/include-any-group
set protocols mpls label-switched-path name primarypath admin-group excludegroup
set protocols mpls label-switched-path name primarypath admin-group excludegroup
set protocols mpls label-switched-path name primarypath admin-group include-anygroup
175
Table 43: RSVP P2P Tunnel (Continued)
Command Name OpenConfig Command Path Junos Configuration
Secondary Path /mpls/lsps/constrained-path/tunnel/config/name
/mpls/lsps/constrained-path/tunnel/config/type/P2P
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/config/name
set protocols mpls label-switched-path name
Secondary Path - Locally-Computed
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/config/ path-computation-method/locally-computed
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/config/use-cspf
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/config/cspf-tiebreaker/random
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/config/cspf-tiebreaker/least-fill
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/config/cspf-tiebreaker/most-fill
set protocols mpls label-switched-path name secondarypath name no-cspf
Secondary Path - ExternallyQueried
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/config/ path-computation-method/externally-queried
Not supported
176
Table 43: RSVP P2P Tunnel (Continued)
Command Name OpenConfig Command Path Junos Configuration
Secondary Path - ExplicitlyDefined
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/config/ path-computation-method/explicitly-defined
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/config/explicit-path-name
set protocols mpls label-switched-path name secondarypath
Secondary Path - Preference /mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/config/preference
set protocols mpls label-switched-path name secondarypath preference preference
Secondary Path - Priorities /mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/config/setup-priority
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/config/hold-priority
set protocols mpls label-switched-path name secondarypath priority setupreservation
Secondary Path - Retry Timer /mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/config/retry-timer
set protocols mpls label-switched-path name secondarypath retry-timer
177
Table 43: RSVP P2P Tunnel (Continued)
Command Name OpenConfig Command Path Junos Configuration
Secondary Path - Admin-Groups
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/admin-groups/config/exclude-group
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/admin-groups/config/include-all-group
/mpls/lsps/constrained-path/tunnel/p2p-tunnel-attributes/ p2p-secondary-paths/admin-groups/config/include-any-group
set protocols mpls label-switched-path name secondarypath admin-group excludegroup
set protocols mpls label-switched-path name secondarypath admin-group include-allgroup
set protocols mpls label-switched-path name secondarypath admin-group include-anygroup
RELATED DOCUMENTATION
Mapping OpenConfig BGP Commands to Junos Configuration | 129
Mapping OpenConfig Interface Commands to Junos Configuration | 152
Mapping OpenConfig LLDP Commands to Junos Configuration | 159
Mapping OpenConfig Local Routing Commands to Junos Configuration | 160
Mapping OpenConfig Routing Policy Commands to Junos Configuration | 183
Mapping OpenConfig Network Instance Commandsto Junos Operation
NOTE: See "OpenConfig Data Model Version" on page 3 topic to understand the data modelssupported version and its Junos OS release for Juniper Networks ACX Series, EX Series, MXSeries, PTX Series, and QFX Series.
178
Network instance models a generic virtual forwarding table on a device. This supports a Layer 3forwarding construct such as a virtual routing and forwarding (VRF) instance, or a Layer 2 instance suchas a virtual switch instance. A mixed Layer 2 and Layer 3 instances are also supported.
Starting with Junos OS Release 17.4R1, network instance based BGP configuration is supported. Afterthe network instance is configured, you will be prompted with options for BGP configuration such asglobal bgp, neighbor bgp, and so on.
NOTE: There is no change in the existing BGP configuration, you can configure BGP in a specificnetwork instance.
Table 44 on page 179 details the network instance commands.
Table 44: Network Instance
Resource Path Description
/network-instances/network-instance/config/name An assigned unique name for the forwarding instance.
In Junos, you need to provide a name because you donot run different BGP in the same routing instance.
/network-instances/network-instance/config/name/description
Description of the network instance.
/network-instances/network-instance/config/type Type of network instance:
• default_instance
• l3vrf
• l2vsi
• l2p2p
• l2l3
NOTE: Only default_instance and l3vrf instances aresupported.
179
Table 44: Network Instance (Continued)
Resource Path Description
/network-instances/network-instance/config/enabled Whether the network instance should be configured tobe active on the network element: True or False.
By default, the value is True.
/network-instances/network-instance/config/router-id An identifier for the local network instance.
/network-instances/network-instance/config/route-distinguisher
The route distinguisher that should be used for thelocal VRF instance when it is signalled through BGP.
NOTE: Supported in Junos OS Release 21.2R1 for PTXSeries and MX Series. Supported in Junos Evolved OSRelease 21.3R1 for PTX10003, PTX10008, andPTX10016 routers.
/network-instances/network-instance/interfaces/config/interface
Name of interfaces belonging to this routing instance.
The Junos CLI mapping is:
set routing-instance name interface name
NOTE: Supported in Junos OS Release 21.2R1 for PTXSeries and MX Series. Supported in Junos Evolved OSRelease 21.3R1 for PTX10003 and PTX10008 routers.Supported in Junos Evolved OS Release 21.4R1 forPTX10016 routers.
/network-instances/network-instance/interfaces/config/interface
The Junos CLI mapping is:
set routing-instance name interface name
180
Table 44: Network Instance (Continued)
Resource Path Description
/network-instances/network-instance/protocols/protocol/config/identifier
Type of identifier:
• BGP
• ISIS
• OSPF
• OSPF3
• STATIC
• DIRECTLY_CONNECTED
• LOCAL_AGGREGATE
NOTE: Only BGP is supported.
/network-instances/network-instance/protocols/protocol/config/name
A unique name for the protocol instance. This is not amandatory field.
• /network-instances/network-instance/protocols/protocol/config/name/enable
• /network-instances/network-instance/protocols/protocol/config/name/target-table
• /network-instances/network-instance/table-connections/table-connection/config/src-table
• /network-instances/network-instance/table-connections/table-connection/config/dst-table
• /network-instances/network-instance/table-connections/table-connection/config/tables
Not supported.
181
Table 44: Network Instance (Continued)
Resource Path Description
NOTE: Supported in Junos OS Release 21.2R1 for PTXSeries and MX Series. Supported in Junos Evolved OSRelease 21.3R1 for PTX10003 and PTX10008 routers.Supported in Junos Evolved OS Release 21.4R1 forPTX10016 routers.
/network-instances/network-instance/inter-instance-policies/apply-policy/config/import-policy
The Junos CLI mapping is:
set routing-instances instance-name routing-optionsinstance-export import-policy
NOTE: Supported in Junos OS Release 21.2R1 for PTXSeries and MX Series. Supported in Junos Evolved OSRelease 21.3R1 for PTX10003 and PTX10008 routers.Supported in Junos Evolved OS Release 21.4R1 forPTX10016 routers.
/network-instances/network-instance/inter-instance-policies/apply-policy/config/export-policy
The Junos CLI mapping is:
set routing-instances instance-name routing-optionsinstance-export export-policy
/network-instances/network-instance/protocols/protocol/static-routes/static/config/prefix
The prefix of the static route that you configure.
/network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/next-hop
The IP address of the next-hop for the static route thatyou configure.
NOTE: Supported in Junos OS Release 21.2R1 for PTXSeries and MX Series. Supported in Junos Evolved OSRelease 21.3R1 for PTX10003 and PTX10008 routers.Supported in Junos Evolved OS Release 21.4R1 forPTX10016 routers.
/network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/config/metric
The Junos CLI mapping is:
set routing-instance name routing-options static routeprefix quaiified-next-hop nexthop metric value
182
Table 44: Network Instance (Continued)
Resource Path Description
/network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/interface-ref/config/interface
The physical interface of the next-hop for the staticroute that you configure.
/network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/next-hop/interface-ref/config/subinterface
The logical interface of the next-hop for the staticroute that you configure.
Release History Table
Release Description
17.4R1 Starting with Junos OS Release 17.4R1, network instance based BGP configuration is supported.
RELATED DOCUMENTATION
Mapping OpenConfig BGP Commands to Junos Configuration | 129
Mapping OpenConfig Interface Commands to Junos Configuration | 152
Mapping OpenConfig Routing Policy Commands toJunos Configuration
NOTE: See "OpenConfig Data Model Version" on page 3 topic to understand the data modelssupported version and its Junos OS release for Juniper Networks EX2300, EX3400, EX4300,EX4600, and EX9200 switches, MX Series, PTX Series, and QFX Series.
Table 45 on page 184 to Table 47 on page 184 show the mapping of OpenConfig routing policycommands to the relevant configuration in Junos.
183
Table 45: Defined Set Configuration
Command Name OpenConfig Command Path Junos Configuration
Prefix Set /routing-policy/defined-sets/prefix-set
set policy-options prefix-list name
Neighbor Set /routing-policy/defined-sets/neighbor-set
set policy-options neighbor-listname
Tag Set /routing-policy/defined-sets/tag-set
set policy-options tag-list nametag-set value
Table 46: BGP Defined Set Configuration
Command Name OpenConfig Command Path Junos Configuration
Community Set /routing-policy/defined-sets/bgp-defined-sets/community-set
set policy-options community namemembers value
AS Path Set /routing-policy/defined-sets/bgp-defined-sets/as-path-set
Not supported
Ext Community Set /routing-policy/defined-sets/bgp-defined-sets/ext-community-set
set policy-options community namemembers value
Table 47: Policy Definition Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
/routing-policy/policy-definition/statement
Call Policy /conditions/call-policy set policy-options policy-statement namefrom policy value
184
Table 47: Policy Definition Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Prefix Set /conditions/match-prefix-set/prefix-set
set policy-options policy-statement namefrom prefix-list name
set policy-options policy-statement namefrom route-filter address prefix-length-range range
Match Set Options /conditions/match-prefix-set/match-set-options
Not supported
Neighbor Set /conditions/match-neighbor-set/neighbor-set
set policy-options policy-statement namefrom neighbor address
Match Neighbor Set /conditions/match-neighbor-set/match-set-options
Not supported
Tag Set /conditions/match-tag-set/tag-set set policy-options policy-statement namefrom tag tag
Match Tag Set /conditions/match-tag-set/match-set-options
Not supported
Install Protocol EQ /conditions/install-protocol-eq set policy-options policy-statement namefrom protocol protocol
IGP Conditions /conditions/igp-conditions Not supported
BGP Match CommunitySet
/conditions/bgp-conditions/match-community-set/community-set
set policy-options policy-statement namefrom community name
BGP Match ExtCommunity Set
/conditions/bgp-conditions/match-ext-community-set
set policy-options policy-statement namefrom community name
185
Table 47: Policy Definition Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
BGP Match ExtCommunity Set Options
/conditions/bgp-conditions/match-ext-community-set/match-set-options
Not supported
BGP Match AS Path Set /conditions/bgp-conditions/match-as-path-set
Not supported
BGP MED EQ /conditions/bgp-conditions/med-eq set policy-options policy-statement namefrom metric metric
BGP Origin EQ /conditions/bgp-conditions/origin-eq set policy-options policy-statement namefrom origin (egp | igp | incomplete)
BGP Next Hop /conditions/bgp-conditions/next-hop-in
set policy-options policy-statement namefrom next-hop address
BGP Local PreferenceEQ
/conditions/bgp-conditions/local-pref-eq
set policy-options policy-statement namefrom local-preference preference
BGP Community Count /conditions/bgp-conditions/community-count
set policy-options policy-statement namefrom community-count count (equal | orhigher|orlower)
BGP AS Path Length /conditions/bgp-conditions/as-path-length
Not supported
Accept-Route /actions/config/accept-route set policy-options policy-statement example-accept then accept
Reject-Route /actions/config/reject-route set policy-options policy-statement example-reject then reject
186
Table 47: Policy Definition Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
IGP Actions /actions/igp-actions/set-tag set policy-options policy-statement namethen tag tag
BGP Actions Set ASPath Prepend
/actions/bgp-actions/set-as-path-prepend
Not supported
BGP Actions SetCommunity
/actions/bgp-actions/set-community set policy-options policy-statement namethen community (set | replace | add) name
BGP Actions Set ExtCommunity
/actions/bgp-actions/set-ext-community
set policy-options policy-statement namethen community (set | replace | add) name
BGP Actions Set RouteOrigin
/actions/bgp-actions/set-route-origin
set policy-options policy-statement namethen origin (egp |igp | incomplete)
BGP Actions Set LocalPreferences
/actions/bgp-actions/set-local-pref set policy-options policy-statement namethen local-preference preference
BGP Actions Set NextHop
/actions/bgp-actions/set-next-hop set policy-options policy-statement namethen next-hop address
BGP Actions Set Med /actions/bgp-actions/set-med set policy-options policy-statement namethen metric metric
BGP Actions As-Path-Prepend
/actions/bgp-actions/config/set-as-path-prepend/asn
set policy-options policy-statement namethen as-path-prepend as-path
RELATED DOCUMENTATION
Mapping OpenConfig BGP Commands to Junos Configuration | 129
Mapping OpenConfig Interface Commands to Junos Configuration | 152
187
Mapping OpenConfig LLDP Commands to Junos Configuration | 159
Mapping OpenConfig Local Routing Commands to Junos Configuration | 160
Mapping OpenConfig MPLS Commands to Junos Configuration | 162
Mapping OpenConfig System Logging ModelCommands to Junos Configuration
NOTE: See "OpenConfig Data Model Version" on page 3 topic to understand the data modelssupported version and its Junos OS release for Juniper Networks MX Series and PTX Series.
Table 48 on page 188 and Table 49 on page 190show the mapping of OpenConfig logging commandswith the relevant configuration in Junos.
Table 48: Remote Logging Configuration
Command Name OpenConfig Configuration Junos Configuration
Hostopenconfig-system:system { logging { remote-servers { remote-server <host> { … } } }}
system { syslog { host <> { …….. } }}
The OpenConfig remote-logging server host leaf maps to the Junos host parameter.
188
Table 48: Remote Logging Configuration (Continued)
Command Name OpenConfig Configuration Junos Configuration
Source-addressopenconfig-system:system { logging { remote-servers { remote-server <> { config { source-address <>; } } } }}
system { syslog { host <> { source-address <>; } }}
The OpenConfig source-address leaf maps to the Junos source-address parameter.
Remote-portopenconfig-system:system { logging { remote-servers { remote-server <> { config { remote-port <>; } } } }
system { syslog { host <> { port <>; } }}
The OpenConfig leaf remote-port maps to the Junos port parameter.
189
Table 48: Remote Logging Configuration (Continued)
Command Name OpenConfig Configuration Junos Configuration
Selectoropenconfig-system:system { logging { remote-servers { remote-server <> { selectors { selector <facility> <severity>; } } } }}
system { syslog { host <> { <facility> <severity>; } }}
The OpenConfig leaves facility and severity map to the Junos facility and severity parameters.
Table 49: Console Logging Configuration
Command Name OpenConfig Configuration Junos Configuration
Consoleopenconfig-system:system { logging { console { ……… } }}
system { syslog { console { ………….. } }}
Selectoropenconfig-system:system { logging { console { selectors { selector <facility> <severity> ; } } }
system { syslog { console { <facility> <severity>; } }}
190
Table 49: Console Logging Configuration (Continued)
Command Name OpenConfig Configuration Junos Configuration
The OpenConfig leaves facility and severity map to the Junos facility and severity parameters.
RELATED DOCUMENTATION
Mapping OpenConfig Routing Policy Commands to Junos Configuration | 183
Mapping OpenConfig Interface Commands to Junos Configuration | 152
Mapping OpenConfig Local Routing Commands to Junos Configuration | 160
Mapping OpenConfig BGP Commands to Junos Configuration | 129
Mapping OpenConfig MPLS Commands to Junos Configuration | 162
Mapping OpenConfig System Management ModelCommands to Junos Configuration
NOTE: See "OpenConfig Data Model Version" on page 3 topic to understand the data modelssupported version and its Junos OS release for Juniper Networks MX Series and PTX Series.
Table 50 on page 192, Table 51 on page 192, Table 52 on page 192, Table 53 on page 193, Table 54 onpage 193, and Table 55 on page 194 show the mapping of OpenConfig system managementconfiguration with the relevant configuration in Junos.
191
Table 50: DNS Configuration
Command Name OpenConfig Configuration Junos Configuration
Searchopenconfig-system:system { dns { config { search [ <> … ]; } }}
system { domain-search [<> …];}
The OpenConfig DNS search leaf maps to the Junos domain-search statement.
Table 51: Domain Name Configuration
Command Name OpenConfig Configuration Junos Configuration
Domain-nameopenconfig-system:system { config { domain-name <>; }}
system { domain-name <>; }
The OpenConfig domain-name leaf maps to the Junos domain-name statement.
Table 52: Host Name Configuration
Command Name OpenConfig Configuration Junos Configuration
Host-nameopenconfig-system:system { config { hostname <>; } }
openconfig-system:system { config { hostname <>; } }
192
Table 52: Host Name Configuration (Continued)
Command Name OpenConfig Configuration Junos Configuration
The OpenConfig hostname leaf maps to the Junos hostname statement.
Table 53: Time Zone Configuration
Command Name OpenConfig Configuration Junos Configuration
Time-zoneopenconfig-system:system { clock { config { timezone-name <>; } }}
system { time-zone <>;}
The OpenConfig timezone-name leaf maps to the Junos time-zone statement.
Table 54: Login Banner Configuration
Command Name OpenConfig Configuration Junos Configuration
Login-banneropenconfig-system:system { config { login-banner <>; }}
system { login { message <>; }}
The OpenConfig DNS login-banner leaf maps to the Junos message statement.
193
Table 55: MOTD Banner Configuration
Command Name OpenConfig Configuration Junos Configuration
Motd-banneropenconfig-system:system { config { motd-banner <>; }}
system { login { announcement <>; }}
The OpenConfig motd-banner leaf maps to the Junos announcement statement.
RELATED DOCUMENTATION
Mapping OpenConfig Routing Policy Commands to Junos Configuration | 183
Mapping OpenConfig Interface Commands to Junos Configuration | 152
Mapping OpenConfig Local Routing Commands to Junos Configuration | 160
Mapping OpenConfig BGP Commands to Junos Configuration | 129
Mapping OpenConfig MPLS Commands to Junos Configuration | 162
Mapping OpenConfig System Model Commands toJunos Configuration
NOTE: See "OpenConfig Data Model Version" on page 3 topic to understand the data modelssupported version and its Junos OS release for Juniper Networks MX Series and PTX Series.
Table 56 on page 195 and Table 57 on page 197 show the mapping of OpenConfig system commandswith the relevant configuration in Junos.
194
Table 56: SSH Server Configuration
Command Name OpenConfig Configuration Junos Configuration
Timeoutopenconfig-system:system { ssh-server { config { timeout <>; } }}
system { services { ssh { client-alive-count-max 1; client-alive-interval <>; } } }
The OpenConfig timeout value is set to client-alive-interval. The leaf client-alive-count-max value is set to 1.The value must be set to 1 to overwrite the default value (3).
Session limitopenconfig-system:system { ssh-server { config { session-limit <>; } }}
system { services { ssh { connection-limit <>; } } }
The OpenConfig session-limit value is set to the Junos parameter connection-connection-limit.
Rate limitopenconfig-system:system { ssh-server { config { rate-limit <>; } }}
system { services { ssh { rate-limit <>; } } }
The OpenConfig rate-limit value is set to the Junos parameter rate-limit.
195
Table 56: SSH Server Configuration (Continued)
Command Name OpenConfig Configuration Junos Configuration
Protocol versionopenconfig-system:system { ssh-server { config { protocol-version <>; } }}
system { services { ssh { protocol-version <>; } } }
The OpenConfig protocol-version value is set to the Junos parameter protocol-version.
Enableopenconfig-system:system { ssh-server { config { enable <>; } }}
system { services { ssh { ………. } } }
The OpenConfig enable leaf value toggles the set system services ssh configuration. When enable is notconfigured, the SSH configuration is enabled by default. The model defines TRUE as the default value for the enableleaf.
196
Table 57: NTP Configuration
Command Name OpenConfig Configuration Junos Configuration
Preferopenconfig-system:system { ntp { servers { server <> { config { prefer <>; } } } }}
system { ntp { server <> prefer; }}
When the OpenConfig prefer value is set to true, the Junos prefer parameter will be set. The Junos preferparameter is a toggle and needs to be set when the OpenConfig value preferpr is set to true.
Versionopenconfig-system:system { ntp { servers { server <> { config { version <>; } } } }
system { ntp { server <> version <>; } }
The OpenConfig NTP version node value is set to the Junos parameter version.
197
Table 57: NTP Configuration (Continued)
Command Name OpenConfig Configuration Junos Configuration
Portopenconfig-system:system { ntp { servers { server <> { config { port <>; } } } }}
Not supported.
Junos doesn’t have a parameter for an NTP server port, and instead, always runs at port 1234. Consequently, theOpenConfig leaf port is not be supported.
Enabledopenconfig-system:system { ntp { config { enabled <>; } }}
system { ntp { ……… }}
The OpenConfig enable leaf value toggles the set system ntp configuration. Since its default value is FALSE, theNTP configuration is enabled only when the enable parameter is set to TRUE.
RELATED DOCUMENTATION
Mapping OpenConfig Routing Policy Commands to Junos Configuration | 183
Mapping OpenConfig Interface Commands to Junos Configuration | 152
Mapping OpenConfig Local Routing Commands to Junos Configuration | 160
Mapping OpenConfig BGP Commands to Junos Configuration | 129
Mapping OpenConfig MPLS Commands to Junos Configuration | 162
198
Mapping OpenConfig System Terminal ModelCommands to Junos Configuration
NOTE: See "OpenConfig Data Model Version" on page 3 topic to understand the data modelssupported version and its Junos OS release for Juniper Networks MX Series and PTX Series.
Table 58 on page 199 and Table 59 on page 202 show the mapping of system terminal commands withthe relevant configurations in Junos.
Table 58: gRPC Server Configuration
Command Name OpenConfig Configuration Junos Configuration
Portopenconfig-system:system { grpc-server { config { port <>; } }}
system { services { extension-service { request-response { grpc { ssl { port <>; } } } } }}
The OpenConfig port value maps to the Junos port statement.
199
Table 58: gRPC Server Configuration (Continued)
Command Name OpenConfig Configuration Junos Configuration
Listen addressopenconfig-system:system { grpc-server { config { listen-addresses <>; } }}
system { services { extension-service { request-response { grpc { ssl { address <>; } } } } }}
The OpenConfig listen-addressesis leaf-list and maps to the Junos leaf address statement. Consequently, listen-addresses is restricted to a single value.
Certificate-idopenconfig-system:system { grpc-server { config { certificate-id <>; } }}
system { services { extension-service { request-response { grpc { ssl { local-certificate <>; } } } } }}
The OpenConfig leaf certificate-id maps to the Junos statement local-certificate. The single OpenConfigcertificate value is merged with Junos certificates.
200
Table 58: gRPC Server Configuration (Continued)
Command Name OpenConfig Configuration Junos Configuration
Enableopenconfig-system:system { grpc-server { config { enable <>; } }}
system { services { extension-service { request-response { grpc { ssl { ………. } } } } }}
The OpenConfig enable leaf value toggles the set system services ssh configuration. When enable is not set, theSSH configuration is enabled by default as the data model defines TRUE as the default value for leaf enable.
Metadata-authenticationopenconfig-system:system { grpc-server { config { metadata-authentication <>; } }}
Not supported.
Metadata authentication is enabled by default in Junos. There is no Junos statement to enable or disable thisfeature.
201
Table 58: gRPC Server Configuration (Continued)
Command Name OpenConfig Configuration Junos Configuration
Transport-securityopenconfig-system:system { grpc-server { config { transport-security <>; } }}
system { services { extension-service { request-response { grpc { ssl { ……… } } } } }}
The OpenConfig leaf transport-security is a toggle to enable or disable gRPC SSL/TLS. The default value fortransport-security is TRUE. SSL is enabled by default. However, if the value for transport-security is FALSE, theconfiguration commit will fail.
Table 59: Telnet Server Configuration
Command Name OpenConfig Configuration Junos Configuration
Rate-limitopenconfig-system:system { telnet-server { config { rate-limit <>; } }}
system { services { telnet { rate-limit <>; } } }
The OpenConfig leaf rate-limit is set to the Junos telnet server rate-limit value.
202
Table 59: Telnet Server Configuration (Continued)
Command Name OpenConfig Configuration Junos Configuration
Session-limitopenconfig-system:system { telnet-server { config { session-limit <>; } }}
system { services { telnet { connection-limit <>; } } }
The OpenConfig leaf session-limit is set to the Junos telnet server connection-limit value.
Timeoutopenconfig-system:system { telnet-server { config { timeout <>; } }}
Not supported.
The OpenConfig leaf timeout is not supported on Junos.
Enableopenconfig-system:system { telnet-server { config { enable <>; } }}
system { services { telnet { …….. } } }
The OpenConfig leaf enable is a toggle to enable or disable the telnet server configuration. It's disabled or set toFALSE by default.
203
RELATED DOCUMENTATION
Mapping OpenConfig Routing Policy Commands to Junos Configuration | 183
Mapping OpenConfig Interface Commands to Junos Configuration | 152
Mapping OpenConfig Local Routing Commands to Junos Configuration | 160
Mapping OpenConfig BGP Commands to Junos Configuration | 129
Mapping OpenConfig MPLS Commands to Junos Configuration | 162
Mapping OpenConfig VLAN Commands to JunosConfiguration
NOTE: See "OpenConfig Data Model Version" on page 3 topic to understand the data modelssupported version and its Junos OS release for Juniper Networks EX Series and QFX Series.
Table 60 on page 204 to Table 63 on page 206 show the mapping of OpenConfig VLAN commands withthe relevant configuration in Junos.
Table 60: Top Level Group VLAN Configuration
Command Name OpenConfig Command Path Junos Configuration
Interface VLAN ID vlans/vlan/vlan-id set vlans vlan-name vlan-id vid
Interface VLAN Name vlans/vlan/name
VLAN Admin State vlans/vlan/status deactivate vlans vlan-name
204
Table 61: VLAN Tagged IFL Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
/ocif:interfaces/ocif:interface/ocif:subinterfaces/ocif:subinterface/vlan
VLAN ID /config/vlan-id set interfaces interface unit subinterfaceindex vlan-id vidset interfaces interface vlan-tagging
Table 62: VLAN Membership Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
/oc-if:interfaces/oc-if:interface/oc-eth:ethernet/switched-vlan
Interface Mode /config/interface-mode set interfaces ge-0/0/0 unit 0 family ethernet-switchinginterface-mode trunk (l2ng)
Native VLAN /config/native-vlan set interfaces ge-0/0/0 native-vlan-id vid (for a trunkport)set interface ge-0/0/0 unit 0 family ethernet-switchinginterface-mode trunk
Trunk VLANs /config/trunk-vlans set interfaces ge-0/0/0 unit 0 family ethernet-switchingvlan members 600set interfaces ge-0/0/0 unit 0 family ethernet-switchingvlan members [10-200]Interface-mode = TRUNK
205
Table 62: VLAN Membership Configuration (Continued)
Command Name OpenConfig Command Path Junos Configuration
Access VLAN /config/access-vlan set interfaces ge-0/0/0 unit 0 family ethernet-switchingvlan members 600Interface-mode = ACCESS
Table 63: Routed VLAN Interfaces Configuration
Command Name OpenConfig Command Path Junos Configuration
Command path prefix:
/oc-if:interfaces/oc-if:interface/routed-vlan
VLAN /config/vlan Set vlans vlan-name l3-interface irb.vid
NOTE: To create IRB IFL, configure IPv4/IPv6under routed VLAN hierarchy.
RELATED DOCUMENTATION
Mapping OpenConfig Interface Commands to Junos Configuration | 152
Mapping OpenConfig Local Routing Commands to Junos Configuration | 160
Mapping OpenConfig Network Instance Commands to Junos Operation | 178
Mapping OpenConfig Routing Policy Commands to Junos Configuration | 183
206
4CHAPTER
Configuration Statements
netconf | 208
schema | 211
track-igp-metric (LSP) | 213
netconf
IN THIS SECTION
Syntax | 208
Hierarchy Level | 210
Description | 210
Default | 210
Options | 210
Required Privilege Level | 210
Release Information | 210
Syntax
netconf { flatten-commit-results; hello-message { yang-module-capabilities { advertise-native-yang-modules; advertise-custom-yang-modules; advertise-standard-yang-modules; } } netconf-monitoring { netconf-state-schemas { retrieve-custom-yang-modules; retrieve-standard-yang-modules; } } notification; rfc-compliant; ssh { client-alive-count-max number; client-alive-interval seconds;
208
connection-limit limit; port port; rate-limit limit; } tls { client-identity client-id { fingerprint fingerprint; map-type (san-dirname-cn | specified); username username; } default-client-identity { map-type (san-dirname-cn | specified); username username; } local-certificate local-certificate; traceoptions { file <filename> <files files> <match match> <size size> <(world-readable | no-world-readable)>; flag name; level (all | error | info | notice | verbose | warning); no-remote-trace; } } traceoptions { file <filename> <files number> <match regular-expression> <size size> <world-readable | no-world-readable>; flag flag; no-remote-trace; on-demand; } yang-compliant; yang-modules { device-specific; emit-extensions; }}
209
Hierarchy Level
[edit system services]
Description
Configure the NETCONF XML management protocol.
Default
If you do not include the netconf statement, NETCONF connections are not permitted.
Options
flatten-commit-results
Suppress the <commit-results> XML subtree in the NETCONF server's response for<commit> operations. This statement must be configured in conjunction with the rfc-compliant statement.
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 7.5.
flatten-commit-results option added in Junos OS Release 21.2R1.
210
RELATED DOCUMENTATION
traceoptions (NETCONF and Junos XML Protocol)
schema
IN THIS SECTION
Syntax | 211
Hierarchy Level | 211
Description | 212
Options | 212
Required Privilege Level | 212
Release Information | 212
Syntax
schema { openconfig { unhide; }}
Hierarchy Level
[edit system]
211
Description
Specify whether OpenConfig statements are available and viewable in the CLI.
Options
openconfigunhide
Unhide the OpenConfig statements in the CLI. By default, the OpenConfig schema is notavailable through the CLI. To rehide the OpenConfig statements, use the followingcommand:
delete system schema openconfig unhide
Required Privilege Level
admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 18.3R1.
RELATED DOCUMENTATION
Installing the OpenConfig Package | 12
212
track-igp-metric (LSP)
IN THIS SECTION
Syntax | 213
Hierarchy Level | 213
Description | 213
Options | 214
Required Privilege Level | 214
Release Information | 214
Syntax
track-igp-metric <install-v4-prefixes> <install-v6-prefixes>;
Hierarchy Level
The hierarchy level for track-igp-metric globally enabled for all LSPs:
[edit protocols mpls]
The hierarchy level for track-igp-metric at the per LSP level:
[edit protocols mpls label-switched-pathpathname],
Description
Track IGP metric for LSP install prefixes
213
Options
install-v4-prefixes Track IGP metric for IPV4 prefixes.
install-v6-prefixes Track IGP metric for IPV6 prefixes.
Required Privilege Level
routing
Release Information
Statement introduced in Junos OS Release 18.4R1.
RELATED DOCUMENTATION
Install Prefix IGP Overview
214