Hello all!
It seems that I am unable to use an aggregation as a physical bridge
for a CentOS 5.3 client.
The dom0 is running SXCE 122 and has the following interfaces defined:
r...@glaurung# dladm show-link
LINK CLASS MTU STATE OVER
nge0 phys 1500 up --
nge1 phys 1500 up --
bge0 phys 1500 up --
bge1 phys 1500 up --
public0 aggr 1500 up bge0 nge0
r...@glaurung# dladm show-aggr
LINK POLICY ADDRPOLICY LACPACTIVITY LACPTIMER FLAGS
public0 L4 auto off short -----
The three physical interfaces bge0, nge0, and bge1 are all connected
to the same gigabit ethernet switch.
The domU is running a PVM CentOS 5.3:
r...@cent-01# uname -a
Linux cent-01 2.6.18-128.el5xen #1 SMP Wed Jan 21 11:12:42 EST 2009 x86_64
x86_64 x86_64 GNU/Linux
Initially I defined the bridge for the xVM vnic to be public0:
<interface type='bridge'>
<mac address='00:bb:c0:00:40:01'/>
<source bridge='public0'/>
<script path='/usr/lib/xen/scripts/vif-vnic'/>
</interface>
[Sorry to the forum readers for the broken XML display.]
This seriously confuses the CentOS domU. While booting, it will complain
about a duplicate address:
Sep 22 23:12:01 cent-01 avahi-daemon[1689]: Joining mDNS multicast group on
interface eth0.IPv4 with address 192.168.222.157.
Sep 22 23:12:01 cent-01 avahi-daemon[1689]: Registering new address record
for 192.168.222.157 on eth0.
Sep 22 23:12:02 cent-01 kernel: eth0: duplicate address detected!
When the domU is up, TCP traffic does not work. ICMP is the only thing
that seems to get through. Specifically, NFS is unusable.
So I redefine the domU, having changed the vnic to go across bge1:
<interface type='bridge'>
<mac address='00:bb:c0:00:40:01'/>
<source bridge='bge1/>
<script path='/usr/lib/xen/scripts/vif-vnic'/>
</interface>
And instantly, everything starts working. Using snoop on the dom0,
I see that cent-01 traffic indeed goes across bge1.
Is this an inherent limitation of Solaris aggregations? If so, any
pointer to the documentation of that fact would be appreciated. In
that case, it's strange that only CentOS is affected. WinXP and
OpenSolaris show no problems at all.
Is there a bug in the Linux 'avahi' daemon that might trigger the problem?
Maybe a bug in Solaris? Simply stopping the 'avahi' stuff again does not
solve anything; just moving the bridge to be bge1 does.
Or have I missed some other setting within the CentOS domU?
Thanks -- Volker
--
------------------------------------------------------------------------
Volker A. Brandt Consulting and Support for Sun Solaris
Brandt & Brandt Computer GmbH WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim Email: [email protected]
Handelsregister: Amtsgericht Bonn, HRB 10513 Schuhgröße: 45
Geschäftsführer: Rainer J. H. Brandt und Volker A. Brandt
_______________________________________________
xen-discuss mailing list
[email protected]
