Scribd
Upload
760 views

Raidcom Provisioning On The VSP

The document provides instructions for using the Raidcom command line tool to configure a Hitachi VSP array. It includes examples of creating a HORCM file, logging into the SVP, checking storage configuration details, creating logical devices (LDEVs) and parity groups, and assigning LDEVs to host groups. The goal is to demonstrate how to use Raidcom to perform end-to-end storage provisioning and configuration of the VSP array.

Uploaded by

Vignesh Babu
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
760 views

Raidcom Provisioning On The VSP

The document provides instructions for using the Raidcom command line tool to configure a Hitachi VSP array. It includes examples of creating a HORCM file, logging into the SVP, checking storage configuration details, creating logical devices (LDEVs) and parity groups, and assigning LDEVs to host groups. The goal is to demonstrate how to use Raidcom to perform end-to-end storage provisioning and configuration of the VSP array.

Uploaded by

Vignesh Babu
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Well our friends at HDS have updated the CCI and VSP code to allow end to end

provisioning on the VSP Freakin sweet no more GUI :-). My Collegues and I have
created a script to perform VSP provisioning but since everyone has there own view on the
best scripting languages I will leave the scripts for you to determine what your favorite one
is. In place of the script I will give you the appropriate commands to run.

Enjoy and let me know if this has helped you!!!

Create a HORCM file and place it in the proper location c:\windows or whatever os requires

HORCM

#
#/************************* For HORCM_MON *************************************/

HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
10.0.0.1 horcm99 1000 3000

#/************************** For HORCM_CMD ************************************/

HORCM_CMD
#dev_name dev_name dev_name
#For IP command device svp is the ip the -31001 is the fixed port for virtual command
device
\\.\IPCMD-10.0.0.2-31001

#/************************** For HORCM_LDEV ***********************************/

HORCM_LDEV
#dev_group dev_name Serial# CU:LDEV(LDEV#) MU#
#VG01 oradb3 11112 01:04 0

#/************************* For HORCM_INST ************************************/


HORCM_INST
#dev_group ip_address service
#VG01 10.0.0.1 horcm99
C:\>set HORCMINST=99

C:\>horcmstart 99
starting HORCM inst 99
HORCM inst 99 starts successfully.

C:\>raidcom -login maintenance raid-mainte

Host Group Creation / WWN Nickname

raidcom add host_grp -port CL2-E-1 -host_grp_name test-it


raidcom add host_grp -port CL1-E-1 -host_grp_name test-it
raidcom modify host_grp -port CL1-E-1 -host_mode 3 -host_mode_opt 12
40 (HPUX and proper modes)
raidcom modify host_grp -port CL2-E-1 -host_mode 3 -host_mode_opt 12
40
raidcom add hba_wwn -port CL1-E-1 -hba_wwn 10000000c9537bb2
raidcom add hba_wwn -port CL2-E-1 -hba_wwn 10000000c9537d06
raidcom set hba_wwn -port CL1-E-1 -hba_wwn 10000000c9537bb2
-wwn_nickname testhpux1
raidcom set hba_wwn -port CL2-E-1 -hba_wwn 10000000c9537d06
-wwn_nickname testhpux1
Create Ldevs and assign to proper CU and Pool

Create an ldev in HDT Pool 0, ldev=00:40:00 , capacity=30GB in blocks

raidcom add ldev -pool_id 0 -ldev_id 0x4000 -capacity 62914560


Create an ldev in HDT Pool 0, ldev=00:46:47 , capacity=300GB in blocks

raidcom add ldev -pool_id 0 -ldev_id 0x4647 -capacity 629145600


Add an ldev to a hostgroup

raidcom add lun -port CL1-E-1 -lun_id 0003 -ldev_id 0x4647


raidcom add lun -port CL2-E-1 -lun_id 0003 -ldev_id 0x4647
C:\>raidcom -logout
C:\>hormcshutdown 99

RAIDCOM (Newest Edition to


the CCI Family)
Posted on July 25, 2011
Hello again.. I figured everyone was probably getting burned out reading posts
on SNM2 CLI. I believe I have beat that horse to death. Thought I would talk
about something a bit more current. Raidcom is a new command added to the
CCI command set for the VSP, it also works a bit with the USPV and USP but
more on that later. Lets go over some basics shall we:

