The console doesn't work for Juniper device.
Closed this issue · 1 comments
singhaniashrinkhala commented
I tested the console for Cisco Nexus and it worked fine.
Now testing for Juniper, I don't get any response for the bgp payload that I sent in.
I checked the logs at the device end and I see the following:
Jul 21 20:03:36 [NETCONF] Started tracing session: 27008
Jul 21 20:03:36 [NETCONF] - [27008] Outgoing: <!-- No zombies were killed during the creation of this user interface -->
Jul 21 20:03:36 [NETCONF] - [27008] Outgoing: <!-- user root, class super-user -->
Jul 21 20:03:36 [NETCONF] - [27008] Outgoing: <hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
Jul 21 20:03:36 [NETCONF] - [27008] Outgoing: <capabilities>
<capability>urn:ietf:params:netconf:base:1.0</capability>
<capability>urn:ietf:params:netconf:capability:candidate:1.0</capability>
<capability>urn:ietf:params:netconf:capability:confirmed-commit:1.0</capability>
<capability>urn:ietf:params:netconf:capability:validate:1.0</capability>
<capability>urn:ietf:params:netconf:capability:url:1.0?scheme=http,ftp,file</capability>
<capability>urn:ietf:params:xml:ns:netconf:base:1.0</capability>
<capability>urn:ietf:params:xml:ns:netconf:capability:candidate:1.0</capability>
<capability>urn:ietf:params:xml:ns:netconf:capability:confirmed-commit:1.0</capability>
<capability>urn:ietf:params:xml:ns:netconf:capability:validate:1.0</capability>
<capability>urn:ietf:params:xml:ns:netconf:capability:url:1.0?protocol=http,ftp,file</capability>
<capability>http://xml.juniper.net/netconf/junos/1.0</capability>
<capability>http://xml.juniper.net/dmi/system/1.0</capability>
Jul 21 20:03:36 [NETCONF] - [27008] Outgoing: </capabilities>
Jul 21 20:03:36 [NETCONF] - [27008] Outgoing: <session-id>27008</session-id>
Jul 21 20:03:36 [NETCONF] - [27008] Outgoing: </hello>
Jul 21 20:03:36 [NETCONF] - [27008] Outgoing: ]]>]]>
Jul 21 20:03:36 [NETCONF] - [27008] Incoming: <?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<capabilities>
<capability>urn:ietf:params:netconf:base:1.0</capability>
<capability>urn:ietf:params:netconf:base:1.1</capability>
</capabilities>
</hello>]]>]]>
Jul 21 20:03:36 [NETCONF] - [27008] Incoming:
#144
<?xml version="1.0" encoding="UTF-8"?>
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
message-id="1">
#205
<rpc>
<get-config>
<source><running/></source>
<filter type="subtree">
<bgp xmlns="http://openconfig.net/yang/bgp">
</bgp>
</filter>
<get-config>
</rpc>
#6
</rpc>
##
Jul 21 20:03:36 [NETCONF] - [27008] Outgoing: <!-- netconf error: unknown command -->
Jul 21 20:03:36 [NETCONF] - [27008] Debug: The last token parsed by mgd [27008] was [
#144] and gram data current token [
#144]
Jul 21 20:03:36 [NETCONF] - [27008] Outgoing: <!-- session end at 2017-07-21 20:03:36 UTC -->
I tested the same payload, directly via ssh, and it worked. This is my payload:
<rpc>
<get-config>
<source><running/></source>
<filter type="subtree">
<bgp xmlns="http://openconfig.net/yang/bgp">
</bgp>
</filter>
</get-config>
</rpc>
]]>]]>
Any pointers on where I could be going wrong with this?
aashaikh commented
You probably don't mean to open this issue here in the ONF OF-Config repository -- you could ask Juniper, or post on the OpenConfig mailing list.