Vous êtes sur la page 1sur 84

OneFS

OneFS 6.0 Command-Line Reference Guide

July 2010

Isilon Systems respects the intellectual property of others.

2010 Isilon Systems, Inc. All rights reserved.

Isilon, Isilon Systems, OneFS, and SyncIQ are registered trademarks of Isilon Systems, Inc., Isilon IQ, SmartConnect,
SnapshotIQ, TrueScale, Autobalance, FlexProtect, SmartCache, SmartPools, InsightIQ, "HOW BREAKTHROUGHS BEGIN."
and the Isilon logo are trademarks of Isilon. Other product and company names mentioned are the trademarks of their respective
owners.
U.S. Patent Numbers 7,146,524; 7,346,720; 7,386,675; 7,509,448; 7,509,524; 7,551,572; 7,590,652; 7,593,938. China Patent
Number ZL 02816665.5. Other patents pending.
Due to ongoing product development, innovation, and revision, the information contained here is subject to change without
notice. Isilon will publish updates and revisions to this document as needed. The systems documented herein are provided
under End User License Agreements. Please refer to the Agreements for details governing the use of Isilon IQ systems.

Contents
Chapter 1: Introduction...............................................................................................................7
Document Conventions.......................................................................................................7

Chapter 2: isi batterystatus.........................................................................................................9

Chapter 3: isi devices................................................................................................................11

Chapter 4: isi iscsi.....................................................................................................................15


isi iscsi list.........................................................................................................................15
isi iscsi isns.......................................................................................................................16
isi iscsi isns status..................................................................................................16
isi iscsi isns discover..............................................................................................16
isi iscsi isns enable.................................................................................................17
isi iscsi isns disable................................................................................................17

Chapter 5: isi job........................................................................................................................19


isi job list............................................................................................................................19
isi job status......................................................................................................................20
isi job history.....................................................................................................................21
isi job config......................................................................................................................23
isi job start.........................................................................................................................23
isi job pause......................................................................................................................24
isi job update.....................................................................................................................24
isi job resume....................................................................................................................25
isi job cancel......................................................................................................................25
isi job policy.......................................................................................................................26
isi job policy list.......................................................................................................26
isi job policy create.................................................................................................27
isi job policy set......................................................................................................28
isi job policy modify................................................................................................28
isi job policy delete.................................................................................................29
isi job schedule..................................................................................................................30
isi job schedule list.................................................................................................30
isi job schedule set.................................................................................................30
isi job schedule delete............................................................................................31

Chapter 6: isi lun........................................................................................................................33

isi lun create......................................................................................................................33


isi lun delete......................................................................................................................34
isi lun modify.....................................................................................................................35
isi lun list............................................................................................................................36
isi lun clone.......................................................................................................................36
isi lun move.......................................................................................................................38
isi lun import......................................................................................................................38
isi lun online......................................................................................................................39
isi lun offline......................................................................................................................39

Chapter 7: isi ndmp....................................................................................................................41


isi ndmp settings...............................................................................................................41
isi ndmp settings list...............................................................................................41
isi ndmp settings set...............................................................................................42
isi ndmp user.....................................................................................................................43
isi ndmp user create...............................................................................................43
isi ndmp user modify..............................................................................................43
isi ndmp user delete...............................................................................................44
isi ndmp user list.....................................................................................................44
isi ndmp list.......................................................................................................................45
isi ndmp kill........................................................................................................................46
isi ndmp probe...................................................................................................................46

Chapter 8: isi networks..............................................................................................................49


isi networks create............................................................................................................50
isi networks create subnet......................................................................................50
isi networks create pool..........................................................................................51
isi networks create rule...........................................................................................52
isi networks modify............................................................................................................53
isi networks modify subnet.....................................................................................53
isi networks modify pool.........................................................................................54
isi networks modify rule..........................................................................................56
isi networks list..................................................................................................................57
isi networks list subnets..........................................................................................57
isi networks list pools..............................................................................................58
isi networks list rules..............................................................................................59
isi networks list interfaces.......................................................................................60
isi networks delete.............................................................................................................61
isi networks delete subnet......................................................................................61
isi networks delete pool..........................................................................................62
isi networks delete rule...........................................................................................63

Chapter 9: isi pkg.......................................................................................................................65

isi pkg create.....................................................................................................................65


isi pkg delete.....................................................................................................................65
isi pkg install......................................................................................................................65
isi pkg info.........................................................................................................................66

Chapter 10: isi services.............................................................................................................69

Chapter 11: isi smartpools........................................................................................................71


isi smartpools process......................................................................................................71

Chapter 12: isi status.................................................................................................................73

Chapter 13: isi target.................................................................................................................77


isi target create..................................................................................................................77
isi target delete..................................................................................................................78
isi target modify.................................................................................................................79
isi target list.......................................................................................................................81

Chapter 14: isi update................................................................................................................83

1
Introduction

This guide describes the isi commands that you can run in order to configure, monitor, and manage an Isilon IQ clustered
storage system and the individual nodes in a cluster.
Note: This initial version of the guide documents a subset of the isi commands.
The OneFS command-line interface extends the standard UNIX command set to include additional commands that enable you
to manage an Isilon cluster outside of the web administration interface or LCD panel. You can access the command-line
interface by opening a secure shell (SSH) connection on any node in the cluster.
Each isi command consists of a command name, any command options, and any sub-commands, in that order. This guide
lists the commands in alphabetical order and includes the following information for each command:

Description
Syntax
Supported options, if applicable
Supported sub-commands, if applicable
Examples

Document Conventions
This guide includes a syntax diagram for each command, using the following conventions.
Symbol

Description
Text that is not enclosed in square brackets [ ], angle brackets < >, or braces { } must be typed as shown.

[]

Square brackets indicate an optional element.

<>

Angle brackets indicate a placeholder for a value you must supply.

{}

Braces indicate a group of mutually exclusive elements that are delimited by vertical-bar (|) symbols.

A vertical bar indicates you can select only one of the options shown.

-- or -

A single or double hyphen indicates an option. Options define the specific action of a command or
modify the operation of a command. Many commands support multiple options.

2
isi batterystatus

Displays the current state of NVRAM batteries and the charging system on node hardware that supports this feature.
Syntax
isi batterystatus
Command Output
This command returns the current status for each NVRAM battery and a numerical code that indicates the specific battery
state. Refer to the following table for specific battery status codes.
Code

Explanation

Unknown

Unable to communicate with battery charger

Charger unable to operate

Battery pack disconnected

Charge paused due to temperature error

Charge paused due to temperature error

Good, charged with high temperature

Battery unable to accept charge

Battery charging normally

Good, charging

10

Good, charging

11

Battery charge circuit shutdown

12

Good, charging

13

Battery tray removed

14

Battery failed

15

Battery overcharged

isi batterystatus
Options
This command does not support any options.
Examples
To determine the NVRAM battery status on a node, run the following command:
isi batterystatus
The system displays the current status for each NVRAM battery and a numerical code indicating the specific battery state.

In the following sample output, both batteries are good and charging (status=10):
battery 1 : Good (10)
battery 2 : Good (10)

In the following sample output, battery 1 is good and charging (status=9) but the tray for battery 2 is not connected
(status=13):
battery 1 : Good (9)
battery 2 : Battery tray removed (13)
Note: If you run this command on an unsupported platform, the system displays the following output:
Battery status not supported on this platform

10

2010 Isilon Systems, Inc.

3
isi devices

Displays information about the devices in a cluster or changes device states. This command is required when hot-swapping a
hard drive in a node.
Syntax
isi devices --device=[<LNN>][:<Drive>] [--action=status] [--grid]
isi devices --device=<LNN> --action=add [--timeout=<TimeLimit>]
isi devices --device=[<LNN>][:<Drive>] [--action=<Action>]
Options
--device=[<LNN>][:<Drive>], -d [<LNN>][:<Drive>]
Required. Specifies the node or drive on which to perform the action, where <LNN> is the logical
node number and <Drive> is either the logical drive number (lnum) or bay number. For example, a
cluster named "isilon" would typically have nodes named "isilon-1", "isilon-2", "isilon-3", and so on.
The "1", "2", and "3" identifiers are the logical node numbers.
If <LNN> is not specified, the current node is used by default. If <Drive> is not specified, the action
is applied to the entire node.
<Drive> specifies a logical drive number or bay number. The <Drive> is indicated by one of the
following entries:

lnum <Number> specifies a logical drive number.


[bay]<Number> specifies a bay number.

--action=<Action>, -a <Action>
If you do not specify an action, the system performs the status action by default. The following
table describes the valid actions that are available with the --action option.
Action

Scope

Description

status

Node or
drive

Default action. Displays the status of the specified device.

smartfail

Node or
drive

Runs the smartfail process on the specified device.

stopfail

Node or
drive

Runs the stopfail process on the specified device. Before you can
use this action, you must run the smartfail action on the device.
The stopfail action is not valid for nodes with a status of OK
or drives with a status of HEALTHY.

11

isi devices

Action

Scope

add

Node or
drive

Description
The add action accepts either a specified drive or an unconfigured
node's serial number as the device argument. (Serial numbers vary
in format. You can locate the node's serial number on the node
label.) If the device argument is a drive, running the add action
scans the drive, performs any required preparation, and then adds
the drive to OneFS, effectively reformatting the drive with the
OneFS data structures. For more information, see the description
of the --device option.
If the device argument is an unconfigured node's serial number, the
add action initiates the process of adding the specified node to the
cluster. Depending on the state of the unconfigured node, the add
process may reimage, patch, or reboot the unconfigured node before
adding it to the cluster.

discover

Node or
drive

The discover action takes no device argument. If you specify


the discover action, the system displays information about any
unconfigured nodes, including each node's serial number, hardware
type, OneFS version, and health status.
You can view and monitor the progress of the node being added by
specifying the discover action, which displays the failure status
and any relevant error messages. If the system returns an error during
the node-add process, the unconfigured node's status message
includes a description of the error.

confirm

Node or
drive

format

Drive

To acknowledge that an error has occurred during the add process,


and to make the unconfigured node available for further add
attempts, you can perform the confirm action, which requires a
node's serial number as the device argument.
The format action accepts only a logical drive number as the
device argument and initiates a OneFS format of the specified drive.
When the format is complete, the drive is automatically initialized
and available for use by OneFS.

! Caution: You can specify the format action only on a drive


that has been smartfailed or otherwise removed from the
system. If OneFS smartfails a faulty drive, do not reformat
that drive or force it back into service. The format action is
intended for use by an Isilon Technical Support representative
or in conjunction with instruction from a representative.

You can specify the discover, add, and confirm actions if you want access to new and
unconfigured nodes that are connected to the same internal switch or switches as the cluster.
Note: Depending on which action you specify, the system displays the status of each
drive in a node using one of the following terms:

12

EMPTY: Drive is empty.


NEW: Drive is new.
PREPARING: Drive is preparing for use.
HEALTHY: Drive is healthy.

2010 Isilon Systems, Inc.

isi devices

SMARTFAIL: Smartfail/restripe in progress.


REPLACE: Drive is not in use and is ready to be replaced.

--grid, -g
Displays the drives and bays in a grid format that corresponds to their physical layout in the chassis.
This option is used only with the status action.
--timeout=<TimeLimit>, -t <TimeLimit>
Sets a time limit that controls how much time the cluster will spend gathering version information
from all member nodes. This is valid only for the node add action. By default, no timeout limit is
configured.
--help, -h
Displays a list of supported options for this command.
Examples

To view the status of the drives on the third node in a cluster, run the following command:
isi devices --action=status --device=3
The system displays a list of devices and their status within the specified node, similar to the following example output:
Node 3, [ OK ]
Bay 1
Lnum 3

[HEALTHY]

SN:KRVN67ZBGLU5HF

/example/ex1

Bay 2

Lnum 2

[HEALTHY]

SN:KRVN67ZBGTS0AF

/example/ex2

Bay 3

Lnum 1

[HEALTHY]

SN:KRVN67ZBG236KF

/example/ex3

Bay 4

Lnum 0

[HEALTHY]

SN:KRVN67ZBGTDT7H

/example/ex4

To view the status of the drives in a cluster in grid format that represents the physical layout of the bays in the chassis, run
the following command:
isi devices --action=status --grid
The system displays status information for the drives organized by bay, similar to the following example output:
Node 1, [ OK ]
Bay 1, Lnum 3
[HEALTHY]
SN:KRVN0AZBGRDS4J
/example/ex1

Bay 2, Lnum 2
[HEALTHY]
SN:KRVN0AZBGRDVJJ
/example/ex2

Bay 3, Lnum 1
[HEALTHY]
SN:KRVN0AZBGRDZHJ
/example/ex3

Bay 4, Lnum 0
[HEALTHY]
SN:KRVN0AZBGR1Z2J
/example/ex4

To view the status of the drive in the second bay of the third node, run the following command:
isi devices --action=status --device=3:2
The system displays the status of the node and the drive, similar to the following example output:
Node 3, [ OK ]
Details for Drive in Bay 2, Node 3
Lnum: 2
Status: [HEALTHY]
Bay 2/ex2
is HDS725050KLA360 FW:K2AOAD1A SN:KRVN67ZBGTS0AF, 976773168 blks
SMART data (Bay 2/da2 ) -Reallocation Count: 64/64
Probational Count: 64/64
Raw Read Error Rate: 64/64
HDD Temperature: 9d/9d

2010 Isilon Systems, Inc.

vs
vs
vs
vs

05
00
10
00

(raw
(raw
(raw
(raw

0000)
0000)
0000)
0023)

[flags
[flags
[flags
[flags

0033]
0022]
000b]
0002]

