I was reading various posts about subject and got pretty much confused by now.
Could somebody clear few questions for me, please?
General configuration:
Physical switch port is configured forstatic VLAN (i.e.
no any dynamic VLAN port assignments) and carries multiple VLAN IDs - 802.1Q trunk
Configuration without Hyper-V
--------------------------------
A0.
One physical NIC (pNIC) (Intel/Broadcom)
For each VLAN ID a virtual NIC (vNIC) is created and bound to thepNIC
B0.
Two or more pNICs (Intel/Broadcom)
A team is created (802.3ad)
For each VLAN ID a vNIC is created and bound to theteam.
With Hyper-V installed:
--------------------------------
A1:
pNIC is bound to vSwitch.
Parent partition vNIC can be bound to one VLAN ID only from GUI
Parent partition vNIC (multi vNIC - mvNIC) can be bound to multiple VLAN ID using WMI?
And then what? I need to create few VNICs bound to the mvNIC, one per each VLAN ID, right?
http://blogs.msdn.com/virtual_pc_guy/archive/2008/03/10/vlan-settings-and-hyper-v.aspx
It is also possible to configure a virtual network adapter so that it can receive network traffic from multiple VLANs, however this is not exposed through the user interface
and you need to make such a configuration using the WMI interfaces.
B1.
Two or more physicals NIC (pNIC) (Intel/Broadcom)
One team is created (802.3ad)
I would think the process is the same as A1, except vSwitch is bound to the team, but it’s not:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01663264/c01663264.pdf
According to HP (100% trusted source ;-)
I will need to do:
For each VLAN ID a vNIC is created and bound to the team.
Bind vSwitch to each vNIC, and get vvNIC (virtual virtual NIC ;-) on parent.
Could somebody explain, please:
1. Why it’s not possible to bind to vSwitch to team?
2. How to present more than one VLAN to parent partition?
3. HP article said: install Hyper-V first, than install teaming – it won’t work otherwise.
Why it is so important?
Cluster
--------------------------------
On Hyper-V host all I need is a management VLAN and quick/live migration VLANs.
The later are on separate NICs and not connected to vSwitch.
Management VLAN is, most likely, in the same boat… I meant, on the same team, as child ones are.
I.e. I usually don’t need to access to child VLANs from parent partition – so I would prefer to disable child related vNICs on parent, if I have any.
However, on cluster configuration I do need to monitor those VLANs and perform migration in case in case connectivity is lost.
(Besides of different failures, connectivity can be lost because of wrong VLAN configuration is applied to physical switch port and it doesn’t carry expected VLAN ID anymore ;-)
So same question again – how do I monitor child VLANs from host – what is the right way of doing it?
Is there a way a child can send a message to host about lost connectivity?
Sorry guys, so many questions for are a quite simple setup…
I’ll really appreciate your help. ;-)