Unsolved
1 Rookie
•
9 Posts
0
688
February 14th, 2023 08:00
Broadcom Team BASP Interface not in Windows Network Connections
Maybe I'm misunderstanding things. I'm looking to have NIC redundancy in networking for a Windows Server 2019 not running HyperV.
The best that I've found to help me is this Dell doc, https://www.dell.com/support/kbdoc/en-us/000105133/how-to-set-up-nic-teaming-on-windows-server-using-broadcom-advanced-control-suite-4.
Aside from where to configure an IPv4 address, the document was pretty straight forward.
In Windows control panel, Network Connections there is no new NIC with a name like "Team1" (what I allowed it to be named) nor is there a NIC named BASP anything. There are no new adapters in Windows control panel, Network Connections, for me to give an IP address. I have tried creating a team without a VLAN (I have no plans to trunk), but I've also added a VLan, 1, which that VLAN was configured untagged (again, no trunking planned, the team is for redundancy)
Broadcom Team BASP Interface is not appearing in Windows Server 2019 Network Connections in order for me to put at IP address on a teamed Interface.
Where do I put the IP address on a Broadcom Team?
Below is the sum of the PO on a Cisco switch.
0#show etherchannel 128 sum
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
M - not in use, minimum links not met
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
A - formed by Auto LAG
Number of channel-groups in use: 2
Number of aggregators: 2
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
128 Po128(SU) LACP Gi2/0/47(P) Gi2/0/48(P)
Which each phy interface is configured with this. channel-group 128 mode active
DELL-Chris H
Moderator
•
9.4K Posts
0
February 14th, 2023 13:00
Boban15,
While normally we don't assist in initial configuration, what I would suggest you start with is updating the server and nic to current, to minimize any variables.
Also, would you confirm the server model you are working on, as that will help clarify the path forward.
Lastly, are you able to see Broadcom Advanced Control Suite, i believe on the desktop, after installation, if not was it selected as described on the page you linked?
Let me know what you see.
boban15
1 Rookie
•
9 Posts
0
February 15th, 2023 10:00
Geez, I don't know exactly how I came to document 000105133, but it is apparently not appropriate for a modern Windows Server OS. However, the document didn't exclude some versions of Windows Server and the document properties seemed to indicate it still was current and may have applied to me based on the words in those properties;
"Affected Product
Servers, Broadcom NetXtreme Family of Adapters
Last Published Date
16 Sep 2021"
Also, for some reason, my Dell R650xs servers came *pre-installed* with Broadcom's Advanced Control Suite 4. Also, while using it, building teams, removing teams, rebuilding teams (so often because no NIC showed up the OS Network Control Panel to configure with an IP address), it would BSOD with ndis.sys involved. So many BSOD across two r650xs servers using BACS.
I sure wish document 000105133 would have had a disclaimer at the top with language like, "discouraged for use with Windows Server 2012 and later," or something to that effect. I spent so much time working on servers using the pre-installed tool Broadcom Advanced Control Suite 4, which caused BSOD. and now on one of the servers one of the NICs which I was working with wasn't even the MS Server Manager teaming configuration as described in this document, <ADMIN NOTE: Broken link has been removed from this post by Dell>. No amount of disable/enable of the phy interface in control panel and no amount of reboots has allowed that NIC to appear as an available teaming NIC in Server Manager Teaming configuration window. So now I have a boogered up Windows OS.