Live migration with Fault Tolerance (FT)?

Dose the new version of VM server for SPARC (2.1) have an option for live migration with Fault Tolerance (seemlier to VMware FT)? while live migration is great it dose not protect against a server failure vs something like live migration with FT would makes this seamless.
Thanks,
-Eli

Hi,
Thank you very much.
I tried SiteSurvey Plugin, now i know why it doesn't work
These ESX hosts are not compatible with FT, but may contain VMs that are:
esxi02.vclass.local
CPU type Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz is not supported by FT.

Similar Messages

Live Migration with Different CPU versions on the hosts, win 2012R2 Datacenter

Hello
This question have been asked in different forums but when I read the the thread's I feel that I get mixed answers.
And most answers are dating from 2012 (Win 2008R2), I don't know if they are still correct in win 2012R2.
So now I ask the question myself and hope to get at clear answer :)
We are in the process of installing a new Hyper-V cluster using Win srv 2012 R2 Datacenter as OS.
I'm planning to re-use some of the "old" servers from our current Hyper-V 2008 R2 cluster, removing it from the cluster and do a clean installation of 2012R2 Datacenter.
But I will need to buy two new servers to manage this (with a new version of CPU, same brand (AMD))
Old server: AMD Opteron(tm) Processor 6172 (12 Cores)
New server:
AMD Opteron™ 6344 (12-core)
Now my question:
Will Live Migration work between these servers in my new cluster without me doing any special settings in hyper-v or in the VM or what do I need to do to get this to work?
/Anders

Hi,
It is important that all the hardware supporting Windows Server 2012 Failover Clusters be certified to work with Windows Server 2012.
In a cluster where all the nodes of the cluster are exactly the same, hardware migration is fairly straightforward. There are no concerns about differences in hardware, and
especially no concerns about different capabilities of the CPUs.
More information:
When to Use Processor Compatibility Mode to Migrate Virtual Machines
http://technet.microsoft.com/en-us/magazine/gg299590.aspx
Hope this helps.
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 with zones

Hi all,
I have been reading into making "SPARC Private Cloud" whitepapers with LDOM's from Oracle. One thing really pops out from the text which really confuses me:
from Page 8 and 10:
"VMs may also be securely live migrated or automatically started or restarted across any servers in their respective pools. *Zones are cold migrated*"
"Secure live migration—Move domains off of servers that are undergoing planned maintenance. *Zones are cold-migrated*."
Does this really mean that if I have zones inside LDOM guest, I can live migrate the LDOM guests but not the zones? Hence zones will go down if I do this? If so, whats the reason behind this, its hard to grasp the idea that the OS itself can be live migrated, but not zones inside it that are using the same kernel, binaries etc from it....
Links:
https://blogs.oracle.com/infrared/entry/building_private_iaas_with_sparc
http://www.oracle.com/us/groups/public/@otn/documents/webcontent/1659149.pdf
- Jukka

Lumi, I'm pretty sure they are comparing LDOMs with zones on a standalone system (i.e. no LDOMs).
When you migrate a domain, everything the guest kernel is doing should emerge as it was before.
Migration might take a bit longer than for the GZ alone, since you're using more virtual memory.
To move an NGZ between standalone GZ's, you would indeed have to halt, detach, attach, and boot it.
But please don't take my word for it... feel free to try both methods for yourself. =-)
The only limitation for zones in LDOMs that I'm aware of: You cannot currently set elastic power policy.
Other than that, I don't see why you couldn't keep zones running inside your guest as it moves around.
Hope that helps... -cheers, CSB

Live Migration Fails with error Synthetic FiberChannel Port: Failed to finish reserving resources on an VM using Windows Server 2012 R2 Hyper-V

Hi, I'm currently experiencing a problem with some VMs in a Hyper-V 2012 R2 failover cluster using Fiber Channel adapters with Virtual SAN configured on the hyper-v hosts.
I have read several articles about this issues like this ones:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/baca348d-fb57-4d8f-978b-f1e7282f89a1/synthetic-fibrechannel-port-failed-to-start-reserving-resources-with-error-insufficient-system?forum=winserverhyperv
http://social.technet.microsoft.com/wiki/contents/articles/18698.hyper-v-virtual-fibre-channel-troubleshooting-guide.aspx
But haven't been able to fix my issue.
The Virtual SAN is configured on every hyper-v host node in the cluster. And every VM has 2 fiber channel adapters configured.
All the World Wide Names are configured both on the FC Switch as well as the FC SAN.
All the drivers for the FC Adapter in the Hyper-V Hosts have been updated to their latest versions.
The strange thing is that the issue is not affecting all of the VMs, some of the VMs with FC adapters configured are live migrating just fine, others are getting this error.
Quick migration works without problems.
We even tried removing and creating new FC Adapters on a VM with problems, we had to configure the switch and SAN with the new WWN names and all, but ended up having the same problem.
At first we thought is was related to the hosts, but since some VMs do work live migrating with FC adapters we tried migrating them on every host, everything worked well.
My guess is that it has to be something related to the VMs itself but I haven't been able to figure out what is it.
Any ideas on how to solve this is deeply appreciated.
Thank you!
Eduardo Rojas

Hi Eduardo,
How are things going ?
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.

What is the difference with 1 Lync Standard Edition using VMware Fault Tolerant and 2 Lync Enterprise Edition in a cluster

Hi
As I will be planning to setup Lync on a virtual environment regardless if it is going to be the Standard or Enterprise edition.
I am thinking if we use 1 Lync Standard Edition for the FE Server with Fault Tolerance enabled, would it be as good as having 2 Lync Enterprise Edition in a cluster?
Thanks

Hi there,
the main difference between using Lync enterprise and lync standard is the High availability and scalability feature,
you will get fault tolrance setup with one lync standard edition running on whatever hyper-v and vmware platform, however this will not be an optimum highly available solution for the simple reason that upon a host server failure the image will move
to another available host server and users will lose their active session durin the move process.
on the other hand what you will gain if you the Enterprise edition is that you will have a unique identity to which all lync clients will be connecting and this identity is the lync pool identity which is in the background handled with multiple Front-End
servers and AV conferencing pools, mediation pools and so on.
In additioin when you have multiple front-ends in place, those front-ends will not work in active/passive mode as in a regular cluster, in contrairy all the servers will be active and handeling the work load.
hope i make it a bit clear, if yiu need more info i am ready
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread
Thanks for the response, being a small environment of 300 users, standard edition would be more than enough for me but the fact for HA is very critical for me at this stage. That is why I am exploring the option of using VMware FT.
I don't quick get what you mean on the users having to move to another image as my understanding of FT is in the event of a host failure (not VM failure like bluescreen etc), the VM will fail over to another host with no lost in any ping etc.
So, in theory, the Lync Server VM would never know that the parent ESX host had failed and it needed to failover to another host. Hope my understanding is correct.
Thanks

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.

Hyper-V Failover Cluster Live migration over Virtual Adapter

Hello,
Currently we have a test environment 3 HyperHost wich have 2 Nic teams. LAN team and team Live/Mngt.
In Hyper-V we created a Virtual Switch (Wich is Nic team Live/Mngt)
We want to seperate the Mngt and live with Vlans. To do this we created 2 virtual adapters. Mngt and Live, assigned ip adresses and 2 vlans(Mngt 10, Live 20)
Now here is our problem: In Failover cluster you cannot select the Virtual Adapter(live). Only the Virtual Switch wich both are on. Meaning live migration simple uses the vSwitch instead of the Virtual adapter.
Either its not possible to seperate Live migration with a Vlan this way or maybe there are Powershell commands to add Live migration to a Virtual adapter?
Greetings Selmer

It can be done in PowerShell but it's not intuitive.
In Failover Cluster Manager, right-click Networks and you'll find this:
Click Live Migration Settings and you'll find this:
Checked networks are allowed to carry traffic. Networks higher in the list are preferred.
Eric Siron
Altaro Hyper-V Blog
I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.

UOO sequencing along with WLS high availability cluster and fault tolerance

Hi WebLogic gurus.
My customer is currently using the following Oracle products to integrate Siebel Order Mgmt to Oracle BRM:
* WebLogic Server 10.3.1
* Oracle OSB 11g
They use path service feature of a WebLogic clustered environment.
They have configured EAI to use the UOO(Unit Of Order) Weblogic 10.3.1 feature to preserve the natural order of subsequent modifications on the same entity.
They are going to apply UOO to a distributed queue for high availability.
They have the following questions:
1) When during the processing of messages having the same UOO, the end point becomes unavailable, and another node is available in order to migrate, there is a chance the UOO messages exist in the failed endpoint.
2) During the migration of the initial endpoint, are these messages persisted?
By persisted we mean that when other messages arrive with the same UOO in the migrated endpoint this migrated resource contains also the messages that existed before the migration?
3) During the migration of endpoints is the client receiving error messages or not?
I've found an entry on the WLS cluster documentation regarding fault tolerance of such solution.
Special Considerations For Targeting a Path Service
When the path service for a cluster is targeted to a migratable target, as a best practice, the path
service and its custom store should be the only users of that migratable target.
When a path service is targeted to a migratable target its provides enhanced storage of message
unit-of-order (UOO) information for JMS distributed destinations, since the UOO information
will be based on the entire migratable target instead of being based only on the server instance
hosting the distributed destinations member.
Do you have any feedback to that?
My customer is worry about loosing UOO sequencing during migration of endpoints !!
best regards & thanks,
Marco

