Release Notes 1.9.4 DR Edition

Contents

  1. 1 What’s New in Superna Eyeglass Isilon Edition Release 1.9
  2. 2 Supported OneFS releases
  3. 3 DR Edition Feature Release Compatibility
  4. 4 Inter Release Functional Compatibility
  5. 5 Feature Support Matrix
  6. 6 End of Life Notifications
  7. 7 Issues Fixed in Eyeglass Release 1.9.3
    1. 7.1 Configuration Replication
      1. 7.1.1 T3814:  Incorrect Audit error for Configuration Replication with overlapping Access Zones
    2. 7.2 Features
      1. 7.2.1 2218: SyncIQ Job Report link to RPO documentation is broken
    3. 7.3 General
      1. 7.3.1 T3958 - Eyeglass Full Backup Initialization Error
  8. 8 Known Issues
    1. 8.1 Failover
      1. 8.1.1 2666/2723: Problems for Controlled Failover when Source becomes unreachable during failover
      2. 8.1.2 2278: Zone Readiness lists Access Zone after all related SyncIQ Policies are deleted
      3. 8.1.3 2919: Eyeglass Configuration Replication Jobs may not display in the Zone Readiness Eyeglass Configuration Replication Readiness list
      4. 8.1.4 3010: Unexpected results for failover where total number of objects exceeds the published limit
      5. 8.1.5 3029: Zone Readiness not calculated correctly for SyncIQ subnet pool with a mapping hint
      6. 8.1.6 3031: Zone Readiness Policy Path Containment Check results in extra errors
      7. 8.1.7 3077: Zone Readiness does not catch pool mapping hint misconfiguration for partial string match
      8. 8.1.8 T477: No Policy Hot/Hot Validation Error for policy with no share/export
      9. 8.1.9 T482: Zone Readiness shows OK for multiple Smartconnect Zone Mapping errors
      10. 8.1.10 T654: Zone Readiness incorrectly includes SyncIQ Policy in System Access Zone
      11. 8.1.11 T1712:  Zone Readiness missing Zone when pool has no SmartConnect Zone - OneFS 7
      12. 8.1.12 T1716:  Eyeglass Runbook Robot NFS mount not functioning for RHEL and Centos deployments
      13. 8.1.13 T1482:  Zone Readiness SyncIQ Readiness not updated after Access Zone associated to a pool
      14. 8.1.14 T3742:  No Policy Hostname Validation error if SyncIQ Policy Target Host is fully qualified and uses short name on target cluster pool that has a Superna Eyeglass mapping hint applied
      15. 8.1.15 T3848:  SPNs not updated during failover for OneFS8 non-default groupnet AD provider
      16. 8.1.16 T4009:  SPNs creation case sensitive to AD provider name
      17. 8.1.17 T4209 Eyeglass Configuration Replication Error Info has Incorrect Job list
      18. 8.1.18 T4124:  Enable Runbook Robot Job does not enable the related Configuration Replication Job
      19. 8.1.19 T4320:  Access Zone not assigned to any Subnet Pools results in many Zone Readiness Errors
      20. 8.1.20 T4316:  Runbook Robot Policy Job does not display SyncIQ Job Reports
      21. 8.1.21 T4960:  Cannot enable Script after created
      22. 8.1.22 T4968:  Zone missing from DR Dashboard Zone Readiness tab if a SyncIQ Policy has a target host that cannot be resolved
    2. 8.2 Configuration Replication
      1. 8.2.1 1683: Export sync where source  is 7.1.1.x and target 8.x.x.x
      2. 8.2.2 649: Export sync where source and target path on each cluster is different is deleted and recreated in each config cycle (affects onefs 7 to 8 or 8 to 7 replication)
      3. 8.2.3 1462 - Export max_file_size cannot be replicated
      4. 8.2.4 1355: Edit Job configuration to include share/export deselected from another Job causes share/export to be reselected.
      5. 8.2.5 1580: Delete and Create export within same replication cycle orphans deleted export on the target with OneFS 7.1.1.x
      6. 8.2.6 1625: Custom QUOTA Jobs require extra replication cycle to be deleted
      7. 8.2.7 1639: Able to manually Run Now disabled Custom Job
      8. 8.2.8 1641: Custom Job does not include shares/export when source or destination path configured with a trailing /
      9. 8.2.9 1788: Delete of unlinked user quota on source may not delete matching quota on the target
      10. 8.2.10 1789: Able to select shares/exports/quotas outside job path after deselected
      11. 8.2.11 1887, T3727: Multiple SyncIQ policies associated with same Zone will result in transient error on Eyeglass Zone replication creation
      12. 8.2.12 1924: Quotas on excluded SyncIQ directory are selected for replication
      13. 8.2.13 1998: Custom Eyeglass configuration replication Job does not have an associated Zone replication Job
      14. 8.2.14 2004: Custom Quota Job is incorrectly listed in the Failover: Quota Failover (RUN MANUALLY) section in the Jobs window
      15. 8.2.15 2007: Job error after deleting quota
      16. 8.2.16 2038: Create alias results in temporary error
      17. 8.2.17 2043: Configuration replication job has error after zone is deleted
      18. 8.2.18 2045: Edit Configuration for Custom Job has multiple source cluster selected where Eyeglass is managing more than 2 clusters
      19. 8.2.19 2046: Job Edit Configuration view has the wrong parent selected
      20. 8.2.20 2049: Delete Zone does not delete associated configuration items on target for custom Jobs and auto jobs with disabled zone Job
      21. 8.2.21 2235: Eyeglass replication Job does not complete when source cluster becomes unreachable after Job has started
      22. 8.2.22 2060: Access Zone Replication Error - Error on creation of shared resource
      23. 8.2.23 2488: Inconsistent behaviour in Run Now for Disabled Jobs
      24. 8.2.24 1938: Issues with Eyeglass Configuration Replication Jobs after the Access Zone is deleted
      25. 8.2.25 2308: In EyeGlass, NFS alias health is always 'unknown'
      26. 8.2.26 2804: Disabled SyncIQ Policy is not initially displayed as Policy Disabled in Eyeglass
      27. 8.2.27 T676: Eyeglass Zone replication Job does not replicate all authentication providers for OneFS 8.0
      28. 8.2.28 T723: Job shows OK when there is an Access Eyeglass Zone Replication Error
      29. 8.2.29 T771: Edit Configuration does not show parent node selected
      30. 8.2.30 T805: Eyeglass Configuration Replication Jobs not updated when IP address changed on Source Cluster
      31. 8.2.31 T593: Eyeglass errors for multiple exports with the same path
      32. 8.2.32 T1792: Eyeglass does not auto-detect Isilon version changes and may use incorrect API version for Configuration Replication
      33. 8.2.33 T1851: Eyeglass Configuration Replication Jobs not removed when there is no SyncIQ privilege for the eyeglass service account
      34. 8.2.34 T2193 - Export max_file_size setting not replicated correctly
      35. 8.2.35 T2757:  Access Zone is not replicated from OneFS 8 to OneFS 7.2
      36. 8.2.36 T1976 - Eyeglass Jobs Window Edit Configuration does not show related Snapshot Schedules
      37. 8.2.37 T2920:  Access Zone Authentication Provider is not replicated to the target cluster
      38. 8.2.38 T3383:  Audit failed when Eyeglass DFS Configuration Replication Job has NFS Exports with the same path but in different Access Zones
      39. 8.2.39 T3629:  Renamed Snapshot Schedule leaves original Snapshot Schedule on the target
      40. 8.2.40 T4297, T4299:  Eyeglass Inventory does not created short SPN for new SmartConnect Zone
    3. 8.3 Features
      1. 8.3.1 1138: Eyeglass UI does not block configuration of duplicate remote logging service
      2. 8.3.2 2224: Eyeglass Cluster Configuration Report runs when Cluster is unreachable
      3. 8.3.3 2061: Access Zone name for Directory Migration is case sensitive
      4. 8.3.4 2882: Phone Home Email Disabled
      5. 8.3.5 3037: Configure Remote Logging Services in Eyeglass requires manual steps
      6. 8.3.6 T1515:  Eyeglass Shell feature not functioning for RHEL and Centos deployments
      7. 8.3.7 T3119:  Access Zone Migration Preview does not always display Configuration information
      8. 8.3.8 T3170:  Quota Requests History shows Status of Error for processed requests after failover
      9. 8.3.9 T4280:  User Storage View may show all quotas instead of only the User Quotas
      10. 8.3.10 T4329:  DR Test Status does not open
      11. 8.3.11 T4432:  DR Test Mode action on multiple policies do not display in Running Jobs
      12. 8.3.12 T4968:  SyncIQ Job Report Troubleshooting section missing information when report is generated on demand
    4. 8.4 General
      1. 8.4.1 924: Inventory View shows + beside component when there are no more children
      2. 8.4.2 943: Inventory View not auto-refreshed
      3. 8.4.3 1612: Some alarms not cleared
      4. 8.4.4 2155: Access Zone Networking info does not display in Inventory View
      5. 8.4.5 2628: Job Definitions window does not sort properly
      6. 8.4.6 2895: Inventory SPN View is truncated
      7. 8.4.7 2366: EyeGlass does not support special characters in email recipient address
      8. 8.4.8 2385: Refresh Now does not refresh the Failover History window
      9. 8.4.9 2744: Failed to Retrieve Inventory Alarm missing information
      10. 8.4.10 2978: Syslog Log Viewer freezes Eyeglass web page
      11. 8.4.11 T971: Eyeglass End User Interface Tree View Expanders do not collapse
      12. 8.4.12 T1514:  Eyeglass Archive cannot be downloaded when Eyeglass is deployed on Redhat or Centos
      13. 8.4.13 T3137 - Eyeglass daily backup not working for RHEL/CentOS Deployments
      14. 8.4.14 T4596: Log Viewer cannot fetch logs
      15. 8.4.15 T4765: Cluster Report Created date is not preserved on Restore
      16. 8.4.16 T5206: Eyeglass Shell Not Available with 1.9.4 and OpenSUSE 42.3
  9. 9 Superna Eyeglass Known Limitations
    1. 9.1 Known Limitations for Isilon OneFS 8.0.0.x with Eyeglass
      1. 9.1.1 T507 Cluster Report for OneFS 8.0 missing information
      2. 9.1.2 Known Limitations for Eyeglass Failover
      3. 9.1.3 T939  Eyeglass Access Zone Replication Job in Error after failover
      4. 9.1.4 T1785  Cannot set ignore flag on subnet pool after failback
      5. 9.1.5 T2479: Access Zone Failover fails between OneFS 7.2 clusters if Eyeglass also managing OneFS 7.1
      6. 9.1.6 T3258: Cannot start failover while Eyeglass initial inventory is running
      7. 9.1.7 T3774: Failover relies on policy naming: <policy name> and <policy name_mirror>
      8. 9.1.8 T4808: SPNs not updated for new authentication providers after Access Zone settings changed to “Use all authentication providers” (OneFS 7.2)
      9. 9.1.9 Known Limitations for Eyeglass Configuration Replication
      10. 9.1.10 Multi-Path Exports
        1. 9.1.10.1 T1359  Update NFS Multi-Path Export path(s) may cause transient Configuration Replication Error
        2. 9.1.10.2 Export cannot have multiple paths that span multiple Eyeglass Jobs
      11. 9.1.11 T1359  Update NFS Multi-Path Export path(s) may cause transient Configuration Replication Error
      12. 9.1.12 T1743  Multiple export with same path and same client do not show Configuration Replication Error
      13. 9.1.13 T1847  OneFS 8 Overlapping Access Zone Replication has error
      14. 9.1.14 T1972  Snapshot schedule replicated with offset
      15. 9.1.15 T2046  Access Zone Replication limitation when all user mapping rules are deleted
      16. 9.1.16 T2241  Incorrect missing SPN alarm issued when Isilon cluster joined to multiple Domains
      17. 9.1.17 T2779 - Eyeglass Configuration Replication “Full Sync Mode” always updates when Default Settings on Source and Target cluster are not the same
      18. 9.1.18 T2780  Same host moved to different NFS Export Client list not updated on target
      19. 9.1.19 T2908  New Eyeglass Configuration Replication Job cannot recover state and mode from the Eyeglass Fingerprint file.
      20. 9.1.20 T4289  Delete Share or Export may result in temporary Audit error
      21. 9.1.21 Known Limitations for Eyeglass Features
      22. 9.1.22 T2350:  Quota Self Serve Portal: Local Group Quotas not displayed when logged in with Local Group User
      23. 9.1.23 T1962: Default Role incorrectly shows Delete option
      24. 9.1.24 Known Limitations for Eyeglass General
      25. 9.1.25 T2289  Backup Archive Job is not always displayed in the Running Jobs window
      26. 9.1.26 T2908  Renamed SyncIQ Policy does not link to RPO Reports from original SyncIQ Policy Name
      27. 9.1.27 T3170 Pending Quota Requests are not preserved on failover
      28. 9.1.28 T4579 Upgrade from 1.5.4 to 1.9 and greater Failover History retrieves Failover Log for SyncIQ Job Reports


