Unix,  VMware

Clariion/Navisphere CLI

A Clariion can be managed using the /opt/Navisphere/bin/navicli command. You can obtain information about the environment using the -h option followed by the IP address of the IP of the Clariion and then a number of get verbs. For example, to get all of the settings for the Clariion at 192.168.210.88:
navicli -h 192.168.210.88 getall

Or to get LUN information
navicli -h 192.168.210.88 getlun

You can also use getagent, getarrayuid, getcache, getconfig, getcontrol, getcrus, getdisk, getlog, getloop, getrg, getsniffer, getsp, getsptime and while it doesn’t start with get, lunmapinfo will obtain information about the LUN mappings. For example, to see a LUN mapped to a UID using the same host as above, you would use the following, replacing YOURUID with the UID for the storage group in question
navicli -h 192.168.210.88 storagegroup -list -uid YOURUID

One task I always do is to set the name of an array. For e
navicli -h 192.168.210.88 arrayname KRYPTED_CLARiiON

You can also use navicli to manage day to day operations. For example, to clear out logs and statistics you can use the following respectively:
navicli -h 192.168.210.88 clearlog
navicli -h 192.168.210.88 clearstats

And then you can of course configure any of the devices that you can get information for using the get* commands. For example, to create two RAID groups, you can use the createrg verb, followed by an ID for the group and then the disks that will be part of the RAID group (IDs can be obtained using the getdisk verb).
navicli -h 192.168.210.88 createrg 0 0_0_0 0_0_1 0_0_2 0_0_3 0_0_4
navicli -h 192.168.210.88 createrg 1 0_0_5 0_0_6 0_0_7 0_0_8 0_1_0

Once you have created RAID groups, you’ll want to use the bind verb on the new RAID groups, and in so doing tell them what RAID level to run at, with r0, r1 and rb being RAID 0, RAID 1 & RAID 5 respectively. For example to set RAID group 0 and 1 to RAID 5:
navicli -h 192.168.210.88 bind r5 0 -rg 0
navicli -h 192.168.210.88 bind r5 0 -rg 1

Note: The only flag we were really using was -h. But when you’re writing scripts against navicli it’s pretty helpful to use the -m which only shows values as the result of commands, which can cut down on the amount of scripting you have to do…

Note 2: If you’re working with an arbitrated loop then also make sure to review the navicli alpha command set. For example:
navicli -h 192.168.210.88 alpa -get