First, if using a distributed queue the Forward Delay attribute controls the number of seconds WebLogic JMS will wait before trying to forward the messages. By default, the value is set to −1, which means that forwarding is disabled. Setting a Forward Delay is incompatible with strictly ordered message processing, including the Unit-of-Order feature.
When using unit-of-order with distributed destinations, you should always send the messages to the distributed destination rather than to one of its members. If you are not careful, sending messages directly to a member destination may result in messages for the same unit-of-order going to more than one member destination and cause you to lose your message ordering.
When unit-of-order messages are processed, they will be processed in strict order. While the current unit-of-order message is being processed by a message consumer, the next message in the unit-of-order will not be delivered unless it is to the same transaction or session. If no message associated with a particular unit-of-order is processing, then a message associated with that unit-of-order may go to any session that’s consuming from the message’s destination. This guarantees that all messages will be processed one at a time and in order, and any rollback or recover will not prevent ordered processing of the messages.
The path service uses a persistent store to save the state of which member destination a particular unit-of-order is currently using. When a Path Service receives the first message for a particular unit-of-order bound for a distributed destination, it uses the normal JMS load balancing heuristics to select which member destination will handle the unit and writes that information into its persistent store. The Path Service ensures that a new UOO, or an old UOO that has no messages currently on any destination, can be enqueued anywhere in the cluster. Adding and removing member destinations will not disrupt any existing unit-of-order because the routing decision is made dynamically and those decisions are persistent.
If the Path Service is unavailable, any requests to create new units-of-order will throw the JMSOrderException until the Path Service is available. Information about existing units-of-order are cached in the connection factory and destination servers so the Path Service availability typically will not prevent existing unit-of-order messages from being sent or processed.
Hope this helps.

Server 2012 r2 live migration fails with hardware error

Hello all, we just upgraded one of our hyper v hosts from server 2012 to server 2012 r2; previously we had live replication setup between it and another box on the network which was also running server 2012. After installing server 2012 r2 when a live migration
is attempted we get the message:
"The virtual machine cannot be moved to the destination computer. The hardware on the destination computer is not compatible with the hardware requirements of this virtual machine. Virtual machine migration failed at migration source."
The servers in question are both dell, currently we have a poweredge r910 running server 2012 and a poweredge r900 running server 2012 r2. The section under processor for "migrate to a physical computer using a different processor" is already checked
and this same vm was successfully being live replicated before the upgrade to server 2012 r2. What would have changed around hardware requirements?
We are migrating from server 2012 on the poweredge r910 to server 2012 r2 on the poweredge r900. Also When I say this was an upgrade, we did a full re install and wiped out the installation of server 2012 and installed server 2012 r2, this was not an upgrade
installation.

The only cause I’ve seen so far is virtual switches being named differently. I do remember that one of our VMs didn’t move, but we simply bypassed this problem, using one-time backup (VeeamZIP, more specifically).
If it’s one-time operation you can use the same procedure for the VMs in question -> backup and restore them at new server.
Kind regards, Leonardo.

Hyper-V Live Migration Compatibility with Hyper-V Replica/Hyper-V Recovery Manager

