ASP Developer Network - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com

ASPDeveloper

ASPDeveloper.Net / VirtualServerFAQ.COM

Make sure you go to our home page for:

* Virtual Server 2005 FAQ
* ASP.Net 2.0 Information
* ASP.Net 2.0 Streaming Tutorials
* ASP.Net 2.0 HTML based Tutorials

Made possible by Business Internet Technology Shop (BitShop)

Virtual Server 2005

Recent Virtual Server 2005 posts

* snapshot?
* can not get all 4 cores utlitized vs 2005 r2 and 2003
* where can one download VS2005 R2 with SP1?
* Problem with SSL on the Virtual Server Administration Website
* Isolated network between 2 virtual servers
* Problem with network connectivity
* Problem with Mouse after importing the VHD
* linked drives
* Virtual server as a Company Production server - reasonable?
* Smartcard on VirtualServer R2
* IP Address
* vmo not found
* VSMT error
* virtual server isntall and setup
* V2P?
* Ghost Virtual DC
* How to force uninstall of Virtual Machine Additions?
* Server sloowwwwww
* Problems with VS admin website
* Backup of guest system

Add Solution

Problem w/Virtual Server cluster & multiple NICs

Source: microsoft.public.virtualserver
Sent: 04/10/2007
From: Jonathan
Message:

Hello,

I have created a virtual server host cluster on an identical pair of HP
ML370 G5 servers using Windows Server 2003 Enterprise x64. Both servers have
embedded dual-port gigabit interfaces as well as each having an add-on HP
dual-port gigabit NIC; all-in-all providing a total of four gigabit ports per
server. I currently have Virtual Machine Network Services bound to all ports
(more on that in a moment). The problem I am having is that when I fail a
virtual network over from one node to the other, it appears bound to a
different port depending on which machine is the active node.

If I bind Virtual Machine Network Services to only some of the interfaces
(the configuration I prefer to use), I show the following error message on
the virtual network after failover...

"The virtual networkâ€™s configuration information could not be retrieved.
Microsoft Virtual Server could not complete the operation due to an
unexpected error (0x80004005)."

It appears to me that either Virtual Server or Windows is enumerating the
network ports in a different order on each machine. This is confirmed by the
fact that the list of available interfaces show up in a different order when
I go to create a new virtual network on either machine (although the names
are the same on both machines).

I have tried removing Virtual Server, deleting the configuration files and
reinstalling multiple times. I have also tried removing and reinstalling the
drivers/NICs to no avail.

Does anyone have a thought on this?

Does anyone out there have

Post Reply | This is Spam! | Mark as Spam

Related Messages

Re: Problem w/Virtual Server cluster & multiple NICs

Sent: 04/11/2007
From: Jonathan
Message:

Thanks for the reply. I stayed up late last night working on this and
actually found a solution. Virtual Server detects the physical interfaces
when it is installed and stores this information in the "Options.xml" file
found in "C:\Documents and Settings\All Users\Application
Data\Microsoft\Virtual Server". What I found was that for some reason, the
interfaces were enumerated differently on each server even though the
hardware, connection names, network configs, network service bindings/order,
etc were identical, and both machines were built side-by-side.

To fix it, I simply edited the xml file on one server and moved the adapter
tags around, also changing the numerical values of the "TYPE" tags so that
they were the same on both machines. I believe one could even do this if the
interfaces were different models/vendors on each server. I don't even think
the GUID's need to match. I found that they were different in each server's
file but I get no errors now on failover and no loss of connectivity.

I liked your idea of using a DFS share for the .vnc files though and may
give that a try. Also, I'm curious how you resolved the issue of duplicate
MAC addresses.

Thanks again.

-j-

---------------------------
"Stefan Cuypers" wrote:

Show quoted text

