dhcpv6d(1M)															       dhcpv6d(1M)

NAME

       dhcpv6d - Dynamic Host Configuration Protocol Server daemon for IPv6

SYNOPSIS

       config_file] max_hop_count]

DESCRIPTION

       The DHCPv6 server daemon  is the IPv6 version of the bootpd daemon.  This implementation of is based on the RFC 3315.

       This version of supports the following features:

	      o  Dynamic renumbering
	      o  Relay preconfiguration with server addresses, or use of multicast addresses
	      o  Multiple IP addresses for an interface

       The daemon is run as a stand-alone daemon and not spawned by

   Options
       Specify an alternate configuration file for the server.	The default configuration file is

       Toggle debugging on or off.

       Specify the maximum number of hops allowed for a DHCP packet
	      after which the server drops the DHCP packet.

       Kill the server gracefully.

       Re-read the configuration file and trigger the server to send a reconfig-init
	      message to the clients when the configuration file has any new or updated information.

       Enable Unicast option.

       Enable Rapid Commit option.

       Run the DHCPv6 server as a relay agent.

   Configuration File
       Upon startup, reads the configuration file, or a file specified with the option to build its internal database, and then listens for DHCPv6
       messages from the client.

       The configuration file contains the following sections:

	 1. DHCPv6 client default settings

	 2. DHCPv6 pool group settings

	 3. DHCPv6 relay settings

	 4. DHCPv6 device group settings

	 5. DHCPv6 address pool settings

	 6. DHCPv6 relay interface mapping settings

	 7. DHCPv6 client duid (DHCP Unique Identifier) group settings

       Blank lines and lines beginning with "#" in the configuration file are ignored.	Entries are separated from one	another  by  a	semicolon.
       Multiple entries of a group can be extended over multiple lines if the lines end with a backslash .  A final semicolon ; followed by a new
       line indicates the end of a group.

       IP addresses are specified in the standard IPv6 notation (colon notation) and can use hexadecimal numbers.

       The binary hexadecimal format of a tag can be represented with each byte separated by a colon (:) and without `0x' prefixed to the hexadec-
       imal number.

       For example: The tag can be represented as

       Alternatively, the prefix length can be specified along with the subnet prefixes with a slash (/).

       Example: For the prefix the prefix length of 64 can be specified as

       The tags for the DHCPv6 client default settings are as listed below. These tags are applicable to all the addresses that the server assigns
       to the DHCPv6 client.

	      This tag specifies the client's default settings.

	      This tag specifies the name of the group default settings.

	      This tag specifies the list of DNS nameservers available to the
			client.  Multiple nameserver addresses are separated by white spaces.

	      This tag specifies the list of names of the client's DNS domain.
			is formatted as a character string consisting of characters from the NVT-ASCII character set.

	      This tag specifies the list of names of the client's NIS domain.
			is formatted as a character string consisting of characters from the NVT-ASCII character set.

	      This tag specifies the list of NIS servers
			available to the client.  Multiple addresses are separated by white spaces.

	      This tag specifies the list of names of the client's NIS+ domain.
			is formatted as a character string consisting of characters from the NVT-ASCII character set.

	      This tag specifies the list of NIS+ servers
			available to the client.  Multiple addresses are separated by white spaces.

	      This tag specifies the SIP server list available to the client.

	      This tag specifies the list of names of the client's SIP domain names.
			The domain name is formatted as a character string consisting of the NVT-ASCII character set.

       The tags applicable for the individual DHCPv6 pool groups are as listed below:

	      This tag specifies the individual pool groups.

	      This tag specifies the name of the pool group as an
			ASCII string.

	      This tag specifies the name of the default settings for the pool group.
			The default settings are specified in the

	      This tag specifies the list of address pool names with each name
			separated by space.  The address pool names are specified in the section

	      This tag specifies the list of deprecated address pool names, with each name
			separated by space. The deprecated address pools are specified in the section

	      This tag specifies the server preference to manage the subnet.  This value can
			range between 0 and 255.

	      This variable is used by the server to control the time at which the
			client contacts the server to extend the lifetimes on assigned addresses.  On expiration of T1, the client sends  a  RENEW
			message to the server.	Default value is 302400 seconds.

	      This variable is used by the server to control the time at which the
			client	contacts the server to extend the lifetimes on assigned addresses.  On expiration of T2, the client sends a REBIND
			message to the server. Default value is 483840 seconds.

	      This tag specifies the preferred lifetime for the IP addresses in seconds.
			Default is 604800 seconds.

	      This tag specifies the valid lifetime for the addresses in seconds.
			Default is 2592000 seconds.

	      This tag specifies the grace period (in seconds) until when the old
			configuration parameters remain valid after reconfiguring the server.  Default is 604800 seconds.

	      This tag specifies the preferred lifetime for temporary
			addresses in seconds. Default is 86400 seconds.

	      This tag specifies the valid lifetime for temporary addresses
			in seconds.  Default is 604800 seconds.

       NOTE: Values for the above listed lifetime-related tags must satisfy the following conditions:

       If the above condition fails, the server takes the default values.

	      This tag specifies
			deprecated address pools to be valid until the A sample format for is as follows:

       The DHCPv6 address-pool-specific tags are as listed below:

	      This tag specifies the individual address pools.

	      This tag specifies the name of the address pool.

	      This tag specifies the subnet-prefix of the network that the server
			manages.  Note that, the complete address of the subnet must be specified.

	      This tag specifies the list of start and end address, which
			constitute the address pool.

	      This tag specifies the list of reserved IPv6 addresses separated
			by a space.

       The DHCPv6 relay-specific tags are as listed below:

	      This tag indicates the start of the DHCP relay settings.

	      This tag specifies the pool group name as a
			ASCII string.

	      This tag specifies the IPv6 subnet prefix in the hexadecimal format. This must be the complete
			address of the subnet.

	      This tag specifies the address of the DHCPv6 server to which the relay
			forwards the client messages.

       The DHCPv6 device-group-specific tags are as listed below:

	      This tag indicates the start of the DHCP device group settings.

	      This tag specifies the vendor-specific data, namely
			enterprise-number and vendor-class-data-list.  enterprise-number is mandatory and must be an integer.	vendor-class-data-
			list  can  be  represented  in ASCII format within double quotes.  vendor-class-data-list can also be in the binary format
			with each byte represented in the hexadecimal format and separated by a colon (:).

	      This tag can be used to represent type or category of the user or client
			application.  The format for user-class-data is similar to that of vendor-class-data.

       NOTE: Either vendor-class-id or user-class-id can be specified at a time.

	      This tag can be used to specify vendor-specific configuration options,
			where n specifies a unique integer.  Ensure that is immediately followed by n.	vendor-options can be represented  in  the
			ASCII format within double quote or in the binary format.

       All the fields applicable to the can be used under the DHCPv6 device group except the

       The DHCPv6 client-duid-group-specific tags are as listed below:

	      This tag indicates the start of the DHCP client duid group settings.

	      This tag specifies that the client duid can be represented in the hexadecimal
			format with each byte separated by a colon (:).

	      This tag specifies the list of addresses for the particular duid group.

       All the fields applicable to the can be used under the DHCPv6 client duid group except the

       The DHCPv6 relay-interface-mapping-specific tags are as listed below:

	      This tag indicates the start of the relay interface mappings.
			The  relay  interface  mapping maps the the relay's interface identifier, which is an unique identifier in DHCP domain, to
			the subnet address in which the client exists.

	      The Interface-ID is represented in the hexadecimal binary format with each
			byte separated by a colon (:).	Subnet-address is represented in an IPv6-hexadecimal format.

			Example:
   Reconfiguration
       If configuration parameters are added, deleted, or modified, then their entries in the internal database are updated when is  invoked  with
       the option.

EXAMPLES

       Refer to the file for the sample DHCP server configuration.

WARNINGS

       The DHCP configuration file supports a maximum of 200 characters in a line.

AUTHOR

       was developed by Hewlett-Packard.

FILES

       This is the	     server default configuration file.

SEE ALSO

       dhcpv6client_ui(1), dhcpv6clientd(1M), dhcpv6db2conf(1M).

																       dhcpv6d(1M)