Capacity Planner for Hyper-V Replica

Hyper-V in Windows Server 2012 includes a new capability called Hyper-V Replica. Hyper-V Replica allows administrators to replicate their virtual machines from a primary server/cluster to a replica server/cluster. The Capacity Planner for Hyper-V Replica guides the IT administrator to design the server, storage and network infrastructure which is required to successfully deploy Hyper-V Replica.

clip_image001

After reviewing the license terms, Click on ‘I accept the license term’ and click on ‘Next’.

clip_image002

Before proceeding from this page, ensure that a Hyper-V Replica server/cluster has been enabled to receive replication traffic from this primary server/cluster. As part of collecting various metrics, the capacity planner attempts to send a temporary VHD from the primary server/cluster to the replica server/cluster. This allows the tool to study the network characteristics of the link between the primary and replica server.

If your primary or replica server is part of a cluster, ensure that the Hyper-V Replica Broker role is added to the cluster.

clip_image003

Specify the following parameters in this screen and click ‘Next’:

Primary Server/Cluster details:

a. For a standalone primary server, enter the server name or FQDN.

b. If your primary server is part of a cluster, enter the FQDN of the (primary cluster) Hyper-V Replica Broker Client Access Point (CAP).

Replica Server/Cluster details:

a. For a standalone replica server, enter the server name or FQDN.

b. If your replica server is part of a cluster, enter the FQDN of the (replica cluster) Hyper-V Replica Broker Client Access Point.

Estimated WAN Bandwidth:

a. Enter the estimated WAN bandwidth link speed between the primary and replica server/cluster.

Duration of collecting metrics:

a. Enter an appropriate interval for which the metrics need to be collected. It is highly recommended that the tool is run during ‘production hours’ which ensures that the most representative data is collected. Running the tool for a short duration (eg: 10mins) may not give quality data.

clip_image004

The tool connects to the primary server and enumerates the virtual machines which are running on the primary. Ensure the following:

1) You are an administrator on the primary server/cluster. Remote-WMI is used to enumerate the virtual machines on the primary server – ensure that the right set of firewalls and permissions are set to allow this call to execute.

2) Ensure that replication has not been enabled on any of the VMs which are on the primary server/cluster.

3) Ensure that the VMs on the primary server/cluster are running.

The following details needs to be provided in the page:

1) Temporary VM location: As part of collecting various metrics, the tool creates a temporary VM on your primary server/cluster and enables replication on the VM. This allows the tool to study the network characteristics between the primary and replica server. Provide a location on the primary server/cluster in which this VHD/VM can be created. In a clustered deployment, ensure that the location is accessible from all the nodes in the cluster.

2) (Optional) Certificate: If your primary and replica servers are in a workgroup [or] if certificate based authentication is being used in your Hyper-V Replica environment, you should provide the required certificate in this page.

3) Select VMs and VHDs: You can select the VMs and VHDs on which the metrics need to be collected. If you are not planning to enable replication on any specific VM/VHD, you can uncheck the VM in this screen.

Click ‘Next’ after providing all the inputs.

clip_image006

The tool now captures the metrics in the background. The tool will run for a few minutes beyond the duration of the run. You can continue to operate on your VM during the duration of the run. Once completed, the screen will look as follows:

clip_image008

Click on ‘View Report’ to go over the recommendations.

Cheers,


Marcos Nogueira
http://blog.marcosnogueira.org
Twitter: @mdnoga

Statistics of a NIC Teaming

If the UI window is sufficiently tall a statistics tile appears at the bottom of the Team tile and the Adapters and Interfaces tile. These statistics windows reflect the traffic of the selected team and selected team member. If you don’t see the statistics try making the UI window a little taller.

clip_image001

Viewing statistics for a team interface

If the Team Interfaces tab is selected in the Adapters and Interfaces tile the statistics at the bottom of the Adapters and Interfaces tile will be those of the selected team interface.

clip_image003

Setting frequency of Statistics updates

The frequency of statistics updates and other updates can be set by selection Settings in the Servers tile Tasks menu. Selecting this item brings up the General Settings dialog box.

clip_image005

