Eyeglass Isilon Edition 1.5.3 Release Notes

Supported OneFS releases


7.1.1.x

7.2.0.x

7.2.1.x

8.0.0.x


Feature Release Compatibility


Feature

Source Cluster  Release

Target SyncIQ Cluster Release

Configuration Replication

non-DFS mode



 Configuration Replication

7.1.1.x

7.1.1.x

 Configuration Replication

7.2.0.x

7.2.0.x

Configuration Replication

 7.2.1.x

7.2.1.x

Configuration Replication

8.0.0.x

8.0.0.x

Configuration Replication

DFS mode



  Configuration Replication - DFS Mode

 7.1.1.3 and higher

 7.1.1.3 and higher

 Configuration Replication - DFS Mode

7.2.0.x

7.2.0.x

Configuration Replication - DFS Mode

 7.2.1.x

7.2.1.x

Configuration Replication - DFS Mode

8.0.0.x

8.0.0.x

SyncIQ Policy Failover

non-DFS mode



SyncIQ Policy Failover

7.1.1.x

7.1.1.x

SyncIQ Policy Failover

7.2.0.x

7.2.0.x

SyncIQ Policy Failover

7.2.1.x

7.2.1.x

SyncIQ Policy Failover

8.0.0.x

8.0.0.x

SyncIQ Policy Failover

DFS mode



SyncIQ Policy Failover - DFS mode

 7.1.1.3 and higher

 7.1.1.3 and higher

SyncIQ Policy Failover - DFS mode

7.2.0.x

7.2.0.x

SyncIQ Policy Failover - DFS mode

7.2.1.x

7.2.1.x

SyncIQ Policy Failover - DFS mode

8.0.0.x

8.0.0.x

Access Zone Failover



Access Zone Failover

7.2.0.x

7.2.0.x

Access Zone Failover

7.2.1.x

7.2.1.x

Access Zone Failover

8.0.0.x

8.0.0.x

Runbook Robot

SyncIQ Policy Failover



SyncIQ Policy Failover

7.1.1.x

7.1.1.x

SyncIQ Policy Failover

7.2.0.x

7.2.0.x

SyncIQ Policy Failover

7.2.1.x

7.2.1.x

SyncIQ Policy Failover

8.0.0.x

8.0.0.x

Runbook Robot*

Access Zone Failover



Access Zone Failover

7.2.0.x

7.2.0.x

Access Zone Failover

7.2.1.x

7.2.1.x

Access Zone Failover

8.0.0.x

8.0.0.x

Live Ops - DR Test Mode



Live Ops DR Test Mode

7.2.0.x

7.2.0.x

Live Ops DR Test Mode

7.2.1.x

7.2.1.x

Live Ops DR Test Mode

8.0.0.x

8.0.0.x




Feature Support Matrix


Description

Supported

Overlapping Access Zone with System (/ifs)


Configuration Replication (non DFS mode)

Yes - Create / Update

No -  Delete

Configuration Replication (DFS mode)

Yes - Create / Update

No - Delete

SyncIQ Failover

Yes

SyncIQ Failover - DFS Mode

Yes

Access Zone Failover

No

Overlapping Access Zone - non System Zones


Configuration Replication (non DFS mode)

Yes - shares / export / alias

No - Access Zone

Configuration Replication (DFS mode)

Yes

No - Access Zone

SyncIQ Failover

Yes

SyncIQ Failover - DFS Mode

Yes

Access Zone Failover

No



End of Life Notifications


Description

End of Life Date

Superna Eyeglass Appliance operating system version OpenSUSE 13.1


The OpenSUSE 13.1 operating system is End of Life for the Superna Eyeglass Appliance.  Operating system update to OpenSUSE 13.2 will be required to maintain a supported appliance.  Upgrade procedure is here

March 31, 2016

End of Support for 1.2, 1.3, 1.4 and 1.4.x Superna Eyeglass Releases

All customers running the above releases should upgrade to 1.5.3 release using upgrade guide located here.  Numerous failover and performance improvements exist in 1.5.x, so earlier releases are end of support with all new cases requiring an upgrade.


April 25, 2016


Superna Eyeglass Isilon Support Agreement can be found here.


What’s New in Superna Eyeglass Isilon Edition Release 1.5.3

Disaster Recovery Planning and Execution

Superna Eyeglass Access Zone Failover Readiness New “Target Writes Disabled” Validation

Access Zone Failover Readiness now has an additional criteria “Target Writes Disabled” which is automatically validated to ensure that the target folder of SyncIQ policy has writes disabled before attempting a failover.  This condition indicates an error since the target cluster is already allowing writes, which should not be the case before failover.


Superna Eyeglass SyncIQ Policy DR Status Criteria - MODIFIED

As of Superna Eyeglass Release 1.5.3, the SyncIQ Policy DR Status in Eyeglass will be either Warning, SyncIQ Running or OK.  The Error state has been eliminated such that a SyncIQ Policy error will no longer block you from initiating a failover with Eyeglass.  In this case depending on what the SyncIQ Job state was and/or if previous problem has been resolved the Eyeglass failover step to run the policy may still fail.


IMPORTANT: SyncIQ Policy in Warning state MAY NOT be able to be run by Eyeglass assisted failover depending on it’s current status.  If not run, you will incur data loss during failover.  

Example 1: SyncIQ Policy has an error state.  If it cannot be run from the OneFS it will also not be able to run from Eyeglass.  

Example 2: SyncIQ Policy is paused.  Eyeglass failover cannot RESUME a paused SyncIQ Policy - this must be resumed from OneFS

You must investigate these errors and understand their impact to your failover solution.


Please refer to the Eyeglass Admin Guide for details:

http://documentation.superna.net/eyeglass-isilon-edition/Eyeglass-Isilon-Edition#TOC-Policy-Readiness-and-DFS-Readiness

http://documentation.superna.net/eyeglass-isilon-edition/Eyeglass-Isilon-Edition#TOC-Zone-Readiness

http://documentation.superna.net/eyeglass-isilon-edition/Eyeglass-Isilon-Edition#TOC-Zone-Readiness---OneFS-SyncIQ-Readiness



Superna Eyeglass Administration

Superna Eyeglass Schedule Format

The Superna Eyeglass schedules are now stored and displayed using a crontab format.  For example:

igls admin schedules list

[

   {

       "interval": "0 0 * * *",

       "enabled": true,

       "id": "InventoryReport",

       "label": "Eyeglass Reports"

   },

   {

       "interval": "*/15 * * * *",

       "enabled": false,

       "id": "PrintInventoryToSyslog",

       "label": "Print Inventory to Syslog"

   },

   {

       "interval": "*/15 * * * *",

       "enabled": false,

       "id": "Readiness",

       "label": "Zone Readiness"

   },

   {

       "interval": "*/5 * * * *",

       "enabled": true,

       "id": "Replication",

       "label": "Configuration Replication"

   },

   {

       "interval": "0 0 * * *",

       "enabled": true,

       "id": "RunbookRobot",

       "label": "Runbook Robot"

   }

]



There is no change to igls admin schedules commands used to set the schedule.



Issues Resolved in Release 1.5.3


Technical Advisory #5 - Incomplete response from Isilon PAPI may result in deletion of Configuration Objects

Eyeglass 1.5.3 release contains defensive code to guard against deletion of configuration objects when the Isilon PAPI becomes unresponsive such that Eyeglass requests for configuration objects are unanswered (for example 503 Service Unavailable). When this condition is detected, Eyeglass does not update it’s database.  The information from the last previously successful Configuration Replication task remains in the database and is used in the next Configuration Replication task.  In the case that this happens:

  • No delete action will occur on ANY configuration objects

  • You may see an Audit Failed alarm should the post replication audit succeed in retrieving the latest configuration information from the cluster and it does not match the target cluster.

  • You will receive the following Critical alarm if the retrieval of any one of NFS Exports, NFS Alias, SMB Shares, Quotas, Access Zones or SyncIQ policies fail

    • Message: Failed to retrieve inventory

  • You will receive the following minor alarm if the retrieval of any cluster configuration other than NFS Exports, NFS Alias, SMB Shares, Quotas, Access Zone or SyncIQ policies

    • Message: Inventory is degraded/incomplete

—————————————————–—————————————————–

T1434:  Eyeglass Trial License does not respect License Limits

The Eyeglass Trial License limits for Jobs and Shares/Export/Alias/Quota were not being respected such that fewer Jobs/Shares/Exports/Alias and Quotas than were licensed were being managed.

Resolution: Trial License logic error has been rectified such that the Trial License limits as provided are respected.

—————————————————–

T1382: SyncIQ Policy shows Error state in Eyeglass when it is not in Error state in OneFS

For the case where a SyncIQ Job has just completed running when Eyeglass checks the status, there may occur a case where the SyncIQ Job details are returned with unexpected results. For example, the Last Success time is not populated when Eyeglass discovery occurs even though the Job has successfully completed in OneFS.  In this case the SyncIQ Job will show with Error in the DR Dashboard.  This condition is transient and will be cleared on the next Configuration Replication cycle but does result in a Critical Alarm indicating that the Job is in error state.

Resolution: To handle these unexpected results, Eyeglass now only uses the SyncIQ Policy last Job state to calculate SyncIQ Policy DR Status.  The DR Dashboard has been updated to display the SyncIQ Policy state.

SyncIQ Policy Last Job State

Eyeglass SyncIQ DR Status

finished

OK

scheduled, running

SyncIQ Running

empty

(policy has never been run)

Warning

error, paused, cancelled

Warning


—————————————————–

T1428: Custom DFS Prefix has Replication Error

When Eyeglass is configured for a custom DFS prefix which allows igls-dfs prefix to be changed to another string used with all shares on the DR cluster, the initial Configuration Replication task successfully creates the share but subsequent replication cycles do not recognize the share on the target and continually attempt to create the share again.  This results in a continual Configuration Replication error for this Job.

Resolution: The custom prefix is now recognized.  After the initial Configuration Replication cycle which creates the share, subsequent cycles identify that the share exists and execute an update operation.



Known Issues


1462 - Export max_file_size cannot be replicated

Updated export max_file_size parameter is not replicated and replication Job fails.

———————————-


896: YaST Update Manager inconsistent between recommended and optional updates

Description: Updates are listed with icon for “recommended” but appear in “optional” summary.

Workaround: None Required. Any updates from Superna are recommended and should be applied.

———————————-


924: Inventory View shows + beside component when there are no more children

Description: In the Inventory View, components for which there are no children still show a “+” in the inventory tree. When you select the “+”, it changes to a “-” but there are no children displayed.

Workaround: None Required.

—————————————–


943: Inventory View not auto-refreshed

Description: Inventory View is not auto-refreshed and if open when a change occurs does not reflect the change.

Workaround: Use the Refresh Now button or close and reopen the Inventory View.

————————————————–