What’s New in Superna Eyeglass Isilon Edition Release 1.9

What’s New! In Superna Eyeglass Isilon Edition Release 1.9 can be found here.


Superna Eyeglass DR Edition Release 1.9.4 introduces support for Isilon OneFS 8.1.  Please review Feature Release Compatibility table for supported functionality.





Supported OneFS releases


7.1.1.x

7.2.x.x

7.2.1.x

8.0.0.x

8.0.1.x

8.1.x.x


DR Edition 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

8.0.x.x >> shares only see 1683


 Configuration Replication

7.2.x.x

7.2.x.x

8.0.x.x**

Configuration Replication

8.0.x.x

8.0.x.x

8.1.x.x**

7.2.x.x**

Configuration Replication

8.1.x.x

8.1.x.x***

8.0.x.x**

Configuration Replication

DFS mode



  Configuration Replication - DFS Mode

 7.1.1.3 and higher

 7.1.1.3 and higher

8.0.x.x >> shares only see 1683


 Configuration Replication - DFS Mode

7.2.x.x

7.2.x.x

8.0.x.x**

Configuration Replication - DFS Mode

8.0.x.x

8.0.x.x

8.1.x.x**

7.2.x.x*

Configuration Replication - DFS Mode

8.1.x.x

8.1.x.x***

