1 / 15

DHCPv6 Redundancy Considerations

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.

fallon
Download Presentation

DHCPv6 Redundancy Considerations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DHCPv6 Redundancy Considerations Redundancy Proposals in RFC 6853

  2. DHCPv4 Failover Protocol-level Redundancy Active ---------------- Active 192.168.234.56 172.16.123.45 Geographically separated DHCP Servers

  3. DHCPv6 Failover Internet Draft DHCPv6 Failover Design draft-ietf-dhc-dhcpv6-failover-design-04

  4. DHCPv6 Redundancy Considerations No Redundancy Protocol No Standards-based Failover RFC 6853 Deployment Models

  5. Assumptions 2+ Servers provide DHCPv6 to same Clients 2001:db8:bc:2::547 2001:db8:bc:1::547

  6. Assumptions DHCPv6 Servers are RFC 3315 compliant 2001:db8:bc:2::547 2001:db8:bc:1::547

  7. Assumptions DHCPv6 Replays are RFC 3315 compliant No direct Communication 2001:db8:bc:2::547 2001:db8:bc:1::547

  8. Assumptions Clients running statefulDHCPv6 2001:db8:bc:2::547 2001:db8:bc:1::547

  9. Assumptions Clients have to handle Preference Option 2001:db8:bc:2::547 2001:db8:bc:1::547

  10. 3 semi-redundant Deployment Models Multiple Unique Prefixes Split Pools 2001:db8:bc:2::547 2001:db8:bc:1::547 Identical Prefixes

  11. 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

  12. Multiple Unique Prefixes Multiple Prefixes within the Network No adjacent Pools needed Unique, non-overlapping Prefixes 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

  13. 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

  14. To sum it up. Failure & Restore Address Conflicts Interim Architecture Dynamic DNS

  15. Thank you for your time. Andreas Taudte Sales Engineer

More Related