Pa-P: 1 revision

2021-12-03T13:26:37Z

1 revision

← Older revision	Revision as of 13:26, 3 December 2021
(No difference)

Ma-W: Created page with "'''Release date: 2020-04-16''' '''Build: 38496''' {| class="cke_show_border cke_show_border" |- | TOC |} == Fixed == === Unexpected system reboot via system watchdo..."

2020-09-23T11:47:29Z

Created page with "'''Release date: 2020-04-16''' '''Build: 38496''' {| class="cke_show_border cke_show_border" |- | __TOC__ |} == Fixed == === Unexpected system reboot via system watchdo..."

← Older revision		Revision as of 11:47, 23 September 2020
Line 42:		Line 42:

	=== When using certain Broadcom (previously LSI) SAS HBA controllers with SAS MPIO, Broadcom recommends to install specific firmware from Broadcom SAS vendor. ===		=== 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 ==		== Performance tuning ==

Line 405:		Line 405:
	=== Different Write Cache default setting for zvols in early beta versions of ZX up25 ===		=== 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.		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 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 417:		Line 417:
	=== 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 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.		In order to configure FC Target, kernel module parameter qlini_mode should be set to “exclusive” (in some early beta versions of up25 qlini_mode was set up to “enabled”). In order to verify the value of this parameter open 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 439:		Line 439:


	=== 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 ===		=== Updating nodes of the 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.

Ma-D at 14:24, 22 May 2020

2020-05-22T14:24:22Z

Show changes

Scale Logic ZX ver.1.0 up28r2 Release Notes - Revision history

Pa-P: 1 revision

Ma-W: Created page with "'''Release date: 2020-04-16''' '''Build: 38496''' {| class="cke_show_border cke_show_border" |- | __TOC__ |} == Fixed == === Unexpected system reboot via system watchdo..."

Ma-D at 14:24, 22 May 2020

Ma-W: Created page with "'''Release date: 2020-04-16''' '''Build: 38496''' {| class="cke_show_border cke_show_border" |- | TOC |} == Fixed == === Unexpected system reboot via system watchdo..."