Chapter 2
Information Gathering
Information you need to gather
You need to collect the information described in the following tables to set up and configure your filer. You can use the Configuration Worksheet in Appendix A to record your values.
How setup methods call out information types
When you use a setup method, you are prompted to enter values for information types, depending on the setup method you've chosen. Not all setup methods prompt you for the same information or in the same order. The setup command prompts you for all of the values needed to set up your filer, based on what Data ONTAP discovers upon bootup.
The Setup Wizard prompts you for the information types related to basic filer configuration, network services, network addresses, and protocols.
The differences among the setup methods are noted in the following tables. The alternate names used by the Setup Wizard for the term used in the setup command appear in parenthesis.
Notation for filer cluster configurations
If you are configuring a filer as part of a cluster, some information types must be unique for each filer in the cluster, and some information types must be identical on both filers. In the tables below, the information type description indicates whether the information type must be unique for each filer or identical on both filers.
MAC address
If you intend to use the DHCP service to assign an IP address to the onboard interface, locate the MAC address and record it.
Information type
|
Description
|
MAC address (or Interface MAC Address)
|
The unique address of the network interface built into the filer's motherboard. You can find the address on a label on the back of F800 series filers or by entering sysconfig -a at the filer prompt and looking for the following output:
slot 0: 10/100 Ethernet Controller IV
e0 MAC Address: 00:00:4c:0f:2c:ee
|
Required filer information
The following information is required for all installations.
Information type
|
Description
|
Host name (Hostname or Filer Name)
|
The name by which the filer is known on the network.
If the filer is licensed for the NFS protocol, the name can be no longer than 32 characters.
If the filer is licensed for the CIFS protocol, the name can be no longer than 15 characters.
The host name must be unique for each filer in a cluster.
|
Password (Administrative Password)
|
A password that the filer requires before granting administrative access at the console, through a Telnet client, or through the Remote Shell protocol.
|
Time zone (Timezone)
|
The time zone in which the filer resides. See Appendix B, Time Zones for a list of valid time zones.
The time zone must be identical on both filers in a cluster.
|
Filer location (Location)
|
A description of the physical location of the filer. The string value you enter during filer setup process is recorded in the SNMP location information. Use a description that identifies where to find your filer (for example, "Lab 5, Row 7, Rack B").
|
Language
|
The language used for multiprotocol filers if both the CIFS and NFS protocols are licensed. See Appendix C, Supported Languages for a list of supported languages and their abbreviations.
The language must be identical on both filers in a cluster.
|
Administration host (Administrative Host)
|
A client computer that is allowed to access the filer through a Telnet client or through the Remote Shell protocol.
|
Virtual network interfaces
If you want to create virtual network interfaces (vifs), you must use the setup command. Begin by gathering the following information.
Information type
|
Description
|
Virtual network interfaces
|
For each vif, record the following information:
- Name of each vif
- Number of links for each vif
- Link names for each link
The virtual network interface information must be identical on both filers in a cluster.
|
Network information
If your network uses standard Ethernet or Gigabit Ethernet (GbE) interfaces, record the following information for each interface.
Information type
|
Description
|
Network Interface name
|
The name of the Ethernet (or GbE) interface, depending on what port the Ethernet card is installed in. Examples include e0 (for Ethernet single); e1 (for GbE); and e3a, e3b, e3c, e3d (for Ethernet quad-port). Network interface names are automatically assigned by Data ONTAP as it discovers them.
|
IP address
|
A unique address for each network interface.
|
Subnet mask (Network Mask)
|
The subnet mask for the network to which each network interface is attached.
Example
255.255.255.0
|
Partner IP address (Interface to Take Over)
|
If your filer is licensed for cluster takeover, record the interface name or IP address belonging to the takeover partner that this interface should take over during a cluster takeover.
Examples:
e0 or 10.10.10.2
For vifs, you must specify the interface name rather than the interface IP address.
|
Media type (Network Type)
|
The type of interface:
- 100tx-fd (100Base-TX, full-duplex)
- tp-fd (10Base-T, full-duplex)
- 100tx (100Base-TX, half-duplex)
- tp (10Base-T, half-duplex)
- auto (autonegotiate speed and duplex)
|
If the interface supports jumbo frames, Maximum Transmission Unit (MTU) size
|
The default frame size defined for a jumbo frame on the filer is 9,018 bytes, and the maximum supported size is 9,210 bytes. These sizes correspond to MTU sizes of 9,000 and 9,192, respectively.
Note See the Network Management Guide for details about MTU size. |
DAFS protocol
If your filer is licensed for the DAFS protocol, record the following information.
Information type
|
Description
|
VI/IP network device
|
If your network uses VI/IP network interfaces that you want to configure to work with DAFS, record the following information:
- IP address
- Netmask (or subnet mask)
|
Cluster network devices that use DAFS
|
Record the names of the cluster partner VI/IP network interfaces you want to configure to work with DAFS.
Note This information is required only if you licensed cluster takeover. |
Filer volumes to export
|
Record the names of the filer volumes exported through the DAFS service.
|
Authentication for privileged clients
|
Record the authentication level for privileged clients. This determines whether the clients communicating with the filer are privileged clients that are trusted to have multiple sets of user credentials.
Note The DAFS Database Accelerator client requests AUTH_NONE access to communicate with the filer. |
Idle timeout for sessions
|
Record the length of time, in seconds, that a session can be idle before a session ends, or times out.
|
ATM LANE
If your network supports ATM LANE, record the following information.
Information type
|
Description
|
ATM ForeIP/ SPANS
|
If your network uses Asynchronous Transfer Mode (ATM) Simple Protocol for ATM Network Signaling (SPANS) interfaces, record the following information for each interface:
- Interface name
- Host IP address
OR Partner IP address
- Netmask (or subnet mask)
- Media type
The ATM ForeIP/SPANS interface information must be identical on both filers in a cluster.
|
ATM LANE
|
If your network uses ATM LAN Emulation (LANE) interfaces, record the following information for each interface:
- Interface name
- Host IP address
OR Partner name
- Emulated LAN (ELAN) name
- LANE Configuration Server (LECS) address
- IP address
- Netmask (or subnet mask)
The ATM LANE interface information must be identical on both filers in a cluster.
|
Default gateway
If your network uses routers, record the following information.
Information type
|
Description
|
Router (Routing Gateway)
|
Record the following information for the primary gateway to use for routing outbound network traffic:
- Gateway name
- IP address of the router
|
HTTP protocol
If your filer is licensed for HTTP, record the following information.
Information type
|
Description
|
Location of the http directory
|
The directory where the Web files and directories are stored. The default directory is /home/http in the filer's root volume.
|
DNS services
To configure your filer to use DNS services, you must have the following DNS information.
Information type
|
Description
|
DNS domain
|
The name of your network's Domain Name Service (DNS).
The DNS domain name must be identical on both filers in a cluster.
|
DNS servers
|
The IP addresses of your DNS servers.
|
If...
|
You will need...
|
Your filer will not use Active Directory services
|
The IP address for one or more DNS servers that will provide host name lookup services to the filer.
|
You want to make Active Directory services available to CIFS
|
The IP address of DNS servers that support your Windows Active Directory domain.
|
NIS services
If your network uses NIS services, record the following information.
Information type
|
Description
|
NIS domain name
|
The name of your NIS domain. The filer can use an NIS Domain to authenticate users and client computers.
The NIS domain name must be identical on both filers in a cluster.
|
NIS servers
|
The host names of your preferred NIS servers.
|
If...
|
You will need...
|
Your site uses NIS
|
The host names of your NIS servers.
|
You want NIS to broadcast to find a server
|
To enter an asterisk (*) when asked for the NIS server names
|
CIFS protocol
If your filer is licensed for the CIFS protocol, record the following information.
Information type
|
Description
|
Windows domain
|
The name of your Windows domain. If your site uses Windows servers, it has one or more domains. Record the name of the domain to which the filer should belong.
Note The Windows domain name value does not need to be identical on both filers in a cluster. You can have each filer in a cluster exist in a different domain and/or workgroup from its partner. However, if you have a multiprotocol environment and use UID to SID mapping, the UNIX security information must be compatible between the two domains. |
WINS servers
|
The servers that handle Windows Internet Name Service (WINS) name registrations, queries, and releases. If you choose to make the filer visible through WINS, you need to record up to four WINS IP addresses.
Note The WINS server value does not need to be identical on both filers in a cluster. You can have each filer in a cluster exist in a different domain and/or workgroup from its partner. |
Windows Active Directory domain administrator user name
|
The user name of a Windows domain administrator with sufficient privileges to add this filer to the Windows domain.
Note This is only required if you are using a Windows Active Directory domain. |
Windows Active Directory domain administrator password (Windows 2000 administrator password)
|
The password for the Active Directory domain administrator user account. If your domain is an Active Directory domain, you must use the password for a user account with sufficient permissions to add the filer to the domain.
Caution Before you enter the password, be sure to create a secure connection (HTTPS); otherwise, the password is sent to the filer unencrypted.
|
Active Directory
|
The Windows Active Directory container in which to place filer accounts. This can be either the default of Computers or a previously created organizational unit (OU) specified by you. The path for the OU must be specified in reverse order, separated by commas.
Example
If the path is eng\dev\mgmt, the active directory distinguished name is as follows:
ou=mgmt, ou=dev, ou=eng
Note A user in the Windows Active Directory domain can precreate the account and Data ONTAP updates that account. See Precreating a Filer Domain Account in Active Directory (Optional) |
Remote management controller for Autosupport
If your filer has a remote management controller (RMC) for enhanced Autosupport, record the following information.
Information type
|
Description
|
MAC address
|
If you are using DHCP service, record the MAC address for the RMC. Locate the MAC address by entering sysconfig -v at the filer prompt and looking at the output for the RMC in slot 1.
|
IP address
|
If you are not using DHCP service, record the IP address for the RMC.
|
Network mask
|
If you are not using DHCP service, record the network mask for RMC.
|
Gateway
|
If you are not using DHCP service, record the IP address for the RMC gateway.
|
Media type
|
The type of interface for the RMC:
- 100tx-fd (100Base-TX, full-duplex)
- tp-fd (10Base-T, full-duplex)
- 100tx (100Base-TX, half-duplex)
- tp (10Base-T, half-duplex)
- auto (autonegotiate speed, duplex, and flow control)
|
Mail host
|
The name or IP address of the preferred mail host. The mail host delivers RMC alerts and local Autosupport e-mail.
|
Copyright © 1994-2003, Network Appliance, Inc. All rights
reserved.
Part No. 210-00478
File: info.htm
Last updated: 11/24/03 15:46:40