Register now or log in to join your professional community.
Scope for singlenet while superscope (group) is used when you have a MULTINET-- more than one 'logical subnet' on the same 'physical subnet or segment of wire'.
Basm allah alrahman alrahim
Some Extra Complete To My Friend Muhammad Yuseef
Superscopes can resolve specific types of DHCP deployment issues for multinets, like :
I love Network Protocols
A superscope is an administrative feature of Dynamic Host Configuration Protocol (DHCP) servers running Windows Server 2008 that you can create and manage by using the DHCP Microsoft Management Console (MMC) snap-in. By using a superscope, you can group multiple scopes as a single administrative entity. With this feature, a DHCP server can:
In multinet configurations, you can use DHCP superscopes to group and activate individual scope ranges of IP addresses used on your network. In this way, the DHCP server can activate and provide leases from more than one scope to clients on a single physical network.
One of the biggest advantages of creating superscopes is to ease administration of a multinetted environment. Identifying which scopes go with which networks can be a difficult administration task. Creating superscopes and grouping scopes in some logical manner can make them easier to administer; for example, grouping all the scopes from a single floor in a large office building into a superscope eases the administration process.
Superscopes are also used to support DHCP clients on a single physical network segment (such as a single Ethernet LAN segment) on which multiple logical IP networks are used. When more than one logical IP network is used on each physical subnet or network, such configurations are called multinets .
Let me start by saying that Superscopes are not a standard mechanism of DHCP, just a “hack” by Microsoft to support networks that don’t understand the concept of “1 IP subnet PER vlan, not 10 IP subnets per VLAN”. The only, and I do mean ONLY, time that you use Superscopes is when you have a network design that has multiple IP subnets inside the same VLAN. Let me explain the ONLY instance where this is needed and WHY you need multiple interfaces configured for this to work…
Superscopes are used when you have one network segment where you want to issue IPs from more than one subnet. IPs from the first scope will be assigned, then when full, the IPs from the next scope will be assigned. For this layout to work, you also have to have (for this scenario) multiple gateway interfaces defined on the router’s interface servicing this network segment.
In today’s modern networks, I think it may be more appropriate to create multiple VLANs, use a relay agent, and set up individual scopes on the DHCP server.
A scope is an administrative grouping of IP addresses for computers on a subnet that use the DHCP service. The administrator first creates a scope for each physical subnet and then uses the scope to define the parameters used by clients.
A superscope is an administrative feature of DHCP servers running Windows Server that you can create and manage through the DHCP console. Using a superscope, you can group multiple scopes as a single administrative entity.
A Scope typically define a single physical subnet on your network to which DHCP services are offered. Scopes are the primary way for the DHCP server to manage distribution and assignment of IP addresses and any related configuration parameters to DHCP clients on the network.
A superscope is actually a collection of individual scopes. When you group different scopes together into a single superscope, you can do the following:
agree with expert answer
i'm not specialist on this filed
