Showing results for 
Search instead for 
Did you mean: 

Nexus 5000 - Private Vlan configuration

Daniel Anderson
Level 1
Level 1


I have a Nexus 5000 Switch sat between 2 Routers on which I'm trying to configure Private Vlans. Vlan 1111 is configured as the Primary Vlan configured on the Upstream Port (Eth1/21) to Router A, Router A is configured with an IP address of

I'm then trying to configure a downstream port (Eth1/23) to act as the downstream trunk port to Router B, which is where I'm encountering issues. I have tried multiple configurations for a Private Vlan trunk, but I feel I coming across limitations in the way the 5000s run Private Vlans - The error below suggests that Community Vlans cannot be mapped to a Trunk Port.

5KSwitch(config-if)# switchport private-vlan association trunk 1111 1112
ERROR: Ethernet1/23 : Community vlan cannot be mapped on a secondary trunk port

Given that the above error seems to suggest that only isolated vlans can be mapped on a trunk port, I have tested using an isolated Vlan mapped to the Primary Vlan and whilst I'm able to trunk the isolated Vlan down the downstream trunk, I'm only able to create a single isolated per Primary Vlan which seems quite limited configuration wise, as given it being a trunk port, I'd like to send multiple Vlans down the link.

5KSwitch(config-vlan)# ex
ERROR: Primary vlan 1111 cannot be associated with more than 1 isolated vlan.
ERROR : cli_process_vlan_config_exit(295), command private-vlan association 1112-1114 FAILED
Cannot run commands in the mode at this moment. Please try again.

Switch Version is 7.2(0)N1(1)

Has anyone encountered similar issues - Were you able to implement a workaround?


1 Reply 1

I did not encounter the exact same issue, but I have seen the same error message on a Nexus 5548 when trying to name a VLAN with a name that was already assigned to another VLAN.


Switch(config)# vlan 455
Switch(config-vlan)# name gem41611-LIC
Switch(config-vlan)# exit
ERROR: VLAN with the same name exists

ERROR : cli_process_vlan_config_exit(295), command name gem41611-LIC FAILED
Cannot run commands in the mode at this moment. Please try again.

This VLAN already existed with the same name


Switch(config)# sh run vlan 310

!Command: show running-config vlan 310
!Time: Tue Jun 11 12:59:10 2024

version 7.1(4)N1(1)
vlan 310
  name gem41611-LIC



After deleting the VLAN 310, naming the VLAN 455 works fine.

swarsdataguard1(config)# vlan 455
swarsdataguard1(config-vlan)# name gem41611-LIC
swarsdataguard1(config-vlan)# exit



CCIE #37979 (R/S)
Review Cisco Networking for a $25 gift card