UNSOLVED
CK
Clark kent
23 Posts
0
7972
March 25th, 2004 12:00
Basic Vlan question
Hello,
I'm finally ready to try the vlans on my network, but I need some help as I never did it before.
Let say I have 1 3048 connected with fiber from port 51 and 52 to 2 5224 on port 22 each. Then I have one Domain Controller Server connected to both 5224 on port 1 in Load Balancing with 2 NICs which are vlan aware. Finally both 5224 are connected together via a 4 port trunk on ports 17-20.
At the moment every ports are in the default vlan 1.
Now I want to add one PC on port 48 of the 3048 which should be in vlan 2 as it should not been seen by other PCs but it should be able, as any other PCs, to communicate with the domain controller.
The information I need is the following: which ports should be Tagged or Untagged and the NICs of the server should be Tagged or Untagged, and what PVID should I assign to any ports and to the NICs of the domain controller.
Of course STP is active on all switches.
GregM_1
2 Intern
•
112 Posts
119
0
Posted March 26th, 2004 19:00
You have many configurations to choose from so let me explain the basic configuration needed for VLANs, then we can discuss other setups.
Each edge device (such as the server and PC) will be in the untagged VLAN you want (say 2) with a matching PVID. If the VLAN needs to traverse through two or more switches, then the uplink ports will have the same VLAN added, but tagged (You will only use the PVID for untagged traffic).
In your case, you have a server with two VLAN aware NICs. Are they each in their own subnet? Do they need to be able to communicate with each other? Will the server be acting as a router?
If each NIC is in it's own subnet, even though it is VLAN aware, you only need to use its port as untagged w/ matching PVID. Since the traffic will only be one VLAN, there is no need to tag it to differentiate between VLANs. If, for example, you only had ONE NIC, you would HAVE to tag the port with both vlans (again, PVID will not matter for tagged) and have the NIC tagged as well.
Another scenario many people use is Port Overlap. This allows you to take multiple VLANs and let them share access to a common VLAN. People with a central server or single point of internet access use this ability. For example, you have Accounting in VLAN A, Sales in VLAN B, and Central Server in VLAN C. Accounting and Sales cannot have access to each other, but they both need access to the server, and there is no router. This could apply to your scenario.