Rui Cardoso
2014-10-13 15:23:03 UTC
Hi,
I was using OVS 2.0.1 that was pre-installed with a Mininet Virtual Machine
(MN version 2.1.0p2). I wanted to add some MPLS tags but I saw that It
didn't work with the version of OVS I was working with so I'm trying to
update it.
The problem is that I've been trying for a big while now and using
different methods and can't make it work properly.
I've tried this methods:
https://github.com/mininet/mininet/wiki/Installing-new-version-of-Open-vSwitch
. Both of them and none worked, using the .tar or even with the master
branch from github. Although if I do a ovs-vsctl show I can see that I have
the newest version, v.2.3.9, if I try to do a ping command it won't work.
The host sends the ARP request to the switch but then the switch doesn't do
anything, it doesn't communicate with the controller to install the flow.
I already though that it could also be a problem of the controller, in
communication or something, but it shouldn't be. Using wireshark and
console controller I can see that the controller is connected to the switch
and they switch messages between each other (OFPT_HELLO in the start, then
the stats requests and more stuff and they keep send echo requests to see
if it's still alive). If searched online and found a few cases like this
but no solution, so i would like to know if anyone could help me.
This is what "ovs-vsctl show" shows:
Bridge "s1"
Controller "tcp:192.168.203.1:6653"
is_connected: true
Controller "ptcp:6634"
fail_mode: secure
Port "s1-eth1"
Interface "s1-eth1"
Port "s1"
Interface "s1"
type: internal
Port "s1-eth2"
Interface "s1-eth2"
ovs_version: "2.3.90"
I'm using a host1--Switch1--host2 topology, which works using OVS 2.0.1 and
my floodlight 1.3 controller.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/discuss/attachments/20141013/24a1fc8c/attachment.html>
I was using OVS 2.0.1 that was pre-installed with a Mininet Virtual Machine
(MN version 2.1.0p2). I wanted to add some MPLS tags but I saw that It
didn't work with the version of OVS I was working with so I'm trying to
update it.
The problem is that I've been trying for a big while now and using
different methods and can't make it work properly.
I've tried this methods:
https://github.com/mininet/mininet/wiki/Installing-new-version-of-Open-vSwitch
. Both of them and none worked, using the .tar or even with the master
branch from github. Although if I do a ovs-vsctl show I can see that I have
the newest version, v.2.3.9, if I try to do a ping command it won't work.
The host sends the ARP request to the switch but then the switch doesn't do
anything, it doesn't communicate with the controller to install the flow.
I already though that it could also be a problem of the controller, in
communication or something, but it shouldn't be. Using wireshark and
console controller I can see that the controller is connected to the switch
and they switch messages between each other (OFPT_HELLO in the start, then
the stats requests and more stuff and they keep send echo requests to see
if it's still alive). If searched online and found a few cases like this
but no solution, so i would like to know if anyone could help me.
This is what "ovs-vsctl show" shows:
Bridge "s1"
Controller "tcp:192.168.203.1:6653"
is_connected: true
Controller "ptcp:6634"
fail_mode: secure
Port "s1-eth1"
Interface "s1-eth1"
Port "s1"
Interface "s1"
type: internal
Port "s1-eth2"
Interface "s1-eth2"
ovs_version: "2.3.90"
I'm using a host1--Switch1--host2 topology, which works using OVS 2.0.1 and
my floodlight 1.3 controller.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/discuss/attachments/20141013/24a1fc8c/attachment.html>