[ovs-discuss] ovs-vswitchd usage
Steven Y. Ko
steveko at CS.Princeton.EDU
Sun Nov 15 21:02:42 UTC 2009
It works without any controller and also works with ovs-controller. I
guess it's a NOX issue. Do I have to do anything special with NOX? I'm
just using the same NOX that works with openflow reference
implementation 0.8.9. I tried compiling NOX again by giving
openvswitch to --with-openflow option, but didn't work because some
header files mismatch.
One more thing - I noticed that I have to bring up interfaces for the
switch manually, e.g., "ifconfig eth1 up". I wanted to verify if this
is the case, since I don't do it when I run openflow reference
On Sat, Nov 14, 2009 at 6:06 PM, Justin Pettit <jpettit at nicira.com> wrote:
> On Nov 13, 2009, at 3:15 PM, Steven Y. Ko wrote:
> I don't think you need to set this key.
>> NOX is configured as an out-of-band controller, and connectivity is
>> fine. With this configuration file, I run ovs-vswitchd with -v, then I
>> get the log copied at the end of this email. It seems that there is no
>> error. However, when I actually bring up 2 hosts and try to ping each
>> other, ARP requests never pass through. I used tcpdump to verify that
>> either eth1 or eth2 receives the ARP requests, and they do receive the
> What NOX applications are you running? I'd recommend first trying to run ovs-vswitchd without connecting to a controller. That way, you can at least determine whether ovs-vswitchd is receiving traffic. Without a controller, it should just work like a learning switch. If that looks okay, try running ovs-controller (it's available in the "utilities" directory), since it's much simpler than NOX. If that looks okay, then it's probably a NOX configuration issue.
> I'm a bit surprised that you're not seeing packet-in messages reported in the logs below. It appears that you only have four seconds of logging. I assume you waited longer than that, correct?
More information about the discuss