Module 2: Installation and Configuration

Module 2
Installation and Configuration
NetApp Confidential
MODULE 2: INSTALLATION AND CONFIGURATION
2-1
Clustered Data ONTAP Administration: Installation and Configuration
2013 NetApp, Inc. This material is intended only for training. Reproduction is not authorized.
Module Objectives
After this module, you should be able to:
Configure nodes and install the operating
system
Create a cluster
to the Expand a cluster two nodes
Set the dates, times, and time zones of the
nodes in the cluster
NetApp Confidential
MODULE OBJECTIVES
2-2
Basic Steps for Setting Up a Cluster

1. Connect controllers, disks, and cables.
2. Set up and configure nodes.
3. Install software onto nodes (software is preinstalled on most systems).
4. Initialize disks.
5. Create a cluster.
6. Join additional nodes to the cluster.
7. Create aggregates and volumes.
8. Configure data Vservers.
NetApp Confidential
BASIC STEPS FOR SETTING UP A CLUSTER
2-3
Hardware Setup
Connect:
Controllers to disk shelves
High-availability (HA) interconnect
Controllers to the networks
Any tape devices
Controllers and disk shelves to power
NetApp Confidential
HARDWARE SETUP
2-4
Connect controllers to disk shelves. Verify that shelf IDs are set properly.
If required for your controller type, connect nonvolatile RAM (NVRAM) high-availability (HA) cable
between partners. The connections can be 10-GbE or InfiniBand, depending on your storage controllers.
Connect controllers to the networks.
If present, connect any tape devices. This task can be performed later.
Connect controllers and disk shelves to power.
Communication Connections
Console connection (using ANSI-9600-8N1)
Remote management device connection,
dependent on model
Service Processor (SP)
Remote LAN Module (RLM)
Management network connections

Cluster network connections
Data network connections
NetApp Confidential
COMMUNICATION CONNECTIONS
Each controller should have a console connection, which is required to get to the firmware and to get to the
Boot menu (for the setup, installation, and initialization options, for example). A remote management device
connection, although not required, is helpful in the event that you cannot get to the UI or console. Remote
management enables remote booting, the forcing of core dumps, and other actions.
Each node must have two connections to the dedicated cluster network. Each node should have at least one
data connection, although these data connections are necessary only for client access. Because the nodes are
clustered together, its possible to have a node that participates in the cluster with its storage and other
resources but doesnt field client requests. Typically, however, each node has data connections.
The cluster connections must be on a network that is dedicated to cluster traffic. The data and management
connections must be on a network that is distinct from the cluster network.
2-5
Disk Cabling
node1
node2
node3
node4
NVRAM* Interconnect
FC or SAS (simplified)
For more detailed information on disk cabling, see module 5 in this

course, and also the Data ONTAP Cabling web-based course.
NetApp Confidential
DISK CABLING
A large amount of cabling must be done with a Data ONTAP cluster. Each node has NVRAM
interconnections to its HA partner. Each node has FC or SAS connections to its disk shelves and to those of
its HA partner.
In a multipath high-availability (MPHA) cabling strategy, each storage controller has multiple ways to
connect to a disk. An I/O module failure does not require a controller failover. This method is the most
resilient and preferred method of shelf cabling.
Ethernet cabling for alternate control path (ACP) requires one connection to each controller, connected in a
series through all shelves. First you connect stack to stack. Then you connect between I/O modules from top
to bottom in each stack.
2-6
Network Cabling
1 of 2
Cluster Interconnect
Management
Data
Management
Network
Data Network
NOTE: NetApp recommends switch redundancy for data and

management networks.
NetApp Confidential
NETWORK CABLING: 1 OF 2
For customers with strict security requirements, management ports can be connected to a network that is
separate from the data network. In that case, management ports must have a role of management, and network
failover cannot occur between data and management interfaces.
2-7
Network Cabling
2 of 2
Management
Data
Data and
Management
Network
NOTE: NetApp recommends switch redundancy for data and

management networks.
NetApp Confidential
NETWORK CABLING: 2 OF 2
When you cable the network connections, consider the following:
2-8
Each node is connected to at least two distinct networks: one for management (the UI) and data access
(clients) and one for intracluster communication. NetApp supports two 10-GbE cluster connections to
each node to create redundancy and improve cluster traffic flow.
The cluster can be created without data network connections but not without cluster network connections.
Having more than one data network connection to each node creates redundancy and improves client
traffic flow.
Powering On a Node and Cluster

1.
2.
3.
4.
Power on network switches.

