So now we're going to configure a DHCPv6 server on Windows Server 2012.
You'll notice this is the same DHCP server that we used for DHCPv4.
It's funny how that works I guess.
So at any rate,
first we'll set up a stateless DHCP server simply
because it's a lot easier to do so.
Now you'll remember the difference between stateless and stateful is that
stateless only gives out configuration information,
it does not actually hand out any IP addresses,
so all you have to do to a DHCPv6 server on Server
2012 is configure the server options.
Here you right-click the Server Options,
you say Configure Options,
and this is where you configure the DNS Recursive Name Server IP address,
the Domain Search List, so on and so forth.
So I'll go in here and as an example enable the Domain
Search List and I'll put in globomantics.
com, hit Apply, and OK, and congratulations,
you now have a stateless DHCPv6 server on Windows Server.
Now you still have to go to all of the routers or switches
that are on your IPv6 segments if there's more than one
IPv6 segment on your network, and turn on the O flag,
or the Other Configuration Information Flag,
and possibly setup a DHCP relay pointing at this DHCP server.
We'll look at how to do that on the Cisco side here in just a bit.
To set up a stateful DHCPv6 server it's just about as simple.
You simply right-click IPv6 and you say New Scope,
and we'll go through the scope setup wizard real quickly here,
so we'll name this scope Test, with a description of Test like so,
give it a prefix of fdee and a double colon,
just because I don't feel like making up 3 or 4 more octets of IPv6 data there,
and we'll hit Next.
This is where we can add exclusions.
Again, it looks just exactly like the DHCPv4 setup.
In this case, we'll say exclude addresses 1 to 100, hit Add.
Here is the timing information for the non-temporary addresses.
You'll notice that we have a Preferred Life Time and a Valid Life Time.
The Preferred Life Time is how long should this address last
before you start asking for another one.
It's essentially the T1 timer.
The Valid Life Time is essentially the T2 timer on IPv6.
After this timer expires the address is no longer valid
and you have to somehow go find another address if you
can't contact this DHCPv6 server.
Even though it doesn't say it on the screen,
the Valid Life Time should be equal to or greater than the Preferred Life Time.
Again, that's pretty common sense.
You want an address to expire after it becomes non-preferred to give your
client some time to actually contact the DHCP server if need be.
In this case, we'll just leave it as the defaults,
hit Next, and it asks if we want to activate the scope now,
we'll go ahead and hit No because I don't want to be handing out DHCPv6
addresses on my network and potentially breaking it.
And you'll notice that we now have our Scope here.
If we expand the Scope, it looks just like the IPv4 Scope that we have up here.
In fact, I'll go ahead and expand it out.
Other than the Address Pool, we have Leases,
Exclusions, Reservations, and Scope Options.
If we look at Scope Options,
again there's the option that was set up at the root of the server,
but we can also configure more options here if we so desired.
And that's pretty much it.
Just like with DHCPv4, it's very simple to set up a DHCPv6 server on the network,
at least on Windows Server, and so we will move on to configuring it on a Cisco router.