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

Ma-W at 15:32, 25 April 2024

2024-04-25T15:32:47Z

Ma-W: 1 revision

2024-04-25T14:58:02Z

1 revision

← Older revision	Revision as of 14:58, 25 April 2024
(No difference)

migrate>Kr-C at 09:20, 20 March 2024

2024-03-20T09:20:18Z

← Older revision		Revision as of 09:20, 20 March 2024
Line 234:		Line 234:

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



Line 268:		Line 267:

	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.		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 298:		Line 298:

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



Line 304:		Line 305:

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



Line 352:		Line 354:

	In certain environments in case of large number of disks (about 100 and more) the zpool move operation 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.


Line 380:		Line 376:

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

			Our HCL is available at this link: [https://www.scalelogicinc.com/support/hardware-compatibility-list/Scale Logic-NX-dss/ https://www.scalelogicinc.com/support/hardware-compatibility-list/Scale Logic-NX-dss/]

	=== E-mail password cannot contain special non-ASCII characters ===		=== E-mail password cannot contain special non-ASCII characters ===
Line 452:		Line 450:

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


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

	The SED functionality in Scale Logic NX enables to use the drives with verified SED configuration only.		The SED functionality in Scale Logic NX enables to use the drives with verified SED configuration only - they are tagged as "SED" and listed on the Scale Logic NX HCL. In order to properly configure the functionality, please follow the steps described in the Knowledge Base article: [https://kb.scalelogicinc.com/NX-sed-support-in-NX_3381.html https://kb.scalelogicinc.com/NX-sed-support-in-NX_3381.html]

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

	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.		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 ([https://www.scalelogicinc.com/support/hardware-compatibility-list/Scale Logic-NX-dss/ https://www.scalelogicinc.com/support/hardware-compatibility-list/Scale Logic-NX-dss/]). To find devices for which we support the SED functionality, on the Scale Logic HCL page in the form: "Search by component", enter: “SED” in the keyword field and click the search button (loupe icon).

	=== Enabling the autotrim functionality in the zpools may cause drastic increase load or iowait in the system. ===		=== Enabling the autotrim functionality in the zpools may cause drastic increase load or iowait in the system. ===
Line 520:		Line 519:
	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 NX (the network interface is usually: eth0).		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 NX (the network interface is usually: eth0).

	=== <!-- #~~JBmail 31.10.2023 g. 17:29~~ -->~~Sometimes a web browser may display a blank help page~~. ===		=== <!-- #116234 -->Identification LED blinking does not work on NVMe drives in AMD-based servers. ===

	~~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~~.		The Identification LED blinking on NVMe drives does not work on servers based on AMD processors. This problem will be solved in future releases.

	=== <!-- #~~116234~~ -->~~Identification LED blinking~~ does not ~~work on NVMe drives in AMD-based servers~~. ===		=== <!-- #115416 -->The SED configuration tool available in TUI does not lists devices when using the Broadcom 9600 Storage Adapter. ===

	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.

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

Ma-W: Created page with "'''Release date: 2023-12-22''' '''Build: 54118''' '''Important!''' To upgrade the product, you need to have an active Te..."

2024-01-15T07:49:18Z

Created page with "'''Release date: 2023-12-22''' '''Build: 54118''' <span style="color:#cc0033">'''Important!''' </span>To upgrade the product, you need to have an active Te..."

Show changes

← Older revision		Revision as of 15:32, 25 April 2024
Line 234:		Line 234:

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



Line 267:		Line 268:

	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.		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 298:		Line 300:

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



Line 305:		Line 308:

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



Line 450:		Line 454:

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



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

	The SED functionality in Scale Logic NX enables to use the drives with verified SED configuration only ~~- they are tagged as "SED" and listed on the Scale Logic NX HCL~~. In order to properly configure the functionality, please follow the steps described in the Knowledge Base article: [https://kb.scalelogicinc.com/NX-sed-support-in-NX_3381.html https://kb.scalelogicinc.com/NX-sed-support-in-NX_3381.html]		The SED functionality in Scale Logic NX 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. ===

	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 ([https://www.scalelogicinc.com/support/hardware-compatibility-list/Scale Logic-NX-dss/ https://www.scalelogicinc.com/support/hardware-compatibility-list/Scale Logic-NX-dss/]). To find devices for which we support the SED functionality, on the Scale Logic HCL page in the form: "Search by component", enter: “SED” in the keyword field and click the search button (loupe icon).		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. ===		=== Enabling the autotrim functionality in the zpools may cause drastic increase load or iowait in the system. ===