Closed nsinha123 closed 1 year ago
klacke
commented
8 years ago Interesting, alcalu and NOKIA URNs.
However, the device is not std compliant yet. It's sending broken XML. The NETCONF impl there needs more work.
I'm not sure where to start, but you must take this with the manufacturer of the device.
For example the rpc-error, a proper one looks as:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="3">
nsinha123
commented
8 years ago Hi Klacke
Thanks a lot for replying back in such a sort time and explaining everything in details.
Incidentally I posted the same question in stackoverflow and one knowledgeable person has replied that while sending get-config request to the server, the JNC client should send the message-id in default namespace instead of the nc namespace. Please look at here - stackoverflow. So do you agree with him, should we change JNC to make the message-id in default namespace?
Thanks in advance...
klacke
commented
8 years ago On 29/06/16 19:42, nsinha123 wrote:
Hi Klacke
Thanks a lot for replying back in such a sort time and explaining everything in details.
Incidentally I posted the same question in stackoverflow and one knowledgeable person has replied that while sending get-config request to the server, the JNC client should send the message-id in default namespace instead of the nc namespace. Please look at here - stackoverflow http://stackoverflow.com/questions/38099946/netconf-not-able-to-perform-getconfig/38102036#38102036. So do you agree with him, should we change JNC to make the message-id in default namespace?
Hmmm, maybe, from an aesthetics POV, OTOH correct XML is correct XML. Weather the default ns is used or an explicit ns is used is irrelevant. Both are correct. All XML parsers should cope equally well with both. If not, they are buggy and cannot parse XML.
The problem at hand here isn't what the client sends, but what the agent replies with - which wasn't XML
/klacke
nsinha123
commented
8 years ago Hi Klacke, I am now able to make it work. I had to modify the NetconfSession.java and modified line 1618 as follows – //out.print("<" + nc + "rpc " + xmlnsAttr + " " + nc + "message-id=\""); out.print("<" + nc + "rpc " + xmlnsAttr + " " + "message-id=\""); You can see that I have removed the nc namespace and bingo. I am able to send get-config to the router and get reply. So the router was not able to detect the message-id properly and crying. After it gets the proper message-id it sends the proper XML. So do you think there is anything wrong with the JNC code? Thanks for your help.
klacke
commented
8 years ago On 30/06/16 08:26, nsinha123 wrote:
Hi Klacke, I am now able to make it work. I had to modify the NetconfSession.java and modified line 1618 as follows – //out.print("<" + nc + "rpc " + xmlnsAttr + " " + nc + "message-id=\""); out.print("<" + nc + "rpc " + xmlnsAttr + " " + "message-id=\""); You can see that I have removed the nc namespace and bingo. I am able to send get-config to the router and get reply.
Which mean that JNC is now sending erroneous XML
So the router was not able to detect the message-id properly and crying.
Also, if there ever are errors. The router will still send the badly formatted rpc-error.
After it gets the proper message-id it sends the proper XML.
That patch above now means that JNC instead of sending
nsinha123
commented
8 years ago Thanks Klacke for your great explanation.
Hi We have a netconf enabled router and I am able to perform get/get-config operations using Mg-Soft client browser. This is the output of getConfig() -
REQ:
RESP:
But I am unable to perform the same operation using tailf Netconf client. Here is my code -
I am getting the following in the eclipse console -
I have been debugging this issue for a long time, but I am unable to fix it. Can you please help me out? I will be really indebted to you.
Thanks and regards...