Connectivity MS Server 2012 and LACP

jfish · Feb 13, 2014

Anyone an expert on MS Server 2012 (not R2)

Got a off problem and it has effected 3 servers so far.

The HP Servers ASR (Automatic Server Reboot) kicks in and restarts the server but that's not the problem. The problem is the server network does not kick in. The NIC's are configured as a team with LACP and Address Hashing.

The only fix is the network guy has to disable and enable the port on the switch where the NICs are plugged into to kick start network.

The network guy is saying its a Server 2012 issue, but I am convinced the issue is with the Cisco Switch configuration (You know how these network guys are so protective of there network)

Anyone come across this issue, or know what could cause it.

RedFirecracker · Feb 13, 2014

Have a read of this;

A Networker's Log File: Server NIC Teaming with Cisco Nexus

particularly the last bit on BACS.

Cisco LACP can be a bit 'interesting' at times. We run LACP links to our HP core network switches from Dell (I believe) Windows servers without this sort of issue. From a network config on the HP point of view, once the ports are teamed, it is just the Vlan config that can cause issues.

Does bouncing the network on the server give the same result of a restored connection? Unfortunately, there doesn't seem to be a 100% fix for a lot of people, changing the BACS Team type to 'generic' works most of the time, but not for all reboots.

jfish · Feb 13, 2014

RedFirecracker said:
Have a read of this;

A Networker's Log File: Server NIC Teaming with Cisco Nexus

particularly the last bit on BACS.

Cisco LACP can be a bit 'interesting' at times. We run LACP links to our HP core network switches from Dell (I believe) Windows servers without this sort of issue. From a network config on the HP point of view, once the ports are teamed, it is just the Vlan config that can cause issues.

Does bouncing the network on the server give the same result of a restored connection? Unfortunately, there doesn't seem to be a 100% fix for a lot of people, changing the BACS Team type to 'generic' works most of the time, but not for all reboots.

The NIC's are Broadcom and we have used Native 2012 Teaming setup - as recommended.

As servers are live servers we can't do a controlled test of this, so trying to get this done on a weekend but got to have network guy available incase network doesnt come up and he needs to do his bit.

Connectivity MS Server 2012 and LACP

jfish

VIP Member

RedFirecracker

Inactive User

jfish

VIP Member

Similar threads

We value your privacy