I think the wording is unclear. I believe what we're trying to say there is "put front-facing client protocol traffic in an access zone other than System", not "put SMB and NFS in different access zones". As you point out, that doesn't make any sense. Access Zones are a way of separating different groups that (can) use different authentication directory services. If you are implementing multi-protocol, there has to be a common source of identities for that to work and so all protocols you wish to use would be active in the same zone.
Hi All, I have a question regarding Access Zones in OneFS 8.2.2. The goal is to have a production and test access zone, each with their ownAD/domain. Two 10Gb interfaces are connected to the switch using LACP. OnIsilon there are 2 groupnets (since DNS servers are different withdifferent search domains) and 2 subnets, each with their own vlan-id. Two access zones are created (prod and test) with path:/ifs/isilon1/prod/ifs/isilon1/test I would like to segregate network traffic according to best practices andto move data access from System zone. Therefore, there should be accesszone for each protocol. In my case only SMB is used, so I need only oneaccess zone for SMB. The synciq and ndmp are also used, but they don'trequire the access zone. Since the best practice is to use unique paths for access zones, whatshould I use in this case? For example, should the root directory for SMB zone look like:/ifs/isilon1/smb or I need to use shared access zones, like:/ifs/isilon1/prod/smb It seems logical, that all shares should be created under prod/test zonesand related path, but this would mean use of shared access zones toseparate SMB traffic, if I understood everything correctly. Is there any better approach? Thank you in advance!
Multiple access zone config