Dell PowerFlex 4.0.x Release Notes
Known issues and limitations from PowerFlex 3.6.x.x
The following table lists known issues and limitations that exist in the PowerFlex 3.6.x.x releases that also apply to this release.
NOTE:If an issue was reported by customers, the customers' Service Request numbers appear in the "Issue number & SR number" column, and serve to correlate between customer-reported issues and the
issue number.
The following table lists known issues and limitations for PowerFlex Custom Node.
| Issue number & SR number | Problem summary | Workaround |
|---|---|---|
| SCI-62961 | Disk slot information for PowerEdge nodes introduced in PowerFlex 3.6 does not work on R650/R6525/R750 nodes with HBA355. | Use iDRAC or perccli to get the disk slot information. |
The following table lists known issues and limitations for the PowerFlex Gateway.
| Issue number & SR number | Problem summary | Workaround |
|---|---|---|
| SCI-57304 |
PowerFlex Installer (also known as the PowerFlex Gateway) is exposed to issue HSTS Missing From HTTPS Server, CVE: https://nvd.nist.gov/vuln/detail/CVE-2017-7789 |
None |
| SCI-55819 | During NDU to v3.5.1.x, in rare cases, the PowerFlex Gateway might have high CPU usage and get stuck at the upload phase. | Perform a restart of the gateway service using an SSH session to the PowerFlex Gateway:
service scaleio-gateway restart Then, in the PowerFlex Installer user interface, click Retry to continue the upgrade. |
The following table lists known issues and limitations for the SDC.
| Issue number & SR number | Problem summary | Workaround |
|---|---|---|
| SCI-57752 |
The SDC rpm package for SLES15.X installs without any issues. However, after installation, when checking if the SDC driver's scini service is loaded, the following confusing state is returned: service scini status service: no such service scini This is a false positive status alert. |
None |
The following table lists known issues and limitations for the SDR.
| Issue number & SR number | Problem summary | Workaround |
|---|---|---|
| SCI-62047 | A replication failover on an RCG that is still in the initial copy phase may not present all volume members at the remote target location. | Wait for all volumes in the RCG to complete their initial copy phase before performing the failover operation for that RCG. |
The following table lists known issues and limitations for the SDS.
| Issue number & SR number | Problem summary | Workaround |
|---|---|---|
| SCI-63216 | When adding NVMe devices using the by-id path similar to the following: dev/disk/by-id/nvme-Dell_Express_Flash_NVMe_ P4610_1.6TB_SFF_BTLN950106ZB1P6AGN
the MDM blocks the addition due to the error: new_device_path too long, MDM supports up to 63 characters. |
Use the alternative name path in by-id location with nvme-eui in the path. For example:
/dev/disk/by-id/nvme-eui.01000000010000005cd2e448b0b75151 |
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\