13

isi devices

Spin Retries: 64/64 vs 3c


CRC Errors: c8/fd vs 00
Throughput Performance: 64/64 vs 32
Spinup Time: 6b/6b vs 18
Spinup Count: 64/64 vs 00
Seek Error Rate: 64/64 vs 43
Seek Performance: 64/64 vs 14
Power-on Time: 62/62 vs 00
Power Cycles: 64/64 vs 00
Emergency Retract Cycles: 64/64 vs 32
Load/Unload Cycles: 64/64 vs 32
Offline Realloc Events: 64/64 vs 00
Scan Uncorrectable Errs: 64/64 vs 00
SMART status is threshold NOT exceeded

(raw
(raw
(raw
(raw
(raw
(raw
(raw
(raw
(raw
(raw
(raw
(raw
(raw

0000)
0000)
0000)
0287)
0040)
0000)
0000)
4a9a)
0040)
032f)
032f)
0000)
0000)

[flags
[flags
[flags
[flags
[flags
[flags
[flags
[flags
[flags
[flags
[flags
[flags
[flags

0013]
000a]
0005]
0007]
0012]
000b]
0005]
0012]
0032]
0032]
0012]
0032]
0008]

SMART errlog (Bay 2/da2 ) -error index 00


historic error count 0000
reserved:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00
version 01 cksum ff(ok)

14

2010 Isilon Systems, Inc.

4
isi iscsi

Displays information about current iSCSI sessions or configures the Internet Storage Name Service (iSNS). This command
requires a sub-command.

isi iscsi list


Displays information about current iSCSI sessions.
Syntax
isi iscsi list [--target=<TargetName>] [--verbose]
Options
If you run the command without options, the system displays a list of all current iSCSI sessions.
--target=<TargetName>, -t=<TargetName>
Displays session information only for the specified target.
--verbose, -v
Displays detailed session information.
--help, -h
Displays a list of supported options with brief descriptions.
Examples
To view detailed information about each current iSCSI session, run the following command:
isi iscsi list --verbose

15

isi iscsi

isi iscsi isns


Configures Internet Storage Name Service (iSNS) settings. iSNS is used for target discovery by iSCSI initiators. This
command requires a sub-command.

isi iscsi isns status


Displays the current status and configured IP address of the iSNS server.
Syntax
isi iscsi isns status
Command Output
This command returns the following information:

Status: Displays the status (enabled or disabled) of the iSNS server.


Server: Displays the IP address of the iSNS server.

Options
There are no options for this command.
Example
To view the connection status and configured IP address for the iSNS server, run the following command:
isi iscsi isns status

isi iscsi isns discover


Displays a list of iSNS-provided initiators that can connect to targets on the system.
Note: To use this command, the iSNS client service must be configured and enabled. For more information, see
isi iscsi isns enable on page 17.
Syntax
isi iscsi isns discover [--target=<TargetName>]
Options
If you run this command without options, the system displays the initiators that are available to each target on the system.
--target=<TargetName>, -t=<TargetName>
Displays initiators for the specified target.
--help, -h
Displays a list of supported options for this command.
Examples
To view the initiators that are available for all targets, run the following command:
isi iscsi isns discover
To view the initiators that are available for a target named linux1, run the following command:
isi iscsi isns discover --target=linux1

16

2010 Isilon Systems, Inc.

isi iscsi

isi iscsi isns enable


Configures or starts the iSNS client service.
Syntax
isi iscsi isns enable [--server=<IPaddress>] [--port={<PortNumber>|default}]
Options
You must specify the --server option the first time you run this command. The iSNS service cannot be enabled unless
it is configured with the IP address of a valid iSNS server.
--server=<IPaddress>, -s=<IPaddress>
Specifies the IP address of the iSNS server.
--port={<PortNumber>|default}, -p={<PortNumber>|default}
Specifies the server port number. Type a port number or type default to use the default port 3205.
--help, -h
Displays a list of supported options for this command.
Examples

To configure an iSNS server with the IP address 11.22.3.45, run the following command:
isi iscsi isns enable --server=11.22.3.45
You can confirm that the iSNS service is configured and enabled by running the isi iscsi isns status
command.

To configure the iSNS server to use port 4400, run the following command:
isi iscsi isns enable --port=4400
you can confirm that the iSNS service is configured to use the new port by running the isi iscsi isns status
command.

If the iSNS service is configured and disabled, you can enable it by running the following command:
isi iscsi isns enable
You can confirm that the iSNS service is enabled by running the isi iscsi isns status command.

isi iscsi isns disable


Disables the iSNS client service.
Syntax
isi iscsi isns disable
Options
There are no options for this command.
Examples
To disable iSNS, run the following command:
isi iscsi isns disable
You can confirm that the iSNS service is disabled by running the isi iscsi isns status command.

2010 Isilon Systems, Inc.

17

5
isi job

Manages jobs, job policies, and job schedules. This command requires a sub-command.
OneFS includes the following jobs:

AutoBalance: Balances free space in the cluster.


AVScan: Scans files for viruses.
Collect: Reclaims free space that could not be freed due to node or drive unavailability.
FlexProtect: Reprotects the file system.
FSAnalyze: Gathers file system analytics data.
IntegrityScan: Verifies file system integrity.
MediaScan: Scrubs disks for media-level errors.
MultiScan: Runs the Collect and AutoBalance jobs concurrently.
QuotaScan: Updates quota accounting for domains created on an existing file tree.
SetProtectPlus: Applies the default file policy if SmartPools is not licensed.
SmartPools: Enforces SmartPools file policies.
SnapshotDelete: Frees space associated with deleted snapshots.
TreeDelete: Deletes a path in /ifs.

isi job list


Displays a list of jobs that you can control and schedule.
Syntax
isi job list [--quiet]
Options
--quiet, -q
Suppresses job impact policy and enabled/disabled state from the system output.
--help, -h
Displays a list of supported options for this command.
Examples

To display the enabled/disabled state, associated job policy, and description for each job, run the following command:
isi job list

19

isi job

The system displays text similar to the following example output:


Jobs:
Name
Enabled Policy
Description
---------------- ------- ----------- -----------------------------AutoBalance
True
LOW
Balance free space in the
cluster.
AVScan
True
LOW
Scan files for viruses.
Collect
True
LOW
Reclaims free space that
couldn't be freed due to node
or drive unavailability.
FlexProtect
True
MEDIUM
Reprotect the file system.
FSAnalyze
True
LOW
Gather file system analytics
data.
IntegrityScan
True
MEDIUM
Verify file system integrity.
MediaScan
True
LOW
Scrub disks for media-level
errors.
MultiScan
True
LOW
Runs Collect and AutoBalance
jobs concurrently.
QuotaScan
True
LOW
Update quota accounting for
domains created on an existing
file tree.
SetProtectPlus
True
LOW
Applies default file policy if
SmartPools is not licensed.
SmartPools
True
LOW
Enforces SmartPools file
policies.
SnapshotDelete
True
MEDIUM
Free space associated with
deleted snapshots.
TreeDelete
True
HIGH
Delete a path in /ifs.

To restrict the system output to display only the descriptions for each job, run the following command:
isi job list -q
The system displays text similar to the following example output:
AutoBalance: Balance free space in the cluster.
AVScan: Scan files for viruses.
Collect: Reclaims free space that couldn't be freed due to node or drive
unavailability.
FlexProtect: Reprotect the file system.
FSAnalyze: Gather file system analytics data.
IntegrityScan: Verify file system integrity.
MediaScan: Scrub disks for media-level errors.
MultiScan: Runs Collect and AutoBalance jobs concurrently.
QuotaScan: Update quota accounting for domains created on an existing file
tree.
SetProtectPlus: Applies default file policy if SmartPools is not licensed.
SmartPools: Enforces SmartPools file policies.
SnapshotDelete: Free space associated with deleted snapshots.
TreeDelete: Delete a path in /ifs.

isi job status


Displays summaries of running, paused, and waiting jobs, failed jobs, and recent job results.
Syntax
isi job status [--verbose]

20

2010 Isilon Systems, Inc.

isi job
Options
--verbose, -v
Displays the progress of paused and running jobs.
--help, -h
Displays a list of supported options for this command.
Examples
To view job status, including current progress, run the following command:
isi job status --verbose
In the following example output, the FSAnalyze job (job ID 67) was manually started and then paused 5 seconds later.
The SmartPools job (job ID 68) started two seconds ago. There are no recently failed jobs; several recent jobs have run
successfully.
Running jobs:
Job
Impact
------------------------- -----SmartPools[68]
Low
Progress: Processed 1174

Pri Policy
Phase Run Time
--- --------- ----- ---------6
LOW
1/1
0:00:02
LINs: 827 files, 338 directories; 0 errors

Paused and waiting jobs:


Job
Impact Pri Policy
Phase Run Time
State
------------------------- ------ --- --------- ----- ---------- ----------FSAnalyze[67]
Low
6
LOW
1/2
0:00:05
User Paused
Progress: Started
No failed jobs.
Recent job results:
Time
Job
--------------- -------------------------07/03 22:15:05 SnapshotDelete[59]
07/04 22:00:45 FSAnalyze[60]
07/04 22:16:35 SnapshotDelete[61]
07/05 22:00:26 FSAnalyze[62]
07/05 22:18:06 SnapshotDelete[63]
07/06 10:06:22 FlexProtect[64]
07/06 10:23:18 MultiScan[65]
07/06 13:11:30 SmartPools[66]

Event
-------------------Succeeded
Succeeded
Succeeded
Succeeded
Succeeded
Succeeded
Succeeded
Succeeded

Note: If the cluster contains down nodes or read-only nodes or drives, the following notification message displays
at the beginning of the output:
The cluster has down or read-only nodes or drives which may prevent jobs
from
running.

isi job history


Displays recent job events.
Syntax
isi job history [--job=<Job>] [--limit=<Number>] [--no-headers] [--verbose]

2010 Isilon Systems, Inc.

21

isi job
Options
--job=<Job>, -j=<Job>
Displays job history for the specified job only. Valid <Job> values are a job's name or ID number.
--limit=<Number>, -l=<Number>
Specifies the number of most recent job events to display. Valid <Number> values include any
non-negative integer. 10 is the default value. 0 displays all events.
--no-headers, -H
Hides the Time, Job, and Event headers in the system output.
--verbose, -v
Displays event summary information such as elapsed time and errors encountered.
--help, -h
Displays a list of supported options for this command.
Examples

To display the 20 most recent job events, run the following command:
isi job history --limit=20
The system displays text similar to the following example output:
Job events:
Time
--------------06/17 22:18:12
06/18 09:11:06
06/18 09:11:47
06/18 09:11:48
06/18 09:11:53
06/18 09:11:54
06/18 09:11:58
06/18 09:11:58
06/18 09:59:05
06/18 09:59:05
06/18 09:59:05
06/18 09:59:14
06/18 09:59:15
06/18 09:59:20
06/18 09:59:20
06/18 10:10:38
06/18 10:10:38
06/18 10:10:38
06/18 10:10:38
06/18 10:10:38

Job
----------------------SnapshotDelete[10]
MultiScan[11]
MultiScan[11]
MultiScan[11]
MultiScan[11]
MultiScan[11]
MultiScan[11]
MultiScan[11]
FSAnalyze[12]
FSAnalyze[12]
FSAnalyze[12]
FSAnalyze[12]
FSAnalyze[12]
FSAnalyze[12]
FSAnalyze[12]
SnapshotDelete[13]
SnapshotDelete[13]
SnapshotDelete[13]
SnapshotDelete[13]
SnapshotDelete[13]

Event
-----------------------------Succeeded
Waiting
Running
phase 1 fs_lin begin
phase 1 fs_lin end
phase 2 fs_sweep begin
phase 2 fs_sweep end
Succeeded
Waiting
Running
phase 1 fsa begin
phase 1 fsa end
phase 2 fsa_merge begin
phase 2 fsa_merge end
Succeeded
Waiting
Running
phase 1 sdl begin
phase 1 sdl end
Succeeded

To display the event history for job 13 of the previous example, and include additional event summary information,
run the following command:
isi job history --job=13 --verbose
The system displays text similar to the following example output:
Job events:
Time
--------------06/18 10:10:38
06/18 10:10:38
06/18 10:10:38
06/18 10:10:38

22

Job
----------------------SnapshotDelete[13]
SnapshotDelete[13]
SnapshotDelete[13]
SnapshotDelete[13]

Event
-----------------------------Waiting
Running
phase 1 sdl begin
phase 1 sdl end

2010 Isilon Systems, Inc.

isi job

Elapsed time:
LINs deleted:
Snapshots deleted:
Errors:
06/18 10:10:38 SnapshotDelete[13]

0 seconds
36/36
1/1
0
Succeeded

isi job config


Lists or modifies job configuration values. This command is intended for internal use and should not be used without
guidance from Isilon Technical Support.

isi job start


Starts jobs.
Note: To view a list of available jobs that can be started, run the isi job list command.

Syntax
isi job start --job=<Job>
Options
--job=<Job>, -j=<Job>
Required. Specifies the name of the job to start.
--help, -h
Displays a list of supported options for this command.
Examples
To start the SmartPools job, run the following command:
isi job start --job=smartpools
You can verify whether the job started by running the following command:
isi job history --job=smartpools
The system displays recent events for the SmartPools job, similar to the following output:
Job events:
Time
--------------06/16 13:04:52
06/16 13:04:52
06/16 13:04:52
06/16 13:04:53
06/16 13:04:53

Job
-------------------------SmartPools[24]
SmartPools[24]
SmartPools[24]
SmartPools[24]
SmartPools[24]

