Disk Enclosures
cancel
Showing results for
Did you mean:

SOLVED
Go to solution

## pairdisplay error

Output from one volume group pairdisplay -g BC1_PRBIDDAT -fc
Group PairVol(L/R) (Port#,TID,LU-M),Seq#,LDEV#.P/S,Status, % ,P-LDEV# M
BC1_PRBIDDAT prbiddat.1-1(L) (CL1-A , 7, 5-0)55239 138..P-VOL PSUS, 99 74 W
BC1_PRBIDDAT prbiddat.1-1(R) (CL1-A ,12, 5-0)55239 63..P-VOL PSUS, 0 219 W
BC1_PRBIDDAT prbiddat.1-2(L) (CL1-A , 6, 4-0)55239 157..P-VOL PSUS, 0 225 W
BC1_PRBIDDAT prbiddat.1-2(R) (CL1-A , 0, 2-0)55239 293..SMPL ----,----- ---- -

Output from the second volume group

pairdisplay -g BC1_PRIN1 -fc
Group PairVol(L/R) (Port#,TID,LU-M),Seq#,LDEV#.P/S,Status, % ,P-LDEV# M
BC1_PRIN1 prin1.1-1(L) (CL1-A ,10, 6-0)55239 41..P-VOL PSUS, 61 51 W
BC1_PRIN1 prin1.1-1(R) (CL1-A , 0, 0-0)55239 291..SMPL ----,----- ---- -
BC1_PRIN1 prin1.1-2(L) (CL1-A , 0, 1-0)55239 292..SMPL ----,----- ---- -
BC1_PRIN1 prin1.1-2(R) (CL1-A , 0, 3-0)55239 294..SMPL ----,----- ---- -

It looks to me that all the disks which have a target ID zero are the with SMPL.

18 REPLIES
Honored Contributor
Solution

## Re: pairdisplay error

You are right. Second field in (CL1-A , 0, 0-0) is TID.

And all LDEVs with TID 0 are SMPL (Not paired) whereas other LDEVs are showing PSUS (Pair has been suspended).

sks
A rigid mind is very sure, but often wrong. A flexible mind is generally unsure, but often right.
Honored Contributor

## Re: pairdisplay error

But it is quite intriguing as some volumes in a volume group are SMPL and some are PSUS.

Generally all show the same state. Was the paircreate sucessful and COPY operation started?

sks
A rigid mind is very sure, but often wrong. A flexible mind is generally unsure, but often right.

## Re: pairdisplay error

hi SKS
I have not done any paircreate, can you may be take me through all the necessay steps i have to take in order to have the disks in the required state.
Thanks

## Re: pairdisplay error

To All,

We added a disk to the primary vol to extend it and then added a disk to the secondary vol to match primary. After that we edit the horc0.conf for primary and horc1.conf for secondary to include target ID's of new disks.

Afterwhich we re-start the horcmgr, then try to do pairresync -g. It is at this point that we get error?
Honored Contributor

## Re: pairdisplay error

My sugeestion is:

Create a new group name for all the newly added LDEVs in the horcm file. This name has to be different from the existing groups (BC1_PRBIDDAT or BC1_PRIN1).

1. Use the following command to check the correctness of horcm file:
# pairdisplay -c -g group_name

2. Check the status with the command:
# pairdisplay -g group_name -fcx

3. Run paircreate to create the pair.
# paicreate -g group_name -vl

[Note: The configuration file does not indicate whether a volume will be a P-Vol or an S-Vol. This is determined by the -vl (local) or -vr(remote) option.]

4. Check the status with the command:
# pairdisplay -g group_name -fcx

5. Once the pairdisplay show the status of the volumes in the group as PAIR, split the pair with the following command.
# pairsplit -g group_name

6. Resync the split pairs with:
#pairresync -g group_name

sks
A rigid mind is very sure, but often wrong. A flexible mind is generally unsure, but often right.

## Re: pairdisplay error

hi SKS
Thanks for responding, but i'm afraid the names of the vg cannot be changed. Can you give us more suggestions.

## Re: pairdisplay error

Hi SKS

I followed your suggestion and this is what I got.
pairdisplay command just return the same output as the my 1st thread, and paircreate bring this error:COMMAND ERROR : EUserId for HOMRCF : root (0) Fri Aug 13 08:21:46 2004
CMDLINE : paircreate -g BC1_PRBIDDAT -vl
08:21:46-5d2ab-18909- [paircreate] Pairstatus must be SIMPLEX.: local PSUS, remote PSUS, devname prbiddat.1-1
08:21:46-6b770-18909- [paircreate][exit(228)]
[EX_INVSTP] Invalid pair status
[Cause ]:The pair status of a target volume isn't appropriate.
[Action]:Please confirm volume status using the pairdisplay command.
Honored Contributor

## Re: pairdisplay error

Hello Bakang

You have got me wrong. Let me put it again:

1. You had some LDEVs defined in horcm file as below:

#dev_group dev_name port# TargetID LU# MU#
BC1_PRBIDDAT prbiddat.1-1 CL1-A 7 5

2. Now you have added some LDEVs. For these LDEVs you need to have a different dev_group as below: (Don't make any change for existing BC1_PRBIDDAT group in the horcm file)

#dev_group dev_name port# TargetID LU# MU#
abcdefgh pr123456 CL1-A 0 0

3. Now when you issue paircreate command issue it only for dev_group=abcdefgh as below:

CMDLINE : paircreate -g abcdefgh -vl

I hope this helps. All the best.

sks
A rigid mind is very sure, but often wrong. A flexible mind is generally unsure, but often right.

## Re: pairdisplay error

SKS
I think I am lost now. When you say dev_group what are you taking about, is it not the same as volume group? To me they look the same.

BC1_PRBIDDAT prbiddat.1-1(R) (CL1-A ,12, 5-0)55239 63..P-VOL PSUS, 0 219 W
this disk is one we foind on the volume group already working just fine

BC1_PRBIDDAT prbiddat.1-2(R) (CL1-A , 0, 2-0)55239 293..SMPL ----,----- ---- -
this one is the disk which we used to extend the volume group with.

Maybe we don't understand each other. Do you have a phone number I can posiibly call you and then talk ....

I hope that does not offend you.

Honored Contributor

## Re: pairdisplay error

I am sorry since it is one way communication.

1. dev_group is same as volume group.

BC1_PRBIDDAT prbiddat.1-1(R) (CL1-A ,12, 5-0)55239 63..P-VOL PSUS, 0 219 W

2. this disk is one we foind on the volume group already working just fine

Very Good.

3. Now in the following Ldev/disk you have to give a name different than BC1_PRBIDDAT and then do paircreate.

BC1_PRBIDDAT prbiddat.1-2(R) (CL1-A , 0, 2-0)55239 293..SMPL ----,----- ---- -
this one is the disk which we used to extend the volume group with.

I am sure we now understand each other.

sks

A rigid mind is very sure, but often wrong. A flexible mind is generally unsure, but often right.
Honored Contributor

## Re: pairdisplay error

I am leaving office. Will resume on Monday. All the best.

sks
A rigid mind is very sure, but often wrong. A flexible mind is generally unsure, but often right.
Honored Contributor

## Re: pairdisplay error

Hello Bakang

Has the issue resolved?

sks
A rigid mind is very sure, but often wrong. A flexible mind is generally unsure, but often right.
Occasional Visitor

## Re: pairdisplay error

Hi,
I think your horcm.conf files are not good, normaly, the state of the local (L) and remote (R) volumes are the same, the local volume cannot be PSUS and the remote volume SMPL. They must be (L) P-VOL PSUS and (R) S-VOL SSUS or (L) SMPL and (R) SMPL. Verify your TID with RAIDSCAN and adjust your horcmxx.conf files. Verify also you exported HORCM_INST=xxx and HORCC_MRCF=1

Then, you will just have to do a paircreate on your new disk (these that are SMPL) with this command on the :

paircreate -g BC1PRBIDDAT -d prbiddat.1-2 -f xxx -vl
Occasional Visitor

## Re: pairdisplay error

Hi,

paircreate -g BC1PRBIDDAT -d prbiddat.1-2 -f xxx -vl does xxx mean the one used by HORCM_INST=xxx.

Please clarify the use of -f in paircreate
Honored Contributor

## Re: pairdisplay error

-f [CTGID] Specify the fence_level(never/status/data/async)

"fence level" is set up on the MCU. The fence level is a way to maintain the data integrity despite the distance that can between MCU and RCU:

1. data: This fence level is intended to maintain full data integrity at all times. If the RCU is down, all I/O to the P-Vol is prohibited.

2. status: A status level fence requires RAID Manager XP and a network connection between supported hosts. The RAID Managers contact each other to verify if the RCU is down but the ESCON connection is up; I/O to the MCU is still allowed.

3. never: MCU I/O is never interrupted.

sks
A rigid mind is very sure, but often wrong. A flexible mind is generally unsure, but often right.
Honored Contributor

## Re: pairdisplay error

Hello Bastien

I understood from the post as below:

1. Few Ldev were in the PSUS (Split) mode in the BC.

2. Subsequently few more LDEV were added in the horcm configuration and their status was correctly shown as SMPL (simplex - not currently paired).

3. Now these new added Ldevs have to be part of another group so as to use paircreate -g command.

sks

A rigid mind is very sure, but often wrong. A flexible mind is generally unsure, but often right.

## Re: pairdisplay error

To All,

The scenerio is that we had volumes working jus fine and we could do Business Copy. Now becoz of the growth in our Production DB we had to extend the volumes, this we did. Now the disks we added are all in SMPL and the ones that were already there in the volumes are PSUS.

We need to move to a point where all the volumes are consistent so that we could do a Business Copy?
Honored Contributor

## Re: pairdisplay error

My understanding is correct.

You have to do another paicreate using a new dev_group or volume group (different from BC1_PRBIDDAT) in the horcm configuration file.

Steps have been covered in my previous posts.

sks
A rigid mind is very sure, but often wrong. A flexible mind is generally unsure, but often right.