Create virtual switch failure

Hi all,
I'm trying to create external virtual switch on newly installed HyperV 2012 R2 server.
I'm using the same NIC with host server, and Allow management OS to share this network adapter is checked. When I click Apply i get following error after 5-10 min of delay:
Adding ports to the switch 'LAN' failed.
The operation failed with error code '-4'.
After that server becomes unavailable for network communication.
Any help on this issue will be appreciated.

Hi Sergey,
How are things going ?
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.

Similar Messages

Server loses internet connection after creating virtual switch in hyper-v

On a fresh Server 2012R2 Essentials install, I set up Hyper-v and created an external virtual switch. Connection to the vm is good but Health Report no shows loss of internet connectivity and that the router is incorrectly setup.
However, I still have a working internet connection? I worry that the server may not update or allow Anywhere Access at some time. Any suggestions? Thanks

If Hyper-V virtual switch behaves strange and server is destined for testing, then it's correct and I recomend delete this virtual switch and create it again.
Here is some issues with internet connection and Hyper-V switch, none of them does not match your problem, but can be inspirative for troubleshooting:
Windows 8 Hyper-V - how to give VM internet access?
Hyper-V kills internet connection when bridging
Configuring Hyper-V for multiple subnets with only one NIC (Server 2008 R2 Edition)
How does basic networking work in Hyper-V?
Best Regards,
thennet

Poor network when create virtual switch in hyper-v 2012

Hello,
i installed on DELL R620 windows server 2012 STD and add the hyper-v role
when i created a virtual switch , the speed of network in the HOST( the server itself) is ver poor ( copy file from fileserver is 300Kbs)
when i remove the virtual switch , the speed of the network is better( copy file from fileserver is 10-20Mbps)
i spoke with DELL support center , and after check up , no problem has found.
i tried all the chnges with the offload checksum etc but nothing helped
Please your comment about this issue
Thanks
Dotan

Need some additional information
Which Team type are you utilizing?
Which Raid Controller are you using on the hosts?
I would suggest you try this as well while its specific to 10Gb CNA's it can help with 1Gb in some cases. SMB
FILE COPY PERFORMANCE
Also utilizing the low latency Bios settings can often offer additional NIC performance
Dell 12th Gen Low Latency Bios Settings
-Sean

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

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

How to mornitor VSS (Virtual Switching System) & Stack (Switch) By Cisco Prime Infrastructure

Dear all,
I have 02 C6504-E with VSS (Virtual Switching System)
and 02 C3750X-24T-L used Stack
How to you Cisco Prime Infrastructure to monitor VSS & Stack tatus?
Thanks.

Virtual Switching technology is the process of combining two standalone distribution switches found in the local distribution layer into a single management point.
The Virtual Switching System functions and appears as a single switch to the wiring closet and the core layer. You can also create Virtual Switching Systems with a pair of standalone switches available in the core layer.
For configuration please check the below link:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.1/user/guide/configuration/configvss.html#wp1042960

Virtual switch networking in LDOM error

