-
Bug
-
Resolution: Done
-
Medium
-
Beijing Release
-
None
-
None
Using a Juniper vMX 18.1:
Symptom for edit-config:
Jun 5 20:37:24 [NETCONF] - [16025] Incoming: <?xml version="1.0" encoding="UTF-8"?> <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1"> <edit-config> <target> <candidate /> </target> <default-operation>merge</default-operation> <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> <configuration xmlns="http://yang.juniper.net/junos/conf/root"> <interfaces xmlns="http://yang.juniper.net/junos/conf/interfaces"> <interface> <name>fxp0</name> <unit> <name>0</name> <description>pfe 10.195.198.23 access through this port</description> <family> <inet> <address> <name>10.195.198.22/24</name> </address> </inet> </family> </unit> <speed>1g</speed> </interface> </interfaces> </configuration></config>Jun 5 20:37:24 [NETCONF] - [16025] Incoming: <?xml version="1.0" encoding="UTF-8"?> <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1"> <edit-config> <target> <candidate /> </target> <default-operation>merge</default-operation> <config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0"> <configuration xmlns="http://yang.juniper.net/junos/conf/root"> <interfaces xmlns="http://yang.juniper.net/junos/conf/interfaces"> <interface> <name>fxp0</name> <unit> <name>0</name> <description>pfe 10.195.198.23 access through this port</description> <family> <inet> <address> <name>10.195.198.22/24</name> </address> </inet> </family> </unit> <speed>1g</speed> </interface> </interfaces> </configuration></config> </edit-config> </rpc>]]>]]> Jun 5 20:37:24 [NETCONF] - [16025] Outgoing: <nc:rpc-reply xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="http://xml.juniper.net/junos/18.1I0/junos" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1"> Jun 5 20:37:24 [NETCONF] - [16025] Outgoing: <nc:ok/> Jun 5 20:37:24 [NETCONF] - [16025] Outgoing: </nc:rpc-reply> Jun 5 20:37:24 [NETCONF] - [16025] Outgoing: ]]>]]>
Symptom for commit:
Jun 5 20:37:25 [NETCONF] - [16025] Incoming: <?xml version="1.0" encoding="UTF-8"?> <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1"> <commit/> </rpc> ]]>]]> Jun 5 20:37:25 [NETCONF] - [16025] Outgoing: <nc:rpc-reply xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="http://xml.juniper.net/junos/18.1I0/junos" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1"> Jun 5 20:37:26 [NETCONF] - [16025] Outgoing: <nc:ok/> Jun 5 20:37:26 [NETCONF] - [16025] Outgoing: </nc:rpc-reply> Jun 5 20:37:26 [NETCONF] - [16025] Outgoing: ]]>]]> Jun 5 20:3 </edit-config> </rpc>]]>]]> Jun 5 20:37:24 [NETCONF] - [16025] Outgoing: <nc:rpc-reply xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="http://xml.juniper.net/junos/18.1I0/junos" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1"> Jun 5 20:37:24 [NETCONF] - [16025] Outgoing: <nc:ok/> Jun 5 20:37:24 [NETCONF] - [16025] Outgoing: </nc:rpc-reply> Jun 5 20:37:24 [NETCONF] - [16025] Outgoing: ]]>]]>
As you can see, the last outgoing message is not the <rpc-reply> as expected, but the trailing ]]>]]>