problem with the module bnx2

[Anibal Capotorto]

I¹ve run into a lot of stress when using the bnx2 cards with rhel4u4 /u5 on
the HPs.


Basically 3 things that are a problem with this nics.

1st the problem you¹re talking about I think it¹s definitely because of the
topology of the network given that the bnx2 family sometimes takes some time
in bringing the link up which will lead into
The ks process timing out and asking you to enter the ip manually.

With the HPs I¹ve had 2 problems, 1st one the nics weren¹t detected @ boot
time, the pxe was doing fine, but the OS wasn¹t able to bring up the nics
This one was fixed disabled the apci=off to on (or vice versa, I can¹t
really remember well that one, but it¹s definitely something to do with
that.

THEN when the boxes were installed ok, the problem was that if I wanted to
do a /etc/init.d/network restart the nic died and won¹t come back until the
next reboot

The error in the restart was something related to ³ chipset failed to reset
³ 

This was due to the complicated nature of the board itself being HP and
supporting iSCSI, the only solution was to replace the nics

This were PCI-E nics, the onboard ones worked fine with the apci=off thing..


Hope this helps


On 28/04/2008 09:43, "Gerrard Geldenhuis" <Gerrard.Geldenhuis at datacash.com>
wrote:

> Hi
> 
>> > -----Original Message-----
>> > From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-
>> > bounces at redhat.com] On Behalf Of Wilson Felipe
>> > Sent: 25 April 2008 16:28
>> > To: kickstart-list at redhat.com
>> > Subject: problem with the module bnx2
>> >
>> > hello,
>> >
>> > We are starting to install redhat 5.1 and centos 5.1 in our
>> > environment, and it all went well until we tried with Dell machines
>> > (PE1950 and 860), which have network cards using bnx2 (using MSI). The
>> > problem is at the bnx2 module, we found out 2 way:
>> >
>> > - using dhcp at pxe and at the boot:
>> > the kernel and the initrd loads from pxe boot, and stops at
>> > downloading the ks file, though it gets the ip from the dhcp, but the
>> > network link is never put up, but in messages it prints "the link
>> > becomes ready"
>> >
>> > - using dhcp at pxe, and static ip at the boot
>> > the kernel and the initrd loads from pxe boot, and also stops at
>> > download the ks file, but after a few seconds, the links becomes ready
>> > and we can get the ks file and the installation goes all well
>> >
>> > has anyone seen this behavior using bnx2?
>> >
> 
> We use HP machines with bnx2(broadcom) and e1000(intel) nics and we have
> not seen the same behaviour. Could it be switch related?
> 
> Regards
> 
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
> 
> 
> -- 
> Anibal Capotorto Sr. Linux Engineer - travelocity global
> mob: +44 078 12960970
> 24x7 Tech-SOC number:- +44 (0)20 7866 4500
> acapotorto at lastminute.com <mailto:acapotorto at lastminute.com>
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/kickstart-list/attachments/20080428/8665afe6/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.gif
Type: image/gif
Size: 3284 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/kickstart-list/attachments/20080428/8665afe6/attachment.gif>