AWS - Listing users who have not enabled MFA for thier AWS account

Welcome Back!

Well, It's been years since I wrote my last blog.. Life is busy but there is nothing to complain about, as they say - Love the life you live and live the life you love!

Coming back to the topic; today's topic is about a task which I was trying to do since last couple of days..

Task was simple  - List the users who haven't enabled MFA for their AWS account. But integrating boto3 framework with Lambda was the trick.. Hence, thought of sharing the piece of code that I wrote for this task.

Note: You may run this with normal python IDE as well but that will require the AWS credentials.

I hope you will find it useful.

Python code for Lambda function:

##########################

import boto3


def lambda_handler(event, context):
    client = boto3.client('iam')
    users = client.list_users()

    user_list = []
    virutal_enabled =[]


    for key in users['Users']:
        user_list.append(str(key['UserName']))


    for key in users['Users']:
        List_of_MFA_Devices = client.list_mfa_devices(UserName=key['UserName'])
        for key in List_of_MFA_Devices['MFADevices']:
        virutal_enabled.append(str(key['UserName']))
     
    diff_list = [item for item in user_list if not item in virutal_enabled]

    for p in diff_list: print (p)

Procedure: Mount S3 Bucket on AWS EC2 Instance

A quick handy how-to:

How to mount S3 bucket on EC2 instance of AWS

S3FS is the S3 file system that will be required here.

Firstly update the packages on Ubuntu machine

Step 1:

# sudo apt-get install build-essential git libfuse-dev libcurl4-openssl-dev libxml2-dev mime-support automake libtool
# sudo apt-get install pkg-config libssl-dev
# git clone https://github.com/s3fs-fuse/s3fs-fuse
# cd s3fs-fuse/
# ./autogen.sh
# ./configure --prefix=/usr --with-openssl
# make
# sudo make install

Step 2:

S3FS needs AWS access key id and secret key to work. Create "passwd-s3fs" file at /etc/passwd-s3fs with content

<AWS Access Key ID>:<AWS Secret Access Key>

Step 3: Change permission

# chmod 640 /etc/passwd-s3fs

Step 4: Create mountpoint:

# mkdir <mount_point>

Step 5: Now mount the s3 bucket

# sudo s3fs bucketname /mys3bucket

Step 6: To check mounted s3 bucket

# df -Th /mys3bucket

# mkdir /mys3bucket

In most cases, you will want S3 to be mounted automatically after each reboot. So, add below line to /etc/fstab

# s3fs#<buket_name> /mys3bucket fuse allow_other,use_cache=/tmp/cache 0 0

For istance: s3fs#jarvis.pc /mys3bucket fuse allow_other,use_cache=/tmp/cache 0 0

Isilon API

Welcome to the world of API!  

It took a  evening to configure a ISILON sdk on ubuntu and bringing up a two node cluster on VMware workstation; but it is worth doing it. 

Need to spend more time with it.

#api #python #isilon

Isilon OneFS upgrade to 7.2.1.0

It's the time.. Time to UPGRADE

I recently performed a OneFS upgrade to 7.2.1. The entire process is categorized in three phase and below are the steps:

Pre-upgrade tasks:

Use the below commands and do the overall health check of the cluster

• isi status -D
•  isi_for_array -s 'isi devices | grep -v HEALTHY'
•  isi_for_array -s 'gmirror status'
•  In the OneFS web administration interface, click Dashboard > Cluster Overview > Cluster Status.In the Status area, click the ID of a node.In the Chassis and drive status area, click Platform
•  isi_for_array -s 'df -h'  - Check the utilization of all file system and confirm that it is below 90%
•  isi events list

Back up data.
• Backup all important data like corn jobs, etc.
• Ensure synciq jobs completed sucessfully

Collect cluster status.
isi status -D -w

Complete system jobs.
• isi services -a isi_job_d disable

Pause or cancel SyncIQ jobs.
• isi sync policy list -v
• isi sync jobs list"
• isi sync jobs pause --all

Cancel all running jobs:  
Use command (isi job jobs list) to view any running jobs, use command ( isi job jobs cancel JobIDNumber) to cancel by ID number

