###BeginCaseStudy###
Case Study: 6
Contoso Ltd Case C
Background
Overview
Contoso, Ltd., is a manufacturing company. The company has offices in Chicago and Seattle.
Each office contains two data centers. All of the data centers and sites for the company have
network connectivity to each other. The company uses a single Active Directory Domain
Services (AD DS) domain.
Contoso is growing rapidly and needs to expand its computer infrastructure.
Current Environment Chicago Office
The Chicago office contains a primary data center and a backup data center. A Hyper-V
cluster named Clusterl.contoso.com resides in the primary data center. The cluster has a
multiple network path configured. The cluster includes two unused SQL Server virtual
machines (VMs) named SQL-SERVER1 and SQL-SERVER2. The cluster also includes a
Hyper-V Host group named Chi-Primary.
Clusterl.contoso.com contains the following servers:
• CHI1-HVNODE1.contoso.com
• CHI1-HVNODE2.contoso.com
• CHI1-HVNODE3.contoso.com
• CHI1-HVNODE4.contoso.com
The backup data center for the Chicago office is located on a Hyper-V cluster named
Cluster2.contoso.com. The cluster has a single network path configured. The cluster includes
a Hyper-V Host group named Chi-Backup.
Cluster2.contoso.com contains the following servers:
• CHI2-HVNODEl.contoso.com
• CHI2-HVNODE2.contoso.com
• CHI2-HVNODE3.contoso.com
• CHI2-HVNODE4.contoso.com
In addition, the Chicago office contains two standalone Hyper-V servers named CHIHVSERVER1.contoso.com and CHI-HVSERVER2.contoso.com.
There are also four newly built servers:
• CHI-SERVERl.contoso.com
• CHI-SERVER2.contoso.com
• CHI-SERVER3.contoso.com
• CHI-SERVER4.contoso.com
All the servers in the Chicago office run Windows Server 2012. Any future servers that are
deployed in the Chicago office must also run Windows Server 2012.
All servers in the Chicaoo office use the subnet 10.20.xx.
Current Environment Seattle Office
The Seattle office contains a primary data center and a backup data center. The primary data
center is located on a Hyper-V cluster named Cluster3.contoso.com. The cluster has a
multiple network path configured. The cluster includes two unused SQL Server virtual
machines named SQL-SERVER3 and SQL-SERVERS The cluster includes a Hyper-V Host
group named Sea-Primary.
Cluster3.contoso.com contains the following servers:
• SEA3-HVNODEl.contoso.com
• SEA3-HVNODE2.contoso.com
• SEA3-HVNODE3.contoso.com
• SEA3-HVNODE4.contoso.com
The backup data center for the Seattle office is located on a Hyper-V cluster named
Cluster4.contoso.com. The cluster has a single network path configured. The cluster includes
a Hyper-V Host group named Sea-Backup.
Cluster4.contoso.com contains the following servers:
• SEA4-HVNODEl.contoso.com
• SEA4-HVNODE2.contoso.com
• SEA4-HVNODE3.contoso.com
• SEA4-HVNODE4.contoso.com
In addition, the Seattle office contains two standalone Hyper-V servers named SEAHVSERVERl.contoso.com and SEA-HVSERVER2.contoso.com.
There are also four newly built servers:
• SEA-SERVERl.contoso.com
• SEA-SERVER2.contoso.com
• SEA-SERVER3.contoso.com
• SEA-SERVER4.contoso.com
All servers in the Seattle office run Windows Server 2012 R2. Any future servers that are
deployed in the Seattle office must also run Windows Server 2012 R2.
All servers in the Seattle office use the subnet 10.10.x.x.
Business Requirements
Apps
Contoso plans to deploy new applications to make its departments more efficient.
App1
Contoso must create a new application named App1 for the human resources (HR)
department. The infrastructure for App1 must reside in a virtual environment and the data
files for App1 must reside on a single shared disk. In addition, the infrastructure for App1
must meet the following requirements:
• maximize data protection
• withstand the loss of a single guest virtual machine
• withstand the loss of a single physical server
To support App1, Contoso must deploy a new cluster named Applcluster.contoso.com. The
cluster has the following requirements:
• It must span multiple sites.
• It must support dynamic quorums.
• It must prevent failures caused by a 50% split.
App2
Contoso must create a new application named App2. To support App2, Contoso must deploy
a new SQL Server cluster. The cluster must not be part of the domain.
The server deployment team that will install the cluster has limited permissions. The server
deployment team does not have the ability to create objects in Active Directory.
Virtualization and Storage
New VMs
Any new VMs that are deployed to the Hyper-V cluster in Cluster3.contoso.com have the
following requirements:
• New SQL Server VMs must be deployed only to odd-numbered
servers in the cluster.
• All other new VM guests must be deployed to any available server in
the cluster.
New VDE
The company needs a highly available file share cluster for a new Virtual Desktop
Environment (VDE). It has the following requirements:
• The file share cluster must withstand the loss of a single server.
• The file share cluster must withstand the loss of a single network path.
• The file share cluster must use the least amount of disk space.
New virtualized SQL Server cluster
Contoso must create a new application for manufacturing. The company needs a new
virtualized SQL Server cluster named VM-SQLclusterl.contoso.com. It has the following
requirements:
• The cluster must use a shared virtual hard disk.
• The cluster must have two nodes named VM-SQLNODE1.contoso.com and VM-SQL-NODE2.contoso.com.
Highly available storage solution
The company is deploying new hardware that will replace the existing Hyper-V clusters. The
new file share cluster must have a highly available storage solution for a Hyper-V
environment. It has the following requirements:
• The new file share cluster must support guest VM clusters.
• The storage cannot reside on any of the physical Hyper-V hosts.
###EndCaseStudy###
You need to enable virtual machine network health detection on all supported clusters.
What should you do?
A.
On the virtual machine settings page for Cluster4, select the Protect network checkbox for each
virtual machine on the cluster.
B.
On the virtual machine settings page for Cluster1, select the Protect network checkbox for each
virtual machine on the cluster.
C.
On each guest virtual machine in Cluster4, configure protected access for the network interface
card.
D.
On each guest virtual machine in Cluster3, configure protected access for the network interface
card.
E.
On the virtual machine settings page for Cluster3, select the Protect network checkbox for each
virtual machine on the cluster.
F.
On each guest virtual machine in Cluster1, configure protected access for the network interface
card.
Cluster 1 in Chicago runs with Server 2012. Network health protection is a feature introduced with Server 2012 R2. So I think, answer B can’t be correct because the checkbox for protected Network isn’t available.
Answers C and D seem to me correct.
You only get to choose 1 answer so it can’t be both C & D
Hang on. The question says “You need to enable virtual machine network health detection on all SUPPORTED clusters”. As Juerg quite rightly says it can’t be B as this isn’t an option on Server 2012. However, 2012 R2 does support this and cluster 3 runs 2012 R2 so should the answer be C?
Sorry I meant E
Thanks for your replies.
Monkeh, if E is correct, then A should also be correct.
Maybe the whole question is wrong designed and multiple answers are correct.
Ah yes of course it would also be correct – my bad! Hmm, I am a bit confused now. If the question is correct and it is only 1 choice what would your opinion be of the best answer to choose? As I say I am confused!!
Cluster4 (answer A) has a single network path. You need multiple paths for health detection.
Answer E is correct
It has to be on one of the 2012 R2 networks that have multiple network paths (that is the whole point of network health protection surely?). So that is cluster 3. Also, it is set on the NIC I believe not on the server itself. So my answer would be D.
Actually, I’ll change to E as I don’t like the term ‘Protected Access’. It should be ‘Protected Network’. Definitely has to go on Cluster 3 imo.
* Scenario:
———————————————————————————————————————————–
All the servers in the Chicago office run Windows Server 2012. Any future servers that are deployed in the Chicago office must also run Windows Server 2012.
———————————————————————————————————————————–
The Chicago office contains a primary data center and a backup data center. A Hyper-V cluster named Clusterl.contoso.com resides in the primary data center. The cluster has a multiple network path configured.
———————————————————————————————————————————–
The backup data center for the Chicago office is located on a Hyper-V cluster named Cluster2.contoso.com. The cluster has a single network path configured.
———————————————————————————————————————————–
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
All servers in the Seattle office run Windows Server 2012 R2. Any future servers that are deployed in the Seattle office must also run Windows Server 2012 R2.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The Seattle office contains a primary data center and a backup data center. The primary data center is located on a Hyper-V cluster named Cluster3.contoso.com. The cluster has a multiple network path configured. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The backup data center for the Seattle office is located on a Hyper-V cluster named Cluster4.contoso.com. The cluster has a single network path configured.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Explanation:
Network health detection and recovery is now available at the virtual machine level for a Hyper-V host cluster. If a network disconnection occurs on a protected virtual network, the cluster live migrates the affected virtual machines to a host where that external virtual network is available. For this to occur there must be multiple network paths between cluster nodes.
In Windows Server 2012, if there is a network disconnection at the virtual machine level, the virtual machine continues to run on that computer even though the virtual machine may not be available to users.
In Windows Server 2012 R2, there is now a Protected network check box in the virtual machine settings. This setting is available in the advanced features of the network adapter. By default, the setting is enabled. You can configure this setting on a per network basis for each virtual machine. Therefore, if there is a lower priority network such as one used for test or for backup, you can choose not to live migrate the virtual machine if those networks experience a network disconnection.
https://technet.microsoft.com/en-us/library/dn265972.aspx#BKMK_VMHealth
So its obvious Answer should be “On the virtual machine settings page for Cluster3, select the Protect network checkbox for each virtual machine on the cluster.” Option E.
I totally agree with you. because
1、Protect Network is a new feature on server 2012 R2
2、you must have a multiple network path configuration.
so according to the case, only Cluster3 match the requirement.
Think I would go for E as well although the wording is a bit confusing it does say “Protect Network” (see link)
http://blogs.msdn.com/b/virtual_pc_guy/archive/2014/03/11/protected-networks-in-windows-server-2012-r2.aspx
On Server2012, This function is available at Hyper-V level.
On Server 2012R2, This is moved to Each VM Level. So it has to be configured on each individual VM.
Now the Question is , Enable Network health detection on all supported CLUSTERS , Answer should be B
If question was , Enable Network Health detection on all supported Virtual machines , Answer would be E
Answer A would never be the choice as Cluster4 is running 2012R2 and Network Health detection is not supported at cluster level.
https://technet.microsoft.com/en-GB/library/dn265972.aspx
Virtual machine network health detection
——————————————————————————–
Network health detection and recovery is now available at the virtual machine level for a Hyper-V host cluster. If a network disconnection occurs on a protected virtual network, the cluster live migrates the affected virtual machines to a host where that external virtual network is available. For this to occur there must be multiple network paths between cluster nodes.
System_CAPS_noteNote
If there are no available networks that connect to other nodes of the cluster, the cluster removes the node from cluster membership, transfers ownership of the virtual machine files, and then restarts the virtual machines on another node.
What value does this change add?
This change increases the availability of virtual machines when there is a network issue. If live migration occurs, there is no downtime because live migration maintains the session state of the virtual machine.
What works differently?
In Windows Server 2012, if there is a network disconnection at the virtual machine level, the virtual machine continues to run on that computer even though the virtual machine may not be available to users.
In Windows Server 2012 R2, there is now a Protected network check box in the virtual machine settings. This setting is available in the advanced features of the network adapter. By default, the setting is enabled. You can configure this setting on a per network basis for each virtual machine. Therefore, if there is a lower priority network such as one used for test or for backup, you can choose not to live migrate the virtual machine if those networks experience a network disconnection.
Protected network setting for a virtual machine
Figure 1. Protected network setting
Agree with everything Jatin said.
Answer is E: imo
Pretty obviously E
https://technet.microsoft.com/en-us/library/dn265972(v=ws.11).aspx#BKMK_VMHealth
2012 doesn’t have this feature, 2012 R2 does
Virtual machine network health detection
Network health detection and recovery is now available at the virtual machine level for a Hyper-V host cluster. If a network disconnection occurs on a protected virtual network, the cluster live migrates the affected virtual machines to a host where that external virtual network is available. For this to occur there >>>MUST BE MULTIPLE NETWORK PATHS<<In Windows Server 2012, if there is a network disconnection at the virtual machine level, the virtual machine continues to run on that computer even though the virtual machine may not be available to users.
In Windows Server >>>2012 R2<<>>PROTECTED NETWORK CHECK BOX<< in the virtual machine settings. This setting is available in the advanced features of the network adapter.