What’s New in Superna Eyeglass PowerScale Edition Release 2.5.5

eyeglass ALL=(ALL) NOPASSWD: /usr/bin/isi_for_array -s isi_run -z ? isi_classic smb file*

T11585 DR Dashboard incorrectly displays SSIP when IP Pool Smartconnect Subnet is not in same subnet as pool

When the Smartconnect Subnet on a IP pool is different that the subnet the IP pool was created in the DR Dashboard displays the incorrect SSIP.

Workaround: None Required. No impact to failover capabilities. Refer to PowerScale networking for correct SSIP.

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

T11697 API call corner case may affect failover for Ransomware Defender and Easy Auditor customers

There is a small probability for Ransomware Defender and Easy Auditor customers that a corner case condition could affect a critical API call during failover that does not have a retry.

Workaround: Contact support.superna.net for assistance in updating Eyeglass configuration settings to mitigate this issue.

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

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 PowerScale 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-PowerScale-edition/Eyeglass-PowerScale-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 PowerScale version changes and may use incorrect API version for Configuration Replication

You may see Inventory errors after upgrading the PowerScale 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-PowerScale-edition/Eyeglass-PowerScale-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-PowerScale-edition/tech-notes/PowerScale-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.

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

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.

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

T11893 Eyeglass unable to create Configuration Replication Jobs for OneFS 8.2 SyncIQ policy using SSIP as target host

When using OneFS 8.2 if the SyncIQ policy target host is set to use SSIP of target cluster Eyeglass will be unable to create the related Configuration Replication job. This could also affect mirror policy jobs that are created by PowerScale OneFS as part of failover where PowerScale has selected SSIP as target host.

Workaround: Configure a replication pool on the target cluster and configure SyncIQ policy target host to point to the replication pool smartconnect zone.

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

T15884 Some scenarios in networking API failures during Configuration replication may not block deletes

Some scenarios remain after resolution in T12773 where when Eyeglass has an incomplete view of PowerScale configuration due to a PowerScale PAPI networking API call failure there is a risk of deleting and readding Eyeglass Configuration Replication Jobs and losing their settings such as DFS mode or AutoSkipConfig mode or risk of deleting meta data such as SMb shares or NFS exports.

Workaround: In 2.5.6 all new Eyeglass configuration replication jobs will be in an unconfigured state. When activating ensure that you are activating in the correct mode: AUTO, DFS or AUTOSKIPCONFIG.

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

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

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

T5173:  Quota Modification Request window does not close after Submit

After a Quota Modification Request is submitted, the window does not close and remains in a loading state.

Workaround: None required - display issue only.  Action was completed and the request can be seen in the Pending Requests window.

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

T6389:  Built-In AD Groups cannot be used with the Cluster Storage Monitor Active Directory Managed Quota feature

When configuring Cluster Storage Monitor AD Group Mode Templates for automated quota creation, AD built-in groups such as "domain users" cannot be used as the users in the group will not be correctly identified.

Workaround: Create new AD Group for quota assignment and add this group to related shares in PowerScale. For additional information on use of AD groups for share security vs quota creation please read here.

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

T8716:  Upgrade issues for Cluster Storage Monitor Quota or Data Recovery requests

After upgrade to new release see following issues for Quota or Data Recovery requests:

1) Data Recovery does not show any pending requests or history

2) Quota Request shows history but with incorrect status

Workaround: None available for history. For Data Recovery pending request, re-issue the request.

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

T8834:  Storage Monitor Report missing user information when friendly name cannot be resolved

User quotas created for users who are not in the default AD Domain, a friendly name cannot be resolved and quota itself is associated with user SID but in the Storage Monitor Report the user is reported as "user" instead of showing user SID.

Workaround: None available.

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

T9561:  Unlock my files incorrectly displays directories

Unlock My Files window incorrectly includes directories in the display instead of just files. If a directory is inadvertently "unlocked" it may disconnect clients or have other unexpected results.

Workaround: Do not use unlock for directories.

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

T9621, T14813:  Unable to break lock for filenames/path with special characters

When a filename/path contains special characters, Unlock My Files is unable to break the lock. Message displayed says "No open session...."

Workaround: Use manual procedure to unlock.

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

T11807 Alarm for quota synchronization error does not contain error details

For case where quota synchronization fails (example advisory threshold configured to be greater than hard threshold), an Eyeglass alarm is raised but the alarm does not contain any details of the error.