Hi All,
I am trying to create virtual switches for 10 Gbe interfaces and when I try to bind the resource to the domain, I get the following warning:
root@ebsprdb1 # ldm bind-domain vmprdb1
Mar 11 15:28:54 ebsprdb1 vsw: WARNING: vsw6: Failed to programmacaddr,vid(0:14:4f:f8:23:c5, 0) err=6
Mar 11 15:28:54 ebsprdb1 vsw: WARNING: vsw7: Failed to programmacaddr,vid(0:14:4f:fb:60:5c, 0) err=6
I am able to see the devices in the Guest Domain. Is it safe to ignore the messages?
I used the following commands:
root@ebsprdb1 # dladm show-phys
LINK MEDIA STATE SPEED DUPLEX DEVICE
net1 Ethernet unknown 0 unknown igb1
net0 Ethernet up 1000 full igb0
net3 Ethernet unknown 100 full igb3
net2 Ethernet up 1000 full igb2
net4 Ethernet up 10000 full nxge0
net5 Ethernet unknown 0 unknown nxge1
net6 Ethernet unknown 0 unknown nxge2
net7 Ethernet unknown 0 unknown nxge3
net8 Ethernet up 10000 full nxge4
net9 Ethernet unknown 0 unknown nxge5
net10 Ethernet unknown 0 unknown nxge6
net11 Ethernet unknown 0 unknown nxge7
net27 Ethernet up 1000 full vsw0
net29 Ethernet up 1000 full vsw1
net16 Ethernet up 10000 full vsw2
net33 Ethernet up 10000 full vsw3
net13 Ethernet up 10 full usbecm0
net35 Ethernet up 0 unknown vsw4
net37 Ethernet up 100 full vsw5
root@ebsprdb1 # dladm show-linkprop -p mtu net16
LINK PROPERTY PERM VALUE DEFAULT POSSIBLE
net16 mtu rw 1500 1500 1500
root@ebsprdb1 # dladm show-linkprop -p mtu net33
LINK PROPERTY PERM VALUE DEFAULT POSSIBLE
net33 mtu rw 1500 1500 1500
root@ebsprdb1 # ldm add-vsw net-dev=net16 primary-vsw16 primary
root@ebsprdb1 # ldm add-vsw net-dev=net33 primary-vsw33 primary
root@ebsprdb1 # ldm add-vnet vnet16 primary-vsw16 vmprdb1
root@ebsprdb1 # ldm add-vnet vnet33 primary-vsw33 vmprdb1
Regards

Not sure if you figured this out but at least in my case, tagging the VSW with a VLAN id when the port was already tagged on the switch generated this error. When I recreated the VSW without specifying a VLAN id eliminated the error; all frames leaving the physical switch port will be tagged with its VLAN on egress anyway unless you're using multiple VLANs on the same port.

Failed while creating virtual Ethernet switch. Failed to connect Ethernet switch port

Hello Folks
I am completely stuck with the configuration of my virtual networks. I have one logical switch left to add to one of my Hyper-V 2012 R2 hosts when I started getting the error below when I try to add logical switches to either Hyper-V Host. I have been using
the document. 'Hybrid Cloud with NVGRE (Cloud OS)' to implement the virtual networking. Basically using the exact configuration that is in the document. I have added the PA Logical Network and the Network adapters and added the logical switch for it to my
hyper-v 2012 R2 host and everything was fine. I am now trying to add my ISCSI Logical Switch to the host and this is the error I get. My other Hyper-V host I get this error for any logical switch I am trying to add. Can someone help me with this error. I haven't
been able to find any information about it.
Also a some quick info on tracing an error like this so I can figure out what is causing it.
Thsi is my configuration so far
So as far as I know everything is peachy untill the error below. Dead stop now
Error (12700)
VMM cannot complete the host operation on the 08-NY-VHOST01.accounts.ccac-ont.ca server because of the error: Failed while creating virtual Ethernet switch.
Failed to connect Ethernet switch port (switch name = '******', port name = '88C16766-ED02-4AC0-8CD7-660AC9D424DD', adapter GUID = '{FAF431D8-0124-4E40-BB3B-9234BAA02973}'): The system cannot find the file specified. (0x80070002).
Unknown error (0x800b)
Thank you for your time
Christopher
Christopher Scannell

notice your GUID? you may want to consider ensuring that is the same GUID associated in your database. Sometimes during data corruption theres a smidge of a chance your sql database kind of either pulls old guids esp if this was reverted to snapshot
without it being powered off etc.
I would try that first. then i would consider if you get to configure that with your current liscense associated with the host. I would need way more info to help any further

Cannot create Hyper-V external virtual switch Server 2012 R2

Hi,
I am unable to create an external virtual switch on server 2012 R2. I have two Broadcom NICS bridged on a DC fully functional now. I can install Hyper-V but the option is grayed out to create an external switch. I try binding it to the
network bridge, connecting my two NICS and it makes no difference.
Am I correct in assuming that I cannot use Hyper-V on this server if the two NICS are bridged?

