Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

paircreate error

Claudio_17
Frequent Advisor

paircreate error

Hi

any idea about this error ?

COMMAND ERROR : EUserId for HOMRCF : root (0) Fri Sep 12 13:50:29 2003
CMDLINE : paircreate -g vg01_02 -d device28_M -vl
13:50:31-f27ff-07824- ERROR:cm_sndrcv[rc < 0 from HORCM]
13:50:32-1ae09-07824- [paircreate] L_CMD(CREATEPAIR) ERROR :rc = -35
13:50:32-2109b-07824- [paircreate][exit(221)]
[EX_CMDRJE] An order to the control/command device was rejected
[Cause ]: An order to the command(control) device failed,or was rejected.
[Action]:Please confirm the following items.If this trouble doesn't resolve,then collect HORCM error logs(HORCM_LOG=/HORCM/log2/curlog) and trace data,and send them to service personnel.
(1) Check if the 'HORC or HOMRCF function' is installed in the RAID.
(2) Check if the RCP and LCP are installed in the RAID.
(3) Check if the path between the RAID CUs is established by using the SVP.
(4) Check if the pair target volume is an appropriate status.


I've checked all XP device on local/remote are ok
7 REPLIES
Duncan Edmonstone
Honored Contributor

Re: paircreate error

Is this a BC or CA volume?

What is the output 0f 'pairdisplay -g vg01_02' ?

Remember that for BC volumes you must set the HORCC_MRCF env variable to 1 before proceeding:

export HORCC_MRCF=1
paircreate -g vg01_02 -d device28_M -vl


HTH

Duncan

HTH

Duncan
Claudio_17
Frequent Advisor

Re: paircreate error

Hi,

this output of pairdisplay -g vg01_02

