This section contains changes that could not be included in NetApp documentation. The information in this section supersedes the information in any other NetApp documentation.
This release does not support clusters with ATM FORE/IP Permanent Virtual Circuits (PVCs). PVCs are statically assigned. For each destination, you must establish (attach the IP layer to) a PVC explicitly and delete (detach the IP layer from) the PVC explicitly.
Note: Bringing a SPANS interface down does not flush incoming or outgoing PVCs. You must enter an explicit atmarp -d and atmarp -x command or wait until the filer reboots to flush PVCs.
A FORE/IP SPANS interface is supported for each ATM adapter and has the prefix fa. An interface with the prefix a now refers to the physical ATM adapter. Use the adapter interface to configure a LANE partner for clusters. You do not assign it an IP address.
If you plan to use CIFS, set the wafl.net_admin_priv_map_to_root option to On. This option maps the Windows NT administrator to root. If you do not set this option to On, you cannot perform administrative tasks from a Windows client.
Using the date or rdate command to make the date on a filer go backward when the SnapMirrorTM feature is running can cause snapshots to appear out of sequence. When this occurs, SnapMirror assumes that the older snapshot was created before the newer one, causing SnapMirror to ask for a new, complete transfer before proceeding with any incremental transfers.
To avoid this problem, turn SnapMirror off until the filer completes the date change, or change the date while SnapMirror is inactive.
A filer can contain up to 20 destination volumes (mirrors) used by SnapMirror. The filer does not replicate data to more than 20 mirrors. For example, if you specify 21 local mirrors in the /etc/snapmirror.conf file, the filer replicates data only to the first 20 mirrors specified. When the filer tries to replicate data to the 21st volume, it displays the following message:
/etc/snapmirror.conf: line 21 Error Scheduling snapmirror, ignoring line
On page 540 of the System Administrator's Guide, Step 1 of the procedure for converting a mirror to a regular volume should read as follows:
If you want to enable quotas after converting the mirror to a regular volume, go to Step 2. Otherwise, go to Step 3.
Data ONTAP 5.3.2 enables you to create up to 24 volumes on a filer, not 23 as stated in the System Administrator's Guide.
The filer automatically sets the maximum number of files for a newly created volume based on the amount of disk space in the volume. The filer also increases the maximum number of files when you add a disk to a volume. In either case, the number set by the filer never exceeds 33,554,432. Imposing a limit on the maximum number of files prevents a filer with terabytes of storage from creating a very large inode file (for example, a 64-GB inode file) that might be unnecessary.
If you need a larger number of files on your filer, use the maxfiles command to increase the number beyond 33,554,432.
The setup command does not prompt for PC-style or UNIX-style permission semantics as stated in First-Time Configuration Using the Setup Command.
The System Administrator's Guide should mention that the filer supports media changers only if they are compliant with SCSI-2 specifications.
The information in "Shared interface example" on page 128 of the System Administrator's Guide needs the following clarification:
If you are configuring EtherChannel trunking for clusters using ATM LANE with the ifconfig command, you must provide interface names rather than interface addresses in the ifconfig partner command. For example:
ifconfig fa1 partner fa2
Upon takeover, all ELANs on partner interface a2 are configured on local interface a1. Local interface a1 and partner interface a2 should not have ELANs in common before the takeover.
If you are configuring clusters with virtual interfaces as described in "Creating second-level virtual interfaces in a cluster" on page 148, you must provide interface names rather than interface IP addresses in the ifconfig partner command.
For example, to configure local virtual interface vif0 for takeover of the partner's vif1 virtual interface, use the following command:
ifconfig vif0 partner vif1
Note that virtual interfaces can only take over for other virtual interfaces.
In addition to the filers listed in "LANE standards supported in this release" on page 162, the standards are also supported on the F720 and F740 filers.
The permission checking for NFS users accessing files with Windows NT-style security has changed in Data ONTAP 5.3. If a file has Windows NT-style security, the NFS accessor's UID must map to a Windows NT account.
You can ensure access in either of the following ways:
| 1 | Set up a special Windows NT account for mapped users that are not found in the NT domain. |
| 2 | Set the wafl.default_nt_user option with the account that you set up in Step 1. |
NDMP file history does not support Unicode. Therefore, if you use a third-party tool to back up a filer using the Unicode directory format, the NDMP client displays the file names in the NDMP file history database in one of two ways:
:XXXXXXX
where XXXXXXX is a character string.
Because NDMP uses the restore command to recover files, you can use NDMP to restore files with correct file names regardless of how the client displays the file names in the NDMP file history database.
The section titled "Using disks of various sizes" in the System Administrator's Guide refers to SCSI disk shelves only.
The example for the -o option in the table at the top of page 246 of the System Administrator's Guide should read
exportfs -i -o rw=mixer /vol/vol0/home/terry
Copyright © 1998-1999, Network Appliance, Inc. All rights reserved.
Part No. 210-02449
File: common4.htm
Last updated: 07/23/99 14:38:18