NCS CLI can be used to generate preview of these configs as well. API provides an ability to extract the same preview output that would be obtained from CLI. From Config mode of NCS CLI,       To create/modify services — set services <$serviceName> <$KeyParam1Val> <$dyanamicParam2> <$dyanamicParam2Val>  …….           Commit dry-run out format native       To delete  services — delete services <$serviceName> <$KeyParam1Val>              Commit dry-run out format native           Example for using the NCS RequestActionTh API for accomplishing the same preview as above:       /**        * Execute NCS Commit Dry run Action        *        * @param params        *            - an array of ConfXMLParam, parameters for completing the        *            action        * @param output        *            - A list of ConfXMLParam, parameters for output        * @param maapi        *            -- Maapi , session object        * @param th        *            -- int , session index        * @param reviewErrIndexNum        *            -- String, Error index Number        * @param reviewErrMsg        *            -- String, Error index Message        * @param service        *            -- String, Service Name        * @throws ConfException        * @throws IOException        *        */       private void executeNCSCommitDryRun(ConfXMLParam[] params ,               List<ConfXMLParam> output , Maapi maapi , int th ,               String reviewErrIndexNum , String reviewErrMsg , String service )                       throws ConfException, IOException {           ConfNamespace ncsNS = null ;           ConfXMLParam[] diffNative = null ;           ConfXMLParam[] diff = null ;           String previewDiffSetValue = null ;               ncsNS = new Ncs();           diffNative = new ConfXMLParam[]{ new ConfXMLParamValue( ncsNS .hash(),                   Ncs. _outformat , new ConfEnumeration(2))};           diff = maapi .requestActionTh( th , diffNative , "/services/commit-dry-run" );               previewDiffSetValue = generatePreviewDiffSetValue(ConfXMLParam                   .toXML( diff )) != null                   ? generatePreviewDiffSetValue(ConfXMLParam.toXML( diff ))                           : "" ;                       LOGGER .info( "Extracted Preview Value: " + previewDiffSetValue );                       EnterpriseOnboardUtility.setErrorReturn( output ,                           Integer.parseInt( reviewErrIndexNum ), reviewErrMsg ,                           previewDiffSetValue ); ... View more

Don’t think we have a notion of protected/unprotected. For some of the NEDs we actually just hash the entire config to be able compare and compute the check-sync. The APIC NED comes to mind. It sort of has the notion of protected/unprotected. Basically with the APIC NED, one can spell out the sections of the device tree that is to be managed by NSO (sync’ed into CDB) and the rest is left out. ... View more

an XPath expression returns an XPath value, string, number, boolean or date. You just select a node with no content. To illustrate I will use the ncs_cmd utility using the 'xe' command, short for XPath Expression: » ncs_cmd -c "xe /devices/device[name='ios0']/config/ios:router/bgp/as-no" 64512 This returns the text representation of the node as-no, we can also write explicitly: » ncs_cmd -c "xe /devices/device[name='ios0']/config/ios:router/bgp/as-no/text()" 64512 Selecting a node with no content will yield an empty result: » ncs_cmd -c "xe /devices/device[name='ios0']/config/ios:router/bgp/bgp" We are in fact selecting a node it just do not have any content, verify with the XPath function count() » ncs_cmd -c "xe count(/devices/device[name='ios0']/config/ios:router/bgp/bgp)" 1 What you want is to test if something exists or not, an empty node-set is always false, a non-empty is always true. You can test that by using the XPath function boolean(): » ncs_cmd -c "xe boolean(/devices/device[name='ios0']/config/ios:router/bgp[as-no=64512])" true » ncs_cmd -c "xe boolean(/devices/device[name='ios0']/config/ios:router/bgp[as-no=64513])" false For more one XPath please consult: https://www.w3.org/TR/xpath/ ... View more

You should use NavuList.children(), i.e. " for (NavuContainer test2: testlist1.children()){" ... View more

We have used both, it depends on what you are trying to do: During sync-from: good for HW resources. These things do not change via config changes and you always will do a sync-from when you add hardware. You will have an inventory list in the device container. Using reactive-fastmap: good for config resources (IPS, vlans, interface counts). These are typically checks that you want to perform using reactive fastmap as their status changes as services evolve. ... View more