[173951] in North American Network Operators' Group
Re: ASR9K xml agent vs netconf
daemon@ATHENA.MIT.EDU (Jared Mauch)
Thu Aug 14 11:41:46 2014
X-Original-To: nanog@nanog.org
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <20140805133227.GB72334@ricotta.doit.wisc.edu>
Date: Thu, 14 Aug 2014 11:41:36 -0400
To: "Dale W. Carder" <dwcarder@wisc.edu>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Did cisco bother to open any DDTSes on the issues you saw? I=E2=80=99ve =
found that they care very little about these =E2=80=9Cautomation=E2=80=9D =
issues because they have zero automation in their lab testing that =
reflects how someone truly uses a device. I=E2=80=99ve been through =
many iterations with Cisco on this front with their ARF teams, platform =
teams, BU teams, etc.. they all have to be a very strategic engagement =
to get these things properly fixed and made usable.
I am interested in anyone trying to use any of these agents.. I suspect =
they all worked before the RP went x86 and like you said, nobody tests =
them now.
(please respond off-list)
- Jared
> On Aug 5, 2014, at 9:32 AM, Dale W. Carder <dwcarder@wisc.edu> wrote:
>=20
> 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. =20=
>=20
> There is likely a fundamental design flaw in that the cli is not =
itself=20
> 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=20=
> get (3) ddts' assigned, related to missing data compared to cli, =
endian=20
> issues, etc. My recommendation is DO NOT USE IT. =20
>=20
> I went back to screen scraping for ios-xr. Related to this and other
> issues, all of our subsequent purchases have been MX.
