bootfile (dhcpv4-pool-static-binding)

The Bootfile command provides a diskless node the path to the image file used while booting up. Only one file can be configured for each static IP binding.

For more information on the BOOTP protocol with reference to static binding, see bootp (dhcpv4-server-policy-config).

Supported on the following devices:

Access Points: AP5010, AP310i/e, AP410i/e, AP505i, AP510i, AP510e, AP560i, AP6522, AP6562, AP7161, AP7502, AP7522, AP7532, AP7562, AP7602, AP7612, AP7622, AP763, AP7662, AP8163, AP8543, AP8533.
Service Platforms: NX5500, NX7500, NX9500, NX9600
Virtual Platforms: CX9000, VX9000

Syntax

bootfile <IMAGE-FILE-PATH>

Parameters

bootfile <IMAGE-FILE-PATH>


<IMAGE-FILE-PATH>>	Sets the path to the boot image for BOOTP file used with this user pool. The file name can contain letters, numbers, dots and hyphens. Consecutive dots and hyphens are not permitted. Boot files (Boot Protocol) can be used to boot remote systems over the network. BOOTP messages are encapsulated inside UDP messages so requests and replies can be forwarded. Each DHCP network pool can use a different file as needed.

Examples

nx9500-6C8809(config-dhcp-policy-test-pool-pool1-binding-test)#bootfile test.txt

nx9500-6C8809(config-dhcp-policy-test-pool-pool1-binding-test)#show context
  static-binding client-identifier test
   bootfile test.txt
nx9500-6C8809(config-dhcp-policy-test-pool-pool1-binding-test)#

Related Commands


bootp (dhcpv4-server-policy-config)	Configures BOOTP protocol parameters
no (dhcpv4-pool-static-binding)	Resets values or disables DHCP pool static binding settings