[ovs-discuss] Simple MPLS experiment with OpenvSwitch

[Ben Pfaff]

Your output makes it clear that you are not using Open vSwitch but actually
the OpenFlow reference implementation.
On Mar 9, 2013 4:15 PM, "Dushyant Arora" <dushyantarora13 at gmail.com> wrote:

> Here are the contents of /tmp/s1-ofd.log
> RTNETLINK answers: No such file or directory
> RTNETLINK answers: No such file or directory
> ofdatapath: udatapath/datapath.c:2245: fwd_control_input: Assertion
> `oh->version == 0x01' failed.
> Mar 09 12:18:23|00001|fault|EMER|Caught signal 6.
>   0x08056ded
>   0x61706174
> Mar 09 12:18:23|00002|fault|EMER|Caught signal 11.
>   0x08056ded
>   0x08056ded
>   0x61706174
>
> and /tmp/s1-ofp.log
>
> Mar 09 12:18:22|00001|secchan|INFO|OpenFlow reference implementation
> version 1.0.0
> Mar 09 12:18:22|00002|secchan|INFO|OpenFlow protocol version 0x01
> Mar 09 12:18:22|00003|secchan|WARN|new management connection will
> receive asynchronous messages
> Mar 09 12:18:22|00004|rconn|INFO|unix:/tmp/s1: connecting...
> Mar 09 12:18:22|00005|vconn_unix|ERR|/tmp/vconn-unix.13280.0:
> connection to /tmp/s1 failed: Connection refused
> Mar 09 12:18:22|00006|rconn|WARN|unix:/tmp/s1: connection failed
> (Connection refused)
> Mar 09 12:18:22|00007|rconn|INFO|unix:/tmp/s1: waiting 1 seconds
> before reconnect
> Mar 09 12:18:22|00008|rconn|INFO|tcp:127.0.0.1:6633: connecting...
> Mar 09 12:18:22|00009|rconn|INFO|tcp:127.0.0.1:6633: connection failed
> (Connection refused)
> Mar 09 12:18:22|00010|rconn|WARN|tcp:127.0.0.1:6633: connection
> dropped (Connection refused)
> Mar 09 12:18:23|00011|rconn|INFO|unix:/tmp/s1: connecting...
> Mar 09 12:18:23|00012|rconn|INFO|tcp:127.0.0.1:6633: connecting...
> Mar 09 12:18:23|00013|rconn|INFO|unix:/tmp/s1: connected
> Mar 09 12:18:23|00014|rconn|INFO|tcp:127.0.0.1:6633: connected
> Mar 09 12:18:23|00015|rconn|INFO|tcp:127.0.0.1:6633: connection closed by
> peer
> Mar 09 12:18:23|00016|rconn|INFO|tcp:127.0.0.1:6633: waiting 2 seconds
> before reconnect
> Mar 09 12:18:23|00017|rconn|WARN|unix:/tmp/s1: connection dropped
> (Connection reset by peer)
>
> Earlier I used to do:
> $ sudo ovs-vsctl set bridge s1 protocols=OpenFlow10,OpenFlow12,OpenFlow13
> what should I do in the userspace switch?
>
> On Sat, Mar 9, 2013 at 6:58 PM, Dushyant Arora
> <dushyantarora13 at gmail.com> wrote:
> > Ok, I figured out I need to use dpctl utility but I don't know what to
> > provide as the switch path $ dpctl show unix:???
> > The only example I could find on the Internet uses /var/run/... as the
> > path but I don't see s1.sock there.
> >
> > On Sat, Mar 9, 2013 at 6:32 PM, Dushyant Arora
> > <dushyantarora13 at gmail.com> wrote:
> >> Thanks for replying Ben. I changed the Mininet python file to use a
> UserSwitch :
> >>
> >> def emptyNet():
> >>
> >>     "Create an empty network and add nodes to it."
> >>
> >>     net = Mininet( controller=lambda name: NOX ( name, 'NOXSwitch' ),
> >> switch=UserSwitch )
> >>
> >>
> >> but now when I fire up Mininet I don't the switch when using utilities
> >> ovs-vsctl and ovs-dpctl
> >>
> >> $ sudo ovs-vsctl show
> >> 01407762-26a9-43f5-9094-7b9bcf45eacc
> >> $ sudo ovs-dpctl show
> >> system at ovs-system:
> >>         lookups: hit:2019 missed:302 lost:0
> >>         flows: 0
> >>         port 0: ovs-system (internal)
> >>
> >> I have been using the kernel module so far, so please pardon my
> >> ignorance. What am I doing wrong?
> >>
> >> On Fri, Mar 8, 2013 at 7:11 PM, Ben Pfaff <blp at nicira.com> wrote:
> >>> On Fri, Mar 08, 2013 at 06:54:31PM -0500, Dushyant Arora wrote:
> >>>> I am trying to run a very basic MPLS test. I have the following
> >>>> versions of OpenvSwitch and Mininet:
> >>>>
> >>>> $ ovs-vsctl --version
> >>>> ovs-vsctl (Open vSwitch) 1.10.90
> >>>> Compiled Mar  5 2013 16:25:06
> >>>> $ mn --version
> >>>> 2.0.0
> >>>
> >>> MPLS only works with the userspace switch at the moment.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20130309/384f603c/attachment.html>