From what I see to use the "Add-VMNetworkAdapter" cmdlet we need to have the Hyper-V shell installed. My quesiton though is if I for example have 1 physical adapter for use and I want to divide it into multiple adapters (vNICs), for example so that for each adapter I can configure a dedicated VLAN tag and/or configure QOS. For example, vNIC1 will use VLAN 1 and be used for software-based replication with a bandwith allocation of 10%. vNIC2 will use VLAN 2 and be used for client traffic with a bandwidth allocation of 20%, etc.
This purpose will be used for Application X, NOT Hyper-V or a VM. My question is, is there a way to "carve out" multiple vNICs from a single adapter? Is this only supported/allowed for Hyper-V? And if so, for example is I install the Hyper-V Management Tools/Shell and do this, will I have issues? Or, are there other cmdlets to do the same thing, just not via the Hyper-V Cmdlets?
Thanks,
Reuvy