Here it is, September 18th and I’m just now getting around to my first post of the month! It’s been very busy lately, I’ve taken some time off, and to be honest, a little lazy in regards to spending time blogging. With everything else going on, the blog has suffered a bit, I had thought the information may be getting “stale”, but I think I’ve had more hits once I stopped creating new posts, go figure. Anyway, I have a bit of energy and feel like I need to get the 2008 R2 Hyper-V series done with, so here you have it, the much anticipated resumption of the 2008 R2 Hyper-V series!! I’m just kidding…..

Here are the links to the previous posts:

Part 1 – Creating a Windows Server 2008 R2 Hyper-V Failover Cluster: Install Hyper-V and Failover Clustering
Part 2 – Creating a Windows Server 2008 R2 Hyper-V Failover Cluster: Configuring iSCSI Connectivity

To this point, we have 2 Windows 2008 R2 Hyper-V servers (LAB-HVCORE-01 and LAB-HVCORE-02) and we have attached to a couple of 300GB iSCSI LUNs hosted on EMC Storage. In this step, we’re going to create the initial External virtual network on each Hyper-V host using Hyper-V Manager.

1. Launch Hyper-V Manager and connect to one of the Hyper-V servers. Remember that you cannot connect to a Windows Server 2008 R2 Hyper-V server if you launch Hyper-V Manager (or the Failover Cluster MMC for that matter) from Windows Server 2008, the connection will fail. Thus, you must open Hyper-V Manager from another 2008 R2 server, or you can load the Remote Server Administration Tools (RSAT) on your desktop. The RSAT for Windows 7 can be found here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en

Anyway, after launching Hyper-V Manager, under Actions, click Virtual Network Manager

2. Under Create virtual network, select External and then click Add

3. Enter a network name (the name must be the same on each HyperV Server), select the appropriate network adapter, and click OK.

4. When prompted to apply network changes, click Yes.

5. Repeat steps 1-4 on each Hyper-V server.

On Step 4, we will Validate the failover cluster configuration…stay tuned!