PowerFlex: Add Existing Resource Group Missing Defined Network Object Type - VXFM00561

The PowerFlex MDS or Production system was manually deployed or removed from PFxM and is ready to be ingested by PFxM as a resource group.

The SVM and Hypervisor Management network share the same VLAN and are on the same vSwitch port group.

Screenshot showing that some or all the required IP addresses to add or update an existing service are missing: (VXFM00561)
 

Unable to ingest the MDS system as a resource group.

To include an existing resource group, the wizard expects to have all the necessary network objects associated with the PowerFlex system. For instance, the PowerFlex system uses network types such as vMotion, PowerFlex Management, PowerFlex Data1, PowerFlex Data2, and Hypervisor Management. In this specific case, the vSwitch in vCenter had a single port group containing both Hypervisor Management and PowerFlex Management. Therefore, the wizard only included a dropdown item for the Hypervisor Management network type, omitting the dropdown object for PowerFlex Management. All network types linked to PFxM are essential for properly incorporating the PowerFlex system as a resource group.

In vCenter, create another port group on the same vSwitch and separate the PowerFlex Management and Hypervisor Management networks.

The SVMs must point to the newly created port group.

In PFxM, run inventory on vCenter

Attempt to ingest the PowerFlex system as a resource group. 

 

Impacted Versions

PowerFlex Manager 4.x

Fixed In Version

N/A - Working as designed 

VxFlex Ready Nodes, PowerFlex custom node, PowerFlex appliance R650, PowerFlex appliance R6525, PowerFlex appliance R660, PowerFlex appliance R6625, Powerflex appliance R750, PowerFlex appliance R760, PowerFlex appliance R7625 , PowerFlex appliance R740XD, PowerFlex appliance R7525, PowerFlex appliance R840 ... View More View Less