1080: New inventory may not appear in change management report for alarms

Description: Should change management report run before newly added object is discovered in inventory, there will be no associated change report associated to an alarm from that object until it is discovered by inventory.

Workaround: None available

—————————————————–


1138: Eyeglass UI does not block configuration of duplicate remote logging service

Description: If you configure the same remote logging service twice in Eyeglass, the forwarding of logs to the logging service will fail

Workaround: Only configure 1 instance of a remote logging service.

—————————————————–


1213: Change Management Report for all Isilon Clusters

Description: Change records for both Isilon Clusters managed on an Eyeglass appliance will be provided in a single report.

Workaround: None Available

—————————————————–


1354: Update export path creates new export instead of updating existing one

Description: When the path for an export where only a single export is specified is modified, the Eyeglass replication Job creates a new export on the target based on the updated path and leaves the previous export on the target.  

Workaround: Manually remove the old export from the target using Isilon OneFS.

—————————————————–


1355: Edit Job configuration to include share/export deselected from another Job causes share/export to be reselected.

Description: When you edit a Job B configuration to include share/export that had already been deselected from Job A, this causes this share/export to be reselected for Job A as well.  

Workaround: None available.  Should the share/export subsequently be deselected from Job B it should then also be manually deselected again from Job A.

—————————————————–


1580: Delete and Create export within same replication cycle orphans deleted export on the target with OneFS 7.1.1.x

With OneFS 7.1.1.x, a delete and create export operation which occurs within the same replication cycle will replicate the export that was created on the next replication cycle but the export deleted on the source will not be deleted on the target.  

Workaround: Manually remove the deleted export from the target using Isilon OneFS.

—————————————————–

1612: Some alarms not cleared

Alarms other than the “Replication job failed to run “ are not cleared automatically once the error condition has been resolved.

Workaround: Clear the alarm manually from the Eyeglass UI.

—————————————————–


1625: Custom QUOTA Jobs require extra replication cycle to be deleted

In the Eyeglass Jobs window, when you delete a CUSTOM Job and then the associated QUOTA Job is not immediately deleted.  It is deleted on the next replication cycle.

Workaround: None required.

—————————————————–


1639: Able to manually Run Now disabled Custom Job

Eyeglass Jobs window allows you to Run Now on a Custom Job which has been disabled.  A message is displayed indicating that the Job has been queued but the share/export configuration replication Job is not run and the associated QUOTA Job is run and quotas are replicated.

Workaround: Do not Run Now for Custom Job that has been Disabled.

—————————————————–


1641: Custom Job does not include shares/export when source or destination path configured with a trailing /

If you enter source or destination path for Eyeglass Custom Job with a trailing / (for example /ifs/data/test/ ), the Custom Job will not pick up the related shares and exports.

Workaround: Source and destination paths must be entered without the trailing / - for example /ifs/data/test.

—————————————————–




1788: Delete of unlinked user quota on source may not delete matching quota on the target

Attempting a quota replication after deleting an unlinked user quota may fail to delete the quota on the target with a Job status of success but an Audit failure.

Workaround: Deleted quota manually deleted on the target.

—————————————————–


1789: Able to select shares/exports/quotas outside job path after deselected

After a share/export/quota has been deselected from an Eyeglass Job, it can be re-selected for a different Job even if it is outside the Job path.  As a result, the Job may have  an error for these share/export/quota due to path not found error.

Workaround: Do not customize Eyeglass configuration replication Job and select share/export/quota that are outside the Job path.

—————————————————–


1887: Multiple SyncIQ policies associated with same Zone will result in transient error on Eyeglass Zone replication creation

Where there are multiple SyncIQ policies which are associated to the same zone and Eyeglass configuration replication is being used to create the zone on the target, the first Zone replication job will succeed, but subsequent Zone replication jobs for the same Zone will fail with the message “Zone ‘<zone name>’ already exists”.

Workaround: None required.  Error will be cleared on subsequent configuration replication cycle.

—————————————————–



1924: Quotas on excluded SyncIQ directory are selected for replication

Eyeglass quota job includes quotas related to excluded SyncIQ directories.  If quota job is run, it will typically fail due to path not found.

Workaround: Customize Quota Job and deselect quotas for excluded directories.

—————————————————–


1998: Custom Eyeglass configuration replication Job does not have an associated Zone replication Job

When you create a new custom Eyeglass Job, an associated Zone replication Job is not created.

Workaround: Zone must be created manually or already exist on the target cluster in order for Eyeglass configuration replication to succeed.

—————————————————–


2004: Custom Quota Job is incorrectly listed in the Failover: Quota Failover (RUN MANUALLY) section in the Jobs window

When you create a new custom Eyeglass Job, the associated Quota replication Job is created and incorrectly listed under Failover: Quota Failover (RUN MANUALLY) section in the Jobs window.  Custom Quota Jobs do not need to be run manually, they are run automatically each time the customer Eyeglass configuration replication Job is run.

Workaround: None required.  Custom Quota Jobs do not need to be run manually, they are run automatically each time the customer Eyeglass configuration replication Job is run.

—————————————————–


2007: Job error after deleting quota

After running Quota Job and successfully replicating quota to target, if quota is deleted and Quota Job is run again the Quota is successfully deleted from the target but the Quota Job has Error status.

Workaround: None required - quota is deleted.

—————————————————–


2038: Create alias results in temporary error

When an nfs alias is replicated to the target, the initial create leaves Job in Error state with  related alarm " Alias <alias name> already exists on this zone"

Workaround: None required.  Next replication cycle clears the error.

—————————————————–


2043: Configuration replication job has error after zone is deleted

For the case where Zone related to a Configuration Replication Job is deleted on the source, the Zone and associated configuration items are successfully deleted on the target, but the Configuration Replication job remains in Error state.

Workaround: None required.  Shares and exports are deleted as expected.

—————————————————–


2045: Edit Configuration for Custom Job has multiple source cluster selected where Eyeglass is managing more than 2 clusters

For the case where Eyeglass is managing more than 2 clusters, it may occur that the Edit Configuration view incorrect.

Workaround: None required.  Shares and exports are replicated as expected.

—————————————————–


2046: Job Edit Configuration view has the wrong parent selected

For the case where a configuration replication job contained a configuration items and the last configuration item is deleted - after the configuration item is deleted, the parent in the Edit Configuration view continues to be selected for the Job even though when you expand the tree there are correctly no children selected.

Workaround: None required.

—————————————————–


2049: Delete Zone does not delete associated configuration items on target for custom Jobs and auto jobs with disabled zone Job

When a non System zone is deleted on the Source, the Eyeglass Configuration Replication Custom Job or Auto job with disabled Zone Job does not remove the associated configuration items from target related to the deleted Zone.

Workaround: Manually delete the Zone and associated configuration items on the target using OneFS.

—————————————————–


2081: Update export job shows error when multi-path export overlaps the path of a single path export

Update is correctly replicated to the target, but the Eyeglass Job shows an error if a multipath export contains a path which is overlapping with another export.

Workaround: If possible, remove the overlapping path from the multi-path export.

—————————————————–


2155: Access Zone Networking info does not display in Inventory View

To see the Networking info for an Access Zone in the Inventory View:

  • the Failover Readiness job has to have run

  • the Access Zone must have an associated SyncIQ Policy

Workaround: Enable Failover Readiness job.

—————————————————–


2218: SyncIQ Job Report link to RPO documentation is broken

Selecting the Eyeglass documentation link in the SyncIQ Job report email leads to a page not found error.

Workaround: Access the RPO documentation using this link: RPO Trending and Reporting.

—————————————————–


2224: Eyeglass Cluster Configuration Report runs when Cluster is unreachable

Eyeglass attempts to run the Cluster Configuration Report for Cluster that is not reachable.  The Job is started but does not complete.

Workaround: None available.  Report will run successfully once cluster is reachable.

—————————————————–


2235: Eyeglass replication Job does not complete when source cluster becomes unreachable after Job has started

If the source cluster becomes unreachable after the Eyeglass configuration replication Job has started, the Job does not complete.

Workaround: None required.  The Job will eventually complete after all communications timeouts have occurred.  This may take an hour.

—————————————————–


2060: Access Zone Replication Error - Error on creation of shared resource

Error on Replication for Access Zone which shows Error on creation of shared resource.

Workaround: None required.  Once SyncIQ Job has run again in OneFS, the next time configuration replication runs the Access Zone is replicated.

—————————————————–



2061: Access Zone name for Directory Migration is case sensitive

Check for Access Zone exists on target cluster for Directory migration fails is case sensitive and will fail if Access Zone exists with same name but different case.

Workaround: Access Zone name and case must be identical between source and target for Directory Migration.

—————————————————–


2488: Inconsistent behaviour in Run Now for Disabled Jobs

When Run Now is selected for an Eyeglass Job which is disabled, the handling is different depending on Job Type and state:

For Job which is “Policy Disabled” - Run Now is blocked for all Jobs

For Job which is “User Disabled” - Run Now not blocked and all enabled Jobs run

For Robot Job which is disabled - Run Now not blocked, Job is initiated and then fails.

Workaround: Only select enabled Jobs for Run Now.  

—————————————————–


2599: DFS Readiness Status Pending blocks Failover

When the DFS Readiness Status for a policy is “Pending” you are blocked from failing over.

Workaround: None Required.  “Pending” is an interim state for new Job that has not been run, or a Job where Configuration Replication has run but Audit has not completed.  The Job will leave Pending state and then the Failover can be initiated.

—————————————————–



2628: Job Definitions window does not sort properly

Click on column headings in Jobs window to sort listings does not sort properly and sometimes lists jobs outside of the category groupings.  

Workaround: None available

—————————————————–


2666/2723: Problems for Controlled Failover when Source becomes unreachable during failover

In a Controlled Failover where requirement is that Source cluster is reachable, should the Source cluster become unreachable during the failover an error will occur on the failover job but it is possible that no failover log will be generated.  

If the Source becomes unreachable after Failover Wizard validation but before the Failover starts, a log is generated with 1 line that states success.  The Running Jobs window has no details

Workaround: None available

—————————————————–

2882: Phone Home Email Disabled

Phone home feature is changing and will be disabled . A new web direct option will be used in a future release.

Workaround: Use the Eyeglass Backup Full Archive function to collect Eyeglass configuration and logs.  Procedure is described in the document

—————————————————–


2895: Inventory SPN View is truncated

The Eyeglass Inventory view may be truncated and not display all SPNs stored in the database.

Workaround: Use isi command directly on cluster to determine all SPN.

—————————————————–

1938: Issues with Eyeglass Configuration Replication Jobs after the Access Zone is deleted

When you delete an Access Zone in OneFS, the following issues occur in Eyeglass:

  • corresponding Eyeglass Zone Configuration Replication Job is not deleted

Workaround: None Required.  Job is empty.

—————————————————–


