Dear friends,

I have not found a solution yet, and feels it is a matter of some basic config 
error. Kindly help!

Let me rephrase the scenario again:

I want to know procedure to setup bridge on top of an existing bond interface 
which is configured using linux native bonding.

I have configured "bond0" bond interface using eth1 and eth2 using mode=4 (alb) 
in the CentOS 6.4 host, and LACP configured in the physical switches (stacked). 

Later I tested it by assigning an IP address to the bond0 bond interface, and 
it seems to be working just fine! I could successfully ping the default gateway.

Please note that the physical switch ports to which eth1 & eth2 are connected 
is configured as access ports for VLAN 1200.

Later I removed the IP Address from bond interface (bond0) which I had created 
(but retained the bonding configurations in the 
/etc/sysconfig/network-scripts/ifcfg-bond0 ). -- please refer the attached file 
for reference

Now I want to create a main bridge named "cloudbr" using open vswitch on top of 
this native linux bond interface (bond0),  and finally create an internal port 
named "vlan1200", assign an IP address to it, so as to connect from externally 
for management purpose.

I have tried the same using ovs-vsctl command, but it is failing. Please find 
the commands I had executed:

# ovs-vsctl add-br cloudbr
# ovs-vsctl add-port cloudbr bond0
# ovs-vsctl add-port cloudbr vlan1200 tag=1200 -- set interface vlan1200 
type=internal
# ifconfig vlan1200 192.168.120.100 netmask 255.255.255.0 broadcast 
192.168.120.255 up
# ovs-vsctl show
01c9bfe9-8d4b-4d9e-bf5c-a0be244583d9
    Bridge cloudbr
        Port cloudbr
            tag: 1200
            Interface cloudbr
                type: internal
        Port "bond0"
            tag: 1200
            Interface "bond0"
        Port "vlan1200"
            tag: 1200
            Interface "vlan1200"
                type: internal
    ovs_version: "1.10.0"

# ping 192.168.120.1 (trying to ping the default gateway)
PING 192.168.120.1 (192.168.120.1) 56(84) bytes of data.
>From 192.168.120.100 icmp_seq=1 Destination Host Unreachable
>From 192.168.120.100 icmp_seq=2 Destination Host Unreachable
>From 192.168.120.100 icmp_seq=3 Destination Host Unreachable
>From 192.168.120.100 icmp_seq=5 Destination Host Unreachable
>From 192.168.120.100 icmp_seq=6 Destination Host Unreachable
>From 192.168.120.100 icmp_seq=7 Destination Host Unreachable
>From 192.168.120.100 icmp_seq=9 Destination Host Unreachable
>From 192.168.120.100 icmp_seq=10 Destination Host Unreachable
>From 192.168.120.100 icmp_seq=11 Destination Host Unreachable
>From 192.168.120.100 icmp_seq=13 Destination Host Unreachable
>From 192.168.120.100 icmp_seq=14 Destination Host Unreachable
>From 192.168.120.100 icmp_seq=15 Destination Host Unreachable
>From 192.168.120.100 icmp_seq=17 Destination Host Unreachable
>From 192.168.120.100 icmp_seq=18 Destination Host Unreachable

I even tried adding the "vlan_mode=native-tagged" option to the bond0 port, but 
with no success.

# ovs-vsctl add-port cloudbr bond0 tag=1200 vlan_mode=native-taggedKindly guide 
me to find a solution to this issue which has been haunting me for days 
together :-(

Thanks & Kind Regards,
Ashraf Khalid


                                          

Attachment: command output.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document

_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to