File:NYMNETWORKS-MIB-up30.txt

2023-12-12T16:06:30Z

Pa-P:

File:NYMNETWORKS-MIB.txt

2023-12-12T16:06:12Z

Pa-P:

Scale Logic ZX ver.1.0 up30 Release Notes

2023-12-12T16:02:42Z

Pa-P: 1 revision

'''Release date: 2023-12-06'''

'''Build: 53984'''

   <span style="color:#cc0033">'''Important!''' </span>To upgrade the product, you need to have an active Technical Support plan. You will be prompted to re-activate your product after installing the upgrade to verify your Technical Support status.

If you don't have an active Technical Support plan, please contact Scale Logic sales team or your reseller for further assistance.

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

|}

== New ==

=== ZFS Special Devices feature ===

=== NVMe Disk Partitioning feature ===

=== Self-Encrypting Drives (SED) support for HA Non-Shared Storage Clusters ===

=== Active Directory with extended RID Range and RFC2307 compatibility ===

=== Support for macOS Time Machine backup mechanism ===

=== Support for ”hide unreadable folder and files” option in Samba ===

=== Support for recycle bin in Samba for Microsoft Windows ===

=== The "Send Compressed Data" Option in Scale Logic ZX On- & Off-Site Data Protection ===

=== Support for Zero-configuration networking (zeroconf) feature with the services discovery options ===

=== TUI: New predefined as well as editable custom storage performance profiles for tools testing purposes ===

=== TRIM management for selected drives ===

=== Active SMB user connections and active iSCSI connections statistics are available in the WebGUI in the Service Status tab ===

=== S.M.A.R.T monitoring functionality in the WebGUI ===

=== ZFS ARC, L2ARC, and ZIL statistics in the WebGUI ===

=== LSI SNMP Agent ===

=== Checkmk agent turn off in the TUI ===

=== Driver for Broadcom HBA 9600-16e 12Gb Tri-Mode Storage Adapter (mpi3mr, v8.6.1.0.0) ===

== Updated ==

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

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

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

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

=== Broadcom NeXtreme-E Series 10/100GbE Network Controller driver (bnxt_en, v1.10.2-223.0.162.0) ===

=== Broadcom BCM57xx Network Controller driver (bnx2x, v1.715.13) ===

=== Broadcom BCM57xx Network Controller driver (bnx2, v2.2.6a) ===

=== Solarflare 10GbE Network Controller driver (sfc, v4.15.14.1001) ===

=== Chelsio 10GbE Network Controller driver (cxgb4, v3.18.0.0) ===

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

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

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

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

=== Microsemi Adaptec SmartHBA and SmartRAID Adapter driver (smartpqi, v2.1.22-040) ===

=== Microsemi Adaptec MaxView tool (v3.10.00 (24308)) ===

=== LSI Storage Authority Software (v008.004.010.000) ===

=== ATTO ExpressSAS 6Gb/s HBA Adapter driver (esas2hba, v2.41.0f1) ===

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

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

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

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

=== ATTO Config Tool (v4.39) ===

=== Emulex LightPulse Fibre Channel Adapter driver (lpfc, v12.8.614.22) ===

=== Mellanox firmware update driver (mft, v4.23.0) ===

=== Check_mk agent (check_mk, v2.1.0p14) ===

== Fixed ==

=== (SU 90895): In the environments with more than 128GB RAM, kernel panic logs are not saved by Kdump ===

=== In some environments, under a heavy load and while using On- and Off-site Data Protection, the connection to the SMB share is interrupted ===

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

=== 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 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%.

=== Sometimes a web browser may display a blank help page. ===

     Sometimes a web browser may redirect to the help page using HTTPS, which can result in a blank page being displayed. To resolve this issue, please ensure that your web browser is redirected to the help page using HTTP.

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

[[Category:Release Notes]]

Service discovery

2023-12-12T15:30:38Z

Pa-P: Created page with "__NOTOC__ === Zeroconf service discovery === <div>This functionality allows discovering NAS devices by any operating system that supports zero-configuration networking (zero..."

__NOTOC__

