05-29-2021 01:10 AM - edited 05-29-2021 01:13 AM
Dear All,
I have an issue configuring PVLAN Trunk for a server that it's not able to configure private vlan itself.
This mean following the theory that a private vlan trunk needs to be configured between the switch that is able to configure the pvlan association and the device that is not able to configure it.
I´ll need that the configured trunk against the server can support normal traffic vlan 100 and vlan 102 and be able to associated vlan 102 to the vlan 101 and send that information to the core switch to maintain the pvlan association.
Normal vlan ID 100
Primary vlan 101
Isolated vlan 102
The OS of the switch NXOS: version 9.3(1)
and the configuration looks like:
interface Ethernet1/1
switchport
switchport mode private-vlan trunk promiscuous
switchport private-vlan trunk allowed vlan 100,102
switchport private-vlan association trunk 101 102
switchport private-vlan mapping trunk 101 102
05-29-2021 02:09 AM
05-29-2021 02:22 AM
Thanks but that´s for configure a port as a host (access mode) not as a trunk.
My situation is to configure the port to work as a trunk that carries normal traffic plus the associated isolated vlan and the trunk re-tag this as a pvlan associationg when communicating with the gateway
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide