UNSOLVED

mouad_idelhadj

updated

9 years ago

0

2007

June 17th, 2017 17:00

single SmartConnect zone - multiple Aliases

Hello Isilon experts,

I have an ISILON customer with two site configuration. As they have limited range of IP addresses, we can’t afford many IP pools, thus we have to use few SmartConnect zones.

The issue here is that the customer wants to make many SyncIQ policies in order partial failovers when needed. So I thought maybe I can use a unique SmartConnect Zone with many aliases and declare only the aliases on the DNS.

Below the suggested config:

SITE1 SITE2
SmartConnect Zone site1.customer.com SmartConnect Zone site2.customer.com
SSIP 10.10.10.10 SSIP 10.20.10.10
Pool1 10.10.10.100 - 10.10.10.110 Pool1 10.20.10.100 - 10.20.10.110
AccessZone NAS_Prod AccessZone NAS_Prod
Alias1 smbprod1.customer.com Alias1 smbprod1.customer.com
Alias2 smbprod2.customer.com Alias2 smbprod2.customer.com
Alias3 smbprod3.customer.com Alias3 smbprod3.customer.com
Alias4 nfsprod1.customer.com Alias4 nfsprod1.customer.com
Alias5 nfsprod2.customer.com Alias5 nfsprod2.customer.com

So if I failover only the application running on nfsprod1.customer.com, I would only change the delegation for one Alias and keep the rest intact :

DNS Delegations
Before Failover After Failover
Subzone NS Subzone NS
smbprod1.customer.com 10.10.10.10 smbprod1.customer.com 10.10.10.10
smbprod2.customer.com 10.10.10.10 smbprod2.customer.com 10.10.10.10
smbprod3.customer.com 10.10.10.10 smbprod3.customer.com 10.10.10.10
nfsprod1.customer.com 10.10.10.10 nfsprod1.customer.com 10.20.10.10
nfsprod2.customer.com 10.10.10.10 nfsprod2.customer.com 10.10.10.10

What do you think about this config and do you see any limitations.

In addition to that, the customer is thinking about purchasing Superna Eyeglass license in the future; do you think of any drawbacks of this setup with Eyeglass way of managing failovers?

Thanks in advance

Regards

--

Mouad IDELHADJ

  • sluetze

    2 Intern

    300 Posts

    1316

    1

    Posted June 19th, 2017 05:00

    for smb i would rather use a dfs-structure for Failover since I only have to failover the syncIQ policy and do nothing else (this is also supported by superna).

    this construct could work and you can also integrate "custom-scripts" to automate the DNS changes in superna. afaik the construct above is unsupported from superna.

    since i have enough IPs i don't have to use such constructs so i can't talk from practice.