Question : Network Design IP Scheme

I have a large network that is on a 192.168.0.x - 192.168.6.x  255.255.0.0 network addressing scheme. I am adding a new location and would like to change my IP scheme starting at the new location. I will change the older location serveral months down the line.

At location 1 -old

We have 9 servers that preform verious funtions DCs, Exchange 2007, Application, files. (3 DCs, and 3 DNS servers, 1 exchange)
Sonicwall NSA and 3 t1.s

At the Location -2 New

We will have 4 servers (2 DCs, DNS 2 File)
400 computers and could grow along with servers.
Sonic wall NSA amd 3 t1s

The buidings will be linked together via private fiber and will be connected via Dell 6224 switches and both locations will have separate internet access. Location 2 only need to access e-mail and AD replication from location 1. They will both have their own DHCP server.


Should I setup separate VLans? Should they be trunked?

What IP Scheme do you recommed?

Should I change the IP Scheme or continue with 192.168.10.x  - 192.168.x.x????

Thanks,

Answer : Network Design IP Scheme

I personally prefer to use the 10.x.x.x network for my networks. You could also use 172.16.x.x - 172.31.255.255 and of course 192.168.x.x.

I recommend that you create VLANs (preferably trunked as this requires less switch work), however you can setup the ports to be static but if you move devices you will need to reconfigure the switch. All server NICs have the ability to specify a VLAN ID so ensuring the server is on the right VLAN is simple.

As for VLAN design, I would recommend that VLANs be created based on location, and then function. The table below is a quick example of how you could divide your network into VLANs.

Function           Location         VLAN
Servers             Extranet          10.50.x.x
Servers             Internal           10.40.x.x
Clients              Wired              10.30.x.x
Clients              Wireless        10.20.x.x
Guests              Wireless        10.100.x.x

Larger organizations will also separate departments into their own VLANs, for instance, Accounting, HR, Development, Engineering, Management, etc. With 400 users this may be more work than it is worth.

Another benefit of VLANs is simplified firewall management. If you have servers in the Extranet that you don't want to reach the intranet, if they are on different VLANs you can simply block traffic from the entire subnet instead of one by one.