Scalelogic Wiki - User contributions [en]

Scale Logic ZX ver.1.0 up31 ZFS Upgrade

2025-01-21T11:40:04Z

Ma-W: 1 revision

#REDIRECT [[File system upgrade]]

ISCSI connections

2025-01-21T11:40:04Z

Ma-W: 1 revision

#REDIRECT [[Active iSCSI connections]]

SMB connections

2025-01-21T11:40:04Z

Ma-W: 1 revision

#REDIRECT [[Active SMB user connections]]

Critical IO Errors

2025-01-21T11:40:04Z

2025-01-21T10:13:07Z

Ma-W:

<div>This feature is available only when the special devices group exists in the pool.</div><br/><div>Devices assigned to the special devices group are designated for storing specific data, including metadata, indirect blocks of user data, and deduplication tables. Additionally, devices in the special devices group can be configured to handle small file blocks that are not listed above by applying the small blocks policy.</div><div>The size of the small block refers to the size of a single block of data configured on the dataset. Maximum size of such blocks can be set for each dataset under the “Record size” option.</div><div>Deduplication tables can alternatively be placed in a separate group known as the deduplication group.</div><br/><div><span style="color:#ff0000">'''WARNING''': If the size of the small block is greater than or equal to the value of record size on the dataset, all the blocks will be offloaded to the special devices group.</span></div><br/><div>The small block size can be configured for the whole Pool or for each dataset separately. Options to choose range from 4 KiB to 16 MiB.</div><br/><div>Configuring a bigger size for the small block policy can be helpful in case the administrator expects the to have a substantial amount of small files that will require low access times separated from the bigger files. Using this option is recommended only if the administrator understands what kind of data will be stored in configured datasets and the maximum size of offloaded files is exactly known, to avoid accidental data offload and special devices congestion.</div><div></div><div></div>
[[Category:Help topics]]

Backup & Recovery destination server

2025-01-21T10:12:03Z

Ma-W: 1 revision

<div>Remote servers that are added as snapshot targets are called Destination servers. To add one, click the “Add server” button.</div><br/><div>[[File:Add server option.png|none|800px|Add server option.png]]</div><br/><div>You will be asked for the following information:
*'''IP address/domain''': provide IP address or a hostname associated with your Destination server.<br/>'''<u>Note</u>: In case the snapshot target is an HA cluster, it is highly recommended to use Virtual IP configured on a Pool. It allows the connection to be stable even after exporting the pool to the other node'''.
*'''Port''': 40000 is set by default. This value should not be changed, unless explicitly asked by the Support Team.
*'''Password''': to establish the connection, it is required to provide the administrator password to the remote server.
*'''Description''': This field is optional. Provide a short description of your server to identify it in the future.
</div><br/><div>[[File:Add server form.png|none|450px|Add server form.png]]</div><br/><div>Destination servers configured here will be available during the Destination configuration step of the Replication task wizard.</div><div>If you wish to remove the Destination server click the “Remove” button. '''Remember to remove all Backup tasks related to this server beforehand!'''</div><br/><div>[[File:Remove server option.png|none|800px|Remove server option.png]]</div><div></div>
[[Category:Help topics]]

Backup & Recovery Esx server

2025-01-21T10:12:03Z

Ma-W: 1 revision

<div>Snapshot feature can be integrated with VMware ESX/vSphere snapshots. To integrate a new VMware server with click on the “Add server” option.</div><br/>
[[File:V-center add server option.png|800px|V-center add server option.png]]
<div>You will be asked for the following information:
*'''IP address''': provide IP address or a hostname associated with your Destination server.
*'''Port''': 443 is set by default. This value should not be changed, unless explicitly asked by the Support Team.
*'''Username''': provide the username for the VMware user you wish to use during integration. It is recommended to use the root user for this purpose.
*'''Password''': to establish the connection, it is required to provide the password to the VMware user account provided in the previous step.
</div><br/>
[[File:Add VMware server form.png|450px|Add VMware server form.png]]
<div><br/>The integrated server will be visible in the table below. The user can browse through the configured datastores and Virtual Machines by going to the Options > Details.</div>
[[File:Details of WMware server.png|800px|Details of WMware server.png]]

[[File:VMware server details.png|450px|VMware server details.png]]
<div><br/>It is also possible to remove the server from integration by clicking the Remove option. <span style="color:#ff0000">'''Remember to remove all Backup tasks related to this server beforehand!'''</span></div>
[[File:Remove WMware server.png|800px|Remove WMware server.png]]

[[Category:Help topics]]

Critical system error response policy

2025-01-21T10:12:03Z

Ma-W: 1 revision

<div><span style="color:#ff0000">'''Important!'''</span> <span style="color:#ff0000">Please be aware that these settings are applicable only for a single node configuration or for a cluster configuration with the other node being unavailable.<br/>'''For cluster configuration with both nodes available the policy is set to immediate reboot in all cases'''.</span></div><br/><div>A system reboot may be necessary when a critical error is detected. The administrator may choose to handle different errors in a different manner.</div><br/><div>Possible critical errors are divided into three categories:
*'''ZFS pool I/O suspend''': errors from this group are raised in case an uncorrectable I/O failure is encountered during read/write operation to the Pool. The I/O operation is suspended and the system awaits a reboot.
*'''Kernel oops or bug''': kernel oops is defined as a deviation from the correct behavior of the Linux kernel that produces a certain error log. Such an error is not fatal to the system but may be dangerous to the system’s stability. Kernel oops often precedes a kernel panic, causing the system to immediately shutdown. Kernel bug refers to an internal error in the kernel code. Un-Kh errors put the system integrity at risk. It is highly recommended that a reboot is performed immediately to avoid unexpected failures.
*'''Out-of-memory error''': This error, abbreviated as OOM, refers to the state of the system where no additional memory can be allocated for use by programs or the operating system. It is necessary to free up or add memory to the system to recover the system operation. Once this error occurs the system enters an unresponsive state until the memory issue is solved. It is highly recommended to reboot the system at the first moment possible.
</div><br/><div>For each of the mentioned categories the following behavior patterns can be configured:
*'''Immediate''': system will reboot the machine immediately after the error occurs (the event will not be recorded in the event viewer).
*'''Automatic''': system will restart in 30 seconds from when the errors appear.
*'''Manual''': system will prompt for manual restart.
</div>
[[Category:Help topics]]

Backup & Recovery replication task

2025-01-21T10:12:03Z

Ma-W: 1 revision

__NOTOC__
== Backup & Recovery: Overview Tabs ==

#'''Tasks''': View the list of all tasks with their current statuses.
#'''Destination Servers''': View all added destination servers. Use the '''Add Server''' button to configure a new server outside of the Backup Task Wizard.
#'''vCenter/vSphere Servers''': View all added vCenter/vSphere servers. Use the '''Add Server''' button to configure a new server outside of the Backup Task Wizard.

For additional support or detailed guidance, refer to the article [[On- and Off-site Data Protection|On-_and_Off-site_Data_Protection]]
<div><br/></div>
== Backup & Recovery: Creating a Replication Task ==

To create a replication task, navigate to '''Backup & Recovery''' and click on the '''Add Replication Task''' button. This launches the Backup Task Wizard, which consists of the following steps:

=== Step 1: Source Configuration ===

#'''Resource Path''': Browse and select the ZVOLs or datasets to be backed up. Confirm your selection by clicking '''Apply'''.
#'''Retention Interval Plan''': Specify how often snapshots should be taken and how long they should be retained.
<div><br/></div>
=== Step 2: Destination Configuration ===

*If the '''Toggle Bar''' is disabled, no destination will be configured. Enable the toggle bar to activate '''Destination 1'''.
*The destination server can be either:
**'''Local Server''': The same machine as the source.
**'''Remote Server''': A different server. To configure a remote server:
**#Select '''Add New Server'''.
**#Provide the following details:
**#*'''IP Address/Domain'''
**#*'''Port''' (default: 40000)
**#*'''Password'''
**#*'''Description''' (optional)
**#After adding the server, select the appropriate '''Resource Path'''.

<span style="color:#ff0000">'''Note''': '''The resource path cannot have iSCSI targets attached (for ZVOLs) or shared datasets.'''</span>

*Specify the '''Retention Interval Plan''' for the destination.
*To configure additional destinations, click '''Add Another Destination'''.

For detailed explanations of these options, refer to the article [[On- and Off-site Data Protection|On-_and_Off-site_Data_Protection]].
<div><br/></div>
=== Step 3: vCenter/vSphere Server Integration ===

*Add a vCenter/vSphere server to enable consistent snapshots.

For detailed instructions, refer to the article [[On- and Off-site Data Protection|On-_and_Off-site_Data_Protection]].
<div><br/></div>
=== Step 4: Task Properties ===

#'''Task Description''': Create a custom description for the task.
#'''Enable MBuffer''': Buffer the data stream on the source and destination to prevent buffer underruns. Configure:
#*'''Buffer Size'''
#*'''Rate Limit'''
#'''Send Compressed Data''': Enable this option to transfer compressed data directly without decompression, which speeds up the process and reduces network bandwidth usage.
<div><br/></div>
=== Step 5: Summary ===

*Review a summary of the configured settings.
*Click '''Add''' to finalize the task.

[[Category:Help topics]]

Small blocks policy settings

2025-01-21T10:12:02Z

Ma-W: 1 revision

File system upgrade

2025-01-21T10:12:02Z

Ma-W: 1 revision

<div>After upgrading to a version with a newer ZFS filesystem, the following notification will be displayed upon first access:</div><br/>
<q>Zpools available for ZFS filesystem upgrade Upgrading Zpools to the latest ZFS file system is recommended. Although the file system upgrade is absolutely safe for your data and its integrity and will only take few minutes please be aware that this operation cannot be undone and accessing this zpool data will not be possible with older software versions. In order to upgrade a single Zpool, please use “Upgrade file system" from Zpool's option menu.</q>
<br/><div>Additionally, the zpool itself will display the following zpool status:</div><br/>
<q>Some supported features are not enabled on the pool. The pool can still be used but it is recommended to upgrade it in order to fully utilize all system features. Action: Upgrade the pool using "Upgrade file system" in pool options menu. Once this is done, the pool will no longer be accessible by software that does not support new features.</q>
<br/><div>As prompted, expand the zpool options and choose "Upgrade file system":</div>
[[File:Upgrade file system option.png]]
<br/><div>The following windows will appear. Type ‘upgrade’ and click the Upgrade button to proceed:</div>
[[File:Upgrade file system confirmation.png]]
<br/><div>Once completed, the system will notify you that the zpool has been updated successfully.</div>
[[Category:Help topics]]

IDs range conflict within the cluster

2025-01-21T10:12:02Z

Ma-W: 1 revision

<div>In a clustered environment connected to an Active Directory (AD) server, user IDs (UIDs) and group IDs (GIDs) must remain consistent across all nodes. However, using the autorid backend for mapping IDs can create problems during failover. When one node fails and another takes over, autorid may map user IDs differently, causing users to lose access to shared files and folders.</div><div>If the system detects that different ID ranges are assigned to the same AD domain across cluster nodes, it will display the warning: '''"ID range conflict within the cluster."'''</div>
== Steps to resolve the problem ==
<div>Follow these steps to resolve the issue and ensure consistent ID mappings across the cluster:</div>
#'''Identify the node with correct mapping''':<br/>Log in to the node where user access is working correctly and user IDs are mapped as expected.
#'''Change the ID mapping backend''':<br/>Update the ID mapping backend from autorid to rid+tdb. The rid+tdb backend assigns IDs based on the relative identifier (RID) from the AD, ensuring the same IDs are used across all cluster nodes, while also allowing for dynamic ID assignment through the tdb backend for greater flexibility. <u>'''Don't change the tdb backend ranges to keep the UID/GIDs ranges assigned to domains so far'''</u>.
#'''Synchronize settings across nodes''':<br/>After switching the backend, the ID settings from the updated node will automatically synchronize with the other node in the cluster.
#'''Verify and check configuration''':<br/>Check that users can still access their files and folders. Perform a failover test to confirm that permissions remain correct when a node takes over.

== Why use the rid+tdb backend? ==
<div>Switching to the rid+tdb backend provides a reliable and predictable way to map IDs across nodes, avoiding conflicts caused by the dynamic ID assignment of autorid. It is a proven solution for maintaining stable user ID mappings in clustered environments.</div>

Zpool wizard

2025-01-21T10:12:02Z

Ma-W: 1 revision

<div>A '''zpool''' is the foundational storage construct in ZFS. It serves as a logical storage pool that combines multiple physical storage devices (disks) into '''vdevs''' (virtual devices), which collectively form the unified zpool. From this zpool, ZFS creates and manages '''datasets''' (file systems) and '''zvols''' (block storage volumes).</div><br/><div>The zpool wizard is made up of the following steps:</div><br/><div>
<span style="font-size:larger">'''1. Add data group'''</span>

This section provides information about all storage devices connected to the storage server. To add the first Data Group to your Zpool, follow these steps:

#Select the desired disks from the list on the left.
#Choose the redundancy type.
#Click the "Add group" button.
</div><br/><div>The available redundancy options for groups are as follows:
*'''Single''': Each disk operates as an independent drive with no redundancy.
*'''Mirror''': All data written to one device in the mirror is automatically replicated to another device, ensuring data redundancy. A minimum of two disks is required to create a mirrored vdev.
**'''Mirror (Single Group)''': All selected disks will be combined into a single mirrored group.
**'''Mirror (Multiple Groups)''': The selected disks will be paired into multiple mirrored groups, each consisting of two disks.
*'''RAIDZ-1''': Allows for the failure of one disk per RAIDZ-1 group without losing data. A minimum of three disks is required for a RAIDZ-1 group.
*'''RAIDZ-2''': Allows for the failure of two disks per RAIDZ-2 group without losing data. A minimum of four disks is required for a RAIDZ-2 group.
*'''RAIDZ-3''': Allows for the failure of three disks per RAIDZ-3 group without losing data. A minimum of five disks is required for a RAIDZ-3 group.
</div><br/><div>To learn more vdev types, please refer to the following article: [[Redundancy in Disks Groups|Redundancy_in_Disks_Groups]]</div><br/>
<span style="font-size:larger">'''2. Add write log'''</span>
<div>This feature allows you to configure the write log function using a chosen redundancy level (either a single drive or a mirror). The write log utilizes a separate intent log (SLOG) device. A fast SSD/NVME should be used for this vdev.</div><br/><div>Key points to consider:
*If multiple log devices are specified, write operations are load-balanced between the devices.
*Log devices can be configured with redundancy by using mirrors to enhance fault tolerance.
*RAIDZ vdev types are not supported for the intent log.
</div><br/><div>This ensures efficient and reliable write operations while leveraging the selected redundancy level.</div><br/>
<span style="font-size:larger">'''3. Add read cache'''</span>
<div>A cache device is used to store frequently accessed storage pool data, providing an additional layer of caching between main memory and disk. These devices cannot be configured as mirrors or RAIDZ groups. A fast SSD/NVME should be used for this vdev.</div><br/><div>Key benefits and considerations:
*Cache devices are particularly useful for '''read-heavy workloads''' where the working dataset size exceeds the capacity of main memory.
*By utilizing cache devices, a larger portion of the working dataset can be served from low-latency storage, improving performance significantly.
*The greatest performance improvements are seen in workloads characterized by '''random reads''' of primarily static content.
</div><br/><div>Adding a read cache helps enhance performance and reduces latency for storage systems with high read demands.</div><br/>
<span style="font-size:larger">'''4. Add special devices group'''</span>
<div>Special devices are used to store specific types of data, such as metadata or small files, on dedicated storage devices separate from the main data pool. A fast SSD/NVME should be used for this vdev.</div><br/><div>Key features and benefits:
*Storing metadata on special devices improves performance for metadata-intensive operations, such as file lookups and directory traversals.
*Small files below a certain size threshold can also be stored on these devices, enhancing read and write speeds for such workloads.
*Special devices are particularly beneficial for environments with a large number of small files or high metadata activity.<div></div>
<div>Using special devices optimizes the overall performance of the ZFS pool by offloading critical metadata and small-file operations to faster storage.</div><br/>
<span style="font-size:larger">'''5. Add deduplication group'''</span>
<div>A deduplication group can be explicitly excluded from a special device group as a dedicated storage group used to hold deduplication tables. This allows the deduplication tables to be stored separately from the special device class.</div><br/><div>Key features and considerations:
*Storing deduplication tables in a dedicated group improves the efficiency of deduplication processes by isolating them from other metadata operations.
*This configuration provides flexibility in optimizing storage layout based on workload requirements.
*Using a deduplication group is particularly beneficial for systems with high deduplication demands, ensuring better performance and management.
</div><br/><div>This setup enhances deduplication performance while maintaining a clear separation of metadata and deduplication operations.</div><br/>
<span style="font-size:larger">'''6. Add spare disks'''</span>
<div>A spare disk is a special pseudo-vdev used to track available spare devices for a zpool.</div><br/><div>Using spare disks enhances the reliability of the storage pool by allowing seamless drive replacement and reducing the risk of data loss.</div><br/>
<span style="font-size:larger">'''7. Configuration'''</span>
<div>During this step, you can configure the Zpool by naming it and enabling additional features if required.</div><br/><div>Key configurations:
*'''Zpool Name''': Assign a unique and descriptive name to the Zpool for easy identification.
*'''Enable AutoTRIM''': If supported by your devices, enable the AutoTRIM feature to automatically reclaim unused space. AutoTRIM helps optimize the performance and lifespan of SSDs by informing them when blocks are no longer in use.
*'''Small blocks policy settings''' if a special device group has been configured in Step. When the small block size is set for the pool all datasets inherit this value by default. It can be changed for a particular dataset in its setting.
</div><br/><div>Proper configuration ensures that the Zpool is tailored to your needs and operates efficiently.</div><br/>
<span style="font-size:larger">'''8. Summary'''</span>
<div>This step provides a summary of the zpool configuration, detailing the arrangement of disk groups and their roles within the pool. Click ‘Add zpool’ to create a zpool.</div>
</div>
[[Category:Help topics]]

Backup & Recovery destination server

2025-01-20T12:04:40Z

Ma-W:

Backup & Recovery Esx server

2025-01-20T12:04:21Z

Ma-W:

Main Page

2024-12-20T08:45:29Z

Ma-W:

===== ''Release Notes:'' =====

{{
#tag:DynamicPageList|
category = Release Notes
ordermethod = categorysortkey
order = descending
count = 1
mode = none
}}
<div>[[Release Notes|All release notes »]]</div>

----

'''''Help topics:'''''

{| style="width: 100%"
|-
|
{{
#tag:DynamicPageList|
category = Help topics
count=50
ordermethod = categorysortkey
order = ascending
}}

|
{{
#tag:DynamicPageList|
category = Help topics
offset = 50
count= 50
ordermethod = categorysortkey
order = ascending
}}

| style="vertical-align: top" |
{{
#tag:DynamicPageList|
category = Help topics
offset = 100
count=50
ordermethod = categorysortkey
order = ascending
}}

|}

----

'''''ZFS and data storage articles:'''''

{| style="width: 100%"
|-
|
{{
#tag:DynamicPageList|
category = ZFS and data storage articles
count=60
ordermethod = categorysortkey
order = ascending
}}

|}

File:Ad-structure.png

2024-12-19T14:46:30Z

Ma-W: Ma-W uploaded a new version of "File:Ad-structure.png"

Redundancy in Disks Groups

2024-12-19T14:42:37Z

Ma-W: 1 revision

__NOTOC__

<br/><br/>Disk group redundancy refers to the ability of a zpool to maintain data integrity and availability in the event of disk failures. This is achieved through mirrored or RAID-Z configurations, which store multiple copies of data across different disks. When a disk fails or data corruption is detected, ZFS can use the redundant copies to repair or reconstruct the lost data, ensuring the system continues to operate without data loss.

It is important not to mix the types of data groups (vdevs) inside your storage zpool, as it might lead to potential issues, so it is strongly recommended to consistently use only one type of vdev.

== <br/>Data Group redundancy level: 2-way mirror (2 disks per group) ==

*The chances of suffering multiple disk failures increase with the number of mirror vdevs in the zpool.
*The 2-way mirror accepts a single disk failure in a given vdev.
*The 2-way mirrors can be used for mission critical applications, but it is recommended not to exceed 12 vdevs in a zpool (recommended up to 12 x 2 = 24 disks for mission-critical applications and 24 x 2 = 48 disks for non-mission critical applications in a zpool).
*'''Note''': as a rule, the zpool performance increases with the number of vdevs in the pool. For mission-critical applications and using more than 12 groups, It is recommended to use 3-way mirrors or RAID-Z2 or RAID-Z3.
*For mission critical applications it is not recommended to use HDDs bigger than 4TB.

== Data Group redundancy level: 3-way mirror (3 disks per group) ==

*The chances of suffering multiple disk failures increase with number of mirror vdevs in the zpool.
*The 3-way mirror accepts up to two disks failures in a given vdev.
*3-way mirrors can be used for mission critical applications, but it is recommended not to exceed vdevs in a zpool (recommended up to 16 x 3 = 48 disks for mission critical applications and 24 x 3 = 72 disks for non-mission critical applications in a zpool).
*'''Note''': the zpool performance increases with the number of vdevs in a zpool. For mission-critical applications, it is recommended to use RAID-Z3.
*For mission critical applications it is not recommended to use HDDs bigger than 10TB.

== Data Group redundancy level: 4-way mirror (4 disks per group) ==

*The chances of suffering multiple disk failures increase with number of mirror vdevs in the zpool.
*The 4-way mirror accepts up to three disks failures in a given vdev.
*The 4-way mirror is recommended for a Non-Shared HA Cluster that can be used for mission-critical applications.
*It is also recommended not to exceed 24 of 4-way mirror vdevs in a zpool as a single group damage results in the destruction of the entire zpool (recommended up to 24 x 4 = 96 disks for mission-critical applications in a zpool).
*'''Note''': as a rule, the zpool performance increases with the number of vdev in the pool.
*HDDs bigger than 16TB should be avoided for mission critical applications.

== Data Group redundancy level: RAIDZ-1 (3-8 disks in a group) ==

*The chances of suffering multiple disk failures increase with the number of disks in a RAID-Z1 vdev.
*RAID-Z1 accepts one disk failure in a given vdev.
*The RAID-Z1 can be used for non-mission critical applications and it is not recommended to exceed 8 disks in a vdev. HDDs bigger than 4TB should be avoided.
*It is also not recommended to exceed 8 RAID-Z1 vdevs in a zpool as a single group damage results in the destruction of entire zpool (recommended up to 8 x 8 = 64 disks for non-mission critical applications in a zpool).
*RAID-Z1 configuration is not possible in a Non-Shared HA Cluster configuration.
*'''Note''': the zpool performance is doubled with 2 x RAID-Z1 with 4 disks each comparing to a single RAID-Z1 vdev with 8 disks.

== <br/>Data Group redundancy level: RAIDZ-2 (4-24 disks per group) ==

*The chances of suffering multiple disk failures increase with the number of disks in the RAID-Z2 group.
*The RAID-Z2 accepts up to two disks failures in a given vdev.
*The RAID-Z2 can be used for mission-critical applications.
*It is not recommended to exceed 12 disks in a vdev for mission-critical and 24 disks for non-mission critical applications.
*It is also not recommended to exceed 16 of RAID-Z2 groups in a zpool as a single group damage results in the destruction of the entire zpool (recommended up to 16 x 12 = 192 disks for mission-critical applications and 16 x 24 = 384 disks for non-mission critical in a zpool). HDDs bigger than 16 TB should be avoided.
*If 3 disks failure in a vdev is required, it is recommended to use RAID-Z3.
*RAID-Z2 configuration is not possible in a Non-Shared HA Cluster configuration.
*'''Note''': the pool performance is doubled with 2 x RAID-Z2 with 6 disks each comparing to a single RAID-Z2 with 12 disks.

== <br/>Data Group redundancy level: RAIDZ-3 (5-48 disks per group) ==

*The chances of suffering multiple disk failures increase with the number of disks in the RAID-Z3 group.
*The RAID-Z3 accepts up to three disks failure in a given vdev.
*The RAID-Z3 can be used for mission-critical applications.
*It is not recommended to exceed 24 disks in a vdev for mission-critical and 48 disks for non- mission critical applications.
*It is also not recommended to exceed 24 of RAID-Z3 groups in a zpool as a single group damage results in the destruction of the entire zpool (recommended up to 24x 24 =576 disks for mission critical applications and 24x 48 = 1152 disks for non-mission critical applications in a zpool). HDDs bigger than 16TB should be avoided.
*RAID-Z3 configuration is not possible in a Non-Shared HA Cluster configuration.
*'''Note''': the zpool performance is doubled with 2 x RAID-Z3 with 12 disks each comparing to single RAID-Z3 vdev with 24 disks.

== Write Log redundancy level ==

*In both single nodes and HA clusters, it should be configured as a 2-way mirror.
*When choosing a disk model for the Write Log, make sure to take the endurance parameter into consideration. Selecting a disk classified by the manufacturer as write intensive is strongly recommended.
*When selecting a disk size for the write log, consider the potential amount of data that’ll be able to reach the server in three consecutive ZFS transactions, e.g. based on the network card bandwidth for the data transfer. If the transaction length is set to 5 seconds (default), the write log device should be able to accommodate the amount of data that can be transferred within three transaction groups, i.e. 15 seconds of writing. Using a larger disk does not make sense economically, while a smaller one can be a performance bottleneck during synchronous writes. '''Practically speaking, 100GB for a write log should be more than enough.'''

== Read Cache redundancy level ==

Read Cache disks can only be configured as single disks, but it is possible to configure any number of them. In an HA cluster, Read Cache can only be configured as local disks on both nodes on the cluster.

== Special devices and deduplication group redundancy level ==

In both single nodes and HA clusters, it should be configured as a 2-way mirror.

[[Category:ZFS and data storage articles]]

Scale Logic ZX ver.1.0 up31 Release Notes

2024-12-19T14:42:37Z

Ma-W: 1 revision

'''Release date: 2024-12-16'''

'''Build: 58473'''

{| class="cke_show_border cke_show_border cke_show_border"
|-
| __TOC__

|}

== New ==

=== The iSCSI Target visibility and access to data through specified VIPs. ===

=== Low-level console tools allow users to enable or disable the Transmit Packet Steering (XPS) mechanism for network interfaces (Hardware Configuration menu -> Tuning options -> Network interface options -> network interface -> XPS Transmit Packet Steering). ===

=== Proxmox Qemu Guest Agent now available for improved ZX VMs administration. ===

=== Support for SED functionality on Micron drives. ===

=== ATTO ExpressSAS 24Gb/s GT HBA Adapter driver (esas6hba, v1.00.0f1). ===

== Updated ==

=== Linux kernel (v5.15.167). ===

=== ZFS (v2.2.4). ===

=== LSI Storage Authority Software (v008.009.009.000, please note that email notifications in LSA will need to be reconfigured). ===

=== Mellanox ConnectX-4/5 Network Controller driver (native driver from linux kernel 5.15.167). ===

=== Broadcom BCM573xx and Broadcom BCM574xx controllers driver (bnxt_en, v1.10.3-230.2.52.0). ===

=== Intel 100GbE Network Controller driver (ice, v1.14.11). ===

=== Intel 10/40GbE Network Controller driver (i40e, v2.25.9). ===

=== Intel 10GbE Network Controller driver (ixgbe, v5.20.9). ===

=== Intel 1GbE Network Controller driver (igb, v5.16.9). ===

=== Marvell FastLinQ 41000 Network Controller driver (qede, v8.74.1.0). ===

=== Chelsio T4/t5 10 Gigabit Ethernet controller driver (cxgb4, v3.19.0.2). ===

=== Mellanox firmware update driver (mft, v4.28.0-92). ===

=== Broadcom HBA 9600-16e 12Gb Tri-Mode Storage Adapter driver (mpi3mr, v8.9.1.0.0). ===

=== Broadcom HBA Adapter driver (mpt3sas, v50.00.00.00). ===

=== Broadcom MegaRAID Adapter driver (megaraid_sas, v07.729.00.00). ===

=== ATTO ExpressSAS 12Gb/s HBA Adapter driver (esas4hba, v1.54.0f1). ===

=== ATTO ExpressSAS 12Gb/s GT HBA Adapter driver (esas5hba, v1.08.0f1). ===

=== ATTO Celerity 16Gb/32Gb Fibre Channel Adapter driver (celerity16fc, v2.09.0f1). ===

=== ATTO Celerity 8Gb Fibre Channel Adapter driver (celerity8fc, v2.26.0f1). ===

=== Areca RAID Adapter driver (arcmsr, v1.51.00.16). ===

=== Microsemi Adaptec SmartHBA and SmartRAID Adapter driver (smartpqi, v2.1.28-025). ===

=== S.M.A.R.T monitoring tool (smartmontools, v7.4). ===

== Fixed ==

=== SSL Medium Strength Cipher Suites Supported (SWEET32) vulnerability (CVE-2016-2183). ===

=== The product activation mechanism does not complete successfully on Proxmox virtual machines. ===

=== Cluster service failed to start in environments with zpool containing a very large number of disks. ===

=== VLANs from remote nodes are not listed correctly while configuring VIPs in the cluster. ===

=== Unexpected reboots occurred during ultra-heavy write operations. ===

== Important notes for ZX HA configuration ==

=== It is necessary to use sync always option for zvols and datasets in cluster  ===

=== It is strongly recommended not to use more than eight ping nodes ===

=== It is strongly recommended to configure each IP address in separate subnetwork ===

=== It is necessary to run Scrub scanner after failover action triggered by power failure (dirty system close) ===

=== It is strongly recommended to use UPS unit for each cluster node ===

=== It is necessary to use static discovery in all iSCSI initiators ===

=== It is strongly not recommended to change any settings when both nodes do not have the same ZX version, for example during software updating ===

=== It is necessary to use different Server names for cluster nodes ===

=== HA cluster does not work properly with Infiniband controllers ===

=== HA cluster does not work stable with ALB bonding mode ===

=== FC Target HA cluster does not support Persistant Reservation Synchronization and it cannot be used as a storage for Microsoft Hyper-V cluster. This problem will be solved in future releases. ===

=== When using certain Broadcom (previously LSI) SAS HBA controllers with SAS MPIO, Broadcom recommends to install specific firmware from Broadcom SAS vendor. ===
<p style="text-align: justify"><span class="toctext">    *Please consult Broadcom vendor for specific firmware that is suitable for your hardware setup.</span></p>
== Performance tuning ==

=== iSCSI Target with VMware ESX performance tuning ===

     In case of low iSCSI Target performance with VMware ESX, a few parameters need to be changed in VMware ESX iSCSI Initiator. Go to Storage Adapters -> iSCSI Software Adapter -> Advanced Options and the change the following settings:
<pre>
MaxOutstandingR2T change the default 1 to 8

FirstBurstLength change the default 262144 to 65536

MaxBurstLength change the default 262144 to 1048576

MaxRecvDataSegLen change the default 131072 to 1048576
</pre>
=== Write cache sync requests performance tuning ===

     Write cache sync requests (sync) set to “always” for zvol is the safest option and is set by default. However, it can cause write performance decreases since all operations are written and flushed directly to the persistent storage. In case of using sync=always, it is strongly recommended using mirrored write log devices (very fast random writes devices).<br/>     Sync=standard or sync=disabled zvol options provide huge performance improvement but the most recent (up to 5 seconds) cached data can be lost in case of a sudden power failure. Use this option only in environments equipped with UPS.<br/>     For NFS shares the Synchronous data record is enabled by default. This option causes performance to be worse, but data can be safely written. In order to improve the NFS performance you can use Asynchronous data record but in such case, it is strongly recommended to use UPS.

== Known issues ==

=== Browser recommendations ===

     It is strongly recommended to use Mozilla Firefox browser to navigate the system’s GUI. When using other browsers some slight problems with displaying content may occur.

=== Web browser’s cache ===

     After updating from previous versions, some problems with WebGUI content and navigation may occur. To resolve this problems, please clear Web browser cache.

=== System as a guest in virtual environments ===

     Hyper-V:<br/>     In case of installing the system as a Hyper-V guest please use the following settings:<br/>       - Number of virtual processors: 4<br/>       - Memory: Minimum 8GB<br/>       - Boot Disk: 20GB IDE Disk<br/>       - Add at least 6 virtual disk

The utilization of physical hard drives in virtual machines hosted by Hyper-V is not supported and may cause problems. The problem does not occur when utilizing virtual hard drives in virtual machines within a Hyper-V environment.

     VMware ESXi:<br/>     In case of installing the system as a VMware ESXi guest please use the following settings:<br/>       - Guest OS: Other 2.6.x Linux ( 64bit )<br/>       - Number of Cores: 4<br/>       - Memory: Minimum 8GB<br/>       - Network Adapter: VMXNET 3<br/>       - SCSI Controller Type: Paravirtual or LSI Logic SAS<br/>       - Boot Disk : 20GB Thick Provision Eager Zeroed<br/>       - Add at least 6 virtual disk<br/>       - Edit Settings->Options->Advanced-General->Configuration-> Add row: disk.EnableUUID : TRUE

=== Reclaim deleted blocks on thin-provisioned LUNs in various systems ===

     In case of deleting large amounts of data, reclaimed deleted blocks on thin-provisioned LUNs in Windows 2012 can significantly slow down system performance. If you predict frequent deletions of large amounts of data, we recommend turning off the automatic reclaim function in Windows 2012. This can be done by disabling the "file-delete notification" feature in the system registry. To do so, follow the steps below:<br/>       - start Registry Editor.<br/>       - locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem       <br/>       - double-click DisableDeleteNotification.<br/>       - in the Value data box, enter a value of 1, and then click OK.<br/> <br/>     In order to reclaim the free space in Windows 2012 please change the    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\DisableDeleteNotification key value back to 0 and use "Optimize" tool located in Disc Management->[disk]->Properties->Tools. As the operation can generate a very high load in the system, it is recommended to perform it after-hours.  <br/>In case of VMware ESXi, the automatic reclaim feature is disabled by default. To reclaim the space of deleted blocks on thin-provisioned LUNs, please use vmkfstools. For details, please refer to the VMware Knowledge Base:

For VMware ESXi 5.0: [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849 http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849]<br/>For VMware ESXi 5.5 and newer: [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513 https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513]<br/>For VMware ESXi 6.7 and newer: search in Internet for “Space Reclamation Requests from VMFS Datastores” and read vendor documentation.

In case of using Windows 2008 there is no possibility to reclaim the space released by deleted data of thin-provisioned LUNs.

=== Deduplication issues and recommendations ===

     Please be aware that deleting the zvol with deduplication enabled can generate a very high load in the system and lead to unstable behavior. It is strongly recommended to perform such operation only after-hours. To avoid this issue, please use (if possible) single zvol on zpools dedicated for deduplication and delete the zpool which includes the single zvol.<br/>   <br/>     To determine the amount of System RAM required for deduplication, use this formula:<br/> <br/>                                                                                                                    (Size of Zvol / Volume block size) * 320B / 0.75 / 0.25<br/> <br/>Where:<br/>320B - is the size of entry in DDT table<br/>0.75 - Percentage of RAM reservation for ARC (75%)<br/>0.25 - Percentage of DDT reservation in ARC (25%)<br/> <br/>     Example for 1TB data and 64KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 65536B) * 320B / 0.75 / 0.25 = 28633115306.67B<br/>                                                                                                                       28633115306.67B / 1024 / 1024 / 1024 = 26.67GB<br/> <br/>so for every extra 1TB of storage, system needs extra 26.67GB RAM.<br/><br/>     Example for 1TB data and 128KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 131072B) * 320B / 0.75 / 0.25 = 14316557653.33B<br/>                                                                                                                        14316557653.33B / 1024 / 1024 / 1024 = 13.33GB<br/> <br/>so for every extra 1TB of storage, system needs extra 13.33GB RAM.
<div><br/></div><div>     Example for 1TB data and 1MB Volume block size:</div><div><br/></div><div>                                                                                                      (1099511627776B / 1048576B) * 320B / 0.75 / 0.25 = 1789569706,66B</div><div>                                                                                                                        1789569706,66B / 1024 / 1024 / 1024 = 1.66GB</div><div> </div><div>     so for every extra 1TB of storage, system needs extra 1.66GB RAM.</div><div><br/></div>
<br/>'''IMPORTANT: '''The above calculations only apply to the worst case scenario, when data is completely unique and will not be deduplicated. For the deduplicable data, the need for RAM drastically decreases. If SSD based Read Cache is present, part of deduplication table will be moved to the SSD and deduplication will work with good performance using less RAM.

<br/>'''IMPORTANT: '''With SAN (iSCSI) it is CRITICAL to match User-File-System format block size with the zvol volume-block-size. A simple example is a Windows file system NTFS with default format block size 4k and zvol default volume-block-size is 128k. With defaults like this deduplication will mostly NOT match because files can be aligned in 32 (128/4) different positions on the pool. If the NTFS format is increased to 64k and the zvol default volume-block-size is 128k, deduplication match can fail only one time because a file can be aligned to 2 (128/64) different positions on the pool. Every next write will match already as both alignment options already exist on the pool. In order to achieve all files matching and efficient memory usage NTFS must use 64k format block size and the zvol volume-block-size must equal 64k. Another option is that the NTFS=32k and zvol=32k, but in this case the deduplication table will be twice as large. That is why the NTFS=64k and zvol=64k is the most efficient setting for deduplication.

'''IMPORTANT: '''With NAS (NFS, SMB/CIFs) deduplication matching works always due to the data blocks being aligned by ZFS natively.

'''IMPORTANT: '''De-duplication is working on the pool level in the pool-range. This is why zvol-Physical size cannot show de-duplication benefit. In order to prove that deduplication saved space run the scrub and notice the current physical data space on the pool reported by the scrub. Next copy of new data and run the scrub again. Now scrub will show new physical data space. Comparing the data size from storage client side with the data space growth from the scrub will give the deduplication advantage. The exact pool of the deduplication ratio can be found in LOGs in zfs.log.

=== Zvols configuration issues and recommendations ===

     It is strongly recommended to set the client file system block size same as the zvol volume block size. For example, when using 64k zvol volume block size, the Windows Allocation unit size of NTFS should be set to 64k.

=== Target number limit ===

    In case of more than 60 targets, GUI will not be displayed correctly. This issue will be fixed in the next releases.

=== Targets with the same name are not assigned correctly ===

    Having two or more targets with the same name but belonging to various Zpools, will cause that all targets with the same name will be assigned to one Zpool during the import process.

=== Installation on disks containing LVM metadata ===

     There is no possibility to install the system on disks containing LVM metadata. You will need to clear those disks before installation. To do so, use the “Remove ZFS data structures and disks partitions” function located in the Extended tools. To access this function, boot the system from a temporary media like a USB drive or DVD.

=== Import Zpool with broken write log ===

     There is no option to import Zpool with a broken write log disk using the system’s functions. This is why it is STRONGLY recommended to use mirrored disks for write logs. In case it is necessary to import Zpool with a broken write log, please contact technical support.

=== Replacing disks in data groups for larger ones can cause your storage license capacity to be exceeded ===

     In case of replacing damaged disks for larger ones, the size of the entire Zpool will increased. Make sure that the new size will not exceed your purchased storage license.

=== Periodically after some operations, the GUI needs to be manually refreshed ===

     After performing some operations, e.g. resilvering, the GUI will show outdated information. In this case refresh the web page manually by pressing F5 on your keyboard. This issue will be fixed in next releases.

=== Replacing disks in data groups for smaller ones can cause an error and make the disk disappear from the list of available disks ===

     Operation of replacing a disk in a data group for a smaller one will cause an error "zpool unknown error, exit code 255", and the disk will become unavailable. In order to reuse this disk, please use function "Remove ZFS data structures and disks partitions" located in the Extended tools on the Console screen.

=== It is strongly recommended to use 64KB or higher Volume block size ===

     Smaller than 64KB block sizes used with deduplication or read cache will cause very high memory consumption.

=== RAM recommendations for Read Cache ===

     To determine how much System RAM is required for Read Cache, use the following formula:

<br/> <br/>                                                                      RAM needed = (Size of Read Cache - reserved size and labels) * bytes reserved by l2hdr structure / Volume block size<br/> 

     For 8KB Volume block size and 1TB Read Cache:<br/><br/>                                                                           RAM needed = (1099511627776B - 4718592B) * 432B / 8192B = 57981809664B<br/>                                                                                                        57981809664B / 1024 / 1024 / 1024 = 54GB<br/> <br/>Where:<br/>1099511627776B - 1TB Read Cache<br/>4718592B - reserved size and labels<br/>432B - bytes reserved by l2hdr structure<br/>8192B - Volume block size<br/> <br/>                                                                                                  For 64KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 65536B = 7247726208B<br/>                                                                                                       7247726208B / 1024 / 1024 /1024 = 6.75GB<br/><br/><br/>                                                                                                  For 128KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 131072B = 3623863104B<br/>                                                                                                       3623863104B / 1024 / 1024 /1024 = 3.37GB

=== Multiple GUI disk operations may result in an inaccurate available disks list ===

     Multiple operations of adding and detaching disks from groups can cause that the next operation of detaching will fail, but the disk will be shown on a list of available disks. When trying to add this disk to one group it will fail with the following error "[zfslib-wrap-zpool-ZpoolCmdError-1] invalid vdev specification". In this case, detach this disk once again.

=== After removing disks from groups they may not be displayed on a list of available disks ===

     Sometimes after removing disks from groups, Spare/Read Cache/Write Log disks are displayed on a list of unassigned disks, but they are not on a list of available disks. In this case, click the rescan button located in the adding group form.

=== Reusing disks from an exported and deleted Zpool ===

     After deleting an exported Zpool, not all disks which were a part of a Zpool become immediately available. Before you can reuse disks, which were previously used as a Spare or a Read Cache, you must first clean them. Use “Remove ZFS data structures and disks partitions” function located in the “Extended tools”.

=== Negotiated speed of network interfaces may not display correctly ===

     For some network interfaces, the negotiated speed field may display an incorrect value in GUI and Console. This issue will be fixed in next releases.

=== Limited possibility to display a large number of elements by the GUI ===

     After creating multiple snapshots, clones or zvols some forms in GUI work very slow. If you need to create many snapshots, clones or zvols, it is strongly recommended to use CLI in order to perform operations on them.

=== Scale Logic VSS Hardware Provider system recommendations ===

     It is strongly recommended to use Windows Server 2012. On the other Windows systems, Scale Logic VSS Hardware Provider Configuration works unstable.

=== Exceeded quota for dataset does not allow to remove files ===

     Files located on datasets with exceeded quota cannot be removed. In this case, please resize quota and then remove unnecessary files.

=== Slow WebGUI with multiple datagroups ===

     Zpool with more than 20 datagroups causes that some forms on WebGUI work very slow. If you need to create many datagroups, it is strongly recommended to use CLI API.

=== Slow WebGUI with multiple datasets ===

     More than 25 datasets cause that WebGUI works slow.

=== ZFS Upgrade ===

     For Scale Logic ZX users, it is recommended to upgrade Zpools to the latest ZFS file system. Although the file system upgrade is absolutely safe for your data, and takes only few minutes, please be aware that this operation cannot be undone. In order to upgrade a single Zpool, please use "WebGUI -> Zpool options -> Upgrade file system" from Zpool's option menu.

=== Intel® Ethernet Controller XL710 Family ===

     In case of using Scale Logic ZX with Intel® Ethernet Controller XL710 Family, it is necessary to update firmware’s network controller to the version: f4.33.31377 a1.2 n4.42 e1932.

=== Motherboards with x2APIC technology ===

     In case of using a motherboard with x2APIC technology enabled, it is necessary to disable x2APIC in BIOS. Otherwise, problems with CPU cores will occur.

=== NFS FSIDs and Zpool name ===

     One of the factors that have been taken into account when NFS FSIDs are generated is Zpool name. It indicates that when Zpool name is changed, e.g. during export and import with different names, FSIDs for NFS Shares located on this Zpool will also be changed.

=== High Availability shared storage cluster does not work with Infiniband controllers ===

     Due to technical reasons the High Availability shared storage cluster does not work properly when using the Infiniband controllers for VIP interface configuration. This limitation will be removed in the future releases.

=== Disks with LVM data cannot be used with the created Zpool ===

     Attempt to create Zpool with drives that contain LVM data will fail with the following error:

''"cannot open 'lvm-pv-uuid-R25lTS-kcDc-eiAN-eAlf-ppgi-rAqu-Oxy1Si': no such device in /dev must be a full path or shorthand device name"''

In this case, if you want use those disks, please use “Remove ZFS data structures and disks partitions” function located in “Extended tools”.

=== Unexpected long failover time, especially with HA-Cluster with two or more pools ===

     Current failover mechanism procedure is moving pools in sequence. Since up27 release, up to 3 pools are supported in HA-cluster. If all pools are active on single node and failover needs to move all 3 pools, the failover may take longer than 60 seconds which is a default iSCSI timeout in Hyper-V Clusters. In some environments, under heavy load a problem with too long time of cluster resources switching may occur as well. If the switching time exceeds the iSCSI initiator timeout, it is strongly recommended to increase the timeout up to 600 seconds.

     '''In case of using Windows, to increase iSCSI initiator timeout, please perform following steps:'''

1. Run regedit tool and find: ''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\...\Parameters\MaxRequestHoldTime registry key''

2. Change value of the key from default 60 sec to 600 sec (decimal)

     '''In case of using VMware, to increase iSCSI initiator timeout, please perform following steps:'''

1. Select the host in the vSphere Web Client navigator

2. Go to Settings in the Manage tab

3. Under System, select Advanced System Settings

4. Choose the ''Misc.APDTimeout'' attribute and click the Edit icon

5. Change value from default 140 to 600 sec.

     '''In case of using XenServer, to increase iSCSI initiator timeout, please perform following steps:'''

A. For existing Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Detach and reattach SRs. This will update the new iSCSI timeout settings for the existing SRs.

B. For new Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Create the new SR. New and existing SRs will be updated with the new iSCSI timeout settings.

=== Activation may be lost after update ===

     In some environments, after update to up11 system may require re-activation. This issue will be removed in the future releases.

=== Bonding ALB, Round-Robin and Round-Robin with RDMA do not work in Hyper-V and VMware environments ===

     In case of using Scale Logic ZX as Hyper-V or VMware guest, bonding ALB, Round-Robin and Round-Robin with RDMA is not supported. Please use another type of bonding.

=== Continuous writing in VMware guest can cause that deleting VMware snapshot can take long time ===

     Using ODPS on zvol/dataset with VMware guest where many I/O operations are performed can cause that the process of deleting VMware snapshot can take long time. Please take this into consideration while you set up the scheduler for Off-site Data Protection Service task.

=== Enabling quota on dataset can cause file transfer interrupt ===

     Enabling quota functionality on a dataset can cause file transfer interrupt. Before using it in production environment, please enable quota on dataset, or make sure that no file transfers are active.

=== Nodes connected to the same AD server must have unique Server names ===

     If ZX nodes are connected to the same AD server, they cannot have the same Server names.

=== Share can not be named the same as Zpool ===

     In case of share with the same name as Pool connections problem will occur. Please use different names.

=== No persistent rules for network cards in virtual environment ===

     Changing settings of virtual network cards (delete, changing MAC, etc.) can cause unstable system behaviour. Please do not change settings on production system. This issue will be fixed in next releases.

=== Downgrade to up17 or earlier is not possible ===

     Starting from up18 bootable medium has always SW RAID structure. Attempt to come back to earlier version is impossible. If you need come back to earlier version, you must reinstall version again.

=== System cannot be installed on cciss based controllers ===

     This issue will be fixed in next releases.

=== Interrupt the process of adding second disk to SW RAID (bootable medium) can cause run system from disk with uncompleted data ===

     Performing operation like: reboot, shutdown, power off, etc. during mirroring data on new added disk can cause that system will be booted from new disk which has incomplete data. In this case, SW RAID function shows empty status and wrong number of RAID members. To resolve this issue, please plug off disk which has incomplete data, boot system, plug in disk and add it once again to SW RAID.

=== SAS-MPIO cannot be used with Cluster over Ethernet ===

     It is strongly not recommended to use Cluster over Ethernet with SAS-MPIO functionality. Such a configuration can lead to a very unstable cluster behavior.

=== On- & Off-site Data Protection backward compatibility problem ===

     In case of using On- & Off-site Data Protection functionality in up21 or earlier, it is strongly recommended to remove all backup tasks created by CLI API and re-create it using GUI.

=== Wrong state of storage devices in VMware after power cycle of both nodes in HA FC Target ===

     In FC Target HA environment, power cycle of both nodes simultaneously may lead to a situation when VMware is not able to restore proper state of the storage devices. In vSphere GUI LUNs are displayed as Error, Unknown or Normal,Degraded. Moving affected pools to another node and back to its native node should bring LUNs back to normal. A number two option is to restart the Failover in ZX’s GUI. Refresh vSphere’s Adapters and Devices tab afterwards.

=== Problem with maintenance in case of disk failure ===

     In case of disk failure, please remove the damaged disks from the system, before starting administrative work to replace the disk. The order of actions is important.

=== Separated mode after update from ZX up24 to ZX up25 ===

     In HA cluster environment after updating of one node from ZX up24 to ZX up25 the other node can fall into separated mode and the mirror path might indicate disconnected status. In such a case go to Failover Settings and in the Failover status section select Stop Failover on both nodes. Once this operation is finished select Start Failover.

=== Different Write Cache default setting for zvols in early beta versions of ZX up25 ===

     In the early beta versions of ZX up25 the default value of the Write Cache Log bias of zvols was set to “In Pool (Throughput)”. In the final release of ZX up25 the Log bias is set to “Write log device (Latency)”.<br/>Please note, that “In Pool (Throughput)” setting may cause a drop in performance in environments with a lot of random access workloads which is a common factor for a majority of production environments.

=== Target alias name is required while configuring HA FC Target in case of adding two or more ports to one FC group ===

     If we want to have more then one port in each FC group (in HA FC configuration) it is necessary to type in Target alias name for every port. Otherwise an error message “Target alias is already used” can show up while setting up remote port mapping for FC targets in (pool name) -> Fibre Channel -> Targets and initiators assigned to this zpool. This issue will be resolved in the future release.

=== New default value for qlini_mode parameter for FC kernel module qla2xxx_scst ===

     In order to configure FC Target, kernel module parameter qlini_mode should be set to “exclusive” (in some early beta versions of ZX up25 qlini_mode was set up to “enabled”). In order to verify the value of this parameter open ZX TUI and use CTRL+ALT+W key combination to launch Hardware configuration. Press "Yes" to acknowledge the initial warning message. Type in the password. Choose option: Kernel module parameters. Select qla2xxx_scst QLogic Fibre Channel HBA Driver and make sure the value of this parameter is set to “exclusive”.<br/><br/>Please note that in order to change this parameter Failover must be stopped first.

=== Very low performance of FIO/WT in case of mixed FIO/WT and FIO/WB zvol configurations over Fiber Channel ===

     In case of the mixed FIO/WT and FIO/WB zvol configurations over FC one can observe significantly decreased performance on FIO/WT.

=== More than one zvol with FIO/WB mode can cause instability of the Fiber Channel connection ===

     If there's more than one FIO/WB zvol or a FIO/WB zvol is coexisting with other types of zvols it can cause an instability of the FC connection with client machines. As a result client machines may unexpectedly lose FC connected resources.

=== In certain situations system page cache is not able to flush File I/O errors by itself and cache flushing has to be performed manually ===

     Under certain conditions (like overfilling zvol and then expanding its size) some File I/O errors may be held by the system page cache and it requires manual flushing (in GUI use Storage -> Rescan).

=== Updating nodes of the ZX cluster from up24 and earlier versions changes FC ports to target mode resulting in losing connection to a storage connected via FC initiator ===

     There is a significant difference in FC configurations in up24 and earlier versions. Those versions allowed the FC ports to be configured in initiator mode only, while later versions allow both target and initiator mode with target as default, so in case of using storage connected via FC initiator, FC port(s) must be manually corrected in GUI of the updated node.

=== Updating Metro Cluster node with NVMe disks as read cache from ZX up26 or earlier can cause the system to lose access to the NVMe disks ===

     The process of updating of Metro Cluster node from ZX up26 or earlier is changing NVME disk IDs. In consequence moving pool back to updated node is possible but the read cache is gone (ID mismatch). In order to bring read cache back to the pool we recommend to use console tools in the following way: press Ctrl+Alt+x -> “Remove ZFS data structures and disks partitions”, locate and select the missing NVMe disk and press OK to remove all ZFS metadata on the disk. After this operation click Rescan button in GUI -> Storage. The missing NVMe disk should now appear in Unassigned disks at the bottom of the page which allows to select that disk in pool’s Disk group’s tab. Open Disk group tab of the pool, press the Add group button and select Add read cache. The missing disk should now be available to select it as a read cache.

=== Synchronization of a large LDAP database can last for a long time (e.g. 10h for 380K users) and can be associated with high system load ===

     This problem will be solved in future releases.

=== Long time of a failover procedure in case of Xen client with iSCSI MPIO configuration ===

     In a scenario where Xen client is an iSCSI initiator in MPIO configuration, the power-off of one node starts the failover procedure that takes a very long time. Pool is finally moved successfully but there are many errors showing up in dmesg in meantime. In case of such an environment we recommend to add the following entry in the device section of the configuration file: /etc/multipath.conf:

'''no_path_retry queue'''

<br/>The structure of the device section should look as follows:
<pre>device {
vendor "SCST_FIO|SCST_BIO"
product "*"
path_selector "round-robin 0"
path_grouping_policy multibus
rr_min_rio 100
no_path_retry queue
}
</pre>
=== In case of large number of disks, zpool move can take a long time ===

     In certain environments in case of large number of disks (about 100 and more) the zpool move operation can take a long time.

=== Rolled back data are not properly refreshed both in Windows and Vmware systems ===

     Before using rollback operation on zvol please detach iSCSI or FC target, perform rollback operation and reattach target.

=== User gets deleted from share access list after changing its username on AD server ===

     If the AD user is assigned to a share and later the username is changed we should let ZX know about it. Using the "Synchronize and update shares configurations" operation on ZX leads to a situation where the changed user gets deleted from the share’s access list. The new username needs to be added to the share’s access list manually.

=== QLogic 32Gbit FC HBA is no longer supported ===

     Starting from ZX up29 we no longer support QLogic 32Gbit FC adapters.

=== Certain 16Gbit FC HBAs are no longer supported ===

     Starting from ZX up29 we no longer support certain 16Gbit FC adapters. If you are using a 16Gbit FC adapter based on the Qlogic chipset using the qla2xxx_scts driver, please refer to our online hardware compatibility list (HCL) to verify if that particular adapter is supported.

=== E-mail password cannot contain special non-ASCII characters ===

     The following special characters # : + cannot be used in a password used in an e-mail notification feature. They can break the authentication process.

=== LSA e-mail notifications does not work with SMTP servers requiring SSL/TLS authentication ===

     E-mail alert configuration in LSI Storage Authority Software does not work with SMTP servers which require SSL/TLS authentication

=== Moving IP address of the NFS share’s IP read only access list to read/write access list cannot be performed in one step ===

     If an IP address is already present on the NFS access list and you would like to move it to another access list, it has to be performed in two steps. First delete the IP address from the current list and apply the changes. Next edit the NFS share again and add the IP address to the other access list.

=== If the used space on zpool reaches more than 80%, the system may generate high load and become unstable ===

     If the used space on the zpool reaches more then 80%, the system is trying to utilize the available space to the maximum. As a result, the system load may increase, especially waiting I/O and cause its unstable work. Expanding the pool size space is recommended.

=== In certain situations WebGUI is not showing the current state of the system ===

     There are situations when the system is performing actions taking too long for the WebGUI to refresh the values in the web browser. In such a case the system is showing the old value taken directly from cache memory. We recommend using the F5 key to refresh the WebGUI.

=== An ongoing O&ODP process involving small zvol block size or dataset record size generate high load and render the system unstable ===

     O&ODP backup tasks involving small zvol block sizes as well as small dataset record sizes (4KB - 16KB) are known to generate very high load rendering the system unstable. We recommend using at least 64KB sizes for zvols and datasets.

=== Runtime UPS calibration in the client-server configuration unexpectedly shutdowns ZX ===

     In the client-server configuration of the UPS, the runtime UPS calibration process returns an improper value interpreted by ZX as being on battery. When it timeouts it shuts the system down.

=== Starting from up29 (including updating from previous version), system cannot boot up in UEFI mode if your boot medium is controlled by LSI SAS 9300 HBA with outdated firmware ===

     Make sure your LSI SAS 9300 HBA has the latest firmware installed. A quick workaround is changing the booting mode from UEFI to Legacy.

=== Bonded Mellanox network cards show negative values on the network usage chart ===

     This issue will be solved in the future release.

=== In case of hundreds of thousands of LDAP users system starts very slowly ===

     LDAP database is stored on the boot medium. If you have that large LDAP database we recommend using ultra fast NVMe disk for boot medium.

=== After update to ZX up29 write back cache on some hardware RAID volumes can be unintentionally disabled ===

     Starting from ZX up29 we disable write-back cache on all HDD disks by default, but we do not disable write-back cache on SSD drives and hardware RAID volumes. It can happen however that the write-back cache on some RAID volumes can be turned off. Hardware RAID volume performance can be heavily impacted by the lack of the write-back cache, so please make sure it's enabled after update. Open TUI and invoke Extended tools by pressing CTRL+ALT+X, then select Disk write-back cache settings.

=== Restarting or disconnecting JBOD with the write-back cache enabled on disks can lead to the data inconsistency ===

     If write-back cache is enabled on disks in JBOD then restarting or disconnecting JBOD can lead to data inconsistency. Starting from ZX up29 we disable write-back cache on HDD disks by default during bootup procedure. We do not disable write-back cache on SSD drives and hardware RAID volumes.

=== Snapshots are not displayed after a system reboot if there are more than a few thousands of snapshots ===

     In case there is a large number of snapshots (more than a few thousands) there might be a significant delay in listing them in WebGUI after a system reboot. Depending on how big the number of snapshots is, it may take a few minutes or up to several dozen minutes to populate the list in WebGUI.

=== It is not recommended to use the gzip-9 compression algorithm. ===

     In case of using the gzip-9 compression algorithm the system can behave unstable when copying the data to storage. It is possible to use this compression algorithm only in environments where very efficient processors are being used.

=== It is not recommended to use more than 500 zvols. ===

     In case of using more than 500 zvols in the system, the responsiveness of the Web-GUI may be low and the system may have problems with the import of zpools.

=== It is recommended to use Fibre Channel groups in Fibre Channel Target HA Cluster environments that use the Fibre Channel switches. ===

     In case of using the Fibre Channel switches in FC Target HA Cluster environments, it is recommended to use only Fibre Channel groups (using the Fibre Channel Public group it is not recommended).

=== Manual export and import of zpool in the system or deactivation of the Fibre Channel group without first suspending or turning off the virtual machines on the VMware ESXi side may cause loss of access to the data by VMware ESXi. ===

     Before a manual export and import of a zpool in the system or deactivation of the Fibre Channel group in Fibre Channel Target HA Cluster environment, you must suspend or turn off the virtual machines on the VMware ESXi side. Otherwise, the VMware ESXi may lose access to the data, and restarting it will be necessary.

=== In Fibre Channel Target HA Cluster environments the VMware ESXi 6.7 must be used instead of VMware ESXi 7.0. ===

     In case of using the VMware ESXi 7.0 in Fibre Channel Target HA Cluster environment, restarting one of the cluster nodes may cause the Fibre Channel paths to report a dead state.

=== Sometimes cluster nodes hang up during boot of Scale Logic ZX. ===

     In case one of the cluster nodes hangs up during Scale Logic ZX boot, it must be manually restarted.

=== Sometimes when using the ipmi hardware solutions, the cluster node may be restarted again by the ipmi watchdog ===

     In this case, it is recommended to wait 5 minutes before turning on the cluster node after it was turned off.

=== Sometimes restarting one of the cluster nodes may cause some disks to be missing in the zpool configuration. ===

     In this case, click the “Rescan storage” button on the WebGUI to solve this problem.

=== The Internet Connection Check functionality has been removed. ===

     In order to check the internet connection, try to get the date and time from the NTP server using the Web-GUI (System Settings -> System -> Time and date settings).

=== After upgrading the system to a newer version, the event viewer reported an error message: An unexpected system reboot occurred. ===

     After upgrading the system to a newer version, the event viewer reported an error message: "An unexpected system reboot occurred. Run the 'Scrub scanner' on all pools to check the system integrity. Analysis of logs and previous events can help to find the cause of this problem and prevent the issue in the future. For more information, refer to the help article.". This information should be ignored.

=== Low performance on remote disks in case of new installation of ZX up29r2. ===

     The source for this problem is the zfs_vdev_max_active parameter set to 1 on a new installation of ZX up29r2. To resolve this problem, please change the value of the zfs_vdev_max_active parameter from 1 to 1000 in TUI.  In order to change the zfs_vdev_max_active parameter to 1000 open ZX TUI and use CTRL+ALT+W keys combination to launch Hardware configuration. Press "Yes" to acknowledge the initial warning message. Type in the password. Choose option: Kernel module parameters. Select the zfs module, then the zfs_vdev_max_active parameter and change its value to 1000. This operation requires a restart of the ZX. This should be done by selecting the Reboot option in the TUI. 