=== Zeroconf service discovery ===
<div>This functionality allows discovering NAS devices by any operating system that supports zero-configuration networking (zeroconf), e.g., macOS.</div><div>Two types of services are currently supported:
*Discovering SMB services
*Discovering NAS for Time Machine via SMB
</div><br/>
===== Discovering SMB services =====
<div>Allows the server to broadcast information about its SMB services.</div><br/>
===== Discovering NAS for Time Machine via SMB =====
<div>Allows macOS users to perform backup tasks from the Mac computer to shared folders via SMB.</div><div>The following conditions must be met for the functionality to work:
*The “Discovering SMB services” option must be enabled.
*The “Discovering NAS for Time Machine via SMB” option must be enabled.
*The SMB protocol must be enabled, and the following options must be set as follows:
**Vfs_fruit ON
**oplocks ON
**level2 oplocks ON
**SMB2 leases ON
**kernel oplocks OFF
</div><br/><div>When all conditions above are met, the option that allows shares to be discovered by Time Machine becomes active. The next step is to select the "Enable macOS Time Machine support" option in every share the user wishes to make visible for Time Machine. All shares with this option enabled will be visible for Time Machine.</div><br/><div>'''<span style="color:#ff0000">Note!</span> If any of the above settings are changed, shares will no longer appear in Time Machine.'''</div>
[[Category:Help topics]]

SNMP settings

2023-12-12T15:19:43Z

2023-11-03T10:03:08Z

Pa-P: 1 revision

<div>This article describes how to set up an MS Windows desktop machine to support the Network File System (NFS) shares and how to connect to those shares. The presented method allows maintaining a connection to NFS shares when the pool moves. '''Recommended for cluster configuration'''.<br/></div><div><br/></div>
Make sure that Services for NFS are enabled on your computer.

#Go to '''Control Panel > Programs > Programs and Features'''.
#Enable the "Turn Windows features on or off" option. You can find it in the menu on the left side.
#Go to the "Services for NFS" option.
#Enable the "Services for NFS" and both subfeatures.
#Reboot the computer to apply changes.

<div>[[File:WinFeatures.png|none|WinFeatures.png]]<br/></div><div><br/></div><div>Use the following command-line syntax in the "Command prompt" window to mount the NFS share:<br/></div><div>
*Replace the "server.name.or.IP" with the server's name where the NFS share is on or with its IP.
*Replace the "share_name" with the name of the NFS share (for example, "test_share")
*Replace the "X" with the desired drive letter.
</div><pre>mount -o anon mtype=hard timeout=30 \\server.name.or.IP\share_name X:</pre><div></div><div></div><div></div><div>An example of a correct command:<br/></div><pre>mount -o anon mtype=hard timeout=30 \\192.168.188.3\test_share F:</pre><div><br/></div><div>After the command is executed, the following confirmation is displayed:<br/></div><div><br/></div><div>[[File:Command prompt mount nfs share1.png|none|750px|Command prompt mount nfs share.PNG]]<br/></div><div><br/></div><div>The mounted NFS share is displayed in the "Network locations" section of the computer. <br/></div><div><br/></div><div>[[File:PC view.png|none|The mounted share in the PC view.png]]<br/></div><div><br/></div>
[[Category:ZFS and data storage articles]]

Multiple NICs in the same subnetwork

2023-11-03T10:03:08Z

Pa-P: 1 revision

__NOTOC__

<div>This document explains how to configure different network layouts that involve having multiple network interfaces in the same subnet. Each layout has specific setup steps.<br/>
In the examples we use:

*Host 1 to represent the storage server
*while Host 2 represents the machine that communicates with the storage server.
</div><br/>
'''IMPORTANT NOTE'''
<div>As a rule, we suggest that you avoid using network layouts that need multiple interfaces in the same subnet, because they may cause some network services to be unstable. Additionally, it might result in routing issues – for example, a packet sent through eth0 may get a reply from eth1. If you want to improve network performance, please consider using bonding or iSCSI multipathing scenarios instead.</div><br/>
== Scenario 1 ==
<div>Host 1 and Host 2 are connected through a switch. They have multiple network interfaces in the same subnet to communicate with each other.</div><div>[[File:Multiple NICs in the same subnetwork Scenario1.png|none|Multiple NICs in the same subnetwork Scenario1.png]]</div><div style="text-align: center"></div>
==== CONFIGURATION ====
<div>
*The need for static routing depends on the service being used.
*If Host 2 initiates the connection, Host 1 may not need static routing, but it is better to set it up for more reliability.
*If Host 1 initiates the connection, Host 1 needs static routing. This also applies if Host 2 is another storage server.
</div><br/>
==== POSSIBLE ISSUES ====
<div>Without static routing, Host 1 will use only the interface that comes first in the routing table (for example, eth1) for all connections it starts.</div><div>[[File:Multiple NICs in the same subnetwork scenario1-issue1.png]]</div><br/><div>The interface that comes first in the routing table is essential for Host 1 to initiate any connections. If it fails, Host 1 will lose this ability.</div><div>[[File:Multiple NICs in the same subnetwork scenario1-issue2.png]]</div><div>You can prevent this problem by configuring static routing for each interface.</div><div>[[File:Multiple NICs in the same subnetwork scenario1-issue3.png]]</div><br/><div>To configure static routing in the GUI, go to "System Settings", then select the "Network" tab and click the "Add static routing" button in the "Static routing manager" section.</div><br/><div>[[File:Multiple NICs static-routing-GUI.png]]</div><br/><div>The 'New route' window will appear. The fields should be filled in with the appropriate values.</div><br/><div>[[File:Multiple NICs static-routing-new-route.png]]</div><br/><div>'''Network/Host IP''': enter the IP address of the network card of the target host<br/>'''Netmask''': when we use a static route for a specific end host, the subnet mask is 32-bit (255.255.255.255)<br/>'''Interface''': from the drop-down menu, select the interface from which communication is to be established.</div><br/><div>Below is an example static route configuration for three NICs in the same subnet.</div><br/><div>[[File:Multiple NICs static-routing-table.png]]</div><br/>
== Scenario 2 ==
<div>Host 1 and Host 2 are connected through a switch. They have multiple network interfaces in the same subnet to communicate with each other. Additionally,  Host 1 also has an interface for WAN access.</div><br/><div>[[File:Multiple NICs scenario2 conf1.png]]</div><br/>
==== CONFIGURATION ====
<div>
*We strongly suggest that you use a different subnet for the WAN interface than the other interfaces. In such a case, this layout will be similar to Layout 1 and you can follow the same setup steps.
*But, unlike Layout 1, this layout always needs a gateway on the WAN interface (see the image below)
*Please check the “Possible issues” section for Layout 1 for problems that may also happen in this layout.
</div><br/><div>[[File:Multiple NICs scenario2 conf2.png]]</div><br/><div>To set up the gateway, please press CTRL+ALT+N on the system console and choose the interface. Then, select "Gateway."</div><br/><div>[[File:Network-setting.png]]</div><br/>
== Scenario 3 ==
<div>Host 1 and Host 2 are directly connected. For better connectivity with this host, there are several network interfaces within the same subnetwork.</div><br/><div>[[File:Multiple NICs scenario3.png]]</div><br/>
==== CONFIGURATION ====
<div>
*This scenario requires static routing to be set up on Host 1 and, depending on the operating system, on Host 2 as well.
*A local output interface must be assigned to every remote IP. This rule applies to both hosts.
</div><br/>
==== POTENTIAL ISSUES ====
<div>If Host 1 does not use static routing, it will always initiate connections through the interface that appears first in the routing table (in the example below, eth1).</div><div>[[File:Multiple NICs scenario3 issue1.png]]</div><br/><div>You can prevent this issue by configuring static routing for each interface.</div><br/><div>[[File:Multiple NICs scenario3 issue2.png]]</div><br/>
[[Category:ZFS and data storage articles]]

JBODs & JBOFs

2023-11-03T10:03:08Z

Pa-P: 1 revision

This functionality is available in the '''Storage Settings > JBODs & JBOFs''' tab

It’s used to obtain more information about the disks in the JBOD or JBOF by using external services, e.g. Redfish. For this reason, it is dedicated to disks enclosures with out-of-band management.

The functionality only works on currently supported devices such as '''VORTEX SHELF'''.

In the case of VORTEX SHELF, the Redfish service is used to gain more information about disks, so an account with this service will be needed. To link an enclosure to the service, click on the "'''Add device'''" button. A pop-up with a form will appear. Fill in the form.

To link a device through the service, the following information must be provided:

*'''Name (alias)''' - Set a name for the enclosure that allows the device to be recognized should there be a few machines of the same model.
*'''IP address / domain''' - The domain name or IP address connecting the device to the network.
*'''Port''' - Enter the number of the port used to communicate with the device through the Redfish service. The default port number is 443. Change as needed.
*'''Username''' - Enter the username to the Redfish service.
*'''Password''' - Enter the password that’s associated with the user name that’s been entered above.

