Shared nothing live migration wrong network

Hey,
I have a problem when doing shared nothing live migration between clusters using SCVMM 2012 R2.
The transfer goes ok. But It choose to use my team of 2 x 1GB nic (routable) instead of the team with 2x10GB (non routable, but opened between all hosts).
I have set vmmigrationsubnet to correct net. Check live migration setting, and that port 6600 is listening on the correct IP.
But still it chooses to use the 1GB net.
Anyone got any idea what I can do next?
//Johan Runesson

Do you have only your live migration network defined as such on the clusters or do you have both defined? What are the IP networks on the live migration networks on each cluster?
.:|:.:|:. tim

Similar Messages

Hyper-V replica vs Shared Nothing Live Migration

Shared Nothing Live Migration allows to transport your VM over the WAN without shutting it down (how much time it takes on io intensive vm is another story)
  Hyper-V replica does not allow to perform the DR switch without shutdown operation on primary site VM !
why can't it take the VM live to the DR ?
that's because if we use Shared Nothing across the WAN, we don't use the data that Hyper-V replica can and then it also breaks everything hyper-V replica does.
Point is: how to take the VM to DR in running state, what is the best way to do that ?
Shahid Roofi

Hi Shahid,
Hyper-V Replica is designed as a DR technology, not as a technique to move VMs. It assumes that should you require it, the source VM would probably be offline and therefore you would be powering up the passive copy from a previous point in time
as its not a true synchronous replica copy. It does give you the added benefit to be able to run a planned failover which as you say, powers of the VM first, runs a final Sync then powers the new VM up. Obviously you cant have the duplicate copy of this VM
running all the time at the remote site, otherwise you would have a split brain situation for network traffic.
Like the live migration the shared nothing live migration is a technology aimed at moving a VM, but as you know offers the ability to do this without having shared storage and only requires a network connection. When initiated moves the whole
VM, well copies the virtual drive and memory before sending machine writes to both, then only to the new VM when they both match. With regards to the speed, I assume you have the SNLM setup to compress data before sending across the wire?
If you want a true live migration between remote sites, one way would be to have a SAN array between both sites synchronously replicating data, then stretch the Hyper-V cluster across both sites. Obviously this is a very expensive solution but perhaps
the perfect scenario.
Kind Regards
Michael Coutanche
Blog:
Twitter:   LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Shared nothing live migration over SMB. Poor performance

Hi,
I´m experiencing really poor performance when migrating VMs between newly installed server 2012 R2 Hyper-V hosts.
Hardware:
Dell M620 blades
256Gb RAM
2*8C Intel E5-2680 CPUs
Samsung 840 Pro 512Gb SSD running in Raid1
6* Intel X520 10G NICs connected to Force10 MXL enclosure switches
The NICs are using the latest drivers from Intel (18.7) and firmware version 14.5.9
The OS installation is pretty clean. Its Windows Server 2012 R2 + Dell OMSA + Dell HIT 4.6
I have removed the NIC teams and vmSwitch/vNICs to simplify the problem solving process. Now there is one nic configured with one IP. RSS is enabled, no VMQ.
The graphs are from 4 tests.
Test 1 and 2 are nttcp-tests to establish that the network is working as expected.
Test 3 is a shared nothing live migration of a live VM over SMB
Test 4 is a storage migration of the same VM when shut down. The VMs is transferred using BITS over http.
It´s obvious that the network and NICs can push a lot of data. Test 2 had a throughput of 1130MB/s (9Gb/s) using 4 threads. The disks can handle a lot more than 74MB/s, proven by test 4.
While the graph above doesn´t show the cpu load, I have verified that no cpu core was even close to running at 100% during test 3 and 4.
Any ideas?
Test
Config
Vmswitch
RSS
VMQ
Live Migration Config
Throughput (MB/s)
NTtcp
NTttcp.exe -r -m 1,*,172.17.20.45 -t 30
No
Yes
No
N/A
500
NTtcp
NTttcp.exe -r -m 4,*,172.17.20.45 -t 30
No
Yes
No
N/A
1130
Shared nothing live migration
Online VM, 8GB disk, 2GB RAM. Migrated from host 1 -> host2
No
Yes
No
Kerberos, Use SMB, any available net
74
Storage migration
Offline VM, 8Gb disk. Migrated from host 1 -> host2
No
Yes
No
Unencrypted BITS transfer
350

