Release 1.6.1 release Notes

Contents

  1. 1 What’s New in Superna Eyeglass Isilon Edition Release 1.6
  2. 2 What’s New in Superna Eyeglass Isilon Edition Release 1.6.1
  3. 3 Supported OneFS releases
  4. 4 Feature Release Compatibility
  5. 5 Inter Release Functional Compatibility
  6. 6 Feature Support Matrix
  7. 7 End of Life Notifications
  8. 8 Issues Fixed in Eyeglass Release 1.6
    1. 8.1 Failover
      1. 8.1.1 3047: Zone Readiness not calculated correctly when Policy Diverse Target Requirement is not met
      2. 8.1.2 T627: Zone Readiness for Policy Source Nodes Restriction not reported properly for OneFS 8.0
      3. 8.1.3 T795: DFS Failover log uses Access Zone ID
      4. 8.1.4 T797: Zone Readiness does not show System Access Zone if it only contains disabled policies
      5. 8.1.5 T813: Uncontrolled DFS Failover Log incorrectly shows Resync Prep step as being selected
      6. 8.1.6 T972: Failover Wizard selection is not cleared
      7. 8.1.7 T942: Failover Log for Uncontrolled Failover incorrectly lists the delete quota step
      8. 8.1.8 T1285:  Failover log does not display the Post Failover steps
      9. 8.1.9 T1349: SPN Readiness does not show Active Directory Domain after Access Zone Failover
      10. 8.1.10 T1355:  Uncontrolled failover incorrectly attempts to delete Quotas on the Source Cluster
      11. 8.1.11 T1364:  Error after upgrade to 1.5.2 when starting failover
      12. 8.1.12 T1345:  Mirror policy not DFS enabled after failover if Quota Job fails
      13. 8.1.13 T1303:  REST API does not validate failover target
      14. 8.1.14 T1518:  Zone Readiness alarm severity to match validation severity
    2. 8.2 Configuration Replication
      1. 8.2.1 1354: Update export path creates new export instead of updating existing one
      2. 8.2.2 2081: Update export job shows error when multi-path export overlaps the path of a single path export
      3. 8.2.3 T578: Multiple exports with same path have replication error if Clients are identical , audit error if Clients are different
      4. 8.2.4 T873: Eyeglass errors for multiple exports with the same path
      5. 8.2.5 T979: NFS Alias created instead of updated for A -> B -> C replication topology
      6. 8.2.6 T976: Eyeglass Zone Configuration Replication “Edit Configuration” window does not show the correct zone
      7. 8.2.7 T982: Deletion of Shares and Exports does not work for A -> B -> C replication topology
      8. 8.2.8 T1358:  Export update does not handle removal of clients from client list
    3. 8.3 Features
    4. 8.4 General
      1. 8.4.1 896: YaST Update Manager inconsistent between recommended and optional updates
      2. 8.4.2 1080: New inventory may not appear in change management report for alarms
      3. 8.4.3 T786: No error when adding managed device and no licenses available
      4. 8.4.4 T883: Eyeglass End User Interface Tree View Expanders do not collapse
      5. 8.4.5 T954: Eyeglass “Restore” operation does not restore failover logs
      6. 8.4.6 T1467:  Info cannot be opened for Failed to retrieve inventory and Inventory is degraded/incomplete alarms
      7. 8.4.7 T1420:  Change Management Report contains no data
  9. 9 Known Issues
    1. 9.1 Failover
      1. 9.1.1 1747: Access Zone Failover SPN’s inserted to all AD providers found on target cluster
      2. 9.1.2 175: DFS Readiness Status Pending blocks Failover
      3. 9.1.3 2666/2723: Problems for Controlled Failover when Source becomes unreachable during failover
      4. 9.1.4 2278: Zone Readiness lists Access Zone after all related SyncIQ Policies are deleted
      5. 9.1.5 2919: Eyeglass Configuration Replication Jobs may not display in the Zone Readiness Eyeglass Configuration Replication Readiness list
      6. 9.1.6 3010: Unexpected results for failover where total number of objects exceeds the published limit
      7. 9.1.7 3029: Zone Readiness not calculated correctly for SyncIQ subnet pool with a mapping hint
      8. 9.1.8 3031: Zone Readiness Policy Path Containment Check results in extra errors
      9. 9.1.9 3077: Zone Readiness does not catch pool mapping hint misconfiguration for partial string match
      10. 9.1.10 T477: No Policy Hot/Hot Validation Error for policy with no share/export
      11. 9.1.11 T482: Zone Readiness shows OK for multiple Smartconnect Zone Mapping errors
      12. 9.1.12 T654: Zone Readiness incorrectly includes SyncIQ Policy in System Access Zone
      13. 9.1.13 T1465:  Failover option to Disable SyncIQ on Failover Target still runs the policy before disabling it
      14. 9.1.14 T1690:  Zone Readiness for pool where service subnet is not the same as pool subnet blocks Access Zone failover for OneFS 7.2
      15. 9.1.15 T1712:  Zone Readiness missing Zone when pool has no SmartConnect Zone - OneFS 7
      16. 9.1.16 T1716:  Eyeglass Runbook Robot NFS mount not functioning for RHEL and Centos deployments
      17. 9.1.17 T1482:  Zone Readiness SyncIQ Readiness not updated after Access Zone associated to a pool
    2. 9.2 Configuration Replication
      1. 9.2.1 1683: Export sync where source  is 7.1.1.x and target 8.x.x.x
      2. 9.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. 9.2.3 1822: Export is created each time Config Replication runs when two exports one multi path and one single path export with  a path in common
      4. 9.2.4 1462 - Export max_file_size cannot be replicated
      5. 9.2.5 1355: Edit Job configuration to include share/export deselected from another Job causes share/export to be reselected.
      6. 9.2.6 1580: Delete and Create export within same replication cycle orphans deleted export on the target with OneFS 7.1.1.x
      7. 9.2.7 1625: Custom QUOTA Jobs require extra replication cycle to be deleted
      8. 9.2.8 1639: Able to manually Run Now disabled Custom Job
      9. 9.2.9 1641: Custom Job does not include shares/export when source or destination path configured with a trailing /
      10. 9.2.10 1788: Delete of unlinked user quota on source may not delete matching quota on the target
      11. 9.2.11 1789: Able to select shares/exports/quotas outside job path after deselected
      12. 9.2.12 1887: Multiple SyncIQ policies associated with same Zone will result in transient error on Eyeglass Zone replication creation
      13. 9.2.13 1924: Quotas on excluded SyncIQ directory are selected for replication
      14. 9.2.14 1998: Custom Eyeglass configuration replication Job does not have an associated Zone replication Job
      15. 9.2.15 2004: Custom Quota Job is incorrectly listed in the Failover: Quota Failover (RUN MANUALLY) section in the Jobs window
      16. 9.2.16 2007: Job error after deleting quota
      17. 9.2.17 2038: Create alias results in temporary error
      18. 9.2.18 2043: Configuration replication job has error after zone is deleted
      19. 9.2.19 2045: Edit Configuration for Custom Job has multiple source cluster selected where Eyeglass is managing more than 2 clusters
      20. 9.2.20 2046: Job Edit Configuration view has the wrong parent selected
      21. 9.2.21 2049: Delete Zone does not delete associated configuration items on target for custom Jobs and auto jobs with disabled zone Job
      22. 9.2.22 2235: Eyeglass replication Job does not complete when source cluster becomes unreachable after Job has started
      23. 9.2.23 2060: Access Zone Replication Error - Error on creation of shared resource
      24. 9.2.24 2488: Inconsistent behaviour in Run Now for Disabled Jobs
      25. 9.2.25 1938: Issues with Eyeglass Configuration Replication Jobs after the Access Zone is deleted
      26. 9.2.26 2308: In EyeGlass, NFS alias health is always 'unknown'
      27. 9.2.27 2804: Disabled SyncIQ Policy is not initially displayed as Policy Disabled in Eyeglass
      28. 9.2.28 T676: Eyeglass Zone replication Job does not replicate all authentication providers for OneFS 8.0
      29. 9.2.29 T723: Job shows OK when there is an Access Eyeglass Zone Replication Error
      30. 9.2.30 T771: Edit Configuration does not show parent node selected
      31. 9.2.31 T805: Eyeglass Configuration Replication Jobs not updated when IP address changed on Source Cluster
      32. 9.2.32 T593: Eyeglass errors for multiple exports with the same path
      33. 9.2.33 T1792: Eyeglass does not auto-detect Isilon version changes and may use incorrect API version for Configuration Replication
      34. 9.2.34 T1852: Eyeglass Configuration Replication Jobs not removed when there is no SyncIQ privilege for the eyeglass service account
    3. 9.3 Features
      1. 9.3.1 1138: Eyeglass UI does not block configuration of duplicate remote logging service
      2. 9.3.2 1213: Change Management Report for all Isilon Clusters
      3. 9.3.3 2218: SyncIQ Job Report link to RPO documentation is broken
      4. 9.3.4 2224: Eyeglass Cluster Configuration Report runs when Cluster is unreachable
      5. 9.3.5 2061: Access Zone name for Directory Migration is case sensitive
      6. 9.3.6 2882: Phone Home Email Disabled
      7. 9.3.7 3037: Configure Remote Logging Services in Eyeglass requires manual steps
      8. 9.3.8 T758: Live Ops DR Test Mode does not work for for DFS enabled policies
      9. 9.3.9 T1515:  Eyeglass Shell feature not functioning for RHEL and Centos deployments
    4. 9.4 General
      1. 9.4.1 924: Inventory View shows + beside component when there are no more children
      2. 9.4.2 943: Inventory View not auto-refreshed
      3. 9.4.3 1612: Some alarms not cleared
      4. 9.4.4 2155: Access Zone Networking info does not display in Inventory View
      5. 9.4.5 2628: Job Definitions window does not sort properly
      6. 9.4.6 2895: Inventory SPN View is truncated
      7. 9.4.7 2366: EyeGlass does not support special characters in email recipient address
      8. 9.4.8 2385: Refresh Now does not refresh the Failover History window
      9. 9.4.9 2744: Failed to Retrieve Inventory Alarm missing information
      10. 9.4.10 2978: Syslog Log Viewer freezes Eyeglass web page
      11. 9.4.11 T971: Eyeglass End User Interface Tree View Expanders do not collapse
      12. 9.4.12 T1514:  Eyeglass Archive cannot be downloaded when Eyeglass is deployed on Redhat or Centos
  10. 10 Superna Eyeglass Known Issues
    1. 10.1 Known Limitations for Isilon OneFS 8.0.0.x with Eyeglass
      1. 10.1.1 T507 Cluster Report for OneFS 8.0 missing information
      2. 10.1.2 T831 Failover Allow Writes step not allowed when quotas being created in OneFS 8.0
      3. 10.1.3 Known Limitations for Eyeglass Failover
      4. 10.1.4 T939  Eyeglass Access Zone Replication Job in Error after failover
      5. 10.1.5 T1785  Cannot set ignore flag on subnet pool after failback
      6. 10.1.6 Known Limitations for Eyeglass Configuration Replication
      7. 10.1.7 Multi-Path Exports
        1. 10.1.7.1 T1359  Update NFS Multi-Path Export path(s) may cause transient Configuration Replication Error
        2. 10.1.7.2 Export cannot have multiple paths that span multiple Eyeglass Jobs
      8. 10.1.8 T1743  Multiple export with same path and same client do not show Configuration Replication Error
      9. 10.1.9 T1847  OneFS 8 Overlapping Access Zone Replication has error




