SyncIQ jobs can fail if there are nodes not on network (NANON) nodes.

Summary: SyncIQ jobs can intermittently fail if there are non-networked nodes (NANON).

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Conditions:

  1. Sync policies failing intermittently with error: "SyncIQ is unable to connect to a resource on the target cluster." 
  2. Recent upgrade to OneFS/PowerScale version, and,
  3. Source cluster contains non-networked (NANON) nodes.

    Also, SyncIQ's log /var/log/isi_migrate.log prior to upgrade shows "source nodes" exclude NANON nodes, while isi_migrate.log post upgrade includes NANON nodes.  
    Example command:
# zgrep -h 'source nodes' /var/log/isi_migrate.log* |sort

Cause

Post upgrade, SyncIQ can attempt to use nodes on the source cluster that are not networked (NANON). The issue is intermittent because sometimes, a worker that fails to connect can restart on a networked node. The policy is then able to complete. However, in other cases, the worker will attempt to restart on another NANON node and after several retries/failures on NANON nodes, the policy fails.
The issue can also occur if there are source nodes configured on a different subnet with no route to the target.

Resolution

Workaround:
Modify all policies to use a specific source network pool. Also set force interface and restrict target network options on the policy.
For example: 
# isi sync policies modify <policy name> --source-subnet <subnet> --source-pool <pool> --force-interface yes --restrict-target-network yes

Affected Products

Isilon SyncIQ

Products

Isilon
Article Properties
Article Number: 000187131
Article Type: Solution
Last Modified: 05 Dec 2025
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.