What’s New in Superna Eyeglass Isilon Edition Release 1.8.3
What’s New! In Superna Eyeglass Isilon Edition Release 1.8.3 can be found here. Supported OneFS releases7.1.1.x 7.2.x.x 7.2.1.x 8.0.0.x 8.0.1.x Feature Release Compatibility
** 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
Feature Support Matrix
End of Life Notifications
Features Disabled in Eyeglass Release 1.8.3FeaturesT3781 SyncIQ Job Report has Screenshots disabled by default In some cases SyncIQ Job Report screenshot feature was causing memory issues on the Superna Eyeglass appliance. As a result, the Screenshot feature of SyncIQ Job Report has been disabled in R1.8.3. It is planned to re-enable once the memory issue has been addressed in a future release. Note: If this feature is not causing an issue in your environment, it can be re-enabled by following these steps:
igls adv skipscreenshots set --skip=false —————————————————– Issues Fixed in Eyeglass Release 1.8.3FailoverT2946: Zone Readiness Eyeglass Configuration Replication Readiness shows OK when cluster is unreachableFor the case where cluster is unreachable, Zone Readiness Configuration Replication Readiness check incorrectly shows Eyeglass Configuration Replication Readiness as OK. Policy Readiness shows Warning. Resolution: Readiness status consistently shows Warning in this case. Note : Uncontrolled failover supported when source cluster is not reachable. —————————————————– T3168: Source Node Restriction Validation reports incorrectly when clusters have overlapping namesFor the case where the clusters being managed by Eyeglass have overlapping names (for example C8000 and C800DR), the Source Node Restriction Validation incorrectly reports that there is no igls-ignore hint on the Source Node Restriction pool when in fact the hint is provisioned. This results in a Warning state for this validation. Workaround: Policy Source Node Restriction is now correctly reported for clusters with overlapping names. —————————————————– Configuration ReplicationT2788 - Eyeglass Configuration Replication “Error retrieving cluster version”If the Eyeglass sca service is restarted while a cluster is unreachable, when the cluster comes back online the cluster version cannot be determined by Eyeglass resulting in Configuration Replication error blocking all jobs. Resolution: Cluster version can now be determined once the cluster comes back online. ———————————- T3360: Failed to Retrieve Inventory error when a node is downIn the event that one or more of the nodes in a cluster are down, this may result in a Failed to Retrieve Inventory alarm in Eyeglass blocking initial discovery as well as subsequent Configuration Replication tasks. Resolution: Node down on the cluster no longer blocks initial discovery or Configuration Replication. —————————————————– GeneralT2959 - Eyeglass Initial inventory does not check cluster reachabilityIf the Eyeglass sca service is started while a cluster is unreachable, initial Inventory will take a very long time as each REST API call has a 5 minute timeout. Also the Continuous Operations dashboard shows the cluster as Reachable. Resolution: Initial inventory finds cluster unreachable and therefore no Inventory actions taken against unreachable cluster so that Inventory time is not affected. Also Continuous Operations dashboard correctly shows the cluster as unreachable. ———————————- Known IssuesFailover2666/2723: Problems for Controlled Failover when Source becomes unreachable during failoverIn 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 deletedFor 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 listIf 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 limitRunning 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 hintThe 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 errorsZone 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 matchZone 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:
—————————————————– T477: No Policy Hot/Hot Validation Error for policy with no share/exportZone 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 errorsIn 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 ZoneFor the case where a SyncIQ Policy source path corresponds to a non-System Access Zone path (path is at or below the Access Zone path) but there is a share protected by that policy in the System Access Zone, the SyncIQ Policy incorrectly is evaluated for Zone Readiness in the System Access Zone. Workaround: None required. This policy can be ignored in the System Access Zone as in this configuration the System Access Zone cannot be failed over. —————————————————– T1712: Zone Readiness missing Zone when pool has no SmartConnect Zone - OneFS 7In 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 deploymentsIf Eyeglass is deployed on a Redhat or Centos operating system the Eyeglass Runbook Robot pre and post failover check for file system read/write by making an NFS mount does not work. Workaround: Disable the Runbook Robot mount step by setting to false following the instructions here: http://documentation.superna.net/eyeglass-isilon-edition/igls-administration/eyeglass-administration-guide#TOC-Runbook-Robot-Mount-Export-Enable-Disable Manually check read/write status of filesystem. —————————————————–– T1482: Zone Readiness SyncIQ Readiness not updated after Access Zone associated to a poolFor 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. —————————————————– T3151: Network Visualization window has UNKNOWN status for DFS and Policy Readiness when Policy is Failed OverFor the case where the DR Dashboard shows Policy or DFS Readiness for a policy to be “FAILED OVER”, the Network Visualization window incorrectly displays the readiness for this policy as “UNKNOWN”. Workaround: Confirm the DR Failover status for DFS or Policy Readiness in the DR Dashboard window. —————————————————– T3384: No SPN readiness warning when Active Directory Provider is in an error stateIn the event that the connection to an Active Directory provider is in an error state on the cluster, Eyeglass does not provide an SPN readiness warning. Workaround: None available. —————————————————– T3699: Quota sync fails if there are linked and unlinked quotas being failed overIf on the source there are linked quotas where some of the quotas have been unlinked, when the quotas are replicated during failover both the parent quota and unlinked quota are created which results in an error during replication due to a conflict. Workaround: None available. Prior to failover make sure there are no unlinked quotas related to a linked quota being failed over. After failover, if different limits are required - re-unlink on target and apply custom settings. —————————————————– T3735: SPN missing alarm incorrectly raised when cluster joined to multiple domainsIf a cluster is joined to multiple domains, an SPN missing alarm may be raised incorrectly stating that SPNs from one domain are missing from the other domain. Workaround: None available. Review all missing SPN alarms to verify that error is valid or not. —————————————————– T3742: No Policy Hostname Validation error if SyncIQ Policy Target Host is fully qualified and uses short name on target cluster pool that has a Superna Eyeglass mapping hint appliedIf the pool on the target cluster which contains the SmartConnect Zone which is configured on the source cluster as the SyncIQ policy target host is configured as “short” name instead of fully qualified name AND that pool has a Superna Eyeglass mapping hint defined instead of the required igls-ignore hint, Zone Readiness INCORRECTLY does not show an error. Workaround: Use fully qualified domain name for SyncIQ Policy target host and in the pool SmartConnect Zone name. —————————————————– T3848: SPNs not updated during failover for OneFS8 non-default groupnet AD providerFor the case where OneFS 8 is configured with multiple groupnet and different AD provider between groupnets, the SPN update during failover does not succeed for non-default groupnet AD providers. SPN are not deleted for source cluster and are not created for the target cluster. The failover log indicates success. This is due to a OneFS8 defect with multiple AD providers and isi commands. SPN delete / create for the AD provider defined in groupnet0 is successful. Workaround: Manually delete and create the SPN for the Smartconnect Zones that were moved from AD ADSI Edit interface. —————————————————– Configuration Replication1683: Export sync where source is 7.1.1.x and target 8.x.x.xDescription: 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 replicatedUpdated 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.xWith 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 deletedIn 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 JobEyeglass 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 targetAttempting 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 deselectedAfter 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 creationWhere 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 replicationEyeglass 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 JobWhen 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 windowWhen 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 quotaAfter 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 errorWhen 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 deletedFor 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 clustersFor 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 selectedFor 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 JobWhen 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 startedIf 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 resourceError 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 JobsWhen 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 deletedWhen you delete an Access Zone in OneFS, the following issues occur in Eyeglass:
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 EyeglassWhen 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.0For 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 ErrorThe 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 selectedIf 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 ClusterAn 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
IMPORTANT: You must enable DFS mode before enabling the Job to prevent creation of active shares on target cluster.
—————————————————– T593: Eyeglass errors for multiple exports with the same pathIf 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:
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 ReplicationYou may see Inventory errors after upgrading the Isilon cluster version or adding a cluster to be managed by Eyeglass which has a different OneFS version than clusters already managed due to wrong version of API being used to connect to the cluster. Workaround: Restart the Eyeglass sca service as per instructions here for sca service: http://documentation.superna.net/eyeglass-isilon-edition/Eyeglass-Isilon-Edition#TOC-Eyeglass-Processes —————————————————– T1851: Eyeglass Configuration Replication Jobs not removed when there is no SyncIQ privilege for the eyeglass service account If the eyeglass service account has the SyncIQ privilege removed the Eyeglass Jobs are not updated to removed even though the associated SyncIQ policy cannot be retrieved. The Jobs run successfully with the message “The job has no data to replicate; skipping it.” Workaround: eyeglass service account must have the SyncIQ privilege as documented in minimum permissions document here: http://documentation.superna.net/eyeglass-isilon-edition/tech-notes/isilon-cluster-user-minimum-privileges-for-eyeglass —————————————————– T2193 - Export max_file_size setting not replicated correctlyA 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. ———————————- T2482 - Eyeglass does not create alias for “short” SmartConnect ZonesDuring the Eyeglass Inventory process missing SPNs are detected and created. If a pool contains a SmartConnect Zone that is not fully qualified the related SPN is not created. For example: “prod” instead of “prod.example.com”. Workaround: Create “short” SPNs manually. Note: During Access Zone Failover this issue does not exist, SPN delete and add sequence works correctly for SmartConnect Zones that are not fully qualified. ———————————- T2757: Access Zone is not replicated from OneFS 8 to OneFS 7.2Access 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 SchedulesIf 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 clusterEyeglass Configuration Replication does not sync the Access Zone Authentication Provider to the target cluster. Workaround: Add Authentication Provider to the Access Zone manually. ————————————————— T3814: Incorrect Audit error for Configuration Replication with overlapping Access ZonesConfiguration Replication completes successfully for Job where configuration data (shares, exports, nfs alias) exist in multiple access zones, however audit may incorrectly report an error when in fact the properties and permissions are identical. This results in an associated Policy / DFS Readiness error: attention - no update, src and dst are equal - no update, src and dst are equal - no update, src and dst are equal - no update, src and dst are equal Workaround: Verify manually that properties and permissions for shares /exports/NFS alias with the audit error are in fact identical. Verify that Readiness warning is related to this error. ————————————————— T3629: Renamed Snapshot Schedule leaves original Snapshot Schedule on the targetAfter 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. ————————————————— Features1138: Eyeglass UI does not block configuration of duplicate remote logging serviceDescription: 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. —————————————————– 2218: SyncIQ Job Report link to RPO documentation is brokenSelecting 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 unreachableEyeglass 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 sensitiveCheck 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 DisabledPhone 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 stepsAfter configuring the Remote Log Consumer in Eyeglass, additional manual steps are required on the Eyeglass appliance to update syslog-ng.conf to enable the service. Workaround: Please refer to Eyeglass Tech Note Eyeglass Isilon Remote Logging Service Tech Note section “Setup Eyeglass remote logging manually for log Analysis”. —————————————————– T1515: Eyeglass Shell feature not functioning for RHEL and Centos deploymentsIf 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. ————————————————— T1962: Default Role incorrectly shows Delete optionEyeglass 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. ————————————————— T2863: DR Test Mode Error may leave Eyeglass Disaster Recovery Testing Job in disabled stateIf an error occurs in DR Test Mode, once the Error is recovered the Job might still be in Error state in the Job GUI. The Job GUI does not show whether the underlying Configuration Replication Job is disabled or enabled. If disabled it is blocked from running the Job again. Workaround: Enable the Job first and then run it. ————————————————— T3119: Access Zone Migration Preview does not always display Configuration informationThe 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. ————————————————— T3101, T3120: Superna Eyeglass DR Test Mode Enable/Disable Error when Eyeglass-DR-Testing SyncIQ Policy is runningWhen Superna Eyeglass DR Test Mode is enabled or disabled, Superna Eyeglass starts the Eyeglass-DR-Testing SyncIQ Job to complete a data sync. If the Eyeglass-DR-Testing SyncIQ Job is already running this result in an error during the Enable / Disable Workaround: Set Eyeglass-DR-Testing SyncIQ policy schedule to manual before attempting to Enable or Disable DR Test Mode. ————————————————— T3110: Quota Self Serve Portal bulk update error for linked quotasWhen linked quotas are being used, a bulk update for limits incorrectly attempts to update the linked entity resulting in the error “{ "code" : "AEC_BAD_REQUEST", "message" : "Cannot modify/save linked domains without unlinking: Invalid argument" } . Workaround: Update individual quotas rather than using the bulk quota update. ————————————————— T3170: Quota Requests History shows Status of Error for processed requests after failoverAfter 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. ————————————————— T3427: Quota Requests Auto Create fails when Quota path contains “%U, %L, %D or %Z” expansion path variablesQuota Request Auto Create feature does not recognize the expansion path variables and fails with path does not exist error. Workaround: Do not enable Auto Create Quota feature where expansion path variables are being used. Use per quota request approval for paths without expansion path variables. Use manual updates via OneFS for paths with expansion path variables. ————————————————— General924: Inventory View shows + beside component when there are no more childrenDescription: 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-refreshedDescription: 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 clearedAlarms 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 ViewTo see the Networking info for an Access Zone in the Inventory View:
Workaround: Enable Failover Readiness job. —————————————————– 2628: Job Definitions window does not sort properlyClick 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 truncatedThe 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 addressEmail 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 windowThe 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 informationFor 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 pageOpening 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 collapseThe 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 CentosEyeglass 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 DeploymentsThe 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 ———————————- Superna Eyeglass Known LimitationsKnown Limitations for Isilon OneFS 8.0.0.x with EyeglassT507 Cluster Report for OneFS 8.0 missing informationThe Eyeglass Cluster Configuration Report for OneFS 8.0 is missing following information:
Known Limitations for Eyeglass FailoverT939 Eyeglass Access Zone Replication Job in Error after failoverThe 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 failbackIt 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.1For 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 runningFor 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:
The first failover name cannot be <policy name>_mirror.
Workaround: Manual process on naming the convention above must be followed. Known Limitations for Eyeglass Configuration ReplicationMulti-Path ExportsT1359 Update NFS Multi-Path Export path(s) may cause transient Configuration Replication ErrorEyeglass 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 JobsExport 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 ErrorEyeglass 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 ErrorMultiple 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 errorIn OneFS 8 where there are Access Zones have identical paths, Eyeglass Access Zone Replication will fail with the following error from the Isilon cluster: AEC_CONFLICT “field” “path” “message” “access zone base path \*/ifs\* overlaps with base path \*/ifs/data/zone\* in Access Zone Use the force overlap option to override. In this case disable Eyeglass Configuration Replication Jobs for Access Zones and manually create the Access Zone on the target cluster. T1972 Snapshot schedule replicated with offsetSnapshot 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.
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 deletedAccess Zone Replication successfully creates and updates user mapping rules and also successfully deletes user mapping rules except when all user mapping rules are removed from the source. In the case where all user mapping rules are deleted from the source, the Access Zone configuration replication job will not delete all on the target - the user mapping rules remain on the target. T2241 Incorrect missing SPN alarm issued when Isilon cluster joined to multiple DomainsIn an environment where the Isilon cluster is joined to multiple Domains, the OneFS SPN check command for a specified domain returns list of SPNs from other domains and lists them as missing. In this case Eyeglass issues an SPN alarm for missing SPNs based on the list returned even if there are no missing SPNs in the domain specified in the check command. T2779 - Eyeglass Configuration Replication “Full Sync Mode” always updates when Default Settings on Source and Target cluster are not the sameIf 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:
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. Known Limitations for Eyeglass FeaturesT2350: Quota Self Serve Portal: Local Group Quotas not displayed when logged in with Local Group UserQuotas 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. Known Limitations for Eyeglass GeneralT2289 Backup Archive Job is not always displayed in the Running Jobs windowIn 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 NameWhen 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 failoverIf 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. |