info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Can't configure virtual network connect to external
458 views
Skip to first unread message
Hii Sing Chung
Apr 22, 2008, 5:45:12 AM4/22/08
to
I am running Windows 2008 Enterprise x64 and had updated the Hyper-V to RC0.
The server is an HP Proliant DL360 G5 5110 (Xeon 2 Cores), 4GB RAM. I
configured teaming on the 2 Gigabit NIC (HP NC373i Multifunction Gigabit
Server Adapter). The Server (the host) has fixed IP address configured. In
Hyper-V the Virtual Network was default set up as "Private virtual machine
network". Whenever I changed it to External, and clicked OK or Apply, it
said "Apply Changes...." and would remains at this state forever. I left it
running for 2 weeks, it was still like that. I rebuilt the server from
scratch (re-created the RAID, re-install OS), when I reached the Virtual
Network Manager and configure the virtual network to External, click OK or
Apply, it went to the "Apply changes....." endless loop. I am stuck here.
The server is an HP Proliant DL360 G5 5110 (Xeon 2 Cores), 4GB RAM. I
configured teaming on the 2 Gigabit NIC (HP NC373i Multifunction Gigabit
Server Adapter). The Server (the host) has fixed IP address configured. In
Hyper-V the Virtual Network was default set up as "Private virtual machine
network". Whenever I changed it to External, and clicked OK or Apply, it
said "Apply Changes...." and would remains at this state forever. I left it
running for 2 weeks, it was still like that. I rebuilt the server from
scratch (re-created the RAID, re-install OS), when I reached the Virtual
Network Manager and configure the virtual network to External, click OK or
Apply, it went to the "Apply changes....." endless loop. I am stuck here.
Is this caused by the NIC teaming?
Any idea why?
Ryan Sokolowski [MVP]
Apr 22, 2008, 9:56:26 AM4/22/08
to
Break the NIC team and try this again.
--
Ryan Sokolowski
MVP - Clustering
MCSE, CCNA, CCDA, BCFP
"Hii Sing Chung" <sing...@sgintracod.com> wrote in message
news:AA40862C-5584-4F59...@microsoft.com...
Charlie Russel - MVP
Apr 22, 2008, 10:24:49 AM4/22/08
to
I'd agree with Ryan, this is probably from the NIC teaming. The issue is
that when you create an external network in Hyper-V, it removes the TCP/IP
stack from the NIC and replaces it with the "Microsoft Virtual Network
Switch Protocol", and creates a new network that has all the TCP/IP stuff on
it. Apparently that causes issues with the teamed adapter. (Note also that
you should always leave one network adapter free to connect to the parent
partition for management.)
that when you create an external network in Hyper-V, it removes the TCP/IP
stack from the NIC and replaces it with the "Microsoft Virtual Network
Switch Protocol", and creates a new network that has all the TCP/IP stuff on
it. Apparently that causes issues with the teamed adapter. (Note also that
you should always leave one network adapter free to connect to the parent
partition for management.)
--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel
"Hii Sing Chung" <sing...@sgintracod.com> wrote in message
news:AA40862C-5584-4F59...@microsoft.com...
Hii Sing Chung
Apr 23, 2008, 12:09:27 AM4/23/08
to
I broke the team, restarted. When I tried to configure virtual network as
external, press Apply, it says "Error Applying New Virtual Network Changes.
Setup switch failed. The switch could not bind to HP NC373i Multifunction
Gigabit Server Adapter because it is already bound to another switch." I
tried the second network card, it was the same result. What is the 'switch'
refer to? What is the 'bind' about?
external, press Apply, it says "Error Applying New Virtual Network Changes.
Setup switch failed. The switch could not bind to HP NC373i Multifunction
Gigabit Server Adapter because it is already bound to another switch." I
tried the second network card, it was the same result. What is the 'switch'
refer to? What is the 'bind' about?
"Ryan Sokolowski [MVP]" <ry...@clustering101.com> wrote in message
news:E4994088-5DE5-4D29...@microsoft.com...
Charlie Russel - MVP
Apr 23, 2008, 1:03:13 AM4/23/08
to
The problem is that the Microsoft Virtual Switch protocol has been enabled
on those switches. And once that happens, it's a bit of a nuisance getting
them sorted. I just had to do this on a machine (for a different reason, but
same process.) To resolve it, I did the following:
on those switches. And once that happens, it's a bit of a nuisance getting
them sorted. I just had to do this on a machine (for a different reason, but
same process.) To resolve it, I did the following:
1.) deleted all external networks using the Hyper-V Network Manager
2.) Went in to Device Manager and uninstalled the adapters
3.) Rebooted, letting Windows re-create the adapters.
4.) Re-created the external network using the Hyper-V Network Manager
5.) Fixed the "configuration error" for all VMs that were attached to those
networks by detaching the network, and then re-attaching to the new switch.
"Hii Sing Chung" <sing...@sgintracod.com> wrote in message
news:97BE4A3B-589A-4697...@microsoft.com...
Hii Sing Chung
Apr 23, 2008, 3:48:29 AM4/23/08
to
Right, uninstall all the network adapters, re-start. That did the trick.
"Charlie Russel - MVP" <cha...@mvKILLALLSPAMMERSps.org> wrote in message
news:82F48A60-D54F-4419...@microsoft.com...
Charlie Russel - MVP
Apr 23, 2008, 10:45:43 AM4/23/08
to
Good, glad it got you working.
"Hii Sing Chung" <sing...@sgintracod.com> wrote in message
news:4E43F398-692F-4AD0...@microsoft.com...
Enzo Bastianello
Oct 6, 2011, 10:58:52 AM10/6/11
to
Great... now it work fine
> On Tuesday, April 22, 2008 5:45 AM Hii Sing Chung wrote:
> I am running Windows 2008 Enterprise x64 and had updated the Hyper-V to RC0.
> The server is an HP Proliant DL360 G5 5110 (Xeon 2 Cores), 4GB RAM. I
> configured teaming on the 2 Gigabit NIC (HP NC373i Multifunction Gigabit
> Server Adapter). The Server (the host) has fixed IP address configured. In
> Hyper-V the Virtual Network was default set up as "Private virtual machine
> network". Whenever I changed it to External, and clicked OK or Apply, it
> said "Apply Changes...." and would remains at this state forever. I left it
> running for 2 weeks, it was still like that. I rebuilt the server from
> scratch (re-created the RAID, re-install OS), when I reached the Virtual
> Network Manager and configure the virtual network to External, click OK or
> Apply, it went to the "Apply changes....." endless loop. I am stuck here.
>
> Is this caused by the NIC teaming?
>
> Any idea why?
>>>> On Wednesday, April 23, 2008 12:09 AM Hii Sing Chung wrote:
>>>> I broke the team, restarted. When I tried to configure virtual network as
>>>> external, press Apply, it says "Error Applying New Virtual Network Changes.
>>>> Setup switch failed. The switch could not bind to HP NC373i Multifunction
>>>> Gigabit Server Adapter because it is already bound to another switch." I
>>>> tried the second network card, it was the same result. What is the 'switch'
>>>> refer to? What is the 'bind' about?
>>>>
>>>> "Ryan Sokolowski [MVP]" <ry...@clustering101.com> wrote in message
>>>> news:E4994088-5DE5-4D29...@microsoft.com...
> On Tuesday, April 22, 2008 5:45 AM Hii Sing Chung wrote:
> I am running Windows 2008 Enterprise x64 and had updated the Hyper-V to RC0.
> The server is an HP Proliant DL360 G5 5110 (Xeon 2 Cores), 4GB RAM. I
> configured teaming on the 2 Gigabit NIC (HP NC373i Multifunction Gigabit
> Server Adapter). The Server (the host) has fixed IP address configured. In
> Hyper-V the Virtual Network was default set up as "Private virtual machine
> network". Whenever I changed it to External, and clicked OK or Apply, it
> said "Apply Changes...." and would remains at this state forever. I left it
> running for 2 weeks, it was still like that. I rebuilt the server from
> scratch (re-created the RAID, re-install OS), when I reached the Virtual
> Network Manager and configure the virtual network to External, click OK or
> Apply, it went to the "Apply changes....." endless loop. I am stuck here.
>
> Is this caused by the NIC teaming?
>
> Any idea why?
>> On Tuesday, April 22, 2008 9:56 AM Ryan Sokolowski [MVP] wrote:
>> Break the NIC team and try this again.
>>
>> --
>> Ryan Sokolowski
>> MVP - Clustering
>> MCSE, CCNA, CCDA, BCFP
>> Break the NIC team and try this again.
>>
>> --
>> Ryan Sokolowski
>> MVP - Clustering
>> MCSE, CCNA, CCDA, BCFP
>>> On Tuesday, April 22, 2008 10:24 AM Charlie Russel - MVP wrote:
>>> I'd agree with Ryan, this is probably from the NIC teaming. The issue is
>>> that when you create an external network in Hyper-V, it removes the TCP/IP
>>> stack from the NIC and replaces it with the "Microsoft Virtual Network
>>> Switch Protocol", and creates a new network that has all the TCP/IP stuff on
>>> it. Apparently that causes issues with the teamed adapter. (Note also that
>>> you should always leave one network adapter free to connect to the parent
>>> partition for management.)
>>>
>>>
>>> I'd agree with Ryan, this is probably from the NIC teaming. The issue is
>>> that when you create an external network in Hyper-V, it removes the TCP/IP
>>> stack from the NIC and replaces it with the "Microsoft Virtual Network
>>> Switch Protocol", and creates a new network that has all the TCP/IP stuff on
>>> it. Apparently that causes issues with the teamed adapter. (Note also that
>>> you should always leave one network adapter free to connect to the parent
>>> partition for management.)
>>>
>>>
>>> --
>>> Charlie.
>>> http://msmvps.com/blogs/xperts64
>>> http://mvp.support.microsoft.com/profile/charlie.russel
>>>
>>>
>>> "Hii Sing Chung" <sing...@sgintracod.com> wrote in message
>>> news:AA40862C-5584-4F59...@microsoft.com...
>>> Charlie.
>>> http://msmvps.com/blogs/xperts64
>>> http://mvp.support.microsoft.com/profile/charlie.russel
>>>
>>>
>>> "Hii Sing Chung" <sing...@sgintracod.com> wrote in message
>>>> On Wednesday, April 23, 2008 12:09 AM Hii Sing Chung wrote:
>>>> I broke the team, restarted. When I tried to configure virtual network as
>>>> external, press Apply, it says "Error Applying New Virtual Network Changes.
>>>> Setup switch failed. The switch could not bind to HP NC373i Multifunction
>>>> Gigabit Server Adapter because it is already bound to another switch." I
>>>> tried the second network card, it was the same result. What is the 'switch'
>>>> refer to? What is the 'bind' about?
>>>>
>>>> "Ryan Sokolowski [MVP]" <ry...@clustering101.com> wrote in message
>>>> news:E4994088-5DE5-4D29...@microsoft.com...
>>>>> On Wednesday, April 23, 2008 1:03 AM Charlie Russel - MVP wrote:
>>>>> The problem is that the Microsoft Virtual Switch protocol has been enabled
>>>>> on those switches. And once that happens, it's a bit of a nuisance getting
>>>>> them sorted. I just had to do this on a machine (for a different reason, but
>>>>> same process.) To resolve it, I did the following:
>>>>>
>>>>> 1.) deleted all external networks using the Hyper-V Network Manager
>>>>> 2.) Went in to Device Manager and uninstalled the adapters
>>>>> 3.) Rebooted, letting Windows re-create the adapters.
>>>>> 4.) Re-created the external network using the Hyper-V Network Manager
>>>>> 5.) Fixed the "configuration error" for all VMs that were attached to those
>>>>> networks by detaching the network, and then re-attaching to the new switch.
>>>>>
>>>>> --
>>>>> Charlie.
>>>>> http://msmvps.com/blogs/xperts64
>>>>> http://mvp.support.microsoft.com/profile/charlie.russel
>>>>>
>>>>>
>>>>> "Hii Sing Chung" <sing...@sgintracod.com> wrote in message
>>>>> news:97BE4A3B-589A-4697...@microsoft.com...
>>>>> The problem is that the Microsoft Virtual Switch protocol has been enabled
>>>>> on those switches. And once that happens, it's a bit of a nuisance getting
>>>>> them sorted. I just had to do this on a machine (for a different reason, but
>>>>> same process.) To resolve it, I did the following:
>>>>>
>>>>> 1.) deleted all external networks using the Hyper-V Network Manager
>>>>> 2.) Went in to Device Manager and uninstalled the adapters
>>>>> 3.) Rebooted, letting Windows re-create the adapters.
>>>>> 4.) Re-created the external network using the Hyper-V Network Manager
>>>>> 5.) Fixed the "configuration error" for all VMs that were attached to those
>>>>> networks by detaching the network, and then re-attaching to the new switch.
>>>>>
>>>>> --
>>>>> Charlie.
>>>>> http://msmvps.com/blogs/xperts64
>>>>> http://mvp.support.microsoft.com/profile/charlie.russel
>>>>>
>>>>>
>>>>> "Hii Sing Chung" <sing...@sgintracod.com> wrote in message
>>>>> news:97BE4A3B-589A-4697...@microsoft.com...
>>>>>> On Wednesday, April 23, 2008 3:48 AM Hii Sing Chung wrote:
>>>>>> Right, uninstall all the network adapters, re-start. That did the trick.
>>>>>> Right, uninstall all the network adapters, re-start. That did the trick.
0 new messages