What’s New in Superna Eyeglass Isilon Edition Release 1.6

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


What’s New in Superna Eyeglass Isilon Edition Release 1.6.1

Failover Validation acknowledge step to set SyncIQ Job schedule to Manual prior to failover has been added in 1.6.1.  This is related to Technical Advisory #6.



Supported OneFS releases


7.1.1.x

7.2.x.x

7.2.1.x

8.0.0.x


Feature Release Compatibility


Feature

Source Cluster  Release

Target SyncIQ Cluster Release

Configuration Replication

non-DFS mode



 Configuration Replication

7.1.x.x

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

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

7.2.x.x**

SyncIQ Policy Failover

non-DFS mode



SyncIQ Policy Failover

7.1.x.x

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

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

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

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

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

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

8.0.x.x

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



Inter Release Functional Compatibility


OneFS 7.2 - OneFS 8.0

OneFS 7.1 - OneFS 8.0

Eyeglass Configuration Replication

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




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


April 25, 2016






Issues Fixed in Eyeglass Release 1.6

Failover

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.

Resolution: Not Applicable - Policy Diverse Target is no longer a required for Access Zone Failover with introduction of Multi Site Access Zone failover support in Release 1.6.

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

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

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

Resolution: Eyeglass Zone Readiness now correctly detects and displays the Restrict Source Nodes setting for SyncIQ Policy in OneFS 8.

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

