Bonded NICs for Hyper-V Virtual Switch?

[Miscbrah]

Hi all - I've had a Google, but stopped really at the lengthy powershell bits and bobs. Or more accurately, chickened out a bit.

 

Just wondered if anyone had a walkthrough of bonding two NICs together, and presenting these as one connection for the virtual switch to use. One bond for the LACP trunk for serving all the VLANs, the other to bond the two NICs that connect to the SAN. Host OS has a USB ethernet adapter all to itself and four 'regular' NICs onboard.

 

Anyone got anything like that to hand or do I just grow a and get my powershell on?

 

Thanks any and everyone.

Edited June 20, 2016 by Miscbrah

[JordanT91]

I can't remember the exact way but if you go to Server Manager, Local Server then NIC Teaming you can set it all up in there. The NICs then present themselves as a teamed interface that Hyper-V can use. No Powershell required!

[Davit2005]

If you have installed core then I think you enable the remote management then I think you can do it from another server, from memory.

 

That is a lot of thinks

[Miscbrah]

I can't remember the exact way but if you go to Server Manager, Local Server then NIC Teaming you can set it all up in there. The NICs then present themselves as a teamed interface that Hyper-V can use. No Powershell required!

 

Oh that worked a treat! Thanks.

[ITJS2015]

About time Microsoft does something usefull for a change and add in that requirement of NIC Teaming, its a life saver