Overview

After the extensive Juniper Core switch designs, configurations and network testing. The next step is to initiate migration of servers and workstations onto the new VLAN subnet. This document covers migrating the current Windows Server 2012 Failover Cluster with a File Server role onto a new subnet or network. The File server cluster infrastructure utilizes two VM file server nodes with VMware 3-Node clustering with vDS VLAN networking in place.

Procedure

Step 1. Add Network Interfaces to VM File Server Nodes

• Add new network interfaces to the file server nodes Virtual Machine using vSphere Client or vSphere web client.
  • Right Click VM > Edit Settings > Add > Ethernet Adapter > Next

    

  • Add the New Network connection, select an adapter type and network connection. In this case I am using VMXNet3 since it is faster, has lower overhead and more stable. E1000 should only be used purely as a fallback for OSes that have no VMware utilities.

    

  • Repeat this process for other VM nodes.

Step 2. Assign Network Address to the File Server Nodes

• Assign Static IP Address to new Network Interface. Repeat for both nodes.
  • Right Click Network Interface > Properties > Internet Protocol Version 4 > Properties. Enter IP address

    

  • Disable NetBIOS over TCP/IP

    

  • On the File Server Nodes, flush and register dns by running the following commands on CMD. Upon running the command, each nodes should now have two IP addresses binded to it.
    • ipconfig /flushdns
    • ipconfig /registerdns
  • Launch DNS manager and verify that the new IP addresses have been registered.

    

Step 3. Add New Network IP to File Server Role

• Allow Cluster Network Communication and Allow clients to connect through this network.
  • Launch Failover Cluster Manager > Networks. Right Click on new network > Properties

    

  • Check the radio button Allow cluster network communication in this network. Check the box Allow clients to connect through this network.

    

• Add New IP Address to the File Server Role
  • Click Roles > Resources > Right Click Name > Properties

    

  • Click Add. Select the new network and assign the file server role a static IP address.

    

    

    

  • You should now have two network interfaces tied to your File Server Role. Ensure that Publish PTR Records is check. In doing so, new networks binded to this role will be published to the DNS server. Verify that both IP addresses are online.

    

Step 4. Switchover File Server Role to New Network

• Take Old IP Address Binding Offline
  • Under Roles > File Server > Server Name. Right click Old Network > Take Offline.

    

• Monitor role and verify that the file server role status remains running

  

• Remove Old Network Binding From File Server Role
  • Right Click IP Address > Remove. Select Yes when prompted to remove IP Address

    

    

• Launch DNS Manager and reload DNS. Verify that the old IP address binding to the file server role instance has been removed from the server.
  • nslookup filesvr

  

  

Step 5. Switchover Failover Cluster IP Address to New Network

• Add New IP Address to the Failover Cluster Role
  • Under Failover Cluster Manager > Select Cluster. Under Cluster Core Resources > Right Click Cluster Name > Properties

    

  • Under Properties > Add. Select the correct network adapter and assign it a static IP address > OK

    

  • Ensure the Publish PTR Records is selected > Apply. Click Yes to Confirm

    

    

  • Similar to Adding IP New networks to File Server Role, verify that both IP address shows online. Also ensure that the newly added IP address has been binded to DNS.

    

• Remove Old Network Binding From Failover Cluster
  • Right Click Old IP Address > Take Offline

    

  • Launch DNS Manager and reload DNS. Verify that the old IP address DNS binding has been removed.

    

  • Right Clik Old IP Address > More Actions > Remove

Step 6. Test Live Failover

• Launch Remote Desktop with access to file server shares.
  • Open a file on the shared drive.
  • Monitor Desktop Icons (User profile desktop directory is also shared on our file server cluster)
• Initiate Live Failover
  • Launch File Server Cluster Manager >Nodes > Select the active node > Pause > Drain Roles

    

  • Verify that there are no disconnection in file share connections and that the file server role has been migrated to the second node.

    

• Initiate Live Failback by draining roles and monitor file shares.
  • Launch File Server Cluster Manager > Nodes > Select the paused node > Resume > Fail Roles Back
  • Verify that there are no disconnection in file share connections and that the file server role has been migrated back to the first node.

    

    

References

1. https://community.spiceworks.com/topic/457808-can-ping-printer-and-access-web-interface-but-cannot-print-via-network