PowerFlex Add service fails when NSX port groups on separate VDS with no LAG

• After the service was deployed using PowerFlex Manager the environment is modified or reconfigured to use NSX.
• The service was removed from PowerFlex Manager.
•  When try to add the service back to PowerFlex Manager, it fails at the summary screen triggering error message "a mix of LACP and non-LACP port groups are not allowed"
•  The asmManager.log reports similar to below error.

 2022-05-17 09:54:22,026 DEBUG [pool-5-thread-3,tid=2071] (ProcessEsxiBrownfieldHost.java:329): Adding Host node1 to Service.
2022-05-17 09:54:22,038 DEBUG [pool-5-thread-1,tid=2069] (ProcessEsxiBrownfieldHost.java:403): Found NSX-T Hyperconverged
2022-05-17 09:54:22,039 ERROR [pool-5-thread-1,tid=2069] (ProcessEsxiBrownfieldHost.java:1145): Can not have a mix of LACP and non LACP VDS.
2022-05-17 09:54:22,040 DEBUG [pool-5-thread 2,tid=2070] (ProcessEsxiBrownfieldHost.java:403): Found NSX-T Hyperconverged 2022-05-17 09:54:22,040 ERROR [pool-5-thread-2,tid=2070] (ProcessEsxiBrownfieldHost.java:1145): Can not have a mix of LACP and non LACP VDS. 

• PowerFlex Manager expects all port groups under particular VDS should have the same Teaming and Load Balancing settings. 
• Port groups on one of the VDS may have different settings. 
• In the vCenter inventory, PowerFlex Manager may see NSX port groups that do not have LAGs configured. Since the NSX port groups are not managed as a part of the service, it should ignore these port groups when checking, but does not.

Procedure:
1) Ensure that you followed the below KB article and confirmed the issue still exists.
PowerFlex Manager: Update Service Details error "a mix of LACP and non-LACP port groups are not allowed"

2) Confirm that the particular service does not have any standard PowerFlex port groups that are incorrectly configured without the lag setup.

Copy the vCenter facts JSON file from Troubleshooting bundle to PowerFlex Manager appliance under location /home/delladmin OR Copy the vCenter facts JSON file from PowerFlex Manager under location /opt/Dell/ASM/cache/ to location /home/delladmin/
a) Use winscp or similar tool to copy the vCenter facts JSON file from Troubleshooting bundle under directory DeviceFacts to PowerFlex manager location /home/delladmin/.
OR
b) Run the below command to copy the vCenter facts JSON file from PowerFlex Manager location /opt/Dell/ASM/cache/ to location /home/delladmin.
 

 cp /opt/Dell/ASM/cache/<vcenter-xx.xx.x.com.jason>/ /home/delladmin/

Example: 
[delladmin@pfxm-jade ~]$ cp /opt/Dell/ASM/cache/vcenter-vc-prod.sust.isg.com.json /home/delladmin/
[delladmin@pfxm-jade ~]$ ls
spdump  vcenter-vc-prod.sust.isg.com.json
[delladmin@pfxm-jade ~]$

Run the following commands to generate a file that is more readable. 

pry
require "json"
data = JSON.parse(File.read("/home/delladmin/vcenter-vc-prod.sust.isg.com.json"))
inventory = JSON.parse(data["inventory"])
File.write("/home/delladmin/vcenter-vc-prod.sust.isg.com-parsed.json", JSON.pretty_generate(inventory))

Example:

[delladmin@pfxm-jade ~]$ pry
[1] pry(main)> require "json"
=> true

[2] pry(main)> data = JSON.parse(File.read("/home/delladmin/vcenter-vc-prod.sust.isg.com.json"))
=> {"vcenter_name"=>"vc-prod.sust.isg.com",
 "service_tag"=>"vc-prod.sust.isg.com",
 "puppet_certname"=>"vcenter-vc-prod.sust.isg.com",
 "vcenter_version"=>"7.0.2",
 "vcenter_build"=>"17958471",
 "datacenter_count"=>"1",
 "cluster_count"=>"2",
 "vm_count"=>"21",
 "host_count"=>"5",
 "customization_specs"=>"[]",
 "storage_profiles"=>
.
.
.
#press q button.

[3] pry(main)> inventory = JSON.parse(data["inventory"])
=> {"name"=>"Datacenters",
 "id"=>"group-d1",
 "type"=>"Folder",
 "attributes"=>{},
 "children"=>
  [{"name"=>"boston_dc",
    "id"=>"datacenter-2292",
    "type"=>"Datacenter",
    "attributes"=>{},
    "children"=>
.
.
. 
#press q button.

[4] pry(main)> File.write("/home/delladmin/vcenter-vc-prod.sust.isg.com-parsed.json", JSON.pretty_generate(inventory))
=> 131584

[5] pry(main)> quit
[delladmin@pfxm-jade ~]$

 Confirm that the parsed file is generated in the specified location.

[delladmin@pfxm-jade ~]$ ls -l|grep -i vcenter
-rw-r--r--. 1 delladmin delladmin  62635 Jul  7 02:13 vcenter-vc-prod.sust.isg.com.json
-rw-rw-r--. 1 delladmin delladmin 131599 Jul  7 02:34 vcenter-vc-prod.sust.isg.com-parsed.json
[delladmin@pfxm-jade ~]$

iv) Use the new generated parse file for cross checking vCenter does not have any standard PowerFlex port groups that are incorrectly configured without the lag setup. You can do this by searching for uplink1 or uplink2. If those show as the active uplinks for any port groups, it must be verified if those are configured correctly or not. If they are standard PowerFlex port groups, they should all be configured with the LAG as the active uplink.

3) If all the standard PowerFlex port groups are configured with the LAG as the active uplink, NSX is installed on the system, and the NSX port groups are the only port groups not using the LAG as the active uplinks, go to next step to apply the patch.

To fix this issue a patch is available for the 3.8.x versions of PowerFlex Manager.

Note: This patch only applies to systems that have NSX and have no other standard PowerFlex port groups that are incorrectly configured without the lag setup.

Patch for PowerFlex manager version 3.8.0 is available under attachment section of this KB article with name patch-3.8.0-vxfm-28567_csp.
Patch for PowerFlex manager version 3.8.1 is available under attachment section of this KB article with name patch-3.8.1-vxfm-28567_csp.
The README file inside the .zip file contains the instructions to apply the patch.

Note: After applying the above patch when you try to perform add existing service operation an informational message appears stating that there is a mix of LACP and non-LACP port groups in the summary screen, but it allows you to go to adding the service.