Providing disk (LUN) ownership and system identification data

Power on the gFiler to load the kernel from the CompactFlash^TM card.

Result

The system boot process begins.

Interrupt the boot process by pressing Ctrl-C when you see the following message on the console:

Starting Press Ctrl-C for floppy boot menu

Result

The following boot options menu appears:

(1) Normal boot.

(2) Boot without /etc/rc.

(3) Change password.

(4) No disks assigned (use `disk assign' from the

    Maintenance Mode).

(5) Maintenance mode boot.

Enter 5 for Maintenance mode.

Determine the disks (LUNs) on the storage subsystem that you want this gFiler to be configured to own. Enter

disk show -v

A list of all LUNs available on the storage system port to which the gFiler is physically connected is displayed.

Caution
LUN security can be configured on a storage subsystem to restrict the LUNs that are available to specific hosts. NetApp recommends that you use LUN security to prevent gFilers from accessing LUNs owned by non-gFiler hosts, and the reverse.

If LUN security is not configured, all LUNs mapped to the port on the storage subsystem are visible to all gFilers and non-gFilers connected to the port. In this case you must pay close attention to how you assign disk (LUN) ownership in the next steps so that gFilers do not overwrite LUNs owned by non-gFilers.

Assign the LUNs (disks) on the storage subsystem that you want this gFiler to own.

You must assign one LUN. You can assign more LUNs at this stage or wait to assign additional LUNs after Data ONTAP is installed. In most cases, you will use the disk assign command to identify specific disks (LUNs) that this gFiler is to own. If this gFiler is to own all the LUNs, you can use the disk assign all command.

Caution
This step is a destructive operation. Ensure that you are not performing this step on a LUN that is to be used by a host such as a Hewlett-Packard® or Sun® host. Although the gFiler provides controls to prevent one gFiler from owning a LUN that is assigned to another gFiler, there are no controls to prevent you from assigning a gFiler ownership of a LUN owned by a non-gFiler host. Because the gFiler writes ownership information to the LUN when you use the disk assign command, and the non-gFiler host has already configured its version of ownership to the LUN, the LUN becomes corrupted. It is not possible to reverse the corruption. Using LUN security on the storage subsystem will enable you to restrict the hosts that are visible and, therefore, eliminate the possibility of a gFiler overwriting a non-gFiler owned LUN.

If you are not going to be deploying SyncMirror, enter the command in the form

disk assign fullLUNname1 fullLUNname2 ...

You do not need to enter the pool parameter (-p). The pool parameter defaults to 0 (zero).

You can enter all LUNs for a particular storage subsystem on the same command line.

If you are going to be deploying SyncMirror, you must use the pool parameter with the disk assign command, and you enter the pool parameter correctly. See Planning for RAID mirroring for data protection for details so that you can plan your configuration correctly.

Command example:

disk assign storeAlun1 storeAlun2 -p 0
disk assign storeBlun1 storeBlun2 -p 1

Typically, pool 0 is assigned to the local pool and pool 1 is assigned to the remote pool.

Enter the following command:

disk show -v

The Local System ID is shown and the LUNs (disks) exported on the port are shown.

Review the list of disks (LUNs) to confirm that all disks (LUNs) that you expected to be assigned to this gFiler (the local system) are shown with the ID of this gFiler.

Enter halt, then type boot at the OK prompt.

Press Ctrl-C to interrupt the boot process.

Result

The following boot options menu appears:

(1) Normal boot.

(2) Boot without /etc/rc.

(3) Change password.

(4) Initialize owned disks (n are owned by this filer).

(5) Maintenance mode boot.

n in Option 4 is the number of disks (LUNs) that were assigned in Option 5 for this gFiler to own.

Select Option 4.

This step creates a root volume with one of the LUNs that you entered in Step 5. The LUN is automatically selected; it is typically the smallest LUN.

Enter y when prompted as to whether you want to install a new file system.

Enter y to the following message:

This will erase all the data on the disks, are you sure?

Result

The gFiler creates a root volume using one of the assigned LUNs and begins prompting for system information.

When you see the question "Would you like to continue setup through the Web interface?" enter n and continue using the setup command. Answer the prompts in the setup program, using the information that you gathered.

See Gathering data needed for the setup program for help with answering the setup prompts.

If you want remote console access, answer y when prompted as to whether you want to configure the RMC LAN interface.

This prompt is displayed only for the gFiler 900 series models.

Install licenses and install and download Data ONTAP software, as described in Chapter 4, Installing Data ONTAP Software.

If you have a gateway cluster, repeat the same procedure on the other gateway in the cluster.

disk show -v

Shows all disks (LUNs) that are mapped to the physical port on the storage subsystem to which the gFiler is connected. The LUNs might be owned or unowned.

disk show -a

Shows all disks (LUNs) that have an owner.

disk show -n

Shows all disks (LUNs) that do not have an owner.