We wanted to decommission nodes and LIF's homed onthese nodes. The problem is that some VMware NFS Datastores and also NFS file systems are using these LIF's/IP's, is there any way non-discruptively remove these LIF's/IP's?
My understanding is that we would be downtime to remount NFS datastores or file systems.
I have total of 8 nodes in the cluster. Planning on replacing two of them by adding two new ones first, then take two out. In the end, there would be still 8 nodes.
Understood I can lif move all lif's to the other two nodes(HA) without interruption. However, as I said, move lif's will also move all connections along with NFS datastores and file systems , it will put a lot of loads to those two nodes, causing unbalanced load.
I am thinking to manuall umount those NFS's connecting to two nodes going away, and remount them to two new nodes. That will have service downtime.
However, I have not sure an information with you: two new nodes have already added into the cluster, and now there are 10 nodes with new LIF's and new everything. Loads are already balanced across all 10 nodes.
Now, i just need to remove two old nodes. I can move all LIF's to the other nodes, which will cause unbalancing, and yet leave all old LIF's with old name convention (ex, nfs-lif-node1, nfs-lif-node2..) in the cluster forever, whereas node1 and node2 should be already gone. That is why I am thinking to take a downtime and remove all old lif's...
it makes sense.. the only issue with that is the downtime...
If you want to avoid downtime U have to migrate lifs. after lifs will be balanced across nodes (for better perf ensure that lif and volumes reside in the same node) and rename it according to your naming conv.
No. You cannot remove nodes that host volumes. If volumes are already relocated to another nodes, any traffic to LIFs on these nodes will go via interconnect to another node(s). So moving LIFs to nodes that actually host volumes will actually improve situation by avoiding indirection via cluster interconnect.