Changing NIC's in a Cluster

  • Thread starter Thread starter Skippy
  • Start date Start date
S

Skippy

I have a two node cluster that I want to change the
public NIC from a 10/100 to a GIG card. Has anyone done
this before? I know the public NIC is a big part of the
the backup heartbeat. Can someone point me in the right
direction?
 
This posting is provided "AS IS" with no warranties, and confers no rights.

This is a pretty painless process. What you need to do is move all resources over to one node so this will probably need to be scheduled during off hours. Set the cluster service to manual on the node that does not have the resources. Uninstall the 'old' NIC card. Shut the node down. Change the NIC card out and bring it back up. Install the new NIC with the Hardware Wizard and set the correct IP configuration on the newly installed NIC. Start the cluster service and set it back to Automatic. Assuming it joins the cluster ok, proceed. If it does not join, then check connectivity to the cluster over the Public network and check IP settings to confirm proper configuration.

Now fail the resources over to the node you just upgraded and complete the same process on the other node in the cluster.

This posting is provided "AS IS" with no warranties, and confers no rights.

I have a two node cluster that I want to change the
public NIC from a 10/100 to a GIG card. Has anyone done
this before? I know the public NIC is a big part of the
the backup heartbeat. Can someone point me in the right
direction?
 
One other thing I noticed. To prevent the node from trying to online resources or rejoin the cluster etc before uninstalling your NIC from Device Manager, be sure to stop the cluster service on that node after setting it to Manual.

This posting is provided "AS IS" with no warranties, and confers no rights.

This posting is provided "AS IS" with no warranties, and confers no rights.

This is a pretty painless process. What you need to do is move all resources over to one node so this will probably need to be scheduled during off hours. Set the cluster service to manual on the node that does not have the resources. Uninstall the 'old' NIC card. Shut the node down. Change the NIC card out and bring it back up. Install the new NIC with the Hardware Wizard and set the correct IP configuration on the newly installed NIC. Start the cluster service and set it back to Automatic. Assuming it joins the cluster ok, proceed. If it does not join, then check connectivity to the cluster over the Public network and check IP settings to confirm proper configuration.

Now fail the resources over to the node you just upgraded and complete the same process on the other node in the cluster.

This posting is provided "AS IS" with no warranties, and confers no rights.

I have a two node cluster that I want to change the
public NIC from a 10/100 to a GIG card. Has anyone done
this before? I know the public NIC is a big part of the
the backup heartbeat. Can someone point me in the right
direction?
 
Thanks. I figured that if I use the same IP, and just do
a hardware swap, that it has some potential to go
smoothly.

Thanks!
-----Original Message-----
This posting is provided "AS IS" with no warranties, and confers no rights.

This is a pretty painless process. What you need to do
is move all resources over to one node so this will
probably need to be scheduled during off hours. Set the
cluster service to manual on the node that does not have
the resources. Uninstall the 'old' NIC card. Shut the
node down. Change the NIC card out and bring it back up.
Install the new NIC with the Hardware Wizard and set the
correct IP configuration on the newly installed NIC.
Start the cluster service and set it back to Automatic.
Assuming it joins the cluster ok, proceed. If it does not
join, then check connectivity to the cluster over the
Public network and check IP settings to confirm proper
configuration.
Now fail the resources over to the node you just
upgraded and complete the same process on the other node
in the cluster.
This posting is provided "AS IS" with no warranties, and confers no rights.

"Skippy" <[email protected]> wrote
in message news:[email protected]...
 
Back
Top