Hyper-V Failover Cluster Networking Configuration After Install

Hello All,
Is it possible to install hyper-v and failover or in other words create a hyper-v failover cluster and then configure the networking part of the solution later? As I am coming into
terms with the networking part of it, wanted to do it later after the install. Is it possible?
And from later configuration, I am trying to say, creation of NIC Team, Virtual NICs, VLAN tagging, etc.

Hi,
Failover cluster deployment requires network connectivity between cluster nodes. You can't create a cluster without properly configured TCP\IP on cluster nodes.
http://OpsMgr.ru/

Similar Messages

Server 2008 R2 Failover cluster network configuration

Hi
We have a customer with a Server 2008 R2 Hyper-V failover cluster. They have 2 cluster networks, "Cluster Network 1" and "Cluster Network 2".
"Cluster Network 1": NIC team on 172.16.1.0/24 for private cluster network communication
"Cluster Network 2": NIC team on 192.168.1.0/24 for production network communication
I can see that "Cluster Network 1" is configured to "Allow cluster network communication on this network" and "Allow clients to connect through this network".
If "Cluster Network 1" is ONLY for communication between the to cluster nodes then I assume the selection in "Allow clients to connect through this network" should be removed?
/Lasse

It will cause a lost network connection for any client that is accessing through that network. Those clients would need to reconnect.
Did you configure both IPs on the cluster resource name that clients are accessing? If you only configured the one you want, there should be no issue. If you configured both, then it is possible some clients might be connected via the private
network.
Another thing you should, and if you have already done this you will most likely not have issues at all, is that you should disable DNS registration on any network you do not want client access coming through. If the clients can only find the resource
through the DNS name registered, that is the way they will be coming in. In my clusters, which often have 7 or more NICs, there is only one with a published DNS record.
. : | : . : | : . tim

Hyper-V Failover Cluster Configuration Confirmation

Dear All,
I have created a Hyper-V Failover Cluster and I want you to confirm if the configuration I have done is okay and I have not missed
out anything that is mandatory for a Hyper-V Failover Cluster to work. My configuration is below:
1. Presented Disks to servers, formatted and taken offline
2. Installed necessary features, such as failover clustering
3. Configured NIC Teaming
4. Created cluster, not adding storage at the time of creation
- Added disks to the cluster
- Added disks as CSV
- Renamed disks to represent respective CSV volumes
- Assigning each node a CSV volume
- Configured quorum automatically which configured the disk witness
- There were two networks so renamed them to Management and Cluster Communication
- Exposed Management Network to Cluster and Clients
- Exposed Cluster Communication Network to Cluster only
5. Installed Hyper-V
- Changed Virtual Disks, Configuration and Snapshots Location
- Assigned one CSV volume to each node
- Configured External switch with allow management option checked
1. For minimum configuration, is this enough?
2. If I create a virtual machine and make it highly available from hyper-v console, would it be highly available and would live
migrate, etc.?
3. Are there any configuration changes required?
4. Please, suggest how it can be made better?
Thanks in advan

Hi ,
Please refer to following steps to build a hyper-v failover cluster :
Step 1: Connect both physical computers to the networks and storage
Step 2: Install Hyper-V and Failover Clustering on both physical computers
Step 3: Create a virtual switch
Step 4: Validate the cluster configuration
Step 5: Create the cluster
Step 6: Add a disk as CSV to store virtual machine data
Step 7: Create a highly available virtual machine
Step 8: Install the guest operating system on the virtual machine
Step 9: Test a planned failover
Step 10: Test an unplanned failover
Step 11: Modify the settings of a virtual machine
Step 12: Remove a virtual machine from a cluster
For details please refer to following link:
http://technet.microsoft.com/en-us//library/jj863389.aspx
Hope it helps
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.

Heartbeat Network inside Hyper-V Failover Cluster

