WHAT’S NEW. This issue does not affect SmartConnect Zone rename during failover. When doing concurrent Access Zone or Pool Failover where the Access Zone or Pool have associated jobs in Eyeglass DFS mode the share renaming step may happen in parallel and depending on the OneFS release an PowerScale OneFS API defect may incorrectly handle the request causing the share rename to be in error. Readiness logic to determine whether 2 pools are mapped for Access Zone or Pool failover will map based on partial match instead of an exact match. Failover readiness SyncIQ File Pattern Validation which detects that SyncIQ policy has file patterns should be ERROR instead of WARNING as PowerScale OneFS Resync Prep function that prepares you for failback will fail when SyncIQ is configured this way. Please refer to the Eyeglass Admin Guide for published limits here. Workaround: Access Zone name and case must be identical between source and target for Directory Migration. compare_arrows Compare rate_review Write a Review. Shares and exports are replicated as expected. As of 2.5.6-20258 build OneFS 9.1 is supported. Eyeglass Backup Archive file cannot be downloaded from the Eyeglass web page if Eyeglass is deployed on a Redhat or Centos operating system. Workaround: None available. Instead of reporting Pool Readiness alarms per Pool they are reported against the Access Zone that is configured for Pool Failover. If a policy, dfs, zone or pool readiness alarm occurs multiple times, the Alarm time will not be updated with each occurrence. After a Quota Modification Request is submitted, the window does not close and remains in a loading state. Some versions of vmware vcenter HTML user interface have a known issue with OVA properties being read correctly post power on, leading to first boot issues. Phone home logging can now be found in the dedicated log /opt/superna/sca/logs/phonehome.log . 4) Copy and paste the following commands: T12034 Eyeglass appliance rediscover does not preserve Eyeglass Job state unless Configuration Replication has run, T16137 Anyrelease restore does not restore all Ransomware Defender and Easy Auditor settings, Support Removed in Eyeglass Release 2.5.6, New: T16949 DR Rehearsal Mode available for OneFS 9.0, 9.1, T15111 DR Rehearsal Enable incorrectly results in REHEARSAL_ERROR status when failover includes AUTOSKIPCONFIG type jobs, T9621, T14813: Unable to break lock for filenames/path with special characters, T15280 Web widgets: Embeddable Widgets functionality Deprecated, T15504 Threshold for SCA0075 Disk Space Consumption Alarm Increased, T5808: Inconsistent Zone Readiness Status between DR Dashboard and Eyeglass API, T7881, T7893: Missing Validations for SPN readiness, T11083 Restore from backup does not preserve failover scripts, T1712: Zone Readiness missing Zone when pool has no SmartConnect Zone - OneFS 7, T1716: Eyeglass Runbook Robot NFS mount not functioning for RHEL and Centos deployments, T1482: Zone Readiness SyncIQ Readiness not updated after Access Zone associated to a pool, T3742: No Policy Hostname Validation error if SyncIQ Policy Target Host is fully qualified and uses short name on target cluster pool that has a Superna Eyeglass mapping hint applied, T3848: SPNs not updated during failover for OneFS8 non-default groupnet AD provider, T4009: SPNs creation case sensitive to AD provider name, T4320: Access Zone not assigned to any Subnet Pools results in many Zone Readiness Errors, T4316: Runbook Robot Policy Job does not display SyncIQ Job Reports, T4857: Failed SmartConnect Zone Rename step is not displayed in Failover Log, T4878: Pool Failover - Non Runbook Robot SyncIQ policies can be mapped to Robot pool, T4968: Zone missing from DR Dashboard Zone Readiness tab if a SyncIQ Policy has a target host that cannot be resolved, T5092, T4490: Access Zone Pre and Post Failover Scripting Issues, T5473: Zone/Pool Readiness Pool Mapping Hint Matching Issue, T5961: Failover Log shows Incorrect Final Steps, T5897: Post Failover Inventory step may fail during multiple concurrent failovers, T5941: Pool Failover Failover Log Summary incorrectly displayed Client Redirection step not run, T5967: Failover where Quota Sync is disabled has extra lines in Failover Log, T5934: Access Zone Readiness shows OK for DFS only failed over Access Zone, T6289: SyncIQ policy with no shares or exports is associated with the System Access Zone for failover, T6311: Selecting the DR Failover Status link on the DR Assistant Summary page may result in an Error, T6402: Access Zone Failover Post Failover Inventory step runs multiple times, T6842: Zone Readiness: Zone does not display Failover Over state for Access Zones where custom SmartConnect Zone prefix is being used, T7184: Pool Readiness: Pool to SyncIQ Policy Mapping is not displayed in DR Dashboard until Readiness task is run, T8824: User Quota creation fails on failover for multiple disjointed AD Domain environment, T10363 Overlapping Access Zone Failover blocked for System Access Zone, T10912 Quota Sync fails for quotas where quota container property set to true, T14965 Failover readinessSyncIQ File Pattern Validation has WARNING state instead of ERROR, 1683: Export sync where source is 7.1.1.x and target 8.x.x.x, T2757: Access Zone is not replicated from OneFS 8 to OneFS 7.2, T2920: Access Zone Authentication Provider is not replicated to the target cluster, T3629: Renamed Snapshot Schedule leaves original Snapshot Schedule on the target, T1515: Eyeglass Shell feature not functioning for RHEL and Centos deployments, T3119: Access Zone Migration Preview does not always display Configuration information, T3170: Quota Requests History shows Status of Error for processed requests after failover, T4280: User Storage View may show all quotas instead of only the User Quotas, T4432: DR Test Mode action on multiple policies do not display in Running Jobs, T4968: SyncIQ Job Report Troubleshooting section missing information when report is generated on demand, T5173: Quota Modification Request window does not close after Submit, T6389: Built-In AD Groups cannot be used with the Cluster Storage Monitor Active Directory Managed Quota feature, T8716: Upgrade issues for Cluster Storage Monitor Quota or Data Recovery requests, T8834: Storage Monitor Report missing user information when friendly name cannot be resolved, T9561: Unlock my files incorrectly displays directories, T1514: Eyeglass Archive cannot be downloaded when Eyeglass is deployed on Redhat or Centos, T939 Eyeglass Access Zone Replication Job in Error after failover, T1785 Cannot set ignore flag on subnet pool after failback, T1359 Update NFS Multi-Path Export path(s) may cause transient Configuration Replication Error, T1743 Multiple export with same path and same client do not show Configuration Replication Error, T1847 OneFS 8 Overlapping Access Zone Replication has error, T1972 Snapshot schedule replicated with offset, T2046 Access Zone Replication limitation when all user mapping rules are deleted, T2241 Incorrect missing SPN alarm issued when PowerScale cluster joined to multiple Domains, T2780 Same host moved to different NFS Export Client list not updated on target. The initial and maintenance release notes contain similar information, but there are a few differences. Workaround: For assessing Pool Failover readiness open the DR Dashboard and select Pool Readiness. No workaround required. Do the release notes provide the information that you really need? Workaround: Manually remove the deleted export from the target using PowerScale OneFS. Workaround: Do not customize Eyeglass configuration replication Job and select share/export/quota that are outside the Job path. Phone home feature is changing and will be disabled . The cluster usage icon has  a quota share export tab that will be removed. Workaround : If cluster still added to Eyeglass using FQDN modify to be added using IP. 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. 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. Custom Quota Jobs do not need to be run manually, they are run automatically each time the customer Eyeglass configuration replication Job is run. Isilon Reviews by Dell EMC in Distributed File Systems and Object Storage. The failover log indicates success. Workaround: Determine the NFS Alias healt from the OneFS command line using isi command.. While the DR Assistant allows you to select a failover in the wrong direction (inactive -> active) it is blocked further along in the Failover Wizard due to no enabled policies. Workaround: None Required. Resolution: Smb3 Encryption Enabled setting for shares is now synced. Workaround: Clear the alarm manually from the Eyeglass UI. Workaround: Manually edit the Access Zone on the target cluster and add the required authentication providers. If an PowerScale node is unreachable when Eyeglass is searching for open files there is no error message for the unreachable PowerScale nodes. 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. Workaround: Deleted quota manually deleted on the target. I brought this up to the team during the Alpha release, with the argument of having multiple Isilon clusters in a single environment, and the lack of a specified SmartConnect zone would require all clusters being connected to, to have the same credentials. Eyeglass quota job includes quotas related to excluded SyncIQ directories. If an AD Group templates, if the AD group name has special characters in the AD group name the quotas will not be applied. Resolution: Access Zone configured for Pool failover now appears in Pool Readiness tab and functionality to configure Pool Failover is available. When you delete an Access Zone in OneFS, the following issues occur in Eyeglass: corresponding Eyeglass Zone Configuration Replication Job is not deleted. After restoring Eyeglass backup , the Eyeglass log files location is not properly set. To fix this, we removed some information that can be accessed in other product documents, such as the upgrade instructions. Resolution: UserGroupQuotas and ShareExportUsage reports have been deprecated. Workaround: Enter "zone id" for "failovertarget" when initiating pool failover. 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. Workaround: Use the About/Contact -> Backup to create a Backup Archive and then download to your local system to review logs. Workaround: Do not use unlock for directories. Archive is still created and available for download on completion. Workaround: The original SyncIQ policy schedule is captured in the failover log. Action was completed and the request can be seen in the Pending Requests window. Resolution: Config Only Migration job now only creates/updates/deletes based on the source access zone. 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. If the Delete option is selected the Default Role is not deleted. : Readiness now matched between DR Dashboard and Eyeglass API. Workaround: None Required. This validation should only be being assessed for Access Zone or Pool failover. Once run this way the correct java version should be available to igls app report command as well. Workaround: Create a file sharing object at or underneath the SyncIQ Policy path and in the Access Zone under which the SyncIQ Policy falls. PowerScale Info Hub for OneFS 9.0.0.0 documentation. Workaround: Verify presence of snapshot manually on target cluster, isi snapshot snapshots list | grep , Replacing SyncIQ Policy Name iwth your our SyncIQ Policy Name, isi snapshot snapshots list | grep policy1, 12345 SIQ-Failover-policy1-2020-05025_21-33-37 /ifs/data/policy1. If this Quota job is run manually it will delete all related quotas on the source (cluster A) leaving you without related quotas on source or target. Workaround: Create SmartConnect Zone for the pools associated with the Access Zone that you want to failover. When Rehearsal Mode is enabled for an Access which has DFS policies or enabled with multiple pools which also have DFS, the failover log summary shows an interim summary after data access steps and a final summary at end. The Info link should contain error details if available. Eyeglass API now can be used to retrieve DR readiness information - please refer to documentation. For additional information on readiness validations in Warning state please refer to our documentation, T15610 Policy Readiness Pool Mapping Validation alarm and email indicate Warning severity instead of Error, T15613 DR Rehearsal Readiness - no alarm or email when DR Rehearsal status changes from OK to Warning or Error, T15623 REST API - Pool Failover API does not support multiple pool selection, T15624 REST API - Failover API does not block controlled failover when source cluster unreachable, T15769 DNS Dual Delegation Validation does not work where NS Record does not resolve directly to an SSIP, T16154 DR Rehearsal mode has invalid readiness validation for Corrupt Failover Snapshots, T17477 DFS share suffix not applied for failover or configuration replication, T17428 REST API - Policy Readiness returns incorrect Access Zone, T17447 OneFS 9.0 and 9.1 Readiness Validation for Policy Source Nodes Restriction always shows INFO, T17522 Failover Scripting Engine SOURCE and TARGET variables expose password, 1683: Export sync where source  is 7.1.1.x and target 8.x.x.x. Workaround: None required - summary has required information. Once configured run the Eyeglass Configuration Replication Job to update DR Dashboard / DR Assistant. For the cases where an Access Zone is configured for Pool Failover and there are policies which are not mapped to pools the Un-Mapped Policy SmartConnect/IP Pool Status alarm and email incorrectly indicate that this is a Warning level issue. Workaround: Select the checkbox for the Disaster Recovery Testing job and then Select a bulk action / Enable/Disable to enable it. Workaround: Do not Run Now for Custom Job that has been Disabled. The failover log for an uncontrolled Access Zone failover will incorrectly report the status of the final failover readiness step as SUCCESS instead of error and will incorrectly summarize the Pool aliases on source after failover and Pool aliases on destination after failover at the end of the log. The Upgrading OneFS topic contains information about where you can find system requirements and applicable patches for the release, as well as the list of OneFS releases that can be upgraded to the documented release. 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. If PowerScale does not identify any missing SPNs Eyeglass Configuration Replication will not insert custom SPNs. More information is available here. There must be one failover snapshot on the target cluster per SyncIQ policy being failed over. Multiple exports with the same path are required to have different clients in order to be replicated as per PowerScale default behaviour. Different units of off set all result in a value greater than entered. Download PDF. Description: Syncing exports does not function between these releases. This will ensure that the login process can easily match the user. Workaround: Review shares/exports/quota paths manually to determine which configuration data will be migrated for the selected source path. 1) ssh to the eyeglass appliance and login with the admin account (default password 3y3gl4ss). Manually check read/write status of filesystem. Quota Request Management Icons:  Affects User Storage icon, Quota Request Management workflow, Cluster Storage Usage Icon quotas tab are. With OneFS 8 there is an entry in Zone Readiness with appropriate error. Workaround: To avoid this warning DNS Dual Delegation validation can be disabled. Message displayed says "No open session....". This is achieved by configuring the associated IP pool to be "ignored" during failover. When you create a new custom Eyeglass Job, an associated Zone replication Job is not created. Workaround: In 2.5.6 all new Eyeglass configuration replication jobs will be in unconfigured state. Selecting the DR Failover Status link on the DR Assistant may result in following error:  No policy data has been provided, cannot execute request. Example. Once the Access Zone is associated with the pool the Policy remains associated with the System Access Zone. Report will run successfully once cluster is reachable. Workaround: Do not use these variables in scripting. This export configuration is not supported for DR as it would not allow per policy failover and is an unsupported configuration for Eyeglass. IMPORTANT: You must enable DFS mode before enabling the Job to prevent creation of active shares on target cluster. Finally, we understand that cross-referencing two different types of release notes can be challenging, and that it might not always be clear which document contains the information you need. As of 2.5.6-20258 build OneFS 9.1 is supported. OpenSUSE 42.3 operating system: Upgrade on OpenSUSE 42.3 operating system will no longer be supported. INFO Raised alarm: MAJOR Access Zone Failover Job failed. Additional logging provided for AD SPN Delegation Validation. Workaround: To assist in recovery from this state please open a support case at support.superna.net . Workaround: Close and reopen the Failover History window to see updates. Overview Reviews Ratings Alternatives. If DR Test Mode Make Target Writeable/ Make Target Read-Only does not complete and is left in the Entering DR Testing or Exiting DR Testing state there is no way to revert or retry the operation. This may result in an AEC Duplicate Permission error from the PowerScale cluster or no error until duplicate permissions exceeds allowed space and an AEC Message Too Long error occurs. OneFS 6.5.5.18 Release Notes Published March 6, 2013. Click on column headings in Jobs window to sort listings does not sort properly and sometimes lists jobs outside of the category groupings. The Failover Scripting Engine SOURCE and TARGET enivironment variable information includes the password of the account used to connect from Eyeglass to PowerScale in plain text. In a Controlled Failover where requirement is that Source cluster is reachable, should the Source cluster become unreachable during the failover an error will occur on the failover job but it is possible that no failover log will be generated. When multiple failovers are initiated in parallel and running concurrently the Post Failover Inventory step may fail if the same step is running for one of the concurrent failovers. For example, information about previously released patches can help you to confirm whether or not a later release includes the fixes from a patch that you’ve installed on your cluster. Search. When a SyncIQ Job Report is generated from the Reports on Demand window, the Troubleshooting section may not be populated. Workaround: Expand the Inventory View tree for SMB and NFS to see which objects are contained in the Job. Zone Readiness error for an Access Zone that is not assigned to any Subnet Pool has multiple rows displayed in the DR Dashboard - 1 per Subnet Pool on the PowerScale Cluster. ** Inter-version capabilities: In the case of inter-version operation, the capabilities of the lower OneFS API version will be applied across both OneFS versions. The LiveOptics Isilon collector generates an excel output that includes the following Isilon information. If a directory is inadvertently "unlocked" it may disconnect clients or have other unexpected results. 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. Release Notes Update below sample files of Dell CSI Operator corresponding to Isilon/PowerScale with latest Patch release : CSI Driver for Powerscale v1.3.0.1 Note : Replace image "dellemc/csi-isilon:v1.3.0.000R" with "dellemc/csi-isilon:v1.3.0.100R" Documentation reference can be found, T15547 Failover Readiness Domain Mark Validation fails for path with spaces or special characters, Workaround: Manually confirm presence of domain mark by running command on PowerScale: isi_classic domain list . This URL is used to get configuration details about your Isilon cluster via OneFS API. 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. Isilon Gen 6 drastically reduces physical footprint and offers improved scalability, compute power, software optimization and protection against hardware failures. Workaround: Reset Eyeglass to pick up IP address changes for Jobs on the new active cluster. This is a display issue only - the mapping is successfully saved and displayed after the next readiness task has run.