: Addressed Issues in OpenConfig Plugin 2.1.3-h3
Focus
Focus

Addressed Issues in OpenConfig Plugin 2.1.3-h3

Table of Contents

Addressed Issues in OpenConfig Plugin 2.1.3-h3

Learn about addressed issues in the OpenConfig Plugin 2.1.3-h3.
The following are addressed issues in the OpenConfig 2.1.3-h3 version of the plugin.

PLUG-24363

Two issues with OpenConfig plugin dial-out streaming telemetry to external collectors (Ext-Client) have been resolved:
1. Ext-Client Configuration Now Persists Across Reboots
Previously, selecting Ext-Client as the dial-out region and configuring the collector endpoint were lost on every plugin restart, device reboot, or plugin upgrade, requiring manual reconfiguration each time. The Ext-Client selection and collector FQDN now persist automatically — dial-out reconnects to the external collector after any restart without operator intervention.
2. Insecure TLS Support for External Collector Dial-Out
Dial-out to external collectors (Ext-Client) previously required full mutual TLS, including a device client certificate. On devices with expired or unusable device certificates, or against collectors that do not require a client certificate, the TLS handshake failed and telemetry could not flow. Ext-Client dial-out now uses insecure TLS: no client certificate is presented and the collector's server certificate is not verified. Traffic remains encrypted in transit. This change applies exclusively to Ext-Client — all managed regions (device telemetry, AIOps) continue to use full secure mutual TLS, unchanged.
New CLI Value
A new DT-Client value has been added to the set-client command to return from Ext-Client back to the managed dial-out path:
request plugins openconfig streaming_telemetry dial-out-enable set-client DT-Client
This reverts the region to the device's managed telemetry region, restores the device-telemetry/AIOps collector endpoint, clears persisted Ext-Client state, and re-enables full mutual TLS.