A C D E F G H I L M N O P R S T V W
Index
A
- administration tools
- Africa, time zone names for
- Australia, time zone names for
- Autosupport described
C
- Canada, time zone names for
- checksum space on LUN
- CIFS
- making gateway data available to
- oplocks, setting for volumes
- requirement for using
- cluster
- defined
- with GF270c
- Cluster Configuration Checker
- clustered gFilers
- checking configuration
- defined
- networking interfaces for
- verifying configuration for
- configuration worksheet
- core dump space on LUNs
D
- dedicated interfaces
- disk ownership
- assigning
- benefits of
- changing ownership of spares
- command
- control for gFilers only
- defined
- examples
- planning for
- rules for
- scheme described
- disk show command options
- disk.target_port.cmd_queue_depth option
E
- Europe, time zone names for
F
- FilerView
- accessing
- described
- how it works
G
- gFiler planning overview
- gFilers
- administration tools
- clusters, verifying configuration for
- GF270c
- cluster with
- MetroCluster and
- spare LUN requirement
- SyncMirror and
- GMT, time zone names for
H
- host name resolution, setting up
I
- installation overview
- installing Data ONTAP software
- interfaces
- dedicated description
- shared description
- standby description
L
- languages supported
- licenses
- codes for
- installing
- MultiStore
- SnapMover
- SyncMirror
- Logical Unit Number, defined
- LUN ownership
- assigning
- benefits of
- changing ownership of spares
- command
- control for gFilers only
- defined
- examples
- planning for
- rules for
- scheme described
- LUN security, preventing LUN overwriting
- LUNs
- adding to RAID groups
- adding to volumes
- changing composition
- changing size
- checksum space on
- core dump space on
- defined
- how gFilers access
- making available to gFilers
- making unused
- mapping to a non-gFiler host
- moving
- name format
- number in volume
- removing ownership
- spare defined
- spare requirement for GF270c
M
- MetroCluster
- deployment example
- GF270c and
- maximum in a neighborhood
- use with SyncMirror
- MultiStore vFilers with SnapMover
N
- neighborhood
- defined
- in switch fabric
- maximum MetroClusters in
- SnapMover with
- network connections, verifying
- New Zealand, time zone names for
- NFS hosts, making gateway data available to
- NOW Web site
O
- oplocks, setting for volumes
- overview, setup and installation
P
- planning overview
- plexes
- described
- relationship to pools
- when created
- pools
- relationship to plexes
- with SyncMirror
- prerequisites to setup
R
- RAID groups
- adding LUNs to
- default size
- when to change
- definition
- forcing a new one
- how created
- maximum number
- metrics
- modifying size of
- number in volume
- performance issues
- sizes
- RAID mirroring. See SyncMirror
- raidsize volume option
- changing size of
- forcing a new RAID group
- verifying setting
- RAID-0
- RAID-1
- RAID-10
- RAID-5
- Remote Management Controller
- connections and setup, verifying
- reverting SnapMover
- RMC connections and setup
- root volume
- defined
- minimum size
S
- security styles, setting for volumes
- setup data, providing
- setup overview
- setup program, gathering system data for
- shared switch configuration requirement
- SnapMirror, contrasted to SnapMover
- SnapMover
- command
- what it does
- contrasted to SnapMirror
- how it works
- information moved
- licenses for
- migration in neighborhood
- moving the vFiler
- preparing for use of
- purpose of
- requirements
- restriction
- qtree movement
- reverting
- setting up volumes
- vFilers with
- volume-level vFilers
- defined
- South America, time zones for
- spare LUN
- changing ownership of
- defined
- spare LUNs
- requirement for GF270c
- storage subsystems
- gFiler access to LUNs on
- switch fabric, neighborhoods in
- switch zoning, preventing LUN overwriting
- switches, configuration requirement with
- SyncMirror
- configuration requirement
- GF270c and
- how it works
- license for
- MetroCluster
- deployment example
- planning for
- plexes
- described
- pools with
- requirements
- example configuration
- storage space required
- why use
- with MetroCluster
- system data for setup program
T
- target queue depth length, setting
- time zones
- troubleshooting
- giveback failure
- takeover failure
V
- vFilers
- defined
- use with SnapMover
- volume association
- volumes
- adding LUNs to
- creating
- examples
- parameters after
- creating additional
- defined
- guidelines to determine
- LUNs in, number
- maximum number
- metrics
- moving LUNs in
- naming
- non-root
- size
- plexes in
- RAID groups in
- maximum number in
- root volume
- size
- security style
- setting up for SnapMover
- size
- guidelines to determine
- vFilers with
W
- workload distribution. See SnapMover
A C D E F G H I L M N O P R S T V W
Copyright © 1994-2004, Network Appliance, Inc. All rights
reserved.
Part No. 210-00661
File: bookix.htm
Last updated: 04/13/04 09:26:51