Ma-W at 13:56, 12 January 2024

2024-01-12T13:56:15Z

Ma-W at 13:29, 10 January 2024

2024-01-10T13:29:07Z

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

2024-01-10T13:26:05Z

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

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

Pa-P: 1 revision

2022-03-07T09:05:45Z

1 revision

← Older revision	Revision as of 09:05, 7 March 2022
(No difference)

Ma-W: Created page with "'''Release date:''' '''Build:''' {| class="cke_show_border cke_show_border" |- | TOC |} == Fixed == === Unexpected system reboot via system watchdog while space rec..."

2020-09-23T11:43:06Z

Created page with "'''Release date:''' '''Build:''' {| class="cke_show_border cke_show_border" |- | __TOC__ |} == Fixed == === Unexpected system reboot via system watchdog while space rec..."

@@ Line 1: / Line 1: @@
-'''Release date: 2020-04-16'''
+'''Release date:'''
-'''Build: 38496'''
+'''Build:'''
 {| class="cke_show_border cke_show_border"
@@ Line 17: / Line 17: @@
 === Ultra-slow scrub or resilver on some HDD pools and especially on SSD pools ===
 == Performance tuning ==

Ma-D at 14:24, 22 May 2020

2020-05-22T14:24:22Z

Show changes

← Older revision		Revision as of 13:29, 10 January 2024
Line 205:		Line 205:
	=== 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 211:		Line 211:
	=== 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 297:		Line 297:
	=== 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 315:		Line 315:
	=== 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 361:		Line 361:
	=== Wrong state of storage devices in VMware after power cycle of both nodes in HA FC Target ===		=== 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 ~~NX2’s~~ GUI. Refresh vSphere’s Adapters and Devices tab afterwards.		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 NX’s GUI. Refresh vSphere’s Adapters and Devices tab afterwards.


Line 371:		Line 371:


	=== Separated mode after update from ~~NX2~~ up24 to ~~NX2~~ up25 ===		=== Separated mode after update from NX up24 to NX up25 ===

	In HA cluster environment after updating of one node from ~~NX2~~ up24 to ~~NX2~~ 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.		In HA cluster environment after updating of one node from NX up24 to NX 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 ~~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 391:		Line 391:
	=== 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 413:		Line 413:


	=== Updating nodes of the ~~NX2~~ cluster from up24 and earlier versions changes FC ports to target mode resulting in losing connection to a storage connected via FC initiator ===		=== Updating nodes of the NX 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.		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.
Line 419:		Line 419:


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

	The process of updating of Metro Cluster node from ~~NX2~~ 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.		The process of updating of Metro Cluster node from NX 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.