Main Nav

Message from jhealy@logn.net

So we're starting to think about IPv6 (better late than never I always say), and some of the protocol changes that might take place on our network. One major one for us is DHCP. We currently provide DHCPv4 on all our public subnets so it's plug-n-play for our clients. We want to give them an address, configure a router, subnet mask, DNS server, and search prefix (and maybe NTP, WINS, etc). Our initial testing has shown that IPv6 covers much of this with its built-in features (though client support is another matter). Assuming a perfect client, though, we're pretty close. The one major change is that we would lose the ability to look up a MAC -> IP association that DHCP currently logs for us. Because clients would auto configure, we'd have to log these associations some other way so we could go back later and figure out who had a particular IP. I know we could just poll the switches (a la NetDisco) to get this info. Or we could mirror ff02::1 ICMP to a machine that collects the ND announcements and logs them. However, I'm hoping there's a programatic way (like, having the switch send us a trap when an ND association is made). I'd prefer not to poll/scrape if there's a more elegant solution. We're running Juniper EX gear on the core and edge, in case anyone has a solution that's vendor-specific. Finally, are there any other major drawbacks to ditching DHCP in v6 (besides the assignment of known, pretty, addresses)? Thanks, Jason ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.

Comments

I don't think IPv6 has a built-in way to deliver DNS servers without DHCPv6, or any other special options for that matter (TFTP boot servers, IP phone settings, etc)
 
We are currently running dual-stack, and IPv4 is providing this information for our network.  The plan is to eventually deploy DHCPv6 using our Infoblox system.
 
As for the IP/MAC/switchport mapping you talk about, we are using Nedi (www.nedi.ch) for this.
 
Cheers!
 
Tristan
 
--
Tristan Rhodes
Network Engineer
Weber State University
(801) 626-8549


>>> On 9/25/2012 at 1:07 PM, in message <81763DEE-7FD1-4035-B7F9-DD74FE643F47@logn.net>, Jason Healy <jhealy@LOGN.NET> wrote:
So we're starting to think about IPv6 (better late than never I always say), and some of the protocol changes that might take place on our network.

One major one for us is DHCP.  We currently provide DHCPv4 on all our public subnets so it's plug-n-play for our clients.  We want to give them an address, configure a router, subnet mask, DNS server, and search prefix (and maybe NTP, WINS, etc).

Our initial testing has shown that IPv6 covers much of this with its built-in features (though client support is another matter).  Assuming a perfect client, though, we're pretty close.

The one major change is that we would lose the ability to look up a MAC -> IP association that DHCP currently logs for us.  Because clients would auto configure, we'd have to log these associations some other way so we could go back later and figure out who had a particular IP.

I know we could just poll the switches (a la NetDisco) to get this info.  Or we could mirror ff02::1 ICMP to a machine that collects the ND announcements and logs them.  However, I'm hoping there's a programatic way (like, having the switch send us a trap when an ND association is made).  I'd prefer not to poll/scrape if there's a more elegant solution.

We're running Juniper EX gear on the core and edge, in case anyone has a solution that's vendor-specific.

Finally, are there any other major drawbacks to ditching DHCP in v6 (besides the assignment of known, pretty, addresses)?

Thanks,

Jason
**********
Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.

Message from jhealy@logn.net

Hi Tristan,

RFC6106 provides the framework for RA based DNS configuration

Regards,

Adrian Bucurica

Manager of Network Services 

Illinois Institute of Technology

Phone: 312-567-5238

Fax:       312-567-5968

 

 

From: Tristan Rhodes [mailto:TristanRhodes@WEBER.EDU]
Sent: Tuesday, September 25, 2012 4:39 PM
Subject: Re: IPv6 neighbor discovery vs DHCPv6

 

I don't think IPv6 has a built-in way to deliver DNS servers without DHCPv6, or any other special options for that matter (TFTP boot servers, IP phone settings, etc)

 

We are currently running dual-stack, and IPv4 is providing this information for our network.  The plan is to eventually deploy DHCPv6 using our Infoblox system.

 

As for the IP/MAC/switchport mapping you talk about, we are using Nedi (www.nedi.ch) for this.

 

Cheers!

 

Tristan

 

--
Tristan Rhodes
Network Engineer
Weber State University
(801) 626-8549


>>> On 9/25/2012 at 1:07 PM, in message <81763DEE-7FD1-4035-B7F9-DD74FE643F47@logn.net>, Jason Healy <jhealy@LOGN.NET> wrote:

So we're starting to think about IPv6 (better late than never I always say), and some of the protocol changes that might take place on our network.

One major one for us is DHCP.  We currently provide DHCPv4 on all our public subnets so it's plug-n-play for our clients.  We want to give them an address, configure a router, subnet mask, DNS server, and search prefix (and maybe NTP, WINS, etc).

Our initial testing has shown that IPv6 covers much of this with its built-in features (though client support is another matter).  Assuming a perfect client, though, we're pretty close.

The one major change is that we would lose the ability to look up a MAC -> IP association that DHCP currently logs for us.  Because clients would auto configure, we'd have to log these associations some other way so we could go back later and figure out who had a particular IP.

I know we could just poll the switches (a la NetDisco) to get this info.  Or we could mirror ff02::1 ICMP to a machine that collects the ND announcements and logs them.  However, I'm hoping there's a programatic way (like, having the switch send us a trap when an ND association is made).  I'd prefer not to poll/scrape if there's a more elegant solution.

We're running Juniper EX gear on the core and edge, in case anyone has a solution that's vendor-specific.

Finally, are there any other major drawbacks to ditching DHCP in v6 (besides the assignment of known, pretty, addresses)?

Thanks,

Jason
**********
Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.

********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.

********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.

Are there any shipping network products with this feature?

Thanks!

Sent from my iPhone