Troubleshooting Guides

DR Manager Configuration Sync Errors and Resolutions

Home




Message AEC_NOT_FOUND "Path 'X/Y/Z' Not Found: No Such File Or Directory" For Eyeglass Configuration Replication Job


Problem:


Eyeglass Configuration Replication Job fails with error AEC_NOT_FOUND "Path 'x/y/z' not found: No such file or directory". (Alarm code SCA0004)

This error is issued when the Eyeglass Configuration Replication job runs and attempts to replicate a share or export or quota when the associated directory does not exist on the target.

Resolution:


See below for the various reasons we see this error and their resolution (in bullets)

SyncQ Policy associated with the path has not been run and therefore the path does not exist on the target cluster

  • Ensure the SyncIQ policy has recently run on the cluster.

 The SMB Share or NFS Export path points to a path that does not exist on the Source cluster filesystem OR the share path does not match the path on the filesystem exactly (case-sensitive)

  • Review the SMB Share or NFS Export path on the source cluster and copy it to the clipboard and then SSH to the Source cluster and run command:   cd <pasted path>

  • If the cd command fails then either the path does not exist or there is a mismatch in the case-sensitivity of the path

 SyncIQ Policy has paths in the included or excluded list and the path that was not found is protected by the policy but is not in either list.

  • Review the policy configuration and determine if the excludes or includes are configured as expected.  Please note that using those options are not supported by Dell EMC for failover/failback

 SMB Share path has a trailing "/" at the end of the share path - example /ifs/home/

  • Remove the trailing "/" from the path of the share to resolve the error.

 

Once resolved the next Configuration Replication job will succeed and the alarm will be cleared.

 

Other possible causes for Missing Path on target cluster:


1) SyncIQ Policy associated with the path has not been run.

2) Path is on the SyncIQ Policy Excluded list.

3) SyncIQ Policy has paths in the Included or Excluded list and the path that was not found is protected by the policy but is not in either list.

 

Message AEC_FORBIDDEN For Eyeglass Configuration Replication Job


Problem:


Eyeglass configuration replication Job fails with error “AEC_FORBIDDEN…..”.


Possible Cause:


Isilon is provisioned in Eyeglass with a user who does not have minimum required privileges.

 

Troubleshooting Steps:


  1. Cross reference the permissions of the Isilon OneFS user that is used in Eyeglass provisioning with Minimum Required Privileges documented here: User Minimum Privileges.

  2. If the OneFS user does not have the required privileges, update the user privileges in OneFS.  The next Eyeglass configuration replication job will be based on these updated privileges.

  3. If the OneFS user has the minimum required privileges, double check the OneFS user privileges from the Isilon command line to ensure that they are set as required.

Message AEC_NOT_FOUND Zone <Zone Name> Not Found For Eyeglass Configuration Replication Job


Problem:


Eyeglass Configuration Replication Job fails with error “AEC_NOT_FOUND Zone <Zone Name> not found”. (Alarm code SCA0004)

 This error is issued when the Eyeglass configuration replication job runs and attempts to replicate a share or export when the associated Zone does not exist on the target.

Resolution:


Review the SyncIQ policy associated to the Configuration Replication job in error and determine the following information:

  • The SyncIQ policy source path on the Source cluster

  • What is the name of the Access Zone where that SyncIQ policy source path is a part of on the Source cluster?

  • What path is the SyncIQ policy target path replicating to on the Target cluster?

  • On the Target cluster, what is the name of the Access Zone where the SyncIQ policy target path is pointing to?

  • These Access Zone names need to be the same on source and target cluster otherwise you will receive the error in question.

Ensure that all Zones associated with shares and exports exist on the target.

Once the Zones exist, the next configuration replication job will succeed and the alarm will be cleared.


Message AEC_EXCEPTION Bad Hostname For Eyeglass Configuration Replication Job


Problem:


Eyeglass Configuration Replication Job fails with error “AEC_EXCEPTION message bad hostname 'host name'”. (Alarm code SCA0004)

 This means that Eyeglass cannot replicate the NFS Export to the target cluster due to a hostname listed on the NFS Export "Clients" list not resolving on the target cluster.

It is best practice to allow the DR cluster to resolve host names, or data will not be mountable after a failover.

 

Possible Causes:


NFS Exports "Clients" field has a host name entry that cannot be resolved on replication of the Export.

 

Resolution:


  1. Ensure that "Clients" field on the NFS Export on the source has valid host name entry.

  2. Run nslookup <hostname> to determine if that name resolves correctly or not

  3. Remove the host name from the clients list if not required any longer

  4. If unable to remove or make the name resolve in DNS you can use the Eyeglass CLI command:
    igls admin ignoreunresolvablehosts

  5. If issue still persists after running command to ignore then remove the export from the target cluster and allow Eyeglass to recreate it during Configuration Replication job

MESSAGE "AEC_NOT_FOUND", "message" : "Zone 'x' not found" For Eyeglass Configuration Replication Job


Problem:

This error will occur when Eyeglass attempts to replicate a share or export and the associated Zone does not exist on the target.

 

Possible Cause for Missing Zone:

1) Zone associated with share or export on the source cluster does not exist on the target cluster with the exact same name.

 

Solution:

Directory associated with the share or export or quota being replicated must exist on the target.

1) Run SyncIQ Policy to create the paths.

2) For SyncIQ Policy with Includes or Excludes, manually verify that the error relates to excluded paths and Job has succeeded for Included paths.

Zone associated with the share or export being replicated must exist on the target with the same name.

© Superna LLC