Applies to: QSM 4 and XEVO 3 #

How to troubleshoot unstable network connections? #

If you experience intermittent network connectivity, check the storage system’s firmware version and uptime. If the system is running an older firmware version and has been operating continuously for more than 1,000 days, a firmware update and cold reboot may help resolve the issue.

Schedule a maintenance window, upgrade to the recommended firmware version for your model, and perform a cold reboot by fully shutting down and then powering on the system. Afterward, monitor network connectivity to determine whether the issue recurs.

How to configure VLAN isolation without VLAN tagging on the host or storage system? #

You can separate network traffic by configuring VLANs on the switch, even when the host and storage interfaces send untagged traffic.

1. Configure the switch ports connected to the host and storage system as access ports, or their equivalent, in the intended VLAN.
2. Ensure that each port’s PVID and untagged VLAN membership match the intended VLAN. Devices that need to communicate directly should belong to the same VLAN.
3. Where configurable, enable ingress filtering to reject traffic assigned to VLANs that are not permitted on the receiving port. Ensure that the port accepts untagged traffic from the connected device.
4. To isolate different VLANs, ensure that inter-VLAN routing is disabled or restricted by appropriate access control or firewall rules.

An unsuccessful ping alone does not confirm network isolation. Verify both the intended connectivity within each VLAN and the access restrictions between VLANs.

Configuration options vary by switch model. Refer to your switch vendor’s documentation for detailed instructions.

How to troubleshoot Wake-on-LAN issues? #

If Wake-on-LAN (WoL) is not working, check whether the storage system is connected through a network switch. Record the switch manufacturer and model, and review its configuration for any settings that may prevent WoL packets from reaching the storage system.

External Connections and Web Finder Functions #

If it is found that the NAS is initiating a connection to the external IP 166.62.94.122, and there is no record of the source port in the netstat query within the debug log, it is likely related to the web finder.

What to do if the system configuration is lost after drives in slots 1-4 fail? #

If all drives in slots 1-4 fail, the system configuration may be lost, and you may be unable to sign in to the management interface using your existing administrator account.

To restore access, follow these steps:

1. Power off the storage system.
2. Insert at least one new drive into an available drive slot within slots 1-4.
3. Power on the storage system.
4. After startup, sign in to the management interface using the default credentials: username admin and password 1234.
5. If you have previously exported a system configuration backup, import it to restore the system settings.

Note: Without a previously exported configuration backup, the original settings can’t be restored automatically. Restoring the system configuration does not restore user data or resolve storage pool failures.

Applies to: QSM 4 #

How long does SMB reconnection take during cluster IP failover in QSM 4? #

With a cluster IP configured, SMB reconnection times vary depending on the event. The following results were observed in testing:

During sequential controller reboots, the overall interruption includes the time required for the controllers to restart. In the tested scenario, failover itself took approximately 60 seconds. SMB connectivity was briefly restored after failover, then interrupted again when the next controller restarted.

Schedule a maintenance window for sequential controller reboots. Actual reconnection times may vary depending on the system configuration, client behavior, and operating conditions.

Why is the system name limited to 15 characters in QSM 4? #

QSM 4 limits system names to 15 characters to maintain compatibility with Windows NetBIOS naming conventions. This helps prevent name resolution and shared folder access issues in Windows environments. The limit is fixed and cannot be changed.

How to troubleshoot missing system settings after removing drives in QSM 4? #

QSM 4 stores system configuration information on designated drives. Removing all drives containing this information may cause system settings to become unavailable or lead to abnormal system behavior.

If you encounter this issue after removing drives, contact QSAN Support and provide the storage model, firmware version, the original slot locations of the removed drives, and system debug logs, if available. These details can help the support team investigate the issue.

How to download debug logs via SSH #

Applies to: Dual-controller systems running QSM 4.2.0 or later.

Before you begin, ensure that OpenSSH Client is installed and SSH access to the storage system is enabled. Use root as the SSH username and the same password as the admin account. If you need assistance with SSH access, contact QSAN Support.

1. Open PowerShell and run the following commands to create a folder for the debug logs and navigate to it:

New-Item -ItemType Directory -Force -Path "$HOME\Downloads\QSAN-Debug"
Set-Location "$HOME\Downloads\QSAN-Debug"

2. Replace NAS_IP in the commands below with the storage system’s IP address. Run the following command to generate the diagnostic report. Enter the SSH password when prompted and wait for the command to finish:

ssh root@NAS_IP "diagnosis_report.sh"

3. Download the generated report to the current folder. Enter the SSH password again if prompted:

scp -O root@NAS_IP:/tmp/debug_info.zip .

4. Locate debug_info.zip in the Downloads\QSAN-Debug folder and provide it to QSAN Support.