M03 BasicAdmin FINAL

7/29/2019 M03 BasicAdmin FINAL

1/39

BasicAdministration

Module 3

Data ONTAP 7.3 Fundamentals


2/39

2008 NetApp. All rights reserved. 2

Module Objectives

By the end of this module, you should be able to:

Connect remotely to the CLI of a FAS system

using the console and a remote host

Access FilerView to manage a storage system

Execute commands using the console, a

remote host, and FilerView

Demonstrate how to use commands to analyze

a FAS system Configure and manage the AutoSupport

service for a FAS system


3/39


Graphical Interfaces


4/39


Administration Options

A storage system may be managed from a:

GUI

CLI


5/39


Graphical Interfaces

A storage system can be managed through

multiple graphical interfaces:

FilerView administration tool

Operations Manager (formerly DataFabric

Manager)

Microsoft Windows interfaces such as

Computer Management for certain CIFS

functionality


6/39


FilerView Administration Tool

http:///na_admin


7/39 2008 NetApp. All rights reserved. 7

Operations Manager

Operations Manager is a Web application that discovers,

monitors, and manages NetApp storage from a

management console for maximum availability, reduced

TCO, and business policy compliance.



Alternative GUIs

Some operating systems have other interfaces, such as

Windows Computer Management, that interact with the

functionality of the storage system.



Command LineInterface



Command Line Interface

The CLI is a powerful tool to administer storage

systems and can be accessed through:

Console

Telnet

Remote LAN Module (RLM)

FilerView CLI

Remote Shell (RSH)

Secure Shell (SSH)system> Wed Apr 7 20:53:01 ...logged in from console

system>



Telnet to the Console

Login>Password>



Remote LAN Module

The RLM, which is available in some hardware

configurations, provides:

Remote access to your storage system

regardless of the system state

Continuous power and secure access

RLM Port



FilerView CLI



CLI Session Limitations

A storage system allows only one session and

one user at a time. Attempts to create additional

sessions will generate an error.

To create two separate sessions to use at the

same time:

telnet.distinct.enable

NOTE: If separate sessions are notcreated,

administrators must share the same session.

Too many users logged in! Please try again later. Connectionclosed.



Remote Shell

RSH allows you to issue console commands without a

console session.

To use RSH, enable it with the following:

options rsh.enable on

If there is a console password, you must modify/etc/hosts.equiv to allow access

Multiple RSH commands can be issued using the

following syntax:

UNIX

rsh [; ]

Windows

rsh l



Secure Shell

SSH is a network protocol that allows data

exchange over a secure channel. SSH also:

Allows for secure administrative access to the

storage system

Requires no license Can be implemented using the secureadmin

command or by using FilerView

For a complete description of the SSH feature,

see the System Administration Guide.



Common Commands



Basic Administration Commandssystem> ?? halt nfs snapvaultaggr help nfsstat snmp

backup hostname nis softwarecf httpstat options sourcecifs ifconfig orouted storageconfig ifstat partner sysconfigdafs igroup passwd sysstatdate ipsec ping timezonedf ipspace priv traceroute

disk iscsi qtree upsdisk_fw_update iswt quota uptimedns license rdate useradmindownload lock reboot versiondump logger restore vfilerecho logout rmc vifems lun route vlanenvironment man routed vol

exportfs maxfiles rsm vscanfcp mt savecore wccfcstat nbtstat secureadmin ypcatfile ndmpcopy setup ypgroupfilestats ndmpd shelfchk ypmatchfpolicy netdiag snap ypwhichftp netstat snapmirror

system>



system> priv set advancedWarning: These advanced commands are potentially dangerous; use

them only when directed to do so by Network Appliance

personnel.df led_on quota sysstatdisk led_on_all rdate test_lcddisk led_on_off rdfile timezonedisk_fw_update led_test reboot toedisk_list led_test_one registry traceroutedisk_stat license remote upsdns lmem_stat restore uptime

download lock result useradmindump log revert_to versionecho logger rm vfilerems logout rmc vifenviron ls rmt vlanenvironment lun rod volexit man route vscanexportfs maxfiles routed wafl

fcadmin mbstat rsm wafl_suspfcp mem_scrub_stats rtag wccfcstat mt savecore wrfilefile mv scsi ypcatfilestats nbtstat secureadmin ypgroupfpolicy ndmpcopy setup ypmatchftp ndmpd sh ypwhich

getXXbyYY

priv set admin

Advanced Privilege Commands



Basic System Configuration

The following are basic system configuration commands:

System configuration

sysconfig

sysconfig -v

RAID configuration

sysconfig r

vol status -r

Disk configuration

sysconfig -d

Check your configuration

sysconfig -c



Configuring YourSystem


22/39


Configuring Your System

To change the configuration of a storage system, use

one of the following methods:

CLI

options

vol options

Configuration files

/etc/hosts

/etc/rc

/etc/hosts.equiv

