PurposeCommand or Action
singleprivate VLAN ID or a hyphenated range of private VLAN
IDs.
mapping 20 add 501-503
Entera secondary_vlan_list, or use the add keyword with a
secondary_vlan_listto map the secondary VLANs to the private
VLANpromiscuous port.
Usethe remove keyword with a secondary_vlan_list to clear
themapping between secondary VLANs and the private VLAN
promiscuousport.
Returnsto privileged EXEC mode.end
Example:
Switch(config-if)# end
Step 5
Verifiesthe configuration.
showinterfaces [interface-id]switchport
Example:
Switch# show interfaces gigabitethernet1/0/2
Step 6
switchport
Savesyour entriesin the switchstartup configuration file.copyrunning-config startup config
Example:
Switch# copy running-config startup-config
Step 7
Related Topics
PrivateVLANs Ports, on page88
Example:Configuring an Interface as a Private VLAN Promiscuous Port, on page 103
Mapping Secondary VLANs to a Primary VLAN Layer 3 VLAN Interface
Ifthe private VLAN will be used for inter-VLAN routing, you configure an SVI for the primary VLAN and
mapsecondary VLANs to theSVI.
Isolatedand community VLANs areboth secondaryVLANs.
Theprivate-vlan mapping interface configuration command only affects private VLAN traffic that is Layer
3switched.
Beginningin privileged EXEC mode, follow these steps to map secondary VLANs to the SVI of a primary
VLANto allow Layer 3 switching of private VLAN traffic:
Catalyst 2960-XR Switch VLAN Configuration Guide, Cisco IOS Release 15.0(2)EX1
OL-29440-01 99
Configuring Private VLANs
Mapping Secondary VLANs to a Primary VLAN Layer 3 VLAN Interface