Symptom/Cause | Solution |
|---|---|
Private VLAN cannot be created VLAN is not created. Incorrect command Syntax Given Bridge Group is incorrect. With the issue of “no shutdown” command, vlan interface is not activated Due to the nature of Private VLANs, you cannot activate the VLAN interface for isolated or community VLANs. You can only activate the VLAN interface that belongs to primary VLAN. | Use these commands: show vlan brief Confirm if the VLAN is created. show running-config Confirm the bridge type created. Private Vlan cannot be created for provider bridges Use this command: show vlan private-vlan bridge BRIDGE_GROUP Confirm the type of Private vlans configured |
Not able to associate a Secondary PVLAN to the Primary PVLAN Secondary Private VLAN type is Isolated and one isolated PVLAN is already associated with the particular Primary PVLAN. Secondary PVLAN is already associated with some other Primary PVLAN. | Use this command: show vlan private-vlan bridge BRIDGE_GROUP Confirm the types of PVLANs configured and associations of Secondary PVLANs with Primary PVLANs. |
Not able to configure an interface as private-vlan host-port Interface is not access-port | Use this command: show interface IFNAME Verify the port mode. Only Access ports can be configured as host-ports. |