Scale Logic NX ver.1.0 up29r2 Release Notes - Revision history

Ma-W at 14:21, 12 January 2024

2024-01-12T14:21:52Z

@@ Line 356: / Line 356: @@
 In this case, if you want use those disks, please use “Remove ZFS data structures and disks partitions” function located in “Extended tools”.
@@ Line 426: / Line 380: @@
 &nbsp;&nbsp;&nbsp;&nbsp; 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.
@@ Line 485: / Line 433: @@
 === New default value for qlini_mode parameter for FC kernel module qla2xxx_scst ===
-&nbsp;&nbsp;&nbsp;&nbsp; In order to configure FC Target, kernel module parameter qlini_mode should be set to “exclusive” (in some early beta versions of NX up25 qlini_mode was set up to “enabled”). In order to verify the value of this parameter open NX 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.
+&nbsp;&nbsp;&nbsp;&nbsp; In order to configure FC Target, kernel module parameter qlini_mode should be set to “exclusive” (in some early beta versions of NX up25 qlini_mode was set up to “enabled”). In order to verify the value of this parameter open NX 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”.
@@ Line 513: / Line 461: @@
 === In case of large number of disks, zpool move can take a long time ===

Ma-W at 13:19, 10 January 2024

2024-01-10T13:19:17Z

Ma-W: Ma-W moved page Scale Logic NX2 ver.1.0 up29r2 Release Notes to Scale Logic NX ver.1.0 up29r2 Release Notes

2024-01-10T13:18:10Z

Ma-W moved page Scale Logic NX2 ver.1.0 up29r2 Release Notes to Scale Logic NX ver.1.0 up29r2 Release Notes

← Older revision	Revision as of 13:18, 10 January 2024
(No difference)

Ma-W: 1 revision

2022-12-14T13:40:05Z

1 revision

← Older revision	Revision as of 13:40, 14 December 2022
(No difference)

migrate>Kr-C at 08:08, 24 November 2022

2022-11-24T08:08:53Z

Show changes

Pa-P: 1 revision

2022-07-08T10:18:54Z

1 revision

← Older revision	Revision as of 10:18, 8 July 2022
(No difference)

Ma-W at 13:29, 6 July 2022

2022-07-06T13:29:16Z

Show changes

Ma-W: 1 revision

2022-06-09T13:55:42Z

1 revision

← Older revision	Revision as of 13:55, 9 June 2022
(No difference)

migrate>Kr-C at 13:09, 13 May 2022

2022-05-13T13:09:13Z

Show changes

← Older revision		Revision as of 13:19, 10 January 2024
Line 327:		Line 327:
	=== ZFS Upgrade ===		=== ZFS Upgrade ===

	For Scale Logic ~~NX2~~ 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.		For Scale Logic NX 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.


Line 333:		Line 333:
	=== Intel® Ethernet Controller XL710 Family ===		=== Intel® Ethernet Controller XL710 Family ===

	In case of using Scale Logic ~~NX2~~ 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.		In case of using Scale Logic NX 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.


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

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


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

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


Line 477:		Line 477:


	=== Different Write Cache default setting for zvols in early beta versions of ~~NX2~~ up25 ===		=== Different Write Cache default setting for zvols in early beta versions of NX up25 ===

	In the early beta versions of ~~NX2~~ up25 the default value of the Write Cache Log bias of zvols was set to “In Pool (Throughput)”. In the final release of ~~NX2~~ 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.		In the early beta versions of NX up25 the default value of the Write Cache Log bias of zvols was set to “In Pool (Throughput)”. In the final release of NX 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.


Line 485:		Line 485:
	=== New default value for qlini_mode parameter for FC kernel module qla2xxx_scst ===		=== 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 ~~NX2~~ up25 qlini_mode was set up to “enabled”). In order to verify the value of this parameter open ~~NX2~~ 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.		In order to configure FC Target, kernel module parameter qlini_mode should be set to “exclusive” (in some early beta versions of NX up25 qlini_mode was set up to “enabled”). In order to verify the value of this parameter open NX 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.


Line 549:		Line 549:
	=== User gets deleted from share access list after changing its username on AD server ===		=== 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 ~~NX2~~ know about it. Using the "Synchronize and update shares configurations" operation on ~~NX2~~ 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.		If the AD user is assigned to a share and later the username is changed we should let NX know about it. Using the "Synchronize and update shares configurations" operation on NX 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.


Line 555:		Line 555:
	=== QLogic 32Gbit FC HBA is no longer supported ===		=== QLogic 32Gbit FC HBA is no longer supported ===

	Starting from ~~NX2~~ up29 we no longer support QLogic 32Gbit FC adapters.		Starting from NX up29 we no longer support QLogic 32Gbit FC adapters.

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

	Starting from ~~NX2~~ 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.		Starting from NX 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 ===		=== E-mail password cannot contain special non-ASCII characters ===
Line 585:		Line 585:
	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.		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 ~~NX2~~ ===		=== Runtime UPS calibration in the client-server configuration unexpectedly shutdowns NX ===

	In the client-server configuration of the UPS, the runtime UPS calibration process returns an improper value interpreted by ~~NX2~~ as being on battery. When it timeouts it shuts the system down.		In the client-server configuration of the UPS, the runtime UPS calibration process returns an improper value interpreted by NX 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 ===		=== 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 ===
Line 601:		Line 601:
	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.		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 ~~NX2~~ up29 write back cache on some hardware RAID volumes can be unintentionally disabled ===		=== After update to NX up29 write back cache on some hardware RAID volumes can be unintentionally disabled ===

	Starting from ~~NX2~~ 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.		Starting from NX 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 ===		=== 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 ~~NX2~~ 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.		If write-back cache is enabled on disks in JBOD then restarting or disconnecting JBOD can lead to data inconsistency. Starting from NX 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 ===		=== Snapshots are not displayed after a system reboot if there are more than a few thousands of snapshots ===
Line 629:		Line 629:
	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.		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 ~~NX2~~ up29r2. ===		=== Low performance on remote disks in case of new installation of NX up29r2. ===

	The source for this problem is the zfs_vdev_max_active parameter set to 1 on a new installation of ~~NX2~~ 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 ~~NX2~~ 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 ~~NX2~~. This should be done by selecting the Reboot option in the TUI.		The source for this problem is the zfs_vdev_max_active parameter set to 1 on a new installation of NX 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 NX 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 NX. This should be done by selecting the Reboot option in the TUI.

	[[Category:Release Notes]]		[[Category:Release Notes]]