On Tue, Aug 18, 2009 at 3:38 AM, Adam Wead<awead@xxxxxxxxxxx> wrote:
> Thanks, Dustin.
> I used your script and it seems to work... I couldn't get my setup to work
> with the alias that's off of the bond devices, but it works when I used the
> bond device directly.
Glad to hear it. So all is working for you now?
>> > > And I tried duplicating this, mind you, without the patched ifup
>> > > script and setup something like this:
>> > >
>> > > - (eth1 + eth2) = bond0 with mode 2
>> > > - create VLAN bond0.2 to bond0
>> > > - attach bridge xenbr0 to bond0.2
>> > > - modified xend-config file: (vif-script 'vif-bridge bridge=xenbr0')
>> > >
>> > > This appears to work, but when I create guests and attach them to the
>> > > xenbr0, no dice. My question is, is the above correct and where to
>> > > the IPs go? Dom0 has it's own IP address, but what interface/bond/
>> > > VLAN does that go under? Should the other items have IPs as well?
I usually say "when using bridged setup, treat dom0 like a L2 or L3
switch. Get help from your networking guys if you're not familiar with
vlans and switches". So if your dom0 IP is also located on vlan2, then
you need to put the ip address on xenbr0 (or whatever bridge bond0.2
is located). This is similar to L3 switch setup.
For other vlans, if you don't need dom0 to have logical access to it,
you don't need to put IP address on the bridge. It can be up with no
IP address on dom0. This is similar to L2 switch setup.
On my implementations I usually use a separate interface for dom0
management IP, with bonding/vlan/bridges on other interfaces similar
to L2 switch setup.
Xen-users mailing list