[NETCONF-624] Netconf Testtool to Not getting connected to Odl. Created: 05/Jun/19  Updated: 04/Jul/19  Resolved: 04/Jul/19

Status: Resolved
Project: netconf
Component/s: netconf
Affects Version/s: None
Fix Version/s: Sodium

Type: Bug Priority: High
Reporter: Ajay Deep Singh Assignee: Eliezio Oliveira
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to NETCONF-630 Add acceptance/E2E tests to testtool Resolved
Priority: High

 Description   

Hi All,

Running into issue of connecting Netconf Testtool to Odl.

Cmd for Starting, Linking testtool to Odl:

ubuntu@ubuntu-VirtualBox:~/Downloads/netconf/netconf/tools/netconf-testtool/target$ java -jar netconf-testtool-1.7.0-SNAPSHOT-executable.jar  --device-count 10 --distributiolder ~/Downloads/distribution --debug true --schemas-dir ~/test-schemas/

 

After starting Netconf Testtool its Not getting attached to Odl.

I have cloned distribution repository and this is path for it where I have karaf script  : /home/ubuntu/Downloads/distribution/karaf/target/assembly/bin

The same path I have tried providing as an input to Netconf Testtool and I don’t see any activity in karaf log that of attaching of Netconf testtool, even I have tried several option of providing till ~/Downloads/distribution and more but it didn’t work please can you point what am doing wrong here.?

 

12:26:22.339 [main] DEBUG o.o.netconf.test.tool.Main - Trying to start netconf test-tool with parameters TesttoolParameters

{editContent='null', async='false', threadAmount='1', throttle='5000', auth='null', controllerDestination='null', schemasDir='/home/ubuntu/test-schemas', deviceCount='10', devicesPerPort='1', startingPort='17830', generateConfigsTimeout='1800000', generateConfigsAddress='127.0.0.1', *distroFolder='/home/ubuntu/Downloads/distribution',* generateConfigBatchSize='1', ssh='true', exi='true', debug='true', notificationFile='null', mdSal='false', initialConfigXMLFile='null', timeOut='20', ip='0.0.0.0', threadPoolSize='8', rpcConfig='null'}

 

 

ubuntu@ubuntu-VirtualBox:~/Downloads/distribution/karaf/target/assembly/bin$ ll

total 3952

drwxrwxr-x  3 ubuntu ubuntu    4096 May 29 11:03 ./

drwxrwxr-x 13 ubuntu ubuntu    4096 May 30 10:00 ../

-rwxr-xr-x  1 ubuntu ubuntu 3865422 May 29 10:40 aaa-cli-jar.jar*

-rwxr-xr-x  1 ubuntu ubuntu    4087 May 29 10:45 client*

rw-rw-r-  1 ubuntu ubuntu    4583 May 29 10:45 client.bat

-rwxr-xr-x  1 ubuntu ubuntu    8328 May 29 10:45 configure-cluster-ipdetect.sh*

-rwxr-xr-x  1 ubuntu ubuntu    7562 May 29 10:45 configure_cluster.sh*

drwxr-xr-x  2 ubuntu ubuntu    4096 May 29 10:45 contrib/

-rwxr-xr-x  1 ubuntu ubuntu     722 May 29 10:45 custom_shard_config.txt*

rw-rw-r-  1 ubuntu ubuntu   16095 May 29 11:03 idmtool

-rwxr-xr-x  1 ubuntu ubuntu   10214 Mar 22 15:41 inc*

-rwxr-xr-x  1 ubuntu ubuntu    4453 Mar 22 15:41 instance*

rw-rw-r-  1 ubuntu ubuntu    5609 Mar 22 15:41 instance.bat

-rwxr-xr-x  1 ubuntu ubuntu   12917 Mar 22 15:41 karaf*

rw-rw-r-  1 ubuntu ubuntu   18543 Mar 22 15:41 karaf.bat

-rwxr-xr-x  1 ubuntu ubuntu    2284 Mar 22 15:41 setenv*

rw-rw-r-  1 ubuntu ubuntu    2330 Mar 22 15:41 setenv.bat