Event
-----------------------------Waiting
Running
phase 1 filepolicy begin
phase 1 filepolicy end
Succeeded

The Waiting event indicates when the job started. In this example, the job has already completed.

2010 Isilon Systems, Inc.

23

isi job

isi job pause


Pauses running jobs.
Syntax
isi job pause --job=<Job>
Options
--job=<Job>, -j=<Job>
Required. Specifies the name or ID number of the job.
--help, -h
Displays a list of supported options for this command.
Examples
To pause the FSAnalyze job, run the following command:
isi job pause --job=fsanalyze
You can verify whether the job has been paused by running the following command:
isi job history --job=fsanalyze
The system displays recent events for the FSAnalyze job, similar to the following output:
Job events:
Time
--------------06/16 14:58:55
06/16 14:58:55
06/16 14:58:55
06/16 14:59:06

Job
-------------------------FSAnalyze[13]
FSAnalyze[13]
FSAnalyze[13]
FSAnalyze[13]

Event
-----------------------------Waiting
Running
phase 1 fsa begin
User Paused

isi job update


Overrides default priority levels and impact policies for paused and running jobs.
Syntax
isi job update --job=<Job> --priority=<Priority> --policy=<PolicyName>
Options
--job=<Job>, -j=<Job>
Required. Specifies the name or ID number of a currently paused or running job.
--priority=<PriorityLevel>, -p=<PriorityLevel>
Specifies the priority level for the job. Valid PriorityLevel values are 1 (highest; no other job can
interrupt this job) through 10 (lowest; any job can interrupt this job).
--policy=<PolicyName>, -o=<PolicyName>
Specifies the job impact policy to use.
--help, -h
Displays a list of supported options for this command.

24

2010 Isilon Systems, Inc.

isi job
Examples

To update a currently paused or running FSAnalyze job to use priority level 3, run the following command:
isi job update --job=fsanalyze --priority=3
You can verify that the update succeeded by running the isi job status command.

To update a currently paused or running job whose ID is 38 to use priority level 2 and a Medium impact policy, run
the following command:
isi job update --job=38 --priority=2 --policy=medium
You can verify that the update succeeded by running the isi job status command.

isi job resume


Resumes paused jobs.
Syntax
isi job resume --job=<Job>
Options
--job=<Job>, -j=<Job>
Required. Specifies the name or ID number of the job.
--help, -h
Displays a list of supported options for this command.
Examples
To resume the FSAnalyze job from a paused state, run the following command:
isi job resume --job=fsanalyze
You can verify whether the job has been resumed by running the following command:
isi job history --job=fsanalyze
The system displays recent events for the FSAnalyze job, similar to the following output:
Job events:
Time
--------------06/15 22:00:08
06/15 22:00:13
06/15 22:00:17
06/15 22:00:31
06/16 12:25:59
06/16 12:25:59

Job
-------------------------FSAnalyze[10]
FSAnalyze[10]
FSAnalyze[10]
FSAnalyze[10]
FSAnalyze[10]
FSAnalyze[10]

Event
-----------------------------Waiting
Running
phase 1 fsa begin
System Paused
Waiting
Running

isi job cancel


Cancels paused or running jobs.
Syntax
isi job cancel --job=<Job>

2010 Isilon Systems, Inc.

25

isi job
Options
--job=<Job>, -j=<Job>
Required. Specifies the name or ID number of the job.
--help, -h
Displays a list of supported options for this command.
Examples
To cancel the FlexProtect job, run the following command:
isi job cancel --job=flexprotect
You can verify whether the job has been cancelled by running the following command:
isi job status
The system displays recent events, similar to the following output:
Job events:
Time
Job
Event
--------------- -------------------------- -----------------------------06/09 14:59:06 flexprotect[24]
User Cancelled

isi job policy


Manages job impact policies, which you can use to allocate cluster resources for jobs. This command requires a
sub-command.
A job impact policy requires one or more of the following pre-defined impact levels:

Paused: Do not use cluster resources.


Low: Use 10% or less of cluster resources.
Medium: Use 30% or less of cluster resources.
High: Use unlimited cluster resources.

You can create and modify custom impact policies, or you can use one of the following pre-defined impact policies:

LOW: Always use the Low impact level.


MEDIUM: Always use the Medium impact level.
HIGH: Always use the High impact level.
OFF_HOURS: Pause the job during business hours, and use the Low impact level during non-business hours.

isi job policy list


Displays a list of available job impact policies.
Syntax
isi job policy list
Options
--help, -h
Displays a list of supported options for this command.
Examples
To view a list of available job impact policies, run the following command:

26

2010 Isilon Systems, Inc.

isi job

isi job policy list


The system displays output similar to the following example:
Job Policies:
Name
Start
End
Impact
--------------- ------------ ------------ ---------HIGH
Sun 00:00
Sat 23:59
High
LOW

Sun 00:00

Sat 23:59

Low

MEDIUM

Sun 00:00

Sat 23:59

Medium

OFF_HOURS

Sun
Mon
Mon
Tue
Tue
Wed
Wed
Thu
Thu
Fri
Fri

Mon
Mon
Tue
Tue
Wed
Wed
Thu
Thu
Fri
Fri
Sat

09:00
17:00
09:00
17:00
09:00
17:00
09:00
17:00
09:00
17:00
23:59

Low
Paused
Low
Paused
Low
Paused
Low
Paused
Low
Paused
Low

sample_policy

Sun 00:00
Mon 09:00
Fri 17:00

Mon 09:00
Fri 17:00
Sat 23:59

Low
Paused
Low

00:00
09:00
17:00
09:00
17:00
09:00
17:00
09:00
17:00
09:00
17:00

Note: The HIGH, LOW, MEDIUM, and OFF_HOURS impact policies cannot be modified or deleted.

isi job policy create


Creates job impact policies with default settings.
Note: LOW, MEDIUM, HIGH, and OFF_HOURS are reserved impact policy names.
By default, new impact policies are configured to always use the Low impact level. Other available impact levels are
Medium, High, and Paused. To modify these settings, use the isi job policy modify command.
Syntax
isi job policy create --name=<PolicyName>
Options
--name=<PolicyName>
Required. Specifies a name for the new job impact policy.
--help, -h
Displays a list of supported options for this command.
Examples
To create a job impact policy named testpolicy, run the following command:
isi job policy create --name=testpolicy
You can verify that the policy was created by running the isi job policy list command.

2010 Isilon Systems, Inc.

27

isi job

isi job policy set


Assigns default impact policies to jobs.
Syntax
isi job policy set --job=<JobName> --policy=<PolicyName>
Options
--job=<JobName>, -j=<JobName>
Required. Specifies the job that the impact policy will be assigned to. <JobName> must match a valid
job name.
--policy=<PolicyName>, -o=<PolicyName>
Required. Specifies the impact policy to set for the job. <PolicyName> must match a configured job
policy.
--help, -h
Displays a list of supported options for this command.
Examples
To set the Autobalance job to use the MEDIUM impact policy by default, run the following command:
isi job policy --job=autobalance --policy=medium
Note:

You can view a list of configured job policies by running the isi job policy list command.
You can view a list of available jobs and their current default job policies by running the isi job list
command.
You can override a paused or running job's default impact policy by running the isi job update command.

isi job policy modify


Adds impact intervals to job impact policies.
Impact intervals define a block of time within a given week for which a single impact level (Paused, Low, Medium, or
High) is used. This command adds one impact interval at a time to an existing policy. New intervals are aggregated with
existing intervals.
Note: The LOW, MEDIUM, HIGH, and OFF_HOURS impact policies are reserved and cannot be modified.

Syntax
isi job policy modify --policy=<PolicyName> --start=<Time> --end=<Time>
--impact=<ImpactLevel>
Options
--policy=<PolicyName>, -o=<PolicyName>
Required. Specifies the job impact policy to modify. <PolicyName> must be a valid impact policy
name.
--start=<Time>, -s=<Time>
Required. Specifies the start time for the impact interval. Valid Time values are in the form D,HH:MM.
D can be the full name or three-letter abbreviation for the day of the week. HH is the hour of the day
(0-24), and MM is the minute (0-59). Example: Sat,0:00.
--end=<Time>, -e=<Time>

28

2010 Isilon Systems, Inc.

isi job

Required. Specifies the end time for the impact interval. Valid Time values are in the form D,HH:MM.
D can be the full name or three-letter abbreviation for the day of the week. HH is the hour of the day
(0-24), and MM is the minute (0-59). Example: Sat,23:59.
--impact=<ImpactLevel>, -i=<ImpactLevel>
Required. Specifies the impact level to use for the duration of the impact interval. Valid ImpactLevel
values are:

Paused: Do not use cluster resources.


Low: Use 10% or less of cluster resources.
Medium: Use 30% or less of cluster resources.
High: Use unlimited cluster resources.

--help, -h
Displays a list of supported options for this command.
Examples
To add an interval from midnight Sunday through 11:59 pm Monday to an existing impact policy named testpolicy, and
specify a medium impact level for the interval, run the following command:
isi job policy modify --policy=testpolicy --start=Sun,0:00 --end=Mon,11:59
--impact=medium
You can verify whether the interval was added by running the following command:
isi job policy list
In the following example output, testpolicy includes the new interval:
Job Policies:
Name
Start
End
Impact
--------------- ------------ ------------ ---------HIGH
Sun 00:00
Sat 23:59
High
LOW

Sun 00:00

Sat 23:59

Low

MEDIUM

Sun 00:00

Sat 23:59

Medium

OFF_HOURS

Sun
Mon
Mon
Tue
Tue
Wed
Wed
Thu
Thu
Fri
Fri

Mon
Mon
Tue
Tue
Wed
Wed
Thu
Thu
Fri
Fri
Sat

09:00
17:00
09:00
17:00
09:00
17:00
09:00
17:00
09:00
17:00
23:59

Low
Paused
Low
Paused
Low
Paused
Low
Paused
Low
Paused
Low

testpolicy

Sun 00:00
Mon 11:59

Mon 11:59
Sat 23:59

Medium
Low

00:00
09:00
17:00
09:00
17:00
09:00
17:00
09:00
17:00
09:00
17:00

isi job policy delete


Deletes job impact policies.
Note: The LOW, MEDIUM, HIGH, and OFF_HOURS policies are reserved and cannot be deleted.

2010 Isilon Systems, Inc.

29

isi job
Syntax
isi job policy delete --policy=<PolicyName>
Options
--policy=<PolicyName>, -o=<PolicyName>
Required. Specifies the impact policy to delete. <PolicyName> must be a valid impact policy name.
--help, -h
Displays a list of supported options for this command.
Examples
To delete a job impact policy named deleteme, run the following command:
isi job policy delete --policy=deleteme
You can verify that the policy was deleted by running the isi job policy list command.

isi job schedule


Lists, sets, or deletes job schedules. This command requires a sub-command.

isi job schedule list


Lists all scheduled jobs, their configured schedules, and their next scheduled run time.
Syntax
isi job schedule list
Options
--help, -h
Displays a list of supported options for this command.
Examples
To view a list of all scheduled jobs, run the following command:
isi job schedule list
The system displays output similar to the following example:
Job schedules:
Job
--------------FSAnalyze
MediaScan
SmartPools

Schedule
-----------------------------every day at 22:00
the 1st saturday of every m...
every day at 22:00

Next Run
-------------------06/21 22:00
07/03 00:00
06/21 22:00

isi job schedule set


Sets recurring job schedules. This command is available for the FSAnalyze, MediaScan, and SmartPools jobs only.
Syntax
isi job --job=<JobName> --when="[<Interval> [<Frequency>]]"

30

2010 Isilon Systems, Inc.

isi job
Options
--job=<JobName>, -j=<JobName>
Required. Specifies the name of the job. Valid <JobName> values are fsanalyze, mediascan,
and smartpools.
--when="[<Interval> [<Frequency>]]", -w="[<Interval> [<Frequency>]]"
Required. Specifies the recurring date and time at which to start the job.
<Interval> is required and can take one of the following forms:

every {sun-sat}[, ...]


every [{1-31}] day
every [{1-23}] weekday
every [{1-52}] week [on {sun-sat}[, ...]]
every [<Number>] months [on the {1[st]-31[st]}]
the {1-5|last} {sun-sat} every [{1-12}] month
the {1-23|last} weekday every [{1-12}] month
the {1[st]-31[st]} every [{1-12}] month
the last day every [{1-12}] month
yearly on {jan-dec} {1-31}

<Frequency> is optional and can take either of the following forms, using the 12-hour (am/pm) or
24-hour clock. If not specified, the default frequency is at 0:00.

at {<Hr>[:<Min>]}
every [<Number>] {hours|minutes} [from {<Hr>[:<Min]} to
{<Hr>[:<Min]}]

--help, -h
Displays a list of supported options for this command.
Examples

To schedule the FSAnalyze job to run every day at 10 pm, run the following command:
isi job schedule set fsanalyze --when="every day at 10pm"

To schedule the MediaScan job to run once every Monday, Wednesday, and Friday, run the following command:
isi job schedule set mediascan --when="every week on mon, wed, fri"
The job will run at 0:00, which is the default time of day.

To schedule the SmartPools command to run on the 15th day of the month, run the following command:
isi job schedule set smartpools --when="the 15th every month"

isi job schedule delete


Deletes job schedules.
Syntax
isi job schedule delete --job=<JobName>
Options
--job=<JobName>, -j=<JobName>
Required. Specifies the name of the job whose schedule you want to delete.
--help, -h

2010 Isilon Systems, Inc.

31

isi job

Displays a list of supported options for this command.


