Create Hyper-V virtual switch with VLAN tagging

Hello All,
I would like to create virtual network switch on a physical NIC of the Hyper-V host in Powershell.
I use "New-VMSwitch" with "-AllowManagementOS $true" and the virtual switch will be ready. I would like to use "Enable virtual LAN identification for management operating system"
and tag a VLAN to the virtual switch. Can you please help me with an example how to do it in Powershell?

Start with this walk-through.
http://www.vnotebook.ca/2013/11/configuring-management-vlan-in-hyper-v.html
tags are bound to adapters. A switch must have minimum of one adapter.
¯\_(ツ)_/¯

Similar Messages

Create Hyper-V Virtual Machines with Windows PowerShell searching on hostname

Dear,
I’m a starter with PowerShell scripting an I’m looking for a script to create Hyper-V Virtual Machines with Windows PowerShell. The idea behind the script is that when I run the script its first searching for the hostname. I’m migrating 24 locations and each
location have a different hostname like xxx-SRV001. The script needs to use the first 3 signs from the hostname in this case “xxx” and create 2 VM's with below info:
Virtual Machine 1 2048MB
Virtual Machine 2 4096MB
Location D:\VM\
I can create VM's with Powershell into Hyper-V so only a script to first searching for the first 3 characters of the hostname is enough.
Example:
It's the intention that when the script runs it's looking for the hostname. As example we have hostname 000-SRV001
If the script see the first 3 characters of the hostname, in this case 000 he need to create 2 VMs with name xxx-SRV002 and xxx-SRV004
I think it must be something with
$hostname = "Get-WmiObject -computername $Machine Win32_Computersystem"
But then when i'm asking for $hostname he must give me back the hostname and if the hostname is 1 of the 24 locations then he need to create 2 vm's in Hyper-V with above info.
Can you help me or do you have a script for this?

Juste use :
$vram = 1GB*$vRam
You not need the "
Do you have any error with the creation of the VM?
# Variables
$VMName = Import-Csv "C:\HyperV\input.csv"
$VHD = 40GB
$VMLOC = "C:\HyperV"
$vSwitch = "External"
$ISO = "C:\ISO\WinServer2012R2.iso"
$LocationCode = $env:COMPUTERNAME.Split("-")[0]
# Create VM Folder
MD $VMLOC -ErrorAction SilentlyContinue
Foreach ($VM in $VMNames)
$Name = $VM.name
[int64]$vRam = $vm.vram
$vram = 1GB*$vRam
$VMName = $LocationCode+$Name
# Create Virtual Machine
New-VM -Name $VMName -Path $VMLOC -MemoryStartupBytes $vRam -NewVHDPath "$VMLOC\$VMName\Virtual Harddisks\$VMName.vhdx" -NewVHDSizeBytes $VHD -SwitchName $vSwitch
# Configure Virtual Machines
Set-VMDvdDrive -VMName $VMName -Path $ISO
Start-VM $VMName
# Configure Virtual Machines
Set-VMDvdDrive -VMName $VMName -Path $ISO
Start-VM $VMName
Error message
New-VM : '003' failed to modify device 'Memory'. (Virtual machine ID 8F5F32D7-F1A0-4A68-8B01-CA6661869A1E)
Invalid startup memory amount assigned for '003'. The minimum amount of memory you can assign to this virtual machine is '32' MB. (Virtual machine ID 8F5F32D7-F1A0-4A68-8B01-CA6661869A1E)
A parameter that is not valid was passed to the operation.
At line:20 char:5
+ New-VM -Name $VMName -Path $VMLOC -MemoryStartupBytes $vRam -NewVHDPath "$VM ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (Microsoft.HyperV.PowerShell.VMTask:VMTask) [New-VM], VirtualizationOperationFailedException
+ FullyQualifiedErrorId : InvalidParameter,Microsoft.HyperV.PowerShell.Commands.NewVMCommand
Set-VMDvdDrive : A parameter is invalid. Hyper-V was unable to find a virtual machine with name 003.
At line:23 char:5
+ Set-VMDvdDrive -VMName $VMName -Path $ISO
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (003:String) [Set-VMDvdDrive], VirtualizationInvalidArgumentException
+ FullyQualifiedErrorId : InvalidParameter,Microsoft.HyperV.PowerShell.Commands.SetVMDvdDriveCommand
Start-VM : A parameter is invalid. Hyper-V was unable to find a virtual machine with name 003.
At line:24 char:5
+ Start-VM $VMName
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (003:String) [Start-VM], VirtualizationInvalidArgumentException
+ FullyQualifiedErrorId : InvalidParameter,Microsoft.HyperV.PowerShell.Commands.StartVMCommand
Set-VMDvdDrive : A parameter is invalid. Hyper-V was unable to find a virtual machine with name 003.
At line:27 char:5
+ Set-VMDvdDrive -VMName $VMName -Path $ISO
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (003:String) [Set-VMDvdDrive], VirtualizationInvalidArgumentException
+ FullyQualifiedErrorId : InvalidParameter,Microsoft.HyperV.PowerShell.Commands.SetVMDvdDriveCommand
Start-VM : A parameter is invalid. Hyper-V was unable to find a virtual machine with name 003.
At line:28 char:5
+ Start-VM $VMName
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (003:String) [Start-VM], VirtualizationInvalidArgumentException
+ FullyQualifiedErrorId : InvalidParameter,Microsoft.HyperV.PowerShell.Commands.StartVMCommand
New-VM : '003' failed to modify device 'Memory'. (Virtual machine ID C0FC835E-36D4-462E-BD21-69A75A808E2F)
Invalid startup memory amount assigned for '003'. The minimum amount of memory you can assign to this virtual machine is '32' MB. (Virtual machine ID C0FC835E-36D4-462E-BD21-69A75A808E2F)
A parameter that is not valid was passed to the operation.
At line:20 char:5
+ New-VM -Name $VMName -Path $VMLOC -MemoryStartupBytes $vRam -NewVHDPath "$VM ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (Microsoft.HyperV.PowerShell.VMTask:VMTask) [New-VM], VirtualizationOperationFailedException
+ FullyQualifiedErrorId : InvalidParameter,Microsoft.HyperV.PowerShell.Commands.NewVMCommand
Set-VMDvdDrive : A parameter is invalid. Hyper-V was unable to find a virtual machine with name 003.
At line:23 char:5
+ Set-VMDvdDrive -VMName $VMName -Path $ISO
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (003:String) [Set-VMDvdDrive], VirtualizationInvalidArgumentException
+ FullyQualifiedErrorId : InvalidParameter,Microsoft.HyperV.PowerShell.Commands.SetVMDvdDriveCommand
Start-VM : A parameter is invalid. Hyper-V was unable to find a virtual machine with name 003.
At line:24 char:5
+ Start-VM $VMName
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (003:String) [Start-VM], VirtualizationInvalidArgumentException
+ FullyQualifiedErrorId : InvalidParameter,Microsoft.HyperV.PowerShell.Commands.StartVMCommand
Set-VMDvdDrive : A parameter is invalid. Hyper-V was unable to find a virtual machine with name 003.
At line:27 char:5
+ Set-VMDvdDrive -VMName $VMName -Path $ISO
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (003:String) [Set-VMDvdDrive], VirtualizationInvalidArgumentException
+ FullyQualifiedErrorId : InvalidParameter,Microsoft.HyperV.PowerShell.Commands.SetVMDvdDriveCommand
Start-VM : A parameter is invalid. Hyper-V was unable to find a virtual machine with name 003.
At line:28 char:5
+ Start-VM $VMName
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (003:String) [Start-VM], VirtualizationInvalidArgumentException
+ FullyQualifiedErrorId : InvalidParameter,Microsoft.HyperV.PowerShell.Commands.StartVMCommand

Routing of Network Traffic Between VLANs on a Hyper-V Virtual Switch

I am trying to discover how network traffic generated by reads and writes to RDVH User Profile Disks is routed through my network. I have a pool of Hyper-V
desktop vm’s in their own VLAN (vlan1) with their own NIC bound to a Hyper-V Virtual Switch. On the same server I have another management NIC for the OS on a different VLAN (vlan2) and finally on another server I have a virtual machine which hosts the User
Profile Disks. The VM that hosts the User Profile Disks is on the same VLAN as the management NIC for the OS (vlan2).
When tracing the flow of network traffic to and from the User Profile Disk VM it all comes through the vlan2 NIC on the server where the virtual
desktop VMs reside and nothing comes through the vlan1 NIC on this server. I would have expected the traffic to the virtual desktop VMs to come in through the desktop VMs VLAN NIC (vlan1).
This leads me to two possibilities as to how the desktop vm’s on vlan1 get their data to and from the User Pofile Disk vm on vlan2 without routing.
The desktop vm’s Hyper-V Virtual Switch automatically routes the User Profile Disk traffic from vlan1 to vlan2 internally using a virtual switch learning algorithm
Hyper-V itself handles all reads and writes to the User Profile Disks and since that is using the management NIC for the OS it is already on vlan2 and so the network traffic never leaves vlan2.
Any comments on the reason for traffic taking the path it does (as outlined above) as opposed to being layer-3 routed from VLAN1 to VLAN2?

Thanks for your reply Brian. I think your last paragraph above is what I have set up:
If you simply forward one VLAN to one physical NIC and the VMS on the corresponding External Virtual Switch simply end up on that VLAN without Hyper-V doing anything at all - but this dedicats one physical NIC per VLAN.
The Virtual Machines NIC that the vSwitch is patched to and the NIC for the OS are on different VLANS (both NICs are plugged into un-tagged ports on my switch).
The vNICs on the VM's are not tagged to a VLAN (The VLAN ID\ 'Enable virtual LAN identification' box is unticked)
My vSwitch is set up as connected to 'External Network' and isnt shared with the management network.
What I am trying to get at is how would network traffic on the VLAN my vm's are on get to the VLAN that the NIC for the OS is on without going through the router (even though a routable path is available) ?
Is it possible the 'learning algorithm' referneced in a Technet article below is involved here (sorry I cant post links)?
For the virtual machine to communicate with the management operating system, there are two options. One option is to route the network packet through the physical network adapter and out to the physical network, which then returns the packet back to
the server running Hyper-V using the second physical network adapter. Another option is to route the network packet through the virtual network, which is more efficient. The option selected is determined by the virtual network. The virtual network includes
a learning algorithm, which determines the most efficient port to direct traffic to and will send the network packet to that port. Until that determination is made by the virtual network, network packets are sent out to all virtual ports.
Thanks,
Andrew

Windows 8.1 - Hyper-V Virtual Switch fails to create

I'm running into a problem with creating a new virtual switch on my Windows 8.1 RTM box. Frist time attempt at Hyper-V on this system.
The error I get is as follows:
Error applying Virtual Switch Properties changes
Failed while creating virtual Ethernet switch.
switch create failed, name= 'B57B7B7B-64314AF5-AB8F-4521CBAA9FFBA', friendly name = 'New Virtual Switch': The system cannot find the file specified. (0x80070002)
The steps I have taken to try and resolve this issue.
1. Uninstall and reinstall Hyper-V...numerous times - no change.
2. Uninstall Hyper-V, reboot, uninstall NIC, reboot, reinstall NIC, reboot, reinstall Hyper, reboot - no change.
3. Uninstall it all again. Get new NIC drivers, for ASUS Sabertooth 990FX, first gen. Reinstall it all again - no change.
4. Updated BIOS, and check for virtualization, and DEP are enabled. - no change.
5. User powershell to create virtual switch - no change.
6. Tried resetting Hyper-V networking using the netcfg commands posted
here, failed, file not found.
Any help to resolving this would be greatly appreciated.
Thank you,
Sean

