provisioning not reflected till 'Sync to': I am using REST API to provision SR TE policy in cluster setup. i am using no-networking = false, so that config is pushed to device. After the api is executed through shell script, SR policy is available in cluster but not in device. After 'Sync to' the config is available in device. Should i modify any other parameter in the script, so that config is pushed to device after the script execution. NSO is available in 172.20.63.132 - cnctest/Ovatest123@device in RFS - 172.20.63.148 - xrv9k-4
 Hello, I looked in all of the RFS for a device calledxrv9k-4 and couldnt find one.Attached screenshots.Please provide more information on this ticket for further troubleshooting.Regards,Janaki DuggiralaHi Janaki,There is a typo in device name. Could you please check "xrv9-4" and "xrv9-6" devices in RFS.Thanks,Sreedhar.xrv9-4 is available in 172.20.63.150 - RFS3Hello,Assuming:Your cluster is up > show clusterYou have performed a host key fetch > request cluster remote-node my-rfs-node ssh fetch-host-keysYour devices and NSO and service are all in sync > plan is reached, no commits failedI would recommend not using the no-networking field in CURL command.My command is as below (I tried to update color):::curl -is -u admin:admin -X PATCH -H "Content-type: application/yang-data+xml" -d '<data xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"> <sr-te xmlns="http://cisco.com/ns/nso/cfp/cisco-tsdn-sr-te"> <policies xmlns="http://cisco.com/ns/nso/cfp/cisco-tsdn-sr-te-sr-policies"> <policy> <name>SR-CLI-DYNAMIC</name> <head-end> <name>PIOSXR-1</name> </head-end> <tail-end>127.0.0.1</tail-end> <color>150</color> <binding-sid>111</binding-sid> </policy> </policies> </sr-te></data>' 'http://localhost:8080/restconf/data'And this worked to push config correctly to device. When I use the no-networking, indeed the config does not push correctly to device.Let me know if this is alright.Regards,Janaki DuggiralaThank you. I removed the no-networking option and config is being pushed to the device. However is it a bug in using no-networking option. Is it deprecated option?Hello, The no-networking option is not needed, since its a simple commit to update config. This is like a standard commit on the NSO CLI and with the standard commit there is a no-networking option which enables to not send anything to the device (see screen shot attached). Let me know if this helps and I will proceed to close this ticket. Thank you. Regards, Janaki DuggiralaCustomer was using incorrect params in RPC command. Assisted customer with the right command.