Change VLANS/ IP Addresses of a SQL Server failover cluster instance

 

This has been performed in SQLServer 2012 SP3, A-P cluster setup on windows server 2012. These are virtual machines build on Hypervhosts. Requires a sysadmin/network admin for updating DNS or adding isci names to SAN

In Active node:

  1. Go to Failover cluster manager–>roles–>select SQL Server service name–>in the bottom choose resources tab—>select server name—>right click take offline
  2. Go to network and sharing center—>change network adapter settings–>select your adapter–>right click properties–>in networking tab select Internet protocol version 4       –>properties and make changes to the IP Address, subnet mask, gateway and preferred DNS (according to your requirement) –> you will lose connection
  3. Repeat the same thing for any additional adapters with a new IP Address as subnet mask, gateway and preferred DNS could remain same mostly
  4. Login into the server
  5. Connect to iSCSI initiator and check if LUNs are connected still
  6. Add iSCSI names to SAN
  7. If LUNs are not connected, then reconnect them and chose enable multipath
  8. Go to Failover cluster manager–>roles–>select SQL Server service name–>in the bottom choose resources tab–>select server name–>properties, General tab–>in IP Addresses–>add new IP Address the new network will show up automatically as you have updated the network adapter settings
  9. Go to a command prompt by running as admin and run ipconfig/registerDNS to register your DNS
  10. Update VM VLAN on HyperVHost
  11. Update SQL DNS cluster IP for that cluster in DNS
  12. Select the windows cluster name–>in the right side in cluster core resources–>select server name–>right click properties–>in the IP Address add new IP Address

In Passive node:

  1. Go to network and sharing center–>change network adapter settings–>select your adapter–>right click properties–>in networking tab select Internet protocol version 4–>properties and make changes to the IP Address, subnet mask, gateway and preferred DNS (according to your requirement) –> you will lose connection
  2. Repeat the same thing for any additional adapters with a new IP Address as subnet mask, gateway and preferred DNS could remain same mostly
  3. Go to a command prompt by running as admin and run ipconfig/registerDNS to register your DNS
  4. Remove old IP Addresses from cluster core resources as well as server name properties (wherever you added the new IP Addresses)

In active node:

  1. Remove old IP Addresses from cluster core resources as well as server name properties (wherever you added the new IP Addresses)
  2. Perform failover and see if all is well

On your PC:

  1. From command prompt do ipconfig/flushDNS

 

Hope this helps!

 

Advertisements
This entry was posted in SQL Server DBA Stuff and tagged , , , . Bookmark the permalink.

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 )

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s