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!

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

vscsi on VIO server

Status
Not open for further replies.
unixfreak

unixfreak

ISP
Oct 4, 2003
632
GB

Hi, why am I seeing this:

$ mkvdev -vdev sawct_rvg1 -vadapter sawct_scsi0 -dev vhost6
Method error (/usr/lib/methods/define -g -d):
0514-025 Cannot perform the requested function because the parent of the specified device does not exist.

LV is there, vhost6 says available:

$ lsdev -virtual | grep vhost6
vhost6 Available Virtual SCSI Server Adapter

Does anyone know which parent device it's talking about?

Cheers
 
Sort by date Sort by votes
hdisk37 is an ESS LUN (disk)
with -dev -vt xxxxxxx you can choose a name for the virtual target device (naming convention P11 stays for LPAR 11)
the vadapter can not be choosen
the backing device can be a disk or a logical volume (see the output of the lsdev -virtual)


mkvdev -vdev hdisk37 -vadapter vhost7 -dev vt_p11_lun012

$ lsmap -vadapter vhost7
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost7 U9117.570.659C3DE-V1-C111 0x0000000b

VTD vt_p11_lun001
LUN 0x8200000000000000
Backing device hdisk25
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5611000000000000

VTD vt_p11_lun002
LUN 0x8300000000000000
Backing device hdisk26
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5612000000000000

VTD vt_p11_lun003
LUN 0x8400000000000000
Backing device hdisk27
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5707000000000000

VTD vt_p11_lun004
LUN 0x8500000000000000
Backing device hdisk28
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5708000000000000

VTD vt_p11_lun005
LUN 0x8600000000000000
Backing device hdisk29
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5613000000000000

VTD vt_p11_lun006
LUN 0x8700000000000000
Backing device hdisk30
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5709000000000000

VTD vt_p11_lun007
LUN 0x8800000000000000
Backing device hdisk31
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5614000000000000

VTD vt_p11_lun008
LUN 0x8900000000000000
Backing device hdisk32
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L570A000000000000

VTD vt_p11_lun009
LUN 0x8a00000000000000
Backing device hdisk33
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5615000000000000

VTD vt_p11_lun010
LUN 0x8b00000000000000
Backing device hdisk34
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L570B000000000000

VTD vt_p11_lun011
LUN 0x8c00000000000000
Backing device hdisk36
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L512F000000000000

VTD vt_p11_lun012
LUN 0x8d00000000000000
Backing device hdisk37
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L570C000000000000

VTD vt_p11_rootvg
LUN 0x8100000000000000
Backing device p11_rootvg
Physloc

$ lsdev -virtual
name status description

ent2 Available Virtual I/O Ethernet Adapter (l-lan)
ent3 Available Virtual I/O Ethernet Adapter (l-lan)
vhost0 Available Virtual SCSI Server Adapter
vhost1 Available Virtual SCSI Server Adapter
vhost2 Available Virtual SCSI Server Adapter
vhost3 Available Virtual SCSI Server Adapter
vhost4 Available Virtual SCSI Server Adapter
vhost5 Available Virtual SCSI Server Adapter
vhost6 Available Virtual SCSI Server Adapter
vhost7 Available Virtual SCSI Server Adapter
vsa0 Available LPAR Virtual Serial Adapter
vt_p10_lun001 Available Virtual Target Device - Disk
vt_p10_lun002 Available Virtual Target Device - Disk
vt_p10_lun003 Available Virtual Target Device - Disk
vt_p10_lun004 Available Virtual Target Device - Disk
vt_p10_lun005 Available Virtual Target Device - Disk
vt_p10_lun006 Available Virtual Target Device - Disk
vt_p10_lun007 Available Virtual Target Device - Disk
vt_p10_lun008 Available Virtual Target Device - Disk
vt_p10_lun009 Available Virtual Target Device - Disk
vt_p10_lun010 Available Virtual Target Device - Disk
vt_p10_lun011 Available Virtual Target Device - Disk
vt_p10_lun012 Available Virtual Target Device - Disk
vt_p10_lun013 Available Virtual Target Device - Disk
vt_p10_lun014 Available Virtual Target Device - Disk
vt_p10_lun015 Available Virtual Target Device - Disk
vt_p10_rootvg Available Virtual Target Device - Logical Volume
vt_p11_lun001 Available Virtual Target Device - Disk
vt_p11_lun002 Available Virtual Target Device - Disk
vt_p11_lun003 Available Virtual Target Device - Disk
vt_p11_lun004 Available Virtual Target Device - Disk
vt_p11_lun005 Available Virtual Target Device - Disk
vt_p11_lun006 Available Virtual Target Device - Disk
vt_p11_lun007 Available Virtual Target Device - Disk
vt_p11_lun008 Available Virtual Target Device - Disk
vt_p11_lun009 Available Virtual Target Device - Disk
vt_p11_lun010 Available Virtual Target Device - Disk
vt_p11_lun011 Available Virtual Target Device - Disk
vt_p11_lun012 Available Virtual Target Device - Disk
vt_p11_rootvg Available Virtual Target Device - Logical Volume
vt_p4_lun001 Available Virtual Target Device - Disk
vt_p4_lun002 Available Virtual Target Device - Disk
vt_p4_rootvg Available Virtual Target Device - Logical Volume
vt_p5_lun001 Available Virtual Target Device - Disk
vt_p5_rootvg Available Virtual Target Device - Logical Volume
vt_p6_lun001 Available Virtual Target Device - Disk
vt_p6_lun002 Available Virtual Target Device - Disk
vt_p6_rootvg Available Virtual Target Device - Logical Volume
vt_p7_rootvg Available Virtual Target Device - Logical Volume
vt_p8_rootvg Available Virtual Target Device - Logical Volume
vt_p9_rootvg Available Virtual Target Device - Logical Volume

 
Upvote 0 Downvote
unixfreak -

