Concluding the upgrade

Potential tasks for concluding the upgrade

The following table lists the tasks that you might need to perform to complete upgrade.

If...	Then see...
Your deployment includes a shared switch	Specifying the target queue depth length for a port
You upgraded from Data ONTAP 5.0 or earlier and want to use a security style that is compatible with CIFS	Changing to CIFS-compatible security styles
You purchased any new service or protocol that you are starting to use with the upgrade	Entering codes for new licenses
You want to configure NetApp volumes, add LUNs to NetApp volumes, or configure other Data ONTAP features	gFiler Gateway Series Setup, Installation, and Management Guide and the Data ONTAP documentation library

Specifying the target queue depth length for a port

If your deployment includes a shared switch, you need to plan for and configure the gFilers to limit the number of commands (read and write requests) that the storage subsystem port must handle as a result of gFilers and non-gFiler hosts accessing the port through the switch; that is, you need to plan for limiting the target queue length. When multiple initiators are accessing a target port on the storage subsystem, you do not want the outstanding commands in the queue buffer, from all initiators together, to exceed 256. Otherwise, the performance of gFiler and non-gFiler hosts can suffer.

Beginning with Data ONTAP 5.0, on gFilers you use the disk.target_port.cmd_queue_depth option to set the number of commands that the gFiler can send to the target port on the data subsystem.

Non-gFiler hosts also provide a means for limiting the target queue length. See the documentation for the host for information about limiting target queue length.

Note
Target queue length might also be referred to as Q-Depth or Max Throttle.

Guidelines for determining the appropriate target queue length

You need to consider the impact of all the initiators on the port when you are planning the configuration for a specific gFiler or a specific non-gFiler host. If your deployment includes more than one initiator, you need to configure each initiator so that the total commands by all initiators does not exceed 256. The default for target queue depth value is 256.

Some guidelines for determining the appropriate target queue length are as follows:

0 (zero) means no limit on the outstanding commands. Therefore, do not configure a value of 0.
You could divide 256 by the number of gFiler and non-gFiler hosts that will be acting as initiators on the target port on the storage subsystem, configuring each gFiler and non-gFiler host with the value that resulted.
You could consider the volume of commands that specific initiators would be likely to send to the target port. You could then configure higher values for initiators likely to send a greater number of requests and a lower value for initiators likely to send a lesser number of requests.

Configure non-gFiler hosts according to the guidelines provided for those hosts.

Setting the target queue depth length

To set the disk.target_port.cmd_queue_depth option, complete the following steps.

Step	Action
1	Enter the following command at the Data ONTAP command line: `disk.target_port.cmd_queue_depth <value>` Do not use a value of 0 (zero) because it means no limit on the outstanding commands.

Changing to CIFS-compatible security styles

You change the security style of a gFiler by changing the qtree security style of its root volume. The new security style applies to the root volume and is the default security style for subsequently created volumes and qtrees.

To change the security style of the root volume to mixed or to the NT file system (NTFS) to make it compatible with CIFS, complete the following step at the gFiler console.

Step	Action
1	Enter the following command: qtree security /vol/vol0/ security_style security_style is either `mixed` or `ntfs`. `mixed` allows both UNIX-style and Windows NT-style permissions. `ntfs` allows only Windows NT-style permissions.

Entering codes for new licenses

To enter new license codes, complete the following step from the gFiler console.

Step	Action
1	Enter the following command: *license add code* ...** code is the license code that you were given when you purchased the license for a service or protocol. Example In this example, the license code for CIFS is ABCDEFG and the license code for DAFS is TUVWXYZ. `license add ABCDEFG TUVWXYZ` Result The gFiler acknowledges each license, as shown in the following example: A cifs site license has been installed. Use "cifs setup" to configure cifs. Run cifs setup to enable cifs. A multistore site license has been installed. Use "multistore setup" to configure dafs.

Step

Action

Enter the following command:

license add code ...

code is the license code that you were given when you purchased the license for a service or protocol.

Example

In this example, the license code for CIFS is ABCDEFG and the license code for DAFS is TUVWXYZ.

license add ABCDEFG TUVWXYZ

Result

The gFiler acknowledges each license, as shown in the following example:

A cifs site license has been installed.

         Use "cifs setup" to configure cifs.

         Run cifs setup to enable cifs.

A multistore site license has been installed.

         Use "multistore setup" to configure dafs.