Storage System - Revision history

Qadmin: Link Audit Log Analyzer to the Audit Logging page

2026-09-28T20:46:13Z

Link Audit Log Analyzer to the Audit Logging page

← Older revision		Revision as of 20:46, 28 September 2026
Line 45:		Line 45:
	\| '''Network Connectivity/Ping Checker''' \|\| Tests reachability from this system, useful when diagnosing grid or replication problems.		\| '''Network Connectivity/Ping Checker''' \|\| Tests reachability from this system, useful when diagnosing grid or replication problems.
	\|-		\|-
	\| '''Audit Log Analyzer''' \|\| Browse and search the management audit log. See [[~~Call-home / Alerting#Audit Logging\|~~Audit Logging]].		\| '''Audit Log Analyzer''' \|\| Browse and search the management audit log. See [[Audit Logging]].
	\|-		\|-
	\| '''Send Log Report''' \|\| Send support logs to OSNEXUS.		\| '''Send Log Report''' \|\| Send support logs to OSNEXUS.

Qadmin: Note the grid-wide NTP equivalent and that the time zone is set only from the grid dialog (QSTOR-12352)

2026-09-04T04:39:37Z

Note the grid-wide NTP equivalent and that the time zone is set only from the grid dialog (QSTOR-12352)

← Older revision		Revision as of 04:39, 4 September 2026
Line 101:		Line 101:

	Accurate time is a prerequisite, not a nicety. Kerberos authentication against Active Directory fails outside a small clock skew, TLS certificate validation depends on the clock, and correlating alerts or audit logs across a grid is impractical when nodes disagree about the time. When joining systems to an AD domain, point NTP at the domain controllers.		Accurate time is a prerequisite, not a nicety. Kerberos authentication against Active Directory fails outside a small clock skew, TLS certificate validation depends on the clock, and correlating alerts or audit logs across a grid is impractical when nodes disagree about the time. When joining systems to an AD domain, point NTP at the domain controllers.

			'''This tab sets NTP for this system only.''' The grid-wide equivalent is '''[[Grid Configuration#Modify Grid Network Settings\|Modify Grid Network Settings]]''', which replaces the NTP server list on every system you tick.

			'''The time zone is not set here.''' There is no time zone field on this dialog: the only place to set it is '''[[Grid Configuration#Modify Grid Time Zone Settings\|Modify Grid Time Zone Settings]]''', which is a grid-scope dialog with a per-system tick list, so setting the zone on one system means ticking only that system.

	=== Network Settings ===		=== Network Settings ===

Qadmin: Note the grid-wide equivalent and its replace semantics (QSTOR-12352)

2026-09-04T04:39:04Z

Note the grid-wide equivalent and its replace semantics (QSTOR-12352)

← Older revision		Revision as of 04:39, 4 September 2026
Line 91:		Line 91:

	Working DNS matters more than it first appears: Active Directory (AD) integration, LDAP single sign-on, ITSM webhook delivery and license activation all depend on name resolution. If you plan to join your QuantaStor systems to your AD domain then it is important to set the DNS server to your AD domain controller IP address.		Working DNS matters more than it first appears: Active Directory (AD) integration, LDAP single sign-on, ITSM webhook delivery and license activation all depend on name resolution. If you plan to join your QuantaStor systems to your AD domain then it is important to set the DNS server to your AD domain controller IP address.

			'''This tab sets DNS for this system only.''' To give several grid members the same resolvers and search domain in one operation, use '''[[Grid Configuration#Modify Grid Network Settings\|Modify Grid Network Settings]]''' instead -- but note that it '''replaces''' the DNS servers and search suffix on every system you tick, so anything set here on a ticked system is discarded.

	=== NTP Servers ===		=== NTP Servers ===

Qadmin: /* Network Port Naming Convention */

2026-09-03T23:16:29Z

Network Port Naming Convention

← Older revision		Revision as of 23:16, 3 September 2026
Line 128:		Line 128:
	==== Network Port Naming Convention ====		==== Network Port Naming Convention ====

	Chooses between '''Predictable''' interface naming ({{Code\|1=ensN}}, {{Code\|1=enoN}}, {{Code\|1=enpN}}) and legacy '''Unified''' naming ({{Code\|1=ethN}}).		Chooses between '''Predictable''' interface naming ({{Code\|1=ensN}}, {{Code\|1=enoN}}, {{Code\|1=enpN}}) and legacy '''Unified''' naming ({{Code\|1=ethN}}). Changing this renames interfaces, so treat it as a maintenance-window operation.

	Changing this renames interfaces, so treat it as a maintenance-window operation.

	==== FC WWN & Device Emulation Mode ====		==== FC WWN & Device Emulation Mode ====

Qadmin: /* Network Port Naming Convention */

2026-09-03T23:16:11Z

Network Port Naming Convention

← Older revision		Revision as of 23:16, 3 September 2026
Line 128:		Line 128:
	==== Network Port Naming Convention ====		==== Network Port Naming Convention ====

	Chooses between '''Predictable''' interface naming ({{Code\|1=ensN}}, {{Code\|1=enoN}}, {{Code\|1=enpN}}) and '''Unified''' naming ({{Code\|1=ethN}}).		Chooses between '''Predictable''' interface naming ({{Code\|1=ensN}}, {{Code\|1=enoN}}, {{Code\|1=enpN}}) and legacy '''Unified''' naming ({{Code\|1=ethN}}).

	'''Unified is the preferred mode for QuantaStor''', because it produces consistent names across systems, which highly available cluster VIF management depends on. '''No change''' leaves the current convention alone.

	Changing this renames interfaces, so treat it as a maintenance-window operation.		Changing this renames interfaces, so treat it as a maintenance-window operation.

Qadmin: /* DNS Servers */

2026-09-03T23:14:03Z

DNS Servers

← Older revision		Revision as of 23:14, 3 September 2026
Line 90:		Line 90:
	* '''IP Address''' with '''Add''' and '''Remove''' -- the DNS servers themselves. Add your local DNS servers, or a public resolver such as {{Code\|1=8.8.8.8}} where no local one exists.		* '''IP Address''' with '''Add''' and '''Remove''' -- the DNS servers themselves. Add your local DNS servers, or a public resolver such as {{Code\|1=8.8.8.8}} where no local one exists.

	Working DNS matters more than it first appears: Active Directory (AD) integration, LDAP single sign-on, ITSM webhook delivery and license activation all depend on name resolution. If you plan to join your QuantaStor systems to your AD domain then it is important to set the DNS server to your AD ~~server~~ IP address.		Working DNS matters more than it first appears: Active Directory (AD) integration, LDAP single sign-on, ITSM webhook delivery and license activation all depend on name resolution. If you plan to join your QuantaStor systems to your AD domain then it is important to set the DNS server to your AD domain controller IP address.

	=== NTP Servers ===		=== NTP Servers ===

Qadmin: /* DNS Servers */

2026-09-03T23:13:37Z

DNS Servers

← Older revision		Revision as of 23:13, 3 September 2026
Line 90:		Line 90:
	* '''IP Address''' with '''Add''' and '''Remove''' -- the DNS servers themselves. Add your local DNS servers, or a public resolver such as {{Code\|1=8.8.8.8}} where no local one exists.		* '''IP Address''' with '''Add''' and '''Remove''' -- the DNS servers themselves. Add your local DNS servers, or a public resolver such as {{Code\|1=8.8.8.8}} where no local one exists.

	Working DNS matters more than it first appears: Active Directory (AD) integration, LDAP single sign-on, ITSM webhook delivery and license activation all depend on name resolution. If you plan to join your QuantaStor systems to your AD domain then it is important to set the DNS server to your AD server.		Working DNS matters more than it first appears: Active Directory (AD) integration, LDAP single sign-on, ITSM webhook delivery and license activation all depend on name resolution. If you plan to join your QuantaStor systems to your AD domain then it is important to set the DNS server to your AD server IP address.

	=== NTP Servers ===		=== NTP Servers ===

Qadmin: /* DNS Servers */

2026-09-03T23:13:18Z

DNS Servers

← Older revision		Revision as of 23:13, 3 September 2026
Line 90:		Line 90:
	* '''IP Address''' with '''Add''' and '''Remove''' -- the DNS servers themselves. Add your local DNS servers, or a public resolver such as {{Code\|1=8.8.8.8}} where no local one exists.		* '''IP Address''' with '''Add''' and '''Remove''' -- the DNS servers themselves. Add your local DNS servers, or a public resolver such as {{Code\|1=8.8.8.8}} where no local one exists.

	Working DNS matters more than it first appears: Active Directory integration, LDAP single sign-on, ITSM webhook delivery and license activation all depend on name resolution.		Working DNS matters more than it first appears: Active Directory (AD) integration, LDAP single sign-on, ITSM webhook delivery and license activation all depend on name resolution. If you plan to join your QuantaStor systems to your AD domain then it is important to set the DNS server to your AD server.

	=== NTP Servers ===		=== NTP Servers ===

Qadmin: /* General Settings */

2026-09-03T23:11:34Z

General Settings

← Older revision		Revision as of 23:11, 3 September 2026
Line 79:		Line 79:
	* '''Zero-touch Maintenance''' -- allows routine maintenance actions (selecting unused media to be used as hot-spares) to proceed without an administrator confirming each one.		* '''Zero-touch Maintenance''' -- allows routine maintenance actions (selecting unused media to be used as hot-spares) to proceed without an administrator confirming each one.
	* '''Log Collection Mode''' -- how often logs are gathered for support purposes. '''Never''' disables automatic collection; logs can still be sent on demand with '''Send Log Report'''.		* '''Log Collection Mode''' -- how often logs are gathered for support purposes. '''Never''' disables automatic collection; logs can still be sent on demand with '''Send Log Report'''.
	* '''Vendor''' and '''Server Layouts''' -- identify the underlying hardware so QuantaStor can apply the correct enclosure layout and disk slot mapping. These are detected automatically; change them only when the detection is wrong for your chassis. The recognised vendor logo is shown beneath, which is a quick confirmation the system identified the platform correctly.		* '''Vendor''' and '''Server Layouts''' -- identify the underlying hardware so QuantaStor can apply the correct enclosure layout and disk slot mapping. These are detected automatically; change them only when the detection is wrong for your chassis. The recognised chassis front bezel or hypervisor vendor logo is shown beneath, which is a quick confirmation the system identified the platform correctly.

	=== DNS Servers ===		=== DNS Servers ===

Qadmin: /* General Settings */

2026-09-03T23:10:43Z

General Settings

← Older revision		Revision as of 23:10, 3 September 2026
Line 77:		Line 77:
	* '''I/O Fencing''' -- controls I/O fencing for high-availability configurations, which prevents a failed node from writing to shared storage after a failover. Leave this '''Enabled''' on any HA deployment.		* '''I/O Fencing''' -- controls I/O fencing for high-availability configurations, which prevents a failed node from writing to shared storage after a failover. Leave this '''Enabled''' on any HA deployment.
	* '''Telemetry''' -- controls whether the system sends anonymous telemetry to OSNEXUS.		* '''Telemetry''' -- controls whether the system sends anonymous telemetry to OSNEXUS.
	* '''Zero-touch Maintenance''' -- allows routine maintenance actions to proceed without an administrator confirming each one.		* '''Zero-touch Maintenance''' -- allows routine maintenance actions (selecting unused media to be used as hot-spares) to proceed without an administrator confirming each one.
	* '''Log Collection Mode''' -- how often logs are gathered for support purposes. '''Never''' disables automatic collection; logs can still be sent on demand with '''Send Log Report'''.		* '''Log Collection Mode''' -- how often logs are gathered for support purposes. '''Never''' disables automatic collection; logs can still be sent on demand with '''Send Log Report'''.
	* '''Vendor''' and '''Server Layouts''' -- identify the underlying hardware so QuantaStor can apply the correct enclosure layout and disk slot mapping. These are detected automatically; change them only when the detection is wrong for your chassis. The recognised vendor logo is shown beneath, which is a quick confirmation the system identified the platform correctly.		* '''Vendor''' and '''Server Layouts''' -- identify the underlying hardware so QuantaStor can apply the correct enclosure layout and disk slot mapping. These are detected automatically; change them only when the detection is wrong for your chassis. The recognised vendor logo is shown beneath, which is a quick confirmation the system identified the platform correctly.