Dear All,
I need to build an SQL Server 2012 SP1 Two-node cluster inside Hyper-V Failover Cluster. There is only one virtual switch in the Hyper-V Failover Cluster environment which is being
used for communication to the outside world using VLAN Tagging. Now, since SQL Server 2012 Failover Cluster would require a heartbeat network as well and although possible to assign VLAN tag to the heartbeat adapter and use that for hearbeat, but since there
would not be any gateway on the heartbeat network, it would render the VLAN tagging useless, so is following plan good enough:
1. Create an Internal Virtual Switch on all nodes of the cluster with the same name
2. Link the heartbeat adapter of the virtual machines to the Internal Virtual Switch
Is it good enough? or is there any other better way?
Thanks in advance.

I am not an expert on this, but here is what I would do.
Create the VLAN and use that to keep the network setup as easy to understand as possible. Our Hyper-V cluster is only using IPv6 on the heartbeat network, and that is working like a charm. I would do the same inside the hyper-v hosts if I need to builld
a virtual cluster.
What is the reason for deploying a failover cluster for SQL inside Hyper-V? Wouldn't a log shipping "cluster" provide a more secure solution for your SQL?
/Martin
Exchange is a passion not just a collaboration software.

Moving VMs from Standalone Hyper-V to Hyper-v Failover Cluster

Hello All.................I need to move Virtual Machines from Standalone Hyper-V based on Windows Server 2012 R2 to a Hyper-V Failover Cluster based on Windows Server 2012 R2.
- The VMs OS is Windows Server 2012 R2
- Applications installed on VMs are SCCM, SCOM, SharePoint, etc.
1. I am looking for a Checklist that I can run through and move them. To make sure I do not miss out anything.
2. Would a downtime be required in this scenario while the VM is being moved?
3. What requires special attention in this scenario?

Thanks for the reply.
So, I do not need to do anything and just simply add both the cluster and standalone into VMM and then simply use the Move option. Please, confirm if I have understood it correct.
Yes. But be carefull. First shut down your VM's
if possible and configure them in such a way they don't automatically start. If you install the SCVMM Agent, some Hyper-V related services are restarted, when some VMs start during that process you system may stall. I have seen this multipe times.
There is another dirty option that worked of us perfectly. Export the VMs. Then import those VMs to a local disk on one Hyper-V Server. Refresh the Hyper-V Server and Virtual Machines on that Hyper-V Server. Give it a few minutes. Then do
a Live Migration while at the same time makeing it "Highly Available" by moving it to your CSV. Works flawlessly. DO NOT IMPORT THE VMS TO YOUR CSV, otherwise you can't change it to "Highly Avaiable" unless you have
two CSVs. Importing it straight to a CSV does not make them Highly Available.
Boudewijn Plomp | BPMi Infrastructure & Security
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer".

Virtual memory in a hyper-v failover cluster

Hi all,
We have a window 2008 R2 hyper-V failover cluster working fine. It has two hosts, with 104 GB of memory on each of them.As I added new virtual instances I had been updating memory.
The point is that as I do that page file for virtual memory has been growing and now System volumen has only 20 GB free space.
I had like to go on adding memory for new virtual instances, so I need to fix this problem. Which is the recommended configuration for this? Can I disable virtual memory as long as I have an enormous quantity of physical memory available?
Thank you very much.
Kind regards,
David.

Hi,
that enormous page file at Hyper-V Servers make no sence.
We do not need to configure virtual memory for physical Memory that is assigned to VMs.
Check this for more informations:
http://blogs.technet.com/b/rwagg/archive/2010/03/08/how-big-should-pagefile-sys-be-on-a-server-2008-hyper-v-server.aspx
Hope that helps
Regards
Sebastian

Guest cluster on Hyper-V failover cluster

I want to implement Hyper-V failover cluster on Windows Server 2012 R2. Then Install Windows 2003 R2 as Hyper-V guest OS.
Do you know whether Windows 2003 R2 guest cluster support on Hyper-V on Windows Server 2012 R2?

Hi steventsf,
Windows Server 2003 R2 with Service Pack 2 (SP2) is in the supported guest operation system list :
http://technet.microsoft.com/library/hh831531.aspx
The guest OS is independent of hyper-v host , I think windows server 2003 R2 SP2 guest cluster is a supported scenario .
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.

Requirements for similar hardware in a 2012 Hyper-V failover cluster?

