Configurations Applied During Onboarding for the Active Assurance Usecase
This topic describes the Active Assurance-related configurations that are automatically generated and committed by the Routing Director during device onboarding.
For Routing Director to automatically apply the Active Assurance-related configurations, you need to do the following:
-
Ensure that the device is part of the network implementation plan.
-
Select the Active Assurance use case while creating a network implementation plan.
-
Enable and configure Neighbour Ping Test Parameters, Edge Devices, and Internet Endpoints in the device profile.
Test Agent Installation and Connectivity Tests Configurations
When you publish the network implementation plan that includes devices running Junos OS Evolved, Routing Director commits the following configurations to install the Test Agent Application Docker container on the device:
set services paa test-agent cc-host VIP-Address-of-Active-Assurance set services paa test-agent cc-account 04b1e083-30c4-4174-8308-613fb8fe3561 set services paa test-agent cc-user "loop-secret-key@paa.juniper.net" set services paa test-agent cc-password "Password" set services paa test-agent ta-version latest set services paa test-agent ta-name PE1_TA3 set services paa test-agent cc-insecure set services paa test-agent additional-args --log-level=debug set processes nlsd enable
At the time of onboarding, Routing Director runs a Test to validate connectivity to the required endpoints and cloud services. Test runs for the duration specified in Neighbouring Ping Duration. The required configuration is applied during the Test execution and is automatically removed when the Test execution completes.
For example, you can run a test using the RPM plugin. Following is the sample configuration:
# Group configuration
services {
rpm {
probe dmgw-p5095721754300089765 {
test dmgw-t5095721754300089765 {
probe-type icmp-ping;
target address 10.32.20.229;
probe-count 1;
test-interval 10;
history-size 512;
ttl 64;
}
}
}
}
# Apply group configuration where the above group is applied.
## Last changed: 2026-04-27 07:42:02 PDT
apply-groups [ global member0 mist-script paa-dmgw-plugin-rpm_ping-mmt-5095721754300089765 ];After Routing Director commits the configuration to the device, use the following operational command to verify whether Test Agent is installed on the device:
show configuration services paa
If you have disabled Wait for Test Results in the device profile, Routing Director configures the following tests:
-
Cisco TWAMP Reflector configuration
ipsla responder twamp ! ! server twamp port 862 ! !
-
Cisco IPSLA Ping configuration
ipsla operation 1025 type icmp echo source address 10.48.53.16 destination address 10.48.53.2 datasize request 64 frequency 10 statistics interval 30 buckets 1 ! ! ! schedule operation 1025 start-time now life forever ! !