Hi Iwase,
Also one more thing to add in documentation that ryu would be required to be
executed with 'sudo' priviledges as it starts the BGP listener on a port 179.
There are no error messages displayed with 'Info' log level if sudo command is
not present, can only see those in debug level.
Regards,
Varun.
On Mon, Dec 4, 2017 at 11:33 AM, Varun Amrutiya
<h20170...@pilani.bits-pilani.ac.in <mailto:h20170...@pilani.bits-pilani.ac.in>>
wrote:
Hi Iwase,
The doc changes are correct. I have one more point thing to point out, I am
not sure whether it causes any abnormal behavior or not.
If 'ovs-vsctl set Bridge s1 protocols="OpenFlow13"' is executed after switch
is connected to Ryu then we can see BGP throwing and error message of
openFlow in debug logs. However if set the switch as 'OpenFlow13' during it
creation in mininet, that small error disappears. So I used 's1 =
self.addSwitch('s1', dpid="1", protocols='OpenFlow13')' in my mininet files
so that switches are by default of OpenFlow13 before they connect to ryu
controller. I am not sure about whether setting them as openFlow13 using ovs
command would cause any error. Just wanted to point out, incase anyone faces
any issue.
Regards,
Varun.
On Mon, Dec 4, 2017 at 4:51 AM, Iwase Yusuke <iwase.yusu...@gmail.com
<mailto:iwase.yusu...@gmail.com>> wrote:
Hi Varun,
Thank you for your confirmation!
I've posted my patch for adding some notes when using Mininet VMs with
rest_vtep.py.
https://www.mail-archive.com/ryu-devel@lists.sourceforge.net/msg14341.html
<https://www.mail-archive.com/ryu-devel@lists.sourceforge.net/msg14341.html>
With this patch, Ryu-Doc would be like;
http://ryu-iwase.readthedocs.io/en/rest_vtep-add_some_desc_for_troubleshooting/app/rest_vtep.html#troubleshooting
<http://ryu-iwase.readthedocs.io/en/rest_vtep-add_some_desc_for_troubleshooting/app/rest_vtep.html#troubleshooting>
Thanks,
Iwase
On 2017年12月01日 23:11, Varun Amrutiya wrote:
Hi Iwase,
The lines highlighted by you are correct. I also enabled ipv6 by
changing the sysctl and the grub file the same way.
https://github.com/mininet/mininet/blob/f65e1ab9361632f8ba83b296e27f1fecc257d4f9/util/install.sh#L615-L639
<https://github.com/mininet/mininet/blob/f65e1ab9361632f8ba83b296e27f1fecc257d4f9/util/install.sh#L615-L639>
Regards,
Varun.
On Fri, Dec 1, 2017 at 5:36 AM, Iwase Yusuke
<iwase.yusu...@gmail.com <mailto:iwase.yusu...@gmail.com>
<mailto:iwase.yusu...@gmail.com <mailto:iwase.yusu...@gmail.com>>>
wrote:
Hi Varun,
Thank you so much for using this application!
..but I'm sorry it has some buggy behavior because I
implemented it
experimental...
> The module is fine works correctly. The only thing required
for it to work was
> just to enable 'ipv6'. As soon as I enabled it started
working fine, already
> tested it with more than two vm and more than 5 hosts
connected.*Please
include
> in documentation that 'ipv6' is required to be enabled for
BGP to work
> correctly.* Also the 'EventOFPErrorMsg ' disappeared once
bgp was
enabled. Hope
> you find why it doesn't work only with 'ipv4'.
>
> I was using Mininet VM and they have ipv6 disabled by
default, so I had no
> reason to believe that 'ipv6' could be culprit here. I went
through some old
> threads on the devel group where bgp was failing and you
suggested to enable
> 'ipv6', that where I got hint it might be the issue.
Thanks for reporting this issue!
Just to confirm, you mean the following setting which Mininet
does at its
installation?
https://github.com/mininet/mininet/blob/f65e1ab9361632f8ba83b296e27f1fecc257d4f9/util/install.sh#L615-L639
<https://github.com/mininet/mininet/blob/f65e1ab9361632f8ba83b296e27f1fecc257d4f9/util/install.sh#L615-L639>
<https://github.com/mininet/mininet/blob/f65e1ab9361632f8ba83b296e27f1fecc257d4f9/util/install.sh#L615-L639
<https://github.com/mininet/mininet/blob/f65e1ab9361632f8ba83b296e27f1fecc257d4f9/util/install.sh#L615-L639>>
I will add some descriptions as you said and will investigate
why "disable IPv6"
settings cause this issue.
> Also you can include one more thing in documentation to make
switches in
> mininet via this command 's1 = self.addSwitch('s1', dpid="1",
> protocols='OpenFlow13')' , this helps in eliminating one more
OpenFlow13 error
> message from debug logs.
>
> The module was tested with Ryu:4.19 and ovs: 2.6
Yeah! I will include the OpenFlow version and the tested
version of Ryu, OVS and
Mininet on the document!
Thanks a lot!
I will post the patch later!
Thanks,
Iwase
On 2017年11月30日 16:47, Varun Amrutiya wrote:
Hi Iwase,
First of all, this is a very good module that you have
written in Ryu.
Simply perfect.
The module is fine works correctly. The only thing required
for it to
work was just to enable 'ipv6'. As soon as I enabled it
started working
fine, already tested it with more than two vm and more than
5 hosts
connected.*Please include in documentation that 'ipv6' is
required to be
enabled for BGP to work correctly.* Also the
'EventOFPErrorMsg '
disappeared once bgp was enabled. Hope you find why it
doesn't work only
with 'ipv4'.
I was using Mininet VM and they have ipv6 disabled by
default, so I had
no reason to believe that 'ipv6' could be culprit here. I
went through
some old threads on the devel group where bgp was failing
and you
suggested to enable 'ipv6', that where I got hint it might
be the issue.
Also you can include one more thing in documentation to
make switches
in mininet via this command 's1 = self.addSwitch('s1',
dpid="1",
protocols='OpenFlow13')' , this helps in eliminating one
more OpenFlow13
error message from debug logs.
The module was tested with Ryu:4.19 and ovs: 2.6
Regards,
Varun.
On Thu, Nov 30, 2017 at 12:55 PM, Iwase Yusuke
<iwase.yusu...@gmail.com <mailto:iwase.yusu...@gmail.com>
<mailto:iwase.yusu...@gmail.com
<mailto:iwase.yusu...@gmail.com>> <mailto:iwase.yusu...@gmail.com
<mailto:iwase.yusu...@gmail.com>
<mailto:iwase.yusu...@gmail.com
<mailto:iwase.yusu...@gmail.com>>>> wrote:
Hi Varun,
I'm very sorry for the delay.
Would you mind including the Ryu-devel mailing list?
I've tested rest_vtep.py on my environment, I couldn't
reproduce
your issue...
I used my Docker image which has Mininet and Ryu, and
I create the
topology
which has 3 nodes and each node has 2 Mininet hosts.
Docker Image:
https://hub.docker.com/r/iwaseyusuke/ryu-mininet/
<https://hub.docker.com/r/iwaseyusuke/ryu-mininet/>
<https://hub.docker.com/r/iwaseyusuke/ryu-mininet/
<https://hub.docker.com/r/iwaseyusuke/ryu-mininet/>>
<https://hub.docker.com/r/iwaseyusuke/ryu-mininet/
<https://hub.docker.com/r/iwaseyusuke/ryu-mininet/>
<https://hub.docker.com/r/iwaseyusuke/ryu-mininet/
<https://hub.docker.com/r/iwaseyusuke/ryu-mininet/>>>
Version of OVS, Mininet and Ryu included in the above
Docker image:
root@a96d42869486:~# ovs-vsctl --version
ovs-vsctl (Open vSwitch) 2.5.2 # this is apt
packaged version on
Ubuntu 16.04
Compiled Oct 17 2017 16:38:57
DB Schema 7.12.1
root@a96d42869486:~# mn --version
2.2.1 # this is apt packaged version on Ubuntu
16.04
root@a96d42869486:~# ryu --version
ryu 4.19
Topology:
+---------------+ +---------------+
| node1 | | node2 |
| +-----------+ | | +-----------+ |
| | s1 +----(Linux)----+ s1 | |
| +-+------+--+ | (Bridge) | +-+------+--+ |
| | | | | | | | |
| +-+--+ +-+--+ | | | +-+--+ +-+--+ |
| | h1 | | h2 | | | | | h1 | | h2 | |
| +----+ +----+ | | | +----+ +----+ |
+---------------+ | +---------------+
|
|
+---------------+
| node3 |
| +-----------+ |
| | s1 | |
| +-+------+--+ |
| | | |
| +-+--+ +-+--+ |
| | h1 | | h2 | |
| +----+ +----+ |
+---------------+
> *EventOFPErrorMsg received.*
> *version=0x4, msg_type=0x1, msg_len=0x4c,
xid=0xde4e44b*
> * `-- msg_type: OFPT_ERROR(1)*
> *OFPErrorMsg(type=0x2, code=0xf,
>
data=b'\x04\x0e\x01\x00\x0d\xe4\xe4\x4b\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x02\xff\xff\xff\xff\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01\x00\x2c\x80\x00\x05\x10\x00\x00\x00\x00\x00\x00\x00\x0a')*
> * |-- type: OFPET_BAD_ACTION(2)*
> * |-- code: OFPBAC_BAD_SET_ARGUMENT(15)*
> * `-- data: version=0x4, msg_type=0xe,
msg_len=0x100,
xid=0xde4e44b*
> * `-- msg_type: OFPT_FLOW_MOD(14)*
The above message shows the argument of SET_FIELD
action is invalid
(e.g.,
exceeds the rage), so your OVS cannot accept the flows
which
rest_vetp.py tried
to install...
Thanks,
Iwase
On 2017年11月24日 04:35, AMRUTIYA VARUN ALPESHKUMAR
wrote:
Hi,
Can ipv6 being disabled be the issue ?
regards,
Varun.
On Fri, Nov 24, 2017 at 12:57 AM, AMRUTIYA VARUN
ALPESHKUMAR
<h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>>>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>>>>> wrote:
Hi,
(rest_vtep.sh)
Finally narrowed it down to one step.
The error is of openflow, it occurs when a
client tries to
register
itself
to the switch and 'add_client' is called.
The error msg, Issue with BGP libray
probably, (i think in
vpn.py L111)
New best path selected for destination
Destination(table:
Table(scope_id:
65000:10, rf: RouteFamily(afi=25,safi=70)),
nlri:
EvpnMacIPAdvertisementNLRI(esi=EvpnArbitraryEsi(type=0,value='\x00\x00\x00\x00\x00\x00\x00\x00\x00'),ethernet_tag_id=0,ip_addr='10.0.0.21',ip_addr_len=32,length=37,mac_addr='aa:bb:cc:00:00:21',mac_addr_len=48,route_dist='65000:10',type=2),
paths: 1, withdraws: 0, new paths: 0)
*EVENT ofp_event->ofctl_service
EventOFPErrorMsg*
*EventOFPErrorMsg received.*
*version=0x4, msg_type=0x1, msg_len=0x4c,
xid=0xde4e44b*
* `-- msg_type: OFPT_ERROR(1)*
*OFPErrorMsg(type=0x2, code=0xf,
data=b'\x04\x0e\x01\x00\x0d\xe4\xe4\x4b\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x02\xff\xff\xff\xff\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01\x00\x2c\x80\x00\x05\x10\x00\x00\x00\x00\x00\x00\x00\x0a')*
* |-- type: OFPET_BAD_ACTION(2)*
* |-- code: OFPBAC_BAD_SET_ARGUMENT(15)*
* `-- data: version=0x4, msg_type=0xe,
msg_len=0x100,
xid=0xde4e44b*
* `-- msg_type: OFPT_FLOW_MOD(14)*
*unknown error xid 233104459*
Sent msg to ('192.168.56.102', '179') >>
BGPKeepAlive(len=19,type=4)
Received msg from ('192.168.56.102', '179')
<<
BGPKeepAlive(len=19,type=4)
Sent msg to ('192.168.56.102', '179') >>
BGPKeepAlive(len=19,type=4)
Received msg from ('192.168.56.102', '179')
<<
BGPKeepAlive(len=19,type=4)
Hope you'll fix the error.
Regards,
Varun
On Thu, Nov 23, 2017 at 7:54 PM, AMRUTIYA
VARUN ALPESHKUMAR
<h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>>>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>>>>> wrote:
Hi,
Tested the rest_vtep with ovs 2.6.0 and
ryu versions
{4.5, 4.6,
4.7,
4.8, 4.9} and {4.17, 4.19}. Ping is still
failing. Pls
mention the
environment properties on which this file
was tested.
Can't
find anyone
online who might have used the same
script.
Also, Once it start in switches it adds
all the flows
except arp
response flow. Why is that ? according to
ur thread on
ryu-devel it
should. This seems the main reason for
arp failing.
Regards,
Varun.
On Thu, Nov 23, 2017 at 2:52 PM, AMRUTIYA
VARUN
ALPESHKUMAR
<h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>>>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>
<mailto:h20170...@pilani.bits-pilani.ac.in
<mailto:h20170...@pilani.bits-pilani.ac.in>>>>> wrote:
Hi,
I was using the rest_vtep.py for
making the
topology as
presented in
the example given in ryu website.
But my ping keeps failing, After
doing a lot of
troubleshooting and
verifying all properties are same as
given in
example, in
verbose
mode I found the following error
which might give you
insight. I am
trying to implement the same example
with three
VM instead
of 2.
What is the ovs version it requires
to work ? Mine
is 2.0.2
can this
be problem. Using mininet VM.
ryu-version: 4.18
I would be very gratefull if you can
tell me the
required
versions.
Attached the logs if they can give
insight.
Sry for not using ryu-devel,
souceforge is blocked
on my
network.
(On a tight deadline, if you can
help)
Regards,
Varun.
M.E Grad
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's
most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
<mailto:Ryu-devel@lists.sourceforge.net>
<mailto:Ryu-devel@lists.sourceforge.net
<mailto:Ryu-devel@lists.sourceforge.net>>
https://lists.sourceforge.net/lists/listinfo/ryu-devel
<https://lists.sourceforge.net/lists/listinfo/ryu-devel>
<https://lists.sourceforge.net/lists/listinfo/ryu-devel
<https://lists.sourceforge.net/lists/listinfo/ryu-devel>>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
<mailto:Ryu-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/ryu-devel
<https://lists.sourceforge.net/lists/listinfo/ryu-devel>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel
