Thanks sjones, i understand isilon's subnet only can belong to single groupnet.

Hi tezusky,

This is by design, and I am not aware of any plan to change this. Groupnets are designed to enable multi-tenant DNS support per access zone.

This explanation comes from the OneFS 8.0.0 Release notes on page 12:

Multi-tenant DNS support

OneFS 8.0.0 supports multiple DNS servers for each access zone so different tenants

that operate on the same Isilon cluster can use different DNS servers to perform host

name lookups. DNS servers are configured by a new network object called a

groupnet, which lives above a subnet. Each groupnet is associated with a single

access zone. The default system access zone is automatically associated with the

default groupnet. Authentication providers that communicate with an external server

must be associated with a groupnet. The DNS cache has been enhanced to maintain

separate caches for separate groupnets. You must create new access zones in order

for the groupnets to be used by protocols. The protocols that support groupnets are

SMB, NFS, HDFS, and Swift.

For each AD domain there will be one access zone on the cluster

(not counting the system access zone).

From a networking standpoint, the access zones are configured at the

same level as the SmartConnect zones, namely on the address pool level.

So you would use

one groupnet

one subnet

two address pools (specific IP addresses used by Isilon nodes, not clients)

     - per pool: one SmartConnect zone, one access zone, one AD domain

Makes sense?

-- Peter

Thank you, Peter. In our case, we have to consolidate CIFS servers on 2 VNX to the single isilon from two separate AD domains. There's no DNS forwarding or other equivalent feature between these AD domains, so we need to have 2 groupnets as per DNS server.