Hi Dw3xx,
Unusual problem,my suggestion is :
uninstall any anti-virus software then try to create the virtual switch
insert Win8 media and fix OS
Hope this helps.
Elton Ji

2012 R2 Hyper-V Virtual Switch Refuses to Be Created -- Error Messages Not Especially Helpful

Windows Servers 2012 R2 Standard
4 NICs
Windows 8.1 is guest of the host
Hyper-V
Virtual Switch Manager
External
Create Virtual Switch
External network
Choose a NIC that is connected to the physical Ethernet switch but otherwise unused
Tick Allow management operating system to share this network adapter
Untick everything else
Click Apply
"Error applying Virtual Switch Properties changes"
"Failed while adding virtual Ethernet switch connections."
"External Ethernet adapter "<name-of-adapter>" is already bound to the Microsoft Virtual Switch protocol."
Close
Cancel
Control Panel\Network and Internet\Network Connections
Change Properties of NIC to untick Virtual Switch protocol
Repeat steps as above
"Virtual Switch Manager for <name-of-server>"
"Error applying Virtual Switch Properties changes"
"An internal error occurred while processing the results of creating a new virtual switch."
"To refresh the results, close and then reopen this window."
Close
Dead in the Water
An internal error occurred while processing the results of creating a new virtual switch. To refresh the results, close and then reopen this window.
The first one is to use a tool called “nvspscrub.js”. Download nvspscrub.js then from cmd run: “cscript nvspscrub.js”, this will delete all vswitches, virtual NICs in the parent partition and will unbind the switch protocol from all physical NICs.
This script aborts when a class turns up undefined. Maybe this old script applies solely to Windows Server 2008. Dunno.
NVSPbind
What I do now?
It is an internal error. Internal to what?
MARK D ROCKMAN

Hi Mark,
I just came across the same issue!
After troubleshooting, I deleted all my Virtual Switches and reinstalled my WiFi and Ethernet NIC drivers.
I'm now able to create the Virtual Switches without error.
Hope this helps.
Regards
Lee

How to route traffic across subnets when one NIC is a hyper-V virtual switch?

Having a bit of a problem with a hyper-V environment which does not seem to route network traffic on two different subnets between each other.
If it were a purely physical server with two NICs and a gateway set traffic would automatically be forwarded between the two different subnets.
However when one of those NICs is a hyper-V virtual switch this simple routing no-longer seems to work and no traffic gets forwarded between subnets?
Situation is:
Hyper-V server with two NICs
NIC 1 = 192.168.0/24 - main Internal company network.
NIC 2 (hyper-V virtual switch.) = 192.168.1/24 - connects to ADSL internet router
Virtualized Domain Controller.
One or two virtualiszed NICs as necessary
How then does traffic get routed between these two subnets? If RRAS has to be configured to do this where is the best place to do it, on the hyper-V host or on the virtualized domain controller?
Thanks,

Hi ,
You can create an internal virtual switch and configure an IP for it (I assume it is 192.168.1.2/24) .
After you enable RRAS in hyper-v host there will be two gateways for different subnets .
" NIC 2 (hyper-V virtual switch.) = 192.168.1/24 - connects to ADSL internet router "
The problem is here ,if these VMs need to access internet .
So , these VMs can not configure their gateway same as the IP of internal virtual switch , you may set VM's gateway as the ADSL internet router's IP meanwhile add a static route entry for every VM .
Please refer to the Syntax :
route add -p 192.168.0.0 mask 255.255.255.0 192.168.1.2
Hope this helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

OneDrive and Hyper-V Virtual Switch don't mix