Power on disk shelves.
Power on tape devices (if present).
Power on storage controllers.
NetApp Confidential
POWERING ON A NODE AND CLUSTER
2-9
Firmware
Use LOADER firmware.
Press any key to enter the firmware.
Two boot device images exist: flash0a and
flash0b.
Use printenv to show the firmware
environment variables.
Use setenv to set the firmware environment
variables, for example, setenv AUTOBOOT
true
NetApp Confidential
10
FIRMWARE
1.
2.
3.
4.
Use LOADER firmware.

From the console, early in the booting process, press any key to enter the firmware.
Use version to show the firmware version.
Two boot device images exist (depending on platform): flash0a and flash0b.
CompactFlash
USB flash
5. Use printenv to show the firmware environment variables.

6. Use setenv to set the firmware environment variables; for example, setenv AUTOBOOT true.
To copy flash0a to flash0b, run flash flash0a flash0b. To flash (put) a new image onto the
primary flash, you must first configure the management interface. The auto option of ifconfig can be
used if the management network has a Dynamic Host Configuration Protocol (DHCP) or BOOTP server. If it
doesnt, you must run ifconfig <interface> addr=<ip> mask=<netmask> gw=<gateway>.
After the network is configured, ensure that you can ping the IP address of the TFTP server that contains the
new flash image. To then flash the new image, run
flash tftp://<tftp_server>/<path_to_image> flash0a.
2-10
The Setup Procedure

From the Boot menu:
1. If necessary, run option 7 (Install new
software first).*
2. Run option 4 (Clean configuration and
initialize all disks).*
3. Run the cluster setup wizard.
* Steps 1 and 2 are usually done by NetApp before
hardware arrives at a customer site.
NetApp Confidential
THE SETUP PROCEDURE
2-11
11
The Boot Menu

Please choose one of the following:
1. Normal Boot.
2.
3.
4.
5.
6.
7.
Boot without /etc/rc (no effect in Clustered ONTAP).

Change password.
Clean configuration and initialize all disks.
Maintenance mode boot.
Update flash from backup config.
Install new software first.
8. Reboot node.
Selection (1-8)?
NetApp Confidential
THE BOOT MENU
2-12
12
Installing the Data ONTAP

Operating System on a Node
You need:
Access to an FTP, TFTP, or HTTP server
The software image file on that server
From the boot menu, complete the following:

1. Select option 7.
2. When prompted, enter a URL to a Data ONTAP tgz image.
3. When complete, allow the system to boot.
NetApp Confidential
13
INSTALLING THE DATA ONTAP OPERATING SYSTEM ON A NODE

After you boot the system, if the node stops at the firmware prompt by itself (which happens if the firmware
environment variable AUTOBOOT is set to false), type boot_primary to enable the node to continue to the
boot menu. If AUTOBOOT is set to true, the node goes straight to the boot menu.
If you use TFTP, beware of older TFTP servers that have limited capabilities and might cause installation
failures.
2-13
Initializing a Node
From the Boot menu, select option 4:
Initialization clears the three disks that the system
uses for the first aggregate that it creates.
NOTE: This action requires time, depending on disk size.
Initialization creates one aggregate (for this node) and

a vol0 root volume on the aggregate.
Initialization must be run on both nodes of each HA
pair.
NetApp Confidential
14
INITIALIZING A NODE
Because all disks are initialized parallel to each other, the time that is required to initialize the disks is based
on the size of the largest disk that is attached to the node, not on the sum capacity of the disks. After the disks
are initialized, the nodes first aggregate and its vol0 volume are automatically created.
2-14
The Cluster Setup Wizard

1 of 3
From the Boot menu of an initialized

controller:
1. Boot normally.
2. Log in as admin with no password.
3. Follow the prompts.
You can also run cluster setup from the

CLI.
NetApp Confidential
15
THE CLUSTER SETUP WIZARD: 1 OF 3

An initialized storage controller automatically boots to the cluster setup wizard. You can type exit to stop
the wizard and stay at the command prompt. The node is not yet part of a cluster. You can restart the wizard
from the CLI by typing cluster setup.
2-15

2 of 3
The first node creates the cluster.
You need the:
Cluster name
Cluster network ports and MTU size (usually best to use
default MTU)
Cluster base license key
Cluster management interface port, IP address, network
mask, and default gateway
Node management interface port, IP address, network
mask, and default gateway
DNS domain name
IP addresses of the DNS server
NetApp Confidential
16

To complete the cluster setup wizard, you need the following information for the first node in the cluster:
2-16
The cluster name. The wizard automatically names the node clustername-0x, where x is the order in
which the node joins the cluster. The node that creates the cluster is 01, the next node to join the cluster is
02, and so on.
Cluster network ports. On a private, nonroutable cluster network, the wizard automatically assigns cluster
IP addresses.
The cluster base license key. Additional license keys can be added here.
The cluster management interface port, IP address, network mask, default gateway, and home port
The node management interface port, IP address, network mask, default gateway, and home port
DNS domain name
IP addresses of the DNS server

