Loading...
Loading...
Duplicate port group names may cause Update Service Details to fail in PowerFlex Manager. The issues occur when the MGMT and PROD DC/Cluster have duplicate names for their port groups when on a single vCenter. For appliance and rack builds, a single vCenter is used. The names of the LAG are different for MGMT (for example, LAG) and PROD (for example, lag1). This results in the PowerFlex Manager Inventory Data reading the port groups incorrectly. This, in turn, causes Update Service Details to fail with error "a mix of LACP and non-LACP port groups are not allowed." The same error may also occur if a port group is manually created in vCenter and it does not have its active uplink set to the same as the PROD port group (for example, lag1). In the attachment below, the Fault Tolerant port group was manually created and it does not have its active uplink the same as the PROD port group (for example, lag1). In the attachment below, the Fault Tolerant port group now has its active uplink the same as the PROD port group (for example, lag1).
PowerFlex Manager does not record the port groups correctly unless they have unique names.
Check all port groups in the vCenter to confirm that the lag is the active uplink and that there are no duplicate port group names. If there are, rename the MGMT port group to a unique name and update vCenter inventory in PowerFlex Manager. Verify that if the port group is manually created, that its active uplink is the same as the PROD port group (for example, lag1). This issue is expected to be addressed in a future PowerFlex Manager release.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.