Sent: 11/02/2006
From: Troy
Message:Patrick,
We tried naming the NICs the same but it didn't matter. We even tried to
use the clustr PUBLIC NIC (labeled "Public") on each server but no luck.
We're stumped.
Troy
"patrick" wrote:
Show quoted text
> Maybe this is diffrent, I don't have clustering setup, but when I
> physically move my VHD/VMC files for a Virtual Server from one server
> to ther other the NICS will attach right back up fine as long as they
> are named the same on both host servers... Might this be applicable to
> you as well? Try just nameing them the same and see if it helps...
>
> Maybe I'm not understanding your question fully...
>
>
> Troy wrote:
> > We're setting up a 2 node/host MSCS for Virtual server 2005 R2 - we've found
> > that the .vnc file does not map nicely to the physical NICs on each server.
> > If we use NIC adapter #3 in one host the Virtual .vnc file maps it to a
> > different NIC on the other host (in our case the private NIC on the other
> > host) which was no good? Does anyone know what perameter in the .vnc file
> > that Virtual server uses to map to the physical NIC on each host? This can
> > be a real pain when failing to the other host. As a work around we had to
> > test each NIC from one host and see which NIC matched on the other host -
> > then we had to change all the NIC settings on the second host (public &
> > private) so that failover would work. Seems that it should work like UNIX by
> > device number but it doesn't seem to be the case???
>
>
Sent: 11/02/2006
From: "Stefano Colombo" <(email address - cut out)>
Message:I'm doing the same setup with blades .
I named all the NICs the same and the failover works perfectly . Strange
enough on another pair of blades, configured as the first, I'm experiencing
your sam problem
"patrick" <(email address - cut out)> wrote in message
news:(email address - cut out)...
Show quoted text
> Maybe this is diffrent, I don't have clustering setup, but when I
> physically move my VHD/VMC files for a Virtual Server from one server
> to ther other the NICS will attach right back up fine as long as they
> are named the same on both host servers... Might this be applicable to
> you as well? Try just nameing them the same and see if it helps...
>
> Maybe I'm not understanding your question fully...
>
>
> Troy wrote:
>> We're setting up a 2 node/host MSCS for Virtual server 2005 R2 - we've
>> found
>> that the .vnc file does not map nicely to the physical NICs on each
>> server.
>> If we use NIC adapter #3 in one host the Virtual .vnc file maps it to a
>> different NIC on the other host (in our case the private NIC on the other
>> host) which was no good? Does anyone know what perameter in the .vnc
>> file
>> that Virtual server uses to map to the physical NIC on each host? This
>> can
>> be a real pain when failing to the other host. As a work around we had
>> to
>> test each NIC from one host and see which NIC matched on the other host -
>> then we had to change all the NIC settings on the second host (public &
>> private) so that failover would work. Seems that it should work like
>> UNIX by
>> device number but it doesn't seem to be the case???
>
Sent: 12/07/2006
From: "Bert"<(email address - cut out)>
Message:
I experienced the same problem to solution for me was to modify the file "C:\Documents and Settings\All Users\Application Data\Microsoft\Virtual Server\Options.xml" This file lists the networkadapters and their corresponding integer values. If these don’t match failover will select the wrong NIC. Stop Virtual Server to modify this file if necessary.
hope it helps!
Rgds,
Bert
Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com
Show quoted text
> We're setting up a 2 node/host MSCS for Virtual server 2005 R2 - we've found
> that the .vnc file does not map nicely to the physical NICs on each server.
> If we use NIC adapter #3 in one host the Virtual .vnc file maps it to a
> different NIC on the other host (in our case the private NIC on the other
> host) which was no good? Does anyone know what perameter in the .vnc file
> that Virtual server uses to map to the physical NIC on each host? This can
> be a real pain when failing to the other host. As a work around we had to
> test each NIC from one host and see which NIC matched on the other host -
> then we had to change all the NIC settings on the second host (public &
> private) so that failover would work. Seems that it should work like UNIX by
> device number but it doesn't seem to be the case???
Wiki