How to use storage systems as netboot servers

You can configure a storage system to serve boot images to other NetApp devices that support netboot. You can also serve netboot images from your storage system.

To configure a storage system to serve boot images, you must configure:

HTTP services, TFTP services, or both on the storage system.
The rest of your netboot-using environment to access the storage system as the netboot source. For example, you might configure BOOTP, DHCP, bootparamd, and/or rarpd, depending on the specific procedure you are using.

You can also serve netboot images from your storage system by placing them in the /etc/http directory. The contents of this directory are served by default to enable the FilerView graphical management interface. For example, if you create an /etc/http/boot directory and place a boot image called custom-mips in that directory, the boot image will be available for netboot startup at the following URL: http://your.filer.com/na_admin/boot/custom-mips

Configuring HTTP services
You can configure a storage system as an HTTP netboot server.
Configuring TFTP services
You can configure a storage system as a TFTP netboot server.
Specifying the TFTP root directory
Any path name specified on the TFTP command line is considered to be relative to the TFTP root directory. TFTP access using absolute path names succeeds only if the specified files are located in the file system under this directory.
Enabling console logging of TFTP accessed files
You can enable console logging of files accessed with TFTP.

Parent topic: How to start and stop the storage system