Skip to main content
NetApp Knowledge Base

Netbooting a Data ONTAP 7-Mode System

  1. Last updated
  2. Save as PDF
Views:
3,716
Visibility:
Public
Votes:
1
Category:
data-ontap-7
Specialty:
7dot
Last Updated:

Applies to

 Data ONTAP 7-Mode

Answer

Netboot Overview

Netboot is a procedure that can be used as an alternative way to boot a NetApp Storage system from a Data ONTAP software image that is stored on a HTTP or TFTP server. Netboot is typically used to facilitate specific recovery scenarios. Some common scenarios are; correcting a failed upgrade, repairing a failed boot media, and booting the correct kernel for the current hardware platform. The recovery actions discussed in this article should not be taken without guidance from NetApp Support.
Previously when ONTAP 7G was booted, the kernel would be loaded into memory and there would no longer be any dependency on the boot device, allowing the system to run from the netboot kernel. In Data ONTAP 8, once the kernel has been loaded, there is still a need to access the boot device. Also, the Data ONTAP 8.X Special boot menu options 1 and 2 (normal boot and boot without /etc/rc) are disabled.

How to Netboot with Caveats
The following are the tool requirements for netbooting a storage controller:

  • Access to the RLM/BMC/SP or console of the storage controller
  • Access to an HTTP server (8.0x and beyond) or TFTP (7.3x and below)
  • Access to download the necessary Netboot kernel files for the platform from the NetApp Support site .
  • Access to download the necessary install image file for the platform from the NetApp Support site.
  • The latest version of system firmware on the controller is recommended.
  • A network interface to be configured for the netboot process.
    Depending on the interface selected an available IP address might be required.

Note: The netboot configuration is stored in the firmware environment and is not persistent across reboots. For each boot, the network interface has to be configured manually.

Selecting a network interface:

From the loader or CFE prompt the show devices command can be used to determine which network interfaces are potentially available to for netboot. Generally the available interfaces are only the motherboard based interfaces. In the example below, which is platform specific, the e0a, e0b, and e0M ports are available to the loader. The e0M interface can be used for the netboot procedures; however, the e0P interface should not.

LOADER-A> show devices
Device Name Description
----------- ---------------------------------------------------------
e0M IBA GE Slot 1801 v1351 (00-A0-98-32-65-35)
e0P IBA GE Slot 1800 v1351 (00-A0-98-32-65-34) -- Interface for ACP don’t use.
e0a IBA GE Slot 1701 v1351 (00-A0-98-32-65-33)
e0b IBA GE Slot 1700 v1351 (00-A0-98-32-65-32)

Warning: If the only available interfaces on the storage system are configured to use Multimode or LACP VIFs, a manual reconfiguration of the switch ports and network interfaces might be required.

The network interface selected is dependent on the configuration of the network. For most recovery scenarios the interface and IP selected must be allowed HTTP, SSH or TFTP access to the public IP addresses of both HA nodes.

Warning: CFE (Common Firmware Environment) based storage systems (200 and 3000 series) might encounter errors when attempting to netboot using an interface that is set to 1000 megabits per second.

Errors when Netbooting

Example: Incorrect version of the netboot kernel for the platform

CFE> netboot tftp://10.61.33.230/7351_netboot.e
Loading: Failed.
Could not load tftp://10.61.33.230/7351_netboot.e: Not an ELF-format executable
*** command status = -11
- or -
LOADER-A> netboot tftp://10.61.33.230/netboot/kernel
Loading 10.61.33.230/netboot/kernel:.......Failed: Not a 64-bit executable
Could not load tftp://10.61.33.230/netboot/kernel: Not a 64-bit executable
Not a 64-bit executable (errcode=-45)
- or -
LOADER-A> netboot tftp://10.61.33.230/kernel
Loading 10.61.33.230/kernel:.................Failed: Not a 32-bit executable
Could not load tftp://10.61.33.230/kernel: Not a 32-bit executable
*** command status = -12

Solution: Download the correct version of the netboot kernel for your platform.

Example: Error - Could not activate network interface

LOADER-A> ifconfig e0M -addr=10.113.50.81 -mask=255.255.255.0 -gw=10.113.50.1
Could not activate network interface 'e0M': Error
*** command status = -1
Solution: The selected interface is not available for configuration: Check the output of show devices.

Example: incorrect path.

LOADER-A> netboot http://10.61.64.140/netboot/kernel
Loading 10.61.64.140/netboot/kernel: Failed: File not found Could not load http://10.61.64.140/netboot/kernel: File not found
Solution: Double check the path and provide the correct path. It would be good to add: 'Note: The path is relative to what the tftp/http root directory is set to. For instance, in the example above, if the http root directory on 10.61.64.140 is /etc/http, then netboot will be looking in the directory /etc/http/netboot for the file, kernel.'

Example: options http.admin.enable off (depending on version)

netboot http://10.61.64.140/na_admin/netboot/kernel
Loading 10.61.64.140/na_admin/netboot/kernel:Failed: Network protocol error
Could not load http://10.61.64.140/na_admin/netboot/kernel: Network protocol error
Network protocol error (errcode=-22)
-or-
Loading: Failed: Socket is not connected
Could not load http://10.61.64.140/na_admin/netboot/ Socket is not connected
*** command status = -39
Solution: The IP address used for netbooting is a duplicate - OR - The option http.admin.enable is not on. Enable the option with options http.admin.enable on.

Example: transfer interrupted

LOADER-A> netboot tftp://10.61.33.230/kernel
Loading 10.61.33.230/kernel:.......0x100000/3386728 0x53b000/3222096 0x84da50/1190096 Entry at 0x80148250
Found 10.61.33.230/platform.rc
Loading 10.61.33.230/platform.ko:.0x971000/546300 0xa99e60/514368 0x9f6600/17192 0xb177a0/29592 0x9fa928/1272 0xb1eb38/3816 0x9fae20/52267 0xa07a50/69035 0xa18800/1464 0xb1fa20/4392 0xa18db8/248 0xb20b48/744 0xa18eb0/968 0xb20e30/2904 0xa19278/128 0xb21988/384 0xa19300/130208 0xb21b08/138192 0xa38fa0/425 0xa5d500/8307 0xa99d73/237 0xa5f578/122208 0xa7d2d8/117403
Loading 10.61.33.230/rootfs.img.uzip:............................................0xb44000/14957240
Loading 10.61.33.230/platfs.img.uzip:Failed.: Timeout occurred
Failed.
Could not load tftp://10.61.33.230/kernel: Timeout occurred
Solution: Reattempt the transfer.

Example: Incorrect version of BIOS when attempting to netboot 8.2

LOADER-A> netboot tftp://10.61.33.230/kernel
Loading 10.61.33.230/kernel:.......0x100000/3386728 0x53b000/3222096 0x84da50/1190096 Entry at 0x80148250
Found 10.61.33.230/platform.rc
Loading 10.61.33.230/platform.ko:.0x971000/546300 0xa99e60/514368 0x9f6600/17192 0xb177a0/29592 0x9fa928/1272 0xb1eb38/3816 0x9fae20/52267 0xa07a50/69035 0xa18800/1464 0xb1fa20/4392 0xa18db8/248 0xb20b48/744 0xa18eb0/968 0xb20e30/2904 0xa19278/128 0xb21988/384 0xa19300/130208 0xb21b08/138192 0xa38fa0/425 0xa5d500/8307 0xa99d73/237 0xa5f578/122208 0xa7d2d8/117403
Loading 10.61.33.230/rootfs.img.uzip:............................................0xb44000/14957240
Loading 10.61.33.230/platfs.img.uzip:Failed.: Timeout occurred
Warning: /sbin/mount_nfs returned 60.
NFS netboot support has been deprecated.  If you did not
expect to see this prompt, ensure the system BIOS and
LOADER firmware are up to date.  Also be sure to follow a
supported netboot procedure.
Enter the NFS path for rootfs.img:
Solution: Upgrade system FW to a versions supported on 8.2, consult the bios compatibility matrix.

Note: FAS3140/3160/3170 with PAM1 and PCI-e adapter cards might report a Resource Conflict Error during the NetBoot procedure.

FAILURES DURING UPGRADES
During an upgrade to minor or major versions of Data ONTAP, it might become necessary to netboot the storage controller to recover from a failure. The specific recovery steps are dependent on the current status of the system, versions of Data ONTAP, and mode of failure. Contact Support for assistance in recovering from the error.

REVERT

When reverting from one major version of Data ONTAP to another, a very specific set of steps must be followed to properly revert the system. Most commonly, a system is rebooted before all of the steps have been completed to properly revert the system. When the error occurs, raid label errors might be reported, as see in the following output. Netboot might be needed to address this, contact support for the required recovery steps.

BOOT MEDIA

The boot media in NetApp storage systems are platform specific, and are either CF card or USB based devices. Should a boot device need to be replaced, refer to the boot device replacement documentation for your platform and version of Data ONTAP.

NetApp provides no representations or warranties regarding the accuracy or 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.