Hi,
On a DL380 G8 Server with 2 HP T361 dualport NIC's the vSwitch is not created when Hyper-V Role is installed.
Eventlog shows Event 33204:
Hyper-V-Setup: Es konnte kein virtueller Ethernet-Switch erstellt und an den Adapter "Microsoft Network Adapter Multiplexor Driver #2" gebunden werden: Der Parameter ist ungültig. (0x80041008)
(sorry, only in german)
What I did before I installed the Hyper-V Role:
Updated System-ROM and drivers to the latest / recommended Versions as seen in windowsservercatalog.com
I've got 4 ports on this two T361 NIC's. Each NIC's ports are connected to two different switches.
I figured out which Ethernet Adapter in the OS (Ethernet, Ethernet#2, Ethernet#3, Ethernet#4) belongs to which physical Ports on the NIC's and renamed the Ports in the following manner: NIC1_P1, NIC1_P2, NIC2_P1, NIC2_P2.
With LBFOADMIN I teamed the ports:
Name : Team1
Members : {NIC2_P1, NIC1_P1}
TeamNics : Team1
TeamingMode : SwitchIndependent
LoadBalancingAlgorithm : HyperVPort
Name : Team2
Members : {NIC1_P2, NIC2_P2}
TeamNics : Team2
TeamingMode : SwitchIndependent
LoadBalancingAlgorithm : TransportPorts
So far so good.
When installing Hyper-V Role, I selected Team2 for the vSwitch. After System Reboot, the naming of the Ethernet Adapters is gone (now: Ethernet#2, Ethernet#3, Ethernet#4, Ethernet#5)
Furthermore, both Teams are no longer visible in Network Center. In LBFOADMIN, I can see both teams are present, but with Status "down". When trying to access the properties of a team, LBFOADMIN crashes.
In PS with Get-NetLBLFOTeam I see the above configuration with the old Adapter Names:
Name : Team1
Members : {NIC2_P1, NIC1_P1}
TeamNics : Team1
TeamingMode : SwitchIndependent
LoadBalancingAlgorithm : HyperVPort
Status: Down
Name : Team2
Members : {NIC1_P2, NIC2_P2}
TeamNics : Team2
TeamingMode : SwitchIndependent
LoadBalancingAlgorithm : TransportPorts
Status: Down
Question: Is there a limitation with NIC Teaming when installing Hyper-V Role / creating a vSwitch?
Any thoughts on this?
Regards,
Markus