Virtualization
Infrastructure
Administration
Hyper-V 2012 R2
Jakub Yaghob
Building our own (virtualized)
infrastructure – Hyper-V
port: 112x
internet
10.250.x.249
HVSCMx
GW: 10.2.0.1
Mask: 255.255.0.0
acheron
DNS1: 195.113.19.71
DNS2: 195.113.19.77
10.2.2.x
HVADx
10.250.x.250
10.252.x.y
10.250.x.1
10.250.x.2
10.250.x.3
HVx1
HVx2
HVx3
10.251.x.1
10.251.x.2
10.251.x.3
virtsan
10.251.0.1
W2012R2 installation for AD





Deploy template HVAD
VM name HVADx
Start HVADx
Install W2012R2 (std+GUI)
Install VMware tools (Guest->Install …)



Setup the network cards






Typical
Restart
Network “Kralicek azurit” has IP 10.2.2.x, Mask 255.255.0.0, GW
10.2.0.1, DNS1 195.113.19.71, DNS2 195.113.19.77
Network “Virt mgmt” has IP 10.250.x.250, Mask 255.255.255.0
Use MAC for network detection
Enable remote access
Access from anywhere using RDP to
acheron.ms.mff.cuni.cz:112xx (e.g. 11203)
Make updates
W2012R2 installation

Add role “Active Directory Domain Services”


Promote server to the domain controller






Installs DNS server
Create a new forest
All DNS for all NICs will be set to 127.0.0.1
DNS server must forward foreign queries to the original DNS
(195.113.19.71, 195.113.19.77)
Check internet connectivity
Add features “Failover clustering”, “Hyper-V management tools”
Add role “Remote Access”


Configure router for NAT from 10.250.x.0 to 10.2.2.x
Update Hyper-V core servers
Hyper-V core server
installation





Deploy template HVcore
VM name HVxy
Start HVxy
Install Hyper-V
Install VMware Tools



Set computer name to HVxy
Configure all NICs









D:\setup64
“Network settings”
Use “ipconfig /all” for detecting MAC/IP pairs
All NICs have static IP
“Virt mgmt” - 10.250.x.y, mask 255.255.255.0, GW 10.250.x.250, DNS 10.250.x.250
“Virt SAN” - 10.251.x.y, mask 255.255.0.0
“Virt vmotion” - 10.252.x.y, mask 255.255.255.0
Join the domain
Set the time zone
Configure iSCSI




Run “iscsicpl”
“Discovery” ->”Discover portal” -> 10.251.0.1
“Targets” -> “Connect” (add to favorite targets)
“Volumes and devices” -> “Auto Configure”
Failover cluster




Running on HVADx
Add HVxy servers
Add feature “Failover clustering” to all HVxy
Set iSCSI disks for HVxy



Failover cluster manager









Select HVx1, bring online only the small (2GB) disk, initialize (remove VMware
GPT), format (no letter assigned)
Bring online the small disk on all other HVxy
“Validate configuration”
Add HVxy servers
Go through validation
Create cluster
The small disk should be marked as “Witness in Quorum”
Creates another virtual network card, IP 10.250.x.100
Bring online the big iSCSI disk on all HVxy
Add disk in failover cluster manager
Mark the big disk as “Cluster shared volume”
Hyper-V manager


Running on HVADx
Configure Hyper-V for each node HVxy




Failover cluster manager




Enable “Live migration”
Add incoming live migrations IP 10.252.x.y, mask
255.255.255.0
Create virtual switches
“Roles” -> “Virtual machines” -> “New VM”
Set VM location to the clustered big volume
Set remaining VM attributes
Manage clustered VM from “Failover cluster
manager” of from “Hyper-V manager”
Hyper-V system center
manager – preinstall






Deploy template HVSCM
VM name HVSCMx
Start HVSCMx
Install W2012R2
Install VMware tools (Guest->Install …)
Setup the network cards





Update windows
Add the server to the domain
Login as domain admin
Download and install Windows Assessment and Deployment Kit



Network “Virt mgmt” has IP 10.250.x.249, Mask 255.255.255.0, GW
10.250.x.250, DNS 10.250.x.250
http://go.microsoft.com/fwlink/?LinkID=302319
Only “Deployment tools” and “Windows PE” required
Install SQL Server 2012

[virtlab-large-storage] ISO/virt/HyperV/SQLServer2012SP1-FullSlipstream-ENUx64.iso
Hyper-V system center
manager – base install

Create new administrative users in domain




Set scm-admin account as local administrator for HVSCMx
Set both accounts as local administrators for HVxy



Use ADSI Edit
VMMDKM, full access for scm-admin, scm-adder
Mount DVD with SCM


Restart HVxy
Create a new container for distributed key management in domain


scm-admin
scm-adder
[virtlab-large-storage] ISO/virt/HyperV/
mu_system_center_2012_r2_virtual_machine_manager_x86_and_x64_dvd_2913737.iso
Install SCM VMM


Use scm-admin as a “Run As” service user
Use VMMDKM as distributed keys container



CN=VMMDKM,DC=dom2,DC=dom1
Run the VMM console
Add Hyper-V hosts


Use cluster IP/name
Use scm-adder as a “Run As” user