Examples
To delete the schedule for the SmartPools job, run the following command:
isi job schedule delete --job=smartpools
You can verify the SmartPools job schedule was deleted by running the isi job schedule list command.

32

2010 Isilon Systems, Inc.

6
isi lun

Manages logical unit numbers (LUNs). This command requires a sub-command.

isi lun create


Creates logical units and configures their settings.
Syntax
isi lun create --name=<Target>:<LUN> --size=<Integer>[{B|MB|GB|TB}]
[--comment=<QuotedString>] [--path=<AbsolutePath>] [--protection=<Policy>]
[--access-pattern=<Pattern>] [--online=<Boolean>] [--smart-cache=<Boolean>]
[--read-only=<Boolean>] [--thin=<Boolean>] [--diskpool=<DiskPool>]
Options
--name=<Target>:<LUN>, -n=<Target>:<LunNumber>
Required. Specifies the name of the logical unit. Valid names include the name of an existing target
that will contain the logical unit and a unique logical unit number (0-255) within the target, separated
by a colon (for example, mytarget:0).
--size=<Integer>[{B|MB|GB|TB}]
Required. Specifies the LUN's size (capacity). Valid sizes are 1MB-32TB. Valid units of measure are
B, MB, GB, or TB. The default unit of measure is B. Do not include a space between the integer and
the unit of measure (for example, 50MB). After you create a LUN, you can increase its size but you
cannot decrease it.
--comment=<QuotedString>
Specifies an optional comment for the logical unit. If the comment contains spaces, you must enclose
it in quotation marks.
--path=<AbsolutePath>
Specifies the absolute path, beginning at /ifs, to the default LUN directory. Example:
--path=/ifs/target1luns. This setting overrides the default LUN directory path that is
configured during target creation.
--protection=<Policy>
Specifies the protection policy for the logical unit. You can specify mirroring (2x through 8x) or
Isilon FlexProtect (+1 through +4, +2:1, +3:1) protection.
--access-pattern=<Pattern>, -l=<Pattern>

33

isi lun

Specifies the I/O optimization settings for the logical unit. Valid values are random, streaming,
concurrency, and custom{1-5}. The default setting for logical units is random. Custom settings
are intended for Isilon Technical Support use.
--online=<Boolean>
Sets the logical unit state to online (1) or offline (0). Logical units are online by default.
--smart-cache=<Boolean>
Enables (1) or disables (0) SmartCache. SmartCache can improve performance, but can lead to data
loss if a node loses power or crashes while uncommitted data is in the write cache. This can cause
inconsistencies in any file system that is laid out on the LUN, rendering the file system unusable.
SmartCache is disabled by default.
--read-only=<Boolean>
Sets the write access for the logical unit. Valid values are 1 for read-only or 0 for read/write. Read/write
access is the default setting.
--thin=<Boolean>
Enables (1) or disables (0) thin provisioning. Thin provisioning keeps blocks unallocated until they
are written. Thin provisioning is enabled by default.
--diskpool=<DiskPool>
Adds the logical unit to the specified disk pool. By default, logical units are allocated randomly to any
available disk pool.
--help, -h
Displays a list of supported options for this command.
Examples
To create a logical unit in a target named test1 with a LUN value of 0 and a capacity of 50 GB, run the following
command:
isi lun create --name=test1:0 --size=50GB
To create a logical unit in the target test1 with a LUN value of 1 and capacity of 50 GB, and to pre-allocate space, run
the following command:
isi lun create --name=test1:1 --size=50GB --thin=0
To create a logical unit in the target test1 with a LUN value of 2 and 50 GB capacity, and to specify the default LUN
directory as /ifs/test1luns, run the following command:
isi lun create --name=test1:3 --size=50GB --path=/ifs/test1luns

isi lun delete


Deletes logical units.
Syntax
isi lun delete --name=<TargetName>:<LUN> [--force]
Options
--name=<TargetName>:<LUN>
Required. Specifies the name of the logical unit to delete. Valid names include the name of the target
where the logical unit is located and its logical unit number (LUN), separated by a colon (:), for example
mytarget:4.

34

2010 Isilon Systems, Inc.

isi lun

--force
Suppresses the confirmation prompt.
--help, -h
Displays a list of supported options for this command.
Examples

To delete a logical unit named mytarget:50, run the following command:


isi lun delete --name=mytarget:50
The system displays output similar to the following example:
!! Are you sure you want to delete LUN 50? (yes, y, no, [n])
Type y and then press ENTER.

To delete a logical unit named mytarget:2 without displaying a confirmation message, run the following command:
isi lun delete --name=mytarget:2 --force

isi lun modify


Modifies logical unit configuration settings.
Syntax
isi lun modify --name=<TargetName>:<LUN> [--comment=<QuotedString>]
[--size=<Integer>[{B|MB|GB|TB}]] [--protection=<Policy>]
[--access-pattern=<Pattern>] [--read-only=<Boolean>]
[--online=<Boolean>] [--smart-cache=<Boolean>] [--diskpool=<DiskPool>]
Options
--name=<TargetName>:<LUN>
Required. Specifies the name of an existing logical unit. Valid names include the name of the target
where the logical unit is located and the logical unit number (LUN), separated by a colon (for example,
mytarget:4).
--comment=<QuotedString>
Modifies the description for the logical unit. If the comment contains spaces, it must be enclosed in
quotation marks.
--size=<Integer>[{B|MB|GB|TB}]
Specifies a larger size (capacity) for the logical unit. Valid sizes are 1MB-32TB. Valid units of measure
are B, MB, GB, or TB. The default unit of measure is B. Do not include a space between the integer and
the unit of measure (for example, 50MB).
--protection=<Policy>
Modifies the protection policy for the logical unit. You can specify mirroring or Isilon FlexProtect
protection. Valid values for mirroring are 2x through 8x. Valid values for FlexProtect policy are +1
through +4, +2:1, and +3:1.
--access-pattern=<Pattern>, -l=<Pattern>
Specifies the I/O optimization settings for the logical unit. Valid values are random, streaming,
concurrency, and custom{1-5}. Custom settings are intended for Isilon Technical Support use.
--read-only=<Boolean>

2010 Isilon Systems, Inc.

35

isi lun

Modifies the write access setting for the logical unit. Valid values are 1 for read-only or 0 for read/write.
--online=<Boolean>
Changes the logical unit state to online (1) or offline (0).
--smart-cache=<Boolean>
Enables (1) or disables (0) SmartCache for the logical unit.
--diskpool=<DiskPool>
Adds the logical unit to the specified disk pool.
--help, -h
Displays a list of supported options for this command.
Examples
To increase the capacity to 60 GB for a logical unit named test1:0, run the following command:
isi lun modify --name=test1:0 --size=60GB
To set the write access to read-only and enable write caching for a logical unit named test1:3, run the following command:
isi lun modify --name=test1:3 --read-only=1 --smart-cache=1

isi lun list


Displays information about logical units.
Syntax
isi lun list --name=<Target>:<LUN>
Options
--name=<Target>:<LUN>
Required. Specifies the name of the logical unit whose settings you want to view. Valid names include
the name of the target where the logical unit is located and its logical unit number (LUN), separated
by a colon (for example, mytarget:4).
--help, -h
Displays a list of supported options for this command.
Examples
To view information about a logical unit named test:56, run the following command:
isi lun list --name=test:56

isi lun clone


Creates point-in-time copies of existing logical units.
The source logical units settings are copied to the clone logical unit, enabling you to save time by modifying only the
necessary settings.

36

2010 Isilon Systems, Inc.

isi lun
Syntax
isi lun clone --name=<SourceTarget>:<LUN> --clone=<DestTarget>:<LUN>
[--type=<LUN-type>]
[--comment=<QuotedString>] [--path=<IFSDirectory>] [--access-pattern=<Pattern>]
[--online=<Boolean>] [--smart-cache=<Boolean>] [--read-only=<Boolean>]
Options
--name=<SourceTarget>:<LUN>
Required. Specifies the name of the source logical unit. Valid names include the name of the source
target where the logical unit is located and its logical unit number (LUN), separated by a colon (for
example, mytarget:0).
--clone=<DestTarget>:<LUN>
Required. Specifies a name for the clone logical unit. You must specify a different target, a new LUN,
or both. The LUN must be an integer in the range 0-255, and must be unique for the destination target.
--type=<LUN-type>
Specifies the LUN type (normal, snapshot, or shadow). The default LUN type is normal.
--comment=<QuotedString>
Modifies the description for the logical unit. If the comment contains spaces, it must be enclosed in
quotation marks.
--path=<IFSDirectory>
Specifies a default path, starting at the /ifs directory, where LUN directories will be created. This
setting overrides any default LUN directory paths that are configured for individual targets.
--access-pattern=<Pattern>, -l=<Pattern>
Specifies the I/O optimization settings for the logical unit. Valid values are random, streaming,
concurrency, and custom{1-5}. Custom settings are intended for Isilon Technical Support use.
By default, this setting is inherited from the source.
--online=<Boolean>
Sets the logical unit's state to online (1) or offline (0). The LUN is online by default.
--smart-cache=<Boolean>
Enables (1) or disables (0) SmartCache for the LUN. SmartCache can improve performance, but can
lead to data loss if a node loses power or crashes while uncommitted data is in the write cache. This
can cause inconsistencies in any file system that is laid out on the LUN, rendering the file system
unusable. By default, this setting is inherited from the source.
--read-only=<Boolean>
Specifies the write access setting for the LUN. Valid values are 1 for read-only or 0 for read/write.
--help, -h
Displays a list of supported options for this command.
Examples
To create a shadow clone LUN named mytarget:11 from a source LUN named mytarget:10, run the following
command:
isi lun clone --name=mytarget:10 --clone=mytarget:11 --type=shadow
To create a normal clone LUN named newtarget:0 from a source LUN named oldtarget:10, and specify a new
LUN directory path of /ifs/clones/, run the following command:
isi lun clone --name=oldtarget:10 --clone=newtarget:0 --type=normal
--path=/ifs/clones/

2010 Isilon Systems, Inc.

37

isi lun

isi lun move


Modifies the targets, numbers, and paths of existing logical units.
Syntax
isi lun move --name=<TargetName>:<LUN> --dest=<DestTarget>:<LUN>
[--path=<AbsolutePath>]
Options
--name=<TargetName>:<LUN>
Required. Specifies the name of an existing logical unit. Valid names include the name of the target
where the logical unit is located and the logical unit number (LUN), separated by a colon (for example,
mytarget:4).
--dest=<DestTarget>:<LUN>, -d=<DestTarget>:<LUN>
Required. Specifies a new destination for the logical unit. You can specify a different target, a different
LUN, or both. The LUN must be an integer in the range 0-255, and must be unique for the destination
target.
--path=<AbsolutePath>, -p=<AbsolutePath>
Specifies a new path, beginning at /ifs, to the default LUN directory.
--help, -h
Displays a list of supported options for this command.
Examples
To move a logical unit with a LUN of 0 from a target named oldtarget to a target named newtarget, run the following
command:
isi lun move --name=oldtarget:0 --dest=newtarget:0
To change the LUN of a logical unit from 0 to 3 without changing the target it is contained in (say, target1), run the
following command:
isi lun move --name=target1:0 --dest=target1:3

isi lun import


Recreates logical units that have been replicated to a remote cluster or that have been backed up and then restored to a
remote cluster.
The iSCSI module does not support replicating or restoring snapshots or shadow copies of logical units.
Syntax
isi lun import --name=<TargetName>:<LUN> [--path=<IFSDirectory>]
Options
--name=<TargetName>:<LUN>
Required. Specifies a name for the imported logical unit. Valid names include the name of an existing
target that will contain the logical unit and a unique logical unit number (0-255) within the target,
separated by a colon (for example, mytarget:10).
--path=<IFSDirectory>

38

2010 Isilon Systems, Inc.

isi lun

Specifies the source path, starting at /ifs, where the LUN files are located.
--help, -h
Displays a list of supported options for this command.
Examples
To restore a logical unit from the /ifs/test/recover directory with the name mytarget:40, run the following
command:
isi lun import --name=mytarget:40 --path=/ifs/test/recover

isi lun online


Switches logical units online so that iSCSI initiators are able to discover and connect to them.
Syntax
isi lun online --name=<TargetName>:<LUN>
Options
--name=<TargetName>:<LUN>
Required. Specifies the name of the logical unit to switch online. Valid names include the name of the
target where the logical unit is located and the logical unit number (LUN), separated by a colon (:),
for example mytarget:4.
--help, -h
Displays a list of supported options for this command.
Examples
To make a logical unit named mytarget:1 discoverable to iSCSI initiators, run the following command:
isi lun online --name=mytarget:1

isi lun offline


Switches logical units offline so that they are hidden from iSCSI initiators.
iSCSI initiators cannot discover or connect to offline logical units.
Syntax
isi lun offline --name=<TargetName>:<LUN>
Options
--name=<TargetName>:<LUN>
Required. Specifies the name of the logical unit to take offline. Valid names include the name of the
target that contains the logical unit and the logical unit number (LUN), separated by a colon (:), for
example mytarget:4.
--help, -h
Displays a list of supported options for this command.

2010 Isilon Systems, Inc.

39

isi lun
Examples
To prevent a logical unit named mytarget:1 from being discovered by iSCSI initiators, run the following command:
isi lun offline --name=mytarget:1

40

2010 Isilon Systems, Inc.

7
isi ndmp

Manages Network Data Management Protocol (NDMP) configuration settings, users, and sessions. This command requires a
sub-command.

isi ndmp settings


Displays and configures settings for the NDMP daemon. This command requires a sub-command.

