Ask Your Question
0

Confusion adding Juniper Device to ODL using netconf-connector

asked 2016-06-23 13:05:49 -0700

asilver gravatar image

Hello All,

I'm trying to add a Juniper switch to Opendaylight database. The Juniper device supports netconf but it does NOT list netconf monitoring nor it's YANG capabilities in the Netconf hello exchange. In the Open Daylight user guide (I'm using Beryllium SR2), Chapter 34, there are instructions for "Connecting to a device not supporting NETCONF monitoring". I'm trying to following item 2 (NETCONF device does not support ietf-netconf-monitoring and it does NOT list its YANG models as capabilities in HELLO message). The documentation states to modify the configuration of netconf-connector by adding some XML statements. My question is what exact file do I add this to? Am I supposed to manually create a new file for this device in the directory below:

[allan@SDNAUTOS02 karaf]$ pwd

/home/allan/ODL/distribution-karaf-0.4.2-Beryllium-SR2/etc/opendaylight/karaf

[allan@SDNAUTOS02 karaf]$ ls -l

total 72

-rw-r--r--. 1 as2863 domain users 3791 Jun 15 22:20 00-netty.xml

-rw-r--r--. 1 as2863 domain users 24486 Jun 15 22:20 01-md-sal.xml

-rw-r--r--. 1 as2863 domain users 6750 Jun 15 22:20 01-netconf.xml

-rw-r--r--. 1 as2863 domain users 10705 Jun 15 22:20 05-clustering.xml

-rw-r--r--. 1 as2863 domain users 2218 Jun 15 22:20 06-clustered-entity-ownership.xml

-rw-r--r--. 1 as2863 domain users 985 Jun 15 22:20 08-aaa-h2-store-config.xml

-rw-r--r--. 1 as2863 domain users 985 Jun 15 22:20 08-aaa-idmlight-config.xml

-rw-r--r--. 1 as2863 domain users 1661 Jun 15 22:21 10-restconf-service.xml

-rw-r--r--. 1 as2863 domain users 1803 Jun 15 22:21 10-rest-connector.xml

-rw-r--r--. 1 as2863 domain users 3771 Jun 15 22:20 99-netconf-connector.xml

[allan@SDNAUTOS02 karaf]$

OR

do I add the XML statements to the file:

/home/allan/ODL/distribution-karaf-0.4.2-Beryllium-SR2/etc/opendaylight/current/controller.currentconfig.xml

Note, the new device I'm trying to add is already present in the In the currentconfig.xml file. When using the POSTMAN to send RESTCONF GET commands, the status says "not connected". That makes sense because I need to setup the netconf-connector.

Thanks in advance

edit retag flag offensive close merge delete

Comments

Did you ever get ODL connected to a Juniper device? I'm trying to do the same thing.

berkheimert ( 2016-12-01 19:20:54 -0700 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-02-20 05:32:40 -0700

I got usable NETCONF ODL (0.5.2-Boron-SR2) connector with Junos (VMX 16.1r10).

  1. Get yang model for Junos from https://forums.juniper.net/t5/Automat... ( https://forums.juniper.net/jnet/attac... )

  2. Put it to cache/schema as configuration@2014-11-13.yang

  3. Restart ODL (I don`t sure what its really need, but I did it)

  4. Use POSTMAN to add NetconfDevice (POST): <module xmlns="urn:opendaylight:params:xml:ns:yang:controller:config"> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">prefix:sal-netconf-connector</type> <name>PE-1</name>

    172.16.16.1
    <port xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">830</port> <username xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">root</username> <password xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">passw0rd</password> <tcp-only xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf">false</tcp-only> <yang-module-capabilities xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"> <capability>http://xml.juniper.net/xnm/1.1/xnm?module=configuration&revision=2014-11-13</capability> </yang-module-capabilities> <event-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:netty">prefix:netty-event-executor</type> <name>global-event-executor</name> </event-executor> <binding-registry xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">prefix:binding-broker-osgi-registry</type> <name>binding-osgi-broker</name> </binding-registry> <dom-registry xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:md:sal:dom">prefix:dom-broker-osgi-registry</type> <name>dom-broker</name> </dom-registry> <client-dispatcher xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:config:netconf">prefix:netconf-client-dispatcher</type> <name>global-netconf-dispatcher</name> </client-dispatcher> <processing-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:threadpool">prefix:threadpool</type> <name>global-netconf-processing-executor</name> </processing-executor> <keepalive-executor xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"> <type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:threadpool">prefix:scheduled-threadpool</type> <name>global-netconf-ssh-scheduled-executor</name> </keepalive-executor> </module>

  5. Use POSTMAN to view Netconf topology (GET) http://192.168.5.199:8181/restconf/op... , device should have status "connected" with some capabilities like this: { "node-id": "PE-1", "netconf-node-topology:available-capabilities": { "available-capability": [ "urn:ietf:params:netconf:capability:confirmed-commit:1.0", "urn:ietf:params:netconf:capability:candidate:1.0", "urn:ietf:params:xml:ns:netconf:capability:confirmed-commit:1.0", "urn:ietf:params:netconf:capability:validate:1.0", "http://xml.juniper.net/netconf/junos/1.0", "urn:ietf:params:xml:ns:netconf:base:1.0", "urn:ietf:params:xml:ns:netconf:capability:url:1.0?protocol=http,ftp,file", "urn:ietf:params:netconf:base:1.0", "urn:ietf:params:xml:ns:netconf:capability:validate:1.0", "urn:ietf:params:xml:ns:netconf:capability:candidate:1.0", "(http://xml.juniper ...

(more)
edit flag offensive delete publish link more
Login/Signup to Answer

Question Tools

Follow
1 follower

Stats

Asked: 2016-06-23 13:05:49 -0700

Seen: 304 times

Last updated: Feb 20