Windows Server 2008 problems with Broadcom/802.3ad/VLANs

Hi All,

We've recently started testing the Windows Server 2008 platform and all was
going well, until we tried to configure the NICs. The server platforms are
IBM x336s and we are running the standard edition of Windows Server 2008
(x64). The Broadcom drivers and BACS tool are from their latest CD -
"Broadcom v11.0b.4a Drivers Software CD"; this installs the following....

Windows Server 2008 x64 Driver 10.82.0.0a*
BASP Windows Server 2008 x64 1.1.0*

Note: An asterisk (*) following a version number represents a certified
driver.

Both ethernet ports on the server are connected to a switch stack comprising
of Cisco 3750G switch, with an EtherChannel setup for this server and
configured for LACP (802.3ad).

Configuring the team does not present any problems and both the server, via
Broadcom's configuration tools, and the switch confirm that the team is
configured and operating correctly.

The 1st VLAN was then added, and again, this was successful with both the
server and switch confirming the VLAN was up; we were able to configure a
static IP address and successfully ping the default gateway on the network.
The only anomaly obeservered at this point is that in the 'Network
Connections' window the adapter name was 'SVR-W2K8S-01-TEAM1/VLAN-200',
whilst in other parts of the OS like 'Task Manager' and the output of the
command line tool 'ipconfig', the adapter was named 'Local Area Connection 3'.

We then proceeded to add the three other VLANs required for our
configuration, which is the point at which we started to run into problems.
Firstly, the VLAN that we configured above disappeared from the 'Network
Connections' window, although it still showed in the BACS configuration tool
- however, the VLAN was now shown as unavailable. Rebooting the server caused
the VLAN to reappear in the 'Network Connections' window, but was displaying
'Network Cable Unplugged'. The three new VLANs we created all appeared to be
available and online, but interestingly these also displayed with the same
name 'Local Area Connection 3' in all parts of the OS other than the 'Network
Connections' window. It was possible to configure these VLANs and ping the
default gateways on their respective networks, but the configuration had to
be entered multiple times as it wouldn't always save and it was also noted
that editing the configuration of other virtual adapters caused configuration
settings to be lost in others.

This is a replica of our production environments in terms of server
hardware, switches, switch and network configuration - with the sole aim of
validating and proving the Windows Server 2008 platform which we are looking
to deploy and take advantage of.

The latest updates available from Microsoft via Windows Update were applied
today and this, as far as I can tell, is the most recent driver suite
available from Broadcom. If anyone has any similiar experiences or useful
pointers to assist in troubleshooting this issue, it would be greatly
appreciated.

--
Thanks in advance,

James Mercer.
JXD Consulting Ltd.

Hello James,

I too am having this issue!!! I thought I was losing it or just plain
configuring the switches wrong. We have IBM HS20 Blades and had to configure
a server with 3 VLANs using the BASP tools. Now the server can communicate
over all three VLANs just fine but I can only get two to work at a time (at
most). The NIC Teaming and VLAN functions are just broken between this
software and Server 2008.If you do find a solution, please feel free to share.

I contacted IBM and after finally wading through the support entitlement
gauntlet, I discussed this issue with a tech rep. The solution for me was to
use the Broadcom BASP suite for the NetExtreme II NIC. Apparently the
software will work with the older card just fine and offers newer code which
dows in fact correct this issue. My HS20 8678 Blade can now properly work
with multiple VLANs using the Teaming features of the suite. I was told that
the version that is on the site was not tested with the older server hardware
and you and I were the first ones to bring this issue to light. Hopefully
this works for you.

Hi,

Firstly thanks for your posts and sorry for the delay in following up on
this one. I managed to make some progress, albeit slowly with Broadcom
directly and ended up with a set drivers from them comprising the following...

BASP - v1.1.4
NIC - v10.10.0.0
BACS - v11.3.13.0

....this seemed to resolve the issue and have proved stable in our testing to
date. IBM have just released an update
(http://www.ibm.com/systems/support/s...andind=5000008
- ignore the wrong version on the page title!) on their support site, which I
am now in the process of testing and contains the following....

