DHCP provides a framework for passing configuration information to hosts on a TCP/IP network.
Configuration parameters and other control information are carried in tagged data items that are stored
in the options field of the DHCP message. The data items themselves are also called options.
This appendix contains DHCP options and BOOTP vendor extensions from RFC 2132, and includes the
validation type for each option, as indicated in Table B-10 on page B-14.
This appendix also contains the standard Microsoft client options and several tables displaying the
options sorted by categories.
Option Descriptions
The following sections describe the DHCP options in detail:
• RFC 1497 Vendor Extensions, page B-1
• IP Layer Parameters Per Host, page B-3
APPENDIX
B
• IP Layer Parameters Per Interface, page B-4
• Link Layer Parameters Per Interface, page B-4
• TCP Parameters, page B-5
• Application and Service Parameters, page B-5
• DHCPv4 Extension Options, page B-8
• DHCPv6 Options, page B-10
• Microsoft Client Options, page B-13
• Options by Number, page B-14
• Options by Network Registrar Name, page B-18
• Option Validation Types, page B-24
RFC 1497 Vendor Extensions
Table B-1 on page B-2 lists the vendor extensions as defined in RFC 1497.
OL-16002-01
User Guide for Cisco Network Registrar, 7.1
B-1
Option Descriptions
Part 6: Appendices, Glossary, and Index Appendix B DHCP Options
Table B-1RFC 1497 Vendor Extension Options
Option NameNo. LengthDescription
Pad01 octetCauses the subsequent fields to align on word boundaries.
End255 1 octetEnd of valid information in the vendor field. Subsequent
octets should be filled with the Pad options.
Subnet Mask14 octetsClient subnet mask, as per RFC 950. If both the Subnet Mask
and the Router option are specified in a DHCP reply, the
Subnet Mask option must be first.
Time Offset24 octetsOffset of the client subnet, in seconds, from Universal Time
(UT). The offset is expressed as a twos-complement 32-bit
integer. A positive offset indicates a location east of the zero
meridian and a negative offset indicates a location we s t of the
zero meridian.
Router34 octet minimum;
multiples of 4
Time Server44 octet minimum;
multiples of 4
Name Server
Option
Domain Name
Server
54 octet minimum;
multiples of 4
64 octet minimum;
multiples of 4
List of IP addresses for routers on the client subnet. Routers
should be in order of preference.
List of RFC 868 compliant time servers available to the
client. Servers should be in order of preference.
List of IEN 116 name servers available to the client. Servers
should be in order of preference.
List of Domain Name System (STD 13, RFC 1035) name
servers available to the client. Servers should be in order of
preference.
Log Server74 octet minimum;
multiples of 4
Cookie Server 84 octet minimum;
multiples of 4
LPR Server94 octet minimum;
multiples of 4
Impress
Server
Resource
Location
104 octet minimum;
multiples of 4
114 octet minimum;
multiples of 4
Server
List of MIT-LCS UDP log servers available to the client.
Servers should be in order of preference.
List of RFC 865-compliant cookie servers available to the
client. Servers should be in order of preference.
List of RFC 1179-compliant line printer servers available to
the client. Servers should be in order of preference.
List of Imagen Impress servers available to the client. Servers
should be in order of preference.
List of RFC 887-compliant resource location servers
available to the client. Servers should be in order of
preference.
Host Name121 octet minimum Name of the client. The name may or may not be qualified
with the local domain name. See RFC 1035 for the character
set restrictions.
Boot File Size 132 octetsNumber of 512-octet blocks in the default boot file.
Merit Dump
File
141 octet minimum Path name of a file to which the client core image should be
placed in the event the client crashes. The path is formatted
as a character string consisting of characters from the NVT
ASCII character set.
Domain Name 151 octet minimum Domain name that the client should use when resolving
hostnames through the Domain Name System.
Swap Server164 octetsIP address of the client swap server.
B-2
User Guide for Cisco Network Registrar, 7.1
OL-16002-01
Part 6: Appendices, Glossary, and Index Appendix B DHCP Options
Root Path171 octet minimum Path name that contains the client root disk. The path is
Extensions
181 octet minimum Uses a string to specify a file, retrievable through TFTP. The
Path
IP Layer Parameters Per Host
Table B-2 lists the options that affect the operation of the IP layer on a per-host basis.
Table B-2IP Layer Parameters Per Host Options
Option Descriptions
formatted as a character string consisting of characters from
the NVT ASCII character set.
file contains information that can be interpreted in the same
way as the 64-octet vendor-extension field within the
BOOTP response, with these exceptions: the length of the file
is unconstrained, and all references to instances of this option
in the file are ignored.
Option NameNo. LengthDescription
IP Forwarding
Enable/Disable
Non-Local
Source Routing
Enable/Disable
Policy Filter 218 octet minimum;
191 octetSpecifies whether the client should configure its IP layer
for packet forwarding. Values: 0=disable; 1=enable
201 octetSpecifies whether the client should configure its IP layer to
allow forwarding of datagrams with non-local source
routes. Values: 0=disable; 1=enable
Policy filters for non-local source routing. The filters
multiples of 8
consist of a list of IP addresses and masks that specify
destination/mask pairs with which to filter incoming source
routes. Any source-routed datagram whose next-hop
address does not match one of the filters should be
discarded by the client.
Maximum
Datagram
222 octetsMaximum size datagram that the client should be prepared
to reassemble. Value: 576 minimum
Reassembly
Size
Default IP
Time-to-Live
Path MTU
Aging Timeout
Path MTU
Plateau Table
231 octetDefault TTL that the client should use on outgoing
datagrams. Values: 1 to 255
244 octetsTimeout (in seconds) to use when aging Path MTU values
(defined in RFC 1191).
252 octets minimum;
multiples of 2
Table of MTU sizes to use when performing Path MTU
Discovery as defined in RFC 1191. The table is formatted
as a list of 16-bit unsigned integers, ordered from smallest
to largest. Value: 68 minimum
OL-16002-01
User Guide for Cisco Network Registrar, 7.1
B-3
Option Descriptions
IP Layer Parameters Per Interface
Table B-3 lists the options that affect the operation of the IP layer on a per-interface basis. A client can
issue multiple requests, one per interface, to configure interfaces with their specific parameters.
Table B-3IP Layer Parameters Per Interface Options
Option NameNo. LengthDescription
Interface MTU 262 octetsMaximum time to live to use on this interface.
All Subnets
Are Local
Broadcast
Address
Perform Mask
Discovery
Mask Supplier301 octetSpecifies whether or not the client should respond to subnet
Perform Router
Discovery
Router
Solicitation
Address
Static Route338 octet minimum;
271 octetSpecifies whether or not the client can assume that all
284 octetsBroadcast address in use on the client subnet.
291 octetSpecifies whether or not the client should perform subnet
311 octetSpecifies whether or not the client should solicit routers
324 octetsAddress to which the client should transmit router
multiples of 8
Part 6: Appendices, Glossary, and Index Appendix B DHCP Options
subnets of the IP network to which the client is connected
use the same MTU as the subnet of that network to which the
client is directly connected.
Values: 1=all subnets share same MTU; 0=some
directly-connected subnets can have smaller MTUs
mask discovery using ICMP. Values: 0=disable; 1=enable
mask requests using ICMP.
Values: 0=do not respond; 1=respond
using the Router Discovery mechanism defined in RFC
1256. Values: 0=disable; 1=enable
solicitation requests.
List of static routes that the client should install in its
routing cache. If multiple routes to the same destination are
specified, they are in descending order of priority. The
routes consist of a list of IP address pairs. The first address
is the destination address, and the second address is the
router for the destination. The default route (0.0.0.0) is an
illegal destination for a static route.
Link Layer Parameters Per Interface
Table B-4 lists the options that affect the operation of the data link layer on a per-interface basis.
Table B-4Link Layer Parameters Per Interface Options
Option NameNo. LengthDescription
Trailer
Encapsulation
User Guide for Cisco Network Registrar, 7.1
B-4
341 octetSpecifies whether or not the client should negotiate the use of trailers
(RFC 893) when using the ARP protocol. Values: 0=do not use; 1=use
OL-16002-01
Part 6: Appendices, Glossary, and Index Appendix B DHCP Options
Table B-4Link Layer Parameters Per Interface Options (continued)
Option NameNo. LengthDescription
ARP Cache
Timeout
Ethernet
Encapsulation
354 octets Timeout in seconds for ARP cache entries.
361 octetSpecifies whether or not the client should use Ethernet Version 2 (RFC
TCP Parameters
Table B-5 lists the options that affect the operation of the TCP layer on a per-interface basis.
Table B-5TCP Parameter Options
Option NameNo. LengthDescription
TCP Default
TTL
TCP Keepalive
Interval
TCP Keepalive
Garbage
371 octetDefault TTL that the client should use when sending TCP segments.
384 octets Interval (in seconds) that the client TCP should wait before sending a
391 octetSpecifies the whether or not the client should send TCP keep-alive
Option Descriptions
894) or IEEE 802.3 (RFC 1042) encapsulation if the interface is an
Ethernet.
Value: 0=use RFC 894 encapsulation; 1=use RFC 1042 encapsulation
Value: minimum 1
keepalive message on a TCP connection. The time is specified as a
32-bit unsigned integer. A value of zero indicates that the client should
not generate keepalive messages on connections unless specifically
requested by an application. Value: 32-bit unsigned; 0=do not generate
keepalive messages unless specifically requested.
messages with an octet of garbage for compatibility with older
implementations.
Values: 0=do not send; 1=send
Application and Service Parameters
Table B-6 lists some miscellaneous options used to configure miscellaneous applications and services.
Table B-6Application and Service Parameter Options
Option NameNo. LengthDescription
Network
Information
Service (NIS)
Domain
Network
Information
Service (NIS)
Servers
OL-16002-01
401 octet minimum Name of the client NIS domain. The domain is formatted
414 octet minimum;
multiples of 4
as a character string consisting of characters from the NVT
ASCII character set.
List of IP addresses indicating NIS servers available to the
client. Servers should be in order of preference.
User Guide for Cisco Network Registrar, 7.1
B-5
Option Descriptions
Part 6: Appendices, Glossary, and Index Appendix B DHCP Options
Table B-6Application and Service Parameter Options (continued)
Option NameNo. LengthDescription
Network Time
Protocol Servers
424 octet minimum;
multiples of 4
List of IP addresses indicating NTP servers that are
available to the client. Servers should be in order of
preference.
Vendor-Specific
Information
431 octet minimum This option is used by clients and servers to exchange
vendor-specific information. The information is an opaque
object of n octets, presumably interpreted by
vendor-specific code on the clients and servers. The
definition of this information is vendor specific. The
vendor is indicated in the dhcp-class-identifier option.
Servers not equipped to interpret the vendor-specific
information sent by a client must ignore it (although it can
be reported). Clients that do not receive desired
vendor-specific information should make an attempt to
operate without it, although they can do so (and announce
they are doing so) in a degraded mode.
If a vendor potentially encodes more than one item of
information in this option, then the vendor should encode
the option using encapsulated vendor-specific options as
described here.
The encapsulated vendor-specific options field should be
encoded as a sequence of code, length, and value fields of
identical syntax to the DHCP options field with these
exceptions:
• There should not be a magic cookie field in the
encapsulated vendor-specific extensions field.
NetBIOS over
TCP/IP Name
Server
NetBIOS over
TCP/IP
Datagram
Distribution
Server
444 octet minimum;
multiples of 4
454 octet minimum;
multiples of 4
• Codes other than 0 or 255 can be redefined by the
vendor within the encapsulated vendor-specific
extensions field, but should conform to the
tag-length-value syntax defined in section 2.
Code 255 (END), if present, signifies the end of the
encapsulated vendor extensions, not the end of the vendor
extensions field.
If the code 255 is not present, then the end of the enclosing
vendor-specific information field is taken as the end of the
encapsulated vendor-specific extensions field.
List of RFC 1001/1002 NBNS name servers in order of
preference.
List of RFC 1001/1002 NBDD servers in order of
preference.
B-6
User Guide for Cisco Network Registrar, 7.1
OL-16002-01
Part 6: Appendices, Glossary, and Index Appendix B DHCP Options
Table B-6Application and Service Parameter Options (continued)
Option NameNo. LengthDescription
NetBIOS over
461 octetAllows NetBIOS over TCP/IP client, which are configured
TCP/IP Node
Type
NetBIOS over
471 octet minimum NetBIOS over TCP/IP scope parameter for the client as
TCP/IP Scope
X Window
System Font
484 octet minimum;
multiples of 4
Server
X Window
System Display
494 octet minimum;
multiples of 4
Manager
Network
641 octet minimum Name of the client NIS+ domain. The domain is formatted
Information
Service (NIS+)
Domain
Network
Information
654 octet minimum;
multiples of 4
Service (NIS+)
Servers
Mobile IP Home
Agent
680 octets
minimum;
multiples of 4;
expected, 4 octets
(single home
agent address)
Simple Mail
Transport
694 octet minimum;
multiples of 4
Protocol
(SMTP) Server
Post Office
Protocol (POP3)
704 octet minimum;
multiples of 4
Server
Network News
Transport
714 octet minimum;
multiples of 4
Protocol
(NNTP) Server
Wor ld Wid e We b
(WWW) Server
724 octet minimum;
multiples of 4
Option Descriptions
as described in RFC 1001/1002.
Values: Single hexadecimal octet that identifies the client
type:
• 0x1=B-node (broadcast node)
• 0x2=P-node (point-to-point node)
• 0x4=M-node (mixed node)
• 0x8=H-node
specified in RFC 1001/1002.
List of X Window System Font servers available to the
client. Servers should be in order of preference.
List of IP addresses of systems that are running the X
Window System Display Manager and are available to the
client. Addresses should be in order of preference.
as a character string consisting of characters from the NVT
ASCII character set.
List of IP addresses indicating NIS+ servers available to
the client. Servers should be in order of preference.
List of IP addresses indicating mobile IP home agents
available to the client. Agents should be in order of
preference.
Value: 32-bit address; 0=no home agents available
List of SMTP servers available to the client. Servers
should be in order of preference.
List of POP3 servers available to the client. Servers should
be in order of preference.
List of NNTP servers available to the client. Servers should
be in order of preference.
List of World Wide Web (WWW) servers available to the
client. Servers should be in order of preference.
OL-16002-01
User Guide for Cisco Network Registrar, 7.1
B-7
Option Descriptions
Table B-6Application and Service Parameter Options (continued)
Option NameNo. LengthDescription
Finger Server734 octet minimum;
Internet Relay
Chat Server
StreetTalk
Server
StreetTalk
Directory
Assistance
(STDA) Server
DHCPv4 Extension Options
Table B-7 lists the DHCPv4 extension options.
multiples of 4
744 octet minimum;
multiples of 4
754 octet minimum;
multiples of 4
764 octet minimum;
multiples of 4
Part 6: Appendices, Glossary, and Index Appendix B DHCP Options
List of Finger servers available to the client. Servers
should be in order of preference.
List of IRC servers available to the client. Servers should
be in order of preference.
List of StreetTalk servers available to the client. Servers
should be in order of preference.
List of STDA servers available to the client. Servers should
be in order of preference.
Table B-7DHCPv4 Extensions
Option NameNo. LengthDescription
Requested IP
Address
IP Address
Lease Time
504 octetsUsed in a client request (DHCPDISCOVER) to allow the client to
request that a particular IP address be assigned.
514 octetsUsed in a client request (DHCPDISCOVER or DHCPREQUEST)
to allow the client to request a lease time for the IP address. In a
server reply (DHCPOFFER), a DHCP server uses this option to
specify the lease time it is willing to offer.
Value: seconds, as 32-bit unsigned integer
Option Overload 521 octetIndicates that the DHCP sname or file fields are being overloaded
by using them to carry DHCP options. A DHCP server inserts this
option if the returned parameters will exceed the usual space
allotted for options. If this option is present, the client interprets
the specified additional fields after it concludes interpretation of
the standard option fields.
Values: 1=file field is used to hold options; 2=sname field is used
to hold options; 3=both fields are used to hold options
DHCP Message
Type
531 octetUsed to convey the type of DHCP message. The preset value is 1
Part 6: Appendices, Glossary, and Index Appendix B DHCP Options
Table B-7DHCPv4 Extensions (continued)
Option NameNo. LengthDescription
Server Identifier 544 octetsUsed in DHCPOFFER and DHCPREQUEST messages, and can
Parameter
Request List
551 octet
minimum
Message561 octet
minimum
Maximum
572 octetsMaximum-length DHCP message that a server is willing to accept.
DHCP Message
Size
Renewal (T1)
584 octetsTime interval from address assignment until the client transitions
Time Value
Rebinding (T2)
594 octetsTime interval from address assignment until the client transitions
Time Value
Vendor Class
Identifier
601 octet
minimum
Option Descriptions
optionally be included in the DHCPACK and DHCPNAK
messages. DHCP servers include this option in the DHCPOFFER
in order to allow the client to distinguish between lease offers.
DHCP clients use the contents of the server identifier field as the
destination address for any DHCP messages unicast to the DHCP
server. DHCP clients also indicate which of several lease offers is
being accepted by including this option in a DHCPREQUEST
message. The identifier is the IP address of the selected server.
Used by a DHCP client to request values for specified
configuration parameters. The list of requested parameters is
specified as n octets, where each octet is a valid DHCP option code
as defined in this document. The client can list the options in order
of preference. The DHCP server does not have to return the options
in the requested order, but must try to insert the options in the order
that the client requested.
Used by a DHCP server to provide an error message to a DHCP
client in a DHCPNAK message in the event of a failure. A client
can use this option in a DHCPDECLINE message to indicate why
the client declined the offered parameters. The message consists of
n octets of NVT ASCII text, which the client can display on an
available output device.
The length is specified as an unsigned 16-bit integer. A client can
use the maximum DHCP message size option in
DHCPDISCOVER or DHCPREQUEST messages, but should not
use the option in DHCPDECLINE messages. Value: 576 minimum
to RENEWING state.
Value: seconds, as 32-bit unsigned integer
to REBINDING state.
Value: seconds, as 32-bit unsigned integer
Used by DHCP clients to optionally identify the vendor type and
configuration of a DHCP client. The information is a string of n
octets, interpreted by servers. Vendors can choose to define
specific vendor class identifiers to convey particular configuration
or other identification information about a client. For example, the
identifier can encode the client hardware configuration. Servers
not equipped to interpret the class-specific information sent by a
client must ignore it (although it can be reported). Servers that
respond should only use option 43 to return the vendor-specific
information to the client.
OL-16002-01
User Guide for Cisco Network Registrar, 7.1
B-9
Option Descriptions
Part 6: Appendices, Glossary, and Index Appendix B DHCP Options
Table B-7DHCPv4 Extensions (continued)
Option NameNo. LengthDescription
Client-Identifier612 octet
minimum
Used by DHCP clients to specify their unique identifier. DHCP
servers use this value to index their database of address bindings.
This value is expected to be unique for all clients in an
administrative domain.
DHCP servers should treat identifiers as opaque objects. The client
identifier can consist of type-value pairs similar to the
htype/chaddr fields. For instance, it can consist of a hardware type
and hardware address. In this case, the type field should be one of
the ARP hardware types defined in STD2. A hardware type of 0
(zero) should be used when the value field contains an identifier
other than a hardware address (for example, a fully qualified
domain name).
For correct identification of clients, each client-identifier must be
unique among the client-identifiers used on the subnet to which the
client is attached. Vendors and system administrators are
responsible for choosing client-identifiers that meet this
requirement for uniqueness.
TFTP Server
Name
Bootfile Name671 octet
Relay Agent
661 octet
minimum
Identifies a TFTP server when the sname field in the DHCP header
has been used for DHCP options.
Identifies a bootfile when the file field is the DHCP header that has
minimum
been used for DHCP options.
82Identifies the DHCP relay agent information.
Information
iSNS8314 bytes
Identifies the Internet Storage Name Service (see RFC 4174)
minimum
BCMS
Controller
88VariableList of Broadcast and Multicast Service (BCMS) controller
domains (see RFC 4280)
Domain
BCMS Address894 octets
List of IP addresses for the BCMS controller (see RFC 4280)
minimum
Lease Query
Client Last
914 octetsTime of the most recent access of the client sending a
DHCPLEASEQUERY (see RFC 4388).
Transaction
Time
Lease Query
Associated IP
924 octets
minimum
All IP addresses associated with the client specified in a particular
DHCPLEASEQUERY message (see RFC 4388).
Addresses
DHCPv6 Options
Table B-8 on page B-11 lists the DHCPv6 options, along with their defined data types. All the option
packets include at least an option length (option-len) and a variable length data field. There can also be
additional parameter settings, as described in the table. Mod in the Description column indicates that the
option is modifiable. Many of these options are described in RFC 3315.
User Guide for Cisco Network Registrar, 7.1
B-10
OL-16002-01
Part 6: Appendices, Glossary, and Index Appendix B DHCP Options
Table B-8DHCPv6 Options
Network Registrar Name
(Type)No. Description (Mod=modifiable)
client-identifier
1DUID identifying a client between a client and a server.
AT _B L OB
server-identifier
2DUID identifying a server between a client and a server.
AT _B L OB
ia-na
AT _B L OB
3Nontemporary Addresses option with the associated parameters and
addresses. Parameters are the unique ID, time the client contacts the
addresses in the IA to extend the lifetime, and time the client contacts
any available server to extend the lifetime of the addresses.
ia-ta
AT _B L OB
iaaddr
AT _B L OB
4Temporary Addresses option with the associated parameters and
addresses.
5IPv6 addresses associated with an IA_NA or IA_TA. (The IAADRR
must be encapsulated in the options field of an IA_NA or IA_TA
option.) The IAADDR option includes preferred and valid lifetime
fields, and the options field that encapsulates the options specific to
this address.
oro
AT _S H ORT
6Option Request option (ORO) that identifies a list of options in a
message between a client and a server. A client can include this option
in a Solicit, Request, Renew, Rebind, Confirm, or Information-request
message to inform the server about options the client wants from the
server. A server can include this option in a Reconfigure message to
indicate which option updates the client should request.
preference
AT _I N T8
elapsed-time
AT _S H ORT
relay-message
7A server sends this option to a client to affect what server the client
selects (Mod).
8A client sends this option to a server to indicate how long the client
has been trying to complete a message exchange (Mod).
9DHCP message in a Relay-forward or Relay-reply message.
AT _B L OB
auth
AT _B L OB
11Authenticates the identity and contents of a DHCP message. The
parameters are the authentication protocol, the authentication
algorithm, the replay detection method (RDM), and the authentication
information.
server-unicast
AT_IP6ADDR
status-code
AT _B L OB
12The server sends this option to a client to indicate that the client can
unicast messages to the server.
13Returns a status indication related to the DHCP message or option in
which it appears. The parameters are the status code and status
message.
rapid-commit
14Signals use of the two-message exchange for address assignment.
AT_ZEROSIZE
user-class
AT_TYPECNT
15Clients use this option to identify the type or category of user or
applications it represents. A zero type count value field followed by
user data (as a blob).
vendor-class
AT_VENDOR_CLASS
16Clients use this option to identify the vendor that manufactured the
hardware on which they are running.
Option Descriptions
OL-16002-01
User Guide for Cisco Network Registrar, 7.1
B-11
Option Descriptions
Part 6: Appendices, Glossary, and Index Appendix B DHCP Options
Table B-8DHCPv6 Options (continued)
Network Registrar Name
(Type)No. Description (Mod=modifiable)
vendor-opts
AT_VENDOR_OPTS
17Clients and servers use this option to exchange vendor-specific
information. The enterprise ID for the CableLabs vendor is 4491; the
suboptions for CableLabs are listed in Table C-4 on page C-7.
interface-id
AT _B L OB
reconfigure-message
AT _I N T8
18Relay agents use this option to identify the interface on which the
client message is received.
19The server includes this in a Reconfigure message to indicate whether
the client should respond with a Renew or Information-request
message.
reconfigure-accept
AT_ZEROSIZE
sip-servers-name
AT _D N SNA ME
sip-servers-address
20Clients use this option to announce to the server whether the client is
willing to accept Reconfigure messages.
21Domain names of the SIP outbound proxy servers for the client (Mod).
See RFC 3319.
22IPv6 addresses of the SIP outbound proxy servers for the client (Mod).
AT_IP6ADDR
dns-servers
23IPv6 addresses of DNS recursive name servers (Mod).
AT_IP6ADDR
domain-list
24Domain names in the domain search list (Mod).
AT _D N SNA ME
ia-pd
AT _B L OB
25IPv6 prefix delegation identity association and its associated
parameters and prefixes. Parameters are the unique ID, time the client
contacts the addresses in the IA to extend the lifetime, and time the
client contacts any available server to extend the lifetime of the
addresses.
iaprefix
AT _B L OB
26IPv6 prefixes associated with an IA_PD. The prefix must be
encapsulated in the options field of an IA_PD option. Parameters are
the valid and preferred lifetimes, prefix length, and the prefix.
nis-servers
AT_IP6ADDR
nisp-servers
27List of IPv6 addresses of Network Information Service (NIS) servers
available to the client (see RFC 3898) (Mod).
28List of IPv6 addresses of NIS+ servers available to the client (Mod).
AT_IP6ADDR
nis-domain-name
29Conveys the NIS domain name to the client (Mod).
AT _D N SNA ME
nisp-domain-name
30Conveys the NIS+ domain name to the client (Mod).
AT _D N SNA ME
sntp-servers
AT_IP6ADDR
info-refresh-time
AT _T I ME
bcms-server-d
31List of Simple Network Time Protocol (SNTP) servers available to the
client (see RFC 4075) (Mod).
32Sets an upper bound for how long a client should wait before
refreshing DHCPv6 information (see RFC 4242) (Mod).
33List of BCMS controller domains (see RFC 4280) (Mod).
AT _D N SNA ME
bcms-server-a
AT_IP6ADDR
34List of IPv6 addresses for the Broadcast and Multicast Service
(BCMS) controller (see RFC 4280) (Mod).
B-12
User Guide for Cisco Network Registrar, 7.1
OL-16002-01
Part 6: Appendices, Glossary, and Index Appendix B DHCP Options
Table B-8DHCPv6 Options (continued)
Network Registrar Name
(Type)No. Description (Mod=modifiable)
geoconf-civic
36DHCP civic addresses configuration (Mod).
AT _B L OB
remote-id
AT _B L OB
relay-agent-subscriber-id
AT _B L OB
client-fqdn
37Relay agents that terminate switched or permanent circuits can add
this option to identify remote hosts (see RFC 4649) (Mod).
38Allows assignment and activation of subscriber-specific actions (see
RFC 4580) (Mod).
39DHCP client FQDN (Mod).
AT _B L OB
new-posix-timezone
AT _B L OB
new-tzdb-timezone
41POSIX time zone, for example, EST5EDT4,
M3.2.0/02:00,M11.1.0/02:00.
42POSIX time zone database name, for example, Europe/Zurich.
AT _B L OB
ero
AT _B L OB
lq-query
AT _B L OB
43Relay agent Echo Request option to inform the server of the list of
relay agent options to echo back.
44Used only in a LEASEQUERY message; identifies the query being
performed. The option includes the query type, link-address (or 0::0),
and options to provide data needed for the query.
client-data
AT _B L OB
clt-time
AT _T I ME
45Encapsulates the data for a single client on a single link in a
LEASEQUERY-REPLY message.
46Client last transaction time encapsulated in the client-data option;
identifies how long ago the server last communicated with the client
(in seconds).
lq-relay-data
AT _B L OB
lq-client-link
AT_IP6ADDR
47Used only in a LEASEQUERY-REPLY message; provides the relay
agent data used when the client last communicated with the server.
48Used only in a LEASEQUERY-REPLY message; identifies the links
on which the client has one or more bindings. It is used in reply to a
query when no link-address was specified and the client is found to be
on more than one link.
lost-server
AT _D N SNA ME
51A DHCPv6 client will request a LoST server domain name in an
Options Request Option (ORO) (see RFC3315) (Mod).
This option contains a single domain name and must contain precisely
one root label.
Option Descriptions
Microsoft Client Options
Table B-9 lists the standard Microsoft client options.
domain-name-servers 6IP address of the name servers
netbios-name-servers 44WINS server address
netbios-node-type46Identifies the NetBIOS client type; note that Network Registrar displays
routers3IP address of the router for this subnet
Option Tables
The following tables display the DHCP options in various ways. They show the options sorted
numerically, by Network Registrar name, and by category.
DHCP options have a prescribed format and allowed values for their option parameters. Table B-10 lists
each DHCP option and parameter type (in the Validation column). The parameter formats and allowed
values come from the DHCP and Internet RFCs. All the DHCP options appear, but clients control only
some, and the CLI only others.
Part 6: Appendices, Glossary, and Index Appendix B DHCP Options
a warning if it is not present
Options by Number
Table B-10 shows the DHCPv4 options sorted by option number, and includes the validation type. (See
Table B-12 on page B-24 for details on the option validation types found in the Validation column.) A
0+ in the Comments column means a repeat count of zero or more occurrences, 1+ means one or more
occurrences, 2n means multiple occurrences in multiples of 2. Comments also indicate whether the
option includes suboptions, and, if so, how many, and whether the option is nonmodifiable (NM).
TipFor the syntax for adding more complex option data values for suboptions, see the “Adding Complex