Print this page
Clearview IPMP manpages
| Split |
Close |
| Expand all |
| Collapse all |
--- old/./dhcpagent.txt
+++ new/./dhcpagent.txt
1 1 System Administration Commands dhcpagent(1M)
2 2
3 3
4 4
5 5 NAME
6 6 dhcpagent - Dynamic Host Configuration Protocol (DHCP)
7 7 client daemon
8 8
9 9 SYNOPSIS
10 10 dhcpagent [-a] [ -d n] [-f] [-v]
11 11
12 12
13 13 DESCRIPTION
14 14 dhcpagent implements the client half of the Dynamic Host
15 15 Configuration Protocol (DHCP) for machines running Solaris
16 16 software.
17 17
18 18
19 19 The dhcpagent daemon obtains configuration parameters for
20 20 the client (local) machine's network interfaces from a DHCP
21 21 server. These parameters may include a lease on an IP
22 22 address, which gives the client machine use of the address
23 23 for the period of the lease, which may be infinite. If the
24 24 client wishes to use the IP address for a period longer than
25 25 the lease, it must negotiate an extension using DHCP. For
26 26 this reason, dhcpagent must run as a daemon, terminating
27 27 only when the client machine powers down.
28 28
29 29
30 30 For IPv4, the dhcpagent daemon is controlled through
31 31 ifconfig(1M) in much the same way that the init(1M) daemon
32 32 is controlled by telinit(1M). dhcpagent can be invoked as a
33 33 user process, albeit one requiring root privileges, but this
34 34 is not necessary, as ifconfig(1M) will start it automati-
35 35 cally.
36 36
37 37
38 38 For IPv6, the dhcpagent daemon is invoked automatically by
39 39 in.ndpd(1M). It can also be controlled through ifconfig(1M),
40 40 if necessary.
41 41
42 42
43 43 When invoked, dhcpagent enters a passive state while it
44 44 awaits instructions from ifconfig(1M) or in.ndpd(1M). When
45 45 it receives a command to configure an interface, it brings
46 46 up the interface (if necessary) and starts DHCP. Once DHCP
47 47 is complete, dhcpagent can be queried for the values of the
48 48 various network parameters. In addition, if DHCP was used
49 49 to obtain a lease on an address for an interface, it con-
50 50 figures the address for use. When a lease is obtained, it
51 51 is automatically renewed as necessary. If the lease cannot
52 52 be renewed, dhcpagent will unconfigure the address, but the
53 53 interface will be left up and dhcpagent will attempt to
54 54 acquire a new address lease. dhcpagent monitors system
55 55 suspend/resume events and will validate any non-permanent
56 56 leases with the DHCP server upon resume. Similarly,
57 57
58 58
59 59
60 60 SunOS 5.11 Last change: 15 May 2008 1
61 61
62 62
63 63
64 64
65 65
|
↓ open down ↓ |
65 lines elided |
↑ open up ↑ |
66 66
67 67 System Administration Commands dhcpagent(1M)
68 68
69 69
70 70
71 71 dhcpagent monitors link up/down events and will validate
72 72 any non-permanent leases with the DHCP server when the
73 73 downed link is brought back up.
74 74
75 75
76 - For IPv4, if the configured interface is found to be
77 - unplumbed, marked down, or to have a different IP address,
78 - subnet mask, or broadcast address from those obtained from
79 - DHCP, the interface is abandoned by DHCP control.
76 + For IPv4, if the configured interface is found to be
77 + unplumbed, or to have a different IP address, subnet mask,
78 + or broadcast address from those obtained from DHCP, the
79 + interface is abandoned from DHCP control.
80 80
81 81
82 - For IPv6, dhcpagent automatically plumbs and unplumbs logi-
83 - cal interfaces as necessary for the IPv6 addresses supplied
84 - by the server. The IPv6 prefix length (netmask) is not set
85 - by the DHCPv6 protocol, but is instead set by in.ndpd(1M)
86 - using prefix information obtained by Router Advertisements.
87 - If any of the logical interfaces created by dhcpagent is
88 - unplumbed, marked down, or configured with a different IP
89 - address, it will be abandoned by DHCP control. If the link-
90 - local interface is unplumbed, then all addresses configured
91 - by DHCP on that physical interface will be removed.
82 + For IPv6, dhcpagent automatically plumbs and unplumbs
83 + logical interfaces as necessary for the IPv6 addresses
84 + supplied by the server. The IPv6 prefix length (netmask) is
85 + not set by the DHCPv6 protocol, but is instead set by
86 + *in.ndpd(1M)* using prefix information obtained by Router
87 + Advertisements. If any of the logical interfaces created by
88 + dhcpagent is unplumbed, or configured with a different IP
89 + address, it will be abandoned from DHCP control. If the
90 + link-local interface is unplumbed, then all addresses
91 + configured by DHCP on that physical interface will be
92 + removed.
92 93
93 94
94 95 In addition to DHCP, dhcpagent also supports BOOTP (IPv4
95 96 only). See RFC 951, Bootstrap Protocol. Configuration param-
96 97 eters obtained from a BOOTP server are treated identically
97 98 to those received from a DHCP server, except that the IP
98 99 address received from a BOOTP server always has an infinite
99 100 lease.
100 101
101 102
102 103 DHCP also acts as a mechanism to configure other information
103 104 needed by the client, for example, the domain name and
104 105 addresses of routers. Aside from the IP address, and for
105 106 IPv4 alone, the netmask, broadcast address, and default
106 107 router, the agent does not directly configure the worksta-
107 108 tion, but instead acts as a database which may be interro-
108 109 gated by other programs, and in particular by dhcpinfo(1).
109 110
110 111
111 112 On clients with a single interface, this is quite straight-
112 113 forward. Clients with multiple interfaces may present diffi-
113 114 culties, as it is possible that some information arriving on
114 115 different interfaces may need to be merged, or may be incon-
115 116 sistent. Furthermore, the configuration of the interfaces is
116 117 asynchronous, so requests may arrive while some or all of
117 118 the interfaces are still unconfigured. To handle these
118 119 cases, one interface may be designated as primary, which
119 120 makes it the authoritative source for the values of DHCP
120 121 parameters in the case where no specific interface is
121 122 requested. See dhcpinfo(1) and ifconfig(1M) for details.
122 123
123 124
124 125
125 126
126 127 SunOS 5.11 Last change: 15 May 2008 2
127 128
128 129
129 130
130 131
131 132
132 133
133 134 System Administration Commands dhcpagent(1M)
134 135
135 136
136 137
137 138 For IPv4, the dhcpagent daemon can be configured to request
138 139 a particular host name. See the REQUEST_HOSTNAME description
139 140 in the FILES section. When first configuring a client to
140 141 request a host name, you must perform the following steps as
141 142 root to ensure that the full DHCP negotiation takes place:
142 143
143 144 # pkill dhcpagent
144 145 # rm /etc/dhcp/interface.dhc
145 146 # reboot
146 147
147 148
148 149
149 150
150 151 All DHCP packets sent by dhcpagent include a vendor class
151 152 identifier (RFC 2132, option code 60; RFC 3315, option code
152 153 16). This identifier is the same as the platform name
153 154 returned by the uname -i command, except:
154 155
155 156 o Any commas in the platform name are changed to
156 157 periods.
157 158
158 159 o If the name does not start with a stock symbol and
159 160 a comma, it is automatically prefixed with SUNW.
160 161
161 162 Messages
162 163 The dhcpagent daemon writes information and error messages
163 164 in five categories:
164 165
165 166 critical
166 167
167 168 Critical messages indicate severe conditions that
168 169 prevent proper operation.
169 170
170 171
171 172 errors
172 173
173 174 Error messages are important, sometimes unrecoverable
174 175 events due to resource exhaustion and other unexpected
175 176 failure of system calls; ignoring errors may lead to
176 177 degraded functionality.
177 178
178 179
179 180 warnings
180 181
181 182 Warnings indicate less severe problems, and in most
182 183 cases, describe unusual or incorrect datagrams received
183 184 from servers, or requests for service that cannot be
184 185 provided.
185 186
186 187
187 188 informational
188 189
189 190
190 191
191 192
192 193 SunOS 5.11 Last change: 15 May 2008 3
193 194
194 195
195 196
196 197
197 198
198 199
199 200 System Administration Commands dhcpagent(1M)
200 201
201 202
202 203
203 204 Informational messages provide key pieces of information
204 205 that can be useful to debugging a DHCP configuration at
205 206 a site. Informational messages are generally controlled
206 207 by the -v option. However, certain critical pieces of
207 208 information, such as the IP address obtained, are always
208 209 provided.
209 210
210 211
211 212 debug
212 213
213 214 Debugging messages, which may be generated at two dif-
214 215 ferent levels of verbosity, are chiefly of benefit to
215 216 persons having access to source code, but may be useful
216 217 as well in debugging difficult DHCP configuration prob-
217 218 lems. Debugging messages are only generated when using
218 219 the -d option.
219 220
220 221
221 222
222 223 When dhcpagent is run without the -f option, all messages
223 224 are sent to the system logger syslog(3C) at the appropriate
224 225 matching priority and with a facility identifier LOG_DAEMON.
225 226 When dhcpagent is run with the -f option, all messages are
226 227 directed to standard error.
227 228
228 229 DHCP Events and User-Defined Actions
229 230 If an executable (binary or script) is placed at
230 231 /etc/dhcp/eventhook, the dhcpagent deamon will automatically
231 232 run that program when any of the following events occur:
232 233
233 234 BOUND and BOUND6
234 235
235 236 These events occur during interface configuration. The
236 237 event program is invoked when dhcpagent receives the
237 238 DHCPv4 ACK or DHCPv6 Reply message from the DHCP server
238 239 for the lease request of an address, indicating success-
239 240 ful initial configuration of the interface. (See also
240 241 the INFORM and INFORM6 events, which occur when confi-
241 242 guration parameters are obtained without address
242 243 leases.)
243 244
244 245
245 246 EXTEND and EXTEND6
246 247
247 248 These events occur during lease extension. The event
248 249 program is invoked just after dhcpagent receives the
249 250 DHCPv4 ACK or DHCPv6 Reply from the DHCP server for the
250 251 DHCPv4 REQUEST (renew) message or the DHCPv6 Renew or
251 252 Rebind message.
252 253
253 254 Note that with DHCPv6, the server might choose to remove
254 255 some addresses, add new address leases, and ignore
255 256
256 257
257 258
258 259 SunOS 5.11 Last change: 15 May 2008 4
259 260
260 261
261 262
262 263
263 264
264 265
265 266 System Administration Commands dhcpagent(1M)
266 267
267 268
268 269
269 270 (allow to expire) still other addresses in a given Reply
270 271 message. The EXTEND6 event occurs when a Reply is
271 272 received that leaves one or more address leases still
272 273 valid, even if the Reply message does not extend the
273 274 lease for any address. The event program is invoked just
274 275 before any addresses are removed, but just after any new
275 276 addresses are added. Those to be removed will be marked
276 277 with the IFF_DEPRECATED flag.
277 278
278 279
279 280 EXPIRE and EXPIRE6
280 281
281 282 These events occur during lease expiration. For DHCPv4,
282 283 the event program is invoked just before the leased
283 284 address is removed from an interface and the interface
284 285 is marked as down. For DHCPv6, the event program is
285 286 invoked just before the last remaining leased addresses
286 287 are removed from the interface.
287 288
288 289
289 290 DROP and DROP6
290 291
291 292 These events occur during the period when an interface
292 293 is dropped. The event program is invoked just before the
293 294 interface is removed from DHCP control. If the interface
294 295 has been abandoned due the user unplumbing the inter-
295 296 face, then this event will occur after the user's action
296 297 has taken place. The interface might not be present.
297 298
298 299
299 300 INFORM and INFORM6
300 301
301 302 These events occur when an interface acquires new or
302 303 updated configuration information from a DHCP server by
303 304 means of the DHCPv4 INFORM or the DHCPv6 Information-
304 305 Request message. These messages are sent using an
305 306 ifconfig(1M) dhcp inform command or when the DHCPv6
306 307 Router Advertisement O (letter 0) bit is set and the M
307 308 bit is not set. Thus, these events occur when the DHCP
308 309 client does not obtain an IP address lease from the
309 310 server, and instead obtains only configuration parame-
310 311 ters.
311 312
312 313
313 314 LOSS6
314 315
315 316 This event occurs during lease expiration when one or
316 317 more valid leases still remain. The event program is
317 318 invoked just before expired addresses are removed. Those
318 319 being removed will be marked with the IFF_DEPRECATED
319 320 flag.
320 321
321 322
322 323
323 324
324 325 SunOS 5.11 Last change: 15 May 2008 5
325 326
326 327
327 328
328 329
329 330
330 331
331 332 System Administration Commands dhcpagent(1M)
332 333
333 334
334 335
335 336 Note that this event is not associated with the receipt
336 337 of the Reply message, which occurs only when one or more
337 338 valid leases remain, and occurs only with DHCPv6. If all
338 339 leases have expired, then the EXPIRE6 event occurs
339 340 instead.
340 341
341 342
342 343 RELEASE and RELEASE6
343 344
344 345 This event occurs during the period when a leased
345 346 address is released. The event program is invoked just
346 347 before dhcpagent relinquishes the address on an inter-
347 348 face and sends the DHCPv4 RELEASE or DHCPv6 Release
348 349 packet to the DHCP server.
349 350
350 351
351 352
352 353 The system does not provide a default event program. The
353 354 file /etc/dhcp/eventhook is expected to be owned by root and
354 355 have a mode of 755.
355 356
356 357
357 358 The event program will be passed two arguments, the inter-
358 359 face name and the event name, respectively. For DHCPv6, the
359 360 interface name is the name of the physical interface.
360 361
361 362
362 363 The event program can use the dhcpinfo(1) utility to fetch
363 364 additional information about the interface. While the event
364 365 program is invoked on every event defined above, it can
365 366 ignore those events in which it is not interested. The event
366 367 program runs with the same privileges and environment as
367 368 dhcpagent itself, except that stdin, stdout, and stderr are
368 369 redirected to /dev/null. Note that this means that the event
369 370 program runs with root privileges.
370 371
371 372
372 373 If an invocation of the event program does not exit after 55
373 374 seconds, it is sent a SIGTERM signal. If does not exit
374 375 within the next three seconds, it is terminated by a SIGKILL
375 376 signal.
376 377
377 378
378 379 See EXAMPLES for an example event program.
379 380
380 381 OPTIONS
381 382 The following options are supported:
382 383
383 384 -a
384 385
385 386 Adopt a configured IPv4 interface. This option is for
386 387 use with diskless DHCP clients. In the case of diskless
387 388
388 389
389 390
390 391 SunOS 5.11 Last change: 15 May 2008 6
391 392
392 393
393 394
394 395
395 396
396 397
397 398 System Administration Commands dhcpagent(1M)
398 399
399 400
400 401
401 402 DHCP, DHCP has already been performed on the network
402 403 interface providing the operating system image prior to
403 404 running dhcpagent. This option instructs the agent to
404 405 take over control of the interface. It is intended pri-
405 406 marily for use in boot scripts.
406 407
407 408 The effect of this option depends on whether the inter-
408 409 face is being adopted.
409 410
410 411 If the interface is being adopted, the following condi-
411 412 tions apply:
412 413
413 414 dhcpagent uses the client id specified in
414 415 /chosen:<client_id>, as published by the PROM or as
415 416 specified on a boot(1M) command line. If this value is
416 417 not present, the client id is undefined. The DHCP server
417 418 then determines what to use as a client id. It is an
418 419 error condition if the interface is an Infiniband inter-
419 420 face and the PROM value is not present.
420 421
421 422 If the interface is not being adopted:
422 423
423 424 dhcpagent uses the value stored in
424 425 /etc/default/dhcpagent. If this value is not present,
425 426 the client id is undefined. If the interface is Infini-
426 427 band and there is no value in /etc/default/dhcpagent, a
427 428 client id is generated as described by the draft docu-
428 429 ment on DHCP over Infiniband, available at:
429 430
430 431 http://www.ietf.org
431 432
432 433
433 434
434 435 -d n
435 436
436 437 Set debug level to n. Two levels of debugging are
437 438 currently available, 1 and 2; the latter is more ver-
438 439 bose.
439 440
440 441
441 442 -f
442 443
443 444 Run in the foreground instead of as a daemon process.
444 445 When this option is used, messages are sent to standard
445 446 error instead of to syslog(3C).
446 447
447 448
448 449 -v
449 450
450 451 Provide verbose output useful for debugging site confi-
451 452 guration problems.
452 453
453 454
454 455
455 456
456 457 SunOS 5.11 Last change: 15 May 2008 7
457 458
458 459
459 460
460 461
461 462
462 463
463 464 System Administration Commands dhcpagent(1M)
464 465
465 466
466 467
467 468 EXAMPLES
468 469 Example 1 Example Event Program
469 470
470 471
471 472 The following script is stored in the file
472 473 /etc/dhcp/eventhook, owned by root with a mode of 755. It is
473 474 invoked upon the occurrence of the events listed in the
474 475 file.
475 476
476 477
477 478 #!/bin/sh
478 479
479 480 (
480 481 echo "Interface name: " $1
481 482 echo "Event: " $2
482 483
483 484 case $2 in
484 485 "BOUND")
485 486 echo "Address acquired from server "\
486 487 `/sbin/dhcpinfo -i $1 ServerID`
487 488 ;;
488 489 "BOUND6")
489 490 echo "Addresses acquired from server " \
490 491 `/sbin/dhcpinfo -v6 -i $1 ServerID`
491 492 ;;
492 493 "EXTEND")
493 494 echo "Lease extended for " \
494 495 `sbin/dhcpinfo -i $1 LeaseTim`" seconds"
495 496 ;;
496 497 "EXTEND6")
497 498 echo "New lease information obtained on $i"
498 499 ;;
499 500 "EXPIRE" | "DROP" | "RELEASE")
500 501 ;;
501 502
502 503 esac
503 504 ) >/var/run/dhcp_eventhook_output 2>&1
504 505
505 506
506 507
507 508
508 509 Note the redirection of stdout and stderr to a file.
509 510
510 511
511 512 FILES
512 513 /etc/dhcp/if.dhc
513 514 /etc/dhcp/if.dh6
514 515
515 516 Contains the configuration for interface. The mere
516 517 existence of this file does not imply that the confi-
517 518 guration is correct, since the lease might have expired.
518 519 On start-up, dhcpagent confirms the validity of the
519 520
520 521
521 522
522 523 SunOS 5.11 Last change: 15 May 2008 8
523 524
524 525
525 526
526 527
527 528
528 529
529 530 System Administration Commands dhcpagent(1M)
530 531
531 532
532 533
533 534 address using REQUEST (for DHCPv4) or Confirm (DHCPv6).
534 535
535 536
536 537 /etc/dhcp/duid
537 538 /etc/dhcp/iaid
538 539
539 540 Contains persistent storage for DUID (DHCP Unique Iden-
540 541 tifier) and IAID (Identity Association Identifier)
541 542 values. The format of these files is undocumented, and
542 543 applications should not read from or write to them.
543 544
544 545
545 546 /etc/default/dhcpagent
546 547
547 548 Contains default values for tunable parameters. All
548 549 values may be qualified with the interface they apply to
549 550 by prepending the interface name and a period (".") to
550 551 the interface parameter name. The parameters include:
551 552 the interface parameter name.
552 553
553 554 To configure IPv6 parameters, place the string .v6
554 555 between the interface name (if any) and the parameter
555 556 name. For example, to set the global IPv6 parameter
556 557 request list, use .v6.PARAM_REQUEST_LIST. To set the
557 558 CLIENT_ID (DUID) on hme0, use hme0.v6.CLIENT_ID.
558 559
559 560 The parameters include:
560 561
561 562 RELEASE_ON_SIGTERM
562 563
563 564 Indicates that a RELEASE rather than a DROP should
564 565 be performed on managed interfaces when the agent
565 566 terminates. Release causes the client to discard the
566 567 lease, and the server to make the address available
567 568 again. Drop causes the client to record the lease in
568 569 /etc/dhcp/interface.dhc or /etc/dhcp/interface.dh6
569 570 for later use.
570 571
571 572
572 573 OFFER_WAIT
573 574
574 575 Indicates how long to wait between checking for
575 576 valid OFFERs after sending a DISCOVER. For DHCPv6,
576 577 sets the time to wait between checking for valid
577 578 Advertisements after sending a Solicit.
578 579
579 580
580 581 CLIENT_ID
581 582
582 583 Indicates the value that should be used to uniquely
583 584 identify the client to the server. This value can
584 585 take one of three basic forms:
585 586
586 587
587 588
588 589 SunOS 5.11 Last change: 15 May 2008 9
589 590
590 591
591 592
592 593
593 594
594 595
595 596 System Administration Commands dhcpagent(1M)
596 597
597 598
598 599
599 600 decimal,data...
600 601 0xHHHHH...
601 602 "string...."
602 603
603 604
604 605 The first form is an RFC 3315 DUID. This is legal
605 606 for both IPv4 DHCP and DHCPv6. For IPv4, an RFC 4361
606 607 Client ID is constructed from this value. In this
607 608 first form, the format of data... depends on the
608 609 decimal value. The following formats are defined for
609 610 this first form:
610 611
611 612 1,hwtype,time,lla
612 613
613 614 Type 1, DUID-LLT. The hwtype value is an integer
614 615 in the range 0-65535, and indicates the type of
615 616 hardware. The time value is the number of
616 617 seconds since midnight, January 1st, 2000 UTC,
617 618 and can be omitted to use the current system
618 619 time. The lla value is either a colon-separated
619 620 MAC address or the name of a physical interface.
620 621 If the name of an interface is used, the hwtype
621 622 value can be omitted. For example: 1,,,hme0
622 623
623 624
624 625 2,enterprise,hex...
625 626
626 627 Type 2, DUID-EN. The enterprise value is an
627 628 integer in the range 0-4294967295 and represents
628 629 the SMI Enterprise number for an organization.
629 630 The hex string is an even-length sequence of
630 631 hexadecimal digits.
631 632
632 633
633 634 3,hwtype,lla
634 635
635 636 Type 3, DUID-LL. This is the same as DUID-LLT
636 637 (type 1), except that a time stamp is not used.
637 638
638 639
639 640 *,hex
640 641
641 642 Any other type value (0 or 4-65535) can be used
642 643 with an even-length hexadecimal string.
643 644
644 645 The second and third forms of CLIENT_ID are legal
645 646 for IPv4 only. These both represent raw Client ID
646 647 (without RFC 4361), in hex, or NVT ASCII string for-
647 648 mat. Thus, Sun and 0x53756E are equivalent.
648 649
649 650
650 651
651 652
652 653
653 654
654 655 SunOS 5.11 Last change: 15 May 2008 10
655 656
656 657
657 658
658 659
659 660
660 661
661 662 System Administration Commands dhcpagent(1M)
662 663
663 664
664 665
665 666 PARAM_REQUEST_LIST
666 667
667 668 Specifies a list of comma-separated integer values
668 669 of options for which the client would like values.
669 670
670 671
671 672 REQUEST_HOSTNAME
672 673
673 674 Indicates the client requests the DHCP server to map
674 675 the client's leased IPv4 address to the host name
675 676 associated with the network interface that performs
676 677 DHCP on the client. The host name must be specified
677 678 in the /etc/hostname.interface file for the relevant
678 679 interface on a line of the form
679 680
680 681 inet hostname
681 682
682 683
683 684 where hostname is the host name requested.
684 685
685 686 This option works with DHCPv4 only.
686 687
687 688
688 689
689 690 /etc/dhcp/eventhook
690 691
691 692 Location of a DHCP event program.
692 693
693 694
694 695 ATTRIBUTES
695 696 See attributes(5) for descriptions of the following attri-
696 697 butes:
697 698
698 699
699 700
700 701 ____________________________________________________________
701 702 | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
702 703 |_____________________________|_____________________________|
703 704 | Availability | SUNWcsr |
704 705 |_____________________________|_____________________________|
705 706 | Interface Stability | Committed |
706 707 |_____________________________|_____________________________|
707 708
708 709
709 710 SEE ALSO
710 711 dhcpinfo(1), ifconfig(1M), init(1M), in.ndpd(1M),
711 712 syslog(3C), attributes(5), dhcp(5)
712 713
713 714
714 715 Croft, B. and Gilmore, J.,Bootstrap Protocol (BOOTP)RFC 951,
715 716 Network Working Group, September 1985.
716 717
717 718
718 719
719 720
720 721 SunOS 5.11 Last change: 15 May 2008 11
721 722
722 723
723 724
724 725
725 726
726 727
727 728 System Administration Commands dhcpagent(1M)
728 729
729 730
730 731
731 732 Droms, R., Dynamic Host Configuration Protocol, RFC 2131,
732 733 Network Working Group, March 1997.
733 734
|
↓ open down ↓ |
632 lines elided |
↑ open up ↑ |
734 735
735 736 Lemon, T. and B. Sommerfeld. RFC 4361, Node-specific Client
736 737 Identifiers for Dynamic Host Configuration Protocol Version
737 738 Four (DHCPv4). Nominum and Sun Microsystems. February 2006.
738 739
739 740
740 741 Droms, R. RFC 3315, Dynamic Host Configuration Protocol for
741 742 IPv6 (DHCPv6). Cisco Systems. July 2003.
742 743
743 744 NOTES
744 - The dhcpagent daemon can be used on IPv4 logical interfaces,
745 - just as with physical interfaces. When used on a logical
746 - interface, the daemon automatically constructs a Client ID
747 - value based on the DUID and IAID values, according to RFC
748 - 4361. The /etc/default/dhcpclient CLIENT_ID value, if any,
745 + DHCP can be performed on IPv4 logical interfaces just as
746 + with physical interfaces. When used on a logical interface,
747 + the daemon automatically constructs a Client ID value based
748 + on the DUID and IAID values, according to RFC 4361. The
749 + */etc/default/dhcpclient* *CLIENT_ID* value, if any,
749 750 overrides this automatic identifier.
750 751
751 752
752 753 As with physical IPv4 interfaces, the /etc/hostname.hme0:1
753 754 and /etc/dhcp.hme0:1 files must also be created in order for
754 755 hme0:1 to be automatically plumbed and configured at boot.
755 756 In addition, unlike physical IPv4 interfaces, dhcpagent does
756 757 not add or remove default routes associated with logical
757 758 interfaces.
758 759
759 760
761 + DHCP can be performed on IPMP IP interfaces to acquire and
762 + maintain IPMP data addresses. Because an IPMP IP interface
763 + has no hardware address, the daemon automatically constructs
764 + a Client ID using the same approach described above for IPv4
765 + logical interfaces. In addition, the lack of a hardware
766 + address means the daemon must set the "broadcast" flag in
767 + all *DISCOVER* and *REQUEST* messages on IPMP IP interfaces.
768 + Some DHCP servers may refuse such requests.
769 +
770 +
771 + DHCP can be performed on IP interfaces that are part of an
772 + IPMP group (to acquire and maintain test addresses). The
773 + daemon will automatically set the *NOFAILOVER* and
774 + *DEPRECATED* flags on each test address. Additionally, the
775 + daemon will not add or remove default routes in this case.
776 + Note that the actual DHCP packet exchange may be performed
777 + over any active IP interface in the IPMP group. It is
778 + strongly recommended that test addresses have infinite
779 + leases. Otherwise, an extended network outage detectable
780 + only by probes may cause test address leases to expire,
781 + causing *in.mpathd(1M)* to revert to link-based failure
782 + detection and trigger an erroneous repair.
783 +
784 +
760 785 With DHCPv6, the link-local interface must be configured
761 786 using /etc/hostname6.hme0 in order for DHCPv6 to run on hme0
762 787 at boot time. The logical interfaces for each address are
763 788 plumbed by dhcpagent automatically.
764 789
765 790
766 791
767 792
768 793
769 794
770 795
771 796
772 797
773 798
774 799
775 800
776 801
777 802
778 803
779 804
780 805
781 806
782 807
783 808
784 809
785 810
786 811 SunOS 5.11 Last change: 15 May 2008 12
787 812
788 813
789 814
|
↓ open down ↓ |
20 lines elided |
↑ open up ↑ |
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX