How to Network Boot (Netboot) a LOADER / CFE based filer in Data ONTAP 7G
Currently, netbooting a kernel image over the network by the TFTP and HTTP protocol is supported by platforms using LOADER (FAS2000 series, FAS3040/FAS3070, FAS3200, FAS6000 and FAS8000 series) or Common Firmware Environment (FAS200 series and FAS3020/FAS3050). To configure an existing controller to provide the TFTP and HTTP services for netbooting, the steps are described below:
For setting up TFTP services for netbooting:
- Log in to a controller that is up and running Data ONTAP.
- On the controller, type the following:
filer> options tftpd.enable on
- Create the
/etc/tftpbootdirectory if one does not exist. This is the default root directory where the netboot kernel, for example netapp-mips, should be placed. Check with ‘
options tftpd.rootdir‘ whether the tftp root dir reflects the directory above.
- Place the netboot kernel image into this directory (
/etc/tftpbootor whatever the tftp root dir is set to)
Note: Obtain the file from the Data ONTAP software download (http://mysupport.netapp.com/NOW/cgi-bin/software) page (obtain the one for the right platform)
Setting up HTTP services for netbooting:
- Log in to a controller that is running Data ONTAP.
- Place the netboot kernel, for example netapp-mips, into the
/etc/httpdirectory. By default, this directory serves HTTP requests to service management (ZAPI) requests to the controller.
For TFTP netbooting using the default rootdir:
LOADER> netboot tftp://Filer/netapp-mips
For HTTP netbooting using the
LOADER> netboot http://partner_ip/na_admin/722_netboot.e (http://partner_ip/na_admin/722_netboot.e)
LOADER based filer
FAS2020 / FAS2050 / FAS3040 / FAS3070 / FAS3140/ FAS3170/ FAS3200 /FAS6030 / FAS6040 / FAS6070 / FAS6080/ FAS8000
To netboot a LOADER-based filer, substitute your IP addresses and perform the following at the LOADER> prompt:
LOADER> ifconfig e0a -addr=192.168.1.10 -mask=255.255.255.0 -gw=192.168.1.1 -dns=192.168.1.2
e0a: Link speed: 1000BaseT FDX
Device e0a: hwaddr 00-A0-98-03-48-AB, ipaddr 192.168.1.10, mask 255.255.255.0
gateway 192.168.1.1, nameserver not set
If gateway is available, test connectivity:
LOADER> ping 192.168.1.1
192.168.1.1 (192.168.1.1) is alive
192.168.1.1 (192.168.1.1): 1 packets sent, 1 received
LOADER> netboot tftp://192.168.1.11/tftproot/netapp_7.2.3_x86_64
Type the following at the LOADER> prompt to display the complete syntax: help ifconfig
- Only built-in Ethernet ports are supported for netbooting.a
- This procedure is not persistent across reboots.
Common Firmware Environment (CFE) based filer
FAS250 / FAS270 / FAS3020 / FAS3050
To netboot a FAS250, see the section entitled ‘Netbooting an FAS250’ found in the FAS250 Storage Appliance Hardware and Service Guide.
CFE supports booting from a CompactFlash device or from the network using TFTP or HTTP protocols. For a brand new CompactFlash Card, there is no Data ONTAP image, therefore, it must boot from network (netboot). The netboot network configuration does not persist while rebooting.
It might take some time before the network connection is established. To check the status, use the
ifconfig command to check the link status. Try a ping to the http server first, since loading the kernel image takes a long time to abort.
Provide all the network parameters, that is gateway and DNS, even if they are not needed, it helps to establish the connection faster.
Note: Use the netboot file when downloading and installing Data ONTAP.
NetApp provides no representations or warranties regarding the accuracy, reliability, or serviceability of any information or recommendations provided in this publication, or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS, and the use of this information or the implementation of any recommendations or techniques herein is a customer’s responsibility and depends on the customer’s ability to evaluate and integrate them into the customer’s operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.