Workaround: In Eyelgass Jobs / Running Jobs window tree view under "Group Quota Synchronization Steps" navigate down the tree and find the step with an error. The Info link should contain error details if available.

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

T11882 Storage Monitor Report - UserGroupQuotasReport does not include Group quotas

The UserGroupQuotasReport which reports on quotas created by the Superna Eyeglass Quota Automation reports on user quotas created but does not include group quotas.

Workaround: QuotaSummaryReport also display quota information without the related tier from which quota was created by automation.

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

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,T11989: Some alarms not cleared

Alarms other than the “Replication job failed to run “ are not cleared automatically once the error condition has been resolved. Example, DR Readiness alarm not cleared once readiness is green.

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.

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

T11083 Restore from backup does not preserve failover scripts

If you have configured pre or post failover scripts, the restore from backup does not restore the scripts to the new appliance.

Workaround: 1. Make a manual external backup of failover scripts.  2. Failover scripts may also be available in the backup zip file. 

Superna Eyeglass Known Limitations

Known Limitations for PowerScale 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.

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

T6229: Existing Failover Logs cannot be reviewed after upgrade to Eyeglass R2.0

Failover logs which were generated from previous releases cannot be viewed from the Eyeglass DR Assistant Failover History view after upgrade to Eyeglass R2.0

Workaround: Generate an Eyeglass Backup and download to your local machine.  The Failover logs are contained in the backup archive in the folder failover_logs.

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 PowerScale 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 PowerScale 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 PowerScale cluster joined to multiple Domains

In an environment where the PowerScale 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.

T5972  No Error Message for Duplicate NFS Export on OneFS 7.2 Configuration Replication Failed

Duplicate NFS Export on OneFS 7.2 Configuration Replication failure is expected, however in this case there is no specific Info associated with failed step to identify the issue.

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.

T7980: Cluster Storage Monitor AD Group Template Quota Creation does not created group quota for nested AD Groups

If an AD Group has sub-groups (nested groups) is configured as a Template for automated group quota creation, no group quotas will be created for sub-groups.

Workaround: Each group that requires automated group quota creation must be explicitly added to the relevant share permissions.

T8362: Cluster Storage Monitor AD Group Template Quota Creation does not respect highest quota settting user quota in nested AD Groups

If an AD Group has sub-groups (nested groups) is configured as a Template for automated user quota creation, user quota creation follows explicitly the quota limit for the sub-group when the user already has a quota for a higher limit. In this case, what should have happened is that template setting is ignored if there is already an existing user quota with a higher limit.

Workaround: Avoid use of nested AD groups for automated user quota creation.

T8193: special charaters in Cluster storage monitor AD managed quota templates is not supported

If an AD Group templates, if the AD group name has special characters in the AD group name the quotas will not be applied.

Workaround: Avoid use of special characters when creating AD groups for AD managed quotas.

T9622: Unlock My Files! does not indicate error when PowerScale node is not reachable

If an PowerScale node is unreachable when Eyeglass is searching for open files there is no error message for the unreachable PowerScale nodes.

Workaround: None available.No open files displayed for unreachable nodes.

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.

T6300 After an Eyeglass restore with the -anyrelease option the print screen functionality for SyncIQ Job Reports and Eyeglass backups may be in error

After an Eyeglass restore to a new appliance using the --anyrelease option, print screen functionality may no longer be working due to a incorrect permission setting.  This impacts SyncIQ Job Reports which will be missing the charts and generating an Eyeglass backup with print screens.

To workaround this issue:

1) ssh to the eyeglass appliance and login with the admin account (default password 3y3gl4ss)

2) assume root user by typing

sudo su -

And entering the admin password

3) vi /opt/superna/sca/data/Screenshots.json and write "<placeholder>" as a value in the "plain_text" field and then save it.
4) Copy and paste the following commands:

str=$(sudo cat /dev/urandom | tr -dc 'a-zA-Z' | fold -w 12 | head -n 1)

echo -e "$str\n$str" | passwd screenshots

sed -i "s/<placeholder>/$str/" /opt/superna/sca/data/Screenshots.json

  5) Start a backup with print screens and follow in Running Jobs to verify the backup completes successfully.

T12034 Eyeglass appliance rediscover does not preserve Eyeglass Job state unless Configuration Replication has run

If a change is made to an Eyeglass Job state or Job type and then there is an appliance rediscover before configuration has been run the changed Job state / type will be lost.