/etc/dgateways

FilerView

AutoSupport to report configurations (discussed later)


23/39


CLI Commands

System options:options [option name] [value]

Example: options rsh.enable on

NOTE: If no value is entered, the current value is displayed.

Volume options:vol options volname [option name] [value]

Aggregate options:aggr options aggrname [option name] [value]


24/39


Registry Files

Registry files contain many persistent

configurations.IMPORTANT: The registry should not be edited directly.

File Usage

/etc/registry Current registry

/etc/registry.lastgood Copy of registry after last

successful boot

/etc/registry.bck First-level backup

/etc/registry.default Default registry


25/39


Editing Configuration Files

The following are important configuration files:

/etc/rc

/etc/hosts

/etc/hosts.equiv

There are three ways to edit a configuration file:

Access the /etc directory and use local

editing tools

Use commands on the console Use FilerView to edit configuration files


26/39


Editing Configurations from Host

#Auto-generated by setup Sun Mar 29 15:05:20 GMT1970127.0.0.1 localhost10.254.134.43 DEV-FAS250 DEV-FAS250-e0a# 0.0.0.0 DEV-FAS250-e0b


27/39


Console Editing

To edit files on the console:

1. Make a backup copy of the file.

2. Read the file using rdfile.

3. Write the file using wrfile.

IMPORTANT: When the wrfile command is issued, the original

file is deleted. Therefore, it is important to first use the rdfile

command. To append to a file withoutdeleting it, use wrfile a.


28/39


System Configuration Using FilerView

Configuration settings are accessed through the left

navigation pane.


29/39


AutoSupport


30/39


AutoSupport Mail Host

Email Server


31/39


AutoSupport

The autosupport daemon monitors the storage

system's operations and sends automatic

messages to technical support. Technical

support contacts you with any reported issues.

AutoSupport messages are generated: When events occur on the storage system that

require corrective action

When you initiate a test message

When the system reboots

Once a week (usually after 12 a.m. on

Sundays)


32/39


AutoSupport E-Mail Events

Events E-Mail Subject Line

Low NVRAM battery BATTERY_LOW

Disk failure DISK_FAIL!!!

Disk scrub detected checksum errors DISK_SCRUB CHECKSUM ERROR

Shutdown occurred because of overheating OVER_TEMPERATURE_SHUTDOWN!!!

Partial RPS failure occurred REBOOT

Disk shelf error occurred SHELF_FAULT

Spare disk failure occurred SPARE DISK FAILED

Weekly backup of /etc/messages occurred WEEKLY_LOG

Successful cluster takeover of partner CLUSTER TAKEOVER COMPLETE

Unsuccessful cluster takeover CLUSTER TAKEOVER FAILED

Cluster takeover of virtual filer REBOOT (CLUSTER TAKEOVER)

Cluster giveback occurred CLUSTER GIVEBACK COMPLETE


33/39


AutoSupport E-mail Contents

The options autosupport.content

command specifies how much to send

options autosupport.content

[Minimal|Complete]

The default is Complete Complete AutoSupports are stored in:

/etc/log/autosupport


34/39


AutoSupport Configuration Options

AutoSupport commands:

options autosupport.support.enable

[on|off]

options autosupport.mailhost

[host1,,host5]

options autosupport.to

[address1,,address5]

options autosupport.from

options autosupport.content

options autosupport.noteto

options autosupport.doit [message]

options autosupport.enable [on|off]


35/39


Testing AutoSupport

To send an AutoSupport test message, complete

the following steps:

1. Configure AutoSupport using the options

command.

2. Run the following command on the storagesystem console:options autosupport.doit testing

The message System Notification Sent

appears on the console.


36/39


Module Summary

In this module, you should have learned:

Connect remotely to the CLI of a FAS system

using the console and a remote host

Access FilerView to manage a storage system

Execute commands using the console, aremote host, and FilerView

Demonstrate how to use commands to analyze

a FAS system Configure and manage the AutoSupport

service for a FAS system


37/39

Exercise

Module 3: Basic Administration

Estimated Time: 60 minutes


38/39

Answers

Module 3: Basic Administration


39/39

Check Your Understanding

Name three ways to access a storage systems CLI.

Console, Telnet, RLM, RSH, SecureShare, and the FilerView CLI What is the URL to access FilerView?

http://[system name or IP]/na_admin

How can you view the system configuration for a FAS storagesystem? sysconfig [-v]

FilerView How can you configure a FAS storage system from a remote

adminhost? For UNIX, set up NFS and a mount an export of the root directory

For Windows, set up CIFS and access the \\filer\C$ share

When are AutoSupport messages generated?

Messages are generated when: Events occur on the storage system that require corrective action

The storage system reboots

You initiate a test message

Once a week, usually after 12 a.m. on Sundays

M03 BasicAdmin FINAL

Documents

Transcript of M03 BasicAdmin FINAL