[ovs-discuss] repeated errors connecting to nox

Ben Pfaff blp at nicira.com
Thu May 24 19:02:02 UTC 2012


It's saying that the in_port you sent in your packet_out is invalid.
Probably, you're using OFPP_CONTROLLER, which is not a valid in_port
in OpenFlow 1.0.  You can, however, upgrade to the very latest OVS
(either tip of master or tip of branch-1.4) to make OVS tolerate these
invalid port numbers.

On Thu, May 24, 2012 at 11:59:56AM -0700, Ben Pfaff wrote:
> [adding the list back]
> 
> On Thu, May 24, 2012 at 02:46:02PM -0400, Ryan White wrote:
> > Looking in the ovs log, it shows that it is sending these to the controller:
> > type OFPET_BAD_REQUEST, code NXBRC_BAD_IN_PORT.
> > The only thing i could find regarding these, I found from the ovs-dev list
> > 
> > *Some invalid ports (those above the maximum port number supported by
> > the*>* datapath, including OpenFlow reserved ports that are not
> > translated by OVS*>* into some other number) will be rejected by the
> > datapath.  It's better to*>* catch these early and send back an
> > appropriate OpenFlow error code, rather*>* than to just get EINVAL
> > from the kernel and have to guess at the problem.*
> > 
> > >* +    if (flow->in_port >= ofproto->max_ports && flow->in_port < OFPP_MAX) {*>* +        return ofp_mkerr_nicira(OFPET_BAD_REQUEST, NXBRC_BAD_IN_PORT);*>* +    }
> > *
> > 
> > 
> > But I'm having trouble figuring out what this means. There is only one port
> > on my machine. Or do they mean port as in port 6633? Or is it the number
> > associated to the port of the bridge, ie one for eth0 on br0, another for
> > tap1 on br0 etc?
> > 
> > Anybody have any ideas?
> > 
> > On Tue, May 22, 2012 at 2:44 PM, Ben Pfaff <blp at nicira.com> wrote:
> > 
> > > On Tue, May 22, 2012 at 02:38:54PM -0400, Ryan White wrote:
> > > > then it registers a node on the nox controller machine, but keeps
> > > spitting
> > > > out tons of copies of the same error in nox saying openflow error type
> > > > 45250 code 0.
> > >
> > > This is an Open vSwitch error extension message.  You can decode it by
> > > looking further into the message (see nicira-ext.h in the Open vSwitch
> > > distribution) or you can look in the OVS log, which should say what
> > > particular error OVS is reporting (at least for 1.4 and later).
> > >



More information about the discuss mailing list