Since the release of Windows 10TP I have had a Hyper-V VM configured running Win10TP. Since that time I have had OneDrive synchronisation problems IN THE HOST OS (as well as in Win10TP, but that is not my focus here).
In summary, if the path from OneDrive in the host Win8.1 installation to the Internet is via a Hyper-V Virtual Switch, OneDrive will not sync up any file beyond around 1-2MB. It will sync up deletions, and it will sync down any changes that happen
in the cloud. This happens even if the host OS is the only OS connected to the Virtual Switch - I.e the guest OS has no virtual adapter connected to the VSwitch.
Details:
Configuration A. Surface Pro with Windows 8.1 connected to the Internet via WiFi. Hyper-V has always been installed on this box (for the Windows Phone Emulator) but no VM is normally active. In this configuration the host OS connects directly
to the WiFi adapter.
Configuration B. As above, but a Hyper-V Virtual Switch is in place with the host OS connected to the Internet via this VSwitch, and thence via the WiFi adapter. There is a guest Win10TP VM created. It doesn't matter whether this VM
is running or not, or whether it also has a connection to the Internet via the VSwitch, as far as the tests described below are concerned.
In configuration A, OneDrive syncing works correctly and uploads occur at roughly the speed of my uplink (not high). OneDrive has always worked correctly for me and in the month prior to installing the Win10TP I travelled around the country (Australia)
using sometimes dodgy Internet connections in motels etc., and it always worked.
In configuration B, OneDrive (in the host OS Win8.1) simply will not work correctly. It will sync all downloads correctly. It will sync up file deletions. It will sync up small files. But it WILL NOT sync up larger files.
Attempting to sync up any file above around 1-2MB results in sync hanging at "0.0KB out of x.xMB". In the OneDrive app it shows the file as Pending. Nothing I can do will make it sync those files. Deleting the offending file and
pausing and restarting syncing will straighten everything out and small syncs will continue to work. When this problem is present, there is no traffic visible between the Sync Engine and the cloud.
I can alter the machine setup between Configuration A and B and back and so on and no matter how often I switch from A to B to A to B... configuration A always works and configuration B always fails.
So...
Am I possibly missing something in configuring Hyper-V VSwitches? Otherwise what is incompatible between OneDrive traffic and the VSwitch? There is nothing obvious to me.
I should note that all other operations on the network from the host OS or from the Guest OS appear to be working correctly.

When you performed configuration B - what more did you do other than create a Virtual Switch and check the box "allow management OS to share"?
If you did more than that - there is your issue.
The only difference between the two configuration should be the existence of the Virtual Switch - I mention this because it is not clear in your description and there are some folks that do strange internet sharing configurations that the OneDrive client
is not necessarily compatible with.
Another issue that might happen is that during the sync of your large files the power savings of the NIC is kicking in and interrupting that data transfer.
In this case try disabling all power savings on the physical NIC driver (when there is a Virtual Switch present).
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

Cannot Configure Hyper-V Virtual Switch - VM has no internet access...

HI:
As stated in the title, I cannot configure my VM (OS Windows 7 Pro...) to access the internet...
When I attempt to configure a Virtual Switch with all defaults, I get this error: 0x800705B4.
I found an article online that advised to create the Switch internally without choosing the 'Connect to external network' option, then manually bridging the connections... which also didn't work...
Now I've got 'Hyper-V Virtual Ethernet Adapters' Stuck in my Device Mgr, and my VM still won't connect to the internet.
Help?

Hi GloFields,
As for the Office issue please try to post it here :
http://social.technet.microsoft.com/Forums/en-US/home?category=officeitpro&filter=alltypes&sort=lastpostdesc
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How to get the maximum bandwidth/MaxSpeed/Capacity of a Hyper-V virtual-switch?

We are trying to monitor Hyper-V environment (Windows 2008 R2 and Windows 2012) using WMI, and have a very specific question Hyper-V virtual-switch.
We have referred the below mentioned classes and their properties.
1. Win32_NetworkAdapter (namespace:root\cimv2, property:Speed)
2. Msvm_InternalEthernetPort (namespace:Root\virtualization\v2, property: Speed and Maxspeed)
3. Msvm_EthernetSwitchBandwidthData (namespace:Root\virtualization\v2, property:Capacity and Reservation)
All of the above classes and their properties returns 10000000000 (10 GBps) as MaxSpeed, which is NOT correct (as we know that our network connection is of 1 GBps)
Here is our question: How to get the maximum bandwidth/MaxSpeed/Capacity of a Hyper-V virtual-switch?