Hi Per Kjellkvist,
Please try to change the "advanced features"settings of "live migrations" in "Hyper-v settings" , select "Compression" in "performance options" area .
Then test 3 and 4 .
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.

Win 2012 shared-nothing live migration slow performance

Win 2012 shared-nothing live migration slow performance
Hello,
i have two standalone hyper-v servers - A) 2012 and B) 2012 r2.
I tried live migration on non-shared storage between them. The functionality is alright but performance is low. The copying take a long time with max 200 Mbps.
I am not able to find the bottleneck. Network a disk performance seems to be good. It is 1Gbps network and when I tried simple copy paste the vhd file from A to B through cifs protocol, the speed was about almost full 1Gbps - it was nice and fast.
Is it feature? I am not able reach full network performance with shared-nothing live migration.
Thank you for reply
sincerely
Peter Weiss

Hi,
I don’t found the similar issue with Hyper-V, Does both of your hosts have the chipsets in the same family? Could you try to switch the three Live Migration Performance
Option method then monitor again? Or It seems there may have some disk or file system performance issue, please try to update your RAID card firmware to the least version.
More information:
Shared Nothing Live Migration: Goodbye Shared Storage?
http://blogs.technet.com/b/canitpro/archive/2013/01/03/shared-nothing-live-migration-goodbye-shared-storage.aspx
How to: Copy very large files across a slow or unreliable network
http://blogs.msdn.com/b/granth/archive/2010/05/10/how-to-copy-very-large-files-across-a-slow-or-unreliable-network.aspx
The similar thread:
How to determine when to use the xcopy with the /j parameter?
http://social.technet.microsoft.com/Forums/en-US/5ebfc25a-41c8-4d82-a2a6-d0f15d298e90/how-to-determine-when-to-use-the-xcopy-with-the-j-parameter?forum=winserverfiles
Hope this helps

Slow migration rates for shared-nothing live migration over teaming NICs

I'm trying to increase the migration/data transfer rates for shared-nothing live migrations (i.e., especially the storage migration part of the live migration) between two Hyper-V hosts. Both of these hosts have a dedicated teaming interface (switch-independent,
dynamic) with two 1GBit/s NICs which is used for only for management and transfers. Both of the NICs for both hosts have RSS enabled (and configured), and the teaming interface also shows RSS enabled, as does the corresponding output from Get-SmbMultichannelConnection).
I'm currently unable to see data transfers of the physical volume of more than around 600-700 MBit/s, even though the team is able to saturate both interfaces with data rates going close to the 2GBit/s boundary when transferring simple files over SMB. The
storage migration seems to use multichannel SMB, as I am able to see several connections all transferring data on the remote end.
As I'm not seeing any form of resource saturation (neither the NIC/team is full, nor is a CPU, nor is the storage adapter on either end), I'm slightly stumped that live migration seems to have a built-in limit to 700 MBit/s, even over a (pretty much) dedicated
interface which can handle more traffic when transferring simple files. Is this a known limitation wrt. teaming and shared-nothing live migrations?
Thanks for any insights and for any hints where to look further!