try command "New-VMSwitch" from Powershell to get more information
Windows 2012 & Hyper-V: Converged Network and QoS
Hyper-V Virtual Switch 101: How to create and use Virtual Switches to connect Virtual Machines to Network
Have a nice day !!!

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.
¯\_(ツ)_/¯

How to resolve A VMWare portgroup with VLAN ID 0 cannot be founf on virtual switch vSwitch0.

Hi All,
I have deployed Microsoft private cloud using SCVMM, SCOM, SCCM, SCSM, SCO and SCSM Portal...
Also, i am using cloud service process pack runbooks and offerings for my vm provisioning in VM Ware platform...
After submitted the request vm got created but it is throwing an error in SCVMM jobs:
A VMWare portgroup with VLAN ID 0 cannot be found on virtual switch vSwitch0...
VLAN ID of the existing virtual switch vSwitch is 48 and that we cannot change...also we cannot create a new vswitch in DC...
How can i resolve this error...
Thanks in advance for your help...
Regards,
Sudheesh M A

Hi Alexander,
Thank for answering. I asked custumer to send some config file from the switch. I don´t how complete is this, but, regarding "mls cos" entries, we have:
no aaa new-model
switch 1 provision ws-c2960x-48ts-l
ip domain-name ecs.local
login on-failure trap
login on-success log
vtp mode transparent
mls qos
crypto pki trustpoint TP-self-signed-1837850112
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-1837850112
revocation-check none
rsakeypair TP-self-signed-1837850112
interface GigabitEthernet1/0/1
switchport access vlan 235
switchport mode access
srr-queue bandwidth share 1 70 25 5
priority-queue out
mls qos trust dscp
service-policy input ACCESS_INGRESS
interface GigabitEthernet1/0/2
switchport access vlan 235
switchport mode access
srr-queue bandwidth share 1 70 25 5
priority-queue out
mls qos trust dscp
service-policy input ACCESS_INGRESS
interface GigabitEthernet1/0/48
switchport access vlan 235
srr-queue bandwidth share 1 70 25 5
priority-queue out
mls qos trust dscp
service-policy input ACCESS_INGRESS
Is these entries make any sense for the behavior we are facing?
Thanks

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.

"Server either does not have a virtual switch configured or none of the configured virtual switches have an IP address assigned" error driving me nuts!

OK; have been trying to setup a test VM based RDS deployment for a few days now with no luck.
this error mentioned above:
"Server <server name> either does not have a virtual switch configured or none of the configured virtual switches have an IP address assigned" error is driving me nuts!
I have removed and re-added the RD Virtualization Host role numerous times, each time having the "create a virtual switch" checkbox selected, but it did NOT create any virtual switch.
I created the external virtual switch manually and tried to create the desktop collection again, no luck with the same error.
a few questions:
1. you don't assign IP to a switch! you assign IP to Network Interfaces. why does the error puts it like this?! it is technically wrong.(yeah yeah I know all about how you'd assign IP to managed switches in real world to telnet into them and manage them.
you know better than me that it is not the case here!)
2.the RDS Virtualization hosts are using their wifi card as the card for the virtual switch. could that be the reason? I even disabled their unplugged wired NIC just to make sure that the wifi is the only available option for the RDS wizard to use for the
virtual switch creation; but it didn't use it and it didn't create any virtual switch automatically.
3.if WIFI nic is indeed the reason, is it your suspension or an official documents is there somewhere stating so (that the WIFI NICS on a Virtualization hosts are not supported as the hub for a virtual switch).
4.what are the properties of the virtual switch the RDS requires? does it have to be external? why can't it work even with my manually created external switch?
5.how would I fix it?
P.S: the environment is made up of 2 laptops, having windows 2012 R2 trial installed on them, using their wifi to connect to the out world. no cable is plugged into their wired NIC card.

