New-VMExternalNetwork fails

Aug 9, 2011 at 2:43 PM

Hi,

I'm trying to create a new external network that is bound to my Broadcom Gigabit network card on my Hyper-V server for use with virtual machines (sorry for the German text parst in between):

PS C:\Users\administrator.DEMO> new-vmexternalswitch -virtualswitchname "first new ext switch" -ext "Broadcom NetXtreme"
 -server macwin2k8r2

Bestätigung
Möchten Sie diese Aktion wirklich ausführen?
Ausführen des Vorgangs "Use Host network card for an external virtual network" für das Ziel "Broadcom NetXtreme Gigabit
 Ethernet".
[J] Ja  [A] Ja, alle  [N] Nein  [K] Nein, keine  [H] Anhalten  [?] Hilfe (Standard ist "J"):
Test-WMIResult : Failed to create the external Switch first new ext switch on Server macwin2k8r2:
<INSTANCE CLASSNAME="Msvm_Error"><PROPERTY NAME="CIMStatusCode" TYPE="uint32"><VALUE>1</VALUE></PROPERTY><PROPERTY NAME
="CIMStatusCodeDescription" PROPAGATED="true" TYPE="string"></PROPERTY><PROPERTY NAME="ErrorSource" PROPAGATED="true" T
YPE="string"></PROPERTY><PROPERTY NAME="ErrorSourceFormat" TYPE="uint16"><VALUE>0</VALUE></PROPERTY><PROPERTY NAME="Err
orType" TYPE="uint16"><VALUE>4</VALUE></PROPERTY><PROPERTY NAME="Message" TYPE="string"><VALUE>Fehler beim Einrichten d
es Switches: Name="9af7aa32-2805-40fe-a20c-a8699fcc2125", externer Port="first new ext switch_ExternalPort", interner P
ort="first new ext switch_InternalPort", NIC="{989570E3-3BEC-4B88-A29E-9D1492549038}", interner Name="first new ext swi
tch", interner Anzeigename="first new ext switch", Fehler=2147749896, MOF-Code=0.</VALUE></PROPERTY><PROPERTY.ARRAY NAM
E="MessageArguments" TYPE="string"><VALUE.ARRAY><VALUE>9af7aa32-2805-40fe-a20c-a8699fcc2125</VALUE><VALUE>first new ext
 switch_ExternalPort</VALUE><VALUE>first new ext switch_InternalPort</VALUE><VALUE>{989570E3-3BEC-4B88-A29E-9D149254903
8}</VALUE><VALUE>first new ext switch</VALUE><VALUE>first new ext switch</VALUE><VALUE>2147749896</VALUE><VALUE>0</VALU
E></VALUE.ARRAY></PROPERTY.ARRAY><PROPERTY NAME="MessageID" TYPE="string"><VALUE>14070</VALUE></PROPERTY><PROPERTY NAME
="OtherErrorSourceFormat" PROPAGATED="true" TYPE="string"></PROPERTY><PROPERTY NAME="OtherErrorType" PROPAGATED="true"
TYPE="string"></PROPERTY><PROPERTY NAME="OwningEntity" TYPE="string"><VALUE>Microsoft-Windows-Hyper-V-Network</VALUE></
PROPERTY><PROPERTY NAME="PerceivedSeverity" TYPE="uint16"><VALUE>3</VALUE></PROPERTY><PROPERTY NAME="ProbableCause" TYP
E="uint16"><VALUE>0</VALUE></PROPERTY><PROPERTY NAME="ProbableCauseDescription" PROPAGATED="true" TYPE="string"></PROPE
RTY><PROPERTY.ARRAY NAME="RecommendedActions" PROPAGATED="true" TYPE="string"></PROPERTY.ARRAY></INSTANCE>
+
Bei C:\Windows\system32\WindowsPowerShell\v1.0\Modules\HyperV\Network.ps1:200 Zeichen:54
+                        if ( ($result | Test-wmiResult <<<<  -wait -JobWaitText ($lstr_ExternalSwitchSetup  -f $virtua
lSwitchName) `
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Test-WMIResult

What I also tried is to get more info on the card itself:

PS C:\Users\administrator.DEMO> Get-WmiObject -Namespace $HyperVNamespace -query "Select * from Msvm_ExternalEthernetPor
t " | select name, isbound

name                                                                                                            isbound
----                                                                                                            -------
Broadcom NetXtreme Gigabit Ethernet                                                                                True

 

Any idea what I'm doing wrong here? Is there any way I could also assign a VLAN ID to that new external network?

Thanks!

Kurt

Aug 10, 2011 at 8:35 AM

I just found out that you cannot add a second virtual network to a physical network card in Hyper-V - correct? When I installed Hyper-V, it has created a virtual Network card for the one and only physical card which is in the physical server. So adding a second virtual network card to the physical card is impossible, right? that would explain why this command fails...