[NETVIRT-233] missing rules in elan broadcast group Created: 02/Nov/16  Updated: 19/Oct/17  Resolved: 21/Nov/16

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Boron
Fix Version/s: None

Type: Bug
Reporter: Koby Aizer Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: Zip Archive models.zip     Zip Archive odl.zip    
Issue Links:
Duplicate
duplicates GENIUS-30 Auto tunnels feature doesn't config a... Resolved
External issue ID: 7079

 Description   

Running a setup with 40 computes (not sure whether it is related or not), and for some reason the elan broadcast group (210001) is missing the qdhcp interface, and also missing the vxlan tunnel to the compute holding a VM connected to that network:

dump groups on the control/ODL node:
OFPST_GROUP_DESC reply (OF1.3) (xid=0x2):
group_id=200000,type=all,bucket=actions=set_field:00:1c:73:4e:d3:31->eth_dst,load:0x300->NXM_NX_REG6[],resubmit(,220)
group_id=210003,type=all
group_id=210004,type=all,bucket=actions=group:210003
group_id=150000,type=all,bucket=actions=set_field:fa:16:3e:c6:47:97->eth_dst,load:0x100->NXM_NX_REG6[],resubmit(,220)
group_id=210002,type=all,bucket=actions=group:210001
group_id=210001,type=all

dump groups on the compute node:
stack@nvp-scale-1-c6-bl-5-compute-1:~$ sudo ovs-ofctl -OOpenFlow13 dump-groups br-int | sort -n
group_id=150001,type=all,bucket=actions=set_field:fa:16:3e:69:8b:1a->eth_dst,load:0x2a00->NXM_NX_REG6[],resubmit(,220)
group_id=200000,type=all,bucket=actions=set_field:00:1c:73:4e:d3:31->eth_dst,load:0x2300->NXM_NX_REG6[],resubmit(,220)
group_id=200001,type=all
group_id=210001,type=all,bucket=actions=set_field:0x2a->tun_id,resubmit(,55)
group_id=210002,type=all,bucket=actions=group:210001,bucket=actions=set_field:0x1389->tun_id,output:3
group_id=210003,type=all
group_id=210004,type=all,bucket=actions=group:210003,bucket=actions=set_field:0x138a->tun_id,output:3

Attached several models outputs (ietf interface, elan, elaninterfaces) and ODL log

 Comments   
Comment by Koby Aizer [ 02/Nov/16 ]

The DHCP interface is:
ec418278-ce4d-4e9f-83e6-667fd1c16ee

ovs-vsctl show output on the control node:
stack@c6-bl-1:/opt/stack/opendaylight/distribution-karaf-0.5.1-SNAPSHOT$ sudo ovs-vsctl show
bfec0651-1e96-4dd3-8766-1e6c52e571c7
Manager "tcp:172.16.1.240:6640"
is_connected: true
Bridge br-int
Controller "tcp:172.16.1.240:6653"
is_connected: true
fail_mode: secure
Port "tun9b14421ffb8"
Interface "tun9b14421ffb8"
type: vxlan
options:

{key=flow, local_ip="172.16.1.240", remote_ip="10.0.80.180"}
Port "tun2ce620ced33"
Interface "tun2ce620ced33"
type: vxlan
options: {key=flow, local_ip="172.16.1.240", remote_ip="10.0.80.180"}

Port "tapec418278-ce"
Interface "tapec418278-ce"
type: internal
Port br-int
Interface br-int
type: internal
Port "eno50.475"
Interface "eno50.475"
ovs_version: "2.5.0"

Comment by Koby Aizer [ 02/Nov/16 ]

Attachment models.zip has been added with description: mdsal models

Comment by Koby Aizer [ 02/Nov/16 ]

Attachment odl.zip has been added with description: odl log

Comment by Koby Aizer [ 02/Nov/16 ]

Restarting OVS workarounds this issue:
OFPST_GROUP_DESC reply (OF1.3) (xid=0x2):
group_id=210004,type=all,bucket=actions=group:210003,bucket=actions=set_field:0x138a->tun_id,output:7
group_id=200000,type=all,bucket=actions=set_field:00:1c:73:4e:d3:31->eth_dst,load:0x300->NXM_NX_REG6[],resubmit(,220)
group_id=210003,type=all
group_id=150000,type=all,bucket=actions=set_field:fa:16:3e:c6:47:97->eth_dst,load:0x100->NXM_NX_REG6[],resubmit(,220)
group_id=210002,type=all,bucket=actions=group:210001,bucket=actions=set_field:0x1389->tun_id,output:7
group_id=210001,type=all,bucket=actions=set_field:0x1->tun_id,resubmit(,55)

Comment by Olga Schukin [ 21/Nov/16 ]

The root cause is GENIUS-30 - not all tunnels created

Comment by Olga Schukin [ 21/Nov/16 ]

The root cause is GENIUS-30 - not all tunnels created

Generated at Wed Feb 07 20:21:02 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.