Group PairVol(L/R) (Port#,TID,LU-M),Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M
vg01_02 device03_M(L) (CL1-A , 5, 0-0)55491 40..P-VOL PAIR,55491 285 -
vg01_02 device03_M(R) (CL1-E , 5, 0-0)55491 285..S-VOL PAIR,----- 40 -
vg01_02 device04_M(L) (CL1-A , 5, 1-0)55491 41..P-VOL PAIR,55491 286 -
vg01_02 device04_M(R) (CL1-E , 5, 1-0)55491 286..S-VOL PAIR,----- 41 -
vg01_02 device1A_M(L) (CL1-A , 3, 2-0)55491 26..P-VOL PAIR,55491 287 -
vg01_02 device1A_M(R) (CL1-E , 3, 2-0)55491 287..S-VOL PAIR,----- 26 -
vg01_02 device1B_M(L) (CL1-A , 3, 3-0)55491 27..P-VOL PAIR,55491 288 -
vg01_02 device1B_M(R) (CL1-E , 3, 3-0)55491 288..S-VOL PAIR,----- 27 -
vg01_02 device24_M(L) (CL1-A , 5, 2-0)55491 42..P-VOL PAIR,55491 289 -
vg01_02 device24_M(R) (CL1-E , 5, 2-0)55491 289..S-VOL PAIR,----- 42 -
vg01_02 device25_M(L) (CL1-A , 5, 3-0)55491 43..P-VOL PAIR,55491 290 -
vg01_02 device25_M(R) (CL1-E , 5, 3-0)55491 290..S-VOL PAIR,----- 43 -
vg01_02 device26_M(L) (CL1-A , 5, 4-0)55491 44..P-VOL PAIR,55491 291 -
vg01_02 device26_M(R) (CL1-E , 5, 4-0)55491 291..S-VOL PAIR,----- 44 -
vg01_02 device27_M(L) (CL1-A , 5, 5-0)55491 45..P-VOL PAIR,55491 292 -
vg01_02 device27_M(R) (CL1-E , 5, 5-0)55491 292..S-VOL PAIR,----- 45 -
vg01_02 device28_M(L) (CL1-A , 5, 6-0)55491 46..SMPL ----,----- ---- -
vg01_02 device28_M(R) (CL1-E , 5, 6-0)55491 293..SMPL ----,----- ---- -
vg01_02 device29_M(L) (CL1-A , 5, 7-0)55491 47..SMPL ----,----- ---- -
vg01_02 device29_M(R) (CL1-E , 5, 7-0)55491 294..SMPL ----,----- ---- -
Group PairVol(L/R) (Port#,TID,LU-M),Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M
vg01_02 device2A_M(L) (CL1-A , 6, 0-0)55491 54..SMPL ----,----- ---- -
vg01_02 device2A_M(R) (CL1-E , 6, 0-0)55491 295..SMPL ----,----- ---- -
vg01_02 device2B_M(L) (CL1-A , 6, 1-0)55491 55..SMPL ----,----- ---- -
vg01_02 device2B_M(R) (CL1-E , 6, 1-0)55491 296..SMPL ----,----- ---- -
vg01_02 device55_M(L) (CL1-A , 6, 5-0)55491 59..SMPL ----,----- ---- -
vg01_02 device55_M(R) (CL1-E , 6, 5-0)55491 302..SMPL ----,----- ---- -
vg01_02 device56_M(L) (CL1-A , 6, 6-0)55491 60..SMPL ----,----- ---- -
vg01_02 device56_M(R) (CL1-E , 6, 6-0)55491 303..SMPL ----,----- ---- -
vg01_02 device57_M(L) (CL1-A , 6, 7-0)55491 61..SMPL ----,----- ---- -
vg01_02 device57_M(R) (CL1-E , 6, 7-0)55491 304..SMPL ----,----- ---- -
vg01_02 device58_M(L) (CL1-A , 8, 0-0)55491 62..SMPL ----,----- ---- -
vg01_02 device58_M(R) (CL1-E , 8, 0-0)55491 305..SMPL ----,----- ---- -
vg01_02 device59_M(L) (CL1-A , 8, 1-0)55491 63..SMPL ----,----- ---- -
vg01_02 device59_M(R) (CL1-E , 8, 1-0)55491 306..SMPL ----,----- ---- -
vg01_02 device5A_M(L) (CL1-A , 8, 2-0)55491 64..SMPL ----,----- ---- -
vg01_02 device5A_M(R) (CL1-E , 8, 2-0)55491 307..SMPL ----,----- ---- -


HORCC_MRCF is set to 1

Strange is that first I did command

paircreate -g vg01_02 -vg and got an error .
So I've repeated command specifyng first device device03_M .

After pairdisplay -g vg01_02 I've seen devices from 03 to 27 was in copy ; I was aspected only 03 in copy . At end all devices come in pair .

Local devices are also CA devices , that's primary BC devices. I'm tring making a secondary BC devices for backup purposes




Dave La Mar
Honored Contributor

Re: paircreate error

Claudio -
A couple of things to note that we have encountered.
1. When adding new pairs to the horcm file, we normally stop and start the horcm to insure it reads the updated config.
(It appears you did so since the display works and they are in simplex mode.)
2. Insure the apporpriate horcminst is exported as well as the HOMRCF.
3. Not sure what our differences are but our normal create command goes like-
paircreate ???g ???groupname??? ???d P002S015 ???vl

Best of luck,

Regards,

dl
"I'm not dumb. I just have a command of thoroughly useless information."
Dave La Mar
Honored Contributor

Re: paircreate error

Just noticed your comment on a second pair for backup purposes. In the horcm.conf file the column MU is for this purpose. a value of 0 or 1 may be used. 0=primary pair 1=backup pair in our shop. This is mandatory if the same primary is used with two different business copy devices.

Hang in there.
dl
"I'm not dumb. I just have a command of thoroughly useless information."
Claudio_17
Frequent Advisor

Re: paircreate error

Problem solved running pvcreate for few devices at once . Seems raidmanager has a limit of pair can be created at same time.

I must say that my primary BC vols are also secondary CA vols .


Claudio_17
Frequent Advisor

Re: paircreate error

Problem solved running pvcreate for few devices at once . Seems raidmanager has a limit of pair can be created at same time.

I must say that my primary BC vols are also secondary CA vols .


Claudio_17
Frequent Advisor

Re: paircreate error

Errate corrige .. I discover I can create a max of 8 pair using any devices ; while tring create next ( #9 ) pair i got the error. Seems a problem due license of BC that put a limit to Tera byte can be copied