DELL 361 Power Flex Release Instruction Manual

June 14, 2024
Dell

DELL LOGO

361 Power Flex Release
Instruction Manual

361 Power Flex Release

Dell Power Flex 3.6.1 Release Notes
3.6.1 Power Flex 3.6.1
Rev. 01 April 2023
These release notes contain supplemental information about this release.

Revision history

Revision history for PowerFlex3.6.1 release notes
Table 1. PowerFlex3.6.1 release notes revision history

Revision Date Description
01 April 28, 2023 Release of Power Flex 3.6.1

Product description

Power Flex is a software-defined storage platform designed to significantly reduce operational and infrastructure complexity.
It empowers organizations to move faster by delivering flexibility, elasticity, and simplicity with predictable performance and resiliency at scale.
The Power Flex family provides a foundation that combines compute as well as high performance storage resources in a managed unified fabric. Power Flex comes in fully managed flexible deployment options for rack or appliance that enable Server SAN, HCI, and storage only architectures. Power Flex can now be deployed in the public cloud. A Ready Node option is also available. Power Flex is ideal for high performance applications and databases, building an open  private cloud, or consolidating resources in heterogeneous environments.

New and changed features

Learn about new and changed features in this version of Power Flex.

New features for Power Flex

Learn about the new features introduced in Power Flex 3.6.1 software.

  • Power Flex is now available as a consumption model in the public cloud. Power Flex 3.6.0.4 is supported on AWS.

  • Power Path 7.4 for Linux now supports Power Flex devices. Power Path Migration enabler can be used for data migration across Power Flex and other Power Path supported storage array classes.
    NOTE: Only Power Flex SCSI devices are supported. Since Power Flex devices have only a single path, Power Flex takes care of load balancing across different SDS.

  • A new alert, S D S E X C E E D E D I M M _ T I M E O U T, is displayed if S D S n a m e < N A M E > S D S I d < n n n > is running with Instant Maintenance Mode (IMM), exceeding the configured duration. It places the system at risk for a second failure of another node and might lead to data unavailability.

Important
The following aspects of PowerFlex 3.6.1 must be understood before deploying or upgrading your system:

  1. CloudIQ integration
    ● Discovering a PowerFlex system in CloudIQ requires the system to be registered with Secure remote services. In the PowerFlex Installer, Maintain tab, ensure that the PowerFlex system is registered with Secure remote services  and that Send data to CloudIQ is enabled.
    ● After installing a new PowerFlex system with PowerFlex version 3.6, it takes 24 hours until data is available in CloudIQ. Systems upgrading to PowerFlex 3.6 will appear in CloudIQ within an hour of enabling the Send data to CloudIQ option.
    ● PowerFlex appliance and rack systems need PowerFlex Manager version “H” in order to be discovered in CloudIQ.

  2. Replication enhancements
    ● Bi-directional replication between two sites only is supported.
    ● See the PowerFlex Sizer for sizing guidelines for correct replication system specifications, including WAN bandwidth sizing. When using the PowerFlex Sizer, take into account existing workload and existing hardware, and the  possible need to add additional nodes to enable replication without impacting the current workload.
    ● Replication capability has higher I/O overhead, as explained in the v3.6 Getting to Know PowerFlex Guide (Replication section) and the white paper Dell EMC PowerFlex: Introduction to Replication. See these recommendations  in order to size your system correctly, and ensure that you have sufficient existing storage capabilities to enable this ability.

  3. Network resiliency improvements
    ● Proactive network path error detection requires SDC to be at v3.6 or later.

  4. Upgrade Paths
    ● Upgrade from PowerFlex version 3.0.x and 3.5.x to version 3.6 are supported.
    ● Older PowerFlex/ Flex operating system versions must be upgraded to version 3.0.x prior to upgrading to version 3.6.

  5. vSphere plug-in End-of-Support-Life
    ● The PowerFlex vSphere plug-in continues to be supported with vSphere versions 6.5 and 6.7, however it reaches end-of-support-life when vSphere 6.5 and 6.7 reach end-of-support by VMware. For details on the last release of vSphere plug-in due to end of general support for Essig 6.5 and 6.7 by VMware, see: Announcing End of General Support  for vSphere 6.5.x and vSphere 6.7.x (89305). Also note the new issue in the Known Issues section that is  related to vSphere Plug-in.
    ● The PowerFlex vSphere plug-in does not support vSphere 7 hype converged (HCI) configurations.

Changed features

Learn about the enhanced features for this version of PowerFlex.

Updated operating system support matrix
The following operating systems are added to the support matrix in this release:

  • RHEL 8.7
  • REHL9.1

The operating systems support software only customers for the following components:

  • MDM
  •  SDS
  • SDR
  •  SDC
  • LIA

Further to SDC only, the following operating systems support are being added:

  • Windows 2022
  • vSphere 7.0U3g

For more operating system-related information and supported components, see the PowerFlex simple support matrix: https://elabnavigator.dell.com/elm/modernHomeSSM

Oracle JRE and OpenJDK support

  • Oracle JRE 1.8 build 322
  • OpenJDK JDK 8 build 322.b06
  • OpenJDK 11.0.12.07 (Linux-based servers only)

Support deprecation

Learn about the features that are no longer supported in PowerFlex 3.6.1.
Background scanner events and alerts
Some events and alerts for the background scanner feature were deprecated, and replaced with different ones. See the PowerFlex v3.5.1.2 Release Notes, “Documentation” section, for details.
DAS Cache
DAS Cache is no longer supported for PowerFlex running on any operating systems.
System Analysis Tool
The System Analysis Tool is no longer included in PowerFlex.
AMS
Systems managed by AMS system will not be able to upgrade to PowerFlex v3.5 or later. Prior to performing an upgrade, contact PowerFlex Product Management for possible alternatives.
NOTE: AMS artifacts will be removed from the support site. For guidance, contact PowerFlex Product Management.
VxFlex OS GUI client
The GUI from versions earlier than v3.5 of this product is no longer supported and cannot be upgraded.
From v3.5 and later, a new GUI must be deployed/upgraded instead.
Deprecated operating systems
For the most current information, see the Dell Technologies Simple Support Matrix at https://elabnavigator.dell.com/eln/modernHomeSSM/.

Fixed issues

The following table lists the issues that are fixed in PowerFlex3.6.1.
NOTE: If an issue was reported by customers, the customers’ Service Request numbers appear in the “Issue number & SR number” column, and correlate between customer-reported issues and the PowerFlex issue number.
Table 2. Fixed issues

Issue number & SR number Problem summary
SCI-73072 SDS does not support Red Hat Enterprise Linux version 9.1, Kernel

5.14.0-162.12.1.el9_1.x86_64 and latest.
SCI-72513 SR# 162244192| SDS fails during Tree migration.
SCI-71923 SR# 144327231| The gateway fails to generate a performance bundle for CloudIQ when the system is configured to ESRS and SCSI-3 reservation is set on a volume.
SCI-71797| Insecure HTTP TRACE method is exposed to security vulnerability.
SCI-71795| Inaccessible capacity issues for system during the Instant Maintenance Mode (IMM) or rebuild.
SCI-71793| MDM synchronization fails while upgrading to 3.6.x versions.
SCI-71706| MDM fails when PowerFlex is upgraded to version 3.6.0.4 from version 3.0.0.
Issue number & SR number| Problem summary
---|---
SCI-71387| Lack of secure headers in Apache Tomcat is exposed to CVE-2022-42252. Upgraded the Tomcat to version 8.5.84.
SCI-70943 SR# 153797920| When the trusted CA certificate of the MDM is uploaded, MDM fails on the remote site while using Replication Consistency Groups (RCGs).
SCI-70830 SR# 157797887| Presentation server User Interface does not load when self-signed certificate having multiple Storage Area Network (SAN) extensions exist.
SCI-70585 SR# 156727523| Gateway User Interface fails to load or create lockbox with Java version 1.8.0_351.
SCI-69045| Cookies set without the Same Site attribute result in cross-site request forgery, cross- site script inclusion, and timing attacks. The Same Site attribute must be set to ‘lax’ or ‘strict’ for all cookies.
SCI-68490| System raw capacity is enhanced to 16 PB.

Software packages

Learn about the contents of the PowerFlex 3.6.1 software packages.
Download location
The PowerFlex 3.6.1 complete software package, containing all the packages listed below, can be downloaded from the following
location: https://www.dell.com/support/home/en-us/product- support/product/scaleio/overview
Table 3. Software packages

Package Name Operating System GW MDM SDS SDR SDC LIA Xcache Content
RHEL_OEL7 Red Hat / CentOS / Oracle Linux X X X X X X X Core

components for Red Hat, CentOS and Oracle Linux 7.x. Oracle Linux 7.8 and higher includes KVM.
RHEL8_OEL8| Red Hat / CentOS / Oracle Linux| X| X| X| X| X| X| X| Core components for Red Hat, CentOS and Oracle Linux 8.x. Oracle Linux includes KVM.
RHEL_OEL9| Red Hat / CentOS / Oracle Linux| | X| X| X| X| X| | Core components for Red Hat, CentOS and Oracle Linux 9.x.
CENTOS 7.9| | | | | | | | |
CentOS Stream 8| | X| X| X| X| X| X| X| Core components for CentOS Stream 8
CentOS Stream 9| | | X| X| X| X| X| | Core components for CentOS Stream 9
SLES11.4| SUSE Linux| X| | | | X| | | SDC component for SLES 11 SP4
Package Name| Operating System| GW| MDM| SDS| SDR| SDC| LIA| Xcache| Content
---|---|---|---|---|---|---|---|---|---
SLES12.5| | X| X| X| X| X| X| X| Core components for SLES 12 SP5
SLES15.2| SUSE Linux| X| X| X| X| X| X| X| Core components for SLES 15 SP2
SLES15.3| SUSE Linux| X| X| X| X| X| X| X| Core components for SLES 15 SP3
SLES15.4| SUSE Linux| | X| X| X| X| X| | Core components for SLES 15 SP4
Ubuntu18.04| Ubuntu| X| X| X| X| X| X| X| Core components for Ubuntu 18.04
Ubuntu20.04| Ubuntu| X| X| X| X| X| X| X| Core components for Ubuntu 20.04
Ubuntu22.04| Ubuntu| | X| X| X| X| X| | Core components for Ubuntu 22.04.x LTS
XEN 7.1| XenServer / Citrix Hypervisor| | X| X| X| X| X| | Core components for Citrix XenServer 7.1.2 LTSR
XEN 8.0| | X| X| X| X| | | Core components for Citrix Hypervisor 8.1 and 8.2
Complete_VM wares| vSphere| X| X| X| X| X| | | Contains all PowerFlex, VMware- related software artifacts (OVA file, drvcfg file, SVM patching, SDC package, vSphere plug-in, and VASA provider)
NOTE: PowerFlex vSphere plug-in is not compatible with ESXi 7.0 and later.
Complete Win dowses| Windows Server| X| | | | X| X| | Contains all Microsoft Windows (2012-2019) server related software artifacts, including the gateway and CSV deployment templates
RHEL CoreOS| CoreOS| | | | | X| | | SDC component for RHEL CoreOS
CoreOS| | | | | X| | | SDC component for CoreOS
AIX7.2| AIX| | | | | X| | | SDC component for IBM AIX 7.2
Presentation
Server| | | | | | | | | Contains PowerFlex WEDU server (Linux and Ubuntu)
Package Name| Operating System| GW| MDM| SDS| SDR| SDC| LIA| Xcache| Content
---|---|---|---|---|---|---|---|---|---
Gatewayfor Linux| | X| | | | | | | PowerFlex Gateway, which includes the following: Installer, Gateway (for REST API, Alerts, SNMP/ ESRS) for Linux/ Ubuntu (can be used to deploy PowerFlex on Linux- based operating systems only). CSV deployment templates are also included
GPG-RPM- KEY| | | | | | | | | Contains RPM key (RSA for Linux, DSA for Xen) to authenticate the RPM packages using manual install/upgrade procedure

NOTE:

Install and upgrade

PowerFlex 3.6.1 can be installed on a clean system or used as an upgrade. Learn important information about installing or upgrading to this version.
Installation
For complete instructions for installing PowerFlex, see the Deploy PowerFlex Guide.
Licensing
PowerFlex use requires a license. Call your Dell Technologies account representative to purchase a license for PowerFlex.
Upgrade
The following table lists the versions from which the upgrade can be performed:
Table 4. Upgrade support matrix

ScaleIO / VxFlex OS / PowerFlex base version| Upgrade path| Supporting documentation
---|---|---
v2.0.1.4, v2.6.x| Two-step upgrade flow:
1. Upgrade to latest version of v3.0.1.x
2. Upgrade to v3.6.0.x| Upgrade VxFlex OS to v3.0.x Guide
Upgrade PowerFlex to v3.6 Guide
v3.0, v3.0.0.x, v3.0.1.x,
v3.5.x, v3.6, v3.6.0.x| Single-step upgrade from:
● VxFlex OS v3.0/v3.0.0.x/v3.0.1.x
● PowerFlex v3.5.x
● PowerFlex v3.6.0.x to PowerFlex v3.6.1| Upgrade PowerFlex to v3.6 Guide

Cloud Link support

PowerFlex version Cloud Link version Description of change
3.6.0.6 and later 7.1.5 Existing Cloud Link install base with the original

device path logic: /dev/sd X.
3.6.0.2, 3.6.0.3, 3.6.04, and 3.6.0.5| 7.1.3| Cloud Link 7.1.3 enables a new device path logic for encrypted devices, using /dev/disk/by-id/wwn- _< uniqueid>.
3.0.1.x all versions
3.5.x.x, all versions 3.6 3.6.0.1| 7.1
7.0| The Cloud Link versions maintain legacy support for the existing Cloud Link install  base with the original device path logic: /dev/sd X.

PowerFlex 3.6.0.2 supports migration and upgrade flows from CloudLink 7.1 to CloudLink 7.1.2 or CloudLink 7.1.3.
Following are the expected upgrade flow for systems with CloudLink:

  • Upgrade PowerFlex to 3.6.0.6.
  • For CloudLink 7.1 / 7.0, upgrade to CloudLink 7.1.5.
  • For CloudLink 7.1.2 / 7.1.3 / 7.1.4, upgrade to CloudLink 7.1.5 with support assistance.

PowerFlex 3.6.0.6 supports migration and upgrade flows from CloudLink 7.1 to CloudLink 7.1.5.
CloudLink 7.1.5 changes the disk-mapping logic to use /dev/sdX compared to what was introduced in the CloudLink 7.1.2 to 7.1.4 versions. This version removes support for /dev/disk/by– id from CloudLink which reverts to a /dev/sdX  device mapping.
Customers who migrated to CloudLink 7.1.3 and adopted /dev/disk/by-id logic must open a support call as documented in Dell PowerFlex v3.6.x CloudLink for SDS Devices. This helps in reverting to /dev/sdX device mapping and helps adopt the CloudLink 7.1.5.
Customers using the earlier CloudLink releases (CloudLink 7.1.1 or earlier) can adopt the CloudLink 7.1.5 by using the existing device mapping.
Due to key updates, it is recommended that you adopt the latest CloudLink 7.1.5 for usage with PowerFlex for Data at Rest Encryption.
Supported operating systems
The user documentation contains a list of supported operating systems. For the most current information, see the Dell Technologies Simple Support Matrices at https://elabnavigator.dell.com/eln/modernHomeSSM, Storage option.
SDC compatibility
By design, the PowerFlex SDC in this release is compatible with previously released systems that are currently supported (for example, VxFlex OS v3.0.1). In addition, the PowerFlex system (backend) in this release is backward compatible with previously released SDC versions that are currently supported.
Some limitations may apply to mixed-version systems, such as:

  • Replication is not supported on SDC releases earlier than PowerFlex v3.5.
  • The CHAP component authentication feature cannot be enabled unless every MDM, SDC, and SDS in the system is at least version 3.5, and conversely, if the feature is enabled, no pre-v3.5 SDCs can be added.
  • Fine Granularity Storage Pool-based volumes cannot be mapped to a ScaleIO/VxFlex operating system v2.x SDC.
  • Snapshot Policy management is not available with SDC releases earlier than VxFlex operating system v3.0.

Known issues and limitations

The following table lists known issues and limitations that exist in PowerFlex 3.6.1.
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 PowerFlex issue number.
Table 5. Known issues and limitations—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 Dirac or perccli

to get the disk slot information.

Table 6. Known issues and limitations—PowerFlex Gateway

Issue number & SR number Problem summary Workaround
SCI-66203 SR# v989309 The AutoComplete attribute is not disabled for