8.0.x.x**

SyncIQ Policy Failover

non-DFS mode



SyncIQ Policy Failover

7.1.1.x

7.1.1.x

8.0.x.x >> unsupported pending testing

SyncIQ Policy Failover

7.2.x.x

7.2.x.x

8.0.x.x**

SyncIQ Policy Failover

8.0.x.x

8.0.x.x

7.2.x.x**

SyncIQ Policy Failover

8.1.x.x

8.1.x.x***

SyncIQ Policy Failover

DFS mode



SyncIQ Policy Failover - DFS mode

 7.1.1.3 and higher

 7.1.1.3 and higher

8.0.x.x >> unsupported pending testing

SyncIQ Policy Failover - DFS mode

7.2.x.x

7.2.x.x

8.0.x.x**

SyncIQ Policy Failover - DFS mode

8.0.x.x

8.0.x.x

7.2.x.x**

SyncIQ Policy Failover - DFS mode

8.1.x.x

8.1.x.x***

Access Zone Failover



Access Zone Failover

7.2.x.x

7.2.x.x

8.0.x.x**

Access Zone Failover

8.0.x.x

8.0.x.x

8.1.x.x**

7.2.x.x**

Access Zone Failover

8.1.x.x

8.1.x.x***

8.0.x.x**

Runbook Robot cluster pairs

SyncIQ Policy Failover



SyncIQ Policy Failover

7.1.1.x

7.1.1.x

8.0.x.x >> shares only see 1683

SyncIQ Policy Failover

7.2.x.x

7.2.x.x

8.0.x.x**

SyncIQ Policy Failover

8.0.x.x

8.0.x.x

7.2.x.x**

SyncIQ Policy Failover

8.1.x.x

8.1.x.x***

Runbook Robot* cluster pairs

Access Zone Failover



Access Zone Failover

7.2.x.x

7.2.x.x

