PowerFlex: When it is Safe to Ignore UI Non-Compliance During Hardware Component Updates
Summary: This article explains when it is safe to ignore PowerFlex UI non-compliance when hardware component updates are necessary. The compliance flag in PFxM is a best-practice target matrix. If support and engineering guide our customer community to update hardware to fix an issue seen in the field, such as stated in an LKB, DTA, or DSA, deviation is allowed, supported, and acceptable. ...
Instructions
This article aims to clarify the main purpose of the PFxM UI non-compliance and when it is safe to ignore the flag. Compliance deviation is not preferred but is necessary at times. When support and the customer have guidelines to remediate a possible issue, non-compliance becomes necessary. Customers are advised to plan and schedule to pick up the next RCM/IC that will include the necessary fix for their system to run optimally. Running non-compliant for a temporary or short time period is supported under these conditions. If the customer wants to return to compliance and avoid additional issues, engineering always recommends updating to the latest.
The Single Component Upgrade (SCU) was introduced in PowerFlex 4.5.x.x and above. See the Single Component feature to create a custom RCM\IC.
PFxM: Enable the Single Component Upgrade feature on PFxM 4.5.x and later versions.
PFxM: How to perform Single Component Upgrade on PFxM 4.5.x and later versions.
For 3.x code a non-compliance flag in the UI is expected. For versions prior to PowerFlex 4.5.x.x, see the manual update guidelines.
Dell PowerFlex Rack with PowerFlex 3.x Upgrade Guide