The switch interface sets PVID, and the platform's Layer 2 network needs to use NoVlan

[nexus]

Problem description:
The switch interface sets PVID, and the platform’s Layer 2 network needs to use NoVlan. When configuring the switch interface, set the interface pvid 302, and also allow Vlan 302 on the trunk port.
Create a VLAN type VLAN_ID 302 Layer 2 network on the platform, and create a corresponding Layer 3 network. The network cannot communicate.

Analysis of the cause of the problem:
PVID stands for Port-base VLAN ID, which is the VLAN ID based on the port in network communication. A port can belong to multiple VLANs, but there can only be one PVID. When a data packet without a tag header is received, it will be tagged with the VLAN number indicated by the PVID and treated as a data packet of that VLAN.
However, if the VID in the frame header is the same as the PVID value of the port, the switch port will receive the frame normally and will not modify the tag; when the data frame goes out from the port, it will remove the tag and send it out.
This explains why vlan 302 is allowed, but the corresponding Layer 3 network will not be connected.

Problem handling process:
If the Layer 2 network of the cloud platform is of VLAN type vlan 302, then you need to undo port trunk pvid on the switch interface to cancel VLAN 302 as PVID, and the network can return to normal.