Re install MSA30

[Torsten.]

You are right regarding the vgextend command - my fault.
But the command will tell you the disks already included in this VG.

I see in your ioscan you adjusted only 1 HBA to ID 6 - you must adjust the other adapter too.

Already adjusted:
ctl 9 0/3/1/1.6.0 sctl CLAIMED DEVICE Initiator

("6" is the initiator ID)

Make the same for /dev/mpt6 to prevent problems!

[Guillermo Rossney]

Not sure (Fabian was there), but it seems that technician tried to modify de initiatior-id to 6, but the system hangs.

At man pages of mptconfig we see

WARNINGS
Setting the initiator ID on a SCSI controller must be done with caution, since duplicate SCSI IDs on a SCSI bus can result in bus hangs, system hangs, and system panics. The mptconfig command will attempt to verify that no targets are using the specified ID before the change is allowed; however, in the case of multi-initiator (shared bus) configurations, the mptconfig command cannot detect the presence of other initiators on the SCSI bus. Use the ioscan command on any servers connected to the same SCSI bus to verify that the init_id selected is free before using the -i option.


It is safe and necessary to assign the same init-id for both controllers??

[Torsten.]

For 2 HBAs on the same bus one of them MUST be set to ID 6 - otherwise you will get an address conflict (problems like BUS hang etc.).

[Guillermo Rossney]

Thanks Torsten.

Just one of them must be set to 6? (as already we have), or both?

[Guillermo Rossney]

News regarding multipath, from our provider:

"As of HP-UX 11i Version 3, HP recommends using the multipathing inherent in
the mass storage stack, rather than LVM's alternate links. If you want to
use LVM's alternate links, you must use legacy device special files for
physical volumes, and disable the mass storage stack multipathing for those
legacy device special files, using the *scsimgr* command."

[Torsten.]

If your MSA30 is connected with 4 cables, on each bus 1 HBA must be set to 6, the other HBA to 7.

Do you use HP-UX 11i v3 (11.31)???
(run "uname -a")

[Torsten.]

If your MSA30 is connected with 4 cables, on each bus 1 HBA must be set to 6, the other HBA to 7.

Do you use HP-UX 11i v3 (11.31)???
(run "uname -a")

Unlikely, because the vgdisplay output would look different.

[Guillermo Rossney]

More talk with you, more think that our provider doesnt knows a bit about HP.

11.11 is our version.

I don't know much also, but at least i know my limitations.

There is something i cant understand:

you said:
ctl 9 0/3/1/1.6.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c7t6d0

Already changed, but i need to change also /dev/mpt6

I see at ioscan the following lines:

ext_bus 6 0/3/1/0 mpt CLAIMED INTERFACE SCSI Ultra320 1
/dev/mpt6
ext_bus 4 0/4/1/0 mpt CLAIMED INTERFACE SCSI Ultra320 1
/dev/mpt4
ext_bus 7 0/3/1/1 mpt CLAIMED INTERFACE SCSI Ultra320 1
/dev/mpt7
ext_bus 5 0/4/1/1 mpt CLAIMED INTERFACE SCSI Ultra320 1
/dev/mpt5


doesnt mean that initiator id for /dev/mpt6 is set to 6 ??

[Torsten.]

Please run "olrad -q" to see the relation between the hardware path and the slot number.

In your rp3410 server, the relation is like this:

0/4/1 - top slot
0/3/1 - second from top

Back to your ioscan, this is important:

ext_bus 6 0/3/1/0 mpt CLAIMED INTERFACE SCSI Ultra320 1
/dev/mpt6
target 8 0/3/1/0.7 tgt CLAIMED DEVICE
ctl 6 0/3/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c6t7d0
ext_bus 7 0/3/1/1 mpt CLAIMED INTERFACE SCSI Ultra320 1
/dev/mpt7
target 14 0/3/1/1.6 tgt CLAIMED DEVICE
ctl 9 0/3/1/1.6.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c7t6d0

This is the card in the "second from top" slot.
The card has a dualbus controller, 1 is set to ID 6 (0/3/1/1.6.0 ... Initiator), 1 to 7 (0/3/1/0.7.0 ... Initiator).

If your cable goes like this:

HBA in 0/3/1 -> MSA A1 : A2 -> HBA in 0/4/1

and

HBA in 0/3/1 -> MSA B1 : B2 -> HBA in 0/4/1

I would set both controllers on the card in 0/3/1 to "6" - in this case
/dev/mpt6
and
/dev/mpt7

The card in 0/4/1 must remain at ID 7 for both controllers.

Doing this, you have the following IDs on each bus:

7 - the first HBA
0
1
2
3
4
5
8 - the disks (fixed)
15 - the chassis controller (fixed)
6 - the second HBA

Every ID is unique - this is important.

Clear enough now?

[Guillermo Rossney]

I think more clear is not possible.
Thank you very much!

We will work on this today, and we'll comment later.

Thanks again!