> Jonathan,
>
> We have a configuration with 3 HP DL-380 G5 servers, each equipped with 4
> NIC's (2 built-in and 2 on an Add-In card), which should be comparable to
> yours. It works just fine during fail-over.
> Here's what we did:
> - ensure we have exactly the same hardware configuration on all 3 servers
> - renamed the NIC's in Windows identically on all 3 servers (ensuring a NIC
> at the same physical position has the same name on all servers)
> - in the NIC's properties in Virtual Server: also renamed all the NIC's to
> use the same name we assigned in Windows (Virtual Network name), this on all
> 3 servers
> - for each virtual network, we created the virtual network and attached it
> to the correct NIC. Then removed the network again (cfr. Virtual Server
> cluster docu) (on 1 server)
> - we then moved the .vnc files to a local directory C:\ClusterCommonFile. We
> also set up DFS replication to automatically replicate this directory
> between the cluster servers (though I guess you could manually copy the
> files to) (on 1 server)
> - next added the .vnc files from the C:\ClusterCommonFile on all 3 servers
> - We experienced that when adding a .vnc file in Virtual Server, the GUID
> identifying the network is changed. Since this GUID is used to connect a
> virtual machine to a network, all 3 servers should use the same GUID for the
> same network. To achieve this, stop virtual server on all 3 servers and wait
> for DFS replication to replicate the .vnc's to all servers (or if you
> manually copy, ensure the .vnc's are identical on all servers). After that
> restart virtual server and it will use the GUID in the .vnc file, which is
> now the same on all 3 servers.
> - Next start defining the virtual servers themselves.
>
> Note: we are placing the .vnc on a local disk and not on the same cluster
> disk as the virtual machine files. This allows different virtual machines
> using the same network and still failing over independantly to another
> cluster node.
>
> Another note: we were creating all our virtual machines on the same node and
> after creation moved them to the node they would actually run on during
> normal operation. You should not do this though. We experienced duplicate
> MAC addresses doing this when a MAC address got reused after the VM was
> moved to another node (and the move also moved the MAC address)!
>
> regards,
> Stefan Cuypers
>
>
>
> "Jonathan" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Hello,
> >
> > I have created a virtual server host cluster on an identical pair of HP
> > ML370 G5 servers using Windows Server 2003 Enterprise x64. Both servers
> > have
> > embedded dual-port gigabit interfaces as well as each having an add-on HP
> > dual-port gigabit NIC; all-in-all providing a total of four gigabit ports
> > per
> > server. I currently have Virtual Machine Network Services bound to all
> > ports
> > (more on that in a moment). The problem I am having is that when I fail a
> > virtual network over from one node to the other, it appears bound to a
> > different port depending on which machine is the active node.
> >
> > If I bind Virtual Machine Network Services to only some of the interfaces
> > (the configuration I prefer to use), I show the following error message on
> > the virtual network after failover...
> >
> > "The virtual network's configuration information could not be retrieved.
> > Microsoft Virtual Server could not complete the operation due to an
> > unexpected error (0x80004005)."
> >
> > It appears to me that either Virtual Server or Windows is enumerating the
> > network ports in a different order on each machine. This is confirmed by
> > the
> > fact that the list of available interfaces show up in a different order
> > when
> > I go to create a new virtual network on either machine (although the names
> > are the same on both machines).
> >
> > I have tried removing Virtual Server, deleting the configuration files and
> > reinstalling multiple times. I have also tried removing and reinstalling
> > the
> > drivers/NICs to no avail.
> >
> > Does anyone have a thought on this?
> >
> > Does anyone out there have
>
>
>

Re: Problem w/Virtual Server cluster & multiple NICs

Sent: 04/11/2007
From: "Stefan Cuypers" <(email address - cut out)alias>
Message:

Jonathan,

We have a configuration with 3 HP DL-380 G5 servers, each equipped with 4
NIC's (2 built-in and 2 on an Add-In card), which should be comparable to
yours. It works just fine during fail-over.
Here's what we did:
- ensure we have exactly the same hardware configuration on all 3 servers
- renamed the NIC's in Windows identically on all 3 servers (ensuring a NIC
at the same physical position has the same name on all servers)
- in the NIC's properties in Virtual Server: also renamed all the NIC's to
use the same name we assigned in Windows (Virtual Network name), this on all
3 servers
- for each virtual network, we created the virtual network and attached it
to the correct NIC. Then removed the network again (cfr. Virtual Server
cluster docu) (on 1 server)
- we then moved the .vnc files to a local directory C:\ClusterCommonFile. We
also set up DFS replication to automatically replicate this directory
between the cluster servers (though I guess you could manually copy the
files to) (on 1 server)
- next added the .vnc files from the C:\ClusterCommonFile on all 3 servers
- We experienced that when adding a .vnc file in Virtual Server, the GUID
identifying the network is changed. Since this GUID is used to connect a
virtual machine to a network, all 3 servers should use the same GUID for the
same network. To achieve this, stop virtual server on all 3 servers and wait
for DFS replication to replicate the .vnc's to all servers (or if you
manually copy, ensure the .vnc's are identical on all servers). After that
restart virtual server and it will use the GUID in the .vnc file, which is
now the same on all 3 servers.
- Next start defining the virtual servers themselves.

Note: we are placing the .vnc on a local disk and not on the same cluster
disk as the virtual machine files. This allows different virtual machines
using the same network and still failing over independantly to another
cluster node.

Another note: we were creating all our virtual machines on the same node and
after creation moved them to the node they would actually run on during
normal operation. You should not do this though. We experienced duplicate
MAC addresses doing this when a MAC address got reused after the VM was
moved to another node (and the move also moved the MAC address)!

regards,
Stefan Cuypers

"Jonathan" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Hello,
>
> I have created a virtual server host cluster on an identical pair of HP
> ML370 G5 servers using Windows Server 2003 Enterprise x64. Both servers
> have
> embedded dual-port gigabit interfaces as well as each having an add-on HP
> dual-port gigabit NIC; all-in-all providing a total of four gigabit ports
> per
> server. I currently have Virtual Machine Network Services bound to all
> ports
> (more on that in a moment). The problem I am having is that when I fail a
> virtual network over from one node to the other, it appears bound to a
> different port depending on which machine is the active node.
>
> If I bind Virtual Machine Network Services to only some of the interfaces
> (the configuration I prefer to use), I show the following error message on
> the virtual network after failover...
>
> "The virtual network's configuration information could not be retrieved.
> Microsoft Virtual Server could not complete the operation due to an
> unexpected error (0x80004005)."
>
> It appears to me that either Virtual Server or Windows is enumerating the
> network ports in a different order on each machine. This is confirmed by
> the
> fact that the list of available interfaces show up in a different order
> when
> I go to create a new virtual network on either machine (although the names
> are the same on both machines).
>
> I have tried removing Virtual Server, deleting the configuration files and
> reinstalling multiple times. I have also tried removing and reinstalling
> the
> drivers/NICs to no avail.
>
> Does anyone have a thought on this?
>
> Does anyone out there have

Re: Problem w/Virtual Server cluster & multiple NICs

Sent: 04/18/2007
From: "Stefan Cuypers" <(email address - cut out)alias>
Message:

Jonathan,

Thanks for the update.
In fact I did not resolve the issue of the duplicate MAC addresses. I just
avoided it by defining virtual machines on the node they will finally run
on. This ensures MAC addresses stay unique (each node uses it's own range
and checks on virtual machines defined on it to avoid duplicates).
Only thing I need to avoid is to define new virtual machines while we are in
failover (which should be an exceptional situation anyway).
One other consideration: if I move a virtual machine from one node to
another permantently, I shut it down, assign a static MAC address, move it
over to the other node and let it assign a dynamic address again. This
ensure the MAC address comes from that node.

Stefan.

