Issue/Introduction
This article helps troubleshoot failures to add a ZSphere host when the management VLAN differs from the cluster default VLAN.
Symptoms
- Adding a host fails. The error contains
default port group,managementIp vlanId, and an inconsistency withcluster default vlanId. - The target host network is reachable, but default port group initialization fails.
Environment
- Product: ZVF
- Version: 4.x
- Component: ZSphere
- Affected object: add host
- Scenario: For host and hardware issues, confirm the current version, deployment type, storage type, and operation timeline.
Possible causes
- The cluster default VLAN differs from the VLAN plan for the host management network interface.
- The wrong management NIC, bond, or VLAN parameter was selected during installation or initialization.
- Residual bridge or port group configuration on the host conflicts with the current cluster configuration.
Resolution
Perform the following checks in order, and record the affected object, occurrence time, complete error message, and current status.
- Verify the cluster default VLAN, management network VLAN, and VLAN of the switch port that carries the host management IP.
- Confirm that the management NIC or bond selected when adding the host matches the actual management network.
- Check whether the host has residual bridge, bond, or VLAN subinterface configuration.
- Correct the network plan or remove residual configuration before adding the host again.
Remediation
- Align the cluster default VLAN, management network VLAN, and management network configuration of the host to be added.
- After confirming that there are no references, remove historical bridge, bond, or VLAN subinterface configuration and add the host again.
Verification
- The management VLAN and cluster default VLAN are consistent, and the host can be added successfully.
- After the host is added, the host management network and existing service networks in the cluster remain connected normally.
