"NewsReader" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Which is more efficient for a smaller operation
> with about 60 users 5 servers. Our goal is to put
> office and production in their own network just using
> say a 10.1.30.0 and a 10.1.31.0 network. with
> routing and subnetting thru the switch. Somebody else
> just advised us to use a V-lan instead. What is the diff and which is
> best
> for a smaller environment like this.
You don't really need a second subnet until you get close to 200+ hosts.
Unless you are going to use ACLs on a LAN Router between the segments for
some sort of secret security mission,...there is no real point in it. There
is no bandwidth benefit in doing so. A fully switched network already
isolates every converstation between two hosts into its own "virutual
circuit". Separating into Layer3 segments (routing) only reduces the
effect of Broadcasts which is not going to be an issue until you get over
200 hosts.
But if you want to:
It requires a LAN Router. This may be a standalone device or can be a
Layer3 Switch (not to be confused with a normal Layer2 Switch) which is a
LAN Router and a Network Switch built into the same piece of hardware. They
usually have the Routing Functionality disabled by default so it just acts
as only a Switch.
Layer3 Switches use VLANs internally within the Switch to "group" the
Switch's ports into LAN Segments (same thing as a VLAN). Each "group" of
ports acts as a single "Router Interface". Most of the time in a simple
situation such as yours the VLANs exist *only* within the Switch, while
everything outside of the switch are just normal *physical* segments.
Once the VLANs are created within the Switch and the chosen ports are
assigned to the chosen VLAN,...the routing functions of the Switch are
enabled. There usually isn't anything special to do, you just enable it.
Then you configure DHCP Helper Addresses in the Switche's routing functions
and point this to your DHCP Server.
On your DHCP Server you simply create an additional separate, distinct scope
for the new segment you are adding (do not create a superscope!). That is
all there is on the DHCP Server to do. The Router gives the DHCP all it
needs to know to give the right address out from the right scope to the
right client.
Your "Internet sharing device" (whatever that may be) will require a Static
Route added to it that tells it to use the LAN Router as the "path" to get
to the new subnet that is on the opposite side of the LAN Router. If this
device is not capable of that then you will have to throw it out and replace
it with one that can.
All hosts on the LAN will all switch to using the LAN Router as the Default
Gateway and will use the Router's IP# that directly faces them. The LAN
Router will then, in turn, use your "Internet sharing device" as its Default
Gateway.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Similar Threads
Linear Mode
