add ip range to management pool - risk of cutting arm off?

Question

Hi all,

We are expanding our cluster from 8 to ~24 nodes, but we only ever had a pool of 8 addresses for our mgmt network. we have some additional ranges within the same subnet that we can add that would allow us to join additional nodes to the cluster so that is not a problem. my question is, when I edit the existing pool and add the extra range in, do we run a risk of cutting our arm off remotely to the cluster? we currently use the Static allocation method, so I assume nothing would change to the current 8 nodes and their IP addresses and we should stay connected to the cluster?

if we cut our arm off remotely it could take sometime for the local team to resolve (we do not have console access ourselves).

Once the above is sorted we can then power on the nodes and add them to the cluster fine

also, would users recommend the web interface or CLI for adding in additional nodes?

Thoughts appreciated!

DELL-Sam L · Accepted Answer

Hello storageSysAdmin,

You should not have any issues as long as you follow the steps for adding ip address ranges in the administrator guide. I find it easier to use the gui to do most task, however I have also known customers that preferred the cli to make changes.

storageSysAdmin · Answer

you were correct, adding in additional ranges had no impact to our established connection and were able to expand the cluster fine

Isilon

add ip range to management pool - risk of cutting arm off?

Was this post helpful?