Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Support for Model-Driven Telemetry

Juniper Telemetry Interface has adopted Model Driven Telemetry (MDT) architecture. A model-driven network telemetry system is an advanced approach to network monitoring that leverages data models to define and collect telemetry data from network devices. In this system, data models are often defined using the YANG (Yet Another Next Generation) language to specify the structure and types of data to be collected or streamed.

Juniper currently provides two different data models:

  1. Juniper Native data model
  2. OpenConfig data model

Both models use YANG to specify the data structure and data types to be streamed.

The OpenConfig working group defines the OpenConfig data model. It is a vendor-neutral data model to configure and manage the network. OpenConfig data model generates data as Google Protocol Buffers (GPB) messages in a universal key/value format. JTI allows you to leverage OpenConfig models for a broader, vendor-agnostic view of your network.

The Juniper native data model is an open and extensible framework developed by Juniper. This model is used to stream telemetry data about the unique features found on Juniper devices. These include interface statistics, routing information, security metrics, and so on. Additionally, the native model allows for the definition of enterprise-specific sensors. To access information from Juniper or enterprise-specific sensors, subscribe to Juniper native sensors.

Note:

Choosing the right data model depends on the specific needs. You can subscribe to both OpenConfig and native sensors at the same time.

Follow the steps below to set up a model-driven telemetry solution:

  1. Set up the data collector: Configure network devices to collect and encode the data. For more information, see Telemetry Data Collector.
  2. Establish the transport protocols: Choose and configure the appropriate transport protocols for data transmission. For more information, see Telemetry Protocols.
  3. Configure the sensor: A sensor profile defines the parameters of the system resource to monitor and stream data. You can enable only one system resource to monitor each sensor profile. Configure a different sensor profile for each system resource you want to monitor. You can, however, configure more than one sensor to monitor the same system resource. For more information, see Telemetry Sensors and Sensor Paths.
  4. Create subscriptions: Set up subscriptions for the data streams you need to monitor. The telemetry session can be established in dial-in mode or dial-out mode, depending on whether the device or receiver is configured to initiate the subscription. For more information, see Telemetry Modes.