If all of the clients need to be prevented from communicating with each other, you should not be using the same VLAN IDs on the second switch as you used on the first. By doing so, you would allow the clients with the same VLAN ID on both switches to communicate with each other.
If you are using a separate VLAN for all ports, you should create all 48 VLANs in the VLAN database on both switches. The trunk ports need to be tagged for all 48 VLANs. The general mode ports would be untagged on their own VLAN and that of the gateway (VLAN 2, in this case) with the PVID set to their specific VLAN ID. The port for the gateway would need to untagged on all 48 VLANs with a PVID of 2.
GregG1
2 Intern
•
812 Posts
0
March 9th, 2004 11:00
If all of the clients need to be prevented from communicating with each other, you should not be using the same VLAN IDs on the second switch as you used on the first. By doing so, you would allow the clients with the same VLAN ID on both switches to communicate with each other.
If you are using a separate VLAN for all ports, you should create all 48 VLANs in the VLAN database on both switches. The trunk ports need to be tagged for all 48 VLANs. The general mode ports would be untagged on their own VLAN and that of the gateway (VLAN 2, in this case) with the PVID set to their specific VLAN ID. The port for the gateway would need to untagged on all 48 VLANs with a PVID of 2.