PowerFlex: Lifecycle Mode Reasons and NSX Handling

Lifecycle mode

Lifecycle mode allows lifecycle management of node components in an unsupported configuration. In lifecycle mode, a service supports health and compliance monitoring, service mode, and nondisruptive upgrade operations. All other service operations are blocked.

Lifecycle mode controls the operations that can be performed for configurations with limited support, including the following:

• No switch configuration
• No switch connectivity
• Unsupported switch
• Invalid server inventory
• Missing network settings
• Unsupported server configurations
  • As of 4.8, adding an existing Resource Group with nodes in BIOS mode will cause the RG to enter Lifecycle mode
• Unsupported NIC or NIC teaming policies
• Network configuration without a PXE VLAN setting
• PowerFlex MDM cluster without virtual IP addresses
• VMware vSphere Cluster Services (vCLS) virtual machines on local storage

PowerFlex Manager also puts a service in lifecycle mode if you select a minimal compliance version that includes firmware only for the service, and or the VMware NSX-T service is configured.

When NSX is configured, limited actions are available because the RG is in lifecycle mode; hence, the below actions to be followed. 

• Remove the RG and add all the newly created PFxM Networks while adding the RG back to PFxM. 
• Run the "Update Resource Group Details" on the Resource Group

See 

PowerFlex Manager - How to confirm RCM or IC bundle on a Rack or Appliance is supported in Managed Mode

PowerFlex Management Platform: Add Existing Resource Group Lifecycle Mode "has a mix of LACP and non-LACP port groups based on networks selected"

PowerFlex Management Platform: Resource Group in Lifecycle mode after migration

PowerFlex Rack: Lifecycle mode because LLDP is not turned on