The two drop-down lists in this dialog box allow the user to change how often the UI is refreshed. The settings apply equally to all servers in the servers list.

This menu also allows the administrator to decide whether or not adapters that are not able to be part of a team should be shown in the UI. By default these non-teamable adapters are not shown.

Cheers,


Marcos Nogueira
http://blog.marcosnogueira.org
Twitter: @mdnoga

Microsoft System Center Virtual Machine Manager 2012 Cookbook

I definitely recommend this book for who wants to know in deep System Center 2012 Virtual Machine Manager SP1.

image

http://link.packtpub.com/POCsIQ

What you will learn from this book

  • How to use VMM Architecture and plan for a real word deployment
  • Utilize Network Virtualization, Gateway integration, Storage integration, Resource Throttling, and Availability options
  • Deploy Operations Manager and integrate with VMM
  • Integrate SC APP Controller with VMM to manage Private and Public Clouds (Azure)
  • Cluster deployment with VMM Bare Metal
  • Create and deploy Virtual Machines from Templates
  • Deploy a highly available VMM Management Server
  • Manage Hyper-V, Vmware, and Citrix from VMM
  • How to upgrade from SCVMM 2008R2 to SCVMM 2012 SP1

In Detail

Microsoft System Center 2012 is a comprehensive IT infrastructure, virtualization, and cloud management platform. With System Center 2012, you can more easily and efficiently manage your applications and services across multiple hypervisors as well as across public and private cloud infrastructures to deliver flexible and cost-effective IT services for your business.

This cookbook covers architecture design and planning and is full of deployment tips, techniques, and solutions designed to show users how to improve VMM 2012 in a real world scenario. It will guide you to create, deploy, and manage your own Private Cloud with a mix of Hypervisors: Hyper-V, Vmware ESXi, and Citrix XenServer. It also includes the VMM 2012 SP1 features.

This book is a cookbook that covers architecture design, planning and is full of deployment tips, techniques and solutions designed to show users how to improve VMM 2012 in a real world scenario. It will guide you to create, deploy and manage your own Private Cloud with a mix of Hypervisors : Hyper-V, Vmware ESXi and Citrix XenServer.

Approach

This is a Packt Cookbook, full with over 75 recipes for VMM users to carry out vital tasks quickly and easily.

Who this book is for

This book is written for solutions architects, technical consultants, administrators, and any other virtualization lover who needs to use Microsoft System Center Virtual Machine Manager in a real world environment.

Cheers,


Marcos Nogueira
http://blog.marcosnogueira.org
Twitter: @mdnoga

Modifying a NIC Team through GUI and PowerShell

Modifying a team through the UI

Within the UI, modifications to the team can be done by selecting a team in the Team tile, right-clicking on the team, and selecting the Modify Team action. Selecting Modify Team will pop-up the Team properties dialog box. This dialog box is very similar to the

In the Team properties dialog box the following actions can be accomplished:

  • Rename the team: Select the team name and edit it.
  • Add team members: Select additional adapters from the Member Adapters tile
  • Remove team members: De-select adapters from the Member Adapters tile. At least one adapter must be selected.

clip_image002

If the Additional properties drop-down item is selected then the Teaming mode and Load distribution mode may also be modified. This Additional properties drop-down also allows the administrator to select a standby adapter when active-standby mode is desired.

clip_image004

Modifying a team through Windows PowerShell
Renaming a team

To rename Team1 and give it the name TeamA, the Windows PowerShell is:

Rename-NetLbfoTeam Team1 TeamA

Changing the teaming mode

The Windows PowerShell options for teaming mode are:

  • SwitchIndependent
  • Static
  • LACP

To change Team1 to an 802.1ax LACP team, the Windows PowerShell is:

Set-NetLbfoTeam Team1 ‑TeamingMode LACP

The “-TeamingMode” flag can be abbreviated “-TM”, as in

Set-NetLbfoTeam Team1 –TM LACP

Note: For security reasons teams created in VMs may only operate in SwitchIndependent mode.

Changing the load distribution algorithm

The Windows PowerShell options for load distribution algorithm are:

  • TransportPorts
  • IPAddresses
  • MacAddresses
  • HyperVPort

