cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
185
Views
0
Helpful
1
Replies

Isolated PVLANs on Cisco 3750

san ju.
Level 1
Level 1

Hello Team,

I've created this switch script to add new clients to my network. I will provide them with dedicated servers that need to be isolated, ensuring they cannot see each other's traffic. Below is the configuration.

!Primary VLAN 333

vlan 333
 private-vlan primary
 private-vlan association 334,335

!Secondary VLAN 334 (Isolated for Client 1)

vlan 334
 description Isolated VLAN for Client 1
 private-vlan isolated

!Secondary VLAN 335 (Isolated for Client 2)

vlan 335
 description Isolated VLAN for Client 2
 private-vlan isolated

!Configure the ports for Client 1 (VLAN 334)

interface Gi1/0/1
 switchport mode private-vlan host
 switchport private-vlan host-association 333 334
 description Client 1 Port - Isolated to VLAN 334

!Configure the ports for Client 2 (VLAN 335)

interface Gi1/0/2
 switchport mode private-vlan host
 switchport private-vlan host-association 333 335
 description Client 2 Port - Isolated to VLAN 335

I haven’t configured an SVI for the primary vlan on this 3750 and do not want to create it. The gateway for the secondary isolated PVLANs should be the router IP. The router is running on a Dell server connected to another Nexus 6k switch on Proxmox VE, and this Nexus switch is not running any PVLANs.

Note:
On this 3750, I have a few clients that do not require an isolated network and are successfully using the router IP as their gateway.

My Concern is:

Where should I configure the promiscuous port, or is the current configuration sufficient for the secondary isolated VLAN to communicate with the router IP?

I’ve received a lot of valuable help from this community so far, and I would really appreciate it if anyone could assist me in resolving this concern.

Thanks,

Punkn

1 Reply 1

chrihussey
VIP Alumni
VIP Alumni

Hello, 

For starters, I believe you can only have a single isolated VLAN in a PVLAN domain. If however, you create multiple community VLANs and only assign them to one user port that would be a viable work around if it won't get out of control. Also, if I understand your post, the secondary private VLANs are not associated with any L3 interfaces. They must use the L3 interface associated with the primary VLAN.  

Hope this helps

Review Cisco Networking for a $25 gift card