passwords in form-based authentication. If the browser is used in a shared computing environment where more than one person may use the browser, “autocomplete” values may be retrieved or submitted by an unauthorized user.| None
SCI-58953| When running the PowerFlex Gateway on an Internet Explorer 11 browser, LIA Authentication gets stuck in “Loading…” status when retrieving system topology.| Use Chrome or Firefox browsers to perform this action.
SCI-58471| PowerFlex Gateway Tomcat log rotations do not work after an upgrade. At build time, the “server.xml” file is defined as a “nonreplaced- config file” in the RPM. During an upgrade, the RPM mechanism will automatically detect if the file was previously edited or not. If the file was edited, it will not be overwritten during upgrade, and the new file will be created with the “.rumen” suffix.| Edit the file “server.xml” manually, and change the log rotation rules. For more information, see the PowerFlex Troubleshooting Guide, “Some PowerFlex Gateway log files fail to rotate” topic.
SCI-57810| The PowerFlex Gateway Maintenance operation screen might show an invalid LIA authentication for a containerized SDC when connecting to the system. This should appear as N/A, and can be ignored.| None
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-54887| When performing the log collection using the PowerFlex Gateway with the “exception only” check box marked, the log collection fails.| Perform log collection with the default settings using the PowerFlex Gateway.
SCI-54799| If Auto Collect logs is configured in the system during an NDU session, when the NDU ends, the PowerFlex Installer displays a button asking to
start the first phase of the NDU, even though the previous one was  completed successfully (instead of displaying the “Mark operation as done” button).| Disable auto log collection prior to starting the NDU, and run the NDU. After NDU completion, enable auto log collection again.

Table 7. Known issues and limitations—MDM

Issue number & SR number Problem summary Workaround
SCI-60885 When using SRA, the PowerFlex Gateway password and the MDM password

must be the same. Otherwise. one of the following errors is displayed on the SRM/SRA UI: SRA command ‘discover Arrays’ failed. General exception No further information available SRA command ‘discover Arrays’ failed. general error check logs for detail| Change the PowerFlex Gateway and MDM user passwords simultaneously. Ensure that they have admin permissions and the same password.
SCI-69646| By default, Python3 is installed on Ubuntu and is located in /user/bin/python3. During the execution of the command /opt/ emc/scaleio/mdm/diag/ dump_and_balance_check.py — username XXXXX –password YYYYY — approve_certificate — scripts path=/opt/emc/scaleio/mdm/ diag/, the following error is encountered: bash: /opt/emc/scaleio/mdm/diag/ dump_and_balance_check.py: /user/ bin/python: bad interpreter: No such file or directory .| Add “3” at the start of the Python script.

Table 8. Known issues and limitations—Presentation server

Issue number & SR number Problem summary Workaround
SCI-60813 When connecting a presentation server from PowerFlex version 3.6 to

a PowerFlex 3.5 system, some of the UI functionality does not work as expected.| Use the matching version of the presentation server. In an upgrade flow, see the upgrade guide for guidelines about when and how to upgrade the presentation server.

Table 9. Known issues and limitations—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 scene service is loaded, the following confusing state is returned: service scene status service: no  such service scene This is a false positive status alert.| None
Issue number & SR number| Problem summary| Workaround
---|---|---
SCI-69559| SDC installed with flash vSphere plug-in fails without any recovery due to end of support by VMware for ESXi 6.7.x and 6.5.x. For details, see Announcing end of general support for vSphere 6.5.x and vSphere 6.7.x (89305).| None
SCI-69251 SR# 151250184| PowerFlex SDC on ESXi versions 6.5 and 6.7 fail to install on ESXi version 6.7U3 and later.| Perform these procedures to complete the installation:
For example: root: ERROR: vmware.esximage.Errors.Installation Error: (‘EMC_bootbank_scaleio-sdc- esx6.x_3.6-500.106’, “(‘EMC_bootbank_scaleio-sdc- esx6.x_3.6-500.106’, ‘Could not find a trusted signer: unable to get local issuer certificate’)”). For details, see vSphere VIB signing related updates (76276).| ●  Option 1: Update the ESXi version to 6.7U3 or higher and try to reinstall the SDC.
● Option 2: Use the SDC version that supports the older ESXi version, for example: PowerFlex 3.6.0.4.
SCI-71000| The SDC system service in SLES15.x is renamed to scene to maintain consistency with other Linux distributions. However, when upgrading to the latest version (scini.service), the earlier version (sdc.service) remains in use. This conflict prevents the SDC from loading.| Ensure to disable and remove the earlier SDC service manually and then,  restart the latest scene service.
Perform the following procedures:
1. systemctl disable sdc.service
2. rm /user/lib/system/system/sdc.service
3. systemctl restart scini.service

