I’ve added a second node to our Hyper-V cluster. The servers are HP BL460 G5 blades. The setup was simple:
- Install Windows Server 2008 R2
- Install HP’s MPIO 4.0
- Install the HP PSP 8.30
- Set up the NIC’s
- Set up the computer name and computer domain membership
- Enable Hyper-V role
- Install the 2 fixes I’ve blogged about before for W2008 R2 and Hyper-V
- Enable Failover Clustering feature
- Set up/add to the cluster
- Add the cluster to VMM 2008 R2
- Configure the virtual networks for the hosts in VMM on one node – which replicates to the other nodes in the cluster via a job
I deployed a test VM to the cluster and ensure the IC’s were up to date. I set up the IP configuration of the VM for the VLAN that it was located in. I then set up a continuous ping from the VM to its default gateway (a Cisco ASA firewall cluster) and initiated a live migration. As expected, the console window terminated as the VM left node 1 and moved to node 2. Problem! My ping failed.
Not with Live Migration, though. It worked perfectly. When I set up the virtual networks on node 1 in VMM, VMM set them up as Internal networks on the other node. Doh! I changed the virtual networks to External and reran the tests. Perfect! I set a node into maintenance mode – the VM live migrated. Not a single ping was dropped. Perfect!