Configurations Applied During Onboarding for the Observability Usecase
This topic describes the Observability-related configurations that are automatically generated and committed by the Routing Director during device onboarding.
For Routing Director to automatically apply the observability-related configurations, you need to do the following:
-
Ensure that the device is part of the network implementation plan.
-
Select the Observability use case while creating a network implementation plan.
Certificate Configuration for gNMI Connectivity
When you publish the network implementation plan, Routing Director commits the following CA configuration at the device-level:
edit security certificates local gnmi-terminator.juniper.net <PEM-Privake-Key> <Certificate-Bundle> set pki ca-profile jcloud_gnmi_ca ca-identity jcloud_gnmi_ca
After Routing Director commits the configuration to the device, use the following operational commands to verify that the intended configurations have been successfully applied:
show security
gRPC Metadata and Keepalive Configuration
When you publish the network implementation plan, Routing Director commits the following configuration for gRPC metadata and keepalive configuration:
set groups jcloud-gnmi-sensors system services extension-service request-response grpc grpc-keep-alive 60 set groups jcloud-gnmi-sensors forwarding-options suppress-interface-leaf-nodes
After Routing Director commits the configuration to the device, use the following operational command to verify that the intended configurations have been successfully applied:
show apply-groups apply-groups [ global jcloud-script paragon-service-orchestration jcloud-gnmi-sensors ]