Gathering data needed for the setup program

Information you need to gather

After you finish entering disk ownership information into the setup program, you are prompted for gFiler system information to set up your gFiler on the network. Gathering information ahead of time makes setup faster for you. This section describes the information that the setup program prompts you for. You can use the Configuration Worksheet in Appendix A to record your values.

Note
If you are configuring a gFiler as part of a cluster, some information types must be unique for each gateway in the cluster and some information types must be identical on both gateways. In the tables in this section, the information type description indicates whether the information type must be unique for each gateway or identical on both gateways.

Setup information

The following information is needed to set up the gFiler or a gFiler cluster. Some information in the following sections applies only if your gateway uses the feature described in that section. For example, if you use virtual network interfaces, Data ONTAP prompts you for that information. The following sections are listed in the order in which the gateway prompts you for information when setup runs.

Host name

The name by which the gateway is known on the network.

If the gateway is licensed for the NFS protocol, the name can be no longer than 32 characters.

If the gateway is licensed for the CIFS protocol, the name can be no longer than 15 characters.

Caution
If you do not enter the name of an administration host, the gateway and its file systems are available to all hosts on the network. Users from any host can gain access to the gateway's root file system and access the configuration files in the /etc directory. This could cause a security breech.

Virtual network interfaces

If you want to create virtual network interfaces (vifs), gather the following information:

Name of each vif
Number of links for each vif
Link names for each link
Note
The virtual network interface information must be identical on both gateways in a cluster.

See the Network Management Guide for details about vifs.

Network interfaces

If your network uses standard Ethernet or Gigabit Ethernet (GbE) interfaces, gather the following information for each interface. See the Network Management Guide for details about any of the following information types.

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, and 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	The subnet mask for the network to which each network interface is attached. Example `255.255.255.0`
Partner IP address	If your gateway 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 Note For vifs, you must specify the interface name rather than the interface IP address.
Media type	The type of interface, one of the following: 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)
Maximum Transmission Unit (MTU) size	If the interface supports jumbo frames, the default frame size defined for a jumbo frame on the gateway 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.

Default gateway

If your network uses routers, gather the following information:

Gateway name
IP address of the router

Administration host

A host computer that is allowed to access the gateway through a Telnet host or through the Remote Shell (rsh) protocol.

Time zone

The time zone in which the gateway resides. See Appendix B, Time Zones for a list of valid time zones.

The time zone must be identical on both gateways in a cluster.

Gateway location

A description of the physical location of the gateway. This information sets the SNMP location information.

Language

The language used for multiprotocol gateways 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 gateways in a cluster.

HTTP directory

If your gateway is licensed for HTTP, determine where you are storing Web files and directories. The default directory is /home/http in the gateway's root volume.

DNS services

If your network uses DNS services, gather the following 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 gateways in a cluster.
DNS servers	The IP addresses of your DNS servers.
	If...	Then...
	If your site uses DNS	Gather the IP address for one or two DNS servers that the gateway should use for host name lookups.
	If your site has a Windows 2000 domain	Gather the IP address of the DNS server that supports your Windows 2000 domain in the Configuration Worksheet. Note When you run the `cifs setup` command (after setup is complete), Data ONTAP creates the Windows 2000 account through kerberos and LDAP.

NIS services

If your network uses NIS services, gather the following information.

Information type	Description
NIS domain name	The name of your NIS domain. The gateway can use an NIS domain to authenticate users and host computers. The NIS domain name must be identical on both gateways in a cluster.
NIS servers	The host names of your preferred NIS servers.
	If...	Then...
	Your site uses NIS	Record the host names of your NIS servers.
	You want NIS to broadcast to find a server	Enter an asterisk (*).

Remote management controller

If your gateway has a remote management controller (RMC) for enhanced Autosupport, gather 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 gateway 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 the 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.

CIFS protocol

If your gateway is licensed for the CIFS protocol, gather the following information. This information is not necessary for the initial gateway setup because that prepares the gateway for network operation. A subsequent CIFS setup is required to configure the gateway for CIFS operations.

Information type	Description
Windows domain	The name of your Windows domain. If your site uses Windows servers, it has one or more Windows domains. Record the name of the Windows domain to which the gateway should belong. Note The Windows domain name value does not need to be identical on both gateways in a cluster. You can have each gateway in a cluster exist in a different domain and 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 gateway 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 gateways in a cluster. You can have each gateway in a cluster exist in a different domain and workgroup from its partner.
Windows 2000 user	The name of the administrative Windows 2000 domain user who has sufficient privilege to add this gateway to the Windows 2000 domain. Note This is only required if you are using a Windows 2000 domain.
Windows 2000 user password	The Windows 2000 domain password to be used for the Windows 2000 user or administrative user. If your domain is a Windows 2000 domain, you must use the password for the user having sufficient privilege to add the gateway to the domain. Note Before you enter the password, be sure to create a secure connection (HTTPS); otherwise, the password is sent to the gateway unencrypted.
Active Directory	The Windows 2000 Active Directory container in which to place gateway 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 2000 domain can pre-create the account. Data ONTAP updates that account.