netopeer | NETCONF Protocol Toolset
kandi X-RAY | netopeer Summary
kandi X-RAY | netopeer Summary
CLI interface allowing user to connect to a NETCONF-enabled device and to obtain and manipulate its configuration data. The main Netopeer server following the integrated architecture. netopeer-server is supposed to run as a system service controlling a device. By default, we provide example modules to control several areas of a GNU/Linux desktop (network interfaces, packet filter and overall system information). The netopeer-server allows you to simply switch the modules to use your own control modules.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of netopeer
netopeer Key Features
netopeer Examples and Code Snippets
Community Discussions
Trending Discussions on netopeer
QUESTION
I want use the python library ncclient 0.6.6 with Python 2.7.15 to connect to a NETCONF server (netopeer2) and read out the running config.
I tried to follow the example from the manual, running this code in the console:
...ANSWER
Answered 2019-Jun-24 at 14:09m = manager.connect(host="172.17.0.2", port=830, username="netconf", password="netconf", hostkey_verify=False)
QUESTION
I am using ODL oxygen release to connect a netopeer-server (NETCONF host) using the below curl command. I see the following error being returned. May I know what exactly is wrong? netopeer server supports netconf-monitoring.
{"errors":{"error":[{"error-type":"protocol","error-tag":"data-missing","error-message":"Mount point does not exist."}]}}
curl -H "Content-Type: application/xml" -u admin:admin -X POST -d "
prefix:sal netconf-connector
netopeer
192.168.56.101
830
netopeer-server
pass
true
prefix:netty-event-executor
global-event-executor
prefix:binding-broker-osgi-registry
binding-osgi-broker
prefix:dom-broker-osgi-registry
dom-broker
prefix:netconf-client-dispatcher
global-netconf-dispatcher
prefix:threadpool
global-netconf-processing-executor
prefix:scheduled-threadpool
global-netconf-ssh-scheduled-executor
" http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/controller-config/yang-ext:mount/config:modules
I did try the suggested changes. COuld you please tell me what is wrong with the input? I do not see anything obvious!
...ANSWER
Answered 2018-May-09 at 03:13This seems like old way of mounting devices through config sub-system, can you try with this more recent API: http://docs.opendaylight.org/en/stable-oxygen/user-guide/netconf-user-guide.html#netconf-connector-configuration-with-md-sal
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install netopeer
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page