gFiler-specific reversion issues and procedures--6.5.1 to pre-6.5

About this section

Use the information and procedures in this section if you want to revert your gFiler from Data ONTAP 6.5.1 to a version prior to 6.5.

Issues regarding LUN ownership

When you revert to a Data ONTAP version prior to 6.5, you must return to the pre-6.5 LUN ownership scheme. The reversion process removes all LUN ownership data from the storage subsystems that Data ONTAP 6.5 wrote to the LUNs. See Reverting from 6.5.1 to 6.4.x for a single node gFiler.

Requirement to create a LUN 0 on storage subsystem ports

Before you revert, you must configure LUN 0 on each channel adapter port accessible to a gateway. In releases prior to 6.5, Data ONTAP uses LUN 0 to gather information about other LUNs configured on the port.

When you cannot revert

Starting with Data ONTAP 6.5, you have the flexibility to mix the LUNs from the ranges among the gFilers. However, if you do so, you cannot revert to a release of Data ONTAP prior to 6.5.

Note
In pre-6.5 releases, gFiler ownership of LUNs was based on the fixed Host LUN ID scheme that was configured by NetApp for you. For clusters, NetApp configured all LUNs with Host LUN IDs from 0 to 127 to one gFiler in the cluster; that is, the cluster node was set with the LUN-ownership set to low. NetApp configured all LUNs with Host IDs from 128 to 255 to the other gFiler in the cluster; that is, that cluster node was set with LUN-ownership set to high.

Deployment issues when reverting

When you revert to a Data ONTAP version prior to 6.5, you must return to either of the configurations allowed for previous releases:

One single node
Two-node cluster

Starting with Data ONTAP 6.5, up to six gFilers can access LUNs on a storage subsystem. However, when you revert to a version of Data ONTAP prior to 6.5, you must return to the pre-6.5 LUN ownership scheme in which LUNs on the storage subsystem can be seen by a single gFiler or by a clustered pair. You must disconnect the remaining gFilers from storage subsystem.

Features not supported in pre-6.5 releases

The following features are not supported in pre-6.5 Data ONTAP releases:

SnapMover
SyncMirror
MetroCluster

Mixing software releases in a cluster

If you are reverting one partner in the cluster to a pre-6.5 release of Data ONTAP, you must also revert the other partner to a pre-6.5 release of Data ONTAP.

Reverting from 6.5.1 to 6.4.x for a single node gFiler

To revert to an earlier version of Data ONTAP when a gFiler is not a member of a cluster, complete the following steps.

Step	Action
1	Obtain the system files from the CD-ROM or from the NOW Web site, as described in Chapter 3, Upgrading Data ONTAP on the gFiler.
2	Transfer the system files onto the gFiler using either the UNIX NFS or Windows method described in Installing Data ONTAP system files.
3	From the console prompt, enter the following command: `download` Note Do not reboot your gFiler at this step. If your gFiler reboots itself, contact NetApp Technical Support or your authorized reseller.
4	From the console prompt, enter the following command: `revert_to 6.4`
5	Follow the instructions on the screen about the conditions that you need to complete.
6	From the console prompt, enter the following command again: `revert_to 6.4` Result The 6.4.x release is restored on the gFiler.
7	At the ok prompt, enter the following command: `bye`
8	Configure the initiators-per-port option, as described in Setting the initiators-per-port environment variable.

Reverting to 6.4.x when a gFiler is a cluster member

To revert to an earlier version of Data ONTAP for gFilers in a cluster, complete the following steps.

Note
If you mixed LUNs from the ranges among the gFilers in the cluster, you cannot revert. See When you cannot revert.

Step	Action
1	Obtain the system files from the CD-ROM or from the NOW Web site, as described in Chapter 3, Upgrading Data ONTAP on the gFiler.
2	Transfer the system files onto one gFiler in the cluster using either the UNIX NFS or Windows method described in Installing Data ONTAP system files.
3	Disable the cluster by entering the following command at the console of one of the gFilers: `cf disable`
4	Enter the following command and note whether the LUNs are in the low range or high range: `sysconfig -r` If the LUN numbers are in the range of 0 to 127, they are in the low range. See When you cannot revert for issues related to mixed ranges that prevent reverting.
5	From the console prompt, enter the following command: `download`
6	From the console prompt, enter the following command: `revert_to 6.4` If the revert fails with the message "Unable to revert since LUN firmware isn't set!," Halt the gFiler. At the prompt, enter one of the following commands, depending on the range of the LUNs on this gFiler: `setenv LUN-ownership high` OR `setenv LUN-ownership low` Note If you set the LUN-ownership to high on this gFiler, you must set LUN-ownership to low on the other gFiler.
7	Follow the instructions on the screen about the conditions that you need to complete.
8	From the console prompt, enter the following command again: `revert_to 6.4` Result The 6.4.x release is restored on the gFiler.
9	Press Delete while the memory test is in progress to interrupt the boot process.
10	Configure the initiators-per-port option, as described in Setting the initiators-per-port environment variable.
11	Enter the following command: `bye`
12	On the partner in the gFiler cluster, follow Steps 1 through 11. Ensure that if you set LUN-ownership to high on the other gFiler that you set it to low on this gFiler, and vice versa.
13	Reenable the cluster by entering the following command on one of the gFilers: `cf enable`