I''m configuring Xen on a blade in an Intel SBCE. Currently I''m using Fedora Core 6 with all patches installed and the Xen 3.0.3 RPMs that are part of that distribution, in the default configuration. When xend is started it appears that the network bridging breaks something such that although I can see ARP traffic (possibly all broadcast traffic?) arriving, no ICMP/TCP/UDP packets appear to reach the machine. Running /etc/xen/scripts/network-bridge stop returns things to normal. Reading around it looks like some people have ascribed this problem to a problem with the Broadcom NICs used on the blades, but I''ve upgraded the firmware to 1.9.6 (the latest I can find) with no obvious change in behaviour. I have a very similar configuration (FC6/same kernel/same xen RPMs/same default configuration) running ok on a different box, so I don''t believe I''ve got anything too seriously wrong software-wise. Any ideas on why might be wrong and/or how to fix it? Obviously I could change to a routed network connection, but I''d very much prefer the bridged option if at all possible. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Feb 21, 2007 at 05:18:51PM +0000, James Fidell wrote:> I''m configuring Xen on a blade in an Intel SBCE. Currently I''m using > Fedora Core 6 with all patches installed and the Xen 3.0.3 RPMs that are > part of that distribution, in the default configuration. > > When xend is started it appears that the network bridging breaks > something such that although I can see ARP traffic (possibly all > broadcast traffic?) arriving, no ICMP/TCP/UDP packets appear to > reach the machine. Running > > /etc/xen/scripts/network-bridge stop > > returns things to normal. > > Reading around it looks like some people have ascribed this problem to > a problem with the Broadcom NICs used on the blades, but I''ve upgraded > the firmware to 1.9.6 (the latest I can find) with no obvious change in > behaviour. > > I have a very similar configuration (FC6/same kernel/same xen RPMs/same > default configuration) running ok on a different box, so I don''t believe > I''ve got anything too seriously wrong software-wise. > > Any ideas on why might be wrong and/or how to fix it? Obviously I could > change to a routed network connection, but I''d very much prefer the > bridged option if at all possible. > > JamesI fixed this problem with IBM HS20 blades by upgrading the broadcom NIC firmware. You can check IBM support site for version information.. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pasi Kärkkäinen wrote:> I fixed this problem with IBM HS20 blades by upgrading the broadcom NIC > firmware. You can check IBM support site for version information..As far as I can tell, the one blade I''ve upgraded is now running the latest firmware, though I don''t know how to confirm that. Is there any way to check that you know of? The Intel driver update requires a DOS boot floppy which isn''t too simple when the unit is 200 miles away. At least IBM distribute one that runs under Linux (though it doesn''t want to work for me). Is restarting the network interfaces all that''s required to use the new firmware? James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Itamar Reis Peixoto
2007-Feb-21 20:13 UTC
Re: [Xen-users] Possible Broadcom-related problem?
ask someone to upgrade for you. -------------------- Itamar Reis Peixoto e-mail: itamar@ispbrasil.com.br msn: itamarjp@starmedia.com skype: itamarjp icq: 81053601 +55 34 3238 3845 +55 11 4063 5033 ----- Original Message ----- From: "James Fidell" <james@cloud9.co.uk> To: "Pasi Kärkkäinen" <pasik@iki.fi> Cc: <xen-users@lists.xensource.com> Sent: Wednesday, February 21, 2007 6:05 PM Subject: Re: [Xen-users] Possible Broadcom-related problem?> Pasi Kärkkäinen wrote: > >> I fixed this problem with IBM HS20 blades by upgrading the broadcom NIC >> firmware. You can check IBM support site for version information.. > > As far as I can tell, the one blade I''ve upgraded is now running the > latest firmware, though I don''t know how to confirm that. Is there > any way to check that you know of? The Intel driver update requires a > DOS boot floppy which isn''t too simple when the unit is 200 miles away. > At least IBM distribute one that runs under Linux (though it doesn''t > want to work for me). Is restarting the network interfaces all that''s > required to use the new firmware? > > James > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Fidell wrote:> I''m configuring Xen on a blade in an Intel SBCE. Currently I''m using > Fedora Core 6 with all patches installed and the Xen 3.0.3 RPMs that are > part of that distribution, in the default configuration. > > When xend is started it appears that the network bridging breaks > something such that although I can see ARP traffic (possibly all > broadcast traffic?) arriving, no ICMP/TCP/UDP packets appear to > reach the machine. Running > > /etc/xen/scripts/network-bridge stop > > returns things to normal. > > Reading around it looks like some people have ascribed this problem to > a problem with the Broadcom NICs used on the blades, but I''ve upgraded > the firmware to 1.9.6 (the latest I can find) with no obvious change in > behaviour. > > I have a very similar configuration (FC6/same kernel/same xen RPMs/same > default configuration) running ok on a different box, so I don''t believe > I''ve got anything too seriously wrong software-wise. > > Any ideas on why might be wrong and/or how to fix it? Obviously I could > change to a routed network connection, but I''d very much prefer the > bridged option if at all possible.For the record, in case it''s useful to someone else: I''ve spent a fair bit more time on this now, and tried both the latest intel NIC firmware update (v1.9.3) and the latest IBM update (v1.9.6). Neither one, by itself, fixes the problem. The intel update is part of a package of firmware updates, but I have only applied the NIC update. I also discovered this: http://thread.gmane.org/gmane.linux.hardware.dell.poweredge/23270/focus=23276 Running the uxdiag commands given in that posting after the upgrade and rebooting does fix the problem, in that I can now start xend without the bridged network killing connectivity. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Here are more details related to this topic... I had the same problem on Dell PowerEdge 1950 Servers with two integrated Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet NICs. The "solution" was to deactivate the IPMI management feature. To deactivate IPMI on first NIC use this: uxdiag -c 1 -mfw 0 -t abcd To deactivate IPMI on second NIC use this: uxdiag -c 2 -mfw 0 -t abcd Note that ''-t abcd'' is not related to IPMI but it will skip those long-and-boring tests of uxdiag. A good idea is to deactivate IPMI only for the interface used by Xen and to keep IPMI activated on the management interface. A better idea is to have a look at uxdiag -help :) I''ve made a nice MS-DOS 6.22 *bootable* ISO with DOS-based utilities for the Broadcom NetXtreme II (\Broadcom\Userdiag\uxdiag.exe) Of course I have to mention those blablabla things like: "use it at your own risk"... http://xen.ro/dellpe1950.iso OR Read this http://mywiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround Xen community rulz!> I''m configuring Xen on a blade in an Intel SBCE. Currently I''m using > Fedora Core 6 with all patches installed and the Xen 3.0.3 RPMs that are > part of that distribution, in the default configuration. > > When xend is started it appears that the network bridging breaks > something such that although I can see ARP traffic (possibly all > broadcast traffic?) arriving, no ICMP/TCP/UDP packets appear to > reach the machine. Running > > /etc/xen/scripts/network-bridge stop > > returns things to normal. > > Reading around it looks like some people have ascribed this problem to > a problem with the Broadcom NICs used on the blades, but I''ve upgraded > the firmware to 1.9.6 (the latest I can find) with no obvious change in > behaviour. > > I have a very similar configuration (FC6/same kernel/same xen RPMs/same > default configuration) running ok on a different box, so I don''t believe > I''ve got anything too seriously wrong software-wise. > > Any ideas on why might be wrong and/or how to fix it? Obviously I could > change to a routed network connection, but I''d very much prefer the > bridged option if at all possible. > > James > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Sergiu Strat, HQN - High Quality Networks www.hqn.ro _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users