8.0.x.x**

Access Zone Failover

8.0.x.x

8.0.x.x

7.2.x.x**

Access Zone Failover

8.1.x.x

8.1.x.x***

Live Ops - DR Test Mode



Live Ops DR Test Mode

7.2.x.x

7.2.x.x

8.0.x.x**

Live Ops DR Test Mode

8.1.x.x

8.1.x.x***

Snapshots and Schedules

7.2.x.x

7.2.x.x

8.0.x.x**

Snapshots and Schedules

8.0.x.x

8.0.x.x

7.2.0.x.x **

Snapshots and Schedules

8.1.x.x

8.1.x.x***

Dedupe Path settings

7.2.x.x

7.2.x.x

8.0.x.x**


Dedupe Path Settings

8.0.x.x

8.0.x.x

7.2.0.x.x **

Dedupe Path Settings

8.1.x.x

8.1.x.x**


** Inter-version capabilities: In the case of inter-version operation, the capabilities of the lower OneFS version will be applied across both OneFS versions.  Capabilities of the higher OneFS version that are not present in the lower OneFS version will not be available.  Example: OneFS 8 specific attributes will not be synced but OneFS 7 attributes will be synced.


***Due to Isilon OneFS 8.1 defect, the following configuration change must be made on the Eyeglass appliance to support OneFS 8.1 with Eyeglass features

  1. ssh to the Eyeglass appliance

  2. Elevate to root user by using command below and entering admin password

sudo su -

  1. cd /opt/superna/sca/data

  2. edit system.xml

  3. Find the line

<runconfigsyncinparallel>true</runconfigsyncinparallel>

  1. And modify to false

<runconfigsyncinparallel>false</runconfigsyncinparallel>

  1. Save your changes

  2. Restart the sca service

systemctl restart sca

  1. Done

Inter Release Functional Compatibility


OneFS 7.2 - OneFS 8.0

OneFS 7.1.1 - OneFS 8.0

Eyeglass Configuration Replication (including Snapshots and Dedupe)

Only OneFS 7.2 properties will be synced

Yes (shares only)

SyncIQ Policy Failover

Yes

Unsupported Pending testing

DFS Failover

Yes

Unsupported Pending testing

Access Zone Failover

Yes

Unsupported Pending testing

Runbook Robot - SyncIQ Policy Failover

Yes

Unsupported Pending testing

Runbook Robot - Access Zone Failover

Yes

Unsupported Pending testing

DR Test Mode


Unsupported Pending testing

Snapshots and Schedules

Yes

Unsupported Pending testing

Dedupe

Yes

Unsupported Pending testing




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

Runbook  Robot Access Zone Multi cluster

No (only cluster pairs with no common cluster)



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 the latest  release using upgrade guide located here.  Numerous failover and performance improvements exist in later releases so earlier releases are end of support with all new cases requiring an upgrade.


April 25, 2016

End of Support for 1.5.x Superna Eyeglass Releases

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

Active releases are posted here.

Jan 1, 2017

End of Support for 1.6.x Superna Eyeglass Releases

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

Active releases are posted here.

July 31, 2017

End of Support for 1.7.x and 1.8.x Superna Eyeglass Releases

All customers running the above releases should upgrade to the latest  release using upgrade guide located here.  OpenSUSE 13.2 no longer being patched and is End of Life for the Superna Eyeglass Appliance.  Operating system update to OpenSUSE 42.2 will be required to maintain a supported appliance.

Also Numerous failover and performance improvements exist in later releases so earlier releases are end of support with all new cases requiring an upgrade.

Active releases are posted here.

Oct 29, 2017



Issues Fixed in Eyeglass Release 1.9.3


Configuration Replication


T3814:  Incorrect Audit error for Configuration Replication with overlapping Access Zones

Configuration Replication completes successfully for Job where configuration data (shares, exports, nfs alias) exist in multiple access zones, however audit may incorrectly report an error when in fact the properties and permissions are identical.

This results in an associated Policy / DFS Readiness error: attention - no update, src and dst are equal - no update, src and dst are equal - no update, src and dst are equal - no update, src and dst are equal

Resolution: Auditor now handles this condition and does not alarm.  Note that the message in readiness is reporting status for all replication activities related to that policy.  When there is no change you will see this message “ no update, src and dst are equal”.

—————————————————


Features

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.

Resolution: Eyeglass documentation link now resolves correctly to the Eyeglass Isilon Edition Recovery Point Objective Trending and Reporting document.

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

General


T3958 - Eyeglass Full Backup Initialization Error

An Eyeglass Full Backup may have an Initialization Error after initial install.

Resolution:  Initialization error no longer occurs after initial install.

———————————


Known Issues

Failover


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

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


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.

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


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.

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


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.

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

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.

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

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.

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


T1712:  Zone Readiness missing Zone when pool has no SmartConnect Zone - OneFS 7

In OneFS 7 When a subnet pool is associated with an Access Zone and does not have a Smartconnect Zone, the Access Zone is not displayed in Eyeglass Zone Readiness window.  With OneFS 8 there is an entry in Zone Readiness with appropriate error.

Workaround: Create SmartConnect Zone for the pools associated with the Access Zone that you want to failover.

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

T1716:  Eyeglass Runbook Robot NFS mount not functioning for RHEL and Centos deployments

If Eyeglass is deployed on a Redhat or Centos operating system the Eyeglass Runbook Robot pre and post failover check for file system read/write by making an NFS mount does not work.

