[c-nsp] IOS-XR 5.3.3 add Yang Models

[chip]

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
the command.  The output is not formatted in any structured way so one is
still effectively "screen scraping".  There does seem to be methods for
getting operational data in a more formatted output but trying to find the
proper XML query and understanding the responses are confusingly
difficult.  At least for me, perhaps I'm just ignorant in the methods.
Enlightenment is appreciated.

I recently attended a Cisco webinar going over some of the new capabilities
and methods for interacting with IOS-XR in >v6.0 and things seem a good
deal more user friendly.  So at least there is progress being made and I'm
very happy to see that.

--chip

On Thu, May 12, 2016 at 6:12 AM, Joshua Morgan <joshua.morgan at gmail.com>
wrote:

> Have you considered the IOS XR XML API?
>
> From memory, it's essentially a wrapper to the CLI.
>
> Josh
>
> On Thursday, 12 May 2016, Christian Kildau <lists at chrisk.de> wrote:
>
> > (That last message was actually intended for the list.)
> >
> > On Wed, May 11, 2016 at 4:02 PM, Phil Mayers <p.mayers at imperial.ac.uk
> > <javascript:;>>
> > wrote:
> >
> > > On 11/05/16 14:56, Christian Kildau wrote:
> > >
> > >>
> > >> That's pretty bad news, as the supplied models don't offer much
> > >> functionality from what we can tell. At least in 5.3.3.
> > >>
> > >
> > > A sadly familiar state of affairs. The laughable Netconf support on
> > > 6500/sup720 had virtually zero functionality. XML transport without
> > > anything to actually send over it.
> > >
> > > I look to vendors other than Cisco for automation these days.
> > >
> >
> > That doesn't help if you already have your Cisco gear deployed :)
> >
> > As a side note: IOS-XR on ASR9k states to
> > support draft-ietf-idr-flowspec-redirect-ip, but what they missed is
> > implementing the C (copy) bit feature to duplicate packets to a tcpdump
> > host in our case. Instead it just silently ignores the copy bit and
> > redirects all packets leaving the real dst inaccessible.
> >
> > That's why we were now looking at spanning the port with an ACL applied
> > that we dynamically adjust via netconf... But yet another fail. Looks
> like
> > we still have to use ssh / cli input in our scripts in 2016.
> >
> > Best regards,
> > Chris
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net <javascript:;>
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>



-- 
Just my $.02, your mileage may vary,  batteries not included, etc....