Implementation plan

Check the upgrade image:

# isi update --check-only
when asked to specify  the image to update then provide the path where the OneFS image is stored.

Check if you have any job running

# isi job jobs list

Flush the cache 

# isi_for_array isi_flush

Perform the upgrade

# isi update

when asked to specify  the image to update then provide the path where the OneFS image is stored.

Are you sure you wish to upgrade (yes/no)? yes

Reboot to complete the process? (Yes/No) Yes

Now system run the upgrade process and you may need to reconnect to the cluster

Check the version

# isi version

Check the events

# isi event list -w

Install the patch if required/needed

Change to the directory where the patch image is stored

# cd <path>

# isi pkg install <file name>

Some times few drives may need firmware upgarde, run below command to do the same

# isi_disk_firmware_reboot -p

Check the services and enable if you have disabled it before performing the upgrade

# isi services -a supportiq enable
# isi services -a nfs enable
# isi services -a smb enable

Cancel all the events

#isi events cancel all

Gather the info and gave it to EMC for review

# isi_gather_info


Happy Learning!

Isilon Drive firmware upgrade

And i love this photo :-D


Well i recently performed a Drive firmware upgrade for one of our Isilon cluster and below are the steps.

Procedure for Isilon Drive Firmware Upgrade:

1. Download the package from support.emc.com link

2. Copy the package to Install directory of the cluster, example:

<cluster>:/ifs/data/2015/upgrade/software

3. Disable the notifications:

a.  isi services -a celog_notification disable

b.  isi services -a supportiq disable

4. Install the package (once per cluster)
       Command: isi pkg install /ifs/data/2015/upgrade/software/<package_name.tar>

5. Flush the cache and reboot each node; normally prefer doing it in a bottom-up fashion

a.     Run  isi_flush step prior rebooting each node.

b.     After this comand runs, it will reboot the node.

                                                   i.   isi_disk_firmware_reboot –p

6. After the node comes back online, verify the firmware status on that node

                  i. isi devices

                 ii. isi_disk_firmware_reboot -p

Note: if all drives have been updated then the message "no disks needs firmware update" will be displayed

7. Repeat step 5 & 6 for the rest of the nodes in the cluster

8. Clear the alerts with command

a.  isi events quiet all

b.     isi events cancel all

9.  Enable the notifications with commands:

a.  isi services -a celog_notification enable

b.     isi services -a supportiq enable     

Happy Learning!

SyncIQ Failover and Failback

SyncIq automated data failover & failback provides the high availability to OneFS which means in the event that a primary culster becomes unavailable, SyncIQ provides the ability to failover to a mirrored, DR cluster with minimal interruption.

Please note that: SyncIQ follows asynchronous replication not synchronous.

Below are the steps that needs to be executed for Isilon SyncIQ failover and failback; this can also be used for DR testing.

To initiate failover:

1) Set the target cluster as read-write

# isi sync recovery allow-write <policy_name>

Failback can be accomplished if the policy meets the following criteria:

1) source directory is not a smartlock directory

2) The policy has been failed over

3) The policy is a Sync Policy and not a copy policy

Steps in failback:

1) Resync-prep on the policy

# isi sync recovery resync-prep <policy_name>

2) Run a typical job on the mirror policy, a final failback differential sync is preformed:

# isi sync job start <policy_name_mirror>

3) Change the mirror local target to allow writes

# isi sync recovery allow-write <policy_name_mirror>

4) Run Resync-prep again on the mirror policy

# isi sync recovery resync-prep <policy_name_mirror>

5) Delete the mirror policy

# isi sync policies delete <policy_name_mirror>

Also read Isilon SyncIQ

Happy Learning!

Object Storage for dummies

Cisco Vs Broacde SAN Switch

Bottleneck detection best practices

Cisco UCS Boot from SAN config

Shutdown procedure of Isilon cluster via CLI

Below is the process of shutting down the EMC Isilon cluster via CLI

Step 1: Ensure there is no read/write operation on the cluster. You can do this by checking the smb/nfs sessions and ask the user to close the session:

