Monthly Archive: March 2013

0

Overview of NIC Teaming (LBFO) in Windows Server 2012

NIC teaming, also known as Load Balancing/Failover (LBFO), allows multiple network adapters to be placed into a team for the purposes of · bandwidth aggregation, and/or · traffic failover to maintain connectivity in the event of a network component failure. This feature has long been available from NIC vendors but until now NIC teaming has not been included with Windows Server. The following sections address: · NIC teaming architecture ·...

0

Update for SCVMM 2012 SP1 on Windows server 2012

If you are using System Center 2012 Virtual Machine Manager Service Pack 1 (SCVMM) to manage storage and assign LUNS, there is a collection of updates that may improve this functionality. These updates are for Windows Server 2012 and need to be applied on hosts, VMM servers and any other system that will interact with storage. These updates are offered via Windows Update (see KB2785094) but you can also download...

0

General Methodology for Troubleshooting Hyper-V Replica

Hyper-V Replica connectivity issues between Primary and Replica servers Symptom:  Hyper-V Replica functionality is disrupted and the Hyper-V VMMS\Admin log reports general network connectivity errors between the Primary and Replica server Verify the Replica server is booted and running. Check network connectivity and name resolution functionality between the Primary and Replica server by executing ping and nslookup tests.  If ping test fails, resolve network connectivity issues.  If name resolution fails,...

0

VLANs with Hyper-V Network Virtualization

Isolating different departments’ virtual machines can be a challenge on a shared network. When entire networks of virtual machines must be isolated, the challenge becomes even greater. Traditionally, VLANs have been used to isolate networks, but VLANs are very complex to manage on a large scale. The following are the primary drawbacks of VLANs: · Cumbersome reconfiguration of production switches is required whenever virtual machines or isolation boundaries must be...

4

Hyper-V Failover Cluster as a Primary or Replica Server

Failover Clustering has proven its value in making virtualized workloads highly available.  We saw this in Windows Server 2008 using Quick Migration and then in Windows Server 2008 R2 with the addition of Live Migration. Failover Clustering can also play an important role as a Replica Cluster.  To accommodate this, a new role has been added in Failover Clustering called the Hyper-V Replica Broker.  A new resource type, Virtual Machine...

2

Enabling a Virtual Machine for Replication

Replication is configured on a per virtual machine basis.  Virtual machines running on Primary site Hyper-V servers (or Hyper-V Failover Clusters) are configured to replicate to Replica servers (or Replica Failover Clusters) at remote sites. 1.     In Hyper-V Manager, in the Details pane, Click on a virtual machine 2.     With a virtual machine selected, Right-click and choose Enable Replication.  This starts the Enable Replication wizard 3.     In the Specify Replica...

0

Configuring and Managing Hyper-V Replica

Management Considerations Hyper-V servers are managed locally using the Hyper-V Manager interface or remotely using the Hyper-V Remote Server Administration Tools (RSAT) or System Center Virtual Machine Manager (SCVMM).  If the configuration is a Hyper-V Failover Cluster, the Failover Cluster Management interface is used. Configuration and Management UI Hyper-V Replica settings are configured in the Hyper-V Manager interface for standalone Hyper-V servers and the Failover Cluster Manager interface for Hyper-V...