isi ndmp settings list


Displays the TCP/IP port number and data management application (DMA) vendor settings that are configured for the
NDMP daemon.
Syntax
isi ndmp settings list [--name={port|dma}]
Options
--name={port|dma}
Limits the output to display only the TCP/IP port number (port) or DMA vendor settings (dma).
--help, -h
Displays a list of supported options for this command.
Examples
To display the configured port and DMA settings, run the following command:
isi ndmp settings list
The system displays the port and DMA settings and their corresponding values, similar to the following example output:
Setting
Value
-----------------------------------port
10000
dma
generic
To display the port number only, run the following command:
isi ndmp settings list --name=port

41

isi ndmp

The system displays the port number, similar to the following example output:
Setting
Value
-----------------------------------port
10000

isi ndmp settings set


Modifies NDMP TCP/IP port number and data management application (DMA) vendor settings. Running this command
modifies all nodes on the cluster.
Syntax
isi ndmp settings set --name=port --value=<Number>
isi ndmp settings set --name=dma --value={generic|atempo|bakbone
|commvault|emc|symantec|tivoli}
Options
--name={port|dma}, -n={port|dma}
Required. Specifies the name of the NDMP configuration parameter that you want to modify. To
modify the port number, specify port. To modify the DMA vendor, specify dma.
--value=<Value>, -v=<Value>
Required. Specifies the port number or DMA vendor setting.

For the port setting, the default value is 10000. You can change the port number if required for
your particular configuration.
For the DMA vendor setting, the default value is generic. Other valid values are atempo,
bakbone, commvault, emc, symantec, and tivoli.

--help, -h
Displays a list of supported options for this command.
Examples
To set the port number to 10001, run the following command:
isi ndmp settings set --name=port --value=10001
To set the DMA vendor to Symantec, run the following command:
isi ndmp settings set --name=dma --value=symantec
Note: You can view the modified settings by running the isi ndmp settings list command.

42

2010 Isilon Systems, Inc.

isi ndmp

isi ndmp user


Manages NDMP user accounts. NDMP data management applications (DMAs) authenticate themselves to the NDMP
daemon that is running on the cluster by supplying user names and passwords that you configure. This command requires
a sub-command.

isi ndmp user create


Creates NDMP user accounts.
Syntax
isi ndmp user create --name=<NDMPuser> [--password=<Password>]
Options
--name=<NDMPuser>
Required. Specifies the name of the new NDMP user. The name must be unique on the system.
--password=<Password>
Optional. Specifies a password for the user. If you omit this option, the system prompts you to enter
and then confirm a password.
--help, -h
Displays a list of supported options for this command.
Examples
To create a new user with the user name ndmpuser and password Pass1234, run the following command:
isi ndmp user create --name=ndmpuser --password=Pass1234
You can confirm that the system created the new user by running the following command:
isi ndmp user list --name=ndmpuser
The system displays the following output:
NDMP User
--------ndmpuser

isi ndmp user modify


Changes passwords for NDMP user accounts.
Syntax
isi ndmp user modify --name=<NDMPuser> [--password=<Password>]
Options
--name=<NDMPuser>
Required. Specifies the name of the NDMP user whose password you want to change.
--password=<Password>
Optional. Specifies a new password for the user. If you omit this option, the system prompts you to
enter and then confirm a password.
--help, -h
Displays a list of supported options for this command.

2010 Isilon Systems, Inc.

43

isi ndmp
Examples
To change the password to newpass for an NDMP user named ndmpuser, run the following command:
isi ndmp user modify --name=ndmpuser --password=newpass

isi ndmp user delete


Removes NDMP users.
Syntax
isi ndmp user delete --name=<NDMPuser>
Options
--name=<NDMPuser>
Required. Specifies the name of the NDMP user to delete.
--help, -h
Displays a list of supported sub-commands with brief descriptions.
Examples
To delete a user named ndmpuser, run the following command:
isi ndmp user delete --name=ndmpuser
You can confirm that the system deleted the user by running the following command:
isi ndmp user list --name=ndmpuser
The system displays the following output:
User 'ndmpuser' does not exist.

isi ndmp user list


Displays current NDMP users.
Syntax
isi ndmp user list [--name=<NDMPuser>]
Options
--name=<NDMPuser>
Specifies the name of an NDMP user to list. If you omit this option, the system displays all NDMP
users.
--help, -h
Displays a list of supported options for this command.
Examples

To view a list of all NDMP users, run the following command:


isi ndmp user list
As an example, if there are two NDMP users named ndmpuser and ndmpuser2, the system displays the following
output:
NDMP User
---------

44

2010 Isilon Systems, Inc.

isi ndmp

ndmpuser
ndmpuser2

To verify the existence of an NDMP user named ndmpuser, run the following command:
isi ndmp user list --name=ndmpuser
If the user exists, the system displays the following output:
NDMP User
--------ndmpuser
If the user does not exist, the system displays the following output:
NDMP User
--------User 'ndmpuser' not found.

isi ndmp list


Displays information about NDMP sessions. If you run this command without options, the system displays information
about all NDMP sessions in the cluster.
Syntax
isi ndmp list [--session=<SessionID>] [--node=<NodeID>] [--verbose]
Options
--session=<SessionID>
Specifies the NDMP identifier of the session to list.
--node=<NodeID>
Specifies the identifier of the node for which to display sessions.
--verbose, -v
Displays detailed information about the NDMP sessions.
--help, -h
Displays a list of supported options for this command.
Examples
To view detailed information about an NDMP session with the session ID 3.2211, run the following command:
isi ndmp list --session=3.2211 --verbose
The system displays information about that session, including client, start time, and elapsed time, similar to the following
example output:
Session 3.2211
========================================================================
Client
Start Time
Elapsed Time
Data State
Mover State

10.20.29.17

08-13-09 03:38:28

00d 02:48:15

IDLE

Bytes Moved (MB)


0.000000

Throughput (MB/s)
0.000

Tape Device
tape041

Mode
Read/Write

2010 Isilon Systems, Inc.

IDLE

45

isi ndmp

isi ndmp kill


Terminates NDMP sessions. The system also terminates any orphan sessions and releases the associated resources.
Syntax
isi ndmp kill --session=<SessionID>
Options
--session=<SessionID>
Required. Specifies the NDMP identifier of the session that you want to terminate.
--help, -h
Displays a list of supported options for this command.
Examples
To terminate an NDMP session whose session ID is 3.2211, run the following command:
isi ndmp kill --session 3.2211
You can verify that the NDMP session was terminated by running the isi ndmp list command and checking that
the NDMP session is no longer listed.

isi ndmp probe


Displays diagnostic information about NDMP sessions.
Syntax
isi ndmp probe --session=<SessionID>
Options
--session=<SessionID>
Required. Specifies the NDMP identifier of the session to probe.
--help, -h
Displays a list of supported options for this command.
Example
To view diagnostic information about an NDMP session with a session identifier of 3.2211, run the following command:
isi ndmp probe --session=3.2211
The system displays detailed information about the specified session, organized by service type (TAPE, MOVER,
DATA, and PERFWATCH), in output similar to the following example:
Session 3.2211 probe data
================================
Session ID:
2211
Protocol version:
4
Session unique id:
1
DMA interface:
12.33.21.145
DMA address:
12.33.21.16
SCSI device:

46

2010 Isilon Systems, Inc.

isi ndmp

TAPE device:
Open mode:
Session PID:
Session update interval:
TAPE
Device path:
Given device name :
Given unit number:
Device name:
Device unit number:
Controller name:
Controller unit number:
Bus id:
Peripheral device:
Port Number :
Target:
Current File Number:
Current Block Number:
File descriptor:
Pass through device name:
LUN :
Block size:
Record count:
Tape open mode:
Writing:
MOVER
Data Interface:
State:
Mode:
Pause reason:
Halt reason:
Data written:
Bytes written this window:
Seek position:
Bytes left to read:
Window offset:
Window length:
Is new mover window set:
Position:
Record size:
Record number:
Listen socket:
Socket:
Read index:
Write index:
Last bytes xfered:

tape464
2
2211
5
/example/gh/tape464.pass
0
pass
47
isp
0
0
1
3
1
0
0
8
tape464.pass
0
0
0
NDMP_TAPE_RDWR_MODE
0
0.0.0.0
IDLE
NOACTION
NDMP_MOVER_PAUSE_NA
NDMP_MOVER_HALT_NA
0
0
0
0
0
18446744073709551615
1
0
65536
0
-1
-1
0
0
0

DATA
Interface:
Last bytes xfered:
Operation:
State:
Halt reason:
Abort flag:
IO ready:
Socket:
Listen socket:
Read offset:
Read length:
Bytes left to read:
Position:

2010 Isilon Systems, Inc.

0.0.0.0
0
0
0
0
0
0
-1
-1
0
0
0
0

47

isi ndmp

Discard length:

Backup environment
Nlist
PERFWATCH
Timers (sec.msec.usec)
mover write latency
samples:
Counters

48

2010 Isilon Systems, Inc.

8
isi networks

Manages external network configuration settings.


Syntax
isi
isi
isi
isi

networks
networks
networks
networks

--[{add-|remove-}]dns-servers=<IPAddressList>
--[{add-|remove-}]dns-search=<DNSDomainList>
--[{add-|remove-}]tcp-port=<TCPPortList>
--sc-rebalance-all

Note: Syntax and usage for the create, modify, list, and delete sub-commands is available at the links below.

Options
If you run this command without options or sub-commands, the system displays all domain name servers, DNS search lists,
client TCP ports, and subnets configured on the cluster.
--dns-servers=<IPAddressList>
Sets the list of DNS IP addresses, up to a maximum of three. This option overwrites the current list
of DNS servers. Example: --dns-servers=10.52.0.1,10.52.0.2
--add-dns-servers=<IPAddressList>
Adds one or more DNS IP addresses, separated by commas, up to a maximum of three.
--remove-dns-servers=<IPAddressList>
Removes one or more DNS IP addresses.
--dns-search=<DNSDomainList>
Sets the list of DNS search suffixes, up to a maximum of six. This option overwrites the current list
of DNS search suffixes. Example: --dns-search=domain1,domain2,domain3
--add-dns-search=<DNSDomainList>
Adds one or more DNS search suffixes, up to a maximum of six.
--remove-dns-search=<DNSDomainList>
Removes one or more DNS search suffixes.
--tcp-port=<TCPPortList>
Sets one or more recognized client TCP ports. This option overwrites the current list of TCP ports.
Example: --tcp-port=2049,445,20,21,80
--add-tcp-port=<TCPPortList>
Adds one or more recognized client TCP ports.

49

isi networks

--remove-tcp-port=<TCPPortList>
Removes one or more client TCP ports.
--sc-rebalance-all
Rebalances IP addresses in all pools.
--help, -h
Displays a list of supported options and sub-commands.

isi networks create


Creates network configuration objects. This command requires a sub-command.

isi networks create subnet


Creates network subnets. Subnets simplify external network management, and provide flexibility in implementing and
maintaining efficient cluster network operations.
Syntax
isi networks create subnet --name=<String> [--desc=<QuotedString>]
{--netmask=<IPAddress>|--prefixlen=<Number>} [--dsr-addrs=<IPAddressList>]
[--gateway=<IPAddress>] [--gateway-prio=<Number>] [--mtu=<MTU>]
[--sc-service-addr=<IPAddress>] [--vlan-id=<VlanIdentifier>] [--verbose]
Options
--name=<String>
Required. Specifies the name of the new subnet. The subnet name must be unique throughout the
cluster.
--netmask=<IPAddress>
Required for IPv4 addresses. Specifies the netmask of the IPv4 subnet.
--prefixlen=<Number>
Required for IPv6 addresses. Specifies the IPv6 subnet prefix length.
--desc=<QuotedString>
Specifies an optional description for the subnet.
--dsr-addrs=<IPAddressList>
Sets one or more Direct Server Return address for this subnet.
--gateway=<IPAddress>
Specifies the gateway IP address used by the subnet.
--gateway-prio=<Number>
Specifies the gateway priority for the subnet.
--mtu=<MTU>
Specifies the MTU of the subnet.
--sc-service-addr=<IPAddress>
Specifies the IP address on which the SmartConnect module listens for domain name server (DNS)
requests on this subnet.
--vlan-id=<VlanIdentifier>
Specifies the VLAN ID or tag for all interfaces on the subnet.
--verbose

50

2010 Isilon Systems, Inc.

isi networks

Displays detailed information about the progress of the subnet that you are creating.
--help, -h
Displays a list of supported options for this command.
Examples

To create a subnet named ipv4test with a subnet mask of 100.50.10.5, run the following command:
isi networks create subnet --name=ipv4test --netmask=100.50.10.5
The system displays output similar to the following:

Creating subnet 'ipv4test':

OK

Saving:

OK

To create a subnet named ipv6test with a prefix length of 64, run the following command:
isi networks create subnet --name=ipv6test --prefixlen=64
The system displays output similar to the following:
Creating subnet 'ipv6test':

OK

Saving:

OK

You can verify whether a subnet was successfully created by running the isi networks list subnets command.

isi networks create pool


