Moving the cluster to another network segment

-

hi there,

we need move our 2 cluster nodes new network segment. cluster physical nics gets new ip address , network address , network mark. virtual ips need new ip addresses.

what recommended process changing ip addresses? should disable cluster resources , cluster service after restart in new network segment cluster not start incorrect ips?

any knows what's correct process this?

thanks

hi,

here correct steps (as confirmed ms support)

1.    take cluster resources offline

a.    in failover cluster management, right click each of 4 resources , select take service or application offline

b.    wait resources being offline.

 

2.    shut down cluster service on both nodes

a.    in failover cluster management, right click cluster node , select more actions. click on shutdown cluster.

b.    wait cluster services being shut down.

 

3.    shut down windows on both physical nodes

4.    physically move cluster , storage new data center

5.    start both cluster nodes , verify physical nics on public network got new ip address (dhcp)

a.    start network connections in control panel , verify correct ip addresses has been assigned.

b.    start failover cluster management console , verify if network online. if not, shutdown , restart cluster service using shutdown cluster function.

6.    configure new cluster virtual ip address on node 1

a.    start failover cluster management console, open cluster core resources, expand cluster name container, right click ip address entry , select properties.

b.    change static address entry new virtual ip address of cluster.

7.    verify cluster core resources on node 2

a.    start failover cluster management on node 2. open cluster core resource , verify node see correct virtual cluster ip.

8.    verify cluster storage (node 1)

a.    in failover cluster management open storage container , verify disks online.

9.    configure ip addresses of cluster resources

a.    click on service entry in services , applications

b.    expand name entry. right click on ip address , click properties. change static ip address of resource new virtual ip address. verify correct network displayed.

c.     right click on service entry , select bring service or application online

 

10.  verify cluster resources node 2

a.    start failover cluster management on node 2. verify cluster resources

cheers,
gunter



Windows Server  >  High Availability (Clustering)



Comments

Post a Comment

Popular posts from this blog

Error: 0x80073701 when trying to add Print Services Role in Windows 2012 Standard

-
hello, i'm getting error when trying add print services role in windows 2012 standard. i'm getting same error whether use gui or powershell. this new server install. the powershell error follows: add-windowsfeature : request add or remove features on specified server failed. installation of 1 or more roles, role services, or features failed. the referenced assembly not found. error: 0x80073701 at line:1 char:1 + add-windowsfeature print-services + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : invalidoperation: (@{vhd=; credent...name=localhost}:psobject) [install-windowsfeature],     exception     + fullyqualifiederrorid : dismapi_error__failed_to_enable_updates,microsoft.windows.servermanager.commands.addwind    owsfeaturecommand success restart needed exit code      feature result ------- ------...
Read more

Windows 2016 RDS event 1306 Connection Broker Client failed to redirect the user... Error: NULL

-
Image
i'm attempting setup windows 2016 rds standard deployment session hosting.  layout follows: rds01 - rds connection broker , web access ts02 - rds session host ts03 - rds session host domain these servers part of has (1) windows 2008 server , (2) windows 2016 servers acting dcs.  domain running @ windows 2003 functional level. servers on single routed network no firewall between them.  dns , ptr records servers exist , resolve on hosts.  servers can pinged each other. in other words, there no network connectivity issues. i've setup rds deployment several times w/ same results. the issue can login via rdweb interface on rds01 win10 desktop , connect published rdp desktop without issue (i.e. no error messages user) , no errors in logs.  when try directly rdp rds01, authenticate user (per event log) error stating user doesn't have access system.  in event log event id 1306 message of "remote desktop connection broker client faile...
Read more

Como saber quien entro a mi PC por la Red

-
quisiera saber si es posible, o existe forma de auditar quien accedió a mi pc vía red, es decir se que hay software que perminten auditar el file server para saber quien entro y modifico y/o borro un archivo... pero si alguien entro mi pc \\pcname\c$ hay forma de determinar que usuario entro al disco c de una pc en especifica y copio, modifico o borro un archivo...   y la otra pregunta cuales son las mejores herramientas para auditar la red y el file server   gracias una forma de detectar quien esta conectado tu pc es través del comando net user entra en cmd y escribes net user eso muestra los usuarios que están conectados en tu equipo en un momento determinado, se que no es lo que pides pero puede servir para descubir alguien en determinado momento. para que no este compartido le dan clic derecho sobre mi pc>propiedades>remoto y le desmarcan donde dice ''permitir que este equipo envíe invitaciones ...
Read more