ProactionTech
asked on
Will adding a superscope to an in production DHCP server cause any loss of functionality of the original DHCP service?
Good morning experts!
I have a need to create a new superscope as an addition to an in production DHCP server. I will be doing this to use with a new VLAN I am creating for putting my wireless APs on and keeping wireless clients on the new VLAN.
Will creating a superscope onto the existing DHCP cause any down time or break in functionality of the service?
I have 3 VLANs that are each assigned to a different building (in walking distance). The buildings are connected via fiber and layer 3 switches. The switches are connected via trunk ports and all the 3 vlans are tagged on them.
Again the end goal is to have the wireless clients on their own (new) VLAN.
The APs should be on trunk ports as well if I am not mistaken.. but I am also not sure if I should tag all of the vlans on these ports too.. I guess I would need to tag all VLANs so they could reach other network segments.
Any help would be appreciated!
I have a need to create a new superscope as an addition to an in production DHCP server. I will be doing this to use with a new VLAN I am creating for putting my wireless APs on and keeping wireless clients on the new VLAN.
Will creating a superscope onto the existing DHCP cause any down time or break in functionality of the service?
I have 3 VLANs that are each assigned to a different building (in walking distance). The buildings are connected via fiber and layer 3 switches. The switches are connected via trunk ports and all the 3 vlans are tagged on them.
Again the end goal is to have the wireless clients on their own (new) VLAN.
The APs should be on trunk ports as well if I am not mistaken.. but I am also not sure if I should tag all of the vlans on these ports too.. I guess I would need to tag all VLANs so they could reach other network segments.
Any help would be appreciated!
asavener
Can you advise why you want to create a superscope rather than just adding a regular scope for the new VLAN?
ASKER
Yes, I wanted to do this on an existing DHCP server (dont want to create a new server) but want to give a different subnet..
So I currently have
192.168.0/23 vlan 100
192.168.2.0/23 vlan 200
192.168.4.0/23 vlan 300
and I want to create 192.168.8.0/23 for wireless clients only (might be getting a new additional building soon so wanted to leave open .6.0/23)
This would be vlan 500 (the .8.0/23)
Is there another way to keep this on an existing DHCP server without having to create a superscope?
So I currently have
192.168.0/23 vlan 100
192.168.2.0/23 vlan 200
192.168.4.0/23 vlan 300
and I want to create 192.168.8.0/23 for wireless clients only (might be getting a new additional building soon so wanted to leave open .6.0/23)
This would be vlan 500 (the .8.0/23)
Is there another way to keep this on an existing DHCP server without having to create a superscope?
ASKER
The DHCP server I wanted to add the new scope to is on VLAN 300 only. Forgot that detail.
Would a better option be to add a virtual network adapter to the existing DHCP server and plug it into a port that I tag with the new wireless VLAN and then cofigure the network adapter to use the new segment?
Would a better option be to add a virtual network adapter to the existing DHCP server and plug it into a port that I tag with the new wireless VLAN and then cofigure the network adapter to use the new segment?
Sure, you can do this. Just add a new scope (not a superscope) with the appropriate options (default gateway, DNS servers, etc.), and when you configure the VLAN on the router, you add this DHCP server as the IP helper.
Check the router that serves these existing VLANs and you should see an entry referencing the IP address of the DHCP server.
Check the router that serves these existing VLANs and you should see an entry referencing the IP address of the DHCP server.
ASKER
Ok so creating a new scope in production DHCP server wont cause any confusion with existing and new clients right? Like it wont try and give out IPs from this new scope to the people who are supposed to be getting an IP from the current existing scope?
So should I tag the ports that the APs are connected to with ONLY the new wireless VLAN or should these be connected to a trunk port? If its supposed to be connected to a trunk port how will it know to use the new VLAN when wireless clients connect?
And the clients connecting to the wireless APs will know to use the helper because they send a special header with the request that identifies it came from the helper right?
Thanks for help so far. If anything I just asked is confusing just let me know and I will clarify.
So should I tag the ports that the APs are connected to with ONLY the new wireless VLAN or should these be connected to a trunk port? If its supposed to be connected to a trunk port how will it know to use the new VLAN when wireless clients connect?
And the clients connecting to the wireless APs will know to use the helper because they send a special header with the request that identifies it came from the helper right?
Thanks for help so far. If anything I just asked is confusing just let me know and I will clarify.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your help.