# isi smb sessions list
# isi nfs nlm locks list


Step 2: Check the status of the client facing protocols running on the cluster and disable them:

# isi services apache2
# isi services isi_hdfs_d
# isi services isi_iscsi_d
# isi services ndmpd
# isi services nfs
# isi services smb
# isi services vsftpd

Now disable the services that are running

# isi services -a <service name> disable

Step 3: Flush the node journal to file system

# isi_for_array -s isi_flush

Note: Run the command once again if any node fails to flush the journal.

Step 4: Shutdown each on sequentially and don't run 'isi_for_array shutdown -p'

a) Connect to node and run command

# isi config
>> shutdown

Watch the console and ensure that the node is shutdown properly

Not: If you wish to shutdown all nodes simultaneously then run command:

# isi config
>>> shutdown all

Step 5: Once you power up the nodes, run the below command to check the status:

# isi status -q

Step 6: Enable all the services that you disabled in step 2

isi services apache2 enable
isi services isi_hdfs_d enable
isi services isi_iscsi_d enable
isi services ndmpd enable
isi services nfs enable
isi services smb enable
isi services vsftpd enable

Step 7: Verify client are able to connect to cluster and able to perform operation as usually.


Happy Learning!

XtremIO Theory of Operation

Below is the theory of operation for XtremIO. I'll try to cover as much ground as i can and while keeping things simple.

As we know XtremIO is an all flash array, based on scale-out architecture. The system's building block is X-Brick, which can be clustered together to grow the array.

Each X-Brick consist of:

a) 1 DAE (disk array enclosure); containing 25 SSDs, 2 PSUs, 2 SAS redundant module interconnect.

b) 1 Battery backup unit (BBU)

c) 2 Storage controllers. Each controller has 2 PSUs, 2 Eight Gb/s FC ports, Two 10GbE isci ports, Two 40 Gb/s Infiniband ports, One 1 Gb/s management port.

Note: If its a single brick cluster then you may need a additional BBU for redundancy.

The system operation is controlled via stand-alone dedicated Linux-based server called XtremIO Management Server (XMS). One XMS can manage only one cluster. Array continues operating if XMS is disconnected but can't be monitored or configured. XMS can be either be a virtual or physical server. It communicates with each storage controller in X-Brick via management LAN. XMS enables array administrator to manage array via GUI or CLI.

XtremIO Operating System:

XtremIO runs on a Open Source Linux distribution as a base platform and on top which runs XIOS. OS manages the functional modules, RDMA functions over InfiniBand (IB) between all storage controllers in the cluster.

 XIOS handles all activities in storage controller. There are 6 software modules that are responsible for all system functions.

1) I/O modules R, C & D that are used for routing, control and data placement throughout the array.

Routing Module: It translate all SCSI commands into internal XtremIO commands. It is also responsible for breaking incoming I/O into 4K chunk and calculate data hash value.

Control Module: This module contains the address to hash mapping table (A2H).

Data Module: This module contains Hash to Physical (H2P) SSD address mapping. It is also responsible for maintaining data protection (XDP).

2) Platform Module: Each storage controller has PM to manage the hardware and system process; it also restart system process if required. PM also clustering agent that manages the entire cluster.

3) Management Module: Each Storage Controller has one management module running on it; in a active/passive way. If one SC fails then MM starts on the other SC of X-Brick. If both SC fails then the system will halt.

Below picture depicts the module communication flow-chart:

Write Operation:

When host writes a I/O to array. 

1) It is picked up by R Module, which breaks it into 4K chunks and calculate the corresponding hash value. 

2) C Module stores the hash value 

3) D module updates the physical address information in its mapping table before storing it at physical SSD. 

4) System sends the acknowledgement back to host.

Below picture depicts the normal Write I/O operation.

Write operation of duplicated I/O:

Read Operation:

Whenever a read I/O is issued to array:

1) System analyse each request to determine the LBA (logical block address) for each data block. This logical block address is stored C Module.

2) C module do a look up for Hash value stored in D module. 