"Jonathan" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Thanks for the reply. I stayed up late last night working on this and
> actually found a solution. Virtual Server detects the physical interfaces
> when it is installed and stores this information in the "Options.xml" file
> found in "C:\Documents and Settings\All Users\Application
> Data\Microsoft\Virtual Server". What I found was that for some reason,
> the
> interfaces were enumerated differently on each server even though the
> hardware, connection names, network configs, network service
> bindings/order,
> etc were identical, and both machines were built side-by-side.
>
> To fix it, I simply edited the xml file on one server and moved the
> adapter
> tags around, also changing the numerical values of the "TYPE" tags so that
> they were the same on both machines. I believe one could even do this if
> the
> interfaces were different models/vendors on each server. I don't even
> think
> the GUID's need to match. I found that they were different in each
> server's
> file but I get no errors now on failover and no loss of connectivity.
>
> I liked your idea of using a DFS share for the .vnc files though and may
> give that a try. Also, I'm curious how you resolved the issue of
> duplicate
> MAC addresses.
>
> Thanks again.
>
> -j-
>
> ---------------------------
> "Stefan Cuypers" wrote:
>
>> Jonathan,
>>
>> We have a configuration with 3 HP DL-380 G5 servers, each equipped with 4
>> NIC's (2 built-in and 2 on an Add-In card), which should be comparable to
>> yours. It works just fine during fail-over.
>> Here's what we did:
>> - ensure we have exactly the same hardware configuration on all 3 servers
>> - renamed the NIC's in Windows identically on all 3 servers (ensuring a
>> NIC
>> at the same physical position has the same name on all servers)
>> - in the NIC's properties in Virtual Server: also renamed all the NIC's
>> to
>> use the same name we assigned in Windows (Virtual Network name), this on
>> all
>> 3 servers
>> - for each virtual network, we created the virtual network and attached
>> it
>> to the correct NIC. Then removed the network again (cfr. Virtual Server
>> cluster docu) (on 1 server)
>> - we then moved the .vnc files to a local directory C:\ClusterCommonFile.
>> We
>> also set up DFS replication to automatically replicate this directory
>> between the cluster servers (though I guess you could manually copy the
>> files to) (on 1 server)
>> - next added the .vnc files from the C:\ClusterCommonFile on all 3
>> servers
>> - We experienced that when adding a .vnc file in Virtual Server, the GUID
>> identifying the network is changed. Since this GUID is used to connect a
>> virtual machine to a network, all 3 servers should use the same GUID for
>> the
>> same network. To achieve this, stop virtual server on all 3 servers and
>> wait
>> for DFS replication to replicate the .vnc's to all servers (or if you
>> manually copy, ensure the .vnc's are identical on all servers). After
>> that
>> restart virtual server and it will use the GUID in the .vnc file, which
>> is
>> now the same on all 3 servers.
>> - Next start defining the virtual servers themselves.
>>
>> Note: we are placing the .vnc on a local disk and not on the same cluster
>> disk as the virtual machine files. This allows different virtual machines
>> using the same network and still failing over independantly to another
>> cluster node.
>>
>> Another note: we were creating all our virtual machines on the same node
>> and
>> after creation moved them to the node they would actually run on during
>> normal operation. You should not do this though. We experienced duplicate
>> MAC addresses doing this when a MAC address got reused after the VM was
>> moved to another node (and the move also moved the MAC address)!
>>
>> regards,
>> Stefan Cuypers
>>
>>
>>
>> "Jonathan" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Hello,
>> >
>> > I have created a virtual server host cluster on an identical pair of HP
>> > ML370 G5 servers using Windows Server 2003 Enterprise x64. Both
>> > servers
>> > have
>> > embedded dual-port gigabit interfaces as well as each having an add-on
>> > HP
>> > dual-port gigabit NIC; all-in-all providing a total of four gigabit
>> > ports
>> > per
>> > server. I currently have Virtual Machine Network Services bound to all
>> > ports
>> > (more on that in a moment). The problem I am having is that when I
>> > fail a
>> > virtual network over from one node to the other, it appears bound to a
>> > different port depending on which machine is the active node.
>> >
>> > If I bind Virtual Machine Network Services to only some of the
>> > interfaces
>> > (the configuration I prefer to use), I show the following error message
>> > on
>> > the virtual network after failover...
>> >
>> > "The virtual network's configuration information could not be
>> > retrieved.
>> > Microsoft Virtual Server could not complete the operation due to an
>> > unexpected error (0x80004005)."
>> >
>> > It appears to me that either Virtual Server or Windows is enumerating
>> > the
>> > network ports in a different order on each machine. This is confirmed
>> > by
>> > the
>> > fact that the list of available interfaces show up in a different order
>> > when
>> > I go to create a new virtual network on either machine (although the
>> > names
>> > are the same on both machines).
>> >
>> > I have tried removing Virtual Server, deleting the configuration files
>> > and
>> > reinstalling multiple times. I have also tried removing and
>> > reinstalling
>> > the
>> > drivers/NICs to no avail.
>> >
>> > Does anyone have a thought on this?
>> >
>> > Does anyone out there have
>>
>>
>>

Post Reply | This is Spam! | Mark as Spam

Other groups

Virtual PC (Mac)(3592)	Virtual PC(12844)	Virtual PC (French)(496)
Virtual Server 2005(6245)

Our Sponsors

Virtual Server 2005 Info Here!
http://www.aspdeveloper.net

Wiki

Blogs

Articles

Image galleries

File galleries

Forums

Maps

Directories

ASP Developer Network (since 1996) - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com
Copyright © 1997-2005 by BitShop, Inc. All Rights Reserved.
No content may be reproduced in any form without written permission from BitShop, Inc.
We will be honored to assist with reproduction rights on our material if you contact us.
We also can provide print articles for your magazine, private training seminars at your site, and conference presentations.
Thank you for visiting. Please bookmark our site if you found it useful!
If you wish to make a donation it will help further the development of these free resources: