[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] quick question about bonding with vlans and Xen

On 6/16/2010 8:39 PM, Fajar A. Nugraha wrote:
On Wed, Jun 16, 2010 at 10:14 PM, Donny Brooks<dbrooks@xxxxxxxxxxxxxxxx>  wrote:
And I just THOUGHT I had it working. It seems that no machine on the same
vlan as my domu can connect to it unless the domu first pings the machine
trying to connect to it. That and the domu has about 80% packet loss! It has
to be something I am missing.
Centos 5.5 x86_64
Xen 4.0 from gitco repo
So Xen 4.0 can work with Centos kernel-xen now? Good to know. It
didn't work the last time I tried.

Let me clarify this: Anything NOT on the same vlan has no issues getting to
the domu. I have tried various domu's on various vlans and all exhibit the
same behavior. Anything outside the vlan of the domu can connect to it.
While anything on the same vlan cannot connect to it unless the domu first
pings the machine in question. Even with that it has about 80% packet loss.

Is anyone else doing a balance-alb style bond0 with various vlans passing
over it and having success?
I'd start by troubleshooting the problems one by one.
First of all, the switch side. You MIGHT need spanning-tree portfast there.

Second, bonding mode. You might want to try with simpler modes first
(0,1, or 2), and then simulate links failure (possibly by disabling
the port on switch side) to make sure that at least the basic failover
stuff and switch config is working properly.

If all fails, you might need to actually do 802.3ad.

I have to be missing something simple. It usually happens that way. I have tried the "spanning-tree portfast trunk" to no avail. Also I tried mode 0,1,2,4, and 6 with the various configs to no avail. All exhibit the same behavior where anything outside the domu's vlan can access it no problem but nothing on the same vlan can.

With all I have tried, I am giving up on the whole "bonding w/ vlans" for now. But I would like to at least take advantage of the vlan support so I can at least test that. Shouldn't I be able to do the following to enable vlan support?:

remove bond0 interface
setup eth1 as vlan master
change any reference to bond0 in the bond0.XX and brXX files to eth1
restart networking
and hopefully it just work?

Currently I have gone back to the xen bridge-script way of doing things just to get them working. After much deliberation I have decided it is probably best that I only do vlans since my other machines I plan to setup as dom0's only have 2 network cards and I plan to keep one of them as a dedicated management interface.

Donny B.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.