Hi,
Thank you for posting in Windows Server Forum.
The simplest short term solution was to connect each computer to a small switch that had no other connectivity. This brought up the link light on the external NIC and allowed the creation of the collection to complete. You need to use an external switch. You
can create one external switch which might fix the problem.
Please check below article for information.
VDI Deployment Error About Virtual Switch
In addition please referthis article for information regarding virtual switch.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Need help setting up a virtual switch setup for my lab.

Hi,
I used to be able to get this to work. But, I'm not able to anymore.
I have two network cards in my PC.
#1 Is what I use for everyday use and it's configured to use :
IP: 192.168.0.2
GW: 192.168.0.1
DNS : 192.168.0.1 (Router address)
#2 Is setup to use
IP: 192.168.0.3
GW: 192.168.0.1
DNS : 192.168.0.1 (Router address)
Then I create a Virtual Switch in Hyper V Virtual Switch Manager and bind it to Network Card #2.
This creates the Hyper V Virtual Ethernet Adapter that I bind my VM's to.
But for some reason none of my VM's can get a connection to the internet. There is an exclamation mark over the network icon.
When I go back and look at the TCP/IP V4 properties of the Virtual Ethernet Adapter, I release that it has no DNS settings.
But when I put any settings in there it gives me a warning about setting multiple default gateways, and do I want to continue, yes or no?
What could I be doing wrong?
Thanks

Hi midi25,
Then I create a Virtual Switch in Hyper V Virtual Switch Manager and bind it to Network Card #2.
This creates the Hyper V Virtual Ethernet Adapter that I bind my VM's to.
I think you checked the "Allow management operating system ..." , the new Vethernet adapter is a virtual adapter for HOST ( the name same with the Vswitch) .
So , the "multiple default gateway" will arise when you configure GW for it .
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.

SCVMM Virtual Switch Provisioning ignores "Inherit settings from the physical management adapter" setting

When provisioning a new Hyper-V hosting into SCVMM I have a situation occur that causes loss of management to the server, which really should not be happening. When I add a new host, I set the 'Virtual Switch' adding a new 'Logical Switch' as well as a 'Virtual
Network Adapter' for the management OS traffic.
The first NIC in the team is active and configured with correct static IP information, which is allowing VMM access to the server to perform these steps. The 'Virtual Network Adapter' has a checkbox in the 'This virtual network adapter inherits settings
from the physical management adapter.' option box.
From my understanding what should happen is when the virtual adapter is created on the host the IP information should move to the virtual adapter from the physical adapter that is now part of the NIC Team. What is actually happening is the NIC Team seems
to create OK, but it picks up a DHCP IP address instead of assuming the first physical NIC's IP information. I tried this with only one NIC as well as both NICs in the team to see what happens. Either case the same problem presents.
To get around this, what I did was sit on the console after I started the provisioning process. As soon as I saw Teamed NIC create I applied the static IP address via PowerShell manually to that Teamed NIC virtual adapter and then VMM just continued along
normally. It then moving the IP from the NIC Team adapter to the Hyper-V virtual adapter properly. I did get a warning back from the creation (below) which hints me to the problem.
The Error code details as 2147942465 which is a "Network Access Denied" code followed by "Error while applying physical adapter network settings to teamed adapter". So, this is telling me there was a permission issue of some sort during
the step of adding the original physical NIC IP settings to the virtual NIC.
The VMM Run As user 'HVAdmin' is a Local Administrator on the Hyper-V host, this has been verified. It has also been temporarily granted Administrator access on the domain to see if it helps. No go.
Searching around the net has now revealed this problem so far, has anyone else seen this? It makes provisioning a bit of a chore because I have to be at the Hyper-V console and on VMM at the exact same time to add a new host.

It's a workaround but this works best.
When initially configuring the host use a dedicated Nic.
Configure the new team with a management Vnic and assign the Vnic an IP.
Now disable the dedicated nic and you can start working the the team and the Vnic.
Gil Gross | Technical Lead | G-Net Network Solutions | www.g-net.co.il | plz visit my blog - gilgrossblog.wordpress.com

Create virtual switch failure

Similar Messages

Maybe you are looking for