Today I write to one of my customers, and I thought this would make a good public confirmation for some Admin out there, who his having a bad Saturday, because his updates are not going so well.
Below you will find a basic process for doing NIC updates to a Hyper-V cluster. This is not an MS best Practices article, But in some capacity, It should be. Follow this process to keep your cluster nodes a clean as they can be, with your Networks as fast and updated as they can be.
Before you begin, Make sure you run Ipconfig /all > mytxt.txt. THis is so you can put the network back together, if needed.
To update the Network Drivers on your Hyper-V Cluster.
- 1. Take all the Virtual Machines off the Server to be updated.
- 2. Remove it from the Hyper-V cluster.
- 3. Remove all Software or Hardware Teams
- 4. If any VMs are staying on the Cluster node, make sure their NIC is set to not configured, so they are not attached to any virtual network.
- 5. At this point, you should only have physical NICS in your Device Manager and NCPA.CPL.
- 6. In device manager, show hidden devices to make sure you don’t have a ghost NIC. If you do, deleted it.
- 7. Remove the existing Network Driver Package.
- 8. If Possible, delete the driver from the server.
- 9. The NICS may auto discover, and they may be assigned an MS DRIVER. That Is ok.
- 10. The main thing, is they should not be assigned a Broadcom or Intel driver, as those should be deleted.
- 11. Restart the Server.
- 12. Apply the new Firmware first, and then Apply the Driver package.
- 13. Restart the server and begin adding your teams and Virtual networks.
- 14. Re-add your Server to the cluster.
- 15. Proceed as normal
If you have any additional trouble
Now notice I did not say you have to delete the virtual networks from Hyper-V. If you do the updates like I have laid out, then you should not have to . But, If you go through the process, and you did not succeed, then you must go Through the same process, but you will have to delete all virtual networks from the console.
Yes this will mean you will need to re-configure the virtual networks, and re-assign the VMs to the new networks you created. You should always be prepared to do this, if you are going to update your server.
Even as Cluster Aware Updating becomes Popular, you should always be prepared to Re-Deploy you Virtual Network.
If you are asking why these things are, My response is You don’t want to know some of the problems that can happen! So let me add to this, in closing, that the upside to doing it this way are many. One good things, is that you may decide to go ahead to reset the Winsock and TCP stack at this time. This will guarantee that your network is clean and that there are no problems with the stack. MS networks are very flexible and dynamic. However, the load and changes we put on them
Require us to make sure we keep things as clean operating as possible.
I hope this message has been informative.