The key is that you will have to route between the subnets. If your
switch is a layer 3 device it should be able to do that for you.
Otherwise you have to go through a router, either with separate physical
interfaces or logical subinterfaces. A router adds a bit of latency, so
you should try to keep the server and workstations that are going to be
communicating a lot on the same subnet.
One of the values in subnetting is keeping broadcast traffic local. It
makes sense to separate workgroups, such as school buildings within a
district, into their own VLANs when there is a lot of communication
between partners, but it makes less sense to place users and their
servers on different VLANs. I don't think it would be a good idea to put
a group of workstatioons and their default printer on different VLANs,
South Burlington High School
Cisco Networking Academy
From: School Information Technology Discussion
[mailto:[log in to unmask]] On Behalf Of Eric Hall
Sent: Monday, July 30, 2007 12:29 PM
To: [log in to unmask]
Subject: Multiple subnets
OK, we're growing and I think it's time to divide my network into
multiple subnets. I've done some searching around and have not yet come
up with a clear answer.
Specifically, I would hope to divide IP addresses into three subnets:
Servers/Printers ("system"), Workstations, Labs. We do not use DHCP so
that is not an issue. I would need machines on one subnet to
authenticate/file share from a Win2K server on another subnet, and print
by IP to that
("system") subnet as well. Will I need to do more than change the subnet
mask? VLANs on my switch (HP2524)? Other strategies?
Any thoughts or suggestions are welcome. Am I going to get too deep
trying to do this?
Washington West Supervisory Union
If you have not already done so, PLEASE NOTE my change of email address
[log in to unmask]
This email may contain information protected under the Family
Educational Rights and Privacy Act (FERPA) or the Health Insurance
Portability and Accountability Act (HIPAA). If this email contains
confidential and/or privileged health or student information and you
are not entitled to access such information under FERPA or HIPAA,
federal regulations require that you destroy this email without
reviewing it and you may not forward it to anyone.
This message has been scanned for viruses and
dangerous content by MailScanner, ClamAV and Bitdefender and is
believed to be clean.