Cisco Systems OL-6240-02 Manual De Usuario
22-2
Cisco CNS Network Registrar User’s Guide
OL-6240-02
Chapter 22 Advanced DHCP Server Properties
Configuring BOOTP
Every Network Registrar DHCP policy has attributes with which you can configure the information you
want returned directly in the file, siaddr, or sname fields. The Network Registrar DHCP server also
supports a configuration parameter with which you can configure the policy options and determine
which of the file, sname, or siaddr values you want returned to the BOOTP device.
want returned directly in the file, siaddr, or sname fields. The Network Registrar DHCP server also
supports a configuration parameter with which you can configure the policy options and determine
which of the file, sname, or siaddr values you want returned to the BOOTP device.
Network Registrar supports an analogous configuration parameter with which you can configure the
options and file, sname, or siaddr values you want returned to the DHCP client. This is in addition to
any options requested by the DHCP clients in the dhcp-parameter-request option in the DHCP request.
Thus, you can configure both the BOOTP and DHCP response packets appropriately for your devices.
options and file, sname, or siaddr values you want returned to the DHCP client. This is in addition to
any options requested by the DHCP clients in the dhcp-parameter-request option in the DHCP request.
Thus, you can configure both the BOOTP and DHCP response packets appropriately for your devices.
Step 1
Decide which values you want for the BOOTP attributes:
•
file—Name of the boot file
•
siaddr—Server’s IP address
•
sname—Optional server host name
Step 2
Decide the list of options and their values that you want returned to the BOOTP client.
Step 3
Set these values in the policy you want associated with the BOOTP request:
•
Attributes—Packet-siaddr, packet-file-name, packet-server-name to send to the BOOTP client.
•
Option values, such as the server addresses and domain name to return to the BOOTP client.
•
List of fields and options you want returned to the BOOTP client.
Step 4
Enable the associated scope or scopes for BOOTP processing.
Step 5
Enable dynamic BOOTP processing if you want to have this scope provide an address for any BOOTP
client that requests one. If you do not enable dynamic BOOTP, you must make reservations for each
BOOTP client for which you want this scope to provide an address.
client that requests one. If you do not enable dynamic BOOTP, you must make reservations for each
BOOTP client for which you want this scope to provide an address.
Enabling BOOTP for Scopes
You can enable BOOTP processing for a scope. Set certain attributes and BOOTP reply options for a
created policy in the local cluster Web UI, or use policy name create and policy name set in the CLI, to
configure BOOTP. Set the policy attributes and options as a comma-separated list. The attributes are
entities to use in a client’s boot process:
created policy in the local cluster Web UI, or use policy name create and policy name set in the CLI, to
configure BOOTP. Set the policy attributes and options as a comma-separated list. The attributes are
entities to use in a client’s boot process:
•
packet-siaddr—IP address of the next server
•
packet-file-name—Name of the boot file
•
packet-server-name—Host name of the server
The server looks through the policy hierarchy for the first instances of these attribute values.
In the CLI, policy name setOption requires spaces (not equal signs) before values. Also, enable BOOTP
and dynamic BOOTP, if desired, and ensure that the DHCP server updates the DNS server with BOOTP
requests. The options are:
and dynamic BOOTP, if desired, and ensure that the DHCP server updates the DNS server with BOOTP
requests. The options are:
•
Set the option dhcp-lease-time.
•
Enable the dynamic-bootp attribute.
•
Enable the update-dns-for-bootp attribute.
•
Enable the update-dns-for-bootp attribute.