To change Team1’s Load balancing algorithm to Hyper-V Ports, the Windows PowerShell is:

Set-NetLbfoTeam Team1 ‑LoadBalancingAlgorithm HyperVPorts

The “-LoadBalancingAlgorithm” flag can be abbreviated “-LBA”, as in

Set-NetLbfoTeam Team1 ‑LBA HyperVPorts

To change the Teaming mode and Load balancing algorithm at the same time,

Set-NetLbfoTeam Team1 ‑TM LACP ‑LBA HyperVPorts

Note: Teams created in VMs may not use the HyperVPort load distribution algorithm.

Adding new members to the team

To add NIC1 to Team1 the Windows PowerShell command is:

Add-NetLbfoTeamMember NIC1 Team1

Removing members from the team

To remove NIC1 from Team1 the Windows PowerShell command is:

Remove-NetLbfoTeamMember NIC1 Team1

Setting a team member to be the Standby Adapter

A team member can be set as the Standby Adapter through Windows PowerShell:

Set-NetLbfoTeamMember NIC4 -AdministrativeMode Standby

At most one team member may be in standby mode at any point in time. If a different team member is already in standby mode that team member must be returned to active mode before this Windows PowerShell cmdlet will succeed.

Adding new interfaces to the team

To add a new interface to the team select the Team in the Teams Tile and the Team Interfaces tab in the Adapters and Interfaces tile. Select the Tasks menu in the Adapters and Interfaces tile, then select Add Interface.

clip_image005

Selecting the Add Interface action item pops-up the New team interface dialog box.

clip_image006

Since only one team interface, the primary team interface, can be in Default mode, the new team interface must have a specific VLAN value. As the specific VLAN value is entered the name of the interface will be modified to be the team name followed by the VLAN value of this team interface. The interface name can be modified to any other name (duplicates are not allowed) if the administrator chooses to do so.

Selecting OK will create the new team interface.

clip_image008

The Windows PowerShell to add a team interface with VLAN 42 to Team1 is

Add-NetLbfoTeamNIC Team1 42

Modifying team interfaces

There are only two modifications that can be done to a team interface:

  • change the team interface name and/or
  • change the VLAN ID.

To modify the team interface VLAN ID select and then right-click the team interface in the Team Interfaces tab. Select the Properties action item.

clip_image010

This pops-up the Network Adapter Properties dialog box. This dialog box has some useful information about the team interface. It also has the box where the new VLAN ID can be entered. If a new VLAN ID is entered and the team name is the one the system provided when the team interface was created the team interface name will be changed to reflect the new VLAN ID. If the team interface name has been previously changed then the team name will not be changed when the new VLAN ID is entered.

clip_image012

To modify a team interface’s VLAN ID in Windows PowerShell

Set-NetLbfoTeamNIC “Team1 ‑ VLAN 42” -VlanID 15

Just as in the UI, changing the VLAN ID will cause the team interface name to change if the team interface name is still the same as the one the system created when the team interface was created. I.e., if the team interface name is <teamName ‑ VLAN xx> where xx is the VLAN ID of the team interface, then the VLAN ID portion of the team interface name will be modified to reflect the new VLAN ID.

Removing interfaces from the team

To delete a team interface, select and then right-click the team interface in the Team Interfaces tab. Select the Delete team interface action item. A confirmation dialog box will pop-up. Once confirmed the team interface is deleted.

The Primary team interface (i.e., the one that was created when the team was created) can’t be deleted except by deleting the team.

To delete a team interface in Windows PowerShell

Remove-NetLbfoTeamNIC “Team1 ‑ VLAN 42”

Deleting a team

To delete a team from the server select the team in the Teams tile. Right-click the team and select the Delete team action item.

clip_image014

A confirmation dialog box will be displayed. Once confirmed the team will be deleted.

To delete a team in Windows PowerShell

Remove-NetLbfoTeam Team1

To remove all teams from the server in Windows PowerShell (i.e., to clean up the server),

Get-NetLbfoTeam | Remove-NetLbfoTeam

Cheers,


Marcos Nogueira
http://blog.marcosnogueira.org
Twitter: @mdnoga