Simple question:
How similar does the hardware have to be on the host servers in a Windows Server 2012 Hyper-V failover cluster?
We have 6 dell servers that we are hoping to use for building a Windows 2012 Hyper-V cluster.
As I recall from our existing 2-host Hyper-V cluster, which is running on 2008 R2, there are fairly harsh demands in the cluster validation wizard with regard to similarity of hardware. So I am wondering if it will work?
The servers in question are 3 x R620, 2 x T410 and 1 x T610 Dell servers. So 3 x 12th generation servers and 3 x 11th generation servers
The servers all use Intel CPUs:
R620: Xeon E5-2670/2680
T410/610: Xeon X5650
and broadcom NICs:
T610: Broadcom 5709c
2 x T410: Broadcom 5716c
3 x R620: Broadcom 5720
Windows 2012 is supported by Dell on all the servers.
Shared storage will be on an SMB3 file share.

Simple question:
How similar does the hardware have to be on the host servers in a Windows Server 2012 Hyper-V failover cluster?
We have 6 dell servers that we are hoping to use for building a Windows 2012 Hyper-V cluster.
As I recall from our existing 2-host Hyper-V cluster, which is running on 2008 R2, there are fairly harsh demands in the cluster validation wizard with regard to similarity of hardware. So I am wondering if it will work?
The servers in question are 3 x R620, 2 x T410 and 1 x T610 Dell servers. So 3 x 12th generation servers and 3 x 11th generation servers
The servers all use Intel CPUs:
R620: Xeon E5-2670/2680
T410/610: Xeon X5650
and broadcom NICs:
T610: Broadcom 5709c
2 x T410: Broadcom 5716c
3 x R620: Broadcom 5720
Windows 2012 is supported by Dell on all the servers.
Shared storage will be on an SMB3 file share.
You'll be fine with a listed config no need to have identical machines. The only thing I'd try to change is use the same NICs all-around if possible.
P.S. Make sure you understand SMB share is a single point of failure unless SoFS or "old skool" NAS failover is configured. But it adds latency so using shared storage
directly w/o a file transport is FASTER and CHEAPER.
StarWind iSCSI SAN & NAS

VSA Manager 5.1 stuck in "Validating VSA Cluster Network Configuration"

Hi all!
I am experiencing a problem with VSA Manager 5.1.3.0 running on a Win2008R2 server with vCenter 5.1 build 1123961. When I open the VSA Mananger tab in the VI Client it displays "Validating VSA Cluster Network Configuration".
When trying to close the window it says:
I have tried to open the VSA Manager tab on another server with the VI Client installed but the result is the same. I have also tried to upgrade the VSA Manager to 5.5 but it stayed the same.
The cluster with the VSA nodes is working normally but I cannot manage VSA or upgrade the environment. Any advice or help would be greatly appreciated!
Best regards
Kenneth

Sorted with HP support, needed some extra tagging, jumbo frames and flow control.

The Cluster Service function call 'ClusterResourceControl' failed with error code '1008(An attempt was made to reference a token that does not exist.)' while verifying the file path. Verify that your failover cluster is configured properly.

I am experiencing this error with one of our cluster environment. Can anyone help me in this issue.
The Cluster Service function call 'ClusterResourceControl' failed with error code '1008(An attempt was made to reference a token that does not exist.)' while verifying the file path. Verify that your failover cluster is configured properly.
Thanks,
Venu S.
Venugopal S ----------------------------------------------------------- Please click the Mark as Answer button if a post solves your problem!

Hi Venu S,
Based on my research, you might encounter a known issue, please try the hotfix in this KB:
http://support.microsoft.com/kb/928385
Meanwhile since there is less information about this issue, before further investigation, please provide us the following information:
The version of Windows Server you are using
The result of SELECT @@VERSION
The scenario when you get this error
If anything is unclear, please let me know.
Regards,
Tom Li

Hyper-V Failover Cluster virtual guests suddenly reboots

The environment is Server 2012 R2 using dual clusters--a Hyper-V Failover Cluster running guest application virtual machines and a Scale-Out File Server Cluster using Tiered Storage Spaces which are used to supply SMB3 shares
for Quorum and CSV. Has anyone had this problem?

