Re: [ovs-discuss] unexpected behavior in ovs faucet tutorial

Hi, Lee Thanks for your advice. I tried to use faucet 1.6.16 and modify faucet.yaml to be like this dps: switch-1: dp_id: 0x1 timeout: 3600 arp_neighbor_timeout: 3600 interfaces: 1: native_vlan: 100 2:

Re: [ovs-discuss] unexpected behavior in ovs faucet tutorial

On Tue, Jan 16, 2018 at 3:04 PM, Hongwei Du wrote: > Hi, > > I'm following the ovs faucet tutorial to get familiar with > openvswitch. Everything goes smoothly until section Triggering MAC > Learning. > > I tried the ovs-appctl ofproto/trace ... ... -generate command, but no >

[ovs-discuss] unexpected behavior in ovs faucet tutorial

Hi, I'm following the ovs faucet tutorial to get familiar with openvswitch. Everything goes smoothly until section Triggering MAC Learning. I tried the ovs-appctl ofproto/trace ... ... -generate command, but no new logs showed in inst/faucet.log, and diff-flows also gives nothing. I'm using ovs

Re: [ovs-discuss] REDHAT: Route issue with dpdk-bond ports

Hi Flavio, Thanks for looking into this issue. I believe the order of initialization does not matter. Just an FYI: I tried with your suggestion of renaming the bridge name to zbr0 but it did not solve the issue. In my opinion the issue is with networking scripts which is not triggering

Re: [ovs-discuss] REDHAT: Route issue with dpdk-bond ports

On Tue, Dec 26, 2017 at 08:31:49AM +, Vishal Deep Ajmera wrote: > Hi, > > On Red-Hat, kernel IP Routes are getting deleted whenever a dpdk-bond port is > added to "netdev" type bridge. I understand that when a DPDK port is added to > ovs, the bridge port (LOCAL) is reconfigured with MAC

Re: [ovs-discuss] OVS port name differ from interface name

On Mon, Jan 15, 2018 at 09:50:52AM -0800, Fred Licht wrote: >Is it possible to have an OVS port ‘name’ differ from the interface name? > > Bridge ovs-ha-sw > Port ovs-ha-sw > Interface ovs-ha-sw > type: internal > Port "bond1" >

[ovs-discuss] OVS port name differ from interface name

Hi, Is it possible to have an OVS port ‘name’ differ from the interface name? Bridge ovs-ha-sw Port ovs-ha-sw Interface ovs-ha-sw type: internal Port "bond1" Interface "bond1" To have the effect of: Bridge ovs-ha-sw Port

Re: [ovs-discuss] clustered OVSDB in 2.9 or 2.10?

On Mon, Jan 15, 2018 at 2:30 AM, Numan Siddique wrote: > > > On Fri, Jan 12, 2018 at 1:28 AM, Ben Pfaff wrote: >> >> I posted the patches to add clustering support to OVSDB at the end of >> last year so that it was technically qualified to make it into OVS 2.9.