Creates IP address pools. With IP address pools, you can partition your cluster's network interfaces into groups, and
then assign ranges of IP addresses to logical or functional groups within your organization.
Syntax
isi networks create pool --name=<Subnet>:<Pool> [--ranges=<IPRangeList>]
[--ifaces=<NodeInterfaces>] [--sc-subnet=<Subnet>] [--desc=<QuotedString>]
[{--dynamic|--static}] [--zone=<Zone>] [--add-zone-aliases=<String>]
[--remove-zone-aliases=<String>] [--connect-policy=<ConnectPolicy>]
[--failover-policy=<FailoverPolicy>] [{--manual-failback|--auto-failback}]
[--sc-suspend-node=<Node>] [--sc-resume-node=<Node>]
[--verbose]
Options
--name=<Subnet>:<Pool>
Required. Specifies the name of the new pool that you want to create, including the name of the subnet
and the name of the pool, separated by a colon (for example, subnet1:pool0). The pool name
must be unique throughout the given subnet.
--ranges=<IPRangeList>
Specifies one or more IP address ranges for the pool that you want to create. You assign IP addresses
within this range to new interface members.
--ifaces=<NodeInterfaces>
Specifies one or more interface members in this pool.
--sc-subnet=<Subnet>
Specifies the name of the SmartConnect Service subnet that is responsible for this zone.
--desc=<QuotedString>

2010 Isilon Systems, Inc.

51

isi networks

Specifies an optional description of this pool.


--dynamic
Dynamically assigns IP addresses among pool members.
--static
Statically assigns IP addresses to pool members.
--zone=<Zone>
Specifies the SmartConnect zone name for this pool.
--add-zone-aliases=<String>
Adds SmartConnect zone aliases to the pool as a comma-delimited string of DNS names.
--remove-zone-aliases=<String>
Removes SmartConnect zone aliases from the pool as a comma-delimited string of DNS names.
--connect-policy=<ConnectPolicy>
Specifies the SmartConnect client connection balancing policy for this pool.
--failover-policy=<FailoverPolicy>
Specifies the SmartConnect failover policy for this pool.
--manual-failback
Performs connection rebalancing manually after failback.
--auto-failback
Enables automatic connection rebalancing after failback.
--sc-suspend-node=<Node>
Suspends SmartConnect DNS query responses for the specified node.
--sc-resume-node=<Node>
Resumes suspended SmartConnect DNS query responses for the specified node.
--verbose
Displays detailed information about the pool-creation process.
--help, -h
Displays a list of available options.
Examples
To create a new address pool named pool2 under a subnet named subnet1, run the following command:
isi networks create pool --name=subnet1:pool2

isi networks create rule


Creates provisioning rules for configuring network interfaces.
By establishing provisioning rules, you can configure network settings once. The configuration rules that you create
automate the configuration process as you add new nodes to a cluster.
Syntax
isi networks create rule --name=<Subnet>:<Pool>:<Rule>
--iface=<InterfaceName> [--desc=<Description>] [--verbose]
[{--all|--storage|--accelerator|--storage-x|--accelerator-x}]
Options
--name=<Subnet>:<Pool>:<Rule>

52

2010 Isilon Systems, Inc.

isi networks

Required. Specifies the name of the new provisioning rule. Valid names include the subnet, pool, and
a unique rule name, each separated by a colon (for example, subnet1:pool1:newrule). The
rule name must be unique throughout the given pool.
--iface=<InterfaceName>
Required. Specifies the interface name to which the rule applies.
--desc=<QuotedString>
Specifies an optional description for the rule.
--all
Applies this rule to all nodes (default).
--storage
Applies this rule to storage nodes only.
--accelerator
Applies this rule to Accelerator nodes only.
--storage-x
Applies this rule to X-Series storage nodes only.
--accelerator-x
Applies this rule to Accelerator-X nodes only.
--verbose, -v
Displays detailed information about the progress of the rule creation.
--help, -h
Displays a list of supported options for this command.

isi networks modify


Modifies existing network configuration settings. This command requires a sub-command.

isi networks modify subnet


Modifies network subnet settings.
Syntax
isi networks modify subnet [--name=<Subnet>] [--new-name=<Subnet>]
[--desc=<Description>] [{--enable-vlan|--disable-vlan}]
[--vlan-id=<VlanIdentifier>] [{--netmask=<IPAddress>|--prefixlen=<Number>}]
[--dsr-addrs=<IPAddressList>] [--add-dsr-addrs=<IPAddressList>]
[--remove-dsr-addrs=<IPAddressList>] [--gateway=<IPAddress>]
[--gateway-prio=<Number>] [--sc-service-addr=<IPAddress>]
[--mtu=<MTU>] [--verbose] [--force]
Options
--name=<Subnet>
Required. Specifies the name of the subnet to modify.
--new-name=<Subnet>
Specifies a new name for the subnet. The name must be unique throughout the cluster.
--desc=<QuotedString>
Specifies an optional description for this subnet.
--enable-vlan

2010 Isilon Systems, Inc.

53

isi networks

Enables all virtual LAN tagging on this subnet.


--disable-vlan
Disables any virtual LAN tagging on this subnet.
--vlan-id=<VlanIdentifier>
Specifies the VLAN ID or tag for all interfaces on this subnet.
--netmask=<IPAddress>
For IPv4 addresses only. Specifies the netmask of the IPv4 subnet.
--prefixlen=<Number>
For IPv6 addresses only. Specifies the IPv6 subnet prefix length.
--dsr-addrs=<IPAddressList>
Specifes one or more Direct Server Return addresses for this subnet.
--add-dsr-addrs=<IPAddressList>
Adds one or more Direct Server Return addresses to this subnet.
--remove-dsr-addrs=<IPAddressList>
Removes one or more Direct Server Return addresses from this subnet.
--gateway=<IPAddress>, -g=<IPAddress>
Specifies the gateway IP address used by this subnet.
--gateway-prio=<Number>, -p=<Number>
Specifies the gateway priority for the subnet.
--sc-service-addr=<IPAddress>
Specifies the address on which SmartConnect listens for DNS requests on this subnet.
--mtu=<MTU>
Specifies the MTU of this subnet.
--verbose, -v
Displays detailed information about the progress of the subnet modification process.
--force, -f
Suppresses any prompts, warnings, or confirmation messages that would otherwise appear before or
during the subnet modification operation.
--help, -h
Displays a list of supported options for this command.

isi networks modify pool


Modifies IP address pool settings.
Syntax
isi networks modify pool --name=<Subnet>:<Pool> [--new-name=<Pool>]
[--sc-rebalance] [--ranges=<IPRangeList>] [--add-ranges=<IPRangeList>]
[--remove-ranges=<IPRangeList>] [--ifaces=<NodeInterface>]
[--add-ifaces=<NodeInterface>] [--remove-ifaces=<NodeInterface>]
[--sc-subnet=<String>] [--desc=<QuotedString>] [{--dynamic|--static}]
[--zone=<Zone>] [--add-zone-aliases=<String>]
[--remove-zone-aliases=<String>] [--connect-policy=<ConnectPolicy>]
[--failover-policy=<FailoverPolicy>] [{--manual-failback|--auto-failback}]
[--sc-suspend-node=<NodeLnn>] [--sc-resume-node=<NodeLnn>] [--verbose]
[--force]

54

2010 Isilon Systems, Inc.

isi networks
Options
--name=<Subnet>:<Pool>
Required. Specifies the name of the subnet to modify. Valid names include the name of the subnet
and the name of the pool, separated by a colon, for example subnet1:pool0.
--new-name=<Pool>
Sets a new name for the pool. This must be unique throughout the subnet. Note that this option does
not include the name of the subnet.
--sc-rebalance
rebalances IP addresses for the specified pool.
--ranges=<IPRangeList>
Sets one or more IP address ranges in this pool. You assign IP addresses within this range to new
interface members.
--add-ranges=<IPRangeList>
Adds one or more IP address ranges to this pool.
--remove-ranges=<IPRangeList>
Removes the specified IP address range or ranges from this pool.
--ifaces=<NodeInterface>
Sets the interface members in this pool.
--add-ifaces=<NodeInterface>
Adds one or more member interfaces to this pool.
--remove-ifaces=<NodeInterface>
Removes one or more member interfaces from this pool.
--sc-subnet=<String>
Specifies the name of the SmartConnect Service subnet that is responsible for this zone.
--desc=<QuotedString>
Specifies an optional description for this pool.
--dynamic
Dynamically assigns addresses among pool members.
--static
Statically assigns addresses to pool members.
--zone=<Zone>
Specifies the SmartConnect zone name for this pool.
--add-zone-aliases=<String>
Adds SmartConnect zone aliases to the pool as a comma-delimited string of DNS names.
--remove-zone-aliases=<String>
Removes SmartConnect zone aliases from the pool as a comma-delimited string of DNS names.
--connect-policy=<ConnectPolicy>
Specifies the SmartConnect client connection balancing policy for this pool.
--failover-policy=<FailoverPolicy>
Specifies the SmartConnect failover policy for this pool.
--manual-failback
Performs connection rebalancing manually after failback.
--auto-failback

2010 Isilon Systems, Inc.

55

isi networks

Performs connection rebalancing automatically after failback.


--sc-suspend-node=<NodeLnn>
Suspends SmartConnect DNS query responses for the node.
--sc-resume-node=<NodeLnn>
Resumes suspended SmartConnect DNS query responses for the node.
--verbose, -v
Displays detailed information about the progress of the pool modification process.
--force, -f
Suppresses any prompts, warnings, or confirmation messages that would otherwise appear before or
during the operation.
--help, -h
Displays a list of supported options for this command.
Examples
To remove node 6 from participating in the SmartConnect profile for the default pool named auto-ext1-Static-pool, run
the following command:
isi networks modify pool --name=auto-ext1:auto-ext1-Static-pool
--sc-suspend-node=6
You can confirm that the node has been suspended by running the following command:
isi networks list pools --verbose

isi networks modify rule


Modifies network provisioning rule settings.
Syntax
isi networks modify rule --name=<Subnet>:<Pool>:<Rule> [--new-name=<Rule>]
[--pool=<Subnet>:<Pool>] [--iface=<NodeInterface>] [--desc=<Description>]
[{--all|--storage|--accelerator|--storage-x|--accelerator-x}] [--verbose]
Options
--name=<Subnet>:<Pool>:<Rule>
Required. Specifies the name and location of the rule, including the name of the subnet, the name of
the pool, and the name of the rule, separated by colons (for example, subnet1:pool0:rule3).
--new-name=<Rule>
Specifies a new name for the rule. This name must be unique throughout the pool. Note that this option
does not include the name of the subnet or the pool.
--pool=<Subnet>:<Pool>
Changes the pool to which the rule belongs. You must specify the name of the subnet and the name
of the pool, separated by a colon (for example, subnet1:pool3).
--iface=<NodeInterface>
Specifies the node interface to which the rule applies.
--desc=<Description>
Specifies an optional description for this rule.
--all
Applies this rule to all nodes. This is the default setting.

56

2010 Isilon Systems, Inc.

isi networks

--storage
Applies this rule to storage nodes only.
--accelerator
Applies this rule to Accelerator nodes only.
--storage-x
Applies this rule to Storage-x nodes only.
--accelerator-x
Applies this rule to Accelerator-x nodes only.
--verbose, -v
Displays detailed information about the the rule modification process.
--help, -h
Displays a list of supported options for this command.

isi networks list


Displays network configuration objects. This command requires a sub-command.

isi networks list subnets


Displays available subnets.
Subnets simplify external network management, and provide flexibility when implementing and maintaining efficient
cluster network operations.
Syntax
isi networks list subnets [--name=<Subnet>] [--has-addr=<IPAddress>]
[--verbose]
Options
If you run this command without options or with only the --verbose option, the system displays a list of all available
subnets.
--name=<Subnet>
Displays only subnets that contain the specified string.
--has-addr=<IPAddress>
Displays the subnet whose range includes the specified IP address.
--verbose, -v
Displays detailed subnet information.
--help, -h
Displays a list of supported options for this command.
Examples
To view a list of all subnets, run the following command:
isi networks list subnets

2010 Isilon Systems, Inc.

57

isi networks

The system displays the available subnets, as shown in the following sample output:
Name
Subnet
Gateway:Prio
SC Service Pools
--------------- ------------------ ------------------ --------------- ----subnet0
11.22.3.0/24
11.22.0.1:1
11.22.100.10
2
10gbe
11.22.33.0/24
N/A
N/A
1
To view detailed information about the subnet whose range includes the IP address 11.22.3.45, run the following
command:
isi networks list subnets --has-addr=11.22.3.45 --verbose
The system displays the subnet, similar to the following sample output:
subnet0 - test 1
Netmask:
Subnet:
Gateway
MTU:
SC Service Address:
VLAN Tagging:
VLAN ID:
DSR Addresses:
Pools:

255.255.255.0
11.22.3.0
11.22.3.1, Priority 1
1500
11.22.3.129
Disabled
0
0
2
pool0 - Default pool
dynamic

isi networks list pools


Displays available IP address pools.
IP address pools enable you to partition your cluster's network interfaces into groups, and then assign ranges of IP
addresses to logical or functional groups within your organization.
Syntax
isi networks list pools [--name=<String>] [--subnet=<String>]
[--rule=<String>] [--iface=<InterfaceName>] [--verbose]
isi networks list pools --has-addr=<IPAddress> [--verbose]
Options
If you run this command without options or with only the --verbose option, the system displays a list of all available IP
address pools.
--name=<String>
Displays only pool names that match the specified string, or specifies a full pool name in the form
<Subnet>:<Pool> (for example, subnet0:pool1).
--subnet=<String>
Displays only pools within a subnet whose name matches the specified string.
--rule=<String>
Displays only pools containing a rule name that matches the specified string.
--iface=<InterfaceName>
Displays only pools containing the specified member interface.
--has-addr=<IPAddress>
Displays only the pool that contains the specified IP address.
--verbose, -v
Displays detailed information about the specified pool.

58

2010 Isilon Systems, Inc.

isi networks

