Kinda. I've looked for EMC documation on that but not coming up with anything. The DNS server has access to subnet0, and can properly return a value for isilon.domain.local. That is correct. If you feel anything is missed out, feel free to comment and I will try to cover the topics. Zone name: isilon.nfs.domain.local; SmartConnect service subnet: subnet1 ; The following graphic details the typical look-up process for the isilon.domain.local SmartConnect Zone. September 2020 Updated ‘DNS delegation best practices’ and ‘SmartConnect in isolated network environments’ sections. <<. Because with the config you proposed above if you have a system that only resides on 172.16.1.x network, it will no longer able to use smartconnect to connect to the cluster. Subnet0/pool0 aren’t isolated. Mine is the same way, I believe it is because dcdiag is checking the delegation with the assumption that the delegate NS is a real NS, while the NS for SmartConnect is strictly for Isilon. subnet1 – 10.16.1.x (customer 1) |, Configuring EMC Isilon SmartConnect – Part I: SmartConnect Basic, How to update VMware Windows VM's DNS using PowerCLI - Mike Tabor, PowerCLI cmdlets: Get/Set-VMGuestNetworkInterface, Query the Isilon Fully Qualified Domain Name (isilon.domain.local), DNS delegates the query to the SmartConnect Service IP (ssip.domain.local DNS record), SmartConnect gives out the SmartConnect Zone Name, The FQDN is accessed by the Management Network, Query the Isilon Fully Qualified Domain Name (isilon.nfs.domain.local), DNS delegates the query to the SmartConnect Service IP (ssip.nfs.domain.local DNS record), Update the DNS Delegation to point to ssip.domain.local, Update the SmartConnect service subnet for subnet1/pool1 to use subnet0 to answer SmartConnect queries, The FQDN is accessed by the NFS Data Network. I'm having some troubles trying got the isilon smartconnect load balancing working. customer 1 and customer 2 networks are firewalled (or not routed). You should setup two pools, one static pool for SMB and one dynamic for NFS work flows. DNS Dual delegation validation check that all smartconnect names are correctly setup for DNS auto failover. if dualdelegation_use_eyglass_dns is true, instead of taking the DNS server from the isilon's groupnet, get the DNS server from the local OS, and issue the dual dns delegation validation request(s) to that DNS server instead. Please Login or Join the community to continue to read. I use it myself on a bunch of different servers. You can specify domain name server addresses in IPv4 or IPv6 format. Checks that 2 name servers are setup, verifies an A record correctly points to Isilon SSIP, validates the SSIP is the correct subnet for the pools that are failing over. Isilon is Dell EMC’s scale out storage platform. Content published here is not read, reviewed, or approved in advance by Pure Storage and does not necessarily represent or reflect the views or opinions of Pure Storage or business partners. 4. It was strange the connection would authenticate when using the isilon’s delegation record, but fail when connecting via the alias record which points at the same delegation record. On the BIND server all I did was forward any request going to nas1.xyz.com to go to 10.x.x.x. System on the isolated network cannot leverage SmartConnect. The first network defined for the “front-end” is typically configured as subnet0. Conclusion. Your email address will not be published. I’ve tried this, and it does work. Set up DNS for SmartConnect Thank you for your feedback! But this doesn’t work… Because there is no connectivity from our DNS server to our SmartConnect Service IP for our second Zone (isilon.nfs.domain.local). For more such videos subscribe to the channel. Above are the most common EMC Isilon interview questions. 2. Because the DNS server does not have access to subnet1, it cannot delegate to the SmartConnect service IP (172.16.1.80) for resolution of isilon.nfs.domain.local. We’ll see what my TC says about filling out some paperwork for RFE. You can watch the below video that explains the configuration of SmartConnect DNS in Isilon. Users connecting directly to the Isilon’s delegation dns record could successfully connected to their shares. This site uses Akismet to reduce spam. As previously stated, this isn’t the preferred method. Upon standing up a new cluster tonight, I realized that the above method also works for subnets/zones that do not have a SSIP associated with it. Because the DNS server does not have access to subnet1, it cannot delegate to the SmartConnect service IP (172.16.1.80) for resolution of isilon.nfs.domain.local. You must also provide a zone delegation to the fully qualified domain name (FQDN) of the SmartConnect zone in your DNS infrastructure. When this is the case, and isolated networks are being used, it is impossible to leverage SmartConnect on the isolated network, unless there is a DNS, and subsequent delegation, in that isolated network. This section covers the completion of the SmartConnect configuration. i work at a big university with many distinct customers/ network zones ..so sure, i consider myself a service provider . Saved from jasemccarty.com. Once this is done, SmartConnect assigns the workload to each node using the round-robin method. That would require yet another subnet and subnet1 and subnet2 would have to be able to access subnet3. The data is rebalanced to utilize the new node, and the extra storage is added to your total available capacity, all without any downtime. Name * Email * Website. Part 1 is redirecting your DNS requests to the secondary Isilon; this is a simple step in your DNS server where you change the DNS delegation. Configuring EMC Isilon SmartConnect – Part III: Isolated Storage Networks. Pool1 on the other hand, is configured for a SmartConnect service subnet of subnet1. When a client queries their DNS server, the DNS server will delegate the DNS lookup to the SmartConnect Service IP. This site uses Akismet to reduce spam. Any connection to the SmartConnect IP will use Round Robin to load balance user connections to your cluster, using the external IP range you provided earlier. You still only need one DNS delegation (NS) entry which could be cluster.company.com and then anything which ends in cluster.company.com would be forwarded to the SmartConnect service ip address to be resolved. Notice how each pool is leveraging the SmartConnect service subnet that it resides in? I tried setting up the same forward on infoblox and when I do a lookup against nas1.xyz.com I get server failed. In our DNS Management interface, we need to make a New Delegation. Pool0, which is part of subnet0, is using the SmartConnect service subnet of subnet0. August 2020 thAdded ‘Isilon 6 generation 1 GbE interfaces’ and ‘VLAN and interface MTU’ sections. How can this happen if the SmartConnect Service IP for that zone is on an isolated network? Required fields are marked * Comment. In my previous posts (SmartConnect Part I & SmartConnect Part II) the SmartConnect Zone was on the same subnet/pool. In the Domain name server(s) field, enter up to three domain name server IP addresses. Isilon SmartConnect - DNS Delegation - When a client queries their DNS server, the DNS server will delegate the DNS lookup to the SmartConnect Service IP. Each node does have its own IP assigned from a pool of IP address… Thanks go to James Walkenhorst for his input. I was able to do this on a BIND dns server just fine. Above config in place Making a couple changes will correct the issue. DNS search suffixes are appended to unqualified host names . When we delegate the DNS control to Isilon when your client tries to make the connection Isilon will return an IP of an active node (I only have one node, but if it were a real cluster, this is very important). Keep in mind, that DNS needs to contact the SmartConnect Service IP to request an IP resolution for the FQDN. In standing up a new cluster, I left the SmartConnect service IP blank (not really using it on the isolated network), and it still works. Users which used the dns alias record were getting logon failures to the same share. February 2021 Updated ‘IPMI’ section. Expand the Isilon sub domain; Remove Original A Record for the Old SmartConnect IP; Create an A Record for the New SmartConnect IP; Adjust Delegation in DNS to point to the new SmartConnect IP 3. So you are looking at this from a Service Provider perspective. As if that weren’t enough information about SmartConnect, there are more scenario-based descriptions of hot networking topics such as where the SmartConnect service runs, what happens when you replace nodes while SmartConnect is active, and … It is a common practice to leverage subnet0 for the management of an Isilon cluster. that’s yet another subnet that i have to request just for SmartConnect to work and establish connectivity between two networks that should have no inter-connectivity at all, not likely to happen. On the BIND server all I did was forward any request going to nas1.xyz.com to go to 10.x.x.x. When you create the NS record for and Isilon SmartConnect Zone, is there any reason to add a "a" record for that entry as well? Any of my code, configuration references, or suggestions, should be researched and verified in a lab environment before attempting in a production environment.