Dell PowerFlex 4.0.x Release Notes

PDF

Known issues from PowerFlex Manager 3.8.1

The following table lists known issues from PowerFlex Manager 3.8.1 that also apply to this release.


Issue ID	Symptom	Recommended action
ESRCM-3148	Remediation is available for the Apache Log4j remote code execution vulnerability that could be exploited by malicious users to compromise the affected system. Dell recommends implementing this remediation as soon as possible in light of the critical severity of the vulnerability. The PowerFlex presentation server uses Log4j with version 2.14.1 and is impacted by this issue.	For details, see https://www.dell.com/support/kbdoc/enus/000194548/dsa-2021-272-dellpowerflex-securityupdate-for-apachelog4j-remote-codeexecutionvulnerabilitycve-2021-44228?ref=emcadvisory_000194548_Critical_null
VXFM-24115	A service status is displaying incorrectly on the Services page after performing service mode operation.	None.
VXFM-23822	An attempt to perform a service upgrade fails after a backup and restore from an earlier release of PowerFlex Manager. This could be caused by a change in the state of the environment after the backup is performed. For example, this would happen if the hostname of the PowerFlex gateway changed after the backup was performed, since PowerFlex Manager restores the state of objects at the time of the backup, and any subsequent service operations would fail because of the mismatch in the gateway hostname.	Ensure that the state of your system resources does not change after a backup is performed. The backup state must match the state of your production environment once the restore is performed.
VXFM-23802	The SDC nodes are not listed under View details on the Resources page for PowerFlex Gateway.	None.
VXFM-23775	Disruptive upgrade on the PowerFlex hyperconverged service fails, if upgrading from VMware ESXi 7.0.Ux to VMware ESXi 7.0 Ux. The PowerFlex hyperconverged nodes become unresponsive after deactivating the protection domain and shutting down all the VMs.	Use the non-disruptive upgrade.
VXFM-23756	After upgrading from PowerFlex Manager 3.4 to PowerFlex Manager 3.8, PowerFlex storage-only service is showing as Healthy instead of Lifecycle Mode.	You need to perform Update Service Details after adding the latest compatibility matrix.
VXFM-23672	The PowerFlex storage-only service shows as `Incomplete` with a banner message displaying `To add volume` even though two PowerFlex service volumes exist.	Volumes created outside of the service will not display within the service until inventory and Update Service Details is performed.
VXFM-23639	New OS10 switches are non-compliant with newer firmware versions as expected version in RCMs and Intelligent Catalogs may be lower and downgrades are not allowed.	None.
VXFM-23636	If you perform an update on a node in a service, you may not be able to update a second node in the service immediately after the first node is upgraded without manually running inventory on the PowerFlex gateway in PowerFlex Manager.	Run the inventory for the PowerFlex gateway and re-initiate the node upgrade.
VXFM-23630	Unable to initiate the scaleup of networks on a PowerFlex management controller 2.0 setup.	None.
VXFM-23231	If the server profile is incorrect, PowerFlex storage-only service scaleup volume completes with an Error deployment state.	Reapply the server profile so that it displays the model name correctly and retry the service. Set the correct model name for PowerFlex Manager appliance when converting from PowerFlex Ready Node to PowerFlex appliance.
VXFM-23193	Editing a service with a new OS image is not reflected in the Services or Compliance and OS Repositories. New PowerFlex nodes deployed will reflect the new OS image. Only existing PowerFlex nodes upgraded will have this issue.	Confirm the current OS image, go to Services and confirm. Re-adding the service will identify the latest OS image available and reflect the selected one during import.
VXFM-23136	Reserving virtual IP address comes from the SDC role, if the IP address range is small.	None.
VXFM-23132	In the Resources page, filtering resource type PowerFlex Gateway/Presentation Server(PS) using the corresponding service name displays `No Devices Found`.	None.
VXFM-23124	Multiple inventory jobs are causing service failures.	Retry the service.
VXFM-23066	Cannot search for volumes starting with `+` in the search text.	Do not use `+` in the search criteria.
VXFM-23061	In resource discovery, cannot select Next from Assign Users step in Create Node Pool wizard due to incorrect validation error.	None.
VXFM-22804	The Filter by Groups feature for Active Directory is not working.	None. Scroll through the list of users.
VXFM-22573	On a PowerFlex storage-only template, when changing to the Add Networks to this port option from Mirror, the selected networks are inversed.	Re-edit and the selected folders will be available.
VXFM-21849	The Import Networks feature is not working when adding an existing service with VMware NSX and VMware vCenter network folders.	Do not use the Import Networks feature while adding an existing service. Manually define the required networks in PowerFlex Manager - PowerFlex / hypervisor management and PowerFlex data networks. It is not necessary to define the general purpose LAN networks - they can be left blank.
VXFM-21559	During a deployment, if servers are discovered before switches, the service is returned in lifecycle mode.	Manually run inventory on the switches.
VXFM-21531	CloudLink Center SNMP settings are applied without user input and are not fully functional.	After completing a change configuration, save the configuration again without making any changes.
VXFM-21467	Deployment fails if overlapping data network subnets are used.	Set up the correct network subnets and redeploy. Ensure you have one interface per subnet and redeploy.
VXFM-21353	PowerFlex gateway upgrade does not update the compliance report on the PowerFlex nodes.	Rerun the inventory on all the PowerFlex nodes.
VXFM-21278	VMware vCLS volumes fail to migrate to the shared datastore if VMware ESXi nodes are added using an IP address, but resolve to a hostname in the DNS.	Add the PowerFlex nodes back into the vCSA under the resolved hostname.
VXFM-21256	The iDRAC service module is not in a running state during an NVMe replacement. The NVMe eject operation fails.	Restart the iDRAC network and restart the ISM service dcism.
VXFM-21233	The migration of vCLS VMs fails on a PowerFlex hyperconverged service if there is a mix of PowerFlex compute-only nodes and hyperconverged-only nodes in same VMware cluster but in different services that you are trying to upgrade. Migration is failing because one of the vCLS VMs belongs to the PowerFlex compute-only service, but it does not have access to the new utility datastores.	Run the VMware vCLS migration on the PowerFlex hyperconverged service. If that fails, go to PowerFlex compute-only service, and run the vCLS migration on that service.
VXFM-21232	Network scale up fails on a hyperconverged service due to port down when adding service.	Reseat the network cable to see if uplink can be restored. Remove the service. Readd the service using the Add Existing Service function. Verify the network connectivity displays in the Port View.
VXFM-21231 and VXFM-21180	Partial network automation option is only intended to be used with LACP networking. However, there is no validation performed in the Add Existing Service wizard to prevent the use of partial network automation without LACP networking. Selecting this combination can result in various failures including: The service shows a blank Teaming And Bonding Configuration in the service's View All Settings dialog under OS Settings. Rebooting the PowerFlex Manager appliance will cause the service to go into an Upgrade Service Components error status. Service update operations run on the service fail. PowerFlex cluster upgrades fail.	Remove the service and add it again by using Add Existing Service with the Full Network Automation option. Only choose Partial Network Automation if your service is using LACP networking.
VXFM-21186	If you are upgrading a service, the service may be placed in lifecycle mode due to validation errors. The validation errors are displayed as a part of the reason. If the service prompts for vCLS migration also, you can perform vCLS migration on the service. In this case, the validation reasons are removed, and the banner no longer includes the reasons for lifecycle mode. You no longer see the reasons, but the service is in lifecycle mode and prevents any further actions.	None.
VXFM-21049	The service name displayed in the Duplicate Node Summary screen shows special characters in an HTML encoded format.	None.
VXFM-20957	During an import of Active Directory users, if you click View Details, PowerFlex Manager displays a broken page.	None.
VXFM-20944	Appliance and Alert Connector state shows different timezone and time stamp.	No functional impact, reboot the appliance and timezone and time stamp align.
VXFM-20940	Dell CloudLink Center deployment fails if you are using different subnet than PowerFlex Manager appliance.	Set the subnet manually.
VXFM-20868	If a service only has a single node, the Add Existing Service function works, but the overall service health shows error status once the service add finishes.	None.
VXFM-20877	PowerFlex Manager may show the wrong compliance status on nodes. PowerFlex Manager shows the nodes are compliant on the Resources page, even though the nodes are not compliant.	Run a manual inventory, and the correct compliance status displays.
VXFM-20816	Adding an OS Image with the same repository name does not return an error.	None.
VXFM-20735	VLAN 4094 through 4096 are reserved VLANs on the Dell PowerSwitch switches.	Do not use any of the reserved VLANs.
VXFM-20686	VMware vSphere vMotion vmk is missing from the second node in an VMware ESXi compute-only node deployment.	Manually create the VMware vSphere vMotion vmk on the second node.
VXFM-20666	No warning displays when adding an existing encrypted service to a brownfield deployment.	Ensure an encryption tool or CloudLink is discovered first.
VXFM-20655	Drive replacement and MDM reconfiguration are allowed through PowerFlex Manager when a service is in an error state.	Do not attempt a drive replacement or an MDM reconfiguration if a service is in an error state.
VXFM-20593	PowerFlex Manager creates an Element Manager credential via REST API fails with wrong error message if snmpCommunityString is omitted.	None.
VXFM-20590	When scaling up of the network on a PowerFlex compute-only service, the new network does not show under the port view for one of the three nodes in the service.	None.
VXFM-20588	PowerFlex Manager displays Update Resource when current version is higher than expected version.	None.
VXFM-20571	PowerFlex Manager lets you add a static route to a subnet that already exists on the node. This fails as it is not needed - the node already has a route to that subnet.	None.
VXFM-20546	If existing port channels that do not have any interfaces are reused on Dell OS10 as part of the new service, any previous VLANs on those port channels are not cleared. If new port channels are created they will only have the correct VLANs.	None.
VXFM-20533	PowerFlex Manager fails to set the default compliance package version when you add a compliance file and select Make this the default version for compliance checking.	Click Change to reset the default version.
VXFM-20318	A PowerFlex hyperconverged service deployment using an existing VMware cluster with different storage pools fails.	Remove the nodes and add them back with the same storage pool.
VXFM-20215	In the teardown of a PowerFlex hyperconverged service where the datacenter, cluster, and network information are all moved into their own folders in VMware vCenter, the service resources are re-inventoried, and the service is removed. However, the VMware vCenter cluster and nodes are left and not removed.	Manually remove the vCenter cluster and nodes.
VXFM-20169	MDM reconfiguration fails for certain role transitions.	You can set the role manually, if needed. Retry or rescan refreshes the roles.
VXFM-20154	If you attempt to restart a failed job by clicking Retry, PowerFlex Manager displays a warning page with a View Compliance Report link. This link is broken. You may encounter this issue after a resize volume or migrate vCLS VMs operation fails.	Click View Compliance Report under Service Actions.
VXFM-19482	PowerFlex Manager fails to configure the server facing ports due to switchport mode trunk returning the following error: % Error: MODE_L2HYBRID, Configured as a lag interface ToR-B(conf-if-eth1/1/3)#	Remove swichport mode trunk before running through PowerFlex Manager.
VXFM-19010	The wizard for updating resources displays incorrect error messages when trying to update the PowerFlex gateway or presentation server resources from the Services page.	Go to the management VM service and click Update resource.
VXFM-18857	During an Add Volume job, a service will go from the In Progress state to the Completed state, then suddenly return to In Progress. While the job is still In Progress, some of the service actions may be enabled.	Allow the job to finish before you try to use any of the service actions.
VXFM-18580	Clusters already in services on the appliance are provided as selection options when importing an existing service.	None.
VXFM-18554	During a PowerFlex hyperconverged replication service deployment, retry does not set the VMware VM version. This can cause the deployment to fail when trying to add NVDIMM devices to the VM.	Delete the VM and retry the service.
VXFM-18167	Adding an existing service wizard network mapping shows %2f instead of / in port group name.	Unsupported special characters cause a rendering issue with the port group name and should not be used. Spaces, underscores, and hyphens are allowed.
VXFM-18005	Retrying a failed PowerFlex upgrade fails to cancel previous upgrade job.	If you start the upgrade, and request PowerFlex Manager to start another upgrade, it fails. If you see this failure, you may must cancel the previous upgrade.
VXFM-17760	Service sees old NIC cabling data resulting in failure.	Contact Dell Support for a workaround.
VXFM-17610	The DHCP setting in PowerFlex Manager does not allow you to disable the DHCP/PXE node if the virtual appliance is not currently on the subnet.	Do not change your network while you are working on it. If you must do this, at least disable DHCP first.
VXFM-17023	Unable to use NetApp NFS share from PowerFlex Manager.	PowerFlex Manager does not support NFS shares set up this way.
VXFM-16623	A node discovery may appear to fail with the following log message: `Failed to collect the system configuration for server`	Check for the following conditions: Networking issues between iDRAC and PowerFlex Manager The server is booted into the BIOS screen. In this case, jobs cannot be run.
VXFM-16261	During a restore, the PowerFlex Manager appliance gets stuck at Starting Restoration stage when a filename is not provided, that is, if only the path is specified.	Use the full path to the restore file.
VXFM-15653	Download of the ONIE firmware upgrade package fails, but the failure is not displayed in the logs.	None.
ESRCM-2526	VMware ESXi 7.0 requires a security patch that is available in VMware ESXi 7.0 Update 1.	For VMware ESXi 7.0, you must perform a manual workaround. For details, see https://kb.vmware.com/s/article/76372.
VXFM-15308	PowerFlex Manager collects switch performance metrics only if NXAPI is listening on both HTTPS (Port 443) and HTTP (Port 80). If either of these ports are disabled, switch performance metrics are not collected.	Be sure that ports for both HTTP and HTTPS are enabled for Cisco switches.
VXFM-15227	PowerFlex Manager allows you to publish and deploy a CloudLink template containing a password with all lowercase characters.	Be sure to include at least one uppercase letter in the password.
VXFM-15267	If you try to upload an SSL certificate on the Appliance SSL Certificates section of the Settings page, you may encounter security errors with the Certificate Signing Request (CSR). The CSR does not include the Subject Alternative Name (SAN) field. It only includes the Common Name (CN) field. This problem occurs only with the Chrome browser.	Contact Dell Support for a workaround.
VXFM-15188	When deploying a service, you may see an error message stating that a static IP address could not be reserved. The error may include empty brackets ([ ]). If you see this error, the IP addresses may not be pingable.	Check your IP addresses to be sure you have enough pingable IP addresses, and try again.
VXFM-15110	You may see incorrect warning messages when using invalid characters for a hostname in a template. If you try to publish the template, you may see a message indicating that a hostname exceeds the limit of 15 characters. The message should indicate that the hostname has invalid characters.	Be sure to use valid characters and conform to the character limit for the operating system. For Windows, the limit is 15 characters for a hostname. For ESXi and Linux, the limit is 26 characters.
VXFM-15069	A node cannot be removed from a storage-only service because of a failure removing the switch. If the switch removal fails, PowerFlex Manager leaves the node in the service.	Update the service details or remove the node manually from the service.
VXFM-15010	Adding replication networks to a hyperconverged template breaks the service.	None.
VXFM-14898	During drive replacement, if you type `CONTINUE WITHOUT DRIVE` with a bad drive, PowerFlex Manager tries to add it back and fails.	None.
VXFM-14872	You may notice a type casing inconsistency, when creating templates with uppercase host and SVM names. VMware ESXi uses lowercase host names. There is no impact to functionality.	None.
VXFM-14773	If you try to download two RCMs simultaneously, the operation fails.	Resynchronize the RCMs or download them again separately.
VXFM-14771	If you deploy a service with only one node in it, the service may show Critical. This condition is caused by a warning at the component level.	None.
VXFM-14770	The inventory is not running on the PowerFlex gateway after you use service mode. If you place a node in service mode, then exit service mode, then try to enter service mode again, the PowerFlex gateway is left in an abnormal state.	Manually run the inventory or wait for the next hourly update.
VXFM-14767	PowerFlex Manager does not refresh text boxes in the Discovery Wizard. This display problem can happen if you select Node as the Resource Type and choose Hostname, then change the Resource Type to any other type other than Node.	Click the trash can icon to remove the resource, then add it again.
VXFM-14763	Mellanox ConnectX-4 LC firmware must be on 14.25.80.00 or later to upgrade to 14.27.10.16 or later. This problem is not a PowerFlex Manager issue. PowerFlex Manager does not support step upgrades.	None.
VXFM-14753	If an upgrade of the PowerFlex Manager virtual appliance fails, you may see duplicate email messages and alerts.	None.
VXFM-14724	If you try to delete an RCM that is used on a service, the operation fails with a 500 internal server error.	Remove the service that previously used the RCM, delete the RCM, and add the services back as an existing service.
VXFM-14581	When you add an existing hyperconverged or storage-only service that includes a CloudLink Center VM in a cluster, the Inventory Summary page does not show the Adding icon for the CloudLink Center VM.	None.
VXFM-14535 and VXFM-15309	If you change the password for an SVM, View All Settings on the Services page still shows the old password. This issue also breaks Update Service Details if you try to use a new credential.	If you need to change the OS credential to a newly-defined credential and update to use that credential on a service, you have to remove the service and readd it to select that credential.
VXFM-14496 and VXFM-14254	After upgrading from an earlier version of PowerFlex Manager, you may notice that the inventory might not be updated correctly or that subsequent operations such as Add Existing Service may fail.	Run a manual inventory after the upgrade.
VXFM-14494 and VXFM-14762	After changing an iDRAC password, if you select the same credentials again, you may see an error message in the Update Password wizard. After you see the error, you cannot proceed with the wizard.	Cancel and restart the wizard.
VXFM-14470	PowerFlex Manager does not perform validation to ensure that you have a minimum of three fault sets for a protection domain and storage pool.	Ensure that your fault set configuration conforms to best practices. Dell recommends that all nodes in a protection domain should be in the same storage pool.
VXFM-14397	PowerFlex Manager displays the wrong progress bar during the resizing of a datastore.	None.
VXFM-14377	After you remove a node from a service, PowerFlex Manager may not update the PowerFlex gateway inventory.	Run a manual inventory after removing the node.
VXFM-14028	The Services page does not show lifecycle mode as the deployment state for NSXT services that are in lifecycle mode.	None.
VXFM-13994	If a Dell CloudLink Center is non-compliant, PowerFlex Manager disables node selection for upgrade.	Upgrade the CloudLink Center from the Resources page and try the upgrade from the Services page.
VXFM-13744	An RCM upgrade to a major version of NSX and ESXi may fail with a VIB error. This failure could be caused by a VIB incompatibility if you are using a nonstandard Dell image. Be aware that NSX VIBs are specific to the version of ESXi that is installed on the host. If you upgrade ESXi, you must install new NSX VIBs appropriate for the new ESXi version.	Install new NSX VIBs for the new ESXi version. For more information, see Upgrade to ESXi 6.5 or 6.7 in an NSX Environment.
VXFM-12990	The state of a discovery job may show as Running on the Jobs page, even though it has completed.	Restart the PowerFlex Manager virtual appliance.
VXFM-12477	On the Resources page, if you select a machine with self-encrypting drives (SEDs) for a CloudLink Center, you might see two entries for each drive. One entry shows the status as "encrypted" with a type of "data_sed". The other entry shows the status as "unencrypted" with a type of "data_sds". The SED drives are encrypted, but PowerFlex Manager should not show duplicate entries.	None.
VXFM-12402	After deleting a node from a storage-only service, you may see an incorrect error message in Recent Activity. The message indicates a failure removing the Storage Data Client (SDC), even though an SDC is not installed on a storage-only node.	None.
VXFM-12391	If you put an SDS into Protected Maintenance Mode (PMM) manually, and then run inventory for the PowerFlex gateway within PowerFlex Manager, the service does not exit service mode. When you click Exit Service Mode, PowerFlex Manager shows an error. This error occurs because PowerFlex Manager is trying to exit Instant Maintenance Mode (IMM) instead of PMM.	Manually take the SDS out of PMM outside of PowerFlex Manager.
VXFM-12366	If you cancel a service deployment, and then retry the deployment later, the service succeeds. However, the warning banner that is displayed while PowerFlex Manager is canceling the deployment remains during and after the successful deployment.	Remove the service and add it back again.
VXFM-12096	The deployment for a storage-only service may sometimes fail to start.	Retry the service deployment.
VXFM-12074	On the View Details page for CloudLink, PowerFlex Manager shows a hyperlink for the IP Address field for the SDS. The hyperlink should not be displayed for an SDS IP address.	None.
VXFM-11998	PowerFlex Manager does not always show the new status when you add an operating system image on the OS Image Repositories tab.	Manually refresh the screen to see the new status.
VXFM-11977	If you delete a node that was not deployed successfully in a service, PowerFlex Manager might show the node as deployed.	To remove the failed node from the service, choose the Remove Resource option, rather than the Delete Resource option.
VXFM-11930	After upgrading from version 3.3 or 3.4, you might notice that a service that has a fault set enabled shows Deployed as the Deployment State, even though it should show Lifecycle Mode.	Click Update Service Details to show the correct state.
VXFM-11760	After updating the firmware and software on a node, or during a service mode operation, PowerFlex Manager might show the node as being in service mode, even though it is no longer in service mode. Due to a time lag, the service mode status that is shown on the service does not always match the state of the system exactly. The node eventually comes out-of-service mode, and the update completes successfully.	None.
VXFM-11758	A compute-only service with ESXi displays the Protected Maintenance Mode option for a firmware and software update on a PowerFlex 3.5 cluster. This type of service offers only compute resources, and does not have an SDS component. The Protected Maintenance Mode option should not be available. The update succeeds even if you choose this option.	None.
VXFM-11705	If you attempt to discover a Cisco switch with terminal color configured, the discovery fails.	Disable the terminal color option by running configure no terminal color persist.
VXFM-11242	If you click Update Service Details, PowerFlex Manager might display an incorrect error indicating that the `device could not be connected through SSH`. The message should state that the iDRAC was not responding, most likely because of bad cabling.	None.
VXFM-10663	PowerFlex Manager has only one firmware component id set for all OS10 switches in PowerFlex Manager. This means that PowerFlex Manager can only include one set of OS10 switch versions for all models of OS10 switch in a given RCM package. This is a problem for management switches.	Do not discover the management switches.
VXFM-3727	If you try to create a network containing IP addresses that are in use by vCenter or the PowerFlex gateway inventory, `Invalid IP address range is entered` errors are thrown. An extra error message states: `The entered IP range overlaps with the IP ranges configured on one or more configured networks`. This situation only happens if you have multiple networks with the same subnet. For example, this situation might happen if you have an SDC only network and a network that supports both SDS and SDC traffic.	Remove your vCenter or gateway from the inventory, create the network ranges, and then rediscover them.
VXFM-3517	If the PowerFlex gateway is deployed onto an operating system that does not have systemctl (such as SuSE 11 or Red Hat Enterprise Linux 6), the PowerFlex configuration script fails to restart the gateway after configuring it. However, it does not return any error, so ultimately the deployment fails when trying to talk to the gateway REST API. This configuration is unsupported, but PowerFlex Manager does not block the configuration or provide a clear error message.	None.