-rwxr-xr-x  1 ubuntu ubuntu    2924 May 29 10:45 set_persistence.sh*

-rwxr-xr-x  1 ubuntu ubuntu    4067 May 29 10:45 shell*

rw-rw-r-  1 ubuntu ubuntu    4947 May 29 10:45 shell.bat

-rwxr-xr-x  1 ubuntu ubuntu    2767 May 29 10:45 start*

rw-rw-r-  1 ubuntu ubuntu    2495 May 29 10:45 start.bat

-rwxr-xr-x  1 ubuntu ubuntu    2616 May 29 10:45 status*

rw-rw-r-  1 ubuntu ubuntu    2448 May 29 10:45 status.bat

-rwxr-xr-x  1 ubuntu ubuntu    2618 May 29 10:45 stop*

rw-rw-r-  1 ubuntu ubuntu    2444 May 29 10:45 stop.bat

ubuntu@ubuntu-VirtualBox:~/Downloads/distribution/karaf/target/assembly/bin$

 

Regards,

Ajay



 Comments   
Comment by Ajay Deep Singh [ 07/Jun/19 ]

Please some one in watch list can comment on issue.

Comment by Luis Gomez [ 10/Jun/19 ]

ajay.dp001, the above command just starts the netconf device simulation but you still have to setup the netconf connection in controller.

Comment by Ajay Deep Singh [ 10/Jun/19 ]

Hi Luis,

I have started netconf testtool and followed wiki link  https://wiki.opendaylight.org/view/OpenDaylight_Controller:Netconf:Testtool

which says :

Start the device with following command:

java -jar netconf-testtool-1.7.0-SNAPSHOT-executable.jar --device-count 4 --distribution-folder ../../../../../distribution/karaf/target/assembly/ --debug=true

 

> Here the attribute : --distribution-folder ../../../../../distribution/karaf/target/assembly/ --debug=true    is to connect to Odl.

but it never gets connected to ODL, I have restconf, netconf-connector feature installed.

 

Please can you highlight what config change i need to make in ODL for getting it connected to netconf testtool. 

 

Regards,

Ajay

Comment by Luis Gomez [ 11/Jun/19 ]

Yeah, I think the netconf test tool documentation is old, try as a minimum what is described in here:

https://docs.opendaylight.org/projects/netconf/en/stable-neon/user-guide.html#netconf-connector-configuration-with-md-sal

Comment by Ajay Deep Singh [ 11/Jun/19 ]

Hi Luis,

Thanks for your comments.

I have already tried steps mentioned in refereed link an it didn't worked for me. Not sure what am missing i have followed exactly the same steps but not even once the Netconf Testtool got connected to Odl.

Regards,

Ajay

Comment by Luis Gomez [ 12/Jun/19 ]

Did you try the topology REST mount from the example? the CSIT (system test) uses something like this you can try:

PUT http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/new-netconf-device

<node xmlns="urn:TBD:params:xml:ns:yang:network-topology">
<node-id>new-netconf-device</node-id>
<host xmlns="urn:opendaylight:netconf-node-topology">127.0.0.1</host>
<port xmlns="urn:opendaylight:netconf-node-topology">17830</port>
<username xmlns="urn:opendaylight:netconf-node-topology">admin</username>
<password xmlns="urn:opendaylight:netconf-node-topology">admin</password>
<tcp-only xmlns="urn:opendaylight:netconf-node-topology">false</tcp-only>
<keepalive-delay xmlns="urn:opendaylight:netconf-node-topology">0</keepalive-delay>
</node>

Also if the above does not work can you post the logs from controller + netconf test tool?

Comment by Eliezio Oliveira [ 03/Jul/19 ]

After comparing the behavior of different testtool versions, we've found the root cause of this issue: since v1.6.0 the RPC GetSchema request is being answered with an empty <data/>, without no schemas whatsoever. We just submitted the fix in https://git.opendaylight.org/gerrit/#/q/Ia43cdcf10b54d9528921675fed321665771bd667.

Generated at Wed Feb 07 20:15:29 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.