Loading...
Loading...
Duplicate port group names may cause a redeployed service to have issues in PowerFlex Manager. It can come up in Life-Cycle Mode only, and the nodes have errors "the host has an unsupported teaming policy for port group." 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 and causes issues with the port groups.
PowerFlex Manager does not record the port groups correctly unless they have unique names.
Check all port groups in the vCenter to confirm 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 fixed in PowerFlex Manager release 3.7.
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.