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

Re: [Xen-users] NIC bonding - missing eth0?



On 2/16/2011 3:42 PM, Fajar A. Nugraha wrote:
On Thu, Feb 17, 2011 at 2:47 AM, Smithies, Russell
<Russell.Smithies@xxxxxxxxxxxxxxxx>  wrote:
It’s always eth0 that shows a different aggregator ID. Changing the cables
around so it hits a different port on the switch makes no difference. The
switch is correctly configured for the port channel.

The only difference between the 2 servers is one is running Xen
(kernel-xen-2.6.18-194.32.1.el5.centos.plus) so I have the usual virtual
interfaces and bridges.



Any ideas what might be happening?

Is something that needs to be “fixed” or is it not really a problem?
eth0      Link encap:Ethernet  HWaddr 1C:C1:DE:74:97:5C
peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
The presence of "peth0" shows you still use the default xend's
network-bridge script. Comment it out from /etc/xen/xend-config.sxp,
and create bridges manually on top of your bonding using OS config
files (/etc/sysconfig/network-scripts/ifcfg-br*). There's a recent
example on this list (with vlans on top of bonding) from Donny Brooks,
search the archive if you need it.

If you need help setting this up I may can help. I have it running properly on a few centos 5.5 machines with xen4 currently. I know how frustrating it can be too.

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


 


Rackspace

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