3 of 3
Subsequent nodes join the cluster.
You need the:
Cluster network ports and MTU size
Node management interface port, IP address,
network mask, and default gateway
For more detailed information on cluster setup and configuration,

enroll in the Clustered Data ONTAP Installation Workshop.
NetApp Confidential
17

To complete the cluster setup wizard, you need the following information for subsequent nodes:
2-17
Cluster network ports. On a private, nonroutable cluster network, the wizard automatically assigns cluster
IP addresses.
The node management interface port, IP address, network mask, default gateway, and home port
The Normal Boot Sequence

1. The firmware loads the kernel from the boot device.
2. The kernel mounts the / root image from rootfs.img on
the boot device.
3. Init is loaded, and startup scripts run.
4. NVRAM kernel modules are loaded.
5. The /var partition on NVRAM is created and mounted
(restored from boot device if a backup copy exists).
6. The management gateway daemon (mgwd) is started.
7. The data module, the network module, and other
components are loaded.
8. The vol0 root volume is mounted from the local data

module.
9. The CLI is ready for use.
NetApp Confidential
THE NORMAL BOOT SEQUENCE
2-18
18
System Setup Tool

The System Setup tool and simple instructions are included with every FAS2200 shipment.
NetApp Confidential
19
SYSTEM SETUP TOOL

System Setup is a new utility tool that lets partners and end-user customers set up their NetApp FAS2220 or
FAS2240 system quickly and easily. System Setup takes the user through a series of simple steps to set up
and provision their FAS2200 series system. The System Setup tool is designed to improve the initial overall
customer experience.
2-19
System Setup Benefits

Set up your FAS2200 three times faster.
You dont need to be a storage expert.
Defaults take the guesswork out of the setup
process.
You get NetApp best practices for optimal
performance.
Deduplication, flexible volumes, auto grow,
and storage provisioning
NetApp Confidential
20
SYSTEM SETUP BENEFITS

System Setup is big news for NetApp partners and customers alike. With System Setup, installation and
configuration of your FAS2200 series is completed three times faster than previously. You dont need to be a
storage expert either. Numerous IT generalists used System Setup and were able to set up and configure a
FAS2200 series in minutes.
For NetApp partners, this means more options. They can choose to continue to sell their own professional
services, knowing that System Setup will make installation much easier. Alternatively, NetApp partners can
choose not to sell installation services and allow their customers to do their own installation and setup.
System Setup is designed for a positive out-of-the-box experience. Default settings mean that the guesswork
is taken out of the setup process. These default settings also mean that the customer benefits by having
NetApp best practices for optimal performance of their new FAS2200 system. System Setup helps customers
set up efficiency technologies such as deduplication, flexible volumes, auto grow, and storage provisioning.
2-20
System Setup Installation Requirements

System Setup:
Runs on the following systems:
Windows XP
Windows 7
Windows Server 2008 R2 x64
Requires .NET Framework 3.5 SP1

Can configure FAS2200 systems running:
Clustered Data ONTAP 8.2

Data ONTAP 8.1 7-Mode
Data ONTAP 8.1.1 7-Mode
Data ONTAP 8.1.2 7-Mode
NetApp Confidential
21
SYSTEM SETUP INSTALLATION REQUIREMENTS

Note that a few installation requirements apply to System Setup.
The utility is only supported on Windows platforms running Windows XP, Windows 7, or Windows Server
2008 R2 x64. System Setup also requires the .NET Framework, 3.5 SP1.
The systems to be configured should be running Data ONTAP 8.1, 8.1.1, or 8.1.2 in 7-Mode. System Setup
will configure the 10-GbE mezzanine card in FAS2220 systems with Data ONTAP 8.1.2.
2-21
More Information About System Setup

support.netapp.com
Download System Setup
Access documentation
fieldportal.netapp.com
Slides
Sales FAQs
NetApp Confidential
22
MORE INFORMATION ABOUT SYSTEM SETUP

Download the System Setup utility tool and access documentation on the NetApp Support site at
support.netapp.com
NetApp employees and partners can also access sales tools, including slides and an FAQ, on the NetApp
Field Portal at fieldportal.netapp.com.
2-22
Network Time Protocol

Manually set the date, time, and time zone with
system date modify.
Kerberos is time-sensitive and typically requires the
Network Time Protocol (NTP).
NTP is disabled by default.
NTP enablement and disablement are cluster-wide.
The commands for verifying and monitoring NTP are:

system services ntp config show
system services ntp server show
NetApp Confidential
NETWORK TIME PROTOCOL
2-23
23
7-Mode Transition Tool
Transition
Data ONTAP 7-Mode
Clustered Data ONTAP
NetApp Confidential
24
7-MODE TRANSITION TOOL

