In Data ONTAP 6.5, access rules in the /etc/exports file changed. Rules that previously allowed read access to all hosts have been changed to allow no access. For example, this is a rule in pre-6.5 versions of Data ONTAP:
/vol/vol1 -rw=host1:host2
The rule meant that the hosts named host1 and host2 both had read-write access to vol1, while all other hosts had read access.
In Data ONTAP 6.5 and later, the rule now means that host1 and host2 have read-write access and all other hosts have no access. To allow read access for all hosts in 6.5, you need to add -ro after vol1 to allow read access to all hosts:
/vol/vol1 -ro,rw=host1:host2
The first time you upgrade to Data ONTAP 6.5 or later, the /etc/exports file is changed automatically to be sure your rules work the same way:
/vol/vol1 -rw=host1:host2
are converted to the form
/vol/vol1 -ro,rw=host1:host2
When subsequent upgrades are performed, Data ONTAP assumes that the rules in the /etc/exports file have already been converted and additional conversions do not take place.
Other changes to the /etc/exports file in Data ONTAP 6.5 include the following:
The -access option was used to list hosts that could have any access. Instead, the -rw and -ro options are used together to enable the same privileges.
The sizes of existing volumes' RAID groups remain the same as before the Data ONTAP 6.5 upgrade, even if the size exceeds the new limits. However, the raidsize option changes to the new, reduced limit, and any new RAID groups that are created as disks are added to the volumes to conform to the new raidsize option.
The default RAID group size for gFilers is 8; the limit is 14.
If you are upgrading from 6.5 or a 6.5R release, you can skip this section.
In pre-6.5 Data ONTAP releases, gFiler ownership of LUNs was based on a 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, setting the LUN ownership to low. NetApp configured all LUNs with Host IDs from 128 to 255 to the other gFiler in the cluster, setting the LUN ownership to high.
Starting with Data ONTAP 6.5, gFilers began using a software-based scheme instead of the fixed scheme to control access of gFilers to LUNs that a storage subsystem makes available to gFilers. The following illustration shows the relationship between the LUNs that are made available for gFilers on the storage subsystem and configuration of the gFiler.
When you follow the upgrade procedure in this guide, the previous fixed LUN ownership scheme is upgraded to the new software-based scheme.
Caution
The gFiler software-based scheme provides LUN ownership control only for gFilers. It does not prevent gFilers and non-gFiler hosts from overwriting data in the same LUN. See the gFiler Gateway Series Software Setup, Installation, and Management Guide for deployment recommendations.
The software scheme enables you to make changes at the software level that previously could only be made at the hardware level. See the gFiler Gateway Series Software Setup, Installation, and Management Guide for more information about the software LUN ownership scheme for gFilers.
If you revert to a version of Data ONTAP prior to 6.5, you must revert the LUN ownership scheme used in Data ONTAP 6.5 and later to the fixed scheme used by previous releases. See gFiler-specific reversion issues and procedures--6.5.1 to pre-6.5 for more information about how to revert to the fixed ownership scheme and issues involved with reverting.
Copyright © 1994-2004, Network Appliance, Inc. All rights
reserved.
Part No. 210-00662
File: upgrade8.htm
Last updated: 04/12/04 17:11:45