On Thu, Apr 13, 2017 at 05:01:56PM +0530, Pradeep Antil wrote: > Let me give the background of my setup. I have CentOS 6.8 KVM hypervisor > along with OVS 2.5. I have build the openvswitch rpm and then install it. > Installation was successful. > > I have created a bride with name br0 and add bond interface to the bridge > and my bond consists of 4 Lan Cards ( eth2, eth3 , eth4 & eth5), Below are > the exact commands > > Lan Ports eth2,3,4,5 are already on Trunk mode on switch > > > ovs-vsctl add-br br0 > > ifconfig br0 up > ovs-vsctl add-bond br0 bond0 eth2 eth3 eth4 eth5 bond_mode=balance-slb > other_config:bond-detect-mode=miimon other_config:bond-miimon-interval=100 > other_config:trunks=3,4,5,8,12,13,10,11 other_config:bond_updelay=100 > other_config:lacp-time=fast
This is a strange configuration. It requests balance-slb, which is only for bonds that are connected to a physical switch that cannot recognize the ports as bonded, and LACP, which only for physical switches that do understand bonding. It also requests miimon, which as far as I know is only for old, broken drivers. (I'd be happy to be corrected on this point; if it is wrong, then I'd like to update the documentation to explain properly.) > ovs-vsctl set interface eth2 other-config:enable-vlan-splinters=true > ovs-vsctl set interface eth3 other-config:enable-vlan-splinters=true > ovs-vsctl set interface eth4 other-config:enable-vlan-splinters=true > ovs-vsctl set interface eth5 other-config:enable-vlan-splinters=true enable-vlan-splinters is definitely only for old, broken drivers. It was removed from OVS 2.6. You should not use it if you use Linux kernel 3.3 or later. > *When i boot the VM with fake bridge , i not able to ping and access it. > Any idea how to troubleshoot further and resolve the issue.* > Below is the output of ovs-vsctl command > > [root@eginosrvhyp15 ~]# ovs-vsctl show > efbab8e3-7fb7-4835-93c1-4b8aa9963134 > Bridge "br0" > Port "br0" > Interface "br0" > type: internal > Port "br13" > tag: 13 > Interface "br13" > type: internal > Port "bond0" > Interface "eth5" > Interface "eth4" > Interface "eth3" > Interface "eth2" > Port "vnet0" > tag: 13 > Interface "vnet0" > ovs_version: "2.5.0" > [root@eginosrvhyp15 ~]# Is the VM or machine that you're trying to ping also on VLAN 13? (I know, stupid question, but a surprising number of people who have this problem do not actually know the answer.) _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