=== In case of no local storage disks in any Non-Shared storage HA Cluster node, the remote disks mirroring path connection status shows incorrect state: Disconnected. ===

     According to assumptions, each cluster nodes in Non-Shared storage HA Cluster must have at least one local storage disk before creating the remote disk mirroring path connection.

=== In some environments in case of using RDMA for remote disks mirroring path, shutdown one of the cluster nodes may causes its restart instead of shutting down. ===

     In some environments in case of using RDMA for remote disks mirroring path, shutdown one of the cluster nodes may causes its restart instead of shutting down.

=== It is not recommended to use the ATTO Fibre Channel Target in the HA cluster environment. ===

     In case of using the ATTO Fibre Channel Target in a HA Cluster environment, after the power cycle of one of the cluster nodes, the fibre channel path reports a dead state. In order to restore the correct status of these fibre channel paths, the VMware server must be restarted.<br/><br/>     In case of using the ATTO Fibre Channel Target in a HA cluster environment, restarting the cluster node with both zpools imported in the system causes the second cluster node to be unexpectedly restarted.

<br/>Therefore, using the ATTO Fibre Channel Target in the HA cluster environment is not recommended.

=== The SED functionality configuration issues. ===

     The SED functionality in Scale Logic ZX enables to use the drives with verified SED configuration only.

=== The SED configuration tool available in TUI also lists devices that are not currently supported. ===

     The SED configuration tool available in TUI also lists devices that are not currently supported. To check if a given device is supported, see the HCL list available on the Scale Logic webpage.

=== Enabling the autotrim functionality in the zpools may cause drastic increase load or iowait in the system. ===

     In case of a drastic increase load or iowait in the system after enabling the autotrim functionality in the zpools, consider disabling it. It is recommended to run the "Trim" function manually on demand and at a convenient time (e.g. at a time when the system is working under less load).

=== The Mellanox ConnectX-3 network controller is no longer supported in RDMA mode due to its instability. ===

     In order to provide stable work with RDMA we recommend using the Mellanox ConnectX-4, ConnectX-5, or ConnectX-6.

=== The Network usage charts display incorrect data for an Active-Backup bonding with RDMA. ===

     The Network usage charts incorrectly display data for systems using the Active-Backup bonding with RDMA. The charts only reflect the usage of one network interface included in the Active-Backup bonding (the charts for the second network interface are not generated at all).

=== Duplicate entries appear in the Service Status tab in the WebGUI. ===

     In certain scenarios, the Service Status tab in the WebGUI shows duplicated instances of the same connection.

=== Restoring data backups from the macOS Time Machine application may not work correctly with older versions of the macOS system. ===

     In case of problems with restoring a copy of data from the Time Machine application, it is recommended to update the macOS system to a new version.

=== The Virtual Hard disks smaller than 1B are visible in the WebGUI. ===

     It’s possible to disable the virtual disks through IPMI settings. In Settings -> Media Redirection Settings -> VMedia Instance Settings:
<pre> Uncheck "Emulate SD Media as USB disk to Host" checkbox - it manages one of the virtual disks.
Set "Hard disk instances" to 0 in a combo box.
Set "Remote KVM Hard disk instances" to 0 in the combo box - settings of the combo box manage the second virtual disk.
</pre>
=== Unsupported configuration of VMware virtual machines (consisting of multiple disks) for data rollback from snapshots in On- & Off-site Data Protection. ===

     The VMware virtual machine data rollbacks from snapshots using the On- & Off-site Data Protection functionality are not supported when the virtual machines consist of multiple disks. The specific virtual machine configuration is incompatible with the restoration process.

=== Subdomain statuses in the User Management tab in the WebGUI are not updated. ===

     In case of unavailability of a given subdomain, information about its status will not be updated on the WebGUI (even by pressing the refresh button).

=== The problems with users and groups synchronization within the Active Directory one-way trusted configuration. ===

     In case of problems it’s recommended to use two-way trusted configuration.

=== Partial support for REST API v3. ===

     The REST API v3 is currently only partially supported. As a result, not all operations can be executed using this version of the REST API. For optimal utilization of the REST API, we highly recommend all customers to employ REST API v4.

=== SAS Multipath configuration is not supported in the Non-Shared Storage Cluster. ===

     In the case of the Non-Shared Storage Cluster, the SAS Multipath configuration is not supported at all. In this scenario, all the disks need to be connected through one path only. In the case of using the JBOD configuration with disks connected through a pair of SAS cables, one of them must be disconnected.

=== Username in LDAP database can’t be changed. ===

     To modify a username in the LDAP database, the administrator needs to delete the user account and creating a new one in the WebGUI.

=== The hard disk LED locating and disk faulty functionality do not work properly using the Broadcom HBA 9600 Storage Adapter. ===

     In the case of using the Broadcom HBA 9600 Storage Adapter the Hard disk LED locating and disk faulty functionality do not work.

=== The Broadcom HBA 9600 Storage Adapter may cause “Target allocation failed, error -6” error messages in dmesg. ===

     In the case of using the Broadcom HBA 9600 Storage Adapter,using the “Rescan” button in the storage tab in the WebGUI may results in the “Target allocation failed, error -6” error messages in dmesg.

=== The ARCHTTP tool, when in use, might erroneously redirect to another network interface. ===

     To avoid redirection to another network interface, it’s recommended to connect to the ARCHTTP tool using the primary network interface available in the Scale Logic ZX (the network interface is usually: eth0).

=== Resilver progress bar in the HA Non-shared Cluster Storage environment may show values over 100%. ===

     In the case of using the HA Non-Shared storage cluster with compression and deduplication enabled it has been observed that the resilver progress bar on the WebGUI may display values exceeding 100%.

=== Identification LED blinking does not work on NVMe drives in AMD-based servers. ===

     The Identification LED blinking on NVMe drives does not work on servers based on AMD processors. This problem will be solved in future releases.

=== The SED configuration tool available in TUI does not lists devices when using the Broadcom 9600 Storage Adapter. ===

     The SED configuration tool available in TUI does not lists devices when using the Broadcom 9600 Storage Adapter.

=== The TDB UID/GIDs mapping does not function properly. ===

     Workarounds:

*Single-Domain Environments:
**Use the "autorid" option in the "ID mapping backend" settings.
**Alternatively, use "rid+tdb":
**#Connect to the domain.
**#Navigate to the “Accessed domains” section.
**#Click the “Edit domain settings” button.
**#Set the UID/GID mapping to "rid" and define the Min ID and Max ID range (e.g., 2,000,000 to 2,999,999).

Note: The range 1,000,000 to 1,999,999 is reserved.

*Multi-Domain Environments:
**The "autorid" option is not supported. Use one of the following:
**#"rid+tdb"
**#"ad (with RFC2307 schema) + tdb"
**Steps for configuration:<ol style="margin-left: 40px;">
<ol style="margin-left: 80px;">
<li>Connect to the domains.</li>
<li>Navigate to the “Accessed domains” section.</li>
<li>Click the “Edit domain settings” button for each domain.</li>
<li>Set the UID/GIDs mapping to "rid" for all domains.</li>
<li>Define unique Min ID and Max ID ranges for each domain (e.g., 2,000,000 to 2,999,999 for the first domain, 3,000,000 to 3,999,999 for the second domain, etc.).</li>
</ol>

=== No Warning for Duplicate IP Addresses on Network Interfaces ===

     No warning or error message is displayed if two network interfaces are configured with the same IP address. This can lead to network conflicts or connectivity issues. Users must manually verify configurations to avoid duplicates.

=== No LED Management for aacraid Storage Controllers ===

     LED management is no longer supported for storage controllers using the aacraid driver, aligning with the manufacturer’s decision to discontinue these controllers. Users depending on LED indicators should explore alternative monitoring solutions or consider upgrading to supported hardware.

=== LED Blinking Not Functional on NVMe Drives in Supermicro X12 Servers ===

     On Supermicro X12 servers, LED blinking functionality for NVMe drives is not operational. Users should rely on alternative methods to identify and manage drives.

=== Web Server Settings in Maxview Storage Manager Not Preserved After Restart ===

     Changes made to the Web server settings in Maxview Storage Manager revert to default values after a server restart. Custom configurations are lost upon reboot. This issue will be addressed in a future release.

=== Unnecessary dmesg Entries After Zpool Export/Import ===

     Following a zpool export and import, dmesg may show entries such as "debugfs: Directory 'zdX' with parent 'block' already present!" While these entries do not affect functionality, they will be addressed in a future release.

=== Discontinued IDE Disk Support in Scale Logic ZX Up31 ===

     In Scale Logic ZX Up31, IDE disk support has been removed. Older servers or virtual machines relying on IDE disks may experience compatibility issues or failures. We recommend migrating to supported storage solutions to avoid disruptions. Future releases will not reintroduce IDE disk support.

=== Consider Reducing Volume Block Size to 16KB for High Random Workloads ===

     For workloads with high levels of random I/O, reducing the iSCSI volume block size to 16KB can improve performance. Users experiencing performance challenges with random workloads should consider this tuning option.

[[Category:Release Notes]]

Active Directory (AD) server authentication

2024-12-19T14:42:37Z

Ma-W: 1 revision

__NOTOC__
This functionality is available in '''User Management > Share users/groups > Authorization protocols'''.

<br/>To configure a connection to the existing Active Directory server:

#Navigate to the '''User Management '''section in the left menu.
#Go to the '''Share users/groups''' tab.
#Find the '''Active Directory (AD) server authentication''' block.
#Enable the '''Enable protocol''' option.

== AD server authentication status ==

*'''Connection''' - shows whether you are connected to an AD server or not.
*'''Users/groups list''' - shows when the lists of users and groups were last synchronized or if the synchronization is taking place at the moment.

Users and groups are synchronized with an Active Directory server every 2 hours. Synchronization can also be started manually by using the '''Synchronize''' button.

== AD server authentication settings ==

To connect to the existing AD server, fill in the following fields with credentials provided by the AD server administrator and click the '''Apply''' button.

*'''Realm'''
*'''Administrator name'''
*'''Password'''<br/>NOTE''': Password cannot contain:'''
**special characters such as ' " ` ^ & $ # ~ [ ] \ / | * : ? < >
**spaces
**less than 12 and more than 16 characters
*'''Organizational Unit (OU) - '''a direct path to the container where the Computer Organizational Unit is placed. The path must be entered starting from the primary container name within the domain structure. The container name set by default is '''Computers'''. If another container name is used instead, then '''Computers''' must be changed to the appropriate name. If the path to the container is nested, use a slash as the connector. In the screenshot below, the OU is in the '''Computers''' container that is nested in '''AllComputers > Marketing'''. In this example, the path to the OU is: '''AllComputers/Marketing/Computers'''<br/><br/>[[File:Ad-structure.png]]<br/><br/>NOTE''': Container name can't contain:'''
**special characters such as , + " \ < > ; = / #
**spaces

<div>'''The following reasons might prevent you from connecting to Active Directory:'''<br/></div>
#Difference in time between Active Directory Server - if the time difference is greater than 5 minutes, the connection is not possible.
#The method of authenticating trusted domains - the authentication has to be set to two-way trust. Otherwise, it is not possible to read users and groups from trusted domains.
#DNS configuration - for an Active Directory domain, it is not possible to use a round-robin mechanism in DNS. This is connected to the fact that only one IP address is authorized. In a moment when another IP is obtained from DNS, the connection is not possible.
#The '''server name''' is the same as the Computer Organizational Unit (OU) named in the Active Directory (AD) server. If the object with the same name exists and the user that you use to log in to the AD server does not have permission to access this file, the connection will fail. The solution is to delete the existing computer object from the AD server. The following information explains how to delete the OU file:
<ul style="margin-left: 80px;">
<li>Log on to the Domain Controller with the domain administrator account. Press Windows Logo + R, enter "dsa.msc" and press Enter.</li>
<li>In the "Active Directory Users and Computers" window, select the domain container in which the OU you are looking for is located.</li>
<li>Select the computer object and delete it.</li>
</ul>

::'''Note''': By default, any created Organizational Unit is protected from accidental deletion. To delete the OU, you need to clear the "Protect object from accidental deletion" checkbox, which you can find in the object properties in the "Object" tab. By deleting OU, you delete all nested objects that it contains as well.
:::<div><br/></div>

== Users and user groups management ==

'''Management mode:'''

*'''Scan single domain (default)''' - Using this function allows the user to obtain users and groups from the main domain only.

*'''Scan all trusted domains''' - Using this function allows the user to obtain users and groups from the main and trusted domains.

<br/>'''ID mapping backend:'''

