Ok, after further research, poring over the manuals and doing extensive google searches, my conclusion is that there is no way to specifically link internal ports to external ports other than using VLAN's.
My actual interest is in aggregating ports.
It seems possible to aggregate external ports to an external switch, but is it possible to aggregate the internal port group for a blade to the blade? The LAG options appear to be available for the internal ports.
I've installed Windows server on a blade and used Windows (switch independant) NIC Teaming to create a 4 NIC team (which reports a single 4Gbps team adapter) (Which I have then used to create a Hyper V virtual switch). That's all good and well but it doesn't really give 4Gbps.
Is it advisable to create a LACP LAG in Windows Server to interface to an internal port LAG?
Spyne13
2 Posts
0
November 27th, 2019 19:00
Ok, after further research, poring over the manuals and doing extensive google searches, my conclusion is that there is no way to specifically link internal ports to external ports other than using VLAN's.
My actual interest is in aggregating ports.
It seems possible to aggregate external ports to an external switch, but is it possible to aggregate the internal port group for a blade to the blade? The LAG options appear to be available for the internal ports.
I've installed Windows server on a blade and used Windows (switch independant) NIC Teaming to create a 4 NIC team (which reports a single 4Gbps team adapter) (Which I have then used to create a Hyper V virtual switch). That's all good and well but it doesn't really give 4Gbps.
Is it advisable to create a LACP LAG in Windows Server to interface to an internal port LAG?