cc/td/doc/product/rtrmgmt/ciscoasu/nr/nr30t
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Configuring BOOTP

Configuring BOOTP

BOOTP (BOOTstrap Protocol) was originally created for loading diskless computers. It was later used to allow a host to obtain all the required TCP/IP information to use the Internet. BOOTP allows a host to broadcast a request onto the network, and obtains information required from a BOOTP server. The BOOTP server is a computer that listens for incoming BOOTP requests and generates responses from a configuration database for the BOOTP clients on that network. BOOTP differs from DHCP in that it has no concept of lease or lease expiration. All IP addresses allocated by a BOOTP server are permanent.

You can configure Network Registrar to act like a BOOTP server. In addition, although BOOTP normally requires static address assignments, you can choose to either reserve IP addresses (and therefore use static assignments) or have IP addresses dynamically allocated for BOOTP clients.

Note Network Registrar supports the BOOTP-only protocol, not TFTP. Often older versions of BOOTP use both protocols.

For more information about LDAP and its attributes, refer to the Network Registrar Concepts Guide.

Table 12-1 lists the BOOTP configuration tasks described in this chapter and the sections where you can find more information about them.
Table 12-1: BOOTP Configuration Topics
If you want to... Go to this section...

Know more about the Network Registrar DHCP server BOOTP support

"About BOOTP" section

Know more about how Network Registrar configures BOOTP packets

"Enabling BOOTP for a Scope" section

Move or decommission a BOOTP client

"Moving or Decommissioning a BOOTP Client" section

About BOOTP

When you configure the DHCP server to return a BOOTP packet, be aware that BOOTP requires information in the DHCP packet in fields other than the option space. BOOTP devices often need information in the file (the bootfile), siaddr (the server's IP address), or sname (server's host name) fields of the DHCP packet (see RFC 2131).

Every Network Registrar DHCP policy has fields that allow you to configure the information you want returned directly in the file, siaddr, or sname fields.

Network Registrar's DHCP server also supports a configuration parameter that allows you to configure the policy options and determine which of the fields' file, sname, or siaddr you want returned to the BOOTP device.

Network Registrar supports an analogous configuration parameter that allows you to configure which options and which of the fields: file, sname and siaddr 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 the values that you want in the BOOTP packet reply fields:

Step 2 Decide the list of options and their values that you want returned to the BOOTP client.

Step 3 Set the following values in the policy you want associated with the BOOTP request:

Step 4 Enable the associated scope or scopes for BOOTP processing.

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 will need to make reservations for each BOOTP client for which you want this scope to provide an address.

Enabling BOOTP for a Scope

Using the GUI:

Step 1 In the Policies tab of the DHCP Server Properties dialog box (Figure 6-2), configure a packet to contain the information that BOOTP requires.

Step 2 In the Edit Options dialog box, select the options you want.

Step 3 Click the Send to BOOTP clients check box.

Step 4 If you select the Always send to DHCP clients check box, the DHCP server sends an option back in the DHCP reply packet regardless of whether the client requested the option.

Step 5 Click OK.

Step 6 In the Advanced tab of the DHCP Scope Properties dialog box (Figure 6-3), select the Enable BOOTP check box.

Step 7 If you want dynamic IP address assignment, select the check box, otherwise create reservations.

For more information about making reservations, see the "Making Lease Reservations" section.

Step 8 Click OK.

Step 9 Reload the DHCP server.

Using the CLI:

You use the policy create and policy set commands to configure BOOTP.

Step 1 Set the policy fields. Specify the boot-reply options as a comma-separated list of strings. Specify the name of the option or field. The options have regular names, whereas the fields have names, such as packet-siaddr, packet-file-name, and packet-server-name.

    nrcmd> policy MyPolicy create
nrcmd> policy MyPolicy set packet-siaddr=192.168.1.5
nrcmd> policy MyPolicy set packet-file-name=mybootfile.bin
nrcmd> policy MyPolicy set packet-server-name=<your-sname>
nrcmd> policy MyPolicy set bootp-reply-options=packet-siaddr, packet-file-name,domain-name,domain-name-servers

Step 2 Set the correct option values. The setOption method requires spaces (not equal signs) before values.

    nrcmd> policy MyPolicy setOption <your-options> <option-value>

Step 3 Enable BOOTP.

    nrcmd> scope MyScope enable bootp

Step 4 Enable dynamic BOOTP.

    nrcmd> scope MyScope enable dynamic-bootp

Moving or Decommissioning a BOOTP Client

When you move or decommission a BOOTP client, you can reuse its lease. To decommission a BOOTP client, you actually de-activate the lease.

Using the GUI:

Step 1 From the Server Manager window, select the DHCP server for which BOOTP client lease you want to make available.

Step 2 Select the DHCP scope.

Step 3 Select the lease de-activated lease that you want to make available.

Step 4 Click the Lease Properties button. The Lease Properties dialog box appears (Figure 12-1).


Figure 12-1: Lease Properties Dialog Box (DHCP Server Properties Leases Tab)


Step 5 Click the Force Available button.

Step 6 Click off the Deactivate Lease button.

Step 7 Click OK.

Step 8 In the Lease Properties dialog box, click the Refresh button to see the lease's new available state.

Step 9 Click OK.

Using the CLI:

Use the lease force-available command to make a de-activated lease available again.

nrcmd> lease 5.5.0.14 force-available
100 Ok
nrcmd> 
[Log Output]
06/16/1999 15:37:35 name/dhcp/1 Warning Server 0 04704 Forcing Lease:'5.5.0.14' into available state, was leased to  CID: 01:06:05:05:05:05:05:05

hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Nov 18 13:45:46 PST 1999
Copyright 1989-1999©Cisco Systems Inc.