2308: In EyeGlass, NFS alias health is always 'unknown'

Eyeglass Inventory, NFS Alias audit and Cluster Configuration Report always have the NFS alias health property set to unknown.

Workaround: Determine the NFS Alias healt from the OneFS command line using isi command..

—————————————————–


2366: EyeGlass does not support special characters in email recipient address

Email addresses in Eyeglass do not support special characters.

Workaround: Do not provision email recipients or Email Server user with email address that has special characters.

—————————————————–


2278: Zone Readiness lists Access Zone after all related SyncIQ Policies are deleted

For the case where an Access Zone which initially had associated SyncIQ Policies and then all SyncIQ Policies are deleted, the Access Zone will incorrectly appear in the Zone Readiness view with a Status of UNKNOWN.

Workaround: None required.  This entry can be ignored.

—————————————————–


2385: Refresh Now does not refresh the Failover History window

The Failover History window is not updated by the Eyeglass Refresh Now functionality.

Workaround: Close and reopen the Failover History window to see updates.

—————————————————–


2744: Failed to Retrieve Inventory Alarm missing information

For the case where Inventory does not run because another instance of the Inventory Task was already running, the alarm that is raised does not provide this additional information

Workaround: Review the Eyeglass logs at the time that the inventory alarm occurred and search for the string “Another instance of Inventory Task is still running. Not starting”.

—————————————————–


2804: Disabled SyncIQ Policy is not initially displayed as Policy Disabled in Eyeglass

When the Eyeglass system setting for INITIALSTATE is set to Disabled for Configuration Replication Jobs (Type = AUTO), the Jobs window State for the Eyeglass Configuration Replication Job where the corresponding SyncIQ Policy is disabled displays as “User Disabled” instead of “Policy Disabled”.  In this state the Eyeglass GUI allows you to Enable this Job, but in fact after the next Configuration Replication Job the Job is correctly displayed with the Policy Disabled state.

Workaround: None Required.

—————————————————–


2919: Eyeglass Configuration Replication Jobs may not display in the Zone Readiness Eyeglass Configuration Replication Readiness list

If an Eyeglass Configuration Replication Job has no associated shares, exports, alias or quotas, the Job will not be displayed under Eyeglass Configuration Replication Readiness if the SyncIQ OneFS Readiness is WARNING.

Workaround: None Required.  Failover will run all logic and policies as expected.

—————————————————–


2978: Syslog Log Viewer freezes Eyeglass web page

Opening the Eyeglass Syslog Log Viewer window may cause the Eyeglass web page to freeze.

Workaround: Refresh the Eyeglass web page or Fetch the Eyeglass Main Log first and then Fetch the Eyeglass Syslog.

—————————————————–


3010: Unexpected results for failover where total number of objects exceeds the published limit

Running an Eyeglass assisted failover where the total number of objects exceeds the published maximum limit will lead to unexpected results.

Workaround: Review published limits and do not use Eyeglass assisted failover if your system exceeds the published limit.

Please refer to the Eyeglass Admin Guide for published limits here.

—————————————————–


3029: Zone Readiness not calculated correctly for SyncIQ subnet pool with a mapping hint

The subnet:pool which are provisioned against SyncIQ Policies for the Restrict Source Nodes option require an igls-ignore hint for Access Zone Failover to prevent the networking in the pool from becoming failed over during an Access Zone Failover.  If there is an Eyeglass igls- mapping hint assigned to these subnet:pool which could result in the networking being failed over Zone Readiness either does not show an error OR it may show the error that mapping is incomplete.

Workaround: Only configure igls-ignore hint on subnet:pool that is provisioned against SyncIQ policy for the Restrict Source Nodes option.

—————————————————–


3031: Zone Readiness Policy Path Containment Check results in extra errors

Zone Readiness for an Access Zone which does not meet SyncIQ Policy path requirement “SyncIQ Policy(s) source root directory must be at or below the Access Zone Base Directory” may in errors for every validation category, with the message "Cannot calculate Access Zone Failover Readiness for a zone with no pools".

Workaround: To resolve the error, ensure that the Policy Path Containment Requirement is met.

Eyeglass Assisted Access Zone Failover Requirements are documented in the Access Zone Failover Guide here.

—————————————————–


3037: Configure Remote Logging Services in Eyeglass requires manual steps

After configuring the Remote Log  Consumer in Eyeglass, additional manual steps are required on the Eyeglass appliance to update syslog-ng.conf to enable the service.

Workaround: Please refer to Eyeglass Tech Note Eyeglass Isilon Remote Logging Service Tech Note section “Setup Eyeglass remote logging manually for log Analysis”.

—————————————————–


3047: Zone Readiness not calculated correctly when Policy Diverse Target Requirement is not met

If the SyncIQ Policies in an Access Zone are not all configured with the same Target host, the Zone Readiness is in Error as expected, but the display only shows Zone Readiness for one of the failover paths.

Workaround: To resolve this error, system must be configured as per Access Zone requirement that all the SyncIQ Policies in an Access Zone are configured with the same Target Cluster.

—————————————————–

3077: Zone Readiness does not catch pool mapping hint misconfiguration for partial string match

Zone Readiness: Smartconnect Zone Failover Mapping Readiness validation does not detect a pool mapping error when there is a partial string match.  For example:

cluster A Smartconnect Zone Mapping Hint = igls-pool

cluster B Smartconnect Zone Mapping Hint = igls-pool1

Readiness check from A to B does not detect the error.  Readiness check from B to A shows an error that no mapping is available.

Workaround:

  • Ensure that your Smartconnect Zone Mapping Hints are identical for mapped pools

—————————————————–

T477: No Policy Hot/Hot Validation Error for policy with no share/export

Zone Readiness incorrectly shows Policy Hot/Hot Validation as OK in an environment where there are one or more policies in the Access Zone which do not have any file sharing objects (shares or exports).

Workaround: Add a file sharing object under the SyncIQ Policy path.

—————————————————–

T482: Zone Readiness shows OK for multiple Smartconnect Zone Mapping errors

In the case where Smartconnect Zone Mapping contains many errors such as multiple hints or combination of hint and igls-ignore on both clusters, the mapping error may only show for one of the clusters instead of both clusters.

Workaround: Provision Smartconnect Zone Mapping according to requirements documented here.

—————————————————–

T578: Multiple exports with same path have replication error if Clients are identical

If there are multiple exports with the same path and identical Clients, it may take more than one replication cycle to create all exports and if an updating an export results in error:  AEC_EXCEPTION,message Export rules <exportid>  and <exportid> conflict on <path>" .

Workaround: Update exports so that their Clients are not identical.

—————————————————–

T627: Zone Readiness for Policy Source Nodes Restriction not reported properly for OneFS 8.0

For OneFS 8.0, the Zone Readiness Policy Source Nodes Restriction check shows Warning even when the Restrict Source Nodes option is provisioned on the SyncIQ policy.

Workaround: None required.  Check the SyncIQ Policy in OneFS to confirm whether the Restrict Source Nodes option is set or not.  Warning state does not block failover.

—————————————————–

T676: Eyeglass Zone replication Job does not replicate all authentication providers for OneFS 8.0

For OneFS 8.0, if an Access Zone has multiple authentication providers not all providers will be replicated for the Access Zone on the target cluster.

Workaround: Manually edit the Access Zone on the target cluster and add the required authentication providers.

—————————————————–


T654: Zone Readiness incorrectly includes SyncIQ Policy in System Access Zone

For the case where a SyncIQ Policy source path corresponds to a non-System Access Zone path (path is at or below the Access Zone path) but there is a share protected by that policy in the System Access Zone, the SyncIQ Policy incorrectly is evaluated for Zone Readiness in the System Access Zone.

Workaround: None required.  This policy can be ignored in the System Access Zone as in this configuration the System Access Zone cannot be failed over.

—————————————————–


T723: Job shows OK when there is an Access Eyeglass Zone Replication Error

The Jobs window for an Access Zone replication Job which had a replication error or audit error shows as OK even though an Alarm was issued for the Error.

Workaround: Monitor email for Access Zone replication errors.  Address the replication issues.

—————————————————–

T758: Live Ops DR Test Mode does not work for for DFS enabled policies

For DFS enabled Eyeglass Configuration Replication Jobs, the DR Test Mode does not create the associated shares in the DR Test zone.

Note: After failover, shares for DFS enabled Eyeglass Configuration Replication Jobs are replicated to the DR Test Access Zone.

Workaround: None available.  Shares must be created manually in the DR Test Mode Access Zone..

—————————————————–

T771: Edit Configuration does not show parent node selected

If a change is made to a Configuration Replication Job to deselect a file sharing object from the job, the parent node where there still are selected objects is no longer selected in the Edit Configuration window.

Workaround: Expand the Inventory View tree for SMB and NFS to see which objects are contained in the Job.

—————————————————–

T786: No error when adding managed device and no licenses available

Eyeglass does not provide an error if you add a managed device but do not have any available licenses.  Message says that device was successfully added and the Inventory View will show device as “adding….” but the adding will not complete.  This failures will block regular Configuration Replication with error “Caught error while running a step in replication: null”.

Workaround: Delete newly added devices so that the number of clusters being managed matches the Eyeglass licensing.  Obtain licenses for all Isilon clusters that are being managed by Superna Eyeglass.

—————————————————–

T795: DFS Failover log uses Access Zone ID

In the DFS Failover log you will see references to the Access Zone ID (example “zone 1” where “1” is the zone ID).

Workaround: From Eyeglass Inventory View determine the Zone name using the Zone ID by reviewing the Access Zone properties (Right click on zone and select Properties).

—————————————————–

T797: Zone Readiness does not show System Access Zone if it only contains disabled policies

The DR Dashboard / Zone Readiness view does not show the System Access Zone if that Access Zone only has Disabled Sync IQ Policies (for example after System Zone failover - policies on failover source cluster will be disabled)

Workaround: None required.  In the case where a failover has occurred, the System Access Zone failover that is not displayed is in Failed Over state.

—————————————————–

T805: Eyeglass Configuration Replication Jobs not updated when IP address changed on Source Cluster

An IP address change on the Source Cluster of an Eyeglass Configuration Replication job does not get picked up and the job continues to reference the old IP address resulting in a configuration replication error.

Workaround: Reset Eyeglass to pick up IP address changes for Jobs on the new active cluster

  1. Make a record of the state of all Configuration Replication Jobs in the Eyeglass Jobs window - these states will NOT be preserved on the reset:

    1. Jobs which are Configuration Replication type

    2. Jobs that are DFS enabled

    3. Jobs that are User Disabled

  2. SSH to Eyeglass appliance using admin: sudo -s enter (must use root)  then use admin password (default password: 3y3gl4ss)

  3. set the initial state for all Eyeglass Job types to User disabled

    1. http://documentation.superna.net/eyeglass-isilon-edition/Eyeglass-Isilon-Edition#TOC-igls-adv-initialstate

  4. cd /opt/superna/sbin

  5. ./reset.sh

  6. Once reset completes, go to the chrome browser and refresh the browser and login with the credentials

  7. Now, you need to add both of the cluster using Management subnet SSIP.

  8. Once it is added, open the Job window - now you will see all the Eyeglass configuration replication jobs are in “user disabled” state

  9. .Enable all the Eyeglass configuration Job to DFS Mode if configured

