[OOR-Users] [OOR-users] How to do dynamic eid registration using LISP netconf interface
Nagesh L
laginagesh at gmail.com
Tue Nov 8 21:38:28 CET 2016
Hi Albert,
Thank you for the reply.
I have tried with the sample xml file using netopeer-cli but I am seeing
the below errors.
NETCONF error: access-denied (application) - creating "etr-cfg" data node
is not permitted.
Please correct me If i am doing any wrong steps.
Attaching config file(lisp_netconf.txt) which i have used.
netconf> get-config
Select target datastore (running|startup|candidate|url:<dsturl>): running
Result:
<netopeer xmlns="urn:cesnet:tmc:netopeer:1.0">
<modules>
<module>
<name>lispsimple</name>
<enabled>true</enabled>
</module>
</modules>
</netopeer>
netconf> edit-config running
NETCONF error: access-denied (application) - creating "etr-cfg" data node
is not permitted.
netconf> copy-config running
NETCONF error: access-denied (application) - Access to the requested
protocol operation or data model is denied because the authorization failed.
netconf> edit-config running
NETCONF error: access-denied (application) - creating "etr-cfg" data node
is not permitted.
netconf>
Thanks
Nagesh
On Mon, Nov 7, 2016 at 7:46 PM, Albert López <alopez at ac.upc.edu> wrote:
> Hi Nagesh,
>
> I attached an xml example file that shows how to configure Map Server and
> EIDs of an xTR using netconf. You can send this configuration to oor using
> ODL but it is easy with netopeer-cli. I have never used directly ssh
> connection so I can not help you at this point.
> If you check lispsimple.yang file you could check all the parameters that
> can be configured at this moments. At this moment we only support edit
> configuration with replace so if you need to modify any parameter you will
> have to resend the full configuration. The map server configuration is
> shared for all the eids of the database.
> I hope this information helps you. If not, let me know.
>
> Best regards
>
> Albert
>
>
>
> On 04/11/16 14:03, Nagesh L wrote:
>
>> Hi,
>>
>> I am trying to do "Dynamic EID registration from XTR to MS via Netconf
>> interface @ XTR".
>> I followed all the steps mentioned in "lispmob/netconf/README" but i
>> don't see sample xml file to feed EID information to XTR via netconf.
>>
>> Can someone provide the steps, sample xml file to feed EID information to
>> XTR via netconf.
>>
>> netopeer is running:
>>
>> ps aux | grep netop
>> root 524 0.0 0.1 71240 2108 ? S 11:10 0:00 sudo
>> netopeer-server
>> root 525 0.0 0.5 211980 10884 ? Sl 11:10 0:02
>> netopeer-server
>> root 526 0.0 0.1 61384 3036 ? S 11:10 0:00
>> /usr/sbin/sshd -D -f //usr/local/etc/netopeer/sshd_config.running
>> root 4386 0.0 0.0 15944 900 pts/27 S+ 18:18 0:00 grep
>> --color=auto netop
>>
>> netconf port is in listen mode:
>>
>> netstat -a | grep 830
>> tcp 0 0 *:830 *:* LISTEN
>> tcp6 0 0 [::]:830 [::]:* LISTEN
>>
>> LISPD is running
>>
>> ps aux | grep lisp
>> root 4390 0.0 0.0 15940 900 pts/27 S+ 18:20 0:00 grep
>> --color=auto lisp
>> root 4780 5.8 0.1 125244 2708 pts/7 Sl Oct21 1183:01
>> /usr/local/sbin/lispd -f /etc/lispd.conf
>>
>> I am able to connect to netconf port using ssh, what is the input do i
>> need to provide?
>>
>> ssh test at x.x.x.x -p 830 -s netconf
>> test at x.x.x.x's password:
>> <?xml version="1.0" encoding="UTF-8"?>
>> <hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
>> <capabilities>
>> <capability>urn:ietf:params:netconf:base:1.0</capability>
>> <capability>urn:ietf:params:netconf:base:1.1</capability>
>> <capability>urn:ietf:params:netconf:capability:writable-runn
>> ing:1.0</capability>
>> <capability>urn:ietf:params:netconf:capability:candidate:1.0</capability>
>> <capability>urn:ietf:params:netconf:capability:startup:1.0</capability>
>> <capability>urn:ietf:params:netconf:capability:rollback-on-
>> error:1.0</capability>
>> <capability>urn:ietf:params:netconf:capability:interleave:1.
>> 0</capability>
>> <capability>urn:ietf:params:netconf:capability:notification:
>> 1.0</capability>
>> <capability>urn:ietf:params:netconf:capability:validate:1.0</capability>
>> <capability>urn:ietf:params:netconf:capability:validate:1.1</capability>
>> <capability>urn:ietf:params:netconf:capability:with-defaults
>> :1.0?basic-mode=explicit&also-supported=report-all,
>> report-all-tagged,trim,explicit</capability>
>> <capability>urn:ietf:params:netconf:capability:url:1.0?schem
>> e=scp,file</capability>
>> <capability>urn:ietf:params:xml:ns:yang:lispsimple?module=li
>> spsimple&revision=2015-07-02</capability>
>> <capability>urn:ietf:params:xml:ns:yang:iana-afn-safi?module
>> =iana-afn-safi&revision=2013-07-04</capability>
>> <capability>urn:cesnet:tmc:netopeer:1.0?module=netopeer-cfgn
>> etopeer&revision=2013-02-14</capability>
>> <capability>urn:ietf:params:xml:ns:yang:ietf-netconf-server?
>> module=ietf-netconf-server&revision=2014-01-24&
>> features=ssh,inbound-ssh,outbound-ssh</capability>
>> <capability>urn:ietf:params:xml:ns:yang:ietf-x509-cert-to-na
>> me?module=ietf-x509-cert-to-name&revision=2013-03-26</capability>
>> <capability>urn:ietf:params:xml:ns:yang:ietf-netconf-acm?mod
>> ule=ietf-netconf-acm&revision=2012-02-22</capability>
>> <capability>urn:ietf:params:xml:ns:yang:ietf-netconf-with-de
>> faults?module=ietf-netconf-with-defaults&revision=2010-
>> 06-09</capability>
>> <capability>urn:ietf:params:xml:ns:netconf:notification:1.0?
>> module=notifications&revision=2008-07-14</capability>
>> <capability>urn:ietf:params:xml:ns:netmod:notification?modul
>> e=nc-notifications&revision=2008-07-14</capability>
>> <capability>urn:ietf:params:xml:ns:yang:ietf-netconf-notific
>> ations?module=ietf-netconf-notifications&revision=
>> 2011-08-07</capability>
>> <capability>urn:ietf:params:xml:ns:yang:ietf-netconf-monitor
>> ing?module=ietf-netconf-monitoring&revision=2010-10-04</capability>
>> <capability>urn:ietf:params:xml:ns:netconf:base:1.0?module=
>> ietf-netconf&revision=2011-03-08&features=
>> writable-running,candidate,rollback-on-error,validate,
>> startup,url</capability>
>> <capability>urn:ietf:params:xml:ns:yang:ietf-yang-types?modu
>> le=ietf-yang-types&revision=2013-07-15</capability>
>> <capability>urn:ietf:params:xml:ns:yang:ietf-inet-types?modu
>> le=ietf-inet-types&revision=2010-09-24</capability>
>> </capabilities>
>> <session-id>46</session-id>
>> </hello>
>> ]]>]]>
>>
>>
>> Thanks
>> Nagesh
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openoverlayrouter.org/pipermail/users/attachments/20161109/8b1ee6a8/attachment.html>
-------------- next part --------------
<etr-cfg xmlns="urn:ietf:params:xml:ns:yang:lispsimple">
<map-servers>
<map-server>
<address>1.1.1.100</address>
<auth-key>test</auth-key>
<auth-key-type>hmac-sha-1-96</auth-key-type>
</map-server>
<proxy-reply>true</proxy-reply>
</map-servers>
<local-eids>
<local-eid>
<id>eid1</id>
<eid-address>
<afi>ipv4</afi>
<instance-id>0</instance-id>
<ipv4>5.5.5.0</ipv4>
<mask>24</mask>
</eid-address>
<rlocs>
<rloc>
<name>rloc1</name>
<interface>eth2</interface>
<priority>1</priority>
<weight>50</weight>
<multicast-priority>255</multicast-priority>
<multicast-weight>0</multicast-weight>
</rloc>
</rlocs>
<record-ttl>10</record-ttl>
</local-eid>
</local-eids>
</etr-cfg>
More information about the Users
mailing list