Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Telemetry Interface

  • IS-IS configuration using OpenConfig (MX204, MX240, MX304, MX150, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020, and vMX)—Junos OS Release 23.2R1 introduces support for new configuration paths based on OpenConfig data model openconfig-isis.yang version 1.0.0.

    See Mapping OpenConfig ISIS Commands to Junos Configuration.

  • Support for configuring the routing-instance and source address for each gRPC tunnel session (MX204, MX240, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020, VMX, and QFX5110)—Starting with Junos OS Release 23.2R1, you can configure the routing instance and the source address for each gRPC remote procedure call (gRPC) tunnel session to dial out a connection to the tunnel server.

    To configure the routing instance, add the routing-instance <routing-instance> option and to configure the source address, add the source-address <ip-address> option in the grpc-tunnel configuration statement.

    If you do not configure a routing instance, the gRPC tunnel uses the default routing instance. If you do not configure the source address, the kernel picks the source address that can reach the tunnel server.

    [See gRPC Tunnels Overview and grpc-tunnel].

  • Telemetry streaming for IS-IS protocol based on OpenConfig data model (MX204, MX240, MX304, MX150, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020, and vMX)—Starting in Junos OS Release 23.2R1, the data model for IS-IS is compliant with OpenConfig. The node type for /network-instances/network-instance/protocols/protocol/ is defined as a list which contains user-configurable keys for the protocol name and identifier.

    [See Junos YANG Data Model Explorer.]