T795: DFS Failover log uses Access Zone ID

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

Resolution: Failover log now references the Access Zone name.

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

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

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

Resolution: DR Dashboard / Zone Readiness now shows the System Access Zone if that Access Zone only has Disabled SyncIQ Policies

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

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

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

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

Resolution: Failover Log now correctly shows that ResyncPrep step is NOT executed for Uncontrolled DFS failover.  For example:

2016-03-15 15:53:24::791 INFO SyncIQ Resync Prep : false

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

T972: Failover Wizard selection is not cleared

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

Resolution: Closing the Failover Wizard window now clears previously selected policies.

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

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

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

Resolution: Quota operation on Source cluster are no longer attempted for Uncontrolled failover.  The log message indicates that the quota step was skipped.  For example:

2016-04-29 08:23:29::867 INFO Starting Step: "Quota operations on source cluster are skipped"

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

T1285:  Failover log does not display the Post Failover steps

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

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

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

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

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

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

Resolution: After an Access Zone Failover, the Superna Eyeglass Zone Readiness / SPN Readiness view now shows the domain associated with the Access Zone that was shown previously before the failover.

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

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

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

Resolution: Quota operation on Source cluster are no longer attempted for Uncontrolled failover.  The log message indicates that the quota step was skipped.  For example:

2016-04-29 08:23:29::867 INFO Starting Step: "Quota operations on source cluster are skipped"

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

