Professional Documents
Culture Documents
Docu43579 - OneFS 6.0 Command Refe
Docu43579 - OneFS 6.0 Command Refe
Docu43579 - OneFS 6.0 Command Refe
July 2010
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
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.
[]
<>
{}
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
Good, charging
10
Good, charging
11
12
Good, charging
13
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
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:
--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
smartfail
Node or
drive
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
confirm
Node or
drive
format
Drive
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
isi devices
--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
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
(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]
14
4
isi iscsi
Displays information about current iSCSI sessions or configures the Internet Storage Name Service (iSNS). This command
requires a sub-command.
15
isi iscsi
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
16
isi iscsi
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.
17
5
isi job
Manages jobs, job policies, and job schedules. This command requires a sub-command.
OneFS includes the following jobs:
To display the enabled/disabled state, associated job policy, and description for each job, run the following command:
isi job list
19
isi job
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.
20
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
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.
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
isi job
Elapsed time:
LINs deleted:
Snapshots deleted:
Errors:
06/18 10:10:38 SnapshotDelete[13]
0 seconds
36/36
1/1
0
Succeeded
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.
23
isi job
Job
-------------------------FSAnalyze[13]
FSAnalyze[13]
FSAnalyze[13]
FSAnalyze[13]
Event
-----------------------------Waiting
Running
phase 1 fsa begin
User Paused
24
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.
Job
-------------------------FSAnalyze[10]
FSAnalyze[10]
FSAnalyze[10]
FSAnalyze[10]
FSAnalyze[10]
FSAnalyze[10]
Event
-----------------------------Waiting
Running
phase 1 fsa begin
System Paused
Waiting
Running
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
You can create and modify custom impact policies, or you can use one of the following pre-defined impact policies:
26
isi job
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.
27
isi job
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.
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
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:
--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
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.
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
30
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:
<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"
31
isi job
32
6
isi lun
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
34
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:2 without displaying a confirmation message, run the following command:
isi lun delete --name=mytarget:2 --force
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
36
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/
37
isi lun
38
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
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
7
isi ndmp
Manages Network Data Management Protocol (NDMP) configuration settings, users, and sessions. This command requires a
sub-command.
41
isi ndmp
The system displays the port number, similar to the following example output:
Setting
Value
-----------------------------------port
10000
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
isi ndmp
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
44
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.
10.20.29.17
08-13-09 03:38:28
00d 02:48:15
IDLE
Throughput (MB/s)
0.000
Tape Device
tape041
Mode
Read/Write
IDLE
45
isi ndmp
46
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:
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
8
isi networks
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.
50
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:
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.
51
isi networks
52
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.
53
isi networks
54
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
55
isi networks
56
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.
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
58
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
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
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
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:
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.
62
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.
63
9
isi pkg
Distributes and manages hot fixes, service updates, and new applications on a cluster. This command requires a sub-command.
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.
66
isi pkg
If the patch is not installed, the system displays the following output:
patch-example.tar
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
69
isi services
70
11
isi smartpools
Manages the application of the SmartPools file pool policy. This command requires a sub-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)
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%)
isi status
Network Status:
Internal:
External:
Bay 6 <7>
1.4Mb/s
[HEALTHY]
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)
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
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:
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
78
isi target
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)
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:
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:
The Allowed Initiators section displays +CHAP, which indicates that CHAP authentication is enabled.
80
isi target
81
14
isi update
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