[c-nsp] Cisco CNS initial configuration

[Brett Wooldridge]

Phil,

I'm sending back a content type of "application/xml".  Though it doesn't
seem to matter what content type I return.  I've turned on all debugging,
what I'm getting is a failure to parse the top-level tag.  Something along
the lines of "No handler for tag rpc".  I've jettisoned 'rpc' as the top
level tag and tried about twenty other tags.  I even went so far as to run
the unix 'strings' command on the uncompressed IOS image -- resulting in
about 4000 unique strings.  I've tried many of the obvious ones as top level
tags, "config", "config-data", "startup", "response", "boot", etc.  It's not
a fruitful exercise.  All result in the same error, "No handler for tag
XXX".

I'm down to putting out a call to anyone where with a Cisco Configuration
Engine (any version).  If you have said beast, would you be willing to
wireshark a 'cns config initial' conversation between a device (any IOS) and
CCE?  You'll be enriching the fountain of knowledge from which we all drink.
 I'll be happy to fully document the results here for posterity.

TIA,
Brett


On Tue, Dec 22, 2009 at 10:10 PM, Phil Mayers <p.mayers at imperial.ac.uk>wrote:

>
>> What I'm currently sending the device is this:
>>
>> <?xml version=\"1.0\" encoding=\"UTF-8\"?>
>> <rpc message-id="123" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
>>    "xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>>    <edit-config>
>>        <target><startup/></target>
>>        <default-operation>replace</default-operation>
>>        <test-option>test-then-set</test-option>
>>        <error-option>stop-on-error</error-option>
>>        <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"
>> xc:operation="replace">
>>             <cli-config-data-block>
>>                    ... config text here ...
>>             </cli-config-data-block>
>>    </edit-config>
>> </rpc>
>>
>
> What Content-Type are you sending in the HTTP headers?
>
> Have you tried the various "debug cns" commands; they seemed to provide
> varying degrees of info when I tried them (though I was trying to use
> netconf over SSH, as you say they seem to use the same underlying subsystem)
>