Until MSFT makes a change to increase the max speed of the virtual switch (and the resulting virtual ports) it will be 10 Gbps.
It has been this way since the original introduction in 2008.
What you are looking for is the most limiting segment in the path. The virtual switch does not assume the properties of the most limiting segment. Since the physical side could be a team, it could be a single NIC.
Your management layer must interpret the most limiting segment.
If you have not already been here:
http://blogs.msdn.com/b/tvoellm/archive/2009/04/23/monitoring-hyper-v-performance.aspx Then take a look.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

List all Virtual Machines with Associated Tags

I have custom attributes for application engineer, OS engineer, application name, etc. In the vSphere Client I can list all VMs and their custom attributes. I can then sort the list by custom attribute. Doing this allows me to find virtual machines with empty custom attributes.
I have converted my custom attributes to tags. I cannot find a way to list all virtual machines with associated tags in the vSphere Web Client. Is there a way to do this using PowerCLI? I'd like to be able to produce a CSV file that contains all virtual machines and their associated tags.

If you have tag assignments for the category of "OS engineer". You can write this:
Get-TagAssignment -Category "OS engineer"
That will list the tags in the category and the associated VMs.

Maximising throughput of a team in converged networking scenario using Hyper-V virtual switch

Hi,
Recently I have been looking into the converged network scenario, I have read quite a few resources about this but I am struggling to make sense of maximising the bandwidth I have available.
I understand that a single TCP stream can only go down 1 physical NIC, so even if I had a team of 6 x 1Gbps NICS – the team would be 6Gbps, but I will never have a single transfer go faster than 1 Gbps. I’m pretty sure that’s right, how I understood it anyway.
To make a converged network, I need to team adapters together, then make a virtual switch, and make virtual NIC’s off of that virtual switch. Each vNIC I can assign for different purposes,
such as ISCSI, data sync and backup traffic. In the diagram below I have shown this configuration, each green pNIC is only 1Gbps, on my blue vNICs I use the minimum weighting configuration.
In my example below, I have 1 ISCSI vNIC, if a physical NIC failed then I understand that to mean that the bandwidth won’t reduce for ISCSI because a single stream can only go down one
NIC anyway, the team will reduce to 5Gbps. No vNIC will go faster than 1Gbps.
If this is correct, then how would I increase bandwidth to the disk system using ISCSI, is it simply a case of creating an additional vNIC for ISCSI traffic, adding it to the same team
and configuring MPIO so the traffic will eventually end up through different pNICS? In my mind, MPIO can’t round robin ISCSI data to more physical NICs because the ISCSI and MPIO only know about the vNIC, I assume it is the team that ultimately handles the
placement of the stream onto the pNICS.
Do I simply do the same for Data Sync and Backup traffic?
I’m not too concerned about the VMNET team, I am mostly focused on getting the best out of the core cluster resources I have. I haven’t shown the physical switches to the right of the diagram,
but these are already configured to accept the VLAN traffic on the ports and the same is all configured for the other half of the solution.
Just a little confused over the whole thing on how I could potentially achieve the 6Gbps I have at my disposal. In this configuration and testing so far, it seems quite difficult for me
to exceed about 1.5-2Gbps combined across all the vNICS (in this particular test server I am limited to 1 physical disk so it’s hard to gauge the performance, the disk will take probably about 200MB/2Gbps maximum, that’s with ISCSI (file copying) and data
Sync going on between two servers at the same time.
many thanks for your help
Steve

Hi,
Recently I have been looking into the converged network scenario, I have read quite a few resources about this but I am struggling to make sense of maximising the bandwidth I have available.
I understand that a single TCP stream can only go down 1 physical NIC, so even if I had a team of 6 x 1Gbps NICS – the team would be 6Gbps, but I will never have a single transfer go faster than 1 Gbps. I’m pretty sure that’s right, how I understood it anyway.
To make a converged network, I need to team adapters together, then make a virtual switch, and make virtual NIC’s off of that virtual switch. Each vNIC I can assign for different purposes,
such as ISCSI, data sync and backup traffic. In the diagram below I have shown this configuration, each green pNIC is only 1Gbps, on my blue vNICs I use the minimum weighting configuration.
In my example below, I have 1 ISCSI vNIC, if a physical NIC failed then I understand that to mean that the bandwidth won’t reduce for ISCSI because a single stream can only go down one
NIC anyway, the team will reduce to 5Gbps. No vNIC will go faster than 1Gbps.
If this is correct, then how would I increase bandwidth to the disk system using ISCSI, is it simply a case of creating an additional vNIC for ISCSI traffic, adding it to the same team
and configuring MPIO so the traffic will eventually end up through different pNICS? In my mind, MPIO can’t round robin ISCSI data to more physical NICs because the ISCSI and MPIO only know about the vNIC, I assume it is the team that ultimately handles the
placement of the stream onto the pNICS.
Do I simply do the same for Data Sync and Backup traffic?
I’m not too concerned about the VMNET team, I am mostly focused on getting the best out of the core cluster resources I have. I haven’t shown the physical switches to the right of the diagram,
but these are already configured to accept the VLAN traffic on the ports and the same is all configured for the other half of the solution.
Just a little confused over the whole thing on how I could potentially achieve the 6Gbps I have at my disposal. In this configuration and testing so far, it seems quite difficult for me
to exceed about 1.5-2Gbps combined across all the vNICS (in this particular test server I am limited to 1 physical disk so it’s hard to gauge the performance, the disk will take probably about 200MB/2Gbps maximum, that’s with ISCSI (file copying) and data
Sync going on between two servers at the same time.
many thanks for your help
Steve

6 instances of broken Hyper-V Virtual Switch Extension Adapters.

Hi. I am unable to create a hyper-v virtual network switch (post Windows 8.1 Update installation). Every time I attempt it, a new corrupted adapter is created and an error is reported.  They all report the same issue:   Code 10
Operation Failed.    I have tried the following:
1. Right click "uninstall". No error but the adapter is not removed.
2. No virtual adapters are currently visible in Hyper-V Management studio .... but not from the lack of trying. They fail to create and cause the Hyper-V management service to abort.
3. Tried to uninstall Hyper-V but it won't uninstall. Also does a restore at the end.
4. Run numerous Microsoft utilities (SFC, FixIt, etc).
OS was recently updated to Windows 8.1 Update (64bit). My problems started with the rather painful upgrade.   Also unable to re-install the Cisco VPN after uninstalling to complete the upgrade. Installing the Cicso VPN client is
my ultimate goal but was going to run it in a VM if necessary since I couldn't install it. Hence the Hyper-V cluster. Any help would be greatly appreciated. I have spend a couple of weeks on the Upgrade and trying to get my computer
working again with no luck.  Thank you!

Hi,
Was your issue resolved?
If yes, we will archive this thread temporarily.
If no, please reply and tell us the current situation.
If you have any other question, feel free to contact us. We will try our best to help you.
Karen Hu
TechNet Community Support

Two srw switches with vlans and pfsense gatway

Hi,
I've got a bit of a problem that a can't seem to get a handle of things.
I've got two srw 48 port switches that I would like to link together and then on to the pfsense box.
First I'd like to connect the two switches to see if everything works and then on connect the pfsense box.
Now I would be very great full if someone with a bit more experience with VLANs would be so kind to walk me trough the procedure of creating VLANs, configuring them to ports on the switch and connecting the whole thing to another switch.
This is what I've done so fare.
1. I created 3 VLANs on both switches (VLAN2-office,VLAN3-WiFi, VLAN5-VoIP). I've created these VLANs with the same tags on all the devices.
2. I configured the ports that connect the switches as trunk. (I can't seem to be able to configure anything else on this port. Is there something else I should configure on these ports?)
Now as fare as I understand the documentation the VLANs on each switch should now see each other.
I'm still not sure on how to configure a physical port to one VLAN. After creating the VLANs on both switches and connecting them trough the trunk port I set ports 10-20 to VLAN2 by going to VLAN Management -> Ports to VLAN I selected VLAN2 and marked ports general and untagged and saved the settings. I repeated the procedure on the other switch. Now if I stuck my network cable into one of this ports I didn't get an IP anymore form the DHCP witch means that they were on a different VLAN than the other ports so I setup another router to act as a test DHCP with a different IP range as the main DHCPto see if it works. Now when I connectedthe test router to one of the ports in VLAN2 and my PC to the same VLAN2 port I got the test IP no problem. But when I connected the PC to the other switch VLAN2 port nothing happened until I connected the test DHCP to one of the VLAN2 ports. So clearly the switch VLANs are not communicating.
Now I don't know did I forget something, made a mistake with some setting or I just don't know what I'm doing because I think I need to get the VLANs between switches working before tackling the pfsense connection.
I would be really great full if someone explains to me how to set these VLANs up so that they would work between switches.
Thank you for your help.

Hi,
I was successful and I did exactly that. I put all VLANs on trunk ports and the switch to switch to pfSense started to work.
The only thing that gave me some problems was the end port(port connecting to the device pc, phone, printer) configuration. I was under the impression that the port was supposed to be in general mode and tagged. But I figured out that the port is supposed to be in access mode and untagged and only a member of one VLAN(the one I wanted it to connect to).
Anyway all is working now and I've figured out all the kinks.
So thanks guys for the help.
Nice day to all.
Bye

Hyper-V virtual switch connecting to different wireless router than mine, and stops the Hyper-V session from working

hi,
I have hyper v running on windows 8.1 pro laptop and have 2 virtual switches configured. the ethernet connection works great all the time.
The wireless has problems with wireless networks. half pics up my home network as i want and the other half picks up a wireless network in range which is not mine.
How do i fix this, as when this happens i cannot use the virtual machine to connect to the network or the internet
My home wireless network is the KamelsHome which you see is connected thus the laptop works. But as you can see the VEthernet (Wireless) is picking up a NETGEAR88.
Screenshot attached
Anyone help please??

Hi Dominic,
Would you pleaes let me know if you have removed the wireless profile and then to see if the issue persists?
How to Delete or Forget Wireless Network Profiles in Windows 8.1
http://www.7tutorials.com/how-delete-forget-wireless-network-profiles-windows-81
Have a nice day!
Regards,
Steven Song
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Mesh Ethernet Bridging with VLAN Tagging Issue

Hi all.
I'm a little stuck with a 4400 7.0.220.0 + RAP 1550 + MAP 1260 Ethernet bridging issue. I'm using the VLAN tagging functionality and I'm finding that periodically a VLAN that I've tagged on the MAP will deregister from the backhaul and stop passing traffic. If I go into the Mesh tab on the MAP, select the wired interface, remove the VLAN from the list of tagged VLAN IDs and then add it right back to the list, its starts passing traffic again.
Has anyone else seen this? I can't find any relevant bugs.
Justin

Hi Saravanan,
It is one RAP and three MAPs. After a TAC call and 30 hours of monitoring, my VLANs have remained registered. I think the issue was mismatched VLANs to bridge groups an it looks like the mesh bridge may be stable for now. Here is what I was seeing on the RAP and MAPs when the VLANs were deregistering unexpectedly. Notice how VLANs 2 and 10 are mapped to opposite bridge groups on the RAP and MAP:
After I removed all the VLAN IDs from the Trunk configuration on the MAPs (through each AP's Mesh tab -- Ethernet Bridging config) and then rebuilt the VLAN IDs, I ran the same commands and now see this:
My very unscientific theory here is that the mismatching was causing consistency checks to fail, so the RAP was just tearing down the registrations after getting bogus or non- responses from the MAPs during the periodic VLAN registration maintenance checks (debug mesh ethernet registration).
If I have continued issues, I'll post back with updates.
Thanks for the response!
Justin

Create Hyper-V virtual switch with VLAN tagging

Similar Messages

Maybe you are looking for