After filling in every field, click the "'''Add'''" button. The system will then connect to the service and start to scan all the available disks. This may take some time. The system needs a while to scan a disk. Thus the more disks there are in an enclosure, the more time is needed to scan them all. After all the disks are scanned, the information will be available in the disk details section. Additional data such as:

*Name of the enclosure in which the disk is located,
*Number of the slot in which the disk is located

will also be displayed generally (i.e., in pool's disk groups, pool wizard, etc.).

'''NOTE!''' When the connection status changes, a rescan of all disks is required. This occurs, e.g.:

*When a device configuration is changing,
*When the system is restarted,
*After network reconnection (when the connection has been lost), etc.

The connection status of the enclosure is displayed in the table in the "'''JBODs & JBOFs'''" tab at all times. Next to the connection status there’s a power state displayed that shows if the device is turned on.<br/>Every device that has been added can be edited, removed from the table, or selected to display its details.

To do any of the above, use the context menu.<br/>The “'''Edit'''” option allows changing the device’s data or credentials.<br/>The “'''Details'''” option shows more information about an enclosure such as:

*Name (alias)
*Model
*Vendor name

The “'''Remove'''” option leads to the removal of a device from the table. Removing a device causes it to disconnect from the external service. Any additional information uploaded via the service after removing a device will not be displayed. In some cases, the option to turn on the LED for disks in the JBOD/JBOF may also become disabled.

[[Category:Help topics]]

FC Public Group

2023-11-03T10:03:08Z

Pa-P: 1 revision

This functionality is available in: '''Storage > FC Targets > Fibre Channel groups > Public group'''

= What is an FC public group =

A public group is a group of one or more Fibre Channel ports. Fibre Channel port groups help you organize and manage LUN mappings more easily. FC Public Group gives access to assigned volumes to any initiator that is able to connect to the FC target ports assigned to a given group.<br/><br/>'''IMPORTANT!''' '''It is recommended to use FC Public Group only with peer-to-peer FC connections to avoid unexpected behavior.'''

<br/>A public group is present on a pool by default and cannot be removed or created. Initially, no volumes or targets are assigned to this group, so nothing is available until it is configured manually. Devices available in such a group are visible globally, and there is no need to configure Fibre Channel Initiator by assigning WWN using GUI.

= Functionalities within the public group =

Within the public group, you can:

*'''Deactivate group''' - causes that access to the data in the group is no longer valid.
*'''Add target''' - specifies access to a public group for a given target.
*'''Attach an existing zvol''' - attaches an existing zvol to a public group.
*'''Add a new zvol''' - creates a new zvol. The options available here are described in this [[Add zvol|article]].

<br/>In the case of an existing zvol, you can edit, delete, detach it from the group, and add it to a backup task, but for the Fibre Channel targets it is only possible to detach a zvol from a group.

While it might be convenient to use this feature as it removes the necessity to configure initiators that will have access to the group resources, it might cause unwanted side effects for configurations that utilize an FC switch. Note that using an FC public group may lead to the following on the initiator's side:

#An unauthorized system connected to the same public group can gain access to FC resources.
#Unpredicted system states, e.g. creating a multipath.

<br/>'''Note! ''' You cannot add a target to a public group when it is assigned to another Fibre Channel group. The same target cannot be assigned to two groups that share a set of initiators.

= What must be taken into considerations/risks =

When the FC switch is used, and any of the server FC ports in initiator mode is also connected to that switch, it will cause the server to connect the volumes added to the public group. This behavior is caused by the fact that the public group allows connections from any initiator, including the initiator mode ports of the server that are connected to the same FC switch. In other words, the server will simply connect to itself. As a result, volumes exported by the server will be visible as connected to the server disks - it behaves as some sort of a loopback. Moreover, depending on the number of ports running in initiator mode connected to the same switch as target ports, the same volume might be connected to the server multiple times, creating a multipath configuration if that feature is enabled. The safest way to avoid this situation is to use the public group only for ports that are directly connected without utilizing the switch. In the case of FC switches, those devices usually allow the configuration of zones that describe which switch ports are logically interconnected. Zones may also be used to resolve described issues, but it might simply move the configuration effort from the FC group initiators configuration to the FC switch zone configuration.

----

More information about [[FC group|Fibre Channel groups]] can be found [[FC group|here]].

[[Category:Help topics]]