Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Another vscsi on VIO server problem 1

Status
Not open for further replies.

Gloups

IS-IT--Management
Sep 16, 2003
394
FR
Hi all

i was trying to had a new hdispower to mu VIO server but something seems to be wrong.

I can see my hdiskpower using lspv

hdisk104 none None
hdisk105 none None
hdisk106 none None
hdisk107 none None
hdisk108 none None
hdisk109 none None
hdiskpower17 none None




I also see it with powermt:

# powermt display dev=hdiskpower17
Pseudo name=hdiskpower17
CLARiiON ID=CK200044900139 [P570_VIOS]
Logical device ID=600601609BD41200C65D4E663AF8D911 [LUN 23]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP B, current=SP B
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
0 fscsi0 hdisk104 SP A0 active alive 0 0
0 fscsi0 hdisk105 SP A2 active alive 0 0
0 fscsi0 hdisk106 SP B0 active alive 0 0
0 fscsi0 hdisk107 SP B2 active alive 0 0
1 fscsi1 hdisk108 SP B1 active alive 0 0
1 fscsi1 hdisk109 SP A1 active alive 0 0



I'd like to attach it to VHOST1

$ lsmap -vadapter vhost1
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost1 U9117.570.654491E-V3-C11 0x00000001

VTD vtscsi2
LUN 0x8100000000000000
Backing device hdiskpower2
Physloc U7879.001.DQD0GJA-P1-C4-T1-L15

VTD vtscsi3
LUN 0x8200000000000000
Backing device hdiskpower3
Physloc U7879.001.DQD0GJA-P1-C4-T1-L16

VTD vtscsi11
LUN 0x8300000000000000
Backing device hdiskpower12
Physloc U7879.001.DQD0GVB-P1-C4-T1-L26


But when i use mkvdev:

$ mkvdev -vdev hdiskpower17 -vadapter vhost1
Method error (/usr/lib/methods/cfg_vt_scdisk):
0514-070 Only disks that support multi-path I/O (MPIO) or which
have a physical volume identifier (PVID) or an IEEE volume name may be
used as a virtual target device.


Have i forgoten something ?? Also strange the lun is correctly seen as attach to my VIOS partition in navisphere but without hdiskpower information

 
I have no idea if this will help or not but I figured I would throw it out there. I noticed in the error message one of the possible issues was not having a PVID. You can have a PVID created for your hdiskpower by running the following command:

chdev -l hdiskpower17 -a pv=yes

Again, I have no idea if this will fix your issue but it seems like it might help.


Jim Hirschauer
 
try to add the name of the vscsi device you are creating to the end of the command.

mkvdev -vdev hdiskpower17 -vadapter vhost1 -dev VSCSIDEVNAME




 
Thank's for all, i've juste assigned a pvid to my hdiskpower and all is ok
 
Hi

Clarion is not supported yet on the vio server.
You need to build the multipathing over manuell mpio on you hdisks.

 
I disagree with you AIX5L, i've already configured clariion disks for 5 virtual partitions with powerpath 4.3 and 4.4 installed on the vios and all is ok exept this problem of pvid attribution
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top