Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

Raid manager error with continuous access

SOLVED
Go to solution
Nedved
Frequent Advisor

Raid manager error with continuous access

Hi,


i am trying to configure Continuous Access between my DC and Dr..

This is the conf file from from both servers
DC

root@DC-TEST#grep horcm7 /etc/services
horcm7 65007/udp #Raid Manager Instance7

horcm7.conf
-------------
HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
DC_TEST horcm7 1000 6000

HORCM_CMD
#dev_name dev_name dev_name
/dev/rdsk/c1t15d7 /dev/rdsk/c6t15d7 /dev/rdsk/c12t15d7 /dev/rdsk/c18t15d7


HORCM_LDEV
#dev_group dev_name Serial# CU:LDEV(LDEV#) MU#
catest ldev-1 25818 3f:ff 0

HORCM_INST
#dev_group ip_address service
catest DR-TEST horcm7


DR
--

root@-DR-TEST#grep horcm7 /etc/services
horcm7 10007/udp ##TESTCA

horcm7.conf
-------------
HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
DR_TEST horcm7 1000 3000

HORCM_CMD
#dev_name dev_name dev_name
/dev/rdsk/c3t0d1 /dev/rdsk/c5t0d1


HORCM_LDEV
#dev_group dev_name Serial# CU:LDEV(LDEV#) MU#
catest ldev-1 25895 3f:0f 0

HORCM_INST
#dev_group ip_address service
catest DC-TEST horcm7


the hostnames are correct and i can able ping the server from both sides. Instances are starting correctly in bot the side.. process are also running.
I tried to execute pairdisplay from the DC and getting the following error.


export HORCMINST=7
export HORCC_MRCF=7

root@DC-TEST#./pairdisplay -g catest
pairdisplay: [EX_ATTHOR] Can't be attached to HORC manager
Refer to the command log(/HORCM/log/horcc_DC-TEST.log) for details.


COMMAND ERROR : EUserId for HOMRCF : root (0) Mon Mar 21 10:56:32 2011
CMDLINE : ./pairdisplay -g catest
*********** SYSTEM ERROR ***********
P.P. : Raid Manager XP for HP-UX
Model : Raid-Manager-XP/HP-UX
Ver&Rev: 01.23.08
Release: Production

Host: DC-TEST
EUserId: root (0)
Process: 23608

[System Call Error]
SysCall: bind
Errorno: 2 (No such file or directory)
ErrInfo: Internal Error
ErrTime: Mon Mar 21 10:56:32 2011
SrcFile: shorcmc.c
SrcLine: 669

10:56:32-82ab5-23608- 23608:HORCM death detected
10:56:35-a876b-23608- ERROR:cm_open[scmclcon() timeout_err]
10:56:35-aa1fd-23608- ERROR:horcm_lep_create
10:56:35-ac0a6-23608- [pairdisplay][exit(251)]
[EX_ATTHOR] Can't be attached to HORC manager
[Cause ]:Couldn't connect with the HORC manager.
[Action]:Please check if HORC manager is running or if HORCMINST is set correctly.

Please help me to solve this issue..

Thanks,

18 REPLIES
GuyPaul
Occasional Advisor
Solution

Re: Raid manager error with continuous access

Try:

export HORCC_MRCF=0

1 is for Business copy
0 is for CA (default)
Nedved
Frequent Advisor

Re: Raid manager error with continuous access

Hi,

thanks for the reply.

Today i am out of office. i will test tomorrow and let you know..
Michael Leu
Honored Contributor

Re: Raid manager error with continuous access

Or even better use 'pairdisplay -IH7 ...' instead of env variables.

