cisco Catalyst 9300 — Promiscuous Private VLAN Trunk Ports

Traffic in the upstream direction is sent by host1 to the non-PVLAN switch, arriving in VLAN 11. The packets are then transmitted to the Catalyst 9k series switch tagged with that VLAN’s tag (VLAN 11) over the trunk port. On the Catalyst 9k series switch, VLAN 11 is configured as the isolated VLAN, and the traffic is forwarded as if it came from an isolated host port. Note The Catalyst 9k series switch provides isolation between the isolated trunk and directly connected hosts (such as host3), but not between hosts connected to the non-PVLAN switch (such as host1 and host2).

Isolation between these hosts must be provided by the non-PVLAN switch, using a feature such as protected ports on a Catalyst 2950. Promiscuous Private VLAN Trunk Ports Promiscuous private VLAN trunk ports are used in situations where a PVLAN promiscuous host port is normally used, but where it is necessary to carry multiple VLANs, either normal VLANs or multiple PVLAN domains. You can connect to an upstream router that does not support PVLANs, such as a Cisco 7200 router. Figure 7: Promiscuous PVLAN Trunk Ports In this illustration, a Catalyst 9k series switch connects a PVLAN domain to an upstream router, which does not support PVLANs.

Traffic being sent upstream by host1 arrives on the Catalyst 9k series switch in the community VLAN (VLAN 12). When this traffic is bridged onto the promiscuous PVLAN trunk towards the router, it is tagged with the primary VLAN (VLAN 10), so that it can be routed by using the correct subinterface configured on the router. Configuring Private VLANs Promiscuous Private VLAN Trunk Ports VLAN Configuration Guide, Cisco IOS XE 17.16.x (Catalyst 9300 Switches) 69