3) D module returns the relevant Physical SSD address to the Host.

Below picture depict the read operation:

Also read array-administration and xtremio-architecture

Happy Learning!

XtremIO Array Administration

Finally writing my post on XtremIO array administration. It was due since long after i completed my blog on xtremio-architecture

So here we go... I'm covering basic details like - GUI overview, array administration and monitoring. I've tried covering few basic commands which can be used to check the system status using CLI. For details kindly check the array administration guide available at support.emc.com

GUI Overview:

Below picture depict the array dashboard where you check the system status in a glance. It shows overview about capacity, alerts, performance and hardware status.

  

Hardware overview:

Below picture depict the hardware overview of the array and cable connectivity:

Front view:

Back View:

Cable Connectivity:

The different cable connections are illustrated between the brick parts and where the storage connections would fit in.

Hardware Failure:

You can see that the hardware failure is highlighted via change in color.

Storage Provisioning:

Below are the steps for storage provisioning on XtremIO array:

1) Create new volume. You can also create multiple volumes in a single step and club them in a single folder. 

2) Create initiator group

3) Map the volumes created in Step 1 to the initiator group created in step 2. Just select the volumes and initiator group respectively and click on apply.

Array Alerts and Events:

XtremIO array has built in dashboard for the alert and event management. The reporting allows for events or alerts to be filter based on the severity, type and time frame. These are all good filter options and should allow admins to find the information they are looking for.

CLI Administration:

xmcli (admin)> xmcli (admin)>

xmcli (admin)> show-clusters

Cluster-Name Index State  Conn-State Num-of-Vols Vol-Size Logical-Space-In-Use Space-In-Use UD-SSD-Space Total-Writes Total-Reads Stop-Reason Size-and-Capacity

demo_sys4    1     active connected  15          155.006T 37.019T              815.314G     7.475T       633.341T     644.048T    none        1X10TB           

xmcli (admin)>

xmcli (admin)> show-clusters-performance

Cluster-Name Index Write-BW(MB/s) Write-IOPS Read-BW(MB/s) Read-IOPS BW(MB/s) IOPS Total-Write-IOs Total-Read-IOs

demo_sys4    1     6.236          1109       8.032         1241      14.269   2350 11394017006     4136936530    

xmcli (admin)> show-targets-performance

Name          Index Write-BW(MB/s) Write-IOPS Read-BW(MB/s) Read-IOPS BW(MB/s) IOPS Total-Write-IOs Total-Read-IOs

X1-SC1-fc1    1     1.582          279        2.077         312       3.659    591  2985113428      1099644445    

X1-SC1-fc2    2     1.432          245        1.793         314       3.225    559  2757886971      1002224794    

X1-SC1-iscsi1 5     0.000          0          0.000         0         0.000    0    0               0             

X1-SC1-iscsi2 6     0.000          0          0.000         0         0.000    0    0               0             

X1-SC2-fc1    11    1.674          310        2.165         308       3.839    618  3174570251      1191688338    

X1-SC2-fc2    12    1.548          274        1.994         305       3.542    579  2612228199      979161273     

X1-SC2-iscsi1 15    0.000          0          0.000         0         0.000    0    0               0             

X1-SC2-iscsi2 16    0.000          0          0.000         0         0.000    0    0               0             

xmcli (admin)> show-storage-controllers

Storage-Controller-Name Index Mgr-Addr     IB-Addr-1    IB-Addr-2    IPMI-Addr    Brick-Name Index Cluster-Name Index State   Unknown-Prop Enabled-State Unorderly-Stop-Reason Conn-State IPMI-State Unknown-Prop

X1-SC1                  1     10.10.169.50 169.254.0.1  169.254.0.2  10.10.169.53 X1         1     demo_sys4    1     healthy healthy      enabled       none                  connected  connected  on          

X1-SC2                  2     10.10.169.51 169.254.0.17 169.254.0.18 10.10.169.54 X1         1     demo_sys4    1     healthy healthy      enabled       none                  connected  connected  on          

xmcli (admin)> show-datetime

