Log in

Sangfor Support Center

Table of Contents
< All Topics
Print

【VDI】VMP SSD Firmware Remediation Guide_V5.5.0EN-5.5.6EN

Posted
Updated
Byhuijun.chan@sangfor.com
Views4

Issue and Impact

SSD firmware bugs causing IO Latency.

  • Issue 1: Intel S4510 S4610.

    In FW versions XCV10132 and XCV10140, CI053 command timeout and command interruption may occur under certain business scenarios due to the Counter, resulting in SSD IO timeout.

  • Issue 2: Samsung PM897.

    In FW version JXTE004Q, there are flaws in handling reading interference. In certain business scenarios, serious reading interference problems occur in the SSD quickly, resulting in data anomalies and IO latency when reading the SSD. In severe cases, data errors may occur and lead to data loss.

  • Issue 3: SSD FW abnormalities resulting in data errors.

    Products need to fix such abnormal data to avoid data loss. Therefore, the patches to fix the data are merged into the current product’s patches. Apply these patches to concurrently fix other common product issues to prevent customers from encountering other defects.

Note:
This solution only applies to aServer and VDS. For third-party services, customers need to contact the respective vendor.

Issue Confirmation

VMP

Install the patch based on the name list provided by Ryan.

Remediation

Remediation for VMP

VMP Patch information:

Patch type VMP version Name Note
Firmware patch 5.5.0EN aDesksp-ssd_fw_upgrade-550-556R1(20240130).pkg Time needed:
Each SSD firmware upgrade takes about 1 minute. The total time required is the sum of (the number of SSDs needing upgrade on each host * 1 minute). For example, in a typical cluster of 3 hosts with 24 SSDs awaiting an upgrade, the estimated upgrade time would be around 24 minutes.
Impacts:
IO delays of 0 to 13 seconds: Upgrades must be coordinated during periods of low IO activity or arrange business downtimes.
If it is a Single-node scenario, a business downtime must be arranged.
Firmware patch 5.5.0R1EN aDesksp-ssd_fw_upgrade-550-556R1(20240130).pkg Time needed:
Each SSD firmware upgrade takes about 1 minute. The total time required is the sum of (the number of SSDs needing upgrade on each host * 1 minute). For example, in a typical cluster of 3 hosts with 24 SSDs awaiting an upgrade, the estimated upgrade time would be around 24 minutes.
Impacts:
IO delays of 0 to 13 seconds: Upgrades must be coordinated during periods of low IO activity or arrange business downtimes.
If it is a Single-node scenario, a business downtime must be arranged.
Firmware patch 5.5.3.R2EN aDesksp-ssd_fw_upgrade-550-556R1(20240130).pkg Time needed:
Each SSD firmware upgrade takes about 1 minute. The total time required is the sum of (the number of SSDs needing upgrade on each host * 1 minute). For example, in a typical cluster of 3 hosts with 24 SSDs awaiting an upgrade, the estimated upgrade time would be around 24 minutes.
Impacts:
IO delays of 0 to 13 seconds: Upgrades must be coordinated during periods of low IO activity or arrange business downtimes.
If it is a Single-node scenario, a business downtime must be arranged.
Firmware patch 5.5.6EN aDesksp-ssd_fw_upgrade-550-556R1(20240130).pkg Time needed:
Each SSD firmware upgrade takes about 1 minute. The total time required is the sum of (the number of SSDs needing upgrade on each host * 1 minute). For example, in a typical cluster of 3 hosts with 24 SSDs awaiting an upgrade, the estimated upgrade time would be around 24 minutes.
Impacts:
IO delays of 0 to 13 seconds: Upgrades must be coordinated during periods of low IO activity or arrange business downtimes.
If it is a Single-node scenario, a business downtime must be arranged.