Cluster Shared Volumes change metric configuration with powershell only !

 

How do I change the metric off my cluster shared volumes network ?

Well If you don’t want to use the autometric then you need to change it but where can I change it.

When you enable Cluster Shared Volumes, the failover cluster automatically chooses the network that appears to be the best for CSV communication. However, you can designate the network by using the cluster network property, Metric. The lowest Metric value designates the network for CSV and internal cluster communication. The second lowest value designates the network for live migration, if live migration is used (you can also designate the network for live migration by using the failover cluster snap-in).

When the cluster sets the Metric value automatically, it uses increments of 100. For networks that do not have a default gateway setting (private networks), it sets the value to 1000 or greater. For networks that have a default gateway setting, it sets the value to 10000 or greater. Therefore, for your preferred CSV network, choose a value lower than 1000, and give it the lowest metric value of all your networks.

Another property, called AutoMetric, uses true and false values to track whether Metric is being controlled automatically by the cluster or has been manually defined.

 

To set the Metric value for a network, use the Windows PowerShell cmdlet Get-ClusterNetwork as described in the following procedure. For more information about the cmdlet, see Get-ClusterNetworkhttp://go.microsoft.com/fwlink/?LinkId=143787 ) .

To designate a network for Cluster Shared Volumes

  1. On a node in the cluster, click Start, click Administrative Tools, and then click Windows PowerShell Modules. (If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.)

  2. To identify the networks used by a failover cluster and the properties of each network, type the following:

    Get-ClusterNetwork | ft Name, Metric, AutoMetric, Role

clip_image002

clip_image001

A table of cluster networks and their properties appears (ft is the alias for the Format-Table cmdlet). For the Role property, 1 represents a private cluster network and 3 represents a mixed cluster network (public plus private).

  1. To change the Metric setting to 900 for the network named Cluster Network 1, type the following:

    ( Get-ClusterNetwork "Cluster Network 1" ).Metric = 9000

The AutoMetric setting changes from True to False after you manually change the Metric setting. This tells you that the cluster is not automatically assigning a Metric setting. If you want the cluster to start automatically assigning the Metric setting again for the network named Cluster Network 1, type the following:

  1. ( Get-ClusterNetwork "Cluster Network 1" ).AutoMetric = $true

  2. To review the network properties, repeat step 2.

 

clip_image004

In this example, Cluster Network 1 is enabled for client communication, so it has a value of 10000, while Cluster Network 2 is internal only, so it has a value of 1000.

CSV traffic goes over the lowest metric cluster network that’s upclip_image005

clip_image003

Note the 3 Role values:

Role: 1 for a private network, 0 for ignored by cluster, 3 for mixed traffic

Metric: the weight of the connection, generally in the 10,000 range for public networks, 1,000 for private ones. If a network has a default gateway, it is considered public; if not, private. Should there be more than one private or public network, the metric is incremented by 100 in order of enumeration (e.g. private network 2 will have a default metric of 1,100)

Autometric: 1 if the metric is set automatically by the cluster, 0 if you have set it manually.

 

 

WordPress Tags: Cluster,Volumes,want,Metric,Another,AutoMetric,Windows,PowerShell,ClusterNetwork,procedure,LinkId,Start,Administrative,Tools,Modules,User,Account,Control,displays,Name,Role,Format,Table,Network,True,False,Note,Should,order,change,failover,appears,communication,designate,lowest,value,designates,internal,migration,uses,networks,default,gateway,greater,values,cmdlet,click,properties,represents,public,traffic

Posted October 22, 2010 by Robert Smit in AutoMetric

  • Tag