I have had install (probably this module is not istalled by default) odl-netconf-topology (in karaf shell: feature:install odl-netconf-topology ) and after restarting of ODL I can see PE-2 adn xrv-P1 nodes at operational datastore too. Also, I`am able to get config portions of these nodes over REST (Postman). I will try again later with latest version of Junos yang from github (for 16.1 junos release).
opendaylight-user@root>feature:list | grep odl-netconf
odl-netconf-all | 1.1.2-Boron-SR2 |
odl-netconf-api | 1.1.2-Boron-SR2 | x
odl-netconf-mapping-api | 1.1.2-Boron-SR2 | x
odl-netconf-util | 1.1.2-Boron-SR2 | x
odl-netconf-impl | 1.1.2-Boron-SR2 | x
odl-config-netconf-connector | 1.1.2-Boron-SR2 | x
odl-netconf-netty-util | 1.1.2-Boron-SR2 | x
odl-netconf-client | 1.1.2-Boron-SR2 | x
odl-netconf-monitoring | 1.1.2-Boron-SR2 | x
odl-netconf-notifications-api | 1.1.2-Boron-SR2 | x
odl-netconf-notifications-impl | 1.1.2-Boron-SR2 | x
odl-netconf-ssh | 1.1.2-Boron-SR2 | x
odl-netconf-tcp | 1.1.2-Boron-SR2 | x
odl-netconf-mdsal | 1.4.2-Boron-SR2 |
odl-aaa-netconf-plugin | 1.1.2-Boron-SR2 | x
odl-aaa-netconf-plugin-no-cluster | 1.1.2-Boron-SR2 |
odl-netconf-connector-all | 1.1.2-Boron-SR2 | x
odl-netconf-connector | 1.1.2-Boron-SR2 | x
odl-netconf-connector-ssh | 1.1.2-Boron-SR2 | x
odl-netconf-topology | 1.1.2-Boron-SR2 | x
odl-netconf-clustered-topology | 1.1.2-Boron-SR2 |
odl-netconf-console | 1.1.2-Boron-SR2 |
opendaylight-user@root>
1. Get yang model for Junos from https://forums.juniper.net/t5/
2. Put it to cache/schema as configuration@2014-11-13.yang
3. Restart ODL
4. Use POSTMAN to add NetconfDevice via REST:
Junos does not list his capabilities in hello message, so add it manually:
Put node to config datastore:
<node xmlns="urn:TBD:params:xml:ns:yang:network-topology">
<node-id>PE-2</node-id>
<host xmlns="urn:opendaylight:netconf-node-topology">172.16.16.2</host>
<port xmlns="urn:opendaylight:netconf-node-topology">830</port>
<username xmlns="urn:opendaylight:netconf-node-topology">root</username>
<password xmlns="urn:opendaylight:netconf-node-topology">passw0rd</password>
<tcp-only xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only>
<keepalive-delay xmlns="urn:opendaylight:netconf-node-topology">0</keepalive-delay>
<yang-module-capabilities xmlns="urn:opendaylight:netconf-node-topology">
<capability>http://xml.juniper.net/xnm/1.1/xnm?module=configuration&revision=2014-11-13</capability>
</yang-module-capabilities>
</node>
XRv lists capabilities in hello, so nothing need:
PUT http://192.168.5.199:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/xrv-P1
<node xmlns="urn:TBD:params:xml:ns:yang:network-topology">
<node-id>xrv-P4</node-id>
<host xmlns="urn:opendaylight:netconf-node-topology">172.16.17.4</host>
<port xmlns="urn:opendaylight:netconf-node-topology">830</port>
<username xmlns="urn:opendaylight:netconf-node-topology">rmavrichev</username>
<password xmlns="urn:opendaylight:netconf-node-topology">passw0rd</password>
<tcp-only xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only>
<keepalive-delay xmlns="urn:opendaylight:netconf-node-topology">0</keepalive-delay>
</node>
Show config datastore:
{
"topology": [
{
"topology-id": "topology-netconf",
"node": [
{
"node-id": "xrv-P1",
"netconf-node-topology:host": "172.16.17.1",
"netconf-node-topology:
"netconf-node-topology:
"netconf-node-topology:port": 830,
"netconf-node-topology:tcp-
"netconf-node-topology:
},
{
"node-id": "PE-2",
"netconf-node-topology:pass-
"netconf-node-topology:
"netconf-node-topology:host": "172.16.16.2",
"netconf-node-topology:
"netconf-node-topology:
"netconf-node-topology:yang-
"override": false,
"capability": [
]
},
"netconf-node-topology:port": 830,
"netconf-node-topology:tcp-
}
],
"topology-types": {
"l3-unicast-igp-topology:l3-
"ospf-topology:ospf": {},
"isis-topology:isis": {}
},
"odl-bgp-topology-types:bgp-
"odl-bgp-topology-types:bgp-
"odl-bgp-topology-types:bgp-
"network-topology-pcep:
"netconf-node-topology:
"topology-tunnel-pcep:
"topology-tunnel:topology-
}
}
]
}
Operational datastore, node PE-2:
{
"node": [
{
"node-id": "PE-2",
"netconf-node-topology:
"available-capability": [
"urn:ietf:params:netconf:
"urn:ietf:params:netconf:
"urn:ietf:params:xml:ns:
"urn:ietf:params:netconf:
"urn:ietf:params:xml:ns:
"urn:ietf:params:xml:ns:
"urn:ietf:params:netconf:base:
"urn:ietf:params:xml:ns:
"urn:ietf:params:xml:ns:
"urn:ietf:params:netconf:
]
},
"netconf-node-topology:host": "172.16.16.2",
"netconf-node-topology:
"netconf-node-topology:
"netconf-node-topology:port": 830
}
]
}
Operational datastore, node xrv-P1:
GET http://192.168.5.199:8181/restconf/operational/network-topology:network-topology/topology/topology-netconf/node/xrv-P1
{
"node": [
{
"node-id": "xrv-P1",
"netconf-node-topology:available-capabilities": {
"available-capability": [
"urn:ietf:params:netconf:capability:candidate:1.0",
"(http://cisco.com/ns/yang/Cisco-IOS-XR-lib-keychain-cfg?revision=2013-07-22)Cisco-IOS-XR-lib-keychain-cfg",
"(http://cisco.com/ns/yang/Cisco-IOS-XR-rgmgr-oper?revision=2013-07-22)Cisco-IOS-XR-rgmgr-oper-sub1",
-------- cut -------
"(http://cisco.com/ns/yang/Cisco-IOS-XR-tty-server-oper?revision=2013-07-22)Cisco-IOS-XR-tty-server-oper-sub5"
]
},
"netconf-node-topology:host": "172.16.17.1",
"netconf-node-topology:unavailable-capabilities": {},
"netconf-node-topology:connection-status": "connected",
"netconf-node-topology:port": 830
}
]
}
Get config portion of PE-2:
{
"services": {
"ssh": {
"protocol-version": [
"v2"
]
},
"netconf": {
"ssh": {
"port": 830
}
}
}
}
Get config portion of xrv-P1:
GET http://192.168.5.199:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/xrv-P1/yang-ext:mount/Cisco-IOS-XR-ifmgr-cfg:interface-configurations/interface-configuration/act/Loopback0/
{
"interface-configuration": [
{
"interface-name": "Loopback0",
"active": "act",
"interface-virtual": [
null
],
"Cisco-IOS-XR-ipv4-io-cfg:ipv4-network": {
"addresses": {
"primary": {
"address": "172.16.17.1",
"netmask": "255.255.255.255"
}
}
},
"description": "GRT-loopback"
}
]
}
