How create the alternate link

[RNC]

Hello all,

I have the next problem, I have a HP9000 conected to a VA7100 (with alternate link), but now I added one lun to the vg, and I don't see the alternate link, 2questions:
- How can I create the alternate link
- Do I need to create the pv?

Thanks in advanced

PV Name /dev/dsk/c7t2d4
PV Name /dev/dsk/c5t2d4 Alternate Link
PV Status available
Total PE 1279
Free PE 0
Autoswitch On

PV Name /dev/dsk/c7t4d1
PV Status available
Total PE 2559
Free PE 18
Autoswitch On

[xertusit]

Try to :
insf -e

This command scan all hardware and recreate the special file.

After you could see:
c574d1
and you execute:
vgextend vgXXXX /dev/dsk/c574d1

Regards,
Massimo

[Tom Danzig]

Does /dev/dsk/c5t4d1 exist? Is it the date stamp on the file the same as /dev/dsk/c7t4d1
?

If so, just add /dev/dsk/c5t4d1 into the volume group via vgextend.

[A. Clay Stephenson]

1) execute ioscan -fn to detect new devices
2) execute insf -e
3) Now add the alternate path using vgextend. Man vgextend for details.

[Mark Greene_1]

Yes, create the pv for the lun and if there are multiple paths to it, for each path.

Then vgextend the volume group to point to the new physical volumes. See man vgextend for the proper syntax and special instructions.


mark

[RNC]

but when I execute the insf -e, I not obtain the /dev/dsk/c5t4d1 (but the file exists)

[xertusit]

if the file exists try to
rmsf /dev/dsk/c5t4d1

then

ioscan -fn
insf -e
vgextend

Regards,
Massimo

[RNC]

I execute the insf -e, but I obtain the insf: Installing special files for sdisk instance 21 address 0/4/0/0.1.16.39.0.4.1, but no the
insf: Installing special files for sdisk instance 21 address 0/7/0/0.1.16.42.0.4.1

[xertusit]

can you put in attach the output of:

ioscan -fn

Regards,
Massimo

[Tom Danzig]

If /dev/dsk/c5t4d1 exists, the host can see the disk via the alternate path. As explained above, simply do:

vgextend /dev/ /dev/dsk/c5t4d1

Naturally, substitute with the actual volume group name.

[RNC]

That is the output of vgextend


vgextend: Couldn't open physical volume "/dev/dsk/c5t4d1":
Invalid argument

[RNC]

output of ioscan -fnC diks:

Class I H/W Path Driver S/W State H/W Type Description
==================================================================================
disk 0 0/0/1/1.2.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 1 0/0/2/0.2.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
disk 2 0/0/2/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
disk 8 0/4/0/0.1.16.39.0.0.0 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c7t0d0 /dev/rdsk/c7t0d0
disk 9 0/4/0/0.1.16.39.0.0.1 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c7t0d1 /dev/rdsk/c7t0d1
disk 10 0/4/0/0.1.16.39.0.2.1 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c7t2d1 /dev/rdsk/c7t2d1
disk 26 0/4/0/0.1.16.39.0.2.4 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c7t2d4 /dev/rdsk/c7t2d4
disk 11 0/4/0/0.1.16.39.0.2.7 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c7t2d7 /dev/rdsk/c7t2d7
disk 15 0/4/0/0.1.16.39.0.3.2 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c7t3d2 /dev/rdsk/c7t3d2
disk 24 0/4/0/0.1.16.39.0.3.4 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c7t3d4 /dev/rdsk/c7t3d4
disk 19 0/4/0/0.1.16.39.0.3.5 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c7t3d5 /dev/rdsk/c7t3d5
disk 17 0/4/0/0.1.16.39.0.3.6 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c7t3d6 /dev/rdsk/c7t3d6
disk 13 0/4/0/0.1.16.39.0.4.0 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c7t4d0 /dev/rdsk/c7t4d0
disk 21 0/4/0/0.1.16.39.0.4.1 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c7t4d1 /dev/rdsk/c7t4d1
disk 3 0/7/0/0.1.16.42.0.0.0 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
disk 4 0/7/0/0.1.16.42.0.0.1 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c5t0d1 /dev/rdsk/c5t0d1
disk 5 0/7/0/0.1.16.42.0.2.1 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c5t2d1 /dev/rdsk/c5t2d1
disk 27 0/7/0/0.1.16.42.0.2.4 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c5t2d4 /dev/rdsk/c5t2d4
disk 6 0/7/0/0.1.16.42.0.2.7 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c5t2d7 /dev/rdsk/c5t2d7
disk 16 0/7/0/0.1.16.42.0.3.2 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c5t3d2 /dev/rdsk/c5t3d2
disk 25 0/7/0/0.1.16.42.0.3.4 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c5t3d4 /dev/rdsk/c5t3d4
disk 20 0/7/0/0.1.16.42.0.3.5 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c5t3d5 /dev/rdsk/c5t3d5
disk 18 0/7/0/0.1.16.42.0.3.6 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c5t3d6 /dev/rdsk/c5t3d6
disk 14 0/7/0/0.1.16.42.0.4.0 sdisk CLAIMED DEVICE HP A6188A
/dev/dsk/c5t4d0 /dev/rdsk/c5t4d0

[Tom Danzig]

Try: insf -H 0/7

[RNC]

Continue the same problem, I can't see the path ot the hardaware in the /0/7,,,

[Tom Danzig]

Perhaps you're running a version of SecurePath (or something along those lines) that is restricting host access of the LUN through this alternate path.

[Mark Greene_1]

Have you tried removing and recreating the /dev/dsk/c5t2d4 file? If you got the wrong major number or used a duplicate minor number when you did the mknod, that might be the problem here.

mark

[James A. Donovan · Accepted solution]

I'm basing my answer on my experience witht the VA7400, but I think it may still be relevant....

I'd guess that you have Secure Manager running. I've seen this problem happen when I only add one of my HBA's the security settings for a newly created LUN.

Use the armsecure command or the CommandView GUI to give your 2nd HBA access to the new LUN

[RNC]

Hello all! that was the problem, I had that modified the secure table it wasn't in the table. Now it is working properly.

Thanks all for all.

[Senthil Kumar .A_1]

Hi RNC,

Happy that it has resolved your issue. I see lot of guys responded to your query in getting you through this issue. The post by Jim Donovon has been spot on with your problem. If I were you , I would award him a Bunny and others some points, for there effort in getting this issue resolved.

Regards,
Senthil Kumar .A

[RNC]

Thanks all for all!