05-09-2019 07:52 PM
Hi Experts:
There are some devices(APIC, Openstack, CPNR) which not only managed by NSO but also others
so nso will manipulate such devices fail as out of sync error
also check sync will slow performance
we want to disable check sync to these devices, are there any solutions for this ?
05-09-2019 10:47 PM
Either
admin@ncs% set devices device ce0 out-of-sync-commit-behaviour
Possible completions:
accept reject
out-of-sync-commit-behaviour - Specifies the behaviour of a commit operation involving a device that is out of sync with NCS.
Or
admin@ncs% commit no-out-of-sync-check
or
admin@ncs% commit no-overwrite
05-09-2019 10:59 PM
thanks a lot!
In my understanding, set out-of-sync-commit-behaviour accept, will just ignore out of check,
but it still will do check sync, then it will cost some performance
the second option:commit no-out-of-sync-check seems work
but our service code didn;t know how to commit no-out-of-sync-check when apply templates
do you know how to acheve this from service model code perspective ?
thanks again!
05-10-2019 03:13 PM
'but our service code didn;t know how to commit no-out-of-sync-check when apply templates'
The 'no-out-of-sync-check' is not associated with a service model or modification via code/template, it is a commit flag applied to the transaction.
In the case of cli, you make your changes and then make the commit using the flag as Hakan has stated:
admin@ncs% commit no-out-of-sync-check
For Northbound interfaces (e.g. REST) where the commit is inferred from the request the no-out-of-sync-check commit flag must be attached to the URI:
05-09-2019 11:15 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide