[NAME], check this out. [URL] 
Hello All, as first, I apologize for the long post...The purpose of this post is to discuss some Isilon concepts/best practicesand to document it for myself, and maybe for some other people who are newto Isilon and find this helpful. This post will be based on the externalnetwork configuration, as I see it as the most complex part of the Isilon,and there are still some things which aren't clear enough to me. Idea is to make the "basic config" for external network configuration, whichcould be later easily modified/expanded if required. Let's assume we have following scenario: 1. Two Isilon Gen6 clusters - OneFS 8.2.X2. Both 10-gige interfaces connected3. The mgmt-1 interface connected4. One subnet for production, and one subnet for test, separated with 2 VLANs5. Two access zones (production and test), each with their own AD/DNS provider6. SyncIQ between Isilon clusters7. SMB and NFS protocols will be used, but will not access the same data8. NDMP backup9. Superna Eyeglass Based on my understanding of Isilon and documentation I would configure iton following way. a. NETWORK INTERFACES- According to the documentation the best practice is to use LACP if bothexternal NICs are connected- The mgmt-1 interfaces will be used only for cluster administration (WebUI/SSH) 1. If for some reason customer doesn't want to use LACP, do you stillconnect both interfaces, or just one?2. According to the below article there are some issues with the mgmt-1interface: [URL] Do you still use mgmt-1 interface with 2nd workaround from the article, oryou don't use it at all? b. SUBNETS/POOLS- let's assume the mgmt-1 interface is being used- since there should be 2 access zones with 2 different AD providers (notrust), there should be at least 2 groupnets- the 3rd groupnet may be needed if 1GB subnet is using different DNS settings- There should be following 3 subnets: SUBNET0 - 1GB ID: groupnet0.subnet0Name: subnet0Groupnet: groupnet0Pools: pool0Addr Family: ipv4Base Addr: 192.168.90.0CIDR: 192.168.90.0/24Description: Subnet for 1 GBDSR Addrs: -Gateway: 192.168.90.1Gateway Priority: 20MTU: 1500Prefixlen: 24Netmask: 255.255.255.0SC Service Addrs: 192.168.90.10-192.168.90.10SC Service Name:VLAN Enabled: TrueVLAN ID: 100 POOLSID: groupnet0.subnet0.pool0Groupnet: groupnet0Subnet: subnet0Name: pool0Rules: -Access Zone: SystemAllocation Method: staticAggregation Mode: lacpSC Suspended Nodes: -Description: Pool created for ssh accessIfaces: 1:ext-agg, 2:ext-agg, 3:ext-agg, 4:ext-aggIP Ranges: 192.168.90.11-192.168.90.14Rebalance Policy: autoSC Auto Unsuspend Delay: 0SC Connect Policy: round_robinSC Zone:SC DNS Zone Aliases:SC Failover Policy: round_robinSC Subnet:SC TTL: 0Static Routes: -   SUBNET1 - 10gB - prod ID: groupnet1.subnet1Name: subnet1Groupnet: groupnet1Pools: webui, smb, nfs, synciq, ndmpAddr Family: ipv4Base Addr: 192.168.91.0CIDR: 192.168.91.0/24Description: Subnet for productionDSR Addrs: -Gateway: 192.168.91.1Gateway Priority: 10MTU: 1500Prefixlen: 24Netmask: 255.255.255.0SC Service Addrs: 192.168.91.10-192.168.91.10SC Service Name:VLAN Enabled: TrueVLAN ID: 101 POOLSID: groupnet1.subnet1.webuiGroupnet: groupnet1Subnet: subnet1Name: webuiRules: -Access Zone: prodAllocation Method: staticAggregation Mode: lacpSC Suspended Nodes: -Description: Pool created for webui accessIfaces: 1:ext-agg, 2:ext-agg, 3:ext-agg, 4:ext-aggIP Ranges: 192.168.91.15-192.168.91.18Rebalance Policy: autoSC Auto Unsuspend Delay: 0SC Connect Policy: round_robinSC Zone:SC DNS Zone Aliases:SC Failover Policy: round_robinSC Subnet:SC TTL: 0Static Routes: - ID: groupnet1.subnet1.smbGroupnet: groupnet1Subnet: subnet1Name: smbRules: -Access Zone: prodAllocation Method: staticAggregation Mode: lacpSC Suspended Nodes: -Description: Pool created for smb accessIfaces: 1:ext-agg, 2:ext-agg, 3:ext-agg, 4:ext-aggIP Ranges: 192.168.91.19-192.168.91.22Rebalance Policy: autoSC Auto Unsuspend Delay: 0SC Connect Policy: round_robinSC Zone:SC DNS Zone Aliases:SC Failover Policy: round_robinSC Subnet:SC TTL: 0Static Routes: - ID: groupnet1.subnet1.nfsGroupnet: groupnet1Subnet: subnet1Name: nfsRules: -Access Zone: prodAllocation Method: dynamicAggregation Mode: lacpSC Suspended Nodes: -Description: Pool created for nfs accessIfaces: 1:ext-agg, 2:ext-agg, 3:ext-agg, 4:ext-aggIP Ranges: 192.168.91.27-192.168.91.34Rebalance Policy: autoSC Auto Unsuspend Delay: 0SC Connect Policy: round_robinSC Zone:SC DNS Zone Aliases:SC Failover Policy: round_robinSC Subnet:SC TTL: 0Static Routes: - ID: groupnet1.subnet1.synciqGroupnet: groupnet1Subnet: subnet1Name: synciqRules: -Access Zone: SystemAllocation Method: staticAggregation Mode: lacpSC Suspended Nodes: -Description: Pool created for synciq accessIfaces: 1:ext-agg, 2:ext-agg, 3:ext-agg, 4:ext-aggIP Ranges: 192.168.91.35-192.168.91.38Rebalance Policy: autoSC Auto Unsuspend Delay: 0SC Connect Policy: round_robinSC Zone:SC DNS Zone Aliases:SC Failover Policy: round_robinSC Subnet:SC TTL: 0Static Routes: - ID: groupnet2.subnet1.ndmpGroupnet: groupnet1Subnet: subnet1Name: ndmpRules: -Access Zone: SystemAllocation Method: staticAggregation Mode: lacpSC Suspended Nodes: -Description: Pool created for ndmp accessIfaces: 1:ext-agg, 2:ext-agg, 3:ext-agg, 4:ext-aggIP Ranges: 192.168.91.39-192.168.91.42Rebalance Policy: autoSC Auto Unsuspend Delay: 0SC Connect Policy: round_robinSC Zone:SC DNS Zone Aliases:SC Failover Policy: round_robinSC Subnet:SC TTL: 0Static Routes: - SUBNET2 - testID: groupnet2.subnet2Name: subnet2Groupnet: groupnet2Pools: smb, nfsAddr Family: ipv4Base Addr: 192.168.92.0CIDR: 192.168.92.0/24Description: Subnet for test zoneDSR Addrs: -Gateway: 192.168.92.1Gateway Priority: 30MTU: 1500Prefixlen: 24Netmask: 255.255.255.0SC Service Addrs: 192.168.92.10-192.168.92.10SC Service Name:VLAN Enabled: TrueVLAN ID: 102 ID: groupnet2.subnet2.smbGroupnet: groupnet2Subnet: subnet2Name: smbRules: -Access Zone: prodAllocation Method: staticAggregation Mode: lacpSC Suspended Nodes: -Description: Pool created for smb accessIfaces: 1:ext-agg, 2:ext-agg, 3:ext-agg, 4:ext-aggIP Ranges: 192.168.92.11-192.168.92.14Rebalance Policy: autoSC Auto Unsuspend Delay: 0SC Connect Policy: round_robinSC Zone:SC DNS Zone Aliases:SC Failover Policy: round_robinSC Subnet:SC TTL: 0Static Routes: - ID: groupnet2.subnet2.nfsGroupnet: groupnet2Subnet: subnet2Name: nfsRules: -Access Zone: prodAllocation Method: dynamicAggregation Mode: lacpSC Suspended Nodes: -Description: Pool created for nfs accessIfaces: 1:ext-agg, 2:ext-agg, 3:ext-agg, 4:ext-aggIP Ranges: 192.168.92.15-192.168.92.22Rebalance Policy: autoSC Auto Unsuspend Delay: 0SC Connect Policy: round_robinSC Zone:SC DNS Zone Aliases:SC Failover Policy: round_robinSC Subnet:SC TTL: 0Static Routes: - 1. How do you name the pools? Like pool0, pool1... or do you use smb,nfs...?2. How do you name the subnets? Like subnet0, subnet1... or something else?3. Do you use System zone for NDMP backup in this scenario or prod/test? c. ACCESS ZONES- let's assume following cluster1 hostname: isilon1cluster2 hostname: isilon2 - best practice for root based directory is to name it /ifs/ /  1. On cluster isilon1 we create following 2 access zones: Root base directory for production zone: /ifs/isilon1/prodRoot base directory for test zone: /ifs/isilon1/test 2. On cluster isilon2 we create following 2 access zones: Root base directory for production zone: /ifs/isilon2/prodRoot base directory for test zone: /ifs/isilon2/test 3. In case Superna Eyeglass is used, we need to create (if I understand itcorrectly) additional 2 access zones on each cluster, in order thatEyeglass can failover DFS shares to the other cluster. As I understand it,failover must be performed to the Access zone on the other cluster. If thisis correct we need to create/modify access zones and in the end it couldlook like this with 4 access zones on each cluster: a. On isilon1 Root base directory for isilon1 production zone: /ifs/isilon1/prodRoot base directory for isilon1 test zone: /ifs/isilon1/testRoot base directory for isilon2 production zone: /ifs/isilon2/prodRoot base directory for isilon2 test zone: /ifs/isilon2/test b. On isilon2 Root base directory for isilon1 production zone: /ifs/isilon1/prodRoot base directory for isilon1 test zone: /ifs/isilon1/testRoot base directory for isilon2 production zone: /ifs/isilon2/prodRoot base directory for isilon2 test zone: /ifs/isilon2/test Is this the best way to do it, or there is some other recommended way? d. SHARES/EXPORTS- Considering above, directory path for shares/exports should be as following: /ifs/ / / /  For example for production zone on isilon1: 1. SMB share /ifs/isilon1/prod/smb/share1 2. NFS export /ifs/isilon1/prod/nfs/nfs_export1 For example for test zone on isilon1: 1. SMB share /ifs/isilon1/test/smb/share1 2. NFS export /ifs/isilon1/test/nfs/nfs_export1 e. ADDITIONAL QUESTIONS 1. Is the above design recommended and according to the best practices?2. In case you need to have access to the same data using multipleprotocols (smb/nfs), how would you design access zones in this scenario?2. Every now and then I stumble upon some articles where it's mentionedthat you can divide the network by multiple subnets (each with own vlanid).For example you can have one subnet for smb, one subnet for nfs, one subnetfor synciq, one subnet for ndmp... However, I couldn't find some detaileddocumentation about it. Is this approach possible, and what are thecons/pros of this approach compared to the one described in this post? Please comment/share your experience on above topics. Thank you all!
Network design/considerations