Table 10. Known issues and limitations—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.

Table 11. Known issues and limitations—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

Table 12. Known issues and limitations— viol’s

Issue number & SR number Problem summary Workaround
SCI-54057 Uncapping a VMware virtual volume, and then immediately afterwards

trying to overwrite its content, might generate the error: “volume n is in use”.| None. Try again shortly after, because some volume operations are performed in an asynchronous fashion.

Operating system known issues and limitations

Learn about known issues and limitations for specific operating systems.
Table 13. Known issues and limitations—operating systems

Issue number & SR number Problem summary Workaround
VXFV-296 Mixing the Mellanox CX-6 100GbE NIC driver with the Broadcom
PCIe/OCP 25GbE NIC driver is not supported. Remove the bnxt_en driver and

install the Mellanox driver.
VXFV-283| Dirac support for “Prepare for Removal” on PowerEdge R650/R6525/R750/ nodes fails.| NVMe hot-swap on Linux operating systems is supported. Skip the Prepare for Removal step in Dirac.
VXFV-265| During execution of the command create- namespace with 4k alignment on RHEL 8.4, the following error is encountered: Warning: namespace0.0 unable to validate alignment| This is a false notification. The command result is as expected, and the resulting DAX device can be used with PowerFlex acceleration devices.
VXFV-243| Upgrade of a RedHat-based operating system to RHEL 8.3 fails if the node contains NVDIMMs.
This is due to a known issue on RHEL
8.3: https://access.redhat.com/documentation/ en-us/red_hat_enterprise_linux/8/html- single/  8.3_release_notes/index#known- issue_installer- and-image- creation| Follow the procedures described in “RHEL/ CentOS upgrade to version 8.3” in the Upgrade Dell PowerFlex.
VXFV-224| In a RHEL 8.x-based node using CloudLink encrypted SDS devices, after reboot the device moves to failed state.
NOTE: This issue is much rarer on RHEL7.x- based nodes, but it might occur.| 1. SSH to the relevant SDS’s operating system.
2. Delete the SDS service.|
3. Clear the device errors using the PowerFlex GUI or CLI.
4. Recreate the SDS service.
5. Verify that devices come back online. Rebuild/ Rebalance will occur if instant maintenance mode or protected maintenance mode was not used.
6. If instant maintenance mode or protected maintenance mode was used, exit maintenance mode.
VXFV-157| NVMe disks are not supported on RHEL 8.0 due to the following issue: https://access.redhat.com/solutions/4280341
Failure to observe this limitation might cause RHEL-based SDSs with NVMe to experience kernel panic during a disk removal flow.| None
VXFV-360| The device name appears incorrectly as Non PCI device instead of Dirac, but the current and baseline versions are accurate (6.00.30.201 and 6.00.30.202, respectively).| Dell recommends upgrading the OME catalog to the latest version.
—| PowerFlex nodes running CPLD 1.0.7 stop responding during Power On Self- Test (POST) when upgrading to certain RCM or IC packages that include BIOS 1.8.2 and Dirac 6.00.30.202.| Before upgrading to the latest supported version of PowerFlex, ensure that the PowerFlex nodes are running CPLD 1.0.8 or later. For details, see https://www.dell.com/support/ kbdoc/en-us/000205925.

Additional resources

Use these resources to find more information about this product, get support and provide feedback.
Product information
For documentation, release notes, software updates, or information about Dell products, go to Dell Online Support at: https://www.dell.com/support/home/en- us/product-support/product/scaleio/overview
Power Flex Documentation Library

DELL 361 Power Flex Release - Product

Where to get support
Go to Dell Online Support and click Support. You will see several options for contacting Dell Technical Support. Note that to open a service request, you must have a valid support agreement. Contact your Dell sales representative for  details about obtaining a valid support agreement or with questions about your account.
Notes, cautions, and warnings
NOTE: A NOTE indicates important information that helps you make better use of your product.
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

© 2023 Dell Inc. or its subsidiaries.
All rights reserved. Dell Technologies, Dell, and other
trademarks are trademarks of Dell Inc. or its
subsidiaries. Other trademarks may be
trademarks of their respective owners.

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>

Related Manuals