Mode NTP-Servers Cluster-Time Cluster-Time-Zone

xmcli (admin)> show-data-protection-groups

Name   Index State  Useful-SSD-Space UD-SSD-Space UD-SSD-Space-In-Use Rebuild-Progress Preparation-Progress Rebalance-Progress Rebuild-Prevention Brick-Name Index Cluster-Name Index

X1-DPG 1     normal 9.095T           7.475T       815.314G            0                0                    0                  none               X1         1     demo_sys4    1    

xmcli (admin)> show-xms

Name Index Xms-IP-Addr  Xms-Mgmt-Ifc

xms  1     10.10.169.52 eth0        

xmcli (admin)> show-storage-controllers-infiniband-ports

Name       Index Port-Index Peer-Type Port-In-Peer-Index Link-Rate-In-Gbps Port-State Storage-Controller-Name Index Brick-Name Index Cluster-Name Index

X1-SC1-IB1 1     1          None      0                  0                 up         X1-SC1                  1     X1         1     demo_sys4    1    

X1-SC1-IB2 2     2          None      0                  0                 up         X1-SC1                  1     X1         1     demo_sys4    1    

X1-SC2-IB1 3     1          None      0                  0                 up         X1-SC2                  2     X1         1     demo_sys4    1    

X1-SC2-IB2 4     2          None      0                  0                 up         X1-SC2                  2     X1         1     demo_sys4    1    

xmcli (admin)>

xmcli (admin)> show-storage-controllers-infiniband-counters

Storage-Controller-Name Index Port-Index Symb-Errs Symb-Errs-pm Recovers Recovers-pm Lnk-Downed Lnk-Downed-pm Rcv-Errs Rcv-Errs-pm Rmt-Phys-Errs Rmt-Phys-Errs-pm Integ-Errs Integ-Errs-pm Rate-Gbps Rcv-Errs-pl Recovers-pl Lnk-Downed-pl Symb-Errs-pl Intg-Errs-pl Rmt-Phys-Errs-pm

X1-SC1                  1     1                                                                                                                                                                                                                                                       

X1-SC1                  1     2                                                                                                                                                                                                                                                       

X1-SC2                  2     1                                                                                                                                                                                                                                                       

X1-SC2                  2     2                                                                                                                                                                                                                                                       

xmcli (admin)> show-infiniband-switches-ports

Port-Index Peer-Type Port-In-Peer-Index Link-Rate-In-Gbps Port-State IBSwitch-Name IBSwitch-Index Cluster-Name Index

xmcli (admin)> show-infiniband-switches

Name Index Serial-Number Index-In-Cluster State FW-Version Part-Number Cluster-Name Index

xmcli (admin)>  show-daes-controllers

Name         Index Serial-Number  State   Index-In-DAE Location FW-Version Part-Number  DAE-Name DAE-Index Brick-Name Index Cluster-Name Index

X1-DAE-LCC-A 1     US1D0121500226 healthy 1            bottom   149        303-104-000E X1-DAE   1         X1         1     demo_sys4    1    

X1-DAE-LCC-B 2     US1D0121500700 healthy 2            top      149        303-104-000E X1-DAE   1         X1         1     demo_sys4    1    

xmcli (admin)> show-daes-psus

Name        Index Serial-Number  Location-Index Power-Feed State   Input Location HW-Revision Part-Number DAE-Name DAE-Index Brick-Name Index Cluster-Name Index

X1-DAE-PSU1 1     AC7B0121702789 1              feed_a     healthy on    left     2a10        071-000-541 X1-DAE   1         X1         1     demo_sys4    1    

X1-DAE-PSU2 2     AC7B0121702790 2              feed_b     healthy on    right    2a10        071-000-541 X1-DAE   1         X1         1     demo_sys4    1    

xmcli (admin)> show-daes

Name   Index Serial-Number  State   FW-Version Part-Number Brick-Name Index Cluster-Name Index

X1-DAE 1     US1D1122100068 healthy 149        100-562-964 X1         1     demo_sys4    1    

xmcli (admin)>