Compression is not configured on the live migrations (but rather it's set to SMB), but as far as I understand, for the storage migration part of the shared-nothing live migration this is not relevant anyway.
Yes, all NICs and drivers are at their latest version, and RSS is configured (as also stated by the corresponding output from Get-SmbMultichannelConnection, which recognizes RSS on both ends of the connection), and for all NICs bound to the team, Jumbo Frames
(9k) have been enabled and the team is also identified with 9k support (as shown by Get-NetIPInterface).
As the interface is dedicated to migrations and management only (i.e., the corresponding Team is not bound to a Hyper-V Switch, but rather is just a "normal" Team with IP configuration), Hyper-V port does not make a difference here, as there are
no VMs to bind to interfaces on the outbound NIC but just traffic from the Hyper-V base system.
Finally, there are no bandwidth weights and/or QoS rules for the migration traffic bound to the corresponding interface(s).
As I'm able to transfer close to 2GBit/s SMB traffic over the interface (using just a plain file copy), I'm wondering why the SMB(?) transfer of the disk volume during shared-nothing live migration is seemingly limited to somewhere around 700 MBit/s on the
team; looking at the TCP-connections on the remote host, it does seem to use multichannel SMB to copy the disk, but I might be mistaken on that.
Are there any further hints or is there any further information I might offer to diagnose this? I'm currently pretty much stumped on where to go on looking.

Hyper-V 2012 R2 VMQ live migrate (shared nothing) Blue Screen

Hello,
Have Windows Server 2012 R2 Hyper-V server, fully patched, new install. There are two intel Network cards ant there is configured NIC team of them (Windows NIC teaming). Also there is some "Virtual" NICS with assigned VLAN ID.
If I enable VMQ on these NICS and do shared nothing live migration of VM - host gets BSDO. What can be wrong?

Hi,
I would like to check if you need further assistance.
Thanks.
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.

RDS 2012 re-connection after live migration.

Is there a way to speed up the re-connection after a live migration?
So if i am in a vm that live migrates it feels like it hangs for about 10 seconds the reconnects and is fine..... While this is OK its not ideal. Is there a way to improve this?

Actually 10 seconds sounds like a very long time to me. In my experience using Shared Nothing Live Migration I've seen the switch being almost instantaneous, with a continual ping possibly dropping one or two packets, and certainly quick enough that it's
unlikely any users would notice the change. So in terms of whether it can be improved I'd say yes.
As you can see from the technical overview here
http://technet.microsoft.com/en-us/library/hh831435.aspx the final step is for a signal to be sent to the switch informing it of the new MAC address of the servers new destination, so I wonder if the slow switch over might be connected to that, or perhaps
some other network issue.
Is the network connection poor between the servers which might cause a delay during the final sync of changes between the server copies? Are you moving between subnets?

Hyper V Lab and Live Migration

Hi Guys,
I have 2 Hyper V hosts I am setting up in a lab environment. Initially, I successfully setup a 2 node cluster with CSVs which allowed me to do Live Migrations.
The problem I have is my shared storage is a bit of a cheat as I have one disk assigned in each host and each host has starwinds virtual SAN installed. The hostA has an iscsi connection to hostB storage and visa versa.
The issue this causes is when the hosts shutdown (because this is a lab its only on when required), the cluster is in a mess when it starts up eg VMs missing etc. I can recover from it but it takes time. I tinkered with the HA settings and the VM settings
so they restarted/ didnt restart etc but with no success.
My question is can I use something like SMB3 shared storage on one of the hosts to perform live migrations but without a full on cluster? I know I can do Shared Nothing Live Migrations but this takes time.
Any ideas on a better solution (rather than actually buying proper shared storage ;-) ) Or if shared storage is the only option to do this cleanly, what would people recommend bearing in mind I have SSDs in the hyper V hosts.
Hope all that makes sense

Hi Sir,
>>I have 2 Hyper V hosts I am setting up in a lab environment. Initially, I successfully setup a 2 node cluster with CSVs which allowed me to do Live Migrations.
As you mentioned , you have 2 hyper-v host and use starwind to provide ISCSI target (this is same as my first lab environment ) , then I realized that I need one or more host to simulate more production scenario .
But ,if you have more physical computers you may try other's progects .
Also please refer to this thread :
https://social.technet.microsoft.com/Forums/windowsserver/en-US/e9f81a9e-0d50-4bca-a24d-608a4cce20e8/2012-r2-hyperv-cluster-smb-30-sofs-share-permissions-issues?forum=winserverhyperv
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.

Live Migration Failure

I am attempting to migrate virtual machines from one site to another but they are failing. I have sufficient bandwidth but am concerned about the latency. Can anyone recommend the maximum latency between the two sites?

Hi Sir,
I assume it is shared nothing live migration .
I would suggest you to perform live migration inside each site to check if the configuration is OK.
If live migration run successfully within local site , you may need to check the link layer between two sites .
During live migration you also can use netmon.exe to analyse the traffic to find some useful information.
In addition , please check the evet log of hyper-v host to check if there is any clue .
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Live Migration and private network

Is it a best practice to put up a Private Network beetween the nodes in a pool (reserving a few network cards and switch ports for it), to have a dedicated network for the traffic generated e.g. by live migration and/or ocfs2 heartbeat? I was wondering why such setup is generally recommended in other virtualization solutions, but apparently it's not considered strictly necessary in OVM... Why? Are there any docs regarding this? I couldn't find any.
Thanks!

