Windows Server 2012R2 NIC Teaming - big problem

%3CLINGO-SUB%20id%3D%22lingo-sub-1848616%22%20slang%3D%22en-US%22%3EWindows%20Server%202012R2%20NIC%20Teaming%20-%20big%20problem%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1848616%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI%20am%20in%20the%20process%20of%20building%20a%20new%20physical%20backup%20server%2C%20and%20I%20would%20like%20to%20team%20the%20NIC's%20in%20order%20to%20double%20the%20throughput.%20I%20have%20attempted%20to%20configure%202x%20NIC%20teams%20with%202x%20physical%20NIC's%20in%20each.%20Team%201%20will%20be%20for%20the%20LAN%20access%20for%20accessing%20the%20VM's%20to%20backup%2C%20and%20Team%202%20will%20be%20for%20the%20iSCSI%20network%2C%20in%20order%20to%20attach%20the%20backup%20storage%20directly.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20set%20the%20teams%20up%20as%20LACP%2C%20and%20then%20configured%20the%20connected%20switch%20with%20LACP%20port%20channels%20using%20a%20Cisco%20Catalyst%209300%20switch%20on%20the%20connected%20ports.%20This%20all%20seemed%20to%20work%20fine%20initially%2C%20and%20network%20performance%20looked%20good%20on%20both%20NIC%20teams.%20I%20was%20able%20to%20connect%20the%20iSCSI%20volumes%20and%20the%20local%20LAN%20was%20working%20properly%2C%20so%20everything%20looked%20to%20be%20working.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20was%20until%20I%20rebooted.%20After%20a%20reboot%2C%20both%20the%20iSCSI%20and%20the%20LAN%20died.%20The%20only%20way%20I%20could%20recover%20it%20was%20to%20either%20shut%2Fno%20shut%20the%20port%20channel%2C%20or%20disable%2Fre-enable%20the%20NIC%20team%2C%20or%20simply%20change%20the%20IPv4%20address%20around.%20It%20simply%20will%20not%20recover%20from%20a%20reboot.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20to%20add%20more%20issues%2C%20the%20connected%20iSCSI%20targets%20became%20corrupted%2C%20and%20I%20had%20to%20recover%20the%20backup%20targets%20on%20another%20server%20(VM)%20using%20chkdsk%20%2Ff.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20noticed%20that%20when%20I%20disabled%20the%20iSCSI%20NIC%20team%20after%20one%20reboot%2C%20the%20LAN%20NIC%20team%20came%20up%20all%20by%20itself%20without%20any%20reconfiguration.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20question%20is%20-%20am%20I%20doing%20this%20right%3F%20I've%20read%20that%20iSCSI%20is%20supported%20and%20I%20cant%20seem%20to%20find%20any%20issues%20on%20behaviour%20like%20this%20being%20normal%20in%20Server%202012%20R2.%20I'm%20putting%20it%20down%20to%20some%20kind%20of%20bug%20at%20the%20moment%2C%20but%20it%20might%20be%20the%20way%20I've%20set%20it%20up.%20Is%20an%20LACP%20port%20channel%20the%20way%20to%20go%20here%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1848616%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eserver%202012%20r2%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Visitor

Hi,

I am in the process of building a new physical backup server, and I would like to team the NIC's in order to double the throughput. I have attempted to configure 2x NIC teams with 2x physical NIC's in each. Team 1 will be for the LAN access for accessing the VM's to backup, and Team 2 will be for the iSCSI network, in order to attach the backup storage directly.

 

I set the teams up as LACP, and then configured the connected switch with LACP port channels using a Cisco Catalyst 9300 switch on the connected ports. This all seemed to work fine initially, and network performance looked good on both NIC teams. I was able to connect the iSCSI volumes and the local LAN was working properly, so everything looked to be working.

 

That was until I rebooted. After a reboot, both the iSCSI and the LAN died. The only way I could recover it was to either shut/no shut the port channel, or disable/re-enable the NIC team, or simply change the IPv4 address around. It simply will not recover from a reboot.

 

Then to add more issues, the connected iSCSI targets became corrupted, and I had to recover the backup targets on another server (VM) using chkdsk /f.

 

I noticed that when I disabled the iSCSI NIC team after one reboot, the LAN NIC team came up all by itself without any reconfiguration.

 

My question is - am I doing this right? I've read that iSCSI is supported and I cant seem to find any issues on behaviour like this being normal in Server 2012 R2. I'm putting it down to some kind of bug at the moment, but it might be the way I've set it up. Is an LACP port channel the way to go here?

 

Thanks :)

0 Replies