[OOR-Users] Question regarding Netconf-netopeer

[Albert López]

Hello Kshitija,

Once you have set libnetconf and netopeer in all the xTRs (we don't have 
implemented netconf methods for MS), you use netopeer-configurator to 
set the permissions of the ssh users that are allowed to configure the 
module using netconf. Then you use netopeer-cli to configure remotely 
OOR using netconf (connect to the netopeer-server and edit 
configuration). I attach a file showing the XML structure that could be 
used to configure OOR. As far as I can remember, netopeer-cli didn't 
allow to configure ETR and ITR parameters at the same time. Other option 
is to use Open Daylight instead of netopeer-cli but my knowledge of Open 
Daylight is very poor and I can not help you at this point.

Best regards

Albert


On 27/02/17 21:01, Kshitija Mane wrote:
> Hello,
>
> I have implemented a simple layout of 6 Ubuntu Vms for testing LISP.
> MN1 <-> XTR1 <->MS <-> XTR2 <-> MN2.
> Now I am trying to work with NETCONF with OOR.
>
> After configuring libnetconf and netopeer, what particular steps are 
> to be followed?
>
> Should libnetconf and netopeer be installed on all the VMs (MS, all 
> XTRs and MNs )?
>
> Is there an issue/error if libnetconf2 and netpeerguid is used instead 
> of libnetcong and netopeer (as specifiled in README).
>
>
> -- 
>
> Thank You,
> Kshitija Mane
> MS in Electrical Engineering (Networking)
> San Jose State University
>
>
>
> _______________________________________________
> Users mailing list
> Users at openoverlayrouter.org
> http://mail.openoverlayrouter.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openoverlayrouter.org/pipermail/users/attachments/20170228/18596f71/attachment.html>
-------------- next part --------------
<edit-config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<target><running /></target>
<default-operation>replace</default-operation>
<config>

<etr-cfg xmlns="urn:ietf:params:xml:ns:yang:lispsimple">
  <map-servers>
    <map-server>
      <address>84.88.81.2</address>
      <auth-key>password</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>2.2.2.0</ipv4>
	<mask>24</mask>
      </eid-address>
      <rlocs>
        <rloc>
          <name>rloc1</name>
          <interface>eth0</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-eid>
      <id>eid2</id>
      <eid-address>
	<afi>ipv4</afi>
	<instance-id>0</instance-id>
	<ipv4>3.3.3.0</ipv4>
	<mask>24</mask>
      </eid-address>
      <rlocs>
        <rloc>
          <name>rloc2</name>
          <locator-address>
	    <afi>ipv4</afi>
            <ipv4>84.88.81.86</ipv4>
	  </locator-address>
          <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>

<itr-cfg xmlns="urn:ietf:params:xml:ns:yang:lispsimple">
  <map-resolvers>
    <map-resolver>
      <id>MR-ODL</id>
      <map-resolver-address>192.168.16.11</map-resolver-address>
    </map-resolver>
  </map-resolvers>
</itr-cfg>

</config>
</edit-config>