T1364:  Error after upgrade to 1.5.2 when starting failover

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

Resolution: This condition no longer causes an error.

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

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

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

Resolution: DFS Failover mirror policy Eyeglass Configuration Replication Job is now correctly enabled in DFS mode as expected.

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

T1303:  REST API does not validate failover target

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

  • Target is same cluster as the source

  • Zone Readiness not executed  

Resolution: REST API now validates the failover target.

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

T1518:  Zone Readiness alarm severity to match validation severity

Issues of all severities encountered during Zone Readiness validation result in a Zone Readiness alarm of Critical severity.

Resolution: Zone Readiness Critical alarm is now only sent if Zone Readiness status is Error. Zone Readiness status of Warning no longer results in alarm.

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


Configuration Replication

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.  

Resolution: Export with old path is deleted from the target after the export with the new path is created.

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




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.

Resolution: Eyeglass Job no longer has an error for this case.

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

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

If there are multiple exports with the same path and identical Clients, configuration replication job will be in  error:  AEC_EXCEPTION,message Export rules <exportid>  and <exportid> conflict on <path>" .  This is expected.  

If there are multiple exports with the same path and different Clients, configuration replication job will succeed but the DR Dashboard audit will fail because due to comparing the wrong exports.

Resolution: It is a requirement for exports with the same path to have different Clients in order for add, update and delete exports to function with Eyeglass.

