How to change subnets with Windows Failover Clusters?


hello,

i have 2 separate windows failover clusters running on current class c subnet , have ran out of ip address space , need move subnetted class a. question how proceed changing each of nodes, re-adding iscsi storage disk (as san's ip changing new class subnet) each of nodes. here planned change:

current ip subnet wfc nodes , services live on - 192.168.2.x

new ip subnet wfc nodes , services live on - 10.10.1.x

i have read bit of information steps required perform, changing on network, including domain controllers, sans, etc, etc, - order of steps need follow? assume need change cluster's ip information first before changing our domain controllers, need verify permission make changes. correct in thinking way? if has information or steps follow, appreciate much.

thank all,  

pretty easy do, particularly if can in maintenance period when don't have guarantee access cluster resources.

first, not recommended practices put onto single subnet.  recommended use different subnets different functions.  reason should using single subnet if have single nic.

as sequence of changes, start dcs , infrastructure - dns, dhcp, etc. - first.  , before that, ensure routing able handle change infrastructure.  there absolutely no problem dc , other components being in different subnet else depends on - rather common, even.  require routing work.  since relies on that, rather ensure backbone solid before trying move else.  not mention version of cluster.  if 2008 r2, need have dc in place accessible re-ip'ing nodes.  change ip address on nodes , within cluster manager change ip address of caps.


. : | : . : | : . tim



Windows Server  >  High Availability (Clustering)



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group