DHCP Failover and Redundancy Considerations for Networks
Explore DHCPv4 and DHCPv6 failover mechanisms, redundancy proposals, and deployment models outlined in RFCs. Learn about geographically separated DHCP servers, protocol-level redundancy, and unique prefix configurations for enhanced network reliability.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
DHCPv6 Redundancy Considerations Redundancy Proposals in RFC 6853
DHCPv4 Failover Protocol-level Redundancy Active ---------------- Active 192.168.234.56 172.16.123.45 Geographically separated DHCP Servers
DHCPv6 Failover Internet Draft DHCPv6 Failover Design draft-ietf-dhc-dhcpv6-failover-design-04
DHCPv6 Redundancy Considerations No Standards- based Failover No Redundancy Protocol RFC 6853 Deployment Models
Assumptions 2+ Servers provide DHCPv6 to same Clients 2001:db8:bc:2::547 2001:db8:bc:1::547
Assumptions DHCPv6 Servers are RFC 3315 compliant 2001:db8:bc:2::547 2001:db8:bc:1::547
Assumptions DHCPv6 Replays are RFC 3315 compliant No direct Communication 2001:db8:bc:2::547 2001:db8:bc:1::547
Assumptions Clients running stateful DHCPv6 2001:db8:bc:2::547 2001:db8:bc:1::547
Assumptions Clients 2001:db8:bc:2::547 2001:db8:bc:1::547 have to handle Preference Option
3 semi-redundant Deployment Models Multiple Unique Prefixes Split Pools 2001:db8:bc:2::547 2001:db8:bc:1::547 Identical Prefixes
Split Pools Simultaneously active and operational Unique, non- overlapping Pools Proprietary Mechanisms 2001:db8:bc:2::547 2001:db8:bc:1::547 Prefix = 2001:db8:bc:1::/64 Pool = 2001:db8:bc:1:0000::/65 Preference = 255 Prefix = 2001:db8:bc:1::/64 Pool = 2001:db8:bc:1:8000::/65 Preference = 0
Multiple Unique Prefixes Multiple Prefixes within the Network No Unique, non- overlapping Prefixes adjacent Pools needed 2001:db8:bc:2::547 2001:db8:bc:1::547 Prefix = 2001:db8:bc:1::/64 Pool = 2001:db8:bc:1::/64 Preference = 255 Prefix = 2001:db8:bc:5::/64 Pool = 2001:db8:bc:5::/64 Preference = 0
Identical Prefixes Same Prefix, Length & Pool Definition Overlapping Prefixes and Pools 2001:db8:bc:2::547 2001:db8:bc:1::547 Prefix = 2001:db8:bc:1::/64 Pool = 2001:db8:bc:1::/64 Preference = 255 Prefix = 2001:db8:bc:1::/64 Pool = 2001:db8:bc:1::/64 Preference = 0
To sum it up. Failure & Restore Address Conflicts Interim Architecture Dynamic DNS
Thank you for your time. Andreas Taudte Sales Engineer