Hi Roynor,
regarding the physical separation beetween management+hypervisor and the guest VMs, it's now implemented and working...
My next doubt on the list of doubts :-) at this point is:
I could easily set up ONE MORE dedicated bond, create a Bridge with a private IP on it on each server (e.g. 10.xxx.xxx.xxx), and then create a Private VLAN completely insulated from the rest of the world.
I'd be putting the physical switch ports where the Private Bonds/Bridges belong to on the same VLAN ID.
But:
- How can I be sure that this network WILL be actually used by the relevant traffic? If I'm not wrong, when you set up e.g. a physical RAC cluster, at a certain point you are prompted to choose what network to use for the Heartbeat (and it will be marked as PRIVATE), and what network will be used by clients traffic (PUBLIC).
In Oracle VM such setting does not exist... Neither during installation, nor in VM Manager, nowhere.
- Apart from Security, I'm doubting that during heavy VMs migration problems could arise, because if the network gets saturated, there are chances that the OCFS2 heartbeat would be somehow "lost", therefore messing up HA etc. This is at least the reason why in a RAC setup a private network is highly recommended.
- I finally found that doc you mention from IBM (thanks for pointing it out!) but my opinion is that THEIR INTENTION was to separate the traffic at the same way I'd like to, but there is simply NO PROOF that such setup would work... They do not mention where you can specify what traffic you want to be on what network...
This is a very important point... I'm wondering why this lack of information.
Thanks for your feedback, btw
Edited by: rlomba on Dec 17, 2009 6:16 AM

Hyper-v 2012 r2 slow throughputs on network / live migrations

Hi, maybe someone can point me in the right direction, I have 10 servers 5 Dell r210s and 5 Dell R320's, I have basically converted these servers to standalone hyper-v 2012 servers, so there is no clustering on any at the moment.
Each server is configured with 2 1Gb nics teamed via a virtual switch, now when I copt files between server 1 and 2 for example I see 100MBs throughput, but if I copy a file to server 3 at the same time the file copy load splits the 100MBs throughput between
the 2 copy processes. I was under the impression if I copied 2 files to 2 totally different servers the load would basically be split across the 2 nics effectively giving me 2Gbs throughput but this does not seem to be the case. I have played around with tcpip
large send offloads, jumbo packets, disabled vmq on the cards, they are broadcoms. :-( but it doesn't really seem to make a difference with all of these settings.
The other issue is If I live migrate a 12Gb vm machine running only 2gb ram, effectively just an o/s it takes between 15 to 20 minutes to migrate, I have played around with the advanced settings, smb, compression, tcpip not real game changers, BUT if I shut
town the vm and migrate it, it takes, just under 3 and a half minutes to move across.
I am really stumped here, I am busy in a test phase of hyper-v but cant find any definitive documents relating to this stuff.

Hi Mark,
The servers (hyper-v 2012 r2) are all basically configured with ssvmm2012R2 where they all have teamed 1Gb pNics, into a virtual switch, then there are vNics for the Vmcloud, live migration etc. The physical network is 2 Netgear Gs724T switches which
are interlinked and each servers 1st nic is plugged into the switch1 and the second nic is plugged into the switch2.See Below Image) The hyper-v port is set to independent Hyper-v load balancing.
The R320 servers are running raid 5 sas drives, the R210s have 1Tb drives mirrored. The servers all are using DAS storage, we have not moved to looking at using iscsi and san is out the question at the moment.
I am currently testing between 2x 320s and 2x R210s, I am not copying data to the vm's yets, I am basically testing the transfer between the actual hosts at the moment by copying a 4Gb file manually, After testing the live migrations I decided to test to
see the transfer rates between the servers first, I have been playing around with the offload settings and rss, what I don't understand is yesterday, the copy between the servers was running up to 228Mbs ie (using both nics) when copying
the file between the servers, and then a few hours later it only was copying at 50/60Mbs, but its now back at 113Mbs seemingly to be only using one nic.
I was under the impression if you copy a file between 2 servers the nicks could use the 2gb bandwidth, but after reading many posts they say only one nic, so how did the copies get up to 2Gb yesterday. Then again if you copy files between 3 servers, then
each copy would use one nic, basically giving you 2Gbs, but this is again not being seen.
Regards Keith

When setting up converged network in VMM cluster and live migration virtual nics not working

Hello Everyone,
I am having issues setting up converged network in VMM. I have been working with MS engineers to no avail. I am very surprised with the expertise of the MS engineers. They had no idea what a converged network even was. I had way more
experience then these guys and they said there was no escalation track so I am posting here in hopes of getting some assistance.
Everyone including our consultants says my setup is correct.
What I want to do:
I have servers with 5 nics and want to use 3 of the nics for a team and then configure cluster, live migration and host management as virtual network adapters. I have created all my logical networks, port profile with the uplink defined as team and
networks selected. Created logical switch and associated portprofle. When I deploy logical switch and create virtual network adapters the logical switch works for VMs and my management nic works as well. Problem is that the cluster and live
migration virtual nics do not work. The correct Vlans get pulled in for the corresponding networks and If I run get-vmnetworkadaptervlan it shows cluster and live migration in vlans 14 and 15 which is correct. However nics do not work at all.
I finally decided to do this via the host in powershell and everything works fine which means this is definitely an issue with VMM. I then imported host into VMM again but now I cannot use any of the objects I created and VMM and have to use standard
switch.
I am really losing faith in VMM fast.
Hosts are 2012 R2 and VMM is 2012 R2 all fresh builds with latest drivers
Thanks

Have you checked our whitepaper http://gallery.technet.microsoft.com/Hybrid-Cloud-with-NVGRE-aa6e1e9a for how to configure this through VMM?
Are you using static IP address assignment for those vNICs?
Are you sure your are teaming the correct physical adapters where the VLANs are trunked through the connected ports?
Note; if you create the teaming configuration outside of VMM, and then import the hosts to VMM, then VMM will not recognize the configuration.
The details should be all in this whitepaper.
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

Live Migrating Virtual Machines with Shared VHDx

I am facing problems when live migrating a Virtual Machine that is using Shared VHDx. The Virtual Machine gets migrated that is the configuration gets migrated, but the Virtual Machine fails to start up and if manually tried, it fails too.
What is the method to to live migrate virtual machines that are using Shared VHDx. Thanks in advance.

Another couple of gotchas:
You cannot do host-level backups of the guest cluster. This is the same as it always was. You will have to install backup agents in the guest cluster nodes and back them up as if they were physical machines.
You cannot perform a hot-resize of the shared VHDX. But you can hot-add more shared VHDX files to the clustered VMs.
You cannot Storage Live Migrate the shared VHDX file. You can move the other VM files and perform normal Live Migration.
as Long as you have your shared VHDx on a SMB3 Share you also could have the Nodes of the Guest Cluster on different Hyper-V Hosts.

Server 2012 cluster - virtual machine live migration does not work

Hi,
We have a hyper-v cluster with two nodes running Windows Server 2012. All the configurations are identical.
When I try to make a Live migration from one node to the other I get an error message saying:
Live migration of 'Virtual Machine XXXXXX' failed.
I get no other error messages, not even in event viewer. This same happens with all of our virtual machines.
A normal Quick migration works just fine for all of the virtual machines, so network configuration should not be an issue.
The above error message does not provide much information.

Hi,
Please check whether your configuration meet live migration requirement:
Two (or more) servers running Hyper-V that:
Support hardware virtualization.
Yes they support virtualization.
Are using processors from the same manufacturer (for example, all AMD or all Intel).
Both Servers are identical and brand new Fujitsu-Siemens RX300S7 with the same kind of processor (Xeon E5-2620).
Belong to either the same Active Directory domain, or to domains that trust each other.
Both nodes are in the same domain.
Virtual machines must be configured to use virtual hard disks or virtual Fibre Channel disks (no physical disks).
All of the vitual machines have virtual hard disks.
Use of a private network is recommended for live migration network traffic.
Have tried this, but does not help.
Requirements for live migration in a cluster:
Windows Failover Clustering is enabled and configured.
Yes
Cluster Shared Volume (CSV) storage in the cluster is enabled.
Yes
Requirements for live migration using shared storage:
All files that comprise a virtual machine (for example, virtual hard disks, snapshots, and configuration) are stored on an SMB share. They are all on the same CSV
Permissions on the SMB share have been configured to grant access to the computer accounts of all servers running Hyper-V.
Requirements for live migration with no shared infrastructure:
No extra requirements exist.
Also please refer to this article to check whether you have finished all preparation works for live migration:
Virtual Machine Live Migration Overview
http://technet.microsoft.com/en-us/library/hh831435.aspx
Hyper-V: Using Live Migration with Cluster Shared Volumes in Windows Server 2008 R2
http://technet.microsoft.com/en-us/library/dd446679(v=WS.10).aspx
Configure and Use Live Migration on Non-clustered Virtual Machines
http://technet.microsoft.com/en-us/library/jj134199.aspx
Hope this helps!
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Lawrence
TechNet Community Support
I have also read all of the technet articles but can't find anything that could help.

