Trunk mode vlan to a VM with 8 vNIC's - targetting one specific vNIC

Question

Hi all
I've popped a question into the Powerhsell forum this morning, and realised it may have been more suitable in Hyper-V section due to the nature of the question. Apologies if dual posting is not the done thing.
My original question can be seen here:
https://social.technet.microsoft.com/Forums/scriptcenter/en-US/5b12e416-ffc9-4391-b3f1-91fdb192f11a/hyperv-trunk-mode-to-vm-how-to-target-a-specific-virtual-nic-using-powershell?forum=winserverpowershell
Essentially, my question is around a VM that currently has 8 x vNIC's, but needs to communicate over 9 x vlans at present. I have attempted the following command in a test environment, but I can't see how this would comms over a specific vNIC; it looks like
its a global command to the target VM:
Set-VMNetworkAdapterVlan -VMName test1 -Trunk -AllowedVlanIdList "1-5" -NativeVlanId 6
Is there a way to target a specific vNIC on a VM with the above command at all, or is there a better way to enable trunk mode to the intended VM please?
Thanks
Paul

Answer 1

Hi Eric
Thanks for reply.
Thanks - your reply got me thinking a little more about this, and I found another article (which was also a reply from yourself when someone asked about how you rename a network adaptor when every adaptor is called "Network Adapter"),
that lead to a working command for what I would like to achieve.
So, here is my working command now:
Get-VMNetworkAdapter -VMName test2 | Where-Object -Property MacAddress -eq "000000000098" | Set-VMNetworkAdapterVlan -Trunk -AllowedVlanIdList "2214-2217" -NativeVlanId 22
Upon running Get-VMNetworkAdapterVlan I can see how the various adaptors are now configured:
test2                    Network Adapter               Untagged
test2                    Network Adapter               Untagged
test2                    Network Adapter               Trunk    22,2214-2217
test2                    Network Adapter               Untagged
I appreciate my command may not be pretty, but it completes successfully in my lab in terms of applying the settings.  Is there any obvious problems that you can see with the above?
Lastly, the reason for the vlans in this way is because the server is NetBackup Master Server, and needs comms over all the relevant vlans. I'm intending on configuring a secondary interface through the teaming GUI in Server 2012, and specifying vlan ID's
there.
Thanks
Paul