Anything relevant in the host or guest event logs? I would also check the cluster event logs to see if there are any indications there as well.
Does the guest go down hard or gracefully reboot?
Need more info.
Andy Syrewicze
Come talk more about Hyper-V and the Microsoft Server Stack at
Syrewiczeit.com and the Altaro Hyper-V Hub!
Post are my own and in no way reflect the views of my employer or any other entity in which I produce technical content for.

Removal of Node from Hyper-V Failover Cluster

Hello All....................I have a 8 node Hyper-V Failover Cluster based on Windows Server 2012 R2. I am facing some issues with one of the servers, so I have decided to take that node out of the Hyper-V Failover cluster. I would appreciate if someone
could share the steps that I should take to ensure smooth removal of node especially with respect to CSV Volume and Quorum. THanks.

Hi Sir ,
Please try the following command (before you do this please live migrate VMs to another nodes ):
Remove-ClusterNode –Name node4 -Force
For this command please refer to :
http://technet.microsoft.com/en-us/library/hh847251.aspx
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.

Very Strange Network Issue With Two Guests on 2012 R2 Hyper-V Failover Cluster

Hi all. We're having a odd issue with two guests on our 2012 R2 failover cluster.
In a nutshell, if we shutdown a particular server (I'll call it Server A) another totally different server (Server B) on the same node loses it's network connectivity to the domain. If we start server A back up, network connectivity returns on server B.
At first I thought server A might be running a service that was somehow linked to server B, so I decided to disable server A's NIC. Interestingly, that had no affect on server B's connectivity.
The next step I tried was pausing server A and again, no adverse affect on server B's connectivity.
Next step was to live migrate server A to another node. This action did
cause server B to lose its network connection.
One other clue is that if I ping server B from either of the Hyper-V hosts in the cluster, I never lose network connection to server B.
So I would suspect this is some network issue on the cluster, but I'm kind of at a loss where to go from here.
Has anyone seen this behavior before or does anyone have any troubleshooting suggestions I can try?
Thanks!
George Moore

Hi Sir,
I'v never seen this before .
>>Next step was to live migrate server A to another node. This action did
cause server B to lose its network connection.
They are connecting to same virtual switch ?
First please run cluster validation to check if there is any error .
If it is ok , please try the following items for troubleshooting :
1. shutdown serverA serverB
2. then add another virtual NIC for serverB
3. start server B check if the issue happens to both "old" and "new" virtual NIC .
In addition , you can live migrate both A and B to another node , then try to live migrate A to the original node .
If the issue persists , I would suggest you to remove that virtual switch on both nodes then re-create them .
Best Regards,
Elton Ji
If it is not the answer please unmark it to continue
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] .

Hyper-V Failover Cluster - Inconsistent Network Availability

We've got a Small cluster with, 7 hosts and a dozen or two VM's. For some reason i'm getting inconsistent availability with the Cluster networks. The host seem to function fine on there own but theres all types of issues using Migration which
i'm assuming is because certain hosts think other hosts are unavailable. For Example:
Cluster Network 1 - From Host 8
Cluster Network 1 - From Host 10
As far as I can tell all of the networks are UP. I can ping all hosts on all interfaces. What criteria goes into determining host availability?

Hi,
Maybe you forgot to configure the Live migration Settings,
In the Failover cluster manager->right click networks-> select the livemigration network.
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.

LUN can't be accessed after move it to another Hyper-V Failover Cluster without "remove from cluster shared volumes" on the original cluster

Hi all,
I have a old cluster, let's call it cluster01, and a new cluster, cluster02. There is a LUN attach to cluster01 as a CSV volume. I forgot to "remove from cluster shared volumes" in Failover Cluster console, then power off the cluster01 and
attach the LUN to the cluster02. Now the LUN can't be accessed in cluster02, it show as a RAW disk. I tried to attach the LUN to it's original cluster cluster01 but can't read it too.
Is there any way to get it back?

Hi Zephyrhu,
Can you run Clear-ClusterDiskReservation powershell cmdlet and see that helps?
http://technet.microsoft.com/en-us/library/ee461016(WS.10).aspx
Thanks,
Umesh.S.K

Hyper-V Failover Cluster Networking Configuration After Install

Similar Messages

Maybe you are looking for