[173779] in North American Network Operators' Group
Re: ASR9K xml agent vs netconf
daemon@ATHENA.MIT.EDU (Corey Touchet)
Tue Aug 5 09:42:56 2014
X-Original-To: nanog@nanog.org
From: Corey Touchet <corey.touchet@corp.totalserversolutions.com>
CC: NANOG <nanog@nanog.org>
Date: Tue, 5 Aug 2014 13:42:18 +0000
In-Reply-To: <20140805133227.GB72334@ricotta.doit.wisc.edu>
Errors-To: nanog-bounces@nanog.org
I always preferred the displays where you have commands without all the
bracket garbage and just indented text for sub items.
On the MX the show configuration | display set is about as close as you
can get, but it=B9s workable. Kudo=B9s is that you can just dump it in as
well and get what you want. I think the only time I really get annoyed at
the JunOS configurations is when I=B9m staring down any of their switches.
On 8/5/14, 7:32 AM, "Dale W. Carder" <dwcarder@wisc.edu> wrote:
>
>Thus spake Jeremy (jbaino@gmail.com) on Fri, Aug 01, 2014 at 03:07:19PM
>-0700:
>>=20
>> I'm currently working on writing some automation around the ASR9K
>>platform
>> and I've been looking at both the netconf and xml interfaces. Anyone
>>have
>> experience with either?
>>=20
>> It looks like the XML interface is much more feature rich, supporting
>>both
>> config and operational state objects where netconf is limited to config
>> only.
>>=20
>> Currently I'm leaning towards the xml interface,
>
>I wasted a week of my life trying to get xml interface on n9k to work
>correctly. I would never use it again, as it obviously gets no QA.
>
>There is likely a fundamental design flaw in that the cli is not itself
>an xml client like you see on other platforms. The XML interface, and
>CLI (presumably netconf) may all be distinct clients to sysdb. I did
>get (3) ddts' assigned, related to missing data compared to cli, endian
>issues, etc. My recommendation is DO NOT USE IT.
>
>I went back to screen scraping for ios-xr. Related to this and other
>issues, all of our subsequent purchases have been MX.
>
>Dale
>AS{59,2381,3128}
