Loading...
Loading...
Issue SyncIQ relies on properly configured DNS. If DNS is not properly configured, SyncIQ policies might fail to run. Symptoms Messages similar to the following appear in the /var/log/isi_migrate.log file: isi_migrate[10861]: coord[siqtest]: 5 nodes on target available: 1)10.1.215.1 2)10.1.215.2 3)10.1.215.3 4)10.1.215.4 5)10.1.215.6 .... isi_migrate[18315]: primary[siqtest]: Failed to connect to target worker 0 (10.1.215.6): connect failed: Operation timed out isi_migrate[18344]: primary[siqtest]: Failed to connect to target worker 0 (10.1.215.3): connect failed: Operation timed out
Cause When a SyncIQ policy is configured to target a SmartConnect zone name, SyncIQ connects to the nodes in that zone. When the policy starts to run, the source and target cluster communicate a list of available nodes. When DNS has not been properly configured with a delegation entry for the Isilon cluster s target SmartConnect zone name, the SyncIQ policy fails to run.
Solution Do the following: Open an SSH connection on any node in the cluster and log in using the "root" account. Run the nslookup command, where <target IP> is the IP address identified in the isi_migrate.log on the source cluster: nslookup <target IP> For example: nslookup 10.1.215.2 Output similar to the following appears: 2.215.1.10.in-addr.arpa name = cluster01-2.lab.example.com. 2.215.1.10.in-addr.arpa name = cluster02-2.lab.example.com. In the example above, two different names are returned for the same IP address. Correct any incorrect DNS SmartConnect zone names by running the following command, where <policy_name> is the SyncIQ policy and <ip_fqdn> i s the IP address or fully qualified domain name (FQDN) of the target cluster. isi sync policies modify --target-host=<ip_fqdn> <policy_name> SyncIQ should now function properly. Contact Isilon Technical Support if further issues are encountered.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.