I want to use services deep-check-sync to verify if all service involved devices still have expected configuration. Here is my test scenario:
1. deploy a l3vpn service instance
2. issue service check-sync, return in-sync true
3. issue device check-sync to all involved devices, all in sync
4. issue service deep-check-sync, return in-sync false
5. check details:
admin@ncs(config)# services l3vpn testvpn1001 deep-check-sync outformat cli
cli {
local-node {
data devices {
device R203 {
config {
cisco-ios-xr:route-policy testvpn1001 {
- value " pass\r
";
+ value pass;
}
}
}
device R205 {
config {
cisco-ios-xr:route-policy testvpn1001 {
- value " pass\r
";
+ value pass;
}
}
}
}
}
}
The NSO and NED info are
build-info package name cisco-iosxr
build-info package version 6.2.1
build-info package ref 6.2.1
build-info package sha1 0fd63fb
build-info ncs version 4.4.2
It seems there are some discrepancy between real router configure and service expected configuration. These route-policy configure is pushed to router by NSO service commit. So what NSO sent to router and saved expected service configuration in CDB are different.
Could any one shed some light on this? any work around?
Thanks,
Jamie