Hi,
Is Hyper-V Live Migration compatible with Hyper-V Replica/Hyper-V Recovery
Manager?
I have 2 Hyper-V clusters in my datacenter - both using CSVs on Fibre Channel arrays. These clusters where created and are managed using the same "System Center 2012 R2 VMM" installation. My goal it to eventually move one of these clusters to a remote
DR site. Both sites are connected/will be connected to each other through dark fibre.
I manually configured Hyper-V Replica in the Fail Over Cluster Manager on both clusters and started replicating some VMs using Hyper-V
Replica.
Now every time I attempt to use SCVMM to do a Live Migration of a VM that is protected using Hyper-V Replica to
another host within the same cluster,
the Migration VM Wizard gives me the following "Rating Explanation" error:
"The virtual machine virtual machine name which
requires Hyper-V Recovery Manager protection is going to be moved using the type "Live". This could break the recovery protection status of the virtual machine.
When I ignore the error and do the Live Migration anyway, the Live migration completes successfully with the info above. There doesn't seem to be any impact on the VM or it's replication.
When a Host Shuts-down or is put into maintenance, the VM Migrates successfully, again, with no noticeable impact on users or replication.
When I stop replication of the VM, the error goes away.
Initially, I thought this error was because I attempted to manually configure
the replication between both clusters using Hyper-V Replica in Failover Cluster Manager (instead of using Hyper-V Recovery Manager).
However, even after configuring and using Hyper-V Recovery Manager, I still get the same error. This error does not seem to have any impact on the high-availability of
my VM or on Replication of this VM. Live migrations still occur successfully and replication seems to carry on without any issues.
However, it now has me concern that Live Migration may one day occur and break replication of my VMs between both clusters.
I have searched, and searched and searched, and I cannot find any mention in official or un-official Microsoft channels, on the compatibility of these two features.
I know vMware vSphere replication and vMotion are compatible with each otherhttp://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.replication_admin.doc%2FGUID-8006BF58-6FA8-4F02-AFB9-A6AC5CD73021.html.
Please confirm to me: Are Hyper-V Live Migration and Hyper-V Replica compatible
with each other?
If they are, any link to further documentation on configuring these services so that they work in a fully supported manner will be highly appreciated.
D

This can be considered as a minor GUI bug.
Let me explain. Live Migration and Hyper-V Replica is supported on both Windows Server 2012 and 2012 R2 Hyper-V.
This is because we have the Hyper-V Replica Broker Role (in a cluster) that is able to detect, receive and keep track of the VMs and the synchronizations. The configuration related to VMs enabled with replications follows the VMs itself.
If you try to live migrate a VM within Failover Cluster Manager, you will not get any message at all. But VMM will (as you can see), give you an
error but it should rather be an informative message instead.
Intelligent placement (in VMM) is responsible for putting everything in your environment together to give you tips about where the VM best possible can run, and that is why we are seeing this message here.
I have personally reported this as a bug. I will check on this one and get back to this thread.
Update: just spoke to one of the PMs of HRM and they can confirm that live migration is supported - and should work in this context.
Please see this thread as well: http://social.msdn.microsoft.com/Forums/windowsazure/en-US/29163570-22a6-4da4-b309-21878aeb8ff8/hyperv-live-migration-compatibility-with-hyperv-replicahyperv-recovery-manager?forum=hypervrecovmgr
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

Hyper-v Live Migration not completing when using VM with large RAM

hi,
i have a two node server 2012 R2 cluster hyper-v which uses 100GB CSV, and 128GB RAM across 2 physical CPU's (approx 7.1GB used when the VM is not booted), and 1 VM running windows 7 which has 64GB RAM assigned, the VHD size is around 21GB and the BIN file
is 64GB (by the way do we have to have that, can we get rid of the BIN file?).
NUMA is enabled on both servers, when I attempt to live migrate i get event 1155 in the cluster events, the LM starts and gets into 60 something % but then fails. the event details are "The pending move for the role 'New Virtual Machine' did not complete."
however, when i lower the amount of RAM assigned to the VM to around 56GB (56+7 = 63GB) the LM seems to work, any amount of RAM below this allows LM to succeed, but it seems if the total used RAM from the physical server (including that used for the
VMs) is 64GB or above, the LM fails.... coincidence since the server has 64GB per CPU.....
why would this be?
many thanks
Steve

Hi,
I turned NUMA spanning off on both servers in the cluster - I assigned 62 GB, 64GB and 88GB and each time the VM started up no problems. with 62GB LM completed, but I cant get LM to complete with 64GB+.
my server is a HP DL380 G8, it has the latest BIOS (I just updated it today as it was a couple of months behind), i cant see any settings in BIOS relating to NUMA so i'm guessing it is enabled and cant be changed.
if i run the cmdlt as admin I get ProcessorsAvailability : {0, 0, 0, 0...}
if i run it as standard user i get ProcessorsAvailability
my memory and CPU config are as follows, hyper-threading is enabled for the CPU but I dont
think that would make a difference?
Processor 1 1 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 1 4 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 1 9 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 1 12 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 2 1 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 2 4 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 2 9 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor 2 12 Good, In Use Yes 713756-081 DIMM DDR3 16384 MB 1600 MHz 1.35 V 2 Synchronous
Processor Name
Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz
Processor Status
OK
Processor Speed
2400 MHz
Execution Technology
12/12 cores; 24 threads
Memory Technology
64-bit Capable
Internal L1 cache
384 KB
Internal L2 cache
3072 KB
Internal L3 cache
30720 KB
Processor 2
Processor Name
Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz
Processor Status
OK
Processor Speed
2400 MHz
Execution Technology
12/12 cores; 24 threads
Memory Technology
64-bit Capable
Internal L1 cache
384 KB
Internal L2 cache
3072 KB
Internal L3 cache
30720 KB
thanks
Steve

Live migration of domains with OVMM

Can anybody point out the reference for performing live migration of domains through OVM Manager instead of CLI. Could not find it in the User's manual for OVM Server 2.2 release.

Does the same thing happen if you initiate the live migration from within SCVMM? Generally speaking, if SCVMM is in use, you should first try to perform the operation from SCVMM before trying to use the Failover Cluster Manager or the Hyper-V Manager.
Should not make any difference, but it would be another point of information.
What is so strange is that a live migration within the cluster is not doing anything with the disks. All it is doing is moving the executing VM from the memory of one node of the cluster to another node in the cluster. The virtual hard disks,
.vhd or .vhdx, are not touched, unless when you say 'live migration' you mean 'live storage migration'. Very strange that it is only happening on the VMs with .vhd.
Another thing you could try ... convert the .vhd on one of the problematic VMs to a .vhdx file and see if that fixes the issue.
. : | : . : | : . tim

Fault tolerance hardware with vSphere 5.5

Hi,
I'm trying to test vSphere 5.5.
So i have 5 physical machines : 2 ESXi, 1 Domain Controller, 1 vCenter, and a Freenas for iSCSI.
ESXi01 : Intel Core i3 540 with 8 GB RAM and 120 GB SSD, 2 NIC
ESXi02 : Intel Core i3 4150 with 8 GB RAM and 250 GB SATA, 2 NIC
Hosted an OpenBSD VM (128 MB RAM, 1vCPU)
I tested :
- vMotion works
- High Availability works (with EVC enabled).
Now I tried Fault Tolerance : no success
To have FT, do i need absolutely the same CPU on the 2 ESXi ?? Any advices ?
Thank you very much for your reply.

Hi,
Thank you very much.
I tried SiteSurvey Plugin, now i know why it doesn't work
These ESX hosts are not compatible with FT, but may contain VMs that are:
esxi02.vclass.local
CPU type Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz is not supported by FT.

Experience VMware Fault Tolerance with Central Services/SRM for Appl Servs?

Hello all, I am looking for real-life experience of VMware Fault Tolerance enabled for SAP Central Services (ABAP/Java). FT is valid only for 1 vCPU VM's, therefor a probable good match with CS. Tips & trics are welcome.
If SRM is available, is it worthwhile to use it for protecting Application Servers in a dual datacenter? That way, the full capacity is guaranteed even after a disaster (resources should be available of course in the surviving DC).
So, are the VMware features like SRM and FT actually being used to protect SAP environments, and if yes, to any satisfaction?
Thanks in advance for your replies,
Roland

Hi Roland,
Did you finally use VMWare Fault Tolerance ? what has been your experience?
thanks,
Thomas

Configure Live Migration Multi-channel with SW QoS

I'm a bit confused about what is needed to properly configure Live Migration using SMB multi-channel with QoS, using a SCVMM logical switch. Where I'm confused, coming from a VMware background, is how many and what type of vNICs that I need. I'm thinking
I need two of some virtual NIC type, each with a unique IP address, which SMB multi-channel for LM would use. I would then somehow tie a SW QoS policy to the vNICs to ensure LM traffic doesn't stomp all over other network traffic types.
Any explanations would be most welcomed.
Blog: www.derekseaman.com, VMware vExpert 2012/2013

Hi there.
Hopefully this guide should give you a detailed explanation of the configuration of this setup, explaining logical switches, port profiles (virtual and uplink) and QoS:
http://gallery.technet.microsoft.com/Hybrid-Cloud-with-NVGRE-aa6e1e9a
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

Live migration with Fault Tolerance (FT)?

Similar Messages

Maybe you are looking for