Hi,
Attached is a logfile.
It seems that the problem is related to LLDP messages that come from
"bad in-port" i.e. a port that is not connected to ovs. My setup is the
following:
NOX linux1
| |
-----------------------192.168.4.0/24
|
linux3----OVS--------linux2
OVS has ports 1(eth0, towards linux3), 2(eth1, towards linux2), 3 and 4
(gre0 and gre1 towards linux1). In addition to this the machine where
OVS is running has eth2 that is not connected as a port to OVS but has
an IP address (.101) towards the 192.168.4.0/24 subnet. (Gre tunnels do
not work if this port is connected to OVS). Are there any possibilities
to have the gre tunnels and connection to NOX via this same eth2? The
limitation is that NOX and Linux1 have only one interface, and I'd like
to avoid adding a router in between also if possible.
Otherwise the connection to NOX seems to be ok and also the gre tunnels
are working fine.
Thanks a lot for your help,
Johanna
>-----Original Message-----
>From: ext Ben Pfaff [mailto:[email protected]]
>Sent: Wednesday, January 18, 2012 8:46 PM
>To: Heinonen, Johanna (NSN - FI/Espoo)
>Cc: [email protected]
>Subject: Re: [ovs-discuss] GRE tunnel creation fails: "applying
"create"
>command to table Interface without --id option will have no effect"
>
>On Wed, Jan 18, 2012 at 12:59:59PM +0200, Heinonen, Johanna (NSN -
>FI/Espoo) wrote:
>> When connection from ovs to NOX openflow controller is made, ovs
sends
>> continuously error messages approximately once per second in the
>> following way:
>> NOX->OVS: vendor (SM)
>> OVS->NOX: Error (SM)
>> NOX->OVS: Flow Mod (CSM)
>> OVS->NOX: Error (SM)
>> OVS->NOX: Error (SM)
>> OVS->NOX: Error (SM)
>> OVS->NOX: Error (SM)
>> OVS->NOX: Error (SM)
>> ...
>>
>> Is there any way to suppress these messages? The error type is
unknown
>> (45250) and error code 0.
>
>Suppressing errors without any idea of their cause doesn't make any
>sense. Please obtain a proper dump of the traffic, e.g. with
>"ovs-ofctl snoop" or by turning up the log level on the "vconn" log
>module, and pass that along.
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44407|vconn|DBG|tcp:192.168.4.102:6633:
sent (Success): OFPT_HELLO (xid=0x11):
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44408|vconn|DBG|tcp:192.168.4.102:6633:
received: OFPT_HELLO (xid=0x1010000):
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44409|vconn|DBG|tcp:192.168.4.102:6633:
negotiated OpenFlow version 0x01 (we support versions 0x01 to 0x01 inclusive,
peer no later than version 0x01)
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44410|rconn|INFO|br0<->tcp:192.168.4.102:
connected
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44411|vconn|DBG|tcp:192.168.4.102:6633:
received: OFPT_FEATURES_REQUEST (xid=0x2010000):
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44412|vconn|DBG|tcp:192.168.4.102:6633:
sent (Success): OFPT_FEATURES_REPLY (xid=0x2010000): ver:0x1,
dpid:0000000000000001
Jan 19 12:40:18 ovs-new ovs-vswitchd: n_tables:255, n_buffers:256
Jan 19 12:40:18 ovs-new ovs-vswitchd: features: capabilities:0xc7, actions:0xfff
Jan 19 12:40:18 ovs-new ovs-vswitchd: 1(eth0): addr:08:00:27:c1:51:13
Jan 19 12:40:18 ovs-new ovs-vswitchd: config: 0
Jan 19 12:40:18 ovs-new ovs-vswitchd: state: 0
Jan 19 12:40:18 ovs-new ovs-vswitchd: current: 100MB-FD AUTO_NEG
Jan 19 12:40:18 ovs-new ovs-vswitchd: advertised: 10MB-HD 10MB-FD 100MB-HD
100MB-FD COPPER AUTO_NEG
Jan 19 12:40:18 ovs-new ovs-vswitchd: supported: 10MB-HD 10MB-FD 100MB-HD
100MB-FD COPPER AUTO_NEG
Jan 19 12:40:18 ovs-new ovs-vswitchd: 2(eth1): addr:08:00:27:ad:aa:c1
Jan 19 12:40:18 ovs-new ovs-vswitchd: config: 0
Jan 19 12:40:18 ovs-new ovs-vswitchd: state: 0
Jan 19 12:40:18 ovs-new ovs-vswitchd: current: 100MB-FD AUTO_NEG
Jan 19 12:40:18 ovs-new ovs-vswitchd: advertised: 10MB-HD 10MB-FD 100MB-HD
100MB-FD COPPER AUTO_NEG
Jan 19 12:40:18 ovs-new ovs-vswitchd: supported: 10MB-HD 10MB-FD 100MB-HD
100MB-FD COPPER AUTO_NEG
Jan 19 12:40:18 ovs-new ovs-vswitchd: 3(gre1): addr:06:ac:48:d9:51:7c
Jan 19 12:40:18 ovs-new ovs-vswitchd: config: 0
Jan 19 12:40:18 ovs-new ovs-vswitchd: state: 0
Jan 19 12:40:18 ovs-new ovs-vswitchd: 4(gre2): addr:7a:44:70:31:0b:6e
Jan 19 12:40:18 ovs-new ovs-vswitchd: config: 0
Jan 19 12:40:18 ovs-new ovs-vswitchd: state: 0
Jan 19 12:40:18 ovs-new ovs-vswitchd: LOCAL(br0): addr:08:00:27:ad:aa:c1
Jan 19 12:40:18 ovs-new ovs-vswitchd: config: 0
Jan 19 12:40:18 ovs-new ovs-vswitchd: state: 0
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44413|vconn|DBG|tcp:192.168.4.102:6633:
received: OFPT_SET_CONFIG (xid=0x3010000): frags=normal miss_send_len=65535
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44414|ofp_util|WARN|received Nicira
extension message of unknown type 8
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44415|vconn|DBG|tcp:192.168.4.102:6633:
received: ***decode error: OFPBRC_BAD_SUBTYPE***
Jan 19 12:40:18 ovs-new ovs-vswitchd: 00000000 01 04 00 18 04 01 00 00-00 00
23 20 00 00 00 08 |..........# ....|
Jan 19 12:40:18 ovs-new ovs-vswitchd: 00000010 00 00 00 00 00 00 00 00-
|........ |
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44416|ofp_util|WARN|received Nicira
extension message of unknown type 8
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44417|connmgr|INFO|Dropped 11 log
messages in last 16 seconds (most recently, 15 seconds ago) due to excessive
rate
Jan 19 12:40:18 ovs-new ovs-vswitchd:
44418|connmgr|INFO|br0<->tcp:192.168.4.102: sending OFPBRC_BAD_SUBTYPE error
reply to invalid message
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44419|vconn|DBG|tcp:192.168.4.102:6633:
sent (Success): OFPT_ERROR (xid=0x4010000): OFPBRC_BAD_SUBTYPE
Jan 19 12:40:18 ovs-new ovs-vswitchd: ***decode error: OFPBRC_BAD_SUBTYPE***
Jan 19 12:40:18 ovs-new ovs-vswitchd: 00000000 01 04 00 18 04 01 00 00-00 00
23 20 00 00 00 08 |..........# ....|
Jan 19 12:40:18 ovs-new ovs-vswitchd: 00000010 00 00 00 00 00 00 00 00-
|........ |
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44420|vconn|DBG|tcp:192.168.4.102:6633:
received: OFPT_FLOW_MOD (xid=0x38145b00): DEL priority=0 buf:0x0 actions=drop
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44421|fail_open|WARN|No longer in
fail-open mode
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44422|vconn|DBG|tcp:192.168.4.102:6633:
received: OFPT_PACKET_OUT (xid=0x0): in_port=CONTROLLER actions_len=8
actions=output:1 data_len=34
Jan 19 12:40:18 ovs-new ovs-vswitchd: priority:0,tunnel:0,in_port:0000,tci(0)
mac(00:00:00:00:00:01->01:23:20:00:00:01) type:88cc proto:0 tos:0 ttl:0
ip(0.0.0.0->0.0.0.0)
Jan 19 12:40:18 ovs-new ovs-vswitchd:
44423|connmgr|INFO|br0<->tcp:192.168.4.102: sending NXBRC_BAD_IN_PORT error
reply to OFPT_PACKET_OUT message
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44424|vconn|DBG|tcp:192.168.4.102:6633:
sent (Success): OFPT_ERROR (xid=0x0): NXBRC_BAD_IN_PORT
Jan 19 12:40:18 ovs-new ovs-vswitchd: OFPT_PACKET_OUT (xid=0x0):
in_port=CONTROLLER actions_len=8 actions=output:1 data_len=34
Jan 19 12:40:18 ovs-new ovs-vswitchd: priority:0,tunnel:0,in_port:0000,tci(0)
mac(00:00:00:00:00:01->01:23:20:00:00:01) type:88cc proto:0 tos:0 ttl:0
ip(0.0.0.0->0.0.0.0)
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44425|vconn|DBG|tcp:192.168.4.102:6633:
received: OFPT_PACKET_OUT (xid=0x0): in_port=CONTROLLER actions_len=8
actions=output:2 data_len=34
Jan 19 12:40:18 ovs-new ovs-vswitchd: priority:0,tunnel:0,in_port:0000,tci(0)
mac(00:00:00:00:00:01->01:23:20:00:00:01) type:88cc proto:0 tos:0 ttl:0
ip(0.0.0.0->0.0.0.0)
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44426|vconn|DBG|tcp:192.168.4.102:6633:
sent (Success): OFPT_ERROR (xid=0x0): NXBRC_BAD_IN_PORT
Jan 19 12:40:18 ovs-new ovs-vswitchd: OFPT_PACKET_OUT (xid=0x0):
in_port=CONTROLLER actions_len=8 actions=output:2 data_len=34
Jan 19 12:40:18 ovs-new ovs-vswitchd: priority:0,tunnel:0,in_port:0000,tci(0)
mac(00:00:00:00:00:01->01:23:20:00:00:01) type:88cc proto:0 tos:0 ttl:0
ip(0.0.0.0->0.0.0.0)
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44427|vconn|DBG|tcp:192.168.4.102:6633:
received: OFPT_PACKET_OUT (xid=0x0): in_port=CONTROLLER actions_len=8
actions=output:3 data_len=34
Jan 19 12:40:18 ovs-new ovs-vswitchd: priority:0,tunnel:0,in_port:0000,tci(0)
mac(00:00:00:00:00:01->01:23:20:00:00:01) type:88cc proto:0 tos:0 ttl:0
ip(0.0.0.0->0.0.0.0)
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44428|vconn|DBG|tcp:192.168.4.102:6633:
sent (Success): OFPT_ERROR (xid=0x0): NXBRC_BAD_IN_PORT
Jan 19 12:40:18 ovs-new ovs-vswitchd: OFPT_PACKET_OUT (xid=0x0):
in_port=CONTROLLER actions_len=8 actions=output:3 data_len=34
Jan 19 12:40:18 ovs-new ovs-vswitchd: priority:0,tunnel:0,in_port:0000,tci(0)
mac(00:00:00:00:00:01->01:23:20:00:00:01) type:88cc proto:0 tos:0 ttl:0
ip(0.0.0.0->0.0.0.0)
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44429|vconn|DBG|tcp:192.168.4.102:6633:
received: OFPT_PACKET_OUT (xid=0x0): in_port=CONTROLLER actions_len=8
actions=output:4 data_len=34
Jan 19 12:40:18 ovs-new ovs-vswitchd: priority:0,tunnel:0,in_port:0000,tci(0)
mac(00:00:00:00:00:01->01:23:20:00:00:01) type:88cc proto:0 tos:0 ttl:0
ip(0.0.0.0->0.0.0.0)
Jan 19 12:40:18 ovs-new ovs-vswitchd: 44430|vconn|DBG|tcp:192.168.4.102:6633:
sent (Success): OFPT_ERROR (xid=0x0): NXBRC_BAD_IN_PORT
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
