IOS XE and XR Telemetry Ingestion - Configuration and Deployment

This article explains how to deploying the default IOS XR and IOS XE telemetry ingestion pipeline, with either a Dial-Out or Dial-In connectivity configuration between the router and the Telemetry Collector.

Setting up a Data Ingestion Pipeline

The Telemetry Collector receives and ingests a default set of sensor path telemetry metrics that are being streamed out of the IOS XR and IOS XE devices on a user-defined cadence.

To set up a data ingestion pipeline, you must deploy the Sensor Collector in a location accessible to both the Telemetry Collector and Provider Connectivity Assurance.

Both the Sensor Collector and Telemetry Collector are deployed as Docker containers but have slightly different installation methods:

Sensor Collector: Downloaded from Provider Connectivity Assurance through the user interface, transferred to the target machine, extracted, and run via a shell script.

Telemetry Collector: Installed using Docker Compose, which automatically pulls the required binaries.

Important It is recommended to deploy the Sensor Collector before the Telemetry Collector.
Deploying them in reverse order may trigger warning messages if the Telemetry Collector cannot locate a Sensor Collector to which it can connect. The instructions below deploy the Sensor Collector first, followed by the Telemetry Collector.

Step 1: Configure and Deploy Sensor Collector

Here are the docker-based instructions for configuring and deploying the Sensor Collector to work with a Telemetry Collector: Instructions to configure and deploy Sensor Collector for IOS Telemetry

Step 2: Configure and Deploy Telemetry Collector

To build a Telemetry Collector instance for IOS XR or IOS XE ingestion, you have a two options, based on whether you want MDT Dial-Out or gNMI Dial-In connectivity with the router:

• MDT Dial-Out: Follow these instructions to leverage the User Interface to create a Telemetry Collector configuration that connects via MDT Dial-Out.
  • Note that if you prefer to use API calls rather than the User Interface to create the Telemetry Collector configuration, refer to these instructions

Once configured, refer to Deploying Telemetry Collector for the detailed steps to deploy the Telemetry Collector.

• gNMI Dial-In - Alternatively you can use APIs to create a Telemetry Collector run time configuration that connects via gNMI Dial-In. Follow the instructions here to fully configure and deploy the Telemetry Collector for this option.

Step 3: Configure the Router to Stream to the Telemetry Collector

Refer to IOS XR - Stream Telemetry via gNMI Dial-Out to set up an IOS XR router to stream telemetry to the Telemetry Collector (and ultimately through to Provider Connectivity Assurance)

Refer to IOS XE - Stream Telemetry via MDT Dial-Out to set up an IOS XE router to stream telemetry to the Telemetry Collector (and ultimately through to Provider Connectivity Assurance)

With these steps, you have completed building the telemetry ingestion pipeline and your telemetry should be reaching Provider Connectivity Assurance. Move on to Step 3: Enabling Data in Provider Connectivity Assurance