Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Starting a New Segmented Network 2

Status
Not open for further replies.

Whitewolfz

IS-IT--Management
Feb 24, 2010
5
US
I am a newbie to the segmented network issues. I now have a flat network with around 15 3com 2948 switches. Yeah, I know it isn't smart, well, it is that I've just recently realized that. I am about to tackle this issue and I am looking at putting a 3com Superstack 4400 in as the core and starting the vlans at 0. Can anyone suggest a help file that will get me on the right track? Also, I will be handing out DHCP on a subnet of 255.255.252.0 and utilizing the ranges of .100,101,102,103.
Does it seem like I've bitten off too big of a chunk, or what?
I realize I need to do a great deal more research and fact finding, and that VLans start at 1. That part has already been addressed.
Thanks,

Ken
 
What are you going to use as a router? Once you break up your network into VLANs you need a way to route data between them. I would use at least a 4500 as my core.

At a glance it would seem you're in over your head. Try getting a Network+ cert before attempting. At least you will have some basic networking training at that point.

Have fun! [pipe]
 
Make your VLAN IDs match your subnets - VLAN 101 has subnet 101, VLAN 102 has the subnet 102, etc...all with a 255.255.255.0 mask.

Basically 1 subnet = 1 VLAN.

Also we no longer use VLANs to separate people into "Sales" and "Accounting" as per the old textbooks - now it's purely separation by geography - so make each of your VLANs span as few switches as possible and make as few VLANs exist on each switch as possible.

Think of a star - each VLAN/subnet is one stub off your "core" which is a layer-3 switch which has the default GW for each subnet and an IP-helper/DHCP-forwarder to connect each to your DHCP server.
 
I appreciate all of the suggestions. I realize this will be a daunting task but not undo-able.
Thanks again,


Ken
 
It's not that hard. You just need to make sure you've planned it out thoroughly with no loose ends. Correctly planning and implementing your project ensures your customers are taken care of and don't fall through the cracks. It also should make you familiar with your equipment and the roles each device plays in your environment.

Have Fun! [pipe]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top