*'''rid + tdb (default)''' - This option utilizes the rid backend for ID mapping to AD users. UID/GIDs range has to be entered manually The tdb backend is used when no other configuration is set. Recommended for large databases.Samba Wiki link for rid backend: [https://wiki.samba.org/index.php/Idmap_config_rid https://wiki.samba.org/index.php/Idmap_config_rid]
*'''ad (with RFC2307 schema) + tdb''' - Allows reading ID mappings from an AD server, provided that the uidNumber attributes for users and gidNumber attributes for groups were added in advance in the AD. This backend requires additional configuration of uidNumber and gidNumber on the AD server side. The tdb back end is used when no other configuration is set. Samba Wiki link for rid backend: [https://wiki.samba.org/index.php/Idmap_config_ad https://wiki.samba.org/index.php/Idmap_config_ad]
*'''autorid''' - This backend can be used if users are imported from a set of different domains. Automatically configures the range to be used for each domain. The only configuration needed is the range of UID/GIDs used for user/group mappings and the number of IDs per domain.Samba Wiki link for autorid backend: [https://wiki.samba.org/index.php/Idmap_config_autorid https://wiki.samba.org/index.php/Idmap_config_autorid]

== Troubleshooting ==

'''<span style="font-size:small">The TDB UID/GIDs mapping does not work properly.</span>'''

'''Single-Domain Environments'''
<div>It is recommended to use the "autorid" option in the "ID mapping backend" settings. Alternatively, you can use the "rid+tdb" option. If you choose "rid+tdb," set the UID/GIDs mapping to "rid" and define the Min ID and Max ID range (e.g., 2,000,000 to 2,999,999). The range 1,000,000 to 1,999,999 is reserved.</div><br/>
'''Multi-Domain Environments'''
<div>The "autorid" option cannot be used. Instead, use "rid+tdb" or "ad (with RFC2307 schema) + tdb." Ensure the UID/GIDs mapping is set to "rid" and define the Min ID and Max ID range for each domain (e.g., 2,000,000 to 2,999,999 for the first domain, 3,000,000 to 3,999,999 for the second domain, etc.).</div>
[[Category:Help topics]]

SNMP settings

2024-12-19T14:42:37Z

Ma-W: 1 revision

This function enables you to configure access over the '''SNMP''' protocol in versions 2 or 3.

With SNMP enabled, you receive a wealth of information (CPU usage, system load, memory info, ethernet traffic, running processes).<br/>System location and system contact are only for your information.  For example, when you connect from an SNMP client, you will see your location and name.

SNMP, version 3 has an encrypted transmission feature as well as authentication by username and password.<br/>SNMP, version 2 does not have encrypted transmission, and authentication is done only via the community string.

The community string you set can contain up to 20 characters, while the password needs to have at least 8 characters.

Links to SNMP clients:

*<span style="font-size:larger">[http://www.muonics.com http://www.muonics.com]</span>
*<span style="font-size:larger">[http://www.mg-soft.com http://www.mg-soft.com]</span>
*<span style="font-size:larger">[http://www.manageengine.com http://www.manageengine.com]</span>

{{Note|
Our storage system supports the SNMP protocol in MIB-II standard.  List of MIBs:

*- mib-2.host

*- mib-2.ip

*- mib-2.tcp

*- mib-2.udp

*- mib-2.interfaces

*- mib-2.at

*- system
}}

ZX offers additional SNMP values to monitor Pool and ZFS attributes.<br/>It is necessary to query specific OIDs in order to receive those attributes.

For basic ZFS parameters, NYMNETWORKS-MIB mib is included:

*to version v.1.0 up29r4  [[:Media:NYMNETWORKS-MIB.txt|NYMNETWORKS-MIB.txt]]
*from version v.1.0 up30 [[:Media:NYMNETWORKS-MIB-up30.txt|NYMNETWORKS-MIB.txt]]

<br/>'''SNMP v2:''' snmpwalk -v 2c -m NYMNETWORKS-MIB -c community 192.168.251.79 .1.3.6.1.4.1.25359.1<br/>'''SNMP v3:''' snmpwalk -v3 -l authPriv -u nagios -a MD5 -x DES -A 12345678 -X 12345678 192.168.150.70

<br/>NYMNETWORKS-MIB::zfsFilesystemName.1 = STRING: "Pool-0"<br/>NYMNETWORKS-MIB::zfsFilesystemName.2 = STRING: "Pool-1"<br/>NYMNETWORKS-MIB::zfsFilesystemAvailableKB.1 = Gauge32: 15861464<br/>NYMNETWORKS-MIB::zfsFilesystemAvailableKB.2 = Gauge32: 15861672<br/>NYMNETWORKS-MIB::zfsFilesystemUsedKB.1 = Gauge32: 4327720<br/>NYMNETWORKS-MIB::zfsFilesystemUsedKB.2 = Gauge32: 4327512<br/>NYMNETWORKS-MIB::zfsPoolHealth.1 = INTEGER: online(1)<br/>NYMNETWORKS-MIB::zfsPoolHealth.2 = INTEGER: online(1)<br/>NYMNETWORKS-MIB::zfsFilesystemSizeKB.1 = Wrong Type (should be INTEGER): Gauge32: 20189184<br/>NYMNETWORKS-MIB::zfsFilesystemSizeKB.2 = Wrong Type (should be INTEGER): Gauge32: 20189184<br/>NYMNETWORKS-MIB::zfsFilesystemAvailableMB.1 = Gauge32: 15489<br/>NYMNETWORKS-MIB::zfsFilesystemAvailableMB.2 = Gauge32: 15489<br/>NYMNETWORKS-MIB::zfsFilesystemUsedMB.1 = Gauge32: 4226<br/>NYMNETWORKS-MIB::zfsFilesystemUsedMB.2 = Gauge32: 4226<br/>NYMNETWORKS-MIB::zfsFilesystemSizeMB.1 = Gauge32: 19716<br/>NYMNETWORKS-MIB::zfsFilesystemSizeMB.2 = Gauge32: 19716<br/>NYMNETWORKS-MIB::zfsARCSizeKB.0 = Gauge32: 61086<br/>NYMNETWORKS-MIB::zfsARCMetadataSizeKB.0 = Gauge32: 9278<br/>NYMNETWORKS-MIB::zfsARCDataSizeKB.0 = Gauge32: 51808<br/>NYMNETWORKS-MIB::zfsARCHits.0 = Counter32: 229308<br/>NYMNETWORKS-MIB::zfsARCMisses.0 = Counter32: 41260<br/>NYMNETWORKS-MIB::zfsARCTargetSize.0 = Gauge32: 64287<br/>NYMNETWORKS-MIB::zfsARCMru.0 = Gauge32: 59529<br/>NYMNETWORKS-MIB::zfsL2ARCHits.0 = Counter32: 0<br/>NYMNETWORKS-MIB::zfsL2ARCMisses.0 = Counter32: 0<br/>NYMNETWORKS-MIB::zfsL2ARCReads.0 = Counter32: 0<br/>NYMNETWORKS-MIB::zfsL2ARCWrites.0 = Counter32: 0

Additional information, like compression ratio, deduplication ratio, available space (in bytes), age (in seconds) of latest snapshot on volume,<br/>can be obtained with standard NET-SNMP-EXTEND-MIB:

'''Examples:'''<br/><br/>NET-SNMP-EXTEND-MIB::nsExtendOutputFull."deduplication" = STRING:

"deduplication Pool-0 1.00"<br/><br/>NET-SNMP-EXTEND-MIB::nsExtendOutputFull."compression" = STRING:

"compression Pool-0/vol00 1.01<br/>compression Pool-0/clone-vol00 1.00"

NET-SNMP-EXTEND-MIB::nsExtendOutputFull."volumes_list" = STRING:<br/><br/>"available Pool-0/vol00 11981377536<br/>available Pool-0/clone-vol00 11981377536"

NET-SNMP-EXTEND-MIB::nsExtendOutputFull."snapshots_age" = STRING:<br/><br/>"snapshot_age Pool-0/vol00 3<br/>snapshot_age Pool-0/vol01 371"

'''Untranslated OIDs:'''<br/><br/>root@p-GA-880GM-USB3:/home/p# snmpwalk -v2c -c public 192.168.0.80  1.3.6.1.4.1.8072.1.3.2.3<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.1.11.99.111.109.112.114.101.115.115.105.111.110 = STRING: "compression Pool-0/vol00 1.01"<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.1.12.115.110.97.112.115.104.111.116.95.97.103.101 = STRING: "snapshot_age Pool-0/vol00 3"<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.1.12.118.111.108.117.109.101.115.95.108.105.115.116 = STRING: "available Pool-0/vol00 11981377536"<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.1.13.100.101.100.117.112.108.105.99.97.116.105.111.110 = STRING: "deduplication Pool-0 1.00"<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.2.11.99.111.109.112.114.101.115.115.105.111.110 = STRING: "compression Pool-0/vol00 1.01<br/>compression Pool-0/clone-vol00 1.00"<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.2.12.115.110.97.112.115.104.111.116.95.97.103.101 = STRING: "snapshot_age Pool-0/vol00 3<br/>snapshot_age Pool-0/vol01 371"<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.2.12.118.111.108.117.109.101.115.95.108.105.115.116 = STRING: "available Pool-0/vol00 11981377536<br/>available Pool-0/clone-vol00 11981377536"<br/>iso.3.6.1.4.1.8072.1.3.2.3.1.2.13.100.101.100.117.112.108.105.99.97.116.105.111.110 = STRING: "deduplication Pool-0 1.00"

[[Category:Help topics]]

2023-12-04T09:36:47Z

Ma-W:

Backup & recovery tasks consist of:

*source - dataset or zvol with the data we want to back up
*source retention plan - schedule plan that states how often snapshots of a resource will be made and how long they will be kept; the shortest interval also manages when and how often the created snapshots will be sent to the destination
*destination - a dataset or zvol where we want to keep the backup data; when you choose the dataset as a source in destination only datasets will be available, backups can only be made from a dataset to datasets and a from zvol to zvols
*destination retention plan - schedule plan that states in which intervals the received backup snapshots should be kept and for how long
*VMware VSphere integration - if we have a datastore created on a source resource before the snapshot of source is made, Vsphere makes a snapshot of every virtual machine on the datastore, so that the data on the datastore will stay consistent (on virtual machines for this snapshot)
*task description - your own task description
*mbuffer - buffers data stream on source and destination to prevent buffer underruns and, if used correctly, to speed up the whole backup process
*rate limit - allows you to specify the maximum data transfer rate or bandwidth that the backup process can consume

Tasks can be:

*created without destination - it allows you to create local snapshots creation routine
*created with local destination - destination can be some other resource on the same or different pool
*created with remote destination - destination servers can be added in the “Destination servers” tab, but also in a wizard
*disabled/enabled - you can stop creating and sending snapshots to destination if required

[[Category:Help topics]]

Storage performance test tool

2023-07-05T13:20:52Z

Ma-W:

=== General information ===

The storage performance test tool allows you to test speed of raw disks or zvols. The tool is available via TUI (Text-based User Interface). To access the tool, perform the following steps:

#While in TUI, press '''Ctrl'''+'''Alt'''+'''T'''.
#Select '''Add-ons''' from the menu.
#Select '''Storage performance test''' from the list.

You are able to select either a raw device test or zvol device test. Also, you can view test results.Once the test type is selected, you will be asked to select a device to be tested. After performing this operation, a test profile has to be selected. The following types can be chosen:

*ran_write (blocksize 512B)
*ran_read (blocksize 512B)
*seq_write (blocksize 1MB)
*seq_read (blocksize 1MB) 
<div><div>Every random test takes 100 seconds and sequential test takes 150 seconds. Testing progress is shown while running the test. To interrupt the test, press the Ctrl+\ keyboard shortcuts. Test results are available from tool or in logs downloaded from the GUI.</div><div><br/></div>
=== Raw device test ===

This test allows you to choose disks that are not assigned to zpool. 

=== Zvol device test ===
</div><div>This test allows you to choose zvols. To ensure data safety on zvols in zpool, zvol name must contain: '''data_DESTRUCTIVE_benchmark_test_ONLY.''' Otherwise, it won’t be listed under the '''Zvol device selection''' list. Note that you can overwrite data on this zvol using ran_write or seq_write profile. Once a write profile is selected, you will need to confirm that you understand the risk of using such profiles.</div><div><br/></div>
=== Test results viewer ===
<div>Here you can view the results or remove them one by one. Test results are also available in logs downloaded from GUI in the “TEST_RESULTS” folder.</div><div><br/></div><div><br/></div><div><br/></div>
[[Category:ZFS and data storage articles]]

Scale Logic ZX ver.1.0 up29r4 Release Notes

2023-06-01T09:26:29Z

Ma-W: 1 revision

'''Release date: 2023-03-20'''

'''Build: 50996'''

{| class="cke_show_border cke_show_border"
|-
| __TOC__

|}

== New ==

=== Restart remote disks mirroring path connection available in TUI ===

== Updated ==

=== Driver for Areca RAID controllers (arcmsr, v1.50.00.12) ===

=== Areca ArcHTTP tool v2.7.0 ===

== Fixed ==

=== (SU 90848): Stability issue with RDMA solution using bonded Mellanox network controllers ===

=== (SU 90855): After one power cycle of the cluster nodes in the Advanced Metro HA Cluster, some disks might become unavailable in the system ===

=== (SU 90856): Problem with empty diagnostic charts on WebGUI ===

=== (SU 90859): The process of listing all disks with self-encryption was disrupted due to the inability to read SED data from particular drives ===

=== SNMP agent returned invalid values ===

=== Unrealistic values on network usage charts during software update ===

== Important notes for ZX HA configuration ==

=== It is necessary to use sync always option for zvols and datasets in cluster  ===

=== It is strongly recommended not to use more than eight ping nodes ===

=== It is strongly recommended to configure each IP address in separate subnetwork ===

=== It is necessary to run Scrub scanner after failover action triggered by power failure (dirty system close) ===

=== It is strongly recommended to use UPS unit for each cluster node ===

=== It is necessary to use static discovery in all iSCSI initiators ===

=== It is strongly not recommended to change any settings when both nodes do not have the same ZX version, for example during software updating ===

=== It is necessary to use different Server names for cluster nodes ===

=== HA cluster does not work properly with Infiniband controllers ===

=== HA cluster does not work stable with ALB bonding mode ===

=== FC Target HA cluster does not support Persistant Reservation Synchronization and it cannot be used as a storage for Microsoft Hyper-V cluster. This problem will be solved in future releases. ===

=== When using certain Broadcom (previously LSI) SAS HBA controllers with SAS MPIO, Broadcom recommends to install specific firmware from Broadcom SAS vendor. ===
<p style="text-align: justify"><span class="toctext">    *Please consult Broadcom vendor for specific firmware that is suitable for your hardware setup.</span></p>
== Performance tuning ==

=== iSCSI Target with VMware ESX performance tuning ===

     In case of low iSCSI Target performance with VMware ESX, a few parameters need to be changed in VMware ESX iSCSI Initiator. Go to Storage Adapters -> iSCSI Software Adapter -> Advanced Options and the change the following settings:
<pre>
MaxOutstandingR2T change the default 1 to 8

FirstBurstLength change the default 262144 to 65536

MaxBurstLength change the default 262144 to 1048576

MaxRecvDataSegLen change the default 131072 to 1048576
</pre>
=== Write cache sync requests performance tuning ===

     Write cache sync requests (sync) set to “always” for zvol is the safest option and is set by default. However, it can cause write performance decreases since all operations are written and flushed directly to the persistent storage. In case of using sync=always, it is strongly recommended using mirrored write log devices (very fast random writes devices).<br/>     Sync=standard or sync=disabled zvol options provide huge performance improvement but the most recent (up to 5 seconds) cached data can be lost in case of a sudden power failure. Use this option only in environments equipped with UPS.<br/>     For NFS shares the Synchronous data record is enabled by default. This option causes performance to be worse, but data can be safely written. In order to improve the NFS performance you can use Asynchronous data record but in such case, it is strongly recommended to use UPS.

== Known issues ==

=== Browser recommendations ===

     It is strongly recommended to use Mozilla Firefox browser to navigate the system’s GUI. When using other browsers some slight problems with displaying content may occur.

=== Web browser’s cache ===

     After updating from previous versions, some problems with WebGUI content and navigation may occur. To resolve this problems, please clear Web browser cache.

=== System as a guest in virtual environments ===

     Hyper-V:<br/>     In case of installing the system as a Hyper-V guest please use the following settings:<br/>       - Number of virtual processors: 4<br/>       - Memory: Minimum 8GB<br/>       - Boot Disk: 20GB IDE Disk<br/>       - Add at least 6 virtual disk

 <br/>     VMware ESXi:<br/>     In case of installing the system as a VMware ESXi guest please use the following settings:<br/>       - Guest OS: Other 2.6.x Linux ( 64bit )<br/>       - Number of Cores: 4<br/>       - Memory: Minimum 8GB<br/>       - Network Adapter: VMXNET 3<br/>       - SCSI Controller Type: Paravirtual or LSI Logic SAS<br/>       - Boot Disk : 20GB Thick Provision Eager Zeroed<br/>       - Add at least 6 virtual disk<br/>       - Edit Settings->Options->Advanced-General->Configuration-> Add row: disk.EnableUUID : TRUE

=== Reclaim deleted blocks on thin-provisioned LUNs in various systems ===

     In case of deleting large amounts of data, reclaimed deleted blocks on thin-provisioned LUNs in Windows 2012 can significantly slow down system performance. If you predict frequent deletions of large amounts of data, we recommend turning off the automatic reclaim function in Windows 2012. This can be done by disabling the "file-delete notification" feature in the system registry. To do so, follow the steps below:<br/>       - start Registry Editor.<br/>       - locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem       <br/>       - double-click DisableDeleteNotification.<br/>       - in the Value data box, enter a value of 1, and then click OK.<br/> <br/>     In order to reclaim the free space in Windows 2012 please change the    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\DisableDeleteNotification key value back to 0 and use "Optimize" tool located in Disc Management->[disk]->Properties->Tools. As the operation can generate a very high load in the system, it is recommended to perform it after-hours.  <br/>In case of VMware ESXi, the automatic reclaim feature is disabled by default. To reclaim the space of deleted blocks on thin-provisioned LUNs, please use vmkfstools. For details, please refer to the VMware Knowledge Base:

For VMware ESXi 5.0: [http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849 http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014849]<br/>For VMware ESXi 5.5 and newer: [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513 https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513]<br/>For VMware ESXi 6.7 and newer: search in Internet for “Space Reclamation Requests from VMFS Datastores” and read vendor documentation.

In case of using Windows 2008 there is no possibility to reclaim the space released by deleted data of thin-provisioned LUNs.

=== Deduplication issues and recommendations ===

     Please be aware that deleting the zvol with deduplication enabled can generate a very high load in the system and lead to unstable behavior. It is strongly recommended to perform such operation only after-hours. To avoid this issue, please use (if possible) single zvol on zpools dedicated for deduplication and delete the zpool which includes the single zvol.<br/>   <br/>     To determine the amount of System RAM required for deduplication, use this formula:<br/> <br/>                                                                                                                    (Size of Zvol / Volume block size) * 320B / 0.75 / 0.25<br/> <br/>Where:<br/>320B - is the size of entry in DDT table<br/>0.75 - Percentage of RAM reservation for ARC (75%)<br/>0.25 - Percentage of DDT reservation in ARC (25%)<br/> <br/>     Example for 1TB data and 64KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 65536B) * 320B / 0.75 / 0.25 = 28633115306.67B<br/>                                                                                                                       28633115306.67B / 1024 / 1024 / 1024 = 26.67GB<br/> <br/>so for every extra 1TB of storage, system needs extra 26.67GB RAM.<br/><br/>     Example for 1TB data and 128KB Volume block size:<br/> <br/>                                                                                                       (1099511627776B / 131072B) * 320B / 0.75 / 0.25 = 14316557653.33B<br/>                                                                                                                        14316557653.33B / 1024 / 1024 / 1024 = 13.33GB<br/> <br/>so for every extra 1TB of storage, system needs extra 13.33GB RAM.
<div><br/></div><div>     Example for 1TB data and 1MB Volume block size:</div><div><br/></div><div>                                                                                                      (1099511627776B / 1048576B) * 320B / 0.75 / 0.25 = 1789569706,66B</div><div>                                                                                                                        1789569706,66B / 1024 / 1024 / 1024 = 1.66GB</div><div> </div><div>     so for every extra 1TB of storage, system needs extra 1.66GB RAM.</div><div><br/></div>
<br/>'''IMPORTANT: '''The above calculations only apply to the worst case scenario, when data is completely unique and will not be deduplicated. For the deduplicable data, the need for RAM drastically decreases. If SSD based Read Cache is present, part of deduplication table will be moved to the SSD and deduplication will work with good performance using less RAM.

<br/>'''IMPORTANT: '''With SAN (iSCSI) it is CRITICAL to match User-File-System format block size with the zvol volume-block-size. A simple example is a Windows file system NTFS with default format block size 4k and zvol default volume-block-size is 128k. With defaults like this deduplication will mostly NOT match because files can be aligned in 32 (128/4) different positions on the pool. If the NTFS format is increased to 64k and the zvol default volume-block-size is 128k, deduplication match can fail only one time because a file can be aligned to 2 (128/64) different positions on the pool. Every next write will match already as both alignment options already exist on the pool. In order to achieve all files matching and efficient memory usage NTFS must use 64k format block size and the zvol volume-block-size must equal 64k. Another option is that the NTFS=32k and zvol=32k, but in this case the deduplication table will be twice as large. That is why the NTFS=64k and zvol=64k is the most efficient setting for deduplication.

'''IMPORTANT: '''With NAS (NFS, SMB/CIFs) deduplication matching works always due to the data blocks being aligned by ZFS natively.

'''IMPORTANT: '''De-duplication is working on the pool level in the pool-range. This is why zvol-Physical size cannot show de-duplication benefit. In order to prove that deduplication saved space run the scrub and notice the current physical data space on the pool reported by the scrub. Next copy of new data and run the scrub again. Now scrub will show new physical data space. Comparing the data size from storage client side with the data space growth from the scrub will give the deduplication advantage. The exact pool of the deduplication ratio can be found in LOGs in zfs.log.

=== Zvols configuration issues and recommendations ===

     It is strongly recommended to set the client file system block size same as the zvol volume block size. For example, when using 64k zvol volume block size, the Windows Allocation unit size of NTFS should be set to 64k.

=== Target number limit ===

    In case of more than 60 targets, GUI will not be displayed correctly. This issue will be fixed in the next releases.

=== Targets with the same name are not assigned correctly ===

    Having two or more targets with the same name but belonging to various Zpools, will cause that all targets with the same name will be assigned to one Zpool during the import process.

=== Installation on disks containing LVM metadata ===

     There is no possibility to install the system on disks containing LVM metadata. You will need to clear those disks before installation. To do so, use the “Remove ZFS data structures and disks partitions” function located in the Extended tools. To access this function, boot the system from a temporary media like a USB drive or DVD.

=== Import Zpool with broken write log ===

     There is no option to import Zpool with a broken write log disk using the system’s functions. This is why it is STRONGLY recommended to use mirrored disks for write logs. In case it is necessary to import Zpool with a broken write log, please contact technical support.

=== Replacing disks in data groups for larger ones can cause your storage license capacity to be exceeded ===

     In case of replacing damaged disks for larger ones, the size of the entire Zpool will increased. Make sure that the new size will not exceed your purchased storage license.

=== Periodically after some operations, the GUI needs to be manually refreshed ===

     After performing some operations, e.g. resilvering, the GUI will show outdated information. In this case refresh the web page manually by pressing F5 on your keyboard. This issue will be fixed in next releases.

=== Replacing disks in data groups for smaller ones can cause an error and make the disk disappear from the list of available disks ===

     Operation of replacing a disk in a data group for a smaller one will cause an error "zpool unknown error, exit code 255", and the disk will become unavailable. In order to reuse this disk, please use function "Remove ZFS data structures and disks partitions" located in the Extended tools on the Console screen.

=== It is strongly recommended to use 64KB or higher Volume block size ===

     Smaller than 64KB block sizes used with deduplication or read cache will cause very high memory consumption.

=== RAM recommendations for Read Cache ===

     To determine how much System RAM is required for Read Cache, use the following formula:

<br/> <br/>                                                                      RAM needed = (Size of Read Cache - reserved size and labels) * bytes reserved by l2hdr structure / Volume block size<br/> 

     For 8KB Volume block size and 1TB Read Cache:<br/><br/>                                                                           RAM needed = (1099511627776B - 4718592B) * 432B / 8192B = 57981809664B<br/>                                                                                                        57981809664B / 1024 / 1024 / 1024 = 54GB<br/> <br/>Where:<br/>1099511627776B - 1TB Read Cache<br/>4718592B - reserved size and labels<br/>432B - bytes reserved by l2hdr structure<br/>8192B - Volume block size<br/> <br/>                                                                                                  For 64KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 65536B = 7247726208B<br/>                                                                                                       7247726208B / 1024 / 1024 /1024 = 6.75GB<br/><br/><br/>                                                                                                  For 128KB Volume block size and 1TB Read Cache:<br/>                                                                    RAM needed = (1099511627776B - 4718592B) * 432B / 131072B = 3623863104B<br/>                                                                                                       3623863104B / 1024 / 1024 /1024 = 3.37GB

=== Multiple GUI disk operations may result in an inaccurate available disks list ===

     Multiple operations of adding and detaching disks from groups can cause that the next operation of detaching will fail, but the disk will be shown on a list of available disks. When trying to add this disk to one group it will fail with the following error "[zfslib-wrap-zpool-ZpoolCmdError-1] invalid vdev specification". In this case, detach this disk once again.

=== After removing disks from groups they may not be displayed on a list of available disks ===

     Sometimes after removing disks from groups, Spare/Read Cache/Write Log disks are displayed on a list of unassigned disks, but they are not on a list of available disks. In this case, click the rescan button located in the adding group form.

=== Reusing disks from an exported and deleted Zpool ===

     After deleting an exported Zpool, not all disks which were a part of a Zpool become immediately available. Before you can reuse disks, which were previously used as a Spare or a Read Cache, you must first clean them. Use “Remove ZFS data structures and disks partitions” function located in the “Extended tools”.

=== Negotiated speed of network interfaces may not display correctly ===

     For some network interfaces, the negotiated speed field may display an incorrect value in GUI and Console. This issue will be fixed in next releases.

=== Limited possibility to display a large number of elements by the GUI ===

     After creating multiple snapshots, clones or zvols some forms in GUI work very slow. If you need to create many snapshots, clones or zvols, it is strongly recommended to use CLI in order to perform operations on them.

=== Scale Logic VSS Hardware Provider system recommendations ===

     It is strongly recommended to use Windows Server 2012. On the other Windows systems, Scale Logic VSS Hardware Provider Configuration works unstable.

=== Exceeded quota for dataset does not allow to remove files ===

     Files located on datasets with exceeded quota cannot be removed. In this case, please resize quota and then remove unnecessary files.

=== Slow WebGUI with multiple datagroups ===

     Zpool with more than 20 datagroups causes that some forms on WebGUI work very slow. If you need to create many datagroups, it is strongly recommended to use CLI API.

=== Slow WebGUI with multiple datasets ===

     More than 25 datasets cause that WebGUI works slow.

=== ZFS Upgrade ===

     For Scale Logic ZX users, it is recommended to upgrade Zpools to the latest ZFS file system. Although the file system upgrade is absolutely safe for your data, and takes only few minutes, please be aware that this operation cannot be undone. In order to upgrade a single Zpool, please use "WebGUI -> Zpool options -> Upgrade file system" from Zpool's option menu.

=== Intel® Ethernet Controller XL710 Family ===

     In case of using Scale Logic ZX with Intel® Ethernet Controller XL710 Family, it is necessary to update firmware’s network controller to the version: f4.33.31377 a1.2 n4.42 e1932.

=== Motherboards with x2APIC technology ===

     In case of using a motherboard with x2APIC technology enabled, it is necessary to disable x2APIC in BIOS. Otherwise, problems with CPU cores will occur.

=== NFS FSIDs and Zpool name ===

     One of the factors that have been taken into account when NFS FSIDs are generated is Zpool name. It indicates that when Zpool name is changed, e.g. during export and import with different names, FSIDs for NFS Shares located on this Zpool will also be changed.

=== High Availability shared storage cluster does not work with Infiniband controllers ===

     Due to technical reasons the High Availability shared storage cluster does not work properly when using the Infiniband controllers for VIP interface configuration. This limitation will be removed in the future releases.

=== Disks with LVM data cannot be used with the created Zpool ===

     Attempt to create Zpool with drives that contain LVM data will fail with the following error:

''"cannot open 'lvm-pv-uuid-R25lTS-kcDc-eiAN-eAlf-ppgi-rAqu-Oxy1Si': no such device in /dev must be a full path or shorthand device name"''

In this case, if you want use those disks, please use “Remove ZFS data structures and disks partitions” function located in “Extended tools”.

=== Unexpected long failover time, especially with HA-Cluster with two or more pools ===

     Current failover mechanism procedure is moving pools in sequence. Since up27 release, up to 3 pools are supported in HA-cluster. If all pools are active on single node and failover needs to move all 3 pools, the failover may take longer than 60 seconds which is a default iSCSI timeout in Hyper-V Clusters. In some environments, under heavy load a problem with too long time of cluster resources switching may occur as well. If the switching time exceeds the iSCSI initiator timeout, it is strongly recommended to increase the timeout up to 600 seconds.

     '''In case of using Windows, to increase iSCSI initiator timeout, please perform following steps:'''

1. Run regedit tool and find: ''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\...\Parameters\MaxRequestHoldTime registry key''

2. Change value of the key from default 60 sec to 600 sec (decimal)

     '''In case of using VMware, to increase iSCSI initiator timeout, please perform following steps:'''

1. Select the host in the vSphere Web Client navigator

2. Go to Settings in the Manage tab

3. Under System, select Advanced System Settings

4. Choose the ''Misc.APDTimeout'' attribute and click the Edit icon

5. Change value from default 140 to 600 sec.

     '''In case of using XenServer, to increase iSCSI initiator timeout, please perform following steps:'''

A. For existing Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Detach and reattach SRs. This will update the new iSCSI timeout settings for the existing SRs.

B. For new Storage Repositories (SR):

1. Edit /etc/iscsi/iscsid.conf

2. node.session.timeo.replacement_timeout = 120

3. Change value from default 120 to 600 sec.

4. Create the new SR. New and existing SRs will be updated with the new iSCSI timeout settings.

=== Activation may be lost after update ===

     In some environments, after update to up11 system may require re-activation. This issue will be removed in the future releases.

=== Bonding ALB and Round-Robin do not work in Hyper-V and VMware environments ===

     In case of using ZX as Hyper-V or VMware guest, bonding ALB and Round-Robin is not supported. Please use another type of bonding.

=== Continuous writing in VMware guest can cause that deleting VMware snapshot can take long time ===

     Using ODPS on zvol/dataset with VMware guest where many I/O operations are performed can cause that the process of deleting VMware snapshot can take long time. Please take this into consideration while you set up the scheduler for Off-site Data Protection Service task.

=== Enabling quota on dataset can cause file transfer interrupt ===

     Enabling quota functionality on a dataset can cause file transfer interrupt. Before using it in production environment, please enable quota on dataset, or make sure that no file transfers are active.

=== Nodes connected to the same AD server must have unique Server names ===

     If ZX nodes are connected to the same AD server, they cannot have the same Server names.

=== Share can not be named the same as Zpool ===

     In case of share with the same name as Pool connections problem will occur. Please use different names.

=== No persistent rules for network cards in virtual environment ===

     Changing settings of virtual network cards (delete, changing MAC, etc.) can cause unstable system behaviour. Please do not change settings on production system. This issue will be fixed in next releases.

=== Downgrade to up17 or earlier is not possible ===

     Starting from up18 bootable medium has always SW RAID structure. Attempt to come back to earlier version is impossible. If you need come back to earlier version, you must reinstall version again.

=== System cannot be installed on cciss based controllers ===

     This issue will be fixed in next releases.

=== Interrupt the process of adding second disk to SW RAID (bootable medium) can cause run system from disk with uncompleted data ===

     Performing operation like: reboot, shutdown, power off, etc. during mirroring data on new added disk can cause that system will be booted from new disk which has incomplete data. In this case, SW RAID function shows empty status and wrong number of RAID members. To resolve this issue, please plug off disk which has incomplete data, boot system, plug in disk and add it once again to SW RAID.

=== SAS-MPIO cannot be used with Cluster over Ethernet ===

     It is strongly not recommended to use Cluster over Ethernet with SAS-MPIO functionality. Such a configuration can lead to a very unstable cluster behavior.

=== On- & Off-site Data Protection backward compatibility problem ===

     In case of using On- & Off-site Data Protection functionality in up21 or earlier, it is strongly recommended to remove all backup tasks created by CLI API and re-create it using GUI.

=== Wrong state of storage devices in VMware after power cycle of both nodes in HA FC Target ===

     In FC Target HA environment, power cycle of both nodes simultaneously may lead to a situation when VMware is not able to restore proper state of the storage devices. In vSphere GUI LUNs are displayed as Error, Unknown or Normal,Degraded. Moving affected pools to another node and back to its native node should bring LUNs back to normal. A number two option is to restart the Failover in ZX’s GUI. Refresh vSphere’s Adapters and Devices tab afterwards.

=== Problem with maintenance in case of disk failure ===

     In case of disk failure, please remove the damaged disks from the system, before starting administrative work to replace the disk. The order of actions is important.

=== Separated mode after update from ZX up24 to ZX up25 ===

     In HA cluster environment after updating of one node from ZX up24 to ZX up25 the other node can fall into separated mode and the mirror path might indicate disconnected status. In such a case go to Failover Settings and in the Failover status section select Stop Failover on both nodes. Once this operation is finished select Start Failover.

=== Different Write Cache default setting for zvols in early beta versions of ZX up25 ===

     In the early beta versions of ZX up25 the default value of the Write Cache Log bias of zvols was set to “In Pool (Throughput)”. In the final release of ZX up25 the Log bias is set to “Write log device (Latency)”.<br/>Please note, that “In Pool (Throughput)” setting may cause a drop in performance in environments with a lot of random access workloads which is a common factor for a majority of production environments.

=== Target alias name is required while configuring HA FC Target in case of adding two or more ports to one FC group ===

     If we want to have more then one port in each FC group (in HA FC configuration) it is necessary to type in Target alias name for every port. Otherwise an error message “Target alias is already used” can show up while setting up remote port mapping for FC targets in (pool name) -> Fibre Channel -> Targets and initiators assigned to this zpool. This issue will be resolved in the future release.

=== New default value for qlini_mode parameter for FC kernel module qla2xxx_scst ===

     In order to configure FC Target, kernel module parameter qlini_mode should be set to “exclusive” (in some early beta versions of ZX up25 qlini_mode was set up to “enabled”). In order to verify the value of this parameter open ZX TUI and use CTRL+ALT+W key combination to launch Hardware configuration. Press "Yes" to acknowledge the initial warning message. Type in the password. Choose option: Kernel module parameters. Select qla2xxx_scst QLogic Fibre Channel HBA Driver and make sure the value of this parameter is set to “exclusive”.<br/><br/>Please note that in order to change this parameter Failover must be stopped first.

=== Very low performance of FIO/WT in case of mixed FIO/WT and FIO/WB zvol configurations over Fiber Channel ===

     In case of the mixed FIO/WT and FIO/WB zvol configurations over FC one can observe significantly decreased performance on FIO/WT.

=== More than one zvol with FIO/WB mode can cause instability of the Fiber Channel connection ===

     If there's more than one FIO/WB zvol or a FIO/WB zvol is coexisting with other types of zvols it can cause an instability of the FC connection with client machines. As a result client machines may unexpectedly lose FC connected resources.

=== In certain situations system page cache is not able to flush File I/O errors by itself and cache flushing has to be performed manually ===

     Under certain conditions (like overfilling zvol and then expanding its size) some File I/O errors may be held by the system page cache and it requires manual flushing (in GUI use Storage -> Rescan).

=== Updating nodes of the ZX cluster from up24 and earlier versions changes FC ports to target mode resulting in losing connection to a storage connected via FC initiator ===

     There is a significant difference in FC configurations in up24 and earlier versions. Those versions allowed the FC ports to be configured in initiator mode only, while later versions allow both target and initiator mode with target as default, so in case of using storage connected via FC initiator, FC port(s) must be manually corrected in GUI of the updated node.

=== Updating Metro Cluster node with NVMe disks as read cache from ZX up26 or earlier can cause the system to lose access to the NVMe disks ===

     The process of updating of Metro Cluster node from ZX up26 or earlier is changing NVME disk IDs. In consequence moving pool back to updated node is possible but the read cache is gone (ID mismatch). In order to bring read cache back to the pool we recommend to use console tools in the following way: press Ctrl+Alt+x -> “Remove ZFS data structures and disks partitions”, locate and select the missing NVMe disk and press OK to remove all ZFS metadata on the disk. After this operation click Rescan button in GUI -> Storage. The missing NVMe disk should now appear in Unassigned disks at the bottom of the page which allows to select that disk in pool’s Disk group’s tab. Open Disk group tab of the pool, press the Add group button and select Add read cache. The missing disk should now be available to select it as a read cache.

=== Synchronization of a large LDAP database can last for a long time (e.g. 10h for 380K users) and can be associated with high system load ===

     This problem will be solved in future releases.

=== Long time of a failover procedure in case of Xen client with iSCSI MPIO configuration ===

     In a scenario where Xen client is an iSCSI initiator in MPIO configuration, the power-off of one node starts the failover procedure that takes a very long time. Pool is finally moved successfully but there are many errors showing up in dmesg in meantime. In case of such an environment we recommend to add the following entry in the device section of the configuration file: /etc/multipath.conf:

'''no_path_retry queue'''

<br/>The structure of the device section should look as follows:
<pre>device {
vendor "SCST_FIO|SCST_BIO"
product "*"
path_selector "round-robin 0"
path_grouping_policy multibus
rr_min_rio 100
no_path_retry queue
}
</pre>
=== In case of large number of disks, zpool move can take a long time ===

     In certain environments in case of large number of disks (about 100 and more) the zpool move operation can take a long time.

=== No support for VMD option in BIOS leads to a problem with listing PCI devices ===

     On some servers, an enabled VMD option in BIOS causes that PCI devices are not listed properly. If this is the case please disable the VMD option in BIOS. This problem will be solved in the future release.

=== Rolled back data are not properly refreshed both in Windows and Vmware systems ===

     Before using rollback operation on zvol please detach iSCSI or FC target, perform rollback operation and reattach target.

=== User gets deleted from share access list after changing its username on AD server ===

     If the AD user is assigned to a share and later the username is changed we should let ZX know about it. Using the "Synchronize and update shares configurations" operation on ZX leads to a situation where the changed user gets deleted from the share’s access list. The new username needs to be added to the share’s access list manually.

=== QLogic 32Gbit FC HBA is no longer supported ===

     Starting from ZX up29 we no longer support QLogic 32Gbit FC adapters.

=== Certain 16Gbit FC HBAs are no longer supported ===

     Starting from ZX up29 we no longer support certain 16Gbit FC adapters. If you are using a 16Gbit FC adapter based on the Qlogic chipset using the qla2xxx_scts driver, please refer to our online hardware compatibility list (HCL) to verify if that particular adapter is supported.

=== E-mail password cannot contain special non-ASCII characters ===

     The following special characters # : + cannot be used in a password used in an e-mail notification feature. They can break the authentication process.

=== LSA e-mail notifications does not work with SMTP servers requiring SSL/TLS authentication ===

     E-mail alert configuration in LSI Storage Authority Software does not work with SMTP servers which require SSL/TLS authentication

=== Moving IP address of the NFS share’s IP read only access list to read/write access list cannot be performed in one step ===

     If an IP address is already present on the NFS access list and you would like to move it to another access list, it has to be performed in two steps. First delete the IP address from the current list and apply the changes. Next edit the NFS share again and add the IP address to the other access list.

=== If the used space on zpool reaches more than 80%, the system may generate high load and become unstable ===

     If the used space on the zpool reaches more then 80%, the system is trying to utilize the available space to the maximum. As a result, the system load may increase, especially waiting I/O and cause its unstable work. Expanding the pool size space is recommended.

=== In certain situations WebGUI is not showing the current state of the system ===

     There are situations when the system is performing actions taking too long for the WebGUI to refresh the values in the web browser. In such a case the system is showing the old value taken directly from cache memory. We recommend using the F5 key to refresh the WebGUI.

=== An ongoing O&ODP process involving small zvol block size or dataset record size generate high load and render the system unstable ===

     O&ODP backup tasks involving small zvol block sizes as well as small dataset record sizes (4KB - 16KB) are known to generate very high load rendering the system unstable. We recommend using at least 64KB sizes for zvols and datasets.

=== Runtime UPS calibration in the client-server configuration unexpectedly shutdowns ZX ===

     In the client-server configuration of the UPS, the runtime UPS calibration process returns an improper value interpreted by ZX as being on battery. When it timeouts it shuts the system down.

=== Starting from up29 (including updating from previous version), system cannot boot up in UEFI mode if your boot medium is controlled by LSI SAS 9300 HBA with outdated firmware ===

     Make sure your LSI SAS 9300 HBA has the latest firmware installed. A quick workaround is changing the booting mode from UEFI to Legacy.

=== Bonded Mellanox network cards show negative values on the network usage chart ===

     This issue will be solved in the future release.

=== In case of hundreds of thousands of LDAP users system starts very slowly ===

     LDAP database is stored on the boot medium. If you have that large LDAP database we recommend using ultra fast NVMe disk for boot medium.

=== After update to ZX up29 write back cache on some hardware RAID volumes can be unintentionally disabled ===

     Starting from ZX up29 we disable write-back cache on all HDD disks by default, but we do not disable write-back cache on SSD drives and hardware RAID volumes. It can happen however that the write-back cache on some RAID volumes can be turned off. Hardware RAID volume performance can be heavily impacted by the lack of the write-back cache, so please make sure it's enabled after update. Open TUI and invoke Extended tools by pressing CTRL+ALT+t, then select Disk write-back cache settings.

=== Restarting or disconnecting JBOD with the write-back cache enabled on disks can lead to the data inconsistency ===

     If write-back cache is enabled on disks in JBOD then restarting or disconnecting JBOD can lead to data inconsistency. Starting from ZX up29 we disable write-back cache on HDD disks by default during bootup procedure. We do not disable write-back cache on SSD drives and hardware RAID volumes.

=== Snapshots are not displayed after a system reboot if there are more than a few thousands of snapshots ===

     In case there is a large number of snapshots (more than a few thousands) there might be a significant delay in listing them in WebGUI after a system reboot. Depending on how big the number of snapshots is, it may take a few minutes or up to several dozen minutes to populate the list in WebGUI.

=== It is not recommended to use the gzip-9 compression algorithm. ===

     In case of using the gzip-9 compression algorithm the system can behave unstable when copying the data to storage. It is possible to use this compression algorithm only in environments where very efficient processors are being used.

=== It is not recommended to use more than 500 zvols. ===

     In case of using more than 500 zvols in the system, the responsiveness of the Web-GUI may be low and the system may have problems with the import of zpools.

=== It is recommended to use Fibre Channel groups in Fibre Channel Target HA Cluster environments that use the Fibre Channel switches. ===

     In case of using the Fibre Channel switches in FC Target HA Cluster environments, it is recommended to use only Fibre Channel groups (using the Fibre Channel Public group it is not recommended).

=== Manual export and import of zpool in the system or deactivation of the Fibre Channel group without first suspending or turning off the virtual machines on the VMware ESXi side may cause loss of access to the data by VMware ESXi. ===

     Before a manual export and import of a zpool in the system or deactivation of the Fibre Channel group in Fibre Channel Target HA Cluster environment, you must suspend or turn off the virtual machines on the VMware ESXi side. Otherwise, the VMware ESXi may lose access to the data, and restarting it will be necessary.

=== In Fibre Channel Target HA Cluster environments the VMware ESXi 6.7 must be used instead of VMware ESXi 7.0. ===

     In case of using the VMware ESXi 7.0 in Fibre Channel Target HA Cluster environment, restarting one of the cluster nodes may cause the Fibre Channel paths to report a dead state.

=== Sometimes cluster nodes hang up during boot of Scale Logic ZX. ===

     In case one of the cluster nodes hangs up during Scale Logic ZX boot, it must be manually restarted.

=== Sometimes when using the ipmi hardware solutions, the cluster node may be restarted again by the ipmi watchdog ===

     In this case, it is recommended to wait 5 minutes before turning on the cluster node after it was turned off.

=== Sometimes restarting one of the cluster nodes may cause some disks to be missing in the zpool configuration. ===

     In this case, click the “Rescan storage” button on the WebGUI to solve this problem.

=== The Internet Connection Check functionality has been removed. ===

     In order to check the internet connection, try to get the date and time from the NTP server using the Web-GUI (System Settings -> System -> Time and date settings).

=== After upgrading the system to a newer version, the event viewer reported an error message: An unexpected system reboot occurred. ===

     After upgrading the system to a newer version, the event viewer reported an error message: "An unexpected system reboot occurred. Run the 'Scrub scanner' on all pools to check the system integrity. Analysis of logs and previous events can help to find the cause of this problem and prevent the issue in the future. For more information, refer to the help article.". This information should be ignored.

=== Low performance on remote disks in case of new installation of ZX up29r2. ===

     The source for this problem is the zfs_vdev_max_active parameter set to 1 on a new installation of ZX up29r2. To resolve this problem, please change the value of the zfs_vdev_max_active parameter from 1 to 1000 in TUI.  In order to change the zfs_vdev_max_active parameter to 1000 open ZX TUI and use CTRL+ALT+W keys combination to launch Hardware configuration. Press "Yes" to acknowledge the initial warning message. Type in the password. Choose option: Kernel module parameters. Select the zfs module, then the zfs_vdev_max_active parameter and change its value to 1000. This operation requires a restart of the ZX. This should be done by selecting the Reboot option in the TUI. 

=== In case of no local storage disks in any Non-Shared storage HA Cluster node, the remote disks mirroring path connection status shows incorrect state: Disconnected. ===

     According to assumptions, each cluster nodes in Non-Shared storage HA Cluster must have at least one local storage disk before creating the remote disk mirroring path connection.

=== In case of adding an NVMe disk to one of the cluster nodes in Non-Shared storage HA Cluster this information will not automatically refresh on the remote cluster node. ===

     To resolve this problem, please remove and add remote disks mirroring path connection again on the WebGUI. After the remote disks mirror path connection is re-established, the disks information should be refreshed on both cluster nodes.

=== In some environments in case of using RDMA for remote disks mirroring path, shutdown one of the cluster nodes may causes its restart instead of shutting down. ===

     In some environments in case of using RDMA for remote disks mirroring path, shutdown one of the cluster nodes may causes its restart instead of shutting down.

=== It is not recommended to use the ATTO Fibre Channel Target in the HA cluster environment. ===

     In case of using the ATTO Fibre Channel Target in a HA Cluster environment, after the power cycle of one of the cluster nodes, the fibre channel path reports a dead state. In order to restore the correct status of these fibre channel paths, the VMware server must be restarted.<br/><br/>     In case of using the ATTO Fibre Channel Target in a HA cluster environment, restarting the cluster node with both zpools imported in the system causes the second cluster node to be unexpectedly restarted.

<br/>Therefore, using the ATTO Fibre Channel Target in the HA cluster environment is not recommended.

=== The SED functionality configuration issues. ===

     The SED functionality in Scale Logic ZX enables to use the drives with verified SED configuration only.

=== The SED configuration tool available in TUI also lists devices that are not currently supported. ===

     The SED configuration tool available in TUI also lists devices that are not currently supported. To check if a given device is supported, see the HCL list available on the Scale Logic webpage.

=== Enabling the autotrim functionality in the zpools may cause drastic increase load or iowait in the system. ===

     In case of a drastic increase load or iowait in the system after enabling the autotrim functionality in the zpools, consider disabling it. It is recommended to run the "Trim" function manually on demand and at a convenient time (e.g. at a time when the system is working under less load).

=== The Mellanox ConnectX-3 network controller is no longer supported in RDMA mode due to its instability. ===

     In order to provide stable work with RDMA we recommend using the Mellanox ConnectX-4, ConnectX-5, or ConnectX-6.

[[Category:Release Notes]]