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).
bootfile <IMAGE-FILE-PATH>
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. |
Print
this page
Email this topic
Feedback
View PDF
Download EPUBnx9500-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)#
| bootp (dhcpv4-server-policy-config) |
Configures BOOTP protocol parameters |
| no (dhcpv4-pool-static-binding) |
Resets values or disables DHCP pool static binding settings |