Dell PowerEdge M520 Dell PowerConnect M6220/M6348/M8024 Switches Configuration - Page 131

DHCPv6 Prefix Delegation Scenario, Enable DHCPv6

Get Dell PowerEdge M520 PDF manuals and user guides View all Dell PowerEdge M520 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 131 highlights

causes DHCPv6 clients to send the DHCPv6 "Information Request" message in response. A DHCPv6 server then responds by providing only networking definitions such as DNS domain name and server definitions, NTP server definitions, and/or SIP definitions. RFC 3315 also describes DHCPv6 Relay Agent interactions, which are very much like DHCPv4 Relay Agents. Additionally, there is a DHCPv6 Relay Agent Option Internet draft [9], which employs very similar capabilities as those described by DHCPv4 Relay Agent Option in RFC 2132. With the larger address space inherent to IPv6, addresses within a network can be allocated more effectively in a hierarchical fashion. DHCPv6 introduces the notion of "prefix delegation" as described in RFC 3633 [8] as a way for routers to centralize and delegate IP address assignment. The following diagram depicts a typical network scenario where prefix delegation is used. Figure 6-2. DHCPv6 Prefix Delegation Scenario PE Router DHCPv6 PD Server CPE Router DHCPv6 PD to Client DHCPv6 Server DHCPv6 Server Host DHCPv6 Client Host DHCPv6 Client General Prefix (such as /48) General Prefix (such as /64) In Figure 6-2, the PE router acts as Prefix Delegation server and defines one or more "general" prefixes to delegate to a CPE router acting as a Prefix Delegation client. The CPE router then can then allocate more specific addresses within the given general prefix range to assign to its local router interfaces. The CPE router can in turn use the given general prefix in allocating and assigning addresses to host machines that may be utilizing IPv6 auto-address configuration or acting as DHCPv6 clients. CLI Examples DHCPv6 is disabled by default and can be enabled using the following CLI configuration: Enable DHCPv6: console# config Service dhcpv6 exit IPv6 131

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
IPv6
131
causes DHCPv6 clients to send the DHCPv6 “Information Request” message in response. A DHCPv6
server then responds by providing only networking definitions such as DNS domain name and server
definitions, NTP server definitions, and/or SIP definitions.
RFC 3315 also describes DHCPv6 Relay Agent interactions, which are very much like DHCPv4 Relay
Agents. Additionally, there is a DHCPv6 Relay Agent Option Internet draft [9], which employs very
similar capabilities as those described by DHCPv4 Relay Agent Option in RFC 2132.
With the larger address space inherent to IPv6, addresses within a network can be allocated more
effectively in a hierarchical fashion. DHCPv6 introduces the notion of “prefix delegation” as described in
RFC 3633 [8] as a way for routers to centralize and delegate IP address assignment. The following
diagram depicts a typical network scenario where prefix delegation is used.
Figure 6-2.
DHCPv6 Prefix Delegation Scenario
In Figure 6-2, the PE router acts as Prefix Delegation server and defines one or more “general” prefixes to
delegate to a CPE router acting as a Prefix Delegation client. The CPE router then can then allocate
more specific addresses within the given general prefix range to assign to its local router interfaces. The
CPE router can in turn use the given general prefix in allocating and assigning addresses to host
machines that may be utilizing IPv6 auto-address configuration or acting as DHCPv6 clients.
CLI Examples
DHCPv6 is disabled by default and can be enabled using the following CLI configuration:
Enable DHCPv6:
console# config
Service dhcpv6
exit
CPE Router
PE Router
Host
Host
DHCPv6
Client
DHCPv6
Client
DHCPv6
PD Server
DHCPv6
PD to Client
DHCPv6
Server
DHCPv6
Server
General Prefix (such as /48)
General Prefix (such as /64)