On Tue, Feb 03, 2009 at 08:10:18AM +0000, Phil Mayers wrote: > On Tue, Feb 03, 2009 at 07:11:13AM +0000, Jeffrey Ollie wrote: > >This piqued my interest, so I whipped up a quick program to do some > >testing. I've attached the resulting program, which when run against > >my 6500 running 12.2(33)SXI produces a copy of the running config. > > > >Some things I observed: > > Yep, those match my observations. > > >The script is in Python, and you'll need the Paramiko (SSHv2) and lxml > > I used Twisted & a Nevow web UI, but seems python is popular ;o)
FWIW, I've been working on NETCONF software in python for JUNOS (see a recent j-nsp thread about my frustrations...) and have the beginnings of a library for generating and parsing NETCONF documents in Python with lxml. It's got all JUNOS centric stuff, so it won't be too much help as-is, but if you're interested let me know. > ><rpc-reply xmlns="urn:ietf:params:netconf:base:1.0" message-id="101"> > > <data> > > <cli-config-data-block>! > > Yeah - note that the cli-config-data-block element is not namespaced > here. I suspect the netconf XML parser/generator is just broken in SXI. > I'm going to bug TAC later today - it's either a software or docs bug. Well, in an XML sense, it's taken the default namespace provided by the rpc-reply tag. So that is "<urn:ietf:params:netconf:base:1.0:data>". I don't know if there's a data element defined by NETCONF, so I can't speak to the well-formedness of the above XML, only its validity. Ross -- Ross Vandegrift [email protected] "If the fight gets hot, the songs get hotter. If the going gets tough, the songs get tougher." --Woody Guthrie _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
