Hi all, sorry for not replying earlier.
We will continue evaluating YANG in the lab as we have now upgraded one box to 6.0.1 and there is Cisco-IOS-XR-ipvX-acl-cfg.yang. Currently we still have other issues with 6.0.1 like totally broken netflow... Best regards, Chris On Thu, May 12, 2016 at 4:02 PM, Phil Mayers <p.may...@imperial.ac.uk> wrote: > On 12/05/16 12:49, chip wrote: > >> I don't really get the benefit of using XML wrapped cli commands and >> output >> via XML. One must still ssh to the device and the output is the same as >> the CLI with just an <output></output> tag wrapped around the results of >> > > Depends on the vendor. It's obviously not ideal, but at least in theory it > can be a marginal improvement over using expect-over-CLI, if for no other > reason than you don't have to much around with parsing the reply e.g. > detecting prompt-as-end-of-data, pager, setting term len 0, etc. > > If you're *really* lucky, the CLI-over-XML API will actually distinguish > between a successful command and a failed command. > > You do still have to screen-scrape the actual command output, which > obviously sucks. > > On the downside I've seen platforms that don't XML-escape the CLI output, > so a CLI command like: > > # sh int desc > ... > Vlan10 up up NOC & others > > ...ends up as on-the-wire XML: > > <output> > ... > Vlan10 up up NOC & others > </output> > > i.e. the & doesn't get turned to & and similarly with <>. > > This level of fail is, obviously, worse than useless. > > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/