Daniel Dehennin <daniel.dehen...@baby-gnu.org> writes:

> Hello,
>
> I have 3 hypervisors with two OVS bridges:
>
> - phybr0: connected to physical infrastructure though bond0 trunk to give
>   access to physical VLANs
>
> - vibr0: for user virtual networks disconnected from physical
>   infrastructure, 1 network == 1 VLAN
>
> Each hypervisor has an lan0 interface on a dedicated VLAN:
>
>     ovs-vsctl add-port phybr0 lan0 lan=702 -- set interface lan0 type=internal
>
> I linked each hypervisor vibr0 to the next one with VXLAN using the lan0
> IP address:
>
> - nebula1 
>
>     ovs-vsctl add-port vibr0 nebula2 -- set interface nebula2 type=vxlan 
> options:remote_ip=@IP_nebula2
>
> - nebula2
>
>     ovs-vsctl add-port vibr0 nebula1 -- set interface nebula1 type=vxlan 
> options:remote_ip=@IP_nebula1
>     ovs-vsctl add-port vibr0 nebula3 -- set interface nebula3 type=vxlan 
> options:remote_ip=@IP_nebula3
>
> - nebula3
>
>     ovs-vsctl add-port vibr0 nebula2 -- set interface nebula1 type=vxlan 
> options:remote_ip=@IP_nebula1

This was a cut&past bug, you should read:

    ovs-vsctl add-port vibr0 nebula2 -- set interface nebula2 type=vxlan 
options:remote_ip=@IP_nebula2

>
>
> The bond0 intefaces has an MTU=9000, I want to increase the lan0 MTU to
> 9000 to avoid the following errors:
>
>     Aug 24 14:34:05 nebula2 kernel: [15615.881948] lan0: dropped over-mtu 
> packet: 1554 > 1500
>
> Is there a solution?
>
> Regards.

-- 
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF

Attachment: signature.asc
Description: PGP signature

_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to