james_daley
asked on
Suggestions about network design - DHCP multiple subnets
Hi Everyone,
I'm designing a network for around 3 servers (The DC is the DHCP Server), 25 Workstation, 25 IP Phones, 1 router, 1 NAS and a few other network devices.
I'd like to setup the DHCP Server to hand-out IP's depending on which switch it's attached to.
I'd also like setup each group of devices to be in a specific IP range (see below).
Servers: 192.168.0.1 - 255
Workstations: 192.168.1.1-255
NAS/SAN Enironment: 192.168.2.1-255
Other Network Devicess ( Printers etc): 192.168.3.1-255
IP Phones and PABX: 192.168.4.1-255
Currently we have a number of unmanaged switches for the workstations and IP Phones (these are seperate, meaning the traffic is physically seperated until it reaches the main switch) which run uplinks back to the Comms Room into the main switch (unmanaged).
The servers use a HP Managed Switch which also connects to the main switch.
And finally we have all other network devices patched back into main switch.
The router connects directely into the main too. And it connects out to our modem as well.
All workstations/servers use the router as a gateway, and use our DC as our DNS address (It has a DNS running already).
I would like our DHCP Server to distribute IP based on which switch I plug the device into.
I'm not sure exactly how to set this up with multiple subnets etc. Currently all IP are using a subnet mask of 255.255.0.0 so everything can see everything (which is what I want it to stay).
Could someone please provide any suggestions/options as to whether this is possible and how to acheive this?
Also if you could provide subnetting suggestions to, that would be greatly appreciated.
Thank you everyone in advance.
I'm designing a network for around 3 servers (The DC is the DHCP Server), 25 Workstation, 25 IP Phones, 1 router, 1 NAS and a few other network devices.
I'd like to setup the DHCP Server to hand-out IP's depending on which switch it's attached to.
I'd also like setup each group of devices to be in a specific IP range (see below).
Servers: 192.168.0.1 - 255
Workstations: 192.168.1.1-255
NAS/SAN Enironment: 192.168.2.1-255
Other Network Devicess ( Printers etc): 192.168.3.1-255
IP Phones and PABX: 192.168.4.1-255
Currently we have a number of unmanaged switches for the workstations and IP Phones (these are seperate, meaning the traffic is physically seperated until it reaches the main switch) which run uplinks back to the Comms Room into the main switch (unmanaged).
The servers use a HP Managed Switch which also connects to the main switch.
And finally we have all other network devices patched back into main switch.
The router connects directely into the main too. And it connects out to our modem as well.
All workstations/servers use the router as a gateway, and use our DC as our DNS address (It has a DNS running already).
I would like our DHCP Server to distribute IP based on which switch I plug the device into.
I'm not sure exactly how to set this up with multiple subnets etc. Currently all IP are using a subnet mask of 255.255.0.0 so everything can see everything (which is what I want it to stay).
Could someone please provide any suggestions/options as to whether this is possible and how to acheive this?
Also if you could provide subnetting suggestions to, that would be greatly appreciated.
Thank you everyone in advance.
ASKER
Hi Packetguy,
Firstly, thank you for your reply.
I had a quick look at our existing router, and it already supports vlans. Its a Snapgear SG580 router.
I'd be interested in using this router before spending any money. I has 4 LAN ports which can be seperated into a per port/vlan. Perhaps this will do?
You were saying that we'd need to replace all unmanaged switches with managed ones, could we use our unmanaged switches to connect the same devices, then physically seperate the uplink and run it into a managed switch (which can be used as the backbone)? <- We could purchase this managed switch.
I'm thinking this will reduce cost and setup etc. We've currently got our workstations and IP Phones physically connected to different unmanaged switches which runs to the backbone managed switch.
Thanks for all your help,
Cheers,
James
Firstly, thank you for your reply.
I had a quick look at our existing router, and it already supports vlans. Its a Snapgear SG580 router.
I'd be interested in using this router before spending any money. I has 4 LAN ports which can be seperated into a per port/vlan. Perhaps this will do?
You were saying that we'd need to replace all unmanaged switches with managed ones, could we use our unmanaged switches to connect the same devices, then physically seperate the uplink and run it into a managed switch (which can be used as the backbone)? <- We could purchase this managed switch.
I'm thinking this will reduce cost and setup etc. We've currently got our workstations and IP Phones physically connected to different unmanaged switches which runs to the backbone managed switch.
Thanks for all your help,
Cheers,
James
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
james_daley, did this address your issues? Points, man, I need points! ;)
-mel
-mel
ASKER
SOrry packetguy, yes it sure did.
Thank you for your help :)
Thank you for your help :)
So the question is, before I or somebody else spends time on a VLAN tutorial, are you prepared to go that route (as it were ;). You'll need one Layer-3 switch (an HP will do, but Cisco is better because it's more plentiful and there is more talent readily available), and you'll need to replace all your unmanaged switches with managed VLAN-capable switches (used Cisco 2948s can be had for $100 on eBay; they're perfect for this application).
To reliably deploy VoIP you generally must have VLAN traffic isolation. Otherwise simple YouTube videos and the like will overrun your voice traffic and kill voice quality.
Once you have a solid VLAN network in place, then I am happy to explain the details of using the DHCP Helper settings in Cisco routers, and how to configure multiple DHCP scopes on your DC. It's straightforward, but you have to have a good foundation or you'll just end up with a garbage network.