Workaround: Disable the Runbook Robot mount step by setting to false following the instructions here: http://documentation.superna.net/eyeglass-isilon-edition/igls-administration/eyeglass-administration-guide#TOC-Runbook-Robot-Mount-Export-Enable-Disable

Manually check read/write status of filesystem.

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

T1482:  Zone Readiness SyncIQ Readiness not updated after Access Zone associated to a pool

For the case where initially an Access Zone with a policy is not associated with a pool, the policy appears in Zone Readiness/SyncIQ Readiness under the System Access Zone.  Once the Access Zone is associated with the pool the Policy remains associated with the System Access Zone.

Workaround: None Available.  This is a display issue and the policy will failover if the access zone it is a member of is failed over.  

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

T3742:  No Policy Hostname Validation error if SyncIQ Policy Target Host is fully qualified and uses short name on target cluster pool that has a Superna Eyeglass mapping hint applied

If the pool on the target cluster which contains the SmartConnect Zone which is configured on the source cluster as the SyncIQ policy target host is configured as “short” name instead of fully qualified name AND that pool has a Superna Eyeglass mapping hint defined instead of the required igls-ignore hint, Zone Readiness INCORRECTLY does not show an error.

Workaround: Use fully qualified domain name for SyncIQ Policy target host and in the pool SmartConnect Zone name.  

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

T3848:  SPNs not updated during failover for OneFS8 non-default groupnet AD provider

For the case where OneFS 8 is configured with multiple groupnet and different AD provider between groupnets, the SPN update during failover does not succeed for non-default groupnet AD providers.  SPN are not deleted for source cluster and are not created for the target cluster.  The failover log indicates success.  This is due to a OneFS8 defect with multiple AD providers and isi commands.

SPN delete / create for the AD provider defined in groupnet0 is successful.

Workaround: Manually delete and create the SPN for the Smartconnect Zones that were moved from AD ADSI Edit interface.  

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

T4009:  SPNs creation case sensitive to AD provider name

If you have domain name in lowercase but smartconnect zone name has upper case domain name then in that case Eyeglass does not add the SPN Host automatically .

Workaround: AD provider name and AD provider in SmartConnect Zone name should have same case.  

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

T4209 Eyeglass Configuration Replication Error Info has Incorrect Job list

During a failover, a failed Eyeglass Configuration Replication task Info will list all Jobs instead of only listing the Jobs that failed

Workaround: Check the Alarms window for failed Configuration Replication Jobs during the failover time period.  The associated Major severity alarms will have the details regarding which share or export was affected.

If it has been less than 15 minutes since the Configuration Replication Job ran, you may also check the Jobs -> Running Jobs tab to view which Jobs failed within the task.

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

T4124:  Enable Runbook Robot Job does not enable the related Configuration Replication Job

If both of the Eyeglass Configuration Replication Job for Runbook Robot and the Runbook Robot Job itself are disabled, enabling the Runbook Robot Job only does not enable the related Configuration Replication Job.  Running the Runbook Robot job in this state results in an error.

Workaround: Always ensure that both the Runbook Robot Configuration Replication and Runbook Robot Job are enabled.  This can be done manually by selecting the Job and then Edit Configuration -> Enable/Disable.  

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

T4320:  Access Zone not assigned to any Subnet Pools results in many Zone Readiness Errors

Zone Readiness error for an Access Zone that is not assigned to any Subnet Pool has multiple rows displayed in the DR Dashboard - 1 per Subnet Pool on the Isilon Cluster.

Workaround: Associate the Access Zone with at least 1 Subnet pool.  

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

T4316:  Runbook Robot Policy Job does not display SyncIQ Job Reports

Runbook Robot job creates 2 failover history records - one for policy failover or access zone failover and one for for Runbook Robot.  The Runbook Robot SyncIQ Reports log incorrectly repeats the Failover log information instead of showing the associated SyncIQ Job reports.

Workaround: View the associated Policy or Access Zone Failover results to retrieve the SyncIQ Job Reports.  

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

T4960:  Cannot enable Script after created

If you enable a Script in the Script Editor immediately after creating it, it may not enable and the window will remain in a loading state.

Workaround: Close the Script Editor window and then re-open it to Enable the script.  

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

T4968:  Zone missing from DR Dashboard Zone Readiness tab if a SyncIQ Policy has a target host that cannot be resolved

When an Access Zone contains a SyncIQ Policy which has a Target Host configured which cannot be resolved by Eyeglass, the Access Zone does not appear in the DR Dashboard Zone Readiness tab.

Workaround: Ensure that all SyncIQ Policy Target Host can be resolved by Eyeglass.  To verify, ssh to the Eyeglass appliance and test with nslookup <target host> to confirm that it can be resolved.  

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




Configuration Replication


1683: Export sync where source  is 7.1.1.x and target 8.x.x.x

Description: Syncing exports does not function between these releases.  

Resolution:  None unsupported sync, upgrade to 7.2.x.x

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


649: Export sync where source and target path on each cluster is different is deleted and recreated in each config cycle (affects onefs 7 to 8 or 8 to 7 replication)

Description: When the path on source cluster and target of the SyncIQ policy are different, exports will be deleted on target and then recreated again  within the same replication job.  No error is seen on the config sync job.  May affect other releases as well.

Resolution:  None, export is created correctly after config sync job completes.

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

1462 - Export max_file_size cannot be replicated

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

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


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.

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


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, T3727: 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 for OneFS 7.2 - 7.2 or 8 - 8 replication.  Error will be cleared on subsequent configuration replication cycle.

For OneFS 7.2 - 8 replication, Zone Replication Readiness always has warning status and alarm is raised for failed audit on zone job.  Manually inspect that Access Zones are identical and that Zone Readiness Warning is related to this issue.

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



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.

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


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.

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


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.  

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

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

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


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.

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

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.

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


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.

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

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.

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

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


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

T593: 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.

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


T1792: Eyeglass does not auto-detect Isilon version changes and may use incorrect API version for Configuration Replication

You may see Inventory errors after upgrading the Isilon cluster version or adding a cluster to be managed by Eyeglass which has a different OneFS version than clusters already managed due to wrong version of API being used to connect to the cluster.

Workaround: Restart the Eyeglass sca service as per instructions here for sca service:

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

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

T1851: Eyeglass Configuration Replication Jobs not removed when there is no SyncIQ privilege for the eyeglass service account

If the eyeglass service account has the SyncIQ privilege removed the Eyeglass Jobs are not updated to removed even though the associated SyncIQ policy cannot be retrieved.  The Jobs run successfully with the message “The job has no data to replicate; skipping it.”

Workaround: eyeglass service account must have the SyncIQ privilege as documented in minimum permissions document here:  http://documentation.superna.net/eyeglass-isilon-edition/tech-notes/isilon-cluster-user-minimum-privileges-for-eyeglass

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

T2193 - Export max_file_size setting not replicated correctly

A large export max_file_size parameter is not replicated exactly to target as it is configured on the source which results in an Audit failure during Eyeglass Configuration Replication.  For example:

Source 4611686018427388000

Target: 4611686018427387904

Workaround:  None available. For smaller values such as 1024 or 1048576 this error does not occur.

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

T2757:  Access Zone is not replicated from OneFS 8 to OneFS 7.2

Access Zone is not replicated from OneFS 8 to OneFS 7.2.

Workaround: Create Access Zone and make updates manually.

—————————————————


T1976 - Eyeglass Jobs Window Edit Configuration does not show related Snapshot Schedules

If a Snapshot Schedule Replication Job is selected in the Jobs window, the Edit Configuration option does not mark the Snapshot Schedules which are included in the Job..

Workaround:  Expand the Snapshot Schedule Job in the Jobs window to see the Source Path.  Manually review Snapshot schedule paths.  Any Snapshot Schedule where the path is at or below the Job source path will be included in the Job.

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

T2920:  Access Zone Authentication Provider is not replicated to the target cluster

Eyeglass Configuration Replication does not sync the Access Zone Authentication Provider to the target cluster.

Workaround: Add Authentication Provider to the Access Zone manually.

—————————————————

T3383:  Audit failed when Eyeglass DFS Configuration Replication Job has NFS Exports with the same path but in different Access Zones

Eyeglass DFS Configuration Replication Job has multiple exports with same path and properties but in different Access Zones, the post replication Audit task fails due to comparing objects in different zones:

Values for key 'zone' do not match (as per value comparison method): source: <source zone>; target: <targetzone> hence audit fails




Workaround: Verify manually that properties and permissions for NFS export in their matching Access Zone are identical.

—————————————————

T3629:  Renamed Snapshot Schedule leaves original Snapshot Schedule on the target

After renaming a Snapshot Schedule, the next Configuration Replication cycle creates the new Snapshot schedule on the target but does not remove the Snapshot schedule with the original name such that on the target they both exist.

Workaround: Manually remove the extra Snapshot Schedule from the target.

—————————————————

T4297, T4299:  Eyeglass Inventory does not created short SPN for new SmartConnect Zone

If a new Smartconnect Zone is detected during Eyeglass Inventory, the SPN for the fully qualified version of the Smartconnect Zone is created but the SPN for the “short” version is not created.

Workaround: Manually create the short version of the SPN.

Note: This problem does not affect delete and create of SPNs during failover.

—————————————————


Features


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.

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


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.

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


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.

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

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

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


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

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

T1515:  Eyeglass Shell feature not functioning for RHEL and Centos deployments

If Eyeglass is deployed on a Redhat or Centos operating system the Eyeglass Shell feature does not work.

Workaround: ssh to the Eyeglass server using other tools such as putty.

—————————————————

T3119:  Access Zone Migration Preview does not always display Configuration information

The Access Zone Migration Preview window does not display the shares, exports and quotas that will be migrated if the source path selected for migration does not have an associated SyncIQ policy.

Workaround: Review shares/exports/quota paths manually to determine which configuration data will be migrated for the selected source path.

—————————————————


T3170:  Quota Requests History shows Status of Error for processed requests after failover

After failover, the Quota Requests History will show state for all processed quota requests as error instead of showing the status of the request as it was when the request was processed.

Workaround: Verify from OneFS that the quota settings are as expected.

—————————————————


T4280:  User Storage View may show all quotas instead of only the User Quotas

It may occur that the User Storage View shows all quotas configured instead of just the quotas related to the logged in User.

Workaround: Logout and refresh browser and then log back in and reopen window may clear this condition.  If not, the quota path may be used to determine which quota apply to the logged in user.

—————————————————


T4329:  DR Test Status does not open

When DR Test Job has first been created, the DR Test Status window does not open and shows the error “Readiness data not found.  Please run configuration replication.” even though Configuration Replication has run.

Workaround: DR Status window will open once DR Test Mode has been Enabled.

—————————————————

T4432:  DR Test Mode action on multiple policies do not display in Running Jobs

When multiple DR Test Jobs are selected in the DR Assistant to enable or disable DR Test mode, the Running Jobs window only shows 1 Job even though action is being applied to all selected Jobs.

Workaround: None required - display issue only.  Action completed against all selected jobs.

—————————————————

T4968:  SyncIQ Job Report Troubleshooting section missing information when report is generated on demand

When a SyncIQ Job Report is generated from the Reports on Demand window, the Troubleshooting section may not be populated.

Workaround: Use the scheduled daily report for Troubleshooting information.

—————————————————



General


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.

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

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.

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


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.

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


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

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


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.

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


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.

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


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

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


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.

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

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

The Eyeglass End User Interface DR Dashboard tree display ‘+’ can be used to expand the tree but then the ‘-’ does not collapse the tree again.

Workaround: Close and reopen the window

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

T1514:  Eyeglass Archive cannot be downloaded when Eyeglass is deployed on Redhat or Centos

Eyeglass Backup Archive file cannot be downloaded from the Eyeglass web page if Eyeglass is deployed on a Redhat or Centos operating system.

Workaround: The Eyeglass Backup Archive files are stored here on the Eyeglass server: /srv/www/htdocs/archive/  and can be copied from this location with a tool such as WinSCP.

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

T3137 - Eyeglass daily backup not working for RHEL/CentOS Deployments

The scheduled daily backup for Eyeglass is not working for RHEL/CentOS deployments.

Workaround:  Manually create backup file from the Eyeglass GUI:  About/Contact -> Backup -> Create Full Backup

———————————

T4596: Log Viewer cannot fetch logs

Under certain conditions the Log View may not be able to Fetch logs.  

Workaround: Use the About/Contact -> Backup to create a Backup Archive and then download to your local system to review logs.  

The Log View feature will be deprecated in a future release.

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


T4765: Cluster Report Created date is not preserved on Restore

When you restore an Eyeglass appliance from it’s backup file, the Cluster Reports are restored, but in the GUI the Created date shows the date/time the files were restored instead of the date/time they were created.  

Workaround: The date/time created can also be viewed by opening the file.  At the top you will see the date and time of the file creation.

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


T5206: Eyeglass Shell Not Available with 1.9.4 and OpenSUSE 42.3

The Eyeglass shell feature is not working as of Release 1.9.4 and OpenSUSE 42.3.  

Workaround: Use an external tool such as putty to access the Eyeglass appliance command line.

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



Superna Eyeglass Known Limitations

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




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.

T1785  Cannot set ignore flag on subnet pool after failback

It is not supported to apply an igls-ignore flag on a subnet pool that has been failed over and failed back such that the SmartConnect Zone has an igls-original prefix due to the fact that on a subsequent failover the igls-original prefix will not be removed and will leave the Access Zone in a state where both directions are failed over.

Workaround:  Manually edit SmartConnect Zone on active cluster to remove the igls-original prefix.  Run Configuration Replication and then run the Failover Readiness job to update Zone Readiness.


T2479: Access Zone Failover fails between OneFS 7.2 clusters if Eyeglass also managing OneFS 7.1

For the case where Eyeglass is managing OneFS 7.2 and OneFS 7.1 clusters, an Access Zone failover between OneFS 7.2 clusters will fail as OneFS7.1 linmap command is attempted and fails.

Workaround: Access Zone failover in this Configuration is unsupported as for Eyeglass Inter-version management, it is expected to apply capabilities of lower versions to all versions being managed and Access Zone failover for OneFS 7.1 is not supported. No workaround required.

T3258: Cannot start failover while Eyeglass initial inventory is running

For the case where Eyeglass has been restarted and the initial inventory is running for initial discovery, while the initial inventory is running a failover cannot be started.  A “Failover configuration is not valid” message will be displayed in the GUI followed by a message that the target cluster is not managed by Eyeglass.

Workaround: Wait for initial inventory to completed before initiating a failover.   Check running jobs windows for the initial inventory job to show completed.

T3774: Failover relies on policy naming: <policy name> and <policy name_mirror>

The Superna Eyeglass failover relies on following naming conventions:

  1. First failover A to B- policy name = <policy name>.

The first failover name cannot be <policy name>_mirror.

  1. Second failover B to A - policy name = <policy name>_mirror.

Workaround: Manual process on naming the convention above must be followed.

T4808: SPNs not updated for new authentication providers after Access Zone settings changed to “Use all authentication providers” (OneFS 7.2)

If an Access Zone is modified from manually defining the authentication providers to using the “Use all authentication providers” setting in OneFS 7.2, Eyeglass will not update SPNs for any new authentication providers that where not previously provisioned.

Workaround: Manual process required to create these SPNs.


Known Limitations for Eyeglass Configuration Replication

Multi-Path Exports

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.

Export cannot have multiple paths that span multiple Eyeglass Jobs

Export with multiple paths that are protected by different SyncIQ policies is not supported.  This export configuration is not supported for DR as it would not allow per policy failover and is an unsupported configuration for Eyeglass.

The solution for this is to split the single export into multiple exports each with paths that correspond to a single SyncIQ policy.


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.

T1743  Multiple export with same path and same client do not show Configuration Replication Error

Multiple exports with the same path are required to have different clients in order to be replicated as per Isilon default behaviour.  In the case where they have been provisioned with same client, Eyeglass Configuration Replication will only show error for this condition on the second configuration replication cycle.

T1847  OneFS 8 Overlapping Access Zone Replication has error

In OneFS 8 where there are Access Zones have identical paths, Eyeglass Access Zone Replication will fail with the following error from the Isilon cluster:  AEC_CONFLICT “field” “path” “message” “access zone base path \*/ifs\* overlaps with base path \*/ifs/data/zone\* in Access Zone Use the force overlap option to override. In this case disable Eyeglass Configuration Replication Jobs for Access Zones and manually create the Access Zone on the target cluster.

T1972  Snapshot schedule replicated with offset

Snapshot schedule expiration offset has OneFS API bug that adds extra time to snapshot expiration when the snapshot schedule is created.  This results in an expiration on the DR cluster, that can be greater than entered on the source cluster.   example expire in 20 days will be 22 days on the target cluster.  Different units of off set all result in a value greater than entered.   After failover the DR (target cluster) value will be synced back to the source (Prod cluster).  Thereby losing the original expiry offset  and extending the expire time by a new offset from the API error.  This has been raised with EMC as SR to resolve.

  1. Work around:  Before failover ensure a cluster report has been generated (cluster reports icon), or an existing emailed cluster report exists.   Post Failover re-enter the original values on the DR snapshot schedules using the cluster report values from the source cluster as a reference.

  2. Another option is disable Snapshot Sync jobs in the jobs window if the above workaround does not meet your needs to preserve expiry of snapshot settings.

UPDATE: Resolution for this OneFS issue is available in OneFS 8.0.0.3

T2046  Access Zone Replication limitation when all user mapping rules are deleted

Access Zone Replication successfully creates and updates user mapping rules and also successfully deletes user mapping rules except when all user mapping rules are removed from the source.  In the case where all user mapping rules are deleted from the source, the Access Zone configuration replication job will not delete all on the target - the user mapping rules remain on the target.

T2241  Incorrect missing SPN alarm issued when Isilon cluster joined to multiple Domains

In an environment where the Isilon cluster is joined to multiple Domains, the OneFS SPN check command for a specified domain returns list of SPNs from other domains and lists them as missing.  In this case Eyeglass issues an SPN alarm for missing SPNs based on the list returned even if there are no missing SPNs in the domain specified in the check command.


T2779 - Eyeglass Configuration Replication “Full Sync Mode” always updates when Default Settings on Source and Target cluster are not the same

If on the Source and Target cluster for an Eyeglass Configuration Replication Job the “Default Settings” say for SMB are not the same, each replication cycle will perform an update operation even though the shares are already synced and identical.  Making the Default Settings the same for both clusters will eliminate this behaviour and return to expected behaviour to not perform the update when shares are determined to already be identical.

T2780  Same host moved to different NFS Export Client list not updated on target

For the cases where:

  • same host is provisioned on multiple client list and then one host is removed

  • Same host is moved from one client list to another

The change in NFS client list is not replicated to the target cluster.  Target cluster client list must be updated manually.

T2908  New Eyeglass Configuration Replication Job cannot recover state and mode from the Eyeglass Fingerprint file.

When a SyncIQ Policy is renamed, Eyeglass considers it to be a new SyncIQ Policy and therefore creates a new Eyeglass Configuration Replication Job with the new name.  The Eyeglass Fingerprint file which holds Eyeglass Configuration Replication Job Mode and State for recovery does not link the original Job name with the new name and can therefore not be used to recover these properties for the new Eyeglass Job.


T4289  Delete Share or Export may result in temporary Audit error

After a share or export is deleted as part of Eyeglass Configuration Replication Job, the next Eyeglass Configuration Replication Job Audit task may incorrectly expect that the object is not deleted resulting in a alarm such as “ Replication job audit failed" - "objects not found on source or target cluster, hence audit fails” .  The error is cleared on the next Eyeglass Configuration Replication Job where the Audit task correctly does not try to audit the deleted object.


Known Limitations for Eyeglass Features

T2350:  Quota Self Serve Portal: Local Group Quotas not displayed when logged in with Local Group User

Quotas associated with a Local Group (for example wheel) are not displayed in the Quota self serve portal when logged in as a Local Group User for that group.


T1962: Default Role incorrectly shows Delete option

Eyeglass User Roles Default Roles incorrectly provide the option to be deleted when in fact they cannot be deleted.

Workaround: None Required.  If the Delete option is selected the Default Role is not deleted.


Known Limitations for Eyeglass General

T2289  Backup Archive Job is not always displayed in the Running Jobs window

In some cases after a Backup Archive job is initiated it will not appear as a running task in the Jobs / Running Jobs window.  Archive is still created and available for download on completion.

T2908  Renamed SyncIQ Policy does not link to RPO Reports from original SyncIQ Policy Name

When a SyncIQ Policy is renamed, Eyeglass considers it to be a new SyncIQ Policy.  Therefore RPO Reporting for the original SyncIQ Policy name will not be linked to RPO reporting for the new SyncIQ Policy name.


T3170 Pending Quota Requests are not preserved on failover

If a failover is done while there are Quota Pending Requests, the Pending Requests are lost as the quota to which the request was originally made no longer exists on the original cluster after failover.  The pending quota request will appear in the Quota Requests History in Error state.


T4579 Upgrade from 1.5.4 to 1.9 and greater Failover History retrieves Failover Log for SyncIQ Job Reports

After an upgrade from 1.5.4 to 1.9 or greater, in the DR Assistant -> Failover History list the link to open SyncIQ Job Reports opens the Failover Log due to fact that prior to this release Failover Log and SyncIQ Job Report log were combined.  In this case you are able to see the SyncIQ Job Reports related to failover at the bottom of the Failover Log.