Issue/Introduction

This article helps troubleshoot failures to create a ZSphere distributed port group with VLAN type None.

Symptoms

• Creating a distributed port group with VLAN type None fails and the page reports API ERROR.
• Cluster hosts have a residual underlying novlan bridge or a bond configuration issue.

Environment

• Product: ZVF
• Version: 4.x
• Component: ZSphere
• Affected object: distributed port group
• Scenario: For network and switch issues, confirm the current version, deployment type, storage type, and operation timeline.

Possible causes

• Bond configurations are inconsistent or do not meet port group requirements.
• A residual underlying novlan bridge conflicts with new port group creation.
• Network configurations of some hosts do not match the cluster network model.

Resolution

Perform the following checks in order, and record the affected object, occurrence time, complete error message, and current status.

1. Check whether bond, bridge, and VLAN subinterface configuration is consistent across all hosts in the cluster.
2. Confirm whether a historical residual novlan bridge exists, and record its name and associated ports.
3. Review the specific failure reason for API ERROR in the management service logs.
4. Before removing residual underlying network configuration, confirm that there is no service traffic and no port group reference, and then perform the change.

Remediation

1. Verify the bond and bridge configuration of hosts in the cluster, and locate the residual novlan bridge that conflicts with port group creation.
2. After confirming that the bridge carries no service traffic, is not referenced by a port group, and its configuration has been backed up, remove the residual configuration and create the port group again.

Verification

• A distributed port group with VLAN type None can be created successfully.
• After creation, host network connectivity in the cluster and existing port group services are unaffected.