BASP - v1.1.4
NIC - v10.100.0.0
BACS - v11.3.13.0

..... so only a newer version of the NIC driver, relative to the what was
supplied to me by Broadcom a little while ago. It appears that there is still
a problem with the virtual LAN interface names, as in task manager they are
all still appearing as "Local Area Connection 3" rather than the name
assigned to the connection, e.g. VLAN101, VLAN709, etc, etc.
Do you see this with the version of drivers you are currently running?

--
Thanks in advance,

[BlargMaN]

Hello James...

I am trying to attempt the exact same setup, only I am still using Server 2k3 Ent.

Can you please help me by providing the config you used for your switches, as I would really like to get this working.

Thanks,

Jeff Phelps

Hi Jeff,

What type of switches are you using, our typical data centres are
predominantly Cisco based? Windows 2003 running on the IBM xSeries hardware
has been working extremely well and reliably for us in this scenario, so
hopefully we can get you a working configuration.

Regards, James.

[BlargMaN]

I am using Dell Servers with BroadCom NetXtreme II NICs, and I am using Cisco 3570Gs Stacked.

What I am trying to accomplish is to get one of my servers (RADIUS Server) to be on two VLANs. I have my main corporate VLAN 100, and then I have a separate VLAN 150 for my Guest Wireless access.

I believe I have the Server setup correctly; Taggin both Virtual Interfaces with the appropriate VLAN. I also need to get my Cisco switches setup properly to accept the data from the server, and route it to the appropriate place.

I hope what I have explained is enough to help you help me.

Just wanted to let you know, that I was able to get the issue resolved, and everything is now working for me.

[sarfrazali]

Hello All,
My Name is Sarfraz
i have a question regarding vLans...
i actually have some vlans on Juniper Switches 4200 series, all are working fine but the user who is in vlan 1 can't see vlan 2 computers or any other vlans computers, i have single domain on Windows Server 2008 Ent.. & just one site...i also added other vlans subneting & linked them to my default Site..
but still i 'm unable to see other vlans...

Example: i have vlans (V1)10.111.15.X & (V2)10.111.16.X. & (V3) 10.111.17.X.

kindly help if someone can.

Regards
Sarfraz

You cannot create VLANs in a Layer2 Switch and expect them to comunicate.
The Switch must be Layer3 and be operating as a LAN Router. The L3 Switch
is generally the only switch that even has the VLANs,...all the other L2
Switches simply function based on the physical cable they are attached to
and they have no VLAN config at all in anyway.


ADS&S has nothing to do with this context at all. That is relevant to AD
Replication over slow links and has nothing to with networking itself.

[sarfrazali]

Dear Phillip..
i appreciate the concerning of Layer-3 switches,however'
my question was to see all vlans workstation from any vlan..(accurate formating of Sub-netting with) Active Directory Sites & Services... BTW my switches are layer 3 & even having advanced options like advanced routing.etc..& as i cleared in my question that all vlans are communicatin' smoothly without any trouble & all workstations are part of my domain..

awaiting the helpful reply
Regards
Sarfraz

[sarfrazali]

thanks a lot dear Philip,
i think i couldnt explain currectly,
i just want to see all other domain computers in my network places..

please help man...

That uses the Computer Browser components that are Netbios, and hence,
Broadcast Dependent. To get it to function accross subnets will require
using WINS. I run two WINS Servers here that are Push/Pull Partners of each
other.

But I would never expect all machines to show up consistantly. I have been
where I am for 10 years and I do everything I need to do to get the machines
to do that and still I never see "all" the active machines whenever I open
Network Places.

I always use ADUC to find the machine names of the machine I want (adding a
Description to them helps). Then I just go the the Run line and type
\\machinename.

As far as regular users,...they just never "browse" to machines all over
anyway,...and you should not allow that practice to start. Ours have one
File Server that they have to get to and I have simply put a shortcut to
that Fileserver on the Desktop of the "All Users" profile on each machine.
so they just use it