Are you using a switch that has the NXT_SET_PACKET_IN_FORMAT and 
NXT_FLOW_MOD_TABLE_ID Nicira extensions?

I'm not sure which version of Open vSwitch is the first to support these... 
maybe 1.8?

Glancing at the code, I actually don't immediately see where the new packet-in 
format is actually used.  You could try commenting out the lines which try to 
turn it on (around 81-83 of l2_nx.py in my local copy).

(As a sidenote, you're supposed to pass --convert-packet-in to openflow.nicira. 
 The docs show this, but it's not clear enough -- I'll fix it in carp.  But if 
you're going to try to disable this feature anyway, it shouldn't matter.)

-- Murphy

On May 28, 2013, at 12:23 PM, Mayumi Park Campos wrote:

> Hi all, 
> 
> I try to run pox with this line: 
> 
> ./pox.py log.level --DEBUG openflow.nicira forwarding.l2_nx
> 
> And get this reply on the screen: 
> POX 0.1.0 (betta) / Copyright 2011-2013 James McCauley, et al.
> INFO:forwarding.l2_nx:Simple NX switch running.
> DEBUG:core:POX 0.1.0 (betta) going up...
> DEBUG:core:Running on CPython (2.7.3/Aug 1 2012 05:16:07)
> DEBUG:core:Platform is 
> Linux-3.2.0-41-generic-pae-i686-with-Ubuntu-12.04-precise
> INFO:core:POX 0.1.0 (betta) is up.
> DEBUG:openflow.of_01:Listening on 0.0.0.0:6633
> INFO:openflow.of_01:[00-50-04-9d-16-db 1] connected
> ERROR:openflow.of_01:[00-50-04-9d-16-db 1] OpenFlow Error:
> [00-50-04-9d-16-db 1] Error: header:
> [00-50-04-9d-16-db 1] Error:   version: 1
> [00-50-04-9d-16-db 1] Error:   type:    1 (OFPT_ERROR)
> [00-50-04-9d-16-db 1] Error:   length:  32
> [00-50-04-9d-16-db 1] Error:   xid:     6
> [00-50-04-9d-16-db 1] Error: type: OFPET_BAD_REQUEST (1)
> [00-50-04-9d-16-db 1] Error: code: OFPBRC_BAD_SUBTYPE (4)
> [00-50-04-9d-16-db 1] Error: datalen: 20
> [00-50-04-9d-16-db 1] Error: 0000: 01 04 00 14 00 00 00 06  00 00 23 20 00 00 
> 00 10   ..........# ....
> [00-50-04-9d-16-db 1] Error: 0010: 00 00 00 01                                
>         ....
> INFO:forwarding.l2_nx:[00-50-04-9d-16-db 1] ready
> 
> And I lose communication with the hosts
> 
> I don't see where is the problem and don't know how to correct it.
> 
> Thanks in advance 
> 
> 

Reply via email to