[PKG-Openstack-devel] [ovs-dev] Bug#771863: Bug#771863: Bug#771863: Service does not start or parse interfaces correctly
Gurucharan Shetty
shettyg at nicira.com
Tue Dec 30 17:25:02 UTC 2014
>> Then ovs networks starts automatically on boot also without "auto", is it
>> correct?
Yes.
>
>
> I tried also other network type and bonding following
> openvswitch-switch.README.Debian and is not working:
>
> allow-ovs xenbr0
> iface xenbr0 inet static
> address 192.168.1.90
> netmask 255.255.255.0
> network 192.168.1.0
> broadcast 192.168.1.255
> gateway 192.168.1.200
> ovs_type OVSBridge
> ovs_ports bond0
>
> allow-xenbr0 bond0
> iface bond0 inet manual
> # pre-up ip link set dev eth0 up
> # pre-up ip link set dev eth1 up
> ovs_bridge xenbr0
> ovs_type OVSBond
> ovs_bonds eth0 eth1
> ovs_options bond_mode=balance-tcp lacp=active
Your above config looks alright to me. What does 'ovs-vsctl show' say?
If it shows 'xenbr0', do a 'ovs-vsctl del-br xenbr0' (If xenbr0 is
what you use for ssh connectivity, you probably should do it using
serial console to avoid losing any ssh connectivity) and then follow
it by:
ifup --allow=ovs xenbr0
Does the above give any error? if so, what? What does 'ovs-vsctl show' say now?
You don't need things below with 'allow-bond0' (The readme does not
mention them). You can remove them.
>
> allow-bond0 eth0
> iface eth0 inet manual
> ovs_bridge bond0
> ovs_type OVSPort
>
> allow-bond0 eth1
> iface eth1 inet manual
> ovs_bridge bond0
> ovs_type OVSPort
>
>
More information about the Openstack-devel
mailing list