Helpful isi CLI commands

isi_radish –q (helpful for finding bay-to-twe mapping and drive serial numbers)
fs61-7# isi_radish -q
Bay 1/twed0 is Maxtor 7Y250P0 FW:YAR41BW0 SN:Y62VM7AE, 490234752 blks
Bay 2/twed1 is Maxtor 7Y250P0 FW:YAR41BW0 SN:Y62VN2ME, 490234752 blks
Bay 3/twed2 is Maxtor 7Y250P0 FW:YAR41BW0 SN:Y62WDAKE, 490234752 blks
Bay 4/twed3 is Maxtor 7Y250P0 FW:YAR41BW0 SN:Y62VMYEE, 490234752 blks
Bay 5/twed4 is Maxtor 7Y250P0 FW:YAR41BW0 SN:Y62X1J4E, 490234752 blks
Bay 6/twed5 is Maxtor 7Y250P0 FW:YAR41BW0 SN:Y62Y1BXE, 490234752 blks
Bay 7/twed6 is Maxtor 7Y250P0 FW:YAR41BW0 SN:Y62VN57E, 490234752 blks
Bay 8/twed7 is Maxtor 7Y250P0 FW:YAR41BW0 SN:Y62VN6CE, 490234752 blks
Bay 9/twed8 is Maxtor 7Y250P0 FW:YAR41BW0 SN:Y62VN8ME, 490234752 blks
isi stat –n # (helpful for finding which bay the dead drive is in)
jerryb@TSUPPORT2-2:~$ isi stat -n 4
Node ID: 4
Node Name: TSUPPORT2-4
Node IP Address: 172.16.0.222
Node Health: [ATTN]
Node Capacity 931GB
Available 874GB ( 6%)
Used 57GB ( 6%)
Disk Drive Status:
twed4 <2> Empty Empty
0 b/s [DOWN] [DOWN]
twed5 <1> twed2 <4> twed0 <6>
0 b/s 0 b/s 0 b/s
twed6 <0> twed3 <3> Empty
0 b/s 0 b/s [DOWN]
isi_drivenum (Also shows bay-to-twe mapping)
Intravision-2# isi_drivenum
Bay 1 Unit 0 Lnum 8 Active /dev/twed0
Bay 2 Unit 1 Lnum 7 Active /dev/twed1
Bay 3 Unit 2 Lnum 6 Active /dev/twed2
Bay 4 Unit 3 Lnum 5 Active /dev/twed3
Bay 5 Unit 4 Lnum 4 Active /dev/twed4
Bay 6 Unit 5 Lnum 3 Active /dev/twed5
Bay 7 Unit 6 Lnum 2 Active /dev/twed6
Bay 8 Unit 7 Lnum 1 Active /dev/twed7
Bay 9 Unit 8 Lnum 0 Active /dev/twed8
isi_net_info (helpful to ensure MTU is set correctly)
repfs01-2# isi_net_info
1500 bytes to 172.17.110.191 default mtu: 0% packet loss
1500 bytes to 172.17.110.191 real mtu: 0% packet loss
9000 bytes to 172.17.110.191 default mtu: 0% packet loss
9000 bytes to 172.17.110.191 real mtu: 0% packet loss
1500 bytes to 172.17.110.192 default mtu: 0% packet loss
1500 bytes to 172.17.110.192 real mtu: 0% packet loss
9000 bytes to 172.17.110.192 default mtu: 0% packet loss
9000 bytes to 172.17.110.192 real mtu: 0% packet loss
1500 bytes to 172.17.110.193 default mtu: 0% packet loss
1500 bytes to 172.17.110.193 real mtu: 0% packet loss
9000 bytes to 172.17.110.193 default mtu: 0% packet loss
9000 bytes to 172.17.110.193 real mtu: 0% packet loss
isi_hw_sane (NE in !"#"$" %hows &slow' drives" Available on ftp"isilon"com as
(outgoing(bin(isi)hw)sane")
Intravision-2# /root/isi_hw_sane
: total physical memory (3734417408 kB) looks okay
: isi_radish -F drive settings look okay
: drive speed (kB/s) 8kB read 8kB write 128kB read 128kB write
: bay 1 (A603SSZE) ok 39024:34000 35839:27000 39789:34000 40947:34000
: bay 2 (A603TA3E) ok 39797:34000 34749:27000 39730:34000 39723:34000
: bay 3 (A603SRPE) ok 39921:34000 34869:27000 40064:34000 40966:34000
: bay 4 (A603SWLE) ok 38932:34000 37609:27000 38944:34000 40125:34000
ERROR: bay 5 (Y60NK1FE) slow 40242:40000 46246:40000 54116:54000 62751:63000
: bay 6 (A603T5WE) ok 38732:34000 35812:27000 39934:34000 40619:34000
: bay 7 (A603SW9E) ok 38202:34000 35342:27000 39892:34000 40960:34000
: bay 8 (A603SW8E) ok 38978:34000 36890:27000 39559:34000 39915:34000
: bay 9 (A603SSBE) ok 39563:34000 36147:27000 39832:34000 38653:34000
----------
-- FAIL -- Saw 1 total hardware oddities
----------
isi_hwcheck (%how temps from the node" Note a *-$+ means there was no reading from
the probe" (usr(bin(isi)hwtools(isi)hwchec,)
Intravision-2# /usr/bin/isi_hwtools/isi_hwcheck
Chassis: 9-Bay (AIC 9-Bay Chassis)
Mobo: Force4201 (Force 4201 Motherboard)
NVRam: MM5415 (MicroMemory 5415 33MHz NVRam Card) (size 536870912B)
DskCtl: TWE7500-12 (3Ware 7500 12-port Controller) (12 ports)
IMB: Board Version 3
Power Supplies OK
CPU Operation (raw 0x0) = Normal
Fan 1 (MB Fan 0) = -1
Fan 2 (MB Fan 1) = -1
Fan 3 (F1) = 4643
Fan 4 (F2) = 4488
Fan 5 (F3) = 4691
Fan 6 (F4) = 4488
Voltage Vcc = 1.43
Voltage 3.3v = 3.30
Voltage 2.5v = 2.46
Voltage 5v = 4.91
Voltage 12v = 12.07
Voltage 5v (IMB) = 4.94
Voltage 12v (IMB) = 12.25
Temperature Management Chip = 30 Degrees C
Temperature Drives 1-6 (T1) = 23 Degrees C
Temperature Drives 7-9 (T2) = 22 Degrees C
Temperature PCI Riser Exhaust (T3) = 34 Degrees C
Temperature NIC area (T4) = 28 Degrees C
Temperature CPU Exhaust (T5) = 28 Degrees C
Temperature IMB = 25 Degrees C
Temperature CPU = 32 Degrees C
isi_for_array (E-ecutes a command on every node of the cluster" &man isi)for)array' is
really helpful" .ay particular attention to the /01 -l1 and /s flags")
root@TSUPPORT2-2:~$ isi_for_array -q uptime
Password:
TSUPPORT2-2: 10:13AM up 1 day, 21:28, 2 users, load averages: 0.02, 0.03, 0.01
TSUPPORT2-1: 10:13AM up 1 day, 21:28, 3 users, load averages: 0.21, 0.09, 0.02
TSUPPORT2-4: 10:13AM up 1 day, 21:28, 0 users, load averages: 0.01, 0.01, 0.00
isi_dmilog (%how the 234% 5M3 log" Note1 a .4%T error is normal" 3t means the
motherboard didn't detect a ,eyboard on boot" Also1 since the 2ios log is full1 no new
messages will be written" The log will have to be cleared before new messages will
be written")
Intravision-2# isi_dmilog
Current change-id: 245
Note: Bios event log is full.
Log:
04/29/04 20:57:10 POST error: 00000200 00000000
04/29/04 21:36:09 POST error: 00000200 00000000
04/29/04 21:58:27 POST error: 00000200 00000000
04/29/04 22:03:03 POST error: 00000200 00000000
04/30/04 17:41:02 POST error: 00000200 00000000
04/30/04 19:11:29 POST error: 00000200 00000000
05/03/04 21:20:42 POST error: 00000200 00000000
05/03/04 21:34:45 POST error: 00000200
00000000
05/03/04 22:30:58 POST error: 00000200 00000000
05/03/04 22:50:46 POST error: 00000200 00000000
05/04/04 16:31:50 POST error: 00000200 00000000
05/04/04 16:52:56 POST error: 00000200 00000000
Totals:
12 of POST error
isi_bug_info (ay too much output to show a sample here" Engineering will sometimes
as, for this output" 6ere's how to capture it")
isi_bug_info > /tmp/demo-1.bug_info
isi_dav_cp – 7opy utility that uses the dav protocol (http)" This is very
useful when ftp is not good enough"
usage8 dav)cp src$ 9src!""": targethost89targetport:(targetdir
-v8 verbose - print out what is happeneing at the file level"
-d8 debug - print out what is happening at the protocol level"
-u ;user<8 user - for authentication"
-p ;pass<8 password - for authentication"
isi_distill – The distill tool is used to capture the file and directory structure of a
customer's data" This tool is useful to understand file si=e usage" 3t can also be useful to
determine empirically the performance of the cluster given a specific file structure"
Usage: isi_distill [-hq] [-o outfile] path
Options:
-h Print this message.
-p Preserve file names.
-q Be quiet about errors.
-o <outfile> Redirect output to <outfile> instead of stdout.
isi_dumpjournal – This tool is mainly used for debugging purposes. As
the name implies it dumps the content of the format into stdout.
Usage: isi_dumpjournal [-v] [-f <journal file>]
-v: Show transaction resolution archive as well
-f: Specify partition containing log (default /dev/mnv0)
-h: Print usage
isi_fixjournal –
isi_flush / >lushes the content of cache to dis, (syncing to dis,)" This tool is useful when
trying to unmount the filesystem" Usually invo,ed by another script"
isi_get_itrace / Automated script for obtaining *itraces+" This script ta,es a # second
snapshot of performance information often re0uired to debug problems with the cluster" 3t
generates a "g= file that is saved by default on (ifs(itraces( directory"
isi)get)mbinfo / This script loads a debugging ",o to obtain mbuf information about a
node" 3t creates a "g= file that is saved by default on (ifs(itraces directory"
isi_restill / The restill tool is used to regenerate a file and directory structure using a distill
file" 3t can ta,e a /? argument that parelli=es the ?ob of restilling files thereby ma,ing the
process faster"
Usage: isi_restill [-hiq] [-j job#/#jobs] basepath
Options:
-h Print this message.
-i <infile> Input file.
-j job#/#jobs Only do work for job# out of #jobs.
-n Ignore protection and coalescer settings.
-q Be quiet about errors.
-v Print files and directories as they are created.
isi_save_journal / This tools automates the process of saving the contents of the ?ournal to
the (var(crash( partition" This is one of the utilities used in the *dis, tango+ process"
isi_restore_journal / The restore)?ournal tool is used to recover a saved ?ournal from the (
var(crash partition to the N@AAM"
isi_reimage / The isi)reimage tool installs a specified version of 4ne>% to a cluster or
node without preserving any of the cluster data" The reimage tool by default attempts to
mount buildbio-" Typing &ls' at the prompt shows the images available for installation"
usage: isi_reimage [-mfh] [-b build]
-f: force to reimage without confirmatiom
-m: to reimage all the alive nodes on cluster
-i: ignore md5 checking after install
-h: help
-b build: to reimage with the build
isi_update - The isi)reimage tool installs a specified version of 4ne>% to a cluster or node
while preserving all of the cluster data" Unli,e isi update1 the tool by default attempts to
mount buildbio-" Typing &ls' at the prompt shows the images available for upgrade
installation"
isi_kill_busy / The ,ill)busy tool attempts to ,ill any services that can cause prevent the
(ifs partition from being unmounted cleanly (filesystem is busy)" This tool should only be
used when attempting to unmount the filesystem"
isi alerts
The isi alerts command provides access to active and historical alerts on the
cluster, and the ability to quiet, unquiet, or cancel any active alerts. To perform
one of the actions, specify the command followed by one or more alert ids or all.
>>> isi alerts [-w] [args [...]]
The isi alerts command with no argument appended returns a list of all currently
active alerts, with their ids, time of occurrence, severity, quiet status, and
message. If history is specified, then historical alerts are listed.
The -w argument specifies a wide view, to see all aspects of the alerts.
Alerts may be quieted if periodic notifications are no longer desired, or unquieted
to resume notifications. Alerts will be automatically cancelled after a period of time
if the condition no longer persists, or they may be cancelled explicitly by the user
(not recommended.
isi config
!hen a user executes isi config at the command line, the system opens a subset
of configuration commands directed at managing configuration settings. The isi
config command brings the user to an interactive configuration system where
various node and cluster settings may be altered.
NOTE!hile Isilon I" is in the isi config subsystem, the other Isilon I" commands
are unavailable.
>>> help
The help command lists all of the commands available in the current Isilon I" #$I
context.
>>> help <Isilon IQ command>
The user can append the help command with another Isilon I" command to get
details on how the specified command operates.
>>> close
The close command disconnects the user from the current isi_config session.
>>> config
The config command commits the latest configuration settings to the system.
>>> date [ < mm/dd/yyyy HH:mm:ss > ]
The date command sets the date and time the cluster uses for time%date
stamping.
If the user executes the date command with no arguments, it displays the current
system date and time. &r the user can set a new date and time using two-digit
month ('(-() and day ('(-*(, and a four-digit year, and then a space to
separate the time using )+-hour format for hour values (''-)* and two-digit
values for minutes and seconds (''-,'.

>>> dns [primary <IP> secondary <IP> domain <domain>] ...
The dns command, when executed with no argument, displays the -./
information the cluster currently uses0
>>> dns
Primary DNS server is set to 172.16.0.1.
The secondary DNS server is not set.
The DNS domain is set to isilon.com.
>>> dns primary <IP>
-esignates the I1 address to use for the primary -./ server.
>>> dns secondary <IP>
-esignates the I1 address to use for the secondary -./ server.
>>> dns domain <IP>
-esignates the domain name to use.
>>> dns delete [primary | secondary | domain]
The dns delete command deletes all -./ information if used without any other
argument. If delete is followed by primary, secondary or domain, only that
information is deleted.

>>> e!it
The exit command disconnects the user from the current isi_config session.

>>> iprange [<interface-name> [<lowest IP>-<highest IP>]]
The iprange command displays a list of ranges of I1 addresses currently
assignable to
nodes, when executed with no argument. It designates I1 addresses assignable to
nodes, when appended with a range of I1 addresses.
>>> list [cl"sters "nconfig"red]
The list command displays a list of clusters on the same subnet as the node
executing the command, when appended with the 2clusters2 argument.
It displays a list of unconfigured nodes on the same subnet as the node executing
the command, when appended with the 2unconfigured2 argument.
!hen executed with no argument, it displays both lists.
The add and join commands use the list command.
>>> add < #$% address list position >
The add command attempts to export the configuration settings from the cluster
executing the command to an unconfigured node on the same subnet, thus ma3ing
it part of the cluster. The node is specified in the argument by its 4A# address, or
by the number corresponding to its position in the list of unconfigured nodes
(obtained by executing the 2list unconfigured2 command. 4ultiple machines can be
added simultaneously.
>>> &oin < name list position > '<password>(
The join command attempts to 5oin a node to a cluster, specified by its name or by
the number that corresponds to its position in the list of clusters (see list.
>>> &oinmode [ mode ]
The joinmode command determines how the system will behave when new Isilon
I" nodes come online on the subnet occupied by the Isilon I" cluster0
The manual argument configures the system to 5oin new nodes into the cluster in
a separate manual process (see 5oin and add. This is the default 5oin mode
setting.
The secure argument configures the cluster to disallow any new node from 5oining
the cluster externally. It also ma3es some other aspects of operation more secure.
>>> migrate [ <interface-name> [<old IP range>] <new IP
range>]
The migrate command displays a list of ranges of I1 addresses currently
assignable to nodes, when executed with no argument. It migrates all nodes that
are assigned addresses in the old range of I1 addresses over to addresses in the
new range of I1 addresses. If the old range is not given, all nodes in the cluster are
migrated to addresses in the new range.
>>> remo)e [<node id> all]
The remove command deletes a node from the cluster, as specified by its node I-.
If no argument specifying a node is appended, remove will act upon the node that
is running the current isi6config session.
If the 2all2 argument is appended, it removes all cluster nodes. In all cases, the
system returns a confirmation prompt before executing the command.
&nce executed, any removed node will reboot and return to its unconfigured state
with all data removed.
The system returns a warning prompt, as3ing the user to confirm execution0
DANGER Resettin! device 2 mi!ht ca"se data loss i# there are
#iles on that
device $hich are not on any other device.
Are yo" s"re yo" $ish to contin"e% &no'
((( ) yes * no (
The default entry at this prompt is 7no89 so if the user presses Enter without
typing a response, remove will not execute.
>>> deliprange [<interface-name> lowest IP - highest IP ]
The deliprange command removes the I1 addresses in the range specified in the
argument from the list of I1 addresses reserved for use in the particular named
interface.
If deliprange is executed with no arguments, the system will return a list of I1
ranges reserved for assignment to Isilon I" nodes
If an address in the range specified to be deleted is currently assigned to an Isilon
I" node, the system will return an error message0
((( deli+ran!e Primary 172.16.20.,1-172.16.20.,,

.P /172.16.20.,1/ is in "se and may not 0e deleted
!hen the system has successfully executed the deliprange command, it returns a
confirmation message0
Removed .P ran!e Primary 172.16.20.,1-172.16.20.,,.
>>> interface [<interface-name> [ena*ledisa*le]]
The interface command displays the I1 ranges, netmas3 and 4T: of all networ3
interfaces when issued with no argument. It displays the I1 ranges, netmas3 and
4T: of the given interface when issued with a networ3 interface name argument.
It enables or disables the given networ3 interface when issued with the enable or
disable argument.
>>> name < name >
The name command displays the name currently assigned to the Isilon I" cluster,
when executed with no argument. It sets the name of the cluster, when appended
with a name. The name will appear in the list of masters and should be used if the
cluster is named on a -./ server.
>>> netmas+ [<interface-name> [<!.!.!.!>]]
The netmask command displays the subnet I1 mas3 that the named interface is
currently using, when executed with no argument. It sets the subnet I1 mas3 that
the named interface will use, when appended by a valid subnet I1 mas3.
>>> gateway [<IP address> delete]
The gateway command displays the I1 address of the gateway machine the
cluster users to communicate with systems external to its ;thernet subnet, when
executed with no argument. -esignates the gateway machine the cluster uses to
communicate with systems external to its ;thernet subnet, when appended with
the I1 address of the gateway machine. <emoves the gateway machine the cluster
currently uses, when appended with the 2delete2 argument.
>>> mt" [<interface-name> [<)al"e>mi!ed]]
The mtu command displays the si=e of the 4aximum Transmission :nit (4T: the
named interface uses in networ3 communications, when executed with no
argument. /ets the si=e of the 4T: the named interface uses, when appended with
a value. #ommon settings are (>'' (standard frames, ?''' (5umbo frames, and
4ixed ((>'' external, ?''' internal.
It is highly recommended that users configure the networ3 interface used for
internal communications for @umbo Arames. @umbo Arames enable the Isilon I"
cluster to more efficiently communicate to all storage nodes within the cluster,
improving read and write performance up to *' percent.
NOTE#hanges to the 4T: setting will not be applied until the nodes are rebooted.
>>> ,"it
The quit command disconnects the user from the current isi_config session.
>>> re*oot [<node id> all]
The reboot command reboots the node from which the command is executed,
when executed with no argument. <eboots a specified node, when appended with a
node2s I-. <eboots all cluster nodes, when appended with the 2all2 argument.
>>> redisco)er
The rediscover command attempts to reacquire Isilon I" nodes on the networ3 by
rebroadcasting discover pac3ets.
>>> stat"s [ ad)anced ]
The status command returns the current configuration of the cluster.
!ith the advanced argument appended, stat"s gives additional configuration
details, such as the 4aster .ode I- and the $ocal ifsd 1I-.
>>> time-one [<time-one identifier>]
The timeone command sets the time=one on the cluster to the specified
time=one. Balid time=one identifiers are0 C4T, Creenwich 4ean Time, ;astern,
;astern Time Done, #entral, #entral Time Done, 4ountain, 4ountain Time Done,
1acific, 1acific Time Done, Ari=ona, Alas3a, Eawaii.
>>> )irtip [adddelete [<ip address>]]
The virtip command displays the configured virtual I1 address when issued with no
argument. Adds a new I1 address to the list of configured virtual I1 addresses
when appended with 2add2 and an I1 address. <emoves an existing I1 address from
the list of configured virtual I1 addresses when appended with 2delete2 and an I1
address.
>>> )ersion
The version command displays product version information.
>>> wi-ard
The wiard command puts the user into a scripted series of commands that
manipulate the basic configuration settings.
isi get
The isi get command displays the the properties of the files and directories stored
in the Isilon I" cluster, including their policy, protection level, and caching level. It
also contains color coded status information.
>>> isi get [-ad./] file
.silon-12 isi !et 33i#s3test
P45.67 5E8E5 64A5 9.5E
:1 1:1 on 1!
:1 2; on 6o+y o# dash3
2; 2; on dash3
!a!hen appended with the -a flag, the isi !et command is used to include the
hidden F.2 and F..2 entries of each directory and so displays the directory properties
as well as the file properties.
!d!hen appended with the -d flag, the isi !et command is used to view the
attributes of a directory itself rather than its contents and displays directories as
plain files.
!"!hen appended with the -- flag, the isi !et command is used for more
verbose information for debugging purposes and displays the data bloc3 IA--</
where the data is located on the dis3.
!#!hen appended with the -< flag, the isi !et command is used to descend into
a directory recursively and displays the properties of the directory specified in the
path and any files and directories it contains.
At any level of output, the protection policy appears in one of three colors0 green,
yellow, or red. The color indicates the protection status of the file, with green
corresponding full protection, yellow corresponding to a degraded protection under
a mirroring policy, and red corresponding to a loss of one or more data bloc3s
under a parity policy.
4ore succinctly, yellow indicates that a file Gneeds reprotectG, while red indicates
that it Gneeds repairG.
isi services
The isi services command controls the enabling or disabling of the various 3inds of
services that are available in the Isilon environment, including .T1, smbtime, .I/,
.A/, Telnet, //h, ETT1, /amba, AT1, and two Isilon utilities, isi spy and isi
restripe.
>>> isi ser)ices [-la] [ser)ice [<ena*ledisa*le>]]
The isi services command with no argument appended returns a list of the
activation status of each service0
Availa0le Services
nt+d Net$or< Time Server Ena0led
sm0time =indo$s Time Service Ena0led
n#s N9S Server Ena0led
nis Net$or< .n#ormation Service Ena0led
telnetd Telnet Server Ena0led
sshd Sec"re Shell Server Ena0led
htt+d =e0 Server Ena0led
sam0a =indo$s Share >S?@A Server Ena0led
isiBs+yBd .silon S+y Daemon Ena0led
#t+ 9TP server Disa0led
isiBrestri+eBd .silon Restri+e Daemon Ena0led

If the isi services command is used with the enable argument, the service will be
turned on.
>>> isi ser)ices ftp ena*le

If the isi services command is used with the disable argument, the service will be
turned off.
>>> isi ser)ices ftp disa*le

!l!hen appended with the -l flag, the isi serv command will display all services
that the user may change, along with a short description and their state.

!a!hen appended with the -a flag, the services list will be augmented to include all
services and their current status, even those that the user cannot change.

isi set
The isi set command controls the protection policy settings on files and folders in
the Isilon I" file system. There are several ways a protection policy can be set on a
file0
• a policy can be set explicitly on files
• a policy can be inherited from a parent folder (i
• a policy on a folder can be forced upon the contents of that folder,
overriding the settings already in place.
>>>isi set [-fnr)/] [-p policy] [-c <onoff>] file
Protection Policy
To set a protection policy explicitly on a particular file, execute the isi set
command appended with the Hp flag followed directly with a protection policy, and
then the path to the file on which you want to set the policy, as in the following
example0
)cl"ster name(2 isi set -p< policy > <file path>
&r, more specifically0
)cl"ster name(2 isi set –p[ i | <n>x | <n>+1 ] <file path>
!here the policy options act in the following ways0
• The i argument configures the file to inherit its protection policy from the
nearest parent folder that has an explicitly set policy. The i setting is the
implicit state.
• The $n%x argument configures the file system to mirror the file n times,
where n cannot exceed the number of nodes in the cluster.
• The $n%&' argument configures the file system to stripe the file n
times with parity protection.
Aor example, the following command would protect the designated file with twice-
over mirroring0
)cl"ster name(2 isi set –p2x //ifs/song.mp3
Write-Coalescing Policy
!rite-coalescing may be set to either on or off , and is specified with the -c flag.
Iy default, only the files specified on the command-line are modified, as in the
following example0
)cl"ster name(2 isi set -c on <file path>
Scope
The file upon which the protection policy acts can be further defined by prepending
the file path with one of the following scope operators%delimiters0
)cl"ster name(2 isi set [-fnr!] –p<policy> <file path>
!here the scope options act in the following ways0
• The !f argument may be specified to suppress warnings on failures to
change a file.
• The !n argument outputs the list of files that would be changed without
actually ta3ing any action.
• The !r argument explicitly forces a restripe. It relaxes the requirement
that a change be performed, and restripes each file regardless of whether
this would have occurred otherwise.
• The !v argument causes set to list each file as it is reached.
• The !# argument recursively sets the protection on files.

Summary
In its entirety, the isi set command ta3es this form0
isi set [-fnr!] [-p policy] [-c <on|off>] file
isi status [-qwD] [-n [ID]]
!hen a user executes isi status at the command line of any node in an Isilon I"
cluster, the user can get a snapshot of the system2s current state.
The isi status command returns real-time information about the status of the
cluster, including data on the health, capacity, space available, detailed throughput
data, and operations whether finished, active, waiting, or failed. The #luster Eealth
and .ode Eealth status indicators are color coded, with green indicating healthy,
red indicating offline, and yellow indicating attention needed.

6l"ster Name .silon
6l"ster Cealth & 4D '
6l"ster 6a+acity E.2T@
Availa0le E.2T@ >100FA
Gsed 6.HG@ > 0FA
Thro"!h+"t >0its3sA
.D * .P Address * Cealth * .n 4"t Total * Gsed 3
Total
----:-----------------:--------:-------:-------:-------
:------------------------
1 * 172.16.0.1H1 * & 4D ' * 0 * 0 * 0 * 2.1G@ 3
1.ET@ > 0FA
2 * 172.16.0.1H2 * & 4D ' * 0 * 0 * 0 * 2.1G@ 3
1.ET@ > 0FA
H * 172.16.0.1HH * & 4D ' * 0 * 0 * 0 * 2.1G@ 3
1.ET@ > 0FA

9inished 4+erations >2A
4PERAT.4N START 64?P5ETE E5APSED ERR4RS
A"to@alance 12301 1721 12301 1721 000001 0
6ollect 12301 1721 12301 1721 00000H 0
No active o+erations.
No $aitin! o+erations.
No #ailed o+erations.

The isi status !q flag (GquietG output is used to return the cluster status without
information on operations.
The isi status !w flag (GwideG output specifies that no truncation of operations
status should ta3e place.
The isi status !n flag (GnodeG output returns information about each node in the
cluster. Iy using this command a user can quic3ly tell which nodes and%or dis3s
are up and down, as in the following example0
isi stat -n
Node .D 1
Node Name .silon-1
Node .P Address 172.16.0.1H1
Node SN
Node Cealth & 4D '
Node 6a+acity 1.ET@
Availa0le 1.ET@ > 0FA
Gsed E6,?@ > 0FA
Net$or< Stat"s
Prim 3 0c0
172.16.0.1H1
26D 3 1.ED
Dis< Drive Stat"s
t$ed1 )2( t$ed2 )1( ad0 )I(
0 03s 1HD03s 1HD03s
t$ed6 )1( t$edH )E( t$ed0 )7(
0 03s 0 03s 1HD03s
t$ed7 )0( t$edE )H( t$ed1 )6(
1HD03s 0 03s 0 03s
Node .D 2
Node Name .silon-2
Node .P Address 172.16.0.1H2
Node SN
Node Cealth & 4D '
Node 6a+acity 1.ET@
Availa0le 1.ET@ > 0FA
Gsed E6I?@ > 0FA
Net$or< Stat"s
Prim 3 0c0
172.16.0.1H2
27D 3 1.1D
Dis< Drive Stat"s
t$ed1 )2( t$ed2 )1( ad0 )I(
1.6D03s E1D03s 1.6D03s
t$ed6 )1( t$edH )E( t$ed0 )7(
E1D03s E1D03s 1.6D03s
t$ed7 )0( t$edE )H( t$ed1 )6(
1.6D03s E1D03s 1.6D03s
Node .D H
Node Name .silon-H
Node .P Address 172.16.0.1HH
Node SN
Node Cealth &ATTN'
Node 6a+acity 1.2T@
Availa0le 1.2T@ > 0FA
Gsed E1E?@ > 0FA
Net$or< Stat"s
Prim 3 0c0
172.16.0.1HH
HED 3 E.7D
Dis< Drive Stat"s
t$ed1 )1( t$ed2 )E( ad0 )7(
0 03s 0 03s 1HD03s
Em+ty t$edH )H( t$ed0 )6(
&D4=N' 0 03s 0 03s
t$ed6 )0( t$edE )2( t$ed1 )1(
1HD03s 1HD03s 1HD03s
(rocedure ! )oftfail
$) /oft Aail the drive. This is what would occur in 99% of the cases
of a drive falling out of the acceptable Isilon specifications and
needing to be removed before a hard failure of the drive.
a. Arom the command line type the following0
i" JJ isi conf
b. Arom within the isi configuration menu display the help
mode for softfail.
i" JJJ softfail help
:n3nown option0 help
usage0 softfail -q Knode-drive-specJ 0 "uery current
soft-fail status.
softfail -s Knode-drive-specJ 0 /et soft-fail flag.
Knode-drive-specJ 00L KnodeJ 7 G0G 7 KdriveJ 8 8
00L 7 KnodeJ 8 G0G KdriveJ
KnodeJ 00L KnumberJ
KdriveJ 00L GlnumG KnumberJ
00L GbayG KnumberJ
00L GportG KnumberJ
00L GtwedG KnumberJ
00L GunitG KnumberJ
KnumberJ 00L 7'-?8M
c. :se the help menu as your syntax guide select the
appropriate node, and drive you wish to softfail.
/ome notes about this procedure0
$) This will put the selected drive into softfail mode as would the
&/ or Isilon #ustomer /ervice determined the drive was no
longer acceptable to be part of the overall cluster. The system
will begin a restripe of the contents on this drive and re-stripe
the contents to other drives in the cluster. &nce the restripe is
complete the drive is then logically removed the system.
1lease note0 during this restripe the drive can still be read
from, but is no longer available for writes.
) <epeat the procedure for another drive if you have .M) set for
the entire system as you have planned.