openvswitch - received packet on unknown port

czechsys

Renowned Member
Nov 18, 2015
414
41
93
Hi,

pve5, openvswitch with this config:

Code:
iface ens1f0 inet manual

iface ens1f1 inet manual

allow-vmbr0 bond0
iface bond0 inet manual
    ovs_bridge vmbr0
    ovs_type OVSBond
    ovs_bonds ens1f0 ens1f1
    ovs_options lacp=active bond-mode=balance-tcp
    pre-up ( /sbin/ip link set ens1f0 mtu 9000 && /sbin/ip link set ens1f1 mtu 9000 )
    up /sbin/ip link set mtu 9000 bond0

auto vmbr0
iface vmbr0 inet manual
    ovs_type OVSBridge
    ovs_ports bond0 pve_mgmt
    mtu 9000

allow-vmbr0 pve_mgmt
iface pve_mgmt inet static
    address IP
    netmask MASK
    gateway GW
    ovs_type OVSIntPort
    ovs_bridge vmbr0
    ovs_options tag=TAG
    mtu 1500
#pve-backup-1 node management

Problem with "unknown port 3" in the ovs-vswitchd.log:
Code:
2017-10-05T14:28:36.922Z|00017|bridge|INFO|bridge vmbr0: added interface vmbr0 on port 65534
2017-10-05T14:28:36.922Z|00018|bridge|INFO|bridge vmbr0: using datapath ID 00003e4ade9d4e42
2017-10-05T14:28:36.922Z|00019|connmgr|INFO|vmbr0: added service controller "punix:/var/run/openvswitch/vmbr0.mgmt"
2017-10-05T14:28:37.024Z|00020|bridge|INFO|bridge vmbr0: added interface ens1f0 on port 1
2017-10-05T14:28:37.073Z|00021|bridge|INFO|bridge vmbr0: added interface ens1f1 on port 2
2017-10-05T14:28:37.076Z|00022|bridge|INFO|bridge vmbr0: using datapath ID 00003cfdfeab18e4
2017-10-05T14:28:37.089Z|00001|ofproto_dpif_xlate(handler34)|WARN|received packet on unknown port 3 while processing pkt_mark=0xd4,skb_priority=0x7,ct_state=new|trk,icmp6,in_port=3,vlan_tci=0x0000,dl_src=aa:be:78:fa:6a:75,dl_dst=33:33:00:00:00:16,ipv6_src=::,ipv6_dst=ff02::16,ipv6_label=0x00000,nw_tos=0,nw_ecn=0,nw_ttl=1,icmp_type=143,icmp_code=0,nd_target=::,nd_sll=00:00:00:00:00:00,nd_tll=00:00:00:00:00:00 on bridge vmbr0
2017-10-05T14:28:37.189Z|00001|ofproto_dpif_xlate(handler33)|WARN|received packet on unknown port 3 while processing ct_state=new|trk,icmp6,in_port=3,vlan_tci=0x0000,dl_src=aa:be:78:fa:6a:75,dl_dst=33:33:ff:fa:6a:75,ipv6_src=::,ipv6_dst=ff02::1:fffa:6a75,ipv6_label=0x00000,nw_tos=0,nw_ecn=0,nw_ttl=255,icmp_type=135,icmp_code=0,nd_target=fe80::a8be:78ff:fefa:6a75,nd_sll=00:00:00:00:00:00,nd_tll=00:00:00:00:00:00 on bridge vmbr0
2017-10-05T14:28:37.402Z|00023|bridge|INFO|bridge vmbr0: added interface pve_mgmt on port 4
2017-10-05T14:28:38.093Z|00024|bond|INFO|interface ens1f0: link state up
2017-10-05T14:28:38.093Z|00025|bond|INFO|interface ens1f0: enabled
2017-10-05T14:28:38.093Z|00026|bond|INFO|bond bond0: active interface is now ens1f0
2017-10-05T14:28:38.097Z|00027|bond|INFO|interface ens1f1: link state up
2017-10-05T14:28:38.097Z|00028|bond|INFO|interface ens1f1: enabled
2017-10-05T14:28:38.191Z|00001|ofproto_dpif_xlate(handler27)|WARN|received packet on unknown port 3 while processing in_port=3,vlan_tci=0x0000,dl_src=aa:be:78:fa:6a:75,dl_dst=01:80:c2:00:00:0e,dl_type=0x88cc on bridge vmbr0
2017-10-05T14:28:38.221Z|00001|ofproto_dpif_xlate(handler29)|WARN|received packet on unknown port 3 while processing ct_state=new|trk,icmp6,in_port=3,vlan_tci=0x0000,dl_src=aa:be:78:fa:6a:75,dl_dst=33:33:00:00:00:02,ipv6_src=fe80::a8be:78ff:fefa:6a75,ipv6_dst=ff02::2,ipv6_label=0x00000,nw_tos=0,nw_ecn=0,nw_ttl=255,icmp_type=133,icmp_code=0,nd_target=::,nd_sll=00:00:00:00:00:00,nd_tll=00:00:00:00:00:00 on bridge vmbr0
2017-10-05T14:28:46.763Z|00029|memory|INFO|218168 kB peak resident set size after 10.0 seconds
2017-10-05T14:28:46.763Z|00030|memory|INFO|handlers:17 ports:5 revalidators:7 rules:261 udpif keys:31
2017-10-05T14:28:47.293Z|00031|bridge|INFO|bridge vmbr0: added interface tap100i0 on port 5
2017-10-05T14:28:48.538Z|00032|bridge|INFO|bridge vmbr0: added interface tap100i1 on port 6
2017-10-05T14:29:08.173Z|00002|ofproto_dpif_xlate(handler29)|WARN|received packet on unknown port 3 while processing ct_state=new|trk,icmp6,in_port=3,vlan_tci=0x0000,dl_src=aa:be:78:fa:6a:75,dl_dst=33:33:00:00:00:02,ipv6_src=fe80::a8be:78ff:fefa:6a75,ipv6_dst=ff02::2,ipv6_label=0x00000,nw_tos=0,nw_ecn=0,nw_ttl=255,icmp_type=133,icmp_code=0,nd_target=::,nd_sll=00:00:00:00:00:00,nd_tll=00:00:00:00:00:00 on bridge vmbr0
2017-10-05T14:29:38.192Z|00002|ofproto_dpif_xlate(handler27)|WARN|Dropped 1 log messages in last 30 seconds (most recently, 30 seconds ago) due to excessive rate
2017-10-05T14:29:38.192Z|00003|ofproto_dpif_xlate(handler27)|WARN|received packet on unknown port 3 while processing in_port=3,vlan_tci=0x0000,dl_src=aa:be:78:fa:6a:75,dl_dst=01:80:c2:00:00:0e,dl_type=0x88cc on bridge vmbr0

ovs-dpctl show:
Code:
system@ovs-system:
    lookups: hit:2304 missed:131 lost:0
    flows: 7
    masks: hit:14351 total:7 hit/pkt:5.89
    port 0: ovs-system (internal)
    port 1: vmbr0 (internal)
    port 2: ens1f0
    port 3: ens1f1
    port 4: bond0 (internal)
    port 5: pve_mgmt (internal)
    port 6: tap100i0
    port 7: tap100i1

Any idea, where is problem? In the log the port numbers != ovs-dpctl port numbers...Openvswitch mailing list with this problem is without answer :/
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!