StoreVirtual Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

4730 Repaired - Readding to Cluster? FOM Question.

santaselite
Occasional Contributor

4730 Repaired - Readding to Cluster? FOM Question.

Hi,


One of the 4730s we have had to be repaired (new motherboard, etc.) and we are just ready to re-IP it and add it back to the cluster.  Obviously this will cause a resync.


Is it okay just leaving it to go straight back in the cluster or is there a specific way to re-add it?

 

Also we were told the FOM should not be virtual and to install it on the storage node - how do we actually do that?

 

Thanks.

2 REPLIES
Torsten.
Acclaimed Contributor

Re: 4730 Repaired - Readding to Cluster? FOM Question.

With a  new motherboard you need a special procedure in order to make the license work again. Ask HP support!


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
oikjn
Honored Contributor

Re: 4730 Repaired - Readding to Cluster? FOM Question.

a FOM is NOT on a storage node, its on a seporate physical virtual machine host.  Its a VM that you install either on hyper-v or on vmware.  That said, if you have an even number of nodes and a total of less than 6 nodes, a FOM is the suggested method for maintaining quorum, but I see no reason why adding back in a repaired node will change what you should have been doing all along for quorum.

 

On another note.  you can join the node to the management group without really affecting anything.  do that, make sure its licensed correctly and that the available storage shows up correctly.  Then you can add it to a cluster, or if you have a node that is marked as missing, you can exchange it with that missing node.  Just keep in mind that a resync uses resources, so unless you manage the rebuild rate, it CAN cause your cluster to have performance problems.  You can adjust this by monitoring your cluster's performance and then adjusting the rebuild rate by going into the properties of the management group and adjusting the management group alloted bandwidth.  I think the default is 16MB/s, but you can turn it up or down depending on if you need more or less resources for Live Data.