Unsolved
This post is more than 5 years old
38 Posts
0
809
Best practice for multiple zone names each with distinct shares
Hi all,
I'm setting up a new cluster. I will be migrating our existing file systems to this cluster. Our environment consists of multiple different Windows and NFS file servers. We will want to keep the existing "hostnames" of these systems. Also I only want to show the shares that currently exist on that host. So for example:
host-a.domain.com = Share1 & Share2
host-b.domain.com = Share3
host-c.domain.com = Share4, Share5, Share6
I figured out one way to do this by creating a new Access Zone and assigning it to a new IP Address pool. My question is this the best way to go about this? I will have to create quite a few distinct IP address pools to accomplish my goal. It seems like I'm wasting a lot of IP's. Any guidance would be much appreciated!
Thanks!!
sluetze
300 Posts
1
August 19th, 2016 06:00
you could create aliases to point only to one
host-a.domain.com -> isilon.domain.com
host-b.domain.com -> isilon.domain.com
host-c.domain.com -> isilon.domain.com
this will spare you from wasting IPs, but won't enable you to only show the shares of the old host. To Achieve this you could work with Access Based Enumeration and Permissions (just SMB, not NFS).
if you are using nfsv3 you should definitely have a separate IP Address pool.
If consolidation is no option, you have to waste the amount of IP Addresses.
Rgds
--sluetze
dynamox
20.4K Posts
1
August 19th, 2016 07:00
Can't you take advantage of ABSE (access based share enumeration). Unless you have share access (yes you must configure share ACLs), the share will not be visible in \\isilon
ZBoT
38 Posts
0
August 19th, 2016 10:00
Thanks all! I'm going to look into using ABSE.