Monthly Archives: August 2015

Netboot

How to Network Boot (Netboot) a LOADER / CFE based filer in Data ONTAP 7G

 

KB ID: 1012003 Version: 13.0 Published date: 03/02/2015 Views: 14837

Description

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:

Procedure

For setting up TFTP services for netbooting:

  1. Log in to a controller that is up and running Data ONTAP.
  2. On the controller, type the following:
    filer> options tftpd.enable on
  3. Create the /etc/tftpboot directory 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.
  4. Place the netboot kernel image into this directory (/etc/tftpboot or 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:

  1. Log in to a controller that is running Data ONTAP.
  2. Place the netboot kernel, for example netapp-mips, into the /etc/http directory. 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 /etc/http directory, type:
    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
Execute netboot
:///  command:
LOADER> netboot tftp://192.168.1.11/tftproot/netapp_7.2.3_x86_64
Loading:...........

Type the following at the LOADER> prompt to display the complete syntax: help ifconfig

Notes:

  • 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.

Important Note:
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.

Related Links:

Note: Use the netboot file when downloading and installing Data ONTAP.

 

Disclaimer

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.

Cluster mode to 7 mode

Maybe this will help.

The Controller is now set to boot c-mode. You need to change this at the LOADER prompt.

Procedure:

– halt controller

– at the boot loader, set the environment variable bootarg.init.boot_clustered to false

LOADER> setenv bootarg.init.boot_clustered false

– Install 7-mode

– boot into the boot menu and select 4 for the initial installation

How to move an aggregate between software disk-owned HA pairs.

How to move an aggregate between software disk-owned HA pairs.

 

KB ID: 1011651 Version: 7.0 Published date: 08/07/2014 Views: 3206

Description

This article explains, how move an aggregate from one controller in a HA pair to its partner in a software disk owned system. This procedure only applies to 7-mode systems.

Procedure

For reference: FILER1 owns the disk initially. FILER2 is where the disks/volume are being moved to.

WARNING:
Before starting this procedure, confirm that there are no aggregates or FlexVols on FILER2 that have the same name as the original aggregate/FlexVols or traditional volume being moved. Failure to do so will result in the relocated volume(s) with conflicting names being appended with a (1) instead of the original name.

Note:
This procedure is only supported under the following conditions:

  • Disks do not get moved, ownership remains of either node in HA pair.
  • If disks are moved outside the HA pair, shelf MUST NOT be moved.

It could be misunderstood to move disk/shelf to another filer using similar procedure. If the shelf needs to be moved outside of the HA pair, downtime is required.

    1. Start by taking the aggregate offline from FILER1.

Example:
For a traditional volume:

FILER1>aggr offline <volname>

      For an aggregate with FlexVols:

FILER1>priv set diag
FILER1*>aggr offline <volname> -a
FILER1*>priv set admin
FILER1>

    1. Move disk ownership of all disks in the aggr to FILER2.

WARNING:
The node on which the disk assign is done must be the node that is giving away the aggregate.

   FILER1> disk assign 0a.16 0a.17 0a.18 0a.19 -o FILER2 -f

(-f must be used since the disks are already owned)

    1. Verify that no further disks belonging to the original aggregate are left on the original node.

FILER1>aggr status -r <original-volname>

    1. Online the relocated aggregate from FILER2:

FILER2> aggr online <test>

Note:
It will be necessary to reconfigure any Common Internet File System Protocol (CIFS) shares,Network File System (NFS) exports or configure the appropriate igroups on the partner for the relocated volume(s) before clients can access this data.

Related Link:

 

Disclaimer

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.