DR Dashboard Audit error is targeted for resolution in next release.  This error does not block failover.  When this error occurs, manually inspect NFS export in error on source and target cluster to confirm that all properties are identical.

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

T873: Eyeglass errors for multiple exports with the same path

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

Resolution: It is a requirement for exports with the same path to have different Clients in order for add, update and delete exports to function with Eyeglass.

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

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

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

Resolution: NFS Alias update is now correctly synced to Cluster C.

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

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

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

Resolution: Eyeglass Zone Configuration Replication “Edit Configuration” window now shows the correct zone..

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

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

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

Resolution: Shares and Exports deleted on Cluster A are now deleted on Cluster B and Cluster C as expected.

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

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

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

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

Resolution: Removal of an export from an export client list on the source is now correctly synced to the target cluster by Eyeglass.

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


Features



General

896: YaST Update Manager inconsistent between recommended and optional updates

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

Resolution: Not applicable - YaST Update Manager discontinued.  Use yast2 from command line..

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

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.

Resolution: Not Applicable in Release 1.6 as the Alarm Change Management report has been disabled.

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

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

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

Resolution: As of Release 1.6, you are blocked from adding managed device when there is no available license.

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

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

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

Resolution: Inventory View tree display can be expanded and collapsed using the ‘+’ and ‘-’ controls as expected.

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

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

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

Resolution: Failover Logs are restored now when an Eyeglass backup archive is restored to a new Eyeglass appliance.

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

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

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

Resolution: Alarms window info for “Failed to retrieve inventory” and “Inventory is degraded/incomplete” now opens to display additional info.

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

T1420:  Change Management Report contains no data

The Change Management Report does not contain any data in Eyeglass 1.5.4 due to a database query issue.

Resolution: Change Management Report query issue has been resolved and report is now populated.


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







Known Issues


Failover


1747: Access Zone Failover SPN’s inserted to all AD providers found on target cluster

Description: Only on failover, Access Zone SPN involved in the failover are incorrectly inserted into all ad providers on the target cluster versus  only the AD provider of the target access zone.

Workaround: Delete the SPN’s from the failover log generated by eyeglass from the AD providers (if more than one AD provider exists) for other access zones with that provider defined.  Impact of this does not allow authentication, since the smartconnect zone names do not exist in the other Access Zones so the SPN would never be valid.  It will be detected.  Using ADSI edit tool remove the SPN’s.  Impact none to failover.



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

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


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.

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

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

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

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

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

T1690:  Zone Readiness for pool where service subnet is not the same as pool subnet blocks Access Zone failover for OneFS 7.2

For the case where a pool has configured the service subnet as a subnet that is different from the subnet that the pool was created in and cluster version is 7.2, Eyeglass Zone Readiness will not display the Access Zone and therefore the Access Zone will not be available for failover.

This is not an issue for OneFS 8.

Workaround: If possible, use the same subnet for the pool service subnet as the subnet that the pool was created in.

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

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/Eyeglass-Isilon-Edition#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.  

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


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.

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

1822: Export is created each time Config Replication runs when two exports one multi path and one single path export with  a path in common

Description: Have two exports, one single path and one multi path export. One path is overlapping on both exports.  Client lists are unique on each export.  Config Replication runs and  exports are replicated on target cluster.  Each time Config Replication runs, single path export is deleted and created again. No  updates are done to the exports.  This behavior isn't 100% reproducible.

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

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


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

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


T1852: 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

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



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.

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


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

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


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.

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


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

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

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

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

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

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

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

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.

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



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.

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


Superna Eyeglass Known Issues

Known Limitations for Isilon OneFS 8.0.0.x with Eyeglass


T507 Cluster Report for OneFS 8.0 missing information

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

  • DNS and Subnet information

  • File System Explorer

  • Protocols - new HDFS, FTP, HTTP settings


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

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

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


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


Known Limitations for Eyeglass Failover

T939  Eyeglass Access Zone Replication Job in Error after failover

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

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

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.


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. 

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.