HORCM error [EX_INVMUN] Invalid mu# with HORC/UR or HOMRCF

[amit murde_1]

Hello,

I am tryingto setup raidmanager between and XP 24K and an XP20K.
I could create the CA sync pair between the 2 xp's find but cannot get HORCM working.
pairdisplay -g catest -l works find in both sites showing the status of the local LDEV.
--------------

C:\HORCM\etc>pairdisplay -g catest -l
Group PairVol(L/R) (Port#,TID, LU),Seq#,LDEV#.P/S,Status,Fence,Seq#,P-LDEV# M
catest Drive12T(L) (CL3-A-1, 1, 5)45287 29.P-VOL PAIR NEVER ,25482 17 -
-------------------------
However if I try to check the status og the remote LDEV by
pairdisplay -g catest -

C:\HORCM\etc>pairdisplay -g catest
pairdisplay: [EX_INVMUN] Invalid mu# with HORC/UR or HOMRCF
Refer to the command log(C:\HORCM\log0\horcc_bkpdc002_log.txt) for details.
-----
following is the extract from the log file
----------
CMDLINE : pairdisplay -g catest
11:19:15-0a7f8-03736- [pairdisplay] Invalid muno(10) is used in remote devname(Drive12T).
11:19:15-0a7f8-03736- [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.
----------------
I have tried MU# valur 0 or none or 4 but nogo

-------------
horcm0
---------
#/************************* For HORCM_MON *************************************/
HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
10.95.66.153 horcm0 6000 3000

#/************************** For HORCM_CMD ************************************/
HORCM_CMD
#dev_name dev_name dev_name
\\.\PHYSICALDRIVE13

#/************************** For HORCM_DEV ************************************/
HORCM_LDEV
#dev_group dev_name Serial# CU:LDEV(LDEV#) MU#
catest Drive12T 45287 00:1D 10



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

HORCM_INST
#dev_group ip_address service
catest 10.95.66.158 horcm1

-----
horcm1
----
#/************************* For HORCM_MON *************************************/
HORCM_MON
#ip_address service poll(10ms) timeout(10ms)
10.95.66.158 horcm1 6000 13000

#/************************** For HORCM_CMD ************************************/
HORCM_CMD
#dev_name dev_name dev_name
\\.\PHYSICALDRIVE2

#/************************** For HORCM_DEV ************************************/
HORCM_LDEV
#dev_group dev_name Serial# CU:LDEV(LDEV#) MU#
catest Drive12T 25482 00:11 10


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

HORCM_INST
#dev_group ip_address service
catest 10.95.66.153 horcm0

----------
Please note that from the XP web console I am able to operate the sync pair without problems.

I would appreciate any inputs on this.

[IBaltay]

Hi,

some ideas:

1. in HPUX try to check the execution logs:

HORCM/loginstance/curlog/horcm_hostname.log,
HORCM/loginstance/horcm_hostname.log,

HORC startup log files:
$HORCM_LOG/horcm_host.log,
$HORCC_LOG/horcc_host.log and horcc_host.log.old,

ERR log file
$HORCM_LOG/horcmlog_HOST/horcm.log

TRACE files
$HORCM_LOG/horcmlog_HOST/horcm_PID.trc
$HORCM_LOG/horcmlog_HOST/horcc_PID.trc

CORE files
$HORCM_LOG/core_HOST_PID/core

2. HOMRCF may use the $HORCC_MRCF envir var, which sets the exec environment for XP BC commands. This var determines if the command applies to XPCA or XPBC. If you use the XPCA only, its not necessary to set this var.

3. $HORCMPERM var is set by default in HPUX in either /etc/horcperm.conf or /etc/horcpermn.conf (n=instance number)
you can check it via cat $HORCMPERM -find inst
from here you can see the permitted LDEVs/(LVMs) for the appropriate MU#.
...

[Nigel Poulton]

Hi,

May be Im missing something :-S

but last time I wrote a HORCM file for CA, you did not specify an MU (mirror unit) number.

You only use MU with Business Copy...... right??????

Remove the MU number (10 in your examples above) and it will be assumed that it is CA rather tha nBusiness Copy.

E.g. your HORCM_LDEV section should read -
catest Drive12T 45287 00:1D
and NOT
catest Drive12T 45287 00:1D 10

Hope this helps,

Nigel