XIO - CorteX Developer Forums

X-IO ISE CorteX API Document

jnicholson — Tue, 11 Sep 2012 01:03:26 GMT

CorteX PowerShell Demo Script v1.1

JD Wallace — Tue, 07 Aug 2012 19:19:18 GMT

Building upon the POST, GET, DELETE, and PUT samples posted on the forum I have created a PowerShell demo script that will walk the user step by step through creating, assigning, modifying, and deleting a storage volume and host.

Actionable Alert Codes and their meanings

Butch Clark — Thu, 17 Nov 2011 20:22:15 GMT

Note: Actionable ISE alert codes begin on page 47.

Perl Scripts for Automating Snapshots on Block Storage Controllers

Joel Grace — Fri, 08 Apr 2011 16:56:51 GMT

This package includes two example Perl scripts that allow for discovery of volumes on Block Storage Controller (Enterprise/Data Center) and the creation of snapshots through CorteX. FIle descriptions:

bsc.config - This is an XML config file that can be used to store the system Serial Number, IP address, and authentication info

bsc_getvols.pl - This script will query the BSC for all volumes, and report their GUID (needed for snapshot creation) as well as the volume type (primary, snapshot, metadata, etc) This script can be combined with bsc_snapvol.pl to perform the query and snapshot in a single script, or for verification purposes.

bsc_snapvol.pl - This script takes a given GUID ($src_id) and snapshot name ($dst) to create a snapshot of a volume. For the sake of an example script, the variables are set manually, but they certainly could be passed via @ARGV, entries in the bsc.config, or auto-generated, etc....

Xiotech Emprise 5000 CorteX API Document

jnicholson — Fri, 03 Dec 2010 20:51:19 GMT

This is the PDF document for the Xiotech Emprise 5000 CorteX API. It calls out the various resources and methods that can be manipulated on this storage device.

iseperf.pl - Perl Script to Log ISE LUN Performance

Joel Grace — Sat, 10 Jul 2010 06:39:32 GMT

iseperf.pl is a Perl script and associated configuration file, that can be used to quickly and easily retrieve LUN performance data from Emprise 5000's, and store in .csv format to be used for custom graphs, reports, and trend analysis.

iseperf.conf - Configuration File

This file is used to store the list of ISE's that will be queried for performance data. The format looks like this:

<config>
   <systems>
      <system1>
         <serial>11111111</serial>
         <ip>1.1.1.1</ip>
         <username>user</username>
         <password>pass</password>
      </system1>
      <system2>
         <serial>11111112</serial>
         <ip>1.1.1.2</ip>
         <username>user</username>
         <password>pass</password>
      </system2>
   </systems>
   <options>
      <loop>no</loop>
      <loop_interval>5</loop_interval>
   </options>
</config>

The primary tag is a user-defined friendly name of the ISE (in this case it's system1 and system2). Within these tags lies the necessary information to connect to the ISE, Serial Number, IP Address, Username, and Password. Obviously you'll want to protect this file, or the script could easily be modified to prompt for the sensitive information. The configuration file also provides options for controller whether the script runs once per call, or loops infinitely based on a polling interval (loop_interval). For instance, if you schedule the script with cron or MS Task Scheduler, you would want to set the <loop> option to no. If you want to kick off the script and let it run on it's own for an extended period of time, just set the <loop> tag to 'yes' and then set the <loop_interval> to the number of seconds between each collection.

iseperf.pl - Performance Logging Script

The script can be run on just about any system that supports Perl. Each run of the script produces a single output of the performance statistics for the LUN's on the ISE being queried. This could be useful for current point in time analysis, but it's mainly designed so that it can be run at user-defined intervals to collect performance statistics. Windows Task Scheduler, UNIX/Linux cron, or modifying the script with a loop statement and sleep intervals are all viable options. The script will generate two files, a iseperf.csv for performance data, and iseperf.log for logging any failed attempts to query an ISE/Emprise 5000. The script queries each ISE/Emprise 5000 listed in the configuration file through the Cortex RESTful API. The Emprise 5000 replies back with the performance data in XML format which is then parsed and written to the .csv file. Here's a sample of the .csv output:

Date,ISE Serial,Volume,Read Percentage,Queue Depth,Queue Depth Max,Average Transfer Size,Read Latency Max,Write Latency Max,Read Latency,Write Latency,Total IOPS,Read IOPS,Write IOPS,Total Kbps,Read Kbps,Write Kbps
7/9/10 23:50,11111111,demojg1,79,8,9,4096,35,16,3,0,3233,2563,670,12932,10252,2680
7/9/10 23:51,11111111,demojg1,79,8,9,4096,167,29,3,0,2651,2096,555,10604,8384,2220
7/9/10 23:52,11111111,demojg1,81,8,9,4096,257,54,3,0,2542,2065,477,10168,8260,1908
7/9/10 23:53,11111111,demojg1,81,8,9,4096,257,67,3,0,2774,2255,519,11096,9020,2076
7/9/10 23:54,11111111,demojg1,79,8,9,4096,257,98,3,0,2803,2234,569,11212,8936,2276
7/9/10 23:55,11111111,demojg1,79,8,9,4096,264,98,3,0,2859,2284,575,11436,9136,2300

The date field in the output is in a format that's friendly to MS Excel, so you can easily sort the data and generate graphs, charts, etc.

To run the script on Linux, simply open a shell and 'cd' to the directory containing the script, and run it './iseperf.pl'

To run the script on Windows, first ensure Perl is installed (ActiveState Perl or Cygwin are great options), open DOS and navigate to the folder containing the script, and run 'perl iseperf.pl'

Have fun!

-Joel

getFiles perl script which fetches XML data from an ISE

kmorgan — Tue, 27 Apr 2010 02:04:23 GMT

Attached is the perl script I wrote to fetch the XML data from an ISE and save it in a directory for the virtual ISE available at

external ip addresses 207.250.72.221 / 222

internal ip addresses 172.21.187.71 / 72

It fetches the data saving it in the specified directory, sets up a .htaccess file to rewrite the directory names -> file.xml. Another .htaccess file is created to setup basic athentication and prompt for the default userid/passwd challenge like an ISE (administrator/administrator).

Regards

/Karl

P.S. Sorry for the .txt file, the forum would not let me upload it with a .pl extension

SNIA CDMI Version 1.0

peglarr — Wed, 14 Apr 2010 19:10:38 GMT

This is the SNIA Cloud Data Management Interface (CDMI) version 1.0 spec.

Powered By CorteX Images

Butch Clark — Wed, 07 Apr 2010 19:29:39 GMT

Set of three JPG images (One in black & white, two in color) that say "Powered by CORTEX", for use in documents and websites.

ISE CorteX XML Schema Documents

jnicholson — Wed, 07 Apr 2010 13:07:16 GMT

CorteX XML Schema Documents

This is the first release of the ISE CorteX XML schema documents. There are 18 individual documents that pertain to each of the available resources on the ISE. Here is a quick list:

1. allocations.xsd - Describes the /allocations resource for connections between /volumes and /endpoints (LUN Mapping/Masking)

2. arrays.xsd - Describes the /arrays "main page" or "start page" when coming into the system

3. batteries.xsd - Describes the /batteries resource

4. chronometer.xsd - Describes the /chronometer resource for date, time, time zone, DST, and uptime

5. controllers.xsd - Describes the /controllers resource (ISE Managed Reliability Controllers) and includes the FC Port and SFP info

6. endpoints.xsd - Describes the /endpoints resource for both the array and the remote hosts

7. files.xsd - Describes the /files resource which contains the syslog, upgrade, modules, and diagreport for each /controller and event and mgmt logs for the array, and provides the system SNMP MIB

8. hosts.xsd - Describes the /hosts resource which is a grouping of one or more remote host /endpoints

9. jobs.xsd - Describes the /jobs resource for any active long-lived operations

10. media.xsd - Describes the /media resource (DataPacs on ISE) which is the physical media resource for /pools

11. network.xsd - Describes the /network resource for DHCP, Wake-on-LAN, and reporting/configuring the local Ethernet connectivity info

12. performance.xsd - Describes the /performance resource which contains the /volumes, /endpoints, /controllers, and /arrays instantaneous performance info

13. pools.xsd - Describes the /pools resource which is the logical representation of /media. It provides /volumes for /allocations to /endpoints

14. powersupplies.xsd - Describes the /powersupplies resource which includes fan information

15. query.xsd - Describes the /query resource which is the non-authenticated way to discover /arrays

16. revision.xsd - Describes the /revision resource for doing code updates

17. subscriptions.xsd - Describes the /subscriptions resource for Clients to subscribe for receiving alerts, general updates, and telemetry

18. volumes.xsd - Describes the /volumes resource that is storage capacity carved out of /pools for /allocations to /endpoints

STAT5000 1.1: Status and Performance monitoring: source and executables

toddburkey — Sat, 03 Apr 2010 16:41:44 GMT

This is the STAT5000 documented in the forum section as:

http://cortexdeveloper.com/cortexdeveloper/f/13/t/2.aspx

It is intended to be a lightweight intro to one of many methods of monitoring performance and status. It also has a start to the full configuration view (via tooltips) that I just haven't had time to complete yet...been busy with the iPhone API (which is definitely NOT a one day excercise.)

-Todd Burkey