Preliminary procedures

About the preliminary procedures

Before installing the latest Data ONTAP release on your filer, you might need to perform one or more of the procedures described in the following table.

Procedure	Complete the procedure if...
Saving core files	Your situation meets both of the following criteria: You are upgrading from a release of Data ONTAP earlier than 4.0.3. Your filer contains core files that have not been saved. Caution When you boot the latest release of Data ONTAP and the filer then executes `savecore`, it does not recognize a core file written by a release earlier than 4.0.3.
Verifying that the filer has a domain account	You are running CIFS on the filer and are using a Windows NT 4.0 domain controller for authentication. In this case, the filer must have a domain account.
Enabling DNS with Windows 2000 name server addresses	You are running CIFS on the filer and are using a Windows 2000 domain controller for authentication.
Removing `snap reserve` and `snap sched` commands	You will create additional volumes after the upgrade and are upgrading from Data ONTAP 5.0 or earlier. The lack of a volume name in the `snap sched` command in a release earlier than Data ONTAP 5.0 prevents the command from working properly on a multivolume system. In Data ONTAP, the `snap reserve` and `snap sched` commands are persistent across reboots.
Clients unmounting the filer	You are upgrading from Data ONTAP 4.0.1c or earlier and have clients using NFS over TCP. Starting with Data ONTAP 4.0.3 and continuing in the latest release of Data ONTAP, NFS over TCP is disabled by default, so clients do not have to unmount the filer. In Data ONTAP 4.0.1c, NFS over TCP is enabled.

Saving core files

To save core files, complete the following step.

Step	Action
1	From the filer, enter the following command: savecore

Verifying that the filer has a domain account

To verify that the filer has a domain account, complete the following step.

Step	Action
1	From the filer, enter the following command: cifs lookup

Enabling DNS with Windows 2000 name server addresses

To enable DNS with Windows 2000 name server addresses, complete the following steps.

Step	Action
1	Using a text editor, create or open the /etc/resolv.conf file in the root volume. Include up to three lines, each specifying a Windows 2000 name server host in the following format: nameserver ip_address Example: nameserver 192.9.200.10
2	Enter the following command to enable DNS: options dns.enable on

Step

Action

Using a text editor, create or open the /etc/resolv.conf file in the root volume. Include up to three lines, each specifying a Windows 2000 name server host in the following format:

nameserver ip_address

Example:

nameserver 192.9.200.10

Enter the following command to enable DNS:

options dns.enable on

Removing snap reserve and snap sched commands

To remove snap reserve and snap sched commands, complete the following step.

Step	Action
1	Use a text editor on your client system to remove any `snap reserve` and `snap sched` commands from the /etc/rc or C$\etc\rc file in the root volume.

Clients unmounting the filer

Complete the following step.

Step	Action
1	Have clients unmount the filer.