Error 10698 Virtual machine could not be live migrated to virtual machine host

Hi all,
I am running a fail over cluster of
Host:
2 x WS2008 R2 Data Centre
managed by VMM:
VMM 2008 R2
Virtual Host:
1x windows 2003 64bit guest host/virtual machine
I have attempted a live migration through VMM 2008 R2 and im presented withe the following error:
Error (10698)
Virtual machine XXXXX could not be live migrated to virtual machine host xxx-Host01 using this cluster configuration.
(Unspecified error (0x80004005))
What i have found when running the cluster validation:
1 out of the 2 hosts have an error with RPC related to network configuration:
An error occurred while executing the test.
Failed to connect to the service manager on 'xxx-Host02'.
The RPC server is unavailable
However there are no errors or events on host02 that are showing any probelms at all.
In fact the validation report goes on to showing the rest of the configuration information of both cluster hosts as ok.
See below:
List BIOS Information
List BIOS information from each node.
xxx-Host01
Gathering BIOS Information for xxx-Host01
Item Value
Name Phoenix ROM BIOS PLUS Version 1.10 1.1.6
Manufacturer Dell Inc.
SMBios Present True
SMBios Version 1.1.6
SMBios Major Version 2
SMBios Minor Version 5
Current Language en|US|iso8859-1
Release Date 3/23/2008 9:00:00 AM
Primary BIOS True
xxx-Host02
Gathering BIOS Information for xxx-Host02
Item Value
Name Phoenix ROM BIOS PLUS Version 1.10 1.1.6
Manufacturer Dell Inc.
SMBios Present True
SMBios Version 1.1.6
SMBios Major Version 2
SMBios Minor Version 5
Current Language en|US|iso8859-1
Release Date 3/23/2008 9:00:00 AM
Primary BIOS True
Back to Summary
Back to Top
List Cluster Core Groups
List information about the available storage group and the core group in the cluster.
Summary
Cluster Name: xxx-Cluster01
Total Groups: 2
Group Status Type
Cluster Group Online Core Cluster
Available Storage Offline Available Storage
Cluster Group
Description:
Status: Online
Current Owner: xxx-Host01
Preferred Owners: None
Failback Policy: No failback policy defined.
Resource Type Status Possible Owners
Cluster Disk 1 Physical Disk Online All Nodes
IP Address: 10.10.0.60 IP Address Online All Nodes
Name: xxx-Cluster01 Network Name Online All Nodes
Available Storage
Description:
Status: Offline
Current Owner: Per-Host02
Preferred Owners: None
Failback Policy: No failback policy defined.
Cluster Shared Volumes
Resource Type Status Possible Owners
Data Cluster Shared Volume Online All Nodes
Snapshots Cluster Shared Volume Online All Nodes
System Cluster Shared Volume Online All Nodes
Back to Summary
Back to Top
List Cluster Network Information
List cluster-specific network settings that are stored in the cluster configuration.
Network: Cluster Network 1
DHCP Enabled: False
Network Role: Internal and client use
Metric: 10000
Prefix Prefix Length
10.10.0.0 20
Network: Cluster Network 2
DHCP Enabled: False
Network Role: Internal use
Metric: 1000
Prefix Prefix Length
10.13.0.0 24
Subnet Delay
CrossSubnetDelay 1000
CrossSubnetThreshold 5
SameSubnetDelay 1000
SameSubnetThreshold 5
Validating that Network Load Balancing is not configured on node xxx-Host01.
Validating that Network Load Balancing is not configured on node xxx-Host02.
An error occurred while executing the test.
Failed to connect to the service manager on 'xxx-Host02'.
The RPC server is unavailable
Back to Summary
Back to Top
If it was an RPC connection issue, then i shouldnt be able to mstsc, explorer shares to host02. Well i can access them, which makes the report above is a bit misleading.
I have also checked the rpc service and it has started.
If there is anyone that can shed some light or advice me oany other option for trouble shooting this, that would be greatley appreciated.
Kind regards,
Chucky

Hi all,
I am running a fail over cluster of
Host:
2 x WS2008 R2 Data Centre
managed by VMM:
VMM 2008 R2
Virtual Host:
1x windows 2003 64bit guest host/virtual machine
I have attempted a live migration through VMM 2008 R2 and im presented withe the following error:
Error (10698)
Virtual machine XXXXX could not be live migrated to virtual machine host xxx-Host01 using this cluster configuration.
(Unspecified error (0x80004005))
What i have found when running the cluster validation:
1 out of the 2 hosts have an error with RPC related to network configuration:
An error occurred while executing the test.
Failed to connect to the service manager on 'xxx-Host02'.
The RPC server is unavailable
However there are no errors or events on host02 that are showing any probelms at all.
In fact the validation report goes on to showing the rest of the configuration information of both cluster hosts as ok.
See below:
List BIOS Information
List BIOS information from each node.
xxx-Host01
Gathering BIOS Information for xxx-Host01
Item Value
Name Phoenix ROM BIOS PLUS Version 1.10 1.1.6
Manufacturer Dell Inc.
SMBios Present True
SMBios Version 1.1.6
SMBios Major Version 2
SMBios Minor Version 5
Current Language en|US|iso8859-1
Release Date 3/23/2008 9:00:00 AM
Primary BIOS True
xxx-Host02
Gathering BIOS Information for xxx-Host02
Item Value
Name Phoenix ROM BIOS PLUS Version 1.10 1.1.6
Manufacturer Dell Inc.
SMBios Present True
SMBios Version 1.1.6
SMBios Major Version 2
SMBios Minor Version 5
Current Language en|US|iso8859-1
Release Date 3/23/2008 9:00:00 AM
Primary BIOS True
Back to Summary
Back to Top
List Cluster Core Groups
List information about the available storage group and the core group in the cluster.
Summary
Cluster Name: xxx-Cluster01
Total Groups: 2
Group Status Type
Cluster Group Online Core Cluster
Available Storage Offline Available Storage
Cluster Group
Description:
Status: Online
Current Owner: xxx-Host01
Preferred Owners: None
Failback Policy: No failback policy defined.
Resource Type Status Possible Owners
Cluster Disk 1 Physical Disk Online All Nodes
IP Address: 10.10.0.60 IP Address Online All Nodes
Name: xxx-Cluster01 Network Name Online All Nodes
Available Storage
Description:
Status: Offline
Current Owner: Per-Host02
Preferred Owners: None
Failback Policy: No failback policy defined.
Cluster Shared Volumes
Resource Type Status Possible Owners
Data Cluster Shared Volume Online All Nodes
Snapshots Cluster Shared Volume Online All Nodes
System Cluster Shared Volume Online All Nodes
Back to Summary
Back to Top
List Cluster Network Information
List cluster-specific network settings that are stored in the cluster configuration.
Network: Cluster Network 1
DHCP Enabled: False
Network Role: Internal and client use
Metric: 10000
Prefix Prefix Length
10.10.0.0 20
Network: Cluster Network 2
DHCP Enabled: False
Network Role: Internal use
Metric: 1000
Prefix Prefix Length
10.13.0.0 24
Subnet Delay
CrossSubnetDelay 1000
CrossSubnetThreshold 5
SameSubnetDelay 1000
SameSubnetThreshold 5
Validating that Network Load Balancing is not configured on node xxx-Host01.
Validating that Network Load Balancing is not configured on node xxx-Host02.
An error occurred while executing the test.
Failed to connect to the service manager on 'xxx-Host02'.
The RPC server is unavailable
Back to Summary
Back to Top
If it was an RPC connection issue, then i shouldnt be able to mstsc, explorer shares to host02. Well i can access them, which makes the report above is a bit misleading.
I have also checked the rpc service and it has started.
If there is anyone that can shed some light or advice me oany other option for trouble shooting this, that would be greatley appreciated.
Kind regards,
Chucky
Raja. B

Shared nothing live migration wrong network

Similar Messages

Maybe you are looking for