First off the newer version of CCI can work with a virtual command device (IP
address of the SVP), or a more traditional physical command device (\\.\CMD-
23340, GUID, or Physical Device. However, even though there is a virtual
command device now be wary, I would only plan on using it with Raidcom
commands. Applications like Tuning Manager, Replication Manager and CCI (CCI
things like paircreate, pairsplit etc) will not work with a virtual command device.
(Nice little hidden and most annoying secret).

With a virtual command device you must login to the svp via the command line
in order to execute anything. Here is a snapshot of some useful get commands,
as well as some lun creation, and host group adding ones..

Simple Test HORCM File

HORCM

#/*************************ForHORCM_MON
*************************************/

HORCM_MON

#ip_addressservicepoll(10ms)timeout(10ms)
10.0.0.1horcm9910003000

#/**************************ForHORCM_CMD
************************************/

HORCM_CMD

#dev_namedev_namedev_name

#ForIPcommanddevicesvpistheipthe31001isthefixedportforvirtual
commanddevice

\\.\IPCMD10.0.0.331001

#/**************************ForHORCM_LDEV
***********************************/

HORCM_LDEV

#dev_groupdev_nameSerial#CU:LDEV(LDEV#)MU#

#VG01oradb35888801:040

#/*************************ForHORCM_INST
************************************/

HORCM_INST

#dev_groupip_addressservice
#VG0110.0.0.1horcm99

C:\>setHORCMINST=99

C:\>horcmstart99

startingHORCMinst99

HORCMinst99startssuccessfully.

C:\>raidcomloginmaintenanceraidmainte(VSPSVPDefaultusernameand
passwordSuggestchangingthis)

raidcomlogoutToLogoutofthesystem

C:\>raidcomgetpoolkeyopt

PIDPOLSU(%)POOL_NAMESeq#NumLDEV#H(%)
VCAP(%)

000POLN31DP058888225734480

001POLN35DP158888225760080

100POLN0COWPool5888846144280

C:\>raidcomgetthp_poolkeyopt

PIDPOLSMODESTSDATTNOTL_RANGETD_RANGETU_CAP(MB)TT_CAP(MB)T(%)
P(%)R(%)
000POLNAUTMONVAL10000000000000005148379281648626085
100

000POLNAUTMONVAL2000000000000000011930103381033680
100

001POLNAUTMONVAL10000000000000005148380121648626085
100

001POLNAUTMONVAL2000000000000000029444943381033684
100

C:\>raidcomgetport

PORTTYPEATTRSPDLPIDFABCONNSSWSLSerial#WWN

CL1AFIBRETARAUTEFYPtoPY05387350060e8000000000

CL1BFIBRETARAUTE1YPtoPY05387350060e8000000000

CL1CFIBRETARAUTB2YPtoPY05387350060e8000000000

CL1DFIBRETARAUTACYPtoPY05387350060e8000000000

C:\>raidcomgetparity_grp

TGROUPNum_LDEVU(%)AV_CAP(GB)R_LVLR_TYPESLCLDRIVE_TYPE

R1111000RAID53D+1P00DKS5CJ600SS

R1211000RAID53D+1P00DKS5CJ600SS

R1311000RAID53D+1P00DKS5CJ600SS

R1411000RAID53D+1P00DKS5CJ600SS

R1511000RAID53D+1P00DKS5CJ600SS
R1611000RAID53D+1P00DKS5CJ600SS

R1711000RAID53D+1P00DKS5CJ600SS

R181990RAID53D+1P00DKS5CJ600SS

R191990RAID53D+1P00DKS5CJ600SS

R1101990RAID53D+1P00DKS5CJ600SS

R1114990RAID53D+1P00DKS5CJ600SS

R2111000RAID53D+1P00DKS5CJ600SS

R2211000RAID53D+1P00DKS5CJ600SS

R2311000RAID53D+1P00DKS5CJ600SS

R2411000RAID53D+1P00DKS5CJ600SS

R2511000RAID53D+1P00DKS5CJ600SS

R2611000RAID53D+1P00DKS5CJ600SS

R271990RAID53D+1P00DKS5CJ600SS

R281990RAID53D+1P00DKS5CJ600SS

R291990RAID53D+1P00DKS5CJ600SS

R2101990RAID53D+1P00DKS5CJ600SS

R211201600RAID53D+1P00DKS5CJ600SS

R514990RAID66D+2P00DKR2CH2R0AT

R524990RAID66D+2P00DKR2CH2R0AT

R534990RAID66D+2P00DKR2CH2R0AT

R544990RAID66D+2P00DKR2CH2R0AT
R554990RAID66D+2P00DKR2CH2R0AT

R564990RAID66D+2P00DKR2CH2R0AT

CreateLdevsandassigntoproperCUandPool

raidcomaddldevpool_id0ldev_id0x4000capacity62914560Createan
ldevinHDTPool0,ldev=00:40:00,capacity=30GBinblocks

raidcomaddldevpool_id0ldev_id0x4647capacity629145600Createan
ldevinHDTPool0,ldev=00:46:47,capacity=300GBinblocks

Addanldevtoahostgroup

raidcomaddlunportCL5A4lun_id0003ldev_id0x4647

raidcomaddlunportCL6A4lun_id0003ldev_id0x4647

HopefullythiswashelpfultoyouwhendeployingyounewVSP's

You might also like