xmcli (admin)> add-volume alignment-offset=0 lb-size=512 vol-name="LDN_VDI_00" vol-size="20g" parent-folder-id="/"

Added Volume LDN_VDI_00 [16]

xmcli (admin)> 

xmcli (admin)> show-volumes

Volume-Name     Index Vol-Size LB-Size VSG-Space-In-Use Offset Ancestor-Name Index VSG-Index Cluster-Name Index Parent-Folder-Name Index Unknown-Prop Unknown-Prop Unknown-Prop Total-Writes Total-Reads Certainty-State 

HA_Heartbeats01 1     2G       512     17.355M          0                          1         demo_sys4    1     /                  1     enabled      enabled      enabled      10.793G      77.218G     ok              

HA_Heartbeats02 2     2G       512     17.629M          0                          2         demo_sys4    1     /                  1     enabled      enabled      enabled      10.575G      77.211G     ok              

LDN_VDI_00      16    20G      512     0                0                          16        demo_sys4    1     /                  1     enabled      enabled      enabled      0            0           ok              

LUN_01          14    1G       512     0                0                          14        demo_sys4    1     Host_DBA           2     disabled     disabled     disabled     0            0           ok              

LUN_02          15    1G       512     0                0                          15        demo_sys4    1     Host_DBA           2     disabled     disabled     disabled     0            0           ok              

VDI-DS1         4     15T      512     3.604T           0                          4         demo_sys4    1     /                  1     disabled     disabled     disabled     9.974T       739.662G    ok              

VDI-DS2         5     15T      512     3.589T           0                          5         demo_sys4    1     /                  1     disabled     disabled     disabled     9.935T       722.896G    ok              

VDI-DS3         6     15T      512     3.604T           0                          6         demo_sys4    1     /                  1     disabled     disabled     disabled     9.975T       706.256G    ok              

VDI-DS4         7     15T      512     3.604T           0                          7         demo_sys4    1     /                  1     disabled     disabled     disabled     9.975T       690.904G    ok              

VDI-DS5         8     15T      512     3.604T           0                          8         demo_sys4    1     /                  1     disabled     disabled     disabled     9.975T       673.812G    ok              

VDI-DS6         9     15T      512     3.604T           0                          9         demo_sys4    1     /                  1     disabled     disabled     disabled     9.975T       657.464G    ok              

VDI-DS7         10    15T      512     3.604T           0                          10        demo_sys4    1     /                  1     disabled     disabled     disabled     9.976T       642.827G    ok              

VDI-DS8         11    15T      512     3.618T           0                          11        demo_sys4    1     /                  1     disabled     disabled     disabled     10.014T      628.075G    ok              

VDI-DS9         12    15T      512     3.618T           0                          12        demo_sys4    1     /                  1     disabled     disabled     disabled     10.013T      608.400G    ok              

VDI-DS10        13    15T      512     3.618T           0                          13        demo_sys4    1     /                  1     disabled     disabled     disabled     10.014T      592.012G    ok              

VDI_Infra1      3     5T       512     977.266G         0                          3         demo_sys4    1     /                  1     disabled     disabled     disabled     3.474T       199.027T    ok              

xmcli (admin)> 

xmcli (admin)> show-volume vol-id="LDN_VDI_00"

Volume-Name Index Vol-Size LB-Size VSG-Space-In-Use Offset Ancestor-Name Index VSG-Index Cluster-Name Index Parent-Folder-Name Index Unknown-Prop Unknown-Prop Unknown-Prop Total-Writes Total-Reads NAA-Identifier   Certainty-State 

LDN_VDI_00  16    20G      512     0                0                          16        demo_sys4    1     /                  1     enabled      enabled      enabled      0            0           860f8099b3e34ab3 ok              

xmcli (admin)> 

xmcli (admin)> show-initiator-groups

IG-Name     Index Parent-Folder-Name Index Certainty-State 

esx_scvdi01 1     /VDI_Cluster       2     ok              

esx_scvdi02 2     /VDI_Cluster       2     ok              

esx_scvdi03 3     /VDI_Cluster       2     ok              

