Pages

3/21/2013

Isi Blogging?: Job Engine

Isi Blogging?: Job Engine:

There is a single Isilon node that is the job coordinator.
Find out which node is is with:

isi job status -r
example-output:
coordinator.connected=True
coordinator.devid=1
coordinator.down_or_read_only=False

Isilon Performance Stats

Summary
isi statistics drive --nodes=all --orderby=busy --type=sas,sata --top
or
isi statistics drive --nodes=all --orderby=busy --type=sas,sata | head -n 30

Drive Queue
isi statistics drive --nodes=all --orderby=queued --type=sas,sata --top

Cluster Performance Snapshot
isi statistics pstat

List files in use
isi statistics heat --nodes=all --orderby=ops --top

List of client connections
isi statistics client --nodes=all --orderby=ops --top

Get rid of "pseudo nics"

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters for a REG_DWORD entry called DisabledComponents.
If it's not there, create it in Parameters. Set its value to 1

3/15/2013

Isi Blogging?: Job Engine

Isi Blogging?: Job Engine: Job Engine
Isilon Blog

Re: How do you calculate usable capacity for Isilon?

Clear as mud:
Re: How do you calculate usable capacity for Isilon?
Here is the general accepted formula used when sizing:
1) Find total raw TB in base 10
2) Multiply that result by (1000^4/1024^4) to get base 2 TB
3) Subtract 1 GB per drive for the OS partitions
4) Subtract 0.0083% of that result to account for the filesystem format
5) Subtract the protection overhead from that result
As for the protection overhead that you are planning to use, look to the "OneFS User Guide" on support.emc.com. Skip to the section: "OneFS data protection" where it will talk about N+M data protection, protection schemes such as N+1, N+2:1 (default), 2x, etc and the associated cost/parity overhead. Also, you will see a very good matrix listing the percent overhead which begins by reminding us: "The parity overhead for each protection level depends on the file size and the number of nodes in the cluster."

3/08/2013

ESXi Remote Administration

Remotely managing ESXi servers has turned into such a pain in the butt. From VCS: - Software > Security Profile - Check firewall and check box for SSH client & server if needed. - Open Services and start the SSH service. - SSH to server - you can type DCUI to get the same user interface as if you are on the console of the physical server. - or you can do the following to restart all the services: - cd /sbin - services.sh restart