What do you get from lsmap -vadapter vhost6 ?

You're command was this:
mkvdev -vdev sawct_rvg1 -vadapter sawct_scsi0 -dev vhost6

Is sawct_rvg1 the lv you want to make into a vscsi called sawct_scsi0 ? If so, then you're syntax is correct.

 
Upvote 0 Downvote
you can not determine the name of the vadapter's : they are always vhost0 through vhostn.

$ $ lsmap -vadapter vhost6
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost6 U9117.570.659C3DE-V1-C110 0x0000000a

VTD vt_p10_lun001
LUN 0x8200000000000000
Backing device hdisk10
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L560A000000000000

VTD vt_p10_lun002
LUN 0x8300000000000000
Backing device hdisk11
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L560B000000000000

VTD vt_p10_lun003
LUN 0x8400000000000000
Backing device hdisk12
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5701000000000000

VTD vt_p10_lun004
LUN 0x8500000000000000
Backing device hdisk13
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L560C000000000000

VTD vt_p10_lun005
LUN 0x8600000000000000
Backing device hdisk14
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5702000000000000

VTD vt_p10_lun006
LUN 0x8700000000000000
Backing device hdisk15
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L560D000000000000

VTD vt_p10_lun007
LUN 0x8800000000000000
Backing device hdisk16
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5703000000000000

VTD vt_p10_lun008
LUN 0x8900000000000000
Backing device hdisk17
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L560E000000000000

VTD vt_p10_lun009
LUN 0x8a00000000000000
Backing device hdisk18
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5704000000000000

VTD vt_p10_lun010
LUN 0x8b00000000000000
Backing device hdisk19
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5229000000000000

VTD vt_p10_lun011
LUN 0x8c00000000000000
Backing device hdisk20
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5326000000000000

VTD vt_p10_lun012
LUN 0x8d00000000000000
Backing device hdisk21
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L560F000000000000

VTD vt_p10_lun013
LUN 0x8e00000000000000
Backing device hdisk22
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5705000000000000

VTD vt_p10_lun014
LUN 0x8f00000000000000
Backing device hdisk23
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5130000000000000

VTD vt_p10_lun015
LUN 0x9000000000000000
Backing device hdisk35
Physloc U7879.001.DQD10AB-P1-C4-T1-W5005076300C49A41-L5227000000000000

VTD vt_p10_rootvg
LUN 0x8100000000000000
Backing device p10_rootvg
Physloc
 
Upvote 0 Downvote

I got it working. Don't know how but it suddenly accepted it. Thanks anyway.

Cheers
 
Upvote 0 Downvote
raylin -

you can determine the vhost number by looking at the slot number of "Server SCSI". It's not a direct correlation, however, the lowest slot number will come in vhost0, and they will increment together.

For example:

if you have slot10, 20, 30, 40 define as "Server SCSI" on the VIO server(s) they will come in as slot10 - vhost0, slot20 - vhost1, slot30 - vhost2, slot 40 - vhost3.

You should try and following a naming convention. Maybe something like slots 10,11,12,13,14 for vhost0,1,2,3,4

my2cents
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

E
  • Locked
  • Question
AIX Power5 on 5.3- On varyonvg error "cannot be varied on because no good copies of the descriptor area"
Replies
1
Views
469
JenLM
J
David Figueiredo
  • Locked
  • Question
CDE on AIX
Replies
0
Views
282
David Figueiredo
David Figueiredo
bjvail
  • Locked
  • Question
IBM PS700 replaced, map existing drives on DS3500
Replies
1
Views
222
iggsterman
iggsterman
spricer
  • Locked
  • Question
Virtual I/O Ethernet Adapter not showing up in VIO after adding virtual adapter in profile
Replies
0
Views
205
spricer
spricer
Amandeep Gautam
  • Locked
  • Question
VIO server not finding image to boot
Replies
1
Views
231
Amandeep Gautam
Amandeep Gautam

Part and Inventory Search

Sponsor

Back
Top