From pairdisplay -h:
-IH[#] or -ICA[#] Set to HORC mode [and HORCMINST#]
-IM[#] or -IBC[#] Set to MRCF mode [and HORCMINST#]
---------------------------------------------------------------------------------
Navigation: Forum Site Map // ye olde ITRC Tree
@HP: please get rid of the Passport login timeout
Nedved
Frequent Advisor

Re: Raid manager error with continuous access

Hi Michael,

i tried # pairdisplay -IH7 -g catest also but still getting the same error..
now i saw the version of raid manager is different in dc and dr.

Is that should be same?
Michael Leu
Honored Contributor

Re: Raid manager error with continuous access

Yes, both versions should be the same I think.
You did start the raidmanager? :-)
---------------------------------------------------------------------------------
Navigation: Forum Site Map // ye olde ITRC Tree
@HP: please get rid of the Passport login timeout
Nedved
Frequent Advisor

Re: Raid manager error with continuous access

Hi

Horcm process is running only..
i modified the horcm conf file from horcm_ldev to horcm_dev.

now in the dr site instance is starting perfectly and i can able to see the pairstatus of S-VOL without any problem..

but in the primary side i could not start the horcm instance. getting the below log..

- HORCM STARTUP LOG - Wed Mar 23 22:11:30 2011
*****************************************************************************
22:11:30-49233-22337- horcmgr started on Wed Mar 23 22:11:30 2011
22:11:30-4b1d9-22337- execvp() horcmd_07 using /etc/horcmgr [CWD=/]
22:11:30-55542-22338- Fibre address conversion TBL has been set to '4'

P.P. : Raid Manager XP for HP-UX
Model : Raid-Manager-XP/HP-UX
Ver&Rev: 01.23.08
Release: Production

(C) Copyright 1999-2009 Hewlett-Packard Co., All Rights Reserved

HORCM(DC-BKUP22338) started by root (0) on Wed Mar 23 22:11:30 2011

22:11:30-5e35e-22338- horcmd_07 started on Wed Mar 23 22:11:30 2011
slmcmrhdr size = 56 bytes
rqry_test size = 288 bytes
rpprc_cmd size = 688 bytes
rread_cfg size = 172 bytes
rwait_evt size = 184 bytes
22:11:30-64772-22338- ******** starts Loading library for IPv6 *******
[ AF_INET6 = 22, AI_PASSIVE = 1 ]
getaddrinfo() : Linked on /usr/lib/libc.sl
inet_pton() : Linked on /usr/lib/libc.sl
inet_ntop() : Linked on /usr/lib/libc.sl
22:11:30-69584-22338- ******** finished Loading library **************
22:11:30-6fa06-22338- [horcmcfgrdf] access(conf_file) OK.
22:11:30-70ba4-22338- [horcmcfgrdf] access(check) OK.
22:11:30-71bc5-22338- [horcmcfgrdf] open(conf_file) OK.
22:11:30-756d0-22338- [horcmcfgetent] fseek(top) OK.
22:11:30-76c73-22338- ERROR: No Number in TID exists in HORCM_DEV: line 12
22:11:30-77fe8-22338- catest ldev1 CL1-F 0c 60
22:11:30-7a59d-22338- grpname:[catest] ipaddr:[192.168.44.5] port:[horcm7] are registered.
22:11:30-7b7ca-22338- [horcmcfgetent] read(conf_file) OK.
22:11:30-7c77c-22338- [horcmcfgrdf] close(conf_file) OK.
22:11:30-7d80d-22338- ERROR:horcm_cfg_create
22:11:35-72efb-22337- horcmgr:Failed to connect to HORCM.
root@HR-BKUP1#


# xpinfo -i
Device File ALPA Tgt Lun Port CU:LDev Type Serial#
/dev/rdisk/disk500 dc 0c 60 CL1F 3f:ff OPEN-V 00058751
/dev/rdisk/disk521 ac 0f 7ff CL2F 01:ff OPEN-V-CM 00058751

Please tell me what is wrong with this..
GuyPaul
Occasional Advisor

Re: Raid manager error with continuous access

I noticed that your HORCM_MON ip_address/hostname has a '_' while your actual hostnames have hyphens in them. If horcm can't resolve the hostname it will fail.

You can also try changing HORCM_MON to this:


HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
NONE horcm7 1000 3000

This will allow HORCM to bind to any Nic on your system. If this works then it is likely because of not being able to resolve hostname.

HTH

Nedved
Frequent Advisor

Re: Raid manager error with continuous access

I changed the server address to NONE instead of hostname.. but still getting the same error.
From the log i am suspecting it's having problem with lun id. but could not find the what is the problem.
because i mentioned the correct lun id ton the conf file. ( xpinfo output also showing the same lun id )

suggest yr idea to solve this issue.
GuyPaul
Occasional Advisor

Re: Raid manager error with continuous access

According to the HORCM startup error message

22:11:30-76c73-22338- ERROR: No Number in TID exists in HORCM_DEV: line 12
22:11:30-77fe8-22338- catest ldev1 CL1-F 0c 60

you are using HORCM_DEV and it is not finding the target ID (TID). Here is the syntax:

HORCM_DEV
#dev_group dev_name port# TargetID LU# MU#
Group dev CL1-A 3 1
Group1 dev1 CL1-A 3 1
Nedved
Frequent Advisor

Re: Raid manager error with continuous access

This is the horcm_dev field in my DC horcm file.

HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
none horcm7 1000 6000

HORCM_CMD
#dev_name dev_name dev_name
/dev/rdsk/c1t15d7 /dev/rdsk/c6t15d7

HORCM_DEV
catest ldev1 CL1-F 0c 60


HORCM_INST
#dev_group ip_address service
catest DR horcm7


xpinfo output..

# xpinfo -i
Device File ALPA Tgt Lun Port CU:LDev Type Serial#
/dev/rdisk/disk500 dc 0c 60 CL1F 3f:ff OPEN-V 00058751
/dev/rdisk/disk521 ac 0f 7ff CL2F 01:ff OPEN-V-CM 00058751



GuyPaul
Occasional Advisor

Re: Raid manager error with continuous access

Use the output from raidscan:

ls /dev/rdsk/* | raidscan -find -I7

specifying PORT,TARG,LUN exactly as raidscan sees it..

If that does not work I suggest going back to HORCM_DEV format which is my preference
Michael Leu
Honored Contributor

Re: Raid manager error with continuous access

And why not put /dev/rdisk/ as HORCM_CMD instead of the /dev/rdsk/?
---------------------------------------------------------------------------------
Navigation: Forum Site Map // ye olde ITRC Tree
@HP: please get rid of the Passport login timeout
Nedved
Frequent Advisor

Re: Raid manager error with continuous access

I modified the command device to /dev/rdisk/. but still same problem.
Nedved
Frequent Advisor

Re: Raid manager error with continuous access

using this option
ls /dev/rdsk/* | raidscan -find -I7

i find the correct TID of that ldev and now i can able to successfully start the instance.
But still i can't able to display pairs getting the following error.

root@DC-TEST#./pairdisplay -I7 -g catest
pairdisplay: [EX_INVMUN] Invalid mu# with HORC/UR or HOMRCF
Refer to the command log(/HORCM/log7/horcc_DC-TEST.log) for details.
root@HR-BKUP1#cat /HORCM/log7/horcc_DC_TEST.log

CMDLINE : ./pairdisplay -I7 -g catest
18:40:58-609e5-19515- [pairdisplay] Invalid muno(0) is used in remote devname(ldev-1).
18:40:58-64437-19515- [pairdisplay][exit(220)]
[EX_INVMUN] Invalid mu# with HORC/UR or HOMRCF
[Cause ]:The MU# of the volume to be operated is not appropriate.
[Action]:Please confirm the mu#(MU#1/2/3 cannot be used for HORC, and MU#1/2 must be P-Vol for HOMRCF, MU#1/2/3 must be P-VOL for UR) for the specified group using pairdisplay command.
COMMAND ERROR : EUserId for HORC[7] : root (0) Thu Mar 24 22:41:08 2011
CMDLINE : ./pairdisplay -I7 -g catest
22:41:08-b4c91-25053- ERROR:cm_sndrcv[rc < 0 from HORCM]
22:41:08-b8185-25053- [pairdisplay] R_RDCFG ERROR :rc = -10
22:41:08-b94f3-25053- grpname=catest devname=ldev1
22:41:08-bb474-25053- [pairdisplay][exit(246)]
[EX_ENODEV] No such device
[Cause ]:The device name which was designated with the option doesn't exist in the configuration file.
[Action]:Please confirm if the device name exists in the configuration file of the local and remote host.
COMMAND ERROR : EUserId for HORC[7] : root (0) Thu Mar 24 22:46:43 2011
CMDLINE : ./pairdisplay -I7 -g catwest
22:46:43-e38dd-25130- ERROR:cm_sndrcv[rc < 0 from HORCM]
22:46:43-e59a8-25130- [pairdisplay][exit(239)]
[EX_ENOGRP] No such group
[Cause ]:The group name which was designated or the device name doesn't exist in the configuration file,or the network address for remote communication doesn't exist.
[Action]:Please confirm if the group name exists in the configuration file of the local and remote host.
COMMAND ERROR : EUserId for HORC[7] : root (0) Thu Mar 24 22:46:57 2011
CMDLINE : ./pairdisplay -I7 -g catest
22:46:58-2c4ef-25131- [pairdisplay] Invalid muno(0) is used in remote devname(ldev1).
22:46:58-2e893-25131- [pairdisplay][exit(220)]
[EX_INVMUN] Invalid mu# with HORC/UR or HOMRCF
[Cause ]:The MU# of the volume to be operated is not appropriate.
[Action]:Please confirm the mu#(MU#1/2/3 cannot be used for HORC, and MU#1/2 must be P-Vol for HOMRCF, MU#1/2/3 must be P-VOL for UR) for the specified group using pairdisplay command.


Nedved
Frequent Advisor

Re: Raid manager error with continuous access

this is the current horcm file..

HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
DC-BKUP horcm7 1000 3000

HORCM_CMD
#dev_name dev_name dev_name
#/dev/rdsk/c1t15d7 /dev/rdsk/c6t15d7 /dev/rdsk/c12t15d7 /dev/rdsk/c18t15d7
/dev/rdisk/disk521

HORCM_DEV
#dev_group dev_name port# TargetID LU# MU#
#VG02 oradb2 CL1-A 1 1 0
catest ldev1 CL1-F 12 3
#HORCM_LDEV
#dev_group dev_name Serial# CU:LDEV(LDEV#) MU#
#catest ldev-1 25938 00:78 0



HORCM_INST
#dev_group ip_address service
catest DR-TEST horcm7

GuyPaul
Occasional Advisor

Re: Raid manager error with continuous access

Carefully check each horcm7.conf file.
The error message

Invalid muno(0) is used in remote devname(ldev1).

is telling you that your mirror_unit (MU) #
is invalid.

Considering that your DC node is using HORCM_DEV without a MU# which is optional
I would suspect you are either using HORCM_LDEV format on DR side or are using a
MU# with HORCM_DEV.

In any case, your horcm config appears incorrect
Nedved
Frequent Advisor

Re: Raid manager error with continuous access

this is the current conf file in DC and DR. But i can't find anything wrong in the conf file.


DR
________________________________________________________________________
# pairdisplay -I7 -g catest
Group PairVol(L/R) (Port#,TID, LU),Seq#,LDEV#.P/S,Status,Fence,Seq#,P-LDEV# M
catest ldev1(L) (CL1-F , 0, 3)25875 121.S-VOL PAIR ASYNC ,----- 121 -
catest ldev1(R) (CL1-F , 0, 3)25875 121.S-VOL PAIR ASYNC ,----- 121 -

#cat /etc/horcm7.conf
HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
NONE horcm7 1000 3000

HORCM_CMD
#dev_name dev_name dev_name
/dev/rdisk/disk22

HORCM_DEV
#dev_group dev_name port# TargetID LU# MU#
catest ldev1 CL1-F 00 03

HORCM_INST
#dev_group ip_address service
catest DC-BKUP horcm7



DC
________________________________________________________________________
# pairdisplay -I7 -g catest

pairdisplay: [EX_INVMUN] Invalid mu# with HORC/UR or HOMRCF
Refer to the command log(/HORCM/log7/horcc_DC-TEST.log) for details.


cat /etc/horcm7.conf
HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
NONE horcm7 1000 3000

HORCM_CMD
#dev_name dev_name dev_name
#/dev/rdsk/c1t15d7 /dev/rdsk/c6t15d7 /dev/rdsk/c12t15d7 /dev/rdsk/c18t15d7
/dev/rdisk/disk521

HORCM_DEV
#dev_group dev_name port# TargetID LU# MU#
catest ldev1 CL1-F 12 3


HORCM_INST
#dev_group ip_address service
catest DR-BKUP horcm7
Nedved
Frequent Advisor

Re: Raid manager error with continuous access

Also i am using CA Journal..