--help, -h
Displays a list of supported options for this command.
Examples
To view a list of all available IP address pools, run the following command:
isi networks list pools
The system displays a list of pools in output similar to the following example:
Subnet
-------subnet0
subnet0
subnet0

Pool
-------pool0
pool10
example1

SmartConnect Zone
---------------------example.samplesite.com

Ranges
-----------10.22.132.1-6
10.22.136.1-6
10.33.150.20-30

Alloc
------Static
Static
Dynamic

To display all pools whose names contain the string pool0, run the following command:
isi networks list pools --name=pool0
The system displays output similar to the following example:
Subnet
Pool
-------- -------subnet0
pool0
subnet0
pool10

SmartConnect Zone
-------------------

Ranges
-----------10.22.132.1-6
10.22.136.1-6

Alloc
------Static
Static

isi networks list rules


Displays provisioning rules.
Syntax
isi networks list rules [--name=<String>] [--subnet=<String>]
[--pool=<String>] [--verbose] [--iface=<InterfaceName>]
[{--all|--storage|--accelerator|--storage-x|--accelerator-x}]
Options
If you run this command without options or with only the --verbose option, the system displays a list of all provisioning
rules.
--name=<String>
Displays only rule names that contain the specified string, or specifies a full rule name in the form
<Subnet>:<Pool>:<Rule> (for example, subnet0:pool0:rule3).
--subnet=<String>
Displays only rules within a subnet whose name matches the specified string.
--pool=<String>
Displays only rules within a pool whose name matches the specified string, or specifies a full pool
name in the form <Subnet>:<Pool> (for example, subnet0:pool0).
--iface=<InterfaceName>
Displays only rules that the specified member interface applies to.
--all
Displays provisioning rules that apply to all nodes.
--storage
Displays provisioning rules that apply only to Storage nodes.

2010 Isilon Systems, Inc.

59

isi networks

--accelerator
Displays provisioning rules that apply only to Accelerator nodes.
--storage-x
Displays provisioning rules that apply only to Storage-x nodes.
--accelerator-x
Displays provisioning rules that apply only to Accelerator-x nodes.
--verbose, -v
Displays detailed information about rules.
--help, -h
Displays a list of supported options for this command.
Example
To view a list of provisioning rules on a node, run the following command:
isi networks list rules
The system displays the list of rules in output similar to the following example:
Name
Pool
Node Type
Interface
--------------- ------------------------- -------------- ------------------rule0
subnet0:pool0
All
ext-1

isi networks list interfaces


Displays a list of network interfaces within a subnet's IP address pool.
Syntax
isi networks list interfaces [--show-inactive] [--verbose]
Options
--show-inactive
Includes inactive interfaces.
--verbose, -v
Displays more detailed information.
--help, -h
Displays a list of supported options for this command.
Example
To view a list of network interfaces, including those that are inactive, run the following command:
isi networks list interfaces --show-inactive
The system displays a list of inactive interfaces, similar to the following example output:

60

Interface

Status

Membership

Addresses

--------------1:ext-1
1:ext-2
1:ext-agg
2:ext-1

----------up
no carrier
inactive
up

-------------------subnet0:pool0

------------------11.22.3.45

subnet0:pool0

11.22.34.56

2010 Isilon Systems, Inc.

isi networks

2:ext-2
2:ext-agg

no carrier
inactive

To view detailed information about the network interfaces, run the following command:
isi networks list interfaces --verbose
The system displays detailed information about the interfaces, similar to the following example output:
Node:
Interface:
NIC Name:
Status:
In:
Out:
Owners:
IP Addrs:

1
ext-1
example0
up
49Kb/s
0b/s
1
subnet0:pool0
1
11.22.3.45

Node:
Interface:
NIC Name:
Status:
In:
Out:
Owners:
IP Addrs:

1
ext-2
example1
no carrier
0b/s
0b/s
0
0

Node:
Interface:
NIC Name:
Status:
In:
Out:
Owners:

2
ext-1
example0
up
11Kb/s
0b/s
1
subnet0:pool0
1
11.22.34.56

IP Addrs:

isi networks delete


Deletes network configuration objects. This command requires a sub-command.

isi networks delete subnet


Deletes network subnets.

! Caution: Deleting all subnets may result in connection issues.


Syntax
isi networks delete subnet [--name=<Subnet>] [--force]
Options
--name=<Subnet>
Required. Specifies the name of the subnet that you want to delete.
--force, -f

2010 Isilon Systems, Inc.

61

isi networks

Suppresses any prompts, warnings, or confirmation messages that would otherwise appear.
--help, -h
Displays a list of supported options for this command.
Examples
To delete a subnet named subnet1, run the following command:
isi networks delete subnet subnet1
The following confirmation prompt displays:
!! Are you sure you want to delete subnet 'subnet1'? (yes, [no])
To confirm the deletion, type yes and then press ENTER.
Note: If you attempt to delete the last remaining subnet, a warning message similar to the following example
displays before the confirmation prompt:
Warning: subnet 'subnet1' is the only remaining subnet;
deleting it may result in connection issues.
If you see this message, it is recommended that you type no and then press ENTER to cancel the operation.

isi networks delete pool


Deletes IP address pools.

! Caution: Deleting all IP address pools may result in connection issues.


Syntax
isi networks delete pool [--name=<Subnet>:<Pool>] [--force]
Options
--name=<Subnet>:<Pool>:<Rule>
Required. Specifies the IP address pool to delete. Valid input includes the name of the subnet and the
name of the pool, separated by colons.
--force, -f
Suppresses any prompts, warnings, or confirmation messages that would otherwise appear.
--help, -h
Displays a list of supported options for this command.
Examples
To delete an IP address pool named pool0 from subnet1, run the following command:
isi networks delete pool subnet1:pool0
The following confirmation prompt displays:
!! Are you sure you want to delete pool 'subnet1:pool0'? (yes, [no])
To confirm the deletion, type yes and then press ENTER.

62

2010 Isilon Systems, Inc.

isi networks

Note: If you attempt to delete the only IP address pool in the subnet, a warning message similar to the following
example displays before the confirmation prompt:
!! Warning: pool 'subnet1:pool0' is the only remaining pool; deleting
!! it may result in connection issues.
If you see this message, it is recommended that you type no and then press ENTER to cancel the operation.

isi networks delete rule


Deletes provisioning rules.
Syntax
isi networks delete rule --name=<Subnet>:<Pool>:<Rule> [--force]
Options
--name=<Subnet>:<Pool>:<Rule>
Required. Specifies the provisioning rule to delete. Valid input includes the name of the subnet, the
name of the pool, and the name of the rule, separated by colons.
--force, -f
Suppresses any prompts, warnings, or confirmation messages that would otherwise appear.
--help, -h
Displays a list of supported options for this command.
Examples
To delete a provisioning rule named rule0 from subnet1:pool2, run the following command:
isi networks delete rule subnet1:pool2:rule0
The following confirmation prompt displays:
!! Are you sure you want to delete rule 'subnet1:pool2:rule0'? (yes,
!! [no])
Type yes and then press ENTER.

2010 Isilon Systems, Inc.

63

9
isi pkg

Distributes and manages hot fixes, service updates, and new applications on a cluster. This command requires a sub-command.

isi pkg create


Creates patches. This command is intended for internal use and should not be used without guidance from Isilon Technical
Support.

isi pkg delete


Uninstalls patches.
Syntax
isi pkg delete <PatchName>
Options
<PatchName>
Required. Uninstalls a patch from the cluster. The package identifier can be either a path to a tar archive
or a URL for a patch on an HTTP or FTP site.
Examples
To uninstall a package named patch-example.tar from the cluster, run the following command:
isi pkg delete patch-example.tar
You can verify that the patch was successfully uninstalled by running the isi pkg info command.

isi pkg install


Installs patches from a tar archive or an HTTP or FTP site.
Syntax
isi pkg install <PatchName>

65

isi pkg
Options
<PatchName>
Required. Installs the specified patch on the cluster. PatchName can be either a path to a tar archive
or a URL for a patch on an HTTP or FTP site.
Examples
To install a patch named patch-example.tar on the cluster, run the following command:
isi pkg install patch-example.tar
The system displays output similar to the following example:
Preparing to install the package...
Installing the package...
Committing the installation...
Package successfully installed
You can verify that the patch was successfully installed by running the following command:
isi pkg info patch-example.tar
If the patch was successfully installed, the system displays the package name and date of installation, similar to the
following output:
Information for patch-example:
Description:
Package Name : patch-example - 2009-10-11
If the patch was not installed, the system displays the following output:
patch-example.tar

It is not installed.

isi pkg info


Displays information about patches that are installed on the cluster.
Syntax
isi pkg info [<PatchName>]
Options
<PatchName>
Displays information about the specified patch only. PatchName can be the path to a tar archive or
the URL of a patch on an HTTP or FTP site. If you omit this option, the system displays all installed
patches.
Examples
To check whether a patch named patch-example.tar is installed, run the following command:
isi pkg info patch-example.tar
If the patch is installed, the system displays the package name and date of installation, similar to the following output:
Information for patch-example:
Description:
Package Name : patch-example - 2009-10-11

66

2010 Isilon Systems, Inc.

isi pkg

If the patch is not installed, the system displays the following output:
patch-example.tar

2010 Isilon Systems, Inc.

It is not installed.

67

10
isi services

Displays the state of system services or changes the state of services that you have permissions to modify.
Syntax
isi services [-l] [-a [<Service>]]
isi services <Service> [{enable|disable}]
Options
If you run this command without options, the system displays the output of the -l option. If used together, the -a option overrides
the -l option.
-l
Displays a list of all services whose state you are permitted to change. The output includes a short
description of each service and its current state (enabled or disabled).
-a
Displays an augmented list that includes all services and their current status settings, including those
that you cannot modify. The output includes a short description of each service and its current state
(enabled or disabled).
<Service> enable
Enables the specified service.
<Service> disable
Disables the specified service.
Examples

To view a list of services that you are permitted to modify, run the following command:
isi services -l

To view a ist of all services, including those you cannot modify, run the following command:
isi services -a

To view the current state of the NFS service, run the following command:
isi services -a nfs

To start the VSFTPD service, run the following command:


isi services vsftpd enable

69

isi services

The system displays the following output:


The service 'vsftpd' has been enabled.
Note: If the service is already enabled, the following output displays:
Service 'vsftpd' is already enabled.

70

2010 Isilon Systems, Inc.

11
isi smartpools

Manages the application of the SmartPools file pool policy. This command requires a sub-command.

isi smartpools process


Applies the configured SmartPools file pool policy to files and directories.
Syntax
isi smartpools process --path=<Path> [--recurse] [--verbose]
[--stats] [--nop] [--dont-restripe] [--quiet] [--printable]
Options
--path=<Path>, -p=<Path>
Required. Specifies the path to the file or directory to process.
--recurse, -r
Recurses through directories.
--verbose, -v
Displays the configuration settings that are being applied.
--stats, -s
Displays statistics on the files processed.
--nop, -n
Calculates the specified settings without actually applying them. This option is best used with the -v
or -s option.
--dont-restripe, -d
Changes the per-file policies without restriping the file.
--quiet, -q
Suppresses warning messages.
--printable, -P
Displays file names as unambiguous printable ASCII plus encoding.
--help, -h
Displays a list of supported options for this command.

71

12
isi status

Displays real-time information about the status of the cluster or the status of nodes in the cluster.
The system returns health status, cluster capacity, the amount of space available, detailed throughput data, and operations
status datawhether finished, active, waiting, or failed.
Syntax
isi status [-q] [-w] [-D] [-n[LNN]]
Options
If you run this command without any options, the system displays a summary of cluster health and capacity, health and usage
statistics for each node, all active alerts, the status of current protection operations, and a list of failed protection operations.
-q
Omits the protection operations status output.
-w
Disables truncation. By default, long status messages (for example, alerts descriptions) are truncated
to fit into an 80-column window.
-D
Includes detailed information about the running protection operations and the failed protection operations
on each node, including a list of worker processes and errors.
-n[LNN]
Displays a detailed status report for each node, or for the specified logical node number (LNN),
including statistics for each disk and network interface in the node. This option enables you to quickly
determine which nodes and disks are running and which, if any, have failed.
Examples
To view detailed information about a cluster and its connected nodes, run the following command:
isi status -D
The system displays the current statistics for both the cluster and the individual nodes, similar to the following example output:
Cluster Name:
Cluster Health:
Available:
ID | IP Address

example1
[ OK ]
16T (> 99%)
Health
|D-A--S-R|

Throughput (bits/s)
In
Out
Total |

Used

/ Capacity

73

isi status

----+-----------------+--------+-------+-------+-------+----------------------1 | 11.22.333.1
| [ OK ] |
0 |
36K |
36K | 158M / 5.4T (< 1%)
2 | 11.22.333.2
| [ OK ] |
0 |
0 |
0 | 154M / 5.4T (< 1%)
3 | 11.22.333.3
| [ OK ] |
0 |
0 |
0 | 157M / 5.4T (< 1%)
4 | 11.22.333.4
| [ OK ] |
0 |
18K |
18K | (Diskless)
-------------------------------+-------+-------+-------+----------------------Cluster Totals:
|
0 |
53K |
53K | 469M /
16T (< 1%)
Health Fields: D = Down, A = Attention, S = Smartfailed, R = Read-Only
Finished Operations (3):
OPERATION (ID)
AutoBalance (1)
IntegrityScan (2)
Collect (3)

POLICY
LOW
MEDIUM
LOW

START
08/19 14:32
08/20 14:48
08/20 14:49

COMPLETE
08/19 14:32
08/20 14:49
08/20 14:49

