Can you provide your ml2_conf.ini values you are using? On Thu, Jun 22, 2017 at 7:06 AM, Margin Hu <today.g...@163.com> wrote:
> thanks. > > I met an issue , I configured three ovs bridge ( br-ex, provision, > provider) in ml2_conf.ini but after I reboot the node , found only 2 > bridges flow table is normal , the other one bridge's flow table is empty. > > the bridge sometimes is "provision" , sometimes is "provider" , which > possibilities is there for this issue.? > [root@cloud]# ovs-ofctl show provision > OFPT_FEATURES_REPLY (xid=0x2): dpid:0000248a075541e8 > n_tables:254, n_buffers:256 > capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP > actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src > mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst > 1(bond0): addr:24:8a:07:55:41:e8 > config: 0 > state: 0 > speed: 0 Mbps now, 0 Mbps max > 2(phy-provision): addr:2e:7c:ba:fe:91:72 > config: 0 > state: 0 > speed: 0 Mbps now, 0 Mbps max > LOCAL(provision): addr:24:8a:07:55:41:e8 > config: 0 > state: 0 > speed: 0 Mbps now, 0 Mbps max > OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0 > [root@cloud]# ovs-ofctl dump-flows provision > NXST_FLOW reply (xid=0x4): > > [root@cloud]# ip r > default via 192.168.60.247 dev br-ex > 10.53.16.0/24 dev vlan16 proto kernel scope link src 10.53.16.11 > 10.53.17.0/24 dev provider proto kernel scope link src 10.53.17.11 > 10.53.22.0/24 dev vlan22 proto kernel scope link src 10.53.22.111 > 10.53.32.0/24 dev vlan32 proto kernel scope link src 10.53.32.11 > 10.53.33.0/24 dev provision proto kernel scope link src 10.53.33.11 > 10.53.128.0/24 dev docker0 proto kernel scope link src 10.53.128.1 > 169.254.0.0/16 dev vlan16 scope link metric 1012 > 169.254.0.0/16 dev vlan22 scope link metric 1014 > 169.254.0.0/16 dev vlan32 scope link metric 1015 > 169.254.0.0/16 dev br-ex scope link metric 1032 > 169.254.0.0/16 dev provision scope link metric 1033 > 169.254.0.0/16 dev provider scope link metric 1034 > 192.168.60.0/24 dev br-ex proto kernel scope link src 192.168.60.111 > > what' the root cause ? > > rpm -qa | grep openvswitch > openvswitch-2.6.1-4.1.git20161206.el7.x86_64 > python-openvswitch-2.6.1-4.1.git20161206.el7.noarch > openstack-neutron-openvswitch-10.0.1-1.el7.noarch > > > > On 6/22 9:53, Kevin Benton wrote: > > Rules to allow aren't setup until the port is wired and it calls the > functions like this: > https://github.com/openstack/neutron/blob/master/neutron/ > plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L602-L606 > > On Wed, Jun 21, 2017 at 4:49 PM, Margin Hu <today.g...@163.com> wrote: > >> Hi Guys, >> >> I have a question in setup_physical_bridges funtion of >> neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py >> >> # block all untranslated traffic between bridges >> self.int_br.drop_port(in_port=int_ofport) >> br.drop_port(in_port=phys_ofport) >> >> [refer](https://github.com/openstack/neutron/blob/master/neu >> tron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1159) >> >> when permit traffic between bridges ? when modify flow table of ovs >> bridge? >> >> >> >> >> >> >> >> >> >> ____________________________________________________________ >> ______________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib >> e >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
