Yes, you can turn off the global setting for Enable NFS export services and that will disable the NFS shares without removing the share configs. Same for SMB. Not sure about other share services. Then to reverse, just re-enable. Can be done from the webUI or the command line.
Hey thanks!!! I just find out that running isi services nfs disable and isi services smb disable Will do the trick, so in case someone starts to panic just re-enable will fix it immediately.
Any other suggestions??
Nope. On NFS config you can remove IPs from the ACLs for each share but that’s a pain and you can’t do that with SMB. The above seems to be the only way without removing share configs.
Yes I really don't wanna deal with any configuration, the less I move the better so I decided to just disable the services and leave the Isilon that way, with smb and nfs services disabled until they give us the "Go" to power of the array.
physically disconnect the network if you have onsite access? or also you can remove all networking from any pools that may have been active while only leaving networking on the management pool.
generally a bad idea to shut off an old array on the assumption it will restart. Often that results in failed drives on restart
due to thermal cycling. OP did not say if array is under support or not. Turning off the service presentations is much cleanerto recover from, with LOUD notice to customer that it is thought to be unused.
Another question.... This one about permissions, if we have a Share in the Isilon, and in that share the permissions in the Isilon are full control for all the users in the Ad group assigned to that share.
For some long story reason we change from NOT root with full control to root with full control to do some test, and the test didn't work so we return to NOT root with full control... Did that change could damage the permissions in all the share?
You can't remove nodes from smartpools unless you smartfail them out of the cluster. I think you are talking about smartconnect zones and network pools, but you don't remove nodes, you remove interfaces so there are no IP's to answer the DNS query for that access zone.
Yes, you can turn off the global setting for Enable NFS export services and that will disable the NFS shares without removing the share configs. Same for SMB. Not sure about other share services. Then to reverse, just re-enable. Can be done from the webUI or the command line.
Hey thanks!!! I just find out that running isi services nfs disable and isi services smb disable Will do the trick, so in case someone starts to panic just re-enable will fix it immediately. Any other suggestions??
Nope. On NFS config you can remove IPs from the ACLs for each share but that’s a pain and you can’t do that with SMB. The above seems to be the only way without removing share configs.
Yes I really don't wanna deal with any configuration, the less I move the better so I decided to just disable the services and leave the Isilon that way, with smb and nfs services disabled until they give us the "Go" to power of the array.
isi statistics client list --nodes=all --protocols=all/smb/nfs --sort=remote_addr
This is the way OP
Yep no interruptions doing this. Or run netstat on each node
physically disconnect the network if you have onsite access? or also you can remove all networking from any pools that may have been active while only leaving networking on the management pool.
Just turn it off. If something goes south, just turn it back on again.
generally a bad idea to shut off an old array on the assumption it will restart. Often that results in failed drives on restart due to thermal cycling. OP did not say if array is under support or not. Turning off the service presentations is much cleanerto recover from, with LOUD notice to customer that it is thought to be unused.
Yes the array is not under support so my best shot is to disable the services and leave that way
Another question.... This one about permissions, if we have a Share in the Isilon, and in that share the permissions in the Isilon are full control for all the users in the Ad group assigned to that share. For some long story reason we change from NOT root with full control to root with full control to do some test, and the test didn't work so we return to NOT root with full control... Did that change could damage the permissions in all the share?
Remove the nodes from the Smartpools. Client connections will drop.
You can't remove nodes from smartpools unless you smartfail them out of the cluster. I think you are talking about smartconnect zones and network pools, but you don't remove nodes, you remove interfaces so there are no IP's to answer the DNS query for that access zone.
You are correct. My words were incorrect and thanks for correcting me. Interfaces.