ELAPSED
0:00:05
0:00:27
0:00:03

No active operations.
No waiting operations.
No failed operations.
To view detailed node and disk information, run the following command:
isi status -n
The system displays the health status of each node, whether the nodes are online or offline, and each node's capacity and
availability, similar to the following example output:
Node LNN:
Node ID:
Node Name:
Node IP Address:
Node Health:
Node SN:
Node Capacity:
Available:
Used:
Network Status:
Internal:
External:

1
1
example-55-1
11.22.333.44
[ OK ]
05440039S
1.6T
1.6T (97%)
35G ( 2%)
2 IB network interfaces (1 up, 1 down)
2 GbE network interfaces (1 up, 1 down)
1 Aggregated network interfaces (0 up, 1 down)

Disk Drive Status:


Bay 1 <10>
Bay 2 <7>
0b/s
0b/s
[HEALTHY]
[HEALTHY]
Bay 5 <9>
13Mb/s
[HEALTHY]
Node LNN:
Node ID:
Node Name:
Node IP Address:
Node Health:
Node SN:
Node Capacity:
Available:
Used:

74

Bay 6 <N/A>
N/A
[EMPTY]

Bay 3 <5>
0b/s
[HEALTHY]

Bay 4 <2>
4.3Mb/s
[HEALTHY]

Bay 7 <4>
0b/s
[HEALTHY]

Bay 8 <1>
0b/s
[HEALTHY]

2
2
example-55-2
11.22.333.45
[ OK ]
05520042S
1.8T
1.7T (98%)
35G ( 1%)

2010 Isilon Systems, Inc.

isi status

Network Status:
Internal:
External:

2 IB network interfaces (1 up, 1 down)


2 GbE network interfaces (1 up, 1 down)
1 Aggregated network interfaces (0 up, 1 down)

Disk Drive Status:


Bay 1 <11>
Bay 2 <8>
4.2Mb/s
1.4Mb/s
[HEALTHY]
[HEALTHY]
Bay 5 <10>
0b/s
[HEALTHY]
Node LNN:
Node ID:
Node Name:
Node IP Address:
Node Health:
Node SN:
Node Capacity:
Available:
Used:
Network Status:
Internal:
External:

Bay 6 <7>
1.4Mb/s
[HEALTHY]

2010 Isilon Systems, Inc.

Bay 4 <2>
5.0Mb/s
[HEALTHY]

Bay 7 <4>
0b/s
[HEALTHY]

Bay 8 <1>
0b/s
[HEALTHY]

3
4
example-55-3
11.22.333.56
[ OK ]
05440037S
1.8T
1.7T (98%)
35G ( 1%)
2 IB network interfaces (1 up, 1 down)
2 GbE network interfaces (1 up, 1 down)
1 Aggregated network interfaces (0 up, 1 down)

Disk Drive Status:


Bay 1 <11>
Bay 2 <8>
19Mb/s
0b/s
[HEALTHY]
[HEALTHY]
Bay 5 <10>
66Kb/s
[HEALTHY]

Bay 3 <5>
0b/s
[HEALTHY]

Bay 6 <7>
9.8Mb/s
[HEALTHY]

Bay 3 <5>
0b/s
[HEALTHY]

Bay 4 <2>
66Kb/s
[HEALTHY]

Bay 7 <4>
0b/s
[HEALTHY]

Bay 8 <1>
0b/s
[HEALTHY]

75

13
isi target

Manages iSCSI targets. This command requires a sub-command.

isi target create


Creates iSCSI targets and optionally specifies their description, default LUN directory path, initiator access control, and
CHAP authentication settings.
You can configure or modify a target's settings at a later time by running the isi target modify command.
Syntax
isi target create --name=<TargetName> [--comment=<QuotedString>]
[--path=<ifs-Directory>] [--require-auth=<Boolean>]
[--require-allow=<Boolean>] [--initiator=<Initiator>]
[--chap=<User>:<Secret>]
Options
--name=<TargetName>, -n=<TargetName>
Required. Specifies a name for the target. Valid names begin with a letter and contain only lowercase
letters, numbers, and hyphens (-).
--comment=<QuotedString>
Specifies a description for the target, enclosed in quotation marks.
--path=<ifs-Directory>
Specifies a default path under /ifs for LUN directories.
--require-auth=<Boolean>
Enables (1) or disables (0) CHAP authentication. CHAP authentication is disabled by default.
--require-allow=<Boolean>
Enables (1) or disables (0) initiator access control. Access control is disabled by default.
--initiator=<Initiator>
Adds an initiator to the initiator access list. The specified value must be a valid iSCSI Qualified Name
(IQN).
--chap=<User>:<Secret>
Adds a CHAP user:secret pair to the CHAP secrets list.

77

isi target

Both the user and secret are case-sensitive. Secrets must be 12-16 characters long. You can specify a
valid IQN as the user. If you do not specify an IQN, valid users can contain alphanumeric characters,
periods (.), hyphens (-), and underscores (_). Example: --chap=user1:PassWord1234
--help, -h
Displays a list of supported options for this command.
Examples

To create a target named test1 using the default configuration settings, run the following command:
isi target create --name=test1
You can verify that the target was created by running the following command:
isi target list test1
The system displays the test1 target and its properties, similar to the following output:
Target : test1
Luns: 0
Comment:

Capacity:

Allowed Initiators: All


Default path: /ifs/iscsi

To create a target named test2, require initiator access control for the target, and add a Microsoft iSCSI initiator
named "iqn.1991-05.com.microsoft:example3" to the target's initiator access list, run the following command:
isi target create --name=test2 --require-allow=1
--initiator=iqn.1991-05.com.microsoft:example3
You can verify that the target was created by running the following command:
isi target list test2
The system displays the test2 target and its properties, similar to the following output:
Target : test2
Luns: 0
Comment:

Capacity:

Allowed Initiators: 1
Default path: /ifs/iscsi

isi target delete


Deletes iSCSI targets and their associated LUNs.
Note: If you delete a target, all logical unit numbers (LUNs) that are contained in the target are also deleted, and
all LUN data is destroyed. This operation cannot be undone. In addition, any iSCSI sessions that are connected
to the target are terminated.
Syntax
isi target delete [--force] --name=<TargetName>
Options
--name=<TargetName>, -n=<TargetName>
Required. Specifies the name of the target to delete.
--force
Deletes the target without first displaying a confirmation prompt.
--help, -h

78

2010 Isilon Systems, Inc.

isi target

Displays a list of supported options for this command.


Examples

To delete a target named test1, run the following command:


isi target delete --name=test1
The system displays output similar to the following example:
!! Are you sure you want to delete target 'test1'? 4 LUNs totaling
!! 170 GB will be permanently removed. (yes, y, no, [n])
You can verify that the target was deleted by running the following command:
isi target list --name=test1
The system displays the following error message:
Error: cannot find the specified target (test1)
Type y and then press ENTER.

To delete a target named test2, without displaying a confirmation message, run the following command:
isi target delete --name=test2 --force
You can verify that the target was deleted by running the following command:
isi target list --name=test2
The system displays the following error message:
Error: cannot find the specified target (test2)

isi target modify


Modifies iSCSI target settings.
Syntax
isi target modify --name=<TargetName> [--path=<ifs-Directory>]
[--comment=<QuotedString>] [--require-auth=<Boolean>]
[--add-chap=<User>:<Secret>] [--delete-chap=<User>:<Secret>]
[--require-allow=<Boolean>] [--add-initiator=<Initiator>]
[--delete-initiator=<Initiator>]
Options
--name=<TargetName>, -n=<TargetName>
Required. Specifies the name of the target to modify.
--comment=<QuotedString>
Specifies a description for the target, enclosed in quotation marks.
--path=<ifs-Directory>
Specifies a default path within /ifs for LUN directories.
--require-auth=<Boolean>
Enables (1) or disables (0) CHAP authentication. Chap authentication is disabled by default.
--require-allow=<Boolean>

2010 Isilon Systems, Inc.

79

isi target

Enables (1) or disables (0) initiator access control. Initiator access control is disabled by default.
--add-initiator=<Initiator>
Adds an initiator to the initiator access list. The specified value must be a valid iSCSI Qualified Name
(IQN).
--add-chap=<User>:<Secret>
Adds a CHAP user:secret pair to the CHAP secrets list.
Both the user and secret are case-sensitive. Secrets must be 12-16 characters long. You can specify a
valid IQN as the user. If you do not specify an IQN, valid users can contain alphanumeric characters,
periods (.), hyphens (-), and underscores (_).
--delete-initiator=<Initiator>
Removes an initiator from the initiator access list.
--delete-chap=<User>:<Secret>
Removes a CHAP user:secret pair from the CHAP secrets list.
--help, -h
Displays a list of supported options for this command.
Examples

To change the default LUN directory path to /ifs/example for a target named test1, run the following command:
isi target modify --name=test1 --path=/ifs/example
You can verify that the path was changed by running the following command:
isi target list test1
The system displays the target and its properties, similar to the following output:
Target : test1
Luns: 0
Comment:

Capacity:

Allowed Initiators: All


Default path: /ifs/example

Verify that the default path was updated.

To enable CHAP authentication for a target named test2, and add a CHAP user:secret pair of test:12characters to
the CHAP secrets list, run the following command:
isi target modify --name=test2 --require-auth=1 --add-chap=test:12characters
You can verify the changes by running the following command:
isi target list test2
The system displays the target and its properties, similar to the following output:
Target : test2
Luns: 0
Comment:

Capacity:

Allowed Initiators: All, +CHAP


Default path: /ifs/iscsi

The Allowed Initiators section displays +CHAP, which indicates that CHAP authentication is enabled.

80

2010 Isilon Systems, Inc.

isi target

isi target list


Displays configuration settings for iSCSI targets.
Syntax
isi target list [--name=<Target>] [--luns] [--verbose]
Options
If you run this command without options, the system displays a list of all targets.
--name=<Target>, -n=<Target>
Displays information for the specified target only.
--luns, -l
Displays information about each LUN in the specified target.
--verbose, -v
Displays more detailed information about the specified target.
--help, -h
Displays a list of supported options for this command.
Examples
To view detailed information about a target named test1, run the following command:
isi target list --name=test1 --verbose
To view information about all targets, and include more detailed LUN information, run the following command:
isi target list --luns

2010 Isilon Systems, Inc.

81

14
isi update

Updates a cluster to a newer version of the OneFS operating system.


After you run this command, the system displays the current status of each node.
Syntax
isi update [-d] [--rolling] [--manual] [--drain-time=<Duration>]
Options
-d
Prevents the system from performing chassis-connectivity checks on disk-only (storage expansion)
nodes.
--rolling
Enables rolling updates, which allow the cluster to remain available to clients during the update process.
In rolling update mode, the system reboots one node at a time. If a rolling update is interrupted before
the update is complete, you can run the update command to restart the rolling update. The update
system continues to update the cluster from the point at which the earlier update terminated. It will
not reload the image on any nodes on which an image has already been loaded, and it will do nothing
to any nodes that have already been updated.
Important: Rolling updates are not supported on all OneFS versions. Contact your Isilon
representative for information about the OneFS versions that support rolling updates.
--manual
Forces the rolling update process to pause and wait for user input before the system reboots each node.
--drain-time=<Duration>
Forces the update process to suspend a node from its SmartConnect pool, and then wait for clients to
disconnect or for the specified drain time to elapse before rebooting the node. By default, drain time
is specified in seconds. You can specify a different time unit by adding a letter to the end of the
command: m specifies minutes, h specifies hours, d specifies days, and w specifies weeks.
Examples
To update the cluster while preventing the system from performing chassis-connectivity checks on disk-only nodes, run the
following command:
isi update -d

83

isi update

The system displays a message indicating that the upgrade process has begun, similar to the following example output:
Starting upgrade process...
Connecting to remote and local upgrade processes...
Connecting to remote and local upgrade processes...
successfully connected to node [ 1].
successfully connected to node [ 2].
successfully connected to node [ 3].
Initiating IMDD...
node[ 1] initialized.
node[ 2] initialized.
node[ 3] initialized.
Loading image...
Please specify the image to update. You can specify the image from:
-- an absolute path (i.e. /usr/images/my.tar)
-- http (i.e. http://host/images/my.tar)
Please specify the image to update:
At the Please specify the image to update prompt, type the path to the upgrade image (for example,
/ifs/data/install.tar) and then press ENTER.
Note: The full path and the file name must be specified in order for the upgrade to proceed. This would be the actual
path to the install.tar file. Failure to include this information will result in an error message stating that the image
failed to load.
Also, all upgrade files should be unzipped. If you have downloaded zipped files for the upgrade, unzip them before
beginning this process.
The system displays text similar to the following output:
Image version: 5.5 RELEASE
Are you sure you wish to upgrade (yes/no [no])? yes Please wait,
updating...
Verifying md5...
Installing image...
node[ 1] installed.
node[ 2] installed.
node[ 3] installed.
Restoring user changes...
node[ 1] restored.
node[ 2] restored.
node[ 3] restored.
Successfully updated. Reboot (yes/no [yes])?
At the Reboot (yes/no [yes])? prompt, type y and then press ENTER.
The system displays a message similar to the following output as it reboots the cluster:
Rebooting cluster...
rebooting node[ 1]...
rebooting node[ 2]...
rebooting node[ 3]...
IsilonInc-1#
*** FINAL System shutdown message from root@bIsilonInc-1 ***
System going down IMMEDIATELY
Isilon first-pass shutdown: isi_mcp isi_dmilog isi_lcd_d isi_spy_d.
...

84

2010 Isilon Systems, Inc.