When the primary VLAN is associated with and mapped to the secondary VLAN, any configuration on the primary VLAN is propagated to the secondary VLAN SVIs. For example, if you assign an IP subnet to the primary VLAN SVI, this subnet is the IP subnet address of the entire private VLAN. Private VLANs and Switch Stacks Private VLANs can operate within the switch stack, and private-VLAN ports can reside on different member switches in the stack. However, the following changes to the stack can impact private-VLAN operation:
• If a stack contains only one private-VLAN promiscuous port and the member switch that contains that port is removed from the stack, host ports in that private VLAN lose connectivity outside the private VLAN. • If an active switch that contains the only private-VLAN promiscuous port in the stack fails or leaves the stack and a new active switch is elected, host ports in a private VLAN that had its promiscuous port on the old active switch lose connectivity outside of the private VLAN. • If two stacks merge, private VLANs on the winning stack are not affected, but private-VLAN configuration on the losing switch is lost when that switch reboots.
Private VLAN with Dynamic MAC Address The MAC addresses learnt in the secondary VLAN are replicated to the primary VLAN and not vice-versa. This saves the hardware l2 cam space. The primary VLAN is always used for forwarding lookups in both directions. Dynamic MAC addresses learned in Primary VLAN of a private VLAN are then, if required, replicated in the secondary VLANs. For example, if a MAC-address is dynamically received on the secondary VLAN, it will be learnt as part of primary VLAN. In case of isolated VLANs, a blocked entry for the same mac will be added to secondary VLAN in the mac address table. So, MAC learnt on host ports in secondary domain are installed as blocked type entries.
All mac entries are learnt on secondary VLANs, even if the traffic ingresses from primary VLAN. However, if a MAC-address is dynamically learnt in the primary VLAN it will not get replicated in the associated secondary VLANS. Private VLAN with Static MAC Address Users are not required to replicate the Static MAC Address CLI for private VLAN hosts as compare to legacy model. Example: • In the legacy model, if the user configures a static MAC address, they need to add the same static MAC address in the associated VLAN too.
For example, if MAC address A is user configured on port 1/0/1 in VLAN 101, where VLAN 101 is a secondary VLAN and VLAN 100 is a primary VLAN, then the user has to configure mac-address static A vlan 101 interface G1/0/1 mac-address static A vlan 100 interface G1/0/1 • In this device, the user does not need to replicate the mac address to the associated VLAN. For the above example, user has to configure only mac-address static A vlan 101 interface G1/0/1 Configuring Private VLANs Private VLANs and Switch Stacks VLAN Configuration Guide, Cisco IOS XE 17.16.x (Catalyst 9300 Switches) 71