esx_scvdi04 7     /VDI_Cluster       2     ok              

esx_scvdi05 5     /VDI_Cluster       2     ok              

esx_scvdi06 6     /VDI_Cluster       2     ok              

esx_scvdi07 4     /VDI_Cluster       2     ok              

esx_scvdi08 8     /VDI_Cluster       2     ok              

esx_scvdi09 9     /VDI_Cluster       2     ok              

esx_scvdi10 10    /VDI_Cluster       2     ok              

esx_scvdi11 11    /VDI_Cluster       2     ok              

esx_scvdi12 12    /VDI_Cluster       2     ok              

esx_scvdi13 13    /VDI_Cluster       2     ok              

esx_scvdi14 14    /VDI_Cluster       2     ok              

esx_scvdi15 15    /VDI_Cluster       2     ok              

esx_scvdi16 16    /VDI_Cluster       2     ok              

esx_scvdi17 17    /VDI_Cluster       2     ok              

esx_scvdi18 18    /VDI_Cluster       2     ok              

esx_scvdi19 19    /VDI_Cluster       2     ok              

esx_scvdi20 20    /VDI_Cluster       2     ok              

esx_scvdi21 21    /VDI_Cluster       2     ok              

esx_scvdi22 22    /VDI_Cluster       2     ok              

esx_scvdi23 23    /VDI_Cluster       2     ok              

esx_scvdi24 24    /VDI_Cluster       2     ok              

esx_scvdi25 25    /VDI_Cluster       2     ok              

esx_scvdi26 26    /VDI_Cluster       2     ok              

xmcli (admin)> 

Isilon Command Cheat Sheet

Command	Sub-Command	Description
man isi		To check the man page of isi command
isi license		To check the installed license
isi license activate <key>		To install the license
isi config
isi devices
isi get -a /ifs/data		Will give overall file system layout
isi --help
isi networks		For internal and external network configuration
isi devices -a add -d <device number>		To add the device back to cluster
isi devices -a format -d <device number>		Often need to format the drive for OneFS use first
isi_for_array -s isi_hw_status | grep -i 'power sup'		To check power supply status
isi_hw_status | grep SerNo		To check the serial number of node
isi auth ldap list		To list ldap details
isi nfs	exports	Manage NFS exports
	netgroup	Manage netgroup caching
	nlm	Manage NFS NLM sessions, locks, and waiters
	settings	Manage NFS default export and global protocol settings
isi quota	quotas	Manage quotas
	reports	Manage quota reports
	settings	Manage general quotas settings
isi services		To check Isilon service
Isi services <service name> disable		To disable any service
Isi services <service name> enable		To enable any service
isi set
isi smb	log-level	Configure the log level
	openfiles	List and close open SBM files
	sessions	List and disconnect SMB sessions
	settings	Manage SMB default share and global protocol settings
	shares	Manage SMB shares and their permissions
isi statistics	heat	Heat mode displays most active /ifs paths for a variety of metrics
	pstat	Pstat mode displays a selection of cluster-wide and protocol data
	drive	Drive mode shows peformance by drive
	list	List valid arguments to given option
isi snapshot	locks	manage snapshot locks
	schedules	Manage scheduled creation of snapshots
	settings	Manage snapshot settings
	snapshots	Manage file system snapshots.
isi status		To check cluster status
isi statistics system --top --nodes --interval=2		To check the top node at every two seconds
isi statistics heat --classes=read,write		To check the hottest files on the cluster
isi job		To check the running jobs / **only one job can one run at a time**
LNN set		Command to change the logical node number
# isi config		Go to config mode first
# lnnset		Gives the current status
# lnnset 3 7		Changes the LNN ID of node 3 from 3 to 7
isi distill
isi_distill		Distill the essence of an IFS directory tree
Example: isi_distill -k /ifs/data
Example: isi_distill -k -o /tmp/distill.txt /ifs/data		Allows to dump the output in a text file
Reboot the Isilon Node
# isi config		To go to config mode
# reboot 3		To reboot node 3
# exit		To exit from config mode

To check boot drive status:

# gmirror status