Home » IT - Microsoft » Configuring IP Addresses and Dependencies for Multi-Subnet Clusters – Part II

Configuring IP Addresses and Dependencies for Multi-Subnet Clusters – Part II

Escribe tu dirección de correo electrónico para suscribirte a este blog, y recibir notificaciones de nuevos mensajes por correo.

Join 5 other followers

March 2016
M T W T F S S
« Feb   May »
 123456
78910111213
14151617181920
21222324252627
28293031  

NO! A LOS TOROS

Disclaimer

All messages posted to this blog are provided "AS IS" with no warranties, and confer no rights. The content of this site are personal opinions and might not represent the Microsoft Corporation view. Regarding any sample code that we provide: This Sample Code is provided for the purpose of illustration only and is not intended to be used in a production environment. THIS SAMPLE CODE AND ANY RELATED INFORMATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE. This blog serves 2 purposes. Firstly, I want to share information with other IT pros about the technologies we work with and how to solve problems we often face. Secondly, I use my blog as a notebook. There's so much to learn and remember in our jobs that it's impossible to keep up. By blogging, I have a notebook that I can access from anywhere. Anything you do to your IT infrastructure, applications, services, computer or anything else is 100% down to your own responsibility and liability. Mcselles bears no responsibility or liability for anything you do. Please independently confirm anything you read on this blog before doing whatever you decide to do.
Advertisements

Hi Cluster Fans,

A few weeks ago I posted a blog about configuring IP Addresses with multiple subnets and got some feedback about some additional scenarios to consider. This blog post will discuss the best practice of setting possible owners for the IP Addresses.

Setting Possible Owners

The ‘Possible Owners’ setting is a resource property which allows an admin to designate whether a resource should come online on a specific node. By default, all nodes in the cluster will be the possible owner of a resource. However, you may want a workload to never come online on a specific node, so you will want to adjust these settings to prevent the cluster from trying to start the resource on that node. The resource will be able to move to a non-possible owner, however it will never automatically come online on that node.

An IP Address resource in a multi-subnet cluster is a perfect example of why you may want to configure this property. In our example from the previous blog post we deployed a File Server that used two subnets, a 172.24.13.0/24 and a 172.24.14.0/24. We will refer to these as our “.13 Subnet” and “.14 Subnet”, respectively. We configured two IPv4 Addresses, 172.24.13.1 on my .13 Subnet and 172.24.14.1 on my .14 Subnet. Since the .13 IP Address will only come online on nodes which are on the .13 Subnet, only those nodes should be possible owners. Since the .14 IP Address will only come online on nodes which are on the .14 Subnet, only those nodes should be possible owners.

Although configure Possible Owners is not required for multi-subnet clustering, it is a best practice since it reduces the amount of work which the cluster has to do after a failover since it will never try to bring those IP Addresses online on nodes which will never support it.

To configure Possible Owners, right-click on each IP Address resource and select Properties, then the Advanced Policies tab. Toggle the Possible Owners to the correct setting then click Apply and exit. Make sure you do this for both IP Address resources.

In our example, symonp-N1 is on our .14 Subnet, and symonp-N2 is on our .13 Subnet. This means that we want to make symonp-n1 the Possible Owner for the .14 IP Address and symonp-n2 the Possible Owner for the .13 IP Address.

Now your IP Address resources will only come online on the appropriate cluster nodes.

This KB article contains a great summary of the semantics of the various cluster ownership policies: http://support.microsoft.com/kb/299631.

Source: https://blogs.msdn.microsoft.com/clustering/2011/01/18/configuring-ip-addresses-and-dependencies-for-multi-subnet-clusters-part-ii/

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Microsoft on the Issues

News and perspectives on legal, public policy and citizenship topics

Mike Crowley's Whiteboard

“There are no limits to what you can accomplish when you are supposed to be doing something else."

T.B.D.

There Be Dragons

Ken Cenerelli

My life in software development

VMware, Windows, Virtualization (Servers & Desktops)

VMware, Windows, Virtualization (Servers & Desktops)

Just a random "Microsoft Server / Client Tech" info..

"Feeding Your Training and Technology Obsessions"

WordPress.com

WordPress.com is the best place for your personal blog or business site.

DocSharing

Documentación técnica, notas y apuntes sobre Administración de Sistemas, Servidores, Redes y más

Microsoft Taste

Mary's Blog

%d bloggers like this: