A B C D E F G H I L M N O P R S T U V
Index
A
- adapters
- cabling F800 series cluster
- cabling FAS3000 series cluster
- cabling FAS900 series cluster
- dual-port FC-AL
- installing
- NVRAM5
- removing
- adding a disk shelf
- to mirrored cluster
- to standard cluster
- aggregates
- re-creating mirrored after disaster
- rejoining after disaster
- AT-FCX modules, about
- audience
B
- bring up
- configuring interfaces for
- first time
- manually setting options for
C
- cabling
- Channel A loop in mirrored FAS3000 cluster
- Channel A loop in mirrored FAS900 cluster
- Channel A loop in standard F800 cluster
- Channel A loop in standard FAS3000 cluster
- Channel A loop in standard FAS900 cluster
- Channel B loop in mirrored FAS3000 cluster
- Channel B loop in mirrored FAS900 cluster
- Channel B loop in standard F800 cluster
- Channel B loop in standard FAS3000 cluster
- Channel B loop in standard FAS900 cluster
- dual-port FC-AL
- FC-ALs in FAS900 series mirrored cluster
- location of FAS900 dual-port FC-ALs
- preparing equipment racks for
- preparing system cabinets for
- required
- cf giveback command
- cf-config-check.cgi utility
- checking configuration through a utility
- CIFS sessions terminated on takeover
- cluster adapter
- cabling for F800 series
- cabling for FAS3000 series
- cabling for FAS900 series
- cluster configuration checker
- Cluster failover (CFO)
- cluster types
- comparison
- Fabric Attached MetroCluster
- installed in equipment racks
- installed in system cabinets
- mirrored
- nonswitched MetroCluster
- standard
- clusters
- benefits of
- characteristics of
- configuration information for
- configuring interfaces for
- definition of
- disabling
- displaying disk information
- enabling and disabling takeover (cf)
- first-time bring up of
- hardware components described
- managing in normal mode
- command exceptions for emulated nodes
- commands
- cf (enables and disables takeover)
- cf forcegiveback
- cf forcetakeover (forces a takeover)
- cf forcetakeover (forces takeover)
- cf giveback
- cf giveback (enables giveback)
- cf partner (displays partner's name)
- cf status (determines status)
- cf status (monitors status)
- cf takeover (enables takeover)
- cf takeover (initiates takeover)
- cfclear clears configuration)
- cfgdisable (disables configuration)
- cfgsave (saves configuration)
- configshow (shows switch settings)
- configure (switch parameters)
- halt (halts system without takeover)
- license add (license cluster)
- partner (accesses emulated node)
- storage show disk -p
- switchdisable (disables switch)
- switchenable (enables switch)
- switchname (sets switch name)
- sysconfig/aggr status (displays disk information)
- takeover (description of all takeover commands)
- version (displays switch firmware)
- communications regulations
- configuration
- displaying information for cluster
- reestablishing after disaster
- testing
- configuring
- dedicated and standby interfaces
- interfaces
- shared interfaces
- Controller failover
-
- command
- formatting
- keyboard
D
- Data ONTAP
- in a Fabric Attached MetroCluster
- in a mirrored cluster
- in a nonswitched MetroCluster
- in a standard cluster
- dedicated and standby interfaces, diagram
- dedicated interfaces
- configuring using ifconfig
- configuring using setup
- described
- dedicated interfaces, configuring
- definitions
- appliance
- disk shelf
- F800
- Fabric Attached MetroCluster
- FAS3000
- FAS900
- FC HBA
- FC HBA for Disk
- mirrored cluster
- nonswitched MetroCluster
- switch fabric
- diagnostics, running
- disabling clustering
- disaster recovery
- forcing takeover
- manual fencing
- restricting access to failed node
- steps
- using MetroCluster
- when not to perform
- disasters
- determining whether occurred
- recognizing
- disk information, displaying
- disk shelf
- about adding
- adding to cluster
- adding to mirrored clusters
- adding to standard cluster
- installing in existing mixed-shelf loop
- restrictions for adding
- upgrades supported
- upgrading modules for
- documentation, required
- dual paths, about
E
- eliminating single-point-of-failure
- emulated LANs, considerations in clusters
- emulated node
- accessing from takeover node
- accessing from takeover node (partner)
- accessing remotely
- command exceptions
- description of
- dumps and restores
- equipment racks
- installing in
- preparation of
- ESH modules, about
- ESH2 modules, about
F
- Fabric Attached MetroClusters
- advantages of
- behavior of Data ONTAP with
- cabling the local node and disk shelves in
- cabling the remote node and disk shelves in
- configuring the switches in
- planning worksheet example
- restrictions
- Fabric Attached Metroclusters
- limitations
- failover
- cause-and-effect table
- determining status (cf status)
- determining status in a cluster
- FC-AL adapters, installing
- fencing, manual
- forcing a takeover
- forcing giveback
G
- GBIC, removing
- giveback
- description of
- executing
- forcing
- processes that prevent giveback
- testing
H
- halting system without takeover (halt)
- hardware
- cluster components
- installing an adapter
- removing an adapter
- removing F800 series clustering
- removing FAS900 and FAS3000 series clustering
- upgrading nondisruptively
I
- installing FC-AL adapters
- installing, adapters
- interface configurations
- dedicated
- shared
- standby
- interface types and configurations
L
- licenses
- disabling cluster
- enabling cluster
- required
- LRC modules, about
- lun commands, lun online
- LUNs, bringing online
M
- mailbox disks
- manual fencing
- MetroClusters
- converting to a Fabric Attached
- defined
- Fabric Attached
- See Fabric Attached MetroClusters
- non-switched
- about
- advantages of
- Data ONTAP and
- illustration of
- setup requirements for
- reestablishing configuration after disaster
- mirrored clusters
- about
- adding a disk shelf to
- advantages of
- behavior of Data ONTAP with
- cabling Channel A loop for FAS3000 series in
- cabling Channel A loop for FAS900 series in
- cabling Channel B loop for FAS3000 series in
- cabling Channel B loop for FAS900 series in
- FC-ALs in FAS900 series
- restrictions
- setup requirements for
- modules
- about
- best practices for changing
- hot-adding to existing loop
- hot-swapping
- restrictions for changing types
- testing
- upgrading
- mounting volumes
N
- negotiated failover See failover
- network interfaces
- cluster configuration for takeover
- emulated LAN considerations in clusters
- types and configurations in a cluster
- nondisruptive cluster upgrades, hardware
- non-switched MetroClusters See MetroClusters
O
- options
- recommended to be identical between nodes
- required to be identical between nodes
- setting
P
- parameters
- required to be identical between nodes
- setting
- partner command
- partner name, displaying (cf partner)
- preparing equipment racks
R
- racks, installing in equipment
- reestablishing cluster configuration
- removing hardware
- requirements
- cable
- documentation
- equipment
- tool
- restrictions
- Fabric Attached MetroCluster
- in mirrored clusters
- rsh, using to access after takeover
S
- safety information
- setting options and parameters
- setup, running on clusters
- shared interfaces
- configuring using ifconfig
- configuring using setup
- described
- diagram
- single-point-of-failure
- eliminating
- SNMP protocol, in clustered takeover mode
- special messages
- standard cluster
- adding a disk shelf to
- behavior of Data ONTAP with
- cabling Channel A loop for F800 series in
- cabling Channel A loop for FAS3000 series in
- cabling Channel A loop for FAS900 series in
- cabling Channel B loop for F800 series in
- cabling Channel B loop for FAS3000 series in
- cabling Channel B loop for FAS900 series in
- contents of
- standby interfaces
- configuring using ifconfig
- configuring using setup
- described
- status messages, descriptions of
- status, monitoring cluster
- switch fabric
- switches
- banks
- cabling the local node and disk shelves with
- cabling the remote node and disk shelves with
- checking firmware revision for
- configuring for MetroCluster
- disabling
- pools
- quadrants
- setting the parameters
- system cabinets
- installing in
- preparing for cabling
T
- takeover
- CIFS sessions and
- configuring with dedicated and hot standby interfaces
- forcing for disaster recovery
- mode with SNMP
- rsh access after
- statistics
- telnet access after
- testing
- what happens after
- what happens during
- when occurs
- with SNMP
- telnet, using to access after takeover
- tools, required
- troubleshooting
- giveback failure on F800 series
- giveback failure on FAS3000 series
- giveback failure on FAS900 series
- takeover failure on F800 series
- takeover failure on FAS3000 series
- takeover failure on FAS900 series
U
- upgrading
- disk shelf modules
- hardware nondisruptively
V
- VI cluster adapter, removing
- VIFs, using to reduce SPOF
- volumes, mounting
A B C D E F G H I L M N O P R S T U V
Copyright © 1994-2005, Network Appliance, Inc. All rights
reserved.
Part No. 210-01386_C0
File: bookix.htm
Last updated: 21-Dec-2005 11:32:09