Uploaded image for project: 'netconf'
  1. netconf
  2. NETCONF-28

Netconf candidate capability non RFC compliant fallback


    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • 4.0.6, 5.0.1
    • None
    • netconf
    • Operating System: All
      Platform: All

      When connecting a to a Juniper EX-2200 device using the netconf connector, it reports a non RFC compliant candidate capability in the hello message:


      The Juniper reports: urn:ietf:params:xml:ns:netconf:capability:candidate:1.0

      While it should be: urn:ietf:params:netconf:capability:candidate:1.0

      When executing a change using a restconf call, ODL tries to change using the writable-runnning approach, because it does not detect the candidate capability. This is not supported by Juniper, and the request fails.

      Attached is a log file, which shows the request, starting from line 2657.

      It would be very helpful if ODL has a feature which allows more flexible checking for the candidate capability, or a fallback method for accepting the specific 'Juniper-style' candidate capability.

      The same issue might apply for the confirmed-commit capability, but I am unable to check this yet.

        1. karaf_after_applied_patch.log
          246 kB
        2. karaf_put_log.txt
          42 kB
        3. karaf.log
          282 kB

            ivanhrasko Ivan Hrasko
            erikruiter2@gmail.com Erik Ruiter
            0 Vote for this issue
            5 Start watching this issue