I don't know whether or not to put printers on a seperate Vlan, what would you think.
Also, we are running a 10.68.x.x ip range, from reading some of the other posts on here i've come to the conclusion that i'll have to create subnets for each of my 10 Vlans, is this correct. I want to have all my Vlans routing on the switch through to the servers vlan for dhcp (so ip helper-address i think on all the other vlans).
How would I go about setting this up?
Would I create scopes for each subnet on my DHCP server so that they could assign ip addresses to the clients on each vlan? And this may sound a bit silly, but what ip address do I put in for each default gateway? Is it the ip address that gets assigned to the Vlan on the switch?
Yes, add a printer VLAN, they are terrible culprits for broadcast traffic.
Yes, split into subnets.
You need to set a route up on the switch for each VLAN and set an IP address for the switch in each VLAN. In each VLAN you want to use DHCP you want to add an IP helper address pointing to your DHCP server. You also want to add an IP helper address to any server that you use for PXE boot such as a windows deployment server.
On your DHCP server, yes set up seperate scopes. Have the default gateway as the IP address of the switch in that IP range.
Thanks for that, can i just check one more thing, currently we have a subnet of 255.255.252.0 which has a masive range. This is set as one DHCP scope. If I create scopes for each Vlan on the DHCP server, do I then remove this current subnet and scope?
Also, I read somewhere that you have to enter the subnets in AD sites and services, is this true?
Thanks for that, can i just check one more thing, currently we have a subnet of 255.255.252.0 which has a masive range. This is set as one DHCP scope. If I create scopes for each Vlan on the DHCP server, do I then remove this current subnet and scope? Yes, the easy way is to use a different private IP range if that's possible, especially if you're working on this with the network live.
Also, I read somewhere that you have to enter the subnets in AD sites and services, is this true? Yes
I think what i'll do is get everything setup on a test server running DHCP in a test enviornment, and then when everything is woking fine I can implement it during the summer holidays.
The Admin Vlan will be getting it's DHCP lease from a different range, 10.120.x.x, which is what we have been allocated for our admin domain, so i'm thinking that I would leave that domain as it is for the time being, with the server being a member of the 2 vlans we currently have, curric and admin, so it can send DHCP via it's 10.120.x.x address to admin clients and also allow SIMS to be used by curric clients.
It works that way at the moment, with no routing in place on the current core, would that just be the same, or would I be better off setting up ip helper address for the admin vlan to point to the 10.120.x.x adaptor in the admin dc.
Leave it as it is, it's more secure, unless of course you want to start messing with Access Control Lists on the switches, which you may want to do anyway to prevent traffic routing between client VLANS.
Yep, that's about right, the ip helper address wants to point to the ip address of your DHCP server, the ip address wants to be an address within the range you have assigned to that VLAN (I tend to use the first IP address in the range) and the ip rip address should be the ip address you've set in the ip address line. The ip rip command enables routing in the vlan and igmp enables multicasting, prob won't need that.