Symptom
When configuring an operation with a source-port and ip address the ID of the operation gets truncated by another one randomly
aacrt01-mr23.n01(config)#no ip sla 1000932
aacrt01-mr23.n01(config)#ip sla 1000932
aacrt01-mr23.n01(config-ip-sla)# udp-jitter x.x.x.3 5054 source-ip y.y.y.y source-port 5056 control disable interval 10
aacrt01-mr23.n01(config-ip-sla-jitter)# tos 72
aacrt01-mr23.n01(config-ip-sla-jitter)# vrf VAVRF
aacrt01-mr23.n01(config-ip-sla-jitter)# tag aacrt01-gwnrt01
aacrt01-mr23.n01(config-ip-sla-jitter)#
aacrt01-mr23.n01(config-ip-sla-jitter)#no ip sla 1000942
aacrt01-mr23.n01(config)#ip sla 1000942
aacrt01-mr23.n01(config-ip-sla)# udp-jitter x.x.x.4 5054 source-ip y.y.y.y source-port 5056 control disable interval 10
%Source port 5056 is already in use by operation 17892 (1000932 truncated).
Conditions
ASR1004-10G-VPN/K9 running version 3.16.8S
configuring UDP-JITTER operations
Workaround
Workaround is to configure udp-jitter probes with unique source-port with old release and then upgrade to XE3.16.8s.
In that case, udp-jitter probe configurations will be restored without any issues.
Further Problem Description
N/A