IMPORTANT: You must enable DFS mode before enabling the Job to prevent creation of active shares on target cluster.

  1. Enable all configuration replication job (except ones that were previously User Disabled) and run it


—————————————————–

T813: Uncontrolled DFS Failover Log incorrectly shows Resync Prep step as being selected

For an uncontrolled failover where the ResyncPrep step of the failover is NOT executed, the Failover Log incorrectly indicates that the step will be executed.  For example:

   2016-03-07 11:57:50::050 INFO SyncIQ Resync Prep : true

Workaround: None required.  The Resync Prep step is NOT executed as expected.

—————————————————–

T593, T873: Eyeglass errors for multiple exports with the same path

If an Eyeglass Configuration Replication Job contains more than one Export with the same path, this may result in an AUDITFAILED state or configuration replication error  for the associated Eyeglass Configuration Replication Job in the DR Dashboard or a configuration replication error.

Workaround: The following workaround is available to address this issue:

  1. Modify exports on the source to add a second path which is a sub-folder of the existing path.  This way Eyeglass will identify each Export uniquely.  Example

           Initial State:

            export 1:   /ifs/data/folder

            export 2:   /ifs/data/folder

           Updated State:

            export 1:   /ifs/data/folder

                             /ifs/data/folder/sub-folder

            export 2:   /ifs/data/folder


          2) Exports must have different Clients.

—————————————————–

T883, T971: Eyeglass End User Interface Tree View Expanders do not collapse

The Eyeglass End User Interface with tree displays such as the Inventory View and the DR Dashboard the ‘+’ can be used to expand the tree but then the ‘-’ does not collapse the tree again.

Workaround: Close and reopen the window

—————————————————–

T979: NFS Alias created instead of updated for A -> B -> C replication topology

In the case where NFS Alias are being replicated from Cluster A to Cluster B and then from Cluster B to Cluster C, when the NFS Alias is updated on Cluster A the change is correctly synced to Cluster B but then instead of syncing the update to Cluster C a new NFS Alias is created on cluster C.

Workaround: Manually remove duplicate NFS Alias on Cluster C.

—————————————————–

T972: Failover Wizard selection is not cleared

In the case where a policy has been selected for failover in the failover wizard, if the failover wizard window is closed and reopened the same policy is still selected.

Workaround: Uncheck the previously selected policy and select the required policy.

—————————————————–

T976: Eyeglass Zone Configuration Replication “Edit Configuration” window does not show the correct zone

In some cases the “Edit Configuration” view for an Eyeglass Configuration Zone Replication Job will not show the correct zone.  It may not show a zone at all or may show multiple zones.

Workaround: Use the Job path compared to the Access Zone base path to determine which Access Zone is associated with the job.

—————————————————–

T982: Deletion of Shares and Exports does not work for A -> B -> C replication topology

In the case where Shares and Exports are being replicated from Cluster A to Cluster B and then from Cluster B to Cluster C, when a Share or Export is deleted on Cluster A the change is correctly synced and the Share or Export is also deleted from Cluster B but it is not deleted from Cluster C.

Workaround: Manually remove the Shares and Exports on Cluster C that should have been deleted.

—————————————————–

T942: Failover Log for Uncontrolled Failover incorrectly lists the delete quota step

In the case of an uncontrolled failover (‘Controlled’ failover option is not selected typically when the source cluster is down / not available), the Failover Log incorrectly list the delete quotas on source step with status of ‘SUCCESS’.  In the case of this failover mode, in fact the quotas are not deleted from the source.

Workaround: Manually delete quotas on the failover source cluster when it becomes available.

—————————————————–

T954: Eyeglass “Restore” operation does not restore failover logs

When an Eyeglass backup file is restored to a new appliance, the Failover Logs from the original appliance are in the backup file but are not restored to the new appliance.

Workaround: Failover Logs from original appliance can be found in the Eyeglass backup archive in the failover-logs directory.

—————————————————–

T1285:  Failover log does not display the Post Failover steps

Access Zone Failover post failover steps are not written to the Failover Log. For this step, the log contains an error - example:

2016-04-12 09:48:46::515 ERROR Could not display post failover information

Workaround: Use the DR Assistant, Failover History Job Details Tree to see the post failover steps and their status.

—————————————————–



T1349: SPN Readiness does not show Active Directory Domain after Access Zone Failover

After an Access Zone Failover,=, the Superna Eyeglass Zone Readiness / SPN Readiness view does not show the domain associated with the Access Zone that was shown previously before the failover.

Workaround: None Required.  Readiness status is correct.

—————————————————–

T1355:  Uncontrolled failover incorrectly attempts to delete Quotas on the Source Cluster

When a failover is initiated with the “Controlled failover” option deselected, Eyeglass incorrectly attempts to delete quotas on the source cluster.  In this mode, no actions should be attempted against the source cluster as it is expected that when this mode is selected that the source cluster is unavailable.  In the event that it would be available, the quotas on the source would be deleted.

Workaround: None required.  In the case where the source cluster is not available the end result is as expected with quotas still on the source and requiring manual cleanup.  In the case where the source cluster is available, quotas are present on the target cluster as expected during a failover.

—————————————————–

T1358:  Export update does not handle removal of clients from client list

When you update an export by removing a client from any of the client lists, Eyeglass configuration replication does not update the export on the target to remove the client. In this case, Eyeglass configuration replication is incorrectly Green but the DR status correctly shown as Red because audit detects that the client lists are different and fails.

Note Modifying an IP address in the client list or adding a new IP address to a client list are correctly replicated to the target.  

Workaround: Edit the export client list on the target manually.

—————————————————–

T1359:  Add path to export has Configuration Replication Error on first replication cycle

If an export is updated to add an additional path, on the first configuration replication cycle after the change is detected, Eyeglass deletes the previous export but has an error creating the export with the additional path.  

Workaround: None required.  On the next configuration replication cycle, the export is correctly created.

—————————————————–

T1364:  Error after upgrade to 1.5.2 when starting failover

In the case where an Eyeglass failover has not been executed before upgrading to Eyeglass R1.5.2, when a failover is started there will be an error "Server error when processing request: null".  

Workaround: Close the DR Assistant window.  Open the DR Assistant window and start the failover again. On second attempt the failover will proceed.

—————————————————–

T1345:  Mirror policy not DFS enabled after failover if Quota Job fails

For the first time DFS Mode failover case where the SyncIQ mirror policy is created, if the Quota Job step in the failover fails the Eyeglass Job for the SyncIQ mirror policy will not be enabled in DFS mode.  It will be left in regular configuration replication mode.  With default settings, the Eyeglass Job will be in User Disabled state for the newly created Job.  DFS mode MUST be enabled before the Job is enabled to avoid same shares on both clusters and DFS resolving to both clusters.

Workaround: Follow these steps:

  1. Login to the Eyeglass web page.

  2. Open the Jobs window.

  3. Select the checkbox for the mirror policy Job.

  4. Select the menu Select a bulk action.

  5. Select the option for Enable/Disable Microsoft DFS

  6. This will move the Job into the section “Configuration Replication: DFS mode (AUTOMATIC).  The Job type will be AUTODFS.

   !! IMPORTANT  Do not proceed to next step unless you have verified step 6.

     7)  Select the menu Select a bulk action.

     8)  Select the option for Enable/Disable.

Now the Eyeglass Job for the SyncIQ mirror policy is in DFS mode and is enabled for Configuration Replication.

—————————————————–

T1303:  REST API does not validate failover target

The REST API does not validate the failover target and will initiate a failover under invalid conditions such as:

  • Target is same cluster as the source

  • Zone Readiness not executed  

Workaround: Manual process to ensure that target is valid before initiating failover using the REST API.

—————————————————–

T1465:  Failover option to Disable SyncIQ on Failover Target still runs the policy before disabling it

The Eyeglass DR Assistant Failover Wizard option for "Disable SyncIQ Jobs on Failover Target" still runs the policy before disabling the policy instead of not running it at all.

Workaround: None available. Ensure that data sync is complete and up to date on DR cluster before failing over to ensure that stale data is not replicated back to the source cluster.

—————————————————–

T1467:  Info cannot be opened for Failed to retrieve inventory and Inventory is degraded/incomplete alarms

The info link in the Alarms window for the alarms “Failed to retrieve inventory” and “Inventory is degraded/incomplete” does not open to display additional info.

Workaround: Create an Eyeglass backup and raise a support ticket at support.superna.net to review error details.  Creating logs and raising a ticket are documented here:  http://documentation.superna.net/eyeglass-isilon-edition/how-to-raise-an-eyeglass-isilon-support-request

—————————————————–


Superna Eyeglass Known Issues

Known Limitations for Isilon OneFS 8.0.0.x with Eyeglass


T507 Cluster Report for OneFS 8.0 missing information

The Eyeglass Cluster Configuration Report for OneFS 8.0 is missing following information:

  • DNS and Subnet information

  • File System Explorer

  • Protocols - new HDFS, FTP, HTTP settings


T831 Failover Allow Writes step not allowed when quotas being created in OneFS 8.0

The step to create quotas during an Eyeglass failover occurs before the step to make the data writeable on the target.  For OneFS 8.0, the quota creation step blocks the Allow Writes step with the error:

A new quota domain that has not finished QuotaScan has been found. Please wait for QuotaScan to finish before restarting the sync job.


Workaround: Manually run quota jobs from Eyeglass prior to running doing an Eyeglass failover.  


Known Limitations for Eyeglass Failover

T939  Eyeglass Access Zone Replication Job in Error after failover


The Access Zone Replication Job associated with the SyncIQ mirror policy configuration replication Job has the following error when the SyncIQ policy source and target path are not identical.

Workaround:  Create and update Access Zones manually on source and target cluster and disable Eyeglass Access Zone replication Jobs.  With the Eyeglass Access Zone replication Jobs disabled, the Zone Configuration Replication Readiness Jobs will have a status of Unknown.  This does not block failover.


Known Limitations for Eyeglass Configuration Replication

T1359  Update NFS Multi-Path Export path(s) may cause transient Configuration Replication Error

Eyeglass uniquely identifies an NFS Export based on its path.  When the path is changed this results in a Create and Delete operation in Eyeglass.  It may occur that the create is attempted before the Delete is executed.  In this case a Configuration Replication error occurs.  This is automatically resolved in the subsequent replication cycle when the new export is successfully created.