Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

iSCSI on AIX (VIO server)

613 views
Skip to first unread message

bomahony

unread,
Oct 13, 2009, 10:18:48 AM10/13/09
to
When in oem_setup_env

I have a server that is hosting 4 iSCSI disks from one remote target.
From etc/iscsi/targets
172.16.164.110 3260 iqn.1991-05.com.microsoft:tinycluster-tiny-target

When i check the disks assigned to the system:
bash-3.2# lspv
hdisk0 00018afa8221fa12 rootvg
active
hdisk1 00018afa70e83fa0 rootvg_clients
active
hdisk3 00018afa3adc172a None
hdisk4 00018afa3b0c1380 None
hdisk5 00018afa3b0fcb37 None
hdisk6 00018afa3b11e8ca None

these disks are then assigned using the VIO server ona disk basis to
mLPARs ( two mLPARs, with two assigned to each). Is it possible to
check which diisk is which on the iSCSI target from the VIO server. I
need to edit two of the disks, and dont want to delete the wrong ones.

Is it also possible to see the disk sizes etc from VIO?

(I cant run many of the lspv commands as the devices are not assigned
to a volume group on the VIO server, but instead have their VGs
assigned in the mLPARs)

Thanks

B

Message has been deleted

bomahony

unread,
Oct 14, 2009, 7:30:46 AM10/14/09
to
Tony, none of these worked:


bash-3.2# lscfg -vl hdisk2
hdisk2 Other iSCSI Disk Drive

Manufacturer................MSFT
Machine Type and Model......Virtual HD
ROS Level and ID............332E3020
Serial Number...............
Device Specific.(Z0)........000005925B000002
Device Specific.(Z1)........

bash-3.2# lsattr -El hdisk2
clr_q no Device
CLEARS its Queue on error True
host_addr 172.16.164.110
Hostname or IP Address False
location
Location Label True
lun_id 0x0
Logical Unit Number ID False
max_transfer 0x40000
Maximum TRANSFER Size True
port_num 0xcbc PORT
Number False
pvid 0001f26adcaba4970000000000000000
Physical volume identifier False
q_err yes Use
QERR bit True
q_type simple
Queuing TYPE True
queue_depth 1 Queue
DEPTH True
reassign_to 120
REASSIGN time out value True
rw_timeout 30 READ/
WRITE time out value True
start_timeout 60 START
unit time out value True
target_name iqn.1991-05.com.microsoft:tinycluster-tiny-target Target
NAME False
bash-3.2# bootinfo -s /dev/hdisk2
0

leszekwd

unread,
Oct 16, 2009, 3:27:51 AM10/16/09
to
On 13 Paź, 16:18, bomahony <bomah...@gmail.com> wrote:
[...]

> these disks are then assigned using the VIO server ona  disk basis to
> mLPARs ( two mLPARs, with two assigned to each). Is it possible to
> check which diisk is which on the iSCSI target from the VIO server. I
> need to edit two of the disks, and dont want to delete the wrong ones.

Hello,
In VIO env. (padmin) lsmap command show You various information about
mapping physical dev's to virtual ones.
'lsmap -all' show You all mappings, and 'lsmap -vadapter vhostXXX'
show You devices (i.e. disks) assigned to LPAR. vhostXXX's (Virtual
SCSI Server Adapter) physloc on VIOS is similar to physloc from lscfg
-vl hdiskY on LPAR - i.e U9117.MMA.1223344-V8-C15-T1.
Its 5th element (C15) should be the same on VIO and LPAR.
When You fit 5th element, You can compare LUN and/or PVID parameters
on both VIO and LPAR.

Example:
On VIOS:
$ lsmap -all
SVSA Physloc
Client Partition ID
-------------------------
---------------------------------------------------
----------------------------
vhost0 U9117.MMA.1223344-V8-C12 0x000005

VTD vtscsi0
LUN 0x81000000000
Backing device hdisk2
Physloc U789E.005.DQWERS-P3-D3

SVSA Physloc
Client Partition ID
-------------------------
---------------------------------------------------
----------------------------
vhost1 U9117.MMA.1223344-V3->>>C14<<<
0x000007

VTD vtscsi0
LUN >>>0x81000000000<<<
Backing device hdisk4
Physloc U789E.005.DQWERS-P3-D5

$ lspv | grep hdisk4
hdisk4 >>>00c5cf123c543abc<<< None

==========
On LPAR:

# lscfg -vl hdisk0 # <- we should repeat this command for all
disk and match which interesting us

hdisk0 U9117.MMA.1223344-V7->>>C14<<<-
>>>L81000000000<<< Virtual SCSI Disk

# lspv | grep hdisk0
hdisk0 >>>00c5cf123c543abc<<<
rootvg active

I've marked by >>>...<<< parameters to compare.

With these information You should identify the disks.

>
> Is it also possible to see the disk sizes etc from VIO?
>

In oem_setup_env try a command:
lsattr -El hdiskXX
example:
lsattr -El hdisk4

On my system I can see size of the disk, but I think that not for all
systems it can be the same.

I hope that it will help You.

Best Regards
Leszek Duda

bomahony

unread,
Oct 16, 2009, 10:57:07 AM10/16/09
to
I eventually got it working, using bootinfo. I was using "bootinfo -s /
dev/hdiskX" when it should have been "bootinfo -s hdiskX"

Thanks for the help guys.

I know this isnt related, but just as a matter of interest, on the
actual mLPARs, how do i see what is attached to a vscsi interface?
eg if i do lsdev | grep vscsi, it lists vscsi0 and vscsi1, Im just
wondering what is attached. [I have been doing some mucking about with
attaching and dropping disks and so on and just want to make sure
everything is cleared off]

leszekwd

unread,
Oct 16, 2009, 11:58:29 AM10/16/09
to
On 16 Oct, 16:57, bomahony <bomah...@gmail.com> wrote:

> I know this isnt related, but just as a matter of interest, on the
> actual mLPARs, how do i see what is attached to a vscsi interface?

You can see it using on mLPAR:
lsdev -Cp vscsiX

This command shows what devices are attached to vscsiX.

Best Regards,
Leszek Duda

0 new messages