asked on
Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) teaming issue
Greetings:
We have an IBM System x3500 M2 running Windows Server 2008 R2. It has 2 Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) network adapters with 2 ports each. We'd like to team 2 ports together to give a greater throughput for the machine.
After some research, I found we needed the Broadcom Advanced Control Suite and the Broadcom Advanced Server Program to accomplish this in Windows 2008 R2. I originally found the updated drivers at IBM and Version 3 of the BACS. The drivers worked, but when I went to team, only 1 adapter had the correct NDIS driver for teaming (v6.2). The others were at version 5.1. I could not team.
So I researched again, and found a driver update and the appropriate BACS and BASP packages from Qlogic. I installed them. This updated the drivers to a newer version and BACS to version 4.
The BASP utility is supposed to install/update the appropriate NDIS drivers to make teaming possible. However, after installing the newer drivers and BACS, all the adapters are now at 5.1, and the BACS utility needs at least NDIS v.6 driver to team. I cannot figure out how to update the NDIS driver. The BASP was supposed to do that, but did not. I know the adapters support it, because one of them had the v6.2 driver originally.
I really don't want to spend the $$$ to update to Windows 2012 yet.
Any ideas on how to get the NDIS driver to update in Windows Server 2008 R2 so we can team our NICs?
Thanks!
Jerry Scott
IT Manager
Independent Farmers Bank
admin@farmbank.net
We have an IBM System x3500 M2 running Windows Server 2008 R2. It has 2 Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) network adapters with 2 ports each. We'd like to team 2 ports together to give a greater throughput for the machine.
After some research, I found we needed the Broadcom Advanced Control Suite and the Broadcom Advanced Server Program to accomplish this in Windows 2008 R2. I originally found the updated drivers at IBM and Version 3 of the BACS. The drivers worked, but when I went to team, only 1 adapter had the correct NDIS driver for teaming (v6.2). The others were at version 5.1. I could not team.
So I researched again, and found a driver update and the appropriate BACS and BASP packages from Qlogic. I installed them. This updated the drivers to a newer version and BACS to version 4.
The BASP utility is supposed to install/update the appropriate NDIS drivers to make teaming possible. However, after installing the newer drivers and BACS, all the adapters are now at 5.1, and the BACS utility needs at least NDIS v.6 driver to team. I cannot figure out how to update the NDIS driver. The BASP was supposed to do that, but did not. I know the adapters support it, because one of them had the v6.2 driver originally.
I really don't want to spend the $$$ to update to Windows 2012 yet.
Any ideas on how to get the NDIS driver to update in Windows Server 2008 R2 so we can team our NICs?
Thanks!
Jerry Scott
IT Manager
Independent Farmers Bank
admin@farmbank.net
Windows Server 2008Networking Hardware-Other
Last Comment
Seth Simmons
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
The first set of drivers I found, at IBM, were actually on an iso download for the machine we have. The original drivers were dated 6/2009. The CD drivers were from 8/2009. Unfortunately, though the drivers worked, teaming would not because of the NDIS driver issue. The Broadcom Advance Control Suite client cannot team the NICs without a v.6 or higher NDIS driver. The NDIS driver installed by the CD (and subsequently the newer drivers and BACS v.4) show as v.5.1 in the BACS util.
Not sure what the "cnic" drivers are -- I will research. I realize the v.5 NDIS are out of date: the BACS util let me know that :-) That's why I've been trying to update them to v.6 or v.6.2 (what was originally on the one NIC, but not the others). Guess those drivers are already on the computer; how do I get the adapters to use the newer NDIS drivers and not the v.5.1 drivers? Researching at MS also makes me think the NDIS drivers are manually forced, but I cannot figure out how to do that.
Thanks,
Jerry
Not sure what the "cnic" drivers are -- I will research. I realize the v.5 NDIS are out of date: the BACS util let me know that :-) That's why I've been trying to update them to v.6 or v.6.2 (what was originally on the one NIC, but not the others). Guess those drivers are already on the computer; how do I get the adapters to use the newer NDIS drivers and not the v.5.1 drivers? Researching at MS also makes me think the NDIS drivers are manually forced, but I cannot figure out how to do that.
Thanks,
Jerry
You can upgrade drivers with driver in C:\Windows\INF
ASKER
Ah, let me take a look at that. Thank you.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014710160