Print this page
Clearview IPMP manpages
@@ -72,25 +72,26 @@
any non-permanent leases with the DHCP server when the
downed link is brought back up.
For IPv4, if the configured interface is found to be
- unplumbed, marked down, or to have a different IP address,
- subnet mask, or broadcast address from those obtained from
- DHCP, the interface is abandoned by DHCP control.
+ unplumbed, or to have a different IP address, subnet mask,
+ or broadcast address from those obtained from DHCP, the
+ interface is abandoned from DHCP control.
- For IPv6, dhcpagent automatically plumbs and unplumbs logi-
- cal interfaces as necessary for the IPv6 addresses supplied
- by the server. The IPv6 prefix length (netmask) is not set
- by the DHCPv6 protocol, but is instead set by in.ndpd(1M)
- using prefix information obtained by Router Advertisements.
- If any of the logical interfaces created by dhcpagent is
- unplumbed, marked down, or configured with a different IP
- address, it will be abandoned by DHCP control. If the link-
- local interface is unplumbed, then all addresses configured
- by DHCP on that physical interface will be removed.
+ For IPv6, dhcpagent automatically plumbs and unplumbs
+ logical interfaces as necessary for the IPv6 addresses
+ supplied by the server. The IPv6 prefix length (netmask) is
+ not set by the DHCPv6 protocol, but is instead set by
+ *in.ndpd(1M)* using prefix information obtained by Router
+ Advertisements. If any of the logical interfaces created by
+ dhcpagent is unplumbed, or configured with a different IP
+ address, it will be abandoned from DHCP control. If the
+ link-local interface is unplumbed, then all addresses
+ configured by DHCP on that physical interface will be
+ removed.
In addition to DHCP, dhcpagent also supports BOOTP (IPv4
only). See RFC 951, Bootstrap Protocol. Configuration param-
eters obtained from a BOOTP server are treated identically
@@ -739,15 +740,15 @@
Droms, R. RFC 3315, Dynamic Host Configuration Protocol for
IPv6 (DHCPv6). Cisco Systems. July 2003.
NOTES
- The dhcpagent daemon can be used on IPv4 logical interfaces,
- just as with physical interfaces. When used on a logical
- interface, the daemon automatically constructs a Client ID
- value based on the DUID and IAID values, according to RFC
- 4361. The /etc/default/dhcpclient CLIENT_ID value, if any,
+ DHCP can be performed on IPv4 logical interfaces just as
+ with physical interfaces. When used on a logical interface,
+ the daemon automatically constructs a Client ID value based
+ on the DUID and IAID values, according to RFC 4361. The
+ */etc/default/dhcpclient* *CLIENT_ID* value, if any,
overrides this automatic identifier.
As with physical IPv4 interfaces, the /etc/hostname.hme0:1
and /etc/dhcp.hme0:1 files must also be created in order for
@@ -755,10 +756,34 @@
In addition, unlike physical IPv4 interfaces, dhcpagent does
not add or remove default routes associated with logical
interfaces.
+ DHCP can be performed on IPMP IP interfaces to acquire and
+ maintain IPMP data addresses. Because an IPMP IP interface
+ has no hardware address, the daemon automatically constructs
+ a Client ID using the same approach described above for IPv4
+ logical interfaces. In addition, the lack of a hardware
+ address means the daemon must set the "broadcast" flag in
+ all *DISCOVER* and *REQUEST* messages on IPMP IP interfaces.
+ Some DHCP servers may refuse such requests.
+
+
+ DHCP can be performed on IP interfaces that are part of an
+ IPMP group (to acquire and maintain test addresses). The
+ daemon will automatically set the *NOFAILOVER* and
+ *DEPRECATED* flags on each test address. Additionally, the
+ daemon will not add or remove default routes in this case.
+ Note that the actual DHCP packet exchange may be performed
+ over any active IP interface in the IPMP group. It is
+ strongly recommended that test addresses have infinite
+ leases. Otherwise, an extended network outage detectable
+ only by probes may cause test address leases to expire,
+ causing *in.mpathd(1M)* to revert to link-based failure
+ detection and trigger an erroneous repair.
+
+
With DHCPv6, the link-local interface must be configured
using /etc/hostname6.hme0 in order for DHCPv6 to run on hme0
at boot time. The logical interfaces for each address are
plumbed by dhcpagent automatically.