You can use the new Data ONTAP 7-Mode Transition Tool to migrate NAS workloads from Data ONTAP
operating in 7-Mode to clustered Data ONTAP 8.2. The transition tool is a CLI wizard and GUI that
simplifies and expedites complex transition tasks. The tool collects volume and IP address information from
the Data ONTAP 7-Mode environment and verifies the configuration. The tool then applies the configuration
to the Vserver in the cluster. The tool uses SnapMirror software to seed the cluster with FlexVol volumes, and
regular replication to keep the cluster current until the workload is cut over to the cluster. After all data
configuration information is staged on the target cluster, the tool initiates and manages a cut-over event to
transfer the Data ONTAP 7-Mode workload to the cluster.
Note that the transition tool supports source controllers that run Data ONTAP 7.3.3, Data ONTAP 7.3.7, Data
ONTAP 8.0.3 7-Mode, and Data ONTAP 8.1 7-Mode. Use third-party tools to move LUNs from a Data
ONTAP 7-Mode controller to the cluster.
To learn more about transitioning from Data ONTAP operating in 7-Mode to a cluster, see the NetApp
Transition Fundamentals web-based course.
2-24
Module Summary
Now that you have completed this module, you
should be able to:
Configure nodes and install the operating
system
Create a cluster
to the Expand a cluster two nodes
Set the dates, times, and time zones of the
nodes in the cluster
NetApp Confidential
MODULE SUMMARY
2-25
25
Exercise
Module 2:
Installation and Configuration
Time Estimate: 30 minutes
NetApp Confidential
EXERCISE
Please refer to your exercise guide.
2-26
26

Module 2: Installation and Configuration

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Module 2: Installation and Configuration

Enviado por

Direitos autorais:

Formatos disponíveis

Module 2

Installation and Configuration

MODULE 2: INSTALLATION AND CONFIGURATION

Clustered Data ONTAP Administration: Installation and Configuration

Clustered Data ONTAP Administration: Installation and Configuration

Basic Steps for Setting Up a Cluster

BASIC STEPS FOR SETTING UP A CLUSTER

Clustered Data ONTAP Administration: Installation and Configuration

Clustered Data ONTAP Administration: Installation and Configuration

Management network connections

Clustered Data ONTAP Administration: Installation and Configuration

For more detailed information on disk cabling, see module 5 in this

Clustered Data ONTAP Administration: Installation and Configuration

NOTE: NetApp recommends switch redundancy for data and

Clustered Data ONTAP Administration: Installation and Configuration

NOTE: NetApp recommends switch redundancy for data and

Clustered Data ONTAP Administration: Installation and Configuration

Powering On a Node and Cluster

Power on network switches.

POWERING ON A NODE AND CLUSTER

Clustered Data ONTAP Administration: Installation and Configuration

Use LOADER firmware.

5. Use printenv to show the firmware environment variables.

Clustered Data ONTAP Administration: Installation and Configuration

The Setup Procedure

THE SETUP PROCEDURE

Clustered Data ONTAP Administration: Installation and Configuration

The Boot Menu

Boot without /etc/rc (no effect in Clustered ONTAP).

THE BOOT MENU

Clustered Data ONTAP Administration: Installation and Configuration

Installing the Data ONTAP

From the boot menu, complete the following:

INSTALLING THE DATA ONTAP OPERATING SYSTEM ON A NODE

Clustered Data ONTAP Administration: Installation and Configuration

Initialization creates one aggregate (for this node) and

Clustered Data ONTAP Administration: Installation and Configuration

The Cluster Setup Wizard

From the Boot menu of an initialized

You can also run cluster setup from the

THE CLUSTER SETUP WIZARD: 1 OF 3

Clustered Data ONTAP Administration: Installation and Configuration

The Cluster Setup Wizard

THE CLUSTER SETUP WIZARD: 2 OF 3

Clustered Data ONTAP Administration: Installation and Configuration

The Cluster Setup Wizard

For more detailed information on cluster setup and configuration,

THE CLUSTER SETUP WIZARD: 3 OF 3

Clustered Data ONTAP Administration: Installation and Configuration

The Normal Boot Sequence

8. The vol0 root volume is mounted from the local data

THE NORMAL BOOT SEQUENCE

Clustered Data ONTAP Administration: Installation and Configuration

System Setup Tool

SYSTEM SETUP TOOL

Clustered Data ONTAP Administration: Installation and Configuration

System Setup Benefits

SYSTEM SETUP BENEFITS

Clustered Data ONTAP Administration: Installation and Configuration

System Setup Installation Requirements

Requires .NET Framework 3.5 SP1

Clustered Data ONTAP 8.2

SYSTEM SETUP INSTALLATION REQUIREMENTS