Re: [Xen-users] vlans+bonding+bridging

[Maximilian Wilhelm <max@xxxxxxxxxxx>]

Anno domini 2008 Longina Przybyszewska scripsit:

Hi!

> I have to configure Xen server and DomU's which should be able 
> to talk to different vlans - depending on services put on DomU's.

> I would like to enslave 2 NICs via bond interface.
> Both NICs are on trunk ports which are configured in the same way, the 
> same native vlan.

Sounds like Cisco ;)

> I don't know, if  I have to add vlans tagging to eth* interfaces then 
> enslave tagged eth* interfaces to bond interface and then set up a bridge
> or
> fÃrst enslave eth* interfaces to one bond interface  and then add vlan 
> tagging to that bond. Bridges would be set up per vlan.
> What is the real difference between this to approches?

The main difference will most probably be the pain of setup and
maintainance.

I'm using bonding of trunk interfaces on many systems by just bonding
together some eth* interfaces and splitting up the bondX interface
into vlans so that I have bond0.42, bond0.23 and so on.

> Then, I would like to have bridges bound to different vlans - one vlan per 
> bridge, or more vlans per bridge, depending on domU's services.

The next step is to setup a bridge per vlan like
 # brctl addbr br<VLAN_ID>
 # brctl addif br<VLAN_ID> bond0.<VLAN_ID>
so you get br42 and br23 following the above example.

> What about IP addressing - do I have to assign IP addresses to the bridges 
> or to the DomU's?

If the Dom0 (host system) has to use a bridge for it's networking, you
have to assign this IP to the bridge interface.
The IPs of all DomU (guest systetms) have to be set in the DomU
itself, using the standard mechanisms provides by the distribution.

HTH
Ciao
Max
-- 
        Follow the white penguin.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users