WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
Paul, since you seem to be somewhat more familiar with VLAN business than most of us, I have a query for you. I have read that for switching betwen 2 VLAN's you require a L3 switch. Is this correct ?
No this is not true you require a L3 device as the VLANS will be on different subnets. A L2 switch with a router will do the same job but they both have to support VLAN. Depending upon your application will depend upon what is required if you need any more help tell me more about the setup and the reasons for VLAN implementation.
No this is not true you require a L3 device as the VLANS will be on different subnets. A L2 switch with a router will do the same job but they both have to support VLAN. Depending upon your application will depend upon what is required if you need any more help tell me more about the setup and the reasons for VLAN implementation.
A L2 switch with VLAN capability would do the job (no router) ?
Just curious. Haven't implemented VLAN's yet and wouldn't start in hurry unless I know what I am doing & why I am doing it.
You might want to ask the questions:
Why are they insisting on Vlan?
How much traffic is going to be on these devices?
Vlans are essentially used to break up broadcast domains and institute a basic amoun of network security. If you group employees by department you can limit a departments access to resources by creating an access control list based on their subnet, among other things.
In a small office, they're not usually that necessary, and in a bigger office, I'd hope they could swing slightly better equipment (you can get 2600 series routers new for $300 on ebay)
Luckily the 1721 will actually work for this, but its not a very beefy router. Enabling a lot of vlans on it will really strap its resources. Essentially any traffic from one vlan destined for another travels to the switch then out to the router, then back to the switch to the proper vlan. Conveniently this is the focus of my entire semester at college right now
Your vlans appear to be set up fine. If you enable trunking on the port connected to the router:
switchport mode trunk
switchport trunk encapsulation dot1q
then on the routers main interface:
no shut the interface, and then create subinterfaces like this:
int fa0/0.11
this wil be the logical interface for vlan 11. its good to number your subinterfaces the number of the vlan they are, helps to organize them.
use the command:
encapsulation isl (or dot1q, the 2600s use dot1q, the 1900s use isl, not sure what the 1700s use)
ip address x.x.x.x. m.m.m.m
this address will become the gateway for all hosts on that subnet.
Then set them up with whichever routing protocol you're using and you should be good to go.
the main interface may require you put in an IP prior to configuring subinterfaces, just put in a regular one (normally matching vlan 1s subnet, as this is the management subnet)
