Eyeglass Isilon Edition 1.4.8 release notes

Supported OneFS releases


7.1.1.x

7.2.0.x

7.2.1.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

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

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

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

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

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

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





End of Life Notifications


Description

End of Life Date

Eyeglass Appliance operating system version OpenSUSE 13.1


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

March 31, 2016


Superna Eyeglass Isilon Support Agreement can be found here.



Issues Resolved in Release 1.4.8


T468: Duplicate NFS Exports created by Eyeglass

Under some conditions such as the case where the target cluster fails to respond to API calls and returns a partial list of exports during Eyeglass inventory discovery, Eyeglass may create duplicate NFS exports on the target treating the partial response from the cluster as a new export.  The duplicate export does not affect failover operations.   

Resolution: Eyeglass has been updated to remove the force flag when creating NFS exports such that duplicates can no longer be created but this will now generate a sync failure when the export can not be created.   If this error occurs it indicates the cluster API service PAPI is not return the fill list of exports correctly.   If you find this error, please a raise a support case and instructions to reduce the number of API calls MAY remove or suppress this API error on the cluster.   Future release will raise a new warning when the cluster API response is incomplete.

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



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.

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


1644: Replication still performed when shares/exports de-selected from Custom Job

The Eyeglass Edit Configuration window will indicate that shares/exports have been deselected but deselected shares/exports will still be replicated on schedule.

Workaround: None available.

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


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.

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


2614: Able to set DFS Mode for RunbootRobot Job

DFS Mode is not support for RunbookRobot Jobs, but the Eyeglass GUI does not block you from enabling DFS mode.  

Workaround: Do not enable DFS mode for RunbookRobot Jobs.

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


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

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


2868: Error for Eyeglass Configuration Replication Job with Exports that have the same path

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

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.

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


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.

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


2363: Zone Readiness Network Mapping Window column sorting does not work

Selecting column headings in the Zone Readiness Network Mapping window indicates that the sorting can be done by column but then no sorting occurs.

Workaround: Scroll down Network Mapping window to see all pool mappings.

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


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

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











Comments